|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
|||
|
|||
|
Re: Navx Labview Issue
Quote:
Once calibration completes, the yaw can be zeroed at any time. In addition, a resolution was just release for an issue in the LabVIEW Library in this area. If an attempt was made to zero the yaw immediately after opening it, failures might occur. The updated library that resolves this issue is here: https://github.com/FRC900/navX-MXP-L...s/tag/v2.0.5.0 |
|
#2
|
||||
|
||||
|
Re: Navx Labview Issue
Is there a way to tell when the start-up calibration is complete? We are just now revisiting the Navx for autonomous and we're unable to zero any parameters. Are we not waiting long enough before resetting them to zero? Does the start-up calibration happen every time the RoboRio restarts code after a download or only on power-up?
In fact we're even getting very strange results from 'displacement' as well. Not a continuously increasing value when the robot drives forward but almost a velocity reading. |
|
#3
|
|||
|
|||
|
Re: Navx Labview Issue
Quote:
The estimated displacement values are not accurate enough for tracking robot position to the accuracy typically needed for FRC robotics. There's more information on this at the navX-MXP Frequently Asked Questions page. |
|
#4
|
||||
|
||||
|
Re: Navx Labview Issue
We're now using the Z900_navX_Get_SystemInformation_Status.vi to check for IMU_CAL_STATE_COMPLETE. That works. Initially we still couldn't zero the YAW though until we noticed a strange phenomenon. If we invoke the SET_YAW_ZERO.vi twice in a row the YAW value zeroes perfectly every time
. I have no explanation for that but it appears to be solid. We will do more testing on that tonight. |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|