Description of PL7 software Aasousa/sind/schneider/PL7... · 2007. 2. 12. · PL7 Micro software can only be used to program TSX 37 PLCs. PL7 Pro software offers, in addition to the

A

B

Description of PL7 software

Detailed description of instructions and functionsReferencemanual

___________________________________________________________________________

B/2

___________________________________________________________________________A/1

A

Description of PL7 Contentssoftware Part A

Section Page

___________________________________________________________________________

1 General information A1/1

1.1 Presentation of PL7 software A1/11.1-1 Presentation A1/11.1-2 Single task structure A1/31.1-3 Multitask structure A1/31.1-4 Structured and modular programming A1/41.1-5 Structuring as function modules A1/51.1-6 Symbolic programming A1/61.1-7 PL7 instructions A1/81.1-8 User function blocks A1/9

1.2 Addressable objects A1/101.2-1 Definition of the main Boolean objects A1/101.2-2 Addressing TSX 37 I/O module objects A1/111.2-3 Addressing TSX/PMX/PCX 57 I/O module objects A1/131.2-4 Addressing words A1/161.2-5 Function block objects A1/201.2-6 Structured objects A1/211.2-7 Grafcet objects A1/231.2-8 DFB objects A1/231.2-9 Symbolization A1/24

1.3 User memory A1/261.3-1 General A1/261.3-2 Saving / retrieving internal words %MWi A1/281.3-3 Bit memory A1/291.3-4 Word memory A1/311.3-5 TSX 37-10/21/22 PLCs A1/321.3-6 TSX/PCX/PMX 57-10/20/25 PLCs A1/331.3-7 TSX/PCX 57-30/35 PLCs A1/341.3-8 PMX57-35/45 and TSX 57-40/45 PLCs A1/35

___________________________________________________________________________

A/2

A


Section Page

________________________________________________________________

1.4 Operating modes A1/361.4-1 Processing on power outage and power return A1/361.4-2 Processing on a warm restart A1/371.4-3 Processing on a cold start A1/38

1.5 Single task software structure A1/391.5-1 Presentation of the master task A1/391.5-2 Cyclic execution A1/411.5-3 Periodic execution A1/421.5-4 Monitoring the scan time A1/44

1.6 Multitask software structure A1/451.6-1 Description A1/451.6-2 Master task A1/471.6-3 Fast task A1/481.6-4 Assigning I/O channels to the master and fast tasks A1/491.6-5 Event-triggered tasks A1/50

2 Ladder language A2/1

2.1 Presentation of Ladder language A2/12.1-1 Principle A2/12.1-2 Graphic elements A2/2

2.2 Structure of a rung A2/52.2-1 General A2/52.2-2 Labels A2/62.2-3 Comments A2/62.2-4 Rungs A2/72.2-5 Rungs with function and operation blocks A2/10

2.3 Rules for executing rungs A2/132.3-1 Principle for executing a rung A2/13

___________________________________________________________________________A/3

A


Section Page

___________________________________________________________________________

3 Instruction List language A3/1

3.1 Presentation of Instruction List language A3/13.1-1 Principle A3/13.1-2 Instructions A3/2

3.2 Program structure A3/43.2-1 General A3/43.2-2 Comments A3/43.2-3 Labels A3/43.2-4 Using parentheses A3/53.2-5 MPS, MRD and MPP instructions A3/73.2-6 Principles for programming predefined function blocks A3/8

3.3 Rules for executing Instruction List programs A3/9

4 Structured Text language A4/1

4.1 Presentation of Structured Text language A4/14.1-1 Principle A4/14.1-2 Instructions A4/2

4.2 Program structure A4/74.2-1 General A4/74.2-2 Comment A4/74.2-3 Label A4/84.2-4 Instructions A4/84.2-5 Control structures A4/9

4.3 Rules for executing a Structured Text program A4/15

___________________________________________________________________________

A/4

A


Section Page

________________________________________________________________

5 Grafcet language A5/1

5.1 Presentation of Grafcet language A5/15.1-1 Reminder of principles of Grafcet A5/15.1-2 Progressive analysis : macro-representations A5/2

5.2 Graphic symbols specific to Grafcet language A5/4

5.3 Objects specific to Grafcet A5/6

5.4 Grafcet language possibilities A5/7

5.5 Grafcet chart representation A5/9

5.6 Macro-steps A5/155.6-1 Principle A5/155.6-2 Characteristics A5/165.6-3 Initial steps A5/16

5.7 Actions associated with steps A5/17

5.8 Conditions associated with transitions A5/20

5.9 Organization of the Grafcet section A5/235.9-1 Description of the Grafcet section A5/235.9-2 Preprocessing A5/245.9-3 The use of system bits in preprocessing A5/255.9-4 Sequential processing A5/285.9-5 Post-processing A5/30

___________________________________________________________________________A/5

A


Section Page

___________________________________________________________________________

6 DFBs A6/1

6.1 Presentation of DFBs A6/16.1-1 General A6/16.1-2 Setting up a DFB A6/2

6.2 Designing a DFB type A6/36.2-1 Creating a DFB type A6/36.2-2 Description of parameters and variables A6/36.2-3 DFB type code A6/56.2-4 Confirming the DFB type A6/66.2-5 DFB type properties A6/66.2-6 Descriptive file A6/76.2-7 DFB type properties A6/76.2-8 Importing/exporting a DFB type A6/7

6.3 Creating a DFB type instance A6/86.3-1 Principles A6/8

6.4 Using DFBs A6/96.4-1 General programming rules A6/96.4-2 Programming in Ladder language A6/106.4-3 Programming in Structured Text language or

Instruction List language A6/116.4-4 Accessing variables A6/126.4-5 Saving and restoring public variables A6/126.4-6 Executing DFBs A6/12

6.5 Example A6/13

___________________________________________________________________________

A/6

A


Section Page

________________________________________________________________

7 Function modules A7/1

7.1 Presentation of function modules A7/17.1-1 Definition of a function module A7/17.1-2 Representation of a function module in PL7 PRO A7/27.1-3 The concept of a function submodule A7/37.1-4 The attributes of a function module A7/3

7.2 Setting up function modules A7/47.2-1 Creating a function module A7/47.2-2 Modifying the architecture of function modules A7/4

7.3 Programming a function module A7/67.3-1 Adding / creating a section, an event or a macro-step in

a function module A7/67.3-2 Deleting a section, a macro-step or an event in a module A7/87.3-3 Adding / creating an animation table in a function module A7/97.3-4 Entering / modifying the descriptive file A7/9

7.4 Executing the program A7/10

7.5 Debugging the application A7/10

7.6 Application documentation file A7/10

7.7 Importing and exporting the source file for a function module A7/117.7-1 Exporting A7/117.7-2 Importing A7/11

PL7 general information 1

___________________________________________________________________________1/1

A

1.1 Presentation of PL7 software

1.1-1 Presentation

PL7 Junior software is the programming software for TSX 37 and TSX/PMX/PCX 57PLCs operating under Windows. PL7 Micro software can only be used to programTSX 37 PLCs.PL7 Pro software offers, in addition to the functions provided by PL7 Junior software,the possibility of creating DFB (Derived Function Block) user function blocks, runtimescreens and function modules.PL7 Prodyn software is an operating tool (control, diagnostics, maintenance) forTSX 37 and TSX/PMX/PCX 57 PLCs. It cannot be used to create or modify anapplication.

PL7 software (1) offers :

• A graphic language, Ladder language (LD), for transcribing Ladder diagrams, whichis particularly suitable for combinational processing. It offers the basic graphicelements : contacts, coils and blocks. Numeric calculations can be written withinoperation blocks.

• A Boolean language, Instruction List language (IL), which is a "machine" language forwriting logical and numerical processing operations.

(1) PL7 is used in the rest of this document to refer to PL7 Junior, PL7 Micro, PL7 Proor PL7 Prodyn.

Section 11 General information

1/2___________________________________________________________________________

A

• A Structured Text language (ST) which is a "data processing" type language enablingthe structured writing of logical and numerical processing.

• A Grafcet language which is used to represent the operation of a sequential controlsystem in a graphic and structured way.

These languages use predefined function blocks (timers, counters, etc), which can besupplemented by application-specific functions (analog, communication, counting,etc) and specific functions (time management, character strings, etc).The language objects can be symbolized using the variables editor or online in theprogram editors.

PL7 software conforms to standard IEC 1131-3. The tables of conformity areprovided in the Appendix : part B section 6.


___________________________________________________________________________1/3

A

1.1-2 Single task structure

This is the default structure of the software. It comprises a single task, the master task.

Master taskThis task can either be a periodic, said to be cyclic (the default choice), or periodic.For cyclic operation, the tasks are linked one to the other, without pausing.For periodic operation, tasks are linked at a period fixed by the user.

1.1-3 Multitask structure

The multitask structure of TSX 37 and TSX 57 PLCs enables better use which giveshigh-performance realtime applications by associating a specific program with eachapplication. Each of these programs is controlled by a task.These tasks are independent and executed in "parallel" by the main processor whichmanages their priority as well as their execution.

The aim of this type of structure is to :• Optimize use of processing power.• Simplify design and debugging. Each task is written and debugged independently of

the others.• Structure the application. Each task has a unique function.• Optimize availability.

The multitask system offers a master task, a fast task and from 8 to 64 event-triggeredtasks depending on the processor.

Fast taskThe fast task (optional), which is periodic, is used to perform short processingoperations with a higher priority than in the master task. When it is programmed, it isautomatically launched by the system during start-up. It can also be stopped and thenrestarted by activating a system bit.

