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

CRSF telemetry issues #1285

Closed
digitalentity opened this issue Feb 13, 2017 · 1 comment
Closed

CRSF telemetry issues #1285

digitalentity opened this issue Feb 13, 2017 · 1 comment
Labels
Milestone

Comments

@digitalentity
Copy link
Member

By Dronek @ RCG:

In my recent test I recorded a telemetry LOG on the taranis using crossfire CRSF protocol with micro v2 rx. I noticed that altitude is stored in meters but the actual values rather correspond to cm. The VFAS is apparently given out as a "RxBatt" sensor and the stored curve of sensor "CAPA" (mAh) is identical to VFAS alias "RxBatt". I looked into the telemetry code (crsf.c, crsf.h, telemetry.c, telemetry.h) but didn't find those names. Sorry, I'm not a coder but I'd like to know whether the telemetry issues are something that is done wrong by inav or do I have to address these issues somewhere else? Thanks.

Issue confirmed. Fix pending.

@digitalentity digitalentity added this to the 1.6 milestone Feb 13, 2017
@Dronek Dronek mentioned this issue Feb 13, 2017
@digitalentity
Copy link
Member Author

VBAT is correctly reported as RxBat (CRSF protocol designation for battery voltage). Altitude is incorrectly reported in [cm],

Question - should we report GPS altitude (above sea level) or estimated altitude (above launch)?

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

No branches or pull requests

1 participant