@daniellee This log shows a normal flight happening in altitude hold mode. RC inputs are coming in and motors are spinning. Was there some issue with the flight this log was captured from?

@ralinaresg ,

After discussing this issue with the team, it looks like the ESC has been reworked after the original manufacturing / assembly. Please submit an RMA request and we can figure out the details about what happened and how to proceed.

https://www.modalai.com/pages/rma

Alex

@voxltester Use any port you like. When you connect to voxl-mavlink-server at port 14550 it will remember the ip and port you connected from and maintain a connection with it.

Hello I am in the process of integrating your voxel 2 mini. I need to connect to it wirelessly or wired if i am able to log into mission planner via the ADB connection /USB C port?

J3 - USB3 10-Pin JST
MCBL-00022-2 is recommended.
Example using a wired ethernet adapter connected to J3 (Cable Creation USB to Ethernet)
Example using a wireless ethernet adapter connected to J3 (Alfa Network AWUS036ACS 802.11ac AC600)
Also do you have a pinout for the wiring on a Doodle Labs RM-1700-22M3 ?
Thankyou for your time.

@Jetson-Nano Can you rebuild to add UAVCAN? The code is here: https://github.com/modalai/px4-firmware/tree/v1.14.0-2.0.133-dev

@Mustafa_Cayci You can get the Starling 2 Max with a ToF sensor for depth mapping indoors (The sensors don't really work outdoors). https://www.modalai.com/products/starling-2-max?variant=49129974923568

@WesleyHavocAI I was able to successfully flash 2024-02-09-1.7.4-M0054-2.zip from miscellaneous. I used the image-flash.py script rather than the web gui. I am still interested in knowing if there is a newer image for M0054-2.

@Eric-Katzfey UAVCAN is working in the latest versions, when enabled. And yes I meant heading error, thats my mistake.
The collision prevention is the major issue I am having.
The heading error is in the latest version, and I also came across it in the issues section and it was shown solved, but I did not test it out still with VIO, I was testing with only Optical flow and it was not working.

@tom got it, I think you indirectly answered my question by giving me the last valid configuration. Am I looking in the right place?:

voxl sdk 1.5.0 -> system image 1.8.04 -> recipes-kernel/linux-msm/files/dts/common/m0xxx-modalai-gpio.dtsi :

&soc { voxl_gpio { ... modalai,gpio-init-output-high = <0 1 53 56 57 85 86 87 88 89 124 152 157 159>; modalai,**gpio-init-output-low** = <36 37 **46** 54 55 67 82 83 84 131 153 154 155>; modalai,gpio-init-input = <48 49 50 51 52 110 111 112 113 114>; status = "ok"; }; ... };

So settings for gpio pin 46 on sentinel w/ spektrum receiver should be direction:out, value:0 assuming they aren't overwritten somewhere else.

@astro_phil ,

Which camera connector (J6 or J7) are you using on VOXL2 mini? Also, have you sensormodule (camera driver) to /usr/lib/camera (assuming you are doing a manual configuration). See some details here : https://docs.modalai.com/configure-cameras/#connect-a-new-camera

Since the kernel is reporting that camera probing is failing, this could mean one of several things:

correct sensormodule for the camera and slot id is not present incorrect kernel variant is used (should be 2.0.0) a hardware issue in the interposer / camera

You can also check if the tracking camera works in the upper slot (where you have the IMX214 plugged in right now) and vice versa. Swapping the camera slots would require making sure you have correct mating orientation of the connectors and correct sensormodules available.

I just checked on voxl2 mini, we have the following sensormodules available:

voxl2-mini:/usr/share/modalai/chi-cdk/imx214$ ls com.qti.sensormodule.imx214_0.bin com.qti.sensormodule.imx214_3.bin com.qti.sensormodule.imx214_2.bin com.qti.sensormodule.imx214_4.bin voxl2-mini:/usr/share/modalai/chi-cdk/ov7251$ ls com.qti.sensormodule.ov7251_0.bin com.qti.sensormodule.ov7251_2.bin com.qti.sensormodule.ov7251_4.bin com.qti.sensormodule.ov7251_1.bin com.qti.sensormodule.ov7251_3.bin com.qti.sensormodule.ov7251_5.bin

So you would not be able to get this combo to work on J6 (slot ids 0 and 1) because the imx214 sensormodule for slot 1 is missing (we did not add it by mistake), but J7 should work (slots 2 and 3). If you put IMX214 into lower slot, and tracking camera in upper slot, then you could use J6 : imx214 : slot 0, ov7251 : slot 1.

Additionally, make sure that you are using the correct kernel for voxl2 mini (it should be 2.0.0, not 2.0.2 when you are using the non coax cameras / interposers). you can check the kernel version using voxl-version and look at the top of the output, under mach. var (machine variant), should be 2.0.0. if not, re-install SDK and select the correct kernel variant during install.

Alex

@gerard I also just remembered we had a stint of bad MCBL-00010's a few months ago...
We have since cleared that up, but there is no telling how long ago you may have ordered that cable...
Please see this thread for guidance and if you do think your MCBL-00010 is at fault, we will replace your M0048, just reference both threads in your RMA (this one and this one -->) https://forum.modalai.com/topic/4632/flight-core-2-firmware-update-through-qgc?_=1781284416780

@Eric-Katzfey We reinstalled the QGC in a new laptop and it is working fine now.