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

Data Fields

panel_cmd_kind_t kind
motor_cmd_t motor
servo_cmd_t servo
outbind_t bind
supply_cmd_t supply
uint32_t stops
uint32_t lets_go
uint32_t supply_offs
uint32_t pdmini_edits
uint32_t loss_gen
uint32_t consumed_seq

Field Documentation

◆ bind

outbind_t panel_cmd_t::bind

PANEL_CMD_OUTPUTS: the protocols and their pins

◆ lets_go

uint32_t panel_cmd_t::lets_go

And how many times it had been told to let go; see s_lets_go.

◆ loss_gen

uint32_t panel_cmd_t::loss_gen

And what the render side knew of the touch stream when it queued this: how many times it had dropped the screens' gestures for a loss (s_loss_gen), and the number of the last event it had taken off s_touch_q. An arm completes a hold, and a hold that completed on a contact whose events went missing is an arm the operator may not have made. The render side cancels what it still holds when it finds a loss, but an arm already handed over is past its reach, so the control task compares these when it takes the arm and watches it until the render side has seen the bench armed; see touch_loss.h. Only an arm: a loss makes no throttle or position suspect, and a disarm is never dropped.

◆ pdmini_edits

uint32_t panel_cmd_t::pdmini_edits

And how many edits the PD mini's wiring had had (s_pdmini_edits): an ON queued before an edit on SETUP is not applied after it, even one undone since.

◆ stops

uint32_t panel_cmd_t::stops

How many stops the sender had seen when it queued this.

The queue and the stop latch cross between the two tasks independently, so an arm can be queued from a gesture the sender watched, and a stop be applied before that arm is drained: the arm would then clear a latch that was set after it was asked for. An arm carrying a count that is no longer current is out of date and is dropped.

◆ supply

supply_cmd_t panel_cmd_t::supply

PANEL_CMD_SUPPLY: set points and the switch

◆ supply_offs

uint32_t panel_cmd_t::supply_offs

And how many times the supply's output had been asked off; see s_supply_offs.


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