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

X4R HDOP issue? #1

Open
zatie12 opened this issue Sep 15, 2015 · 4 comments
Open

X4R HDOP issue? #1

zatie12 opened this issue Sep 15, 2015 · 4 comments

Comments

@zatie12
Copy link

zatie12 commented Sep 15, 2015

A great project and very useful on the Taranis!

I have observed when using the X8R receiver the HDOP is reported correctly on the Taranis Plus. When using the X4R-SB receiver, the HDOP is flipping between the correct value (e.g. 1.5) to an incorrect value in the region of 8.5 to 9.9 about once per second. All other telemetry values work normally.

Thanks

@ptsneves
Copy link
Owner

That is very strange and it sounds like a problem, and I hope a Lua script problem. Can you tell me what are the most obvious differences between the receivers as I wasn't able to fully understand what the differences might be?

@zatie12
Copy link
Author

zatie12 commented Sep 17, 2015

I'm not sure what's different between them technically other than the X4R has 3 channel outputs and 1 Serial BUS output which can be connected into Pixhawk. It has an SPort for telemetry but otherwise it seems to behave in the same was as the X8R.

The telemetry seems to work normally for all other parameters. It's only the HDOP which seems to be fluctuating. Perhaps there is something different happening on A2 on the X4R, but I'm not sure due to lack of knowledge/data on the inner workings of these receivers unfortunately.

@ptsneves
Copy link
Owner

Hopefully the 2.1.3 version of the Lua scripts will not have that problem as I reworked the hdop calculation and as far as I know it should work flawlessly. I tested it today. Stay tunned.

@ptsneves ptsneves reopened this Oct 15, 2015
@ptsneves
Copy link
Owner

@zatie12 Can you confirm if the problem persists in the new 2.1.3 version of the scripts?

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