Replies

  • Hi All, sorry if this is redundant, but I can't figure out how to search this thread... Are there any other LUA scripts available that are compatible with this project? I see that the taranis is receiving Roll/Pitch as well as ACC values and a few other items that arne't represented in the "MAIN" lua script. I'd love to see another screen with these values exposed... Thanks for any pointers.

  • Hi Paul,

    Do you have logfiles with included telemetry data, I can use to work on the lua script within the companion software?

    Right now my drone isn't ready to fly, so I can't record them by myself.

    Thanks,

    Markus


  • Markus, I'll comment inline below:


    Markus Manninger said:

    OK, I already thought that the values have to get manipulated before getting displayed. They don't seem to be correct when discovered and displayed straight in the "find telemetry" menu.

    They get manipulated by the Taranis lua script - there are only a small handful of sensors on your sensor screen which can be understood directly. Sorry, I maybe didn't explain this clearly before.

    Thanks for the links, I'll take a look at them to get familiar with lua scripts.

    I do have the compiler (luac option) built into my horus firmware but that doesn't seem to be very handy - at least for developing. I don't want to get the SD out, update the Script, reboot the horus ... just to find out that there is a type.

    The compiler on the radio is purely to reduce the memory footprint of the code at runtime - on the Taranis (sorry don't know about the Horus) memory allocated to running lua is very limited so the compiled version often works fine where running text based lua will fail due to memory limitations - I had to also implement a load of other memory work-arounds to get my code to just run - even the compiled version (basically loading in and out of code as its required to keep memory use down). You develop the code on your PC and can test it in the simulator in the companion app (you can even simulate sensor values and look at the lua console to see messages in there to debug things). Companion runs the text based lua (it doesn't have the memory limitations that the radio does), so no need to compile for running code in Companion sim. Once you have it working, you can transfer it to the Horus radio over the USB cable using the synchronise SD card option you mentioned earlier. 

    Well, I guess I will read through the manuals and wikis. Do you know if its possible to simulate the script somehow in the companion software?

    Yes, read the wiki in full - I spent many hours getting it how it is today. The last part, I answered above. Good luck

  • OK, I already thought that the values have to get manipulated before getting displayed. They don't seem to be correct when discovered and displayed straight in the "find telemetry" menu.

    Thanks for the links, I'll take a look at them to get familiar with lua scripts.

    I do have the compiler (luac option) built into my horus firmware but that doesn't seem to be very handy - at least for developing. I don't want to get the SD out, update the Script, reboot the horus ... just to find out that there is a type.

    Well, I guess I will read through the manuals and wikis. Do you know if its possible to simulate the script somehow in the companion software?

  • Yes Markus, This is all described in the Wiki if you care to read through.

    You don't need to worry about compiling any new scripts you write, as OpenTx 2.2 takes care of this for you. You simply place the .lua file (your text version of the script) in the SCRIPTS/TELEMETRY folder on the SD card and the first time it runs (assuming you have the lua compile version of OpenTx 2.2 installed) the Horus/Taranis compiles a .luac file which it then runs.

    In my project, I started during the reign of OpenTx 2.0 and the only way to compile was to use a dedicated version of the Companion app, which did the compilation - but this is no longer require with the advent of 2.2.

    Like I mentioned previously, some of the sensors you discovered contain combinations of multiple (byte shifted) sets of telemetry data - again explained in the wiki, and the only way to extract these values and display them in sensible form is by using a lua script. There is a bit of a learning curve if you've never coded in lua before - especially in the cut down version which comes with OpenTx 2.2 - I got a load of help from the guys in this forum post: https://www.rcgroups.com/forums/showthread.php?2180477-LUA-scriptin...

    Good luck, Paul 

    RC Groups
    RC Groups - the most active Radio Control model community: electric and fuel rc airplanes,rc helis,rc boats and rc cars. Features discussion forums,…
  • Wow, actually it's much more easy then expected with the horus. In the model setup I switched to the telemetry tab and started discovering telemetry data and immediately all values showed up. After that it's possible to select these values in a widget in the telemetry setup. At least it's a beginning!

    I really want to get the distance between the GEO location of the horus internal GPS and the UAV calculated and displayed. This has to be done with a lua script.

    I know the scripts are pre-compiled and the binaries are installed on the transmitter. Does anyone know how to get the right compiler (compatible with OpenTX 2.2) and maybe a basic Makefile?

    Thanks,

    Markus

  • Paul Atherton said:

    Markus,

    Sorry, but the Telemetry screens have only been created for the Taranis radio, not for the Horus. If anyone out there is a horus lua guru, then would be good to see screens developed for the Horus also.

    The teensy side should work fine on your Pixhawk, and the data should be getting to your telemetry setup screen, just the same way it would on the Taranis radio (running OpenTx 2.2), but without a custom coded telemetry screen it won't be possible to display all of the telemetry items, as some are only available by programmatically decoding the telemetry sensor data.

    Cheers, Paul (aka 'athertop')

    OK, that's what I feared. Is there any way to check if the telemetry data is received by the horus? Even I have never did lua script programming, I think I can dig into it and try to get it working on the horus.

    Yesterday I found this site where telemetry data gets displayed on the horus for the KISS flightcontroller. Maybe that would be a good base for your projekt.

    Thanks for your reply,

    Markus



  • Markus Manninger said:

    Hi,

    I am trying to get the telemetry data to my Horus X12s, via X8R receiver. Did anyone already get this setup running?

    Here are some details:

    - X12s with OpenTX v2.2 (installed via companion with lua option enabled)

    - Teensy v3.2 with Mav_Sport2.1-2.2-master branch (installed via git clone)

    - Pixhawk with Ardupilot v3.4.2

    I tried to stick to the tutorial from [1] and configured the parameters in ardupilot and installed the teensy firmware as described. Now I stuck in configuring the X12s. But I don't know if the serial data is really send via the telemetry port2 to the teensy, if the teensy really encodes the messages and passes it on the X8R receiver and if the receiver really sends the data back to the horus in the right way.

    If all this is OK, I don't know how to include the lua scripts in the horus. All tutorials refer to the tanaris and I don't know if I can use them as they are.

    I appreciate  any help!

    [1] https://github.com/athertop/MavLink_FrSkySPort/wiki/1.-Setup

    Thanks,

    Markus

    Markus,

    Sorry, but the Telemetry screens have only been created for the Taranis radio, not for the Horus. If anyone out there is a horus lua guru, then would be good to see screens developed for the Horus also.

    The teensy side should work fine on your Pixhawk, and the data should be getting to your telemetry setup screen, just the same way it would on the Taranis radio (running OpenTx 2.2), but without a custom coded telemetry screen it won't be possible to display all of the telemetry items, as some are only available by programmatically decoding the telemetry sensor data.

    Cheers, Paul (aka 'athertop')

  • Hi,

    I am trying to get the telemetry data to my Horus X12s, via X8R receiver. Did anyone already get this setup running?

    Here are some details:

    - X12s with OpenTX v2.2 (installed via companion with lua option enabled)

    - Teensy v3.2 with Mav_Sport2.1-2.2-master branch (installed via git clone)

    - Pixhawk with Ardupilot v3.4.2

    I tried to stick to the tutorial from [1] and configured the parameters in ardupilot and installed the teensy firmware as described. Now I stuck in configuring the X12s. But I don't know if the serial data is really send via the telemetry port2 to the teensy, if the teensy really encodes the messages and passes it on the X8R receiver and if the receiver really sends the data back to the horus in the right way.

    If all this is OK, I don't know how to include the lua scripts in the horus. All tutorials refer to the tanaris and I don't know if I can use them as they are.

    I appreciate  any help!

    [1] https://github.com/athertop/MavLink_FrSkySPort/wiki/1.-Setup

    Thanks,

    Markus

    athertop/MavLink_FrSkySPort
    APM MavLink to FrSky S.Port converter. Contribute to athertop/MavLink_FrSkySPort development by creating an account on GitHub.
  • I will double check everything and do another flight to see if I can recreate the 'missing pointer' and post back here... thanks again.

    RK


    Paul Atherton said:

    The log shows a top speed of 18.343 m/s which is just over 40mph. Would suggest comparing what you see on the Taranis with Mission Planner to see if there is a discrepancy. Remember that Mission planner likely shows speed in km/h, so when doing the comparison, select the same for speed units in the LUA telemetry screen. Also remember that you need to keep the sensor configuration for Gspd set to 'kts' in the model's telemetry sensors page - this is the default scale that is assigned by OpenTx, and any other value set for this will cause it to scale incorrectly. Again, all detailed in the wiki here: https://github.com/athertop/MavLink_FrSkySPort/wiki/1.2.-FrSky-Tara...

    Cheers, Paul

