Receiver FastBoot Guide

This guide will go over the functionality of FastBoot, and how it’s behavior varies between receiver platforms.

Supported Devices

Receivers

Supported receivers include the following (with firmware 3.4.0+)

Power Cycle Time Based

• AR630

• AR631

• AS6420A

• AR637T

• AR637TA

• AR8360T

• AR10360T

Intentional Shutdown Based

• AR10410T

• AR14410T

• AR20410T

FastBoot Detection Types

Power Cycle Time Based

This method of FastBoot detection is dependent on how long the device is left off before powering on again. This amount of time can be dependent on external devices connected which might extend this time window (such as extra capacitance or power). The approximate shutdown time required is listed in the categories below.

If the entire model setup prevents this feature from working properly, it can be disabled in Forward Programming > Other Settings > FastBoot.

Category 1

Approximately 5s to 10s of shutdown time required (can be longer dependent on setup).

• AR630

• AR631

• AS6420A

• AR637T

• AR637TA

• AR8360T

Category 2

Approximately 2s to 3s of shutdown time required (can be longer dependent on setup).

• AR10360T

Intentional Shutdown Based

This method of FastBoot detection is dependent on whether the user properly/intentionally shutoff the receiver before it is powered on again. This has the benefit on not requiring the device to be left powered off for a given time period before powering on again. However, the device must be properly shut off before disconnecting power/batteries from it.

• AR10410T

• AR14410T

• AR20410T

Behavior after a FastBoot

When a FastBoot happens, there are a few behaviors to keep in mind. These are all reasons you’d want to make sure the system boots properly on the ground before takeoff, as it is intended to help keep the model flying if there are hardware failures in flight.

• Servos initialize immediately instead of waiting for radio channel data to fully populate. This could cause servos to jump on startup.

• Uses a previous gyro calibration instead of a new one. This could lead to drift, particularly in SAFE mode.

• Skips servo startup dance indicating whether AS3X and/or SAFE have been configured.

• SAFE will still initialize, but starting attitude estimation might be off initially.

• If AS3X Throttle Arm is enabled, it will be skipped.

• Spektrum programmer check is skipped

• XBUS sensors are disabled (for supporting receivers

• Vario/Altimeter disabled (for supporting receivers)

• Onboard sd card data logging disabled (for supporting receivers)