Topics created by alarm_hq

@tom After playing around with CP_DIST, it seems any value > 0 causes position mode to no longer want to allow x/y translation. From what I understand, any value < 0 disables object avoidance. Is this true?

As far as I'm aware, my settings should be in parity with Modal provided guidance in regards to seeker setup with additional configurations overridden to support voxl-mapper.

Thanks for the stabilized advice @mohammednaveed, I've gone as far to replace manual mode with this setting.

Hello @alarm_hq!
Please see the updated readme on voxl-mapper's dev branch for an overview guide of this package. As for the timestamp too new error, this error typically arises when there is a VIO blowup, and one way to prevent this is by ensuring that the tracking camera is correctly calibrated pre-flight. Also, please see the overview guide for instructions on viewing, as RVIZ is no longer utilized!

Hey @alarm_hq! The props for the Seeker development drone can be found here.

@alarm_hq said in How to: Seeker ESC calibration:

And if I've already made the "mistake" of reflashing px4 firmware, is the closed loop RPM control affected?

The ModalAI ESCs used on Seeker have their own firmware and settings stored on the ESC itself, independent from PX4 so your ESC is fine after changing PX4 firmware.