... V9.0 SP2. 06/2019. A5E40797470-AD. Security information. 1. General ... 4%d@. PLC Process Control Message -. Failure. 3. DR @1%d@/@2%d@/DP2: @5%d@.@6%d ...
SIMATIC Process Control System PCS 7 Basis Library (V9.0 SP3)
Function Manual
Security information
1
General Information About Block Description
2
Display for avoiding stop without asset management
3
Icons for user-defined SFC types
4
Family: CONTROL
5
Family: @System
6
Family: @PAM
7
Internal block
8
Appendix
9
Valid for PCS 7 as of V9.0 SP2 06/2019
A5E40797470-AD
Legal information
Warning notice system This manual contains notices you have to observe in order to ensure your personal safety, as well as to prevent damage to property. The notices referring to your personal safety are highlighted in the manual by a safety alert symbol, notices referring only to property damage have no safety alert symbol. These notices shown below are graded according to the degree of danger.
DANGER indicates that death or severe personal injury will result if proper precautions are not taken.
WARNING indicates that death or severe personal injury may result if proper precautions are not taken.
CAUTION indicates that minor personal injury can result if proper precautions are not taken.
NOTICE indicates that property damage can result if proper precautions are not taken. If more than one degree of danger is present, the warning notice representing the highest degree of danger will be used. A notice warning of injury to persons with a safety alert symbol may also include a warning relating to property damage.
Qualified Personnel The product/system described in this documentation may be operated only by personnel qualified for the specific task in accordance with the relevant documentation, in particular its warning notices and safety instructions. Qualified personnel are those who, based on their training and experience, are capable of identifying risks and avoiding potential hazards when working with these products/systems.
Proper use of Siemens products Note the following:
WARNING Siemens products may only be used for the applications described in the catalog and in the relevant technical documentation. If products and components from other manufacturers are used, these must be recommended or approved by Siemens. Proper transport, storage, installation, assembly, commissioning, operation and maintenance are required to ensure that the products operate safely and without any problems. The permissible ambient conditions must be complied with. The information in the relevant documentation must be observed.
Trademarks All names identified by ® are registered trademarks of Siemens AG. The remaining trademarks in this publication may be trademarks whose use by third parties for their own purposes could violate the rights of the owner.
Disclaimer of Liability We have reviewed the contents of this publication to ensure consistency with the hardware and software described. Since variance cannot be precluded entirely, we cannot guarantee full consistency. However, the information in this publication is reviewed regularly and any necessary corrections are included in subsequent editions.
Siemens AG Division Process Industries and Drives Postfach 48 48 90026 NÜRNBERG GERMANY
A5E40797470-AD 08/2020 Subject to change
Copyright © Siemens AG 2019. All rights reserved
Table of contents
1 Security information............................................................................................................................ 13
2 General Information About Block Description..................................................................................... 15
3 Display for avoiding stop without asset management ........................................................................ 19
4 Icons for user-defined SFC types.......................................................................................................... 21
5 Family: CONTROL ................................................................................................................................. 23
5.1 5.1.1 5.1.2
FM_CO: Coordination of function blocks which read data records ....................................... 23 Description of FM_CO ........................................................................................................ 23 I/Os of FM_CO.................................................................................................................... 25
6 Family: @System .................................................................................................................................. 27
6.1 6.1.1 6.1.2 6.1.3
CONEC: Monitoring the AS connection status ..................................................................... 27 Description of CONEC......................................................................................................... 27 I/Os of CONEC .................................................................................................................... 29 Message texts and associated values of CONEC................................................................... 30
6.2 6.2.1 6.2.2
CPU_RT: Determination of the runtime of OBs..................................................................... 31 Description of CPU_RT........................................................................................................ 31 I/Os of CPU_RT ................................................................................................................... 38
6.3 6.3.1 6.3.2
DIAG_AB: Evaluation of statusword AB7000 ....................................................................... 40 Description of DIAG_AB ...................................................................................................... 40 I/Os of DIAG_AB ................................................................................................................. 42
6.4 6.4.1 6.4.2 6.4.3
DPAY_V0: Monitoring DP/PA and Y-Link operating as V0 slave.............................................. 43 Description of DPAY_V0...................................................................................................... 43 I/Os of DPAY_V0 ................................................................................................................. 47 Message texts and associated values of DPAY_V0................................................................ 48
6.5 6.5.1 6.5.2
DPAY_V1: Enabling blocks downstream of a DP/PA and Y-Link operating as V1 slave ............ 49 Description of DPAY_V1...................................................................................................... 49 I/Os of DPAY V1 .................................................................................................................. 51
6.6 6.6.1 6.6.2
DPAY_V1_PN: Enabling blocks downstream of a DP/PA and Y-link operating as a V1 Slave..... 52 Description of DPAY_V1_PN................................................................................................ 52 I/Os of DPAY_V1_PN ........................................................................................................... 52
6.7 6.7.1 6.7.2
DPDIAGV0: Monitoring the status of ET 200S modules acting as DPV0 slaves after the Y link..... 53 Description of DPDIAGV0.................................................................................................... 53 I/Os of DPDIAGV0 ............................................................................................................... 55
6.8 6.8.1 6.8.2 6.8.3
DREP: Diagnostic Repeater in the DP master system ............................................................ 56 Description of DREP............................................................................................................ 56 I/Os of DREP ....................................................................................................................... 61 Message texts and associated values of DREP...................................................................... 62
6.9 6.9.1 6.9.2
DREP_L: Diagnostic Repeater downstream of a Y-Link ......................................................... 64 Description of DREP_L ........................................................................................................ 64 I/Os of DREP_L.................................................................................................................... 68
Basis Library (V9.0 SP3)
Function Manual, 06/2019, A5E40797470-AD
3
Table of contents
6.9.3
6.10 6.10.1 6.10.2 6.10.3
6.11 6.11.1 6.11.2
6.12 6.12.1 6.12.2 6.12.3
6.13 6.13.1 6.13.2 6.13.3
6.14 6.14.1 6.14.2
6.15 6.15.1 6.15.2 6.15.3
6.16 6.16.1 6.16.2
6.17
6.17.1 6.17.2 6.17.3
6.18
6.18.1 6.18.2 6.18.3
6.19
6.19.1 6.19.2 6.19.3
6.20 6.20.1 6.20.2 6.20.3
6.21
Message texts and associated values of DREP_L .................................................................. 69
FFD_CIF: Monitoring FF slaves in CIF mode ......................................................................... 71 Description of FFD_CIF ....................................................................................................... 71 I/Os of FFD_CIF .................................................................................................................. 73 Message texts and associated values of FFD_CIF ................................................................. 75
FFDP_L1: Monitoring FF slaves with maximum 32 values .................................................... 75 Description of FFDP_L1 ...................................................................................................... 75 I/Os of FFDP_L1.................................................................................................................. 77
FF_MOD32: Diagnostics of an FF slave (downstream from FF link DPV1) ............................. 79 Description of FF_MOD32 .................................................................................................. 79 I/Os of FF_MOD32.............................................................................................................. 80 Message texts and associated values of FF_MOD32 ............................................................ 82
FM_CNT: Programming and controlling FM 350 modules .................................................... 83 Description of FM_CNT....................................................................................................... 83 I/Os of FM_CNT .................................................................................................................. 86 Message texts and associated values of FM_CNT................................................................. 87
IM_TS_PN: Status alarms with time stamps......................................................................... 88 Description of IM_TS_PN ................................................................................................... 88 I/Os of IM_TS_PN................................................................................................................ 90
IMDRV_TS: Transferring time-stamped process-signal changes ............................................ 94 Description of IMDRV_TS .................................................................................................... 94 I/Os of IMDRV_TS ............................................................................................................... 98 Message texts of IMDRV_TS.............................................................................................. 100
MHA_CO: Multi HART variable read coordination (0 - 15 Channel)..................................... 101 Description of MHA_CO.................................................................................................... 101 I/Os of MHA_CO ............................................................................................................... 101
MOD_1: Monitoring up to 16 channels on S7-300/400 SM modules without diagnostic capability......................................................................................................................... 103 Description of MOD_1...................................................................................................... 103 I/Os of MOD_1/MOD_2..................................................................................................... 106 Message texts and associated values of MOD_1/MOD_2/MOD_3/MOD_64......................... 108
MOD_2: Monitoring 32 channels on S7-300/400 SM modules without diagnostic capability......................................................................................................................... 109 Description of MOD_2...................................................................................................... 109 I/Os of MOD_1/MOD_2..................................................................................................... 113 Message texts and associated values of MOD_1/MOD_2/MOD_3/MOD_64......................... 114
MOD_3: Monitoring up to 16 channels on S7-200/300/400 SM modules without diagnostic capability ........................................................................................................ 115 Description of MOD_3...................................................................................................... 115 I/Os of MOD_3 ................................................................................................................. 119 Message texts and associated values of MOD_1/MOD_2/MOD_3/MOD_64......................... 121
MOD_4: Monitoring ET 200S modules downstream of a Y-Link ......................................... 122 Description of MOD_4...................................................................................................... 122 I/Os of MOD_4 ................................................................................................................. 125 Message texts and associated values of MOD_4 ................................................................ 127
MOD_64: Monitoring 64 channels on S7-300 SM modules without diagnostic capability... 128
Basis Library (V9.0 SP3)
4
Function Manual, 06/2019, A5E40797470-AD
Table of contents
6.21.1 6.21.2 6.21.3
6.22 6.22.1 6.22.2 6.22.3
6.23 6.23.1 6.23.2 6.23.3
6.24 6.24.1 6.24.2 6.24.3
6.25
6.25.1 6.25.2 6.25.3
6.26
6.26.1 6.26.2 6.26.3
6.27 6.27.1 6.27.2 6.27.3
6.28
6.28.1 6.28.2 6.28.3
6.29
6.29.1 6.29.2 6.29.3
6.30 6.30.1 6.30.2 6.30.3
6.31 6.31.1 6.31.2 6.31.3
Description of MOD_64.................................................................................................... 128 I/Os of MOD_64 ............................................................................................................... 131 Message texts and associated values of MOD_1/MOD_2/MOD_3/MOD_64......................... 133
MOD_CENTRAL: Monitoring external CP and IM ................................................................ 134 Description of MOD_CENTRAL .......................................................................................... 134 I/Os of MOD_CENTRAL ..................................................................................................... 135 Message texts and associated values of MOD_CENTRAL .................................................... 136
MOD_CP: CP 341 diagnostics............................................................................................ 137 Description of MOD_CP .................................................................................................... 137 I/Os of MOD_CP ............................................................................................................... 140 Message texts and associated values of MOD_CP .............................................................. 142
MOD_CP_PN: Monitoring of serial communication modules.............................................. 143 Description of MOD_CP_PN .............................................................................................. 143 I/Os of MOD_CP_PN.......................................................................................................... 143 Message texts and associated values of MOD_CP_PN ........................................................ 145
MOD_D1: Monitoring up to 16 channels on S7-300/400 SM modules with diagnostic functions ......................................................................................................................... 146 Description of MOD_D1.................................................................................................... 146 I/Os of MOD_D1/MOD_D2 ................................................................................................ 152 Message texts and associated values of MOD_D1.............................................................. 154
MOD_D16_PN: Monitoring S7-300 SM modules with up to 16 channels and with diagnostics functions ....................................................................................................... 155 Description of MOD_D16_PN............................................................................................ 155 I/Os of MOD_D16_PN/MOD_D24_PN ................................................................................ 156 Message texts and associated values of MOD_D16_PN/MOD_D24_PN ............................... 158
MOD_D16_S7P: Diagnostic module check (<=16 channels)............................................... 162 Description of MOD_D16_S7P .......................................................................................... 162 I/Os of MOD_D16_S7P...................................................................................................... 162 Message texts and associated values of MOD_D16_S7P .................................................... 164
MOD_D2: Monitoring up to 32 channels of S7-300/400 SM modules with diagnostic functions ......................................................................................................................... 166 Description of MOD_D2.................................................................................................... 166 I/Os of MOD_D1/MOD_D2 ................................................................................................ 172 Message texts and associated values of MOD_D2.............................................................. 174
MOD_D24_PN: Monitoring S7-300 SM modules with up to 24 channels and with diagnostics functions ....................................................................................................... 176 Description of MOD_D24_PN............................................................................................ 176 I/Os of MOD_D16_PN/MOD_D24_PN ................................................................................ 176 Message texts and associated values of MOD_D16_PN/MOD_D24_PN ............................... 178
MOD_D3: Monitoring of hybrid modules with diagnostic capability................................... 182 Description of MOD_D3.................................................................................................... 182 I/Os of MOD_D3 ............................................................................................................... 188 Message texts and associated values of MOD_D3.............................................................. 190
MOD_D32_PN: PN diagnostic block check (32 channels) ................................................... 191 Description of MOD_D32_PN............................................................................................ 191 I/Os of MOD_D32_PN ....................................................................................................... 192 Message texts and associated values of MOD_D32_PN...................................................... 193
Basis Library (V9.0 SP3)
Function Manual, 06/2019, A5E40797470-AD
5
Table of contents
6.32
6.32.1 6.32.2 6.32.3
6.33
6.33.1 6.33.2 6.33.3
6.34 6.34.1 6.34.2 6.34.3
6.35 6.35.1 6.35.2 6.35.3
6.36 6.36.1 6.36.2 6.36.3
6.37 6.37.1 6.37.2 6.37.3
6.38 6.38.1 6.38.2 6.38.3
6.39 6.39.1 6.39.2 6.39.3
6.40
6.40.1 6.40.2 6.40.3
6.41 6.41.1 6.41.2 6.41.3
6.42
6.42.1 6.42.2
MOD_D8: Monitoring up to 8 channels on S7-300/400 SM modules with diagnostic functions ......................................................................................................................... 198 Description of MOD_D8.................................................................................................... 198 I/Os of MOD_D8 ............................................................................................................... 200 Message texts and associated values of MOD_D8.............................................................. 202
MOD_D8_PN: Monitoring S7-300 SM modules with up to 8 channels and with diagnostics functions ......................................................................................................................... 203 Description of MOD_D8_PN.............................................................................................. 203 I/Os of MOD_D8_PN ......................................................................................................... 203 Message texts and associated values of MOD_D8_PN........................................................ 205
MOD_D8_S7P: Diagnostic module check (<=8 channels)................................................... 207 Description of MOD_D8_S7P ............................................................................................ 207 I/Os of MOD_D8_S7P........................................................................................................ 208 Message texts and associated values of MOD_D8_S7P ...................................................... 210
MOD_DRV: Monitoring of drive blocks with diagnostics functions ..................................... 211 Description of MOD_DRV.................................................................................................. 211 I/Os of MOD_DRV ............................................................................................................. 212 Message texts and associated values of MOD_DRV............................................................ 215
MOD_HA: Monitoring device-specific diagnostics of HART field devices.............................. 216 Description of MOD_HA ................................................................................................... 216 I/Os of MOD_HA............................................................................................................... 222 Message texts and associated values of MOD_HA ............................................................. 224
MOD_HA_PN: Monitoring Device-Specific Diagnostics of HART Field Devices ..................... 225 Description of MOD_HA_PN ............................................................................................. 225 I/Os of MOD_HA_PN......................................................................................................... 225 Message texts and associated values of MOD_HA_PN ....................................................... 227
MOD_HA_PN1: Monitoring Device-Specific Diagnostics of HART Field Devices ................... 229 Description of MOD_HA_PN1 ........................................................................................... 229 I/Os of MOD_HA_PN1....................................................................................................... 229 Message texts and associated values of MOD_HA_PN1 ..................................................... 231
MOD_HA_S7P: Diagnostic module check (<=16 channels) ................................................ 233 Description of MOD_HA_S7P ............................................................................................ 233 I/Os of MOD_HA_S7P ....................................................................................................... 233 Message texts and associated values of MOD_HA_S7P ...................................................... 235
MOD_MS: Monitoring up to 16 channels on ET200S/X motor starter modules with diagnostic functions......................................................................................................... 237 Description of MOD_MS ................................................................................................... 237 I/Os of MOD_MS .............................................................................................................. 241 Message texts and associated values of MOD_MS ............................................................. 243
MOD_SWT: Monitoring of Switch blocks with diagnostics functions .................................. 244 Description of MOD_SWT ................................................................................................. 244 I/Os of MOD_SWT............................................................................................................. 245 Message texts and associated values of MOD_SWT ........................................................... 247
MOD_PAL0: Diagnosing a DPV0 PA slave (via DP/PA coupler downstream of a DP/PA link DPV1) .............................................................................................................................. 249 Description of MOD_PAL0 ................................................................................................ 249 I/Os of MOD_PAL0............................................................................................................ 251
Basis Library (V9.0 SP3)
6
Function Manual, 06/2019, A5E40797470-AD
Table of contents
6.42.3
6.43
6.43.1 6.43.2 6.43.3
6.44 6.44.1 6.44.2 6.44.3
6.45 6.45.1 6.45.2 6.45.3
6.46 6.46.1 6.46.2 6.46.3
6.47 6.47.1 6.47.2 6.47.3
6.48 6.48.1 6.48.2 6.48.3
6.49 6.49.1 6.49.2 6.49.3
6.50 6.50.1 6.50.2 6.50.3
6.51 6.51.1 6.51.2 6.51.3
6.52 6.52.1 6.52.2 6.52.3
6.53 6.53.1 6.53.2 6.53.3
Message texts and associated values of MOD_PAL0 .......................................................... 253
MOD_PAX0: Diagnosing a DPV0 PA slave (via DP/PA coupler with connection to a DP master system) ................................................................................................................ 255 Description of MOD_PAX0 ................................................................................................ 255 I/Os of MOD_PAX0 ........................................................................................................... 257 Message texts and associated values of MOD_PAX0 .......................................................... 259
MOD_ENME: Diagnostics for modules of the Energy Meter type ........................................ 261 Description of MOD_ENME............................................................................................... 261 I/Os of MOD_ENME .......................................................................................................... 261 Message texts and associated values of MOD_ENME......................................................... 264
MOD_ENME_S7P: Diagnostic function block for energy meter........................................... 265 Description of MOD_ENME_S7P ....................................................................................... 265 I/Os of MOD_ENME_S7P ................................................................................................... 266 Message texts and associated values of MOD_ENME_S7P.................................................. 268
OB_BEGIN: CPU Diagnostics and AS Connection Diagnostics ............................................. 270 Description of OB_BEGIN.................................................................................................. 270 I/Os of OB_BEGIN ............................................................................................................. 274 Message texts and associated values of OB_BEGIN............................................................ 275
OB_BEGIN_PN: CPU diagnostics ........................................................................................ 279 Description of OB_BEGIN_PN ............................................................................................ 279 I/Os of OB_BEGIN_PN ....................................................................................................... 279 Message texts and associated values of OB_BEGIN_PN ...................................................... 281
OB_BEGIN_HPN: H-CPU diagnostics .................................................................................. 285 Description of OB_BEGIN_HPN.......................................................................................... 285 I/Os of OB_BEGIN_HPN ..................................................................................................... 285 Message texts and associated values of OB_BEGIN_HPN.................................................... 287
OB_DIAG1: OB diagnostics for avoiding stoppages in DPV1 master systems ....................... 292 Description of OB_DIAG1.................................................................................................. 292 I/Os of OB_DIAG1 ............................................................................................................. 295 Message texts and associated values of OB_DIAG1............................................................ 297
OB_DIAG1_PN: OB diagnostics for avoiding stoppages in DPV1 master systems ................. 298 Description of OB_DIAG1_PN............................................................................................ 298 I/Os of OB_DIAG1_PN ....................................................................................................... 298 Message texts and associated values of OB_DIAG1_PN...................................................... 300
OB_DIAG2: OB Diagnostic Function - DP/PA Link - Extended Fieldbus Diagnostics............... 301 Description of OB_DIAG2.................................................................................................. 301 I/Os of OB_DIAG2 ............................................................................................................. 303 Message texts and associated values of OB_DIAG2............................................................ 304
OB_DIAG_NC: OB diagnostic for network devices .............................................................. 305 Description of OB_DIAG_NC ............................................................................................. 305 I/Os of OB_DIAG_NC......................................................................................................... 306 Message texts and associated values of OB_DIAG_NC ....................................................... 309
OB_DIAGF: Monitoring of the FF link and coupler ............................................................. 310 Description of OB_DIAGF.................................................................................................. 310 I/Os of OB_DIAGF ............................................................................................................. 312 Message texts and associated values of OB_DIAGF............................................................ 313
Basis Library (V9.0 SP3)
Function Manual, 06/2019, A5E40797470-AD
7
Table of contents
6.54
6.54.1 6.54.2 6.54.3
6.55 6.55.1 6.55.2
6.56 6.56.1 6.56.2
6.57 6.57.1 6.57.2
6.58 6.58.1 6.58.2
6.59
6.59.1 6.59.2
6.60 6.60.1 6.60.2
6.61 6.61.1 6.61.2
6.62 6.62.1 6.62.2
6.63 6.63.1 6.63.2 6.63.3
6.64
6.64.1 6.64.2 6.64.3
6.65
6.65.1 6.65.2 6.65.3
6.66
OB_DIAGF2: Monitoring device-specific diagnostics for Foundation Fieldbus Compact Link IM 655-2 FF .............................................................................................................. 315 Description of OB_DIAGF2................................................................................................ 315 I/Os of OB_DIAGF2 ........................................................................................................... 316 Message texts and associated values of OB_DIAGF2.......................................................... 317
OB_END: Reset stack pointer of OB_BEGIN........................................................................ 318 Description of OB_END..................................................................................................... 318 I/Os of OB_END ................................................................................................................ 319
OB5X2OB5: OB5X PN information in STRUCT OB55, OB56, OB57 ..................................... 320 Description of OB5X2OB5 ................................................................................................ 320 I/Os of OB5X2OB5............................................................................................................ 320
OR_16_PN: QUALITY of 2 redundant Module (<= 16 Channels) ......................................... 321 Description of OR_16_PN ................................................................................................. 321 I/Os of OR_16_PN............................................................................................................. 322
OR_32_PN: QUALITY of 2 redundant Module (<= 32 Channels) ......................................... 324 Description of OR_32_PN ................................................................................................. 324 I/Os of OR_32_PN............................................................................................................. 325
OR_32_TS: OR value status of two redundant time-stamped signal modules, max. 32 channels.......................................................................................................................... 327 Description of OR_32_TS.................................................................................................. 327 I/Os of OR_32_TS ............................................................................................................. 328
OR_32TPN: Time stamps of 2 redundant module (1..32 Channels) ................................... 330 Description of OR_32TPN ................................................................................................. 330 I/Os of OR_32TPN............................................................................................................. 331
OR_8_PN: Quality of 2 redundant modules (<=8 Channels)............................................... 333 Description of OR_8_PN ................................................................................................... 333 I/Os of OR_8_PN............................................................................................................... 335
OR_H16PN: QUALITY of 2 redundant multi function Modules (<= 16 HART Channels) ....... 337 Description of OR_H16PN................................................................................................. 337 I/Os of OR_H16PN ............................................................................................................ 338
OR_HA16C: OR value status of 2 redundant HART modules, max. 16 channels .................. 340 Description of OR_HA16C................................................................................................. 340 I/Os of OR_M_8C / OR_M_16C / OR_M_32C / OR_HA16C.................................................... 343 Message texts and associated values of OR_HA16C........................................................... 345
OR_M_16C: OR value status of 2 redundant signal modules, max. 16 channels, channel granular........................................................................................................................... 348 Description of OR_M_16C ................................................................................................ 348 I/Os of OR_M_8C / OR_M_16C / OR_M_32C / OR_HA16C.................................................... 348 Message texts and associated values of OR_M_16C .......................................................... 351
OR_M_32C: OR value status of 2 redundant signal modules, max. 32 channels, channel granular........................................................................................................................... 353 Description of OR_M_32C ................................................................................................ 353 I/Os of OR_M_8C / OR_M_16C / OR_M_32C / OR_HA16C.................................................... 353 Message texts and associated values of OR_M_32C .......................................................... 356
OR_M_8C: OR value status of 2 redundant signal modules, max. 8 channels, channel granular........................................................................................................................... 360
Basis Library (V9.0 SP3)
8
Function Manual, 06/2019, A5E40797470-AD
Table of contents
6.66.1 6.66.2 6.66.3
6.67 6.67.1 6.67.2
6.68 6.68.1 6.68.2
6.69 6.69.1 6.69.2 6.69.3 6.69.4 6.69.5 6.69.6 6.69.7
6.70 6.70.1 6.70.2
6.71 6.71.1 6.71.2
6.72 6.72.1 6.72.2 6.72.3
6.73 6.73.1 6.73.2 6.73.3
6.74 6.74.1 6.74.2 6.74.3
6.75 6.75.1 6.75.2 6.75.3
6.76 6.76.1 6.76.2 6.76.3
6.77 6.77.1 6.77.2
Description of OR_M_8C .................................................................................................. 360 I/Os of OR_M_8C / OR_M_16C / OR_M_32C / OR_HA16C.................................................... 362 Message texts and associated values of OR_M_8C ............................................................ 364
OR_MHA_CO: Multi HART variable read coordination (0 - 15 Channel) - redundancy.......... 366 Description of OR_MHA_CO.............................................................................................. 366 I/Os of OR_MHA_CO ......................................................................................................... 367
OR_MHA1_CO: Coordinates multiHART variables - redundancy ......................................... 368 Description of OR_MHA1_CO............................................................................................ 368 I/Os of OR_MHA1_CO ....................................................................................................... 369
PADP_L0x: Monitoring DP/PA slaves .................................................................................. 370 Description of PADP_L00 .................................................................................................. 370 I/Os of PADP_L00/PADP_L01/PADP_L02 ............................................................................. 374 Message texts and associated values of PADP_L00 ............................................................ 375 Description of PADP_L01 .................................................................................................. 376 Message texts and associated values of PADP_L01 ............................................................ 379 Description of PADP_L02 .................................................................................................. 380 Message texts and associated values of PADP_L02 ............................................................ 384
PADP_L10: Monitoring PA slaves downstream of DPV0 with up to 16 slots......................... 385 Description of PADP_L10 .................................................................................................. 385 I/Os of PADP_L10 ............................................................................................................. 390
PADP_L10_PN: Monitoring PA slaves downstream of DPV0 with up to 16 slots ................... 392 Description of PADP_L10_PN ............................................................................................ 392 I/Os of PADP_L10_PN........................................................................................................ 392
PAM_CD: Monitoring Compact Devices within the Package Unit ....................................... 393 Description of PAM_CD .................................................................................................... 393 I/Os of PAM_CD ................................................................................................................ 397 Messages and associated values of PAM_CD ..................................................................... 400
PAM_CPU: Monitoring CPUs within the Package Unit......................................................... 400 Description of PAM_CPU................................................................................................... 400 I/Os of PAM_CPU .............................................................................................................. 405 Message text and associated values of PAM_CPU .............................................................. 407
PAM_IM: Monitoring Interface Modules within the Package Unit ..................................... 408 Description of PAM_IM ..................................................................................................... 408 I/Os of PAM_IM ................................................................................................................ 412 Messages and associated values of PAM_IM...................................................................... 415
PAM_SM: Monitoring Signal Modules within the Package Unit ......................................... 416 Description of PAM_SM .................................................................................................... 416 I/Os of PAM_SM ............................................................................................................... 419 Messages and associated values of PAM_SM..................................................................... 421
PDM_MS: Monitoring of the maintenance status .............................................................. 422 Description of PDM_MS.................................................................................................... 422 I/Os of PDM_MS ............................................................................................................... 422 Message texts and associated values of PDM_MS.............................................................. 423
PNTS2BCD: Converts PNIO time to BCD format ................................................................. 425 Description of PNTS2BCD ................................................................................................. 425 I/Os of PNTS2BCD............................................................................................................. 425
Basis Library (V9.0 SP3)
Function Manual, 06/2019, A5E40797470-AD
9
Table of contents
6.78 6.78.1 6.78.2
6.79 6.79.1 6.79.2
6.80 6.80.1
6.81 6.81.1 6.81.2 6.81.3
6.82 6.82.1 6.82.2 6.82.3
6.83 6.83.1 6.83.2 6.83.3
6.84 6.84.1 6.84.2 6.84.3
6.85 6.85.1 6.85.2 6.85.3
6.86 6.86.1 6.86.2 6.86.3
6.87 6.87.1 6.87.2
6.88 6.88.1 6.88.2
6.89 6.89.1 6.89.2
6.90 6.90.1 6.90.2
6.91
PNTS2DT: Converts PNIO time to DT format ..................................................................... 426 Description of PNTS2DT.................................................................................................... 426 I/Os of PNTS2DT ............................................................................................................... 426
PNTS2ISP: Converts PNIO time to ISP format .................................................................... 427 Description of PNTS2ISP ................................................................................................... 427 I/Os of PNTS2ISP .............................................................................................................. 427
PO_UPDAT: Output Process Image .................................................................................... 428 PO_UPDAT: Output Process Image .................................................................................... 428
PS: Power supply monitoring............................................................................................ 429 Description of PS.............................................................................................................. 429 I/Os of PS ......................................................................................................................... 431 Message texts and associated values of PS........................................................................ 432
RACK: Rack monitoring..................................................................................................... 433 Description of RACK ......................................................................................................... 433 I/Os of RACK..................................................................................................................... 436 Message texts and associated values of RACK ................................................................... 437
RACK_CFU: PROFINET CFU function block ......................................................................... 438 Description of RACK_CFU ................................................................................................. 438 I/Os of RACK_CFU............................................................................................................. 439 Message texts and associated values of RACK_CFU ........................................................... 441
RACK_PN: Rack monitoring............................................................................................... 443 Description of RACK_PN ................................................................................................... 443 I/Os of RACK_PN............................................................................................................... 443 Message texts and associated values of RACK_PN ............................................................. 445
RACK_PN1: PROFINET RACK Function Block - R1 Device ..................................................... 446 Description of RACK_PN1 ................................................................................................. 446 I/Os of RACK_PN1............................................................................................................. 448 Message texts and associated values of RACK_PN1 ........................................................... 449
RACK_PNT: PROFINET RACK function block - R1 device ...................................................... 451 Description of RACK_PNT.................................................................................................. 451 I/Os of RACK_PNT ............................................................................................................. 452 Message texts and associated values of RACK_PNT............................................................ 455
RED_AI: Status processing of redundant AI modules.......................................................... 458 Description of RED_AI....................................................................................................... 458 I/Os of RED_AI .................................................................................................................. 459
RED_AIH: Status processing of redundant AI HART modules (<= 8 CHANNELS) .................. 461 Description of RED_AIH .................................................................................................... 461 I/Os of RED_AIH................................................................................................................ 462
RED_AQ: Status processing of redundant AQ modules....................................................... 464 Description of RED_AQ ..................................................................................................... 464 I/Os of RED_AQ ................................................................................................................ 465
RED_AQH: Status processing of redundant AQ HART modules (<= 8 Channels) .................. 467 Description of RED_AQH................................................................................................... 467 I/Os of RED_AQH .............................................................................................................. 468
RED_DI: Status processing of redundant DI modules ......................................................... 470
Basis Library (V9.0 SP3)
10
Function Manual, 06/2019, A5E40797470-AD
Table of contents
6.91.1 6.91.2
Description of RED_DI ...................................................................................................... 470 I/Os of RED_DI.................................................................................................................. 471
6.92 6.92.1 6.92.2
RED_DQ: Status processing of redundant DQ modules ...................................................... 473 Description of RED_DQ..................................................................................................... 473 I/Os of RED_DQ ................................................................................................................ 474
6.93 6.93.1 6.93.2
RED_F: Status processing of redundant F modules ............................................................ 476 Description of RED_F........................................................................................................ 476 I/Os of RED_F ................................................................................................................... 478
6.94 6.94.1 6.94.2
RED_MF: Status processing of redundant multi function modules ..................................... 479 Description of RED_MF..................................................................................................... 479 I/Os of RED_MF ................................................................................................................ 480
6.95 6.95.1 6.95.2 6.95.3
SUBNET: DP master system monitoring............................................................................. 482 Description of SUBNET ..................................................................................................... 482 I/Os of SUBNET................................................................................................................. 485 Message texts and associated values of SUBNET ............................................................... 487
6.96 6.96.1 6.96.2 6.96.3
SUBNET_PN: Monitoring of the PN IO system .................................................................... 488 Description of SUBNET_PN ............................................................................................... 488 I/Os of SUBNET_PN........................................................................................................... 488 Message texts and associated values of SUBNET_PN ......................................................... 490
6.97 6.97.1 6.97.2
WRDS_CO: Coordinates WRREC DS128 for MRC ................................................................. 491 Description of WRDS_CO ................................................................................................ 491 I/Os of WRDS_CO.............................................................................................................. 492
7 Family: @PAM .................................................................................................................................... 495
7.1 7.1.1 7.1.2
FB_DB_CD: Interface FB for DB_PAM_CD ........................................................................... 495 Description of FB_DB_CD.................................................................................................. 495 I/Os of FB_DB_CD ............................................................................................................. 497
7.2 7.2.1 7.2.2
FB_DB_CPU: Interface FB for DB_PAM_CPU ....................................................................... 498 Description of FB_DB_CPU................................................................................................ 498 I/Os of FB_DB_CPU ........................................................................................................... 500
7.3 7.3.1 7.3.2
FB_DB_IM: Interface FB for DB_PAM_IM ............................................................................ 502 Description of FB_DB_IM .................................................................................................. 502 I/Os of FB_DB_IM ............................................................................................................. 504
7.4 7.4.1 7.4.2
PAM_IF: Interface block to PAM Diagnostic Blocks ............................................................. 505 Description of PAM_IF ...................................................................................................... 505 I/Os of PAM_IF.................................................................................................................. 509
7.5 7.5.1 7.5.2
DB_PAM_CD: DB of CD data for reading from PAM_Station ............................................... 511 Description of DB_PAM_CD............................................................................................... 511 Structure of DB_PAM_CD .................................................................................................. 511
7.6 7.6.1 7.6.2
DB_PAM_CPU: DB of CPU data for reading from PAM_Station ............................................ 512 Description of DB_PAM_CPU............................................................................................. 512 Structure of DB_PAM_CPU ................................................................................................ 513
7.7 7.7.1 7.7.2
DB_PAM_IM: DB of IM data for reading from PAM_Station ................................................. 513 Description of DB_PAM_IM ............................................................................................... 513 Structure of DB_PAM_IM .................................................................................................. 514
Basis Library (V9.0 SP3)
Function Manual, 06/2019, A5E40797470-AD
11
Table of contents
8 Internal block..................................................................................................................................... 515
8.1
ChkREAL: Internal Block.................................................................................................... 515
8.2
LED_STAT: Processing of LED Status .................................................................................. 515
8.3
QC_CHNG: Internal block ................................................................................................. 515
9 Appendix............................................................................................................................................ 517
9.1
MODE settings for FF devices ........................................................................................... 517
9.2
MODE settings for SM modules ........................................................................................ 517
9.3
OMODE settings for SM modules...................................................................................... 527
9.4
MODE settings for field devices......................................................................................... 528
9.5
OMODE settings for field devices ...................................................................................... 529
9.6
Error Information of Output Parameter MSG_STAT ............................................................ 530
9.7
Addressing....................................................................................................................... 530
9.8
Message Classes .............................................................................................................. 531
9.9
Dependencies .................................................................................................................. 532
9.10 9.10.1 9.10.2
Status displays ................................................................................................................. 533 Maintenance status MS .................................................................................................... 533 PA field device status and diagnostics information ............................................................ 533
9.11 9.11.1
9.11.2 9.11.3 9.11.4 9.11.5 9.11.6 9.11.7 9.11.8 9.11.9 9.11.10
9.11.11 9.11.12 9.11.13 9.11.14 9.11.15 9.11.16
Text libraries .................................................................................................................... 536 Text library for PAM_CPU/ PAM_CD/PAM_IM/PAM_SM/PAM_IF/FB_DB_CPU/FB_DB_CD/ FB_DB_IM ........................................................................................................................ 536 Text library for MOD_SWT ................................................................................................ 536 Text library for FF_MOD32 ............................................................................................... 536 Text Library for MOD_PAL0, MOD_PAX0............................................................................ 537 Text Library for PADP_L00, PADP_L01, PADP_L02 .............................................................. 537 Text Library for DREP, DREP_L ........................................................................................... 537 Text library for MOD_1, MOD_2, MOD_3, MOD_64, MOD_D2, MOD_CP ............................ 537 Text Library for MOD_D1 .................................................................................................. 539 Text library for MOD_D3, MOD_D8 ................................................................................... 540 Text library for MOD_D8_PN (FB197) / MOD_D16_PN (FB198) / MOD_D24_PN (FB199) / MOD_ENME (FB 419) ....................................................................................................... 542 Text library for MOD_ D8_S7P, MOD_ D16_S7P ................................................................. 545 Text library for MOD_CP_PN (FB201) ................................................................................ 546 Text Library for MOD_MS ................................................................................................. 547 Text Library for OB_BEGIN ................................................................................................ 549 Text library for OB_BEGIN_PN (FB130) / OB_BEGIN_HPN (FB205)....................................... 549 Text library for MOD_ENME_S7P....................................................................................... 549
Index .................................................................................................................................................. 553
Basis Library (V9.0 SP3)
12
Function Manual, 06/2019, A5E40797470-AD
Security information
1
Siemens provides products and solutions with industrial security functions that support the secure operation of plants, systems, machines and networks.
In order to protect plants, systems, machines and networks against cyber threats, it is necessary to implement and continuously maintain a holistic, state-of-the-art industrial security concept. Siemens' products and solutions constitute one element of such a concept.
Customers are responsible for preventing unauthorized access to their plants, systems, machines and networks. Such systems, machines and components should only be connected to an enterprise network or the internet if and to the extent such a connection is necessary and only when appropriate security measures (e.g. firewalls and/or network segmentation) are in place.
For additional information on industrial security measures that may be implemented, please visit https://www.siemens.com/industrialsecurity.
Siemens' products and solutions undergo continuous development to make them more secure. Siemens strongly recommends that product updates are applied as soon as they are available and that the latest product versions are used. Use of product versions that are no longer supported, and failure to apply the latest updates may increase customer's exposure to cyber threats.
To stay informed about product updates, subscribe to the Siemens Industrial Security RSS Feed under https://www.siemens.com/industrialsecurity.
Basis Library (V9.0 SP3)
Function Manual, 06/2019, A5E40797470-AD
13
Security information
Basis Library (V9.0 SP3)
14
Function Manual, 06/2019, A5E40797470-AD
General Information About Block Description
2
The setup of the block description is always uniform and contains the following sections:
Header of the block description
Example: CTRL_PID: PID controller block
The header begins with the type name of the block (e.g., ""CTRL_PID"). This symbol name is entered in the symbol table and must be unique within the project. In addition to the type name, you will also see a keyword indicating the purpose or function of the block (e.g., "PID controller block").
Object name (type + number)
FB x
The object name for the block type is made up of the type of implementation (function block = FB, function = FC) and the block number = x.
Links for displaying block I/Os Example: · CTRL_PID block I/Os Click the "Block I/Os" link to display a list of block I/Os for the designated block.
Links for displaying the block icon and faceplate If the block is intended for operator control and monitoring and a block icon and faceplate exist, the corresponding image and description can be displayed directly by clicking these links.
Example:
· CTRL_PID block icon
· CTRL_PID faceplate
Function
Here, you will find a brief description of the block function. You will find additional information about complex blocks in the "How it works" section.
How it works
Here, you will find more detailed information, for example about the function of specific inputs, operating modes or time sequences. You must be familiar with these relationships in order to use the block effectively.
Basis Library (V9.0 SP3)
Function Manual, 06/2019, A5E40797470-AD
15
General Information About Block Description
Calling OBs
Here you will find information on the organization blocks (OBs), in which the described block must be installed. If the CFC is used, the block is automatically installed in the cyclic OB (cyclic interrupt) and in the OBs listed in the block's task list (for eample in restart OB100).
CFC generates the required OBs during compilation. If you use the blocks without CFC, you will have to program these OBs and call their instance within the blocks.
Error handling
The ENO Boolean block output indicates the error in the CFC chart. The value is equivalent to the BIE (binary result in STEP 7 STL, after completion of the block) or OK bit (in SCL notation) and indicates:
ENO = BIE = OK = 1 (TRUE) -> The result of the block is free of errors.
ENO = BIE = OK = 0 (FALSE) -> Invalid result or constraints (for example, input values and modes).
The FBs also return the inverted BIE at the QERR output of the instance DB.
QERR = NOT ENO
The error message is generated in two separate operations:
· The operating system detects a processing error (e.g. value overflow, system functions called return an error ID with BIE = 0). This is a system function and is not specifically mentioned in the block description.
· The block algorithm checks for functional invalidity of values and operating modes. These error events are logged in the block description.
You can evaluate the error display, for example, to generate messages or use substitute values for invalid results. You will find more information about messages in the "Message blocks" section.
Startup characteristics
The different startup behaviors are as follows:
· Initial start The block is called for the first time from the OB in which it has been inserted. This is usually the OB that performs the standard, process-specific operations (for example, the cyclic interrupt OB). The block adopts a status that conforms to its input parameters. These may be default values (additional information in "I/Os" section) or values you have already configured, for example, in CFC. The initial startup characteristics are not described separately unless the block does not conform to this rule.
· Startup The block is executed once during CPU startup. The block is called in the startup OB (where it is additionally installed either automatically in the ES or manually in STEP 7). In this case, the startup characteristics are described. Please note that the block outputs have default values and that these can take effect during the CPU startup with other blocks, if these are processed first. The correct startup behavior of the blocks is the responsibility of the configuration engineer.
Basis Library (V9.0 SP3)
16
Function Manual, 06/2019, A5E40797470-AD
General Information About Block Description
Time response
A block assigned this function must be installed in a cyclic interrupt OB. It calculates its time constants/parameters on the basis of its sampling time (the time which elapses between two consecutive cyclic operations).
In a CFC configuration on ES, the sampling time is also determined by the segmentation of the runtime group, which ensures that the block is not executed during every OB run.
This sampling time is entered at the I/Os, in the SAMPLE_T parameter.
When configuring with CFC, this occurs automatically once the block has been inserted in the OB and the runtime group. For this reason, this input is set to invisible in CFC.
During the STEP 7 configuration, you set the time response manually.
Time response is mentioned only if the block has been assigned this feature.
Message response
A block with message response reports various events to the higher level OS. Existing parameters required for the generation of messages are documented.
Blocks without message response can be expanded with additional message blocks. A reference to the message response is found in the description of the individual message blocks.
I/Os
The I/Os of the block represent its data interface. These I/Os can be used either to transfer data to the block or to fetch results from the block.
I/O (parameter)
U1
.....
Meaning Addend 1
Data type REAL
Default 0
The "I/O" table lists all I/O parameters of the block type. You can access these lists using the engineering tools. They are in alphabetical order. Elements accessible only via the block algorithm (internal variables) are not listed. The meaning of the columns is as follows:
· I/O Name of the parameter, derived from the English, e.g. PV_IN = Process Variable INput (process variable, controlled variable). The SIMATIC naming conventions have been applied. The block representation in CFC as supplied is as follows: I/O name in bold characters = I/O is visible, regular = I/O is invisible.
· Meaning Function (possibly also short description)
· Data type S7 data type of the parameter (BOOL, REAL, etc.)
· Default (default value) The value of the parameter before the block runs for the first time (unless changed in the configuration)
Basis Library (V9.0 SP3)
Function Manual, 06/2019, A5E40797470-AD
17
General Information About Block Description
Basis Library (V9.0 SP3)
18
Function Manual, 06/2019, A5E40797470-AD
Display for avoiding stop without asset management
3
Block icon "OB_BEGIN_BASE" / "OB_BEGIN_PN_BASE" / "OB_BEGIN_HPN_BASE "
If your system does not have ASSET diagnostics, a separate block icon for the avoidance of stop is provided on the OS in the template @TemplateBasisLibraryV8.
Configuration
You configure a corresponding block icon for each AS. You then interconnect each block icon with the corresponding structure variable.
To achieve all the required interconnections to the block icon, it is best to use the PCS 7 WinCC Wizard for interconnecting faceplates to process tags. In the tag dialog "List of all structure variables", you can select the relevant block instance.
Note on the faceplate
In the OB_BEGIN/ OB_BEGIN_PN/OB_BEGIN_HPN and CPU_RT faceplates without asset management, the message view, the performance view and the detailed views (OB3x and OB8x/ OB1) are displayed if SFC78 is supported on the AS. If SFC78 is not supported, only the message view of the faceplate is displayed.
The identification view and parameter view are not shown.
Basis Library (V9.0 SP3)
Function Manual, 06/2019, A5E40797470-AD
19
Display for avoiding stop without asset management
Basis Library (V9.0 SP3)
20
Function Manual, 06/2019, A5E40797470-AD
Icons for user-defined SFC types
Icons for user-defined SFC types The following icons are available in the template for user-defined SFC types "@TemplateBasisLibraryV8".
4
For more information, refer to the manual SFC Visualization - Manual for S7 or in Simatic Manager to the "SFC properties" dialog, "OS" tab or the "Properties for SFC type/SFC instance" dialog, "Options" tab.
Basis Library (V9.0 SP3)
Function Manual, 06/2019, A5E40797470-AD
21
Icons for user-defined SFC types
Basis Library (V9.0 SP3)
22
Function Manual, 06/2019, A5E40797470-AD
Family: CONTROL
5
5.1
FM_CO: Coordination of function blocks which read data records
5.1.1
Description of FM_CO
Object name (type + number) FB 79 · FM_CO block I/Os (Page 25)
Function
The block coordinates the data record reading of the blocks
Block FM_CNT FMCS_PID FMT_PID REAS355P FmCont FmTemp
Library PCS 7 Basic Library PCS 7 Library PCS 7 Library PCS 7 Library PCS 7 APL PCS 7 APL
Module FM350-1, FM350-2 FM355 FM355-2 FM355, FM355-2 FM355 FM355-2
The block is installed and the parameters interconnected by the driver generator.
Block
Configuration of the coor- Interconnections between FM_CO and the data re-
dination number
cord reading instance: FM_CO - DS reading instance
FM_CNT, FMCS_PID
CO_NO
EN_CO_x <-> EN_CO
FM_PID, READ355P
CO_NO
ENCOx_yy <-> ENCO
FmCont, FmTemp CoordNo
EN_CO_x <-> EnCoord
ENCOx_yy <-> EnCoNum
Where:
x = Sequence of data record reading blocks (0 to 7)
yy = Coordination number within a sequence (0 to 63)
It is possible to include data record reading blocks of other modules in the coordination.
How it works
The FM_CO block can start a maximum of 8 block sequences.
Basis Library (V9.0 SP3)
Function Manual, 06/2019, A5E40797470-AD
23
Family: CONTROL
5.1 FM_CO: Coordination of function blocks which read data records
The blocks connected to the output structure EN_COx check whether the current coordination number (EN_COx.CO_ACT) corresponds to their own coordination number (CO_NO/CoordNo). If this is the case, they read their data records from the module and reduce the coordination number EN_COx.CO_ACT by 1, so that the next block can read out its data records.
If the current coordination number of a sequence (EN_COx.CO_ACT) has a value less than 1, the FM_CO block determines the highest number assigned in sequence x based on its inputs ENCOx_yy. The data reading blocks supply the inputs ENCOx_yy with their respective coordination number via an interconnection. The highest coordination number is the number for which ENCOx_yy = yy still applies. The FM_CO module restarts the sequence in which it sets EN_COx.CO_ACT to this value.
This algorithm ensures that no more than one read data record operation ever takes place at any given time within the block sequence.
Calling OBs
The fastest cyclic interrupt OB of all OBs in which you have installed data reading block instances and OB100 as well.
Use in CFC
When using the CFC function "Generate Module Drivers", the block is automatically installed and the connections, such as those described under "Installation regulation" are made.
If you install, delete or move blocks of an existing block sequence in other OBs or runtime groups, the driver generator must be called.
Should the sequence not start up as expected (after CPU restart) or not continue to run (after downloading changes), you must set ACC_ID to 1.
Installation rules/capacity
One FM_CO is responsible for one DP master system and has 8 sequences with data record reading block instances that are coordinated in parallel. The first block sequence contains instances of the data recording reading blocks that relate to the DP slaves 1, 9, 17 and so on. The second block sequence contains instances of the data recording reading blocks that relate to the DP slaves 2, 10, 18 and so on. The same principle applies to the remainder of the eight block sequences.
Note
When an instance is added to a sequence by a data recording reading block, the sampling time of all instances in the sequence increases. If, for example, an instance from DP slave 9 is added to the sequence 1, then the sampling time of all instances of sequence 1 increases including the instances from DP slave 1.
Basis Library (V9.0 SP3)
24
Function Manual, 06/2019, A5E40797470-AD
Family: CONTROL 5.1 FM_CO: Coordination of function blocks which read data records
A sequence may contain up to 63 data recording reading instances of the following blocks:
Block FM_CNT
FMCS_PID, FMT_PID, FmCont, FmTemp
READ355P
Data record reading channels
Module
One instance of FM_CNT is required for each FM350-1, FM350-2 module. 4 channels are read with one data re- cord read operation per cycle
The module has 4 controller channels. One channel is read with one data record read op- eration per cycle.
FM355, FM355-2
Certain process values of all 4 channels are read with one data record read operation per cycle.
FM355, FM355-2
The FM_CO must always be installed before the first data record reading instance in the fastest cyclic interrupt OB. The output structure EN_COx for the DP slave is connected to the input structures EN_COx or EnCoord of all data record reading instances that communicate with the controller modules of rack x. The output ENCO or EnCoNum of each data record reading instance is connected to an input ENCOx_yy (yy corresponds to the coordination number CO_NO or CoordNo assigned to each data recording reading instance) of the FM_CO block.
The selection of the cyclic interrupt OB depends on the CPU load. Note that the CPU has no reserves for other "Read data record" jobs if operating with eight or more DP slaves because only eight jobs can be buffered per DP master system. Simply inserting a module would lead to an overflow. It is advisable to operate only up to six DP slaves on a DP master system. The remaining DP slaves must be distributed on other DP master systems with further FM_CO blocks.
When selecting the cyclic OB, remember that the new data will be available at the earliest after two cycles. Make sure that the maximum runtime of this OB does not have any negative impact on overall system runtime as a result of the number of blocks installed. If the data recording reading block instances to be processed exceed the runtime limit, group the DP slaves with the FM350/FM355 modules in fast and slow control loops.
Startup characteristics EN_CO_x.CO_ACT = 1 is set at all outputs during startup (restart).
Time response Not available
Message functionality Not available
5.1.2
I/Os of FM_CO
The factory setting of the block display in the CFC is identified in the "I/O" column: I/O name bold = I/O visible, I/O name normal = I/O not visible.
Basis Library (V9.0 SP3)
Function Manual, 06/2019, A5E40797470-AD
25
Family: CONTROL 5.1 FM_CO: Coordination of function blocks which read data records
You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15)".
Input parameters
I/O (parameter) DIAG_BUF
ENCOx_yy
Meaning
Data type
Entry in diagnostic buffer (relevant for maintenance person- BOOL nel)
The coordination number yy is assigned in the rack x if the BYTE input has the value yy (x = 0 - 7, yy = 1 - 64)
Default 0 0
Output parameters
I/O (parameter)
EN_CO_x
Meaning
Data type
Coordination number of the block that can read data records STRUCT
Default 0
In/out parameters
I/O (parameter)
ACC_ID
Meaning Restart all sequences
Data type Default
BOOL
1
Basis Library (V9.0 SP3)
26
Function Manual, 06/2019, A5E40797470-AD
Family: @System
6
6.1
CONEC: Monitoring the AS connection status
6.1.1
Description of CONEC
Object name (type + number) FB 88 · CONEC Block I/Os (Page 29)
Area of application The CONEC block monitors the status of AS connections, and reports the associated error events.
Calling OBs
The block must be installed in the run sequence in the following OBs:
OB 100
Warm restart
Use in CFC
With the "Generate module drivers" CFC function, the CONEC block is automatically installed in the OBs listed above.
Function and method of operation
The CONEC block generates messages which are output at ALARM_8P to WinCC (see "Message response"). For connection diagnostics, SFC 87 (C_DIAG) is called at intervals of 10 seconds in the cyclic interrupt OB 32. Up to 128 simple and up to 64 redundant connections are monitored.
Note
The messages "Failure or loss of redundancy connection ID" are generated by each CPU of the two connected AS except when the CPU (or both H-CPUs) of an AS fails. The connection ID determines whether a message is output. If the connection ID >= 16#C00 no message is generated.
Basis Library (V9.0 SP3)
Function Manual, 06/2019, A5E40797470-AD
27
Family: @System 6.1 CONEC: Monitoring the AS connection status
Formation of the maintenance status MS If any connection in the CONEC block is detected as having failed, the "Maintenance alarm" maintenance status is output. If any connection in the CONEC block is detected as a redundancy loss, the "Maintenance demanded" maintenance status is output. If the messages are disabled via the parameter EN_MSG in the CONEC block, the maintenance status "Unchecked / Unknown" is output.
Error handling
Error handling for the block is limited to the evaluation of the error information of ALARM_8P. You will find additional information in the
"Error Information of Output Parameter MSG_STAT" (Page 530) section.
Startup characteristics
The CONEC block initializes the messages of ALARM_8P.
If there is a CPU with SFC 87, connection diagnostics is initialized. After this, there is a wait time of approx. 1 minute in the cyclic interrupt OB before the connection diagnostics messages are generated.
Overload behavior Not available
Time response For additional information, refer to "Message response".
Message response The block generates the following messages in the OBs listed below:
OB OB 32
Start Event
1 sec. cyclic interrupt or alter- native cyclic interrupt OB
Message
Failure connection ID: xx incoming/outgoing Loss of redundancy connection ID: xx entering/exiting state
If EN_MSG = FALSE, messaging is disabled.
Operator control and monitoring
If asset management is used in the project and the diagnostic screens have been generated, the faceplate can be called via its block icon.
For additional information, refer to the "Process Control System PCS 7; Maintenance Station" manual.
Basis Library (V9.0 SP3)
28
Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.1 CONEC: Monitoring the AS connection status
Additional information For additional information, refer to the sections: Message texts and associated values of CONEC (Page 30) Maintenance status MS (Page 533)
6.1.2
I/Os of CONEC
The factory setting of the block display in the CFC is identified in the "I/O" column:
I/O name bold = I/O visible, I/O name normal = I/O not visible.
You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15)".
Input parameters
I/O (parameter) DIAG_BUF
EN_MSG EV_IDx
MS SAMPLE_T
Meaning
Data type Default
Entry in diagnostic buffer (relevant for maintenance person- BOOL
0
nel)
1 = Enable message
BOOL
1
Message number for ALARM_8P_x
DWORD
0
(x = 1 - 24, assigned by the ES)
Maintenance status
DWORD
0
Sampling time OB in seconds
REAL
1.0
Output parameters
I/O (parameter) MSGSTAx O_MS QMSGERx
Meaning
Output STATUS of the ALARM_8P_x (x = 1 - 24) Maintenance status Error output of the ALARM_8P_x (x = 1 - 24)
Data type Default
WORD
0
DWORD
0
BOOL
0
Additional information For additional information, refer to the sections: Message texts and associated values of CONEC (Page 30) Maintenance status MS (Page 533)
Basis Library (V9.0 SP3)
Function Manual, 06/2019, A5E40797470-AD
29
Family: @System 6.1 CONEC: Monitoring the AS connection status
6.1.3
Message texts and associated values of CONEC
Assignment of message text and message class
Message block ALARM_8P
EV_ID1 to EV_ID16
Message number
1
2
Default message text
Failure connection ID: 16#@1%X@ Failure connection ID: 16#@2%X@
3
Failure connection ID: 16#@3%X@
4
Failure connection ID: 16#@4%X@
5
Failure connection ID: 16#@5%X@
6
Failure connection ID: 16#@6%X@
7
Failure connection ID: 16#@7%X@
8
Failure connection ID: 16#@8%X@
EV_ID17 to 1 EV_ID24
2
3
4
5
6
7
8
Loss of redundancy connection ID: 16#@1%X@
Loss of redundancy connection ID: 16#@2%X@
Loss of redundancy connection ID: 16#@3%X@
Loss of redundancy connection ID: 16#@4%X@
Loss of redundancy connection ID: 16#@5%X@
Loss of redundancy connection ID: 16#@6%X@
Loss of redundancy connection ID: 16#@7%X@
Loss of redundancy connection ID: 16#@8%X@
Message class (Page 531)
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Error
PLC Process Control Message Error
PLC Process Control Message Error
PLC Process Control Message Error
PLC Process Control Message Error
PLC Process Control Message Error
PLC Process Control Message Error
PLC Process Control Message Error
Basis Library (V9.0 SP3)
30
Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.2 CPU_RT: Determination of the runtime of OBs
Assignment of associated values
Process control messages are generated with EV_ID1 up to EV_ID24 via ALARM_8P associated values. The table below shows how the associated values are assigned to the block parameters.
Message block ALARM_8P
EV_ID1... EV_ID24
Associated value
1 2 3 4 5 6 7 8
Block parameter
Connection_ID 1+x Connection_ID 2+x Connection_ID 3+x Connection_ID 4+x Connection_ID 5+x Connection_ID 6+x Connection_ID 7+x Connection_ID 8+x
Data type
WORD WORD WORD WORD WORD WORD WORD WORD
x = 0 for EV_ID1, x = 8 for EV_ID2, x = 16 for EV_ID3 etc. up to x = 120 for EV_ID16 x = 0 for EV_ID17, x = 8 for EV_ID18, x = 16 for EV_ID19 etc. up to x = 56 for EV_ID24
6.2
CPU_RT: Determination of the runtime of OBs
6.2.1
Description of CPU_RT
Object name (type + number) FB 128 · CPU_RT block I/Os (Page 38)
Area of application
The CPU_RT block is installed by the CFC in OB 100, OB 1, in all OB 3x as well as OB 8x, if this is used by the user program.
The CPU_RT determines the runtime of the individual OBs and their participation in the cycle time. If there is CPU overload (OB 80 cycle time exceeded), it instigates suitable actions selected by the user in limits to ensure operability of the AS.
This situation is designated as emergency operation and is made clearly visible by a process control message. Buffered start events (OB 3x still executing) are also detected and displayed. The loss of start events is reported as error.
Basis Library (V9.0 SP3)
Function Manual, 06/2019, A5E40797470-AD
31
Family: @System 6.2 CPU_RT: Determination of the runtime of OBs
Use in CFC
During compilation of the CFC, a chart is automatically created with the name @CPU_RT. The CPU_RT block is already included in it.
Note Never attempt to insert the CPU_RT block in a different block because it is a system block.
Function and method of operation At CPU restart and when downloading changes the slowest OB 3x is determined with SZL ID 822 (data records of all assigned alarms of an alarm class). Note: The slowest cyclic OB 3x (slowest OB) must also have the lowest priority set so that a useful analysis is possible. If there are implausible settings in OB-BEGIN, a "Priorities of cyclic OBs do not conform to PCS 7" EV_ID2 signal 3 message is output and the maintenance status (MS) is set to "Maintenance demanded" = 16#00000005. SFC78 is used to determine the OB runtimes. If it is not present, no warning limit will be output as a message.
Note Older CPUs do not support SFC78. Use SSL112 to check whether SFC78 is available.
Note The status of CPU_RT is reset when you download.
Behavior at higher CPU load If the average value of all net runtimes (in % of OB 3x, OB 8x + OB 1) exceeds the value MAX_LIM, then in OB_BEGIN, the message EV_ID2- signal 1 "Net time consumption of all OBs exceeds max limit" is output.
The maintenance status MS is set to "Maintenance demand" = 16#00000005 in OB_BEGIN.
The message and MS are cleared with a value less than MAX_LIM HYS.
Behavior in the event of OB request errors If a programmable number of these OB 3x events has been exceeded or if an OB 1 event is detected without an OB 1 having been processed, the message EV_ID3 Signal 2 "OB request: OB 3x still being processed" is output in OB_BEGIN. The number of OB 3x events can be set at the input "N_REG_ERR"; the default value = 4.
The maintenance status MS is set to "Uncertain maintenance demanded" = 16#00000006 in OB_BEGIN.
Basis Library (V9.0 SP3)
32
Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.2 CPU_RT: Determination of the runtime of OBs
If an OB 1 is then run through again, the MS is reset and this process control message will be marked as "outgoing". In the faceplate of OB_BEGIN, there is a display of the request error for each OB 3x. The first occurrence of a request error is be displayed. These displays can be reset with the reset key.
Behavior when the maximum cycle time is exceeded If the maximum cycle time is exceeded, a message EV_ID3 Signal 1 "Cycle time exceeded: @1d@ OB@2d@" is output. The maintenance status MS is set to "Bad or maintenance alarm" = 16#00000007 in OB_BEGIN. If an OB 1 is then run through again, the MS is reset and this process control message will be marked as "outgoing".
Behavior to prevent stop If the cycle time is exceeded twice without an OB 1 being processed, this results in Emergency Operation with stop avoidance activated. The process control message EV_ID1 Signal 3 "Emergency operation, reducing ratio of cyclic OBs" is output. The maintenance status MS is set to "Bad or maintenance alarm" = 16#00000007. If the CPU resumes normal operation after the problem has been eliminated, the MS is reset and this process control message is marked as "outgoing".
Behavior during downloading The status of CPU_RT is reset when you download.
Measures for avoiding stop When the CPU is overloaded you can prevent the CPU from becoming inoperable by "load shedding". Load shedding is achieved by suspending the cyclic levels and is an emergency mode. The user can still exclude individual OBs for the first escalation stage, for example the level with the F drivers. To avoid a CPU stop, CPU_RT takes the following measures in OB 80 when reaching a cycle overflow occurs: · Cycle time monitoring is triggered with an SFC43 call, to prevent a CPU stop. · A memory bit is set to detect the next immediate OB 80 call within an OB 1 call, so that, if necessary, measures can be initiated that prevent an overload of the AS. In OB 80, the measures to prevent the overload are initiated and they reversed in the slowest OB. Two escalation stages can be set: Stage 1: None of the used OB 3x blocks will be processed for one cycle, unless they have been excluded by the user (OB3x_ATTN = FALSE). Stage 2: Now all previously excluded OB 3x blocks will likewise not be processed for one cycle. If this does not have a steadying effect, whenever OB 3x blocks are executed their execution will be suspended again for one cycle.
Basis Library (V9.0 SP3)
Function Manual, 06/2019, A5E40797470-AD
33
Family: @System 6.2 CPU_RT: Determination of the runtime of OBs
Assign the parameters in CPU_RT for each OB 3x at the following inputs:
OB3x_ATTN = TRUE
The OB is included in the measures to prevent overload. Default is "TRUE".
The maximum number of SFC43 calls can be set at the input MAX_RTRG. If the maximum number x is exceeded, the CPU goes to stop.
The number x is reset when there is an OB 1 call again.
If you set MAX_RTRG = 0, then the function stop avoidance on overload function is deactivated.
If the measures are effective, in other words OB 1 is run through again, a calculation is made at that point to determine whether canceling the measures would again result in overload. If yes, the measures remain in effect. The measures are reduced step-by-step, when safe operation is possible again.
Reversal of the measures for stop avoidance
To initiate a reversal the percentage sum of the cyclic OBs calculated back to a lower reduction ratio, must be less than full CPU utilization.
Use the parameter MAX_VAL to set the value that corresponds to full CPU utilization. The value "95" is default.
The calculation is made according to the following formula:
((NET30PERint * (OB30_N_START+1) / OB30_N_START)+ (NET31PERint * (OB31_N_START+1) / OB31_N_START)+ (NET32PERint * (OB32_N_START+1) / OB32_N_START)+ (NET33PERint * (OB33_N_START+1) / OB33_N_START)+ (NET34PERint * (OB34_N_START+1) / OB34_N_START)+ (NET35PERint * (OB35_N_START+1) / OB35_N_START)+ (NET36PERint * (OB36_N_START+1) / OB36_N_START)+ (NET37PERint * (OB37_N_START+1) / OB37_N_START)+ (NET38PERint * (OB38_N_START+1) / OB38_N_START)+ NET01PER)< MAX_VAL
NETxxPERint is the percentage share of a cyclic OB in the total runtime as a mean value and (OB30_N_START+1) is the current reduction factor of the OB.
The net percentage values are also mean values, because in case of reduction, averaging is a must.
For the calculation, a separate mean value generation was used that has a separate sample factor (SAMPLE_RE).
If the condition is satisfied, then after a number of cycles in the slowest OB (parameter "UndoCycle") the reduction factor is decremented by 1 for all OBs.
If the total sum of the OBs is still below MAX_VAL after this, then after a number of cycles in the slowest OB (UndoCycle), the factor will continue to be decremented until the used cyclic OBs have reached the reduction factor 1.
After this, for the OBs (OB3x_ATTN = FALSE) excluded by the user, the reduction ratio will be set to 0.
Finally. the reduction ratio will be set to 0 for all other cyclic OBs.
Basis Library (V9.0 SP3)
34
Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.2 CPU_RT: Determination of the runtime of OBs
If no SFC78 is present, then the time at which reversal of the stop avoidance measures can be triggered cannot be calculated.
The reversal of reduction ratios is started when the slowest OB has again processed a number of cycles (UndoCycle).
The value of the UndoCycle in this case should not be too low, to avoid a frequent back and forth between stop avoidance measures and normal operation.
For the reduction ratio in the CFC, two parameters are available in the CPU_RT block for each cyclic OB:
OB3x_N_START OB3x_N_CNT
The start value for reduction ratio is specified by the input OB3x_N of CPU_RT and also in OB3x_N_CNT
The counter is decremented in the CFC at each OB call. For OB3x_N_CNT <= 0 there is complete OB processing and OB3x_N_START will be re-entered in OB3x_N_CNT.
The CPU block is also called when reduction becomes necessary, so that in emergency operation an evaluation of the averaged cycle time is possible.
Utilization display with SFC78
When the block executes, the calling OB is determined. For every OB with the system function SFC78, it reads the net runtime, LAST_RTxx, and the gross runtime LAST_Etxx of the last completed OB processing. The absolute times are specified in milliseconds.
The mean value is generated for each OB (OB 3x and OB 8x) according to the formula
Mean value = mean value + (new value mean value ) / sample_AV
SAMPLE_AV is a parameter that is calculated separately for each OB 3x, OB 8x. If necessary, you can adapt the precision of the mean value with this parameter that is based on the number of measuring cycles, or on the influence of the new value on the mean value.
The default of SAMPLE_AV = 25 cycles, based on the slowest cyclic OB.
The actual sample factor for specific OBs is determined according to the following formula:
SampleOB3x = Sample * execution frequency of the slowest OB / execution frequency of OB3x
This ensures equally-weighted mean value generation over time for all cyclic OBs.
The sample factor for the total mean value of OB 1, and for OB 8x, is set to = sample, because the basis for these values is also the execution frequency of the slowest OB.
Use the reset button on the faceplate of OB_BEGIN to reset mean value generation.
After the reset, the divisor "Sample" of 1 per cycle is incremented by 1.
This means that with the reset, mean value generation is initially imprecise and it becomes more precise through the factor "sample". The influence of the new value on the mean value initially is significant and diminishes as the "sample" factor becomes greater.
By resetting the data, a fresh measuring cycle can be started at anytime.
Basis Library (V9.0 SP3)
Function Manual, 06/2019, A5E40797470-AD
35
Family: @System 6.2 CPU_RT: Determination of the runtime of OBs
The reset of all mean values takes place in OB 1. Mean value generation does not take place during this time.
Note After CPU restart/reset, the block has a value of TOTALMIN = 100 and TOTALMAX = 0 till the slowest OB3x has been run, before reaching its first process cycle. After the first cycle the values are updated from the calculated actual value (TOTALMIN value decreases and TOTALMAX value increases).
Connection load display
The connection states of the configured connections from the CPU V6 are queried through the block. The data are evaluated for all connections*. The 5 connections with the highest load are set at the CON1-5 block outputs.
Connection type
The connection type specifies the kind of connection involved. These are listed in the following table:
CONx_TYPE 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14
Type of connection Invalid connection type Fixed configured S7 connection Fixed configured S7 connection (fault-tolerant) T connection (TCP native) T connection (UDP) T connection (ISO-on-TCP) Routed connection PG connection OP connection OMS connection Free connection Free connection (TCP) System connection RPC7 connection Connection for basic communication
Identification / partner
You can use this to recognize the connection involved. This connection must be unique. Depending on the connection type, the ID and the partner are determined as follows:
Connection type 1-2 3-5 6 7-9 10-11
Text Local ID: a AWP ID: 16# a Partner address: a.b.c.d* -
tag a = User ID (hex) a = User ID (hex) a..d = CONx_R_ADDR0..3* -
Basis Library (V9.0 SP3)
36
Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.2 CPU_RT: Determination of the runtime of OBs
12 13-14
Device ID 16# a R/S b/c Partner address: a.b.c.d*
a = UserId (hex), b = rackNr c = slotNr
a..d = CONx_R_ADDR0..3*
* CONx_R_ADDR_LEN is used to determine the length of the CONx_R_ADDR0..3 = a..d to be represented. Only the number of bytes actually addressed are displayed.
Last
This shows the load of the connection in percent, associated with the CONx_PER tag
Error handling
If the read-out of data from the cyclic OB fails for the CPU_RT block, then ERR_NUM = 1 is set and processing of the CPU_RT block is abandoned, because these data are the basic prerequisite for useful processing.
Startup characteristics
Calculations with SFC78 are restarted only after a number of cycles (RunUpCyc) after restart. The RunUpCyles are counted down in the slowest cyclic OB.
Time response Not applicable.
Message response The block reports via OB_BEGIN (Page 270)
Operator control and monitoring:
If asset management is used in the project and the diagnostics screens have been generated, the faceplate can be called via the block icon of the AS.
· OB_BEGIN faceplate
· Asset Management block icons (for additional information, refer to the "Process Control System PCS 7; Maintenance Station" manual)
If no asset management is used in the project, the "OB-BEGIN" block icon is used to display avoidance of stop.
Additional information You can find additional information on this subject in the following sections: Message texts and associated values of OB_BEGIN (Page 275) Maintenance status MS (Page 533)
Basis Library (V9.0 SP3)
Function Manual, 06/2019, A5E40797470-AD
37
Family: @System 6.2 CPU_RT: Determination of the runtime of OBs
6.2.2
I/Os of CPU_RT
The factory setting of the block display in the CFC is identified in the "I/O" column:
I/O name bold = I/O visible, I/O name normal = I/O not visible.
You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15)".
Input parameters
I/O
Meaning
DELTA_L DIAG_BUF HYS MAX_LIM MAX_RTRG MAX_VAL N_REQ_ERR OB3x_ATTN RESET RUNUPCYC SAMPLE_AV SAMPLE_RE UNDO_CYC
Flag for change compile Entry in diagnostic buffer (relevant for maintenance personnel) Hysteresis of the max. total number Max. total number Max. number of calls (for SFC 43) Max. value for calculating the reset of reduction ratios Number of OB 3x request errors (x = 0 8) OB 3x: 1 = participates in measures to prevent overloads Resets the mean values, minimum values, and maximum values Number of start-up cycles Sample factor for mean value generation Sample factor for mean value generation internal Counter in the slowest OB for emergency operation
Type
BOOL BOOL INT REAL INT REAL INT BOOL BOOL INT INT INT INT
De- fault
1 0 5 75 50 95 4 1 1 5 50 50 100
Output parameters
I/O
CON_LOAD_ACT CONx_TYPE CONx_USER_ID CONx_INT_CN_ID CONx_DEVICE_ID CONx_MAXP CONx_REM_ADDR_LEN CONx_REM_ADDR0..7 CONx_LOAD
CONx_PER CPU_RT_DATA DAT_PLAU ERR_NUM EXC_FR3x
Meaning
Type
1 = I/O for loading function is available (x = 1 - 5) I/O type (x = 1 - 5) I/O ID from NetPro (x = 1 - 5) Unique internal name of I/O (x = 1 - 5) Low byte: Device I/O, high byte: Rack/Slot of the CP (x = 1 - 5) Maximum proportion of bytes, sent and received (x = 1 - 5) Length of the I/O address (x = 1 - 5) I/O address 0 to 7 (x = 1 - 5) Number of bytes sent and received during the sampling time (x = 1 - 5) Percentage of total number of bytes System structure: Performance data 1 = slowest OB 3x has the lowest priority 1 = occurrence of an error (x = 0 8) execution cycle (in ms) of the OB 3x
BOOL WORD WORD WORD WORD INT WORD BYTE DINT
INT STRUCT BOOL INT INT
De- fault 0 0 0 0 0 0 0 0 0
0
0
0
Basis Library (V9.0 SP3)
38
Function Manual, 06/2019, A5E40797470-AD
I/O
GRO3xAV GRO3xCUR GRO3xMAX GRO3xMIN GRO3xPER MAXCYCTI N_OB1_CYC NET01AV NET01CUR NET01MAX NET01MIN NET01PER NET3xAV NET3xCUR NET3xMAX NET3xMIN NET3xPER NET8xAV NET8xCUR NET8xMAX NET8xPER OB3x_N_CNT OB3x_N_START REQ01ERR REQ3xERR SFC78_EX SL_OB SL_OB_EXC_FR TOTALAV TOTALCUR TOTALMAX TOTALMIN
Family: @System 6.2 CPU_RT: Determination of the runtime of OBs
Meaning
(x = 0 8) gross mean value (x = 0 8) gross current value (x = 0 8) gross maximum value (x = 0 8) gross minimum value (x = 0 8) gross mean value (in %) Set scan cycle monitoring time Number of OB 1 calls during a cycle of the slowest OB Net mean value of OB 1 (in ms) Net current value of OB 1 (in ms) Net maximum value of OB 1 (in ms) Net minimum value of OB 1 (in ms) Net mean value of OB 1 (in %) (x = 0 8) net mean value of OB 3x (in ms) (x = 0 8) net current value of OB 3x (in ms) (x = 0 8) net maximum value of OB 3x (in ms) (x = 0 8) net minimum value of OB 3x (in ms) (x = 0 8) net mean value of OB 3x (in %) (x = 0 8) net mean value of OB 8x (in ms) (x = 0 8) net current value of OB 8x (in ms) (x = 0 8) net maximum value of OB 8x (in ms) (x = 0 8) net mean value of OB 8x (in %) (x = 0 8) decrementing counter for reduction ratio (x = 0 8) start value for reduction ratio (x = 0 8) OB request errors since the last reset (x = 0 8) OB request errors 1 = SFC 78 available in CPU Slowest OB 3x Number of calls of the slowest OB 3x Total average value of all OB 1, OB 3x, OB 8x (in %) Total current value of all OB 1, OB 3x, OB 8x (in %) Total maximum value of all OB 1, OB 3x, OB 8x (in %) Total minimum value of all OB 1, OB 3x, OB 8x (in %)
Type
REAL REAL REAL REAL REAL INT INT REAL REAL REAL REAL REAL REAL REAL REAL DINT REAL REAL REAL REAL REAL INT INT BOOL BOOL BOOL BYTE INT DINT DINT DINT DINT
De- fault
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
In/out parameters
I/O
Meaning
IDLE_CYC
CPU utilization display
Type INT
De- fault
0
Additional information You can find additional information on this subject in the following sections:
Basis Library (V9.0 SP3)
Function Manual, 06/2019, A5E40797470-AD
39
Family: @System 6.3 DIAG_AB: Evaluation of statusword AB7000
Message texts and associated values of OB_BEGIN (Page 275)
6.3
DIAG_AB: Evaluation of statusword AB7000
6.3.1
Description of DIAG_AB
Object name (type + number) FB 414 · DIAG_AB Block I/Os (Page 42)
Area of application
The DIAG_AB block evaluates the status word of an AB7000 slave and acknowledges newly reported errors via the control word of the slave.
Calling OBs
The cyclic OB and OB 100.
Use in CFC
The following actions are executed automatically with the "Generate module drivers" CFC function:
· The block is installed in the run sequence before the MOD_PAL0 or MOD_PAX0 block, both of which are also installed by the driver generator. The install is executed in the same cyclic OB as the associated signal processing blocks FF_A_xx.
· Parameters are assigned to the LADDR_C input with the address of the control word of the AB7000.
· Parameters are assigned to the input LADDR_S with the address control word of the AB7000.
· The OUT structure CPU_DIAG of the OB_BEGIN block is interconnected with the IN_OUT structures of the same name of DIAG_AB.
· The input mode of the DIAG_AB block is interconnected with the output OMODE_00 of the PADP_L10 or PADP_L01 block.
· The input PA_DIAG of the DIAG_AB block is interconnected with the output PA_DIAG of the PADP_L10 or PADP_L01 block.
· The output OMODE of the DIAG_AB block is interconnected with the input MODE_00 of the MOD_PAL0 or MOD_PAX0 block.
· The output ODIAG of the DIAG_AB block is interconnected with the input PA_DIAG of the MOD_PAL0 or MOD_PAX0 block.
Basis Library (V9.0 SP3)
40
Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.3 DIAG_AB: Evaluation of statusword AB7000
Function and method of operation
The DIAG_AB block cyclically analyses the status word of the AB7000 slave,
If a Modbus device fails, or if there is a higher-level error at the MODE input, then the OMODE and PA_DIAG outputs are set to "Bad":
Parameters OMODE ODIAG
Value 16#40000001 16#00400000
Description Higher level error Due to process no valid values
After an error exiting state the outputs are set to the status "Good":
Parameters OMODE ODIAG
Value 16#80000001 PA_DIAG
Description Valid value Diagnostics information from PADP_L10 or PADP_L01 block
The outputs SR_CODE and SR_DATA show the last values of a status tab sent by the AB7000. The meaning of SR_DATA depends on SR_CODE:
SR_CODE 16#00
16#01 16#03 16#04 16#13
16#1F
SR_DATA Number of retransmissions Address of the FIM Address of the FIM Address of the FIM
---
Description
Reading or writing an FIM tab needed to be executed again due to an error No connection to the FIM The FIM has sent more data than expected An error has occurred, no more data is available No error if SR_DATA = 16#00; otherwise, failure of the FIM (with the address in SR_DATA) An error is no longer present
Error handling The validity of input parameters is not checked.
Startup characteristics
Initialization of outputs OMODE with 16#80000001 ("valid value") and ODIAG with 16#00000000 ("no error")
Time response Not available
Message response Not available
Basis Library (V9.0 SP3)
Function Manual, 06/2019, A5E40797470-AD
41
Family: @System 6.3 DIAG_AB: Evaluation of statusword AB7000
Operator control and monitoring Not available
6.3.2
I/Os of DIAG_AB
The factory setting of the block display in CFC is identified in the "I/O" column:
I/O name bold = I/O visible, I/O name normal = I/O not visible.
You can find explanations and the meaning of abbreviations in the section: General Information About Block Description (Page 15).
Input parameters
I/O LADDR_C LADDR_S MODE PA_DIAG
Meaning Logical address of the control word Logical address of the control word Value status Diagnostic information
Type INT INT DWORD DWORD
Default 0 0 16#80 000 000 0
Output parameters
I/O ODIAG OMODE SR_CODE SR_DATA
Meaning Field devices diagnostics information Value status of the slave Code of the status tab Data of the status tab
Type DWORD DWORD BYTE BYTE
Default 0 0 0 0
In-out parameters
I/O CPU_DIAG
Meaning CPU diagnostics (system structure)
Type STRUCT
Default
Basis Library (V9.0 SP3)
42
Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.4 DPAY_V0: Monitoring DP/PA and Y-Link operating as V0 slave
6.4
DPAY_V0: Monitoring DP/PA and Y-Link operating as V0 slave
6.4.1
Description of DPAY_V0
Object name (type + number) FB 108 · DPAY_V0 block I/Os (Page 47)
Area of application
Block DPAY_V0 monitors the status of a DP/PA or Y-Link as a V0 slave (IM 157) and reports the corresponding error events.
The DP/PA link operates as a PA master for the lower-level PA field devices and as a slave on the DP bus.
The Y-Link operates as a DP master for the lower-level DP field devices and as a slave on the higher-level DP bus.
Calling OBs
The block must be installed in the run sequence in the following OBs:
OB 1 OB 70 OB 72 OB 82 OB 85 OB 86 OB 100
Cyclic program I/O redundancy error CPU redundancy error Diagnostic interrupt Program execution error Rack failure Warm restart
Use in CFC
The following actions are executed automatically with the "Generate module drivers" CFC function:
· The block is integrated in the run sequence downstream from the SUBNET block and upstream from the PADP_L0x block.
· RACK_NO (rack/station number) is configured.
· SUBN_TYP (internal/external PROFIBUS interface) is set.
· SUBN1_ID (ID of the master systems) is set.
· SUBN2_ID (ID of the redundant master system) is set.
· DADDR (diagnostic address of the DP/PA or Y-Link) is set.
Basis Library (V9.0 SP3)
Function Manual, 06/2019, A5E40797470-AD
43
Family: @System
6.4 DPAY_V0: Monitoring DP/PA and Y-Link operating as V0 slave
· DPPA_xx (slave xx address), 1st module (slot) address of slave xx in the link, number of slots of slave xx are set.
· The CPU_DIAG of the OB_BEGIN block and SUB_DIAG of the SUBNET block OUT structures are interconnected with the IN_OUT structures of the same name of DPAY_V0.
· In the case of PA or DP field devices, they are interconnected with PADP_L0x.
Function and method of operation
If redundancy losses and link failures occur, the DPAY_V0 block generates a control-system error message for the OS. The block also indicates error events at active links (SUBN1ERR, SUBN2ERR) and at the preferred channel (SUBN1ACT, SUBN2ACT) in the output status bar. The output structure RAC_DIAG contains the geographic address of the link as well as the group error information RACK_ERR. The corresponding link is not available if RACK_ERR = 1.
The block requires a PROFIBUS DP interface. This can either be integrated in the CPU or provided by means of an external DP interface (CP). PROFIBUS DP is converted to PROFIBUS PA by means of a SIMATIC DP/PA-Link.
The field devices of a link are always addressed at the higher-level DP bus via the DP address of IM 157.
The AS addresses the field devices via the link, i.e., indirectly. The topological structure of the PA bus is mapped in the flat structure of the slave interface. A maximum of 64 field devices can be operated downstream from a link. Each field device can use any number of virtual slots at the link, up to 223 maximum.
In order to enable the assignment of diagnostic data to the field devices, the block provides each field device a DPPA_xx input structure consisting of 3 bytes with the following contents:
· Byte (SLAV_NO) = node number (address) of the field device at the PA/DP master system of the LINK
· Byte (SLOT_NO) = 1st module address of the field device in the link
· Byte (SLAV_SL) = number of slots of the field device
The "Generate module drivers" CFC function fetches this data from HW Config.
The start information is read from the CPU_DIAG I/O structure. This structure must be interconnected to the CPU_DIAG structure of the OB_BEGIN block (carried out by the CFC function "Generate module drivers").
The block generates a corresponding message (see "Message Response") on the basis of the startup information of calling OBs, if the current instance is affected.
When operating with redundant PROFIBUS DP interfaces, the block determines the currently active preferred channel (SUBN1ACT, SUBN2ACT) by evaluating the error events as well as via the diagnostic address DADDR of the link.
SFC 13 (DPNRM_DG, read diagnostic data consistently) reads the diagnostic data (OB 82). The reading process can take several cycles (OB 1). It is therefore possible in a few rare cases that the triggering diagnostic event cannot be recognized.
Diagnostic user data contains information about the status of the link, and of connected field devices. The structure DPPA_ST indicates the link status.
Basis Library (V9.0 SP3)
44
Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.4 DPAY_V0: Monitoring DP/PA and Y-Link operating as V0 slave
The status of a field device is entered in the structure DPA_M_xx. A field device can have a maximum of 32 slots (modules). Three block types are available, according to the number of slots on the field device:
· PADP_L00 (field device with max. 7 slots)
· PADP_L01 (field device with max. 16 slots)
· PADP_L02 (field device with max. 32 slots)
The structure DPA_M_xx is interconnected to the structure DPA_M and the output EN_Mx with EN of one of the PADP_Lxx blocks (carried out by the CFC function "Generate module drivers").
The DPA_M_xx structure consists of two DWORD value (S_01 for modules 1 to 16 and S_02 for modules 17 to 32) and one BOOL value (S_ERR = DP/PA field device faulty). Two bits of the DWORD are assigned to each slot of the DP/PA field device, whereby bit 0 and bit 1 belong to slot 1 (module 1) of the DP/PA field device, etc. These bits are defined as follows:
Status Bit 0 0 0 1 1
Status Bit 1 0 1 0 1
Meaning Module x OK (valid user data) Module x error (invalid user data) Wrong module x (invalid user data) No module x (invalid user data)
If the diagnostics alarm applies to the entire DP/PA field device, then DPA_M_xx.S_ERR = TRUE is set.
Note: If you want to change the SUBN1_ID (connection to CPU 0) and SUBN2_ID (connection to CPU 1) inputs online, you must set input ACC_ID = TRUE. This verifies the Link states and updates output values.
Redundancy
The block supports redundant DP master systems in an H system (distributed I/Os only). The SUBN1_ID (connection to CPU 0) and SUBN2_ID (connection to CPU 1) inputs of the SUBNET block are configured with the numbers of the redundant DP master systems. If the DP master systems are not redundant, the remaining input is set to 16#FF (default).
Error handling
Error handling for the block is limited to the evaluation of the error information of ALARM_8P. For additional information on this, refer to the section:
Error information of the MSG_STAT output parameter (Page 530)" section.
Startup characteristics
The block initializes the messages of ALARM_8P. Availability of the link is verified. In H systems, determines the preferred channel of the link.
Basis Library (V9.0 SP3)
Function Manual, 06/2019, A5E40797470-AD
45
Family: @System 6.4 DPAY_V0: Monitoring DP/PA and Y-Link operating as V0 slave
Overload behavior
The block counts OB 86 (no DP master system failure, see SUBNET block) and OB 82 calls. Both counters are reset in OB 1. If more than five OB 86 events or more than five OB 82 events in succession before the cycle control point is reached (OB 1), these events are discarded and the message ""DP-Link DP-Master:x Rack:y: Multiple failure" or the message "DP-Link Master:x Rack:y: Muktiple alarm (OB 82)" is output. 1 minute later the status of the link will be re-checked.
Time response Not available
Message response
After its call by OB 70, OB 72, OB 85 or OB 86, the block analyzes the status of its assigned CPU, DP master and link. If the link loses redundancy or fails, the block outputs corresponding messages via ALARM_8P.
The block generally reports only the events generated in the link that it monitors. Redundancy loss and link failures which are caused by the failure of a DP masters or of a CPU, are initially neither signaled nor indicated at the outputs SUBN1ERR and SUBN2ERR.
The DELAY input is used to delay the output of error messages for higher-priority outgoing errors. This delay time is configurable. When the block recognizes an outgoing error at an interconnected DP master, it initially assumes that there is a faulty assigned DP slave in the link it monitors and sets the corresponding output SUBNxERR. The error status is not reset until the DP slave returns (in this case: OB 86, OB 70). The blocks delay error messages relevant to any slave failure states for a time in seconds as specified in DELAY, in order not to trigger the output of surge of messages from DP slaves which are not yet synchronized after the master has returned. An error message is only output to the OS when the DP slave has not reported its return before this delay time has expired.
Do not set the value of DELAY too high, since messages reporting faulty DP slaves or their removal during a master failure will be output too late to the OS after the DP master returns.
The block generates the following messages in the OBs listed below:
OB no. OB 1
Start Event Cyclic processing
OB 70 OB 85 OB 86 OB 100
Redundancy loss Program execution error Rack failure Restart
Message
Repeat the update of ALARM_8P outputs/messages, if necessary Link redundancy loss/return Link failure going Link failure coming/going Initialization of ALARM_8P
Operator control and monitoring
If asset management is used in the project and the diagnostic screens have been generated, the faceplate can be called via its block icon.
For additional information, refer to the "Process Control System PCS 7; Maintenance Station" manual.
Basis Library (V9.0 SP3)
46
Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.4 DPAY_V0: Monitoring DP/PA and Y-Link operating as V0 slave
Additional information For additional information, refer to the sections: Message texts and associated values of DPAY_V0 (Page 48) Maintenance status MS (Page 533)
6.4.2
I/Os of DPAY_V0
I/Os The factory setting of the block display in the CFC is identified in the "I/O" column:
I/O name bold = I/O visible, I/O name normal = I/O not visible.
You can find explanations and the meaning of abbreviations in the section: General Information About Block Description (Page 15).
Input parameters
I/O (parameter) DADDR DELAY DIAG_BUF
DPPA_xx EN_MSG EV_ID MS RACK_NO SUBN_TYP SUBN1_ID SUBN2_ID
Meaning
Diagnostic address of the DP slave Interrupt delay (s) Entry in diagnostic buffer (relevant for maintenance per- sonnel) Information of the DP/PA slave (xx = 00 - 63) 1 = enable message Message number Maintenance status Rack/station number 1 = external DP interface ID of the primary DP master system ID of the redundant DP master system
Data type
INT INT BOOL
STRUCT BOOL DWORD DWORD WORD BOOL BYTE BYTE
Default
0 15 0
1 0 0 0 0 255 255
Output parameters
I/O (parameter)
DPA_M_xx DPPA_ST EN_Mxx MSG_STAT O_MS RAC_DIAG
Meaning
Status of the DP/PA slave (xx = 00 - 63) DP/PA/Y-Link status 1 = Enable modules (xx = 00 - 63) Message error information Maintenance status Rack diagnostics
Data type
STRUCT STRUCT BOOL WORD DWORD BOOL
Default
0 0 0 0
Basis Library (V9.0 SP3)
Function Manual, 06/2019, A5E40797470-AD
47
Family: @System 6.4 DPAY_V0: Monitoring DP/PA and Y-Link operating as V0 slave
I/O (parameter)
SUBN1ACT SUBN1ERR SUBN2ACT SUBN2ERR
Meaning
1 = Slave 1 is active 1 = Error in DP master system 1 1 = Slave 2 is active 1 = Error in DP master system 2
In/out parameters
I/O (parameter)
ACC_ID CPU_DIAG SUB_DIAG
Meaning
1 = accept MODE settings CPU diagnostics (system structure) OB startup information
Additional information For additional information, refer to the sections: Message texts and associated values of DPAY_V0 (Page 48) Maintenance status MS (Page 533)
Data type
BOOL BOOL BOOL BOOL
Default
0 0 0 0
Data type
BOOL STRUCT STRUCT
Default 0
6.4.3
Message texts and associated values of DPAY_V0
Assignment of message text and message class
Message no. 1
2
3
4
5 6 7
8
Default message text DP Link @1%d@/ @3%d@: Redundancy loss DP Link @2%d@/ @3%d@: Redundancy loss DP Link @1%d@/ @3%d@: Failure
DP Link @2%d@/ @3%d@: Failure
DP LINK @1%d@/ @3%d@: Multiple alarm (OB 82) DP LINK @1%d@/ @3%d@: Multiple fail- ure
Message class PLC Process Control Message - Error
PLC Process Control Message - Error
PLC Process Control Message - Fail- ure PLC Process Control Message - Fail- ure No message No message PLC Process Control Message - Fail- ure PLC Process Control Message - Fail- ure
Basis Library (V9.0 SP3)
48
Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.5 DPAY_V1: Enabling blocks downstream of a DP/PA and Y-Link operating as V1 slave
Assignment of associated values
Associated value 1 2 3
Block parameter ID of the primary DP master system (SUBN1_ID) ID of the redundant DP master system (SUBN2_ID) Rack/station number (RACK_NO)
See also
Message Classes (Page 531)
6.5
DPAY_V1: Enabling blocks downstream of a DP/PA and Y-Link
operating as V1 slave
6.5.1
Description of DPAY_V1
Object name (type + number) FB 115 · DPAY_V1 Block I/Os (Page 51)
Area of application
The DPAY_V1 block enables the field device-specific blocks downstream of the DP/PA or Y links.
The DP/PA link acts as a PA master for the lower-level PA field devices, and as a slave on the DP bus.
The Y link acts as a DP master for the lower-level DP field devices, and as a slave on the higherlevel DP bus.
Calling OBs
The block must be installed in the run sequence in the following OBs:
OB 1 OB 55 OB 56 OB 57 OB 70 OB 72 OB 82 OB 83 OB 85
Cyclic program Status interrupt Update interrupt Vendor-specific interrupts I/O redundancy error CPU redundancy error Diagnostic interrupt Insert/remove module interrupt Program execution error
Basis Library (V9.0 SP3)
Function Manual, 06/2019, A5E40797470-AD
49
Family: @System 6.5 DPAY_V1: Enabling blocks downstream of a DP/PA and Y-Link operating as V1 slave
OB 86 OB 100
Rack failure Warm restart
Use in CFC
The following actions are executed automatically with the "Generate module drivers" CFC function:
· The block is integrated in the run sequence after the OB_DIAG1 block.
· SUBN_1ID (ID of primary DP master system) is configured.
· SUBN_2ID (ID of secondary DP master system) is configured.
· RACK_NO (rack/station number) is configured.
· The OUT structure CPU_DIAG of the OB_BEGIN block is interconnected with the IN_OUT structures of the same name of DPAY_V1.
· The OUT structure CPU_OB_5X of the OB_BEGIN block is interconnected with the IN_OUT structures of the same name of DPAY_V1.
· EN_Mxx are interconnected with EN of OB_DIAG1 and PADP_L10 for each field device.
Function and method of operation
The start information is read from the CPU_DIAG I/O structure. The structure must be interconnected with the CPU_DIAG structure of OB_BEGIN (carried out by the CFC function "Generate module drivers"). The affected downstream blocks will be enabled according to the start information.
OB 5x characteristics Enables the output for the affected field device.
Redundancy
The redundancy is evaluated in OB_DIAG1.
Error handling The plausibility of input parameters is not checked.
Startup characteristics The block initializes its outputs.
Overload behavior OB_DIAG1 disables the block in response to an overload.
Basis Library (V9.0 SP3)
50
Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.5 DPAY_V1: Enabling blocks downstream of a DP/PA and Y-Link operating as V1 slave
Time response Not available
Message response Not available
Operator control and monitoring The block has no faceplate.
6.5.2
I/Os of DPAY V1
The factory setting of the block display in CFC is identified in the "I/O" column:
I/O name bold = I/O visible, I/O name normal = I/O not visible.
You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15)".
Input parameters
I/O (parameter) CPU_DIAG CPU_OB_5X DPPA_xx RACK_NO SUBN1_ID SUBN2_ID
Meaning
CPU diagnostics (system structure) OB_5x startup information Information about the DP/PA slave (xx = 00 - 63) Rack/station number ID of the primary DP master system ID of the redundant DP master system
Data type Default
STRUCT
STRUCT
STRUCT
WORD
0
BYTE
255
BYTE
255
Output parameters
I/O (parameter) CPU_DIAG CPU_OB_5X EN_Mxx
Meaning
CPU diagnostics (system structure) OB_5x startup information 1 = Enable slave (xx = 00 - 63)
Data type Default
STRUCT
STRUCT
BOOL
0
Basis Library (V9.0 SP3)
Function Manual, 06/2019, A5E40797470-AD
51
Family: @System 6.6 DPAY_V1_PN: Enabling blocks downstream of a DP/PA and Y-link operating as a V1 Slave
6.6
DPAY_V1_PN: Enabling blocks downstream of a DP/PA and Y-link
operating as a V1 Slave
6.6.1
Description of DPAY_V1_PN
Object name (type + number) FB 204 · I/Os of DPAY_V1_PN (Page 52)
Area of application
The DPAY_V1_PN block releases the field device-specific blocks downstream of the IE/PB link.
The IE/PB link operates as a PA master for the lower-level PA field devices and as a slave on the IE bus.
See also
General Information About Block Description (Page 15)
6.6.2
I/Os of DPAY_V1_PN
The factory setting of the block display in CFC is identified in the "I/O" column:
I/O name bold = I/O visible, I/O name normal = I/O not visible.
You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15)".
Input parameters
I/O (parameter) DPPA_00 RACK_NO SUBN1_ID SUBN2_ID
Meaning
Information about the DP/PA slave (xx = 00 - 63) Rack number PN IO system 1 ID (100 - 115) PN IO system 2 ID (100 - 115)
Data type Default
STRUCT
BYTE
0
BYTE
255
BYTE
255
Output parameters
I/O (parameter) EN_Mxx
Meaning 1 = Enable slave (xx = 00 - 63)
Data type Default
BOOL
0
Basis Library (V9.0 SP3)
52
Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.7 DPDIAGV0: Monitoring the status of ET 200S modules acting as DPV0 slaves after the Y link
In-out parameters
I/O (parameter) CPU_DIAG_PN CPU_OB_5X
Meaning System structure: CPU diagnostics OB_5x startup information
Data type STRUCT STRUCT
Default
6.7
DPDIAGV0: Monitoring the status of ET 200S modules acting as
DPV0 slaves after the Y link
6.7.1
Description of DPDIAGV0
Object name (type + number) FB 117 · DPDIAGV0 Block I/Os (Page 55)
Area of application
The DPDIAGV0 block monitors the status of the modules of an ET 200S acting as a DPV0 slave (IM 151-1 High Feature) after a Y link.
Calling OBs
The block must be installed in the run sequence in the following OBs:
OB 1 OB82 OB 83 OB 85 OB 86 OB 100
Cyclic program Diagnostic interrupt Insert/remove module interrupt Program execution error Rack failure Warm restart
Basis Library (V9.0 SP3)
Function Manual, 06/2019, A5E40797470-AD
53
Family: @System 6.7 DPDIAGV0: Monitoring the status of ET 200S modules acting as DPV0 slaves after the Y link
Use in CFC
The following actions are executed automatically with the "Generate module drivers" CFC function:
· The block is integrated in the run sequence after the OB_DIAG1 block.
· The following inputs are configured:
SUBN_1ID (ID primary DP master system)
SUBN_2ID (ID secondary DP master system)
RACK_NO (rack/station number)
· The following I/Os are interconnected:
The OUT structures CPU_DIAG of the OB_BEGIN block and RAC_DIAG of the RACK block with the DPDIAGV0-block IN_OUT structures of the same name
EN_Mxx with EN of the OB_DIAG1 block and the DPDIAGV0 block of each ET 200S
The DPA_M_xx outputs with the DPA_M input and EN_Mxx output with EN of a MOD_4 block.
Function and method of operation
In the event of a diagnostic interrupt, the DPDIAGV0 block analyzes the ID-specific diagnostic data, and the module status of an ET 200S in DPV0 mode after a Y link.
The upstream OB_DIAG1 block detects the failure/restart of an ET 200S.
The AS addresses the devices via the link, i.e., indirectly. The topological structure of the DP bus is mapped in the flat structure of the slave interface. There may be up to 64 devices downstream of a Link. Each device can be assigned any number of virtual slots (max. 223) of the link. To assign the diagnostic data of an ET 200S, the block uses the following inputs of data type BYTE with the meaning shown below:
· SUBN1_ID = Primary ID of the master system
· SUBN2_ID = Secondary ID of the master system
· RACK_NO = Station number (address) of the DP master system of the link
· PADP_ADR = Station number (address) of the ET 200S
· SLAVE _NO = 1st module address of the ET 200S in the link
· SLAVE_SL = Number of slots at the ET 200S
The "Generate module drivers" CFC function fetches this data from HW Config.
The useful diagnostic data contains information about the ET 200S status.
The status of an ET 200S module is entered in byte DPA_M_xx. An ET 200S can have up to 64 slots (modules).
Bits 0 to 2 of DPA_M are defined as follows:
Status Bit 2 0 0
Status Bit 1 0 1
Status Bit 0 0 0
Meaning Module x OK (valid user data) Module x error (invalid user data)
Basis Library (V9.0 SP3)
54
Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.7 DPDIAGV0: Monitoring the status of ET 200S modules acting as DPV0 slaves after the Y link
Status Bit 2 0 0 1
Status Bit 1 0 1 x
Status Bit 0 1 1 x
Meaning Wrong module x (invalid user data) No module x (invalid user data) ET 200S failure (invalid user data)
Note: If you want to change the SUBN1_ID (connection to CPU 0) and SUBN2_ID (connection to CPU 1) inputs online, you must set input ACC_ID = TRUE. This verifies the Link states and updates output values.
Redundancy
Only non-redundant devices may be used downstream of a Y link.
Error handling The validity of input parameters is not checked.
Startup characteristics The system verifies that the ET 200S is available.
Overload behavior The overload behavior takes place in the upstream OB_DIAG1 block.
Time response Not available
Message response Not available
Operator control and monitoring The block has no faceplate.
6.7.2
I/Os of DPDIAGV0
The factory setting of the block display in the CFC is identified in the "I/O" column:
I/O name bold = I/O visible, I/O name normal = I/O not visible.
You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15)".
Basis Library (V9.0 SP3)
Function Manual, 06/2019, A5E40797470-AD
55
Family: @System 6.8 DREP: Diagnostic Repeater in the DP master system
Input parameters
I/O (parameter) DADDR DIAG_BUF
PADP_ADR RACK_NO SLAVE_NO SLAVE_SL SUBN_TYP SUBN1_ID SUBN2_ID
Meaning
Data type Default
Diagnostic address of the Y-Link
INT
0
Entry in diagnostic buffer (relevant for maintenance person- BOOL
0
nel)
DP address ET 200S
BYTE
255
Rack/station number
BYTE
0
1st slot number of the slave in the Y-link
BYTE
0
Number of ET 200S slots
BYTE
0
1 = external DP interface
BOOL
0
ID of the primary DP master system
BYTE
255
ID of the redundant DP master system
BYTE
255
Output parameters
I/O (parameter) DPA_M_xx EN_Mxx QRACKF SUBNERR
Meaning
Status of the DP/PA slave (xx = 00 - 63) 1 = Enable modules (xx = 00 - 63) 1 = higher-level error 1 = Y link failure
Data type Default
BYTE
0
BOOL
0
BOOL
0
BOOL
0
In/out parameters
I/O (parameter) ACC_ID CPU_DIAG RAC_DIAG
Meaning
1 = accept MODE settings CPU diagnostics (system structure) Rack diagnostics of the DP slave downstream of Y link (system structure)
Data type Default
BOOL
0
STRUCT
STRUCT
6.8
DREP: Diagnostic Repeater in the DP master system
6.8.1
Description of DREP
Object name (type + number) FB 113 · DREP block I/Os (Page 61)
56
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.8 DREP: Diagnostic Repeater in the DP master system
Area of application The DREP block evaluates the diagnostic data from a SIMATIC diagnostic repeater for PROFIBUS DP. This repeater must be connected to a DP master.
Calling OBs
OB 1 OB 82 OB 86 OB 100
Cyclic processing Diagnostic interrupt Rack failure Warm restart (startup, message initialization)
Use in CFC
The following actions are executed automatically with the "Generate module drivers" CFC function:
· Block OB_DIAG1 is installed in the run sequence upstream of the DREP block.
· The following addresses are configured:
The diagnostic address DADDR of the diagnostics repeater
The geographic address (SUBN_ID and PADP_ADR)
· The following I/Os are interconnected:
The OUT structures CPU_DIAG of the OB_BEGIN block and RAC_DIAG of the OB_DIAG1 block with the IN_OUT structures of the same name of the DREP block.
The EN input with the output of an AND block.
The inputs of the AND block with the EN_SUBx outputs (x = number of the DP master system) of the OB_BEGIN block, with EN_Rxxx (xxx = rack/station number) of the SUBNET block and with EN_F of the OB_DIAG1 block.
EN_DIAG with the EN_DIAG output of the OB_DIAG1 block.
Function and method of operation
The diagnostics repeater is assigned the following tasks:
· Diagnostics function for two PROFIBUS segments (DP2 and DP3): The diagnostics function returns the location and cause of line faults, such as a wire break or missing terminating resistors. The error location is output, including a reference to the relevant nodes, e.g., "Short-circuit to shielding at signal line A, node 12 and 13".
· Repeater function for three PROFIBUS segments (DP1, DP2, DP3): The diagnostics repeater amplifies data signals on the bus and interconnects the relevant RS-485 segments.
· Galvanic/electrical isolation of the PG interface from other bus segments: Even if the system is operating at higher transmission rates, interference due to the removal or connection of PG cables is not to be expected at the other PROFIBUS DP segments.
Basis Library (V9.0 SP3)
Function Manual, 06/2019, A5E40797470-AD
57
Family: @System 6.8 DREP: Diagnostic Repeater in the DP master system
The manual titled Diagnostic Repeaters for PROFIBUS DP contains information about the structure of line error states at the DP1, DP2 and DP3 segments and describes the PG interface.
Block DREP reports only the diagnostic events at segments DP2 and DP3 of the diagnostic repeater.
Events of the DP1 segment are reported as general "Cable disturbance" group error.
The PG interface is not evaluated and does not result in a message.
Failure and return of the diagnostics repeater are detected by the upstream OB_DIAG1 block, and are forwarded to the block to report "DR failure".
If an error occurs, an incoming "line error" group message is generated for each segment (DP2 or DP3) when a diagnostic repeater detects the error event (bits in the diagnostic message frame indicating the cause of error):
Bit Description A.0 1: The location and cause of the error cannot be identified (possibly electromagnetic interference) A.1 CPU redundancy loss A.2 1: - A.3 1: Further measurement circuits at the segment, the other diagnostic repeater is connected
to its segment DP2 A.4 1: Further measurement circuits at the segment, the other diagnostic repeater is connected
to its segment DP3 A.5 1: - A.6 1: Cause of error is not clearly identified A.7 1: Critical message frame error rate B.0 1:- -. B.1 1: - B.2 1: - B.3 1: - B.4 1: - -. B.5 1: - B.6 1: - -. B.7 1: - C.0 1: Segment automatically switched off due to continuous zero level on the line. C.1 1: Segment automatically switched off due to constantly fluctuating line levels. C.2 1: - C.3 1: - C.4 1: More than 32 nodes connected to the measurement segment. C.5 1: The distance between the node and the diagnostic repeater exceeds the permitted
line length. C.6 1: The maximum permitted number of diagnostic repeaters connected in series has been ex-
ceeded. C.7 1: - -
The outgoing message will be generated when all segment bits are equal to zero.
Call HW Config to analyze details of events output by the diagnostic repeater.
Basis Library (V9.0 SP3)
58
Function Manual, 06/2019, A5E40797470-AD
Family: @System
6.8 DREP: Diagnostic Repeater in the DP master system
An appropriate incoming/outgoing message will be generated for each segment (DP2 or DP3) in response to the following events detected by a diagnostic repeater:
Bit Description
A.0 1: A.1 1:A.2 1: A.3 1: A.4 1: A.5 1: A.6 1: A.7 1: B.0 1: Wire break on signal line A. B.1 1: Short-circuit to shield on signal line B. B.2 1: B.3 1: Short-circuit to shield on signal line A. B.4 1: Wire break on signal line B. B.5 1: B.6 1: Wire break on signal line A and/or B, or the terminating resistor is missing. B.7 1: Short-circuit between signal line A and/or B, or an additional terminating resistor
has been installed. C.0 1: C.1 1: C.2 1: C.3 1: C.4 1: C.5 1: -. C.6 1: C.7 1: -
Events detected by the diagnostics repeater are acquired synchronously in OB 82. Diagnostic event data is fetched via SFB 54 in the OB_BEGIN block and written to the structure DINFO. The function always sets just one bit to indicate the cause of an event-entering state. Bit C7 may also be set if the diagnostics repeater has detected further errors. In this case, all previously reported events will be queued. DREP generates a corresponding group error message via ALARM_8P. Flutter messages may occur, particularly in response to error causes A.0.1 and A.6.1. They are suppressed as follows:
After an outgoing message, a new outgoing message will be delayed by the time in [s] set at the DELAY parameter. If a further error is queued, the outgoing message will not be generated until this error has been reported outgoing.
Error handling
The block evaluates the error information from ALARM_8P, and writes it to the corresponding output parameters. You will find additional information about this in the "Error information of output parameter MSG_STAT (Page 530)" section.
Basis Library (V9.0 SP3)
Function Manual, 06/2019, A5E40797470-AD
59
Family: @System 6.8 DREP: Diagnostic Repeater in the DP master system
The block reports a diagnostic error if an error occurs while reading the diagnostic data, or if any other fault corrupts diagnostic data.
Startup characteristics
ALARM_8P messages are initialized by the DREP block. This uses SFC13 (DPNRM_DG) to read the latest diagnostic information from the diagnostic repeater.
Overload behavior The interconnected OB_DIAG1 locks the call of DREP for diagnostics if an overload has occurred.
Dynamic response: Not available
Message response:
The multiple instances ALARM_8P are only called if a message is to be output by this instance. It is only at this point that previously acknowledged messages are updated by the corresponding ALARM block. If the connection to WinCC is down, each ALARM_8P instance can hold up to two message statuses of its event ID. (Usually two messages maximum). Flutter messages can be suppressed via the DELAY input.
The block generates the messages listed below:
OB no. Start Event
1
Cyclic processing
82
Diagnostic interrupt
100 Restart
Message
Call of ALARM_8P due to incomplete transfer or unacknowledged message Group message Initialization of ALARM_8P
Operator control and monitoring
If asset management is used in the project and the diagnostic screens have been generated, the faceplate can be called via its block icon.
For additional information, refer to the "Process Control System PCS 7; Maintenance Station" manual.
Additional information For additional information, refer to the sections: Message texts and associated values of DREP (Page 62) Maintenance status MS (Page 533)
Basis Library (V9.0 SP3)
60
Function Manual, 06/2019, A5E40797470-AD
6.8.2
Family: @System 6.8 DREP: Diagnostic Repeater in the DP master system
I/Os of DREP
The factory setting of the block display in the CFC is identified in the "I/O" column: I/O name bold = I/O visible, I/O name normal = I/O not visible. You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15)".
Input parameters
I/O (parameter)
DADDR DELAY DIAG_BUF EN_DIAG EN_MSG EV_IDx MS PADP_ADR SUBN_ID
Meaning
Diagnostic address of the diagnostic repeater Interrupt delay (s) Entry in CPU diagnostic buffer 1 = Queued diagnostic event 1 = enable message Message number Maintenance status DP/PA address of the diagnostic repeater DP master system ID
Type
INT INT BOOL BOOL BOOL DWORD DWORD BYTE BYTE
Default
0 2 0 0 1 0 0 255 255
Output parameters
I/O (parameter)
DINFO MSG_ACKx MSG_STATx O_MS QDREPF QERR
Meaning
Diagnostic information from the diagnostic repeater Message acknowledgment Message error information Maintenance status 1 = Removed/faulty diagnostic repeater 1 = program error
Type
STRUCT WORD WORD DWORD BOOL BOOL
Default
0 0 0 0 1
In/out parameters
I/O (parameter)
ACC_MODE CPU_DIAG RAC_DIAG
Meaning
1 = accept MODE settings CPU diagnostics OB_DIAG1 diagnostics
Type
BOOL STRUCT STRUCT
Default 0
Additional information For additional information, refer to the sections: Message texts and associated values of DREP (Page 62)
Basis Library (V9.0 SP3)
Function Manual, 06/2019, A5E40797470-AD
61
Family: @System 6.8 DREP: Diagnostic Repeater in the DP master system
Maintenance status MS (Page 533)
6.8.3
Message texts and associated values of DREP
Assignment of message text and message class
Message block ALARM_8P EV_ID1
EV_ID2
Message no. Default message text
Message class
1
DR @1%d@/@2%d@/ Segment DP2: Line PLC Process Control Message -
fault
Failure
2
DR @1%d@/@2%d@/DP2:
PLC Process Control Message -
@5%d@.@6%d@m/wire break A /
Failure
@3%d@ @4%d@
3
DR @1%d@/@2%d@/DP2:
PLC Process Control Message -
@5%d@.@6%d@m/short A/@3%d@
Failure
@4%d@
4
1%d@/@2%d@/DP2:
PLC Process Control Message -
@5%d@.@6%d@m/wire break B/
Failure
@3%d@ @4%d@
5
DR @1%d@/@2%d@/DP2:
PLC Process Control Message -
@5%d@.@6%d@m/short B/@3%d@
Failure
@4%d@
6
DR @1%d@/@2%d@/DP2:
PLC Process Control Message -
@5%d@.@6%d@m/wire break AB or ter- Failure
minating resistor missing/@3%d@
@4%d@
7
DR @1%d@/@2%d@/DP2:
PLC Process Control Message -
@5%d@.@6%d@m/short AB or too
Failure
many terminating resistors/@3%d@
@4%d@
8
DR @1%d@/@2%d@/ segment DP1: Line PLC Process Control Message -
fault
Failure
1
DR @1%d@/@2%d@/ segment DP3: Line PLC Process Control Message -
fault
Failure
2
DR @1%d@/@2%d@/DP3:
PLC Process Control Message -
@5%d@.@6%d@m/wire break A /
Failure
@3%d@ @4%d@
3
DR @1%d@/@2%d@/DP3:
PLC Process Control Message -
@5%d@.@6%d@m/short A/@3%d@
Failure
@4%d@
4
DR @1%d@/@2%d@/DP3:
PLC Process Control Message -
@5%d@.@6%d@m/wire break B/
Failure
@3%d@ @4%d@
5
DR @1%d@/@2%d@/DP3:
PLC Process Control Message -
@5%d@.@6%d@m/short B/@3%d@
Failure
@4%d@
Basis Library (V9.0 SP3)
62
Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.8 DREP: Diagnostic Repeater in the DP master system
Message block ALARM_8P
Message no. Default message text
Message class
6
DR @1%d@/@2%d@/DP3:
PLC Process Control Message -
@5%d@.@6%d@m/wire break AB or ter- Failure
minating resistor missing/@3%d@
@4%d@
7
DR @1%d@/@2%d@/DP3:
PLC Process Control Message -
@5%d@.@6%d@m/short AB or too
Failure
many terminating resistors/@3%d@
@4%d@
8
DR @1%d@/@2%d@: @7W
%t#DREP_TXT@
PLC Process Control Message Failure
You will find the message texts and their text numbers in "Text library for DREP (Page 537)".
Assignment of associated values
Message block ALARM_8P EV_ID1
EV_ID2
Associ- ated value
1 2 3 4 5 6 1 2 3 4 5 6 7
Block parameter SUBN_ID PADP_ADR
SUBN_ID PADP_ADR
Meaning
DP master system ID (byte) Address of diagnostic repeater (byte) Station x (segment DP2) Station y (segment DP2) Removal of diagnostic repeater (segment DP2) Removal of diagnostic repeater (segment DP2) DP master system ID (byte) Address of diagnostic repeater (byte) Station x (segment DP3) Station y (segment DP3) Removal of diagnostic repeater (segment DP3) Removal of diagnostic repeater (segment DP3) Text number (Message 1 - 2) of DREP_TXT
See also
Message Classes (Page 531)
Basis Library (V9.0 SP3)
Function Manual, 06/2019, A5E40797470-AD
63
Family: @System 6.9 DREP_L: Diagnostic Repeater downstream of a Y-Link
6.9
DREP_L: Diagnostic Repeater downstream of a Y-Link
6.9.1
Description of DREP_L
Object name (type + number) FB 125 · DREP_L block I/Os (Page 68)
Area of application
The DREP_L block evaluates diagnostic data from a SIMATIC diagnostic repeater for PROFIBUS DP. The diagnostic repeater (after DPV0) must be connected downstream of a Y-Link (after DPV1).
Calling OBs
OB 1 OB 82 OB 86 OB 100
Cyclic processing Diagnostic interrupt Rack failure Warm restart (startup, message initialization)
Use in CFC
The following actions are executed automatically with the "Generate module drivers" CFC function:
· The OB_DIAG1 block is integrated into the run sequence upstream of DREP_L.
· The following addresses are configured:
The diagnostic address of the DP/PA link (DADDR) is connected downstream of the diagnostic repeater
The geographical address (SUBN1_ID, SUBN2_ID, RACK_NO and PADP_ADR)
· The following I/Os are interconnected:
The OUT structures CPU_DIAG of the OB_BEGIN block and RAC_DIAG of the OB_DIAG1 block with the DREP_L INOUT structures of the same name.
The EN input is interconnected with the output of an AND block. The inputs of the AND block with the EN_SUBx outputs (x = number of the DP master system) of the OB_BEGIN block, with EN_Rxxx (xxx = rack/station number) of the SUBNET block and with EN_F of the OB_DIAG1 block.
EN_DIAG with the EN_DIAG output of the OB_DIAG1 block.
Basis Library (V9.0 SP3)
64
Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.9 DREP_L: Diagnostic Repeater downstream of a Y-Link
Function and method of operation
The diagnostics repeater is assigned the following tasks:
· Diagnostics function for two PROFIBUS segments (DP2 and DP3): The diagnostics function returns the location and cause of line faults, such as a wire break or missing terminating resistors. The error location is output, including a reference to the relevant nodes, e.g., "Short-circuit to shielding at signal line A, node 12 and 13".
· Repeater function for three PROFIBUS segments (DP1, DP2, DP3): The diagnostics repeater amplifies data signals on the bus and interconnects the relevant RS-485 segments.
· Galvanic/electrical isolation of the PG interface from other bus segments: Even if the system is operating at higher transmission rates, interference due to the removal or connection of PG cables is not to be expected at the other PROFIBUS DP segments.
The manual titled Diagnostic Repeaters for PROFIBUS DP contains information about the structure of line error states at the DP1, DP2 and DP3 segments and describes the PG interface.
Block DREP_L only reports diagnostic events at segments DP2 and DP3 of the diagnostic repeater.
Events of the DP1 segment are reported as general "Cable disturbance" group error.
The PG interface is not evaluated and does not result in a message.
Failure and return of the diagnostics repeater are detected by the upstream OB_DIAG1 block, and are forwarded to the block to report "DR failure".
If an error occurs, an incoming "line error" group message is generated for each segment (DP2 or DP3) when a diagnostic repeater detects the error event (bits in the diagnostic message frame indicating the cause of error):
Bit Description
A.0 1: The location and cause of the error cannot be identified (possibly electromagnetic interference) A.1 CPU redundancy loss A.2 1: - A.3 1: Further measurement circuits at the segment, the other diagnostic repeater is connected
to its segment DP2 A.4 1: Further measurement circuits at the segment, the other diagnostic repeater is connected
to its segment DP3 A.5 1: - A.6 1: Cause of error is not clearly identified A.7 1: Critical message frame error rate B.0 1: B.1 1: B.2 1: - B.3 1: B.4 1: B.5 1: - B.6 1: B.7 1: C.0 1: Segment automatically switched off due to continuous zero level on the line.
Basis Library (V9.0 SP3)
Function Manual, 06/2019, A5E40797470-AD
65
Family: @System 6.9 DREP_L: Diagnostic Repeater downstream of a Y-Link
Bit Description C.1 1: Segment automatically switched off due to constantly fluctuating line levels. C.2 1: - C.3 1: - C.4 1: More than 32 nodes connected to the measurement segment C.5 1: The distance between the node and the diagnostic repeater exceeds the permitted
line length C.6 1: The maximum permitted number of diagnostic repeaters connected in series has been ex-
ceeded C.7 1: - -
The outgoing message will be generated when all segment bits are equal to zero.
Call HW Config to analyze details of events output by the diagnostic repeater.
An appropriate incoming/outgoing message will be generated for each segment (DP2 or DP3) in response to the following events detected by a diagnostic repeater:
Bit Description A.0 1: A.1 1:A.2 1: A.3 1: A.4 1: A.5 1: A.6 1: A.7 1: B.0 1: Wire break at signal line A B.1 1: Short-circuit to shielding at signal line B B.2 1: B.3 1: Short-circuit to shielding at signal line A B.4 1: Wire break at signal line B B.5 1: B.6 1: Wire break at signal line A and/or B, or the terminating resistor is missing B.7 1: Short-circuit between signal line A and/or B, or an additional terminating resistor has been
installed C.0 1: C.1 1: C.2 1: C.3 1: C.4 1: C.5 1: -. C.6 1: C.7 1: -
Events detected by the diagnostics repeater are acquired synchronously in OB 82. Diagnostic event data is fetched via SFB 54 in the OB_BEGIN block and written to the structure DINFO. The function always sets only one bit to indicate the cause of an incoming event. Bit C7 may also be
Basis Library (V9.0 SP3)
66
Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.9 DREP_L: Diagnostic Repeater downstream of a Y-Link
set if the diagnostics repeater has detected further errors. In this case, all previously reported events will be queued. DREP_L generates a corresponding group error message via ALARM_8P. Flutter messages may occur, particularly in response to error causes A.0.1 and A.6.1. They are suppressed as follows:
After an outgoing message, a new outgoing message will be delayed by the time in [s] set at the DELAY parameter. If a further fault is queued, the outgoing message will not be generated until this fault is outgoing.
Error handling
The block evaluates the error information from ALARM_8P, and writes it to the corresponding output parameters.
You will find additional information in the "Error information of output parameter MSG_STATx (Page 530)" section.
The block reports a diagnostic error if an error occurs while reading the diagnostic data, or if any other fault corrupts diagnostic data.
Startup characteristics
ALARM_8P messages are initialized by the DREP_L block The current diagnostics information is read from the diagnostics repeater using SFB 52 (RDREC).
Overload behavior
In the event of an overload, the upstream OB_DIAG1 block prevents DREP_L being called for diagnostics.
Dynamic response: Not available
Message response:
The multiple instances ALARM_8P are only called if a message is to be output by this instance. It is only at this point that previously acknowledged messages are updated by the corresponding ALARM block. If the connection to WinCC is down, each ALARM_8P instance can hold up to two message statuses of its event ID. Flutter messages can be suppressed via the DELAY input.
The block generates the messages listed below:
OB no. Start event
1
Cyclic processing
82
Diagnostic interrupt
100 Restart
Message
Call of ALARM_8P due to incomplete transfer or unacknowledged message Group message Initialization of ALARM_8P
Basis Library (V9.0 SP3)
Function Manual, 06/2019, A5E40797470-AD
67
Family: @System 6.9 DREP_L: Diagnostic Repeater downstream of a Y-Link
Operator control and monitoring If asset management is used in the project and the diagnostic screens have been generated, the faceplate can be called via its block icon. For additional information, refer to the "Process Control System PCS 7; Maintenance Station" manual.
Additional information For additional information, refer to the sections: Message texts and associated values of DREP_L (Page 69) Maintenance status MS (Page 533)
6.9.2
I/Os of DREP_L
The factory setting of the block display in the CFC is identified in the "I/O" column:
I/O name bold = I/O visible, I/O name normal = I/O not visible.
You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15)".
Input parameters
I/O (parameter) DADDR DELAY DIAG_BUF
EN_DIAG EN_MSG EV_IDx MS PADP_ADR RACK_NO SUBN1_ID SUBN2_ID
Meaning
Type
Diagnostic address of the DP/PA link Interrupt delay (s) Entry in diagnostic buffer (relevant for maintenance person- nel) 1 = Queued diagnostic event 1 = enable message Message number Maintenance status DP/PA address of the diagnostic repeater Number of the rack ID of the primary DP master system ID of the redundant DP master system
INT INT BOOL
BOOL BOOL DWORD DWORD BYTE BYTE BYTE BYTE
De- fault 0 2 0
0 1 0 0 255 255 255 255
Output parameters
I/O (parameter) DINFO MSG_ACKx
Meaning
Diagnostic information from the diagnostic repeater Message acknowledgment
Type
STRUCT WORD
De- fault
0
Basis Library (V9.0 SP3)
68
Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.9 DREP_L: Diagnostic Repeater downstream of a Y-Link
I/O (parameter)
MSG_STATx O_MS QDREPF QERR
Meaning
Message error information Maintenance status 1 = Removed/faulty diagnostic repeater 1 = program error
Type
WORD DWORD BOOL BOOL
De- fault
0 0 0 1
In/out parameters
I/O (parameter) ACC_MODE CPU_DIAG RAC_DIAG
Meaning
1 = accept MODE settings CPU diagnostics OB_DIAG1 diagnostics
Type
BOOL STRUCT STRUCT
De- fault
0
Additional information For additional information, refer to the sections: Message texts and associated values of DREP_L (Page 69) Maintenance status MS (Page 533)
6.9.3
Message texts and associated values of DREP_L
Assignment of message text and message class
Message block ALARM_8P
EV_ID1
Message no. Default message text
Message class
1
DR @1%d@/@2%d@/@3%d@/ Segment PLC Process Control Message -
DP2: Line fault
Failure
2
DR @1%d@/@2%d@/@3%d@/DP2:
PLC Process Control Message -
@6%d@.@7%d@m/wire break A/
Failure
@4%d@ @5%d@
3
DR @1%d@/@2%d@/@3%d@/DP2:
PLC Process Control Message -
@6%d@.@7%d@m/short A/@4%d@
Failure
@5%d@
4
DR @1%d@/@2%d@/@3%d@/DP2:
PLC Process Control Message -
@6%d@.@7%d@m/wire break B/
Failure
@4%d@ @5%d@
5
DR @1%d@/@2%d@/@3%d@/DP2:
PLC Process Control Message -
@6%d@.@7%d@m/short B/@4%d@
Failure
@5%d@
Basis Library (V9.0 SP3)
Function Manual, 06/2019, A5E40797470-AD
69
Family: @System 6.9 DREP_L: Diagnostic Repeater downstream of a Y-Link
Message block ALARM_8P
EV_ID2
Message no. Default message text
Message class
6
DR @1%d@/@2%d@/@3%d@/DP2:
PLC Process Control Message -
@6%d@.@7%d@m/wire break AB or ter- Failure
minating resistor missing/@4%d@
@5%d@
7
DR @1%d@/@2%d@/@3%d@/DP2:
PLC Process Control Message -
@6%d@.@7%d@m/short AB or too
Failure
many terminating resistors/@4%d@
@5%d@
8
DR @1%d@/@2%d@/@3%d@/ Segment PLC Process Control Message -
DP1: Line fault
Failure
1
DR @1%d@/@2%d@/@3%d@/ Segment PLC Process Control Message -
DP3: Line fault
Failure
2
DR @1%d@/@2%d@/@3%d@/DP3:
PLC Process Control Message -
@6%d@.@7%d@m/wire break A/
Failure
@4%d@ @5%d@
3
DR @1%d@/@2%d@/@3%d@/DP3:
PLC Process Control Message -
@6%d@.@7%d@m/short A/@4%d@
Failure
@5%d@
4
DR @1%d@/@2%d@/@3%d@/DP3:
PLC Process Control Message -
@6%d@.@7%d@m/wire break B/
Failure
@4%d@ @5%d@
5
DR @1%d@/@2%d@/@3%d@/DP3:
PLC Process Control Message -
@6%d@.@7%d@m/short B/@4%d@
Failure
@5%d@
6
DR @1%d@/@2%d@/@3%d@/DP3:
PLC Process Control Message -
@6%d@.@7%d@m/wire break AB or ter- Failure
minating resistor missing/@4%d@
@5%d@
7
DR @1%d@/@2%d@/@3%d@/DP3:
PLC Process Control Message -
@6%d@.@7%d@m/short AB or too
Failure
many terminating resistors/@4%d@
@5%d@
8
DR @1%d@/@2%d@/@3%d@: @8W
PLC Process Control Message -
%t#DREP_L_TXT@
Failure
You will find the message texts and their text numbers in "Text library for DREP_L (Page 537)".
Assignment of associated values
Message block ALARM_8P
EV_ID1
Associated value
1 2 3 4 5 6
Block parameter
SUBN_ID1 RACK_NO PADP_ADR
Meaning
DP master system ID (byte) Rack/station number (byte) Address of diagnostic repeater (byte) Station x (segment DP2) Station y (segment DP2) Removal of diagnostic repeater (segment DP2)
Basis Library (V9.0 SP3)
70
Function Manual, 06/2019, A5E40797470-AD
See also
Family: @System 6.10 FFD_CIF: Monitoring FF slaves in CIF mode
Message block ALARM_8P
EV_ID2
Associated value
7 1 2 3 4 5 6 7
Block parameter
SUBN_ID1 RACK_NO PADP_ADR
Meaning
Removal of diagnostic repeater (segment DP2) DP master system ID (byte) Rack/station number (byte) Address of diagnostic repeater (byte) Station x (segment DP3) Station y (segment DP3) Removal of diagnostic repeater (segment DP3) Removal of diagnostic repeater (segment DP3)
If SUBN_ID1 = 16#FF, SUBN_ID2 is used as associated value 1.
Message Classes (Page 531)
6.10
FFD_CIF: Monitoring FF slaves in CIF mode
6.10.1
Description of FFD_CIF
Object name (type + number) FB 145 · I/Os of FFD_CIF (Page 73)
Area of application and method of operation
The FFD_CIF blocks monitors the higher-level errors of a field device, such as failure/return. The block runs acyclically.
The block FFD_CIF is enabled to run by the higher-level DPAY_V1 block. Start and diagnostic information is read from the CPU_DIAG structure. The event to be evaluated is entered in the start information (CPU_DIAG) of OB_BEGIN. The block FFD_CIF checks the geographic address and SLOT_NO of the FF device to determine whether it is responsible for this event.
Byte 3 of the additional alarm information contains the slot number of the field device that triggered the diagnostic interrupt. The corresponding slot is enabled.
The parameter EN_MSG_D = 1 is still set here. This means that the AS asset faceplate for the FF device accesses this block; messages and maintenance state are generated here.
Basis Library (V9.0 SP3)
Function Manual, 06/2019, A5E40797470-AD
71
Family: @System 6.10 FFD_CIF: Monitoring FF slaves in CIF mode
Use in CFC
The following actions are executed automatically with the "Generate module drivers" CFC function:
· The FFD_CIF block is installed downstream from the DPAY_V1 block.
· The RACK_NO, DADDR, EN_MSG_D, SUBN1_ID, SUBN2_ID, SLOT_NO and FFDP_ADR inputs are configured.
· The EN input is interconnected with the output of an AND block. These block inputs are interconnected with the outputs EN_SUBx (x = number of the DP master system) of the OB_BEGIN block, EN_Rxxx (xxx = rack/station number) of the SUBNET block, with EN_Mx (x= number of the FF device) of the DPAY_V1 block and EN_F of the OB_DIAGF block.
· The CPU_DIAG OUT structure of the OB_BEGIN block and SUB_DIAG of the SUBNET block are interconnected with the IN_OUT structures of the FFD_CIF block.
· RAC_DIAG is interconnected with the OUT structure RAC_DIAG of OB_DIAGF block.
· DINFO is interconnected with the OUT structure DINFO of the OB_DIAGF block.
· The OUT structure FF_DIAG of OB_DIAGF is interconnected with the IN_OUT structure of the same name of FFD_CIF.
Calling OBs
The block must be installed in the run sequence in the following OBs:
OB 1 OB 72 OB 70 OB 82 OB 83 OB 86 OB 100
Cyclic program CPU redundancy loss Redundancy loss Diagnostic interrupt Remove/insert module interrupt (failure/return of a field device) Rack failure Restart
Operator control and monitoring
If asset management is used in the project and the diagnostic screens have been generated, the faceplate can be called via its block icon.
For additional information, refer to the "Process Control System PCS 7; Maintenance Station" manual.
Basis Library (V9.0 SP3)
72
Function Manual, 06/2019, A5E40797470-AD
Family: @System
6.10 FFD_CIF: Monitoring FF slaves in CIF mode
Message response
The DELAY input is used to delay the outputting of error messages for an outgoing, higherpriority error. For example, if the FFD_CIF block recognizes an outgoing error at a DP master connected to it, it initially assumes that there is a faulty assigned DP slave in the rack it monitors, and sets the corresponding output SUBNxERR. The error status is not reset until the DP slave returns (in this case: OB 86, OB 70). The FFD_CIF blocks suppress the potential slave failure states for DELAY seconds so as not to trigger a surge of messages from DP slaves which are not yet synchronized when the master returns. An error message is only output to the OS when the DP slave has not reported its return before this delay time has expired.
Note: Do not set the value of DELAY too high, since messages reporting faulty DP slaves or their removal during a master failure will be output too late to the OS after the DP master returns.
6.10.2
I/Os of FFD_CIF
I/Os of FFD_CIF The factory setting of the block display in the CFC is identified in the "I/O" column.
I/O name bold = I/O visible, I/O name normal = I/O not visible.
You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15)".
Input parameters
I/O (parameter) DADDR DELAY DINFO DIAG_BUF
EN_MSG EN_MSG_D EV_ID FFDP_ADR MS RACK_NO SLOT_NO SUBN1_ID SUBN2_ID SUBN_TYP
Meaning
Diagnostic address of the FF link Interrupt delay (s) Diagnostic information Entry in diagnostic buffer (relevant for maintenance personnel) 1 = enable interrupt 1 = Enable message "Device failure" Message number FF slave address Maintenance status Rack number Slot number ID of the primary DP master system ID of the redundant DP master system 1 = external DP interface
Data type INT INT STRUCT BOOL
BOOL BOOL DWORD BYTE DWORD BYTE BYTE BYTE BYTE BOOL
Default 0 15
0
1 1 0 16#FF 0 16#FF 16#FF 16#FF 16#FF 0
Basis Library (V9.0 SP3)
Function Manual, 06/2019, A5E40797470-AD
73
Family: @System 6.10 FFD_CIF: Monitoring FF slaves in CIF mode
Output parameters
I/O (parameter) MSG_ACK MSG_STAT O_MS OMODE QMODF QRACKF RETURN_CODE SUBN1ACT SUBN2ACT SUBN1ERR SUBN2ERR V1_MODE
Meaning
Message acknowledgment Error message status Maintenance status Channel 0 mode 1 = module removed/defective 1 = higher-level error Return value of the function 1 = Slave 1 is active 1 = Slave 2 is active 1 = Error in the primary DP master system 1 = Error in the redundant DP master system 1 = DPV1 mode of the DP master system
In/out parameters
I/O (parameter) ACC_ID CPU_DIAG FF_DIAG RAC_DIAG SUB_DIAG
Meaning 1 = accept MODE settings System structure: CPU diagnostics Diagnostics of the FF device System structure RACK diagnostics System structure: SUBNET diagnostics
Data type
WORD WORD DWORD DWORD BOOL BOOL INT BOOL BOOL BOOL BOOL BOOL
Default 0 0 0 0 0 0
0 0 0 0 0
Data type BOOL STRUCT STRUCT STRUCT STRUCT
Default 0
Basis Library (V9.0 SP3)
74
Function Manual, 06/2019, A5E40797470-AD
6.10.3
Family: @System 6.11 FFDP_L1: Monitoring FF slaves with maximum 32 values
Message texts and associated values of FFD_CIF
Message texts and associated values of FFD_CIF Assignment of message text and message class (Page 531)
Message block
EV_ID1 (ALARM_8P)
Message number 1
2
3
4
5
6 7
8
Default message text
Message class
Device @1%d@/ @2%d@/@3%d@: Main- PLC Process Control Message -
tenance alarm
Failure
Device @1%d@/ @2%d@/@3%d@: Main- PLC Process Control Message -
tenance demanded
Error
Device @1%d@/ @2%d@/@3%d@: Mul- PLC Process Control Message -
tiple alarm (OB 83)
Failure
Device @1%d@/ @2%d@/@3%d@: Mul- PLC Process Control Message -
tiple alarm (OB 82)
Failure
Device @1%d@/ @2%d@/@3%d@: Main- Preventative Maintenance -
tenance required
Standard
No message
Device @1%d@/ @2%d@/@3%d@: Con- PLC Process Control Message figuration error: Name does not match Failure address
Device @1%d@/ @2%d@/@3%d@: Fail- PLC Process Control Message -
ure
Failure
Assignment of Associated Values
Associated value 1 2 3
Block parameters DP master system ID (SUBN_ID) Rack/station number (RACK_NO) FF slave address (FFDP_ADR)
6.11
FFDP_L1: Monitoring FF slaves with maximum 32 values
6.11.1
Description of FFDP_L1
Object name (type + number) FB 139 · I/Os of FFDP_L1 (Page 77)
Basis Library (V9.0 SP3)
Function Manual, 06/2019, A5E40797470-AD
75
Family: @System
6.11 FFDP_L1: Monitoring FF slaves with maximum 32 values
Area of application and method of operation
The FFDP_L1 block monitors the higher-level errors of a field device, such as failure/return and runs acyclically.
The FFDP_L1 block is enabled to run by the higher-level DPAY_V1 block. The event to be evaluated is entered in the start information (CPU_DIAG) of OB_BEGIN. The FFDP_L1 block checks the geographic address and SLOT_NO of the FF device to determine whether it is responsible for this event.
Byte 3 of the additional alarm information contains the slot number of the field device that triggered the diagnostic interrupt. The corresponding slot is enabled.
If a higher-level error goes away the diagnostics is read per SFC 13 from FF link (the data are all located locally on the link and do not have to be retrieved by the FF device) and reported accordingly.
The FFDP_L1 block monitors
· FF devices downstream from an FF link (DPV1 slave)
It generates the MODE (FF_MODE) and the value status for the signal processing blocks. The subordinate blocks FF_MOD32 are always enabled for processing and run cyclically. The information is relayed via the structure FF_DIAG to the FF_MOD32. This structure outputs the message.
Calling OBs
The block must be installed in the run sequence in the following OBs:
OB 1 OB 72 OB 70 OB 82 OB 83 OB 85 OB 86 OB 100
Cyclic program CPU redundancy loss Redundancy loss Diagnostic interrupt Remove/insert module interrupt (failure/return of a field device) Program execution error Rack failure Restart
Use in CFC
The following actions are executed automatically with the "Generate module drivers" CFC function:
· The FFDP_L1 block is installed downstream from the DPAY_V1 block.
· The CPU_DIAG OUT structure of the OB_BEGIN block and SUB_DIAG of the SUBNET block are interconnected with the IN_OUT structures of the same name of block FFDP_L1.
· RAC_DIAG is interconnected with the OUT structure RAC_DIAG of OB_DIAGF block.
Basis Library (V9.0 SP3)
76
Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.11 FFDP_L1: Monitoring FF slaves with maximum 32 values
· The following will be configured:
Diagnostic address of the FF link DADDR
Geographical address (SUBN1_ID, SUBN2_ID, RACK_NO) of the FF device
SLOT_NO
FF address of the FF device (FFDP_ADR)
MODE_xy (mode of the FF device)
NUM_IODATA
· The EN input is interconnected with the output of an AND block. These block inputs are interconnected with the outputs EN_SUBx (x = number of the DP master system) of the OB_BEGIN block, EN_Rxxx (xxx = rack/station number) of the SUBNET block, with EN_Mx (x= number of the FF device) of the DPAY_V1 block and EN_F of the OB_DIAGF block.
· The QPERAF output is interconnected with the PERAF input of the FF_MOD32.
· The QMODF output is interconnected with the MODF input of the FF_MOD32.
· The FF_DIAG output is interconnected with the FF_DIAG input of the FF_MOD32.
· DINFO is interconnected with the OUT structure DINFO of the OB_DIAGF block.
Message response The DELAY input is used to delay the outputting of error messages for an outgoing, higherpriority error. For example, if the FFDP_L1 block recognizes an outgoing error at a DP master connected with it, it initially assumes that there is a faulty assigned DP slave in the rack it monitors, and sets the corresponding output SUBNxERR. The error status is not reset until the DP slave returns (in this case: OB 86, OB 70). The FFDP_L1 blocks suppress the potential slave failure states for DELAY seconds so as not to trigger a surge of messages from DP slaves which are not yet synchronized when the master returns. An error message is only output to the OS when the DP slave has not reported its return before this delay time has expired.
Note: Do not set the value of DELAY too high, since messages reporting faulty DP slaves or their removal during a master failure will be output too late to the OS after the DP master returns.
6.11.2
I/Os of FFDP_L1
I/Os of FFDP_L1 The factory setting of the block display in the CFC is identified in the "I/O" column.
I/O name bold = I/O visible, I/O name normal = I/O not visible.
You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15)".
Basis Library (V9.0 SP3)
Function Manual, 06/2019, A5E40797470-AD
77
Family: @System 6.11 FFDP_L1: Monitoring FF slaves with maximum 32 values
Input parameters
I/O (parameter) DADDR DELAY DIAG_BUF
FFDP_ADR MODE NUM_IODATA RACK_NO SLOT_NO SUBN_TYP SUBN1_ID SUBN2_ID
Meaning
Diagnostic address of the FF link Interrupt delay (s) Entry in diagnostic buffer (relevant for maintenance personnel) Address of the FF device Device status Number of I/O data in the FF device Number of the rack Number of the slot 1 = external DP interface ID of the primary DP master system ID of the redundant DP master system
Data type INT INT BOOL
BYTE WORD INT BYTE BYTE BOOL BYTE BYTE
Default 0 15 0
0 0 0 0 0 0 16#FF 16#FF
Output parameters
I/O (parameter) EN_D_Q FF_DIAG OMODE QERR QMODF QPERAF QRACKF RAC_DIAG RETURN_CODE_O SUBN1ACT SUBN2ACT SUBN1ERR SUBN2ERR V1_MODE
Meaning
1 = Processing of the quality code FF device diagnostics Operating mode slot 1 = Error runtime 1 = Error/defect field device 1 = Access error I/O 1 = higher-level error System structure RACK diagnostics Return value 1 = Slave 1 is active 1 = Slave 2 is active 1 = Error in the primary DP master system 1 = Error in the redundant DP master system DPV1 mode of the DP master system
Data type
BOOL DWORD DWORD BOOL BOOL BOOL BOOL STRUCT INT BOOL BOOL BOOL BOOL BOOL
Default 0 0 0 1 0 0 0
0 0 0 0 0 0
In/out parameters
I/O (parameter) ACC_MODE CPU_DIAG DINFO FF_DIAG_I SUB_DIAG
Meaning 1 = accept MODE settings CPU diagnostics Diagnostic information Diagnostics of the FF device System structure: SUBNET diagnostics
Data type BOOL STRUCT STRUCT STRUCT STRUCT
Default 0
Basis Library (V9.0 SP3)
78
Function Manual, 06/2019, A5E40797470-AD
6.12
Family: @System 6.12 FF_MOD32: Diagnostics of an FF slave (downstream from FF link DPV1)
FF_MOD32: Diagnostics of an FF slave (downstream from FF link DPV1)
6.12.1
Description of FF_MOD32
Object name (type + number) FB 124 · I/Os of FF_MOD32 (Page 80)
Area of application and method of operation
The block reports the maintenance status of an FF field device downstream from an FF link. For diagnostics in the Maintenance Station, all error sources will be linked with OR and the worst will be assigned to the MS output. The channel blocks (FbAnIn, FbAnOu, FbDiIn, FbDiOu) will be controlled by quality codes.
The block analyses cyclically all events that affect an FF device and reports the following events:
· Evaluation of the RAC_DIAG info (from FFDP_L1): Device failure
· Evaluation of the FF_DIAG info (from FFDP_L1): Diagnostics
Use in CFC
The following actions are executed automatically with the "Generate module drivers" CFC function:
· The block is integrated in the run sequence upstream of the FbAxXx, FbDxXx block.
· The SUBN1_ID, SUBN2_ID, RACK_NO, SLOT_NO, FFDP_ADR and NUM_IODATA inputs are configured.
· The block inputs are interconnected with the following outputs:
FF_DIAG with FF_DIAG output of the FFDP_L1 block
MODE_xy with OMODE_xy outputs of the FFDP_L1 block
MODF, PERAF with QMODF and QPERAF outputs of the FFDP_L1 block
RAC_DIAG with output structure RAC_DIAG of the OB_DIAGF block
QC_x input with icon of the FF field device
EN_D_Q with EN_DQ output of the FFDP_L1 block
· The output parameter of DXCHG_xx is interconnected with the following channel block at the DataXchg parameter.
· The output parameter of O_MS is interconnected with the following channel block at the MS parameter.
Basis Library (V9.0 SP3)
Function Manual, 06/2019, A5E40797470-AD
79
Family: @System 6.12 FF_MOD32: Diagnostics of an FF slave (downstream from FF link DPV1)
· The output parameter of OMODE_xy is interconnected with the following channel block at the OMODE_xy parameter.
· The OUT structure CPU_DIAG of the OB_BEGIN block is interconnected with the IN_OUT structures of the same name of the FFDP_L1 block.
Calling OBs
OB no. OB 1 OB 100
Start Event Cyclic program Warm restart
Message
The Alarm_8P is initialized at startup (OB 100)
Operator control and monitoring
If asset management is used in the project and the diagnostic screens have been generated, the faceplate can be called via its block icon.
For additional information, refer to the "Process Control System PCS 7; Maintenance Station" manual.
6.12.2
I/Os of FF_MOD32
I/Os of FF_MOD32 The factory setting of the block display in the CFC is identified in the "I/O" column.
I/O name bold = I/O visible, I/O name normal = I/O not visible.
You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15)".
Input parameters
I/O (parameter) EN_D_Q EN_MSG EV_ID1 EV_ID2 FFDP_ADR FF_DIAG MODE_xx MODF MS MS_REQ NUM_IODATA
Meaning
1 = Processing of the quality code 1 = enable interrupt Message number 1 Message number 2 Address of the FF device Diagnostics of the FF device Device mode (xx = IOData 0 - 31) 1 = field device error/fault Maintenance status 1 = Request maintenance release Number of I/O data in the FF device
Data type
BOOL BOOL DWORD DWORD BYTE DWORD DWORD BOOL DWORD BOOL INT
Default 0 1 0 0 0
0 0 0 0 0
Basis Library (V9.0 SP3)
80
Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.12 FF_MOD32: Diagnostics of an FF slave (downstream from FF link DPV1)
I/O (parameter) PERAF QC_xx RACK_NO SLOT_NO SUBN1_ID SUBN2_ID
Meaning 1 = I/O access error Status of FF field device (x = channel 0 to 31) Rack number Slot number ID of the primary DP master system ID of the redundant DP master system
Data type BOOL BYTE BYTE BYTE BYTE BYTE
Default 0 0 0 0 16#FF 16#FF
Output parameter
I/O (parameter) B_QC DXCHG_xx
DXCHG1_xx
DXCHG1 EXT_STAT EXT_STAT_A
FS_ACTIVE IODATA_ACTIVE IODATA_EXIST IODATA_OK MS_XCHG_00 MS_XCHG_xx
MSGSTAT1 MSGSTAT2 MSG_ACK1 OMODE_xx O_MS QERR QMODF QPERAF QRACKF
Meaning
Quality code, bit-granular 1st internal data exchange channel for channel block 2nd internal data exchange channel for channel block Bidirectional data exchange channel Release for maintenance - extended status Extended status - Application Application data transfer active Flutter suppression Channel active I/O data available I/O data OK Maintenance Status - Data exchange channel Maintenance Status - Data exchange channel (xx = 00 - 31) Message error - information 1 Message error - information 2 Message acknowledgment 1 Value status FF field device (xx = IOData 0 to 31) Maintenance status 1 = program error 1 = field device error/fault 1 = I/O access error 1 = higher-level error
Data type STRUCT DWORD
Default 0
DWORD
0
DWORD
0
DWORD
0
DWORD
0
DWORD DWORD DWORD DWORD DWORD DWORD
0 16#00000000 0 0 0 0
WORD
0
WORD
0
WORD
0
DWORD
0
DWORD
0
BOOL
1
BOOL
0
BOOL
0
BOOL
0
In/out parameters
I/O (parameter) CPU_DIAG RAC_DIAG
Meaning CPU diagnostics System structure: SUBNET diagnostics
Data type STRUCT STRUCT
Default
Basis Library (V9.0 SP3)
Function Manual, 06/2019, A5E40797470-AD
81
Family: @System 6.12 FF_MOD32: Diagnostics of an FF slave (downstream from FF link DPV1)
6.12.3
Message texts and associated values of FF_MOD32
Message texts and associated values of FF_MOD32 Assignment of message text and message class (Page 531)
Message block EV_ID1 (ALARM_8P)
EV_ID2 (NO- TIFY_8P)
Message no. Default message text
Message class
1
Device @1%d@/ @2%d@/@3%d@: Main- PLC Process Control Message -
tenance alarm
Failure
2
Device @1%d@/ @2%d@/@3%d@: Main- PLC Process Control Message -
tenance demanded
Error
3
Device @1%d@/ @2%d@/@3%d@: Main- Preventative Maintenance -
tenance required
Standard
4
Device @1%d@/ @2%d@/@3%d@: Fail- PLC Process Control Message -
ure
Failure
5
Device @1%d@/@2%d@/@3%d@: @4W PLC Process Control Message -
%#FF_MOD32_TXT@
Failure
6
No message
No message
7
Device @1%d@/ @2%d@/@3%d@: Main- PLC Process Control Message -
tenance demanded (external)
Error
8
Device @1%d@/ @2%d@/@3%d@: Main- Preventative Maintenance -
tenance required (external)
Standard
1
Device @1%d@/ @2%d@/@3%d@: Goes Status Message - PLC
to fail-safe position
2
Device @1%d@/ @2%d@/@3%d@: Mak- Status Message - PLC
ing configuration change
3
Device @1%d@/ @2%d@/@3%d@: Sim- Status Message - PLC
ulation
4
Device @1%d@/ @2%d@/@3%d@: Proc- Status Message - PLC
ess-related, no maintenance
5
Device @1%d@/ @2%d@/@3%d@: Proc- Status Message - PLC
ess-related, no maintenance
6
Device @1%d@/ @2%d@/@3%d@: Local Status Message - PLC
operation/functional check
7
Device @1%d@/ @2%d@/@3%d@: De- Status Message - PLC
vice passivated
8
No message
Assignment of Associated Values
Associated value 1 2 3 4
Block parameters DP master system ID (SUBN_ID) Rack/station number (RACK_NO) FF slave address (FFDP_ADR) Text number (message 5) from FF_MOD32_TXT
Basis Library (V9.0 SP3)
82
Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.13 FM_CNT: Programming and controlling FM 350 modules
You can find the message texts and their text numbers in the section "Text library for FF_MOD32 (Page 536)".
6.13
FM_CNT: Programming and controlling FM 350 modules
6.13.1
Description of FM_CNT
Object name (type + number) FB 126 · FM_CNT Block I/Os (Page 86)
Area of application
The FM_CNT block assigns parameters and controls the FM 350-1 and FM 350-2 modules It writes the counter levels, limits and comparison values of the FM 350-2 module.
Calling OBs
OB 100 and the cyclic OB (100 ms recommended) used for transmitting data. Also note the assignments (Page 532) to the FM_CO block.
Use in CFC
The following actions are executed automatically with the "Generate module drivers" CFC function:
· The block is installed in the cyclic OB upstream of the CH_CNT blocks.
· The block runtime group is installed in OB 100 downstream of MOD_D1.
· The LADDR, FM_MODE, RACK_NO, SUBN1_ID, SUBN2_ID, and SLOT_NO inputs are configured.
· The MODEx inputs are interconnected with the OMODEx outputs of the MOD_D1 block.
· The FM_DATA output structure is interconnected with the structure of the same name of the CH_CNT block.
· The OMODEx output is interconnected with the MODE input of the CH_CNT block.
· The OUT structure CPU_DIAG of OB_BEGIN is interconnected with the IN_OUT structure of the same name of FM_CNT.
· The EN_CO input structure is interconnected with the EN_CO_x output structure of the FM_CO block (x = number of the rack).
· The output ENCO is connected to the input ENCOx_yy of the FM_CO block (x = number of the rack, yy = coordination number).
Basis Library (V9.0 SP3)
Function Manual, 06/2019, A5E40797470-AD
83
Family: @System 6.13 FM_CNT: Programming and controlling FM 350 modules
Addressing
The logical base address of the module is entered in the LADDR I/O by the CFC driver generator.
Redundancy
Higher-level block MOD_D1 evaluates the redundancy of DP master systems operating in an H system. Redundancy for two FM 350-1 or FM 350-2 modules is not supported, and must be controlled by the user outside the block.
MODE Setting
Signal states of the MODE_xx input, or QMODE_xx output of the FM_CNT block are described under the MODE settings.
MODE_xx input parameters are available for up to 8 signal channels. Their default setting is "0" (no signal). For each signal channel xx, the operating mode of the FM 350 module must be set at the MODE_xx input (the CFC driver generator does this for you).
The module recognizes the following modes:
Term
Channel not used Continuous counting
One-time counting
Periodic counting
Frequency measurement
Speed measurement
Period duration measure- ment Dosing
Coding MODE 16#0000 16#xx01
16#xx02
16#xx03
16#xx04
16#xx05
16#xx06
16#xx07
Description
Channel of the FM 350 not used. The FM 350 counts continuously, starting with the cur- rent counter level when the internal gate opens. The FM 350 counts from the start value to the end value when the internal gate opens. The FM 350 counts between the start value and the end value when the internal gate opens. The FM 350 determines the frequency pulse sequence at the input. The FM 350 determines the speed of the device connec- ted to the input. The FM 350 determines the duration of the pulse se- quence at the input. Four channels of the FM 350-2 are used for dosing.
The count and measured values can be recorded with the FM 350-2 module, either via the process image (fast update) or via "Read data record" (slower update). If the count and measured values of a channel in the process image are made available, they have to be in alignment in the process image. The following variants are possible.
Term
Count and measured value are not in the process image Only the count value is in the process image Only the measured value is in the process image
Coding MODE 16#Cxxx
16#8xxx
16#4xxx
Description
Read count and measured values via data record
Read measured value via data record and count value in the process image Read count values via data record and measured value in the process image
Basis Library (V9.0 SP3)
84
Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.13 FM_CNT: Programming and controlling FM 350 modules
Term
Count and measured value are in the process image Data type DWORD count and meas- ured value Data type WORD count value
Coding MODE 16#0xxx
16#x0xx
16#x1xx
Data type WORD measured value
16#x2xx
Data type WORD count and measured value
Data type DWORD count and meas- ured value
Data type WORD count value
16#x3xx 16#x8xx 16#x9xx
Data type WORD measured value
16#xAxx
Data type WORD count and measured 16#xBxx value
Description
Read count and measured value in the process im- age
Count value before measured value, both of the data type DWORD
Count value of the the data type WORD before measured value of the data type DWORD
Count value of the data type DWORD before meas- ured value of the data type WORD
Measured value before count value, both of the data type WORD
Measured value before count value, both of the data type DWORD
Measured value of the the data type DWORD be- fore count value of the data type WORD
Measured value of the the data type WORD before count value of the data type DWORD
Count value before measured value, both of the data type WORD
MODE is formed by the linking the operating mode code, and the access type value. Example: Count and measured value in "Dosing" mode of the the data type DWORD is not in the process image MODE = 16#C007.
Error handling The plausibility of input parameters is not checked.
Startup characteristics
Whenever the system or FM 350-1/FM 350-2 starts up, the block coordinates the restart with the module. The CMP_VALx parameters are then loaded into the FM 350.
ALARM_8P is initialized.
Overload behavior Not available
Time response Not available
Message response
The block reports operating and data errors for the FM 350-1 module, and data errors for FM 350-2 using ALARM_8P. The message function can be disabled by setting EN_MSG = FALSE. The MOD_D1 block reports diagnostic interrupts from the FM 350-1 or FM 350-2.
Basis Library (V9.0 SP3)
Function Manual, 06/2019, A5E40797470-AD
85
Family: @System 6.13 FM_CNT: Programming and controlling FM 350 modules
Operator control and monitoring The block has no faceplate.
Additional information For additional information, refer to the sections: Message texts and associated values of FM_CNT (Page 87)
6.13.2
I/Os of FM_CNT
The factory setting of the block display in the CFC is identified in the "I/O" column:
I/O name bold = I/O visible, I/O name normal = I/O not visible.
You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15)".
Input parameters
I/O (parameter) CO_NO DIAG_BUF
EN_MSG EV_ID FM_MODE LADDR MODEx RACK_NO SLOT_NO SUBN1_ID SUBN2_ID
Meaning
Data type
Coordination number for data record reading
INT
Entry in diagnostic buffer (relevant for maintenance person- BOOL nel)
1 = enable message
BOOL
Message number
DWORD
0 = FM 350-1, >0 = FM 350-2
BYTE
Logical address FM 350
INT
Mode channel (x = 0 to 7)
DWORD
Rack number
BYTE
Slot number
BYTE
ID of the primary DP master system
BYTE
ID of the redundant DP master system
BYTE
De- fault 0 0
1 0 0 0 0 0 0 255 255
Output parameters
I/O (parameter) FM_DATA MSG_ACK MSG_STAT OMODEx QDATA_ERR QDONE
Meaning
Structure FM 350 data Message acknowledgment Message error information Mode channel (x = 0 to 7) 1 = Data error 1 = Write new data
Data type
STRUCT WORD WORD DWORD BOOL BOOL
De- fault
0 0 0 0 0
Basis Library (V9.0 SP3)
86
Function Manual, 06/2019, A5E40797470-AD
I/O (parameter)
QDONE_RD QMODF QPARF QRD_ERR QWR_ERR STATUS_RD STATUS_WR
Family: @System 6.13 FM_CNT: Programming and controlling FM 350 modules
Meaning
1 = New data read 1 = Error FM 350 1 = Module not programmed 1 = Error when reading data 1 = Error read data Read status of data record Write status of data record
Data type
BOOL BOOL BOOL BOOL BOOL DWORD DWORD
De- fault
0 0 0 0 0 0 0
In/out parameters
I/O (parameter) ACC_MODE EN_CO ENCO CPU_DIAG
Meaning
1 = accept MODE settings Current coordination number Coordination number CPU diagnostics (system structure)
Data type
BOOL STRUCT BYTE STRUCT
De- fault 0
0
Additional information Additional information is available in the section: Message texts and associated values of FM_CNT (Page 87)
6.13.3
Message texts and associated values of FM_CNT
Assignment of message text and message class
Message block ALARM_8P
EV_ID
Message no. Default message text
1
FM 350 @1%d@/@2%d@/@3%d
@data error number@4%d@
2
FM 350 @1%d@/@2%d@/@3%d
@data error number @5%d@
3
4
5
6
7
8
Message class
PLC Process Control Message Failure PLC Process Control Message Failure No message No message No message No message No message No message
Basis Library (V9.0 SP3)
Function Manual, 06/2019, A5E40797470-AD
87
Family: @System 6.14 IM_TS_PN: Status alarms with time stamps
Assignment of associated values
Message block ALARM_8P
EV_ID
Associ- ated value
1
2
3
4
5
Block parameters
SUBN_ID RACK_NO SLOT_NO DA_ERR_W OT_ERR_B
Meaning
DP master system ID (byte) Rack/station number (byte) Slot number (byte) Data error number Operator error number
See also
Message Classes (Page 531)
6.14
IM_TS_PN: Status alarms with time stamps
6.14.1
Description of IM_TS_PN
Object name (type + number) FB 420 · I/Os of IM_TS_PN (Page 90)
Area of application
The block IM_TS_PM transfers time-stamped process signal changes in a PNIO System to the EventTs/Event16Ts block and reports SOE information from the time stamping DI module to the RACK_PNT block.
Use in CFC
The following actions are executed automatically with the "Generate module drivers" CFC function:
· The IM_TS_PN block is copied from the library and instantiated in a system chart. The block is installed in its runtime group after the RACK_PNT block runtime group in the OB 1, OB 55, and OB 100.
· OR_32TPN is always interconnected between Pcs7DiIT and IM_TS_PN.
· The logical addresses LADDR0/LADDR1 are configured with the logical address(es) of the IM(s) (diagnostics address).
Basis Library (V9.0 SP3)
88
Function Manual, 06/2019, A5E40797470-AD
Family: @System
6.14 IM_TS_PN: Status alarms with time stamps
· The RAC_DIAG structure of the RACK_PNT block is interconnected with the structure of the same name of the IM_TS_PN block.
· The S_CH_xxx and TINF_xxx inputs of the TRIG_INF structure are set. Every signal that is timestamped by the IM has a unique assignment identified by the slot of the module combined with the corresponding channel number. For all 512 channels, this information is entered in the block inputs S_CH_xxx. The information about the triggering is entered in structure TRIG_INF.
Block functions
The IM_TS_PN block reads the messages from the message buffers (up to approx.. 100 data records, max 4096 Bytes) of an IM, and transfers them to a message block for time stamping (EventTs/Event16Ts). The Event-block sends the messages via an ALARM_8P block whose time stamps for its 8 messages are entered in the 1st associated value in an ARRAY of BYTE.
· Hardware interrupt (OB 55): The IM generates a hardware interrupt if there are new messages. The time-stamp status, including the number of the IM data record to be fetched and the number of messages in the data record, are fetched from the start information of the status alarm OB and stored for cyclic processing. If the maximum capacity of the interrupt stack is exceeded, all new information will be lost. The loss of information is indicated by the "Loss of message at IM (buffer overflow)" message.
· Cyclic processing: If any messages are queued in the stack, SFB 52 (RDREC, read data record) reads the relevant data record (message buffer). If there are several data records to be fetched, it will fetch the record that contains the oldest messages (oldest hardware interrupt). The block instance temporarily stores a maximum of 4096 Bytes of data records.The IM can enter new messages in a data record once it has been read. If all data records are in use, the IM enters "Loss of message at IM (buffer overflow)" (incoming) as the last message in the message buffer. "Loss of message at IM (buffer overflow)" (outgoing) is then entered as the first message in the first free data record. Messages received within the interval between a buffer overflow and the enabling of a record will be lost. The slot number/ channel number of the stored messages are compared with the input parameters of the block for slot number/channel number (S_CH_xxx). If they match, the message is written to the corresponding output (TS_xxx).
Startup characteristics
During startup/restart of the IM, the system will generate process interrupts once again for those records which were occupied prior to restart but had not been fetched. The message "Startup data (incoming)" is entered as the first message of the first free data record. After restart, the system checks all monitored digital signals for changes, outputs a message if appropriate. It finally generates the message "Startup data (outgoing)".
During an initial startup, the signal state is set to "Zero". During startup, the block verifies the existence of an IM at its logical address set in LADDR. If this does not exist, it sets the QPARF output to TRUE, and does not access any I/Os in its subsequent cycles. QPARF = FALSE and I/O access is enabled only after the correct module has been inserted, or the logical address has been set correctly. Stored process interrupt data which were not computed before the restart will be deleted.
Basis Library (V9.0 SP3)
Function Manual, 06/2019, A5E40797470-AD
89
Family: @System 6.14 IM_TS_PN: Status alarms with time stamps
Error handling
Errors occurring during data exchange between the block and IM are reported to the RACK_PNT block.
· I/O access error: QPERAF The block could not access the IM. A data record could not be read.
· Block processing error: QERR A block execution error has occurred.
· Module parameter assignment error: QPARF Faulty block configuration: Incorrect logical basic address entered.
· Parameter assignment error: QBPARF Faulty block configuration: The slot/channel number of an IM message does not match any slot/channel number of the block input parameters.
· Rack error: QRACKF Failure of the rack containing the IM or IM failure.
6.14.2
I/Os of IM_TS_PN
The factory setting of the block display in the CFC is identified in the "I/O" column:
I/O name bold = I/O visible, I/O name normal = I/O not visible.
You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15)".
Input parameters
I/O (parameter) EN ACC_MODE DIAG_BUF
LADDR0 LADDR1 S_CH_xxx TRIG_INF
FEATURE TS_SI_IN TS_TmStat_NoSync_IN TS_TmStat_Jitter_IN TS_BufStat_APP_IN TS_BufStat_DAPP_IN TS_SIObStop_APP_IN
TS_SIObStop_DAPP_IN
Meaning
Data type
Default
Enable the block
BOOL
1
Assign the record to be read (0 -1 )
BOOL
0
Release the diagnostic buffer input (De- BOOL
0
bugging)
Logical address IM-Left
INT
0
Logical address IM-Right
INT
0
Slot/ Channel Number (xxx=0..511)
WORD
0
Flank selection for all 512 channels
STRUCT
0 = Trigger 0 ->1, 1 = Trigger 1 -> 0
(from 512 BOOLs)
Features of hardware parameter
DWORD
0
Source identification
STRUCT
Time status observer
Time status observer
Buffer status appears
Buffer status disappers
Source identification observer stop ap- pears
Source identification observer stop disap- pears
Basis Library (V9.0 SP3)
90
Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.14 IM_TS_PN: Status alarms with time stamps
I/O (parameter) TS_TmStatOb- Stop_APP_IN TS_TmStatOb- Stop_DAPP_IN TS_BufStatOb- Stop_APP_IN TS_BufStatOb- Stop_DAPP_IN TS_SRLObStop_APP_IN TS_SRLObStop_DAPP_IN TS_DIObStop_APP_IN
TS_DIObStop_DAPP_IN
TS_SRL_APP_IN TS_SRL_DAPP_IN TS_DIN_IN_xxx
Meaning
Data type
Time status observer stop appears
Time status observer stop disappears
Buffer status observer stop appears
Buffer status observer stop disappears
SRL observer stop appears
SRL observer stop disappears
Observer digital input observer stop ap- pears
Observer digital input observer stop disap- pears
System redundancy layer appears
System redundancy layer disappears
Digital input observer (xxx=0..511)
Default
Output parameter
I/O (parameter) DIAG_INF DIAG_INF_SRAL TS_DIN_xxx (xxx=0..511)
Meaning
Module diagnosis Diagnostic Information Structure Time stamp in DT format
TS_SI TS_TmStat_NoSync TS_TmStat_Jitter TS_BufStat_APP TS_BufStat_DAPP TS_SIObStop_APP TS_SIObStop_DAPP TS_TmStatObStop_APP
Time stamp in DT format Time stamp in DT format Time stamp in DT format Time stamp in DT format Time stamp in DT format
Data type
Default
STRUCT
STRUCT
STRUCT
Year:INT:=0; Month:INT:=0; Day:INT:=0; Hour:INT:=0; Mi- nute:INT:=0; Sec- ond:INT:=0; Milli- Second:INT:=0; MicroSec- ond:INT:=0; NanoSec- ond:INT:=0; Msg:BOOL:=0;
END_STRUCT
STRUCT
STRUCT
STRUCT
STRUCT
STRUCT
STRUCT
STRUCT
STRUCT
Basis Library (V9.0 SP3)
Function Manual, 06/2019, A5E40797470-AD
91
Family: @System 6.14 IM_TS_PN: Status alarms with time stamps
I/O (parameter) TS_TmStatObStop_DAPP TS_BufStatObStop_APP TS_BufStatObStop_DAPP TS_SRLObStop_APP TS_SRLObStop_DAPP TS_DIObStop_APP TS_DIObStop_DAPP TS_SRL_APP TS_SRL_DAPP QERR QPARF QBPARF QPERAF QRACKF QTS_NCON TS_xxx
TS_OSO_DI_DT_xxx
TS_C_xxx
Meaning
Time stamp in DT format Time stamp in DT format Time stamp in DT format Time stamp in DT format
1 = Processing Error block 1 = Parameterization error module 1 = Parameterization error block 1 = Peripheral access error 1 = Module carrier error 1 = TS_xxx is not interconnected Timestamp (xxx = 000 - 511) Bit 0: Signal condition (MsgSig) Bit 1: Information flank change (TriInf) Bit 2: Handshake (HdSh) Byte 1: Timestamp's quality code (ST) DWORD TS0: Date/ Timestamp in ISP for- mat (seconds) DWORD TS1: Date/ Timestamp in ISP for- mat (split seconds/ second fragments) Observer status observer digital input (xxx = 000..511) TS communication (xxx = 000 - 511) Bit 0: Transaction acknowledgment (HS) Bit 1: Interconnection check (LI)
Data type
Default
STRUCT
STRUCT
STRUCT
STRUCT
STRUCT
STRUCT
STRUCT
STRUCT
STRUCT
BOOL
1
BOOL
0
BOOL
0
BOOL
0
BOOL
0
BOOL
0
STRUCT DigValTS2
STRUCT
BYTE
0
In/out parameters
I/O (parameter) ACC_MODE ACK_E061 CPU_DIAG_PN OB_55_PN
RAC_DIAG
Meaning
Data type
1 = Save settings
BOOL
1 = Acknowledge the messages BOOL
System structure: CPU Diagnosis STRUCT
System structure: status alarm STRUCT diagnosis
Status information rack
STRUCT
Default
0 0
Basis Library (V9.0 SP3)
92
Function Manual, 06/2019, A5E40797470-AD
I/O (parameter)
RACK_TS_XCHG
Family: @System 6.14 IM_TS_PN: Status alarms with time stamps
Meaning
SoE Message Exchange with higher order block
Data type
Default
STRUCT
PERAF: BOOL; // 1=Module I/O Access Failure
PARF: BOOL; // 1=Parameter Assignment Error Module
RET: WORD;
BUFOV : BOOL; //Buffer over- flow
DIOF: BOOL; //Digital input ob- server failure
BSOF : BOOL; //Buffer status observer failure
TSOF: BOOL; //Time status ob- server failure
SRLOF: BOOL; //System redun- dancy layer observer failure
SIOF: BOOL; //Source identifi- cation observer failure
BPARF: BOOL; // 1=Parameter Assignment Error Block
TS_NCON : BOOL; // 1=TS_xxx is not connected
SICH : BOOL; // Source identifi- cation channel TMSTAT : BOOL; // Time status
SRLS : BOOL; // Redundancy status
MSG_BUSY : BOOL; // reserve
RESV1 : BOOL; // reserve
RESV2 :BOOL; // reserve
SUBNET: BYTE;
RACK: BYTE;
SLOT: BYTE;
CHANNEL: BYTE;
SaS_TS_00: ARRAY [0..65] OF BYTE; //Timestamp ALARM_T-Call 0, 1 Format, 2..65 8*TS
SaS_TS_01: ARRAY [0..65] OF BYTE; //Timestamp ALARM_T-Call 0,1 Format, 2..65 8*TS
END_STRUCT;
Basis Library (V9.0 SP3)
Function Manual, 06/2019, A5E40797470-AD
93
Family: @System 6.15 IMDRV_TS: Transferring time-stamped process-signal changes
I/O (parameter)
TIME_STATUS
Meaning
SaS_TS_00
Time stamp
SaS_TS_01
Time stamp
Data type
STRUCT CPU_NO_SYNC:BOOL; CPU_JITTER_MSG:BOOL; TmStat_R1:BOOL;
... TmStat_R256:BOOL; TmStat_Lim:BOOL; END_STRUCT STRUCT BYTE0: BYTE;
.... BYTE65: BYTE; END_STRUCT STRUCT BYTE0: BYTE; .... BYTE65: BYTE; END_STRUCT
Default
6.15
IMDRV_TS: Transferring time-stamped process-signal changes
6.15.1
Description of IMDRV_TS
Object name (type + number) FB 129 · IMDRV_TS Block I/Os (Page 98)
Area of application
The IMDRV_TS block transfers time-stamped process signal changes to the MSG_TS blocks, and messages from the interface module (IM) to the OS.
Calling OBs
The block must be installed in the run sequence in the following OBs:
OB 1 OB 40 OB 100
Cyclic program Hardware interrupt Warm restart
Basis Library (V9.0 SP3)
94
Function Manual, 06/2019, A5E40797470-AD
Use in CFC
Family: @System
6.15 IMDRV_TS: Transferring time-stamped process-signal changes
The following actions are executed automatically with the "Generate module drivers" CFC function:
· The IMDRV_TS block is copied from the library and instantiated in a system chart. The block is installed in its runtime group after the RACK block runtime group in the above-mentioned OBs.
· OR_32_TS is always interconnected between MSG_TS and IMDRV_TS.
· The logical address LADDR is configured with the logical address of the IM (diagnostics address). If you operate the DP master system in DPV1 mode, the input address of the IM is entered.
· The RAC_DIAG structure of the RACK block is interconnected with the structure of the same name of the IMDRV_TS block.
· The S_CH_xxx and TINF_xxx inputs of the TRIG_INF structure are set. Every signal that is time-stamped by the IM has a unique assignment identified by the slot of the module combined with the corresponding channel number. There are 128 inputs of the WORD data type for 128 signals. The slot number of the relevant digital input module is entered in the more significant byte and the channel number (signal of the digital input module) is entered into the less significant byte. The slot and channel number of the process signals are entered in the block inputs S_CH_xxx. Example: In HW Config, you have activated time-stamping for the digital signal of channel 10 of a digital input module that is inserted in slot 5 of an ET 200M. The number 16#050A is entered at the first available input S_CH_xxx of the IM_DRV_TS. The information about the edge evaluation for the event entering state is stored in the TINF_xxx parameters of the TRIG_INF structure. 0 means: 0 -> 1 is event entering state 1 means: 1 -> 0 is event entering state.
Description of the functions
The IMDRV_TS block reads the messages from the message buffers (up to 15 data records, each with 20 messages) of an IM, and transfers them to a message block for time stamps (MSG_TS). The MSG_TS sends the messages via an ALARM_8P block whose time stamps for its 8 messages are entered in the 1st associated value in an ARRAY of BYTE.
Basis Library (V9.0 SP3)
Function Manual, 06/2019, A5E40797470-AD
95
Family: @System 6.15 IMDRV_TS: Transferring time-stamped process-signal changes
How it works
· Hardware interrupt (OB 40): The IM generates a hardware interrupt if there are new messages. The time-stamp status, including the number of the IM data record to be fetched and the number of messages in the data record, are fetched from the start information of the process interrupt OB and stored for cyclic processing. The interrupt stack can hold up to 17 process interrupts. If this maximum is exceeded, all new information will be lost. The loss of information is indicated by the "Loss of message at IM (buffer overflow)" message.
· Cyclic processing: If any messages are queued in the stack, SFB 52 (RDREC, read data record) reads the relevant data record (message buffer). If there are several data records to be fetched, it will fetch the record that contains the oldest messages (oldest hardware interrupt). The block instance temporarily stores a maximum of 20 messages of a data record. The IM can enter new messages in a data record once it has been read. If all data records are in use, the IM enters "Loss of message at IM (buffer overflow)" (incoming) as the last message in the message buffer. "Loss of message at IM (buffer overflow)" (outgoing) is then entered as the first message in the first free data record. Messages received within the interval between a buffer overflow and the enabling of a record will be lost. The slot number/channel number of the stored messages are compared with the input parameters of the block for slot number/channel number (S_CH_xxx). If they match, the message is written to the corresponding output (TS_xxx). Errors occurring during data exchange between the block and IM are reported by the ALARM_8P block (for example, an I/O access error).
Quality code for the time stamp TS_xxx.TS0/TS1 A quality code QC_TS is formed for the time stamp TS0/TS1, and entered in TS_xxx.
State
Valid value Invalid value (higher level error) · Time-of-day frame failure · Stop the time stamp function · Message loss on IM (buffer overflow) · Loss of information with redundancy Invalid value
Quality code TS_xxx.QC_TS 16#80 16#40
16##00
Addressing
For general information, see also Addressing (Page 530)
The logical address of the IM obtained in HW Config (corresponds to the diagnostic address, or the input address of the IM for a DP master system in DPV1 mode) is entered at the driver's block input (LADDR) by the "Generate module driver" CFC function. Any change to the LADDR block input will initiate a single check of the logical address according to the startup characteristics of the block.
Process signals that require a time stamp and are detected via an IM must be configured accordingly in HW Config.
Basis Library (V9.0 SP3)
96
Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.15 IMDRV_TS: Transferring time-stamped process-signal changes
Error handling I/O access error:
QPERAF The block could not access the IM. A data record could not be read. Block processing error:
QERR
A block execution error has occurred.
Module parameter assignment error:
QPARF Faulty block configuration: Incorrect logical basic address entered. Parameter assignment error:
QBPARF Faulty block configuration: The slot/channel number of an IM message does not match any slot/channel number of the block input parameters.
Rack error:
QRACKF Failure of the rack containing the IM or IM failure.
IM Startup Characteristics
During startup/restart of the IM, the system will generate process interrupts once again for those records which were occupied prior to restart but had not been fetched.
The message "Startup data (incoming)" is entered as the first message of the first free data record. After restart, the system checks all monitored digital signals for changes, outputs a message if appropriate. It finally generates the message "Startup data (outgoing)".
IMDRV_TS driver block startup characteristics
Initializes the ALARM_8P blocks using the data stored prior to the CPU transition to STOP. During an initial startup, the signal state is set to "Zero".
During startup, the block verifies the existence of an IM at its logical address set in LADDR. If this does not exist, it sets the QPARF output to TRUE, and does not access any I/Os in its subsequent cycles. QPARF = FALSE and I/O access is enabled only after the correct module has been inserted, or the logical address has been set correctly. Stored process interrupt data which were not computed before the restart will be deleted.
Redundancy
Time stamping in H systems equipped with two IM units is redundant under the following conditions:
· Both IM units communicate via the communication (K) bus.
· No error has occurred during the update of the active and passive IM.
The SUBNET and RACK blocks report loss of redundancy (failure of an IM), separately from the IMDRV_TS block.
Basis Library (V9.0 SP3)
Function Manual, 06/2019, A5E40797470-AD
97
Family: @System 6.15 IMDRV_TS: Transferring time-stamped process-signal changes
Time stamping is interrupted for the duration of the changeover between the active and passive IM. This period of interruption is indicated by the message "Redundant changeover" (incoming/ outgoing state). The active IM usually reports the current I/O status to the redundant IM. If this communication is disrupted, the message "Loss of information with redundancy" (entering state) is output. When the I/O statuses of the active and redundant IM are synchronized, the message "Loss of information with redundancy" (outgoing) is output.
Time response Not available
Message response The block signals system messages from the IM via the ALARM_8P block. The time-stamped hardware interrupts are forwarded to the MSG_TS IM message block via OR_32_TS.
Operator control and monitoring: The block does not have a faceplate.
Additional information You will find more information in: Message texts of IMDRV_TS (Page 100)
6.15.2
I/Os of IMDRV_TS
The factory setting of the block display in the CFC is identified in the "I/O" column:
I/O name bold = I/O visible, I/O name normal = I/O not visible.
You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15)".
Input parameters
I/O (parameter)
DIAG_BUF EV_ID EV_ID_00 LADDR S_CH_xxx TRIG_INF
Meaning
Entry in diagnostic buffer (relevant for maintenance personnel) Message number for ALARM_8P Message number 0 for ALARM_8P Logic address IM Slot/channel number (xxx = 000 - 127) Edge evaluation: 0 = trigger 0 -> 1, 1 = trigger 1 -> 0
Data type
BOOL DWORD DWORD INT WORD STRUCT
Default
0 0 0 0 0
Basis Library (V9.0 SP3)
98
Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.15 IMDRV_TS: Transferring time-stamped process-signal changes
Output parameters
I/O (parameter) M_ACK_00 Q_ERR_00 QERR QPARF QBPARF QPERAF QRACKF QTS_NCON STAT_00 TS_xxx
TS_C_xxx
Meaning
Message acknowledgment Message error 1 = processing error block 1 = parameter assignment error module 1 = parameter assignment error block 1 = I/O access error 1 = higher-level error 1 = TS_xxx is not interconnected Status output Time stamp (xxx = 000 127) Bit 0: Message signal state (MsgSig) Bit 1: Edge change information (TriInf) Bit 2: Handshake (HdSh) Byte 1: Quality code of the time stamp (ST) DWORD TS0: Date/time stamp in ISP format (seconds) DWORD TS1: Date/time stamp in ISP format (fractions of seconds) TS communication (xxx = 000 - 127) Bit 0: Acknowledgment of transfer (HS) Bit 1: Interconnection check (LI)
Data type
WORD BOOL BOOL BOOL BOOL BOOL BOOL BOOL WORD STRUCT
Default
0 0 1 0 0 0 0 0 0
BYTE
0
In/out parameters
I/O (parameter)
RAC_DIAG
Meaning Rack status information
Data type STRUCT
Default
Additional information For additional information, refer to the sections: Message texts of IMDRV_TS (Page 100)
Basis Library (V9.0 SP3)
Function Manual, 06/2019, A5E40797470-AD
99
Family: @System 6.15 IMDRV_TS: Transferring time-stamped process-signal changes
6.15.3
Message texts of IMDRV_TS
Assignment of message text and message class You will find more information in Message classes (Page 531)
Message block EV_ID (ALARM_8P)
EV_ID_00 (ALARM_T)
Message no. Default message text
Message class
1
IM @1%d@@2%d@: Parameter assign- PLC Process Control Message -
ment error
Failure
Slot=@3%d@ Channel=@4%d@
2
IM @1%d@@2%d@: I/O access error: PLC Process Control Message -
Ret_Val@5%d@
Failure
3
IM @1%d@@2%d@: Parameter assign- PLC Process Control Message -
ment error LADDR
Failure
4
IM @1%d@@2%d@: Output TS_xxx of PLC Process Control Message -
S_CHxx:
Failure
Slot=@3%d@ Channel=@4%d@ is not
interconnected
5
Reserve5
No message
6
Reserve6
No message
7
Reserve7
No message
8
Reserve8
No message
1
IM @3%d@@4%d@: Startup data
PLC Process Control Message -
Failure
2
IM @3%d@@4%d@: Time-of-day frame PLC Process Control Message -
failure
Failure
3
No message
4
IM @3%d@@4%d@: Time difference be- PLC Process Control Message -
tween the frame and the internal clock Failure
may cause inaccuracy
5
IM @3%d@@4%d@: Stop the time
PLC Process Control Message -
stamp function
Failure
6
IM @3%d@@4%d@: Message loss on IM PLC Process Control Message -
(buffer overflow)
Failure
7
IM @3%d@@4%d@: Redundant change- PLC Process Control Message -
over
Failure
8
IM @3%d@@4%d@: Loss of information PLC Process Control Message -
with redundancy
Failure
Note
The message "IM @1%d@@2%d@: Output TS_xxx of S_CHxx: Slot=@3%d@ Channel=@4%d@ is not interconnected" is generated when the time stamp of a signal could not be forwarded. The reason for this could be configured but not interconnected time stamp signals (e.g. missing channel block PCS7DiIT and missing message block EventTs).
100
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
6.16
Family: @System 6.16 MHA_CO: Multi HART variable read coordination (0 - 15 Channel)
MHA_CO: Multi HART variable read coordination (0 - 15 Channel)
6.16.1
Description of MHA_CO
Object name (type + number) FB 426 · I/Os of MHA_CO (Page 101)
Area of application
The MHA_CO block coordinates the reading of the MultiHART variables for ET 200SP HA HART modules.
Configuration
The following actions are executed automatically with the "Generate module drivers" CFC function:
· The MHA_CO block is installed in OB 1.
· MODE1_xx inputs are interconnected with the OMODE_xx outputs of the MOD_x block.
· The OUT structure CPU_DIAG_PN of the OB_BEGIN_PN block is interconnected with the IN_OUT structures of the same name of the MHA_CO block.
· The MULTI_HART_xx outputs are interconnected with the inputs of the Pcs7HaAI/Pcs7HaAO blocks.
Error handling The plausibility of input parameters is not checked.
Block functions
The MHA_CO block reads the values of the HART auxiliary variables for which the HVPriEn / HV_SecEN / HV_TerEn / HV_QuaEn is selected at the Pcs7HaAI / Pcs7HaAO blocks.
Messaging
Not available
6.16.2
I/Os of MHA_CO
The factory setting of the block display in the CFC is identified in the "I/O" column: I/O name bold = I/O visible, I/O name normal = I/O not visible.
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
101
Family: @System 6.16 MHA_CO: Multi HART variable read coordination (0 - 15 Channel)
You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15)".
Input parameters
I/O (parameter)
CHAN_NUM MUL_HART HV1ADDR HV1ADDR_CMD HV2ADDR HV2ADDR_CMD HV3ADDR HV3ADDR_CMD HV4ADDR HV4ADDR_CMD RACKF MODF FEATURE MODE_xx
Meaning
Total number of channels -1 1 = 1 Multi HART, 4 = 4 Multi HART HART variable 1 address HART variable 1 command address HART variable 2 address HART variable 2 command address HART variable 3 address HART variable 3 command address HART variable 4 cddress HART variable 4 command address 1= Higher level error 1 = Module 1 removed / Out of Order Reserve Channel mode xx (xx = 00 - 15)
Data type
INT INT INT INT INT INT INT INT INT INT BOOL BOOL DWORD DWORD
Default
0 0 0 0 0 0 0 0 0 0 0 0 0 0
Output parameters
I/O (parameter)
MULTI_HART_xx
Meaning
Bidirectional information exchange channel (xx = 00 15)
Data type
STRUCT
Default 0
In/out parameters
I/O (parameter) ACC_MODE CPU_DIAG_PN
Meaning
1 = Accept new settings System structure: CPU-Diagnose
Data type
BOOL
STRUCT
Default 0
102
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.17 MOD_1: Monitoring up to 16 channels on S7-300/400 SM modules without diagnostic capability
6.17
MOD_1: Monitoring up to 16 channels on S7-300/400 SM modules without diagnostic capability
6.17.1
Description of MOD_1
Object name (type + number) FB 91 · I/Os of MOD_1/MOD_2 (Page 106)
Area of application
The MOD_1 block monitors up to 16 channels on S7-300/400 SM modules without diagnostic capability (no mixed modules). H systems support only the modules installed in switched racks.
Calling OBs
The block must be installed in the run sequence in the following OBs:
OB 1 OB 83 OB 85 OB 86 OB 100
Cyclic program Insert/remove module interrupt Program execution error Rack failure Warm restart
Use in CFC
The following actions are executed automatically with the "Generate module drivers" CFC function:
· The MOD_1 block is installed in its runtime group downstream of the RACK block runtime group in the above-mentioned OBs.
· The MODE_xx inputs (mode of module channels xx) are configured.
· The logical base address of the LADDR module is configured.
· The OUT structures CPU_DIAG of the OB_BEGIN block and RAC_DIAG of the RACK block are interconnected with the IN_OUT structures of the same name of MOD_1.
· The EN input is interconnected with the output of an AND block. Its inputs are interconnected with the outputs EN_SUBx (x = number of the DP master system) of the OB_BEGIN block, EN_Rxxx (xxx = rack/station number) of the SUBNET block and EN_Mxx (xx = module number) of the RACK block.
· The output parameter of DXCHG_xx is interconnected with the following channel block at the DataXchg parameter.
· The output parameter of O_MS is interconnected with the following channel block at the MS parameter.
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
103
Family: @System 6.17 MOD_1: Monitoring up to 16 channels on S7-300/400 SM modules without diagnostic capability
Function
The MOD_1 block analyzes all events that affect a module and its channels acyclically. It generates a channel-specific MODE (Page 517) and value status for the signal processing blocks. ALARM_8P reports the events.
The block is enabled by the higher-level RACK block at runtime. The event to be evaluated can be found in the CPU_DIAG start information of the OB_DIAG block. There is a MODE_xx input for each signal channel of the module. The module channel configuration data created in HW Config is reported here. The function writes MODE_xx to the low word of the OMODE_xx (Page 527) output parameter. This occurs only during startup or if you set ACC_MODE = TRUE. The current channel value status is written to the most significant byte. If the result is positive, the system sets OMODE_xx = 16#80xxxxxx.
The following events lead to the value status "invalid value due to higher-level error" (OMODE_xx = 16#40xxxxxx):
· Events that are evaluated by the RACK block:
Rack failure (OB 86) (output parameter QRACKF = TRUE)
· Events that are evaluated by the MOD block:
Program execution error (OB 85) (output parameter QPERAF = TRUE)
Module removed (OB 83) (output parameter QMODF = TRUE)
"Module removed" and "I/O access error" events are reported to the OS by ALARM_8P. The diagnostics interrupt function distinguishes between module and channel errors, whereby each channel is assigned a message ID.
The system verifies during startup that the module is available (plugged in). The module status information that is read here is then available in the form of service output parameters (MOD_INF).
You will find additional information about faults in the System Software for S7-300/400 System and Standard Functions reference manual.
Redundancy
The higher-level RACK block monitors the redundancy of DP master systems operating in an H system.
MODE setting You will find additional information about this in the "MODE settings (Page 517)" section.
Note If you make changes to the MODE_xx input configurations at runtime, they are not accepted at the outputs until you set the ACC_MODE input to 1.
104
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.17 MOD_1: Monitoring up to 16 channels on S7-300/400 SM modules without diagnostic capability
OMODE Structure You will find additional information in the "OMODE (Page 527)" section.
Valid channel display
The available channels on a module are displayed in the CH_EXIST output by setting a bit in the DWORD, starting at bit 0, for every existing channel. If the bit assigned to a channel = 0, the channel is not available.
Output CH_OK displays the valid channels on a module by setting a bit to TRUE for every valid channel, where bit 0 is assigned to channel 0, etc. If the bit assigned to a channel is 0, the channel is faulty. If a module error occurs, all channels are disrupted.
Addressing
You will find additional information about this in the "Addressing (Page 530)" section.
Error handling
The plausibility of input parameters is not checked.
You will find additional information about error handling in the "Error information of output parameter MSG_STAT (Page 530)" section.
Service Information
To analyze faults, the module status information entered during startup is read via the MOD_INF structured output parameter. You will find additional information in the System Software for S7-300/400 System and Standard Functions; System Status List, Module Status Information reference manual.
Startup characteristics
After a restart/initial startup, the system verifies that the module is available under its logical base address. A restart (OB 100) is reported via the LSB in byte 2 of the OMODE_xx (Page 527) outputs.
Time response Not available
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
105
Family: @System 6.17 MOD_1: Monitoring up to 16 channels on S7-300/400 SM modules without diagnostic capability
Message response MOD_1 uses ALARM_8P to report module errors. The inputs DELAY1 and DELAY2 are used to delay the output of I/O access error messages. DELAY1 allows you to enter a time in seconds for which the block will wait for a higher-priority error (rack failure or removal/insertion) following a program execution error (OB 85) before it outputs the message. The message is output only under the condition that no higher-priority error is reported within this delay time. DELAY2 determines the number of seconds the block waits after the higher-priority error has been reported outgoing until it outputs the queued I/O access error as well. Both values are set to 2 seconds by default. The message function can be disabled by setting EN_MSG = FALSE.
Operator control and monitoring If asset management is used in the project and the diagnostic screens have been generated, the faceplate can be called via its block icon. For additional information, refer to the "Process Control System PCS 7; Maintenance Station" manual.
Additional information For additional information, refer to the sections: Message texts and associated values of MOD_1 (Page 108) Maintenance status MS (Page 533) You can also find additional information on this in PCS 7 Advanced Process Library > Basics of APL > General functions of the blocks > Operating, monitoring and reporting > Release for maintenance
6.17.2
I/Os of MOD_1/MOD_2
The MOD_1 and MOD_2 block I/Os are identical with the exception of the number of MODE_xx and OMODE_xx. The number of monitored channels determines the corresponding number of I/O parameters (xx).
The factory setting of the block display in the CFC is identified in the "I/O" column:
I/O name bold = I/O visible, I/O name normal = I/O not visible.
You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15)".
Input parameters
I/O (parameter) CHAN_NUM DELAY1 DELAY2
Meaning
Total number of channels -1 Alarm delay 1 (s) Alarm delay 2 (s)
Data type Default
INT
0
INT
2
INT
2
106
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.17 MOD_1: Monitoring up to 16 channels on S7-300/400 SM modules without diagnostic capability
I/O (parameter) DIAG_BUF
EN_MSG EV_ID LADDR MODE_xx MS MS_REQ RACK_NO SLOT_NO SUBN_TYP SUBN1_ID SUBN2_ID
Meaning
Data type Default
Entry in diagnostic buffer (relevant for maintenance BOOL
0
personnel)
1 = Enable message
BOOL
1
Message number
DWORD
0
Logical address of the module
INT
0
Channel mode (xx = 00 - 15/00 - 31)
DWORD
0
Maintenance status
DWORD
0
1 = Request maintenance release
BOOL
0
Rack number
BYTE
0
Slot number
BYTE
0
1 = external DP interface
BOOL
0
ID of the primary DP master system
BYTE
255
ID of the redundant DP master system
BYTE
255
Output parameters
I/O (parameter) CH_ACTIVE CH_EXIST CH_OK DXCHG_xx
DXCHG1_xx
EXT_STAT EXT_STAT_A
MOD_INF MS_XCHG_xx
MSG_ACK MSG_STAT O_MS OMODE_xx QERR QMODF QPERAF QRACKF
Meaning
Channel active Channel exists Channel OK 1st internal data exchange channel for channel block 2nd internal data exchange channel for channel block Release for maintenance - extended status Extended status - Application Application data transfer active System structure: Module parameter Maintenance Status - Data exchange channel (xx = 00 - 63) Message acknowledgment Message error information Maintenance status Channel mode (xx = 00 - 15/00 - 31) 1 = program error 1 = module removed/defective 1 = I/O access error 1 = higher-level error
Data type DWORD DWORD DWORD DWORD
DWORD
DWORD DWORD
STRUCT DWORD
WORD WORD DWORD DWORD BOOL BOOL BOOL BOOL
Default
16#00000000 0 0 0
0
0 0
0
0 0 0 0 1 0 0 0
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
107
Family: @System 6.17 MOD_1: Monitoring up to 16 channels on S7-300/400 SM modules without diagnostic capability
In/out parameters
I/O (parameter) ACC_MODE CPU_DIAG RAC_DIAG
Meaning
1 = accept MODE settings System structure: CPU diagnostics System structure: Rack diagnostics
Data type
BOOL STRUCT STRUCT
Default 0
Additional information For additional information, refer to the sections: Message texts and associated values of MOD_1/MOD_2/MOD_3/MOD_64 (Page 108) Maintenance status MS (Page 533)
6.17.3
Message texts and associated values of MOD_1/MOD_2/MOD_3/MOD_64
Assignment of message text and message class to the block parameters of MOD_1/MOD_2/MOD_3/ MOD_64
Message block ALARM_8P
EV_ID
Message number
1
2 3
4 5 6 7
8
Default message text
Message class
Module @1%d@/@2%d@/@3%d@: Failure
PLC Process Control Message Failure
No message
No message
Module @1%d@/@2%d@/@3%d@: @4W PLC Process Control Message %t#MOD_n_TXT@ (n = 1, 2, 3 or 64) Failure
No message
No message
No message
Module @1%d@/@2%d@/@3%d@: Maintenance demanded (external)
PLC Process Control Message Error
Module @1%d@/@2%d@/@3%d@: Maintenance required (external)
Preventative Maintenance Standard
Assignment of associated values to the block parameters of MOD_1/MOD_2/MOD_3
Message block ALARM_8P
EV_ID
Associ- ated value
1
2
Block parameters
MOD_INF.SUBN_ID MOD_INF.RACK_NO
Meaning
DP master system ID (byte) Rack/station number (byte)
108
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
See also
Family: @System 6.18 MOD_2: Monitoring 32 channels on S7-300/400 SM modules without diagnostic capability
Message block ALARM_8P
Associ- ated value
3
4
Block parameters MOD_INF.SLOT_NO
Meaning
Slot number (byte) Text number from MOD_n_TXT (n = 1, 2, 3 or 64) (Message 1)
You will find the message texts and their text numbers in the "Text library for MOD_1, MOD_2, MOD_3, MOD_64 (Page 537)" section.
Message Classes (Page 531)
6.18
MOD_2: Monitoring 32 channels on S7-300/400 SM modules without diagnostic capability
6.18.1
Description of MOD_2
Object name (type + number) FB 92 · MOD_2 block I/Os (Page 113)
Area of application
The MOD_2 block monitors 32 channels on S7-300/400 SM modules without diagnostic capability (no mixed modules). H systems support only the modules installed in switched racks.
Calling OBs
The block must be installed in the run sequence in the following OBs:
OB 1 OB 83 OB 85 OB 86 OB 100
Cyclic program Insert/remove module interrupt Program execution error Rack failure Warm restart
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
109
Family: @System 6.18 MOD_2: Monitoring 32 channels on S7-300/400 SM modules without diagnostic capability
Use in CFC
The following actions are executed automatically with the "Generate module drivers" CFC function:
· The MOD_2 block is installed in its runtime group downstream of the RACK block runtime group in the above-mentioned OBs.
· The MODE_xx inputs (mode of module channels xx) are configured.
· The logical base address of the LADDR module is configured.
· The OUT structures CPU_DIAG of the OB_BEGIN block and RAC_DIAG of the RACK block are interconnected with the IN_OUT structures of the same name of MOD_2.
· The EN input is interconnected with the output of an AND block. Its inputs are interconnected with the outputs EN_SUBx (x = number of the DP master system) of the OB_BEGIN block, EN_Rxxx (xxx = rack/station number) of the SUBNET block and EN_Mxx (xx = module number) of the RACK block.
· The output parameter of DXCHG_xx is interconnected with the following channel block at the DataXchg parameter.
· The output parameter of O_MS is interconnected with the following channel block at the MS parameter.
Function
Block MOD_2 analyzes all events affecting a module and its channels in non-cyclic mode. It generates a channel-specific MODE (Page 517) and value status for the signal processing blocks. ALARM_8P reports the events.
The block is enabled to run by the higher-level RACK block. The event to be evaluated can be found in the CPU_DIAG start information of the OB_DIAG block. There is a MODE_xx input for each signal channel of the module. The module channel configuration data created in HW Config is reported here. The function writes MODE_xx to the low word of the OMODE_xx (Page 527) output parameter. This occurs only during startup or if you set ACC_MODE = TRUE. The current channel value status is written to the most significant byte. If the result is positive, the system sets OMODE_xx = 16#80xxxxxx.
The following events lead to the value status "invalid value due to higher-level error" (OMODE_xx = 16#40xxxxxx):
· Events that are evaluated by the RACK block:
Rack failure (OB 86) (output parameter QRACKF = TRUE)
· Events that are evaluated by the MOD block:
Program execution error (OB 85) (output parameter QPERAF = TRUE)
Module removed (OB 83) (output parameter QMODF = TRUE)
"Module removed" and "I/O access error" events are reported to the OS by ALARM_8P. The diagnostics interrupt function distinguishes between module and channel errors, whereby each channel is assigned a message ID.
110
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.18 MOD_2: Monitoring 32 channels on S7-300/400 SM modules without diagnostic capability
The system verifies during startup that the module is available (plugged in). The module status information that is read here is then available in the form of service output parameters (MOD_INF). You will find additional information about errors in the System Software for S7-300/400; System and Standard Functions reference manual.
Redundancy
The higher-level RACK block monitors the redundancy of DP master systems operating in an H system.
MODE setting You will find additional information about this in the "MODE settings (Page 517)" section.
Note If you change the parameter settings for the MODE_xx inputs at runtime, these changes will not be accepted at the outputs until the ACC_MODE is set to 1.
OMODE Structure You will find additional information in the "OMODE (Page 527)" section.
Valid channel display
The available channels on a module are displayed in the CH_EXIST output by setting a bit in the DWORD, starting at bit 0, for every existing channel. If the bit assigned to a channel = 0, the channel is not available.
Output CH_OK displays the valid channels on a module by setting a bit to TRUE for every valid channel, where bit 0 is assigned to channel 0, etc. If the bit assigned to a channel is 0, the channel is faulty. If a module error occurs, all channels are disrupted.
Addressing
You will find additional information about this in the "Addressing (Page 530)" section.
Error handling
The plausibility of input parameters is not checked.
You will find additional information about error handling in the "Error information of output parameter MSG_STAT (Page 530)" section.
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
111
Family: @System 6.18 MOD_2: Monitoring 32 channels on S7-300/400 SM modules without diagnostic capability
Service Information To analyze faults, the module status information entered during startup is read via the MOD_INF structured output parameter. You will find additional information about this in the reference manual System Software for S7-300/400 System and Standard Functions; System Status List, Module Status Information.
Startup characteristics After a restart/initial startup, the system verifies that the module is available under its logical base address. A restart (OB 100) is reported via the LSB in byte 2 of the OMODE_xx (Page 527) outputs.
Time response Not available
Message response MOD_2 uses ALARM_8P to report module errors. The inputs DELAY1 and DELAY2 are used to delay the output of I/O access error messages. DELAY1 allows you to enter a time in seconds for which the block will wait for a higher-priority error (rack failure or removal/insertion) following a program execution error (OB 85) before it outputs the message. The message is output only under the condition that no higher-priority error is reported within this delay time. DELAY2 determines the number of seconds the block waits after the higher-priority error has been reported outgoing until it outputs the queued I/O access error as well. Both values are set to 2 seconds by default. The message function can be disabled by setting EN_MSG = FALSE.
Operator control and monitoring If asset management is used in the project and the diagnostic screens have been generated, the faceplate can be called via its block icon. For additional information, refer to the "Process Control System PCS 7; Maintenance Station" manual.
Additional information For additional information, refer to the sections: Message texts and associated values of MOD_2 (Page 114) Maintenance status MS (Page 533) You can also find additional information on this in PCS 7 Advanced Process Library > Basics of APL > General functions of the blocks > Operating, monitoring and reporting > Release for maintenance
112
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
6.18.2
Family: @System 6.18 MOD_2: Monitoring 32 channels on S7-300/400 SM modules without diagnostic capability
I/Os of MOD_1/MOD_2
The MOD_1 and MOD_2 block I/Os are identical with the exception of the number of MODE_xx and OMODE_xx. The number of monitored channels determines the corresponding number of I/O parameters (xx). The factory setting of the block display in the CFC is identified in the "I/O" column: I/O name bold = I/O visible, I/O name normal = I/O not visible. You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15)".
Input parameters
I/O (parameter) CHAN_NUM DELAY1 DELAY2 DIAG_BUF
EN_MSG EV_ID LADDR MODE_xx MS MS_REQ RACK_NO SLOT_NO SUBN_TYP SUBN1_ID SUBN2_ID
Meaning
Data type Default
Total number of channels -1
INT
0
Alarm delay 1 (s)
INT
2
Alarm delay 2 (s)
INT
2
Entry in diagnostic buffer (relevant for maintenance BOOL
0
personnel)
1 = Enable message
BOOL
1
Message number
DWORD
0
Logical address of the module
INT
0
Channel mode (xx = 00 - 15/00 - 31)
DWORD
0
Maintenance status
DWORD
0
1 = Request maintenance release
BOOL
0
Rack number
BYTE
0
Slot number
BYTE
0
1 = external DP interface
BOOL
0
ID of the primary DP master system
BYTE
255
ID of the redundant DP master system
BYTE
255
Output parameters
I/O (parameter) CH_ACTIVE CH_EXIST CH_OK DXCHG_xx
DXCHG1_xx
EXT_STAT EXT_STAT_A
Meaning
Channel active Channel exists Channel OK 1st internal data exchange channel for channel block 2nd internal data exchange channel for channel block Release for maintenance - extended status Extended status - Application Application data transfer active
Data type DWORD DWORD DWORD DWORD
DWORD
DWORD DWORD
Default
16#00000000 0 0 0
0
0 0
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
113
Family: @System 6.18 MOD_2: Monitoring 32 channels on S7-300/400 SM modules without diagnostic capability
I/O (parameter) MOD_INF MS_XCHG_xx
MSG_ACK MSG_STAT O_MS OMODE_xx QERR QMODF QPERAF QRACKF
Meaning
System structure: Module parameter Maintenance Status - Data exchange channel (xx = 00 - 63) Message acknowledgment Message error information Maintenance status Channel mode (xx = 00 - 15/00 - 31) 1 = program error 1 = module removed/defective 1 = I/O access error 1 = higher-level error
Data type
STRUCT
DWORD
Default 0
WORD 0
WORD 0
DWORD 0
DWORD 0
BOOL
1
BOOL
0
BOOL
0
BOOL
0
In/out parameters
I/O (parameter) ACC_MODE CPU_DIAG RAC_DIAG
Meaning
1 = accept MODE settings System structure: CPU diagnostics System structure: Rack diagnostics
Data type
BOOL STRUCT STRUCT
Default 0
Additional information For additional information, refer to the sections: Message texts and associated values of MOD_1/MOD_2/MOD_3/MOD_64 (Page 114) Maintenance status MS (Page 533)
6.18.3
Message texts and associated values of MOD_1/MOD_2/MOD_3/MOD_64
Assignment of message text and message class to the block parameters of MOD_1/MOD_2/MOD_3/ MOD_64
Message block ALARM_8P
EV_ID
Message number
1
2 3
4 5
Default message text
Message class
Module @1%d@/@2%d@/@3%d@: Failure
PLC Process Control Message Failure
No message
No message
Module @1%d@/@2%d@/@3%d@: @4W PLC Process Control Message %t#MOD_n_TXT@ (n = 1, 2, 3 or 64) Failure
No message
No message
114
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.19 MOD_3: Monitoring up to 16 channels on S7-200/300/400 SM modules without diagnostic capability
Message block ALARM_8P
Message number
6 7
8
Default message text
Module @1%d@/@2%d@/@3%d@: Maintenance demanded (external) Module @1%d@/@2%d@/@3%d@: Maintenance required (external)
Message class
No message PLC Process Control Message Error Preventative Maintenance Standard
Assignment of associated values to the block parameters of MOD_1/MOD_2/MOD_3
Message block ALARM_8P
EV_ID
Associ- ated value
1
2
3
4
Block parameters
MOD_INF.SUBN_ID MOD_INF.RACK_NO MOD_INF.SLOT_NO
Meaning
DP master system ID (byte) Rack/station number (byte) Slot number (byte) Text number from MOD_n_TXT (n = 1, 2, 3 or 64) (Message 1)
You will find the message texts and their text numbers in the "Text library for MOD_1, MOD_2, MOD_3, MOD_64 (Page 537)" section.
See also
Message Classes (Page 531)
6.19
MOD_3: Monitoring up to 16 channels on S7-200/300/400 SM modules without diagnostic capability
6.19.1
Description of MOD_3
Object name (type + number) FB 95 · MOD_3 block I/Os (Page 119)
Area of application
The MOD_3 block monitors up to 16 channels on S7-300/400 SM mixed modules without diagnostic capability (I/O modules). H-Systems support only the modules installed in switched racks.
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
115
Family: @System 6.19 MOD_3: Monitoring up to 16 channels on S7-200/300/400 SM modules without diagnostic capability
Calling OBs
The block must be installed in the run sequence in the following OBs:
OB 1 OB 83 OB 85 OB 86 OB 100
Cyclic program Insert/remove module interrupt Program execution error Rack failure Warm restart
Use in CFC
The following actions are executed automatically with the "Generate module drivers" CFC function:
· The MOD_3 block is installed in its runtime group downstream of the RACK block runtime group in the above-mentioned OBs.
· The MODE_xx inputs are configured.
· The logical addresses LADDR and LADDR1 are configured.
· The structures CPU_DIAG of the OB_BEGIN block and RAC_DIAG of the RACK block are interconnected with the MOD_3 structures of the same name.
· The output parameter of DXCHG_xx is interconnected with the following channel block at the DataXchg parameter.
· The output parameter of O_MS is interconnected with the following channel block at the MS parameter.
Function
The MOD_3 block cyclically analyzes all events that affect a module. It generates a channelspecific MODE (Page 517) and value status for the signal processing blocks. ALARM_8P reports the events. The message function can be disabled.
The block is enabled to run by the higher-level RACK block. The diagnostic event is entered in the CPU_DIAG start information of the OB_BEGIN block.
There is a MODE_xx input for each signal channel of the module. The module channel configuration data created in HW Config is reported here. MODE_00 to MODE_15 inputs are available for encoding up to 16 input channels, and MODE_16 ... MODE_31 for encoding up to 16 output channels. The function writes MODE_xx to the low word of the OMODE_xx (Page 527) output parameter. This occurs only during startup or if you set ACC_MODE = TRUE. The current channel value status is written to the most significant byte. If the result is positive, the system sets OMODE_xx = 16#80xxxxxx.
116
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.19 MOD_3: Monitoring up to 16 channels on S7-200/300/400 SM modules without diagnostic capability
The following events lead to the value status "invalid value due to higher-level error" (OMODE_xx = 16#40xxxxxx): · Events that are evaluated by the RACK block:
Rack failure (OB 86) (output parameter QRACKF = TRUE) Program execution error (OB 85) (output parameter QRACKF = TRUE) · Events that are evaluated by the MOD block: I/O access error (OB 85) (output parameter QPERAF = TRUE) Module removed (OB 83) (output parameter QMODF = TRUE)
"Module removed" and "I/O access error" events are reported to the OS by ALARM_8P. The diagnostics interrupt function distinguishes between module and channel errors, whereby each channel is assigned a message ID. The system verifies during startup that the module is available (plugged in). The module status information read here makes this data available in the form of service output parameters (MOD_INF). You can find additional information about faults in the System Software for S7-300/400 System and Standard Functions reference manual.
Redundancy
Block MOD_3 supports segment redundancy of H systems operating with distributed I/Os. If you want to use this function, you must configure the SUBN1_ID (connection to CPU 0) and SUBN2_ID (connection to CPU 1) inputs of the SUBNET block with the numbers of the redundant segments. If there is no segment redundancy, the remaining input must be set to the (default) value 16#FF.
MODE setting You can find additional information about this in the "MODE settings (Page 517)" section.
Note If you change the parameter settings for the MODE_xx inputs at runtime, these changes will not be accepted at the outputs until the ACC_MODE is set to 1.
OMODE Structure You can find additional information in the "OMODE (Page 527)" section.
Valid channel display The available channels on a module are displayed in the CH_EXIST output by setting a bit in the DWORD, starting at bit 0, for every existing channel. If the bit assigned to a channel = 0, the channel is not available.
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
117
Family: @System 6.19 MOD_3: Monitoring up to 16 channels on S7-200/300/400 SM modules without diagnostic capability
Output CH_OK displays the valid channels on a module by setting a bit to TRUE for every valid channel, where bit 0 is assigned to channel 0, etc. If the bit assigned to a channel is 0, the channel is faulty. If a module error occurs, all channels are disrupted.
Addressing
You can find additional information about this in the "Addressing (Page 530)" section.
Error handling
The plausibility of input parameters is not checked.
You can find additional information about error handling in the "Error information of output parameter MSG_STAT (Page 530)" section.
Service Information
To analyze faults, the module status information entered during startup is read via the MOD_INF structured output parameter. You can find additional information about this in the reference manual System Software for S7-300/400 System and Standard Functions; System Status List, Module Status Information.
Startup characteristics
After a restart/initial startup, the system verifies that the module is available under its logical base address. A restart (OB 100) is reported via the LSB in byte 2 of the OMODE_xx (Page 527) outputs.
Time response Not available
Message response
Block MOD_3 uses ALARM_8P to report module errors. The inputs DELAY1 and DELAY2 are used to delay the output of I/O access error messages. DELAY1 allows you to enter a time in seconds for which the block will wait for a higher-priority error (rack failure or removal/insertion) following a program execution error (OB 85) before it outputs the message. DELAY2 determines the number of seconds the block waits after the higher-priority error has been reported outgoing until it outputs the queued I/O access error as well. Both values are set to 2 seconds by default. The message function can be disabled by setting EN_MSG = FALSE.
Operator control and monitoring
If asset management is used in the project and the diagnostic screens have been generated, the faceplate can be called via its block icon.
For additional information, refer to the "Process Control System PCS 7; Maintenance Station" manual.
118
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.19 MOD_3: Monitoring up to 16 channels on S7-200/300/400 SM modules without diagnostic capability
Additional information For additional information, refer to the sections: Message texts and associated values of MOD_3 (Page 121) Maintenance status MS (Page 533) You can also find additional information on this in PCS 7 Advanced Process Library > Basics of APL > General functions of the blocks > Operating, monitoring and reporting > Release for maintenance
6.19.2
I/Os of MOD_3
The factory setting of the block display in the CFC is identified in the "I/O" column:
I/O name bold = I/O visible, I/O name normal = I/O not visible.
You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15)".
Input parameters
I/O (parameter) CHAN_NUM DELAY1 DELAY2 DIAG_BUF
EN_MSG EV_ID LADDR LADDR1 MODE_xx MS MS_REQ RACK_NO SLOT_NO SUBN_TYP SUBN1_ID SUBN2_ID
Meaning
Data type
Total number of channels -1 Alarm delay 1 (s) Alarm delay 2 (s) Entry in diagnostic buffer (relevant for maintenance person- nel) 1 = Enable message Message number Logical address of the input channels Logical address of the output channels Channel xx mode Maintenance status 1 = Request maintenance release Rack number Slot number 1 = external DP interface ID of the primary DP master system ID of the redundant DP master system
INT INT INT BOOL
BOOL DWORD INT INT DWORD DWORD BOOL BYTE BYTE BOOL BYTE BYTE
De- fault 0 2 2 0
1 0 0 0 0 0 0 0 0 0 255 255
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
119
Family: @System 6.19 MOD_3: Monitoring up to 16 channels on S7-200/300/400 SM modules without diagnostic capability
Output parameters
I/O (parameter) CH_ACTIVE CH_EXIST CH_OK DXCHG_xx
DXCHG1_xx
EXT_STAT EXT_STAT_A
MOD_INF MS_XCHG_xx
MSG_ACK MSG_STAT O_MS OMODE_xx QERR QMODF QPERAF QRACKF
Meaning
Channel active Channel exists Channel OK 1st internal data exchange channel for channel block 2nd internal data exchange channel for channel block Release for maintenance - extended status Extended status - Application Application data transfer active System structure: Module parameter Maintenance Status - Data exchange channel (xx = 00 - 63) Message acknowledgment Message error information Maintenance status Channel xx mode 1 = program error 1 = module removed/defective 1 = I/O access error 1 = higher-level error
Data type DWORD DWORD DWORD DWORD
DWORD
DWORD DWORD
STRUCT DWORD
WORD WORD DWORD DWORD BOOL BOOL BOOL BOOL
Default
16#00000000 0 0 0
0
0 0
0
0 0 0 0 1 0 0 0
In/out parameters
I/O (parameter) ACC_MODE CPU_DIAG RAC_DIAG
Meaning
1 = accept MODE settings System structure: CPU diagnostics System structure: Rack diagnostics
Data type
BOOL STRUCT STRUCT
De- fault
0
Additional information For additional information, refer to the sections: Message texts and associated values of MOD_1/MOD_2/MOD_3/MOD_64 (Page 121) Maintenance status MS (Page 533)
120
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.19 MOD_3: Monitoring up to 16 channels on S7-200/300/400 SM modules without diagnostic capability
6.19.3
Message texts and associated values of MOD_1/MOD_2/MOD_3/MOD_64
Assignment of message text and message class to the block parameters of MOD_1/MOD_2/MOD_3/ MOD_64
Message block ALARM_8P
EV_ID
Message number
1
2 3
4 5 6 7
8
Default message text
Message class
Module @1%d@/@2%d@/@3%d@: Failure
PLC Process Control Message Failure
No message
No message
Module @1%d@/@2%d@/@3%d@: @4W PLC Process Control Message %t#MOD_n_TXT@ (n = 1, 2, 3 or 64) Failure
No message
No message
No message
Module @1%d@/@2%d@/@3%d@: Maintenance demanded (external)
PLC Process Control Message Error
Module @1%d@/@2%d@/@3%d@: Maintenance required (external)
Preventative Maintenance Standard
Assignment of associated values to the block parameters of MOD_1/MOD_2/MOD_3
Message block ALARM_8P
EV_ID
Associ- ated value
1
2
3
4
Block parameters
MOD_INF.SUBN_ID MOD_INF.RACK_NO MOD_INF.SLOT_NO
Meaning
DP master system ID (byte) Rack/station number (byte) Slot number (byte) Text number from MOD_n_TXT (n = 1, 2, 3 or 64) (Message 1)
You will find the message texts and their text numbers in the "Text library for MOD_1, MOD_2, MOD_3, MOD_64 (Page 537)" section.
See also
Message Classes (Page 531)
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
121
Family: @System 6.20 MOD_4: Monitoring ET 200S modules downstream of a Y-Link
6.20
MOD_4: Monitoring ET 200S modules downstream of a Y-Link
6.20.1
Description of MOD_4
Object name (type + number) FB 119 · MOD_4 block I/Os (Page 125)
Area of application
Block MOD_4 monitors modules (up to 16 channels) of an ET 200S acting as a DPV0 slave (IM 151 High Feature) downstream of a Y link.
Calling OBs
The block must be installed in the run sequence in the following OBs:
OB 1 OB 82 OB 83 OB 85 OB 86 OB 100
Cyclic program Diagnostic interrupt Insert/remove module interrupt Program execution error Rack failure Warm restart
Use in CFC
The following actions are executed automatically with the "Generate module drivers" CFC function:
· Block MOD_4 is installed in its runtime group downstream of the OB_DIAG1 block, which is used for the ET 200S downstream of a Y link, in the above-mentioned OBs.
· The MODE_xx inputs (mode of module channels xx) are configured.
· The logical base address of the LADDR module is configured.
· The OUT structures CPU_DIAG of the OB_BEGIN block and RAC_DIAG of the OB_DIAG1 blocks (for DP slave downstream of a Y link, and an OB_DIAG1 for each Y link) are interconnected with the IN_OUT structures RAC_DIAG (DP slave) and RAC_DIAG_L (Y link) of MOD_4.
· The EN input is interconnected with the output of an AND block. whose inputs are interconnected with the outputs EN_SUBx (x = number of the DP master system) of the OB_BEGIN block, EN_Rxxx (xxx = rack/station number) of the SUBNET block, EN_F of the OB_DIAG1 block for the Y link, EN_F of the OB_DIAG1 block for the ET 200S downstream of the Y link, and EN_Mxx (xx = module slot number in the ET 200S) of the DPDIAGV0 block.
122
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.20 MOD_4: Monitoring ET 200S modules downstream of a Y-Link
· The DPA_M input is interconnected with the DPA_Mxx (xx= module slot number in the ET 200S) output of the DPDIAGV0 block.
· The output parameter of DXCHG_xx is interconnected with the following channel block at the DataXchg parameter.
· The output parameter of O_MS is interconnected with the following channel block at the MS parameter.
Function
Block MOD_4 analyzes all events related to an ET 200S module acyclically. It generates a channelspecific MODE (Page 517) and value status for the signal processing blocks. ALARM_8P reports events separately for each module.
The block enabled to run by the higher-level DPDIAGV0 block. The event to be evaluated is available at input DPA_M. Possible byte assignments:
0000000 = Module OK
0000001 = Module error
0000010 = Wrong module
0000011 = Module missing
00001xx = ET 200S failure; x = irrelevant
There is a MODE_xx input for each signal channel of the module. The module channel configuration data created in HW Config is reported here. The function writes MODE_xx to the low word of the OMODE_xx (Page 527) output parameter. This only occurs if the module status changes during startup, or if you set ACC_MODE = TRUE. The current channel value status is written to the most significant byte. If the result is positive, the system sets OMODE_xx = 16#80xxxxxx.
The following events lead to the value status "invalid value due to higher-level error" (OMODE_xx = 16#40xxxxxx):
· Events that are evaluated by the OB_DIAG1 block:
Rack failure (OB 86,OB 83) (output parameter QRACKF = TRUE)
· Events that are evaluated by the MOD block:
Module diagnostics (OB 82) (output parameter QMODF = TRUE)
ALARM_8P is used to report "Module error ", "Wrong module " or "Module missing " events to the OS.
Redundancy
You can not use redundant DP slaves downstream of a Y link.
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
123
Family: @System 6.20 MOD_4: Monitoring ET 200S modules downstream of a Y-Link
MODE setting You will find additional information about this in the "MODE settings (Page 517)" section.
Note If you change the parameter settings for the MODE_xx inputs at runtime, these changes will not be accepted at the outputs until the ACC_MODE is set to 1.
OMODE Structure You will find additional information in the "OMODE (Page 527)" section.
Valid channel display
The available channels on a module are displayed in the CH_EXIST output by setting a bit in the DWORD, starting at bit 0, for every existing channel. If the bit assigned to a channel = 0, the channel is not available.
Output CH_OK displays the valid channels on a module by setting a bit to TRUE for every valid channel, where bit 0 is assigned to channel 0, etc. If the bit assigned to a channel is 0, the channel is faulty. If a module error occurs, all channels are disrupted.
Addressing
You will find additional information about this in the "Addressing (Page 530)" section.
Error handling
The plausibility of input parameters is not checked. You will find additional information about error handling in "Error Information of Output Parameter MSG_STAT" (Page 530) section.
Startup characteristics A restart (OB 100) is reported via the LSB in byte 2 of the OMODE_xx (Page 527) outputs.
Time response Not available
Message response
MOD_4 uses ALARM_8P to report module errors. The message function can be disabled by setting EN_MSG = FALSE.
The block generates the maintenance status MS.
124
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.20 MOD_4: Monitoring ET 200S modules downstream of a Y-Link
Operator control and monitoring If asset management is used in the project and the diagnostic screens have been generated, the faceplate can be called via its block icon. For additional information, refer to the "Process Control System PCS 7; Maintenance Station" manual.
Additional information For additional information, refer to the sections: Message texts and associated values of MOD_4 (Page 127) Maintenance status MS (Page 533) You can also find additional information on this in PCS 7 Advanced Process Library > Basics of APL > General functions of the blocks > Operating, monitoring and reporting > Release for maintenance
6.20.2
I/Os of MOD_4
The factory setting of the block display in the CFC is identified in the "I/O" column:
I/O name bold = I/O visible, I/O name normal = I/O not visible.
You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15)".
Input parameters
I/O (parameter) CHAN_NUM DPA_M EN_MSG EV_ID LADDR MODE_xx MS MS_REQ PADP_ADR RACK_NO SLOT_NO SUBN_TYP SUBN1_ID SUBN2_ID
Meaning
Total number of channels -1 Module status 1 = Enable message Message number Logical address of the module Mode channel (xx = 00 - 15) Maintenance status 1 = Request maintenance release DP address of ET 200S Rack number (Y-Link) Slot number 1 = external DP interface ID of the primary DP master system ID of the redundant DP master system
Data type
INT BYTE BOOL DWORD INT DWORD DWORD BOOL BYTE BYTE BYTE BOOL BYTE BYTE
De- fault
0 0 1 1 0 0 0 0 255 0 0 0 255 255
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
125
Family: @System 6.20 MOD_4: Monitoring ET 200S modules downstream of a Y-Link
Output parameters
I/O (parameter) CH_ACTIVE CH_EXIST CH_OK DXCHG_xx DXCHG1_xx EXT_STAT EXT_STAT_A
MSG_ACK MSG_STAT MS_XCHG_xx
O_MS OMODE_xx QERR QMODF QRACKF
Meaning
Channel active Channel exists Channel OK 1st internal data exchange channel for channel block 2nd internal data exchange channel for channel block Release for maintenance - extended status Extended status - Application Application data transfer active Message acknowledgment Message error information Maintenance Status - Data exchange channel (xx = 00 - 15) Maintenance status Mode channel (xx = 00 - 15) 1 = program error 1 = module removed/defective 1 = higher-level error
Data type DWORD DWORD DWORD DWORD DWORD DWORD DWORD
WORD WORD DWORD
DWORD DWORD BOOL BOOL BOOL
Default
16#00000000 0 0 0 0 0 0
0 0 0
0 0 1 0 0
In/out parameters
I/O (parameter) ACC_MODE CPU_DIAG RAC_DIAG
RAC_DIAG_L
Meaning
1 = accept new MODE settings System structure: CPU diagnostics System structure: Rack diagnostics of the DP slave down- stream of Y link System structure: Rack diagnostics for the Y link
Data type
BOOL STRUCT STRUCT
De- fault
0
STRUCT
Additional information For additional information, refer to the sections: Message texts and associated values of MOD_4 (Page 127) Maintenance status MS (Page 533)
126
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
6.20.3
Family: @System 6.20 MOD_4: Monitoring ET 200S modules downstream of a Y-Link
Message texts and associated values of MOD_4
Assignment of message text and message class
Message block ALARM_8P
EV_ID
Message number
1
2
3
4 5 6 7
8
Default message text
Module @1%d@/@2%d@/@3%d@/ @4%d@: Error Module @1%d@/@2%d@/@3%d@/ @4%d@: Wrong Module @1%d@/@2%d@/@3%d@/ @4%d@: Missing No message No message No message Module @1%d@/@2%d@/@3%d@: Maintenance demanded (external) Module @1%d@/@2%d@/@3%d@: Maintenance required (external)
Message class
PLC Process Control Message Failure PLC Process Control Message Failure PLC Process Control Message Failure No message No message No message PLC Process Control Message Error Preventative Maintenance Standard
Assignment of associated values
Message block ALARM_8P
EV_ID
Associ- ated value
1
2
3
4
Block parameter
SUBN_ID RACK_NO PADP_ADR SLOT_NO
Meaning
DP master system ID (byte) Rack/station number (byte) (Y link) DP address of ET 200S Slot number (byte)
See also
Message Classes (Page 531)
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
127
Family: @System 6.21 MOD_64: Monitoring 64 channels on S7-300 SM modules without diagnostic capability
6.21
MOD_64: Monitoring 64 channels on S7-300 SM modules without diagnostic capability
6.21.1
Description of MOD_64
Object name (type + number) FB 137 · MOD_64 block I/Os (Page 131)
Area of application
The MOD_64 block monitors 64 channels on S7-300 SM modules without diagnostic capability (no mixed modules). H systems support only the modules installed in switched racks.
Calling OBs
The block must be installed in the run sequence in the following OBs:
OB 1 OB 83 OB 85 OB 86 OB 100
Cyclic program Insert/remove module interrupt Program execution error Rack failure Warm restart
Use in CFC
The following actions are executed automatically with the "Generate module drivers" CFC function:
· The MOD_64 block is installed in its runtime group downstream of the RACK block runtime group in the above-mentioned OBs.
· The MODE_xx inputs (mode of module channels xx) are configured.
· The logical base address of the LADDR module is configured.
· The OUT structures CPU_DIAG of the OB_BEGIN block and RAC_DIAG of the RACK block are interconnected with the IN_OUT structures of the same name of MOD_2.
· The EN input is interconnected with the output of an AND block. Its inputs are interconnected with the outputs EN_SUBx (x = number of the DP master system) of the OB_BEGIN block, EN_Rxxx (xxx = rack/station number) of the SUBNET block and EN_Mxx (xx = module number) of the RACK block.
· The output parameter of DXCHG_xx is interconnected with the following channel block at the DataXchg parameter.
· The output parameter of O_MS is interconnected with the following channel block at the MS parameter.
128
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Function
Family: @System 6.21 MOD_64: Monitoring 64 channels on S7-300 SM modules without diagnostic capability
The MOD_64 block analyzes all events that affect a module and its channels acyclically. It generates a channel-specific MODE (Page 517) and value status for the signal processing blocks. ALARM_8P reports the events.
The block is enabled to run by the higher-level RACK block. The event to be evaluated can be found in the CPU_DIAG start information of the OB_DIAG block. There is a MODE_xx input for each signal channel of the module. The module channel configuration data created in HW Config is reported here. The function writes MODE_xx to the low word of the OMODE_xx (Page 527) output parameter. This occurs only during startup or if you set ACC_MODE = TRUE. The current channel value status is written to the most significant byte. If the result is positive, the system sets OMODE_xx = 16#80xxxxxx.
The following events lead to the value status "invalid value due to higher-level error" (OMODE_xx = 16#40xxxxxx):
· Events that are evaluated by the RACK block:
Rack failure (OB 86) (output parameter QRACKF = TRUE)
· Events that are evaluated by the MOD block:
Program execution error (OB 85) (output parameter QPERAF = TRUE)
Module removed (OB 83) (output parameter QMODF = TRUE)
"Module removed" and "I/O access error" events are reported to the OS by ALARM_8P. The diagnostics interrupt function distinguishes between module and channel errors, whereby each channel is assigned a message ID.
The system verifies during startup that the module is available (plugged in). The module status information that is read here is then available in the form of service output parameters (MOD_INF).
You will find additional information about errors in the System Software for S7-300/400; System and Standard Functions reference manual.
Redundancy
The higher-level RACK block monitors the redundancy of DP master systems operating in an H system.
MODE setting You will find additional information about this in the "MODE settings (Page 517)" section.
Note If you change the parameter settings for the MODE_xx inputs at runtime, these changes will not be accepted at the outputs until the ACC_MODE is set to 1.
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
129
Family: @System 6.21 MOD_64: Monitoring 64 channels on S7-300 SM modules without diagnostic capability
OMODE Structure You will find additional information in the "OMODE (Page 527)" section.
Valid channel display
The available channels on a module are displayed in the CH_EXIST or CH_EXIST_2 output by setting a bit in the DWORD, starting at bit 0, for every existing channel. If the bit assigned to a channel = 0, the channel is not available.
Output CH_OK or CH_OK_2 displays the valid channels on a module by setting a bit to TRUE for every valid channel, where bit 0 is assigned to channel 0, etc. If the bit assigned to a channel is 0, the channel is faulty. If a module error occurs, all channels are disrupted.
Addressing
You will find additional information about this in the "Addressing (Page 530)" section.
Error handling
The plausibility of input parameters is not checked.
You will find additional information about error handling in the "Error information of output parameter MSG_STAT (Page 530)" section.
Service Information
To analyze faults, the module status information entered during startup is read via the MOD_INF structured output parameter. You will find additional information about this in the reference manual System Software for S7-300/400 System and Standard Functions; System Status List, Module Status Information.
Startup characteristics
After a restart/initial startup, the system verifies that the module is available under its logical base address. A restart (OB 100) is reported via the LSB in byte 2 of the OMODE_xx (Page 527) outputs.
Time response Not available
130
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.21 MOD_64: Monitoring 64 channels on S7-300 SM modules without diagnostic capability
Message response MOD_64 uses ALARM_8P to report module errors. The inputs DELAY1 and DELAY2 are used to delay the output of I/O access error messages. DELAY1 allows you to enter a time in seconds for which the block will wait for a higher-priority error (rack failure or removal/insertion) following a program execution error (OB 85) before it outputs the message. The message is output only under the condition that no higher-priority error is reported within this delay time. DELAY2 determines the number of seconds the block waits after the higher-priority error has been reported outgoing until it outputs the queued I/O access error as well. Both values are set to 2 seconds by default. The message function can be disabled by setting EN_MSG = FALSE.
Operator control and monitoring If asset management is used in the project and the diagnostic screens have been generated, the faceplate can be called via its block icon. For additional information, refer to the "Process Control System PCS 7; Maintenance Station" manual.
Additional information For additional information, refer to the sections: Message texts and associated values of MOD_64 (Page 133) Maintenance status MS (Page 533) You can also find additional information on this in PCS 7 Advanced Process Library > Basics of APL > General functions of the blocks > Operating, monitoring and reporting > Release for maintenance
6.21.2
I/Os of MOD_64
The factory setting of the block display in the CFC is identified in the "I/O" column:
I/O name bold = I/O visible, I/O name normal = I/O not visible.
You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15)".
Input parameters
I/O (parameter) CHAN_NUM DELAY1 DELAY2 DIAG_BUF
EN_MSG
Meaning
Data type
Total number of channels -1 Alarm delay 1 (s) Alarm delay 2 (s) Entry in diagnostic buffer (relevant for maintenance per- sonnel) 1 = Enable message
INT INT INT BOOL
BOOL
De- fault 0 2 2 0
1
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
131
Family: @System 6.21 MOD_64: Monitoring 64 channels on S7-300 SM modules without diagnostic capability
I/O (parameter)
EV_ID LADDR MODE_xx MS MS_REQ RACK_NO SLOT_NO SUBN_TYP SUBN1_ID SUBN2_ID
Meaning
Message number Logical address of the module Mode channel (xx = 00 - 63) Maintenance status 1 = Request maintenance release Rack number Slot number 1 = external DP interface ID of the primary DP master system ID of the redundant DP master system
Data type
DWORD INT DWORD DWORD BOOL BYTE BYTE BOOL BYTE BYTE
De- fault
0 0 0 0 0 0 0 0 255 255
Output parameters
I/O (parameter) CH_ACTIVE CH_ACTIVE_2 CH_EXIST CH_EXIST_2 CH_OK CH_OK_2 DXCHG_xx
DXCHG1_xx
EXT_STAT EXT_STAT_2 EXT_STAT_A
MOD_INF MS_XCHG_xx
MSG_ACK MSG_STAT O_MS OMODE_xx QERR QMODF QPERAF QRACKF
Meaning
Data type
Channel active
DWORD
Channel active
DWORD
Channel exists (0 to 31)
DWORD
Channel exists (32 to 63)
DWORD
Channel OK (0 to 31)
DWORD
Channel OK (32 to 63)
DWORD
1st internal data exchange channel for chan- DWORD nel block
2nd internal data exchange channel for chan- DWORD nel block
Release for maintenance - extended status DWORD
Release for maintenance - extended status 2 DWORD
Extended status - Application Application data transfer active
DWORD
System structure: Module parameter
STRUCT
Maintenance Status - Data exchange channel DWORD (xx = 00 - 63)
Message acknowledgment
WORD
Message error information
WORD
Maintenance status
DWORD
Mode channel (xx = 00 - 63)
DWORD
1 = program error
BOOL
1 = module removed/defective
BOOL
1 = I/O access error
BOOL
1 = higher-level error
BOOL
Default
16#00000000 16#00000000 0 0 0 0 0
0
0 0 0
0
0 0 0 0 1 0 0 0
132
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.21 MOD_64: Monitoring 64 channels on S7-300 SM modules without diagnostic capability
In/out parameters
I/O (parameter) ACC_MODE CPU_DIAG RAC_DIAG
Meaning
1 = accept MODE settings System structure: CPU diagnostics System structure: Rack diagnostics
Data type
BOOL STRUCT STRUCT
De- fault
0
Additional information For additional information, refer to the sections: Message texts and associated values of MOD_1/MOD_2/MOD_3/MOD_64 (Page 133) Maintenance status MS (Page 533)
6.21.3
Message texts and associated values of MOD_1/MOD_2/MOD_3/MOD_64
Assignment of message text and message class to the block parameters of MOD_1/MOD_2/MOD_3/ MOD_64
Message block ALARM_8P
EV_ID
Message number
1
2 3
4 5 6 7
8
Default message text
Message class
Module @1%d@/@2%d@/@3%d@: Failure
PLC Process Control Message Failure
No message
No message
Module @1%d@/@2%d@/@3%d@: @4W PLC Process Control Message %t#MOD_n_TXT@ (n = 1, 2, 3 or 64) Failure
No message
No message
No message
Module @1%d@/@2%d@/@3%d@: Maintenance demanded (external)
PLC Process Control Message Error
Module @1%d@/@2%d@/@3%d@: Maintenance required (external)
Preventative Maintenance Standard
Assignment of associated values to the block parameters of MOD_1/MOD_2/MOD_3
Message block ALARM_8P
EV_ID
Associ- ated value
1
2
Block parameters
MOD_INF.SUBN_ID MOD_INF.RACK_NO
Meaning
DP master system ID (byte) Rack/station number (byte)
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
133
Family: @System 6.22 MOD_CENTRAL: Monitoring external CP and IM
Message block ALARM_8P
Associ- ated value
3
4
Block parameters MOD_INF.SLOT_NO
Meaning
Slot number (byte) Text number from MOD_n_TXT (n = 1, 2, 3 or 64) (Message 1)
You will find the message texts and their text numbers in the "Text library for MOD_1, MOD_2, MOD_3, MOD_64 (Page 537)" section.
See also
Message Classes (Page 531)
6.22
MOD_CENTRAL: Monitoring external CP and IM
6.22.1
Description of MOD_CENTRAL
Object name (type + number) FB 206 · I/Os of MOD_CENTRAL (Page 135)
Area of application
The block monitors external CP 443-1 PROFINET, external CP 443-5 PROFIBUS and IM 460 / IM 461 from version PCS7 V8.0 SP1.
MODE Configuration
Input parameters MODE
PROFIBUS (DP-CP-IO nodes)
16#00000001
PROFINET (IE-CP-Net- work nodes)
16#00000002
PROFINET (IE-CP-IO no- Central IM-46x-x /
des)
CP(Gateway)
16#00000004
16#00000003
Additional information For additional information, refer to the following sections: Message texts and associated values of MOD_CENTRAL (Page 136) Maintenance status MS (Page 533)
See also
OMODE settings for SM modules (Page 527)
134
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
6.22.2
Family: @System 6.22 MOD_CENTRAL: Monitoring external CP and IM
I/Os of MOD_CENTRAL
The factory setting of the block display in the CFC is identified in the "I/O" column: I/O name bold = I/O visible, I/O name normal = I/O not visible. You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15)".
Input parameters
I/O (parameter) DIAG_BUF
EN_MSG EV_ID LADDR MODE MS GBIT_ADR GBIT_PORT1_ADR PNIO_ADR PORT1_ADR PORT1_CONNECT PORT2_ADR PORT2_CONNECT PORT3_ADR PORT3_CONNECT PORT4_ADR PORT4_CONNECT RACK_NO SLOT_NO SUBN_TYP SUBN1_ID
Meaning
Data type
Entry in diagnostic buffer (relevant for maintenance BOOL personnel)
1 = enable message
BOOL
Message number
DWORD
Logical address of the module
INT
Operating mode
DWORD
Maintenance status
DWORD
Diagnostics address GBIT interface
INT
Diagnostics address GBIT PORT 1
INT
Diagnostic address PN-IO interface
INT
Diagnostic address PORT 1
INT
1=Port 1 connected
BYTE
Diagnostic address PORT 2
INT
1=Port 2 connected
BYTE
Diagnostic address PORT 3
INT
1=Port 3 connected
BYTE
Diagnostic address PORT 4
INT
1=Port 4 connected
BYTE
Rack number
BYTE
Slot number
BYTE
0 = central / 1 = external
BOOL
CP: ID of subnet, if available. Otherwise, default val- BYTE ue IM 46x-x: always 0
Default
0
1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 16#FF
Output parameters
I/O (parameter) EXT_STAT MOD_INF MSG_ACK MSG_STAT OMODE O_MS
Meaning
Maintenance Release - Extended Status System structure: Module parameter Message acknowledgment Message error information Operating mode Maintenance status
Data type
DWORD STRUCT WORD WORD DWORD DWORD
Default
0
0 0 0 0
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
135
Family: @System 6.22 MOD_CENTRAL: Monitoring external CP and IM
I/O (parameter)
QERR QMODF QRACKF
Meaning
1 = program error 1 = module removed/defective 1 = higher-level error
Data type
BOOL BOOL BOOL
Default
1 0 0
In/out parameters
I/O (parameter) ACC_MODE CPU_DIAG RAC_DIAG
Meaning
1 = accept MODE settings CPU diagnostics (system structure) System structure: Rack diagnostics
Data type
BOOL STRUCT STRUCT
Default 0
Additional information For additional information, refer to the sections: Message texts and associated values of MOD_CENTRAL (Page 136) Maintenance status MS (Page 533)
6.22.3
Message texts and associated values of MOD_CENTRAL
Assignment of message text and message class
Message block ALARM_8P
EV_ID
Message number
1
2
3
4
5 6 7 8
Default message text
Message class
Module @1%d@/@2%d@/@3%d@: Fail- ure
Module @1%d@/@2%d@/@3%d@: Maintenance demanded
Module @1%d@/@2%d@/@3%d@: Maintenance alarm
Module @1%d@/@2%d@/@3%d@: Maintenance required
PLC Process Control Message Failure
PLC Process Control Message Error
PLC Process Control Message Failure
Preventative Maintenance Standard
No message
No message
No message
No message
136
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.23 MOD_CP: CP 341 diagnostics
Assignment of associated values
Message block Associ-
ALARM_8P
ated
value
EV_ID
1
2
3
Block parameters
SUBN_ID RACK_NO SLOT_NO
Meaning
DP master system ID (byte) Rack/station number (byte) Slot number (byte)
You can find additional information in the section: Message Classes (Page 531).
6.23
MOD_CP: CP 341 diagnostics
6.23.1
Description of MOD_CP
Object name (type + number) FB 98 · MOD_CP block I/Os (Page 140)
Area of application
The MOD_CP block monitors a serial communication module CP 341. H systems support only the modules installed in switched racks.
Calling OBs
The block must be installed in the run sequence in the following OBs:
OB 1 OB 82 OB 83 OB 85 OB 86 OB 100
Cyclic program Diagnostic interrupt Insert/remove module interrupt Program execution error Rack failure Warm restart
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
137
Family: @System 6.23 MOD_CP: CP 341 diagnostics
Use in CFC
The following actions are executed automatically with the "Generate module drivers" CFC function:
· The MOD_CP block is installed in its runtime group downstream of the RACK block runtime group in the above-mentioned OBs.
· The SUBN1_ID, SUBN2_ID, SUBN_TYP, RACK_NO, and SLOT_NO inputs are configured.
· The logical base address LADDR of the module is configured.
· The OUT structures CPU_DIAG of the OB_BEGIN block and RAC_DIAG of the RACK block are interconnected with the IN_OUT structures of the same name of MOD_CP.
· The EN input is interconnected with the output of an AND block. Its inputs are interconnected with the outputs EN_SUBx (x = number of the DP master system) of the OB_BEGIN block, EN_Rxxx (xxx = rack/station number) of the SUBNET block and EN_Mxx (xx = module number) of the RACK block.
Function and method of operation
Block MOD_CP analyzes all events that affect a module and its channels acyclically. and generates a value status for the serial communication blocks (such as RCV_341). ALARM_8P is used to report these events.
The higher-level RACK block enables the MOD_CP block to run. The event to be evaluated is stored in the CPU_DIAG start and diagnostic information of the OB_BEGIN block. A (MODE_00) is assigned to the communication channel of the module. The function writes MODE_xx to the low word of the OMODE_xx (Page 527) output. This occurs only during startup or if you set ACC_MODE = TRUE. The current value status of the communication channel is written to the most significant byte. If the result is positive, the system sets OMODE_xx = 16#80xxxxxx.
The following events lead to the value status "invalid value due to higher-level error" (OMODE_xx = 16#40xxxxxx):
· Events that are evaluated by the RACK block:
Rack failure (OB 86) (output parameter QRACKF = TRUE)
· Events that are evaluated by the MOD block:
Program execution error (OB 85) (output parameter QPERAF = TRUE)
Module removed (OB 83) (output parameter QMODF = TRUE)
Diagnostic interrupt (OB 82) Distinguishing between module errors and channel errors
The following events are module errors (QMODF = TRUE output parameter):
ALARM_8P is used to report "Module removed", "I/O access error" and "Diagnostic interrupt" events to WinCC.
Redundancy
The higher-level RACK block monitors the redundancy of DP master systems operating in an H system.
138
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.23 MOD_CP: CP 341 diagnostics
Valid channel display The existing channels on a module are displayed in the CH_EXIST output by setting a bit in the DWORD, starting at bit 0, for every existing channel. If the bit assigned to a channel = 0, the channel is not available. Output CH_OK displays the valid channels on a module by setting a bit to TRUE for every valid channel, where bit 0 is assigned to channel 0, etc. If the bit assigned to a channel is 0, the channel is faulty. If a module error occurs, all channels are disrupted.
Error handling The plausibility of input parameters is not checked.
Startup characteristics After a restart/initial startup, the system verifies that the module is available under its logical base address. A restart (OB 100) is reported via the LSB in byte 2 of the OMODE_xx (Page 527) outputs.
Overload behavior The MOD_CP block counts the OB 82 calls. The counter is reset in OB1. If more than five OB 82 events occur in succession before the cycle control point is reached (OB 1), these events are rejected and the message "OB 82 DP master failure: x Rack: y Slot: z" is output.
Time response Not available
Message response MOD_CP uses ALARM_8P to report module errors. The inputs DELAY1 and DELAY2 are used to delay the output of I/O access error messages. DELAY1 allows you to enter a time in seconds for which the block will wait for a higher-priority error (rack failure or removal/insertion) following a program execution error (OB 85) before it outputs the message. The message is output only under the condition that no higher-priority error is reported within this delay time. DELAY2 determines the number of seconds the block waits after the higher-priority error has been reported outgoing until it outputs the queued I/O access error as well. Both values are set to 2 seconds by default. The message function can be disabled by setting EN_MSG = FALSE.
Operator control and monitoring If asset management is used in the project and the diagnostic screens have been generated, the faceplate can be called via its block icon. For additional information, refer to the "Process Control System PCS 7; Maintenance Station" manual.
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
139
Family: @System 6.23 MOD_CP: CP 341 diagnostics
Additional information For additional information, refer to the sections: Message texts and associated values of MOD_CP (Page 142) Maintenance status MS (Page 533)
See also
MODE settings for SM modules (Page 517)
6.23.2
I/Os of MOD_CP
The factory setting of the block display in the CFC is identified in the "I/O" column: I/O name bold = I/O visible, I/O name normal = I/O not visible.
You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15)".
Input parameters
I/O (parameter) DELAY1 DELAY2 DIAG_BUF
EN_MSG EV_ID LADDR MODE_00
MODE_01
MS RACK_NO SLOT_NO SUBN_TYP SUBN1_ID SUBN2_ID
Meaning
Data type
Alarm delay 1 (s) Alarm delay 2 (s) Entry in diagnostic buffer (relevant for maintenance per- sonnel) 1 = enable message Message number Logical address of the module Channel 1 mode 1: CP341 1: if the operating mode <> none 2: if the operating mode = none Channel 2 mode 0: for CP341 1: if the operating mode <> none 2: if the operating mode = none Maintenance status Rack number Slot number 1 = external DP interface ID of the primary DP master system ID of the redundant DP master system
INT INT BOOL
BOOL DWORD INT WORD
WORD
DWORD BYTE BYTE BOOL BYTE BYTE
Default
2 2 0
1 0 0 0
0
0 0 0 0 255 255
140
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Output parameters
I/O (parameter) CH_ACTIVE CH_EXIST CH_OK DIAG_INF MOD_INF MSG_ACK MSG_STAT O_MS OMODE_00 OMODE_01 QERR QMODF QPERAF QRACKF
Meaning
Channel active Channel exists Channel OK System structure: Diagnostic information System structure: Module parameter Message acknowledgment Message error information Maintenance status Value status/channel 1 mode Value status/channel 2 mode 1 = program error 1 = module removed/defective 1 = I/O access error 1 = higher-level error
Family: @System 6.23 MOD_CP: CP 341 diagnostics
Data type
DWORD DWORD DWORD STRUCT STRUCT WORD WORD DWORD DWORD DWORD BOOL BOOL BOOL BOOL
Default
16#00000000 0 0
0 0 0 0 0 1 0 0 0
In/out parameters
I/O (parameter) ACC_MODE CPU_DIAG RAC_DIAG
Meaning
1 = accept MODE settings System structure: CPU diagnostics System structure: Rack diagnostics
Data type
BOOL STRUCT STRUCT
Default 0
Additional information For additional information, refer to the sections: Message texts and associated values of MOD_CP (Page 142) Maintenance status MS (Page 533)
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
141
Family: @System 6.23 MOD_CP: CP 341 diagnostics
6.23.3
Message texts and associated values of MOD_CP
Assignment of message text and message class
Message block ALARM_8P
EV_ID
Mes- Block sage param- number eter
1
QMODF
2
QPERAF
3
4
5
6
7
8
Default message text
Message class
CP @1%d@/@2%d@/@3%d@: Re- PLC Process Control Message -
moved
Failure
CP @1%d@/@2%d@/@3%d@: Ac- PLC Process Control Message -
cess error
Failure
CP @1%d@/@2%d@/@3%d@: @4W PLC Process Control Message -
%t#MOD_CP_TXT@
Failure
CP @1%d@/@2%d@/@3%d@: Wrong parameter
PLC Process Control Message Failure
CP @1%d@/@2%d@/@3%d@: Wire break
PLC Process Control Message Failure
CP @1%d@/@2%d@/@3%d@/2: Wrong parameter
PLC Process Control Message Failure
CP @1%d@/@2%d@/@3%d@/2: Wire break
PLC Process Control Message Failure
CP @1%d@/@2%d@/@3%d@: Multiple diagnostic interrupt
PLC Process Control Message Failure
You will find the message texts and their text numbers in the "Text library for MOD_CP (Page 537)" section.
Assignment of associated values
Message block Associ-
ALARM_8P
ated
value
EV_ID
1
2
3
Block parameters
SUBN_ID RACK_NO SLOT_NO
Meaning
DP master system ID (byte) Rack/station number (byte) Slot number (byte)
SUBN_ID = SUBN1_ID. If SUBN1_ID = 16#FF, the associated value is substituted with SUBN2_ID.
See also
Message Classes (Page 531)
142
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
6.24
Family: @System 6.24 MOD_CP_PN: Monitoring of serial communication modules
MOD_CP_PN: Monitoring of serial communication modules
6.24.1
Description of MOD_CP_PN
Object name (type + number) FB 201 · I/Os of MOD_CP_PN (Page 143)
Area of application The MOD_CP_PN block monitors a serial communication module CP 341.
6.24.2
I/Os of MOD_CP_PN
The factory setting of the block display in the CFC is identified in the "I/O" column: I/O name bold = I/O visible, I/O name normal = I/O not visible.
You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15)".
Input parameters
I/O (parameter) DELAY1 DELAY2 DIAG_BUF
EN_MSG EV_ID LADDR MODE_00 MODE_01 MS RACK_NO SLOT_NO SUBSL_NO SUBN_TYP SUBN1_ID SUBN2_ID
Meaning
Data type
Alarm delay 1 (s) Alarm delay 2 (s) Entry in diagnostic buffer (relevant for maintenance per- sonnel) 1 = enable message Message number ALARM_8P (assigned by the ES) Logical address of the module Channel 1 mode Channel 2 mode (CP 441 only) Maintenance status Rack number Slot number Subslot number 1 = external PN interface PN IO system 1 ID (100 - 115) PN IO system 2 ID (100 - 115)
INT INT BOOL
BOOL DWORD INT WORD WORD DWORD BYTE BYTE BYTE BOOL BYTE BYTE
Default
2 2 0
1 0 0 0 0 0 0 0 0 0 255 255
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
143
Family: @System 6.24 MOD_CP_PN: Monitoring of serial communication modules
Output parameters
I/O (parameter) CH_ACTIVE
CH_EXIST CH_OK DIAG_INF MOD_INF MSG_ACK MSG_STAT O_MS OMODE_00 OMODE_01 QERR QMODF QPERAF QRACKF
Meaning
Channel active
Channel exists Channel OK System structure: Diagnostic information System structure: Module parameter Message acknowledgment Message error information Maintenance status Value status/channel 1 mode Value status/channel 2 mode (CP 441 only) 1 = program error 1 = module removed/defective 1 = I/O access error 1 = higher-level error
In/out parameters
I/O (parameter)
ACC_MODE CPU_DIAG_PN RAC_DIAG
Meaning
1 = accept MODE settings System structure: CPU diagnostics System structure: Rack diagnostics
Additional information For additional information, refer to the sections: Message texts and associated values of MOD_CP_PN (Page 145) Maintenance status MS (Page 533)
Data type
DWORD
DWORD DWORD STRUCT STRUCT WORD WORD DWORD DWORD DWORD BOOL BOOL BOOL BOOL
Default
16#000 00000 0 0
0 0 0 0 0 1 0 0 0
Data type
BOOL STRUCT STRUCT
Default 0
144
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
6.24.3
Family: @System 6.24 MOD_CP_PN: Monitoring of serial communication modules
Message texts and associated values of MOD_CP_PN
Assignment of message text and message class The process control messages of ALARM_8P with EV_ID1 are assigned as follows:
Message block ALARM_8P
EV_ID1
Message number
1
2
3
4
5
6
7
8
Default message text
Message class
CP @1%d@/@2%d@/@3%d@: With- drawn
PLC Process Control Message Failure
CP @1%d@/@2%d@/@3%d@: Access er- PLC Process Control Message -
ror
Failure
CP @1%d@/@2%d@/@3%d@: @4W %t#MOD_CP_TXT@
PLC Process Control Message Failure
CP @1%d@/@2%d@/@3%d@: Wrong parameter
PLC Process Control Message Failure
CP @1%d@/@2%d@/@3%d@: Wire break
PLC Process Control Message Failure
CP @1%d@/@2%d@/@3%d@/2: Wrong parameter
SPLC Process Control Mes- sage - Failure
CP @1%d@/@2%d@/@3%d@/2: Wire break
PLC Process Control Message Failure
CP @1%d@/@2%d@/@3%d@: Multiple diagnostic interrupt
PLC Process Control Message Failure
Associated values of ALARM_8P with EV_ID1
Associated value
1 2 3
Block parameter
SUBN_ID RACK_NO SLOT_NO
Meaning
ID of the PN IO system (bytes) Rack/station number (byte) Slot number (byte)
You can find the message texts and their text numbers in the section "Text library for MOD_CP_PN (FB201) (Page 546)".
You can find additional information in the section: AUTOHOTSPOT.
See also
Message Classes (Page 531)
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
145
Family: @System 6.25 MOD_D1: Monitoring up to 16 channels on S7-300/400 SM modules with diagnostic functions
6.25
MOD_D1: Monitoring up to 16 channels on S7-300/400 SM modules with diagnostic functions
6.25.1
Description of MOD_D1
Object name (type + number) FB 93 · MOD_D1 block I/Os (Page 152)
Area of application The MOD_D1 block can monitor the following modules: · Power modules · ET200S counter modules · FM350 counter modules · up to 16 channels on S7-300/400 SM modules with diagnostic functions (no mixed modules) · and the power supplies of an ET 200iSP in a redundant configuration. H systems support only the modules installed in switched racks.
Calling OBs
The block must be installed in the run sequence in the following OBs:
OB 1 OB 82 OB 83 OB 85 OB 86 OB 100
Cyclic program Diagnostic interrupt Insert/remove module interrupt Program execution error Rack failure Warm restart
Use in CFC
The following actions are executed automatically with the "Generate module drivers" CFC function:
· The MOD_D1 block is installed in its runtime group downstream of the RACK block runtime group in the above-mentioned OBs.
· The MODE_xx (mode of the channels xx of the module), SUBN1_ID, SUBN2_ID, and SUBN_TYP inputs are configured.
· The logical base address LADDR of the module is configured.
146
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.25 MOD_D1: Monitoring up to 16 channels on S7-300/400 SM modules with diagnostic functions
· The OUT structures CPU_DIAG of the OB_BEGIN block and RAC_DIAG of the RACK block are interconnected with the IN_OUT structures of the same name of MOD_D1.
· The EN input is interconnected with the output of an AND block. Its inputs are interconnected with the outputs EN_SUBx (x = number of the DP master system) of the OB_BEGIN block, EN_Rxxx (xxx = rack/station number) of the SUBNET block and EN_Mxx (xx = module number) of the RACK block.
· The output parameter of DXCHG_xx is interconnected with the following channel block at the DataXchg parameter.
· The output parameter of O_MS is interconnected with the following channel block at the MS parameter.
Function and method of operation Block MOD_D1 analyzes all events that affect a module and its channels acyclically. It generates a channel-specific MODE (Page 517) and value status for the signal processing blocks. ALARM_8P is used to report these events.
MOD_D1 monitors the redundant power supplies for ET 200iSP and reports the failure of a power supply via the slot number of the interface module. If the power supply fails, the maintenance status (MS) of the module shows "Maintenance: Requirement Moderate".
Block MOD_D1 is enabled by the higher-level RACK block at runtime. The event to be evaluated is stored in the CPU_DIAG start and diagnostic information of the OB_BEGIN block. There is a MODE_xx input for each signal channel of the module. The module channel configuration data created in HW Config is reported here. The function writes MODE_xx to the low word of the OMODE_xx (Page 527) output parameter. This occurs only during startup or if you set ACC_MODE = TRUE. The current channel value status is written to the most significant byte. If the result is positive, the system sets OMODE_xx = 16#80xxxxxx.
The following events lead to the value status "invalid value due to higher-level error" (OMODE_xx = 16#40xxxxxx):
· Events that are evaluated by the RACK block:
Rack failure (OB 86) (output parameter QPERAF = TRUE)
· Events that are evaluated by the MOD block:
Program execution error (OB 85) (output parameter QPERAF = TRUE)
Module removed (OB 83) (output parameter QMODF = TRUE)
Diagnostic interrupt (OB 82) Distinguishing between module errors and channel errors
The following events are module errors (QMODF = TRUE output parameter): · External auxiliary voltage missing
· Front connector missing
· Module not configured
· Wrong parameter in module
· Wrong/missing module
· Communication error at a CPU module
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
147
Family: @System 6.25 MOD_D1: Monitoring up to 16 channels on S7-300/400 SM modules with diagnostic functions
· Timeout (watchdog) · Loss of internal power at a module · Rack failure · CPU failure · EPROM error · RAM error · ADC/DAC error · Fuse tripped · Power supply 1: Error · Power supply 2: Error
The following events are channel errors (value status "invalid value", OMODE_xx = 16#00xxxx): · Configuration/parameter assignment error · Common-mode errors (analog I/Os only) · Short-circuit to P · Short circuit to M · Interruption at the output transistor · Wire break · Reference channel error (analog inputs only) · Measuring range underflow (analog inputs only) · Measuring range overflow (analog inputs only) · Missing load voltage (analog and digital outputs only) · Missing sensor power supply (digital outputs only) · Fuse tripped (digital outputs only) · Mass error (digital I/Os only) · Excess temperature (digital outputs only) ALARM_8P is used to report "Module removed", "I/O access error", and "Diagnostic interrupt" events to WinCC. The diagnostics interrupt function distinguishes between module and channel errors, whereby each channel is assigned a message ID. Only one incoming/outgoing event can be reported for each channel. As long as an incoming message is queued at a channel, further messages on new events at this channel will be lost. If the event is defined uniquely in the diagnostic information, the corresponding text will be entered in the message. If ambiguous entries exist, the text of the first set bit in the error byte of the diagnostic information will be displayed. When using modules assigned diagnostic functions and more than one error byte for diagnostic information, only the channel xx error text will be output if the error information is not displayed in the first error byte.
148
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.25 MOD_D1: Monitoring up to 16 channels on S7-300/400 SM modules with diagnostic functions
The system verifies during startup that the module is available (plugged in). The module status information that is read here is then available in the form of service output parameters (MOD_INF).
Detailed information about the errors is entered in the DIAG_INF output parameter of data type STRUCT. You will find additional information about this in the reference manual System Software for S7-300/400 System and Standard Functions; Diagnostic Data, Byte 0 to Byte 8, Structure of Channel-Specific Diagnostic Data.
Note
If you run a HART module in HART MODE (Page 517) =16#070C, any HART protocol errors/ configuration changes will be masked by the MOD_D1 driver block, and will not be signaled as channel errors.
Redundancy
The higher-level RACK block monitors the redundancy of DP master systems operating in an H system.
MODE setting You will find additional information about this in the "MODE settings (Page 517)" section.
Note If you change the parameter settings for the MODE_xx inputs at runtime, these changes will not be accepted at the outputs until the ACC_MODE is set to 1.
OMODE Structure You will find additional information in the "OMODE (Page 527)" section.
Valid channel display
The available channels on a module are displayed in the CH_EXIST output by setting a bit in the DWORD, starting at bit 0, for every existing channel. If the bit assigned to a channel = 0, the channel is not available.
Output CH_OK displays the valid channels on a module by setting a bit to TRUE for every valid channel, where bit 0 is assigned to channel 0, etc. If the bit assigned to a channel is 0, the channel is faulty. If a module error occurs, all channels are disrupted.
Addressing
You will find additional information about this in "Addressing (Page 530)".
HART modules with read/write access to the process image are configured in the same way as input modules. The set I/O range must always be identical.
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
149
Family: @System 6.25 MOD_D1: Monitoring up to 16 channels on S7-300/400 SM modules with diagnostic functions
Example: SM 332 AO 2x0/4..20mA HART 332-5TB00-0AB0:
Address input range (HW Config)
544
Address output range (HW Config)
544
LADDR (decimal/hex)
544 / 16#0220
Error handling
The plausibility of input parameters is not checked. You will find additional information about error handling in the "Error information of output parameter MSG_STAT (Page 530)" section.
Service Information
To analyze faults, the module status information entered during startup is read via the MOD_INF structured output parameter. You will find additional information about this in the reference manual System Software for S7-300/400 System and Standard Functions; System Status List, Module Status Information.
Following a diagnostic interrupt, you will also find detailed module diagnostic information in the MODDIAG0 to MODDIAG8 output parameters. You will find additional information in the reference manual System Software for S7-300/400 System and Standard Functions; Diagnostic Data, Byte 0 to Byte 8.
The CHDIAG00 to CHDIAG15 output parameters contain detailed channel-status information. You will find additional information in the reference manual System Software for S7-300/400 System and Standard Functions; Structure of Channel-Specific Diagnostic Data.
The system resets this diagnostic information after a diagnostic interrupt has been reported outgoing (no further channel or module errors are queued).
Startup characteristics
After a restart/initial startup, the system verifies that the module is available under its logical base address. A restart (OB 100) is reported via the LSB in byte 2 of the OMODE_xx (Page 527) outputs.
Overload behavior
The MOD_D1 block counts the OB82 calls. The counter is reset in OB1. If more than two OB82 events occur in succession before the cycle control point is reached (OB1), these events are rejected and the message "OB82 DP master failure: x Rack: y Slot: z" is output.
Time response Not available
150
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.25 MOD_D1: Monitoring up to 16 channels on S7-300/400 SM modules with diagnostic functions
Message response MOD_D1 uses ALARM_8P_1 to report module errors. The function also calls ALARM_8P_2 and ALARM_8P_3 which are intended for channel errors. The inputs DELAY1 and DELAY2 are used to delay the output of I/O access error messages. DELAY1 allows you to enter a time in seconds for which the block will wait for a higher-priority error (rack failure or removal/insertion) following a program execution error (OB 85) before it outputs the message. The message is output only under the condition that no higher-priority error is reported within this delay time. DELAY2 determines the number of seconds the block waits after the higher-priority error has been reported outgoing until it outputs the queued I/O access error as well. Both values are set to 2 seconds by default. The message function can be disabled by setting EN_MSG = FALSE.
Flutter suppression The "Flutter suppression" function is used to delay the outgoing of a message by a configurable period. The flutter time is entered at the channel block at the FlutTmIn parameter. The high byte of the DXCHG parameter of the channel blocks contains the flutter time. Flutter suppression comes into effect when FlutEN = 1 or FlutTmIn > 0 is set at the channel block. There is only one flutter message per module. The delay times and fault messages are channelspecific. The fault messages are extended by at least the delay time. Flutter exists if the fault messages "Outgoing" and then "Incoming" are present within the delay time. The last fluttering channel and its set delay time deactivates the flutter message.
Operator control and monitoring If asset management is used in the project and the diagnostic screens have been generated, the faceplate can be called via its block icon. For additional information, refer to the "Process Control System PCS 7; Maintenance Station" manual.
Additional information For additional information, refer to the sections: Message texts and associated values of MOD_D1 (Page 154) Maintenance status MS (Page 533) You can also find additional information on this in PCS 7 Advanced Process Library > Basics of APL > General functions of the blocks > Operating, monitoring and reporting > Release for maintenance
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
151
Family: @System 6.25 MOD_D1: Monitoring up to 16 channels on S7-300/400 SM modules with diagnostic functions
6.25.2
I/Os of MOD_D1/MOD_D2
The MOD_D1 and MOD_D2 block I/Os are identical, with the exception of the number of MODE_xx and OMODE_xx. The number of monitored channels determines the corresponding number of I/O parameters (xx).
The factory setting of the block display in the CFC is identified in the "I/O" column: I/O name bold = I/O visible, I/O name normal = I/O not visible.
You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15)".
Input parameters
I/O (parameter) CHAN_NUM DELAY1 DELAY2 DIAG_BUF
EN_MSG EV_IDx LADDR MODE_xx MS MS_REQ RACK_NO SLOT_NO SUBN_TYP SUBN1_ID SUBN2_ID
Meaning
Data type
Total number of channels -1 Alarm delay 1 (s) Alarm delay 2 (s) Entry in diagnostic buffer (relevant for maintenance personnel) 1 = Enable message Message number (x = 1 - 3) Logical address of the module Operating mode channel xx (xx = 00 - 15 / 00 - 31) Maintenance status 1 = Request maintenance release Rack number Slot number 1 = external DP interface ID of the primary DP master system ID of the redundant DP master system
INT INT INT BOOL
BOOL DWORD INT DWORD DWORD BOOL BYTE BYTE BOOL BYTE BYTE
Default
0 2 2 0
1 0 0 0 0 0 0 0 0 255 255
Output parameters
I/O (parameter) CH_ACTIVE
CH_EXIST CH_OK DIAG_INF DM_ACTIVE DXCHG_xx DXCHG1_xx EXT_STAT
Meaning
Data type
Channel active
DWORD
Channel exists Channel OK System structure: Diagnostic information Fault delay 1st internal data exchange channel for channel block 2nd internal data exchange channel for channel block Release for maintenance - extended status
DWORD DWORD STRUCT DWORD DWORD DWORD DWORD
Default
16#000 00000 0 0 0 16#0 0 0 0
152
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.25 MOD_D1: Monitoring up to 16 channels on S7-300/400 SM modules with diagnostic functions
I/O (parameter) EXT_STAT_A
FS_ACTIVE
MOD_INF MS_XCHG_xx
MSG_ACKx MSGSTATx O_MS OMODE_xx QERR QMODF QPERAF QRACKF
Meaning
Data type
Extended status - Application Application data transfer active Flutter suppression
DWORD DWORD
System structure: Module parameter Maintenance Status - Data exchange channel (xx = 00 - 63) Message acknowledgment (x = 1 - 3) Message error information (x = 1 - 3) Maintenance status Channel mode (xx = 00 - 15/00 - 31) 1 = program error 1 = module removed/defective 1 = I/O access error 1 = higher-level error
STRUCT DWORD
WORD WORD DWORD DWORD BOOL BOOL BOOL BOOL
Default
0
16#000 00000
0
0 0 0 0 1 0 0 0
In/out parameters
I/O (parameter) ACC_MODE CPU_DIAG RAC_DIAG
Meaning
1 = accept MODE settings System structure: CPU diagnostics System structure: Rack diagnostics
Data type
BOOL STRUCT STRUCT
Default 0
Additional information For additional information, refer to the sections: Message texts and associated values of MOD_D1 (Page 154) Message texts and associated values of MOD_D2 (Page 174) Maintenance status MS (Page 533)
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
153
Family: @System 6.25 MOD_D1: Monitoring up to 16 channels on S7-300/400 SM modules with diagnostic functions
6.25.3
Message texts and associated values of MOD_D1
Assignment of message text and message class
Message block ALARM_8P
EV_ID1
Message number
1
2
3 4 5 6 7 8
EV_ID2
1
... ...
8
EV_ID3
1
... ...
8
Default message text
Module @1%d@/@2%d@/@3%d@: Failure Module @1%d@/@2%d@/@3%d@: Maintenance demanded (external) Module @1%d@/@2%d@/@3%d@: @5W%t#MOD_D1_TXT@ Module @1%d@/@2%d@/@3%d@: Multiple diagnostic interrupt Module @1%d@/@2%d@/@3%d@: @4W%t#MOD_D1_TXT@
Module @1%d@/@2%d@/@3%d@: @5W%t#MOD_D1_TXT@ Module @1%d@/@2%d@/@3%d@: Maintenance required (external) Module @1%d@/@2%d@/@3%d@: Error channel 00 @4W %t#MOD_D1_TXT@ ... ... Module @1%d@/@2%d@/@3%d@: Error channel 07 @4W %t#MOD_D1_TXT@ Module @1%d@/@2%d@/@3%d@: Error channel 08 @4W %t#MOD_D1_TXT@ ... ... Module @1%d@/@2%d@/@3%d@: Error channel 15 @4W %t#MOD_D1_TXT@
Message class
PLC Process Control Message Failure PLC Process Control Message Error
PLC Process Control Message Failure PLC Process Control Message Failure PLC Process Control Message Failure No message PLC Process Control Message Error Preventative Maintenance Standard
PLC Process Control Message Failure
... ... PLC Process Control Message Failure
PLC Process Control Message Failure
... ... PLC Process Control Message Failure
You will find the message texts and their text numbers in "Text library for MOD_D1 (Page 539)".
Assignment of associated values
Message block ALARM_8P
EV_ID1
Associ- ated value
1
2
Block parameters
MOD_INF.SUBN_ID MOD_INF.RACK_NO
Meaning
DP master system ID (byte) Rack/station number (byte)
154
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.26 MOD_D16_PN: Monitoring S7-300 SM modules with up to 16 channels and with diagnostics functions
Message block ALARM_8P
Associ- ated value
3
4
5
Block parameters MOD_INF.SLOT_NO
EV_ID2
1
MOD_INF.SUBN_ID
2
MOD_INF.RACK_NO
3
MOD_INF.SLOT_NO
4
EV_ID3
1
MOD_INF.SUBN_ID
2
MOD_INF.RACK_NO
3
MOD_INF.SLOT_NO
4
Meaning
Slot number (byte) Text number (message 5) from MOD_D1_TXT Text number (message 3) from MOD_D1_TXT
DP master system ID (byte) Rack/station number (byte) Slot number (byte) Text number (messages 1 - 8) from MOD_D1_TXT
DP master system ID (byte) Rack/station number (byte) Slot number (byte) Text number (messages 1 - 8) from MOD_D1_TXT
See also
Message Classes (Page 531)
6.26
MOD_D16_PN: Monitoring S7-300 SM modules with up to 16 channels and with diagnostics functions
6.26.1
Description of MOD_D16_PN
Object name (type + number) FB 198 · I/Os of MOD_D16_PN/MOD_D24_PN (Page 156)
Area of application
Block MOD_D16_PN monitors S7-300 SM modules with a maximum of 16 channels and with diagnostics functions.
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
155
Family: @System 6.26 MOD_D16_PN: Monitoring S7-300 SM modules with up to 16 channels and with diagnostics functions
6.26.2
I/Os of MOD_D16_PN/MOD_D24_PN
The factory setting of the block display in the CFC is identified in the "I/O" column:
I/O name bold = I/O visible, I/O name normal = I/O not visible.
You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15)".
Input parameters
I/O (parameter) CHAN_NUM DELAY1 DELAY2 DIAG_BUF
EN_MSG EV_IDx
FEATURE_xx FEATURE_yy LADDR LADDR1
MODE_xx
MS MS_REQ RACK_NO SLOT_NO SUBSL_NO SUBN_TYP SUBN1_ID SUBN2_ID
Meaning
Data type Default
Total number of channels -1
INT
0
Alarm delay 1 (s)
INT
2
Alarm delay 2 (s)
INT
2
Entry in diagnostic buffer (relevant for maintenance BOOL
0
personnel)
1 = Enable message
BOOL
1
Message number ALARM_8P_x (x = 1 - 2/1 - 3/1 - 4, assigned by the ES)
DWORD
0
Feature parameter (xx = 01 - 04)
WORD
0
Feature parameter (yy = 05 - 10)
DWORD
0
Logic input address of the module
INT
0
Logical output address of the module (if output ad- INT
0
dress is not the same as input address).
Operating mode channel xx (xx = 00 - 07/00 - 15/00 - DWORD
0
23)
Maintenance status
DWORD
0
1 = Request maintenance release
BOOL
0
Rack number
BYTE
0
Slot number
BYTE
0
Subslot number
BYTE
0
1 = external PN interface
BOOL
0
PN IO system 1 ID (100 - 115)
BYTE
255
PN IO system 2 ID (100 - 115)
BYTE
255
Output parameters
I/O (parameter) CH_ACTIVE
CH_EXIST CH_OK DIAG_INFx DXCHG_xx
Meaning
Data type Default
Channel active
DWORD
Channel exists
DWORD
Channel OK
DWORD
System structure: Diagnostic information
STRUCT
1st internal data exchange channel for channel block DWORD
16#0000000 0 0 0 0 0
156
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.26 MOD_D16_PN: Monitoring S7-300 SM modules with up to 16 channels and with diagnostics functions
I/O (parameter) DXCHG1_xx
EXT_STATx EXT_STAT_A
FS_ACTIVE
MOD_INF MS_XCHG_xx
MSG_ACKx MSGSTATx O_MS OMODE_xx
QERR QMODF QPERAF QRACKF
Meaning
Data type Default
2nd internal data exchange channel for channel block
Release for maintenance - extended status
Extended status - Application Application data transfer active
Flutter suppression active
DWORD DWORD DWORD
DWORD
System structure: Module parameter Maintenance Status - Data exchange channel (xx = 00 - 63) Message acknowledgment (x = 1 - 2/1 - 3/1 - 4) Message error information (x = 1 - 2/1 - 3/1 - 4) Maintenance status Operating mode channel xx (xx = 00 - 07/00 - 15/00 - 23) 1 = program error 1 = module removed/defective 1 = I/O access error 1 = higher-level error
STRUCT DWORD
WORD WORD DWORD DWORD
BOOL BOOL BOOL BOOL
0
0 0
16#0000000 0
0
0 0 0 0
1 0 0 0
In/out parameters
I/O (parameter) ACC_MODE CPU_DIAG_PN RAC_DIAG
Meaning
1 = accept MODE settings System structure: CPU diagnostics System structure: Rack diagnostics
Data type
BOOL STRUCT STRUCT
Default 0
Additional information For additional information, refer to the sections: Message texts and associated values of MOD_D16_PN/MOD_D24_PN (Page 158) Maintenance status MS (Page 533)
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
157
Family: @System 6.26 MOD_D16_PN: Monitoring S7-300 SM modules with up to 16 channels and with diagnostics functions
6.26.3
Message texts and associated values of MOD_D16_PN/MOD_D24_PN
Assignment of message text and message class The process control messages of ALARM_8P with EV_ID1 are assigned as follows:
Message block ALARM_8P
EV_ID1
Message number
1
2
3
4 5
6 7
8
Default message text
Message class
Module @1%d@/@2%d@/@3%d@/ @6%d@: Failure
Module @1%d@/@2%d@/@3%d@/ @6%d@:@5W%t#MOD_n_TXT@
Module @1%d@/@2%d@/@3%d@/ @6%d@:
@5W%t#MOD_n_TXT@ (n=16, 24)
Module @1%d@/@2%d@/@3%d@/ @6%d@: Multiple diagnostics interrupt
Module @1%d@/@2%d@/@3%d@/ @6%d@:
@4W%t#MOD_n_TXT@ (n=16, 24)
Module @1%d@/@2%d@/@3%d@/ @6%d@: maintenance required
Module @1%d@/@2%d@/@3%d@/ @6%d@:
Maintenance demanded (external)
No message module @1%d@/@2%d@/ @3%d@/@6%d@:
Maintenance required (external)
PLC Process Control Message Failure PLC Process Control Message Error PLC Process Control Message Failure
PLC Process Control Message Error PLC Process Control Message Failure
Preventative Maintenance Standard PLC Process Control Message Error
Preventative Maintenance Standard
Associated values of ALARM_8P with EV_ID1
Associated value 1 2 3 4
5
6
Block parameter
ID of the PN IO system Rack/station number Slot number Text number (message 5) from MOD_D16_PN_TXT / MOD_D24_PN_TXT Text number (message 3) from MOD_D16_PN_TXT / MOD_D24_PN_TXT Subslot number
Data type BYTE BYTE BYTE BYTE
BYTE
BYTE
The process control messages of ALARM_8P with EV_ID2 are assigned as follows:
158
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.26 MOD_D16_PN: Monitoring S7-300 SM modules with up to 16 channels and with diagnostics functions
Message block ALARM_8P
EV_ID2
Message number
1
2
3
4
5
6
7
8
Default message text
Message class
Module @1%d@/@2%d@/@3%d@/ @5%d@: Error channel 00 @4W%t# MOD_D16_PN_TXT /MOD_D24_PN_TXT @
Module @1%d@/@2%d@/@3%d@/ @5%d@: Error channel 01 @4W%t# MOD_D16_PN_TXT /MOD_D24_PN_TXT @
Module @1%d@/@2%d@/@3%d@/ @5%d@: Error channel 02 @4W%t# MOD_D16_PN_TXT /MOD_D24_PN_TXT @
Module @1%d@/@2%d@/@3%d@/ @5%d@: Error channel 03 @4W%t# MOD_D16_PN_TXT /MOD_D24_PN_TXT @
Module @1%d@/@2%d@/@3%d@/ @5%d@: Error channel 04 @4W%t# MOD_D16_PN_TXT /MOD_D24_PN_TXT @
Module @1%d@/@2%d@/@3%d@/ @5%d@: Error channel 05 @4W%t# MOD_D16_PN_TXT /MOD_D24_PN_TXT @
Module @1%d@/@2%d@/@3%d@/ @5%d@: Error channel 06 @4W%t# MOD_D16_PN_TXT /MOD_D24_PN_TXT @
Module @1%d@/@2%d@/@3%d@/ @5%d@: Error channel 07 @4W%t# MOD_D16_PN_TXT /MOD_D24_PN_TXT @
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
Associated values of ALARM_8P with EV_ID2
Associated value 1 2 3 4 5
Block parameter ID of the PN IO system Rack/station number Slot number Text number from MOD_D16_PN_TXT /MOD_D24_PN_TXT Subslot number
Data type BYTE BYTE BYTE BYTE BYTE
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
159
Family: @System 6.26 MOD_D16_PN: Monitoring S7-300 SM modules with up to 16 channels and with diagnostics functions
The process control messages of ALARM_8P with EV_ID3 are assigned as follows:
Message block ALARM_8P
EV_ID3
Message number
1
2
3
4
5
6
7
8
Default message text
Message class
Module @1%d@/@2%d@/@3%d@/ @5%d@: Error channel 08 @4W%t# MOD_D16_PN_TXT /MOD_D24_PN_TXT @
Module @1%d@/@2%d@/@3%d@/ @5%d@: Error channel 09 @4W%t# MOD_D16_PN_TXT /MOD_D24_PN_TXT @
Module @1%d@/@2%d@/@3%d@/ @5%d@: Error channel 10 @4W%t# MOD_D16_PN_TXT /MOD_D24_PN_TXT @
Module @1%d@/@2%d@/@3%d@/ @5%d@: Error channel 11 @4W%t# MOD_D16_PN_TXT /MOD_D24_PN_TXT @
Module @1%d@/@2%d@/@3%d@/ @5%d@: Error channel 12 @4W%t# MOD_D16_PN_TXT /MOD_D24_PN_TXT @
Module @1%d@/@2%d@/@3%d@/ @5%d@: Error channel 13 @4W%t# MOD_D16_PN_TXT /MOD_D24_PN_TXT @
Module @1%d@/@2%d@/@3%d@/ @5%d@: Error channel 14 @4W%t# MOD_D16_PN_TXT /MOD_D24_PN_TXT @
Module @1%d@/@2%d@/@3%d@/ @5%d@: Error channel 15 @4W%t# MOD_D16_PN_TXT /MOD_D24_PN_TXT @
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
Associated values of ALARM_8P with EV_ID3
Associated value 1 2 3 4 5
Block parameter ID of the PN IO system Rack/station number Slot number Text number from MOD_D16_PN_TXT /MOD_D24_PN_TXT Subslot number
Data type BYTE BYTE BYTE BYTE BYTE
160
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.26 MOD_D16_PN: Monitoring S7-300 SM modules with up to 16 channels and with diagnostics functions
Process control messages for ALARM_8P with EV_ID4 are assigned as follows:
Message block ALARM_8P
EV_ID_4
Message number
1
2
3
4
5
6
7
8
Default message text
Module @1%d@/@2%d@/@3%d@/ @5%d@: Error channel 16 @4W%t# MOD_D24_PN_TXT @
Module @1%d@/@2%d@/@3%d@/ @5%d@: Error channel 17 @4W%t# MOD_D24_PN_TXT @
Module @1%d@/@2%d@/@3%d@/ @5%d@: Error channel 18 @4W%t# MOD_D24_PN_TXT @
Module @1%d@/@2%d@/@3%d@/ @5%d@: Error channel 19 @4W%t# MOD_D24_PN_TXT @
Module @1%d@/@2%d@/@3%d@/ @5%d@: Error channel 20 @4W%t# MOD_D24_PN_TXT @
Module @1%d@/@2%d@/@3%d@/ @5%d@: Error channel 21 @4W%t# MOD_D24_PN_TXT @
Module @1%d@/@2%d@/@3%d@/ @5%d@: Error channel 22 @4W%t# MOD_D24_PN_TXT @
Module @1%d@/@2%d@/@3%d@/ @5%d@: Error channel 23 @4W%t# MOD_D24_PN_TXT @
Message class
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
Associated values of ALARM_8P with EV_ID4
Associated value 1 2 3 4 5
Block parameter ID of the PN IO system Rack/station number Slot number Text number from MOD_D24_PN_TXT Subslot number
Data type BYTE BYTE BYTE BYTE BYTE
You can find the message texts and their text numbers in the section Text library for MOD_D8_PN (FB197) / MOD_D16_PN (FB198) / MOD_D24_PN (FB199) / MOD_ENME (FB 419) (Page 542).
You can find additional information in the section: Message Classes (Page 531).
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
161
Family: @System 6.27 MOD_D16_S7P: Diagnostic module check (<=16 channels)
6.27
MOD_D16_S7P: Diagnostic module check (<=16 channels)
6.27.1
Description of MOD_D16_S7P
Object name (type + number) FB 434 · I/Os of MOD_D16_S7P (Page 162)
Area of application
The MOD_D16_S7P block creates the device specific DP S7+ diagnostics information for modules with 16 channels.
Calling OBs
The cyclic OB 1 and OB 82, OB 83, OB 85, OB 86 and OB 100.
Use in CFC
The following actions are executed automatically with the "Generate module drivers" CFC function:
· If a module with > 8 and 16 channels is available in HW Configuration, an instance of the diagnostic function block MOD_D16_S7P is added to the system charts of the project.
· Information from HW configuration is read and the input parameters of MOD_D16_S7P are parameterized correspondingly.
The MOD_D16_S7P gets connected with the corresponding channel blocks of the IO module.
Startup characteristics Initialization of the ALARM_8P blocks.
6.27.2
I/Os of MOD_D16_S7P
I/Os of MOD_D8_S7P The factory setting of the block display in the CFC is identified in the "I/O" column.
I/O name bold = I/O visible, I/O name normal = I/O not visible.
You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15)".
162
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.27 MOD_D16_S7P: Diagnostic module check (<=16 channels)
Input parameters
I/O (parameter) CHAN_NUM DELAY1 DELAY2 DIAG_BUF
EN_MSG EV_ID1 EV_ID2 FEATURE LADDR LADDR1 MODE_xx MS MS_REQ RACK_NO SLOT_NO SUBN_TYP SUBN1_ID SUBN2_ID
Meaning
Type
Total number of channels -1
INT
Interrupt delay 1 (s)
INT
Interrupt delay 2 (s)
INT
Entry in diagnostic buffer (relevant for maintenance person- BOOL nel)
1 = Enable message
BOOL
Message number 1
DWORD
Message number 2
DWORD
Feature parameter
DWORD
Logical address of the module
INT
Reserve
INT
Channel xx mode (xx = 00...15)
DWORD
Maintenance status
DWORD
1 = Request maintenance release
BOOL
Rack number
BYTE
Slot number
BYTE
1 = External DP interface
BOOL
DP master system 1 ID
BYTE
DP master system 2 ID
BYTE
Default 0 2 2 0
1 16#0 16#0 0 -1 -1 0 16#0 0 0 0 0 255 255
Out parameters
I/O (parameter) CH_ACTIVE CH_EXIST CH_OK DIAG_INF DM_ACTIVE DXCHG_xx
DXCHG1_xx
EXT_STAT
EXT_STAT_A FS_ACTIVE MOD_INF MS_XCHG_xx
MSGSTAT1 MSGSTAT2 MSG_ACK1
Meaning
Type
Channel active
DWORD
Channel exists
DWORD
Channel OK
DWORD
System structure: Diagnostic information STRUCT
Fault delay
DWORD
1st internal data exchange channel for channel block (xx = 00...15)
DWORD
2nd internal data exchange channel for DWORD channel block (xx = 00...15)
Release for maintenance - extended sta- DWORD tus
Extended Status Application
DWORD
Flutter suppression
DWORD
System structure: Module parameter
STRUCT
Maintenance Status - Data exchange channel (xx = 00...07)
DWORD
Message failure 1
WORD
Message failure 2
WORD
Message acknowledged 1
WORD
Default 0 0 0
0 16#0
16#0
0
0 0
0
0 0 0
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
163
Family: @System 6.27 MOD_D16_S7P: Diagnostic module check (<=16 channels)
I/O (parameter) MSG_ACK2 OMODE_xx O_MS QREC_VAL QREC_ERR QSTATUS QERR QMODF QPERAF QRACKF
Meaning Message acknowledged 2 Channel xx mode (xx = 00...15) Maintenance status 1 = Received new data record 1 = Error read data record Status read data record 1 = program error 1 = Module pulled/defective 1 = I/O access error 1 = higher level error
In/out parameters
I/O (parameter) Meaning
ACC_MODE CPU_DIAG RAC_DIAG
1 = Apply MODE settings System structure: CPU diagnostics System structure: RACK diagnostics
Type WORD DWORD DWORD BOOL BOOL DWORD BOOL BOOL BOOL BOOL
Default 0 0 0 0 0 0 1 0 0 0
Type
BOOL STRUCT STRUCT
De- fault 0
0
6.27.3
Message texts and associated values of MOD_D16_S7P
Assignment of message text and message class The process control messages of ALARM_8P with EV_ID1 are assigned as follows:
Message block ALARM_8P
EV_ID1
Mes- Event sage number
Message class
1
Module @1%d@/@2%d@/@3%d@: Maintenance PLC Process Control
alarm
Message - Failure
2
Module @1%d@/@2%d@/@3%d@: Maintenance de- PLC Process Control
manded (external)
Message - Error
3
Module @1%d@/@2%d@/@3%d@: @5W
%t#MOD_D16_S7P_TXT@
PLC Process Control Message - Failure
4
Module @1%d@/@2%d@/@3%d@: Maintenance de- PLC Process Control
manded
Message - Error
5
Module @1%d@/@2%d@/@3%d@: @4W
%t#MOD_D16_S7P_TXT@
PLC Process Control Message - Failure
6
Module @1%d@/@2%d@/@3%d@: Maintenance re- Preventative Mainte-
quired
nance - Standard
7
Module @1%d@/@2%d@/@3%d@: @5W
%t#MOD_D16_S7P_TXT@
PLC Process Control Message - Error
8
Module @1%d@/@2%d@/@3%d@: Maintenance re- Preventative Mainte-
quired (external)
nance - Standard
164
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.27 MOD_D16_S7P: Diagnostic module check (<=16 channels)
Associated values of ALARM_8P with EV_ID1
Associated value 1 2 3
Block parameter DP master system number Rack number/Station number Slot number
Data type BYTE BYTE BYTE
The process control messages of ALARM_8P with EV_ID2 are assigned as follows:
Message block ALARM_8P
EV_ID2
Message number
Event
Message class
1
Module @1%d@/@2%d@/@3%d@: Error chan- PLC Process Control
nel 00 @4W%t#MOD_ D16_S7P_TXT@
Message - Failure
2
Module @1%d@/@2%d@/@3%d@: Error chan- PLC Process Control
nel 01 @4W%t#MOD_ D16_S7P_TXT@
Message - Failure
3
Module @1%d@/@2%d@/@3%d@: Error chan- PLC Process Control
nel 02 @4W%t#MOD_ D16_S7P_TXT@
Message - Failure
4
Module @1%d@/@2%d@/@3%d@: Error chan- PLC Process Control
nel 03 @4W%t#MOD_ D16_S7P_TXT@
Message - Failure
5
Module @1%d@/@2%d@/@3%d@: Error chan- PLC Process Control
nel04 @4W%t#MOD_ D16_S7P_TXT@
Message - Failure
6
Module @1%d@/@2%d@/@3%d@: Error chan- PLC Process Control
nel05 @4W%t#MOD_ D16_S7P_TXT@
Message - Failure
7
Module @1%d@/@2%d@/@3%d@: Error chan- PLC Process Control
nel06 @4W%t#MOD_ D16_S7P_TXT@
Message - Failure
8
Module @1%d@/@2%d@/@3%d@: Error chan- PLC Process Control
nel 07 @4W%t#MOD_ D16_S7P_TXT@
Message - Failure
Associated values of ALARM_8P with EV_ID2
Associated value 1 2 3 4
Block parameters DP master system number Rack number/Station number Slot number Text number from MOD_ D16_S7P_TXT
Data type BYTE BYTE BYTE BYTE
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
165
Family: @System 6.28 MOD_D2: Monitoring up to 32 channels of S7-300/400 SM modules with diagnostic functions
The process control messages of ALARM_8P with EV_ID3 are assigned as follows:
Message block ALARM_8P
EV_ID3
Message number
Event
Message class
1
Module @1%d@/@2%d@/@3%d@: Error Chan- PLC Process Control
nel 08 @4W%t#MOD_ D16_S7P_TXT@
Message - Failure
2
Module @1%d@/@2%d@/@3%d@: Error Chan- PLC Process Control
nel 09 @4W%t#MOD_ D16_S7P_TXT@
Message - Failure
3
Module @1%d@/@2%d@/@3%d@: Error Chan- PLC Process Control
nel 10 @4W%t#MOD_ D16_S7P_TXT@
Message - Failure
4
Module @1%d@/@2%d@/@3%d@: Error Chan- PLC Process Control
nel 11 @4W%t#MOD_ D16_S7P_TXT@
Message - Failure
5
Module @1%d@/@2%d@/@3%d@: Error Chan- PLC Process Control
nel 12 @4W%t#MOD_ D16_S7P_TXT@
Message - Failure
6
Module @1%d@/@2%d@/@3%d@: Error Chan- PLC Process Control
nel13 @4W%t#MOD_ D16_S7P_TXT@
Message - Failure
7
Module @1%d@/@2%d@/@3%d@: Error Chan- PLC Process Control
nel14 @4W%t#MOD_ D16_S7P_TXT@
Message - Failure
8
Module @1%d@/@2%d@/@3%d@: Error Chan- PLC Process Control
nel15 @4W%t#MOD_ D16_S7P_TXT@
Message - Failure
Associated values of ALARM_8P with EV_ID3
Associated value 1 2 3 4
Block parameters DP master system number Rack number/Station number Slot number Text number from MOD_ D16_S7P_TXT
Data type BYTE BYTE BYTE BYTE
You can find the message texts and their text numbers in the section: Text library for MOD_ D8_S7P, MOD_ D16_S7P (Page 545).
You can find additional information in the section: Message Classes (Page 531).
6.28
MOD_D2: Monitoring up to 32 channels of S7-300/400 SM modules with diagnostic functions
6.28.1
Description of MOD_D2
Object name (type + number) FB 94 · MOD_D2 block I/Os (Page 172)
166
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.28 MOD_D2: Monitoring up to 32 channels of S7-300/400 SM modules with diagnostic functions
Area of application Block MOD_D2 monitors up to 32 channels on S7-300/400 SM modules with diagnostic capability (no mixed modules). H systems support only the modules installed in switched racks.
Calling OBs
The block must be installed in the run sequence in the following OBs:
OB 1 OB 82 OB 83 OB 85 OB 86 OB 100
Cyclic program Diagnostic interrupt Insert/remove module interrupt Program execution error Rack failure Warm restart
Use in CFC
The following actions are executed automatically with the "Generate module drivers" CFC function:
· The MOD_D2 block is installed in its runtime group downstream of the RACK block runtime group in the above-mentioned OBs.
· The MODE_xx (mode of the channels xx of the module), SUBN1_ID, SUBN2_ID, and SUBN_TYP inputs are configured.
· The logical base address LADDR of the module is configured.
· The OUT structures CPU_DIAG of the OB_BEGIN block and RAC_DIAG of the RACK block are interconnected with the IN_OUT structures of the same name of MOD_D2.
· The EN input is interconnected with the output of an AND block. Its inputs are interconnected with the outputs EN_SUBx (x = number of the DP master system) of the OB_BEGIN block, EN_Rxxx (xxx = rack/station number) of the SUBNET block and EN_Mxx (xx = module number) of the RACK block.
· The output parameter of DXCHG_xx is interconnected with the following channel block at the DataXchg parameter.
· The output parameter of O_MS is interconnected with the following channel block at the MS parameter.
Function and method of operation
Block MOD_D2 analyzes all events that affect a module and its channels acyclically. It generates a channel-specific MODE (Page 517) and value status for the signal processing blocks. ALARM_8P is used to report these events. The message function can be disabled.
The block is enabled by the higher-level RACK block at runtime. The event to be evaluated is stored in the CPU_DIAG start and diagnostic information of the OB_BEGIN block. There is a MODE_xx input for each signal channel of the module. The module channel configuration data created in HW Config is reported here. The function writes MODE_xx to the low word of the OMODE_xx (Page 527) output parameter. This occurs only during startup or if you set
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
167
Family: @System 6.28 MOD_D2: Monitoring up to 32 channels of S7-300/400 SM modules with diagnostic functions
ACC_MODE = TRUE. The current channel value status is written to the most significant byte. If the result is positive, the system sets OMODE_xx = 16#80xxxxxx. The following events lead to the value status "invalid value due to higher-level error" (OMODE_xx = 16#40xxxxxx): · Events that are evaluated by the RACK block:
Rack failure (OB 86) (output parameter QRACKF = TRUE) · Events that are evaluated by the MOD block:
Program execution error (OB 85) (output parameter QPERAF = TRUE) Module removed (OB 83) (output parameter QMODF = TRUE) Diagnostic interrupt (OB 82) Distinguishing between module errors and channel errors
The following events are module errors (QMODF = TRUE output parameter): · External auxiliary voltage missing · Front connector missing · Module not configured · Wrong parameter in module · Wrong/missing module · Communication error at a CPU module · Timeout (watchdog) · Loss of internal power at a module · Rack failure · CPU failure · EPROM error · RAM error · ADC/DAC error · Fuse tripped
The following events are channel errors (value status "invalid value", OMODE_xx = 16#00xxxx): · Configuration/parameter assignment error · Common-mode errors (analog I/Os only) · Short-circuit to P · Short circuit to M · Interruption at the output transistor · Wire break · Reference channel error (analog inputs only) · Measuring range underflow (analog inputs only)
168
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System
6.28 MOD_D2: Monitoring up to 32 channels of S7-300/400 SM modules with diagnostic functions
· Measuring range overflow (analog inputs only)
· Missing load voltage (analog and digital outputs only)
· Missing sensor power supply (digital outputs only)
· Fuse tripped (digital outputs only)
· Mass error (digital I/Os only)
· Excess temperature (digital outputs only)
ALARM_8P is used to report "Module removed", "I/O access error", and "Diagnostic interrupt" events to WinCC.
The diagnostics interrupt function distinguishes between module and channel errors, whereby each channel is assigned a message ID. Only one incoming or outgoing event can be reported for each channel. As long as an incoming message is queued at a channel, further messages on new events at this channel will be lost.
If the event is defined uniquely in the diagnostic information, the corresponding text will be entered in the message. If ambiguous entries exist, the text of the first set bit in the error byte of the diagnostic information will be displayed. When using modules assigned diagnostic functions and more than one error byte for diagnostic information, only the channel xx error text will be output if the error information is not displayed in the first error byte.
The system verifies during startup that the module is available (plugged in). The module status information read here makes this data available in the form of service output parameters (MOD_INF).
Detailed information about the errors is entered in the DIAG_INF output parameter of data type STRUCT. You will find additional information about this in the reference manual System Software for S7-300/400 System and Standard Functions; Diagnostic Data, Byte 0 to Byte 8, Structure of Channel-Specific Diagnostic Data.
Redundancy
The block supports segment redundancy of CPU 417H for distributed I/Os. The SUBN1_ID (connection to CPU 0) and SUBN2_ID (connection to CPU 1) inputs are configured with the numbers of the redundant segments. If there is no segment redundancy, the remaining input must be set to the (default) value 16#FF.
MODE setting You will find additional information about this in the "MODE settings (Page 517)" section.
Note If you change the parameter settings for the MODE_xx inputs at runtime, these changes will not be accepted at the outputs until the ACC_MODE is set to 1.
OMODE Structure You will find additional information in the "OMODE (Page 527)" section.
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
169
Family: @System 6.28 MOD_D2: Monitoring up to 32 channels of S7-300/400 SM modules with diagnostic functions
Valid channel display The available channels on a module are displayed in the CH_EXIST output by setting a bit in the DWORD, starting at bit 0, for every existing channel. If the bit assigned to a channel = 0, the channel is not available.
Output CH_OK displays the valid channels on a module by setting a bit to TRUE for every valid channel, where bit 0 is assigned to channel 0, etc. If the bit assigned to a channel is 0, the channel is faulty. If a module error occurs, all channels are disrupted.
Addressing
You will find additional information about this in the "Addressing (Page 530)" section.
Error handling
The plausibility of input parameters is not checked. You will find additional information about error handling in the "Error information of output parameter MSG_STAT (Page 530)" section.
Service Information
To analyze faults, the module status information entered during startup is read via the MOD_INF structured output parameter. You will find additional information about this in the reference manual System Software for S7-300/400 System and Standard Functions; System Status List, Module Status Information.
Following a diagnostic interrupt, you will also find detailed module diagnostic information in the MODDIAG0 to MODDIAG10 output parameters. You will find additional information in the reference manual System Software for S7-300/400 System and Standard Functions; Diagnostic Data, Byte 0 to Byte 10.
The CHDIAG00 to CHDIAG31 output parameters contain detailed channel status information. You will find additional information in the reference manual System Software for S7-300/400 System and Standard Functions; Structure of Channel-Specific Diagnostic Data.
The system resets this diagnostic information after a diagnostic interrupt has been reported outgoing (no further channel or module errors are queued).
Startup characteristics
After a restart/initial startup, the system verifies that the module is available under its logical base address. A restart (OB 100) is reported via the LSB in byte 2 of the OMODE_xx (Page 527) outputs.
Time response Not available
170
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.28 MOD_D2: Monitoring up to 32 channels of S7-300/400 SM modules with diagnostic functions
Message response MOD_D2 uses ALARM_8P_1 to report module errors. In addition, the error blocks ALARM_8P_2, ALARM_8P_3, ALARM_8P_4 and ALARM_8P_5 intended for channel errors are called. The inputs DELAY1 and DELAY2 are used to delay the output of I/O access error messages. DELAY1 allows you to enter a time in seconds for which the block will wait for a higher-priority error (rack failure or removal/insertion) following a program execution error (OB 85) before it outputs the message. The message is output only under the condition that no higher-priority error is reported within this delay time. DELAY2 determines the number of seconds the block waits after the higher-priority error has been reported outgoing until it outputs the queued I/O access error as well. Both values are set to 2 seconds by default. The message function can be disabled by setting EN_MSG = FALSE.
Flutter suppression The "Flutter suppression" function is used to delay the outgoing of a message by a configurable period. The flutter time is entered at the channel block at the FlutTmIn parameter. The high byte of the DXCHG parameter of the channel blocks contains the flutter time. Flutter suppression comes into effect when FlutEN = 1 or FlutTmIn > 0 is set at the channel block. There is only one flutter message per module. The delay times and fault messages are channelspecific. The fault messages are extended by at least the delay time. Flutter exists if the fault messages "Outgoing" and then "Incoming" are present within the delay time. The last fluttering channel and its set delay time deactivates the flutter message.
Operator control and monitoring If asset management is used in the project and the diagnostic screens have been generated, the faceplate can be called via its block icon. For additional information, refer to the "Process Control System PCS 7; Maintenance Station" manual.
Additional information For additional information, refer to the sections: Message texts and associated values of MOD_D2 (Page 174) Maintenance status MS (Page 533) You can also find additional information on this in PCS 7 Advanced Process Library > Basics of APL > General functions of the blocks > Operating, monitoring and reporting > Release for maintenance
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
171
Family: @System 6.28 MOD_D2: Monitoring up to 32 channels of S7-300/400 SM modules with diagnostic functions
6.28.2
I/Os of MOD_D1/MOD_D2
The MOD_D1 and MOD_D2 block I/Os are identical, with the exception of the number of MODE_xx and OMODE_xx. The number of monitored channels determines the corresponding number of I/O parameters (xx).
The factory setting of the block display in the CFC is identified in the "I/O" column: I/O name bold = I/O visible, I/O name normal = I/O not visible.
You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15)".
Input parameters
I/O (parameter) CHAN_NUM DELAY1 DELAY2 DIAG_BUF
EN_MSG EV_IDx LADDR MODE_xx MS MS_REQ RACK_NO SLOT_NO SUBN_TYP SUBN1_ID SUBN2_ID
Meaning
Data type
Total number of channels -1 Alarm delay 1 (s) Alarm delay 2 (s) Entry in diagnostic buffer (relevant for maintenance personnel) 1 = Enable message Message number (x = 1 - 3) Logical address of the module Operating mode channel xx (xx = 00 - 15 / 00 - 31) Maintenance status 1 = Request maintenance release Rack number Slot number 1 = external DP interface ID of the primary DP master system ID of the redundant DP master system
INT INT INT BOOL
BOOL DWORD INT DWORD DWORD BOOL BYTE BYTE BOOL BYTE BYTE
Default
0 2 2 0
1 0 0 0 0 0 0 0 0 255 255
Output parameters
I/O (parameter) CH_ACTIVE
CH_EXIST CH_OK DIAG_INF DM_ACTIVE DXCHG_xx DXCHG1_xx EXT_STAT
Meaning
Data type
Channel active
DWORD
Channel exists Channel OK System structure: Diagnostic information Fault delay 1st internal data exchange channel for channel block 2nd internal data exchange channel for channel block Release for maintenance - extended status
DWORD DWORD STRUCT DWORD DWORD DWORD DWORD
Default
16#000 00000 0 0 0 16#0 0 0 0
172
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.28 MOD_D2: Monitoring up to 32 channels of S7-300/400 SM modules with diagnostic functions
I/O (parameter) EXT_STAT_A
FS_ACTIVE
MOD_INF MS_XCHG_xx
MSG_ACKx MSGSTATx O_MS OMODE_xx QERR QMODF QPERAF QRACKF
Meaning
Data type
Extended status - Application Application data transfer active Flutter suppression
DWORD DWORD
System structure: Module parameter Maintenance Status - Data exchange channel (xx = 00 - 63) Message acknowledgment (x = 1 - 3) Message error information (x = 1 - 3) Maintenance status Channel mode (xx = 00 - 15/00 - 31) 1 = program error 1 = module removed/defective 1 = I/O access error 1 = higher-level error
STRUCT DWORD
WORD WORD DWORD DWORD BOOL BOOL BOOL BOOL
Default
0
16#000 00000
0
0 0 0 0 1 0 0 0
In/out parameters
I/O (parameter) ACC_MODE CPU_DIAG RAC_DIAG
Meaning
1 = accept MODE settings System structure: CPU diagnostics System structure: Rack diagnostics
Data type
BOOL STRUCT STRUCT
Default 0
Additional information For additional information, refer to the sections: Message texts and associated values of MOD_D1 (Page 154) Message texts and associated values of MOD_D2 (Page 174) Maintenance status MS (Page 533)
See also
MODE settings for SM modules (Page 517) OMODE settings for SM modules (Page 527)
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
173
Family: @System 6.28 MOD_D2: Monitoring up to 32 channels of S7-300/400 SM modules with diagnostic functions
6.28.3
Message texts and associated values of MOD_D2
Assignment of message text and message class
Message block ALARM_8P
EV_ID1
Message number
1
2 3
4
5
6 7
8
EV_ID2
1
... 8
EV_ID3
1
... 8
EV_ID4
1
... 8
EV_ID5
1
Default message text
Message class
Module @1%d@/@2%d@/@3%d@: Fail- ure
Module @1%d@/@2%d@/@3%d @: @5W%t#MOD_D2_TXT@
Module @1%d@/@2%d@/@3%d@: Multiple diagnostic interrupt
Module @1%d@/@2%d@/@3%d@: @4W%t#MOD_D2_TXT@
Module @1%d@/@2%d@/@3%d@: Maintenance demanded (external)
Module @1%d@/@2%d@/@3%d@: Maintenance required (external)
Module @1%d@/@2%d@/@3%d@: Error channel 00 @4W%t#MOD_D2_TXT@
...
Module @1%d@/@2%d@/@3%d@: Error channel 07 @4W%t#MOD_D2_TXT@
Module @1%d@/@2%d@/@3%d@: Error channel 08 @4W%t#MOD_D2_TXT@
...
Module @1%d@/@2%d@/@3%d@: Error channel 15 @4W%t#MOD_D2_TXT@
Module @1%d@/@2%d@/@3%d@: Error channel 16 @4W%t#MOD_D2_TXT@
...
Module @1%d@/@2%d@/@3%d@: Error channel 23 @4W%t#MOD_D2_TXT@
Module @1%d@/@2%d@/@3%d@: Error channel 24 @4W%t#MOD_D2_TXT@
PLC Process Control Message Failure No message PLC Process Control Message Failure PLC Process Control Message Failure PLC Process Control Message Failure No message PLC Process Control Message Error Preventative Maintenance Standard PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
174
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.28 MOD_D2: Monitoring up to 32 channels of S7-300/400 SM modules with diagnostic functions
Message block ALARM_8P
Message number
... 8
Default message text
... Module @1%d@/@2%d@/@3%d@: Error channel 31 @4W%t#MOD_D2_TXT@
Message class
PLC Process Control Message Failure
You will find the message texts and their text numbers in "Text library for MOD_D2 (Page 537)".
Assignment of associated values
Message block Associ-
ALARM_8P
ated
value
EV_ID1
1
2
3
4
Block parameters
MOD_INF.SUBN_ID MOD_INF.RACK_NO MOD_INF.SLOT_NO -
Meaning
DP master system ID (byte) Rack/station number (byte) Slot number (byte) Text number (messages 1 - 3) of MOD_D2_TXT
EV_ID2
1
MOD_INF.SUBN_ID DP master system ID (byte)
2
MOD_INF.RACK_NO Rack/station number (byte)
3
MOD_INF.SLOT_NO Slot number (byte)
4
-
Text number (message 5) of MOD_D2_TXT
5
-
Text number (message 3) of MOD_D2_TXT
EV_ID3
1
MOD_INF.SUBN_ID DP master system ID (byte)
2
MOD_INF.RACK_NO Rack/station number (byte)
3
MOD_INF.SLOT_NO Slot number (byte)
4
-
Text number (messages 1 - 8) of MOD_D2_TXT
EV_ID4
1
MOD_INF.SUBN_ID DP master system ID (byte)
2
MOD_INF.RACK_NO Rack/station number (byte)
3
MOD_INF.SLOT_NO Slot number (byte)
4
-
Text number (messages 1 - 8) of MOD_D2_TXT
EV_ID5
1
MOD_INF.SUBN_ID DP master system ID (byte)
2
MOD_INF.RACK_NO Rack/station number (byte)
3
MOD_INF.SLOT_NO Slot number (byte)
4
-
Text number (messages 1 - 8) of MOD_D2_TXT
See also
Message Classes (Page 531)
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
175
Family: @System 6.29 MOD_D24_PN: Monitoring S7-300 SM modules with up to 24 channels and with diagnostics functions
6.29
MOD_D24_PN: Monitoring S7-300 SM modules with up to 24 channels and with diagnostics functions
6.29.1
Description of MOD_D24_PN
Object name (type + number) FB 199 · I/Os of MOD_D16_PN/MOD_D24_PN (Page 176)
Area of application
Block MOD_D24_PN monitors S7-300 SM modules with a maximum of 24 channels and with diagnostics functions.
6.29.2
I/Os of MOD_D16_PN/MOD_D24_PN
The factory setting of the block display in the CFC is identified in the "I/O" column:
I/O name bold = I/O visible, I/O name normal = I/O not visible.
You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15)".
Input parameters
I/O (parameter) CHAN_NUM DELAY1 DELAY2 DIAG_BUF
EN_MSG EV_IDx
FEATURE_xx FEATURE_yy LADDR LADDR1
MODE_xx
Meaning
Data type Default
Total number of channels -1
INT
0
Alarm delay 1 (s)
INT
2
Alarm delay 2 (s)
INT
2
Entry in diagnostic buffer (relevant for maintenance BOOL
0
personnel)
1 = Enable message
BOOL
1
Message number ALARM_8P_x (x = 1 - 2/1 - 3/1 - 4, assigned by the ES)
DWORD
0
Feature parameter (xx = 01 - 04)
WORD
0
Feature parameter (yy = 05 - 10)
DWORD
0
Logic input address of the module
INT
0
Logical output address of the module (if output ad- INT
0
dress is not the same as input address).
Operating mode channel xx (xx = 00 - 07/00 - 15/00 - DWORD
0
23)
176
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.29 MOD_D24_PN: Monitoring S7-300 SM modules with up to 24 channels and with diagnostics functions
I/O (parameter)
MS MS_REQ RACK_NO SLOT_NO SUBSL_NO SUBN_TYP SUBN1_ID SUBN2_ID
Meaning
Maintenance status 1 = Request maintenance release Rack number Slot number Subslot number 1 = external PN interface PN IO system 1 ID (100 - 115) PN IO system 2 ID (100 - 115)
Data type Default
DWORD
0
BOOL
0
BYTE
0
BYTE
0
BYTE
0
BOOL
0
BYTE
255
BYTE
255
Output parameters
I/O (parameter) CH_ACTIVE
CH_EXIST CH_OK DIAG_INFx DXCHG_xx DXCHG1_xx
EXT_STATx EXT_STAT_A
FS_ACTIVE
MOD_INF MS_XCHG_xx
MSG_ACKx MSGSTATx O_MS OMODE_xx
QERR QMODF QPERAF QRACKF
Meaning
Data type Default
Channel active
DWORD
Channel exists
DWORD
Channel OK
DWORD
System structure: Diagnostic information
STRUCT
1st internal data exchange channel for channel block DWORD
2nd internal data exchange channel for channel block
DWORD
Release for maintenance - extended status
DWORD
Extended status - Application
DWORD
Application data transfer active
Flutter suppression active
DWORD
System structure: Module parameter Maintenance Status - Data exchange channel (xx = 00 - 63) Message acknowledgment (x = 1 - 2/1 - 3/1 - 4) Message error information (x = 1 - 2/1 - 3/1 - 4) Maintenance status Operating mode channel xx (xx = 00 - 07/00 - 15/00 - 23) 1 = program error 1 = module removed/defective 1 = I/O access error 1 = higher-level error
STRUCT DWORD
WORD WORD DWORD DWORD
BOOL BOOL BOOL BOOL
16#0000000 0 0 0 0 0 0
0 0
16#0000000 0
0
0 0 0 0
1 0 0 0
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
177
Family: @System 6.29 MOD_D24_PN: Monitoring S7-300 SM modules with up to 24 channels and with diagnostics functions
In/out parameters
I/O (parameter) ACC_MODE CPU_DIAG_PN RAC_DIAG
Meaning
1 = accept MODE settings System structure: CPU diagnostics System structure: Rack diagnostics
Data type
BOOL STRUCT STRUCT
Default 0
Additional information For additional information, refer to the sections: Message texts and associated values of MOD_D16_PN/MOD_D24_PN (Page 178) Maintenance status MS (Page 533)
6.29.3
Message texts and associated values of MOD_D16_PN/MOD_D24_PN
Assignment of message text and message class The process control messages of ALARM_8P with EV_ID1 are assigned as follows:
Message block ALARM_8P
EV_ID1
Message number
1
2
3
4 5
6 7
8
Default message text
Message class
Module @1%d@/@2%d@/@3%d@/ @6%d@: Failure
Module @1%d@/@2%d@/@3%d@/ @6%d@:@5W%t#MOD_n_TXT@
Module @1%d@/@2%d@/@3%d@/ @6%d@:
@5W%t#MOD_n_TXT@ (n=16, 24)
Module @1%d@/@2%d@/@3%d@/ @6%d@: Multiple diagnostics interrupt
Module @1%d@/@2%d@/@3%d@/ @6%d@:
@4W%t#MOD_n_TXT@ (n=16, 24)
Module @1%d@/@2%d@/@3%d@/ @6%d@: maintenance required
Module @1%d@/@2%d@/@3%d@/ @6%d@:
Maintenance demanded (external)
No message module @1%d@/@2%d@/ @3%d@/@6%d@:
Maintenance required (external)
PLC Process Control Message Failure PLC Process Control Message Error PLC Process Control Message Failure
PLC Process Control Message Error PLC Process Control Message Failure
Preventative Maintenance Standard PLC Process Control Message Error
Preventative Maintenance Standard
178
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.29 MOD_D24_PN: Monitoring S7-300 SM modules with up to 24 channels and with diagnostics functions
Associated values of ALARM_8P with EV_ID1
Associated value 1 2 3 4
5
6
Block parameter
ID of the PN IO system Rack/station number Slot number Text number (message 5) from MOD_D16_PN_TXT / MOD_D24_PN_TXT Text number (message 3) from MOD_D16_PN_TXT / MOD_D24_PN_TXT Subslot number
Data type BYTE BYTE BYTE BYTE
BYTE
BYTE
The process control messages of ALARM_8P with EV_ID2 are assigned as follows:
Message block ALARM_8P
EV_ID2
Message number
1
2
3
4
5
6
7
8
Default message text
Message class
Module @1%d@/@2%d@/@3%d@/ @5%d@: Error channel 00 @4W%t# MOD_D16_PN_TXT /MOD_D24_PN_TXT @
Module @1%d@/@2%d@/@3%d@/ @5%d@: Error channel 01 @4W%t# MOD_D16_PN_TXT /MOD_D24_PN_TXT @
Module @1%d@/@2%d@/@3%d@/ @5%d@: Error channel 02 @4W%t# MOD_D16_PN_TXT /MOD_D24_PN_TXT @
Module @1%d@/@2%d@/@3%d@/ @5%d@: Error channel 03 @4W%t# MOD_D16_PN_TXT /MOD_D24_PN_TXT @
Module @1%d@/@2%d@/@3%d@/ @5%d@: Error channel 04 @4W%t# MOD_D16_PN_TXT /MOD_D24_PN_TXT @
Module @1%d@/@2%d@/@3%d@/ @5%d@: Error channel 05 @4W%t# MOD_D16_PN_TXT /MOD_D24_PN_TXT @
Module @1%d@/@2%d@/@3%d@/ @5%d@: Error channel 06 @4W%t# MOD_D16_PN_TXT /MOD_D24_PN_TXT @
Module @1%d@/@2%d@/@3%d@/ @5%d@: Error channel 07 @4W%t# MOD_D16_PN_TXT /MOD_D24_PN_TXT @
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
179
Family: @System 6.29 MOD_D24_PN: Monitoring S7-300 SM modules with up to 24 channels and with diagnostics functions
Associated values of ALARM_8P with EV_ID2
Associated value 1 2 3 4 5
Block parameter ID of the PN IO system Rack/station number Slot number Text number from MOD_D16_PN_TXT /MOD_D24_PN_TXT Subslot number
Data type BYTE BYTE BYTE BYTE BYTE
The process control messages of ALARM_8P with EV_ID3 are assigned as follows:
Message block ALARM_8P
EV_ID3
Message number
1
2
3
4
5
6
7
8
Default message text
Message class
Module @1%d@/@2%d@/@3%d@/ @5%d@: Error channel 08 @4W%t# MOD_D16_PN_TXT /MOD_D24_PN_TXT @
Module @1%d@/@2%d@/@3%d@/ @5%d@: Error channel 09 @4W%t# MOD_D16_PN_TXT /MOD_D24_PN_TXT @
Module @1%d@/@2%d@/@3%d@/ @5%d@: Error channel 10 @4W%t# MOD_D16_PN_TXT /MOD_D24_PN_TXT @
Module @1%d@/@2%d@/@3%d@/ @5%d@: Error channel 11 @4W%t# MOD_D16_PN_TXT /MOD_D24_PN_TXT @
Module @1%d@/@2%d@/@3%d@/ @5%d@: Error channel 12 @4W%t# MOD_D16_PN_TXT /MOD_D24_PN_TXT @
Module @1%d@/@2%d@/@3%d@/ @5%d@: Error channel 13 @4W%t# MOD_D16_PN_TXT /MOD_D24_PN_TXT @
Module @1%d@/@2%d@/@3%d@/ @5%d@: Error channel 14 @4W%t# MOD_D16_PN_TXT /MOD_D24_PN_TXT @
Module @1%d@/@2%d@/@3%d@/ @5%d@: Error channel 15 @4W%t# MOD_D16_PN_TXT /MOD_D24_PN_TXT @
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
180
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.29 MOD_D24_PN: Monitoring S7-300 SM modules with up to 24 channels and with diagnostics functions
Associated values of ALARM_8P with EV_ID3
Associated value 1 2 3 4 5
Block parameter ID of the PN IO system Rack/station number Slot number Text number from MOD_D16_PN_TXT /MOD_D24_PN_TXT Subslot number
Data type BYTE BYTE BYTE BYTE BYTE
Process control messages for ALARM_8P with EV_ID4 are assigned as follows:
Message block ALARM_8P
EV_ID_4
Message number
1
2
3
4
5
6
7
8
Default message text
Module @1%d@/@2%d@/@3%d@/ @5%d@: Error channel 16 @4W%t# MOD_D24_PN_TXT @
Module @1%d@/@2%d@/@3%d@/ @5%d@: Error channel 17 @4W%t# MOD_D24_PN_TXT @
Module @1%d@/@2%d@/@3%d@/ @5%d@: Error channel 18 @4W%t# MOD_D24_PN_TXT @
Module @1%d@/@2%d@/@3%d@/ @5%d@: Error channel 19 @4W%t# MOD_D24_PN_TXT @
Module @1%d@/@2%d@/@3%d@/ @5%d@: Error channel 20 @4W%t# MOD_D24_PN_TXT @
Module @1%d@/@2%d@/@3%d@/ @5%d@: Error channel 21 @4W%t# MOD_D24_PN_TXT @
Module @1%d@/@2%d@/@3%d@/ @5%d@: Error channel 22 @4W%t# MOD_D24_PN_TXT @
Module @1%d@/@2%d@/@3%d@/ @5%d@: Error channel 23 @4W%t# MOD_D24_PN_TXT @
Message class
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
Associated values of ALARM_8P with EV_ID4
Associated value 1 2 3 4 5
Block parameter ID of the PN IO system Rack/station number Slot number Text number from MOD_D24_PN_TXT Subslot number
Data type BYTE BYTE BYTE BYTE BYTE
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
181
Family: @System 6.30 MOD_D3: Monitoring of hybrid modules with diagnostic capability
You can find the message texts and their text numbers in the section Text library for MOD_D8_PN (FB197) / MOD_D16_PN (FB198) / MOD_D24_PN (FB199) / MOD_ENME (FB 419) (Page 542). You can find additional information in the section: Message Classes (Page 531).
6.30
MOD_D3: Monitoring of hybrid modules with diagnostic capability
6.30.1
Description of MOD_D3
Object name (type + number) FB 134 · MOD_D3 block I/Os (Page 188)
Area of application
Block MOD_D3 monitors a maximum of up to 16 channels on S7-300 SM modules with diagnostics functions. H systems support only the modules installed in switched racks.
MOD_D3 includes all the functionality of MOD_D1, plus additional functions for diagnostic evaluation of multiple channel types in a diagnostic data record. The block also fully supports 4byte channel-specific diagnostics. Note: MOD_D1 only evaluated 8 selected bits of the 4-byte channel-specific diagnosis.
The modules supported are the ET 200PRO modules: 6ES7 148 4FC00 0AB0 -> 8DI/4DO 6ES7 148 4FA00 0AB0 -> 8/16 DI
Calling OBs
The block must be installed in the run sequence in the following OBs:
OB 1 OB 82 OB 83 OB 85 OB 86 OB 100
Cyclic program Diagnostic interrupt Insert/remove module interrupt Program execution error Rack failure Warm restart
182
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Use in CFC
Family: @System 6.30 MOD_D3: Monitoring of hybrid modules with diagnostic capability
The following actions are executed automatically with the "Generate module drivers" CFC function:
· The MOD_D3 block is installed in its runtime group downstream of the RACK-block runtime group in the above-mentioned OBs.
· The MODE_xx (mode of the channels xx of the module), SUBN1_ID, SUBN2_ID, and SUBN_TYP inputs are configured.
· The logical base address LADDR of the module is configured.
· The OUT structures CPU_DIAG of the OB_BEGIN block and RAC_DIAG of the RACK block are interconnected with the IN_OUT structures of the same name of MOD_D3.
· The EN input is interconnected with the output of an AND block. Its inputs are interconnected with the outputs EN_SUBx (x = number of the DP master system) of the OB_BEGIN block, EN_Rxxx (xxx = rack/station number) of the SUBNET block and EN_Mxx (xx = module number) of the RACK block.
· The output parameter of DXCHG_xx is interconnected with the following channel block at the DataXchg parameter.
· The output parameter of O_MS is interconnected with the following channel block at the MS parameter.
Function and method of operation
The MOD_D3 block analyzes all events affecting a module and its channels acyclically. It generates a channel-specific MODE (Page 517) and value status for the signal processing blocks. ALARM_8P is used to report these events.
Execution of the MOD_D3 block is enabled by the higher-level RACK block. The event to be evaluated is stored in the CPU_DIAG start and diagnostic information of the OB_BEGIN block. There is a MODE_xx input for each signal channel of the module. The module channel configuration data created in HW Config is reported here. The function writes MODE_xx to the low word of the OMODE_xx (Page 527) output parameter. This occurs only during startup or if you set ACC_MODE = TRUE. The current channel value status is written to the most significant byte. If the result is positive, the system sets OMODE_xx = 16#80xxxxxx.
The following events lead to the value status "invalid value due to higher-level error" (OMODE_xx = 16#40xxxxxx):
· Events that are evaluated by the RACK block:
Rack failure (OB 86) (output parameter QPERAF = TRUE)
· Events that are evaluated by the MOD block:
Program execution error (OB 85) (output parameter QPERAF = TRUE)
Module removed (OB 83) (output parameter QMODF = TRUE)
Diagnostic interrupt (OB 82) Distinguishing between module errors and channel errors
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
183
Family: @System 6.30 MOD_D3: Monitoring of hybrid modules with diagnostic capability
The following events are module errors (QMODF = TRUE output parameter): · External auxiliary voltage missing · Front connector missing · Module not configured · Wrong parameter in module · Wrong/missing module · Communication error at a CPU module · Timeout (watchdog) · Loss of internal power at a module · Rack failure · CPU failure · EPROM error · RAM error · ADC/DAC error · Fuse tripped · Power supply 1: Error · Power supply 2: Error
The following events are channel errors (value status "invalid value", OMODE_xx = 16#00xxxx): · Configuration/parameter assignment error · Common-mode errors (analog I/Os only) · Short-circuit to P · Short circuit to M · Interruption at the output transistor · Wire break · Reference channel error (analog inputs only) · Measuring range underflow (analog inputs only) · Measuring range overflow (analog inputs only) · Missing load voltage (analog and digital outputs only) · Missing sensor power supply (digital outputs only) · Fuse tripped (digital outputs only) · Mass error (digital I/Os only) · Excess temperature (digital outputs only) · Undervoltage · Overvoltage
184
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System
6.30 MOD_D3: Monitoring of hybrid modules with diagnostic capability
· Overload
· Hardware interrupt
· Actuator warning
· Safety shutdown
· Ambiguous error
· Error 1 in actuator/sensor
· Error 2 in actuator/sensor
· Channel temporarily not available
ALARM_8P is used to report "Module removed", "I/O access error" and "Diagnostics interrupt" events to the OS.
The diagnostics interrupt function distinguishes between module and channel errors, whereby each channel is assigned a message ID. Only one incoming/outgoing event can be reported for each channel. As long as an incoming message is queued at a channel, further messages on new events at this channel will be lost.
If the event is defined uniquely in the diagnostic information, the corresponding text will be entered in the message. If ambiguous entries exist, the text of the first set bit in the error byte of the diagnostic information will be displayed. When using modules assigned diagnostic functions and more than one error byte for diagnostic information, only the channel xx error text will be output if the error information is not displayed in the first error byte.
The system verifies during startup that the module is available (plugged in). The module status information that is read here is then available in the form of service output parameters (MOD_INF).
Detailed information about the errors is entered in the DIAG_INF output parameter of data type STRUCT. You will find additional information about this in the reference manual System Software for S7-300/400 System and Standard Functions; Diagnostic Data, Byte 0 to Byte 8, Structure of Channel-Specific Diagnostic Data.
Several channel types can occur in one diagnostic data record. If the "further channel types exist" bit is set, MOD_D3 runs through the entire diagnostic evaluation and handles reporting for each further channel type.
The new diagnostic data ("channel being calibrated" and "channel temporarily not available") are considered as channel errors and output. The detailed texts are output via the system text library and a corresponding associated value.
Redundancy
The higher-level RACK block monitors the redundancy of DP master systems operating in an H system.
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
185
Family: @System 6.30 MOD_D3: Monitoring of hybrid modules with diagnostic capability
MODE Setting You will find additional information about this in the "MODE settings (Page 517)" section.
Note If you change the parameter settings for the MODE_xx inputs at runtime, these changes will not be accepted at the outputs until the ACC_MODE is set to 1.
OMODE Structure You will find additional information about this in the "OMODE settings (Page 527)" section.
Valid channel display
The available channels on a module are displayed in the CH_EXIST output by setting a bit in the DWORD, starting at bit 0, for every existing channel. If the bit assigned to a channel = 0, the channel is not available.
Output CH_OK displays the valid channels on a module by setting a bit to TRUE for every valid channel, where bit 0 is assigned to channel 0, etc. If the bit assigned to a channel is 0, the channel is faulty. If a module error occurs, all channels are disrupted.
Addressing
You will find additional information about this in "Addressing (Page 530)".
HART modules with read/write access to the process image are configured in the same way as input modules. The set I/O range must always be identical.
Example: SM 332 AO 2x0/4..20mA HART 332-5TB00-0AB0:
Address input range (HW Config) Address output range (HW Config) LADDR (decimal/hex)
544
544
544 / 16#0220
Error handling
The plausibility of input parameters is not checked. You will find additional information about error handling in the "Error information of output parameter MSG_STAT" (Page 530) section.
Service Information
To analyze faults, the module status information entered during startup is read via the MOD_INF structured output parameter. You will find additional information about this in the reference manual System Software for S7-300/400 System and Standard Functions; System Status List, Module Status Information.
Following a diagnostic interrupt, you will also find detailed module diagnostic information in the MODDIAG0 to MODDIAG8 output parameters. You will find additional information in the
186
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.30 MOD_D3: Monitoring of hybrid modules with diagnostic capability
reference manual System Software for S7-300/400 System and Standard Functions; Diagnostic Data, Byte 0 to Byte 8. The CHDIAG00 to CHDIAG15 output parameters contain detailed channel-status information. You will find additional information in the reference manual System Software for S7-300/400 System and Standard Functions; Structure of Channel-Specific Diagnostic Data. The system resets this diagnostic information after a diagnostic interrupt has been reported outgoing (no further channel or module errors are queued).
Startup characteristics After a restart/initial startup, the system verifies that the module is available under its logical base address. A restart (OB 100) is reported via the LSB in byte 2 of the OMODE_xx outputs.
Overload Behavior The MOD_D3 block counts the OB82 calls. The counter is reset in OB1. If more than two OB82 events occur in succession before the cycle control point is reached (OB1), these events are rejected and the message "OB82 DP master failure: x Rack: y Slot: z" is output.
Time response Not available
Message response MOD_D3 uses ALARM_8P_1 to report module errors. The function also calls ALARM_8P_2 and ALARM_8P_3 which are intended for channel errors. The inputs DELAY1 and DELAY2 are used to delay the output of I/O access error messages. DELAY1 allows you to enter a time in seconds for which the block will wait for a higher-priority error (rack failure or removal/insertion) following a program execution error (OB 85) before it outputs the message. The message is output only under the condition that no higher-priority error is reported within this delay time. DELAY2 determines the number of seconds the block waits after the higher-priority error has been reported outgoing until it outputs the queued I/O access error as well. Both values are set to 2 seconds by default. The message function can be disabled by setting EN_MSG = FALSE.
Flutter suppression The "Flutter suppression" function is used to delay the outgoing of a message by a configurable period. The flutter time is entered at the channel block at the FlutTmIn parameter. The high byte of the DXCHG parameter of the channel blocks contains the flutter time. Flutter suppression comes into effect when FlutEN = 1 or FlutTmIn > 0 is set at the channel block. There is only one flutter message per module. The delay times and fault messages are channelspecific. The fault messages are extended by at least the delay time. Flutter exists if the fault messages "Outgoing" and then "Incoming" are present within the delay time. The last fluttering channel and its set delay time deactivates the flutter message.
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
187
Family: @System 6.30 MOD_D3: Monitoring of hybrid modules with diagnostic capability
Operator control and monitoring If asset management is used in the project and the diagnostic screens have been generated, the faceplate can be called via its block icon. For additional information, refer to the "Process Control System PCS 7; Maintenance Station" manual.
Additional information For additional information, refer to the sections: Message texts and associated values of MOD_D3 (Page 190) Maintenance status MS (Page 533) You can also find additional information on this in PCS 7 Advanced Process Library > Basics of APL > General functions of the blocks > Operating, monitoring and reporting > Release for maintenance
6.30.2
I/Os of MOD_D3
The factory setting of the block display in the CFC is identified in the "I/O" column: I/O name bold = I/O visible, I/O name normal = I/O not visible.
You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15)".
Input parameters
I/O (parameter) CHAN_NUM DELAY1 DELAY2 DIAG_BUF EN_MSG EV_IDx FEATURE_xx FEATURE_yy LADDR LADDR1
MODE_xx MS MS_REQ RACK_NO SLOT_NO SUBN_TYP
Meaning
Data type
Total number of channels -1
INT
Alarm delay 1 (s)
INT
Alarm delay 2 (s)
INT
Entry in diagnostic buffer (relevant for maintenance personnel) BOOL
1 = Enable message
BOOL
Message number (x = 1 - 3)
DWORD
Feature parameter (xx = 01 - 04)
WORD
Feature parameter (yy = 05 - 10)
DWORD
Logic input address of the module
INT
Logical output address of the module (if output address is not INT the same as input address).
Mode channel xx (xx = 00 - 15)
DWORD
Maintenance status
DWORD
1 = Request maintenance release
BOOL
Rack number
BYTE
Slot number
BYTE
1 = external DP interface
BOOL
De- fault 0 2 2 0 1 0 0 0 0 0
0 0 0 0 0 0
188
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.30 MOD_D3: Monitoring of hybrid modules with diagnostic capability
I/O (parameter)
SUBN1_ID
SUBN2_ID
Meaning
ID of the primary DP master system ID of the redundant DP master system
Data type
BYTE BYTE
De- fault
255
255
Output parameters
I/O (parameter) CH_ACTIVE CH_EXIST CH_OK DIAG_INF DM_ACTIVE DXCHG_xx DXCHG1_xx EXT_STAT EXT_STAT_A
FS_ACTIVE MOD_INF MS_XCHG_xx
MSG_ACKx MSGSTATx O_MS OMODE_xx QERR QMODF QPERAF QRACKF
Meaning
Channel active Channel exists Channel OK System structure: Diagnostic information Fault delay 1st internal data exchange channel for channel block 2nd internal data exchange channel for channel block Release for maintenance - extended status Extended status - Application Application data transfer active Flutter suppression System structure: Module parameter Maintenance Status - Data exchange channel (xx = 00 63) Message acknowledgment (x = 1 - 3) Message error information (x = 1 - 3) Maintenance status Mode channel (xx = 00 - 15) 1 = program error 1 = module removed/defective 1 = I/O access error 1 = higher-level error
Data type DWORD DWORD DWORD STRUCT DWORD DWORD DWORD DWORD DWORD
DWORD STRUCT DWORD
WORD WORD DWORD DWORD BOOL BOOL BOOL BOOL
Default
16#00000000 0 0 0 16#0 0 0 0 0
16#00000000
0
0 0 0 0 1 0 0 0
In/out parameters
I/O (parameter) ACC_MODE CPU_DIAG RAC_DIAG
Meaning
1 = accept MODE settings System structure: CPU diagnostics System structure: Rack diagnostics
Data type
BOOL STRUCT STRUCT
De- fault
0
Additional information For additional information, refer to the sections: Message texts and associated values of MOD_D3 (Page 190)
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
189
Family: @System 6.30 MOD_D3: Monitoring of hybrid modules with diagnostic capability
Maintenance status MS (Page 533)
6.30.3
Message texts and associated values of MOD_D3
Assignment of message text and message class
Message block ALARM_8P
EV_ID1
Message number
1
2 3
4
5
6 7
8
EV_ID2
1
... ...
8
EV_ID3
1
... ...
8
Default message text
Module @1%d@/@2%d@/@3%d@/ @6%d@: Failure
Module @1%d@/@2%d@/@3%d@/ @6%d@: @5W%t#MOD_D3_TXT@ Module @1%d@/@2%d@/@3%d@/ @6%d@: Multiple diagnostics interrupt Module @1%d@/@2%d@/@3%d@/ @6%d@: @4W%t#MOD_D3_TXT@
Module @1%d@/@2%d@/@3%d@/ @6%d@: Maintenance demanded (external) Module @1%d@/@2%d@/@3%d@/ @6%d@: Maintenance required (external) Module @1%d@/@2%d@/@3%d@: Error channel 00 @4W %t#MOD_D3_TXT@ ... ... Module @1%d@/@2%d@/@3%d@: Error channel 07 @4W %t#MOD_D3_TXT@ Module @1%d@/@2%d@/@3%d@: Error channel 08 @4W %t#MOD_D3_TXT@ ... ... Module @1%d@/@2%d@/@3%d@: Error channel 15 @4W %t#MOD_D3_TXT@
Message class
PLC Process Control Message Failure No message PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
No message PLC Process Control Message Error
Preventative Maintenance Standard
PLC Process Control Message Failure
... ... PLC Process Control Message Failure
PLC Process Control Message Failure
... ... PLC Process Control Message Failure
You will find the message texts and their text numbers in "Text library for MOD_D3" (Page 540).
190
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.31 MOD_D32_PN: PN diagnostic block check (32 channels)
Assignment of Associated Values
Message block ALARM_8P
EV_ID1
Associ- ated value
1
2
3
4
5
Block parameters
MOD_INF.SUBN_ID MOD_INF.RACK_NO MOD_INF.SLOT_NO
Meaning
DP master system ID (byte) Rack/station number (byte) Slot number (byte) Text number (message 5) of MOD_D3_TXT Text number (message 3) of MOD_D3_TXT
EV_ID2
1
MOD_INF.SUBN_ID
DP master system ID (byte)
2
MOD_INF.RACK_NO Rack/station number (byte)
3
MOD_INF.SLOT_NO Slot number (byte)
4
Text number (messages 1 - 8) from
MOD_D3_TXT
EV_ID3
1
MOD_INF.SUBN_ID
DP master system ID (byte)
2
MOD_INF.RACK_NO Rack/station number (byte)
3
MOD_INF.SLOT_NO Slot number (byte)
4
Text number (messages 1 - 8) from
MOD_D3_TXT
See also
Message Classes (Page 531)
6.31
MOD_D32_PN: PN diagnostic block check (32 channels)
6.31.1
Description of MOD_D32_PN
Object name (type + number) FB 421 · I/Os of MOD_D32_PN (Page 192)
Area of application The block MOD_D32_PN monitors diagnostics-capable 32-channel modules.
Additional information Additional information is available in the section:
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
191
Family: @System 6.31 MOD_D32_PN: PN diagnostic block check (32 channels)
Message texts and associated values of MOD_D32_PN (Page 193)
6.31.2
I/Os of MOD_D32_PN
The factory setting of the block display in the CFC is identified in the "I/O" column:
I/O name bold = I/O visible, I/O name normal = I/O not visible.
You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15)".
Input parameters
I/O (parameter)
LADDR LADDR1 SUBN_TYP SUBN1_ID SUBN2_ID RACK_NO SLOT_NO SUBSL_NO CHAN_NUM MODE_00 ... MODE_31 DELAY1 DELAY2 FEATURE_01 ... FEA- TURE_10
EV_ID1 .. EV_ID5 EN_MSG MS MS_REQ DIAG_BUF
Meaning
Data type
Logical address of module Logical address of module 1=External PN interface ID of primary subnet ID of redundant subnet Rack/station number Slot number Subslot number Total number of channels -1 Mode channel 0 ... Mode channel 31 Alarm delay 1 (s) Alarm delay 2 (s) Features of hardware parameter 01 ... Features of hardware parameter 10 Event ID 1 ... Event ID 5 1 = Enable message Maintenance State Maintenance release request 1=CPU diagnostic buffer entry on (relevant for service personnel)
INT INT BOOL BYTE BYTE BYTE BYTE BYTE INT DWORD INT INT WORD
DWORD BOOL DWORD BOOL BOOL
Default
0 0
16#FF 16#FF
0 0 0 0 2 2 0
0 1 0 0 0
In/Out parameters
I/O (parameter) CPU_DIAG_PN RAC_DIAG ACC_MODE
Meaning 1=Accept new mode settings
Data type Default
STRUCT
STRUCT
BOOL
0
192
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.31 MOD_D32_PN: PN diagnostic block check (32 channels)
Out parameters
I/O (parameter)
Meaning
QERR
1=Runtime error
QRACKF
1=Rack failure
QMODF
1=Module pulled / out of order
QPERAF
1=Module I/O access failure
O_MS
Maintenance State
CH_EXIST
Channel exist
CH_ACTIVE
Channel active
CH_OK
Channel OK
EXT_STAT
Maintenance release Extended status
EXT_STAT_A
Extended status application
FS_ACTIVE
Flutter suppression active
OMODE_00 ... OMODE_31
Mode channel 0 ... Mode channel 31
DXCHG_00 ... DXCHG_31 Bidirectional data exchange channel 0 ...
Bidirectional data exchange channel 31
DXCHG1_00 ... DXCHG1_31
Bidirectional data exchange channel 0 ... Bidirectional data exchange channel 31
MS_XCHG_00 ... MS_XCHG_31
MS exchange channel 0 ... MS exchange channel 31
MSGSTAT1 ... MSGSTAT5 Message failure 1 ...
Message failure 5
MSG_ACK1 ... MSG_ACK5
Message acknowledged 1 ... Message acknowledged 5
MOD_INF
Module information structure
DIAG_INF
Module diagnostic information structure
Data type
BOOL BOOL BOOL BOOL DWORD DWORD DWORD DWORD DWORD DWORD DWORD DWORD
DWORD
DWORD
DWORD
WORD
WORD
STRUCT STRUCT
Default
1 0 0 0 0 0 0 0 0 0 0 0
0
0
0
0
0
6.31.3
Message texts and associated values of MOD_D32_PN
Assignment of message text and message class The process control messages of ALARM_8P with EV_ID1 are assigned as follows:
Message number 1
2
3
Default message text Module @1%d@/@2%d@/@3%d@/@6%d@: Failure
BG @1%d@/@2%d@/@3%d@/@6%d@: @5W%t# MOD_D8_PN_TXT /MOD_D16_PN_TXT / MOD_D24_PN_TXT/MOD_D32_TXT @
Message class
PLC Process Control Message - Failure
PLC Process Control Message - Error
PLC Process Control Message - Failure
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
193
Family: @System 6.31 MOD_D32_PN: PN diagnostic block check (32 channels)
Message number 4 5
6 7 8
Default message text Module @1%d@/@2%d@/@3%d@/@6%d@: Multiple diag- nostics interrupt BG @1%d@/@2%d@/@3%d@/@6%d@: @4W%t# MOD_D8_PN_TXT /MOD_D16_PN_TXT / MOD_D24_PN_TXT/MOD_D32_TXT @
Module @1%d@/@2%d@/@3%d@/@6%d@: Maintenance demanded (external) Module @1%d@/@2%d@/@3%d@/@6%d@: Maintenance required (external)
Message class
PLC Process Control Message - Error PLC Process Control Message - Failure
Preventative Main- tenance - Standard PLC Process Control Message - Error Preventative Main- tenance - Standard
Associated values of ALARM_8P with EV_ID1:
Associated value 1 2 3 4
5
6
Block parameter
ID of the PN IO system Rack/station number Slot number Text number (message 5) from MOD_D8_PN_TXT / MOD_D16_PN_TXT /MOD_D24_PN_TXT/MOD_D32_TXT Text number (message 3) from MOD_D8_PN_TXT / MOD_D16_PN_TXT /MOD_D24_PN_TXT/MOD_D32_TXT Subslot number
Data type BYTE BYTE BYTE BYTE
BYTE
BYTE
The process control messages of ALARM_8P with EV_ID2 are assigned as follows:
Message number 1 2 3 4 5 6
Default message text
Module @1%d@/@2%d@/@3%d@/@5%d@: Error channel 00 @4W%t# MOD_D8_PN_TXT /MOD_D16_PN_TXT / MOD_D24_PN_TXT/MOD_D32_TXT @
Module @1%d@/@2%d@/@3%d@/@5%d@: Error channel 01 @4W%t# MOD_D8_PN_TXT /MOD_D16_PN_TXT / MOD_D24_PN_TXT/MOD_D32_TXT @
Module @1%d@/@2%d@/@3%d@/@5%d@: Error channel 02 @4W%t# MOD_D8_PN_TXT /MOD_D16_PN_TXT / MOD_D24_PN_TXT /MOD_D32_TXT @
Module @1%d@/@2%d@/@3%d@/@5%d@: Error channel 03 @4W%t# MOD_D8_PN_TXT /MOD_D16_PN_TXT / MOD_D24_PN_TXT/MOD_D32_TXT @
Module @1%d@/@2%d@/@3%d@/@5%d@: Error channel 04 @4W%t# MOD_D8_PN_TXT /MOD_D16_PN_TXT / MOD_D24_PN_TXT /MOD_D32_TXT @
Module @1%d@/@2%d@/@3%d@/@5%d@: Error channel 05 @4W%t# MOD_D8_PN_TXT /MOD_D16_PN_TXT / MOD_D24_PN_TXT/MOD_D32_TXT @
Message class
PLC Process Con- trol Message - Fail- ure
PLC Process Con- trol Message - Fail- ure
PLC Process Con- trol Message - Fail- ure
PLC Process Con- trol Message - Fail- ure
PLC Process Con- trol Message - Fail- ure
PLC Process Con- trol Message - Fail- ure
194
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.31 MOD_D32_PN: PN diagnostic block check (32 channels)
Message number 7
8
Default message text
Module @1%d@/@2%d@/@3%d@/@5%d@: Error channel 06 @4W%t# MOD_D8_PN_TXT /MOD_D16_PN_TXT / MOD_D24_PN_TXT/MOD_D32_TXT @
Module @1%d@/@2%d@/@3%d@/@5%d@: Error channel 07 @4W%t# MOD_D8_PN_TXT /MOD_D16_PN_TXT / MOD_D24_PN_TXT/MOD_D32_TXT @
Message class
PLC Process Con- trol Message - Fail- ure
PLC Process Con- trol Message - Fail- ure
Associated values of ALARM_8P with EV_ID2:
Associated value 1 2 3 4
5
Block parameter
Data type
ID of the PN IO system
BYTE
Rack/station number
BYTE
Slot number
BYTE
Text number from MOD_D8_PN_TXT /MOD_D16_PN_TXT / BYTE MOD_D24_PN_TXT/MOD_D32_TXT
Subslot number
BYTE
The process control messages of ALARM_8P with EV_ID3 are assigned as follows:
Message number 1 2 3 4 5 6 7 8
Default message text
Module @1%d@/@2%d@/@3%d@/@5%d@: Error channel 08 @4W%t# MOD_D16_PN_TXT /MOD_D24_PN_TXT/ MOD_D32_TXT @
Module @1%d@/@2%d@/@3%d@/@5%d@: Error channel 09 @4W%t# MOD_D16_PN_TXT /MOD_D24_PN_TXT/ MOD_D32_TXT @
Module @1%d@/@2%d@/@3%d@/@5%d@: Error channel 10 @4W%t# MOD_D16_PN_TXT /MOD_D24_PN_TXT/ MOD_D32_TXT @
Module @1%d@/@2%d@/@3%d@/@5%d@: Error channel 11 @4W%t# MOD_D16_PN_TXT /MOD_D24_PN_TXT/ MOD_D32_TXT @
Module @1%d@/@2%d@/@3%d@/@5%d@: Error channel 12 @4W%t# MOD_D16_PN_TXT /MOD_D24_PN_TXT/ MOD_D32_TXT @
Module @1%d@/@2%d@/@3%d@/@5%d@: Error channel 13 @4W%t# MOD_D16_PN_TXT /MOD_D24_PN_TXT/ MOD_D32_TXT @
Module @1%d@/@2%d@/@3%d@/@5%d@: Error channel 14 @4W%t# MOD_D16_PN_TXT /MOD_D24_PN_TXT/ MOD_D32_TXT @
Module @1%d@/@2%d@/@3%d@/@5%d@: Error channel 15 @4W%t# MOD_D16_PN_TXT /MOD_D24_PN_TXT/ MOD_D32_TXT @
Message class
PLC Process Con- trol Message - Fail- ure
PLC Process Con- trol Message - Fail- ure
PLC Process Con- trol Message - Fail- ure
PLC Process Con- trol Message - Fail- ure
PLC Process Con- trol Message - Fail- ure
PLC Process Con- trol Message - Fail- ure
PLC Process Con- trol Message - Fail- ure
PLC Process Con- trol Message - Fail- ure
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
195
Family: @System 6.31 MOD_D32_PN: PN diagnostic block check (32 channels)
Associated values of ALARM_8P with EV_ID3:
Associated value 1 2 3 4
5
Block parameter
ID of the PN IO system Rack/station number Slot number Text number from MOD_D8_PN_TXT /MOD_D16_PN_TXT / MOD_D24_PN_TXT/MOD_D32_TXT Subslot number
Data type BYTE BYTE BYTE BYTE
BYTE
The process control messages of ALARM_8P with EV_ID4 are assigned as follows:
Message number 1 2 3 4 5 6 7 8
Default message text Module @1%d@/@2%d@/@3%d@/@5%d@: Error channel 16 @4W%t# MOD_D24_PN_TXT/MOD_D32_TXT @
Module @1%d@/@2%d@/@3%d@/@5%d@: Error channel 17 @4W%t# MOD_D24_PN_TXT/MOD_D32_TXT @
Module @1%d@/@2%d@/@3%d@/@5%d@: Error channel 18 @4W%t# MOD_D24_PN_TXT /MOD_D32_TXT @
Module @1%d@/@2%d@/@3%d@/@5%d@: Error channel 19 @4W%t# MOD_D24_PN_TXT/MOD_D32_TXT @
Module @1%d@/@2%d@/@3%d@/@5%d@: Error channel 20 @4W%t# MOD_D24_PN_TXT /MOD_D32_TXT @
Module @1%d@/@2%d@/@3%d@/@5%d@: Error channel 21 @4W%t# MOD_D24_PN_TXT/MOD_D32_TXT @
Module @1%d@/@2%d@/@3%d@/@5%d@: Error channel 22 @4W%t# MOD_D24_PN_TXT/MOD_D32_TXT @
Module @1%d@/@2%d@/@3%d@/@5%d@: Error channel 23 @4W%t# MOD_D24_PN_TXT/MOD_D32_TXT @
Message class
PLC Process Con- trol Message - Fail- ure
PLC Process Con- trol Message - Fail- ure
PLC Process Con- trol Message - Fail- ure
PLC Process Con- trol Message - Fail- ure
PLC Process Con- trol Message - Fail- ure
PLC Process Con- trol Message - Fail- ure
PLC Process Con- trol Message - Fail- ure
PLC Process Con- trol Message - Fail- ure
Associated values of ALARM_8P with EV_ID4:
Associated value 1 2 3 4 5
Block parameter ID of the PN IO system Rack/station number Slot number Text number from MOD_D24_PN_TXT/MOD_D32_TXT Subslot number
Data type BYTE BYTE BYTE BYTE BYTE
196
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.31 MOD_D32_PN: PN diagnostic block check (32 channels)
The process control messages of ALARM_8P with EV_ID5 are assigned as follows:
Message number 1 2 3 4 5 6 7 8
Default message text Module @1%d@/@2%d@/@3%d@/@5%d@: Error channel 24 @4W%t# MOD_D32_TXT @
Module @1%d@/@2%d@/@3%d@/@5%d@: Error channel 25 @4W%t# MOD_D32_TXT @
Module @1%d@/@2%d@/@3%d@/@5%d@: Error channel 26 @4W%t# MOD_D32_TXT @
Module @1%d@/@2%d@/@3%d@/@5%d@: Error channel 27 @4W%t# MOD_D32_TXT @
Module @1%d@/@2%d@/@3%d@/@5%d@: Error channel 28 @4W%t# MOD_D32_TXT @
Module @1%d@/@2%d@/@3%d@/@5%d@: Error channel 29 @4W%t# MOD_D32_TXT @
Module @1%d@/@2%d@/@3%d@/@5%d@: Error channel 30 @4W%t# MOD_D32_TXT @
Module @1%d@/@2%d@/@3%d@/@5%d@: Error channel 31 @4W%t# MOD_D32_TXT @
Message class
PLC Process Con- trol Message - Fail- ure
PLC Process Con- trol Message - Fail- ure
PLC Process Con- trol Message - Fail- ure
PLC Process Con- trol Message - Fail- ure
PLC Process Con- trol Message - Fail- ure
PLC Process Con- trol Message - Fail- ure
PLC Process Con- trol Message - Fail- ure
PLC Process Con- trol Message - Fail- ure
Associated values of ALARM_8P with EV_ID5:
Associated value 1 2 3 4 5
Block parameter ID of the PN IO system Rack/station number Slot number Text number from MOD_D32_TXT Subslot number
Data type BYTE BYTE BYTE BYTE BYTE
You can find additional information in the section: Message Classes (Page 531)
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
197
Family: @System 6.32 MOD_D8: Monitoring up to 8 channels on S7-300/400 SM modules with diagnostic functions
6.32
MOD_D8: Monitoring up to 8 channels on S7-300/400 SM modules with diagnostic functions
6.32.1
Description of MOD_D8
Object name (type + number) FB 424 · MOD_D8 block I/Os (Page 200)
Area of application
The MOD_D8 block monitors S7-300 and S7-400 SM modules with diagnostic capability and up to 8 channels.
Calling OBs
The block must be installed in the run sequence in the following OBs:
OB 1 OB 82 OB 83 OB 85 OB 86 OB 100
Cyclic program Diagnostic interrupt Insert/remove module interrupt Program execution error Rack failure Warm restart
Use in CFC
The following actions are executed automatically with the "Generate module drivers" CFC function:
· The MOD_D8 block is implemented into its runtime group behind the runtime group of the RACK block in the OBs listed above.
· The MODE_xx (mode of the channels xx of the module), SUBN1_ID, SUBN2_ID, and SUBN_TYP inputs are configured.
· The logical start address LADDR of the module is configured.
· The OUT structures CPU_DIAG of the OB_BEGIN block and RAC_DIAG of the RACK block are interconnected with the IN_OUT structures of the same name of MOD_D8.
· The EN input is interconnected with the output of an AND block.
· The inputs of this block are interconnected with the outputs EN_SUBx (x = number of the DP master system) of the OB_BEGIN block, EN_Rxxx (xxx = rack/station number) of the OB_BEGIN_PN block and EN_Mxx (xx = module number) of the RACK block.
198
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.32 MOD_D8: Monitoring up to 8 channels on S7-300/400 SM modules with diagnostic functions
· The output parameter of the DXCHG_xx is interconnected with the subsequent channel block at the DataXchg parameter.
· The output parameter of the O_MS is interconnected with the subsequent channel block at the MS parameter.
Startup characteristics After a restart/initial startup, the system verifies that the module is available under its logical base address. A restart (OB 100) is reported via the LSB in byte 2 of the OMODE_xx (Page 527) outputs.
Troubleshooting Troubleshooting of the block is limited to the error information of the ALARM_8P. In addition, the ALARM_8P_2 provided for channel faults are called. Signaling can be disabled with EN_MSG = FALSE.
Forming the maintenance status The maintenance status MS of the data type DWORD is copied as is to the output O_MS.
Overload behavior When more than two OB 82 events take place one after the other before the delay time (OB 1) is reached, the events are discarded and a flatter alarm "Failure OB 82 DP master system:x station:y slot: z" is generated. The delay times and alarm messages are for specific channels; the alarm messages are extended by at least the delay time. The last flattering channel and its set delay time de-activates the flatter alarm.
System text library The block contains a system text library identical to MOD_D3.
Firmware update The firmware update for the listed HART modules is started by a diagnostic event "OB83 entering state" (remove module) followed directly by diagnostic event "OB83 exiting state" (insert module). With "OB83 exiting state", byte 2 bit 2 is set in data record 0 (1 = STOP mode). Once the firmware is completed, there is a repeated diagnostic event "OB83 entering state" (remove module) followed directly by diagnostic event "OB83 exiting state" (insert module). With "OB83 exiting state", byte 2 bit 2 is reset in data record 0 (0 = RUN mode). In MOD_D8, after an "OB83 exiting state" (module removed) the data record 0 (DS0) is always read extra in OB1 using SFC51 and SZL 00B1 to establish whether bit (1 = STOP mode) is set. If this is the case, this is always recognized as a firmware update and the module continues to be indicated as removed and not available. Only when there is an OB83 (module inserted) with the
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
199
Family: @System 6.32 MOD_D8: Monitoring up to 8 channels on S7-300/400 SM modules with diagnostic functions
information in DS0 (0 = RUN mode), is the module indicated as being inserted and available again.
It is assumed that "Module change in run" is always set for the ET 200M head modules so that a firmware update of the HART module always calls an OB83. This means that a firmware update cannot trigger an OB86 diagnostic interrupt.
The "Generate module driver" function enters 16#0001 in the Feature01 parameter for both HART modules. This means that DS0 is read extra when there is an OB 83 exiting state only when Feature01 = 16#0001
The Feature parameters (FEATURE_01 .. FEATURE_10) are intended for future expansions of the MOD_D8 block and for parameter settings for special module situations.
Currently only FEATURE_01 is used as an ID for HART module with a firmware update in RUN.
See also
Message texts and associated values of MOD_D8 (Page 202) Maintenance status MS (Page 533)
6.32.2
I/Os of MOD_D8
The factory setting of the block display in the CFC is identified in the "I/O" column: I/O name bold = I/O visible, I/O name normal = I/O not visible.
You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15)".
Input parameters
I/O (parameter) CHAN_NUM DELAY1 DELAY2 DIAG_BUF
EN EN_MSG EV_IDx FEATURE_01 ... FEATURE_04 FEATURE_05 ... FEATURE_10
Meaning
Total number of channels -1 Alarm delay 1 (s) Alarm delay 2 (s) 1= CPU Diagnostic Buffer entry on (relevant for service personnel)
1 = Enable message Message number (x = 1 - 3) Features of hardware paramter
Features of hardware paramter
Data type
INT INT INT BOOL
Default
0 2 2 0
BOOL BOOL DWORD WORD
1 1 0 16#0000
DWORD 16#00000000
200
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.32 MOD_D8: Monitoring up to 8 channels on S7-300/400 SM modules with diagnostic functions
I/O (parameter)
LADDR LADDR1 MODE_xx MS MS_REQ RACK_NO SLOT_NO SUBN_TYP SUBN1_ID SUBN2_ID
Meaning
Logical address of the module Logical address of the module Operating mode channel xx (xx = 00 - 15 / 00 - 07) Maintenance status 1 = Request maintenance release Rack number Slot number 1 = external DP interface ID of the primary DP master system ID of the redundant DP master system
Data type
INT INT DWORD DWORD BOOL BYTE BYTE BOOL BYTE BYTE
Default
0 0 16#00000000 16#00000000 0 16#00 16#00 0 16#FF 16#FF
Output parameters
I/O (parameter) CH_ACTIVE CH_EXIST CH_OK DIAG_INF DM_ACTIVE DXCHG_xx DXCHG1_xx
ENO EXT_STAT EXT_STAT_A
FS_ACTIVE MOD_INF MS_XCHG_xx
MSG_ACKx MSGSTATx O_MS OMODE_xx QERR QMODF QPERAF QRACKF
Meaning
Data type
Channel active
DWORD
Channel exists
DWORD
Channel OK
DWORD
System structure: Diagnostic information
STRUCT
Delayed messaging active
DWORD
1st internal data exchange channel for channel block DWORD
2nd internal data exchange channel for channel block
DWORD
BOOL
Release for maintenance - extended status
DWORD
Extended status - Application
DWORD
Application data transfer active
Flutter suppression
DWORD
System structure: Module parameter
STRUCT
Maintenance Status - Data exchange channel (xx = DWORD 00 - 07)
Message acknowledgment (x = 1 - 2)
WORD
Message error information (x = 1 - 2)
WORD
Maintenance status
DWORD
Channel mode (xx = 00 - 07)
DWORD
1 = program error
BOOL
1 = module removed/defective
BOOL
1 = I/O access error
BOOL
1 = higher-level error
BOOL
Default
16#00000000 0 0
16#00000000 0 0
0 16#00000000 16#00000000
16#00000000
0
16#0000 16#0000 16#00000000 16#00000000 1 0 0 0
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
201
Family: @System 6.32 MOD_D8: Monitoring up to 8 channels on S7-300/400 SM modules with diagnostic functions
In/out parameters
I/O (parameter) ACC_MODE CPU_DIAG RAC_DIAG
Meaning
1 = accept MODE settings System structure: CPU diagnostics System structure: Rack diagnostics
Data type
BOOL STRUCT STRUCT
Default 0
Additional information For additional information, refer to the sections: Message texts and associated values of MOD_D8 (Page 202) Maintenance status MS (Page 533)
6.32.3
Message texts and associated values of MOD_D8
Assignment of message text and message class
Message block ALARM_8P
EV_ID1
Message number
1
2
3 4 5
6 7
8
EV_ID2
1
... ...
8
Default message text
Message class
Module @1%d@/@2%d@/@3%d@: Failure Module @1%d@/@2%d@/@3%d@: Maintenance demanded (external) BG @1%d@/@2%d@/@3%d@: @5W%t#MOD_D8_TXT@ Module @1%d@/@2%d@/@3%d@: Multiple diagnostic interrupt BG @1%d@/@2%d@/@3%d@: @4W%t#MOD_D8_TXT@
BG @1%d@/@2%d@/@3%d@: @5W%t#MOD_D8_TXT@ BG @1%d@/@2%d@/@3%d@: Mainte- nance required (external) BG @1%d@/@2%d@/@3%d@: Error channel 00 @4W %t#MOD_D8_TXT@ ... ... BG @1%d@/@2%d@/@3%d@: Error channel 07 @4W %t#MOD_D8_TXT@
PLC Process Control Message Failure PLC Process Control Message Error
PLC Process Control Message Failure PLC Process Control Message Failure PLC Process Control Message Failure
No message PLC Process Control Message Error
Preventative Maintenance Standard PLC Process Control Message Failure
... ... PLC Process Control Message Failure
202
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.33 MOD_D8_PN: Monitoring S7-300 SM modules with up to 8 channels and with diagnostics functions
You can find the message texts and their text numbers in "Text library for MOD_D8 (Page 540)".
Assignment of associated values
Message block ALARM_8P
EV_ID1
Associated value
1 2 3 4 5
EV_ID2
1
2
3
4
Block parameters MOD_INF.SUBN_ID MOD_INF.RACK_NO MOD_INF.SLOT_NO
MOD_INF.SUBN_ID MOD_INF.RACK_NO MOD_INF.SLOT_NO
Meaning
DP master system ID (byte) Rack/station number (byte) Slot number (byte) Text number from MOD_D8_TXT Text number from MOD_D8_TXT
DP master system ID (byte) Rack/station number (byte) Slot number (byte) Text number from MOD_D8_TXT
6.33
MOD_D8_PN: Monitoring S7-300 SM modules with up to 8 channels and with diagnostics functions
6.33.1
Description of MOD_D8_PN
Object name (type + number) FB 197 · I/Os of MOD_D8_PN (Page 203)
Area of application
Block MOD_D8_PN monitors S7-300 SM modules with a maximum of 8 channels and with diagnostics functions.
6.33.2
I/Os of MOD_D8_PN
The factory setting of the block display in the CFC is identified in the "I/O" column:
I/O name bold = I/O visible, I/O name normal = I/O not visible.
You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15)".
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
203
Family: @System 6.33 MOD_D8_PN: Monitoring S7-300 SM modules with up to 8 channels and with diagnostics functions
Input parameters
I/O (parameter) CHAN_NUM DELAY1 DELAY2 DIAG_BUF
EN_MSG EV_IDx
FEATURE_xx FEATURE_yy LADDR LADDR1
MODE_xx
MS MS_REQ RACK_NO SLOT_NO SUBSL_NO SUBN_TYP SUBN1_ID SUBN2_ID
Meaning
Data type Default
Total number of channels -1
INT
0
Alarm delay 1 (s)
INT
2
Alarm delay 2 (s)
INT
2
Entry in diagnostic buffer (relevant for maintenance BOOL
0
personnel)
1 = Enable message
BOOL
1
Message number ALARM_8P_x (x = 1 - 2/1 - 3/1 - 4, assigned by the ES)
DWORD
0
Feature parameter (xx = 01 - 04)
WORD
0
Feature parameter (yy = 05 - 10)
DWORD
0
Logic input address of the module
INT
0
Logical output address of the module (if output ad- INT
0
dress is not the same as input address).
Operating mode channel xx (xx = 00 - 07/00 - 15/00 - DWORD
0
23)
Maintenance status
DWORD
0
1 = Request maintenance release
BOOL
0
Rack number
BYTE
0
Slot number
BYTE
0
Subslot number
BYTE
0
1 = external PN interface
BOOL
0
PN IO system 1 ID (100 - 115)
BYTE
255
PN IO system 2 ID (100 - 115)
BYTE
255
Output parameters
I/O (parameter) CH_ACTIVE
CH_EXIST CH_OK DIAG_INFx DM_ACTIVE DXCHG_xx DXCHG1_xx
EXT_STATx EXT_STAT_A
FS_ACTIVE
Meaning
Data type Default
Channel active
DWORD
Channel exists
DWORD
Channel OK
DWORD
System structure: Diagnostic information
STRUCT
Fault delay
DWORD
1st internal data exchange channel for channel block DWORD
2nd internal data exchange channel for channel block
DWORD
Release for maintenance - extended status
DWORD
Extended status - Application
DWORD
Application data transfer active
Flutter suppression active
DWORD
16#0000000 0 0 0 0 16#0 0 0
0 0
16#0000000 0
204
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.33 MOD_D8_PN: Monitoring S7-300 SM modules with up to 8 channels and with diagnostics functions
I/O (parameter) MOD_INF MS_XCHG_xx
MSG_ACKx MSGSTATx O_MS OMODE_xx
QERR QMODF QPERAF QRACKF
Meaning
Data type Default
System structure: Module parameter
STRUCT
Maintenance Status - Data exchange channel (xx = DWORD
0
00 - 63)
Message acknowledgment (x = 1 - 2/1 - 3/1 - 4)
WORD
0
Message error information (x = 1 - 2/1 - 3/1 - 4)
WORD
0
Maintenance status
DWORD
0
Operating mode channel xx (xx = 00 - 07/00 - 15/00 DWORD
0
- 23)
1 = program error
BOOL
1
1 = module removed/defective
BOOL
0
1 = I/O access error
BOOL
0
1 = higher-level error
BOOL
0
In/out parameters
I/O (parameter) ACC_MODE CPU_DIAG_PN RAC_DIAG
Meaning
1 = accept MODE settings System structure: CPU diagnostics System structure: Rack diagnostics
Data type
BOOL STRUCT STRUCT
Default 0
Additional information For additional information, refer to the sections: Message texts and associated values of MOD_D8_PN (Page 205) Maintenance status MS (Page 533)
6.33.3
Message texts and associated values of MOD_D8_PN
Assignment of message text and message class The process control messages of ALARM_8P with EV_ID1 are assigned as follows:
Message block ALARM_8P
EV_ID1
Message number
1
2
Default message text
Message class
Module @1%d@/@2%d@/@3%d@/ @6%d@: Failure
Module @1%d@/@2%d@/@3%d@/ @6%d@: @5W%t#MOD_D8_PN_TXT@
PLC Process Control Message Failure
PLC Process Control Message Error
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
205
Family: @System 6.33 MOD_D8_PN: Monitoring S7-300 SM modules with up to 8 channels and with diagnostics functions
Message block ALARM_8P
Message number
3
4 5
6 7
8
Default message text
Message class
Module @1%d@/@2%d@/@3%d@/ @6%d@: @5W%t#MOD_D8_PN_TXT@ Module @1%d@/@2%d@/@3%d@/ @6%d@: Multiple diagnostics interrupt Module @1%d@/@2%d@/@3%d@/ @6%d@: @4W%t#MOD_D8_PN_TXT@ No message
Module @1%d@/@2%d@/@3%d@/ @6%d@: Maintenance demanded (external) Module @1%d@/@2%d@/@3%d@/ @6%d@: Maintenance required (external)
PLC Process Control Message Failure
PLC Process Control Message Error PLC Process Control Message Failure
Preventative Maintenance Standard PLC Process Control Message Error
Preventative Maintenance Standard
Associated values of ALARM_8P with EV_ID1
Associated value 1 2 3 4 5 6
Block parameter ID of the PN IO system Rack/station number Slot number Text number (message 5) from MOD_D8_PN_TXT Text number (message 3) from MOD_D8_PN_TXT Subslot number
Data type BYTE BYTE BYTE BYTE BYTE BYTE
The process control messages of ALARM_8P with EV_ID2 are assigned as follows:
Message block ALARM_8P
EV_ID2
Message number
1
2
3
4
Default message text
Module @1%d@/@2%d@/@3%d@/ @5%d@: Error channel 00 @4W%t# MOD_D8_PN_TXT @ Module @1%d@/@2%d@/@3%d@/ @5%d@: Error channel 01 @4W%t# MOD_D8_PN_TXT @ Module @1%d@/@2%d@/@3%d@/ @5%d@: Error channel 02 @4W%t# MOD_D8_PN_TXT @ Module @1%d@/@2%d@/@3%d@/ @5%d@: Error channel 03 @4W%t# MOD_D8_PN_TXT @
Message class
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
206
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
6.34
Family: @System 6.34 MOD_D8_S7P: Diagnostic module check (<=8 channels)
Message block ALARM_8P
Message number
5
6
7
8
Default message text
Module @1%d@/@2%d@/@3%d@/ @5%d@: Error channel 04 @4W%t# MOD_D8_PN_TXT @ Module @1%d@/@2%d@/@3%d@/ @5%d@: Error channel 05 @4W%t# MOD_D8_PN_TXT @ Module @1%d@/@2%d@/@3%d@/ @5%d@: Error channel 06 @4W%t# MOD_D8_PN_TXT @ Module @1%d@/@2%d@/@3%d@/ @5%d@: Error channel 07 @4W%t# MOD_D8_PN_TXT @
Message class
EPLC Process Control Mes- sage - Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
Associated values of ALARM_8P with EV_ID2
Associated value 1 2 3 4 5
Block parameter ID of the PN IO system Rack/station number Slot number Text number from MOD_D8_PN_TXT Subslot number
Data type BYTE BYTE BYTE BYTE BYTE
You will find the message texts and their text numbers in the section Text library for MOD_D8_PN (FB197) / MOD_D16_PN (FB198) / MOD_D24_PN (FB199) / MOD_ENME (FB 419) (Page 542).
You can find additional information in the section: Message Classes (Page 531)
MOD_D8_S7P: Diagnostic module check (<=8 channels)
6.34.1
Description of MOD_D8_S7P
Object name (type + number) FB 433 · I/Os of MOD_D8_S7P (Page 208)
Area of application
The MOD_D8_S7P block creates the device specific DP S7+ diagnostics information for modules with 8 channels.
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
207
Family: @System 6.34 MOD_D8_S7P: Diagnostic module check (<=8 channels)
Calling OBs
The cyclic OB 1 and OB 82, OB 83, OB 85, OB 86 and OB 100.
Use in CFC
The following actions are executed automatically with the "Generate module drivers" CFC function:
· If a module with 8 channels is available in HW configuration, an instance of the diagnostic function block MOD_D8_S7P is added to the system charts of the project.
· Information from HW configuration is read and the input parameters of MOD_D8_S7P are parameterized correspondingly.
The MOD_D8_S7P gets connected with the corresponding channel blocks of the IO module.
Startup characteristics Initialization of the ALARM_8P blocks.
6.34.2
I/Os of MOD_D8_S7P
I/Os of MOD_D8_S7P The factory setting of the block display in the CFC is identified in the "I/O" column.
I/O name bold = I/O visible, I/O name normal = I/O not visible.
You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15)".
Input parameters
I/O (parameter) CHAN_NUM DELAY1 DELAY2 DIAG_BUF
EN_MSG EV_ID1 EV_ID2 FEATURE LADDR LADDR1 MODE_xx MS
Meaning
Type
Total number of channels - 1
INT
Interrupt delay 1 (s)
INT
Interrupt delay 2 (s)
INT
Entry in diagnostic buffer (relevant for maintenance person- BOOL nel)
1 = Enable message
BOOL
Message number 1
DWORD
Message number 2
DWORD
Feature parameter
DWORD
Logical address of the module
INT
Reserve
INT
Channel xx mode (xx = 00...07)
DWORD
Maintenance status
DWORD
Default 0 2 2 0
1 16#0 16#0 0 -1 -1 0 16#0
208
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.34 MOD_D8_S7P: Diagnostic module check (<=8 channels)
I/O (parameter) MS_REQ RACK_NO SLOT_NO SUBN_TYP SUBN1_ID SUBN2_ID
Meaning 1 = Request maintenance release Rack number Slot number 1 = External DP interface ID of Primary subnet ID of Redundant subnet
Type BOOL BYTE BYTE BOOL BYTE BYTE
Default 0 0 0 0 255 255
Out parameters
I/O (parameter) CH_ACTIVE CH_EXIST CH_OK DIAG_INF DM_ACTIVE DXCHG_xx
DXCHG1_xx
EXT_STAT
EXT_STAT_A FS_ACTIVE MOD_INF MS_XCHG_xx
MSGSTAT1 MSGSTAT2 MSG_ACK1 MSG_ACK2 OMODE_xx O_MS QREC_VAL QREC_ERR QSTATUS QERR QMODF QPERAF QRACKF
Meaning
Type
Channel active
DWORD
Channel exists
DWORD
Channel OK
DWORD
System structure: Diagnostic information STRUCT
Fault delay
DWORD
1st internal data exchange channel for channel block (xx = 00...07)
DWORD
2nd internal data exchange channel for DWORD channel block (xx = 00...07)
Release for maintenance - extended sta- DWORD tus
Extended Status Application
DWORD
Flutter suppression
DWORD
System structure: Module parameter
STRUCT
Maintenance Status - Data exchange channel (xx = 00...07)
DWORD
Message failure 1
WORD
Message failure 2
WORD
Message acknowledged 1
WORD
Message acknowledged 2
WORD
Channel xx mode (xx = 00...07)
DWORD
Maintenance status
DWORD
1 = Received new data record
BOOL
1 = Error read data record
BOOL
Status read data record
DWORD
1 = program error
BOOL
1 = Module pulled/defective
BOOL
1 = I/O access error
BOOL
1 = higher level error
BOOL
Default 0 0 0
0 16#0
16#0
0
0 0
0
0 0 0 0 0 0 0 0 0 1 0 0 0
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
209
Family: @System 6.34 MOD_D8_S7P: Diagnostic module check (<=8 channels)
In/out parameters
I/O (parameter) Meaning
ACC_MODE CPU_DIAG RAC_DIAG
1 = Apply MODE settings System structure: CPU diagnostics System structure: RACK diagnostics
Type
BOOL STRUCT STRUCT
De- fault 0
0
6.34.3
Message texts and associated values of MOD_D8_S7P
Assignment of message text and message class The process control messages of ALARM_8P with EV_ID1 are assigned as follows:
Message block ALARM_8P
EV_ID1
Mes- Event sage number
Message class
1
Module @1%d@/@2%d@/@3%d@: Maintenance PLC Process Control
alarm
Message - Failure
2
Module @1%d@/@2%d@/@3%d@: Maintenance de- PLC Process Control
manded (external)
Message - Error
3
Module @1%d@/@2%d@/@3%d@: @5W
%t#MOD_D8_S7P_TXT@
PLC Process Control Message - Failure
4
Module @1%d@/@2%d@/@3%d@: Maintenance de- PLC Process Control
manded
Message - Error
5
Module @1%d@/@2%d@/@3%d@: @4W
%t#MOD_D8_S7P_TXT@
PLC Process Control Message - Failure
6
Module @1%d@/@2%d@/@3%d@: Maintenance re- Preventative Mainte-
quired
nance - Standard
7
Module @1%d@/@2%d@/@3%d@: @5W
%t#MOD_D8_S7P_TXT@
PLC Process Control Message - Error
8
Module @1%d@/@2%d@/@3%d@: Maintenance re- Preventative Mainte-
quired (external)
nance - Standard
Associated values of ALARM_8P with EV_ID1
Associated value 1 2 3
Block parameter DP master system number Rack number/Station number Slot number
Data type BYTE BYTE BYTE
210
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.35 MOD_DRV: Monitoring of drive blocks with diagnostics functions
The process control messages of ALARM_8P with EV_ID2 are assigned as follows:
Message block ALARM_8P
EV_ID2
Message number
Event
Message class
1
Module @1%d@/@2%d@/@3%d@: Error chan- PLC Process Control
nel 00 @4W%t#MOD_ D8_S7P_TXT@
Message - Failure
2
Module @1%d@/@2%d@/@3%d@: Error chan- PLC Process Control
nel 01 @4W%t#MOD_ D8_S7P_TXT@
Message - Failure
3
Module @1%d@/@2%d@/@3%d@: Error chan- PLC Process Control
nel 02 @4W%t#MOD_ D8_S7P_TXT@
Message - Failure
4
Module @1%d@/@2%d@/@3%d@: Error chan- PLC Process Control
nel 03 @4W%t#MOD_ D8_S7P_TXT@
Message - Failure
5
Module @1%d@/@2%d@/@3%d@: Error chan- PLC Process Control
nel 04 @4W%t#MOD_ D8_S7P_TXT@
Message - Failure
6
Module @1%d@/@2%d@/@3%d@: Error chan- PLC Process Control
nel 05 @4W%t#MOD_ D8_S7P_TXT@
Message - Failure
7
Module @1%d@/@2%d@/@3%d@: Error chan- PLC Process Control
nel 06 @4W%t#MOD_ D8_S7P_TXT@
Message - Failure
8
Module @1%d@/@2%d@/@3%d@: Error chan- PLC Process Control
nel 07 @4W%t#MOD_ D8_S7P_TXT@
Message - Failure
Associated values of ALARM_8P with EV_ID2
Associated value 1 2 3 4
Block parameters DP Master system number Rack number/Station number Slot number Text number from MOD_ D8_S7P_TXT
Data type BYTE BYTE BYTE BYTE
You can find the message texts and their text numbers in the section: Text library for MOD_ D8_S7P, MOD_ D16_S7P (Page 545).
You can find additional information in the section: Message Classes (Page 531).
6.35
MOD_DRV: Monitoring of drive blocks with diagnostics functions
6.35.1
Description of MOD_DRV
Object name (type + number) FB 148 · Block interfaces of MOD_DRV (Page 212)
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
211
Family: @System 6.35 MOD_DRV: Monitoring of drive blocks with diagnostics functions
Area of application The MOD_DRV block creates a device-specific diagnostics function for devices of the Drive type.
Calling OBs
The cyclic OB 1 and OB 100.
Use in CFC
The following actions are executed automatically with the "Generate module drivers" CFC function:
· The block is installed when the corresponding SlaveFamily 1 object exists
· The corresponding inputs are interconnected and configured.
· The block is interconnected with the corresponding channel block.
Startup characteristics Initialization of the ALARM_8P blocks and of the NOTIFY_8P blocks.
Message response The block reports errors using ALARM_8P and NOTIFY_8P.
MODE response The output OMODE shows the device type. A distinction is made between the device and type or profile respectively. Only the Drive type is currently implemented. It has the value 16#XXXX0010.
6.35.2 I/Os
I/Os of MOD_DRV
The factory setting of the block display in the CFC is identified in the "I/O" column. I/O name bold = I/O visible, I/O name normal = I/O not visible. You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15)".
212
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Input parameters
Parameter
EN_MSG EV_ID1 EV_ID2 LINK_ADR MS MS_REQ PADP_ADR SUBN1_ID SUBN2_ID PORT_ERR
Family: @System 6.35 MOD_DRV: Monitoring of drive blocks with diagnostics functions
Description
1 = Enable message Message number 1 Message number 2 Link address Maintenance status 1 = Request maintenance release Address of the PA field device ID of the primary DP master system ID of the redundant DP master system Port error
Type
BOOL DWORD DWORD BYTE DWORD BOOL BYTE BYTE BYTE STRUCT
De- fault
1 16#00 16#00 0 16#00 0 16#00 16#FF 16#FF
In/out parameters
Parameter CPU_DIAG
RAC_DIAG
Description System structure: CPU diagnostics
System structure: RACK diagnostics
Type
Struct (Siehe OB_BE- GIN)
Struct (Siehe OB_DI- AG1)
Output parameters
Parameter
CH_ACTIVE
CH_EXIST
CH_OK
DXCHG_xx DXCHG1_xx EN_RST_DIAG Error Error_Rst EXT_STAT EXT_STAT_A
MS_XCHG_00 MSG_ACK1
Description
Channel active
Channel exists
Channel OK
1st internal data exchange channel for channel block 2nd internal data exchange channel for channel block Reset enable Error message is active Message error reset active Release for maintenance - extended status Extended status - Application Application data transfer active Maintenance Status - Data exchange channel Message acknowledgment 1
Type
DWORD
DWORD
DWORD
DWORD DWORD BOOL BOOL BOOL DWORD DWORD
DWORD WORD
De- fault
16#00 00000 0 16#00 00000 0 16#00 00000 0 16#00 0 0 0 0 16#00 0
0 16#00
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
213
Family: @System 6.35 MOD_DRV: Monitoring of drive blocks with diagnostics functions
Parameter
MSG_ACK2 MsgNamurAct MSGSTAT1 MSGSTAT2 Namur1 Namur2 Namur3 Namur4 Namur5 Namur6 Namur7 Namur8 Namur9 Namur10 Namur11 Namur12 Namur13 Namur14 Namur15 Namur16 Namur1_Rst Namur2_Rst Namur3_Rst Namur4_Rst Namur5_Rst Namur6_Rst Namur7_Rst Namur8_Rst Namur9_Rst Namur10_Rst Namur11_Rst Namur12_Rst Namur13_Rst Namur14_Rst Namur15_Rst Namur16_Rst O_MS OMODE_00 QERR QRACKF Warning Warning_Rst
Description
Message acknowledgment 2 Namur message is active Message error information 1 Message error information 2 Namur1 message is active Namur2 message is active Namur3 message is active Namur4 message is active Namur5 message is active Namur6 message is active Namur7 message is active Namur8 message is active Namur9 message is active Namur10 message is active Namur11 message is active Namur12 message is active Namur13 message is active Namur14 message is active Namur15 message is active Namur16 message is active Message Namur1 reset active Message Namur2 reset active Message Namur3 reset active Message Namur4 reset active Message Namur5 reset active Message Namur6 reset active Message Namur7 reset active Message Namur8 reset active Message Namur9 reset active Message Namur10 reset active Message Namur11 reset active Message Namur12 reset active Message Namur13 reset active Message Namur14 reset active Message Namur15 reset active Message Namur16 reset active Maintenance status Value status of the PA field device 1 = program error 1 = higher-level error Warning message is active Message warning reset active
Type
WORD BOOL WORD WORD BOOL BOOL BOOL BOOL BOOL BOOL BOOL BOOL BOOL BOOL BOOL BOOL BOOL BOOL BOOL BOOL BOOL BOOL BOOL BOOL BOOL BOOL BOOL BOOL BOOL BOOL BOOL BOOL BOOL BOOL BOOL BOOL DWORD DWORD BOOL BOOL BOOL BOOL
De- fault
16#00 0 16#00 16#00 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 16#00 16#00 1 0 0 0
214
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
6.35.3
Family: @System 6.35 MOD_DRV: Monitoring of drive blocks with diagnostics functions
Message texts and associated values of MOD_DRV
Assignment of message text and message class The process control messages of ALARM_8P with EV_ID1 are assigned as follows:
Message block ALARM_8P
EV_ID1
Message number
1
2
3
4 5 6
7
8
Event
Message class
Device @1%d@/@2%d@: Maintenance alarm Device @1%d@/@2%d@: Maintenance demanded Device @1%d@/ @2%d@: Maintenance required
Device @1%d@/ @2%d@: Failure
Device @1%d@/ @2%d@: Maintenance demanded (external) Device @1%d@/ @2%d@: Maintenance required (external)
PLC Process Control Message Failure
PLC Process Control Message Error
Preventative Maintenance Standard
No message
No message
PLC Process Control Message Failure
PLC Process Control Message Error
Preventative Maintenance Standard
Associated values of ALARM_8P with EV_ID1
Associated value 1 2
Block parameters Subnet Address
The process control messages of NOTIFY_8P with EV_ID2
Data type BYTE BYTE
Message block NOTI- FY_8P
EV_ID2
Mes- sage number 1 2
3 4 5 6
7 8
Event
Device @1%d@/ @2%d@: Making configuration change Device @1%d@/ @2%d@: Simulation Device @1%d@/ @2%d@: ready to start Device @1%d@/ @2%d@: ready to operate Device @1%d@/@2%d@: Local operation/function check Device @1%d@/@2%d@: Device disabled
Message class
No message Status Message - PLC
Status Message - PLC Status Message - PLC Status Message - PLC Status Message - PLC
Status Message - PLC No message
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
215
Family: @System 6.36 MOD_HA: Monitoring device-specific diagnostics of HART field devices
Associated values of NOTIFY_8P with EV_ID2
Associated value 1 2
Block parameter Subnet Address
Data type BYTE BYTE
The process control messages of ALARM_8P with EV_ID3 are assigned as follows:
Message block ALARM_8P
EV_ID3
Message number
1
2
3
4
5 6 7 8
Event
Message class
Device 1%d@/@2%d@: Port 1 error
PLC Process Control Message Error
Device 1%d@/@2%d@: Port 2 error
PLC Process Control Message Error
Device 1%d@/@2%d@: Maintenance de- PLC Process Control Message -
manded
Error
Device 1%d@/@2%d@: Maintenance re- Preventative Maintenance -
quired
Standard
No message
No message
No message
No message
Associated values of ALARM_8P with EV_ID3
Associated value 1 2
Block parameter Subnet Address
Data type BYTE BYTE
See also
Message Classes (Page 531)
6.36
MOD_HA: Monitoring device-specific diagnostics of HART field devices
6.36.1
Description of MOD_HA
Object name (type + number) FB 97 · MOD_HA block I/Os (Page 222)
216
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.36 MOD_HA: Monitoring device-specific diagnostics of HART field devices
Area of application The MOD_HA module reports diagnostic events of an HART field device that is connected to a channel of an ET 200M HART module or ET 200iSP HART module. HART modules of ET 200iS are not supported. H systems support only the modules installed in switched racks.
Calling OBs
The block must be installed in the run sequence in the following OBs:
OB 1 OB 82 OB 83 OB 85 OB 86 OB 100
Cyclic program Diagnostic interrupt Insert/remove module interrupt Program execution error Rack failure Warm restart
Use in CFC
The following actions are executed automatically with the "Generate module drivers" CFC function:
· The block is installed downstream of the diagnostic block that is responsible for the HART module.
· LADDR (logical base address of the HART module) is configured.
· The geographic addresses SUBN1_ID, SUBN2_ID, RACK_NO, SLOT_NO, and CHAN_NO (channel number of the HART module to which the HART field device is connected) are configured.
· The CPU_DIAG structures of the OB_BEGIN block are interconnected
· The EN input is interconnected with the output of an AND block. The block inputs are interconnected with the outputs EN_SUBx (x = number of the DP master system) of the OB_BEGIN block, EN_Rxxx (xxx = rack/station number) of the SUBNET block, and EN_Mxx (xx = module number) of the RACK block and MODE with OMODE_xx of the diagnostic block.
· The DXCHG output parameter is interconnected with the following channel block at the DataXchg parameter.
· The O_MS output parameter is interconnected with the following channel block at the MS parameter.
Function and method of operation
Block MOD_HA analyzes events relating to a HART field device acyclically. ALARM_8P is used to report these events. The message function can be disabled.
The block is enabled to run by the higher-level RACK block. By default, MOD_HA requires synchronous diagnostic data in OB 82 (additional alarm information with SFB 54 call by OB_BEGIN). With an ET 200iSP HART module, the channel type 16#65 is generated during diagnostics. Here, 2 bytes of diagnostic information are defined per channel of the module, and
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
217
Family: @System 6.36 MOD_HA: Monitoring device-specific diagnostics of HART field devices
the block reports the statuses of the 2nd bit of the 1st byte and the 2nd byte for the respective HART field device.
Structure of byte 1 (ET 200iSP HART):
Bit
Meaning
0
Parameter assignment error (HART module)
1
HART communications error (HART module)
2
Readback error (HART module)
3
Short circuit (HART module)
4
Wire break (HART module)
5
No load voltage (HART module)
6
Overflow (HART module)
7
Underflow (HART module)
Structure of byte 2 (ET 200iSP HART):
Bit
Meaning
0
Primary variable outside limits (field device)
1
Secondary variable outside limits (field device)
2
Analog output saturated (field device)
3
Analog output current specified (field device)
4
More statuses available (field device)
5
Reserved for maintenance alarm (field device)
6
Reassignment the field device parameters
7
Malfunction of the field device
For an ET 200M with two-channel HART modules, channel type 16#61 or 16#63 is generated during diagnostics. Bit 5 in byte 8 for channel 0 and byte 9 for channel 1 in the additional alarm information means "HART channel error". If bit 5 = TRUE, the additional diagnostic data is read with SFB 52 (RDREC) as follows:
· with data record 128 for channel 0
· with data record 129 for channel 1
Diagnostic data records 128 (for channel 0) and 129 (for channel 1) have the same structure. and return detailed HART diagnostic information on the previous transfer. The table below shows the individual error messages/warnings.
Byte/Bit No. 0: general
1: fault groups = group error
7
1= Mod. comm. Channel fault (L+, DrBr)
6
5
No. of (triggering) client,
if module com No. =0
HART
HART
channel fault
slave com- munication
4
HART command error
then bytes -
2
8
8
3
2
1
0
Polling address (of HART transducer),
always 0 for monodrop
device sta- tus <> 0 (e.g., config- uration changed)
more status
Com-
0 = Not used
mand re-
jected
9
-
-
-
218
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.36 MOD_HA: Monitoring device-specific diagnostics of HART field devices
Byte/Bit No.
2: HART cf = "communica- tion faults" Field device for module 3 to 6: time stamp 7: HART/ module 8: HART ce
9: HART ds
7
HART ac- cess not possible
6
parity error in re- sponse
5
overrun error in re- sponse
4
framing er- ror in re- sponse
3
wrong checksum in response
2
Wrong char timing
1
0
too
wrong tele-
many gram timing
chars in
response
Broadcast system time: Milliseconds (10s and 100s), seconds, minutes, and hours in two-digit BCD code. If the timestamp function is not used: Content = 0
last HART or module command
1
"Communication error bits" of "slave", (first status byte)
0
"Command response" list - no errors, but warnings
Device status bits (second status byte)
Two HART status bytes are reserved in the HART protocol to display errors and warnings. These are entered in diagnostic data records 128 and 129 unchanged. The meaning of the HART status bytes is defined in the HART Standard.
· First HART status byte (meaning depends on bit 7):
Bit 7 = 1: Communication error during the transmission of a HART command to the field device
Bit 7 = 0: Only warnings that the field device sends in response to a command
Bit 7/Bit No.
7
Either
1
Bit 7 = 1:
HART
"communication error" from mod- ule to field device
or
0
Bit 7 = 0:
HART
"response to a command"
6
5
parity error overrun er- in command ror in com-
mand
4
framing er- ror in com- mand
3
wrong checksum in command
2
1
0
Reserved = 0 too many char- (unde- acters in com- fined) mand
(rx buffer over- flow)
The messages in bits 0 - 6 are coded as integers: 0: No command-specific error 1: Undefined 2: Invalid section 3: Transferred parameter too large 4: Transferred parameter too small 5: Too few data bytes received 6: Device-specific command error (rarely used) 7: In write-protected mode 8-15: Various meanings (see code commands) 16: Restricted access 28: Various meanings (see code commands) 32: Device is busy 64: Command not implemented
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
219
Family: @System 6.36 MOD_HA: Monitoring device-specific diagnostics of HART field devices
Code 8 *)
9
10
11
12 13 14 *) 15 28
Commands 1,2,3,33,60,61,62, 110,34,55,64,48 35,65,36,37,43,52,45,46,67,68
6,35,65,36,37,43,52
35,65,40,45,46,66,67,68,53
35,65,53,66,67,68 35,65,69 35,36,65,37 65,66,67,68,69 65
Alternative meanings
"Update" error set to nearest possible value, "Update" being executed Lower range limit too high, "applied process" too high, not in correct current mode (fixed at 4 mA or 20 mA) Multidrop is not supported Lower range limit too low, "applied process" too low, Upper range limit too high, In multidrop mode, bad transmitter variable code Upper range limit too low, bad units code Both range limits outside the limit value, bad transfer function code Span too limited, "pushed" upper range limit outside the limit Faulty code for the number of the analog output bad code for the range unit ("range units code")
· Second HART status byte: Device status of the HART field device in the event of a communication error (otherwise, byte = 0)
Bit No.
HART de- vice sta- tus:
"field de- vice sta- tus"
7
Malfunction of the field device
6
Reassign- ment of pa- rameters:
"configura- tion changed (CC)"
5
Cold re- start
4
Further sta- tus available
"more sta- tus"
3
Analog output current speci- fied
("fixed)"
2
Analog out- put satura- ted
1
Non-pri- mary varia- ble outside limits
0
Primary varia- ble outside limits
Process control messages are generated when "communication errors" and HART field device errors (byte 9 <> 0) occur. Operating messages with acknowledgment are generated if bit 7 = 0 (byte 8) and the remaining bits <> 0. The last read data record 128 or 129 (depending on the channel number) is written to the output structure DIAG_H.
Bytes 8 and 9 are evaluated and event messages generated in OB 1. You can find additional information about this in the section "Message texts and associated values of MOD_HA (Page 224)".
The MODE input is interconnected with the corresponding OMODE_xx output of the diagnostic block. The module channel configurations set in HW Config are reported at these locations.
220
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.36 MOD_HA: Monitoring device-specific diagnostics of HART field devices
MODE (Page 517) is written to the low word of theOMODE (Page 527) output parameter. This occurs only during startup or if you set ACC_MODE = TRUE. The current channel value status is written to the most significant byte. If valid, OMODE = 16#80xxxxxx. The diagnostic block contains the events that lead to a value status "invalid value due to higher-priority error" (OMODE = 16#40xxxxxx), or to channel error (OMODE = 16#00xxxxxx).
Redundancy
The higher-level RACK block evaluates the redundancy of DP master systems operating in an H system. Redundant HART field devices are not supported.
Error handling The plausibility of input parameters is not checked.
Startup characteristics A restart (OB 100) is reported via the LSB in byte 2 of the OMODE (Page 527) output. ALARM_8P will be initialized.
Overload behavior
The MOD_HA block counts the OB 82 calls. The counter is reset in OB1. A diagnostic message will not be generated if more than five OB 82 events occur before the cycle control point is reached (OB 1). A "multiple diagnostic interrupt" message will not be generated, because the diagnostic block performs this action.
Time response Not available
Message response
MOD_HA reports diagnostic information from a HART field device by means of ALARM_8P or NOTIFY_8P.
The message function can be disabled by setting EN_MSG = FALSE.
Operator control and monitoring
If asset management is used in the project and the diagnostic screens have been generated, the faceplate can be called via its block icon.
For additional information, refer to the "Process Control System PCS 7; Maintenance Station" manual.
Additional information For additional information, refer to the sections:
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
221
Family: @System 6.36 MOD_HA: Monitoring device-specific diagnostics of HART field devices
Message texts and associated values of MOD_HA (Page 224) Maintenance status MS (Page 533) You can also find additional information on this in PCS 7 Advanced Process Library > Basics of APL > General functions of the blocks > Operating, monitoring and reporting > Release for maintenance
6.36.2
I/Os of MOD_HA
The factory setting of the block display in the CFC is identified in the "I/O" column: I/O name bold = I/O visible, I/O name normal = I/O not visible.
You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15)".
Input parameters
I/O (parameter) CHAN_NO DIAG_BUF EN_MSG EV_ID LADDR MODE MS MS_REQ RACK_NO SLOT_NO SUBN_TYP SUBN1_ID SUBN2_ID
Meaning
Type
Channel number
BYTE
Entry in diagnostic buffer (relevant for maintenance personnel) BOOL
1 = Enable message
BOOL
Message number
DWORD
Logical address of the channel
INT
Channel operating mode
DWORD
Maintenance status
DWORD
1 = Request maintenance release
BOOL
Rack number
BYTE
Slot number
BYTE
1 = external DP interface
BOOL
ID of the primary DP master system
BYTE
ID of the redundant DP master system
BYTE
Default
0 0 1 0 0 0 0 0 0 0 0 255 255
Output parameters
I/O (parameter) CH_ACTIVE CH_EXIST CH_OK DIAG_H
DM_ACTIVE DXCHG_xx
Meaning
Type
Channel active Channel exists Channel OK Diagnostic information of HART communication chan- nel Fault delay 1st internal data exchange channel for channel block
DWORD DWORD DWORD STRUCT
DWORD DWORD
Default 16#00000000 16#00000000 16#00000000
16#0 0
222
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.36 MOD_HA: Monitoring device-specific diagnostics of HART field devices
I/O (parameter) DXCHG1_xx EXT_STAT EXT_STAT_A
FS_ACTIVE MS_XCHG MSG_ACK MSGSTAT QERR O_MS OMODE QPERAF QREC_ERR QREC_VAL STATUS
Meaning
Type
2nd internal data exchange channel for channel block Release for maintenance - extended status Extended status - Application Application data transfer active Flutter suppression Maintenance Status - Data exchange channel Message acknowledgment Message error information 1 = program error Maintenance status Channel operating mode 1 = I/O access error 1 = Read diagnostic data error 1 = Read diagnostic data Read diagnostics status
DWORD DWORD DWORD
DWORD DWORD WORD WORD BOOL DWORD DWORD BOOL BOOL BOOL DWORD
Default 0 0 0
16#00000000 0 0 0 1 0 0 0 0 0 0
In/out parameters
I/O (parameter) ACC_MODE CPU_DIAG DXCHG_IN DXCHG1_IN MS_XCHG_IN
Meaning
1 = accept MODE settings CPU diagnostics Bidirectional data exchange channel Bidirectional data exchange channel - HART channel Maintenance Status - Data exchange channel
Type
BOOL STRUCT DWORD DWORD DWORD
Default 0
0 0 0
Additional information For additional information, refer to the sections: Message texts and associated values of MOD_HA (Page 224) Maintenance status MS (Page 533)
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
223
Family: @System 6.36 MOD_HA: Monitoring device-specific diagnostics of HART field devices
6.36.3
Message texts and associated values of MOD_HA
Assignment of message text and message class
Message block Message no.
EV_ID
1
(ALARM_8P)
2
3
4 5 6 7
8
EV_ID1
1
(NOTIFY_8P)
2
3
4 5 6 7 8
Default message text
Message class
HART field device@1%d@/
PLC Process Control Message -
@2%d@/@3%d@/@4%d@: Main- Failure
tenance alarm
HART field device@1%d@/
PLC Process Control Message - Er-
@2%d@/@3%d@/@4%d@: Main- ror
tenance demanded
HART field device@1%d@/
Preventative Maintenance -
@2%d@/@3%d@/@4%d@: Main- Standard
tenance required
No message
No message
No message
HART field device @1%d@/ @2%d@/@3%d@:
PLC Process Control Message - Er- ror
Maintenance demanded (exter- nal)
HART field device @1%d@/ @2%d@/@3%d@:
Preventative Maintenance Standard
Maintenance required (external)
HART field device@1%d@/
Status Message - PLC
@2%d@/@3%d@/@4%d@: Re-pa-
rameterization
HART field device@1%d@/ @2%d@/@3%d@/@4%d@: Cold restart
Status Message - PLC
HART field device @1%d@/
Status Message - PLC
@2%d@/@3%d@/@4%d@: Addi-
tional status available
No message
No message
No message
No message
No message
Assignment of associated values
Message block ALARM_8P
EV_ID
Associated value
1 2 3 4
Block parameter
SUBN_ID RACK_NO SLOT_NO CHAN_NO
Meaning
DP master system ID (byte) Rack/station number (byte) Slot number (byte) Channel error text number
224
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
See also
Family: @System 6.37 MOD_HA_PN: Monitoring Device-Specific Diagnostics of HART Field Devices
Message block Associated
ALARM_8P
value
Block parameter
Meaning
EV_ID1
1
2
3
4
SUBN_ID RACK_NO SLOT_NO CHAN_NO
DP master system ID (byte) Rack/station number
If SUBN1_ID = 16#FF, the associated value is substituted with SUBN2_ID.
Message Classes (Page 531)
6.37
MOD_HA_PN: Monitoring Device-Specific Diagnostics of HART Field Devices
6.37.1
Description of MOD_HA_PN
Object name (type + number) FB 200 · I/Os of MOD_HA_PN (Page 225)
Area of application The MOD_HA_PN module reports diagnostic events of an HART field device.
6.37.2
I/Os of MOD_HA_PN
The factory setting of the block display in the CFC is identified in the "I/O" column: I/O name bold = I/O visible, I/O name normal = I/O not visible.
You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15)".
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
225
Family: @System 6.37 MOD_HA_PN: Monitoring Device-Specific Diagnostics of HART Field Devices
Input parameters
I/O (parameter) CHAN_NO DIAG_BUF
EN_MSG EV_IDx
LADDR LADDR1 MODE MS MS_REQ RACK_NO SLOT_NO SUBN_TYP SUBN1_ID SUBN2_ID
Meaning
Type
Channel number Entry in diagnostic buffer (relevant for maintenance personnel) 1 = Enable message Message number ALARM_8P_x (x = 1 - 2, assigned by the ES) Logical address of the channel Logical address of the redundant channel Channel operating mode Maintenance status 1 = Request maintenance release Rack number Slot number 1 = external PN interface PN IO system 1 ID (100 - 115) PN IO system 1 ID (100 - 115)
BYTE BOOL
BOOL DWORD
INT INT WORD DWORD BOOL BYTE BYTE BOOL BYTE BYTE
Default
0 0
1 0
0 0 0 0 0 0 0 0 255 255
Output parameters
I/O (parameter) CH_ACTIVE CH_EXIST
Meaning
Channel active Channel exists
Type
Default
DWORD DWORD
16#00000000 16#00000000
CH_OK DIAG_H
DM_ACTIVE DXCHG_xx DXCHG1_xx EXT_STAT EXT_STAT_A
FS_ACTIVE MS_XCHG MSG_ACK MSGSTAT QERR O_MS OMODE
Channel OK Diagnostic information of HART communication chan- nel Fault delay 1st internal data exchange channel for channel block 2nd internal data exchange channel for channel block Release for maintenance - extended status Extended status - Application Application data transfer active Flutter suppression Maintenance Status - Data exchange channel Message acknowledgment Status output of ALARM_8P_x (x = 1-2) 1 = program error Maintenance status Channel operating mode
DWORD STRUCT
DWORD DWORD DWORD DWORD DWORD
DWORD DWORD WORD WORD BOOL DWORD DWORD
16#00000000
16#0 0 0 0 0
16#00000000 0 0 0 1 0 0
226
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.37 MOD_HA_PN: Monitoring Device-Specific Diagnostics of HART Field Devices
I/O (parameter) QPERAF QREC_ERR QREC_VAL STATUS
Meaning
1 = I/O access error 1 = Read diagnostic data error 1 = Read diagnostic data Read diagnostics status
Type
Default
BOOL
0
BOOL
0
BOOL
0
DWORD 0
In/out parameters
I/O (parameter) ACC_MODE CPU_DIAG_PN DXCHG_IN DXCHG1_IN MS_XCHG_IN
Meaning
1 = accept MODE settings CPU diagnostics Bidirectional data exchange channel Bidirectional data exchange channel - HART channel Maintenance Status - Data exchange channel
Type
Default
BOOL
0
STRUCT
DWORD 0
DWORD 0
DWORD 0
Additional information For additional information, refer to the sections: Message texts and associated values of MOD_HA_PN (Page 227) Maintenance status MS (Page 533)
6.37.3
Message texts and associated values of MOD_HA_PN
Assignment of message text and message class Process control messages of ALARM_8P with EV_ID are assigned as follows:
Message block
EV_ID (ALARM_8P)
Message number
1
2
3
4 5 6
Default message text
Message class
HART field device@1%d@/@2%d@/ @3%d@/@4%d@: Maintenance alarm
PLC Process Control Message Failure
HART field device@1%d@/@2%d@/ @3%d@/@4%d@: Maintenance demanded
PLC Process Control Message Error
HART field device@1%d@/@2%d@/
Preventative Maintenance -
@3%d@/@4%d@: Maintenance required Standard
No message
No message
No message
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
227
Family: @System 6.37 MOD_HA_PN: Monitoring Device-Specific Diagnostics of HART Field Devices
Message block
Message number 7
8
Default message text
Module @1%d@/@2%d@/@3%d@: Maintenance demanded (external) Module @1%d@/@2%d@/@3%d@: Maintenance required (external)
Associated values of ALARM_8P with EV_ID
Message class
PLC Process Control Message Error Preventative Maintenance Standard
Associated value Block parameter
1
ID of the PN IO system
2
Rack/station number
3
Slot number
4
Channel number
Data type BYTE BYTE BYTE BYTE
The process control messages of NOTIFY_8P with EV_ID1 are assigned as follows:
Message block
EV_ID1 (NOTIFY_8P)
Message no. Default message text
1
HART field device@1%d@/@2%d@/
@3%d@/@4%d@: Reassignment of pa-
rameters
2
HART field device@1%d@/@2%d@/
@3%d@/@4%d@: Cold restart
3
HART field device @1%d@/@2%d@/
@3%d@/@4%d@: Additional status
available
4
7
8
Associated values of ALARM_8P with EV_ID1
Message class Status Message - PLC
Status Message - PLC Status Message - PLC
No message No message No message
Associated value Block parameter
1
ID of the primary PN IO system
2
Rack/station number
3
Slot number
4
Channel number
Data type BYTE BYTE BYTE BYTE
You can find additional information in the section: Message Classes (Page 531).
228
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
6.38
Family: @System 6.38 MOD_HA_PN1: Monitoring Device-Specific Diagnostics of HART Field Devices
MOD_HA_PN1: Monitoring Device-Specific Diagnostics of HART Field Devices
6.38.1
Description of MOD_HA_PN1
Object name (type + number) FB 417 · I/Os of MOD_HA_PN1 (Page 229)
Area of application The MOD_HA_PN1 block reports diagnostic events of an HART field device.
Calling OBs
The block must be installed in the run sequence in the following OBs:
OB 1 OB 82 OB 83 OB 85 OB 86 OB 100
Cyclic program Diagnostic interrupt Plug/pull module interrupt Program execution error Rack failure Warm restart
Operator control and monitoring
If asset management is used in the project and the diagnostic screens have been generated, the faceplate can be called via its block icon.
6.38.2
I/Os of MOD_HA_PN1
The factory setting of the block display in the CFC is identified in the "I/O" column: I/O name bold = I/O visible, I/O name normal = I/O not visible.
You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15)".
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
229
Family: @System 6.38 MOD_HA_PN1: Monitoring Device-Specific Diagnostics of HART Field Devices
Input parameters
I/O (parameter) CHAN_NO DIAG_BUF
EN_MSG EV_IDx
LADDR LADDR1 MODE MS MS_REQ RACK_NO SLOT_NO SUBN_TYP SUBN1_ID SUBN2_ID
Meaning
Type
Channel number Entry in diagnostic buffer (relevant for maintenance personnel) 1 = Enable message Message number ALARM_8P_x (x = 1 - 2, assigned by the ES) Logical address of the channel Logical address of the redundant channel Channel operating mode Maintenance status 1 = Request maintenance release Rack number Slot number 1 = external DP interface PN IO system 1 ID (100 - 115) PN IO system 1 ID (100 - 115)
BYTE BOOL
BOOL DWORD
INT INT WORD DWORD BOOL BYTE BYTE BOOL BYTE BYTE
Default
0 0
1 0
0 0 0 0 0 0 0 0 255 255
Output parameters
I/O (parameter) CH_ACTIVE CH_EXIST
Meaning
Channel active Channel exists
Type
Default
DWORD DWORD
16#00000000 16#00000000
CH_OK DIAG_H
DM_ACTIVE DXCHG_xx DXCHG1_xx EXT_STAT EXT_STAT_A
FS_ACTIVE MS_XCHG MSG_ACK MSGSTAT QERR O_MS OMODE
Channel OK Diagnostic information of HART communication chan- nel Fault delay 1st internal data exchange channel for channel block 2nd internal data exchange channel for channel block Release for maintenance - extended status Extended status - Application Application data transfer active Flutter suppression Maintenance Status - Data exchange channel Message acknowledgment Status output of ALARM_8P_x (x = 1-2) 1 = program error Maintenance status Channel operating mode
DWORD STRUCT
DWORD DWORD DWORD DWORD DWORD
DWORD DWORD WORD WORD BOOL DWORD DWORD
16#00000000
16#0 0 0 0 0
16#00000000 0 0 0 1 0 0
230
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.38 MOD_HA_PN1: Monitoring Device-Specific Diagnostics of HART Field Devices
I/O (parameter) QPERAF QREC_ERR QREC_VAL STATUS
Meaning
1 = I/O access error 1 = Read diagnostic data error 1 = Read diagnostic data Read diagnostics status
Type
Default
BOOL
0
BOOL
0
BOOL
0
DWORD 0
In/out parameters
I/O (parameter) ACC_MODE CPU_DIAG_PN DXCHG_IN DXCHG1_IN MS_XCHG_IN
Meaning
1 = accept MODE settings CPU diagnostics Bidirectional data exchange channel Bidirectional data exchange channel - HART channel Maintenance Status - Data exchange channel
Type
Default
BOOL
0
STRUCT
DWORD 0
DWORD 0
DWORD 0
Additional information For additional information, refer to the sections: Message texts and associated values of MOD_HA_PN1 (Page 231) Maintenance status MS (Page 533)
6.38.3
Message texts and associated values of MOD_HA_PN1
Assignment of message text and message class The process control messages of ALARM_8P with EV_ID are assigned as follows:
Message block
EV_ID (ALARM_8P)
Message number
1
2
3
4 5 6
Default message text
HART field device@1%d@/@2%d@/ @3%d@/@4%d@: Maintenance alarm
HART field device@1%d@/@2%d@/ @3%d@/@4%d@: Maintenance demanded
HART field device@1%d@/@2%d@/ @3%d@/@4%d@: Maintenance required
Message class
PLC Process Control Message Failure
PLC Process Control Message Error
Preventative Maintenance Standard
No message No message No message
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
231
Family: @System 6.38 MOD_HA_PN1: Monitoring Device-Specific Diagnostics of HART Field Devices
Message block
Message number 7
8
Default message text
Module @1%d@/@2%d@/@3%d@: Maintenance demanded (external) Module @1%d@/@2%d@/@3%d@: Maintenance required (external)
Message class
PLC Process Control Message Error Preventative Maintenance Standard
Associated values of ALARM_8P with EV_ID
Associated value Block parameter
1
PN IO system number (SUBN1_ID)
2
Rack/station number (RACK_NO)
3
Slot number (SLOT_NO)
4
Channel number (CHAN_NO)
Data type BYTE BYTE BYTE BYTE
The process control messages of NOTIFY_8P with EV_ID1 are assigned as follows:
Message block
EV_ID1
Message no. Default message text
Message class
1
HART field device@1%d@/@2%d@/
Status Message - PLC
@3%d@/@4%d@: Reassignment of pa-
rameters
2
HART field device@1%d@/@2%d@/
Status Message - PLC
@3%d@/@4%d@: Cold restart
3
HART field device @1%d@/@2%d@/
Status Message - PLC
@3%d@/@4%d@: Additional status
available
4
No message
7
No message
8
No message
Associated values of NOTIFY_8P with EV_ID1
Associated value Block parameter
1
PN IO system number (SUBN1_ID)
2
Rack/station number (RACK_NO)
3
Slot number (SLOT_NO)
4
Channel number (CHAN_NO)
Data type BYTE BYTE BYTE BYTE
You can find additional information in the section: Message Classes (Page 531).
232
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
6.39
Family: @System 6.39 MOD_HA_S7P: Diagnostic module check (<=16 channels)
MOD_HA_S7P: Diagnostic module check (<=16 channels)
6.39.1
Description of MOD_HA_S7P
Object name (type + number) FB 435 · I/Os of MOD_HA_S7P (Page 233)
Area of application Function block MOD_HA_S7P creates diagnostics information for a HART field device.
Calling OBs
The cyclic OB 1 and OB 82, OB 83, OB 85, OB 86 and OB 100.
Use in CFC
The following actions are executed automatically with the "Generate module drivers" CFC function:
· If a module with 16 channels is available in HW Configuration, an instance of the diagnostic function block MOD_HA_S7P is added to the system charts of the project.
· Information from HW Config is read and the input parameters of MOD_HA_S7P are parameterized correspondingly.
The MOD_HA_S7P gets connected with the corresponding channel block of the module.
Startup characteristics Initialization of the ALARM_8P blocks.
6.39.2
I/Os of MOD_HA_S7P
I/Os of MOD_HA_S7P The factory setting of the block display in the CFC is identified in the "I/O" column.
I/O name bold = I/O visible, I/O name normal = I/O not visible.
You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15)".
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
233
Family: @System 6.39 MOD_HA_S7P: Diagnostic module check (<=16 channels)
Input parameters
I/O (parameter) CHAN_NO DIAG_BUF
EN_MSG EV_ID1 EV_ID2 FEATURE LADDR LADDR1 MODE MS MS_REQ RACK_NO SLOT_NO SUBN_TYP SUBN1_ID SUBN2_ID
Meaning
Type
HART channel number
INT
Entry in diagnostic buffer (relevant for maintenance person- BOOL nel)
1 = Enable message
BOOL
Message number 1
DWORD
Message number 2
DWORD
Feature parameter
DWORD
Logical address of the channel
INT
Reserve
INT
Channel mode
DWORD
Maintenance status
DWORD
1 = Request maintenance release
BOOL
Rack number
BYTE
Slot number
BYTE
1 = External DP interface
BOOL
ID of Primary subnet
BYTE
ID of Redundant subnet
BYTE
Default 0 0
1 16#0 16#0 0 -1 -1 0 16#0 0 0 0 0 255 255
Out parameters
I/O (parameter) CH_ACTIVE CH_EXIST CH_OK DIAG_INF DIAG_H DM_ACTIVE DXCHG
DXCHG1
EXT_STAT
EXT_STAT_A FS_ACTIVE MOD_INF MS_XCHG
MSGSTAT MSG_ACK OMODE O_MS
Meaning
Type
Channel active
DWORD
Channel exists
DWORD
Channel OK
DWORD
System structure: Diagnostic information STRUCT
HART Diagnostic Information Structure STRUCT
Fault delay
DWORD
1st internal data exchange channel for channel block
DWORD
2nd internal data exchange channel for DWORD channel block
Release for maintenance - Extended sta- DWORD tus
Extended Status Application
DWORD
Flutter suppression
DWORD
System structure: Module parameter
STRUCT
Maintenance Status - Data exchange channel
DWORD
Message failure
WORD
Message acknowledged
WORD
Channel mode
DWORD
Maintenance status
DWORD
Default 0 0 0
0 16#0
16#0
0
0 0
0
0 0 0 0
234
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.39 MOD_HA_S7P: Diagnostic module check (<=16 channels)
I/O (parameter) QREC_VAL QREC_ERR QSTATUS QERR QMODF QPERAF QRACKF
Meaning 1 = Received new data record 1 = Error read data record Status read data record 1 = program error 1 = Module pulled/defective 1 = I/O access error 1 = higher level error
Type BOOL BOOL DWORD BOOL BOOL BOOL BOOL
Default 0 0 0 1 0 0 0
In/out parameters
I/O (parameter) Meaning
ACC_MODE CPU_DIAG DXCHG_IN DXCHG1_IN MS_XCHG_IN
1 = Apply MODE settings System structure: CPU diagnostics Bidirectional data exchange HART channel Bidirectional data exchange HART channel MS exchange channel
Type
BOOL STRUCT DWORD DWORD DWORD
De- fault 0
0 0 0
6.39.3
Message texts and associated values of MOD_HA_S7P
Assignment of message text and message class The process control messages of ALARM_8P with EV_ID are assigned as follows:
Message block ALARM_8P
EV_ID
Mes- Event sage number
1
HART field device @1%d@/@2%d@/@3%d@/
@4%d@: Maintenance alarm
2
HART field device @1%d@/@2%d@/@3%d@/
@4%d@: Maintenance demanded
3
HART field device @1%d@/@2%d@/@3%d@/
@4%d@: Maintenance required
4
5
6
7
HART field device @1%d@/@2%d@/@3%d@: Main-
tenance demanded (external)
8
HART field device @1%d@/@2%d@/@3%d@: Main-
tenance required (external)
Message class
PLC Process Control Message - Failure PLC Process Control Message - Error Preventative Mainte- nance - Standard No message No message No message PLC Process Control Message - Error Preventative Mainte- nance - Standard
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
235
Family: @System 6.39 MOD_HA_S7P: Diagnostic module check (<=16 channels)
Associated values of ALARM_8P with EV_ID
Associated value 1 2 3 4
Block parameter DP-Master-System number Rack number- / Station number Slot number Channel number
Data type BYTE BYTE BYTE BYTE
The process control messages of ALARM_8P with EV_ID1 are assigned as follows:
Message block ALARM_8P
EV_ID1 (NOTI- FY_8P)
Message number
1
2
3
4 5 6 7 8
Event
HART field device @1%d@/@2%d@/@3%d@/ @4%d@: Re-parameterization HART field device @1%d@/@2%d@/@3%d@/ @4%d@: Cold restart HART field device @1%d@/@2%d@/@3%d@/ @4%d@: Additional status available
Message class
Status Message - PLC
Status Message - PLC
Status Message - PLC
No message No message No message No message No message
Associated values of NOTIFY_ 8P with EV_ID1
Associated value 1 2 3 4
Block parameters DP-Master-System number Rack number- / Station number Slot number Channel number
Data type BYTE BYTE BYTE BYTE
236
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.40 MOD_MS: Monitoring up to 16 channels on ET200S/X motor starter modules with diagnostic functions
6.40
MOD_MS: Monitoring up to 16 channels on ET200S/X motor starter modules with diagnostic functions
6.40.1
Description of MOD_MS
Object name (type + number) FB 96 · MOD_MS block I/Os (Page 241)
Area of application
The MOD_MS block the up to 16-channel motor starter modules with diagnostic capability (ET 200S). H systems support only the modules installed in switched racks.
Calling OBs
The block must be installed in the run sequence in the following OBs:
OB 1 OB 82 OB 83 OB 85 OB 86 OB 100
Cyclic program Diagnostic interrupt Insert/remove module interrupt Program execution error Rack failure Warm restart
Use in CFC
The following actions are executed automatically with the "Generate module drivers" CFC function:
· The MOD_MS block is installed in its runtime group downstream of the RACK block runtime group in the above-mentioned OBs.
· The MODE_xx, SUBN1_ID, SUBN2_ID, and SUBN_TYP inputs are configured.
· The logical addresses LADDR and LADDR1 are configured.
· The OUT structures CPU_DIAG of the OB_BEGIN block and RAC_DIAG of the RACK block are interconnected with the IN_OUT structures of the same name of MOD_MS.
· The output parameter of DXCHG_xx is interconnected with the following channel block at the DataXchg parameter.
· The output parameter of O_MS is interconnected with the following channel block at the MS parameter.
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
237
Family: @System 6.40 MOD_MS: Monitoring up to 16 channels on ET200S/X motor starter modules with diagnostic functions
Function and method of operation Block MOD_MS analyzes all events that affect a module and its channels acyclically. It generates a channel-specific MODE (Page 517) and value status for the signal processing blocks. ALARM_8P is used to report these events. The message function can be disabled. The block is enabled to run by the higher-level RACK block. The event to be evaluated is stored in the CPU_DIAG start and diagnostic information of the OB_BEGIN block. There is a MODE_xx input for each signal channel of the module. The module channel configuration data created in HW Config is reported here. The function writes MODE_xx to the low word of the OMODE_xx (Page 527) output parameter. This occurs only during startup or if you set ACC_MODE = TRUE. The current channel value status is written to the most significant byte. If the result is positive, the system sets OMODE_xx = 16#80xxxxxx. The following events lead to the value status "invalid value due to higher-level error" (OMODE_xx = 16#40xxxxxx): · Events that are evaluated by the RACK block: Rack failure (OB 86) (output parameter QRACKF = TRUE) Program execution error (OB 85) (output parameter QRACKF = TRUE) · Events that are evaluated by the MOD block: Program execution error (OB 85) (output parameter QPERAF = TRUE) Module removed (OB 83) (output parameter QMODF = TRUE) Diagnostic interrupt (OB 82)
The following events in OB 82 will lead to a module error, and are indicated with 16#40xxxxxx ("higher-priority error") in OMODE. At the same time, output parameter QMODF = TRUE: · Configuration/parameter assignment error · Overload · Short circuit · Error · Actuator OFF · Wire break · Safety-related shutdown · High limit exceeded · Low limit undershot · Missing supply voltage · Switching element overload · External error ALARM_8P is used to report "module removed", "I/O access error", and the above "OB 82 error" events to WinCC.
238
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System
6.40 MOD_MS: Monitoring up to 16 channels on ET200S/X motor starter modules with diagnostic functions
The system verifies during startup that the module is available (plugged in). The module status information that is read here is then available in the form of service output parameters (MOD_INF).
Detailed information about the errors is entered in the DIAG_INF output parameter of data type STRUCT. You will find additional information in the "Service Information" section, and in the System Software for S7-300/400 System and Standard Functions; Diagnostic Data, Byte 0 to Byte 8, Structure of Channel-Specific Diagnostic Data reference manual.
Redundancy
The block supports segment redundancy of CPU 417H for distributed I/Os. To use this function, you must configure the SUBN1_ID (connection to CPU 0) and SUBN2_ID (connection to CPU 1) inputs with the numbers of the redundant segments. If there is no segment redundancy, the remaining input must be set to the (default) value 16#FF.
MODE setting You will find additional information about this in the "MODE settings (Page 517)" section.
Note If you change the parameter settings for the MODE_xx inputs at runtime, these changes will not be accepted at the outputs until the ACC_MODE is set to 1.
OMODE Structure You will find additional information in the "OMODE (Page 527)" section.
Valid channel display
The existing channels on a module are displayed in the CH_EXIST output by setting a bit in the DWORD, starting at bit 0, for every existing channel. If the bit assigned to a channel = 0, the channel is not available.
Output CH_OK displays the valid channels on a module by setting a bit to TRUE for every valid channel, where bit 0 is assigned to channel 0, etc. If the bit assigned to a channel is 0, the channel is faulty. If a module error occurs, all channels are disrupted.
Addressing
You will find additional information about this in the "Addressing (Page 530)" section.
Error handling
The plausibility of input parameters is not checked. You will find additional information about this in the "Error information of output parameter MSG_STAT (Page 530)" section.
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
239
Family: @System 6.40 MOD_MS: Monitoring up to 16 channels on ET200S/X motor starter modules with diagnostic functions
Service Information To analyze faults, the module status information entered during startup is read via the MOD_INF structured output parameter. You will find additional information about this in the reference manual System Software for S7-300/400 System and Standard Functions; System Status List, Module Status Information.
Following a diagnostic interrupt, you will also find detailed module diagnostic information in the MODDIAG0 to MODDIAG8 output parameters. You will find additional information in the reference manual System Software for S7-300/400 System and Standard Functions; Diagnostic Data, Byte 0 to Byte 10.
The CHDIAG00 to CHDIAG15 output parameters contain detailed channel-status information. You will find additional information in the reference manual System Software for S7-300/400 System and Standard Functions; Structure of Channel-Specific Diagnostic Data.
Of the motor starter module channels, only channel 0 is assigned the diagnostic function. The error code is stored in CHDIAG00 to CHDIAG03. You will find additional information about this in the ET 200S, Motor Starter Safety Technology SIGUARD; Diagnostics and Monitoring via the User Program reference manual.
The system resets this diagnostic information after a diagnostic interrupt has been reported outgoing (no further channel or module errors are queued).
Startup characteristics After a restart/initial startup, the system verifies that the module is available under its logical base address. A restart (OB 100) is reported via the LSB in byte 2 of the OMODE_xx (Page 527) outputs.
Time response Not available
Message response MOD_MS reports module and motor-starter errors by means of ALARM_8P_1 and ALARM_8P_2. The inputs DELAY1 and DELAY2 are used to delay the output of I/O access error messages. DELAY1 allows you to enter a time in seconds for which the block will wait for a higher-priority error (rack failure or removal/insertion) following a program execution error (OB 85) before it outputs the message. DELAY2 determines the number of seconds the block waits after the higher-priority error has been reported outgoing until it outputs the queued I/O access error as well. Both values are set to 2 seconds by default.
Operator control and monitoring If asset management is used in the project and the diagnostic screens have been generated, the faceplate can be called via its block icon.
For additional information, refer to the "Process Control System PCS 7; Maintenance Station" manual.
240
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.40 MOD_MS: Monitoring up to 16 channels on ET200S/X motor starter modules with diagnostic functions
Additional information For additional information, refer to the sections: Message texts and associated values of MOD_MS (Page 243) Maintenance status MS (Page 533) You can also find additional information on this in PCS 7 Advanced Process Library > Basics of APL > General functions of the blocks > Operating, monitoring and reporting > Release for maintenance
6.40.2
I/Os of MOD_MS
The factory setting of the block display in the CFC is identified in the "I/O" column: I/O name bold = I/O visible, I/O name normal = I/O not visible.
You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15)".
Input parameters
I/O (parameter) DELAY1 DELAY2 DIAG_BUF
EN_MSG EV_IDx LADDR LADDR1 MODE_xx MS MS_REQ RACK_NO SLOT_NO SUBN_TYP SUBN1_ID SUBN2_ID
Meaning
Data type Default
Alarm delay 1 (s)
INT
2
Alarm delay 2 (s)
INT
2
Entry in diagnostic buffer (relevant for maintenance per- BOOL
0
sonnel)
1 = enable message
BOOL
1
Message number x
DWORD
0
Logical address of the input channels
INT
0
Logical address of the output channels
INT
0
Mode channel xx (xx = 00 - 31)
WORD
0
Maintenance status
DWORD
0
1 = Request maintenance release
BOOL
0
Rack number
BYTE
0
Slot number
BYTE
0
1 = external DP interface
BOOL
0
ID of the primary DP master system
BYTE
255
ID of the redundant DP master system
BYTE
255
Output parameters
I/O (parameter) CH_ACTIVE
CH_EXIST
Meaning Channel active Channel exists
Data type Default
DWORD DWORD
16#00000 000
0
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
241
Family: @System 6.40 MOD_MS: Monitoring up to 16 channels on ET200S/X motor starter modules with diagnostic functions
I/O (parameter)
CH_OK DIAG_INF DXCHG_xx DXCHG1_xx EXT_STAT MOD_INF MSG_ACKx MSGSTATx O_MS OMODE_xx QERR QMODF QPERAF QRACKF
Meaning
Channel OK System structure: Diagnostic information 1st internal data exchange channel for channel block 2nd internal data exchange channel for channel block Release for maintenance - extended status System structure: Module parameter Message acknowledgment x Message error information x Maintenance status Mode channel xx (xx = 00 - 31) 1 = program error 1 = module removed/defective 1 = I/O access error 1 = higher-level error
Data type Default
DWORD
0
STRUCT
DWORD
0
DWORD
0
DWORD
0
STRUCT
WORD
0
WORD
0
DWORD
0
DWORD
0
BOOL
1
BOOL
0
BOOL
0
BOOL
0
In/out parameters
I/O (parameter) ACC_MODE CPU_DIAG RAC_DIAG
Meaning
1 = accept MODE settings System structure: CPU diagnostics System structure: Rack diagnostics
Data type Default
BOOL
0
STRUCT
STRUCT
Additional information For additional information, refer to the sections: Message texts and associated values of MOD_MS (Page 243) Maintenance status MS (Page 533)
242
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.40 MOD_MS: Monitoring up to 16 channels on ET200S/X motor starter modules with diagnostic functions
6.40.3
Message texts and associated values of MOD_MS
Assignment of message text and message class
Mes- sage block ALARM _8P EV_ID1
EV_ID2
Mes- Block sage param- number eter
1
QMODF
2
QPERAF
3
4
-
5
-
6
-
7
-
8
-
1
2
3
4
-
5
-
6
-
7
-
8
-
Default message text
Message class
Module @1%d@/@2%d@/@3%d@: With- PLC Process Control Message -
drawn
Failure
Module @1%d@/@2%d@/@3%d@: Access error
PLC Process Control Message Failure
Module @1%d@/@2%d@/@3%d@: @4W PLC Process Control Message -
%t#MOD_MS_TXT@
Failure
Module @1%d@/@2%d@/@3%d@: Mul- PLC Process Control Message -
tiple diagnostic alarm
Failure
Module @1%d@/@2%d@/@3%d@: @4W%t#MOD_MS_TXT@
PLC Process Control Message Failure
Module @1%d@/@2%d@/@3%d@: Short-circuit
PLC Process Control Message Failure
Module @1%d@/@2%d@/@3%d@: Overload
PLC Process Control Message Failure
Module @1%d@/@2%d@/@3%d@: Error
PLC Process Control Message Failure
Module @1%d@/@2%d@/@3%d@: High PLC Process Control Message -
limit violated
Failure
Module @1%d@/@2%d@/@3%d@: Low PLC Process Control Message -
limit violated
Failure
Module @1%d@/@2%d@/@3%d@: Pa- PLC Process Control Message -
rameter assignment error
Failure
Module @1%d@/@2%d@/@3%d@: Ac- PLC Process Control Message -
tuator shutoff
Failure
Module @1%d@/@2%d@/@3%d@: Fail- PLC Process Control Message -
safe shutoff
Failure
Module @1%d@/@2%d@/@3%d@: External error
PLC Process Control Message Failure
Module @1%d@/@2%d@/@3%d@: Overload contact block
PLC Process Control Message Failure
Module @1%d@/@2%d@/@3%d@: Miss- PLC Process Control Message -
ing supply voltage
Failure
You will find the message texts and their text numbers in "Text library for MOD_MS (Page 547)".
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
243
Family: @System 6.41 MOD_SWT: Monitoring of Switch blocks with diagnostics functions
Assignment of associated values
Message block Associ-
ALARM_8P
ated
value
EV_ID1
1
2
3
4
Block parameter
SUBN_ID RACK_NO SLOT_NO -
EV_ID2
1
2
3
SUBN_ID RACK_NO SLOT_NO
Meaning
DP master system ID (byte) Rack/station number (byte) Slot number (byte) Text number (message 5) of MOD_MS_TXT
DP master system ID (byte) Rack/station number (byte) Slot number (byte)
See also
Message Classes (Page 531)
6.41
MOD_SWT: Monitoring of Switch blocks with diagnostics functions
6.41.1
Description of MOD_SWT
Object name (type + number) FB 149 · MOD_SWT block I/Os (Page 245)
Area of application
The MOD_SWT block creates the device-specific diagnostics function for devices of the Switch type.
Calling OBs
The cyclic OB 1 and OB 100.
244
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Use in CFC
Family: @System 6.41 MOD_SWT: Monitoring of Switch blocks with diagnostics functions
The following actions are executed automatically with the "Generate module drivers" CFC function: · The block is installed when the corresponding SlaveFamily 2 object exists · The corresponding inputs are interconnected and configured. · The block is interconnected with the corresponding channel block.
Startup characteristics Initialization of the ALARM_8P blocks and of the NOTIFY_8P blocks.
Message response The block reports errors using ALARM_8P and NOTIFY_8P.
MODE response
The output OMODE shows the device type. A distinction is made between the device and type or profile respectively.
Only the "Motor Management Starter" type is currently implemented. It has the value 16#XXXX0030.
6.41.2
I/Os of MOD_SWT
I/Os The factory setting of the block display in the CFC is identified in the "I/O" column.
I/O name bold = I/O visible, I/O name normal = I/O not visible.
You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15)".
Input parameters
I/O (parameter) EN_MSG EV_ID1 EV_ID2 MS MS_REQ LINK_ADR
Meaning 1 = Enable message Message number 1 Message number 2 Maintenance status 1 = Request maintenance release Link address
Type BOOL DWORD DWORD DWORD BOOL BYTE
Default 1 16#00 16#00 16#00 0 0
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
245
Family: @System 6.41 MOD_SWT: Monitoring of Switch blocks with diagnostics functions
I/O (parameter) PADP_ADR SUBN1_ID SUBN2_ID PORT_ERR
Meaning Address of the PA field device ID of the primary DP master system ID of the redundant DP master system Port error
In/out parameters
I/O (parameter) Meaning
CPU_DIAG
System structure: CPU diagnostics
DIAG_RST RAC_DIAG
Reset of DIAG values System structure: RACK diagnostics
Output parameters
I/O (parameter) CH_ACTIVE CH_EXIST CH_OK DXCHG_xx
DXCHG1_xx
EN_RST_DIAG Error Error_Rst EXT_STAT
EXT_STAT_A
MS_XCHG_00
MSGSTAT1 MSGSTAT2 MSG_ACK1 MSG_ACK2 OMODE_00 O_MS Overload Overload_Rst QERR QRACKF
Meaning
Channel active Channel exists Channel OK 1st internal data exchange channel for channel block 2nd internal data exchange channel for channel block Reset enable Error message is active Message error reset active Release for maintenance - extended sta- tus Extended status - Application Application data transfer active Maintenance Status - Data exchange channel Message error information 1 Message error information 2 Message acknowledgment 1 Message acknowledgment 2 Value status of the PA field device Maintenance status Overload message is active Message overload warning reset active 1 = program error 1 = higher-level error
Type DWORD DWORD DWORD DWORD
DWORD
BOOL BOOL BOOL DWORD
DWORD
DWORD
WORD WORD WORD WORD DWORD DWORD BOOL BOOL BOOL BOOL
Type BYTE BYTE BYTE STRUCT
Default 16#00 16#FF 16#FF
Type
Struct (Siehe OB_BE- GIN)
BOOL
Struct (Siehe OB_DI- AG1)
Default 16#00000000 16#00000000 16#00000000 16#00
0
0 0 0 16#00
0
0
16#00 16#00 16#00 16#00 16#00 16#00 0 0 1 0
246
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.41 MOD_SWT: Monitoring of Switch blocks with diagnostics functions
I/O (parameter) Warning Warning_Rst
Meaning Warning message is active Message warning reset active
Type BOOL BOOL
Default 0 0
6.41.3
Message texts and associated values of MOD_SWT
Assignment of message text and message class The process control messages of ALARM_8P with EV_ID1 are assigned as follows:
Message block ALARM_8P
EV_ID1
Message number
1
2
3
4 5 6
7
8
Event
Message class
Device @1%d@/ @2%d@: Maintenance alarm Device @1%d@/ @2%d@: Maintenance demanded Device @1%d@/ @2%d@: Maintenance required
Device @1%d@/ @2%d@: Failure Device @1%d@/@2%d@: Maintenance demanded (external) Device @1%d@/@2%d@: Maintenance required (external)
PLC Process Control Message Failure
PLC Process Control Message Error
Preventative Maintenance Standard
No message
No message
PLC Process Control Message Failure
PLC Process Control Message Error
Preventative Maintenance Standard
Associated values of ALARM_8P with EV_ID1
Associated value 1 2
Block parameters Subnet Address
Data type BYTE BYTE
The process control messages of NOTIFY_8P with EV_ID2 are assigned as follows:
Message block NOTI- FY_8P
EV_ID2
Message Event number
Message class
1
No message
2
Device @1%d@/ @2%d@: Making configuration change Status Mes-
sage - PLC
3
Device @1%d@/ @2%d@:
Simulation
Status Mes- sage - PLC
4
No message
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
247
Family: @System 6.41 MOD_SWT: Monitoring of Switch blocks with diagnostics functions
Message block NOTI- FY_8P
Message number
5 6
7
8
Event
Device @1%d@/@2%d@: local operation/functional check Device @1%d@/@2%d@: Device passivated Device @1%d@/@2%d@ @4W%t#MOD_SWT_TXT@
Message class
No message SStatus Mes- sage - PLC Status Mes- sage - PLC Status Mes- sage - PLC
Associated values of NOTIFY_8P with EV_ID2
Associated value 1 2
Block parameter Subnet Address
Data type BYTE BYTE
The process control messages of ALARM_8P with EV_ID3 are assigned as follows:
Message block ALARM_8P
EV_ID3
Mes- sage number
1
Event Device 1%d@/@2%d@: Port 1 error
2
Device 1%d@/@2%d@: Port 2 error
3
Device 1%d@/@2%d@: Maintenance demanded
4
Device 1%d@/@2%d@: Maintenance required
5 6 7 8
Message class
PLC Process Control Message - Error PLC Process Control Message - Error PLC Process Control Message - Error Preventative Mainte- nance - Standard No message No message No message No message
Associated values of ALARM_8P with EV_ID3
Associated value 1 2
Block parameter Subnet Address
Data type BYTE BYTE
You can find the message texts and their text numbers in the section "Text library for MOD_SWT (Page 536)".
You can find additional information in the section: Message Classes (Page 531).
248
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
6.42
Family: @System 6.42 MOD_PAL0: Diagnosing a DPV0 PA slave (via DP/PA coupler downstream of a DP/PA link DPV1)
MOD_PAL0: Diagnosing a DPV0 PA slave (via DP/PA coupler downstream of a DP/PA link DPV1)
6.42.1
Description of MOD_PAL0
Object name (type + number) FB 99 · MOD_PAL0 block I/Os (Page 251)
Area of application
Block MOD_PAL0 reports the maintenance status of a PA field device that is used as a DPV0 slave downstream of a DP/PA link DPV1. The PA field devices must conform to the PROFIBUS V3.0 profile.
Calling OBs
The cyclic OB and OB 100.
In addition, the block is installed in the cyclic interrupt OB OB3x in which the following signal processing driver block is installed.
Use in CFC
The following actions are executed automatically with the "Generate module drivers" CFC function:
· The block is integrated in the run sequence upstream of block PA_x
· The SUBN1_ID, SUBN2_ID, RACK_NO, SLOT_NO, PADP_ADR, PROF_V30 inputs are configured.
· The block inputs are interconnected with the following outputs:
Output PA_DIAG of block PADP_L10
OMODEx outputs of block PADP_L10
QMODF and QPERAF outputs of block PADP_L10
with output structure RAC_DIAG of block OB_DIAG1
input QC_x with PA field device icon
· The output parameter of DXCHG_xx is interconnected with the following channel block at the DataXchg parameter.
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
249
Family: @System 6.42 MOD_PAL0: Diagnosing a DPV0 PA slave (via DP/PA coupler downstream of a DP/PA link DPV1)
· The output parameter of O_MS is interconnected with the following channel block at the MS parameter.
Note The CFC function "Generate module drivers" can only be used if the PA field device belongs to slave family 12.
· In the case of Compact Field Unit (CFU) The parameters DXCHG_IN, DXCHG1_IN, MS_XCHG_IN are connected with the corresponding parameters of RACK_CFU block. The block is installed in the run sequence downstream of the SUBNET_PN block.
Function and method of operation
Block MOD_PAL0 analyzes all events that affect the status of a PA field-device slot cyclically. With modular PA field devices, the statuses of the slots are combined to form one status. The acyclic diagnostic events of a PA field device are acquired by the PADP_L10 block. It then stores them in the PA_DIAG parameter. The PA field-device status and the diagnostic information are evaluated, and entered in the MS parameter.
For additional information on this, refer to the section: "PA field device status and diagnostic information (Page 533)".
The statuses are generated with ALARM_8P for messages requiring acknowledgment, and with NOTIFY_8P for those not requiring acknowledgment. The message function can be disabled.
Input PROF_V30 must be set to zero if the PA field device used does not conform to profile 3.0 (this is done by the "Generate module drivers" CFC function).
For a diagnostic event, the block reports "Device xx: uncertain diagnosis".
The failure of a PA field device is identified in the upstream block OB_DIAG1, and is reported via the RAC_DIAG structure. A message "Device xx: Failure" is also generated.
Redundancy
The higher-level block evaluates the redundancy of DP master systems operating in an H system.
Error handling The plausibility of input parameters is not checked.
Startup characteristics Initialization of ALARM_8P and NOTIFY_8P.
Time response Not available
250
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.42 MOD_PAL0: Diagnosing a DPV0 PA slave (via DP/PA coupler downstream of a DP/PA link DPV1)
Message response The block reports by means of ALARM_8P and NOTIFY_8P. The block generates the following messages in the OBs listed below:
OB no. Start Event
x
Cyclic processing
100
Restart
Message
Have the ALARM_8P/NOTIFY_8P outputs/messages updated, if nec- essary
Initialization of ALARM_8P
Operator control and monitoring
If asset management is used in the project and the diagnostic screens have been generated, the faceplate can be called via its block icon.
For additional information, refer to the "Process Control System PCS 7; Maintenance Station" manual.
Additional information
For additional information, refer to the sections:
Message texts and associated values of MOD_PAL0 (Page 253)
Maintenance status MS (Page 533)
You can also find additional information on this in PCS 7 Advanced Process Library > Basics of APL > General functions of the blocks > Operating, monitoring and reporting > Release for maintenance
6.42.2
I/Os of MOD_PAL0
I/Os
The factory setting of the block display in the CFC is identified in the "I/O" column: I/O name bold = I/O visible, I/O name normal = I/O not visible.
You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15)".
Input parameters
I/O (parameter) EN_DIAG EN_MSG EV_IDx MODE_xx MODF
Meaning 1 = Queued diagnostic event 1 = Enable message Message number x Value status PA field device (xx = channel 16 to 31) 1 = PA slave error
Type BOOL BOOL DWORD DWORD BOOL
Default 0 1 0 0 0
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
251
Family: @System 6.42 MOD_PAL0: Diagnosing a DPV0 PA slave (via DP/PA coupler downstream of a DP/PA link DPV1)
I/O (parameter)
MS MS_REQ NUM_CHN PA_DIAG PADP_ADR PERAF PROF_V30 QC_xx RACK_NO SLOT_NO SUBN1_ID SUBN2_ID
Meaning
Maintenance status 1 = Request maintenance release Number of channels of the PA device PA field device diagnostic information Address of the PA field device 1 = I/O access error 1 = PA slave profile V3.0 Status of PA field device (xx = channel 16 to 31) Number of the DP link Slot number of the PA field device in the DP link ID of the primary DP master system ID of the redundant DP master system
Type
DWORD BOOL INT DWORD BYTE BOOL BOOL BYTE BYTE BYTE BYTE BYTE
Default
0 0 0 0 0 0 0 0 0 0 255 255
Output parameters
I/O B_QC
CH_ACTIVE
CH_EXIST CH_OK DXCHG_xx
DXCHG1_xx
EXT_STAT
EXT_STAT_A
FS_ACTIVE
MS_XCHG_00 MSG_ACKx MSGSTATx MS_XCHG_xx
O_MS OMODE_xx QERR QMODF
Meaning
Bit-granular status (channel 0 to 31) of the PA field device
Channel active
Type STRUCT
DWORD
Channel exists
Channel OK
1st internal data exchange channel for channel block
2nd internal data exchange channel for channel block
Release for maintenance - extended status Bit 0=1: ConditionMonitoring On
Extended status - Application Application data transfer active
Flutter suppression
DWORD DWORD
DWORD DWORD DWORD DWORD
Maintenance Status - Data exchange channel Message acknowledgment x Message error information x Maintenance Status - Data exchange channel (xx = 00 - 31) Maintenance status Operating mode slot (xx = Slot 16 to 31) 1 = program error 1 = PA slave error
DWORD WORD WORD DWORD
DWORD DWORD BOOL BOOL
Default
16#00 00000 0 0 0 0
0
0
0
16#00 00000 0 0 0 0 0
0 0 1 0
252
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.42 MOD_PAL0: Diagnosing a DPV0 PA slave (via DP/PA coupler downstream of a DP/PA link DPV1)
I/O QPERAF QRACKF
Meaning 1 = I/O access error 1 = higher-level error
Type BOOL BOOL
Default 0 0
In/out parameters
I/O RAC_DIAG CPU_DIAG DXCHG_IN DXCHG1_IN MS_XCHG_IN
Meaning System structure: RACK diagnostics CPU diagnostics Data exchange Data exchange MS exchange
Type STRUCT STRUCT DWORD DWORD DWORD
Default
0 0 0
Additional information For additional information, refer to the sections: Message texts and associated values of MOD_PAL0 (Page 253) Maintenance status MS (Page 533) PA field device status and diagnostics information (Page 533)
6.42.3
Message texts and associated values of MOD_PAL0
Assignment of message text and message class
Message block
EV_ID1 (ALARM_8P)
Mes- sage no. 1
2
3
4 5
6 7
8
Default message text
Message class
Device @1%d@/ @2%d@/@3%d@: Mainte- nance alarm Device @1%d@/ @2%d@/@3%d@: Mainte- nance demanded Device @1%d@/ @2%d@/@3%d@: Mainte- nance required
Device @1%d@/@2%d@/@3%d@: Uncertain diagnostics
Device @1%d@/@2%d@/@3%d@: Maintenance demanded (external) Device @1%d@/@2%d@/@3%d@: Maintenance required (external)
PLC Process Control Message Failure
PLC Process Control Message Error
Preventative Maintenance Standard
No message
PLC Process Control Message Failure
No message
PLC Process Control Message Error
Preventative Maintenance Standard
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
253
Family: @System 6.42 MOD_PAL0: Diagnosing a DPV0 PA slave (via DP/PA coupler downstream of a DP/PA link DPV1)
Message block
EV_ID2 (NOTIFY_8P)
Mes- sage no. 1
2
3 4
5
6
7
8
Default message text
Message class
Device @1%d@/ @2%d@/@3%d@: Goes to fail-safe position
Status Message - PLC
Device @1%d@/ @2%d@/@3%d@: Making configuration change
Status Message - PLC
Device @1%d@/ @2%d@/@3%d@: Simulation Status Message - PLC
Device @1%d@/ @2%d@/@3%d@: Process-re- Status Message - PLC lated, no maintenance
Device @1%d@/ @2%d@/@3%d@: Process-re- Status Message - PLC lated, no maintenance
Device @1%d@/ @2%d@/@3%d@: Local oper- Status Message - PLC ation/functional check
Device @1%d@/ @2%d@/@3%d@: Device pas- Status Message - PLC sivated
Device @1%d@/ @2%d@/ @3%d@: @4W %t#MOD_PAL0_TXT@
Status Message - PLC
Assignment of associated values
Message block
EV_ID1 (ALARM_8P)
Associated value 1
2 3
Block parameter SUBN_ID
RACK_NO PADPADR
Meaning
DP master system ID (byte)
Rack/station number (byte) PA field device address (byte)
EV_ID2
1
(NOTIFY_8P)
2
3
4
SUBN_ID
RACK_NO PADPADR
DP master system ID (byte)
Rack/station number (byte) PA field device address (byte) Text number MOD_PAL0
If the PA field device is connected downstream from an inactive DP/PA-Link V1and SUBN1_ID = 16#FF, the associated variable is substituted by SUBN2_ID.
You will find the message texts and their text numbers in "Text library for MOD_PAL0 (Page 537)".
See also
Message Classes (Page 531)
254
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.43 MOD_PAX0: Diagnosing a DPV0 PA slave (via DP/PA coupler with connection to a DP master system)
6.43
MOD_PAX0: Diagnosing a DPV0 PA slave (via DP/PA coupler with connection to a DP master system)
6.43.1
Description of MOD_PAX0
Object name (type + number) FB 112 · MOD_PAX0 block I/Os (Page 257)
Area of application
Block MOD_PAX0 reports the maintenance status of a PA field device that is used as a DPV0 slave in a DP master system. The PA field devices must conform to the PROFIBUS V3.0 profile.
Calling OBs
The cyclic OB and OB 100.
In addition, the block is installed in the cyclic interrupt OB OB3x in which the following signal processing driver block is installed.
Use in CFC
The following actions are executed automatically with the "Generate module drivers" CFC function:
· The block is integrated in the run sequence upstream of the PA_x block.
· The inputs SUBN1_ID, SUBN2_ID, PADP_ADR and PROF_V30 have parameters assigned.
· The inputs are interconnected with the following outputs:
Output PA_DIAG of block PADP_L10
OMODEx outputs of block PADP_L10
QMODF and QPERAF outputs of block PADP_L10
with output structure RAC_DIAG of block OB_DIAG1
· Input QC_x is interconnected with the PA field device status icon.
· Output OMODExx is interconnected with the MODE input of the PA_x block.
· The output parameter of DXCHG_xx is interconnected with the following channel block at the DataXchg parameter.
· The output parameter of O_MS is interconnected with the following channel block at the MS parameter.
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
255
Family: @System 6.43 MOD_PAX0: Diagnosing a DPV0 PA slave (via DP/PA coupler with connection to a DP master system)
Note The CFC function "Generate module drivers" can only be used if the PA field device belongs to slave family 12.
Function and method of operation
Block MOD_PAX0 analyzes all events relating to the status of a PA field device slot cyclically. With modular PA field devices, the statuses of the slots are combined to form one status. The acyclic diagnostic events of a PA field device are acquired by the PADP_L10 block. It then stores them in the PA_DIAG parameter. The PA field-device status and the diagnostic information are evaluated, and entered in the MS parameter.
You will find additional information in the "PA field device status and diagnostic information (Page 533)" section.
Input PROF_V30 must be set to zero if the PA field device used does not conform to profile 3.0 (this is done by the "Generate module drivers" CFC function).
In the event of a diagnostic event, the block reports "PA field device diagnostics".
There is an input (MODE_xx (Page 517)) for each slot (module) on the PA field device that is used to read in configuration settings made for the PA field device slots (module) in HW Config.
The function writes MODE_xx to the low word of the OMODE_xx (Page 527) output parameter. This occurs only during startup or if you set ACC_MODE = TRUE. The current slot value status is written to the most significant byte. If the result is positive, the system sets OMODE_xx = 16#80xxxxxx. The following events lead to the value status "Invalid value due to higher-priority error" (OMODE_xx = 16#40xxxxxx):
MODE setting for PA profiles
You will find additional information in "PA_MODE settings (Page 528)".
Note
If you change the parameter settings for the MODE_xx inputs at runtime, these changes will not be accepted at the outputs until the ACC_MODE is set to 1.
OMODE Structure You will find additional information in the "OMODE (Page 527)" section.
Redundancy
The higher-level block evaluates the redundancy of DP master systems operating in an H system.
Error handling The plausibility of input parameters is not checked.
256
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.43 MOD_PAX0: Diagnosing a DPV0 PA slave (via DP/PA coupler with connection to a DP master system)
Startup characteristics Initialization of ALARM_8P and NOTIFY_8P
Time response Not available
Message response The block uses ALARM_8P and NOTIFY_8P The block generates the following messages in the OBs listed below:
OB no. x 100
Start Event Cyclic processing Restart
Message Repeat the update of ALARM_8P outputs/messages, if necessary Initialization of ALARM_8P
Operator control and monitoring
If asset management is used in the project and the diagnostic screens have been generated, the faceplate can be called via its block icon.
For additional information, refer to the "Process Control System PCS 7; Maintenance Station" manual.
Additional information
For additional information, refer to the sections:
Message texts and associated values of MOD_PAX0 (Page 259)
Maintenance status MS (Page 533)
You can also find additional information on this in PCS 7 Advanced Process Library > Basics of APL > General functions of the blocks > Operating, monitoring and reporting > Release for maintenance
6.43.2 I/Os
I/Os of MOD_PAX0
The factory setting of the block display in the CFC is identified in the "I/O" column: I/O name bold = I/O visible, I/O name normal = I/O not visible. You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15)".
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
257
Family: @System 6.43 MOD_PAX0: Diagnosing a DPV0 PA slave (via DP/PA coupler with connection to a DP master system)
Input parameters
I/O (parameter) EN_MSG EV_IDx MODE_xx MODF MS MS_REQ NUM_CHN PA_DIAG PADP_ADR PERAF PROF_V30 QC_xx SUBN1_ID SUBN2_ID
Meaning
1 = Enable message Message number x Value status PA field device (xx = channel 16 to 31) 1 = PA slave error Maintenance status 1 = Request maintenance release Number of channels of the PA device PA field device diagnostic information Address of the PA field device 1 = I/O access error 1 = PA slave profile V3.0 Status of PA field device (xx = channel 16 to 31) ID of the primary DP master system ID of the redundant DP master system
Type
BOOL DWORD DWORD BOOL DWORD BOOL INT DWORD BYTE BOOL BOOL BYTE BYTE BYTE
Default
1 0 0 0 0 0 0 0 0 0 0 0 255 255
Output parameters
I/O (parameter) B_QC
CH_ACTIVE
CH_EXIST CH_OK DXCHG_xx DXCHG1_xx EXT_STAT EXT_STAT_A
FS_ACTIVE
MS_XCHG_00 MS_XCHG_xx
MSG_ACKx MSGSTATx
Meaning
Type
Bit-granular status (channel 0 to 31) of the PA field device
Channel active
STRUCT DWORD
Channel exists
DWORD
Channel OK
DWORD
1st internal data exchange channel for channel block DWORD
2nd internal data exchange channel for channel block DWORD
Release for maintenance - extended status
DWORD
Extended status - Application
DWORD
Application data transfer active
Flutter suppression
DWORD
Maintenance Status - Data exchange channel Maintenance Status - Data exchange channel (xx = 00 - 31) Message acknowledgment x Message error information x
DWORD DWORD
WORD WORD
Default
16#00000 000 0 0 0 0 0 0
16#00000 0000 0 0
0 0
O_MS OMODE_xx
Maintenance status Operating mode slot (xx = Slot 16 to 31)
DWORD
0
DWORD
0
258
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.43 MOD_PAX0: Diagnosing a DPV0 PA slave (via DP/PA coupler with connection to a DP master system)
I/O (parameter)
QERR QMODF QPERAF QRACKF
Meaning
1 = program error 1 = PA slave error 1 = I/O access error 1 = higher-level error
Type
BOOL BOOL BOOL BOOL
Default
1 0 0 0
In/out parameters
I/O (parameter) RAC_DIAG CPU_DIAG
Meaning
System structure: RACK diagnostics CPU diagnostics
Type
STRUCT STRUCT
Default
Additional information For additional information, refer to the sections: Message texts and associated values of MOD_PAX0 (Page 259) Maintenance status MS (Page 533) PA field device status and diagnostics information (Page 533)
6.43.3
Message texts and associated values of MOD_PAX0
Assignment of message text and message class
Message block
EV_ID1 (ALARM_8P)
Message no. 1 2 3 4 5 6 7
8
Default message text
Device @1%d@/@2%d@/@3%d@: Main- tenance alarm Device @1%d@/@2%d@/@3%d@: Main- tenance demanded Device @1%d@/@2%d@/@3%d@: Main- tenance required Device @1%d@/@2%d@/@3%d@: Fail- ure Device @1%d@/@2%d@/@3%d@: Un- certain diagnostics
Device @1%d@/@2%d@/@3%d@: Maintenance demanded (external) Device @1%d@/@2%d@/@3%d@: Maintenance required (external)
Message class
PLC Process Control Message Failure
PLC Process Control Message Error
Preventative Maintenance Standard
PLC Process Control Message Failure
PLC Process Control Message Failure
No message
PLC Process Control Message Error
Preventative Maintenance Standard
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
259
Family: @System 6.43 MOD_PAX0: Diagnosing a DPV0 PA slave (via DP/PA coupler with connection to a DP master system)
Message block
EV_ID2 (NO- TIFY_8P)
Message no. Default message text
1
Device @1%d@/ @2%d@: Goes to fail-
safe position
2
Device @1%d@/ @2%d@: Making con-
figuration change
3
Device @1%d@/ @2%d@:
Simulation
4
Device @1%d@/ @2%d@:
Process-related, no maintenance
5
Device @1%d@/ @2%d@: Process-rela-
ted, no maintenance
6
Device @1%d@/ @2%d@: Local opera-
tion/functional check
7
Device @1%d@/@2%d@:
Device passivated
8
Device @1%d@/ @2%d@:@3W
%t#MOD_PAX0_TXT@
Message class Status Message - PLC Status Message - PLC Status Message - PLC Status Message - PLC Status Message - PLC Status Message - PLC Status Message - PLC Status Message - PLC
Assignment of associated values
Message block
EV_ID1 (ALARM_8P)
Associated value 1
2
Block parameter SUBN_ID
PADPADR
Meaning DP master system ID (byte) PA field device address (byte)
EV_ID2 (NOTI- 1 FY_8P)
2
3
SUBN_ID PADPADR
DP master system ID (byte)
PA field device address (byte) Text number MOD_PAXL0
If SUBN1_ID = 16#FF, the associated value is substituted with SUBN2_ID.
You will find the message texts and their text numbers in the section:
Text library for MOD_PAX0 (Page 537)" section.
See also
Message Classes (Page 531)
260
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
6.44
Family: @System 6.44 MOD_ENME: Diagnostics for modules of the Energy Meter type
MOD_ENME: Diagnostics for modules of the Energy Meter type
6.44.1
Description of MOD_ENME
Object name (type + number) FB 419 · I/Os of MOD_ENME (Page 261)
Area of application
The MOD_ENME block creates device-specific diagnostics for the ET 200 SP module of the type Energy Meter ST.
Calling OBs
The cyclic OB 1 and OB 82, OB 83, OB 85, OB 86 and OB 100.
Use in CFC
The following actions are executed automatically with the "Generate module drivers" CFC function:
· The block is installed when an ET200SP Energy Meter is present.
· The corresponding inputs are read out of HW Config and configured.
· The block is interconnected with the corresponding channel module for the ET200 SP Energy Meter.
Startup characteristics Initialization of the ALARM_8P blocks.
6.44.2 I/Os
I/Os of MOD_ENME
The factory setting of the block display in the CFC is identified in the "I/O" column. I/O name bold = I/O visible, I/O name normal = I/O not visible. You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15)".
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
261
Family: @System 6.44 MOD_ENME: Diagnostics for modules of the Energy Meter type
Input parameters
I/O (parameter) CHAN_NUM DELAY1 DELAY2 DIAG_BUF
EN_MSG EV_ID1 EV_ID2 FEATURE_XX LADDR LADDR1 MODE_00 MODE_01 MODE_02 MS MS_REQ RACK_NO SLOT_NO SUBN_TYP SUBN1_ID SUBN2_ID SUBSL_NO
Meaning
Type
Total number of channels -1
INT
Interrupt delay 1 (s)
INT
Interrupt delay 2 (s)
INT
Entry in diagnostic buffer (relevant for maintenance person- BOOL nel)
1 = Enable message
BOOL
Message number 1
DWORD
Message number 2
DWORD
Feature parameter (xx= 01 - 10)
WORD
Logical input address of the module
INT
Logical output address of the module
INT
Channel 00 mode
DWORD
Channel 01 mode
DWORD
Channel 02 mode
DWORD
Maintenance status
DWORD
1 = Request maintenance release
BOOL
Rack number
BYTE
Slot number
BYTE
1 = external PN interface
BOOL
PN IO system 1 ID (100 - 115)
BYTE
PN-IO System 2 ID (100 - 115)
BYTE
Subslot number
BYTE
Default 0 2 2 0
1 16#00 16#00 0 0 0 0 0 0 16#00 0 0 0 0 255 255 0
In/out parameters
I/O (parameter) Meaning
ACC_MODE CPU_DIAG_PN DIAG_RST RAC_DIAG
1 = Apply MODE settings System structure: CPU diagnostics Reset diagnostic values System structure: RACK diagnostics
Type
BOOL STRUCT BOOL STRUCT
De- fault 0
0
Output parameters
I/O (parameter) CH_ACTIVE CH_EXIST CH_OK DIAG_INF DM_ACTIVE
Meaning
Type
Channel active
DWORD
Channel exists
DWORD
Channel OK
DWORD
System structure: Diagnostic information STRUCT
Fault delay
DWORD
Default 0 0 0
0
262
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.44 MOD_ENME: Diagnostics for modules of the Energy Meter type
I/O (parameter) DXCHG_00
DXCHG1_00
EN_RST_DIAG EXT_STAT
EXT_STAT_A FS_ACTIVE IL1_Rst IL1_St IL2_Rst IL2_St IL3_Rst IL3_St MOD_INF MS_XCHG_00
MSGSTAT1 MSG_ACK1 MSGSTAT2 MSG_ACK2 OMODE_00 OMODE_01 OMODE_02 O_MS QERR QMODF QPERAF QRACKF Quadrant UL1_Rst UL1_St UL2_Rst UL2_St UL3_Rst UL3_St
Meaning
1st internal data exchange channel for channel block 2nd internal data exchange channel for channel block Activate reset Release for maintenance - extended sta- tus Extended Status Application Flutter suppression Reset of message IL1 is active Message IL1 is OK Reset of message IL2 is active Message IL2 is OK Reset of message IL3 is active Message IL3 is OK System structure: Module parameter Maintenance Status - Data exchange channel Message failure 1 Message acknowledged 1 Message failure 2 Message acknowledged 2 Channel 0 mode Channel 1 mode Channel 2 mode Maintenance status 1 = program error 1 = Module pulled/defective 1 = I/O access error 1 = higher-level error Current quadrant information Reset of message UL1 is active Message UL1 is OK Reset of message UL2 is active Message UL2 is OK Reset of message UL3 is active Message UL3 is OK
Type DWORD
DWORD
BOOL DWORD
DWORD DWORD BOOL BOOL BOOL BOOL BOOL BOOL STRUCT DWORD
WORD WORD WORD WORD DWORD DWORD DWORD DWORD BOOL BOOL BOOL BOOL INT BOOL BOOL BOOL BOOL BOOL BOOL
Default 0
0
0 0
0 0 0 0 0 0 0 0
0
16#0000 16#0000 16#0000 16#0000 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
263
Family: @System 6.44 MOD_ENME: Diagnostics for modules of the Energy Meter type
6.44.3
Message texts and associated values of MOD_ENME
Assignment of message text and message class The process control messages of ALARM_8P with EV_ID1 are assigned as follows:
Message block ALARM_8P
EV_ID1
Mes- Event sage number
Message class
1
Module @1%d@/@2%d@/@3%d@/@4%d@: Mainte- PLC Process Control
nance alarm
Message - Failure
2
Module @1%d@/@2%d@/@3%d@/@4%d@: Main- PLC Process Control
tenance demanded
Message - Error
3
Module @1%d@/@2%d@/@3%d@/@4%d@: Mainte- Preventative Mainte-
nance required
nance - Standard
4
No message
5
No message
6
Module @1%d@/@2%d@/@3%d@/@4%d@: Failure PLC Process Control
Message - Failure
7
Module @1%d@/@2%d@/@3%d@/@4%d@: Mainte- PLC Process Control
nance demanded (external)
Message - Error
8
Module @1%d@/@2%d@/@3%d@/@4%d@: Main- Preventative Mainte-
tenance required (external)
nance - Standard
Associated values of ALARM_8P with EV_ID1
Associated value 1 2 3 4
Block parameter Subnet Address Slot number Subslot number
Data type BYTE BYTE BYTE BYTE
The process control messages of ALARM_8P with EV_ID2 are assigned as follows:
Message block ALARM_8P
EV_ID2
Message number
Event
Message class
1
Module @1%d@/@2%d@/@3%d@/@5%d@:
PLC Process Control
Error channel 00 @4W%t#MOD_EN_ME_TXT@ Message - Failure
2
Module @1%d@/@2%d@/@3%d@/@5%d@:
PLC Process Control
Error channel 01 @4W%t#MOD_EN_ME_TXT@ Message - Failure
3
Module @1%d@/@2%d@/@3%d@/@4%d@:
PLC Process Control
Error channel 02 @4W%t#MOD_EN_ME_TXT@ Message - Failure
4
No message
5
No message
6
No message
264
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.45 MOD_ENME_S7P: Diagnostic function block for energy meter
Message block ALARM_8P
Message number
Event
7 8
Message class
No message No message
Associated values of ALARM_8P with EV_ID2
Associated value 1 2 3 4 5
Block parameters ID of the PN IO system Rack/station number Slot number Text number from MOD_EN_ME_TXT Subslot number
Data type BYTE BYTE BYTE BYTE BYTE
You can find the message texts and their text numbers in the section: Text library for MOD_D8_PN (FB197) / MOD_D16_PN (FB198) / MOD_D24_PN (FB199) / MOD_ENME (FB 419) (Page 542).
You can find additional information in the section: Message Classes (Page 531).
6.45
MOD_ENME_S7P: Diagnostic function block for energy meter
6.45.1
Description of MOD_ENME_S7P
Object name (type + number) FB 449 · I/Os of MOD_ENME_S7P (Page 266)
Area of application
The MOD_ENME_S7P block creates the device specific diagnostics information for ET200 SP modules of type Energy Meter ST, V4.0 with IM 155-6DP HF V3.1.
Calling OBs
The cyclic OB 1 and OB 82, OB 83, OB 85, OB 86 and OB 100.
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
265
Family: @System 6.45 MOD_ENME_S7P: Diagnostic function block for energy meter
Use in CFC
The following actions are executed automatically with the "Generate module drivers" CFC function if the energy meter module V4.0 is configured in the HW:
· If an ET200 SP Energy Meter module is available in HW Config, an instance of the diagnostic function block MOD_ENME_S7P is added to the system charts of the project.
· Information from HW configuration is read and the input parameters of MOD_ENME_S7P are parameterized correspondingly.
The MOD_ENME_S7P gets connected with the corresponding channel block of the ET200 SP Energy Meter module.
Startup characteristics Initialization of the ALARM_8P blocks.
6.45.2
I/Os of MOD_ENME_S7P
I/Os The factory setting of the block display in the CFC is identified in the "I/O" column.
I/O name bold = I/O visible, I/O name normal = I/O not visible.
You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15)".
Input parameters
I/O (parameter) CHAN_NUM DELAY1 DELAY2 DIAG_BUF
EN_MSG EV_ID1 EV_ID2 FEATURE_XX LADDR LADDR1 MODE_00 MODE_01 MODE_02 MS MS_REQ
Meaning
Total number of channels -1 Interrupt delay 1 (s) Interrupt delay 2 (s) Entry in diagnostic buffer (relevant for maintenance personnel) 1 = Enable message Message number 1 Message number 2 Feature parameter (xx = 01...10) Logical input address of the module Logical output address of the module Channel 00 mode Channel 01 mode Channel 02 mode Maintenance status 1 = Request maintenance release
Type INT INT INT BOOL
BOOL DWORD DWORD WORD INT INT DWORD DWORD DWORD DWORD BOOL
Default 0 2 2 0
1 16#0 16#0 0 -1 -1 0 0 0 16#0 0
266
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.45 MOD_ENME_S7P: Diagnostic function block for energy meter
I/O (parameter) RACK_NO SLOT_NO SUBN_TYP SUBN1_ID SUBN2_ID
Meaning Rack number Slot number 1 = External DP interface DP master System 1 ID DP master System 2 ID
Type BYTE BYTE BOOL BYTE BYTE
Default 0 0 0 255 255
Out parameters
I/O (parameter) CH_ACTIVE CH_EXIST CH_OK DIAG_INF DM_ACTIVE DXCHG_00
DXCHG1_00
EN_RST_DIAG EXT_STAT
EXT_STAT_A FS_ACTIVE IL1_Rst IL1_St IL2_Rst IL2_St IL3_Rst IL3_St MOD_INF MS_XCHG_00
MSGSTAT1 MSG_ACK1 OMODE_00 OMODE_01 OMODE_02 O_MS QREC_VAL QREC_ERR QSTATUS QERR QMODF
Meaning
Type
Channel active
DWORD
Channel exists
DWORD
Channel OK
DWORD
System structure: Diagnostic information STRUCT
Fault delay
DWORD
1st internal data exchange channel for channel block
DWORD
2nd internal data exchange channel for DWORD channel block
Activate reset
BOOL
Release for maintenance - Extended sta- DWORD tus
Extended Status Application
DWORD
Flutter suppression
DWORD
Reset of message IL1 is active
BOOL
Message IL1 is OK
BOOL
Reset of message IL2 is active
BOOL
Message IL2 is OK
BOOL
Reset of message IL3 is active
BOOL
Message IL3 is OK
BOOL
System structure: Module parameter
STRUCT
Maintenance Status - Data exchange channel
DWORD
Message failure 1
WORD
Message acknowledged 1
WORD
Channel 0 mode
DWORD
Channel 1 mode
DWORD
Channel 2 mode
DWORD
Maintenance status
DWORD
1 = Received new data record
BOOL
1 = Error read data record
BOOL
Status read data record
DWORD
1 = program error
BOOL
1 = Module pulled/defective
BOOL
Default 0 0 0
0 16#0
16#0
0 0
0 0 0 0 0 0 0 0
0
0 0 0 0 0 0 0 0 0 1 0
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
267
Family: @System 6.45 MOD_ENME_S7P: Diagnostic function block for energy meter
I/O (parameter) QPERAF QRACKF Quadrant UL1_Rst UL1_St UL2_Rst UL2_St UL3_Rst UL3_St
Meaning 1 = I/O access error 1 = higher level error Current quadrant information Reset of message UL1 is active Message UL1 is OK Reset of message UL2 is active Message UL2 is OK Reset of message UL3 is active Message UL3 is OK
In/out parameters
I/O (parameter) ACC_MODE CPU_DIAG DIAG_RST RAC_DIAG
Meaning 1 = Apply MODE settings System structure: CPU diagnostics Reset diagnostic values System structure: RACK diagnostics
Type BOOL BOOL INT BOOL BOOL BOOL BOOL BOOL BOOL
Type BOOL STRUCT BOOL STRUCT
Default 0 0 0 0 0 0 0 0 0
Default 0
0
6.45.3
Message texts and associated values of MOD_ENME_S7P
Assignment of message text and message class The process control messages of ALARM_8P with EV_ID1 are assigned as follows:
Message block ALARM_8P
EV_ID1
Mes- Event sage number
Message class
1
Module @1%d@/@2%d@/@3%d@: Maintenance PLC Process Control
alarm
Message - Failure
2
Module @1%d@/@2%d@/@3%d@: Maintenance de- PLC Process Control
manded
Message - Error
3
Module @1%d@/@2%d@/@3%d@: Maintenance re- Preventative Mainte-
quired
nance - Standard
4
No message
5
No message
6
Module @1%d@/@2%d@/@3%d@: Failure
PLC Process Control Message - Failure
7
Module @1%d@/@2%d@/@3%d@: Maintenance de- PLC Process Control
manded (external)
Message - Error
8
Module @1%d@/@2%d@/@3%d@: Maintenance re- Preventative Mainte-
quired (external)
nance - Standard
268
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.45 MOD_ENME_S7P: Diagnostic function block for energy meter
Associated values of ALARM_8P with EV_ID1
Associated value 1 2 3
Block parameter DP master system number Rack number/Station number Slot number
Data type BYTE BYTE BYTE
The process control messages of ALARM_8P with EV_ID2 are assigned as follows:
Message block ALARM_8P
EV_ID2
Message number
Event
Message class
1
Module @1%d@/@2%d@/@3%d@: Error chan- PLC Process Control
nel 00 @4W%t#MOD_ ENME_S7P _TXT@
Message - Failure
2
Module @1%d@/@2%d@/@3%d@: Error chan- PLC Process Control
nel 01 @4W%t#MOD_ ENME_S7P _TXT@
Message - Failure
3
Module @1%d@/@2%d@/@3%d@: Error chan- PLC Process Control
nel 02 @4W%t#MOD_ENME_S7P_TXT@
Message - Failure
4
No message
5
No message
6
No message
7
No message
8
No message
Associated values of ALARM_8P with EV_ID2
Associated value 1 2 3 4
Block parameters DP master system number Rack number/Station number Slot number Text number from MOD_ENME_S7P_TXT
Data type BYTE BYTE BYTE BYTE
You can find the message texts and their text numbers in the section: Text library for MOD_ENME_S7P (Page 549).
You can find additional information in the section: Message Classes (Page 531).
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
269
Family: @System 6.46 OB_BEGIN: CPU Diagnostics and AS Connection Diagnostics
6.46
OB_BEGIN: CPU Diagnostics and AS Connection Diagnostics
6.46.1
Description of OB_BEGIN
Object name (type + number) FB100 · OB_BEGIN block I/Os (Page 274)
Area of application
Block OB_BEGIN is used for CPU diagnostics of the automation system (AS). By installing the block in CFC, the system creates all acyclic tasks (OBs) in which the driver blocks of PCS 7 Basis Library are executed.
Calling OBs
The block must be installed in the run sequence in the following OBs:
OB 1 OB 55 OB 56 OB 57 OB 70 OB 72 OB 80 OB 81 OB 82 OB 83 OB 84 OB 85 OB 86 OB 88 OB 100 OB 121 OB 122
Cyclic processing Status interrupt (only if a DP/PA slave is required) Update interrupt (only if a DP/PA slave is required) Vendor-specific alarm (only if a DP/PA slave is required) I/O redundancy error CPU redundancy error Timeout error Power supply error Diagnostic interrupt Remove/insert interrupt CPU hardware error (only for CPU with this function) Program execution error Rack failure Stop avoidance Restart Programming error I/O access error
Use in CFC
With the "Generate module drivers" CFC function, the OB_BEGIN block is automatically installed in the OBs listed above.
270
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System
6.46 OB_BEGIN: CPU Diagnostics and AS Connection Diagnostics
Function and method of operation
Block OB_BEGIN is used to report and display CPU events and statuses. It reads the start information of the tasks (OBs), diagnostic data of the I/O and enables the relevant blocks for processing on the basis of the start events.
OB_BEGIN reads the start information of SFC 6 (RD_SINFO) or SFB 54 (RALRM) to identify the OB in which it is currently running.
If this information is not available, the block reads the logical basic address from the start information and converts it into the geographic address. This is available at the relevant OBs of the output structure CPU_DIAG the lower-level blocks can also access. On the basis of the geographic address, OB_BEGIN enables the relevant SUBNET blocks for further evaluation of the start information.
In the case of a diagnostic event (OB 82), the diagnostic data are simultaneously written to the CPU_DIAG.OB 82 structure along with the start information, using SFB54. Diagnostic (alarm) information of a length exceeding 59 bytes must contain the call of the relevant driver blocks.
In H systems, the current status of the two H CPUs is read from the system status list 71 (SSL71) in OB 100. A detailed description of the SSL71 appears in the reference manual titled System Software for S7-300/400 System and Standard Functions. The statuses of SSL_71.MASTER_0/1 and SSL_71.CPU_ERR_0/1 are updated in OB 72.
OB_BEGIN provides the diagnostic information of OB 55, OB 56 and OB 57 to the downstream blocks in its output structure CPU_OB_5X.
The block reports diagnostic events of an OB 88 block.
All OB 88 events are incoming events. OB 1 generates the relevant event message exiting state after a delay of approximately 10 seconds in order to allow the reporting of a new OB 88 event.
Error handling
Block OB_BEGIN evaluates error information from ALARM_8P and writes it to the relevant output parameters.
You will find additional information about this in the "Error information of output parameter MSG_STAT (Page 530)" section.
If the block installation sequence OB_BEGIN, xx blocks, ..., OB_END is not observed in an OB, the message "OB_END installation error, no OB 8x processing" will be output and QERR = TRUE set. In this case, the acyclic OBs do not evaluate the data. The downstream blocks will not be enabled.
Error information at output parameter STATUS of SFB 54 (RALRM) is handled as follows:
· The values 16#8096, 16#80A7, 16#80C0, 16#80C2, 16#80C3 or 16#80C4 at STATUS[2] and STATUS[3] indicate temporary errors. STATUS[3] of the corresponding OB will be set in the structure CPU_DIAG = 16#C4. Downstream blocks can read access the diagnostic data asynchronously.
· After any other error event, SFC 6 (RD_SINFO) reads the startup information once again and the message "OB_BEGIN diagnostic error RALRM STATUS = xxxxxxxx" is output. OB 1 generates the message exiting state once a delay of approximately 10 seconds has expired.
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
271
Family: @System 6.46 OB_BEGIN: CPU Diagnostics and AS Connection Diagnostics
Startup characteristics Block OB_BEGIN initializes the messages of ALARM_8P. In H systems (CPU_DIAG.H_MODE = TRUE), the current status of the two H CPUs is determined by reading SSL71 (see "Function and method of operation").
Overload Behavior
Messages exiting state associated with OB 121, OB 122 and OB 88 are generated subject to a delay of approx. 10 seconds. This on the one hand prevents blocking of the WinCC connection due to a high message transfer volume of these OBs. On the other hand, OB events may be due to the delay.
Time response Not available
Message response
ALARM_8P multiple instances are only called if OB_BEGIN is to output a message. It is only at this point that previously acknowledged messages are updated by the corresponding ALARM block. If the connection to WinCC is down, each ALARM_8P can hold up to two message statuses of its event ID.
The CPU generates a programming error (OB 121) only as an incoming event. OB 1 resets the relevant message to status exiting state. In order to avoid an excessive number of programming error messages, these will not be reported as outgoing until a delay time of 10 seconds has expired. The same applies to I/O access errors (OB 122) and OB 88 events.
The block generates the following messages in the OBs listed below:
OB OB 1
Start Event Cyclic processing
OB 72 CPU redundancy loss
Message
· Outgoing message with 10 s delay: Timeout (OB 80/OB 84)
· Program execution error (OB 80) · Programming error (OB 121) · Write I/O access error (OB 122) · Read I/O access error (OB 122) · Error code B#16#71: Nested stack error (OB 88) · Error code B#16#72: Master control relay stack error (OB 88) · Error code B#16#73: Synchronous error nesting depth exceeded (OB 88) · Error code B#16#74: U stack nesting depth exceeded in priority class stack
(OB 88) · Error code B#16#75: B stack nesting depth exceeded in priority class stack (OB
88) · Error code B#16#76: Local data allocation error (OB 88) · Error code B#16#78: Unknown opcode (OB 88) · Error code B#16#7A: Code length error (OB 88) CPU redundancy loss/return
272
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
OB OB 80
Start Event Timeout error
OB 84 CPU hardware error
OB 85 Program execution error OB 88 Stop avoidance
OB 100 OB 121 OB 122
Restart Programming error I/O access error
Family: @System 6.46 OB_BEGIN: CPU Diagnostics and AS Connection Diagnostics
Message Incoming message on timeout: · Cycle time exceeded · OB request: OBxx is busy · OB request: Overflow PRIOxx · TOD interrupt xx expired Interface error entering/exiting state; · Memory error detected and corrected by operating system. · Accumulation of detected and corrected memory errors. · Error in PC operating system. · Performance of an H-Sync coupling impaired. · Multiple-bit memory error detected and corrected. Incoming message on program-execution error: · OBxx not loaded · Access error - error xx: ... Incoming message on OB 88 events: · Error code B#16#71: Nested stack error · Error code B#16#72: Master control relay stack error · Error code B#16#73: Nesting depth exceeded on synchronization errors · Error code B#16#74: U-stack nesting depth exceeded in the priority class stack · Error code B#16#75: B-stack nesting depth exceeded in the priority class stack · Error code B#16#76: Local data allocation error · Error code B#16#78: Unknown opcode · Error code B#16#7A: Code length error Initialization of ALARM_8P Programming error incoming · Read I/O access, incoming · Write I/O access, entering state
Operator control and monitoring If asset management is used in the project and the diagnostic screens have been generated, the faceplate can be called via its block icon. For additional information, refer to the "Process Control System PCS 7; Maintenance Station" manual. · OB_BEGIN faceplate If no asset management is used in the project, the "OB-BEGIN" block icon is used to display avoidance of stop.
Additional information For additional information, refer to the sections: Message texts and associated values of OB_BEGIN (Page 275)
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
273
Family: @System 6.46 OB_BEGIN: CPU Diagnostics and AS Connection Diagnostics
Maintenance status MS (Page 533)
6.46.2
I/Os of OB_BEGIN
The factory setting of the block display in the CFC is identified in the "I/O" column: I/O name bold = I/O visible, I/O name normal = I/O not visible.
You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15)".
Input parameters
I/O (parameter) DIAG_BUF
EN_MSG EV_IDx
MS SUB0IDxx SUB1IDxx
Meaning
Data type
Entry in diagnostic buffer (relevant for maintenance person- nel)
Reserve
Message number ALARM_8P_x (x = 1 - 4, assigned by the ES)
Maintenance status
DP master system 1 IDxx (xx = 00 - 15)
DP master system 2 IDxx (xx = 00 - 15)
BOOL
BOOL DWORD
DWORD BYTE BYTE
De- fault 0
1 0
0 255 255
Output parameters
I/O (parameter)
CPU_DIAG CPU_OB_4X CPU_OB_5X CPU_OB_6X CPUERR_0 CPUERR_1 EN_SUBx MASTER_0 MASTER_1 MSGSTATx O_MS QERR QMSGERx SZL_71
Meaning
System structure: CPU diagnostics Start information OB 40 - OB 47 Start information OB 55, OB 56, OB 57 Start information OB 60 - OB 64 1 = CPU error in rack 0 *) 1 = CPU error in rack 1 *) Enable SUBNET x (x = 0 - 15) 1 = Master CPU in rack 0 1 = Master CPU in rack 1 STATUS output of ALARM_8P_x (x = 1 - 4) Maintenance status 1 = processing error Error output of ALARM_8P_x (x = 1 - 4) System structure: SZL71
Data type
STRUCT STRUCT STRUCT STRUCT BOOL BOOL BOOL BOOL BOOL WORD DWORD BOOL BOOL STRUCT
De- fault
0 0 0 0 0 0 0 1 0
The structure of the CPU_DIAG is integrated as OUT in the OB_BEGIN block, and as IN_OUT in all other blocks with this I/O.
*) You will find additional information about CPU errors in the CPU Manual.
274
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.46 OB_BEGIN: CPU Diagnostics and AS Connection Diagnostics
Additional information For additional information, refer to the sections: Message texts and associated values of OB_BEGIN (Page 275) Maintenance status MS (Page 533)
6.46.3
Message texts and associated values of OB_BEGIN
Assignment of message text and message class The process control messages of ALARM_8P with EV_ID1 are assigned as follows:
Mes- sage block ALARM _8P
EV_ID1
Mes- OB no. sage number
1
OB 85
2
3
OB 84
4
-
5
OB 85
6
OB 122
7
OB 122
8
OB 84
Default message text
Message class
OB @7%d@ not loaded
PLC Process Control Message Failure
No message
Interface error
PLC Process Control Message Failure
Error installing OB_BEGIN/OB_END: No PLC Process Control Message OB@2%d@ processing of stack @1%d@ Failure
Access error-Error @7%d@: @10%2s@@8%d@/@9%d@
PLC Process Control Message Failure
Read error I/O: @4%2s@@5%d@ Addr: PLC Process Control Message -
@6%d@
Failure
Write error I/O: @4%2s@@5%d@ Addr: PLC Process Control Message -
@6%d@
Failure
Performance of an H-Sync link negative- PLC Process Control Message -
ly affected
Failure
Messages 1, 4, 5, 6, 7 and 8 are only incoming events. They are reset to "outgoing" status during the normal run sequence (OB 1) of the block.
Associated Values of ALARM_8P with EV_ID1
Process control messages are generated with EV_ID1 and associated values via ALARM_8P. The table below shows how the associated values are assigned to the block parameters.
Message block ALARM_8P
EV_ID1
Associated val- ue
1 2 3 4
Block parameters
CPU_DIAG.OB_S_NUM_CNT TINFO_TOP_SI_NUM OB 72_supp_info 1 OB 122_BLK_TYP
Data type
BYTE BYTE WORD WORD
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
275
Family: @System 6.46 OB_BEGIN: CPU Diagnostics and AS Connection Diagnostics
Message block ALARM_8P
Associated val- ue
5 6 7 8 9 10
Block parameters
OB 122_BLK_NUM OB 122_MEM_ADDR OB 85_supp_info 1 OB 85_HW_supp_info 2_3 OB 85_LW_supp_info 2_3 OB 85_DKZ2_3
Data type
WORD WORD WORD WORD WORD WORD
The process control messages of ALARM_8P with EV_ID2 are assigned as follows:
Mes- sage block ALARM _8P
EV_ID2
Mes- OB no. sage number
1
OB 80
2
OB 80
3
OB 80
4
OB 84
5
OB 84
6
OB 84
7
OB 121
8
OB 84
Default message text
Message class
Net consumption of all OBs exceeds max. limit
Preventative Maintenance Standard
Emergency operation, cyclic OBs are used
PLC Process Control Message Failure
Priorities of the cyclic OBs not PCS 7 con- Preventative Maintenance -
form
Standard
Memory error detected and corrected by PLC Process Control Message -
operating system.
Failure
Accumulation of detected and corrected PLC Process Control Message -
memory errors
Failure
Error in PC operating system
PLC Process Control Message Failure
Programming error @1%d@: @2%2s@@5%d@ /@6%d@/@4%d@/ @3%d@
PLC Process Control Message Failure
Multiple-bit memory error detected and PLC Process Control Message -
corrected
Failure
Messages 1 to 3 are generated in CPU_RT (Page 31) and forwarded to OB_BEGIN.
Messages 4, 5, 7 and 8 are only incoming events. They are reset to "outgoing" status during the normal run sequence (OB 1) of the block.
Message 7 is to be interpreted as follows, in accordance with the error code number before the colon:
OB 121_BLK_TYP/OB 121_BLK_NUM/OB 121_PRG_ADDR/OB 121_FLT_REG/ OB 121_RESERVED_1.
This is described in the reference manual titled System Software for S7-300/400 System and Standard Functions. Example: 10.05.00 10:30:45 Programming error 35: FB44/1234/5/9
276
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.46 OB_BEGIN: CPU Diagnostics and AS Connection Diagnostics
Associated Values of ALARM_8P with EV_ID2
Process control messages are generated with EV_ID2 and associated values via ALARM_8P. The table below shows how the associated values are assigned to the block parameters.
Message block ALARM_8P
EV_ID2
Associated value
1 2 3 4 5 6
Block parameters
OB 121_SW_FLT OB 121_BLK_TYP OB 121_RESERVED_1 OB 121_FLT_REG OB 121_BLK_NUM OB 121_PRG_ADDR
Data type
BYTE WORD BYTE WORD WORD WORD
The process control messages of ALARM_8P with EV_ID3 are assigned as follows:
Mes- sage block ALARM _8P
EV_ID3
Mes- OB no. sage number
1
OB 80
2
OB 80
3
OB 80
4
OB 80
5
OB 80
6
OB 80
7
OB 80
8
Default message text
Message class
Cycle time exceeded: @1%d@ms OB@2%d@
PLC Process Control Message Failure
OB request: OB3x still being processed PLC Process Control Message Error
TOD interrupt OB @3%d@ expired (TOD PLC Process Control Message -
jump)
Failure
TOD interrupt OB @4%d@ expired (Stop/ PLC Process Control Message -
Run)
Failure
OB request: Overflow PRIO @5%d@
PLC Process Control Message Failure
Synchronous cycle interrupt-Timing er- PLC Process Control Message -
ror: OB@6%d@ PRIO @7%d@
Failure
Interrupt loss: OB@8%d@ PRIO @9%d@ PLC Process Control Message Failure
No message
Message 2 is generated in CPU_RT (Page 31) and forwarded to OB_BEGIN.
Messages 1 to 8 are only incoming events. They are reset to "outgoing" status during the normal run sequence (OB 1) of the block.
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
277
Family: @System 6.46 OB_BEGIN: CPU Diagnostics and AS Connection Diagnostics
Associated Values of ALARM_8P with EV_ID3
Process control messages are generated with EV_ID3 and associated values via ALARM_8P. The table below shows how the associated values are assigned to the block parameters.
Message block ALARM_8P
EV_ID3
Associated value 1 2
3 4 5
6
7
8
9
10
Block parameters
Data type
Cycle time (OB 80_supp_info 1)
WORD
Cause OB (OB 80_1st byte supplementary info BYTE 2_3)
Cycle time (OB 80_supp_info 1)
WORD
Cycle time (OB 80_supp_info 1)
WORD
Priority class (OB 80_2nd byte supplementary in- BYTE fo 2_3)
Cause OB (OB 80_1st byte supplementary info BYTE 2_3)
Priority class (OB 80_2nd byte supplementary in- BYTE fo 2_3)
Cause OB (OB 80_1st byte supplementary info BYTE 2_3)
Priority class (OB 80_2nd byte supplementary in- BYTE fo 2_3)
Cycle time (OB 80_supp_info 1)
WORD
Process control messages for ALARM_8P with EV_ID4 are assigned as follows:
Message block ALARM_8P
EV_ID_4
Message number
1
2
3
4 5 6 7 8
Default message text
Message class
OB 88(@6W%t#OB_BEGIN_TXT@): OB@1%d@ PRIO@2%d@ @3%2s@@4%d@ /@5%d@
Diagnostic error RALRM STATUS = @7%8X@
CPU loss of redundancy in rack @8%d@
PLC Process Control Message Failure
PLC Process Control Message Failure PLC Process Control Message Error No message No message No message No message No message
278
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.47 OB_BEGIN_PN: CPU diagnostics
Associated Values of ALARM_8P with EV_ID4
Message block ALARM_8P
EV_ID4
Associated value 1 2 3 4 5
6 7
Meaning
Cause OB (M_OB 88.FLT_OB) Priority class (M_OB 88.FLT_OB_PRIO) Block type (M_OB 88.BLK_TYP) Block number (M_OB 88.FLT_NUM) MC7 command causing error Relative address (M_OB 88.FLT_ADDR) Error number in OB_BEGIN_TXT (M_OB 88.T_OB 88) Status RALRM
You will find the message texts and their text numbers in "Text library for OB_BEGIN (Page 549)".
See also
Message Classes (Page 531)
6.47
OB_BEGIN_PN: CPU diagnostics
6.47.1
Description of OB_BEGIN_PN
Object name (type + number) FB 130 · I/Os of OB_BEGIN_PN (Page 279)
Area of application
Block OB_BEGIN_PN is used for CPU diagnostics of the automation system (AS). By installing the block in CFC, the system creates all acyclic tasks (OBs) in which the driver blocks of PCS 7 Basis Library are executed.
6.47.2
I/Os of OB_BEGIN_PN
The factory setting of the block display in the CFC is identified in the "I/O" column: I/O name bold = I/O visible, I/O name normal = I/O not visible.
You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15)".
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
279
Family: @System 6.47 OB_BEGIN_PN: CPU diagnostics
Input parameters
I/O (parameter) DIAG_BUF
EN_MSG EV_IDx
MS SUB0IDxx
SUB1IDxx
Meaning
Data type
Entry in diagnostic buffer (relevant for maintenance person- BOOL nel)
Reserve
BOOL
Message number ALARM_8P_x (x = 1 - 4, assigned by the ES)
DWORD
Maintenance status
DWORD
DP master system 1 IDxx (xx = 00 - 15)/PN IO system 1 (100-115)
BYTE
DP master system 2 IDxx (xx = 00 - 15)/PN IO system 2 (100-115)
BYTE
De- fault 0
1 0
0 255
255
Output parameters
I/O (parameter)
CPU_DIAG CPU_DIAG_PN CPU_OB_4X CPU_OB_5X CPU_OB_5X_PN CPU_OB_6X CPUERR_0 CPUERR_1 EN_SUBx MASTER_0 MASTER_1 MSGSTATx O_MS QERR QMSGERx SZL_71
Meaning
System structure: CPU diagnostics System structure: CPU diagnostics (PN) Start information OB 40 - OB 47 Start information OB 55, OB 56, OB 57 Start information OB 55, OB 56, OB 57 Start information OB 60 - OB 64 1 = CPU error in rack 0 *) 1 = CPU error in rack 1 *) Enable SUBNET x (DP: x = 0 - 15/PN: x = 100-115)) 1 = Master CPU in rack 0 1 = Master CPU in rack 1 STATUS output of ALARM_8P_x (x = 1 - 4) Maintenance status 1 = processing error Error output of ALARM_8P_x (x = 1 - 4) System structure: SZL71
Data type
STRUCT STRUCT STRUCT STRUCT STRUCT STRUCT BOOL BOOL BOOL BOOL BOOL WORD DWORD BOOL BOOL STRUCT
De- fault
0 0 0 0 0 0 0 1 0
The structure of the CPU_DIAG is integrated as OUT in the OB_BEGIN block, and as IN_OUT in all other blocks with this I/O.
*) You will find additional information about CPU errors in the CPU Manual.
Additional information For additional information, refer to the sections: Message texts and associated values of OB_BEGIN_PN (Page 281) Maintenance status MS (Page 533)
280
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.47 OB_BEGIN_PN: CPU diagnostics
6.47.3
Message texts and associated values of OB_BEGIN_PN
Assignment of message text and message class The process control messages of ALARM_8P with EV_ID1 are assigned as follows:
Message block ALARM_8P
EV_ID1
Mes- sage num- ber
1
2
3
4
5
6
7
8
OB no. Default message text
Message class
OB 85 OB @7%d@ not loaded
OB 84
Time-of-day synchronization not synchronized on higher-level
Interface error
OB 85 OB 122 OB 122
Assembly error OB_BEGIN_PN/OB_END: No OB@2%d@ processing stack @1%d@
Access error: @7%d@: @10%2s@@8%d@/@9%d@
I/O read access error: @4%2s@@5%d@ Addr: @6%d@
Write error I/O: @4%2s@@5%d@ Adr: @6%d@
PLC Process Control Mes- sage - Failure
PLC Process Control Mes- sage - Failure
PLC Process Control Mes- sage - Failure
PLC Process Control Mes- sage - Failure
PLC Process Control Mes- sage - Failure
PLC Process Control Mes- sage - Failure
PLC Process Control Mes- sage - Failure
No message
Messages 1, 4, 5, 6, 7 and 8 are only incoming events. They are reset to "outgoing" status during the normal run sequence (OB 1) of the block.
Associated values of ALARM_8P with EV_ID1
Process control messages are generated with EV_ID1 and associated values via ALARM_8P. The table below shows how the associated values are assigned to the block parameters.
Message block ALARM_8P
EV_ID1
Associated val- ue
1 2 3 4 5 6 7 8
Block parameter
CPU_DIAG_PN.OB_S_NUM_CNT TINFO_TOP_SI_NUM OB 72_supp_info 1 OB 122_BLK_TYP OB 122_BLK_NUM OB 122_MEM_ADDR OB 85_supp_info 1 OB 85_HW_supp_info 2_3
Data type
BYTE BYTE WORD WORD WORD WORD WORD WORD
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
281
Family: @System 6.47 OB_BEGIN_PN: CPU diagnostics
Message block ALARM_8P
Associated val- ue
9
10
Block parameter
OB 85_LW_supp_info 2_3 OB 85_DKZ2_3
Data type
WORD WORD
The process control messages of ALARM_8P with EV_ID2 are assigned as follows:
Message block ALARM_8P
EV_ID2
Mes- sage num- ber
1
2
3
4
5
6
7
8
OB no. Default message text
Message class
OB 80 OB 80 OB 80 OB 84 OB 84 OB 84 OB 121
OB 84
Net consumption of all OBs exceeds max. limit Emergency operation, cyclic OBs are used
Priorities of the cyclic OBs not PCS 7 con- form Memory error detected and corrected by operating system. Accumulation of detected and corrected memory errors Error in PC operating system
Programming error @1%d@: @2%2s@@5%d@ /@6%d@/@4%d@/ @3%d@ Multiple-bit memory error detected and corrected
Preventative Maintenance - Standard
PLC Process Control Mes- sage - Failure
Preventative Maintenance - Standard
PLC Process Control Mes- sage - Failure
PLC Process Control Mes- sage - Failure
PLC Process Control Mes- sage - Failure
PLC Process Control Mes- sage - Failure
PLC Process Control Mes- sage - Failure
Messages 1 to 3 are generated in CPU_RT (Page 31) and forwarded to OB_BEGIN_PN.
Messages 4, 5, 7 and 8 are only incoming events. They are reset to "outgoing" status during the normal run sequence (OB 1) of the block.
Message 7 is to be interpreted as follows, in accordance with the error code number before the colon:
OB 121_BLK_TYP/OB 121_BLK_NUM/OB 121_PRG_ADDR/OB 121_FLT_REG/ OB 121_RESERVED_1.
Associated Values of ALARM_8P with EV_ID2
Process control messages are generated with EV_ID2 and associated values via ALARM_8P. The table below shows how the associated values are assigned to the block parameters.
Message block ALARM_8P
EV_ID2
Associated value
1 2 3 4
Block parameter
OB 121_SW_FLT OB 121_BLK_TYP OB 121_RESERVED_1 OB 121_FLT_REG
Data type
BYTE WORD BYTE WORD
282
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.47 OB_BEGIN_PN: CPU diagnostics
Message block ALARM_8P
Associated value
5
6
Block parameter
OB 121_BLK_NUM OB 121_PRG_ADDR
Data type
WORD WORD
The process control messages of ALARM_8P with EV_ID3 are assigned as follows:
Message block ALARM_8P
EV_ID3
Mes- sage num- ber
1
2
3
4
5
6
7
8
OB no. Default message text
Message class
OB 80 OB 80 OB 80 OB 80 OB 80 OB 80 OB 80 -
Cycle time exceeded: @1%d@ms OB@2%d@ OB request: OB3x still being processed
TOD interrupt OB @3%d@ expired (TOD jump) TOD interrupt OB @4%d@ expired (Stop/ Run) OB request: Overflow PRIO @5%d@
Synchronous cycle interrupt-Timing er- ror: OB@6%d@ PRIO @7%d@ Interrupt loss: OB@8%d@ PRIO @9%d@
Time-of-day interrupt: External time-ofday synchronization failed
PLC Process Control Mes- sage - Failure
PLC Process Control Mes- sage - Error
PLC Process Control Mes- sage - Failure
PLC Process Control Mes- sage - Failure
PLC Process Control Mes- sage - Failure
PLC Process Control Mes- sage - Failure
PLC Process Control Mes- sage - Failure
PLC Process Control Mes- sage - Failure
Message 2 is generated in CPU_RT (Page 31) and forwarded to OB_BEGIN_PN.
Messages 1 to 8 are only incoming events. They are reset to "outgoing" status during the normal run sequence (OB 1) of the block.
Associated Values of ALARM_8P with EV_ID3
Process control messages are generated with EV_ID3 and associated values via ALARM_8P. The table below shows how the associated values are assigned to the block parameters.
Message block ALARM_8P
EV_ID3
Associated value
1 2 3 4 5 6
Block parameter
OB 121_SW_FLT OB 121_BLK_TYP OB 121_RESERVED_1 OB 121_FLT_REG OB 122_BLK_NUM OB 121_PRG_ADDR
Data type
BYTE WORD BYTE WORD WORD WORD
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
283
Family: @System 6.47 OB_BEGIN_PN: CPU diagnostics
Process control messages for ALARM_8P with EV_ID4 are assigned as follows:
Message block ALARM_8P
EV_ID4
Message number Default message text
Message class
1
OB 88(@6W%t#OB_BE-
PLC Process Control Message -
GIN_PN_TXT@): OB@1%d@ Failure
PRIO@2%d@
@3%2s@@4%d@ /@5%d@
2
OB_BEGIN_PN: Diagnostics PLC Process Control Message -
error ALARM STATUS =
Failure
@7%8X@
3
No message
4
Time-of-day interrupt: The PLC Process Control Message -
control deviation is out of tol- Failure
erance range
5
No message
6
No message
7
No message
8
No message
Associated values of ALARM_8P with EV_ID4
Message block ALARM_8P
EV_ID4
Associated value 1 2 3 4 5
6 7
Meaning
Cause OB (M_OB 88.FLT_OB) Priority class (M_OB 88.FLT_OB_PRIO) Block type (M_OB 88.BLK_TYP) Block number (M_OB 88.FLT_NUM) MC7 command causing error Relative address (M_OB 88.FLT_ADDR) Error number in OB_BEGIN_TXT (M_OB 88.T_OB 88) Status RALRM
You can find the message texts and their text numbers in the section "Text library for OB_BEGIN_PN (FB130) / OB_BEGIN_HPN (FB205) (Page 549)"
You can find additional information in the section: Message Classes (Page 531).
284
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
6.48
Family: @System 6.48 OB_BEGIN_HPN: H-CPU diagnostics
OB_BEGIN_HPN: H-CPU diagnostics
6.48.1
Description of OB_BEGIN_HPN
Object name (type + number) FB 205 · I/Os of OB_BEGIN_HPN (Page 285)
Area of application
Block OB_BEGIN_HPN is used for H-CPU diagnostics of the automation system (AS). By installing the block in CFC, the system creates all acyclic tasks (OBs) in which the driver blocks of PCS 7 Basis Library are executed.
Additional information For additional information, refer to the following sections: Message texts and associated values of OB_BEGIN_HPN (Page 287) Maintenance status MS (Page 533)
6.48.2
I/Os of OB_BEGIN_HPN
The factory setting of the block display in the CFC is identified in the "I/O" column: I/O name bold = I/O visible, I/O name normal = I/O not visible.
You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15) ".
Input parameters
I/O (parameter) CPU_RT_DATA DIAG_BUF
EN_MSG EV_IDx
MS R0_PLUG_TRANS_0_ADDR R0_PLUG_TRANS_1_ADDR R1_PLUG_TRANS_0_ADDR
Meaning
Data type
CPU_RT Performance data
Entry in diagnostic buffer (relevant for main- tenance personnel)
Reserve
Message number ALARM_8P_x (x = 1 - 5, as- signed by the ES)
Maintenance status
Address of Rack 0 Pluggable Transceiver 0
Address of Rack 0 Pluggable Transceiver 1
Address of Rack 1 Pluggable Transceiver 0
STRUCT BOOL
BOOL DWORD
DWORD INT INT INT
De- fault 0
1 0
0 0 0 0
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
285
Family: @System 6.48 OB_BEGIN_HPN: H-CPU diagnostics
I/O (parameter) R1_PLUG_TRANS_1_ADDR SUB0IDxx
SUB1IDxx
Meaning
Data type
Address of Rack 1 Pluggable Transceiver 1
DP master system 1 IDxx (xx = 00 - 15)/PN IO system 1 (100 - 115)
DP master system 2 IDxx (xx = 00 - 15)/PN IO system 2 (100 - 115)
INT BYTE
BYTE
De- fault 0 255
255
Output parameters
I/O (parameter) CPU_DIAG CPU_DIAG_PN CPU_OB_4X CPU_OB_5X CPU_OB_5X_PN CPU_OB_6X CPUERR_0 CPUERR_1 DIAG_INF EN_SUBx EXT_STAT EXT_STAT_1 MASTER_0 MASTER_1 MSGSTATx O_MS QERR QMSGERx SZL_71 TIME_STATUS
Meaning
System structure: CPU diagnostics System structure: CPU diagnostics Start information OB 40 - OB 47 Start information OB 55, OB 56, OB 57 Start information OB 55, OB 56, OB 57 Start information OB 60 - OB 64 1 = CPU error in rack 0 1 = CPU error in rack 1 Module Diagnostic Information Structure Enable SUBNET x (DP: x = 0 15 / PN: x = 100 - 115) Extended Status Extended Status 1 = Master CPU in rack 0 1 = Master CPU in rack 1 STATUS-output of the ALARM_8P_x (x = 1 - 5) Maintenance status 1 = processing error Output error of the ALARM_8P_x (x = 1 - 5) System structure: SZL71 Time synchronization status
Data type
STRUCT STRUCT STRUCT STRUCT STRUCT STRUCT BOOL BOOL STRUCT BOOL DWORD DWORD BOOL BOOL WORD DWORD BOOL BOOL STRUCT STRUCT
De- fault
0 0 0 0 0 0 0 0 0 0 1 0 -
The structures of the CPU_DIAG and CPU_DIAG_PN are integrated in the block OB_BEGIN_HPN as OUT, and in all other blocks with this connection as IN_OUT .
Additional information For additional information, refer to the sections: Message texts and associated values of OB_BEGIN_HPN (Page 287) Maintenance status MS (Page 533)
286
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
6.48.3
Family: @System 6.48 OB_BEGIN_HPN: H-CPU diagnostics
Message texts and associated values of OB_BEGIN_HPN
Assignment of message text and message class The process control messages of ALARM_8P with EV_ID1 are assigned as follows:
Message block ALARM_8P
EV_ID1
Mes- sage number
1
OB no. OB 85
2
-
3
OB 84
4
-
5
OB 85
6
OB 122
7
OB 122
8
Default message text
OB @7%d@not loaded
Time-of-day synchronization not synchronized on higher-level Interface error
Error installation OB_BEGIN_HPN/ OB_END: No OB@2%d@ processing stack @1%d@ Program execution error: @7%d@: @10%2s@@8%d@/@9%d@ Read error I/O: @4%2s@@5%d@ Addr: @6%d@ Write error I/O: @4%2s@@5%d@ Addr: @6%d@
Message class
PLC Process Control Mes- sage - Failure PLC Process Control Mes- sage - Failure PLC Process Control Mes- sage - Failure PLC Process Control Mes- sage - Failure
PLC Process Control Mes- sage - Failure PLC Process Control Mes- sage - Failure PLC Process Control Mes- sage - Failure No message
Messages 1, 4, 5, 6, 7 and 8 are only incoming events. They are reset to "outgoing" status during the normal run sequence (OB 1) of the block.
Associated Values of ALARM_8P with EV_ID1
Process control messages are generated with EV_ID1 and associated values via ALARM_8P. The table below shows how the associated values are assigned to the block parameters.
Message block ALARM_8P
EV_ID1
Associated val- ue
1 2 3 4 5 6 7 8 9 10
Block parameters
CPU_DIAG.OB_S_NUM_CNT TINFO_TOP_SI_NUM OB 72_supp_info 1 OB 122_BLK_TYP OB 122_BLK_NUM OB 122_MEM_ADDR OB 85_supp_info 1 OB 85_HW_supp_info 2_3 OB 85_LW_supp_info 2_3 OB 85_DKZ2_3
Data type
BYTE BYTE WORD WORD WORD WORD WORD WORD WORD WORD
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
287
Family: @System 6.48 OB_BEGIN_HPN: H-CPU diagnostics
The process control messages of ALARM_8P with EV_ID2 are assigned as follows:
Message block ALARM_8P
EV_ID2
Mes- sage num- ber
1
OB no. OB80
2
OB80
3
OB80
4
OB 84
5
OB 84
6
OB 84
7
OB 121
8
OB 84
Default message text
Message class
Net consumption of all OBs exceeds Preventative Mainte-
max. limit
nance - Standard
Emergency operation, cyclical OBs are PLC Process Control
reduced
Message - Failure
Priorities of cyclical OBs not conform- Preventative Mainte-
ing to PCS 7
nance - Standard
Memory error in operating system de- PLC Process Control
tected and corrected
Message - Failure
Accumulation of detected and correc- PLC Process Control
ted memory errors
Message - Failure
Error in PC operating system
PLC Process Control Message - Failure
Programming error @1%d@: @2%2s@@5%d@ /@6%d@/@4%d@/ @3%d@
PLC Process Control Message - Failure
Multiple-bit memory error detected and corrected
PLC Process Control Message - Failure
Messages 1 to 3 are generated in CPU_RT (Page 31) and forwarded to OB_BEGIN_HPN .
Messages 4, 5, 7 and 8 are only incoming events. They are reset to "outgoing" status during the normal run sequence (OB 1) of the block.
Message 7 is to be interpreted as follows, in accordance with the error code number before the colon:
OB 121_BLK_TYP/OB 121_BLK_NUM/OB 121_PRG_ADDR/OB 121_FLT_REG/ OB 121_RESERVED_1.
Associated values of ALARM_8P with EV_ID2
Process control messages are generated with EV_ID2 and associated values via ALARM_8P . The table below shows how the associated values are assigned to the block parameters.
Message block ALARM_8P
EV_ID2
Associated value
1 2 3 4 5 6
Block parameters
OB 121_SW_FLT OB 121_BLK_TYP OB 121_RESERVED_1 OB 121_FLT_REG OB 121_BLK_NUM OB 121_PRG_ADDR
Data type
BYTE WORD BYTE WORD WORD WORD
288
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.48 OB_BEGIN_HPN: H-CPU diagnostics
The process control messages of ALARM_8P with EV_ID3 are assigned as follows:
Message block ALARM_8P
EV_ID3
Mes- sage number
1
OB no. OB 80
2
OB 80
3
OB 80
4
OB 80
5
OB 80
6
OB 80
7
OB 80
8
-
Default message text
Message class
Cycle time exceeded: @1%d@ms OB@2%d@
PLC Process Control Mes- sage - Failure
OB request: OB3x still in process
PLC Process Control Mes- sage - Failure
Time-of-day interrupt OB @3%d@ elapsed (time jump)
PLC Process Control Mes- sage - Failure
Time-of-day interrupt OB @4%d@ elapsed (Stop/Run)
PLC Process Control Mes- sage - Failure
OB request: Overflow PRIO @5%d@ PLC Process Control Mes- sage - Failure
Synchronous cycle interrupt-Timing PLC Process Control Mes-
error: OB@6%d@ PRIO @7%d@
sage - Failure
Interrupt loss: OB@8%d@ PRIO @9%d@
PLC Process Control Mes- sage - Failure
Time-of-day interrupt: External time- PLC Process Control Mes-
of-day synchronization failed
sage - Failure
Message 2 is generated in CPU_RT (Page 31) and forwarded to OB_BEGIN_HPN.
Messages 1 to 8 are only incoming events. They are reset to "outgoing" status during the normal run sequence (OB 1) of the block.
Associated values of ALARM_8P with EV_ID3
Process control messages are generated with EV_ID3 and associated values via ALARM_8P . The table below shows how the associated values are assigned to the block parameters.
Message block ALARM_8P
EV_ID3
Associated value
1 2 3 4 5 6 7 8 9 10
Meaning
Cycle time Originator OB Cycle time Cycle time Priority class Originator OB Priority class Originator OB Priority class Cycle time
Message 2 is generated in CPU_RT (Page 31) and forwarded to OB_BEGIN_HPN.
Messages 1 to 8 are only incoming events. They are reset to "outgoing" status during the normal run sequence (OB 1) of the block.
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
289
Family: @System 6.48 OB_BEGIN_HPN: H-CPU diagnostics
The process control messages of ALARM_8P with EV_ID4 are assigned as follows:
Message block ALARM_8P
EV_ID_4
Message number
1
2 3 4 5 6 7 8
Default message text
Message class
OB 88(@6W%t#OB_BE-
PLC Process Control Message -
GIN_HPN_TXT@): OB@1%d@
Failure
PRIO@2%d@ @3%2s@@4%d@ /@5%d@
Diagnostics error RALRM STATUS = @7%8X@
PLC Process Control Message Failure
CPU loss of redundancy in rack @8%d@ PLC Process Control Message Error
Time-of-day interrupt: The control devi- PLC Process Control Message -
ation is out of tolerance range
Failure
UR0/Transceiver 0: Maintenance alarm PLC Process Control Message Failure
UR0/Transceiver 1: Maintenance alarm PLC Process Control Message Failure
UR1/Transceiver 0: Maintenance alarm PLC Process Control Message Failure
UR1/Transceiver 1: Maintenance alarm PLC Process Control Message Failure
Associated values of ALARM_8P with EV_ID4
Message block ALARM_8P
EV_ID4
Associated value 1 2 3 4 5
6 7 8
Meaning
Cause OB (M_OB 88.FLT_OB) Priority class (M_OB 88.FLT_OB_PRIO) Block type (M_OB 88.BLK_TYP) Block number (M_OB 88.FLT_NUM) MC7 command causing error Relative address (M_OB 88.FLT_ADDR) Error number in OB_BEGIN_TXT (M_OB 88.T_OB 88) Status RALRM CPU rack number
Message 2 is generated in CPU_RT (Page 31) and forwarded to OB_BEGIN_HPN.
Messages 1 to 8 are only incoming events. They are reset to "outgoing" status during the normal run sequence (OB 1) of the block.
290
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.48 OB_BEGIN_HPN: H-CPU diagnostics
The process control messages of ALARM_8P with EV_ID5 are assigned as follows:
Message block ALARM_8P
EV_ID_5
Message number
1
2
3
4
5
6
7
8
Default message text
Message class
UR0/Transceiver 0: Maintenance re- quired
Preventative Maintenance Standard
UR0/Transceiver 0: Maintenance deman- PLC Process Control Message -
ded
Error
UR0/Transceiver 1: Maintenance re- quired
Preventative Maintenance Standard
UR0/Transceiver 1: Maintenance deman- PLC Process Control Message -
ded
Error
UR1/Transceiver 0: Maintenance re- quired
Preventative Maintenance Standard
UR1/Transceiver 0: Maintenance deman- PLC Process Control Message -
ded
Error
UR1/Transceiver 1: Maintenance re- quired
Preventative Maintenance Standard
UR1/Transceiver 1: Maintenance deman- PLC Process Control Message -
ded
Error
Associated values of ALARM_8P with EV_ID5
Message block ALARM_8P
EV_ID5
Associated value 1 2 3 4 5
6 7
Meaning
Cause OB (M_OB 88.FLT_OB) Priority class (M_OB 88.FLT_OB_PRIO) Block type (M_OB 88.BLK_TYP) Block number (M_OB 88.FLT_NUM) MC7 command causing the error Relative address (M_OB 88.FLT_ADDR) Error number in OB_BEGIN_HPN_TXT (M_OB 88.T_OB 88) Status RALRM
You can find the message texts and their text numbers in the section "Text library for OB_BEGIN_PN (FB130) / OB_BEGIN_HPN (FB205) (Page 549)".
You can find additional information in the section: Message Classes (Page 531).
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
291
Family: @System 6.49 OB_DIAG1: OB diagnostics for avoiding stoppages in DPV1 master systems
6.49
OB_DIAG1: OB diagnostics for avoiding stoppages in DPV1 master systems
6.49.1
Description of OB_DIAG1
Object name (type + number) FB 118 · OB_DIAG1 block I/Os (Page 295)
Area of application
Block OB_DIAG1 monitors the failure and recovery of DP or PA slaves (referred to as "slaves" below). The slaves can be connected to a DPV0 or DPV1 master system, or to a DPV1 DP/PA link (Y link). OB_DIAG1 blocks further evaluation if a slave is defective (frequent producer) to prevent the CPU stopping. It indicates the preferred channel of the active slave in an H system. The indicated preferred channel 1 (SUBN1ACT ) is always TRUE, if the slave is downstream of a DP/PA link (Y link) and is active.
Calling OBs
The block must be installed in the run sequence in the following OBs:
OB 1 OB 70 OB 72 OB 82 OB 83 OB 85 OB 86 OB 100 OB 55 OB 56 OB 57
Cyclic program I/O redundancy error CPU redundancy error Diagnostic interrupt Insert/remove module interrupt Program execution error Rack failure Warm restart Status interrupt (only as required) Update interrupt (only as required) Manufacturer-specific alarms (only as required)
The driver generator only installs the block in OB 55, OB 56 and OB 57 if diagnostic messages are to be expected from these locations; consequently OB 5x are not entered in this block's task list.
292
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Use in CFC
Family: @System 6.49 OB_DIAG1: OB diagnostics for avoiding stoppages in DPV1 master systems
The following actions are executed automatically with the "Generate module drivers" CFC function: · Block OB_DIAG1 is installed downstream of the SUBNET/DPAY_V1 block (when used
downstream of a DP/PA or Y link). · The RACK_NO, LADDR, DADDR, EN_MSG_D, SUBN1_ID, SUBN2_ID, and SUBN_TYP inputs are
configured. · The EN input is interconnected with the output of an AND block.
The block inputs will be interconnected with output EN_SUBx (x = DP master system ID) of the OB_BEGIN block and with output EN_Rxxx (xxx = rack/station number) of the SUBNET block. · The CPU_DIAG OUT structure of the OB_BEGIN block and SUB_DIAG of the SUBNET block are interconnected with the IN_OUT structures of the same name of block OB_DIAG. · RAC_DIAG_I is interconnected with its own RAC_DIAG OUT structure when used in a DP master system. · RAC_DIAG_I is interconnected with the RAC_DIAG OUT structure of the DPAY_V1 block when used downstream of a Y link.
Function and method of operation
The DPA_LINK block input receives information on the operational status of the slave, in other words whether it is in use on a DP master system (DPA_LINK = FALSE) or downstream of a DP/PA link (Y link). If the slave is connected to a DP master system, a failure is reported in OB 86. If the slave is connected downstream of a DP/PA link (Y link), the failure is reported in OB 83.
The block counts the number of calls to an acyclic OB of a block instance before an OB 1 can be executed.
OB_DIAG1 indicates higher-level errors of the CPU, DP master/slave (QRACKF, SUBN1ERR, SUBN2ERR). It determines the preferred channel of connected DP slaves (SUBN1ACT, SUBN2ACT). The group error message QRACKF indicates failure of the DP master or slave. An active DP slave has lost redundancy if one of the output parameters SUBN1ERR or SUBN2ERR = TRUE.
Start and diagnostic information is read from the CPU_DIAG structure, which is interconnected with the CPU_DIAG structure of the OB_BEGIN block.
The block evaluates error events, and uses the diagnostic address DADDR of the slave (on the DP master system only) to determine the currently active preferred channel (SUBN1ACT, SUBN2ACT) of redundant PROFIBUS DP interface circuits.
The slaves downstream of a DP/PA link (Y link) are not always active. In this case, the diagnostic address DADDR is the diagnostic address of the link. The active preferred channel (SUBN1ACT, SUBN2ACT) is displayed here by the DP/PA link (Y link).
The DP master systems or DP/PA links (Y link) must be operated in DPV1 mode (V1-MODE = TRUE).
Failure and return of a DP slave are reported with ALARM_8P. The message function for all messages can be disabled with EN_MSG = FALSE.
The "Device failure" message can be disabled with EM_MSG_D = FALSE (see "Message Response").
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
293
Family: @System
6.49 OB_DIAG1: OB diagnostics for avoiding stoppages in DPV1 master systems
Overload behavior
Block OB_DIAG1 counts the frequency of the calls to the acyclic OB 55, OB 56, OB 57, OB 82, and OB 86 blocks (except in the case of a DP master system failure, see SUBNET block). If the block is downstream of a DP/PA or Y link, the calls will be counted in OB 83, rather than in OB 86. The following section deals only with OB 86.
Each OB is assigned a counter that is checked for the condition > 5. If this condition is fulfilled, the block sets EN_F = FALSE (disable function block). The counters are reset in OB 1. The output EN_F = TRUE (enable function block) is set in all other OBs.
OB_DIAG1 reports failure of the blocks mentioned above in OB 1, OB 82 or OB 86, including the geographic address of the slave.
OB 55, OB 56, OB 57 and OB 82 are locked in the event of an overload, however, so the event is not evaluated in the downstream blocks. The outputs cannot correspond to the current slave status. If an OB is locked and no more slave events have been reported after a delay of around 1 minute, if it is OB 86 that is disabled, the slave status is checked, and the outputs are updated. It may take several cycles to update the slave status.
If it is OB 82 that is disabled, rather than OB 86, the EN_DIAG variable is set to TRUE after around 1 minute. The interconnected DP slave block can then fetch the current diagnostic data for the slave, and update its own data. The same applies to OB 55, OB 56, and OB 57.
The "outgoing" message about the fault is generated when the OB lock is canceled, and either a new event has occurred for this OB or the wait time has elapsed.
Redundancy
The block supports redundant DP master systems in an H system (distributed I/Os only). The SUBN1_ID (connection to CPU 0) and SUBN2_ID (connection to CPU 1) inputs of the OB_DIAG1 block are configured with the numbers of the redundant DP master systems. If the DP master systems are not redundant, the remaining input is set to 16#FF (default).
Startup characteristics
The availability of the slave is checked. In H systems the preferred channel of the slave is determined (active slaves only).
Error handling
The block evaluates the error information from ALARM_8P, and writes it to the relevant output parameter.
You will find additional information about this in the "Error information of output parameter MSG_STAT (Page 530)" section.
294
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.49 OB_DIAG1: OB diagnostics for avoiding stoppages in DPV1 master systems
Message response
The multiple instances ALARM_8P are only called if a message is to be output by this instance. It is only at this point that previously acknowledged messages are updated by the corresponding ALARM block. If the connection to WinCC is down, each ALARM_8P instance can hold up to two message statuses of its event ID. (and generally no more than two messages). The block generates the messages listed below:
OB no. Start Event
1
Cyclic processing
72
CPU redundancy loss
70
Redundancy loss
83
Removal/insertion
86
Rack failure
100 Restart
Message
Call of ALARM_8P due to incomplete transfer or unacknowl- edged message
If no redundant diagnostic repeater is connected to this CPU, the "Slave" failure/return message is output.
If there is no redundant slave connected to this DP master sys- tem, message "Device" failure/return, otherwise message "Slave" redundancy loss/return
Message "Slave" failure/return
Message "Slave" failure/return
Initialization of ALARM_8P
If the diagnostic blocks (e.g., MOD_PAL0) of a device also report the failure of a device, the "Device failure" message can be disabled with EN_MSG_D = FALSE (this is done automatically by the driver generator).
Operator control and monitoring
If asset management is used in the project and the diagnostic screens have been generated, the faceplate can be called via its block icon.
For additional information, refer to the "Process Control System PCS 7; Maintenance Station" manual.
Additional information For additional information, refer to the sections: Message texts and associated values of OB_DIAG1 (Page 297) Maintenance status MS (Page 533)
6.49.2
I/Os of OB_DIAG1
The factory setting of the block display in the CFC is identified in the "I/O" column: I/O name bold = I/O visible, I/O name normal = I/O not visible.
You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15)".
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
295
Family: @System 6.49 OB_DIAG1: OB diagnostics for avoiding stoppages in DPV1 master systems
Input parameters
I/O (parameter) DADDR DELAY DIAG_BUF
DP_SL_DIAG DPA_LINK DPA_M EN_MSG EN_MSG_D EV_ID FEATURE IO_ADDR LADDR MS PADP_ADR RACK_NO SLOT_NO SUBN_TYP SUBN1_ID SUBN2_ID
Meaning
Data type Default
Diagnostic address of the slave or DP/PA link
INT
0
Alarm delay time [s]
INT
15
Entry in diagnostic buffer (relevant for maintenance person- BOOL
0
nel)
DP slave diagnostics
STRUCT
Slave connection: 0 = DP master system 1 = Link
BOOL
0
Status of the PA or DP slave module (DPV0)
STRUCT
1 = enable message
BOOL
1
1 = Enable message "Device failure"
BOOL
1
Message number
DWORD
0
Feature parameter
BYTE
0
Address of the slave
INT
0
Logical basic address of the slave
INT
0
Maintenance status
DWORD
0
Address of the PA/DP slave
BYTE
255
Rack number
BYTE
255
Slot number 0 of the slave at the DP/PA Link
BYTE
255
1 = External DP interface
BOOL
0
ID of the primary DP master system
BYTE
255
ID of the redundant DP master system
BYTE
255
Output parameters
I/O (parameter) DP_SL_DI- AG_OUT EN_DIAG EN_F MSG_ACK MSG_STAT O_MS QRACKF RAC_DIAG SUBN1ACT SUBN1ERR SUBN2ACT SUBN2ERR V1_MODE
Meaning
DP slave diagnostics
1 = Read diagnostics with SFC 13 1 = Enable function/function block Message acknowledgment Message error information Maintenance status 1 = higher-level error System structure: RACK diagnostics 1 = Slave 1 is active 1 = Error in the primary DP master system 1 = Slave 2 is active 1 = Error in the redundant DP master system 1 = DPV1 mode of the DP master system
Data type
STRUCT
BOOL BOOL WORD WORD DWORD BOOL STRUCT BOOL BOOL BOOL BOOL BOOL
Default
0 0 0 0 0 0
0 0 0 0 0
296
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.49 OB_DIAG1: OB diagnostics for avoiding stoppages in DPV1 master systems
In/out parameters
I/O (parameter) ACC_ID CPU_DIAG CPU_OB_5X RAC_DIAG_I SUB_DIAG
Meaning
1 = Accept MODE settings System structure: CPU diagnostics OB_5x start information System structure: RACK diagnostics System structure: SUBNET diagnostics
Data type
BOOL STRUCT STRUCT STRUCT STRUCT
Default 0
Additional information For additional information, refer to the sections: Message texts and associated values of OB_DIAG1 (Page 297) Maintenance status MS (Page 533)
6.49.3
Message texts and associated values of OB_DIAG1
Assignment of message text and message class
Message No. 1 2 3 4 5 6 7 8
Default message text
DP slave @4%d@/ @2%d@: Redundancy loss
DP slave @1%d@/ @2%d@: Failure
DP slave @1%d@/ @2%d@/@3%d@ : Multiple failure
Device @1%d@/ @2%d@/@3%d@: Mul- tiple alarm (OB 82)
Device @1%d@/ @2%d@/@3%d@: Mul- tiple alarm (OB 55)
Device @1%d@/ @2%d@/@3%d@: Mul- tiple alarm (OB 56)
Device @1%d@/ @2%d@/@3%d@: Mul- tiple alarm (OB 57)
Device @1%d@/ @2%d@/@3%d@: Fail- ure
Message class PLC Process Control Message - Error PLC Process Control Message - Failure PLC Process Control Message - Failure PLC Process Control Message - Failure PLC Process Control Message - Failure PLC Process Control Message - Failure PLC Process Control Message - Failure PLC Process Control Message - Failure
Assignment of Associated Values
Associated value 1 2
Block parameters ID of the primary DP master system (SUBN_ID) Rack/station number (RACK_NO)
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
297
Family: @System 6.50 OB_DIAG1_PN: OB diagnostics for avoiding stoppages in DPV1 master systems
Associated value 3 4
Block parameters Slot number (SLOT_NO) Subnet ID of the master in the event of redundancy loss (SUBN2_ID)
See also
Message Classes (Page 531)
6.50
OB_DIAG1_PN: OB diagnostics for avoiding stoppages in DPV1 master systems
6.50.1
Description of OB_DIAG1_PN
Object name (type + number) FB 202 · I/Os of OB_DIAG1_PN (Page 298)
Area of application
Block OB_DIAG1_PN monitors the failure and recovery of all Profinet standard slaves and the IE/ PB-Link. The slaves can be connected to an IE/PB. To prevent the CPU stopping, OB_DIAG1_PN blocks further evaluation if a slave is defective.
6.50.2
I/Os of OB_DIAG1_PN
The factory setting of the block display in the CFC is identified in the "I/O" column: I/O name bold = I/O visible, I/O name normal = I/O not visible.
You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15)".
Input parameters
I/O (parameter) DADDR DELAY DIAG_BUF
DPA_LINK EN_MSG
Meaning
Data type
IE/PB link diagnostic address Alarm delay time [s] Entry in diagnostic buffer (relevant for maintenance per- sonnel) Slave connection: 0 = PN-IO Master 1 = IE/PB link 1 = enable message
INT INT BOOL
BOOL BOOL
Default
0 15 0
0 1
298
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.50 OB_DIAG1_PN: OB diagnostics for avoiding stoppages in DPV1 master systems
I/O (parameter)
EN_MSG_D EV_ID FEATURE IO_ADDR LADDR MS PADP_ADR PNIO_ADR PORT1_ADR PORT1_CON- NECT PORT2_ADR PORT2_CON- NECT RACK_NO SLOT_NO SUBN_TYP SUBN1_ID SUBN2_ID PORT_ERR PN_REDUNDAN- CY_LEVEL
Meaning
1 = Enable message "Device failure" Message number ALARM_8P (assigned by the ES) Feature parameter Address of the slave Logical basic address of the slave Maintenance status Diagnostic address of the PN IO device Diagnostic address PN-IO interface Diagnostic address PORT 1 1=Port 1 connected
Diagnostic address PORT 2 1=Port 2 connected
Rack number Slot number of the slave at the IE/PB link 1 = external PN interface PN IO system 1 ID (100 - 115) PN IO system 2 ID (100 - 115) Port error PN redundancy level S1=16#1; S2=16#2; R1=16#4; R2=16#8
Data type
BOOL DWORD BYTE INT INT DWORD BYTE INT INT BYTE
INT BYTE
BYTE BYTE BOOL BYTE BYTE STRUCT BYTE
Default
1 0 0 0 0 0 255 0 0 0
0 0
255 255 0 255 255
0
Output parameters
I/O (parameter) EN_F EN_DIAG MSG_ACK MSG_STAT O_MS QRACKF RAC_DIAG SUBN1ACT SUBN1ERR SUBN2ACT SUBN2ERR V1_MODE
Meaning
1 = Enable function/function block 1 = Diagnostic event pending Message acknowledgment STATUS output of the ALARM_8P Maintenance status 1 = higher-level error System structure: RACK diagnostics 1 = PN IO device 1 active 1 = Error in the PN IO device 1 1 = PN IO device 2 active 1 = Error in the PN IO device 2 Not used
Data type
BOOL BOOL WORD WORD DWORD BOOL STRUCT BOOL BOOL BOOL BOOL BOOL
Default
0 0 0 0 0 0
0 0 0 0 0
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
299
Family: @System 6.50 OB_DIAG1_PN: OB diagnostics for avoiding stoppages in DPV1 master systems
In/out parameters
I/O (parameter)
ACC_ID CPU_DIAG_PN CPU_OB_5X RAC_DIAG_I SUB_DIAG
Meaning
1 = accept MODE settings System structure: CPU diagnostics OB_5x start information System structure: RACK diagnostics OB startup information
Data type
BOOL STRUCT STRUCT STRUCT STRUCT
Default 0
6.50.3
Message texts and associated values of OB_DIAG1_PN
Assignment of message text and message class The process control messages of ALARM_8P with EV_ID are assigned as follows:
Message block ALARM_8P
EV_ID
Message number
1
2
Default message text
Device @4%d@/@2%d@: Loss of re- dundancy Device @1%d@/@2%d@: Failure
3
Device @1%d@/@2%d@/@3%d@:
Multiple failure
4
Device @1%d@/ @2%d@/@3%d@:
Multiple alarm (OB 82)
5
Device @1%d@/ @2%d@/@3%d@:
Multiple alarm (OB 55)
6
Device @1%d@/ @2%d@/@3%d@:
Multiple alarm (OB 56)
7
Device @1%d@/ @2%d@/@3%d@:
Multiple alarm (OB 57)
8
Device @1%d@/ @2%d@/@3%d@:
Failure
Associated values of ALARM_8P with EV_ID:
Message class
PLC Process Control Mes- sage - Error
PLC Process Control Mes- sage - Failure
PLC Process Control Mes- sage - Failure
PLC Process Control Mes- sage - Failure
PLC Process Control Mes- sage - Failure
PLC Process Control Mes- sage - Failure
PLC Process Control Mes- sage - Failure
PLC Process Control Mes- sage - Failure
Associated value 1 2 3
Block parameter ID of the primary PN IO system (SUBN1_ID) Rack/station number (RACK_NO) Slot number (SLOT_NO)
Data type BYTE BYTE BYTE
300
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
See also
Family: @System 6.51 OB_DIAG2: OB Diagnostic Function - DP/PA Link - Extended Fieldbus Diagnostics
The process control messages of ALARM_8P with EV_ID1 are assigned as follows:
Message block ALARM_8P
EV_ID1
Message number
1
2
3
4
5
6
7
8
Default message text
Message class
Device @1%d@/@2%d@: Port1 Error
Device @1%d@/@2%d@: Port 2 Error
Device @1%d@/@2%d@: Maintenance demanded (PN-IO) Device @1%d@/@2%d@: Maintenance required (PN-IO) Device @1%d@/@2%d@/@3%d@: Port 1 Error Device @1%d@/@2%d@/@3%d@: Port 2 Error Device @1%d@/@2%d@/@3%d@: Main- tenance demanded (PN-IO) Device @1%d@/@2%d@/@3%d@: Main- tenance required (PN-IO)
PLC Process Control Message Error
PLC Process Control Message Error
PLC Process Control Message Error
Preventative Maintenance Standard
PLC Process Control Message Error
PLC Process Control Message Error
PLC Process Control Message Error
Preventative Maintenance Standard
Associated values of ALARM_8P with EV_ID1:
Associated value 1 2 3
Block parameter ID of the primary PN IO system (SUBN1_ID) Rack/station number (RACK_NO) Slot number (SLOT_NO)
Data type BYTE BYTE BYTE
Message Classes (Page 531)
6.51
OB_DIAG2: OB Diagnostic Function - DP/PA Link - Extended Fieldbus Diagnostics
6.51.1
Description of OB_DIAG2
Object name (type + number) FB 416 · OB_DIAG2 block I/Os (Page 303)
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
301
Family: @System 6.51 OB_DIAG2: OB Diagnostic Function - DP/PA Link - Extended Fieldbus Diagnostics
Area of application The OB_DIAG2 block monitors the DP/PA Link and coupler with extended fieldbus diagnostics for · Failure/return of the DP/PA Link · Redundancy loss · Diagnostic interrupts · Status interrupts and reports these events.
Calling OBs
The block must be installed in the run sequence in the following OBs:
OB 1 OB 55 OB 70 OB 72 OB 82 OB 83 OB 85 OB 86 OB 100
Cyclic program Status interrupt I/O redundancy error CPU redundancy error Diagnostic interrupt Insert/remove module interrupt Program execution error Rack failure Warm restart
Operator control and monitoring
If asset management is used in the project and the diagnostic screens have been generated, the faceplate can be called via its block icon.
For additional information, refer to the "Process Control System PCS 7; Maintenance Station" manual.
Additional information For additional information, refer to the sections: Message texts and associated values of OB_DIAG2 (Page 304) Maintenance status MS (Page 533)
See also
Error Information of Output Parameter MSG_STAT (Page 530)
302
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
6.51.2
Family: @System 6.51 OB_DIAG2: OB Diagnostic Function - DP/PA Link - Extended Fieldbus Diagnostics
I/Os of OB_DIAG2
The factory setting of the block display in the CFC is identified in the "I/O" column: I/O name bold = I/O visible, I/O name normal = I/O not visible. You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15)".
Input parameters
I/O (parameter) DADDR DIAG_BUF
DPA_LINK EN_MSG EN_MSG_D EV_ID LADDR MS PADP_ADR RACK_NO SLOT_NO SUBN_TYP SUBN1_ID SUBN2_ID
Meaning
Data type Default
Diagnostic address of the slave or DP/PA link
INT
0
Entry in diagnostic buffer (relevant for maintenance per- BOOL
0
sonnel)
Slave connection: 0 = DP master system 1 = Link
BOOL
0
1 = enable message
BOOL
1
1 = Enable message "Device failure"
BOOL
1
Message number
DWORD
0
Logical basic address of the slave
INT
0
Maintenance status
DWORD
0
Address of the PA/DP slave
BYTE
255
Rack number
BYTE
0
Slot number 0 of the slave at the DP/PA Link
BYTE
255
1 = External DP interface
BOOL
0
ID of the primary DP master system
BYTE
255
ID of the redundant DP master system
BYTE
255
Output parameters
I/O (parameter) EN_DIAG EN_F MOD_INF MSG_ACK MSG_STAT O_MS QRACKF RAC_DIAG SUBN1ACT SUBN1ERR SUBN2ACT SUBN2ERR V1_MODE
Meaning
1 = Read diagnostics with SFC 13 1 = Enable function/function block System structure: Module diagnostics Message acknowledgment Message error information Maintenance status 1 = higher-level error System structure: RACK diagnostics 1 = Slave 1 is active 1 = Error in the primary DP master system 1 = Slave 2 is active 1 = Error in the redundant DP master system 1 = DPV1 mode of the DP master system
Data type
BOOL BOOL STRUCT WORD WORD DWORD BOOL STRUCT BOOL BOOL BOOL BOOL BOOL
Default
0 0
0 0 0 0
0 0 0 0 0
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
303
Family: @System 6.51 OB_DIAG2: OB Diagnostic Function - DP/PA Link - Extended Fieldbus Diagnostics
In/out parameters
I/O (parameter) ACC_ID CPU_DIAG CPU_OB_5X RAC_DIAG_I SUB_DIAG
Meaning
1 = Accept MODE settings System structure: CPU diagnostics OB_5x start information System structure: RACK diagnostics System structure: SUBNET diagnostics
Data type
BOOL STRUCT STRUCT STRUCT STRUCT
Default 0
Additional information For additional information, refer to the sections: Message texts and associated values of OB_DIAG1 (Page 304) Maintenance status MS (Page 533)
6.51.3
Message texts and associated values of OB_DIAG2
Assignment of message text and message class The process control messages of ALARM_8P with EV_ID are assigned as follows:
Message No. 1
Default message text DP slave @3%d@/ @2%d@: Redundancy loss
2
DP slave @1%d@/ @2%d@: Failure
3
DP slave @1%d@/ @2%d@ : Multiple failure
4
DP slave @1%d@/ @2%d@: Multiple alarm (OB 82)
5
DP slave @1%d@/ @2%d@: Multiple alarm (OB 55)
6
DP slave @1%d@/ @2%d@: Multiple alarm (OB 56)
Message class
PLC Process Control Mes- sage - Error
PLC Process Control Mes- sage - Failure
PLC Process Control Mes- sage - Failure
PLC Process Control Mes- sage - Failure
PLC Process Control Mes- sage - Failure
PLC Process Control Mes- sage - Failure
304
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
See also
Family: @System 6.52 OB_DIAG_NC: OB diagnostic for network devices
Message No. 7
Default message text DP slave @1%d@/ @2%d@: Multiple alarm (OB 57)
8
DP slave @1%d@/ @2%d@: Maintenance required
Message class
PLC Process Control Mes- sage - Failure
Preventative Maintenance Standard
Associated values of ALARM_8P with EV_ID:
Associated value 1 2 3
Block parameters DP master system ID (SUBN1_ID) Rack/station number (RACK_NO) Subnet ID of the master in the event of redundancy loss (SUBN2_ID)
Message Classes (Page 531)
6.52
OB_DIAG_NC: OB diagnostic for network devices
6.52.1
Description of OB_DIAG_NC
Object name (type + number) FB 439 · I/Os of OB_DIAG_NC (Page 306)
Area of application
The OB_DIAG_NC block monitors the failure and recovery for all the PROFINET network components up to 32 network ports.
Calling OBs
The cyclic OB 1 and OB 82, OB 70, OB 72, OB 83, OB 85, OB 86 and OB 100.
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
305
Family: @System 6.52 OB_DIAG_NC: OB diagnostic for network devices
Use in CFC
The following actions are executed automatically with the "Generate module drivers" CFC function:
· The block will be placed for all profinet devices of the main family "13" (Network Components)
· The inputs will be connected and parameterized with the information out of hardware (Object Type)
Startup characteristics Initialization of the ALARM_8P blocks.
6.52.2
I/Os of OB_DIAG_NC
I/Os The factory setting of the block display in the CFC is identified in the "I/O" column.
I/O name bold = I/O visible, I/O name normal = I/O not visible.
You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15)".
Input parameters
I/O (parameter) DADDR DELAY DIAG_BUF
EN_MSG EN_MSG_D EV_ID FEATURE LADDR MS PNIO_ADR PORT1_ADR PORT1_CONNECT PORT2_ADR PORT2_CONNECT PORT3_ADR PORT3_CONNECT PORT4_ADR PORT4_CONNECT
Meaning
Diagnostic address of slave Interrupt delay (s) Entry in diagnostic buffer (relevant for maintenance personnel) 1 = Enable message 1 = Enable message "Device failure" Message number Reserve Logical address of slave Maintenance state Diagnostic address of PN-IO interface Diagnostic address PORT 1 1 = Port 1 connected Diagnostic address PORT 2 1 = Port 2 connected Diagnostic address PORT 3 1 = Port 3 connected Diagnostic address PORT 4 1 = Port 4 connected
Type INT INT BOOL
BOOL BOOL DWORD BYTE INT DWORD INT INT BYTE INT BYTE INT BYTE INT BYTE
Default 0 2 0
1 1 16#0 0 16#0 0 0 0 0 0 0 0 0 0 0
306
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.52 OB_DIAG_NC: OB diagnostic for network devices
I/O (parameter)
PORT5_ADR
PORT5_CONNECT
PORT6_ADR
PORT6_CONNECT
PORT7_ADR
PORT7_CONNECT
PORT8_ADR
PORT8_CONNECT
PORT9_ADR
PORT9_CONNECT
PORT10_ADR
PORT10_CON- NECT
PORT11_ADR
PORT11_CON- NECT
PORT12_ADR
PORT12_CON- NECT
PORT13_ADR
PORT13_CON- NECT
PORT14_ADR
PORT14_CON- NECT
PORT15_ADR
PORT15_CON- NECT
PORT16_ADR
PORT16_CON- NECT
PORT17_ADR
PORT17_CON- NECT
PORT18_ADR
PORT18_CON- NECT
PORT19_ADR
PORT19_CON- NECT
PORT20_ADR
PORT20_CON- NECT
PORT21_ADR
Meaning Diagnostic address PORT 5 1 = Port 5 connected Diagnostic address PORT 6 1 = Port 6 connected Diagnostic address PORT 7 1 = Port 7 connected Diagnostic address PORT 8 1 = Port 8 connected Diagnostic address PORT 9 1 = Port 9 connected Diagnostic address PORT 10 1 = Port 10 connected
Diagnostic address PORT 11 1 = Port 11 connected
Diagnostic address PORT 12 1 = Port 12 connected
Diagnostic address PORT 13 1 = Port 13 connected
Diagnostic address PORT 14 1 = Port 14 connected
Diagnostic address PORT 15 1 = Port 15 connected
Diagnostic address PORT 16 1 = Port 16 connected
Diagnostic address PORT 17 1 = Port 17 connected
Diagnostic address PORT 18 1 = Port 18 connected
Diagnostic address PORT 19 1 = Port 19 connected
Diagnostic address PORT 20 1 = Port 20 connected
Diagnostic address PORT 21
Type INT BYTE INT BYTE INT BYTE INT BYTE INT BYTE INT BYTE
INT BYTE
INT BYTE
INT BYTE
INT BYTE
INT BYTE
INT BYTE
INT BYTE
INT BYTE
INT BYTE
INT BYTE
INT
Default 0 0 0 0 0 0 0 0 0 0 0 0
0 0
0 0
0 0
0 0
0 0
0 0
0 0
0 0
0 0
0 0
0
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
307
Family: @System 6.52 OB_DIAG_NC: OB diagnostic for network devices
I/O (parameter)
PORT21_CON- NECT
PORT22_ADR
PORT22_CON- NECT
PORT23_ADR
PORT23_CON- NECT
PORT24_ADR
PORT24_CON- NECT
PORT25_ADR
PORT25_CON- NECT
PORT26_ADR
PORT26_CON- NECT
PORT27_ADR
PORT27_CON- NECT
PORT28_ADR
PORT28_CON- NECT
PORT29_ADR
PORT29_CON- NECT
PORT30_ADR
PORT30_CON- NECT
PORT31_ADR
PORT31_CON- NECT
PORT32_ADR
PORT32_CON- NECT
PORT_NUM
RACK_NO
SUBN_TYP
SUBN1_ID
SUBN2_ID
Meaning 1 = Port 21 connected
Diagnostic address PORT 22 1 = Port 22 connected
Diagnostic address PORT 23 1 = Port 23 connected
Diagnostic address PORT 24 1 = Port 24 connected
Diagnostic address PORT 25 1 = Port 25 connected
Diagnostic address PORT 26 1 = Port 26 connected
Diagnostic address PORT 27 1 = Port 27 connected
Diagnostic address PORT 28 1 = Port 28 connected
Diagnostic address PORT 29 1 = Port 29 connected
Diagnostic address PORT 30 1 = Port 30 connected
Diagnostic address PORT 31 1 = Port 31 connected
Diagnostic address PORT 32 1 = Port 32 connected
Highest port address Rack number 1 = External DP interface DP master system 1 ID ID of redundant subnet
Type BYTE
INT BYTE
INT BYTE
INT BYTE
INT BYTE
INT BYTE
INT BYTE
INT BYTE
INT BYTE
INT BYTE
INT BYTE
INT BYTE
INT BYTE BOOL BYTE BYTE
Default 0
0 0
0 0
0 0
0 0
0 0
0 0
0 0
0 0
0 0
0 0
0 0
0 0 0 255 255
308
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.52 OB_DIAG_NC: OB diagnostic for network devices
Out parameters
I/O (parameter)
MSG_ACK MSG_STAT O_MS EN_RST_DIAG PORT_EXIST PORT_ACTIVE PORT_NOK PORT_NOKG MSG_ERR QRACKF RAC_DIAG SUBN1ACT SUBN1ERR V1_MODE
Meaning
Message acknowledged Message failure Maintenance state Reset enable Port exists Port active Port not OK Port not OK gone 1 = Message error 1 = higher level error System structure: RACK diagnostic 1 = Slave 1 active 1 = Slave 1 failure Not used
Type
WORD WORD DWORD BOOL DWORD DWORD DWORD DWORD BOOL BOOL STRUCT BOOL BOOL BOOL
Default 0 0 0 0 0 0 0 0 0 0
0 0 0
In/out parameters
I/O (parameter) DIAG_RST ACC_ID CPU_DIAG_PN CPU_OB_5X RAC_DIAG_I SUB_DIAG
Meaning Reset of diagnostic values Accept new ID settings System structure: CPU diagnostic OB_5x start information System structure: RACK diagnostic OB start information
Type BOOL BOOL STRUCT STRUCT STRUCT STRUCT
Default 0 0
You can find additional information in the section: Message Classes (Page 531).
6.52.3
Message texts and associated values of OB_DIAG_NC
Assignment of message text and message class The process control messages of ALARM_8P with EV_ID are assigned as follows:
Message No. 1
Default message text Device @3%d@/@2%d@: Maintenance alarm
2
Device @3%d@/@2%d@: Maintenance demanded
Message class
PLC Process Control Mes- sage - Failure
PLC Process Control Mes- sage - Error
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
309
Family: @System 6.53 OB_DIAGF: Monitoring of the FF link and coupler
Message No. 3
Default message text Device @3%d@/@2%d@: Maintenance required
4 5 6 7 8
Message class
Preventative Maintenance Standard No message No message No message No message No message
Associated values of ALARM_8P with EV_ID:
Associated val- Block parameters ue
1
not used
2
Rack/station number (RACK_NO)
3
PN-IO system number
Data type
BYTE BYTE
You can find additional information in the section: Message Classes (Page 531).
6.53
OB_DIAGF: Monitoring of the FF link and coupler
6.53.1
Description of OB_DIAGF
Object name (type + number) FB 146 · I/Os of OB_DIAGF (Page 312)
Area of application The OB_DIAGF block monitors the FF link and coupler for · Failure and return of FF link and coupler · Redundancy loss · diagnostic interrupts and reports these events. The OB_DIAGF block runs acyclically and is enabled to run by the higher-level SUBNET block.
310
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Calling OBs
Family: @System 6.53 OB_DIAGF: Monitoring of the FF link and coupler
The block must be installed in the run sequence downstream from the SUBNET block in the following OBs (this is done automatically in the CFC):
OB no. 1 72 70 82 83 85 86 100
Start Event Cyclic processing CPU redundancy loss Redundancy loss Diagnostic interrupt Removal/insertion Program execution error Module driver failure Restart
Use in CFC
The following actions are executed automatically with the "Generate module drivers" CFC function:
· The OB_DIAGF block is installed downstream from the SUBNET block.
· The DADDR, SUBN1_ID, SUBN2_ID, RACK_NO, COUP_RED, and SLOT_NO inputs are assigned parameters.
· The EN input is interconnected with the output of an AND block. The block inputs will be interconnected with output EN_SUBx (x = DP master system ID) of the OB_BEGIN block and with output EN_Rxxx (xxx = rack/station number) of the SUBNET block.
· The CPU_DIAG OUT structure of the OB_BEGIN block and SUB_DIAG of the SUBNET block are interconnected with the IN_OUT structures of the same name of block OB_DIAGF.
Message response
The DELAY input is used to delay the outputting of error messages for an outgoing, higherpriority error. For example, if the OB_DIAGF block recognizes an outgoing error at a DP master connected with it, it initially assumes that there is a faulty assigned DP slave in the rack it monitors, and sets the corresponding output SUBNxERR. The error status is not reset until the DP slave returns (in this case: OB 86, OB 70). The OB_DIAGF blocks suppress the potential slave failure for DELAY seconds so as not to trigger a surge of messages from DP slaves which are not yet synchronized when the master returns. An error message is only output to the OS when the DP slave has not reported its return before this delay time has expired.
Note: Do not set the value of DELAY too high, since messages reporting faulty DP slaves or their removal during a master failure will be output too late to the OS after the DP master returns.
Operator control and monitoring
If asset management is used in the project and the diagnostic screens have been generated, the faceplate can be called via its block icon.
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
311
Family: @System 6.53 OB_DIAGF: Monitoring of the FF link and coupler
For additional information, refer to the "Process Control System PCS 7; Maintenance Station" manual.
6.53.2
I/Os of OB_DIAGF
I/Os of OB_DIAGF The factory setting of the block display in the CFC is identified in the "I/O" column.
I/O name bold = I/O visible, I/O name normal = I/O not visible.
You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15)".
Input parameters
I/O (parameter) COUP_RED
DADDR DIAG_BUF
DELAY EN_MSG EV_ID1 EV_ID2 MS RACK_NO SUBN_TYP SUBN1_ID SUBN2_ID
Meaning
Data type Default
0 = No redundant structure 1 = Coupler redundancy 2 = Ring redundancy Diagnostic address of the FF link Entry in diagnostic buffer (relevant for maintenance personnel) Interrupt delay (s) 1 = enable message Message number Message number Maintenance status Number of the rack 1 = external DP interface ID of the primary DP master system ID of the redundant DP master system
BYTE
INT BOOL
INT BOOL DWORD DWORD DWORD BYTE BOOL BYTE BYTE
16#FF
0 0
15 1 0 0 0 16#FF 0 16#FF 16#FF
Output parameters
I/O (parameter) DINFO EN_F FF_DIAG MSG_ACK MSG_STAT O_MS
Meaning
Diagnostic information 1 = Enable function/function block Diagnostics of the FF device Message acknowledgment Message error Maintenance status
Data type Default
STRUCT
BOOL
0
STRUCT
WORD
0
WORD
0
DWORD
0
312
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.53 OB_DIAGF: Monitoring of the FF link and coupler
I/O (parameter)
QRACKF RAC_DIAG RETURN_CODE_O SUBN1ACT SUBN2ACT SUBN1ERR SUBN2ERR V1_MODE
Meaning
1 = higher-level error RACK diagnostics Return value 1 = Slave 1 is active 1 = Slave 2 is active 1 = Error in the primary DP master system 1 = Error in the redundant DP master system 1 = DPV1 mode of the DP master system active
Data type Default
BOOL
0
STRUCT
INT
0
BOOL
0
BOOL
0
BOOL
0
BOOL
0
BOOL
0
In/out parameters
I/O (parameter) ACC_ID CPU_DIAG SUB_DIAG
Meaning
1 = accept MODE settings System structure: CPU diagnostics System structure: SUBNET diagnostics
Data type Default
BOOL
0
STRUCT
STRUCT
6.53.3
Message texts and associated values of OB_DIAGF
Message texts and associated values of OB_DIAGF Assignment of message text and message class (Page 531)
Message block ALARM_8P
EV_ID1
Message No. Default message text
Message class
1
FF Link @4%d@/@2%d@: Loss of redun- PLC Process Control Message -
dancy
Error
2
FF link @1%d@/@2%d@: Failure
PLC Process Control Message -
Failure
3
FF link @1%d@/@2%d@: Multiple failure PLC Process Control Message -
Failure
4
FF link @1%d@/@2%d@: Multiple alarm PLC Process Control Message -
(OB 82)
Failure
5
Coupler @1%d@/@2%d@/2: Loss of re- PLC Process Control Message -
dundancy
Error
6
Coupler @1%d@/@2%d@/3: Loss of re- PLC Process Control Message -
dundancy
Error
7
FF-Link @1%d@/@2%d@/1:DIP switch PLC Process Control Message -
has a different DP address setting than at Failure
"power on" of the IM/Redundant config-
uration, neighboring IM has a different
DP address.
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
313
Family: @System 6.53 OB_DIAGF: Monitoring of the FF link and coupler
Message block ALARM_8P
EV_ID2
Message No. Default message text
Message class
8
FF link @1%d@/@2%d@/1: SDB_UUID PLC Process Control Message -
does not match saved UUID
Failure
1
Coupler @1%d@/@2%d@/2: Failure
PLC Process Control Message -
Failure
2
Coupler @1%d@/@2%d@/2: Conflict PLC Process Control Message -
with configuration:Coupler configura- Error
tion does not match determined config-
uration
3
Coupler @1%d@/@2%d@/2: External PLC Process Control Message -
connection, short circuit or wire break Error
detected
4
Coupler @1%d@/@2%d@/2: Loss of re- PLC Process Control Message -
dundancy in case of ring redundancy Error
5
Coupler @1%d@/@2%d@/3: Failure
PLC Process Control Message -
Failure
6
Coupler @1%d@/@2%d@/3: Conflict PLC Process Control Message -
with configuration: Coupler configura- Error
tion does not match determined config-
uration
7
Coupler @1%d@/@2%d@/3: External PLC Process Control Message -
connection, short circuit or wire break Error
detected
8
Coupler @1%d@/@2%d@/3: Loss of re- PLC Process Control Message -
dundancy in case of ring redundancy Error
Assignment of Associated Values Associated values of ALARM_8P with EV_ID1:
Associated value 1 2 3 4
Block parameters DP master system ID (SUBN_ID) Rack/station number (RACK_NO) ID of the redundant DP master system (SUBN2_ID) ID of the redundant DP master system (SUBN2_ID)
Associated values of ALARM_8P with EV_ID2:
Associated value 1 2
Block parameters DP master system ID (SUBN_ID) Rack/station number (RACK_NO)
314
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.54 OB_DIAGF2: Monitoring device-specific diagnostics for Foundation Fieldbus Compact Link IM 655-2 FF
6.54
OB_DIAGF2: Monitoring device-specific diagnostics for Foundation Fieldbus Compact Link IM 655-2 FF
6.54.1
Description of OB_DIAGF2
Object name (type + number) FB 418 · I/Os of OB_DIAGF2 (Page 316)
Area of application The OB_DIAGF2 block reports diagnostics events of a Foundation Fieldbus Compact Link IM 655-2 FF and monitors the following events: · Failure and return of FF link and coupler · Redundancy loss · diagnostic interrupts and reports these events.
Calling OBs
OB 1 OB72 OB 70 OB 82 OB 83 OB 85 OB 86 OB 100
Cyclic processing CPU redundancy loss Redundancy loss Diagnostic interrupt Removal/insertion Program execution error Module driver failure Restart
Operator control and monitoring
If asset management is used in the project and the diagnostic screens have been generated, the faceplate can be called via its block icon.
For additional information, refer to the "Process Control System PCS 7; Maintenance Station" manual.
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
315
Family: @System 6.54 OB_DIAGF2: Monitoring device-specific diagnostics for Foundation Fieldbus Compact Link IM 655-2 FF
6.54.2
I/Os of OB_DIAGF2
I/Os of OB_DIAGF2 The factory setting of the block display in the CFC is identified in the "I/O" column.
I/O name bold = I/O visible, I/O name normal = I/O not visible.
You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15)".
Input parameters
I/O (parameter) COUP_RED
DADDR DIAG_BUF
DELAY EN_MSG EV_ID1 EV_ID2 MS RACK_NO SUBN_TYP SUBN1_ID SUBN2_ID
Meaning
Data type Default
0 = No redundant structure 1 = Coupler redundancy 2 = Ring redundancy Diagnostic address of the FF link Entry in diagnostic buffer (relevant for maintenance personnel) Interrupt delay (s) 1 = enable message Message number Message number Maintenance status Number of the rack 1 = external DP interface ID of the primary DP master system ID of the redundant DP master system
BYTE
INT BOOL
INT BOOL DWORD DWORD DWORD BYTE BOOL BYTE BYTE
16#FF
0 0
15 1 0 0 0 16#FF 0 16#FF 16#FF
Output parameters
I/O (parameter)
DINFO EN_F FF_DIAG MSG_ACK MSG_STAT O_MS QRACKF RAC_DIAG RETURN_CODE_O SUBN1ACT
Meaning
Diagnostic information 1 = Enable function/function block Diagnostics of the FF device Message acknowledgment Message error Maintenance status 1 = higher-level error RACK diagnostics Return value 1 = Slave 1 is active
Data type Default
STRUCT
BOOL
0
STRUCT
WORD
0
WORD
0
DWORD
0
BOOL
0
STRUCT
INT
0
BOOL
0
316
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.54 OB_DIAGF2: Monitoring device-specific diagnostics for Foundation Fieldbus Compact Link IM 655-2 FF
I/O (parameter) SUBN2ACT SUBN1ERR SUBN2ERR V1_MODE
Meaning
1 = Slave 2 is active 1 = Error in the primary DP master system 1 = Error in the redundant DP master system 1 = DPV1 mode of the DP master system active
Data type Default
BOOL
0
BOOL
0
BOOL
0
BOOL
0
In/out parameters
I/O (parameter) ACC_ID CPU_DIAG SUB_DIAG
Meaning
1 = accept MODE settings System structure: CPU diagnostics System structure: SUBNET diagnostics
Data type Default
BOOL
0
STRUCT
STRUCT
6.54.3
Message texts and associated values of OB_DIAGF2
Message texts and associated values of OB_DIAGF2 Assignment of message text and message class (Page 531)
Message block ALARM_8P EV_ID1
Message Default message text No.
1
FF Link @1%d@/@2%d@:Maintenance alarm
2
FF Link @1%d@/@2%d@:Maintenance demanded
3
FF Link @1%d@/@2%d@:Maintenance required
4 5 6 7 8
Assignment of Associated Values
Associated value 1 2
Block parameters DP master system ID (SUBN1_ID) Rack/station number (RACK_NO)
Message class
PLC Process Control Mes- sage - Failure
PLC Process Control Mes- sage - Error
Preventative Maintenance - Standard
No message
No message
No message
No message
No message
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
317
Family: @System 6.55 OB_END: Reset stack pointer of OB_BEGIN
6.55
OB_END: Reset stack pointer of OB_BEGIN
6.55.1
Description of OB_END
Object name (type + number) FC 280 · OB_END block I/Os (Page 319)
Area of application The OB_END block is used to reset the stack pointer of OB_BEGIN and OB_BEGIN_PN.
Calling OBs
The OB_END block is the final entry in the OB that contains an OB_BEGIN and/or an OB_BEGIN_PN block.
OB 1 OB 55 OB 56 OB 57 OB 70 OB 72 OB 80 OB 81 OB 82 OB 83 OB 84 OB 85 OB 86 OB 88 OB 100 OB 121 OB 122
Cyclic processing Status interrupt (only as required) Update interrupt (only as required) Manufacturer-specific alarms (only as required) I/O redundancy error CPU redundancy error Timeout error Power supply error Diagnostic interrupt Remove/insert interrupt CPU hardware error (only for CPU with this function) Program execution error Rack failure Stop avoidance Restart Programming error I/O access error
Use in CFC
When the CFC function "Generate module drivers" is used, OB_END is automatically installed in the above OBs of the run sequence.
318
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Function
Family: @System 6.55 OB_END: Reset stack pointer of OB_BEGIN
The OB_END block decrements the stack pointer (NUM_CNT) of OB_BEGIN and OB_BEGIN_PN. In the event of an interruption, it enters the last interrupted OB number read from the CPU stack into the CPU_DIAG and CPU_DIAG_PN structure.
Error handling Not available
Startup characteristics Not available
Initial startup behavior Not available
Time response Not available
Message response Not available
Operator control and monitoring The block has no faceplate.
6.55.2
I/Os of OB_END
The factory setting of the block display in the CFC is identified in the "I/O" column: I/O name bold = I/O visible, I/O name normal = I/O not visible.
You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15)".
In-out parameters
I/O (parameter) CPU_DIAG CPU_DIAG_PN
Meaning
System structure: CPU diagnostics System structure: CPU diagnostics (PN)
Data type
STRUCT STRUCT
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
319
Family: @System 6.56 OB5X2OB5: OB5X PN information in STRUCT OB55, OB56, OB57
6.56
OB5X2OB5: OB5X PN information in STRUCT OB55, OB56, OB57
6.56.1
Description of OB5X2OB5
The function provides the information to be used on the output structure OB55_PN...OB57_PN. The function is inserted in sequence before the IM_TS_PN block.
Object name (type + number) FC 265 · I/Os of OB5X2OB5 (Page 320)
Area of application
This block is a system block and is used exclusively internally. For this reason, a Help is not available.
6.56.2
I/Os of OB5X2OB5
The factory setting of the block display in the CFC is identified in the "I/O" column:
I/O name bold = I/O visible, I/O name normal = I/O not visible.
You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15)".
Input parameters
I/O (parameter)
CPU_DIAG_PN
CPU_OB_5X_PN
Meaning
System structure: CPU diagnosis System structure: CPU diagnosis
Data type
STRUCT
STRUCT
Default
Output parameters
I/O (parameter) OB_55_PN OB_56_PN OB_57_PN
Meaning
System structure: CPU diagnosis System structure: CPU diagnosis System structure: CPU diagnosis
Data type
STRUCT STRUCT STRUCT
Default
320
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
6.57
Family: @System 6.57 OR_16_PN: QUALITY of 2 redundant Module (<= 16 Channels)
OR_16_PN: QUALITY of 2 redundant Module (<= 16 Channels)
6.57.1
Description of OR_16_PN
Object name (type + number) FB 428 · I/Os of OR_16_PN (Page 322)
Area of application
The OR_16_PN block generates a channel-granular value status from two redundant signal modules.
Calling OBs
OB 1 OB 100
Cyclic program Warm restart
Configuration
The following actions are executed automatically with the "Generate module drivers" CFC function:
· The OR_16_PN block is installed upstream in the OBs of the channel blocks that are interconnected with it.
· MODE1_x inputs are interconnected with the OMODE_xx outputs of the MOD_x block in the primary module.
· MODE2_x inputs are interconnected with the OMODE_xx outputs of the MOD_x block in the redundant module.
· The MOD_INF1 input structure is interconnected with the MOD_INF output structure of the MOD_x block in the primary module.
· The MOD_INF2 input structure is interconnected with the MOD_INF output structure of the MOD_x block in the redundant module.
· The ACTIV_H and ACTIV_L inputs are interconnected with the outputs of the same name of the RED block in the redundant module.
· The OMODE_xx outputs are interconnected with the relevant channel blocks.
· The OUT structure CPU_DIAG of the OB_BEGIN block is interconnected with the IN_OUT structures of the same name of the OR_16_PN block.
· The RACKF1 and RACKF2 inputs are interconnected with the QRACKF1 and QRACKF2 outputs of MOD_xx.
· The CH_INF_H and CH_INF_L inputs are interconnected with the outputs of the same name of the RED block.
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
321
Family: @System 6.57 OR_16_PN: QUALITY of 2 redundant Module (<= 16 Channels)
· The output parameter of DXCHG_xx is interconnected with the following channel block at the DataXchg parameter.
· The output parameter of O_MS is interconnected with the following channel block at the MS parameter.
Startup characteristics The OMODE_xx outputs are updated when the "Startup" bit is set.
Error handling The plausibility of input parameters is not checked.
Redundancy
Redundancy of the modules in an H system is monitored in the higher-level RED block.
6.57.2
I/Os of OR_16_PN
The factory setting of the block display in the CFC is identified in the "I/O" column:
I/O name bold = I/O visible, I/O name normal = I/O not visible.
You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15)".
Input parameters
I/O (parameter) ACTIV_L ACTIV_H RACKF1 RACKF2 CH_INF_L CH_INF_H RED_STAT MOD_STAT MOD_STAT_PN CHAN_NUM MODE1_xx MODE2_xx MS RED_LIB_PCS7 FEATURE
Meaning
Data type Default
1=Low module active
BOOL
0
1=High module active
BOOL
0
1=Rack 1 failure
BOOL
0
1=Rack 2 failure
BOOL
0
Low address: 1 = Channel x active
DWORD
0
High address: 1 = Channel x active
DWORD
0
Return value of RED_STATUS
INT
0
Reserve
WORD
0
MODUL_STATUS of PN RED_STATUS
DWORD
0
Total number of channels -1
INT
7
Module 1 mode channel xx (xx = 00 - 15) DWORD
0
Module 2 mode channel xx (xx = 00 - 15) DWORD
0
Maintenance State
DWORD
0
Reserve
BOOL
0
Reserve
DWORD
0
322
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
In/Out parameters
I/O (parameter) CPU_DIAG MOD_INF1 MOD_INF2 DXCHG1_xx
DXCHG11_xx
DXCHG2_xx
DXCHG21_xx
MS_XCHG1_xx MS_XCHG2_xx DEPASS_RED_PCS7
Out parameters
I/O (parameter) QERR QMODF1 QMODF2 QDISCREP CH_ALM CH_WRN O_MS CH_EXIST CH_ACTIVE CH_OK EXT_STAT EXT_STAT_A OMODE_xx DXCHG_xx
DXCHG_1_xx
MS_XCHG_xx RETURN_VAL EXT_INFO
Family: @System 6.57 OR_16_PN: QUALITY of 2 redundant Module (<= 16 Channels)
Meaning
Data type Default
STRUCT
Module 1 information structure
STRUCT
Module 2 information structure
STRUCT
Bidirectional data exchange channel xx (xx DWORD
0
= 00 - 15)
Bidirectional data exchange channel xx (xx DWORD
0
= 00 - 15)
Bidirectional data exchange channel xx (xx DWORD
0
= 00 - 15)
Bidirectional data exchange channel xx (xx DWORD
0
= 00 - 15)
MS exchange channel xx (xx = 00 - 15) DWORD
0
MS exchange channel xx (xx = 00 - 15) DWORD
0
1=Depassivation
BOOL
0
Meaning
Data type Default
1=Runtime error
BOOL
1
1=Module 1 pulled / out of order
BOOL
0
1=Module 2 pulled / out of order
BOOL
0
1=Module discrepancy
BOOL
0
Channel Failure of redundancy pair
DWORD
0
Channel Redundancy loss
DWORD
0
Maintenance State
DWORD
0
Channel exist
DWORD
0
Channel active
DWORD
0
Channel OK
DWORD
0
Maintenance release Extended status DWORD
0
Extended status application
DWORD
0
Mode channel xx (xx = 00 - 15)
DWORD
0
Bidirectional data exchange channel xx (xx DWORD
0
= 00 - 15)
Bidirectional data exchange channel xx (xx DWORD
0
= 00 - 15)
MS exchange channel xx (xx = 00 - 15) DWORD
0
Return value of FC451
INT
0
Extension information of FC451
INT
0
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
323
Family: @System 6.58 OR_32_PN: QUALITY of 2 redundant Module (<= 32 Channels)
6.58
OR_32_PN: QUALITY of 2 redundant Module (<= 32 Channels)
6.58.1
Description of OR_32_PN
Object name (type + number) FB 429 · I/Os of OR_32_PN (Page 325)
Area of application
The OR_32_PN block generates a channel-granular value status from two redundant signal modules.
Calling OBs
OB 1 OB 100
Cyclic program Warm restart
Configuration
The following actions are executed automatically with the "Generate module drivers" CFC function:
· The OR_32_PN block is installed upstream in the OBs of the channel blocks that are interconnected with it.
· MODE1_x inputs are interconnected with the OMODE_xx outputs of the MOD_x block in the primary module.
· MODE2_x inputs are interconnected with the OMODE_xx outputs of the MOD_x block in the redundant module.
· The MOD_INF1 input structure is interconnected with the MOD_INF output structure of the MOD_x block in the primary module.
· The MOD_INF2 input structure is interconnected with the MOD_INF output structure of the MOD_x block in the redundant module.
· The ACTIV_H and ACTIV_L inputs are interconnected with the outputs of the same name of the RED block in the redundant module.
· The OMODE_xx outputs are interconnected with the relevant channel blocks.
· The OUT structure CPU_DIAG of the OB_BEGIN block is interconnected with the IN_OUT structures of the same name of the OR_32_PN block.
· The RACKF1 and RACKF2 inputs are interconnected with the QRACKF1 and QRACKF2 outputs of MOD_xx.
· The CH_INF_H and CH_INF_L inputs are interconnected with the outputs of the same name of the RED block.
324
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.58 OR_32_PN: QUALITY of 2 redundant Module (<= 32 Channels)
· The output parameter of DXCHG_xx is interconnected with the following channel block at the DataXchg parameter.
· The output parameter of O_MS is interconnected with the following channel block at the MS parameter.
Startup characteristics The OMODE_xx outputs are updated when the "Startup" bit is set.
Error handling The plausibility of input parameters is not checked.
Redundancy
The Redundancy of the modules in an Redundant-System is monitored in the higher-level RED block.
6.58.2
I/Os of OR_32_PN
The factory setting of the block display in the CFC is identified in the "I/O" column:
I/O name bold = I/O visible, I/O name normal = I/O not visible.
You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15)".
Input parameters
I/O (parameter) ACTIV_L ACTIV_H RACKF1 RACKF2 CH_INF_L CH_INF_H RED_STAT MOD_STAT MOD_STAT_PN CHAN_NUM MODE1_xx MODE2_xx MS
Meaning
Data type Default
1=Low module active
BOOL
0
1=High module active
BOOL
0
1=Rack 1 failure
BOOL
0
1=Rack 2 failure
BOOL
0
Low address: 1 = Channel x active
DWORD
0
High address: 1 = Channel x active
DWORD
0
Return value of RED_STATUS
INT
0
Reserve
WORD
0
MODUL_STATUS of PN RED_STATUS
DWORD
0
Total number of channels -1
INT
7
Module 1 mode channel xx (xx = 00 - 31) DWORD
0
Module 2 mode channel xx (xx = 00 - 31) DWORD
0
Maintenance State
DWORD
0
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
325
Family: @System 6.58 OR_32_PN: QUALITY of 2 redundant Module (<= 32 Channels)
I/O (parameter)
RED_LIB_PCS7
FEATURE
Meaning
Reserve Reserve
Data type Default
BOOL
0
DWORD
0
In/Out parameters
I/O (parameter) CPU_DIAG MOD_INF1 MOD_INF2 DXCHG1_xx
DXCHG11_xx
DXCHG2_xx
DXCHG21_xx
MS_XCHG1_xx MS_XCHG2_xx DEPASS_RED_PCS7
Meaning
Data type Default
STRUCT
Module 1 information structure
STRUCT
Module 2 information structure
STRUCT
Bidirectional data exchange channel xx (xx DWORD
0
= 00 - 31)
Bidirectional data exchange channel xx (xx DWORD
0
= 00 - 31)
Bidirectional data exchange channel xx (xx DWORD
0
= 00 - 31)
Bidirectional data exchange channel xx (xx DWORD
0
= 00 - 31)
MS exchange channel xx (xx = 00 - 31) DWORD
0
MS exchange channel xx (xx = 00 - 31) DWORD
0
1=Depassivation
BOOL
0
Out parameters
I/O (parameter) QERR QMODF1 QMODF2 QDISCREP CH_ALM CH_WRN O_MS CH_EXIST CH_ACTIVE CH_OK EXT_STAT EXT_STAT_A OMODE_xx DXCHG_xx
DXCHG_1_xx
Meaning
Data type Default
1=Runtime error
BOOL
1
1=Module 1 pulled / out of order
BOOL
0
1=Module 2 pulled / out of order
BOOL
0
1=Module discrepancy
BOOL
0
Channel Failure of redundancy pair
DWORD
0
Channel Redundancy loss
DWORD
0
Maintenance State
DWORD
0
Channel exist
DWORD
0
Channel active
DWORD
0
Channel OK
DWORD
0
Maintenance release Extended status
DWORD
0
Extended status application
DWORD
0
Mode channel xx (xx = 00 - 31)
DWORD
0
Bidirectional data exchange channel xx (xx DWORD
0
= 00 - 31)
Bidirectional data exchange channel xx (xx DWORD
0
= 00 - 31)
326
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.59 OR_32_TS: OR value status of two redundant time-stamped signal modules, max. 32 channels
I/O (parameter)
MS_XCHG_xx RETURN_VAL EXT_INFO
Meaning
MS exchange channel xx (xx = 00 - 31) Return value of FC451 Extension information of FC451
Data type Default
DWORD
0
INT
0
INT
0
6.59
OR_32_TS: OR value status of two redundant time-stamped signal modules, max. 32 channels
6.59.1
Description of OR_32_TS
Object name (type + number) FB 138 · OR_32_TS block I/Os (Page 328)
Area of application
The OR_32_TS block forms the resulting time stamp from two redundant time-stamped signal modules.
Calling OBs
The block must be installed in OB 1.
Use in CFC
The following actions are executed automatically with the "Generate module drivers" CFC function: · The OR_32_TS block is installed in OB 1. · The TS1_xx inputs are interconnected with the TS_xx output of IMDRV_TS that is
responsible for the signal module with the lower address. · The TS2_xx inputs are interconnected with the TS_xx output of IMDRV_TS that is
responsible for the signal module with the higher address. · The TS_xx outputs are interconnected with the inputs of the MSG_TS channel blocks or
Pcs7InIT.
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
327
Family: @System 6.59 OR_32_TS: OR value status of two redundant time-stamped signal modules, max. 32 channels
Function and method of operation The OR_32_TS block forwards the time stamps of the channels of two redundant signal modules to the MSG_TS channel blocks or Pcs7InIT and acts like an OR function. · If both channels are active, the time stamp of the signal module with the lower address is always used. · If one channel is passivated, the time stamp of the redundant channel is forwarded. · If both channels are passivated, the time stamp of the signal module with the lower address is entered.
Redundancy
Redundancy of the modules in an H system is monitored in the higher-level RED_STATUS block.
Error handling The plausibility of input parameters is not checked.
Startup characteristics Not available
Message response Not available
Operator control and monitoring Not available
Additional information You will find more information in Description of IMDRV_TS (Page 94)
6.59.2
I/Os of OR_32_TS
The factory setting of the block display in CFC is identified in the "I/O" column:
I/O name bold = I/O visible, I/O name normal = I/O not visible.
You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15)".
328
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.59 OR_32_TS: OR value status of two redundant time-stamped signal modules, max. 32 channels
Input parameters
I/O (parameter) CH_INF_H CH_INF_L RED RED_STAT TS1_xx
TS2_xx
TS1_C_xx TS2_C_xx
Meaning
Type
Status of the channels of the 2nd module; info on a chan- DWORD nel-specific basis
0 = passivated, 1 = operational
Status of the channels of the 1st module; info on a channel- DWORD specific basis
0 = passivated, 1 = operational
1 = with redundant time stamp
BOOL
Return value from RED_STATUS
INT
Time stamp (xx = 00 - 31) from the module with the lower STRUCT address
Byte 0:
Bit 0: Message signal state (MsgSig)
Bit 1: Edge change information (TriInf)
Bit 2: Handshake (HdSh)
Byte 1:
Quality code of the time stamp (ST)
DWORD TS0:
Date/time stamp in ISP format (seconds)
DWORD TS1:
Date/time stamp in ISP format (fractions of seconds)
Time stamp (xx = 00 - 31) from the module with the higher STRUCT address
Byte 0:
Bit 0: Message signal state (MsgSig)
Bit 1: Edge change information (TriInf)
Bit 2: Handshake (HdSh)
Byte 1:
Quality code of the time stamp (ST)
DWORD TS0:
Date/time stamp in ISP format (seconds)
DWORD TS1:
Date/time stamp in ISP format (fractions of seconds)
TS communication (xx = 00 - 31) from the module with the BYTE lower address
Bit 0: Acknowledgment of transfer (HS)
Bit 1: Interconnection check (LI)
TS communication (xx = 00 - 31) from the module with the BYTE higher address
Bit 0: Acknowledgment of transfer (HS)
Bit 1: Interconnection check (LI)
Default 0 0 0 0
0 0
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
329
Family: @System 6.60 OR_32TPN: Time stamps of 2 redundant module (1..32 Channels)
Output parameters
I/O (parameter) CH_ALM CH_WRN QERR TS_xx
TS_C_xx
Meaning
Channel failure Redundant pair Channel redundancy loss 1 = program error (module status not available) Time stamp (xx = 00 - 31) Byte 0: Bit 0: Message signal state (MsgSig) Bit 1: Edge change information (TriInf) Bit 2: Handshake (HdSh) Byte 1: Quality code of the time stamp (ST) DWORD TS0: Date/time stamp in ISP format (seconds) DWORD TS1: Date/time stamp in ISP format (fractions of seconds) TS communication (xx = 00 - 31) Bit 0: Acknowledgment of transfer (HS) Bit 1: Interconnection check (LI)
Type DWORD DWORD BOOL STRUCT
BYTE
Additional information For additional information, refer to the following sections: · Maintenance status MS (Page 533)
Default 0 0 1
0
6.60
OR_32TPN: Time stamps of 2 redundant module (1..32 Channels)
6.60.1
Description of OR_32TPN
Object name (type + number) FB 431 · I/Os of OR_32TPN (Page 331)
330
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.60 OR_32TPN: Time stamps of 2 redundant module (1..32 Channels)
Area of application The OR_32TPN block forms the resulting time stamp from two redundant time-stamped signal modules.
Configuration
The following actions are executed automatically with the "Generate module drivers" CFC function:
· The OR_32TPN block is installed in OB 1.
· The TS1_xx inputs are interconnected with the TS_xx output of IM_TS_PN that is responsible for the signal module with the lower address.
· The TS2_xx inputs are interconnected with the TS_xx output of IM_TS_PN that is responsible for the signal module with the higher address.
· The TS_xx outputs are interconnected with the inputs of the Pcs7DiIT.
Error handling The plausibility of input parameters is not checked.
Block functions
The OR_32TPN block forwards the time stamps of the channels of two redundant signal modules to the Pcs7DiIT and acts like an OR function.
· If both channels are active, the time stamp of the signal module with the lower address is always used.
· If one channel is passivated, the time stamp of the redundant channel is forwarded.
· If both channels are passivated, the time stamp of the signal module with the lower address is entered.
Redundancy
Redundancy of the modules in an H system is monitored in the higher-level RED_x block.
6.60.2
I/Os of OR_32TPN
The factory setting of the block display in the CFC is identified in the "I/O" column:
I/O name bold = I/O visible, I/O name normal = I/O not visible.
You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15)".
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
331
Family: @System 6.60 OR_32TPN: Time stamps of 2 redundant module (1..32 Channels)
Input parameters
I/O (parameter) EN CH_INF_Mas CH_INF_Slv RED RED_STAT TS1_xx
TS2_xx
TS1_C_xx TS2_C_xx
Meaning
Enable the block
Status of the channels of the master module; in- formation channel by channel 0 = passivated, 1 = operational
Status of the channels of the slave module; infor- mation channel by channel 0 = passivated, 1 = operational
1 = with redundant time stamp
Return value from RED_STATUS
Time stamp (xx = 00 - 31) from the module with the lower address Byte 0: Bit 0: Message signal state (MsgSig) Bit 1: Edge change information (TriInf) Bit 2: Handshake (HdSh) Byte 1: Quality code of the time stamp (ST) DWORD TS0: Date/time stamp in ISP format (sec- onds) DWORD TS1: Date/time stamp in ISP format (frac- tions of seconds)
Time stamp (xx = 00 - 31) from the module with the higher address Byte 0: Bit 0: Message signal state (MsgSig) Bit 1: Edge change information (TriInf) Bit 2: Handshake (HdSh) Byte 1: Quality code of the time stamp (ST) DWORD TS0: Date/time stamp in ISP format (sec- onds) DWORD TS1: Date/time stamp in ISP format (frac- tions of seconds)
TS communication (xx = 00 - 31) from the module with the lower address Bit 0: Acknowledgment of transfer (HS) Bit 1: Interconnection check (LI)
TS communication (xx = 00 - 31) from the module with the higher address Bit 0: Acknowledgment of transfer (HS) Bit 1: Interconnection check (LI)
Data type BOOL DWORD DWORD BOOL INT STRUCT
STRUCT
BYTE BYTE
Default 1 0 0 0 0
0 0
332
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Output parameters
I/O (parameter) CH_ALM CH_WRN QERR TS_xx
TS_C_xx
Family: @System 6.61 OR_8_PN: Quality of 2 redundant modules (<=8 Channels)
Meaning
Data type
Channel failure Redundant pair
DWORD
Channel redundancy loss
DWORD
1 = program error (module status not available) BOOL
Time stamp (xx = 00 - 31)
STRUCT
Byte 0:
Bit 0: Message signal state (MsgSig)
Bit 1: Edge change information (TriInf)
Bit 2: Handshake (HdSh)
Byte 1: Quality code of the time stamp (ST)
DWORD TS0: Date/time stamp in ISP format (sec- onds)
DWORD TS1: Date/time stamp in ISP format (frac- tions of seconds)
TS communication (xx = 00 - 31)
BYTE
Bit 0: Acknowledgment of transfer (HS)
Bit 1: Interconnection check (LI)
Default 0 0 1
0
In/out parameters
I/O (parameter) TS1_C_xx
TS2_C_xx
Meaning
TS communication (xx = 00 - 31) Bit 0: Acknowledgment of transfer (HS) Bit 1: Interconnection check (LI) TS communication (xx = 00 - 31) Bit 0: Acknowledgment of transfer (HS) Bit 1: Interconnection check (LI)
Data type
BYTE
Default 0
BYTE
0
6.61
OR_8_PN: Quality of 2 redundant modules (<=8 Channels)
6.61.1
Description of OR_8_PN
Object name (type + number) FB 430 · I/Os of OR_8_PN (Page 335)
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
333
Family: @System 6.61 OR_8_PN: Quality of 2 redundant modules (<=8 Channels)
Area of application The OR_8_PN block generates a channel-granular value status from two redundant signal modules.
Calling OBs
OB 1 OB 100
Cyclic program Warm restart
Configuration
The following actions are executed automatically with the "Generate module drivers" CFC function:
· The OR_PN block is installed upstream in the OBs of the channel blocks that are interconnected with it.
· MODE1_x inputs are interconnected with the OMODE_xx outputs of the MOD_x block in the primary module.
· MODE2_x inputs are interconnected with the OMODE_xx outputs of the MOD_x block in the redundant module.
· The MOD_INF1 input structure is interconnected with the MOD_INF output structure of the MOD_x block in the primary module.
· The MOD_INF2 input structure is interconnected with the MOD_INF output structure of the MOD_x block in the redundant module.
· The ACTIV_H and ACTIV_L inputs are interconnected with the outputs of the same name of the RED block in the redundant module.
· The OMODE_xx outputs are interconnected with the relevant channel blocks.
· The OUT structure CPU_DIAG of the OB_BEGIN block is interconnected with the IN_OUT structures of the same name of the OR_8_PN block.
· The RACKF1 and RACKF2 inputs are interconnected with the QRACKF1 and QRACKF2 outputs of MOD_xx.
· The CH_INF_H and CH_INF_L inputs are interconnected with the outputs of the same name of the RED block.
· The output parameter of DXCHG_xx is interconnected with the following channel block at the DataXchg parameter.
· The output parameter of O_MS is interconnected with the following channel block at the MS parameter.
Startup characteristics The OMODE_xx outputs are updated when the "Startup" bit is set.
334
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.61 OR_8_PN: Quality of 2 redundant modules (<=8 Channels)
Error handling The plausibility of input parameters is not checked.
Redundancy
Redundancy of the modules in an H system is monitored in the higher-level RED block.
6.61.2
I/Os of OR_8_PN
The factory setting of the block display in the CFC is identified in the "I/O" column:
I/O name bold = I/O visible, I/O name normal = I/O not visible.
You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15)".
Input parameters
I/O (parameter) ACTIV_L ACTIV_H RACKF1 RACKF2 CH_INF_L CH_INF_H RED_STAT MOD_STAT MOD_STAT_PN CHAN_NUM MODE1_xx MODE2_xx MS RED_LIB_PCS7 FEATURE
Meaning
Data type Default
1=Low module active
BOOL
0
1=High module active
BOOL
0
1=Rack 1 failure
BOOL
0
1=Rack 2 failure
BOOL
0
Low address: 1 = Channel x active
DWORD
0
High address: 1 = Channel x active
DWORD
0
Return value of RED_STATUS
INT
0
Reserve
WORD
0
MODUL_STATUS of PN RED_STATUS
DWORD
0
Total number of channels -1
INT
7
Module 1 mode channel xx (xx = 00 - 07) DWORD
0
Module 2 mode channel xx (xx = 00 - 07) DWORD
0
Maintenance State
DWORD
0
Reserve
BOOL
0
Reserve
DWORD
0
In/Out parameters
I/O (parameter) CPU_DIAG MOD_INF1 MOD_INF2 DXCHG1_xx
Meaning
Data type Default
STRUCT
Module 1 information structure
STRUCT
Module 2 information structure
STRUCT
Bidirectional data exchange channel xx (xx DWORD
0
= 00 - 07)
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
335
Family: @System 6.61 OR_8_PN: Quality of 2 redundant modules (<=8 Channels)
I/O (parameter) DXCHG11_xx
DXCHG2_xx
DXCHG21_xx
MS_XCHG1_xx MS_XCHG2_xx DEPASS_RED_PCS7
Meaning
Data type Default
Bidirectional data exchange channel xx (xx DWORD
0
= 00 - 07)
Bidirectional data exchange channel xx (xx DWORD
0
= 00 - 07)
Bidirectional data exchange channel xx (xx DWORD
0
= 00 - 07)
MS exchange channel xx (xx = 00 - 07) DWORD
0
MS exchange channel xx (xx = 00 - 07) DWORD
0
1=Depassivation
BOOL
0
Out parameters
I/O (parameter) QERR QMODF1 QMODF2 QDISCREP CH_ALM CH_WRN O_MS CH_EXIST CH_ACTIVE CH_OK EXT_STAT EXT_STAT_A OMODE_xx DXCHG_xx
DXCHG_1_xx
MS_XCHG_xx RETURN_VAL EXT_INFO
Meaning
Data type Default
1=Runtime error
BOOL
1
1=Module 1 pulled / out of order
BOOL
0
1=Module 2 pulled / out of order
BOOL
0
1=Module discrepancy
BOOL
0
Channel Failure of redundancy pair
DWORD
0
Channel Redundancy loss
DWORD
0
Maintenance State
DWORD
0
Channel exist
DWORD
0
Channel active
DWORD
0
Channel OK
DWORD
0
Maintenance release Extended status
DWORD
0
Extended status application
DWORD
0
Mode channel xx (xx = 00 - 07)
DWORD
0
Bidirectional data exchange channel xx (xx DWORD
0
= 00 - 07)
Bidirectional data exchange channel xx (xx DWORD
0
= 00 - 07)
MS exchange channel xx (xx = 00 - 07) DWORD
0
Return value of FC451
INT
0
Extension information of FC451
INT
0
336
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
6.62
Family: @System 6.62 OR_H16PN: QUALITY of 2 redundant multi function Modules (<= 16 HART Channels)
OR_H16PN: QUALITY of 2 redundant multi function Modules (<= 16 HART Channels)
6.62.1
Description of OR_H16PN
Object name (type + number) FB 423 · I/Os of OR_H16PN (Page 338)
Area of application
The OR_H16PN block represents the value status from two redundant multi-function signal modules up to 32 IO channels including 16 HART channels. The OR_H16PN block determines the loss of redundancy.
Configuration
The following actions are executed automatically with the "Generate module drivers" CFC function:
· The OR_HA16PN block is installed before its interconnected MOD_HA_PN driver block in its OB.
· MODE1_xx inputs are interconnected with the OMODE_xx outputs of the MOD_x block in the primary module.
· MODE2_xx inputs are interconnected with the OMODE_xx outputs of the MOD_x block in the redundant module.
· The MOD_INF1 input structure is interconnected with the MOD_INF output structure of the MOD_x block in the primary module.
· The MOD_INF2 input structure is interconnected with the MOD_INF output structure of the MOD_x block in the redundant module.
· The ACTIV_H and ACTIV_L inputs are interconnected with the outputs of the same name of the RED block in the redundant module.
· The OMODE_xx outputs are interconnected with the downstream MOD_HA_PN.
· The OUT structure CPU_DIAG_PN of the OB_BEGIN_PN block is interconnected with the IN_OUT structures of the same name of the OR_H16PN block.
· The inputs RACKF1 and RACKF2 are interconnected with the outputs QRACKF1 and QRACKF2 of MOD_x.
· The CH_INF_H and CH_INF_L inputs are interconnected with the outputs of the same name of the RED block.
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
337
Family: @System 6.62 OR_H16PN: QUALITY of 2 redundant multi function Modules (<= 16 HART Channels)
· The output parameter of DXCHG_xx is interconnected with the following channel block at the DataXchg parameter.
· The output parameter of O_MS is interconnected with the following channel block at the MS parameter.
Redundancy
Redundancy of the modules is monitored in a higher-level RED block.
Startup characteristics The OMODE_xx outputs are updated when the "Startup" bit is set.
Error handling The plausibility of input parameters is not checked.
Block functions
The value status of a signal module and of a redundant signal module are disjuncted by the OR_H16PN block. Signal modules or signal channels set to passive mode by the system are regarded as invalid.
When module signals are processed in different OB 3x, in very few cases, a faulty signal value may be processed in one cycle by one of the channel blocks configured to process the module signals following a process-control malfunction affecting the module. This can be avoided by processing all channel blocks of a module inthe OB 3x that also processes the process image partition to which this module is assigned
6.62.2
I/Os of OR_H16PN
The factory setting of the block display in the CFC is identified in the "I/O" column:
I/O name bold = I/O visible, I/O name normal = I/O not visible.
You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15)".
Input parameters
I/O (parameter) ACTIV_L ACTIV_H RACKF1 RACKF2 CH_INF_L
Meaning
1=Low module active 1=High module active 1=Rack 1 failure 1=Rack 2 failure Low address: 1 = Channel x active
Data type Default
BOOL
0
BOOL
0
BOOL
0
BOOL
0
DWORD
0
338
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.62 OR_H16PN: QUALITY of 2 redundant multi function Modules (<= 16 HART Channels)
I/O (parameter)
CH_INF_H CH_INF_L_AUX CH_INF_H_AUX RED_STAT MOD_STAT MOD_STAT_PN CHAN_NUM MODE1_xx MODE2_xx MS RED_LIB_PCS7 FEATURE SUBN1_ID SUBN2_ID
Meaning
Data type Default
High address: 1 = Channel x active
DWORD
0
Low address: 1 = Aux value x active
DWORD
0
High address: 1 = Aux value x active
DWORD
0
Return value of RED_STATUS
INT
0
MODUL_STATUS_WORD of RED_STATUS WORD
0
MODUL_STATUS of PN RED_STATUS
DWORD
0
Total number of channels -1
INT
7
Module 1 mode channel xx (xx = 00 - 31) DWORD
0
Module 2 mode channel xx (xx = 00 - 31) DWORD
0
Maintenance State
DWORD
0
Reserve
BOOL
0
Reserve
DWORD
0
PN-IO System 1 ID (100 115)
BYTE
255
PN-IO System 2 ID (100 115)
BYTE
255
In/Out parameters
I/O (parameter) CPU_DIAG MOD_INF1 MOD_INF2 DXCHG1_xx
DXCHG11_xx
DXCHG2_xx
DXCHG21_xx
MS_XCHG1_xx MS_XCHG2_xx DEPASS_RED_PCS7
Out parameters
I/O (parameter) QERR QMODF1 QMODF2 QDISCREP CH_ALM
Meaning
Data type Default
STRUCT
Module 1 information structure
STRUCT
Module 2 information structure
STRUCT
Bidirectional data exchange channel xx (xx DWORD
0
= 00 - 31)
Bidirectional data exchange channel xx (xx DWORD
0
= 00 - 31)
Bidirectional data exchange channel xx (xx DWORD
0
= 00 - 31)
Bidirectional data exchange channel xx (xx DWORD
0
= 00 - 31)
MS exchange channel xx (xx = 00 - 31) DWORD
0
MS exchange channel xx (xx = 00 - 31) DWORD
0
1=Depassivation
BOOL
0
Meaning
1=Runtime error 1=Module 1 pulled / out of order 1=Module 2 pulled / out of order 1=Module discrepancy Channel Failure of redundancy pair
Data type Default
BOOL
1
BOOL
0
BOOL
0
BOOL
0
DWORD
0
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
339
Family: @System 6.63 OR_HA16C: OR value status of 2 redundant HART modules, max. 16 channels
I/O (parameter) CH_WRN O_MS CH_EXIST CH_ACTIVE CH_OK EXT_STAT EXT_STAT_A OMODE_xx DXCHG_xx
DXCHG_1_xx
MS_XCHG_xx RETURN_VAL EXT_INFO
Meaning
Data type Default
Channel Redundancy loss
DWORD
0
Maintenance State
DWORD
0
Channel exist
DWORD
0
Channel active
DWORD
0
Channel OK
DWORD
0
Maintenance release Extended status
DWORD
0
Extended status application
DWORD
0
Mode channel xx (xx = 00 - 31)
DWORD
0
Bidirectional data exchange channel xx (xx DWORD
0
= 00 - 31)
Bidirectional data exchange channel xx (xx DWORD
0
= 00 - 31)
MS exchange channel xx (xx = 00 - 31) DWORD
0
Return value of FC451
INT
0
Extension information of FC451
INT
0
6.63
OR_HA16C: OR value status of 2 redundant HART modules, max. 16 channels
6.63.1
Description of OR_HA16C
Object name (type + number) FB 133 · OR_HA16C block I/Os (Page 343)
Area of application
The OR_HA16C block is used to create a value status from two redundant signal modules, and reports loss of redundancy for HART modules.
Calling OBs
The block must be installed in OB 100 and in the OB before the MOD_HA driver block that is responsible for the relevant module.
340
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Use in CFC
Family: @System 6.63 OR_HA16C: OR value status of 2 redundant HART modules, max. 16 channels
The following actions are executed automatically with the "Generate module drivers" CFC function:
· The OR_HA16C block is installed before its interconnected MOD_HA driver block in its OB.
· MODE1_xx inputs are interconnected with the OMODE_xx outputs of the MOD_x block in the primary module.
· MODE2_xx inputs are interconnected with the OMODE_xx outputs of the MOD_x block in the redundant module.
· The MOD_INF1 input structure is interconnected with the MOD_INF output structure of the MOD_x block in the primary module.
· The MOD_INF2 input structure is interconnected with the MOD_INF output structure of the MOD_x block in the redundant module.
· The ACTIV_H and ACTIV_L inputs are interconnected with the outputs of the same name of the RED_STATUS block in the redundant module.
· The OMODE_xx outputs are interconnected with the downstream MOD_HA.
· The OUT structure CPU_DIAG of the OB_BEGIN block is interconnected with the IN_OUT structures of the same name of the OR_HA_16C block.
· The inputs RACKF1 and RACKF2 are interconnected with the outputs QRACKF1 and QRACKF2 of MOD_x.
· The CH_INF_H and CH_INF_L inputs are interconnected with the outputs of the same name of the RED_STATUS block.
· The output parameter of DXCHG_xx is interconnected with the following channel block at the DataXchg parameter.
· The output parameter of O_MS is interconnected with the following channel block at the MS parameter.
Function and method of operation
The value status of a signal module and of a redundant signal module are ORed by the OR_HA16C block. Signal modules or signal channels set to passive mode by the system are regarded as invalid. The "At least one channel pair does not match", "Redundancy loss" and "Failure of the redundant I/O" events are reported by ALARM_8P. The message function can be disabled.
When module signals are processed in different OB 3x, in very few cases, a faulty signal value may be processed in one cycle by one of the channel blocks configured to process the module signals following a process-control malfunction affecting the module. This can be avoided by processing all channel blocks of a module in the OB 3x that also processes the process image partition to which this module is assigned.
Depassivation can be triggered for a passivated block or channel by setting the DEPASS input. For this the function RED_DEPA (FC 451) is called internally.
For OR_M_xxC / OR_HA16C blocks:
With channel-granular redundancy, "Loss of redundancy channel x" is reported if one channel fails. If both channels fail, "Redundancy pair failure channel x" is reported.
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
341
Family: @System 6.63 OR_HA16C: OR value status of 2 redundant HART modules, max. 16 channels
With OR_HA16C, the message "Redundancy pair failure HART variable 01" to "Redundancy pair failure HART variable 08" is output for HART signals 01 to 08. The message function can be disabled.
For all OR blocks
Depassivation can be triggered for a passivated block or channel by setting the DEPASS input. For this, the RED_DEPA function (FC 451) is called internally.
Redundancy
Redundancy of the modules is monitored in a higher-level RED_STATUS block (FB 453).
Error handling The plausibility of input parameters is not checked.
Startup characteristics The OMODE_xx outputs are updated when the "Startup" bit is set. ALARM_8P will be initialized.
Time response Not available
Message response
OR_HA16C uses ALARM_8P for reporting. The message function can be disabled by setting EN_MSG = FALSE.
Operator control and monitoring
If asset management is used in the project and the diagnostic screens have been generated, the faceplate can be called via its block icon.
For additional information, refer to the "Process Control System PCS 7; Maintenance Station" manual.
Note: Online help and the manual "PCS 7 FACEPLATES" are only available if the "PCS 7 FACEPLATES" software package is installed.
Additional information For additional information, refer to the sections: Message texts and associated values of OR_HA16C (Page 345) Maintenance status MS (Page 533)
342
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.63 OR_HA16C: OR value status of 2 redundant HART modules, max. 16 channels
You can also find additional information on this in PCS 7 Advanced Process Library > Basics of APL > General functions of the blocks > Operating, monitoring and reporting > Release for maintenance
6.63.2
I/Os of OR_M_8C / OR_M_16C / OR_M_32C / OR_HA16C
The OR_M_8C and OR_M_16C / OR_HA16C / OR_M_32C block I/Os are identical, with the exception of the number of MODE1_xx and MODE2_xx and OMODE_xx.
The factory setting of the block display in the CFC is identified in the "I/O" column: I/O name bold = I/O visible, I/O name normal = I/O not visible.
You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15)".
Input parameters
I/O (parameter) ACTIV_H ACTIV_L CHAN_NUM CH_INF_H
CH_INF_L
DEPASS DEPASS_EN EN_MSG EV_IDx MOD_STAT MODE1_xx
MODE2_xx
MS RACKF1 RACKF2 RED_STAT
Meaning
Data type Default
1 = module with more significant address is active
BOOL
0
1 = module with less significant address is active
BOOL
0
Total number of channels -1
INT
0
Status of the channels of the 2nd module; info on a DWORD 0 channel-specific basis 0 = passivated, 1 = operational
Status of the channels of the 1st module; info on a DWORD 0 channel-specific basis 0 = passivated, 1 = operational
1 = depassivation
BOOL
0
1 = enable depassivation
BOOL
1
1 = Enable message
BOOL
1
Message number (x = 1 3 / 1 5 / 1 - 9 / 1 - 5)
DWORD 0
Module status word from RED_STATUS
WORD
0
Channel mode (xx = 00 07 / 00 15 / 00 - 31) on the DWORD 0 primary module
HART variable mode x (x = 1 - 8) on the primary module
Channel mode (xx = 00 07 / 00 15 / 00 - 31) on the DWORD 0 redundant module
HART variable mode x (x = 1 - 8) on the redundant module
Maintenance status
DWORD 0
1 = error rack 1
BOOL
0
1 = error rack 2
BOOL
0
Value returned by the RED_STATUS block
INT
0
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
343
Family: @System 6.63 OR_HA16C: OR value status of 2 redundant HART modules, max. 16 channels
Output parameters
I/O (parameter) CH_ACTIVE CH_ALM CH_EXIST CH_OK CH_WRN DXCHG_xx DXCHG1_xx EXT_INFO EXT_STAT EXT_STAT_A MS_REQ MS_XCHG_xx
MSG_ACKx
MSG_STATx
O_MS OMODE_xx
QDISCREP QERR
QMODF1 QMODF2 QPASS RETURN_VAL
Meaning
Data type Default
Channel active
DWORD
Channel failure Redundant pair
DWORD
Channel exists
DWORD
Channel OK
DWORD
Channel redundancy loss
DWORD
1st internal data exchange channel for channel block DWORD
2nd internal data exchange channel for channel block DWORD
Supplemental info of RED_OUT
INT
Release for maintenance - extended status
DWORD
Extended status
DWORD
1 = Request maintenance release
BOOL
Maintenance Status - Data exchange channel (xx = 00 DWORD - 63)
Message acknowledgment ALARM_8P_x (x = 1 3 / 1 5 / 1 - 9 / 1 - 5)
WORD
Message error information ALARM_8P_x (x = 1 3 / 1 5 / 1 - 9 / 1 - 5)
WORD
Maintenance status
DWORD
Channel mode (xx = 00 07 / 00 15 / 00 - 31) mode HART variable x (x = 1 - 8)
DWORD
1 = At least one channel pair does not match
BOOL
1 = program error (cannot determine module status)
BOOL
1 = error module 1
BOOL
1 = error module 2
BOOL
1 = at least one module is passivated
BOOL
Error information from RED_OUT
INT
16#00000000 0 0 0 0 0 0 0 0 0 0 0
0
0
0 0
0 1
0 0 0 0
In/out parameters
I/O (parameter) CPU_DIAG DXCHG1_xx
DXCHG11_xx
Meaning
Data type Default
System structure: CPU diagnostics
STRUCT
Bidirectional data exchange channel 1
DWORD 0
xx = 00 to 07 (OR_M8C and OR_HA16C
xx = 00 to 15 (OR_M16C)
xx = 00 to 31 (OR_32C)
Bidirectional data exchange channel 1 (xx = 00 - 07 / 00 DWORD 0 - 15 / 00 - 31 / 00 - 63)
344
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.63 OR_HA16C: OR value status of 2 redundant HART modules, max. 16 channels
I/O (parameter) DXCHG2_xx
DXCHG21_xx MOD_INF1 MOD_INF2 MS_XCHG1_xx MS_XCHG2_xx
Meaning
Bidirectional data exchange channel 2 xx = 00 to 07 (OR_M8C and OR_HA16C xx = 00 to 15 (OR_M16C) xx = 00 to 31 (OR_32C) Bidirectional data exchange channel Module parameters module 1 Module parameters module 2 Maintenance Status - Data exchange channel Maintenance Status - Data exchange channel
Data type Default DWORD 0
DWORD 0 STRUCT STRUCT DWORD 0 DWORD 0
Additional information For additional information, refer to the sections: Maintenance status MS (Page 533) Message texts and associated values of OR_M_8C (Page 364) Message texts and associated values of OR_M_16C (Page 351) Message texts and associated values of OR_HA16C (Page 345) Message texts and associated values of OR_M_32C (Page 356) General Information About Block Description (Page 15)
6.63.3
Message texts and associated values of OR_HA16C
Assignment of message text and message classes You can find more information under Message classes (Page 531)
Message block ALARM_8P
EV_ID1
Message number
1
2
3
4
5 6 8
Default message text
Message class
Module @1%d@/@2%d@/@3%d@: Failure module redundancy pair Module @1%d@/@2%d@/@3%d@: Modules loss of redundancy Module @1%d@/@2%d@/@3%d@: Cannot determine module status Module @1%d@/@2%d@/@3%d@: Discrepancy time has expired for at least one channel pair
...
PLC Process Control Message Failure PLC Process Control Message Error PLC Process Control Message Failure Preventative Maintenance Standard
No message
No message
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
345
Family: @System 6.63 OR_HA16C: OR value status of 2 redundant HART modules, max. 16 channels
Message block ALARM_8P
EV_ID2
Message number
1
2
3
4
5
6
7
8
EV_ID3
1
2
3
4
5
6
7
8
EV_ID4
1
2
3
4
Default message text
Message class
Module @1%d@/@2%d@/@3%d@: Failure redundancy pair channel 00
Module @1%d@/@2%d@/@3%d@: Failure redundancy pair channel 01
Module @1%d@/@2%d@/@3%d@: Failure redundancy pair channel 02
Module @1%d@/@2%d@/@3%d@: Failure redundancy pair channel 03
Module @1%d@/@2%d@/@3%d@: Failure redundancy pair channel 04
Module @1%d@/@2%d@/@3%d@: Failure redundancy pair channel 05
Module @1%d@/@2%d@/@3%d@: Failure redundancy pair channel 06
Module @1%d@/@2%d@/@3%d@: Failure redundancy pair channel 07
Module @1%d@/@2%d@/@3%d@: Failure redundancy pair HART variable 01
Module @1%d@/@2%d@/@3%d@: Failure redundancy pair HART variable 02
Module @1%d@/@2%d@/@3%d@: Failure redundancy pair HART variable 03
Module @1%d@/@2%d@/@3%d@: Failure redundancy pair HART variable 04
Module @1%d@/@2%d@/@3%d@: Failure redundancy pair HART variable 05
Module @1%d@/@2%d@/@3%d@: Failure redundancy pair HART variable 06
Module @1%d@/@2%d@/@3%d@: Failure redundancy pair HART variable 07
Module @1%d@/@2%d@/@3%d@: Failure redundancy pair HART variable 08
Module @1%d@/@2%d@/@3%d@: Redundancy loss channel 00
Module @1%d@/@2%d@/@3%d@: Redundancy loss channel 01
Module @1%d@/@2%d@/@3%d@: Redundancy loss channel 02
Module @1%d@/@2%d@/@3%d@: Redundancy loss channel 03
PLC Process Control Message Failure PLC Process Control Message Failure PLC Process Control Message Failure PLC Process Control Message Failure PLC Process Control Message Failure PLC Process Control Message Failure PLC Process Control Message Failure PLC Process Control Message Failure PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Error PLC Process Control Message Error PLC Process Control Message Error PLC Process Control Message Error
346
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.63 OR_HA16C: OR value status of 2 redundant HART modules, max. 16 channels
Message block ALARM_8P
Message number
5
6
7
8
EV_ID5
1
2
3
4
5
6
7
8
Default message text
Module @1%d@/@2%d@/@3%d@: Redundancy loss channel 04
Module @1%d@/@2%d@/@3%d@: Redundancy loss channel 05
Module @1%d@/@2%d@/@3%d@: Redundancy loss channel 06
Module @1%d@/@2%d@/@3%d@: Redundancy loss channel 07
Module @1%d@/@2%d@/@3%d@: Redundancy loss HART variable 01
Module @1%d@/@2%d@/@3%d@: Redundancy loss HART variable 02
Module @1%d@/@2%d@/@3%d@: Redundancy loss HART variable 03
Module @1%d@/@2%d@/@3%d@: Redundancy loss HART variable 04
Module @1%d@/@2%d@/@3%d@: Redundancy loss HART variable 05
Module @1%d@/@2%d@/@3%d@: Redundancy loss HART variable 06
Module @1%d@/@2%d@/@3%d@: Redundancy loss HART variable 07
Module @1%d@/@2%d@/@3%d@: Redundancy loss HART variable 08
Message class
PLC Process Control Message Error
PLC Process Control Message Error
PLC Process Control Message Error
PLC Process Control Message Error
PLC Process Control Message Error
PLC Process Control Message Error
PLC Process Control Message Error
PLC Process Control Message Error
PLC Process Control Message Error
PLC Process Control Message Error
PLC Process Control Message Error
PLC Process Control Message Error
Assignment of associated values
Message block ALARM_8P
EV_ID1 ... 5
Associ- ated value
1
2
3
Block parameters
SUBN_ID RACK_NO SLOT_NO
Meaning
DP master system ID (byte) Rack/station number (byte) Slot number (byte)
Redundancy loss causes the geographic address of the failed module to be entered dynamically.
If both modules fail, the message text always contains the geographic address of the primary module.
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
347
Family: @System 6.64 OR_M_16C: OR value status of 2 redundant signal modules, max. 16 channels, channel granular
6.64
OR_M_16C: OR value status of 2 redundant signal modules, max. 16 channels, channel granular
6.64.1
Description of OR_M_16C
Object name (type + number) FB 84 · OR_M_16C block I/Os (Page 348) The OR_M_16C block corresponds to OR_M_8C (Page 360), but with 16, rather than 8 channels.
Additional information
For further information, refer to the following sections:
Message texts and associated values of OR_M_16C (Page 351)
Maintenance status MS (Page 533)
You can also find additional information on this in PCS 7 Advanced Process Library > Basics of APL > General functions of the blocks > Operating, monitoring and reporting > Release for maintenance
6.64.2
I/Os of OR_M_8C / OR_M_16C / OR_M_32C / OR_HA16C
The OR_M_8C and OR_M_16C / OR_HA16C / OR_M_32C block I/Os are identical, with the exception of the number of MODE1_xx and MODE2_xx and OMODE_xx.
The factory setting of the block display in the CFC is identified in the "I/O" column: I/O name bold = I/O visible, I/O name normal = I/O not visible.
You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15)".
Input parameters
I/O (parameter) ACTIV_H ACTIV_L CHAN_NUM CH_INF_H
CH_INF_L
Meaning
Data type Default
1 = module with more significant address is active
BOOL
0
1 = module with less significant address is active
BOOL
0
Total number of channels -1
INT
0
Status of the channels of the 2nd module; info on a DWORD 0 channel-specific basis 0 = passivated, 1 = operational
Status of the channels of the 1st module; info on a DWORD 0 channel-specific basis 0 = passivated, 1 = operational
348
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.64 OR_M_16C: OR value status of 2 redundant signal modules, max. 16 channels, channel granular
I/O (parameter) DEPASS DEPASS_EN EN_MSG EV_IDx MOD_STAT MODE1_xx
MODE2_xx
MS RACKF1 RACKF2 RED_STAT
Meaning
Data type Default
1 = depassivation
BOOL
0
1 = enable depassivation
BOOL
1
1 = Enable message
BOOL
1
Message number (x = 1 3 / 1 5 / 1 - 9 / 1 - 5)
DWORD 0
Module status word from RED_STATUS
WORD
0
Channel mode (xx = 00 07 / 00 15 / 00 - 31) on the DWORD 0 primary module
HART variable mode x (x = 1 - 8) on the primary module
Channel mode (xx = 00 07 / 00 15 / 00 - 31) on the DWORD 0 redundant module
HART variable mode x (x = 1 - 8) on the redundant module
Maintenance status
DWORD 0
1 = error rack 1
BOOL
0
1 = error rack 2
BOOL
0
Value returned by the RED_STATUS block
INT
0
Output parameters
I/O (parameter) CH_ACTIVE CH_ALM CH_EXIST CH_OK CH_WRN DXCHG_xx DXCHG1_xx EXT_INFO EXT_STAT EXT_STAT_A MS_REQ MS_XCHG_xx
MSG_ACKx
MSG_STATx
O_MS OMODE_xx
QDISCREP QERR
Meaning
Data type Default
Channel active
DWORD
Channel failure Redundant pair
DWORD
Channel exists
DWORD
Channel OK
DWORD
Channel redundancy loss
DWORD
1st internal data exchange channel for channel block DWORD
2nd internal data exchange channel for channel block DWORD
Supplemental info of RED_OUT
INT
Release for maintenance - extended status
DWORD
Extended status
DWORD
1 = Request maintenance release
BOOL
Maintenance Status - Data exchange channel (xx = 00 DWORD - 63)
Message acknowledgment ALARM_8P_x (x = 1 3 / 1 5 / 1 - 9 / 1 - 5)
WORD
Message error information ALARM_8P_x (x = 1 3 / 1 5 / 1 - 9 / 1 - 5)
WORD
Maintenance status
DWORD
Channel mode (xx = 00 07 / 00 15 / 00 - 31) mode HART variable x (x = 1 - 8)
DWORD
1 = At least one channel pair does not match
BOOL
1 = program error (cannot determine module status)
BOOL
16#00000000 0 0 0 0 0 0 0 0 0 0 0
0
0
0 0
0 1
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
349
Family: @System 6.64 OR_M_16C: OR value status of 2 redundant signal modules, max. 16 channels, channel granular
I/O (parameter)
QMODF1 QMODF2 QPASS RETURN_VAL
Meaning
1 = error module 1 1 = error module 2 1 = at least one module is passivated Error information from RED_OUT
Data type Default
BOOL
0
BOOL
0
BOOL
0
INT
0
In/out parameters
I/O (parameter) CPU_DIAG DXCHG1_xx
DXCHG11_xx DXCHG2_xx
DXCHG21_xx MOD_INF1 MOD_INF2 MS_XCHG1_xx MS_XCHG2_xx
Meaning
Data type Default
System structure: CPU diagnostics
STRUCT
Bidirectional data exchange channel 1
DWORD 0
xx = 00 to 07 (OR_M8C and OR_HA16C
xx = 00 to 15 (OR_M16C)
xx = 00 to 31 (OR_32C)
Bidirectional data exchange channel 1 (xx = 00 - 07 / 00 DWORD 0 - 15 / 00 - 31 / 00 - 63)
Bidirectional data exchange channel 2
DWORD 0
xx = 00 to 07 (OR_M8C and OR_HA16C
xx = 00 to 15 (OR_M16C)
xx = 00 to 31 (OR_32C)
Bidirectional data exchange channel
DWORD 0
Module parameters module 1
STRUCT
Module parameters module 2
STRUCT
Maintenance Status - Data exchange channel
DWORD 0
Maintenance Status - Data exchange channel
DWORD 0
Additional information For additional information, refer to the sections: Maintenance status MS (Page 533) Message texts and associated values of OR_M_8C (Page 364) Message texts and associated values of OR_M_16C (Page 351) Message texts and associated values of OR_HA16C (Page 345) Message texts and associated values of OR_M_32C (Page 356) General Information About Block Description (Page 15)
350
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.64 OR_M_16C: OR value status of 2 redundant signal modules, max. 16 channels, channel granular
6.64.3
Message texts and associated values of OR_M_16C
Assignment of message text and message class
Message block ALARM_8P
EV_ID1
Message number
1
2
3
4
5
...
8
EV_ID2
1
2
3
4
5
6
7
8
EV_ID3
1
2
3
4
5
6
Default message text
Message class
Module @1%d@/@2%d@/@3%d@: Failure module redundancy pair
Module @1%d@/@2%d@/@3%d@: Modules loss of redundancy
Module @1%d@/@2%d@/@3%d@: Cannot determine module status
Module @1%d@/@2%d@/@3%d@: Discrepancy time has expired for at least one channel pair
...
Module @1%d@/@2%d@/@3%d@: Failure redundancy pair channel 00
Module @1%d@/@2%d@/@3%d@: Failure redundancy pair channel 01
Module @1%d@/@2%d@/@3%d@: Failure redundancy pair channel 02
Module @1%d@/@2%d@/@3%d@: Failure redundancy pair channel 03
Module @1%d@/@2%d@/@3%d@: Failure redundancy pair channel 04
Module @1%d@/@2%d@/@3%d@: Failure redundancy pair channel 05
Module @1%d@/@2%d@/@3%d@: Failure redundancy pair channel 06
Module @1%d@/@2%d@/@3%d@: Failure redundancy pair channel 07
Module @1%d@/@2%d@/@3%d@: Failure redundancy pair channel 08
Module @1%d@/@2%d@/@3%d@: Failure redundancy pair channel 09
Module @1%d@/@2%d@/@3%d@: Failure redundancy pair channel 10
Module @1%d@/@2%d@/@3%d@: Failure redundancy pair channel 11
Module @1%d@/@2%d@/@3%d@: Failure redundancy pair channel 12
Module @1%d@/@2%d@/@3%d@: Failure redundancy pair channel 13
PLC Process Control Message Failure
PLC Process Control Message Error
PLC Process Control Message Failure
Preventative Maintenance Standard
No message
No message
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
351
Family: @System 6.64 OR_M_16C: OR value status of 2 redundant signal modules, max. 16 channels, channel granular
Message block ALARM_8P
Message number
7
8
EV_ID4
1
2
3
4
5
6
7
8
EV_ID5
1
2
3
4
5
6
7
8
Default message text
Module @1%d@/@2%d@/@3%d@: Failure redundancy pair channel 14
Module @1%d@/@2%d@/@3%d@: Failure redundancy pair channel 15
Module @1%d@/@2%d@/@3%d@: Redundancy loss channel 00
Module @1%d@/@2%d@/@3%d@: Redundancy loss channel 01
Module @1%d@/@2%d@/@3%d@: Redundancy loss channel 02
Module @1%d@/@2%d@/@3%d@: Redundancy loss channel 03
Module @1%d@/@2%d@/@3%d@: Redundancy loss channel 04
Module @1%d@/@2%d@/@3%d@: Redundancy loss channel 05
Module @1%d@/@2%d@/@3%d@: Redundancy loss channel 06
Module @1%d@/@2%d@/@3%d@: Redundancy loss channel 07
Module @1%d@/@2%d@/@3%d@: Redundancy loss channel 08
Module @1%d@/@2%d@/@3%d@: Redundancy loss channel 09
Module @1%d@/@2%d@/@3%d@: Redundancy loss channel 10
Module @1%d@/@2%d@/@3%d@: Redundancy loss channel 11
Module @1%d@/@2%d@/@3%d@: Redundancy loss channel 12
Module @1%d@/@2%d@/@3%d@: Redundancy loss channel 13
Module @1%d@/@2%d@/@3%d@: Redundancy loss channel 14
Module @1%d@/@2%d@/@3%d@: Redundancy loss channel 15
Message class
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Error
PLC Process Control Message Error
PLC Process Control Message Error
PLC Process Control Message Error
PLC Process Control Message Error
PLC Process Control Message Error
PLC Process Control Message Error
PLC Process Control Message Error
PLC Process Control Message Error
PLC Process Control Message Error
PLC Process Control Message Error
PLC Process Control Message Error
PLC Process Control Message Error
PLC Process Control Message Error
PLC Process Control Message Error
PLC Process Control Message Error
Assignment of associated values
Message block ALARM_8P
EV_ID1 ... 5
Associ- ated value
1
2
3
Block parameters
SUBN_ID RACK_NO SLOT_NO
Meaning
DP master system ID (byte) Rack/station number (byte) Slot number (byte)
352
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.65 OR_M_32C: OR value status of 2 redundant signal modules, max. 32 channels, channel granular
Redundancy loss causes the geographic address of the failed module to be entered dynamically. If both modules fail, the message text always contains the geographic address of the primary module.
See also
Message Classes (Page 531)
6.65
OR_M_32C: OR value status of 2 redundant signal modules, max. 32 channels, channel granular
6.65.1
Description of OR_M_32C
Object name (type + number) FB85
· OR_M_32C block I/Os (Page 353)
Block OR_M_32C corresponds to the OR_M_8C (Page 360) block, but with 32 channels instead of 8.
Additional information
You will find more information in:
Message texts and associated values of OR_M_32C (Page 356)
Maintenance status MS (Page 533)
You can also find additional information on this in PCS 7 Advanced Process Library > Basics of APL > General functions of the blocks > Operating, monitoring and reporting > Release for maintenance
6.65.2
I/Os of OR_M_8C / OR_M_16C / OR_M_32C / OR_HA16C
The OR_M_8C and OR_M_16C / OR_HA16C / OR_M_32C block I/Os are identical, with the exception of the number of MODE1_xx and MODE2_xx and OMODE_xx.
The factory setting of the block display in the CFC is identified in the "I/O" column: I/O name bold = I/O visible, I/O name normal = I/O not visible.
You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15)".
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
353
Family: @System 6.65 OR_M_32C: OR value status of 2 redundant signal modules, max. 32 channels, channel granular
Input parameters
I/O (parameter) ACTIV_H ACTIV_L CHAN_NUM CH_INF_H
CH_INF_L
DEPASS DEPASS_EN EN_MSG EV_IDx MOD_STAT MODE1_xx
MODE2_xx
MS RACKF1 RACKF2 RED_STAT
Meaning
Data type Default
1 = module with more significant address is active
BOOL
0
1 = module with less significant address is active
BOOL
0
Total number of channels -1
INT
0
Status of the channels of the 2nd module; info on a DWORD 0 channel-specific basis 0 = passivated, 1 = operational
Status of the channels of the 1st module; info on a DWORD 0 channel-specific basis 0 = passivated, 1 = operational
1 = depassivation
BOOL
0
1 = enable depassivation
BOOL
1
1 = Enable message
BOOL
1
Message number (x = 1 3 / 1 5 / 1 - 9 / 1 - 5)
DWORD 0
Module status word from RED_STATUS
WORD
0
Channel mode (xx = 00 07 / 00 15 / 00 - 31) on the DWORD 0 primary module
HART variable mode x (x = 1 - 8) on the primary module
Channel mode (xx = 00 07 / 00 15 / 00 - 31) on the DWORD 0 redundant module
HART variable mode x (x = 1 - 8) on the redundant module
Maintenance status
DWORD 0
1 = error rack 1
BOOL
0
1 = error rack 2
BOOL
0
Value returned by the RED_STATUS block
INT
0
Output parameters
I/O (parameter) CH_ACTIVE CH_ALM CH_EXIST CH_OK CH_WRN DXCHG_xx DXCHG1_xx EXT_INFO EXT_STAT EXT_STAT_A MS_REQ
Meaning
Data type Default
Channel active
DWORD
Channel failure Redundant pair
DWORD
Channel exists
DWORD
Channel OK
DWORD
Channel redundancy loss
DWORD
1st internal data exchange channel for channel block DWORD
2nd internal data exchange channel for channel block DWORD
Supplemental info of RED_OUT
INT
Release for maintenance - extended status
DWORD
Extended status
DWORD
1 = Request maintenance release
BOOL
16#00000000 0 0 0 0 0 0 0 0 0 0
354
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.65 OR_M_32C: OR value status of 2 redundant signal modules, max. 32 channels, channel granular
I/O (parameter) MS_XCHG_xx
MSG_ACKx
MSG_STATx
O_MS OMODE_xx
QDISCREP QERR
QMODF1 QMODF2 QPASS RETURN_VAL
Meaning
Data type Default
Maintenance Status - Data exchange channel (xx = 00 DWORD 0 - 63)
Message acknowledgment ALARM_8P_x (x = 1 3 / 1 5 / 1 - 9 / 1 - 5)
WORD
0
Message error information ALARM_8P_x (x = 1 3 / 1 5 / 1 - 9 / 1 - 5)
WORD
0
Maintenance status
DWORD 0
Channel mode (xx = 00 07 / 00 15 / 00 - 31) mode HART variable x (x = 1 - 8)
DWORD 0
1 = At least one channel pair does not match
BOOL
0
1 = program error (cannot determine module status)
BOOL
1
1 = error module 1
BOOL
0
1 = error module 2
BOOL
0
1 = at least one module is passivated
BOOL
0
Error information from RED_OUT
INT
0
In/out parameters
I/O (parameter) CPU_DIAG DXCHG1_xx
DXCHG11_xx DXCHG2_xx
DXCHG21_xx MOD_INF1 MOD_INF2 MS_XCHG1_xx MS_XCHG2_xx
Meaning
Data type Default
System structure: CPU diagnostics
STRUCT
Bidirectional data exchange channel 1
DWORD 0
xx = 00 to 07 (OR_M8C and OR_HA16C
xx = 00 to 15 (OR_M16C)
xx = 00 to 31 (OR_32C)
Bidirectional data exchange channel 1 (xx = 00 - 07 / 00 DWORD 0 - 15 / 00 - 31 / 00 - 63)
Bidirectional data exchange channel 2
DWORD 0
xx = 00 to 07 (OR_M8C and OR_HA16C
xx = 00 to 15 (OR_M16C)
xx = 00 to 31 (OR_32C)
Bidirectional data exchange channel
DWORD 0
Module parameters module 1
STRUCT
Module parameters module 2
STRUCT
Maintenance Status - Data exchange channel
DWORD 0
Maintenance Status - Data exchange channel
DWORD 0
Additional information For additional information, refer to the sections: Maintenance status MS (Page 533) Message texts and associated values of OR_M_8C (Page 364)
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
355
Family: @System 6.65 OR_M_32C: OR value status of 2 redundant signal modules, max. 32 channels, channel granular
Message texts and associated values of OR_M_16C (Page 351) Message texts and associated values of OR_HA16C (Page 345) Message texts and associated values of OR_M_32C (Page 356) General Information About Block Description (Page 15)
6.65.3
Message texts and associated values of OR_M_32C
Assignment of message text and message class
Message block ALARM_8P
EV_ID1
Message number
1
2
3
4
5
...
8
EV_ID2
1
2
3
4
5
6
7
8
EV_ID3
1
2
Default message text
Message class
Module @1%d@/@2%d@/@3%d@: Failure module redundancy pair
Module @1%d@/@2%d@/@3%d@: Modules loss of redundancy
Module @1%d@/@2%d@/@3%d@: Cannot determine module status
Module @1%d@/@2%d@/@3%d@: Discrepancy time has expired for at least one channel pair
...
Module @1%d@/@2%d@/@3%d@: Failure redundancy pair channel 00
Module @1%d@/@2%d@/@3%d@: Failure redundancy pair channel 01
Module @1%d@/@2%d@/@3%d@: Failure redundancy pair channel 02
Module @1%d@/@2%d@/@3%d@: Failure redundancy pair channel 03
Module @1%d@/@2%d@/@3%d@: Failure redundancy pair channel 04
Module @1%d@/@2%d@/@3%d@: Failure redundancy pair channel 05
Module @1%d@/@2%d@/@3%d@: Failure redundancy pair channel 06
Module @1%d@/@2%d@/@3%d@: Failure redundancy pair channel 07
Module @1%d@/@2%d@/@3%d@: Failure redundancy pair channel 08
Module @1%d@/@2%d@/@3%d@: Failure redundancy pair channel 09
PLC Process Control Message Failure
PLC Process Control Message Error
PLC Process Control Message Failure
Preventative Maintenance Standard
No message
No message
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
356
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.65 OR_M_32C: OR value status of 2 redundant signal modules, max. 32 channels, channel granular
Message block ALARM_8P
Message number
3
4
5
6
7
8
EV_ID4
1
2
3
4
5
6
7
8
EV_ID5
1
2
3
4
5
6
7
8
EV_ID6
1
Default message text
Module @1%d@/@2%d@/@3%d@: Failure redundancy pair channel 10
Module @1%d@/@2%d@/@3%d@: Failure redundancy pair channel 11
Module @1%d@/@2%d@/@3%d@: Failure redundancy pair channel 12
Module @1%d@/@2%d@/@3%d@: Failure redundancy pair channel 13
Module @1%d@/@2%d@/@3%d@: Failure redundancy pair channel 14
Module @1%d@/@2%d@/@3%d@: Failure redundancy pair channel 15
Module @1%d@/@2%d@/@3%d@: Failure redundancy pair channel 16
Module @1%d@/@2%d@/@3%d@: Failure redundancy pair channel 17
Module @1%d@/@2%d@/@3%d@: Failure redundancy pair channel 18
Module @1%d@/@2%d@/@3%d@: Failure redundancy pair channel 19
Module @1%d@/@2%d@/@3%d@: Failure redundancy pair channel 20
Module @1%d@/@2%d@/@3%d@: Failure redundancy pair channel 21
Module @1%d@/@2%d@/@3%d@: Failure redundancy pair channel 22
Module @1%d@/@2%d@/@3%d@: Failure redundancy pair channel 23
Module @1%d@/@2%d@/@3%d@: Failure redundancy pair channel 24
Module @1%d@/@2%d@/@3%d@: Failure redundancy pair channel 25
Module @1%d@/@2%d@/@3%d@: Failure redundancy pair channel 26
Module @1%d@/@2%d@/@3%d@: Failure redundancy pair channel 27
Module @1%d@/@2%d@/@3%d@: Failure redundancy pair channel 28
Module @1%d@/@2%d@/@3%d@: Failure redundancy pair channel 29
Module @1%d@/@2%d@/@3%d@: Failure redundancy pair channel 30
Module @1%d@/@2%d@/@3%d@: Failure redundancy pair channel 31
Module @1%d@/@2%d@/@3%d@: Redundancy loss channel 00
Message class
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Error
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
357
Family: @System 6.65 OR_M_32C: OR value status of 2 redundant signal modules, max. 32 channels, channel granular
Message block ALARM_8P
Message number
2
3
4
5
6
7
8
EV_ID7
1
2
3
4
5
6
7
8
EV_ID8
1
2
3
4
5
6
7
8
Default message text
Module @1%d@/@2%d@/@3%d@: Redundancy loss channel 01
Module @1%d@/@2%d@/@3%d@: Redundancy loss channel 02
Module @1%d@/@2%d@/@3%d@: Redundancy loss channel 03
Module @1%d@/@2%d@/@3%d@: Redundancy loss channel 04
Module @1%d@/@2%d@/@3%d@: Redundancy loss channel 05
Module @1%d@/@2%d@/@3%d@: Redundancy loss channel 06
Module @1%d@/@2%d@/@3%d@: Redundancy loss channel 07
Module @1%d@/@2%d@/@3%d@: Redundancy loss channel 08
Module @1%d@/@2%d@/@3%d@: Redundancy loss channel 09
Module @1%d@/@2%d@/@3%d@: Redundancy loss channel 10
Module @1%d@/@2%d@/@3%d@: Redundancy loss channel 11
Module @1%d@/@2%d@/@3%d@: Redundancy loss channel 12
Module @1%d@/@2%d@/@3%d@: Redundancy loss channel 13
Module @1%d@/@2%d@/@3%d@: Redundancy loss channel 14
Module @1%d@/@2%d@/@3%d@: Redundancy loss channel 15
Module @1%d@/@2%d@/@3%d@: Redundancy loss channel 16
Module @1%d@/@2%d@/@3%d@: Redundancy loss channel 17
Module @1%d@/@2%d@/@3%d@: Redundancy loss channel 18
Module @1%d@/@2%d@/@3%d@: Redundancy loss channel 19
Module @1%d@/@2%d@/@3%d@: Redundancy loss channel 20
Module @1%d@/@2%d@/@3%d@: Redundancy loss channel 21
Module @1%d@/@2%d@/@3%d@: Redundancy loss channel 22
Module @1%d@/@2%d@/@3%d@: Redundancy loss channel 23
Message class
PLC Process Control Message Error
PLC Process Control Message Error
PLC Process Control Message Error
PLC Process Control Message Error
PLC Process Control Message Error
PLC Process Control Message Error
PLC Process Control Message Error
PLC Process Control Message Error
PLC Process Control Message Error
PLC Process Control Message Error
PLC Process Control Message Error
PLC Process Control Message Error
PLC Process Control Message Error
PLC Process Control Message Error
PLC Process Control Message Error
PLC Process Control Message Error
PLC Process Control Message Error
PLC Process Control Message Error
PLC Process Control Message Error
PLC Process Control Message Error
PLC Process Control Message Error
PLC Process Control Message Error
PLC Process Control Message Error
358
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.65 OR_M_32C: OR value status of 2 redundant signal modules, max. 32 channels, channel granular
Message block ALARM_8P
EV_ID9
Message number
1
2
3
4
5
6
7
8
Default message text
Module @1%d@/@2%d@/@3%d@: Redundancy loss channel 24 Module @1%d@/@2%d@/@3%d@: Redundancy loss channel 25 Module @1%d@/@2%d@/@3%d@: Redundancy loss channel 26 Module @1%d@/@2%d@/@3%d@: Redundancy loss channel 27 Module @1%d@/@2%d@/@3%d@: Redundancy loss channel 28 Module @1%d@/@2%d@/@3%d@: Redundancy loss channel 29 Module @1%d@/@2%d@/@3%d@: Redundancy loss channel 30 Module @1%d@/@2%d@/@3%d@: Redundancy loss channel 31
Message class
PLC Process Control Message Error PLC Process Control Message Error PLC Process Control Message Error PLC Process Control Message Error PLC Process Control Message Error PLC Process Control Message Error PLC Process Control Message Error PLC Process Control Message Error
Assignment of associated values
Message block ALARM_8P
EV_ID1 ... 9
Associ- ated value
1
2
3
Block parameters
SUBN_ID RACK_NO SLOT_NO
Meaning
DP master system ID (byte) Rack/station number (byte) Slot number (byte)
Redundancy loss causes the geographic address of the failed module to be entered dynamically.
If both modules fail, the message text always contains the geographic address of the primary module.
See also
Message Classes (Page 531)
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
359
Family: @System 6.66 OR_M_8C: OR value status of 2 redundant signal modules, max. 8 channels, channel granular
6.66
OR_M_8C: OR value status of 2 redundant signal modules, max. 8 channels, channel granular
6.66.1
Description of OR_M_8C
Object name (type + number) FB 83 · OR_M_8C block I/Os (Page 362)
Area of application
The OR_M_8C block generates a channel-granular value status from two redundant signal modules.
Calling OBs
The block must be installed in OB 100 and in the fastest OB upstream of the CH_x block that is interconnected with OR_M_8C.
Use in CFC
The following actions are executed automatically with the "Generate module drivers" CFC function:
· The OR_M_8C block is installed upstream in the OBs of the CH_x channel blocks that are interconnected with it.
· MODE1_x inputs are interconnected with the OMODE_xx outputs of the MOD_x block in the primary module.
· MODE2_x inputs are interconnected with the OMODE_xx outputs of the MOD_x block in the redundant module.
· The MOD_INF1 input structure is interconnected with the MOD_INF output structure of the MOD_x block in the primary module.
· The MOD_INF2 input structure is interconnected with the MOD_INF output structure of the MOD_x block in the redundant module.
· The ACTIV_H and ACTIV_L inputs are interconnected with the outputs of the same name of the RED_STATUS block in the redundant module.
· The OMODE_xx outputs are interconnected with the relevant CH_x channel blocks.
· The OUT structure CPU_DIAG of the OB_BEGIN block is interconnected with the IN_OUT structures of the same name of the OR_M_8C block.
· The RACKF1 and RACKF2 inputs are interconnected with the QRACKF1 and QRACKF2 outputs of MOD_xx.
360
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.66 OR_M_8C: OR value status of 2 redundant signal modules, max. 8 channels, channel granular
· The CH_INF_H and CH_INF_L inputs are interconnected with the outputs of the same name of the RED_STATUS block.
· The output parameter of DXCHG_xx is interconnected with the following channel block at the DataXchg parameter.
· The output parameter of O_MS is interconnected with the following channel block at the MS parameter.
Function and method of operation
The value statuses of a signal module and of a redundant signal module are ORed by the OR_M_8C block. Signal modules or signal channels set to passive mode by the system are regarded as invalid. For redundant digital input modules, when a signal discrepancy occurs, no module or channel is set to passive after the discrepancy time has elapsed. The module or channel whose signal does not change is then set to passive. The "At least one channel pair does not match", "Redundancy loss" and "Failure of the redundant I/O" events are reported by ALARM_8P. The message function can be disabled.
Note: When module signals are processed in different OB 3x, in very few cases, a faulty signal value may be processed in one cycle by one of the channel blocks configured to process the module signals following a process-control malfunction affecting the module. This can be avoided by processing all channel blocks of a module in the OB 3x that also processes the process image partition to which this module is assigned.
For OR_M_Cxx blocks:
With channel-granular redundancy, "Loss of redundancy channel x" is reported if one channel fails. If both channels fail, "Redundancy pair failure channel x" is reported. The message function can be disabled.
For all OR blocks:
Depassivation can be triggered for a passivated block or channel by setting the DEPASS input. This is done by calling the RED_DEPA FC451 function internally.
Redundancy
Redundancy of the modules in an H system is monitored in the higher-level RED_STATUS block.
Error handling The plausibility of input parameters is not checked.
Startup characteristics The OMODE_xx (Page 527) outputs are updated when the "Startup" bit is set. ALARM_8P will be initialized.
Message response
OR_M_8C uses ALARM_8P for reporting. The message function can be disabled by setting EN_MSG = FALSE.
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
361
Family: @System 6.66 OR_M_8C: OR value status of 2 redundant signal modules, max. 8 channels, channel granular
Operator control and monitoring If asset management is used in the project and the diagnostic screens have been generated, the faceplate can be called via its block icon. For additional information, refer to the "Process Control System PCS 7; Maintenance Station" manual.
Additional information For additional information, refer to the sections: Message texts and associated values of OR_M_8C (Page 364) Maintenance status MS (Page 533) You can also find additional information on this in PCS 7 Advanced Process Library > Basics of APL > General functions of the blocks > Operating, monitoring and reporting > Release for maintenance
6.66.2
I/Os of OR_M_8C / OR_M_16C / OR_M_32C / OR_HA16C
The OR_M_8C and OR_M_16C / OR_HA16C / OR_M_32C block I/Os are identical, with the exception of the number of MODE1_xx and MODE2_xx and OMODE_xx.
The factory setting of the block display in the CFC is identified in the "I/O" column: I/O name bold = I/O visible, I/O name normal = I/O not visible.
You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15)".
Input parameters
I/O (parameter) ACTIV_H ACTIV_L CHAN_NUM CH_INF_H
CH_INF_L
DEPASS DEPASS_EN EN_MSG EV_IDx MOD_STAT
Meaning
Data type Default
1 = module with more significant address is active
BOOL
0
1 = module with less significant address is active
BOOL
0
Total number of channels -1
INT
0
Status of the channels of the 2nd module; info on a DWORD 0 channel-specific basis 0 = passivated, 1 = operational
Status of the channels of the 1st module; info on a DWORD 0 channel-specific basis 0 = passivated, 1 = operational
1 = depassivation
BOOL
0
1 = enable depassivation
BOOL
1
1 = Enable message
BOOL
1
Message number (x = 1 3 / 1 5 / 1 - 9 / 1 - 5)
DWORD 0
Module status word from RED_STATUS
WORD
0
362
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.66 OR_M_8C: OR value status of 2 redundant signal modules, max. 8 channels, channel granular
I/O (parameter) MODE1_xx
MODE2_xx
MS RACKF1 RACKF2 RED_STAT
Meaning
Data type Default
Channel mode (xx = 00 07 / 00 15 / 00 - 31) on the DWORD 0 primary module
HART variable mode x (x = 1 - 8) on the primary module
Channel mode (xx = 00 07 / 00 15 / 00 - 31) on the DWORD 0 redundant module
HART variable mode x (x = 1 - 8) on the redundant module
Maintenance status
DWORD 0
1 = error rack 1
BOOL
0
1 = error rack 2
BOOL
0
Value returned by the RED_STATUS block
INT
0
Output parameters
I/O (parameter) CH_ACTIVE CH_ALM CH_EXIST CH_OK CH_WRN DXCHG_xx DXCHG1_xx EXT_INFO EXT_STAT EXT_STAT_A MS_REQ MS_XCHG_xx
MSG_ACKx
MSG_STATx
O_MS OMODE_xx
QDISCREP QERR
QMODF1 QMODF2 QPASS RETURN_VAL
Meaning
Data type Default
Channel active
DWORD
Channel failure Redundant pair
DWORD
Channel exists
DWORD
Channel OK
DWORD
Channel redundancy loss
DWORD
1st internal data exchange channel for channel block DWORD
2nd internal data exchange channel for channel block DWORD
Supplemental info of RED_OUT
INT
Release for maintenance - extended status
DWORD
Extended status
DWORD
1 = Request maintenance release
BOOL
Maintenance Status - Data exchange channel (xx = 00 DWORD - 63)
Message acknowledgment ALARM_8P_x (x = 1 3 / 1 5 / 1 - 9 / 1 - 5)
WORD
Message error information ALARM_8P_x (x = 1 3 / 1 5 / 1 - 9 / 1 - 5)
WORD
Maintenance status
DWORD
Channel mode (xx = 00 07 / 00 15 / 00 - 31) mode HART variable x (x = 1 - 8)
DWORD
1 = At least one channel pair does not match
BOOL
1 = program error (cannot determine module status)
BOOL
1 = error module 1
BOOL
1 = error module 2
BOOL
1 = at least one module is passivated
BOOL
Error information from RED_OUT
INT
16#00000000 0 0 0 0 0 0 0 0 0 0 0
0
0
0 0
0 1
0 0 0 0
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
363
Family: @System 6.66 OR_M_8C: OR value status of 2 redundant signal modules, max. 8 channels, channel granular
In/out parameters
I/O (parameter) CPU_DIAG DXCHG1_xx
DXCHG11_xx DXCHG2_xx
DXCHG21_xx MOD_INF1 MOD_INF2 MS_XCHG1_xx MS_XCHG2_xx
Meaning
Data type Default
System structure: CPU diagnostics
STRUCT
Bidirectional data exchange channel 1
DWORD 0
xx = 00 to 07 (OR_M8C and OR_HA16C
xx = 00 to 15 (OR_M16C)
xx = 00 to 31 (OR_32C)
Bidirectional data exchange channel 1 (xx = 00 - 07 / 00 DWORD 0 - 15 / 00 - 31 / 00 - 63)
Bidirectional data exchange channel 2
DWORD 0
xx = 00 to 07 (OR_M8C and OR_HA16C
xx = 00 to 15 (OR_M16C)
xx = 00 to 31 (OR_32C)
Bidirectional data exchange channel
DWORD 0
Module parameters module 1
STRUCT
Module parameters module 2
STRUCT
Maintenance Status - Data exchange channel
DWORD 0
Maintenance Status - Data exchange channel
DWORD 0
Additional information For additional information, refer to the sections: Maintenance status MS (Page 533) Message texts and associated values of OR_M_8C (Page 364) Message texts and associated values of OR_M_16C (Page 351) Message texts and associated values of OR_HA16C (Page 345) Message texts and associated values of OR_M_32C (Page 356) General Information About Block Description (Page 15)
6.66.3
Message texts and associated values of OR_M_8C
Assignment of message text and message class
Message block ALARM_8P
EV_ID1
Message number
1
2
Default message text
Module @1%d@/@2%d@/@3%d@: Failure module redundancy pair Module @1%d@/@2%d@/@3%d@: Modules loss of redundancy
Message class
PLC Process Control Message Failure PLC Process Control Message Error
364
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.66 OR_M_8C: OR value status of 2 redundant signal modules, max. 8 channels, channel granular
Message block ALARM_8P
Message number
3
4
5
...
8
EV_ID2
1
2
3
4
5
6
7
8
EV_ID3
1
2
3
4
5
6
7
8
Default message text
Message class
Module @1%d@/@2%d@/@3%d@: Cannot determine module status
Module @1%d@/@2%d@/@3%d@: Discrepancy time has expired for at least one channel pair
...
Module @1%d@/@2%d@/@3%d@: Failure redundancy pair channel 00
Module @1%d@/@2%d@/@3%d@: Failure redundancy pair channel 01
Module @1%d@/@2%d@/@3%d@: Failure redundancy pair channel 02
Module @1%d@/@2%d@/@3%d@: Failure redundancy pair channel 03
Module @1%d@/@2%d@/@3%d@: Failure redundancy pair channel 04
Module @1%d@/@2%d@/@3%d@: Failure redundancy pair channel 05
Module @1%d@/@2%d@/@3%d@: Failure redundancy pair channel 06
Module @1%d@/@2%d@/@3%d@: Failure redundancy pair channel 07
Module @1%d@/@2%d@/@3%d@: Redundancy loss channel 00
Module @1%d@/@2%d@/@3%d@: Redundancy loss channel 01
Module @1%d@/@2%d@/@3%d@: Redundancy loss channel 02
Module @1%d@/@2%d@/@3%d@: Redundancy loss channel 03
Module @1%d@/@2%d@/@3%d@: Redundancy loss channel 04
Module @1%d@/@2%d@/@3%d@: Redundancy loss channel 05
Module @1%d@/@2%d@/@3%d@: Redundancy loss channel 06
Module @1%d@/@2%d@/@3%d@: Redundancy loss channel 07
PLC Process Control Message Failure
Preventative Maintenance Standard
No message
No message
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Failure
PLC Process Control Message Error
PLC Process Control Message Error
PLC Process Control Message Error
PLC Process Control Message Error
PLC Process Control Message Error
PLC Process Control Message Error
PLC Process Control Message Error
PLC Process Control Message Error
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
365
Family: @System 6.67 OR_MHA_CO: Multi HART variable read coordination (0 - 15 Channel) - redundancy
Assignment of associated values
Message block ALARM_8P
EV_ID1 / 2 / 3
Associ- ated value
1
2
3
Block parameters
SUBN_ID RACK_NO SLOT_NO
Meaning
DP master system ID (byte) Rack/station number (byte) Slot number (byte)
Redundancy loss causes the geographic address of the failed module to be entered dynamically.
If both modules fail, the message text always contains the geographic address of the primary module.
See also
Message Classes (Page 531)
6.67
OR_MHA_CO: Multi HART variable read coordination (0 - 15 Channel) - redundancy
6.67.1
Description of OR_MHA_CO
Object name (type + number) FB 427 · I/Os of OR_MHA_CO (Page 367)
Area of application
The block OR_MHA_CO coordinates the two upstream MHA_CO blocks and forwards the value of the MultiHART variables to the Pcs7HaAI / Pcs7HaAO channel blocks for ET 200SP HA HART modules.
Configuration
The following actions are executed automatically with the "Generate module drivers" CFC function:
· The OR_MHA_CO block is installed after its interconnected MHA_CO driver block in its OB.
· MODE1_xx inputs are interconnected with the OMODE_xx outputs of the MOD_x block in the primary module.
· MODE2_xx inputs are interconnected with the OMODE_xx outputs of the MOD_x block in the redundant module.
366
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.67 OR_MHA_CO: Multi HART variable read coordination (0 - 15 Channel) - redundancy
· MULTI_HART_00_xx inputs are interconnected with the MULTI_HART_00_xx outputs of the MHA_CO block in the master module.
· MULTI_HART_00_xx inputs are interconnected with the MULTI_HART_00_xx outputs of the MHA_CO block in the slave module.
· The ACTIV_H and ACTIV_L inputs are interconnected with the outputs of the same name of the RED block in the redundant module.
· The MULTI_HART_00_xx outputs are interconnected with the downstream Pcs7HaAI/ Pcs7HaAO blocks.
· The OUT structure CPU_DIAG_PN of the OB_BEGIN_PN block is interconnected with the IN_OUT structures of the same name of the OR_MHA_CO block.
· The ouputs CH_INF_L_AUX_x (x=0,1) and CH_INF_H_AUX_x (x=0,1) are connected with the inputs of the same name of the OR_HA16PN block in the redundant mode.
Error handling The plausibility of input parameters is not checked.
Messaging
Not available
6.67.2
I/Os of OR_MHA_CO
The factory setting of the block display in the CFC is identified in the "I/O" column:
I/O name bold = I/O visible, I/O name normal = I/O not visible.
You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15)".
Input parameters
I/O (parameter) ACTIV_L ACTIV_H CHAN_NUM RACKF1 RACKF2 FEATURE MODE1_xx MODE2_xx
Meaning
1=Low Module Active 1=High Module Active Total number of channels -1 1=Higher level error 1=Higher level error Reserve Channel mode xx (xx : 00 - 15) Module 1 Channel mode xx (xx : 00 - 15) Module 2
Data type
Bool Bool INT BOOL BOOL DWORD DWORD DWORD
Default
0 0 0 0 0 0 0 0
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
367
Family: @System 6.68 OR_MHA1_CO: Coordinates multiHART variables - redundancy
Output parameters
I/O (parameter)
CH_INF_L_AUX_0 CH_INF_H_AUX_0 CH_INF_L_AUX_1 CH_INF_H_AUX_1 MULTI_HART_xx
Meaning
Low address aux value 0..31: 1 = active High address aux value 0..31: 1 = active Low address aux value 32..63: 1 = active High address aux value 32..63: 1 = active Bidirectional information exchange (xx = 00 15)
Data type
DWORD DWORD DWORD DWORD STRUCT
Default
0 0 0 0 0
In/out parameters
I/O (parameter)
ACC_MODE CPU_DIAG_PN MOD_INF1 MOD_INF2 MULTI_HART_xx_1 MULTI_HART_xx_2
Meaning
1 = Accept new settings System structure: CPU-Diagnose Module 1 information structure Module 2 information structure Multi HART values of Module 1 (xx = 00 15) Multi HART values of Module 2 (xx = 00 15)
Data type
BOOL STRUCT STRUCT STRUCT STRUCT STRUCT
Default 0
6.68
OR_MHA1_CO: Coordinates multiHART variables - redundancy
6.68.1
Description of OR_MHA1_CO
Object name (type + number) FB 440 · I/Os of OR_MHA1_CO (Page 369)
Area of application
The block OR_MHA1_CO coordinates with the two upstream MHA_CO blocks and forwards the value of the MultiHART variables to the Pcs7HaAI / Pcs7HaAO channel blocks for ET 200SP HA HART modules.
368
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.68 OR_MHA1_CO: Coordinates multiHART variables - redundancy
Configuration
The following actions are executed automatically with the "Generate module drivers" CFC function:
· The OR_MHA1_CO block is installed after its interconnected MHA_CO driver block in its OB.
· MODE1_xx inputs are interconnected with the OMODE_xx outputs of the MOD_x block in the primary module.
· MODE2_xx inputs are interconnected with the OMODE_xx outputs of the MOD_x block in the redundant module.
· MULTI_HART_00_xx inputs are interconnected with the MULTI_HART_00_xx outputs of the MHA_CO block in the master module.
· MULTI_HART_00_xx inputs are interconnected with the MULTI_HART_00_xx outputs of the MHA_CO block in the slave module.
· The ACTIV_H and ACTIV_L inputs are interconnected with the outputs of the same name of the RED block in the redundant module.
· The MULTI_HART_00_xx outputs are interconnected with the downstream Pcs7HaAI/ Pcs7HaAO blocks.
· The OUT structure CPU_DIAG_PN of the OB_BEGIN_PN block is interconnected with the IN_OUT structures of the same name of the OR_MHA1_CO block.
· The ouputs CH_INF_L_AUX_0 and CH_INF_H_AUX_0 are connected with the inputs of the same name of the OR_HA16PN block in the redundant mode.
Error handling The plausibility of input parameters is not checked.
Messaging
Not available
6.68.2
I/Os of OR_MHA1_CO
The factory setting of the block display in the CFC is identified in the "I/O" column:
I/O name bold = I/O visible, I/O name normal = I/O not visible.
You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15)".
Input parameters
I/O (parameter) ACTIV_L ACTIV_H
Meaning
1=Low Module Active 1=High Module Active
Data type
Bool
Bool
Default
0 0
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
369
Family: @System 6.69 PADP_L0x: Monitoring DP/PA slaves
I/O (parameter)
CHAN_NUM RACKF1 RACKF2 FEATURE MODE1_xx MODE2_xx
Meaning
Total number of channels -1 1=Higher level error 1=Higher level error Reserve Channel mode xx (xx : 00 - 15) Module 1 Channel mode xx (xx : 00 - 15) Module 2
Data type
INT BOOL BOOL DWORD DWORD DWORD
Default
0 0 0 0 0 0
Output parameters
I/O (parameter)
CH_INF_L_AUX_0
CH_INF_H_AUX_ 0
MULTI_HART_xx
Meaning
Low address aux value 0..31: 1 = active High address aux value 0..31: 1 = active
Bidirectional information exchange (xx = 00 15)
Data type DWORD DWORD
STRUCT
Default
0 0
0
In/out parameters
I/O (parameter)
ACC_MODE CPU_DIAG_PN MOD_INF1 MOD_INF2 MUL- TI_HART_xx_1 MUL- TI_HART_xx_2
Meaning
1 = Accept new settings System structure: CPU-Diagnose Module 1 information structure Module 2 information structure Multi HART values of Module 1 (xx = 00 07)
Multi HART values of Module 2 (xx = 00 07)
Data type
BOOL STRUCT STRUCT STRUCT STRUCT
Default 0
STRUCT
6.69
PADP_L0x: Monitoring DP/PA slaves
6.69.1
Description of PADP_L00
Object name (type + number) FB 109 · PADP_L00 block I/Os (Page 374)
370
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.69 PADP_L0x: Monitoring DP/PA slaves
Area of application
Block PADP_L00 monitors DP/PA field devices operating as DPV0 or DPV1 slaves downstream of a DP/PA or Y-Link that is operated as a DPV0 slave. The PA field devices must conform to the PROFIBUS V3.0 profile. There must be individual blocks available for the diagnostics and signal processing for DP field devices. H systems support only the PA field devices at an active DP/PALink.
Calling OBs
The block must be installed in the run sequence in the following OBs:
OB 1 OB 82 OB 85 OB 86 OB 100
Cyclic program Diagnostic interrupt Program execution error Rack failure Warm restart
Use in CFC
The following actions are executed automatically with the "Generate module drivers" CFC function: · Block PADP_L00 is integrated in the run sequence downstream of block DPAY_V0. · Parameters are assigned to the MODE_xx input (mode of slot xx of a field device). · The PADP_ADR input (DP/PA slave address downstream of the DP/PA link or Y link) is
configured. · The DPA_M input is interconnected with the DPA_M_xx output of the DPAY_V0 block. · The OUT structures CPU_DIAG of the OB_BEGIN block and RAC_DIAG of the DPAY_V0 block
are interconnected with the IN_OUT structures of the same name of PADP_L00. · The QMODF and PA_DIAG outputs are interconnected with the MOD_PAL0 block.
Note The CFC function "Generate module drivers" can only be used if the PA field device belongs to slave family 12.
Function and method of operation
Block PADP_L00 analyzes all events affecting a DP or PA field device and its slots acyclically. It generates the relevant DP_MODE or PA_MODE, depending on the slot, and the value status for the DP or PA signal processing blocks. The permitted PA_MODE (Page 528) is already defined for the PA signal processing blocks. The DP_MODE must be defined individually for the DP field device blocks. ALARM_8P is used to report these events. The message function can be disabled.
The higher-level DPAY_V0 block enables the block to run. The diagnostic event is entered in the start information (CPU_DIAG) of the OB_BEGIN block.
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
371
Family: @System 6.69 PADP_L0x: Monitoring DP/PA slaves
The data is already evaluated by the link block (DPAY_V0) if diagnostics are required. The diagnostic information concerning the PA field device is stored in the DPA_M structure. The structure consists of 2 DWORD (S_01 for module 1 to 16 and S_02 for module 17 to 32), and 1 BOOL (S_ERR = DP/PA field device faulty) variables. Two bits of the DWORD are assigned to each slot of the DP/PA field device, whereby bit 0 and bit 1 belong to slot 1 of the DP/PA field device, etc. Slots 1 to 7 are evaluated. The bit states are defined as follows:
Status Bit 0 0 0 1 1
Status Bit 1 0 1 0 1
Meaning Module x OK (valid user data) Module x error (invalid user data) Wrong module x (invalid user data) No module x (invalid user data)
There is an input (MODE_xx) for each slot (module) on the DP/PA field device that is used to read in configuration settings made for the PA field device slots (module) in HW Config.
For DP field devices, the user must do his own encoding at the MODE input.
The function writes MODE_xx to the low word of the OMODE_xx (Page 527) output parameter. This occurs only during startup or if you set ACC_MODE = TRUE. The current slot value status is written to the most significant byte. If the result is positive, the system sets OMODE_xx = 16#80xxxxxx. The following events are evaluated by block DPAY_V0 and lead to the value status "Invalid value" due to a higher-level error (OMODE_xx = 16#40xxxxxx):
· Rack failure (OB 86)
(Output parameter QRACKF = TRUE)
· Diagnostic interrupt that affects entire field (Output parameter QMODF = TRUE,
device (OB 82)
if DPA_M.S_ERR = TRUE)
· Diagnostic interrupt slot xx that affects a field device (OB 82):
(Output parameter OMODE_xx = Module (slot) error-specific DPA_M)
In the event of a diagnostic interrupt, the block reports field-device-specifically to WinCC by means of ALARM_8P. We distinguish between the field device and its slots; each slot is assigned a message ID.
The "Device failure" message can be disabled with EM_MSG_D = FALSE.
Redundancy
The higher-level block DPAY_V0 evaluates the redundancy of the DP master systems used in an H system.
MODE Setting for PA Profiles You will find additional information in "PA_MODE Settings (Page 528)".
Note If you change the parameter settings for the MODE_xx inputs at runtime, these changes will not be accepted at the outputs until the ACC_MODE is set to 1.
372
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.69 PADP_L0x: Monitoring DP/PA slaves
OMODE Structure You will find additional information in the "OMODE (Page 527)" section.
Error handling The plausibility of input parameters is not checked.
Startup characteristics
After a restart or an initial start, the system verifies that the PA field device is available under its logical base address. A restart (OB100) is reported via the LSB in byte 2 of the OMODE_xx (Page 527) outputs.
Time response Not available
Message response
The block signals field device errors using ALARM_8P, and generates the following messages in the OBs listed below:
OB no. OB 1 OB 82
Start Event Cyclic processing Diagnostic interrupt
OB 100 Restart
Message
Repeat the update of ALARM_8P outputs/messages, if necessary
Device error incoming/outgoing Device module xx error incoming/outgoing Device module xx incorrect incoming/outgoing Device module xx missing incoming/outgoing
Initialization of ALARM_8P
Operator control and monitoring The block has no faceplate.
Additional information For additional information, refer to the sections: Message texts and associated values of PADP_L00 (Page 375)
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
373
Family: @System 6.69 PADP_L0x: Monitoring DP/PA slaves
6.69.2
I/Os of PADP_L00/PADP_L01/PADP_L02
I/Os
The I/Os of the PADP_L00, PADP_L01 and PADP_L02 blocks are identical save for the number of MODE_xx and OMODE_xx. The number of monitored slots determines the number of corresponding I/O parameters.
The default block view in the CFC is identified in the "I/O" column: I/O name in bold = I/O is visible, standard I/O name = I/O is not visible.
You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15)".
Input parameters
I/O (parameter) DPA_M EN_MSG EN_MSG_D EV_ID MODE_xx PADP_ADR
Meaning
DP/PA field device diagnostic information 1 = enable message 1 = enable "Device failure" message Message number Module mode (xx = 00 - 06 / 00 - 15 / 00 - 31) DP/PA field device address
Data type
STRUCT BOOL BOOL DWORD WORD BYTE
De- fault
1 1 0 0 0
Output parameters
I/O (parameter) MSG_ACK MSGSTAT OMODE_xx PA_DIAG QERR QMODF QRACKF
Meaning
Message acknowledgment Message error information Module mode (xx = 00 - 06 / 00 - 15 / 00 - 31) PA field device diagnostic information 1 = program error 1 = module removed/defective 1 = higher-level error
Data type
WORD WORD DWORD DWORD BOOL BOOL BOOL
De- fault
0 0 0 0 1 0 0
In-out parameters
I/O (parameter) ACC_MODE CPU_DIAG RAC_DIAG
Meaning
1 = accept MODE settings CPU diagnostics 1 = DPV1 mode
Data type
BOOL STRUCT STRUCT
De- fault
0
374
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.69 PADP_L0x: Monitoring DP/PA slaves
Additional information For additional information, refer to the following sections: Message texts and associated values of PADP_L00 (Page 375) Message texts and associated values of PADP_L01 (Page 379) Message texts and associated values of PADP_L02 (Page 384)
6.69.3
Message texts and associated values of PADP_L00
Assignment of message text and message class
Mes- sage block ALARM _8P
EV_ID
Mes- Block sage param- number eter
1
QMODF
2
-
3
-
4
-
5
-
6
-
7
-
8
-
Default message text
Message class
Device @1%d@/ @2%d@/@3%d@: Fail- PLC Process Control Message -
ure
Failure
Device @1%d@/ @2%d@/@3%d@: Module 00 @4W%t#PADP_L00_TXT@
PLC Process Control Message Failure
Device @1%d@/ @2%d@/@3%d@: Module 01 @5W%t#PADP_L00_TXT@
PLC Process Control Message Failure
Device @1%d@/ @2%d@/@3%d@: Module 02 @6W%t#PADP_L00_TXT@
PLC Process Control Message Failure
Device @1%d@/ @2%d@/@3%d@: Module 03 @7W%t#PADP_L00_TXT@
PLC Process Control Message Failure
Device @1%d@/ @2%d@/@3%d@: Mod- PLC Process Control Message -
ule 04 @8W%t#PADP_L00_TXT@
Failure
Device @1%d@/ @2%d@/@3%d@: Mod- PLC Process Control Message -
ule 05 @9W%t#PADP_L00_TXT@
Failure
Device @1%d@/ @2%d@/@3%d@:
PLC Process Control Message -
Module 06 @10W%t#PADP_L00_TXT@ Failure
You will find the message texts and their text numbers in the
Text library for PADP_L00 (Page 537)".
Assignment of associated values
Message block Associated
ALARM_8P
value
EV_ID
1
2
3
4 - 10
Block parameter
SUBN_ID RACK_NO PADP_ADR -
Meaning
DP master system ID (byte) Rack/station number (byte) DP/PA device address (byte) Text number (message 2 - 8) from PADP_L00_TXT
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
375
Family: @System 6.69 PADP_L0x: Monitoring DP/PA slaves
If the PA field device is connected downstream from an inactive DP/PA-Link V0and SUBN1_ID = 16#FF, the associated variable is substituted by SUBN2_ID.
See also
Message Classes (Page 531)
6.69.4
Description of PADP_L01
Object name (type + number) FB 110 · PADP_L01 block I/Os (Page 374)
Area of application
The PADP_L01 monitors DP/PA field devices that are used as DPV0 or DPV1 slaves, downstream of a DP/PA or Y link that is used as a DPV0 slave. The PA field devices must conform to the PROFIBUS V3.0 profile. There must be individual blocks available for the diagnostics and signal processing for DP field devices. H systems support only the PA field devices at an active DP/PALink.
Calling OBs
The block must be installed in the run sequence in the following OBs (this is done automatically in the CFC):
OB 1 OB 82 OB 85 OB 86 OB 100
Cyclic program Diagnostic interrupt Program execution error Rack failure Warm restart
Use in CFC
The following actions are executed automatically with the "Generate module drivers" CFC function:
· The PADP_L01 block is integrated in the run sequence downstream of block DPAY_V0.
· Parameters are assigned to the MODE_xx input (mode of slot xx of a field device).
· The PADP_ADR input (DP/PA slave address downstream of the DP/PA link or Y link) is configured.
· The DPA_M input is interconnected with the DPA_M_xx output of the DPAY_V0 block.
376
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.69 PADP_L0x: Monitoring DP/PA slaves
· The OUT structures CPU_DIAG of the OB_BEGIN block and RAC_DIAG of the DPAY_V0 block are interconnected with the IN_OUT structures of the same name of PADP_L01.
· The outputs QMODF and PA_DIAG are interconnected with the MOD_PAL0 block.
Note The CFC function "Generate module drivers" can only be used if the PA field device belongs to slave family 12.
Function and method of operation
Block PADP_L01 analyzes all events affecting a DP or PA field device and its slots acyclically. It generates the relevant DP_MODE or PA_MODE, depending on the slot, and the value status for the DP or PA signal processing blocks. The permitted PA_MODE (Page 528) is already defined for the PA signal processing blocks. The DP_MODE must be defined individually for the DP field device blocks. ALARM_8P is used to report these events. The message function can be disabled.
The higher-level DPAY_V0 block enables the block to run. The diagnostic event is entered in the start information (CPU_DIAG) of the OB_BEGIN block.
The data is already evaluated by the link block (DPAY_V0) if diagnostics are required. The diagnostic information concerning the PA field device is stored in the DPA_M structure. The structure consists of 2 DWORD (S_01 for module 1 to 16 and S_02 for module 17 to 32), and 1 BOOL (S_ERR = DP/PA field device faulty) variables. Two bits of the DWORD are assigned to each slot of the DP/PA field device, whereby bit 0 and bit 1 belong to slot 1 of the DP/PA field device, etc. Slots 1 to 16 are evaluated. The bit states are defined as follows:
Status Bit 0 0 0 1 1
Status Bit 1 0 1 0 1
Meaning Module x OK (valid user data) Module x error (invalid user data) Wrong module x (invalid user data) No module x (invalid user data)
There is an input (MODE_xx (Page 517)) for each slot (module) on the DP/PA field device that is used to read in configuration settings made for the PA field device slots (module) in HW Config.
For DP field devices, the user must do his own encoding at the MODE input.
The function writes MODE_xx to the low word of the OMODE_xx (Page 527) output parameter. This occurs only during startup or if you set ACC_MODE = TRUE. The current slot value status is written to the most significant byte. If the result is positive, the system sets OMODE_xx = 16#80xxxxxx. The following events are evaluated by block DPAY_V0 and lead to the value status "Invalid value" due to a higher-level error (OMODE_xx = 16#40xxxxxx):
· Rack failure (OB 86)
(Output parameter QRACKF = TRUE)
· Diagnostic interrupt that affects entire field (Output parameter QMODF = TRUE,
device (OB 82)
if DPA_M.S_ERR = TRUE)
· Diagnostic interrupt slot xx that affects a field device (OB 82):
(Output parameter OMODE_xx = Module (slot) error-specific DPA_M)
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
377
Family: @System 6.69 PADP_L0x: Monitoring DP/PA slaves
The block reports a diagnostic interrupt to the OS for a specific field device using ALARM_8P. We distinguish between the field device and its slots; each slot is assigned a message ID. The "Device failure" message can be disabled with EM_MSG_D = FALSE.
Redundancy
The higher-level block DPAY_V0 evaluates the redundancy of the DP master systems used in an H system.
MODE setting for PA profiles You will find additional information in "PA_MODE settings (Page 528)".
Note If you change the parameter settings for the MODE_xx inputs at runtime, these changes will not be accepted at the outputs until the ACC_MODE is set to 1.
OMODE structure You will find additional information in the "OMODE (Page 527)" section.
Error handling The plausibility of input parameters is not checked.
Startup characteristics After a restart or an initial start, the system verifies that the PA field device is available under its logical base address. A restart (OB100) is reported via the LSB in byte 2 of the OMODE_xx (Page 527) outputs.
Time response Not available
378
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.69 PADP_L0x: Monitoring DP/PA slaves
Message response
The block signals field device errors using ALARM_8P, and generates the following messages in the OBs listed below:
OB no. OB 1 OB 82
Start Event Cyclic processing Diagnostic interrupt
OB 100 Restart
Message
Repeat the update of ALARM_8P outputs/messages, if necessary
Device error incoming/outgoing Device module xx error incoming/outgoing Device module xx incorrect incoming/outgoing Device module xx missing incoming/outgoing
Initialization of ALARM_8P
Operator control and monitoring The block has no faceplate.
Additional information For additional information, refer to the sections: Message texts and associated values of PADP_L01 (Page 379)
6.69.5
Message texts and associated values of PADP_L01
Assignment of message text and message class
Mes- sage block ALARM _8P EV_ID1
EV_ID2
Mes- Block sage param- number eter
1
QMODF
2
-
3
-
4
-
...
8
-
1
-
...
7
-
8
-
Default message text
Device @1%d@/ @2%d@/@3%d@: Failure Device @1%d@/ @2%d@/@3%d@: Module 07 @4W%t#PADP_L01_TXT@ Device @1%d@/ @2%d@/@3%d@: Module 15 @5W%t#PADP_L01_TXT@ ... Device @1%d@/ @2%d@/@3%d@: Module 00 @4W%t#PADP_L01_TXT@ ... Device @1%d@/ @2%d@/@3%d@: Module 06 @10W%t#PADP_L01_TXT@ -
Message class
PLC Process Control Message Failure PLC Process Control Message Failure PLC Process Control Message Failure No message
No message PLC Process Control Message Failure
PLC Process Control Message Failure No message
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
379
Family: @System 6.69 PADP_L0x: Monitoring DP/PA slaves
Mes- sage block ALARM _8P
EV_ID3
Mes- Block sage param- number eter
1
-
...
7
-
8
-
Default message text
Device @1%d@/ @2%d@/@3%d@: Module 08 @4W%t#PADP_L01_TXT@ ... Device @1%d@/ @2%d@/@3%d@: Module 14 @10W%t#PADP_L01_TXT@ -
Message class
PLC Process Control Message Failure
PLC Process Control Message Failure No message
You will find the message texts and their text numbers in the Text library for PADP_L01 (Page 537)".
Assignment of associated values
Message block ALARM_8P EV_ID1
EV_ID2
EV_ID3
Associated value
1 2 3 4 - 5 1 2 3 4 - 10 1 2 3 4 - 10
Block parameter
SUBN_ID RACK_NO PADP_ADR SUBN_ID RACK_NO PADP_ADR SUBN_ID RACK_NO PADP_ADR -
Meaning
DP master system ID (byte) Rack/station number (byte) DP/PA device address (byte) Text number (message 2 - 3) from PADP_L01_TXT DP master system ID (byte) Rack/station number (byte) DP/PA device address (byte) Text number (message 1 - 7) from PADP_L01_TXT DP master system ID (byte) Rack/station number (byte) DP/PA device address (byte) Text number (message 1 - 7) from PADP_L01_TXT
If the PA field device is connected downstream from an inactive DP/PA-Link V0and SUBN1_ID = 16#FF, the associated variable is substituted by SUBN2_ID.
See also
Message Classes (Page 531)
6.69.6
Description of PADP_L02
Object name (type + number) FB 111 · PADP_L02 block I/Os (Page 374)
380
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.69 PADP_L0x: Monitoring DP/PA slaves
Area of application
The PADP_L02 monitors DP/PA field devices that are used as DPV0 or DPV1 slaves, downstream of a DP/PA or Y link that is used as a DPV0 slave. The PA field devices must conform to the PROFIBUS V3.0 profile. There must be individual blocks available for the diagnostics and signal processing for DP field devices. H systems support only the PA field devices at an active DP/PALink.
Calling OBs
The PADP_L02 block must be installed in the run sequence in the following OBs:
OB 1 OB 82 OB 85 OB 86 OB 100
Cyclic program Diagnostic interrupt Program execution error Rack failure Warm restart
Use in CFC
The following actions are executed automatically with the "Generate module drivers" CFC function:
· The PADP_L02 block is integrated in the run sequence downstream of block DPAY_V0.
· Parameters are assigned to the MODE_xx input (mode of slot xx of a field device).
· The PADP_ADR input (DP/PA slave address downstream of the DP/PA link or Y link) is configured.
· The DPA_M input is interconnected with the DPA_M_xx output of the DPAY_V0 block.
· The OUT structures CPU_DIAG of the OB_BEGIN block and RAC_DIAG of the DPAY_V0 block are interconnected with the IN_OUT structures of the same name of PADP_L02.
· The QMODF and PA_DIAG outputs are interconnected with the MOD_PAL0 block.
Function and method of operation
Block PADP_L02 analyzes all events affecting a DP or PA field device and its slots acyclically. It generates the relevant DP_MODE or PA_MODE, depending on the slot, and the value status for the DP or PA signal processing blocks. The permitted PA_MODE (Page 528) is already defined for the PA signal processing blocks. The DP_MODE must be defined individually for the DP field device blocks. ALARM_8P is used to report these events. The message function can be disabled.
The higher-level DPAY_V0 block enables the block to run. The event to be evaluated is entered in the start information (CPU_DIAG) of OB_BEGIN.
The data is already evaluated by the link block (DPAY_V0) if diagnostics are required. The diagnostic information concerning the PA field device is stored in the DPA_M structure. The structure consists of 2 DWORD (S_01 for module 1 to 16 and S_02 for module 17 to 32), and 1 BOOL (S_ERR = DP/PA field device faulty) variables. Two bits of the DWORD are assigned to each
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
381
Family: @System 6.69 PADP_L0x: Monitoring DP/PA slaves
slot of the DP/PA field device, whereby bit 0 and bit 1 belong to slot 1 of the DP/PA field device, etc. Slots 1 to 32 are evaluated. The bit states are defined as follows:
Status Bit 0 0 0 1 1
Status Bit 1 0 1 0 1
Meaning Module x OK (valid user data) Module x error (invalid user data) Wrong module x (invalid user data) No module x (invalid user data)
There is an input (MODE_xx) for each slot (module) on the DP/PA field device that is used to read in configuration settings made for the PA field device slots (module) in HW Config.
For DP field devices, the user must do his own encoding at the MODE input.
The function writes MODE_xx to the low word of the OMODE_xx (Page 527) output parameter. This occurs only during startup or if you set ACC_MODE = TRUE. The current slot value status is written to the most significant byte. If the result is positive, the system sets OMODE_xx = 16#80xxxxxx. The following events are evaluated by block DPAY_V0 and lead to the value status "Invalid value" due to a higher-level error (OMODE_xx = 16#40xxxxxx):
· Rack failure (OB 86)
(Output parameter QRACKF = TRUE)
· Diagnostic interrupt that affects entire field (Output parameter QMODF = TRUE,
device (OB 82)
if DPA_M.S_ERR = TRUE)
· Diagnostic interrupt slot xx that affects a field device (OB 82):
(Output parameter OMODE_xx = Module (slot) error-specific DPA_M)
The block reports a diagnostic interrupt to WinCC for a specific field device using ALARM_8P. We distinguish between the field device and its slots; each slot is assigned a message ID.
The "Device failure" message can be disabled with EM_MSG_D = FALSE.
Redundancy
The higher-level block DPAY_V0 evaluates the redundancy of the DP master systems used in an H system.
MODE setting for PA profiles You will find additional information in "PA_MODE settings (Page 528)".
Note If you change the parameter settings for the MODE_xx inputs at runtime, these changes will not be accepted at the outputs until the ACC_MODE is set to 1.
OMODE Structure You will find additional information in the "OMODE (Page 527)" section.
382
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.69 PADP_L0x: Monitoring DP/PA slaves
Error handling The plausibility of input parameters is not checked.
Startup characteristics
After a restart or an initial start, the system verifies that the PA field device is available under its logical base address. A restart (OB100) is reported via the LSB in byte 2 of the OMODE_xx (Page 527) outputs.
Time response Not available
Message response
The block signals field device errors using ALARM_8P, and generates the following messages in the OBs listed below:
OB no. OB 1
Start Event Cyclic processing
OB 82 Diagnostic interrupt
OB 100 Restart
Message
Repeat the update of ALARM_8P outputs/messages, if necessary
Device error incoming/outgoing Device module xx error incoming/outgoing Device module xx incorrect incoming/outgoing Device module xx missing incoming/outgoing
Initialization of ALARM_8P
Operator control and monitoring The block has no faceplate.
Additional information For additional information, refer to the sections: Message texts and associated values of PADP_L02 (Page 384)
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
383
Family: @System 6.69 PADP_L0x: Monitoring DP/PA slaves
6.69.7
Message texts and associated values of PADP_L02
Assignment of message text and message class
Mes- sage block ALARM _8P EV_ID1
EV_ID2
EV_ID3
EV_ID4
EV_ID5
Mes- Block sage param- number eter
1
QMODF
...
5
-
6
-
...
8
-
1
-
...
7
-
8
-
1
-
...
7
-
8
-
1
-
...
7
-
8
-
1
-
...
7
-
8
-
Default message text
Device @1%d@/ @2%d@/@3%d@: Failure ... Device @1%d@/ @2%d@/@3%d@: Module 31 @7W%t#PADP_L02_TXT@ ... Device @1%d@/ @2%d@/@3%d@: Module 00 @4W%t#PADP_L02_TXT@ ... Device @1%d@/ @2%d@/@3%d@: Module 06 @10W%t#PADP_L02_TXT@
Device @1%d@/ @2%d@/@3%d@: Module 08 @4W%t#PADP_L02_TXT@ ... Device @1%d@/ @2%d@/@3%d@: Module 14 @10W%t#PADP_L02_TXT@
Device @1%d@/ @2%d@/@3%d@: Module 16 @4W%t#PADP_L02_TXT@ ... Device @1%d@/ @2%d@/@3%d@: Module 22 @10W%t#PADP_L02_TXT@
Device @1%d@/ @2%d@/@3%d@: Module 24 @4W%t#PADP_L02_TXT@ ... Device @1%d@/ @2%d@/@3%d@: Module 30 @10W%t#PADP_L02_TXT@
You will find the message texts and their text numbers in "Text library for PADP_L02 (Page 537)".
Message class
PLC Process Control Message Failure
PLC Process Control Message Failure No message
No message PLC Process Control Message Failure
PLC Process Control Message Failure No message PLC Process Control Message Failure
PLC Process Control Message Failure No message PLC Process Control Message Failure
PLC Process Control Message Failure No message PLC Process Control Message Failure
PLC Process Control Message Failure No message
384
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.70 PADP_L10: Monitoring PA slaves downstream of DPV0 with up to 16 slots
Assignment of associated values to the block parameters of PADP_L02
Message block Associated
ALARM_8P
value
EV_ID1
1
2
3
4 - 7
EV_ID2
1
2
3
4 - 10
EV_ID3
1
2
3
4 - 10
EV_ID4
1
2
3
4 - 10
EV_ID5
1
2
3
4 - 10
Block parameter
SUBN_ID RACK_NO PADP_ADR SUBN_ID RACK_NO PADP_ADR SUBN_ID RACK_NO PADP_ADR SUBN_ID RACK_NO PADP_ADR SUBN_ID RACK_NO PADP_ADR -
Meaning
DP master system ID (byte) Rack/station number (byte) DP/PA device address (byte) Text number (message 2 - 5) from PADP_L02_TXT DP master system ID (byte) Rack/station number (byte) DP/PA device address (byte) Text number (message 1 - 7) from PADP_L02_TXT DP master system ID (byte) Rack/station number (byte) DP/PA device address (byte) Text number (message 1 - 7) from PADP_L02_TXT DP master system ID (byte) Rack/station number (byte) DP/PA device address (byte) Text number (message 1 - 7) from PADP_L02_TXT DP master system ID (byte) Rack/station number (byte) DP/PA device address (byte) Text number (message 1 - 7) from PADP_L02_TXT
If the PA field device is connected downstream from an inactive DP/PA-Link V0and SUBN1_ID = 16#FF, the associated variable is substituted by SUBN2_ID.
See also
Message Classes (Page 531)
6.70
PADP_L10: Monitoring PA slaves downstream of DPV0 with up to 16 slots
6.70.1
Description of PADP_L10
Object name (type + number) FB 116 · PADP_L10 block I/Os (Page 390)
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
385
Family: @System 6.70 PADP_L10: Monitoring PA slaves downstream of DPV0 with up to 16 slots
Area of application Block PADP_L10 monitors DPV0 PA field devices with a maximum of 32 slots, which are operated as DPV0 slaves on a DP master system, either directly or via a DP/PA coupler. The DP/PA coupler is connected downstream of a DPV1 DP/PA link. The PA field devices must conform to the PROFIBUS V3.0 profile. H systems support only the PA field devices at an active DP/PA-Link.
Calling OBs
The block must be installed in the run sequence downstream from the OB_DIAG1 block in the following OBs (this is done automatically in the CFC):
OB 1 OB 55 OB 56 OB 57 OB 82 OB 83 OB 85 OB 86 OB 100
Cyclic program Status interrupt (only if a PA slave is required) Update interrupt (only if a PA slave is required) Vendor-specific interrupt (only if a PA slave is required) Diagnostic interrupt Remove/insert module interrupt (failure/return of a field device) Program execution error Rack failure Warm restart
Use in CFC
The following actions are executed automatically with the "Generate module drivers" CFC function:
· Block OB_DIAG1 is installed in the run sequence upstream of PADP_L10.
· The following are configured, depending on whether the PA field device is connected directly to a DP master system or downstream of a DP/PA link:
the diagnostic address of the PA field device or of the DADDR DP/PA link
the geographic address (SUBN1_ID, SUBN2_ID, RACK_NO of the PA address of the PA field device or the DP/PA link)
SLOT_NO = 0 or the geographic address of the PA field device in the DP/PA link (SLOT0_NO = Slot 0 no. for the PA field device, SLOTS_NO = number of slots of the PA field device)
SLOTS_NO = number of slots of the PA field device
the PA address of the PA field device (PADP_ADR)
MODE_xx (mode of slot xx of a PA field device)
· The CPU_DIAG and CPU_OB_5X OUT structures of OB_BEGIN and RAC_DIAG of OB_DIAG1 are interconnected with the IN_OUT structures of the same name of PADP_L10.
· The EN input is interconnected with the output of an AND block. whose inputs are interconnected with the outputs EN_SUBx (x = number of the DP master system) of the OB_BEGIN block, EN_Rxxx (xxx = rack/station number) of the SUBNET block, EN_Mx (x= number of the PA device) of the DPAY_V1 block, and EN_F of the OB_DIAG1 block.
· EN_DIAG is interconnected with output EN_DIAG of OB_DIAG1.
386
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.70 PADP_L10: Monitoring PA slaves downstream of DPV0 with up to 16 slots
· Output QPERAF is interconnected with input PERAF of MOD_PAX0 or MOD_PAL0. · Output QMODF is interconnected with input MODF of MOD_PAX0 or MOD_PAL0. · Output PA_DIAG is interconnected with input PA_DIAG of MOD_PAX0 or MOD_PAL0.
Note The CFC function "Generate module drivers" can only be used if the PA field device belongs to slave family 12.
Description of the functions
Block PADP_L10 analyzes all events affecting a PA field device acyclically. It generates the slotspecific MODE (PA_MODE (Page 528)) and the value status for signal processing blocks. The permitted PA_MODE is defined for PA field devices.
If you are using modular PA field devices (DPV0), the next block (MOD_PAX0/MOD_PAL0) always reports the events in slot 0 of the PA field device in the DP/PA link. The affected MOD_PAX0/ MOD_PAL0 block is enabled.
How it works
Block PADP_L10 is enabled to run by the higher-level OB_DIAG1 block. The event to be evaluated is entered in the start information (CPU_DIAG) of OB_BEGIN. Block PADP_L10 checks the geographic address and the number of slots (SLOT_NO) of the PA field device to determine whether it is responsible for this event.
For a diagnostic event (OB 82, OB 55, OB 56, OB 57), SFB 54 is used to synchronously read the data from OB_BEGIN.
If diagnostic data could not be read synchronously from OB_BEGIN or when requested by OB_DIAG1 (EN_DIAG = TRUE), SFB 52 (RDREC) is used to read the current diagnostic data asynchronously.
Byte 9 of the additional alarm information contains the slot number of the field device that triggered the diagnostic interrupt. The corresponding slot is enabled.
The following diagnostic data is interpreted as a higher-level error in the block:
Additional alarm information
Byte no. Byte 1 to 6 Byte 7
Byte 8
Byte 9
DPV1 name Header
Status_Type
Bit no.
Bit 7 Bit 6 Bit 5 to bit 0 Bit 7 Bit 6 to bit 0
Value
DDLM_SLAVE_DIAG 0 0 8 or optional 1 126
Slot_number
Slot number of the PB
Info
fixed fixed Length of diagnostic data Status Highest vendorspecific status, will not be used in future The PB contains the diagnos- tic data.
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
387
Family: @System 6.70 PADP_L10: Monitoring PA slaves downstream of DPV0 with up to 16 slots
Byte no. Byte 10
Byte 11 to 14 optional Bytes 11 to 20
DPV1 name Specifier
Bit no. Bit 7 to bit 2 Bit 1 to bit 0
Value
Reserved 1: status is displayed 2: status is not displayed Diagnostics
Info
depends on the content of di- agnostic data
With a DPV0 PA field device, the diagnostic data is always assigned to slot 0.
It is also possible to generate slot-specific diagnostics for DPV1 PA field devices. These have not yet been defined. With a DPV1 field device, only the field-device slot that triggered the diagnostics is enabled. Evaluation of the coding in the context of higher-level errors in the slotspecific OMODE_xx (Page 527) outputs is based solely on the diagnostic information at slot 0.
MODE setting for PA profiles (PA_MODE)
For more information, refer to the section: "MODE settings for PA devices (Page 528)".
The function writes MODE_xx to the low word of the OMODE_xx (Page 527) output parameter. This occurs only during startup or if you set ACC_MODE = TRUE. The current slot value status is written to the most significant byte. If the result is positive, the system sets OMODE_xx = 16#80xxxxxx. The following events lead to the value status "invalid value due to higher-level error" (OMODE_xx = 16#40xxxxxx):
· Rack failure (OB 86) (output parameter QRACKF = TRUE)
· Failure/return of a field device (OB 83)
· Slot-specific diagnostic interrupt (OB 82)
388
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.70 PADP_L10: Monitoring PA slaves downstream of DPV0 with up to 16 slots
Byte 11 12
13 14
Bytes 11 to 14 of the additional interrupt information are evaluated to form the slot-specific value status:
Bit
0 1 2 3 4 5 6 7
0 1 2 3 4 5 6 7
0 1 2
3
4...7
0...4 5 6 7
Mnemonics
DIA_HW_ELECTR DIA HW MECH DIA_TEMP_MOTOR DIA TEMP ELECTR DIA MEM CHKSUM DIA_MEASUREMENT DIA NOT INIT DIA_INIT_ERR
DIA ZERO ERR DIA_SUPPLY DIA CONV INVAL DIA_WARMSTART DIA COLDSTART DIA MAINTENANCE DIA_CHARACT IDENT NUMBER Violation
DIA_MAINTENANCE_ALARM DIA_MAINTENANCE_DEMANDED DIA_FUNCTION_CHECK
DIA_INV_PRO_COND
Reserved
Reserved PROFILE_SPECIFIC_EXTENSION _AVAILABLE MANUFACTURER_SPECIFIC _EXTENSION_AVAILABLE EXTENSION_AVAILABLE
Description
Display class
Electronic hardware failure
R
Mechanical hardware failure
R
Excess motor temperature
R
Excess temperature at electronic circuit
R
Memory error
R
Measurement failure
R
Device not initialized
R
(no auto-calibration)
R
Auto-calibration error
Zero error (limit position)
R
No power supply (electr. pneum.)
R
Invalid configuration
R
Warm start executed
A
Complete restart executed
A
Maintenance necessary
R
Invalid identifier
R
= 1, if the ID number of
R
the current cyclic data transfer
and the value of the IDENT NUMBER
parameter of the physical block are different
Device error
R
Maintenance requested
R
Device is in a functional check or in simulation R or under local operator control (maintenance)
The process conditions do not permit valid val- R ues to be returned. (Set if quality "Uncertain, process-related, no maintenance" or "Bad, process-related, no main- tenance")
Reserved for PNO, default 0
Reserved for PNO use
= 0: For devices with this profile
= 0: For devices with this profile
= 0: No further diagnostic information available = 1: Further diagnostic information available in DIAGNOSIS_EXTENSION
Display class R = incoming / outgoing events.
Display class A = incoming events that are reset by the field device after a few cycles. All events in byte 11 and the events of bit 0, 1 and 2 in byte 12 lead to the value status "Higher-level error" (OMODE_xx (Page 527) = 16#40xxxxxx).
Bytes 11, 12, 13, and 14 are entered in bytes 0 to 3 of the PA_DIAG parameter to generate messages and maintenance status (MS) in the MOD_PAX0/MOD_PAL0 block.
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
389
Family: @System 6.70 PADP_L10: Monitoring PA slaves downstream of DPV0 with up to 16 slots
Special features of PA_AO and PA_DO field devices
With the field devices listed above, the PA profiles can be defined at two different slots. In this case, the driver generator will assign the mode code of the PA field device to the first slot and the mode code 16#8000 to the second at the corresponding MODE inputs of the block. The block links the diagnostic information of the second slot with the first with an OR logic operation. which allows the generation of a uniform value status for the PA_x block.
Redundancy
The higher-level block evaluates the redundancy of DP master systems operating in an H system.
OMODE Structure You will find additional information in the "OMODE (Page 527)" section.
Addressing
You will find additional information in the "Addressing (Page 530)" section.
Error handling The plausibility of input parameters is not checked.
Startup characteristics A restart (OB 100) is reported via the LSB in byte 2 of the OMODE_xx (Page 527) outputs.
Time response Not available
Message response Not available
Operator control and monitoring The block has no faceplate.
6.70.2
I/Os of PADP_L10
The factory setting of the block display in the CFC is identified in the "I/O" column: I/O name bold = I/O visible, I/O name normal = I/O not visible.
You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15)".
390
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.70 PADP_L10: Monitoring PA slaves downstream of DPV0 with up to 16 slots
Input parameters
I/O
DADDR DIAG_BUF
EN_DIAG MODE_xx PADP_ADR PROF_V30 RACK_NO SLOT0_NO
SLOTS_NO SUBN_TYP SUBN1_ID SUBN2_ID
Meaning
Type
Diagnostic address of the PA field device or DP/PA link Entry in diagnostic buffer (relevant for maintenance person- nel) 1 = Queued diagnostic event Mode slot (xx = 16 - 31) Address of the PA field device 1 = PA slave profile V3.0 Address of PA field device or rack number Slot number 0 of the field device in the DP/PA or Y link, or 0 if there is no link Number of slots of the field device 1 = external DP interface ID of the primary DP master system ID of the redundant DP master system
INT BOOL
BOOL WORD BYTE BOOL BYTE BYTE
BYTE BOOL BYTE BYTE
De- fault 0 0
0 0 0 0 255 0
0 0 255 255
Output parameters
I/O
DINFO EN_M_xx OMODE_xx PA_DIAG QERR QMODF QPERAF QRACKF
Meaning
Diagnostic status of the PA field device Enable slot (xx = 0 - 31) Mode slot (xx = 16 - 31) PA field device diagnostic information 1 = program error 1 = field device error/fault 1 = I/O access error 1 = higher-level error
Type
STRUCT BOOL DWORD DWORD BOOL BOOL BOOL BOOL
De- fault
0 0 0 0 0 0 0
In/out parameters
I/O
ACC_MODE CPU_DIAG CPU_OB_5X RAC_DIAG
Meaning
1 = accept MODE settings CPU diagnostics OB_5x startup information PA field device or link diagnostics
Type
BOOL STRUCT STRUCT STRUCT
De- fault
0
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
391
Family: @System 6.71 PADP_L10_PN: Monitoring PA slaves downstream of DPV0 with up to 16 slots
6.71
PADP_L10_PN: Monitoring PA slaves downstream of DPV0 with up to 16 slots
6.71.1
Description of PADP_L10_PN
Object name (type + number) FB 203 · I/Os of PADP_L10_PN (Page 392)
Area of application
Block PADP_L10_PN monitors DPV0 PA field devices with a maximum of 16 slots which are operated as DPV0 slaves on a DP master system, either directly or via a DP/PA coupler. The DP/PA coupler is connected downstream of an IE/PB link. The PA field devices must conform to the PROFIBUS V3.0 profile.
6.71.2
I/Os of PADP_L10_PN
The factory setting of the block display in the CFC is identified in the "I/O" column: I/O name bold = I/O visible, I/O name normal = I/O not visible.
You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15)".
Input parameters
I/O
DADDR DIAG_BUF
EN_DIAG MODE_xx PADP_ADR PROF_V30 RACK_NO SLOT0_NO SLOTS_NO SUBN_TYP SUBN1_ID SUBN2_ID
Meaning
Type
Diagnostic address of the PN IO device Entry in diagnostic buffer (relevant for maintenance person- nel) 1 = Queued diagnostic event Mode slot (xx = 00 - 31) Address of the PA field device 1 = PA slave profile V3.0 Rack number Slot number 0 of the slave at the IE/PB link Number of slots of the field device 1 = external PN interface PN IO system 1 ID (100 - 115) PN IO system 2 ID (100 - 115)
INT BOOL
BOOL WORD BYTE BOOL BYTE BYTE BYTE BOOL BYTE BYTE
De- fault 0 0
0 0 0 0 255 0 0 0 255 255
392
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Output parameters
I/O
DINFO EN_M_xx OMODE_xx PA_DIAG QERR QMODF QPERAF QRACKF
Family: @System 6.72 PAM_CD: Monitoring Compact Devices within the Package Unit
Meaning
Diagnostic status of the PA field device Enable slot (xx = 0 - 31) Mode slot (xx = 16 - 31) PA field device diagnostic information 1 = program error 1 = field device error/fault 1 = I/O access error 1 = higher-level error
Type
STRUCT BOOL DWORD DWORD BOOL BOOL BOOL BOOL
De- fault
0 0 0 0 0 0 0
In/out parameters
I/O
ACC_MODE CPU_DIAG_PN CPU_OB_5X RAC_DIAG
Meaning
1 = accept MODE settings System structure: CPU diagnostics OB_5x startup information System structure: RACK diagnostics
Type
BOOL STRUCT STRUCT STRUCT
De- fault
0
6.72
PAM_CD: Monitoring Compact Devices within the Package Unit
6.72.1
Description of PAM_CD
Object name (type + number) FB 438 · I/Os of PAM_CD (Page 397)
Functions
The PAM_CD block:
· Retrieves data from the Compact Devices(CD) of the package unit and sends it to the automation station of the PAM unit.
· Reads 160 bytes of data specific to PAM_CD block from the user data block (for example: DB_PAM_CD) of the package unit.
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
393
Family: @System 6.72 PAM_CD: Monitoring Compact Devices within the Package Unit
How it works
The PAM_CD block retrives data either through the DB_PAM_CD block of the package unit or through the PAM_IF block. (For more information on PAM_IF block see: PAM_IF: Interface block to PAM Diagnostic Blocks (Page 505))
It creates Maintenance Status (MS) that depends on:
· MS provided by SIMATIC PDM.
· External MS.
· Analog values that are monitored for three limits.
· Status of the analog values.
Of all these events, the highest priority event is displayed in the MS.
Note
The table below is valid exclusively for the MS and not for the signal status displays of the individual process values; these are created exclusively by the ST parameters. The priority is similar to the MS coding. Therefore, the following applies: the lower the value of the MS, the higher the priority.
GP bits of DB_CPU
MS via PDM PVx.Value via DXCHG
PVx.ST via DXCHG
MS_Ext via DXCHG
10...16: Re- serve 9: Redundan- 9 cy error 8: Unknown 8 7: Configura- 7 tion changed 6: Function 6 control
5: Passivated 5
4: Out of or- 4 der 3: Mainte- 3 nance re- quest 2: Mainte- 2 nance de- mand 1: Mainte- 1 nance alarm
0
PVx.Value >= 16#00
7
PVx_AH
PVx_AH >
16#68
6
PVx.Value >=
PVx_DH
PVx_DH >
16#A4
5
PVx.Value >=
PVx_RH
16#60
PVx_RH > PVx.Value
16#28, 16#78
Output pa- rameter (O_MS) 10...16 9 8 7 6
5
4 3
2
1 0
394
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.72 PAM_CD: Monitoring Compact Devices within the Package Unit
The inputs PVx.Value and PVx.ST are transfered via DXCHG with PAM_IF block. However, the source of these inputs might differ between DB or direct connection in CFC (Link). When you click the "Reset" button in the faceplate, a reset impulse is available at the corresponding output of the PAM_IF block for one cycle. After one successful cycle, the reset value is set back to 0 PAM_CD block and the diagnostic information is transferred to PAM_IF block. The PAM_CD block does not participate in coordination if DBNO=0. A message "Communication breakdown" is reported and MS of 6 is set. · If the communication between PAM_CD block of PAM station and package unit is disrupted. · If the OT <> 4 (compact device). In case the OT delivered by data block do not match with the
expected OT of PAM_CD, then OT = 4.
Calling OBs
The PAM_CD block is instantiated during diagnostics screen generation in OB35. The block coordinates the FB_GET operations of lower order objects. Here, the lower order block refers to PAM_SM, PAM_IM, and PAM_CD whereas, the higher order block refers to PAM_CPU.
The following parameters are automatically parametrized by the driver generator:
Parameter PLT_ID ID DBNO
Meaning
PLT-ID of SIMATIC PDM object. Netpro connection ID. Data block number configured in the "Advanced Diagnostics Settings" of Plant Hierarchy (PH).
The following output parameters are automatically connected with corresponding parameters within the lower order blocks by the driver generator:
Output parameter of PAM_CPU block
connected with I/O parameter of PAM_CD block
TOP_SI
START_UP_SI
DXCHG_xx (xx: 00..199)
TOP_SI START_UP_SI DXCHG_IN
If the processing of Process Value for the corresponding PAM object is enabled in "Advanced Diagnostic Settings" dialog of PH, the following connections are automatically created by the driver generator:
Output parameter of PAM_CPU block
DXCHG_PAM
connected with I/O parameter of PAM_IF block DXCHG_PAM
Error handling
The values of I/Os QERR and ERR_NUM are independent of each other. The value of QERR = 1 represents a runtime error.
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
395
Family: @System 6.72 PAM_CD: Monitoring Compact Devices within the Package Unit
The ERR_NUM I/O is used to obtain the following errors in the output:
Error number -1 0 1
2 3 4 5
6
Meaning
Predefined value when inserting the block; block is not processed. There is no error. Connection problems, for example: · Connection is not established.
· Connection establishment is in progress.
· No availability of information regarding connection status.
· Connection is not configured. Negative acknowledgement from the partner device. The function can- not be executed. Access error on the partner CPU. Errors in the receive area pointers RD_i involving the data length or the data type. No instance data block found. · Access to the local user memory is not possible (for example, access
to a deleted data block).
· S7-400: Not enough work memory is available. If there is still enough total work memory available, then the solution is to compress the work memory.
OT number is not equal to 4.
Startup characteristics The PAM_CD block initializes the instances of ALARM_8P and NOTIFY_8P. Once the startup for the number of cycles is set at RunUpCyc, the messages are suppressed.
Modes
The following modes are available for operators in the faceplate to initiate or select an operation: · On · Passivated · Out of service On The following actions occur in this mode: · processing of messages (for example: alarms). · processing of MS, MS_Ext, and signal states. Passivated The following actions occur in this mode: · processing of MS, MS_Ext, and signal states but without any impact on MS. · setting the value of MS_OUT to 16#01 (to denote the "passivated" mode).
396
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.72 PAM_CD: Monitoring Compact Devices within the Package Unit
The following action does not occur in this mode: · processing of messages (for example: alarms). Out of service The following actions occur in this mode: · setting the value of MS_OUT = 16#02 (to denote "out of service" mode). · processing of analog values PVx.Value = 0, PVx_ST=16#80. · disabling the display of DIAG_GB / DIAG_DD parameter in "Binary details diagnose view" of
faceplate. The value of DIAG_GB / DIAG_DD is set to 0. The following actions do not occur in this mode: · processing of messages (for example: alarms). · processing of MS, MS_Ext, and signal states. · FB_GET operations. In the "Monitoring View", all the information is displayed in grey.
Time response Not available
Additional information For additional information, refer to the sections: Messages and associated values of PAM_CD (Page 400) I/Os of PAM_CD (Page 397)
6.72.2
I/Os of PAM_CD
I/Os of PAM_CD The factory setting of the block display in the CFC is identified in the "I/O" column:
I/O name bold = I/O visible, I/O name normal = I/O not visible.
You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15)".
Input parameters
I/O Parameter PLT_ID MS MS2
Meaning
Type
Asset ID for EDD Maintenance status Maintenance status 2 for OS operations
DWORD DWORD DWORD
Default
16#00000000 16#F0000008 16#00000000
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
397
Family: @System 6.72 PAM_CD: Monitoring Compact Devices within the Package Unit
I/O Parameter EV_ID1 EV_ID2 EN_MSG RUNUPCYC CYCL_UPD
DIAG_BUF
FEATURE ID DBNO PV_EN PVx_AH_En
PVx_DH_En
PVx_RH_En
PVx_Rst
Meaning
Type
Message number 1
Message number 2
1 = Enable message
Number of Run Up Cycles
1 = Cyclic update active (preselection for FB first run or CPU restart)
Entry in diagnostic buffer (relevant for maintenance personnel)
Feature parameter
Netpro connection ID
Data block number
1 = Enable process value
1=Enable maintenance alarm process value x (x: 0...2)
1=Enable maintenance demand process value x (x: 0...2)
1=Enable maintenance request process value x (x: 0...2)
Reset process value x(x: 0...2)
DWORD DWORD BOOL INT BOOL
BOOL
DWORD WORD WORD BOOL BOOL
BOOL
BOOL
BOOL
Output parameters
I/O Parameter QERR O_MS MSG_STATx MSG_ERRx MSG_ACKx NDR1 ERROR1 STATUS1 DB_LID DB_CP DB_OT DIAG_GB DIAG_DD DIAG_ST ERR_NUM P_PVx_Rst PVx_AH_Act
PVx_DH_Act
Meaning
Type
1 = Runtime error
BOOL
Maintenance state
DWORD
Message status x (x:1...2)
WORD
Message error x (x: 1...2)
WORD
Message acknowledgementx (x:1)
WORD
SFB14 New data received 1
BOOL
SFB14 Error 1
BOOL
SFB14 Status number 1
WORD
LID
STRING(64)
Connection point
STRING(64)
Object type
INT
Interface sector Pos01-16
WORD
Detail diagnosis
WORD
Status information
BYTE
Error number
INT
1=Reset process value x (x: 0...2)
STRUCT
1=Limit maintenance alarm process val- BOOL ue x (x: 0...2)
1=Limit maintenance demand process BOOL value x (x: 0...2)
Default
16#00000000 16#00000000 1 1 1
1
16#00000000 16#0000 16#0000 1 1
1
1
1
Default
1 16#08000000 16#0000 16#0000 16#0000 1 1 16#0000 `' `' 1 16#0000 16#0000 0 1 0 1
1
398
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.72 PAM_CD: Monitoring Compact Devices within the Package Unit
I/O Parameter PVx_RH_Act
PVx_Diff
DXCHG_PAM ERROR STATUS C_CONN C_STATUS PVx
PVx_AH
PVx_DH
PVx_RH
PVx_Name PVx_Unit PVx_OpScale
UPDATE_TIME PRE_UP- DATE_TIME UP- DATE_DIFF_TIME
Meaning
Type
1=Limit maintenance request process value x (x: 0...2)
Difference value to the next expected Alarm x (x: 0...2)
BOOL STRUCT
Bidirectional data exchange channel Connection function check ERROR Connection function check STATUS Status of the corresponding connection Connection status Process value x (x: 0...2)
STRUCT (UDT283) BOOL WORD BOOL WORD STRUCT
Limit maintenance alarm process value x (x: 0...2)
Limit maintenance demand process val- ue x (x: 0...2)
Limit maintenance request process val- ue x (x: 0...2)
Text of Process value x (x:0...2)
Unit of Process value x (x:0...2)
Range of process value x (x: 0...2)
REAL
REAL
REAL
STRING[16] INT STRUCT
Time of update in ms Time of previous update in ms
DINT DINT
Time difference between present and previous update in ms
DINT
Default
1
0 16#80 0 1 16#0000 1 16#0000 0 16#80 99.99
99.99
99.99
`' 1 0 100 0 0
0
In_Out parameters
I/O Parameter ACC_MODE DXCHG_IN TOP_SI START_UP_SI
Meaning
Type
1 = Accept new settings
Bidirectional data exchange channel
Start information of the current OB
Start information of the startup OB last started
BOOL DWORD STRUCT STRUCT
Default
1 16#00000000 0 0
Additional information For additional information, refer to the section: Messages and associated values of PAM_CD (Page 400) Message Classes (Page 531)
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
399
Family: @System 6.73 PAM_CPU: Monitoring CPUs within the Package Unit
6.72.3
Messages and associated values of PAM_CD
Assignment of message text and message class The process control messages of ALARM_8P with EV_ID1 are assigned as follows:
Message number 1
2
3
4
5
6 7 8
Default message text
Message class
Maintenance alarm (@4W%t#PAM_CD_TXT@): PLC PLC Process Control Message Failure
Communication breakdown: PLC Process Control PLC Process Control Message -
Message - Error
Error
Maintenance demand (@4W%t#PAM_CD_TXT@): PLC Process Control Message -
PLC Process Control Message - Error
Error
Maintenance request (@4W%t#PAM_CD_TXT@)
Preventative Maintenance Standard
Device out of order (@4W%t#PAM_CD_TXT@)
PLC Process Control Message Failure
No message
No message
No message
The process control messages of NOTIFY_8P with EV_ID2 are assigned as follows:
Message number 1 2 3
4 5 6 7 8
Default message text
Device passivated (@1W%t#PAM_CD_TXT@) Undefined diagnostics (@1W%t#PAM_CD_TXT@) Local operation/functional check (@1W %t#PAM_CD_TXT@) Simulation (@1W%t#PAM_CD_TXT@ Configuration change (@1W%t#PAM_CD_TXT@) Process-related fault (@1W%t#PAM_CD_TXT@)
Message class Status Message - PLC Status Message - PLC Status Message - PLC
Status Message - PLC Status Message - PLC Status Message - PLC No message No message
You can find additional information in the section: Message Classes (Page 531)
6.73
PAM_CPU: Monitoring CPUs within the Package Unit
6.73.1
Description of PAM_CPU
Object name (type + number) FB 436 · I/Os of PAM_CPU (Page 405)
400
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Functions
Family: @System 6.73 PAM_CPU: Monitoring CPUs within the Package Unit
The PAM_CPU block: · Coordinates with the lower order objects of package unit. · Reads 160 bytes of data specific to PAM_CPU block from the user data block (for example:
DB_CPU_XX) of the package unit.
How it works
The PAM_CPU block obtains data specific to PAM station either through the package unit or through the PAM_IF block. (For more information on PAM_IF block see:PAM_IF: Interface block to PAM Diagnostic Blocks (Page 505)).
It creates Maintenance Status (MS) that depends on:
· MS provided by SIMATIC PDM.
· External MS.
· Analog values that are monitored for three limits.
· Status of the analog values.
Of all these events, the highest priority event is displayed in the MS.
Note
The table below is valid exclusively for MS and not for the signal status displays of individual process values (these are created exclusively by the ST parameters). The priority is similar to MS coding. Therefore, the following applies: the lower the value of the MS, the higher the priority.
GP bits of DB_CPU
MS via PDM
PVx.Value via DXCHG
PVx.ST via DXCHG
12...16: Re- serve 11: Productin- fo Rack 0/1 10: Productin- fo Single/Red 9: Redundancy 9 error 8: Unknown 8 7: Configura- 7 tion changed 6: Function 6 control
5: Reserved 5
PVx.Value >= PVx_AH PVx_AH > PVx.Value >= PVx_DH PVx_DH > PVx.Value >= PVx_RH
16#00 16#68
16#A4
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
MS_Ext via DXCHG
7 6
Output parame- ter (O_MS) 12...16
11
10
9
8 7
6
5
5
401
Family: @System 6.73 PAM_CPU: Monitoring CPUs within the Package Unit
GP bits of DB_CPU
MS via PDM
PVx.Value via DXCHG
4: Reserved 4
3: Mainte-
3
nance request
2: Mainte-
2
nance demand
1: Mainte-
1
nance alarm
0
PVx_RH > PVx.Value
PVx.ST via DXCHG
MS_Ext via DXCHG
16#60
16#28, 16#78
Output parame- ter (O_MS) 4 3
2
1
0
The inputs PVx.Value and PVx.ST are transfered via DXCHG with PAM_IF block. However, the source of these inputs might differ between DB or direct connection in CFC (Link).
When you click the "Reset" button in the faceplate, a reset impulse is available at the corresponding output of the PAM_IF block for one cycle. After one successful cycle, the reset value is set back to 0 in PAM_SM /PAM_IM /PAM_CD block and the diagnostic information is transferred to PAM_IF block.
A message "Communication breakdown" is reported and MS of 6 is set if:
· the communication between the PAM_CPU blocks of PAM station and the package unit is disrupted.
· OT (Object Type) <> 1 (CPU). In case the OT delivered by data block do not match with the expected OT of PAM_CPU, then OT = 1.
Calling OBs
The PAM_CPU block is instantiated during diagnostics screen generation in OB35. The block coordinates the FB_GET operations of lower order objects. Here, the lower order block refers to PAM_SM, PAM_IM, and PAM_CD whereas, the higher order block refers to PAM_CPU.
The following parameters are automatically parameterized by the driver generator:
Parameter PLT_ID ID DBNO
Meaning
PLT-ID of SIMATIC PDM object. Netpro connection ID. Data block number configured in the "Advanced Diagnostics Settings" of Plant Hierarchy (PH).
The following output parameters are automatically connected with corresponding parameters within the lower order blocks by the driver generator:
Output parameter of PAM_CPU block
TOP_SI
START_UP_SI
DXCHG_xxx (xxx: 0...199)
connected with I/O parameter of PAM_SM / PAM_IM / PAM_CD block
TOP_SI START_UP_SI DXCHG_IN
402
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.73 PAM_CPU: Monitoring CPUs within the Package Unit
If the processing of Process Value for the corresponding PAM object is enabled in "Advanced Diagnostic Settings" dialog of PH, the following connections are automatically created by the driver generator:
Output parameter of PAM_CPU block
DXCHG_PAM
connected with I/O parameter of PAM_IF block DXCHG_PAM
Error handling
The values of I/Os QERR and ERR_NUM are independent of each other. The value of QERR = 1 represents a runtime error. The ERR_NUM I/O is used to obtain the following errors in the output:
Error number -1 0 1
2 3 4 5
6
Meaning
Predefined value when inserting the block; block is not processed. There is no error. Connection problems, for example: · Connection is not established.
· Connection establishment is in progress.
· No availability of information regarding connection status.
· Connection is not configured. Negative acknowledgement from the partner device. The function can- not be executed. Access error on the partner CPU. Errors in the receive area pointers RD_i involving the data length or the data type. No instance data block found. · Access to the local user memory is not possible (for example, access
to a deleted data block).
· S7-400: Not enough work memory is available. If there is still enough total work memory available, then the solution is to compress the work memory.
OT number is not equal to 1.
Startup characteristics The PAM_CPU block initializes the instances of ALARM_8P and NOTIFY_8P . Once the startup for the number of cycles is set at RunUpCyc, the messages are suppressed.
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
403
Family: @System 6.73 PAM_CPU: Monitoring CPUs within the Package Unit
Modes
The following modes are available for operators in the faceplate to initiate or select an operation: · On · Passivated · Out of service On The following actions occur in this mode: · processing of messages (for example: alarms). · processing of MS, MS_Ext and signal states. Passivated The following actions occur in this mode: · processing of MS, MS_Ext, and signal states but without any impact on MS. · setting the value of MS_OUT to 16#01 (to denote the "passivated" mode). The following action does not occur in this mode: · processing of messages (for example: alarms). Out of service The following actions occur in this mode: · setting the value of MS_OUT = 16#02 (to denote "out of service" mode). · processing of analog values PVx.Value = 0, and PVx_ST = 16#80. · disabling the display of DIAG_GB / DIAG_DD parameter in "Binary details diagnose view" of
faceplate. The value of DIAG_GB / DIAG_DD is set to 0. The following actions do not occur in this mode: · processing of messages (for example: alarms). · processing of MS, MS_Ext, and signal states. · FB_GET operations. In the "Monitoring View", all the information is displayed in grey.
Time response Not available
Additional information For additional information, refer to the sections: Message text and associated values of PAM_CPU (Page 407) Maintenance status MS (Page 533)
404
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
See also
Family: @System 6.73 PAM_CPU: Monitoring CPUs within the Package Unit
Description of PAM_IF (Page 505)
6.73.2
I/Os of PAM_CPU
The factory setting of the block display in the CFC is identified in the "I/O" column:
I/O name bold = I/O visible, I/O name normal = I/O not visible.
You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15)".
Input parameters
I/O (parameter) PLT_ID MS MS2 EV_ID1 EV_ID2 EN_MSG RUNUPCYC CYCL_UPD
DIAG_BUF
FEATURE ID DBNO PV_EN PVx_AH_En
PVx_DH_En
PVx_RH_En
PVx_Rst
Meaning
Data type
Asset ID for EDD
Maintenance status
Maintenance status 2 for OS operations
Message number 1
Message number 2
1 = Enable message
Number of Run Up Cycles
1 = Cyclic update active (preselection for FB first run or CPU restart)
Entry in diagnostic buffer (relevant for maintenance personnel)
Feature parameter
Netpro connection ID
Data block number
1 = Enable process value
1=Enable maintenance alarm process value x (x: 0...2)
1=Enable maintenance demand process value x (x: 0...2)
1=Enable maintenance request process value x (x: 0...2)
Reset process value x (x: 0...2)
DWORD DWORD DWORD DWORD DWORD BOOL INT BOOL
BOOL
DWORD WORD WORD BOOL BOOL
BOOL
BOOL
BOOL
Default
16#00000000 16#F0000008 16#00000000 16#00000000 16#00000000 1 1 1
1
16#00000000 16#0000 16#0000 1 1
1
1
1
Output parameters
I/O (parameter) QERR O_MS
Meaning
1 = Runtime error Maintenance state
Data type
BOOL DWORD
Default
1 16#08000000
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
405
Family: @System 6.73 PAM_CPU: Monitoring CPUs within the Package Unit
I/O (parameter) MSG_STATx MSG_ERRx MSG_ACKx NDR1 ERROR1 STATUS1 DB_LID DB_CP DB_OT DIAG_GB DIAG_DD P_PVx_Rst PVx_AH_Act
PVx_DH_Act
PVx_RH_Act
PVx_Diff
PVx
PVx_AH
PVx_DH
PVx_RH
PVx_Name PVx_Unit PVx_OpScale
RESERVE_00 DXCHG_xx
TOP_SI START_UP_SI
ERROR STATUS C_CONN C_STATUS UPDATE_TIME
Meaning
Data type
Message status x (x:1...2)
WORD
Message error x (x: 1...2)
WORD
Message
WORD
SFB14 New data received 1
BOOL
SFB14 Error 1
BOOL
SFB14 Status number 1
WORD
LID
STRING(64)
OKZ
STRING(64)
Object type
INT
Global part
WORD
Detail diagnosis
WORD
1=Reset process value x (x: 0...2)
STRUCT
1=Limit maintenance alarm process val- BOOL ue x (x: 0...2)
1=Limit maintenance demand process BOOL value x (x: 0...2)
1=Limit maintenance request process value x (x: 0...2)
BOOL
Difference value to the next expected Alarm x (x: 0...2)
STRUCT
Process value x (x: 0...2)
STRUCT
Limit maintenance alarm process value x (x: 0...2)
Limit maintenance demand process val- ue x (x: 0...2)
Limit maintenance request process val- ue x (x: 0...2)
Text of Process value x (x:0...2)
Unit of Process value x (x:0...2)
Range of process value x (x: 0...2)
REAL
REAL
REAL
STRING[16] INT STRUCT
Reserve Bidirectional data exchange Channel xx (xx:00...199) Start information of the current OB Start information of the startup OB last started Connection function check ERROR Connection function check STATUS Status of the corresponding connection Connection status Time of update in ms
BYTE DWORD
STRUCT STRUCT
BOOL WORD BOOL WORD DINT
Default
16#0000 16#0000 16#0000 1 1 16#0000 `' `' 1 16#0000 16#0000 16#0000 1
1
1
0 16#80 0 16#80 99.99
99.99
99.99
`' 1 0 100 0 16#00000000
0 0
1 16#0000 1 16#0000 0
406
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.73 PAM_CPU: Monitoring CPUs within the Package Unit
I/O (parameter)
PRE_UP- DATE_TIME
UP- DATE_DIFF_TIME
ERR_NUM
DXCHG_PAM
Meaning
Time of previous update in ms
Time difference between present and previous update in ms Error number Bidirectional data exchange Channel
Data type
Default
DINT
0
DINT
0
INT
1
STRUCT (UDT283) 0
In/Out parameters
I/O (parameter) ACC_MODE
Meaning 1= Accept new settings
Data type BOOL
Default 1
Additional information For additional information, refer to the section: Message text and associated values of PAM_CPU (Page 407) Maintenance status MS (Page 533)
6.73.3
Message text and associated values of PAM_CPU
Assignment of message text and message class The process control messages of ALARM_8P with EV_ID1 are assigned as follows:
Message number Default message text
1
Maintenance alarm (@4W%t#PAM_CPU_TXT@)
2
Communication breakdown: PLC Process Control
3
Maintenance demand (@4W
%t#PAM_CPU_TXT@):PLC
Message class
PLC Process Control Message Failure
PLC Process Control Message Error
PLC Process Control Message Error
4
Maintenance request (@4W%t#PAM_CPU_TXT@) Preventative Maintenance -
Standard
5
Device out of order (@4W%t#PAM_CPU_TXT@): PLC Process Control Message -
PLC
Failure
6
No message
7
No message
8
No message
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
407
Family: @System 6.74 PAM_IM: Monitoring Interface Modules within the Package Unit
The process control messages of NOTIFY_8P with EV_ID2 are assigned as follows:
Message number 1 2 3
4 5 6 7 8
Default message text
Device passivated (@1W%t#PAM_CPU_TXT@): Undefined diagnostics (@1W%t#PAM_CPU_TXT@) Local operation/functional check (@1W %t#PAM_SM_TXT@) Simulation (@1W%t#PAM_CPU_TXT@) Configuration change (@1W%t#PAM_SM_TXT@) Process-related fault (@1W%t#PAM_CPU_TXT@)
Message class Status Message - PLC Status Message - PLC Status Message - PLC
Status Message - PLC Status Message - PLC Status Message - PLC No message No message
You can find additional information in the section: Message Classes (Page 531)
6.74
PAM_IM: Monitoring Interface Modules within the Package Unit
6.74.1
Description of PAM_IM
Object name (type + number) FB 422 · I/Os of PAM_IM (Page 412)
Functions
The PAM_IM block:
· Retrieves data from the Interface Modules (IM) of the package unit and sends it to the automation station of the PAM unit.
· Reads 160 bytes of data specific to the PAM_IM block from the user data block (DB_PAM_IM) of the package unit.
How it works
The PAM_IM block retrives data either through the DB_PAM_IM block of the package unit or through the PAM_IF block. (For more information on PAM_IF block see: PAM_IF: Interface block to PAM Diagnostic Blocks (Page 505)).
It creates Maintenance Status (MS) that depends on:
· MS provided by SIMATIC PDM.
· External MS.
408
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.74 PAM_IM: Monitoring Interface Modules within the Package Unit
· Analog values that are monitored for three limits. · Status of the analog values. Of all these events, the highest priority event is displayed in the MS.
Note The table below is valid exclusively for the MS and not for the signal status displays of the individual process values; these are created exclusively by the ST parameters. The priority is similar to the MS coding. Therefore, the following applies:the lower the value of the MS, the higher the priority.
GP bits of DB_CPU
MS via PDM
10...16: Re- serve
9: Redundan- 9 cy error
8: Unknown 8
7: Configura- 7 tion changed
6: Function 6 control
5: Passivated 5
4: Out of order 4
3: Mainte-
3
nance request
2: Mainte-
2
nance de-
mand
1: Mainte-
1
nance alarm
0
PVx.Value via DXCHG
PVx.Value >= PVx_AH PVx_AH > PVx.Value >= PVx_DH PVx_DH > PVx.Value >= PVx_RH
PVx_RH > PVx.Value
PVx.ST via DXCHG
MS_Ext via DXCHG Output pa- rameter (O_MS)
10...16
9
8
16#00
7
7
16#68
6
6
16#A4
5
5
4
16#60
3
2
1
16#28,
0
16#78
The inputs PVx.Value and PVx.ST are transfered via DXCHG with PAM_IF block. However, the source of these inputs might differ between DB or direct connection in CFC (Link).
When you click the "Reset" button in the faceplate, a reset impulse is available at the corresponding output of the PAM_IF block for one cycle. After one successful cycle, the reset value is set back to 0 PAM_IM block and the diagnostic information is transferred to PAM_IF block.
The PAM_IM block does not participate in coordination if DBNO=0.
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
409
Family: @System 6.74 PAM_IM: Monitoring Interface Modules within the Package Unit
A message "Communication breakdown" is reported and MS of 6 is set: · If the communication between PAM_IM block of PAM station and package unit is disrupted. · If the OT <> 2 (interface modules). In case the OT delivered by data block do not match with
the expected OT of PAM_IM, then OT = 2.
Calling OBs
The PAM_IM block is instantiated during diagnostics screen generation in OB35. The block coordinates the FB_GET operations of lower order objects. Here, the lower order block refers to PAM_SM, PAM_IM, and PAM_CD whereas, the higher order block refers to PAM_CPU.
The following parameters are automatically parametrized by the driver generator:
Parameter PLT_ID ID DBNO
Meaning
PLT-ID of SIMATIC PDM object. Netpro connection ID. Data block number configured in the "Advanced Diagnostics Settings" of Plant Hierarchy (PH).
The following output parameters are automatically connected with corresponding parameters within the lower order blocks by the driver generator:
Output parameter of PAM_CPU block
connected with I/O parameter of PAM_IM block
TOP_SI
START_UP_SI
DXCHG_xx (xx: 00...199)
TOP_SI START_UP_SI DXCHG_IN
If the processing of Process Value for the corresponding PAM object is enabled in "Advanced Diagnostic Settings" dialog of PH, the following connections are automatically created by the driver generator:
Output parameter of PAM_CPU block
DXCHG_PAM
connected with I/O parameter of PAM_IF block DXCHG_PAM
Error handling
The values of I/Os QERR and ERR_NUM are independent of each other. The value of QERR = 1 represents a runtime error. The ERR_NUM I/O is used to obtain the following errors in output:
Error number -1 0
Meaning Predefined value when inserting the block; block is not processed. There is no error.
410
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.74 PAM_IM: Monitoring Interface Modules within the Package Unit
Error number 1
2 3 4 5
6
Meaning Connection problems, for example: · Connection is not established. · Connection establishment is in progress. · No availability of information regarding connection status. · Connection is not configured. Negative acknowledgement from the partner device. The function can- not be executed. Access error on the partner CPU. Errors in the receive area pointers RD_i involving the data length or the data type. No instance data block found. · Access to the local user memory is not possible (for example, access
to a deleted data block). · S7-400: Not enough work memory is available. If there is still enough
total work memory available, then the solution is to compress the work memory.
OT number is not equal to 2.
Startup characteristics The PAM_IM block initializes the instances of ALARM_8P and NOTIFY_8P . Once the startup for the number of cycles is set at RunUpCyc, the messages are suppressed.
Modes
The following modes are available for operators in the faceplate to initiate or select an operation: · On · Passivated · Out of service On The following actions occur in this mode: · processing of messages (for example: alarms). · processing of MS, MS_Ext, and signal states. Passivated The following actions occur in this mode: · processing of MS, MS_Ext, and signal states but without any impact on MS. · setting the value of MS_OUT to 16#01 (to denote the "passivated" mode). The following action does not occur in this mode: · processing of messages (for example: alarms).
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
411
Family: @System 6.74 PAM_IM: Monitoring Interface Modules within the Package Unit
Out of service The following actions occur in this mode: · setting the value of MS_OUT = 16#02 (to denote "out of service" mode). · processing of analog values PVx.Value = 0, PVx_ST=16#80. · disabling the display of DIAG_GB / DIAG_DD parameter in "Binary details diagnose view" of
faceplate. The value of DIAG_GB / DIAG_DD is set to 0. The following actions do not occur in this mode: · processing of messages (for example: alarms). · processing of MS, MS_Ext, and signal states. In the "Monitoring View", all the information is displayed in grey.
Time response Not available
Additional information For additional information, refer to the sections: Messages and associated values of PAM_IM (Page 415) I/Os of PAM_IM (Page 412)
See also
Description of PAM_IF (Page 505)
6.74.2
I/Os of PAM_IM
The factory setting of the block display in the CFC is identified in the "I/O" column:
I/O name bold = I/O visible, I/O name normal = I/O not visible.
You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15)".
Input parameters
I/O Parameter PLT_ID MS MS2 EV_ID1 EV_ID2
Meaning
Type
Asset ID for EDD Maintenance status Maintenance status 2 for OS operations Message number 1 Message number 2
DWORD DWORD DWORD DWORD DWORD
Default
16#00000000 16#F0000008 16#00000000 16#00000000 16#00000000
412
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
I/O Parameter EN_MSG RUNUPCYC CYCL_UPD
DIAG_BUF
FEATURE ID DBNO PV_EN PVx_AH_En
PVx_DH_En
PVx_RH_En
PVx_Rst
Output parameters
I/O Parameter QERR O_MS MSG_STATx MSG_ERRx MSG_ACKx NDR1 ERROR1 STATUS1 DB_LID DB_CP DB_OT RESERVE_00 DIAG_GB DIAG_DD DIAG_ST RESERVE_01 SM_NOK1 SM_NOK2 ERR_NUM P_PVx_Rst
Family: @System 6.74 PAM_IM: Monitoring Interface Modules within the Package Unit
Meaning
Type
1 = Enable message
Number of Run Up Cycles
1 = Cyclic update active (preselection for FB first run or CPU restart)
Entry in diagnostic buffer (relevant for maintenance personnel)
Feature parameter
Netpro connection ID
Data block number
1 = Enable process value
1=Enable maintenance alarm process value x (x: 0...2)
1=Enable maintenance demand process value x (x: 0...2)
1=Enable maintenance request process value x (x: 0...2)
Reset process value x(x: 0...2)
BOOL INT BOOL
BOOL
WORD WORD WORD BOOL BOOL
BOOL
BOOL
BOOL
Default
1 1 1
1
16#0000 16#0000 16#0000 1 1
1
1
1
Meaning
1 = Runtime error Maintenance state Message status x (x:1...2) Message error x (x: 1...2) Message acknowledgement x (x:1) SFB14 New data received 1 SFB14 Error 1 SFB14 Status number 1 LID Connection point Object type Reserve Global part Detail diagnosis Status information Reserve Signal module status 0...31 Signal module status 31...63 Error number 1=Reset process value x (x: 0...2)
Type
BOOL DWORD WORD WORD WORD BOOL BOOL WORD STRING(64) STRING(64) INT DWORD WORD WORD BYTE WORD DWORD DWORD INT STRUCT
Default
1 16#08000000 16#0000 16#0000 16#0000 1 1 1 `' `' 1 16#00000000 16#0000 16#0000 0 16#0000 16#00000000 16#00000000 1 0
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
413
Family: @System 6.74 PAM_IM: Monitoring Interface Modules within the Package Unit
I/O Parameter PVx_AH_Act
PVx_DH_Act
PVx_RH_Act
PVx_Diff
DXCHG_PAM ERROR STATUS C_CONN C_STATUS PVx
PVx_AH
PVx_DH
PVx_RH
PVx_Name PVx_Unit PVx_OpScale
UPDATE_TIME PRE_UP- DATE_TIME UP- DATE_DIFF_TIME DXCHG_xx
Meaning
Type
1=Limit maintenance alarm process val- BOOL ue x (x: 0...2)
1=Limit maintenance demand process BOOL value x (x: 0...2)
1=Limit maintenance request process value x (x: 0...2)
BOOL
Difference value to the next expected Alarm x (x: 0...2)
STRUCT
Bidirectional data exchange Channel Connection function check ERROR Connection function check STATUS Status of the corresponding connection Connection status Process value x (x: 0...2)
STRUCT (UDT283) BOOL WORD BOOL WORD STRUCT
Limit maintenance alarm process value x (x: 0...2)
Limit maintenance demand process val- ue x (x: 0...2)
Limit maintenance request process val- ue x (x: 0...2)
Text of Process value x (x:0...2)
Unit of Process value x (x:0...2)
Range of process value x (x: 0...2)
REAL
REAL
REAL
STRING[16] INT STRUCT
Time of update in ms Time of previous update in ms
DINT DINT
Time difference between present and previous update in ms
Bidirectional data exchange Channel xx (xx: 00...63)
DINT DWORD
Default
1
1
1
0 16#80 0 1 16#0000 1 16#0000 0 16#80 99.99
99.99
99.99
`' 1 0 100 0 0
0
16#00000000
In/Out parameters
I/O Parameter ACC_MODE DXCHG_IN TOP_SI START_UP_SI
Meaning
Type
1 = Accept new settings
Bidirectional data exchange Channel
Start information of the current OB
Start information of the startup OB last started
BOOL DWORD STRUCT STRUCT
Default
1 16#00000000 0 0
414
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.74 PAM_IM: Monitoring Interface Modules within the Package Unit
Additional information For additional information, refer to the section: Messages and associated values of PAM_IM (Page 415) Message Classes (Page 531)
6.74.3
Messages and associated values of PAM_IM
Assignment of message text and message class The process control messages of ALARM_8P with EV_ID1 are assigned as follows:
Message number Default message text
1
Maintenance alarm (@4W%t#PAM_IM_TXT@)
2
Communication breakdown
3
Maintenance demand
(@4W%t#PAM_IM_TXT@)
4
Maintenance request
(@4w%t#PAM_IM_TXT@)
5
Device out of order
(@4W%t#PAM_IM_TXT@)
6
7
8
Message class
PLC Process Control Message Failure PLC Process Control Message Error PLC Process Control Message Error
Preventative Maintenance Standard
PLC Process Control Message Failure
No message No message No message
The process control messages of NOTIFY_8P with EV_ID2 are assigned as follows:
Message number 1 2 3
4 5 6 7 8
Default message text
Device passivated (@1W%t#PAM_IM_TXT@) Undefined diagnostics (@1W%t#PAM_IM_TXT@) Local operation/functional check (@1W %t#PAM_IM_TXT@) Simulation (@1W%t#PAM_IM_TXT@) Configuration change (@1W%t#PAM_IM_TXT@) Process-related fault (@1W%t#PAM_IM_TXT@)
Message class Status Message - PLC Status Message - PLC Status Message - PLC
Status Message - PLC Status Message - PLC Status Message - PLC No message No message
You can find additional information in the section: Message Classes (Page 531)
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
415
Family: @System 6.75 PAM_SM: Monitoring Signal Modules within the Package Unit
6.75
PAM_SM: Monitoring Signal Modules within the Package Unit
6.75.1
Description of PAM_SM
Object name (type + number) FB 437 · I/Os of PAM_SM (Page 419)
Functions
The PAM_SM block:
· Processes the data specific to Signal Module(SM) received from the higher order block (PAM_IM).
· Processes the values from PAM_IF block that is displayed in the operator station.
It is employed only to process the data but not to retrieve any data from the signal modules of PAM unit to the automation station of the PAM unit.
How it works
The PAM_IM block creates a Maintenance Status (MS) that depends on: · MS provided by SIMATIC PDM. · External MS. · Analog values that are monitored for three limits. · Status of the analog values. Of all these events, the highest priority event is displayed in the MS.
Note The table below is valid exclusively for the MS and not for the signal status displays of the individual process values; these are created exclusively by the ST parameters. The priority is similar to the MS coding. Therefore, the following applies:the lower the value of the MS, the higher the priority.
MS via PDM
9 8 7
PVx.Value via DXCHG
PVx.Value >= PVx_AH
PVx.ST via DXCHG 16#00
MS_Ext Via DXCHG 7
Output param- eter (O_MS)
9 8 7
416
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.75 PAM_SM: Monitoring Signal Modules within the Package Unit
MS via PDM
6
5
4 3 2 1 0
PVx.Value via DXCHG PVx_AH > PVx.Value >= PVx_DH PVx_DH > PVx.Value >= PVx_RH
PVx_RH > PVx.Value
PVx.ST via DXCHG 16#68
MS_Ext Via DXCHG 6
Output param- eter (O_MS)
6
16#A4
5
5
4
16#60
3
2
1
16#28, 16#78
0
The inputs PVx.Value and PVx.ST are transfered via DXCHG with PAM_IF block. However, the source of these inputs might differ between DB or direct connection in CFC (Link).
When you click the "Reset" button in the faceplate a reset impulse is available at the corresponding output of the PAM_IF block for one cycle.After one successful cycle, the reset value is set back to 0 in PAM_CD and the information is transferred to PAM_IF block.
In the case of "Communication breakdown", the SM_NOKx (transferred via DXCHG_PAM_IM I/O parameter) Information is not processed.
Calling OBs
The PAM_SM block is instantiated during diagnostics screen generation in OB35. The block coordinates the FB_GET operations of lower order objects. Here, the lower order block refers to PAM_SM, PAM_IM, and PAM_CD whereas, the higher order block refers to PAM_CPU.
The following parameters are automatically parametrized by the driver generator:
Parameter PLT_ID
Value PLT-ID of SIMATIC PDM object.
The following output parameters are automatically connected with corresponding parameters within the lower order blocks by the driver generator:
Output parameter of PAM_CPU block
TOP_SI
START_UP_SI
DXCHG_xx (xx: 00...199)
connected with I/O parameter of PAM_SM block
TOP_SI START_UP_SI DXCHG_IN
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
417
Family: @System 6.75 PAM_SM: Monitoring Signal Modules within the Package Unit
The following connections between the PAM_SM and PAM_IM blocks are automatically created by the driver generator:
Output parameter of PAM_IM block
connected with I/O Parameter of PAM_SM block
DXCHG_xx (xx: 00...63)
DXCHG_PAM_IM
If the processing of Process Value for the corresponding PAM object is enabled in "Advanced Diagnostic Settings" dialog of PH, the following connections are automatically created by the driver generator:
Output parameter of PAM_IM block
DXCHG_PAM
connected with I/O parameter of PAM_IF block DXCHG_PAM
Error handling
The values of I/Os QERR and ERR_NUM are independent of each other. The value of QERR = 1 represents a runtime error. The ERR_NUM I/O is used to obtain the following errors in output:
Error number -1 0 6
Meaning of the error number Predefined value when inserting the block; block is not processed. There is no error. OT number is not equal to 3.
Startup characteristics The PAM_SM block initializes the instances of ALARM_8P and NOTIFY_8P . Once the startup for the number of cycles is set at RunUpCyc, the messages are suppressed.
Modes
The following modes are available for operators in the faceplate to initiate or select an operation: · On · Passivated · Out of service On The following actions occur in this mode: · processing of messages (for example: alarms). · processing of MS, MS_Ext, and signal states. Passivated
418
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.75 PAM_SM: Monitoring Signal Modules within the Package Unit
The following actions occur in this mode: · processing of MS, MS_Ext, and signal states but without any impact on MS. · setting the value of MS_OUT to 16#01 (to denote the "passivated" mode). The following action does not occur in this mode: · processing of messages (for example: alarms). Out of service The following actions occur in this mode: · setting the value of MS_OUT = 16#02 (to denote "out of service" mode). · processing of analog values PVx.Value = 0, PVx_ST=16#80. · disabling the display of DIAG_GB / DIAG_DD parameter in "Binary details diagnose view" of
faceplate. The value of DIAG_GB / DIAG_DD is set to 0. The following actions do not occur in this mode · processing of messages (for example: alarms). · processing of MS, MS_Ext, and signal states. · FB_GET operations. In the "Monitoring View", all the information is displayed in grey.
Time response Not available
Additional information For additional information, refer to the sections: Messages and associated values of PAM_SM (Page 421) I/Os of PAM_SM (Page 419)
6.75.2
I/Os of PAM_SM
The factory setting of the block display in the CFC is identified in the "I/O" column:
I/O name bold = I/O visible, I/O name normal = I/O not visible.
You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15)".
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
419
Family: @System 6.75 PAM_SM: Monitoring Signal Modules within the Package Unit
Input parameters
I/O Parameter PLT_ID MS MS2 EV_ID1 EV_ID2 EN_MSG RUNUPCYC CYCL_UPD
DIAG_BUF
FEATURE PV_EN PVx_AH_En
PVx_DH_En
PVx_RH_En
PVx_Rst
Meaning
Type
Asset ID for EDD
Maintenance status
Maintenance status 2 for OS operations
Message number 1
Message number 2
1 = Enable message
Number of Run Up Cycles
1 = Cyclic update active (preselection for FB first run or CPU restart)
Entry in diagnostic buffer (relevant for maintenance personnel)
Feature parameter
1 = Enable process value
1=Enable maintenance alarm process value x (x: 0...2)
1=Enable maintenance demand process value x (x: 0...2)
1=Enable maintenance request process value x (x: 0...2)
Reset process value x(x: 0...2)
DWORD DWORD DWORD DWORD DWORD BOOL INT BOOL
BOOL
DWORD BOOL BOOL
BOOL
BOOL
BOOL
Output parameters
I/O Parameter QERR O_MS MSG_STATx
MSG_ERRx MSG_ACKx SM_NOK ERR_NUM P_PVx_Rst Vx_AH_Act
PVx_DH_Act
PVx_RH_Act
PVx_Diff
Meaning
Type
1 = Runtime error Maintenance state Message status x (x:1...2)
BOOL DWORD WORD
Message error x (x: 1...2)
WORD
Message acknowledgementx (x:1)
WORD
Signal module status
BOOL
Error number
INT
1=Reset process value x (x: 0...2)
STRUCT
1=Limit maintenance alarm process val- BOOL ue x (x: 0...2)
1=Limit maintenance demand process BOOL value x (x: 0...2)
1=Limit maintenance request process value x (x: 0...2)
BOOL
Difference value to the next expected Alarm x (x: 0...2)
STRUCT
Default
16#00000000 16#F0000008 16#00000000 16#00000000 16#00000000 1 1 1
1
16#00000000 1 1
1
1
1
Default
1 16#080000000 16#0000
16#0000 16#0000 1 1 0 1
1
1
0 16#80
420
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
I/O Parameter DXCHG_PAM PVx
PVx_AH
PVx_DH
PVx_RH PVx_Name PVx_Unit PVx_OpScale
Family: @System 6.75 PAM_SM: Monitoring Signal Modules within the Package Unit
Meaning
Type
Default
Bidirectional data exchange Channel Process value x (x: 0...2)
STRUCT (UDT283) STRUCT
Limit maintenance alarm process value x REAL (x: 0...2)
0 0 16#80 99.99
Limit maintenance demand process val- REAL ue x (x: 0...2)
99.99
Limit maintenance request process val- ue x (x: 0...2)
Text of Process value x (x:0...2)
Unit of Process value x (x:0...2)
Range of process value x (x: 0...2)
REAL
STRING[16] INT STRUCT
99.99
`' 1 0 100
In/Out parameters
I/O Parameter ACC_MODE TOP_SI START_UP_SI
DXCHG_PAM_IM
Meaning
Type
1 = Accept new settings
Start information of the current OB
Start information of the startup OB last started
Bidirectional data exchange Channel
BOOL STRUCT STRUCT
DWORD
Default
1 0 0
16#00000000
6.75.3
Messages and associated values of PAM_SM
Assignment of message text and message class The process control messages of ALARM_8P with EV_ID1 are assigned as follows:
Message number Default message text
1
Maintenance alarm (@4W%t#PAM_SM_TXT@)
2
3
Maintenance demand (@4W%t#PAM_SM_TXT@)
4
Maintenance request (@4W%t#PAM_SM_TXT@)
5
Device out of order (@4W%t#PAM_SM_TXT@)
Message class
PLC Process Control Message Failure
No message
PLC Process Control Message Error
Preventative Maintenance Standard
PLC Process Control Message Failure
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
421
Family: @System 6.76 PDM_MS: Monitoring of the maintenance status
Message number 6 7 8
Default message text
Message class No message No message No message
The process control messages of NOTIFY_8P with EV_ID2 are assigned as follows:
Message-number 1 2 3
4 5 6 7 8
Default message text
Device passivated (@1W%t#PAM_SM_TXT@) Undefined diagnostics (@1W%t#PAM_SM_TXT@) Local operation/functional check (@1W %t#PAM_SM_TXT@) Simulation (@1W%t#PAM_SM_TXT@ Configuration change (@1W%t#PAM_SM_TXT@) Process-related fault (@1W%t#PAM_SM_TXT@)
Message class Status Message - PLC Status Message - PLC Status Message - PLC
Status Message - PLC Status Message - PLC Status Message - PLC No message No message
You can find additional information in the section: Message Classes (Page 531)
6.76
PDM_MS: Monitoring of the maintenance status
6.76.1
Description of PDM_MS
Object name (type + number) FB 81 · I/Os of PDM_MS (Page 422)
How it works
The block reports the maintenance state supplied by PDM via the maintenance station.
Additional information
You can find additional information in the section: Message texts and associated values of PDM_MS (Page 423).
6.76.2
422
I/Os of PDM_MS
The factory setting of the block display in the CFC is identified in the "I/O" column: I/O name bold = I/O visible, I/O name normal = I/O not visible.
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.76 PDM_MS: Monitoring of the maintenance status
You can find explanations and the meaning of abbreviations in the section: General Information About Block Description (Page 15).
Input parameters
I/O (parame- ter) DIAG_BUF
EN EN_MSG EV_IDx FEATURE MS MS2 RUNUPCYC CYCL_UPD
Meaning
Entry in diagnostic buffer (relevant for maintenance personnel)
1 = enable message Message number (x = 1, 2) Reserve Maintenance status Maintenance status 2 for OS operations Number of replacement run cycles 1 = Cyclic update active (preselection for FB first run or CPU restart)".
Type
BOOL
BOOL BOOL DWORD DWORD DWORD DWORD INT BOOL
Default
0
1 1 0 16#00000000 0 16#00000000 3 1
Output parameters
I/O (parameter) MSGSTATx O_MS QERR
Meaning Message error information (x = 1, 2) Maintenance status 1 = program error
Type WORD DWORD BOOL
Default 0 0 1
Additional information Additional information is available in the section: Message texts and associated values of PDM_MS (Page 423)
6.76.3
Message texts and associated values of PDM_MS
Messaging
The statuses are generated with ALARM_8P for messages requiring acknowledgment, and with NOTIFY_8P for those not requiring acknowledgment. The message function can be disabled by setting EN_MSG = 0. In this case MS = 8 is set.
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
423
Family: @System 6.76 PDM_MS: Monitoring of the maintenance status
Assignment of message text and message class The process control messages of ALARM_8P with EV_ID1 are assigned as follows:
Message block ALARM_8P
EV_ID1
Message number
1
2 3
4
5
6 7 8
Default message text
Maintenance alarm
Maintenance demanded Maintenance required Device out of order
Message class
PLC Process Control Message Failure No message PLC Process Control Message Error Preventative Maintenance Standard PLC Process Control Message Failure No message No message No message
The process control messages of ALARM_8P with EV_ID2 are assigned as follows:
Message block NOTIFY_8P
EV_ID2
Message number Default message text
1
Device passivated
2
Undefined diagnostics
3
Local operation/functional check
4
Simulation
5
Configuration change
6 7 8
Message class
Status Message PLC Status Message PLC Status Message PLC Status Message PLC Status Message PLC No message No message No message
Additional information You can find additional information in the section: Message Classes (Page 531)
424
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
6.77
Family: @System 6.77 PNTS2BCD: Converts PNIO time to BCD format
PNTS2BCD: Converts PNIO time to BCD format
6.77.1
Description of PNTS2BCD
The PNTS2BCD function converts the PNIO Time-stamp to BCD Format and delivers the values in the Output parameter TS_x.
Object name (type + number) FC 266 · I/Os of PNTS2BCD (Page 425)
Area of application This block is a system block and is used exclusively internally.
6.77.2
I/Os of PNTS2BCD
The factory setting of the block display in the CFC is identified in the "I/O" column:
I/O name bold = I/O visible, I/O name normal = I/O not visible.
You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15)".
Input parameters
I/O (parameter)
Meaning
PNIO_TS_Status
Status of PNIO Timestamp
PNIO_TS_SecondsHigh Seconds of PNIO Timestamp
(> 136 Years)
PNIO_TS_SecondsLow Seconds of PNIO Timestamp
(< 136 Years)
PNIO_TS_Nanoseconds Nanoseconds of PNIO Timestamp
Data type Default
WORD
0
WORD
0
DWORD 0
DWORD 0
Output parameters
I/O (parameter) TS_0 TS_1 TS_2 TS_3
Meaning
Years Month Date Hour
Data type Default
BYTE
0
BYTE
0
BYTE
0
BYTE
0
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
425
Family: @System 6.78 PNTS2DT: Converts PNIO time to DT format
I/O (parameter)
TS_4 TS_5 TS_6 TS_7 ErrNum
Meaning
Minutes Seconds 2 MSB of milliseconds LSB of millisecond and Day of week Error Number (0 = No error)
Data type Default
BYTE
0
BYTE
0
BYTE
0
BYTE
INT
-1
6.78
PNTS2DT: Converts PNIO time to DT format
6.78.1
Description of PNTS2DT
The PNTS2DT function converts the PNIO Time-stamp to DT Format and delivers the below mentioned values for the display in the Exit parameter PNTS_DT_DeltaTriggerDiscrete etc... for the various RS Alarm types.
Object name (type + number) FC 261 · I/Os of PNTS2DT (Page 426)
Area of application This block is a system block and is used exclusively internally.
6.78.2
I/Os of PNTS2DT
The factory setting of the block display in the CFC is identified in the "I/O" column:
I/O name bold = I/O visible, I/O name normal = I/O not visible.
You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15)".
Input parameters
I/O (parameter) PNIO_TS_Status PNIO_TS_Second- sHigh
Meaning
Status of PNIO Timestamp Seconds of PNIO Timestamp (> 136 Years)
Data type Default
WORD
0
WORD
0
426
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.79 PNTS2ISP: Converts PNIO time to ISP format
I/O (parameter)
Meaning
PNIO_TS_SecondsLow Seconds of PNIO Timestamp
(< 136 Years)
PNIO_TS_Nanosec- onds
Nanoseconds of PNIO Timestamp
Data type Default DWORD 0 DWORD 0
Output parameters
I/O (parameter) Years Month Day Hour Minutes Seconds Milliseconds ErrNum
Meaning
Years Month Date Hour Minutes Seconds Milliseconds Error Number (0 = No error)
Data type Default
INT
0
INT
0
INT
0
INT
0
INT
0
INT
0
INT
0
INT
-1
6.79
PNTS2ISP: Converts PNIO time to ISP format
6.79.1
Description of PNTS2ISP
The PNTS2ISP function converts the PNIO timestamp into ISP Format and delivers the values in the Output Parameter TS_x.
Object name (type + number) FC 264 · I/Os of PNTS2ISP (Page 427)
Area of application This block is a system block and is used exclusively internally.
6.79.2
I/Os of PNTS2ISP
The factory setting of the block display in the CFC is identified in the "I/O" column: I/O name bold = I/O visible, I/O name normal = I/O not visible.
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
427
Family: @System 6.80 PO_UPDAT: Output Process Image
You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15)".
Input parameters
I/O (parameter)
Meaning
PNIO_TS_Status
Status of PNIO Timestamp
PNIO_TS_Second- sHigh
Seconds of PNIO Timestamp (> 136 Years)
PNIO_TS_SecondsLow Seconds of PNIO Timestamp
(< 136 Years)
PNIO_TS_Nanosec- onds
Nanoseconds of PNIO Timestamp
Data type Default
WORD
0
WORD
0
DWORD 0
DWORD 0
Output parameters
I/O (parameter) TS_0 TS_1 TS_2 TS_3 TS_4 TS_5 TS_6 TS_7 ErrNum
Meaning
Seconds - Bit 31 ... 24 Seconds - Bit 23 ... 16 Seconds - Bit 15 ... 8 Seconds - Bit 7 ... 0 Part of milliSeconds in 1 / 2^32 - Bit 31 ... 24 Part of milliSeconds in 1 / 2^32 - Bit 23 ... 16 Part of milliSeconds in 1 / 2^32 - Bit 15 ... 8 Part of milliSeconds in 1 / 2^32 - Bit 7 ... 0 Error Number (0=No error)
Data type Default
BYTE
0
BYTE
0
BYTE
0
BYTE
0
BYTE
0
BYTE
0
BYTE
0
BYTE
0
INT
-1
6.80
PO_UPDAT: Output Process Image
6.80.1
PO_UPDAT: Output Process Image
Object name (type + number) FC 279
Area of application
The PO_UPDAT block safeguards the output module functions "Hold last value" and "Apply substitute value" when a CPU is restarted (OB 100).
428
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.81 PS: Power supply monitoring
Run Sequence
With the "Generate module drivers" CFC function, the PO_UPDAT block is automatically installed in OB 100 at the end.
Description of Functions
On a CPU restart (OB 100), the CH_DO and CH_AO blocks write the start values to the process image. The PO_UPDAT block sends all process images (partitions) to the modules at the end of OB 100 in order for these values to be active immediately when the CPU goes into RUN. Output PO_MAP indicates the process image partitions which have been updated or are used in the system (BIT0: Process image 0, BIT15: Process image partition 15).
6.81
PS: Power supply monitoring
6.81.1
Description of PS
Object name (type + number) FB 89 · PS block I/Os (Page 431)
Area of application The PS block monitors the status of a rack power supply, and reports the associated error events.
Calling OBs
The PS block must be installed in the run sequence of the following OBs:
OB 1 OB 81 OB 83 OB 100
Cyclic program Power supply error Remove/insert interrupt Warm restart
Use in CFC
The following actions are executed automatically with the "Generate module drivers" CFC function:
· The block is installed in the run sequence downstream of the RACK block.
· The SLOT_NO input (slot number of the power supply) is configured.
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
429
Family: @System 6.81 PS: Power supply monitoring
· The EN input is interconnected with the output of an AND block. Its inputs are interconnected with the output EN_SUBx of the OB_BEGIN block, the output EN_Rxxx of the SUBNET block and the output EN_Mxx of the RACK block.
· The OUT structures CPU_DIAG of the OB_BEGIN block and RAC_DIAG of the RACK block are interconnected with the IN_OUT structures of the same name of the PS block.
Function and method of operation The PS block reports events of the power supply error OB 81 and OB 83 relating to the power supply module. The module is installed to supply power to the central rack, and to each expansion rack.
Note Note the following: · If a battery fails, the battery must always be replaced with the power supply turned on. Then
press the "FMR" button. In all other situations, the block does not reset a reported error. · For redundant power supply modules in a rack with a standard CPU, a corresponding
message is sent for both power supply modules in the event of a battery error or power supply error. You can tell which module is affected by the "BATTF" LED that lights up.
Redundancy
In a redundant system, the block is also installed extra for the power supply of the redundant rack.
Error handling
The error handling of the block is limited to the evaluation of the error information of ALARM_8P. Refer to the section "Error information of output parameter MSG_STAT (Page 530)" for additional information on error handling.
Startup characteristics The PS block initializes the messages of the ALARM_8P.
Overload behavior Not available
Time response You will find additional information in the "Message response" section.
430
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.81 PS: Power supply monitoring
Message response After OB 81 or OB 83 is called, the block analyzes the status of the power supply of the rack assigned to it. It generates the "Backup battery failure", "Backup voltage failure" and "24 V supply failure" or "Module removed" or "Wrong or faulty module" messages with ALARM_8P. The message function can be disabled by setting EN_MSG = FALSE.
Operator control and monitoring If asset management is used in the project and the diagnostic screens have been generated, the faceplate can be called via its block icon. For additional information, refer to the "Process Control System PCS 7; Maintenance Station" manual.
Additional information For additional information, refer to the sections: Message texts and associated values of PS (Page 432) Maintenance status MS (Page 533)
6.81.2
I/Os of PS
The factory setting of the block display in the CFC is identified in the "I/O" column: I/O name bold = I/O visible, I/O name normal = I/O not visible.
You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15)".
Input parameters
I/O (parameter) DIAG_BUF
EN_MSG EV_ID MS SLOT_NO
Meaning
Data type Default
Entry in diagnostic buffer (relevant for maintenance person- BOOL
0
nel)
1 = enable message
BOOL
1
Message number
DWORD
0
Maintenance status
DWORD
0
Slot number of the power supply
BYTE
0
Output parameters
I/O (parameter) MSG_STAT O_MS
Meaning
Message error information Maintenance status
Data type Default
WORD
0
DWORD
0
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
431
Family: @System 6.81 PS: Power supply monitoring
In/out parameters
I/O (parameter) CPU_DIAG RAC_DIAG
Meaning
CPU diagnostics (system structure) System structure
Additional information For additional information, refer to the sections: Message texts and associated values of PS (Page 432) Maintenance status MS (Page 533)
Data type Default
STRUCT STRUCT
6.81.3
Message texts and associated values of PS
Message texts and associated values of PS The process control messages of ALARM_8P with EV_ID are assigned as follows:
Message No. 1
2
3 4 5 6 7 8
Default message text Station @1%d@/ @3%d@: Redundancy loss Station @2%d@/ @3%d@: Redundancy loss Station @1%d@/ @3%d@: Failure Station @2%d@/ @3%d@: Failure
Station @1%d@/ @3%d@: Multiple fail- ure
Message class PLC Process Control Message - Error
PLC Process Control Message - Error
PLC Process Control Message - Failure PLC Process Control Message - Failure No message No message No message PLC Process Control Message - Failure
Associated values of ALARM_8P with EV_ID:
Associated value
1 2 3
Block parameters
ID of the primary DP master system (SUBN1_ID) ID of the redundant DP master system (SUBN2_ID) Rack/station number (RACK_NO)
See also
Message Classes (Page 531)
432
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
6.82
RACK: Rack monitoring
Family: @System 6.82 RACK: Rack monitoring
6.82.1
Description of RACK
Object name (type + number) FB 107 · RACK block I/Os (Page 436)
Area of application The RACK block monitors the status of a rack, and reports the associated error events.
Calling OBs
The block is installed in the run sequence in the following OBs:
OB 1 OB 70 OB 72 OB 81 OB 82 OB 83 OB 85 OB 86 OB 100
Cyclic program I/O redundancy error CPU redundancy error Power supply error Diagnostic interrupt Insert/remove module interrupt Program execution error Rack failure Warm restart
Use in CFC
The following actions are executed automatically with the "Generate module drivers" CFC function:
· The RACK block is installed in the run sequence downstream of the SUBNET block.
· The RACK_NO, DADDR, SUBN1_ID, SUBN2_ID, and SUBN_TYP inputs are configured.
· The EN input is interconnected with the output of an AND block. whose inputs are interconnected to the EN_SUBx output of the OB BEGIN block, and to the EN_Rxxx output of the SUBNET block.
· The CPU_DIAG OUT structure of the OB_BEGIN block and SUB_DIAG of the SUBNET block are interconnected with the IN_OUT structures of the same name of the RACK block.
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
433
Family: @System
6.82 RACK: Rack monitoring
Function and method of operation
The RACK block generates a process control error message for the OS in the event of redundancy losses and rack/station failures. It also indicates internal errors of the rack/station (SUBN1ERR, SUBN2ERR), and of the preferred channel (SUBN1ACT, SUBN2ACT) if there are active DP slaves at its outputs. The output structure RAC_DIAG contains the geographic address of the rack, and the group error information RACK_ERR. If RACK_ERR = 1, the corresponding rack is not available.
The block is installed in the OBs listed above once at each station or local I/O device. The SUBNET block enables the runtime group that contains the RACK block. Start and diagnostic information is read from the CPU_DIAG IN_OUT structure, which is interconnected with the CPU_DIAG structure of the OB_BEGIN block. The RACK block has one enable output for each rack (station) slot.
The RACK block generates the number of a corresponding message (see "Message Response") on the basis of the start information of the calling OBs if the current block is affected.
The block evaluates error events, and uses the diagnostic address DADDR of the DP slave to determine the currently active preferred channel (SUBN1ACT, SUBN2ACT) of redundant PROFIBUS DP interface circuits.
Note: If you want to change the SUBN1_ID (connection to CPU 0) and SUBN2_ID (connection to CPU 1) inputs online, you must set input ACC_ID = TRUE. to update the output values.
Redundancy
In H systems with distributed I/Os, the RACK block supports redundancy of the DP Master systems. If you want to use this function, you must configure the SUBN1_ID (connection to CPU 0) and SUBN2_ID (connection to CPU 1) inputs of the RACK block with the numbers of the redundant DP master systems. If there is no redundancy, the remaining input must be set to the (default) value 16#FF.
Note
With redundant CPU racks, the two RACK blocks inserted in the system chart are only responsible for enabling lower-level block chains. Their maintenance status MS is therefore irrelevant. The "Good" and "Not redundant" state is always shown in the associated faceplate and block icon because the bits 0 to 16 of the MS are always "0" in this case.
Error handling
Error handling for the block is limited to the evaluation of the error information of ALARM_8P.
You will find additional information about this in "Error information of output parameter MSG_STAT (Page 530)".
Startup characteristics
The RACK block initializes ALARM_8P messages. It checks availability of the station and, in H systems, determines the preferred channel of the station.
434
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.82 RACK: Rack monitoring
The SUB_DIAG.V1_MODE structure (0 = compatibility mode, 1 = DPV1 mode) is transferred to the RAC_DIAG.V1_MODE structure.
Overload behavior
The RACK block counts the OB 86 calls (except in the case of a DP master system failure; see SUBNET block). The counter is reset in OB1. If more than two OB 86 events occur in succession before the cycle control point (OB 1) is reached, these will be rejected and the message "Station...: Multiple failure" is output. When an OB 86 call is rejected, the rack (station) is registered as having failed.
Time response See "Message Response"
Message response
After it is called by OB 70, OB 72, OB 85 or OB 86, the block analyzes the status of its assigned CPU, DP master and DP slave. If the rack (station) loses redundancy or fails, the block outputs the corresponding messages by broadcasting an ALARM_8P. The message function can be disabled by setting EN_MSG = FALSE.
The block generally reports only the events that were originally generated in the rack that it monitors. Redundancy loss and station failures which are caused by the failure of a DP master or CPU are initially neither signaled nor indicated at the SUBN1ERR and SUBN2ERR outputs.
The DELAY input is used to delay the outputting of error messages for an outgoing, higherpriority error. For example, if the RACK block recognizes an outgoing error at an interconnected DP master, it initially assumes that there is a faulty assigned DP slave in the rack it monitors, and sets the corresponding output SUBNxERR. The error status is not reset until the DP slave returns (in this case: OB 86, OB 70). The RACK blocks suppress the potential slave failure states for DELAY seconds so as not to trigger a surge of messages from DP slaves which are not yet synchronized when the master returns. An error message is only output to the OS when the DP slave has not reported its return before this delay time has expired.
Note: Do not set the value of DELAY too high, since messages reporting faulty DP slaves or their removal during a master failure will be output too late to the OS after the DP master returns.
The RACK block generates the following messages in the OBs listed below:
OB OB 1 OB 70 OB 81 OB 85 OB 86 OB 100
Start event Cyclic processing Redundancy loss Power supply error Program execution error Rack failure Restart
Message Repeat the update of ALARM_8P outputs/messages, if necessary Station redundancy loss/return
Station failure, incoming/outgoing Station failure, incoming/outgoing Initialization of ALARM_8P
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
435
Family: @System 6.82 RACK: Rack monitoring
Operator control and monitoring If asset management is used in the project and the diagnostic screens have been generated, the faceplate can be called via its block icon. For additional information, refer to the "Process Control System PCS 7; Maintenance Station" manual.
Additional information For additional information, refer to the sections: Message texts and associated values of RACK (Page 437) Maintenance status MS (Page 533)
6.82.2
I/Os of RACK
The factory setting of the block display in the CFC is identified in the "I/O" column: I/O name bold = I/O visible, I/O name normal = I/O not visible.
You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15)".
Input parameters
I/O (parameter) DADDR DIAG_BUF
DELAY EN_MSG EV_ID MS RACK_NO SUBN_TYP SUBN1_ID SUBN2_ID
Meaning
Data type Default
Diagnostic address of the DP slave
INT
0
Entry in diagnostic buffer (relevant for maintenance person- BOOL
0
nel)
Interrupt delay (s)
INT
15
1 = enable message
BOOL
1
Message number
DWORD
0
Maintenance status
DWORD
0
Rack number
BYTE
0
1 = external DP interface
BOOL
0
ID of the primary DP master system
BYTE
255
ID of the redundant DP master system
BYTE
255
Output parameters
I/O (parameter) EN_Mxx MSG_STAT O_MS QRACKF
Meaning
1 = Enable module xx (xx = 0 - 63) Message error information Maintenance status 1 = higher-level error
Data type Default
BOOL
0
WORD
0
DWORD
0
BOOL
0
436
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
I/O (parameter)
RAC_DIAG SUBN1ACT SUBN1ERR SUBN2ACT SUBN2ERR
Meaning
System structure 1 = Slave 1 is active 1 = Error in slave 1 1 = Slave 2 is active 1 = Error in slave 2
In/out parameters
I/O (parameter) ACC_ID CPU_DIAG SUB_DIAG
Meaning
1 = accept MODE settings CPU diagnostics (system structure) OB start information
Additional information For additional information, refer to the sections: Message texts and associated values of RACK (Page 437) Maintenance status MS (Page 533)
Family: @System 6.82 RACK: Rack monitoring
Data type Default
STRUCT
BOOL
0
BOOL
0
BOOL
0
BOOL
0
Data type Default
BOOL
0
STRUCT
STRUCT
6.82.3
Message texts and associated values of RACK
Assignment of message text and message class
Message no. 1
2
3
4
5 6 7 8
Default message text Station @1%d@/ @3%d@: Redundancy loss Station @2%d@/ @3%d@: Redundancy loss Station @1%d@/ @3%d@: Failure
Station @2%d@/ @3%d@: Failure
Station @1%d@/ @3%d@: Multiple fail- ure
Message class PLC Process Control Message - Error
PLC Process Control Message - Error
PLC Process Control Message - Fail- ure PLC Process Control Message - Fail- ure No message No message No message PLC Process Control Message - Fail- ure
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
437
Family: @System 6.83 RACK_CFU: PROFINET CFU function block
Assignment of associated values
Associated value 1 2 3
Block parameters ID of the primary DP master system (SUBN1_ID) ID of the redundant DP master system (SUBN2_ID) Rack/station number (RACK_NO)
See also
Message Classes (Page 531)
6.83
RACK_CFU: PROFINET CFU function block
6.83.1
Description of RACK_CFU
Object name (type + number) FB 425 · I/Os of RACK_CFU (Page 439)
Area of application
The RACK_CFU block monitors the status of a CFU unit, and reports the associated error events and releases the downstream spur blocks when they are affected.
Configuration
The following actions are executed automatically with the "Generate module drivers" CFC function:
· The RACK_CFU block is installed in the run sequence downstream of the SUBNET_PN block.
· The RACK_NO, DADDR, SUBN1_ID, SUBN2_ID, and SUBN_TYP inputs are configured.
· The EN input is interconnected with the output of an AND block. whose inputs are interconnected to the EN_SUBx output of the OB BEGIN_HPN block, and to the EN_Rxxx output of the SUBNET_PN block.
· The CPU_DIAG_PN OUT structure of the OB_BEGIN_HPN block and SUB_DIAG of the SUBNET_PN block are interconnected with the IN_OUT structures of the same name of the RACK_CFU block.
Startup characteristics
The RACK_CFU block initializes ALARM_8P messages. It checks availability of the station, and in H systems, determines the preferred channel of the station.
438
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.83 RACK_CFU: PROFINET CFU function block
Error handling Error handling for the block is limited to the evaluation of the error information of ALARM_8P.
Block functions The RACK_CFU block generates a process control error message for the OS in the event of connection losses and rack/station failures. It also indicates internal errors of the rack/station (SUBN1ERR, SUBN2ERR(FALSE for S1/S2 header)), and of the preferred channel (SUBN1ACT, SUBN2ACT (FALSE for S1/S2 header)) if there are active PN slaves at its outputs. The output structure RAC_DIAG contains the geographic address of the rack, and the group error information RACK_ERR. If RACK_ERR = 1, the corresponding rack is not available. The block is installed in the OBs (OB1, OB70, OB72, OB81, OB82, OB83, OB85, OB86, OB100) once at each station or local I/O device. The SUBNET_PN block enables the runtime group that contains the RACK_CFU block. Start and diagnostic information is read from the CPU_DIAG_PN IN_OUT structure, which is interconnected with the CPU_DIAG_PN structure of the OB_BEGIN_HPN block. The RACK_CFU block has one enable output for each rack (station) slot. The RACK_CFU block generates the number of a corresponding message on the basis of the start information of the calling OBs if the current block is affected.
Additional information Additional information is available in the section: Message texts and associated values of RACK_CFU (Page 441)
6.83.2
I/Os of RACK_CFU
The factory setting of the block display in the CFC is identified in the "I/O" column:
I/O name bold = I/O visible, I/O name normal = I/O not visible.
You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15)".
Input parameters
I/O (parameter) DADDR DADDR_DIDO DADDR_PA_M DELAY DIAG_BUF
EN_MSG
Meaning
Diagnose address of PN-IO device Diagnostic Address of DI-DO Slot Diagnostic Address of PA Master Alarm delay (s) 1= CPU Diagnostic Buffer entry on (relevant for service personnel) 1 = Message enable
Data type Default
INT
0
INT
0
INT
0
INT
15
BOOL
0
BOOL
1
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
439
Family: @System 6.83 RACK_CFU: PROFINET CFU function block
I/O (parameter) EV_ID
EV_ID1
FEATURE PN_REDUNDANCY_LEV- EL MODE_xx MS MS_REQ PNIO_ADR PORT1_ADR PORT1_CONNECT PORT2_ADR PORT2_CONNECT RACK_NO SUBN_TYP SUBN1_ID SUBN2_ID
Meaning
Message number ALARM_8P (configured by ES) Message number ALARM_8P (configured by ES) Features of hardware (reserve) PN redundancy level S1=16#1; S2=16#2; R1=16#4; R2=16#8 MODE parameter (xx: 00-15) Maintenance status Maintenance Release Request Diagnostic address of PN-IO Interface Diagnostic address of PORT1 Port1 connection status Diagnostic address of PORT2 Port2 connection status Rack number 1 = External PN interface PN-IO System 1 ID (100 115) PN-IO System 2 ID (100 115)
Data type
DWORD
DWORD
WORD BYTE
DWORD DWORD BOOL INT INT BYTE INT BYTE BYTE BOOL BYTE BYTE
Default
0
0
0 0
0 0 0 0 0 0 0 0 0 0 255 255
Output parameters
I/O (parameter)
CH_EXIST CH_ACTIVE CH_OK DIAG_INF DIAG_INF_DI_DO DIAG_INF_PA_M DXCHG_xx DXCHG1_xx EN_Mxx EXT_STAT EXT_STAT_A FS_ACTIVE MS_XCHG_xx MSGSTATx MSG_ACKx OMODE_xx O_MS O_MS_x
Meaning
Channel exist Channel active Channel OK Diagnostic information Diagnostic information Diagnostic information Data exchange Data exchange 1 = Enable module (xx = 0 63) Extended status Extended status Flutter suppress active MS exchange (xx: 0..15) STATUS of ALARM_8P_x (x = 1 2) ACK of ALARM_8P_x (x = 1 2) Mode channel xx (xx: 0..15) Maintenance status Maintenance status (x=0..15) of device
Data type
DWORD DWORD DWORD STRUCT STRUCT STRUCT DWORD DWORD BOOL DWORD DWORD DWORD DWORD WORD WORD DWORD DWORD DWORD
Default
0 0 0
0 0 0 0 0 0 0 0 0 0 0 0
440
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.83 RACK_CFU: PROFINET CFU function block
I/O (parameter)
PA_DIAG_x QERR QMSGERx QRACKF RAC_DIAG SUBN1ACT SUBN1ERR SUBN2ACT SUBN2ERR
Meaning
PA- Slave Diagnostic- Information 1=Runtime Error Message ERROR of ALARM_8P_x (x = 1 2) 1 = higher-level error System structure 1 = PN-IO-Device 1 active 1 = error in PN-IO device 1 1 = PN-IO-Device 2 active 1 = Error in PN-IO device 2
Data type
DWORD BOOL BOOL BOOL STRUCT BOOL BOOL BOOL BOOL
Default
0 1 0 0 -0 -0 -0 -0
In/out parameters
I/O (parameter) ACC_ID CPU_DIAG_PN SUB_DIAG
Meaning
1 = Accept MODE settings System structure: CPU diagnostics System structure: Subnet diagnostics
Data type
BOOL STRUCT STRUCT
Default
0 -
6.83.3
Message texts and associated values of RACK_CFU
Assignment of message text and message class The process control messages of ALARM_8P with EV_ID are assigned as follows:
Message num- ber
1
Default message text Station @4%d@/@3%d@: Maintenance alarm
2
Station @4%d@/@3%d@: Maintenance demanded
3
Station @4%d@/@3%d@: Maintenance required
4
Station @4%d@/@3%d@: Multiple diagnostic failure
5
6
7
Station @4%d@/@3%d@: Maintenance demanded (Extern)
8
Station @4%d@/@3%d@: Maintenance required (Extern)
Message class
PLC Process Control Message - Failure PLC Process Control Message - Error Preventative Mainte- nance - Standard PLC Process Control Message - Failure No message No message PLC Process Control Message - Error Preventative Mainte- nance - Standard
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
441
Family: @System 6.83 RACK_CFU: PROFINET CFU function block
Note · Maintenance alarm will also be reported when both ports report an error. · Maintenance demand will also be reported in the following cases:
when the device reports redundancy loss, or when only one of the ports report an error, or when the PN-IO Interface reports an error
The process control messages of ALARM_8P with EV_ID1 are assigned as follows:
Message num- ber
1
Default message text Station @4%d@/@3%d@/0: Port 1 error
2
Station @4%d@/@3%d@/0: Port 2 error
3
Station @4%d@/@3%d@/0: Maintenance demanded (PN-IO)
4
Station @4%d@/@3%d@/0: Maintenance required (PN-IO)
5 6 7 8
Message class
PLC Process Control Message - Error PLC Process Control Message - Error PLC Process Control Message - Error Preventative Mainte- nance - Standard No message No message No message No message
Associated values of ALARM_8P with EV_ID and EV_ID1:
Associated val- ue
1 2 3 4
Block parameter
Primary PN-IO system number (SUBN1_ID) Redundant PN-IO system number (SUBN2_ID) Rack number (RACK_NO) PN-IO System number
Data type
BYTE BYTE BYTE BYTE
442
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
6.84
RACK_PN: Rack monitoring
Family: @System 6.84 RACK_PN: Rack monitoring
6.84.1
Description of RACK_PN
Object name (type + number) FB 90 · I/Os of RACK_PN (Page 443)
Area of application The RACK_PN block monitors the status of a rack, and reports the associated error events.
Additional information For additional information, refer to the following sections: Message texts and associated values of RACK_PN (Page 445) Maintenance status MS (Page 533)
6.84.2
I/Os of RACK_PN
The factory setting of the block display in the CFC is identified in the "I/O" column: I/O name bold = I/O visible, I/O name normal = I/O not visible.
You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15)".
Input parameters
I/O (parameter) DADDR DELAY DIAG_BUF
EN_MSG EV_ID EV_ID1 FEATURE_01 PN_REDUNDANCY_LEV- EL MS PNIO_ADR
Meaning
Data type
Diagnostics address of the PN IO device Interrupt delay (s) Entry in diagnostic buffer (relevant for mainte- nance personnel) 1 = enable message Message number ALARM_8P (assigned by the ES) Message number ALARM_8P (assigned by the ES) Property of the hardware parameter 01 PN redundancy level S1=16#1; S2=16#2; R1=16#4; R2=16#8 Maintenance status Diagnostic address of the PN-IO interface
INT INT BOOL
BOOL DWORD DWORD WORD BYTE
DWORD INT
Default
0 15 0
1 0 0 0 0
0 0
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
443
Family: @System 6.84 RACK_PN: Rack monitoring
I/O (parameter) PORT1_ADR PORT1_CONNECT PORT2_ADR PORT2_CONNECT RACK_NO SUBN_TYP SUBN1_ID SUBN2_ID
Meaning
Diagnostic address of PORT 1 Port 1 Connection Status Diagnostic address of PORT 2 Port 2 Connection Status Rack number 1 = External PN-IO-System ID of primary PN-IO-System ID of redundant PN-IO-System
Output parameters
I/O (parameter) EN_Mxx MSGSTATx O_MS QMSGERx QRACKF RAC_DIAG SUBN1ACT SUBN1ERR SUBN2ACT SUBN2ERR
Meaning
1 = Enable rack xx (xx = 0 - 63) Status output of ALARM_8P_x (x = 1-2) Maintenance status ERROR message of ALARM_8P_x (x = 1 - 2) 1 = higher-level error System structure 1 = Slave 1 is active 1 = Error in slave 1 1 = Slave 2 is active 1 = Error in slave 2
In/out parameters
I/O (parameter) ACC_ID CPU_DIAG_PN SUB_DIAG
Meaning
1 = accept MODE settings CPU diagnostics (system structure) OB start information
Additional information For additional information, refer to the sections: Message texts and associated values of RACK_PN (Page 445) Maintenance status MS (Page 533)
Data type Default
INT
0
BYTE
0
INT
0
BYTE
0
BYTE
0
BOOL
0
BYTE
255
BYTE
255
Data type Default
BOOL
0
WORD
0
DWORD
0
BOOL
0
BOOL
0
STRUCT
BOOL
0
BOOL
0
BOOL
0
BOOL
0
Data type Default
BOOL
0
STRUCT
STRUCT
444
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
6.84.3
Family: @System 6.84 RACK_PN: Rack monitoring
Message texts and associated values of RACK_PN
Assignment of message text and message class The process control messages of ALARM_8P with EV_ID are assigned as follows:
Message number 1
2
3 4 5 6 7 8
Default message text Station @1%d@/ @3%d@: Redundancy loss Station @2%d@/ @3%d@: Redundancy loss Station @1%d@/ @3%d@: Failure Station @2%d@/ @3%d@: Failure
Station @1%d@/ @3%d@: Multiple fail- ure
Message class PLC Process Control Message - Error
PLC Process Control Message - Error
PLC Process Control Message - Failure PLC Process Control Message - Failure No message No message No message PLC Process Control Message - Failure
Associated values of ALARM_8P with EV_ID
Associated val- ue
1 2 3
Block parameter
ID of the primary PN IO system (SUBN1_ID) ID of the redundant PN IO system (SUBN2_ID) Rack/station number (RACK_NO)
Data type
BYTE BYTE BYTE
The process control messages of ALARM_8P with EV_ID1 are assigned as follows:
Message number 1 2 3
4
5 6 7 8
Default message text
Station @4%d@/ @3%d@/0: Port 1 error
Station @4%d@/ @3%d@/0: Port 2 error
Station @4%d@ @3%d@/0: Mainte- nance demanded (PN-IO)
Station @4%d@/ @3%d@/0: Mainte- nance required (PN-IO)
Message class PLC Process Control Message - Error PLC Process Control Message - Error PLC Process Control Message - Error
Preventative Maintenance - Standard
No message No message No message No message
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
445
Family: @System 6.85 RACK_PN1: PROFINET RACK Function Block - R1 Device
Associated values of ALARM_8P with EV_ID1
Associated value Block parameter
1
ID of the primary PN IO system (SUBN1_ID)
2
ID of the redundant PN IO system (SUBN2_ID)
3
Rack/station number (RACK_NO)
4
ID of the PN IO system
Data type BYTE BYTE BYTE WORD
You can find additional information in the section: Message Classes (Page 531).
6.85
RACK_PN1: PROFINET RACK Function Block - R1 Device
6.85.1
Description of RACK_PN1
Object name (type + number) FB 415 · I/Os of RACK_PN1 (Page 448)
Area of application The block RACK_PN1 monitors the status of a PN-IO rack and reports the associated error events.
Calling OBs
The block must be installed in the following OBs (performed automatically in CFC):
OB 1 OB 81 OB 82 OB 85 OB 86 OB 100
Cyclic program Power failure Diagnostic alarm Program sequence error Module failure New start (Warm start)
Configuration
The following actions are executed automatically with the "Generate module drivers" CFC function:
· The RACK_PN1 block is installed in the run sequence downstream of the SUBNET block.
· The RACK_NO, DADDR, SUBN1_ID, SUBN2_ID, and SUBN_TYP inputs are configured.
446
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.85 RACK_PN1: PROFINET RACK Function Block - R1 Device
· The EN input is interconnected with the output of an AND block, whose inputs are interconnected to the EN_SUBx output of the OB_BEGIN_HPN block, and to the EN_Rxxx output of the SUBNET block.
· The CPU_DIAG_PN OUT structure of the OB_BEGIN_HPN block and SUB_DIAG_PN of the SUBNET_PN block are interconnected with the IN_OUT structures of the same name of the RACK_PN1 block.
Startup characteristics The RACK_PN block initializes ALARM_8P messages. It checks availability of the station and, in H systems, determines the preferred channel of the station.
Error handling Error handling for the block is limited to the evaluation of the error information of ALARM_8P.
Block functions The RACK_PN1 block generates a process control error message for the OS in the event of redundancy losses and rack/station failures. It also indicates internal errors of the rack/station (SUBN1ERR, SUBN2ERR), and of the preferred channel (SUBN1ACT, SUBN2ACT) if there are active DP slaves at its outputs. The output structure RAC_DIAG contains the geographic address of the rack, and the group error information RACK_ERR. If RACK_ERR = 1, the corresponding rack is not available.The block is installed in the OBs listed above once at each station or local I/O device. The SUBNET_PN block enables the runtime group that contains the RACK_PN1 block. Start and diagnostic information is read from the CPU_DIAG_PN IN_OUT structure, which is interconnected with the CPU_DIAG_PN structure of the OB_BEGIN_HPN block. The RACK_PN1 block has one enable output for each rack (station) slot. The RACK_PN1 block generates the number of a corresponding message on the basis of the start information of the calling OBs if the current block is affected. The block evaluates error events, and uses the diagnostic address DADDR of the PN-IO device to determine the currently active preferred channel (SUBN1ACT, SUBN2ACT) of redundant PROFINET PN interface circuits.
Note If you want to change the SUBN1_ID (connection to CPU 0) and SUBN2_ID (connection to CPU 1) inputs online, you must set input ACC_ID = TRUE to update the output values.
Redundancy
In H systems with distributed I/Os, the RACK_PN1 block supports redundancy of the PN-IO systems. If you want to use this function, you must configure the SUBN1_ID (connection to CPU 0) and SUBN2_ID (connection to CPU 1) inputs of the RACK_PN1 block with the numbers of the redundant DP master systems. If there is no redundancy, the remaining input must be set to the (default) value 16#FF.
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
447
Family: @System 6.85 RACK_PN1: PROFINET RACK Function Block - R1 Device
Additional information Additional information is available in the section: Message texts and associated values of RACK_PN1 (Page 449)
6.85.2
I/Os of RACK_PN1
The factory setting of the block display in the CFC is identified in the "I/O" column:
I/O name bold = I/O visible, I/O name normal = I/O not visible.
You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15)".
Input parameters
I/O (parameter) SUBN_TYP SUBN1_ID SUBN2_ID RACK_NO DADDR_L PNIO_L_ADR PORT1_L_ADR PORT1_L_CONNECT PORT2_L_ADR PORT2_L_CONNECT DADDR_R PNIO_R_ADR PORT1_R_ADR PORT1_R_CONNECT PORT2_R_ADR PORT2_R_CONNECT PN_REDUNDANCY_LEV- EL DELAY FEATURE_01 EN_MSG EV_ID
EV_ID1 MS DIAG_BUF
Meaning
Data type
1=External PN IO-System
BOOL
ID of primary PN-IO-System
BYTE
ID of redundant PN-IO-System
BYTE
Rack/station number
BYTE
Diagnostic address of PN slave - left
INT
Diagnostic address of PN-IO Interface - Left INT
Diagnostic address of PORT1 - left
INT
1=Port1 connected - left
BYTE
Diagnostic address of PORT2 - left
INT
1=Port2 connected - left
BYTE
Diagnostic address of PN slave - right
INT
Diagnostic address of PN-IO Interface - Right INT
Diagnostic address of PORT1 - right
INT
1=Port1 connected - right
BYTE
Diagnostic address of PORT2 - right
INT
1=Port2 connected - right
BYTE
PN redundancy level S1=16#1; S2=16#2; BYTE R1=16#4; R2=16#8
Alarm delay (s)
INT
Features of hardware parameter 01
WORD
1=Enable alarm
BOOL
Message number ALARM_8P (assigned by DWORD the ES)
Event ID
DWORD
Event ID
DWORD
1= CPU diagnostic buffer entry on (relevant BOOL for service personnel)
Default
0 255 255 0 0 0 0 0 0 0 0 0 0 0 0 0 0
15 0 1 0
0 0 0
448
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
In/Out parameters
I/O (parameter) ACC_ID CPU_DIAG_PN SUB_DIAG
Out parameters
I/O (parameter) O_MS QRACKF RAC_DIAG SUBN1ERR SUBN2ERR SUBN1ACT SUBN2ACT EN_Mxx MSG_STAT MSG_STAT1 QMSGER QMSGER1
Family: @System 6.85 RACK_PN1: PROFINET RACK Function Block - R1 Device
Meaning
1 = Accept new ID settings CPU diagnostics (system structure) System structure
Data type Default
BOOL
0
STRUCT
STRUCT
Meaning
Maintenance State 1 = Higher-level error System structure 1=Slave 1 failure 1=Slave 2 failure 1=Slave 1 active 1=Slave 2 active 1=Enable MODUL xx (xx = 0 - 63) Message failure Message failure 1=Message ERROR 1=Message ERROR
Data type Default
DWORD
0
BOOL
0
STRUCT
BOOL
0
BOOL
0
BOOL
0
BOOL
0
BOOL
0
WORD
0
WORD
0
BOOL
0
BOOL
0
Note
The RACK_PNT block is used instead of the RACK_PN1 block when time stamping (SOE) is activated.
6.85.3
Message texts and associated values of RACK_PN1
Assignment of message text and message class The process control messages of ALARM_8P with EV_ID are assigned as follows:
Message num- ber
1
Default message text Station @1%d@/@3%d@: Redundancy loss
2
Station @2%d@/@3%d@: Redundancy loss
Message class
PLC Process Control Message - Error PLC Process Control Message - Error
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
449
Family: @System 6.85 RACK_PN1: PROFINET RACK Function Block - R1 Device
Message num- ber
3
Default message text Station @1%d@/@3%d@: Failure
4
Station @2%d@/@3%d@: Failure
5
Station @4%d@/@3%d@: Missing or wrong server module
6
7
8
Station @1%d@/@3%d@: Multiple failure
Message class
PLC Process Control Message - Failur PLC Process Control Message - Failure PLC Process Control Message - Error No message No message PLC Process Control Message - Failure
Associated values of ALARM_8P with EV_ID:
Associated val- ue
1 2 3
Block parameter
Primary PN-IO system number (SUBN1_ID) Redundant PN-IO system number (SUBN2_ID) Rack/station number (RACK_NO)
Data type
BYTE BYTE BYTE
The process control messages of ALARM_8P with EV_ID1 are assigned as follows:
Message num- ber 1 2 3 4 5 6 7 8
Default message text Station @4%d@/ @3%d@/0: Port 1 error Station @4%d@/ @3%d@/0: Port 2 error Station @4%d@/ @3%d@/0: Maintenance demanded (PN-IO) Station @4%d@/ @3%d@/0: Maintenance required (PN-IO) Station @4%d@/ @3%d@/1: Port 1 error Station @4%d@/ @3%d@/1: Port 2 error Station @4%d@/ @3%d@/1: Maintenance demanded (PN-IO) Station @4%d@/ @3%d@/1: Maintenance required (PN-IO)
Message class
PLC Process Control Message - Error
PLC Process Control Message - Error
PLC Process Control Message - Error
Preventative Mainte- nance - Standard
PLC Process Control Message - Error
PLC Process Control Message - Error
PLC Process Control Message - Error
Preventative Mainte- nance - Standard
450
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.86 RACK_PNT: PROFINET RACK function block - R1 device
Associated values of ALARM_8P with EV_ID1:
Associated val- ue
1 2 3 4
Block parameter
Primary PN-IO system number (SUBN1_ID) Redundant PN-IO system number (SUBN2_ID) Rack/station number (RACK_NO) PN-IO System number
Data type
BYTE BYTE BYTE WORD
You can find additional information in the section: Message Classes (Page 531)
6.86
RACK_PNT: PROFINET RACK function block - R1 device
6.86.1
Description of RACK_PNT
Object name (type + number) FB 432 · I/Os of RACK_PNT (Page 452)
Area of application The block RACK_PNT monitors the status of a PN-IO rack and reports the associated error events. The block releases the lower-level IM_TS_PN block when a status alarm occurs (OB55).
Calling OBs
The block must be installed in the run sequence in the following OBs:
OB1 OB55 OB81 OB82 OB85 OB86 OB100
Cyclic program Status alarm Power outage Diagnostic alarm Program sequence error Rack failure New start (warm start)
Configuration
The following actions are executed automatically with the "Generate module drivers" CFC function:
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
451
Family: @System 6.86 RACK_PNT: PROFINET RACK function block - R1 device
The RACK_PNT block is installed in the run sequence downstream of the SUBNET block. The RACK_NO, DADDR, SUBN1_ID, SUBN2_ID, and SUBN_TYP inputs are configured. The EN input is interconnected with the output of an AND block. whose inputs are interconnected to the EN_SUBx output of the OB BEGIN_HPN block, and to the EN_Rxxx output of the SUBNET block. The CPU_DIAG_PN OUT structure of the OB_BEGIN_HPN block and SUB_DIAG_PN of the SUBNET_PN block are interconnected with the IN_OUT structures of the same name of the RACK_PNT block.
Startup characteristics The RACK_PNT block initializes ALARM_8P messages. It checks availability of the station and, in H systems, determines the preferred channel of the station.
6.86.2
I/Os of RACK_PNT
Quintessence The factory setting of the block display in the CFC is identified in the "I/O" column: I/O name bold = I/O visible, I/O name normal = I/O not visible. You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15)".
Input parameters
I/O (parameter) DADDR_L
DADDR_R
DELAY DIAG_BUF
EN_MSG EV_ID
EV_ID1
EV_ID2
EV_ID3
FEATURE_01
Meaning
Data type Default
Diagnostic address of the PN_IO) Device - INT
0
left
Diagnostic address of the PN_IO) Device - INT
0
right
Alarm delay
INT
15
Entry in the diagnostic buffer (relevant for BOOL
0
maintenance personnel)
Message release
BOOL
1
Message number ALARM_8P (assigned by DWORD
0
ES)
Message number ALARM_8P (assigned by DWORD
0
ES)
Message number ALARM_8P (assigned by DWORD
0
ES)
Message number ALARM_8P (assigned by DWORD
0
ES)
Property of the hardware parameter 01 WORD
0
452
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.86 RACK_PNT: PROFINET RACK function block - R1 device
I/O (parameter) PN_REDUNDANCY_LEVEL
MS PNIO_L_ADR PNIO_R_ADR
PORT1_L_ADR PORT1_R_ADR PORT1_L_CONNECT PORT1_R_CONNECT PORT2_L_ADR PORT2_R_ADR PORT2_L_CONNECT PORT2_R_CONNECT RACK_NO SUBN_TYP SUBN1_ID SUBN2_ID
Meaning
Data type
PN redundancy level S1=16#1; S2=16#2; BYTE R1=16#4; R2=16#8
Maintenance status
DWORD
Diagnostic address of PN-IO Interface - Left INT
Diagnostic address of PN-IO Interface - INT Right
Diagnostic address of PORT 1 - left
INT
Diagnostic address of PORT 1 - right
INT
Port 1 Connection Status - left
BYTE
Port 1 Connection Status - right
BYTE
Diagnostic address of PORT 2 - left
INT
Diagnostic address of PORT 2 - right
INT
Port 2 Connection Status - left
INT
Port 2 Connection Status - right
INT
Rack number
BYTE
1 = External PN-IO-System
BOOL
ID of primary PN-IO-System
BYTE
ID of redundant PN-IO-System
BYTE
Default
0
0 0 0
0 0 0 0 0 0 0 0 0 0 255 255
Output parameters
I/O (parameter) EN_Mxx
MSGSTATx
O_MS QMSGERx
RAC_DIAG QRACKF SUBN1ACT SUBN1ERR SUBN2ACT SUBN2ERR
Meaning
Data type
1= Enable MODUL xx (xx = 0 - 63)
Status output of ALARM_8P_x (x = 1-2)
Maintenance status
Message error for the ALARM_8P_x x = 1 - 2)
System structure
1 = Higher-level error
1 = Slave 1 active
1 = Error Slave 1
1 = Slave 2 active
1 = Error Slave 2
BOOL
WORD
DWORD BOOL
STRUCT BOOL BOOL BOOL BOOL BOOL
Default
0
0
0 0
0 0 0 0 0 0
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
453
Family: @System 6.86 RACK_PNT: PROFINET RACK function block - R1 device
I/O (parameter)
RACK_TS_XCHG
Meaning Data exchange
SaS_TS_00 SaS_TS_01
Time stamp Time stamp
Data type
Default
STRUCT
0
RET: WORD;
PERAF: BOOL; // 1=Module I/O Ac- cess Failure
PARF: BOOL; // 1=Parameter As- signment Error Module
BUFOV : BOOL; //Buffer overflow
DIOF: BOOL; //Digital input observ- er failure
BSOF : BOOL; //Buffer status ob- server failure
TSOF: BOOL; //Time status observ- er failure
SRLOF: BOOL; //System redundan- cy layer observer failure
SIOF: BOOL; //Source identification observer failure
BPARF: BOOL; // 1=Parameter As- signment Error Block
TS_NCON : BOOL; // 1=TS_xxx is not connected
SICH : BOOL; // Source identifica- tion channel
TMSTAT_NO_SYNC : BOOL; // Time status
TMSTAT_JITTER : BOOL; // Time sta- tus
SRLS : BOOL; // Redundancy status
MSG_BUSY : BOOL; // reserve
RESV1 : BOOL; // reserve
SUBNET: BYTE; RACK: BYTE;
SLOT: BYTE;
CHANNEL: BYTE;
STRUCT
-
BYTE0: BYTE; .... BYTE65:BYTE; END_STRUCT
STRUCT BYTE0: BYTE; ....
-
BYTE65:BYTE; END_STRUCT
Input/Output parameters
I/O (parameter) ACC_ID CPU_DIAG_PN
Meaning
1 = Accept new ID settings CPU-diagnosis (system structure)
Data type Default
BOOL
0
STRUCT
-
454
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
I/O (parameter)
SUB_DIAG
CPU_OB_5X_PN
Family: @System 6.86 RACK_PNT: PROFINET RACK function block - R1 device
Meaning
System structure OB_5x-Start information
Data type Default
STRUCT
-
STRUCT
-
6.86.3
Message texts and associated values of RACK_PNT
Assignment of message text and message class The process control messages of ALARM_8P with EV_ID are assigned as follows:
Message num- ber 1 2 3 4 5 6 7 8
Default message text
Station @7%d@ / @3%d@: Loss of redundancy
Station @10%d@/@3%d@: Missing or wrong server module
Station @7%d@/ @3%d@: Failure
Station @8%d@/@9%d@: Output TS_xxx von S_CHxx: Slot=@5%d@channel=@6%d@is not interconnected Station @1%d@/@3%d@: I/O access error: Ret_Val@4%d@
Station @1%d@/@3%d@: Parameter assignment error LADDR
Station @1%d@/@2%d@: Parameter assignment error slot=@5%d@, channel=@6%d@ Station @1%d@/ @3%d@: Multiple failure
Message class
PLC Process Control Message - Error
PLC Process Control Message - Error
PLC Process Control Message - Failure
PLC Process Control Message - Failure
PLC Process Control Message - Failure
PLC Process Control Message - Failure
PLC Process Control Message - Failure
PLC Process Control Message - Failure
Associated values of ALARM_8P with EV_ID:
Associated val- ue
1 2 3 4 5 6 7 8 9 10
Block parameter
Primary PN-IO-System Number (SUBN1_ID) Redundant PN-IO-System Number (SUBN2_ID) Rack or station number (RACK_NO) Return value Slot number Channel number Subnet ID Subnet ID Rack number Subnet ID
Data type
BYTE BYTE BYTE BOOL BYTE BYTE WORD WORD BYTE WORD
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
455
Family: @System 6.86 RACK_PNT: PROFINET RACK function block - R1 device
The process control messages of ALARM_8P with EV_ID1 are assigned as follows:
Message num- ber 1 2 3 4 5 6 7 8
Default message text Station @4%d@/ @3%d@/0: Port 1 error Station @4%d@/ @3%d@/0: Port 2 error Station @4%d@/ @3%d@/0: Maintenance demanded (PN-IO) Station @4%d@/ @3%d@/0: Maintenance required (PN-IO) Station @4%d@/ @3%d@/1: Port 1 error Station @4%d@/ @3%d@/1: Port 2 error Station @4%d@/ @3%d@/1: Maintenance demanded (PN-IO) Station @4%d@/ @3%d@/1: Maintenance required (PN-IO)
Message class
PLC Process Control Message - Error
PLC Process Control Message - Error
PLC Process Control Message - Error
Preventative Mainte- nance - Standard
PLC Process Control Message - Error
PLC Process Control Message - Error
PLC Process Control Message - Error
Preventative Mainte- nance - Standard
Associated values of ALARM_8P with EV_ID1:
Associated value Block parameter
1
Primary PN-IO-System Number (SUBN1_ID)
2
Primary PN-IO-System Number (SUBN2_ID)
3
Rack or station number (RACK_NO)
4
PN-IO-System - Number
Data type BYTE BYTE BYTE WORD
The process control messages of ALARM_T with EV_ID2 are assigned as follows:
Message num- ber 1
2
3
4
5
6
Default message text
Message class
Station @1%d@/@2%d Maintenance demanded (buffer over- PLC Process Control
flow)
Message - Error
Station @1%d@/@2%d@/@3%d@/@4%d@: Maintenance alarm (stop time stamping functionality)
PLC Process Control Message - Failure
Station @1%d@ @2%d@: Maintenance alarm (buffer status observer failure)
PLC Process Control Message - Failure
Station @1%d@/@2%d@: Maintenance alarm (time status ob- PLC Process Control
server failure)
Message - Failure
Station @1%d@/@2%d@: Maintenance alarm (redundancy lay- PLC Process Control
er (SRL) observer failure)
Message - Failure
Station @1%d@/@2%d@: Maintenance alarm (source identifi- PLC Process Control
cation observer failure)
Message - Failure
456
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.86 RACK_PNT: PROFINET RACK function block - R1 device
Message num- ber
7
8
Default message text
Message class
No message No message
Associated values of ALARM_T with EV_ID2:
Associated value Block parameter
1
Primary PN-IO-System Number (SUBN1_ID)
2
Primary PN-IO-System Number (SUBN2_ID)
3
Rack number
4
Subnet ID
Data type BYTE BYTE BYTE BYTE
The process control messages of ALARM_T with EV_ID3 are assigned as follows:
Message num- ber 1
2
3
4
5
6 7 8
Default message text
Message class
Station @1%d@/@2%d@/@3%d@/@4%d@: Maintenance re- quired (start-up information)
Station @1%d@/@2%d@: Maintenance required (time-of-day frame failure, status=@3%d@, Sec=@4%d@, nSec=@5%d@)
Station @1%d@/@2%d@: Maintenance required (switch in case of redundancy incoming)
Station @1%d@/@2%d@: Maintenance required (time differ- ence between message frame and internal clock may impair accuracy)
Station @1%d@/@2%d@: Maintenance required (switch in case of redundancy outgoing)
Preventative Main- tenance - Standard Preventative Main- tenance - Standard Preventative Main- tenance - Standard Preventative Main- tenance - Standard
Preventative Main- tenance - Standard No message No message No message
Associated values of ALARM_T with EV_ID3:
Associated value Block parameter
1
Timestamp
2
PN-IO-System - Number
3
Rack
4
Slot
5
Channel
Data type ARRAY BYTE BYTE BYTE BYTE
You can find additional information in the section: Message Classes (Page 531).
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
457
Family: @System 6.87 RED_AI: Status processing of redundant AI modules
6.87
RED_AI: Status processing of redundant AI modules
6.87.1
Description of RED_AI
Object name (type + number) FB 444 · I/Os of RED_AI (Page 459)
Area of application Diagnosis of the redundant analog output module pair.
Configuration
The following are automatically executed with the "Generate module driver" CFC function:
· The OB_BEGIN block`s OUT-Structure CPU_DIAG/CPU_DIAG_80 is interconnected with the identically named IN_OUT-Structure of the RED_xxx-block.
· The OUT-Structure MOD_INF of the upstream MOD-block is interconnected with the MOD_INF1/MOD_INF2 IN_OUT-Structure of the RED_xxx-block.
· The input parameters LADDR_Mas, LADDR_Slv, PER_TYPE, PAR_PROI, CHAN_NUM, CHAN_BITS, DIS_TIME, VAL_UNIT, DIS_PERC, CHAN_MAS, EXEC_TIM, CHAN01..08_S are parameterised with the values set in HW config.
· The input parameters MODF1, MODF2, MODE1_00..07, MODE2_00..07 are interconnected with the correspondent output parameters of the previous block.
Calling OBs
The block must be installed in the run sequence in the following OBs:
OB 3x OB 100 OB 72 OB 80 OB 85
Cyclic interrupt OB (Channel OB) New restart CPU-Redundancy Error (only in H-Systems) "Time error-OB" (only in Single-Mode) Program sequence error
Error handling The plausibility of input parameters is not checked.
458
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.87 RED_AI: Status processing of redundant AI modules
Block functions The RED_AI block processes the status of all channels cyclically based on the outputs OMODE_xx or the MOD_x blocks and then forms the information on redundancy of the OR blocks.
Message response Not available
6.87.2
I/Os of RED_AI
The factory setting of the block display in the CFC is identified in the "I/O" column:
I/O name bold = I/O visible, I/O name normal = I/O not visible.
You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15)".
Input parameters
I/O (parameter) CH_INF_Mas CH_INF_Slv LADDR_Mas LADDR_Slv MODF1 MODF2 QI_INFO PER_TYPE PAR_PROI CHAN_NUM CHAN_BIT DIS_TIME RESERVE1 VAL_UNIT RESERVE2 DIS_PERC CHAN_MAS EXEC_TIM CHANxx_S MODE1_xx MODE2_xx FEATURE
Meaning
Data type Default
Master address: 1 = Channel x active
DWORD
0
Slave address: 1 = Channel x active
DWORD
0
Master module address
INT
0
Slave module address
INT
0
1=Module 1 pulled / out of order
BOOL
0
1=Module 2 pulled / out of order
BOOL
0
1= Quality info active
BYTE
0
Reserve
BYTE
0
Process image partition
BYTE
0
Total number of channels -1
BYTE
0
Reserve
BYTE
0
Reserve
WORD
0
Reserve 1
BYTE
0
Reserve
BYTE
0
Reserve 1
BYTE
0
Reserve
BYTE
0
Reserve
WORD
0
Reserve
WORD
0
Reserve (xx = 01 - 16)
WORD
0
Module 1 mode channel xx (xx = 00 - 15) DWORD
0
Module 2 mode channel xx (xx = 00 - 15) DWORD
0
Features of the hardware parameters
DWORD
0
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
459
Family: @System 6.87 RED_AI: Status processing of redundant AI modules
In/Out parameters
I/O (parameter) CPU_DIAG_PN CPU_DIAG_80 MOD_INF1 MOD_INF2 DIAG_INF_1 DIAG_INF_2 ACC_MODE
Meaning
Data type Default
System structure
STRUCT
-
Time error OB start information
STRUCT
-
Module 1 information structure
STRUCT
-
Module 2 information structure
STRUCT
-
Module Diagnostic Information Structure STRUCT
-
Module Diagnostic Information Structure STRUCT
-
1 = Accept new mode settings
BOOL
0
Out parameters
I/O (parameter) QERR QACTIV_L QACTIV_H QPASS
QMOD_CH_L QMOD_CH_H QLADDR_L QLADDR_H
QCH_INF_L QCH_INF_H QUN_OV_L
QUN_OV_H
QDIS_EXPIRE QCH_DISCREP QPER_TYPE QPAR_PROI QCHAN_NUM QCHAN_BIT QDIS_TIME QVAL_UNIT QDIS_PERC QCHAN_MAS QEXEC_TIM MODUL_STATUS DEPASS_RED
Meaning
Data type Default
1=Runtime error
BOOL
1
1=Low Module Active
BOOL
0
1=High Module Active
BOOL
0
1=At least one module or one channel is BOOL
0
passivized
Status of the channels of the 1st module BOOL
0
Status of the channels of the 2nd module BOOL
0
Lower address (address that the user uses) WORD
0
Higher address (address of the redundant WORD
0
module)
Status of the channels of the 1st module DWORD
0
Status of the channels of the 2nd module DWORD
0
Underflow / overflow status of the channels DWORD
0
of the L module
Underflow / overflow status of the channels DWORD
0
of the H module
Reserve
DWORD
0
Reserve
DWORD
0
Reserve
BYTE
0
Partial process image
BYTE
0
Total number of channels -1
BYTE
0
Reserve
BYTE
0
Reserve
WORD
0
Reserve
BYTE
0
Reserve
BYTE
0
Reserve
WORD
0
Reserve
WORD
0
MODUL_STATUS of RED_AI
DWORD
0
Depassivation
BOOL
0
460
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.88 RED_AIH: Status processing of redundant AI HART modules (<= 8 CHANNELS)
I/O (parameter)
RETURN_VAL QCH_VAL_xx QVALxx_L QVALxx_H QCH_LV_VAL_xx QMODF1 QMODF2
Meaning
Return Value Active channel value (xx = 00 - 15) Reserve (xx = 00 - 15) Reserve (xx = 00 - 15) Reserve (xx = 00 - 15) 1 = Module 1 Removed / Out of Order 1 = Module 2 Removed / Out of Order
Data type Default
INT
0
BYTE
0
WORD
0
WORD
0
WORD
0
BOOL
0
BOOL
0
6.88
RED_AIH: Status processing of redundant AI HART modules (<= 8 CHANNELS)
6.88.1
Description of RED_AIH
Object name (type + number) FB 447 · I/Os of RED_AIH (Page 462)
Area of application Diagnosis of the HART Analog input module pair.
Configuration
The following are automatically executed with the "Generate module driver" CFC function:
· The OB_BEGIN block`s OUT-Structure CPU_DIAG/CPU_DIAG_80 is interconnected with the identically named IN_OUT-Structure of the RED_xxx-block.
· The OUT-Structure MOD_INF of the upstream MOD-block is interconnected with the MOD_INF1/MOD_INF2 IN_OUT-Structure of the RED_xxx-block.
· The input parameters LADDR_Mas, LADDR_Slv, PER_TYPE, PAR_PROI, CHAN_NUM, CHAN_BITS, DIS_TIME, VAL_UNIT, DIS_PERC, CHAN_MAS, EXEC_TIM, CHAN01..08_S are parameterised with the values set in HW config.
· The input parameters MODF1, MODF2, MODE1_00..07, MODE2_00..07 are interconnected with the correspondent output parameters of the previous block
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
461
Family: @System 6.88 RED_AIH: Status processing of redundant AI HART modules (<= 8 CHANNELS)
Calling OBs
The block must be installed in the run sequence in the following OBs:
OB 3x OB 100 OB 72 OB 80 OB 85
Cyclic interrupt OB (Channel OB) New restart CPU-Redundancy Error (only in H-Systems) "Time error-OB" (only in Single-Mode) Program sequence error
Error handling The plausibility of input parameters is not checked.
Block functions
The RED_AIH block processes the status of all channels cyclically based on the outputs OMODE_xx or the MOD_x blocks and then forms the information on redundancy of the OR blocks.
Message response Not available
6.88.2
I/Os of RED_AIH
The factory setting of the block display in the CFC is identified in the "I/O" column:
I/O name bold = I/O visible, I/O name normal = I/O not visible.
You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15)".
Input parameters
I/O (parameter) CH_INF_Mas CH_INF_Slv LADDR_Mas LADDR_Slv MODF1 MODF2 QI_INFO PER_TYPE PAR_PROI CHAN_NUM
Meaning
Master address: 1 = Channel x active Slave address: 1 = Channel x active Master module address Slave module address 1=Module 1 pulled / out of order 1=Module 2 pulled / out of order 1= Quality info active Reserve Process image partition Total number of channels -1
Data type Default
DWORD
0
DWORD
0
INT
0
INT
0
BOOL
0
BOOL
0
BYTE
0
BYTE
0
BYTE
0
BYTE
0
462
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.88 RED_AIH: Status processing of redundant AI HART modules (<= 8 CHANNELS)
I/O (parameter)
CHAN_BIT DIS_TIME RESERVE1 VAL_UNIT RESERVE2 DIS_PERC CHAN_MAS EXEC_TIM CHANxx_S CHAN_AV ADDL_AV ADDH_AV MODE1_xx MODE2_xx FEATURE HART8_VAR
Meaning
Data type Default
Reserve
BYTE
0
Reserve
WORD
0
Reserve 1
BYTE
0
Reserve
BYTE
0
Reserve 1
BYTE
0
Reserve
BYTE
0
Reserve
WORD
0
Reserve
WORD
0
Reserve (xx = 01 - 08)
WORD
0
Reserve
INT
0
Reserve
INT
0
Reserve
INT
0
Module 1 mode channel xx (xx = 00 - 07) DWORD
0
Module 2 mode channel xx (xx = 00 - 07) DWORD
0
Features of the hardware parameters
DWORD
0
1 = 8 HART
BOOL
0
In/Out parameters
I/O (parameter) CPU_DIAG_PN CPU_DIAG_80 MOD_INF1 MOD_INF2 DIAG_INF_1 DIAG_INF_2 ACC_MODE
Meaning
Data type Default
System structure
STRUCT
-
Time error OB start information
STRUCT
-
Module 1 information structure
STRUCT
-
Module 2 information structure
STRUCT
-
Module Diagnostic Information Structure STRUCT
-
Module Diagnostic Information Structure STRUCT
-
1 = Accept new mode settings
BOOL
0
Out parameters
I/O (parameter) QERR QACTIV_L QACTIV_H QPASS
QMOD_CH_L QMOD_CH_H QLADDR_L
Meaning
Data type Default
1=Runtime error
BOOL
1
1=Low Module Active
BOOL
0
1=High Module Active
BOOL
0
1=At least one module or one channel is BOOL
0
passivized
Status of the channels of the 1st module BOOL
0
Status of the channels of the 2nd module BOOL
0
Lower address (address that the user uses) WORD
0
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
463
Family: @System 6.89 RED_AQ: Status processing of redundant AQ modules
I/O (parameter) QLADDR_H
QCH_INF_L QCH_INF_H QUN_OV_L
QUN_OV_H
QDIS_EXPIRE QCH_DISCREP QPER_TYPE QPAR_PROI QCHAN_NUM QCHAN_BIT QDIS_TIME QVAL_UNIT QDIS_PERC QCHAN_MAS QEXEC_TIM MODUL_STATUS QDEPASS_RED_PCS7 RETURN_VAL QCUR_L_xx QCUR_H_xxx CH_INF_Mas_AUX_0 CH_INF_Slv_AUX_0 QMODF1 QMODF2
Meaning
Data type Default
Higher address (address of the redundant WORD
0
module)
Status of the channels of the 1st module DWORD
0
Status of the channels of the 2nd module DWORD
0
Underflow / overflow status of the channels DWORD
0
of the L module
Underflow / overflow status of the channels DWORD
0
of the H module
Reserve
DWORD
0
Reserve
DWORD
0
Reserve
BYTE
0
Partial process image
BYTE
0
Total number of channels -1
BYTE
0
Reserve
BYTE
0
Reserve
WORD
0
Reserve
BYTE
0
Reserve
BYTE
0
Reserve
WORD
0
Reserve
WORD
0
MODUL_STATUS
DWORD
0
Depassivation
BOOL
0
Return Value
INT
0
Reserve (xx = 00 - 07)
WORD
0
Reserve (xx = 00 - 07)
WORD
0
Master address aux value 0..31: 1 = active DWORD
0
Slave address aux value 0..31: 1 = active DWORD
0
1 = Module 1 Removed / Out of Order
BOOL
0
1 = Module 2 Removed / Out of Order
BOOL
0
6.89
RED_AQ: Status processing of redundant AQ modules
6.89.1
Description of RED_AQ
Object name (type + number) FB 445 · I/Os of RED_AQ (Page 465)
464
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.89 RED_AQ: Status processing of redundant AQ modules
Area of application Diagnosis of the redundant analog output module pair.
Configuration
The following are automatically executed with the "Generate module driver" CFC function:
· The OB_BEGIN block`s OUT-Structure CPU_DIAG/CPU_DIAG_80 is interconnected with the identically named IN_OUT-Structure of the RED_xxx-block.
· The OUT-Structure MOD_INF of the upstream MOD-block is interconnected with the MOD_INF1/MOD_INF2 IN_OUT-Structure of the RED_xxx-block.
· The input parameters LADDR_Mas, LADDR_Slv, PER_TYPE, PAR_PROI, CHAN_NUM, CHAN_BITS, DIS_TIME, VAL_UNIT, DIS_PERC, CHAN_MAS, EXEC_TIM, CHAN01..08_S are parameterised with the values set in HW config.
· The input parameters MODF1, MODF2, MODE1_00..07, MODE2_00..07 are interconnected with the correspondent output parameters of the previous block.
Calling OBs
The block must be installed in the following OBs (performed automatically in CFC):
OB 3x OB 100 OB 72 OB 80 OB 85
Cyclic interrupt OB (Channel OB) New restart CPU-Redundancy Error (only in H-Systems) "Time error-OB" (only in Single-Mode) Program sequence error
Error handling The plausibility of input parameters is not checked.
Block functions
The RED_AQ block processes the status of all channels cyclically based on the outputs OMODE_xx or the MOD_x blocks and then forms the information on redundancy of the OR blocks.
Message response Not available
6.89.2
I/Os of RED_AQ
The factory setting of the block display in the CFC is identified in the "I/O" column: I/O name bold = I/O visible, I/O name normal = I/O not visible.
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
465
Family: @System 6.89 RED_AQ: Status processing of redundant AQ modules
You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15)".
Input parameters
I/O (parameter) CH_INF_Mas CH_INF_Slv LADDR_Mas LADDR_Slv MODF1 MODF2 QI_INFO PER_TYPE PAR_PROI CHAN_NUM CHAN_BIT CHAN_MAS MASK_CUR MIN_CUR CORR_CUR HALF_CUR MODE1_xx MODE2_xx FEATURE
Meaning
Data type Default
Master address: 1 = Channel x active
DWORD
0
Slave address: 1 = Channel x active
DWORD
0
Master module address
INT
0
Slave module address
INT
0
1=Module 1 pulled / out of order
BOOL
0
1=Module 2 pulled / out of order
BOOL
0
1= Quality info active
BYTE
0
Reserve
BYTE
0
Process image partition
BYTE
0
Total number of channels -1
BYTE
0
Reserve
BYTE
0
Reserve
WORD
0
Reserve
WORD
0
Reserve
WORD
0
Reserve
WORD
0
Reserve
BYTE
0
Module 1 mode channel xx (xx = 00 - 07) DWORD
0
Module 2 mode channel xx (xx = 00 - 07) DWORD
0
Features of the hardware parameters
DWORD
0
In/Out parameters
I/O (parameter) CPU_DIAG_PN CPU_DIAG_80 MOD_INF1 MOD_INF2 DIAG_INF_1 DIAG_INF_2 ACC_MODE
Meaning
Data type Default
System structure
STRUCT
-
Time error OB start information
STRUCT
-
Module 1 information structure
STRUCT
-
Module 2 information structure
STRUCT
-
Module Diagnostic Information Structure STRUCT
-
Module Diagnostic Information Structure STRUCT
-
1 = Accept new mode settings
BOOL
0
466
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.90 RED_AQH: Status processing of redundant AQ HART modules (<= 8 Channels)
Out parameters
I/O (parameter) QERR QACTIV_L QACTIV_H QMOD_CH_L QMOD_CH_H QLADDR_L QLADDR_H
QCH_INF_L QCH_INF_H QPER_TYPE QPAR_PROI QCHAN_NUM QCHAN_BIT QCHAN_MAS QMASK_CUR QMIN_CUR QCORR_CUR MODUL_STATUS DEPASS_RED RETURN_VAL QCUR_L_xx QCUR_H_xx QMODF1 QMODF2
Meaning
Data type Default
1=Runtime error
BOOL
1
1=Low Module Active
BOOL
0
1=High Module Active
BOOL
0
Status of the channels of the 1st module BOOL
0
Status of the channels of the 2nd module BOOL
0
Lower address (address that the user uses) WORD
0
Higher address (address of the redundant WORD
0
module)
Status of the channels of the 1st module DWORD
0
Status of the channels of the 2nd module DWORD
0
Reserve
BYTE
0
Partial process image
BYTE
0
Total number of channels -1
BYTE
0
Reserve
BYTE
0
Reserve
WORD
0
Reserve
WORD
0
Reserve
WORD
0
Reserve
WORD
0
MODUL_STATUS
DWORD
0
Depassivation
BOOL
0
Return Value
INT
0
Reserve (xx = 00 - 07)
WORD
0
Reserve (xx = 00 - 07)
WORD
0
1 = Module 1 Removed / Out of Order
BOOL
0
1 = Module 2 Removed / Out of Order
BOOL
0
6.90
RED_AQH: Status processing of redundant AQ HART modules (<= 8 Channels)
6.90.1
Description of RED_AQH
Object name (type + number) FB 448 · I/Os of RED_AQH (Page 468)
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
467
Family: @System 6.90 RED_AQH: Status processing of redundant AQ HART modules (<= 8 Channels)
Area of application Diagnosis of the redundant HART Analog output module pairs.
Configuration
The following are automatically executed with the "Generate module driver" CFC function:
· The OB_BEGIN block`s OUT-Structure CPU_DIAG/CPU_DIAG_80 is interconnected with the identically named IN_OUT-Structure of the RED_xxx-block.
· The OUT-Structure MOD_INF of the upstream MOD-block is interconnected with the MOD_INF1/MOD_INF2 IN_OUT-Structure of the RED_xxx-block.
· The input parameters LADDR_Mas, LADDR_Slv, PER_TYPE, PAR_PROI, CHAN_NUM, CHAN_BITS, DIS_TIME, VAL_UNIT, DIS_PERC, CHAN_MAS, EXEC_TIM, CHAN01..08_S are parameterised with the values set in HW config.
· The input parameters MODF1, MODF2, MODE1_00..07, MODE2_00..07 are interconnected with the correspondent output parameters of the previous block.
Calling OBs
The block must be installed in the following OBs (performed automatically in CFC):
OB 3x OB 100 OB 72 OB 80 OB 85
Cyclic interrupt OB (Channel OB) New restart CPU-Redundancy Error (only in H-Systems) "Time error-OB" (only in Single-Mode) Program sequence error
Error handling The plausibility of input parameters is not checked.
Block functions
The RED_AQH block processes the status of all channels cyclically based on the outputs OMODE_xx or the MOD_x blocks and then forms the information on redundancy of the OR blocks.
Message response Not available
6.90.2
I/Os of RED_AQH
The factory setting of the block display in the CFC is identified in the "I/O" column: I/O name bold = I/O visible, I/O name normal = I/O not visible.
468
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.90 RED_AQH: Status processing of redundant AQ HART modules (<= 8 Channels)
You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15)".
Input parameters
I/O (parameter) CH_INF_Mas CH_INF_Slv LADDR_Mas LADDR_Slv MODF1 MODF2 QI_INFO PER_TYPE PAR_PROI CHAN_NUM CHAN_BIT CHAN_MAS MASK_CUR CHAN_AV ADDL_AV ADDH_AV CUR_ACTV MIN_CUR CORR_CUR HALF_CUR MODE1_xx MODE2_xx FEATURE HART8_VAR
Meaning
Data type Default
Master address: 1 = Channel x active
DWORD
0
Slave address: 1 = Channel x active
DWORD
0
Master module address
INT
0
Slave module address
INT
0
1=Module 1 pulled / out of order
BOOL
0
1=Module 2 pulled / out of order
BOOL
0
1= Quality info active
BYTE
0
Reserve
BYTE
0
Process image partition
BYTE
0
Total number of channels -1
BYTE
0
Reserve
BYTE
0
Reserve
WORD
0
Reserve
WORD
0
Reserve
INT
0
Reserve
INT
0
Reserve
INT
0
Reserve
WORD
0
Reserve
WORD
0
Reserve
WORD
0
Reserve
BYTE
0
Module 1 mode channel xx (xx = 00 - 07) DWORD
0
Module 2 mode channel xx (xx = 00 - 07) DWORD
0
Features of the hardware parameters
DWORD
0
1 = 8 HART
BOOL
0
In/Out parameters
I/O (parameter) CPU_DIAG_PN CPU_DIAG_80 MOD_INF1 MOD_INF2 DIAG_INF_1 DIAG_INF_2 ACC_MODE
Meaning
Data type Default
System structure
STRUCT
-
Time error OB start information
STRUCT
-
Module 1 information structure
STRUCT
-
Module 2 information structure
STRUCT
-
Module Diagnostic Information Structure STRUCT
-
Module Diagnostic Information Structure STRUCT
-
1 = Accept new mode settings
BOOL
0
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
469
Family: @System 6.91 RED_DI: Status processing of redundant DI modules
Out parameters
I/O (parameter) QERR QACTIV_L QACTIV_H QMOD_CH_L QMOD_CH_H QLADDR_L QLADDR_H
QCH_INF_L QCH_INF_H QPER_TYPE QPAR_PROI QCHAN_NUM QCHAN_BIT QCHAN_MAS QMASK_CUR QMIN_CUR QCORR_CUR MODUL_STATUS DEPASS_RED RETURN_VAL QCUR_L_xx QCUR_H_xx CH_INF_Mas_AUX_0 CH_INF_Slv_AUX_0 QMODF1 QMODF2
Meaning
Data type Default
1=Runtime error
BOOL
1
1=Low Module Active
BOOL
0
1=High Module Active
BOOL
0
Status of the channels of the 1st module BOOL
0
Status of the channels of the 2nd module BOOL
0
Lower address (address that the user uses) WORD
0
Higher address (address of the redundant WORD
0
module)
Status of the channels of the 1st module DWORD
0
Status of the channels of the 2nd module DWORD
0
Reserve
BYTE
0
Partial process image
BYTE
0
Total number of channels -1
BYTE
0
Reserve
BYTE
0
Reserve
WORD
0
Reserve
WORD
0
Reserve
WORD
0
Reserve
WORD
0
MODUL_STATUS
DWORD
0
Depassivation
BOOL
0
Return Value
INT
0
Reserve (xx = 00 - 07)
WORD
0
Reserve (xx = 00 - 07)
WORD
0
Master address aux value 0..31: 1 = active DWORD
0
Slave address aux value 0..31: 1 = active DWORD
0
1 = Module 1 Removed / Out of Order
BOOL
0
1 = Module 2 Removed / Out of Order
BOOL
0
6.91
RED_DI: Status processing of redundant DI modules
6.91.1
Description of RED_DI
Object name (type + number) FB 442 · I/Os of RED_DI (Page 471)
470
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.91 RED_DI: Status processing of redundant DI modules
Area of application The RED_DI block is used for diagnostics of the redundant digital input module pair.
Configuration
The following are automatically executed with the "Generate module driver" CFC function:
· OUT-Structure CPU_DIAG/CPU_DIAG_80 of the OB_BEGIN-block is interconnected with the IN_OUT-Structure of the RED_xxx-block.
· The upstram MOD block's OUT-Struktur MOD_INF is interconnected with the MOD_INF1/ MOD_INF2 IN_OUT-Structure of the RED_xxx-block.
· The input parameters LADDR_Mas, LADDR_Slv, PER_TYPE, PAR_PROI, CHAN_NUM, CHAN_BITS, DIS_TIME, VAL_UNIT, DIS_PERC, CHAN_MAS, EXEC_TIM, CHAN01..08_S are parameterised with the values set in HW config.
· The input parameters MODF1, MODF2, MODE1_00..07, MODE2_00..07 are interconnected with the correspondent output parameters of the previous block.
Calling OBs
The block must be installed in the following OBs (performed automatically in CFC):
OB 3x OB 100 OB 72 OB 80 OB 85
Cyclic interrupt OB (Channel OB) New restart CPU-Redundancy Error (only in H-Systems) "Time error-OB" (only in Single-Mode) Program sequence error
Error handling The plausibility of input parameters is not checked.
Block functions
The RED_DI block processes the status of all channels cyclically based on the outputs OMODE_xx or the MOD_x blocks and then forms the information on redundancy of the OR blocks.
Message response Not available
6.91.2
I/Os of RED_DI
The factory setting of the block display in the CFC is identified in the "I/O" column: I/O name bold = I/O visible, I/O name normal = I/O not visible.
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
471
Family: @System 6.91 RED_DI: Status processing of redundant DI modules
You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15)".
Input parameters
I/O (parameter) CH_INF_Mas CH_INF_Slv LADDR_Mas LADDR_Slv MODF1 MODF2 QI_INFO PER_TYPE PAR_PROI CHAN_NUM CHAN_BIT DIS_TIME RESERVE1 R_TO_TD MODE1_xx MODE2_xx FEATURE
Meaning
Data type Default
Master address: 1 = Channel x active
DWORD
0
Slave address: 1 = Channel x active
DWORD
0
Master module address
INT
0
Slave module address
INT
0
1=Module 1 pulled / out of order
BOOL
0
1=Module 2 pulled / out of order
BOOL
0
1= Quality info active
BYTE
0
Reserve
BYTE
0
Process image partition
BYTE
0
Total number of channels -1
BYTE
0
Reserve
BYTE
0
Reserve
WORD
0
Reserve
BYTE
0
Reserve
BYTE
0
Module 1 mode channel xx (xx = 00 - 31) DWORD
0
Module 2 mode channel xx (xx = 00 - 31) DWORD
0
Features of the hardware parameters
DWORD
0
In/Out parameters
I/O (parameter) CPU_DIAG_PN CPU_DIAG_80 MOD_INF1 MOD_INF2 DIAG_INF_1 DIAG_INF_2 ACC_MODE
Meaning
Data type Default
System structure
STRUCT
-
Time error OB start information
STRUCT
-
Module 1 information structure
STRUCT
-
Module 2 information structure
STRUCT
-
Module Diagnostic Information Structure STRUCT
-
Module Diagnostic Information Structure STRUCT
-
1 = Accept new mode settings
BOOL
0
Out parameters
I/O (parameter) QERR QVAL QACTIV_MAS
Meaning
1=Runtime error Output value 1=Master module active
Data type Default
BOOL
1
DWORD
0
BOOL
0
472
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.92 RED_DQ: Status processing of redundant DQ modules
I/O (parameter) QACTIV_SLV QMOD_CH_MAS QMOD_CH_SLV QLADDR_MAS QLADDR_SLV
QCH_INF_MAS QCH_INF_SLV QDIS_EXPIRE QCH_DISCREP QPER_TYPE QPAR_PROI QCHAN_NUM QCHAN_BIT QDIS_TIME QR_TO_TD MODUL_STATUS QDEPASS_RED_ PCS7 RETURN_VAL QCH_VAL_xx QCH_LV_VAL_xx QMODF1 QMODF2
Meaning
Data type Default
1=Slave module active
BOOL
0
Status of the channels of the 1st module BOOL
0
Status of the channels of the 2nd module BOOL
0
Master address (address that the user uses) INT
0
Slave address (address of the redundant INT
0
module)
Status of the channels of the 1st module DWORD
0
Status of the channels of the 2nd module DWORD
0
Reserve
DWORD
0
Reserve
DWORD
0
Reserve
BYTE
0
Process image partition
BYTE
0
Total number of channels -1
BYTE
0
Reserve
BYTE
0
Reserve
WORD
0
Reserve
BYTE
0
MODUL_STATUS
DWORD
0
1=Depassivation
BOOL
0
Return value
INT
0
Reserve (xx = 00 - 31)
BYTE
255
Reserve (xx = 00 - 31)
BOOL
0
1 = Module 1 Removed / Out of Order
BOOL
0
1 = Module 2 Removed / Out of Order
BOOL
0
6.92
RED_DQ: Status processing of redundant DQ modules
6.92.1
Description of RED_DQ
Object name (type + number) FB 443 · I/Os of RED_DQ (Page 474)
Area of application Diagnosis of the redundant digital output module pairs.
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
473
Family: @System 6.92 RED_DQ: Status processing of redundant DQ modules
Calling OBs
The block must be installed in the following OBs (performed automatically in CFC):
OB 3x OB 100 OB 72 OB 80 OB 85
Cyclic interrupt OB (Channel OB) New restart CPU-Redundancy Error (only in H-Systems) "Time error-OB" (only in Single-Mode) Program sequence error
Configuration
The following are automatically executed with the "Generate module driver" CFC function:
· The OB_BEGIN block`s OUT-Structure CPU_DIAG/CPU_DIAG_80 is interconnected with the identically named IN_OUT-Structure of the RED_xxx-block.
· The OUT-Structure MOD_INF of the upstream MOD-block is interconnected with the MOD_INF1/MOD_INF2 IN_OUT-Structure of the RED_xxx-block.
· The input parameters LADDR_Mas, LADDR_Slv, PER_TYPE, PAR_PROI, CHAN_NUM, CHAN_BITS, DIS_TIME, VAL_UNIT, DIS_PERC, CHAN_MAS, EXEC_TIM, CHAN01..08_S are parameterised with the values set in HW config.
· The input parameters MODF1, MODF2, MODE1_00..07, MODE2_00..07 are interconnected with the correspondent output parameters of the previous block.
Error handling The plausibility of input parameters is not checked.
Block functions
The RED_DQ block processes the status of all channels cyclically based on the outputs OMODE_xx or the MOD_x blocks and then forms the information on redundancy of the OR blocks.
Message response Not available
6.92.2
I/Os of RED_DQ
The factory setting of the block display in the CFC is identified in the "I/O" column:
I/O name bold = I/O visible, I/O name normal = I/O not visible.
You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15)".
474
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Input parameters
I/O (parameter) CH_INF_Mas CH_INF_Slv LADDR_Mas LADDR_Slv MODF1 MODF2 QI_INFO PER_TYPE PAR_PROI CHAN_NUM CHAN_BIT MODE1_xx MODE2_xx FEATURE
In/Out parameters
I/O (parameter) CPU_DIAG_PN CPU_DIAG_80 MOD_INF1 MOD_INF2 DIAG_INF_1 DIAG_INF_2 ACC_MODE
Out parameters
I/O (parameter) QERR QACTIV_L QACTIV_H QMOD_CH_L QMOD_CH_H QLADDR_L QLADDR_H
QCH_INF_L
Family: @System 6.92 RED_DQ: Status processing of redundant DQ modules
Meaning
Data type Default
Master address: 1 = Channel x active
DWORD
0
Slave address: 1 = Channel x active
DWORD
0
Master module address
INT
0
Slave module address
INT
0
1=Module 1 pulled / out of order
BOOL
0
1=Module 2 pulled / out of order
BOOL
0
1= Quality info active
BYTE
0
Reserve
BYTE
0
Process image partition
BYTE
0
Total number of channels -1
BYTE
0
Reserve
BYTE
0
Module 1 mode channel xx (xx = 00 - 07) DWORD
0
Module 2 mode channel xx (xx = 00 - 07) DWORD
0
Features of the hardware parameters
DWORD
0
Meaning
Data type Default
System structure
STRUCT
-
Time error OB start information
STRUCT
-
Module 1 information structure
STRUCT
-
Module 2 information structure
STRUCT
-
Module Diagnostic Information Structure STRUCT
-
Module Diagnostic Information Structure STRUCT
-
1 = Accept new mode settings
BOOL
0
Meaning
Data type Default
1=Runtime error
BOOL
1
1=Low Module Active
BOOL
0
1=High Module Active
BOOL
0
Status of the channels of the 1st module BOOL
0
Status of the channels of the 2nd module BOOL
0
Lower address (address that the user uses) WORD
0
Higher address (address of the redundant WORD
0
module)
Status of the channels of the 1st module DWORD
0
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
475
Family: @System 6.93 RED_F: Status processing of redundant F modules
I/O (parameter)
QCH_INF_H QPER_TYPE QPAR_PROI QCHAN_NUM QCHAN_BIT MODUL_STATUS DEPASS_RED RETURN_VAL QMODF1 QMODF2
Meaning
Data type Default
Status of the channels of the 2nd module DWORD
0
Reserve
BYTE
0
Partial process image
BYTE
0
Total number of channels -1
BYTE
0
Reserve
BYTE
0
MODUL_STATUS
DWORD
0
Depassivation
BOOL
0
Return Value
INT
0
1 = Module 1 Removed / Out of Order
BOOL
0
1 = Module 2 Removed / Out of Order
BOOL
0
6.93
RED_F: Status processing of redundant F modules
6.93.1
Description of RED_F
Object name (type + number) FC 289 · RED_F block I/Os (Page 478)
Area of application The RED_F block is used to set up redundant F modules in safety mode.
Calling OBs
The block must be installed in the same OB before the OR block. It is also installed in OB 100.
Use in CFC
The following actions are executed automatically with the "Generate module drivers" CFC function:
· The RED_F block is installed before the OR block in its OB.
· MODE1_xx inputs are interconnected with the OMODE_xx outputs of the MOD_x block in the primary module.
· MODE2_xx inputs are interconnected with the OMODE_xx outputs of the MOD_x block in the redundant module.
· The RACKF1 input is interconnected with the QRACKF output of the MOD_x block of the primary module.
476
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.93 RED_F: Status processing of redundant F modules
· The RACKF2 input is interconnected with the QRACKF output of the MOD_x block of the redundant module.
· The MS1 input is interconnected with the O_MS output of the MOD_x block of the primary module.
· The MS2 input is interconnected with the O_MS output of the MOD_x block of the redundant module.
· The ACTIV_H and ACTIV_L outputs are interconnected with the inputs with the same name in the OR block.
· The CH_INF_H and CH_INF_L outputs are interconnected with the inputs with the same name in the OR block.
· The RETURN_VAL output is interconnected with the RED_STAT input of the OR block.
· The MODUL_STATUS_WORD output is interconnected with the MOD_STAT input of the OR block.
Function and method of operation
The RED_F block processes the status of all channels cyclically based on the outputs OMODE_xx or the MOD_x blocks and then forms the information on redundancy of the OR blocks.
Addressing
Not available
Error handling Not available
Startup characteristics Not available
Time response Not available
Message response Not available
Operator control and monitoring The block has no faceplate.
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
477
Family: @System 6.93 RED_F: Status processing of redundant F modules
6.93.2
I/Os of RED_F
The factory setting of the block display in CFC is identified in the "I/O" column: I/O name in bold characters = I/O is visible; I/O name in standard characters = I/O is hidden.
You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15)".
Input parameters
I/O (parameter) MODE1_xx
MODE2_xx
MS1 MS2 RACKF1 RACKF2
Meaning
Channel mode (xx = 00 31) on the primary module Channel mode (xx = 00 31) on the redundant module Maintenance status (MS) 1 Maintenance status (MS) 2 1 = error rack 1 1 = error rack 2
Data type Default
DWORD
0
DWORD
0
BOOL
0
BOOL
0
BOOL
0
BOOL
0
Output parameters
I/O (parameter) ACTIV_H ACTIV_L CH_INF_H CH_INF_L MODUL_STATUS_WORD RETURN_ VAL
Meaning
1 = module with more significant address is active 1 = module with less significant address is active 1 = channel with more significant address is active 1 = channel with less significant address is active Status information Error information
Data type Default
BOOL
0
BOOL
0
DWORD
0
DWORD
0
WORD
0
INT
0
Additional information You will find more information in: Maintenance status MS (Page 533)
478
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
6.94
Family: @System 6.94 RED_MF: Status processing of redundant multi function modules
RED_MF: Status processing of redundant multi function modules
6.94.1
Description of RED_MF
Object name (type + number) FB 441 · I/Os of RED_MF (Page 480)
Area of application Diagnosis of the redundant multi function modules.
Calling OBs
The block must be installed in the following OBs (performed automatically in CFC):
OB 3x OB 100 OB 72 OB 80 OB 85
Cyclic interrupt OB (Channel OB) New restart CPU-Redundancy Error (only in H-Systems) "Time error-OB" (only in Single-Mode) Program sequence error
Configuration
The following actions are executed automatically with the "Generate module drivers" CFC function:
· The OB_BEGIN block`s OUT-Structure CPU_DIAG/CPU_DIAG_80 is interconnected with the identically named IN_OUT-Structure of the RED_xxx-block.
· The OUT-Structure MOD_INF of the upstream MOD-block is interconnected with the MOD_INF1/MOD_INF2 IN_OUT-Structure of the RED_xxx-block.
· The input parameters LADDR_Mas, LADDR_Slv, PER_TYPE, PAR_PROI, CHAN_NUM, CHAN_BITS, DIS_TIME, VAL_UNIT, DIS_PERC, CHAN_MAS, EXEC_TIM, CHAN01..08_S are parameterised with the values set in HW config.
· The input parameters MODF1, MODF2, MODE1_00..07, MODE2_00..07 are interconnected with the correspondent output parameters of the previous block
Error handling The plausibility of input parameters is not checked.
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
479
Family: @System 6.94 RED_MF: Status processing of redundant multi function modules
Block functions The RED_MF block processes the status of all channels cyclically based on the outputs OMODE_xx or the MOD_x blocks and then forms the information on redundancy of the OR blocks.
Message response Not available
6.94.2
I/Os of RED_MF
The factory setting of the block display in CFC is identified in the "I/O" column: I/O name in bold characters = I/O is visible; I/O name in standard characters = I/O is hidden.
You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15)".
Input parameters
I/O (parameter) CH_INF_Mas CH_INF_Slv LADDR_Mas LADDR_Slv LADDR_DQ_Mas LADDR_DQ_Slv MODF1 MODF2 MULTI_CHN QI_INFO PER_TYPE PAR_PROI CHAN_NUM CHAN_BIT DIS_TIME RESERVE1 R_TO_TD VAL_UNIT RESERVE2 DIS_PERC CHAN_MAS EXEC_TIM CHANxx_S
Meaning
Master address: 1 = Channel x active Slave address: 1 = Channel x active Master module address Slave module address Master Module Address - DQ Slave Module Address - DQ 1=Module 1 pulled / out of order 1=Module 2 pulled / out of order 1=Multiple channels 1= Quality info active Reserve Process image partition Total number of channels -1 Reserve Reserve Reserve 1 Reserve Reserve Reserve 2 Reserve Reserve Reserve Reserve (xx = 01 - 16)
Data type Default
DWORD
0
DWORD
0
INT
0
INT
0
WORD
0
WORD
0
BOOL
0
BOOL
0
BYTE
0
BYTE
0
BYTE
0
BYTE
0
BYTE
0
BYTE
0
WORD
0
BYTE
0
BYTE
0
BYTE
0
BYTE
0
BYTE
0
WORD
0
WORD
0
WORD
0
480
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
I/O (parameter) CHAN_AV ADDL_AV ADDH_AV MODE1_xx MODE2_xx FEATURE HART8_VAR
In/Out parameters
I/O (parameter) CPU_DIAG_PN CPU_DIAG_80 MOD_INF1 MOD_INF2 DIAG_INF_1 DIAG_INF_2 ACC_MODE
Out parameters
I/O (parameter) QERR QACTIV_L QACTIV_H QMOD_CH_L QMOD_CH_H QLADDR_L QLADDR_H
QCH_INF_L QCH_INF_H QUN_OV_L
QUN_OV_H
QDIS_EXPIRE QCH_DISCREP QPER_TYPE QPAR_PROI
Family: @System 6.94 RED_MF: Status processing of redundant multi function modules
Meaning
Data type Default
Reserve
INT
0
Reserve
INT
0
Reserve
INT
0
Module 1 mode channel xx (xx = 00 - 31) DWORD
0
Module 2 mode channel xx (xx = 00 - 31) DWORD
0
Features of the hardware parameters
DWORD
0
1 = 8 HART
BOOL
0
Meaning
Data type Default
System structure
STRUCT
-
Time error OB start information
STRUCT
-
Module 1 information structure
STRUCT
-
Module 2 information structure
STRUCT
-
Module Diagnostic Information Structure STRUCT
-
Module Diagnostic Information Structure STRUCT
-
1 = Accept new mode settings
BOOL
0
Meaning
Data type Default
1=Runtime error
BOOL
1
1=Low Module Active
BOOL
0
1=High Module Active
BOOL
0
Status of the channels of the 1st module BOOL
0
Status of the channels of the 2nd module BOOL
0
Lower address (address that the user uses) WORD
0
Higher address (address of the redundant WORD
0
module)
Status of the channels of the 1st module DWORD
0
Status of the channels of the 2nd module DWORD
0
Underflow / overflow status of the channels DWORD
0
of the L module
Underflow / overflow status of the channels DWORD
0
of the H module
Reserve
DWORD
0
Reserve
DWORD
0
Reserve
BYTE
0
Partial process image
BYTE
0
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
481
Family: @System 6.95 SUBNET: DP master system monitoring
I/O (parameter)
QCHAN_NUM QCHAN_BIT QDIS_TIME QVAL_UNIT QDIS_PERC QCHAN_MAS QEXEC_TIM MODUL_STATUS DEPASS_RED RETURN_VAL QCH_VAL_xx QCH_LV_VAL_DI_xx QCH_LV_VAL_xx QVALxx_L QVALxx_H CH_INF_Mas_AUX_0 CH_INF_Slv_AUX_0 QMODF1 QMODF2
Meaning
Data type Default
Total number of channels -1
BYTE
0
Reserve
BYTE
0
Reserve
WORD
0
Reserve
BYTE
0
Reserve
BYTE
0
Reserve
WORD
0
Reserve
WORD
0
MODUL_STATUS
DWORD
0
Depassivation
BOOL
0
Return Value
INT
0
Reserve (xx = 00 - 15)
BYTE
255
Reserve (xx = 00 - 15)
BOOL
0
Reserve (xx = 00 - 15)
WORD
0
Reserve (xx = 00 - 15)
WORD
0
Reserve (xx = 00 - 15)
WORD
0
Master address aux value 0..31: 1 = active DWORD
0
Slave address aux value 0..31: 1 = active DWORD
0
1 = Module 1 Removed / Out of Order
BOOL
0
1 = Module 2 Removed / Out of Order
BOOL
0
6.95
SUBNET: DP master system monitoring
6.95.1
Description of SUBNET
Object name (type + number) FB 106 · SUBNET block I/Os (Page 485)
Area of application
The SUBNET block is used to shorten acyclic OB processing times. Only the blocks that are actually affected can be called in the case of an acyclic event.
Calling OBs
The SUBNET block must be installed in the run sequence in the following OBs:
OB 1 OB 55
Cyclic program Status interrupt (only if a DP/PA slave is required)
482
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.95 SUBNET: DP master system monitoring
OB 56 OB 57 OB 70 OB 72 OB 81 OB 82 OB 83 OB 85 OB 86 OB 100
Update interrupt (only if a DP/PA slave is required) Vendor-specific alarm (only if a DP/PA slave is required) I/O redundancy error CPU redundancy error Power supply error Diagnostic interrupt Insert/remove module interrupt Program execution error Rack failure Warm restart
Use in CFC
The following actions are executed automatically with the "Generate module drivers" CFC function:
· Runtime groups with driver/system blocks are created and organized by rack.
· The SUBN1_ID, SUBN2_ID and SUBN_TYP inputs are configured.
· The EN_Rxxx outputs are interconnected with the relevant blocks (e.g., RACK).
· The IN_OUT structure CPU_DIAG is interconnected with the OUT structure of the OB_BEGIN block.
· The IN_OUT structure SZL_71 is interconnected with the OUT structure of the OB_BEGIN block.
· The OUT structure SUB_DIAG is interconnected with the IN_OUT structures of the affected blocks (such as RACK).
Function and method of operation
The SUBNET block monitors a DP master system, and enables the blocks (such as RACK) for processing the connected DP slaves (such as ET 200M). Corresponding messages are generated, and the SUBN1ERR and SUBN2ERR outputs are set if a DP master system fails or loses redundancy. The SUB_DIAG output structure contains the geographic address of the DP Master system 1 (and of DP Master system 2 in H systems), as well as the group error information SUBN0_ERR (for DP master system 1) and SUBN1_ERR (for DP master system 2). If SUBN0_ERR = 1 or SUBN1_ERR = 1, the corresponding DP master system is not available.
The SUBNET block is installed in each connected DP master system or in the OBs listed above once for the local I/O devices. It is enabled by OB_BEGIN. Start and diagnostic information is read from the CPU_DIAG structure. It is interconnected with the CPU_DIAG structure of the OB_BEGIN. The SUBNET block is assigned one enable output for each connectable rack or DP Master system (for each expansion rack for central I/Os). It uses the start information of the calling OB to determine whether the reported event occurred at its DP master (or at the central I/O), and then sets the output for the affected rack or DP master system (EN_Rxxx).
If redundant DP master systems are used (for H CPUs only), a rack (such as ET 200M) is connected to the two DP masters, and is assigned the same station number at both. The SUBNET block has two input parameters (SUBNx_ID), and the type identifier SUBN_TYP for this function. If the
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
483
Family: @System 6.95 SUBNET: DP master system monitoring
integrated interface of the CPU module is the DP master, SUBN_TYP = FALSE, otherwise SUBN_TYP = TRUE.
The MASTER_0 and MASTER_1 outputs indicate which CPU is currently the master.
If a DP master fails, the system sets all EN_Rxxx = TRUE, and reports a redundancy loss or failure. The return of redundancy or the DP master is reported when a failed DP slave has reestablished the connection.
The status of the DP master system, the set SUBNx_ID and type identifier are saved in the output structure SUB_DIAG.
If a "power supply error" (OB 81) event occurs, the SUBNET block will enable only those RACK blocks that are expansion racks, which is indicated by SUBNx_ID = 0.
Note: If you want to change the SUBN1_ID (connection to CPU 0) and SUBN2_ID (connection to CPU 1) inputs online, you must set input ACC_ID = TRUE. to update the output values.
Redundancy
The SUBNET block supports redundancy of DP master systems of the 414-H/417-H CPU if distributed I/Os are used. To use this function, you must configure the SUBN1_ID (connection to CPU 0) and SUBN2_ID (connection to CPU 1) inputs with the numbers of the redundant DP master systems. If there is no redundancy, the remaining input must be assigned the value 16#FF (default).
Error handling
Error handling for the block is limited to the evaluation of the error information of ALARM_8P. You will find additional information about error handling in the "Error information of output parameter MSG_STAT (Page 530)" section.
Startup/initial startup behavior
The SUBNET block initializes the messages of ALARM_8P.
The operating mode of the DP Master system is checked, and entered in the SUB_DIAG.V1_MODE structure with SSL 0X90H (0 = compatibility mode, 1 = DPV1 mode). If DPV1 mode is active, the CPU_DIAG.MODE_V1 structure is also set to TRUE.
Overload behavior
The SUBNET block counts the OB 86 calls (failures only). The counter is reset in OB1. If more than two OB 86 failure events occur in succession before the cycle control point (OB1) is reached, these are rejected and a message "Failure OB 86 DP master system:x" is output. If an OB 86 call is rejected, the DP master system is registered as having failed.
Time response Not available
484
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.95 SUBNET: DP master system monitoring
Message response After being called by an OB 86, OB 70 and OB 72, the block analyzes the status of its assigned DP master system, and generates the relevant messages for redundancy loss or DP master system failure by broadcasting an ALARM_8P. The message function can be disabled by setting EN_MSG = FALSE. The SUBNET block generally reports only events triggered in the DP master system it monitors. Exception: If a CPU fails in the H system, the following messages are generated: · in a non-redundant DP master system: "DP master failure" message · in a redundant DP master system: "DP master redundancy loss" message
Operator control and monitoring If asset management is used in the project and the diagnostic screens have been generated, the faceplate can be called via its block icon. For additional information, refer to the "Process Control System PCS 7; Maintenance Station" manual.
Additional information For additional information, refer to the sections: Message texts and associated values of SUBNET (Page 487) Maintenance status MS (Page 533)
6.95.2
I/Os of SUBNET
The factory setting of the block display in the CFC is identified in the "I/O" column: I/O name bold = I/O visible, I/O name normal = I/O not visible.
You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15)".
Input parameters
I/O (parameter) DIAG_BUF
EN_MSG EV_ID FEATURE MS SUBN_TYP
Meaning
Data type
Entry in diagnostic buffer (relevant for maintenance person- BOOL nel)
1 = enable message
BOOL
Message number
DWORD
Hardware feature parameter
WORD
Maintenance status
DWORD
1 = external DP interface
BOOL
De- fault 0
1 0 0 0 0
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
485
Family: @System 6.95 SUBNET: DP master system monitoring
I/O (parameter)
SUBN1_ID
SUBN2_ID
Meaning
ID of the primary DP master system ID of the redundant DP master system
Data type
BYTE BYTE
De- fault
255
255
Output parameters
I/O (parameter) CPU0LED1 CPU0LED2 CPU0LED3 CPU0LED4 CPU0LED5 CPU1LED1 CPU1LED2 CPU1LED3 CPU1LED4 CPU1LED5 EN_Rxxx MASTER_0 MASTER_1 MSG_STAT O_MS SUB_DIAG SUBN1ERR SUBN2ERR
Meaning
LED 1 set on CPU 0 LED 2 set on CPU 0 LED 3 set on CPU 0 LED 4 set on CPU 0 LED 5 set on CPU 0 LED 1 set on CPU 1 LED 2 set on CPU 1 LED 3 set on CPU 1 LED 4 set on CPU 1 LED 5 set on CPU 1 1 = Enable rack (xxx = 0 - 127) 1 = Master CPU in rack 0 1 = Master CPU in rack 1 Message error information Maintenance status System structure: CPU diagnostics 1 = Error in DP master system 1 1 = Error in DP master system 2
Data type
DWORD DWORD DWORD DWORD DWORD DWORD DWORD DWORD DWORD DWORD BOOL BOOL BOOL WORD DWORD STRUCT BOOL BOOL
De- fault 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0
In/out parameters
I/O (parameter) ACC_ID CPU_DIAG CPU_OB_5X READ_LED SZL_71
Meaning
1 = accept MODE settings CPU diagnostics OB_5x startup information 1 = Reading LED status System structure SZL71
Data type
BOOL STRUCT STRUCT BOOL STRUCT
De- fault 0
0
Note
The maximum number of racks is determined by the address volume of PROFIBUS. All available CPUs can thus be used. The entire address volume is used by the CPU 417-4.
486
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.95 SUBNET: DP master system monitoring
Additional information For additional information, refer to the sections: Message texts and associated values of SUBNET (Page 487) Maintenance status MS (Page 533)
6.95.3
Message texts and associated values of SUBNET
Assignment of message text and message class
Message no. 1 2 3 4 5 6 7 8
Default message text DP master @1%d@: Redundancy loss DP master @2%d@: Redundancy loss DP master @1%d@: Failure DP master @2%d@: Failure DP master @2%d@: Multiple failure CPU loss of redundancy in rack @4%d@
Message class PLC Process Control Message - Error PLC Process Control Message - Error PLC Process Control Message - Failure PLC Process Control Message - Failure PLC Process Control Message - Failure PLC Process Control Message - Error No message No message
Assignment of associated values
Associated value 1 2 3 4
Block parameters ID of the primary DP master system (SUBN1_ID) ID of the redundant DP master system (SUBN2_ID) Multiple failure, ID of DP master system CPU rack number
See also
Message Classes (Page 531)
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
487
Family: @System 6.96 SUBNET_PN: Monitoring of the PN IO system
6.96
SUBNET_PN: Monitoring of the PN IO system
6.96.1
Description of SUBNET_PN
Object name (type + number) FB 82 · I/Os of SUBNET_PN (Page 488)
Area of application
The SUBNET_PN block is used to reduce acyclic OB processing times. Only the blocks that are actually affected can be called in the case of an acyclic event.
6.96.2
I/Os of SUBNET_PN
The factory setting of the block display in the CFC is identified in the "I/O" column: I/O name bold = I/O visible, I/O name normal = I/O not visible.
You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15)".
Input parameters
I/O (parameter) DADDR DADDR_1
DIAG_BUF
EN_MSG EV_ID EV_ID1 FEATURE MS PNIO_ADR
PORT1_ADR PORT2_ADR PORT3_ADR PORT1_CONNECT PORT2_CONNECT
Meaning
Data type
Diagnostic address of the PN IO device - primary subnet INT
Diagnostic address of the PN IO device - redundant INT subnet
Entry in diagnostic buffer (relevant for maintenance BOOL personnel)
1 = enable message
BOOL
Message number ALARM_8P (assigned by the ES)
DWORD
Message number ALARM_8P (assigned by the ES)
DWORD
Hardware feature parameter
WORD
Maintenance status
DWORD
Diagnostic address of the PN-IO interface - Primary INT subnet
Diagnostics address of the first port - Primary subnet INT
Diagnostics address of the second port - Primary subnet INT
Diagnostics address of the third port - Primary subnet INT
Connection status of the first port - Primary subnet BYTE
Connection status of the second port - Primary subnet BYTE
De- fault 0 0
0
1 0 0 0 0 0
0 0 0 0 0
488
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.96 SUBNET_PN: Monitoring of the PN IO system
I/O (parameter) PORT3_CONNECT PNIO_ADR_1
PORT1_ADR_1 PORT1_CONNECT_1 PORT2_ADR_1
PORT2_CONNECT_1
SUBN_TYP SUBN1_ID SUBN2_ID
Meaning
Data type
Connection status of the third port - Primary subnet BYTE
Diagnostic address of the PN-IO interface - Redundant INT subnet
Diagnostics address of the first port - Redundant subnet INT
Connection status of the first port - Redundant subnet BYTE
Diagnostics address of the second port - Redundant INT subnet
Connection status of the second port - Redundant sub- BYTE net
1 = external PN interface
BOOL
ID of the Primary subnet
BYTE
ID of the Redundant subnet
BYTE
De- fault 0 0
0 0 0
0
0 255 255
Output parameters
I/O (parameter) CPU0LED1 CPU0LED2 CPU0LED3 CPU0LED4 CPU0LED5 CPU1LED1 CPU1LED2 CPU1LED3 CPU1LED4 CPU1LED5 EN_Rxxx MASTER_0 MASTER_1 MSGSTATx O_MS QMSGERx SUB_DIAG SUBN1ERR SUBN2ERR
Meaning
LED 1 set on CPU 0 LED 2 set on CPU 0 LED 3 set on CPU 0 LED 4 set on CPU 0 LED 5 set on CPU 0 LED 1 set on CPU 1 LED 2 set on CPU 1 LED 3 set on CPU 1 LED 4 set on CPU 1 LED 5 set on CPU 1 1 = Enable rack (xxx = 0 - 255) 1 = Master CPU in rack 0 1 = Master CPU in rack 1 STATUS output of ALARM_8P_x (x = 1 - 2) Maintenance status ERROR message of ALARM_8P_x (x = 1 - 2) System structure: CPU diagnostics 1 = Subnet 1 failure 1 = Subnet 2 failure
Data type
DWORD DWORD DWORD DWORD DWORD DWORD DWORD DWORD DWORD DWORD BOOL BOOL BOOL WORD DWORD BOOL STRUCT BOOL BOOL
De- fault 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
489
Family: @System 6.96 SUBNET_PN: Monitoring of the PN IO system
In/out parameters
I/O (parameter) ACC_ID CPU_DIAG_PN CPU_OB_5X_PN READ_LED SZL_71 CPU_OB_5X_PN
Meaning
1 = accept MODE settings CPU diagnostics system structure Start information OB 55, OB 56, OB 57 1 = Reading LED status System structure SZL71 OB_5x-Startinformation
Additional information For additional information, refer to the sections: Message texts and associated values of SUBNET_PN (Page 490) Maintenance status MS (Page 533)
Data type
BOOL STRUCT STRUCT BOOL STRUCT STRUCT
De- fault 0
0
6.96.3
Message texts and associated values of SUBNET_PN
Assignment of message text and message class The process control messages of ALARM_8P with EV_ID are assigned as follows:
Message number 1 2 3 4 5 6 7 8
Default message text
Message class
PN IO system @1%d@: Redundancy loss PLC Process Control Message - Error
PN IO system @2%d@: Redundancy loss PLC Process Control Message - Error
PN IO system @1%d@: Failure
PLC Process Control Message - Failure
PN IO system @2%d@: Failure
PLC Process Control Message - Failure
PN IO system @2%d@: Multiple failure PLC Process Control Message - Failure
CPU loss of redundancy in rack @4%d@ PLC Process Control Message - Error
PN-IO system @3%d@: Port 3 Error
PLC Process Control Message - Error
PN-IO system @1%d@/@2%d@: Commu- PLC Process Control Message - Error nication error (AR)
Associated values of ALARM_8P with EV_ID
Associated value 1 2 3 4
Block parameter ID of the primary PN IO system (SUBN1_ID) ID of the redundant PN IO system (SUBN2_ID) ID of the multiple failure PN IO system CPU rack number
Data type BYTE BYTE BYTE BYTE
490
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @System 6.97 WRDS_CO: Coordinates WRREC DS128 for MRC
The process control messages of ALARM_8P with EV_ID1 are assigned as follows:
Message number 1 2 3
4
5 6 7
8
Default message text
Message class
PN IO system @1%d@: Port 1 error
PLC Process Control Message - Error
PN IO system @1%d@: Port 2 error
PLC Process Control Message - Error
PN IO system @1%d@: Maintenance de- PLC Process Control Message - Error manded (PN-IO)
PN IO system @1%d@: Maintenance re- Preventative Maintenance - Standard quired (PN-IO)
PN IO system @2%d@: Port 1 error
PLC Process Control Message - Error
PN IO system @2%d@: Port 2 error
PLC Process Control Message - Error
PN IO system @2%d@: Maintenance de- PLC Process Control Message - Error manded (PN-IO)
PN IO system @2%d@: Maintenance re- Preventative Maintenance - Standard quired (PN-IO)
Associated values of ALARM_8P with EV_ID1
Associated value 1 2 3
Block parameter ID of the primary PN IO system (SUBN1_ID) ID of the redundant PN IO system (SUBN2_ID) ID of the PN IO system
Data type BYTE BYTE WORD
You can find additional information in the section: Message Classes (Page 531).
6.97
WRDS_CO: Coordinates WRREC DS128 for MRC
6.97.1
Description of WRDS_CO
Object name (type + number) FB 147 · I/Os of WRDS_CO (Page 492)
Area of application
This function block coordinates the requests for new Measuring Range Center (MRC) values from different instances of the APL channel block Pcs7AITC.
Configuration The WRDS_CO function block is used in PROFIBUS DP and PROFINET environment.
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
491
Family: @System 6.97 WRDS_CO: Coordinates WRREC DS128 for MRC
The following actions are executed automatically with the "Generate module drivers" CFC function: · The function block is installed in OB1, OB100 and OB72 (if available). · The MODExx (xx=channel number 0...7) input parameter is interconnected with
the OMODE_xx output parameter of the MOD function block. · The following diagnostic structures are automatically interconnected:
CPU_DIAG (PROFIBUS DP) or CPU_DIAG_PN (PROFINET) RAC_DIAG and SUB_DIAG. · The WRDS_CO function block is also connected to the QRACKF and QMODF output parameters with its input parameter RACKF and MODF as it is additionally used with the MOD function block. · The MRC_XCHG output parameter is interconnected with MRC_XCHG of the Pcs7AITC instances that belong to the same module. · The LADDR input parameter is parameterized with the logical input address of the module. · The CHAN_NUM input parameter is parameterized with the highest channel number. For example: If it is parameterized with 3, that means there are 0...3 channels or 4 channels in whole.
Error handling The output parameter QERR displays a runtime error.
Block functions The WRDS_CO function block coordinates the MRC requests from different Pcs7AITC instances. The WRDS_CO function block along with Pcs7AITC ensures that in each case, the MRC values in the module and in the channel blocks remain the same.
6.97.2
I/Os of WRDS_CO
The factory setting of the block display in the CFC is identified in the "I/O" column:
I/O name bold = I/O visible, I/O name normal = I/O not visible.
You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15)".
Input parameters
Parameter name LADDR
CHAN_NUM
Data type INT
INT
Initial value -1
0
Description
Logical base adress mas- ter module
Total number of chan- nels -1
492
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Parameter name RACKF MODF MODExx DIAG_BUF
FEATURE CPU_DIAG CPU_DIAG_PN
Output parameters
Parameter name QERR QERR_INF MRC_XCHG
In_Out parameters
Parameter name SUB_DIAG RAC_DIAG ACC_MODE
Family: @System 6.97 WRDS_CO: Coordinates WRREC DS128 for MRC
Data type BOOL BOOL
DWORD
DWORD
DWORD
CPU_DIAG CPU_DIAG_PN
Initial value 0 0 0 0
0
Description
1 = Higher - level error
1 = Module removed / Out of Order
Channel xx mode (xx = 00...07)
1=CPU Diagnostic Buffer entry on (relevant for service personnel)
Hardware information (Reserved)
Data type BOOL INT MRC_XCHG
Initial value 0 0
Description
Error
Error information
Coordinates WRREC DS128 with new 'mea- suring range center'
Data type SUB_DIAG RAC_DIAG BOOL
Initial value 0
Description
1=Accept new mode set- tings
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
493
Family: @System 6.97 WRDS_CO: Coordinates WRREC DS128 for MRC
494
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @PAM
7
7.1
FB_DB_CD: Interface FB for DB_PAM_CD
7.1.1
Description of FB_DB_CD
Object name (type + number) FB 27 · I/Os of FB_DB_CD (Page 497)
Functions
The FB_DB_CD block acts as an interface to transfer data from the user program in the package unit to the DB_PAM_CD block.
How it works
The FB_DB_CD block acts as an interface to transfer data from the user program in the package unit to the DB_PAM_CD block. It can be used if CFC configuration is available in the package unit. The various input values are: · Identity (LID) · Global Part (GP) · Detail Diagnosis (DD) · Status information (STAT) · Analog Values (PV) The input "Identity" contains the following information: · bit1 OKZ string · bit2 Connection Point (CP) · bit3 Object Type (OT) The input "Global Part" contains the following information: · bit1 Maintenance alarm · bit2 Maintenance demand · bit3 Maintenance request · bit4 Out of order · bit5 Passivated
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
495
Family: @PAM 7.1 FB_DB_CD: Interface FB for DB_PAM_CD
· bit6 Function control · bit7 Configuration changed · bit8 Unknown · bit9 Redundancy error · bit10-16 Reserve The input "Detail Diagnosis" contains the following information: · bit1-bit16 single information (bool, is directly proportional to the position in the text library). The input "Status Information" contains the following information: · Pos. 01 Application/device with define shut down · Pos. 02 Archive/save function active · Pos. 03 08 single information The input "Analog Values" contains the following information: · bit1 Value 1 · bit 2 State 1 · bit3 Unit 1 · bit4 Value 2 · bit5 State · bit6 Unit 2 · bit7 Value 3 · bit8 State 3 · bit9 Unit 3
Configuration
You must enter the value of the destination data block to which the values are to be transferred at the input parameter DBNO.
Error handling
The value of QERR = 1 represents a runtime error. The ERR_NUM I/O is used to obtain the following errors in output:
Error number -1 0 1
2
Meaning of the error number
Predefined value when inserting the block; block is not processed.
There is no error.
The value entered at input parameter DBNO is not correct. DB length <> 160 bytes.
A date block with the value entered at input parameter DBNO does not exist. (DBNO = 0 is not allowed).
496
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @PAM 7.1 FB_DB_CD: Interface FB for DB_PAM_CD
Startup characteristics The operation is suppressed after startup for the number of cycles set at RunUpCyc.
Modes
Not available
Time response Not available
Message response Not available
Opearator control and monitoring Not available
7.1.2
I/Os of FB_DB_CD
The factory setting of the block display in the CFC is identified in the "I/O" column:
I/O name bold = I/O visible, I/O name normal = I/O not visible.
You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15)".
Input parameters
I/O Parameter LID CP GP DD STAT PV0_VALUE PV0_ST PV0_UNIT PV1_VALUE PV1_ST PV1_UNIT PV2_VALUE PV2_ST
Meaning
Type
LID Connection point Global part Detail diagnosis Status information Process value 0 State of Process value 0 Unit of Process value 0 Process value 1 State of Process value 1 Unit of Process value 1 Process value 2 State of Process value 2
STRING[64] STRING[64] WORD WORD BYTE REAL BYTE INT REAL BYTE INT REAL BYTE
Default
'' '' 16#0000 16#0000 0 99.99 0 1 99.99 0 1 99.99 0
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
497
Family: @PAM 7.2 FB_DB_CPU: Interface FB for DB_PAM_CPU
I/O Parameter PV2_UNIT RUNUPCYC
DIAG_BUF
FEATURE DBNO
Meaning
Type
Unit of Process value 2
Number of Run Up Cy- cles
1= CPU Diagnostic Buf- fer entry on (relevant for service personnel)
Feature parameter
DB number
INT INT BOOL
DWORD INT
Output parameters
I/O Parameter QERR WR_BUSY RET_VAL2
ERR_NUM
Meaning
1 = Runtime error BUSY of WRIT_DBL Return value of WRIT_DBL Error Number
Type
BOOL BOOL INT
INT
In/Out parameters
I/O Parameter ACC_MODE
Meaning
Type
1 = Accept new settings BOOL
Default 1 1 1
16#00000000 1
Default 1 1 1 1
Default 1
7.2
FB_DB_CPU: Interface FB for DB_PAM_CPU
7.2.1
Description of FB_DB_CPU
Object name (type + number) FB 132 · I/Os of FB_DB_CPU (Page 500)
Functions
The FB_DB_CPU block acts as an interface to transfer data from the user program in the package unit to the DB_PAM_CPU block.
498
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @PAM 7.2 FB_DB_CPU: Interface FB for DB_PAM_CPU
How it works
The FB_DB_CPU block acts as an interface to transfer data from the user program in the package unit to the DB_PAM_CPU block. It can be used if CFC configuration is available in the package unit. The various input values are: · Identity (LID) · Global Part (GP) · Detail Diagnosis (DD) · Analog values (PV) The input "Identity" contains the following information: · bit1 OKZ string · bit2 Connection Point (CP) · bit3 Object Type (OT) The input "Global Part" contains the following information: · bit1 Maintenance alarm · bit2 Maintenance demand · bit3 Maintenance request · bit4 Reserved · bit5 Reserved · bit6 Function control · bit7 Configuration changed · bit8 Unknown · bit9 Redundancy error · bit10 Productinfo Single/Red · bit11 Productinfo Rack 0/1 · bit12-16 Reserve (Status Information) The input "Detail Diagnosis" contains the following information: · bit1-bit16 single information (bool, is directly proportional to the position in the text library). The input "Analog Values" contains the following information: · bit1 Value 1 · bit 2 State 1 · bit3 Unit 1 · bit4 Value 2 · bit5 State · bit6 Unit 2 · bit7 Value 3
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
499
Family: @PAM 7.2 FB_DB_CPU: Interface FB for DB_PAM_CPU
· bit8 State 3 · bit9 Unit 3
Configuration
You must enter the value of the destination data block to which the values are to be transferred at the input parameter DBNO.
Error handling The ERR_NUM I/O is used to obtain the following errors in output:
Error number -1 0 1
2
Meaning
Predefined value when inserting the block; block is not processed.
There is no error.
The value entered at input parameter DBNO is not correct. The length of data block <> 160 Bytes.
A data block with the value entered at input parameter DBNO does not exist. (DBNO = 0 is not allowed).
Startup characteristics The operation is suppressed after startup for the number of cycles set at RunUpCyc.
Modes
Not available
Time response Not available
Message response Not available
Opearator control and monitoring Not available
7.2.2
I/Os of FB_DB_CPU
The factory setting of the block display in the CFC is identified in the "I/O" column: I/O name bold = I/O visible, I/O name normal = I/O not visible.
500
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @PAM 7.2 FB_DB_CPU: Interface FB for DB_PAM_CPU
You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15)".
Input parameters
I/O Parameter LID CP GP DD PV0_VALUE PV0_ST PV0_UNIT PV1_VALUE PV1_ST PV1_UNIT PV2_VALUE PV2_ST PV2_UNIT RESERVE_00 RUNUPCYC
DIAG_BUF
FEATURE DBNO
Meaning
Type
LID Connection point Global part Detail diagnosis Process value 0 State of Process value 0 Unit of Process value 0 Process value 1 State of Process value 1 Unit of Process value 1 Process value 2 State of Process value 2 Unit of Process value 2 Reserve Number of Run Up Cy- cles 1= CPU Diagnostic Buf- fer entry on (relevant for service personnel) Feature parameter DB number
STRING[64] STRING[64] WORD WORD REAL BYTE INT REAL BYTE INT REAL BYTE INT BYTE INT
BOOL
DWORD INT
Default
`' `' 16#0000 16#0000 99.99 1 1 99.99 1 1 99.99 0 1 0 1
1
16#00000000 1
Output parameters
Parameter QERR WR_BUSY RET_VAL2
ERR_NUM
Meaning
1 = Runtime error BUSY of WRIT_DBL Return value of WRIT_DBL Error Number
Type BOOL BOOL INT
INT
default value 1 1 1
1
In/Out parameters
I/O Parameter ACC_MODE
Meaning
Type
1 = Accept new settings BOOL
Default 1
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
501
Family: @PAM 7.3 FB_DB_IM: Interface FB for DB_PAM_IM
7.3
FB_DB_IM: Interface FB for DB_PAM_IM
7.3.1
Description of FB_DB_IM
Object name (type + number) FB 28 · I/Os of FB_DB_IM (Page 504)
Functions
The FB_DB_IM block acts as an interface to transfer data from the user program in the package unit to the DB_PAM_IM block.
How it works
The FB_DB_IM block acts as an interface to transfer data from the user program in the package unit to the DB_PAM_IM block. It can be used if CFC configuration is available in the package unit. The various input values are: The various input values are: · Identity (LID) · Global Part (GP) · Detail Diagnosis (DD) · Status information (STAT) · Signal Module information (SM) The input "Identity" contains the following information: · bit1 OKZ string · bit2 Connection Point (CP) · bit3 Object Type (OT) The input "Global Part" contains the following information: · bit1 Maintenance alarm · bit2 Maintenance demand · bit3 Maintenance request · bit4 Out of order · bit5 Passivated · bit6 Function control · bit7 Configuration changed · bit8 Unknown
502
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @PAM 7.3 FB_DB_IM: Interface FB for DB_PAM_IM
· bit9 Redundancy error · bit10 - bit16 Reserve The input "Detail Diagnosis" contains the following information: · bit1-bit16 single information (bool, is directly proportional to the position in the text library). The input "Status Information" contains the following information: · bit1 Application/device with define shut down · bit2 Archive/save function active · bit3-bit8 single information The input "Signal Module" contains the following information: · bit3 Signal Module 0-31 error · bit4 Signal Module 32-63 error
Configuration
You must enter the value of the destination data block to which the values are to be transferred at the input parameter DBNO.
Error handling
The value of QERR = 1 represents a runtime error. The ERR_NUM I/O is used to obtain the following errors in output:
Error number -1 0 1
2
Meaning of the error number
Predefined value when inserting the block; block is not processed.
There is no error.
The value entered at input parameter DBNO is not correct. DB length <> 160 Bytes.
A data block with the value entered at input parameter DBNO does not exist. (DBNO = 0 is not allowed).
Startup characteristics The operation is suppressed after startup for the number of cycles set at RunUpCyc.
Modes
Not available
Time response Not available
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
503
Family: @PAM 7.3 FB_DB_IM: Interface FB for DB_PAM_IM
Message response Not available
Opearator control and monitoring Not available
7.3.2
I/Os of FB_DB_IM
The factory setting of the block display in the CFC is identified in the "I/O" column:
I/O name bold = I/O visible, I/O name normal = I/O not visible.
You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15)".
Input parameters
I/O Parameter LID CP GP DD STAT SM_NOK1
SM_NOK2
RESERVE_00 RESERVE_01 PV0_VALUE PV0_ST PV0_UNIT RUNUPCYC
DIAG_BUF
FEATURE DBNO
Meaning
Type
LID
STRING[64]
Connection point
STRING[64]
Global part
WORD
Detail diagnosis
WORD
Status information
BYTE
Signal module 0-31 er- DWORD ror
Signal module 32-63 er- DWORD ror
Reserve
DWORD
Reserve
WORD
Process value 0
REAL
State of Process value 0 BYTE
Unit of Process value 0 INT
Number of Run Up Cy- INT cles
1= CPU Diagnostic Buf- BOOL fer entry on (relevant for service personnel)
Feature parameter
DWORD
Data block number
INT
Default
'' '' 16#00000000 16#00000000 0 16#00000000
16#00000000
16#00000000 016#0000 99.99 0 1 1
1
16#00000000 1
504
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Output parameters
I/O Parameter QERR WR_BUSY RET_VAL2
ERR_NUM
In/Out parameters
I/O Parameter ACC_MODE
Family: @PAM 7.4 PAM_IF: Interface block to PAM Diagnostic Blocks
Meaning
1 = Runtime error BUSY of WRIT_DBL Return value of WRIT_DBL Error Number
Type
BOOL BOOL INT
INT
Default
1 1 1
1
Meaning
Type
1 = Accept new settings BOOL
Default 1
7.4
PAM_IF: Interface block to PAM Diagnostic Blocks
7.4.1
Description of PAM_IF
Object name (type + number) FB 29 · I/Os of PAM_IF (Page 509)
Functions
The PAM_IF block: · Transfers upto three analog process variables (PV0, PV1, and PV2) for monitoring purposes. · Transfers MS_Ext for processing and corresponding display in the operator station.
How it works
The PAM_IF block transfers upto three analog values between PAM driver blocks (PAM_CPU / PAM_CD / PAM_IM / PAM_SM) and PAM_IF blocks for further processing. Additionally, you can perform the following using this block:
Limit monitoring with hysteresis
You can define a hysteresis for all the limit monitoring functions (using parameter PVx_Hyst (x: 0...2)).
An example to use the hysteresis is to suppress signal flutter. For this, you can enter the hysteresis as a physical variable at the block.
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
505
Family: @PAM 7.4 PAM_IF: Interface block to PAM Diagnostic Blocks
Suppressing messages using the MsgLock parameter You can suppress the messages as follows: · Bit = 0: Messages are not suppressed. · Bit = 1: All messages (MS_Ext, PVx messages) are suppressed. If MsgLock = 1, · The PV signal status, limits (pending on Feature.Bit 28) and MS_Ext does not generate
any messages in PAM_CPU / PAM_CD / PAM_IM / PAM_SM blocks. · In the operator station, the signal status and the limit values are displayed in monitoring view. · The maintenance state of PAM_XX block is only updated by events from PDM Maintenance
State and DIAG_GB. You can disable the message function with regard to input from PAM_IF block (MS_Ext, PVx_ST, and Limit vlaues) by setting MsgLock = 0. Remaining value The difference between the actual value and the next limit value. Reset You can use the reset function by pressing the "Reset" button in faceplate. As a result, a pulse is generated and is available at the block output P_PVx_Rst for one block cycle. This pulse is used as the reset signal in a connected block. Source of Analog Values You can select via the parameter PVx_PU_LK, whether the process values from package unit (PVx_PU_LK = 0) or via the linked parameter (PVx_PU_LK = 1). External Maintenance Status You can connect an external Maintenance Status to this block using MS_Ext parameter. This external Maintenance Status is then merged to the Maintenance Status of the PAM_xxx block. The following values of MS_Ext are allowed, which generates a message in the higher order blocks:
Value of MS_Ext 5 6 7
Meaning maintenance required maintenance demanded maintenance alarm
Application
The parameters PVx_Out, P_PVx_Rst, PVx_AH_Act, PVx_DH_Act, PVx_RH_Act, PVx_Diff, PVx_OutUnit etc. can be used either for the further processing or for reporting in a user-specific application.
For example:
· PVx_Out, PVx_Diff, PVx_OutUnit can be used for reporting. · P_PVx_Rst can be used for resetting a counter value. · PVx_AH_Act, PVx_DH_Act, PVx_RH_Act can be used for the monitoring of various Limits. Configuration variants
506
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @PAM 7.4 PAM_IF: Interface block to PAM Diagnostic Blocks
There are two ways to instantiate the PAM_IF block: 1. You can first configure the usage of analog values in "Advanced Diagnosis Settings" dialog.
The PAM_IF block is then automatically instantiated during Create/Update Diagnostic screens generation. 2. You can manually instantiate this block in CFC. For this, first you need to parametrize the corresponding PLT-ID at the input pin of the block. After Create/Update diagnostic screens are generated, the PAM_xx and PAM_IF block are automatically connected.
Calling OBs
The PAM_IF block is configured during "Create/Update Diagnostic Pictures".
· In the CFC editor, the block is installed automatically by driver generatoronly if it is configured in advanced diagnostic settings, in a cyclic interrupt OB35 in user charts. The block is also installed automatically in the startup OB (OB 100).
· The PLT-ID of the linked PDM object of the specific PAM object to be monitored in the parameter PLT_ID is automatically entered.
· The interconnections between PAM_CPU / PAM_CD / PAM_IM / PAM_SM, and PAM_IF blocks are created.
· Block can also be installed manually by user. If PLT-ID is configured, the connections are automatically created by the driver generator.
Startup characteristics Based on the number of cycles set at RunUpCyc, the operation is suppressed after startup.
Status word allocation The signal status of PAM_IF block for field devices represents the following values:
PVx.ST (input)
16#00.. 1F, 16#24 .. 27,
PVx.ST (mapped out- Signal status icon put) 16#00
Meaning
Bad, device related (value not valid)
16#28 .. 2B
16#28
Bad, process rela- ted
16#23, 16#3C .. 3F, 16#44 .. 4F 16#60 .. 67, 16#70 .. 77
16#60
Manipulated value (for example, sub- stitute value, simu- lation, last valid val- ue)
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
507
Family: @PAM 7.4 PAM_IF: Interface block to PAM Diagnostic Blocks
PVx.ST (input)
16#20 .. 22, 16#2C .. 3B, 16#40 .. 43, 16#50 .. 5F, 16#68 .. 6F, 16#7C .. 7F, 16#9C .. 9F, 16#AC .. FF 16#78 .. 7B,
PVx.ST (mapped out- Signal status icon put) 16#68
16#78
16#80... 9B, 16#A0 .. A3 16#A4 .. AB
16#80 16#A4
Meaning Uncertain, device related
Uncertain, process related
Good Maintenance re- quired
Feature bit allocation Update acknowledgment and error status of the message call Number of the Feature bit: 22 You can use the Feature bit to determine if the acknowledgment and error status of the message call at the block output should be updated. The default setting is 0. · Bit = 0: The MSG_ERRx, MSG_STATx, and MSG_ACKx block outputs are set to the default settings and are not updated. The block executes faster in this setting. · Bit = 1: The MSG_ERR, MSG_STATx,and MSG_ACKx block outputs are updated based on the feedback of the lower level message blocks. The lower level message blocks are called every other cycle as long as an acknowledgment is expected or error information is pending.
Note The output pins MSG_ERRx, MSG_STATx and MSG_ACKx are not available in PAM_IF block. These pins are available at blocks PAM_CPU/PAM_CD etc.
Disabling operating points Number of the Feature bit: 28 You can use this Feature bit to determine if the operating point function of a limit for disabling the message (MsgLock = 1) should also be disabled.
508
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Family: @PAM 7.4 PAM_IF: Interface block to PAM Diagnostic Blocks
The default setting is 0. · Bit = 0: Operating point is not suppressed. · Bit = 1: Operating point is suppressed.
Note The above mentioned feature bits are available in the PAM_IF block and the various functionaliies related to PAM are activated at the respective blocks (PAM_CPU, PAM_CD, PAM_IM etc).
Error handling The ERR_NUM I/O can be used to obtain the following errors in output:
Error number -1 0 4 30
Meaning Predefined value when inserting the block; block is not processed. There is no error. Value selection for SM from Paclage Unit is not possible. The entered PVx Value is not a REAL number.
Modes
Not available
Time response Not available
See also
General Information About Block Description (Page 15)
7.4.2
I/Os of PAM_IF
The factory setting of the block display in the CFC is identified in the "I/O" column:
I/O name bold = I/O visible, I/O name normal = I/O not visible.
You can find explanations and the meaning of abbreviations in the section: "General Information About Block Description (Page 15)".
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
509
Family: @PAM 7.4 PAM_IF: Interface block to PAM Diagnostic Blocks
Input parameters
I/O Parameter PLT_ID MS_Ext PVx_Hyst PVx PVx_Name PVx_Unit PVx_OpScale PVx_AH
PVx_DH
PVx_RH
PVx_PU_LK
MsgLock RunUpCyc FEATURE
Meaning
Type
Asset ID for EDD
Ext Maintenance status
Hysteresis for PV x (x: 0..2) messages
Process value x (x: 0..2)
DWORD DWORD REAL
STRUCT
Text of Process value x (x: 0..2)
Unit of Process value x (x: 0..2)
Range of process value x (x: 0..2)
STRING[16] INT STRUCT
Limit maintenance alarm process value x (x: 0..2)
Limit maintenance de- mand process value x (x: 0..2)
Limit maintenance re- quest process value x (x: 0..2)
Process value x selection (x: 0..2) 0= via Pack- age unit / 1= via Link
Inhibit process message
REAL REAL REAL BOOL STRUCT
Lag: Number of Run Up Cycles
Feature parameter
INT STRUCT
Default
16#00000000 16#00000000 99.99 0 16#80 '' 1 0 100 99.99
99.99
99.99
1
0 16#80 1 0
Output parameters
Parameter ErrorNum P_PVx_Rst
PVx_AH_Act
PVx_DH_Act
Meaning
Error Number
1=Reset process value x (x: 0..2) (Pulse output)
Type INT STRUCT
1=Limit maintenance alarm process value x (x: 0..2)
1=Limit maintenance demand process value x (x: 0..2)
BOOL BOOL
default value -1 0 16#80 1
1
510
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Parameter PVx_RH_Act
PVx_Diff
PVx_Out PVx_OutUnit
In_Out parameters
Parameter Dxchg_PAM
Family: @PAM 7.5 DB_PAM_CD: DB of CD data for reading from PAM_Station
Meaning
Type
1=Limit maintenance re- BOOL quest process value x (x: 0..2)
Difference value to the next expected Alarm x (x: 0..2)
STRUCT
Process value x (x: 0..2) STRUCT
Unit of Process value x INT (x: 0..2)
default value 1
0 16#80
0 16#80 1
Meaning
Bidirectional data ex- change Channel
Type STRUCT (UDT283)
default value 0
7.5
DB_PAM_CD: DB of CD data for reading from PAM_Station
7.5.1
Description of DB_PAM_CD
Object name (type + number) DB4 · Structure of DB_PAM_CD (Page 511)
Area of application
The data block DB_PAM_CD in the package unit contains the user data that is read by the corresponding PAM_CD block of PAM Station.
You can assign (or change) the DB number based on the number of Compact Devices (CD) available for connection.
7.5.2
Structure of DB_PAM_CD
The size of the data block DB_PAM_CD is 160 bytes and the structure is as follows:
Address 0.0 +0.0
Name STRUCT LID
Type STRING[64]
Initial value ''
Comment LID
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
511
Family: @PAM 7.6 DB_PAM_CPU: DB of CPU data for reading from PAM_Station
Address +66.0 +132.0
Name CP OT
Type STRING[64] INT
+134.0 +136.0 +138.0 +142.0 +146.0 +150.0 +152.0 +154.0 +156.0 +157.0 +158.0 +159.0 =160.0
GP DD PV0_VALUE PV1_VALUE PV2_VALUE PV0_UNIT PV1_UNIT PV2_UNIT PV0_ST PV1_ST PV2_ST STAT END_STRUCT
WORD WORD REAL REAL REAL INT INT INT BYTE BYTE BYTE BYTE
Initial value '' 4
W#16#0 W#16#0 0.000000e+000 0.000000e+000 0.000000e+000 0 0 0 B#16#0 B#16#0 B#16#0 B#16#0
Comment Connection point Object type (4=Compact de- vice) Global part Detail diagnostics
PV0 Value PV1 Value PV2 Value PV0 Unit PV1 Unit PV2 Unit PV0 Status PV1 Status PV2 Status Status information
7.6
DB_PAM_CPU: DB of CPU data for reading from PAM_Station
7.6.1
Description of DB_PAM_CPU
Object name (type + number) DB1 · Structure of DB_PAM_CPU (Page 513)
Area of application
The data block DB_PAM_CPU in the package unit contains the user data that is read by the corresponding PAM_CPU block of PAM station.
You can assign (or change) the DB number based on the number of CPUs available for connection.
512
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
7.6.2
Family: @PAM 7.7 DB_PAM_IM: DB of IM data for reading from PAM_Station
Structure of DB_PAM_CPU
The size of the data block DB_PAM_CPU is 160 bytes and the structure is as follows:
Address 0.0 +0.0 +66.0 +132.0
+134.0 +136.0 +138.0 +142.0 +146.0 +150.0 +152.0 +154.0 +156.0 +157.0 +158.0 +159.0 =160.0
Name STRUCT LID CP OT
GP DD PV0_VALUE PV1_VALUE PV2_VALUE PV0_UNIT PV1_UNIT PV2_UNIT PV0_ST PV1_ST PV2_ST RESERVE_00 END_STRUCT
Type
STRING[64] STRING[64] INT
WORD WORD REAL REAL REAL INT INT INT BYTE BYTE BYTE BYTE
Initial value
Comment
'' '' 1
DW#16#0 DW#16#0 0.000000e+000 0.000000e+000 0.000000e+000 0 0 0 B#16#0 B#16#0 B#16#0 B#16#0
LID Connection point Object type (1=CPU) Global part Detail diagnosis
PV0 Value PV1 Value PV2 Value PV0 Unit PV1 Unit PV2 Unit PV0 Status PV1 Status PV2 Status Reserve
7.7
DB_PAM_IM: DB of IM data for reading from PAM_Station
7.7.1
Description of DB_PAM_IM
Object name (type + number) DB2 · Structure of DB_PAM_IM
Area of application
The data block DB_PAM_IM in the package unit contains the user data that is read by the corresponding PAM_IM block of PAM Station.
You can assign (or change) the DB number based on the number of Interface Modules (IM) available for connection.
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
513
Family: @PAM 7.7 DB_PAM_IM: DB of IM data for reading from PAM_Station
7.7.2
Structure of DB_PAM_IM
The size of the data block DB_PAM_IM is 160 bytes and the structure is as follows:
Address 0.0 +0.0 +66.0 +132.0 +134.0 +136.0 +138.0
+142.0
+146.0 +150.0 152.0 156.0 +158.0 +159.0 =160.0
Name STRUCT LID CP OT GP DD SM_NOK1
SM_NOK2
RESERVE_00 RESERVE_01 PV0_VALUE PV0_UNIT PV0_ST STAT END_STRUCT
Type
STRING[64] STRING[64] INT WORD WORD DWORD
DWORD
DWORD WORD REAL INT BYTE BYTE
Initial value
Comment
'' '' 2 W#16#0 W#16#0 DW#16#0
DW#16#0
DW#16#0 W#16#0 0.000000e+000 0 B#16#0 B#16#0
LID Connection point Object type (2=IM) Global part Detail diagnostics Signal modul 0-31 error Signal modul 32-63 error Reserve Reserve
PV0 Value
PV0 Unit
PV0 Status Status information
514
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Internal block
8
8.1
ChkREAL: Internal Block
Object name (type + number)
FC260
This block is a system block and is only used internally. There is therefore no help available for it.
8.2
LED_STAT: Processing of LED Status
Object name (type + number) FC267 This block is a system block and is used exclusively internally. A help is therefore not available.
8.3
QC_CHNG: Internal block
Object name (type + number)
FB 135
This block is a system block and is only used internally. There is therefore no help available for it.
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
515
Internal block 8.3 QC_CHNG: Internal block
516
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Appendix
9
9.1
MODE settings for FF devices
MODE_xx input parameters are available for up to 32 values of a FF field device.
Block
Analog input (FbAnIn) Analog output (FbAnOu) Discrete input (FbDiIn) Discrete output (FbDiOu)
I/O (parameters) (cyclic data) permitted combinations and sequence
OUT
SP
OUT_D
SP_D
Input (I)/Output (O) (PLS view)
I O I O
MODE 16#xxyy O=xx, I=yy
16#0001 16#0100 16#0002 16#0400
9.2
MODE settings for SM modules
Measuring range coding of the analog input modules
Depending on the measuring-range coding of the analog input modules, the parameter MODE_xx (measuring-range coding) corresponding to the channel must be specified in accordance with the table. When thermocouples are used there are various options for combining the measuring type (coding A) with the measuring range (coding B). In this case, the MODE_xx parameter must be calculated according to the following formula and the result written to the MODE input as an INTEGER value: Measuring range coding = 256 coding A + coding B
Please note: The table shows codes A and B in binary format, and as the result the measuring range coding as a hexadecimal number.
Measuring type
Deactivated Voltage
Coding Measuring range (A)
2#0001
± 25 mV ± 50 mV ± 80 mV ± 250 mV ± 500 mV ± 1 V ± 2.5 V ± 5 V 1 to 5 V
Code (B) MODE (256A+B)
16#0000 2#1010 16#010A 2#1011 16#010B 2#0001 16#0101 2#0010 16#0102 2#0011 16#0103 2#0100 16#0104 2#0101 16#0105 2#0110 16#0106 2#0111 16#0107
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
517
Appendix 9.2 MODE settings for SM modules
Measuring type 4-wire measuring transducer HART interface 2-wire measuring transducer Resistor 4-wire connection
Resistor 3-wire connection
Resistor 2-wire connection
Thermocouple + linear, 4-wire connection
Coding (A) 2#0010 2#0111 2#0011 2#0100
2#0101
2#0110
2#1000
Measuring range
0 to 10 V ± 10 V ± 100 mV ±3.2 mA ± 5 mA ± 10 mA 0 to 20 mA 4 to 20 mA ± 20 mA 4 to 20 mA (variant 0) OMODE settings for SM modules (Page 527) 0 to 20 mA 4 to 20 mA ± 20 mA 0 to 10 mA 48 150 300 600 1000 3000 6000 PTC 48 150 300 600 1000 3000 6000 PTC 48 150 300 600 1000 3000 6000 PTC Pt 100 climate range
Code (B)
2#1000 2#1001 2#1100 2#0000 2#0101 2#0001 2#0010 2#0011 2#0100 2#1100
MODE (256A+B)
16#0108 16#0109 16#010C 16#0200 16#0205 16#0201 16#0202 16#0203 16#0204 16#070C
2#0010 2#0011 2#0100 2#0110 2#0000 2#0010 2#0100 2#0110 2#0111 2#0111 2#1000 2#1111 2#0000 2#0010 2#0100 2#0110 2#0111 2#0111 2#1000 2#1111 2#0000 2#0010 2#0100 2#0110 2#0111 2#0111 2#1000 2#1111 2#0000
16#0302 16#0303 16#0304 16#0306 16#0400 16#0402 16#0404 16#0406 16#040E 16#0407 16#0408 16#040F 16#0500 16#0502 16#0504 16#0506 16#050E 16#0507 16#0508 16#050F 16#0600 16#0602 16#0604 16#0606 16#060E 16#0607 16#0608 16#060F 16#0800
Pt 200 climate range
2#0111 16#0807
518
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Measuring type
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Appendix 9.2 MODE settings for SM modules
Coding (A)
Measuring range
Code (B) MODE (256A+B)
Pt 500 climate range
2#1000 16#0808
Pt 1000 climate range
2#1001 16#0809
Ni 100 climate range
2#0001 16#0801
Ni 1000/LG-Ni 1000 climatic range
2#1010 16#080A
Pt 100 standard range
2#0010 16#0802
Pt 200 standard range
2#0011 16#0803
Pt 500 standard range
2#0100 16#0804
Pt 1000 standard range
2#0101 16#0805
Ni 100 standard range
2#1011 16#080B
Ni 1000/LG-Ni 1000 standard range
2#0110 16#0806
Ni 120 standard range
2#1100 16#080C
Ni 120 climate range
2#1101 16#080D
Cu 10 climate range
2#1110 16#080E
Cu 10 standard range
2#1111 16#080F
Ni 200 standard range
2#1000 16#0810 0
Ni 200 climate range
2#1000 16#0811 1
Ni 500 standard range
2#1001 16#0812 0
Ni 500 climate range
2#1001 16#0813 1
Pt 10 GOST climatic
2#1010 16#0814 0
Pt 10 GOST standard (TC = 3910) 2#1010 16#0815 1
Pt 50 GOST climatic
2#1011 16#0816 0
Pt 50 GOST standard (TC = 3910) 2#1011 16#0817 1
Pt 100 GOST climatic
2#1100 16#0818 0
Pt 100 GOST standard (TC = 3910)
2#1100 16#0819 1
Pt 500 GOST climatic
2#1101 16#081A 0
Pt 500 GOST standard (TC = 3910)
2#1101 16#081B 1
Cu 10 GOST climatic
2#1110 16#081C 0
Cu 10 GOST standard (TC = 426) 2#1110 16#081D 1
Cu 50 GOST climatic
2#1111 16#081E 0
519
Appendix 9.2 MODE settings for SM modules
Measuring type
Coding (A)
Measuring range
Cu 50 GOST standard (TC = 426)
Cu 100 GOST climatic
Cu 100 GOST standard (TC = 426) Ni 100 GOST climatic
Ni 100 GOST standard
Pt 10 GOST standard (TC = 3850)
Pt 50 GOST standard (TC = 3850)
Pt 100 GOST standard (TC = 3850) Pt 500 GOST standard (TC = 3850) Cu 10 GOST standard (TC = 428)
Cu 50 GOST standard (TC = 428)
Cu 100 GOST standard (TC = 428)
Code (B)
2#1111 1
2#1000 00
2#1000 01
2#1000 10
2#1000 11
2#1010 101
2#1010 111
2#1011 001
2#1011 011
2#1001 1101
2#1001 1111
2#1010 0001
MODE (256A+B) 16#081F 16#0820 16#0821 16#0822 16#0823 16#0855 16#0857 16#0859 16#085B 16#089D 16#089F 16#08A1
Thermocouple + linear, 3-wire connection
2#1001 Pt 100 climate range
2#0000 16#0900
Pt 200 climate range
Pt 500 climate range
Pt 1000 climate range
Ni 100 climate range
Ni 1000/LG-Ni 1000 climatic range
Pt 100 standard range
Pt 200 standard range
Pt 500 standard range
Pt 1000 standard range
Ni 100 standard range
Ni 1000/LG-Ni 1000 standard range
Ni 120 standard range (variant 0)
KTY83/110 (variant 1) OMODE settings for SM modules (Page 527)
2#0111 2#1000 2#1001 2#0001 2#1010
2#0010 2#0011 2#0100 2#0101 2#1011 2#0110
2#1100
16#0907 16#0908 16#0909 16#0901 16#090A
16#0902 16#0903 16#0904 16#0905 16#090B 16#0906
16#090C
520
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Measuring type
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Appendix 9.2 MODE settings for SM modules
Coding (A)
Measuring range
Code (B) MODE (256A+B)
Ni 120 climate range (variant 0) 2#1101 16#090D
KTY84/130 (variant 1) OMODE settings for SM modules (Page 527)
Cu10 climate range
2#1110 16#090E
Cu10 standard range
2#1111 16#090F
Ni 200 standard range
2#1000 16#0910 0
Ni 200 climate range
2#1000 16#0911 1
Ni 500 standard range
2#1001 16#0912 0
Ni 500 climate range
2#1001 16#0913 1
Pt 10 GOST climatic
2#1010 16#0914 0
Pt 10 GOST standard (TC = 3910) 2#1010 16#0915 1
Pt 50 GOST climatic
2#1011 16#0916 0
Pt 50 GOST standard (TC = 3910) 2#1011 16#0917 1
Pt 100 GOST climatic
2#1100 16#0918 0
Pt 100 GOST standard (TC = 3910)
2#1100 16#0919 1
Pt 500 GOST climatic
2#1101 16#091A 0
Pt 500 GOST standard (TC = 3910)
2#1101 16#091B 1
Cu 10 GOST climatic
2#1110 16#091C 0
Cu 10 GOST standard (TC = 426) 2#1110 16#091D 1
Cu 50 GOST climatic
2#1111 16#091E 0
Cu 50 GOST standard (TC = 426) 2#1111 16#091F 1
Cu 100 GOST climatic
2#1000 16#0920 00
Cu 100 GOST standard (TC = 426)
2#1000 16#0921 01
Ni 100 GOST climatic
2#1000 16#0922 10
Ni 100 GOST standard
2#1000 16#0923 11
521
Appendix 9.2 MODE settings for SM modules
Measuring type
Coding (A)
Thermocouple + linear, 2-wire connection
2#1111
Thermocouple, linear, reference 2#1010 temperature 0 ºC / no reference point
Measuring range
Pt 10 GOST standard (TC = 3850)
Pt 50 GOST standard (TC = 3850)
Pt 100 GOST standard (TC = 3850) Pt 500 GOST standard (TC = 3850) Cu 10 GOST standard (TC = 428)
Cu 50 GOST standard (TC = 428)
Cu 100 GOST standard (TC = 428) Pt 100 climate range
Code (B)
2#1010 101
2#1010 111
2#1011 001
2#1011 011
2#1001 1101
2#1001 1111
2#1010 0001
2#0000
MODE (256A+B) 16#0955 16#0957 16#0959 16#095B 16#099D 16#099F 16#09A1 16#0F00
Pt 200 climate range Pt 500 climate range Pt 1000 climate range Ni 100 climate range Ni 1000/LG-Ni 1000 climatic range Pt 100 standard range Pt 200 standard range Pt 500 standard range Pt 1000 standard range Ni 100 standard range Ni 1000/LG-Ni 1000 standard range Ni 120 standard range Ni 120 climate range Cu10 climate range Cu10 standard range Ni 200 standard range
Ni 200 climate range
Ni 500 standard range
Ni 500 climate range
Type B [PtRh-PtRh]
2#0111 2#1000 2#1001 2#0001 2#1010
16#0F07 16#0F08 16#0F09 16#0F01 16#0F0A
2#0010 2#0011 2#0100 2#0101 2#1011 2#0110
16#0F02 16#0F03 16#0F04 16#0F05 16#0F0B 16#0F06
2#1100
2#1101
2#1110
2#1111
2#1000 0
2#1000 1
2#1001 0
2#1001 1
2#0000
16#0F0C 16#0F0D 16#0F0E 16#0F0F 16#0F10
16#0F11
16#0F12
16#0F13
16#0A00
Type N [NiCrSi-NiSi] Type E [NiCr-CuNi]
2#0001 16#0A01 2#0010 16#0A02
522
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Appendix 9.2 MODE settings for SM modules
Measuring type
Coding (A)
Thermocouple, linear, reference 2#1011 temperature 50 ºC
Thermocouple, fixed ref. temp 2#1100
Thermocouple, linear, internal compensation / internal refer- ence point
2#1101
Measuring range
Type R [PtRh-Pt] Type S [PtRh-Pt] Type J [Fe-CuNi IEC] Type L [Fe-CuNi DIN] Type T [Cu-CuNi IEC] Type K [NiCr-Ni] Type U [Cu-CuNi DIN] Type C Type TXK/XK(L) Type B [PtRh-PtRh]
Type N [NiCrSi-NiSi] Type E [NiCr-CuNi] Type R [PtRh-Pt] Type S [PtRh-Pt] Type J [Fe-CuNi IEC] Type L [Fe-CuNi DIN] Type T [Cu-CuNi IEC] Type K [NiCr-Ni] Type U [Cu-CuNi DIN] Type C Type TXK/XK(L) Type B [PtRh-PtRh] Type N [NiCrSi-NiSi] Type E [NiCr-CuNi] Type R [PtRh-Pt] Type S [PtRh-Pt] Type J [Fe-CuNi IEC] Type L [Fe-CuNi DIN] Type T [Cu-CuNi IEC] Type K [NiCr-Ni] Type U [Cu-CuNi DIN] Type C Type TXK/XK(L) Type B [PtRh-PtRh]
Type N [NiCrSi-NiSi] Type E [NiCr-CuNi] Type R [PtRh-Pt] Type S [PtRh-Pt] Type J [Fe-CuNi IEC] Type L [Fe-CuNi DIN]
Code (B) MODE (256A+B)
2#0011 16#0A03 2#0100 16#0A04 2#0101 16#0A05 2#0110 16#0A06 2#0111 16#0A07 2#1000 16#0A08 2#1001 16#0A09 2#1010 16#0A0A 2#1011 16#0A0B 2#0000 16#0B00
2#0001 2#0010 2#0011 2#0100 2#0101 2#0110 2#0111 2#1000 2#1001 2#1010 2#1011 2#0000 2#0001 2#0010 2#0011 2#0100 2#0101 2#0110 2#0111 2#1000 2#1001 2#1010 2#1011 2#0000
16#0B01 16#0B02 16#0B03 16#0B04 16#0B05 16#0B06 16#0B07 16#0B08 16#0B09 16#0B0A 16#0B0B 16#0C00 16#0C01 16#0C02 16#0C03 16#0C04 16#0C05 16#0C06 16#0C07 16#0C08 16#0C09 16#0C0A 16#0C0B 16#0D00
2#0001 2#0010 2#0011 2#0100 2#0101 2#0110
16#0D01 16#0D02 16#0D03 16#0D04 16#0D05 16#0D06
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
523
Appendix 9.2 MODE settings for SM modules
Measuring type
Coding (A)
Thermocouple, linear, external compensation / reference point RTD(0)
2#1110
Thermocouple, dynamic ref. temp
2#0111
Measuring range
Type T [Cu-CuNi IEC] Type K [NiCr-Ni] Type U [Cu-CuNi DIN] Type C Type TXK/XK(L) Type B [PtRh-PtRh]
Code (B)
2#0111 2#1000 2#1001 2#1010 2#1011 2#0000
MODE (256A+B)
16#0D07 16#0D08 16#0D09 16#0D0A 16#0D0B 16#0E00
Type N [NiCrSi-NiSi]
2#0001
Type E [NiCr-CuNi]
2#0010
Type R [PtRh-Pt]
2#0011
Type S [PtRh-Pt]
2#0100
Type J [Fe-CuNi IEC]
2#0101
Type L [Fe-CuNi DIN]
2#0110
Type T [Cu-CuNi IEC]
2#0111
Type K [NiCr-Ni]
2#1000
Type U [Cu-CuNi DIN]
2#1001
Type C
2#1010
Type TXK/XK(L)
2#1011
Type B [PtRh-PtRh] (variant
2#0000
1) OMODE settings for SM mod-
ules (Page 527)
Type N [NiCrSi-NiSi] (variant
2#0001
1) OMODE settings for SM mod-
ules (Page 527)
Type E [NiCr-CuNi] (variant
2#0010
1) OMODE settings for SM mod-
ules (Page 527)
Type R [PtRh-Pt] (variant
2#0011
1) OMODE settings for SM mod-
ules (Page 527)
Type S [PtRh-Pt] (variant
2#0100
1) OMODE settings for SM mod-
ules (Page 527)
Type J [Fe-CuNi IEC] (variant
2#0101
1) OMODE settings for SM mod-
ules (Page 527)
Type L [Fe-CuNi DIN] (variant 2#0110 1) OMODE settings for SM mod- ules (Page 527)
Type T [Cu-CuNi IEC] (variant 2#0111 1) OMODE settings for SM mod- ules (Page 527)
Type K [NiCr-Ni] (variant
2#1000
1) OMODE settings for SM mod-
ules (Page 527)
16#0E01 16#0E02 16#0E03 16#0E04 16#0E05 16#0E06 16#0E07 16#0E08 16#0E09 16#0E0A 16#0E0B 16#0700
16#0701
16#0702
16#0703
16#0704
16#0705
16#0706
16#0707
16#0708
524
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Appendix 9.2 MODE settings for SM modules
Effect of the temperature coefficients on the measuring range · Setting TC = 3850 at GOST Standard Pt10, Pt50, Pt100, Pt500 sets Bit 7 in the measuring range byte (0x40) · Setting TC = 428 at GOST Standard Cu10, Cu50, Cu100 sets Bit 8 in the measuring range byte (0x80)
Measuring range coding of the analog output modules
Depending on the measuring-range coding of the analog output modules, the parameter MODE_xx (measuring-range coding) corresponding to the channel must be specified in accordance with the table.
Measuring type Voltage
Current
HART interface
Measuring range ± 5 V 1 to 5 V 0 to 10 V ± 10 V 0 to 20 mA 4 to 20 mA ± 20 mA 0 to 10 mA 4 to 20 mA
MODE 16#0106 16#0107 16#0108 16#0109 16#0202 16#0203 16#0204 16#0206 16#070C
Mode: Celsius and Fahrenheit
Variant 0
1
x
0, 1 (depending on the other var- iant IDs)
8, 9 (depending on the other var- iant IDs)
y 0,1,2,4
0,1,2,4
Measuring range Celsius
Fahrenheit
Mode: 16#090C and variant
Variant
x
0
0
1
1
y 0,1,2,4 0,1,2,4
Measuring range Ni 120 standard range KTY84/110
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
525
Appendix 9.2 MODE settings for SM modules
Mode: 16#090D and variant
Variant
x
0
0
1
1
y 0,1,2,4 0,1,2,4
Measuring range Ni 120 climate range KTY84/130
Mode: 16#07 (Coding A) and variant
Variant 0 1
x
y
0
0,1,2,4
1
0,1,2,4
Measuring range HART interface Thermocouple, dynamic reference temperature
MODE: 16#08, 16#0A, 16#0B, 16#0D, 16#0E (coding A) and variant
Table 9-1
Variant 0 1
PCS 7 as of V8.1: MODE parameter variant
x
y
0
0,1,2,4
3
0,1,2,4
Measuring range S7-300 module S7-300, ET 200M Ex I/O module
Table 9-2 Variant 0
1
PCS 7 V7.x: MODE parameter variant
Mode 16#08, 16#0A, 16#0B, 16#0D, 16#0E 16#18, 16#1A, 16#1B, 16#1D, 16#1E
Measuring range S7-300 module
S7-300, ET 200M Ex I/O module
Measuring-Range Coding of the Digital Input and Output Modules
With digital input modules and digital output modules, there is no measuring type and no measuring range: MODE = 16#FFFF (with DI) MODE = 16#FFFE (with DO)
MODE: 1oo1 / 1oo2 evaluation for F-modules
Variant 0 1
x
y
0
0,1,2,4
4
0,1,2,4
Measuring range 1oo1 (1v1) evaluation 1oo2 (2v2) evaluation
526
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Appendix 9.3 OMODE settings for SM modules
Measuring range coding of the controller module There is no measuring type and no measuring range for controller modules: MODE = 16#FFFD
Measuring range coding of the communication module There is no measuring type and no measuring range for communication modules: MODE = 16#0001
Measuring range encoding of the ET 200SP Analog Input Energy Meter module There is no measuring type and no measuring range for Analog Input Energy Meter modules: MODE = 16#200C
9.3
OMODE settings for SM modules
OMODE structure
The table below shows the structure and meaning of the outputs OMODE_xx of data type DWORD:
Byte 3: Byte 2: Byte 1, 0 (low word):
16#80: Value status "valid value" 16#85 Value status "valid value" 16#00: Value status "invalid value" 16#40: Value status "invalid value" 16#01: Restart (OB 100) has been carried out 16#02: Measuring-range overshoot 16#04: Measuring range low limit exceeded 16#xy: Variant identifier at multiple MODE_ assignment (see below) MODE (see above)
(IO redundancy warning) (Channel error) (Higher-level error)
(Channel-error diagnostics) (Channel-error diagnostics)
Example:
16#80010203 = value status "valid value", restart has been carried out, current 4 mA to 20mA
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
527
Appendix 9.4 MODE settings for field devices
9.4
MODE settings for field devices
MODE_xx input parameters are available for a maximum of 32 slots of a PA/FF field device. Their initial value is zero (no read/write access). You must set the combination selected from the options of the PROFIBUS PA 3.0 profile at the MODE_xx input of each slot channel xx:
Block
Analog input (PA_AI/ FbAnIn) Totalizer (PA_TOT/ FbAnTot) Totalizer (PA_TOT/ FbAnTot) Totalizer (PA_TOT/ FbAnTot)
Analog output (PA_AO/FbAnOu) Analog output (PA_AO/FbAnOu)
Analog output (PA_AO/FbAnOu) Analog output (PA_AO/FbAnOu)
Analog output (PA_AO/FbAnOu) Analog output (PA_AO/FbAnOu)
Analog output (PA_AO/FbAnOu)
Discrete input (PA_DI/ FbDiIn) Discrete output (PA_DO/FbDiOu) Discrete output (PA_DO/FbDiOu) Discrete output (PA_DO/FbDiOu)
I/O (parameters) (cyclic data) permissible combi- nation and sequence
OUT
TOTAL
TOTAL SET_TOT TOTAL SET_TOT MODE_TOT SP
SP READBACK POS_D SP CHECK_BACK SP READBACK POS_D CHECK_BACK RCAS_IN, RCAS_OUT RCAS_IN, RCAS_OUT, CHECK_BACK SP RCAS_IN READBACK RCAS_OUT POS_D CHECK_BACK OUT_D
SP_D
SP_D READBACK_D SP_D CHECKBACK_D
Input (I)/Output (O) (PLS view)
I
I
I O I O O O
O I I O I O I I I O I O I I O O I I I I I
O
O I O I
MODE 16#xxyy, O=xx I=yy
16#0001 16#000F 16#070F 16#080F
16#0100 16#0103
16#0104 16#0105
16#0206 16#0207
16#0308
16#0002 16#0400 16#0409 16#040A
Configuration possible with field device
PA + FF PA PA PA
PA + FF PA
PA PA
PA PA
PA
PA + FF PA + FF PA PA
528
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Block
Discrete output (PA_DO/FbDiOu)
Discrete output (PA_DO/FbDiOu) Discrete output (PA_DO/FbDiOu)
Discrete output (PA_DO/FbDiOu)
Appendix 9.5 OMODE settings for field devices
I/O (parameters) (cyclic data)
permissible combi- nation and sequence
SP_D READBACK_D CHECK_BACK_D
RCAS_IN_D RCAS_OUT_D
RCAS_IN_D RCAS_OUT_D CHECK_BACK_D
SP_D RCAS_IN_D READBACK_D RCAS_OUT_D CHECK_BACK_D
Input (I)/Output (O) (PLS view)
O I I
O I
O I I
O O I I I
MODE 16#xxyy, O=xx I=yy
16#040B
16#050C 16#050D
16#060E
Configuration possible with field device
PA
PA PA
PA
PA/FF device variant identifier
Variant
x
y
Field device
0
0
0
PA device
1
1
0
FF device
9.5
OMODE settings for field devices
OMODE Structure
The table below shows the structure and meaning of the outputs OMODE_xx of data type DWORD:
Byte 3: Byte 2: Byte 1, 0 (low word):
16#80: Value status "valid value"
16#00: Value status "invalid value"
16#40: Value status "invalid value"
16#xy: Variant identifier at multiple MODE_ assignment (see MODE settings for field devices (Page 528))
MODE (see above)
(Channel error) (Higher-level error)
Example:
16#80000001 corresponds to the value status "valid value", analog input, whereby parameter Out supplies the cyclic data.
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
529
Appendix 9.7 Addressing
9.6
Error Information of Output Parameter MSG_STAT
The messages can be disabled by setting input EN_MSG = FALSE (output MSG_STAT(_x) remains unchanged).
Block ALARM8_P(_x) is called in the acyclic OBs and in OB1 if message suppression is not enabled. Error information of ALARM_8P(_x) - messages cannot be output - is indicated at output parameter MSG_STAT(_x).
Details on the error information of output parameter MSG_STAT and on the acknowledgment word MSG_ACK(_x) of ALARM_8P are found in the Online Help of SF B35 (ALARM_8P).
9.7
Rules
Addressing
If you do not use the CFC function "Generate module drivers", you must set the logical basic address of the module created with HW Config at the LADDR input parameter. If input SUBN_TYP = FALSE, the RACK of the module is connected to an integrated DP interface (distributed I/O device interface) of the CPU module by means of a line. Otherwise, you must set SUBN_TYP = TRUE.
The following points are generally to be observed for all SM, PA and FF blocks:
· The basic address of modules equipped only with inputs, i.e., modules which only write data to the input range of the CPU process image, can be fetched directly from HW Config; for example: The module SM 331 AI 8x12Bit 6ES7 331-7KF01-0AB0:
Address input range (HW Config)
512
Address output range (HW Config)
-
LADDR (decimal/hex)
512 / 16#0200
· The MSB (most significant bit) must be set in the basic address fetched from HW Config for modules equipped only with outputs, which means modules which only read data from the output range of the CPU process image; for example, module SM 332 AO 4x12Bit 6ES7 332-5HD01-0AB0:
Address input range (HW Config)
-
Address output range (HW Config)
512
LADDR (decimal/hex)
-32256 / 16#8200
· The basic address of the input range must be set at input LADDR and the basic address of the output range from HW Config must be set at input LADDR1 for mixed modules, which means modules that write data to the input range and read data from the output range of the CPU process image; for example, module SM 323 DI/O 8x24V/05A 6ES7 323-1BH81-0AA0:
Address input range (HW Config)
12
Address output range (HW Config)
12
LADDR (decimal/hex)
12 / 16# 000C
LADDR1 (decimal/hex)
12 / 16# 000C
530
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Appendix 9.8 Message Classes
· For FF devices which only write data to the input range of the CPU process image, the lowest input address should be fetched from HW Config.
· For FF devices which only write data to the output range of the CPU process image, the lowest output address from HW Config should be set.
· For FF devices which write the data in the input range of the CPU process image and read from the output range of the CPU process image, you must set the lowest address of the input/ output range from HW Config at the DADDR input.
Address input range (HW Config) 512
512 512 516
Address output range (HW Config)
512 516 512 512
DADDR (decimal/hex)
512 16896 (16384 + 512)/ 16#4200 512 512 16896 (16384 + 512) / 16#4200
9.8
Message Classes
Message classes
Message classes are used to group messages according to their cause. The following message classes are used in the SIMATIC process control system:
· Process messages triggered when process-specific monitoring values (for example, alarms, warnings, high/low tolerances, general process messages) are reached or exceeded.
· Process control messages which are output by the control system (system messages) or the I/O units (errors in the field), or for preventive maintenance.
· Requests for operator input which, in the case of certain operation sequences, draw the operator's attention to the necessity of an operator intervention (for example, request to acknowledge a stepping operation manually in order to enable transition) or operation logs.
Table of message classes and their meaning
Message class Meaning
AH
Alarm high (High High Alarm)
AL
Alarm low (Low Low Alarm)
WH
Warning high (High Alarm)
WL
Warning low (Low Alarm)
TH
Tolerance high (Tolerance High)
TL
Tolerance low (Tolerance Low)
F
AS process control message (error)
S
AS process control message (fault)
S*
OS process control message (fault)
M
Preventive maintenance (Maintenance)
With acknowledg- ment
Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
531
Appendix 9.9 Dependencies
Message class Meaning
PM PM OR OM *1) SA SO
Process message (Process Message) Operating message Operator request (Operator Request) Operator message (Operation Message) Status AS Status OS
With acknowledg- ment
Yes No No No No No
*1) If the block is used for operation messages, the inputs I_1, ... have to be supplied with pulses. Assignment of the static value "1" would lead to multiple messages.
See also
Message texts and associated values of MOD_CENTRAL (Page 136)
9.9
Dependencies
Dependency on the FM_CO block
The FM_CO block (PCS 7 Basic Library) coordinates the reading of data records for the FM_CNT, FMCS_PID, FMT_PID, and READ355P blocks. Therefore, when installing these blocks you must ensure that the driver generator installs FM_CO in the fastest cyclic-interrupt OB of one of the blocks named above. This OB must not run slower than 30 s or faster than 25 ms.
Notes on reading data records
In an ET 200M with n controller blocks, reading of data records is activated every n+1 cycles (ideally, when the installation sequence tallies with the interconnection).
This means that, in the worst case, a setpoint changed by means of a faceplate will only be viewed by the operator after n+1 cycles (e.g. this would amount to 17 s for OB 32 (1,000 ms) with 4 controller modules and 16 blocks).
The same applies for position feedback for the step controller. At the time of changeover (manual/auto), the manipulated variable LMN is set to an out-of-date value.
Changing the visualization time You can reduce the visualization time as follows:
· Install the controller blocks in a faster OB or
· Distribute the controller modules over several ET 200 stations.
532
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
9.10
Status displays
Appendix 9.10 Status displays
9.10.1
Maintenance status MS
Layout of the maintenance status The maintenance status MS with the DWORD data type has the following layout:
Bit Bit 0 to 7 Bit 8 to 15 Bit 16 Bit 17
Bit 18 Bit 19 to 20
Bit 21 Bit 22 Bit 23 Bit 24 to 27 Bit 28 to 29 Bit 30 Bit 31
Explanation Display of the maintenance state Display of the maintenance state of the redundant partner 1 = Redundant partner available 0 = primary partner is master, 1 = redundant partner is master SIMATIC PDM maintenance state worse than device status Coding of cycle time for the cyclic update Bit 19 = 0, Bit 20 = 0; 1 day Bit 19 = 1, Bit 20 = 0; 12 hours Bit 19 = 0, Bit 20 = 1; 1 hour Bit 19 = 1, Bit 20 = 1; 10 minutes "1" = Device is selected as "Selection for exports" in the maintenance view SIMATIC PDM has detected a state change Block takes part in the cyclical updating of SIMATIC PDM OS operation SIMATIC PDM maintenance state
OP_OFF OP_PASSIV
The MS is copied 1:1 to the output O_MS.
For more information, refer to the "Process Control System PCS 7; Maintenance Station" manual.
9.10.2
PA field device status and diagnostics information
PA-Field-Device Status
PA Status
Limits (Bit 1 + 0 irrelevant)
Quality (bit 7 + 6)
Substatus (bits 5 2)
Meaning of PA Status
10
0000
Good
10
0001
Making configuration change
Message
Coding MS
M = Message Q = Must be acknowledged
0
M
0
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
533
Appendix 9.10 Status displays
PA Status
Meaning of PA Status
Limits (Bit 1 + 0 irrelevant)
10
0010
Active warning
10
0011
Active alarm
10
0100
Unacknowledged configuration change
10
0101
Unacknowledged warning
10
0110
Unacknowledged interrupt
10
1000
Device switches to fail-safe position
10
1001
Maintenance required pending
(more diagnostic data available)
10
1010
Maintenance demanded pending
(more diagnostic data available)
10
1111
Self-test in progress
01
0000
Not specified
01
0001
Last valid value
01
0010
Substitute value
01
0011
Initial value
01
0100
Measured value formation incorrect
01
0101
Value outside defined range
01
0110
Signal source uncertain
01
0111
Configuration error
01
1000
Measured value simulated
01
1001
Sensor calibration
01
1010
Maintenance demanded
(more diagnostic data available)
01
1100
Simulation started
01
1101
Simulation completed
01
1110
Process-related, no maintenance
00
0000
Not specified
00
0001
Configuration error
00
0010
Not connected
00
0011
Device error
00
0100
Sensor error
00
0101
No connection - last valid value
00
0110
No connection - no valid value
00
0111
Out of service
00
1000
Out of service
(no diagnostic data, passivated)
00
1001
Maintenance alarm
(more diagnostic data available)
00
1010
Process-related, no maintenance
00
1111
Local operation/function check
Message
M Q
Q
Q Q Q
Q Q Q Q Q Q Q
M M M Q Q Q Q Q Q Q Q M
Q
M M
Coding MS
0 0 0 0 0 0 5
6
0 6 7 7 0 6 6 6 6 3 6 6
3 0 0 7 7 7 7 7 7 7 2 1
7
0 4
You can find additional information about status icons for the maintenance status (MS) in the "Maintenance status MS (Page 533)" section.
534
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Appendix 9.10 Status displays
Diagnostic information The structure of the PA_DIAG parameter is as follows:
Byte Bit position PROFIBUS - diagnostic significance
Message MS
0
0
Electronic hardware failure
Q
7
1
Mechanical hardware failure
2
Excess motor temperature
3
Excess temperature at electronic circuit
4
Memory error
5
Measurement failure
Q
7
Q
6
Q
6
Q
7
Q
7
6
Device not initialized (no auto-calibration)
Q
0
7
Auto-calibration error
7
1
0
Zero error (limit position)
Q
6
1
No power supply (electr. pneum.)
Q
7
2
Invalid configuration
Q
7
3
Warm start executed
M
0
4
Complete restart executed
5
Maintenance necessary
6
Invalid identifier
7
Invalid ID number
M
0
Q
5
Q
7
Q
7
2
0
Device error
Q
7
1
Maintenance requested
Q
5
2
Device is in a functional check or in simulation or under
0
3
local operator control (maintenance)
0
The process conditions do not allow the valid values to be
returned; this is set when the quality is "uncertain, process-
4 - 7
related, no maintenance" or "bad, process-related, no maintenance"
Reserved for PNO, default 0
3
0-4
5
6
Reserved for PNO use = 0: for devices of the corresponding profile = 0: for devices of the corresponding profile
7
= 0: no further information available
= 1: Further diagnostic information available in DIAGNO- SIS_EXTENSION
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
535
Appendix 9.11 Text libraries
9.11
Text libraries
9.11.1
Text library for PAM_CPU/ PAM_CD/PAM_IM/PAM_SM/PAM_IF/FB_DB_CPU/ FB_DB_CD/FB_DB_IM
The following table lists the text library message texts and their text numbers for the blocsk PAM_CPU (FB 436), PAM_CD (FB 438),PAM_IM (FB 422), PAM_SM (FB 437), PAM_IF (FB 29), FB_DB_CPU (132), FB_DB_CD (FB 27), FB_DB_IM (FB 28):
Text no. 1 2 3 4
Message text SIMATIC PDM External station External application Analog value
9.11.2
Text library for MOD_SWT
The following table lists the text library message texts and their text numbers for the block MOD_SWT (FB 149):
Text no. 1 2 3
Message text Running forwards Standstill Running backwards
9.11.3
Text library for FF_MOD32
The following table lists the text library message texts and their text numbers for the block FF_MOD32 (FB 124):
Text no. 1 2 3
Message text Multiple alarm OB83 Multiple alarm OB82 Configuration error: Name does not match address
536
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
9.11.4
Appendix 9.11 Text libraries
Text Library for MOD_PAL0, MOD_PAX0
The following table lists the text-library message texts and their numbers for the blocks MOD_PAL0 (FB99) and MOD_PAX0 (FB112):
Text no. 1 2 3 4
Message text Warm restart Cold restart PA field device diagnostics Memory error
9.11.5
Text Library for PADP_L00, PADP_L01, PADP_L02
The following table lists the text-library message texts and their numbers for the blocks PADP_L00 (FB 109), PADP_L01 (FB 110), PADP_L02 (FB 111):
Text No. 1 2 3
Message Text Module error Wrong module Module missing
9.11.6
Text Library for DREP, DREP_L
The following table lists the text-library message texts and their numbers for the blocks DREP (FB 113) and DREP_L (FB 125):
Text No. 1 2
Message Text Failure Diagnostics
9.11.7
Text library for MOD_1, MOD_2, MOD_3, MOD_64, MOD_D2, MOD_CP
The following table lists the message texts and their text numbers from the text library for the MOD_1 (FB 91) / MOD_2 (FB 92) / MOD_3 (FB 95) / MOD_64 (FB 137) / MOD_D2 (FB 94) / MOD_CP (FB 98) blocks :
Text Message Text No.
1
Parameter assignment error
2
Common mode error
3
Short-circuit to P
4
Short circuit to M
5
Wire break
6
Reference channel error
Remark
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
537
Appendix 9.11 Text libraries
Text Message Text No.
7
Measuring range violation low
8
Measuring range violation high
9
Load voltage missing
10
Chassis ground error
11
Sensor supply missing
12
Excess temperature
13
Module OK
14
Internal error
15
External error
16
External auxiliary voltage missing
17
Front connector missing
18
No configuration
19
Wrong module parameters
20
Wrong/missing user module
21
Communication error
22
Operating mode RUN/STOP
23
Timeout
24
Failure mod. int. supply voltage
25
Battery depleted
26
Total backup failure
27
CPU failure
28
EPROM error
29
RAM error
30
ADC/DAC error
31
Fuse tripped
32
Process interrupt lost
33
Removed
34
Plugged
35
Wrong module type plugged
36
Faulty module inserted
37
Module inserted (parameter error)
38
Chatter error
39
Changeover contact diagnostics
40
41
Remark RUN: going STOP: coming
538
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
9.11.8
Appendix 9.11 Text libraries
Text Library for MOD_D1
The following table lists the text-library message texts and their numbers for the block MOD_D1 (FB 93):
Text Message text no.
1
Parameter assignment error
2
Common mode error
3
Short-circuit to P
4
Short circuit to M
5
Wire break
6
Reference channel error
7
Measuring range violation low
8
Measuring range violation high
9
Load voltage missing
10
Chassis ground error
11
Sensor supply missing
12
Excess temperature
13
Module OK
14
Internal error
15
External error
16
External auxiliary voltage missing
17
Front connector missing
18
No configuration
19
Wrong parameter in module
20
Wrong/missing user module
21
Communication error
22
Operating mode RUN/STOP
23
Timeout
24
Failure mod. int. supply volt.
25
Battery depleted
26
Total backup failure
27
CPU failure
28
EPROM error
29
RAM error
30
ADC/DAC error
31
Fuse tripped
32
Process interrupt lost
33
Removed
34
Plugged
35
Wrong module type plugged
36
Faulty module inserted
37
Module inserted (parameter assignment error)
38
Chatter error
Remark RUN: going STOP: coming
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
539
Appendix 9.11 Text libraries
Text Message text no.
39
Changeover contact diagnostics
40
Sensor or load voltage loss
41
Faulty fuse
42
AI error hardware
43
AI wire break
44
AI below measuring range
45
AI above measuring range
46
AO wire break
47
AO short-circuit
48
49
50
Signal A faulty
51
Signal B faulty
52
Signal N faulty
53
Faulty value supplied to the channels
54
Sensor supply 5.2 V/8.2 V faulty
55
Sensor supply 24 V faulty
56
Namur sensor signal line error
57
Readback error
58
Power supply 1: Error
59
Power supply 2: Error
60
Actuator OFF
61
Discrepancy error
Remark
9.11.9
540
Text library for MOD_D3, MOD_D8
The following table lists the text library message texts and their numbers for the blocks MOD_D3 and MOD_D8:
Text Message text no.
1
Parameter assignment error
2
Common mode error
3
P short circuit
4
M short circuit
5
Wire break
6
Reference channel error
7
Below measuring range
8
Above measuring range
9
Load voltage missing
10
Mass error
11
Sensor supply missing
Remark
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Text Message text no.
12
Excess temperature
13
Module OK
14
Internal error
15
External error
16
External aux. voltage missing
17
Front connector missing
18
No parameter assignment
19
Wrong parameter in module
20
Wrong/missing user module
21
Communication problem
22
Operating mode RUN/STOP
23
Time monitoring addressed
24
Module failure int. supply voltage
25
Battery empty
26
Total backup battery failure
27
Process failure
28
EPROM error
29
RAM error
30
ADC/DAC error
31
Fuse blown
32
Process interrupt lost
33
Withdrawn
34
Plugged
35
Wrong module type plugged
36
Faulty module plugged
37
Module plugged (param. error)
38
Chatter error
39
Changeover contact diagnostics
40
Sensor or load voltage missing
41
Fuse defective
42
AI hardware error
43
AI wire break
44
AI below measuring range
45
AI above measuring range
46
AO wire break
47
AO short circuit
48
CiR configuration
49
CiR configuration not successful
50
Signal A faulty
51
Signal B faulty
52
Signal N faulty
53
Incorrect value transferred between channels
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Remark
Appendix 9.11 Text libraries
RUN: going STOP: coming
541
Appendix 9.11 Text libraries
Text Message text no.
54
Sensor supply 5.2 V/8.2 V faulty
55
24 V sensor supply faulty
56
Signal line error Namur sensor
57
Readback error
58
Power supply 1: Error
59
Power supply 2: Error
60
Actuator switch off
61
Undervoltage
62
Overvoltage
63
Overload
64
Standby
65
Hardware interrupt
66
Actuator alarm
67
Safety shutdown
68
Ambiguous error
69
Error 1 in actuator/sensor
70
Error 2 in actuator/sensor
71
Channel temporarily not available
72
Calibrating channel
73
Discrepancy error
74
Overcurrent at output driver
75
Faulty P output driver
76
Internal P short circuit
77
External P short circuit/cross fault
78
Internal fault in the read circuit/test circuit
79
Output short circuit to M or faulty output driver
80
Switching frequency exceeded
81
PROFIsafe communication error
Remark
9.11.10
Text library for MOD_D8_PN (FB197) / MOD_D16_PN (FB198) / MOD_D24_PN (FB199) / MOD_ENME (FB 419)
The following table lists the message texts and their numbers from the text library for the block MOD_D8_PN (FB197) / MOD_D16_PN (FB198) / MOD_D24_PN (FB199):
Text Message text no.
1
Parameter assignment error
2
Common mode error
3
Short circuit to P
4
Short circuit to M
5
Wire break
Remark
542
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Appendix 9.11 Text libraries
Text Message text no.
Remark
6
Reference channel error
7
Measuring range/low limit violated
8
Measuring range/high limit violated
9
Load voltage missing
10
Ground error
11
Sensor supply missing
12
Excess temperature
13
Module OK
14
Internal error
15
External error
16
External auxiliary voltage missing
17
Front connector missing
18
Missing parameters
19
Wrong parameters in module
20
Wrong/missing user module
21
Communication error
22
Operating mode RUN/STOP
RUN: going, STOP: coming
23
Time monitoring addressed
24
Failure mod. int. supply volt.
25
Battery depleted
26
Total backup battery failure
27
Processor failure
28
EPROM error
29
RAM error
30
ADC/DAC error
31
Fuse blown
32
Process interrupt lost
33
Withdrawn
34
Plugged
35
Wrong module type plugged
36
Faulty module plugged
37
Module plugged (parameter assignment error)
38
Chatter error
39
Changeover contact diagnostics
40
Front connector missing or sensor/load voltage missing
41
Fuse defective
42
AI hardware error
43
AI wire break
44
AI below measuring range
45
AI above measuring range
46
AO wire break
47
AO short-circuit
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
543
Appendix 9.11 Text libraries
Text Message text no.
Remark
48
49
50
Signal A faulty
51
Signal B faulty
52
Signal N faulty
53
Incorrect value transferred between channels
54
Sensor supply 5.2 V/8.2 V faulty
55
Sensor supply 24 V faulty
56
Namur sensor signal line error
57
Readback error
58
Power supply 1: Error
59
Power supply 2: Error
60
Actuator switch off
61
Undervoltage
62
Overvoltage
63
Overload
64
Reserve
65
Hardware interrupt
66
Actuator warning
67
Safety-related shutdown
68
Ambiguous error
69
Error 1 in actuator/sensor
70
Error 2 in actuator/sensor
71
Channel / module temporarily not available
72
Channel is being calibrated
73
Discrepancy error
74
Overcurrent at output driver
75
P-output driver defective
76
Internal P short-circuit
77
External P short-circuit / cross-circuit
78
Internal error in the read circuit/test circuit
79
Short-circuit of the output to M or output driver defective
80
Switching frequency exceeded
81
PROFIsafe communication error
82
Error
83
Unknown error
84
Short-circuit
85
Wire break
86
Warning
87
Shutdown
88
Unknown error
89
Fault
544
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Text Message text no.
Remark
90
Short-circuit or overload on the external encoder supply
91
Missing supply voltage
92
Power switch-off
93
Undervoltage or overload of power supply
94
Overvoltage on backplane
95
Overcurrent
96
Supply voltage disrupted
97
Input voltage illegal
98
Common mode error
Appendix 9.11 Text libraries
9.11.11
Text library for MOD_ D8_S7P, MOD_ D16_S7P
The following table lists the text library message texts and their numbers for the blocks MOD_D8_S7P and MOD_D16_S7P:
Text Message text no.
1
Short circuit
2
Undervoltage
3
Overvoltage
4
Overload
5
Excess temperature
6
Wire break
7
High limit violated
8
Low limit violated
9
Error
10
Simulation running
11
Unknown error
12
Unknown error
13
Unknown error
14
Unknown error
15
Missing parameters
16
Parameter assignment error
17
No supply voltage
18
Fuse defective
19
Communication error
20
Mass error
21
Reference channel error
22
Process interupt lost
23
Limit warning
24
Actuator switch off
25
Safety event
Remark
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
545
Appendix 9.11 Text libraries
Text Message text no.
26
External Error
27
General Error
28
PROFIsafe communication error
29
Error 1 in actuator/encoder
30
Error 2 in actuator/encoder
31
Channel/component temporarily unavailable
32
Process interrupt lost
33
Withdrawn
34
Plugged
35
Wrong module type plugged
36
Faulty module plugged
37
Module plugged (parameter error)
Remark
9.11.12
Text library for MOD_CP_PN (FB201)
The following table lists the message texts and their numbers from the text library for the block MOD_CP_PN (FB201):
Text Message text no.
1
Parameter assignment error
2
Common mode error
3
Short circuit to P
4
Short circuit to M
5
Wire break
6
Reference channel error
7
Below measuring range
8
Above measuring range
9
Load voltage missing
10
Ground error
11
Sensor supply missing
12
Excess temperature
13
Module OK
14
Internal error
15
External error
16
External auxiliary voltage missing
17
Front connector missing
18
No parameter assignment
19
Wrong parameters in module
20
Wrong/missing user module
21
Communication problem
22
Operating mode RUN/STOP
Remark
546
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Text Message text no.
23
Time monitoring addressed
24
Failure mod. int. supply volt.
25
Battery depleted
26
Total backup battery failure
27
Processor failure
28
EPROM error
29
RAM error
30
ADC/DAC error
31
Fuse blown
32
Process interrupt lost
33
Withdrawn
34
Plugged
35
Wrong module type plugged
36
Faulty module plugged
37
Module plugged (parameter assignment error)
38
Chatter error
39
Changeover contact diagnostics
40
41
42
Error
Remark
Appendix 9.11 Text libraries
9.11.13
Text Library for MOD_MS
The following table lists the text-library message texts and their numbers for the block MOD_MS (FB 96):
Text Message Text No.
1
Parameter assignment error
2
Common mode error
3
Short-circuit to P
4
Short circuit to M
5
Wire break
6
Reference channel error
7
Measuring range violation low
8
Measuring range violation high
9
Load voltage missing
10
Chassis ground error
11
Sensor supply missing
12
Excess temperature
13
Module OK
14
Internal error
Remark
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
547
Appendix 9.11 Text libraries
Text Message Text No.
15
External error
16
External auxiliary voltage missing
17
Front connector missing
18
No configuration
19
Wrong module parameters
20
Wrong/missing user module
21
Communication error
22
Operating mode RUN/STOP
23
Timeout
24
Failure mod. int. supply volt.
25
Battery depleted
26
Total backup failure
27
CPU failure
28
EPROM error
29
RAM error
30
ADC/DAC error
31
Fuse tripped
32
Process interrupt lost
33
Removed
34
Plugged
35
Wrong module type plugged
36
Faulty module inserted
37
Module inserted (parameter error)
38
Chatter error
39
Changeover contact diagnostics
40
Sensor or load voltage loss
41
Faulty fuse
42
Undervoltage
43
Overvoltage
44
Actuator warning
45
Actuator OFF
46
Safety-related shutdown
47
Unknown error
48
Short-circuit
49
Error
50
51
Remark RUN: going STOP: coming
548
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
9.11.14
Appendix 9.11 Text libraries
Text Library for OB_BEGIN
The following table lists the text-library message texts and their numbers for the block OB_BEGIN (FB 100):
Text No. Message Text
1
Nested stack error
2
Master control relay stack error
3
Max. nesting depth for synchronous errors exceeded
4
U-stack nesting depth exceeded
5
B-stack nesting depth exceeded
6
Local data allocation error
7
Unknown opcode
8
Code length error
Remark Error code B#16#71: Error code B#16#72: Error code B#16#73 Error code B#16#74 Error code B#16#75 Error code B#16#76 Error code B#16#78 Error code B#16#7A
9.11.15
Text library for OB_BEGIN_PN (FB130) / OB_BEGIN_HPN (FB205)
The following table lists the message texts and their text numbers from the text library for the block OB_BEGIN_PN (FB130) / OB_BEGIN_HPN (FB205):
Text No. Message Text
1
Nested stack error
2
Master control relay stack error
3
Max. nesting depth for synchronous errors exceeded
4
U-stack nesting depth exceeded
5
B-stack nesting depth exceeded
6
Local data allocation error
7
Unknown opcode
8
Code length error
Remark Error code B#16#71: Error code B#16#72: Error code B#16#73 Error code B#16#74 Error code B#16#75 Error code B#16#76 Error code B#16#78 Error code B#16#7A
9.11.16
Text library for MOD_ENME_S7P
The following table lists the text library message texts and their numbers for the blocks MOD_ENME_S7P:
Text Message text no.
1
Parameter assignment error
2
Common mode error
3
P short circuit
4
M short circuit
5
Wire break
6
Reference channel error
7
Measuring range/low limit violated
Remark
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
549
Appendix 9.11 Text libraries
Text Message text no.
Remark
8
Measuring range/high limit violated
9
Load voltage missing
10
Mass error
11
Sensor supply missing
12
Excess temperature
13
Module OK
14
Internal error
15
External error
16
External auxiliary voltage missing
17
Front connector missing
18
Missing parameters
19
Wrong parameter in module
20
Simulating running
21
Communication error
22
Operating mode RUN/STOP
RUN: going STOP: coming
23
Time monitoring addressed
24
Module failure int. supply voltage
25
Battery empty
26
Total backup battery failure
27
Process failure
28
EPROM error
29
RAM error
30
ADC/DAC error
31
Fuse blown
32
Process interrupt lost
33
Withdrawn
34
Plugged
35
Wrong module type plugged
36
Faulty module plugged
37
Module plugged (param. error)
38
Chatter error
39
Changeover contact diagnostics
40
Front connector missing or sensor/load voltage missing
41
Fuse defective
42
AI hardware error
43
AI wire break
44
AI below measuring range
45
AI above measuring range
46
AO wire break
47
AO short circuit
48
Limit warning
49
General error
550
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Text Message text no.
50
Signal A faulty
51
Signal B faulty
52
Signal N faulty
53
Incorrect value transferred between channels
54
Sensor supply 5.2 V/8.2 V faulty
55
24 V sensor supply faulty
56
Signal line error Namur sensor
57
Readback error
58
Power supply 1: Error
59
Power supply 2: Error
60
Actuator switch off
61
Under voltage
62
Over voltage
63
Overload
64
Standby
65
Hardware interrupt
66
Actuator alarm
67
Safety event
68
Ambiguous error
69
Error 1 in actuator/sensor
70
Error 2 in actuator/sensor
71
Channel/module temporarily unavailable
72
Calibrating channel
73
Discrepancy error
74
Over current at output driver
75
Faulty P output driver
76
Internal P short circuit
77
External P short circuit/cross fault
78
Internal fault in the read circuit/test circuit
79
Output short circuit to M or faulty output driver
80
Switching frequency exceeded
81
PROFIsafe communication error
82
Error
83
Unknown error
84
Short circuit
85
Wire break
86
Warning
87
Shutdown
88
Unclear error
89
Faulty
90
Faulty
91
No supply voltage
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Remark
Appendix 9.11 Text libraries
551
Appendix 9.11 Text libraries
Text Message text no.
92
Power switch-off
93
Under voltage or overload of the power supply
94
Over voltage of the bus circuit board
95
Overcurrent
96
Supply voltage faulty
97
Input voltage illegal
98
Common mode error
Remark
552
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
Index
A
Addressing, 530
B
Block icons OB_BEGIN_BASE, 19 OB_BEGIN_HPN_BASE, 19 OB_BEGIN_PN_BASE, 19
C
ChkREAL, 515 Description, 515
CONEC, 27, 29 Description, 27 I/Os, 29
Coordination of FMCS_PID/FMT_PID, 23 CPU_RT, 31, 38
Description, 31 I/Os, 38
D
DB_PAM_CD, 511, 513 Description, 511, 513
DB_PAM_CPU, 512 Description, 512
Description, 320 OR_32_TS, 327
Description of, 27, 31, 49, 53, 56, 64, 83, 88, 101, 103, 109, 115, 122, 128, 134, 137, 146, 162, 166, 191, 198, 207, 216, 233, 237, 244, 249, 255, 261, 265, 292, 301, 305, 310, 315, 318, 321, 324, 330, 333, 337, 348, 360, 366, 370, 376, 380, 385, 393, 400, 408, 416, 422, 425, 426, 427, 428, 429, 433, 438, 443, 446, 451, 458, 461, 464, 467, 470, 473, 482, 488, 491, 495, 498, 502, 505, 511, 512, 513
ChkREAL, 515 CONEC, 27 CPU_RT, 31 DB_PAM_CD, 511, 513 DB_PAM_CPU, 512 DIAG_AB, 40 DPAY_V0, 43
DPAY_V1, 49 DPDIAGV0, 53 DREP, 56 DREP_L, 64 FB_DB_CD, 495 FB_DB_CPU, 498 FB_DB_IM, 502 FM_CNT, 83 FM_CO, 23 IM_TS_PN, 88 IMDRV_TS, 94 MHA_CO, 101 MOD_1, 103 MOD_2, 109 MOD_3, 115 MOD_4, 122 MOD_64, 128 MOD_CENTRAL, 134 MOD_CP, 137 MOD_D1, 146, 182 MOD_D2, 166 MOD_D32_PN, 191 MOD_D8, 198 MOD_HA, 216 MOD_MS, 237 MOD_PAL0, 249 MOD_PAX0, 255 OB_BEGIN, 270 OB_BEGIN_HPN, 285 OB_BEGIN_PN, 279 OB_DIAG1, 292, 310 OB_DIAG2, 301 OB_DIAGF2, 315 OB_END, 318 OB5X2OB5, 320 OR_16_PN, 321 OR_32_PN, 324 OR_32TPN (FB431), 330 OR_8_PN, 333 OR_H16PN, 337 OR_HA16C, 340 OR_M_16C, 348 OR_M_32C, 353 OR_M_8C, 360 OR_MHA_CO, 366 OR_MHA1_CO, 368 PADP_L00, 370 PADP_L01, 376 PADP_L02, 380
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
553
Index
PADP_L10, 385 PAM_CD, 393 PAM_CPU, 400 PAM_IF, 505 PAM_IM, 408 PAM_SM, 416 PNTS2BCD, 425 PNTS2DT, 426 PNTS2ISP, 427 PO_UPDAT, 428 PS, 429 QC_CHNG, 515 RACK, 433, 443 RACK_CFU, 438 RACK_PN1, 446 RACK_PNT, 451 RED_AI, 458 RED_AIH, 461 RED_AQ, 464 RED_AQH, 467 RED_DI, 470 RED_DQ, 473 RED_F, 476 RED_MF, 479 SUBNET, 482 SUBNET_PN, 488 WRDS_CO, 491 Description of MOD_DRV, 211 Description of: MOD_D16_S7P, 162 Description of: MOD_D8_S7P, 207 Description of: MOD_ENME, 261 Description of: MOD_ENME_S7P, 265 Description of: MOD_HA_S7P, 233 Description of: MOD_SWT, 244 Description of: OB_DIAG_NC, 305 Description of: PDM_MS, 422 DIAG_AB Description, 40 I/Os, 42 DPAY V1, 51 I/Os, 51 DPAY V1_PN, 52 I/Os, 52 DPAY_V0, 47 Description, 43 I/Os, 47 DPAY_V1, 49 Description, 49 DPDIAGV0, 53, 55 Description, 53 I/Os, 55
554
DREP, 56, 61 Description, 56 I/Os, 61
DREP_L, 64, 68 Description, 64 I/Os, 68
E
Error Information of Output Parameter MSG_STAT, 530
F
FB_DB_CD, 495, 536 Description, 495 Text library, 536
FB_DB_CPU, 498, 536 Description, 498 Text library, 536
FB_DB_IM, 502, 536 Description, 502 Text library, 536
FF_MOD32, 536 Text library, 536
FM_CNT, 83, 86 Description, 83 I/Os, 86
FM_CO Description, 23 I/Os, 25
G
General information about the block description, 15
I
I/Os of, 29, 38, 47, 51, 52, 55, 61, 68, 86, 106, 113, 119, 125, 131, 135, 140, 143, 152, 162, 172, 200, 208, 212, 222, 225, 229, 233, 241, 245, 251, 257, 261, 266, 274, 279, 285, 295, 298, 303, 306, 319, 374, 390, 392, 397, 405, 431, 436, 443, 485, 488
CPU_RT, 38 DIAG_AB, 42 DPAY V1, 51 DPAY V1_PN, 52 DPAY_V0, 47 DPDIAGV0, 55 DREP, 61
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
DREP_L, 68 FM_CNT, 86 FM_CO, 25 IMDRV_TS, 98 MOD_1, 106, 113 MOD_2, 106, 113 MOD_3, 119 MOD_4, 125 MOD_64, 131 MOD_CENTRAL, 135 MOD_CP, 140 MOD_CP_PN, 143 MOD_D1, 152, 172 MOD_D2, 152, 172 MOD_D3, 188 MOD_D8, 200 MOD_HA, 222 MOD_HA_PN, 225 MOD_HA_PN1, 229 MOD_MS, 241 MOD_PAL0, 251 MOD_PAX0, 257 OB_BEGIN, 274 OB_BEGIN_HPN, 285 OB_BEGIN_PN, 279 OB_DIAG1, 295 OB_DIAG1_PN, 298 OB_DIAG2, 303 OB_END, 319 OR_32_TS, 328 OR_HA16C, 343, 348, 353, 362 OR_M_16C, 343, 348, 353, 362 OR_M_32C, 343, 348, 353, 362 OR_M_8C, 343, 348, 353, 362 PADP_L00/L01/L02, 374 PADP_L10, 390 PADP_L10_PN, 392 PAM_CD, 397 PAM_CPU, 405 PS, 431 RACK, 436 RACK_PN, 443 RED_F, 478 RED_MF, 480 SUBNET, 485 SUBNET_PN, 488 I/Os of: MOD_D8_S7P, 162, 208 I/Os of: MOD_DRV, 212 I/Os of: MOD_ENME, 261 I/Os of: MOD_ENME_S7P, 266 I/Os of: MOD_HA_S7P, 233 I/Os of: MOD_SWT, 245
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
I/Os of: OB_DIAG_NC, 306 IM_TS_PN, 88
Description, 88 IMDRV_TS
Description, 94 I/Os, 98 Message texts, 100
M
Maintenance status MS, 533 Message classes, 531 Message texts of
IMDRV_TS, 100 MHA_CO, 101
Description, 101 MOD_ CP_PN
Text library, 546 MOD_1, 103, 106, 113, 537
Description, 103 I/Os, 106, 113 Text library, 537 MOD_2, 106, 109, 113, 537 Description, 109 I/Os, 106, 113 Text library, 537 MOD_3, 115, 119, 537 Description, 115 I/Os, 119 Text library, 537 MOD_4, 122, 125 Description, 122 I/Os, 125 MOD_64, 128, 131, 537 Description, 128 I/Os, 131 Text library, 537 MOD_CENTRAL, 134, 135 Description, 134 I/Os, 135 MOD_CP, 137, 140, 537 Description, 137 I/Os, 140 Text library, 537 MOD_CP_PN, 143, 546 I/Os, 143 MOD_D1, 146, 152, 172, 539 Description, 146 I/Os, 152, 172 Text library, 539 MOD_D16_PN, 542 Text library, 542
Index 555
Index
MOD_D16_S7P, 162 MOD_D16_S7P: Description, 162 MOD_D2, 152, 166, 172, 537
Description, 166 I/Os, 152, 172 Text library, 537 MOD_D24_PN, 542 Text library, 542 MOD_D3 Description, 182 I/Os, 188 Text library, 540 MOD_D32_PN, 191 Description, 191 MOD_D8, 198, 200, 540 Description, 198 I/Os, 200 MOD_D8_PN, 542 Text library, 542 MOD_D8_S7P, 162, 207, 208 MOD_D8_S7P: Description, 207 MOD_D8_S7P: I/Os, 162, 208 MOD_DRV, 211, 212 MOD_DRV: I/Os, 212 MOD_ENME, 261 MOD_ENME: Description, 261 MOD_ENME: I/Os, 261 MOD_ENME_S7P, 265, 266 MOD_ENME_S7P: Description, 265 MOD_ENME_S7P: I/Os, 266 MOD_HA, 216, 222 Description, 216 I/Os, 222 MOD_HA_PN, 225 I/Os, 225 MOD_HA_PN1, 229 I/Os, 229 MOD_HA_S7P, 233 MOD_HA_S7P: Description, 233 MOD_HA_S7P: I/Os, 233 MOD_MS, 237, 241, 547 Description, 237 I/Os, 241 Text library, 547 MOD_PAL0, 249, 251, 537 Description, 249 I/Os, 251 Text library, 537 MOD_PAX0, 255, 257, 537 Description, 255 I/Os, 257 Text library, 537
556
MOD_SWT, 244, 245, 536 Text library, 536
MOD_SWT: Description, 244 MOD_SWT: I/Os, 245 MODE, 517 MODE settings for PA/FF field devices, 528 MODE Settings for SM Modules, 517 MSG_STAT, 530
O
OB_BEGIN, 274, 549 Description, 270 I/Os, 274 Text library, 549
OB_BEGIN_HPN, 285 Description, 285 I/Os, 285
OB_BEGIN_PN, 279, 549 Description, 279 I/Os, 279 Text library, 549
OB_DIAG_NC, 305, 306 OB_DIAG_NC: Description, 305 OB_DIAG_NC: I/Os, 306 OB_DIAG1, 292, 295, 298, 310
Description, 292, 310 I/Os, 295 OB_DIAG1_PN I/Os, 298 OB_DIAG2, 301, 303 Description, 301 I/Os, 303 OB_DIAGF2, 315 Description, 315 OB_END, 318, 319 Description, 318 I/Os, 319 OB5X2OB5, 320 Description, 320 OMODE settings for SM modules, 527 OR_16_PN, 321 Description, 321 OR_32_PN, 324 Description, 324 OR_32_TS Description, 327 I/Os, 328 OR_32TPN (FB431), 330 Description, 330, 331 OR_8_PN, 333 Description, 333
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
OR_H16PN, 337 Description, 337
OR_HA16C Description, 340 I/Os, 343, 348, 353, 362
OR_M_16C, 348 Description, 348 I/Os, 343, 348, 353, 362
OR_M_32C Description, 353 I/Os, 343, 348, 353, 362
OR_M_8C, 360 Description, 360 I/Os, 343, 348, 353, 362
OR_MHA_CO, 366 Description, 366
OR_MHA1_CO Description, 368
P
PA field device status and diagnostics information, 533 PA/FF device
Variant identifier, 529 PA/FF field devices
Settings, 528 PADP_L00, 370, 537
Description, 370 Text library, 537 PADP_L00/L01/L02, 374 I/Os, 374 PADP_L01, 376, 537 Description, 376 Text library, 537 PADP_L02, 380, 537 Description, 380 Text library, 537 PADP_L10, 385, 390, 392 Description, 385 I/Os, 390 PADP_L10_PN I/Os, 392 PAM_CD, 393, 397, 536 Description, 393 I/Os, 397 Text library, 536 PAM_CPU, 400, 405, 536 Description, 400 I/Os, 405 Text library, 536
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
PAM_IF, 505, 536 Description, 505 Text library, 536
PAM_IM, 408, 536 Description, 408 Text library, 536
PAM_SM, 416, 536 Description, 416 Text library, 536
PDM_MS, 422 PDM_MS: Description, 422 PNTS2BCD, 425
Description, 425 PNTS2DT, 426
Description, 426 PNTS2ISP, 427
Description, 427 PO_UPDAT, 428
Description, 428 PS, 429, 431
Description, 429 I/Os, 431
Q
QC_CHNG, 515 Description, 515
R
RACK, 433, 436, 443 Description, 433, 443 I/Os, 436
RACK_CFU, 438 Description, 438
RACK_PN, 443 I/Os, 443
RACK_PN1, 446 Description, 446
RACK_PNT, 451 Description, 451
RED_AI, 458 Description, 458
RED_AIH, 461 Description, 461
RED_AQ, 464 Description, 464
RED_AQH, 467 Description, 467
RED_DI, 470 Description, 470
Index 557
Index
RED_DQ, 473 Description, 473
RED_F Description, 476 I/Os, 478
RED_MF Description, 479 I/Os, 480
S
SUBNET, 482, 485 Description, 482 I/Os, 485
SUBNET_PN, 488 Description, 488 I/Os, 488
T
Text library for, 536, 537, 539, 546, 547, 549 DREP, 537 DREP_L, 537 FB_DB_CD, 536 FB_DB_CPU, 536 FB_DB_IM, 536 FF_MOD32, 536 MOD_ CP_PN, 546 MOD_1, 537 MOD_2, 537 MOD_3, 537 MOD_64, 537 MOD_CP, 537 MOD_D1, 539 MOD_D16_PN, 542 MOD_D2, 537 MOD_D24_PN, 542 MOD_D3, 540 MOD_D8_PN, 542 MOD_MS, 547 MOD_PAL0, 537 MOD_PAX0, 537 MOD_SWT, 536 OB_BEGIN, 549 OB_BEGIN_PN, 549 PADP_L00, 537 PADP_L01, 537 PADP_L02, 537 PAM_CD, 536 PAM_CPU, 536 PAM_IF, 536
558
PAM_IM, 536 PAM_SM, 536
V
Variant identifier PA/FF device, 529
W
WRDS_CO, 491 Description, 491
Basis Library (V9.0 SP3) Function Manual, 06/2019, A5E40797470-AD
AH XSL Formatter V6.6 MR1 for Windows (x64) : 6.6.2.35616 (2018/10/15 18:42JST) Antenna House PDF Output Library 6.6.1317 (Windows (x64)); modified using iTextSharp 5.0.2 (c) 1T3XT BVBA