The address remap works on VOXL2 for two AR0144 with the same SID on the the same CCI bus. Need a custom kernel.
VOXL2 Kernel: https://storage.googleapis.com/modalai_public/temp/ar0144/qti-ubuntu-robotics-image-m0054-boot-1.0.1-ar0144-remap.img (variant 1.0.1, built off 1. 8.10. (https://docs.modalai.com/voxl2-voxl2-mini-system-image/#1810)
Latest AR0144_V2 drivers. 40 variants. (pdf doc inside) : https://storage.googleapis.com/modalai_public/temp/ar0144/ar0144_v2_qrb5165_20261115.zip . The doc has explanation for all sensormodules and additional details.
M0173 R5 : install 0 ohm to enable FSYNC in camera 1 (J4)
[image: 1794804520158-0047a3af-58cd-49db-9809-34b7cb7ffb25-image.jpeg]
Quick install guide:
#all unsynced, 0x20 SID in slot 1
adb push ar0144/com.qti.sensormodule.ar0144_v2_combo_nosync_0.bin /usr/lib/camera/
adb push ar0144/com.qti.sensormodule.ar0144_v2_combo_nosync_6.bin /usr/lib/camera/
adb push ar0144/com.qti.sensormodule.ar0144_v2_0x20_1.bin /usr/lib/camera/
adb push ar0144/com.qti.sensormodule.ar0144_v2_2.bin /usr/lib/camera/
adb push ar0144/com.qti.sensormodule.ar0144_v2_5.bin /usr/lib/camera/
adb push boson/com.qti.sensormodule.boson_4.bin /usr/lib/camera/
#all synced (M0173 + M0181 default with R5 fix), 0x20 SID in slot 1
adb push ar0144/com.qti.sensormodule.ar0144_v2_combo_0.bin /usr/lib/camera/
adb push ar0144/com.qti.sensormodule.ar0144_v2_combo_6.bin /usr/lib/camera/
adb push ar0144/com.qti.sensormodule.ar0144_v2_fsin_0x20_1.bin /usr/lib/camera/
adb push ar0144/com.qti.sensormodule.ar0144_v2_fsin_2.bin /usr/lib/camera/
adb push ar0144/com.qti.sensormodule.ar0144_v2_fsin_5.bin /usr/lib/camera/
adb push boson/com.qti.sensormodule.boson_4.bin /usr/lib/camera/
#all sync'ed except for slot 1 (M0173 + M0181 default without R5 fix), 0x20 SID in slot 1
adb push ar0144/com.qti.sensormodule.ar0144_v2_combo_0.bin /usr/lib/camera/
adb push ar0144/com.qti.sensormodule.ar0144_v2_combo_6.bin /usr/lib/camera/
adb push ar0144/com.qti.sensormodule.ar0144_v2_0x20_1.bin /usr/lib/camera/
adb push ar0144/com.qti.sensormodule.ar0144_v2_fsin_2.bin /usr/lib/camera/
adb push ar0144/com.qti.sensormodule.ar0144_v2_fsin_5.bin /usr/lib/camera/
adb push boson/com.qti.sensormodule.boson_4.bin /usr/lib/camera/
#all unsynced, all same SID, use SID remap (with new kernel)
adb push ar0144/com.qti.sensormodule.ar0144_v2_combo_remap_0.bin /usr/lib/camera/
adb push ar0144/com.qti.sensormodule.ar0144_v2_combo_6.bin /usr/lib/camera/
adb push ar0144/com.qti.sensormodule.ar0144_v2_fsin_remap_1.bin /usr/lib/camera/
adb push ar0144/com.qti.sensormodule.ar0144_v2_fsin_2.bin /usr/lib/camera/
adb push ar0144/com.qti.sensormodule.ar0144_v2_fsin_5.bin /usr/lib/camera/
adb push boson/com.qti.sensormodule.boson_4.bin /usr/lib/camera/
# Camera Server Config
## without boson
camera-server-config-helper ar0144_0:ar0144:0 ar0144_1:ar0144:1 ar0144_2:ar0144:2 ar0144_3:ar0144:3 ar0144_4:ar0144:4
## with boson
camera-server-config-helper ar0144_0:ar0144:0 ar0144_1:ar0144:1 ar0144_2:ar0144:2 ar0144_3:ar0144:4 ar0144_4:ar0144:5 boson:boson-fpv:3
## configure gpio fsync (set manually or run below):
sed -E -i '/"fsync_en":/c\ "fsync_en": true,' /etc/modalai/voxl-camera-server.conf
sed -E -i '/"fsync_gpio":/c\ "fsync_gpio": 109,' /etc/modalai/voxl-camera-server.conf
# start camera server and inspect (dont inspect all possible streams, as it will load up the system
voxl-camera-server
voxl-inspect-cam ar0144_0 ar0144_1 ar0144_2 ar0144_3 ar0144_4 boson320
Please note that the camera server replaces the AR0144 timestamps with the closest fsync time if fsync_en is set to true, even if the unsync'ed AR0144 sensormodule is used.
Another note, if you are using voxl-portal in multi view, only 6 connections are supported by Chrome browser (may be others), so if you open 6 camera views at the same time, the other functionality in voxl-portal may stop working (so you can limit to 5 streams in multi-view).
when you use the SID remap functionality, you can check dmesg, look for:
[ 4733.137530] CAM_INFO: CAM-SENSOR: cam_sensor_addr_move: 477 slot 1: moved sensor 0x356 from 0x30 to 0x32
[ 4733.137535] CAM_INFO: CAM-SENSOR: cam_sensor_driver_cmd: 1145 CAM_ACQUIRE_DEV Success, sensor_id:0x356,sensor_slave_addr:0x32
[ 4733.137602] CAM_INFO: CAM-SENSOR: cam_sensor_addr_drop_soft_reset: 501 slot 1: dropped soft reset 0x301a=0x959 to keep address 0x32
...
[ 4733.457870] CAM_INFO: CAM-SENSOR: cam_sensor_addr_move: 477 slot 6: moved sensor 0x356 from 0x30 to 0x22
[ 4733.457876] CAM_INFO: CAM-SENSOR: cam_sensor_driver_cmd: 1145 CAM_ACQUIRE_DEV Success, sensor_id:0x356,sensor_slave_addr:0x22
[ 4733.457937] CAM_INFO: CAM-SENSOR: cam_sensor_addr_drop_soft_reset: 501 slot 6: dropped soft reset 0x301a=0x959 to keep address 0x22
Please test it out and let me know how it goes.. I suggest testing one change at a time. I suggest testing the latest voxl-camera-server from dev branch, even if you are on older SDK. May need to update several packages. if you just install via apt (from dev), it will update automatically:
change apt sources to dev : /etc/apt/sources.list.d/modalai.list : deb [trusted=yes] http://voxl-packages.modalai.com/ ./dists/qrb5165/dev/binary-arm64/
apt update
apt install voxl-camera-server
if you view the ar0144_*_misp_grey streams, they are with Lens Shading Correction applied. We also have improved Auto Exposure coming shortly for AR0144.
I don't think i forgot anything...