You may also be able to resolve your issue by switching to voxl-cross:4.0 docker image, which was recently released.
ModalAI Team
-
RE: Request for access to Qualcomm-specific libgbm package for VOXL 2 cross-compile
-
RE: query on wifi adapter
@shivam-rana , you can try to plug your USB adapter into VOXL2's USB expansion board and check
dmesg
to see if awlan
adapter is detected. If you don't see anything related to wlan or ethernet adapter being connected, then your adapter is not supported. Adding support for 3rd party wifi adapters to VOXL2's kernel would require expert knowledge and experience in building linux kernel modules.Alex
-
RE: Request for access to Qualcomm-specific libgbm package for VOXL 2 cross-compile
You can use the following trick on VOXL2 to find which package the library belongs to and then build the deb from the installed package. In this case the library is in a proprietary package qti-gbm, which you can easily re-create for use in your docker container. This is related to the following documentation page which describes how to run OpenCL inside a docker container : https://docs.modalai.com/voxl-2-opencl-in-docker/
voxl2-mini:~$ dpkg -S /usr/lib/libgbm.so qti-gbm: /usr/lib/libgbm.so apt install dpkg-repack voxl2-mini:~$ dpkg-repack qti-gbm dpkg-repack: warning: unknown information field 'Oe' in input data in entry in dpkg's status file dpkg-repack: warning: unknown information field 'Packagearch' in input data in entry in dpkg's status file dpkg-deb: building package 'qti-gbm' in './qti-gbm_18.0.0-rc5_arm64.deb'.
-
RE: VOXL2 didn't detect IMX412 Camera
Hi @ysc , please see the following documentation pages:
https://docs.modalai.com/debugging-camera-issues/
https://docs.modalai.com/configure-cameras/#connect-a-new-cameraYour VOXL2 SW is likely set up for different camera configuration and you have a non-standard single camera setup (your IMX412 is connected to J7L, which is camera slot 2).
Considering that
voxl-camera-server -l
is already detecting your camera, you can confirm that it is IMX412 based on the sensor ID (also in docs above). The i2c read errors are coming from trying to detect cameras which are not physically connected (0x356 is the WHOAMI register value of AR0144 camera, which you do not have connected to your voxl2).If you look in your
/usr/lib/camera/
, you should only have an imx412 sensormodule with slot 2 (com.qti.sensormodule.imx412*_2.bin) and if you don't want to see the i2c probe errors, you can remove other sensormodules from that directory (however they should not hurt, since you are already detecting your IMX412 camera, it seems).You also need to take a look at your
/etc/modalai/voxl-camera-server.conf
and confirm it is correctly set up for a single hires imx412 camera. Then runvoxl-camera-server
in foreground to see any error messages.Alex
-
RE: ESC lights turn off when plugged into voxl2
@brendan424 , please check the following Q/A and let me know what you find about your LED behavior. Please note that after the initial few flashes, the blue LEDs on the ESC turn off until the flight controller (VOXL2) starts communicating with the ESC. Therefore, I do not fully understand your statement " turns on with lights when connected to battery power, but when I plug in the voxl esc cable, lights shut off". Are you able to make a video or describe more specifically what LED behavior is before you connect your cable to VOXL2?
https://docs.modalai.com/voxl-escs/faq/#q-what-is-the-behavior-of-the-four-blue-on-board-leds
https://docs.modalai.com/voxl-escs/faq/#unboxing-and-testing-new-standalone-escAlso, what cable are you using to connect between VOXL2 and the ESC (what is the cable part number, which should be marked on the cable)? Where on VOXL2 are you connecting the cable? Does the same cable work with another ESC? How do you test?
Alex
-
RE: VOXL2 troubleshooting
@claw That is definitely not the expected behavior, I recommend going through the RMA process
-
RE: VOXL2 troubleshooting
@claw I would try installing the SDK with
./install.sh -w
to wipe all partitions and start fresh.If that doesn't work it may be worth submitting an RMA: https://www.modalai.com/pages/rma
-
RE: Follow up the MAVLink custom port to GCS
@will-huang-oksi That post also refers to using mavlink router. Have you tried that?
-
RE: VOXL2 troubleshooting
@claw Are you running Ubuntu natively? If so, what version?