RC QUICKCAL UPDATE
RC QUICKCAL REGISTRATION
RC QUICKCAL CODE

GPS signal was weak in certain regions, searching for options of using BeiDou to supplement.Q.6 : Using the BeiDou satellite network - Tony USE CASE : Trying to command the Servo’s position for a whole 1 minute, when reaching a mission point (item).Q.5 : MAV command for Mission Item doesn’t have timing information This can be documented better - OR, get a smart battery.Much better to use ‘current’ reading, to know how much power drone has consumed.By default, the compensation is done by battery voltage & estimated thrust.Q.4 : Battery load compensation for load-carrying aerial vehicle - Safy

RC QUICKCAL UPDATE

shares that there is a C++ firmware update class in PX4 within the PX4IO uploader class: PX4-Autopilot/px4io_uploader.cpp at master.

Besides the uploader script, the only other thing that comes to mind is QGroundControl.

will be putting together a PR in the near future to add better error handling/feedback to improve this, and will also be creating a standalone C++ lib+app for performing firmware updates, specifically for offboard compute driven firmware update use-cases.

warning message about modem-manager apparently regardless of if it’s installed or not.

Seems like the uploader has issues getting the Px4 into BL (retries a few times).

Chris Seto also reported flaky behaviors through their experience flashing targets 10+ times a day.

Example: if pyserial is not installed, creation of the uploader object fails, but the exception is silenced and a retry occurs indefinitely

Many exceptions are silenced at the “Waiting for bootloader” stage.

Q.3 : Alternatives to the px_uploader.py script for flashing firmware - The current script seems to exhibit some flaky behaviors in triggering reboots into bootloader mode and failure to report explicit error messages in many situations

RC QUICKCAL CODE

and suggest that there is the opportunity to unify the GPIO initialization process and share the same code between the application and bootloader, at least in the case of in-tree bootloaders, such as for the H7-based boards.

See: PWM outputs go high for ~500ms on boot

The bootloader (at least for some boards) does not share this initialization logic, nor does it have access to some of the timer channel configuration helpers/utility methods/classes due to being a C target, so to achieve the same safe GPIO init, a clumsy, hand-coded duplication of the init logic can be performed.

Q.2 : Bootloader GPIO Initialization - In order to get safe/deterministic initialization of PWM (and other GPIO) outputs that avoid unintentional actuation under certain conditions, a PX4 application needs to safely initialize those GPIO during board init.

You can however customize the rate freely!.

Current rate is a NuttX Default (57600), but probably won’t be updated since it’s dependent on NuttX.

Q.1 : Debug Consoles baud rate is quite low, why?

The Dev Summit will be happening at the same time with other Linux Open Source Events!Ĭommunity Q&A (No deep technical discussions).

Call For Proposals (CFP) | Linux Foundation Events.

RC QUICKCAL REGISTRATION

CFP registration deadline extended till the end of Friday (April 22nd) this week!.No deep technical discussions during the first 45 minutes of general call.

Rc quickcal