Developers

No mystery DLL.

Asynchronous. Cancellable where physics allows. Strongly typed and versioned. Observable, with explicit timeouts, transaction IDs, connection generations, structured errors and machine-readable diagnostics. And a developer should be able to move one axis within minutes.

C
C++
Python
.NET
Rust
LabVIEW
MATLAB / Simulink
ROS 2
EPICS
OPC UA
IEC 61131 / PLCopen

# illustrative — the concept, not a frozen syntax
z = machine.axis("Z")

tx = z.move_to(
    84.650,
    frame="HOLDER",
    profile="precision"
)

result = await tx.verified()
assert result.motion_proven

state = await machine.snapshot()
state.frame.trust                      # VERIFIED
state.axes["Z"].position
state.axes["Z"].position_provenance

Simulation first

Test the machine software before the machine exists.

Every KineticON machine project runs against the real controller or the KineticON virtual controller — through the same API. The virtual controller models axes, limits, drives, frames, I/O, brakes, faults, communications and geometry, and hardware-in-the-loop follows on the same path.

That means a link drop, a failed read, an encoder discontinuity or a brake that will not release can be rehearsed in a test suite, long before it happens at three in the morning on a real gantry.

Same API

Real or virtual

Swap the endpoint, not the code.

Faults on demand

Rehearse failure

Inject communication loss, sensor faults and brake faults deterministically.

Geometry

Collisions in software

ToolSafe previews run in simulation exactly as on the controller.

HIL

Hardware-in-the-loop

Real drives against a simulated plant, when the project is ready.

CONTROLGRAPH · DISPENSE CYCLE● STATIC CHECK

VERIFY FRAME · holder rev 4
RAISE Z · to safe height
MOVE XY · validated by ToolSafe
VERIFY STATIONARY
LOWER Z · needs VERIFIED frame
PROCESSSYNC EVENT · dispense
RETRACT
TRANSACTION COMPLETE

Dependencies explicit, brake order legal, frame present, geometry clear, outputs owned once. The graph is accepted.

ControlGraph™ · declarative deterministic actions

Wrong programs are refused before anything moves.

Complex machines outgrow primitive scripting. A ControlGraph is a declarative action graph with explicit dependencies, where parallel safe actions run concurrently — and the whole graph is checked statically before execution for impossible dependencies, an unsafe brake sequence, a missing frame, forbidden geometry, a missing device and conflicting output ownership.

Graphs that pass can be sealed into a signed Motion Capsule that the controller validates and owns.

Digital commissioning

One cryptographically identifiable machine manifest.

A machine definition is portable: the controller configuration, drive, motor and encoder identities, frame and tool definitions, AxisDNA, the safety configuration, firmware hashes and motion-program versions — bound into one machine manifest. If the hardware changes, KineticON knows the machine definition changed.

KineticON Studio

One environment

Discover, configure, identify drives, characterise, tune, build frames and geometry, configure safety, build ControlGraphs, inspect MotionProof and ShadowTwin, analyse vibration, compare sessions, manage firmware, export evidence.

Visual tools

See the machine

Real-time oscilloscope, Bode plots, FFT, trajectory and 3D geometry viewers, collision preview, timing traces, EtherCAT health, MotionProof timeline, FrameProof graph, AxisDNA fingerprint, thermal and current/torque maps.

Not Windows 95

Spectacular on purpose

Engineering software people want to open — because the tool you commission with shapes how well a machine is understood.

Documentation · licensing · price

Make engineers feel they own the controller they bought.

Documentation for adults

Protocol documentation, SDK docs, state machines, timing behaviour, error semantics, examples, recovery behaviour, firmware notes and compatibility tables. No hidden error numbers. No “contact sales to learn whether the feature exists”. If something has a limitation, the limitation is documented.

No crippled hardware

Commercial tiers may differ in hardware capability. What never happens is selling a high-performance controller and then demanding another licence to use a basic filter or an extra API language.

No artificial scarcity

High-end motion systems become expensive after the controller, software, optional algorithms, drives, I/O, cables, licences and integration. KineticON attacks total cost with modern electronics, integrated function, open drive choice, simpler commissioning, fewer modules and fewer paid software fragments.

Serious motion control does not need artificial scarcity.

Frequently asked

Frequently asked questions

Which programming languages does KineticON support?

C, C++, Python, .NET and Rust, with LabVIEW, MATLAB and Simulink where appropriate, ROS 2, EPICS, OPC UA and IEC 61131 / PLCopen interoperability.

Can I develop without hardware?

Yes. The KineticON virtual controller exposes the same API as the real controller and models axes, limits, drives, frames, I/O, brakes, faults, communications and geometry, so machine software can be written and tested before the machine exists.

What is a ControlGraph?

A declarative graph of machine actions with explicit dependencies. It is statically checked before execution for impossible dependencies, unsafe brake sequences, missing frames, forbidden geometry, missing devices and conflicting output ownership, and safe parallel actions can run concurrently.

What is a machine manifest?

A cryptographically identifiable record of a machine’s definition — controller configuration, drive, motor and encoder identities, frames, tools, AxisDNA, safety configuration, firmware hashes and program versions — so any hardware change is detected as a change to the machine.

Is the example code the final API?

No. The examples illustrate the concepts — transactions, verification and provenance — and do not constrain the future syntax of the SDK.

References

Sources

Motion integrity →What the API is verifying. Machine intelligence →AxisDNA, ShadowTwin, QuietHold. Platform →Back to KineticON.

This week in the field

11 – 17 September 2026

Newest PubMed records in robotic manipulation, automated laboratories and precision control — refreshed weekly. Listing only; inclusion is not endorsement.