DOCUMENTATION
Build from known interfaces.
Every guide states which runtime, firmware, and hardware evidence it describes. Architecture targets stay visibly separate from released configurations.
How JetFlight is structured
Host planning, machine-side timing, native applications, and expandable machine I/O.
Getting startedStart with simulation
Prove the program, machine definition, and operator workflow before connecting physical hardware.
Getting startedDedicated controls with JC3 Appliance
Boot into full CAD, CAM, and control—or into your own packaged JetFlight HMI.
Machine planningRetrofit inventory
Identify what the machine already has before deciding what to replace.
HardwareConnecting supported hardware
How compatibility is published and why the board revision matters.
Machine interfacesMixed drives and encoder feedback
Choose each motor's command and feedback path without forcing the whole machine into one drive type.
Machine planningDistributed machines
Place control near the joints and I/O instead of routing every signal to one cabinet.
DevelopersNative HMI and scripting
Create the screen, connect its events, and keep your process logic readable with setup() and loop().
DevelopersConnected automation with setup and loop
Bring devices, process logic, and native operator screens into one maintainable application.
DevelopersProprietary applications with .jfpkg
Deliver your machine's HMI and process logic as a compiled application while keeping your source private.
DevelopersI/O and peripheral extensions
Add non-motion machine functions through reviewed Ethernet and USB integrations.
SupportTroubleshooting and evidence
Separate software behavior, compatibility, wiring, and physical commissioning evidence.