@Alex-Kushleyev Ahh I see. I was just using RB5 as an abbreviation for qrb5165.
It is a standalone module, but since the hadron just passes through the OV64B MIPI/I2C its quite similar.

Qualcomm advises using the SSC QUPs to interface with IMUs for EIS (I'm guessing for lower latency). Have you seen any differences in latency when comparing the SSC connected 42688 onboard the voxl2 vs the one connected to the generic QUP? Additionally, are you utilizing the 42688 interrupts to synchronize the data with the frames from the camera?

@Alex-Kushleyev Sounds like we are pursuing the same sort of hardware setup. We have been using the SPI port connected to a 42688 IMU mounted directly on the rear of an OV64B sensor.
If you aren't targeting VOXL2/VOXL2 mini (both RB5 based), what hardware are you targeting?

@Alex-Kushleyev So this is a custom implementation, not using any of Qualcomm's built in tools? If so how are you planning on implementing the RSC? Reading through some of the QC documentation, it seems like the supported QC EIS versions (1.0, 2.6) for the RB5 only correct rolling shutter for linear motion on a per frame basis. That doesn't help much on a high vibration platform where the intra-frame motion is non-linear.

Are you planning on implementing X and Y rolling shutter corrections on a per line basis? That would be sweet.

I'm looking to use this on a custom quadcopter that has pretty poor vibration isolation. Eager to see your results so far with the EIS.

@Alex-Kushleyev Looking forward to trying this out. A couple questions.

1. Which version of Qualcomm's EIS is this using? 1.0, 2.6, or 3.0?
2. What's the ETA for getting RSC implemented?