Event-triggered tasksUnlike the tasks described above, these tasks are not linked to a period. They aretriggered by calls originating from certain modules. These tasks have the highestpriority. The processing they perform is deliberately short so that they do not interferewith the execution of other tasks.

Fasttask

Priority

Mastertask

Event-triggered tasks

+-

1/4___________________________________________________________________________

A

1.1-4 Structured and modular programming

PL7 program tasks are made up of several parts (called sections) and subroutines.

Each of these sections can be programmed in the language which is most suitable forthe process to be executed.

This division into sections means that a structured program can be created and programmodules can be generated or incorporated without difficulty.

The subroutines can be called from any section of the task to which they belong, or fromother subroutines in the same task.

Chamber (LD)

MAST

Oven_1(Grafcet)

PRL (LD)

CHART

POST(LD)

Drying (LD)

Cleaning(ST)

FAST

Alarm_Chamber (LD)

Monitor_Sec(LD)

Alarm_Oven(ST)

Alarm_Cleaning(ST)

SR0

SR0

EVT0


___________________________________________________________________________1/5

A

1.1-5 Structuring as function modules

A function module is a group of program elements (sections, events, macro-steps,animation tables, etc) used to perform a control system function.A function module is defined by a certain number of attributes (name, comment,programming, associated animation tables, etc).

A function module contains a program directory (made up of one or more code modules)and an animation table directory.

A function module containsthe program and theanimation tables

A function module can itself be divided into lower level function modules which performone or more subfunctions of the main control system function.

PL7 PRO is the only product which can be used to set up function modules onTSX/PMX/PCX57 PLCs.

The Mixer_1 module contains a submodule Adjust_1

1/6___________________________________________________________________________

A

1.1-6 Symbolic programming

The user can enter or display objects :

• either by their address (for example : %Q2.5),

• or by a character string (32 characters max) known as a symbol (for exampleFc_door).

NoteThe objects associated with the DFB user function block are purely symbolic objects.

Example : symbolic display of objects in Ladder language.

Addresses and symbols can be displayed simultaneously in Ladder language.

The language objects can be symbolized using the variables editor or online in theprogram editors.

This symbols database, which is managed by the software VARIABLES editor, is globalto the PLC station.

NoteSome application-specific modules enable symbols to be allocated automatically to the objectsassociated with them.


___________________________________________________________________________1/7

A

Symbols and comments stored in the TSX Premium PLC

• FunctionSymbols and comments can be stored in a TSX Premium PLC (TSX/PMX/PCX 57202,57302, 57402, 57452 V3.3) fitted with the following type of memory card :• 128 Kword memory card : TSXMRP 2128P• 256 Kword memory card : TSXMRP 3256P

When an application is saved on the PC, an *.STX file is created.The application image in the form of the *.STX file includes, among other things,symbols and comments.

The "Symbols and comments stored in the TSX Premium PLC" function provides thePL7 user with the same ease of programming and operation with respect to symbolsand comments, whether an application image in STX form is available in the PLC ornot.

Notes1. In online mode, modifications to symbols and comments made in the Variables

Editor are not fed back to the cartridge as they are made. A prompt to update thedatabase in the PLC is made on a disconnection request if there is a discrepancybetween the local database and the database in the PLC.

2. Freeing space in the symbols and comments database does not increase the sizeof the program zone, because the symbols and comments are not stored in the sameplace as the program part of the application.

3. The various PL7 editors (data, program, debug tool) use the symbols and commentsdatabase available in the PC in online mode.

4. The Comparison function can be used to compare PC/PLC symbols.

1/8___________________________________________________________________________

A

1.1-7 PL7 instructions

All PL7 languages use the same instruction set.

Part B of this document describes all the instructions in detail. For simplicity's sake,these have been classified in 2 sets : basic instructions and advanced instructions.

Basic instructionsThey include basic Boolean instructions, predefined function blocks and arithmeticand logic instructions on integers.

Advanced instructionsThese include instructions which meet the needs of advanced programming.

They are of 2 types :

• PL7 language : these increase language processing performance through specificfunctions (manipulation of character strings, time management, etc),

• Applications : these offer functions which are specific to the application to beprocessed. For example, functions for the communication application :- PRINT to send a standard character string message to a terminal or printer.- SEND to send a message to an application.- PID : PID control function.

Function entry helpAn entry help screen gives access to all the language functions. This screen isaccessible at all times, including during programming.


___________________________________________________________________________1/9

A

1.1-8 User function blocks

PL7 Pro software can be used to create DFB user function blocks for Premium PLCs.These DFBs are created in Structured Text language, and can then be used in a sectionor a subroutine whatever language is used (they can also be used with PL7 Juniorsoftware).

Example of DFBs used in Ladder language.

The main components of a DFB are :

• name• input and output parameters• public and private variables• code in Structured Text language

A DFB can have a maximum of 15 inputsand/or I/O and 15 outputs and/or I/O.

Once it has been created, each DFB canbe used several times in an application.The designer programs the model DFB(known as the DFB type) and for each use,the user defines an instance name usingthe variables editor or using the entry helpscreen for the selected language.

DFB type name

Inputs Outputs

I/O

Public variablesPrivate variables

Code in Structured Text

1/10___________________________________________________________________________

A

1.2 Addressable objects

1.2-1 Definition of the main Boolean objects

I/O bits

These bits are the "logical images" of the electrical state of the I/O. They are stored inthe data memory and are updated on each scan of the task in which they are configured.

Internal bitsInternal bits %Mi are used to store intermediate states during execution of the program.

Note : Unused I/O bits cannot be used as internal bits.

System bitsSystem bits %S0 to %S127 monitor correct operation of the PLC as well as progressionof the application program. The role and use of these bits are described in detail insection 3.1 of part B.

Function block bitsFunction block bits correspond to the outputs of blocks. These outputs can be eitherwired directly, or used as objects.

Word extract bitsUsing PL7 software it is possible to extract one of the 16 bits from a word object.

Grafcet step and macro-step status bitsGrafcet step status bits for steps %Xi, macro-steps %XMj and steps of macro-steps%Xj.i (Xj.IN and Xj.OUT for input and output steps of macro-steps) are used to identifythe status of Grafcet step i, macro-step j or step i of macro-step j.

List of bit operandsThe following table gives a list of all types of Boolean operands.

Type Address Access in See(or value) write mode (1) Section Part

Immediate value 0 or 1 (False or True) – 1.2-4 A

Input bits %Ix.i or %IXx.i no 1.2-2 AOutput bits %Qx.i or %QXx.i yes 1.2-3

Internal bits %Mi or %MXi yes –

System bits %Si according to i 3.1 B

Function block eg : %TMi.Q no 1.2-5 Abits %DRi.F.....

Grafcet bits %Xi, %XMj, %Xj.i... yes 5.2 A

Word extract bits eg : %MW10:X5 acc. to word type 1.2-4 A

(1) Written by program or in adjust mode via the terminal


___________________________________________________________________________1/11

A

ExtensionBaseBase Extension

8

7 9

06

5

10

TSX 37-10 TSX 37-21/22

6 8

5 7

2

1

4

3

2

1

4

3

% I or Q X, W or D x . i

Symbol Type of objectI = inputQ =output

FormatX = Bool eanW = wordD = double word

Positionx= Position number in the rack

Channel No.i = 0 to 127or MOD

1.2-2 Addressing TSX 37 I/O module objects

Addressing of the main word and bit objects in I/O modules is defined by the followingcharacters :

• Type of objectI and Q : the physical inputs and outputs of modules exchange this informationimplicitly on each scan of the task to which they are attached.Note : Other types of data (status, command words, etc) can also be exchanged ifrequested by the application.

• Format (Size)For objects in Boolean format, the X can be omitted. Other types of format such asbyte, word and double word are defined in section 1.2-4.

• Channel position and numberThe base modularity of the TSX 37 is 1/2 format. The positions for each type of TSX37 PLC (base and extension) are shown in the diagrams below.

Standard format modules are addressed as two superposed 1/2 format modules (seetable below).

For example, a 64 I/O module is viewed as two 1/2 format modules :a 32 input 1/2 module located in position 5, and a 32 output 1/2 module located inslot 6.

1/12___________________________________________________________________________

A

Module 1/2 format Standard format4 Q 8 Q 12 I 28 I/O 32 I 32 Q 64 I/O

Channel number : i 0 to 3 0 to 7 0 to 11 0 to 15 0 to 15 0 to 15 0 to 31

0 to 11 0 to 15 0 to 15 0 to 31

Position and ch. no. x.0 x.0 x.0 x.0 x.0 x.0 x.0(x = position) to to to to to to to

x.3 x.7 x.11 x.15 x.15 x.15 x.31

(x+1).0 (x+1).0 (x+1).0 (x+1).0to to to to(x+1).11 (x+1).15 (x+1).15 (x+1).31

Note :The channel number can be replaced by "MOD" to access data which is general to the module.

• Rank : an optional suffix can be added after the channel number. This is used todistinguish different objects of the same type associated with the same channel.ERR : indicates a module or channel fault.Examples :%I4.MOD.ERR : information on fault in module 4%I4.3.ERR : information on fault in channel 3 of module 4.

Note :For an addressing operation across the network or for remote I/O addressing, the full access pathto the station is added to the position number in the rack.

Examples

%I1.5 input channel no. 5 of the modulelocated at position no. 1.

%I3.8 input channel no. 8 of the normalformat module located in positionno. 3 and 4.

%Q4.5 output channel no. 5 of thestandard format module locatedin position no. 3 and 4.

