IMU383 SERIES USER MANUAL

1.On page 13 it is stated that the product ID is 0x3813, and on page 19 it is stated that the product ID is 0x3830, which one is correct?
2.The register addresses of xyz_rate and xyz_acc are not stated in the manual. Where should I read their values?

we found and confirmed they are need to be updated, we will update it later.
pls use user manual in Aceinna link:
https://www.aceinna.com/inertial-systems/IMU383ZA
thanks a lot for your feedback.

@cek said in IMU383 SERIES USER MANUAL:

we found and confirmed they are need to be updated, we will update it later.
pls use user manual in Aceinna link:

I found in the link you provided that the product ID is still inconsistent.Can you tell me which one is correct?
And, can you tell me which register xyz_rate and xyz_acc can be read in polling mode?

1. right value is 0x3813.
   2 .0x4/6/8 is xyz_rate, 0xA/C/E is xyz_accel

3. .0x4/6/8 is xyz_rate, 0xA/C/E is xyz_accel. both register could be read in polling mode.

@cek But 0x04-19 in the manual are reserved，Does this mean I can't read the corresponding value by reading register 0x04-0E？
And the same program reads 0x04-0E of imu381 is correct, but it does not work on imu383, why is this?

you can try to read 0x0E, what did you get in 381 and 383? both should be 2 bytes feedback, LSB.

@cek The current situation is like this, the xyz-rate and xyz-acc of imu383 cannot be read all at once.
The same reading code, I can only get 04, 08, 0C or 06, 0A, 0E,May I ask where is the problem?

I think you want to do is "Multiple Register Read via Polled-Mode", like below pic:

if yes, it is different with 381.
Now not supported in UM(pls check the time sequence in UM, sure not totally with 381), so, I hope you can try to do burst read 0x3E in 383, like pic in 383 manual:

thanks a lot for your under standing and pls follow up the time sequence UM of 383.

@cek I only use the burst mode to read, but the data is incorrect. My imu383 is on the table and does not move, but the data display is not close to zero. But when I only read in polling mode, the data is correct. Did I overlook something?