I have a 2 imx678 hires cameras attached to a voxl 2 mini the stream video using the voxl-camera-server without any problems, however there is a weird color tint on the cameras. Is there any way to adjust to color calibration for the voxl-camera-server? If not is there a way to access the raw8 or raw10 grey video without any image processing done to them?

@tom I thought I did but it wasn't in properly I tested it again and I got sucess.
so this confirms that uart is working correct? and then for using it in my own program I could use the same things I see in the test program with #include <voxl_io.h> and then all the same voxl_uart functions used in the program yeah?
Thanks.

@Moderator Any update on accessing the RAW8 for the hires image sensors?
Also, is there a way to change the exposure and gain manually. In the voxl-camera-server config I have been able to change the setting of ae_mode to off and I've tried using the "voxl-send-command hires0_small_color set_exp_gain 100 200" for example but nothing changes. I also tried setting the ae_mode to lme_msv but changing the settings in the config had no effect of the exposure or gain either, it was acting the same as the off mode. Are these settings available to the hires imx678? If not, is there any way for me to adjust the exposure and gain settings?

@tom Gotcha, I did not realize that and in the version of QGC I was using the motor spin tool was not working. I updated QGC and was able to get them working correctly, thanks for the help.

@constantines

1. I'm pretty sure motor order is correct, what is the best way to check/change this my method so far has been running the spin test command you provide and then switching the wires for where they are plugged in, is there a way in software to change this?
2. Rotation direction is correct
3. The voxl orientation matches the voxl 2 flight deck, with the picture below the front is the voxl side going to the top of the image
   

I have another drone that matched this setup as well that at one point was able to fly and now has a similar issue so I'm trying to figure out why it no longer can fly.

Hello, I have a voxl flight deck 2 with the 4 in 1 esc using the SunnySky V2806 v 650 motors. I've gone through the ESC calibration with props on defined on the git and motors seem to be able to spin up to correct rpm, however when I go to actually fly giving any throttle the drone pitches hard up and attempts to flip.

https://review.px4.io/plot_app?log=20ac3c83-485a-41ce-94a0-cca4886b4724

It seems like 2 of the motors are not reaching the same rpm as the others and I think this may be my issue, but when I run ./voxl-esc-spin.py --id 3 --rpm 4000 --ramp-time 2.0 all motors seem to ramp up and able to hold 4000 rpm fairly constantly so I don't think the esc calibration is the issue. I've also turned the px4 PID down pretty low just to try to get the drone in the air.

There seems to be something I am missing in this setup so I'm trying to get any answers, thanks.

Hello, I am testing the ar0144 camera with the ae_mode set to "lme_msv" and I don't see the "ae_exposure_period" making any signifigant change. I set it to "1.0" then "1.5" and the images look exactly the same, and it seems like there is no different between the "recovery" time when going from dark to light. I'm wondering what this setting does because I believe it works different then what I am assuming.

Hello,

I have been doing alot of test recently with a voxl2 mini and I have come across an issue that I'm hoping I can get some help with. After extreme shock the app proc imu, the one from the voxl-imu-server, the imu becomes extremely saturated and seems to lock at this saturated state. shown in the graph below is the accels and the y reaches 156 m/s2 and never comes back down. This seems to be resolved with a reset of the entire system, so power off power on of the voxl, however that isn't really an option during operation so I'm wondering if there is a way to reset or power cycle only the imu in hopes to correct this without having to shut down the entire system? Any leads on this are helpful.

@tom Thanks for replying, I have actually resolved this already, There was an issue with the power supply and I guess whenever it would get to 12 % it would drop enough power to shut off and I didn't have access to any of the lights so I just didn't realize. After fixing the power supply I was able to complete the flashing process and everything is working properly now.

Hello, I have a voxl2 mini that I am trying to reflash with a new SDK however I'm running into issues. It detects the device and begins the flashing process but it then hangs at
"
Flashing: xbl_a | xbl.elf
-------
"
and never progresses any more from there. All I'm doing is powering it with the fastboot button held and then running install.sh. I'm hoping someone can give me some advice on what I am doing wrong.

Heres the full output after i run install.sh

                                                     ▂▂▂▂▂▂▂▂▂▂▂▂▂          
                                                ▂▄▆▆██▛▀▀▀▀▀▀▀▀▜████▆▆▄▂    

███╗ ███╗ ██████╗ ██████╗ █████╗ ██╗ ▗▆████▀▔ ▔▔▀▀▀▀▚▄
████╗ ████║██╔═══██╗██╔══██╗██╔══██╗██║ ▗▟████▀ ▗██▖ ▐█ ▝▀▆▄▄▄
██╔████╔██║██║ ██║██║ ██║███████║██║ ▟████▀ ▗█▘▝█▖ ▐█ ▜█▀
██║╚██╔╝██║██║ ██║██║ ██║██╔══██║██║ █▌ ▐█▌ ▗█▘ ▝█▖ ▐█ ▐▄
██║ ╚═╝ ██║╚██████╔╝██████╔╝██║ ██║███████╗ ▀████ ▗█▘ ▝█▖ ▐█ ▂▄███
╚═╝ ╚═╝ ╚═════╝ ╚═════╝ ╚═╝ ╚═╝╚══════╝ ▀▀██▄▄ ▂▆███▀
▀▀██▄▄ ▀▀▆▄▄▄▄▆██▀▀▀▘

Running in Interactive mode.

Flashing the following System Image:
Build Name: 1.8.02-M0104-14.1a-perf
Build Date: 2024-11-11
Platform: M0104
System Image Version: 1.8.02