%I5.MOD.ERR Information on modulefault, of the module located inposition no. 5.

%IW8.0 input channel no. 0 of the 1/2format module located in positionno. 8.

6 8

5 7

Base Extension

%IW8.0TSX 37-10

%Q4.5

%I5.MOD.ERR%I3.8%I1.5

2

1

4

3


___________________________________________________________________________1/13

A

1.2-3 Addressing TSX/PMX/PCX 57 I/O module objects

Addressing of the main word and bit objects in I/O modules is defined as follows :

• Type of objectI and Q : the physical inputs and outputs of modules exchange this informationimplicitly on each scan of the task to which they are attached.Note : Other types of data (status, command words, etc) can also be exchanged ifrequested by the application.

• Format (Size)For objects in Boolean format, the X can be omitted. Other types of format such asbyte, word and double word are defined in section 1.2-4.

• Channel addressingChannel addressing depends on the rack address, the physical location of themodule in the rack and the channel number.

Notes :• For the list of objects associated with a module, refer to the manual for the relevant application-

specific function.• Remote I/O addressing is described in the application-specific functions manual, in the part

entitled "Common features of application-specific functions".

PS 00 01 02 03 04 05 06 07 08 09 10

PS 00 01 02 03 04 05 06 07 08 09 10

00

01

% I or Q X, W or D y . i

Symbol Type of objectI = inputQ =output

FormatX = Bool eanW = wordD = double word

Modulepositiony= 00 to 10

Channel Noi =0 to 127or MOD

x

Rackaddressx= 0 to 7

1/14___________________________________________________________________________

A

Rack addresses (x) and module positions (y)

TSX racks RKY 6 RKY 8 RKY 12 RKY 4EX RKY 6EX RKY 8EX RKY 12EX

Rack address : x 0 0 0 0 to 7 0 to 7 0 to 7 0 to 7

Module position : y 00 to 04 00 to 06 00 to 10 00 to 02 00 to 04 00 to 06 00 to 10

Note :The address of the rack supporting the processor is always 0.

Channel number (i)

Modules TSX DEY ..../DSY .... 64 I/O 32 I/O 16 I/O 8 I/O

Channel number : i 0 to 63 0 to 31 0 to 15 0 to 7

Note :The channel number can be replaced by "MOD" to access general module information.

• Rank : an optional suffix can be added after the channel number. This is used todistinguish between different objects of the same type which are associated with asingle channel.

ERR : indicates a module or a channel fault.

Examples :- %I104.MOD.ERR : information on fault in the module in position 4 in rack at

address 1.- %I104.3.ERR : information on fault in channel 3 of the module in position 4 in rack

at address 1.

Note :For an addressing operation across the network or for remote I/O addressing, the full access pathto the station is added to the channel address.

Examples :

• %I102.5 : input channel 5 of the module located in position 2 in rack ataddress 1.

• %Q307.2 : output channel 2 of the module located in position 7 in rack ataddress 3.

• %I102.MOD.ERR : information on module fault, of the module located in position2 in rack at address 1.


___________________________________________________________________________1/15

A

Use of extension racks

• FunctionsExtension racks are used to configure a larger number of modules by using a largernumber of racks. This function is only available with processors version 3.3 or later.These extension racks have the same functions for configuring their modules or theirpower supplies as other racks.They are added after the base rack if the base rack is extendable and has 8 slots orless.They are identified by the letters EX in the reference.The first address for the first configurable module (excluding the power supply) isalways 8.

• Number of slots availableExtension racks must not have more than 8 slots.

Base rack Extension rack Total number (type E or EX) (type EX) of slots

4 4 84 6 104 8 126 4 106 6 126 8 148 4 128 6 148 8 1612 0 12

Example : base rack with 6 slots and extension rack with 6 slots6-channel DEY 16A2 module%I18.6 where rack no. = 1, position = 8, channel = 6

1/16___________________________________________________________________________

A

0 1 1 1

15 14 13 12

0 1 1 1

11 10 9 8

0 0 1 1

7 6 5 4

0 1 0 0

3 2 1 0

Least significantMost significant

Bit rank

16-bit format

1.2-4 Addressing words

Addressing I/O module words is defined in section 1.2-2 or 1.2-3. Other words used inPL7 language (except network words and function block words) are addressed in thefollowing way :

% B, W, D or F

Symbol FormatB = byteW = wordD = double wordF = floating point

Number

M, K or SS

Type of objectM = internalK = constantS = system

i

• Type of object

M internal words which store values during execution of the program. They are storedin the data zone within a single memory zone.

K constant words which store constant values or alphanumeric messages. Theircontent can only be written or modified by the terminal. They are stored in the sameplace as the program. They can therefore use the FLASH EPROM memory as theirsupport.

S system words. These words perform several functions :- some provide information on the status of the system by reading %SWi words

(system and application operating time, etc).- others are used to perform operations on the application (operating mode, etc).

System words are described in section 3, part B.

• Format

Word objects can be addressed by PL7 software using four different formats :

B byte : this format is used exclusively for operations on character strings.W single length : these 16-bit words can contain an algebraic value between -32 768

and 32 767.


___________________________________________________________________________1/17

A

0 1 0 1

15 14 13 12

0 0 1 1

11 10 9 8

1 1 1 1

7 6 5 4

0 1 1 1

3 2 1 0

0 0 1 1 0 1 1 0 0 1 0 1 0 0 1 0

D double length : these 32-bit words can contain an algebraic value between- 2 147 483 648 and 2 147 483 647. These words are stored in the memory on twoconsecutive single length words.

F floating point : the floating point format used is that of IEEE Std 754-1985 (equivalentto IEC 559). Words are 32 bits long, which corresponds to single length floating pointnumbers.Example of floating point values :1285.2812.8528E2

Overlapping between objects :Bytes, single, double length and floatingpoint words are stored within the data areain the same memory zone.Thus, there is overlapping between :• Double length word %MDi and single

length words %MWi and %MWi+1 (word%MWi containing the least significantbits and word %MWi+1 containing themost significant bits of word %MDi).

• Single length word %MWi and bytes%MBj and %MBj +1 (where j=2.i).

• Between the floating point %MFk andsingle length words %MWk and%MWk+1.

Examples :%MD0 corresponds to %MW0 and %MW1.%MW3 corresponds to %MB7 and %MB6.%KD543 corresponds to %KW543 and%KW544.%MF10 corresponds to %MW10 and%MW11.

32-bit format

Least significant

Rank n

Rank n+1

Most significant

%MB1 %MB0

%MB3 %MB2

%MB5

%MB7

%MB4

%MB6

%MW0

%MW1

%MW2

%MW3

%MD0

%MD2

%MD1

%MD3

%MWi

%MWi+1%MDi

%MWk

%MWk+1%MFk

1/18___________________________________________________________________________

A

Type Syntax

WORD :X j

Immediate values

These are algebraic values whose format is similar to that of single and double lengthword (16 or 32 bits), which allow assignment of values to these words. They are storedin the program memory and can take the following syntax :

Lower Upperlimit limit

Boolean 0 or 1 (FALSE or TRUE)Base 10 integer single length 1506 -32768 +32767

double length 578963 -2 147 483 648 2 147 483 647Base 2 integer single length 2#1000111011111011011 2#10...0 2#01...1(binary) double length 2#1000111011111011011 2#10...0 2#01...1

1111111011111011111Base 10 integer single length 16#AB20 16#0000 16#FFFF(hexadecimal) double length 16#5AC10 16#000000000 16#FFFFFFFFFloating point -1.32E12 -3.402824E+38 (1) -1.175494E-38 (1)

1.175494E-38 (1) 3.402824E+38 (1)Character string 'aAbBcC'

(1) excluding limit values

Addressing words on the network

Addressing words on the network is described in the Communication manual.

However, networks use specific objects : common words. These are single length wordobjects (16 bits) common to all the stations connected to the communication network.

Addressing : %NW{i.j}kwhere : i = network no. 0 to 127, j = station no. 0 to 31 and k = word no. 0 to 3

Word extract bits

PL7 software can be used to extract one of the 16 bits from single length words. The rankof the bit extracted is then added to the word address, following the syntax below :

Examples : %MW10:X4 = bit no. 4 of internal word %MW10%QW5.1:X10 = bit no. 10 of output word %QW5.1

Note : Word bits can also be extracted on indexed words.

Positionj=0 to 15Rank of bitin the word


___________________________________________________________________________1/19

A

Summary list of main word objects and associated bits

The notations used are R for read, and W for write.

Associated Type Addressing Limits Possibilitieswords and bits

Internal words single length %MWi (1) R/Wdouble length %MDi (1) R/Wfloating point %MFi (1) R/Wbyte (2) %MBi (1) R/W

Constant words single length %KWi (1) R/W (3)double length %KDi (1) R/W (3)floating point %KFi (1) R/W (3)byte (2) %KBi (1) R/W (3)

I/O module Input single length %IWxy.i 0≤i≤127 Rwords Input double length %IDxy.i 0≤i≤126 R

Output single length %QWxy.i 0≤i≤127 R/WOutput double length %QDxy.i 0≤i≤126 R/W

Grafcet words single length %Xi.T 0≤i≤249 Rdouble length %Xj.i.T 0≤j≤63 0≤i≤249 R

Common words on network %NW{i.j}k 0≤i≤127 0≤j≤31 0≤k≤3 R/W

System words single length %SWi 0≤i≤255 R/W (4)double length %SDi 0≤i≤254 R/W (4)

