Hi @Matthew-Howlett ,
No the m500 currently has a BMP388.
Engineer at ModalAI
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 @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.
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.
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:
This allows you to keep the battery connected during the ESC calibration process.
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:
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 @dongsup-seo thanks for reporting, things should be up again here: https://gitlab.com/voxl-public/system-image-build/qrb5165-kernel
The Starling has this breakoutboard attached:
It has an apps proc UART available at
Perhaps you can use this UART, and voxl-mavlink-server has external FC support:
Hi @Enrico-Bandera ,
I've seen this to, and I believe my work around was to sort of remove the working output/or start from a clean git clone.
There's some bitbake/poky cache something or other that causes this problem that I'm not clear yet how to fix... holler if you are still stuck.
the px4io implementation changed in px4 1.12 to 1.14... SDK 1.0.0 moved to 1.14 and the protocol busted...
We are planning to support SBUS in a SDK 1.0.1 release (as an engineer, I will say it's coming out soon, but I'm optimistic always... so I can't put a date down just yet).
As far as PWM support, we are looking at ripping px4io totally out of the voxl2io board and putting our own FW inside so we aren't tied to px4io at all.
Sorry for the inconvenience here, the support matrix got way to out of control and we are trying to get PWM/RC support back going with voxl2io properly and not use px4io which we can't control...
We can provide updates as we have them, including swapping out voxl2io boards in case you can't reflash in the field.
@Anubhav I believe use QGC should work, I would not try to use the method for FCv1 (since we couldn't power over USB, you weren't able to use the standard method in QGC).
If you are powered off USB on FCv2 and use the QGC method, what issue are you having?
@Mastermind OK I think I'm seeing things a bit more now!
First, let's confirm, when you say LTE v2, you mean this right? https://docs.modalai.com/4G-LTE-Modems/
I ask because Tom brought up, our 5G Modem, has a real UART: https://docs.modalai.com/5G-Modems/
OK back to the question, I think what you are seeing now, if you go directly from a USB port (say LTE board or MH board) to a Flight Core, you will basically be doing what happens when you connect a Flight Core to QGC.
That USB port on FCv1/FCv2 J3 is used for QGC connections and not telemetry like we expect via a UART TELEM. (as far as I know).
So imagine if you had QGC installed on VOXL2 (this won't work!) and then you had the setup of FC straight into USB, you would then have a QGC USB connection like a host PC!
Now, if there is a USB to Serial adapter between the LTE or MH board and a Flight Core's TELEM UART port, then I would expect something similar to enumerate in LSUSB (like /dev/ttyXXX) that COULD act as a UART, and then this would be OK to try with voxl-mavlink-server, but we likely need to modify code as it expects /dev/ttyHSX at this point.
voxl2 --> add on board with USB --> straight to FC J3, not gonna work as we intended
voxl2 --> add on board with USB --> USB to Serial --> to FC TELEM port, should work as intended!
We are still pressing on with the DSP UART path and will get that online anyhow ASAP (but I'm kinda slow lately so bear with me)
@Mastermind what are you wanting to use on VOXL2 to talk to the external flight controller SW wise, you own program, or voxl-mavlink-server?
I was about to start testing and I failed to realize we need to do some work to get voxl-mavlink-server to use this new interface... so more like EOW