# 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.

| Simulator | Protocol | Host ports | Models |
| --- | --- | --- | --- |
| `opcua-sim` | OPC UA | `4841` | General-purpose OPC UA address space. |
| `flow-test-bench` | OPC UA | `4842` | Flow test bench — runs alongside opcua-sim. |
| `opcua-chemical-dosing` | OPC UA | `4843` | Chemical dosing skid with explicit string NodeIds `(ns=2;s=<Name>)`. |
| `hydraulic-press` | Siemens S7 | `10102` | Host TCP port 10102 maps to container port 102. Set port = 10102 in \[devices.config\]. |
| `cip-aerospace-bench` | EtherNet/IP (CIP) | `44818` | Aerospace test bench behind a proxy, so comm-loss faults don't reset bench state. |
| `water-power-meters` | Modbus TCP | `5020` | Utility metering — water, power. |
| `modbus-plc-farm` | Modbus TCP | `5050+ (one per PLC)` | Simulated PLCs — 10 by default; the simulator accepts up to 1000. Expand published ports with the count. |
| `modbus-chiller-bank` | Modbus TCP | `6050+ (one per chiller)` | Chiller bank, 2 by default. |
| `bacnet-vav-farm` | BACnet/IP (UDP) | `47808+ (one per VAV)` | VAV boxes — 30 by default; the simulator accepts up to 1000. Expand published ports with the count. |
| `bacnet-ahu-bank` | BACnet/IP (UDP) | `48900+ (one per AHU)` | Air-handling units, 6 by default. |
| `bacnet-chiller-plant` | BACnet/IP (UDP) | `49000+ (plant + chillers)` | Plant controller plus 4 chillers. |
| `mqtt-building-sensors` | MQTT (publisher) | `— (publishes to the broker)` | IoT sensor fan-out publishing bare-JSON scalars; scale with SENSOR_COUNT. |

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.

```sh
# 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](https://thermitescada.com/contact) 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.

| Endpoint | Effect |
| --- | --- |
| `POST /inject?type=<kind>&duration=<v>` | Inject a fault — comm loss, stale data, quality degradation — optionally time-boxed. |
| `POST /clear[?type=<kind>]` | Clear one fault kind, or all of them. |
| `GET /status` | Current fault state. |
| `GET /health` | Container healthcheck. |

```sh
# 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.
