Please refer to the mavlink routing documentation here: https://docs.modalai.com/mavlink/#mavlink-routing-on-voxl

@tom Perfect, thanks! I'll check these out

@peterkrull I think qrb5165-emulator is a fine choice.

@James-Strawson That makes a ton of sense, thanks for the explanation! Also just noticed that it mentions this right above the definition. I should just learn to use my eyes 😁

Plan so far for setup

clone voxl-configure on gitlab

add my own case statement to voxl-configure-mpa
d0bdfbf8-2393-4a2c-bbd5-a039b2b0408b-image.png

If I wanted to add my own script to run after, I could probably add it after voxl-check-calibration
80734ed0-6595-428c-8cf4-ef5db25e33f3-image.png

modify voxl-configure-sku with the board that I am using and the camera setup I have482ed50c-2d31-4752-9289-386c196a375d-image.png

I would recompile voxl-configurator myself (forming a deb file)

Plug in voxl2

Flash most recent SDK

copy the voxl-configurator deb file onto the device and install it

run voxl-configure-sku

run voxl-configure-mpa and select my custom added drone

@JoeC Ah, yes, that is an excellent question! Rather than try to update the firmware in your existing voxl io board(s) we will send you new one(s) with the updated firmware. These new ones will also be upgradeable in the future. Contact us at http://modalai.com/contact to request your updated module(s).

nevermind, this is fixable with voxl-configure-mpa-to-ros2 and voxl-configure-pkg-manager. Leaving this up for anyone else having the same problem.

@Moderator I think none of the previous yolo versions allow tracker usage without having explicit access to the model itself, and based on what I read on the modal ai documentation there is no way to do that.

@Eric-Katzfey Thanks to you we now have our motors running right off the SLPI processor with PX4 as a UART 'bus'. Everything seems to work great. The main issue was figuring out what qshell commands to send to start it up properly.

@Darshit-Desai Can you try the v1.13 PX4 for the Flight Core? https://docs.modalai.com/flight-core-v2-firmware/

@Manu-Bhardwaj

Hey Manu, happy to help you with this and any other questions you may have. Can I start by asking what version of the VOXL SDK you're using? /etc/modalai/voxl-tflite-server.conf is a file that is written upon flashing the SDK and so I'm surprised to hear the file isn't being found. If by some chance it got deleted, you might benefit from re-flashing the SDK.

Also in your email I saw you had some other questions about VOXL TFlite Server, maybe you'd like to post those here or create a new forum topic?

Looking forward to helping you on this!

Thomas Patton

Thanks it works like a charm now for the help

@michi

Yeah, I'd be curious to know what your results are like using a custom YOLOv5 model. If things are still slow, the issue might be in your quantization process. However if it speeds up, it may just be that the model architecture is too big.

I have it on my to-do list at some point in the next few weeks to add YOLOv8 to our list of default models so when/if I do that I'll keep you posted with the results of that as well.

Keep me posted on how I can be of assistance!

Thomas Patton

@Jeffrey-Mao

I am assuming you are asking about VOXL2 with ov7251 stereo in combo mode (using a single 4-lane camera port)

Please check in /usr/lib/camera, you should see two com.qti.sensormodule.ov7251_combo* files. you should remove them and replace them with ones from /usr/share/modalai/chi-cdk/ov7251-combo-flip, making sure you copy the files with the same camera slot index (the number at the end before .bin). Then simply restart voxl-camera-server and the cameras should be rotated 180 (this happens by reversing the direction the images are read from the camera itself, not rotated in software)

@tyorb It would be a massive undertaking and we would only be able to provide very minimal support. I'd definitely recommend against it.

@Eric-Katzfey This is working great, been playing around with it for the last week or so. The next thing I'll be working on will be the order in which the cameras streams are displayed to QGC. It seems right now on boot the initial stream that comes up in randomized over the various camera being fed into QGC.

@jenyeom , i am not sure, can you please try setting cpu mode to performance:

voxl-set-cpu-mode perf

This will prevent cpu from sleeping excessively in low power mode. Perhaps the dt is so low that the cpu oversleeps and does not handle all the imu messages.