PL7 Junior/Pro

Premium PLC Applications

Standard applications
TLX DS 57 PL7 xx eng
2
 Related Documentation

Related Documentation

At a Glance This manual is made up of 8 parts:

l Volume 1
l Common application-specific functions
l Discrete Application
l AS-i implementation
l AS-i V2 implementation
l Dialog Operator Application
l Volume 2
l Counting Application
l Volume 3
l Axes Control Application
l Volume 4
l Step by step Control Application
l Volume 5
l Electronic Cam Application
l Volume 6
l SERCOS Movement Command Application
l Volume 7
l Analog Application
l PID Control Application
l Weighing Application
l Volume 8
l Adjustment Application

TLX DS 57 PL7 xx 3
Related Documentation

4 TLX DS 57 PL7 xx
 Table of Contents

About the book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Part I Shared application-specific functions . . . . . . . . . . . . . . 17

Presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Chapter 1 Common application specific functions: General . . . . . . . . . . 19

Presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
General Presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Configuration of an application-specific function. . . . . . . . . . . . . . . . . . . . . . . . . 22
Adjustment of an application-specific function . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Debugging an application-specific function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Chapter 2 Objects associated with specific applications . . . . . . . . . . . . 27

Presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
2.1 Addressing of language objects associated with specific applications . . . . . . . . 28
Presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Addressing of built-in application-specific interfaces. . . . . . . . . . . . . . . . . . . . . . 29
Addressing input/output module objects in rack . . . . . . . . . . . . . . . . . . . . . . . . . 31
Addressing of language objects for modules remoted on the FIPIO bus . . . . . . 33
Addressing of language objects associated with AS-i bus . . . . . . . . . . . . . . . . . 35
2.2 Implicit exchanges. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Implicit exchanges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
2.3 Explicit exchanges. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Explicit exchanges: General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
READ_STS: Reading status words. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
WRITE_CMD: Writing command words . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
READ_PARAM: Reading adjustment parameters . . . . . . . . . . . . . . . . . . . . . . . 45
WRITE_PARAM: Writing adjustment parameters . . . . . . . . . . . . . . . . . . . . . . . . 46
SAVE_PARAM: Saving adjustment parameters . . . . . . . . . . . . . . . . . . . . . . . . . 47
RESTORE_PARAM: Restoring adjustment parameters . . . . . . . . . . . . . . . . . . . 49
Exchange and report management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
2.4 Presymbolization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Presymbolized objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

5
 Automatic symbolization of objects associated with a channel . . . . . . . . . . . . . . 54

Chapter 3 Application-specific instructions . . . . . . . . . . . . . . . . . . . . . . . 55

Presentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Application-specific instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Accessing a specific function, method or procedure type instruction . . . . . . . . . 57

Chapter 4 Appendices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Presentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Reminders concerning the configuration editor . . . . . . . . . . . . . . . . . . . . . . . . . . 60
The PL7 toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
The PL7 status bar. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
How to declare a module in a PLC rack. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
How to declare a remote module on the FIPIO bus. . . . . . . . . . . . . . . . . . . . . . . 64
Confirming the configuration of a module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Globally reconfiguring an application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Application-specific fault processing (in-rack modules) by program . . . . . . . . . . 68
Processing of FIPIO faults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Part II Discrete specific application . . . . . . . . . . . . . . . . . . . . . . 71

Presentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Chapter 5 General presentation of the discrete application -specific

function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Introduction to the Discrete Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Chapter 6 Configuration of the discrete specific application . . . . . . . . . 77

Presentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
6.1 Configuring a discrete module: General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Presentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Description of the configuration screen for a discrete module . . . . . . . . . . . . . . . 79
Accessing the configuration screen for an in -rack discrete module. . . . . . . . . . . 80
Accessing the configuration screen for a discrete module remoted on the FIPIO bus
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Modifying the configuration parameters of a discrete module's: General . . . . . . 83
6.2 Discrete input channel parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Presentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
In-rack discrete input parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Parameters of TBX discrete inputs remoted on the FIPIO bus . . . . . . . . . . . . . . 87
Parameters of Momentum discrete inputs remoted on the FIPIO bus. . . . . . . . . 88
Parameters of IP67 discrete inputs remoted on the FIPIO bus . . . . . . . . . . . . . . 89
6.3 Discrete output channel parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Presentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Discrete output parameters for in-rack 8-channel modules. . . . . . . . . . . . . . . . . 91
Discrete output parameters for in-rack modules with over 8 channels . . . . . . . . 92

6
 Parameters of 8, 10 or 12 channel TBX discrete outputs remoted on the FIPIO bus
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Parameters of 16 channel TBX discrete outputs remoted on the FIPIO bus . . . 95
Momentum Parameters of Momentum discrete outputs remoted on the FIPIO bus
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Parameters of IP67 discrete outputs remoted on the FIPIO bus. . . . . . . . . . . . . 97
6.4 Configuration of discrete parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Configuring the programmable channels of the TBX DMS 16P22 module . . . . . 99
Modifying the Task parameter of a discrete module . . . . . . . . . . . . . . . . . . . . . 100
Modifying the Wiring check parameter of a TBX discrete module. . . . . . . . . . . 101
Modifying the Monitoring of external supply fault parameter for a discrete module.
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Modifying the Functions parameter of a discrete input module. . . . . . . . . . . . . 103
Modifying the Filtering parameter of a discrete input module.. . . . . . . . . . . . . . 105
How to modify the Latching parameter of a discrete input module . . . . . . . . . . 106
Parametering the Run/Stop input of a discrete module. . . . . . . . . . . . . . . . . . . 107
Modifying the Fallback mode parameter of a discrete output module. . . . . . . . 108
Modifying the Reactivation of outputs parameter of a discrete module. . . . . . . 109

Chapter 7 Debugging discrete modules . . . . . . . . . . . . . . . . . . . . . . . . .111

At a Glance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Presentation of the debug function of a discrete module. . . . . . . . . . . . . . . . . . 112
Description of the debug screen of a discrete module . . . . . . . . . . . . . . . . . . . 113
Accessing the debug screen for an in-rack discrete module. . . . . . . . . . . . . . . 115
Accessing the diagnostics function of a discrete module . . . . . . . . . . . . . . . . . 116
Accessing the channel diagnostics function of a discrete module . . . . . . . . . . 117
Accessing the forcing/unforcing function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
How to access the SET and RESET commands . . . . . . . . . . . . . . . . . . . . . . . 119
Accessing the masking/unmasking function for an event . . . . . . . . . . . . . . . . . 120
Accessing the reactivation of outputs command . . . . . . . . . . . . . . . . . . . . . . . . 121
Maintain outputs of a discrete module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

Chapter 8 Bits and words associated with discrete specific applications

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
8.1 Addressing of discrete I/O module objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Addressing of language objects associated with discrete in-rack I/O modules. 125
Addressing of language objects associated with discrete I/O modules remoted on
the FIPIO bus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Indexable discrete I/O objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
8.2 Language objects associated with the discrete specific application . . . . . . . . . 128
Presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Implicit exchange language objects associated with the discrete specific application
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

7
 Exchange management: Exchanges in progress module %MW@module.MOD.0:Xj
or channel %MW@module.i.0:Xj . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Exchange management: Module %MW@module.MOD.1:Xj or channel
%MW@module.i.1:Xj report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Explicit exchange objects: General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Explicit exchange object: %MW@module.i.2:Xj channel status . . . . . . . . . . . . 135
Explicit exchange object: Status Module %MW@module.MOD.2:Xj. . . . . . . . . 136
Explicit exchange object: %MW@module.i.3:Xj channel command . . . . . . . . . 137

Chapter 9 Installation of the discrete reflex module . . . . . . . . . . . . . . . 139

Presentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
9.1 General presentation of discrete reflex module . . . . . . . . . . . . . . . . . . . . . . . . . 140
Presentation of discrete reflex module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
9.2 Reflex function blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
Presentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
Function block: Direct . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Reflex function block: Combinational. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
Reflex function block: Operation timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
Reflex function block: Idle timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Reflex function block: Operation-idle timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Reflex function block: 2 value operation timer . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Reflex function block: Operation-idle time with value selection . . . . . . . . . . . . . 153
Reflex function block: Retriggerable monostable. . . . . . . . . . . . . . . . . . . . . . . . 156
Reflex function block: Monostable with time delay . . . . . . . . . . . . . . . . . . . . . . 157
Reflex function block: 2 value monostable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
Reflex function block: Oscillator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Reflex function block: D flip-flop. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Reflex function block: T flip-flop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
Reflex function block: 2 threshold counter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
Reflex function block: Came électronique simple . . . . . . . . . . . . . . . . . . . . . . . 168
Reflex function block: 1 threshold intervalometer . . . . . . . . . . . . . . . . . . . . . . . 170
Reflex function block: Burst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
Reflex function block: PWM (Pulse Width Modulation) . . . . . . . . . . . . . . . . . . . 173
Reflex function block: Detection of underspeed. . . . . . . . . . . . . . . . . . . . . . . . . 174
Reflex function block: Speed monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
Reflex function block: Type 1 command-check . . . . . . . . . . . . . . . . . . . . . . . . . 179
Reflex function block: Type 2 command-check . . . . . . . . . . . . . . . . . . . . . . . . . 181
Reflex function block: Command-counting . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Reflex function block: Fault Signaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
9.3 Configuration of discrete reflex module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
Presentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
Configuring the discrete reflex module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
Presentation of the reflex function configuration editor . . . . . . . . . . . . . . . . . . . 189
Assigning and configuring a reflex function . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
Adjusting the configuration parameters of a reflex function . . . . . . . . . . . . . . . . 192
Associating an event with a virtual output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193

8
 9.4 Bits and words associated with discrete reflex module . . . . . . . . . . . . . . . . . . . 194
Presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
Implicit exchange language objects associated with module TSX DMY 28 RFK195
Explicit exchange language objects associated with module TSX DMY 28 RFK
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197

Part III AS-i Bus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199

At a Glance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199

Chapter 10 General introduction to the AS-i Bus . . . . . . . . . . . . . . . . . . . 201

At a Glance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
Presentation of the AS-i Bus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
Architecture of the TSX SAY 100 module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
Structure of an AS-i slave . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
How to declare an AS-i communication module in the PLC rack . . . . . . . . . . . 207
How to access the AS-i Bus configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208

Chapter 11 AS-i bus configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .209

At a Glance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
Description of an AS-i communication module’s configuration screen . . . . . . . 210
How to define a slave device on the AS-i bus . . . . . . . . . . . . . . . . . . . . . . . . . . 212
How to modify the AS-i Bus software configuration . . . . . . . . . . . . . . . . . . . . . 214
How to access the description of an AS-i slave . . . . . . . . . . . . . . . . . . . . . . . . 215
How to define a new slave profile in the standard AS-I catalogue . . . . . . . . . . 217
How to modify AS-i slave general parameters: Automatic addressing . . . . . . . 219
How to modify AS-i slave general parameters: Fallback mode. . . . . . . . . . . . . 220

Chapter 12 Debugging the AS-i bus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221

At a Glance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
Introduction to the Debug function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
Description of an AS-i module’s debugging screen. . . . . . . . . . . . . . . . . . . . . . 223
How to access functionality in the module diagnostics and channel diagnostics for
an AS-i device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
Displaying the slaves’ status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
How to access adjustment of an AS-i device’s parameters . . . . . . . . . . . . . . . 228
How to access the AS-i channels’ forcing/unforcing function . . . . . . . . . . . . . . 229
How to access the SET and RESET commands of the AS-i channels . . . . . . . 230
Automatic replacement of a faulty AS-i slave . . . . . . . . . . . . . . . . . . . . . . . . . . 231
How to insert a slave device into an existing AS-i configuration. . . . . . . . . . . . 232
How to modify the address of an AS-i device . . . . . . . . . . . . . . . . . . . . . . . . . . 233

Chapter 13 Bits and words associated with the AS-i function . . . . . . . . 235
At a Glance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
13.1 Addressing objects associated with the AS-i function . . . . . . . . . . . . . . . . . . . . 236
Adressing language objects associated with slave devices connected to the AS-i
bus. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236

9
 13.2 Language objects associated with the AS-i function . . . . . . . . . . . . . . . . . . . . . 237
At a Glance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
Implicit exchange objects associated with the AS-i function . . . . . . . . . . . . . . . 238
Management of exchanges: Module %MWxy.MOD.0:Xj or channel MWxy.0.0 :Xj
exchanges in progress. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
Exchange management: Module %MWxy.MOD.1:Xj or channel %MWxy.i.1:Xj
report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
Explicit exchange objects: General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
Explicit exchange objects: %MWxy.0.2:Xj to %MWxy.0.23:Xj channel status. . 242
Explicit exchange object: %MWxy.0.24:Xj channel command. . . . . . . . . . . . . . 244
Explicit exchange object: %MWxy.0.25 to %MWxy.0.56 parameter adjustment 245
Explicit exchange object: Status %MWxy.MOD.2:Xj . . . . . . . . . . . . . . . . . . . . . 246

Chapter 14 AS-i operating mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247

At a Glance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
AS-i operating mode: General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
AS-i protected mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
AS-i wiring test mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
AS-I offline operating mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
AS-i data exchange off operating mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253

Chapter 15 AS-i performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255

AS-i bus performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255

Chapter 16 DFB for AS-i Security Monitor . . . . . . . . . . . . . . . . . . . . . . . . 257

AS-i security monitor DFBs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257

Part IV AS-i V2 bus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259

At a Glance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259

Chapter 17 General introduction to the AS-i V2 Bus . . . . . . . . . . . . . . . . 261

At a Glance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
Introduction to the AS-i V2 Bus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262
Architecture of TSX SAY 1000 Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
Structure of a Standard Address AS-i . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
Structure of a Standard Address AS-i slave . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
How to Declare an AS-i Communication Module in the PLC Rack . . . . . . . . . . 269
How to Access Configuration of the AS-i V2 Bus . . . . . . . . . . . . . . . . . . . . . . . 270

Chapter 18 AS-i V2 bus configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271

At a Glance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271
Description of an AS-i V2 communication module’s configuration screen. . . . . 272
How to define a slave device on the AS-i V2 bus . . . . . . . . . . . . . . . . . . . . . . . 274
How to modify the AS-i V2 Bus software configuration . . . . . . . . . . . . . . . . . . . 277
How to access the description of an AS-i V2 slave . . . . . . . . . . . . . . . . . . . . . . 278
How to define a new slave profile in the standard AS-i V2 catalog . . . . . . . . . . 280

10
 How to modify the general parameters of an AS-i V2 slave: Automatic addressing
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282
How to modify the parameters of an AS-i V2 slave. . . . . . . . . . . . . . . . . . . . . . 283
How to modify the parameters of an analog AS-i V2 slave . . . . . . . . . . . . . . . . 284
How to Modify the Parameters of an AS-i V2 Slave with Combined Parameters285
AS-i V2 security device issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286

Chapter 19 Debugging the AS-i V2 bus . . . . . . . . . . . . . . . . . . . . . . . . . . .287

At a Glance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287
Introduction to the Debug function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288
Description of an AS-i V2 module's debugging screen . . . . . . . . . . . . . . . . . . . 289
How to access module- and channel-diagnostics functions on an AS-i V2 device.
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291
Displaying the slaves' status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293
How to access adjustment of an AS-i V2 device's parameters . . . . . . . . . . . . . 295
How to access the AS-i V2 digital channels' forcing/unforcing function . . . . . . 297
How to access the SET and RESET commands on AS-i V2 digital channels . 298
How to modify the value of an analog channel . . . . . . . . . . . . . . . . . . . . . . . . . 299
Automatic replacement of a faulty AS-i V2 slave . . . . . . . . . . . . . . . . . . . . . . . 300
How to insert a slave device into an existing AS-i V2 configuration.. . . . . . . . . 301
How to modify the address of an AS-i V2 device . . . . . . . . . . . . . . . . . . . . . . . 302

Chapter 20 Bits and words associated with the AS-i V2 function . . . . . . 303
At a Glance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303
20.1 Addressing objects associated with the AS-i V2 function . . . . . . . . . . . . . . . . . 304
Addressing Language Objects Associated with Slave Devices Connected to the AS-
i V2 Bus. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304
20.2 Language objects associated with the AS-i V2 function . . . . . . . . . . . . . . . . . . 305
At a Glance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305
Implicit exchange objects associated with the AS-i V2 function . . . . . . . . . . . . 306
Exchange management: Module %MWxy.MOD.0:Xj or channel MWxy.0.0 :Xj
exchanges in progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308
Exchange management: Module %MWxy.MOD.1:Xj or channel %MWxy.i.1:Xj
report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309
Explicit exchange objects: General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310
Explicit Exchange Objects: %MWxy.MOD.2 and %MWxy.0.2:Xj to %MWxy.0.73:Xj
channel status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311
Constant %KWxy.i.r configuration objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314
Explicit Exchange Object: %MWxy.0.74:Xj channel command. . . . . . . . . . . . . 315
Explicit Exchange Object: %MWxy.0.75 to %MWxy.0.138 Parameter Adjustment
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316
Explicit Exchange Object: Status %MWxy.MOD.2:Xj . . . . . . . . . . . . . . . . . . . . 317

Chapter 21 AS-i V2 operating mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319

At a Glance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319
AS-i V2 Operating Mode: General. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320

11
 AS-i V2 Protected Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322
AS-i V2 Offline Operating Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323
AS-i V2 Data Exchange Off Operating Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . 324

Chapter 22 AS-i V2 performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325

AS-i V2 Bus Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325

Chapter 23 DFB for AS-i Security Monitor . . . . . . . . . . . . . . . . . . . . . . . . 327

At a Glance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327
Description of the security function block of the AS-i bus . . . . . . . . . . . . . . . . . 328
Operation of the AS-i security function block . . . . . . . . . . . . . . . . . . . . . . . . . . . 331
Programming rules for security DFB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332
How to implement a DFB function block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334

Part V Operator Dialog functions . . . . . . . . . . . . . . . . . . . . . . . 335

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335

Chapter 24 General presentation of the Operator Dialog functions . . . . 337

General presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337

Chapter 25 Built-in DOP functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339
25.1 Description of the parameters common to the different DOP functions. . . . . . . 340
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341
Parameters field: Console address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342
Parameters field: Data to be sent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345
Parameter field: Data to be received: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347
Parameters field: Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348
Message field. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352
Field zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354
25.2 Description of the built-in DOP functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356
List of the built-in DOP functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357
SEND_MSG function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358
GET_MSG function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361
ASK_MSG function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364
SEND_ALARM function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366
DISPLAY_MSG function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369
DISPLAY_GRP function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370
DISPLAY_ALRM function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372
ASK_VALUE function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374
GET_VALUE function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375
CONTROL_LEDS function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377
ASSIGN_KEYS function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380
PANEL_CMD function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383

12
 ADJUST function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386

Chapter 26 Appendices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .393

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393
26.1 Precautions for DOP use. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394
Precautions for DOP use. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394
26.2 Description of the built-in DOP functions "Data to send" parameter coding . . . 395
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395
PLC status message display: SEND_MSG function . . . . . . . . . . . . . . . . . . . . . 396
PLC checked status message entry: ASK_MSG and GET_MSG function . . . . 399
PLC alarm message display: SEND_ALARM function . . . . . . . . . . . . . . . . . . . 403
Display of status, alarm or a group of messages contained in the CCX 17 memory:
ASK_VALUE, DISPLAY_MSG, GET_VALUE, DISPLAY_ALRM and
DISPLAY_GRP functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406
Display of luminous column LEDS: CONTROL_LEDS function . . . . . . . . . . . . 407
Configuring command keys: ASSIGN_KEYS function . . . . . . . . . . . . . . . . . . . 408
Generic send command: PANEL_CMD function. . . . . . . . . . . . . . . . . . . . . . . . 410

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413

13
14
 About the book

At a Glance

Document Scope This manual deals with the software implementation of the applications (except
communication applications) on Premium/Atrium using PL7 software.

Validity Note This updated publication takes account of the functionality of PL7 V4.3. However it
supports the implementation of previous versions of PL7.

Related
Documents
Title of Documentation Reference Number
Hardware installation manual TSX DM 57 xxE

User Comments We welcome your comments about this document. You can reach us by e-mail at
TECHCOMM@modicon.com

TLX DS 57 PL7 xx 15
About the book

16 TLX DS 57 PL7 xx
 Shared application-specific
functions
I
Presentation

Subject of this This part gives a general overview of the acknowledgment of specific applications
part by the PL7 software.

What's in this This Part contains the following Chapters:

part?
Chapter Chaptername Page
1 Common application specific functions: General 19
2 Objects associated with specific applications 27
3 Application-specific instructions 55
4 Appendices 59

TLX DS 57 PL7 xx 17
Shared application-specific functions

18 TLX DS 57 PL7 xx
 Common application specific
functions: General
1
Presentation

Subject of this This chapter presents the common application specific functions of the PL7
chapter software.

What's in this This Chapter contains the following Maps:

Chapter?
Topic Page
General Presentation 20
Configuration of an application-specific function. 22
Adjustment of an application-specific function 24
Debugging an application-specific function 25

TLX DS 57 PL7 xx 19
General

General Presentation

Introduction The PL7 software allows for the installation of application-specific functions in
software form (DISCRETE, analog, process control, weighing, etc.).

The application-specific functions are automated functions which interface with the
control part (the PLC program) and the operational part (sensors, actuators and
man/machine interfaces).

An application-specific function on TSX Premium is presented, depending on the

application, in the form of:
l a module (e.g.: counting application),
l a built-in interface (e.g.: communication port).

0 1 2 3 4
Integrated P
Application-specific
T C
interface S S T module
Y X Y
0
2 5 o 4
6 7 o A
0 1 C
0 0 o
3 m
m

Software The table below gives a short description of the general principle for the installation
installation of an application-specific function. This principle will be covered again later in this
principle manual in more specific detail for each application.
Mode Phase Description
Local Configuration Configuration of the module or built-in interface
Local or online Symbolization Symbolization of variables associated with the
application-specific function.
Programming Programming of the function to be carried out using:
l bit and word objects associated with the module,
l application-specific instructions.

Online Transfer Transferring the application to the PLC.

Debug Debugging the application (I/O control, fault
identification).
Local (or online) Documentation Printing of the different information about the
application.

20 TLX DS 57 PL7 xx
 General

Note: The order shown above is given as an indication only; the PL7 software
allows the editors to be used interactively in the order required (however, the data
or program editor cannot be used if the I/O modules have not been configured first).

Software An application-specific function is installed using:

installation l standard PL7 tools:
resources l pull-down menus,
l status bars, tool bars,
l editors,
l ...
l application-specific screens,
l configuration screens,
l adjustment screens,
l debug screens,
l language objects giving program-based access to inputs and outputs of the
module or built-in interface.
l instructions relative to the application-specific function, where applicable.

Note: The different screens as well as the objects associated with an application-
specific module are accessible via the software as soon as the module is declared
in the configuration, without it even being necessary to write a program line.

TLX DS 57 PL7 xx 21
General

Configuration of an application-specific function.

Introduction The Configuration function makes it possible to define the operating characteristics
of the module or the application-specific interface.

This function is carried out from the PL7 configuration editor:

l in local mode,
l in online mode when the application is stored in non-write protected RAM (limited
to certain parameters).

Note: The configuration parameters are not modifiable by program.

Illustration The screen below is an example of a configuration screen of an application-specific

module (application-specific module TSY CTY 4A).

TSX CTY 4A [RACK 0 POSITION 4 ]

Configuration
Designation : 4 CH COUNTER MOD 40KHZ

Symbol :
Counter : Function: Task :
Counter 0 Up/Down counting MAST
Input interfaces Event
IA Up/Down counts, application direction EVT 3
Solid state counter Reset Outputs
Line check Multiply Manual
by 1 by 4
Automatic
Preset on IPres Fallback Mode
Reset
Rising edge IPres
Maintain
Read on IRead
Rising edgeIRead

Here, the operating characteristics are:

l the selection of a function associated with a channel: up counting, down counting
or up/down counting,
l selection of the task which updates the inputs/outputs of the module,
l the type of reactivation of outputs,
l the type of fallback mode,
l ...

22 TLX DS 57 PL7 xx
 General

Confirmation The characteristics defined in the configuration screen must be subject to a global
confirmation of the application. This may be done:
l in local mode, so that the modifications are taken into account,
l in online mode in order to:
l update the configuration parameters in the PLC,
l reconfigure the channel of the module with its new parameters (the adjustment
parameters return to their initial value).

TLX DS 57 PL7 xx 23
General

Adjustment of an application-specific function

Introduction The Adjustment function allows the operating parameters of the application-
specific module or interface to be displayed and modified, when they are modifiable.

This function is carried out from the PL7 adjustment editor:

l in local mode, in order to define the initial parameters (value of the parameters
during setup or on a cold restart),
l in online mode, in order to define the current parameters (values lost upon cold
restart if they have not been saved in advance).

Note: The adjustment parameters are modifiable by program.

Illustration The screen below is an example of an adjustment screen of an application-specific

module (application-specific module TSY CTY 4A).
TSX CTY 4A [RACK 0 POSITION 7 ]
Adjust
Designation : 4 CH COUNTER MOD.

Symbol :
Counter : Function:
Counter 0 Up/Down counting Counter output state

Preset value
1 000
Initial value 1000
Threshold value
Threshold 2 000
Initial value 2000
Threshold 3 000
Initial value 3000
Setpoint values
High 0
Initial value 0
Low 0
Initial value 0

Here, the operating parameters are:

l the threshold values,
l the setpoint values,
l the counter output states.

Confirmation The characteristics defined in the adjustment screen must, depending on the mode,
be subject to:
l local: a global confirmation of the application,
l online: confirmation of the modifications in order to update the current parameters
in the PLC and on the module channel.

24 TLX DS 57 PL7 xx
 General

Debugging an application-specific function

Introduction The Debug function of the module or the built-in application-specific interface
provides the tools to help with debugging of the application-specific function such as:
l display of module channel status,
l display of possible faults,
l control of language objects,
l and, in the event of a fault, access to the module or channel diagnostics,
l ...

This function is carried out in online mode, with the PLC in STOP or in RUN, from
the PL7 debug editor.

Illustration The screen below is an example of a debug screen of an application-specific module

(application-specific module TSX DSY 08R5).
TSX DSY 08R5 [RACK 0 POSITION 3]

Debug
Designation : 8O RELAY 50VA, BORN Version : 1.0

Global unforcing RUN ERR IO DIAG...

Chan. Symbol State Fault Reactivate Applied Q

0 0 DIAG... Reactivate STOP Control of channel x
1 0 DIAG... Forcing
2 0 DIAG...
3 0 DIAG... F4 Force to 0
4 0 DIAG...
5 0 DIAG...
6 DIAG... F5 Force to1
0
7 0 DIAG...
F6 Unforce

Write

F7 Set

F8 Reset

Here the debug tools are:

l forcing of the output channels to 0 or 1,
l access to module and channel diagnostics.

TLX DS 57 PL7 xx 25
General

26 TLX DS 57 PL7 xx
 Objects associated with specific
applications
2
Presentation

Subject of this This chapter presents the addressing and the exchange modes for language objects
chapter associated with PL7 specific applications.

What's in this This Chapter contains the following Sections:

Chapter?
Section Topic Page
2.1 Addressing of language objects associated with specific 28
applications
2.2 Implicit exchanges 37
2.3 Explicit exchanges 39
2.4 Presymbolization 52

TLX DS 57 PL7 xx 27
Objects associated with specific applications

2.1 Addressing of language objects associated with

specific applications

Presentation

Subject of this This section presents the addressing of language objects associated with
section application-specific modules.

What's in this This Section contains the following Maps:

Section?
Topic Page
Addressing of built-in application-specific interfaces 29
Addressing input/output module objects in rack 31
Addressing of language objects for modules remoted on the FIPIO bus 33
Addressing of language objects associated with AS-i bus 35

28 TLX DS 57 PL7 xx
 Objects associated with specific applications

Addressing of built-in application-specific interfaces

Presentation The TSX Premium range offers 4 types of built-in application-specific interfaces
such as:
l terminal socket link,
l communication interface,
l FIPIO interface,
l process control channels.
Their addressing depends on the basic topology of the application. In other words:
l on the type of power supply,
l on the processor type.

Illustration The illustration below shows the different basic topologies.

Processor slot 0

0 F
1 2 3 4
P T i
S S p
Y X i
o
0 2 5 1 2 3 4
6 o F
7 o P T
0 1 i
0 5
C S S p
o Y X
3 m i
m o
8 5
5 7 o 1
0 1 o L F 3 4
0 5 C P T o i
3 o S S o p
m Y X p
m i
s o
8 5
5 7 o
0 4 o
0 5 C
o
3 m
m

Processors slot 1

TLX DS 57 PL7 xx 29
Objects associated with specific applications

Number of The tableau below shows the assignment of built-in application-specific channel
channels addressing depending on the processor used in the application.
Processor Terminal Communication interface FIPIO interface Process control
socket channels
TSX 57-10/20/30 Channel x.0 Channel x.1 - -
TSX 57-102/202/302/402
TSX 57-103
TSX 57-252/352/452 Channel x.2
TSX 57-153
TSX 57-203 - Channels x.4 to x.13
TSX 57-303 Channels x.4 to x.18
TSX 57-253 Channel x.2 Channels x.4 to x.13
TSX 57-353 Channels x.4 to x.18
TSX 57-453 Channels x.4 to x.23
PMX 57-102/202 - Channels x.4 to x.13
PMX 57-352/452 Channel x.2
PCX 57-1012 - Channel 1 - -
PCX 57-3512 Channel 2
PCX 57-203 - Channels 4 to 13
PCX 57-353 Channel 2 Channels 4 to 18
(x): 0 when the processor is in slot 0,
1 when the processor is in slot 1,

30 TLX DS 57 PL7 xx
 Objects associated with specific applications

Addressing input/output module objects in rack

Presentation Addressing input/output module bit and word principal objects is done geopgraph-
ically. That means that it depends:
l on the number (address) of the rack,
l the physical position of the module in the rack,
l the module channel number.

Illustration Addressing is defined in the following way:

% I, Q, M, K X, W, D, F X Y • i • r
Symbol Object type Format Rack Position Channel no. Rank

Syntax The table below describes the different elements that make up addressing.
Family Element Values Description
Symbol % - -
Object type I - Picture of the physical input of the module,
Q - Picture of the physical output of the module,
This information is exchanged automatically each cycle of the task to
which they are attached.
M - Internal variable
This reading or writing information is exchanged at the request of the
application.
K - Internal constant
This configuration information is available as read only.
Format (size) X - Boolean
For Boolean objects this element can be omitted.
W 16 bits Single length.
D 32 bits Double length.
F 32 bits Floating. The floating format used is the IEEE Std 754-1985 standard
(equivalent to IEC 559).
Rack address x 0 or 1 TSX 5710/102/103/153, PMX 57102, PCX 571012).
0-7 Other processors.
(1) : the maximum number of slots means that 2 racks must be used for the same address.

TLX DS 57 PL7 xx 31
Objects associated with specific applications

Family Element Values Description

Module position y 00 - 14 Position number in the rack.
(1) When the rack number (x) is not 0, the position (y) is coded with 2 digits:
00 - 14; on the other hand, if the rack number (x) is 0, you remove the
zeros which are not significant (elimination from the left) from "y" ("x"
does not appear and "y" is 1 digit for values less than 9).
Channel no. i 0 - 127 or MOD : channel reserved for managing the module and parameters
MOD common to all the channels.
Row r 0 - 127 or Position of the bit in the word.
ERR ERR: indicates a module or channel fault.
(1) : the maximum number of slots means that 2 racks must be used for the same address.

Examples The table below shows some examples of addressing objects.

Object Description Illustration
%MW2.0.3 Status word of row 3 of track 0 of the
discrete input module on position 2 of rack
0. 0 2 3 4
L
P T o
%MW103.0.3 Status word of row 3 of track 0 of the S S o
Y X p
discrete input module on position 3 of rack 0 s
2 5 o
1. 6 7 o
0 2 C
%I102.MOD.ERR Information on analogue input module 0 0 o
3 m
fault on position 2 of rack 1. m

%I204.3.ERR Information on a fault on channel 3 of the

analogue output module on position 4 of
0 1 2 3 4
rack 2.
P D
S A S
Y E Y
1 Y
2 0
6 8 8
0 0 R
0 0 5

0 1 2 3 4
P A
S S
Y Y
2 2
6 8
0 0
0 0

32 TLX DS 57 PL7 xx
 Objects associated with specific applications

Addressing of language objects for modules remoted on the FIPIO bus

Presentation Addressing for the main bit and word objects for modules remoted on the FIPIO bus
is geographical. This means that it depends on:
l the connection point,
l the module type (base or extension),
l the channel number.

Illustration Addressing is defined as follows:

% I, Q, M, K X, W, D, F \ p.2.c \ m • i • r
Symbol Object type Format Module/channel Module Channel Rank
address and number number
connection point

Syntax The table below shows the different elements which constitute addressing.
Family Element Values Meaning
Symbol % - -
Object type I - Image of the module's physical input,
Q - Image of the module's physical output,
This information is exchanged automatically on each cycle of the task to
which it is connected.
M - Internal variable
This read or write information is exchanged at the request of the
application.
K - Internal constant
This configuration information is only accessible in read-only.
Format (size) X - Boolean
For boolean-type objects, the X may be omitted.
W 16 bits Single length.
D 32 bits Double length
F 32 bits Floating. The floating format used is that of IEEE standard 754-1985
(equivalent IEC 559).
Module/channel p 0 or 1 Number of the processor's position in the rack.
address and 2 - Channel number of the processor's built-in FIPIO link.
connection point
c 1 to 127 Number of the connection point.
Module position m 0 or 1 0 : base module, 1: extension module.
Channel no. i 0 to 127 MOD: channel reserved for management of the module and the
or MOD parameters shared by all channels.

TLX DS 57 PL7 xx 33
Objects associated with specific applications

Family Element Values Meaning

Position r 0 to 255 ERR: indicates a module or channel fault.
or ERR

Examples The table below gives some examples of object addressing.

Object Meaning
%MW\0.2.1\0.5.2 Position 2 status word for the image bit of input 5 of the remote input
base module located at connection point 1 of the FIPIO bus.
%I\0.2.1\0.7 image bit of input 7 of the remote input base module located at
connection point 1 of the FIPIO bus.
%Q\0.2.1\1.2 image bit of output 2 of the remote output extension module located
at connection point 1 of the FIPIO bus.
%I\0.2.2\0.MOD.ERR Fault information for the Momentum module located at connection
point 2 of the FIPIO bus.
%Q\1.2.3\0.0.ERR Fault information for channel 0 of module CCX17 located at
connection point 3 of the FIPIO bus.

0 FIPIO manager TSX 57253

1 TBX LEP 030 0 TBX DES 1622 1 TBX DSS 1622

2 170 FNT 110 01 0 170 AAI 030 00

3 TSX FPP 010 0 T CCX 17 20 F

34 TLX DS 57 PL7 xx
 Objects associated with specific applications

Addressing of language objects associated with AS-i bus

Presentation Addressing for the main bit and word objects associated with the AS-i bus is
geographical. This means that it depends on:
l the number (address) of the rack where the interface card is positioned,
l the physical position of the interface card in the rack,
l the number (address) of the slave device on the AS-i bus.

Illustration Addressing is defined as follows:

% I ou Q \ xy.0 \ n • i
Symbol Object type Rack/module/channel Slave Bit rank
addrss for TSX SAY 100 number

Syntax The table below describes the different elements which constitute addressing.
Family Element Values Description
Symbol % - -
Object type I - Image of the module's physical input,
Q - Image of the module's physical output,
This data is exchanged automatically on every cycle of the task to which
it is connected.
Rack address x 0 or 1 TSX 5710/102/103/153, PMX 57102, PCX 571012).
0 to 7 Other processors
Module position y 00 to 14 Rack position number.
(1) When the rack number (x) is other than 0, the position (y) has a 2 digit
code: 00 to 14; however, if the rack number (x) = 0, the non-meaningful
zeros are deleted (from the left) from "y" ("x" does not appear and "y"
takes 1 digit for values of less than 9).
Channel no. 0 - The interface card TSX SAY 100 only has one channel.
Slave no. n 0 to 31 Physical address of slave.
Position i 0 to 3 Position of output or input image bit.
(1) : The maximum number of slots requires an extension rack to be used.

TLX DS 57 PL7 xx 35
Objects associated with specific applications

Example The table below gives some examples of object addressing.

Object Description
%I3.0\2.2 Input 2 of slave 2, the module TSX SAY 100 being positioned at slot 3 of
rack 0.
%Q3.0\4.3 Output 3 of slave 4, the module TSX SAY 100 being positioned at slot 3
of rack 0.

0 1 2 3 4
P T S
S S A
Y X Y
0
2 5 o 1
6 7 o 0
0 1 C 0
0 0 o
3 m
m

0
1
2 P ABE-8R44SB11
3
4 P XVA-S102

36 TLX DS 57 PL7 xx
 Objects associated with specific applications

2.2 Implicit exchanges

Implicit exchanges

Presentation A built-in specific application interface where the addition of a module automatically
enhances the application of language objects making it possible to program this
interface or module.
These objects correspond to the images of the I/Os of the module or built-in specific
application module.
The %I bits and the %IW words, images of the module's input values are updated
automatically in the PLC processor at the start of the task, whether the task is in
RUN or STOP mode.
The %Q bits and %QW words, images of the module's output values are updated
automatically in the module by the processor at the end of the task, with the task in
RUN mode.

Note: When the task in STOP mode, depending on the configuration chosen:
l the outputs are in the fallback position (fallback mode),
l the outputs are maintained at their last value (maintain mode).

Illustration The graph illustrates the operational cycle relating to a PLC task (cyclical execution).

Internal processing

Acquisition of input

RUN STOP

Program processing

Updating of output

TLX DS 57 PL7 xx 37
Objects associated with specific applications

Examples The table below shows several examples of implicit exchanges relating to a given
application.
Object Specific Description
application
%I103.1 Discrete Gives the status of channel 1 of the module located in position 3 of rack 1.
%IW4.2 Analog Gives the analog value of channel 2 of the module located in position 4 of rack
0.
%IW203.2:X4 Counting Gives the status of the capture input of the module located in position 3 of rack
2.
%Q306.5 Discrete Gives the status of channel 5 of the module located in position 6 of rack 3.
%I6.5.ERR - Indicates, when the bit is set to 1, that channel 5 of the module located in
position 6 of rack 0 is faulty.
%I107.MOD.ERR - Indicates, when the bit is set to 1, that the module located in position 7 of rack
1 is faulty.

38 TLX DS 57 PL7 xx
 Objects associated with specific applications

2.3 Explicit exchanges

Presentation

Subject of this This section presents the principle of explicit exchanges as well as the different
section instructions which allow them to be carried out.

What's in this This Section contains the following Maps:

Section?
Topic Page
Explicit exchanges: General 40
READ_STS: Reading status words 42
WRITE_CMD: Writing command words 44
READ_PARAM: Reading adjustment parameters 45
WRITE_PARAM: Writing adjustment parameters 46
SAVE_PARAM: Saving adjustment parameters 47
RESTORE_PARAM: Restoring adjustment parameters 49
Exchange and report management 50

TLX DS 57 PL7 xx 39
Objects associated with specific applications

Explicit exchanges: General

Introduction Explicit exchanges are exchanges performed at the request of the user program
using the following instructions:
l READ_STS (reading status words),
l WRITE_CMD (writing command words)
l WRITE_PARAM (writing adjustment parameters),
l READ_PARAM (reading adjustment parameters),
l SAVE_PARAM (saving adjustment parameters),
l RESTORE_PARAM (restoring adjustment parameters),
These exchanges apply to a set of %MW objects of the same type (status,
commands or parameters) on the same channel.

Note: These objects are not necessary for the programming of an application-
specific function, but they provide additional information (e.g.: terminal block fault,
module absent etc.) and additional commands for advanced programming of
application-specific functions (for more information on Explicit exchange objects
relating to a specific application, refer to the corresponding section).

General principle The diagram below shows the different types of explicit exchange possible between
of use for explicit the PLC processor and the module (or the built-in interface).
instructions PLC processor E/S Module or interface
built-in task
%MWxy.i.r objects
or
%MWxy.MOD.r (1)

Status words READ_STS Status words

WRITE_CMD
Command words Command words

WRITE_PARAM
Adjustment parameters READ_PARAM
current
SAVE_PARAM
Adjustment parameters
current

Adjustment parameters
RESTORE_PARAM
initial

Only with the READ_RTS and WRITE_CMD instructions.

40 TLX DS 57 PL7 xx
 Objects associated with specific applications

Exchange During an explicit exchange, it may prove advantageous to check on its progress, in
management order, for example, to ensure that the data read is only acknowledged once the
exchange has been completed.
To do this, two types of information are available:
l detection of an exchange in progress,
l the end of exchange report.
The summary below explains the principle for management of an exchange
Execution of an Detection of an Report
explicit exchange exchange in of the end of the
progress exchange

Logical channel The channel %CHxy.i is a general syntax used to update, via the explicit
%CHxy.i instructions, the set of objects of the same type associated with this channel or a
group of channels.

Example: READ_STS%CH102.3

Note: In the case of a channel group, the address used must be that of the first
channel of the group of channels managed by the module.

Limit concerning The number of explicit exchange functions activated simultaneously is limited to 24
the FIPIO bus on the FIPIO bus.
Several cycles of the master task may be required to send an exchange request to
the FIPIO bus, and it is also necessary that the exchange management parameter
words are managed for all explicit variable exchanges (see ).

TLX DS 57 PL7 xx 41
Objects associated with specific applications

READ_STS: Reading status words

Introduction Status words contain information about the functioning state of the module or the
channel.
The READ_STS instruction allows reading in the module (or in the built-in interface)
of these kind of words. This reading updates the %MW status words .
These words can be used to carry out diagnostics by program.

Note: The status words are specific to each task. However, 2 words are used by
all of the modules in the TSX Premium range:
l %MWxy.MOD.2 (module level fault),
l %MWxy.i.2 (channel i level fault).

Illustration Writing instruction

E/S Module or interface
Processor PLC
built-in task
Objects %MWxy.ir
or
%MWxy.MOD.2

Status words READ_STS Status words

Syntax The READ_STS instruction is defined in the following way :

READ_STS%CHxy.i

The table below describes the different elements that are part of the instruction.
Element Description
READ_STS Name of the instruction
%CH Channel-type object
x Rack address.
y Module position.
i Channel or MOD number.

42 TLX DS 57 PL7 xx
 Objects associated with specific applications

Examples The example below presents some examples of explicit exchanges using the
READ_STS instruction.
Object Description
READ_STS%CH302.1 Reading the status words of channel 1, which is on the module
situated in position 2 in rack number 3.
READ_STS%CH401.MOD Reading the status words of the module situated in position 1 in
rack 4.

TLX DS 57 PL7 xx 43
Objects associated with specific applications

WRITE_CMD: Writing command words

Introduction The command words act on the module or the channel (e.g.: reactivation of discrete
outputs).
The WRITE_CMD instruction enables the %MW command words to be written
to the module (or the built-in interface).

Note: The command words are specific to each application.

Illustration Write instruction

E/S Module or interface
Processor PLC
built-in task

Objects %MWxy.ir
or
%MWxy.MOD.2
WRITE_CMD
Command words Command words

Syntax The WRITE_CMD instruction is defined as follows:

WRITE_CMD%CHxy.i

The table below describes the different elements which constitute the instruction.
Element Description
WRITE_CMD Name of instruction.
%CH Channel-type object.
x Rack address.
y Module position.
i Channel number.

Examples The table below gives an example of an explicit exchange using the WRITE_CMD
instruction.
Object Description
WRITE_CMD%CH3.0 Writing the command information of channel 0 of the module
located in position 3 of rack 0.

44 TLX DS 57 PL7 xx
 Objects associated with specific applications

READ_PARAM: Reading adjustment parameters

Introduction The READ_PARAM instruction enables the adjustment parameters of the module
(or built-in interface) to be read.
Reading updates the status words associated with the adjustment parameters
%MWxy.i.r .

Illustration Read instruction

E/S Module or interface
Processor PLC
built-in task
%MWxy.i.r objects

Current adjustment READ_PARAM Current adjustment

parameters parameters

Syntax The READ_PARAM instruction is defined as follows:

READ_PARAM%CHxy.i

The table below describes the different elements which constitute the instruction.
Element Description
READ_PARAM Name of instruction.
%CH Channel-type object.
x Rack address.
y Module position.
i Channel number.

Examples The table below gives an example of an explicit exchange using the READ_PARAM
instruction.
Object Description
READ_PARAM%CH3.1 Reading the adjustment parameters of channel 1 of the module
located in position 3 of rack 0.

TLX DS 57 PL7 xx 45
Objects associated with specific applications

WRITE_PARAM: Writing adjustment parameters

Introduction The WRITE_PARAM instruction enables the adjustment parameters to be written to

the module (or the built-in interface).
This instruction enables the adjustment values defined in the configuration
contained in the %MWxy.i.r words to be modified by the program.

Illustration Write instruction

E/S Module or interface
Processor PLC
built-in task

%MWxy.i.r objects

WRITE_PARAM
Adjustment parameters Adjustment parameters
current current

Syntax The WRITE_PARAM instruction is defined as follows:

WRITE_PARAM%CHxy.i

The table below describes the different elements which constitute the instruction.
Element Description
WRITE_PARAM Name of instruction.
%CH Channel-type object.
x Rack address.
y Module position.
i Channel number.

Examples The table below gives an example of an explicit exchange using the
WRITE_PARAM instruction.
Object Description
WRITE_PARAM%CH302.1 Writing the adjust parameters of channel 1 of the module
located in position 3 of rack 3.

46 TLX DS 57 PL7 xx
 Objects associated with specific applications

SAVE_PARAM: Saving adjustment parameters

Introduction When modifying the module’s (or built-in interfaces’) adjustment parameters, the
SAVE_PARAM instruction allows you to save these new parameters and substitute
them for the initial parameters.
These parameters replace the initial defined values with the help of the configuration
editor (or of the last save ).
The SAVE_PARAM instruction is the equivalent to the order Services → Save
parameters

Note: During a cold start, the current parameters (not saved) are replaced by the
initial parameters.

Illustration Writing instruction

Processor PLC E/S Module or interface
built-in task
%MWxy.i.r objects

Adjustment parameters SAVE_PARAM Adjustment parameters

current current

Adjustment parameters
initial

Syntax The SAVE_PARAM instruction is defined in the following way:

SAVE_PARAM%CHxy.i

The table below describes the different elements that are part of the instruction.
Element Description
SAVE_PARAM Name of the instruction.
%CH Channel-type object.
x Rack address.
y Module position.
i Channel number.

TLX DS 57 PL7 xx 47
Objects associated with specific applications

Examples The table below presents an example of explicit exchange using the instruction
SAVE_PARAM.
Object Description
SAVE_PARAM%CH5.2 Reading then saving the adjustment parameters of channel 2,
which is part of the module situated in position 5 in rack number
0.

48 TLX DS 57 PL7 xx
 Objects associated with specific applications

RESTORE_PARAM: Restoring adjustment parameters

Introduction The RESTORE_PARAM instruction allows you to restore the initial adjustment
parameters (written during configuration or during the last save).
The RESTORE_PARAM instruction is the equivalent to the order Services → Save
parameters

Illustration Writing instruction

Processor PLC E/S Module or interface
built-in task
%MWxy.i.r objects

Adjustment parameters RESTORE_PARAM Adjustment parameters

current current

Adjustment parameters
initial

Syntax The RESTORE_PARAM instruction is defined in the following way:

RESTORE_PARAM%CHxy.i

The table below describes the different elements that are part of the instruction.
Element Description
RESTORE_PARAM Name of the instruction
%CH Channel-type object.
x Rack address.
y Module position.
i Channel number.

Examples The table below presents an example of explicit exchange using the instruction
RESTORE_PARAM.
Object Description
RESTORE_PARAM%CH1.0 Writing the adjustment parameters of channel 0, which is part
of the module situated in position 1 in rack 0.

TLX DS 57 PL7 xx 49
Objects associated with specific applications

Exchange and report management

Introduction When data is exchanged between the PLC memory and the module, several task
cycles may be required for the exchange to be acknowledged by the interface card.
2 words are used to manage the exchanges:
l %MWxy.i: Exchange in progress,
l %MWxy.i.1: Report

Note: These words are described in detail in each part on specific applications.

Illustration The illustration below shows the various bits which are significant for exchange
management.

Reconfiguration (X15)
Adjust (X2)
Command (X1)
State (X0)

%MWxy.i.0
%MWxy.i.1

Status words READ_STS

Command words WRITE_CMD

WRITE_PARAM
Adjustment parameters READ_PARAM
SAVE_PARAM
RESTORE_PARAM

Description of Each of the bits of the words %MWxy.i and %MWxy.i.1 is associated with a type of
significant bits parameter:
l position 0 bits are associated with status parameters:
l the bit %MWxy.i.0:X0 indicates whether a status word read request is in
progress,
l position 1 bits are associated with command parameters:
l the bit %MWxy.i.0:X1 indicates whether the control parameters have been
sent to channel i of the module,
l the bit %MWxy.i.1:X1 specifies whether the control parameters have been
accepted by channel i of the module,

50 TLX DS 57 PL7 xx
 Objects associated with specific applications

l position 2 bits are associated with adjustment parameters:

l the bit %MWxy.i.0:X2 indicates whether the adjustment parameters have been
exchanged with channel i of the module (by WRITE_PARAM, READ_PARAM,
SAVE_PARAM, RESTORE_PARAM),
l the bit %MWxy.i.1:X2 specifies whether the adjustment parameters have been
accepted by the module. If the exchange has been made successfully the bit
is set to 0,
l the position 15 bits indicate that channel i of the module has been reconfigured
from the terminal (modification of the configuration parameters + cold start of the
channel).

Note: The exchange and report words also exist at module level (%MWxy.MOD
and %MWxy.MOD.1).

Example Phase 1: Transmission of data using the WRITE_PARAM instruction

PLC memory E/S module memory or built-in
application specific function
1
0
Status words Status words
Command words Command words
Current adjustment parameters Current adjustment parameters

When the instruction is scanned by the PLC processor, the Exchange in progress
bit is set to 1 in %MWxy.

Phase 2: Analysis of data by the I/O module and report

PLC memory E/S module memory or built-in
application specific function
0
1
Status words Status words
Command words Command words
Current adjustment parameters Current adjustment parameters

When data is exchanged between the PLC memory and the module,
acknowledgment by the interface card is managed by the %MWxy.i.1:X2 bit: Report
(0 = exchange successful, 1=exchange unsuccessful).

Note: There are no adjustment parameters at module level.

TLX DS 57 PL7 xx 51
Objects associated with specific applications

2.4 Presymbolization

Presentation

Purpose of this This section presents the presymbolization function for the objects of a specific
section application.

What's in this This Section contains the following Maps:

Section?
Topic Page
Presymbolized objects 53
Automatic symbolization of objects associated with a channel 54

52 TLX DS 57 PL7 xx
 Objects associated with specific applications

Presymbolized objects

Role Certain application specific functions (example: counting, axes request, …) support
an automatic symbolization of the objects which are linked to them.

If you give the generic symbol of the module’s %CHxy.i channel, all of the symbols
of the objects linked to this channel can then be automatically generated on request.

Syntax These objects are symbolized with the following syntax:

PREFIX_USER_SUFFIX_MANUFACTURER

The elements have the following meaning and characteristics:

Element Maximum Description
number of
characters
PREFIX_USER 12 generic symbol given to the channel by the user
SUFFIX_MANUFACT 20 part of the symbol which corresponds to the bit
URER object or word of the channel given by the
system

Note: As well as the symbol, a manufacturer’s comment is automatically

generated, this comment recalls succinctly the object’s role.

Example This example shows a counting module situated in slot 3 of the automatic tray.

If the generic symbol (prefix-user) given to channel 0 is Pieces_count, the

following symbols are automatically generated.
Address Type Symbol Comment
%CH3.0 CH
%ID3.0 DWORD Pieces_count_cur-meas Counter current value
%ID3.0.4 DWORD Pieces_count_capt Counter captured value
%I3.0 EBOOL Pieces_count_enab_activ Counter enable active
%I3.0.1 EBOOL Pieces_count_pres_done Preset done

TLX DS 57 PL7 xx 53
Objects associated with specific applications

Automatic symbolization of objects associated with a channel

Introduction The manufacturer's presymbolization (manufacturer's suffix) assigned to language

objects is specific to each application. The detailed list of these suffixes is contained
in the documentation relating to the specific application concerned.

Conditions Automatic symbolization implies that:

required l the module has been declared in the PL7 configuration in advance.
l the application-specific module accepts this function. The specific applications
concerned are:
l analog,
l counting,
l axes control,
l step by step control,
l weighing,
l process control,
l communication (requires an in-rack interface card).

Procedure The table below shows the procedure for the automatic symbolization of objects
associated with a channel.
Step Action
1 Access the variable editor.
2 Access to I/O type variables.
Note: The channels whose objects can be symbolized have a letter P on the
button to the left of the%CH address.
3 Double-click on the P button for the channel to be symbolized.
4 Enter the user prefix.
Note: If a symbol is already defined for the channel, the prefix proposed is the
retrieved symbol truncated to 12 characters.
5 Confirm with the Presymbolize button.

De-activating Canceling automatic symbolization, for a given logical channel, makes it possible to
automatic delete all or part of an object's symbols.
symbolization. Two options are proposed:
If the option chosen is … then …
Delete all presymbols No prefix is chosen: all symbols are deleted (including those which have
been modified directly using the editor).
Delete prefixed presymbols Only objects with a prefix identical to that entered are deleted.

54 TLX DS 57 PL7 xx
 Application-specific instructions

3
Presentation

Subject of this This chapter presents the application-specific instructions.

chapter

What's in this This Chapter contains the following Maps:

Chapter?
Topic Page
Application-specific instructions 56
Accessing a specific function, method or procedure type instruction 57

TLX DS 57 PL7 xx 55
Application-specific instructions

Application-specific instructions

Introduction Application-specific instructions (of function, method or procedure type) are

programming instructions specific to an application-specific function which
supplement the basic and advanced instructions.

They are defined in the documentation of each specific application.

The parameters are always made up of the following PL7 language objects: words,
word tables, immediate values.

Note: Function-type instructions require additional application memory space (only

when they are actually being used in the program). This memory space
requirement is to be taken into consideration for each function, whatever the
number of uses and must respect the maximum memory size of the PLC used.

Example of a The SMOVE (method type) function dedicated to movement control modules (TSX
specific CAY and TSX CFY) enables movements to be made.
instruction SMOVE %CH103.2 (01,90,01,10000000,200,0)
Each parameter has a particular meaning:
l 10000000 is the coordinate to be attained in micrometers,
l 200 is the movement speed of the moving part in mm/minute,
l ...

56 TLX DS 57 PL7 xx
 Application-specific instructions

Accessing a specific function, method or procedure type instruction

Presentation Application-specific function entry can be accessed by:

l directly entering the instruction and its parameters in an operate block,
l by the entry help function accessible through the program editors (LD, IL, ST).

Calling up a
function
Step Action
1 Access the required editor.
2 Depending on the editor used, choose one of the following methods to open the
function library.
l Press Shift + F8 (LD, IL,ST editors).
l Click on the (LD editor) icon.
l Select the command Utilities → Enter call for a (IL, ST editors) function.
Note: The function library appears.

PL7 : Library functions ?

EF
Function information Parameters Detail...
Family Lib.V. App.V Name Comment
Characters string 2.00 - SMOVE Automatic movement command
Interpolation Command 1.0 -
Movement Command 2.00 -
Communication 3.07 -
Call format
Parameters of the METHOD:
Name Type Kind Comment Family
Channel MAIN Channel %CH103.2
NRUN WORD IN Movement number 01
G9 World IN G9 90

Display the call

SMOVE %CH103.2 ( 01.90.01.10000000.20000.0 )

OK Cancel

3 Select the specific application in the Family field.

4 Select the instruction in the Name field.
5 Many of the instructions have a customized entry help screen.
Access this screen by clicking on the Details button.

TLX DS 57 PL7 xx 57
Application-specific instructions

Step Action
6 Enter each instruction parameter (each instruction is developed in the relevant
application-specific documentation)
l in the customized screen
or
l in the Entry field in the Library Functions screen. To do this, the Parameter
item must be selected in the Function Information field.
7 Click Ok to confirm.

58 TLX DS 57 PL7 xx
 Appendices

4
Presentation

Subject of this This chapter introduces several elementary notions that are useful for the installation
chapter of application-specific functions.
Some of these notions are taken from the PL7 Installation and Start-up Guide.

What's in this This Chapter contains the following Maps:

Chapter?
Topic Page
Reminders concerning the configuration editor 60
The PL7 toolbar 61
The PL7 status bar 62
How to declare a module in a PLC rack 63
How to declare a remote module on the FIPIO bus. 64
Confirming the configuration of a module. 66
Globally reconfiguring an application. 67
Application-specific fault processing (in-rack modules) by program 68
Processing of FIPIO faults 69

TLX DS 57 PL7 xx 59
Appendices

Reminders concerning the configuration editor

Presentation The configuration editor enables the various constitutive elements of the PLC to be
declared and configured in a graphical and intuitive manner:
l rack,
l power supply,
l processor,
l application-specific modules.
In online mode the configuration editor also performs debug, adjustment and
diagnostics functions.

Illustration The following screen provides an example of a hardware configuration.

Configuration
XMW I
TSX 57103 V4.0 ... XTI..

0 1 2 3 4 5 6
P T D D D C S I
S S E E S T C S
Y X Y Y Y Y Y P
0 o 0
2 5 3 1 2 2 Y
6 7 o 8 2 6 C 1 1
0 1 C D D R 6 0
0 0 o 2 2 5 0 0
3 m K 1
m

Accessing the The following table shows the different ways of accessing the configuration editor.
editor
From: Action
the menu bar Select Tools → Configuration.
the application Double-click on Hardware configuration or select it using the arrow
browser keys and confirm with Enter.
Application Browser

Structure View
STATION
Configuration
Hardware configuration
Software configuration
Program
MAST Task
Events
DFB types
Variables
Animation tables

60 TLX DS 57 PL7 xx
 Appendices

The PL7 toolbar

Presentation The software's basic functions can be accessed quickly via the toolbar, using the
mouse.
Access to the different functions is dynamic and varies according to the context.

Illustration The PL7 toolbar is displayed as follows:

RUN
RUN STOP
STOP
? ?
? ?

Elements and This table gives the function of each element in the toolbar:
functions
Element Function Element Function
New application Local mode

Open an application Online mode

Save the application RUN PLC changes to RUN

Print all or part of the application STOP PLC changes to STOP

Undo last modifications Start / Stop the animation

Confirm modifications Organize windows so that they

overlap
Go to Tile windows horizontally

Application browser Tile windows vertically

Cross references
?
?
Help

Function library
?? What's this?

PLC <-> terminal transfer

Note: All these functions can also be accessed via the menu.

TLX DS 57 PL7 xx 61
Appendices

The PL7 status bar

At a Glance The status bar, situated at the bottom of the screen, shows a range of information
associated with operational aspects of the software.

Illustration The PL7 status bar appears thus:

1 2 3 4 5 6 7 8

Ready ONLINE STOP U:SYS GR7 OK MODIF OVR CAPS

Elements and This table describes the different zones that make up the status bar:
functions
Number Zone Function
1 Information supplies information concerning menu commands, toolbar
icons and the different editors when these are selected.
2 Operating mode indicates the current operating mode (offline, online).
3 PLC state indicates the PLC state (Run, Stop, faulty, etc.).
4 Network address gives the network address of the PLC.
5 Grafcet mode indicates whether Grafcet mode is used in the application.
6 Modification in indicates that the current application has not been saved or is
progress different from the back-up.
7 Animation indicates that the PLC is in online mode.
indicator
8 Keyboard indicates the status of the Insert and All Caps keyboard
functions functions.

62 TLX DS 57 PL7 xx
 Appendices

How to declare a module in a PLC rack

Procedure This operation enables the user to make a software declaration of a module in a PLC
rack.
The example below concerns a Discrete module; the same procedure is used
whatever the type of in-rack module.
Step Action
1 Access the application's hardware configuration screen.
2 Double-click on the slot in which the module is to be configured.
Result: the Add module screen appears.
Add module
Family: Module:
Analog Module1.5 TSX DEY 08D2 8I 24VDC SINK BORN OK
Communication1.5 TSX DEY 16A2 16I 24VAC BORN
Counting1.5 TSX DEY 16A3 16I 48VAC BORN
Remote BusX1.0 TSX DEY 16A4 16I 110/120VACBORN Cancel
Movement1.5 TSX DEY 16A5 16I 220/240VAC BORN
Weighing1.5 TSX DEY 16D2 16I 24VDC SINK BORN
Simulation1.0 TSX DEY 16D3 16I 48VDC SINK BORN
Discrete I/O1.5 TSX DEY 16FK 16I FAST 24VDC SINK CONN
TSX DEY 32D2K 32I 24VDC SINK CONN
TSX DEY 32D3K 32I 48VDC SINK CONN
TSX DEY 64D2K 64I 24VDC SINK CONN
TSX DMY 28FK 16I 24VDC.12S 24 VCC

3 Select the specific application (e.g.:Discrete) in the Family field.

4 Select the module reference in the Module field.
5 Click on Ok to confirm the selection.
Result: the module is declared in its slot; the slot is shown in gray and contains
the module reference.
Configuration
XMWI
TSX 57452 V5.0 ... XTI..

0 2 3 4
L F
P T o i D
S S o p E
Y X p
s
i
o Y
0
2 5 o 0
6 7 o 8
0 4 C D
0 5 o 2
2 m
m

TLX DS 57 PL7 xx 63
Appendices

How to declare a remote module on the FIPIO bus.

Procedure This operation enables the user to make a software declaration of a module
connected to the FIPIO bus.
Note: This operation requires a processor with a built-in FIPIO link.
Step Action
1 Access the application's hardware configuration screen.
2 Double-click on the processor's FIPIO zone.
Result: the FIPIO Configuration screen appears
FIPIO Configuration
TSX 57453 V5.0 Bus length: 0 15 km Devices configured: 0
1
Logical address Communicator Base module Extension module

0 Fipio managerTSX 57453

63 Privileged terminal

12

3 Double-click on one of the available connection points.

Result: the Add/Modify device screen appears.
Add/Modify a Device
Connection point
Connection number 1 OK
Comment
Cancel

Families
Module de base

ATV-161.0
ATV-16 1.0 ATV16U09M2/50Hz ATV16 0.37kw240V
ATV 0.37kw 240 V50Hz
50Hz
ATV-581.0 ATV16U09M2/60Hz ATV16 0.5HP 240 V 60Hz
CCX-171.0 ATV16U18M2/50Hz ATV16 0.75kw 240 V 50Hz
CCX17-321.0 ATV16U18M2/60Hz ATV16 1.0HP 240 V 60Hz
MAGELIS1.0 ATV16U18N2/50Hz ATV16 0.75kw 460 V 50Hz
MOMENTUM1.0 ATV16U18N2/60Hz ATV16 1.0HP 460 V 60Hz
PASSERELLE1.0 ATV16U29M2/50Hz ATV16 1.5kw 240 V 50Hz
SIMULATION1.0 ATV16U29M2/60Hz ATV16 2.0HP 240 V 60Hz
STD_P1.0
TBX1.0
Communicator
TSX1.0
TSX FPP 010 PCMCIA Agent Fipio

64 TLX DS 57 PL7 xx
 Appendices

Step Action
4 Enter the number of the connection point corresponding to the address where the
module is to be connected (available addresses run from 1 - 62 and 64 - 127;
addresses 0 and 63 are reserved by the system).
By default, the PL7 software proposes the address for the selected connection
point.
5 Enter a comment if necessary.
6 In the Family field, select the type of device to be connected to the bus. (e.g.: TBX,
Momentum, etc.).
7 Select the base module.
8 Select, according to the type of device:
l the base module and/or extension module,
l the communicator.
Note:
l If the reference for the Momentum base module is not already proposed, select
reference OTHER FRD.
9 Click Ok to confirm.
Result: the module is declared.
FIPIO Configuration
TSX 57453 V5.0 Bus length: 0 15 km Devices configured: 1
1
Logical address Communicator Base module Extension module

0 Fioio manager TSX 57453

1 TBX LEP 030 0 TBX ASS 200 1 TBX AES 400

63 Privileged terminal

TLX DS 57 PL7 xx 65
Appendices

Confirming the configuration of a module.

Introduction When a module is declared, and when the configuration or adjustment parameters
are modified, this module's configuration must be confirmed.

Illustration The table below shows where the confirmation of a module's configuration is
positioned within the various hardware installation phases of an application.
Step Description
1 Declaration of a module:
2 Configuration of module channels.
3 Adjustment
4 Confirmation of the configuration of the module.
5 Declaration and/or parametering of new modules
6 Global confirmation of the application

Procedure The table below shows the procedure for confirming the configuration of a module.
Step Action
1 Select Edit → Confirm or use the icon located in the toolbar.

66 TLX DS 57 PL7 xx
 Appendices

Globally reconfiguring an application.

Introduction An application needs to be globally reconfigured in order for the modifications

confirmed for each module to be taken into account. This is generally carried out in
local mode,

Note: Global reconfiguration of an application in online mode causes the module

to stop.

Illustration The table below shows where the global reconfiguration of an application is
positioned within the various hardware installation phases of an application.
Step Description
1 Declaration of a module:
2 Configuration of module channels
3 Adjustment
4 Confirmation of the configuration of the module
5 Declaration and/or parametering of new modules
6 Global confirmation of the application

Procedure The table below shows the procedure for globally reconfiguring a module.
Step Action
1 Select Edit → Confirm ... or use the icon located in the toolbar.
2 Confirm the reconfiguration:

TLX DS 57 PL7 xx 67
Appendices

Application-specific fault processing (in-rack modules) by program

Presentation Application-specific fault processing can be performed using the debugging and
diagnostics screens.
It may however be advantageous to use a program to perform this processing.

Algorithm The following algorithm is an application example of the detection and management
application-specific (in rack) module faults by a program.
Test the %S10 bit
(general input/output default)

No No default
%S10=0 ? of input/output

Yes

Locate the default on

the FIPIO bus via
%S119

No Locate the default on

%S119 = 0 ? the FIPIO bus via
%S118 (1)
Yes

Locate the rack

at default
%S40 to %S47

Locate the module

at default in the rack
%Ixy.MOD.ERR = 1

Diagnose the default module

READ_STS %CHxy.MOD
%MWxy.MOD.2

Locate the channel

at default via
%Ixy.i.ERR = 1

Diagnose the default channel

READ_STS %CHxy.i
%MWxy.i.2

(1) See Processing of FIPIO faults , p. 69

68 TLX DS 57 PL7 xx
 Appendices

Processing of FIPIO faults

Presentation FIPIO fault processing can be performed using the debug and diagnostics screens.
It may however be advantageous to use a program to perform this processing.

Algorithm The algorithm shown is an example of an application algorithm for fault detection
and management on the FIPIO bus
Test the %S10 bit
(general input/output
default)

No No default
%S10=0 ? of input/output

Yes

Locate the default on

the FIPIO bus via
%S118

No Test the default on

%S118 = 0 ? the X bus via
%S119
Yes

Locate the default Locate the %SW128 to The location of the default
connection %SW143 word which is connection point may be carried
point via different to 0 out in two distinct ways.
%I\p2c\m.MOD.ERR = 1 The recommended method is
location via the system words
Locate the default %SW128 to %SW143.
connection point via the
%SWi:x word bit which is
different to 0

Diagnose the connection point via the

function
READ_STS %CH\p.2.c\0.MOD

Locate the channel

at default via
%I\p2c\m.v.ERR = 1

Diagnose the channel

via the function
READ_STS %CH\p.2.c\m.v.ERR

TLX DS 57 PL7 xx 69
Appendices

70 TLX DS 57 PL7 xx
 Discrete specific application

II
Presentation

Subject of this This part presents the Discrete application-specific function on the TSX/PCX57 PLC
part and describes its installation using PL7 Junior and Pro software.

What's in this This Part contains the following Chapters:

part?
Chapter Chaptername Page
5 General presentation of the discrete application -specific 73
function
6 Configuration of the discrete specific application 77
7 Debugging discrete modules 111
8 Bits and words associated with discrete specific applications 123
9 Installation of the discrete reflex module 139

TLX DS 57 PL7 xx 71
Discrete specific application

72 TLX DS 57 PL7 xx
 General presentation of the
discrete application -specific
function 5
Introduction to the Discrete Application

Introduction The discrete application-specific function applies:

l to rack-mounted discrete I/O modules,
l to discrete I/O modules remoted on the FIPIO bus.

Note: In order to access the latter, the configured processor must have a built-in
FIPIO link.

In order to install the discrete application, its physical context (rack, power supply,
processor, modules or hardware, etc.) must be defined and the necessary software
installation carried out.
This second aspect will be carried out from the different PL7 editors:
l either in local mode,
l or in connected mode; in this case the modification is limited to certain
parameters.

TLX DS 57 PL7 xx 73
General presentation

Implementation The table below shows the different installation phases of the discrete application-
specific function.
Mode Phase Description
Local Declaration of a module Choice:
in-rack module (See How to l of geographical position
declare a module in a PLC l number and slot for an in-rack module,
rack, p. 63) l connection point for a remote module,
or l of module type.
remoted on the FIPIO bus
(See How to declare a
remote module on the FIPIO
bus., p. 64)
Configuration of module Input of the configuration parameters.
channels (See Configuration
of discrete parameters,
p. 98)
Adjustment (See Adjusting Entry of initial adjustment parameters (only on TSX DMY 28 FRK).
the configuration
parameters of a reflex
function, p. 192)
Confirmation of Confirmation of module level.
configuration parameters
(See Confirming the
configuration of a module.,
p. 66)
Global confirmation of the Confirmation of application level.
application (See Globally
reconfiguring an
application., p. 67)
Local or Symbolization Symbolization of variables associated with the application-specific
connected function.
Programming Programming of functions to be performed by the application
using:
l bit and word objects associated with the module,
l specific application instructions.

Connected Transfer Transfer of the application to the PLC.

Debugging Debugging the application with the help of:
l debugging help screens enabling the user to control I/Os,
l diagnostic screens allowing identification of errors.

Local or Documentation Printing the different information relating to the application.

connected

74 TLX DS 57 PL7 xx
 General presentation

Note: The order shown above is given as an indication only; the PL7 software
allows the editors to be used interactively in the order required (however, the data
or program editor cannot be used unless the I/O modules have been configured
first).

TLX DS 57 PL7 xx 75
General presentation

76 TLX DS 57 PL7 xx
 Configuration of the discrete
specific application
6
Presentation

Subject of this This chapter describes the Configuration aspect of the installation of the discrete
chapter specific application.

What's in this This Chapter contains the following Sections:

Chapter?
Section Topic Page
6.1 Configuring a discrete module: General 78
6.2 Discrete input channel parameters 85
6.3 Discrete output channel parameters 90
6.4 Configuration of discrete parameters 98

TLX DS 57 PL7 xx 77
Configuration of the discrete specific application

6.1 Configuring a discrete module: General

Presentation

Purpose of this This section describes the basic operations required for configuring a Discrete
section module.

What's in this This Section contains the following Maps:

Section?
Topic Page
Description of the configuration screen for a discrete module 79
Accessing the configuration screen for an in -rack discrete module. 80
Accessing the configuration screen for a discrete module remoted on the 82
FIPIO bus
Modifying the configuration parameters of a discrete module's: General 83

78 TLX DS 57 PL7 xx
 Configuration of the discrete specific application

Description of the configuration screen for a discrete module

Presentation The module's configuration screen, selected in the rack or on the FIPIO bus,
displays the parameters associated with the Discrete.

Illustration This screen gives access to parameter viewing and modification in local mode, and
debugging in online mode.
1 TSX DMY 28FK [RACK 0 POSITION 2]
Configuration Inputs
Designation : 16I 24VDC, 12O 24
2
Chan. Symbol Supply Monit. Task Filter Function
0 Active MAST 4 ms
1 4 ms
2 4 ms
3 4 ms
4 4 ms
5 4 ms
6 4 ms
3 7 4 ms
8 MAST 4 ms
9 4 ms
10 4 ms
11 4 ms
12 4 ms
13 4 ms
14 4 ms
15 4 ms

Description The table below shows the different elements in the configuration screen, along with
their functions.
Number Element Function
1 Title bar Indicates the reference and physical position of the selected module along with the rack number
for in-rack modules or the FIPIO connection point for remote I/Os.
2 Module Enables the user t select:
zone l the installation phase:
l Configuration,
l Adjustment (only for TSX DMY 28 RFK),
l Installation (diagnostics), only accessible in online mode.
l the type of channels (inputs or outputs), if the designated module has both inputs and
outputs,
l the program part for TBX DMS 16P22 modules.
Displays the designation of the selected module.
Displaying this zone is optional. The option is activated using the command View → Module
zone.
3 Channel Enables the different channels to be parametered. The Symbol column displays the symbol
zone associated with the channel when this has been defined by the user (via the variables editor).

TLX DS 57 PL7 xx 79
Configuration of the discrete specific application

Accessing the configuration screen for an in -rack discrete module.

Procedure This operation enables the user to access the configuration parameters for the
channels of a discrete module.
Step Action
1 Access the module's hardware configuration screen.
2 Double-click on the module to be configured or select the module and execute the
command Service → Open the module.
Result: The configuration screen for the selected module appears.
TSX DMY 28FK [RACK 0 POSITION 2]
Configuration Inputs
Designation : 16I 24VDC, 12O 24 VDC

Chan. Symbol Supply Monit. Task Filter Function

0 Active MAST 4 ms
1 4 ms
2 4 ms
3 4 ms
4 4 ms
5 4 ms
6 4 ms
7 4 ms
8 MAST 4 ms
9 4 ms
10 4 ms
11 4 ms
12 4 ms
13 4 ms
14 4 ms
15 4 ms

80 TLX DS 57 PL7 xx
 Configuration of the discrete specific application

Certain modules have a dialogue box giving access to additional parameters. To

access this dialogue box:
Step Action
1 Perform one of the following:
l right-click on the row in the table corresponding to the channel to be
parametered and then select the Properties command from the pull-down
menu,
l or double-left-click on the row in the table corresponding to the channel to be
parametered,
l or select the Function cell of the channel to be parametered and then confirm
using Enter.
Result: The dialogue box appears, superimposed on the configuration screen.

TSX DMY 28FK [RACK 0 POSITION 2]

Configuration Inputs
Designation : 16I 24VDC, 12O 24

Chan Symbol Supply Task Filter Function

0 Active MAST 4 ms
1 4 ms Properties of channel x
2 4 ms
3 4 ms
4 4 ms
5 4 ms Normal
6 4 ms
7 4 ms Latch state 0
8 MAST 4 ms Latch state 1
9 4 ms
10 4 ms Event procesing
11 4 ms
12 4 ms Rising
13 4 ms
14 4 ms Falling
15 4 ms
EV 1

TLX DS 57 PL7 xx 81
Configuration of the discrete specific application

Accessing the configuration screen for a discrete module remoted on the FIPIO
bus

Procedure This operation enables the user to access the configuration parameters for the
channels of a discrete module remoted on the FIPIO bus.
Step Action
1 Access the module's hardware configuration screen.
2 Double-click on the processor's FIPIO zone.
3 Double-click on the module to be configured or select the module and execute the
command Service → Open the module.
Result: The configuration screen for the selected module appears.

TBX CSP 1622 [FIPIO1 MODULE 0]

Configuration
Designation : TBX7 MONOBLOC 16SO 24Vdc

Chan. Symbol Task Reactivate

0 MAST Automatic
1
2
3
4
5
6
7
8 Automatic
9
10
11
12
13
14
15

82 TLX DS 57 PL7 xx
 Configuration of the discrete specific application

Modifying the configuration parameters of a discrete module's: General

Introduction The configuration editor provides a set of functions which enable the user to input or
modify the parameters of modules such as:
l contextual menus,
l single or multiple selection of channels,
l cutting/pasting of parameters (using the contextual menus).

Accessing the These can be accessed by right-clicking with the mouse, and give quick access to
contextual the main commands.
menus
If the element to be selected is... Then the available functions are...
the cell Copy parameters
Paste parameters
the module zone (except in tables) Undo modifications
Confirm
Animate

Selecting a The table below shows the procedure for selecting a module channel cell or channel.
channel or cell
Step Action
1 Left-click on the required cell or channel number.

Selecting a The table below shows the procedure for selecting a group of consecutive channels
group of of a module.
consecutive
Step Action
channels
1 Select the first channel.
2 Press Shift and click on the last channel.

Selecting a The table below shows the procedure for selecting a group of non-consecutive
group of non- channels of a module.
consecutive
Step Action
channels
1 Select the first channel.
2 Press Ctrl and click on each of the channels in turn.

TLX DS 57 PL7 xx 83
Configuration of the discrete specific application

Selecting a The table below shows the procedure for selecting a group of consecutive cells of a
group of module.
consecutive
Step Action
cells
1 Select the first cell.
2 Move the mouse up or down whilst holding down the mouse button, then
release the button when the last cell has been reached.

84 TLX DS 57 PL7 xx
 Configuration of the discrete specific application

6.2 Discrete input channel parameters

Presentation

Subject of this This section presents the different input channel parameters by type of Discrete
section module.

What's in this This Section contains the following Maps:

Section?
Topic Page
In-rack discrete input parameters 86
Parameters of TBX discrete inputs remoted on the FIPIO bus 87
Parameters of Momentum discrete inputs remoted on the FIPIO bus 88
Parameters of IP67 discrete inputs remoted on the FIPIO bus 89

TLX DS 57 PL7 xx 85
Configuration of the discrete specific application

In-rack discrete input parameters

Presentation Discrete input modules contain parameters per channel, or per group of 8 or 16
consecutive channels.

Parameters The table below shows the parameters available for each in-rack discrete input
module.
Module Number of Associated task Function Filtering Supply fault
Reference inputs (8 channel group) (per channel). (per channel). monit.
(16 channel
group)
TSX DEY 08D2 8 Mast / Fast - - Active / Inactive
TSX DEY 16A2 16 Mast / Fast / None - - Active / Inactive
TSX DEY 16A3 16 Mast / Fast / None - - Active / Inactive
TSX DEY 16A4 16 Mast / Fast / None - - Active / Inactive
TSX DEY 16A5 16 Mast / Fast / None - - Active / Inactive
TSX DEY 16D2 16 Mast / Fast / None - - Active / Inactive
TSX DEY 16D3 16 Mast / Fast / None - - Active / Inactive
TSX DEY 32D2K 32 Mast / Fast / None - - Active / Inactive
TSX DEY 32D3K 32 Mast / Fast / None - - Active / Inactive
TSX DEY 64D2K 64 Mast / Fast / None - - Active / Inactive
TSX DMY 16FK 16 Mast / Fast / None Normal or (1) 4 ms or (2) Active / Inactive
TSX DMY 28FK 16 (input part) Mast / Fast / None Normal or (1) 4 ms or (2) Active / Inactive
TSX PAY 262 8 (input part) Mast / Fast / None - - -
TSX PAY 262 8 (input part)
TSX DMY 28RFK 16 (input part) Mast / Fast / None - 4 ms or (2) Active / Inactive
Key:
(1) Memorization of status 0 or 1, event processing on rising edge (RE), on falling edge (FE) or both
together.
(2) 0.1 to 7.5 ms

Note:
l Parameters in bold correspond to the parameters configured by default.
l The modules' first group of channels (addresses from 0 to 7) is always assigned
to a Mast or Fast task. The following groups also have the choice of: None (no
task associated with the group of unused channels).

86 TLX DS 57 PL7 xx
 Configuration of the discrete specific application

Parameters of TBX discrete inputs remoted on the FIPIO bus

Presentation The Discrete TBX input modules on the FIPIO bus have parameters per channel and
for all channels.

Parameters The table below shows the parameters available for each TBX discrete input
module.
Module Number of Associated task Filtering Latching (per Wiring Check
Reference inputs (for the module) (per channel) channel) (per channel)
TBX CEP 1622 16 Mast / Fast - - -
TBX DES 1622 16 Mast / Fast - - -
TBX DES 1633 16 Mast / Fast - - -
TBX EEP 1622 16 Mast / Fast - - -
TBX DMS 1025 8 (input part) Mast / Fast - - -
TBX DMS 1625 8 (input part) Mast / Fast - - -
TBX DES 16S04 16 Mast / Fast - - -
TBX DMS 16S44 (1) Mast / Fast - - Active / Inactive
TBX DMS 16P22 8 (input part) Mast / Fast - - Active / Inactive
TBX DES 16C22 16 Mast / Fast - - Active / Inactive
TBX EEP 08C22 16 Mast / Fast - - Active / Inactive
TBX DMS 16C22 8 Mast / Fast - - Active / Inactive
TBX DMS 16C222 8 Mast / Fast - - Active / Inactive
TBX DES 16F22 16 Mast / Fast Normal / Fast Active / Inactive -

Key:
(1) 8 input channels + 8 programmable input or output channels.

Note: Parameters in bold correspond to the parameters configured by default.

TLX DS 57 PL7 xx 87
Configuration of the discrete specific application

Parameters of Momentum discrete inputs remoted on the FIPIO bus

Presentation The Discrete Momentum input modules on the FIPIO bus have parameters for all
channels.

Parameters The table below shows the parameters available for each Momentum discrete input
module.
Module Reference Number of inputs Associated task (for the
module)
170 ADI 340 00 16 Mast / Fast
170 ADI 350 00 32 Mast / Fast
170 ADM 350 10 16 (input part) Mast / Fast
170 ADM 390 30 10 (input part) Mast / Fast
170 ADM 370 10 10 (input part) Mast / Fast

Note: Parameters in bold correspond to the parameters configured by default.

88 TLX DS 57 PL7 xx
 Configuration of the discrete specific application

Parameters of IP67 discrete inputs remoted on the FIPIO bus

Presentation The Discrete IP67 input modules on the FIPIO bus have parameters for all channels.

Parameters The table below shows the parameters available for each IP67 discrete input
module.
Module Reference Number of inputs Associated task (for the
module)
TSX EEF 08D2 8 Mast / Fast
TSX EEF 16D2 16 Mast / Fast
TSX EMF 16DT2 8 (input part) Mast / Fast

Note: Parameters in bold correspond to the parameters configured by default.

TLX DS 57 PL7 xx 89
Configuration of the discrete specific application

6.3 Discrete output channel parameters

Presentation

Subject of this This section presents the different output channel parameters by type of Discrete
section module.

What's in this This Section contains the following Maps:

Section?
Topic Page
Discrete output parameters for in-rack 8-channel modules. 91
Discrete output parameters for in-rack modules with over 8 channels 92
Parameters of 8, 10 or 12 channel TBX discrete outputs remoted on the FIPIO 94
bus
Parameters of 16 channel TBX discrete outputs remoted on the FIPIO bus 95
Momentum Parameters of Momentum discrete outputs remoted on the FIPIO 96
bus
Parameters of IP67 discrete outputs remoted on the FIPIO bus 97

90 TLX DS 57 PL7 xx
 Configuration of the discrete specific application

Discrete output parameters for in-rack 8-channel modules.

Presentation 8-channel discrete output modules have parameters per channel or for all channels.

Parameters The table below shows the parameters available for each in-rack 8-channel discrete
output module.
Group of 8 channels Channel by
channel.
Module Reference Associated Reactivation Fallback Supply fault Fallback
task mode monit. value
TSX DSY 08R4D Mast / Fast Programmed / Automatic Fallback / - 0/1
Maintain
TSX DSY 08R5A Mast / Fast Programmed / Automatic Fallback / - 0/1
Maintain
TSX DSY 08S5 Mast / Fast Programmed / Automatic Fallback / - 0/1
Maintain
TSX DSY 08T2 Mast / Fast Programmed / Automatic Fallback / Active / Inactive 0/1
Maintain
TSX DSY 08T22 Mast / Fast Programmed / Automatic Fallback / Active / Inactive 0/1
Maintain
TSX DSY 08T31 Mast / Fast Programmed / Automatic Fallback / Active / Inactive 0/1
Maintain
TSX DSY 08R5 Mast / Fast Programmed / Automatic Fallback / - 0/1
Maintain

Note: Parameters in bold correspond to the parameters configured by default.

TLX DS 57 PL7 xx 91
Configuration of the discrete specific application

Discrete output parameters for in-rack modules with over 8 channels

Presentation Discrete output modules with more than 8 channels have parameters per channel
or for all channels.

Parameters The table below shows the parameters available for each in-rack discrete output
module with more than 8 channels.
Group of 8 channels Channel by
channel.
Module Number of Associated Reactivation Fallback Supply fault Fallback
Reference outputs task mode monit. value
TSX DSY 16S5 16 Mast / Fast / Programmed / Fallback / - 0/1
None Automatic Maintain
TSX DSY 16T2 16 Mast / Fast / Programmed / Fallback /
None Automatic Maintain
TSX DSY 16T3 16 Mast / Fast / Programmed / Fallback / Active / 0/1
None Automatic Maintain Inactive
TSX DSY 32T2K 32 Mast / Fast / Programmed / Fallback / Active / 0/1
None Automatic Maintain Inactive
TSX DSY 64T2K 64 Mast / Fast / Programmed / Fallback / Active / 0/1
None Automatic Maintain Inactive
TSX DSY 16R5 16 Mast / Fast / - Fallback / - 0/1
None Maintain
TSX DSY 16S4 16 Mast / Fast / - Fallback / - 0/1
None Maintain
TSX DMY 28 FK 12 (output part) Mast / Fast / Programmed / Fallback / Active / 0/1
None Automatic (1) Maintain Inactive
TSX DMY 28RFK 12 (output part) Mast / Fast / Programmed / Fallback / Active / 0/1/
None Automatic (1) Maintain Inactive Continuous
(2)
TSX PAY 262 2 (output part) Mast / Fast / - - - -
TSX PAY 262 4 (output part) None
Key:
(1) Reactivation is chosen globally for the 12 output channels.
(2) Only for TSX DMY 28 RFK.

92 TLX DS 57 PL7 xx
 Configuration of the discrete specific application

Note:
l Parameters in bold correspond to the parameters configured by default.
l The modules' first group of channels (addresses from 0 to 7) is always assigned
to a Mast or Fast task. For subsequent groups the following additional option is
available: None (no task associated with the group of unused channels).

TLX DS 57 PL7 xx 93
Configuration of the discrete specific application

Parameters of 8, 10 or 12 channel TBX discrete outputs remoted on the FIPIO

bus

Presentation The 8, 10 or 12 channel discrete TBX output modules have parameters per channel,
per group of 8 channels or for all channels.

Parameters The table below shows the parameters available for each 8, 10 or 12 channel TBX
discrete output module remoted on the FIPIO bus.
Module Group of 8 channels Channel by channel
Module Number of Associated Reactivation Fallback Fallback Wiring
Reference outputs task mode value Check
TBX ESP 08C22 8 Mast / Fast Programmed Fallback / 0/1 Yes / No
/ Automatic Maintain
TBX DSS 1235 12 Mast / Fast - Fallback / 0/1 -
Maintain
TBX DMS 1025 2 (output part) Mast / Fast Programmed Fallback / 0/1 -
/ Automatic Maintain

Note: Parameters in bold correspond to the parameters configured by default.

94 TLX DS 57 PL7 xx
 Configuration of the discrete specific application

Parameters of 16 channel TBX discrete outputs remoted on the FIPIO bus

Presentation The 16 channel discrete TBX output modules have parameters per channel, per
group of 8 channels or for all channels.

Parameters The table below shows the parameters available for each 16 channel TBX discrete
output module remoted on the FIPIO bus.
Module Group of 8 channels Channel by channel
Module Number of Associated Reactivation Fallback Fallback Wiring
Reference outputs task mode value Check
TBX CSP 1625 16 Mast / Fast - - - -
TBX DSS 1622 16 Mast / Fast Programmed Fallback / 0/1 -
/ Automatic Maintain
TBX ESP 1622 16 Mast / Fast Programmed Fallback / 0/1 -
/ Automatic Maintain
TBX DSS 16C22 16 Mast / Fast Programmed Fallback / 0/1 Yes / No
/ Automatic Maintain
TBX DMS 16C22 16 Mast / Fast Programmed Fallback / 0/1 Yes / No
/ Automatic Maintain
TBX DMS 16C222 16 Mast / Fast Programmed Fallback / 0/1 Yes / No
/ Automatic Maintain
TBX CSP 1622 16 Mast / Fast Programmed - - -
/ Automatic
TBX DSS 1625 16 Mast / Fast - Fallback / 0/1 -
Maintain
TBX DMS 1625 8 (output part) Mast / Fast - Fallback / 0/1 -
Maintain
TBX DMS 16S44 8 (output part) Mast / Fast - Fallback / 0/1 -
Maintain
TBX DMS 16P22 (1) Mast / Fast Programmed Fallback / 0/1 -
/ Automatic Maintain

Key:
(1) 8 programmable output channels.

Note: Parameters in bold correspond to the parameters configured by default.

TLX DS 57 PL7 xx 95
Configuration of the discrete specific application

Momentum Parameters of Momentum discrete outputs remoted on the FIPIO

bus

Presentation The discrete Momentum output modules on the FIPIO bus have parameters for all
channels.

Parameters The table below shows the parameters available for each Momentum discrete
output module.
Module Reference Number of inputs Associated task (for the
module)
170 ADO 340 00 16 Mast / Fast
170 ADO 350 00 32 Mast / Fast
170 ADO 530 50 8 Mast / Fast
170 ADM 350 10 16 (output part) Mast / Fast
170 ADM 390 30 8 (output part) Mast / Fast
170 ADM 370 10 8 (output part) Mast / Fast

Note: Parameters in bold correspond to the parameters configured by default.

96 TLX DS 57 PL7 xx
 Configuration of the discrete specific application

Parameters of IP67 discrete outputs remoted on the FIPIO bus

Presentation The Discrete IP67 output modules on the FIPIO bus have parameters for all
channels.

Parameters The table below shows the parameters available for each Momentum discrete
output module.
Module Reference Number of inputs Associated task (for the
module)
TSX EMF 16DT2 8 (output part) Mast / Fast
TSX ESF 08T22 8 Mast / Fast

Note: Parameters in bold correspond to the parameters configured by default.

TLX DS 57 PL7 xx 97
Configuration of the discrete specific application

6.4 Configuration of discrete parameters

Presentation

Subject of this This section presents the installation of different discrete I/O channel configuration
section parameters.

What's in this This Section contains the following Maps:

Section?
Topic Page
Configuring the programmable channels of the TBX DMS 16P22 module 99
Modifying the Task parameter of a discrete module 100
Modifying the Wiring check parameter of a TBX discrete module 101
Modifying the Monitoring of external supply fault parameter for a discrete 102
module.
Modifying the Functions parameter of a discrete input module 103
Modifying the Filtering parameter of a discrete input module. 105
How to modify the Latching parameter of a discrete input module 106
Parametering the Run/Stop input of a discrete module 107
Modifying the Fallback mode parameter of a discrete output module 108
Modifying the Reactivation of outputs parameter of a discrete module. 109

98 TLX DS 57 PL7 xx
 Configuration of the discrete specific application

Configuring the programmable channels of the TBX DMS 16P22 module

Presentation In addition to its 8 input channels, this module possesses 8 channels which can be
individually configured as input or output channels.

Note: the channel type cannot be reconfigured in online mode.

Illustration The illustration below shows the configuration screen for the TBX DMS 16P22
module.
TBX DMS 16P22 [FIPIO1 MODULE 0]
Configuration Program
Designation : TBX7 SOCK 8E+8I/O 0,5 A Version : 1.0

Chan. Symbol Task Type Reactivate Fall. Mode Fall. Value

8 MAST Input Automatic Fallback
9 Input Automatic Fallback
10 Input Automatic Fallback
11 Output Automatic Fallback 0
12 Output Automatic Fallback 0
13 Input Automatic Fallback
14 Input Automatic Fallback
15 Output Automatic Fallback 0

Procedure The table below gives the procedure for configuring the programmable channels of
the TBX DMS 16P22 module.
Step Action
1 Access the module's hardware configuration screen.
2 Select Program part from the pull-down menu in the module zone.
3 Parameter the channels one by one as inputs or outputs using the pull-down
list in the Type column.

TLX DS 57 PL7 xx 99
Configuration of the discrete specific application

Modifying the Task parameter of a discrete module

Presentation This parameter defines the processor task in which inputs are acquired and outputs
are updated.
The task is defined:
l for 8 consecutive channels for Discrete in-rack modules,
l for all channels for discrete modules remoted on the FIPIO bus.
The possible choices are as follows:
l The MAST task (for discrete in-rack modules or modules on the FIPIO bus).
l The FAST task (for discrete in-rack modules or modules on the FIPIO bus).
l None if the group of channels (apart from group 0 - 7) is unused (discrete in-rack
modules only).
It is advisable to deconfigure the groups of channels not used in the application; as
a result, even if no connector is connected, the module will not indicate a fault.

Note: This parameter can only be modified in local mode.

Procedure The table below shows the procedure for defining the type of task assigned to the
channels of a module.
Step Action
1 Access the hardware configuration screen of the required module.
2 In the pull-down menu located in the Task column, click on the button for the
required group of channels.
Result: a pull-down list appears.

MAST
MAST
FAST
NONE

Note: For discrete in-rack modules with more than 16 channels, use the
scrollbar to access the different groups of channels.
3 Select the required task.
Note:
Selecting None causes the group of channels in question and the following
groups to be deconfigured, after the modification is confirmed.
reconfiguration (MAST or FAST) of a group of deconfigured channels will, after
the modification is confirmed, cause the preceding non-configured groups to be
reconfigured.
4 Confirm the deconfiguration or reconfiguration if necessary.

100 TLX DS 57 PL7 xx

 Configuration of the discrete specific application

Modifying the Wiring check parameter of a TBX discrete module

Presentation This function is used to permanently check the quality of links between:
l sensors and inputs,
l actuators and outputs.

Note: This parameter can be modified in online mode.

Procedure The table below shows the procedure for activating or deactivating the Wiring
Check parameter.
Step Action
1 Access the hardware configuration screen of the required module.
2 Click on the checkbox in the Wiring Check column of the channel to be
parametered.
3 Repeat the operation for every channel to be configured (from step 2).

TLX DS 57 PL7 xx 101

Configuration of the discrete specific application

Modifying the Monitoring of external supply fault parameter for a discrete

module.

Presentation This parameter defines the status (activated or deactivated) of external supply fault
monitoring.
It acts per group of 16 consecutive channels.
Checking is active by default (box checked).

Note: For < V2.0 versions of discrete modules (the version number is mentioned
on the label located on one side of the module), the external supply fault monitoring
cannot be deactivated; the function should be left active. If the monitoring
function is deactivated by mistake, after transfer and connection, the Diagnostics
function detects the error and the choice can then be changed in online mode. .

Procedure The table below shows the procedure for activating or deactivating the external
supply fault monitoring function.
Step Action
1 Access the hardware configuration screen of the required module.
2 Click on the checkbox in the Supply fault monitoring column.
Note: For discrete modules with more than 16 channels, use the scrollbar to
access the different groups of channels.

102 TLX DS 57 PL7 xx

 Configuration of the discrete specific application

Modifying the Functions parameter of a discrete input module

Presentation This parameter defines the properties of event inputs for TSX DEY 16 FK and TSX
DMY 28 FK modules.
The parameter may have the following values:
l normal (no event associated with the channel),
l channel by channel memorization of status (status at 0 or status at 1),
l channel by channel event processing,
l event triggered on a rising edge (RE),
l event triggered on a falling edge (FE),
l event triggered on a rising edge and falling edge,
Event inputs have an associated processing number (Evti). These numbers range
from:
l 0 to 31 for TSX5710/102/103/153, PMX 57 102, PCX 571012 processors,
l 0 to 63 for other processors.
If two edge types are selected on one channel, only one event number is associated
with the channel.
The highest priority event processing (Evti) number is 0, which can only be attributed
to channel 0.

Note:
l The event number proposed is the first available number in the list.
l A manually input number outside the tolerance range will not be accepted on
confirmation.
l Event numbers cannot be added, deleted or changed when in online mode.

TLX DS 57 PL7 xx 103

Configuration of the discrete specific application

Procedure The table below shows the procedure for defining the parameters associated with
event inputs.
Step Action
1 Access the hardware configuration screen of the required module.
2 Select the required channel.
3 In the Function column, double-click on the cell of the channel to be
parametered.
Result: The properties dialogue box appears.
Properties of channel 6 x
Function

Normal
Latch state 0
Latch state 1
Event processing
Rising
Falling
EVT 1

4 Select the required function.

5 Enter the Evt event number.
6 Repeat the operation for every channel to be configured (from step 2).

104 TLX DS 57 PL7 xx

 Configuration of the discrete specific application

Modifying the Filtering parameter of a discrete input module.

Presentation This parameter defines the filtering time for the selected channel.
The proposed values are as follows:
l 0.1 to 7.5 ms in increments of 0.5 ms for in-rack input modules,
l 0.7 ms (fast) or 5.7 ms (normal) for input modules on the FIPIO bus.

Note: Filtering of in-rack modules can only be modified in online mode.

Procedure The table below shows the procedure for defining the Filtering parameter.
Step Action
1 Access the hardware configuration screen of the required module.
2 In the pull-down menu located in the Filtering column, click on the button for
the required channel.
Result: one of the following pull-down lists appears:

In-rack module Module on FIPIO bus

Filter Filter
4 ms Fast
0.1 ms Normal
0.5 ms Fast
1 ms
1.5 ms
2 ms
2.5 ms

3 Select the required filtering time.

TLX DS 57 PL7 xx 105

Configuration of the discrete specific application

How to modify the Latching parameter of a discrete input module

Presentation This parameter defines whether or not to acknowledge a positive pulse which is
shorter than the task period.
By default, the acknowledgment is valid (box checked).

Procedure The table below shows the procedure for activating or deactivating the Latching
function.
Step Action
1 Access the hardware configuration screen of the required module.
2 Click on the checkbox in the Latching column of the channel to be
parametered.
3 Repeat the operation for every channel to be configured (from step 2).

Note: This parameter can be modified in online mode.

106 TLX DS 57 PL7 xx

 Configuration of the discrete specific application

Parametering the Run/Stop input of a discrete module

Presentation An in-rack discrete module input can be parametered to control the running or
stopping of the application program.
The change to Stop by the physical input assigned to the Run/Stop input takes
priority over a Run command from a terminal or network.
The input defined as the Run/Stop input is represented, in the module zone of the
configuration screen for the module in question, by a Run icon and Stop icon
followed by the channel number.

Note: When a channel is configured in Run/Stop input, it is not advisable to modify

the module configuration in online mode as this causes the PLC to change to Stop.

Procedure The table below shows the procedure for parametering the Run/Stop input.
Step Action
1 Access the CPU configuration screen.
2 Check the Run/Stop Input box.
3 Enter the input to be assigned in the data entry window.

TLX DS 57 PL7 xx 107

Configuration of the discrete specific application

Modifying the Fallback mode parameter of a discrete output module

Presentation This parameter defines the fallback mode adopted by outputs when the PLC
changes to Stop, in the event of a processor, rack or inter-rack cable fault.
The possible modes are as follows:
Mode Meaning
Fallback Channels are set to 0 or 1 depending on the parametered fallback value, for
the group of 8 corresponding channels.
Maintain Outputs retain the status occupied before the change to Stop.
Continuou This mode only concerns TSX DMY 28 RFK modules.
s Reflex outputs are updated by the module; when this mode is selected, the
reflex function remains active.

Note: This parameter may be modified in online mode for discrete in-rack modules.

Procedure The table below shows the procedure for defining the fallback mode assigned to a
group of channels.
Step Action
1 Access the hardware configuration screen of the required module.
2 In the pull-down menu located in the Fallback mode column, click on the
button for the required group of channels.
Result: a pull-down list appears.

Fall. mode
Fallback
Maintain
Fallback

Note: For discrete in-rack modules with more than 16 channels, use the
scrollbar to access the different groups of channels.
3 Select the required fallback mode.
4 For Fallback mode, parameter each of the channels in the selected group.
To do this, click on the button in the pull-down menu in the Fallback val.
column.
5 Click on the required value (0 or 1).

108 TLX DS 57 PL7 xx

 Configuration of the discrete specific application

Modifying the Reactivation of outputs parameter of a discrete module.

Presentation This parameter defines the tripped output reactivation mode

The possible modes are as follows:
Mode Meaning
Programmed Reactivation is performed by a command from the PLC application or via the
debug screen (1).
Note: In order to avoid closely spaced, repetitive reactivation, the module
allows a period of 10 seconds between two reactivations.
Automatic Reactivation is carried out automatically every 10 seconds until the fault
disappears.

Key:
(1) Faulty outputs can only be reactivated from the debug screen for in-rack
modules.

The reactivation mode is defined per group of 8 channels.

Note: This parameter may be modified in online mode for discrete in-rack
modules..

Procedure The table below shows the procedure for defining the reactivation mode for a
module's output channels.
Step Action
1 Access the hardware configuration screen of the required module.
2 In the pull-down menu located in the Reactivation column, click on the button
for the required group of channels.
Result: a pull-down list appears.

Reactivate
Programmedd
Programmed
Automatic

Note: For discrete in-rack modules with more than 16 channels, use the
scrollbar to access the different groups of channels.
3 Select the required task.

TLX DS 57 PL7 xx 109

Configuration of the discrete specific application

110 TLX DS 57 PL7 xx

 Debugging discrete modules

7
At a Glance

Subject of this This chapter describes the Debug aspect of the installation of the discrete
chapter application.

What's in this This Chapter contains the following Maps:

Chapter?
Topic Page
Presentation of the debug function of a discrete module. 112
Description of the debug screen of a discrete module 113
Accessing the debug screen for an in-rack discrete module. 115
Accessing the diagnostics function of a discrete module 116
Accessing the channel diagnostics function of a discrete module 117
Accessing the forcing/unforcing function 118
How to access the SET and RESET commands 119
Accessing the masking/unmasking function for an event 120
Accessing the reactivation of outputs command 121
Maintain outputs of a discrete module 122

TLX DS 57 PL7 xx 111

Debugging discrete modules

Presentation of the debug function of a discrete module.

Introduction The debug function enables the user to view the parameters of each channel (status
of channel, filter value, etc.) for each of the application's discrete I/O modules, and
to access diagnostics and adjustment for the selected channel (channel forcing,
channel masking, etc.).
The function also gives access to the module diagnostics in the event of a fault.

Note: This function is only accessible in online mode.

Limitations The table below shows the access limitations for the Debug function for I/O modules
(TBX, Momentum) remoted on the FIPIO bus.
Configuration Access to the debug function...
PL7 of version prior to V3.3 not available.
(PL7 + CPU + Application PL7) limited to four screens open simultaneously.
of version V3.3 or higher

112 TLX DS 57 PL7 xx

 Debugging discrete modules

Description of the debug screen of a discrete module

Presentation The debug screen displays the value and status of each of the selected module's
channels in real time. It is also used to control the channels (forcing of the input/
output value, reactivation of outputs, etc.).

Illustration The debug screen is displayed as follows:

1 TSX DSY 08R5 [RACK 0 POSITION 3]
Debug
2 Designation : 8O RELAY 50VA, BORN Version :
Global unforcing RUN ERR IO DIAG...

Chan. Symbol State Fault Reactivate Applied Q Channel control x

0 0 DIAG.. Reactivate STOP Forcing
1 0 DIAG..
3 2 0 DIAG.. F4 Force to 0
3 0 DIAG..
4 0 DIAG.. F5 Force to 1
5 0 DIAG..
6 0 DIAG..
7 0 DIAG.. F6 Unforce
4
Write
F7 Set

F8 Reset

Description The table below shows the different elements in the debug screen, along with their
functions.
Number Element Function
1 Title bar Indicates the reference and physical position of the selected module along with the rack
number for in-rack modules or the FIPIO connection point for remote I/Os.
2 Module zone Enables the user to select:
l the debug phase:
l Configuration,
l Installation (diagnostics), only accessible in online mode.
l the type of channels (inputs or outputs), if the module in question has both inputs and
outputs.
Displays the designation of the selected module and shows the module's status indicator
lights (Run, Err, I/O).
Provides direct access to:
l the module diagnostics when the module is faulty (shown by the indicator in the
diagnostics access button, which turns red)
l the channel Global unforcing function.
Note: Display of this zone is optional. The choice is made using the command View →
Module zone.

TLX DS 57 PL7 xx 113

Debugging discrete modules

Number Element Function

3 Channel zone Displays, in real time, the value and status of each of the channels of the module. The
symbol column displays the symbol associated with the channel, when defined by the
user (via the variables editor).
Provides direct access to:
l the channel-by-channel diagnostics when the channels are faulty (shown by the
indicator in the diagnostics access button, which turns red)
l the output reactivation command.
For TSX DMY 28 RFK modules, the channel zone, by default, displays information
relating to the diagnostics functions and gives access to the relevant commands. The
information on the status of each of the module's channels is accessed using the View
Status / View Diag contextual buttons in the module zone.
4 Command Provides access to the commands for a channel
zone

114 TLX DS 57 PL7 xx

 Debugging discrete modules

Accessing the debug screen for an in-rack discrete module.

Procedure This operation enables the user to access the debug screen for the channels of a
discrete module.
The debug screen is only accessible in online mode.
Step Action
1 Access the hardware configuration screen.
2 Double-click on the module to be configured or select the module and execute the
command Service → Open the module.
Result: The configuration screen for the selected module appears.

TSX DSY 08R5 [RACK 0 POSITION 3]

Debug
Designation : 8O RELAY 50VA, BORN Version :
Global unforcing RUN ERR IO DIAG...

Chan. Symbol State Fault Reactivate Applied Q Channel control x

0 0 DIAG.. Reactivate STOP Forcing
1 0 DIAG..
2 0 DIAG.. F4 Force to 0
3 0 DIAG..
4 0 DIAG.. Force to 1
5 0 DIAG.. F5
6 0 DIAG..
7 0 DIAG.. F6 Unforce
Write
F7 Set

F8 Reset

TLX DS 57 PL7 xx 115

Debugging discrete modules

Accessing the diagnostics function of a discrete module

Presentation The module diagnostics function displays the current faults, if there are any,
classified according to their category:
l internal faults (module failures, self-test running)
l external faults (terminal block fault),
l other fault (configuration fault, module absent or powered-down, faulty
channel(s) (details in the channel diagnostics)).
Certain indicators turn red to indicate a faulty module, for example:
l in the configuration editor at rack level:
l the module position indicator.
l in the configuration editor at module level:
l the Err and I/O indicators, depending on the type of fault,
l the Diag indicator.

Procedure The table below shows the procedure for accessing the module diagnostics screen.
Step Action
1 Access the module's debug screen.
2 Click on the Diag button in the module zone.
Result: The list of module faults appears:
Module diagnostics
Internal faults External faults Other fault
Faulty channel(s)

OK

Note: If a configuration fault occurs, in the event of a major failure or missing

module, the module diagnostics screen cannot be accessed. The following
message then appears on the screen: Module is missing or different
from that configured in this position .

116 TLX DS 57 PL7 xx

 Debugging discrete modules

Accessing the channel diagnostics function of a discrete module

Presentation The channel diagnostics function displays the current faults, if there are any,
classified according to their category:
l internal faults (channel failure)
l external faults (link or sensor supply fault),
l other faults (terminal block fault, configuration fault, communication fault).
The Diag indicator, located in the Err column of the configuration editor, turns red to
indicate a channel fault.

Procedure The table below shows the procedure for accessing the channel diagnostics screen.
Step Action
1 Access the module's debug screen.
2 Click on the Diag button in the Err column.
Result: The list of channel faults appears.
Channel diagnostics
Internal faults External faults Other faults
External supply

OK

Note: The channel diagnostics information can also be accessed via the
program using the READ_STS instruction.

TLX DS 57 PL7 xx 117

Debugging discrete modules

Accessing the forcing/unforcing function

Presentation This function is used to modify the status of all or part of a module's channels.
The status of a forced output is fixed and can only be modified by the application
after unforcing.

Note: However, when a fault causes the outputs to fall back, the status of these
channels takes the value set when the fallback mode parameter was configured.

The available commands are as follows:

l for one or more channels:
l forcing to 1,
l forcing to 0,
l unforcing (when the selected channel(s) is (are) forced),
l for all channels of a module (when at least one channel is forced):
l global unforcing of channels.

Procedure The table below shows the procedure for forcing or unforcing all or part of the
channels of a module.
See Modifying the configuration parameters of a discrete module's: General, p. 83
for multiple selection.
Step Action for one channel Action for all channels
1 Access the module's debug screen.
2 In the Status column, double-click on the Click on the Global unforcing button
cell of the required channel (1). in the module zone.
3 Select the required function. -

Key:
(1) The Channel commands screen can also be accessed by double-clicking on
the required channel and then left-clicking on the Command button.

118 TLX DS 57 PL7 xx

 Debugging discrete modules

How to access the SET and RESET commands

At a Glance These commands are used to modify the state of a module's outputs to 0 (RESET)
or 1 (SET).

Note: The state of the output assigned by one of these commands is temporary
and can be modified at any time by the application when the PLC is in RUN.

Procedure The table below shows the procedure for assigning the value 0 or 1 to all or part of
the channels of a module.
See (Modifying the configuration parameters of a discrete module's: General, p. 83 )
for multiple selection.
Step Action for one channel
1 Access the module's debug screen.
2 In the Status column, double click on the cell of the required channel (1).
3 Select the required function.

Key:
(1) The Channel commands screen can also be accessed by double-clicking on
the required channel and then left-clicking on the Command button.

TLX DS 57 PL7 xx 119

Debugging discrete modules

Accessing the masking/unmasking function for an event

Presentation This function enables the user to inhibit or restore the processing associated with
the input or output channel which caused the event.
The available commands are as follows:
l Mask (masks the events),
l Unmask (deactivates masking of events).

Note: If one or more events occur while they are inhibited, the associated
processing is lost.

Procedure The table below shows the procedure for masking or unmasking all or part of the
channels configured in event processing.
Step Action for one or more channels (1) Action for all of the configured
channels of the application
modules (2)
1 Access the module's debug screen. Access the CPU debug screen.
2 In the Status column, double-click on the Click on the Activation/Deactivation
cell of the required channel (3). button located in the Events field.
3 Select the required function. -

Key:
(1) For multiple selection, see Modifying the configuration parameters of a discrete
module's: General, p. 83.
(2) Global masking/unmasking can also be carried out using:
l the instruction PL7 MASKEVT(),
l the instruction PL7 UNMASKEVT(),
l the %S38 system bit.

(3) The Channel commands screen can also be accessed by double-clicking on

the required channel and then left-clicking on the Command button.

120 TLX DS 57 PL7 xx

 Debugging discrete modules

Accessing the reactivation of outputs command

Presentation This command is used to reactivate an output when a fault has caused it to trip, if no
fault persists at its terminals.
Reactivation is defined per group of 8 channels. It has no effect on an inactive or
fault-free channel.

Note: Outputs may only be reactivated in online mode for TBX modules.

Procedure The table below shows the procedure for reactivating tripped outputs.
Step Action
1 Access the module's debug screen.
2 Click on the Reactivate button in the Reactivation column for the required
group of channels.

TLX DS 57 PL7 xx 121

Debugging discrete modules

Maintain outputs of a discrete module

Presentation This control (red Stop indicator on) informs the user that, for a given output channel
group, these outputs are not being correctly maintained by the PLC (fallback status).
The possible causes are as follows:
l processor fault,
l rack fault,
l inter-rack link fault.

122 TLX DS 57 PL7 xx

 Bits and words associated with
discrete specific applications
8
Presentation

Subject of this This chapter presents the different word and bit objects associated with discrete
chapter specific applications as well as their addressing mode.

What's in this This Chapter contains the following Sections:

Chapter?
Section Topic Page
8.1 Addressing of discrete I/O module objects 124
8.2 Language objects associated with the discrete specific 128
application

TLX DS 57 PL7 xx 123

Language words and bits

8.1 Addressing of discrete I/O module objects

Presentation

Subject of this This section presents the specific features of addressing linked to the discrete
section specific application.

What's in this This Section contains the following Maps:

Section?
Topic Page
Addressing of language objects associated with discrete in-rack I/O modules 125
Addressing of language objects associated with discrete I/O modules remoted 126
on the FIPIO bus
Indexable discrete I/O objects. 127

124 TLX DS 57 PL7 xx

 Language words and bits

Addressing of language objects associated with discrete in-rack I/O modules

Presentation Addressing of bit and word objects is defined in Shared specific applications (See
Addressing input/output module objects in rack, p. 31).
This page describes the specific features linked to the discrete in-rack I/O modules.

Illustration Addressing principle:

% I, Q, M, K X, W, D, F X Y • i • r
Symbol Object type Format Rack Position Channel no. Rank

Specific values The table below shows the values specific to the discrete in-rack I/O module objects.
Element Values Comment
x 0 to 1 TSX 5710/102/103/153, PMX 57102, PCX 571012.
0 to 7 Other processors
y 00 to 14 When the rack number (x) is other than 0, the position (y) has a 2 digit
(1) code: 00 to 14; however, if the rack number (x) = 0, the non-meaningful
zeros are deleted (from the left) from "y" ("x" does not appear and "y"
takes 1 digit for values of less than 9).
i 0 to 63 or MOD: channel reserved for management of the module and the
MOD parameters shared by all channels.
r 0 to 3 or ERR: indicates a module or channel fault.
ERR
(1) : The number of slots requires the use of 2 racks at the same address.

TLX DS 57 PL7 xx 125

Language words and bits

Addressing of language objects associated with discrete I/O modules remoted

on the FIPIO bus

Presentation Addressing of bit and word objects is defined in (See Addressing of language
objects for modules remoted on the FIPIO bus, p. 33).
This page describes the specific features linked to the discrete I/O modules remoted
on the FIPIO bus.

Illustration Addressing principle:

% I, Q, M, K X, W, D, F \ p.2.c \ m • i • r
Symbol Object type Format Module/channel Module Channel Rank
address and number number
connection point

Specific values The table below shows the values specific to remote discrete I/O module objects.
Element Values Comment
i 0 to 31 or 0 to 15 for TBX modules.
MOD 0 to 31 for Momentum modules.
MOD: channel reserved for management of the module and the
parameters shared by all channels.
r 0 to 255 ERR: indicates a module or channel fault.
or ERR

126 TLX DS 57 PL7 xx

 Language words and bits

Indexable discrete I/O objects.

Presentation All the discrete module I/O objects are indexable (apart from the TSX DMY 28RFK
and TBX DMS 16P22 I/O module objects).
For in-rack TSX and TBX modules, indexing of %I and %Q objects is done
independently.
For Momentum modules, indexing for %I objects continues for %Q objects of the
same module.

TLX DS 57 PL7 xx 127

Language words and bits

8.2 Language objects associated with the discrete

specific application

Presentation

Subject of this This section presents the different language objects associated with the discrete
section specific application.

What's in this This Section contains the following Maps:

Section?
Topic Page
Implicit exchange language objects associated with the discrete specific 129
application
Exchange management: Exchanges in progress module 130
%MW@module.MOD.0:Xj or channel %MW@module.i.0:Xj
Exchange management: Module %MW@module.MOD.1:Xj or channel 132
%MW@module.i.1:Xj report
Explicit exchange objects: General 134
Explicit exchange object: %MW@module.i.2:Xj channel status 135
Explicit exchange object: Status Module %MW@module.MOD.2:Xj 136
Explicit exchange object: %MW@module.i.3:Xj channel command 137

128 TLX DS 57 PL7 xx

 Language words and bits

Implicit exchange language objects associated with the discrete specific

application

Presentation Exchanges for these objects are carried out automatically on each cycle of the task
in which the module channels are configured.

Bit objects The table below shows the different implicit exchange bit objects.
Address (1) Function Meaning when the bit is at status 1
%I@module.i Input channel bit Indicates, for input channel i, that the sensor output controlling
the input is activated.
%Q@module.i Output channel bit Indicates that output channel i is activated.
%I@module.i.ERR Channel error bit Indicates that input channel i is faulty.
%I@module.MOD.ERR Module error bit Indicates that the module is faulty.

Key:
(1) @module = module address.
l xy for in-rack modules,
l \p2c\m for remote modules.

Word objects The table below shows the different implicit exchange word objects.
Address (1) Function Meaning for Xj = 1
%IW@module.i:X0 Event status Indicates that event processing is configured on a rising edge.
%IW@module.i:X1 associated with Indicates that event processing is configured on a falling edge.
channel i
%QW@module.i:X0 Command word Masks/unmasks the event associated with the channel.
associated with
channel i

Key:
(1) @module = module address.
l xy for in-rack modules,
l \p2c\m for remote modules.

TLX DS 57 PL7 xx 129

Language words and bits

Exchange management: Exchanges in progress module

%MW@module.MOD.0:Xj or channel %MW@module.i.0:Xj

Presentation These word-type objects provide information on the module or channel i exchanges
in progress.
They are updated automatically by the system.

Description The table below explains the meanings of the different bits in the word
%MW@module.MOD.0.
Address (1) Meaning for Xj = 1
%MW@module.MOD.0:X0 Exchange of status words in progress on at least one channel
of the module.
%MW@module.MOD.0:X1 Exchange of command words in progress on at least one
channel of the module.

Key:
(1) @module = module address.
l xy for in-rack modules,
l \p2c\m for remote modules.

Description The table below explains the meanings of the different bits in the word
%MW@module.i.0.
Address (1) Meaning for Xj = 1
%MW@module.i.0:X0 Exchange of status words in progress on channel i.
%MW@module.i.0:X1 Exchange of command words in progress on channel i.

Key:
(1) @module = module address.
l xy for in-rack modules,
l \p2c\m for remote modules.

130 TLX DS 57 PL7 xx

 Language words and bits

Example The example below shows one possible way in which this type of word can be used

(* Update request for channel 0 status words*)

(* for the module located at slot 3 of rack 0 *)
(* if no exchange in progress on this channel *)
IF NOT %MW3.0:X0 THEN READ_STS %CH3.0;
END_IF;

Note: If the explicit exchange does not last as long as the PLC task cycle time, the
%MW@module.i:X0 bit never changes to 1.

TLX DS 57 PL7 xx 131

Language words and bits

Exchange management: Module %MW@module.MOD.1:Xj or channel

%MW@module.i.1:Xj report

Presentation These word-type objects provide information on the exchange reports for the
module or channel i.
They are updated automatically by the system.

Description The table below explains the meanings of the different bits in the word
%MW@module.MOD.1.
Address (1) Meaning for Xj = 1
%MW@module.i.1:X0 Status parameter exchange error on at least one channel of the
module.
%MW@module.i.1:X1 Command parameter exchange error on at least one channel
of the module.

Key:
(1) @module = module address.
l xy for in-rack modules,
l \p2c\m for remote modules.

Description The table below explains the meanings of the different bits in the word
%MW@module.i.1.
Address (1) Meaning for Xj = 1
%MW@module.i.1:X0 Status parameter exchange error on channel i.
%MW@module.i.1:X1 Command parameter exchange error on channel i.

Key:
(1) @module = module address.
l xy for in-rack modules,
l \p2c\m for remote modules.

132 TLX DS 57 PL7 xx

 Language words and bits

Example The example below shows one possible way in which this type of word can be used

(* Status error detected on module located at *)

(*slot 3 of rack 0 *)
IF NOT %MW3.MOD.0:X0 THEN READ_STS %CH3.MOD;
END_IF;
IF %MW3.MOD.1:X0 THEN SET %M100;
END_IF;

TLX DS 57 PL7 xx 133

Language words and bits

Explicit exchange objects: General

Presentation Explicit exchange objects carry information (e.g. terminal block fault, module
missing etc.) and additional commands for advanced programming of specific
application functions.

Note: The configuration constants %KW@module.i.r (@module = module

address), which are not documented in this manual, are accessible in read only
mode and correspond to the configuration parameters entered using the
Configuration editor.

Explicit exchanges objects are exchanged at the request of the user program using
the following instructions:
l READ_STS (read status words),
l WRITE_CMD (write command words),
l WRITE_PARAM (write adjustment parameters),
l READ_PARAM (read adjustment parameters),
l SAVE_PARAM (save adjustment parameters),
l RESTORE_PARAM (restore adjustment parameters).

134 TLX DS 57 PL7 xx

 Language words and bits

Explicit exchange object: %MW@module.i.2:Xj channel status

Presentation This word-type object provides information on the status of channel i.

It is updated on execution of the instruction READ_STS%CH@module.i.

Description The table below explains the meanings of the different bits in the word
%MW@module.i.2.
Address (1) Meaning for Xj = 1
%MW@module.i.2:X0 External fault: Tripped.
%MW@module.i.2:X1 (2) External fault: Fuse.
%MW@module.i.2:X2 Terminal block fault.
%MW@module.i.2:X3 External supplyfault.
%MW@module.i.2:X4 Internal fault: Module Out of Order
%MW@module.i.2:X5 Software or hardware configuration fault.
%MW@module.i.2:X6 Communication fault.
%MW@module.i.2:X7 Reserved.
%MW@module.i.2:X8 External fault: Short-circuit.
%MW@module.i.2:X9 External fault: Line fault.
%MW@module.i.2:X10 à X15 Reserved.

Key:
(1) @module = module address.
l xy for in-rack modules,
l \p2c\m for remote modules.

(2) For Momentum I/Os: minor external fault on the connection base; the meaning of
this depends on the connection base in use (see Momentum documentation).

TLX DS 57 PL7 xx 135

Language words and bits

Explicit exchange object: Status Module %MW@module.MOD.2:Xj

Presentation This word-type object provides information on the status of the module.
It is updated on execution of command READ_STS%CH@module.MOD.

Description The table below explains the meanings of the different bits in the word
%MW@module.MOD.2.
Address (1) Meaning for Xj = 1 Module type
%MW@module.MOD.2:X0 Internal fault: Module Out of Order. Base
%MW@module.MOD.2:X1 Functional Fault (2). Base
%MW@module.MOD.2:X2 Terminal block fault. Base
%MW@module.MOD.2:X3 Functional Fault (2). Base
%MW@module.MOD.2:X4 Self-testing Base
%MW@module.MOD.2:X4 Reserved. Base
%MW@module.MOD.2:X5 Software or hardware configuration fault. Base
%MW@module.MOD.2:X6 Module missing Base
%MW@module.MOD.2:X7 Fault on FIPIO extension module. Base
%MW@module.MOD.2:X8 Internal fault: Module Out of Order. FIPIO extension
%MW@module.MOD.2:X9 Functional Fault (2). FIPIO extension
%MW@module.MOD.2:X10 FIPIO Extension Terminal Block Fault. FIPIO extension
%MW@module.MOD.2:X11 Self-testing FIPIO extension
%MW@module.MOD.2:X12 Reserved. FIPIO extension
%MW@module.MOD.2:X13 Software or hardware configuration fault. FIPIO extension
%MW@module.MOD.2:X14 Module missing FIPIO extension
%MW@module.MOD.2:X15 Reserved. FIPIO extension
Key:
(1) @module = module address.
l xy for in-rack modules,
l \p2c\m for remote modules.

(2) Fault coming from extension module or bus (Base-extension or FIPIO).

Note: for FIPIO remoted I/Os comprising a base module followed by an extension
module, only the status word of the base module is significant. Its least significant
byte is assigned to the base module, while its most significant byte is assigned to
the extension module.

136 TLX DS 57 PL7 xx

 Language words and bits

Explicit exchange object: %MW@module.i.3:Xj channel command

Presentation This word-type object is used to modify certain parameters for a group of channels.
It is updated on execution of command WRITE_CMD%CH@module.i.

Note: This object is specific to output modules with reactivation.

Description The table below explains the meanings of the different bits in the word
%MW@module.i.3.
Address (1) Meaning for Xj = 1
%MW@module.i.3:X0 Reactivation of tripped outputs (protected outputs).
%MW@module.i.3:X1 Inhibition of external supply control.
%MW@module.i.3:X2 Confirmation of external supply control.
%MW@module.i.3:X3 to X15 Reserved.

Key:
(1) @module = module address.
l xy for in-rack modules,
l \p2c\m for remote modules.
i = first channel in group of channels (0, 8, 16, ...).

TLX DS 57 PL7 xx 137

Language words and bits

138 TLX DS 57 PL7 xx

 Installation of the discrete reflex
module
9
Presentation

Subject of this This chapter presents the specific installation features of discrete reflex module TSX
chapter DMY 28 RFK.

What's in this This Chapter contains the following Sections:

Chapter?
Section Topic Page
9.1 General presentation of discrete reflex module 140
9.2 Reflex function blocks 142
9.3 Configuration of discrete reflex module 187
9.4 Bits and words associated with discrete reflex module 194

TLX DS 57 PL7 xx 139

Installation of the discrete reflex module

9.1 General presentation of discrete reflex module

Presentation of discrete reflex module

General The standard architecture of the PLC with I/O modules and periodical or event tasks
does not allow for the reaction time required by certain types of applications.

The aim of the TSX DMY 28 RFK discrete reflex module is to resolve these particular
application issues. In order to do this, it has:
l a faster response time than the Fast task or event task.
l an output reaction with a simple logic of under 0.5 ms,
l speed control for moving parts and movement stopping control when the speed
becomes too slow,
l feedback control between movements,
l time-outs with a time base of 0.1ms
l continuous oscillation generation at a fixed frequency, but with a variable duty
cycle,
l ...

Operating The TSX DMY 28 RFK module operates independently from the PLC task . It has its
principle own I/Os (16I/12O), ensuring a reaction time of less than 1ms.

At the same time, the internal variables are exchanged with the PLC processor, but
at the rate of the PLC task assigned to them.
These variables are as follows:
l the image bits of the module's physical input status (%I),
l the image bits of the module's physical and auxiliary output statuses (%I),
l the command bits of the module outputs (%Q).

140 TLX DS 57 PL7 xx

 Installation of the discrete reflex module

Illustration The diagram below shows the operating principle of the discrete reflex module.
Response time < 1 ms

TSX DMY 28 RFK Module

Inputs Outputs

Reflex function

%Ixy.i (0 à 15) %Ixy.i (16 à 31)

%Ixy.i.1 (16 à 31)
PLC task
Acquisition

Processing

Update

%Qxy.i

TLX DS 57 PL7 xx 141

Installation of the discrete reflex module

9.2 Reflex function blocks

Presentation

Subject of this This section presents the different reflex functions available.
section

What's in this This Section contains the following Maps:

Section?
Topic Page
Function block: Direct 143
Reflex function block: Combinational 144
Reflex function block: Operation timer 146
Reflex function block: Idle timer 147
Reflex function block: Operation-idle timer 148
Reflex function block: 2 value operation timer 150
Reflex function block: Operation-idle time with value selection 153
Reflex function block: Retriggerable monostable 156
Reflex function block: Monostable with time delay 157
Reflex function block: 2 value monostable 159
Reflex function block: Oscillator 161
Reflex function block: D flip-flop 162
Reflex function block: T flip-flop 164
Reflex function block: 2 threshold counter 166
Reflex function block: Came électronique simple 168
Reflex function block: 1 threshold intervalometer 170
Reflex function block: Burst 172
Reflex function block: PWM (Pulse Width Modulation) 173
Reflex function block: Detection of underspeed 174
Reflex function block: Speed monitoring 176
Reflex function block: Type 1 command-check 179
Reflex function block: Type 2 command-check 181
Reflex function block: Command-counting 183
Reflex function block: Fault Signaling 185

142 TLX DS 57 PL7 xx

 Installation of the discrete reflex module

Function block: Direct

Role This block is proposed by default and does not apply any reflex function to the
module output. The output is then controlled from the application as for a standard
discrete output module.

Structure The table below shows the block's different interfaces.

Name Meaning
x Block's physical output.
x Aux Block's internal auxiliary output.

Operation Physical output x is directly controlled by its command bit %Qxy.i updated by the
PLC processor.
Outputs x and x Aux have identical values.

Illustration The diagram below illustrates the Direct.

TSX DM 28 RFK Module
Inputs Outputs

PLC task
Acquisition of the inputs

Application processing

Update of the outputs

TLX DS 57 PL7 xx 143

Installation of the discrete reflex module

Reflex function block: Combinational

Role This function enables a logic function to be performed between the inputs and one
or more of the module's outputs.

Structure The table below shows the block's different interfaces.

Name Meaning
x Block's physical output.
x Aux Block's internal auxiliary output.

Operation The logic function entered is directly applied to the x output.

Outputs x and x Aux have identical values.

Note: A logic function can be made up of several combinational functions by using

the %Ixy.i bits associated with the output channels as intermediate variables.

Illustration 1 The illustration below shows an example of a simple combinational function

%I2.1.0 %I2.0.0 %I2.4.0 Combinational Output 16

I %I2.16.0 I

Output 16 Aux

144 TLX DS 57 PL7 xx

 Installation of the discrete reflex module

Illustration 2 The illustration below shows an example of a combinational function using the
auxiliary output of the first combinational as an intermediate variable.

%I2.1.0 %I2.0.0 %I2.4.0 Combinational Output 16

I %I2.16.0 I

Output 16 Aux

%I2.16.1 %I2.10.0 Combinational Output 17

I %I2.8.0 I

Output 17 Aux

TLX DS 57 PL7 xx 145

Installation of the discrete reflex module

Reflex function block: Operation timer

Role This function is used to apply an on-delay to an action.

Structure The table below shows the block's different interfaces.

Name Meaning Illustration
E Timer input.
E TIMER in operation Output x
x Timer's physical output.
x Aux Block's internal auxiliary ti
output. Output x Aux

Operation This table describes the different operating phases of the operation timer.
Phase Description
1 On the rising edge of the E input, time-out ti is launched (time base of 0.1ms).
2 When the time-out is over, the x output changes to 1.
If the high status of input E lasts less time than ti, output x stays at 0.
Note: The values of outputs x and x Aux are identical.

Illustration The illustration below shows the trend diagram of the operation timer function block.

E
ti

x Aux

146 TLX DS 57 PL7 xx

 Installation of the discrete reflex module

Reflex function block: Idle timer

Role This function is used to apply an off-delay to an action.

Structure The table below shows the block's different interfaces.

Name Meaning Illustration
E Timer input.
E TIMER idle Output x
x Timer's physical output.
x Aux Block's internal auxiliary output.
ti
Output x Aux

Operation This table describes the different operating phases of the idle timer.
Phase Description
1 The x output changes to 1 when the E input changes to 1.
2 On the falling edge of the E input, time-out ti is launched (time base of 0.1ms).
3 When the time-out is over, the x output changes to 0.
If the low status of input E lasts less time than ti, output x stays at 1.
Note: The values of outputs x and x Aux are identical.

Illustration The illustration below shows the trend diagram of the idle timer function block.

ti

x Aux

TLX DS 57 PL7 xx 147

Installation of the discrete reflex module

Reflex function block: Operation-idle timer

Role This function is used to apply an on-off-delay to an action.

Structure The table below shows the block's different interfaces.

Name Meaning Illustration
E Timer input.
E TIMER in operation/idle Output x
x Timer's physical output.
x Aux Block's internal auxiliary
tri
output.
tfi Output x Aux

Operation This table describes the different operating phases of the operation-idle timer.
Phase Description
1 On the rising edge of the E input (on-delay) , time-out tri is launched (time base
of 0.1ms).
2 When time-out tri is over, the x output changes to 1.
If the high status of input E lasts less time than tri, output x stays at 0.
3 On the falling edge of the E input (off-delay) , time-out tfi is launched (time base
of 0.1ms).
4 When time-out tfi is over, the x output changes to 0.
During time-out tfi, if the low status of input E lasts less time than tfi, output x
stays at 1.
Note: The x Aux output is at 1 as long as input E or output x is at 1.

148 TLX DS 57 PL7 xx

 Installation of the discrete reflex module

Illustration The illustration below shows the trend diagram of the operation-idle timer function
block.

tri tfi

x Aux

TLX DS 57 PL7 xx 149

Installation of the discrete reflex module

Reflex function block: 2 value operation timer

Role This function is used to apply a t1i or t2i on-delay to an action.

Structure The table below shows the block's different interfaces.

Name Meaning
E Timer input.
Sel Selection of time-out t1i or t2i.
l Sel = 0 : time-out t1i,
l Sel = 1 : time-out t2i,

Direct Selection of block (for string operation).

l Direct = 0: block selected
l Direct = 1: block not selected (output x takes the value of E).

x Timer's physical output.

x Aux Block's internal auxiliary output.
Illustration

E 2-valuesTIMER Output x

Sel t1i
Direct t2i Output x Aux

Operation This table describes the different operating phases of the 2 value operation timer.
Phase Description
1 On the rising edge of the E input, a time-out corresponding to the status of input
Sel is launched.
2 When the time-out is over, the x and x Aux outputs change to 1.
If the high status of input E lasts less time than the selected time-out, output x
stays at 0.

150 TLX DS 57 PL7 xx

 Installation of the discrete reflex module

Illustration The illustration below shows the trend diagram of the 2 value operation timer
function block.

E
Sel

x
t1i t2i

x Aux

String operation It is possible to increase the number of time-outs which can be selected by stringing
together several blocks, with the x output of one forming the E input of the next.
Phase Description
1 On the rising edge of the E input of the first block a time-out is launched,
corresponding to:
l the block whose Direct input is at 0,
l the status of the Sel input.
Note: Two blocks must not simultaneously have their Direct inputs set to 0.
2 When the time-out is over, the x and x Aux outputs change to 1.
If the high status of the E input of the first block lasts less time than the selected
time-out, output x stays at 0.
3 The x output changes to 0 on the falling edge of the E input .
Note:
l x and x Aux have identical values.
l the x Aux outputs can be used for tracking,
l when stringing together several blocks, it is essential to change the statuses of Sel
and Direct only when the 0 status of input E is at 0.

TLX DS 57 PL7 xx 151

Installation of the discrete reflex module

Illustration The table below shows the tracking of two timers.

E 2-values TIMER Output x E 2-values TIMER Output x1

Sel t1i Sel t1i

Direct t2i Output x Aux Direct t2i Output x Aux1

152 TLX DS 57 PL7 xx

 Installation of the discrete reflex module

Reflex function block: Operation-idle time with value selection

Role This function is used to apply a t1i or t2i on-delay or off-delay to an action.
The assignment of a t1i time-out on-delay to an action causes the t2i off-delay for
this same action.
Similarly, the assignment of a t2i time-out on-delay causes a t1i off-delay to be
assigned.

Structure The table below shows the block's different interfaces.

Name Meaning
E Timer input.
Sel Selection of time-out t1i or t2i.
l Sel = 0 : t1i on-delay, t2i off-delay.
l Sel = 1 : t2i on-delay, t1i off-delay.

Direct Selection of block (for string operation).

l Direct = 0: block selected
l Direct = 1: block not selected (output x takes the value of E).

x Timer's physical output.

x Aux Block's internal auxiliary output.
Illustration

E TIMER in operation/idle Output x

Sel ti1
Direct t2i Output x Aux

TLX DS 57 PL7 xx 153

Installation of the discrete reflex module

Operation This table describes the different operating phases of the operation-idle timer with
value selection.
Phase Description
1 On the rising edge of input E :
l the time-out corresponding to the status of input Sel is launched,
l output x Aux changes to 1.

2 When the selected time-out is over

l output x changes to 1,
l output x Aux changes to 0.
If the high status of input E lasts less time than the selected time-out, output x
stays at 0.
3 On the falling edge of input E:
l the time-out corresponding to the status of input Sel is launched,
l output x Aux changes to 1.

4 When the selected time-out is over

l output x changes to 1,
l output x Aux changes to 0.
If the low status of input E lasts less time than the selected time-out, output x
stays at 0.

Illustration The illustration below shows the trend diagram of the operation-idle timer with value
selection function block.

Sel

x Aux
t1i t2i t2i t1i

154 TLX DS 57 PL7 xx

 Installation of the discrete reflex module

String operation It is possible to increase the number of time-outs which can be selected by stringing
together several blocks, with the x output of one forming the E input of the next.
Phase Description
1 On the rising edge of input E of the first block:
l the time-out is launched, corresponding to:
l the block whose Direct input is at 0,
l the status of the Sel input.
l output x Aux changes to 1.
Note: Two blocks must not simultaneously have their Direct inputs set to 0.
2 When the selected time-out is over
l output x of the relevant block changes to 1.
l output x Aux of the relevant block changes to 0.
If the high status of the E input of the first block lasts less time than the selected
time-out, output x stays at 0.
3 On the falling edge of input E of the first block:
l the time-out is launched, corresponding to:
lthe block whose Direct input is at 0,
lthe status of the Sel input.
l output x Aux changes to 1.
Note: Two blocks must not simultaneously have their Direct inputs set to 0.
4 When the selected time-out is over:
l output x of the relevant block changes to 1.
l output x Aux of the relevant block changes to 0.
If the low status of the E input of the first block lasts less time than the selected
time-out, output x stays at 0.
5 The x output changes to 0 on the falling edge of the E input.
Note:When stringing together several blocks It is essential to change the statuses of
the Sel and Direct inputs only when the status of input E of the first block is set to 0..

Illustration The table below shows the tracking of the two timers.

E TIMER in operation/idle Output x E TIMER in operation/idle Output x1

Sel ti1 Sel ti1

Direct t2i Output x Aux Direct t2i Output x Aux1

TLX DS 57 PL7 xx 155

Installation of the discrete reflex module

Reflex function block: Retriggerable monostable

Role This function launches an action of duration ti, with the possibility of extending it for
an identical duration.

Structure The table below shows the block's different interfaces.

Name Meaning Illustration
E Monostable input.
E Retriggerable MONO Output x
x Monostable's physical output.
x Aux Block's internal auxiliary output.
ti
Output x Aux

Operation This table describes the different operating phases of the retriggerable monostable.
Phase Description
1 On the rising edge of input E (on-delay):
l time-out ti is launched (time-base of 0.1ms),
l outputs x and x Aux change to 1.

2 When time-out ti is over, outputs x and x Aux change to 0.

If a new rising edge for input E occurs before time-out ti has elapsed, outputs x
and x Aux remain at 1 for a further time-out ti.

Illustration The illustration below shows the trend diagram of the retriggerable monostable
function block.

x
ti ti
ti

x Aux

156 TLX DS 57 PL7 xx

 Installation of the discrete reflex module

Reflex function block: Monostable with time delay

Role This function enables an action of a duration t2i to be launched with a t1i delay, with
the possibility of extending it for an identical duration.

Structure The table below shows the block's different interfaces.

Name Meaning Illustration
E Monostable input.
E Time-delayed MONO Output x
x Monostable's physical output.
x Aux Block's internal auxiliary output.
t1i
t2i Output x Aux

Operation This table describes the different operating phases of the monostable with time
delay.
Phase Description
1 On the rising edge of input E :
l time-out t1i is launched (time-base of 0.1ms),
l output x Aux changes to 1.

2 When time out t1i is over:

l time-out t2i is launched (time base of 0.1ms),
l output x changes to 1 for duration t2i.
If the high status of input E lasts less time than time-out t1i, output x stays at 0.
3 When time-out t2i is over, outputs x and x Aux change to 0.
If a new rising edge for input E occurs before time-out t2i has elapsed:
l output x remains at 1 for duration t2i of the cycle in progress.
l a new cycle begins (see phase).

TLX DS 57 PL7 xx 157

Installation of the discrete reflex module

Illustration The illustration below shows the trend diagram of the monostable with time delay
function block.

x
t1i t2i
t1i t2i

x Aux

158 TLX DS 57 PL7 xx

 Installation of the discrete reflex module

Reflex function block: 2 value monostable

Role This function enables an action of duration t1i or t2i to be applied to the triggering
of an action.

Structure The table below shows the block's different interfaces.

Name Meaning
E Monostable input.
Sel Selection of time-out t1i or t2i.
l Sel = 0 : t1i on-delay,
l Sel = 1 : t2i on-delay,

Direct Selection of block (for string operation).

l Direct = 0: block selected
l Direct = 1: block not selected (output x takes the value of E).

x Monostable's physical output.

x Aux Block's internal auxiliary output.
Illustration

E 2-values MONO Output x

Set t1i
Direct t2i Output x Aux

Operation This table describes the different operating phases of the 2 value monostable.
Phase Description
1 On the rising edge of input E :
l a time-out corresponding to the status of input Sel is launched (time base of
0.1ms),
l outputs x and x Aux change to 1.

2 When the time-out is over, the x and x Aux outputs change to 0.

TLX DS 57 PL7 xx 159

Installation of the discrete reflex module

Illustration The illustration below shows the trend diagram of the monostable with time delay
function block.

Sel
t2i t1i

x Aux

String operation It is possible to increase the number of time-outs which can be selected by stringing
together several blocks, with the x output of one forming the E input of the next.
Phase Description
1 On the rising edge of input E of the first block:
l the time-out is launched, corresponding to:
l the block whose Direct input is at 0,
l the status of the Sel input.
l outputs x and x Aux change to 1.
Note: Two blocks must not simultaneously have their Direct inputs set to 0.
2 When the time-out is over, the x and x Aux outputs change to 0.
Note:When stringing together several blocks It is essential to change the statuses of
the Sel and Direct inputs only when the status of input E is set to 0.

Illustration The table below shows the tracking of the two monostables.

E 2-values MONO Output x E 2-values MONO Output x 1

Set t1i Set t1i

Direct t2i Output x Aux Direct t2i Output x Aux

160 TLX DS 57 PL7 xx

 Installation of the discrete reflex module

Reflex function block: Oscillator

Role This function enables a time base to be created, with the option of defining the signal
parameters (status 0 or 1).

Structure The table below shows the block's different interfaces.

Name Meaning Illustration
E Oscillator input.
E OSCILLATOR Output x
x Oscillator's physical output.
x Aux Block's internal auxiliary output.
t1i
t2i Output x Aux

Operation This table describes the different operating phases of the oscillator.
Phase Description
1 On the rising edge of input E :
l output x oscillates for period t1i +t2i where:
l t1i = length of high status of oscillation (time base of 0.1ms),
l t2i = length of low status of oscillation (time base of 0.1ms),
l output x Aux changes to 1.

2 On the falling edge of input E:

l output x changes to 0 as soon as t1i for the current period is over,
l the x output changes to 0 when the current period is over.

Illustration The illustration below shows the trend diagram of the oscillator function block.

x
t1i t2i t1i t2i

x Aux

TLX DS 57 PL7 xx 161

Installation of the discrete reflex module

Reflex function block: D flip-flop

Role This function is used to carry out sequential logic functions, such as memorization
of an edge, etc.

Structure The table below shows the block's different interfaces.

Name Meaning
D Flip-flop input.
CLK Enable input.
SET Output x set to 1.
RESET Output x set to 0. This input takes priority over SET input.
x Flip-flop's physical output.
x Aux Block's internal auxiliary output.
Illustration

E D flip-flop Output x
Clk
Set
Reset Output x Aux

Operation This table describes the different operating phases of the D flip-flop.
Phase Description
1 On the rising edge of input CLK:
l output x takes the status of input D,
l output x Aux takes the opposite status to input D.

162 TLX DS 57 PL7 xx

 Installation of the discrete reflex module

Illustration The illustration below shows the trend diagram of the D flip-flop function block.

CLK

RESET

SET

x Aux

TLX DS 57 PL7 xx 163

Installation of the discrete reflex module

Reflex function block: T flip-flop

Role This function allows a 2-way split to be performed.

Structure The table below shows the block's different interfaces.

Name Meaning
E Flip-flop input.
CLK Enable input.
SET Outputs x / x Aux set respectively to 1 / 0.
RESET Outputs x / x Aux set respectively to 0 / 1. This input takes priority over SET
input.
x Flip-flop's physical output.
x Aux Block's internal auxiliary output.
Illustration

E T flip-flop Output x
Clk
Set
Reset Output x Aux

Operation This table describes the different operating phases of the T flip-flop.
Phase Description
1 On the rising edge of input CLK:
l if input E is at 1:
l output x takes the opposite status to its current status,
l output x Aux takes the opposite value to x,
l if input E is at 0, outputs x and x Aux remain at that status.

164 TLX DS 57 PL7 xx

 Installation of the discrete reflex module

Illustration The illustration below shows the trend diagram of the T flip-flop function block.

CLK

RESET

SET

x Aux

TLX DS 57 PL7 xx 165

Installation of the discrete reflex module

Reflex function block: 2 threshold counter

Role This counting function is used to detect when a threshold th1 or th2 has been
crossed.

Structure The table below shows the block's different interfaces.

Name Meaning
E Enable input.
l E = 0: Up input frozen,
l E = 1: Up input valid.

Up Counting input.
Note: the maximum performance of the counter is 2 Khz (with the Up input
directly controlled by the physical input (without filtering)).
RESET Counter initialization input.
In order to take into account a change in the value of the threshold to be reached,
a Reset is required.
Sel Selection of counting threshold:
l Sel = 0 : threshold th1 selected,
l Sel = 1: threshold th2 selected,
Note: the maximum value of a threshold corresponds to the maximum number
of points (65536points).
x Counter's physical output.
x Aux Block's internal auxiliary output.
Illustration

E COUNTER, 2 Output x
Up
Reset th1
Set th2 Output x Aux

166 TLX DS 57 PL7 xx

 Installation of the discrete reflex module

Operation This table describes the different operating phases of the 2 threshold counter.
Phase Description
1 On the rising edge of RESET input:
l counter initialized to 0
l inputs x and x Aux change to 0,
l Counter increased on the rising edge of Up input .

2 On the rising edge of Up input, counter increased (value not accessible).

3 When the selected threshold is reached, inputs x and x Aux change to 1.

Illustration The illustration below shows the trend diagram of the 2 threshold counter function
block.

RESET

Sel

Up

th2
th1

x Aux

TLX DS 57 PL7 xx 167

Installation of the discrete reflex module

Reflex function block: Came électronique simple

Role This function is used to detect when the two thresholds th1 and th2 have been
crossed.

Structure The table below shows the block's different interfaces.

Name Meaning
E Enable input.
l E = 0: Up input frozen,
l E = 1: Up input valid.

Up Counting input.
Note: the maximum performance of the counter is 2 Khz (with the Up input
directly controlled by the physical input (without filtering)).
RESET 0 Output x forced to 0.
RESET 1 Counter initialization input.
Note: If the counter is not reset to 0, when it reaches the maximum value (65536
points), it will change to 0,1,2 etc. Therefore it is advisable to inhibit counting
(E=0) by using the x Aux output in series with output E.
x Cam's physical output.
x Aux Block's internal auxiliary output.
Illustration

E Single electronic CAM Output x

UP
Reset0 ti
Reset1 th Output x Aux

168 TLX DS 57 PL7 xx

 Installation of the discrete reflex module

Operation This table describes the different operating phases of the simple cam.
Phase Description
1 On the rising edge of input RESET 1:
l counter initialized to 0
l input x Aux changes to 1,
On the high status of input RESET 0:
l input x is forced to 0.

2 On the rising edge of input Up, the counter is increased.

3 When threshold th1 is reached, output x changes to 1.
4 When threshold th2 is reached, outputs x and x Aux change to 0.

Illustration The illustration below shows the trend diagram of the simple cam function block.

RESET 0

RESET 1

Up

th2
th1

x Aux

TLX DS 57 PL7 xx 169

Installation of the discrete reflex module

Reflex function block: 1 threshold intervalometer

Role This function is used to trigger an action after an interval th with a maximum
precision of 0.1ms

Structure The table below shows the block's different interfaces.

Name Meaning
E Intervalometer initialization input.
RESET 1 Outputs x and x Aux are set to 0.
ti Time-base (0.1ms to 6.5535 s).
x Intervalometer's physical output.
x Aux Block's internal auxiliary output.
Illustration

E INTERVALOMETER, 1 Output x

ti
Reset1 th Output x Aux

Operation This table describes the different operating phases of the intervalometer.
Phase Description
1 On the rising edge of input E :
l counter initialized to 0
l input x changes to 0.

2 Counter increases at the rate of time-base ti.

3 When threshold th is reached, output x changes to 1.
4 On the falling edge of input E with output x at 1, output x Aux changes to 1.

170 TLX DS 57 PL7 xx

 Installation of the discrete reflex module

Illustration The illustration below shows the trend diagram of the intervalometer function block.

RESET 1

Time-
base

th

x Aux

TLX DS 57 PL7 xx 171

Installation of the discrete reflex module

Reflex function block: Burst

Role This function is used to generate a pulse stream of a time length 2 x ti.

Structure The table below shows the block's different interfaces.

Name Meaning Illustration
E Block's input.
E BURST Output x
x Block's physical output.
x Aux Block's internal auxiliary output.
ti
ni Output x Aux

Operation This table describes the different operating phases of the Burst function block.
Phase Description
1 On the rising edge of input E :
l oscillation of output x for ni periods of time,
l input x Aux changes to 1,

2 When number of periods ni is reached, output x Aux changes to 0.

If output E changes to 0 before time periods ni have elapsed:
l the oscillation stops at the low status of outputx,
l input x Aux changes to 0,

Illustration The illustration below shows the trend diagram of the burst function block.

ti ti

x Aux

172 TLX DS 57 PL7 xx

 Installation of the discrete reflex module

Reflex function block: PWM (Pulse Width Modulation)

Role This function is used to generate a fixed period periodic signal t1i with a variable
duty cycle t2i/t1i.

Structure The table below shows the block's different interfaces.

Name Meaning Illustration
E Block's input.
E PWM generation Output x
x Block's physical output.
x Aux Block's internal auxiliary
t1i
output (control output).
t2i Output x Aux

Operation This table describes the different operating phases of the PWM function block.
Phase Description
1 On the rising edge of input E :
l oscillation of output x,
l control input x Aux changes to 1.

2 On the low status of input E:

l the oscillation of output x stops at its low status,
l control input x Aux changes to 0.
Note: if t2i (high status of period t1i) is higher than or equal to t1i, output x
continually keeps the high status.

Illustration The illustration below shows the trend diagram of the PMW function block.

t2i
t1i

x Aux

TLX DS 57 PL7 xx 173

Installation of the discrete reflex module

Reflex function block: Detection of underspeed

Role This function is used to halt an action, after a start phase t1i (masking), if the time
elapsing between two consecutive pulses is higher than t2i.

Structure The table below shows the block's different interfaces.

Name Meaning Illustration
E Enable function input.
E slow speed detection 1 Output x
FB Control input.
x Block's physical output.
t1i
x Aux Block's internal auxiliary
FB t2i Output x Aux
output.

Operation This table describes the different operating phases of the speed detection.
Phase Description
1 On the rising edge of input E :
l time-out t1i (masking time) is launched,
l input x changes to 1.

2 When time-out t1 has elapsed, and then on each edge of input à FB, time-out
t2i is launched.
If the rising edges of input FB are spaced out at interval t2i:
l output x changes to 0,
l output x Aux changes to 1 (signaling end of movement).
If input E changes to 0, outputs x and x Aux change to 0.

174 TLX DS 57 PL7 xx

 Installation of the discrete reflex module

Illustration The illustration below shows the trend diagram of the speed detection function block.

E
t1i

FB
t<t2i t<t2i t<t2i t2i

x Aux

TLX DS 57 PL7 xx 175

Installation of the discrete reflex module

Reflex function block: Speed monitoring

Role This function is used to control or halt an action according to two thresholds t1i and
t2i.

Structure The table below shows the block's different interfaces.

Name Meaning Illustration
E Enable function input.
FB Control input. E slow speed detection 2 Output x

x Block's physical output.

x Aux Speed control output. t1i
FB t2i Output x Aux

Application Activation of a conveyor belt upstream (controlled by the x Aux input) depending on
example the speed of a conveyor belt downstream:
l conveyor belt operational when the speed of the downstream belt is greater than
the high threshold 1/t1i,
l conveyor belt stops when the speed of the downstream belt is less than the low
threshold 1/t2i,
This involves analyzing the time elapsed between 2 consecutive pulses on control
input FB.
The following graph illustrates the application example given above.

Speed of the downstream belt

Speed 1/t1i

Speed 1/t2i

x Aux

176 TLX DS 57 PL7 xx

 Installation of the discrete reflex module

Operation This table describes the different operating phases of the speed monitoring function.
Phase Description
1 On the rising edge of input E :
l time-out t1i is launched,
l input x changes to 1.

2 As long as the interval between 2 rising edges of input FB remains greater than
t1i:
l time-out t1i is relaunched on the rising edge of input FB.
If the interval between 2 rising edges of input FB falls below t1i:
l output x Aux changes to 1,
l time-out t2i is launched,
If input E changes to 0, outputs x and x Aux change to 0.

x Aux

1/t1i Speed

3 As long as the interval between 2 rising edges of input FB is less than t2i:
l time-out t2i is relaunched on the rising edge of input FB.
If the interval between 2 rising edges of input FB becomes greater than t2i:
l output x Aux changes to 0,
l time-out t1i is launched (see phase),
If input E changes to 0, outputs x and x Aux change to 0.

x Aux

1/t2i 1/t1i Speed

Note: The operation defined above implies that t2i >t1i.

TLX DS 57 PL7 xx 177

Installation of the discrete reflex module

Illustration The illustration below shows the trend diagram of the speed monitoring function
block.

FB

t>t1i t<t1i t<t2i t>t2i t<t1i t<t1i

t=t2i

x Aux

178 TLX DS 57 PL7 xx

 Installation of the discrete reflex module

Reflex function block: Type 1 command-check

Role This function is used to command an action and to check whether it has been carried
out after time period ti

Structure The table below shows the block's different interfaces.

Name Meaning Illustration
Cde Command input.
Cmd Command / Control type 1 Output x
Ctrl Control input.
Acq Acknowledgement of fault.
Ack ti
x Block's physical output. Ctrl Output x Aux
x Aux Block's internal auxiliary output.

Operation This table describes the different operating phases of the type 1 command-check
function.
Phase Description
1 On the rising edge of input Cde:
l time-out ti is launched,
l input x changes to 1.

2 When time-out ti is over:

l if the Ctrl signal changes to status 1 during the time-out interval, the x Aux
output stays at 0 (normal situation),
l if the Ctrl signal is not received, the x Aux output changes to 1 (type A error
signal).
l if the Ctrl signal falls back while the Cde input is at 1, the x Aux output
changes to 1 (type B error signal).
A rising edge on the Acq input with the Ctrl input at 1 causes the x Aux to be
set to 0.
3 On the falling edge of the Cde input, the x and x Aux outputs change to 0.

TLX DS 57 PL7 xx 179

Installation of the discrete reflex module

Illustration The illustration below shows the trend diagram of the type 1 command-check
function block.

Cde

x
t<ti t<ti t>ti

ti
Ctrl

Acq

x Aux

180 TLX DS 57 PL7 xx

 Installation of the discrete reflex module

Reflex function block: Type 2 command-check

Role This function is used to:

l command an action and check whether it has been carried out after time period
t1i,
l delete the action and check whether it has been deleted after time period t2i.

Structure The table below shows the block's different interfaces.

Name Meaning Illustration
Cde Command input.
Ctrl n Control n input Cmd Command / Control type 2 Output x

Acq Acknowledgement of fault. Ack

Ctrl 1 t1i
x Block's physical output.
Ctrl 2 t2i Output x Aux
x Aux Block's internal auxiliary output.

Operation This table describes the different operating phases of the type 2 command-check
function.
Phase Description
1 On the rising edge of input Cde:
l time-out t1i is launched,
l input x changes to 1.

2 When time out t1i is over:

l if the Ctrl1 signal changes to status 1 during time-out interval t1i, the x Aux
input stays at 0 (normal situation),
l if the Ctrl1 signal is not received, the x Aux output changes to 1 (type A error
signal).
l if the Ctrl1 signal falls back while the Cde input is at 1, the x Aux output
changes to 1 (type B error signal).
The x Aux input is set to 0 in the event of:
l a rising edge on input Acq with input Ctrl1 at 1,
l change of status of input Cde.

3 On the falling edge of input Cde:

l time-out t2i is launched,
l input x changes to 0.

TLX DS 57 PL7 xx 181

Installation of the discrete reflex module

Phase Description
4 When time out t2i is over:
l if the Ctrl2 signal changes to status 1 during time-out interval t2i, the x Aux
input stays at 0 (normal situation),
l if the Ctrl2 signal is not received, the x Aux output changes to 1 (type A error
signal).
l if the Ctrl2 signal falls back while the Cde input is at 0, the x Aux output
changes to 1 (type B error signal).
The x Aux input is set to 0 in the event of:
l a rising edge on input Acq with input Ctrl2 at 1,
l change of status of input Cde.

Illustration The illustration below shows the trend diagram of the type 2 command-check
function block.

Cde

x
t<t1i t<t1i t>t1i

t1i
Ctrl1
t<t2i t>t2i
t2i
Ctrl2

Acq

x Aux

182 TLX DS 57 PL7 xx

 Installation of the discrete reflex module

Reflex function block: Command-counting

Role This function is used to decect a th threshold in order to command a positioning

action.

Structure The table below shows the block's different interfaces.

Name Meaning Illustration
Cde Command input.
E Command / Counting Output x
Reset Outputs x and x Aux are set to 0.
Up Counting input.
Reset th
x Block's physical output.
Up Output 18 Aux
x Aux Block's internal auxiliary output.

Operation This table describes the different operating phases of the command-counting
function.
Phase Description
1 Counter initialized to 0 on the rising edge of the Reset input.
2 On the rising edge of the Cde input, the x input changes to 1.
On every rising edge of the Up input, the counter is increased.
3 When threshold th is reached, or if input Cde changes to 0, outputs x and x Aux
change to 0.
Note: Input Cde does not influence the counting carried out on the rising edge of the
Up input.

TLX DS 57 PL7 xx 183

Installation of the discrete reflex module

Illustration The illustration below shows the trend diagram of the command-counting function
block.

Cde

Reset

Up

th

x Aux

184 TLX DS 57 PL7 xx

 Installation of the discrete reflex module

Reflex function block: Fault Signaling

Role This function is used to indicate a fault, with acknowledgement and clearing.

Structure The table below shows the block's different interfaces.

Name Meaning Illustration
Def Fault input.
Err Fault signalling Output x
Acq Acknowledgement input
Eff Clear input AcK t1i
x Block's physical output. Clr t2i Output x Aux
x Aux Output inactive for this block.

Operation This table describes the different operating phases of the Fault Signaling function.
Phase Description
1 If the Def status is at the high status, the x output oscillates for period 2 x t1i.
2 On the rising edge of input Acq:
l if the fault persists, the output changes to 1,
l if the fault disappears, the output oscillates for period 2 x t2i.

3 On the rising edge of the Eff input, the x output changes to 0.

Note: Should the fault still remain, the cycle begins again in phase.
Note: Output x flashes when a fault occurs:
l t1i flashes rapidly: fault present and unacknowledged by Acq,
l t2i flashes slowly: fault not present and acknowledged by Acq,
l lit up: fault present and acknowledged by Acq,
l out: last fault cleared by the Eff input after acknowledgement.

TLX DS 57 PL7 xx 185

Installation of the discrete reflex module

Illustration The illustration below shows the trend diagram of the Fault Signaling function with
t1i < t2i.

Def

Acq

Eff

2 x t1i 2 x t1i 2 x t2i

186 TLX DS 57 PL7 xx

 Installation of the discrete reflex module

9.3 Configuration of discrete reflex module

Presentation

Subject of this This section presents the specific configuration features of a discrete reflex module.
section

What's in this This Section contains the following Maps:

Section?
Topic Page
Configuring the discrete reflex module 188
Presentation of the reflex function configuration editor 189
Assigning and configuring a reflex function 191
Adjusting the configuration parameters of a reflex function 192
Associating an event with a virtual output 193

TLX DS 57 PL7 xx 187

Installation of the discrete reflex module

Configuring the discrete reflex module

Introduction The TSX DMY 28 RFK discrete reflex module uses the standard discrete I/O
parameters (See Configuration of discrete parameters, p. 98)).
However, it also has its own specific parameters, such as:
l assigning of a reflex function to a given output channel,
l association of an event with a virtual output.
A reflex function, assigned in this way to a given channel, must itself be configured
and its internal parameters adjusted.

Illustration The screen below shows some examples of function assignment for a given
channel.
Spécific parameters

Chan. Symbol Supply Monit. Task Reactivate Fall. Value Function Event
16 Active MAST Programmed Fallback to Combinational
17 Fallback to TIMER in operation
18 Fallback to TIMER idle
19 Fallback to TIMER with 2 values,
20 Fallback to MONO with time delay
21 Fallback to OSCILLATOR
22 Fallback to COUNTER, 2
23 Fallback to PWM generation
24 MAST Programmed Fallback to Command/counting
25 Fallback to Fault signalling
26 Fallback to Direct
27 Fallback to Direct
28v Fallback to Direct
29v Fallback to Direct
30v Fallback to Direct
31v Fallback to Direct

188 TLX DS 57 PL7 xx

 Installation of the discrete reflex module

Presentation of the reflex function configuration editor

Presentation The reflex function configuration editor is made up of a grid from which the function
block is chosen and into which graphical objects relating to the sequential logic of
the block are entered.

Illustration The illustration below shows the configuration zone of a reflex function block.

E TIMER in operation Output 26

ti=0

Output 26 Aux

1 2 1 2 1 2 1 2 3 4 5 6

Description The table below shows the different parts of the configuration zone.
Number Function
1 Columns allowing contacts to be entered with their associated language object.
2 Columns allowing horizontal and vertical links between contacts to be entered.
3 Column allowing the function blocks or their link with the combinational to be set
to 1.
4 Column showing the inputs on the selected function block.
5 Column:
l showing the type of internal parameter used by the block,
l allowing the required reflex function to be selected.

6 Column allowing the type of output coil to be entered.

TLX DS 57 PL7 xx 189

Installation of the discrete reflex module

Description of The table below shows the various graphical objects available depending on the
graphical objects entry column or cell.
Object Column(s) Description
-- -- 1, 2, 3 Empty zone
----------- 1, 2, 3 Horizontal link

------ |------ 2 Vertical link

1- 3 Input set to 1
----| |---- 1 Normally open contact
----|/|---- 1 Normally closed contact
----( )---- 6 Direct coil
----(/)---- 6 Negated coil

190 TLX DS 57 PL7 xx

 Installation of the discrete reflex module

Assigning and configuring a reflex function

Presentation By default, the output channels of a reflex module are declared as standard discrete
outputs. It is also necessary to reassign the required function for each channel used.
Configuration of a reflex function involves defining operating conditions such as:
l the sequential logic associated to the different inputs,
l the type of output required,
l parametering of the block.
The sequential logic is generated in contact language using the language objects
associated with the reflex module concerned.

Procedure The table below shows the different steps involved in the configuration of a reflex
function block.
Step Action
1 Access the module's hardware configuration screen.
2 Select Outputs from the pull-down menu in the module zone.
3 Click in the Function cell of the channel to be assigned.
4 Select the required function from the pull-down list.
5 Generate the sequential logic. To do this, click in the chosen cell then:
l select a graphical object (contact, link, set input to 1),
l for a contact select:
l the variable (%Ixy, %Qxy, ERR),
l the i address.
l select the type of coil.

4 Confirm the configuration by clicking onConfirm.

TLX DS 57 PL7 xx 191

Installation of the discrete reflex module

Adjusting the configuration parameters of a reflex function

Introduction Certain reflex function blocks have internal parameters (values of between 0 and
65535) required for their operation (example: temporal thresholds).
These parameters are modifiable:
l from the module's adjustment screen (in local mode only),
l by program (see Explicit exchange objects: General, p. 134 ).

Procedure The table below describes the procedure for modifying the adjustment parameters
of a reflex function block.
Step Action
1 Access the module's hardware configuration screen.
2 Select the adjustment mode from the pull-down list in the module zone.
Result: the screen below appears.

TSX DMY 28RFK [RACK 0 POSITION 2]

Chan. Function block Input 1 TM value 1 Input 2 TM value 2
16 INTERVALOMETER, 1 ti 2 th 50000
17 TIMER with 2 values, in operation t1i 3000 t2i 50000
18 TIMER with 2 values, in operation t1i 50000 t2i 50000
19 OSCILLATOR t1i 10000 t2i 10000
20 Fault signalling t1i 1000 t2i 200
21 Direct
22 Direct
23 Direct
24 Directe
25 Direct
26 Direct
27 Direct
28v Direct
29v Directe
30v Direct
31v Combinational

3 For the channel concerned, select the cell relating to the parameter to be
entered.
4 Enter the parameter.
5 Confirm by pressing Enter.

192 TLX DS 57 PL7 xx

 Installation of the discrete reflex module

Associating an event with a virtual output

Introduction Virtual outputs are not physical outputs of the module. They act on the internal status
bits of the module and can be associated with events.
A virtual output can thus trigger a PLC processor event task.

Event output The possible event processing properties are:

properties l normal (no event associated with the channel),
l channel by channel event processing,
l event triggered on a rising edge (RE),
l event triggered on a falling edge (FE),
l event triggered on a rising edge and falling edge,
If two edge types are selected on one channel, only one event number is associated
with the channel.
Event inputs have an associated processing number (Evti). These numbers range
from:
l 0 to 31 for TSX 5710/102/103/153, PMX 57 102, PCX 571012 processors,
l 0 to 63 for other processors.
The highest priority event processing (Evti) number is 0, which can only be attributed
to channel 0.

Note: The following concerns the event number.

l The event number proposed is the first available number in the list.
l A manually input number outside the tolerance range will not be accepted on
confirmation.
l Event numbers cannot be added, deleted or changed when in online mode.

Performance The maximum event frequency is 1 kHz / Number of programmed event outputs.
The maximum number of events in one burst is 100 events per 100ms.

Procedure The table below gives the different steps enabling an event to be associated with an
output and its properties to be defined.
Step Action
1 Access the module's hardware configuration screen.
2 Select Outputs from the pull-down menu in the module zone.
3 Double-click in the Event cell of the channel to be assigned.
4 Select the required function.
5 Enter the Evt event number.
6 Repeat the operation for every channel to be configured (from step).

TLX DS 57 PL7 xx 193

Installation of the discrete reflex module

9.4 Bits and words associated with discrete reflex

module

Presentation

Subject of this This section presents the different language objects specific to the discrete reflex
section module.

What's in this This Section contains the following Maps:

Section?
Topic Page
Implicit exchange language objects associated with module TSX DMY 28 RFK 195
Explicit exchange language objects associated with module TSX DMY 28 RFK 197

194 TLX DS 57 PL7 xx

 Installation of the discrete reflex module

Implicit exchange language objects associated with module TSX DMY 28 RFK

Presentation Implicit exchange language objects associated with the reflex module can be used
in:
l the sequential logic of the function block,
l the PLC processor program,

Illustration The illustration below shows the different exchanges possible:

l within a reflex module,
l between the reflex module and the PLC processor.

PLC processor Reflex module

PLC program Physical
inputs
%Ixy.i (i=0 à 15) 0 à 15

%Ixy.i (i=16 à 31) Physical

outputs
16 à 27
Output x
%Qxy.i (i=16 à 31)
Sequential Logic

Output x Aux
%Ixy.i.1 (i=16 à 31)

Event task

%Ixy.i (i=28 à 31)

Bit objects The table below shows the different implicit exchange bit objects of module TSX
DMY 28 RFK.
Address Function Use within module Use in the PLC program
Mode Update Mode Update
%Ixy.i Image bits of the module's physical Read Real time Read (1)
(i = 0 to 15) input status.
%Ixy.i Image bits of the module's physical Read Real time Read (1)
(i = 16 to 27) output status.
%Ixy.i Image bits of the module's virtual Read Real time Read (1)
(i = 28 to 31) output status.

TLX DS 57 PL7 xx 195

Installation of the discrete reflex module

Address Function Use within module Use in the PLC program

Mode Update Mode Update
%Ixy.i.1 Image bits of the module's internal Read Real time Read (1)
(i = 16 to 31) auxiliary output status.
%Qxy.i Module output command bits Read (1) Read/ (1)
(i = 16 to 31) (2) Write
ERRi Short circuit error bits for the Read Real time -
(i = 16 to 27) module's physical outputs
ERR28 External supply error bits for Read Real time -
module inputs
ERR29 External supply error bits for Read Real time -
module outputs
%Ixy.i.ERR Channel error bit - Read (1)
%Ixy.i.MOD.ERR Module error bit - Read (1)

Key:
- Not used
(1) Update to the rate of the PLC task in which the channels are configured.
(2) These command bits control the corresponding physical outputs when the Direct function is
selected.

Word objects The table below shows the different implicit exchange word objects of module TSX
DMY 28 RFK.
Address Function Use within module Use in the PLC program
Mode Update Mode Update
%IWxy.i:X0 Event status associated with - Read (1)
(i = 28 to 31) channel i X0 = 1: rising edge
%IWxy.i:X1 Event status associated with - Read (1)
(i = 28 to 31) channel i X1 = 1: falling edge
%IWxy.i:X7 Event status associated with - Read (1)
(i = 28 to 31) channel i X7 = 1: loss of event
%QWxy.i:X0 Event masking command bit - Write (1)
(i = 28 to 31)

Key:
- Not used
(1) Update to the rate of the PLC task in which the channels are configured.

196 TLX DS 57 PL7 xx

 Installation of the discrete reflex module

Explicit exchange language objects associated with module TSX DMY 28 RFK

Presentation The TSX DMY 28 RFK module reuses the language objects of standard discrete
modules (see the Language objects associated with the discrete specific
application, p. 128.
It does however have two explicit exchange objects, specific to the reflex outputs,
which enable the internal values of the function blocks to be modified (e.g.: th1, th2
for a 2 threshold counter).
These objects are as follows:
l %MWxy.i.4 which contains the first internal value of the function block,
l %MWxy.i.5 which contains the second internal value of the function block,

Modification of Other than the standard instructions (see Explicit exchange language objects
the internal associated with module TSX DMY 28 RFK , p. 197), the TSX DMY 28 RFK module
values by also uses a specific instruction MOD_PARAM (Modify parameters) which enables
program the parameters associated with a single channel to be modified.
Syntax: MOD_PARAM %CHxy.i (no., value1 , value2 , 0) where:
l i = 16 or 24 (index of the first channel of a group of 8 channels),
l no. = 0 to7 (index of the channel in the group of channels).
Example:
Modification of parameters of channel 18 (value 01 = 10 ms (100 x 0.1 ms) , value
2 = 500 ms (5000 x 0.1 ms))
MOD_PARAM %CHxy.16 (2, 100 , 5000 , 0)

TLX DS 57 PL7 xx 197

Installation of the discrete reflex module

198 TLX DS 57 PL7 xx

 AS-i Bus

III
At a Glance

Aim of this part This part presents the AS-i bus on PLC TSX/PCX 57 and describes its implemen-
tation with the software PL7 Junior and Pro.

What's in this This Part contains the following Chapters:

part?
Chapter Chaptername Page
10 General introduction to the AS-i Bus 201
11 AS-i bus configuration 209
12 Debugging the AS-i bus 221
13 Bits and words associated with the AS-i function 235
14 AS-i operating mode 247
15 AS-i performance 255
16 DFB for AS-i Security Monitor 257

TLX DS 57 PL7 xx 199

AS-i Bus

200 TLX DS 57 PL7 xx

 General introduction to the AS-i
Bus
10
At a Glance

Subject of this This Chapter introduces the AS-i bus on the TSX/PCX 57 PLC, and describes how
Chapter to access the different application editors.

What's in this This Chapter contains the following Maps:

Chapter?
Topic Page
Presentation of the AS-i Bus 202
Architecture of the TSX SAY 100 module 204
Structure of an AS-i slave 206
How to declare an AS-i communication module in the PLC rack 207
How to access the AS-i Bus configuration 208

TLX DS 57 PL7 xx 201

AS-i Bus

Presentation of the AS-i Bus

At a Glance The AS-i Bus (Actuator Sensor-Interface) allows the interconnection on a single
cable of sensor devices/actuators at the lowest level of automation.
These sensors/actuators will be defined in the documentation as slave devices.

To implement the AS-i application you need to define the physical context of the
application into which it will integrated (rack, supply, processor, modules, AS-i slave
devices connected to the bus) then ensure its software implementation.

This second aspect will be carried out from the different PL7 editors:
l either in local mode,
l or in connected mode; in this case the modification is limited to certain
parameters.

Implementation The following table presents the different implementation phases of the AS-i bus.
principles
Mode Phase Description
Local Declaration of module Selection of the TSX SAY 100 module’s slot in the rack.
Declaration of slave devices Selection for each device:
l of its slot number on the bus,
l of the slave type.

Configuration of the module Input of the configuration parameters.

channel (See AS-i bus
configuration, p. 209)
Confirmation of the Confirmation on the module level.
configuration parameters.
(See Confirming the
configuration of a module.,
p. 66)
Global confirmation of the Confirmation at application level.
application (See Globally
reconfiguring an
application., p. 67)
Local or Symbolization Symbolization of the variables associated with the slave devices.
connected Programming Programming the functions that are carried out with the help of the
AS-i bus.

202 TLX DS 57 PL7 xx

 AS-i Bus

Mode Phase Description

Connected Transfer Transfer of the application to the PLC.
Debugging Debugging the application with the help of:
l the debugging help screens which display the slave
connection, their parameters, …
l the diagnostic screens which allow identification of errors.

Local or Documentation Printing the different information relating to the application.

connected

Note: The order defined above is given for information only, the PL7 software
allows you to use the editors interactively in the required order (however you
cannot use the data or program editor without having configured the module and
the slave devices beforehand).

TLX DS 57 PL7 xx 203

AS-i Bus

Architecture of the TSX SAY 100 module

At a Glance The TSX SAY 100 module operates according to the master/slave mode. The
master only controls exchanges on the bus.
The AS-i standard sets several operating levels offered by the master:
l Profile M0 - Minimum Master: the master only puts forward the configuration of
slaves connected to the bus on power-up and input/output exchanges.
l Profile M1 - Full Master: this profile covers all the operating functions set by the
AS-i standard,
l Profile M2 - Reduced Master: this profile corresponds to profile M0 operating
functions with a slave-parametering option.

Note: The TSX SAY 100 module has an M2 profile, with the additional option of
reading slave diagnostics information.

The module includes data fields which are used to manage the lists of slaves and I/
O data images. This information is stored in a volatile memory.

Illustration of the The figure below shows the TSX SAY 100 module architecture.
architecture TSX SAY 100

1 I/O data

Parameters
2
current AS-i bus

3 Configuration /
Identification

4 LDS
5 LAS
6 LPS

204 TLX DS 57 PL7 xx

 AS-i Bus

Description of The table below shows the different elements that make up the architecture of the
constituent TSX SAY 100 module.
elements
Number Element Description
1 I/O data Image of 124 inputs and 124 outputs of AS-i bus.
2 Current parameters Image of parameters for all slaves.
3 Configuration/ This field contains all the I/O codes and identification
Identification codes for all the detected slaves.
4 LDS List of all the slaves detected on the bus.
5 LAS List of active slaves on the bus.
6 LPS List of slaves expected on the bus and configured by
PL7.

TLX DS 57 PL7 xx 205

AS-i Bus

Structure of an AS-i slave

At a Glance The AS-i bus is used to interconnect 31 slave devices, each one having:
l 4 input bits,
l 4 output bits,
l 4 parametering bits,
Thus the AS-i bus can manage a maximum number of 248 I/O.
Each slave has its own address and a profile (defines variables exchange).

Structure The figure below shows the structure of an AS-i slave.

illustration
AS-i slave
D3
1 I/O data
D0

P3
2 Parameters
P0

Configuration/
3 Identification AS-i bus

4 Address

Description of The table below shows the different elements that make up the structure of an AS-i
constituent slave.
elements
Number Element Description
1 Input/output Input data is stored by the slave and made available for the AS-i
data master.
Output data is updated by the master module.
2 Parameters The parameters are used to control and switch internal operating
modes to the sensor or the actuator.
3 Configuration/ This field contains:
Identification l the code which corresponds to I/O configuration,
l the slave identification (ID) code.

4 Address Physical address of slave.

Note: The operating parameters, address, configuration and identification data are saved in
a non-volatile memory.

206 TLX DS 57 PL7 xx

 AS-i Bus

How to declare an AS-i communication module in the PLC rack

Procedure This operation allows you to declare an AS-i communication module in the rack of
the PLC TSX 57 using the software.
Step Action
1 Double click on the required position in the rack displayed.
Result: The dialog box Add a module appears:
Add a module

Family: Module:
Analog mod. 1.5 TSX SAY100 As-Interface OK
Communication 1.5 MODULE
Upcounting 1.5 TSX SCY 21600 PCMCIA MODULE Cancel
Movement 1.5 TSX SCY 21601 PCMCIA MODULE
Weighing 1.7
Discrete 1.5

2 Select the choice Communication in the Family field.

3 Select in the field Module the reference of the module.
4 Confirm the selection with OK.
Result: The module is declared in its slot; this is grayed out and contains the
module reference.
Configuration
XMWI
TSX 57303 V5.0... XT I..

0 1 2 3 4 5 6
P T S
S S A
Y X Y
0 2 5
6 7 1
0 1 0
0 0 0
3

Note: The maximum number of TSX SAY 100 modules which can be installed
in a configuration is:
l 2 modules, with a TSX/PMX/PCX 57-1• processor,
l 4 modules, with a TSX/PMX/PCX 57-2• processor,
l 8 modules, with a TSX/PMX/PCX 57-3• processor, a TSX/PMX 57-4•
processor.

TLX DS 57 PL7 xx 207

AS-i Bus

How to access the AS-i Bus configuration

Procedure This operation allows access to the configuration of an AS-i communication module.
Step Action
1 Access the screen Hardware configuration
Result: The rack’s hardware configuration screen appears.
Configuration
XMWI
TSX 57303 V5.0... XT I..

0 1 2 3 4 5 6
P T S
S S A
Y X Y
0
2 5
6 7 1
0 1 0
0 0 0
3

2 Double click on the position of the communication module or select the module
and then carry out the command Service → Open the module.
Result: The selected module’s hardware configuration screen appears.
TSX SAY 100 [RACK 0 POSITION 6]
Configuration
Designation :AS-Interface module

Chan. 0 MAST

AS-interface configuration General parameters Fallback mode on failure

1 Automatic addressing Maintien Fallb. to 0
2 Slave 1 configuration:
3 Profile
Comment
4
Asi entry AS-i symbol Parameters
5 1 0
2
6 3 1
4
7 2
8 Asi output AS-i symbol 3
1
9 2
3
10 4

208 TLX DS 57 PL7 xx

 AS-i bus configuration

11
At a Glance

Subject of this This Chapter describes the Configuration aspect for installing the AS-i bus.
Chapter

What's in this This Chapter contains the following Maps:

Chapter?
Topic Page
Description of an AS-i communication module’s configuration screen 210
How to define a slave device on the AS-i bus 212
How to modify the AS-i Bus software configuration 214
How to access the description of an AS-i slave 215
How to define a new slave profile in the standard AS-I catalogue 217
How to modify AS-i slave general parameters: Automatic addressing 219
How to modify AS-i slave general parameters: Fallback mode 220

TLX DS 57 PL7 xx 209

AS-i bus configuration

Description of an AS-i communication module’s configuration screen

At a Glance The configuration screen of the AS-i module gives access to the parameters
associated with the module and the slave devices.

Illustration This screen allows the display and modification of the parameters in local mode, as
well as Debugging in connected mode.

1 TSX SAY 100 [RACK 0 POSITION 6]

Configuration
Designation :AS-Interface module
2

Chan. 0 MAST
3

AS-interface configuration General parameters Fallback mode on failure

1 Maintien Fallb. to 0 5
Automatic addressing
2 Slave 1 configuration:
3 Profile
Comment
4 Parameters
Asi entry AS-i symbol
5 1 0
4 2
6 3 1
7 4 6
2
8 Asi output AS-i symbol 3
1
9 2
10 3
4

210 TLX DS 57 PL7 xx

 AS-i bus configuration

Description The following table shows the different elements of the configuration screen and
their functions.
Address Element Function
1 Title bar Indicates the reference of the selected module and its physical position in the rack.
2 Command zone Allows the selection of the parameter type:
l Configuration,
l Debugging (diagnostic), only accessible in connected mode.
Displays the designation of the selected module.
Display of this zone is optional. Selection is made using the command View →
Module zone.
3 Channel zone Allows selection of the task in which the information from the AS-i communication
channel will be scanned:
l MAST task,
l FAST task.
Display of this zone is optional. Selection is made using the command View →
Channel zone.
4 AS-i configuration Allows:
zone l display of the slave devices connected to the bus,
l definition of a new configuration (adding, modifying or detecting slave devices).

5 General parameters Allows the display and the selection of the general parameters which are applied
zone to all the slaves on the bus.
l Automatic addressing,
l Fallback mode.

6 Slave configuration Allows display of the data associated with the selected slave, such as:
zone l its profile,
l a comment,
l its AS-i symbol (the symbols are defined with the help of the variables editor),
l its parameters.

TLX DS 57 PL7 xx 211

AS-i bus configuration

How to define a slave device on the AS-i bus

At a Glance The PL7 software offers a catalogue, which regroups all of the AS-i slaves that are
available. This catalogue is structured in families (e.g.: Inductive detectors).
The list of slave device families contains two distinct elements:
l Non-specialized products,
l Private family.
Selection of a non-specialized product allows the selection of an AS-i profile
amongst 240 possibilities.
Selecting Private family gives the user the possibility of managing a specific AS-i
device catalogue file via its programming terminal.

Note: An application using the AS-i products from the Private Family catalogue is
always linked to the usage of this same private family catalogue.

Procedure This operation supports the declaration of a slave device on the AS-i bus.
Step Action
1 Access the AS-i module’s hardware configuration screen.
2 In the field AS-interface configuration, double click in the cell corresponding to
the new slave’s (1 to 31) host slot number or select the said cell and then carry
out the Edit → Add a slave command.
Result: The screen Associate a profile appears.
Associate Profile
AS-interface profile families
Code AS-i family name
8 Capacitive detectors
11 Inductive proximity sensors
9 Photo-electric detectors
1 Private family
12 IP20 connection interface

AS-interface profile catalog

AS-i Name Comment View

Add

Modify

Details

Ok Cancel

212 TLX DS 57 PL7 xx

 AS-i bus configuration

Step Action
3 In the Family Name field select the required family.
Result: The Profile catalogue associated with the selected family appears.

Associate a profiile
AS-interface profile families
AS-i AS-i family name
7 Control station
8 Détecteurs capacitifs
9 Photo-electric detectors
10 Interface E/S
11 Détecteurs inductifs

AS-i -Catalog : Photo-electric detectors

Nom Commentaire View
1.1 XUJ-K063539AS Photo elect. detect. reflex
1.1 XUJ-K103534AS Photo elect. detect. Thru beam Add
1.1 XUJ-K123538AS Photo elect. detect bs 1.2m
Modify
1.1 XUJ-K703538AS Photo elect. detect bs 0.7m
1.1 XUJ-ZAS1 Back over for XUJ detectors Détails

Ok Cancel

4 In the Profile catalogue select the required device.

5 Confirm the selection with OK.
Result: The slave device is defined in its slot, the reference of the connected
device appears opposite the number of the slave.
AS-interface configuration

1
2 P XUJ-K1233538AS
3
4
5

6 To connect other slave devices to the AS-i bus, repeat the procedure from step
2.

TLX DS 57 PL7 xx 213

AS-i bus configuration

How to modify the AS-i Bus software configuration

At a Glance The PL7 software offers, from the AS-i module’s configuration screen, a group of
functions which allow you to easily modify, in locale mode, the software
configuration of the AS-i bus.

Procedure for This operation allows the deletion of a slave declared on an AS-i Bus.
deleting a slave
Step Action
1 Select the slave to be deleted.
2 Select the command Edit → Delete an AS-i slave.

Procedure for This operation allows the movement of a slave declared on an AS-i Bus.
moving a slave
Step Action
1 Select the slave to be moved.
2 Select the command Edit → Cut an AS-i slave.
3 Select the new required slot.
4 Select the command Edit → Paste an AS-i slave.

Procedure for This operation allows the copying of a slave declared on an AS-i Bus.
copying a slave
Step Action
1 Select the slave to be copied.
2 Select the command Edit → Copy an AS-i slave.
3 Select the slot of the new slave.
4 Select the command Edit → Paste an AS-i slave.

214 TLX DS 57 PL7 xx

 AS-i bus configuration

How to access the description of an AS-i slave

At a Glance The PL7 software allows access to all the information relating to an AS-i device such
as:
l the definition of a profile,
l the details of a profile.

Definition of a A profile is defined by:

profile l its name,
l a comment (optional),
l identifiers (IO, ID),
l a number of inputs and/or outputs,
l operation parameters.

Details of a The Detail function allows access, for a given slave, to all the information presented
profile in the catalog file.
Profile Details

r4e_01
Reference: XZ-SDA10D2
User module active
Enable the connection of 4 sensors.
PNP type input.
Maximum current used by 4 sensors = 100mA
Version:
Supplier: Télémécanique
AS- profilei: 0.0
I/O Error:
INPUTS:
PNP type
D0: I-1 Sensor signal 1 (pins 4-2)
D1: I-2 Sensor signal 2 (pins 4-2)
D2: I-3 Sensor signal 3 (pins 4-2)
D3: I-4 Sensor signal 4 (pins 4-2)

OK

TLX DS 57 PL7 xx 215

AS-i bus configuration

Procedure for The following table shows the procedure for displaying the characteristics of a slave
accessing device.
information on a
Step Action
profile
1 Access the AS-i module’s hardware configuration screen.
2 Double click on the required slave.
Result:: The window Associate a profile displays and highlights the device in
question
3 Click on the button:
l View to access definition information,
l Detail to access all the information.

216 TLX DS 57 PL7 xx

 AS-i bus configuration

How to define a new slave profile in the standard AS-I catalogue

At a Glance The PL7 software offers the possibility to define a slave profile, which was not
provided, in the standard catalogue.
The new profile, defined in this way, is added to the catalogue in Private family.
This profile can then be used as a standard catalogue profile.

Note: A profile cannot be deleted, only their name and comment can be changed.

Procedure The following table presents the procedure for defining a slave profile, which is not
provided in the standard catalogue.
Step Action
1 Access the AS-i module’s hardware configuration screen.
2 Double click in a slave’s host cell (1 to 31).
Result: The screen Associate a profile appears.
3 Select Private family in the field Family name.
Result: The Profile catalog linked to the selected family appears.
Associate Profile
AS-interface profile families
Code AS-i family name
8 Capacitive detectors
11 Inductive proximity sensors
9 Photo-electric detectors
1 Private family
12 IP20 connection interface

AS-interface profile catalog

AS-i Name Comment View
A.4 Sensor 1I 4Q
Add

Modify

Details

Ok Cancel

4 Click on the button Add.

5 Enter:
l the name of the new profile,
l a comment (optional).

TLX DS 57 PL7 xx 217

AS-i bus configuration

Step Action
6 Select:
l the IO code (corresponds to the input/output configuration),
l the ID code (identifier).

7 For each parameter define:

l the system’s acknowledgement (box checked),
l a label (optional).

8 Confirm the introduction of a new profile using Confirm.

218 TLX DS 57 PL7 xx

 AS-i bus configuration

How to modify AS-i slave general parameters: Automatic addressing

At a Glance Each slave on the AS-i bus must be assigned (via configuration) a unique physical
address. This must be the same as the one declared in PL7.

PL7 software offers an automatic slave addressing utility so that an AS-i console
does not have to be used.
The automatic addressing utility, which can be accessed via PL7, is used for:
l replacing a faulty slave (See Automatic replacement of a faulty AS-i slave,
p. 231),
l inserting a new slave (See How to insert a slave device into an existing AS-i
configuration., p. 232).

Note: A new configuration with automatic addressing will not be accepted if one or
more slaves with a 0 address are on the bus. In this case, the Configuration
refused by module message appears.

Procedure The table below shows the procedure for setting the Automatic addressing
parameter.
Step Action
1 Access the AS-i communication module’s configuration screen.
2 Click on the Automatic addressing check box found in the General
parameters zone.
Result: The Automatic addressing utility will be activated (box checked) or
disabled (box not checked).
General parameters Fallback mode on failure
Automatic addressing Fallback: Maintain

Note: By default, the Automatic addressing parameter has been selected in

the configuration screen.

TLX DS 57 PL7 xx 219

AS-i bus configuration

How to modify AS-i slave general parameters: Fallback mode

At a Glance This parameter sets the fallback mode which slave outputs take on while switching
to STOP mode or if there is a PLC fault.
Possible modes are:
l Fallback to 0: AS-i slave outputs which are present on the bus are set to 0 (%Q
objects are not modified),
l Maintain state: AS-i slave outputs remain in the state they were before STOP
mode was engaged.

Note: The fallback mode for slaves which do not have a watchdog (AS-i bus
monitoring function) is not guaranteed in case of an AS-i bus fault, or AS-i power
supply failure. For slaves with a watchdog, the fallback position is preset within the
device.

Procedure The table below shows the procedure for setting the Fallback mode assigned to
slave device outputs.
Step Action
1 Access the AS-i communication module’s configuration screen.
2 Click on the Fallback to 0 / Maintain state check-box found in the General
parameters zone, in the Fallback mode on fault field.
Result: The fallback mode selected will therefore be assigned to the slave
device.
General parameters
Fallback mode on failure
Automatic addressing Fallback: Maintain

220 TLX DS 57 PL7 xx

 Debugging the AS-i bus

12
At a Glance

Subject of this This Chapter describes the Debug aspect of the AS-i bus.
Chapter

What's in this This Chapter contains the following Maps:

Chapter?
Topic Page
Introduction to the Debug function 222
Description of an AS-i module’s debugging screen 223
How to access functionality in the module diagnostics and channel diagnostics 225
for an AS-i device
Displaying the slaves’ status 227
How to access adjustment of an AS-i device’s parameters 228
How to access the AS-i channels’ forcing/unforcing function 229
How to access the SET and RESET commands of the AS-i channels 230
Automatic replacement of a faulty AS-i slave 231
How to insert a slave device into an existing AS-i configuration. 232
How to modify the address of an AS-i device 233

TLX DS 57 PL7 xx 221

Debugging the AS-i bus

Introduction to the Debug function

At a Glance The Debug function is used for each AS-i communication module present in the
application:
l to display the slave state (connection, parameters etc.),
l to access the adjustment function for the selected channel (channel forcing etc.).
The function also accesses module diagnostics in the event of a fault.

Note: This function is only available in online mode.

222 TLX DS 57 PL7 xx

 Debugging the AS-i bus

Description of an AS-i module’s debugging screen

At a Glance The debugging screen dynamically displays the status of the AS-i module and the
devices which are connected to the bus.
It also allows access to the adjustment of the slave parameters and to the channel
commands (forcing the input or output value, Set/Reset of an output, …).

Illustration The following is the layout of the debugging screen:

1 TSX SAY 100 [RACK 0 POSITION 8]
Debug

2 Designation : AS-Interface module Version : 0.0

RUN ERR IO DIAG...

Chan. 0 : Asi

3 Channel 0

As-Interface BUS MAST DIAG...

AS-interface configuration Slave no : 1

Profile Parameters (3-0)
D 1 P XZ-SDA22D32
Projected : 3.0 Value : 1111 Modify PARAM
D 2 P XAL-S2003
Detected 3.0
3 Global unforcing
4 Chan. Asi Symbol State Chan. action
5 0 0
4 1 0 F4 Force to 0 5
D 6 P LF2K09BW#**C %I Not handled
2
3 Not handled F5 Force to 1
7
8 Not handled F6 Unforce
0
9 1 Not handled F7 Set
%Q 0
2
D 10 P XZ-SDA22D32 1 F8 Reset
3

TLX DS 57 PL7 xx 223

Debugging the AS-i bus

Description The following table shows the different elements of the debugging screen and their
functions.
Address Element Function
1 Title bar Indicates the reference of the selected module and its physical position in the
PLC.
2 Module zone Allows the selection of the parameter type:
l Configuration,
l Debugging (diagnostic), only accessible in connected mode.
Displays the status of the module’s lights RUN, ERR, I/O.
Provides direct access to the diagnostics of the module when it is faulty
(signaled by the light built-in to the diagnostics access button DIAG, which turns
red).
3 Channel zone Provides direct access to the diagnostics of one of the module’s channels when
it is at default (signaled by the light built-in to the diagnostics access button
DIAG, which turns red).
4 AS-i configuration zone Displays the slave devices connected to the bus.
5 Slave zone Displays the status of the slave’s channels and gives access to the debugging
functions.

224 TLX DS 57 PL7 xx

 Debugging the AS-i bus

How to access functionality in the module diagnostics and channel diagnostics

for an AS-i device

At a Glance The functions of the module or channel diagnostics display the current errors in
which are classed according to their category:
l internal errors (internal software errors, communication error with the processor,
configuration, parametering or command error),
l external errors(slave device failed, AS-i supply switched off, terminal error,
difference between physical configuration and PL7 configuration),
l other errors (module absent or switched off).

A faulty module becomes apparent when certain lights change to red, such as:
l in the configuration editor at rack level:
l the module position light,
l in the configuration editor at module level:
l the lights RUN, ERR and I/O,
l the light DIAG.

A faulty channel becomes apparent when certain lights change to red, such as:
l in the configuration editor at rack level:
l the module position light,
l in the configuration editor at channel level:
l the light DIAG.

Procedure for The following table presents the procedure to access the screen Module
accessing the diagnostics.
module
Step Action
diagnostics
1 Access the AS-i module’s hardware configuration screen.
2 Click on the button DIAG situated in the module zone.
Result: The list of module errors appears.
Module Diagnostics
Internal faults External faults Other faults

OK

TLX DS 57 PL7 xx 225

Debugging the AS-i bus

Procedure for The following table presents the procedure for accessing the screen Channel
accessing the diagnostics.
channel
Step Action
diagnostics
1 Access the AS-i module’s hardware configuration screen.
2 Click on the button DIAG situated in the channel zone.
Result: The list of channel errors appears.
Channel Diagnostics
Internal faults External faults Other faults

Device error Configuration error

OK

226 TLX DS 57 PL7 xx

 Debugging the AS-i bus

Displaying the slaves’ status

At a Glance The lower part of the communication module’s debugging screen is reserved for
diagnostics of the AS-i bus.
The slave devices connected to the bus are displayed in the AS-i Configuration
zone. On each side of the slave number, two different icons are displayed, indicating
that the slave was specified or detected.

Displaying slave For each slave device, one of the following four cases can occur:
status
Case Illustration Explanation
1 Slave status: The slave P specified in configuration and the detected slave D are
AS-interface configuration
identical.
D 1 P XAL-S2003
2
3
4
5

2 Slave status: The slave P specified in configuration and the detected slave D are
AS-interface configuration
not identical. The slave is declared faulty (1).
D 1 P XAL-S2003
2
3
4
5

3 Slave status: A slave P is specified at configuration but no slave is detected.

AS-interface configuration
The slave is declared faulty (1).
1 P XAL-S2003
2
3
4
5

4 Slave status: An additional slave, not specified at configuration, is connected to

AS-interface configuration
the bus. The slave is declared faulty (1).
D 1 XAL-S2003
2
3
4
5

Key:
(1) When a slave is faulty, the icons situated beside the number as well as the button DIAG turn to red.

Note: The Profile field in the Slave zone of the debugging screen allows you to check if the profiles of the specified
(Projected) slave and the Detected slave are really identical.

TLX DS 57 PL7 xx 227

Debugging the AS-i bus

How to access adjustment of an AS-i device’s parameters

At a Glance The debugging screen of an AS-i module allows, amongst other things, access to
modification of a slave’s parameters.

Procedure The following table shows the procedure for modifying the parameters of a slave
device declared faulty.
Step Action
1 Access the AS-i module’s debugging screen.
2 Select the slave with the error.
Result: In the slave zone of the debugging screen, it is possible to read all the
information relating to the selected slave.
AS-interface configuration Slave no : 1
Profile Parameters (3-0)
D 1 P XZ-SDA22D32 Projected 3.0 Value : 1111 Modify PARAM
D 2 P XAL-S2003
Detected 3.0
3 Global unforcing
4 Chan. action
Chan. Asi Symbol State
5 F4 Force to 0
0 0
D 6 P LF2K09BW#**C %I 1 0
2 Not handled F5 Force to 1
7
3 Not handled F6
8 Unforce
0 Not handled
9 %Q 1 Not handled F7 Set
2 0
D 10 P XZ-SDA22D32 F8 Reset
3 1

3 Click on the button Modif PARAM situated in the slave zone’s Parameters field.
Result: The window Parameter modification appears.
TSX SAY 100 [RACK 0 POSITION 8]
Modify Parameters slave no : 1
Mise au point
Parameters
Désignation : COUPLEUR AS-Interface Version :
0 Unused 2 Unused RUN ERR IO DIAG...
1 Unused 3 Flash On/Off
Voie 0 : Asi
Voie 0
Send Cancel entry Close
BUS As-Interface MAST DIAG...

AS-interface configuration Slave no : 1

Profile Parameters (3-0)
D 1 P XZ-SDA22D32
Projected: 3.0 Value : 1111 Modif PARAM
D 2 P XAL-S2003
Detected: 3.0
3 Global unforcing
4 Chan. AS-i Symbol State Chan. action

4 Modify the required parameters.

5 Click on Send to recognize the new values.

228 TLX DS 57 PL7 xx

 Debugging the AS-i bus

How to access the AS-i channels’ forcing/unforcing function

Introduction This function supports the modification of the state of the channels, which are linked
to the AS-i slave.
The different commands, which are available are:
l for a channel:
l forcing to 0,
l forcing to 1,
l unforcing.
l for all the channels (when at least one channel is forced):
l global unforcing.

Procedure The following table shows the procedure to follow to force or unforce the channels
linked to an AS-i slave.
Step Action for a channel Action for a group of channels
1 Access the AS-i interface card’s debugging screen.
2 Select a slave in the zone AS-i Configuration.
3 Select the channel to modify in the slave zone table. Click on the button Global unforcing found
Result: It is possible to modify the channel using the buttons in the slave zone.
situated in the field Channel action .
Slave no : 1
Profile Parameters (3-0)
Projected 3.0 Value : 1111 Modify PARAM
Detected 3.0
Global unforcing
Chan. action
Chan. Asi Symbol State
0 0 F4 Force to 0
%I 1 00
2 Not handled F5 Force to 1
3 Not handled F6 Unforce
0 Not handled
%Q 1 Not handled F7 Set
2 0
3 1 F8 Reset

4 Select the required function (buttons Force to 0 or Force to 1

in the field Channel Action.

TLX DS 57 PL7 xx 229

Debugging the AS-i bus

How to access the SET and RESET commands of the AS-i channels

At a Glance These commands allow the assignment of the values 0 (RESET) or 1 (SET) to the
channels of an AS-i slave.
The status of the output affected by one of these commands is temporary and can
be modified at any time by the application.

Procedure The following table presents the procedure for assigning a value of 0 or 1 to the
selected AS-i slave’s channels.
Step Action
1 Access the AS-i module’s debugging screen.
2 Select a slave in the zone AS-i Configuration.
3 Select the channel to be modified in the Slave zone table.
Result: It is possible to modify the channel using the buttons situated in the
field Channel action.
Slave no : 1
Profile Parameters (3-0)
Projected 3.0 Value : 1111 Modify PARAM
Detected 3.0
Global unforcing
Chan. action
Chan. Asi Symbol State
0 0 F4 Force to 0
%I 1 00
2 Not handled F5 Force to 1
3 Not handled F6 Unforce
0 Not handled
%Q 1 Not handled F7 Set
2 0
3 1 F8 Reset

4 Select the required function (buttons Set or Reset) in the field Channel action.

230 TLX DS 57 PL7 xx

 Debugging the AS-i bus

Automatic replacement of a faulty AS-i slave

Principle When a slave has been declared faulty, it can be automatically replaced with a slave
of the same type.
This happens without the AS-i bus having to stop, and without any particular
manipulation since the configuration mode Automatic addressing utility is active
(see How to modify AS-i slave general parameters: Automatic addressing, p. 219).
Two options are available:
l The replacement slave is programmed with the same address using the pocket
programmer, and has the same profile as the faulty slave. It will then be
automatically inserted into the list of detected slaves (LDS) and list of active
slaves (LAS).
l the replacement slave is blank (address 0, new slave) and has the same profile
as the faulty slave. It will automatically assume the address of the replaced slave,
and will then be inserted into the list of detected slaves (LDS) and the list of active
slaves (LAS).

TLX DS 57 PL7 xx 231

Debugging the AS-i bus

How to insert a slave device into an existing AS-i configuration.

At a Glance It is possible to insert a device into an existing AS-i configuration without having to
use the pocket programmer.
This operation is possible as soon as:
l the service Automatic addressing of the configuration mode is active (See How
to modify AS-i slave general parameters: Automatic addressing, p. 219),
l a single slave is absent in the physical configuration,
l the slave which is to be inserted is projected in the PL7 configuration,
l the slave has the profile expected by the configuration,
l the slave has the address 0.
Therefore the AS-i interface card will automatically assign to the slave the value
predefined in the configuration.

Procedure The following table presents the procedure for making the automatic insertion of a
new slave effective.
Step Action
1 Add the new slave in the configuration screen in local mode.
2 Do a configuration transfer to the PLC in connected mode.
3 Physically link the new slave with address 0 to the AS-i bus.

Note: It is possible to modify an application by carrying out the above manipulation

as many times as necessary.

232 TLX DS 57 PL7 xx

 Debugging the AS-i bus

How to modify the address of an AS-i device

At a Glance This command allows the movement of the selected AS-i device to another available
address. The address is only modified on the slave and not in configuration. The
physical configuration and the software configuration are different.

Note: This function is only operational for the TSX SAY 100 modules, version PV
higher than 02.

Procedure The following table shows the procedure for modifying the address of an AS-i slave
device.
Step Action
1 Access the TSX SAY 100 module’s debugging screen.
2 Select a slave in the zone AS-i configuration then execute the command Edit
→ Modify the AS-i address.
Result: The selection screen for a new address is displayed.

Modify Address

Current address: 3
Addresses available: 0
2
4
5
6
7
8
9
OK Cancel

3 Select the required address in the list of Available addresses (use the scroll bar
if necessary).
4 Confirm the selection with OK.

TLX DS 57 PL7 xx 233

Debugging the AS-i bus

234 TLX DS 57 PL7 xx

 Bits and words associated with
the AS-i function
13
At a Glance

Subject of this This Chapter introduces the different word and bit objects associated with the AS-i
Chapter function, as well as how to address them.

What's in this This Chapter contains the following Sections:

Chapter?
Section Topic Page
13.1 Addressing objects associated with the AS-i function 236
13.2 Language objects associated with the AS-i function 237

TLX DS 57 PL7 xx 235

Bits and words associated with the AS-i function

13.1 Addressing objects associated with the AS-i

function

Adressing language objects associated with slave devices connected to the AS-
i bus.

At a Glance Addressing bit and word objects associated with application-specific functions is laid
out in the Common Applications part.
This page presents specific details associated with the AS-i function.

Illustration Reminder of the principle of addressing:

% I or Q \ xy.0 \ n • i
Symbol Type of object TSX SAY 100 address Slave no. Bit
rack/module/channel position

Specific values The table below gives specific values to AS-i slave objects.
Element Values Comment
n 0 to 31 Slot 0 cannot be configured.
i 0 to 3 -

236 TLX DS 57 PL7 xx

 Bits and words associated with the AS-i function

13.2 Language objects associated with the AS-i

function

At a Glance

Subject of this This Section introduces the different language objects associated with the AS-i
Section function.

What's in this This Section contains the following Maps:

Section?
Topic Page
Implicit exchange objects associated with the AS-i function 238
Management of exchanges: Module %MWxy.MOD.0:Xj or channel MWxy.0.0 239
:Xj exchanges in progress
Exchange management: Module %MWxy.MOD.1:Xj or channel %MWxy.i.1:Xj 240
report
Explicit exchange objects: General 241
Explicit exchange objects: %MWxy.0.2:Xj to %MWxy.0.23:Xj channel status 242
Explicit exchange object: %MWxy.0.24:Xj channel command 244
Explicit exchange object: %MWxy.0.25 to %MWxy.0.56 parameter adjustment 245
Explicit exchange object: Status %MWxy.MOD.2:Xj 246

TLX DS 57 PL7 xx 237

Bits and words associated with the AS-i function

Implicit exchange objects associated with the AS-i function

At a Glance In each task cycle where the AS-i function has been configured, these objects are
exchanged automatically.

Bit objects The table below shows the different implicit exchange bit objects.
Address Function Meaning when bit is on 1
%Ixy.0.ERR Channel fault bit Indicates a power supply fault or a slave is missing on the AS-i
bus.
%Ixy.MOD.ERR Module fault bit Indicates that the module has a fault.
%Ixy.0 Validity of input Indicates that all inputs are valid
Note: When this bit is on 0, this indicates that at least one input is
invalid: either offline mode, data exchange off mode, or channel
fault.
%Ixy.0.i Reserved -
%I\xy.0\.n.i input channel bit Indicates that the input channel i of device n is activated.
%Q\xy.0\.n.i output channel bit Indicates that the output channel i of device n is activated.
%Qxy.0 Reserved -
%Qxy.0.i Reserved -

Word objects The table below shows the different implicit exchange word objects.
Address Function Meaning for Xj = 1 (j = position of bit in the word)
%IWxy.0 List of faulty slaves j = 0 to 15 -> slaves 0 to 15 respectively are faulty or missing.
%IWxy.0.1 j = 0 to 15 -> slaves 16 to 31 respectively are faulty or missing.
%IWxy.0.2 List of activated slaves (LAS) j = 0 to 15 -> slaves 0 to 15 respectively are activated.
%IWxy.0.3 j = 0 to 15 -> slaves 16 to 31 respectively are activated.

238 TLX DS 57 PL7 xx

 Bits and words associated with the AS-i function

Management of exchanges: Module %MWxy.MOD.0:Xj or channel MWxy.0.0 :Xj

exchanges in progress

At a Glance These word type objects carry information about the module or channel exchanges
in progress.
They are updated automatically by the system.

Description The following table provides the meaning of the different bits of the word
%MWxy.MOD.0.
Address Meaning for Xj =1
%MWxy.MOD.0:X0 Exchange of status words in progress on the module channel.
%MWxy.MOD.0:X1 Exchange of command words in progress on the module
channel.

Description The following table provides the meaning of the different bits of the word
%MWxy.i.0.
Address Meaning for Xj =1
%MWxy.0.0:X0 Exchange of status words in progress on the AS-i channel.
%MWxy.0.0:X1 Exchange of command words in progress on the AS-i channel.

Example The following example shows a possible use of this type of word

(* Request to update the status words on channel 0*)

(*of the module situated in slot 4 of rack 0 *)
(* if there is no exchange in progress on this channel *)
IF NOT %MW4.0:X0 THEN READ_STS %CH4.0;
END_IF;

Note: When the length of the explicit exchange is less than the cycle time of PLC
task, the %MWxy.0:x0 bit never changes to 1.

TLX DS 57 PL7 xx 239

Bits and words associated with the AS-i function

Exchange management: Module %MWxy.MOD.1:Xj or channel %MWxy.i.1:Xj

report

At a Glance These word type objects carry information about the module or channel exchange
reports.
They are updated automatically by the system.

Description The following table provides the meaning of the different bits of the word
%MWxy.MOD.1.
Address Meaning for Xj =1
%MWxy.0.1:X0 Status parameter exchange error on channel 0 of the module.
%MWxy.0.1:X1 Command parameter exchange error on channel 0 of the
module.

Description The following table provides the meaning of the different bits of the word
%MWxy.i.1.
Address Meaning for Xj =1
%MWxy.0.1:X0 Status parameter exchange error on the AS-i channel.
%MWxy.0.1:X1 Command parameter exchange error on the AS-i channel.

Example The following example shows a possible use of this type of word

(* Detection of a status error on the module situated in *)

(* slot 4 of rack 0 *)
IF NOT %MW4.MOD0:X0 THEN READ_STS %CH4.MOD;
END_IF;
IF %MW4.MOD.1:X0 THEN SET %M100;
END_IF;

240 TLX DS 57 PL7 xx

 Bits and words associated with the AS-i function

Explicit exchange objects: General

At a Glance Explicit exchange objects carry information (e.g.: bus operation, status of slaves…)
and the additional commands for advanced programming of the AS-i function.

Note: The configuration constants %KWxy.i.r, which are not documented in this
manual, can only be accessed in read format and correspond to the configuration
parameters input with the help of the Configuration editor.

The explicit exchange objects are exchanged at the request of the program user
using instructions:
l READ_STS (reading of status words),
l WRITE_CMD (writing the command words),
l WRITE_PARAM (writing the adjustment words),
l READ_PARAM (reading the adjustment parameters),
l SAVE_PARAM (saving the adjustment parameters),
l RESTORE_PARAM (restoring the adjustment parameters).

TLX DS 57 PL7 xx 241

Bits and words associated with the AS-i function

Explicit exchange objects: %MWxy.0.2:Xj to %MWxy.0.23:Xj channel status

At a Glance These word type objects provide information on all the slaves present on the AS-i
bus.

Description of The table below provides the meaning of the different bits of the word %MWxy.0.2.
word %MWxy.0.2
Address Function Meaning for Xj = 1
%MWxy.0.2:X0 Standard status Reserved
%MWxy.0.2:X1 One or several slaves are faulty.
%MWxy.0.2:X2 Line error (power supply off or faulty terminal block).
%MWxy.0.2:X3 Physical configuration different from PL7 configuration.
%MWxy.0.2:X4 Internal software error.
%MWxy.0.2:X5 Reserved
%MWxy.0.2:X6 Error communicating with processor
%MWxy.0.2:X7 Command or parameter configuration fault.

Description of The table below provides the meaning of the different bits of the word %MWxy.0.3.
word %MWxy.0.3
Address Function Meaning for Xj = 1
%MWxy.0.3:X0 AS-i specific status Correct configuration.
%MWxy.0.3:X1 Slave 0 present.
%MWxy.0.3:X2 Automatic addressing enabled.
%MWxy.0.3:X3 Reserved
%MWxy.0.3:X4 Reserved
%MWxy.0.3:X5 Reserved
%MWxy.0.3:X6 Faulty AS-i power supply.
%MWxy.0.3:X7 Offline phase active.
%MWxy.0.3:X8 Reserved

242 TLX DS 57 PL7 xx

 Bits and words associated with the AS-i function

Description of The table below provides the meaning of the different bits of words %MWxy.0.4 and
words %MWxy.0.5.
%MWxy.0.4 and
%MWxy.0.5
Address Function Meaning for Xj = 1
%MWxy.0.4:Xj List of detected slaves LDS j = 0 to 15 -> slaves 0 to 15 respectively have been detected.
%MWxy.0.5:Xj j = 0 to 15 -> slaves 16 to 31 respectively have been detected.

Description of The table below provides the meaning of the different bits of words %MWxy.0.6 to
words %MWxy.0.21.
%MWxy.0.6 to
%MWxy.0.21
Address Function Meaning
%MWxy.0.6 to I/O configuration and ID of Words 6 to 21 -> devices respectively 0-1, 2-3, ... 28-29, 30-31.
%MWxy.0.21 all detected slaves Least significant bytes concern slaves with even addresses.
Most significant bytes concern slaves with odd addresses.
For each byte:
bit 0-3 = configuration code for I/O channels,
bit 4-7 = identification (ID) code.

Description of The table below provides the meaning of the word %MWxy.0.22.
word
%MWxy.0.22
Address Function Meaning
%MWxy.0.22 Parameter data of last Contains the reply (value of parameters sent) of the last
parametered slave. parametered slave. This is so that the PL7 can check the slave has
correctly received these values.

Description of The table below provides the meaning of the word %MWxy.0.23.
word
%MWxy.0.23
Address Function Meaning
%MWxy.0.23 Address of last parametered Contains the address of last parametered slave.
slave.

TLX DS 57 PL7 xx 243

Bits and words associated with the AS-i function

Explicit exchange object: %MWxy.0.24:Xj channel command

At a Glance This word type object is used to manage the switch to Offline mode (See AS-I offline
operating mode, p. 252) or Data exchange off mode (See AS-i data exchange off
operating mode, p. 253) of the AS-i master.

Note: Using this object requires a thorough knowledge of AS-i communication

principles.

Description The table below shows the coding of bits 0 to 3 of the word %MWxy.0.24 allowing
access to the different modes.
Bit 3 Bit 2 Bit 1 Bit 0 Function
0 0 0 0 Normal operating mode
0 0 0 1 Activation of offline mode
0 0 1 0 Disabling offline mode
0 0 1 1 No effect

0 1 0 0 Activation of data exchange off mode

1 0 0 0 Disabling data exchange off mode
1 1 1 1 No effect

Note: Offline mode has priority over data exchange off mode.

244 TLX DS 57 PL7 xx

 Bits and words associated with the AS-i function

Explicit exchange object: %MWxy.0.25 to %MWxy.0.56 parameter adjustment

At a Glance These objects are used to manage the parameters of AS-i slave devices.
They can be modified without stopping the AS-i function.

Description The table below shows AS-i channel Adjustment objects.

Address Function Meaning
%MWxy.0.25 Parameter adjustment no meaning
%MWxy.0.26 Contain the parameter values for slaves 1 to 31 respectively.
to
%MWxy.0.56

TLX DS 57 PL7 xx 245

Bits and words associated with the AS-i function

Explicit exchange object: Status %MWxy.MOD.2:Xj

At a Glance This word type object provides information on the state of the module.

Description The table below provides the meaning of the different bits of the word
%MWxy.MOD.2:Xj.
Address Function Meaning for Xj = 1
%MWxy.MOD.2:X0 Standard module status Internal error.
%MWxy.MOD.2:X1 Configuration fault.
%MWxy.MOD.2:X2 Line fault.
%MWxy.MOD.2:X3 Not used.
%MWxy.MOD.2:X4 Not used.
%MWxy.MOD.2:X5 Not used.
%MWxy.MOD.2:X6 Module missing.
%MWxy.MOD.2:X7 Not used.

246 TLX DS 57 PL7 xx

 AS-i operating mode

14
At a Glance

Subject of this This Chapter introduces the different AS-i function operating modes.
Chapter

What's in this This Chapter contains the following Maps:

Chapter?
Topic Page
AS-i operating mode: General 248
AS-i protected mode 250
AS-i wiring test mode 251
AS-I offline operating mode 252
AS-i data exchange off operating mode 253

TLX DS 57 PL7 xx 247

AS-i operation

AS-i operating mode: General

At a Glance The AS-i function allows four operating modes, each one fulfilling particular needs.
These modes are:
l protected mode,
l wiring test mode (can be accessed using the button on the front panel of the
module),
l offline mode,
l data exchange off mode.

Operating mode The figure below shows the general schema of AS-i bus functioning.

Offline mode
PLC
off

Start
AS-i master module

No Activate No Is the master

PLC

wiring test configured?

on

Yes Yes

Offline Wiring test Protected mode

mode

(1)

Slave I/O Automatic AS-i

display (2) bus management

(1) : It is possible to switch from protected mode to offline or data exchange off
modes (see AS-I offline operating mode, p. 252 ou AS-i data exchange off operating
mode, p. 253).
(2) : The module exits the wiring test mode and passes to protected mode if it
receives a configuration.

248 TLX DS 57 PL7 xx

 AS-i operation

Correspondence The table below shows the correspondence between TSX/PMX/PCX 57 PLC
between PLC operating modes and those of the AS-i bus.
operating modes
PLC AS-i bus
and the AS-i bus
Configured mode (1) Protected mode
Non-configured mode (1) Wiring test mode (Configuration mode)

Legend:
(1) These PLC notions (ie. configured, non-configured) concern the
declaration of the module and slave devices in the PL7
application hardware configuration screen.

TLX DS 57 PL7 xx 249

AS-i operation

AS-i protected mode

At a Glance The AS-i protected operating mode is the mode generally used for an application
which is running.
It is assumed that the TSX SAY 100 module is configured in PL7.
This:
l continually checks that the list of detected slaves is the same as the list of
expected slaves.
l monitors the power supply.
In this mode, a slave will only be activated if it has been declared in the configuration
and been detected.

Principle of The schema below show the principle of activating AS-i slaves.
activating a slave
PL7 AS-i Module

List of slaves List of slaves

expected LPS detected LDS

Comparison

List of slaves
activated LAS

250 TLX DS 57 PL7 xx

 AS-i operation

AS-i wiring test mode

At a Glance The Wiring test mode, particularly useful when starting new installations, is used to
display on the front panel of the TSX SAY 100 module:
l expected and detected slaves,
l unexpected and non-detected slaves,
l expected and non-detected slaves, or unexpected and detected slaves.
For each slave present on the bus, this mode can also be used to display the state
of I/O bits.

Note: LDS and LAS lists, as well as slave adjustment parameters, cannot be
accessed in this mode.

Access The wiring test mode is an AS-i function which can be accessed when:
conditions l the TSX SAY 100 module is in non-configured mode.
This mode is obtained when:
l the TSX SAY 100 module has not been declared in the application,
l the PLC processor is missing.
l each device has a unique address,
l 0 address is not used.

TLX DS 57 PL7 xx 251

AS-i operation

AS-I offline operating mode

At a Glance The AS-i offline mode is an advanced operating mode which can be used in
debugging or maintenance.

Note: To use it, you must be thoroughly familiar with AS-i communication.

Principle When offline mode is engaged, the module first resets all the present slaves to zero
and stops exchanges on the bus.
During offline mode, the I/O image in the module is frozen in the state that is was in
when the offline mode started.
On module output, if the list of present slaves (LPS) is the same as the list of
detected slaves (LDS), the system restarts. If this is not the case, a fault is generated
and you must refer to diagnostics mode or go back to the configuration.

Procedure The offline operating mode can be accessed either:

l from PL7 application software by acting on bits 0 and 1 of the word %MWxy.0.24,
l automatically when an AS-i power supply fault is detected.
Remember: Bit 7 of word %MWxy.0.24 set on 1 indicates that the AS-i bus is in
offline mode.

252 TLX DS 57 PL7 xx

 AS-i operation

AS-i data exchange off operating mode

At a Glance The AS-i data exchange off mode is an advanced operating mode which can be
used in debugging or maintenance.

Note: To use it, you must be thoroughly familiar with AS-i communication.

Principle When the offline data exchange mode is engaged, exchanges on the bus continue
to function, but data is not longer refreshed.

Procedure The data exchange off operating mode can be accessed from PL7 application
software by acting on bits 2 and 3 of the %MWxy.0.3 word.

Remember: Bit 8 of word %MWxy.0.3 set on 1 indicates that the AS-i bus is in data
exchange off mode.

TLX DS 57 PL7 xx 253

AS-i operation

254 TLX DS 57 PL7 xx

 AS-i performance

15
AS-i bus performance

At a Glance The AS-i bus is independently managed by the master. This exchanges data on
each cycle with each slave device configured on the bus (in ascending order of slave
address number).

AS-i scanning t scanning time represents the exchange time between the master and n slaves (31
time maximum).
Either:
l t = 156 micro seconds x (n+2), if n < 31,
l t = 156 micro seconds x (n+1), if n = 31.
Thus the scanning time cannot exceed 5 ms.

AS-i response T response time represents the AS-i cycle time.

time This includes:
l the bus scanning time,
l the update of the AS-I module internal memory,
l the PLC cycle.

Example The table below shows three examples of T response time for a PLC task lasting 10
ms, 30 ms, and 60 ms.
This T time is for a bus loaded with 31 slaves operating normally with no link faults.
PLC task Typical response time Maximum response time
10 ms 35 ms 56 ms
30 ms 65 ms 96 ms
60 ms 110 ms 156 ms

TLX DS 57 PL7 xx 255

AS-i performance

256 TLX DS 57 PL7 xx

 DFB for AS-i Security Monitor

16
AS-i security monitor DFBs

At a Glance The DFBs for the AS-i bus security monitor are described in the section on AS-i V2
(See DFB for AS-i Security Monitor, p. 327).

TLX DS 57 PL7 xx 257

DFB AS-i

258 TLX DS 57 PL7 xx

 AS-i V2 bus

IV
At a Glance

Aim of this Part This part presents the AS-i V2 bus on PLC TSX/PCX 57 and describes its implemen-
tation with the software PL7 Junior and Pro.

What's in this This Part contains the following Chapters:

part?
Chapter Chaptername Page
17 General introduction to the AS-i V2 Bus 261
18 AS-i V2 bus configuration 271
19 Debugging the AS-i V2 bus 287
20 Bits and words associated with the AS-i V2 function 303
21 AS-i V2 operating mode 319
22 AS-i V2 performance 325
23 DFB for AS-i Security Monitor 327

TLX DS 57 PL7 xx 259

AS-i V2 bus

260 TLX DS 57 PL7 xx

 General introduction to the AS-i
V2 Bus
17
At a Glance

Aim of this This chapter introduces the AS-i V2 bus on the Premium/Atrium PLC, and describes
chapter how to access the different application editors.

What's in this This Chapter contains the following Maps:

Chapter?
Topic Page
Introduction to the AS-i V2 Bus 262
Architecture of TSX SAY 1000 Module 264
Structure of a Standard Address AS-i 266
Structure of a Standard Address AS-i slave 267
How to Declare an AS-i Communication Module in the PLC Rack 269
How to Access Configuration of the AS-i V2 Bus 270

TLX DS 57 PL7 xx 261

AS-i V2 Bus

Introduction to the AS-i V2 Bus

Introduction The AS-i Bus (Actuator Sensor-Interface) allows the interconnection on a single
cable of sensor devices/actuators at the lowest level of automation.
These sensors/actuators will be defined in the documentation as slave devices.

To implement the AS-i application you need to define the physical context of the
application into which it will integrated (rack, power supply, processor, modules, AS-
i slave devices connected to the bus) then ensure its software implementation.

This second aspect will be carried out from the different PL7 editors:
l either in local mode,
l or in connected mode; in this case the modification is limited to certain
parameters.

AS-i V2 Bus The coupler TSX SAY 1000 integrates the functions AS-i V2.
The AS-i bus then allows:
l up to 62 standard and/or extended address slaves,
l up to 248 inputs and 186 outputs,
l up to 124 analog values integrated in the master AS-i,
l a cycle time of 10ms maximum.

262 TLX DS 57 PL7 xx

 AS-i V2 Bus

Implementation The following table shows the different implementation phases of the AS-i bus.
Mode Phase Description
Local Declaration of module Selection of slot for TSX SAY 1000 module in the rack.
Declaration of slave devices Selection for each device:
l of its slot number on the bus,
l of the type of standard or extended address slave

Configuration of the module Input of the configuration parameters.

channel (See AS-i V2 bus
configuration, p. 271)
Confirmation of Confirmation of module level.
configuration parameters
(See Confirming the
configuration of a module.,
p. 66)
Global confirmation of the Confirmation of application level.
application (See Globally
reconfiguring an
application., p. 67)
Local or Symbolization Symbolization of the variables associated with the slave devices.
connected Programming Programming the functions carried out using the AS-i V2 bus.
Connected Transfer Transfer of the application to the PLC.
Debugging Debugging the application using:
l the debugging help screens which display the slave
connections, their parameters, etc.
l diagnostic screens allowing identification of errors.

Local or Documentation Printing the different information relating to the application.

connected

Note: The order defined above is given for information only; the PL7 software
allows you to use the editors interactively in the required order (however you
cannot use the data or program editor without having previously configured the
module and the slave devices.)

TLX DS 57 PL7 xx 263

AS-i V2 Bus

Architecture of TSX SAY 1000 Module

At a Glance The TSX SAY 1000 module operates according to the master/slave mode. The
master only controls exchanges on the bus.
The AS-i standard sets several operating levels offered by the master:
l Profile M0 and M0e - Minimum Master: the master only puts forward the
configuration of slaves connected to the bus on power-up, and only input/output
exchanges.
l Profile M1 and M1e - Full Master: this profile covers all the operating functions set
by the AS-i standard,
l Profile M2 and M2e - Reduced Master: this profile corresponds to profile M0
operating functions with a slave-parametering option.
The master profiles with an "e" support extended profiles.

Note: The TSX SAY 1000 module has an M2e profile, with the additional option of
reading slave and slave channel diagnostics information.

The module includes data fields which are used to manage the lists of slaves and I/
O data images. This information is stored in a volatile memory.

Illustration of the The figure below shows the TSX SAY 1000 module architecture.
architecture TSX SAY 1000

1 I/O data

Parameters
2
current AS-i bus

3 Configuration/
Identification

4 LDS
5 LAS
6 LPS
7 LPF

264 TLX DS 57 PL7 xx

 AS-i V2 Bus

Description of The table below shows the different elements that make up the architecture of the
constituent TSX SAY 1000 module.
elements
Number Element Description
1 I/O data Images of 248 inputs and 186 outputs of AS-i V2 bus.
2 Current parameters Image of parameters of all slaves.
3 Configuration/ This field contains all the I/O codes and identification
Identification codes for all the detected slaves.
4 LDS List of all the slaves detected on the bus.
5 LAS List of active slaves on the bus.
6 LPS List of slaves expected on the bus and configured by
PL7.
7 LPF List of slaves having a device fault.

TLX DS 57 PL7 xx 265

AS-i V2 Bus

Structure of a Standard Address AS-i

At a Glance The AS-i V2 bus is used to interconnect 31 standard address devices.

The standard address slaves each have:
l 4 input bits,
l 4 output bits,
l 4 parametering bits.
The AS-i V2 bus can manage a maximum of 124 standard address slave Inputs and
124 Outputs.
Each slave has its own address and a profile (defines variables exchange).

Structure The figure below shows the structure of a standard address slave.
illustration AS-i slave
D3
1 I/O data
D0

P3
2 Parameters
P0

Configuration/
3 Identification AS-i bus

4 Address

Description of The table below shows the different elements that make up the structure of a
constituent standard address slave.
elements
Number Element Description
1 Input/output Input data is stored by the slave and made available for the AS-i
data master.
Output data is updated by the master module.
2 Parameters The parameters are used to control and switch internal operating
modes to the sensor or the actuator.
3 Configuration/ This field contains:
Identification l the code which corresponds to I/O configuration,
l the slave identification codes (ID, ID1, ID2).

4 Address Physical address of slave.

Note: The operating parameters, address, configuration and identification data are saved in
a non-volatile memory.

266 TLX DS 57 PL7 xx

 AS-i V2 Bus

Structure of a Standard Address AS-i slave

At a Glance The extended AS-i V2 bus is used to interconnect 62 extended address devices.
The extended address slaves each have:
l 4 input bits,
l 3 output bits,
l 3 parametering bits.
The AS-i V2 bus can manage a maximum of 248 Inputs and 186 Outputs from
extended address slaves.
Each slave has its own address, profile and sub-profile (defines variables
exchange).

Structure The figure below shows the structure of an extended address slave.
illustration
AS-i slave
Input Bit Only
(D3)
1 I/O data
D0

2 Parameters P2
P0

Configuration/
3 Identification AS-i bus

4 Address

TLX DS 57 PL7 xx 267

AS-i V2 Bus

Description of The table below shows the different elements that make up the structure of an
constituent extended address slave.
elements
Number Element Description
1 Input/output Input data is stored by the slave and made available for the AS-i
data master.
Output data is updated by the master module.
2 Parameters The parameters are used to control and switch internal operating
modes to the sensor or the actuator.
3 Configuration/ This field contains:
Identification l the code which corresponds to I/O configuration,
l the slave identification (ID) code,
l the slave identification codes (ID1 and ID2).

4 Address Physical address of slave.

Note: The operating parameters, address, configuration and identification data are saved in
a non-volatile memory.

268 TLX DS 57 PL7 xx

 AS-i V2 Bus

How to Declare an AS-i Communication Module in the PLC Rack

Procedure This operation allows you to declare an AS-i communication module in the rack of
the PLC TSX 57 using the software.
Step Action
1 Double click on the required position in the rack displayed.
Result: The dialog box Add a module appears:
Add a module
Family: Module:
Analog 1.5 TSX SAY1000 AS-Interface MODULE OK
Communication 1.5 TSX SCY 21600 PCMCIA HOST MODULE
Upcounting 1.5 TSX SCY 21601 PCMCIA HOST MODULE Cancel
Movement 1.5
Weighing 1.7
Alternating 1.5

2 Select the choice Communication in the Family field.

3 Select in the Module field the reference of the module.
4 Confirm the selection with OK.
Result: The module is declared in its slot; this turns yellow and contains the
module reference.
Configuration
XMWI
TSX 57303 V5.0... XT I..

0 1 2 3 4 5 6
P T S
S S A
Y X Y
0 2 5 1
6 7 0
0 1 0
0 0 0
3

Note: The maximum number of TSX SAY 1000 modules which can be installed
in a configuration is:

l 2 modules, with a TSX/PMX/PCX 57-1• processor,

l 4 modules, with a TSX/PMX/PCX 57-2• processor,
l 8 modules, with a TSX/PMX/PCX 57-3•, TSX/PMX 57-4• processor.

TLX DS 57 PL7 xx 269

AS-i V2 Bus

How to Access Configuration of the AS-i V2 Bus

Procedure This operation allows access to the configuration of an AS-i communication module.
Step Action
1 Access the Hardware configuration screen
Result: The rack’s hardware configuration screen appears.
Configuration
XMWI
TSX 57303 V5.0... XT I..

0 1 2 3 4 5 6
P T S
S S A
Y X Y
0
2 5
6 7 1
0 1 0
0 0 0
3 0

2 Double click on the position of the communication module or select the module
and then carry out the command Service → Open the module.
Illustration: Example of a configuration screen with 2 configured slaves
TSX SAY 1000 [RACK 0 POSITION 1]
Configuration
Designation: AS-interface V2 Module
Channel 0:
Channel 0
AS-interface V2 Bus MAST
AS-interface V2 configuration Slave 2B
Automatic addressing Specifications
Std/A Slaves /B Slaves Profile: IO 0 ID a ID2 0 ID1 0
0 Comment 4 input extended addr. Module
XVBC21A P 1 Parameters
2 P ASIME4IE
0 Unused 2 Unused
3
4 1 Unused 0
5
6 Input / Output Symbols
7 Input Number Symbol
8 1 %I\1.0\102.0
9 2 %I\1.0\102.1
10 3 %I\1.0\102.2
11 4 %I\1.0\102.3
12 Output Number Symbol
13 Not handled
1 Not handled
14 Not handled
2 Not handled
3 Not handled Not handled
4 Not handled Not handled

270 TLX DS 57 PL7 xx

 AS-i V2 bus configuration

18
At a Glance

Subject of this This Chapter describes the Configuration aspect for installing the AS-i V2 bus.
Chapter

What's in this This Chapter contains the following Maps:

Chapter?
Topic Page
Description of an AS-i V2 communication module’s configuration screen 272
How to define a slave device on the AS-i V2 bus 274
How to modify the AS-i V2 Bus software configuration 277
How to access the description of an AS-i V2 slave 278
How to define a new slave profile in the standard AS-i V2 catalog 280
How to modify the general parameters of an AS-i V2 slave: Automatic 282
addressing
How to modify the parameters of an AS-i V2 slave 283
How to modify the parameters of an analog AS-i V2 slave 284
How to Modify the Parameters of an AS-i V2 Slave with Combined Parameters 285
AS-i V2 security device issues 286

TLX DS 57 PL7 xx 271

AS-i V2 bus configuration

Description of an AS-i V2 communication module’s configuration screen

At a Glance The configuration screen of the AS-i V2 module gives access to the parameters
associated with the module and the slave devices.

Illustration This screen allows the display and modification of the parameters in local mode, as
well as Debugging in connected mode.
1 TSX SAY 1000 [RACK 0 POSITION 1]
Configuration
2 Designation: AS-interface V2 Module

Channel 0
3
AS-interface V2 Bus MAST
AS-interface V2 configuration Slave 2B
Automatic addressing Specifications
Std/A Slaves /B Slaves Profile: IO 0 ID a ID2 0 ID1 0
5
0 Comment 4 input extended addr. Module
XVBC21A P 1 Parameters
2 P ASIME4IE
0 Unused 2 Unused
3 6
4 4 1 Unused 0
5
6 Input / Output Symbols
7 Input Number Symbol
8 1 %I\1.0\102.0
9 2 %I\1.0\102.1
10 3 %I\1.0\102.2
11 4 %I\1.0\102.3 7
12 Output Number Symbol
13
1 Not handled Not handled
14
2 Not handled Not handled
3 Not handled Not handled
4 Not handled Not handled

272 TLX DS 57 PL7 xx

 AS-i V2 bus configuration

Description The following table shows the different elements of the configuration screen and
their functions.
Number Element Function
Module
1 Title bar Indicates the reference of the selected module and its physical position in the rack.
2 Command Allows the selection of the parameter type:
l Configuration,
l Debugging (diagnostics), only accessible in connected mode.
Displays the designation of the selected module.
Display of this zone is optional. Selection is made using the command View →
Module zone.
AS-i V2 bus
3 Channel 0 Allows selection of the task in which the information from the AS-i communication
channel will be scanned:
l MAST Task,
l FAST Task.
Display of this zone is optional. The choice is made using the command View →
Channel zone.
4 AS-interface V2 Allows:
configuration l Viewing standard and extended address setting slave devices connected to the
bus,
l definition of a new configuration (adding, modifying or detecting slave devices).
l Selecting automatic addressing mode

Slave
5 Specifications Allows viewing of:
l Slave profile
l Comments on the selected slave

6 Parameters Allows display and selection of parameters applied to the selected slave. The
parameters displayed differ according to the type of slave selected.
For example:
l Watchdog
l Fallback Position

7 Input / Output Allows data associated with the selected slave to be displayed, such as:
Symbols l its AS-i symbol (the symbols are defined with the help of the variables editor),
l Its label (or address) which can be used in the program

TLX DS 57 PL7 xx 273

AS-i V2 bus configuration

How to define a slave device on the AS-i V2 bus

At a Glance PL7 software offers a catalog of Schneider products which groups together all of the
AS-i V2 slaves that are available. This catalog is currently structured around the
following product families:

l Keyboards
l Illuminated columns
l Command and signaling
l AS-i modules and interfaces
l Motor-starters
l Inductive sensors
l Phototronic sensors
l Private family
l IP20 linkage interfaces
l Position switches
l Analog modules
l Security modules
l Logical modules
l IP67 Distributors
l Variable speed controllers

Selecting Private family enables the user to enhance the PL7 catalog with specific
AS-i products via a programming terminal.

Note: An application using AS-i products from the Private Family catalog is
always linked to the usage of the same Private Family on the workstation upon
which the catalog was created.

274 TLX DS 57 PL7 xx

 AS-i V2 bus configuration

Procedure This operation enables the declaration of a slave device on the AS-i V2 bus.
Step Action
1 Access the AS-i module’s hardware configuration screen.
2 In the AS-interface V2 configuration field, double click in the cell
corresponding to the new slave’s host slot number (1A to 31A or 1B to 31B) or
select this cell and then carry out the Edit command → Add a slave.
Result: The Associate a profile screen appears.
Associate a profile
Families of AS-interface profiles
Code ASI Family Name
5 Keyboards
6 Illuminated columns
7 Command and signaling
8 AS-i Modules and Interfaces
4 Motor-starters

Catalog of AS-interface profiles Consult

ASI Name @ Comment Add

Modify

Delete

Detail
Ok Cancel

3 In the ASI Family Name field select the required family.

Result: The Profile catalogue associated with the selected family appears.
Associate a profile
Families of AS-interface profiles
Code ASI Family Name
15 12345678 Analog Modules
16 Security modules
14 Logical modules
10 IP67 Distributors
13 Variable speed controllers

ASI Catalog: IP67 Distributors Consult

ASI Name @ Comment Add
0.0.F.F XZ-SDA40D2 std 4 E 100 mA User Module
0.0.F.F XZ-SDA40D3 std 4 I 200 mA User Module Modify
0.A.0.0 ASIME4IE A/B 4 input extended addr. Module
0.A.0.0 ASIMM04IE A/B Mini mod. 4 input extended addr
Delete
3,0.F.F XZ-SDA22D11 std 2I/2O rel. M12 User Module

Detail
Ok Cancel

Column Legend @ :
std: standard address slave (for configuration in column /A).
A/B: extended address slave (for configuration in columns /A or /B).

TLX DS 57 PL7 xx 275

AS-i V2 bus configuration

Step Action
4 In the Profile catalogue select the required device.
5 Confirm the selection with OK.
Result: The slave device is declared in its slot, the connected device reference
appears opposite the slave number.
AS-interface V2 configuration
Automatic addressing
Std/A Slaves /B Slaves
0
1 P ASIME4IE
2
3
4
5
6
7
8
9
10
11
12
13
14

6 To connect other slave devices to the AS-i V2 bus, repeat the procedure from
step 2.

Configuration The configuration rules for the slaves are as follows:

Rules l The /B Slaves column can only support extended address slaves, and this on
condition that the std /A Slaves cell immediately to its left is not occupied by a
standard address slave.
l The std /A Slaves column can support extended address slaves. This column
can also support standard address slaves, as long as the /B Slaves cell
immediately to its right is not occupied by an extended address slave.
A maximum of 62 extended or 31 standard address slaves can be configured.
A validity check is carried out during slave entry. A message like the one below will
be displayed if this is not possible:
PL7Pro

Confirmation Impossible:
One extended address slave
is already present on /B.

OK

Note: An analog slave must be configured as a standard address slave (in the /A
Slaves column) and prohibits the use of the slot immediately to its right (in the /B
Slaves column).

276 TLX DS 57 PL7 xx

 AS-i V2 bus configuration

How to modify the AS-i V2 Bus software configuration

Introduction From the AS-i V2 module’s configuration screen, PL7 software offers a group of
functions which allow you to easily modify, in local mode, the software configuration
of the AS-i V2 bus.

Note: standard Windows keyboard shortcut keys (Del, Ctrl-X, Ctrl-C, Ctrl-V) are
also available for the following operations:

Procedure for This operation allows the deletion of a slave declared on an AS-i Bus.
deleting a slave
Step Action
1 Select the slave to be deleted.
2 Select the command Edit → Delete an AS-i slave.

Procedure for This operation allows a slave declared on an AS-i V2 Bus to be moved.
moving a slave
Step Action
1 Select the slave to be moved.
2 Select the command Edit → Cut an AS-i slave.
3 Select the new required slot.
4 Select the command Edit → Paste an AS-i slave.

Procedure for This operation allows the copying of a slave declared on an AS-i V2 Bus.
copying a slave
Step Action
1 Select the slave to be copied.
2 Select the command Edit → Copy an AS-i slave.
3 Select the slot of the new slave.
4 Select the command Edit → Paste an AS-i slave.

TLX DS 57 PL7 xx 277

AS-i V2 bus configuration

How to access the description of an AS-i V2 slave

At a Glance The PL7 software allows access to all the information relating to an AS-i V2 device
such as:
l the definition of a profile,
l the details of a profile.

Definition of a A profile is defined by:

profile l its name,
l a comment (optional),
l identifiers (IO, ID, ID1, ID2),
l a number of inputs and/or outputs,
l operation parameters.

Note: profile description for Private Family products is not accessible.

Details of a The Detail function allows access, for a given slave, to all the information presented
profile in the catalog file.
Details of a profile

r4e_01
Reference: XZ-SDA10D2
User module active
Allows the linking of 4 sensors.
PNP type input.
Maximum current used by the 4 sensors = 100mA
Version:
Supplier: Telemechanics
AS-i profile: 0.0
I/O Configuration:
Inputs:
PNP type
D0: I-1 Signal sensor 1 (pins 4-2)
D1: I-2 Signal sensor 2 (pins 4-2)
D2: I-3 Signal sensor 3 (pins 4-2)
D3: I-4 Signal sensor 4 (pins 4-2)

OK

278 TLX DS 57 PL7 xx

 AS-i V2 bus configuration

Procedure for The following table shows the procedure for displaying the characteristics of a slave
accessing device.
information on a
Step Action
profile
1 Access the AS-i V2 module’s hardware configuration screen.
2 Double click on the required slave.
Result: The Associate a profile window displays and highlights the device in
question.
3 Select the profile family and the reference for the desired slave.
4 Click on the button:
l View to access definition information,
l Detail to access all the information.

TLX DS 57 PL7 xx 279

AS-i V2 bus configuration

How to define a new slave profile in the standard AS-i V2 catalog

At a Glance PL7 software enables the user to define a non-specified slave profile in the standard
catalog.
Defined in this way, the new profile is added to the catalog in Private family.
This profile can then be used as a standard catalog profile.

Procedure The following table presents the procedure for defining a slave profile, which is not
provided in the standard catalog.
Step Action
1 Access the AS-i module’s hardware configuration screen.
2 Double click in a slave’s host cell (1 to 31 /A or /B).
Result: The Associate a profile screen appears.
3 Select Private family in the Family name field.
Result: The Profile catalog associated with the selected family appears.

Associate a profile
Families of AS-interface profiles
Code ASI Family Name
9 Phototronic sensors
1 Private family
12 Connection interfaces IP20
3 Position switches
15 12345678 Analog Modules

ASI Catalog: Private family Consult

ASI Name @ Comment Add
1.1.F.1 Sens 1I 4O std Special Sensor
1.A.1.1 Test A/B Test Modify

Delete

Detail
Ok Cancel

4 Click on the Add button.

A new AS-interface profile definition window opens.
5 Enter:
l the name of the new profile,
l a comment (optional).

6 Select:
l the IO code (corresponds to the input/output configuration),
l the ID code (identifier) (plus ID1 and for an extended type),

280 TLX DS 57 PL7 xx

 AS-i V2 bus configuration

Step Action
7 For each parameter define:
l the system’s acknowledgement (box checked),
l a label (optional).

8 Confirm the introduction of a new profile using Confirm.

TLX DS 57 PL7 xx 281

AS-i V2 bus configuration

How to modify the general parameters of an AS-i V2 slave: Automatic

addressing

At a Glance Each slave on the AS-i bus must be assigned (via configuration) a unique physical
address. This must be the same as the one declared in PL7.

PL7 software offers an automatic slave addressing utility so that an AS-i console
does not have to be used.
The automatic addressing utility, which can be accessed via PL7, is used for:
l replacing a faulty slave (See Automatic replacement of a faulty AS-i V2 slave,
p. 300),
l inserting a new slave (See How to insert a slave device into an existing AS-i V2
configuration., p. 301).

Note: A new configuration with automatic addressing will not be accepted if one or
more slaves with a 0 address are on the bus. In this case, the Configuration
refused by module message appears.

Procedure The table below shows the procedure for setting the Automatic addressing
parameter.
Step Action
1 Access the AS-i V2 communication module’s configuration screen.
2 Click on the Automatic addressing check box found in the AS-interface V2
configuration zone.
Result: The Automatic addressing utility will be activated (box checked) or
disabled (box not checked.
AS-interface V2 configuration
Automatic addressing
Std/A Slaves /B Slaves
0
1 P ASIME4IE

Note: By default, the Automatic addressing parameter is selected in the

configuration screen.

282 TLX DS 57 PL7 xx

 AS-i V2 bus configuration

How to modify the parameters of an AS-i V2 slave

At a Glance The Parameters zone of the configuration screen enables the user to choose
whether or not to activate the parameters of certain slaves.
The parameters displayed differ according to the slave in use, please refer to slave
documentation for further details.

Example of On certain slaves, the following may be activated:

parameters
l The internal watchdog, upon a communication stop with the (TSX SAY 1000)
bus master.
l The output fallback position pre-programmed in the slave.
This parameter activates the slaves' output fallback when changing to STOP or
when the PLC is faulty.
The fallback position is pre-defined in the slave device. Possible modes are:
l Fallback to 0: the outputs ofAS-i slaves present on the bus are set to 0 status.
l Maintain status: AS-i slave outputs remain in the status they were in before
STOP mode was engaged.

Procedure The table below shows the procedure for selecting the Watchdog and the Fallback
Position assigned to the output of a slave supporting these parameters.
Step Action
1 Access the AS-i V2 communication module’s configuration screen.
2 Select the slave whose parameters are to be modified.
3 Click on the Watchdog checkbox and/or Fallback Position checkbox located
in the Parameters zone.
Result: The watchdog and/or fallback position will be activated in the slave
device.
Parameters
0 Watchdog 2 Unused

1 Fallback 3 Unused

TLX DS 57 PL7 xx 283

AS-i V2 bus configuration

How to modify the parameters of an analog AS-i V2 slave

At a Glance The Parameters zone of the configuration screen enables the user to choose
whether to activate or deactivate pre-defined parameters in an analog slave. For
example:

l Filter Selection, which activates la rejection of 50/60 Hz on inputs.

l Channel 2 Enabling, which enables the second analog channel.
l Peri Flt Enabling, which enables peripheral faults to be displayed.
The parameters displayed differ according to the slave in use, please refer to slave
documentation for further details.

Note: Module TSX SAY 1000 can only manage 7.3 type analog slaves.

Procedure The following table shows the procedure for defining the parameters of an analog
slave device.
Step Action
1 Access the AS-i V2 communication module’s configuration screen.
2 Select the slave whose parameters are to be modified.
3 Click on the Filter Selection and/or Channel 2 Enabling and/or Peri Flt
Enabling checkboxes located in the parameters Parameters zone.
Result: The parameters checked will be activated in the slave device.
Parameters
0 Filter Selection 2 Peri. Flt. Conf

1 Conf. Channel 2 3 Unused

284 TLX DS 57 PL7 xx

 AS-i V2 bus configuration

How to Modify the Parameters of an AS-i V2 Slave with Combined Parameters

At a Glance Some AS-i V2 slaves have several pre-defined combinations of parameters. The
user can then choose the combination of parameters required from a list.
The Parameters zone of the configuration screen allows the user to choose this
combination of parameters (called Page).

As the parameters differ according to the slave in use, please refer to slave
documentation for further details.

Procedure The table below shows the procedure for selecting the parameters of the slave
devices with combined parameters.
Step Action
1 Access the configuration screen of the AS-i V2 communication module.
2 Select the slave whose parameters are to be modified.
3 Select a combination of parameters (page) in the List of values zone.
Result: The list of parameters selected will be activated in the slave device.

Parameters

List of Values Pages 112 to 127

TLX DS 57 PL7 xx 285

AS-i V2 bus configuration

AS-i V2 security device issues

At a Glance The TSX SAY 1000 module supports AS-i security devices on its bus. The
addresses of these devices can be configured by PL7 software.

The AS-i security product consists of a Monitor and one or more slaves. The bus
master sees these devices as standard address slaves, but with a special profile.
There is a Security Module family on the Configuration Screen (See How to define
a slave device on the AS-i V2 bus, p. 274).

Precautions of Input/Output objects from these devices should not be used in the application
Use program, as their values are not significant.
The diagnostics information on the Security Monitor may, however, be utilized by the
DFB supplied with this product.

286 TLX DS 57 PL7 xx

 Debugging the AS-i V2 bus

19
At a Glance

Aim of this This Chapter describes the Debug aspect of the AS-i V2 bus.
chapter

What's in this This Chapter contains the following Maps:

Chapter?
Topic Page
Introduction to the Debug function 288
Description of an AS-i V2 module's debugging screen 289
How to access module- and channel-diagnostics functions on an AS-i V2 291
device.
Displaying the slaves' status 293
How to access adjustment of an AS-i V2 device's parameters 295
How to access the AS-i V2 digital channels' forcing/unforcing function 297
How to access the SET and RESET commands on AS-i V2 digital channels 298
How to modify the value of an analog channel 299
Automatic replacement of a faulty AS-i V2 slave 300
How to insert a slave device into an existing AS-i V2 configuration. 301
How to modify the address of an AS-i V2 device 302

TLX DS 57 PL7 xx 287

Debugging the AS-i V2 bus

Introduction to the Debug function

Introduction The Debug function allows each AS-i V2 communication module present in the
application:
l to display slave status (connection, parameters etc.),
l to access the adjustment function for the selected channel (channel forcing etc.).
The function also accesses module diagnostics in the event of a fault.

Note: This function is only available in online mode.

Rack Display It is also possible to access As-i V2 module information from the Rack Display page
of a Web FactoryCast server embedded in a TSX ETY 4102 or TSX ETY 5102
module. These web pages can be accessed via an Internet browser.
Please refer to the TLX DS COM PL7 Manual and the FactoryCast User's Manual
for more information.

288 TLX DS 57 PL7 xx

 Debugging the AS-i V2 bus

Description of an AS-i V2 module's debugging screen

At a Glance The debugging screen dynamically displays the status of the AS-i V2 module and
the devices which are connected to the bus.
It also allows access to the adjustment of the slave parameters and to the channel
commands (forcing the input or output value, Set/Reset of an output, etc.).

Illustration This is the layout of the debugging screen:

1
TSX SAY 1000 [RACK 0 POSITION 5]
Debugging
Designation: AS-Interface V2 MODULE Version: 0.1
2
RUN ERR IO DIAG...

Channel 0: Maestro
3 Channel
AS-interface V2 BUS MAST DIAG...
AS-interface V2 configuration Slave 21A
Automatic addressing Profile
Std/A Slaves /B Slaves Projected: IO 7 ID 3 ID2 d ID1 f
14 Ext I/O Module Detected: IO 7 ID 3 ID2 d ID1 f
XZ-SDA22D12 15 Parameters (3-0)
Ext I/O Module 16 Ext I/O Module
XZ-SDA22D12 17 Value: 0111 Modif PARAM
XZ-SDA22D12 18
4 XZ-SDA22D12 19 %I Ch. Asi Symbol Status Action channel 0 5
XZ-SDA22D12 20 0 0
Analog B&W 2IN 21 Change value
1 0
Analog B&W 2IN 22 2 0
Ext I/O Module 23 Ext I/O Module
3 0
XZ-SDA22D12 24
0 10000
Ext I/O Module 25 Ext I/O Module
1 0
XZ-SDA22D12 26 %Q
2 0
XZ-SDA22D12 27
3 0
Format: Decimal Global unforcing

TLX DS 57 PL7 xx 289

Debugging the AS-i V2 bus

Description The following table shows the different elements of the debugging screen and their
functions.
Number Element Function
1 Title bar Indicates the reference of the selected module and its physical position in the
PLC.
2 Module zone Allows parameter type to be selected:
l Configuration,
l Debugging (diagnostics), only accessible in connected mode.
Displays the status of the module’s RUN, ERR, I/O LEDs.
Provides direct access to the diagnostics of the module when it is faulty
(signaled by the DIAG LED on the diagnostics access button , which turns red).
3 Channel zone Provides direct access to the diagnostics of one of the module’s channels when
it is faulty (signaled by the DIAG LED on the diagnostics access button , which
turns red).
4 Configuration Zone Displays the slave devices connected to the bus.
AS-interface V2
5 Slave zone Displays the status of the slave’s channels and gives access to the debugging
functions.

290 TLX DS 57 PL7 xx

 Debugging the AS-i V2 bus

How to access module- and channel-diagnostics functions on an AS-i V2 device.

At a Glance The functions of the module or channel diagnostics display the current errors in
which are classed according to category:
l internal errors (internal software errors, communication error with the processor,
configuration, parameter or command error),
l external errors(slave device failed, AS-i power supply switched off, terminal error,
difference between physical configuration and PL7 configuration),
l other errors (module absent or switched off).

A faulty module becomes apparent when certain LEDs change to red, e.g.:
l in the configuration editor at rack level:
l the module position LED,
l in the configuration editor at module level:
l the RUN, ERR and I/OLEDs,
l the DIAG LED.

A faulty channel becomes apparent when certain lights change to red, such as:
l in the configuration editor at rack level:
l the module position LED,
l in the configuration editor at channel level:
l the DIAGLED.

Procedure for The following table shows the procedure to access the Module diagnostics screen.
accessing the
Step Action
module
diagnostics 1 Access the AS-i module’s hardware configuration screen.
2 Click on the DIAG button located in the module zone.
Result: The list of module errors appears.
Diagnostics Module
Internal faults External faults Other faults

Faulty Channel(s).

OK

TLX DS 57 PL7 xx 291

Debugging the AS-i V2 bus

Procedure for The following table shows the procedure for accessing the Channel
accessing diagnosticsscreen.
channel
Step Action
diagnostics
1 Access the AS-i module’s hardware configuration screen.
2 Click on the DIAG button located in the channel zone.
Result: The list of channel errors appears.
Diagnostics Channel
Internal faults External faults Other faults

Slave error Data Exchange inactive on

Inconsistency with logical AS-i bus
and physical configuration

OK

292 TLX DS 57 PL7 xx

 Debugging the AS-i V2 bus

Displaying the slaves' status

At a Glance The lower part of the communication module’s debugging screen is reserved for AS-
i V2 bus diagnostics.
The slave devices connected to the bus are displayed in the two columns of the AS-
interface V2 Configuration zone. The left hand column lists standard (A) or
extended (B) address slaves, and the right hand column lists only extended address
(B) slaves only. An icon shows the status of the slave number.

Displaying slave Illustration

status AS-interface V2 configuration

Std/A Slaves /B Slaves

0
1
2
3
Faulty Slave: 4
red "LED" 5
6 Slave
7
8 4I/3O valid
9
10
11
12
13
14

When you click on the slave button, a window shows the status of the slave, as
shown in the diagram below:
Slave Diagnostics
Slave 5A
Configured Profile
IO 7 ID 0 ID2 f ID1 f

Detected Profile
IO 3 ID f ID2 f ID1 f

Diagnostics
Detected profile differs from configured profile

Close

TLX DS 57 PL7 xx 293

Debugging the AS-i V2 bus

The Slave Diagnostics window displays the following faults for each slave device:
l A configured profile is specified but no slave is detected.
l A profile is detected but there is no configured slave profile.
l A profile is detected but a different profile is specified in configuration (I/O, ID, ID1
or ID2).
l The peripheral fault, if the slave supports it.

Note: The Profile field in the Slave Zone of the debugging screen allows you to
check if the profiles of the specified (Projected) slave and the Detected slave are
identical.

294 TLX DS 57 PL7 xx

 Debugging the AS-i V2 bus

How to access adjustment of an AS-i V2 device's parameters

At a Glance The debugging screen of an AS-i V2 module allows the user, amongst other things,
to modify a slave’s parameters.

Procedure The table below shows the procedure for modifying the parameters of a slave.
Step Action
1 Access the AS-i module’s debugging screen.
2 Select a slave.
Result: All information relating to the selected slave can be read in the slave zone
of the debugging screen.
Slave 5A
Profile
Projected: IO 3 ID f ID2 f ID1 f
Detected: IO 3 ID f ID2 f ID1 f
Parameters (3-0)
Value: 1111 Modif PARAM

%I Ch. Asi Symbol Status Action channel 0

0 0 F4 Force to 0
1 0 F5 Force to 1
2 Not handled
3 Not handled F6 Unforce
0 Not handled
1 Not handled F7 Set
%Q
2 0
F8 Reset
3 0
Format: Decimal Global unforcing

3 Click on the Modif PARAM button located in the slave zone’s Parameters field.
Result: The Parameter modification window appears.

Modify Parameters Slave no : 40

Parameters
0 Unused 2 Unused

1 Unused 3 Unused

Send Cancel Input C lose

4 Selecting and omitting parameters.

5 Click on Send to recognize the new values.

TLX DS 57 PL7 xx 295

Debugging the AS-i V2 bus

Parameter Lists Where a slave can support parameter lists, the procedure to follow is the same as
above, but the window looks like this:
Parameter Modification

Parameters of slave 15

combination: combination 5

Send Cancel

Select a combination of parameters from the drop-down list

296 TLX DS 57 PL7 xx

 Debugging the AS-i V2 bus

How to access the AS-i V2 digital channels' forcing/unforcing function

At a Glance This function allows the status of channels linked to an AS-i V2 digital slave to be
modified.
The different commands available are:
l for a channel:
l forcing to 0
l forcing to 1
l unforcing.
l for all channels (when at least one channel is forced):
l global unforcing.

Procedure The table below shows the procedure to follow to force or unforce the channels
linked to an AS-i V2 slave.
Step Action for a channel Action for all channels
1 Access the AS-i V2 module’s debugging screen.
2 Select a slave in the AS-interface V2 Configuration zone.
3 Select the channel which is to be modified from the slave zone Click on the Global unforcing button
table. located in the slave zone.
Result: The channel can be modified using the buttons
situated in the Action channel field.

%I Ch. Asi Symbol Status Action channel 0

0 0 F4 Force to 0
1 0 F5 Force to 1
2 Not handled
3 Not handled F6 Unforce
0 Not handled
1 Not handled F7 Set
%Q
2 0
F8 Reset
3 0
Format: Decimal Global unforcing

4 Select the required function (buttons Force to 0 or Force to

1) in the Channel Action field.

TLX DS 57 PL7 xx 297

Debugging the AS-i V2 bus

How to access the SET and RESET commands on AS-i V2 digital channels

At a Glance These commands allow values 0 (RESET) or 1 (SET) to be assigned to the channels
of an AS-i V2 digital slave.
The status of the output affected by one of these commands is temporary and can
be modified by the application at any time.

Procedure The table below shows the procedure for assigning a value of 0 or 1 to the selected
AS-i V2 slave’s channels.
Step Action
1 Access the AS-i V2 module’s debugging screen.
2 Select a slave in the AS-interface V2 Configuration zone.
3 Select the channel to be modified in the Slave zone table.
Result: The channel can be modified using the buttons situated in the Action
channelfield.

%I Ch. Asi Symbol Status Action channel 0

0 0 F4 Force to 0
1 0 F5 Force to 1
2 Not handled
3 Not handled F6 Unforce
0 Not handled
1 Not handled F7 Set
%Q
2 0
F8 Reset
3 0
Format: Decimal Global unforcing

4 Select the required function (buttons Set or Reset) in the Channel action field.

298 TLX DS 57 PL7 xx

 Debugging the AS-i V2 bus

How to modify the value of an analog channel

At a Glance This function allows the values of channels linked to an AS-i V2 analog slave to be
modified.

Procedure The following table shows the procedure for modifying the value of an AS-i V2
slave's analog channel.
Step Action
1 Access the AS-i V2 module’s debugging screen.
2 Select an analog slave in the AS-interface V2 Configuration zone.
3 Select the channel whose value you wish to modify from the Slave zone.

%I Ch. Asi Symbol Status Action channel 0

0 0
1 0 Change value
2 0
3 0
0 10000
1 0
%Q
2 0
3 0
Format: Decimal Global unforcing

4 Click on the Change Value button.

Result: the following window appears:

Analog I/O

Slave 21A / Channel 0

Value
10000
decimal:

OK

5 Enter the value in decimals and click on OK

Note: the value is always entered as decimal, but it may be displayed in a
different format using the Format drop-down list, located at the bottom of the
Slave zone.

TLX DS 57 PL7 xx 299

Debugging the AS-i V2 bus

Automatic replacement of a faulty AS-i V2 slave

Principle When a slave has been declared faulty, it can be automatically replaced with a slave
of the same type.
This happens without the AS-i V2 bus having to stop, and without requiring any
manipulation since the configuration mode's Automatic addressing utility is active
(see How to modify the general parameters of an AS-i V2 slave: Automatic
addressing, p. 282).

Two options are available:

l The replacement slave is programmed with the same address using the pocket
programmer, and has the same profile and sub-profile as the faulty slave. It is
thus automatically inserted into the list of detected slaves (LDS) and into the list
of active slaves (LAS),
l The replacement slave is blank (address 0 (A), new slave) and has the same
profile as the faulty slave. It will automatically assume the address of the replaced
slave, and will then be inserted into the list of detected slaves (LDS) and into the
list of active slaves (LAS).

300 TLX DS 57 PL7 xx

 Debugging the AS-i V2 bus

How to insert a slave device into an existing AS-i V2 configuration.

At a Glance It is possible to insert a device into an existing AS-i V2 configuration without having
to use the pocket programmer.
This operation is possible once:
l the configuration mode's Automatic addressing utility is active (See How to
modify the general parameters of an AS-i V2 slave: Automatic addressing,
p. 282),
l a single slave is absent in the physical configuration,
l the slave which is to be inserted is specified in the PL7 configuration,
l the slave has the profile and sub-profile expected by the configuration,
l the slave has the address 0 (A).
The AS-i V2 module will therefore automatically assign to the slave the value
predefined in the configuration.

Procedure The following table shows the procedure for making the automatic insertion of a new
slave effective.
Step Action
1 Add the new slave in the configuration screen in local mode.
2 Carry out a configuration transfer to the PLC in connected mode.
3 Physically link the new slave with address 0 (A) to the AS-i V2 bus.

Note: An application can be modified by carrying out the above manipulation as

many times as necessary.

TLX DS 57 PL7 xx 301

Debugging the AS-i V2 bus

How to modify the address of an AS-i V2 device

At a Glance This command allows the movement of the selected AS-i V2 device to another
available address. This address modification can only be done on the slave and not
in configuration: thus physical configuration and software configuration are different.

Procedure The following table shows the procedure for modifying the address of an AS-i V2
slave device.
Step Action
1 Access the TSX SAY 1000 module’s debugging screen.
2 Select a slave in the AS-interface V2 configuration zone then execute the
command Edit → Modify the address of an AS-i slave.
Result: The selection screen for a new address is displayed.

Modify address

Current Address: 4B

Bank selection: A

Addresses available on this bank: 0

1
2
3
4
5
6
7
8
OK Cancel

3 Select bank A or B in the Bank Selection list.

Note: bank B cannot be selected where there is a standard address slave.
4 Select the required address in the list of Available addresses (use the scroll bar
if necessary).
5 Confirm the selection with OK.

302 TLX DS 57 PL7 xx

 Bits and words associated with
the AS-i V2 function
20
At a Glance

Aim of this This Chapter introduces the different word and bit objects associated with the AS-i
chapter V2 function, as well as how to address them.

What's in this This Chapter contains the following Sections:

Chapter?
Section Topic Page
20.1 Addressing objects associated with the AS-i V2 function 304
20.2 Language objects associated with the AS-i V2 function 305

TLX DS 57 PL7 xx 303

Bits and words associated with the AS-i V2 function

20.1 Addressing objects associated with the AS-i V2

function

Addressing Language Objects Associated with Slave Devices Connected to the

AS-i V2 Bus.

At a Glance The addressing of bit and word objects associated with application-specific
functions is defined in the Common Applications part.
This page presents specific details associated with the AS-i V2 function.

Illustration Reminder of the principle of addressing:

% I, Q, IW, QW \ xy.0 \ n i
Symbol Type of Module address/channel Slave no. Bit
object of TSX SAY 1000 position
0 = channel 0 of module

Specific Values The table below gives specific values to AS-i V2 slave objects.
Element Values Comment
n (for bank A) 0 to 31 Slot 0 cannot be configured.
n (for bank B) 100 to 131 Slot 0 cannot be configured.
i 0 to 3 -

304 TLX DS 57 PL7 xx

 Bits and words associated with the AS-i V2 function

20.2 Language objects associated with the AS-i V2

function

At a Glance

Aim of this This section introduces the different language objects associated with the AS-i V2
Section function.

What's in this This Section contains the following Maps:

Section?
Topic Page
Implicit exchange objects associated with the AS-i V2 function 306
Exchange management: Module %MWxy.MOD.0:Xj or channel MWxy.0.0 :Xj 308
exchanges in progress
Exchange management: Module %MWxy.MOD.1:Xj or channel %MWxy.i.1:Xj 309
report
Explicit exchange objects: General 310
Explicit Exchange Objects: %MWxy.MOD.2 and %MWxy.0.2:Xj to 311
%MWxy.0.73:Xj channel status
Constant %KWxy.i.r configuration objects 314
Explicit Exchange Object: %MWxy.0.74:Xj channel command 315
Explicit Exchange Object: %MWxy.0.75 to %MWxy.0.138 Parameter 316
Adjustment
Explicit Exchange Object: Status %MWxy.MOD.2:Xj 317

TLX DS 57 PL7 xx 305

Bits and words associated with the AS-i V2 function

Implicit exchange objects associated with the AS-i V2 function

At a Glance In each task cycle where the AS-i V2 function has been configured, these objects
are exchanged automatically.

Bit objects The table below shows the different implicit exchange bit objects.
Address Function Meaning when bit is on 1
%Ixy.MOD.ERR Module fault bit Indicates that the AS-i module has a fault.
%Ixy.0.ERR Channel fault bit 0 Indicates a channel 0 fault on the AS-i module
%Ixy.0.0 Validity of input Indicates that all inputs are valid.
Note: When this bit is on 0, it indicates that at least one input is
invalid: offline mode, data exchange off mode, or channel fault.
%I\xy.0\n.i digital input channel bit* Indicates that the input channel i of device n is activated.
%Q\xy.0\.n.i digital output channel bit* Indicates that output channel i of device n is activated.
*For bank A, n = 0 to 31
*For bank B, n = 100 to 131

Word objects The table below shows the different implicit exchange word objects.
Address Function Meaning for Xj = 1 (j = position of bit in the word)
%IWxy.0.0 List of standard (A) inactive j = 0 to 15 -> respectively standard address slave 0 to 15 inactive.
%IWxy.0.1 slaves (/LAS) j = 0 to 15 -> respectively standard address slave 16 to 31 inactive.
%IWxy.0.2 Liste of inactive extended (B) j = 0 to 15 -> respectively extended address slave 0 to 15 inactive.
%IWxy.0.3 slaves (/LAS) j = 0 to 15 -> respectively extended address slave 16 to 31
inactive.
%IWxy.0.4 Peripheral fault (LPF) on j = 0 to 15 -> respectively standard address slave 0 to 15 has
%IWxy.0.5 standard slaves (A) peripheral fault.
j = 0 to 15 -> respectively standard address slave 16 to 31 has
peripheral fault.
%IWxy.0.6 Peripheral fault (LPF) on j = 0 to 15 -> respectively extended address slave 0 to 15 has
%IWxy.0.7 extended slaves (B) peripheral fault.
j = 0 to 15 -> respectively extended address slave 16 to 31 has
peripheral fault.
%IWxy.0.8 Liste of standard (A) active j = 0 to 15 -> respectively standard address slave 0 to 15 active.
%IWxy.0.9 slaves (LAS) j = 0 to 15 -> respectively standard address slave 16 to 31 active.
%IWxy.0.10 List of active extended (B) j = 0 to 15 -> respectively extended address slave 0 to 15 active.
%IWxy.0.11 slaves (LAS) j = 0 to 15 -> respectively extended address slave 16 to 31 active.
*For bank A, n = 0 to 31
*For bank B, n = 100 to 131

306 TLX DS 57 PL7 xx

 Bits and words associated with the AS-i V2 function

Address Function Meaning for Xj = 1 (j = position of bit in the word)

%IW\xy.0\n Analog Input Channel* Value of input word in analog channel.
%QW\xy.0\n Analog Output Channel* Value of output word in analog channel.
*For bank A, n = 0 to 31
*For bank B, n = 100 to 131

TLX DS 57 PL7 xx 307

Bits and words associated with the AS-i V2 function

Exchange management: Module %MWxy.MOD.0:Xj or channel MWxy.0.0 :Xj

exchanges in progress

At a Glance These word type objects carry information about the module or channel exchanges
in progress.
They are updated automatically by the system.

Description The table below provides the meaning of the word %MWxy.MOD.0.
Address Meaning
%MWxy.MOD.0:X0 Exchange of status words in progress on the module channel.
%MWxy.MOD.0:X1 Exchange of command words in progress on the module
channel.

Description The following table provides the meaning of the different bits of the word
%MWxy.i.0.
Address Meaning
%MWxy.0.0 Byte 0
X0: Periodic status reading in progress
X1: Specific command in progress
X2: Setting in progress
X15: configuration in progress

308 TLX DS 57 PL7 xx

 Bits and words associated with the AS-i V2 function

Exchange management: Module %MWxy.MOD.1:Xj or channel %MWxy.i.1:Xj

report

At a Glance These word type objects carry information about module or channel exchange
reports.
They are updated automatically by the system.

Description The following table provides the meaning of the different bits of the word
%MWxy.MOD.1.
Address Meaning
%MWxy.MOD.1:X0 Status parameter exchange error on channel 0 of the module
%MWxy.MOD.1:X1 Command parameter exchange error on channel 0 of the
module

Description The following table provides the meaning of the different bits of the word
%MWxy.i.1.
Address Meaning
%MWxy.0.1 Byte 0
X0: error in last periodic status reading
X1: error in last command action
X2: error in last setting action

Byte 1
X7: error in last configuration action

Example The following example shows a possible use of this type of word

(* Detection of a status error on the module situated in *)

(* slot 4 of rack 0 *)
IF NOT %MW4.MOD0:X0 THEN READ_STS %CH4.MOD;
END_IF;
IF %MW4.MOD.1:X0 THEN SET %M100;
END_IF;

TLX DS 57 PL7 xx 309

Bits and words associated with the AS-i V2 function

Explicit exchange objects: General

At a Glance Explicit exchange objects carry information (e.g.: bus operation, status of slaves)
and the additional commands for advanced programming of the AS-i function.

The explicit exchange objects are exchanged at the request of the program user
using instructions:
l READ_STS (reading of status words),
l WRITE_CMD (writing the command words),
l WRITE_PARAM (writing the adjustment words),
l READ_PARAM (reading the adjustment parameters),
l SAVE_PARAM (saving the adjustment parameters),
l RESTORE_PARAM (restoring the adjustment parameters),

310 TLX DS 57 PL7 xx

 Bits and words associated with the AS-i V2 function

Explicit Exchange Objects: %MWxy.MOD.2 and %MWxy.0.2:Xj to

%MWxy.0.73:Xj channel status

At a Glance These word type objects provide information on all the slaves present on the AS-i
V2 bus.

Description of The table below gives the meaning of the different bits of the word %MWxy.0.2.
word %MWxy.0.2
Address Function Meaning for Xj = 1
%MWxy.0.2:X0 Standard status No meaning
%MWxy.0.2:X1 Slave error.
%MWxy.0.2:X2 Line error (APF).
%MWxy.0.2:X3 Physical configuration different from PL7 configuration.
%MWxy.0.2:X4 Internal software fault.
%MWxy.0.2:X5 No meaning
%MWxy.0.2:X6 Fault communicating with processor
%MWxy.0.2:X7 Command or parameter configuration fault.

Description of The table below gives the meaning of the different bits of the word %MWxy.0.3.
word %MWxy.0.3
Address Function Meaning for Xj = 1
AS-i master status
Byte 0
%MWxy.0.3:X0 Correct configuration.
%MWxy.0.3:X1 Slave 0 present on the bus.
%MWxy.0.3:X2 Automatic addressing.
%MWxy.0.3:X3 Automatic addressing authorized.
%MWxy.0.3:X4 Operation in AS-i configuration mode.
%MWxy.0.3:X5 Operation in normal mode.
%MWxy.0.3:X6 Faulty AS-i power supply.
%MWxy.0.3:X7 Offline mode active.
Byte 1
%MWxy.0.3:X0 Data exchange inactive.
%MWxy.0.3:X1 Peripheral fault on a bus device.

TLX DS 57 PL7 xx 311

Bits and words associated with the AS-i V2 function

Description of The table below gives the meaning of the different bits of words %MWxy.0.4 and
words %MWxy.0.7.
%MWxy.0.4 to
%MWxy.0.7
Address Function Meaning for Xj = 1
%MWxy.0.4:Xj List of detected slaves in j = 0 to 15 -> slaves 0 to 15 respectively have been detected.
%MWxy.0.5:Xj bank A (LDS) j = 0 to 15 -> slaves 16 to 31 respectively have been detected.
%MWxy.0.6:Xj List of detected slaves in j = 0 to 15 -> slaves 0 to 15 respectively have been detected.
%MWxy.0.7:Xj bank B (LDS) j = 0 to 15 -> slaves 16 to 31 respectively have been detected.

Description of The table below gives the meaning of the different bits of words %MWxy.0.8 to
words %MWxy.0.71.
%MWxy.0.8 to
%MWxy.0.71
Address Function Meaning
%MWxy.0.8 to I/O configuration and ID of Words 8 to 39 -> devices 0 to 31 respectively.
%MWxy.0.39 all detected slaves in bank A Byte 0
bit 0-3 = configuration code for I/O channels,
bit 4-7 = identification (ID) code.
Byte 1
bit 0-3 = identification code (ID1),
bit 4-7 = identification code (ID2).
%MWxy.0.40 to I/O configuration and ID of Words 40 to 71 -> devices 0 to 31 respectively.
%MWxy.0.71 all detected slaves in bank B Byte 0
bit 0-3 = configuration code for I/O channels,
bit 4-7 = identification code (ID).
Byte 1:
bit 0-3 = identification code (ID1),
bit 4-7 = identification code (ID2).

Description of The table below gives the meaning of the word %MWxy.0.72.
word
%MWxy.0.72
Address Function Meaning
%MWxy.0.72 Parameter data of last Contains the information (value of parameters sent) of the last
parametered slave. parametered slave. This is so that the PL7 can check the slave has
correctly received these values.

312 TLX DS 57 PL7 xx

 Bits and words associated with the AS-i V2 function

Description of The table below provides the meaning of the word %MWxy.0.73.
word
%MWxy.0.73
Address Function Meaning
%MWxy.0.73 Address of last parametered Contains the address of last parametered slave.
slave. Byte 0:
Address of the slave (1 to 31).

Byte 1:
Slave bank:
0 = bank A
1 = bank B.

TLX DS 57 PL7 xx 313

Bits and words associated with the AS-i V2 function

Constant %KWxy.i.r configuration objects

At a Glance %KWxy.i.r configuration constants are accessible in read-only mode and

correspond to the configuration parameters entered using the Configuration editor.

Description The table below shows constant objects on the AS-i exteneded bus.
Address Function Meaning
%KWxy.0.0 AS-i master When byte 0 = 10, this shows that AS-i is master.
%KWxy.0.1:Xj List of expected slaves in j = 0 to 15 -> expected slaves 0 to 15 respectively.
%KWxy.0.2:Xj bank A (LDS) j = 0 to 15 -> expected slaves 16 to 31 respectively.
%KWxy.0.3:Xj List of expected slaves in j = 0 to 15 -> expected slaves 0 to 15 respectively.
%KWxy.0.4:Xj bank B (LPS) j = 0 to 15 -> expected slaves 16 to 31 respectively.
%KWxy.0.5 à I/O configuration and ID of Words 5 to 36 -> devices 0 to 31 respectively.
%KWxy.0.36 all expected slaves in Byte 0:
bank A bits 0-3 = configuration code for I/O channels,
bits 4-7 = identification code (ID).
Byte 1:
bits 0-3 = identification code (ID1),
bits 4-7 = identification code (ID2).
%KWxy.0.37 à I/O configuration and ID of Words 37 to 68 -> devices 0 to 31 respectively.
%KWxy.0.68 all expected slaves in Byte 0:
bank B bits 0-3 = configuration code for I/O channels,
bits 4-7 = identification code (ID).
Byte 1:
bits 0-3 = identification code (ID1),
bits 4-7 = identification code (ID2).
%KWxy.0.69:X0 Automatic Address If this = 1, automatic addressing is active.
Monitoring If this = 0, automatic addressing is deactivated.

314 TLX DS 57 PL7 xx

 Bits and words associated with the AS-i V2 function

Explicit Exchange Object: %MWxy.0.74:Xj channel command

At a Glance This word type object is used to manage the switch to Offline mode (See AS-i V2
Offline Operating Mode, p. 323) or Data Exchange Off mode (See AS-i V2 Data
Exchange Off Operating Mode, p. 324) of the AS-i V2 master.

Note: Use of this object requires a thorough knowledge of AS-i V2 communication

principles.

Description The table below gives the different states of the word %MWxy.0.74, giving access
to the different modes.
Address Meaning for Xj=1
%MWxy.0.74:X0 Switching to Offline mode
%MWxy.0.74:X1 Leaving Offline mode
%MWxy.0.74:X2 Data exchange inactive
%MWxy.0.74:X3 Data exchange active

Note: Offline mode has priority over Data Exchange Offmode.

TLX DS 57 PL7 xx 315

Bits and words associated with the AS-i V2 function

Explicit Exchange Object: %MWxy.0.75 to %MWxy.0.138 Parameter Adjustment

At a Glance These objects are used to manage the parameters of AS-i V2 slave devices.
They can be modified without stopping the AS-i V2 function.

Description The table below shows AS-i V2 parameter adjustment objects.

Address Function Meaning
%MWxy.0.75 to Adjustment of parameters of Contain the parameter values of slaves 0 to 31 respectively.
%MWxy.0.106 slaves in bank A.
%MWxy.0.107 to Adjustment of parameters of Contain the parameter values of slaves 0 to 31 respectively.
%MWxy.0.138 slaves in bank B.

316 TLX DS 57 PL7 xx

 Bits and words associated with the AS-i V2 function

Explicit Exchange Object: Status %MWxy.MOD.2:Xj

At a Glance This word type object provides information on the state of the module TSX SAY
1000.

Description The table below gives the meaning of the different bits of the word
%MWxy.MOD.2:Xj.
Address Function Meaning for Xj = 1
%MWxy.MOD.2:X0 Standard module status Internal error.
%MWxy.MOD.2:X1 Configuration fault.
%MWxy.MOD.2:X2 Line fault.

TLX DS 57 PL7 xx 317

Bits and words associated with the AS-i V2 function

318 TLX DS 57 PL7 xx

 AS-i V2 operating mode

21
At a Glance

Aim of this This chapter introduces the different AS-i V2 function operating modes.
chapter

What's in this This Chapter contains the following Maps:

Chapter?
Topic Page
AS-i V2 Operating Mode: General 320
AS-i V2 Protected Mode 322
AS-i V2 Offline Operating Mode 323
AS-i V2 Data Exchange Off Operating Mode 324

TLX DS 57 PL7 xx 319

AS-i V2 operation

AS-i V2 Operating Mode: General

At a Glance The extended AS-i V2 function allows three operating modes, each one fulfilling
particular needs. These modes are:
l protected mode,
l offline mode,
l data exchange off mode.

Operating mode The figure below shows the general operating diagram of the AS-i V2 bus.

Offline mode
PLC
off

Start
AS-i master module

No
Waiting to receive
configuration Is the master configured?
PLC
on

Yes

Protected mode

(1)

Standard management of
AS-i V2 slaves

(1) : It is possible to switch from protected mode to offline or data exchange off
modes (see AS-i V2 Offline Operating Mode, p. 323 or AS-i V2 Data Exchange Off
Operating Mode, p. 324).

320 TLX DS 57 PL7 xx

 AS-i V2 operation

Correspondence The table below shows the correspondence between Premium PLC operating
between PLC modes and those of the AS-i V2 bus.
operating modes
PLC AS-i bus
and the AS-i bus
Configured mode (1) Protected mode
Non-configured mode (1) Configuration mode

Legend:
(1) These PLC notions (configured, non-configured) concern the
declaration of the module and slave devices in the PL7
application hardware configuration screen.

TLX DS 57 PL7 xx 321

AS-i V2 operation

AS-i V2 Protected Mode

At a Glance The AS-i V2 protected operating mode is the mode generally used for an application
which is running.
It assumes that the AS-i V2 module is configured in PL7.
This:
l continually checks that the list of detected slaves is the same as the list of
expected slaves,
l monitors the power supply.
In this mode, a slave will only be activated if it has been declared in the configuration
and been detected.

Principle of The diagram below shows the principle of activating AS-i V2 slaves.
activating a slave
PL7 AS-i V2 Bus Module

List of slaves List of detected

expected LPS slaves LDS

Comparison

List of activated
slaves LAS

322 TLX DS 57 PL7 xx

 AS-i V2 operation

AS-i V2 Offline Operating Mode

At a Glance The Offline AS-i V2 mode is an advanced operating mode which can be used in
debugging or maintenance.

Note: The user must be thoroughly familiar with AS-i V2 communication.

Principle When Offline mode is engaged, the module first resets all the present slaves to zero
and stops exchanges on the bus.
During Offline mode, the outputs are forced to zero.

Note: The Offline mode is also used to exploit the infrared addressing function on
the slaves which support this function.

Procedure The Offline operating mode is accessible from the PL7 application software by
acting on bits 0 and 1 of the word %MWxy.0.74.

Reminder: Bit 7 of word %MWxy.0.3 set on 1 indicates that the AS-i bus is in Offline
mode.

TLX DS 57 PL7 xx 323

AS-i V2 operation

AS-i V2 Data Exchange Off Operating Mode

At a Glance The Data Exchange Off AS-i V2 mode is an advanced operating mode which can
be used in debugging or maintenance.

Note: The user must be thoroughly familiar with AS-i V2 communication.

Principle When the Data Exchange Off mode is engaged, exchanges on the bus continue to
function, but data is no longer refreshed.

Procedure The Data Exchange Off operating mode can be accessed from PL7 application
software by acting on bits 2 and 3 of the word %MWxy.0.74.

324 TLX DS 57 PL7 xx

 AS-i V2 performance

22
AS-i V2 Bus Performance

Introduction The AS-i V2 bus is independently managed by the master. This exchanges data on
each cycle with each slave device configured on the bus (in ascending order of slave
address number).

AS-i V2 Scanning Scanning time t represents the exchange time between the master and n slaves (31
Time maximum on /A and/or /B).
Either:
l up to 19 active slaves, t = 3ms
l from 20 to 31 active slaves t = (1 + number of active slaves) * 0.156 ms
When two slaves A and B are at the same address, each slave of this pair is scanned
on every second cycle.
Thus, for 31 extended address slaves in /A + 31 extended address slaves in /B, the
scanning time will be 10ms.

AS-i V2 The response time T represents the AS-i V2 cycle time.

Response Time This includes:
l the bus scanning time,
l the update of the AS-i V2 module internal memory,
l the PLC cycle.

Example The table below shows three examples of T response time for a PLC task lasting 10
ms, 30 ms, and 60 ms.
This T time is for a bus loaded with 31 slaves operating normally with no link faults.
PLC task Typical response time Maximum response time
10 ms 35 ms 56 ms
30 ms 65 ms 96 ms
60 ms 110 ms 156 ms

TLX DS 57 PL7 xx 325

AS-i V2 performance

326 TLX DS 57 PL7 xx

 DFB for AS-i Security Monitor

23
At a Glance

Aim of this This DFB describes the DFB for the AS-i Security Monitor.
Section

What's in this This Chapter contains the following Maps:

Chapter?
Topic Page
Description of the security function block of the AS-i bus 328
Operation of the AS-i security function block 331
Programming rules for security DFB 332
How to implement a DFB function block 334

TLX DS 57 PL7 xx 327

DFB AS-i

Description of the security function block of the AS-i bus

General This DFB is used to obtain data processed by the safety monitor.

Graphic This drawing provides a graphic representation of the AS-i security function block:
representation SAFETY_MONITOR

I0:Bit Enable
Q0 Error:Bit
I1:Bit
Inputs Q1 Outputs
I2:Bit Q2 Running:Bit
I3:Bit Q3

Internal public
data
Abort Bit
Timeout Word
Dfb_stat Word
Dfb_err Word
Moni_err Bit
Out_1 Bit
Out_2 Bit
SI_Ready Dword
SI_off Dword
SI_error Dword

Input parameters The table below describes the input parameters of the security DFB:
Name Type Description of monitor data
I0 Bit Input variable 0: %I\x.y.0\i.0 (x=rack, y=module, i=AS-i monitor address)
I1 Bit Input variable 1: %I\x.y.0\i.1 (x=rack, y=module, i=AS-i monitor address)
I2 Bit Input variable 2: %I\x.y.0\i.2 (x=rack, y=module, i=AS-i monitor address)
I3 Bit Input variable 3: %I\x.y.0\i.3 (x=rack, y=module, i=AS-i monitor address)

328 TLX DS 57 PL7 xx

 DFB AS-i

Output The table below describes the output parameters of the security DFB:
parameters
Name Type Description
Error Bit This bit is set to "1" if an error occurs: DFB error or security bus error (error on at
least one slave):
l if it is a DFB error (enable = 0): consult dfb_error ( ≠ 0) for further information. In
the event of a DFB error, the information from the security application is no
longer valid.
l if it is a security application error (dfb_error = 0 and enable = 1): consult sl_error
to obtain the list of slaves on which an error has occurred.
Running Bit This Bit is set to "1" during DFB execution.

Input/output The table below describes the input/output parameters of the security DFB:
parameters
Name Type Description
Enable Bit DFB activation (Cold Start): if this Bit is set to "1", the DFB is executed; otherwise it
is deactivated. The information can only be used if Enable = 0.
Q0 Bit Output variable 0: %Q\x.y.0\i.0 (x=rack, y=module, i=AS-i monitor address)
Q1 Bit Output variable 1: %Q\x.y.0\i.1 (x=rack, y=module, i=AS-i monitor address)
Q2 Bit Output variable 2: %Q\x.y.0\i.2 (x=rack, y=module, i=AS-i monitor address)
Q3 Bit Output variable 3: %Q\x.y.0\i.3 (x=rack, y=module, i=AS-i monitor address)

TLX DS 57 PL7 xx 329

DFB AS-i

Public data The table below describes the public data parameters of the security DFB:
parameters
Name Type Description
Abort Bit If this bit is set to "0" in one cycle then set to "1" in the next cycle, all
exchanges between the CPU and Safety monitor are stopped and the
DFB is reinitialized.
All the internal data of the DFB is set to 0.
Timeout Word Data exchange timeout (time base of 100ms).
If the DFB does not receive a correct response before this period has
elapsed, the transaction is cancelled, the DFB is deactivated and the
error bit is set to "1" (Dfb_stat and Dfb_err are updated).
Moni_err Bit this bit is set to "1" if an error has occurred on the monitor.
Out_1 Bit this bit is set to "1" if the contact on OUT1 is closed.
Out_2 Bit this bit is set to "1" if the contact on OUT2 is closed.
SI_ready Dword each bit corresponds to the index of the security device which is in test
or read status.
SI_off Dword each bit corresponds to the index of the security device which is
deactivated.
SI_error Dword each bit corresponds to the index of the security device on which an
error has occurred.
Dfb_stat Word this is the DFB status; this variable enables the user to check on DFB
(See Operation of the AS-i security function block, p. 331) progress.
Dfb_err Word This word specifies the error type:
l 16#90; the response sent by the monitor is not valid,
l 16#91: the DFB has been deleted by the user,
l 16#92: the exchange has stopped as a result of a TimeOut. The
DFB cannot receive data.

To search for a The search for the address of a safety slave which has been activated can be
safety slave facilitated by acknowledgment of the slave's inputs I3/I2/I1/I0. These inputs are
which has been equal to 0/0/0/0 if the slave has been activated, and not equal to 0/0/0/0 if the slave
activated has not been activated. This information shall not be taken into account for safety
purposes: only the safety monitor supplies the safety outputs.

330 TLX DS 57 PL7 xx

 DFB AS-i

Operation of the AS-i security function block

General All the information used in the AS-i security DFB is obtained from the language
operation objects associated with the TSX SAY 100 AS-i module and the TSX SAY 1000 AS-
i V2 module.

Step-by-step The table below provides a step-by-step description of how the security DFB
description of operates:
operation
Step Action
1 The bus master sends the request to test the monitor.
2 The bus master sends the request for the monitor to copy its status to static
memory.
3 The bus master analyses the data from the monitor.
4 Retrieval of data from all security devices.
5

TLX DS 57 PL7 xx 331

DFB AS-i

Programming rules for security DFB

General The security DFB, which is implemented in exactly the same way as the AS-i DIAG
DFB, can be programmed in any type of program (Main, SR or section) in Ladder
(LD), Structured Text (ST) or Instruction List (IL) language.
It is:
l systematically available in PL7 (See How to insert a security DFB, p. 334),
l read and write protected,
l dedicated to a single security monitor.

Rules l Preferably, the security DFB should be executed in the MAST task (for
performance reasons).
l You are strongly advised to only program a single instance of the security DFB in
the application.
l For a security DFB to be executed, the following conditions must be met:
l the DFB must be called (the part of the program to which it has been assigned
must be executed)
l the Enable input must be set to 1

332 TLX DS 57 PL7 xx

 DFB AS-i

Programming in The security DFB function block is inserted in a ladder network. Programming
Ladder language consists of linking together these inputs/outputs
Sécurité

DFB SAFETY_MONITOR

%I\1.0\31.0 %M102
EBOOL
I0 EBOOL
Error S
%I\1.0\31.1
EBOOL
I1 EBOOL
%I\1.0\31.2 Running
EBOOL
I2
%I\1.0\31.3
EBOOL
I3

EBOOL
%M101 Enable Enable %M101

%Q\1.0\31.0 EBOOL
Q0 Q0 %Q\1.0\31.0
EBOOL
%Q\1.0\31.1
Q1 Q1 %Q\1.0\31.1
EBOOL
%Q\1.0\31.2
Q2 Q2 %Q\1.0\31.2
EBOOL
%Q\1.0\31.3
Q3 Q3 %Q\1.0\31.3

Programming in The programming syntax is as follows:

Structured Text %Li: label
language Inst ( I0,..., I3, %MW101, Q0,...,Q3, %M102);

where:
l %Li: label,
l Inst: name of a DFB instance,
l I0,..., I3: DFB inputs,
l %M101: Enable input of DFB,
l Q0,...,Q3: variables linked to the DFB outputs,
l %M102: Error output variable.

TLX DS 57 PL7 xx 333

DFB AS-i

How to implement a DFB function block

Reminder The AS-i security DFB is included in the PL7 base (See How to insert a security
DFB, p. 334).

Using DFBs This block instance can then be used as a standard function block in Ladder
language, or as an elementary function in Structured Text or Instruction List
language.

It can be programmed in all the different tasks (except in event processing tasks)
and sections of the application.

How to insert a The following table describes the procedure used to insert a security DFB:
security DFB
Step Action
1 Declare the security DFBs
1. Import the binary DFB file (SAFETY_MONITOR .UFB) by selecting Import
binary from the context-sensitive menu and importing the file from the
Dfb_asi sub-directory in the PL7 installation directory (e.g.
C:\PL7\PL7PRO43\Dfb_asi),
2. Declare an instance of the DFB in the PL7 variable editor.
2 Program the DFB in the ladder network in LD or in the sequence in ST.
See Programming rules for security DFB, p. 332

334 TLX DS 57 PL7 xx

 Operator Dialog functions

V
Introduction

Subject of this This part introduces the specific built-in Operator Dialog functions of PL7 and
part describes the software setup.

What's in this This Part contains the following Chapters:

part?
Chapter Chaptername Page
24 General presentation of the Operator Dialog functions 337
25 Built-in DOP functions 339
26 Appendices 393

TLX DS 57 PL7 xx 335

Operator Dialog functions

336 TLX DS 57 PL7 xx

 General presentation of the
Operator Dialog functions
24
General presentation

Introduction The PL7 software allows the implementation of specific functions, designed to
simplify the use of an operator dialog terminal (version 2.0 and higher) on a TSX
Premium PLC.

These functions are the basic elements of the PL7 language.

They allow the following actions to be carried out without referring to the
communication media between the command console CCX 17 and the PLC:
l displaying messages,
l displaying message and alarm message groups,
l entering values from the PLC program.

Hence the Operator Dialog functions are completely integrated in the PLC
application and support:
l data cohesion,
l unique saving,
l easy maintenance,
l simplified consoles.
l ...

The processing of these functions occurs asynchronously to the processing of the

operative task that enabled their activation.

How to access a See Application-specific instructions, p. 56.

DOP function

TLX DS 57 PL7 xx 337

General presentation

Conditions for The built-in DOP functions require a program space of 1 Kword (4.7 Kwords for
using built-in ADJUST). Variables must be reserved for the data you want to display (use the
DOP functions constants %KWi).

Example of a The illustration below shows an example of a DOP function written in the different
DOP function PL7 languages using the assisted entry of the library functions.

PANEL-CMD
Parameters
Console address: %MW0 6 Report: %MW100 4
Data to Send: %KW40 2
Commands
Clear
Screen Line Line number 1
Entry log
Print Clear
Alarm log
Print Clear
Alarm management
Cancel an Alarm Alarm number 1

OK Cancel

LD Language

%M100 %MW100>> OPERATE

PANEL_CMD (ADR#0.0.4, %KW0:2, %MW>>

IL Language

LDN %100
ANDN %MW100:X0
[PANEL_CMD (ADR#0.0.4, %KW0:2, %MW0: 4 ) ]

ST Language

IF NOT %M100 AND NOT %MW100. X0 THEN PANEL_CND (%MW0 . 6,%KV0 . 2,%MW100 . 4),
END_-F

338 TLX DS 57 PL7 xx

 Built-in DOP functions

25
Introduction

Subject of this This chapter describes the different built-in DOP functions and shows how they are
chapter set-up in PL7.

What's in this This Chapter contains the following Sections:

Chapter?
Section Topic Page
25.1 Description of the parameters common to the different DOP 340
functions
25.2 Description of the built-in DOP functions 356

TLX DS 57 PL7 xx 339

Built-in DOP functions

25.1 Description of the parameters common to the

different DOP functions

Introduction

Subject of this This section shows the main parameters, divided into zones, of the built-in DOP
section functions.

Note: The parameters specific to a DOP function are shown at the level of the
function concerned.

What's in this This Section contains the following Maps:

Section?
Topic Page
General 341
Parameters field: Console address 342
Parameters field: Data to be sent 345
Parameter field: Data to be received: 347
Parameters field: Report 348
Message field 352
Field zone 354

340 TLX DS 57 PL7 xx

 Built-in DOP functions

General

Introduction The Built-in DOP functions are part of the procedure category; they do not return
value, but they do possess several parameters, some of which have to be filled in.

The functions use three types of parameters:

l in read only (IN) format, acknowledged at the start of function execution,
l in write only (OUT) format, set at close of function execution,
l in read and write format (IN/OUT), whose contents have been acknowledged at
the start of function execution and are then updated by the function results.
The parameter type is displayed in the Type of Parameter of the … column located
in the Library functions screen.

Illustration The illustration below gives an insight into the Library functions screen where the
various parameters of the selected function are displayed.

PL7: Library functions ?

EF
Function information: Parameters Detail...
Family Lib.V. App.V Name Comment
Dates, Times, and Periods2.10 - ADJUST Read/write memory objects and I/O
Diagnostics 1.01 - ASK_MSG Variable blocking entry on CCX
Integrated DOP 3.03 3.03 ASK_VALUEVariable blocking entry on >>
Explicit exchanges 1.00 ASSIGN_K Dynamic key assignment >>
Call format
PROCEDURE parameter:
Name Type Kind Comment Entry field
ADR AR_W IN CCX17 address table
DATA AR_W IN Table for data to be sent
VAL AR_W OUT Table for data to be received

Call display
ASK_MSG( )

OK Cancel

TLX DS 57 PL7 xx 341

Built-in DOP functions

Parameters field: Console address

Introduction This parameter contains the access path (address) for the CCX 17 dialog console.
This path can be either:
l located in a table of six internal words (%MW),
l located in a table of six internal constants (%KW),
l or passed directly to an immediate value in the form of an ADR# operator.
ADR# is then assimilated into a table of six consecutive internal words.

Addressing via The table below shows the signification of different words which make up the
words or console address.
constants
Word number Description
Most significant Least significant
%MWi / %KWi 6 (Uni-telway) 0
7 (FIPIO
%MWi +1 / %KWi+1 254 (1) 0 (1)
%MWi +2 / %KWi+2 Rack number Module number
%MWi +3 / %KWi+3 CCX 17 address channel
SYS
FIPIO connection point
%MWi +4 / %KWi+4 0 SYS (FIPIO)
%MWi +5 / %KWi+5 0 0

Key
(1) Operating a CCX 17 console means that only one intra-station
address is authorized. As a result, the {Station.Network} pair
systematically takes on the value {0.254}.
Writing this field is optional.

Note: The key word SYS (value 254) corresponds to attributing an address to the
system channel (UNI-TE server) for a communication channel.

342 TLX DS 57 PL7 xx

 Built-in DOP functions

Uni-telway The format of a CCX 17 address connected to the Uni-telway bus is:
addressing ADR#{<Network>.<Station>}<rack.module>.<channel>.<CCX 17
address>,
ADR#{<Network>.<Station>}< rack.module>.<channel>.SYS,
ADR#< rack.module>.<channel>.<CCX 17 address>,
ADR#< rack.module>.<channel>. SYS.

FIPIO addressing The format of a CCX 17 address connected to the FIPIO bus is:
ADR#{<Network>.<Station>}<rack.module>.<channel>.<connection
point>\SYS,
ADR#< rack.module>.<channel>.<connection point>\SYS.

Examples of For a CCX 17 slave on a UTW 4-5 address, connected to a TSX Premium PLC
addressing via the built-in Uni-telway link (channel 0) positioned in rack 0.
Addresses can be entered in many ways (example here using internal words %MW0
to %MW5):
If you use: in the function entry Help screen, … you must enter the program…
internal (or Example: %MW0:=16#0600;
constant) words %MW1:=16#FE00;
Parameters
Console address: %MW0 6 %MW2:=16#0000;
%MW3:=16#0400;
%MW4:=16#0000;
%MW5:=16#0000;
or
%MW0:6:=ADR#0.0.4;
ADR syntax Example: -

Parameters
Console address: ADR#0.0.4

- DOP_Function(ADR#0.0.4,...

TLX DS 57 PL7 xx 343

Built-in DOP functions

For a slave CCX 17 connected to a TSX Premium master PLC via the built-in
FIPIO link (channel 1) positioned in rack 0 (connection point no. 7).
Addresses can be entered in many ways (example here using constant words
%KW0 to %KW5):
If you use: in the function entry Help screen… you must enter the program…
internal (or Example: %KW0:=16#0700;
constant) words %KW1:=16#FE00;
Parameters
Console address: %KW0 6 %KW2:=16#0000;
%KW3:=16#0701;
%KW4:=16#00FE;
%KW5:=16#0000;
or
%KW0:6:=ADR#\0.1.7\SYS,...;
ADR syntax Example: -

Parameters
Console address: ADR#\0.1.7\SYS

- DOP_Function(ADR#\0.1.7\SYS,
...

Note: If using constants, the %KW0:6 table must be initialized beforehand using
the Data editor by successively assigning the %KWi which make up the table.

344 TLX DS 57 PL7 xx

 Built-in DOP functions

Parameters field: Data to be sent

Introduction Data to be sent is individual to each type of MMI function.

The data can be found either in the PLC application, or in the CCX 17 when it has
its own application.

Locating items In the case where data is to be found in the PLC application, it can be sent from:
within the PLC l a table of internal words (%MW),
application l a table of internal constants (%KW).
The table below shows the structure of data sent in this way.
Word Role
number
1 Contains a contains a marker for value 16#CC17, and has a double role:
l it allows the Help screen to identify a correct message and to redisplay the
values on the entry screen in order to help modify or display default values.
l it allows the function being carried out to check that the table received does
actually contain a message for a CCX 17. In fact, it is possible to call an
Integrated DOP function in a program without going via the Help/Control
screens.
In the case of an unmarked message, the function can immediately return an
error back to the application without sending unreliable data to the console.
2 Contains the command number.
3 Contains the length of data to be sent.
4, 5, ... Contains the data to be sent.

Note: For reasons of efficiency, the <Data to be sent> parameter can be

programmed using %KWi constants. In this way the software automatically
initializes this data field with adequate values.
Selecting %MW bars access to different fields in the entry help box for integrated
DOP functions. It is then necessary to establish, either manually or by program, the
contents of the data to be sent (see PL7 MMI 17 software documentation).

TLX DS 57 PL7 xx 345

Built-in DOP functions

Location in a When data is in a CCX 17, the data to be sent is limited to DOP function execution
CCX 17 with commands.
application This data can be sent from the PLC application:
l from a table of internal words (%MW),
l from a table of internal constants (%KW),
l directly using an immediate integer value.
The table above shows data structure when using a table.
Word Role
number
1 Contains a command number
2 Contains the data to be sent to the console.

346 TLX DS 57 PL7 xx

 Built-in DOP functions

Parameter field: Data to be received:

Introduction This parameter only affects functions ASK_MSG and ASK_VALUE.

The data is located in an %MWi internal word table (length 2 table maximum).

Note: By operating the MMI console, the Data to be received parameter contains
the value entered. If the status message variable is different from the data to be
received, it is not changed by the entry. It only affects the display on the CCX 17.

TLX DS 57 PL7 xx 347

Built-in DOP functions

Parameters field: Report

Introduction The report contains the parameters for managing asynchronous communication
functions.
It is common to all integrated DOP functions.

Report structure The report uses a table of four internal words (%MW) containing different
parameters such as:
l information on function activity,
l the exchange number which identifies the transaction in progress (useful when
using the CANCEL communication function),
l the exchange report split into two feedback codes:
l the communication level,
l the operation level,
l the value of the timeout which is used to monitor absent responses,
l the number of bytes to be sent and/or the number of bytes received.

The table below show the structure of the report.

Word number Most significant Least significant byte Report management
byte
%MWi Exchange number Bit 0: activity bit System
%MWi+1 Operation report Communication report System
%MWi+2 Timeout User
%MWi+3 Length System

%MWi:X0 activity This bit indicates the state of the application of the communication function.
bit It is set on 1 when the function starts and falls back to 0 when a response is received,
at the end of a timeout, or if the operation is cancelled (CANCEL function).

Exchange While a function is being sent, the system automatically assigns it a number which
number is used to identify the exchange.
This number serves as a reference to stop the exchange in progress, if necessary
(on using CANCEL).

348 TLX DS 57 PL7 xx

 Built-in DOP functions

Communication The communication report provides information on the communication aspect of the
report transaction.
This report is significant when the value of the activity bit changes from 1 to 0.

Note: The communication report does not affect the ADJUST function.

The different values of this report are indicated in the following table:
Value Significance of the communication report (least significant byte)
16#xx00 Successful exchange
16#0001 Stopping the exchange via a timeout
16#0002 Stopping the exchange on user request (CANCEL function)
16#0003 Incorrect address format (length is other than 6)
16#0004 Incorrect destination address (addresses unauthorized for the CCX 17, e.g.:
addresses being broadcast)
16#0005 Invalid report
16#xx06 Specific parameters are invalid (particularly those concerning data to be sent)
16#0007 Destination missing
16#0008 Reserved
16#0009 Size of reception buffer is insufficient
16#000A Size of transmission buffer is insufficient
16#000B System resources missing (communication saturation)
16#xx14 Negative response from the CCX 17 or from the PLC (ADJUST function)
16#00FF Message refused (the CCX 17 is not in a state where it can process it)

Note: The function can detect an error in the parameters before activating the
exchange. In this case the activity bit remains 0, the report is initialized with the
values corresponding to the fault.

TLX DS 57 PL7 xx 349

Built-in DOP functions

Operation report The operation report details the result of the operation on the remote application.
It is significant if the communication report has the following values:
l 16#00,
l 16#06,
l 16#14 (except for the ADJUST function).
In other cases, the operation report is worth 0.

The different values of this report are indicated in the following table:
Communication report Significance of the operation report Integrated DOP
(least significant byte) functions
16#0000 Generic positive result All
16#1006 Number of management words below 24 ADJUST only
16#1106 Non-existent type object to be read (greater than 8)
16#1206 Inconsistency between bits RDEC and SINC
16#1306 Invalid value to be written
16#1406 Broadcast address (ALL) prohibited All except ADJUST
16#6506 {network.station} pair different from {0.254}
16#6606 Data to be sent does not have a 16#CC17 marker
16#6706 Invalid size of data to be sent
16#6806 Invalid CCX 17 response
16#6906 Length of "Data to be received" is insufficient
16#FF06 CCX 17 link inoperational
16#0114 Command not recognized
16#0214 Command queue capacity has been exceeded
16#0414 Size of command is less that the minimum required size
16#0814 Command refused because application transfer in progress
16#1414 Inaccessible object ADJUST only
16#1514 System error
16#2014 Incorrect data All except ADJUST

350 TLX DS 57 PL7 xx

 Built-in DOP functions

Timeout Timeout determines the maximum waiting time for a response. The time base for
this parameter is 100 ms.
value 0 corresponds to an infinite wait value. In this case, the CANCEL function
should be used.

Note: Value 0 is mandatory for functions ASK_MSG and ASK_VALUE.

If the timeout period has elapsed, the exchange terminates with an error report
(value 1). Similarly, the system refuses any response received at the end of the
timeout.

Example

Activity bit = 1
Start function
Timeout activation
Report set to zero
Allocation of exchange number

End of timeout
Receive response

Activity bit = 0
Stop timeout
Activity bit = 0
Report update
Report = 1

Note: The timeout value of a communication function must be sufficient to

guarantee receiving a response to the question asked. This time period depends
on the type of network and on the load in effect at the moment of the transaction.

Length The length parameter is used to store the number of bytes received after receiving
a message for functions ASK_MSG and ASK_VALUE.
For the other functions, this parameter is worth 0.

TLX DS 57 PL7 xx 351

Built-in DOP functions

Message field

Introduction The message field groups together the different elements that make up the data to
be displayed on the CCX 17 screen.
These elements are:
l the message text,
l the different display attributes (position, size, etc.).
l the message print command via the CCX 17.

Message text This field is used to enter the message text that is to be displayed on the CCX 17
console.
The length of the message is 40 characters max.

The table below details the types of characters authorized.

Characters Comments
ASCII code above 32 (20h) Characters that can be displayed directly or by a combination
of the and keys.
The _ sign (underscore) This character is reserved by the system to specify the
optional display field for the variable associated with the
message.
To specify the position of the variable field, the character must
be entered in the appropriate place. The system then
automatically calculates the number of necessary for the
length of the variable display.

Print This parameter orders the command console to print a message when it appears on
the console screen.

Overprint This parameter refers to alarm messages only. Enabling this parameter overprints
the alarm message as soon as it appears.

Line This parameter specifies the line where the message must be displayed.
Position Value
Minimum 1
Default 1
Maximum 16

352 TLX DS 57 PL7 xx

 Built-in DOP functions

Column This parameter specifies the column where the first message character is
positioned.
Position Value(s)
Minimum 1
Default 1
Maximum 40
Automatic (1) Left, Centered, Right

Key
(1) This mode can be accessed by selecting automatic mode. It is local
to the function.

Attributes This parameter sets the attributes of the message display.

The different modes are:
l Normal (when no check box has been selected),
l Flashing,
l Reverse video.

Size This parameter specifies the format of all the text characters or the variable to be
displayed.
Possible options are:
l Standard,
l Double.

Clear This field is used to associate a single command that has been executed with a
message before the message has been displayed.
Options are:
l None (no command is associated with a message),
l Line (clears the line on which the message is to be displayed),
l Screen (completely clears the screen).

Note: If no variable has been associated with a message, this command does not
run (so use the PANEL_CMD function).

TLX DS 57 PL7 xx 353

Built-in DOP functions

Field zone

Introduction The Field zone is used to set the different parameters for the object which is
associated with a message.
These parameters are:
l the type of object,
l the display format,
l ...

Field type This parameter sets the type of object which is associated with a message.
The length of the message is 40 characters max.

The table below shows the different object types possible.

Type of object Description
None No field is associated with the message displayed.
Address The object associated with the message is a variable.
Date The message is correlated to the current PLC date.
Time The message is correlated to the current PLC time.

Symbol This parameter specifies the symbol of the variable associated with the message. It
must be set in the station database. The address associated with this symbol is
automatically taken into account on confirming the screen.

Note: In the case of a TSX Agent connected to the FIPIO bus, the variable is read
in the bus master PLC, and not in the function sender PLC.

Address This parameter specifies the address of the variable associated with the message.
When a symbol is associated with the variable, it is automatically taken into account.
Authorized objects can be:
l internal bits (%Mi),
l internal words (%MWi),
l double internal words (%MDi).

Comment This field displays the variable comment for viewing. This comment is set in the
application data editor.

354 TLX DS 57 PL7 xx

 Built-in DOP functions

Refresh This function specifies whether the variable contained in the message should be
periodically refreshed while being displayed (function is active be default).

Display format This parameter specifies the variable display format.

The table below shows the different formats available.
Format Associated parameters
ASCII -
Numerical Signed (1)
Number of digits before the decimal point (1),
Number of digits after the decimal point (1),

Key
(1) these associated parameters can be accessed by clicking on the Modify
button.

Note: From the parameters chosen, the software automatically calculates the
display format.

TLX DS 57 PL7 xx 355

Built-in DOP functions

25.2 Description of the built-in DOP functions

Introduction

Subject of this This section describes the different built-in DOP functions.
section

What's in this This Section contains the following Maps:

Section?
Topic Page
List of the built-in DOP functions 357
SEND_MSG function 358
GET_MSG function 361
ASK_MSG function 364
SEND_ALARM function 366
DISPLAY_MSG function 369
DISPLAY_GRP function 370
DISPLAY_ALRM function 372
ASK_VALUE function 374
GET_VALUE function 375
CONTROL_LEDS function 377
ASSIGN_KEYS function 380
PANEL_CMD function 383
ADJUST function 386

356 TLX DS 57 PL7 xx

 Built-in DOP functions

List of the built-in DOP functions

Introduction The built-in DOP functions make it possible to:

l control the main functions of a CCX 17 console not containing an application (this
has been neither configured nor loaded by the external design software).
l command a CCX 17 console containing an application created with the MMI17
WIN or PL7 M17 OS/2 products.
The table below shows the various built-in DOP functions.
Function Description Application
Witho With
ut
SEND_MSG Displaying status messages contained in the PLC memory on CCX 17 with or X -
without variable.
GET_MSG Free entry (asynchronous) of PLC variable values associated with status X -
messages.
ASK_MSG Blocking entry (synchronous) of a PLC variable value associated with status X -
messages.
SEND_ALARM Displaying alarm messages contained in the PLC memory. X -
DISPLAY_MSG Displaying a status message contained in the memory of the CCX17. - X
DISPLAY_GRP Displaying a group of status messages contained in the CCX17 memory. - X
DISPLAY_ALRM Displaying an alarm message contained in the CCX17 memory. - X
ASK_VALUE Blocking entry (synchronous) of values for the PLC variables associated with - X
a status message contained in the CCX17 memory.
GET_VALUE Free entry (asynchronous) of values for the PLC variables associated with a - X
status message contained in the CCX17 memory.
CONTROL_LEDS Controlling the CCX 17 LEDs and relays. X X
ASSIGN_KEYS Configuring the CCX 17 command keys. X X
PANEL_CMD Sending a generic command. X X
ADJUST Language object adjustment. X X

TLX DS 57 PL7 xx 357

Built-in DOP functions

SEND_MSG function

Role This function is used to display a message with a dynamic variable (if necessary) on
a CCX 17 console screen.

Implementation Implementation of the SEND_MSG function is developed in the Description of

parameters (See Description of the parameters common to the different DOP
functions, p. 340 ) section.

Application The example given below makes use of the SEND_MSG function to display two
example status messages on the screen of a T CCX 1720 W console without an application.
This is connected to a TSX Premium via the AUX port (configured in UNI-TELWAY
link, addresses 4 - 5).

Note: This same example, using a CCX 17 with application, is shown using the
DISPLAY_GRP function.

Application description Variables used

The aim of this example is, after setting application to RUN (%S13 =1): %MW0:6: console address
l initializing the PLC variables, %KW0:x: message 1 data to send
l writing the console address (ADR#0.04) in a word table, %KW40:x: message 2 data to send
l adjustment of timeout to 50 s, %MW100:4: report
l conditions of execution, %MW100:X0: activity bit
l clearing the console screen (see PANEL_CMD function), %MW102: timeout
l to display status messages on the console screen: %M100:2: conditions of activation,
l Manu and Auto (standard format, positioned on line 1, Column 1),
l Four 4 (double format, automatic centering, Line 4),
l storing the function display execution.

358 TLX DS 57 PL7 xx

 Built-in DOP functions

Introduction to the console Program corresponding to the application

Fixed messages (* INIT console address, condition, timeout

*)
IF %S1.3 THEN
%MW0:6:=ADR#0.0.4;
Manu Auto
%MW102:=500;
%M100:2:=0;
Four 4 END_IF;
(*Write Auto, Manu and Four4 messages*)
IF NOT %M100 AND NOT %MW100:X0 THEN
SEND_MSG(%MW0:6,%KW0:28,%MW100:4);
SET %M100;
END_IF;
IF NOT %M101 AND NOT %MW100:X0 THEN
SEND_MSG(%MW0:6,%KW0:28,%MW100:4);
SET %M101;
END_IF;

TLX DS 57 PL7 xx 359

Built-in DOP functions

Entry help screens corresponding to the application:

SEND_MSG
Parameters
Console address: %MW0 6 Report: %MW100 4
Data to Send: %KW0 28
Message
Text: Manu Auto Print
Position Attributes Size
Mode Line 1 Column 1 Flashing Standard
Manual Column alignment Reverse video Double
SEND_MSG
Auto Left Centered Right Clear Parameters
None Console
Line address:
Scree %MW0 6 Report: %MW100 4
Data to Send: %KW40 12
Field
Message
Field type
None Address Date Text:TimeFour 4 Print
Position Attributes Size
Symbol: Address: Mode Update Line 4 Column 15 Flashing Standard
Comment: Manual Column alignment Reverse video Double
Display format
Auto Left Centered Right Clear
Modify
None Line Scree

OK Cancel Field
Field type
None Address Date Time

Symbol: Address: Update

Comment:
Display format
Modify

OK Cancel

360 TLX DS 57 PL7 xx

 Built-in DOP functions

GET_MSG function

Role This function is used to display, on the screen of a CCX 17 console, a message with
a variable which can be modified by the operator.
The entry is made in multiple mode. The operator thus has the possibility of entering
several variables successively, and the PLC program processes the entered value
when the variable appears.

Implementation Implementation of the GET_MSG function is developed in the Description of

parameters (See Description of the parameters common to the different DOP
functions, p. 340) section.

Specific The Value parameter specifies the characteristics of the value which is associated
parameter: Value to the variable.
If the choice is… The value…
Not checked entry on the CCX 17 console keyboard is free (1).
Limited entry on the CCX 17 console keyboard must be within the limits defined
by the Min and Max values in the Entry field in order to be taken into
account by the application (1).
Increment display on the CCX 17 console screen is incremented or decremented
from the value of the increment (1).

Key
(1) The value or the increment entered on the CCX 17 console keyboard
follows the display format (e.g.: 9999.99), this determines the whole
parts and decimal parts authorized by the user entry.

TLX DS 57 PL7 xx 361

Built-in DOP functions

Example of The example given below makes use of the GET_MSG function to display a status
application message containing a variable which can be modified on the screen of a T CCX
1720 W console without application.
This is connected to a TSX Premium via the AUX port (configured in UNI-TELWAY
link, addresses 4 - 5).

Note: This same example, using a CCX 17 with application, is shown using the
GET_VALUE function.

Application description Variables used

Initial conditions %MW0:6: console address
l writing the console address (ADR#0.04) in a table of words, %KW80:x: data to be sent.
l adjustment of timeout to 50 s, %MW100:4: report
l condition of execution, %MW100:X0: activity bit
Application: The aim of this example is, on user request: %MW102: timeout
l to display a status message on the console screen: %M102: activation condition
l Temperature = xxx °C (standard format, automatic centering, %MW10: Temperature variable
Line 6, variable with attributes: increment of 50, three-digit integer,
periodic refreshing),
l storing the function execution.

Introduction to the console Program corresponding to the application

Message displayed on user request (* INIT console address, condition, timeout

*)
IF %S1.3 THEN
%MW0:6:=ADR#0.0.4;
%MW102:=500;
%M102:=0;
Temperature = xxx °C END_IF;
(* Write message Temp… *)
IF NOT %M102 AND NOT %MW100:X0 THEN
GET_MSG(%MW0:6,%KW100:28,%MW100:4);
SET %M102;
END_IF;

362 TLX DS 57 PL7 xx

 Built-in DOP functions

Entry help screen corresponding to the application:

GET_MSG
Parameters
Console address: %MW0 Report: %MW100 4
Data to Send: %KW1000 34
Message
Text: Temperature=____°C Print
Position Attributes Size
Mode Line 6 Column 11
Manual Column alignment Flashing Standard
Auto Left Centered Right Reverse video Double

Field
Symbol: Address: %MV10 Update
Comment:
Display format
999 Modify

Entry
Value
Not Checked Limited Increment

Increment: 50

Ok Cancel

TLX DS 57 PL7 xx 363

Built-in DOP functions

ASK_MSG function

Role This function is used to display, on the screen of a CCX 17 console, a message with
a variable which can be modified by the operator.
The entry is made in synchronized mode. Therefore, it is possible to make one
single operator entry at each message display.

Implementation Implementation of the ASK_MSG function is developed in the Description of

parameters (See Description of the parameters common to the different DOP
functions, p. 340 ) section.

Note: It is strongly advisable to assign parameters for the timeout for an infinite
period (see Parameters field: Report, p. 348 so as not to invalidate the ASK_MSG
function before the operator entry is made.

Specific The Value parameter specifies the characteristics of the value which is associated
parameter: Value to the variable.
If the choice is… The value…
Not checked entry on the CCX 17 console keyboard is free (1).
Limited entry on the CCX 17 console keyboard must be within the limits defined
by the Min and Max values in the Entry field in order to be taken into
account by the application (1).
Increment display on the CCX 17 console screen is incremented or decremented
from the value of the increment (1).

Key
(1) The value or the increment entered on the CCX 17 console keyboard
follows the display format (e.g.: 9999.99), this determines the whole
parts and decimal parts authorized by the user entry.

364 TLX DS 57 PL7 xx

 Built-in DOP functions

Example The illustration below shows an example of ASK_MSG function entry.

ASK_MSG
Parameters
Console address: ADR#,LL0.1.7,SYS Data to receive: %KW200 2
Data to Send: %KW20 34 Report: %KW10 4
Message
Text: ASK MSG:_ Print
Position Attributes Size
Mode Line 5 Column 5
Manual Column alignment Flashing Standard
Auto Left Centered Right Reverse video Double

Field
Symbol: Address: %MV100
Comment:
Display format
99 Modify

Entry
Value
Not Checked Limited Increment

Ok Cancel

TLX DS 57 PL7 xx 365

Built-in DOP functions

SEND_ALARM function

Role This function is used to activate, on the screen of a CCX 17 console, an alarm
message present in the PLC.

Note: Alarm messages are always displayed on the second line of the screen
(Superimpose parameter activated). They are dated and timed by the console
which synchronizes them with the PLC clock.

Implementation Implementation of the SEND_ALARM function is developed in the Description of

parameters (See Description of the parameters common to the different DOP
functions, p. 340 ) section.

Note: It is imperative that the associated message in the CCX 17 console is

deactivated on the disappearance of the alarm in the PLC (see function
PANEL_CMD), in order to enable a potential new activation of this alarm.

Specific The Alarm number parameter defines the alarm message identifier.
parameter: Its value is between 900 and 999.
Alarm number

Example of The example given below makes use of the SEND_ALARM function to display an
application alarm message on the screen of a T CCX 1720 W console without application.
This is connected to a TSX Premium via the AUX port (configured in UNI-TELWAY
link, addresses 4 - 5).

Note: This same example, using a CCX 17 with application, is shown using the
DISPLAY_ALARM function.

366 TLX DS 57 PL7 xx

 Built-in DOP functions

Application description Variables used

Initial conditions %MW0:6: console address
l writing the console address (ADR#0.04) in a table of words, %KW80:x: data to be sent.
l adjustment of timeout to 50 s, %MW100:4: report
l condition of execution, %MW100:X0: activity bit
Application: The aim of this example is: %MW102: timeout
l to detect overshoot of a temperature threshold (500 °C), %M103: activation condition
l to display an alarm message on the console screen: %MW10: Temperature variable
l Overheat four = xxx °C (standard format, automatic setting
imposed by the function, variable with attributes: increment of 50,
three-digit integer),
l storing the function execution.

Introduction to the console Program corresponding to the application

System display Alarm message (*INIT console address, condition, timeout

*)
*ALARM* IF %S1.3 THEN
Oven overheating = xxx °C %MW0:6:=ADR#0.0.4;
%MW102:=500;
%M103:=0;
END_IF;
(*Time overrun control*)
IF %MW10>500 THEN
SET %M12;
ELSE RESET %M12;
END_IF;
(* Write Surch alarm message… *)
IF %M12 AND NOT %M103 AND NOT %MW100:X0 THEN
SEND_ALARM(%MW0:6,%KW0:27,%MW100:4);
SET %M103;
END_IF;

TLX DS 57 PL7 xx 367

Built-in DOP functions

Entry help screen corresponding to the application:

SEND_ALARM
Parameters
Console address: %MW0 6 Report: %MW110 4
Data to be sent: %KW120 29
Message
Text: Oven overheating = ____°C Print
Size
Alarm number: 901 Standard Double Overprint

Field
Symbol: Address: %MW10
Comment:
Display format
999 Modify

OK Cancel

368 TLX DS 57 PL7 xx

 Built-in DOP functions

DISPLAY_MSG function

Role This function is used to display a message contained in the CCX 17 operator dialog
console memory.

Implementation Implementation of the DISPLAY_MSG function is developed in the Description of

parameters (See Description of the parameters common to the different DOP
functions, p. 340) section.

Specific The Message number parameter defines the alarm message identifier contained in
parameter: the CCX 17 memory.
Message number Its value is between 1 and 300.

Example The illustration below shows an example of DISPLAY_MSG function entry.

DISPLAY_MSG
Parameters
Console address: ADR# 0.0.4 Report: %MW10 4
Data to be sent: %KW200

Value of data to be sent

Message number: 1

OK Cancel

TLX DS 57 PL7 xx 369

Built-in DOP functions

DISPLAY_GRP function

Role This function is used to simultaneously display a group of messages contained in

the CCX17 operator dialog console memory.

Implementation Implementation of the DISPLAY_MSG function is developed in the Description of

parameters (See Description of the parameters common to the different DOP
functions, p. 340 ) section.

Specific The Message group number parameter defines the group message identifier
parameter: contained in the CCX 17 memory.
Message group Its value is between 1 and 100.
number

Example of The example given below makes use of the DISPLAY_GRP function to display a
application group of two status messages on the screen of a T CCX 1720 W console containing
an application.
This is connected to a TSX Premium via the AUX port (configured in UNI-TELWAY
link, addresses 4 - 5).

Note: This same example, using a CCX 17 without application, is shown using the
SEND_MSG function.

Application description Variables used

The aim of this example is, after setting application to RUN (%S13 =1): %MW0:6: console address
l initializing the PLC variables, %KW0:x: message 1 data to send
l writing the console address (ADR#0.04) in word table, %MW100:4: report
l adjustment of timeout to 50 s, %MW100:X0: activity bit
l condition of execution, %MW102: timeout
l clearing the console screen (see PANEL_CMD function), %M100: activation condition
l displaying the group of state n°1 messages contained in the CCX 17
application, for:
l message n°1: Manu and Auto (standard format, moved to line 1,
Column 1),
l message n°2: Four 4 (double format, automatic centering, Line 4),
l storing the function execution.

370 TLX DS 57 PL7 xx

 Built-in DOP functions

Introduction to the console Program corresponding to the application

Fixed messages (* INIT console address, condition, timeout

*)
IF %S1.3 THEN
%MW0:6:=ADR#0.0.4;
Manu Auto
%MW102:=500;
%M100:=0;
Oven 4 END_IF;
(*Write Auto, Manu and Four4 messages*)
IF NOT %M100 AND NOT %MW100:X0 THEN
DISPLAY_GRP(%MW0:6,%KW0,%MW100:4);
SET %M100;
END_IF;

Entry help screen corresponding to the application:

DISPLAY_GRP
Parameters
Console address: %MW10 6 Report: %MW100 4
Data to be sent: %KW0

Value of data to be sent

Message group number: 1

OK Cancel

TLX DS 57 PL7 xx 371

Built-in DOP functions

DISPLAY_ALRM function

Role This function is used to display an alarm message contained in the CCX17 operator
dialog console memory.

Implementation Implementation of the DISPLAY_ALRM function is developed in the Description of

parameters (See Description of the parameters common to the different DOP
functions, p. 340 ) section.

Note: It is imperative that the associated message in the CCX 17 console is

deactivated on the disappearance of the alarm in the PLC (see function
PANEL_CMD), in order to enable a potential new activation of this alarm.

Specific The Alarm message number parameter defines the alarm message identifier
parameter: contained in the CCX 17 memory.
Alarm message Its value is between 1 and 300.
number
An alarm can be activated exclusively by:
l letter box (requires MMI 17 WIN software),
l built-in DOP functions

Note: Only the alarms with numbers higher than the length of the letterbox can be
accessed by the DISPLAY_ALRM function.

Application The example given below makes use of the DISPLAY_ALRM function to display an
example alarm message on the screen of a T CCX 1720 W console containing an application.
This is connected to a TSX Premium via the AUX port (configured in UNI-TELWAY
link, addresses 4 - 5).

Note: This same example, using a CCX 17 with application, is shown using the
SEND_ALRM function.

372 TLX DS 57 PL7 xx

 Built-in DOP functions

Application description Variables used

Initial conditions %MW0:6: console address
l writing the console address (ADR#0.04) in a word table, %KW80:x: data to be sent.
l adjustment of timeout to 50 s, %MW100:4: report
l condition of execution, %MW100:X0: activity bit
Application: The aim of this example is: %MW102: timeout
l to detect overshoot of a temperature threshold (500 °C), %M103: activation condition
l to display the alarm message contained in the CCX 17 application, for: %MW10: Temperature
l Overheat four = xxx °C (standard format, automatic setting imposed by the variable
function, variable with attributes: increment of 50, three-digit integer),
l storing the function execution.

Introduction to the console Program corresponding to the application

System display Alarm message (*INIT console address, condition, timeout

*)
*ALARM* IF %S1.3 THEN
Oven overheating = xxx °C %MW0:6:=ADR#0.0.4;
%MW102:=500;
%M103:=0;
END_IF;
(*Time overrun control*)
IF %MW10>500 THEN
SET %M12;
ELSE RESET %M12;
END_IF;
(* Write Surch alarm message… *)
IF %M12 AND NOT %M103 AND NOT %MW100:X0 THEN
DISPLAY_ALRM(%MW0:6,%KW0,%MW100:4);
SET %M103;
END_IF;

Entry help screen corresponding to the application:

DISPLAY_ALRM
Parameters
Console address: %MW0 6 Report: %MW100 4
Data to be sent: %KW150

Value of data to be sent

Number of alarm message: 1

OK Cancel

TLX DS 57 PL7 xx 373

Built-in DOP functions

ASK_VALUE function

Role This function is used to display a status message contained in the CCX17 operator
dialog console memory on a CCX 17 console screen.
This message includes a variable, which can be modified by the operator.
The entry is made in synchronized mode. Therefore, it is possible to make one
single operator entry at each message display.

Implementation Implementation of the ASK_VALUE function is developed in the Description of

parameters (See Description of the parameters common to the different DOP
functions, p. 340 ) section.

Note: It is strongly advisable to assign parameters for the timeout for an infinite
period (see Parameters field: Report, p. 348 so as not to invalidate the
ASK_VALUE function before the operator entry is made.

Specific This parameter defines the message identifier contained in the CCX 17 memory.
parameter: Its value is between 1 and 300.
Status message
number

Example The illustration below shows an example of ASK_VALUE function entry.

ASK_VALUE
Parameters
Console address: ADR# 0.0.4 6 Data to receive: %MW10 2
Data to be sent: %KW20 Report: %MW20 4

Value of data to be sent

Status message number: 3

OK Cancel

374 TLX DS 57 PL7 xx

 Built-in DOP functions

GET_VALUE function

Role This function is used to display a status message contained in the CCX17 operator
dialog console memory on a CCX 17 console screen.
This message includes a variable, which can be modified by the operator.
Entry is made in multiple mode. The operator thus has the possibility of entering
several variables successively, and the PLC program processes the entered value
when the variable appears.

Implementation Implementation of the GET_VALUE function is developed in the Description of

parameters (See Description of the parameters common to the different DOP
functions, p. 340) section.

Specific This parameter defines the message identifier contained in the CCX 17 memory.
parameter: Its value is between 1 and 300.
Status message
number

Application The example given below makes use of the GET_VALUE function to display a status
example message containing a variable on the screen of a T CCX 1720 W console containing
an application.
This is connected to a TSX Premium via the AUX port (configured in UNI-TELWAY
link, addresses 4 - 5).

Note: This same example, using a CCX 17 without application, is shown using the
GET_MSG function.

Application description Variables used

Initial conditions %MW0:6: terminal address
l writing the console address (ADR#0.04) in a word table, %KW80:x: data to be sent.
l adjustment of timeout to 50 s, %MW100:4: report
l condition of execution, %MW100:X0: activity bit
Application: The aim of this example is, on user request: %MW102: timeout
l initializing the PLC variables, %M102: activation condition
l displaying message n°4 contained in the CCX17 application, for: %MW10: Temperature variable
l Temperature = xxx °C (standard format, automatic centering,
Line 6, variable with attributes: increment of 50, three-digit integer,
periodic updating),
l storing the function execution.

TLX DS 57 PL7 xx 375

Built-in DOP functions

Introduction to the console Program corresponding to the application

Message displayed on user request (*INIT console address, condition, timeout

*)
IF %S1.3 THEN
%MW0:6:=ADR#0.0.4;
%MW102:=500;
%M102:=0;
Temperature = xxx °C END_IF;
(* Write message Temp… *)
IF NOT %M102 AND NOT %MW100:X0 THEN
GET_VALUE(%MW0:6,%KW100:28,%MW100:4);
SET %M102;
END_IF;

Entry help screen corresponding to the application:

GET VALUE
Parameters
Console address: %MW0 6 Report: %MW100 4
Data to be sent: %KW100

Value of data to be sent

Status message number: 4

OK Cancel

376 TLX DS 57 PL7 xx

 Built-in DOP functions

CONTROL_LEDS function

Role This function is used to control some CCX 17 console functions.

These functions are:
l relay state (version 2.1 and above),
l state of the small luminous column LEDs.
The CONTROL_LEDS function is available whether or not the CCX 17 has an
application.

Implementation Implementation of the CONTROL_LEDS function is developed in the Description of

parameters (See Description of the parameters common to the different DOP
functions, p. 340) section.

Specific This parameter defines the current status of each LED.

parameter: LED the various states can be:
status l Unchanged,
l Off,
l Flashing,
l On.

Specific This parameter defines the relay status.

parameter: Relay the various states can be:
status l Unchanged,
l Open,
l Closed.

TLX DS 57 PL7 xx 377

Built-in DOP functions

Application The example given below makes use of the CONTROL_LEDS function to control the
example T CCX 1720 W console’s green LED status.
This is connected to a TSX Premium via the AUX port (configured in UNI-TELWAY
link, addresses 4 - 5).

Application description Variables used

Initial conditions %MW0:6: terminal address
l writing the console address (ADR#0.04) in a word table, %KW200:x:Manu status data to send
l adjustment of timeout to 50 s, %KW210:x: Auto status data to send
l condition of execution, %MW100:4: report
Application: The aim of this example is, on rising edge of the variables: %MW100:X0: activity bit
l Manu: controlling the green LED in Flashing mode, %MW102: timeout
l Auto: controlling the green LED inOn mode %M0:Manu variable
%M2: Auto variable

Introduction to the console Program corresponding to the application

Green LED (*INIT console address, condition, timeout

*)
IF %S1.3 THEN
%MW0:6:=ADR#0.0.4;
%MW102:=500;
%M100:2:=0;
END_IF;
(*State of green LED*)
IF RE %M0 AND NOT %MW100:X0 THEN
CONTROL_LEDS(%MW0:6,%KW200:2,%MW100:4);
END_IF;
IF RE %M2 AND NOT %MW100:X0 THEN
CONTROL_LEDS(%MW0:6,%KW210:2,%MW100:4);
END_IF;
%M0:=%M0;
%M2:=%M2;

378 TLX DS 57 PL7 xx

 Built-in DOP functions

Entry help screens corresponding to the application:

CONTROL_LEDS
Parameters
Console address: %MW0 6 Report: %MW100 4
Data to Send: %KW200 2
LED status

Unchanged Off Flashing On

Unchanged Off Flashing On

Unchanged Off Flashing On

Relay status CONTROL_LEDS

Parameters
Unchanged Open Closed
Console address: %MW0 6 Report: %MW100 4
Data to Send: %KW210 2
OK Cancel LED status

Unchanged Off Flashing On

Unchanged Off Flashing On

Unchanged Off Flashing On

Relay status
Unchanged Open Closed

OK Cancel

TLX DS 57 PL7 xx 379

Built-in DOP functions

ASSIGN_KEYS function

Role This function is used to configure all or some of the command keys of a CCX 17
console by linking them to internal bits from the communication master PLC.
Using this function globally modifies the configuration of the affected command
keys.
The maximum number of keys that can be configured is twelve, however, only the
keys present on the console receiving the command are taken into account.

The ASSIGN_KEYS function is available whether or not the CCX 17 has an

application.

Parameters Zone The principle of implementing the Parameters zone is elaborated in the Description
of parameters (See Description of the parameters common to the different DOP
functions, p. 340 ) section.

Zone: Set by This zone is used to specify which out of the PLC or CCX 17 contains the key
configuration data.
l PLC: the data considered is that entered in the Command key zones,
l CCX 17 the data considered is that from the application contained in the console.

Zone: Command This zone is used to define the characteristics associated with each key.
key x The table below shows the various possible characteristics.
Characteristics Meaning
Inhibit Invalidates the key status. Its confirmation inhibits the action and address
/ symbol fields.
Action Defines the operating mode of the key.
Selecting the mode on edge means that pushing in the key causes the
associated bit to be set to 1, and releasing it causes it to be set to 0.
Choosing counter output mode means that pushing in the key changes
the bit status. The default value is on edge.
Address Specifies the %Mi internal bit address associated with the key. If the
symbol associated with this bit exists in the station database, it is
automatically taken into account during address confirmation.
Symbol Specifies the symbol associated with the bit. The address associated with
this symbol is automatically taken into account.

Zone: Display Command keys are configured in groups of four.

command keys This zone is used to access the various groups of keys.

380 TLX DS 57 PL7 xx

 Built-in DOP functions

Application The example given below makes use of the ASSIGN_KEYS function to assign a
example function to the T CCX 1720 W console command keys1 and 2.
This is connected to a TSX Premium via the AUX port (configured in UNI-TELWAY
link, addresses 4 - 5).

Note: For a CCX 17 with application, the assignment of command keys can be
included here, making this PLC application unnecessary.

Application description Variables used

Initial conditions %MW0:6: terminal address
l writing the console address (ADR#0.0.4) in a word table, %KW240:x: data to be sent.
l adjustment of timeout to 50 s, %MW100:4: report
l condition of execution, %MW100:X0: activity bit
Application: The aim of this example is: %MW102: timeout
l to assign the %M0 variable to command key 1, %M0: Manu variable
l to assign the %M2 variable to command key 2, %M2: Auto variable
l storing the function execution. %M12: condition of execution
%M108: condition of execution

Introduction to the console Program corresponding to the application

Key 1 Key 2 (* INIT console address, condition, timeout

*)
IF %S1.3 THEN
%MW0:6:=ADR#0.0.4;
%MW102:=500;
%M108:=0;
END_IF;
(* Assign command keys *)
IF %M12 AND NOT %M108 AND NOT %MW100:X0 THEN
ASSIGN_KEYS(%MW0:6,%KW240:16,%MW100:4);
END_IF;

TLX DS 57 PL7 xx 381

Built-in DOP functions

Entry help screens corresponding to the application:

ASSIGN_KEYS
Parameters
Console address: %MW0 6 Report: %MW100 4
Data to Send: %KW240 16

Set by
PLC CCX17

Command key 1 Command key 2

Inhibit Action Inhibit Action
Symbol: Manual On edge Symbol: Auto On edge
Address: %MV0 On state Address: %M2 On state
Command key 3 Command key 4
Inhibit Action Inhibit Action
Symbol: On edge Symbol: On edge
Address: On state Address: On state

Key 1 to 4... Key 5 to 8... Key 9 to 12...

Display command keys OK Cancel

382 TLX DS 57 PL7 xx

 Built-in DOP functions

PANEL_CMD function

Role This function is used to send various simple commands of the following type to the
MMI console:
l clearing a line or the screen,
l printing or clearing the operator entry log,
l printing or clearing the alarms log,
l alarm management.

Note: The PANEL_CMD function is available whether or not the CCX 17 has an
application.

Parameters field The principle of implementing the Parameters field is elaborated in the Description
of parameters (See Description of the parameters common to the different DOP
functions, p. 340) section.

Field: Command This field is used to set the command associated with the PANEL_CMD function.

For:
l clearing a line; the line number must be specified,
l canceling an alarm; you must designate the alarm number which corresponds to
identifier given while using SEND_ALRM or DISPLAY_ALRM.

TLX DS 57 PL7 xx 383

Built-in DOP functions

Application The example below shows the implementation of the PANEL_CMD function for the
example purpose of canceling a T CCX 1720 W console alarm.
This is connected to a TSX Premium via the AUX port (configured in UNI-TELWAY
link, addresses 4 - 5).

Application description Variables used

Initial conditions %MW0:6: console address
l writing the console address (ADR#0.04) in a word table, %KW350:x: Wipe data to be sent,
l adjustment of timeout to 50 s, %KW360:x: Cancel data to be sent,
l condition of execution, %MW100:4: report
Application: The aim of this example is: %MW100:X0: activity bit
l wiping the console screen on user demand, %MW102: timeout
l canceling the alarm on fault acknowledgement, %M102: activation condition
l storing the function execution. %M100: fault acknowledgement

Program corresponding to the application

(*INIT console address, condition, timeout *)

IF %S1.3 THEN
%MW0:6:=ADR#0.0.4;
%MW102:=500;
%M120:2:=0;
END_IF;
(* Clear alarm … *)
IF %M100 AND NOT %M120 AND NOT %MW100:X0 THEN
PANEL_CMD(%MW0:6,%KW360:3,%MW100:4);
SET %M120
END_IF;
* Clear screen *)
IF %M102 AND NOT %M121 AND NOT %MW100:X0 THEN
PANEL_CMD(%MW0:6,%KW350:3,%MW100:4);
SET %M121;
END_IF;

384 TLX DS 57 PL7 xx

 Built-in DOP functions

Entry help screens corresponding to the application:

PANEL-CMD
Parameters
Console address: %MW0 6 Report: %MW100 4
Data to be sent: %KW40 2
Commands
Clear
Screen Line Line number 1
Entry log
Print Clear
Alarm log PANEL-CMD
Print Clear Parameters
Console address: ADR#0.0.4 Report: %MW50 4
Alarm management Data to be sent: %KW350 2
Cancel an Alarm Alarm number 1
Commands
Clear
OK Cancel Screen Line Line number 1
Entry log
Print Clear
Alarm log
Print Clear
Alarm management
Cancel an Alarm Alarm number 1

OK Cancel

TLX DS 57 PL7 xx 385

Built-in DOP functions

ADJUST function

Role This function is used to adjust (read and write) language objects (one object at a
time) from a CCX 17 or a MAGELIS, by controlling internal words in the PLC
memory.
The language objects which can be adjusted are:
l internal bits (%Mi),
l internal words or double words (%MWi, %MDi),
l rack or remote inputs/outputs (%I, %Q, %IW, %QW, %ID, %QD).

Note: It is strongly advised:

l to only execute one instance of the ADJUST function per cycle,
l to only execute the ADJUST function every n cycles.
l to assign parameters to the ADJUST function with consecutive words, so as to
optimize the reading of internal words on CCX 17 and MAGELIS.

Activating the This parameter is used to execute the ADJUST function.

function (EN) The types of objects assigned to this parameter may be:
l an internal bit (%Mi),
l an internal word extract bit (%MWi:Xj).

Read / Write This parameter defines the type of operation to be carried out:
(R_W) l read: bit = 0,
l write: bit = 1.
The types of objects assigned to this parameter may be:
l an internal bit (%Mi),
l an internal word extract bit (%MWi:Xj).

386 TLX DS 57 PL7 xx

 Built-in DOP functions

Type of object This parameter defines the type of object to be read or written.
(TYPE) The types of objects assigned to this parameter may be:
l an internal word (%MWi),
l an immediate value.
The table below shows the different types of objects which can be controlled using
the ADJUST function.
Type of Value of internal word or Type of Value of internal word or
object immediate value object immediate value
%Mi 0 %IW 5
%MWi 1 %QW 6
%MDi 2 %ID 7
%I 3 %QD 8
%Q 4

Object address This parameter contains the address of the object to be read or written.
(ADR) The object type assigned to this parameter is a table of eight internal words (%MWi).
The table below shows the content of the different words in the table.
Word This word contains… Possible values of the word
order
number
Word 0 the rack number where the language 0: bit objects, internal words or double words, I/O objects
object concerned is situated whose operations function is registered in rack 0.
n: other rack I/O objects.
Word 1 the number corresponding to the position 0: bit objects, internal words and double words, I/O objects
in the rack of the I/O module or of the whose operations function is associated to channels 1 and
processor in which the language object 2 of the processor registered at position 0 in the rack.
concerned is situated 1: I/O objects whose operations function is associated to
channels 1 and 2 of the processor registered at position 1
the rack.
n: other rack I/O objects.
Word 2 the channel number in the module where 0: bit objects, internal words and double words.
the language object concerned is situated 1: I/O objects whose operations function is associated to
channel 1 of the processor (communication functions with
PCMCIA).
2: I/O objects whose operations function is associated to
channel 2 of the processor (FIPIO link).
n: other rack I/O objects.
Word 3 the rank of the I/O object or the number of 0 or n: bit objects, internal words or double words, I/O
the internal language object concerned. objects with significant rank.
0: Other I/O objects.

TLX DS 57 PL7 xx 387

Built-in DOP functions

Word This word contains… Possible values of the word

order
number
Word 4 the connection point number of the device n: NANET or FIPIO objects.
on the FIPIO bus or the rank of the NANET 0: not significant.
object.
Word 5 the position of the FIPIO module. 0: basic or not significant module.
1: extension module
Word 6 the channel number in the FIPIO module or n: AS-i or FIPIO objects.
the slave bit on the AS-i bus. 0: not significant.
Word 7 the slave number of the AS-i and NANET n: AS-i or NANET objects.
buses. 0: not significant.

Value to write This parameter contains the value to write in the object.
(VAL) The object type assigned to this parameter is a double word (%MDi).

Set at 1, or Depending on the type of object to be written, this parameter is used:

Incrementation l to set the bit value (%Mi, %Q),
(SINC) l to increment by 1 the value of the word or double word (%MWi, %MDi, %QW,
%QD).

Note: the R_W parameter must be set to 1.

The object type assigned to this parameter is an internal bit (%Mi).

Set to 0 or Depending on the type of object to be written, this parameter is used:

Decrementation l to clear the bit value (%Mi, %Q),
(RDEC) l to decrement by 1 the value of the word or double word (%MWi, %MDi, %QW,
%QD).

Note: the R_W parameter must be set to 1.

The object type assigned to this parameter is an internal bit (%Mi).

Value of the This parameter contains the parameter value which has just been read.
object read The object type assigned to this parameter is a double word (%MDi).
(VRET)

388 TLX DS 57 PL7 xx

 Built-in DOP functions

Management The object type assigned to this parameter is a table of 24 internal words (%MWi).
parameters
(GEST)

Examples The illustration below shows an example of ADJUST function entry.

Display the call
ADJUST( %MW20:X0.%MW20:X1.%MW21.%MW22:8.%MD30.%MW20:X2.%MW20:X3.%MD32.%MW34:24 )

To read the internal double word %MD12, the following values would need to be
entered:
Parameter Language Value Comment
object to be
entered
:
EN %MW20:X0 1 Executing the ADJUST function
R_W %MW20:X1 0 Read operation
TYPE %MW21 2 Type of object: %MD
ADR %MW22 0 Not significant
%MW23 0 Not significant
%MW24 0 Not significant
%MW25 12 Object number (%MD12)
%MW26 0 Not significant
%MW27 0 Not significant
%MW28 0 Not significant
%MW29 0 Not significant
VAL %MD30 0 Not significant
SINC %MW20:X2 0 Not significant
RDEC %MW20:X3 0 Not significant
VRET %MD32 Value of the object read
MAN %MD34:24 Buffer parameter for receiving and sending
requests

TLX DS 57 PL7 xx 389

Built-in DOP functions

To write value 15 in the rack output word %QW3.2, the following values need to be
entered:
Parameter Language Value Comment
object to be
entered
:
EN %MW20:X0 1 Executing the ADJUST function
R_W %MW20:X1 1 Write operation
TYPE %MW21 6 Type of object: %QW
ADR %MW22 0 Rack number
%MW23 3 Module position
%MW24 2 Channel number
%MW25 0 Not significant
%MW26 0 Not significant
%MW27 0 Not significant
%MW28 0 Not significant
%MW29 0 Not significant
VAL %MD30 15 Value to write
SINC %MW20:X2 0 Not significant
RDEC %MW20:X3 0 Not significant
VRET %MD32 Value of the object read
MAN %MD34:24 Buffer parameter for receiving and sending
requests

To increment the output word on FIPIO %QW\1.2.12\0.1, the following values would
need to be entered:
Parameter Language Value Comment
object to be
entered
:
EN %MW20:X0 1 Executing the ADJUST function
R_W %MW20:X1 1 Write operation
TYPE %MW21 6 Type of object: %QW

390 TLX DS 57 PL7 xx

 Built-in DOP functions

Parameter Language Value Comment

object to be
entered
:
ADR %MW22 0 Not significant
%MW23 1 Processor address
%MW24 2 Channel number of built-in FIPIO link
%MW25 0 Not significant
%MW26 12 Connection point number
%MW27 0 Module number: Standard
%MW28 1 Channel number
%MW29 0 Not significant
VAL %MD30 0 Not significant
SINC %MW20:X2 0 Incrementing the word value by 1
RDEC %MW20:X3 0 Not significant
VRET %MD32 Not significant
MAN %MD34:24 Buffer parameter for receiving and sending
requests

To set to 0 the output bit on the AS-i %Q\105.0\7.2 bus, the following values need
to be entered:
Parameter Language Value Comment
object to be
entered
:
EN %MW20:X0 1 Executing the ADJUST function
R_W %MW20:X1 1 Write operation
TYPE %MW21 4 Type of object: %Q
ADR %MW22 1 Rack number
%MW23 5 Module position
%MW24 0 Channel number
%MW25 0 Not significant
%MW26 0 Not significant
%MW27 0 Not significant
%MW28 2 Bit rank (slave input/output)
%MW29 7 Slave number
VAL %MD30 0 Not significant

TLX DS 57 PL7 xx 391

Built-in DOP functions

Parameter Language Value Comment

object to be
entered
:
SINC %MW20:X2 0 Not significant
RDEC %MW20:X3 1 Output RESET
VRET %MD32 Not significant
MAN %MD34:24 Buffer parameter for receiving and sending
requests

To decrement the output word on NANET %QW\4.0\2.1, the following values would
need to be entered:
Parameter Language Value Comment
object to be
entered
:
EN %MW20:X0 1 Executing the ADJUST function
R_W %MW20:X1 1 Write operation
TYPE %MW21 6 Type of object: %QW
ADR %MW22 0 Rack number
%MW23 4 Module position
%MW24 0 Channel number
%MW25 1 NANET object rank (word number)
%MW26 0 Not significant
%MW27 0 Not significant
%MW28 0 Not significant
%MW29 2 Slave number
VAL %MD30 0 Not significant
SINC %MW20:X2 0 Not significant
RDEC %MW20:X3 1 Decrementing the word value by 1
VRET %MD32 Not significant
MAN %MD34:24 Buffer parameter for receiving and sending
requests

392 TLX DS 57 PL7 xx

 Appendices

26
Introduction

Subject of this This chapter introduces the supplementary information for installing DOP functions.
chapter

What's in this This Chapter contains the following Sections:

Chapter?
Section Topic Page
26.1 Precautions for DOP use 394
26.2 Description of the built-in DOP functions "Data to send" 395
parameter coding

TLX DS 57 PL7 xx 393

Appendices

26.1 Precautions for DOP use

Precautions for DOP use

Introduction The list below is not exhaustive, however, it does group together the errors most
frequently encountered whilst installing DOP functions in an application.

List of l Do not forget to initialize the Time-out parameter (%MWi+2) before starting the
precautions Operator Dialogue function. For the ASK_MSG or ASK_VALUE functions, the
value has to be 0.
l If you use the same word to save each function’s report, you must then test the
activity bit (%MWi:X0) at value 0 before starting another function.
l Synchronize the start of the different Built-in DOP functions in order that the CCX
17 console command queue does not become full.
l Remember to correctly calculate the size of the %KWi internal constants for
displaying the data to be sent.
l Do not hesitate to allow a margin for error when allocating the data to be sent
(%KWi:n). In fact, if you need to modify the text name, there will be no overlap
between the different %KWi:n references.
l The maximum size for the Built-in DOP functions is 47 words.
l Warning, it is impossible to create a Built-in DOP function in line modification
mode, if the application located in the PLC does not already contain a copy of this
function.
l During power outage or communication loss, the application has to reset the CCX
17 in a coherent state (assigning buttons and messages to the screen).
l Canceling modifications or deleting a rung or phrase (List or Text) does not
cancel initialization of the %KWi variables.

394 TLX DS 57 PL7 xx

 Appendices

26.2 Description of the built-in DOP functions "Data to

send" parameter coding

Introduction

Subject of this This section describes the Data to send parameter.

section It is intended for application developers who want to install built-in DOP functions
without using the input help screens.

What's in this This Section contains the following Maps:

Section?
Topic Page
PLC status message display: SEND_MSG function 396
PLC checked status message entry: ASK_MSG and GET_MSG function 399
PLC alarm message display: SEND_ALARM function 403
Display of status, alarm or a group of messages contained in the CCX 17 406
memory: ASK_VALUE, DISPLAY_MSG, GET_VALUE, DISPLAY_ALRM and
DISPLAY_GRP functions
Display of luminous column LEDS: CONTROL_LEDS function 407
Configuring command keys: ASSIGN_KEYS function 408
Generic send command: PANEL_CMD function 410

TLX DS 57 PL7 xx 395

Appendices

PLC status message display: SEND_MSG function

Introduction Status messages can be constructed from the PLC application by creating the send
using internal words (%Mwi) as intermediaries to display them on a CCX17 console
screen. This is the role of the SEND_MSG function.

Data to send The table below shows the significance of the different words which constitute the
parameter following parameter: Data to send (47 words maximum).
coding
Word Meaning
number
1 contains a marker of value 16#CC17,
2 contains value 0
3 contains the length in bytes and the zone of the following words,
4 to P contain the message text to send, this being the characters that are underlined representing the
characters expected during the display of a variable. The maximum length of this text is 40 characters.
If the text is composed of an odd number of characters, the last byte is worth 0, if the text is of even
length and if it is less than 39 characters, the last byte must contain the value 0,
P +1 contains the line number where the message must be displayed,
P +2 contains the column number where the start of the message must be displayed,
P +3 This two word zone (four characters) contains the message characteristics and is structured as follows:
P +4 Character 1 This character (in capitals) corresponds to a video attribute:
l B = blinking,
l R = reverse video,
l A = blinking and reverse video,
l N = no attribute

Character 2 This character (in capitals) corresponds to the character font size:
l S = normal size,
l D = double width or height

Characters 3 and corresponds to the printing option:

4 l Y followed by a space = yes,
l N followed by a space = no.

P+5 If you do not want to display a variable, the following word must be at 0 (in this instance,
following parameters is ignored), otherwise the following parameters must be added:
P+6 contains the position of the variable to display, counted in number of characters in relation to the start
of the message.
P+7 contains the number of characters to display for the variable.
P Number of words containing the text of the message to send (see line 4 to P).

396 TLX DS 57 PL7 xx

 Appendices

Word Meaning
number
P+8 contains a supplementary command:
l 0: no command,
l 1: clear screen,
l 2: clear the line before the display.

P+9 contains the value 16#0030.

P+10 and 11 contain the type of entry field:
l BIT +space = bit type,
l ANA + space = word type,
l LNG + space = double word type,
l DAY + space = date type,
l HOU + space = hour type.

P+12 contains value 0.

P+13 contains the type of variable to display:
l B +space = bit type,
l W + space = word type,
l DW = double word type,
Note: for a Date or Hour type, this word contains value 0.
P+14 contains:
l the address index of the variable to display for a bit, word or double word type,
l value –1 for a date or hour type.

P+15 and 16 contain the display format for the variable and are structured in the following ways:
Byte 1 specifies if the variable is signed (sign +), or not (space),
Bytes 2 and 3 specifies the display format:
Byte 2 Byte 2
ASCII or DIGITAL without the ASCII code for the space, that being 20
decimal places
DIGITAL with less than the ASCII code for the the ASCII code for the
ten decimal places space, that being 20 number of decimal
places
DIGITAL with at least ten the ASCII code for the the ASCII code for the
decimal places number of tens of decimal number of decimal place
places units
Byte 4 specifies the display type:
l N = no format,
l D = Digital,
l A = ASCII

P Number of words containing the text of the message to send (see line 4 to P).

TLX DS 57 PL7 xx 397

Appendices

Word Meaning
number
P+17 define if the variable must be refreshed or not:
l Y + space = yes,
l N + space = no.

P+18 contains the value N + space,

P+19 to 25 contain the value 0 (7 words).
P Number of words containing the text of the message to send (see line 4 to P).

Example of use The example below shows the values corresponding to the word table %MW0:12
(data to send) of the SEND_MSG(ADR#0.0.4,%MW0:12,%MW100:4) function;
Word Value Comment
number
%MW0 16#CC17 Marker
%MW1 0 Imposed value
%MW2 18 Byte size of the following zone which includes nine words
%MW3 Fo Message text
%MW4 ur Message text (continued)
%MW5 sp4 Message text (end)
%MW6 0 End of message mark
%MW7 2 Message position (line number)
%MW8 15 Message position (column number)
%MW9 ND Message characteristics (no attribute or double font)
%MW10 Nsp Message characteristic (no printing)
%MW11 0 The message includes no variable

398 TLX DS 57 PL7 xx

 Appendices

PLC checked status message entry: ASK_MSG and GET_MSG function

Introduction Checked status messages can be constructed from the PLC application by creating
the send using internal words (%MWi) as intermediaries to display them on a CCX17
console screen. This is the role of the ASK_MSG and GET_MSG functions.

Data to send The table below shows the significance of the different words which constitute the
parameter following parameter: Data to send (47 words maximum).
coding
Word Meaning
number
1 contains a marker of value 16#CC17,
2 contains the command type:
l 33 = command number for ASK_MSG,
l 6 = command number for GET_MSG,

3 contains the length in bytes and the zone of the following words,
4 to P contain the message text to send, this being the characters that are underlined representing the
characters expected during the display of a variable. The maximum length of this text is 40 characters.
If the text is composed of an odd number of characters, the last byte is worth 0, if the text is of even
length and if it is less than 39 characters, the last byte must contain the value 0,
P +1 contains the line number where the message must be displayed,
P +2 contains the column number where the start of the message must be displayed,
P +3 This two word zone (four characters) contains the message characteristics and is structured as follows:
P +4 Character 1 This character (in capitals) corresponds to a video attribute:
l B = blinking,
l R = reverse video,
l A = blinking and reverse video,
l N = no attribute

Character 2 This character (in capitals) corresponds to the character font size:
l S = normal size,
l D = double width or height

Characters 3 and corresponds to the printing option:

4 l Y followed by a space = yes,
l N followed by a space = no.

P+5 contains the position of the variable to display, counted in number of characters in relation to the start
of the message.
P+6 contains the number of characters to display for the variable.
P Number of words containing the text of the message to send (see line 4 to P).

TLX DS 57 PL7 xx 399

Appendices

Word Meaning
number
P+7 contains a supplementary command:
l 0: no command (ASK_MSG synchronized entry),
l 24: free entry authorized after display (GET_MSG multiple entry).

P+8 contains the value 16#0030.

P+9 contain the type of entry field (in Upper case):
P+10 l BIT +space = bit type,
l ANA + space = word type,
l LNG + space = double word type.

P+11 contains value 0.

P+12 contains the type of variable to display (in Upper case):
l B +space = bit type,
l W + space = word type,
l DW = double word type,

P+13 contains the address index of the variable to display.

P+14 contain the display format for the variable and are structured in the following ways:
P+15 Byte 1 specifies if the variable is signed (sign +), or not (space),
Bytes 2 and 3 specifies the display format:
Byte 2 Byte 3
ASCII or DIGITAL without the ASCII code for the space, that being 20
decimal places
DIGITAL with less than the ASCII code for the the ASCII code for the
ten decimal places space, that being 20 number of decimal places
DIGITAL with at least ten the ASCII code for the the ASCII code for the
decimal places number of tens of decimal number of decimal place
places units
Byte 4 specifies the display type:
l N = no format,
l D = Digital,
l A = ASCII

P+16 defines whether or not the variable must be updated:

l Y + space = yes,
l N + space = no.

P+17 defines the field attributes:

l I + space = increment,
l L + space = others.

P Number of words containing the text of the message to send (see line 4 to P).

400 TLX DS 57 PL7 xx

 Appendices

Word Meaning
number
P+18 and 19 define the limit type:
l 0 = unlimited,
l 1 = minimum limit only,
l 2 = maximum limit only,
l 3 = minimum and maximum limit.

P+20 and 21 contain the minimum limit value.

P+22 and 23 contain the maximum limit value.
P+24 and 25 contain the increment value.
P Number of words containing the text of the message to send (see line 4 to P).

Example of use The example below shows the values corresponding to the word table %MW0:38
(data to send) of the GET_MSG(ADR#0.0.4,%MW0:38,%MW100:4) function;
Word Value Comment
number
%MW0 16#CC17 Marker
%MW1 6 Command number for GET_MSG
%MW2 70 Byte size of the following zone which includes 35 word
%MW3 Te Message text
%MW4 mp Message text (continued)
%MW5 er Message text (continued)
%MW6 at Message text (continued)
%MW7 ur Message text (continued)
%MW8 eesp Message text (continued)
%MW9 =sp Message text (continued)
%MW10 __ Message text (continued)
%MW11 _sp Message text (continued)
%MW12 °C Message text (end)
%MW13 0 End of message mark
%MW14 3 Text position (line number)
%MW15 11 Text position (column number)
%MW16 NS Message characteristics (no attribute or double font)
%MW17 Nsp Message characteristic (no printing)
%MW18 15 Position of the variable from the start of the message
%MW19 3 Number of characters to display

TLX DS 57 PL7 xx 401

Appendices

Word Value Comment

number
%MW20 24 Additional command (entered after display)
%MW21 16#0030 Reserved value
%MW22 AN Type of entry field (AN = start of ANA)
%MW23 Asp Type of entry field (continued)
%MW24 0 Reserved value
%MW25 Wsp Type of variable to display (W = word type variable)
%MW26 10 Address index for the variable to display (%MW10)
%MW27 espesp Display format (sp for a non signed variable, sp for the start of the
decoding of decimal places after the point)
%MW28 spD Display format continued (sp for the end of the coding of the
number of digits after the point, D for the decimal format)
%MW29 Yesp The variable must be updated
%MW30 Iesp Entry is incremental
%MW31 0 The variable is not limited
%MD32 0 Minimum limit value
%MD34 0 Maximum limit value
%MD36 50 Increment value

402 TLX DS 57 PL7 xx

 Appendices

PLC alarm message display: SEND_ALARM function

Introduction Alarm messages can be constructed from the PLC application by creating the send
using internal words (%MWi) as intermediaries to display them on a CCX17 console
screen. This is the role of the SEND_ALARM function.

Data to send The table below shows the significance of the different words which constitute the
parameter following parameter: Data to send (37 words maximum).
coding
Word Meaning
number
1 contains a marker of value 16#CC17,
2 contains value 0
3 contains the length in bytes and the zone of the following words,
4 contains the imaginary number given to the alarm message (this word is used after deactivating the
alarm if necessary). The value of this word must be between 900 and 999.
5 to P contain the message text to send, this being the characters that are underlined representing the
characters expected during the display of a variable. The maximum length of this text is 40 characters.
If the text is composed of an odd number of characters, the last byte is worth 0, if the text is of even
length and if it is less than 39 characters, the last byte must contain the value 0,
P +1 and 2 This two word zone (four characters) contains the message characteristics and is structured as follows:
Character 1 This character (in capitals) corresponds to the character font size:
l S = normal size,
l D = double width or height.

Character 2 corresponds to the printing option:

l Y = yes,
l N = no.

Characters 3 and correspond to the overprinting option:

4 l Y followed by a space = yes,
l N followed by a space = no.

P+3 If you do not want to display a variable, the following word must be at 0 (in this instance,
following parameters is ignored), otherwise the following parameters must be added:
P+4 contains the position of the variable to display, counted in number of characters in relation to the start
of the message.
P+5 contains the number of characters to display for the variable.
P+6 contains the value 16#0030.
P Number of words containing the text of the message to send (see line 5 to P).

TLX DS 57 PL7 xx 403

Appendices

Word Meaning
number
P+7 and 8 contain the type of entry field:
l BIT +space = bit type,
l ANA + space = word type,
l LNG + space = double word type,

P+9 contains value 0.

P+10 contains the type of variable to display:
l B +space = bit type,
l W + space = word type,
l DW = double word type,

P+11 contains the address index of the variable to display.

P+12and 13 contain the display format for the variable and are structured in the following ways:
Byte 1 specifies if the variable is signed (sign +), or not (space),
Bytes 2 and 3 specifies the display format:
Byte 2 Byte 3
ASCII or DIGITAL without the ASCII code for the space, that being 20
decimal places
DIGITAL with less than the ASCII code for the the ASCII code for the
ten decimal places space, that being 20 number of decimal
places
DIGITAL with at least ten the ASCII code for the the ASCII code for the
decimal places number of tens of decimal number of decimal place
places units
Byte 4 specifies the display type:
l N = no format,
l D = Digital,
l A = ASCII

P Number of words containing the text of the message to send (see line 5 to P).

Example of use The example below shows the values corresponding to the word table %MW0:29
(data to send) of the SEND_ALARM(ADR#0.0.4,%MW0:29,%MW100:4) function;
Word Value Comment
number
%MW0 16#CC17 Marker
%MW1 0 Imposed value
%MW2 52 Byte size of the following zone which includes 26 word
%MW3 900 Alarm message number

404 TLX DS 57 PL7 xx

 Appendices

Word Value Comment

number
%MW4 Su Message text
%MW5 rc Message text (continued)
%MW6 ha Message text (continued)
%MW7 uf Message text (continued)
%MW8 fe Message text (continued)
%MW9 spf Message text (continued)
%MW10 or Message text (continued)
%MW11 rsp Message text (continued)
%MW12 =sp Message text (continued)
%MW13 __ Message text (continued)
%MW14 _sp Message text (continued)
%MW15 °C Message text (end)
%MW16 0 End of message mark
%MW17 SY Message characteristic (Normal size, printing)
%MW18 Ysp Message characteristic (overprinting)
%MW19 19 Position of the variable from the start of the message
%MW20 3 Number of characters to display
%MW21 16#0030 Reserved value
%MW22 AN Type of entry field (AN = start of ANA)
%MW23 Asp Type of entry field (continued)
%MW24 0 Reserved value
%MW25 Wsp Type of variable to display (W = word type variable)
%MW26 10 Address index for the variable to display (%MW10)
%MW27 espesp Display format (sp for a non signed variable, sp for the start of the
decoding of decimal places after the point)
%MW28 spD Display format continued (sp for the end of the coding of the
number of digits after the point, D for the decimal format)

TLX DS 57 PL7 xx 405

Appendices

Display of status, alarm or a group of messages contained in the CCX 17

memory: ASK_VALUE, DISPLAY_MSG, GET_VALUE, DISPLAY_ALRM and
DISPLAY_GRP functions

Introduction For these functions it is possible to send them by using internal words (%MWi) as
intermediaries.
The Data to send parameter requires one word which contains accordingly:
l The status message number,
l Alarm message number,
l Message group number

Example of use The example below shows an example of a function using the word %MW0 (data to
send).

DISPLAY_GRP(ADR#0.0.4,%MW0,%MW100:4) with %MW0:=3

406 TLX DS 57 PL7 xx

 Appendices

Display of luminous column LEDS: CONTROL_LEDS function

Introduction It is possible to set the relay status (version 2.1 and above) and the LEDs on the
luminous screen of a CCX17 console, then to send them using internal words
(%MWi) as intermediaries. This is the role of the CONTROL_LEDS function.

Data to send The table below shows the significance of the different words which constitute the
parameter following parameter: Data to send (2 words).
coding
Word Meaning
number
1 contains a marker of value 16#CC17,
2 indicates the coding of each LED as well as the relay state to send to the terminal.
l bits 0 to 3: green LED status,
l bits 4 to 7: yellow LED status,
l bits 8 to 11: red LED status,
l bits 12 to 15: relay status,
the state of each of the LEDS is coded on four bits as follows:
l 0000: unchanged LED status,
l 0001: LED off,
l 0010: LED on,
l 1111: LED flashing.
the relay status is coded on bits 12 to 15 as follows:
the state of each of the indicators is coded on four bits as follows:
l 0000: unchanged relay status,
l 0001: open relay status,
l 0010: closed relay status.

Example of use The example below shows the values corresponding to the word table %MW0:2
(data to send) of the CONTROL_1EDS(ADR#0.0.4,%MW0:2,%MW100:4) function;
Word Value Comment
number
%MW0 16#CC17 Marker
%MW1 16#1112 Green LEDS on, yellow and red off, open relay status

TLX DS 57 PL7 xx 407

Appendices

Configuring command keys: ASSIGN_KEYS function

Introduction It is possible to set the configuration of the command keys (bit associated or not, key
operating mode, assignment by CCX17…) and send it using internal words (%MWi)
as intermediaries to display them on a CCX17 console screen. This is the role of the
ASSIGN_KEYS function.

Data to send The table below shows the significance of the different words which constitute the
parameter following parameter: Data to send (12 words).
coding
Word Meaning
number
1 contains a marker of value 16#CC17,
If a PLC carries out the assignment… If a CCX 17 carries out the assignment…
2 this word contains the list of keys to configure. Each this word contains 16#F000
command key is coded on a bit (0: non configured, 1:
configured):
l bit i (i = 1 to 8) command key no. 1.

the following two words indicate the operating mode of the values of the following ten words are
each of the command keys. Each key is coded by two indifferent and will be ignored by the CCX 17
bits console.
l 00: Reset,
l 01: functioning mode on edge,
l 10: toggle functioning mode,
l 11: no action.
Bits 2j,2j+1 = command key i+1 (i = 0 to 11)
the following eight words contain, accordingly:
l a value –1 when the command keys are not affected,
l the index of the internal bits affected by the command
keys
Word i = command key i (i = 1 to 8)

408 TLX DS 57 PL7 xx

 Appendices

Example of use The example below shows the values corresponding to the word table %MW0:16
(data to send) of the ASSIGN_KEYS (ADR#0.0.4,%MW0:16,%MW100:4) function;
Word Value Comment
number
%MW0 16#CC17 Marker
%MW1 16#000F Command keys 1 to 4 are configured, the others are not.
%MW2 16#FF09 Key 1 in edge mode (01), key 2 in toggle mode (02), keys 3 and 4
%MW3 16#00FF inhibited (00), the others not programmed (11)

%MW4 10 Key 1 affected by bit %M10

%MW5 rc Key 1 affected by bit %M11
%MW6 to -1 Keys 3 to 8 not affected
%MW15

TLX DS 57 PL7 xx 409

Appendices

Generic send command: PANEL_CMD function

Introduction It is possible to manage different command types (clearing, printing) and to send
them by using internal words (%MWi) as intermediaries. This is the role of the
PANEL_CMD function.

Data to send The table below shows the significance of the different words which constitute the
parameter following parameter: Data to send (3 words maximum).
coding
Word Meaning
number
1 contains a marker of value 16#CC17,
2 contains the command number:
l 1: clear screen,
l 2: clear a line,
l 9: print the alarm message log,
l 10: clear the alarm message log,
l 11: print the alarm log
l 13: clear the alarm log,
l 29: clear the alarm (from 1 to 300) destined for CCX 17,
l 30: clear the alarm (from 900 to 999) destined for the PLC.

3 indicates the command parameter.

l clear line = line number,
l cancel alarm = alarm number,
l other commands: no object.

Example of use The example below shows the values corresponding to the word table %MW0:2
(data to send) for the PANEL_CMD(ADR#0.0.4,%MW0:2,%MW100:4) function;
Word Value Comment
number
%MW0 16#CC17 Marker
%MW1 1 Clear screen

410 TLX DS 57 PL7 xx

 Glossary

AS-i V2 Actuator Sensor interface version 2, accepting extended address slaves.

AS-interface Actuator Sensor interface.

CCX17 Family of Schneider Automation Human-Machine Interface terminal.

Channel group Channels of the same type with common parameters. This notion concerns certain
application-specific modules such as discrete modules.

CPU Central Processing Unit: generic name used for Schneider Automation processors

Discrete Discrete I/Os

TLX DS 57 PL7 xx 411

Glossary

FIPIO Field bus used to connect sensor or actuator type devices.

IP67 Family of Schneider Automation hardware products consisting of sealed I/O

modules which connect to the FIPIO field bus, used to produce automated systems
with distributed I/Os.

Momentum I/O modules using several open standard communication networks.

PL7 Junior and Schneider Automation PLC programming software.

Pro

PV Identifier indicating the product version.

TBX I/O modules remoted on the FIPIO bus.

TSX/PMX/PCX57 Families of Schneider Automation hardware products.

412 TLX DS 57 PL7 xx

 Index
B
AC
Symbols Adjustment, 24
AS-i Bus, 228
%CHxy.i, 40 Discrete reflex, 192
Adjustment objects
AS-i bus, 245
A AS-i V2 bus, 316
Access to the configuration editor Advanced operation
AS-i Bus, 208 AS-i bus, 252, 253
AS-i bus, 270 AS-i V2 bus, 323, 324
Accessing the configuration editor, 60 Analog Parameters
In-rack discrete, 80 AS-i V2 Bus, 284
Remote I/Os, 82 Analog Value Modification
Accessing the debug editor AS-i V2 Bus, 299
in-rack discrete, 115 Application-specific function
Adding a profile Discrete, 73
AS-I Bus, 217 Application-specific instructions, 56
Adding a slave AS-i, 199
AS-i Bus, 212 AS-i Bus, 202
AS-i V2 Bus, 274 AS-i slave
Adding an AS-i bus, 206, 266, 267
AS-i V2 Bus profile, 280 AS-i V2, 259
Addressing AS-i V2 bus, 262
AS-i bus, 35, 236 ASSIGN_KEYS, 380
AS-i V2 bus, 304 Automatic slave addressing
built-in interfaces, 29 AS-i bus, 219
Discrete in-rack, 125 AS-i V2 bus, 282
FIPIO Bus, 33
Modules in rack, 31
Momentum, 33 B
Remote I/Os, 126
Built-in application-specific interfaces, 29
TBX, 33

TLX DS 57 PL7 xx 413

Index

C Debugging Screen
AS-i V2 Bus, 289
Channel diagnostics
Debugging screen
Discrete, 117
AS-i Bus, 223
Channel fault
Declaration of a module on the FIPIO bus, 64
Discrete, 117
Declaration of an I/O module, 63
Combination of parameters
Device Connection
AS-i V2 Bus, 285
AS-i V2 Bus, 274
Command objects
Device connection
AS-i bus, 244
AS-I Bus, 212
AS-i V2 bus, 315
Diagnostics, 25
Communication Interface, 29
AS-i V2 Bus, 291
Configuration, 22
Bus AS-i, 225
Configuration of reflex function blocks, 191
Diagnostics mode
Configuration screen
AS-i Bus, 227
AS-i Bus, 210
AS-i V2 Bus, 291
AS-i V2 Bus, 272
Bus AS-i, 225
Discrete, 79
Discrete, 71
Configuring slaves
Discrete reflex modules, 140
AS-i Bus, 210
DISPLAY_GRP, 370
AS-i V2 Bus, 272
DISPLAY_MSG, 369
Configuring the reflex function blocks, 188
Confirming the configuration, 66, 67
Connect E
AS-i V2 bus, 288
Event
Connecting
Discrete reflex, 193
AS-i bus, 222
Exchange management, 130, 308
Constants
Explicit exchanges, 40
AS-i Bus, 314
AS-i bus, 242
CONTROL_LEDS, 377
AS-i V2 bus, 311
Copy/paste, 83
Explicit objects, 132, 134, 135, 136, 137,
240, 309
D AS-i Bus, 241
AS-i bus, 246, 310
Data exchange off mode
AS-i V2 bus, 317
AS-i bus, 253
Discrete reflex, 197
AS-i V2 bus, 324
External errors
Debug, 25
AS-i Bus, 225, 291
AS-i bus, 222
External supply fault, 102
AS-i V2 bus, 288
Debug mode, 111
Debug screen F
Discrete, 113
Fallback mode, 108
Debugging
Fallback to 0
Discrete, 112, 115
AS-i bus, 220

414 TLX DS 57 PL7 xx

 Index

Family Latching, 106

AS-i Bus, 207, 269 Library, 56
Fault processing by program, 68
Faulty slave
AS-i bus, 231 M
AS-i V2 bus, 300 Maintain
Filtering, 105 AS-i bus, 220
FIPIO, 64, 82 Maintain outputs
FIPIO connection, 64 Discrete, 122
Forcing, 118 Management of exchanges, 239
AS-i Bus, 229 Masking, 120
AS-i V2 Bus, 297 Master/Slave
Function AS-i bus, 204, 264
Adjustment, 24 Modifying parameters, 83
Configuration, 22 Module diagnostics
Debug, 25 Discrete, 116
Functions, 103 Module fault
Discrete, 116
Module number
G AS-i Bus, 207, 269
GET_MSG, 361 Module selection
GET_VALUE, 375 AS-i bus, 269
Momentum, 64, 88
Multiple selection, 83
I
Implicit exchanges, 37
AS-i bus, 238 O
AS-i V2 bus, 306 Offline mode
Discrete, 129 AS-i bus, 252
Implicit objects AS-i V2 bus, 323
Discrete reflex, 195 Operating mode
Indexable objects AS-i bus, 248
Discrete, 127 AS-i V2 bus, 320
Internal errors
AS-i Bus, 225, 291
IP67, 89, 97 P
Parameter
Discrete, 106
L Parameter Modification
Language objects, 130, 132, 134, 135, 136, AS-i V2 Bus, 283
137, 239, 240, 308, 309 Parameters
AS-i Bus, 241 Discrete, 99, 100, 101, 102, 103, 105,
AS-i V2 bus, 317
Bus AS-i, 246, 310
Discrete, 129
Discrete reflex, 195, 197

TLX DS 57 PL7 xx 415

Index

107, 108, 109 Reflex functions

In-rack discrete inputs, 86 2 threshold counter, 166
In-rack discrete outputs, 91, 92 2 value monostable, 159
IP67 discrete inputs, 89 2 value operation timer, 150
IP67 discrete outputs, 97 Burst, 172
Momentum discrete inputs, 88 Combinational, 144
Momentum discrete outputs, 96 Command-counting, 183
TBX discrete inputs, 87 D flip-flops, 162
TBX discrete outputs, 94, 95 Detection of underspeed, 174
Performance Direct, 143
AS-i bus, 255 Fault signaling, 185
Performances Idle timer, 147
AS-i V2 bus, 325 Intervalometer, 170
PL7 status bar, 62 Monostable with time delay, 157
PL7 Toolbar, 61 Operation timer, 146
Presymbolization, 53, 54 Operation-idle timer, 148
Processing of faults by program, 69 Operation-idle timer with value selection,
Profile 153
AS-i bus, 204, 264 Oscillator, 161
Programmable channels, 99 PWM, 173
Protected mode Retriggerable monostable, 156
AS-i bus, 250 Simple electronic cam, 168
AS-i V2 bus, 322 Speed monitoring, 176
T flip-flop, 164
Type 1 command-check, 179
R Type 2 command-check, 181
Reactivation Réglage
Discrete, 121 AS-i V2 Bus, 295
Reactivation of outputs, 109 RESET, 119
READ_PARAM, 45 AS-i Bus, 230
READ_STS, 42 AS-i V2 Bus, 298
Reading adjustment parameters, 45 RESTORE_PARAM, 49
Reading status words, 42 Restoring adjustment parameters, 49
Reflex function configuration editor, 189 RUN/STOP, 107
RUN/STOP input, 107

S
SAVE_PARAM, 47
Saving adjustment parameters, 47
Security Device
AS-i V2 Bus, 286
Selecting the module
AS-i Bus, 207

416 TLX DS 57 PL7 xx

 Index

Selection of modules TSX SAY 1000 module

Discrete, 63 AS-i bus, 264
Remote I/Os, 64
SEND_ALARM, 366
SEND_MSG, 358 U
SET, 119 Unforcing, 118
AS-i Bus, 230 As-i Bus, 229
AS-i V2 Bus, 298 AS-i V2 Bus, 297
Slave Address Modification Unmasking, 120
AS-i V2 Bus, 302
Slave Insertion
AS-i V2 Bus, 301 W
Slave number Wiring check, 101
AS-i bus, 213 Wiring test mode
AS-i V2 bus, 276 AS-i bus, 251
Slaves Write command, 119
AS-i Bus, 227 Write to 0, 119
AS-i V2 Bus, 293 Write to 1, 119
Slaves' status WRITE_CMD, 44
AS-i V2 Bus, 293 WRITE_PARAM, 46
Slaves’ status Writing adjustment parameters, 46
AS-i Bus, 227 Writing command words, 44
Software installation
General, 20
Status objects
AS-i bus, 238, 242
AS-i V2 bus, 306, 311
Structure of a standard address AS-i
AS-i bus, 266
Structure of an AS-i slave
AS-i bus, 206
Structure of an extended address AS-i slave
AS-i bus, 267

T
Task
Discrete, 100
TBX, 64, 87, 94, 95, 99
Terminal Port, 29
TSX SAY 100
AS-i bus, 204
TSX SAY 100 module
AS-i bus, 204
TSX SAY 1000
AS-i bus, 264

TLX DS 57 PL7 xx 417

Index

418 TLX DS 57 PL7 xx