Schneider Electric Software PLC Application-Specific Functions, Junior/Pro, 4.5 User Guide
Annons
Annons
PL7 Junior/Pro
Modicon Premium PLC
Applications
Standard applications
July 2006 eng
2 35012326 00 July 2006
Document Set
At a Glance This manual is made up of 8 parts: z z z z z z z z
Volume 1 z z
Common application-specific functions
Discrete Application z z
AS-i implementation
AS-i V2 implementation z
Dialog Operator Application
Volume 2 z
Counting Application
Volume 3 z
Axes Control Application
Volume 4 z
Step by step Control Application
Volume 5 z
Electronic Cam Application
Volume 6 z
SERCOS Movement Command Application
Volume 7 z z
Analog Application
PID Control Application z
Weighing Application
Volume 8 z
Adjustment Application
Document Set
35012326 00 July 2006
3
Document Set
4 35012326 00 July 2006
Table of Contents
About the Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Part I Shared application-specific functions . . . . . . . . . . . . . . 17
Chapter 1 Common application specific functions: General . . . . . . . . . . 19
Chapter 2 Objects associated with specific applications . . . . . . . . . . . . 27
2.1
Addressing of language objects associated with specific applications . . . . . . . . 29
Addressing of built-in application-specific interfaces. . . . . . . . . . . . . . . . . . . . . . 30
Addressing input/output module objects in rack . . . . . . . . . . . . . . . . . . . . . . . . . 32
Addressing of language objects for modules remoted on the FIPIO bus . . . . . . 35
Addressing of language objects associated with AS-i bus . . . . . . . . . . . . . . . . . 38
2.2
2.3
WRITE_CMD: Writing command words . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
READ_PARAM: Reading adjustment parameters . . . . . . . . . . . . . . . . . . . . . . . 49
WRITE_PARAM: Writing adjustment parameters . . . . . . . . . . . . . . . . . . . . . . . . 50
SAVE_PARAM: Saving adjustment parameters . . . . . . . . . . . . . . . . . . . . . . . . . 51
RESTORE_PARAM: Restoring adjustment parameters . . . . . . . . . . . . . . . . . . . 53
2.4
35012326 00 July 2006
5
6
Automatic symbolization of objects associated with a channel . . . . . . . . . . . . . . 59
Chapter 3 Application-specific instructions . . . . . . . . . . . . . . . . . . . . . . . 61
Accessing a specific function, method or procedure type instruction . . . . . . . . . 63
Chapter 4 Appendices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Reminders concerning the configuration editor . . . . . . . . . . . . . . . . . . . . . . . . . . 66
How to declare a remote module on the FIPIO bus. . . . . . . . . . . . . . . . . . . . . . . 71
Application-specific fault processing (in-rack modules) by program . . . . . . . . . . 75
Part II Discrete specific application . . . . . . . . . . . . . . . . . . . . . . 79
Chapter 5 General presentation of the discrete application -specific
function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Chapter 6 Configuration of the discrete specific application . . . . . . . . . 85
6.1
Description of the configuration screen for a discrete module . . . . . . . . . . . . . . . 88
Accessing the configuration screen for an in -rack discrete module.. . . . . . . . . . 90
Accessing the configuration screen for a discrete module remoted on the FIPIO
Modifying the configuration parameters of a discrete module's: General . . . . . . 93
6.2
Parameters of TBX discrete inputs remoted on the FIPIO bus . . . . . . . . . . . . . . 97
Parameters of Momentum discrete inputs remoted on the FIPIO bus. . . . . . . . . 98
Parameters of IP67 discrete inputs remoted on the FIPIO bus . . . . . . . . . . . . . . 99
6.3
Discrete output parameters for in-rack 8-channel modules. . . . . . . . . . . . . . . . 101
Discrete output parameters for in-rack modules with over 8 channels . . . . . . . 102
35012326 00 July 2006
Parameters of 8, 10 or 12 channel TBX discrete outputs remoted on the FIPIO
Parameters of 16 channel TBX discrete outputs remoted on the FIPIO bus . . 105
Momentum Parameters of Momentum discrete outputs remoted on the FIPIO
Parameters of IP67 discrete outputs remoted on the FIPIO bus. . . . . . . . . . . . 107
6.4
Configuring the programmable channels of the TBX DMS 16P22 module . . . . 109
Modifying the Task parameter of a discrete module . . . . . . . . . . . . . . . . . . . . . 110
Modifying the Wiring check parameter of a TBX discrete module. . . . . . . . . . . 111
Modifying the Monitoring of external supply fault parameter for a discrete
Modifying the Functions parameter of a discrete input module. . . . . . . . . . . . . 113
Modifying the Filtering parameter of a discrete input module.. . . . . . . . . . . . . . 115
How to modify the Latching parameter of a discrete input module . . . . . . . . . . 116
Parametering the Run/Stop input of a discrete module. . . . . . . . . . . . . . . . . . . 117
Modifying the Fallback mode parameter of a discrete output module. . . . . . . . 118
Modifying the Reactivation of outputs parameter of a discrete module. . . . . . . 119
Chapter 7 Debugging discrete modules . . . . . . . . . . . . . . . . . . . . . . . . . 121
Presentation of the debug function of a discrete module. . . . . . . . . . . . . . . . . . 122
Description of the debug screen of a discrete module . . . . . . . . . . . . . . . . . . . 123
Accessing the debug screen for an in-rack discrete module. . . . . . . . . . . . . . . 125
Accessing the diagnostics function of a discrete module . . . . . . . . . . . . . . . . . 126
Accessing the channel diagnostics function of a discrete module . . . . . . . . . . 127
How to access the SET and RESET commands . . . . . . . . . . . . . . . . . . . . . . . 129
Accessing the masking/unmasking function for an event . . . . . . . . . . . . . . . . . 130
Accessing the reactivation of outputs command . . . . . . . . . . . . . . . . . . . . . . . . 131
Chapter 8 Bits and words associated with discrete specific
applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
8.1
Addressing of language objects associated with discrete in-rack I/O modules. 136
Addressing of language objects associated with discrete I/O modules
8.2
Language objects associated with the discrete specific application . . . . . . . . . 139
Implicit exchange language objects associated with the discrete specific
35012326 00 July 2006
7
8
Exchange management: Exchanges in progress module %MW@module
.MOD.0:Xj or channel %[email protected]:Xj . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Exchange management: Module %[email protected]:Xj or channel
Explicit exchange object: %[email protected]:Xj channel status . . . . . . . . . . . . 146
Explicit exchange object: Status Module %[email protected]:Xj. . . . . . . . . 147
Explicit exchange object: %[email protected]:Xj channel command . . . . . . . . . 149
Chapter 9 Installation of the discrete reflex module . . . . . . . . . . . . . . . 151
9.1
General presentation of discrete reflex module . . . . . . . . . . . . . . . . . . . . . . . . . 153
9.2
Reflex function block: Operation-idle time with value selection . . . . . . . . . . . . . 166
Reflex function block: Retriggerable monostable. . . . . . . . . . . . . . . . . . . . . . . . 169
Reflex function block: Monostable with time delay . . . . . . . . . . . . . . . . . . . . . . 170
Reflex Function Block: 2 Threshold Counter . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
Reflex function block: Came électronique simple . . . . . . . . . . . . . . . . . . . . . . . 181
Reflex function block: 1 threshold intervalometer . . . . . . . . . . . . . . . . . . . . . . . 183
Reflex function block: PWM (Pulse Width Modulation) . . . . . . . . . . . . . . . . . . . 186
Reflex function block: Detection of underspeed. . . . . . . . . . . . . . . . . . . . . . . . . 187
Reflex function block: Type 1 command-check . . . . . . . . . . . . . . . . . . . . . . . . . 192
Reflex function block: Type 2 command-check . . . . . . . . . . . . . . . . . . . . . . . . . 194
Reflex function block: Command-counting . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
9.3
Presentation of the reflex function configuration editor . . . . . . . . . . . . . . . . . . . 203
Adjusting the configuration parameters of a reflex function . . . . . . . . . . . . . . . . 206
35012326 00 July 2006
9.4
Bits and words associated with discrete reflex module . . . . . . . . . . . . . . . . . . . 209
Implicit exchange language objects associated with module
Explicit exchange language objects associated with module
Part III AS-i Bus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
Chapter 10 General introduction to the AS-i Bus . . . . . . . . . . . . . . . . . . . 217
Architecture of the TSX SAY 100 module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
How to declare an AS-i communication module in the PLC rack . . . . . . . . . . . 224
How to access the AS-i Bus configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
Chapter 11 AS-i bus configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
Description of an AS-i communication module’s configuration screen . . . . . . . 228
How to define a slave device on the AS-i bus. . . . . . . . . . . . . . . . . . . . . . . . . . 230
How to modify the AS-i Bus software configuration . . . . . . . . . . . . . . . . . . . . . 233
How to access the description of an AS-i slave . . . . . . . . . . . . . . . . . . . . . . . . 234
How to define a new slave profile in the standard AS-I catalogue . . . . . . . . . . 236
How to modify AS-i slave general parameters: Automatic addressing . . . . . . . 238
How to modify AS-i slave general parameters: Fallback mode. . . . . . . . . . . . . 239
Chapter 12 Debugging the AS-i bus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
Description of an AS-i module’s debugging screen. . . . . . . . . . . . . . . . . . . . . . 243
How to access functionality in the module diagnostics and channel
How to access adjustment of an AS-i device’s parameters . . . . . . . . . . . . . . . 249
How to access the AS-i channels’ forcing/unforcing function . . . . . . . . . . . . . . 250
How to access the SET and RESET commands of the AS-i channels . . . . . . . 251
Automatic replacement of a faulty AS-i slave . . . . . . . . . . . . . . . . . . . . . . . . . . 252
How to insert a slave device into an existing AS-i configuration. . . . . . . . . . . . 253
How to modify the address of an AS-i device . . . . . . . . . . . . . . . . . . . . . . . . . . 254
Chapter 13 Bits and words associated with the AS-i function . . . . . . . . 255
13.1
Addressing objects associated with the AS-i function . . . . . . . . . . . . . . . . . . . . 257
35012326 00 July 2006
9
10
Adressing language objects associated with slave devices connected to the
13.2
Language objects associated with the AS-i function . . . . . . . . . . . . . . . . . . . . . 258
Implicit exchange objects associated with the AS-i function . . . . . . . . . . . . . . . 259
Management of exchanges: Module %MWxy.MOD.0:Xj or channel
Exchange management: Module %MWxy.MOD.1:Xj or channel
Explicit exchange objects: %MWxy.0.2:Xj to %MWxy.0.23:Xj channel status. . 263
Explicit exchange object: %MWxy.0.24:Xj channel command. . . . . . . . . . . . . . 265
Explicit exchange object: %MWxy.0.25 to %MWxy.0.56 parameter
Explicit exchange object: Status %MWxy.MOD.2:Xj . . . . . . . . . . . . . . . . . . . . . 267
Chapter 14 AS-i operating mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
Chapter 15 AS-i performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277
Chapter 16 DFB for AS-i Security Monitor . . . . . . . . . . . . . . . . . . . . . . . . 279
Part IV AS-i V2 bus. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
Chapter 17 General introduction to the AS-i V2 Bus . . . . . . . . . . . . . . . . 283
Structure of a Standard Address AS-i slave . . . . . . . . . . . . . . . . . . . . . . . . . . . 290
How to Declare an AS-i Communication Module in the PLC Rack . . . . . . . . . . 292
How to Access Configuration of the AS-i V2 Bus . . . . . . . . . . . . . . . . . . . . . . . 293
Chapter 18 AS-i V2 bus configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295
Description of an AS-i V2 communication module’s configuration screen. . . . . 296
How to define a slave device on the AS-i V2 bus . . . . . . . . . . . . . . . . . . . . . . . 298
35012326 00 July 2006
How to modify the AS-i V2 Bus software configuration . . . . . . . . . . . . . . . . . . . 302
How to access the description of an AS-i V2 slave . . . . . . . . . . . . . . . . . . . . . . 303
How to define a new slave profile in the standard AS-i V2 catalog . . . . . . . . . . 305
How to modify the general parameters of an AS-i V2 slave: Automatic
How to modify the parameters of an AS-i V2 slave. . . . . . . . . . . . . . . . . . . . . . 308
How to modify the parameters of an analog AS-i V2 slave . . . . . . . . . . . . . . . . 309
How to Modify the Parameters of an AS-i V2 Slave with Combined
Chapter 19 Debugging the AS-i V2 bus . . . . . . . . . . . . . . . . . . . . . . . . . . . 313
Description of an AS-i V2 module's debugging screen . . . . . . . . . . . . . . . . . . . 315
How to access module- and channel-diagnostics functions on an AS-i V2
How to access adjustment of an AS-i V2 device's parameters . . . . . . . . . . . . . 321
How to access the AS-i V2 digital channels' forcing/unforcing function . . . . . . 323
How to access the SET and RESET commands on AS-i V2 digital channels . 324
How to modify the value of an analog channel . . . . . . . . . . . . . . . . . . . . . . . . . 325
Automatic replacement of a faulty AS-i V2 slave . . . . . . . . . . . . . . . . . . . . . . . 326
How to insert a slave device into an existing AS-i V2 configuration.. . . . . . . . . 327
How to modify the address of an AS-i V2 device . . . . . . . . . . . . . . . . . . . . . . . 328
Chapter 20 Bits and words associated with the AS-i V2 function . . . . . . 329
20.1
Addressing objects associated with the AS-i V2 function . . . . . . . . . . . . . . . . . 330
Addressing Language Objects Associated with Slave Devices Connected to
20.2
Language objects associated with the AS-i V2 function . . . . . . . . . . . . . . . . . . 331
Implicit exchange objects associated with the AS-i V2 function . . . . . . . . . . . . 332
Exchange management: Module %MWxy.MOD.0:Xj or channel
Exchange management: Module %MWxy.MOD.1:Xj or channel
Explicit Exchange Objects: %MWxy.MOD.2 and %MWxy.0.2:Xj to
Constant %KWxy.i.r configuration objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341
Explicit Exchange Object: %MWxy.0.74:Xj channel command. . . . . . . . . . . . . 342
Explicit Exchange Object: %MWxy.0.75 to %MWxy.0.138 Parameter
Explicit Exchange Object: Status %MWxy.MOD.2:Xj . . . . . . . . . . . . . . . . . . . . 344
35012326 00 July 2006
11
12
Chapter 21 AS-i V2 operating mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345
AS-i V2 Data Exchange Off Operating Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . 350
Chapter 22 AS-i V2 performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351
Chapter 23 DFB for AS-i Security Monitor . . . . . . . . . . . . . . . . . . . . . . . . 353
Description of the security function block of the AS-i bus . . . . . . . . . . . . . . . . . 354
Part V Operator Dialog functions . . . . . . . . . . . . . . . . . . . . . . . 361
Chapter 24 General presentation of the Operator Dialog functions. . . . 363
Chapter 25 Built-in DOP functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365
25.1
Description of the parameters common to the different DOP functions. . . . . . . 367
25.2
35012326 00 July 2006
Chapter 26 Appendices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423
26.1
26.2
Description of the built-in DOP functions "Data to send" parameter coding . . . 426
PLC status message display: SEND_MSG function . . . . . . . . . . . . . . . . . . . . . 427
PLC checked status message entry: ASK_MSG and GET_MSG function . . . . 431
PLC alarm message display: SEND_ALARM function . . . . . . . . . . . . . . . . . . . 436
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 of luminous column LEDS: CONTROL_LEDS function . . . . . . . . . . . . 441
Configuring command keys: ASSIGN_KEYS function . . . . . . . . . . . . . . . . . . . 442
Generic send command: PANEL_CMD function. . . . . . . . . . . . . . . . . . . . . . . . 444
Glossary
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445
Index
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447
35012326 00 July 2006
13
14 35012326 00 July 2006
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
Hardware installation manual
Reference Number
TSX DM 57 xxE
User Comments We welcome your comments about this document. You can reach us by e-mail at [email protected].
35012326 00 July 2006
15
About the Book
16 35012326 00 July 2006
Shared application-specific functions
I
Presentation
Subject of this part
What's in this
Part?
This part gives a general overview of the acknowledgment of specific applications by the PL7 software.
This part contains the following chapters:
Chapter
1
2
3
4
Chapter Name
Common application specific functions: General
Objects associated with specific applications
Application-specific instructions
Appendices
Page
17
35012326 00 July 2006
Shared application-specific functions
18 35012326 00 July 2006
Common application specific functions: General
1
Presentation
Subject of this chapter
What's in this
Chapter?
This chapter presents the common application specific functions of the PL7 software.
This chapter contains the following topics:
Topic
General Presentation
Configuration of an application-specific function.
Adjustment of an application-specific function
Debugging an application-specific function
Page
35012326 00 July 2006
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).
z
An application-specific function on Premium is presented, depending on the application, in the form of: z a module (e.g.: counting application), a built-in interface (e.g.: communication port).
Integrated interface
0
6
0
P
S
Y
0
0
3
5
7
S
X o m m
1 2
T
Y
A
3 4
Application-specific module
20 35012326 00 July 2006
Software installation principle
Software installation resources
General
The table below gives a short description of the general principle for the installation of an application-specific function. This principle will be covered again later in this manual in more specific detail for each application.
Mode
Local
Local or online
Phase Description
Configuration Configuration of the module or built-in interface
Symbolization Symbolization of variables associated with the application-specific function.
Programming Programming of the function to be carried out using: z bit and word objects associated with the module, z application-specific instructions.
Online Transfer
Debug
Transferring the application to the PLC.
Debugging the application (I/O control, fault identification).
Local (or online) Documentation Printing of the different information about the application.
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).
An application-specific function is installed using: z standard PL7 tools: z pull-down menus, z z z status bars, tool bars, editors, z
...
application-specific screens, z z z z configuration screens, adjustment screens, z debug screens, language objects giving program-based access to inputs and outputs of the module or built-in interface.
instructions relative to the application-specific function, where applicable.
Note: The different screens as well as the objects associated with an applicationspecific 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.
35012326 00 July 2006
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: z in local mode, z 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
Counter 0
Function:
Up/Down counting
Input interfaces
IA Up/Down counts, application direction
Solid state counter
Line check Multiply by 1 by 4
Preset on IPres
Rising edge IPres
Read on IRead
Rising edgeIRead
Task :
MAST
Event
EVT 3
Reset Outputs
Manual
Automatic
Fallback Mode
Reset
Maintain
Here, the operating characteristics are: z the selection of a function associated with a channel: up counting, down counting or up/down counting, z z z z selection of the task which updates the inputs/outputs of the module, the type of reactivation of outputs, the type of fallback mode,
...
22 35012326 00 July 2006
Confirmation
General
The characteristics defined in the configuration screen must be subject to a global confirmation of the application. This may be done: z z in local mode, so that the modifications are taken into account, in online mode in order to: z update the configuration parameters in the PLC, z reconfigure the channel of the module with its new parameters (the adjustment parameters return to their initial value).
35012326 00 July 2006
23
General
Adjustment of an application-specific function
Introduction The Adjustment function allows the operating parameters of the applicationspecific module or interface to be displayed and modified, when they are modifiable.
This function is carried out from the PL7 adjustment editor: z in local mode, in order to define the initial parameters (value of the parameters during setup or on a cold restart), z 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 :
Counter 0
Function:
Up/Down counting
Preset value
Initial value
1 000
1000
Threshold value
Threshold
Initial value
2 000
2000
Threshold
Initial value
3 000
3000
Setpoint values
High
Initial value 0
0
Low
Initial value 0
0
Counter output state
Here, the operating parameters are: z z z the threshold values, the setpoint values, the counter output states.
24 35012326 00 July 2006
Confirmation
General
The characteristics defined in the adjustment screen must, depending on the mode, be subject to: z z local: a global confirmation of the application, online: confirmation of the modifications in order to update the current parameters in the PLC and on the module channel.
35012326 00 July 2006
25
General
Debugging an application-specific function
Introduction
Illustration
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: z z display of module channel status, display of possible faults, z z z control of language objects, and, in the event of a fault, access to the module or channel diagnostics,
...
This function is carried out in online mode , with the PLC in STOP or in RUN, from the PL7 debug editor.
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.
0
1
4
5
2
3
6
7
Symbol
0
0
0
0
0
0
0
0
State Fault
DIAG...
DIAG...
DIAG...
DIAG...
DIAG...
DIAG...
DIAG...
DIAG...
Reactivate
Reactivate
Applied Q
STOP
Control of channel
Forcing
F4 Force to 0
F5
F6
Write
F7
Force to1
Unforce
Set
F8 Reset x
Here the debug tools are: z forcing of the output channels to 0 or 1, z access to module and channel diagnostics.
26 35012326 00 July 2006
Objects associated with specific applications
2
Presentation
Subject of this chapter
What's in this
Chapter?
This chapter presents the addressing and the exchange modes for language objects associated with PL7 specific applications.
This chapter contains the following sections:
Section
2.1
2.2
2.3
2.4
Topic
Addressing of language objects associated with specific applications
Implicit exchanges
Explicit exchanges
Presymbolization
Page
27
35012326 00 July 2006
Objects associated with specific applications
28 35012326 00 July 2006
2.1
Objects associated with specific applications
Addressing of language objects associated with specific applications
Presentation
Subject of this section
What's in this
Section?
This section presents the addressing of language objects associated with application-specific modules.
This section contains the following topics:
Topic
Addressing of built-in application-specific interfaces
Addressing input/output module objects in rack
Addressing of language objects for modules remoted on the FIPIO bus
Addressing of language objects associated with AS-i bus
Page
35012326 00 July 2006
29
Objects associated with specific applications
Addressing of built-in application-specific interfaces
Presentation
Illustration
The Premium range offers 4 types of built-in application-specific interfaces such as: z terminal socket link, z z communication interface,
FIPIO interface, z process control channels.
Their addressing depends on the basic topology of the application. In other words: z z on the type of power supply, on the processor type.
The illustration below shows the different basic topologies.
Processor slot 0
0
6
0
P
S
Y
1
5
5
7
3
S
X
0
F o i p i o m m
1 2
0
0
8
5
S
Y
3 4
1
3
5
7
1
T
S
X
C o m m
F p i o i
2 3
5
0
P
S
Y
4
1
5
3
7
4
T
S
X
L p s o o
C o m m
F p i o i
3 4
Processors slot 1
30 35012326 00 July 2006
Objects associated with specific applications
Number of channels
The tableau below shows the assignment of built-in application-specific channel addressing depending on the processor used in the application.
Processor Terminal socket
Channel x.0
TSX 57-103
TSX 57-153
TSX 57-203/2623
TSX 57-303/3623
TSX 57-253/2823
TSX 57-353
TSX 57-453/4823
PCX 57-203 -
PCX 57-353
(x): 0 when the processor is in slot 0,
1 when the processor is in slot 1,
Communication interface FIPIO interface Process control channels
Channel x.1
-
Channel x.2
-
-
Channel x.2
Channels x.4 to x.13
Channels x.4 to x.18
Channels x.4 to x.13
Channels x.4 to x.18
Channel 1 -
Channel 2
Channels x.4 to x.23
Channels 4 to 13
Channels 4 to 18
35012326 00 July 2006
31
Objects associated with specific applications
Addressing input/output module objects in rack
Presentation
Illustration
Addressing input/output module bit and word principal objects is done geopgraphically. That means that it depends: z z z on the number (address) of the rack, the physical position of the module in the rack, the module channel number.
Addressing is defined in the following way:
% I, Q, M, K X, W, D, F
Symbol Object type Format
X
Rack
Y
Position i r
Channel no. Rank
32 35012326 00 July 2006
Objects associated with specific applications
Syntax The table below describes the different elements that make up addressing.
Family
Symbol
Object type
Format (size)
Rack address
Module position
X
W
D
F
I
Q
Element Values Description
% -
M -
-
Picture of the physical input of the module,
Picture of the physical output of the module,
This information is exchanged automatically each cycle of the task to which they are attached.
Internal variable
This reading or writing information is exchanged at the request of the application.
K -
-
16 bits
32 bits
32 bits
Internal constant
This configuration information is available as read only.
Boolean
For Boolean objects this element can be omitted.
Single length.
Double length.
x y
0 or 1
0 - 7
00 - 14
(1)
Floating. The floating format used is the IEEE Std 754-1985 standard
(equivalent to IEC 559).
TSX 5710/102/103/153, PMX 57102, PCX 571012).
Other processors.
Position number in the rack.
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.
Row r i 0 - 127 or
MOD
0 - 127 or
ERR
MOD : channel reserved for managing the module and parameters common to all the channels.
Position of the bit in the word.
ERR: indicates a module or channel fault.
(1) : the maximum number of slots means that 2 racks must be used for the same address.
35012326 00 July 2006
33
Objects associated with specific applications
Examples The table below shows some examples of addressing objects.
Object
%MW2.0.3
%MW103.0.3
Description
Status word of row 3 of track 0 of the discrete input module on position 2 of rack 0.
Status word of row 3 of track 0 of the discrete input module on position 3 of rack 1.
%I102.MOD.ERR
Information on analogue input module fault on position 2 of rack 1.
%I204.3.ERR
Information on a fault on channel 3 of the analogue output module on position 4 of rack 2.
Illustration
0
0
0
2
6
S
Y
0
T
S
X
0
3
7
2
L p s o o o
C o m m
2
1
0
0
2
6
S
Y
0 1 2
0
8
0
A
E
Y
3
3
5
8
R
S
Y
4
4
2
6
0
P
S
Y
0 1 2 3 4
A
S
Y
8
0
34 35012326 00 July 2006
Objects associated with specific applications
Addressing of language objects for modules remoted on the FIPIO bus
Presentation
Illustration
Addressing for the main bit and word objects for modules remoted on the FIPIO bus is geographical. This means that it depends on: z z z the connection point, the module type (base or extension), the channel number.
Addressing is defined as follows:
% I, Q, M, K X, W, D, F
Symbol Object type Format
\ p.2.c
\
Module/channel address and connection point m
Module number i
Channel number r
Rank
35012326 00 July 2006
35
Objects associated with specific applications
Syntax The table below shows the different elements which constitute addressing.
Family
Symbol
Object type
Format (size)
Module/channel address and connection point c
Module position m p
2
W
D
F
I
Q
Element Values Meaning
% -
M -
-
Image of the module's physical input,
Image of the module's physical output,
This information is exchanged automatically on each cycle of the task to which it is connected.
Internal variable
This read or write information is exchanged at the request of the application.
K
X -
Internal constant
This configuration information is only accessible in read-only.
Boolean
For boolean-type objects, the X may be omitted.
16 bits
32 bits
32 bits
Single length.
Double length
Floating. The floating format used is that of IEEE standard 754-1985
(equivalent IEC 559).
-
0 or 1 Number of the processor's position in the rack.
Channel number of the processor's built-in FIPIO link.
1 to 127 Number of the connection point.
0 or 1 0 : base module, 1: extension module.
Channel no.
Position r i 0 to 127 or MOD
0 to 255 or ERR
MOD: channel reserved for management of the module and the parameters shared by all channels.
ERR: indicates a module or channel fault.
36 35012326 00 July 2006
Examples
Objects associated with specific applications
The table below gives some examples of object addressing.
Object
%MW\0.2.1\0.5.2
%I\0.2.1\0.7
Meaning
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.
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
%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.
image bit of output 2 of the remote output extension module located at connection point 1 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
35012326 00 July 2006
37
Objects associated with specific applications
Addressing of language objects associated with AS-i bus
Presentation
Illustration
Addressing for the main bit and word objects associated with the AS-i bus is geographical. This means that it depends on: z z z the number (address) of the rack where the interface card is positioned, the physical position of the interface card in the rack, the number (address) of the slave device on the AS-i bus.
Addressing is defined as follows:
% I ou Q
Symbol Object type
\ xy.0
Rack/module/channel addrss for TSX SAY 100
\ n
Slave number i
Bit rank
Syntax The table below describes the different elements which constitute addressing.
Family
Symbol
Object type I
Element Values
% -
Q -
-
-
Description
Image of the module's physical input,
Image of the module's physical output,
This data is exchanged automatically on every cycle of the task to which it is connected.
TSX 5710/102/103/153, PMX 57102, PCX 571012).
Other processors
Rack address
Module position
Channel no.
Slave no.
x y
0 n
0 or 1
0 to 7
00 to 14
(1)
-
0 to 31
Rack position number.
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).
The interface card TSX SAY 100 only has one channel.
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.
38 35012326 00 July 2006
Example
Objects associated with specific applications
The table below gives some examples of object addressing.
Object
%I3.0\2.2
%Q3.0\4.3
Description
Input 2 of slave 2, the module TSX SAY 100 being positioned at slot 3 of rack 0.
Output 3 of slave 4, the module TSX SAY 100 being positioned at slot 3 of rack 0.
0
6
0
P
S
Y
0
5
7
S
X
0
3 o o o m
1 2 3
0
0
A
Y
4
0
1
2
3
P ABE-8R44SB11
4 P
XVA-S102
35012326 00 July 2006
39
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: z the outputs are in the fallback position (fallback mode), z 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
40 35012326 00 July 2006
Objects associated with specific applications
Examples
Object
%I103.1
%IW4.2
%IW203.2:X4
%Q306.5
%I6.5.ERR
%I107.MOD.ERR -
The table below shows several examples of implicit exchanges relating to a given application.
Description Specific application
Discrete
Analog
-
Counting
Discrete
Gives the status of channel 1 of the module located in position 3 of rack 1.
Gives the analog value of channel 2 of the module located in position 4 of rack 0.
Gives the status of the capture input of the module located in position 3 of rack 2.
Gives the status of channel 5 of the module located in position 6 of rack 3.
Indicates, when the bit is set to 1, that channel 5 of the module located in position
6 of rack 0 is faulty.
Indicates, when the bit is set to 1, that the module located in position 7 of rack 1 is faulty.
35012326 00 July 2006
41
Objects associated with specific applications
2.3
Explicit exchanges
Presentation
Subject of this section
What's in this
Section?
This section presents the principle of explicit exchanges as well as the different instructions which allow them to be carried out.
This section contains the following topics:
Topic
Explicit exchanges: General
READ_STS: Reading status words
WRITE_CMD: Writing command words
READ_PARAM: Reading adjustment parameters
WRITE_PARAM: Writing adjustment parameters
SAVE_PARAM: Saving adjustment parameters
RESTORE_PARAM: Restoring adjustment parameters
Exchange and report management
Page
42 35012326 00 July 2006
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: z z
READ_STS (reading status words),
WRITE_CMD (writing command words) z z z
WRITE_PARAM (writing adjustment parameters),
READ_PARAM (reading adjustment parameters),
SAVE_PARAM (saving adjustment parameters),
RESTORE_PARAM (restoring adjustment parameters), z
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 applicationspecific 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).
35012326 00 July 2006
43
Objects associated with specific applications
General principle of use for explicit instructions
The diagram below shows the different types of explicit exchange possible between the PLC processor and the module (or the built-in interface).
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
Command words
WRITE_CMD
Command words
Adjustment parameters current
WRITE_PARAM
READ_PARAM
SAVE_PARAM
Adjustment parameters current
Adjustment parameters initial
RESTORE_PARAM
Only with the READ_RTS and WRITE_CMD instructions.
Exchange management
During an explicit exchange, it may prove advantageous to check on its progress, in 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: z z detection of an exchange in progress, the end of exchange report.
The summary below explains the principle for management of an exchange
Execution of an explicit exchange
Detection of an exchange in progress
Report of the end of the exchange
44 35012326 00 July 2006
Objects associated with specific applications
Logical channel
%CHxy.i
The channel %CHxy.i is a general syntax used to update, via the explicit 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 FIPIO bus
The number of explicit exchange functions activated simultaneously is limited to 24 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 ).
35012326 00 July 2006
45
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 Premium range: z z
%MWxy.MOD.2 (module level fault),
%MWxy.i.2 (channel i level fault).
Illustration Writing instruction
Processor PLC
Objects %MWxy.ir or
%MWxy.MOD.2
Status words READ_STS
E/S Module or interface built-in task
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.
i y
Element
READ_STS
%CH x
Description
Name of the instruction
Channel-type object
Rack address.
Module position.
Channel or MOD number.
46 35012326 00 July 2006
Examples
Objects associated with specific applications
The example below presents some examples of explicit exchanges using the
READ_STS instruction.
Object
READ_STS%CH302.1
Description
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.
35012326 00 July 2006
47
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
Processor PLC
Objects %MWxy.ir or
%MWxy.MOD.2
Command words
WRITE_CMD
E/S Module or interface built-in task
Command words
Syntax
Examples
The WRITE_CMD instruction is defined as follows:
WRITE_CMD%CHxy.i
The table below describes the different elements which constitute the instruction.
i y
Element Description
WRITE_CMD Name of instruction.
%CH x
Channel-type object.
Rack address.
Module position.
Channel number.
The table below gives an example of an explicit exchange using the WRITE_CMD instruction.
Object
WRITE_CMD%CH3.0
Description
Writing the command information of channel 0 of the module located in position 3 of rack 0.
48 35012326 00 July 2006
READ_PARAM: Reading adjustment parameters
Objects associated with specific applications
Introduction
Illustration
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 .
Read instruction
Processor PLC
%MWxy.i.r objects
Current adjustment parameters
READ_PARAM
E/S Module or interface built-in task
Current adjustment parameters
Syntax
Examples
The READ_PARAM instruction is defined as follows:
READ_PARAM%CHxy.i
The table below describes the different elements which constitute the instruction.
i y
Element Description
READ_PARAM Name of instruction.
%CH x
Channel-type object.
Rack address.
Module position.
Channel number.
The table below gives an example of an explicit exchange using the READ_PARAM instruction.
Object
READ_PARAM%CH3.1
Description
Reading the adjustment parameters of channel 1 of the module located in position 3 of rack 0.
35012326 00 July 2006
49
Objects associated with specific applications
WRITE_PARAM: Writing adjustment parameters
Introduction
Illustration
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 .
Write instruction
Processor PLC
E/S Module or interface built-in task
%MWxy.i.r objects
WRITE_PARAM
Adjustment parameters current
Adjustment parameters current
Syntax
Examples
The WRITE_PARAM instruction is defined as follows:
WRITE_PARAM%CHxy.i
The table below describes the different elements which constitute the instruction.
i y
Element
WRITE_PARAM
%CH x
Description
Name of instruction.
Channel-type object.
Rack address.
Module position.
Channel number.
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.
50 35012326 00 July 2006
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
%MWxy.i.r objects
Adjustment parameters current
Adjustment parameters initial
SAVE_PARAM
E/S Module or interface built-in task
Adjustment parameters current
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.
i y
Element
SAVE_PARAM
%CH x
Description
Name of the instruction.
Channel-type object.
Rack address.
Module position.
Channel number.
35012326 00 July 2006
51
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.
52 35012326 00 July 2006
Objects associated with specific applications
RESTORE_PARAM: Restoring adjustment parameters
Introduction
Illustration
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
Writing instruction
Processor PLC
%MWxy.i.r objects
Adjustment parameters current
RESTORE_PARAM
E/S Module or interface built-in task
Adjustment parameters current
Adjustment parameters initial
Syntax
Examples
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 i y
Description
RESTORE_PARAM Name of the instruction
%CH x
Channel-type object.
Rack address.
Module position.
Channel number.
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.
35012326 00 July 2006
53
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: z z
%MWxy.i: Exchange in progress,
%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
Adjustment parameters
WRITE_CMD
WRITE_PARAM
READ_PARAM
SAVE_PARAM
RESTORE_PARAM
54 35012326 00 July 2006
Description of significant bits
Objects associated with specific applications
Each of the bits of the words %MWxy.i and %MWxy.i.1 is associated with a type of parameter: z position 0 bits are associated with status parameters: z the bit %MWxy.i.0:X0 indicates whether a status word read request is in progress, z z position 1 bits are associated with command parameters: z the bit %MWxy.i.0:X1 indicates whether the control parameters have been sent to channel i of the module, z the bit %MWxy.i.1:X1 specifies whether the control parameters have been accepted by channel i of the module, position 2 bits are associated with adjustment parameters: z the bit %MWxy.i.0:X2 indicates whether the adjustment parameters have been z z exchanged with channel i of the module (by WRITE_PARAM, READ_PARAM,
SAVE_PARAM, RESTORE_PARAM), 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, 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).
35012326 00 July 2006
55
Objects associated with specific applications
Example Phase 1: Transmission of data using the WRITE_PARAM instruction
PLC memory
1
0
Status words
Command words
Current adjustment parameters
E/S module memory or built-in application specific function
Status words
Command words
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
0
1
Status words
Command words
Current adjustment parameters
E/S module memory or built-in application specific function
Status words
Command words
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.
56 35012326 00 July 2006
Objects associated with specific applications
2.4
Presymbolization
Presentation
Subject of this section
What's in this
Section?
This section presents the presymbolization function for the objects of a specific application.
This section contains the following topics:
Topic
Presymbolized objects
Automatic symbolization of objects associated with a channel
Page
35012326 00 July 2006
57
Objects associated with specific applications
Presymbolized objects
Role
Syntax
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.
These objects are symbolized with the following syntax:
PREFIX_USER_SUFFIX_MANUFACTURER
The elements have the following meaning and characteristics:
Element
PREFIX_USER
SUFFIX_MANUFACT
URER
Maximum number of characters
12
20
Description generic symbol given to the channel by the user part of the symbol which corresponds to the bit object or word of the channel given by the system
Example
Note: As well as the symbol, a manufacturer’s comment is automatically generated, this comment recalls succinctly the object’s role.
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
%ID3.0.4
DWORD Pieces_count_capt
%I3.0
%I3.0.1
Counter current value
Counter captured value
EBOOL Pieces_count_enab_activ Counter enable active
EBOOL Pieces_count_pres_done Preset done
58 35012326 00 July 2006
Objects associated with specific applications
Automatic symbolization of objects associated with a channel
Introduction
Conditions required
Procedure
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.
Automatic symbolization implies that: z z the module has been declared in the PL7 configuration in advance.
the application-specific module accepts this function. The specific applications concerned are: z analog, z z counting, axes control, z z z z step by step control, weighing, process control, communication (requires an in-rack interface card).
The table below shows the procedure for the automatic symbolization of objects associated with a channel.
Step
1
2
3
4
5
Action
Access the variable editor.
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.
Double-click on the P button for the channel to be symbolized.
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.
Confirm with the Presymbolize button.
35012326 00 July 2006
59
Objects associated with specific applications
De-activating automatic symbolization.
Canceling automatic symbolization, for a given logical channel, makes it possible to delete all or part of an object's symbols.
Two options are proposed:
If the option chosen is …
Delete all presymbols
Delete prefixed presymbols then …
No prefix is chosen: all symbols are deleted (including those which have been modified directly using the editor).
Only objects with a prefix identical to that entered are deleted.
60 35012326 00 July 2006
Application-specific instructions
3
Presentation
Subject of this chapter
What's in this
Chapter?
This chapter presents the application-specific instructions.
This chapter contains the following topics:
Topic
Application-specific instructions
Accessing a specific function, method or procedure type instruction
Page
35012326 00 July 2006
61
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 specific instruction
The SMOVE (method type) function dedicated to movement control modules
(TSX CAY and TSX CFY) enables movements to be made.
SMOVE %CH103.2 (01,90,01,10000000,200,0)
Each parameter has a particular meaning: z z z
10000000 is the coordinate to be attained in micrometers,
200 is the movement speed of the moving part in mm/minute,
...
62 35012326 00 July 2006
Application-specific instructions
Accessing a specific function, method or procedure type instruction
Presentation
Calling up a function
Application-specific function entry can be accessed by: z directly entering the instruction and its parameters in an operate block, z by the entry help function accessible through the program editors (LD, IL, ST).
Step
1
2
Action
Access the required editor.
Depending on the editor used, choose one of the following methods to open the function library.
z Press Shift + F8 (LD, IL,ST editors).
z z
Click on the (LD editor) icon.
Select the command Utilities → Enter call for a (IL, ST editors) function.
Note: The function library appears.
PL7 : Library functions
EF
Function information Parameters
Family
Characters string
Lib.V. App.V
Name
2.00 -
Interpolation Command 1.0
-
SMOVE
Movement Command
Communication
Call format
2.00 -
3.07 -
Parameters of the METHOD:
Name Type
Channel MAIN Channel
NRUN WORD
G9 World
Kind
IN
IN
Comment
Movement number
G9
Detail...
Comment
Automatic movement command
Family
%CH103.2
01
90
?
3
4
5
Display the call
SMOVE %CH103.2 ( 01.90.01.10000000.20000.0 )
OK Cancel
Select the specific application in the Family field.
Select the instruction in the Name field.
Many of the instructions have a customized entry help screen.
Access this screen by clicking on the Details button.
35012326 00 July 2006
63
Application-specific instructions
Step
6
7
Action
Enter each instruction parameter (each instruction is developed in the relevant application-specific documentation) z in the customized screen z or in the Entry field in the Library Functions screen. To do this, the Parameter item must be selected in the Function Information field.
Click Ok to confirm.
64 35012326 00 July 2006
Appendices
4
Presentation
Subject of this chapter
What's in this
Chapter?
This chapter introduces several elementary notions that are useful for the installation of application-specific functions.
Some of these notions are taken from the PL7 Installation and Start-up Guide.
This chapter contains the following topics:
Topic
Reminders concerning the configuration editor
The PL7 toolbar
The PL7 status bar
How to declare a module in a PLC rack
How to declare a remote module on the FIPIO bus.
Confirming the configuration of a module.
Globally reconfiguring an application.
Application-specific fault processing (in-rack modules) by program
Processing of FIPIO faults
Page
65
35012326 00 July 2006
Appendices
Reminders concerning the configuration editor
Presentation
Illustration
The configuration editor enables the various constitutive elements of the PLC to be declared and configured in a graphical and intuitive manner: z z rack, power supply, z z processor, application-specific modules.
In online mode the configuration editor also performs debug, adjustment and diagnostics functions.
The following screen provides an example of a hardware configuration.
Configuration
TSX 57103 V4.0 ...
0
XMWI
XTI..
0 o
C o m m
1
E
Y
2 3 4 5
C
1
6
I
P
66 35012326 00 July 2006
Accessing the editor
Appendices
The following table shows the different ways of accessing the configuration editor.
From: the menu bar the application browser
Action
Select Tools → Configuration .
Double-click on Hardware configuration or select it using the arrow keys and confirm with Enter .
Application Browser
Structure View
STATION
Configuration
Hardware configuration
Software configuration
Program
MAST Task
Events
DFB types
Variables
Animation tables
35012326 00 July 2006
67
Appendices
The PL7 toolbar
Presentation
Illustration
Elements and functions
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.
The PL7 toolbar is displayed as follows:
?
?
This table gives the function of each element in the toolbar:
Element Function
New application
Element Function
Local mode
Open an application
Save the application
Print all or part of the application
Undo last modifications
Confirm modifications
Go to
Application browser
Online mode
RUN
PLC changes to RUN
STOP
PLC changes to STOP
Start / Stop the animation
Organize windows so that they overlap
Tile windows horizontally
Tile windows vertically
Cross references
Function library
PLC <-> terminal transfer
?
?
Help
What's this?
Note: All these functions can also be accessed via the menu.
68 35012326 00 July 2006
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
Ready
2
ONLINE
3
STOP
4
U:SYS
5 6
GR7 OK MODIF
7 8
OVR CAPS
Elements and functions
This table describes the different zones that make up the status bar:
Number Zone
1
4
5
2
3
6
7
8
Information
Operating mode
PLC state indicates the current operating mode (offline, online).
indicates the PLC state (Run, Stop, faulty, etc.).
Network address gives the network address of the PLC.
Grafcet mode indicates whether Grafcet mode is used in the application.
Modification in progress
Animation indicator
Keyboard functions
Function supplies information concerning menu commands, toolbar icons and the different editors when these are selected.
indicates that the current application has not been saved or is different from the back-up.
indicates that the PLC is in online mode.
indicates the status of the functions.
Insert and All Caps keyboard
35012326 00 July 2006
69
Appendices
How to declare a module in a PLC rack
Procedure
3
4
5
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
1
2
Action
Access the application's hardware configuration screen.
Double-click on the slot in which the module is to be configured.
Result: the Add module screen appears.
Add module
Family:
Analog Module1.5
Communication1.5
Counting1.5
Remote BusX1.0
Movement1.5
Weighing1.5
Simulation1.0
Discrete I/O1.5
Module:
TSX DEY 08D2
TSX DEY 16A2
TSX DEY 16A3
TSX DEY 16A4
TSX DEY 16A5
TSX DEY 16D2
TSX DEY 16D3
TSX DEY 16FK
TSX DEY 32D2K
TSX DEY 32D3K
TSX DEY 64D2K
TSX DMY 28FK
8I 24VDC SINK BORN
16I 24VAC BORN
16I 48VAC BORN
16I 110/120VACBORN
16I 220/240VAC BORN
16I 24VDC SINK BORN
16I 48VDC SINK BORN
16I FAST 24VDC SINK CONN
32I 24VDC SINK CONN
32I 48VDC SINK CONN
64I 24VDC SINK CONN
16I 24VDC.12S 24 VCC
OK
Cancel
Select the specific application (e.g.: Discrete ) in the Family field.
Select the module reference in the Module field.
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
TSX 57452 V5.0 ...
XMWI
XTI..
0
P
S
Y
2
6
0
T
S
X
5
7
5
2
L p s o o
F o i p i o m m
2
1
3
D
2
0
8
E
Y
4
70 35012326 00 July 2006
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
1
2
Action
Access the application's hardware configuration screen.
Double-click on the processor's FIPIO zone.
Result: the FIPIO Configuration screen appears
FIPIO Configuration
TSX 57453 V5.0
Logical address
Bus length:
Communicator
0
1
Base module
15 km Devices configured: 0
Extension module
0 Fipio managerTSX 57453
63 Privileged terminal
3
12
Double-click on one of the available connection points.
Result: the Add/Modify device screen appears.
Add/Modify a Device
Connection point
Comment
Connection number 1 OK
Cancel
Families
ATV-16 1.0
ATV-581.0
CCX-171.0
CCX17-321.0
MAGELIS1.0
MOMENTUM1.0
PASSERELLE1.0
SIMULATION1.0
STD_P1.0
TBX1.0
TSX1.0
Module de base
ATV16U09M2/50Hz ATV 0.37kw 240V 50Hz
ATV16U09M2/60Hz
ATV16U18M2/50Hz
ATV16U18M2/60Hz
ATV16U18N2/50Hz
ATV16U18N2/60Hz
ATV16U29M2/50Hz
ATV16U29M2/60Hz
ATV16 0.5HP 240 V 60Hz
ATV16 0.75kw 240 V 50Hz
ATV16 1.0HP 240 V 60Hz
ATV16 0.75kw 460 V 50Hz
ATV16 1.0HP 460 V 60Hz
ATV16 1.5kw 240 V 50Hz
ATV16 2.0HP 240 V 60Hz
Communicator
TSX FPP 010 PCMCIA Agent Fipio
35012326 00 July 2006
71
Appendices
7
8
5
6
Step
4
9
Action
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.
Enter a comment if necessary.
In the Family field, select the type of device to be connected to the bus. (e.g.: TBX,
Momentum, etc.).
Select the base module.
Select, according to the type of device: z the base module and/or extension module, z the communicator.
Note: z If the reference for the Momentum base module is not already proposed, select reference OTHER FRD .
Click Ok to confirm.
Result: the module is declared.
FIPIO Configuration
TSX 57453 V5.0
Bus length: 0
1
Logical address Communicator Base module
15 km Devices configured: 1
Extension module
0 Fioio manager TSX 57453
1 TBX LEP 030 0 TBX ASS 200 1 TBX AES 400
63 Privileged terminal
72 35012326 00 July 2006
Appendices
Confirming the configuration of a module.
Introduction
Illustration
When a module is declared, and when the configuration or adjustment parameters are modified, this module's configuration must be confirmed.
The table below shows where the confirmation of a module's configuration is positioned within the various hardware installation phases of an application.
Step
1
2
3
4
5
6
Description
Declaration of a module:
Configuration of module channels.
Adjustment
Confirmation of the configuration of the module.
Declaration and/or parametering of new modules
Global confirmation of the application
Procedure The table below shows the procedure for confirming the configuration of a module.
Step
1
Action
Select Edit → Confirm or use the icon located in the toolbar.
35012326 00 July 2006
73
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
Procedure
The table below shows where the global reconfiguration of an application is positioned within the various hardware installation phases of an application.
Step
1
2
3
4
5
6
Description
Declaration of a module:
Configuration of module channels
Adjustment
Confirmation of the configuration of the module
Declaration and/or parametering of new modules
Global confirmation of the application
The table below shows the procedure for globally reconfiguring a module.
Step
1
Action
2
Select Edit → Confirm ...
or use the icon located in the toolbar.
Confirm the reconfiguration:
74 35012326 00 July 2006
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.
35012326 00 July 2006
75
Appendices
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 default of input/output %S10=0 ?
Yes
Locate the default on the FIPIO bus via
%S119
No
%S119 = 0 ?
Yes
Locate the rack at default
%S40 to %S47
No
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. 77
Locate the default on the FIPIO bus via
%S118 (1)
76 35012326 00 July 2006
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.
35012326 00 July 2006
77
Appendices
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)
%S10=0 ?
Yes
Locate the default on the FIPIO bus via
%S118
No No default of input/output
Locate the default connection
point via
%I\p2c\m.MOD.ERR = 1
%S118 = 0 ?
Yes
No Test the default on the X bus via
%S119
Locate the %SW128 to
%SW143 word which is different to 0
Locate the default connection point via the
%SWi:x word bit which is different to 0
The location of the default connection point may be carried out in two distinct ways.
The recommended method is location via the system words
%SW128 to %SW143.
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
78 35012326 00 July 2006
Discrete specific application
II
Presentation
Subject of this part
What's in this
Part?
This part presents the Discrete application-specific function on the TSX/PCX57 PLC and describes its installation using PL7 Junior and Pro software.
This part contains the following chapters:
Chapter
5
8
9
6
7
Chapter Name
General presentation of the discrete application -specific function
Configuration of the discrete specific application
Debugging discrete modules
Bits and words associated with discrete specific applications
Installation of the discrete reflex module
Page
79
35012326 00 July 2006
Discrete specific application
80 35012326 00 July 2006
General presentation of the discrete application -specific function
5
Introduction to the Discrete Application
Introduction The discrete application-specific function applies: z to rack-mounted discrete I/O modules, z 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: z either in local mode, z or in connected mode; in this case the modification is limited to certain parameters.
81
35012326 00 July 2006
General presentation
Implementation
Mode
Local
Local or connected
Connected
Local or connected
The table below shows the different installation phases of the discrete applicationspecific function.
Phase
Declaration of a module in-rack module (See How to declare a module in a PLC
) or remoted on the FIPIO bus
(See How to declare a remote module on the FIPIO
)
Configuration of module channels (See Configuration of discrete parameters,
Adjustment (See Adjusting the configuration parameters of a reflex
)
Confirmation of configuration parameters
(See Confirming the configuration of a module.,
Global confirmation of the application (See Globally reconfiguring an
)
Symbolization
Programming
Transfer
Debugging
Documentation
Description
Choice: z of geographical position z z z number and slot for an in-rack module, connection point for a remote module, of module type.
Input of the configuration parameters.
Entry of initial adjustment parameters (only on TSX DMY 28 FRK).
Confirmation of module level.
Confirmation of application level.
Symbolization of variables associated with the application-specific function.
Programming of functions to be performed by the application using: z bit and word objects associated with the module, z specific application instructions.
Transfer of the application to the PLC.
Debugging the application with the help of: z z debugging help screens enabling the user to control I/Os, diagnostic screens allowing identification of errors.
Printing the different information relating to the application.
82 35012326 00 July 2006
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).
35012326 00 July 2006
83
General presentation
84 35012326 00 July 2006
Configuration of the discrete specific application
6
Presentation
Subject of this chapter
What's in this
Chapter?
This chapter describes the Configuration aspect of the installation of the discrete specific application.
This chapter contains the following sections:
Section
6.1
6.2
6.3
6.4
Topic
Configuring a discrete module: General
Discrete input channel parameters
Discrete output channel parameters
Configuration of discrete parameters
Page
85
35012326 00 July 2006
Configuration of the discrete specific application
86 35012326 00 July 2006
6.1
Configuration of the discrete specific application
Configuring a discrete module: General
Presentation
Purpose of this section
What's in this
Section?
This section describes the basic operations required for configuring a Discrete module.
This section contains the following topics:
Topic
Description of the configuration screen for a discrete module
Accessing the configuration screen for an in -rack discrete module.
Accessing the configuration screen for a discrete module remoted on the
FIPIO bus
Modifying the configuration parameters of a discrete module's: General
Page
35012326 00 July 2006
87
Configuration of the discrete specific application
Description of the configuration screen for a discrete module
Presentation
Illustration
The module's configuration screen, selected in the rack or on the FIPIO bus, displays the parameters associated with the Discrete.
This screen gives access to parameter viewing and modification in local mode, and debugging in online mode.
1
2
TSX DMY 28FK [RACK 0 POSITION 2]
Configuration
Designation : 16I 24VDC, 12O 24 VDC
Inputs
3
6
7
8
9
10
11
12
13
14
15
Chan.
Symbol
0
1
4
5
2
3
Supply Monit.
Active
Task
MAST
MAST 4 ms
4 ms
4 ms
4 ms
4 ms
4 ms
4 ms
4 ms
4 ms
4 ms
Filter
4 ms
4 ms
4 ms
4 ms
4 ms
4 ms
Function
88 35012326 00 July 2006
Configuration of the discrete specific application
Description The table below shows the different elements in the configuration screen, along with their functions.
Number Element
1
2
3
Title bar
Function
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.
Module zone Enables the user t select: z the installation phase: z
Configuration , z z z
Adjustment (only for TSX DMY 28 RFK),
Installation (diagnostics), only accessible in online mode.
the type of channels (inputs or outputs), if the designated module has both inputs and outputs, z 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 .
Channel zone Enables the different channels to be parametered. The Symbol column displays the symbol associated with the channel when this has been defined by the user (via the variables editor).
35012326 00 July 2006
89
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
1
2
Action
Access the module's hardware configuration screen.
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
Designation : 16I 24VDC, 12O 24 VDC
Inputs
6
7
8
9
10
11
12
13
14
15
Chan.
Symbol
0
1
4
5
2
3
Supply Monit.
Active
Task
MAST
MAST 4 ms
4 ms
4 ms
4 ms
4 ms
4 ms
4 ms
4 ms
4 ms
4 ms
Filter
4 ms
4 ms
4 ms
4 ms
4 ms
4 ms
Function
90 35012326 00 July 2006
35012326 00 July 2006
Configuration of the discrete specific application
Certain modules have a dialogue box giving access to additional parameters.
To access this dialogue box:
Step
1
Action
Perform one of the following: z 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 z menu, or double-left-click on the row in the table corresponding to the channel to be parametered, or select the Function cell of the channel to be parametered and then confirm z using Enter .
Result: The dialogue box appears, superimposed on the configuration screen.
TSX DMY 28FK [RACK 0 POSITION 2]
Configuration
Designation : 16I 24VDC, 12O 24 VDC
Inputs
Chan Symbol
0
1
4
5
2
3
6
7
9
10
12
13
14
15
Supply Task
Active MAST
MAST
4 ms
4 ms
4 ms
4 ms
4 ms
4 ms
4 ms
4 ms
Filter
4 ms
4 ms
4 ms
4 ms
Function
Properties of channel
Function x
Normal
Latch state 0
Latch state 1
Event procesing
Rising
Falling
EV 1
91
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.
2
3
Step
1
Action
Access the module's hardware configuration screen.
Double-click on the processor's FIPIO zone.
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
6
7
8
9
10
11
12
13
14
15
Chan.
Symbol
0
1
4
5
2
3
Task
MAST
Reactivate
Automatic
Automatic
92 35012326 00 July 2006
Configuration of the discrete specific application
Modifying the configuration parameters of a discrete module's: General
Introduction
Accessing the contextual menus
The configuration editor provides a set of functions which enable the user to input or modify the parameters of modules such as: z z z contextual menus, single or multiple selection of channels, cutting/pasting of parameters (using the contextual menus).
These can be accessed by right-clicking with the mouse, and give quick access to the main commands.
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 channel or cell
The table below shows the procedure for selecting a module channel cell or channel.
Step
1
Action
Left-click on the required cell or channel number.
Selecting a group of consecutive channels
Selecting a group of nonconsecutive channels
The table below shows the procedure for selecting a group of consecutive channels of a module.
Step
1
2
Action
Select the first channel.
Press Shift and click on the last channel.
The table below shows the procedure for selecting a group of non-consecutive channels of a module.
Step
1
2
Action
Select the first channel.
Press Ctrl and click on each of the channels in turn.
35012326 00 July 2006
93
Configuration of the discrete specific application
Selecting a group of consecutive cells
The table below shows the procedure for selecting a group of consecutive cells of a module.
Step
1
2
Action
Select the first cell.
Move the mouse up or down whilst holding down the mouse button, then release the button when the last cell has been reached.
94 35012326 00 July 2006
6.2
Configuration of the discrete specific application
Discrete input channel parameters
Presentation
Subject of this section
What's in this
Section?
This section presents the different input channel parameters by type of Discrete module.
This section contains the following topics:
Topic
In-rack discrete input parameters
Parameters of TBX discrete inputs remoted on the FIPIO bus
Parameters of Momentum discrete inputs remoted on the FIPIO bus
Parameters of IP67 discrete inputs remoted on the FIPIO bus
Page
35012326 00 July 2006
95
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
Reference
TSX DEY 08D2
TSX DEY 16A2
TSX DEY 16A3
TSX DEY 16A4
TSX DEY 16A5
TSX DEY 16D2
16
16
16
16
Number of inputs
8
16
Associated task
(8 channel group)
Mast / Fast
Mast / Fast / None
Mast / Fast / None
Mast / Fast / None
Mast / Fast / None
Mast / Fast / None
TSX DEY 16D3 16
TSX DEY 32D2K 32
TSX DEY 32D3K 32
TSX DEY 64D2K 64
Mast / Fast / None
Mast / Fast / None
Mast / Fast / None
Mast / Fast / None
TSX DMY 16FK
TSX DMY 28FK
16 Mast / Fast / None
16 (input part) Mast / Fast / None
TSX PAY 262
TSX PAY 262
8 (input part)
8 (input part)
Mast / Fast / None
TSX DMY 28RFK 16 (input part) Mast / Fast / None -
-
-
-
-
-
-
Function
(per channel).
-
-
-
-
-
-
Filtering
(per channel).
-
-
-
-
-
-
-
-
-
Normal or (1) 4 ms or (2)
Normal or (1) 4 ms or (2)
-
Supply fault monit.
(16 channel group)
Active / Inactive
Active / Inactive
Active / Inactive
Active / Inactive
Active / Inactive
Active / Inactive
Active / Inactive
Active / Inactive
Active / Inactive
Active / Inactive
-
Active / Inactive
Active / Inactive
4 ms or (2) Active / Inactive
Key:
(1)
(2)
Memorization of status 0 or 1, event processing on rising edge (RE), on falling edge (FE) or both together.
0.1 to 7.5 ms
Note: z
Parameters in bold correspond to the parameters configured by default.
z
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).
96 35012326 00 July 2006
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
Reference
TBX CEP 1622
TBX DES 1622
Number of inputs
16
16
TBX DES 1633
TBX EEP 1622
TBX DMS 1025
16
16
8 (input part)
TBX DMS 1625
TBX DES 16S04
8 (input part)
16
TBX DMS 16S44 (1)
TBX DMS 16P22 8 (input part)
TBX DES 16C22 16
TBX EEP 08C22 16
TBX DMS 16C22 8
TBX DMS 16C222 8
TBX DES 16F22 16
Associated task
(for the module)
Mast / Fast
Mast / Fast
Mast / Fast
Mast / Fast
Mast / Fast
Mast / Fast
Mast / Fast
Mast / Fast
Mast / Fast
Mast / Fast
Mast / Fast
Mast / Fast
Mast / Fast
Mast / Fast
-
-
-
-
-
-
-
-
Filtering
(per channel)
-
-
-
-
-
Normal / Fast
-
-
-
-
-
-
-
-
Latching (per channel)
-
-
-
-
-
-
-
Wiring Check
(per channel)
Active / Inactive
-
-
-
Active / Inactive
Active / Inactive
Active / Inactive
-
-
Active / Inactive -
Active / Inactive
Active / Inactive
Key:
(1) 8 input channels + 8 programmable input or output channels.
Note: Parameters in bold correspond to the parameters configured by default.
35012326 00 July 2006
97
Configuration of the discrete specific application
Parameters of Momentum discrete inputs remoted on the FIPIO bus
Presentation
Parameters
The Discrete Momentum input modules on the FIPIO bus have parameters for all channels.
The table below shows the parameters available for each Momentum discrete input module.
Module Reference Number of inputs
170 ADI 340 00
170 ADI 350 00
170 ADI 540 50
170 ADI 740 50
170 ADM 350 10
170 ADM 350 11
170 ADM 350 15
170 ADM 370 10
170 ADM 390 10
170 ADM 390 30
170 ADM 690 50
170 ADM 690 51
170 ADM 850 10
170 ARM 370 30
16
32
16
16
16 (input part)
16 (input part)
16 (input part)
16 (input part)
16 (input part)
10 (input part)
10 (input part)
10 (input part)
16 (input part)
10 (input part)
Associated task (for the module)
Mast / Fast
Mast / Fast
Mast / Fast
Mast / Fast
Mast / Fast
Mast / Fast
Mast / Fast
Mast / Fast
Mast / Fast
Mast / Fast
Mast / Fast
Mast / Fast
Mast / Fast
Mast / Fast
Note: Parameters in bold correspond to the parameters configured by default.
98 35012326 00 July 2006
Configuration of the discrete specific application
Parameters of IP67 discrete inputs remoted on the FIPIO bus
Presentation
Parameters
The Discrete IP67 input modules on the FIPIO bus have parameters for all channels.
The table below shows the parameters available for each IP67 discrete input module.
Module Reference Number of inputs
TSX EEF 08D2
TSX EEF 16D2
TSX EMF 16DT2
8
16
8 (input part)
Associated task (for the module)
Mast / Fast
Mast / Fast
Mast / Fast
Note: Parameters in bold correspond to the parameters configured by default.
35012326 00 July 2006
99
Configuration of the discrete specific application
6.3
Discrete output channel parameters
Presentation
Subject of this section
What's in this
Section?
This section presents the different output channel parameters by type of Discrete module.
This section contains the following topics:
Topic
Discrete output parameters for in-rack 8-channel modules.
Discrete output parameters for in-rack modules with over 8 channels
Parameters of 8, 10 or 12 channel TBX discrete outputs remoted on the FIPIO bus
Parameters of 16 channel TBX discrete outputs remoted on the FIPIO bus
Momentum Parameters of Momentum discrete outputs remoted on the FIPIO bus
Parameters of IP67 discrete outputs remoted on the FIPIO bus
Page
100 35012326 00 July 2006
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
TSX DSY 08R5A
TSX DSY 08S5
TSX DSY 08T2
TSX DSY 08T22
TSX DSY 08T31
TSX DSY 08R5
The table below shows the parameters available for each in-rack 8-channel discrete output module.
Group of 8 channels
Module Reference Associated task
TSX DSY 08R4D Mast / Fast
Mast / Fast
Mast / Fast
Mast / Fast
Mast / Fast
Mast / Fast
Mast / Fast
Reactivation
Programmed / Automatic
Programmed / Automatic
Programmed / Automatic
Programmed / Automatic
Programmed / Automatic
Programmed / Automatic
Programmed / Automatic
Fallback mode
Fallback /
Maintain
Fallback /
Maintain
Fallback /
Maintain
Fallback /
Maintain
Fallback /
Maintain
Fallback /
Maintain
Fallback /
Maintain
-
-
-
-
Supply fault monit.
0
0
Active / Inactive 0 / 1
Active / Inactive 0 / 1
Active / Inactive 0 / 1
0
/ 1
/ 1
/ 1
Channel by channel.
Fallback value
0 / 1
Note: Parameters in bold correspond to the parameters configured by default.
35012326 00 July 2006
101
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.
102 35012326 00 July 2006
Configuration of the discrete specific application
Parameters
Module
Reference
TSX DSY 16S5
TSX DSY 16T2
TSX DSY 16T3
TSX DSY 32T2K
TSX DSY 64T2K
TSX DSY 16R5
TSX DSY 16S4
Number of outputs
16
16
16
32
64
16
16
Associated task
Mast / Fast /
None
Mast / Fast /
None
Mast / Fast /
None
Mast / Fast /
None
Mast / Fast /
None
Mast / Fast /
None
Mast / Fast /
None
TSX DMY 28 FK 12 (output part) Mast / Fast /
None
TSX DMY 28RFK 12 (output part) Mast / Fast /
None
TSX PAY 262
TSX PAY 262
The table below shows the parameters available for each in-rack discrete output module with more than 8 channels.
Group of 8 channels
2 (output part)
4 (output part)
Mast / Fast /
None
-
-
Reactivation
Programmed /
Automatic
Programmed /
Automatic
Programmed /
Automatic
Programmed /
Automatic
-
Programmed /
Automatic
Programmed /
Automatic (1)
Programmed /
Automatic (1)
Fallback mode
Fallback /
Maintain
Fallback /
Maintain
Fallback /
Maintain
Fallback /
Maintain
Fallback /
Maintain
Fallback /
Maintain
Fallback /
Maintain
Fallback /
Maintain
Fallback /
Maintain
-
-
-
Supply fault monit.
Channel by channel.
Fallback value
0 / 1
Active /
Inactive
Active /
Inactive
-
Active /
Inactive
Active /
Inactive
Active /
Inactive
0 / 1
0 / 1
0 / 1
0 / 1
0 / 1
0 / 1
-
0 / 1 /
Continuous
(2)
Key:
(1)
(2)
Reactivation is chosen globally for the 12 output channels.
Only for TSX DMY 28 RFK.
Note: z z
Parameters in bold correspond to the parameters configured by default.
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).
35012326 00 July 2006
103
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
Module
Reference
TBX ESP 08C22
TBX DSS 1235
TBX DMS 1025
12
The table below shows the parameters available for each 8, 10 or 12 channel TBX discrete output module remoted on the FIPIO bus.
Number of outputs
8
Module
Associated task
Mast / Fast
Mast / Fast
2 (output part) Mast / Fast
-
Group of 8 channels
Reactivation Fallback mode
Programmed
/ Automatic
Fallback /
Maintain
Programmed
/ Automatic
Fallback /
Maintain
Fallback /
Maintain
Channel by channel
Fallback value
0 / 1
Wiring
Check
Yes / No
0 / 1
0 / 1 -
-
Note: Parameters in bold correspond to the parameters configured by default.
104 35012326 00 July 2006
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
Module
Reference
TBX CSP 1625
TBX DSS 1622
TBX ESP 1622
TBX DSS 16C22
TBX CSP 1622
TBX DSS 1625
TBX DMS 1625
The table below shows the parameters available for each 16 channel TBX discrete output module remoted on the FIPIO bus.
Number of outputs
16
16
16
16
TBX DMS 16C22 16
TBX DMS 16C222 16
16
16
8 (output part)
TBX DMS 16S44 8 (output part)
TBX DMS 16P22 (1)
Module
Associated task
Mast / Fast
Mast / Fast
Mast / Fast
Mast / Fast
Mast / Fast
Mast / Fast
Mast / Fast
Mast / Fast
Mast / Fast
Mast / Fast
Mast / Fast
-
-
-
Group of 8 channels
Reactivation Fallback mode
-
Programmed
/ Automatic
Programmed
/ Automatic
Programmed
/ Automatic
Programmed
/ Automatic
Programmed
/ Automatic
Fallback
Maintain
/
Fallback /
Maintain
Fallback /
Maintain
Fallback
Maintain
Fallback
Maintain
/
/
-
Programmed
/ Automatic
-
Programmed
/ Automatic
Fallback /
Maintain
Fallback /
Maintain
Fallback /
Maintain
Fallback /
Maintain
-
Channel by channel
Fallback value
Wiring
Check
-
0 / 1 -
-
0 / 1
0 / 1
0 / 1
0 / 1
0 / 1
0 / 1
0 / 1
0 / 1 -
-
-
-
-
-
Yes / No
Yes / No
Yes / No
Key:
(1) 8 programmable output channels.
Note: Parameters in bold correspond to the parameters configured by default.
35012326 00 July 2006
105
Configuration of the discrete specific application
Momentum Parameters of Momentum discrete outputs remoted on the FIPIO bus
Presentation
Parameters
The discrete Momentum output modules on the FIPIO bus have parameters for all channels.
The table below shows the parameters available for each Momentum discrete output module.
Module Reference Number of inputs
170 ADO 340 00
170 ADO 350 00
170 ADO 530 50
170 ADO 540 50
170 ADO 730 50
170 ADO 740 50
170 ADO 830 30
170 ADM 350 10
170 ADM 350 11
170 ADM 350 15
170 ADM 370 10
170 ADM 390 10
170 ADM 390 30
170 ADM 690 50
170 ADM 690 51
170 ADM 850 10
170 ARM 370 30
16
32
8
16
8
16
6
16 (output part)
16 (output part)
16 (output part)
8 (output part)
12 (output part)
8 (output part)
8 (output part)
8 (output part)
16 (output part)
8 (output part)
Associated task (for the module)
Mast / Fast
Mast / Fast
Mast / Fast
Mast / Fast
Mast / Fast
Mast / Fast
Mast / Fast
Mast / Fast
Mast / Fast
Mast / Fast
Mast / Fast
Mast / Fast
Mast / Fast
Mast / Fast
Mast / Fast
Mast / Fast
Mast / Fast
Note: Parameters in bold correspond to the parameters configured by default.
106 35012326 00 July 2006
Configuration of the discrete specific application
Parameters of IP67 discrete outputs remoted on the FIPIO bus
Presentation
Parameters
The Discrete IP67 output modules on the FIPIO bus have parameters for all channels.
The table below shows the parameters available for each Momentum discrete output module.
Module Reference Number of inputs
TSX EMF 16DT2
TSX ESF 08T22
8 (output part)
8
Associated task (for the module)
Mast / Fast
Mast / Fast
Note: Parameters in bold correspond to the parameters configured by default.
35012326 00 July 2006
107
Configuration of the discrete specific application
6.4
Configuration of discrete parameters
Presentation
Subject of this section
What's in this
Section?
This section presents the installation of different discrete I/O channel configuration parameters.
This section contains the following topics:
Topic
Configuring the programmable channels of the TBX DMS 16P22 module
Modifying the Task parameter of a discrete module
Modifying the Wiring check parameter of a TBX discrete module
Modifying the Monitoring of external supply fault parameter for a discrete module.
Modifying the Functions parameter of a discrete input module
Modifying the Filtering parameter of a discrete input module.
How to modify the Latching parameter of a discrete input module
Parametering the Run/Stop input of a discrete module
Modifying the Fallback mode parameter of a discrete output module
Modifying the Reactivation of outputs parameter of a discrete module.
Page
108 35012326 00 July 2006
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
Designation : TBX7 SOCK 8E+8I/O 0,5 A Version : 1.0
Program
Chan.
Symbol
8
9
10
11
12
13
14
15
Task
MAST Input
Type
Input
Input
Output
Output
Input
Input
Output
Reactivate Fall. Mode Fall. Value
Automatic
Automatic
Automatic
Automatic
Automatic
Automatic
Automatic
Automatic
Fallback
Fallback
Fallback
Fallback
Fallback
Fallback
Fallback
Fallback
0
0
0
Procedure The table below gives the procedure for configuring the programmable channels of the TBX DMS 16P22 module.
Step
1
2
3
Action
Access the module's hardware configuration screen.
Select Program part from the pull-down menu in the module zone.
Parameter the channels one by one as inputs or outputs using the pull-down list in the Type column.
35012326 00 July 2006
109
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: z for 8 consecutive channels for Discrete in-rack modules, z for all channels for discrete modules remoted on the FIPIO bus.
The possible choices are as follows: z z
The MAST task (for discrete in-rack modules or modules on the FIPIO bus).
The FAST task (for discrete in-rack modules or modules on the FIPIO bus).
z
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
1
2
Action
Access the hardware configuration screen of the required module.
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
NONE
3
4
Note: For discrete in-rack modules with more than 16 channels, use the scrollbar to access the different groups of channels.
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.
Confirm the deconfiguration or reconfiguration if necessary.
110 35012326 00 July 2006
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: z z sensors and inputs, 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
1
2
3
Action
Access the hardware configuration screen of the required module.
Click on the checkbox in the Wiring Check column of the channel to be parametered.
Repeat the operation for every channel to be configured (from step 2).
35012326 00 July 2006
111
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
1
2
Action
Access the hardware configuration screen of the required module.
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.
112 35012326 00 July 2006
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: z normal (no event associated with the channel), z z channel by channel memorization of status (status at 0 or status at 1), channel by channel event processing, z z event triggered on a rising edge (RE), event triggered on a falling edge (FE), z event triggered on a rising edge and falling edge,
Event inputs have an associated processing number (Evti) . These numbers range from: z
0 to 31 for TSX5710/102/103/153, PMX 57 102, PCX 571012 processors, z
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: z
The event number proposed is the first available number in the list.
z z
A manually input number outside the tolerance range will not be accepted on confirmation.
Event numbers cannot be added, deleted or changed when in online mode.
35012326 00 July 2006
113
Configuration of the discrete specific application
Procedure The table below shows the procedure for defining the parameters associated with event inputs.
Step
1
2
3
Action
Access the hardware configuration screen of the required module.
Select the required channel.
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
Function x
Normal
Latch state 0
Latch state 1
Event processing
Rising
Falling
EVT 1
4
5
6
Select the required function.
Enter the Evt event number.
Repeat the operation for every channel to be configured (from step 2).
114 35012326 00 July 2006
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: z z
0.1 to 7.5 ms in increments of 0.5 ms for in-rack input modules,
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
1
2
Action
Access the hardware configuration screen of the required module.
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
4 ms
0.1 ms
0.5 ms
1 ms
1.5 ms
2 ms
2.5 ms
Filter
Fast
Normal
Fast
3 Select the required filtering time.
35012326 00 July 2006
115
Configuration of the discrete specific application
How to modify the Latching parameter of a discrete input module
Presentation
Procedure
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).
The table below shows the procedure for activating or deactivating the Latching function.
Step
1
2
3
Action
Access the hardware configuration screen of the required module.
Click on the checkbox in the Latching column of the channel to be parametered.
Repeat the operation for every channel to be configured (from step 2).
Note: This parameter can be modified in online mode.
116 35012326 00 July 2006
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
1
2
3
Action
Access the CPU configuration screen.
Check the Run/Stop Input box.
Enter the input to be assigned in the data entry window.
35012326 00 July 2006
117
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
Fallback
Meaning
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 .
Continuous This mode only concerns TSX DMY 28 RFK modules.
Reflex outputs are updated by the module; when this mode is selected, the reflex function remains active.
Procedure
Note: This parameter may be modified in online mode for discrete in-rack modules.
The table below shows the procedure for defining the fallback mode assigned to a group of channels.
Step
1
2
Action
Access the hardware configuration screen of the required module.
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
3
4
5
Note: For discrete in-rack modules with more than 16 channels, use the scrollbar to access the different groups of channels.
Select the required fallback mode.
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.
Click on the required value (0 or 1).
118 35012326 00 July 2006
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
1
2
Action
Access the hardware configuration screen of the required module.
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
Programme dd
Programmed
Automatic
3
Note: For discrete in-rack modules with more than 16 channels, use the scrollbar to access the different groups of channels.
Select the required task.
35012326 00 July 2006
119
Configuration of the discrete specific application
120 35012326 00 July 2006
Debugging discrete modules
7
At a Glance
Subject of this chapter
What's in this
Chapter?
This chapter describes the Debug aspect of the installation of the discrete application.
This chapter contains the following topics:
Topic
Presentation of the debug function of a discrete module.
Description of the debug screen of a discrete module
Accessing the debug screen for an in-rack discrete module.
Accessing the diagnostics function of a discrete module
Accessing the channel diagnostics function of a discrete module
Accessing the forcing/unforcing function
How to access the SET and RESET commands
Accessing the masking/unmasking function for an event
Accessing the reactivation of outputs command
Maintain outputs of a discrete module
Page
35012326 00 July 2006
121
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
PL7 of version prior to V3.3
(PL7 + CPU + Application PL7) of version V3.3 or higher
Access to the debug function...
not available.
limited to four screens open simultaneously.
122 35012326 00 July 2006
Debugging discrete modules
Description of the debug screen of a discrete module
Presentation
Illustration
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.).
The debug screen is displayed as follows:
1
2
TSX DSY 08R5 [RACK 0 POSITION 3]
Debug
Designation : 8O RELAY 50VA, BORN Version : 1.0
Global unforcing RUN ERR IO
4
3
Chan. Symbol
0
1
5
4
2
3
6
7
0
0
0
0
0
0
0
State
0
Fault
DIAG..
DIAG..
DIAG..
DIAG..
DIAG..
DIAG..
DIAG..
Reactivate Applied Q
Reactivate STOP
DIAG...
Channel control
Forcing
F4 Force to 0
F5
Force to 1
Unforce F6
Write
F7 Set
F8 Reset x
35012326 00 July 2006
123
Debugging discrete modules
Description The table below shows the different elements in the debug screen, along with their functions.
Number Element
1
2
Title bar
Function
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.
Module zone Enables the user to select: z the debug phase: z
Configuration , z z
Installation (diagnostics), only accessible in online mode.
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: z the module diagnostics when the module is faulty (shown by the indicator in the diagnostics access button, which turns red) z the channel Global unforcing function.
Note: Display of this zone is optional. The choice is made using the command View →
Module zone .
3
4
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: z the channel-by-channel diagnostics when the channels are faulty (shown by the indicator in the diagnostics access button, which turns red) z 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.
Command zone
Provides access to the commands for a channel
124 35012326 00 July 2006
Accessing the debug screen for an in-rack discrete module.
Debugging discrete modules
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
1
2
Action
Access the hardware configuration screen.
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 : 1.0
Global unforcing RUN ERR IO DIAG...
Chan. Symbol
0
1
4
5
2
3
6
7
0
0
0
0
0
0
0
State
0
Fault
DIAG..
DIAG..
DIAG..
DIAG..
DIAG..
DIAG..
DIAG..
DIAG..
Reactivate Applied Q
Reactivate STOP
Channel control
Forcing
F4 Force to 0
F5
F6
Write
F7
Force to 1
Unforce
Set
F8 Reset x
35012326 00 July 2006
125
Debugging discrete modules
Accessing the diagnostics function of a discrete module
Presentation
Procedure
The module diagnostics function displays the current faults, if there are any, classified according to their category: z z internal faults (module failures, self-test running) external faults (terminal block fault), z 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: z in the configuration editor at rack level: z z the module position indicator.
in the configuration editor at module level: z z the Err and I/O indicators, depending on the type of fault, the Diag indicator.
The table below shows the procedure for accessing the module diagnostics screen.
Step
1
2
Action
Access the module's debug screen.
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 .
126 35012326 00 July 2006
Debugging discrete modules
Accessing the channel diagnostics function of a discrete module
Presentation
Procedure
The channel diagnostics function displays the current faults, if there are any, classified according to their category: z z internal faults (channel failure) external faults (link or sensor supply fault), z 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.
The table below shows the procedure for accessing the channel diagnostics screen.
Step
1
2
Action
Access the module's debug screen.
Click on the Diag button in the Err column.
Result: The list of channel faults appears.
Channel diagnostics
Internal faults External faults
External supply
Other faults
OK
Note: The channel diagnostics information can also be accessed via the program using the READ_STS instruction.
35012326 00 July 2006
127
Debugging discrete modules
Accessing the forcing/unforcing function
Presentation
Procedure
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: z for one or more channels: z forcing to 1, z z z forcing to 0, unforcing (when the selected channel(s) is (are) forced), for all channels of a module (when at least one channel is forced): z global unforcing of channels.
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. 93
for multiple selection.
Step
1
2
3
Action for one channel
Access the module's debug screen.
In the Status column, double-click on the cell of the required channel (1).
Select the required function.
Action for all channels
-
Click on the Global unforcing button in the module zone.
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.
128 35012326 00 July 2006
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. 93 )
for multiple selection.
Step
1
2
3
Action for one channel
Access the module's debug screen.
In the Status column, double click on the cell of the required channel (1).
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.
35012326 00 July 2006
129
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: z
Mask (masks the events), z
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
1
2
3
Action for one or more channels (1)
Access the module's debug screen.
In the Status column, double-click on the cell of the required channel (3).
Select the required function.
Action for all of the configured channels of the application modules (2)
Access the CPU debug screen.
-
Click on the Activation/Deactivation button located in the Events field.
Key:
(1)
(2)
(3)
For multiple selection, see Modifying the configuration parameters of a discrete
Global masking/unmasking can also be carried out using: z the instruction PL7 MASKEVT(), z z the instruction PL7 UNMASKEVT(), the %S38 system bit.
The Channel commands screen can also be accessed by double-clicking on the required channel and then left-clicking on the Command button.
130 35012326 00 July 2006
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
1
2
Action
Access the module's debug screen.
Click on the Reactivate button in the Reactivation column for the required group of channels.
35012326 00 July 2006
131
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: z processor fault, z z rack fault, inter-rack link fault.
132 35012326 00 July 2006
Bits and words associated with discrete specific applications
8
Presentation
Subject of this chapter
What's in this
Chapter?
This chapter presents the different word and bit objects associated with discrete specific applications as well as their addressing mode.
This chapter contains the following sections:
Section
8.1
8.2
Topic
Addressing of discrete I/O module objects
Language objects associated with the discrete specific application
Page
133
35012326 00 July 2006
Language words and bits
134 35012326 00 July 2006
8.1
Language words and bits
Addressing of discrete I/O module objects
Presentation
Subject of this section
What's in this
Section?
This section presents the specific features of addressing linked to the discrete specific application.
This section contains the following topics:
Topic
Addressing of language objects associated with discrete in-rack I/O modules
Addressing of language objects associated with discrete I/O modules remoted on the FIPIO bus
Indexable discrete I/O objects.
Page
35012326 00 July 2006
135
Language words and bits
Addressing of language objects associated with discrete in-rack I/O modules
Presentation
Illustration
Addressing of bit and word objects is defined in Shared specific applications (See
Addressing input/output module objects in rack, p. 32 ).
This page describes the specific features linked to the discrete in-rack I/O modules.
Addressing principle:
% I, Q, M, K X, W, D, F
Symbol Object type Format
X
Rack
Y
Position i r
Channel no. Rank
Specific values The table below shows the values specific to the discrete in-rack I/O module objects.
i
Element Values x 0 to 1
0 to 7 y 00 to 14
(1)
0 to 63 or
MOD
Comment
TSX 5710/102/103/153, PMX 57102, PCX 571012.
Other processors
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).
MOD: channel reserved for management of the module and the parameters shared by all channels.
r 0 to 3 or
ERR
ERR: indicates a module or channel fault.
(1) : The number of slots requires the use of 2 racks at the same address.
136 35012326 00 July 2006
Language words and bits
Addressing of language objects associated with discrete I/O modules remoted on the FIPIO bus
Presentation
Illustration
Addressing of bit and word objects is defined in (See Addressing of language
objects for modules remoted on the FIPIO bus, p. 35
).
This page describes the specific features linked to the discrete I/O modules remoted on the FIPIO bus.
Addressing principle:
% I, Q, M, K X, W, D, F
Symbol Object type Format
\ p.2.c
\
Module/channel address and connection point m
Module number i
Channel number r
Rank
Specific values The table below shows the values specific to remote discrete I/O module objects.
r i
Element Values
0 to 31 or
MOD
0 to 255 or ERR
Comment
0 to 15 for TBX modules.
0 to 31 for Momentum modules.
MOD: channel reserved for management of the module and the parameters shared by all channels.
ERR: indicates a module or channel fault.
35012326 00 July 2006
137
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.
138 35012326 00 July 2006
8.2
Language words and bits
Language objects associated with the discrete specific application
Presentation
Subject of this section
What's in this
Section?
This section presents the different language objects associated with the discrete specific application.
This section contains the following topics:
Topic
Implicit exchange language objects associated with the discrete specific application
Exchange management: Exchanges in progress module
%[email protected]:Xj or channel %[email protected]:Xj
Exchange management: Module %[email protected]:Xj or channel
%[email protected]:Xj report
Explicit exchange objects: General
Explicit exchange object: %[email protected]:Xj channel status
Explicit exchange object: Status Module %[email protected]:Xj
Explicit exchange object: %[email protected]:Xj channel command
Page
35012326 00 July 2006
139
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
Address (1)
The table below shows the different implicit exchange bit objects.
Function
Input channel bit
Output channel bit
Channel error bit
Module error bit
Meaning when the bit is at status 1
Indicates, for input channel i, that the sensor output controlling the input is activated.
Indicates that output channel i is activated.
Indicates that input channel i is faulty.
Indicates that the module is faulty.
Key:
(1) @module = module address.
z xy for in-rack modules, z \p2c\m for remote modules.
Word objects
Address (1)
The table below shows the different implicit exchange word objects.
Function
Event status associated with channel i
Command word associated with channel i
Meaning for Xj = 1
Indicates that event processing is configured on a rising edge.
Indicates that event processing is configured on a falling edge.
Masks/unmasks the event associated with the channel.
Key:
(1) @module = module address.
z xy for in-rack modules, z \p2c\m for remote modules.
140 35012326 00 July 2006
Language words and bits
Exchange management: Exchanges in progress module
%[email protected]:Xj or channel %[email protected]:Xj
Presentation
Description
These word-type objects provide information on the module or channel i exchanges in progress.
They are updated automatically by the system.
The table below explains the meanings of the different bits in the word
.
Address (1) Meaning for Xj = 1
%[email protected]:X0 Exchange of status words in progress on at least one channel of the module.
%[email protected]:X1 Exchange of command words in progress on at least one channel of the module.
Key:
(1) @module = module address.
z xy for in-rack modules, z \p2c\m for remote modules.
Description The table below explains the meanings of the different bits in the word
.
Address (1)
Meaning for Xj = 1
Exchange of status words in progress on channel i.
Exchange of command words in progress on channel i.
Key:
(1) @module = module address.
z z xy for in-rack modules,
\p2c\m for remote modules.
35012326 00 July 2006
141
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
%[email protected]:X0 bit never changes to 1.
142 35012326 00 July 2006
Language words and bits
Exchange management: Module %[email protected]:Xj or channel
%[email protected]:Xj report
Presentation
Description
These word-type objects provide information on the exchange reports for the module or channel i.
They are updated automatically by the system.
The table below explains the meanings of the different bits in the word
.
Address (1)
Meaning for Xj = 1
Status parameter exchange error on at least one channel of the module.
Command parameter exchange error on at least one channel of the module.
Key:
(1) @module = module address.
z z xy for in-rack modules,
\p2c\m for remote modules.
Description The table below explains the meanings of the different bits in the word
.
Address (1)
Meaning for Xj = 1
Status parameter exchange error on channel i.
Command parameter exchange error on channel i.
Key:
(1) @module = module address.
z xy for in-rack modules, z \p2c\m for remote modules.
35012326 00 July 2006
143
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;
144 35012326 00 July 2006
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: z READ_STS (read status words), z z z z z
WRITE_CMD (write command words),
WRITE_PARAM (write adjustment parameters),
READ_PARAM (read adjustment parameters),
SAVE_PARAM (save adjustment parameters),
RESTORE_PARAM (restore adjustment parameters).
35012326 00 July 2006
145
Language words and bits
Explicit exchange object: %[email protected]:Xj channel status
Presentation
Description
This word-type object provides information on the status of channel i.
It is updated on execution of the instruction READ_STS%[email protected]
.
The table below explains the meanings of the different bits in the word
.
Address (1)
%[email protected]:X1 (2)
Meaning for Xj = 1
External fault: Tripped.
External fault: Fuse.
Terminal block fault.
External supplyfault.
Internal fault: Module Out of Order
Software or hardware configuration fault.
Communication fault.
Reserved.
External fault: Short-circuit.
External fault: Line fault.
%[email protected]:X10 à X15 Reserved.
Key:
(1)
(2)
@module = module address.
z xy for in-rack modules, z \p2c\m for remote modules.
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).
146 35012326 00 July 2006
Language words and bits
Explicit exchange object: Status Module %[email protected]:Xj
Presentation This word-type object provides information on the status of the module.
It is updated on execution of command READ_STS%[email protected]
.
35012326 00 July 2006
147
Language words and bits
Description The table below explains the meanings of the different bits in the word
.
Address (1) Meaning for Xj = 1
%[email protected]:X0 Internal fault: Module Out of Order.
%[email protected]:X1 Functional Fault (2).
%[email protected]:X2 Terminal block fault.
Module type
Base
Base
Base
%[email protected]:X3 Functional Fault (2).
%[email protected]:X4 Self-testing
Base
Base
%[email protected]:X4 Reserved.
Base
%[email protected]:X5 Software or hardware configuration fault. Base
%[email protected]:X6 Module missing
%[email protected]:X7 Fault on FIPIO extension module.
%[email protected]:X8 Internal fault: Module Out of Order.
%[email protected]:X9 Functional Fault (2).
Base
Base
FIPIO extension
FIPIO extension
%[email protected]:X10 FIPIO Extension Terminal Block Fault.
%[email protected]:X11 Self-testing
FIPIO extension
FIPIO extension
%[email protected]:X12 Reserved.
FIPIO extension
%[email protected]:X13 Software or hardware configuration fault. FIPIO extension
%[email protected]:X14 Module missing
%[email protected]:X15 Reserved.
FIPIO extension
FIPIO extension
Key:
(1)
(2)
@module = module address.
z xy for in-rack modules, z \p2c\m for remote modules.
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.
148 35012326 00 July 2006
Language words and bits
Explicit exchange object: %[email protected]: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%[email protected]
.
Note: This object is specific to output modules with reactivation.
Description The table below explains the meanings of the different bits in the word
.
Address (1)
Meaning for Xj = 1
Reactivation of tripped outputs (protected outputs).
Inhibition of external supply control.
Confirmation of external supply control.
%[email protected]:X3 to X15 Reserved.
Key:
(1) @module = module address.
z xy for in-rack modules, z \p2c\m for remote modules.
i = first channel in group of channels (0, 8, 16, ...).
35012326 00 July 2006
149
Language words and bits
150 35012326 00 July 2006
Installation of the discrete reflex module
9
Presentation
Subject of this chapter
What's in this
Chapter?
This chapter presents the specific installation features of discrete reflex module
TSX DMY 28 RFK.
This chapter contains the following sections:
Section
9.1
9.2
9.3
9.4
Topic
General presentation of discrete reflex module
Reflex function blocks
Configuration of discrete reflex module
Bits and words associated with discrete reflex module
Page
151
35012326 00 July 2006
Installation of the discrete reflex module
152 35012326 00 July 2006
9.1
Installation of the discrete reflex module
General presentation of discrete reflex module
Presentation of discrete reflex module
General
Operating principle
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: z z a faster response time than the Fast task or event task.
an output reaction with a simple logic of under 0.5 ms, z z z speed control for moving parts and movement stopping control when the speed becomes too slow,
feedback control between movements, time-outs with a time base of 0.1ms
z z continuous oscillation generation at a fixed frequency, but with a variable duty cycle,
...
The TSX DMY 28 RFK module operates independently from the PLC task . It has its 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: z z z the image bits of the module's physical input status (%I), the image bits of the module's physical and auxiliary output statuses (%I), the command bits of the module outputs (%Q).
35012326 00 July 2006
153
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)
PLC task
Acquisition
Processing
%Ixy.i (16 à 31)
%Ixy.i.1 (16 à 31)
Update
%Qxy.i
154 35012326 00 July 2006
Installation of the discrete reflex module
9.2
Reflex function blocks
Presentation
Subject of this section
What's in this
Section?
This section presents the different reflex functions available.
This section contains the following topics:
Topic
Function block: Direct
Reflex function block: Combinational
Reflex function block: Operation timer
Reflex function block: Idle timer
Reflex function block: Operation-idle timer
Reflex function block: 2 value operation timer
Reflex function block: Operation-idle time with value selection
Reflex function block: Retriggerable monostable
Reflex function block: Monostable with time delay
Reflex function block: 2 value monostable
Reflex function block: Oscillator
Reflex function block: D flip-flop
Reflex function block: T flip-flop
Reflex Function Block: 2 Threshold Counter
Reflex function block: Came électronique simple
Reflex function block: 1 threshold intervalometer
Reflex function block: Burst
Reflex function block: PWM (Pulse Width Modulation)
Reflex function block: Detection of underspeed
Reflex function block: Speed monitoring
Reflex function block: Type 1 command-check
Reflex function block: Type 2 command-check
Reflex function block: Command-counting
Reflex function block: Fault Signaling
Page
35012326 00 July 2006
155
Installation of the discrete reflex module
Function block: Direct
Role
Structure
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.
The table below shows the block's different interfaces.
Name x x Aux
Meaning
Block's physical output.
Block's internal auxiliary output.
Operation
Illustration
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.
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
156 35012326 00 July 2006
Installation of the discrete reflex module
Reflex function block: Combinational
Role
Structure
This function enables a logic function to be performed between the inputs and one or more of the module's outputs.
The table below shows the block's different interfaces.
Name x x Aux
Meaning
Block's physical output.
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
I
%I2.0.0
%I2.16.0 I
%I2.4.0
Combinational Output 16
Output 16 Aux
35012326 00 July 2006
157
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
I
%I2.0.0
%I2.16.0 I
%I2.4.0
Combinational Output 16
Output 16 Aux
%I2.16.1
I
%I2.10.0
%I2.8.0 I
Combinational Output 17
Output 17 Aux
158 35012326 00 July 2006
Installation of the discrete reflex module
Reflex function block: Operation timer
Role
Structure
This function is used to apply an on-delay to an action.
The table below shows the block's different interfaces.
Name
E x x Aux
Meaning
Timer input.
Timer's physical output.
Block's internal auxiliary output.
Illustration
E TIMER in operation t i
Output x
Output x Aux
Operation
Illustration
This table describes the different operating phases of the operation timer.
Phase
1
Description
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.
The illustration below shows the trend diagram of the operation timer function block.
E ti x x Aux
35012326 00 July 2006
159
Installation of the discrete reflex module
Reflex function block: Idle timer
Role
Structure
This function is used to apply an off-delay to an action.
The table below shows the block's different interfaces.
Name
E x x Aux
Meaning
Timer input.
Timer's physical output.
Block's internal auxiliary output.
Illustration
E TIMER idle t i
Operation
Illustration
Output x
Output x Aux
This table describes the different operating phases of the idle timer.
Phase
1
Description
The x output changes to 1 when the E input changes to 1.
2
3
On the falling edge of the E input, time-out ti is launched (time base of 0.1ms).
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.
The illustration below shows the trend diagram of the idle timer function block.
E ti x x Aux
160 35012326 00 July 2006
Installation of the discrete reflex module
Reflex function block: Operation-idle timer
Role
Structure
This function is used to apply an on-off-delay to an action.
The table below shows the block's different interfaces.
Name
E x x Aux
Meaning
Timer input.
Timer's physical output.
Block's internal auxiliary output.
Illustration
E TIMER in operation/idle t r i t f i
Output x
Output x Aux
Operation This table describes the different operating phases of the operation-idle timer.
Phase
1
2
Description
On the rising edge of the E input (on-delay) , time-out tri is launched (time base of 0.1ms).
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
4
On the falling edge of the E input (off-delay) , time-out tfi is launched (time base of 0.1ms).
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.
35012326 00 July 2006
161
Installation of the discrete reflex module
Illustration The illustration below shows the trend diagram of the operation-idle timer function block.
E tri tfi x x Aux
162 35012326 00 July 2006
Installation of the discrete reflex module
Reflex function block: 2 value operation timer
Role
Structure
This function is used to apply a t1i or t2i on-delay to an action.
The table below shows the block's different interfaces.
Name
E
Sel
Direct x x Aux
Illustration
Meaning
Timer input.
Selection of time-out t1i or t2i .
z Sel = 0 : time-out t1i, z Sel = 1 : time-out t2i,
Selection of block (for string operation).
z Direct = 0: block selected z Direct = 1: block not selected (output x takes the value of E ).
Timer's physical output.
Block's internal auxiliary output.
E 2-valuesTIMER operatio Output x
Sel
Direct t 1 i t 2 i Output x Aux
Operation This table describes the different operating phases of the 2 value operation timer.
Phase
1
2
Description
On the rising edge of the E input, a time-out corresponding to the status of input
Sel is launched.
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.
35012326 00 July 2006
163
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 x Aux t1i t2i
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
1
Description
On the rising edge of the E input of the first block a time-out is launched, corresponding to: z z the block whose Direct input is at 0, 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.
The x output changes to 0 on the falling edge of the E input .
3
Note: z x and x Aux have identical values.
z z the x Aux outputs can be used for tracking, 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.
164 35012326 00 July 2006
Illustration
Installation of the discrete reflex module
The table below shows the tracking of two timers.
E 2-values TIMER operatio Output x E 2-values TIMER operatio Output x1
Sel
Direct t 1 i t 2 i Output x Aux
Sel
Direct t 1 i t 2 i Output x Aux1
35012326 00 July 2006
165
Installation of the discrete reflex module
Reflex function block: Operation-idle time with value selection
Role
Structure
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.
The table below shows the block's different interfaces.
Name
E
Sel
Direct
Meaning
Timer input.
Selection of time-out t1i or t2i .
z z
Sel = 0 : t1i on-delay, t2i off-delay.
Sel = 1 : t2i on-delay, t1i off-delay.
Selection of block (for string operation).
z z
Direct = 0: block selected
Direct = 1: block not selected (output x takes the value of E ).
Timer's physical output.
x x Aux
Illustration
Block's internal auxiliary output.
E TIMER in operation/idle Output x
Sel
Direct t i 1 t 2 i
Output x Aux
166 35012326 00 July 2006
Operation
Illustration
Installation of the discrete reflex module
This table describes the different operating phases of the operation-idle timer with value selection.
Phase
1
2
3
4
Description
On the rising edge of input E : z the time-out corresponding to the status of input Sel is launched, z output x Aux changes to 1.
When the selected time-out is over z output x changes to 1, z 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.
On the falling edge of input E : z the time-out corresponding to the status of input Sel is launched, z output x Aux changes to 1.
When the selected time-out is over z output x changes to 1, z 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.
The illustration below shows the trend diagram of the operation-idle timer with value selection function block.
E
Sel x x Aux t1i t2i t2i t1i
35012326 00 July 2006
167
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
1
2
3
4
Description
On the rising edge of input E of the first block: z the time-out is launched, corresponding to: z the block whose Direct input is at 0, z z the status of the Sel input.
output x Aux changes to 1.
Note: Two blocks must not simultaneously have their Direct inputs set to 0.
When the selected time-out is over z output x of the relevant block changes to 1.
z 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.
On the falling edge of input E of the first block: z the time-out is launched, corresponding to: z z the block whose Direct input is at 0, the status of the Sel input.
z output x Aux changes to 1.
Note: Two blocks must not simultaneously have their Direct inputs set to 0.
When the selected time-out is over: z z output x of the relevant block changes to 1.
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
Sel
Direct t i 1 t 2 i
Output x Aux
Sel
Direct t i 1 t 2 i
Output x1
Output x Aux1
168 35012326 00 July 2006
Installation of the discrete reflex module
Reflex function block: Retriggerable monostable
Role
Structure
This function launches an action of duration ti , with the possibility of extending it for an identical duration.
The table below shows the block's different interfaces.
Name
E x x Aux
Meaning
Monostable input.
Monostable's physical output.
Block's internal auxiliary output.
Illustration
E Retriggerable MONO t i
Output x
Output x Aux
Operation
Illustration
This table describes the different operating phases of the retriggerable monostable.
Phase
1
2
Description
On the rising edge of input E (on-delay): z time-out ti is launched (time-base of 0.1ms), z outputs x and x Aux change to 1.
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 .
The illustration below shows the trend diagram of the retriggerable monostable function block.
E x ti ti ti x Aux
35012326 00 July 2006
169
Installation of the discrete reflex module
Reflex function block: Monostable with time delay
Role
Structure
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.
The table below shows the block's different interfaces.
Name
E x x Aux
Meaning
Monostable input.
Monostable's physical output.
Block's internal auxiliary output.
Illustration
E Time-delayed MONO t 1 i t 2 i
Output x
Output x Aux
Operation This table describes the different operating phases of the monostable with time delay.
Phase
1
2
3
Description
On the rising edge of input E : z z time-out t1i is launched (time-base of 0.1ms), output x Aux changes to 1.
When time out t1i is over: z z time-out t2i is launched (time base of 0.1ms), 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.
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: z z output x remains at 1 for duration t2i of the cycle in progress.
a new cycle begins (see phase).
170 35012326 00 July 2006
Illustration
Installation of the discrete reflex module
The illustration below shows the trend diagram of the monostable with time delay function block.
E x t1i t2i t1i t2i x Aux
35012326 00 July 2006
171
Installation of the discrete reflex module
Reflex function block: 2 value monostable
Role
Structure
This function enables an action of duration t1i or t2i to be applied to the triggering of an action.
The table below shows the block's different interfaces.
Name
E
Sel
Direct
Meaning
Monostable input.
Selection of time-out t1i or t2i .
z z
Sel = 0 : t1i on-delay,
Sel = 1 : t2i on-delay,
Selection of block (for string operation).
z z
Direct = 0: block selected
Direct = 1: block not selected (output x takes the value of E ).
x x Aux
Illustration
Monostable's physical output.
Block's internal auxiliary output.
E 2-values MONO Output x
Set
Direct t 1 i t 2 i Output x Aux
Operation This table describes the different operating phases of the 2 value monostable.
Phase
1
2
Description
On the rising edge of input E : z z a time-out corresponding to the status of input Sel is launched (time base of
0.1ms), outputs x and x Aux change to 1.
When the time-out is over, the x and x Aux outputs change to 0.
172 35012326 00 July 2006
Illustration
Installation of the discrete reflex module
The illustration below shows the trend diagram of the monostable with time delay function block.
E
Sel t2i t1i x 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
1
Description
On the rising edge of input E of the first block: z the time-out is launched, corresponding to: z the block whose Direct input is at 0, z z the status of the Sel input.
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
Direct t 1 i t 2 i Output x Aux
Set
Direct t 1 i t 2 i Output x Aux
35012326 00 July 2006
173
Installation of the discrete reflex module
Reflex function block: Oscillator
Role
Structure
This function enables a time base to be created, with the option of defining the signal parameters (status 0 or 1).
The table below shows the block's different interfaces.
Name
E x x Aux
Meaning
Oscillator input.
Oscillator's physical output.
Block's internal auxiliary output.
Illustration
E OSCILLATOR t 1 i t 2 i
Output x
Output x Aux
Operation
Illustration
This table describes the different operating phases of the oscillator.
Phase
1
2
Description
On the rising edge of input E : z output x oscillates for period t1i +t2i where: z z z t1i = length of high status of oscillation (time base of 0.1ms), t2i = length of low status of oscillation (time base of 0.1ms), output x Aux changes to 1.
On the falling edge of input E : z output x changes to 0 as soon as t1i for the current period is over, z the x output changes to 0 when the current period is over.
The illustration below shows the trend diagram of the oscillator function block.
E x t1i t2i t1i t2i x Aux
174 35012326 00 July 2006
Installation of the discrete reflex module
Reflex function block: D flip-flop
Role
Structure
This function is used to carry out sequential logic functions, such as memorization of an edge, etc.
The table below shows the block's different interfaces.
Name
D
CLK
SET
RESET
Meaning
Flip-flop input.
Enable input.
Output x set to 1.
Output x set to 0. This input takes priority over x x Aux
I llustration
Flip-flop's physical output.
Block's internal auxiliary output.
SET input.
Output x E
Clk
Set
Reset
D flip-flop
Output x Aux
Operation This table describes the different operating phases of the D flip-flop.
Phase
1
Description
On the rising edge of input CLK : z z output x takes the status of input D , output x Aux takes the opposite status to input D .
35012326 00 July 2006
175
Installation of the discrete reflex module
Illustration The illustration below shows the trend diagram of the D flip-flop function block.
D
CLK
RESET
SET x x Aux
176 35012326 00 July 2006
Installation of the discrete reflex module
Reflex function block: T flip-flop
Role
Structure
This function allows a 2-way split to be performed.
The table below shows the block's different interfaces.
Name
E
CLK
SET
Meaning
Flip-flop input.
Enable input.
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 x Aux
Illustration
Flip-flop's physical output.
Block's internal auxiliary output.
Output x E
Clk
Set
Reset
T flip-flop
Output x Aux
Operation This table describes the different operating phases of the T flip-flop.
Phase
1
Description
On the rising edge of input CLK : z if input E is at 1: z z z output x takes the opposite status to its current status, output x Aux takes the opposite value to x , if input E is at 0, outputs x and x Aux remain at that status.
35012326 00 July 2006
177
Installation of the discrete reflex module
Illustration The illustration below shows the trend diagram of the T flip-flop function block.
E
CLK
RESET
SET x x Aux
178 35012326 00 July 2006
Installation of the discrete reflex module
Reflex Function Block: 2 Threshold Counter
Role
Structure
This counting function is used to detect when a th1 or th2 threshold is crossed.
The following table shows the different interfaces of the block.
Name
E
Up
RESET
Meaning
Enable input.
z z
E = 0: Input Up frozen,
E = 1: Input Up enabled.
Counter input.
Note: Maximum performance of the counter is 500 Hz with a 50% duty cycle
(with the Up input directly controlled by the physical input (without filtering)).
Counter initialization input.
A Reset is required to acknowledge a change in the value of the threshold to be reached.
Sel Selection of the counting threshold: z Sel = 0: Threshold th1 selected, z Sel = 1: Threshold th2 selected.
Note: The maximum value of a threshold corresponds to the maximum number of pulses (65536 pulses).
Counter physical output.
x x Aux
Illustration
Block internal auxiliary output.
x output E
Up
Reset
Set
2 threshold COUNTER t h 1 t h 2 x Aux output
35012326 00 July 2006
179
Installation of the discrete reflex module
Operation This table describes the different operating phases of the 2 threshold counter:
Phase
1
2
3
Description
On the rising edge of the RESET input: z z z counter initialization to 0, the x and x Aux inputs switch to 0, counter on the rising edge of the Up input is incremented.
On the rising edge of the Up input, the counter is incremented (value not accessible).
When the selected threshold is reached, the x and x Aux inputs switch to 1.
Illustration The illustration below shows the timing chart for the 2 threshold Counter function block.
RESET
Sel
E
Up th2 th1 x x Aux
180 35012326 00 July 2006
Installation of the discrete reflex module
Reflex function block: Came électronique simple
Role
Structure
This function is used to detect when the two thresholds th1 and th2 have been crossed.
The table below shows the block's different interfaces.
Name
E
Meaning
Enable input.
z E = 0: Up input frozen, z 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 x Aux
Illustration
Cam's physical output.
Block's internal auxiliary output.
E
UP
Reset0
Reset1
Single electronic CAM t i t h
Output x
Output x Aux
35012326 00 July 2006
181
Installation of the discrete reflex module
Operation This table describes the different operating phases of the simple cam.
Phase
1
2
3
4
Description
On the rising edge of input RESET 1 : z z counter initialized to 0 input x Aux changes to 1,
On the high status of input RESET 0 : z input x is forced to 0.
On the rising edge of input Up , the counter is increased.
When threshold th1 is reached, output x changes to 1.
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. th2 th1
Up
RESET 0
RESET 1
E x x Aux
182 35012326 00 July 2006
Installation of the discrete reflex module
Reflex function block: 1 threshold intervalometer
Role
Structure
This function is used to trigger an action after an interval th with a maximum precision of 0.1ms
The table below shows the block's different interfaces.
Name
E
Meaning
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
Illustration
Block's internal auxiliary output.
E INTERVALOMETER, 1 Output x
Reset1 t i t h
Output x Aux
Operation This table describes the different operating phases of the intervalometer.
Phase
1
2
3
4
Description
On the rising edge of input E : z z counter initialized to 0 input x changes to 0.
Counter increases at the rate of time-base ti .
When threshold th is reached, output x changes to 1.
On the falling edge of input E with output x at 1, output x Aux changes to 1.
35012326 00 July 2006
183
Installation of the discrete reflex module
Illustration The illustration below shows the trend diagram of the intervalometer function block.
E
RESET 1
Timebase th x x Aux
184 35012326 00 July 2006
Installation of the discrete reflex module
Reflex function block: Burst
Role
Structure
This function is used to generate a pulse stream of a time length 2 x ti .
The table below shows the block's different interfaces.
Name
E x x Aux
Meaning
Block's input.
Block's physical output.
Block's internal auxiliary output.
Illustration
E BURST t i n i
Output x
Output x Aux
Operation
Illustration
This table describes the different operating phases of the Burst function block.
Phase
1
2
Description
On the rising edge of input E : z z oscillation of output x for ni periods of time, input x Aux changes to 1,
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: z the oscillation stops at the low status of output x , z input x Aux changes to 0,
The illustration below shows the trend diagram of the burst function block.
E x ti x Aux ti
35012326 00 July 2006
185
Installation of the discrete reflex module
Reflex function block: PWM (Pulse Width Modulation)
Role
Structure
This function is used to generate a fixed period periodic signal t1i with a variable duty cycle t2i/t1i .
The table below shows the block's different interfaces.
Name
E x x Aux
Meaning
Block's input.
Block's physical output.
Block's internal auxiliary output (control output).
Illustration
E PWM generation t 1 i t 2 i
Output x
Output x Aux
Operation
Illustration
This table describes the different operating phases of the PWM function block.
Phase
1
2
Description
On the rising edge of input E : z oscillation of output x , z control input x Aux changes to 1.
On the low status of input E: z the oscillation of output x stops at its low status, z 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.
The illustration below shows the trend diagram of the PMW function block.
E x t2i t1i x Aux
186 35012326 00 July 2006
Installation of the discrete reflex module
Reflex function block: Detection of underspeed
Role
Structure
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 .
The table below shows the block's different interfaces.
Name
E
FB x x Aux
Meaning
Enable function input.
Control input.
Block's physical output.
Block's internal auxiliary output.
Illustration
E
FB slow speed detection 1 t 1 i t 2 i
Output x
Output x Aux
Operation This table describes the different operating phases of the speed detection.
Phase
1
2
Description
On the rising edge of input E : z z time-out t1i (masking time) is launched, input x changes to 1.
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 : z z output x changes to 0, output x Aux changes to 1 (signaling end of movement).
If input E changes to 0, outputs x and x Aux change to 0.
35012326 00 July 2006
187
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 x Aux
188 35012326 00 July 2006
Installation of the discrete reflex module
Reflex function block: Speed monitoring
Role
Structure
This function is used to control or halt an action according to two thresholds t1i and t2i .
The table below shows the block's different interfaces.
Name
E
FB x x Aux
Meaning
Enable function input.
Control input.
Block's physical output.
Speed control output.
Illustration
E
FB slow speed detection 2 t 1 i t 2 i
Output x
Output x Aux
Application example
Activation of a conveyor belt upstream (controlled by the x Aux input) depending on the speed of a conveyor belt downstream: z conveyor belt operational when the speed of the downstream belt is greater than the high threshold 1/t1i , conveyor belt stops when the speed of the downstream belt is less than the low z 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
35012326 00 July 2006
189
Installation of the discrete reflex module
Operation This table describes the different operating phases of the speed monitoring function.
Phase
1
2
Description
On the rising edge of input E : z time-out t1i is launched, z input x changes to 1.
As long as the interval between 2 rising edges of input FB remains greater than t1i : z 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 : z z output x Aux changes to 1, time-out t2i is launched,
If input E changes to 0, outputs x and x Aux change to 0.
x Aux
1
3
1/t1i Speed
As long as the interval between 2 rising edges of input FB is less than t2i : z 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 : z output x Aux changes to 0, z time-out t1i is launched (see phase),
If input E changes to 0, outputs x and x Aux change to 0.
x Aux
1
190
1/t2i 1/t1i
Note: The operation defined above implies that t2i >t1i.
Speed
35012326 00 July 2006
Illustration
Installation of the discrete reflex module
The illustration below shows the trend diagram of the speed monitoring function block.
E x
FB t>t1i t<t1i t<t2i t>t2i t=t2i t<t1i t<t1i x Aux
35012326 00 July 2006
191
Installation of the discrete reflex module
Reflex function block: Type 1 command-check
Role
Structure
This function is used to command an action and to check whether it has been carried out after time period ti
The table below shows the block's different interfaces.
Name
Cde
Ctrl
Acq x x Aux
Meaning
Command input.
Control input.
Acknowledgement of fault.
Block's physical output.
Block's internal auxiliary output.
Illustration
Cmd Command / Control type 1
Ack
Ctrl t i
Output x
Output x Aux
Operation This table describes the different operating phases of the type 1 command-check function.
Phase
1
2
3
Description
On the rising edge of input Cde : z z time-out ti is launched, input x changes to 1.
When time-out ti is over: z if the Ctrl signal changes to status 1 during the time-out interval, the x Aux output stays at 0 (normal situation), z z if the Ctrl signal is not received, the x Aux output changes to 1 (type A error signal).
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.
On the falling edge of the Cde input, the x and x Aux outputs change to 0.
192 35012326 00 July 2006
Illustration
Installation of the discrete reflex module
The illustration below shows the trend diagram of the type 1 command-check function block.
Cde x t<ti t<ti ti t>ti
Ctrl
Acq x Aux
35012326 00 July 2006
193
Installation of the discrete reflex module
Reflex function block: Type 2 command-check
Role
Structure
This function is used to: z command an action and check whether it has been carried out after time z period t1i , delete the action and check whether it has been deleted after time period t2i .
The table below shows the block's different interfaces.
Name
Cde
Ctrl n
Acq x x Aux
Meaning
Command input.
Control n input
Acknowledgement of fault.
Block's physical output.
Block's internal auxiliary output.
Illustration
Cmd Command / Control type 2
Ack
Ctrl 1
Ctrl 2 t 1 i t 2 i
Output x
Output x Aux
194 35012326 00 July 2006
Operation
Installation of the discrete reflex module
This table describes the different operating phases of the type 2 command-check function.
Phase
1
2
3
4
Description
On the rising edge of input Cde : z time-out t1i is launched, z input x changes to 1.
When time out t1i is over: z if the Ctrl1 signal changes to status 1 during time-out interval t1i , the x Aux z input stays at 0 (normal situation), if the Ctrl1 signal is not received, the x Aux output changes to 1 (type A error z signal).
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: z z a rising edge on input Acq with input Ctrl1 at 1, change of status of input Cde .
On the falling edge of input Cde : z z time-out t2i is launched, input x changes to 0.
When time out t2i is over: z if the Ctrl2 signal changes to status 1 during time-out interval t2i , the x Aux input stays at 0 (normal situation), z if the Ctrl2 signal is not received, the x Aux output changes to 1 (type A error signal).
if the Ctrl2 signal falls back while the Cde input is at 0, the x Aux output z changes to 1 (type B error signal).
The x Aux input is set to 0 in the event of: z a rising edge on input Acq with input Ctrl2 at 1, z change of status of input Cde .
35012326 00 July 2006
195
Installation of the discrete reflex module
Illustration The illustration below shows the trend diagram of the type 2 command-check function block.
Cde x t<t1i
Ctrl1 t<t1i t>t1i t1i t<t2i t>t2i t2i
Ctrl2
Acq x Aux
196 35012326 00 July 2006
Installation of the discrete reflex module
Reflex function block: Command-counting
Role
Structure
This function is used to decect a th threshold in order to command a positioning action.
The table below shows the block's different interfaces.
Name
Cde
Reset
Up x x Aux
Meaning
Command input.
Outputs x and x Aux are set to 0.
Counting input.
Block's physical output.
Block's internal auxiliary output.
Illustration
E
Reset
Up
Command / Counting t h
Output x
Output 18 Aux
Operation This table describes the different operating phases of the command-counting function.
Phase
1
2
Description
Counter initialized to 0 on the rising edge of the Reset input.
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.
35012326 00 July 2006
197
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 x Aux
198 35012326 00 July 2006
Installation of the discrete reflex module
Reflex function block: Fault Signaling
Role
Structure
This function is used to indicate a fault, with acknowledgement and clearing.
The table below shows the block's different interfaces.
Name
Def
Acq
Eff x x Aux
Meaning
Fault input.
Acknowledgement input
Clear input
Block's physical output.
Output inactive for this block.
Illustration
Err
AcK
Clr
Fault signalling t 1 i t 2 i
Output x
Output x Aux
Operation This table describes the different operating phases of the Fault Signaling function.
Phase
1
2
3
Description
If the Def status is at the high status, the x output oscillates for period 2 x t1i .
On the rising edge of input Acq : z z if the fault persists, the output changes to 1, if the fault disappears, the output oscillates for period 2 x t2i .
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: z t1i flashes rapidly: fault present and unacknowledged by Acq, z z z t2i flashes slowly: fault not present and acknowledged by Acq, lit up: fault present and acknowledged by Acq, out: last fault cleared by the Eff input after acknowledgement.
35012326 00 July 2006
199
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 x
2 x t1i 2 x t1i 2 x t2i
200 35012326 00 July 2006
9.3
Installation of the discrete reflex module
Configuration of discrete reflex module
Presentation
Subject of this section
What's in this
Section?
This section presents the specific configuration features of a discrete reflex module.
This section contains the following topics:
Topic
Configuring the discrete reflex module
Presentation of the reflex function configuration editor
Assigning and configuring a reflex function
Adjusting the configuration parameters of a reflex function
Associating an event with a virtual output
Page
35012326 00 July 2006
201
Installation of the discrete reflex module
Configuring the discrete reflex module
Introduction
Illustration
The TSX DMY 28 RFK discrete reflex module uses the standard discrete I/O parameters (See
Configuration of discrete parameters, p. 108 )).
However, it also has its own specific parameters, such as: z assigning of a reflex function to a given output channel, z 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.
The screen below shows some examples of function assignment for a given channel.
Spécific parameters
Chan.
16
17
18
19
20
21
22
23
24
25
26
27
28v
29v
30v
31v
Symbol Supply Monit.
Active
Task
MAST
MAST
Reactivate
Programmed
Programmed
Fall. Value
Fallback to
Fallback to
Fallback to
Fallback to
Fallback to
Fallback to
Fallback to
Fallback to
Fallback to
Fallback to
Fallback to
Fallback to
Fallback to
Fallback to
Fallback to
Fallback to
Function
Combinational
TIMER in operation
TIMER idle
TIMER with 2 values,
MONO with time delay
OSCILLATOR
COUNTER, 2
PWM generation
Command/counting
Fault signalling
Direct
Direct
Direct
Direct
Direct
Direct
Event
202 35012326 00 July 2006
Installation of the discrete reflex module
Presentation of the reflex function configuration editor
Presentation
Illustration
Description
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.
The illustration below shows the configuration zone of a reflex function block.
Output 26 E TIMER in operation t i = 0
Output 26 Aux
1 2 1 2 1 2 1 2 3 4 5 6
The table below shows the different parts of the configuration zone.
4
5
Number
1
2
3
6
Function
Columns allowing contacts to be entered with their associated language object.
Columns allowing horizontal and vertical links between contacts to be entered.
Column allowing the function blocks or their link with the combinational to be set to 1.
Column showing the inputs on the selected function block.
Column: z z showing the type of internal parameter used by the block, allowing the required reflex function to be selected.
Column allowing the type of output coil to be entered.
35012326 00 July 2006
203
Installation of the discrete reflex module
Description of graphical objects
The table below shows the various graphical objects available depending on the entry column or cell.
Object
-- --
-----------
------
|
------
1 -
----| |----
----|/|----
----( )----
----(/)----
1
6
3
1
6
Column(s) Description
1, 2, 3 Empty zone
1, 2, 3
2
Horizontal link
Vertical link
Input set to 1
Normally open contact
Normally closed contact
Direct coil
Negated coil
204 35012326 00 July 2006
Installation of the discrete reflex module
Assigning and configuring a reflex function
Presentation
Procedure
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: z the sequential logic associated to the different inputs, z z the type of output required, parametering of the block.
The sequential logic is generated in contact language using the language objects associated with the reflex module concerned.
The table below shows the different steps involved in the configuration of a reflex function block.
2
3
4
Step
1
5
4
Action
Access the module's hardware configuration screen.
Select Outputs from the pull-down menu in the module zone.
Click in the Function cell of the channel to be assigned.
Select the required function from the pull-down list.
Generate the sequential logic. To do this, click in the chosen cell then: z select a graphical object (contact, link, set input to 1), z for a contact select: z z z the variable (%Ixy, %Qxy, ERR), the i address.
select the type of coil.
Confirm the configuration by clicking on Confirm .
35012326 00 July 2006
205
Installation of the discrete reflex module
Adjusting the configuration parameters of a reflex function
Introduction
Procedure
Certain reflex function blocks have internal parameters (values of between 0 and
65535) required for their operation (example: temporal thresholds).
These parameters are modifiable: z from the module's adjustment screen (in local mode only), z by program (see
Explicit exchange objects: General, p. 145 ).
The table below describes the procedure for modifying the adjustment parameters of a reflex function block.
Step
1
2
Action
Access the module's hardware configuration screen.
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.
16
17
18
19
20
21
22
23
24
25
26
27
28v
29v
30v
31v
Function block
INTERVALOMETER, 1
TIMER with 2 values, in operation
TIMER with 2 values, in operation
OSCILLATOR
Fault signalling
Direct
Direct
Direct
Directe
Direct
Direct
Direct
Direct
Directe
Direct
Combinational
Input 1 t i t 1 i t 1 i t 1 i t 1 i
TM value 1
2
3000
50000
10000
1000
Input 2 t h t 2 i t 2 i t 2 i t 2 i
TM value 2
50000
50000
50000
10000
200
3
4
5
For the channel concerned, select the cell relating to the parameter to be entered.
Enter the parameter.
Confirm by pressing Enter .
206 35012326 00 July 2006
Installation of the discrete reflex module
Associating an event with a virtual output
Introduction
Event output properties
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.
The possible event processing properties are: z normal (no event associated with the channel), z channel by channel event processing, z event triggered on a rising edge (RE), z z event triggered on a falling edge (FE), 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: z z
0 to 31 for TSX 5710/102/103/153, PMX 57 102, PCX 571012 processors,
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.
z z
The event number proposed is the first available number in the list.
A manually input number outside the tolerance range will not be accepted on z confirmation.
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.
35012326 00 July 2006
207
Installation of the discrete reflex module
Procedure The table below gives the different steps enabling an event to be associated with an output and its properties to be defined.
Step
1
2
3
4
5
6
Action
Access the module's hardware configuration screen.
Select Outputs from the pull-down menu in the module zone.
Double-click in the Event cell of the channel to be assigned.
Select the required function.
Enter the Evt event number.
Repeat the operation for every channel to be configured (from step).
208 35012326 00 July 2006
9.4
Installation of the discrete reflex module
Bits and words associated with discrete reflex module
Presentation
Subject of this section
What's in this
Section?
This section presents the different language objects specific to the discrete reflex module.
This section contains the following topics:
Topic
Implicit exchange language objects associated with module TSX DMY 28 RFK
Explicit exchange language objects associated with module TSX DMY 28 RFK
Page
35012326 00 July 2006
209
Installation of the discrete reflex module
Implicit exchange language objects associated with module TSX DMY 28 RFK
Presentation
Illustration
Implicit exchange language objects associated with the reflex module can be used in: z z the sequential logic of the function block, the PLC processor program, z
The illustration below shows the different exchanges possible: z within a reflex module, between the reflex module and the PLC processor.
PLC processor Reflex module
PLC program
%Ixy.i (i=0 à 15)
%Ixy.i (i=16 à 31)
%Qxy.i (i=16 à 31)
Output x
Sequential Logic
Output x Aux
%Ixy.i.1 (i=16 à 31)
Physical inputs
0 à 15
Physical outputs
16 à 27
Event task
%Ixy.i (i=28 à 31)
210 35012326 00 July 2006
-
Key:
(1)
(2)
Installation of the discrete reflex module
Bit objects The table below shows the different implicit exchange bit objects of module
TSX DMY 28 RFK.
Address Function Use within module
Mode Update
Read Real time %Ixy.i
(i = 0 to 15)
%Ixy.i
(i = 16 to 27)
%Ixy.i
(i = 28 to 31)
%Ixy.i.1
(i = 16 to 31)
%Qxy.i
(i = 16 to 31)
Image bits of the module's physical input status.
Image bits of the module's physical output status.
Image bits of the module's virtual output status.
Image bits of the module's internal auxiliary output status.
Module output command bits
ERRi
(i = 16 to 27)
ERR28
Short circuit error bits for the module's physical outputs
External supply error bits for module inputs
ERR29 External supply error bits for module outputs
%Ixy.i.ERR
Channel error bit
%Ixy.i.MOD.ERR Module error bit
-
-
Read
Read
Read
Read
(2)
Read
Read
Read
Real time
Real time
Real time
(1)
Real time
Real time
Real time -
-
Use in the PLC program
Mode Update
Read (1)
Read
Read
Read
-
Read/
Write
Read
Read
(1)
(1)
(1)
(1)
(1)
(1)
Not used
Update to the rate of the PLC task in which the channels are configured.
These command bits control the corresponding physical outputs when the Direct function is selected.
35012326 00 July 2006
211
Installation of the discrete reflex module
Word objects
Address
%IWxy.i:X0
(i = 28 to 31)
%IWxy.i:X1
(i = 28 to 31)
%IWxy.i:X7
(i = 28 to 31)
%QWxy.i:X0
(i = 28 to 31)
The table below shows the different implicit exchange word objects of module
TSX DMY 28 RFK.
Function
-
Use within module
Mode Update
Use in the PLC program
Mode Update
Read (1) Event status associated with channel i X0 = 1: rising edge
Event status associated with channel i X1 = 1: falling edge
Event status associated with channel i X7 = 1: loss of event
Event masking command bit -
-
Read
Read
Write
(1)
(1)
(1)
-
Key:
(1)
Not used
Update to the rate of the PLC task in which the channels are configured.
212 35012326 00 July 2006
Installation of the discrete reflex module
Explicit exchange language objects associated with module TSX DMY 28 RFK
Presentation
Modification of the internal values by program
The TSX DMY 28 RFK module reuses the language objects of standard discrete modules (see the Language objects associated with the discrete specific
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: z
%MWxy.i.4 which contains the first internal value of the function block, z
%MWxy.i.5 which contains the second internal value of the function block,
Other than the standard instructions (see Explicit exchange language objects
associated with module TSX DMY 28 RFK , p. 213 ), the TSX DMY 28 RFK module
also uses a specific instruction MOD_PARAM (Modify parameters) which enables the parameters associated with a single channel to be modified.
Syntax: MOD_PARAM %CHxy.i (no., value1 , value2 , 0) where: z i = 16 or 24 (index of the first channel of a group of 8 channels), z 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)
35012326 00 July 2006
213
Installation of the discrete reflex module
214 35012326 00 July 2006
AS-i Bus
III
At a Glance
Aim of this part
What's in this
Part?
This part presents the AS-i bus on PLC TSX/PCX 57 and describes its implementation with the software PL7 Junior and Pro.
This part contains the following chapters:
Chapter
10
11
12
13
14
15
16
Chapter Name
General introduction to the AS-i Bus
AS-i bus configuration
Debugging the AS-i bus
Bits and words associated with the AS-i function
AS-i operating mode
AS-i performance
DFB for AS-i Security Monitor
Page
215
35012326 00 July 2006
AS-i Bus
216 35012326 00 July 2006
General introduction to the AS-i Bus
10
At a Glance
Subject of this
Chapter
What's in this
Chapter?
This Chapter introduces the AS-i bus on the TSX/PCX 57 PLC, and describes how to access the different application editors.
This chapter contains the following topics:
Topic
Presentation of the AS-i Bus
Architecture of the TSX SAY 100 module
Structure of an AS-i slave
How to declare an AS-i communication module in the PLC rack
How to access the AS-i Bus configuration
Page
217
35012326 00 July 2006
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: z either in local mode, z or in connected mode; in this case the modification is limited to certain parameters.
218 35012326 00 July 2006
AS-i Bus
Implementation principles
Mode
Local
Local or connected
Connected
Local or connected
The following table presents the different implementation phases of the AS-i bus.
Phase
Declaration of module
Description
Selection of the TSX SAY 100 module’s slot in the rack.
Declaration of slave devices Selection for each device: z of its slot number on the bus, z of the slave type.
Input of the configuration parameters.
Configuration of the module channel (See AS-i bus
)
Confirmation on the module level.
Confirmation of the configuration parameters.
(See Confirming the configuration of a module.,
)
Global confirmation of the application (See Globally reconfiguring an
Confirmation at application level.
Symbolization
Programming
Transfer
Debugging
Documentation
Symbolization of the variables associated with the slave devices.
Programming the functions that are carried out with the help of the
AS-i bus.
Transfer of the application to the PLC.
Debugging the application with the help of: z the debugging help screens which display the slave z connection, their parameters, … the diagnostic screens which allow identification of errors.
Printing the different information relating to the application.
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).
35012326 00 July 2006
219
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: z z z
Profile M0 - Minimum Master: the master only puts forward the configuration of slaves connected to the bus on power-up and input/output exchanges.
Profile M1 - Full Master: this profile covers all the operating functions set by the
AS-i standard,
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 architecture
The figure below shows the TSX SAY 100 module architecture.
TSX SAY 100
1 I/O data
2
3
4
5
6
Parameters current
Configuration /
Identification
LDS
LAS
LPS
AS-i bus
220 35012326 00 July 2006
Description of constituent elements
AS-i Bus
The table below shows the different elements that make up the architecture of the
TSX SAY 100 module.
4
5
6
2
3
Number Element
1 I/O data
Current parameters
Configuration/
Identification
Description
Image of 124 inputs and 124 outputs of AS-i bus.
Image of parameters for all slaves.
This field contains all the I/O codes and identification codes for all the detected slaves.
LDS
LAS
LPS
List of all the slaves detected on the bus.
List of active slaves on the bus.
List of slaves expected on the bus and configured by PL7.
35012326 00 July 2006
221
AS-i Bus
Structure of an AS-i slave
At a Glance
Structure illustration
The AS-i bus is used to interconnect 31 slave devices, each one having: z
4 input bits, z z
4 output bits,
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).
The figure below shows the structure of an AS-i slave.
AS-i slave
1 I/O data
D3
D0
2 Parameters
P3
P0
3
Configuration/
Identification
AS-i bus
4 Address
222 35012326 00 July 2006
Description of constituent elements
AS-i Bus
The table below shows the different elements that make up the structure of an
AS-i slave.
Number Element
1 Input/output data
2
3
4
Parameters
Configuration/
Identification
Address
Description
Input data is stored by the slave and made available for the AS-i master.
Output data is updated by the master module.
The parameters are used to control and switch internal operating modes to the sensor or the actuator.
This field contains: z z the code which corresponds to I/O configuration, the slave identification (ID) code.
Physical address of slave.
Note : The operating parameters, address, configuration and identification data are saved in a non-volatile memory.
35012326 00 July 2006
223
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
1
Action
Double click on the required position in the rack displayed.
Result : The dialog box Add a module appears:
Add a module
Family:
Analog mod.
Communication
Upcounting
Movement
Weighing
Discrete
1.5
1.5
1.5
1.5
1.7
1.5
Module:
TSX SAY100 As-Interface MODULE
TSX SCY 21600 PCMCIA MODULE
TSX SCY 21601 PCMCIA MODULE
OK
Cancel
2
3
4
Select the choice Communication in the Family field.
Select in the field Module the reference of the module.
Confirm the selection with OK .
Result : The module is declared in its slot; this is grayed out and contains the module reference.
Configuration
TSX 57303 V5.0...
XMWI
XTI..
6
A
Y
0
0 1 2 3 4 5
3
Note : The maximum number of TSX SAY 100 modules which can be installed in a configuration is: z z
2 modules, with a TSX/PMX/PCX 57-1• processor,
4 modules, with a TSX/PMX/PCX 57-2• processor, z 8 modules, with a TSX/PMX/PCX 57-3• processor, a TSX/PMX 57-4• processor.
224 35012326 00 July 2006
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
1
Action
Access the screen Hardware configuration
Result : The rack’s hardware configuration screen appears.
Configuration
TSX 57303 V5.0...
XMWI
XTI..
0 1 2 3 4 5 6
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 .
Result : The selected module’s hardware configuration screen appears.
TSX SAY 100 [RACK 0 POSITION 6]
Configuration
Designation :AS-Interface module
Chan. 0
AS-interface configuration
1
2
3
4
5
8
9
6
7
10
MAST
General parameters
Automatic addressing
Slave 1 configuration:
Profile
Comment
Asi entry AS-i symbol
1
2
3
4
Asi output
1
2
3
4
AS-i symbol
Fallback mode on failure
Maintien Fallb. to 0
Parameters
0
1
2
3
35012326 00 July 2006
225
AS-i Bus
226 35012326 00 July 2006
AS-i bus configuration
11
At a Glance
Subject of this
Chapter
What's in this
Chapter?
This Chapter describes the Configuration aspect for installing the AS-i bus.
This chapter contains the following topics:
Topic
Description of an AS-i communication module’s configuration screen
How to define a slave device on the AS-i bus
How to modify the AS-i Bus software configuration
How to access the description of an AS-i slave
How to define a new slave profile in the standard AS-I catalogue
How to modify AS-i slave general parameters: Automatic addressing
How to modify AS-i slave general parameters: Fallback mode
Page
35012326 00 July 2006
227
AS-i bus configuration
Description of an AS-i communication module’s configuration screen
At a Glance
Illustration
The configuration screen of the AS-i module gives access to the parameters associated with the module and the slave devices.
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
3
4
Chan. 0 MAST
AS-interface configuration
1
2
3
8
9
10
6
7
4
5
General parameters
Automatic addressing
Slave 1 configuration:
Profile
Comment
2
3
4
Asi entry AS-i symbol
1
2
3
Asi output
1
4
AS-i symbol
Fallback mode on failure
Maintien Fallb. to 0
Parameters
0
1
2
3
5
6
228 35012326 00 July 2006
AS-i bus configuration
Description
Address Element
1 Title bar
2 Command zone
3
4
5
6
The following table shows the different elements of the configuration screen and their functions.
Channel zone
AS-i configuration zone
General parameters zone
Slave configuration zone
Function
Indicates the reference of the selected module and its physical position in the rack.
Allows the selection of the parameter type: z Configuration , z 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 .
Allows selection of the task in which the information from the AS-i communication channel will be scanned: z MAST task, z FAST task.
Display of this zone is optional. Selection is made using the command View →
Channel zone .
Allows: z display of the slave devices connected to the bus, z definition of a new configuration (adding, modifying or detecting slave devices).
Allows the display and the selection of the general parameters which are applied to all the slaves on the bus.
z z
Automatic addressing,
Fallback mode.
Allows display of the data associated with the selected slave, such as: z its profile, z z z a comment, its AS-i symbol (the symbols are defined with the help of the variables editor), its parameters.
35012326 00 July 2006
229
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: z
Non-specialized products, z
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.
230 35012326 00 July 2006
Procedure
35012326 00 July 2006
AS-i bus configuration
This operation supports the declaration of a slave device on the AS-i bus.
Step
1
2
Action
Access the AS-i module’s hardware configuration screen.
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.
9
1
8
11
12
Associate Profile
AS-interface profile families
Code AS-i family name
Capacitive detectors
Inductive proximity sensors
Photo-electric detectors
Private family
IP20 connection interface
AS-interface profile catalog
AS-i Name Comment View
Add
Modify
Details
Ok Cancel
3 In the Family Name field select the required family.
Result : The Profile catalogue associated with the selected family appears.
AS-interface profile families
AS-i AS-i family name
7
8
9
10
11
Control station
Détecteurs capacitifs
Photo-electric detectors
Interface E/S
Détecteurs inductifs
Associate a profiile
AS-i -Catalog : Photo-electric detectors
1.1
Nom
XUJ-K063539AS
1.1
XUJ-K103534AS
1.1
XUJ-K123538AS
1.1
XUJ-K703538AS
1.1
XUJ-ZAS1
Commentaire
Photo elect. detect. reflex
Photo elect. detect. Thru beam
Photo elect. detect bs 1.2m
Photo elect. detect bs 0.7m
Back over for XUJ detectors
Ok Cancel
View
Add
Modify
Détails
4 In the Profile catalogue select the required device.
231
AS-i bus configuration
Step
5
Action
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
3
4
5
P XUJ-K1233538AS
6 To connect other slave devices to the AS-i bus, repeat the procedure from step
2.
232 35012326 00 July 2006
AS-i bus configuration
How to modify the AS-i Bus software configuration
At a Glance
Procedure for deleting a slave
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.
This operation allows the deletion of a slave declared on an AS-i Bus.
Step
1
2
Action
Select the slave to be deleted.
Select the command Edit → Delete an AS-i slave .
Procedure for moving a slave
This operation allows the movement of a slave declared on an AS-i Bus.
Step
1
2
3
4
Action
Select the slave to be moved.
Select the command Edit → Cut an AS-i slave .
Select the new required slot.
Select the command Edit → Paste an AS-i slave .
Procedure for copying a slave
This operation allows the copying of a slave declared on an AS-i Bus.
Step
1
2
3
4
Action
Select the slave to be copied.
Select the command Edit → Copy an AS-i slave .
Select the slot of the new slave.
Select the command Edit → Paste an AS-i slave .
35012326 00 July 2006
233
AS-i bus configuration
How to access the description of an AS-i slave
At a Glance
Definition of a profile
Details of a profile
The PL7 software allows access to all the information relating to an AS-i device such as: z z the definition of a profile, the details of a profile.
A profile is defined by: z z its name, a comment (optional), z z z identifiers (IO, ID), a number of inputs and/or outputs, operation parameters.
The Detail function allows access, for a given slave, to all the information presented 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:
AS- profilei:
I/O Error:
Télémécanique
0.0
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
234 35012326 00 July 2006
AS-i bus configuration
Procedure for accessing information on a profile
The following table shows the procedure for displaying the characteristics of a slave device.
Step
1
2
3
Action
Access the AS-i module’s hardware configuration screen.
Double click on the required slave.
Result: The window Associate a profile displays and highlights the device in question
Click on the button: z View to access definition information, z Detail to access all the information.
35012326 00 July 2006
235
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.
236 35012326 00 July 2006
Procedure
AS-i bus configuration
The following table presents the procedure for defining a slave profile, which is not provided in the standard catalogue.
Step
1
2
3
Action
Access the AS-i module’s hardware configuration screen.
Double click in a slave’s host cell (1 to 31).
Result : The screen Associate a profile appears.
Select Private family in the field Family name .
Result : The Profile catalog linked to the selected family appears.
8
11
9
1
12
Associate Profile
AS-interface profile families
Code AS-i family name
Capacitive detectors
Inductive proximity sensors
Photo-electric detectors
Private family
IP20 connection interface
AS-interface profile catalog
AS-i Name
A.4
Sensor 1I 4Q
Comment View
Add
Modify
Details
Ok Cancel
4
5
6
7
8
Click on the button Add .
Enter: z the name of the new profile, z a comment (optional).
Select: z the IO code (corresponds to the input/output configuration), z the ID code (identifier).
For each parameter define: z the system’s acknowledgement (box checked), z a label (optional).
Confirm the introduction of a new profile using Confirm .
35012326 00 July 2006
237
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: z replacing a faulty slave (See Automatic replacement of a faulty AS-i slave, z
), inserting a new slave (See How to insert a slave device into an existing AS-i
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
1
2
Action
Access the AS-i communication module’s configuration screen.
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
Automatic addressing
Fallback mode on failure
Fallback: Maintain
Note : By default, the Automatic addressing parameter has been selected in the configuration screen.
238 35012326 00 July 2006
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: z
Fallback to 0 : AS-i slave outputs which are present on the bus are set to 0 z
(%Q objects are not modified),
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
1
2
Action
Access the AS-i communication module’s configuration screen.
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
Automatic addressing
Fallback mode on failure
Fallback: Maintain
35012326 00 July 2006
239
AS-i bus configuration
240 35012326 00 July 2006
Debugging the AS-i bus
12
At a Glance
Subject of this
Chapter
What's in this
Chapter?
This Chapter describes the Debug aspect of the AS-i bus.
This chapter contains the following topics:
Topic
Introduction to the Debug function
Description of an AS-i module’s debugging screen
How to access functionality in the module diagnostics and channel diagnostics for an AS-i device
Displaying the slaves’ status
How to access adjustment of an AS-i device’s parameters
Page
How to access the AS-i channels’ forcing/unforcing function
How to access the SET and RESET commands of the AS-i channels
Automatic replacement of a faulty AS-i slave
How to insert a slave device into an existing AS-i configuration.
How to modify the address of an AS-i device
35012326 00 July 2006
241
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: z z to display the slave state (connection, parameters etc.), 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.
242 35012326 00 July 2006
Debugging the AS-i bus
Description of an AS-i module’s debugging screen
At a Glance
Illustration
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, …).
The following is the layout of the debugging screen:
1
2
TSX SAY 100 [RACK 0 POSITION 8]
Debug
Designation : AS-Interface module Version : 0.0
3
4
Chan. 0 : Asi
Channel 0
As-Interface BUS
AS-interface configuration
D
D
D
D
1 P
2 P
9
10
6
7
8
3
4
5
P
P
XZ-SDA22D32
XAL-S2003
LF2K09BW#**C
XZ-SDA22D32
RUN
MAST
Slave no : 1
Profile
Projected :
Detected :
%I
%Q
Chan.
0
1
2
3
2
3
0
1
3.0
3.0
Asi Symbol
Not handled
Not handled
Not handled
Not handled
ERR IO DIAG...
DIAG...
0
0
0
1
Parameters (3-0)
Value : 1111
Modify PARAM
State
F5
F6
F7
Global unforcing
Chan. action
F4 Force to 0
F8
Force to 1
Unforce
Set
Reset
5
35012326 00 July 2006
243
Debugging the AS-i bus
Description The following table shows the different elements of the debugging screen and their functions.
4
5
Address Element
1
2
3
Title bar
Module zone
Channel zone
Function
Indicates the reference of the selected module and its physical position in the
PLC.
Allows the selection of the parameter type: z z
Configuration ,
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).
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).
AS-i configuration zone Displays the slave devices connected to the bus.
Slave zone Displays the status of the slave’s channels and gives access to the debugging functions.
244 35012326 00 July 2006
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: z internal errors (internal software errors, communication error with the processor, z z configuration, parametering or command error), external errors(slave device failed, AS-i supply switched off, terminal error, difference between physical configuration and PL7 configuration), other errors (module absent or switched off).
A faulty module becomes apparent when certain lights change to red, such as: z in the configuration editor at rack level: z the module position light, z in the configuration editor at module level: z the lights RUN , ERR and I/O , z the light DIAG .
A faulty channel becomes apparent when certain lights change to red, such as: z in the configuration editor at rack level: z z the module position light, in the configuration editor at channel level: z the light DIAG .
35012326 00 July 2006
245
Debugging the AS-i bus
Procedure for accessing the module diagnostics
The following table presents the procedure to access the screen Module diagnostics .
Step
1
2
Action
Access the AS-i module’s hardware configuration screen.
Click on the button DIAG situated in the module zone.
Result : The list of module errors appears.
Internal faults
Module Diagnostics
External faults Other faults
OK
Procedure for accessing the channel diagnostics
The following table presents the procedure for accessing the screen Channel diagnostics .
Step
1
2
Action
Access the AS-i module’s hardware configuration screen.
Click on the button DIAG situated in the channel zone.
Result : The list of channel errors appears.
Internal faults
Channel Diagnostics
External faults
Device error
Other faults
Configuration error
OK
246 35012326 00 July 2006
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.
35012326 00 July 2006
247
Debugging the AS-i bus
Displaying slave status
Case
1
For each slave device, one of the following four cases can occur:
Illustration
Slave status:
AS-interface configuration
P XAL-S2003 D
3
1
2
4
5
Explanation
The slave P specified in configuration and the detected slave D are identical.
2 The slave P specified in configuration and the detected slave D are not identical. The slave is declared faulty (1).
3
4
Slave status:
AS-interface configuration
P XAL-S2003 D 1
2
3
4
5
Slave status:
AS-interface configuration
P XAL-S2003 1
2
3
4
5
Slave status:
AS-interface configuration
XAL-S2003 D 1
2
3
4
5
A slave P is specified at configuration but no slave is detected.
The slave is declared faulty (1).
An additional slave, not specified at configuration, is connected to the bus. The slave is declared faulty (1).
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.
248 35012326 00 July 2006
Debugging the AS-i bus
How to access adjustment of an AS-i device’s parameters
At a Glance
Procedure
The debugging screen of an AS-i module allows, amongst other things, access to modification of a slave’s parameters.
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
D
D
1 P
2 P
3
XZ-SDA22D32
XAL-S2003
Slave no : 1
Profile
Projected
Detected
3.0
3.0
Parameters (3-0)
Value : 1111
Modify PARAM
Global unforcing
D
D
6
7
8
9
10
4
5
P
P
LF2K09BW#**C
XZ-SDA22D32
%I
%Q
Chan.
0
1
2
3
2
3
0
1
Asi Symbol
Not handled
Not handled
Not handled
Not handled
0
1
0
State
0
Chan. action
F4 Force to 0
F5
F6
F7
F8
Force to 1
Unforce
Set
Reset
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
3 1
Voie 0 : Asi
Unused
Voie 0
BUS As-Interface
Send Cancel entry
AS-interface configuration
D
D
XZ-SDA22D32
XAL-S2003
3
4
1 P
2 P
Slave no : 1
Profile
Projected:
Unused
RUN
Flash On/Off
Detected: 3.0
Chan.
3.0
Close
MAST
AS-i Symbol
ERR IO
Parameters (3-0)
Value : 1111
Modif PARAM
State
DIAG...
DIAG...
Global unforcing
Chan. action
4 Modify the required parameters.
5 Click on Send to recognize the new values.
35012326 00 July 2006
249
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: z z for a channel: z forcing to 0, z z forcing to 1, unforcing.
for all the channels (when at least one channel is forced): z global unforcing.
Procedure The following table shows the procedure to follow to force or unforce the channels linked to an AS-i slave.
Action for a group of channels Step Action for a channel
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.
Result : It is possible to modify the channel using the buttons situated in the field Channel action .
Slave no : 1
Profile
Projected : 3.0
Parameters (3-0)
Value : 1111
Modify PARAM
Detected : 3.0
Global unforcing
%I
%Q
Chan.
0
1
2
3
2
3
0
1
Asi Symbol
Not handled
Not handled
Not handled
Not handled
0
1
0
State
0
0
Chan. action
F4 Force to 0
F5
F6
F7
F8
Force to 1
Unforce
Set
Reset
Click on the button Global unforcing found in the slave zone.
4 Select the required function (buttons Force to 0 or Force to 1 in the field Channel Action .
250 35012326 00 July 2006
Debugging the AS-i bus
How to access the SET and RESET commands of the AS-i channels
At a Glance
Procedure
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.
The following table presents the procedure for assigning a value of 0 or 1 to the selected AS-i slave’s channels.
Step
1
2
3
Action
Access the AS-i module’s debugging screen.
Select a slave in the zone AS-i Configuration .
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
Projected 3.0
Parameters (3-0)
Value : 1111
Modify PARAM
Detected
3.0
Global unforcing
%I
%Q
Chan.
0
1
2
3
2
3
0
1
Asi Symbol
Not handled
Not handled
Not handled
Not handled
0
1
0
State
0
0
Chan. action
F4 Force to 0
F5
F6
F7
F8
Force to 1
Unforce
Set
Reset
4 Select the required function (buttons Set or Reset ) in the field Channel action .
35012326 00 July 2006
251
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. 238
).
Two options are available: z
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 z automatically inserted into the list of detected slaves (LDS) and list of active slaves (LAS).
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).
252 35012326 00 July 2006
How to insert a slave device into an existing AS-i configuration.
Debugging the AS-i bus
At a Glance
Procedure
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: z the service Automatic addressing of the configuration mode is active (See How z z
to modify AS-i slave general parameters: Automatic addressing, p. 238
), a single slave is absent in the physical configuration, the slave which is to be inserted is projected in the PL7 configuration, the slave has the profile expected by the configuration, z z the slave has the address 0.
Therefore the AS-i interface card will automatically assign to the slave the value predefined in the configuration.
The following table presents the procedure for making the automatic insertion of a new slave effective.
2
3
Step
1
Action
Add the new slave in the configuration screen in local mode.
Do a configuration transfer to the PLC in connected mode.
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.
35012326 00 July 2006
253
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
1
2
Action
Access the TSX SAY 100 module’s debugging screen.
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:
OK
8
9
6
7
4
5
0
2
Cancel
3
4
Select the required address in the list of Available addresses (use the scroll bar if necessary).
Confirm the selection with OK .
254 35012326 00 July 2006
Bits and words associated with the AS-i function
13
At a Glance
Subject of this
Chapter
What's in this
Chapter?
This Chapter introduces the different word and bit objects associated with the
AS-i function, as well as how to address them.
This chapter contains the following sections:
Section
13.1
13.2
Topic
Addressing objects associated with the AS-i function
Language objects associated with the AS-i function
Page
35012326 00 July 2006
255
Bits and words associated with the AS-i function
256 35012326 00 July 2006
13.1
Bits and words associated with the AS-i function
Addressing objects associated with the AS-i function
Adressing language objects associated with slave devices connected to the AS-i bus.
At a Glance
Illustration
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.
Reminder of the principle of addressing:
% I or Q
Symbol Type of object
\ xy.0
TSX SAY 100 address rack/module/channel
\ n
Slave no.
i
Bit position
Specific values The table below gives specific values to AS-i slave objects.
i
Element n
Values
0 to 31
0 to 3 -
Comment
Slot 0 cannot be configured.
35012326 00 July 2006
257
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
Section
What's in this
Section?
This Section introduces the different language objects associated with the AS-i function.
This section contains the following topics:
Topic
Implicit exchange objects associated with the AS-i function
Management of exchanges: Module %MWxy.MOD.0:Xj or channel
MWxy.0.0 :Xj exchanges in progress
Exchange management: Module %MWxy.MOD.1:Xj or channel %MWxy.i.1:Xj report
Explicit exchange objects: General
Explicit exchange objects: %MWxy.0.2:Xj to %MWxy.0.23:Xj channel status
Explicit exchange object: %MWxy.0.24:Xj channel command
Explicit exchange object: %MWxy.0.25 to %MWxy.0.56 parameter adjustment
Explicit exchange object: Status %MWxy.MOD.2:Xj
Page
258 35012326 00 July 2006
Bits and words associated with the AS-i function
Implicit exchange objects associated with the AS-i function
At a Glance
Bit objects
Address
%Ixy.0.ERR
%Ixy.MOD.ERR
%Ixy.0
%Ixy.0.i
%I\xy.0\.n.i
%Q\xy.0\.n.i
%Qxy.0
%Qxy.0.i
In each task cycle where the AS-i function has been configured, these objects are exchanged automatically.
The table below shows the different implicit exchange bit objects.
Function
Channel fault bit
Module fault bit
Validity of input
Reserved input channel bit output channel bit
Reserved
Reserved
Meaning when bit is on 1
Indicates a power supply fault or a slave is missing on the AS-i bus.
Indicates that the module has a fault.
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.
-
Indicates that the input channel i of device n is activated.
-
-
Indicates that the output channel i of device n is activated.
Word objects
Address
%IWxy.0
%IWxy.0.1
%IWxy.0.2
%IWxy.0.3
The table below shows the different implicit exchange word objects.
Function
List of faulty slaves
List of activated slaves (LAS)
Meaning for Xj = 1 (j = position of bit in the word) j = 0 to 15 -> slaves 0 to 15 respectively are faulty or missing.
j = 0 to 15 -> slaves 16 to 31 respectively are faulty or missing.
j = 0 to 15 -> slaves 0 to 15 respectively are activated.
j = 0 to 15 -> slaves 16 to 31 respectively are activated.
35012326 00 July 2006
259
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
Description
These word type objects carry information about the module or channel exchanges in progress.
They are updated automatically by the system.
The following table provides the meaning of the different bits of the word
%MWxy.MOD.0
.
Address
%MWxy.MOD.0:X0
%MWxy.MOD.0:X1
Meaning for Xj =1
Exchange of status words in progress on the module channel.
Exchange of command words in progress on the module channel.
Description
Example
The following table provides the meaning of the different bits of the word
%MWxy.i.0
.
Address
%MWxy.0.0:X0
%MWxy.0.0:X1
Meaning for Xj =1
Exchange of status words in progress on the AS-i channel.
Exchange of command words in progress on the AS-i channel.
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.
260 35012326 00 July 2006
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
Description
These word type objects carry information about the module or channel exchange reports.
They are updated automatically by the system.
The following table provides the meaning of the different bits of the word
%MWxy.MOD.1
.
Address
%MWxy.0.1:X0
%MWxy.0.1:X1
Meaning for Xj =1
Status parameter exchange error on channel 0 of the module.
Command parameter exchange error on channel 0 of the module.
Description
Example
The following table provides the meaning of the different bits of the word
%MWxy.i.1
.
Address
%MWxy.0.1:X0
%MWxy.0.1:X1
Meaning for Xj =1
Status parameter exchange error on the AS-i channel.
Command parameter exchange error on the AS-i channel.
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;
35012326 00 July 2006
261
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: z READ_STS (reading of status words), z z z z z
WRITE_CMD (writing the command words),
WRITE_PARAM (writing the adjustment words),
READ_PARAM (reading the adjustment parameters),
SAVE_PARAM (saving the adjustment parameters),
RESTORE_PARAM (restoring the adjustment parameters).
262 35012326 00 July 2006
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 word %MWxy.0.2
The table below provides the meaning of the different bits of the word
Address Function
%MWxy.0.2:X0 Standard status
%MWxy.0.2:X1
%MWxy.0.2:X2
%MWxy.0.2:X3
%MWxy.0.2:X4
%MWxy.0.2:X5
%MWxy.0.2:X6
%MWxy.0.2:X7
%MWxy.0.2
Meaning for Xj = 1
Reserved
One or several slaves are faulty.
Line error (power supply off or faulty terminal block).
Physical configuration different from PL7 configuration.
Internal software error.
Reserved
Error communicating with processor
Command or parameter configuration fault.
.
Description of word %MWxy.0.3
The table below provides the meaning of the different bits of the word
Address Function
%MWxy.0.3:X0 AS-i specific status
%MWxy.0.3:X1
%MWxy.0.3:X2
%MWxy.0.3:X3
%MWxy.0.3:X4
%MWxy.0.3:X5
%MWxy.0.3:X6
%MWxy.0.3:X7
%MWxy.0.3:X8
Meaning for Xj = 1
Correct configuration.
Slave 0 present.
Automatic addressing enabled.
Reserved
Reserved
Reserved
Faulty AS-i power supply.
Offline phase active.
Reserved
%MWxy.0.3
.
35012326 00 July 2006
263
Bits and words associated with the AS-i function
Description of words
%MWxy.0.4 and
%MWxy.0.5
Address
%MWxy.0.4:Xj
%MWxy.0.5:Xj
The table below provides the meaning of the different bits of words
%MWxy.0.5
.
%MWxy.0.4
Function Meaning for Xj = 1
List of detected slaves LDS j = 0 to 15 -> slaves 0 to 15 respectively have been detected.
j = 0 to 15 -> slaves 16 to 31 respectively have been detected.
and
Description of words
%MWxy.0.6 to
%MWxy.0.21
Address
%MWxy.0.6 to
%MWxy.0.21
The table below provides the meaning of the different bits of words
%MWxy.0.21
.
Function
I/O configuration and ID of all detected slaves
%MWxy.0.6
Meaning
Words 6 to 21 -> devices respectively 0-1, 2-3, ... 28-29, 30-31.
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.
to
Description of word
%MWxy.0.22
Address
%MWxy.0.22
The table below provides the meaning of the word
Function
Parameter data of last parametered slave.
%MWxy.0.22
.
Meaning
Contains the reply (value of parameters sent) of the last parametered slave. This is so that the PL7 can check the slave has correctly received these values.
Description of word
%MWxy.0.23
Address
%MWxy.0.23
The table below provides the meaning of the word %MWxy.0.23
.
Function
Address of last parametered slave.
Meaning
Contains the address of last parametered slave.
264 35012326 00 July 2006
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. 275 ) or Data exchange off mode (See
AS-i data exchange off
operating mode, p. 276 ) of the AS-i master.
Note: Using this object requires a thorough knowledge of AS-i communication principles.
Description
0
1
1
The table below shows the coding of bits 0 to 3 of the word %MWxy.0.24
allowing access to the different modes.
0
0
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
1
0
1
Disabling offline mode
No effect
1
0
1
0
0
1
0
0
1
Activation of data exchange off mode
Disabling data exchange off mode
No effect
Note: Offline mode has priority over data exchange off mode.
35012326 00 July 2006
265
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
%MWxy.0.25
Parameter adjustment
%MWxy.0.26 to
%MWxy.0.56
Meaning no meaning
Contain the parameter values for slaves 1 to 31 respectively.
266 35012326 00 July 2006
Bits and words associated with the AS-i function
Explicit exchange object: Status %MWxy.MOD.2:Xj
At a Glance
Description
This word type object provides information on the state of the module.
The table below provides the meaning of the different bits of the word
%MWxy.MOD.2:Xj .
Address Function
%MWxy.MOD.2:X0 Standard module status
%MWxy.MOD.2:X1
%MWxy.MOD.2:X2
%MWxy.MOD.2:X3
%MWxy.MOD.2:X4
%MWxy.MOD.2:X5
%MWxy.MOD.2:X6
%MWxy.MOD.2:X7
Meaning for Xj = 1
Internal error.
Configuration fault.
Line fault.
Not used.
Not used.
Not used.
Module missing.
Not used.
35012326 00 July 2006
267
Bits and words associated with the AS-i function
268 35012326 00 July 2006
AS-i operating mode
14
At a Glance
Subject of this
Chapter
What's in this
Chapter?
This Chapter introduces the different AS-i function operating modes.
This chapter contains the following topics:
Topic
AS-i operating mode: General
AS-i protected mode
AS-i wiring test mode
AS-I offline operating mode
AS-i data exchange off operating mode
Page
35012326 00 July 2006
269
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: z z protected mode, wiring test mode (can be accessed using the button on the front panel of the z z module), offline mode, data exchange off mode.
270 35012326 00 July 2006
Operating mode The figure below shows the general schema of AS-i bus functioning.
AS-i operation
Offline mode
Start
AS-i master module
No Activate wiring test
Yes
No
Is the master configured?
Yes
Offline mode
Wiring test mode
Protected mode
(1)
Slave I/O display (2)
Automatic AS-i 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. 275
ou AS-i data exchange off operating
(2) : The module exits the wiring test mode and passes to protected mode if it receives a configuration.
35012326 00 July 2006
271
AS-i operation
Correspondence between PLC operating modes and the AS-i bus
The table below shows the correspondence between TSX/PMX/PCX 57 PLC operating modes and those of the AS-i bus.
PLC
Configured mode (1)
AS-i bus
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.
272 35012326 00 July 2006
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: z continually checks that the list of detected slaves is the same as the list of expected slaves.
z 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 activating a slave
The schema below show the principle of activating AS-i slaves.
PL7 AS-i Module
List of slaves expected LPS
List of slaves detected LDS
Comparison
List of slaves activated LAS
35012326 00 July 2006
273
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: z z expected and detected slaves, unexpected and non-detected slaves, z 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 conditions
The wiring test mode is an AS-i function which can be accessed when: z the TSX SAY 100 module is in non-configured mode.
This mode is obtained when: z the TSX SAY 100 module has not been declared in the application, z z z the PLC processor is missing.
each device has a unique address,
0 address is not used.
274 35012326 00 July 2006
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
Procedure
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.
The offline operating mode can be accessed either: z from PL7 application software by acting on bits 0 and 1 of the word %MWxy.0.24, z 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.
35012326 00 July 2006
275
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
Procedure
When the offline data exchange mode is engaged, exchanges on the bus continue to function, but data is not longer refreshed.
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.
276 35012326 00 July 2006
AS-i performance
15
AS-i bus performance
At a Glance
AS-i scanning time
AS-i response time
Example
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).
t scanning time represents the exchange time between the master and n slaves
(31 maximum).
Either: z t = 156 micro seconds x (n+2), if n < 31, z t = 156 micro seconds x (n+1), if n = 31.
Thus the scanning time cannot exceed 5 ms.
T response time represents the AS-i cycle time.
This includes: z the bus scanning time, z z the update of the AS-I module internal memory, the PLC cycle.
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
10 ms
30 ms
60 ms
Typical response time
35 ms
65 ms
110 ms
Maximum response time
56 ms
96 ms
156 ms
277
35012326 00 July 2006
AS-i performance
278 35012326 00 July 2006
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. 353
).
35012326 00 July 2006
279
DFB AS-i
280 35012326 00 July 2006
AS-i V2 bus
IV
At a Glance
Aim of this Part
What's in this
Part?
This part presents the AS-i V2 bus on PLC TSX/PCX 57 and describes its implementation with the software PL7 Junior and Pro.
This part contains the following chapters:
Chapter
17
18
19
20
21
22
23
Chapter Name
General introduction to the AS-i V2 Bus
AS-i V2 bus configuration
Debugging the AS-i V2 bus
Bits and words associated with the AS-i V2 function
AS-i V2 operating mode
AS-i V2 performance
DFB for AS-i Security Monitor
Page
281
35012326 00 July 2006
AS-i V2 bus
282 35012326 00 July 2006
General introduction to the AS-i V2 Bus
17
At a Glance
Aim of this chapter
What's in this
Chapter?
This chapter introduces the AS-i V2 bus on the Premium/Atrium PLC, and describes how to access the different application editors.
This chapter contains the following topics:
Topic
Introduction to the AS-i V2 Bus
Architecture of TSX SAY 1000 Module
Structure of a Standard Address AS-i
Structure of a Standard Address AS-i slave
How to Declare an AS-i Communication Module in the PLC Rack
How to Access Configuration of the AS-i V2 Bus
Page
283
35012326 00 July 2006
AS-i V2 Bus
Introduction to the AS-i V2 Bus
Introduction
AS-i V2 Bus
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: z either in local mode, z or in connected mode; in this case the modification is limited to certain parameters.
The coupler TSX SAY 1000 integrates the functions AS-i V2.
The AS-i bus then allows: z up to 62 standard and/or extended address slaves, z z z up to 248 inputs and 186 outputs, up to 124 analog values integrated in the master AS-i, a cycle time of 10ms maximum.
284 35012326 00 July 2006
AS-i V2 Bus
Implementation
Mode
Local
Local or connected
Connected
Local or connected
The following table shows the different implementation phases of the AS-i bus.
Phase
Declaration of module
Description
Selection of slot for TSX SAY 1000 module in the rack.
Declaration of slave devices Selection for each device: z z of its slot number on the bus, of the type of standard or extended address slave
Input of the configuration parameters.
Configuration of the module channel (See AS-i V2 bus
)
Confirmation of module level.
Confirmation of configuration parameters
(See Confirming the configuration of a module.,
)
Global confirmation of the application (See Globally reconfiguring an
Confirmation of application level.
Symbolization
Programming
Transfer
Debugging
Symbolization of the variables associated with the slave devices.
Programming the functions carried out using the AS-i V2 bus.
Transfer of the application to the PLC.
Debugging the application using: z z the debugging help screens which display the slave connections, their parameters, etc.
diagnostic screens allowing identification of errors.
Documentation Printing the different information relating to the application.
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.)
35012326 00 July 2006
285
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: z
Profile M0 and M0e - Minimum Master: the master only puts forward the z configuration of slaves connected to the bus on power-up, and only input/output exchanges.
Profile M1 and M1e - Full Master: this profile covers all the operating functions set by the AS-i standard, z
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 architecture
The figure below shows the TSX SAY 1000 module architecture.
TSX SAY 1000
1 I/O data
2
3
4
5
6
7
Parameters current
Configuration/
Identification
LDS
LAS
LPS
LPF
AS-i bus
286 35012326 00 July 2006
Description of constituent elements
AS-i V2 Bus
The table below shows the different elements that make up the architecture of the
TSX SAY 1000 module.
4
5
6
2
3
Number Element
1 I/O data
Current parameters
Configuration/
Identification
LDS
LAS
LPS
7 LPF
Description
Images of 248 inputs and 186 outputs of AS-i V2 bus.
Image of parameters of all slaves.
This field contains all the I/O codes and identification codes for all the detected slaves.
List of all the slaves detected on the bus.
List of active slaves on the bus.
List of slaves expected on the bus and configured by
PL7.
List of slaves having a device fault.
35012326 00 July 2006
287
AS-i V2 Bus
Structure of a Standard Address AS-i
At a Glance
Structure illustration
The AS-i V2 bus is used to interconnect 31 standard address devices.
The standard address slaves each have: z z
4 input bits,
4 output bits, z
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).
The figure below shows the structure of a standard address slave.
AS-i slave
1 I/O data
D3
D0
2 Parameters
P3
P0
3
Configuration/
Identification
AS-i bus
4 Address
288 35012326 00 July 2006
Description of constituent elements
AS-i V2 Bus
The table below shows the different elements that make up the structure of a standard address slave.
Number Element
1 Input/output data
2
3
4
Parameters
Configuration/
Identification
Address
Description
Input data is stored by the slave and made available for the AS-i master.
Output data is updated by the master module.
The parameters are used to control and switch internal operating modes to the sensor or the actuator.
This field contains: z z the code which corresponds to I/O configuration, the slave identification codes (ID, ID1, ID2).
Physical address of slave.
Note : The operating parameters, address, configuration and identification data are saved in a non-volatile memory.
35012326 00 July 2006
289
AS-i V2 Bus
Structure of a Standard Address AS-i slave
At a Glance
Structure illustration
The extended AS-i V2 bus is used to interconnect 62 extended address devices.
The extended address slaves each have: z z
4 input bits,
3 output bits, z
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).
The figure below shows the structure of an extended address slave.
AS-i slave
(D3)
Input Bit Only
1 I/O data
D0
2 Parameters
P2
P0
3
Configuration/
Identification
AS-i bus
4 Address
290 35012326 00 July 2006
Description of constituent elements
AS-i V2 Bus
The table below shows the different elements that make up the structure of an extended address slave.
Number Element
1 Input/output data
2
3
4
Parameters
Configuration/
Identification
Address
Description
Input data is stored by the slave and made available for the AS-i master.
Output data is updated by the master module.
The parameters are used to control and switch internal operating modes to the sensor or the actuator.
This field contains: z z z the code which corresponds to I/O configuration, the slave identification (ID) code, the slave identification codes (ID1 and ID2).
Physical address of slave.
Note : The operating parameters, address, configuration and identification data are saved in a non-volatile memory.
35012326 00 July 2006
291
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
1
Action
Double click on the required position in the rack displayed.
Result : The dialog box Add a module appears:
Add a module
Family:
Analog
Communication
Upcounting
Movement
Weighing
Alternating
1.5
1.5
1.5
1.5
1.7
1.5
Module:
TSX SAY1000
TSX SCY 21600
TSX SCY 21601
AS-Interface MODULE
PCMCIA HOST MODULE
PCMCIA HOST MODULE
OK
Cancel
292
2
3
4
Select the choice Communication in the Family field.
Select in the Module field the reference of the module.
Confirm the selection with OK .
Result : The module is declared in its slot; this turns yellow and contains the module reference.
Configuration
TSX 57303 V5.0...
XMWI
XTI..
0
0 1 2 3 4 5
3
6
0
0
0
Y
1
S
A
Note : The maximum number of TSX SAY 1000 modules which can be installed in a configuration is: z z z
2 modules , with a TSX/PMX/PCX 57-1• processor,
4 modules , with a TSX/PMX/PCX 57-2• processor,
8 modules , with a TSX/PMX/PCX 57-3• , TSX/PMX 57-4• processor.
35012326 00 July 2006
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
1
Action
Access the Hardware configuration screen
Result : The rack’s hardware configuration screen appears.
Configuration
TSX 57303 V5.0...
XMWI
XTI..
0 1 2 3 4 5 6
0
35012326 00 July 2006
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
AS-interface V2 configuration
Automatic addressing
Std/A Slaves /B Slaves
XVBC21A P
5
6
3
4
7
8
9
0
1
2
10
11
12
13
14
P ASIME4IE
MAST
Slave 2B
Specifications
Profile:
Comment
Parameters
0 Unused
IO 0 ID a ID2 0 ID1
4 input extended addr. Module
2 Unused
1 Unused 0
0
Input / Output Symbols
Input Number
3
4
1
2
Output
3
4
1
2
%I\1.0\102.0
%I\1.0\102.1
%I\1.0\102.2
%I\1.0\102.3
Number
Not handled
Not handled
Not handled
Not handled
Symbol
Symbol
Not handled
Not handled
Not handled
Not handled
293
AS-i V2 Bus
294 35012326 00 July 2006
AS-i V2 bus configuration
18
At a Glance
Subject of this
Chapter
What's in this
Chapter?
This Chapter describes the Configuration aspect for installing the AS-i V2 bus.
This chapter contains the following topics:
Topic
Description of an AS-i V2 communication module’s configuration screen
How to define a slave device on the AS-i V2 bus
How to modify the AS-i V2 Bus software configuration
How to access the description of an AS-i V2 slave
How to define a new slave profile in the standard AS-i V2 catalog
How to modify the general parameters of an AS-i V2 slave: Automatic addressing
How to modify the parameters of an AS-i V2 slave
How to modify the parameters of an analog AS-i V2 slave
How to Modify the Parameters of an AS-i V2 Slave with Combined Parameters
AS-i V2 security device issues
Page
35012326 00 July 2006
295
AS-i V2 bus configuration
Description of an AS-i V2 communication module’s configuration screen
At a Glance
Illustration
The configuration screen of the AS-i V2 module gives access to the parameters associated with the module and the slave devices.
This screen allows the display and modification of the parameters in local mode, as well as Debugging in connected mode.
1
2
3
4
TSX SAY 1000 [RACK 0 POSITION 1]
Configuration
Designation: AS-interface V2 Module
Channel 0:
Channel 0
AS-interface V2 Bus
AS-interface V2 configuration
Automatic addressing
Std/A Slaves /B Slaves
XVBC21A P
10
11
8
9
6
7
12
13
14
3
4
5
0
1
2 P ASIME4IE
MAST
Slave 2B
Specifications
Profile:
Comment
Parameters
0 Unused
IO 0 ID a ID2 0 ID1
4 input extended addr. Module
2 Unused
1 Unused 0
0
Input / Output Symbols
Input Number
1
2
3
4
Output
1
2
3
4
%I\1.0\102.0
%I\1.0\102.1
%I\1.0\102.2
%I\1.0\102.3
Number
Not handled
Not handled
Not handled
Not handled
Symbol
Symbol
Not handled
Not handled
Not handled
Not handled
5
6
7
296 35012326 00 July 2006
AS-i V2 bus configuration
Description
1
2
Number Element
Module
Title bar
Command
The following table shows the different elements of the configuration screen and their functions.
Function
Indicates the reference of the selected module and its physical position in the rack.
Allows the selection of the parameter type: z Configuration , z 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 .
3
AS-i V2 bus
Channel 0
4 AS-interface V2 configuration
Allows selection of the task in which the information from the AS-i communication channel will be scanned: z MAST Task, z FAST Task.
Display of this zone is optional. The choice is made using the command View →
Channel zone .
Allows: z Viewing standard and extended address setting slave devices connected to the z z bus, definition of a new configuration (adding, modifying or detecting slave devices).
Selecting automatic addressing mode
5
Slave
Specifications
6
7
Parameters
Input / Output
Symbols
Allows viewing of: z z
Slave profile
Comments on the selected slave
Allows display and selection of parameters applied to the selected slave. The parameters displayed differ according to the type of slave selected.
For example: z Watchdog z Fallback Position
Allows data associated with the selected slave to be displayed, such as: z its AS-i symbol (the symbols are defined with the help of the variables editor), z Its label (or address) which can be used in the program
35012326 00 July 2006
297
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: z z z z z z z z z z z z z z z
Keyboards
Illuminated columns
Command and signaling
AS-i modules and interfaces
Motor-starters
Inductive sensors
Phototronic sensors
Private family
IP20 linkage interfaces
Position switches
Analog modules
Security modules
Logical modules
IP67 Distributors
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.
298 35012326 00 July 2006
Procedure
35012326 00 July 2006
AS-i V2 bus configuration
This operation enables the declaration of a slave device on the AS-i V2 bus.
Step
1
2
Action
Access the AS-i module’s hardware configuration screen.
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.
7
8
4
5
6
Associate a profile
Families of AS-interface profiles
Code ASI Family Name
Keyboards
Illuminated columns
Command and signaling
AS-i Modules and Interfaces
Motor-starters
Catalog of AS-interface profiles
ASI Name @ Comment
Consult
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
15
16
14
10
13
Code ASI Family Name
12345678 Analog Modules
Security modules
Logical modules
IP67 Distributors
Variable speed controllers
Consult ASI Catalog: IP67 Distributors
0.0.F.F
0.0.F.F
0.A.0.0
0.A.0.0
3,0.F.F
ASI Name
XZ-SDA40D2
XZ-SDA40D3
ASIME4IE
ASIMM04IE
XZ-SDA22D11
@ std std
A/B
A/B std
Comment
4 E 100 mA User Module
4 I 200 mA User Module
4 input extended addr. Module
Mini mod. 4 input extended addr
2I/2O rel. M12 User Module
Add
Modify
Delete
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).
299
AS-i V2 bus configuration
Step
4
5
6
Action
In the Profile catalogue select the required device.
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
8
9
6
7
10
11
12
13
14
0
3
4
1
2
5
P ASIME4IE
To connect other slave devices to the AS-i V2 bus, repeat the procedure from step 2.
300 35012326 00 July 2006
Configuration
Rules
AS-i V2 bus configuration
The configuration rules for the slaves are as follows: z
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.
The std /A Slaves column can support extended address slaves. This column z 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).
35012326 00 July 2006
301
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 deleting a slave
This operation allows the deletion of a slave declared on an AS-i Bus.
Step
1
2
Action
Select the slave to be deleted.
Select the command Edit → Delete an AS-i slave .
Procedure for moving a slave
This operation allows a slave declared on an AS-i V2 Bus to be moved.
Step
1
2
3
4
Action
Select the slave to be moved.
Select the command Edit → Cut an AS-i slave .
Select the new required slot.
Select the command Edit → Paste an AS-i slave .
Procedure for copying a slave
This operation allows the copying of a slave declared on an AS-i V2 Bus.
Step
1
2
3
4
Action
Select the slave to be copied.
Select the command Edit → Copy an AS-i slave .
Select the slot of the new slave.
Select the command Edit → Paste an AS-i slave .
302 35012326 00 July 2006
AS-i V2 bus configuration
How to access the description of an AS-i V2 slave
At a Glance
Definition of a profile
The PL7 software allows access to all the information relating to an AS-i V2 device such as: z z the definition of a profile, the details of a profile.
A profile is defined by: z z its name, a comment (optional), z z z identifiers (IO, ID, ID1, ID2), a number of inputs and/or outputs, operation parameters.
Note: profile description for Private Family products is not accessible.
Details of a profile
The Detail function allows access, for a given slave, to all the information presented 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:
AS-i profile:
I/O Configuration:
Telemechanics
0.0
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
35012326 00 July 2006
303
AS-i V2 bus configuration
Procedure for accessing information on a profile
The following table shows the procedure for displaying the characteristics of a slave device.
Step
1
2
3
4
Action
Access the AS-i V2 module’s hardware configuration screen.
Double click on the required slave.
Result: The Associate a profile window displays and highlights the device in question.
Select the profile family and the reference for the desired slave.
Click on the button: z View to access definition information, z Detail to access all the information.
304 35012326 00 July 2006
AS-i V2 bus configuration
How to define a new slave profile in the standard AS-i V2 catalog
At a Glance
Procedure
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.
The following table presents the procedure for defining a slave profile, which is not provided in the standard catalog.
Step
1
2
3
Action
Access the AS-i module’s hardware configuration screen.
Double click in a slave’s host cell (1 to 31 /A or /B).
Result : The Associate a profile screen appears.
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
9
1
12
3
15
Code ASI Family Name
Phototronic sensors
Private family
Connection interfaces IP20
Position switches
12345678 Analog Modules
ASI Catalog: Private family
1.1.F.1
1.A.1.1
ASI Name
Sens 1I 4O
Test
@ std
A/B
Special Sensor
Test
Comment
Consult
Add
Modify
Delete
Detail
Ok Cancel
35012326 00 July 2006
305
AS-i V2 bus configuration
Step
4
5
6
7
8
Action
Click on the Add button.
A new AS-interface profile definition window opens.
Enter: z the name of the new profile, z a comment (optional).
Select: z the IO code (corresponds to the input/output configuration), z the ID code (identifier) (plus ID1 and for an extended type),
For each parameter define: z the system’s acknowledgement (box checked), z a label (optional).
Confirm the introduction of a new profile using Confirm .
306 35012326 00 July 2006
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: z z replacing a faulty slave (See Automatic replacement of a faulty AS-i V2 slave,
inserting a new slave (See How to insert a slave device into an existing AS-i V2
).
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
1
2
Action
Access the AS-i V2 communication module’s configuration screen.
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.
35012326 00 July 2006
307
AS-i V2 bus configuration
How to modify the parameters of an AS-i V2 slave
At a Glance
Example of parameters
Procedure
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.
On certain slaves, the following may be activated: z z z
The internal watchdog , upon a communication stop with the (TSX SAY 1000) bus master.
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: z
Fallback to 0 : the outputs ofAS-i slaves present on the bus are set to 0 status.
Maintain status : AS-i slave outputs remain in the status they were in before
STOP mode was engaged.
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
1
2
3
Action
Access the AS-i V2 communication module’s configuration screen.
Select the slave whose parameters are to be modified.
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
308 35012326 00 July 2006
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: z z
Filter Selection , which activates la rejection of 50/60 Hz on inputs.
Channel 2 Enabling , which enables the second analog channel.
z
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.
Procedure
Note: Module TSX SAY 1000 can only manage 7.3
type analog slaves.
The following table shows the procedure for defining the parameters of an analog slave device.
Step
1
2
3
Action
Access the AS-i V2 communication module’s configuration screen.
Select the slave whose parameters are to be modified.
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
1 Conf. Channel 2
2
3
Peri. Flt. Conf
Unused
35012326 00 July 2006
309
AS-i V2 bus configuration
How to Modify the Parameters of an AS-i V2 Slave with Combined Parameters
At a Glance
Procedure
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.
The table below shows the procedure for selecting the parameters of the slave devices with combined parameters.
Step
1
2
3
Action
Access the configuration screen of the AS-i V2 communication module.
Select the slave whose parameters are to be modified.
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
310 35012326 00 July 2006
AS-i V2 bus configuration
AS-i V2 security device issues
At a Glance
Precautions of
Use
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. 298 ).
Input/Output objects from these devices should not be used in the application 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.
35012326 00 July 2006
311
AS-i V2 bus configuration
312 35012326 00 July 2006
Debugging the AS-i V2 bus
19
At a Glance
Aim of this chapter
What's in this
Chapter?
This Chapter describes the Debug aspect of the AS-i V2 bus.
This chapter contains the following topics:
Topic
Introduction to the Debug function
Description of an AS-i V2 module's debugging screen
How to access module- and channel-diagnostics functions on an AS-i V2 device.
Displaying the slaves' status
How to access adjustment of an AS-i V2 device's parameters
How to access the AS-i V2 digital channels' forcing/unforcing function
How to access the SET and RESET commands on AS-i V2 digital channels
How to modify the value of an analog channel
Automatic replacement of a faulty AS-i V2 slave
How to insert a slave device into an existing AS-i V2 configuration.
How to modify the address of an AS-i V2 device
Page
35012326 00 July 2006
313
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: z z to display slave status (connection, parameters etc.), 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.
314 35012326 00 July 2006
Debugging the AS-i V2 bus
Description of an AS-i V2 module's debugging screen
At a Glance
Illustration
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.).
This is the layout of the debugging screen:
4
1
2
3
TSX SAY 1000 [RACK 0 POSITION 5]
Debugging
Designation: AS-Interface V2 MODULE Version: 0.1
RUN ERR
Channel 0: Maestro
Channel
AS-interface V2 BUS
AS-interface V2 configuration
Automatic addressing
Std/A Slaves /B Slaves
Ext I/O Module
XZ-SDA22D12
Ext I/O Module
XZ-SDA22D12
XZ-SDA22D12
XZ-SDA22D12
XZ-SDA22D12
Analog B&W 2IN
Analog B&W 2IN
Ext I/O Module
XZ-SDA22D12
Ext I/O Module
XZ-SDA22D12
XZ-SDA22D12
20
21
22
23
24
25
26
27
17
18
19
14
15
16 Ext I/O Module
Ext I/O Module
Ext I/O Module
MAST
Slave 21A
%I
Parameters (3-0)
Value: 0111
%Q
Profile
Projected:
Detected:
IO
IO
IO
DIAG...
7
7
ID
ID
DIAG...
3
3
Ch.
1
2
3
0
2
3
0
1
Asi Symbol
Format: Decimal
Status
0
0
0
0
0
0
10000
0
ID2
ID2 d d
Modif PARAM
ID1
ID1 f f
Action channel 0
Change value
Global unforcing
5
35012326 00 July 2006
315
Debugging the AS-i V2 bus
Description
Number Element
1 Title bar
2
3
4
Module zone
The following table shows the different elements of the debugging screen and their functions.
Channel zone
Function
Indicates the reference of the selected module and its physical position in the
PLC.
Allows parameter type to be selected: z z
Configuration ,
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).
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).
Displays the slave devices connected to the bus.
5
Configuration Zone
AS-interface V2
Slave zone Displays the status of the slave’s channels and gives access to the debugging functions.
316 35012326 00 July 2006
Debugging the AS-i V2 bus
How to access module- and channel-diagnostics functions on an AS-i V2 device.
At a Glance
Procedure for accessing the module diagnostics
The functions of the module or channel diagnostics display the current errors in which are classed according to category: z
internal errors (internal software errors, communication error with the processor, configuration, parameter or command error), z z external errors(slave device failed, AS-i power supply switched off, terminal error, difference between physical configuration and PL7 configuration), other errors (module absent or switched off).
A faulty module becomes apparent when certain LEDs change to red, e.g.: z in the configuration editor at rack level: z z the module position LED, in the configuration editor at module level: z z the RUN , ERR and I/O LEDs, the DIAG LED.
A faulty channel becomes apparent when certain lights change to red, such as: z in the configuration editor at rack level: z the module position LED, z in the configuration editor at channel level: z the DIAG LED.
The following table shows the procedure to access the Module diagnostics screen.
Step
1
2
Action
Access the AS-i module’s hardware configuration screen.
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
35012326 00 July 2006
317
Debugging the AS-i V2 bus
Procedure for accessing channel diagnostics
The following table shows the procedure for accessing the Channel diagnostics screen.
Step
1
2
Action
Access the AS-i module’s hardware configuration screen.
Click on the DIAG button located in the channel zone.
Result : The list of channel errors appears.
Diagnostics Channel
Internal faults External faults
Slave error
Inconsistency with logical and physical configuration
Other faults
Data Exchange inactive on
AS-i bus
OK
318 35012326 00 July 2006
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.
35012326 00 July 2006
319
Debugging the AS-i V2 bus
Displaying slave status
Illustration
AS-interface V2 configuration
Faulty Slave: red "LED"
Std/A Slaves
12
13
14
9
10
7
8
11
5
6
3
4
0
1
2
/B Slaves
4I/3O
Slave valid
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
Diagnostics
Detected profile differs from configured profile f
Close
The Slave Diagnostics window displays the following faults for each slave device: z z
A configured profile is specified but no slave is detected.
A profile is detected but there is no configured slave profile.
z z
A profile is detected but a different profile is specified in configuration (I/O, ID, ID1 or ID2).
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.
320 35012326 00 July 2006
How to access adjustment of an AS-i V2 device's parameters
Debugging the AS-i V2 bus
At a Glance
Procedure
The debugging screen of an AS-i V2 module allows the user, amongst other things, to modify a slave’s parameters.
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
Detected: IO
Parameters (3-0)
Value: 1111
3
3
ID
ID f f ID2
ID2 f f
Modif PARAM
ID1
ID1 f f
%I
Action channel 0
F4 Force to 0
%Q
Ch.
1
2
3
0
2
3
0
1
Asi Symbol
Not handled
Not handled
Not handled
Not handled
Format: Decimal
0
0
0
0
Status
F5
F6
F7
F8
Force to 1
Unforce
Set
Reset
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
1 Unused
2
3
Unused
Unused
Send Cancel Input
4 Selecting and omitting parameters.
5 Click on Send to recognize the new values.
C lose
35012326 00 July 2006
321
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
322 35012326 00 July 2006
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: z for a channel: z z z z forcing to 0 forcing to 1 z unforcing.
for all channels (when at least one channel is forced): 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
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 table.
Result : The channel can be modified using the buttons situated in the Action channel field.
Action for all channels
Click on the Global unforcing button located in the slave zone.
%I
%Q
Ch.
2
3
0
1
0
1
2
3
Asi Symbol
Not handled
Not handled
Not handled
Not handled
Format: Decimal
0
0
0
0
Status
Action channel 0
F4 Force to 0
F5 Force to 1
F6
F7
F8
Unforce
Set
Reset
Global unforcing
4 Select the required function (buttons Force to 0 or Force to
1 ) in the Channel Action field.
35012326 00 July 2006
323
Debugging the AS-i V2 bus
How to access the SET and RESET commands on AS-i V2 digital channels
At a Glance
Procedure
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.
The table below shows the procedure for assigning a value of 0 or 1 to the selected
AS-i V2 slave’s channels.
Step
1
2
3
Action
Access the AS-i V2 module’s debugging screen.
Select a slave in the AS-interface V2 Configuration zone.
Select the channel to be modified in the Slave zone table.
Result : The channel can be modified using the buttons situated in the Action channel field.
4
%I
%Q
Ch.
0
1
2
3
0
1
2
3
Asi Symbol
Not handled
Not handled
Not handled
Not handled
Format: Decimal
0
0
0
0
Status
Action channel 0
F4 Force to 0
F5 Force to 1
F6
F7
F8
Unforce
Set
Reset
Global unforcing
Select the required function (buttons Set or Reset ) in the Channel action field.
324 35012326 00 July 2006
Debugging the AS-i V2 bus
How to modify the value of an analog channel
At a Glance
Procedure
This function allows the values of channels linked to an AS-i V2 analog slave to be modified.
The following table shows the procedure for modifying the value of an AS-i V2 slave's analog channel.
Step
1
2
3
Action
Access the AS-i V2 module’s debugging screen.
Select an analog slave in the AS-interface V2 Configuration zone.
Select the channel whose value you wish to modify from the Slave zone.
%I
%Q
Ch.
2
3
0
1
0
1
2
3
Asi Symbol
Format: Decimal
Status
0
0
0
0
0
0
10000
0
Action channel 0
Change value
Global unforcing
4 Click on the Change Value button.
Result : the following window appears:
Analog I/O
Slave 21A / Channel 0
Value decimal:
10000
5
OK
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.
35012326 00 July 2006
325
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
Two options are available: z
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 z of active slaves (LAS),
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).
326 35012326 00 July 2006
Debugging the AS-i V2 bus
How to insert a slave device into an existing AS-i V2 configuration.
At a Glance
Procedure
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: z the configuration mode's Automatic addressing utility is active (See How to z z modify the general parameters of an AS-i V2 slave: Automatic addressing,
a single slave is absent in the physical configuration, the slave which is to be inserted is specified in the PL7 configuration, z z the slave has the profile and sub-profile expected by the configuration, 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.
The following table shows the procedure for making the automatic insertion of a new slave effective.
Step
1
2
3
Action
Add the new slave in the configuration screen in local mode.
Carry out a configuration transfer to the PLC in connected mode.
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.
35012326 00 July 2006
327
Debugging the AS-i V2 bus
How to modify the address of an AS-i V2 device
At a Glance
Procedure
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.
The following table shows the procedure for modifying the address of an AS-i V2 slave device.
Step
1
2
Action
Access the TSX SAY 1000 module’s debugging screen.
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:
Bank selection:
Addresses available on this bank:
OK Cancel
6
7
4
5
8
2
3
0
1
4B
A
3
4
5
Select bank A or B in the Bank Selection list.
Note : bank B cannot be selected where there is a standard address slave.
Select the required address in the list of Available addresses (use the scroll bar if necessary).
Confirm the selection with OK .
328 35012326 00 July 2006
Bits and words associated with the AS-i V2 function
20
At a Glance
Aim of this chapter
What's in this
Chapter?
This Chapter introduces the different word and bit objects associated with the AS-i
V2 function, as well as how to address them.
This chapter contains the following sections:
Section
20.1
20.2
Topic
Addressing objects associated with the AS-i V2 function
Language objects associated with the AS-i V2 function
Page
329
35012326 00 July 2006
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
Illustration
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.
Reminder of the principle of addressing:
%
Symbol
I, Q, IW, QW
Type of object
\ xy.0
Module address/channel of TSX SAY 1000
0 = channel 0 of module
\ n
Slave no.
i
Bit position
Specific Values The table below gives specific values to AS-i V2 slave objects.
Element n (for bank A) i n (for bank B)
Values
0 to 31
100 to 131
0 to 3
Comment
Slot 0 cannot be configured.
-
Slot 0 cannot be configured.
330 35012326 00 July 2006
20.2
Bits and words associated with the AS-i V2 function
Language objects associated with the AS-i V2 function
At a Glance
Aim of this
Section
What's in this
Section?
This section introduces the different language objects associated with the AS-i V2 function.
This section contains the following topics:
Topic
Implicit exchange objects associated with the AS-i V2 function
Exchange management: Module %MWxy.MOD.0:Xj or channel MWxy.0.0 :Xj exchanges in progress
Exchange management: Module %MWxy.MOD.1:Xj or channel %MWxy.i.1:Xj report
Explicit exchange objects: General
Explicit Exchange Objects: %MWxy.MOD.2 and %MWxy.0.2:Xj to
%MWxy.0.73:Xj channel status
Constant %KWxy.i.r configuration objects
Explicit Exchange Object: %MWxy.0.74:Xj channel command
Explicit Exchange Object: %MWxy.0.75 to %MWxy.0.138 Parameter
Adjustment
Explicit Exchange Object: Status %MWxy.MOD.2:Xj
Page
35012326 00 July 2006
331
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 in which the AS-i V2 function has been configured, these objects are exchanged automatically.
Bit objects
Address
%Ixy.MOD.ERR
%Ixy.0.ERR
%Ixy.0.0
The table below shows the different implicit exchange bit objects.
Function
Module fault bit
Channel fault bit 0
Validity of input
%Ixy.0.1
%I\xy.0\n.i
X Bus communication bit
Digital input channel bit*
%Q\xy.0\.n.i
Digital output channel bit*
*For bank A, n = 0 to 31
*For bank B, n = 100 to 131
Meaning when bit is on 1
Indicates that the AS-i module has a fault.
Indicates a channel 0 fault on the AS-i module
Indicates that all inputs are valid.
Note: When this bit is on 0, it indicates that at least one input is not valid: Offline mode, data exchange off mode, or channel fault.
Indicates a communication error on the X Bus if this bit = 0.
Indicates that the input channel i of device n is activated.
Indicates that output channel i of device n is activated.
332 35012326 00 July 2006
Bits and words associated with the AS-i V2 function
Word objects The table below shows the different implicit exchange word objects.
Address
%IWxy.0.0
%IWxy.0.1
%IWxy.0.2
%IWxy.0.3
%IWxy.0.4
%IWxy.0.5
%IWxy.0.6
%IWxy.0.7
Function
List of standard (A) inactive slaves (/LAS)
List of inactive extended (B) slaves (/LAS)
Peripheral fault (LPF) on standard slaves (A)
Peripheral fault (LPF) on extended slaves (B)
%IWxy.0.8
%IWxy.0.9
%IWxy.0.10
%IWxy.0.11
List of standard (A) active slaves
(LAS)
List of active extended (B) slaves (LAS)
%IW\xy.0\n Analog Input Channel*
%QW\xy.0\n Analog Output Channel*
*For bank A, n = 0 to 31
*For bank B, n = 100 to 131
Meaning for Xj = 1 (j = position of bit in the word) j = 0 to 15 -> respectively standard address slave 0 to 15 inactive.
j = 0 to 15 -> respectively standard address slave 16 to 31 inactive.
j = 0 to 15 -> respectively extended address slave 0 to 15 inactive.
j = 0 to 15 -> respectively extended address slave 16 to 31 inactive.
j = 0 to 15 -> respectively standard address slave 0 to 15 has peripheral fault.
j = 0 to 15 -> respectively standard address slave 16 to 31 has peripheral fault.
j = 0 to 15 -> respectively extended address slave 0 to 15 has peripheral fault.
j = 0 to 15 -> respectively extended address slave 16 to 31 has peripheral fault.
j = 0 to 15 -> respectively standard address slave 0 to 15 active.
j = 0 to 15 -> respectively standard address slave 16 to 31 active.
j = 0 to 15 -> respectively extended address slave 0 to 15 active.
j = 0 to 15 -> respectively extended address slave 16 to 31 active.
Value of input word in analog channel.
Value of output word in analog channel.
35012326 00 July 2006
333
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
Description
These word type objects carry information about the module or channel exchanges in progress.
They are updated automatically by the system.
The table below provides the meaning of the word %MWxy.MOD.0
.
Address
%MWxy.MOD.0:X0
%MWxy.MOD.0:X1
Meaning
Exchange of status words in progress on the module channel.
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
%MWxy.0.0
Meaning
Byte 0
X0: Periodic status reading in progress
X1: Specific command in progress
X2: Setting in progress
X15: configuration in progress
334 35012326 00 July 2006
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
Description
These word type objects carry information about module or channel exchange reports.
They are updated automatically by the system.
The following table provides the meaning of the different bits of the word
%MWxy.MOD.1
.
Address
%MWxy.MOD.1:X0
%MWxy.MOD.1:X1
Meaning
Status parameter exchange error on channel 0 of the module
Command parameter exchange error on channel 0 of the module
Description
Example
The following table provides the meaning of the different bits of the word
%MWxy.i.1
.
Address
%MWxy.0.1
Meaning
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
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;
35012326 00 July 2006
335
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.
z z z z z z
The explicit exchange objects are exchanged at the request of the program user using instructions:
READ_STS (reading of status words),
WRITE_CMD (writing the command words),
WRITE_PARAM (writing the adjustment words),
READ_PARAM (reading the adjustment parameters),
SAVE_PARAM (saving the adjustment parameters),
RESTORE_PARAM (restoring the adjustment parameters),
336 35012326 00 July 2006
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 word %MWxy.0.2
The table below gives the meaning of the different bits of the word
Address Function
%MWxy.0.2:X0 Standard status
%MWxy.0.2:X1
%MWxy.0.2:X2
%MWxy.0.2:X3
%MWxy.0.2:X4
%MWxy.0.2:X5
%MWxy.0.2:X6
%MWxy.0.2:X7
%MWxy.0.2
Meaning for Xj = 1
No meaning
Slave error.
Line error (APF).
Physical configuration different from PL7 configuration.
Internal software fault.
No meaning
Fault communicating with processor
Command or parameter configuration fault.
.
35012326 00 July 2006
337
Bits and words associated with the AS-i V2 function
Description of word %MWxy.0.3
Address
The table below gives the meaning of the different bits of the word
Function
AS-i master status
Meaning for Xj = 1
%MWxy.0.3
.
Byte 0
%MWxy.0.3:X0
%MWxy.0.3:X1
%MWxy.0.3:X2
%MWxy.0.3:X3
%MWxy.0.3:X4
%MWxy.0.3:X5
%MWxy.0.3:X6
%MWxy.0.3:X7
Byte 1
%MWxy.0.3:X0
%MWxy.0.3:X1
Correct configuration.
Slave 0 present on the bus.
Automatic addressing.
Automatic addressing authorized.
Operation in AS-i configuration mode.
Operation in normal mode.
Faulty AS-i power supply.
Offline mode active.
Data exchange inactive.
Peripheral fault on a bus device.
Description of words
%MWxy.0.4 to
%MWxy.0.7
Address
%MWxy.0.4:Xj
%MWxy.0.5:Xj
%MWxy.0.6:Xj
%MWxy.0.7:Xj
The table below gives the meaning of the different bits of words
%MWxy.0.7
.
Function
List of detected slaves in bank A (LDS)
List of detected slaves in bank B (LDS)
%MWxy.0.4
and
Meaning for Xj = 1 j = 0 to 15 -> slaves 0 to 15 respectively have been detected.
j = 0 to 15 -> slaves 16 to 31 respectively have been detected.
j = 0 to 15 -> slaves 0 to 15 respectively have been detected.
j = 0 to 15 -> slaves 16 to 31 respectively have been detected.
338 35012326 00 July 2006
Bits and words associated with the AS-i V2 function
Description of words
%MWxy.0.8 to
%MWxy.0.71
Address
%MWxy.0.8 to
%MWxy.0.39
%MWxy.0.40 to
%MWxy.0.71
The table below gives the meaning of the different bits of words
%MWxy.0.71
.
%MWxy.0.8
Function
I/O configuration and ID of all detected slaves in bank A
I/O configuration and ID of all detected slaves in bank B
Meaning
Words 8 to 39 -> devices 0 to 31 respectively.
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).
Words 40 to 71 -> devices 0 to 31 respectively.
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).
to
Description of word
%MWxy.0.72
Address
%MWxy.0.72
The table below gives the meaning of the word
Function
Parameter data of last parametered slave.
%MWxy.0.72
.
Meaning
Contains the information (value of parameters sent) of the last parametered slave. This is so that the PL7 can check the slave has correctly received these values.
35012326 00 July 2006
339
Bits and words associated with the AS-i V2 function
Description of word
%MWxy.0.73
Address
%MWxy.0.73
The table below provides the meaning of the word %MWxy.0.73
.
Function
Address of last parametered slave.
Meaning
Contains the address of last parametered slave.
Byte 0:
Address of the slave (1 to 31).
Byte 1:
Slave bank:
0 = bank A
1 = bank B.
340 35012326 00 July 2006
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
%KWxy.0.0
%KWxy.0.1:Xj
%KWxy.0.2:Xj
%KWxy.0.3:Xj
%KWxy.0.4:Xj
%KWxy.0.5 à
%KWxy.0.36
%KWxy.0.37 à
%KWxy.0.68
%KWxy.0.69:X0
Function
AS-i master
List of expected slaves in bank A (LDS)
List of expected slaves in bank B (LPS)
I/O configuration and ID of all expected slaves in bank A
I/O configuration and ID of all expected slaves in bank B
Automatic Address
Monitoring
Meaning
When byte 0 = 10, this shows that AS-i is master.
j = 0 to 15 -> expected slaves 0 to 15 respectively.
j = 0 to 15 -> expected slaves 16 to 31 respectively.
j = 0 to 15 -> expected slaves 0 to 15 respectively.
j = 0 to 15 -> expected slaves 16 to 31 respectively.
Words 5 to 36 -> devices 0 to 31 respectively.
Byte 0: 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).
Words 37 to 68 -> devices 0 to 31 respectively.
Byte 0: 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).
If this = 1, automatic addressing is active.
If this = 0, automatic addressing is deactivated.
35012326 00 July 2006
341
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. 349
) or Data Exchange Off mode (See AS-i V2 Data
Exchange Off Operating Mode, p. 350 ) 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
%MWxy.0.74:X0
%MWxy.0.74:X1
%MWxy.0.74:X2
%MWxy.0.74:X3
Meaning for Xj=1
Switching to Offline mode
Leaving Offline mode
Data exchange inactive
Data exchange active
Note: Offline mode has priority over Data Exchange Off mode.
342 35012326 00 July 2006
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
Description
Address
%MWxy.0.75 to
%MWxy.0.106
%MWxy.0.107 to
%MWxy.0.138
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.
The table below shows AS-i V2 parameter adjustment objects.
Function
Adjustment of parameters of slaves in bank A.
Adjustment of parameters of slaves in bank B.
Meaning
Contain the parameter values of slaves 0 to 31 respectively.
Contain the parameter values of slaves 0 to 31 respectively.
35012326 00 July 2006
343
Bits and words associated with the AS-i V2 function
Explicit Exchange Object: Status %MWxy.MOD.2:Xj
At a Glance
Description
This word type object provides information on the state of the module TSX SAY
1000 .
The table below gives the meaning of the different bits of the word
%MWxy.MOD.2:Xj .
Address Function
%MWxy.MOD.2:X0 Standard module status
%MWxy.MOD.2:X1
%MWxy.MOD.2:X2
Meaning for Xj = 1
Internal error.
Configuration fault.
Line fault.
344 35012326 00 July 2006
AS-i V2 operating mode
21
At a Glance
Aim of this chapter
What's in this
Chapter?
This chapter introduces the different AS-i V2 function operating modes.
This chapter contains the following topics:
Topic
AS-i V2 Operating Mode: General
AS-i V2 Protected Mode
AS-i V2 Offline Operating Mode
AS-i V2 Data Exchange Off Operating Mode
Page
35012326 00 July 2006
345
AS-i V2 operation
AS-i V2 Operating Mode: General
At a Glance
Operating mode
The extended AS-i V2 function allows three operating modes, each one fulfilling particular needs. These modes are: z z z protected mode, offline mode, data exchange off mode.
The figure below shows the general operating diagram of the AS-i V2 bus.
Offline mode
Start
AS-i master module
Waiting to receive configuration
No
Is the master configured?
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. 349
or AS-i V2 Data Exchange Off
346 35012326 00 July 2006
AS-i V2 operation
Correspondence between PLC operating modes and the AS-i bus
The table below shows the correspondence between Premium PLC operating modes and those of the AS-i V2 bus.
PLC
Configured mode (1)
AS-i bus
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.
35012326 00 July 2006
347
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: z continually checks that the list of detected slaves is the same as the list of expected slaves, z 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 activating a slave
The diagram below shows the principle of activating AS-i V2 slaves.
PL7 AS-i V2 Bus Module
List of slaves expected LPS
List of detected slaves LDS
Comparison
List of activated
slaves LAS
348 35012326 00 July 2006
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
Procedure
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.
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.
35012326 00 July 2006
349
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
Procedure
When the Data Exchange Off mode is engaged, exchanges on the bus continue to function, but data is no longer refreshed.
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.
350 35012326 00 July 2006
AS-i V2 performance
22
AS-i V2 Bus Performance
Introduction
AS-i V2 Scanning
Time
Scanning time t represents the exchange time between the master and n slaves
(31 maximum on /A and/or /B).
Either: z up to 19 active slaves, t = 3ms z 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
Response Time
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).
Example
The response time T represents the AS-i V2 cycle time.
This includes: z z z the bus scanning time, the update of the AS-i V2 module internal memory, the PLC cycle.
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
10 ms
30 ms
60 ms
Typical response time
35 ms
65 ms
110 ms
Maximum response time
56 ms
96 ms
156 ms
35012326 00 July 2006
351
AS-i V2 performance
352 35012326 00 July 2006
DFB for AS-i Security Monitor
23
At a Glance
Aim of this
Section
What's in this
Chapter?
This DFB describes the DFB for the AS-i Security Monitor.
This chapter contains the following topics:
Topic
Description of the security function block of the AS-i bus
Operation of the AS-i security function block
Programming rules for security DFB
How to implement a DFB function block
Page
35012326 00 July 2006
353
DFB AS-i
Description of the security function block of the AS-i bus
General
Graphic representation
This DFB is used to obtain data processed by the safety monitor.
This drawing provides a graphic representation of the AS-i security function block:
SAFETY_MONITOR
Inputs
I0:Bit
I1:Bit
I2:Bit
I3:Bit
Enable
Q0
Q1
Q2
Q3
Error:Bit
Running:Bit
Outputs
Internal public data
Abort
Timeout
Dfb_stat
Dfb_err
Moni_err
Out_1
Out_2
SI_Ready
SI_off
SI_error
Bit
Word
Word
Word
Bit
Bit
Bit
Dword
Dword
Dword
Input parameters The table below describes the input parameters of the security DFB:
I1
I2
Name
I0
I3
Type
Bit
Bit
Bit
Bit
Description of monitor data
Input variable 0: %I\x.y.0\i.0 (x=rack, y=module, i=AS-i monitor address)
Input variable 1: %I\x.y.0\i.1 (x=rack, y=module, i=AS-i monitor address)
Input variable 2: %I\x.y.0\i.2 (x=rack, y=module, i=AS-i monitor address)
Input variable 3: %I\x.y.0\i.3 (x=rack, y=module, i=AS-i monitor address)
354 35012326 00 July 2006
DFB AS-i
Output parameters
Name
Error
Type
Bit
Running Bit
The table below describes the output parameters of the security DFB:
Description
This bit is set to "1" if an error occurs: DFB error or security bus error (error on at least one slave): z 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.
z 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.
This Bit is set to "1" during DFB execution.
Q0
Q1
Q2
Q3
Input/output parameters
Name
Enable
Type
Bit
Bit
Bit
Bit
Bit
The table below describes the input/output parameters of the security DFB:
Description
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.
Output variable 0: %Q\x.y.0\i.0 (x=rack, y=module, i=AS-i monitor address)
Output variable 1: %Q\x.y.0\i.1 (x=rack, y=module, i=AS-i monitor address)
Output variable 2: %Q\x.y.0\i.2 (x=rack, y=module, i=AS-i monitor address)
Output variable 3: %Q\x.y.0\i.3 (x=rack, y=module, i=AS-i monitor address)
35012326 00 July 2006
355
DFB AS-i
Public data parameters
Name
Abort
Moni_err
Out_1
Out_2
SI_ready
SI_off
SI_error
Dfb_stat
Dfb_err
Timeout
Bit
Bit
Bit
Dword
Dword
Dword
Word
Word
The table below describes the public data parameters of the security DFB:
Type
Bit
Word
Description
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.
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).
this bit is set to "1" if an error has occurred on the monitor.
this bit is set to "1" if the contact on OUT1 is closed.
this bit is set to "1" if the contact on OUT2 is closed.
each bit corresponds to the index of the security device which is in test or read status.
each bit corresponds to the index of the security device which is deactivated.
each bit corresponds to the index of the security device on which an error has occurred.
this is the DFB status; this variable enables the user to check on DFB
(See
Operation of the AS-i security function block, p. 357 ) progress.
This word specifies the error type: z 16#90; the response sent by the monitor is not valid, z 16#91: the DFB has been deleted by the user, z 16#92: the exchange has stopped as a result of a TimeOut. The
DFB cannot receive data.
To search for a safety slave which has been activated
The search for the address of a safety slave which has been activated can be facilitated by acknowledgment of the slave's inputs I3/I2/I1/I0. These inputs are equal to 0/0/0/0 if the slave has been activated, and not equal to 0/0/0/0 if the slave has not been activated. This information shall not be taken into account for safety purposes: only the safety monitor supplies the safety outputs.
356 35012326 00 July 2006
DFB AS-i
Operation of the AS-i security function block
General operation
Step-by-step description of operation
All the information used in the AS-i security DFB is obtained from the language objects associated with the TSX SAY 100 AS-i module and the TSX SAY 1000
AS-i V2 module.
The table below provides a step-by-step description of how the security DFB operates:
Step
1
2
3
4
5
Action
The bus master sends the request to test the monitor.
The bus master sends the request for the monitor to copy its status to static memory.
The bus master analyses the data from the monitor.
Retrieval of data from all security devices.
35012326 00 July 2006
357
DFB AS-i
Programming rules for security DFB
General
Rules
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: z z z systematically available in PL7 (See
How to insert a security DFB, p. 360 ),
read and write protected, dedicated to a single security monitor.
z z z
Preferably, the security DFB should be executed in the MAST task (for performance reasons).
You are strongly advised to only program a single instance of the security DFB in the application.
For a security DFB to be executed, the following conditions must be met: z the DFB must be called (the part of the program to which it has been assigned z must be executed) the Enable input must be set to 1
358 35012326 00 July 2006
DFB AS-i
Programming in
Ladder language
The security DFB function block is inserted in a ladder network. Programming consists of linking together these inputs/outputs
Sécurité
DFB SAFETY_MONITOR
%I\1.0\31.0
EBOOL
I0
%M102
S
%I\1.0\31.1
EBOOL
Error
%I\1.0\31.2
EBOOL
I1 EBOOL
Running
EBOOL
I2
%I\1.0\31.3
EBOOL
I3
%M101
%Q\1.0\31.0
%Q\1.0\31.1
%Q\1.0\31.2
%Q\1.0\31.3
EBOOL
Enable
EBOOL
Q0
EBOOL
Q1
EBOOL
Q2
EBOOL
Q3
Programming in
Structured Text language
The programming syntax is as follows:
%Li: label
Inst ( I0,..., I3, %MW101, Q0,...,Q3, %M102) ; where: z z z z z z
%Li : label,
Inst : name of a DFB instance,
I0,..., I3 : DFB inputs,
%M101: Enable input of DFB,
Q0,...,Q3 : variables linked to the DFB outputs,
%M102: Error output variable.
Enable %M101
Q0 %Q\1.0\31.0
Q1 %Q\1.0\31.1
Q2 %Q\1.0\31.2
Q3 %Q\1.0\31.3
35012326 00 July 2006
359
DFB AS-i
How to implement a DFB function block
Reminder
Using DFBs
How to insert a security DFB
The AS-i security DFB is included in the PL7 base (See How to insert a security
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.
The following table describes the procedure used to insert a security DFB:
Step
1
2
Action
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.
Program the DFB in the ladder network in LD or in the sequence in ST.
See
Programming rules for security DFB, p. 358
360 35012326 00 July 2006
Operator Dialog functions
V
Introduction
Subject of this part
What's in this
Part?
This part introduces the specific built-in Operator Dialog functions of PL7 and describes the software setup.
This part contains the following chapters:
Chapter
24
25
26
Chapter Name
General presentation of the Operator Dialog functions
Built-in DOP functions
Appendices
Page
35012326 00 July 2006
361
Operator Dialog functions
362 35012326 00 July 2006
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
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: z z z displaying messages, displaying message and alarm message groups, entering values from the PLC program.
Hence the Operator Dialog functions are completely integrated in the PLC application and support: z z data cohesion, unique saving, z z z easy maintenance, simplified consoles.
...
The processing of these functions occurs asynchronously to the processing of the operative task that enabled their activation.
How to access a
DOP function
See
Application-specific instructions, p. 62 .
363
35012326 00 July 2006
General presentation
Conditions for using built-in
DOP functions
Example of a
DOP function
The built-in DOP functions require a program space of 1 Kword (4.7 Kwords for
ADJUST). Variables must be reserved for the data you want to display (use the constants %KWi).
The illustration below shows an example of a DOP function written in the different
PL7 languages using the assisted entry of the library functions.
PANEL-CMD
Parameters
Console address:
Data to Send:
%MW0
%KW40
Commands
Clear
Screen
Entry log
Alarm log
Alarm management
Cancel an Alarm
6
2
Line
Clear
Clear
Report:
Line number
Alarm number
%MW100 4
1
1
OK Cancel
LD Language
%M100 %MW100>> OPERATE
PANEL_CMD (ADR#0.0.4, %KW0:2, %MW>>
IL Language
LDN
ANDN
%100
%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
364 35012326 00 July 2006
Built-in DOP functions
25
Introduction
Subject of this chapter
What's in this
Chapter?
This chapter describes the different built-in DOP functions and shows how they are set-up in PL7.
This chapter contains the following sections:
Section
25.1
25.2
Topic
Description of the parameters common to the different DOP functions
Description of the built-in DOP functions
Page
365
35012326 00 July 2006
Built-in DOP functions
366 35012326 00 July 2006
25.1
Built-in DOP functions
Description of the parameters common to the different DOP functions
Introduction
Subject of this section
This section shows the main parameters, divided into zones, of the built-in
DOP functions.
Note: The parameters specific to a DOP function are shown at the level of the function concerned.
What's in this
Section?
This section contains the following topics:
Topic
General
Parameters field: Console address
Parameters field: Data to be sent
Parameters field: Data to be received:
Parameters field: Report
Message field
Field zone
Page
35012326 00 July 2006
367
Built-in DOP functions
General
Introduction
Illustration
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: z z in read only (IN) format, acknowledged at the start of function execution, in write only (OUT) format, set at close of function execution, z 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.
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
Dates, Times, and Periods2.10 -
Diagnostics
Integrated DOP
Explicit exchanges
1.01 -
3.03 3.03
1.00
Name
ADJUST
ASK_MSG
ASK_VALUE
ASSIGN_K
Call format
PROCEDURE parameter:
Name Type
ADR AR_W
DATA AR_W
VAL AR_W
Kind
IN
Comment
CCX17 address table
IN Table for data to be sent
OUT Table for data to be received
Comment
Read/write memory objects and I/O
Variable blocking entry on CCX
Variable blocking entry on >>
Dynamic key assignment >>
Entry field
?
Call display
ASK_MSG( )
OK Cancel
368 35012326 00 July 2006
Built-in DOP functions
Parameters field: Console address
Introduction
Addressing via words or constants
This parameter contains the access path (address) for the CCX 17 dialog console.
This path can be either: z z located in a table of six internal words (%MW), located in a table of six internal constants (%KW), z 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.
The table below shows the signification of different words which make up the console address.
Word number
%MWi / %KWi
%MWi +1 / %KWi+1
%MWi +2 / %KWi+2
%MWi +3 / %KWi+3
%MWi +4 / %KWi+4
%MWi +5 / %KWi+5
Description
0
0
Most significant
6 (Uni-telway)
7 (FIPIO
254 (1)
Rack number
CCX 17 address
SYS
FIPIO connection point
Least significant
0
0 (1)
Module number channel
SYS (FIPIO)
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.
35012326 00 July 2006
369
Built-in DOP functions
Uni-telway addressing
The format of a CCX 17 address connected to the Uni-telway bus is:
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 .
370 35012326 00 July 2006
Built-in DOP functions
Examples of addressing
If you use: internal (or constant) words
ADR syntax
If you use: internal (or constant) words
ADR syntax
-
For a CCX 17 slave on a UTW 4-5 address, connected to a Premium PLC 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): in the function entry Help screen, …
Example:
Parameters
Console address: %MW0
Example:
Parameters
Console address: ADR#0.0.4
6 you must enter the program…
-
%MW0:=16#0600;
%MW1:=16#FE00;
%MW2:=16#0000;
%MW3:=16#0400;
%MW4:=16#0000;
%MW5:=16#0000; or
%MW0:6:=ADR#0.0.4;
DOP_Function(ADR#0.0.4,...
For a slave CCX 17 connected to a 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): in the function entry Help screen…
Example:
Parameters
Console address: %KW0
Example:
Parameters
Console address: ADR#\0.1.7\SYS
6 you must enter the program…
-
%KW0:=16#0700;
%KW1:=16#FE00;
%KW2:=16#0000;
%KW3:=16#0701;
%KW4:=16#00FE;
%KW5:=16#0000; or
%KW0:6:=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.
35012326 00 July 2006
371
Built-in DOP functions
Parameters field: Data to be sent
Introduction
Locating items within the PLC application
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.
In the case where data is to be found in the PLC application, it can be sent from: z a table of internal words (%MW), z a table of internal constants (%KW).
The table below shows the structure of data sent in this way.
Role Word number
1
2
3
4, 5, ...
Contains a contains a marker for value 16#CC17, and has a double role: z 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.
z 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.
Contains the command number.
Contains the length of data to be sent.
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).
372 35012326 00 July 2006
Location in a
CCX 17 with application
Built-in DOP functions
When data is in a CCX 17, the data to be sent is limited to DOP function execution commands.
This data can be sent from the PLC application: z from a table of internal words (%MW), z from a table of internal constants (%KW), z directly using an immediate integer value.
The table above shows data structure when using a table.
Role
1
2
Word number
Contains a command number
Contains the data to be sent to the console.
35012326 00 July 2006
373
Built-in DOP functions
Parameters 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.
374 35012326 00 July 2006
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: z z information on function activity, the exchange number which identifies the transaction in progress (useful when z z z using the CANCEL communication function), the exchange report split into two feedback codes: z z the communication level, the operation level, the value of the timeout which is used to monitor absent responses, 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 byte
%MWi Exchange number
%MWi+1
%MWi+2
%MWi+3
Operation report
Timeout
Length
Least significant byte Report management
Bit 0: activity bit System
Communication report System
User
System
%MWi:X0 activity bit
This bit indicates the state of the application of the communication function.
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 number
While a function is being sent, the system automatically assigns it a number which is used to identify the exchange.
This number serves as a reference to stop the exchange in progress, if necessary
(on using CANCEL).
35012326 00 July 2006
375
Built-in DOP functions
Communication report
The communication report provides information on the communication aspect of the 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.
16#0005
16#xx06
16#0007
16#0008
16#0009
16#000A
16#000B
16#xx14
16#00FF
The different values of this report are indicated in the following table:
Value
16#xx00
16#0001
16#0002
16#0003
16#0004
Significance of the communication report (least significant byte)
Successful exchange
Stopping the exchange via a timeout
Stopping the exchange on user request (CANCEL function)
Incorrect address format (length is other than 6)
Incorrect destination address (addresses unauthorized for the CCX 17, e.g.: addresses being broadcast)
Invalid report
Specific parameters are invalid (particularly those concerning data to be sent)
Destination missing
Reserved
Size of reception buffer is insufficient
Size of transmission buffer is insufficient
System resources missing (communication saturation)
Negative response from the CCX 17 or from the PLC (ADJUST function)
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.
376 35012326 00 July 2006
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: z z
16#00,
16#06, z
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
(least significant byte)
16#0000
16#1006
16#1106
16#1206
16#1306
16#1406
16#6506
16#6606
16#6706
16#6806
16#6906
16#FF06
16#0114
16#0214
16#0414
16#0814
16#1414
16#1514
16#2014
Significance of the operation report
Generic positive result
Number of management words below 24
Non-existent type object to be read (greater than 8)
Inconsistency between bits RDEC and SINC
Invalid value to be written
Broadcast address (ALL) prohibited
{network.station} pair different from {0.254}
Data to be sent does not have a 16#CC17 marker
Invalid size of data to be sent
Invalid CCX 17 response
Length of "Data to be received" is insufficient
CCX 17 link inoperational
Command not recognized
Command queue capacity has been exceeded
Size of command is less that the minimum required size
Command refused because application transfer in progress
Inaccessible object
System error
Incorrect data
Integrated DOP functions
All
ADJUST only
All except ADJUST
ADJUST only
All except ADJUST
35012326 00 July 2006
377
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
Start function
End of timeout
Activity bit = 0
Report = 1
Activity bit = 1
Timeout activation
Report set to zero
Allocation of exchange number
Receive response
Activity bit = 0
Stop timeout
Report update
Length
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.
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.
378 35012326 00 July 2006
Built-in DOP functions
Message field
Introduction
Message text
The message field groups together the different elements that make up the data to be displayed on the CCX 17 screen.
These elements are: z the message text, z z the different display attributes (position, size, etc.).
the message print command via the CCX 17.
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.
Overprint
Line
This parameter orders the command console to print a message when it appears on the console screen.
This parameter refers to alarm messages only. Enabling this parameter overprints the alarm message as soon as it appears.
This parameter specifies the line where the message must be displayed.
Position
Minimum
Default
Maximum
Value
1
1
16
35012326 00 July 2006
379
Built-in DOP functions
Column This parameter specifies the column where the first message character is positioned.
Position
Minimum
Default
Maximum
Automatic (1)
Value(s)
1
1
40
Left, Centered, Right
Key
(1) This mode can be accessed by selecting automatic mode. It is local to the function.
Attributes
Size
Clear
This parameter sets the attributes of the message display.
The different modes are: z z z
Normal (when no check box has been selected),
Flashing,
Reverse video.
This parameter specifies the format of all the text characters or the variable to be displayed.
Possible options are: z
Standard, z
Double.
This field is used to associate a single command that has been executed with a message before the message has been displayed.
Options are: z
None (no command is associated with a message), z z
Line (clears the line on which the message is to be displayed),
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).
380 35012326 00 July 2006
Built-in DOP functions
Field zone
Introduction
Field type
Symbol
Address
Comment
The Field zone is used to set the different parameters for the object which is associated with a message.
These parameters are: z the type of object, z z the display format,
...
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
None
Address
Date
Time
Description
No field is associated with the message displayed.
The object associated with the message is a variable.
The message is correlated to the current PLC date.
The message is correlated to the current PLC time.
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.
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: z z z internal bits (%Mi), internal words (%MWi), double internal words (%MDi).
This field displays the variable comment for viewing. This comment is set in the application data editor.
35012326 00 July 2006
381
Built-in DOP functions
Refresh
Display format
This function specifies whether the variable contained in the message should be periodically refreshed while being displayed (function is active be default).
This parameter specifies the variable display format.
The table below shows the different formats available.
Format
ASCII
Numerical
-
Associated parameters
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.
382 35012326 00 July 2006
25.2
Built-in DOP functions
Description of the built-in DOP functions
Introduction
Subject of this section
What's in this
Section?
This section describes the different built-in DOP functions.
This section contains the following topics:
Topic
List of the built-in DOP functions
SEND_MSG function
GET_MSG function
ASK_MSG function
SEND_ALARM function
DISPLAY_MSG function
DISPLAY_GRP function
DISPLAY_ALRM function
ASK_VALUE function
GET_VALUE function
CONTROL_LEDS function
ASSIGN_KEYS function
PANEL_CMD function
ADJUST function
Page
35012326 00 July 2006
383
Built-in DOP functions
List of the built-in DOP functions
Introduction The built-in DOP functions make it possible to: z control the main functions of a CCX 17 console not containing an application (this z has been neither configured nor loaded by the external design software).
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
SEND_MSG
GET_MSG
ASK_MSG
Displaying status messages contained in the PLC memory on CCX 17 with or without variable.
Free entry (asynchronous) of PLC variable values associated with status messages.
Blocking entry (synchronous) of a PLC variable value associated with status messages.
Displaying alarm messages contained in the PLC memory.
SEND_ALARM
DISPLAY_MSG
DISPLAY_GRP
Displaying a status message contained in the memory of the CCX17.
Displaying a group of status messages contained in the CCX17 memory.
DISPLAY_ALRM Displaying an alarm message contained in the CCX17 memory.
ASK_VALUE Blocking entry (synchronous) of values for the PLC variables associated with a status message contained in the CCX17 memory.
GET_VALUE Free entry (asynchronous) of values for the PLC variables associated with a status message contained in the CCX17 memory.
CONTROL_LEDS Controlling the CCX 17 LEDs and relays.
ASSIGN_KEYS
PANEL_CMD
ADJUST
Configuring the CCX 17 command keys.
Sending a generic command.
Language object adjustment.
-
X
X
X
X
-
-
-
-
X
Application
Without With
X -
X
X -
-
X
X
X
X
X
-
X
X
X
X
384 35012326 00 July 2006
Built-in DOP functions
SEND_MSG function
Role
Implementation
Application example
This function is used to display a message with a dynamic variable (if necessary) on a CCX 17 console screen.
Implementation of the SEND_MSG function is developed in the Description of parameters (See Description of the parameters common to the different DOP
) section.
The example given below makes use of the SEND_MSG function to display two status messages on the screen of a T CCX 1720 W console without an application.
This is connected to a 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
The aim of this example is, after setting application to RUN (%S13 =1): z initializing the PLC variables, z writing the console address (ADR#0.04) in a word table, z z z adjustment of timeout to 50 s, conditions of execution, clearing the console screen (see PANEL_CMD function), z z to display status messages on the console screen: z z
Manu and Auto (standard format, positioned on line 1, Column 1),
Four 4 (double format, automatic centering, Line 4), storing the function display execution.
Variables used
%MW0:6: console address
%KW0:x: message 1 data to send
%KW40:x: message 2 data to send
%MW100:4: report
%MW100:X0: activity bit
%MW102: timeout
%M100:2: conditions of activation,
35012326 00 July 2006
385
Built-in DOP functions
Introduction to the console
Manu Auto
Four 4
Fixed messages
Program corresponding to the application
( * INIT console address, condition, timeout
*)
IF %S1.3 THEN
%MW0:6:=ADR#0.0.4;
%MW102:=500;
%M100:2:=0;
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;
Entry help screens corresponding to the application:
SEND_MSG
Parameters
Console address:
Data to Send:
%MW0
%KW0
6
28
Message
Text: Manu Auto
Position
Mode
Manual
Line 1 Column
Column alignment
1
Auto Left Centered Right
Report:
Attributes
Flashing
Clear
None
Field
Field type
None Address Date
Symbol:
Comment:
Display format
Address:
%MW100 4
Size
Standard
Double
Parameters
Line Scree
Data to Send:
%MW0
%KW40
Message
Text: Time Four 4
Position
Mode
Update
Manual
Line 4 Column
Column alignment
6
12
15
Left Centered Right
Report: %MW100 4
Attributes
Flashing
Reverse video
Clear
None Line
Size
Standard
Double
Screen
OK Cancel Field
Field type
Symbol:
Comment:
Display format
None Address
Address:
Date Time
Update
Modify
OK Cancel
386 35012326 00 July 2006
Built-in DOP functions
GET_MSG function
Role
Implementation
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 of the GET_MSG function is developed in the Description of parameters (See Description of the parameters common to the different DOP
) section.
Specific parameter: Value
The Value parameter specifies the characteristics of the value which is associated to the variable.
If the choice is… The value…
Not checked entry on the CCX 17 console keyboard is free (1).
Limited
Increment 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).
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.
35012326 00 July 2006
387
Built-in DOP functions
Example of application
The example given below makes use of the GET_MSG function to display a status 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 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
Initial conditions z writing the console address (ADR#0.04) in a table of words, z z adjustment of timeout to 50 s, condition of execution,
Application: The aim of this example is, on user request: z to display a status message on the console screen: z
Temperature = xxx °C (standard format, automatic centering,
Line 6, variable with attributes: increment of 50, three-digit integer, z periodic refreshing), storing the function execution.
Variables used
%MW0:6: console address
%KW80:x: data to be sent.
%MW100:4: report
%MW100:X0: activity bit
%MW102: timeout
%M102: activation condition
%MW10: Temperature variable
Introduction to the console
Message displayed on user request
Temperature = xxx °C
Program corresponding to the application
( * INIT console address, condition, timeout
*)
IF %S1.3 THEN
%MW0:6:=ADR#0.0.4;
%MW102:=500;
%M102:=0;
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;
388 35012326 00 July 2006
35012326 00 July 2006
Built-in DOP functions
Entry help screen corresponding to the application:
GET_MSG
Parameters
Console address:
Data to Send:
%MW0
%KW1000 34
Message
Text: Temperature=____°C
Position
Mode
Manual
Line 6 Column
Column alignment
Auto Left
11
Centered Right
Report:
Attributes
Flashing
%MW100
Reverse video
Size
4
Standard
Double
Field
Symbol:
Comment:
Display format
Entry
Value
Not Checked
Address:
Limited
%MV10
999
Modify
Increment
Increment: 50
Update
Ok Cancel
389
Built-in DOP functions
ASK_MSG function
Role
Implementation
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 of the ASK_MSG function is developed in the Description of parameters (See Description of the parameters common to the different DOP
Note: It is strongly advisable to assign parameters for the timeout for an infinite period (see
Parameters field: Report, p. 375
so as not to invalidate the ASK_MSG function before the operator entry is made.
Specific parameter: Value
The Value parameter specifies the characteristics of the value which is associated to the variable.
If the choice is… The value…
Not checked entry on the CCX 17 console keyboard is free (1).
Limited
Increment 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).
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.
390 35012326 00 July 2006
Example
Built-in DOP functions
The illustration below shows an example of ASK_MSG function entry.
ASK_MSG
Parameters
Console address:
Data to Send:
ADR#,LL0.1.7,SYS
%KW20 34
Message
Text: ASK MSG:_
Position
Mode
Manual
Line 5 Column
Column alignment
Auto Left
5
Centered Right
Data to receive:
Report:
Attributes
Flashing
Reverse video
%KW200
%KW10
Size
2
4
Standard
Double
Field
Symbol:
Comment:
Display format
Entry
Value
Not Checked
Address:
Limited
%MV100
99
Modify
Increment
Ok Cancel
35012326 00 July 2006
391
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
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 parameter:
Alarm number
The Alarm number parameter defines the alarm message identifier.
Its value is between 900 and 999.
392 35012326 00 July 2006
Built-in DOP functions
Example of application
The example given below makes use of the SEND_ALARM function to display an alarm message on the screen of a T CCX 1720 W console without application.
This is connected to a 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.
Application description
Initial conditions z z writing the console address (ADR#0.04) in a table of words, adjustment of timeout to 50 s, z condition of execution,
Application: The aim of this example is: z z to detect overshoot of a temperature threshold (500 °C), to display an alarm message on the console screen: z z
Overheat four = xxx °C (standard format, automatic setting imposed by the function, variable with attributes: increment of 50, three-digit integer), storing the function execution.
Variables used
%MW0:6: console address
%KW80:x: data to be sent.
%MW100:4: report
%MW100:X0: activity bit
%MW102: timeout
%M103: activation condition
%MW10: Temperature variable
Introduction to the console
System display Alarm message
*ALARM*
Oven overheating = xxx °C
Program corresponding to the application
( *INIT console address, condition, timeout
*)
IF %S1.3 THEN
%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;
35012326 00 July 2006
393
Built-in DOP functions
Entry help screen corresponding to the application:
SEND_ALARM
Parameters
Console address:
Data to be sent:
%MW0
%KW120
6
29
Message
Text: Oven overheating = ____°C
Alarm number: 901
Size
Standard
Field
Symbol:
Comment:
Display format
Report:
Double
%MW110
Overprint
Address: %MW10
999 Modify
4
OK Cancel
394 35012326 00 July 2006
Built-in DOP functions
DISPLAY_MSG function
Role
Implementation
This function is used to display a message contained in the CCX 17 operator dialog console memory.
Implementation of the DISPLAY_MSG function is developed in the Description of parameters (See Description of the parameters common to the different DOP
) section.
Specific parameter:
Message number
The Message number parameter defines the alarm message identifier contained in the CCX 17 memory.
Its value is between 1 and 300.
Example The illustration below shows an example of DISPLAY_MSG function entry.
DISPLAY_MSG
Parameters
Console address:
Data to be sent:
ADR# 0.0.4
%KW200
Report: %MW10 4
Value of data to be sent
Message number: 1
OK Cancel
35012326 00 July 2006
395
Built-in DOP functions
DISPLAY_GRP function
Role
Implementation
Specific parameter:
Message group number
This function is used to simultaneously display a group of messages contained in the CCX17 operator dialog console memory.
Implementation of the DISPLAY_MSG function is developed in the Description of parameters (See Description of the parameters common to the different DOP
The Message group number parameter defines the group message identifier contained in the CCX 17 memory.
Its value is between 1 and 100.
Example of application
The example given below makes use of the DISPLAY_GRP function to display a group of two status messages on the screen of a T CCX 1720 W console containing an application.
This is connected to a 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
The aim of this example is, after setting application to RUN (%S13 =1): z initializing the PLC variables, z writing the console address (ADR#0.04) in word table, z z z adjustment of timeout to 50 s, z condition of execution, clearing the console screen (see PANEL_CMD function), displaying the group of state n°1 messages contained in the CCX 17 application, for: z message n°1: Manu and Auto (standard format, moved to line 1, z
Column 1), z message n°2: Four 4 (double format, automatic centering, Line 4), storing the function execution.
Variables used
%MW0:6: console address
%KW0:x: message 1 data to send
%MW100:4: report
%MW100:X0: activity bit
%MW102: timeout
%M100: activation condition
396 35012326 00 July 2006
Built-in DOP functions
Introduction to the console
Manu Auto
Oven 4
Fixed messages
Program corresponding to the application
( * INIT console address, condition, timeout
*)
IF %S1.3 THEN
%MW0:6:=ADR#0.0.4;
%MW102:=500;
%M100:=0;
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:
Data to be sent:
%MW10
%KW0
Value of data to be sent
Message group number: 1
6 Report: %MW100 4
OK Cancel
35012326 00 July 2006
397
Built-in DOP functions
DISPLAY_ALRM function
Role
Implementation
This function is used to display an alarm message contained in the CCX17 operator dialog console memory.
Implementation of the DISPLAY_ALRM function is developed in the Description of parameters (See Description of the parameters common to the different DOP
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 parameter:
Alarm message number
The Alarm message number parameter defines the alarm message identifier contained in the CCX 17 memory.
Its value is between 1 and 300.
An alarm can be activated exclusively by: z letter box (requires MMI 17 WIN software), z 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.
398 35012326 00 July 2006
Built-in DOP functions
Application example
The example given below makes use of the DISPLAY_ALRM function to display an alarm message on the screen of a T CCX 1720 W console containing an application.
This is connected to a 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.
Application description
Initial conditions z z writing the console address (ADR#0.04) in a word table, adjustment of timeout to 50 s, z condition of execution,
Application: The aim of this example is: z z to detect overshoot of a temperature threshold (500 °C), to display the alarm message contained in the CCX 17 application, for: z z
Overheat four = xxx °C (standard format, automatic setting imposed by the function, variable with attributes: increment of 50, three-digit integer), storing the function execution.
Variables used
%MW0:6: console address
%KW80:x: data to be sent.
%MW100:4: report
%MW100:X0: activity bit
%MW102: timeout
%M103: activation condition
%MW10: Temperature variable
Introduction to the console
System display Alarm message
*ALARM*
Oven overheating = xxx °C
Program corresponding to the application
( *INIT console address, condition, timeout
*)
IF %S1.3 THEN
%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;
35012326 00 July 2006
399
Built-in DOP functions
Entry help screen corresponding to the application:
DISPLAY_ALRM
Parameters
Console address:
Data to be sent:
%MW0
%KW150
Value of data to be sent
Number of alarm message: 1
6 Report: %MW100 4
OK Cancel
400 35012326 00 July 2006
Built-in DOP functions
ASK_VALUE function
Role
Implementation
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 of the ASK_VALUE function is developed in the Description of parameters (See Description of the parameters common to the different DOP
) section.
Note: It is strongly advisable to assign parameters for the timeout for an infinite period (see
Parameters field: Report, p. 375 so as not to invalidate the
ASK_VALUE function before the operator entry is made.
Specific parameter:
Status message number
This parameter defines the message identifier contained in the CCX 17 memory.
Its value is between 1 and 300.
Example The illustration below shows an example of ASK_VALUE function entry.
ASK_VALUE
Parameters
Console address:
Data to be sent:
ADR# 0.0.4
%KW200
6 Data to receive:
Report:
%MW10
%MW20
2
4
Value of data to be sent
Status message number: 3
OK Cancel
35012326 00 July 2006
401
Built-in DOP functions
GET_VALUE function
Role
Implementation
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 of the GET_VALUE function is developed in the Description of parameters (See Description of the parameters common to the different DOP
Specific parameter:
Status message number
This parameter defines the message identifier contained in the CCX 17 memory.
Its value is between 1 and 300.
402 35012326 00 July 2006
Application example
Built-in DOP functions
The example given below makes use of the GET_VALUE function to display a status message containing a variable on the screen of a T CCX 1720 W console containing an application.
This is connected to a 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
Initial conditions z writing the console address (ADR#0.04) in a word table, z z adjustment of timeout to 50 s, condition of execution,
Application: The aim of this example is, on user request: z initializing the PLC variables, z displaying message n°4 contained in the CCX17 application, for: z
Temperature = xxx °C (standard format, automatic centering, z
Line 6, variable with attributes: increment of 50, three-digit integer, periodic updating), storing the function execution.
Variables used
%MW0:6: terminal address
%KW80:x: data to be sent.
%MW100:4: report
%MW100:X0: activity bit
%MW102: timeout
%M102: activation condition
%MW10: Temperature variable
Introduction to the console
Message displayed on user request
Temperature = xxx °C
Program corresponding to the application
( *INIT console address, condition, timeout
*)
IF %S1.3 THEN
%MW0:6:=ADR#0.0.4;
%MW102:=500;
%M102:=0;
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;
35012326 00 July 2006
403
Built-in DOP functions
Entry help screen corresponding to the application:
GET VALUE
Parameters
Console address:
Data to be sent:
%MW0
%KW100
Value of data to be sent
Status message number: 4
6 Report: %MW100 4
OK Cancel
404 35012326 00 July 2006
Built-in DOP functions
CONTROL_LEDS function
Role
Implementation
Specific parameter:
LED status
Specific parameter:
Relay status
This function is used to control some CCX 17 console functions.
These functions are: z z relay state (version 2.1 and above), state of the small luminous column LEDs.
The CONTROL_LEDS function is available whether or not the CCX 17 has an application.
Implementation of the CONTROL_LEDS function is developed in the Description of parameters (See Description of the parameters common to the different DOP
) section.
This parameter defines the current status of each LED.
the various states can be: z
Unchanged, z z z
Off,
Flashing,
On.
This parameter defines the relay status.
the various states can be: z z z
Unchanged,
Open,
Closed.
35012326 00 July 2006
405
Built-in DOP functions
Application example
The example given below makes use of the CONTROL_LEDS function to control the
T CCX 1720 W console’s green LED status.
This is connected to a Premium via the AUX port (configured in UNI-TELWAY link, addresses 4 - 5).
Application description
Initial conditions z z writing the console address (ADR#0.04) in a word table, adjustment of timeout to 50 s, z condition of execution,
Application: The aim of this example is, on rising edge of the variables: z z
Manu : controlling the green LED in Flashing mode,
Auto : controlling the green LED in On mode
Variables used
%MW0:6: terminal address
%KW200:x:Manu status data to send
%KW210:x: Auto status data to send
%MW100:4: report
%MW100:X0: activity bit
%MW102: timeout
%M0:Manu variable
%M2: Auto variable
Introduction to the console
Green LED
Program corresponding to the application
( *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;
406 35012326 00 July 2006
Entry help screens corresponding to the application:
CONTROL_LEDS
Parameters
Console address:
Data to Send:
%MW0
%KW200
LED status
6
2
Report: %MW100 4
Unchanged Off Flashing On
Unchanged Off
Unchanged
Relay status
Unchanged
Off
OK
Flashing On
Open
Cancel
Flashing On
CONTROL_LEDS
Data to Send:
LED status
%MW0
%KW210
Unchanged Off
6
2
Unchanged Off
Off Unchanged
Relay status
Unchanged
OK
Report:
Flashing
Flashing
Flashing
Open
Cancel
Built-in DOP functions
%MW100 4
On
On
On
Closed
35012326 00 July 2006
407
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
Zone: Set by This zone is used to specify which out of the PLC or CCX 17 contains the key configuration data.
z
PLC: the data considered is that entered in the Command key zones, z
CCX 17 the data considered is that from the application contained in the console.
Zone:
Command key x
This zone is used to define the characteristics associated with each key.
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
Symbol
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.
Specifies the symbol associated with the bit. The address associated with this symbol is automatically taken into account.
408 35012326 00 July 2006
Built-in DOP functions
Zone: Display command keys
Command keys are configured in groups of four.
This zone is used to access the various groups of keys.
Application example
The example given below makes use of the ASSIGN_KEYS function to assign a function to the T CCX 1720 W console command keys1 and 2.
This is connected to a 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
Initial conditions z z writing the console address (ADR#0.0.4) in a word table, adjustment of timeout to 50 s, z condition of execution,
Application: The aim of this example is: z z z to assign the %M0 variable to command key 1, to assign the %M2 variable to command key 2, storing the function execution.
Variables used
%MW0:6: terminal address
%KW240:x: data to be sent.
%MW100:4: report
%MW100:X0: activity bit
%MW102: timeout
%M0: Manu variable
%M2: Auto variable
%M12: condition of execution
%M108: condition of execution
Introduction to the console
Key 1 Key 2
Program corresponding to the application
( * 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;
35012326 00 July 2006
409
Built-in DOP functions
Entry help screens corresponding to the application:
ASSIGN_KEYS
Parameters
Console address:
Data to Send:
%MW0
%KW240
Set by
PLC
6
16
Report:
CCX17
%MW100 4
Command key 1
Inhibit
Symbol: Manual
Address: %MV0
Command key 3
Inhibit
Symbol:
Address:
Action
On edge
On state
Action
On edge
On state
Command key 2
Inhibit
Symbol: Auto
Address: %M2
Command key 4
Inhibit
Symbol:
Address:
Action
On edge
On state
Action
On edge
On state
Key 9 to 12...
Key 1 to 4...
Display command keys
OK
Key 5 to 8...
Cancel
410 35012326 00 July 2006
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: z z clearing a line or the screen, printing or clearing the operator entry log, z z printing or clearing the alarms log, 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
) section.
Field: Command This field is used to set the command associated with the PANEL_CMD function.
For: z z clearing a line; the line number must be specified, canceling an alarm; you must designate the alarm number which corresponds to identifier given while using SEND_ALRM or DISPLAY_ALRM.
35012326 00 July 2006
411
Built-in DOP functions
Application example
The example below shows the implementation of the PANEL_CMD function for the purpose of canceling a T CCX 1720 W console alarm.
This is connected to a Premium via the AUX port (configured in UNI-TELWAY link, addresses 4 - 5).
Application description
Initial conditions z z writing the console address (ADR#0.04) in a word table, adjustment of timeout to 50 s, z condition of execution,
Application: The aim of this example is: z z z wiping the console screen on user demand, canceling the alarm on fault acknowledgement, storing the function execution.
Variables used
%MW0:6: console address
%KW350:x: Wipe data to be sent,
%KW360:x: Cancel data to be sent,
%MW100:4: report
%MW100:X0: activity bit
%MW102: timeout
%M102: activation condition
%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;
412 35012326 00 July 2006
Built-in DOP functions
Entry help screens corresponding to the application:
PANEL-CMD
Parameters
Console address:
Data to be sent:
%MW0
%KW40
Commands
Clear
Screen
Entry log
Alarm log
Alarm management
Cancel an Alarm
6
2
Line
OK
Report:
Line number
%MW100
1
4
Clear
Clear
Alarm number
Cancel
PANEL-CMD
Parameters
Console address:
Data to be sent:
1
Commands
Clear
ADR#0.0.4
%KW350
Screen
Entry log
Alarm log
Alarm management
Cancel an Alarm
2
Line
Clear
Clear
Report:
Line number
Alarm number
%MW50 4
1
1
OK Cancel
35012326 00 July 2006
413
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: z z z internal bits (%Mi), internal words or double words (%MWi, %MDi), rack or remote inputs/outputs (%I, %Q, %IW, %QW, %ID, %QD).
Note: It is strongly advised: z to only execute one instance of the ADJUST function per cycle, z z to only execute the ADJUST function every n cycles.
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 function (EN)
Read / Write
(R_W)
This parameter is used to execute the ADJUST function.
The types of objects assigned to this parameter may be: z an internal bit (%Mi), z an internal word extract bit (%MWi:Xj).
This parameter defines the type of operation to be carried out: z read: bit = 0, z write: bit = 1.
The types of objects assigned to this parameter may be: z z an internal bit (%Mi), an internal word extract bit (%MWi:Xj).
414 35012326 00 July 2006
Type of object
(TYPE)
Built-in DOP functions
This parameter defines the type of object to be read or written.
The types of objects assigned to this parameter may be: z z an internal word (%MWi), an immediate value.
The table below shows the different types of objects which can be controlled using the ADJUST function.
Type of object
%Mi
%MWi
%MDi
%I
%Q
2
3
4
0
1
Value of internal word or immediate value
Type of object
%IW
%QW
%ID
%QD
7
8
5
6
Value of internal word or immediate value
35012326 00 July 2006
415
Built-in DOP functions
Object address
(ADR)
This parameter contains the address of the object to be read or written.
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.
This word contains… Possible values of the word Word order number
Word 0
Word 1
Word 2
Word 3
Word 4
Word 5
Word 6
Word 7 the rack number where the language object concerned is situated the number corresponding to the position in the rack of the I/O module or of the processor in which the language object concerned is situated the channel number in the module where the language object concerned is situated the rank of the I/O object or the number of the internal language object concerned.
0 : bit objects, internal words or double words, I/O objects whose operations function is registered in rack 0.
n : other rack I/O objects.
0 : bit objects, internal words and double words, I/O objects whose operations function is associated to channels 1 and
2 of the processor registered at position 0 in the rack.
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.
0 : bit objects, internal words and double words.
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.
0 or n : bit objects, internal words or double words, I/O objects with significant rank.
0 : Other I/O objects.
n : NANET or FIPIO objects.
0 : not significant.
the connection point number of the device on the FIPIO bus or the rank of the NANET object.
the position of the FIPIO module.
the channel number in the FIPIO module or the slave bit on the AS-i bus.
the slave number of the AS-i and NANET buses.
0 : basic or not significant module.
1 : extension module n : AS-i or FIPIO objects.
0 : not significant.
n : AS-i or NANET objects.
0 : not significant.
Value to write
(VAL)
This parameter contains the value to write in the object.
The object type assigned to this parameter is a double word (%MDi).
416 35012326 00 July 2006
Set at 1, or
Incrementation
(SINC)
Built-in DOP functions
Depending on the type of object to be written, this parameter is used: z to set the bit value (%Mi, %Q), z 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
Decrementation
(RDEC)
Depending on the type of object to be written, this parameter is used: z to clear the bit value (%Mi, %Q), z 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).
This parameter contains the parameter value which has just been read.
The object type assigned to this parameter is a double word (%MDi).
Value of the object read
(VRET)
Management parameters
(GEST)
The object type assigned to this parameter is a table of 24 internal words (%MWi).
35012326 00 July 2006
417
Built-in DOP functions
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 object
EN
R_W
TYPE
ADR
VAL
SINC
RDEC
VRET
MAN
%MW20:X0
%MW20:X1
%MW21
%MW22
%MW23
%MW24
%MW25
%MW26
%MW27
%MW28
%MW29
%MD30
%MW20:X2
%MW20:X3
%MD32
%MD34:24
0
0
0
0
0
0
12
0
0
0
2
0
1
0
Value to be entered:
Comment
Executing the ADJUST function
Read operation
Type of object: %MD
Not significant
Not significant
Not significant
Object number (%MD12)
Not significant
Not significant
Not significant
Not significant
Not significant
Not significant
Not significant
Value of the object read
Buffer parameter for receiving and sending requests
418 35012326 00 July 2006
35012326 00 July 2006
Built-in DOP functions
To write value 15 in the rack output word %QW3.2, the following values need to be entered:
Parameter Language object
EN
R_W
TYPE
ADR
VAL
SINC
RDEC
VRET
MAN
%MW20:X0
%MW20:X1
%MW21
%MW22
%MW23
%MW24
%MW25
%MW26
%MW27
%MW28
%MW29
%MD30
%MW20:X2
%MW20:X3
%MD32
%MD34:24
0
0
0
15
0
0
0
0
3
2
6
0
1
1
Value to be entered:
Comment
Executing the ADJUST function
Write operation
Type of object: %QW
Rack number
Module position
Channel number
Not significant
Not significant
Not significant
Not significant
Not significant
Value to write
Not significant
Not significant
Value of the object read
Buffer parameter for receiving and sending requests
419
Built-in DOP functions
To increment the output word on FIPIO %QW\1.2.12\0.1, the following values would need to be entered:
Parameter Language object
EN
R_W
TYPE
ADR
VAL
SINC
RDEC
VRET
MAN
%MW20:X0
%MW20:X1
%MW21
%MW22
%MW23
%MW24
%MW25
%MW26
%MW27
%MW28
%MW29
%MD30
%MW20:X2
%MW20:X3
%MD32
%MD34:24
0
0
0
0
0
1
0
12
1
2
6
0
1
1
Value to be entered:
Comment
Executing the ADJUST function
Write operation
Type of object: %QW
Not significant
Processor address
Channel number of built-in FIPIO link
Not significant
Connection point number
Module number: Standard
Channel number
Not significant
Not significant
Incrementing the word value by 1
Not significant
Not significant
Buffer parameter for receiving and sending requests
420 35012326 00 July 2006
35012326 00 July 2006
Built-in DOP functions
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 object
EN
R_W
TYPE
ADR
VAL
SINC
RDEC
VRET
MAN
%MW20:X0
%MW20:X1
%MW21
%MW22
%MW23
%MW24
%MW25
%MW26
%MW27
%MW28
%MW29
%MD30
%MW20:X2
%MW20:X3
%MD32
%MD34:24
0
1
7
0
0
2
0
0
5
0
4
1
1
1
Value to be entered:
Comment
Executing the ADJUST function
Write operation
Type of object: %Q
Rack number
Module position
Channel number
Not significant
Not significant
Not significant
Bit rank (slave input/output)
Slave number
Not significant
Not significant
Output RESET
Not significant
Buffer parameter for receiving and sending requests
421
Built-in DOP functions
To decrement the output word on NANET %QW\4.0\2.1, the following values would need to be entered:
Parameter Language object
EN
R_W
TYPE
ADR
VAL
SINC
RDEC
VRET
MAN
%MW20:X0
%MW20:X1
%MW21
%MW22
%MW23
%MW24
%MW25
%MW26
%MW27
%MW28
%MW29
%MD30
%MW20:X2
%MW20:X3
%MD32
%MD34:24
0
1
2
0
0
0
1
0
4
0
6
0
1
1
Value to be entered:
Comment
Executing the ADJUST function
Write operation
Type of object: %QW
Rack number
Module position
Channel number
NANET object rank (word number)
Not significant
Not significant
Not significant
Slave number
Not significant
Not significant
Decrementing the word value by 1
Not significant
Buffer parameter for receiving and sending requests
422 35012326 00 July 2006
Appendices
26
Introduction
Subject of this chapter
What's in this
Chapter?
This chapter introduces the supplementary information for installing DOP functions.
This chapter contains the following sections:
Section
26.1
26.2
Topic
Precautions for DOP use
Description of the built-in DOP functions "Data to send" parameter coding
Page
423
35012326 00 July 2006
Appendices
424 35012326 00 July 2006
Appendices
26.1
Precautions for DOP use
Precautions for DOP use
Introduction
List of precautions
The list below is not exhaustive, however, it does group together the errors most frequently encountered whilst installing DOP functions in an application. z z z z z z z z z
Do not forget to initialize the Time-out parameter (%MWi+2) before starting the
Operator Dialogue function. For the ASK_MSG or ASK_VALUE functions, the value has to be 0.
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.
Synchronize the start of the different Built-in DOP functions in order that the
CCX 17 console command queue does not become full.
Remember to correctly calculate the size of the %KWi internal constants for displaying the data to be sent.
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.
The maximum size for the Built-in DOP functions is 47 words.
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.
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).
Canceling modifications or deleting a rung or phrase (List or Text) does not cancel initialization of the %KWi variables.
35012326 00 July 2006
425
Appendices
26.2
Description of the built-in DOP functions
"Data to send" parameter coding
Introduction
Subject of this section
What's in this
Section?
This section describes the Data to send parameter.
It is intended for application developers who want to install built-in DOP functions without using the input help screens.
This section contains the following topics:
Topic
PLC status message display: SEND_MSG function
PLC checked status message entry: ASK_MSG and GET_MSG function
PLC alarm message display: SEND_ALARM function
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
Display of luminous column LEDS: CONTROL_LEDS function
Configuring command keys: ASSIGN_KEYS function
Generic send command: PANEL_CMD function
Page
426 35012326 00 July 2006
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.
35012326 00 July 2006
427
Appendices
Data to send parameter coding
Meaning
1
2
Word number
3
4 to P
P +1
P +2
P +3
P +4
P+5
P+6
P+7
P+8
P+9
P
The table below shows the significance of the different words which constitute the following parameter: Data to send (47 words maximum).
contains a marker of value 16#CC17, contains value 0 contains the length in bytes and the zone of the following words, 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, contains the line number where the message must be displayed, contains the column number where the start of the message must be displayed,
This two word zone (four characters) contains the message characteristics and is structured as follows:
Character 1 This character (in capitals) corresponds to a video attribute: z z z z
B = blinking,
R = reverse video,
A = blinking and reverse video,
N = no attribute
Character 2
Characters 3 and
4
This character (in capitals) corresponds to the character font size: z S = normal size, z D = double width or height corresponds to the printing option: z Y followed by a space = yes, z N followed by a space = no.
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: contains the position of the variable to display, counted in number of characters in relation to the start of the message.
contains the number of characters to display for the variable.
contains a supplementary command: z 0: no command, z 1: clear screen, z 2: clear the line before the display.
contains the value 16#0030.
Number of words containing the text of the message to send (see line 4 to P).
428 35012326 00 July 2006
Appendices
Word number
P+12
P+13
Meaning
P+10 and 11 contain the type of entry field: z BIT +space = bit type, z z
ANA + space = word type,
LNG + space = double word type, z z
DAY + space = date type,
HOU + space = hour type.
contains value 0.
contains the type of variable to display: z z
B +space = bit type,
W + space = word type, z DW = double word type,
Note: for a Date or Hour type, this word contains value 0.
P+14 contains: z z the address index of the variable to display for a bit, word or double word type, 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:
ASCII or DIGITAL without decimal places
Byte 2 Byte 2 the ASCII code for the space, that being 20
DIGITAL with less than ten decimal places
DIGITAL with at least ten decimal places the ASCII code for the space, that being 20 the ASCII code for the number of tens of decimal places the ASCII code for the number of decimal places the ASCII code for the number of decimal place units
P+17
P+18
Byte 4 specifies the display type: z N = no format, z z
D = Digital,
A = ASCII define if the variable must be refreshed or not: z Y + space = yes, z N + space = no.
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).
35012326 00 July 2006
429
Appendices
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;
Value Comment Word number
%MW0
%MW1
%MW2
%MW3
%MW4
%MW5
%MW6
%MW7
%MW8
%MW9
%MW10
%MW11
15
ND
N sp
0
0
2 ur sp 4
16#CC17
0
18
Fo
Marker
Imposed value
Byte size of the following zone which includes nine words
Message text
Message text (continued)
Message text (end)
End of message mark
Message position (line number)
Message position (column number)
Message characteristics (no attribute or double font)
Message characteristic (no printing)
The message includes no variable
430 35012326 00 July 2006
PLC checked status message entry: ASK_MSG and GET_MSG function
Appendices
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.
35012326 00 July 2006
431
Appendices
Data to send parameter coding
Meaning
1
2
Word number
The table below shows the significance of the different words which constitute the following parameter: Data to send (47 words maximum).
3
4 to P
P +1
P +2
P +3
P +4
P+5
P+6
P+7
P+8
P+9
P+10
P contains a marker of value 16#CC17, contains the command type: z 33 = command number for ASK_MSG, z 6 = command number for GET_MSG, contains the length in bytes and the zone of the following words, 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, contains the line number where the message must be displayed, contains the column number where the start of the message must be displayed,
This two word zone (four characters) contains the message characteristics and is structured as follows:
Character 1 This character (in capitals) corresponds to a video attribute: z z z z
B = blinking,
R = reverse video,
A = blinking and reverse video,
N = no attribute
Character 2
Characters 3 and
4
This character (in capitals) corresponds to the character font size: z S = normal size, z D = double width or height corresponds to the printing option: z Y followed by a space = yes, z N followed by a space = no.
contains the position of the variable to display, counted in number of characters in relation to the start of the message.
contains the number of characters to display for the variable.
contains a supplementary command: z 0: no command (ASK_MSG synchronized entry), z 24: free entry authorized after display (GET_MSG multiple entry).
contains the value 16#0030.
contain the type of entry field (in Upper case): z BIT +space = bit type, z z
ANA + space = word type,
LNG + space = double word type.
Number of words containing the text of the message to send (see line 4 to P).
432 35012326 00 July 2006
Appendices
Word number
P+11
P+12
P+13
P+14
P+15
P+16
Meaning contains value 0.
contains the type of variable to display (in Upper case): z B +space = bit type, z z
W + space = word type,
DW = double word type, contains the address index of the variable to display.
contain the display format for the variable and are structured in the following ways:
Byte 1
Bytes 2 and 3 specifies if the variable is signed (sign +), or not (space), specifies the display format:
ASCII or DIGITAL without decimal places
DIGITAL with less than ten decimal places
DIGITAL with at least ten decimal places
Byte 2 the ASCII code for the space, that being 20 the ASCII code for the number of tens of decimal places
Byte 4 specifies the display type: z z z
N = no format,
D = Digital,
A = ASCII defines whether or not the variable must be updated: z Y + space = yes, z N + space = no.
Byte 3 the ASCII code for the space, that being 20 the ASCII code for the number of decimal places the ASCII code for the number of decimal place units
P+17 defines the field attributes: z I + space = increment, z L + space = others.
P+18 and 19 define the limit type: z 0 = unlimited, z 1 = minimum limit only, z z
2 = maximum limit only,
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).
35012326 00 July 2006
433
Appendices
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;
Value Comment
%MW14
%MW15
%MW16
%MW17
%MW18
%MW19
%MW20
%MW21
%MW22
%MW23
%MW24
%MW25
%MW26
%MW27
%MW6
%MW7
%MW8
%MW9
%MW10
%MW11
%MW12
%MW13
Word number
%MW0
%MW1
%MW2
%MW3
%MW4
%MW5
%MW28
%MW29
NS
N sp
15
3
24
16#0030
AN
A sp
0
W sp
10 espesp
°C
0
3
11 e esp
= sp
__
_ sp mp er at ur
16#CC17
6
70
Te sp D
Y esp
Marker
Command number for GET_MSG
Byte size of the following zone which includes 35 word
Message text
Message text (continued)
Message text (continued)
Message text (continued)
Message text (continued)
Message text (continued)
Message text (continued)
Message text (continued)
Message text (continued)
Message text (end)
End of message mark
Text position (line number)
Text position (column number)
Message characteristics (no attribute or double font)
Message characteristic (no printing)
Position of the variable from the start of the message
Number of characters to display
Additional command (entered after display)
Reserved value
Type of entry field (AN = start of ANA)
Type of entry field (continued)
Reserved value
Type of variable to display (W = word type variable)
Address index for the variable to display (%MW10)
Display format (sp for a non signed variable, sp for the start of the decoding of decimal places after the point)
Display format continued (sp for the end of the coding of the number of digits after the point, D for the decimal format)
The variable must be updated
434 35012326 00 July 2006
Word number
%MW30
%MW31
%MD32
%MD34
%MD36
Value
0
0
I esp
0
50
Comment
Entry is incremental
The variable is not limited
Minimum limit value
Maximum limit value
Increment value
Appendices
35012326 00 July 2006
435
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.
436 35012326 00 July 2006
Appendices
Data to send parameter coding
The table below shows the significance of the different words which constitute the following parameter: Data to send (37 words maximum).
3
4
1
2
Word number
Meaning contains a marker of value 16#CC17, contains value 0 contains the length in bytes and the zone of the following words, 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: z z
S = normal size,
D = double width or height.
Character 2
Characters 3 and
4 corresponds to the printing option: z Y = yes, z N = no.
correspond to the overprinting option: z z
Y followed by a space = yes,
N followed by a space = no.
P+3
P+4
P+5
P+6
P+7 and 8
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: contains the position of the variable to display, counted in number of characters in relation to the start of the message.
contains the number of characters to display for the variable.
contains the value 16#0030.
contain the type of entry field: z z z
BIT +space = bit type,
ANA + space = word type,
LNG + space = double word type,
P+9
P+10
P contains value 0.
contains the type of variable to display: z B +space = bit type, z z
W + space = word type,
DW = double word type,
Number of words containing the text of the message to send (see line 5 to P).
35012326 00 July 2006
437
Appendices
Word number
Meaning
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
Bytes 2 and 3 specifies if the variable is signed (sign +), or not (space), specifies the display format:
ASCII or DIGITAL without decimal places
DIGITAL with less than ten decimal places
DIGITAL with at least ten decimal places
Byte 2 Byte 3 the ASCII code for the space, that being 20 the ASCII code for the space, that being 20 the ASCII code for the number of tens of decimal places the ASCII code for the number of decimal places the ASCII code for the number of decimal place units
P
Byte 4 specifies the display type: z z z
N = no format,
D = Digital,
A = ASCII
Number of words containing the text of the message to send (see line 5 to P).
438 35012326 00 July 2006
Example of use
Appendices
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;
Value Comment
%MW14
%MW15
%MW16
%MW17
%MW18
%MW19
%MW20
%MW21
%MW22
%MW23
%MW24
%MW25
%MW26
%MW27
%MW6
%MW7
%MW8
%MW9
%MW10
%MW11
%MW12
%MW13
Word number
%MW0
%MW1
%MW2
%MW3
%MW4
%MW5
%MW28
0
SY
Y sp
19
3
16#0030
AN
A sp
0
W sp
10 espesp
= sp
__
_ sp
°C fe sp f or r sp
Su rc ha uf
16#CC17
0
52
900 sp D
Marker
Imposed value
Byte size of the following zone which includes 26 word
Alarm message number
Message text
Message text (continued)
Message text (continued)
Message text (continued)
Message text (continued)
Message text (continued)
Message text (continued)
Message text (continued)
Message text (continued)
Message text (continued)
Message text (continued)
Message text (end)
End of message mark
Message characteristic (Normal size, printing)
Message characteristic (overprinting)
Position of the variable from the start of the message
Number of characters to display
Reserved value
Type of entry field (AN = start of ANA)
Type of entry field (continued)
Reserved value
Type of variable to display (W = word type variable)
Address index for the variable to display (%MW10)
Display format (sp for a non signed variable, sp for the start of the decoding of decimal places after the point)
Display format continued (sp for the end of the coding of the number of digits after the point, D for the decimal format)
35012326 00 July 2006
439
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
Example of use
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: z
The status message number, z z
Alarm message number,
Message group number
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
440 35012326 00 July 2006
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 parameter coding
Meaning
1
2
Word number
The table below shows the significance of the different words which constitute the following parameter: Data to send (2 words).
contains a marker of value 16#CC17, indicates the coding of each LED as well as the relay state to send to the terminal.
z bits 0 to 3: green LED status, z bits 4 to 7: yellow LED status, z z bits 8 to 11: red LED status, bits 12 to 15: relay status, the state of each of the LEDS is coded on four bits as follows: z z z
0000: unchanged LED status,
0001: LED off,
0010: LED on, z 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: z z z
0000: unchanged relay status,
0001: open relay status,
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;
Value Comment Word number
%MW0
%MW1
16#CC17
16#1112
Marker
Green LEDS on, yellow and red off, open relay status
35012326 00 July 2006
441
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 parameter coding
Meaning Word number
1
The table below shows the significance of the different words which constitute the following parameter: Data to send (12 words).
2 contains a marker of value 16#CC17,
If a PLC carries out the assignment… this word contains the list of keys to configure. Each command key is coded on a bit (0: non configured, 1: configured): z bit i (i = 1 to 8) command key no. 1.
the following two words indicate the operating mode of each of the command keys. Each key is coded by two bits z 00: Reset, z 01: functioning mode on edge, z z
10: toggle functioning mode,
11: no action.
Bits 2j,2j+1 = command key i+1 (i = 0 to 11) the following eight words contain, accordingly: z a value –1 when the command keys are not affected, z the index of the internal bits affected by the command keys
Word i = command key i (i = 1 to 8)
If a CCX 17 carries out the assignment… this word contains 16#F000 the values of the following ten words are indifferent and will be ignored by the CCX 17 console.
442 35012326 00 July 2006
Example of use
Appendices
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;
Value Comment Word number
%MW0
%MW1
%MW2
%MW3
%MW4
%MW5
%MW6 to
%MW15
10 rc
-1
16#CC17
16#000F
16#FF09
16#00FF
Marker
Command keys 1 to 4 are configured, the others are not.
Key 1 in edge mode (01), key 2 in toggle mode (02), keys 3 and 4 inhibited (00), the others not programmed (11)
Key 1 affected by bit %M10
Key 1 affected by bit %M11
Keys 3 to 8 not affected
35012326 00 July 2006
443
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 parameter coding
Meaning
1
2
Word number
The table below shows the significance of the different words which constitute the following parameter: Data to send (3 words maximum).
3 contains a marker of value 16#CC17, contains the command number: z 1: clear screen, z 2: clear a line, z z z
9: print the alarm message log,
10: clear the alarm message log,
11: print the alarm log z z z
13: clear the alarm log,
29: clear the alarm (from 1 to 300) destined for CCX 17,
30: clear the alarm (from 900 to 999) destined for the PLC.
indicates the command parameter.
z clear line = line number, z z cancel alarm = alarm number, 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;
Value Comment Word number
%MW0
%MW1
16#CC17
1
Marker
Clear screen
444 35012326 00 July 2006
Glossary
A
AS-i V2
AS-interface
Actuator Sensor interface version 2, accepting extended address slaves.
Actuator Sensor interface.
C
CCX17
Channel group
CPU
Family of Schneider Automation Human-Machine Interface terminal.
Channels of the same type with common parameters. This notion concerns certain application-specific modules such as discrete modules.
Central Processing Unit: generic name used for Schneider Automation processors
D
Discrete Discrete I/Os
35012326 00 July 2006
445
Glossary
F
FIPIO
I
IP67
Field bus used to connect sensor or actuator type devices.
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.
M
Momentum I/O modules using several open standard communication networks.
P
PL7 Junior and
Pro
PV
Schneider Automation PLC programming software.
Identifier indicating the product version.
T
TBX I/O modules remoted on the FIPIO bus.
TSX/PMX/PCX57 Families of Schneider Automation hardware products.
446 35012326 00 July 2006
Index
Symbols
A
Access to the configuration editor
Accessing the configuration editor, 66
Accessing the debug editor
Adding a profile
Adding a slave
Adding an
Addressing
Adjustement
35012326 00 July 2006
A C
Adjustment objects
Advanced operation
Analog Parameters
Analog Value Modification
Application-specific function
Application-specific instructions, 62
AS-i slave
Automatic slave addressing
B
Built-in application-specific interfaces, 30
447
Index
C
Channel diagnostics
Channel fault
Combination of parameters
Command objects
Configuration of reflex function blocks, 205
Configuration screen
Configuring slaves
Configuring the reflex function blocks, 202
Confirming the configuration, 73, 74
Connect
Connecting
Constants
D
Data exchange off mode
Debug screen
Debugging
448
Debugging Screen
Debugging screen
Declaration of a module on the FIPIO bus, 71
Declaration of an I/O module, 70
Device Connection
Device connection
Diagnostics mode
E
Event
Explicit objects, 143, 145, 146, 147, 149,
External errors
F
Fallback to 0
35012326 00 July 2006
Family
Fault processing by program, 75
Faulty slave
Function
G
I
Implicit objects
Indexable objects
Internal errors
L
Language objects, 141, 143, 145, 146, 147,
35012326 00 July 2006
Index
M
Maintain
Maintain outputs
Master/Slave
Module diagnostics
Module fault
Module number
Module selection
O
Offline mode
Operating mode
P
Parameter
Parameter Modification
Parameters
Discrete, 109, 110, 111, 112, 113, 115,
449
Index
In-rack discrete outputs, 101, 102
Momentum discrete outputs, 106
TBX discrete outputs, 104, 105
Performance
Performances
Processing of faults by program, 77
Profile
Protected mode
R
Reactivation
Reading adjustment parameters, 49
Reflex function configuration editor, 203
450
Reflex functions
Monostable with time delay, 170
Operation-idle timer with value selection,
Restoring adjustment parameters, 53
S
Saving adjustment parameters, 51
Security Device
Selecting the module
Selection of modules
35012326 00 July 2006
Slave Address Modification
Slave Insertion
Slave number
Slaves
Slaves' status
Slaves’ status
Software installation
Status objects
Structure of a standard address AS-i
Structure of an AS-i slave
Structure of an extended address AS-i slave
T
Task
TSX SAY 100
TSX SAY 100 module
TSX SAY 1000
TSX SAY 1000 module
35012326 00 July 2006
U
W
Wiring test mode
Writing adjustment parameters, 50
Index
451
Index
452 35012326 00 July 2006
Ladda ner
Offentlig länk uppdaterad
Den offentliga länken till din chatt har uppdaterats. You may view and manage your chat links after registration here.
Offentlig länk till dokument
Annons
