DEVELOPERS

A familiar loop. A much bigger canvas.

Initialize in setup(). Keep the process moving in loop(). Connect native controls, device events, and application data in one readable program—from a machine HMI to a network of automation stations.

DRAW IT. CONNECT IT. MAINTAIN IT.

Your screen and your logic, together.

Create labels, buttons, sliders, digital readouts, and G-code viewers with JetFlight’s native UI. Bind a button to an event, a reading to a label, and device data to your process state. No separate JavaScript installation or browser front end is required.

The layout is defined in your script. Keep device adapters, process logic, and configuration in small modules so the next change stays understandable.

Build a native sensor HMI →

var label;

function setup() {
    var screen = ui.screen();
    label = ui.label(screen, 'Ready');
    ui.setPos(label, 24, 24);

    var button = ui.button(screen, 'Inspect', function() {
        ui.setText(label, 'Operator requested inspection');
    });
    ui.setPos(button, 24, 80);
}

function loop() {
    // Check state. Update readings. Keep each pass short.
}

One station—or a connected process.

Run headless near the equipment, add an operator screen where it helps, and exchange data through supported Ethernet or USB interfaces. Sensors, test fixtures, production cells, and larger plant applications can share a consistent application structure.

Follow the three-station example →

Boot straight into your HMI.

Package your scripts and assets into a JetFlight application, then launch it through an OEM startup script on a dedicated JC3 Appliance control computer. Or use JC3 itself for CAD, CAM, simulation, and control at the machine.

Explore dedicated controls →

COMPILED OEM APPLICATIONS

Deliver the application. Keep your source.

Your HMI, process sequences, and device integration can remain proprietary. JetFlight compiles your scripts into a single .jfpkg application, so customers receive a runnable package without your original readable source files.

Keep developing in your private project and deliver compiled updates to the machine. Bytecode provides a barrier to casual source inspection and reuse; it is not encryption or a guarantee against reverse engineering.

Build and distribute a closed-source application →

STARTER APPLICATIONS

Build from a useful starting point.

HMI and peripheral starters will be open source with commercial reuse. The daemon and core firmware remain closed source and free. The cards below show which starter packages are still being prepared.

Preparing for release