Embedded Files
In 3 bullet points
JasperNode is software installed on any PC. It uses the Ethernet connection to read and write the industrial Input/Output (I/O) devices.
Like a traditional PLC, JasperNode has an execution cycle. However, it slightly differs: it reads inputs, checks for changes, executes the logic of changed tags only and then writes to the outputs.
The I/O data can be from OT or IT connections: JasperNode can read data from an EtherCAT device and write to a MQTT broker, and vice versa.
Hardware Connection
🙋♂️ NEED HELP? Having difficulties selecting hardware?
Email us at hello@jasperx.com.au and we will help.
Engineered for 80% of Industrial Use Cases
Engineered for 80% of Industrial Use Cases
JasperNode is architected to prioritise connectivity, logic complexity, and ease of development over microsecond speed. This design choice makes it the ideal controller for the vast majority of industrial applications, while clearly defining where it acts as a supervisory layer rather than a primary motion controller.
We categorise suitability based on the strictness of the application's timing requirements:
The Takeaway JasperNode covers the Tier 1 and Tier 2 applications that make up the bulk of facility automation. For high-speed Tier 4 motion control, we recommend maintaining your existing specialised hardware while using JasperNode to handle the supervisory data, IT integration, and overall process logic.
Supported Protocols (Connectors)
Supported Protocols (Connectors)
JasperNode supports several Industrial and IT Protocols to connect to hardware and your software infrastructure.
Hardware Connectors (OT)
Modbus TCP (Client and Server)
Siemens S7 - to read/write Siemens PLCs
EtherCAT
Ethernet/IP (in testing phase)
OPC UA Client (in testing phase)
BACnet/IP (in development phase)
Software Connectors (IT)
MQTT - Modern Industry 4.0 protocol (sparkplug B only)
InfluxDB - Database Logging
Emails - Send emails
HTTP Server - Create a mini API server (in testing phase)
HTTP Client - read/write data to REST APIs
Node-RED - read and write tags
JasperNode Technical Architecture (Controller Runtime)
Execution Model: JasperNode replaces the traditional, indiscriminate cyclic scan of a PLC. It uses a deterministic, event-driven, four-stage "Main Cycle":
Data In: Reads all values from external hardware/IT systems.
Event Preparation: Identifies only the tags whose values have changed.
Script Execution: Executes *only* the scripts triggered by those specific value changes.
Data Out: Writes all resulting output values in a single batch.
Logic Language: Control logic is written and executed in JavaScript
Core Principle (Atomic Tag Control): A variable (a "tag") can only be changed by its own single, assigned script. This rule eliminates common bugs where multiple program parts write to the same variable.
Core Components: separated from UI and AI Chat in an isolated thread (Worker).
Tag Engine: A persistent, publish/subscribe system that manages all tags, values, and triggers script execution.
Connector Manager: Manages all data I/O to/from OT hardware and IT systems
Script Manager: Manages logic development, execution and versioning.
Version Control: All logic scripts and its changes are stored within a local DB, providing a complete change history and rollback capability.
AI Agent Integration
The primary role of the AI Agent is to translate natural language prompts from a human user into executable JavaScript control logic, create/modify tags and configure the connectors.
Prompt: A user writes a natural language command to generate logic or create connectors into the on-site JasperNode software.
Contextualise and Generate (At JasperX): The prompt is securely sent to JasperX, where it adds essential system context. The AI agent generates all necessary components for the task, including the required connector configurations, new tags (variables), and the JavaScript control logic.
Review & Deploy: The generated code and configurations are sent back to the user. As the "Human-in-the-Loop," the user can review and approve the items (critical tasks) before they are deployed into the live system.
Documentation
Documentation
The documentation is embedded in the JasperNode. Once installed, open AI chat and ask "How to get started?". The AI assistant will guide you through the Key Concept and the Steps to take.
Understanding the concept through the example of a traditional PLC
Understanding the concept through the example of a traditional PLC
If you come from a traditional PLC background (Allen Bradley, Siemens), moving to a JavaScript-based runtime might feel unfamiliar. However, the core logic flow remains surprisingly similar to a standard Ladder Rung.
We use an architecture based on three components: Triggers, Scripts, and Tags. Read more about it at our forum forum.jasperx.io
The Deep Dive
The Deep Dive
For a deep dive into our architecture and the technology behind it, download the full technical white paper.
Questions & Answers
Questions & Answers
Who owns the intellectual property (IP) we create using JasperNode?
Who owns the intellectual property (IP) we create using JasperNode?
You own 100% of the intellectual property you create.
Any control logic, process configurations, tag structure or proprietary data you develop using JasperNode is your exclusive property. JasperNode is a tool, just like a code editor or a compiler and JasperX is a management platform for your "nodes". The IP belongs to the creator - your company.
Who can see the information and prompts we enter into JasperX?
Who can see the information and prompts we enter into JasperX?
Your data is strictly confidential and completely private.
Access to your prompts, your data, and the code you generate is restricted exclusively to the authenticated user. Our platform is built on a secure, multi-tenant architecture. This means we enforce strict logical isolation at both the application and database levels. Our application code and database policies ensure that a query from your account cannot see or access data from any other organisation. No other customer or any unauthorised third party can see your information.
Will our data be used to train AI models for other customers?
Will our data be used to train AI models for other customers?
No. Absolutely not.
Your proprietary data, your prompts, and your business processes are never used to train AI models for other customers. Your competitive advantage always remains yours alone.
Still have questions?
Still have questions?
Report abuse