Installing the following version of voxl-suite:
voxl-suite Version: 1.4.0

Would you like to continue with SDK install?

1. Yes
2. No
   #? 1
   [INFO] adb installed
   [INFO] fastboot installed

---- Starting System Image Flash ----
----./flash-system-image.sh ----
Detected OS: Linux

=======================================================================================================
BOARD IN FASTBOOT, CAN'T DETECT HARDWARE VERSION.
Please determine hardware version, -1 (QRB5165M) or -2 (QSM8250)

See docs.modalai.com/m0054-versions for more info.

=======================================================================================================
In order to support all of VOXL's camera configurations, specific drones require differing kernel images.
Please select your drone hardware to proceed with flashing the appropriate kernel image.

PLEASE SELECT WHICH KERNEL TO FLASH

1. M0054-1 -> QRB5165M, Starling (D0005), Sentinel (D0006), FPV (D0008), D0010, PX4 Dev Kit (D0011)
2. M0054-1 -> QRB5165M w/ M0173 Camera Breakout Board, Starling 2 Max (D0012), Starling 2 (D0014)
3. M0054-2 -> QSM8250, Starling (D0005), FPV (D0008)
4. M0054-2 -> QSM8250 w/ M0173 Camera Breakout Board, Starling 2 Max (D0012)
5. M0104-1 -> QRB5165M
6. M0104-1 -> QRB5165M, Stinger (D0013)
7. M0104-2 -> QSM8250
8. M0104-2 -> QSM8250, Stinger (D0013)

Select your choice from above options: 5

Installer Version: 1.0
Image Version: 1.8.02
Board Version: M0104-1

Please power off your VOXL, connect via USB,
then power on VOXL. We will keep searching for
an ADB or Fastboot device over USB
[INFO] Found ADB device
[ERROR] No device found in adb or fastboot
[INFO] Found fastboot device
[WARNING] This system image flash is intended only for the following
platform: VOXL2 Mini (m0104)

      Make sure that the device that will be flashed is correct.
      Flashing a device with an incorrect system image will lead
      the device to be stuck in fastboot.

Would you like to continue with the VOXL2 Mini (m0104) system image flash?

1. Yes
2. No
   #? 1
   [INFO] checking partition system::0xD3B5D7000
   [INFO] checking partition userdata::0x1000000000
   [INFO] checking partition modalai_cal::0x4000000
   [INFO] checking partition modalai_conf::0x4000000
   [INFO] Found correct partitions
   [INFO] Found all required files

Flashing: xbl_config_a | xbl_config.elf

Flashing: xbl_config_b | xbl_config.elf
---
Flashing: xbl_a | xbl.elf
-------

Another thing I've noticed with this particular voxl that I have not noticed with others is the voxl-suite is missing, I'm not sure why or what this means but seems relevant to the state of the device.

                                                     ▂▂▂▂▂▂▂▂▂▂▂▂▂            
                                                ▂▄▆▆██▛▀▀▀▀▀▀▀▀▜████▆▆▄▂      

███╗ ███╗ ██████╗ ██████╗ █████╗ ██╗ ▗▆████▀▔ ▔▔▀▀▀▀▚▄
████╗ ████║██╔═══██╗██╔══██╗██╔══██╗██║ ▗▟████▀ ▗██▖ ▐█ ▝▀▆▄▄▄
██╔████╔██║██║ ██║██║ ██║███████║██║ ▟████▀ ▗█▘▝█▖ ▐█ ▜█▀█▄
██║╚██╔╝██║██║ ██║██║ ██║██╔══██║██║ █▌ ▐█▌ ▗█▘ ▝█▖ ▐█ ▐▄ ▄█
██║ ╚═╝ ██║╚██████╔╝██████╔╝██║ ██║███████╗ ▀████ ▗█▘ ▝█▖ ▐█ ▂▄███▀
╚═╝ ╚═╝ ╚═════╝ ╚═════╝ ╚═╝ ╚═╝╚══════╝ ▀▀██▄▄ ▂▆███▀
▀▀██▄▄ ▀▀▆▄▄▄▄▆██▀▀▀▘

dpkg-query: package 'voxl-suite' is not installed and no information is available
Use dpkg --info (= dpkg-deb --info) to examine archive files,
and dpkg --contents (= dpkg-deb --contents) to list their contents.

system-image: 1.7.8-M0104-14.1a-perf
kernel: #1 SMP PREEMPT Sat May 18 03:34:36 UTC 2024 4.19.125

hw platform: M0104
mach.var: 2.0.0

voxl-suite:

no current network connection

voxl2-mini:/$

Hello, I am pulling images from the voxl-camera-server of a ar0144 camera over the modal pipe and was wonder what was meant by " int64_t timestamp_ns; ///< timestamp in apps-proc clock-monotonic of beginning of exposure", if this is the case if I am looking for the "center of exposure time" does this mean I take the "exposure_ns" and add half of that to the timestamp_ns?

@Vinny I was able to get it in fastboot mode and flash it so things seem to be working now, switching to off and hitting the button solved it.

Thanks for all the help!

@Vinny It wasn't a power issue, I realized one of the boards in the stack wasn't connecting properly, so pretty simple to fix that.

I am still having the issue of actually getting it to work though, all of my attempts to get it into fastboot mode don't do anything and there doesn't seem to be a button on the board I can push and the switch doesn't seem to be helping. There is a button on the 5G Wireless board at the top, but this also does not seem to put it into fastboot mode. I also can't connect to it any other way, like just doing adb shell and no devices show for adb devices nor fastboot devices.