Skip to content
PreciSim
First release in preparation

Run the whole HMI with nothing plugged in

PreciSim is an HMI for precision motion and 2D vision machines with a virtual device engine built in. Install it, open the camera view, jog three axes and run all seven calibration chains, each one checked against the ground truth inside the engine.

Windows 10/11 · no hardware required · free edition never expires

LIVEPreciSim · demo-xy-galvo · SIMCAM0 · 4096×3000µm/px 1.7251Δ 0.0015 PASSGALVO field correction · residual ×40X12.4210Y-36.0035Z112.3470preparescanfit[10:24:11] chain=pixel_size step=scan n=9/9[10:24:13] solve: µm/px=1.7251 rotation=-0.81°[10:24:13] truth: µm/px=1.7236 rotation=-0.80°[10:24:13] deviation 0.0015 µm/px → PASS (tol 0.002 µm/px)
A trace recorded by the engine, which you can orbit with the mouse. In the app this view updates live with the axes.
Live demo →
01 / 08

This is what opens

Screenshots of the software running.

An HMI in industrial form
01

An HMI in industrial form

Software teams at machine builders · engineers learning HMI work

Four roles: guest, operator, engineer, administrator. The main page shows the connection state of seven device types and the axis positions. Alarms have a popup and a history; logs, manual jog, and signal and fault injection each get their own page.

A machine with nothing wired up
02

A machine with nothing wired up

New hires without hardware · students · training providers

Camera, three axes, galvo, laser, rangefinder, lighting and 22 IO points, all virtual. Camera frames are rendered per exposure, gain, depth of field and noise; axes carry pitch error and repeatability, so the reported position is never the true one.

Seven calibration chains scored against truth
03

Seven calibration chains scored against truth

Vision engineers

The calibration centre runs all seven chains in dependency order. Each chain ends with measured value, true value, deviation, tolerance and verdict, with the residual plot and the history kept for review.

02 / 08

Camera frames are computed from physics

Defocus turns depth of field into a blur radius, exposure scales the signal while the noise stays put, and the same seed reproduces the frame byte for byte. Both series below were captured from the engine by a script, with the full frame on the left and the central 320 pixels enlarged on the right. Use the slider to switch steps.

Defocus · Z lifted off the focal planeIn focus
Exposure · less light, more visible noise8000 µs

Frames come straight from the engine, the same image stream the camera page in the app receives.

03 / 08

Seven calibration chains, each ending with a deviation

The calibration centre runs them in dependency order, and any one can be re-run on its own.

① Pixel size

pixel_size

µm/px in X and Y, axis rotation, non-orthogonality, residual RMS.

② Camera to actuator offset

cam_actuator_offset

(Δx, Δy) from the camera centre to the laser or probe landing point.

③ Lens distortion

lens_distortion

k₁ / k₂ from a dense circle grid, reprojection residual RMS.

④ Nine-point / hand-eye

hand_eye

Affine transform and residual between commanded and vision-measured positions.

⑤ Galvo field correction

field_correction

The galvo marks a grid across the field (11×11 by default), each point is measured; reports max error before, residual after, field coverage.

⑥ Laser focus

laser_focus

Sweep Z for the smallest spot diameter.

⑦ Camera focus

camera_focus

Sweep Z for the sharpness peak; tolerance one notch looser than laser focus.

Id · Steps · Prerequisites · RunAsync

All seven chains implement one interface: each declares its steps and prerequisites and returns a result, so the wizard, progress, cancel and archive are shared. In the algorithms source, PixelSizeProcedure.cs is the template.

Source guide →
04 / 08

The engine is closed. The model is not.

Why trust numbers from a virtual device? The six imaging steps, axis errors, defocus, noise, and the definitions of truth and tolerance are all written out in the docs. Open formulas, closed implementation: anyone who can follow the maths can check it. On the right are the error sources injected into the sample machine; turn them up, rerun, and watch how they reach the calibration results.

Read "Physics and models"
Injected error sourcesdemo-xy-galvo
X pitch error0.8µm50 mm period
Y pitch error0.6µm40 mm period
Repeatability0.2µmX / Y
Axis readout noise0.5µmGaussian σ
Image noise3.0grey levels, Gaussian σ
Range finder noise0.8µm
Camera depth of field0.17mmsets the defocus blur radius
From machines/demo-xy-galvo.json, which ships with the software. Turn them up and rerun.
05 / 08

What it solves

A new hire has no machine

The virtual machine is always available. A bad calibration crashes nothing, and error parameters can be turned up until the consequence is visible.

A calibration result has nothing to compare against

The virtual device knows the truth, so every chain ends with a deviation and a verdict.

Every new machine means a new HMI

Device interfaces, the Station/DAG workflow and the calibration chains are the shared layer. A new machine changes configuration and device implementations.

Debugging only happens on site

Get the logic right against virtual devices first. On site, only the difference between real hardware and virtual remains.

06 / 08

Source is a one-time purchase, updates have no end date

After payment your Git account is added to the private repository as a read-only member, and every later version is a git pull away. Updates have no end date.

See source pricing
  • The repository invite is sent automatically after payment
  • The repository builds from a clean clone, with nothing from our environment
  • A source guide tells you which file to read first
08 / 08

Frequently asked

What does the free edition do, and does it expire?

The free edition includes the complete virtual machine, every machine model, all seven calibration chains and every lab. It never expires and needs no account. Physics, precision and ground truth are identical to the professional edition; the difference is the external interfaces and the commercial licence. The free edition is for personal learning and evaluation; for use at work, buy the professional edition.

The engine is closed source. How do I know the numbers are right?

The docs contain a full "Physics and models" chapter: world and imaging, axes and errors, optics and defocus, noise, ground truth and tolerances. Open formulas, closed implementation. Check the arithmetic yourself.

If I buy the source, do future updates cost extra?

No. Pay once, and every future version is a git pull away.

Our lab network has no internet. Can we still use it?

Yes. Offline activation turns a machine code into an activation code with no network involved, and a failed online check carries a 30-day grace period, so an outage on our side does not stop a class.

What if I change computers?

Paid licences count machines: three for the professional edition or a single source package, five for both source packages. When you switch computers, deactivate the old one yourself from your account. The free edition needs no activation.

Does it work with real hardware?

The device layer is an abstraction: virtual and real devices implement the same interfaces. Once the logic works against virtual devices, going to real hardware means swapping device implementations and configuration. The real-device implementations are placeholders today, so you write that layer for your own hardware.

Finish the first lab

Thirty minutes, no hardware, and a real deviation number at the end.