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 @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!
Hi @amitga ,
This isn't something that we've done internally so we don't have any thing to reference. As you've mentioned there's hardware in there, but we don't have any background at this point enabling BT on the VOXL platform.
If the VOXL1 isn't booting up at all, you likely need to boot it into fastboot mode first, here's a reference on how: https://docs.modalai.com/usb-expander-and-debug-user-guide/#forcing-the-voxl-into-fastboot-to-unbrick
Hey @Patrick-Hinchey I can get on the phone with you tomorrow if easier just let me know.
It's likely the baud rate on the VOXL2 side that needs to be updated. There's a param
UART_ESC_BAUD that by default is 250kbit
I believe the default baud on this F55A config is going to be 2Mbit (
2000000 as the param).
When you mentioned you are talkin' to them over FTDI, is this through the voxl-esc python tools?
As for the MAVLink console, we don't have the plumbing going for some of the commands over the UDP link from QGC to VOXL2.
That said, you can get to the nuttx like shell via command line if you SSH onto target or adb (captured here, as a work around )
When attempting to update the Flight Core v2 firmware with QGC 4.2.x (perhaps other versions as well) on Ubuntu or OSX, the upgrade always fails with a warning like:
As a work around, you can upgrade over the same USB port using a simple python script from the PX4 Tools that are maintained by the PX4 community. Please see info here:
Hi @Slade-Villena , currently it's 18.04.
Next on the roadmap is 20.04, but generally it's not upgradeable in our experience (e.g. I don't believe you can currently go 18 -> 20 without first us generating a full system image).
Upgrades are on our roadmap but I don't have firm dates at this point unfortunately, so it's safe to say expect 18.04 for the time being.