Hello team,

I have a seeker with px4 firmware 1.11 and a M500 with firmware 1.13. We found that our seeker will switch into Altitude mode instead of Position mode when Offboard failsafe activates however our M500 does not (both had their COM_OBL_RC_ACT set to position). Our guess is the px4-fimware cause this problem, so we upgrade the px4 firmware to 1.13 for our seeker. And indeed once the firmware has been updated to 1.13, activating Offboard failsafe will switch seeker into position mode as expected.

However, after we update the seeker to 1.13 (either using the "modalai_fc_v1_default.px4" downloaded from the px4 github releases (we've also tried 1.13.3, 1.13.2, 1.13.0) or using QGC), loading parameters from either files (https://gitlab.com/voxl-public/flight-core-px4/px4-parameters/-/tree/master/platforms/v1.13/Seeker) will result in writing parameter fail for UART_ESC_XXX (and a couple more) because these parameters does not exits for the firmware. We suspect this is the reason for seeker not able to arm after the upgrade.(By not able to arm we mean we can send arm command through QGC and QGC will show "armed" but actually the motor is not responding)

In short:

(1) Why with FCv1 - v1.11.3-0.2.3, activating Offboard failsafe will switch seeker into altitude mode even with COM_OBL_RC_ACT set to position? (While with 1.13 activating Offboard failsafe it will switch to position as expected).

(2) How can we successfully load the parameters from https://gitlab.com/voxl-public/flight-core-px4/px4-parameters/-/tree/master/platforms/v1.13/Seeker after update the firmware to 1.13 using QGC or .px4 files downloaded from https://github.com/PX4/PX4-Autopilot/releases?

(3) Or, could seeker not arming after updated to 1.13 actually caused by some other problem?

thanks in advance for your time and assistance.

Jeff

I think you can use voxl protal first to check if the camera configure is okay, then use "rqt_image_view" in ros to check ros configure.

If you rostopic list on your pc does it show any topic ?

Hello, I would like to get my drone return for repair and I have a question about the rma-form. Since I am not the original buyer, so I'm a little bit confuse about the Original Order Number for Product on the rma-form. Is it Order#2838 on the original box which I received my drone?

Also, besides adding RMA (Drone) Diagnostic and RMA (Drone) Return after Repair/Diagnostic to the cart, Is there anything I should know before I ship my drone? Just want to make sure that everything is fine. Thanks!

Quick update, mavlink suddenly connected yesterday, but after few minutes it disconnected again. Since I didn't change any of setting, so I think it's bad contact causing the disconnection. What do you guys think of this?

@Chad-Sweet Thanks for your quick response.

I check the cable between them and it looks good to me. I also re-plugged some of them and check mavlink status, still shows disconnected.

Hello, I can't connect my seeker to QGC. I have already reconfigured voxl-vision-px4 and voxl-mavlink-server to the factory setting and both of them are enabled and running.

But when I look into it by using status -l voxl-vision-px4, it says:

Jan 01 00:00:09 apq8096 voxl-vision-px4[2589]: WARNING: connected to voxl-mavlink-server but no messages from PX4

And when I check voxl-mavlink-server, it says

Jan 01 00:00:10 apq8096 voxl-mavlink-server[2710]: PX4 DISCONNECTED FROM UART

Here is my mavlink.conf on seeker

I already try my best to fix this and gets no luck...... So hope you guys can help me with it.

Sorry for interrupt your Christmas vacation.

@Patrick-Hinchey looks like your pose didn't fixed according to apriltag this time. Maybe you can try to handhold the drone and inspect voxl-vision-px4 -f or inspect voxl-pose -f to see if the apriltag fix your position or not.

If not maybe you can follow https://docs.modalai.com/voxl-tag-detector/ to setup. If it does change pose, check the value to make sure it's correct according to apirltag

It's been a while since I use apriltag, so I'm not 100% sure.....

But I think you can try to use /mavros/setpoint_raw/local as publisher topic and give it with coordinates frame as FRAME_LOCAL_NED, mask with 1991 and give it a try.

Again I'm not 100% sure so I'm not responsibility any tragedy that happened.

I think since m500 use s500 airframe so the prop guard for s500 should be work, just double check the guard is bigger than prop.