Project

General

Profile

Actions

Configuring Inputs

An input brings a value into the controller — from a physical pin, the CAN
bus, or computed from other inputs. Every input shares the
Common IO Settings; each type adds its own options.

Inputs fall into three groups.

Physical (hardware-pin) inputs

Input Reads Page
Analog Input Analog voltage on a pin Analog Input
Digital Input On/off (shorted to sGND) with debounce/invert Digital Input
Frequency Input Frequency, speed, duty or pulse time from a pin Frequency Input
Analog Switch Input Resistor-ladder / voltage switch Analog Switch Input

Communication inputs

Input Reads Page
CAN Bus Input A signal from a raw CAN frame CAN-Bus Input
CAN Object Input A named object provided by a CAN Preset CAN-Object Input

See Working with the CAN Bus.

Computed / logical / virtual inputs

Input Produces Page
Constant Value Input A fixed value Constant Value Input
Compare Input A boolean (1024 / 0) from a comparison Compare Input
Math / Divide Input Maths between two inputs Math Input
Map Input 1D lookup on another input Map Input
Mux Input Selects 1 of 8 inputs Mux Input
Counter Input Up/down/reset counter Counter Input
Waveform Input Time-based generated signal Waveform Input
RBC Input Decodes Gray code from a set of bit inputs RBC Input
Virtual Input Value set from the datalogger (USB sliders) Virtual Input
System Input A system value, selected by pin System Input

Not documented here: Test Input and AHRS Input (developer/diagnostic), Current
Sense Input (diagnostic), QEI Input (diff-controller only), and the internal
template-only types Gear Ratio Calculator and Clutch Slip Counter. Duty
measurement is covered by the Frequency Input (Duty mode), and the legacy
standalone Frequency/Duty inputs are folded into it.

Updated by Adam Klama 1 day ago · 3 revisions