Driver objects |
S7TCP32 -> Creating variables -> Driver objects and datatypes -> Driver objects |
Show all Hide all |
The following object types are available in this driver:
Driver object types and supported IEC data types for process variables in zenon
Driver object type |
Channel type |
Read / Write |
Supported data types |
Comment |
---|---|---|---|---|
ALARM_S Associated value |
65 |
L |
BOOL, SINT, USINT, INT, UINT, DINT, UDINT |
Variables of the type ALARM_S associated value contain the associated values received with a message, if they exist. Also here the offset contains the S7 message number. The addressing of the associated value in the associated value record is realized via the bit number. If e.g. 3 associated values of the type Byte are received, the first one has bit number 0, the second has bit number 8 and the third has bit number 16. |
ALARM_S Message |
9 |
L |
BOOL, UDINT |
With the datatype ALARM_S bit
spontaneously realtime-stamped alarm messeges of the S7 can be
received (e.g. from PDiag). This variable only has a value, when
the S7 sends an ALARM_S telegram. No initial image or similar thing
is read. The offset here is the S7 message number. |
Output |
11 |
L / S |
BOOL, SINT, USINT, INT, UINT |
If you want outputs to be written, you have to activate this in the general section of the driver settings. |
Input |
10 |
L |
BOOL, SINT, USINT, INT, UINT |
|
Ext. data block |
34 |
L / S |
BOOL, SINT, USINT, INT, UINT, DINT, UDINT, REAL, STRING, WSTRING, DATE_AND_TIME |
STRING: max. 210 characters |
S5Time data block |
97 |
L / S |
REAL |
Only times in seconds will be read and written. Attention: 32 bits of data will be read, but in the S7, S5Time has only 16 bits; you should therefore make sure that there are still 16 bits left after the last S5Time object in a data block. |
PLC marker |
8 |
L / S |
BOOL, SINT, USINT, INT, UINT, DINT, UDINT, REAL |
|
Counters |
4 |
L / S |
UDINT |
|
Time |
5 |
L |
REAL |
|
Driver variable |
35 |
L / S |
BOOL, SINT, USINT, INT, UINT, DINT, UDINT, REAL, STRING |
Variables for the statistical analysis of communication. Find out more in the chapter about the Driver variables |
*)The data type DATE_AND_TIME in detail:
For each offset the following structure is read or written:
Byte |
Contents |
Value |
Possible value range |
BCD code |
---|---|---|---|---|
0 |
Year |
0 - 99 |
1990 - 1999 |
90h - 99h |
1 |
Month |
1 - 12 |
1 - 12 |
01h – 12h |
2 |
Day |
1 - 31 |
1 - 31 |
01h – 31h |
3 |
Hour |
0 - 23 |
0 - 23 |
00h - 23h |
4 |
Minute |
0 - 59 |
0 - 59 |
00h - 59h |
5 |
Second |
0 - 59 |
0 - 59 |
00h - 59h |
6 |
Millisecond HT |
0 - 990 ms Bit 4 - 7 Hundreds, 0 - 3 Tens |
0 - 999 |
00h - 999h |
7 |
Milliseconds O, Data |
0 - 9 Bit 4 - 7 millisec. Ones, 0 - 15 Bit 0 - 3 Data |
|
|