Hello,
We were working on an AI project using VOXL2, unfortunately our model was too heavy for the board it seems. While browsing through the docs for some extra horsepower, we found out that VOXL 2 supports Mythics M1076 Add-On card (ref. Page 2 Product brief + system arch. doc of voxl2 https://cdn.shopify.com/s/files/1/0101/1977/4259/files/VOXL_2_Product_Brief_10.pdf?v=1650857561 ).

I was looking for instructions on how to incoorperate Mythic M1076 to our Voxl2 but unable to find any guidelines related to it. Any help regarding this will be much appreciated.
@Vinny I saw one previous post from you in another thread and was wondering if there had been any updates on supporting Mythic M1076.

Thank you.

@Vinny
Thank you so much for your highly informative reply. This was very helpful.
I have tried the tests that you suggested, and unfortunately it looks like there is some problem with the protection diode.
The diode is measuring ~0.5Volts in both forward and backward direction and the resistance is measured in the ~1.5Kohm range. So looks like something is still wrong.
I think we will continue with the RMA and request you guys to take a look at the board.
Thanks a lot for your help.

@Vinny Great!
So happy to hear about that. Looking forwards to its availability on store soon.

Warm regards,
Jyothish.

Hello,
Our VOXL 2 was connected to our drone. The drone had been functional for long lime and was being used for development on our end. Suddenly, VOXL 2 was not turning on. We observe that connecting the VOXL to power module, the light near the power connector on VOXL just blinks once in red and none of the other lights are on. We also observe slight heat coming from near where the power module connects to the VOXL if we keep it connected for some time (~20 seconds). The temperature is not too hot. The diode near the power module connector seems to be shorted when inspecting with multi-meter.

We have checked with different PowerModuleV3 and have tried changing the wall adapter also.
This happened after the external ESC malfunctioned, overheated and got damaged due to unknown causes. ESC failing has happened to us in the past but it affecting the VOXL is not understood. The power distribution is as shown in the picture, where pass through from the power module is connected to the ESC.

We went ahead with raising an RMA request and while we were in the process of shipping the VOXL to Modal AI for RMA, it started working without any repairs.
We observe normal operating behavior while testing subsequently. So, we are unsure if we should proceed to ship it despite the problem now being resolved.
Requesting you to kindly advice regarding the further steps, considering that the VOXL has to be used in our drone.

Thank you for your inputs.

@tom The usb cables I am using are good quality Type C to Type A cables.
I have tried changing the USB cable to another one. I have also tried using another Power module. Currently my Voxl doesn't have any addon boards connected to it. Just the Voxl2, Power module and USB cable.

Thank you for your reply. Could something else be wrong here?

Yours sincerely,
Jyothish.

@tom Hi Tom, Thank you for your reply.
No luck. I have tried to put it into fastboot mode as advised by you, still computer is not detecting any new usb devices. fastboot devices still shows nothing. same with ```
adb devices

Hello, Greetings for the day.
My VOXL 2, which was earlier accessible through ssh. Didn't connect to network after reboot this time.
Upon inspection, the device is not appearing in ADB Devices either.
Trying to put the device into Fastboot mode is not successful either. When holding the SW1 for extended time, every 15 seconds the led blinks twice, but the device is never put into fastboot mode.
All indicator LEDs on the voxl indicate a normal boot, picture of the current state of LEDs is attached below:

Output of lsusb doesn't recognize voxl as connected, the output is attached for reference:

kyouma@Amadeus:~$ lsusb
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 003: ID 0408:5365 Quanta Computer, Inc. HP TrueVision HD Camera
Bus 003 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0bda:2852 Realtek Semiconductor Corp. Bluetooth Radio
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

When trying to put the board in QDL mode it does get recognized in the system as follows:

kyouma@Amadeus:~$ lsusb
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 003: ID 0408:5365 Quanta Computer, Inc. HP TrueVision HD Camera
Bus 003 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 004: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0bda:2852 Realtek Semiconductor Corp. Bluetooth Radio
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

I have followed the VOXL 2 QDL Flashing guide and the process ends as expected with the last few lines of the output being as follows:

FIREHOSE READ: <?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="INFO: Calling handler for patch" /></data>
LOG: INFO: Calling handler for patch
FIREHOSE READ: <?xml version="1.0" encoding="UTF-8" ?>
<data>
<response value="ACK" rawmode="false" /></data>
FIREHOSE WRITE: <?xml version="1.0"?>
<data><setbootablestoragedrive value="1"/></data>

FIREHOSE READ: <?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="INFO: Calling handler for setbootablestoragedrive" /></data>
LOG: INFO: Calling handler for setbootablestoragedrive
FIREHOSE READ: <?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="INFO: Using scheme of value= 1" /></data>
LOG: INFO: Using scheme of value= 1
FIREHOSE READ: <?xml version="1.0" encoding="UTF-8" ?>
<data>
<response value="ACK" rawmode="false" /></data>
partition 1 is now bootable
FIREHOSE WRITE: <?xml version="1.0"?>
<data><power value="reset"/></data>

FIREHOSE READ: <?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="INFO: Calling handler for power" /></data>
LOG: INFO: Calling handler for power
FIREHOSE READ: <?xml version="1.0" encoding="UTF-8" ?>
<data>

After powering it down, and switching the SW2 back to off position, and connecting power and USB, nothing has changed. I am unable to see the device in adb devices or in fastboot devices and it is not showing up in ```
lsusb

Kindly help me debug this issue. The Voxl 2 is being powered by the supplied power module 2. I have tried other similar power modules and usb cables too with no success. 

Thank you,
Yours sincerely,
Jyothish Kumar J.

Hi @Vinny
An expansion board to access the GPIO pins in J3 and J5 connectors would be extreamly helpful.
Are there any updates on the designing front? Really looking forwards to this option.

Yours sincerely,
Jyothish.

Greetings,
I am seeing CPU loads of 50-60 percent while idling in voxl2. I have voxl camera server (which is handling hires (streaming at 480p only to portal)+trecking+ToF sensors), voxl qvio server and mavlink running. Is this kind of cpu usage stat normal? The voxl2 is heating up well over 80C in a room with 24C temp in this situation and a 25mm fan is not helping the situation much.
I wanted to ask if this is something to be worried about?

Your advice regarding this will be highly appreciated.
Thank you.

I see. Appreciate your help. Currently everything is on the dev branch. The two issues that I have originally mentioned prevail viz.
(1) voxl-configure-camera 6 is giving the error that sysytem image is too old (I am currently on voxl2 image 0.9.5 which is the latest one available in the developer assets). I am able to manually configure the cameras by editing /etc/modalai/voxl-camera-server.conf file to fit my camera arrangement.
I am able to see the stream of cameras on the voxl-portal.

(2) voxl-record-video command Is still showing

waiting for server at /run/mpa/hires_record/

Am I supposed to use some other command to be able to record video?