rcbench
Servo and ESC test bench: panel, IOmcu and shared C
Loading...
Searching...
No Matches
arming_hs_facts_t Struct Reference

What the panel learned for the arm since the last point. More...

#include <arming.h>

Data Fields

bool link_up
bool port_taken
bool release_owed
bool rate_settled
 The rate the surfaces run at is known.
bool disarm_asked
bool endpoints_blocked
 The throttle's pulse endpoints are not known to be in force at the far end: owed (an edit, a binding or a link-up not yet paid, or a write nobody answered) or blocked by the last answer (refused, or another pair stored); see endpoints_block().

Detailed Description

What the panel learned for the arm since the last point.

Field Documentation

◆ disarm_asked

bool arming_hs_facts_t::disarm_asked

a disarm is posted and not yet delivered

◆ endpoints_blocked

bool arming_hs_facts_t::endpoints_blocked

The throttle's pulse endpoints are not known to be in force at the far end: owed (an edit, a binding or a link-up not yet paid, or a write nobody answered) or blocked by the last answer (refused, or another pair stored); see endpoints_block().

The frame that arms carries no CHAN_CFG.

◆ link_up

bool arming_hs_facts_t::link_up

the control loop holds the link as up

◆ port_taken

bool arming_hs_facts_t::port_taken

the servo programmer has a port or an operation under way

◆ rate_settled

bool arming_hs_facts_t::rate_settled

The rate the surfaces run at is known.

Asking can take an exchange; read only at ARMING_HS_PREPARED with the link up and no release owed, and the caller need not ask otherwise.

◆ release_owed

bool arming_hs_facts_t::release_owed

a servo release the far end has not taken


The documentation for this struct was generated from the following file: