Hi @camcam The only I2S functions are on J5, but there is no ModalAI support for it. It has not been on our roadmap, and we only added it in for "Power Users" if they wished to try to develop with it. You would need to be a trailblazer at this point to try it both in HW and SW, and to enable the alternate functions within the chipset. We have zero experience here so we cannot help at this point. Hence why USB is the preferred approach. If you were on the Qualcomm Developer Network Forum, you might need to directly ask on there for assistance at this time. Here is the alternate function mapping for both I2S and SLIMBUS if you wished... these pins will be available on our new breakout board in the works (will be a couple more months before we have that ready). GPIO_142 = I2S_SCK GPIO_143 = I2S_DATA0 GPIO_144 = I2S_DATA1 GPIO_145 = I2S_WS GPIO_137 = I2S_MCLK/REF_CLK Alternatively, GPIO_142 = SLIMBUS_CLK GPIO_143 = SLIMBUS_D0 GPIO_144 = SLIMBUS_D1 GPIO_145 = SLIMBUS_D2

Hi @Dong-Liu OK thank you for the update. Once it has been updated to the latest image, I wouldn't expect that battery error to show up in the future.... if it does please let me know!

@McMason Can you please guide me on how to solve this issue? I am having a similar problem with the Sentinel drone, when I run the voxl-mavlink-server -r command, there is no main loop being triggered. Hence, I am also unable to see the drone connected to the QGround controller.

Thank you, then we will take a look into this. For now, a simple RC circuit works.

Any tips on how to control this from ROS for offboard mode?

@mzahana VIO will definitely be supported. I don't think we are currently using the dds client in any of our applications but there's no reason why it wouldn't work on our platform.

@Chad-Sweet Thanks for replying? Could you please provide an answer for the asked 4 points? What exactly needs to implemented ? Where to start ? I appreciate if you can elaborate more. Thank you.

@Mastermind This is the source for voxl-wifi on VOXL2 if you want to take a look: https://gitlab.com/voxl-public/voxl-sdk/utilities/qrb5165-system-tweaks/-/blob/master/scripts/voxl-wifi

Hi Josh, Did you test the VOXL 2 with FLIR Boson and FLIR Lapton? What is the configuration setup? Yes, please see https://docs.modalai.com/voxl-uvc-server/ For the other items, it may be easier to use an external flight controller. VOXL 2 has a different set of I/O than STM32 based flight controllers. In general, if it's not documented here, it will be a lot of work to implement

Hi @Vinny Sounds good. I have order number 3143. We have the Voxl1 version ready to return. I'll be here for further instructions Thanks Andres

Hi Tamas, did you solve the problem? I have the same issue.

I am facing the same issue. How can I account for this noise? Are there any parameters to tune to filter the sensor output on the voxl2 side? @Anubhav did you solve this issue?

Any ideas from the dev team?

Posted 2D drawings for both front and back here: https://docs.modalai.com/voxl2-datasheets/

To build voxl-qvio-server, please follow the instructions in the README. The instructions are validated nightly by the CI The first paragraph of the README explains the following: "Due to MV SDK being 32-bit only, this is the only 32-bit package for QRB5165. The APQ8096 package builds in voxl-emulator, the QRB5165 package builds in qrb5165-emulator using a 32-bit cross compiler installed in the emulator." the only way to build that package is to follow the instructions in the README. Installing your own compiler will not work, you need to use the toolchain provided.

The lowest level recovery that we use is QDL https://docs.modalai.com/voxl2-qdl/ QDL can be used of fastboot is not working and the flash is completely corrupted. Of course the rest of the device must still be functional as QDL just repairs flash

@Steve-Turner Thanks