Explore model variants side by side. Compare acquisition scope, forwarding protocols and physical ports, then open a model for its full specifications and documents.
1 matching models · 219 in the catalog
Showing 1–1 of 1Match device-side protocols and the host system first, then check ports, wireless connections and capacity. Candidates below use confirmed model specifications.
Check each model’s listed acquisition protocols and the required host-system protocol. A model suffix alone does not establish equivalent acquisition capability.
Listed acquisition protocols: Modbus RTU / Modbus TCP
Forwarding: BACnet / Modbus / MQTT / OPC UA
This guidance narrows the candidates. Confirm communication roles, read/write direction, the point list, wiring and model-specific resources before final selection.
“Unconfirmed” means documentation does not establish a value; it does not mean zero or unsupported.
| ModelDevice acquisition → System forwarding | |
|---|---|
| 01Acquisition scopeDevice side | Listed acquisition protocols |
| 02Forwarding protocolsSystem side | |
| Point capacity | 2048 |
| Device capacity | 256 |
| Ethernet ports | 1 |
| Total serial ports | 8 |
| RS485 | 8 |
| RS232 | — |
| CAN ports | — |
| KNX TP ports | — |
| Two-wire MBus ports | — |
| DI channels | — |
| DO channels | — |
| AI channels | — |
| AO channels | — |
| Touchscreen | — |
| Model documents | Specifications & downloads |
“—” means the documentation does not establish a value; 0 is a confirmed zero. Check model documentation for shared ports, options and protocol roles.