This reply was deleted.

Activity

DIY Robocars via Twitter
RT @TinkerGen_: "The Tinkergen MARK ($199) is my new favorite starter robocar. It’s got everything — computer vision, deep learning, sensor…
Monday
DIY Robocars via Twitter
Monday
DIY Robocars via Twitter
RT @roboton_io: Join our FREE Sumo Competition 🤖🏆 👉 https://roboton.io/ranking/vsc2020 #sumo #robot #edtech #competition #games4ed https://t.co/WOx…
Nov 16
DIY Drones via Twitter
First impressions of Tinkergen MARK robocar https://ift.tt/36IeZHc
Nov 16
DIY Robocars via Twitter
Our review of the @TinkerGen_ MARK robocar, which is the best on the market right now https://diyrobocars.com/2020/11/15/first-impressions-of-tinkergen-mark-robocar/ https://t.co/ENIlU5SfZ2
Nov 15
DIY Robocars via Twitter
RT @Ingmar_Stapel: I have now explained the OpenBot project in great detail on my blog with 12 articles step by step. I hope you enjoy read…
Nov 15
DIY Robocars via Twitter
RT @DAVGtech: This is a must attend. Click the link, follow link to read the story, sign up. #chaos2020 #digitalconnection #digitalworld ht…
Nov 15
DIY Robocars via Twitter
RT @a1k0n: Got a new chassis for outdoor races (hobbyking Quantum Vandal) but I totally didn't expect that it might cause problems for my g…
Nov 11
DIY Drones via Twitter
First impressions of the Intel OpenBot https://ift.tt/36qkVV4
Nov 10
DIY Robocars via Twitter
Nov 9
DIY Robocars via Twitter
Excellent use of cardboard instead of 3D printing! https://twitter.com/Ingmar_Stapel/status/1324960595318333441
Nov 7
DIY Robocars via Twitter
RT @chr1sa: We've got a record 50 teams competing in this month's @DIYRobocars @donkey_car virtual AI car race. Starting today at 10:00am…
Nov 7
DIY Robocars via Twitter
Nov 6
DIY Robocars via Twitter
RT @a1k0n: Car's view, using a fisheye camera. The ceiling light tracking algorithm gave me some ideas to improve ConeSLAM, and having grou…
Nov 5
DIY Robocars via Twitter
RT @a1k0n: To get ground truth I measured the rug, found the pixel coordinates of its corners, calibrated my phone camera with my standard…
Nov 5
DIY Robocars via Twitter
RT @a1k0n: @DIYRobocars is back in December, but outside. Time to reinvestigate ConeSLAM! I rigged up a quick and dirty ground-truth captur…
Nov 5
More…