Wieland samos PRO COMPACT - Data Transferred to the Network (Network Input Data Sets)

Product description
Wieland Electric GmbH | BA000970 | 11/2016 (Rev. F)
19
Data transferred to the network (network input data sets)
910743435
Available data
The samosPRO gateways can provide the following data:
• Operating data
–
Logic results from
the samosPRO safety controller (see Routing table [ch. 5.1.2, p.
37] )
–
Input values
(HIGH/LOW) for all samosPRO input expansion modules in the system
–
Output values
(HIGH/LOW) for all samosPRO input/output expansion modules (see
Module state / input and output values [ch. 3.3.1, p. 22] )
–
Output data
from another network, i.e. data received from a second gateway in the
samosPRO system (see Transmission of data from a second network [ch. 3.3.3, p. 23] )
• Diagnostics
–
Test values
(CRCs): (see Configuration test values (CRCs) [ch. 3.3.4, p. 23] )
–
Error and state information
: Error and state information for the modules [ch. 3.3.5, p.
23]
Data sets
The physical modules are not presented as typical hardware modules in the network. Instead,
the data provided by the samosPRO system has been arranged in four
input data sets .
•
Data set 1
(max. 50 bytes) contains the operating data. It can be compiled with the aid of
samosPLAN5+. In the form in which it is delivered, the content of data set 1 is preconfigu-
red; it can be freely modified.
Details: see table
"Overview of input data sets" [ch. 3.3, p. 20]
For the SP-PROFIBUS-DP gateway, data set 1 was divided into five input data blocks, with
data blocks 1–4 each containing 12 bytes and data block 5 two bytes.
For the SP-CANopen gateway, data set 1 was divided into four blocks, each with 8 bytes.
You will find more detailed information in the corresponding section for each gateway.
•
Data set 2
(32 bytes) contains the test values (CRCs) for the system configuration.
See table "Overview of input data sets 1-3 (basic settings for Modbus TCP)" below
•
Data set 3
(60 bytes) contains the state and diagnostic data for the various modules, with
four (4) bytes per module, with the controller module comprising 3 x 4 bytes. Details: see
table "Meaning of module state bits" [ch. 3.3.5, p. 23]
•
Data set 4
(60 bytes) is currently filled with reserved values.
3.3