Topics created by kiprock

That is what I thought. I have not updated the system yet. Please let me know when this update is available!

Hi @Chad-Sweet it appears that I am on voxl-suite 0.2.0 as indicated above. However, if QGC reports that avoidance system is unavailable and the vehicle will not arm. If I run

voxl-vision -s

I can see the obstacle debug info on the terminal, also I set

"en_voa": true,

Any suggestions as to what I am doing wrong?

@Voxlady Thanks for the clarification I'll report my findings here.

Hi @John-Mccarty , checking in to see if you've progressed at all through this? The process is a little picky and sometimes requires a few tried.

Hi @kiprock ,

The motor test commands I've used were from the MAVLink shell, but using the pwm test command: https://dev.px4.io/master/en/middleware/modules_command.html#pwm

I've seen similar issues when trying to use the built in QGC PWM calibration feature... Since the Flight Core v1 can't be powered over USB (an artifact of sharing the 5VDC rail with VOXL when paired together and the fact that 500mA isn't enough to juice VOXL), it requires the python util that you linked above.

Thanks for the feedback! The documentation has been updated.

@kiprock do you mind if I use your images in our docs?

Good news. We will get that updated to be a little more clear.

ACCESSD16. I tried another receiver and it works, must have been a bad receiver.