Pro - Read The Docs [PDF]

PL7 Junior/Pro Premium PLC Applications Specific Functions : Basic Function

3500267700

TLX DS 57 PL7 40E eng V4.0

2

Related Documentation

Related Documentation At a Glance

This manual is made up of 8 volumes:

l Volume 1

l l l l l l

l

TLX DS 57 PL7 40E 09.2000

l Common application-specific functions l All-or-Nothing Application l AS-i implementation l Application-specific operator dialog Volume 2 l Counting Application Volume 3 l Axes Control Application Volume 4 l Step by step Control Application Volume 5 l Electronic Cam Application Volume 6 l SERCOS movement command Application Volume 7 l Analog Application l PID Control Application l Weighing Application Volume 8 l Adjustment Application

3

Related Documentation

4

TLX DS 57 PL7 40E 09.2000

Table of Contents

About the book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Part I Shared application-specific functions . . . . . . . . 15 Presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Chapter 1

Common application specific functions: General . . . . . . . . . . 17 Presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . General Presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration of an application-specific function. . . . . . . . . . . . . . . . . . . . . . . . . Adjustment of an application-specific function . . . . . . . . . . . . . . . . . . . . . . . . . . Debugging an application-specific function . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 2 2.1

2.2 2.3

2.4

17 18 20 22 23

Objects associated with specific applications . . . . . . . . . . . . 25 Presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Addressing of language objects associated with specific applications . . . . . . . . Presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Addressing of built-in application-specific interfaces. . . . . . . . . . . . . . . . . . . . . . Addressing of language objects for modules remoted on the FIPIO bus . . . . . . Addressing of language objects for modules remoted on the FIPIO bus . . . . . . Addressing of language objects associated with AS-i bus . . . . . . . . . . . . . . . . . Implicit exchanges. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Implicit exchanges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Explicit exchanges. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Presymbolization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

25 27 27 28 30 33 36 38 38 40 40 41 44 46 47 48 49 51 52 55 55 5

Presymbolized objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 Automatic symbolization of objects associated with a channel . . . . . . . . . . . . . . 57

Chapter 3

Application-specific instructions . . . . . . . . . . . . . . . . . . . . . . . 59 Presentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 Application-specific instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 Accessing a specific function, method or procedure type instruction . . . . . . . . . 61

Chapter 4

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

Part II Discrete specific application . . . . . . . . . . . . . . . 75 Presentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Chapter 5

General presentation of the discrete application -specific function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 Presentation of the discrete specific application . . . . . . . . . . . . . . . . . . . . . . . . . 77

Chapter 6 6.1

6.2

6.3

6

Configuration of the discrete specific application . . . . . . . . . 79 Presentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 Configuring a discrete module: General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 Presentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 Description of the configuration screen for a discrete module . . . . . . . . . . . . . . . 82 Accessing the configuration screen for an in -rack discrete module. . . . . . . . . . . 84 Accessing the configuration screen for a discrete module remoted on the FIPIO bus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 Modifying the configuration parameters of a discrete module’s: General . . . . . . 87 Discrete input channel parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 Presentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 In-rack discrete input parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 Parameters of TBX discrete inputs remoted on the FIPIO bus . . . . . . . . . . . . . . 91 Parameters of Momentum discrete inputs remoted on the FIPIO bus. . . . . . . . . 92 Parameters of IP67 discrete inputs remoted on the FIPIO bus . . . . . . . . . . . . . . 93 Discrete output channel parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 Presentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 Discrete output parameters for in-rack 8-channel modules. . . . . . . . . . . . . . . . . 95 Discrete output parameters for in-rack modules with over 8 channels . . . . . . . . 96

6.4

Chapter 7

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

Debugging discrete modules . . . . . . . . . . . . . . . . . . . . . . . . . 115 At a Glance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 8 8.1

8.2

115 116 117 119 120 121 122 123 124 125 126

Bits and words associated with discrete specific applications . . . . . . . . . . . . . . . . . . . . . 127 Presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 Addressing of discrete I/O module objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129 Presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129 Addressing of language objects associated with discrete in-rack I/O modules. 130 Addressing of language objects associated with discrete I/O modules remoted on the FIPIO bus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 Indexable discrete I/O objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132 Language objects associated with the discrete specific application . . . . . . . . . 133 Presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133 Implicit exchange language objects associated with the discrete specific application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134 7

Exchange management: Exchanges in progress module %[email protected]:Xj or channel %[email protected]:Xj . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 Exchange management: Module %[email protected]:Xj or channel %[email protected]:Xj report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137 Explicit exchange objects: General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138 Explicit exchange object: %[email protected]:Xj channel status . . . . . . . . . . . . 139 Explicit exchange object: Status Module %[email protected]:Xj. . . . . . . . . 140 Explicit exchange object: %[email protected]:Xj channel command . . . . . . . . . 142

Chapter 9 9.1 9.2

9.3

8

Installation of the discrete reflex module . . . . . . . . . . . . . . . 143 Presentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143 General presentation of discrete reflex module . . . . . . . . . . . . . . . . . . . . . . . . . 145 Presentation of discrete reflex module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145 Reflex function blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147 Presentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147 Function block: Direct . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148 Reflex function block: Combinational. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149 Reflex function block: Operation timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150 Reflex function block: Idle timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151 Reflex function block: Operation-idle timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152 Reflex function block: 2 value operation timer . . . . . . . . . . . . . . . . . . . . . . . . . . 153 Reflex function block: Operation-idle time with value selection . . . . . . . . . . . . . 155 Reflex function block: Retriggerable monostable. . . . . . . . . . . . . . . . . . . . . . . . 158 Reflex function block: Monostable with time delay . . . . . . . . . . . . . . . . . . . . . . 159 Reflex function block: 2 value monostable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161 Reflex function block: Oscillator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163 Reflex function block: D flip-flop. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164 Reflex function block: T flip-flop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 Reflex function block: 2 threshold counter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168 Reflex function block: Came électronique simple . . . . . . . . . . . . . . . . . . . . . . . 170 Reflex function block: 1 threshold intervalometer . . . . . . . . . . . . . . . . . . . . . . . 172 Reflex function block: Burst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 Reflex function block: PWM (Pulse Width Modulation) . . . . . . . . . . . . . . . . . . . 175 Reflex function block: Detection of underspeed. . . . . . . . . . . . . . . . . . . . . . . . . 176 Reflex function block: Speed monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178 Reflex function block: Type 1 command-check . . . . . . . . . . . . . . . . . . . . . . . . . 181 Reflex function block: Type 2 command-check . . . . . . . . . . . . . . . . . . . . . . . . . 183 Reflex function block: Command-counting . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186 Reflex function block: Fault Signaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188 Configuration of discrete reflex module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190 Presentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190 Configuring the discrete reflex module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191 Presentation of the reflex function configuration editor . . . . . . . . . . . . . . . . . . . 192 Assigning and configuring a reflex function . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194 Adjusting the configuration parameters of a reflex function . . . . . . . . . . . . . . . . 195 Associating an event with a virtual output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196

9.4

Bits and words associated with discrete reflex module . . . . . . . . . . . . . . . . . . . 198 Presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198 Implicit exchange language objects associated with module TSX DMY 28 RFK199 Explicit exchange language objects associated with module TSX DMY 28 RFK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202

Part III AS-i Bus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .203 At a Glance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203

Chapter 10

General introduction to the AS-i Bus . . . . . . . . . . . . . . . . . . . 205 At a Glance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 11

AS-i bus configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .213 At a Glance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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. . . . . . . . . . . . .

Chapter 12

13.1

213 214 216 219 220 222 224 225

Debugging the AS-i bus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227 At a Glance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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 . . . . . . . . . . . . . . . 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 . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 13

205 206 208 210 211 212

227 228 229 231 233 235 236 237 238 239 240

Bits and words associated with the AS-i function . . . . . . . . 241 At a Glance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241 Addressing objects associated with the AS-i function . . . . . . . . . . . . . . . . . . . . 243 Adressing language objects associated with slave devices connected to the AS-i bus. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243 9

13.2

Chapter 14

Language objects associated with the AS-i function . . . . . . . . . . . . . . . . . . . . . 244 At a Glance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244 Implicit exchange objects associated with the AS-i function . . . . . . . . . . . . . . . 245 Management of exchanges: Module %MWxy.MOD.0:Xj or channel MWxy.0.0 :Xj exchanges in progress. . . . . . . . . . . . . . . . . . . . . . . . 246 Exchange management: Module %MWxy.MOD.1:Xj or channel %MWxy.i.1:Xj report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247 Explicit exchange objects: General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248 Explicit exchange objects: %MWxy.0.2:Xj to %MWxy.0.23:Xj channel status. . 249 Explicit exchange object: %MWxy.0.24:Xj channel command. . . . . . . . . . . . . . 251 Explicit exchange object: %MWxy.0.25 to %MWxy.0.56 parameter adjustment 252 Explicit exchange object: Status %MWxy.MOD.2:Xj . . . . . . . . . . . . . . . . . . . . . 253

AS-i operating mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255 At a Glance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255 AS-i operating mode: General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256 AS-i protected mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259 AS-i wiring test mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260 AS-I offline operating mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261 AS-i data exchange off operating mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262

Chapter 15

AS-i performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263 AS-i bus performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263

Part IV Operator Dialog functions . . . . . . . . . . . . . . . . 265 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265

Chapter 16

General presentation of the Operator Dialog functions . . . . 267 General presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267

Chapter 17 17.1

17.2

10

Built-in DOP functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269 Description of the parameters common to the different DOP functions. . . . . . . 271 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272 Parameters field: Console address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273 Parameters field: Data to be sent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277 Parameter field: Data to be received: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279 Parameters field: Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280 Message field. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284 Field zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286 Description of the built-in DOP functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288 List of the built-in DOP functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289 SEND_MSG function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290 GET_MSG function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293

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. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 18 18.1 18.2

296 298 301 302 305 308 309 312 315 318 321

Appendices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .331 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331 Precautions for DOP use. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333 Precautions for DOP use. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333 Description of the built-in DOP functions "Data to send" parameter coding . . . 334 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334 PLC status message display: SEND_MSG function . . . . . . . . . . . . . . . . . . . . . 335 PLC checked status message entry: ASK_MSG and GET_MSG function . . . . 338 PLC alarm message display: SEND_ALARM function . . . . . . . . . . . . . . . . . . . 343 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346 Display of luminous column LEDS: CONTROL_LEDS function . . . . . . . . . . . . 347 Configuring command keys: ASSIGN_KEYS function . . . . . . . . . . . . . . . . . . . 348 Generic send command: PANEL_CMD function. . . . . . . . . . . . . . . . . . . . . . . . 350

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .351 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .353

11

12

About the book

At a Glance Document Scope

This manual deals with the software implementation of the applications (except communication tasks) on the TSX/PMX/PCX57 using PL7 software.

Validity Note

This updated publication takes account of the functionality of PL7 V3.4. It nevertheless supports the implementation of previous versions of PL7.

Related Documents

User Comments

TLX DS 57 PL7 40E 09.2000

Title of Documentation

Reference Number

Hardware installation manual

TSX DM 57 40E

We welcome your comments about this document. You can reach us by e-mail at [email protected]

13

About the book

14

TLX DS 57 PL7 40E 09.2000

Shared application-specific functions

I

Presentation Subject of this part

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

What’s in this part?

This Part contains the following Chapters:

TLX DS 57 PL7 40E 09.2000

Chapter

Chaptername

Page

1

Common application specific functions: General

17

2

Objects associated with specific applications

25

3

Application-specific instructions

59

4

Appendices

63

15

Shared application-specific functions

16

TLX DS 57 PL7 40E 09.2000

Common application specific functions: General

1

Presentation Subject of this chapter

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

What’s in this Chapter?

This Chapter contains the following Maps:

TLX DS 57 PL7 40E 09.2000

Topic

Page

General Presentation

18

Configuration of an application-specific function.

20

Adjustment of an application-specific function

22

Debugging an application-specific function

23

17

General

General Presentation Introduction

The PL7 software allows for the installation of application-specific functions in software form (DISCRETE, analog, process control, weighing, etc.). The application-specific functions are automated functions which interface with the control part (the PLC program) and the operational part (sensors, actuators and man/machine interfaces). An application-specific function on TSX Premium is presented, depending on the application, in the form of: l a module (e.g.: counting application), l a built-in interface (e.g.: communication port).

0

Integrated interface 0

18

P S Y 2 6 0 0

T S X 5 7 1 0 3

1

o o C o m m

2

3

C T Y 4 A

4

Application-specific module

TLX DS 57 PL7 40E 09.2000

General

Software installation principle

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

Phase

Description

Local

Configuration

Configuration of the module or built-in interface

Local or online

Symbolization

Symbolization of variables associated with the application-specific function.

Programming

Online

Local (or online)

Programming of the function to be carried out using: bit and word objects associated with the module, application-specific instructions.

l l

Transfer

Transferring the application to the PLC.

Debug

Debugging the application (I/O control, fault identification).

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).

Software installation resources

An application-specific function is installed using:

l standard PL7 tools:

l pull-down menus, l status bars, tool bars, l editors, l ... l application-specific screens, l configuration screens, l adjustment screens, l debug screens, l language objects giving program-based access to inputs and outputs of the module or built-in interface. l instructions relative to the application-specific function, where applicable. Note: The different screens as well as the objects associated with an 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.

TLX DS 57 PL7 40E 09.2000

19

General

Configuration of an application-specific function Introduction

The Configuration function makes it possible to define the operating characteristics of the module or the application-specific interface. This function is carried out from the PL7 configuration editor:

l in local mode, l in online mode when the application is stored in non-write protected RAM (limited to certain parameters). Note: The configuration parameters are not modifiable by program.

Illustration

The screen below is an example of a configuration screen of an application-specific module (application-specific module TSY CTY 4A). TSX CTY 4A [RACK 0 POSITION 4 ] Configuration Designation : 4 CH COUNTER MOD 40KHZ Symbol : Counter : des cames Counter 0

Function: des cames Up/Down counting

Input interfaces IA Up/Down counts, application direction Solid state counter Multiply Line check by 1 by 4 Preset on IPres Rising edge IPres

Task : des cames MAST Event EVT

3

Reset Outputs Manual Automatic Fallback Mode Reset Maintain

Read on IRead Rising edgeIRead

Here, the operating characteristics are:

l the selection of a function associated with a channel: up counting, down counting l l l l

20

or up/down counting, selection of the task which updates the inputs/outputs of the module, the type of reactivation of outputs, the type of fallback mode, ...

TLX DS 57 PL7 40E 09.2000

General

Confirmation

TLX DS 57 PL7 40E 09.2000

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

21

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:

l in local mode, in order to define the initial parameters (value of the parameters during setup or on a cold restart),

l in online mode, in order to define the current parameters (values lost upon cold restart if they have not been saved in advance). Note: The adjustment parameters are modifiable by program.

Illustration

The screen below is an example of an adjustment screen of an application-specific module (application-specific module TSY CTY 4A). TSX CTY 4A [RACK 0 POSITION 7 ] Adjust Designation : 4 CH COUNTER MOD.

Symbol : Counter : Counter 0

Function: Up/Down counting

Counter output state

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

Here, the operating parameters are:

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

22

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

TLX DS 57 PL7 40E 09.2000

General

Debugging an application-specific function Introduction

The Debug function of the module or the built-in application-specific interface provides the tools to help with debugging of the application-specific function such as: l display of module channel status, l display of possible faults, l control of language objects, l and, in the event of a fault, access to the module or channel diagnostics, l ... This function is carried out in online mode, with the PLC in STOP or in RUN, from the PL7 debug editor.

Illustration

The screen below is an example of a debug screen of an application-specific module (application-specific module TSX DSY 08R5). TSX DSY 08R5 [RACK 0 POSITION 3] Debug Designation : 8O RELAY 50VA, BORN Version : 1.0 Global unforcing

Chan. 0 1 2 3 4 5 6 7

Symbol

State 0 0 0 0 0 0 0 0

Fault DIAG... DIAG... DIAG... DIAG... DIAG... DIAG... DIAG... DIAG...

RUN

Reactivate Reactivate

ERR

Applied Q STOP

IO

DIAG...

Control of channel

x

Forcing F4

Force to 0

F5

Force to1

F6

Unforce

Write F7

Set

F8

Reset

Here the debug tools are:

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

TLX DS 57 PL7 40E 09.2000

23

General

24

TLX DS 57 PL7 40E 09.2000

Objects associated with specific applications

2

Presentation Subject of this chapter

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

What’s in this Chapter?

This Chapter contains the following Sections:

TLX DS 57 PL7 40E 09.2000

Section

Topic

Page

2.1

Addressing of language objects associated with specific applications

27

2.2

Implicit exchanges

38

2.3

Explicit exchanges

40

2.4

Presymbolization

55

25

Objects associated with specific applications

26

TLX DS 57 PL7 40E 09.2000

Objects associated with specific applications

2.1

Addressing of language objects associated with specific applications

Presentation Subject of this section

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

What’s in this Section?

This Section contains the following Maps:

TLX DS 57 PL7 40E 09.2000

Topic

Page

Addressing of built-in application-specific interfaces

28

Addressing of language objects for modules remoted on the FIPIO bus

30

Addressing of language objects for modules remoted on the FIPIO bus

33

Addressing of language objects associated with AS-i bus

36

27

Objects associated with specific applications

Addressing of built-in application-specific interfaces Presentation

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

Illustration

The illustration below shows the different basic topologies. Processor slot 0

0

P S Y 2 6 0 0

0 T S X 5 7 1 5 3

F

1

2

3

4

i p i o

o o

C o m m

P S Y 8 5 0 0

1 T S X 5 7 1 5 3

F

2

3

4

i p i o

o o

C o m m

1 P S Y 8 5 0 0

T S X 5 7 4 5 3

L F o o p s

3

4

i p i o

o o C o m m

Processors slot 1

28

TLX DS 57 PL7 40E 09.2000

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

Communication interface

FIPIO interface

Process control channels

TSX 57-10/20/30 TSX 57-102/202/302/402 TSX 57-103

Channel x.0

Channel x.1

-

-

TSX 57-252/352/452 TSX 57-153

Channel x.2

TSX 57-203

-

TSX 57-303

Channels x.4 to x.18

TSX 57-253

Channel x.2

TSX 57-353

Channels x.4 to x.13 Channels x.4 to x.18

TSX 57-453

Channels x.4 to x.23

PMX 57-102/202

-

PMX 57-352/452 PCX 57-1012

Channels x.4 to x.13

Channels x.4 to x.13

Channel x.2 -

Channel 1

-

-

PCX 57-3512

Channel 2

PCX 57-203

-

Channels 4 to 13

PCX 57-353

Channel 2

Channels 4 to 18

(x):

0 when the processor is in slot 0, 1 when the processor is in slot 1,

TLX DS 57 PL7 40E 09.2000

29

Objects associated with specific applications

Addressing of language objects for modules remoted on the FIPIO bus Presentation

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

Illustration

Addressing is defined as follows:

30

%

I, Q, M, K

X, W, D, F

Symbol

Object type

Format

X Rack

Y Position

.

i

.

r

Channel no. Rank

TLX DS 57 PL7 40E 09.2000

Objects associated with specific applications

Syntax

The table below shows the different elements which constitute addressing.

Family

Element

Values

Meaning

Symbol

%

-

-

Object type

I Q

-

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.

M

-

Internal variable This read or write information is exchanged at the request of the application.

K

-

Internal constant This configuration information is only accessible in read-only.

X

-

Boolean For boolean-type objects, the X may be omitted.

W

16 bits

Single length.

D

32 bits

Double length

F

32 bits

Floating. The floating format used is that of IEEE standard 754-1985 (equivalent IEC 559).

p

0 or 1

Number of the processor’s position in the rack.

2

-

Channel number of the processor’s built-in FIPIO link.

c

1 to 127

Number of the connection point.

Format (size)

Module/channel address and connection point Module position

m

0 or 1

0 : base module,

Channel no.

i

0 to 127 or MOD

MOD: channel reserved for management of the module and the parameters shared by all channels.

Position

r

0 to 255 or ERR

ERR: indicates a module or channel fault.

TLX DS 57 PL7 40E 09.2000

1: extension module.

31

Objects associated with specific applications

Examples

The table below gives some examples of object addressing. Object

Meaning

%MW\0.2.1\0.5.2

Position 2 status word for the image bit of input 5 of the remote input base module located at connection point 1 of the FIPIO bus.

%I\0.2.1\0.7

image bit of input 7 of the remote input base module located at connection point 1 of the FIPIO bus.

%Q\0.2.1\1.2

image bit of output 2 of the remote output extension module located at connection point 1 of the FIPIO bus.

%I\0.2.2\0.MOD.ERR Fault information for the Momentum module located at connection point 2 of the FIPIO bus. %Q\1.2.3\0.0.ERR

0

P S Y 2 6 0 0

0 T S X 5 7 2 0 3

0

1

32

L

2

3

4

2

3

4

o o p s

o o C o m m

1

P S Y 2 6 0 0

A E Y 8 0 0

0

2

Fault information for channel 0 of module CCX17 located at connection point 3 of the FIPIO bus.

1

2

D S X 0 8 R 5

P S Y

3

4 A S Y

2 6 0 0

8 0 0

TLX DS 57 PL7 40E 09.2000

Objects associated with specific applications

Addressing of language objects for modules remoted on the FIPIO bus Presentation

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

Illustration

Addressing is defined as follows: % Symbol

TLX DS 57 PL7 40E 09.2000

I, Q, M, K

X, W, D, F \

Object type

Format

p.2.c

\

Module/channel address and connection point

m Module number

.

i

.

Channel number

r Rank

33

Objects associated with specific applications

Syntax

The table below shows the different elements which constitute addressing.

Family

Element

Values

Meaning

Symbol

%

-

-

Object type

I Q

-

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.

M

-

Internal variable This read or write information is exchanged at the request of the application.

K

-

Internal constant This configuration information is only accessible in read-only.

X

-

Boolean For boolean-type objects, the X may be omitted.

W

16 bits

Single length.

D

32 bits

Double length

F

32 bits

Floating. The floating format used is that of IEEE standard 754-1985 (equivalent IEC 559).

Module/channel address and connection point

p

0 or 1

Number of the processor’s position in the rack.

2

-

Channel number of the processor’s built-in FIPIO link.

c

1 to 127

Number of the connection point.

Module position

m

0 or 1

0 : base module,

Channel no.

i

0 to 127 or MOD

MOD: channel reserved for management of the module and the parameters shared by all channels.

Position

r

0 to 255 or ERR

ERR: indicates a module or channel fault.

Format (size)

34

1: extension module.

TLX DS 57 PL7 40E 09.2000

Objects associated with specific applications

Examples

The table below gives some examples of object addressing. Object

Meaning

%MW\0.2.1\0.5.2

Position 2 status word for the image bit of input 5 of the remote input base module located at connection point 1 of the FIPIO bus.

%I\0.2.1\0.7

image bit of input 7 of the remote input base module located at connection point 1 of the FIPIO bus.

%Q\0.2.1\1.2

image bit of output 2 of the remote output extension module located at connection point 1 of the FIPIO bus.

%I\0.2.2\0.MOD.ERR Fault information for the Momentum module located at connection point 2 of the FIPIO bus. %Q\1.2.3\0.0.ERR

0

TLX DS 57 PL7 40E 09.2000

Fault information for channel 0 of module CCX17 located at connection point 3 of the FIPIO bus.

FIPIO manager TSX 57253

1

TBX LEP 030

0 TBX DES 1622

2

170 FNT 110 01

0 170 AAI 030 00

3

TSX FPP 010

0 T CCX 17 20 F

1 TBX DSS 1622

35

Objects associated with specific applications

Addressing of language objects associated with AS-i bus Presentation

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

Illustration

Addressing is defined as follows:

Syntax

%

I ou Q

Symbol

Object type

\

xy.0

\

Rack/module/channel addrss for TSX SAY 100

n Slave number

.

i Bit rank

The table below describes the different elements which constitute addressing.