Word extract bit j of internal word %MWi:Xj 0≤j≤15 R/Wbits bit j of constant word %KWi:Xj 0≤j≤15 R/W (3)

bit j of input word %IWi:Xj 0≤j≤15 Rbit j of output word %QWi:Xj 0≤j≤15 R/Wbit j of system word %SWi:Xj 0≤j≤15 R/W (4)bit j of common word %NW{j}k:Xm 0≤m≤15 R/Wnetwork 0

(1) The maximum limit depends on the memory size available and the number of words declaredduring software configuration.

(2) This object only exists in the start address of a character string %MBi:L or %KBi:L (see section2.8-1, part B).

(3) Write by terminal only.(4) Write according to i.

1/20___________________________________________________________________________

A

R

S

CU

CD F

D

E

%Ci

C.P : 9999

MODIF : Y

Up/down counter block

1.2-5 Function block objects

Function blocks use specific bit and word objects.

• Bit objects :These correspond to the outputs ofblocks. These bits are accessible usingBoolean test instructions.

• Word objects :These correspond :- to the configuration parameters of the

block. The program may (eg : presetparameter) or may not (eg : time base)be used to access these parameters,

- to the current values (eg : %Ci.V currentcounter value).

List of function block bit and word objects accessible by program

Predefined Associated words and bits Address Access in See function blocks write mode Part B Timer Word Current value %TMi.V no sn1.3-2 %TMi (i=0 to 63) Preset value %TMi.P yes (1) Bit Timer output %TMi.Q no

Up/down Word Current value %Ci.V no sn1.3-3 counter Preset value %Ci.P yes %Ci (i=0 to 31) Bit Underflow output (empty) %Ci.E no

Preset reached output %Ci.D noOverflow output (full) %Ci.F no

Monostable Word Current value %MNi.V no sn2.2-1 %MNi (i=0 to 7) Preset value %MNi.P yes

Bit Current monostable output %MNi.R no

Register Word Register input %Ri.I yes sn2.2-2 %Ri (i= 0 to 3) Register output %Ri.O yes

Bit Register full output %Ri.F noRegister empty output %Ri.E no

Drum Word Current step number %DRi.S yes sn2.2-3 controller Status of step j %DRi.Wj no %DRi (i=0 to 7) Active time of the step %DRi.V no

Bit Last current step defined %DRi.F no

Series 7 Word Current value %Ti.V no sn2.2-4 timer Preset value %Ti.P yes %T (i=0 to 63) (1) Bit Timer running output %Ti.R no

Timer done output %Ti.D no

(1) The total number of timers %TMi and %Ti is limited to 64 for a TSX 37, 255 for a TSX 57.(2) The maximum number is given for a TSX 37, for a TSX 57 i = 0 to 254 for all function blocks.


___________________________________________________________________________1/21

A

16 bits%KW10

%KW14

8 bits%MB10

%MB14

1.2-6 Structured objects

Bit tables

Bit tables are sequences of adjacent bit objects of the same type and of a definedlength, L.

Example of bit tables : %M10:6 nc by

Type Address Maximum size Access in write mode

Discrete input bits %Ix.i:L 1 < L < m (1) No

Discrete output bits %Qx.i:L 1 < L

1/22___________________________________________________________________________

A

Indexed objects

• Direct addressing

Addressing of objects is said to be direct when the address of these objects is fixed anddefined when the program is written.

Example : %MW26 (internal word at address 26)

• Indexed addressing

In indexed addressing, an index is added to the direct address of the object : the contentof the index is added to the address of the object. The index is defined by an internalword %MWi, a constant word %KWi or an immediate value. The number of "indexwords" is unlimited.

Example : %MW108[%MW2] : direct address word 108 + content of word %MW2.If the content of word %MW2 is the value 12, writing %MW108[%MW2]is therefore equivalent to writing %MW120.

Type Format Address Maximum Access insize write mode

Input bit Boolean %Ii[index] 0


___________________________________________________________________________1/23

A

• Index overrun, system bit %S20

Index overrun occurs as soon as the address of an indexed object exceeds the limitsof the zone including this same type of object, that is, when :• object address + index content is lower than the value zero.• object address + index content is higher than the maximum limit configured (see table

on the previous page).

In the event of index overrun, the system sets system bit %S20 to 1 and the object isassigned an index value of 0.

Monitoring of overrun is the responsibility of the user : bit %S20 must be read by the userprogram for any processing. Resetting it is the responsibility of the user.

%S20 (initial state = 0) :• on index overrun : set to 1 by the system,• overrun acknowledgment : set to 0 by the user after modification of the index.

1.2-7 Grafcet objects

Bit objects

The user has the following bit objects :• %Xi associated with the steps which enable him to identify the status of step i of the

main chart.• %XMj associated with the macro-steps which enable him to identify the status of

Grafcet macro-step j.• %Xj.i associated with step i of macro-step j which enable him to identify the status of

Grafcet step i of macro-step j.• %Xj.IN or %Xj.OUT associated with the input or output step of the macro-step.These bits are set to 1 when the step or macro-step is active, and 0 when it is inactive.

Word objects

One word is associated with each step : %Xi.T, %Xj.i.T, %Xj.IN.T or %Xj.OUT.T. Itindicates the activity time of Grafcet step i. It is incremented every 100ms and takes avalue between 0 and 9999.

1.2-8 DFB objects

The DFB output parameters and public variables can be accessed by the program.These objects are Boolean, numerical, or table objects (see section 6).These objects are purely symbolic and are defined by the following syntax :DFB_name.Parameter_name, where DFB_name is the name given to the DFB used(32 characters maximum) and Parameter_name is the name given to the outputparameter or the public variable (8 characters maximum).

1/24___________________________________________________________________________

A

1.2-9 Symbolization

Symbols

A symbol is a string of up to 32 alphanumeric characters, of which the first character isalphabetical. A symbol starts with a capital letter, followed by letters in lower case (forexample : the symbol Burner_1). When it is entered, the symbol can be written in upperor lower case (for example : BURNER_1). The software automatically puts the symbolinto its correct format.

The following characters can therefore be used :• upper case alphabetical :

"A to Z" and accented letters "ÀÁÂÃÄÅÆÇÈÉÊËÌÍÎÏDÑÒÓÓÕÖØÙÚÛÜYp"or lower case alphabetical :" a to z", and accented letters : àáâãäåæçèéêëìíîïðñòóôõöØùúûüypßÿ

• numerical : digits 0 to 9 (they cannot be placed at the start of the symbol).• the character "_" (this cannot be placed either at the beginning or end of the symbol).

A number of words are reserved by the language and cannot be used as symbols. Seefull list in section 5 part B.

The symbols are defined and associated with language objects by the variables editor(see section 5, part D). A comment of 508 characters can be associated with eachsymbol. The symbols and their comments are saved to the terminal disk and not in thePLC.

Objects which can be symbolized

All PL7 objects can be symbolized except table type structured objects and indexedobjects, but if the base object or the index is symbolized, the symbol is used in thestructured object.

Examples :• if word %MW0 has "Temperature" as its symbol, the word table %MW0:12 is

symbolized by "Temperature:12"• if word %MW10 has "Oven_1" as its symbol, the indexed word %MW0[%MW10] is

symbolized by "Temperature[oven_1]".

Word extract bit objects and function block bits or words can be symbolized, but if theyare not symbolized, they can take on the symbol of the base object.Examples :• if word %MW0 has " Pump_status" as its symbol and if the word extract bit %MW0:X1

is not symbolized, it takes on the symbol of the word. %MW0:X1 has as its symbol,"Pump_status:X1".

• if function block %TM0 has "Oven1_timer" as its symbol and if output %TM0.D is notsymbolized, it takes on a symbol of the block. %TM0.D has as its symbol,"Oven_timer.D".


___________________________________________________________________________1/25

A

Purely symbolic objects

DFB parameters only be accessed as symbols. These objects are defined by thefollowing syntax :

DFB_name.Parameter_name.

where DFB_name is the name given to the DFB used (32 characters maximum) andParameter_name is the name given to the output parameter or the public variable (8characters maximum).

Presymbolized objectsApplication-specific modules enable symbols to be allocated automatically to theobjects associated with them. The user gives the generic symbol for channel %CHxy.iof the module, and all the symbols for the objects associated with this channel can thenbe generated automatically on request.

These objects are symbolized using the following syntax :

User_prefix_Manufacturer_suffixwhereUser_prefix is the generic symbol given by the user to channel %CHxy.i (12 charactersmaximum),Manufacturer_suffix is the part of the symbol which corresponds to the channel bit orword given by the system (20 characters maximum).

In addition to the symbol, a manufacturer comment is generated automatically whichgives a brief description of the role of the object.

Example : Auxil_motor2_param where "Auxil_motor2" is the user prefix and "_param"is the predefined manufacturer suffix.

1/26___________________________________________________________________________

A

1.3 User memory

1.3-1 General

The memory space of TSX 37 PLCs , which is accessible to the user, is divided into twodistinct units :

• Bit memory :RAM integrated in the processor module containing the image of 1280 bit objects.

• Word memory :16-bit words (program, data and constants) supported by a RAM memory in theprocessor module. This memory can be extended by a 32 or 64 K word RAM orFLASH EPROM user memory card (on TSX 37-21/22).A 16 K word FLASH EPROM memory integrated in the processor module can be usedto back up the application program (15 Kwords) and 1000 internal words (1 Kword)(see paragraph 1.3-2).

A 32 K word FLASH EPROM backup card can also be used to update an applicationin the internal RAM of the processor. This card contains the program part and theconstants but not the data.

