Topics created by jonathankampia

@jonathankampia Brilliant! thankyou for figuring this out.

@jonathankampia , sorry for the delay, please see the response in this post https://forum.modalai.com/topic/3952/flir-boson-beta-hardware

@jonathankampia , were you able to first confirm that you can control the gimbal using the actuator test in QGC for the pwm channel 5 (make sure to remove propellers for testing, just in case)? it should work just like any other pwm channel, i am assuming you already have channels 1-4 already set up and working with ESCs?

If PWM actuator test is working through QGC, then you have VOXL2 IO board set up correctly and the rest of the logic for actually driving the pwm signal should be the same as for regular PX4 drone (which does not use VOXL).

At the end of the day, the VOXL2 IO driver receives 8 channel values from the mixer and just sends the desired pwm values out to the VOXL2 IO board. All the logic above the mixer is standard PX4 and if you have a question about that, you can also try the PX4 forum (since we are not necessarily the best PX4 experts).

You can try your python script, make sure propellers are off until you know exactly what you are doing and are ready to fly 🙂

Alex

@jonathankampia Edit: managed to fix it by disabling voxl-configure-modem and manually setting the IP of the eth0 interface. I guess 'eth1' is the J11 connector then.

@Zachary-Lowell-0 Hi, sorry for the late reply. This was the issue (lol)

@Alex-Kushleyev I never uploaded any parameters, just used both escs out of the box. maybe that caused the issue?

@jonathankampia Yes, it would require modifying the "tones" in whichever esc param file you're using. For example for starling 2 it is defined here: https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-esc/-/blob/master/voxl-esc-params/D0014_starling_1504_3000kv_ms_props/D0014_starling_1504_3000kv_ms_props.xml?ref_type=heads#L90

@jonathankampia Yes, both qmc5883l and ist8310 are supported now.

@Eric-Katzfey The EKF2_EV_CTRL param is set to 15 bits (all enabled). We don't have any cameras on the drone at the moment, though. Could that be introducing issues in the EKF2 and causing it to reset? I'll try disabling all vision stuff and see if it works different.

@jonathankampia We only add drivers to the build that we have used and tested with. The ll40ls driver is not one of them so you would have to add that to the build yourself.

@jonathankampia You could run UART based comms like an external flight controller on that UART: https://docs.modalai.com/voxl2-external-flight-controller/

but no you couldn't connect a USB device there

Tested on 1.12.2, seeing same issue

@jonathankampia Did you solve this issue?

For the -c which is telling the Voxl board which cameras to expect, choose either 3 or 7 depending on your camera config.

Hi @jonathankampia,

After running voxl-mpa-to-ros, you should see the /tflite_data and /tflite topics created as they just mirror the existing pipe names from the tflite-server.

I am not sure what you are referencing with the tflite_detections topic, but if you could share the output of voxl-version, voxl-list-pipes, as well as a rostopic list with the two services running I can help debug.

This functionality was added to voxl-mpa-to-ros in v0.2.2 and it seems you have some very old software on this drone. I recommend upgrading to the latest sdk by downloading and flashing the VOXL Platform 0.9 release from https://developer.modalai.com/