SmartMotion® MEMS Motion Sensors

phpbb forum ID
13263
By naylandglaznie… , 4 June 2024

Hi,

I'm trying to choose between ICM-42670-P and ICM-42688-V for absolute orientation.

ICM-42670-P - Smart motion library
ICM-42688-V - the advanced sensor fusion library (ASF)

ON the TDK page it states that "the advanced sensor fusion library (ASF) motion sensor algorithm provides highly accurate sensor fusion output (less than 1 degree on yaw, pitch, roll)". "It provides 6 axis and 9 axis sensor fusion outputs such as quaternoins, yaw, pitch and roll"

By kjseirfitness , 22 May 2024

I am following https://github.com/tdk-invn-oss/motion.arduino.ICM42670P driver example to implement my own version for ICM42670P on my psoc6.

I am able to read/write and see interrupts being triggered. But in the example driver the callback being registered for when i read data from fifo using "inv_imu_get_data_from_fifo(&icm_driver);" is never being triggered.

By mecharrihiteccomar , 20 May 2024

We are using the ICM-20689, for vibration measurements purposes.
We are using the low pass filter in 420Hz and then the data rate is 1kHz. We take this data and made a FFT to inform the frequency and amplitud of the vibration.
Now we detect the we have an aliased frequencies. We detect the frequencies above 500 Hz appears aliased, eg. the 510Hz appear as 490Hz with an attenuation, but if we increment the vibration frequency the measured amplitude increments. We are thinking there is an digital filter response.

By kjseirfitness , 15 May 2024

Hi

I am changing from ICM20648 to ICM42670P, and hence i have bought DK-42670-P and I am struggling to directly connect the spi interface to my board? I solely want to use U1 (ICM42670P) on the development kit, is that possible? and if so how should i wire it up?

Currently i have connected my spi interface to J4 corresponding MISO, MOSI, CS and SCLK lines (pin 1,2,3,4) and a GND connected to pin 7 on J4. But I am unsure how/where I should connect my VDD (3.3V)

Thanks

By jiangzihaoaero… , 13 May 2024

Hello, everyone! I've been programming with an ICM-42688-P for its data of acceleration and angular velocity, and now something wrong happens. The output of gyroscope vibrated between -255 to +255 (scale of 2000, 8000 HZ sampling) while it stayed stationary. Sometimes the output data comes back to near 0, but it will jump to ±255 in just a few epochs. Meanwhile, the 3-axis gravity output of accelerometer in rest condition reached 9.87 m/s2, appearing a giant constant zero bias.
How can I deal with these problems? Hope for help!

By tbaumannmgiede , 7 May 2024

Hi@all,

we are currently implementing the ICM20948 in our application. We are using the DMP and so far everything is working fine. However, we are not able to restore the acceleration, gyro and compass bias values. We are able to read the values and write them to the registers mentioned in the application note, however the icm20948 does not seem to care about the written values and always insists of performing a full auto calibration cycle. Therefore we have to turn the device around all axis a few times until all accuracy values go to the value of 3.

By kjseirfitness , 5 May 2024

I just bought a DK-42670-P, installed SmartMotion 4.2.15. and when I start MotionLink and
1) Click "Select and config"
2) Choose ICM42670-P (Leave rest for default)
3) Click Flash MCU --> I get "Please check troubleshooting page for Flash Atmel

I use windows 10, and have both USB connected and J2 shorting 1-2

Any suggestions?

By davidthomas102… , 3 May 2024

Hi team,
I have collected a spatial audio head tracking log in smartbug2.0,also I have applied set reference horizontal and mirror during this log. I have seen position, Raw angles, offset values in smartbug2.0 UI. My observation is that offset value not reflected in log. Also that data seems like normal fusion. Could you please clarify difference between sensor fusion log and the spatial audio head tracking log?.

By neerajdhekaleg… , 2 May 2024

hello All,

I am trying to set MPU 9250 into low power accel only mode. But It seems that After and before setting into Accelerometer only mode data is different. and I guess below statement is culprit:
IP_nrf_drv_twi_i2c_write_8bit(address,MPU9250_REG_PWR_MGMT1,0x29);

Hex values of AccelX, AccelY and AccelZ
Before Accel mode only: (Active Mode)
0 1B 0 26 7 E4

After setting in Accel mode only :
FD BB 2 8F 7 1A

===============================

Before Accel mode only: (Active Mode)
7 F6 0 1 FD 3