The word memory can be organized in 2 different ways depending on whether or nota memory card (PCMCIA) is used :

Data : realtime application data and system data.Program : descriptors and executable code of tasks.Constants : constant words, initial values and I/O configuration.

Note

RAM memories can be backed up by Cadmium-nickel batteries, supported by theprocessor module for the bit and internal RAM memory.

(1) The application is transferred automatically from the FLASH EPROM memory to the RAMmemory if the application in the RAM is lost (backup fault or absence of battery). A manualtransfer can also be requested, via a programming terminal.

TSX 37-05/08/10 orTSX 37-21/22 (no PCMCIA card)

InternalRAM

InternalFlashEPROM (1)

Data

Program

Constants

InternalRAM

RAM orexternalFlashEPROMmemorycard

TSX 37-21/22 (with PCMCIA card)

Unusablezone

%MWbackup

InternalFlashEPROM

Data

Program

Constants

Programand constants

backup

%MWbackup


___________________________________________________________________________1/27

A

The memory space of TSX/PMX/PCX 57 PLCs only has one single unit. The bit memory,which is separate on the TSX 37, is integrated into the word memory (in the data zone).It is limited to 4096 bits.

• Word memory :16-bit words (program, data and constants) supported by a RAM memory in theprocessor module. This memory can be extended by a 32, 64, 128 or 256 K word RAMor FLASH EPROM user memory card (1).A 32 K word FLASH EPROM backup card can also be used for updating an applicationin the internal RAM of the processor. This card contains the program part and theconstants but not the data.

The memory can be organized in 2 different ways depending on whether or not amemory card (PCMCIA) is present and how it is used :

Data : realtime application data and system data (the system reserves a RAMmemory zone of 5 Kwords minimum).

Program : descriptors and executable code of tasks.Constants : constant words, initial values and I/O configuration.Symbols : TSX MRP 2128P and TSX MRP 3256 P cards contain a zone of

128 Kwords and 256 Kwords for storing application symbols.Archive : TSX MRP 232P/264P/2128P/3256 P cards contain an archive zonezone for data which can be accessed by read/write instructions (see section

2.13, part B).There is no possibility either of data overflow on the memory card or of having a programon the internal RAM and on the cartridge at the same time.

NoteRAM memories can be backed up by nickel-cadmium batteries.

TSX/PMX/PCX 57(no memory card)

TSX/PMX/PCX 57(with memory card)

InternalRAM

Data Data

Program

Program

Constants

Constants

InternalRAM

RAM orFLASHEPROMmemorycard

(1)256 Kword memory cards are paged cards. One page of 128 Kwords receives the executablecode, the other page of 128 Kwords receives graphic information.For further information, see section 8 part B.

1/28___________________________________________________________________________

A

1.3-2 Saving / retrieving internal words %MWi

Saving internal words %MWiIn order to save adjustment data in the event of a power outage, when the processorbattery is faulty or missing, TSX 37 PLCs can copy 1000 internal words (%MW)maximum to the internal Flash EPROM memory. This backup zone can be used at alltimes, even if the PLC is fitted with a PCMCIA memory card (TSX 37-21/22).To save internal words to the Flash EPROM, the application must be stopped . It istriggered according to the choice made during configuration :

• by setting the discrete input %I1.9 to 1,• from an adjustment panel, by setting bit 0 of %SW96 to 1.

The value of system word %SW97 defines the number of %MWi to be saved (1000maximum).

At the end of the backup, the display block displays OK or NOK depending on the resultof the operation.

The internal words %MWi are always saved when the application program issaved .If system word %SW97 is initialized to 0, only the application program contained in theinternal RAM is transferred to the Flash EPROM (equivalent to a Backup program).Warning : any saved %MWi are still erased.

Retrieving internal words %MWiSaved %MWi are transferred from the internal Flash EPROM memory to the RAMmemory on a cold start caused by :• loss of the internal RAM contents. In this case, if the application program backup is

valid, this is also transferred to the internal RAM (TSX 37-10 or TSX 37-20 withoutPCMCIA application cartridge),

• pressing the RESET button, on the front panel of the PLC,• setting bit %S0 to 1, in adjust mode,• clicking on the "Cold start" button in the PL7 processor debug screen,• transferring a program to the PLC (via terminal port, FIPWAY, etc),• plugging in a PCMCIA application cartridge.

For the saved %MW to be retrieved to the internal RAM, the "Reset %MWi on cold start"box must not be checked in the processor configuration screen.For further information, refer to part A of the TSX Micro installation manual.


___________________________________________________________________________1/29

A

1.3-3 Bit memory

Composition

This memory contains 1280 bit objects, for all types of TSX 37 PLC. For theTSX/PMX/PCX 57, this bit memory does not exist and its contents are found in the wordmemory in the application data zone.

TSX TSX TSX/PMX TSX/PMX TSX/PMX 37-05/08/10 37-21/22 PCX 57-1• 57-2• PCX 57-3•

System bits %SI 128 128 128 128 128

I/O bits %I/Qx (1) (1) (1) (1) (1)

Internal bits %Mi 256 256 3962 (2) 8056 (2) 12152 (2)

Step bits %Xi (3) 96 128 1024 1024 1024(1)Depends on the declared hardware configuration (I/O module, devices on the AS-i bus and

on the FIPIO bus)(2) The number of internal bits can be set in the configuration. The default value (256 to 2048)

varies depending on the processor being used and on the presence of a memory cartridge. Therest of the memory is available for application-specific functions.

(3) Total number of step bits and macro-step bits for TSX/PMX/PCX 57 PLCs.

StructureEach bit object contained in the bit memory is stored using 3 bits assigned in thefollowing way :

When the bit memory is updated, the system performs the following :• the transfer of the image of the current state to the previous state,• the updating of the current state via the program, the system or the terminal (when

a bit is forced).

Rising or falling edgeThis structure of the bit memory is used to test for a rising or falling edge on :• I/O bits,• internal bits.

Recommendations for the use of rising or falling edgesThe rising or falling edge contact instructions only operate correctly in the followingconditions :

• In all cases, for a single object :- input bit : process the edge contact in the task to which the input module has been assigned,- output or internal bit : process reading and writing of it within the same task .

F P C

Current state (only bit accessible

by the application program)

Previous state

Forcing state

1/30___________________________________________________________________________

A

• Write the coil of an object once only when an edge contact of this object is used ina program.

• Do not perform a SET or RESET on an object where the edge is tested, because evenif the result of the equation conditioning the SET/RESET equals 0, the SET/RESETaction is not performed, but the object log is updated (loss of the edge).

• Do not test the edge of an I/O used in a event-triggered task, in a master or fast task.• For internal bits : the detection of an edge is separate from the task scan. An edge on

internal bit %Mi is detected when it changes state between 2 read operations. Thisfront remains detected as long as this internal bit has not been scanned in theaction zone.

Thus, in the example opposite, if bit %M0is forced to 1 in an animation table, theedge is permanently on.

In order that the edge is only detected once, an intermediate internal bit must be used.

In this case the %M1 log is updated,therefore the edge only occurs once.

Forcing states

When there is a forcing request via the terminal :

• forcing state F is set to 1• current state C is set to :

- 1 if forcing to 1 is requested- 0 if forcing to 0 is requested.

These states remain unchanged until :

• forcing is deactivated and the bit in question updated,• inverse forcing is requested, in which case only the current state is modified.

INC%MW0P%M0

INC%MW0P%M1

%M1%M0


___________________________________________________________________________1/31

A

1.3-4 Word memory

This 16-bit word memory is structured into 3 logical areas :

• Data

• Program

• Constants

of which the size is defined by configuration.

Application data memory

The data memory contains the following zones :

• System words : fixed number

• Function blocks : correspond to the words and I/O of these blocks (current,adjustment values, etc).The number of each type of function block is fixed during configuration.

• Internal words : size defined by the number declared during configuration.

• I/O : correspond to the words associated with each module. Their number dependson the modules configured.

• Network common words : 4 common words per PLC station (only available ifcommunication module present and configured for exchange of common words).

In the case of the TSX/PMX/PCX 57, the data memory also includes the bit data detailedin the preceding paragraph.

Application program memory

This zone contains the executable program code, graphic data (Ladder languagerungs) and program comments.

Application constant memory

This zone contains the parameters of the function blocks and I/O modules definedduring configuration, and constant words %KW.

Note :The symbols and comments associated with objects are not recorded in the PLC memory butstored in the local application (hard disk on the terminal).

Application program

Application constants

Application data

1/32___________________________________________________________________________

A

1.3-5 TSX 37-05/08/10/21/22 PLCs

Size of the bit memory

Processor 37 05/08/10 37 21/22

Size available on processor 1280 1280

Type system bits %Si 128 128

of objects I/O bits %I/Qx.i (1) (1)

internal bits %Mi 256 256

step bits %Xi 96 128

(1) Depends on the declared hardware configuration (I/O module, devices on the AS-i bus)

Size of the word memory

Processor 3705/08 3710 3721 37 22Cartridge - - 32K 64K - 32K 64K

Total size 9K 14K 20K 52K 84K 20K 52K 84K

Data(%MWi) 0.5K(1) 0.5K(1) 0.5K(1) 17.5K 17.5K 0.5K(1) 17.5K 17.5K

Program

100% Boolean

• LD language 1.6 Ki 3.8 Ki 6.6 Ki 13.7 Ki 28.5 Ki 6.3 Ki 13.6 Ki 28.4 Ki

