MACHINE CONTROL, WITHOUT THE OLD LIMITS
Built around your machine.
Build something new. Bring an existing machine forward. Start with the control you need and expand as the machine grows.
MotionFeedbackMachine I/OApplicationsALREADY INSIDE JETCAD3
The engine behind your simulation.
Ready for your machine.
If you have JC3 installed, you already have JetFlight. Every JC3 motion simulation runs through its motion engine, respecting configured velocity and acceleration limits so the preview shows how axes build speed, move, and slow down.
Deploy the same runtime independently for a native HMI or custom automation. A compact native executable for Windows, macOS, or Linux keeps the motion and scripting engines together.
From simulation to machine control →CHOOSE THE WORK IN FRONT OF YOU
A control path that starts with the machine.
JetFlight does not force every build through the same breakout board. Start with what the machine needs—or what it already has—and match the interfaces from there.
Keep the machine.
Modernize the control.
Retain motors, amplifiers, encoders, and machine wiring when a validated interface can use them.
Inventory a retrofit →Start compact.
Expand deliberately.
Build a simple machine around one controller, or prepare a large machine for distributed control.
Plan a new machine →Add the I/O
the process needs.
Use familiar setup/loop scripts to connect supported devices, process logic, and native operator screens—from one sensor station to a coordinated automation project.
Plan an automation project →JC3 APPLIANCE · DEDICATED MACHINE CONTROLS
Power on.
Get to work.
Build a dedicated operator station around JC3 Appliance. Choose a complete CAD/CAM/control workstation or boot straight into your own JetFlight machine interface.
JC3 at the machine
Design the part, prepare the toolpaths, simulate the motion, and operate the machine from one HMI. The standard Appliance starts directly in JetCad3, with JetFlight already included.
Explore the integrated control →Your machine. Your HMI.
Use an OEM startup script to launch a packaged native JetFlight HMI. Operators arrive directly at your process screens, controls, and branding, with the runtime behind them.
Build an OEM operator station →ONE ARCHITECTURE, DIFFERENT MACHINES
Control where the work happens.
The host plans the work. Machine-side hardware handles timing-critical motion. The architecture can grow from one compact controller toward nodes placed near distant joints and I/O.
AVAILABLE ARCHITECTURE
One host. One controller. A clear starting point.
A compact plasma or router keeps JetFlight on the computer and puts motion plus machine I/O on one controller near the cabinet.
JetFlight has made first cuts with prototype hardware. The retail V2 combination is still commissioning.Operator
JetFlight host
Motion controller
Drives + I/O