@Alex-Kushleyev I verified that I used the correct drivers and had already updated maxRAWSizes on /vendor/etc/camera/camxoverridesettings.txt. I just went through the updated EIS docs and I am still seeing the same errors. Let me know if there's anything else I can check!

After upgrading to sdk 1.6.0 things are working well and the transform is incorporated correctly. Thanks for your help! If you know how I can get it working on sdk 1.5.0 I'd still be interested in knowing how.

@Alex-Kushleyev Thanks! After upgrading libmodal-pipe (which also requires a voxl-cpu-manager upgrade), I was able to install and run voxl-camera server, as well as the latest version of voxl-portal from the eis-integration branch.

I followed the instructions here, and set up eis.

when I run voxl-camera-server, I'm seeing this output and I cannot see any camera stream on voxl-portal. Let me know if you recognize this issue and know how to fix it. Thanks!

@Alex-Kushleyev Thanks Alex! I tried testing this out, but it looks like it depends on a newer version of libmodal-pipe.

voxl2-mini (M0104):/data/voxl-suite-offline-packages$ dpkg -i --force downgrade --force-depends voxl-camera-server_2.2.16_arm64.deb
(Reading database ... 102703 files and directories currently installed.)
Preparing to unpack voxl-camera-server_2.2.16_arm64.deb ...
Unpacking voxl-camera-server (2.2.16) over (2.2.4) ...
dpkg: voxl-camera-server: dependency problems, but configuring anyway as you requested:
 voxl-camera-server depends on libmodal-pipe (>= 2.14.0); however:
  Version of libmodal-pipe on system is 2.13.2.

Setting up voxl-camera-server (2.2.16) ...
voxl2-mini (M0104):/data/voxl-suite-offline-packages$ voxl-camera-server
voxl-camera-server: symbol lookup error: voxl-camera-server: undefined symbol: pipe_validate_cpu_stats2_t

would you recommend upgrading the SDK to 1.6.0, or is there another way to get this working? I would prefer not to upgrade the SDK.

Thanks for your help!

@Alex-Kushleyev yes, that's correct!

@Alex-Kushleyev I'm building from the eis branch not the official release. Thanks!

(Note: The images I included in my post are labeled backwards. first image is "eis_mode": "horizon-level" and the second image is "eis_mode": "full-follow")

Hi! I'm noticing some difference in functionality when I switch eis_mode from horizon-level to full-follow.

I built voxl-camera-server off the eis branch and followed the instructions. everything seems to be working correctly including stabilization other than the final output rotation that I am looking for.

My imu_apps to hires extrinsics are set up correctly and I want to apply this additional transform to the output:

 {
        "parent": "hires",
        "child":  "hires_eis",
        "T_child_wrt_parent": [0.066, 0.009, -0.012],
        "RPY_parent_to_child":    [0, 0, -90]
    }

I'm noticing that if I set "eis_mode": "full-follow" the transform isnt applied but if i set "eis_mode": "horizon-level" it rotates the output window as expected. Here's what I see on voxl-portal when I switch eis_mode and leave the extrinsics file untouched.

"eis_mode": "full-follow":

"eis_mode": "horizon-level":

Hoping to find a way to get the output rotation working in full-follow mode. Thanks!

I’m having trouble recovering a couple voxl2 minis (M0104). Here’s what I observed and tried so far:

1. The minis were working normally on a reliable power supply.
2. Minor issues occurred (in one case voxl-camera-server segfaulted, in another I tried a custom binary). This may not be relevant.
3. Units continued to boot normally for 3–4 power cycles.
4. On the 4th or 5th restart, they stopped booting:
   • LEDs show D1 + DS2 solid immediately.
   • Sometimes they briefly show D1 + D2 solid before going back to D1 + DS2.
   • Tried adb in those rare instances where D1 + D2 were on, didn't work
5. Tried powering with nothing connected, same result.
6. Tried unbricking procedure:
   • Board recognized as a QDL device (web UI and lsusb both show the QDL device).
   • Attempting “Flash Flat Build” with VOXL2 QDL Image 14.1a_1.7.8 always times out.
   • I couldn’t find a voxl2 mini specific flat build, and in the latest voxl2 mini SDK there's no ufs directory as described here

My questions:

• Is there a separate QDL flat build for the voxl2 mini (M0104), or should the standard voxl 2 flat builds work?
• Since I’d prefer to recover data if possible, is there any way to get the board into fastboot or ADB without reflashing?
• Does the LED pattern (D1+DS2 solid, sometimes briefly D1+D2) indicate anything specific about the boot state?

Any help would be greatly appreciated, thank you!

@Alex-Kushleyev The drivers worked, and the EIS as expected isn't tuned well. The MISP brightness looks alright outdoors, but indoors its very low. Increasing exposure_max_us helps but adds blur. Not sure if that's to be expected with this sensor, since it isn't as good in low-light conditions as the IMX412. Let me know if there's anything I can tune in the conf file to help with the brightness, and EIS output. Thanks!

@Alex-Kushleyev This worked! Thank you