Family

Element

Values

Description

Symbol

%

-

-

Object type

I Q

-

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.

Rack address

x

0 or 1 0 to 7

TSX 5710/102/103/153, PMX 57102, PCX 571012). Other processors

Module position

y

00 to 14 (1)

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).

Channel no.

0

-

The interface card TSX SAY 100 only has one channel.

Slave no.

n

0 to 31

Physical address of slave.

Position

i

0 to 3

Position of output or input image bit.

(1) : The maximum number of slots requires the use of 2 racks at the same address.

36

TLX DS 57 PL7 40E 09.2000

Objects associated with specific applications

Example

The table below gives some examples of object addressing. Object

Description

%I3.0\2.2

Input 2 of slave 2, the module TSX SAY 100 being positioned at slot 3 of rack 0.

%Q3.0\4.3

Output 3 of slave 4, the module TSX SAY 100 being positioned at slot 3 of rack 0.

0

0

P S Y 2 6 0 0

T S X 5 7 1 0 3

1

2

3

4

S A Y 1o 0o 0Co

m m

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

TLX DS 57 PL7 40E 09.2000

37

Objects associated with specific applications

2.2

Implicit exchanges

Implicit exchanges Presentation

A built-in specific application interface where the addition of a module automatically enhances the application of language objects making it possible to program this interface or module. These objects correspond to the images of the I/Os of the module or built-in specific application module. The %I bits and the %IW words, images of the module’s input values are updated automatically in the PLC processor at the start of the task, whether the task is in RUN or STOP mode. The %Q bits and %QW words, images of the module’s output values are updated automatically in the module by the processor at the end of the task, with the task in RUN mode. Note: When the task in STOP mode, depending on the configuration chosen: l the outputs are in the fallback position (fallback mode), l the outputs are maintained at their last value (maintain mode).

Illustration

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

Internal processing

Acquisition of input RUN

STOP

Program processing

Updating of output

38

TLX DS 57 PL7 40E 09.2000

Objects associated with specific applications

Examples Object

The table below shows several examples of implicit exchanges relating to a given application. Specific application

Description

%I103.1

Discrete

Gives the status of channel 1 of the module located in position 3 of rack 1.

%IW4.2

Analog

Gives the analog value of channel 2 of the module located in position 4 of rack 0.

%IW203.2:X4

Counting

Gives the status of the capture input of the module located in position 3 of rack 2.

%Q306.5

Discrete

Gives the status of channel 5 of the module located in position 6 of rack 3.

%I6.5.ERR

-

Indicates, when the bit is set to 1, that channel 5 of the module located in position 6 of rack 0 is faulty.

%I107.MOD.ERR -

Indicates, when the bit is set to 1, that the module located in position 7 of rack 1 is faulty.

TLX DS 57 PL7 40E 09.2000

39

Objects associated with specific applications

2.3

Explicit exchanges

Presentation Subject of this section

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

What’s in this Section?

This Section contains the following Maps:

40

Topic

Page

Explicit exchanges: General

41

READ_STS: Reading status words

44

WRITE_CMD: Writing command words

46

READ_PARAM: Reading adjustment parameters

47

WRITE_PARAM: Writing adjustment parameters

48

SAVE_PARAM: Saving adjustment parameters

49

RESTORE_PARAM: Restoring adjustment parameters

51

Exchange and report management

52

TLX DS 57 PL7 40E 09.2000

Objects associated with specific applications

Explicit exchanges: General Introduction

Explicit exchanges are exchanges performed at the request of the user program using the following instructions: l READ_STS (reading status words), l WRITE_CMD (writing command words) l WRITE_PARAM (writing adjustment parameters), l READ_PARAM (reading adjustment parameters), l SAVE_PARAM (saving adjustment parameters), l RESTORE_PARAM (restoring adjustment parameters), These exchanges apply to a set of %MW objects of the same type (status, commands or parameters) on the same channel. Note: These objects are not necessary for the programming of an 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).

TLX DS 57 PL7 40E 09.2000

41

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). E/S Module or interface built-in task

PLC processor %MWxy.i.r objects or %MWxy.MOD.r (1) Status words Command words

READ_STS WRITE_CMD

Status words Command words

WRITE_PARAM Adjustment parameters current

READ_PARAM SAVE_PARAM Adjustment parameters current

Adjustment parameters initial

RESTORE_PARAM

Only with the READ_RTS and WRITE_CMD instructions.

42

TLX DS 57 PL7 40E 09.2000

Objects associated with specific applications

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: l detection of an exchange in progress, l the end of exchange report. The summary below explains the principle for management of an exchange Execution of an explicit exchange

Logical channel %CHxy.i

Detection of an exchange in progress

Report of the end of the exchange

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

TLX DS 57 PL7 40E 09.2000

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.

43

Objects associated with specific applications

READ_STS: Reading status words Introduction

Status words contain information about the functioning state of the module or the channel. The READ_STS instruction allows reading in the module (or in the built-in interface) of these kind of words. This reading updates the %MW status words . These words can be used to carry out diagnostics by program. Note: The status words are specific to each task. However, 2 words are used by all of the modules in the TSX Premium range: l %MWxy.MOD.2 (module level fault), l %MWxy.i.2 (channel i level fault).

Illustration

Writing instruction E/S Module or interface built-in task

Processor PLC Objects %MWxy.ir or %MWxy.MOD.2 Status words

44

READ_STS

Status words

TLX DS 57 PL7 40E 09.2000

Objects associated with specific applications

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.

Examples

TLX DS 57 PL7 40E 09.2000

Element

Description

READ_STS

Name of the instruction

%CH

Channel-type object

x

Rack address.

y

Module position.

i

Channel or MOD number.

The example below presents some examples of explicit exchanges using the READ_STS instruction. Object

Description

READ_STS%CH302.1

Reading the status words of channel 1, which is on the module situated in position 2 in rack number 3.

READ_STS%CH401.MOD

Reading the status words of the module situated in position 1 in rack 4.

45

Objects associated with specific applications

WRITE_CMD: Writing command words Introduction

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

Illustration

Write instruction E/S Module or interface built-in task

Processor PLC Objects %MWxy.ir or %MWxy.MOD.2 WRITE_CMD

Command words

Syntax

Command words

The WRITE_CMD instruction is defined as follows: WRITE_CMD%CHxy.i The table below describes the different elements which constitute the instruction.

Examples

46

Element

Description

WRITE_CMD

Name of instruction.

%CH

Channel-type object.

x

Rack address.

y

Module position.

i

Channel number.

The table below gives an example of an explicit exchange using the WRITE_CMD instruction. Object

Description

WRITE_CMD%CH3.0

Writing the command information of channel 0 of the module located in position 3 of rack 0.

TLX DS 57 PL7 40E 09.2000

Objects associated with specific applications

READ_PARAM: Reading adjustment parameters Introduction

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

Illustration

Read instruction E/S Module or interface built-in task

Processor PLC %MWxy.i.r objects READ_PARAM

Current adjustment parameters

Syntax

Current adjustment parameters

The READ_PARAM instruction is defined as follows: READ_PARAM%CHxy.i The table below describes the different elements which constitute the instruction.

Examples

TLX DS 57 PL7 40E 09.2000

Element

Description

READ_PARAM

Name of instruction.

%CH

Channel-type object.

x

Rack address.

y

Module position.

i

Channel number.

The table below gives an example of an explicit exchange using the READ_PARAM instruction. Object

Description

READ_PARAM%CH3.1

Reading the adjustment parameters of channel 1 of the module located in position 3 of rack 0.

47

Objects associated with specific applications

WRITE_PARAM: Writing adjustment parameters Introduction

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

Illustration

Write instruction E/S Module or interface built-in task

Processor PLC %MWxy.i.r objects WRITE_PARAM Adjustment parameters current

Syntax

Adjustment parameters current

The WRITE_PARAM instruction is defined as follows: WRITE_PARAM%CHxy.i The table below describes the different elements which constitute the instruction. Element

Examples

Description

WRITE_PARAM

Name of instruction.

%CH

Channel-type object.

x

Rack address.

y

Module position.

i

Channel number.

The table below gives an example of an explicit exchange using the WRITE_PARAM instruction. Object

Description

WRITE_PARAM%CH303.1 Writing the adjust parameters of channel 1 of the module located in position 3 of rack 3.

48

TLX DS 57 PL7 40E 09.2000

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 E/S Module or interface built-in task

Processor PLC %MWxy.i.r objects Adjustment parameters current

SAVE_PARAM

Adjustment parameters current

Adjustment parameters initial

TLX DS 57 PL7 40E 09.2000

49

Objects associated with specific applications

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.

Examples

50

Element

Description

SAVE_PARAM

Name of the instruction.

%CH

Channel-type object.

x

Rack address.

y

Module position.

i

Channel number.

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.

TLX DS 57 PL7 40E 09.2000

Objects associated with specific applications

RESTORE_PARAM: Restoring adjustment parameters Introduction

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

Illustration

Writing instruction Processor PLC

E/S Module or interface built-in task

%MWxy.i.r objects Adjustment parameters current

RESTORE_PARAM

Adjustment parameters current

Adjustment parameters initial

Syntax

The RESTORE_PARAM instruction is defined in the following way: RESTORE_PARAM%CHxy.i The table below describes the different elements that are part of the instruction.

Examples

TLX DS 57 PL7 40E 09.2000

Element

Description

RESTORE_PARAM

Name of the instruction

%CH

Channel-type object.

x

Rack address.

y

Module position.

i

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.

51

Objects associated with specific applications

Exchange and report management Introduction

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

Illustration

The illustration below shows the various bits which are significant for exchange management. Reconfiguration (X15) Adjust (X2) Command (X1) State (X0) %MWxy.i.0 %MWxy.i.1 Status words

Command words

Adjustment parameters

52

READ_STS

WRITE_CMD WRITE_PARAM READ_PARAM SAVE_PARAM RESTORE_PARAM

TLX DS 57 PL7 40E 09.2000

Objects associated with specific applications

Description of significant bits

Each of the bits of the words %MWxy.i and %MWxy.i.1 is associated with a type of parameter: l position 0 bits are associated with status parameters: l the bit %MWxy.i.0:X0 indicates whether a status word read request is in progress, l position 1 bits are associated with command parameters: l the bit %MWxy.i.0:X1 indicates whether the control parameters have been sent to channel i of the module, l the bit %MWxy.i.1:X1 specifies whether the control parameters have been accepted by channel i of the module, l position 2 bits are associated with adjustment parameters: l the bit %MWxy.i.0:X2 indicates whether the adjustment parameters have been exchanged with channel i of the module (by WRITE_PARAM, READ_PARAM, SAVE_PARAM, RESTORE_PARAM), l the bit %MWxy.i.1:X2 specifies whether the adjustment parameters have been accepted by the module. If the exchange has been made successfully the bit is set to 0, l the position 15 bits indicate that channel i of the module has been reconfigured from the terminal (modification of the configuration parameters + cold start of the channel). Note: The exchange and report words also exist at module level (%MWxy.MOD and %MWxy.MOD.1).

TLX DS 57 PL7 40E 09.2000

53

Objects associated with specific applications

Example

Phase 1: Transmission of data using the WRITE_PARAM instruction PLC memory 1 0

E/S module memory or built-in application specific function

Status words Command words

Status words Command words

Current adjustment parameters

Current adjustment parameters

When the instruction is scanned by the PLC processor, the Exchange in progress bit is set to 1 in %MWxy. Phase 2: Analysis of data by the I/O module and report PLC memory 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.

54

TLX DS 57 PL7 40E 09.2000

Objects associated with specific applications

2.4

Presymbolization

Presentation Purpose of this section

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

What’s in this Section?

This Section contains the following Maps:

TLX DS 57 PL7 40E 09.2000

Topic

Page

Presymbolized objects

56

Automatic symbolization of objects associated with a channel

57

55

Objects associated with specific applications

Presymbolized objects Role

Certain application specific functions (example: counting, axes request, …) support an automatic symbolization of the objects which are linked to them. If you give the generic symbol of the module’s %CHxy.i channel, all of the symbols of the objects linked to this channel can then be automatically generated on request.

Syntax

These objects are symbolized with the following syntax: PREFIX_USER_SUFFIX_MANUFACTURER The elements have the following meaning and characteristics: Element

Maximum number of characters

Description

PREFIX_USER

12

generic symbol given to the channel by the user

SUFFIX_MANUFACT URER

20

part of the symbol which corresponds to the bit object or word of the channel given by the system

Note: As well as the symbol, a manufacturer’s comment is automatically generated, this comment recalls succinctly the object’s role.

Example

This example shows a counting module situated in slot 3 of the automatic tray. If the generic symbol (prefix-user) given to channel 0 is COMPT_PIECES, the following symbols are automatically generated.

56

Address

Type

%CH3.0

CH

Symbol

Comment

%ID3.0

DWORD COMPT_PIECES_CUR-MEAS

Counter current value

%ID3.0.4

DWORD COMPT_PIECES_CAPT

Counter captured value

%I3.0

EBOOL

COMPT_PIECES_ENAB_ACTIV

Counter enable active

%I3.0.1

EBOOL

COMPT_PIECES_PRES_DONE

Preset done

TLX DS 57 PL7 40E 09.2000

Objects associated with specific applications

Automatic symbolization of objects associated with a channel Introduction

Conditions required

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:

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

Procedure

The table below shows the procedure for the automatic symbolization of objects associated with a channel. Step

De-activating automatic symbolization

Action

1

Access the variable editor.

2

Access to I/O type variables. Note: The channels whose objects can be symbolized have a letter P on the button to the left of the%CH address.

3

Double-click on the P button for the channel to be symbolized.

4

Enter the user prefix. Note: If a symbol is already defined for the channel, the prefix proposed is the retrieved symbol truncated to 12 characters.

5

Confirm with the Presymbolize button.

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 …

then …

Delete all presymbols

No prefix is chosen: all symbols are deleted (including those which have been modified directly using the editor).

Delete prefixed presymbols

Only objects with a prefix identical to that entered are deleted.

TLX DS 57 PL7 40E 09.2000

57

Objects associated with specific applications

58

TLX DS 57 PL7 40E 09.2000

Application-specific instructions

3

Presentation Subject of this chapter

This chapter presents the application-specific instructions.

What’s in this Chapter?

This Chapter contains the following Maps:

TLX DS 57 PL7 40E 09.2000

Topic

Page

Application-specific instructions

60

Accessing a specific function, method or procedure type instruction

61

59

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

60

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: l 10000000 is the coordinate to be attained in micrometers, l 200 is the movement speed of the moving part in mm/minute, l ...

TLX DS 57 PL7 40E 09.2000

Application-specific instructions

Accessing a specific function, method or procedure type instruction Presentation

TLX DS 57 PL7 40E 09.2000

Application-specific function entry can be accessed by:

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

61

Application-specific instructions

Calling up a function

Step

Action

1

Access the required editor.

2

Depending on the editor used, choose one of the following methods to open the function library. l Press Shift + F8 (LD, IL,ST editors). l Click on the ((LD editor) icon. l Select the command Utilities → Enter call for a ((IL, ST editors) function. Note: The function library appears. PL7 : Library functions

?

EF Function information

Parameters

Detail...

Name Family Lib.V. App.V Characters string 2.00 SMOVE Interpolation Command 1.0 Movement Command 2.00 Communication 3.07 Call format Parameters of the METHOD: Name Type Kind Comment Channel MAIN Channel NRUN WORD IN Movement number G9 World IN G9

Comment Automatic movement command

Family %CH103.2 01 90

Display the call SMOVE

%CH103.2

( 01.90.01.10000000.20000.0 OK

62

)

Cancel

3

Select the specific application in the Family field.

4

Select the instruction in the Name field.

5

Many of the instructions have a customized entry help screen. Access this screen by clicking on the Details button.

6

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

7

Click Ok to confirm.

TLX DS 57 PL7 40E 09.2000

Appendices

4

Presentation Subject of 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.

What’s in this Chapter?

This Chapter contains the following Maps:

TLX DS 57 PL7 40E 09.2000

Topic

Page

Reminders concerning the configuration editor

64

The PL7 toolbar

65

The PL7 status bar

66

How to declare a module in a PLC rack

67

How to declare a remote module on the FIPIO bus.

68

Confirming the configuration of a module.

70

Globally reconfiguring an application.

71

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

72

Processing of FIPIO faults

73

63

Appendices

Reminders concerning the configuration editor Presentation

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

Illustration

The following screen provides an example of a hardware configuration. Configuration XMWI XTI..

TSX 57103 V4.0 ...

0

0

P S Y 2 6 0 0

T S X 5 7 1 0 3

1

o o

C o m m

2

D E Y 0 8 D 2

3

D E Y 3 2 D 2 K

D S Y 1 6 R 5

4

5

C T Y 2 C

6

S C Y 2 1 6 0 1

I S P Y 1 0 0

1

Accessing the editor

The following table shows the different ways of accessing the configuration editor. From:

Action

the menu bar

Select Tools → Configuration.

the application browser

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

64

TLX DS 57 PL7 40E 09.2000

Appendices

The PL7 toolbar Presentation

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

Illustration

The PL7 toolbar is displayed as follows: RUN RUN STOP STOP

Elements and functions

? ?? ?

This table gives the function of each element in the toolbar: Element

Function

Element

Function

New application

Local mode

Open an application

Online mode

Save the application

RUN

PLC changes to RUN

Print all or part of the application

STOP

PLC changes to STOP

Undo last modifications

Start / Stop the animation

Confirm modifications

Organize windows so that they overlap

Go to

Tile windows horizontally

Application browser

Tile windows vertically

Cross references Function library

?? ??

Help What’s this?

PLC terminal transfer

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

TLX DS 57 PL7 40E 09.2000

65

Appendices

The PL7 status bar At a Glance

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

Illustration

The PL7 status bar appears thus: 1

2

Ready

Elements and functions

66

ONLINE

3

STOP

4

U:SYS

5

6

7

GR7 OK MODIF

8

OVR CAPS

This table describes the different zones that make up the status bar: Number Zone

Function

1

Information

supplies information concerning menu commands, toolbar icons and the different editors when these are selected.

2

Operating mode

indicates the current operating mode (offline, online).

3

PLC state

indicates the PLC state (Run, Stop, faulty, etc.).

4

Network address

gives the network address of the PLC.

5

Grafcet mode

indicates whether Grafcet mode is used in the application.

6

Modification in progress

indicates that the current application has not been saved or is different from the back-up.

7

Animation indicator

indicates that the PLC is in online mode.

8

Keyboard functions

indicates the status of the Insert and All Caps keyboard functions.

TLX DS 57 PL7 40E 09.2000

Appendices

How to declare a module in a PLC rack Procedure

This operation enables the user to make a software declaration of a module in a PLC rack. The example below concerns a Discrete module; the same procedure is used whatever the type of in-rack module. Step

Action

1

Access the application’s hardware configuration screen.

2

Double-click on the slot in which the module is to be configured. Result: the Add module screen appears. Add module Family:

Module: 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

Analog Module1.5 Communication1.5 Counting1.5 Remote BusX1.0 Movement1.5 Weighing1.5 Simulation1.0 Discrete I/O1.5

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

3

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

4

Select the module reference in the Module field.

5

Click on Ok to confirm the selection. Result: the module is declared in its slot; the slot is shown in gray and contains the module reference. Configuration XMWI XTI..

TSX 57452 V5.0 ...

0

0

P S Y 2 6 0 0

T S X 5 7 4 5 2

L

F

o o p s

i p i o

o o C o m m

2

3

4

D E Y 0 8 D 2

1

TLX DS 57 PL7 40E 09.2000

67

Appendices

How to declare a remote module on the FIPIO bus Procedure

This operation enables the user to make a software declaration of a module connected to the FIPIO bus. Note: This operation requires a processor with a built-in FIPIO link. Step

Action

1

Access the application’s hardware configuration screen.

2

Double-click on the processor’s FIPIO zone. Result: the FIPIO Configuration screen appears FIPIO Configuration TSX 57453 V5.0 Bus length:

0 1

Logical address

Communicator

15 km Devices configured: Base module

0

Fipio managerTSX 57453

63

Privileged terminal

0

Extension module

12

3

Double-click on one of the available connection points. Result: the Add/Modify device screen appears. Add/Modify a Device Connection point Connection number Comment

OK

1

Cancel

Families ATV-161.0 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 ATV16U09M2/60Hz ATV16U18M2/50Hz ATV16U18M2/60Hz ATV16U18N2/50Hz ATV16U18N2/60Hz ATV16U29M2/50Hz ATV16U29M2/60Hz

ATV16 0.37kw240V 240 V50Hz 50Hz ATV 0.37kw 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

68

TLX DS 57 PL7 40E 09.2000

Appendices

Step

Action

4

Enter the number of the connection point corresponding to the address where the module is to be connected (available addresses run from 1 - 62 and 64 - 127; addresses 0 and 63 are reserved by the system). By default, the PL7 software proposes the address for the selected connection point.

5

Enter a comment if necessary.

6

In the Family field, select the type of device to be connected to the bus. (e.g.: TBX, Momentum, etc.).

7

Select the base module.

8

9

Select, according to the type of device: the base module and/or extension module, the communicator. Note: l If the reference for the Momentum base module is not already proposed, select reference OTHER FRD.

l l

Click Ok to confirm. Result: the module is declared. FIPIO Configuration TSX 57453 V5.0 Bus length:

0

15 km

Devices configured:

1

1 Logical address

0

1

63

TLX DS 57 PL7 40E 09.2000

Communicator

Base module

Extension module

Fioio manager TSX 57453

TBX LEP 030

0

TBX ASS 200

1

TBX AES 400

Privileged terminal

69

Appendices

Confirming the configuration of a module Introduction

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

Illustration

The table below shows where the confirmation of a module’s configuration is positioned within the various hardware installation phases of an application. Step 1

Procedure

Declaration of a module:

2

Configuration of module channels.

3

Adjustment

4

Confirmation of the configuration of the module.

5

Declaration and/or parametering of new modules

6

Global confirmation of the application

The table below shows the procedure for confirming the configuration of a module. Step 1

70

Description

Action Select Edit → Confirm or use the icon

located in the toolbar.

TLX DS 57 PL7 40E 09.2000

Appendices

Globally reconfiguring an application Introduction

An application needs to be globally reconfigured in order for the modifications confirmed for each module to be taken into account. This is generally carried out in local mode, Note: Global reconfiguration of an application in online mode causes the module to stop.

Illustration

The table below shows where the global reconfiguration of an application is positioned within the various hardware installation phases of an application. Step

Procedure

Declaration of a module:

2

Configuration of module channels

3

Adjustment

4

Confirmation of the configuration of the module

5

Declaration and/or parametering of new modules

6

Global confirmation of the application

The table below shows the procedure for globally reconfiguring a module. Step

TLX DS 57 PL7 40E 09.2000

Description

1

Action

1

Select Edit → Confirm ... or use the icon

2

Confirm the reconfiguration:

located in the toolbar.

71

Appendices

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

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

Algorithm

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

%S10=0 ?

No

No default of input/output

No

Locate the default on the FIPIO bus via %S118 (1)

Yes Locate the default on the FIPIO bus via %S119

%S119 = 0 ? Yes Locate the rack at default %S40 to %S47

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

Diagnose the default module READ_STS %CHxy.MOD %MWxy.MOD.2

Locate the channel at default via %Ixy.i.ERR = 1

Diagnose the default channel READ_STS %CHxy.i %MWxy.i.2

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

72

TLX DS 57 PL7 40E 09.2000

Appendices

Processing of FIPIO faults Presentation

TLX DS 57 PL7 40E 09.2000

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.

73

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 ?

No

No default of input/output

No

Test the default on the X bus via %S119

Yes Locate the default on the FIPIO bus via %S118

%S118 = 0 ? Yes

Locate the default connection point via %I\p2c\m.MOD.ERR = 1

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

74

TLX DS 57 PL7 40E 09.2000

Discrete specific application

II

Presentation Subject of 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.

What’s in this part?

This Part contains the following Chapters: Chapter 5

TLX DS 57 PL7 40E 09.2000

Chaptername General presentation of the discrete application -specific function

Page 77

6

Configuration of the discrete specific application

7

Debugging discrete modules

79

8

Bits and words associated with discrete specific applications

127

9

Installation of the discrete reflex module

143

115

75

Discrete specific application

76

TLX DS 57 PL7 40E 09.2000

General presentation of the discrete application -specific function

5

Presentation of the discrete specific application Introduction

The Discrete application-specific function is applied:

l to rack-mounted discrete I/O modules l to discrete I/O modules remoted on the FIPIO bus. Note: In order to access the latter, the configured processor must have a built-in FIPIO link. In order to install the discrete specific 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 using the different PL7 editors: l either in local mode, l or in online mode; in this case, modification is limited to certain parameters. Note: Functions in online mode are not accessible for remote I/O modules.

TLX DS 57 PL7 40E 09.2000

77

General presentation

Installation principle

The table below shows the different installation phases of the discrete application-specific function.

Mode

Phase

Description

Local

Declaration of: Choice: an in-rack module (See How l of geographical position l number and slot for an in-rack module, to declare a module in a PLC rack, p. 67) l connection point for a remote module, l of module type. or a module remoted on the FIPIO bus (See How to declare a remote module on the FIPIO bus., p. 68) Configuration of module channels (See Configuration of discrete parameters, p. 103)

Entry of configuration parameters.

Adjustment (See Adjusting the configuration parameters of a reflex function, p. 195)

Entry of initial adjustment parameters (only on TSX DMY 28 FRK).

Confirmation of configuration Confirmation of module level. parameters (See Confirming the configuration of a module., p. 70)

Local or online

Online

Global confirmation of the application (See Globally reconfiguring an application., p. 71)

Confirmation of application level.

Symbolization

Symbolization of variables associated with the application-specific function.

Programming

Programming of functions to be performed by the specific application using: l bit and word objects associated with the module, l specific application instructions.

Transfer

Transfer of the application to the PLC.

Debug

Local or online

Documentation

Debugging of application using: debugging help screens enabling the user to control I/Os, diagnostics screens enabling the user to identify faults.

l l

Printing of the information on 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).

78

TLX DS 57 PL7 40E 09.2000

Configuration of the discrete specific application

6

Presentation Subject of this chapter

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

What’s in this Chapter?

This Chapter contains the following Sections:

TLX DS 57 PL7 40E 09.2000

Section

Topic

Page

6.1

Configuring a discrete module: General

81

6.2

Discrete input channel parameters

89

6.3

Discrete output channel parameters

94

6.4

Configuration of discrete parameters

103

79

Configuration of the discrete specific application

80

TLX DS 57 PL7 40E 09.2000

Configuration of the discrete specific application

6.1

Configuring a discrete module: General

Presentation Purpose of this section

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

What’s in this Section?

This Section contains the following Maps:

TLX DS 57 PL7 40E 09.2000

Topic

Page

Description of the configuration screen for a discrete module

82

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

84

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

86

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

87

81

Configuration of the discrete specific application

Description of the configuration screen for a discrete module Presentation

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

Illustration

This screen gives access to parameter viewing and modification in local mode, and debugging in online mode.

1

TBX DMY 28FK [RACK 0 POSITION 2] Configuration

2

3

82

Inputs

Designation : 16I 24VDC, 12O 24

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

Symbol

Supply Monit. Active

Task MAST

MAST

Filter 4 ms 4 ms 4 ms 4 ms 4 ms 4 ms 4 ms 4 ms 4 ms 4 ms 4 ms 4 ms 4 ms 4 ms 4 ms 4 ms

Function

TLX DS 57 PL7 40E 09.2000

Configuration of the discrete specific application

Description

The table below shows the different elements in the configuration screen, along with their functions.

Number

Element

Function

1

Title bar

Indicates the reference and physical position of the selected module along with the rack number for in-rack modules or the FIPIO connection point for remote I/Os.

2

Module zone

Enables the user t select: l the installation phase: l Configuration, l Adjustment (only for TSX DMY 28 RFK), l Installation (diagnostics), only accessible in online mode. l the type of channels (inputs or outputs), if the designated module has both inputs and outputs, l the program part for TBX DMS 16P22 modules. Displays the designation of the selected module. Displaying this zone is optional. The option is activated using the command View → Module zone.

3

Channel 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).

