@tom Thank you for the info. We have custom drone designed with Carbon fiber chamber inside which voxl2 resides over a dampner platform and we have camera bay towards front of the UAV which has CSI connection with VOXL2. We do not have fan over VOXL2 but we have kept fan towards backside of this carbon fiber chamber to act as exhaust but I guess it isnt working out well to cooldown CPU.

@wilkinsaf Thanks for the response, I will see if the superiors are interested. Just hoping for a bit more direction to evaluate ourselves first

@relevinsky You're right, we are going through an overhaul of the docs at the moment, here's an archived link: https://docs.modalai.com/voxl-logger-0_9/

@Mastermind Okay, interesting. Let us know if you figure out the root cause. Thanks!

@Chad-Sweet You are correct. Swapped the IMX214 for a different one and it worked. Thank you for the help!

@Jyotish-Kumar There could've been an ESD issue induced by not having the board on an ESD mat or not using proper ESD protection, check out https://www.modalai.com/pages/rma

@Anubhav Great!

@Hersch-Nathan A quick google gave me: sudo apt update sudo apt install python3-opencv

@Vinny Thanks! I will have to get one of these boards and then see how we might do the integration. This might require a company like ConnectTech

@wilkinsaf Thanks for the feedback

@tom Thank you so much for you help! I got my code to deploy to the voxl! Now on to bug fixing!

Found the offset its gpiochip1100 so for gpio 12 echo 1112 > /sys/class/gpio/export will enable gpio 12

@Chad-Sweet - I have the same issue. How to enable the 4K resolution for IMX412 that we bought for $349 USD from you?

@황인호 It isn't required to use voxl-modem to interact with the modems if you'd like to do a custom config. In your case, I'd recommend using voxl-configure-modem with the quectel option to handle Quectel bringup and then creating a custom script / service file (or modifying the existing one) to handle doodle bringup. Although doodle bringup is very basic, if you follow the code path here in the startup script: https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-modem/-/blob/master/scripts/voxl-modem-start#L99 it monitors the eth0 network interface and if the IP address isn't what is specified in the config file then it assigns said IP address. This could be broken out into a different script

@I_Dwyer I have been down the rabbit hole here. It seems that qualcomm has not used any of the standard network management tools like Netplan. They use a hybrid of Systemd-Networkd and a wide range of complex scripts to manage all the interfaces. None of the scripts are standard. I am at the point of possibly stripping all of that out, and replacing it with either Ifupdown or Netplan and creating a firmware build that works better for our use case. There are a number of problems with the older Qualcomm network scripts, such as the DHCP management you are encountering. For example I have noticed that if WWAN0 has an IP, then WLAN0 will NOT get an IP from the DHCP server, even thought the wifi is connected to the local AP! To get around that I added an ifconfig statement issuing a static IP to wlan0 every time the drone boots, but this is a hacky solution. Would like to see ModalAI replace the entire Network Management stack with something better and easier to maintain.

@afdrus the relocalization is external to the VIO EKF. You can trace this code path here: https://gitlab.com/voxl-public/voxl-sdk/services/voxl-vision-hub/-/blob/master/src/tag_manager.c#L110

@tom Yes, thanks! That is a good idea. I will do that. I was looking at the release page of the system image and saw this line with 1.5.3 internal release: HLOS Added service file that changes SLPI restart level to avoid board crash when SLPI crashes What is SLPI and could you describe a little bit more what kind of issues you saw when SLPI crashed? I also sometimes saw px4io io_reg_get(4,0,15): data error -5 in the logging so maybe that could be related?

@Chad-Sweet Thank you for getting back to me. The radio we are leaning to use has an SPI interface. However, I am not opposed to switching radios if there is an easier to use I/O on the VOXL. We are leaning to using Adafruit RFM95W based on the SX1276 LoRa module with SPI interface.

@Chad-Sweet Thanks for reply, I am just triggering via python subprocess voxl-send-command hires_snapshot snapshot able to get snapshots. will try to look into mavsdk also.