search

DeBesten / opentx

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

No DIST values on telemetry screen #78

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
Which board (stock / gruvin9x / sky9x / Taranis) are you using?
Stock
What is your openTx FW version?
r2647
What is your openTx EEPROM version?
213-3
What steps will reproduce the problem?

1. Using openXVario
2. Configure openXvario to send values as DIST
3. Configure openTx to display DIST on telemetry screen

What is the expected output? What do you see instead?
Displayed value is allways zero.

Please provide any additional information below.
Same issue in r2491, works on r2413 with the same hardware setup (seems to be 
not an openXvario problem).

Original issue reported on code.google.com by Steinlau...@gmail.com on 27 Jul 2013 at 6:07

GoogleCodeExporter commented 8 years ago 
DIST is the distance from the pilot to the plane, why would you like to use it 
for something else?

Original comment by bson...@gmail.com on 27 Jul 2013 at 9:19

GoogleCodeExporter commented 8 years ago

Original comment by bson...@gmail.com on 27 Jul 2013 at 10:13

GoogleCodeExporter commented 8 years ago 
openXvario can be configured to send values like pressure or absolute height as 
DIST, i.e. for debugging purposes. But that's not the point. If openTx receives 
the dataID 0x3c inside a dataframe, the following value should be displayed as 
DIST, or am I wrong? In r2413 it seem to happen that way.

Original comment by Steinlau...@gmail.com on 28 Jul 2013 at 11:36

GoogleCodeExporter commented 8 years ago 
No. DIST is calculated from the GPS. Impossible!

Original comment by bson...@gmail.com on 28 Jul 2013 at 2:10

GoogleCodeExporter commented 8 years ago 
> DIST is calculated from the GPS.

... and then send back to tx with dataID 0x3c and (not) displayed by openTx?

Original comment by Steinlau...@gmail.com on 28 Jul 2013 at 3:03

GoogleCodeExporter commented 8 years ago 
Actually no GPS device send id 0x31:

DIST is calculated inside the radio,

In version 2413 telemetry data was overwriting the memory location just by 
chance.
Then the frsky.cpp was changed to avoid this sort of issues.

Original comment by romolo.m...@gmail.com on 28 Jul 2013 at 3:08

GoogleCodeExporter commented 8 years ago 
o.k. thanks for explaining and
many thanks for your work on openTx :-)

Original comment by Steinlau...@gmail.com on 28 Jul 2013 at 3:38

GoogleCodeExporter commented 8 years ago 
I would prefer we setup another field for that. Perhaps CSTM, with a special ID 
(always the same, not used by FrSky). Not a dirty hack which overwrites the 
structure and could do wrong things!

Original comment by bson...@gmail.com on 28 Jul 2013 at 3:52

GoogleCodeExporter commented 8 years ago 
This issue was closed by revision r2693.

Original comment by bson...@gmail.com on 30 Jul 2013 at 8:28

GoogleCodeExporter commented 8 years ago 
Both consumption and power are now possibly sent by openXsensor on IDs 0x35 and 
0x37

Original comment by bson...@gmail.com on 30 Jul 2013 at 8:28