Hoppa till huvudinnehåll

SIA Connect Connector

The SIA Connect connector enables the platform to publish commands and receive device uplinks on its MQTT broker from a SIA Connect IIoT Edge Gateway. The SIA Connect edge gateway supports over 30 industrial protocols, allowing seamless integration with a wide range of PLC and BMS vendors. It features intuitive configuration software and supports up to 500 tags.

Supported features from the platform:

  • Import devices
  • Receive device uplink updates
  • Publish commands

Key protocol support:

  • BACnet IP
  • BACnet MS/TP
  • Beckhoff TwinCAT ADS
  • Modbus TCP
  • Modbus RTU
  • Modbus RTU over TCP
  • M-Bus
  • Wireless M-Bus (wM-Bus)
  • OPC-UA client
  • OPC-UA server
  • Various manufacturer specific protocols.

Connector details SIA Connect​

Sia Connect

Required Information​

To set up a connection to a SIA Connect Edge Gateway, provide the gateway UUID:

  • a. Edge Gateway UUID: This is the universal unique identifier of the Edge Gateway. It is used in the MQTT topic structure to identify incoming device updates from the gateway.
  • b. MQTT Username: The MQTT username, not available in the UI and must be configured by the platform support team.
  • c. MQTT Password: The MQTT password, not available in the UI and must be configured by the platform support team.

Optional for Commands (not available in the UI)​

  • d. SIA Web Interface URL: The URL to the web interface of the SIA Edge Gateway
  • e. SIA Username: Your API username.
  • f. SIA Password: Your API password.

Configure the Edge Gateway

Hardware Configuration​

The gateway comes pre-configured to use a static IP 10.20.30.40. By accessing the web interface (through that IP or through direct USB-C connection at 192.168.42.42), the network configuration can be changed.

It is important that the gateway can access the Platform MQTT broker through the configured network, as it has no Internet connection.

Software Configuration​

The Gateway must install the MQTT SIA Connector to be able to connect to the platform MQTT broker.

  • For each protocol in addition to MQTT you wish to support, the appropriate SIA Connector must be installed in the gateway.
  • An MQTT instance for the platform should be created pointing to the platform MQTT broker (mqtt.staging.yggio.net) and with the MQTT username and password configured on the platform side.

Item Configuration​

An Item should be created for each SIA Connector supporting uplinks, with the following options:

  • Write only
  • Topic: siaconnect/%UUID%
  • Input template (unique for every SIA Connector). Example for BACnet:
{
"t": "bacnet",
"ts": "%ITEM.VALUE.TIME%",
"v": {
  "unit": "%ITEM.UNIT%",
  "objectType": "%ITEM.OBJECT_TYPE%",
  "objectInstance": "%ITEM.OBJECT_INSTANCE%",
  "property": "%ITEM.PROPERTY%",
  "dataType": "%ITEM.DATA_TYPE%",
  "value": %VALUE%
  }
}

For Each Uplink Protocol​

You need to:

  1. Make sure the SIA Connector is installed.
  2. Create an instance configured to your device.
  3. Create items for each input you desire. The items needs to include MQTT topic and input template.

Note: Items should not require any additional configuration by default.

Beckhoff TwinCAT Setup Example in SIA Edge gateway​

Add the TwinCAT Connector​

  1. Login to the SIA instance.

  2. Go to Connectors from the side menu.

  3. Add Beckhoff TwinCAT connector if it is not already added.

  4. Click on + Add instance to Beckhoff TwinCAT.

  5. Most (if not all) of the information should come from the PLC.
    Consult with the people working with the PLC at site.

    Example configuration (with comments):

    • Name: 85000 A ABF01 (Site building PLC)
    • Address: 25.75.0.20 (PLC IP address)
    • Target Ams NetID: 25.75.0.20.1.1
      (As of writing, all NetIDs have been <ip>.1.1, but consult with the PLC team)
    • Target Ads Port: 851 (PLC ADS port)
    • Timeout: 5000

Item Configuration​

  1. On the side menu, go to Instances and select your instance (e.g., 85000 A AB01).

  2. Click the + New Item button.

  3. Consult the tag list to get the information.

    Example configuration:

    • Name: F85000_EASTERN_A_1501.GT13_AI.rOut
    • Type: REAL
    • Read/Write: Read only
    • Variable Name: F85000_EASTERN_A_1501.GT13_AI.rOut
    • Input template:
{
  "t": "adstwincat",
  "v": %VALUE%,
  "tag": "%ITEM_SENDER.NAME%",
  "type": "%ITEM_SENDER.TYPE%",
  "ts": "%VALUE.EPOCH_TIME_MS%",
  "unit": "%ITEM_SENDER.UNIT%",
  "d": "%ITEM_SENDER.DESCRIPTION%"
}