Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Please add decode of Frsky FLVSS and MLVSS Lipo sensors #3

Open
mkornmue opened this issue Mar 19, 2024 · 2 comments
Open

Please add decode of Frsky FLVSS and MLVSS Lipo sensors #3

mkornmue opened this issue Mar 19, 2024 · 2 comments

Comments

@mkornmue
Copy link

Please add decode of Frsky FLVSS and MLVSS Lipo sensors

@zs6buj
Copy link
Owner

zs6buj commented Mar 21, 2024

Hmm. Wombat. Are you in Australia? I'm in Adelaide, SA for a while.

FrSkyToWiFiBT was written specifically for the DIY range of "sensors", and we adopted physical sensor ID 0x1b for what was popularly named"FrSky Passthru" protocol, where essential telemetry was transcoded from Mavlink.

The FrSky voltage sensor modules use a physical ID of 0x02 I believe. I got this from the FrSky setup instructions for MLVSS

ID Set Up
Each type of FrSky Smart Port enabled sensor has its unique physical ID. The default physical ID for this sensor is 02
The ID number could be changed by FrSky Servo Channel Changer. Please refer to the instruction manual of
FrSky Servo Channel Changer for details.

So we can either change the FrSkyToWiFiBT code, or you can try using FrSky Servo Channel Changer. To change the code, go to the FrSky_Simple_Ports.h tab, line 438

      if (buf[1] == 0x1b) {   // our DIY sensor

and change it to:

     if (buf[1] == 0x02) {   // FrSkyX physical ID

Since the sensors are reported to support S.Port, it may well work, provided that you don't also have other sensors on the S.Port daisy chain. If you do, try this:

      if ( (buf[1] == 0x1b) ||  (buf[1] == 0x02) )           {   // FrSky physical ID

@zs6buj
Copy link
Owner

zs6buj commented Mar 21, 2024

One more thig: I will have to add some code in the decode function.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants