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?

Re: Boson 640 MIPI M0153: 16-bit Pre-AGC

Hello, I saw this post and I'm in a similar boat where I'm looking at using a boson over mipi. Is there any update that has been done or is planned with supporting 16 bit mipi and possibly 60 hz update (less important but would still be nice)?

@Alex-Kushleyev
I am able to see and detect the ESC with one voxl but on another it seems to not work at all, they are both flashed with the same version and settings (voxl2 SDK 1.4.1) and the only difference is the voxl2, all esc and cables are the same.

voxl2:/usr/share/modalai/voxl-esc-tools$ ./voxl-esc-scan.py
Detected Python version : 3.6.9 (default, Mar 10 2023, 16:46:00)
[GCC 8.4.0]
Found voxl-esc tools bin version: 1.9
VOXL Platform: M0054
Detected RB5 Flight, VOXL2 M0054 or M0104!
INFO: Scanning for ESC firmware: /dev/slpi-uart-2, baud: 2000000
Sending library name request: libslpi_qrb5165_io.so
Sending initialization request
INFO: Scanning for ESC bootloader: /dev/slpi-uart-2, baud: 230400
Updated baud rate to 230400
WARNING: No ESC(s) detected
VOXL Platform: M0054
Detected RB5 Flight, VOXL2 M0054 or M0104!
INFO: Scanning for ESC firmware: /dev/slpi-uart-2, baud: 250000
INFO: Scanning for ESC bootloader: /dev/slpi-uart-2, baud: 230400
Updated baud rate to 230400
WARNING: No ESC(s) detected
VOXL Platform: M0054
Detected RB5 Flight, VOXL2 M0054 or M0104!
INFO: Scanning for ESC firmware: /dev/slpi-uart-2, baud: 921600
INFO: Scanning for ESC bootloader: /dev/slpi-uart-2, baud: 230400
ERROR: voxl_uart_read_bytes: Bus '12' is not initialized
Updated baud rate to 230400
WARNING: No ESC(s) detected
VOXL Platform: M0054
Detected RB5 Flight, VOXL2 M0054 or M0104!
INFO: Scanning for ESC firmware: /dev/slpi-uart-2, baud: 57600
INFO: Scanning for ESC bootloader: /dev/slpi-uart-2, baud: 230400
Updated baud rate to 230400
WARNING: No ESC(s) detected

ERROR: not all ESCs found
voxl2:/usr/share/modalai/voxl-esc-tools$ voxl-esc

What do you want to do?

1. scan 3) spin 5) upload_params
2. detect 4) upgrade_firmware
   #? 2
   enabling bridge
   bridge enabled
   ERROR: voxl_uart_read_bytes: Bus '12' is not initialized
   [ERROR] No ESCs detected
   disabling bridge
   Sending kill slpi command!
   bridge disabled
   EXITING VOXL-ESC WITH ERROR
   voxl2:/usr/share/modalai/voxl-esc-tools$

@Vinny Part of the issue is it doesn't see to be detected/work on boot but when I use the commands it does work, sometimes it doesn't work at all even with the commands but at the moment it doesn't work on boot at all. Is this an issue with the cable do you think? I ask because there will be no difference between the scenarios and trying the same setup (cables and voxl) with a different ESC seems to work so to me it seems like I somehow broke the esc, but I'm not sure how.

Hello,
I have a drone using a 5v VOXL ESC Mini 4-in-1 with Built-in Power Module with the voxl2 and I have run into an issue where after some use the ESC are not detected anymore by the voxl2. Sometimes, the I can run the commands described in https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-esc/-/blob/master/voxl-esc-tools/calibration.md to manually spin but I can no longer fly through QGC and the blue status light does not blink anymore. After some time though I could not even run the commands on the voxl either and I get a notice that no ESC is detected. The blue light still comes on and the voxl is powered through it so power is for sure going through. Anything to try or test to diagnose or get these working? Nothing should have changed in between them working and not working

@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.