2026-06-02 9:45 AM
Hello,
We are evaluating the LSM6DSV16BX and LSM6DSV16X for a wearable device attached to the neck for vibration sensing and frequency analysis.
After reviewing the datasheets and application notes, we would appreciate clarification on the following points.
Channel architecture comparison
Could you clarify the relationship between the accelerometer channels in LSM6DSV16BX and LSM6DSV16X?
Specifically:
Is Channel 1 of the LSM6DSV16BX identical to Channel 1 of the LSM6DSV16X in terms of sensing path, filtering, bandwidth, and performance?
Are there any differences in the accelerometer signal chain, filtering stages, ODR limitations, or internal processing between these two devices for Channel 1 operation?
If configured identically, should we expect equivalent vibration measurement performance from LSM6DSV16BX Channel 1 and LSM6DSV16X Channel 1?
Channel 2 characteristics of LSM6DSV16BX
The main reason we are considering the LSM6DSV16BX is its dedicated audio / bone-conduction channel.
Could you explain the practical differences between:
LSM6DSV16BX Channel 2 (audio accelerometer path)
LSM6DSV16BX Channel 1 (standard UI accelerometer path)
LSM6DSV16X Channel 1
In particular, we would like to understand:
Differences in bandwidth
Differences in filtering
Differences in latency
Differences in frequency response
Differences in vibration sensing performance
TDM output configuration
If we decide to acquire vibration data through the TDM interface of the LSM6DSV16BX:
Which registers must be configured to enable the TDM output path?
Which registers select the accelerometer source routed to TDM?
Which registers control slot mapping, output format, clocking, and synchronization?
Is there a recommended register configuration example for vibration sensing or bone-conduction applications?
Reference design or example firmware
Do you have any reference firmware, example register configuration, application note, or evaluation project demonstrating the use of the LSM6DSV16BX audio accelerometer channel with TDM output?
Thank you for your support.
We’re moving the ST Community to a new platform to give you a better and more reliable community experience.