Device zoo
The product repository includes twelve simulator services across OPC UA, S7, EtherNet/IP, Modbus TCP, BACnet/IP, and MQTT. Use their process models and fault controls to exercise applications without connected equipment.
Twelve simulators, six protocols.
Shared infrastructure runs alongside: PostgreSQL (historian + audit, ports 5432 and 5433) and an Eclipse Mosquitto broker (1883, plus 9001 for MQTT-over-WebSocket) — the broker the MQTT sims and driver talk through.
Start the simulators with Compose.
# infrastructure (Postgres + Mosquitto), then the device fleet $ docker compose -f docker/infra/docker-compose.yml up -d $ docker compose -f docker/devices/docker-compose.yml up -d # point a device at a sim like any real device [[devices]] name = "press-sim" driver = "s7" [devices.config] host = "127.0.0.1" port = 10102
Run these commands from a product source checkout. They start simulators and infrastructure; for this walkthrough, run the gateway on the host and connect through the published ports. The repository also supplies a gateway container definition and deployment examples. Ask us about access to the simulator files.
Break things on purpose.
Every sim exposes the same HTTP control surface (host ports 9301–9312, one per sim). This is how driver reconnect behavior, quality propagation, and screen stale-state handling get exercised without touching real equipment.
# 30 seconds of comm loss on the S7 press, then watch quality go bad → good $ curl -X POST "http://localhost:9303/inject?type=comm_loss&duration=30" $ curl http://localhost:9303/status
Drivers tested like software.
The repository includes simulator-based validation harnesses for reconnects, quality handling, alarms, and multi-gateway behavior. Use the fleet for your application-specific integration tests and training environments, including screen behavior during communication loss and recovery.