Hi @Matthew-Howlett ,

No the m500 currently has a BMP388.

The official product documentation is located at https://docs.modalai.com/

The purpose of this forum is to supplement that documentation, and to update the official docs when we find information missing.

Hi @rapit ,

OK we validated that a USB3 device can show up, here's a "guide", but there's no new info really, just an example: https://docs.modalai.com/voxl-as-usb-host/

-Travis

Hi @mrawding ,

The current early release on the EVT hardware relies on gstreamer.... for example:

cd /data/misc/camera
rm *

gst-launch-1.0 -e qtiqmmfsrc camera=0 name=tracker ! video/x-h264,format=NV12,width=640,height=480,framerate=30/1 ! queue ! h264parse ! avdec_h264 ! videoconvert ! pngenc ! multifilesink enable-last-sample=false location="/data/misc/camera/cam0_img_%d_.png"

This will save images to the path specified. We're actively working on getting the same interfacing as VOXL up on this ;). Next few weeks should have some good PUBLIC REPO updates.

Hi @gauravshukla914,

If voxl-vision-px4 is setup for VOA it will connect to the stereo and 'take over', if that's the case can you try the following before launching?

systemctl stop voxl-vision-px4

FYI for the future, the MPA architecture (https://gitlab.com/voxl-public/modal-pipe-architecture) will provide 'fan out' and allow multiple clients for a given camera.

@Gaurav-Borade , we have one in the works that should be ready shortly, I'll send a link once we get it posted!

Hi @mrawding ,

You are correct, there's something wrong, and I'm investigating this now.

The UART is active after bootup but then something fishy is happening.

When used with PX4 (ran on bootup) there's no issue.

I'll post here when there's an update to fix.

Hi @gauravshukla914 ,

Our flight controller is a little unique in that it can't be powered off USB so yes, it will lose power and connection during the standard process. (The reason being our Flight Controller shares the 5V rail with the companion computer and 500mA off USB won't suffice!)

To get around this, we have a tool that has a user guide here:
https://docs.modalai.com/flight-core-pwm-esc-calibration/

This allows you to keep the battery connected during the ESC calibration process.

This is for the STM32 based FlightCore.... not SLPI which I think you're super aware of but making sure!

Hi @Kevin ,

The VOXL2 (M0054) and RB5 Flight (M0052) images aren't compatible as they have different kernel and rootfs. So flashing the VOXL2 onto the RB5 leads to bricking.

But, on the RB5, you can get to a 'factory state' following this:
https://docs.modalai.com/Qualcomm-Flight-RB5-QDL/

That image is a factory image that is pretty old and not fully useable, so we need to flash an update.

You then have two choices.... reflash the same (9.1 based) image and use the RB5 Flight software (now in maintenance mode).

Or, use the ModalAI maintained VOXL SDK. To use the VOXL SDK, you need to update your RB5 Flight hardware with this from downloads.modalai.com :

We are currently working on an improved update guide and will post shortly.

Hi @Moodsh00 ,

Have you tried using voxl-streamer ? This would be the preferred way of using gst

https://docs.modalai.com/voxl-streamer/

Source code here:

https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-streamer

@darwin-keem ,

Going through the thread above, a link was provided for the RB5 Flight QDL, but you have a VOXL2 Sentinel.... So for QDL on VOXL 2 the link is: https://docs.modalai.com/voxl2-qdl/

And you should be using these files for the QDL process:

VOXL2 QDL Image 14.1a_1.1.2
r14.1a_1.1.2-M0054-14.1a-FLAT-V3.zip

Can you confirm that is what you have used? This is what we would use as the first step towards troubleshooting as well internally.

What I normally do is remove any hardware connections to the bare minimum if I'm having issues with bootup..... If camera connectors have issues, it can prevent bootup for sure.

Hi @Andrew-Keefe sorry for the lag, had this sitting in my inbox unread! We've not tried this setup but have used other radios via telem ports, and generally you can configure baud rates, what port are you connecting to on flight core and what baud / mavlink modes are being used?

No flow control.... really just need GND, Rx, Tx

Default UART for the ESC driver is here:

https://docs.modalai.com/flight-core-datasheets-connectors/#j4---uart-esc-uart2telem3

Hi @Tamas-Pal-0 ,

Sorry there's a typo in the docs I will fix now, but here's where the files live:

voxl2:/$ find / -name *.mix

/usr/lib/rfsa/adsp/quad_x.main.mix
/usr/lib/rfsa/adsp/quad_x_io.main.mix

The mixer and PX4IO drivers run on the DSP and this is the location for it's 'file system'.

Hi @Isaac_j ,

Let me check into this. The file should be at /usr/lib/rfsa/adsp/quad_x_io.main.mix, can you verify that it is not there?

The mixer runs on the DSP, and that's a folder that the DSP has access to.

The PWM functionality is available from the voxl-px4 'dev' channel, the file (setup for quad) is here in source as reference:

https://github.com/modalai/px4-firmware/blob/voxl-dev/ROMFS/px4fmu_common/mixers/quad_x_io.main.mix

And get's packaged here in the .deb package:
https://gitlab.com/voxl-public/voxl-sdk/services/voxl-px4/-/blob/dev/make_package.sh#L130

Hi @tanguy-sagere ,

Generally you don't need to disconnect anything to boot successfully into fastboot using the button, but in the case where this battery warning shows up, and until we release our System Image 1.4.x which has a bootloader fix, the work around is to remove the USBC cable if this bootup issue displays.

Thanks for this update @tangotoo . This isn't something we've seen (needing to use the AT commands for this) so we'll need to check this out on our side and I'll relay this to the team to check out. Thanks!!

Hi @tanguy-sagere ,

OK the last part of that console output above "looks OK" for the non-debug kernel, I've captured my system here (note I'm rebooting over adb for connivence to show when thing are happening).

Is this roughly what you see?

https://www.youtube.com/watch?v=5axL8w-Zb6c

The standard system image doesn't provide you a login over the debug console. You need to flash a debug kernel if you want to see the full bootup output (like dmesg but over the serial port) and you also can get a login over that same terminal, but the boot up time goes from ~10 seconds to like ~90 seconds, hence why we don't ship with a debug kernel!