• IL language 2 Ki 4.9 Ki 8.4 Ki 17.5 Ki 36.3 Ki 8.1 Ki 17.3 Ki 36.1 Ki

• ST language 1.3 Ki 3.3 Ki 5.6 Ki 11.7 Ki 24.2 Ki 5.4 Ki 11.5 Ki 24.1 Ki

Program

90% Boolean


• IL language 1.4 Ki 3.8 Ki 6.6 Ki 14.3 Ki 30.0 Ki 6.3 Ki 14.2 Ki 29.8 Ki


Program

65% Boolean


• IL language 1.0 Ki 2.5 Ki 4.6 Ki 10.3 Ki 21.3 Ki 4.4 Ki 10.1 Ki 21.2 Ki


Constants (1) 128 words 128 words128 words 256 words 512 words 128 words 256 words 512 words

K = Kwords Ki = Kinstructions(1) Default size can be extended. However, this will adversely affect the size of the application program.

Note : the PLC/Memory Usage command in PL7 software provides the memory mapping of theapplication in the PLC memory.


___________________________________________________________________________1/33

A

1.3-6 TSX/PCX/PMX 57-10/20/25 PLCs

These tables refer to TSX 57-10, PCX 57-10, PMX 57-10, TSX 57 -20, PMX 57-20 andTSX 57-25 PLC5.


Processor 57 10 57 20/25

Type system bits %Si 128 128

of objects I/O bits %I/Qx.i (1) (1)

internal bits %Mi 3962 8056

step bits %Xi 1024 1024

(1) Depends on the declared hardware configuration (I/O module, devices on the AS-i bus and onthe FIPIO bus)


Processor TSX-PCX57 10 / PMX 57 10 TSX-PMX 5720 / TSX 57 25Cartridge - 32K 64K - 32K 64K 128K

Internal memory 32K/48K 32K/48K 32K/48K 48K/64K 48K/64K 48K/64K 48K/64K

Data (%MWi) 1K(1) 26K 26K 1K(1) 30.5K 30.5K 30.5K

Program

100% Boolean

• LD language 8.8/16.1 Ki 12.4/12.4 Ki 27.2/27.2 Ki 16.1/23.5 Ki 12.4/12.4 Ki 27.2/27.0 Ki 56.8/56.8 K

• IL language 11.2/20.6 Ki 15.8/15.8 Ki 34.7 /34.7Ki 20.5/29.9 Ki 15.8/15.8 Ki 34.7/34.4 Ki 72.4/72.4 K

• ST language 13.7 /13.7 Ki 10.6 /10.6 Ki 23.1/23.1 Ki 13.7/19.9 Ki 10.5/10.5 Ki 23.1/23.0 Ki 48.2/48.2 K

Program

90% Boolean

• LD language 5.3/11.6 Ki 8.8/8.8 K 21.6/21.6 Ki 11.6/17.6 K 8.7/8.7 Ki 21.6/21.6 Ki 47.7/47.5 K

• IL language 6.3/14.2 Ki 10.5/10.7 K 25.9 /26.3Ki 13.9/21.1 K 10.4/10.4 Ki 25.8/25.8 Ki 56.6/56.7 K

• ST language 5.0/11.0 Ki 8.4/8.3 K 20.7/20.4 Ki 11.1/16.9 K 8.4/8.4 Ki 20.7/20.7 Ki 45.4/45.4 K

Program

65% Boolean

• LD language 3.7/8.5 Ki 6.8/6.6K 16.9/16.5 Ki 8.7/13.7 Ki 6.8/6.8 Ki 16.8/16.8 Ki 37.0/37.0 Ki

• IL language 3.8/9.7 Ki 6.9/7.5 K 17.3 /18.7Ki 8.9/14.1 Ki 6.9/6.9 Ki 17.2/17.2 Ki 37.9/37.9 Ki

• ST language 4.4/9.7 Ki 8.0/7.5K 20.0/18.7 Ki 10.3/16.3 Ki 8.0/8.0 Ki 19.9/19.9 Ki 43.8/43.8 Ki

Constants (1) 128 words 128 words 256 words 512 words 128 words 256 words 512 words

K = Kwords Ki = Kinstructions(1) Default size can be extended. However, this will adversely affect the size of the application program.Notes :• When this table gives 2 values for each characteristic separated by a "/", these values relate

respectively to the 2 types of processor (separated by a "/" in the table heading).• The PLC/Memory Usage command in PL7 software provides the memory mapping of the

application in the PLC memory.

1/34___________________________________________________________________________

A

1.3-7 TSX/PCX 57-30/35 PLCs

These tables refer to TSX 57-30, TSX 57-35 and PCX 57-35 PLCs.


Processor 57 30/35

Type system bits %Si 128

of objects I/O bits %I/Qx.i (1)

internal bits %Mi 12152

step bits %Xi 1024

(1) Depends on the declared hardware configuration (I/O module, devices on the AS-i bus andon the FIPIO bus)


Processor TSX 5730 / TSX and PCX 57 35Cartridge - 32K 64K 128K 256K

Internal memory 64K / 80 K 64K / 80 K 64K / 80K 64K / 80K 64K / 80K

Data (%MWi) 1K(1) 30.5 K 30.5K 30.5K 30.5K

Program

100% Boolean

• LD language 23.5/30.8 Ki 12.4 Ki/12.4 Ki 27.2 Ki/27.2 Ki 56.8 Ki/56.8 Ki 90.5 Ki/90.5 Ki

• IL language 29.9/39.3 Ki 15.8 Ki/15.8 Ki 34.7Ki/34.7Ki 72.4 Ki/72.4 Ki 83.6 Ki/83.6 Ki

• ST language 19.9/26.2 Ki 10.5 Ki/10.5 Ki 23.1 Ki/23.1 Ki 48.2 Ki/48.2 Ki 74.6 Ki/74.6 Ki

Program

90% Boolean


• IL language 21.5/29.2 Ki 10.4 Ki/10.4 Ki 25.8 Ki/25.8 Ki 56.7 Ki/56.7 Ki 73.9 Ki/73.9 Ki

• ST language 17.2/23.4 Ki 8.4 Ki/8.4 Ki 20.7 Ki/20.7 Ki 45.49 Ki/45.49Ki 76.0 Ki/76.0 Ki

Program

65% Boolean


• IL language 14.1/19.2 Ki 6.9 Ki/6.9 Ki 17.2 Ki/17.2 Ki 37.9 Ki/37.9 Ki 61.4 Ki/61.4 Ki

• ST language 16.3/22.2 Ki 8.0 Ki/8.0 Ki 19.9 Ki/19.9 Ki 43.8 Ki/43.8 Ki 63.8 Ki/63.8 Ki

Constants (1) 256 words 256 words 256 words 1024 words 1024 words

K = Kwords Ki = Kinstructions(1) Default size can be extended. However, this will adversely affect the size of the application program.

Notes :• When this table gives 2 values for each characteristic separated by a "/", these values relate

respectively to the 2 types of processor (separated by a "/" in the table heading).• The PLC/Memory Usage command in PL7 software provides the memory mapping of the



___________________________________________________________________________1/35

A

1.3-8 PMX57-35/45 and TSX 57-40/45 PLCs

These tables refer to PMX 57-35, PMX 57-45, TSX 57-40 and TSX 57-45 PLCs.


Processor PMX 57 35/45 and TSX 57 40/45

Type system bits %Si 128

of objects I/O bits %I/Qx.i (1)

internal bits %Mi 12152

step bits %Xi 1024

(1) depends on the declared hardware cconfiguration (I/O module, devices on the AS-i bus and on the Fipio bus)


Processor PMX 57 35 / PMX 45 / TSX 57 40 and 45Cartridge - 32K 64K 128K 256K

Internal memory 80K /96K / 96K 80K /96K / 96K 80K /96K / 96K 80K /96K / 96K 80K /96K / 96K

Data(%MWi) 1K(1) 30.5K 30.5K 30.5K 30.5K

Program

100% Boolean

• LD language 28.8/36.1/37.5 Ki 12.4 Ki 27.2 Ki 56.8 Ki 90.5 Ki

• IL language 36.7/46.1/47.8 Ki 15.8 Ki 34.7Ki 72.4 Ki 83.6 Ki

• ST language 24.5/30.7/31.9 Ki 10.5 Ki 23.1 Ki 48.2 Ki 74.6 Ki

Program

90% Boolean


• IL language 27.1/34.7/36.1 Ki 10.4 Ki 25.8 Ki 56.7 Ki 73.9 Ki

• ST language 21.7 /27.8/29.0 Ki 8.4 Ki 20.7 Ki 45.49 Ki 76.0 Ki

Program

65% Boolean


• IL language 17.8/22.9/23.9 Ki 6.9 Ki 17.2 Ki 37.9 Ki 61.4 Ki

• ST language 20.5 /26.5/27.6 Ki 8.0 Ki 19.9 Ki 43.8 Ki 63.8 Ki

Constants (1) 256 words 256 words 256 words 1024 words 1024 words

K = Kwords Ki = Kinstructions(1) Default size can be extended. However, this will adversely affect the size of the application

program.

Notes :• When this table gives several values for each characteristic separated by a "/", these values

relate respectively to each type of processor (separated by a "/" in the table heading).• The PLC/Memory Usage command in PL7 software provides the memory mapping of the


1/36___________________________________________________________________________

A

1.4 Operating modes

1.4-1 Processing on power outage and power return

When the power returns, the context saved is compared to the current one. This definesthe type of start to be performed :• If the application context has changed (loss of the system context or new application),

the PLC initializes the application, that is, performs a cold start.• If the application context is identical, the PLC performs a restart without data