TLX DS 57 PL7 40E 09.2000

83

Configuration of the discrete specific application

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

This operation enables the user to access the configuration parameters for the channels of a discrete module. Step

Action

1

Access the module’s hardware configuration screen.

2

Double-click on the module to be configured or select the module and execute the command Service → Open the module. Result: The configuration screen for the selected module appears. TBX DMY 28FK [RACK 0 POSITION 2] Configuration

Inputs

Designation : 16I 24VDC, 12O 24 VDC

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

84

Symbol

Supply Monit. Active

Task MAST

MAST

Filter 4 ms 4 ms 4 ms 4 ms 4 ms 4 ms 4 ms 4 ms 4 ms 4 ms 4 ms 4 ms 4 ms 4 ms 4 ms 4 ms

Function

TLX DS 57 PL7 40E 09.2000

Configuration of the discrete specific application

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

Action

1

Perform one of the following: l right-click on the row in the table corresponding to the channel to be parametered and then select the Properties command from the pull-down menu, l or double-left-click on the row in the table corresponding to the channel to be parametered, l or select the Function cell of the channel to be parametered and then confirm using Enter. Result: The dialogue box appears, superimposed on the configuration screen. TBX DMY 28FK [RACK 0 POSITION 2] Configuration Designation : 16I 24VDC, 12O 24 Chan 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15

TLX DS 57 PL7 40E 09.2000

Symbol

Supply Active

Task MAST

MAST

Inputs

Filter Function 4 ms 4 ms Properties of channel 4 ms 4 ms 4 ms 4 ms Normal 4 ms Latch state 0 4 ms 4 ms Latch state 1 4 ms 4 ms Event procesing 4 ms 4 ms Rising 4 ms Falling 4 ms 4 ms EV 1

x

85

Configuration of the discrete specific application

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

This operation enables the user to access the configuration parameters for the channels of a discrete module remoted on the FIPIO bus. Step

Action

1

Access the module’s hardware configuration screen.

2

Double-click on the processor’s FIPIO zone.

3

Double-click on the module to be configured or select the module and execute the command Service → Open the module. Result: The configuration screen for the selected module appears. TBX CSP 1622 [FIPIO1

MODULE 0]

Configuration Designation : TBX7 MONOBLOC 16SO 24Vdc

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

86

Symbol

Task MAST

Reactivate Automatic

Automatic

TLX DS 57 PL7 40E 09.2000

Configuration of the discrete specific application

Modifying the configuration parameters of a discrete module’s: General Introduction

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

Accessing the 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

Selecting a group of consecutive channels

TLX DS 57 PL7 40E 09.2000

Action Left-click on the required cell or channel number.

The table below shows the procedure for selecting a group of consecutive channels of a module. Step

Action

1

Select the first channel.

2

Press Shift and click on the last channel.

87

Configuration of the discrete specific application

Selecting a group of non-consecutive channels

Selecting a group of consecutive cells

88

The table below shows the procedure for selecting a group of non-consecutive channels of a module. Step

Action

1

Select the first channel.

2

Press Ctrl and click on each of the channels in turn.

The table below shows the procedure for selecting a group of consecutive cells of a module. Step

Action

1

Select the first cell.

2

Move the mouse up or down whilst holding down the mouse button, then release the button when the last cell has been reached.

TLX DS 57 PL7 40E 09.2000

Configuration of the discrete specific application

6.2

Discrete input channel parameters

Presentation Subject of this section

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

What’s in this Section?

This Section contains the following Maps:

TLX DS 57 PL7 40E 09.2000

Topic

Page

In-rack discrete input parameters

90

Parameters of TBX discrete inputs remoted on the FIPIO bus

91

Parameters of Momentum discrete inputs remoted on the FIPIO bus

92

Parameters of IP67 discrete inputs remoted on the FIPIO bus

93

89

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 Number of inputs

Associated task (8 channel group)

Function (per channel).

Filtering Supply fault monit. (per channel). (16 channel group)

TSX DEY 08D2

8

Mast / Fast

-

-

Active / Inactive

TSX DEY 16A2

16

Mast / Fast / None

-

-

Active / Inactive

TSX DEY 16A3

16

Mast / Fast / None

-

-

Active / Inactive

TSX DEY 16A4

16

Mast / Fast / None

-

-

Active / Inactive

TSX DEY 16A5

16

Mast / Fast / None

-

-

Active / Inactive

TSX DEY 16D2

16

Mast / Fast / None

-

-

Active / Inactive

TSX DEY 16D3

16

Mast / Fast / None

-

-

Active / Inactive

TSX DEY 32D2K

32

Mast / Fast / None

-

-

Active / Inactive

TSX DEY 32D3K

32

Mast / Fast / None

-

-

Active / Inactive

TSX DEY 64D2K

64

Mast / Fast / None

-

-

Active / Inactive

TSX DMY 16FK

16

Mast / Fast / None

Normal or (1)

4 ms or (2)

Active / Inactive

TSX DMY 28FK

16 (input part)

Mast / Fast / None

Normal or (1)

4 ms or (2)

Active / Inactive

TSX PAY 262 TSX PAY 262

8 (input part) 8 (input part)

Mast / Fast / None

-

-

-

TSX DMY 28RFK

16 (input part)

Mast / Fast / None

-

4 ms or (2)

Active / Inactive

Key: (1)

Memorization of status 0 or 1, event processing on rising edge (RE), on falling edge (FE) or both together.

(2)

0.1 to 7.5 ms

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

90

TLX DS 57 PL7 40E 09.2000

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

Number of inputs

Associated task (for the module)

Filtering (per channel)

Latching (per channel)

Wiring Check (per channel)

TBX CEP 1622

16

Mast / Fast

-

-

-

TBX DES 1622

16

Mast / Fast

-

-

-

TBX DES 1633

16

Mast / Fast

-

-

-

TBX EEP 1622

16

Mast / Fast

-

-

-

TBX DMS 1025

8 (input part)

Mast / Fast

-

-

-

TBX DMS 1625

8 (input part)

Mast / Fast

-

-

-

TBX DES 16S04

16

Mast / Fast

-

-

-

TBX DMS 16S44

(1)

Mast / Fast

-

-

Active / Inactive

TBX DMS 16P22

8 (input part)

Mast / Fast

-

-

Active / Inactive

TBX DES 16C22

16

Mast / Fast

-

-

Active / Inactive

TBX EEP 08C22

16

Mast / Fast

-

-

Active / Inactive

TBX DMS 16C22

8

Mast / Fast

-

-

Active / Inactive

TBX DMS 16C222 8

Mast / Fast

-

-

Active / Inactive

TBX DES 16F22

Mast / Fast

Normal / Fast

Active / Inactive -

16

Key: (1)

8 input channels + 8 programmable input or output channels.

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

TLX DS 57 PL7 40E 09.2000

91

Configuration of the discrete specific application

Parameters of Momentum discrete inputs remoted on the FIPIO bus Presentation

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

Parameters

The table below shows the parameters available for each Momentum discrete input module. Module Reference

Number of inputs

Associated task (for the module)

170 ADI 340 00

16

Mast / Fast

170 ADI 350 00

32

Mast / Fast

170 ADM 350 10

16 (input part)

Mast / Fast

170 ADM 390 30

10 (input part)

Mast / Fast

170 ADM 370 10

10 (input part)

Mast / Fast

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

92

TLX DS 57 PL7 40E 09.2000

Configuration of the discrete specific application

Parameters of IP67 discrete inputs remoted on the FIPIO bus Presentation

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

Parameters

The table below shows the parameters available for each IP67 discrete input module. Module Reference

Number of inputs

Associated task (for the module)

TSX EEF 08D2

8

Mast / Fast

TSX EEF 16D2

16

Mast / Fast

TSX EMF 16DT2

8 (input part)

Mast / Fast

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

TLX DS 57 PL7 40E 09.2000

93

Configuration of the discrete specific application

6.3

Discrete output channel parameters

Presentation Subject of this section

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

What’s in this Section?

This Section contains the following Maps:

94

Topic

Page

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

95

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

96

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

98

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

99

Momentum Parameters of Momentum discrete outputs remoted on the FIPIO bus

101

Parameters of IP67 discrete outputs remoted on the FIPIO bus

102

TLX DS 57 PL7 40E 09.2000

Configuration of the discrete specific application

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

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

Parameters

The table below shows the parameters available for each in-rack 8-channel discrete output module. Group of 8 channels

Channel by channel.

Module Reference Associated task

Reactivation

Fallback mode

Supply fault monit.

Fallback value

TSX DSY 08R4D

Mast / Fast

Programmed / Automatic

Fallback / Maintain

0/1

TSX DSY 08R5A

Mast / Fast

Programmed / Automatic

Fallback / Maintain

0/1

TSX DSY 08S5

Mast / Fast

Programmed / Automatic

Fallback / Maintain

0/1

TSX DSY 08T2

Mast / Fast

Programmed / Automatic

Fallback / Active / Inactive Maintain

0/1

TSX DSY 08T22

Mast / Fast

Programmed / Automatic

Fallback / Active / Inactive Maintain

0/1

TSX DSY 08T31

Mast / Fast

Programmed / Automatic

Fallback / Active / Inactive Maintain

0/1

TSX DSY 08R5

Mast / Fast

Programmed / Automatic

Fallback / Maintain

0/1

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

TLX DS 57 PL7 40E 09.2000

95

Configuration of the discrete specific application

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

96

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

TLX DS 57 PL7 40E 09.2000

Configuration of the discrete specific application

Parameters

The table below shows the parameters available for each in-rack discrete output module with more than 8 channels. Group of 8 channels

Channel by channel.

Module Reference

Number of outputs

Associated task

Reactivation

Fallback mode

Supply fault Fallback monit. value

TSX DSY 16S5

16

Mast / Fast / None

Programmed / Automatic

Fallback / Maintain

-

0/1

TSX DSY 16T2

16

Mast / Fast / None

Programmed / Automatic

Fallback / Maintain

TSX DSY 16T3

16

Mast / Fast / None

Programmed / Automatic

Fallback / Maintain

Active / Inactive

0/1

TSX DSY 32T2K

32

Mast / Fast / None

Programmed / Automatic

Fallback / Maintain

Active / Inactive

0/1

TSX DSY 64T2K

64

Mast / Fast / None

Programmed / Automatic

Fallback / Maintain

Active / Inactive

0/1

TSX DSY 16R5

16

Mast / Fast / None

-

Fallback / Maintain

-

0/1

TSX DSY 16S4

16

Mast / Fast / None

-

Fallback / Maintain

-

0/1

TSX DMY 28 FK

12 (output part)

Mast / Fast / None

Programmed / Automatic (1)

Fallback / Maintain

Active / Inactive

0/1

TSX DMY 28RFK

12 (output part)

Mast / Fast / None

Programmed / Automatic (1)

Fallback / Maintain

Active / Inactive

0/1/ Continuous (2)

TSX PAY 262 TSX PAY 262

2 (output part) 4 (output part)

Mast / Fast / None

-

-

-

-

Key: (1)

Reactivation is chosen globally for the 12 output channels.

(2)

Only for TSX DMY 28 RFK.

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

TLX DS 57 PL7 40E 09.2000

97

Configuration of the discrete specific application

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

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

Parameters

The table below shows the parameters available for each 8, 10 or 12 channel TBX discrete output module remoted on the FIPIO bus. Module

Group of 8 channels

Channel by channel

Module Reference

Number of outputs

Associated task

Reactivation

Fallback mode

Fallback value

Wiring Check

TBX ESP 08C22

8

Mast / Fast

Programmed / Automatic

Fallback / Maintain

0/1

Yes / No

TBX DSS 1235

12

Mast / Fast

-

Fallback / Maintain

0/1

-

TBX DMS 1025

2 (output part)

Mast / Fast

Programmed / Automatic

Fallback / Maintain

0/1

-

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

98

TLX DS 57 PL7 40E 09.2000

Configuration of the discrete specific application

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

TLX DS 57 PL7 40E 09.2000

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

99

Configuration of the discrete specific application

Parameters

The table below shows the parameters available for each 16 channel TBX discrete output module remoted on the FIPIO bus. Module

Group of 8 channels

Channel by channel

Module Reference

Number of outputs

Associated task

Reactivation

Fallback mode

Fallback value

Wiring Check

TBX CSP 1625

16

Mast / Fast

-

-

-

-

TBX DSS 1622

16

Mast / Fast

Programmed / Automatic

Fallback / Maintain

0/1

-

TBX ESP 1622

16

Mast / Fast

Programmed / Automatic

Fallback / Maintain

0/1

-

TBX DSS 16C22

16

Mast / Fast

Programmed / Automatic

Fallback / Maintain

0/1

Yes / No

TBX DMS 16C22

16

Mast / Fast

Programmed / Automatic

Fallback / Maintain

0/1

Yes / No

TBX DMS 16C222

16

Mast / Fast

Programmed / Automatic

Fallback / Maintain

0/1

Yes / No

TBX CSP 1622

16

Mast / Fast

Programmed / Automatic

-

-

-

TBX DSS 1625

16

Mast / Fast

-

Fallback / Maintain

0/1

-

TBX DMS 1625

8 (output part)

Mast / Fast

-

Fallback / Maintain

0/1

-

TBX DMS 16S44

8 (output part)

Mast / Fast

-

Fallback / Maintain

0/1

-

TBX DMS 16P22

(1)

Mast / Fast

Programmed / Automatic

Fallback / Maintain

0/1

-

Key: (1)

8 programmable output channels.

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

100

TLX DS 57 PL7 40E 09.2000

Configuration of the discrete specific application

Momentum Parameters of Momentum discrete outputs remoted on the FIPIO bus Presentation

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

Parameters

The table below shows the parameters available for each Momentum discrete output module. Module Reference

Number of inputs

Associated task (for the module)

170 ADO 340 00

16

Mast / Fast

170 ADO 350 00

32

Mast / Fast

170 ADO 530 50

8

Mast / Fast

170 ADM 350 10

16 (output part)

Mast / Fast

170 ADM 390 30

8 (output part)

Mast / Fast

170 ADM 370 10

8 (output part)

Mast / Fast

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

TLX DS 57 PL7 40E 09.2000

101

Configuration of the discrete specific application

Parameters of IP67 discrete outputs remoted on the FIPIO bus Presentation

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

Parameters

The table below shows the parameters available for each Momentum discrete output module. Module Reference

Number of inputs

Associated task (for the module)

TSX EMF 16DT2

8 (output part)

Mast / Fast

TSX ESF 08T22

8

Mast / Fast

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

102

TLX DS 57 PL7 40E 09.2000

Configuration of the discrete specific application

6.4

Configuration of discrete parameters

Presentation Subject of this section

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

What’s in this Section?

This Section contains the following Maps:

TLX DS 57 PL7 40E 09.2000

Topic

Page

Configuring the programmable channels of the TBX DMS 16P22 module

104

Modifying the Task parameter of a discrete module

105

Modifying the Wiring check parameter of a TBX discrete module

106

Modifying the Monitoring of external supply fault parameter for a discrete module.

107

Modifying the Functions parameter of a discrete input module

108

Modifying the Filtering parameter of a discrete input module.

110

How to modify the Latching parameter of a discrete input module

111

Parametering the Run/Stop input of a discrete module

112

Modifying the Fallback mode parameter of a discrete output module

113

Modifying the Reactivation of outputs parameter of a discrete module.

114

103

Configuration of the discrete specific application

Configuring the programmable channels of the TBX DMS 16P22 module Presentation

In addition to its 8 input channels, this module possesses 8 channels which can be individually configured as input or output channels. Note: the channel type cannot be reconfigured in online mode.

Illustration

The illustration below shows the configuration screen for the TBX DMS 16P22 module. TBX DMS 16P22 [FIPIO1 MODULE 0] Configuration

Program

Designation : TBX7 SOCK 8E+8I/O 0,5 A

Chan. 8 9 10 11 12 13 14 15

Procedure

Task MAST

Type Input Input Input Output Output Input Input Output

Reactivate Automatic Automatic Automatic Automatic Automatic Automatic Automatic Automatic

Fall. Mode Fall. Value Fallback Fallback Fallback Fallback 0 Fallback 0 Fallback Fallback Fallback 0

The table below gives the procedure for configuring the programmable channels of the TBX DMS 16P22 module. Step

104

Symbol

Version : 1.0

Action

1

Access the module’s hardware configuration screen.

2

Select Program part from the pull-down menu in the module zone.

3

Parameter the channels one by one as inputs or outputs using the pull-down list in the Type column.

TLX DS 57 PL7 40E 09.2000

Configuration of the discrete specific application

Modifying the Task parameter of a discrete module Presentation

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

Procedure

The table below shows the procedure for defining the type of task assigned to the channels of a module. Step

Action

1

Access the hardware configuration screen of the required module.

2

In the pull-down menu located in the Task column, click on the button for the required group of channels. Result: a pull-down list appears. MAST MAST FAST NONE

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

TLX DS 57 PL7 40E 09.2000

3

Select the required task. Note: Selecting None causes the group of channels in question and the following groups to be deconfigured, after the modification is confirmed. reconfiguration (MAST or FAST) of a group of deconfigured channels will, after the modification is confirmed, cause the preceding non-configured groups to be reconfigured.

4

Confirm the deconfiguration or reconfiguration if necessary.

105

Configuration of the discrete specific application

Modifying the Wiring check parameter of a TBX discrete module Presentation

This function is used to permanently check the quality of links between:

l sensors and inputs, l actuators and outputs.

Note: This parameter can be modified in online mode.

Procedure

106

The table below shows the procedure for activating or deactivating the Wiring Check parameter. Step

Action

1

Access the hardware configuration screen of the required module.

2

Click on the checkbox in the Wiring Check column of the channel to be parametered.

3

Repeat the operation for every channel to be configured (from step 2).

TLX DS 57 PL7 40E 09.2000

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

TLX DS 57 PL7 40E 09.2000

Action

1

Access the hardware configuration screen of the required module.

2

Click on the checkbox in the Supply fault monitoring column. Note: For discrete modules with more than 16 channels, use the scrollbar to access the different groups of channels.

107

Configuration of the discrete specific application

Modifying the Functions parameter of a discrete input module Presentation

This parameter defines the properties of event inputs for TSX DEY 16 FK and TSX DMY 28 FK modules. The parameter may have the following values: l normal (no event associated with the channel), l channel by channel memorization of status (status at 0 or status at 1), l channel by channel event processing, l event triggered on a rising edge (RE), l event triggered on a falling edge (FE), l event triggered on a rising edge and falling edge, Event inputs have an associated processing number (Evti). These numbers range from: l 0 to 31 for TSX5710/102/103/153, PMX 57 102, PCX 571012 processors, l 0 to 63 for other processors. If two edge types are selected on one channel, only one event number is associated with the channel. The highest priority event processing (Evti) number is 0, which can only be attributed to channel 0. Note: l The event number proposed is the first available number in the list. l A manually input number outside the tolerance range will not be accepted on confirmation. l Event numbers cannot be added, deleted or changed when in online mode.

108

TLX DS 57 PL7 40E 09.2000

Configuration of the discrete specific application

Procedure

The table below shows the procedure for defining the parameters associated with event inputs. Step

Action

1

Access the hardware configuration screen of the required module.

2

Select the required channel.

3

In the Function column, double-click on the cell of the channel to be parametered. Result: The properties dialogue box appears. Properties of channel 6

x

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

4

TLX DS 57 PL7 40E 09.2000

Select the required function.

5

Enter the Evt event number.

6

Repeat the operation for every channel to be configured (from step 2).

109

Configuration of the discrete specific application

Modifying the Filtering parameter of a discrete input module. Presentation

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

Procedure

The table below shows the procedure for defining the Filtering parameter. Step

Action

1

Access the hardware configuration screen of the required module.

2

In the pull-down menu located in the Filtering column, click on the button for the required channel. Result: one of the following pull-down lists appears: In-rack module Filter 4 ms 0.1 ms 0.5 ms 1 ms 1.5 ms 2 ms 2.5 ms

