Introduction: You can find a description of this phase in section Phase 1 (Introduction).

This Input Agent allows communication via OPC/UA.

Activating Services

First, the following entries must be made in the configuration file ./etc/factory.xml. An additional licence is required.

<Call name="addService">
	<Arg>com.ebd.hub.services.iot.IoTServerService</Arg>
	<Arg>etc/iotserver.xml</Arg>
</Call>
 
<Call name="addService">
	<Arg>com.ebd.hub.services.iot.IoTClientService</Arg>
	<Arg>etc/iotclient.xml</Arg>
</Call>

Server Model

images/download/attachments/44944557/530-version-4-modificationdate-1657523315943-api-v2.png

(1) If the checkbox is set, a simple response (for an ok or a fail) is sent to the client after the profile has finished. If it is not set, a response with dynamic return values can be created via the target structure. For this purpose, all fields under the root-level node IOT_Result become part of the response.

(2) Selection of partner.

(3) At least one channel must be selected.

Subscription Model

images/download/attachments/44944557/1214-version-2-modificationdate-1657523638189-api-v2.png

(1) The connection alias (is added in the configuration file ./etc/iotclient.xml). Note: At least one alias must be created for the subscription model to be selectable.

<Configure class="com.ebd.hub.services.iot.IoTClientService">
    <Set name="verbose">false</Set>
 
    <Call name="addAlias">
        <Arg>
            <New class="com.ebd.hub.services.iot.opcua.OpcUaClientSettings">
                <Set name="alias">boiler</Set>
                <Set name="endpointURL">opc.tcp://opcua.demo-this.com:51210/UA/SampleServer</Set>
                <Set name="minSize">4</Set>
                <Set name="maxSize">4</Set>
                <Set name="allowGrowing">true</Set>
            </New>
        </Arg>
    </Call>
    
</Configure>

(2) Subcription Values can be selected in an OpcUa browser via the context menu. If one of these values changes, the profile is triggered, see also (4). The Read Values (3) are then also queried.

(3) Read Values can be selected in an OpcUa browser via the context menu menu. Note: You can also manually insert entries via the context menu and structure them hierarchically. The Read Values can then be moved there via drag and drop. See also (7).

(4) With DataChange, changing values triggers the profile. With Direct, the values are actively queried at regular intervals.

(5) Each received record has a status. If this checkbox is set, the status bad is ignored. If the checkbox is not set, the profile will abort with an error in this case.

(6) If the checkbox is set, all values are queried once when the profile is activated.

(7) Creates a suitable source structure for phase 3.

Response Route

There is no corresponding Response Route here.