initialization, that is, a warm restart.If the period of the outage is shorter than the supply filter time (approximately 10 ms foran AC power supply or 1 ms for a DC power supply), it is not seen by the program, whichis executed normally.

Note :A cold start can be activated :• On return of power with loss of context (example : processor backup battery not operating).• During the first execution of an application.• By pressing the RESET button on the processor.• By the program setting system bit %S0 to 1.• Through initialization from PL7 by the terminal.• When the PCMCIA memory card is inserted in its slot or when the handle is manipulated (except

on the PCX 57 PLC, where the PCMCIA card must not be inserted when powered up).

A warm restart can be activated :• On return of power without loss of context.• By the program setting system bit %S1 to 1.• From PL7 by the terminal.

RUNApplication

Power failure

Power return

Outagedetected

Normal program execution

Savecontext OK

Memory card identical

Warmrestart

Coldstart

Yes

Yes

No

No

Yes

No

Await power


___________________________________________________________________________1/37

A

1.4-2 Processing on a warm restart

Restart program executionProgram execution restarts from the element at which power outage took place, withoutupdating outputs. The system then performs a restart cycle in which it takes into accountagain all the input modules, relaunches the master task with bit %S1 set to 1 during onescan of the task, and updates the outputs.The system deactivates the fast and event-triggered tasks until the end of the first scanof the master task.

Warm restart processingIn the event of warm restarts users who require a particular processing operation inrelation to the application must write the corresponding program by testing for %S1 at1 at the beginning of the program of the master task.

Change in outputs• As soon as a power outage is detected, the outputs are set to fallback state : either

set to fallback value or retain their current value, depending on the choice madeduring configuration.

• On return of power, the outputs remain at zero until they are updated by the task.

Program executionTOP

BOT

Readinputs

If %S1 = 1,warm restart

processing possible

Power outage> micro-break

Set bit%S1 to 0

Updateoutputs

Stop processorSave application

context

Power return

Configurationself-tests

Yes

NoSet bit

%S1 to 1

1/38___________________________________________________________________________

A

1.4-3 Processing on a cold start

Initialization of the data and the system, which corresponds to :• Resetting the bits, the image of the I/O and the internal words (if the option to reset

internal words on a cold start is selected in the PLC Configuration screen, see section1.3, part D). If the Reset option for %MW is not active and the %MWi are saved in theFlash EPROM internal memory (TSX37), they are retrieved on a cold start.

• Initialization of system bits and words.• Initialization of function blocks based on configuration data.• The tasks, other than the master task, are deactivated until the end of the first scan

of the master task.• Positioning of the Grafcet on the initial steps.

Cold start processingTo carry out an application processing operation after a cold start, bit %S10:X0 can betested by the program (if %S10:X0 = 1, there has been a cold start ). On a cold start, thePLC either does or does not continue execution , depending on the choice definedby the user during configuration (RUN AUTO parameter).

Change in outputs• As soon as a power outage is detected, the outputs are set to fallback state. They are

either set to fallback value, or the current value is maintained, depending on thechoice made during configuration.

• On return of power, the outputs remain at zero until they are updated by the task.

Readinputs

Program executionTOP

If %S0 = 1,process cold

restart

Power outage> micro-break

BOT

Set bit %S0to 0

Updateoutputs

Yes

No

Stop processorSave application

context

Power return

Configurationself-tests

Initialization ofthe application

Set bit %S0to 1


___________________________________________________________________________1/39

A

1.5 Single task software structure

1.5-1 Presentation of the master task

The program of a single task application is associated with a single user task : themaster task, MAST.The program associated with the master task is structured into a main processingoperation, made up of several sections and subroutines.

• Main processing (MAIN) divided intosections. Each section is programmedas a separate entity in the appropriatelanguage (LD, IL, ST or Grafcet).

• Subroutine SRi (i=0 to 253)The subroutine modules are alsoprogrammed as separate entities in LD,IL or ST, with calls to subroutines beingperformed during main processing orfrom other subroutines (a maximum of 8subroutines can be nested).

Either cyclic or periodic execution of themaster task can be chosen (duringconfiguration).

Function modules : see section 7

Presentation of a section

A section is characterized by :

• a name of 24 characters maximum,

• the language in which it is programmed,

• the task to which it belongs,

• an execution condition (optional). Thesection is active if the condition is 1 andinhibited if it is 0.

Objects authorized as conditions :%M, %S, %X, indexed bit, extract bits, %I , %Q. All these objects can be forced fromthe terminal except %S bits, indexed bits, extract bits, %I xy.i.ERR, and %I xy.MOD.ERR.

• a comment of 250 characters maximum.

• protection : write protection, read/write protection. Protection can be global or partial.

Note : when cold starting, execution conditions are at 0 and all the sections with which a conditionis associated are inhibited.

Chamber(LD)

MAST

Oven_1(Grafcet)

PRL(LD)

CHART

POST(IL)

Drying(LD)

Cleaning(ST)

SR0

1/40___________________________________________________________________________

A

A section is an autonomous entity. Thelabels for identifying lines of instructions orrungs are specific to the section (it is notpossible to perform a program jump toanother section).

Sections are executed in order ofprogramming, as they appear in thebrowser window.

The master task in the example oppositecomprises :• a section in ladder language LD,• a section in Grafcet,• a section in Structured Text language

ST,• a section in Instruction List language.

Grafcet section :A Grafcet section comprises :• preprocessing (PRL) programmed in LD,

ST or IL. This is executed before theGrafcet chart,

• the Grafcet chart (CHART) : transitionconditions associated with the transitionsand actions associated with the steps ormacro-step steps are programmed inthe Grafcet pages,

• post-processing (POST) programmedin LD, ST or IL. This is executed after theGrafcet chart,

• subroutines SRi (i = 0 to 253). Subroutinemodules are programmed separately,with calls to subroutines being madeduring preprocessing or post-processing, in the actions associatedwith the steps or from other subroutines(a maximum of 8 subroutines can benested).

Pre-processingMAIN

GrafcetCHARTpage(8 pages)

Post-processingPOST

SubroutineSRi

Actions

SubroutineSRi

SubroutineSRi

Transition conditions

Mast

Sections

SR

Prl

Chart

Post

SR0

SR1

SR2

Chamber

Oven_1

Drying

Cleaning


___________________________________________________________________________1/41

A

1.5-2 Cyclic execution

This type of operation corresponds to normal execution of the PLC scan (default option).It consists of consecutively linking the cycles of the master task (MAST). After updatingthe outputs, the system performs its specific processing operations and then links toanother task scan.

I.P. Internal processing : the system implicitly monitors the PLC (management ofsystem bits and words, updating current values of the realtime clock, updatingstatus indicator lamps, detection of RUN/STOP changes, etc) and processesrequests from the terminal (modifications and animation),

%I Read inputs : writes to memory the status of the information on the inputs ofdiscrete and application-specific modules associated with the task,

Program processing : execution of the application program, written by the user.

%Q Update outputs : writes output bits or words associated with discrete andapplication-specific modules associated with the task depending on the statusdefined by the application program.

Operating scan and scan monitoring

PLC in RUN : the processor performs, inorder, internal processing, reads the inputs,processes the application program andupdates the outputs.

PLC in STOP : the processor performs• internal processing,• reads the inputs,• and depending on the configuration

chosen :- fallback mode : the outputs are set to"fallback" position,- maintain mode : the outputs maintaintheir current values.

Monitoring the scan time : the scan ismonitored by a watchdog. See section 1.5-4.

(1) In the case of the TSX/PMX/PCX 57, internal processing is carried out in parallel with I/Oprocessing.

I.P. I.P.

%I %I%Q %Q

Programprocessing

Programprocessing

Scan n + 1Scan n

(1) (1)

Internal processing

Read inputs

Program processing

Update outputs

RUN STOP

(1)

1/42___________________________________________________________________________

A

1.5-3 Periodic execution

In this operating mode, reading inputs, application program processing and updatingoutput is performed periodically according to a period of time defined during configuration(from 1 to 255 ms).

At the start of the PLC scan, a timer, whose current value is initialized to the perioddefined during configuration, starts to count down. The PLC scan must finish beforeexpiry of this timer, which then launches a new scan.

I.P. Internal processing : the system implicitly monitors the PLC (management ofsystem bits and words, updating current values of the realtime clock, updatingstatus indicator lamps, detection of RUN/STOP changes, etc) and processesrequests from the terminal (modifications and animation).

%I Read inputs : writes to memory the status of the information on the inputs ofdiscrete and application modules associated with the task.

Program processing : execution of the application program, written by the user.

%Q Update outputs : writes output bits or words associated with discrete andapplication-specific modules, according to the status defined by the applicationprogram.


Programprocessing

Programprocessing

%I %Q %I %Q(1) (1) (1) (1)

I.P. I.P. I.P. I.P.

Period Period


___________________________________________________________________________1/43

A

Operating scan and scan monitoring

PLC in RUN : the processor performs, inorder, internal processing, reads inputs,processes the application program andupdates outputs.If the period is not yet over, the processorcompletes its operating scan until the endof the period, via internal processing.

If the operating time becomes longer thanthat assigned to the period, the PLCindicates a period overrun by setting systembit %S19 of the task to 1, processingcontinues and is fully executed (it mustnot, however, exceed the time limit of thewatchdog). The following scan is linked,after implicit writing of the outputs in thecurrent scan.

PLC in STOP : the processor performs• internal processing,• reads inputs,• and depending on the configuration

