Topics created by blue

After connecting the VOXL2 Mini to an external flight controller as described here via J10 on VOXL2 Mini, MAVlink data was viewable from a VOXL Flight Core v2.

We are still having some troubles with viewing the streams, however now the stream/camera names are appearing in QGC with the video feed selector now that the above MAVlink connection has been established.

It seems like in order to route MAVlink data out of J3 on VOXL2 Mini via USB, we will need to look into MAVrouter or a similar solution. For now we will continue integration via J10.

Our goal with routing MAVlink data via USB on VOXL2 is to reduce the telem connections required on a flight controller for our product. We would like the ability to run multiple RTSP streams and MAVlink communication via a single USB connection (from J3 on VOXL2 Mini) to an external flight controller.

Is UART communication via J10 the preferred or only method of communicating with VOXL2 Mini over MAVlink?

Is there a way to do MAVlink routing with the VOXL SDK as I mentioned, or will this need to be custom implementation?

If the VOXL2 Mini is receiving MAVlink data via a UART connection from another device, will the VOXL2 Mini forward and receive MAVlink data to/from the MAVlink device through to a Flight Core via the external flight controller connection J10 on VOXL2 Mini?

Thank you for very much for your time and feedback on this topic.

@blue
OK thanks for the beta feedback.
We will keep that in mind. I'm sure what we did was to mimic an existing OTS product at first, and that used a backplate. I'll get with our production team to ensure we have a backplate in future kits for this version.
Thanks!

@blue , i just fixed (a few days ago) the calibration script (on voxl-esc dev branch) to plot the total current for M0138 in the calibration procedure, however, yes you still need to run the calibration test using ID2. This is because ID2 measures the total current and it only sends back the data if the feedback is requested from it. If you are running a test on a single ESC which is not ID2, then ID2 is not asked to send any data back, this allows for 4x the feedback rate for that single ESC that is being tested.

So on M0138 if you want to see the current output, you should use ID2 for testing:

./voxl-esc-calibrate.py --id 2 --pwm-min 10 --pwm-max 95

Currently, the current ( 🙂 ) is not used for anything in the calibration procedure, but it is good to look at it to make sure it follows a smooth curve as the power ramps up.

Thanks, I try to add as much data to plot as possible because it is often easier to spot issues by looking at the plots. By the way, it seems your data time scale is kind of coarse (seems like 14-15hz). Sometimes this can happen if your USB-to-serial adapter buffers too much data.. are you using a PC or VOXL for this test? if you are using FTDI, this may be helpful to test out : https://granitedevices.com/wiki/FTDI_Linux_USB_latency

You should be able to get really nice plots when using 2Mbit baud rate and --cmd-rate 1000 or even 2000 helps catch any small spikes or anomalies.

In your calibration test that you originally posted (where the current was reported zero), it looks like towards the end, the top left curve (commanded motor voltage vs rpm) starts curving up a bit more, that can suggest that the motor is not operating optimally at that point. I am not sure which motor / propeller you are testing, but sometimes it helps to adjust the ESC commutation advance from 0 to 20 or so (esc param <param name="timing_advance" value="20"/>). You could try that and see if the high end shape of the curve does not curve up as much.

Alex

@Alex-Kushleyev thank you for your response, this answers my question!

Express LRS does work via the above wiring on VOXL flight after testing 👍 in Q Ground Control

@Vinny thank you so much for the thorough and punctual response!

I will give this rework a shot per your instruction and report back if I have any issues.

@Moderator Thank you for the response.

I did come across this product of yours here: https://www.modalai.com/products/mdk-m0135?_pos=1&_sid=e4d19a51b&_ss=r that should work great after looking through some of your user guides and technical documentation.