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 @mrawding ,
The current early release on the EVT hardware relies on gstreamer.... for example:
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 @gauravshukla914 ,
Thanks for the help with this. We've released a new beta version of the
voxl-hal3-tof-cam-ros that supports auto detection of ToF and defaults the
persist.camera.modalai.tof setting properly.
It will be in out next voxl-suite release, but is available from our dev channel here if you are interested in using this link
The updated readme is here.
Little more detail, we've validated with FrSky X8R reciever and Taranis X7 transmitter with the following setup:
We have a new cable about to come out to assist with this wiring as well:
Hi @roy ,
Typically the easiest way to interface is through a UART. That's what we do on our VOXL-Flight product. There's the Snapdragon 821 on one side, and an STM32 on the other, and they communicate via a UART at 921.6kbuad. Latency has not been an issue.
Same idea roughly on VOXL2, except this time we have PX4 running ON the snapdragon 865 on a DSP instead of offboard.
BUT, you don't need to use that, and can get mavlink going over UART to some other controller that has a UART and speaks mavlink.
We are in the process of exposing more UART(s) that the application processor can have access to.
Right now you need a daughter board that has a 2W uart exposed on a JST 4 pin.
Soon, we're looking to change the SPI on J8 to a UART, and with a little level shifter, we can get UART in that way.
We are also working on getting the UARTs that are on J19 to be "pass through" through the DSP. Once we have that going, then you could connect via J19 without level translators. So a few opions... the only one immediately available is via a daughter board UART, or if you wanted to try a SPI to UART convertor off of J10....
Holler if you have any more questions and we can help.
Hey all on thread, some updates here.
Main issue - USB-C as host not working yet on VOXL2:
Recommended configuration for Boson connection:
If you also need two USB ports, then this board (the M0090 carrier board only) which has:
if just 1 USB port, then we have a smaller M0078 USB debug board
if just 1 USB port AND you want to add an applications processor UART port on 4pin JST, we will have a new M0125 up online shortly, which I think is pretty cool!
Using out of the USBC connector will prevent you from adb access.... so in a vehicle if it's permanently mounted there (and assuming I get the fix!) then you could prevent ability to flash it later on if needed or to troubleshoot, but if that's no issue then I'll update you ASAP when I have updates on this.
Hi @gauravshukla914 ,
This looks to be supported in a new feature that is in our 'beta' system image release version 3.2.0 (available at developer.modalai.com for download).
It requires an unreleased version of
voxl-hal3-tof-cam-ros, see here
We haven't merged this into a release yet, so we don't have a packaged release for this, but you could build from source if needed until then if you're up to try it out.
Hi @Tamas-Pal-0 ,
I think we have a util that can be used as a work around....
Are all 4 image sensors showing up when you run
voxl-camera-server -l ?
If so, then use those IDs and try running this helper which can get the config file setup:
camera-server-config-helper vio0:ov7251:0 fpv:imx214:1 tof_front:pmd-tof:2 tof_rear:pmd-tof:3
Note, the last values there are the IDs from your setup and might be different.
Let me know if this works, I only have a single ToF with me to test so I'm not positive!