search

souldiver / open9x

Automatically exported from code.google.com/p/open9x
0 stars 0 forks source link

Improving FRSKY Telemetry with MegapirateNG #229

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
Which board (stock / gruvin9x / sky9x) are you using?
stock

What is your open9x FW version?
r2050
What is your open9x EEPROM version?
the one from r2050
What steps will reproduce the problem?
1.connecting FRSKY telemetry to Crius AIOP
2.making the FRSKY-Mod in Turnigy 9x
3.trying to get readings from voltage/current sensor via FRSKY-Telemetry and 
MegapirateNG 2.9.1r6 running on Crius AIOP v2.0

What is the expected output? What do you see instead?
I expect to get 11.1V shown on 9x when the tlelmetry reading in ArduPlanner is 
11.1V

instead i got 458,... V shown (thus it can display only 99.9V max it showed 
58,...)

Please provide any additional information below.
I changed the code in frsky.cpp:

code\

#if defined(FAS_BSS)
      frskyData.hub.vfas = (frskyData.hub.volts_bp * 10 + frskyData.hub.volts_ap);
#else
      //frskyData.hub.vfas = ((frskyData.hub.volts_bp * 100 + frskyData.hub.volts_ap * 10) * 21) / 110; //original
      frskyData.hub.vfas = ((frskyData.hub.volts_bp * 100 + frskyData.hub.volts_ap) / 2) / 10; //works correctly
#endif

\code

Original issue reported on code.google.com by hanno.dahlhaus on 10 Mar 2013 at 2:12

GoogleCodeExporter commented 8 years ago 
The code is correct for the real FAS-100 and FAS-40 sensors. I think the 
correction should rather take place in the Megapirate firmware so that it 
complies with the FrSky protocol...

Original comment by bernet.a...@gmail.com on 10 Mar 2013 at 3:26

GoogleCodeExporter commented 8 years ago 
That is the other possibility I tried. The resolution is worse like that. it 
shows voltages in 0.2V steps.
What about the idea of adding an additional Sensor-Hub to choose from, which 
complies with MegapirateNG? I added the change to test it and I get a good 
resolution into 0.1V steps.
Just the question if it pays out the additional work to do so. The change in 
MegapirateNG is smaller than adding an additional sensor hub to open9x.

Original comment by hanno.dahlhaus on 10 Mar 2013 at 4:42

GoogleCodeExporter commented 8 years ago 
Right, we could add the support of another HW as replacement of the Hub. Should 
not cost too much flash.

Original comment by bson...@gmail.com on 13 Mar 2013 at 12:43

GoogleCodeExporter commented 8 years ago 
Depends on, if you want to do that. I do not have the overview, how much space 
in the eeprom is left. If you are interested, I can post a list of parameters 
here which are sent from the megapirateng via the frsky telemetry.

Original comment by hanno.dahlhaus on 13 Mar 2013 at 12:57