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,

Our next VOXL2 beta release will ship with the drivers, this is slated to be available soon (within weeks) and will provide for initial testing.

Hi @Dong-Liu OK thank you for the update. Once it has been updated to the latest image, I wouldn't expect that battery error to show up in the future.... if it does please let me know!

OK thanks, the 20230521 should contain the fix for the battery warning (it's in the android bootloader) but the 1.1.2 image still has the bug so yes, I believe if you're unable to get through the battery warning we need likely press the button in this case

We will also work towards updating our QDL image such that it updates to a newer version.

Let me know if you get stuck and we can perhaps get on a screen share or something.

Thanks!

Hi @Dong-Liu ,

Normally to get around this issue, you need to bootup WITHOUT the USB cable connected initially, here's a video that shows the process:

https://www.youtube.com/watch?v=IM3PnW7cipQ

Out of curiosity, do you know the version of the the system image is on the VOXL2 presently? And what version are you trying to update to?

We should have this battery warning issue fixed in platform release 0.9+.... so I'm making sure you aren't seeing this on a that release, as it 'should' be fixed but perhaps we're missing something!

Hi @Peter-VW ,

Yes correct, we have that defaulted HIGH for one of our modems, that's being set in the kernel here, which is the only way I know how to set a default value....

https://gitlab.com/voxl-public/system-image-build/meta-voxl2-bsp/-/blob/master/recipes-kernel/linux-msm/files/dts/common/m0xxx-kona-pinctrl.dtsi#L125

So, I don't know if this is 'easy' but a kernel rebuild to set default state is currently needed. We've not figured out a way to do DT changes 'run time' at this point.

Hi @Jack-Bishop ,
Not yet, my current plan is to build two versions of devcfg and kernel and provide both for a release as I haven't found a way to do this swap run time.... We need to rebuild the kernel with a tiny change, which I'm waiting for the dust to settle before doing but that seems to be soon here. Would you be up to test out some 'dev' builds?

Hi @Gerhold-Ten-Voorde , I don't have this going yet but it is still scheduled to be worked on 'shortly'... we are releasing a new SDK shortly (1.0) to support a new board and then my plan is the next release thereafter (1.1). As soon as I have a pre-release I will share with you.

@andrespalomino we have manufactured a couple types of the M0090.

There's a VOXL1 based flavor, that only has a single board to board connector on the BOTTOM side of the M0090.

The VOXL2 based flavor has TWO board to board connectors.

Did the M0090 come pre-installed or did you add it yourself?

Can you look under the non-functional board and see if there's 2 board to board connectors? EG for VOXL2, the J3 and J5 connectors, should both be plugged into. The UART referenced here is on the "High Speed Board to Board Connector" which is J5 --> https://docs.modalai.com/voxl2-linux-user-guide/#devttyhs2---hsb2b-connector-uart

If you have the VOXL1 version of the M0090, perhaps this is the culprit....

Hi @Taylor-Presley give me a holler if after you get the new setup you still have problems and I can get on the phone with you and try to troubleshoot!

Hi @andrespalomino , J9 on the M0090 board has the UART exposed (see https://docs.modalai.com/voxl2-external-flight-controller/#using-m2-5g-modem-addon-board-m0090) on pins 2/3 and you'll also need GND on pin 6.

J8 exposes GPIO by default or a SPI, so it definitely won't work for a UART... so don't use J8.

Can you post a pic of your M0090? I don't expect it to be missing J8 connector... Perhaps J6 is DNI as that is a kernel debug UART not used by most.