Skip to content

getPositionError always returns zeroes #40

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

Closed
reinzor opened this issue Jan 3, 2018 · 2 comments
Closed

getPositionError always returns zeroes #40

reinzor opened this issue Jan 3, 2018 · 2 comments
Labels

Comments

@reinzor
Copy link

reinzor commented Jan 3, 2018

pos = pypozyx.Coordinates()
pozyx.doPositioning(pos, pypozyx.POZYX_2D)
pos_error = pypozyx.PositionError()
pozyx.getPositionError(pos_error)
pos_error.data
[0, 0, 0, 0, 0, 0]
@ghost ghost added the question label Jan 4, 2018
@ghost
Copy link

ghost commented Jan 4, 2018

When positioning you can choose between two algorithms:

  • UWB-only gives you "raw positions", no filtering is done, this is the best algorithm to assess you anchor setup
  • Tracking will use current and historic positioning data and sensor data to build a mathematical model that gives more accurate results when the update rate is higher than 1 Hz. It almost always performs better than UWB-only.

The positioning algorithm is chosen using setPositionAlgorithm, both in Arduino as in Python. More information can be found in the Python docs and the register overview. The Arduino library is updated with the tracking algorithm, but the docs are lagging behind.

The Position Error is only available when using the Tracking algorithm.

@ghost ghost closed this as completed Jan 4, 2018
@dennismorits
Copy link

I have the same problem. I writing in Python ROS. I am using the tracking modes. Is there any other condition i have to fullfill.

This issue was closed.
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

2 participants