§ 06 · SUPPORTED PROTOCOLS

Five protocols, one server,
no surcharge for mixing them.

Every protocol implements the same five methods at the driver layer. Adding one does not touch anything above it.

#ProtocolTypical devicesField notesStatus
01Modbus TCPDelta DVP / AS PLCs, meters, inverters, I/O modulesRTU over TCP is supported for devices behind RS485 converters. Picking the wrong mode connects fine but reads nothing — the most common field trap.Supported
02Siemens S7S7-1200 / 1500, S7-300 / 400Enable PUT/GET on the CPU and turn off “optimized block access” on the data blocks; 1200/1500 use rack 0 slot 1, 300/400 rack 0 slot 2.Supported
03BACnet/IPAHUs, chiller controllers, existing third-party building equipmentReads the device object list so points can be created in bulk. Device instances must be unique site-wide, and object numbering must come from the vendor’s point list — never guessed.Supported
04MQTT 3.1.1IoT sensors, gateways and cloud platforms. Raw values and JSON payloads both work, and one topic can feed several pointsThe direction is reversed: we do not poll, the device publishes. So “never received anything” and “broker disconnected” are two different states and must not both read as a communication failure. Staleness detection is off by default — MQTT usually publishes on change, so a status point that changes twice a day would otherwise show red all day.Supported
05SOAP / Web ServiceWeb service interfaces on existing systems. Endpoint, SOAPAction, request template and value path are all entered in the settings pageSOAP has no connection to speak of; the connection test means issuing one call to confirm reachability — otherwise a wrong endpoint or credential only surfaces on the first scan, and it looks like “every point is broken” rather than “the address is wrong”. One scan issues one request, not one per point.Supported

How to choose a protocol, and why the point list is the biggest risk:Three protocols in one building, and how to bring them into one system

§ 09 · START THE ASSESSMENT

Three questions will tell you
whether this fits.

Talk to us Full product page Hardware integration Download the catalogueabout 2 MB
  1. CHK-01Which subsystems does this building have, and who installed each one?
  2. CHK-02Can you still find the point list for the Modbus devices?
  3. CHK-03Do you need to watch status, or to actually control?
  4. We prefer to ask the questions before quoting. A price given before the point count is settled is a price that will change.