Connector catalog
The connectors JasperNode can install. Each is a separate signed package from the connector
catalogue, so a connector is updated without updating the controller. A programme from JasperX names
the connectors it uses and the controller installs them; CNTR= on the Linux installer installs
named ones as it starts, for example CNTR=modbus,s7. The install names are modbus, ethercat,
s7, serial, jaspermate, lidar, mqtt, mqtt_broker, influxdb, modbus_server and hmi.
Adding, configuring and enabling a connector is done from JasperX.
Direction: in = device → tag, out = tag → device.
OT — fieldbus connectors
Section titled “OT — fieldbus connectors”These talk to physical buses and devices.
| Connector | Connects to | Directions | Notes |
|---|---|---|---|
| Modbus | Modbus devices over TCP, RTU (serial), or RTU-over-TCP gateways | in / out | Map coils and registers; group them into shared read/write requests for fussy devices |
| EtherCAT | An EtherCAT fieldbus (slaves, distributed I/O, drives) with cyclic PDO exchange | in / out | Linux hardware only — needs raw-socket access and low latency |
| Siemens S7 / LOGO! | Siemens S7-300/400/1200/1500 and LOGO! PLCs directly | in / out | Reads/writes PLC data areas |
| Serial | Raw serial ports / TTYs on the host | in / out | Generic async serial / RTU bus master |
| JasperMate IO | JasperNode’s JasperMate I/O hardware over its firmware protocol | in / out | Event-driven (push), not polled |
| LiDAR | 2D laser scanners — SICK (CoLa-B) and Leuze ROD (508) over TCP/UDP | in | Linux hardware only. Streams each sweep plus zone / sector / profile monitor results as tags |
IT — network, message-bus and cloud connectors
Section titled “IT — network, message-bus and cloud connectors”These run as network clients/servers and tolerate the link dropping with automatic reconnect.
| Connector | Connects to | Directions | Notes |
|---|---|---|---|
| MQTT | An MQTT broker — plain pub/sub or Sparkplug B | in / out | in subscribes topics → tags; out publishes tags → topics. Sparkplug B maps birth/data messages to tags |
| MQTT Broker | Runs an MQTT broker on this node for other clients to connect to | in | Accepts MQTT 3.1.1, 5.0 and WebSocket clients; mirror chosen topics into tags for scripting and logging |
| InfluxDB | An InfluxDB time-series database | out | Streams tag values out as time-series points |
| Modbus Server | Makes this node a Modbus TCP slave for external masters | in / out | External masters read/write registers mapped to your tags |
| HMI Server | Serves a browser operator panel (pages + components) over HTTP/WS | in / out | Local PIN auth; per-session exclusive control of writable widgets |
System connectors
Section titled “System connectors”The controller’s own services, always present.
| Connector | Responsibility |
|---|---|
| Local web interface | The local web interface and its API, port 9009 |
| JasperX | The link to JasperX: claim, programme, sign-off, telemetry, remote access, updates |
| Persist | Keeps tags in the controller’s local database and restores them at start |
| Tools | Network tools: ARP scan, ping, traceroute |
| Logic Cycle | Runs the tag scripts |