3

110

Module on FIPIO bus Filter Fast Normal Fast

Select the required filtering time.

TLX DS 57 PL7 40E 09.2000

Configuration of the discrete specific application

How to modify the Latching parameter of a discrete input module Presentation

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

Procedure

The table below shows the procedure for activating or deactivating the Latching function. Step

Action

1

Access the hardware configuration screen of the required module.

2

Click on the checkbox in the Latching column of the channel to be parametered.

3

Repeat the operation for every channel to be configured (from step 2).

Note: This parameter can be modified in online mode.

TLX DS 57 PL7 40E 09.2000

111

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

112

Action

1

Access the CPU configuration screen.

2

Check the Run/Stop Input box.

3

Enter the input to be assigned in the data entry window.

TLX DS 57 PL7 40E 09.2000

Configuration of the discrete specific application

Modifying the Fallback mode parameter of a discrete output module Presentation

This parameter defines the fallback mode adopted by outputs when the PLC changes to Stop, in the event of a processor, rack or inter-rack cable fault. The possible modes are as follows: Mode

Meaning

Fallback

Channels are set to 0 or 1 depending on the parametered fallback value, for the group of 8 corresponding channels.

Maintain

Outputs retain the status occupied before the change to Stop.

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.

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

Procedure

The table below shows the procedure for defining the fallback mode assigned to a group of channels. Step

Action

1

Access the hardware configuration screen of the required module.

2

In the pull-down menu located in the Fallback mode column, click on the button for the required group of channels. Result: a pull-down list appears. Fall. mode Fallback Maintain Fallback

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

TLX DS 57 PL7 40E 09.2000

3

Select the required fallback mode.

4

For Fallback mode, parameter each of the channels in the selected group. To do this, click on the button in the pull-down menu in the Fallback val. column.

5

Click on the required value (0 or 1).

113

Configuration of the discrete specific application

Modifying the Reactivation of outputs parameter of a discrete module. Presentation

This parameter defines the tripped output reactivation mode The possible modes are as follows: Mode

Meaning

Programmed Reactivation is performed by a command from the PLC application or via the debug screen (1). Note: In order to avoid closely spaced, repetitive reactivation, the module allows a period of 10 seconds between two reactivations. Automatic

Reactivation is carried out automatically every 10 seconds until the fault disappears.

Key: (1)

Faulty outputs can only be reactivated from the debug screen for in-rack modules.

The reactivation mode is defined per group of 8 channels. Note: This parameter may be modified in online mode for discrete in-rack modules.

Procedure

The table below shows the procedure for defining the reactivation mode for a module’s output channels. Step

Action

1

Access the hardware configuration screen of the required module.

2

In the pull-down menu located in the Reactivation column, click on the button for the required group of channels. Result: a pull-down list appears. Reactivate Programmedd

Programmed Automatic

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

114

Select the required task.

TLX DS 57 PL7 40E 09.2000

Debugging discrete modules

7

At a Glance Subject of this chapter

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

What’s in this Chapter?

This Chapter contains the following Maps:

TLX DS 57 PL7 40E 09.2000

Topic

Page

Presentation of the debug function of a discrete module.

116

Description of the debug screen of a discrete module

117

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

119

Accessing the diagnostics function of a discrete module

120

Accessing the channel diagnostics function of a discrete module

121

Accessing the forcing/unforcing function

122

How to access the SET and RESET commands

123

Accessing the masking/unmasking function for an event

124

Accessing the reactivation of outputs command

125

Maintain outputs of a discrete module

126

115

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

116

Access to the debug function...

PL7 of version prior to V3.3

not available.

(PL7 + CPU + Application PL7) of version V3.3 or higher

limited to four screens open simultaneously.

TLX DS 57 PL7 40E 09.2000

Debugging discrete modules

Description of the debug screen of a discrete module Presentation

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

Illustration

The debug screen is displayed as follows: 1

TSX DSY 08R5 [RACK 0 POSITION 3] Debug

2

Designation : 8O RELAY 50VA, BORN Version : 1.0 Global unforcing

3

4

TLX DS 57 PL7 40E 09.2000

Chan. 0 1 2 3 4 5 6 7

Symbol

State 0 0 0 0 0 0 0 0

Fault DIAG... DIAG... DIAG... DIAG... DIAG... DIAG... DIAG... DIAG...

RUN

Reactivate Reactivate

ERR

Applied Q STOP

IO

DIAG...

Channel control

x

Forcing F4

Force to 0

F5

Force to 1

F6

Unforce

Write F7

Set

F8

Reset

117

Debugging discrete modules

Description

The table below shows the different elements in the debug screen, along with their functions.

Number

Element

Function

1

Title bar

Indicates the reference and physical position of the selected module along with the rack number for in-rack modules or the FIPIO connection point for remote I/Os.

2

Module zone

3

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

4

Command zone

118

Enables the user to select: the debug phase: l Configuration, l Installation (diagnostics), only accessible in online mode. l the type of channels (inputs or outputs), if the module in question has both inputs and outputs. Displays the designation of the selected module and shows the module’s status indicator lights (Run, Err, I/O). Provides direct access to: l the module diagnostics when the module is faulty (shown by the indicator in the diagnostics access button, which turns red) l the channel Global unforcing function. Note: Display of this zone is optional. The choice is made using the command View → Module zone.

l

Provides access to the commands for a channel

TLX DS 57 PL7 40E 09.2000

Debugging discrete modules

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

This operation enables the user to access the debug screen for the channels of a discrete module. The debug screen is only accessible in online mode. Step

Action

1

Access the hardware configuration screen.

2

Double-click on the module to be configured or select the module and execute the command Service → Open the module. Result: The configuration screen for the selected module appears. TSX DSY 08R5 [RACK 0 POSITION 3] Debug Designation : 8O RELAY 50VA, BORN Version : 1.0 Global unforcing

Chan. 0 1 2 3 4 5 6 7

Symbol

State 0 0 0 0 0 0 0 0

Fault DIAG... DIAG... DIAG... DIAG... DIAG... DIAG... DIAG... DIAG...

RUN

Reactivate Reactivate

ERR

Applied Q STOP

IO

DIAG...

x

Channel control Forcing F4

Force to 0

F5

Force to 1

F6

Unforce

Write

TLX DS 57 PL7 40E 09.2000

F7

Set

F8

Reset

119

Debugging discrete modules

Accessing the diagnostics function of a discrete module Presentation

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

Procedure

The table below shows the procedure for accessing the module diagnostics screen. Step

Action

1

Access the module’s debug screen.

2

Click on the Diag button in the module zone. Result: The list of module faults appears: Module diagnostics Internal faults

External faults

Other fault Faulty channel(s)

OK

Note: If a configuration fault occurs, in the event of a major failure or missing module, the module diagnostics screen cannot be accessed. The following message then appears on the screen: Module is missing or different from that configured in this position .

120

TLX DS 57 PL7 40E 09.2000

Debugging discrete modules

Accessing the channel diagnostics function of a discrete module Presentation

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

Procedure

The table below shows the procedure for accessing the channel diagnostics screen. Step

Action

1

Access the module’s debug screen.

2

Click on the Diag button in the Err column. Result: The list of channel faults appears. Channel diagnostics Internal faults

External faults

Other faults

External supply

OK

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

TLX DS 57 PL7 40E 09.2000

121

Debugging discrete modules

Accessing the forcing/unforcing function Presentation

This function is used to modify the status of all or part of a module’s channels. The status of a forced output is fixed and can only be modified by the application after unforcing. Note: However, when a fault causes the outputs to fall back, the status of these channels takes the value set when the fallback mode parameter was configured. The available commands are as follows:

l for one or more channels:

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

The table below shows the procedure for forcing or unforcing all or part of the channels of a module. See Modifying the configuration parameters of a discrete module’s: General, p. 87 for multiple selection. Step

Action for one channel

1

Access the module’s debug screen.

Action for all channels

2

In the Status column, double-click on the Click on the Global unforcing button cell of the required channel (1). in the module zone.

3

Select the required function.

-

Key: (1)

122

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

TLX DS 57 PL7 40E 09.2000

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. 87 ) for multiple selection. Step

Action for one channel

1

Access the module’s debug screen.

2

In the Status column, double click on the cell of the required channel (1).

3

Select the required function.

Key: (1)

TLX DS 57 PL7 40E 09.2000

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

123

Debugging discrete modules

Accessing the masking/unmasking function for an event Presentation

This function enables the user to inhibit or restore the processing associated with the input or output channel which caused the event. The available commands are as follows: l Mask (masks the events), l Unmask (deactivates masking of events). Note: If one or more events occur while they are inhibited, the associated processing is lost.

Procedure

The table below shows the procedure for masking or unmasking all or part of the channels configured in event processing. Step

Action for one or more channels (1)

Action for all of the configured channels of the application modules (2)

1

Access the module’s debug screen.

Access the CPU debug screen.

2

In the Status column, double-click on the Click on the Activation/Deactivation cell of the required channel (3). button located in the Events field.

3

Select the required function.

-

Key:

124

(1)

For multiple selection, see Modifying the configuration parameters of a discrete module’s: General, p. 87.

(2)

Global masking/unmasking can also be carried out using: l the instruction PL7 MASKEVT(), l the instruction PL7 UNMASKEVT(), l the %S38 system bit.

(3)

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

TLX DS 57 PL7 40E 09.2000

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

TLX DS 57 PL7 40E 09.2000

Action

1

Access the module’s debug screen.

2

Click on the Reactivate button in the Reactivation column for the required group of channels.

125

Debugging discrete modules

Maintain outputs of a discrete module Presentation

126

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

TLX DS 57 PL7 40E 09.2000

Bits and words associated with discrete specific applications

8

Presentation Subject of this chapter

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

What’s in this Chapter?

This Chapter contains the following Sections:

TLX DS 57 PL7 40E 09.2000

Section

Topic

Page

8.1

Addressing of discrete I/O module objects

129

8.2

Language objects associated with the discrete specific application

133

127

Language words and bits

128

TLX DS 57 PL7 40E 09.2000

Language words and bits

8.1

Addressing of discrete I/O module objects

Presentation Subject of this section

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

What’s in this Section?

This Section contains the following Maps:

TLX DS 57 PL7 40E 09.2000

Topic

Page

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

130

Addressing of language objects associated with discrete I/O modules remoted on the FIPIO bus

131

Indexable discrete I/O objects.

132

129

Language words and bits

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

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

Illustration

Addressing principle:

Specific values

%

I, Q, M, K

X, W, D, F

Symbol

Object type

Format

X Rack

Y

.

Position

i

.

r

Channel no. Rank

The table below shows the values specific to the discrete in-rack I/O module objects. Element

Values

Comment

x

0 to 1 0 to 7

TSX 5710/102/103/153, PMX 57102, PCX 571012. Other processors

y

00 to 14 (1)

When the rack number (x) is other than 0, the position (y) has a 2 digit code: 00 to 14; however, if the rack number (x) = 0, the non-meaningful zeros are deleted (from the left) from "y" ("x" does not appear and "y" takes 1 digit for values of less than 9).

i

0 to 63 or MOD: channel reserved for management of the module and the MOD parameters shared by all channels.

r

0 to 3 or ERR

ERR: indicates a module or channel fault.

(1) : The number of slots requires the use of 2 racks at the same address.

130

TLX DS 57 PL7 40E 09.2000

Language words and bits

Addressing of language objects associated with discrete I/O modules remoted on the FIPIO bus Presentation

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

Illustration

Addressing principle: % Symbol

Specific values

TLX DS 57 PL7 40E 09.2000

I, Q, M, K

X, W, D, F \

Object type

Format

p.2.c

\

Module/channel address and connection point

m Module number

.

i

r

.

Channel number

Rank

The table below shows the values specific to remote discrete I/O module objects. Element

Values

Comment

i

0 to 31 or 0 to 15 for TBX modules. MOD 0 to 31 for Momentum modules. MOD: channel reserved for management of the module and the parameters shared by all channels.

r

0 to 255 or ERR

ERR: indicates a module or channel fault.

131

Language words and bits

Indexable discrete I/O objects. Presentation

132

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

TLX DS 57 PL7 40E 09.2000

Language words and bits

8.2

Language objects associated with the discrete specific application

Presentation Subject of this section

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

What’s in this Section?

This Section contains the following Maps:

TLX DS 57 PL7 40E 09.2000

Topic

Page

Implicit exchange language objects associated with the discrete specific application

134

Exchange management: Exchanges in progress module %[email protected]:Xj or channel %[email protected]:Xj

135

Exchange management: Module %[email protected]:Xj or channel %[email protected]:Xj report

137

Explicit exchange objects: General

138

Explicit exchange object: %[email protected]:Xj channel status

139

Explicit exchange object: Status Module %[email protected]:Xj

140

Explicit exchange object: %[email protected]:Xj channel command

142

133

Language words and bits

Implicit exchange language objects associated with the discrete specific application Presentation

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

Bit objects

The table below shows the different implicit exchange bit objects.

Address (1)

Function

Meaning when the bit is at status 1

%[email protected]

Input channel bit

Indicates, for input channel i, that the sensor output controlling the input is activated.

%[email protected]

Output channel bit

Indicates that output channel i is activated.

%[email protected]

Channel error bit

Indicates that input channel i is faulty.

%[email protected]

Module error bit

Indicates that the module is faulty.

Key: (1)

Word objects

@module = module address. l xy for in-rack modules, l \p2c\m for remote modules.

The table below shows the different implicit exchange word objects.

Address (1)

Function

Meaning for Xj = 1

%[email protected]:X0

Event status associated with channel i

Indicates that event processing is configured on a rising edge.

Command word associated with channel i

Masks/unmasks the event associated with the channel.

%[email protected]:X1 %[email protected]:X0

Indicates that event processing is configured on a falling edge.

Key: (1)

134

@module = module address. l xy for in-rack modules, l \p2c\m for remote modules.

TLX DS 57 PL7 40E 09.2000

Language words and bits

Exchange management: Exchanges in progress module %[email protected]:Xj or channel %[email protected]:Xj Presentation

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

Description

The table below explains the meanings of the different bits in the word %[email protected]. 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)

Description

@module = module address. l xy for in-rack modules, l \p2c\m for remote modules.

The table below explains the meanings of the different bits in the word %[email protected]. Address (1)

Meaning for Xj = 1

%[email protected]:X0

Exchange of status words in progress on channel i.

%[email protected]:X1

Exchange of command words in progress on channel i.

Key: (1)

TLX DS 57 PL7 40E 09.2000

@module = module address. l xy for in-rack modules, l \p2c\m for remote modules.

135

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.

136

TLX DS 57 PL7 40E 09.2000

Language words and bits

Exchange management: Module %[email protected]:Xj or channel %[email protected]:Xj report Presentation

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

Description

The table explains the meanings of the bits in the word %[email protected]. Address (1)

Meaning for Xj = 1

%[email protected]:X0

Status parameter exchange error on at least one channel of the module.

%[email protected]:X1

Command parameter exchange error on at least one channel of the module.

Key: (1)

Description

@module = module address. l xy for in-rack modules, l \p2c\m for remote modules.

The table explains the meanings of the bits in the word %[email protected]. Address (1)

Meaning for Xj = 1

%[email protected]:X0

Status parameter exchange error on channel i.

%[email protected]:X1

Command parameter exchange error on channel i.

Key: (1)

Example

TLX DS 57 PL7 40E 09.2000

@module = module address. l xy for in-rack modules, l \p2c\m for remote modules.

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;

137

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 %[email protected] (@module = module address), which are not documented in this manual, are accessible in read only mode and correspond to the configuration parameters entered using the Configuration editor. Explicit exchanges objects are exchanged at the request of the user program using the following instructions: l READ_STS (read status words), l WRITE_CMD (write command words), l WRITE_PARAM (write adjustment parameters), l READ_PARAM (read adjustment parameters), l SAVE_PARAM (save adjustment parameters), l RESTORE_PARAM (restore adjustment parameters).

138

TLX DS 57 PL7 40E 09.2000

Language words and bits

Explicit exchange object: %[email protected]:Xj channel status Presentation

This word-type object provides information on the status of channel i. It is updated on execution of the instruction READ_STS%[email protected].

Description

The table below explains the meanings of the different bits in the word %[email protected]. Address (1)

Meaning for Xj = 1

%[email protected]:X0

External fault: Tripped.

%[email protected]:X1 (2)

External fault: Fuse.

%[email protected]:X2

Terminal block fault.

%[email protected]:X3

External supplyfault.

%[email protected]:X4

Internal fault: Module Out of Order

%[email protected]:X5

Software or hardware configuration fault.

%[email protected]:X6

Communication fault.

%[email protected]:X7

Reserved.

%[email protected]:X8

External fault: Short-circuit.

%[email protected]:X9

External fault: Line fault.

%[email protected]:X10 à X15

Reserved.

Key:

TLX DS 57 PL7 40E 09.2000

(1)

@module = module address. l xy for in-rack modules, l \p2c\m for remote modules.

(2)

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

139

Language words and bits

Explicit exchange object: Status Module %[email protected]:Xj Presentation

140

This word-type object provides information on the status of the module. It is updated on execution of command READ_STS%[email protected].

TLX DS 57 PL7 40E 09.2000

Language words and bits

Description

The table below explains the meanings of the different bits in the word %[email protected]. Address (1)

Meaning for Xj = 1

Module type

%[email protected]:X0

Internal fault: Module Out of Order.

Base

%[email protected]:X1

Functional Fault (2).

Base

%[email protected]:X2

Terminal block fault.

Base

%[email protected]:X3

Functional Fault (2).

Base

%[email protected]:X4

Self-testing

Base

%[email protected]:X4

Reserved.

Base

%[email protected]:X5

Software or hardware configuration fault.

Base

%[email protected]:X6

Module missing

Base

%[email protected]:X7

Fault on FIPIO extension module.

Base

%[email protected]:X8

Internal fault: Module Out of Order.

FIPIO extension

%[email protected]:X9

Functional Fault (2).

FIPIO extension

%[email protected]:X10

FIPIO Extension Terminal Block Fault.

FIPIO extension

%[email protected]:X11

Self-testing

FIPIO extension

%[email protected]:X12

Reserved.

FIPIO extension

%[email protected]:X13

Software or hardware configuration fault.

FIPIO extension

%[email protected]:X14

Module missing

FIPIO extension

%[email protected]:X15

Reserved.

FIPIO extension

Key: (1)

@module = module address. l xy for in-rack modules, l \p2c\m for remote modules.

(2)

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

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

TLX DS 57 PL7 40E 09.2000

141

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 %[email protected]. Address (1)

Meaning for Xj = 1

%[email protected]:X0

Reactivation of tripped outputs (protected outputs).

%[email protected]:X1

Inhibition of external supply control.

%[email protected]:X2

Confirmation of external supply control.

%[email protected]:X3 to X15

Reserved.

Key: (1)

142

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

TLX DS 57 PL7 40E 09.2000

Installation of the discrete reflex module

9

Presentation Subject of this chapter

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

What’s in this Chapter?

This Chapter contains the following Sections:

TLX DS 57 PL7 40E 09.2000

Section

Topic

Page

9.1

General presentation of discrete reflex module

145

9.2

Reflex function blocks

147

9.3

Configuration of discrete reflex module

190

9.4

Bits and words associated with discrete reflex module

198

143

Installation of the discrete reflex module

144

TLX DS 57 PL7 40E 09.2000

Installation of the discrete reflex module

9.1

General presentation of discrete reflex module

Presentation of discrete reflex module General

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

Operating principle

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: l the image bits of the module’s physical input status (%I), l the image bits of the module’s physical and auxiliary output statuses (%I), l the command bits of the module outputs (%Q).

TLX DS 57 PL7 40E 09.2000

145

Installation of the discrete reflex module

Illustration

The diagram below shows the operating principle of the discrete reflex module. Response time < 1 ms TSX DM 28 RFK Module Inputs

Outputs

Reflex function

%Ixy.i (0 à 15) PLC task

%Ixy.i (16 à 31) %Ixy.i.1 (16 à 31)

Acquisition Processing Update %Qxy.i

146

TLX DS 57 PL7 40E 09.2000

Installation of the discrete reflex module

9.2

Reflex function blocks

Presentation Subject of this section

This section presents the different reflex functions available.

What’s in this Section?

This Section contains the following Maps:

TLX DS 57 PL7 40E 09.2000

Topic

Page

Function block: Direct

148

Reflex function block: Combinational

149

Reflex function block: Operation timer

150

Reflex function block: Idle timer

151

Reflex function block: Operation-idle timer

152

Reflex function block: 2 value operation timer

153

Reflex function block: Operation-idle time with value selection

155

Reflex function block: Retriggerable monostable

158

Reflex function block: Monostable with time delay

159

Reflex function block: 2 value monostable

161

Reflex function block: Oscillator

163

Reflex function block: D flip-flop

164

Reflex function block: T flip-flop

166

Reflex function block: 2 threshold counter

168

Reflex function block: Came électronique simple

170

Reflex function block: 1 threshold intervalometer

172

Reflex function block: Burst

174

Reflex function block: PWM (Pulse Width Modulation)

175

Reflex function block: Detection of underspeed

176

Reflex function block: Speed monitoring

178

Reflex function block: Type 1 command-check

181

Reflex function block: Type 2 command-check

183

Reflex function block: Command-counting

186

Reflex function block: Fault Signaling

188

147

Installation of the discrete reflex module

Function block: Direct Role

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

Structure

The table below shows the block’s different interfaces. Name

Meaning

x

Block’s physical output.

x Aux

Block’s internal auxiliary output.

Operation

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

Illustration

The diagram below illustrates the Direct. TSX DM 28 RFK Module Inputs

Outputs

PLC task Acquisition of the inputs Application processing Update of the outputs

148

TLX DS 57 PL7 40E 09.2000

Installation of the discrete reflex module

Reflex function block: Combinational Role

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

Structure

The table below shows the block’s different interfaces.

Operation

Name

Meaning

x

Block’s physical output.

x Aux

Block’s internal auxiliary output.

The logic function entered is directly applied to the x output. Outputs x and x Aux have identical values. Note: A logic function can be made up of several combinational functions by using the %Ixy.i bits associated with the output channels as intermediate variables.

Illustration 1

The illustration below shows an example of a simple combinational function %I2.1.0

%I2.0.0

%I2.4.0

Combinational

Output 16

I %I2.16.0 I Output 16 Aux

Illustration 2

The illustration below shows an example of a combinational function using the auxiliary output of the first combinational as an intermediate variable. %I2.1.0

%I2.0.0

%I2.4.0

Combinational

Output 16

I %I2.16.0 I

Output 16 Aux

%I2.16.1

%I2.10.0 I %I2.8.0

Combinational

Output 17

I

Output 17 Aux

TLX DS 57 PL7 40E 09.2000

149

Installation of the discrete reflex module

Reflex function block: Operation timer Role

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

Structure

The table below shows the block’s different interfaces.

Operation

Name

Meaning

E

Timer input.

x

Timer’s physical output.

x Aux

Block’s internal auxiliary output.

Illustration E

TIMER in operation

Output x

ti Output x Aux

This table describes the different operating phases of the operation timer. Phase

Description

1

On the rising edge of the E input, time-out ti is launched (time base of 0.1ms).

2

When the time-out is over, the x output changes to 1. If the high status of input E lasts less time than ti, output x stays at 0.

Note: The values of outputs x and x Aux are identical.

Illustration

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

x

x Aux

150

TLX DS 57 PL7 40E 09.2000

Installation of the discrete reflex module

Reflex function block: Idle timer Role

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

Structure

The table below shows the block’s different interfaces. Name

Meaning

E

Timer input.

x

Timer’s physical output.

x Aux

Block’s internal auxiliary output.

Illustration E

Output x

TIMER idle

ti Output x Aux

Operation

This table describes the different operating phases of the idle timer. Phase

Description

1

The x output changes to 1 when the E input changes to 1.

2

On the falling edge of the E input, time-out ti is launched (time base of 0.1ms).

