Date: Thu, 28 Mar 2024 10:49:37 +0000 (UTC) Message-ID: <789684561.29.1711622977733@d05e89a647d9> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_28_1150661767.1711622977733" ------=_Part_28_1150661767.1711622977733 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
A physical interface that connects to our system. Depending of its techn= ology, it will be managed by a specific module like ModBusRTU or SNMP or ma= ybe even a Camera. In this configuration we define all parameters to access= the device throught the SiteController, for example Slave address, IP addr= ess, passwords, baud rate, etc.
At the moment we have the possibility to connect the following devices= p>
Here we have an exmaple of an ModBusRTU configuration, while using an AD= AM-4051 with 16 DI's. For the sensor configuration, please click here.
<c= omponent_template config_version=3D"1.0" schema_version=3D"1.0"> <description>template_Adam_4051</description> =09=09=09=09=09= =09=09=09=09=09=09# This is the general description respectivly the name of= the Template. <vendor>azeti</vendor>=20 <version>2</version>=20 <class>multi-sensor</class> <sensors> <sensor sensor_id=3D"DI00"> =09=09=09=09=09=09=09=09=09=09=09= =09=09=09=09# This is the name of the sensor as it will be shown in the Das= hboard. . =09=09. =09=09. =09=09 </sensor> =09=09. =09=09. =09=09. =09<devices> =09=09<device device_id=3D"ADAM-4051">=09=09=09=09=09=09=09=09=09=09= =09=09=09=09# Name of the device.=09=09=09=09 =09=09<modbus_device pdu_addressing=3D"false">=09=09=09=09=09= =09=09=09=09=09=09# Wheter or not, PDU addressing is turned on or off. Resp= ectively if the register starts from 0 (true) or 1 (false). <modbus_rtu>=09=09=09=09=09=09=09=09=09=09=09=09=09= =09=09=09# What ModBus type we are using. Possible options are ModBusRTU an= d ModBusTCP. <daemon_id>0</daemon_id>=09=09=09=09=09=09= =09=09=09=09=09=09# This is the serial interface to be used, configurable i= n the SiteController.cfg (See Link below). <data_bits>8</data_bits>=09=09=09=09=09=09= =09=09=09=09=09=09# Databits used by the device (default is 8). <stop_bits>1</stop_bits>=09=09=09=09=09=09= =09=09=09=09=09=09# Stopbits used by the device (default is 1). <baud_rate>9600</baud_rate>=09=09=09=09=09= =09=09=09=09=09=09=09# Baudrate used by the device. <parity>none</parity>=09=09=09=09=09=09=09= =09=09=09=09=09=09# Parity used by the device. <slave_address>1</slave_address>=09=09=09= =09=09=09=09=09=09=09# Slave address used by the device. </modbus_rtu> </modbus_device> <sensor_gateways> <sensor_gateway sensor_gateway_id=3D"ADAM-4051" publish_= strategy=3D"on_change">=09# Here we define the name of the gateway, so t= he sensor knows which one to use. =09=09=09=09=09=09=09=09=09=09=09=09=09=09=09=09=09=09=09=09=09=09=09= # Additionally we can change how the sensor data will be sent to the server= . =09=09=09=09=09=09=09=09=09=09=09=09=09=09=09=09=09=09=09=09=09=09=09# Poss= ible options: never, on_change, interval, always. =09=09=09=09=09=09<modbus>=09=09=09=09=09=09=09=09=09=09=09=09=09=09= =09# In some cases, it is required to use multiple gateways. Exmaple below. <modbus_register> <register_address>1</register_address&= gt;=09=09=09=09=09=09=09# This is the the first register address of the dev= ice. <register_count>16</register_count>= =09=09=09=09=09=09=09=09# Here we tell the system, how many registers the d= evice has. In this case 16, because the Adam has 16 inputs. <block_type>coils</block_type>=09= =09=09=09=09=09=09=09=09# Here we define what kind of type these registers = are (Ex. coils, holding registers, input registers). </modbus_register> <scheduling> <polling_interval>200</polling_interva= l>=09=09=09=09=09=09# Here we define how often the registers should be p= olled. The value 200, is equal to 0.2 seconds. <error_handling> <retry retry_algorithm=3D"linear"/> </error_handling> </scheduling> </modbus> </sensor_gateway> </sensor_gateways>=09 =09=09</device>=20 </devices> </component_template>
Here we have an example of a ModBusTCP configuration, using a IFM AY1020= IO-Link Master
<c= omponent_template config_version=3D"1.0" schema_version=3D"1.0"> <description>template_AY1020</description> =09=09=09=09=09=09= =09=09=09=09=09# This is the general description respectivly the name of th= e Template. <vendor>azeti</vendor>=20 <version>2</version>=20 <class>multi-sensor</class> <sensors> <sensor sensor_id=3D"AY1020-Port1-Bit0"> =09=09=09=09=09=09= =09=09=09=09=09=09=09=09=09# This is the name of the sensor as it will be s= hown in the Dashboard. . =09=09. =09=09. =09=09 </sensor> =09=09. =09=09. =09=09. =09<devices> =09=09<device device_id=3D"AY1020-IOLink-Master">=09=09=09=09=09=09= =09=09=09=09=09# Name of the device. =09=09<modbus_device pdu_addressing=3D"true"> =09=09=09<modbus_tcp>=09=09=09=09=09=09=09=09=09=09=09=09=09=09= =09=09# Definition of the ModBus typ we are using. =09=09=09<address>192.168.118.64</address>=09=09=09=09= =09=09=09=09=09=09# IP address of the ModBus device. =09=09=09<port>502</port>=09=09=09=09=09=09=09=09=09= =09=09=09=09=09# Port of the device (default ist 502). =09=09=09<slave_address>1</slave_address>=09=09=09=09= =09=09=09=09=09=09# Slave address of the device. =09=09</modbus_tcp> =09=09</modbus_device> =09<sensor_gateways> =09=09<sensor_gateway publish_strategy=3D"always" sensor_gateway_i= d=3D"gw_AY1020-Port1">=09# Here we define the name of the gateway, so th= e sensor knows which one to use. =09=09<modbus> =09=09=09<modbus_register> =09=09=09<register_address>1000</register_address>= =09=09=09=09=09=09=09# This is the the first register address of the device= . =09=09=09<register_count>3</register_count>=09=09= =09=09=09=09=09=09=09# Here we tell the system, how many registers the devi= ce has. =09=09=09<block_type>holding_registers</block_type&g= t;=09=09=09=09=09=09=09# Here we define what kind of type these registers a= re (Ex. coils, holding registers, input registers). =09=09=09<timeout>1000.0</timeout>=09=09=09=09=09= =09=09=09=09=09=09# Timeout value (1000 equals 1 second). =09=09</modbus_register> =09=09<scheduling> =09=09=09<polling_interval>1000</polling_interval>= =09=09=09=09=09=09=09# Here we define how often the registers should be pol= led. The value 1000, is equal to 1 second. =09=09=09<error_handling> =09=09=09<retry retry_algorithm=3D"linear"/> =09=09=09<fixed_timeout>1000</fixed_timeout> =09=09=09</error_handling> =09=09</scheduling> =09=09</modbus> =09</sensor_gateway> <sensor_gateway publish_strategy=3D"always" sensor_gateway_id=3D= "gw_AY1020-Port2"> =09=09<modbus> =09=09=09<modbus_register> =09=09=09<register_address>1000</register_address> =09=09=09<register_count>3</register_count> =09=09=09<block_type>holding_registers</block_type&g= t; =09=09=09<timeout>1000.0</timeout> =09=09</modbus_register> =09=09<scheduling> =09=09=09<polling_interval>1000</polling_interval> =09=09=09<error_handling> =09=09=09<retry retry_algorithm=3D"linear"/> =09=09=09<fixed_timeout>1000</fixed_timeout> =09=09=09</error_handling> =09=09</scheduling> =09=09</modbus> =09</sensor_gateway> =09. =09=09=09. =09. </sensor_gateways>=09 =09=09</device>=20 </devices> </component_template>
Here we have an example of a ModBusTCP configuration, using a B&R X2= 0BC0087 ModBusTCP device.