@RoyAzriel Can you just try a fresh SDK install and see if that helps?

@Alex-Kushleyev

I also replaced the voxl-mini but i get the same error on J7

[ 6.548108] CAM_ERR: CAM-CCI: cam_cci_irq: 264 Base: pK-error, M1_Q1 NACK ERROR: 0x40000000 [ 6.548134] CAM_ERR: CAM-CCI: cam_cci_read: 1329 ERROR with Slave 0x20: [ 6.548138] CAM_ERR: CAM-CCI: cam_cci_read_bytes: 1613 failed to read rc:-22 [ 6.548141] CAM_ERR: CAM-SENSOR: cam_cci_i2c_read: 35 rc = -22 [ 6.548145] CAM_WARN: CAM-SENSOR: cam_sensor_match_id: 707 read id: 0x0 expected id 0x214:

the imx214 is not working on J7 upper. I doubt that both VOXl2-mini have the same hardware issues.

The Doodle Labs pinout could be inferred from this cable mcbl-00085

@Alex-Kushleyev

Thank you. We will do, but for future reference:

@Alex-Kushleyev said in Burnt board components:

what type of vehicle was the ESC a part of?

Singer Vision FPV 3.5"

@Alex-Kushleyev said in Burnt board components:

what was the behavior of the motor that was not functioning properly?

Not operating a full power with intermittent operation

@Alex-Kushleyev said in Burnt board components:

did the whole ESC stop working or only one channel, which was originally struggling?

Only one channel

@Alex-Kushleyev said in Burnt board components:

did you notice the burned component when the ESC arrived or did it burn after arrival?

We didn't noticed or inspected it.

@Alex-Kushleyev said in Burnt board components:

was the black paint already on the ESC when you received it?

We didn't notice or checked

Regarding the feature track tab, I recommend upgrading to the latest available SDK, features should show on voxl-portal.

The correct overlay is under VIO indeed

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

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

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