One of the most common questions we get is: “Is JasperNode fast enough for my application?”
The answer depends on your Cycle Time requirements.
JasperNode is architected to prioritise connectivity (IT/OT convergence) and logic complexity over microsecond execution speed. It replaces the indiscriminate cyclic scan of a traditional PLC with an event-driven model.
The Suitability Matrix
We categorise industrial applications into four tiers to help you decide where JasperNode fits.
Tier 1: General Industrial & Building (>500ms)
-
Status: Excellent Fit
-
Examples: HVAC, Lighting control, Energy monitoring, Data logging.
-
Why: These processes are slow-moving; sub-second latency is perfectly acceptable.
Tier 2: Process Control (>50ms)
-
Status: Excellent Fit (Soft Real-Time)
-
Examples: Water treatment, Chemical mixing, Tank level management.
-
Why: Fluid dynamics and thermal processes generally do not require millisecond precision.
Tier 3: Discrete Automation (5–20ms)
-
Status: Supervisory Fit
-
Examples: Conveyor systems, Assembly stations.
-
Why: Use JasperNode for the high-level logic (e.g., “If batch is complete, send data to ERP”), but keep high-speed sorting sensors on a dedicated microcontroller or PLC.
Tier 4: Motion & Safety (<1ms)
-
Status: Not Suitable (Hard Real-Time)
-
Examples: Robotics, CNC, Synchronised optical sorting.
-
Why: These require deterministic execution at the microsecond level, which is outside the scope of the current runtime engine.
Source: JasperX - How it works