chosen :- fallback mode : the outputs are set to"fallback" position,- maintain mode : the outputs maintaintheir current values.

Scan monitoring :2 controls are performed :• period overrun,• via the watchdog,

(see section 1.5-4).


Internal processing

Read inputs

Program processing

Update outputs

RUN STOP

Start ofperiod

End of period

Internal processing

(1)

(1)

1/44___________________________________________________________________________

A

1.5-4 Monitoring the scan time

Software watchdog (periodic or cyclic operation)

The execution time of the master task, whether in cyclic or periodic operation, iscontrolled by the PLC (watchdog) and should not exceed the value Tmax defined duringconfiguration (250 ms default, 500 ms maximum).

In the event of an overrun, the application is declared faulty, which stops the PLCimmediately (on the TSX 37 the alarm output %Q2.0 is set to 0 if it has been configured,on the TSX/PMX/PCX 57, the alarm relay on the supply is set to 0).

Bit %S11 is used to monitor execution of this task.

It indicates a watchdog overrun. It is set to 1 by the system when the scan time becomeslonger than the watchdog.

On the TSX/PMX/PCX 57, the watchdog value must be longer than the period.

In periodic operation, an additional control is used to detect period overrun :

• %S19 : indicates a period overrun. It is set to 1 by the system when the scan timebecomes longer than the task period.

• %SW0 : this word contains the value of the period (in ms). It is initialized on a cold startby the value defined during configuration. It can be modified by the user.

Using the execution time of the master task

The following system words provide data on the scan time :

• %SW30 contains the execution time of the last scan.

• %SW31 contains the execution time of the longest scan.

• %SW32 contains the execution time of the shortest scan.

Note :This data can also be accessed from the configuration editor if requested.


___________________________________________________________________________1/45

A

Priority

Event-triggered tasks

Master task

+-

Fast task

1.6 Multitask software structure

1.6-1 Description

The structure in tasks of such an application is as follows :

• The master task, MAST, which is always present and can be cyclic or periodic.• The fast task, FAST, which is optional and always periodic.• Event-triggered processing operations EVTi, called up by the system when an event

appears on an I/O module. This processing is optional and is used by applicationsrequiring short response times to perform operations on I/O.

Master and fast tasks are structured in sections (see the description of a section insection 1.5).

Only the master task can include a Grafcet section.Event-triggered tasks contain only one section the name of which cannot be modified.

Chamber(LD)

MAST

Oven_1(Grafcet)

PRL(LD)

CHART

POST(IL)

Drying(LD)

Cleaning(ST)

FAST

Alarm_Chamber(LD)

Monitor_Sec(LD)

Alarm_Oven(ST)

Alarm_Cleaning(ST)

SR0

SR0

EVT0

Function modules : see section 7.

1/46___________________________________________________________________________

A

Example of a multitask program structure


___________________________________________________________________________1/47

A

Management of tasks :

The master task is active by default. The fast task is active by default if it is programmed.The event-triggered task is activated on appearance of the event with which it has beenassociated.

If an event occurs, or at the start of the fast task scan, the task stops current executionof lower priority tasks in order to execute its own processing. The interrupted task takesover when processing of the priority task is completed.

The execution of fast and event-triggered tasks can be controlled by the program usingsystem bits :

• %S30 is used to activate or deactivate the master task, MAST.

• %S31 is used to activate or deactivate the fast task, FAST.

• %S38 is used to activate or deactivate event-triggered tasks, EVTi.

Example of multitask processing• cyclic master task• fast task with 20 ms period• event-triggered task.

1.6-2 Master task

This task, which has the lowest priority, manages the majority of the applicationprogram.

The MAST task is organized according to the model described in the previous section :implicit reading of inputs, execution of the application program and implicit writing ofoutputs.

Whether the operating mode is periodic or cyclic, the task is monitored by a watchdogwhich is used to detect an abnormal duration of the application program. In the eventof an overrun, system bit %S11 is set to 1 and the application is declared as faulty, whichstops the PLC.

System bit %S30 enables or inhibits the master task.

I P Q

I

Event

Fast

Master

System

P Q

I P I PP Q P Q I P

20 ms 20 ms 20 ms 20 ms

I P Q I P Q I P Q I P Q

1/48___________________________________________________________________________

A

1.6-3 Fast task

This task, which is higher priority than the master task MAST, is periodic in order to leavetime for execution of the lower priority task.

In addition, the processing operations which are associated with it should therefore beshort, to avoid adversely affecting the master task. Like the master task, the associatedprogram consists of sections and subroutines.

The period of the fast task, FAST, is set during configuration, from 1 to 255 ms. This canbe defined as longer than that of the master task, MAST, in order to adapt it to periodicprocessing operations which are slow but have higher priority. The program executedshould however remain short to avoid overrun of lower priority tasks.

The fast task is monitored by a watchdog which is used to detect an abnormal durationof the application program. In the event of an overrun, system bit %S11 is set to 1 andthe application is declared as faulty, which stops the PLC.

Control of the fast task

System word %SW1 contains the value of the period. It is initialized on a cold start bythe value defined during configuration and can be modified by the user by program orvia the terminal.

System bits and words are used to monitor execution of this task :

• %S19 : indicates a period overrun. It is set to 1 by the system when the scan timebecomes longer than the task period.

• %S31 : is used to enable or inhibit the fast task. It is set to 0 by the system on a coldstart of the application, at the end of the first scan of the master task. It is set to 1 or0 to enable or inhibit the fast task.

Display of the fast task execution times

The following system words provide data on scan times :• %SW33 contains the execution time of the last scan.• %SW34 contains the execution time of the longest scan.• %SW35 contains the execution time of the shortest scan.


___________________________________________________________________________1/49

A

1.6-4 Assigning I/O channels to the master and fast tasks

In addition to the application program, the MAST and FAST tasks execute systemfunctions linked to the management of implicit I/O which are associated with them.

Associating a channel or a group of channels with a task is defined in the configurationscreen for the corresponding module. The default associated task is the MAST task.

Since the modularity of discrete modules is 8 consecutive channels (channels 0 to 7,channels 8 to 15, etc), I/O can be assigned in groups of 8 channels, either to the MASTor FAST task. For example, it is possible to assign the channels of a 28 I/O module inthe following way :

• Inputs 0 to 7 assigned to the MAST task.

• Inputs 8 to 15 assigned to the FAST task.

• Outputs 0 to 7 assigned to the MAST task.

• Outputs 8 to 11 assigned to the FAST task.

Each channel of a counter module can be assigned either to the MAST or FAST task.For example, for a 2 channel counter module, it is possible to assign :

• channel 0 to the MAST task and,

• channel 1 to the FAST task.

The channels of TSX 37 analog input modules must be assigned to the MAST task.However, it is possible to assign analog output channels to either the MAST or FASTtask, with 2 channel modularity. For example, for a module with 4 analog outputs, it ispossible to assign :

• channels 0 and 1 to the MAST task and,

• channels 2 and 3 to the FAST task.

The channels of TSX 57 analog I/O modules can be assigned to the MAST or FAST task.Each channel of the isolated analog I/O modules (4 isolated channels) is assigned onan individual basis. A 4-channel modularity is used for other modules.

1/50___________________________________________________________________________

A

1.6-5 Event-triggered tasks

Event-triggered processing is used to reduce the response time of the software oncommand events.

Command eventsThese are external events associated with applications. The appearance of such anevent diverts the application program to the processing operation associated with theI/O channel which caused the event. The inputs (%I, %IW, %ID) associated with the I/Ochannel which triggered the event are updated by the system before calling up eventprocessing. It is possible to configure :

• 8 events in a TSX 37-05/08/10 PLC (EVT1 to EVT8).• 16 events in a TSX 37-21/22 PLC (EVT0 to EVT15).• 32 events in a TSX/PMX/PCX 57-10 PLC (EVT0 to EVT31).• 64 events in a TSX/PMX/PCX 57-20 PLC (EVT0 to EVT63).

The association between a channel and an event number is created in the channelconfiguration screen.

On the TSX 37, event processing can be triggered by :

• Inputs 0 to 3 of module in position 1, on a rising or falling edge.• The counter channel(s) of counter modules.• The counter channels of module 1 (if this is configured as a counter).• Reception of a telegram in a TSX 37-21/22 fitted with a TSX FPP20 module.

On the TSX/PMX/PCX 57, event processing can be triggered by :

• The inputs of DEY 16 FK, DMY 28 FK and DMY 28 RFK modules.• The channels of counter modules.• The channels of CAY axis control modules.• The channels of CFY stepper motor control modules.• Communication channels "FPP20".

Management of event-triggered tasksEvent-triggered processing can be globally enabled or inhibited by the applicationprogram, using system bit %S38. If one or more events occur while they are inhibited,the associated processing operations are lost.

Two PL7 language instructions MASKEVT() and UNMASKEVT(), used in the applicationprogram, also allow masking or unmasking of event-triggered processing. If one or moreevents occur while they are masked, they are saved by the system and the associatedprocessing will only be carried out after unmasking.

The 8 possible command events with a TSX 37-05/08/10 PLC all have the same level ofpriority. Thus, one event processing operation cannot be interrupted by another. Witha TSX 37-21/22 or a TSX/PMX/PCX 57 PLC, there are 2 levels of priority for commandevents : event 0 (EVT0) has higher priority than the other events.


___________________________________________________________________________1/5

Documents

Description of PL7 software Aasousa/sind/schneider/PL7... · 2007. 2. 12. · PL7 Micro software can only be used to program TSX 37 PLCs. PL7 Pro software offers, in addition to the