Telemetry - OpenLRS and APM

Hi

I have been trying to get telemetry to work with my OpenLRS RX and TX. Been trying out different setups and baud rates but not got it to work.

 

The transparent serial bridge is working perfectly but when I try to connect the RX to the APM Telemetry port (port 3) I cannot connect via Mission Control. Running a serial monitor I can see traffic - ascii in the beginning saying something like "<startup_mode: ground>" and then binary. Seems to be ok... but not good enough to connect.

 

I think the problem might be related to bandwidth. OpenLRS supports 750 byte/seconds from the RX to TX. After looking at the documentation and source code I have not figured out how much data MAVLink protocol is configured to send per second.

Does anybody know?

 

Regards,
Jesper

You need to be a member of diydrones to add comments!

Join diydrones

Email me when people reply –

Replies

        • What radio and what tx/rx module do you have. Try to erase the eprom from your minimosd, burn the bootloader and flash again with the 19200 baudrate firmware version from the website and see if this solves the problem. 

          • Hi!

            By now I have tried flashing with the bootloader and the firmware from the site. Still not displaying any osd info, just video feedthrough.

            Any ideas?

            Thanks

            • Check the cable. If you have another apm, try flashing the minimosd with normal firmware (5700) and see if it's working.

              3702888017?profile=original

              • Thanks. Tried with a second set micro APM and OSD. When connecting to the apm with openlrs I get the following behaviour:

                - No overlay when switching on (either one of the 2 minimOSDs)

                - When pressing the button on the OSD, I get an overlay saying minimOSD and the version. Strangely one osd says 2.4 r805 and the other 2.4 r719, although I tried flashing both first with the standard MinimOSD extra and then with yours. Received "done" message every time in the tool.

                - After pressing the button on the osd and waiting for booting to finish they both display "no mavlink data"

                When connecting the two minimOSDs to an APM without openlrs, I get the following:

                - The minimOSD with r805 displays the overlay fine right away when powering up

                - The minimOSD with r719 does not display anything, not even after pressing the button

                No clue what's going on. I have some hypothesis. Do you think one of the following could be happening:

                - Flashing is not successful, despite the "done" message. Could explain the different versions.

                - The minimOSD with r719 is broken

                What else could it be?

                Thanks!

                • Try to flash the r719 to the working one, and the r805 to the non-working one. This way you will know if the r719 minimosd is broken. (Did you check the wires?)

                  • Cabling checked. Also I already get telemetry via the openlrs to the transmitter and that is on the same set of cables.

                    Tried both osds with both firmwares now. Looks like one is really not working. Does not display anything on my quad, while the other one does, independent of firmware. Both of the osds are out of HK micro apm set.

                    Got a third osd, which is the original minimOSD (bigger than the one from the HK micro set I had used before). Flashed with r805 and also says "no mavlink data"...

                    Will check my APM settings again.

                    Could it be that this has to do that I am using a microAPM from HK (and not a normal sized APM or Pixhawk)?

          • Thanks, AlbEagle. This is my setup:

            - HK micro APM set (incl. APM, OSD, etc.)

            - HK orange openlrs RX (100mW)

            - HK orange openlrs TX (1W) on a Turnigy 9XR

            Flashing the firmware from your page worked without error. So, not sure if that is the problem. However, I had not burned the bootloader. Will try this in 2 weeks, when I am home again.

            Thanks!

  • Hello Martin.

    I am using Gitsly some month ago (not updated from months) and i have two issues, sometimes it lost bind and sometimes it lost full configuration, for example i am using PPM and i have to re-assign PPM to this channel.

    and with droidplanner i can not receive parameters and i can not send flight plans, all other fuctions works perfectly.

    Do someone have this wiorking exactly as 3DR radios?

    • Hi there,

      I have exactly the same problem as Jose 

      When connecting via 3DR radios in APM Planner everything works fine:

      Parameters downloads and I can Upload and Download Waypoints etc.

      I have tried various alternatives including using Openlrsng and ULRS but end up having the same problem:

      Parameters do not upload even when leaving for long periods, when I cancel the parameter upload, Airspeed ALT Roll and Pitch GPS updates without problem, but I can not upload or download Way points. It seems to timeout.

      Jose have you found a solution?

      • Hi there found the problem,

        The ground wire coming from the telemetry port was broken inside the insulation, new wires soldered in and all working now!!! 

This reply was deleted.

Activity

DIY Robocars via Twitter
RT @a1k0n: Did I get rid of hand-tuned parameters? Yes. Am I still hand-tuning more parameters? Also yes. I have a few knobs to address the…
16 hours ago
DIY Robocars via Twitter
RT @a1k0n: I'm not going to spoil it, but (after charging the battery) this works way better than it has any right to. The car is now faste…
16 hours ago
DIY Robocars via Twitter
RT @a1k0n: Decided to just see what happens if I run the sim-trained neural net on the car, with some safety rails around max throttle slew…
21 hours ago
DIY Robocars via Twitter
Saturday
DIY Robocars via Twitter
RT @SmallpixelCar: @a1k0n @diyrobocars I learned from this. This is my speed profile. Looks like I am too conservative on the right side of…
Saturday
DIY Robocars via Twitter
RT @a1k0n: @SmallpixelCar @diyrobocars Dot color is speed; brighter is faster. Yeah, it has less room to explore in the tighter part, and t…
Saturday
DIY Robocars via Twitter
RT @a1k0n: I'm gonna try to do proper offline reinforcement learning for @diyrobocars and throw away all my manual parameter tuning for the…
Friday
DIY Robocars via Twitter
RT @circuitlaunch: DIY Robocars & Brazilian BBQ - Sat 10/1. Our track combines hairpin curves with an intersection for max danger. Take tha…
Thursday
DIY Robocars via Twitter
RT @SmallpixelCar: Had an great test today on @RAMS_RC_Club track. However the car starts to drift at 40mph. Some experts recommended to ch…
Sep 11
DIY Robocars via Twitter
RT @gclue_akira: 世界最速 チームtamiyaのaiカー https://t.co/1Qq2zOeftG
Sep 10
DIY Robocars via Twitter
RT @DanielChiaJH: Always a good time working on my @diyrobocars car at @circuitlaunch. Still got some work to do if I’m to beat @a1k0n howe…
Sep 10
DIY Robocars via Twitter
RT @SmallpixelCar: My new speed profile for @RAMS_RC_Club track https://t.co/RtLb7TcgIJ
Sep 10
DIY Robocars via Twitter
RT @SmallpixelCar: Practiced at @RAMS_RC_Club today with my new @ARRMARC car https://t.co/AEu2hCx89T
Aug 28
DIY Robocars via Twitter
Aug 24
DIY Robocars via Twitter
RT @gclue_akira: 柏の葉で走行させてるjetracerの中身 #instantNeRF #jetracer https://t.co/giVvuE4hP7
Jul 4
DIY Robocars via Twitter
Cool web-based self-driving simulator. Click save when the AI does the right thing https://github.com/pncsoares/self-driving-car
Jul 4
More…