3

When the time-out is over, the x output changes to 0. If the low status of input E lasts less time than ti, output x stays at 1.

Note: The values of outputs x and x Aux are identical.

Illustration

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

x

x Aux

TLX DS 57 PL7 40E 09.2000

151

Installation of the discrete reflex module

Reflex function block: Operation-idle timer Role

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

Structure

The table below shows the block’s different interfaces. Name

Meaning

E

Timer input.

x

Timer’s physical output.

x Aux

Block’s internal auxiliary output.

Illustration E

TIMER in operation/idle

tri Output x Aux

tfi

Operation

Output x

This table describes the different operating phases of the operation-idle timer. Phase

Description

1

On the rising edge of the E input (on-delay) , time-out tri is launched (time base of 0.1ms).

2

When time-out tri is over, the x output changes to 1. If the high status of input E lasts less time than tri, output x stays at 0.

3

On the falling edge of the E input (off-delay) , time-out tfi is launched (time base of 0.1ms).

4

When time-out tfi is over, the x output changes to 0. During time-out tfi, if the low status of input E lasts less time than tfi, output x stays at 1.

Note: The x Aux output is at 1 as long as input E or output x is at 1.

Illustration

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

tfi

x

x Aux

152

TLX DS 57 PL7 40E 09.2000

Installation of the discrete reflex module

Reflex function block: 2 value operation timer Role

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

Structure

The table below shows the block’s different interfaces. Name

Meaning

E

Timer input.

Sel

Selection of time-out t1i or t2i. Sel = 0 : time-out t1i, Sel = 1 : time-out t2i,

l l

Direct

Selection of block (for string operation). Direct = 0: block selected Direct = 1: block not selected (output x takes the value of E).

l l

x

Timer’s physical output.

x Aux

Block’s internal auxiliary output.

Illustration E

Operation

Sel

t1i

Direct

t2i

Output x

Output x Aux

This table describes the different operating phases of the 2 value operation timer. Phase

TLX DS 57 PL7 40E 09.2000

2-valuesTIMER

Description

1

On the rising edge of the E input, a time-out corresponding to the status of input Sel is launched.

2

When the time-out is over, the x and x Aux outputs change to 1. If the high status of input E lasts less time than the selected time-out, output x stays at 0.

153

Installation of the discrete reflex module

Illustration

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

x t1i

t2i

x Aux

String operation

It is possible to increase the number of time-outs which can be selected by stringing together several blocks, with the x output of one forming the E input of the next. Phase

Description

1

On the rising edge of the E input of the first block a time-out is launched, corresponding to: l the block whose Direct input is at 0, l the status of the Sel input. Note: Two blocks must not simultaneously have their Direct inputs set to 0.

2

When the time-out is over, the x and x Aux outputs change to 1. If the high status of the E input of the first block lasts less time than the selected time-out, output x stays at 0.

3

The x output changes to 0 on the falling edge of the E input .

Note: l x and x Aux have identical values. l the x Aux outputs can be used for tracking, l when stringing together several blocks, it is essential to change the statuses of Sel and Direct only when the 0 status of input E is at 0.

Illustration

The table below shows the tracking of two timers. E

154

2-values TIMER

Sel

t1i

Direct

t2i

Output x

E

Sel

t1i

Output x Aux

Direct

t2i

2-values TIMER

Output x1

Output x Aux1

TLX DS 57 PL7 40E 09.2000

Installation of the discrete reflex module

Reflex function block: Operation-idle time with value selection Role

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

Structure

The table below shows the block’s different interfaces. Name

Meaning

E

Timer input.

Sel

Selection of time-out t1i or t2i. Sel = 0 : t1i on-delay, t2i off-delay. Sel = 1 : t2i on-delay, t1i off-delay.

l l

Direct

Selection of block (for string operation). Direct = 0: block selected Direct = 1: block not selected (output x takes the value of E).

l l

x

Timer’s physical output.

x Aux

Block’s internal auxiliary output.

Illustration E

TLX DS 57 PL7 40E 09.2000

TIMER in operation/idle

Sel

ti1

Direct

t2i

Output x

Output x Aux

155

Installation of the discrete reflex module

Operation

This table describes the different operating phases of the operation-idle timer with value selection. Phase

Illustration

Description

1

On the rising edge of input E : l the time-out corresponding to the status of input Sel is launched, l output x Aux changes to 1.

2

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

3

On the falling edge of input E: l the time-out corresponding to the status of input Sel is launched, l output x Aux changes to 1.

4

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

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

x

x Aux t1i

156

t2i

t2i

t1i

TLX DS 57 PL7 40E 09.2000

Installation of the discrete reflex module

String operation

It is possible to increase the number of time-outs which can be selected by stringing together several blocks, with the x output of one forming the E input of the next. Phase

Description

1

On the rising edge of input E of the first block: l the time-out is launched, corresponding to: l the block whose Direct input is at 0, l the status of the Sel input. l output x Aux changes to 1. Note: Two blocks must not simultaneously have their Direct inputs set to 0.

2

When the selected time-out is over l output x of the relevant block changes to 1. l output x Aux of the relevant block changes to 0. If the high status of the E input of the first block lasts less time than the selected time-out, output x stays at 0.

3

On the falling edge of input E of the first block: l the time-out is launched, corresponding to: l the block whose Direct input is at 0, l the status of the Sel input. l output x Aux changes to 1. Note: Two blocks must not simultaneously have their Direct inputs set to 0.

4

When the selected time-out is over: l output x of the relevant block changes to 1. l output x Aux of the relevant block changes to 0. If the low status of the E input of the first block lasts less time than the selected time-out, output x stays at 0.

5

The x output changes to 0 on the falling edge of the E input.

Note:When stringing together several blocks It is essential to change the statuses of the Sel and Direct inputs only when the status of input E of the first block is set to 0..

Illustration

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

Sel Direct

TLX DS 57 PL7 40E 09.2000

TIMER in operation/idle

Output x

E

Sel

ti1

Output x Aux

Direct

t2i

ti1 t2i

TIMER in operation/idle

Output x1

Output x Aux1

157

Installation of the discrete reflex module

Reflex function block: Retriggerable monostable Role

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

Structure

The table below shows the block’s different interfaces. Name

Meaning

Illustration

E

Monostable input.

x

Monostable’s physical output.

x Aux

Block’s internal auxiliary output.

E

Retriggerable MONO

Output x

ti Output x Aux

Operation

This table describes the different operating phases of the retriggerable monostable. Phase

Illustration

Description

1

On the rising edge of input E (on-delay): l time-out ti is launched (time-base of 0.1ms), l outputs x and x Aux change to 1.

2

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

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

E

x ti

ti ti

x Aux

158

TLX DS 57 PL7 40E 09.2000

Installation of the discrete reflex module

Reflex function block: Monostable with time delay Role

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

Structure

The table below shows the block’s different interfaces. Name

Meaning

E

Monostable input.

x

Monostable’s physical output.

x Aux

Block’s internal auxiliary output.

Illustration E

Time-delayed MONO

Output x

t1i t2i

Operation

This table describes the different operating phases of the monostable with time delay. Phase

TLX DS 57 PL7 40E 09.2000

Output x Aux

Description

1

On the rising edge of input E : l time-out t1i is launched (time-base of 0.1ms), l output x Aux changes to 1.

2

When time out t1i is over: l time-out t2i is launched (time base of 0.1ms), l output x changes to 1 for duration t2i. If the high status of input E lasts less time than time-out t1i, output x stays at 0.

3

When time-out t2i is over, outputs x and x Aux change to 0. If a new rising edge for input E occurs before time-out t2i has elapsed: l output x remains at 1 for duration t2i of the cycle in progress. l a new cycle begins (see phase).

159

Installation of the discrete reflex module

Illustration

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

x t1i

t2i t1i

t2i

x Aux

160

TLX DS 57 PL7 40E 09.2000

Installation of the discrete reflex module

Reflex function block: 2 value monostable Role

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

Structure

The table below shows the block’s different interfaces. Name

Meaning

E

Monostable input.

Sel

Selection of time-out t1i or t2i. Sel = 0 : t1i on-delay, Sel = 1 : t2i on-delay,

l l

Direct

Selection of block (for string operation). Direct = 0: block selected Direct = 1: block not selected (output x takes the value of E).

l l

x

Monostable’s physical output.

x Aux

Block’s internal auxiliary output.

Illustration E

Operation

Set

t1i

Direct

t2i

Output x

Output x Aux

This table describes the different operating phases of the 2 value monostable. Phase

TLX DS 57 PL7 40E 09.2000

2-values MONO

Description

1

On the rising edge of input E : l a time-out corresponding to the status of input Sel is launched (time base of 0.1ms), l outputs x and x Aux change to 1.

2

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

161

Installation of the discrete reflex module

Illustration

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

Description

1

On the rising edge of input E of the first block: l the time-out is launched, corresponding to: l the block whose Direct input is at 0, l the status of the Sel input. l outputs x and x Aux change to 1. Note: Two blocks must not simultaneously have their Direct inputs set to 0.

2

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

Note:When stringing together several blocks It is essential to change the statuses of the Sel and Direct inputs only when the status of input E is set to 0.

Illustration

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

Set Direct

162

2-values MONO

t1i t2i

Output x

E

Output x Aux

Direct

Set

2-values MONO

t1i t2i

Output x 1

Output x Aux

TLX DS 57 PL7 40E 09.2000

Installation of the discrete reflex module

Reflex function block: Oscillator Role

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

Structure

The table below shows the block’s different interfaces. Name

Meaning

Illustration

E

Oscillator input.

x

Oscillator’s physical output.

x Aux

Block’s internal auxiliary output.

E

Output x

OSCILLATOR

t1i t2i

Operation

This table describes the different operating phases of the oscillator. Phase

Illustration

Output x Aux

Description

1

On the rising edge of input E : l output x oscillates for period t1i +t2i where: l t1i = length of high status of oscillation (time base of 0.1ms), l t2i = length of low status of oscillation (time base of 0.1ms), l output x Aux changes to 1.

2

On the falling edge of input E: l output x changes to 0 as soon as t1i for the current period is over, l the x output changes to 0 when the current period is over.

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

x t1i

t2i

t1i

t2i

x Aux

TLX DS 57 PL7 40E 09.2000

163

Installation of the discrete reflex module

Reflex function block: D flip-flop Role

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

Structure

The table below shows the block’s different interfaces. Name

Meaning

D

Flip-flop input.

CLK

Enable input.

SET

Output x set to 1.

RESET

Output x set to 0. This input takes priority over SET input.

x

Flip-flop’s physical output.

x Aux

Block’s internal auxiliary output.

Illustration E

D flip-flop

Output x

Clk Set Output x Aux

Reset

Operation

This table describes the different operating phases of the D flip-flop. Phase 1

164

Description On the rising edge of input CLK: l output x takes the status of input D, l output x Aux takes the opposite status to input D.

TLX DS 57 PL7 40E 09.2000

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

TLX DS 57 PL7 40E 09.2000

165

Installation of the discrete reflex module

Reflex function block: T flip-flop Role

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

Structure

The table below shows the block’s different interfaces. Name

Meaning

E

Flip-flop input.

CLK

Enable input.

SET

Outputs x / x Aux set respectively to 1 / 0.

RESET

Outputs x / x Aux set respectively to 0 / 1. This input takes priority over SET input.

x

Flip-flop’s physical output.

x Aux

Block’s internal auxiliary output.

Illustration E

T flip-flop

Output x

Clk Set Output x Aux

Reset

Operation

This table describes the different operating phases of the T flip-flop. Phase 1

166

Description On the rising edge of input CLK: l if input E is at 1: l output x takes the opposite status to its current status, l output x Aux takes the opposite value to x, l if input E is at 0, outputs x and x Aux remain at that status.

TLX DS 57 PL7 40E 09.2000

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

TLX DS 57 PL7 40E 09.2000

167

Installation of the discrete reflex module

Reflex function block: 2 threshold counter Role

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

Structure

The table below shows the block’s different interfaces. Name

Meaning

E

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

Up

Counting input. Note: the maximum performance of the counter is 2 Khz (with the Up input directly controlled by the physical input (without filtering).

RESET

Counter initialization input. In order to take into account a change in the value of the threshold to be reached, a Reset is required.

Sel

Selection of counting threshold: Sel = 0 : threshold th1 selected, Sel = 1: threshold th2 selected, Note: the maximum value of a threshold corresponds to the maximum number of points (65536points).

l l

x

Counter’s physical output.

x Aux

Block’s internal auxiliary output.

Illustration E

COUNTER, 2

Output x

Up Reset Set

168

th1 th2

Output x Aux

TLX DS 57 PL7 40E 09.2000

Installation of the discrete reflex module

Operation

This table describes the different operating phases of the 2 threshold counter. Phase

Illustration

Description

1

On the rising edge of RESET input: l counter initialized to 0 l inputs x and x Aux change to 0, l Counter increased on the rising edge of Up input .

2

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

3

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

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

Sel E

Up

th2 th1 x

x Aux

TLX DS 57 PL7 40E 09.2000

169

Installation of the discrete reflex module

Reflex function block: Came électronique simple Role

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

Structure

The table below shows the block’s different interfaces. Name

Meaning

E

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

Up

Counting input. Note: the maximum performance of the counter is 2 Khz (with the Up input directly controlled by the physical input (without filtering).

RESET 0

Output x forced to 0.

RESET 1

Counter initialization input. Note: If the counter is not reset to 0, when it reaches the maximum value (65536 points), it will change to 0,1,2 etc. Therefore it is advisable to inhibit counting (E=0) by using the x Aux output in series with output E.

x

Cam’s physical output.

x Aux

Block’s internal auxiliary output.

Illustration E

Single electronic CAM

Output x

UP Reset0 Reset1

170

ti th

Output x Aux

TLX DS 57 PL7 40E 09.2000

Installation of the discrete reflex module

Operation

This table describes the different operating phases of the simple cam. Phase 1

Illustration

Description On the rising edge of input RESET 1: l counter initialized to 0 l input x Aux changes to 1, On the high status of input RESET 0: l input x is forced to 0.

2

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

3

When threshold th1 is reached, output x changes to 1.

4

When threshold th2 is reached, outputs x and x Aux change to 0.

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

RESET 1

E

Up th2 th1

x

x Aux

TLX DS 57 PL7 40E 09.2000

171

Installation of the discrete reflex module

Reflex function block: 1 threshold intervalometer Role

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

Structure

The table below shows the block’s different interfaces. Name

Meaning

E

Intervalometer initialization input.

RESET 1

Outputs x and x Aux are set to 0.

ti

Time-base (0.1ms to 6.5535 s).

x

Intervalometer’s physical output.

x Aux

Block’s internal auxiliary output.

Illustration E

INTERVALOMETER, 1

Output x

ti Reset1

Operation

Output x Aux

This table describes the different operating phases of the intervalometer. Phase

172

th

Description

1

On the rising edge of input E : l counter initialized to 0 l input x changes to 0.

2

Counter increases at the rate of time-base ti.

3

When threshold th is reached, output x changes to 1.

4

On the falling edge of input E with output x at 1, output x Aux changes to 1.

TLX DS 57 PL7 40E 09.2000

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

TLX DS 57 PL7 40E 09.2000

173

Installation of the discrete reflex module

Reflex function block: Burst Role

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

Structure

The table below shows the block’s different interfaces. Name

Meaning

Illustration

E

Block’s input.

x

Block’s physical output.

x Aux

Block’s internal auxiliary output.

E

Output x

BURST

ti ni

Operation

This table describes the different operating phases of the Burst function block. Phase

Illustration

Output x Aux

Description

1

On the rising edge of input E : l oscillation of output x for ni periods of time, l input x Aux changes to 1,

2

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

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

x ti

ti

x Aux

174

TLX DS 57 PL7 40E 09.2000

Installation of the discrete reflex module

Reflex function block: PWM (Pulse Width Modulation) Role

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

Structure

The table below shows the block’s different interfaces.

Operation

Name

Meaning

E

Block’s input.

x

Block’s physical output.

x Aux

Block’s internal auxiliary output (control output).

E

PWM generation

Output x

t1i t2i

Output x Aux

This table describes the different operating phases of the PWM function block. Phase

Illustration

Illustration

Description

1

On the rising edge of input E : l oscillation of output x, l control input x Aux changes to 1.

2

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

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

x t2i t1i

x Aux

TLX DS 57 PL7 40E 09.2000

175

Installation of the discrete reflex module

Reflex function block: Detection of underspeed Role

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

Structure

The table below shows the block’s different interfaces. Name

Operation

E

Enable function input.

FB

Control input.

x

Block’s physical output.

x Aux

Block’s internal auxiliary output.

Illustration E

slow speed detection 1

Output x

t1i FB

t2i

Output x Aux

This table describes the different operating phases of the speed detection. Phase

176

Meaning

Description

1

On the rising edge of input E : l time-out t1i (masking time) is launched, l input x changes to 1.

2

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

TLX DS 57 PL7 40E 09.2000

Installation of the discrete reflex module

Illustration

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

FB t slaves 16 to 31 respectively have been detected.

Description of words %MWxy.0.6 to %MWxy.0.21

The table below provides the meaning of the different bits of words %MWxy.0.6 to %MWxy.0.21.

Address

Function

Meaning

%MWxy.0.6 to %MWxy.0.21

I/O configuration and ID of all detected slaves

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.

Description of word %MWxy.0.22

The table below provides the meaning of the word %MWxy.0.22.

Address

Function

Meaning

%MWxy.0.22

Parameter data of last parametered slave.

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

The table below provides the meaning of the word %MWxy.0.23.

Address

Function

%MWxy.0.23

Address of last parametered Contains the address of last parametered slave. slave.

250

Meaning

TLX DS 57 PL7 40E 09.2000

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. 261 ) or Data exchange off mode (See AS-i data exchange off operating mode, p. 262 ) of the AS-i master. Note: Using this object requires a thorough knowledge of AS-i communication principles.

Description

The table below shows the coding of bits 0 to 3 of the word %MWxy.0.24 allowing access to the different modes. Bit 3

Bit 2

Bit 1

Bit 0

Function

0

0

0

0

Normal operating mode

0

0

0

1

Activation of offline mode

0

0

1

0

Disabling offline mode

0

0

1

1

No effect

0

1

0

0

Activation of data exchange off mode

1

0

0

0

Disabling data exchange off mode

1

1

1

1

No effect

Note: Offline mode has priority over data exchange off mode.

TLX DS 57 PL7 40E 09.2000

251

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

252

Meaning no meaning Contain the parameter values for slaves 1 to 31 respectively.

TLX DS 57 PL7 40E 09.2000

Bits and words associated with the AS-i function

Explicit exchange object: Status %MWxy.MOD.2:Xj At a Glance

This word type object provides information on the state of the module.

Description

The table below provides the meaning of the different bits of the word %MWxy.MOD.2:Xj. Address

Function

%MWxy.MOD.2:X0

Standard module status

%MWxy.MOD.2:X1

TLX DS 57 PL7 40E 09.2000

Meaning for Xj = 1 Internal error. Configuration fault.

%MWxy.MOD.2:X2

Line fault.

%MWxy.MOD.2:X3

Not used.

%MWxy.MOD.2:X4

Not used.

%MWxy.MOD.2:X5

Not used.

%MWxy.MOD.2:X6

Module missing.

%MWxy.MOD.2:X7

Not used.

253

Bits and words associated with the AS-i function

254

TLX DS 57 PL7 40E 09.2000

AS-i operating mode

14

At a Glance Subject of this Chapter

This Chapter introduces the different AS-i function operating modes.

What’s in this Chapter?

This Chapter contains the following Maps:

TLX DS 57 PL7 40E 09.2000

Topic

Page

AS-i operating mode: General

256

AS-i protected mode

259

AS-i wiring test mode

260

AS-I offline operating mode

261

AS-i data exchange off operating mode

262

255

AS-i operation

AS-i operating mode: General At a Glance

256

The AS-i function allows four operating modes, each one fulfilling particular needs. These modes are: l protected mode, l wiring test mode (can be accessed using the button on the front panel of the module), l offline mode, l data exchange off mode.

TLX DS 57 PL7 40E 09.2000

AS-i operation

Operating mode

The figure below shows the general schema of AS-i bus functioning.

PLC off

Offline mode

Start AS-i master module

PLC on

No

Activate wiring test

No

Is the master configured? Yes

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. 261 ou AS-i data exchange off operating mode, p. 262). (2) : The module exits the wiring test mode and passes to protected mode if it receives a configuration.

TLX DS 57 PL7 40E 09.2000

257

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

AS-i bus

Configured mode (1)

Protected mode

Non-configured mode (1)

Wiring test mode (Configuration mode)

Legend: (1)

258

These PLC notions (ie. configured, non-configured) concern the declaration of the module and slave devices in the PL7 application hardware configuration screen.

TLX DS 57 PL7 40E 09.2000

AS-i operation

AS-i protected mode At a Glance

The AS-i protected operating mode is the mode generally used for an application which is running. It is assumed that the TSX SAY 100 module is configured in PL7. This: l continually checks that the list of detected slaves is the same as the list of expected slaves. l monitors the power supply. In this mode, a slave will only be activated if it has been declared in the configuration and been detected.

Principle of 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

TLX DS 57 PL7 40E 09.2000

259

AS-i operation

AS-i wiring test mode At a Glance

The Wiring test mode, particularly useful when starting new installations, is used to display on the front panel of the TSX SAY 100 module: l expected and detected slaves, l unexpected and non-detected slaves, l expected and non-detected slaves, or unexpected and detected slaves. For each slave present on the bus, this mode can also be used to display the state of I/O bits. Note: LDS and LAS lists, as well as slave adjustment parameters, cannot be accessed in this mode.

Access conditions

The wiring test mode is an AS-i function which can be accessed when:

l the TSX SAY 100 module is in non-configured mode.

This mode is obtained when: l the TSX SAY 100 module has not been declared in the application, l the PLC processor is missing. l each device has a unique address, l 0 address is not used.

260

TLX DS 57 PL7 40E 09.2000

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:

l from PL7 application software by acting on bits 0 and 1 of the word %MWxy.0.24, l automatically when an AS-i power supply fault is detected. Remember: Bit 7 of word %MWxy.0.24 set on 1 indicates that the AS-i bus is in offline mode.

TLX DS 57 PL7 40E 09.2000

261

AS-i operation

AS-i data exchange off operating mode At a Glance

The AS-i data exchange off mode is an advanced operating mode which can be used in debugging or maintenance. Note: To use it, you must be thoroughly familiar with AS-i communication.

Principle

When the offline data exchange mode is engaged, exchanges on the bus continue to function, but data is not longer refreshed.

Procedure

The data exchange off operating mode can be accessed from PL7 application software by acting on bits 2 and 3 of the %MWxy.0.3 word. Remember: Bit 8 of word %MWxy.0.3 set on 1 indicates that the AS-i bus is in data exchange off mode.

262

TLX DS 57 PL7 40E 09.2000

AS-i performance

15

AS-i bus performance At a Glance

The AS-i bus is independently managed by the master. This exchanges data on each cycle with each slave device configured on the bus (in ascending order of slave address number).

AS-i scanning time

t scanning time represents the exchange time between the master and n slaves (31 maximum). Either: l t = 156 micro seconds x (n+2), if n < 31, l t = 156 micro seconds x (n+1), if n = 31. Thus the scanning time cannot exceed 5 ms.

AS-i response time

T response time represents the AS-i cycle time. This includes: l the bus scanning time, l the update of the AS-I module internal memory, l the PLC cycle.

Example

The table below shows three examples of T response time for a PLC task lasting 10 ms, 30 ms, and 60 ms. This T time is for a bus loaded with 31 slaves operating normally with no link faults.

TLX DS 57 PL7 40E 09.2000

PLC task

Typical response time

Maximum response time

10 ms

35 ms

56 ms

30 ms

65 ms

96 ms

60 ms

110 ms

156 ms

263

AS-i performance

264

TLX DS 57 PL7 40E 09.2000

Operator Dialog functions

IV

Introduction Subject of this part

