ModalAI Forum

@Alex-Kushleyev Dear Alex, It's the M0025-002 high resolution camera. Perhaps the connection sodder was loose and it popped off real easily. In hindsight, perhaps it's not worth anyone's time. If you can provide any repair tricks that'd be neat otherwise I'll probably have to send a new order in. Best, Milton

@smilon The parameter EKF2_REQ_SACC sets the maximum allowable speed accuracy. If you increase that value does the warning go away? Can you post a log?

Did the trick btw

@jacob-yaacubov , FYI, this fix will be in 1.2.0 release which is in testing now

@smilon said in Custom px4-firmware build on StarlingV2: I ran into an issue while installing the newly built voxl-px4 which states it depends on libfc-sensor(>=1.0.5) and I only have (1.0.4) on my system. @Eric-Katzfey I saw you authored some commits on libfc-sensor-api, do you have any clue how I can update? 1 Reply Last reply about 3 hours ago Reply @smilon I would recommend using ros2 wrapper around mavsdk instead of mavros, that is what we have done in the past as mavros and ros1 are both depricated and not supported anymore. Anyways, goodluck with the project!

Ok, in a stroke of epipahny I realised that when switched to offboard mode through ROS2, the drone attempts to do both the modalAI "figure eight" that was configured in /etc/modalai/voxl-vision-hub.conf and satisfy the TrajectorySetpoint given to it by ROS2, resulting in this very jerky motion. Switching offboard_mode parameter to "off" solved this issue!! Works flawlessly now. Any ideas how I can switch off passing the local odometry to PX4 and pass /vvhub_body_wrt_fixed instead? If I just publish to /fmu/in/visual_vehicle_odometry does it only take input from the publisher or will it publish from both sources similar to the offboard mode example? :)))

@Alex-Kushleyev I ran voxl-configure-mpa and was able to get the ESC to function again. Of course it caused other issues due to resetting files and params so I am now trying to work through setting everything back up. Im not sure what would have caused the mpa to need to be reconfigured because I had just done that obviously with the flash of SDK 1.1.2.

Ok final update and case-closed...it was a USB-C issue! Even though I was most of the times able to discover my device, I was never able to discover it when in fastboot mode. Whenever anybody is facing such issues always switch to another USB-C cable first...

@smilon Yeah that's worth a try. You can also pull the calibration files off before performing a factory reset by locating them in /data/modalai and from host running adb pull /data/modalai/* . and then pushing them back on after