Click or drag to resize

SBUS IP configuration

Home
Communication interface settings

Select TCP or UDP as protocol. Socket number settings are ignored and can be set by default as –1 (this setting is valid only for slave sides of the protocol).

Communication interface settings
Figure 1: Communication interface settings
S-Bus protocol settings
Protocol Specific Parameters
Figure 2: Protocol Specific Parameters

CommServer allows us to tune the timeout settings that are used in the S-Bus DataProvider. The following settings are available:

  • InterframeGap - period of time in milliseconds between consecutive request frames

  • MaxNumberOfRetries - maximal number of retries getting the response. After this limit has passed the base station finds that communication with the device using current interface coupled with this protocol is broken and it activates the next interface in the pipe if available. The failed interface is marked inactive and will remain in this state until the defined (as “inactive time after failed”) timeout expiration.

  • ResponseTimeOut - maximal time of waiting for the response from a remote device

  • TimeoutAfterFrame - a silent interval separating message frames

Note Note

The default settings are optimal for communication over the serial link; if TCP/UDP transportation is used it is recommended to tune the settings.

If TCP/UDP transportation is used it is necessary to set a valid segment address. This address is the address of PLC that we want to connect to. Below there is an example of connection settings to PLC using TCP:

Example of connection settings to PLC using TCP
Figure 3: Example of connection settings to PLC using TCP

The syntax of the segment address is:

server_IP_address:port_to_which_commserver_establish_the_connection

In the figure below there is an example connection to PLC, whose IP address is 192.168.0.8 and communication port is 2101:

Example connection to PLC
Figure 4: Example connection to PLC
Configuration and interpretation of received data

S-Bus DataProvider reads the data in blocks. Requests are sent to the device (called station in the CommServer configuration) that has an address (according to the S-Bus protocol) set inside port (interface) definition. The user can freely define a block of data to be read. The block of data is received as an answer from the device.

During the configuration of the data block, the following settings must be configured:

  • Address – the initial address of the block

  • Data Type – the address space in the device to be read (available address spaces are: Flags, Inputs, Outputs, Regis-ters, Timers, Counters)

  • Name – the name of the data block in the CommServer configuration (not used during communication)

  • Tags collection – tags definitions inside the block. Each tag has:

    • Name – the name of the tag inside the OPC server address space

    • Access Rights - indicate if this item is read only, write only or read/write. This is NOT related to security but rather to the nature of the underlying hardware

    • DataTypeConversion - conversion requirements. Data will be available in the required type (if conver-sion is possible).