This part introduces the specific built-in Operator Dialog functions of PL7 and describes the software setup.

What’s in this part?

This Part contains the following Chapters:

TLX DS 57 PL7 40E 09.2000

Chapter

Chaptername

Page

16

General presentation of the Operator Dialog functions

267

17

Built-in DOP functions

269

18

Appendices

331

265

Operator Dialog functions

266

TLX DS 57 PL7 40E 09.2000

General presentation of the Operator Dialog functions

16

General presentation Introduction

The PL7 software allows the implementation of specific functions, designed to simplify the use of an operator dialog terminal (version 2.0 and higher) on a TSX Premium PLC. These functions are the basic elements of the PL7 language. They allow the following actions to be carried out without referring to the communication media between the command console CCX 17 and the PLC: l displaying messages, l displaying message and alarm message groups, l entering values from the PLC program. Hence the Operator Dialog functions are completely integrated in the PLC application and support: l data cohesion, l unique saving, l easy maintenance, l simplified consoles. l ... The processing of these functions occurs asynchronously to the processing of the operative task that enabled their activation.

How to access a DOP function

TLX DS 57 PL7 40E 09.2000

See Application-specific instructions, p. 60 .

267

General presentation

Conditions for using built-in DOP functions

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).

Example of a DOP function

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: %MW0 %KW40 Data to Send:

6 2

Report:

%MW100

4

Commands Clear Screen

Line

Line number

Print

Clear

Print

Clear

1

Entry log Alarm log Alarm management Cancel an Alarm OK

Alarm number

1

Cancel

LD Language %M100

%MW100>>

