@Nishkala I used this link - https://docs.modalai.com/voxl2-system-image/#force-voxl-2-into-fastboot

You will need the latest platform release which can be found here - https://developer.modalai.com/asset/2

VOXL comes in the VOXL-Flight configuration, which basically mates up an STM32 based flight controller (the Flight Core v1) with VOXL, then there's an internal UART connecting the two, and you can control the Flight Controller with 8-PWM outputs.

VOXL2 does support (currently in beta) the VOXL2 IO board which provides PWM outputs, and we've used it on a hex. See here for info on that use case. Again, this is in beta (not directly in the VOXL SDK at this point but in the dev channel).

Depending on your size constraints, VOXL2 also can be used like VOXL-Flight, where you can use an external flight controller (like Flight Core) externally, which has 8-ch PWM. See here for info on that use case.

(Why not native PWM? The VOXL/VOXL2 platforms are Snapdragon 820/865 based, which are primarily used in cell phones.... The PWM feature is not needed in cell phones, so these type of SoCs don't generally have native PWM...)

@Chad-Sweet @Adrian-Hidalgo @James-Strawson
Everything is working now! THANK YOU so much for all your help!!!

@Hector-Nevarez Problem solved, was hardware-related. Thank you for your help!

@Yusuf-Saib If you do ifconfig on your host machine you will get the IP address of that, not of the VOXL. So in your output it looks like you are trying to ssh to yourself.

The problem is solved. The problem was in FTDI cable. I changed the cable and it worked

The problem is solved. It was a hardware issue related to ftdi cable

We have the full toolchain and setup dockerized here: https://gitlab.com/voxl-public/rb5-flight/rb5-flight-px4-build-docker

Following that setup, you will install the Hexagon SDK which provides more info on the lower level stuff.

But, the PX4 code as shown above is what runs on the DSP.

@Alex-Gardner Got it. Thank you!

directly in the main folder or do i have to do it in the sub folder? @Eric-Katzfey

Hi,

We've never tested QVIO on the hires cam, it's been extensively tuned for the fisheye tracking camera and benefits heavily from having a wide field of view. I suspect that this is where you issue originates. You are more than welcome to try this but you'll need to make sure that you've calibrated the hires camera and have defined accurate extrinsics between the camera and the IMU, but even with these done well it's likely to behave worse than the wide FOV tracking camera.

Please see email thread in progress, if possible let's use one channel for communications.

Hi,

The same software stack runs on both VOXL and VOXL2, in which we have a voxl-mapper project for mapping/planning (though this is still firmly in beta and under active development by our team). The VOXL is capable of performing the mapping on its own, but the software stack is heavy and will take up a larger portion of the processing power on the weaker board. The VOXL2 is able to support more sensors and more processing, but with the obvious tradeoff of the higher price point. It'll be dependent on your use case which one you will want to use.

@Ed-Sutter Hi Ed,
I just now see you made two posts, so that other link along with this link is the bulk of what we have for showing the system level connections in a Voxl Flight Deck:
https://docs.modalai.com/flight-deck-datasheet/#2d3d-drawings
The Flight-deck exposes the ModalAI "Legacy" B2B (board to board) 60-pin connector which supports our modems, Microhard, and "debug" boards.
All of those products support additional USB downstream ports so you can keep your primary USB to Voxl clear and open for ADB/Updates.
https://www.modalai.com/products/voxl-debug-board-v2
https://www.modalai.com/products/voxl-lte?variant=32449203601459
https://www.modalai.com/products/voxl-microhard-modem-usb-hub

Our schematics are not open hardware, but we do share a lot more than most.
So if you need more info, please let me know.
Thanks!

@Eric-Katzfey Yea... good thought... I'll look into that... Thx

@vivek-rk For anyone looking for a quick fix, you can use the voxl rtsp server for the hires only, for MPA support use the add-mpa-support branch

Hi,

You can definitely try it but the QVIO algorithm benefits A LOT from having a wide field of view on the camera and the hires cam has a fairly narrow field of view, especially when compared to the fisheye tracking camera. There are no hard restrictions to trying this but know that performance will almost certainly be worse.