Skip to main content

Current

Up-to-date board documentation following the current format.

📄️ Current Sensor Calibration

Some boards include a current sensor in order to provide measures such as "Battery current draw", "Battery mAh drawn" and others. More often than not, the current sensor has to be thoroughly calibrated for the measures to be accurate. Also, Betaflight includes a Virtual Current Sensor feature that can be used when the current sensor is missing or broken. This sensor needs a different calibration procedure to be performed in order to provide reasonably accurate measures. The Betaflight documentation includes very valuable advice on how to calibrate both sensors: Battery

📄️ OSD Profiles

An OSD Profile is a screen or page of OSD elements. Three OSD Profiles are supported, i.e. you can configure 3 different OSD Profiles or pages each with their own OSD elements. Elements may also be on all 3 profiles. The OSD can still be turned on or off as before via an AUX channel. Hence users who don't want this feature are not affected by its availability. With no profiles are configured for elements, all elements are visible, i.e. OSD Profile 1 is the default profile. Keep in mind that if an element is used, it must be in the same position on all OSD Profiles in which it is visible. It is not possible to configure an element to be in a different location on a different profile.

📄️ SBus FPort and Open Tx

OpenTX has the problem that it fails to fully utilise the hardware that FrSky sells for SBus and FPort (called 'D16' in OpenTX terminology). As a consequence, on FrSky hardware that is perfectly capable of supporting 4 RC channels and up to 12 switch channels with an update rate of 9 ms, OpenTX (up to and including version 2.2.3 at least) only supports an update rate of 18 ms for the RC channels. To make matters worse, it does this by sending RC frames to the flight controller at intervals of 9 ms, but sends identical RC data for each pair of consecutive frames.

📄️ USB Flashing

Some newer boards with full USB support must be flashed in USB DFU mode. This is a straightforward process in Configurator versions 0.67 and newer. The standard flashing procedure should work successfully with the caveat of some platform specific problems as noted below. The "No reboot sequence" checkbox has no effect as the device will automatically be detected when already in bootloader mode (a DFU device will appear in the connect dropdown if this is the case). The Full chip erase checkbox operates as normal. The baudrate checkbox is ignored as it has no relevance to USB.