OPERATE PANEL_CMD (ADR#0.0.4, %KW0:2, %MW>>

IL Language LDN %100 ANDN %MW100:X0 [PANEL_CMD (ADR#0.0.4, %KW0:2, %MW0: 4 ) ]

ST Language IF NOT %M100 AND NOT %MW100. X0 THEN PANEL_CND (%MW0 . 6,%KV0 . 2,%MW100 . 4), END_-F

268

TLX DS 57 PL7 40E 09.2000

Built-in DOP functions

17

Introduction Subject of this chapter

This chapter describes the different built-in DOP functions and shows how they are set-up in PL7.

What’s in this Chapter?

This Chapter contains the following Sections:

TLX DS 57 PL7 40E 09.2000

Section

Topic

Page

17.1

Description of the parameters common to the different DOP functions

271

17.2

Description of the built-in DOP functions

288

269

Built-in DOP functions

270

TLX DS 57 PL7 40E 09.2000

Built-in DOP functions

17.1

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?

TLX DS 57 PL7 40E 09.2000

This Section contains the following Maps: Topic

Page

General

272

Parameters field: Console address

273

Parameters field: Data to be sent

277

Parameter field: Data to be received:

279

Parameters field: Report

280

Message field

284

Field zone

286

271

Built-in DOP functions

General Introduction

The Built-in DOP functions are part of the procedure category; they do not return value, but they do possess several parameters, some of which have to be filled in. The functions use three types of parameters:

l in read only (IN) format, acknowledged at the start of function execution, l in write only (OUT) format, set at close of function execution, l in read and write format (IN/OUT), whose contents have been acknowledged at the start of function execution and are then updated by the function results. The parameter type is displayed in the Type of Parameter of the … column located in the Library functions screen. Illustration

The illustration below gives an insight into the Library functions screen where the various parameters of the selected function are displayed. PL7: Library functions

?

EF Function information:

Parameters

Detail...

Family Lib.V. App.V Name Comment ADJUST Read/write memory objects and I/O Dates, Times, and Periods2.10 ASK_MSG Variable blocking entry on CCX Diagnostics 1.01 ASK_VALUEVariable blocking entry on >> Integrated DOP 3.03 3.03 ASSIGN_K Dynamic key assignment >> Explicit exchanges 1.00 Call format PROCEDURE parameter: Name Type Kind Comment Entry field ADR AR_W IN CCX17 address table DATA AR_W IN Table for data to be sent VAL AR_W OUT Table for data to be received

Call display ASK_MSG(

) OK

272

Cancel

TLX DS 57 PL7 40E 09.2000

Built-in DOP functions

Parameters field: Console address Introduction

This parameter contains the access path (address) for the CCX 17 dialog console. This path can be either: l located in a table of six internal words (%MW), l located in a table of six internal constants (%KW), l or passed directly to an immediate value in the form of an ADR# operator. ADR# is then assimilated into a table of six consecutive internal words.

Addressing via words or constants

The table below shows the signification of different words which make up the console address. Word number

Description Most significant

Least significant

%MWi / %KWi

6 (Uni-telway), 7 (FIPIO

0

%MWi +1 / %KWi+1

254 (1)

0 (1)

%MWi +2 / %KWi+2

Rack number

Module number

%MWi +3 / %KWi+3

CCX 17 address SYS FIPIO connection point

channel

%MWi +4 / %KWi+4

0

SYS (FIPIO)

%MWi +5 / %KWi+5

0

0

Key (1)

Operating a CCX 17 console means that only one intra-station address is authorized. As a result, the {Station.Network} pair systematically takes on the value {0.254}. Writing this field is optional.

Note: The key word SYS (value 254) corresponds to attributing an address to the system channel (UNI-TE server) for a communication channel.

TLX DS 57 PL7 40E 09.2000

273

Built-in DOP functions

Uni-telway addressing

The format of a CCX 17 address connected to the Uni-telway bus is: ADR#{.}.., ADR#{.}< rack.module>..SYS, ADR#< rack.module>.., ADR#< rack.module>.. SYS.

FIPIO addressing

The format of a CCX 17 address connected to the FIPIO bus is: ADR#{.}..\SYS, ADR#< rack.module>..\SYS.

274

TLX DS 57 PL7 40E 09.2000

Built-in DOP functions

Examples of addressing

For a CCX 17 slave on a UTW 4-5 address, connected to a TSX 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):

If you use:

in the function entry Help screen, …

you must enter the program…

internal (or constant) words

Example:

%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;

ADR syntax

Parameters Console address: %MW0

Example:

6

Parameters Console address: ADR#0.0.4

-

TLX DS 57 PL7 40E 09.2000

DOP_Function(ADR#0.0.4,...

275

Built-in DOP functions

For a slave CCX 17 connected to a TSX Premium master PLC via the built-in FIPIO link (channel 1) positioned in rack 0 (connection point no. 7). Addresses can be entered in many ways (example here using constant words %KW0 to %KW5): If you use:

in the function entry Help screen…

you must enter the program…

internal (or constant) words

Example:

%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,...;

ADR syntax

Parameters Console address: %KW0

Example:

6

Parameters Console address: ADR#\0.1.7\SYS

-

DOP_Function(ADR#\0.1.7\SYS, ...

Note: If using constants, the %KW0:6 table must be initialized beforehand using the Data editor by successively assigning the %KWi which make up the table.

276

TLX DS 57 PL7 40E 09.2000

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:

l a table of internal words (%MW), l a table of internal constants (%KW).

The table below shows the structure of data sent in this way. Word number

Role

1

Contains a contains a marker for value 16#CC17, and has a double role: l it allows the Help screen to identify a correct message and to redisplay the values on the entry screen in order to help modify or display default values. l it allows the function being carried out to check that the table received does actually contain a message for a CCX 17. In fact, it is possible to call an Integrated DOP function in a program without going via the Help/Control screens. In the case of an unmarked message, the function can immediately return an error back to the application without sending unreliable data to the console.

2

Contains the command number.

3

Contains the length of data to be sent.

4, 5, ...

Contains the data to be sent.

Note: For reasons of efficiency, the parameter can be programmed using %KWi constants. In this way the software automatically initializes this data field with adequate values. Selecting %MW bars access to different fields in the entry help box for integrated DOP functions. It is then necessary to establish, either manually or by program, the contents of the data to be sent (see PL7 MMI 17 software documentation).

TLX DS 57 PL7 40E 09.2000

277

Built-in DOP functions

Location in a CCX 17 with application

278

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: l from a table of internal words (%MW), l from a table of internal constants (%KW), l directly using an immediate integer value. The table above shows data structure when using a table. Word number

Role

1

Contains a command number

2

Contains the data to be sent to the console.

TLX DS 57 PL7 40E 09.2000

Built-in DOP functions

Parameter field: Data to be received: Introduction

This parameter only affects functions ASK_MSG and ASK_VALUE. The data is located in an %MWi internal word table (length 2 table maximum). Note: By operating the MMI console, the Data to be received parameter contains the value entered. If the status message variable is different from the data to be received, it is not changed by the entry. It only affects the display on the CCX 17.

TLX DS 57 PL7 40E 09.2000

279

Built-in DOP functions

Parameters field: Report Introduction

The report contains the parameters for managing asynchronous communication functions. It is common to all integrated DOP functions.

Report structure

The report uses a table of four internal words (%MW) containing different parameters such as: l information on function activity, l the exchange number which identifies the transaction in progress (useful when using the CANCEL communication function), l the exchange report split into two feedback codes: l the communication level, l the operation level, l the value of the timeout which is used to monitor absent responses, l the number of bytes to be sent and/or the number of bytes received. The table below show the structure of the report. Word number

Most significant byte

Least significant byte Report management

%MWi

Exchange number

Bit 0: activity bit

%MWi+1

Operation report

Communication report

%MWi+2

Timeout

User

%MWi+3

Length

System

System 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).

280

TLX DS 57 PL7 40E 09.2000

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. The different values of this report are indicated in the following table: Value

Significance of the communication report (least significant byte)

16#xx00

Successful exchange

16#0001

Stopping the exchange via a timeout

16#0002

Stopping the exchange on user request (CANCEL function)

16#0003

Incorrect address format (length is other than 6)

16#0004

Incorrect destination address (addresses unauthorized for the CCX 17, e.g.: addresses being broadcast)

16#0005

Invalid report

16#xx06

Specific parameters are invalid (particularly those concerning data to be sent)

16#0007

Destination missing

16#0008

Reserved

16#0009

Size of reception buffer is insufficient

16#000A

Size of transmission buffer is insufficient

16#000B

System resources missing (communication saturation)

16#xx14

Negative response from the CCX 17 or from the PLC (ADJUST function)

16#00FF

Message refused (the CCX 17 is not in a state where it can process it)

Note: The function can detect an error in the parameters before activating the exchange. In this case the activity bit remains 0, the report is initialized with the values corresponding to the fault.

TLX DS 57 PL7 40E 09.2000

281

Built-in DOP functions

Operation report

The operation report details the result of the operation on the remote application. It is significant if the communication report has the following values: l 16#00, l 16#06, l 16#14 (except for the ADJUST function). In other cases, the operation report is worth 0. The different values of this report are indicated in the following table:

Communication report Significance of the operation report (least significant byte)

Integrated DOP functions

16#0000

Generic positive result

All

16#1006

Number of management words below 24

ADJUST only

16#1106

Non-existent type object to be read (greater than 8)

16#1206

Inconsistency between bits RDEC and SINC

16#1306

Invalid value to be written

16#1406

Broadcast address (ALL) prohibited

16#6506

{network.station} pair different from {0.254}

16#6606

Data to be sent does not have a 16#CC17 marker

16#6706

Invalid size of data to be sent

16#6806

Invalid CCX 17 response

16#6906

Length of "Data to be received" is insufficient

16#FF06

CCX 17 link inoperational

16#0114

Command not recognized

16#0214

Command queue capacity has been exceeded

16#0414

Size of command is less that the minimum required size

16#0814

Command refused because application transfer in progress

16#1414

Inaccessible object

16#1514

System error

16#2014

Incorrect data

282

All except ADJUST

ADJUST only

All except ADJUST

TLX DS 57 PL7 40E 09.2000

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

Note: The timeout value of a communication function must be sufficient to guarantee receiving a response to the question asked. This time period depends on the type of network and on the load in effect at the moment of the transaction.

Length

TLX DS 57 PL7 40E 09.2000

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.

283

Built-in DOP functions

Message field Introduction

The message field groups together the different elements that make up the data to be displayed on the CCX 17 screen. These elements are: l the message text, l the different display attributes (position, size, etc.). l the message print command via the CCX 17.

Message text

This field is used to enter the message text that is to be displayed on the CCX 17 console. The length of the message is 40 characters max. The table below details the types of characters authorized. Characters

Comments

ASCII code above 32 (20h)

Characters that can be displayed directly or by a combination of the and keys.

The _ sign (underscore)

This character is reserved by the system to specify the optional display field for the variable associated with the message. To specify the position of the variable field, the character must be entered in the appropriate place. The system then automatically calculates the number of necessary for the length of the variable display.

Print

This parameter orders the command console to print a message when it appears on the console screen.

Overprint

This parameter refers to alarm messages only. Enabling this parameter overprints the alarm message as soon as it appears.

Line

This parameter specifies the line where the message must be displayed. Position

284

Value

Minimum

1

Default

1

Maximum

16

TLX DS 57 PL7 40E 09.2000

Built-in DOP functions

Column

This parameter specifies the column where the first message character is positioned. Position

Value(s)

Minimum

1

Default

1

Maximum

40

Automatic (1)

Left, Centered, Right

Key (1)

This mode can be accessed by selecting automatic mode. It is local to the function.

Attributes

This parameter sets the attributes of the message display. The different modes are: l Normal (when no check box has been selected), l Flashing, l Reverse video.

Size

This parameter specifies the format of all the text characters or the variable to be displayed. Possible options are: l Standard, l Double.

Clear

This field is used to associate a single command that has been executed with a message before the message has been displayed. Options are: l None (no command is associated with a message), l Line (clears the line on which the message is to be displayed), l Screen (completely clears the screen). Note: If no variable has been associated with a message, this command does not run (so use the PANEL_CMD function).

TLX DS 57 PL7 40E 09.2000

285

Built-in DOP functions

Field zone Introduction

The Field zone is used to set the different parameters for the object which is associated with a message. These parameters are: l the type of object, l the display format, l ...

Field type

This parameter sets the type of object which is associated with a message. The length of the message is 40 characters max. The table below shows the different object types possible.

Symbol

Type of object

Description

None

No field is associated with the message displayed.

Address

The object associated with the message is a variable.

Date

The message is correlated to the current PLC date.

Time

The message is correlated to the current PLC time.

This parameter specifies the symbol of the variable associated with the message. It must be set in the station database. The address associated with this symbol is automatically taken into account on confirming the screen. Note: In the case of a TSX Agent connected to the FIPIO bus, the variable is read in the bus master PLC, and not in the function sender PLC.

Address

This parameter specifies the address of the variable associated with the message. When a symbol is associated with the variable, it is automatically taken into account. Authorized objects can be: l internal bits (%Mi), l internal words (%MWi), l double internal words (%MDi).

Comment

This field displays the variable comment for viewing. This comment is set in the application data editor.

286

TLX DS 57 PL7 40E 09.2000

Built-in DOP functions

Refresh

This function specifies whether the variable contained in the message should be periodically refreshed while being displayed (function is active be default).

Display format

This parameter specifies the variable display format. The table below shows the different formats available. Format

Associated parameters

ASCII

-

Numerical

Signed (1) Number of digits before the decimal point (1), Number of digits after the decimal point (1),

Key (1)

these associated parameters can be accessed by clicking on the Modify button.

Note: From the parameters chosen, the software automatically calculates the display format.

TLX DS 57 PL7 40E 09.2000

287

Built-in DOP functions

17.2

Description of the built-in DOP functions

Introduction Subject of this section

This section describes the different built-in DOP functions.

What’s in this Section?

This Section contains the following Maps:

288

Topic

Page

List of the built-in DOP functions

289

SEND_MSG function

290

GET_MSG function

293

ASK_MSG function

296

SEND_ALARM function

298

DISPLAY_MSG function

301

DISPLAY_GRP function

302

DISPLAY_ALRM function

305

ASK_VALUE function

308

GET_VALUE function

309

CONTROL_LEDS function

312

ASSIGN_KEYS function

315

PANEL_CMD function

318

ADJUST function

321

TLX DS 57 PL7 40E 09.2000

Built-in DOP functions

List of the built-in DOP functions Introduction

The built-in DOP functions make it possible to:

l control the main functions of a CCX 17 console not containing an application (this has been neither configured nor loaded by the external design software).

l command a CCX 17 console containing an application created with the MMI17 WIN or PL7 M17 OS/2 products. The table below shows the various built-in DOP functions. Function

Description

Application Without

With

SEND_MSG

Displaying status messages contained in the PLC memory on CCX 17 with X or without variable.

-

GET_MSG

Free entry (asynchronous) of PLC variable values associated with status messages.

X

-

ASK_MSG

Blocking entry (synchronous) of a PLC variable value associated with status messages.

X

-

SEND_ALARM

Displaying alarm messages contained in the PLC memory.

X

-

DISPLAY_MSG

Displaying a status message contained in the memory of the CCX17.

-

X

DISPLAY_GRP

Displaying a group of status messages contained in the CCX17 memory.

-

X

DISPLAY_ALRM

Displaying an alarm message contained in the CCX17 memory.

-

X

ASK_VALUE

Blocking entry (synchronous) of values for the PLC variables associated with a status message contained in the CCX17 memory.

-

X

GET_VALUE

Free entry (asynchronous) of values for the PLC variables associated with a status message contained in the CCX17 memory.

X

CONTROL_LEDS

Controlling the CCX 17 LEDs and relays.

X

X

ASSIGN_KEYS

Configuring the CCX 17 command keys.

X

X

PANEL_CMD

Sending a generic command.

X

X

ADJUST

Language object adjustment.

X

X

TLX DS 57 PL7 40E 09.2000

289

Built-in DOP functions

SEND_MSG function Role

This function is used to display a message with a dynamic variable (if necessary) on a CCX 17 console screen.

Implementation

Implementation of the SEND_MSG function is developed in the Description of parameters (See Description of the parameters common to the different DOP functions, p. 271 ) section.

290

TLX DS 57 PL7 40E 09.2000

Built-in DOP functions

Application example

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 TSX Premium via the AUX port (configured in UNI-TELWAY link, addresses 4 - 5). Note: This same example, using a CCX 17 with application, is shown using the DISPLAY_GRP function.

Application description

Variables used

The aim of this example is, after setting application to RUN (%S13 =1): l initializing the PLC variables, l writing the console address (ADR#0.04) in a word table, l adjustment of timeout to 50 s, l conditions of execution, l clearing the console screen (see PANEL_CMD function), l to display status messages on the console screen: l Manu and Auto (standard format, positioned on line 1, Column 1), l Four 4 (double format, automatic centering, Line 4), l storing the function display execution.

%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,

Introduction to the console

Program corresponding to the application Fixed messages

Manu

Auto

Four 4

TLX DS 57 PL7 40E 09.2000

(* 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;

291

Built-in DOP functions

Entry help screens corresponding to the application: SEND_MSG Parameters Console address: %MW0 %KW0 Data to Send:

6 28

Report:

%MW100

4

Message Text: Manu Position Mode Manual Auto

Auto Column 1 Line 1 Column alignment Left

Centered

Right

Print Attributes Flashing

Address Address:

Symbol: Comment: Display format

Reverse video Double SEND_MSG Parameters Console Scree %MW0 Line address: Data to Send: %KW40

Clear None

Field Field type None

Size Standard

Date

Cancel

Left

%MW100

Report:

Message Text:TimeFour 4 Position Column 15 Mode Update Line 4 Manual Column alignment Auto Modify

OK

6 12

Print Attributes Flashing

Size Standard

Reverse video

Centered Right

Clear None

4

Double Scree

Line

Field Field type None

Address Address:

Symbol: Comment: Display format

Date

Time Update

Modify OK

292

Cancel

TLX DS 57 PL7 40E 09.2000

Built-in DOP functions

GET_MSG function Role

This function is used to display, on the screen of a CCX 17 console, a message with a variable which can be modified by the operator. The entry is made in multiple mode. The operator thus has the possibility of entering several variables successively, and the PLC program processes the entered value when the variable appears.

Implementation

Implementation of the GET_MSG function is developed in the Description of parameters (See Description of the parameters common to the different DOP functions, p. 271) 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

entry on the CCX 17 console keyboard must be within the limits defined by the Min and Max values in the Entry field in order to be taken into account by the application (1).

Increment

display on the CCX 17 console screen is incremented or decremented from the value of the increment (1).

Key (1)

TLX DS 57 PL7 40E 09.2000

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.

293

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 TSX Premium via the AUX port (configured in UNI-TELWAY link, addresses 4 - 5). Note: This same example, using a CCX 17 with application, is shown using the GET_VALUE function.

Application description

Variables used

Initial conditions l writing the console address (ADR#0.04) in a table of words, l adjustment of timeout to 50 s, l condition of execution, Application: The aim of this example is, on user request: l to display a status message on the console screen: l Temperature = xxx °C (standard format, automatic centering, Line 6, variable with attributes: increment of 50, three-digit integer, periodic refreshing), l storing the function execution.

%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

294

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;

TLX DS 57 PL7 40E 09.2000

Built-in DOP functions

Entry help screen corresponding to the application: GET_MSG Parameters Console address: %MW0 %KW1000 Data to Send:

Report:

Message Text: Temperature=____°C Position Column 11 Line 6 Mode Manual Column alignment Auto

Left

%MW100

4

34 Print Attributes

Centered Right

Field Symbol: Comment: Display format

Size

Flashing

Standard

Reverse video

Double

Address: %MV10

Update

Modify

999 Entry Value Not Checked

Limited

Increment Increment: 50

Ok

TLX DS 57 PL7 40E 09.2000

Cancel

295

Built-in DOP functions

ASK_MSG function Role

This function is used to display, on the screen of a CCX 17 console, a message with a variable which can be modified by the operator. The entry is made in synchronized mode. Therefore, it is possible to make one single operator entry at each message display.

Implementation

Implementation of the ASK_MSG function is developed in the Description of parameters (See Description of the parameters common to the different DOP functions, p. 271 ) section. Note: It is strongly advisable to assign parameters for the timeout for an infinite period (see Parameters field: Report, p. 280 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

entry on the CCX 17 console keyboard must be within the limits defined by the Min and Max values in the Entry field in order to be taken into account by the application (1).

Increment

display on the CCX 17 console screen is incremented or decremented from the value of the increment (1).

Key (1)

296

The value or the increment entered on the CCX 17 console keyboard follows the display format (e.g.: 9999.99), this determines the whole parts and decimal parts authorized by the user entry.

TLX DS 57 PL7 40E 09.2000

Built-in DOP functions

Example

The illustration below shows an example of ASK_MSG function entry. ASK_MSG Parameters Console address: ADR#,LL0.1.7,SYS %KW20 34 Data to Send:

Data to receive: Report:

%KW200 %KW10

2 4

Message Text: ASK MSG:_ Position Line 5 Column 5 Mode Manual Column alignment Auto

Left

Print Attributes

Centered Right

Field Symbol: Comment: Display format

Size

Flashing

Standard

Reverse video

Double

Address: %MV100

99

Modify

Entry Value Not Checked

Limited

Ok

TLX DS 57 PL7 40E 09.2000

Increment

Cancel

297

Built-in DOP functions

SEND_ALARM function Role

This function is used to activate, on the screen of a CCX 17 console, an alarm message present in the PLC. Note: Alarm messages are always displayed on the second line of the screen (Superimpose parameter activated). They are dated and timed by the console which synchronizes them with the PLC clock.

Implementation

Implementation of the SEND_ALARM function is developed in the Description of parameters (See Description of the parameters common to the different DOP functions, p. 271 ) section. Note: It is imperative that the associated message in the CCX 17 console is deactivated on the disappearance of the alarm in the PLC (see function PANEL_CMD), in order to enable a potential new activation of this alarm.

Specific parameter: Alarm number

298

The Alarm number parameter defines the alarm message identifier. Its value is between 900 and 999.

TLX DS 57 PL7 40E 09.2000

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 TSX Premium via the AUX port (configured in UNI-TELWAY link, addresses 4 - 5). Note: This same example, using a CCX 17 with application, is shown using the DISPLAY_ALARM function.

Application description

Variables used

Initial conditions l writing the console address (ADR#0.04) in a table of words, l adjustment of timeout to 50 s, l condition of execution, Application: The aim of this example is: l to detect overshoot of a temperature threshold (500 °C), l to display an alarm message on the console screen: l Overheat four = xxx °C (standard format, automatic setting imposed by the function, variable with attributes: increment of 50, three-digit integer), l storing the function execution.

%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

Program corresponding to the application Alarm message

*ALARM* Oven overheating = xxx °C

TLX DS 57 PL7 40E 09.2000

(*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;

299

Built-in DOP functions

Entry help screen corresponding to the application: SEND_ALARM Parameters Console address: %MW0 %KW120 Data to be sent:

6 29

%MW110

Report:

Message Text:

4

Print

Oven overheating = ____°C Size Alarm number: 901 Standard

Double

Field Symbol:

Address:

Overprint %MW10

Comment: Display format 999 OK

300

Modify

Cancel

TLX DS 57 PL7 40E 09.2000

Built-in DOP functions

DISPLAY_MSG function Role

This function is used to display a message contained in the CCX 17 operator dialog console memory.

Implementation

Implementation of the DISPLAY_MSG function is developed in the Description of parameters (See Description of the parameters common to the different DOP functions, p. 271) 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: ADR# 0.0.4 Data to be sent: %KW200

Report:

%MW10

4

Value of data to be sent Message number:

1

OK

TLX DS 57 PL7 40E 09.2000

Cancel

301

Built-in DOP functions

DISPLAY_GRP function Role

This function is used to simultaneously display a group of messages contained in the CCX17 operator dialog console memory.

Implementation

Implementation of the DISPLAY_MSG function is developed in the Description of parameters (See Description of the parameters common to the different DOP functions, p. 271 ) section.

Specific parameter: Message group number

The Message group number parameter defines the group message identifier contained in the CCX 17 memory. Its value is between 1 and 100.

302

TLX DS 57 PL7 40E 09.2000

Built-in DOP functions

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 TSX Premium via the AUX port (configured in UNI-TELWAY link, addresses 4 - 5). Note: This same example, using a CCX 17 without application, is shown using the SEND_MSG function.

Application description

Variables used

The aim of this example is, after setting application to RUN (%S13 =1): l initializing the PLC variables, l writing the console address (ADR#0.04) in word table, l adjustment of timeout to 50 s, l condition of execution, l clearing the console screen (see PANEL_CMD function), l displaying the group of state n°1 messages contained in the CCX 17 application, for: l message n°1: Manu and Auto (standard format, moved to line 1, Column 1), l message n°2: Four 4 (double format, automatic centering, Line 4), l storing the function execution.

%MW0:6: console address %KW0:x: message 1 data to send %MW100:4: report %MW100:X0: activity bit %MW102: timeout %M100: activation condition

Introduction to the console

Program corresponding to the application Fixed messages

Manu

Auto

Oven 4

TLX DS 57 PL7 40E 09.2000

(* 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;

303

Built-in DOP functions

Entry help screen corresponding to the application: DISPLAY_GRP Parameters Console address: %MW10 %KW0 Data to be sent:

6

Report:

%MW100

4

Value of data to be sent Message group number:

1

OK

304

Cancel

TLX DS 57 PL7 40E 09.2000

Built-in DOP functions

DISPLAY_ALRM function Role

This function is used to display an alarm message contained in the CCX17 operator dialog console memory.

Implementation

Implementation of the DISPLAY_ALRM function is developed in the Description of parameters (See Description of the parameters common to the different DOP functions, p. 271) section. Note: It is imperative that the associated message in the CCX 17 console is deactivated on the disappearance of the alarm in the PLC (see function PANEL_CMD), in order to enable a potential new activation of this alarm.

Specific 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:

l letter box (requires MMI 17 WIN software), l built-in DOP functions Note: Only the alarms with numbers higher than the length of the letterbox can be accessed by the DISPLAY_ALRM function.

TLX DS 57 PL7 40E 09.2000

305

Built-in DOP functions

Application example

The example given below makes use of the DISPLAY_ALARM function to display an alarm message on the screen of a T CCX 1720 W console containing an application. This is connected to a TSX Premium via the AUX port (configured in UNI-TELWAY link, addresses 4 - 5). Note: This same example, using a CCX 17 with application, is shown using the SEND_ALARM function.

Application description

Variables used

Initial conditions l writing the console address (ADR#0.04) in a word table, l adjustment of timeout to 50 s, l condition of execution, Application: The aim of this example is: l to detect overshoot of a temperature threshold (500 °C), l to display the alarm message contained in the CCX 17 application, for: l Overheat four = xxx °C (standard format, automatic setting imposed by the function, variable with attributes: increment of 50, three-digit integer), l storing the function execution.

%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

306

TLX DS 57 PL7 40E 09.2000

Built-in DOP functions

Introduction to the console System display

Program corresponding to the application Alarm message

(*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;

*ALARM* Oven overheating = xxx °C

Entry help screen corresponding to the application: DISPLAY_ALRM Parameters Console address: %MW0 Data to be sent: %KW150

6

Report:

%MW100

4

Value of data to be sent Number of alarm message:

1

OK

TLX DS 57 PL7 40E 09.2000

Cancel

307

Built-in DOP functions

ASK_VALUE function Role

This function is used to display a status message contained in the CCX17 operator dialog console memory on a CCX 17 console screen. This message includes a variable, which can be modified by the operator. The entry is made in synchronized mode. Therefore, it is possible to make one single operator entry at each message display.

Implementation

Implementation of the ASK_VALUE function is developed in the Description of parameters (See Description of the parameters common to the different DOP functions, p. 271 ) section. Note: It is strongly advisable to assign parameters for the timeout for an infinite period (see Parameters field: Report, p. 280 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: ADR# 0.0.4 %KW20 Data to be sent:

6

Data to receive: Report:

%MW10 %MW20

2 4

Value of data to be sent Status message number:

3

OK

308

Cancel

TLX DS 57 PL7 40E 09.2000

Built-in DOP functions

GET_VALUE function Role

This function is used to display a status message contained in the CCX17 operator dialog console memory on a CCX 17 console screen. This message includes a variable, which can be modified by the operator. Entry is made in multiple mode. The operator thus has the possibility of entering several variables successively, and the PLC program processes the entered value when the variable appears.

Implementation

Implementation of the GET_VALUE function is developed in the Description of parameters (See Description of the parameters common to the different DOP functions, p. 271) section.

Specific parameter: Status message number

This parameter defines the message identifier contained in the CCX 17 memory. Its value is between 1 and 300.

TLX DS 57 PL7 40E 09.2000

309

Built-in DOP functions

Application example

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 TSX Premium via the AUX port (configured in UNI-TELWAY link, addresses 4 - 5). Note: This same example, using a CCX 17 without application, is shown using the GET_MSG function.

Application description

Variables used

Initial conditions l writing the console address (ADR#0.04) in a word table, l adjustment of timeout to 50 s, l condition of execution, Application: The aim of this example is, on user request: l initializing the PLC variables, l displaying message n°4 contained in the CCX17 application, for: l Temperature = xxx °C (standard format, automatic centering, Line 6, variable with attributes: increment of 50, three-digit integer, periodic updating), l storing the function execution.

%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

310

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;

TLX DS 57 PL7 40E 09.2000

Built-in DOP functions

Entry help screen corresponding to the application: GET VALUE Parameters Console address: %MW0 Data to be sent: %KW100

6

Report:

%MW100

4

Value of data to be sent Status message number:

4

OK

TLX DS 57 PL7 40E 09.2000

Cancel

311

Built-in DOP functions

CONTROL_LEDS function Role

This function is used to control some CCX 17 console functions. These functions are: l relay state (version 2.1 and above), l state of the small luminous column LEDs. The CONTROL_LEDS function is available whether or not the CCX 17 has an application.

Implementation

Implementation of the CONTROL_LEDS function is developed in the Description of parameters (See Description of the parameters common to the different DOP functions, p. 271 ) section.

Specific parameter: LED status

This parameter defines the current status of each LED. The various states can be: l Unchanged, l Off, l Flashing, l On.

Specific parameter: Relay status

This parameter defines the relay status. The various states can be: l Unchanged, l Open, l Closed.

312

TLX DS 57 PL7 40E 09.2000

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 TSX Premium via the AUX port (configured in UNI-TELWAY link, addresses 4 - 5).

Application description

Variables used

Initial conditions l writing the console address (ADR#0.04) in a word table, l adjustment of timeout to 50 s, l condition of execution, Application: The aim of this example is, on rising edge of the variables: l Manu: controlling the green LED in Flashing mode, l Auto: controlling the green LED inOn mode

%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;

TLX DS 57 PL7 40E 09.2000

313

Built-in DOP functions

Entry help screens corresponding to the application: CONTROL_LEDS Parameters Console address: %MW0 Data to Send: %KW200

6 2

Report:

%MW100

4

LED status Unchanged

Off

Flashing

On

Unchanged

Off

Flashing

On

Unchanged

Off

Flashing

On

Relay status Open

Unchanged OK

Cancel

CONTROL_LEDS Parameters Closed Console address: %MW0 %KW210 Data to Send:

6 2

Report:

%MW100

4

LED status Unchanged

Off

Flashing

On

Unchanged

Off

Flashing

On

Unchanged

Off

Flashing

On

Relay status Open

Unchanged OK

314

Closed

Cancel

TLX DS 57 PL7 40E 09.2000

Built-in DOP functions

ASSIGN_KEYS function Role

This function is used to configure all or some of the command keys of a CCX 17 console by linking them to internal bits from the communication master PLC. Using this function globally modifies the configuration of the affected command keys. The maximum number of keys that can be configured is twelve, however, only the keys present on the console receiving the command are taken into account. The ASSIGN_KEYS function is available whether or not the CCX 17 has an application.

Parameters Zone

The principle of implementing the Parameters zone is elaborated in the Description of parameters (See Description of the parameters common to the different DOP functions, p. 271) section.

Zone: Set by

This zone is used to specify which out of the PLC or CCX 17 contains the key configuration data. l PLC: the data considered is that entered in the Command key zones, l CCX 17 the data considered is that from the application contained in the console.

Zone: Command key x

This zone is used to define the characteristics associated with each key. The table below shows the various possible characteristics.

TLX DS 57 PL7 40E 09.2000

Characteristics

Meaning

Inhibit

Invalidates the key status. Its confirmation inhibits the action and address / symbol fields.

Action

Defines the operating mode of the key. Selecting the mode on edge means that pushing in the key causes the associated bit to be set to 1, and releasing it causes it to be set to 0. Choosing counter output mode means that pushing in the key changes the bit status. The default value is on edge.

Address

Specifies the %Mi internal bit address associated with the key. If the symbol associated with this bit exists in the station database, it is automatically taken into account during address confirmation.

Symbol

Specifies the symbol associated with the bit. The address associated with this symbol is automatically taken into account.

315

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 TSX Premium via the AUX port (configured in UNI-TELWAY link, addresses 4 - 5). Note: For a CCX 17 with application, the assignment of command keys can be included here, making this PLC application unnecessary.

Application description

Variables used

Initial conditions l writing the console address (ADR#0.0.4) in a word table, l adjustment of timeout to 50 s, l condition of execution, Application: The aim of this example is: l to assign the %M0 variable to command key 1, l to assign the %M2 variable to command key 2, l storing the function execution.

%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

Program corresponding to the application Key 2

(* INIT console address, condition, timeout

*) IF %S1.3 THEN %MW0:6:=ADR#0.0.4; %MW102:=500; %M108:=0; END_IF; (* Assign command keys *) IF %M12 AND NOT %M108 AND NOT %MW100:X0 THEN ASSIGN_KEYS(%MW0:6,%KW240:16,%MW100:4); END_IF;

316

TLX DS 57 PL7 40E 09.2000

Built-in DOP functions

Entry help screens corresponding to the application: ASSIGN_KEYS Parameters Console address: %MW0 Data to Send:

6 16

%KW240

%MW100

Report:

4

Set by PLC

CCX17

Command key 1 Inhibit Symbol: Manual Address: %MV0

Command key 2 Action On edge On state

Command key 3 Inhibit Symbol: Address:

TLX DS 57 PL7 40E 09.2000

Action On edge On state

Command key 4 Action On edge

Inhibit Symbol:

On state

Address:

Key 1 to 4...

Display command keys

Inhibit Symbol: Auto Address: %M2

Key 5 to 8...

OK

Action On edge On state

Key 9 to 12...

Cancel

317

Built-in DOP functions

PANEL_CMD function Role

This function is used to send various simple commands of the following type to the MMI console: l clearing a line or the screen, l printing or clearing the operator entry log, l printing or clearing the alarms log, l alarm management. Note: The PANEL_CMD function is available whether or not the CCX 17 has an application.

Parameters field

The principle of implementing the Parameters field is elaborated in the Description of parameters (See Description of the parameters common to the different DOP functions, p. 271 ) section.

Field: Command

This field is used to set the command associated with the PANEL_CMD function. For:

l clearing a line; the line number must be specified, l canceling an alarm; you must designate the alarm number which corresponds to identifier given while using SEND_ALARM or DISPLAY_ALARM.

318

TLX DS 57 PL7 40E 09.2000

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 TSX Premium via the AUX port (configured in UNI-TELWAY link, addresses 4 - 5).

Application description

Variables used

Initial conditions l writing the console address (ADR#0.04) in a word table, l adjustment of timeout to 50 s, l condition of execution, Application: The aim of this example is: l wiping the console screen on user demand, l canceling the alarm on fault acknowledgement, l storing the function execution.

%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;

TLX DS 57 PL7 40E 09.2000

319

Built-in DOP functions

Entry help screens corresponding to the application: PANEL-CMD Parameters Console address: %MW0 Data to be sent: %KW40

6 2

Report:

%MW100

4

Commands Clear Screen

Line

Line number

Print

Clear

Print

Clear

1

Entry log Alarm log Alarm management Cancel an Alarm OK

PANEL-CMD Parameters Console address: ADR#0.0.4 Data to be sent: %KW350 Alarm number 1 Commands Clear Cancel Screen

%MW50

Report:

4

2

Line

Line number

1

Entry log Print

Clear

Print

Clear

Alarm log Alarm management Cancel an Alarm OK

320

Alarm number

1

Cancel

TLX DS 57 PL7 40E 09.2000

Built-in DOP functions

ADJUST function Role

This function is used to adjust (read and write) language objects (one object at a time) from a CCX 17 or a MAGELIS, by controlling internal words in the PLC memory. The language objects which can be adjusted are: l internal bits (%Mi), l internal words or double words (%MWi, %MDi), l rack or remote inputs/outputs (%I, %Q, %IW, %QW, %ID, %QD). Note: It is strongly advised: l to only execute one instance of the ADJUST function per cycle, l to only execute the ADJUST function every n cycles. l to assign parameters to the ADJUST function with consecutive words, so as to optimize the reading of internal words on CCX 17 and MAGELIS.

Activating the 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: l an internal bit (%Mi), l an internal word extract bit (%MWi:Xj). This parameter defines the type of operation to be carried out:

l read: bit = 0, l write: bit = 1.

The types of objects assigned to this parameter may be: l an internal bit (%Mi), l an internal word extract bit (%MWi:Xj).

TLX DS 57 PL7 40E 09.2000

321

Built-in DOP functions

Type of object (TYPE)

322

This parameter defines the type of object to be read or written. The types of objects assigned to this parameter may be: l an internal word (%MWi), l an immediate value. The table below shows the different types of objects which can be controlled using the ADJUST function. Type of object

Value of internal word or immediate value

Type of object

Value of internal word or immediate value

%Mi

0

%IW

5

%MWi

1

%QW

6

%MDi

2

%ID

7

%I

3

%QD

8

%Q

4

TLX DS 57 PL7 40E 09.2000

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.

Word order number

This word contains…

Possible values of the word

Word 0

the rack number where the language object concerned is situated

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.

Word 1

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

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.

Word 2

the channel number in the module where the language object concerned is situated

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.

Word 3

the rank of the I/O object or the number of the internal language object concerned.

0 or n: bit objects, internal words or double words, I/O objects with significant rank. 0: Other I/O objects.

Word 4

the connection point number of the device n: NANET or FIPIO objects. on the FIPIO bus or the rank of the NANET 0: not significant. object.

Word 5

the position of the FIPIO module.

Word 6

the channel number in the FIPIO module or n: AS-i or FIPIO objects. the slave bit on the AS-i bus. 0: not significant.

Word 7

the slave number of the AS-i and NANET buses.

Value to write (VAL)

TLX DS 57 PL7 40E 09.2000

0: basic or not significant module. 1: extension module

n: AS-i or NANET objects. 0: not significant.

This parameter contains the value to write in the object. The object type assigned to this parameter is a double word (%MDi).

323

Built-in DOP functions

Set at 1, or Incrementation (SINC)

Depending on the type of object to be written, this parameter is used:

l to set the bit value (%Mi, %Q), l to increment by 1 the value of the word or double word (%MWi, %MDi, %QW, %QD). Note: the R_W parameter must be set to 1. The object type assigned to this parameter is an internal bit (%Mi).

Set to 0 or Decrementation (RDEC)

Depending on the type of object to be written, this parameter is used:

l to clear the bit value (%Mi, %Q), l to decrement by 1 the value of the word or double word (%MWi, %MDi, %QW, %QD). Note: the R_W parameter must be set to 1. The object type assigned to this parameter is an internal bit (%Mi).

Value of the object read (VRET)

This parameter contains the parameter value which has just been read. The object type assigned to this parameter is a double word (%MDi).

Management parameters (GEST)

The object type assigned to this parameter is a table of 24 internal words (%MWi).

324

TLX DS 57 PL7 40E 09.2000

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

Value to be entered:

Comment

EN

%MW20:X0

1

Executing the ADJUST function

R_W

%MW20:X1

0

Read operation

TYPE

%MW21

2

Type of object: %MD

ADR

%MW22

0

Not significant

%MW23

0

Not significant

%MW24

0

Not significant

%MW25

12

Object number (%MD12)

%MW26

0

Not significant

%MW27

0

Not significant

%MW28

0

Not significant

%MW29

0

Not significant

%MD30

0

Not significant

VAL

TLX DS 57 PL7 40E 09.2000

SINC

%MW20:X2

0

Not significant

RDEC

%MW20:X3

0

Not significant

VRET

%MD32

Value of the object read

MAN

%MD34:24

Buffer parameter for receiving and sending requests

325

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

Value to be entered:

Comment

EN

%MW20:X0

1

Executing the ADJUST function

R_W

%MW20:X1

1

Write operation

TYPE

%MW21

6

Type of object: %QW

ADR

326

%MW22

0

Rack number

%MW23

3

Module position

%MW24

2

Channel number

%MW25

0

Not significant

%MW26

0

Not significant

%MW27

0

Not significant

%MW28

0

Not significant

%MW29

0

Not significant

VAL

%MD30

15

Value to write

SINC

%MW20:X2

0

Not significant

RDEC

%MW20:X3

0

Not significant

VRET

%MD32

Value of the object read

MAN

%MD34:24

Buffer parameter for receiving and sending requests

TLX DS 57 PL7 40E 09.2000

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

Value to be entered:

Comment

EN

%MW20:X0

1

Executing the ADJUST function

R_W

%MW20:X1

1

Write operation

TYPE

%MW21

6

Type of object: %QW

%MW22

0

Not significant

%MW23

1

Processor address

ADR

TLX DS 57 PL7 40E 09.2000

%MW24

2

Channel number of built-in FIPIO link

%MW25

0

Not significant

%MW26

12

Connection point number

%MW27

0

Module number: Standard

%MW28

1

Channel number

%MW29

0

Not significant

VAL

%MD30

0

Not significant

SINC

%MW20:X2

0

Incrementing the word value by 1

RDEC

%MW20:X3

0

VRET

%MD32

Not significant

MAN

%MD34:24

Buffer parameter for receiving and sending requests

Not significant

327

Built-in DOP functions

To clear the output bit on the AS-i %Q\105.0\7.2 bus, the following values need to be entered: Parameter

Language object

Value to be entered:

Comment

EN

%MW20:X0

1

Executing the ADJUST function

R_W

%MW20:X1

1

Write operation

TYPE

%MW21

4

Type of object: %Q

ADR

328

%MW22

1

Rack number

%MW23

5

Module position

%MW24

0

Channel number

%MW25

0

Not significant

%MW26

0

Not significant

%MW27

0

Not significant

%MW28

2

Bit rank (slave input/output)

%MW29

7

Slave number

VAL

%MD30

0

Not significant

SINC

%MW20:X2

0

Not significant

RDEC

%MW20:X3

1

Output RESET

VRET

%MD32

Not significant

MAN

%MD34:24

Buffer parameter for receiving and sending requests

TLX DS 57 PL7 40E 09.2000

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

Value to be entered:

Comment

EN

%MW20:X0

1

Executing the ADJUST function

R_W

%MW20:X1

1

Write operation

TYPE

%MW21

6

Type of object: %QW

ADR

TLX DS 57 PL7 40E 09.2000

%MW22

0

Rack number

%MW23

4

Module position

%MW24

0

Channel number

%MW25

1

NANET object rank (word number)

%MW26

0

Not significant

%MW27

0

Not significant

%MW28

0

Not significant

%MW29

2

Slave number

VAL

%MD30

0

Not significant

SINC

%MW20:X2

0

Not significant

RDEC

%MW20:X3

1

Decrementing the word value by 1

VRET

%MD32

Not significant

MAN

%MD34:24

Buffer parameter for receiving and sending requests

329

Built-in DOP functions

330

TLX DS 57 PL7 40E 09.2000

Appendices

18

Introduction Subject of this chapter

This chapter introduces the supplementary information for installing DOP functions.

What’s in this Chapter?

This Chapter contains the following Sections:

TLX DS 57 PL7 40E 09.2000

Section

Topic

Page

18.1

Precautions for DOP use

333

18.2

Description of the built-in DOP functions "Data to send" parameter coding

334

331

Appendices

332

TLX DS 57 PL7 40E 09.2000

Appendices

18.1

Precautions for DOP use

Precautions for DOP use Introduction

The list below is not exhaustive, however, it does group together the errors most frequently encountered whilst installing DOP functions in an application.

List of precautions

l Do not forget to initialize the Time-out parameter (%MWi+2) before starting the l l l l l l l l

TLX DS 57 PL7 40E 09.2000

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.

333

Appendices

18.2

Description of the built-in DOP functions "Data to send" parameter coding

Introduction Subject of 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.

What’s in this Section?

This Section contains the following Maps: Topic

Page

PLC status message display: SEND_MSG function

334

335

PLC checked status message entry: ASK_MSG and GET_MSG function

338

PLC alarm message display: SEND_ALARM function

343

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

346

Display of luminous column LEDS: CONTROL_LEDS function

347

Configuring command keys: ASSIGN_KEYS function

348

Generic send command: PANEL_CMD function

350

TLX DS 57 PL7 40E 09.2000

Appendices

PLC status message display: SEND_MSG function Introduction

Status messages can be constructed from the PLC application by creating the send using internal words (%Mwi) as intermediaries to display them on a CCX17 console screen. This is the role of the SEND_MSG function.

Data to send parameter coding

The table below shows the significance of the different words which constitute the following parameter: Data to send (47 words maximum).

Word number

Meaning

1

contains a marker of value 16#CC17,

2

contains value 0

3

contains the length in bytes and the zone of the following words,

4 to P

contain the message text to send, this being the characters that are underlined representing the characters expected during the display of a variable. The maximum length of this text is 40 characters. If the text is composed of an odd number of characters, the last byte is worth 0, if the text is of even length and if it is less than 39 characters, the last byte must contain the value 0,

P +1

contains the line number where the message must be displayed,

P +2

contains the column number where the start of the message must be displayed,

P +3 P +4

This two word zone (four characters) contains the message characteristics and is structured as follows: Character 1

Character 2

Characters 3 and 4

This character (in capitals) corresponds to a video attribute: B = blinking, R = reverse video, A = blinking and reverse video, N = no attribute

l l l l

This character (in capitals) corresponds to the character font size: S = normal size, D = double width or height

l l

corresponds to the printing option: Y followed by a space = yes, N followed by a space = no.

l l

P+5

If you do not want to display a variable, the following word must be at 0 (in this instance, following parameters is ignored), otherwise the following parameters must be added:

P+6

contains the position of the variable to display, counted in number of characters in relation to the start of the message.

P+7

contains the number of characters to display for the variable.

P

Number of words containing the text of the message to send (see line 4 to P).

TLX DS 57 PL7 40E 09.2000

335

Appendices

Word number P+8

P+9

Meaning contains a supplementary command: 0: no command, 1: clear screen, 2: clear the line before the display.

l l l

contains the value 16#0030.

P+10 and 11 contain the type of entry field: l BIT +space = bit type, l ANA + space = word type, l LNG + space = double word type, l DAY + space = date type, l HOU + space = hour type. P+12 P+13

P+14

contains value 0. contains the type of variable to display: B +space = bit type, W + space = word type, DW = double word type, Note: for a Date or Hour type, this word contains value 0.

l l l

contains: l the address index of the variable to display for a bit, word or double word type, l value –1 for a date or hour type.

P+15 and 16 contain the display format for the variable and are structured in the following ways: Byte 1

specifies if the variable is signed (sign +), or not (space),

Bytes 2 and 3

specifies the display format: Byte 2

Byte 4

P

336

Byte 2

ASCII or DIGITAL without decimal places

the ASCII code for the space, that being 20

DIGITAL with less than ten decimal places

the ASCII code for the space, that being 20

the ASCII code for the number of decimal places

DIGITAL with at least ten decimal places

the ASCII code for the number of tens of decimal places

the ASCII code for the number of decimal place units

specifies the display type: N = no format, D = Digital, A = ASCII

l l l

Number of words containing the text of the message to send (see line 4 to P).

TLX DS 57 PL7 40E 09.2000

Appendices

Word number P+17

Meaning define if the variable must be refreshed or not: Y + space = yes, N + space = no.

l l

P+18

contains the value N + space,

P+19 to 25

contain the value 0 (7 words).

P

Number of words containing the text of the message to send (see line 4 to P).

Example of use

TLX DS 57 PL7 40E 09.2000

The example below shows the values corresponding to the word table %MW0:12 (data to send) of the SEND_MSG(ADR#0.0.4,%MW0:12,%MW100:4) function; Word number

Value

Comment

%MW0

16#CC17

Marker

%MW1

0

Imposed value

%MW2

18

Byte size of the following zone which includes nine words

%MW3

Fo

Message text

%MW4

ur

Message text (continued)

%MW5

sp4

Message text (end)

%MW6

0

End of message mark

%MW7

2

Message position (line number)

%MW8

15

Message position (column number)

%MW9

ND

Message characteristics (no attribute or double font)

%MW10

Nsp

Message characteristic (no printing)

%MW11

0

The message includes no variable

337

Appendices

PLC checked status message entry: ASK_MSG and GET_MSG function Introduction

Checked status messages can be constructed from the PLC application by creating the send using internal words (%MWi) as intermediaries to display them on a CCX17 console screen. This is the role of the ASK_MSG and GET_MSG functions.

Data to send parameter coding

The table below shows the significance of the different words which constitute the following parameter: Data to send (47 words maximum).

Word number

Meaning

1

contains a marker of value 16#CC17,

2

contains the command type: 33 = command number for ASK_MSG, 6 = command number for GET_MSG,

l l

3

contains the length in bytes and the zone of the following words,

4 to P

contain the message text to send, this being the characters that are underlined representing the characters expected during the display of a variable. The maximum length of this text is 40 characters. If the text is composed of an odd number of characters, the last byte is worth 0, if the text is of even length and if it is less than 39 characters, the last byte must contain the value 0,

P +1

contains the line number where the message must be displayed,

P +2

contains the column number where the start of the message must be displayed,

P +3 P +4

This two word zone (four characters) contains the message characteristics and is structured as follows: Character 1

Character 2

Characters 3 and 4

This character (in capitals) corresponds to a video attribute: B = blinking, R = reverse video, A = blinking and reverse video, N = no attribute

l l l l

This character (in capitals) corresponds to the character font size: S = normal size, D = double width or height

l l

corresponds to the printing option: Y followed by a space = yes, N followed by a space = no.

l l

P+5

contains the position of the variable to display, counted in number of characters in relation to the start of the message.

P+6

contains the number of characters to display for the variable.

P

Number of words containing the text of the message to send (see line 4 to P).

338

TLX DS 57 PL7 40E 09.2000

Appendices

Word number

Meaning

P+7

contains a supplementary command: l 0: no command (ASK_MSG synchronized entry), l 24: free entry authorized after display (GET_MSG multiple entry).

P+8

contains the value 16#0030.

P+9 P+10

contain the type of entry field (in Upper case): l BIT +space = bit type, l ANA + space = word type, l LNG + space = double word type.

P+11

contains value 0.

P+12

contains the type of variable to display (in Upper case): B +space = bit type, W + space = word type, DW = double word type,

l l l

P+13

contains the address index of the variable to display.

P+14 P+15

contain the display format for the variable and are structured in the following ways: Byte 1

specifies if the variable is signed (sign +), or not (space),

Bytes 2 and 3

specifies the display format: Byte 2

Byte 4

P+16

P+17

P

Byte 3

ASCII or DIGITAL without decimal places

the ASCII code for the space, that being 20

DIGITAL with less than ten decimal places

the ASCII code for the space, that being 20

the ASCII code for the number of decimal places

DIGITAL with at least ten decimal places

the ASCII code for the number of tens of decimal places

the ASCII code for the number of decimal place units

specifies the display type: l N = no format, l D = Digital, l A = ASCII

defines whether or not the variable must be updated: Y + space = yes, N + space = no.

l l

defines the field attributes: I + space = increment, L + space = others.

l l

Number of words containing the text of the message to send (see line 4 to P).

TLX DS 57 PL7 40E 09.2000

339

Appendices

Word number

Meaning

P+18 and 19 define the limit type: l 0 = unlimited, l 1 = minimum limit only, l 2 = maximum limit only, l 3 = minimum and maximum limit. P+20 and 21 contain the minimum limit value. P+22 and 23 contain the maximum limit value. P+24 and 25 contain the increment value. P

340

Number of words containing the text of the message to send (see line 4 to P).

TLX DS 57 PL7 40E 09.2000

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; Word number

TLX DS 57 PL7 40E 09.2000

Value

Comment

%MW0

16#CC17

Marker

%MW1

6

Command number for GET_MSG

%MW2

70

Byte size of the following zone which includes 35 word

%MW3

Te

Message text

%MW4

mp

Message text (continued)

%MW5

er

Message text (continued)

%MW6

at

Message text (continued)

%MW7

ur

Message text (continued)

%MW8

eesp

Message text (continued)

%MW9

=sp

Message text (continued)

%MW10

__

Message text (continued)

%MW11

_sp

Message text (continued)

%MW12

°C

Message text (end)

%MW13

0

End of message mark

%MW14

3

Text position (line number)

%MW15

11

Text position (column number)

%MW16

NS

Message characteristics (no attribute or double font)

%MW17

Nsp

Message characteristic (no printing)

%MW18

15

Position of the variable from the start of the message

%MW19

3

Number of characters to display

%MW20

24

Additional command (entered after display)

%MW21

16#0030

Reserved value

%MW22

AN

Type of entry field (AN = start of ANA)

%MW23

Asp

Type of entry field (continued)

%MW24

0

Reserved value

%MW25

Wsp

Type of variable to display (W = word type variable)

%MW26

10

Address index for the variable to display (%MW10)

%MW27

espesp

Display format (sp for a non signed variable, sp for the start of the decoding of decimal places after the point)

%MW28

spD

Display format continued (sp for the end of the coding of the number of digits after the point, D for the decimal format)

%MW29

Yesp

The variable must be updated

341

Appendices

Word number

342

Value

Comment

%MW30

Iesp

Entry is incremental

%MW31

0

The variable is not limited

%MD32

0

Minimum limit value

%MD34

0

Maximum limit value

%MD36

50

Increment value

TLX DS 57 PL7 40E 09.2000

Appendices

PLC alarm message display: SEND_ALARM function Introduction

Alarm messages can be constructed from the PLC application by creating the send using internal words (%MWi) as intermediaries to display them on a CCX17 console screen. This is the role of the SEND_ALARM function.

Data to send parameter coding

The table below shows the significance of the different words which constitute the following parameter: Data to send (37 words maximum).

Word number

Meaning

1

contains a marker of value 16#CC17,

2

contains value 0

3

contains the length in bytes and the zone of the following words,

4

contains the imaginary number given to the alarm message (this word is used after deactivating the alarm if necessary). The value of this word must be between 900 and 999.

5 to P

contain the message text to send, this being the characters that are underlined representing the characters expected during the display of a variable. The maximum length of this text is 40 characters. If the text is composed of an odd number of characters, the last byte is worth 0, if the text is of even length and if it is less than 39 characters, the last byte must contain the value 0,

P +1 and 2

This two word zone (four characters) contains the message characteristics and is structured as follows: Character 1

Character 2

Characters 3 and 4

This character (in capitals) corresponds to the character font size: S = normal size, D = double width or height.

l l

corresponds to the printing option: Y = yes, N = no.

l l

correspond to the overprinting option: Y followed by a space = yes, N followed by a space = no.

l l

P+3

If you do not want to display a variable, the following word must be at 0 (in this instance, following parameters is ignored), otherwise the following parameters must be added:

P+4

contains the position of the variable to display, counted in number of characters in relation to the start of the message.

P+5

contains the number of characters to display for the variable.

P+6

contains the value 16#0030.

P

Number of words containing the text of the message to send (see line 5 to P).

TLX DS 57 PL7 40E 09.2000

343

Appendices

Word number P+7 and 8

P+9 P+10

P+11

Meaning contain the type of entry field: BIT +space = bit type, ANA + space = word type, LNG + space = double word type,

l l l

contains value 0. contains the type of variable to display: B +space = bit type, W + space = word type, DW = double word type,

l l l

contains the address index of the variable to display.

P+12and 13 contain the display format for the variable and are structured in the following ways: Byte 1

specifies if the variable is signed (sign +), or not (space),

Bytes 2 and 3

specifies the display format: Byte 2

Byte 4

P

344

Byte 3

ASCII or DIGITAL without decimal places

the ASCII code for the space, that being 20

DIGITAL with less than ten decimal places

the ASCII code for the space, that being 20

the ASCII code for the number of decimal places

DIGITAL with at least ten decimal places

the ASCII code for the number of tens of decimal places

the ASCII code for the number of decimal place units

specifies the display type: N = no format, D = Digital, A = ASCII

l l l

Number of words containing the text of the message to send (see line 5 to P).

TLX DS 57 PL7 40E 09.2000

Appendices

Example of use

The example below shows the values corresponding to the word table %MW0:29 (data to send) of the SEND_ALARM(ADR#0.0.4,%MW0:29,%MW100:4) function; Word number

TLX DS 57 PL7 40E 09.2000

Value

Comment

%MW0

16#CC17

Marker

%MW1

0

Imposed value

%MW2

52

Byte size of the following zone which includes 26 word

%MW3

900

Alarm message number

%MW4

Su

Message text

%MW5

rc

Message text (continued)

%MW6

ha

Message text (continued)

%MW7

uf

Message text (continued)

%MW8

fe

Message text (continued)

%MW9

spf

Message text (continued)

%MW10

or

Message text (continued)

%MW11

rsp

Message text (continued)

%MW12

=sp

Message text (continued)

%MW13

__

Message text (continued)

%MW14

_sp

Message text (continued)

%MW15

°C

Message text (end)

%MW16

0

End of message mark

%MW17

SY

Message characteristic (Normal size, printing)

%MW18

Ysp

Message characteristic (overprinting)

%MW19

19

Position of the variable from the start of the message

%MW20

3

Number of characters to display

%MW21

16#0030

Reserved value

%MW22

AN

Type of entry field (AN = start of ANA)

%MW23

Asp

Type of entry field (continued)

%MW24

0

Reserved value

%MW25

Wsp

Type of variable to display (W = word type variable)

%MW26

10

Address index for the variable to display (%MW10)

%MW27

espesp

Display format (sp for a non signed variable, sp for the start of the decoding of decimal places after the point)

%MW28

spD

Display format continued (sp for the end of the coding of the number of digits after the point, D for the decimal format)

345

Appendices

Display of status, alarm or a group of messages contained in the CCX 17 memory: ASK_VALUE, DISPLAY_MSG, GET_VALUE, DISPLAY_ALRM and DISPLAY_GRP functions Introduction

For these functions it is possible to send them by using internal words (%MWi) as intermediaries. The Data to send parameter requires one word which contains accordingly: l The status message number, l Alarm message number, l Message group number

Example of use

The example below shows an example of a function using the word %MW0 (data to send). DISPLAY_GRP(ADR#0.0.4,%MW0,%MW100:4) with %MW0:=3

346

TLX DS 57 PL7 40E 09.2000

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

The table below shows the significance of the different words which constitute the following parameter: Data to send (2 words).

Word number

Meaning

1

contains a marker of value 16#CC17,

2

indicates the coding of each LED as well as the relay state to send to the terminal. l bits 0 to 3: green LED status, l bits 4 to 7: yellow LED status, l bits 8 to 11: red LED status, l bits 12 to 15: relay status, the state of each of the LEDS is coded on four bits as follows: l 0000: unchanged LED status, l 0001: LED off, l 0010: LED on, l 1111: LED flashing. the relay status is coded on bits 12 to 15 as follows: the state of each of the indicators is coded on four bits as follows: l 0000: unchanged relay status, l 0001: open relay status, l 0010: closed relay status.

Example of use

TLX DS 57 PL7 40E 09.2000

The example below shows the values corresponding to the word table %MW0:2 (data to send) of the CONTROL_1EDS(ADR#0.0.4,%MW0:2,%MW100:4) function; Word number

Value

Comment

%MW0

16#CC17

Marker

%MW1

16#1112

Green LEDS on, yellow and red off, open relay status

347

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

The table below shows the significance of the different words which constitute the following parameter: Data to send (12 words).

Word number

Meaning

1

contains a marker of value 16#CC17, If a PLC carries out the assignment…

If a CCX 17 carries out the assignment…

2

this word contains the list of keys to configure. Each command key is coded on a bit (0: non configured, 1: configured): l bit i (i = 1 to 8) command key no. 1.

this word contains 16#F000

the following two words indicate the operating mode of each of the command keys. Each key is coded by two bits l 00: Reset, l 01: functioning mode on edge, l 10: toggle functioning mode, l 11: no action. Bits 2j,2j+1 = command key i+1 (i = 0 to 11)

the values of the following ten words are indifferent and will be ignored by the CCX 17 console.

the following eight words contain, accordingly: a value –1 when the command keys are not affected, the index of the internal bits affected by the command keys Word i = command key i (i = 1 to 8)

l l

348

TLX DS 57 PL7 40E 09.2000

Appendices

Example of use

The example below shows the values corresponding to the word table %MW0:16 (data to send) of the ASSIGN_KEYS (ADR#0.0.4,%MW0:16,%MW100:4) function; Word number

TLX DS 57 PL7 40E 09.2000

Value

Comment

%MW0

16#CC17

Marker

%MW1

16#000F

Command keys 1 to 4 are configured, the others are not.

%MW2

16#FF09

%MW3

16#00FF

Key 1 in edge mode (01), key 2 in toggle mode (02), keys 3 and 4 inhibited (00), the others not programmed (11)

%MW4

10

Key 1 affected by bit %M10

%MW5

rc

Key 1 affected by bit %M11

%MW6 to %MW15

-1

Keys 3 to 8 not affected

349

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

The table below shows the significance of the different words which constitute the following parameter: Data to send (3 words maximum).

Word number

Meaning

1

contains a marker of value 16#CC17,

2

contains the command number: l 1: clear screen, l 2: clear a line, l 9: print the alarm message log, l 10: clear the alarm message log, l 11: print the alarm log l 13: clear the alarm log, l 29: clear the alarm (from 1 to 300) destined for CCX 17, l 30: clear the alarm (from 900 to 999) destined for the PLC.

3

indicates the command parameter. l clear line = line number, l cancel alarm = alarm number, l other commands: no object.

Example of use

350

The example below shows the values corresponding to the word table %MW0:2 (data to send) for the PANEL_CMD(ADR#0.0.4,%MW0:2,%MW100:4) function; Word number

Value

Comment

%MW0

16#CC17

Marker

%MW1

1

Clear screen

TLX DS 57 PL7 40E 09.2000

Glossary

A

AS-interface

Actuator Sensor interface

C

CCX17

Family of Schneider Automation Human-Machine Interface terminal

Channel group

Channels of the same type with common parameters. This notion concerns certain application-specific modules such as discrete modules.

CPU

Central Processing Unit: generic name used for Schneider Automation processors

D

Discrete

TLX DS 57 PL7 40E 09.2000

Discrete I/Os

351

Glossary

F

FIPIO

Field bus used to connect sensor or actuator type devices.

I

IP67

Family of Schneider Automation hardware products consisting of sealed I/O modules which connect to the FIPIO field bus, used to produce automated systems with distributed I/Os.

M

Momentum

I/O modules using several open standard communication networks.

P

PL7 Junior and Pro

Schneider Automation PLC programming software.

PV

Identifier indicating the product version.

T

TBX

I/O modules remoted on the FIPIO bus.

TSX/PMX/PCX57

Families of Schneider Automation hardware products.

352

TLX DS 57 PL7 40E 09.2000

B AC

Index

Symbols %CHxy.i, 41

A Access to the configuration editor AS-i Bus, 212 Accessing the configuration editor, 64 In-rack discrete, 84 Remote I/Os, 86 Accessing the debug editor in-rack discrete, 119 Adding a profile AS-I Bus, 222 Adding a slave AS-i Bus, 216 Addressing AS-i bus, 36, 243 built-in interfaces, 28 Discrete in-rack, 130 FIPIO Bus, 30, 33 Momentum, 30, 33 Remote I/Os, 131 TBX, 30, 33 Adjustment, 22 AS-i Bus, 235 Discrete reflex, 195 Adjustment objects AS-i bus, 252 Advanced operation AS-i bus, 261, 262

TLX DS 57 PL7 40E 09.2000

Application-specific function Discrete, 77 Application-specific instructions, 60 AS-i, 203 AS-i Bus, 206 AS-i slave AS-i bus, 210 ASSIGN_KEYS, 315 Automatic slave addressing AS-i bus, 224

B Built-in application-specific interfaces, 28

C Channel diagnostics Discrete, 121 Channel fault Discrete, 121 Command objects AS-i bus, 251 Communication Interface, 28 Configuration, 20 Configuration of reflex function blocks, 194 Configuration screen AS-i Bus, 214 Discrete, 82 Configuring slaves AS-i Bus, 214 Configuring the reflex function blocks, 191 353

Index

Confirming the configuration, 70, 71 Connecting AS-i bus, 228 CONTROL_LEDS, 312 Copy/paste, 87

D Data exchange off mode AS-i bus, 262 Debug, 23 AS-i bus, 228 Debug mode, 115 Debug screen Discrete, 117 Debugging Discrete, 116, 119 Debugging screen AS-i Bus, 229 Declaration of a module on the FIPIO bus, 68 Declaration of an I/O module, 67 Device connection AS-I Bus, 216 Diagnostics, 23 Bus AS-i, 231 Diagnostics mode AS-i Bus, 234 Bus AS-i, 231 Discrete, 75 Discrete reflex modules, 145 DISPLAY_GRP, 302 DISPLAY_MSG, 301

E Event Discrete reflex, 196 Exchange management, 135 Explicit exchanges, 41 AS-i bus, 249 Explicit objects, 137, 138, 139, 140, 142, 247 AS-i Bus, 248 AS-i bus, 253 Discrete reflex, 202 External errors AS-i Bus, 231 354

External supply fault, 107

F Fallback mode, 113 Fallback to 0 AS-i bus, 225 Family AS-i Bus, 211 Fault processing by program, 72 Faulty slave AS-i bus, 238 Filtering, 110 FIPIO, 68, 86 FIPIO connection, 68 Forcing, 122 AS-i Bus, 236 Function Adjustment, 22 Configuration, 20 Debug, 23 Functions, 108

G GET_MSG, 293 GET_VALUE, 309

I Implicit exchanges, 38 AS-i bus, 245 Discrete, 134 Implicit objects Discrete reflex, 199 Indexable objects Discrete, 132 Internal errors AS-i Bus, 231 IP67, 93, 102

L Language objects, 135, 137, 138, 139, 140,

TLX DS 57 PL7 40E 09.2000

Index

142, 246, 247 AS-i Bus, 248 Bus AS-i, 253 Discrete, 134 Discrete reflex, 199, 202 Latching, 111 Library, 60

M Maintain AS-i bus, 225 Maintain outputs Discrete, 126 Management of exchanges, 246 Masking, 124 Master/Slave AS-i bus, 208 Modifying parameters, 87 Module diagnostics Discrete, 120 Module fault Discrete, 120 Module number AS-i Bus, 211 Momentum, 68, 92 Multiple selection, 87

O Offline mode AS-i bus, 261 Operating mode AS-i bus, 256

112, 113, 114 In-rack discrete inputs, 90 In-rack discrete outputs, 95, 96 IP67 discrete inputs, 93 IP67 discrete outputs, 102 Momentum discrete inputs, 92 Momentum discrete outputs, 101 TBX discrete inputs, 91 TBX discrete outputs, 98, 99 Performance AS-i bus, 263 PL7 status bar, 66 PL7 Toolbar, 65 Presymbolization, 56, 57 Processing of faults by program, 73 Profile AS-i bus, 208 Programmable channels, 104 Protected mode AS-i bus, 259

R Reactivation Discrete, 125 Reactivation of outputs, 114 READ_PARAM, 47 READ_STS, 44 Reading adjustment parameters, 47 Reading status words, 44 Reflex function configuration editor, 192

P Parameter Discrete, 111 Parameters Discrete, 104, 105, 106, 107, 108, 110,

TLX DS 57 PL7 40E 09.2000

355

Index

Reflex functions 2 threshold counter, 168 2 value monostable, 161 2 value operation timer, 153 Burst, 174 Combinational, 149 Command-counting, 186 D flip-flops, 164 Detection of underspeed, 176 Direct, 148 Fault signaling, 188 Idle timer, 151 Intervalometer, 172 Monostable with time delay, 159 Operation timer, 150 Operation-idle timer, 152 Operation-idle timer with value selection, 155 Oscillator, 163 PWM, 175 Retriggerable monostable, 158 Simple electronic cam, 170 Speed monitoring, 178 T flip-flop, 166 Type 1 command-check, 181 Type 2 command-check, 183 RESET, 123 AS-i Bus, 237 RESTORE_PARAM, 51 Restoring adjustment parameters, 51 RUN/STOP, 112 RUN/STOP input, 112

S SAVE_PARAM, 49 Saving adjustment parameters, 49 Selecting the module AS-i Bus, 211 Selection of modules Discrete, 67 Remote I/Os, 68 SEND_ALARM, 298 SEND_MSG, 290 SET, 123 AS-i Bus, 237 356

Slave number AS-i bus, 218 Slaves AS-i Bus, 233 Slaves’ status AS-i Bus, 233 Software installation General, 18 Status objects AS-i bus, 245, 249 Structure of an AS-i slave AS-i bus, 210

T Task Discrete, 105 TBX, 68, 91, 98, 99, 104 Terminal Port, 28 TSX SAY 100 AS-i bus, 208 TSX SAY 100 module AS-i bus, 208

U Unforcing, 122 As-i Bus, 236 Unmasking, 124

W Wiring check, 106 Wiring test mode AS-i bus, 260 Write command, 123 Write to 0, 123 Write to 1, 123 WRITE_CMD, 46 WRITE_PARAM, 48 Writing adjustment parameters, 48 Writing command words, 46

TLX DS 57 PL7 40E 09.2000