application engineer
Hi, it is claims that the angular rate range is +- 400 dps in datasheet. I think the range was 400 dps in default IMU App before you updated to VG_AHRS App, right?
Assuming you check data in 'a1' or 'a2' packet via RS232, could you please switch 'z1' or 's1' packet to see the rate range?
Hi, from your screenshot, we can see "0X55 0X55 0X61 0X31 ... " at the beginning of data, where 0X5555 is the Preamble of packet, 0X6131 is the packet type 'a1'.
Besides, here is a description of 'a1' packet, hope it is helpful for you.
https://openimu.readthedocs.io/en/latest/apps/ahrs.html?highlight=a1#the-definitions-of-the-output-packets-of-the-vg-ahrs-app
Hi, I used 200Hz before and OpenIMU300ZI worked properly at that time.
Please note that if the length of packet is a bit long, you also need to adjust baud rate to 230400 or higher.
Pin 7 of IMU300ZI is SPI/UART Interface selector, could you please check you have selected UART by pin 7 already on your customer board?
Reference: https://openimu.readthedocs.io/en/latest/300ZI/pinout.html
I found the derivation. I have used numerical differential of quaternion as reference to compare the two formula. The one with constraint did give better accuracy when pitch and roll are not close to 0.
Hello,
I think you are right. Just a reminder that the measured velocity in the body frame is no longer [frontVelMean, 0, 0] now. You may also rename Update_PseudoMeasurement() to something else because you are using actual measurements instead of pseudo ones.
Hi, the external crystal frequency is 24.806MHz.
What's is your application with OpenIMU300za?
thanks.
Position and velocity are not required by the AHRS app. By saying AHRS app, we usually mean only attitude is calculated and the heading angle is stabilized by the magnetic heading.
