Hi @Matthew-Howlett ,
No the m500 currently has a BMP388.
Engineer at ModalAI
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.
@Jetson-Nano not at this time and not with QVIO. We are working on multi cam VIO but can't provide any details or release dates really at this time.
@Jetson-Nano can you take a picture? for example, we make a M0070 board that has this sensor on it. Are you making your own carrier board for the sensor?
@Jetson-Nano what is the VL53L1X on?
You can use option 1:
Note, we've seen two connection types from Doodle (legacy and the newer one with multiple JST connectors).
We use this on another product of ours, and from USB3 port, MCBL-00085-1 should suffice:
@Jetson-Nano are you using our M0070 board like this? https://docs.modalai.com/rangefinders/#single-rangefinder-using-m0141-expansion-board
Or custom? If custom check pin 5, which on our M0070 board is pulled up to 3.3VDC.
@SMRazaRizvi we honestly don't have any gimbals on our products at this time so hard for me to say as I would want to have a working reference..... the gremsy gimbals are super nice and if they have a MAVLink interface, but to get this controlled straight from VOXL2 at this point would be some custom coding as we don't have a reference at this time...
@Jetson-Nano If you've reverted back to original config, run voxl-configure-cameras and select the D0005 Starling option.
When you want to use ov9782, you need to copy the correct binary into /usr/lib/camera and also update config file?
A high level helper is here:
https://gitlab.com/voxl-public/voxl-sdk/services/voxl-camera-server/-/blob/master/misc_files/usr/share/modalai/voxl-camera-server/custom_camera_config.txt?ref_type=heads
You can then use voxl-configure-cameras -c to use custom setup, after you've setup the above file into correct place (see top of the file for direction).
see this for logic of setting up proper bins:
https://gitlab.com/voxl-public/voxl-sdk/services/voxl-camera-server/-/blob/master/scripts/qrb5165-configure-cameras
see https://docs.modalai.com/voxl2-image-sensors/ for more info, but since we support a lot of different configs and, because of I2C clashes if we have all binaries in /usr/lib/camera, we copy bins into place using camera-server wizard.
@Aaky agreed - not an issue with camera pipeline at all to do that.
OK all shipped ok.
Above looks good with flat on table test results...
Here's factory test data which shows OK:
2024-05-03T22:01:18.648Z -- {"desc": "IMU1 - APPS PROC - OK", "GYRO_X": 1.001, "GYRO_Y": 0.998, "GYRO_Z": 0.994, "ACCL_X": 0.99, "ACCL_Y": 0.987, "ACCL_Z": 0.957, "FAILURES": []}
2024-05-03T22:01:19.361Z -- {"desc": "IMU0 - SLPI ACCEL - OK", "ACCL_X": 0.11492, "ACCL_Y": 0.20016, "ACCL_Z": 9.89428, "FAILURES": ""}
2024-05-03T22:01:19.960Z -- {"desc": "IMU0 - SLPI GYRO - OK", "GYRO_X": 0.02435, "GYRO_Y": 0.03108, "GYRO_Z": 0.00174, "FAILURES": ""}
If it passes flat on table I think things are OK and it's a result of expecting certain tests to run in this flat orientation during factory test.