m500 VOXL Flight sdk update to v1.1.x
-
@tom V1 or V2? Because when I flash firmware it detects v2
-
@Darshit-Desai Sorry yes v2 https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-px4-params/-/blob/master/params/v1.14/platforms/M500_FCV2.params
-
@tom It's hard for me to follow which hardware you have, so whichever one you have v1 or v2
-
@tom Yes I am also not sure what came with m500 I recently bought because the earlier ones had v1
Edit: The motor issue was resolved with this and I can spin the motors, I will have a flight with the propellers and confirm it
-
@tom On the next reboot it's showing esc failure in the logs
[13:38:12.651] Info: Kill-switch engaged
[13:38:13.768] Info: Kill-switch disengaged
[13:39:33.963] Info: Armed by RC
[13:39:34.096] Info: logging: opening log file sess114/log100.ulg
[13:39:34.296] Critical: Failsafe activated, triggering disarm
ESC failure
[13:39:34.296] Info: Disarmed by failsafe
[13:39:36.780] Info: Armed by RC
[13:39:36.781] Info: logging: opening log file sess114/log101.ulg
[13:39:37.131] Critical: Failsafe activated, triggering disarm
[13:39:37.131] Info: Disarmed by failsafe
[13:39:39.424] Info: Armed by RC
[13:39:39.465] Info: logging: opening log file sess114/log102.ulg
[13:39:39.787] Critical: Failsafe activated, triggering disarm
[13:39:39.787] Info: Disarmed by failsafeAnd the motors try to spin up for a few seconds when arming and then instantly stop
When I move this sliders now the motors rotate but when I try to arm the drone using RC it shows the ESC failure error
-
D Darshit Desai referenced this topic on
-
@Darshit-Desai If you upload the px4 log someone on our team can analyze it
-
@tom By px4 log you mean the one mentioned in the post earlier, How can I access the log file which is mentioned here in the QGC log?
@Darshit-Desai said in m500 VOXL Flight sdk update to v1.1.x:
[13:38:12.651] Info: Kill-switch engaged
[13:38:13.768] Info: Kill-switch disengaged
[13:39:33.963] Info: Armed by RC
[13:39:34.096] Info: logging: opening log file sess114/log100.ulg
[13:39:34.296] Critical: Failsafe activated, triggering disarm
ESC failure
[13:39:34.296] Info: Disarmed by failsafe
[13:39:36.780] Info: Armed by RC
[13:39:36.781] Info: logging: opening log file sess114/log101.ulg
[13:39:37.131] Critical: Failsafe activated, triggering disarm
[13:39:37.131] Info: Disarmed by failsafe
[13:39:39.424] Info: Armed by RC
[13:39:39.465] Info: logging: opening log file sess114/log102.ulg
[13:39:39.787] Critical: Failsafe activated, triggering disarm
[13:39:39.787] Info: Disarmed by failsafe -
@Darshit-Desai The logs can be downloaded through QGroundControl: https://docs.px4.io/v1.11/en/getting_started/flight_reporting.html#downloading-logs-from-the-flight-controller
-
@tom Here's the ulog file link,
https://drive.google.com/file/d/1vuy_Ut0h_rEZDWseDgeywE093CISo9RB/view?usp=sharing
-
@Darshit-Desai Our m500 also showed something needed to be done with the acutator after updgrade to 1.14. But after loading the parameters (assuming you are using fcv2) and then reboot and it is okay.
p.s. I vaguely rember having to do "loading parameters and rebooting" twice to get everything done. But I'm not very sure about this just I have this impression.
-
@coreyazion @tom This didn't work for me, although the drone esc and the drone functionality overall does work on an older sdk and flight core params, so its the newer version that's causing bugs for me
-
@tom any updates on this?
-
@tom any update on this?
-
@Darshit-Desai Can you try the v1.13 PX4 for the Flight Core? https://docs.modalai.com/flight-core-v2-firmware/
