Mavlink to FrSky S.Port Passthru Converter for LRS or PX4 Pro

Hoehenarbeit · January 16, 2020, 6:39am

I am not using a pwm channel for rssi, only the 109 mavlink injected rssi values. With the RFD modules (as far as I know) it is not possible to set up a pwm based rssi reporting.

edit. I have spoken with the RFD guys and they told me, that the rssi values only start to get injected, when heartbeat packets are received (so when I connect to MissionPlanner).

Eric_Stockenstrom · January 16, 2020, 3:47pm

Hi David, so your proposal to fake the rssi until MP connects is probably the best option. I actually have a pair of RFD900s that work very well. I just have not played with their settings for a while. Then ULRS and DL settings just confuse matters. You could send me a Pull Request, or I can just do a little patch. Thank you for your valuable input.

Hoehenarbeit · January 17, 2020, 6:56am

I created a pull request (my first one ever) for you. Hope this helps, maybe we should make a #define for it in config.h. RFD specific settings or similar.

Also I have discovered a different issue. While flying the yaapu scipt keeps repeating my current flight mode and sometimes stabilized, even though I don´t have stabilized configured. Also it sometimes tells me “armed” and “disarmed” randomly. Ever encountered this before? Is this an issue with MAV2PT or the yaapu script?

Eric_Stockenstrom · January 18, 2020, 6:54am

Hi David, thanks for the PR. I’m happy to merge it.

While flying the yaapu scipt keeps repeating my current flight mode and sometimes stabilized

I fixed this in 2.50 on 12-01-2020. The remark was

Eliminate annoying periodic “Stabilized Flight Mode” announcements.

Maybe you didn’t flash the latest? Could you check it out and let me know?

I think it might be useful for non-rfd900 users to also have a dummy rssi as default. It will get overwritten by a true rssi when/if one arrives. The upside is that we don’t always have the confusing “can’t connect” issue. We could make the value easily identifiable, like 66%

Hoehenarbeit · January 20, 2020, 6:29am

I fixed this in 2.50 on 12-01-2020. The remark was
Eliminate annoying periodic “Stabilized Flight Mode” announcements.

I am using 2.50.

Eric_Stockenstrom · January 20, 2020, 7:45am

I added a few small issues after the first push

yak-54 · January 25, 2020, 8:05am

\MavlinkToPassthru.git\trunk\Mav2PT_v2.52\Mav2PT_v2.52.ino:2119:69: error: ‘mavlink_msg_scaled_imu_get_temperature’ was not declared in this scope

       ap26_temp = mavlink_msg_scaled_imu_get_temperature(&R2Gmsg);   ?

bit lost on this one

Eric_Stockenstrom · January 25, 2020, 10:18am

imu temp is new in Mavlink 2. Just get the latest c_library_v2 library here

Eric_Stockenstrom · January 27, 2020, 1:00pm

RDP900x

Hoehenarbeit David

13d

Is there any chace you would port the code to the RFD transmitter module ? It has an ESP8266, which is already implemented in your code. You would only (probably) have to change the pins.

Hi David, I flashed mav2pt_v2.54 onto the txmod this morning, using their OTA, and everything seems to work fine. You might need to play around with the S.Port out pin to suit your circumstances.

If you use AP mode the IP will be the same as the txmod.

If you need to re-flash the txmod firmware, simply use the mav2pt OTA.

EDIT: The mav2pt OLED display also works on the esp8266 if you would like to use it.

Hoehenarbeit · January 29, 2020, 7:36am

I´ll definiatelly test this. How did you compile for the ESP8266? And which pin did you use for the S.Port?

Eric_Stockenstrom · January 29, 2020, 8:25am

I compiled using both the Arduino IDE and PlatformIO, using the NodeMCU 1.0 (ESP-12E) board profile. I used D6 for the S.Port, but you could change to any unused pin.

#elif (Target_Board == 4)         // ESP8266 Platform
  #if (ESP8266_Variant == 1)        // Node MFU 12F
   
    #define MavStatusLed  D0        // Mavlink Status LED
    #define BufStatusLed  99        // None
   //                     D4        // TXD1 - Debug log out                            
    #define FC_Mav_rxPin  D9        // RXD0 default  
    #define FC_Mav_txPin  D10       // TXD0 default    
    #define Fr_rxPin      D5        // GP10 SPort - Not used in single wire mode
    #define Fr_txPin      D6        // GPIO SPort - Use me 
    #define SCL           D1        // I2C OLED board   
    #define SDA           D2        // I2C OLED board

yak-54 · January 30, 2020, 10:28pm

Morning all i got issue i have noted that yaapu script will only work after i have connected to mission planer

Eric_Stockenstrom · January 31, 2020, 6:34am

Hey Yak-man

Did you upgrade Arducopter to 4.0?

yak-54 · January 31, 2020, 7:44am

got it working had to re flash the teensy with Mav2PT_v2.50
i am using 4.0.1 chopper

yak-54 · January 31, 2020, 7:47am

i have just finished removing Frsky X8R receiver and replacing it with RFD900x on the S-bus on a chopper

Eric_Stockenstrom · January 31, 2020, 7:56am

Ah, ok. Do you get good rssi before you connect to MP, or dummy 69%. See David’sposts above.

yak-54 · January 31, 2020, 8:05am

i never been able to get rssi working with rfd900x

Eric_Stockenstrom · January 31, 2020, 8:12am

The newer mav2pt should select mavlink message type #109 for SiK firmware radios (like RFD900). Could you try #define Debug_Rssi, but flash

(v2.51 2020-01-18 Make default rssi 69% for SiK radios, like RFD900x. PR by Hasi123 ) or later version.

EDIT. We noticed that the SiK rssi message is not injected into the mavlink telemetry stream until MP connects.

yak-54 · January 31, 2020, 9:07am

ok Mp jumps to 241 every 3 sec and here is the putty log and the config.h i usedputty.zip (10.6 KB)

yak-54 · January 31, 2020, 9:09am

( Ah, ok. Do you get good rssi before you connect to MP, or dummy 69%. )
just get before MP dummy 69%