Machine interfaces

Mixed drives and encoder feedback

Choose each motor's command and feedback path without forcing the whole machine into one drive type.

RuntimeSteadyWin integration in development
FirmwareExact driver and protocol required
HardwareDirect encoder interfaces are board-dependent

A machine may have step/direction steppers on one axis, servos with retained amplifiers on another, and CAN-connected motors elsewhere. JetFlight's machine definition maps physical joints to logical axes; the interface for each joint determines how commands reach the motor and how feedback returns.

Command and feedback are different choices

ArrangementCommand pathWhere the loop closes
Step/direction stepperPulses from a controller to a driverMay have no position feedback
Step/direction servoPulses from a controller to a servo driveThe servo drive usually reads its encoder
Conventional servo with direct feedbackA compatible controller commands the amplifierThe controller reads the encoder; suitable hardware and firmware are required
SteadyWin CAN motorDevice-specific CAN messagesCommand and motor feedback use the implemented SteadyWin protocol

A servo accepting step/direction is still a step/direction interface. Its encoder does not automatically become controller-side position feedback. In a retrofit, identify the amplifier's command input and the encoder interface separately before deciding what can be retained.

SteadyWin CAN development

SteadyWin CAN control has been implemented and tested in development. The inspected integration targets the GDZ810 / GIM8108-6 motor family and allows step/direction and SteadyWin CAN joints within one controller definition.

This is device-specific development evidence, not a promise that every SteadyWin model or every CAN motor works. Match the exact motor protocol, controller, firmware, and runtime before commissioning. Public release availability is tracked separately from the development test.

Planned integrations

Additional Teknic integrations and other drive protocols are planned. Identify the actual drive model and protocol rather than selecting a manufacturer name as an electrical interface. A model that already accepts step/direction belongs in that command category; Teknic documents this interface for its ClearPath-SD family. This identifies the interface, not a commissioned JetFlight pairing.

Direct analog commands and controller-side encoder feedback depend on the planned industrial interface hardware and its validated firmware. Retaining original servos, amplifiers, and encoders is a key retrofit goal; it is not a universal drop-in compatibility claim.

Record one row per motor

For each joint, record its logical axis, controller location, drive model, command method, feedback source, units, and limits. A dual-motor gantry has two physical joints even if the operator sees one axis. The distributed architecture shows why controller location and logical-axis assignment are separate decisions.

The build guide accepts multiple drive and feedback selections. Choose every arrangement on the machine; all of them must be supported for the final configuration.

Reviewed 2026-11-06. Confirm the hardware catalog and current published release before connecting a machine.