Schneider Electric PL7OSI, MMS Module User Guide

PDF

مستند

General A

___________________________________________________________________________

Set-Up and Methodology B

OSI-LOADER C

PL7-OSI

PL7-MMS

MMS OFBs

General Appendix G

Application Example H

___________________________________________________________________________

________________________________________________________

General A

___________________________________________________________________________

MMS Presentation

1.1

Introduction to MMS

1.2

MMS Services

1.3

Client-Server Model

1.4

Confirmed and Unconfirmed Services

1.5

The MMS Functional Model

1.5-1 Virtual Manufacturing Device (VMD)

1.5-2 MMS Objects

__________________________________________________________________________________________________

MMS and TSX Series 7 PLCs

2.1

Presentation

2.1-1 Client Function

2.1-2 Server Function

2.2

Communication Profile

2.3

MMS Client Function

2.3-1 MMS Services Supported

2.3-2 MMS Variables Supported

2.4

MMS Server Function

2.4-1 MMS Services Supported

2.4-2 MMS Objects Supported

2/3

2/4

2/5

2/6

2/1

2/2

2/3

Page

1/1

1/2

1/3

__________________________________________________________________________________________________

TSX Series 7 PLC MMS Modelization

3.1

The VMD

3.1-1 The VMD Object Description

3.1-2 MMS Services Supported

3/1

3/4

3.2

The Domain

3.2-1 Domain Object Description

3.2-2 MMS Services Supported

3.3

The Program

3.3-1 PI (Program Invocation) Object Description

3.3-2 MMS Services Supported

3/5

3/6

3/7

3/8

___________________________________________________________________________

A / 1

________________________________________________________

___________________________________________________________________________

3.4

The Variables

3.4-1 Objects Assigned to the PLC Station

3.4-2 Objects Assigned to the Station Application

3.4-3 Unnamed Variable Object Description

3.4-4 Named Variable Object Description

3.4-5 Supported MMS Services

Page

3/9

3/10

3/11

3/12

3/13

3/15

__________________________________________________________________________________________________

Conventions

4.1

"Argument" Parameter

4.2

"Result(+)" Parameter

4.3

"Result(-)" Parameter

4.4

Procedure

4/1

__________________________________________________________________________________________________

Context Management

5.1

Initiate Service

5.1-1 MMS Calling Mode

5.1-2 MMS Called Mode

5.2

Conclude Service

5.2-1 MMS Calling Mode

5.2-2 MMS Called Mode

5/1

5/3

5/5

5.3

Abort Service

5.3-1 MMS Calling Mode

5.3-2 MMS Called Mode

5.4

Reject Service

5.4-1 MMS Client Mode

5.4-2 MMS Server Mode

5/6

5/7

5/8

___________________________________________________________________________

A / 2

________________________________________________________

General A

___________________________________________________________________________

6.1

Status Service

6.1-1 MMS Client Mode

6.1-2 MMS Server Mode

6.2

Unsolicited Status Service

6.2-1 MMS Client Mode

6.2-2 MMS Server Mode

6.3

Identify Service

6.4

GetNameList Service

_______________________________________________________________________________________________________________________________________________________________________________________________

Domain Management Services

7.1

InitiateDownLoadSequence Service

7.2

DownLoadSegment Service

7.3

TerminateDownLoadSequence Service

7.4

InitiateUpLoadSequence Service

7.5

UpLoadSegment Service

7.6

TerminateUpLoadSequence Service

7.7

DeleteDomain Service

7.8

GetDomainAttributes Service

7/1

7/3

7/4

7/6

7/7

7/9

7/10

7/12

Page

6/1

6/2

6/3

6/4

6/5

_______________________________________________________________________________________________________________________________________________________________________________________________

Program Invocation Management Services

8.1

CreateProgramInvocation Service

8.2

DeleteProgramInvocation Service

8.3

Start Service

8.4

Stop Service

8.5

Resume Service

8.6

Reset Service

8.7

GetProgramInvocationAttributes Service

8/1

8/3

8/5

8/6

8/7

8/8

8/9

___________________________________________________________________________

A / 3

________________________________________________________

___________________________________________________________________________

Variable Access Services

9.1

Variable Access Specification Parameters

9.2

Access Result Parameters

9.2-1 Parameters

9.2-2 Error Codes

9.3

Read Service

9.3-1 MMS Client Mode

9.3-2 MMS Server Mode

9.4

Write Service

9.4-1 MMS Client Mode

9.4-2 MMS Server Mode

9.5

InformationReport Service

9.5-1 MMS Client Mode

9.5-2 MMS Server Mode

9.6

GetVariableAccessAttributes Service

_______________________________________________________________________________________________________________________________________________________________________________________________

Appendix

10/1

Page

9/1

9/3

9/4

9/6

9/7

9/9

9/10

9/11

9/12

___________________________________________________________________________

A / 4

MMS Presentation 1

__________________________________________________________________________________________

This Section is intended for users that wish to familiarize themselves with the general concepts of MMS.

The intention is not to provide a description of the MMS standard, but simply to review the key points.

Important

The description of status graphs for MMS objects and the detailed description of

MMS service execution procedures are not described in this manual. For these, refer to the MMS standard.

If the user feels familiar with these concepts, they can proceed directly to Divider A,

Section 2, where MMS support by TSX Series 7 PLCs is described.

1.1

Introduction to MMS

MMS (Message Manufacturing Specification) defines the services (ISO 9506-1) and the protocol (ISO 9506-2) for the Application layer of the MAP 3.0 communication profile that ensures inter-operability of factory devices.

MMS uses the services and protocols of the network used by MAP3.0 for device interconnection.

MMS is designed to meet the requirements of exchanges between devices used in industrial manufacturing applications (PLCs, numerical controllers, robots, etc.) and the systems used for production management (computers, supervisory systems, etc.).

MMS defines a functional model that meets the various requirements for operation, exchange types and elements to manage.

__________________________________________________________________________________________

1 / 1

__________________________________________________________________________________________

1.2

MMS Services

The MMS standard defines 86 services combined into functional sub-groups.

These include:

• Environment and general management services,

• VMD support services,

• Domain management services,

• Program Invocation management services,

• Variable access services,

• Event management services,

• Semaphore management services,

• File management services,

• Operator communication services,

• Journal management services.

1.3

Client-Server Model

__________________________________________________________________________________________

MMS uses the Client-Server model, where the Client device sends requests for services and where the Server device executes the requested service and replies to the Client device.

A device may support only the Server mode (responding to requests for services), or only the Client mode (sending requests for services), or both, in which case it is a Client and a Server.

Most MMS services are confirmed ones.

__________________________________________________________________________________________

1.4

Confirmed and Unconfirmed Services

__________________________________________________________________________________________

A service is confirmed when the exchange (or transaction) requires confirmation from the receiver.

An unconfirmed service is processed without confirmation from the receiver device.

__________________________________________________________________________________________

1 / 2

MMS Presentation 1

__________________________________________________________________________________________

1.5

The MMS Functional Model

1.5-1 Virtual Manufacturing Device (VMD)

MMS defines a Virtual Manufacturing Device (VMD) to represent a variety of manufacturing devices.

A VMD is a model of the Server device (PLC, numerical controller, etc.).

Services assigned to the VMD are those in the "device management" family.

The VMD contains a number of other MMS objects, as described in this Sub-section.

1.5-2 MMS Objects

MMS objects in the VMD are defined by their characteristics and by the operations that

MMS services can perform on them.

These objects represent the operation of the VMD to the MMS services.

There are the following MMS objects:

• Domains,

• Programs,

• Variables,

• Events,

• Semaphores,

• Files,

• Operator stations,

• Journals.

__________________________________________________________________________________________

1 / 3

__________________________________________________________________________________________

1 / 4

MMS and TSX Series 7 PLCs 2

__________________________________________________________________________________________

2.1

Presentation

This section describes the MMS features supported by OSI interface modules for integrating TSX Series 7 PLCs into a heterogeneous MMS network layout.

These features are provided by the STACK OSI 3.0 program that must be uploaded into the OSI interface modules (refer to Divider C in this manual).

The PLC acts as an MMS Client and Server device. It can communicate with any MMS device connected to the network.

2.1-1 Client Function

The services implemented in MMS Client mode support the following operations:

• Read and write remote application variables,

• Receive unsolicited variables,

• Read the status of a remote device,

• Receive the unsolicited status of a remote device.

For the user, support for these services in MMS Client mode is provided by OFBs programmed in the PL7-3 application (refer to Divider F, Section 3).

2.1-2 Server Function

The services implemented in MMS Server mode support the following operations:

• Identifying the PLC (model, version),

• Monitoring the PLC operating state,

• Uploading and saving the PLC station application,

• Checking the execution of the PL7-3 sequential program,

• Reading and writing PLC application variables.

For the user, support for these MMS services requires no additional programming in the application. The PLC operates as an auto-answering MMS device.

In addition, in MMS Server mode, the PL7-3 program can initiate the following services:

• Sending unsolicited variables,

• Sending TSX Series 7 station operating status.

__________________________________________________________________________________________

2 / 1

__________________________________________________________________________________________

These services are triggered by OFBs programmed in the PL7-3 application PL7-3 (refer to Divider F, Section 3).

In addition, all MMS services are supported simultaneously with Telemecanique X-WAY services (UNI-TE message system, common words, NETDIAG network management, bridge functions, etc.) described in the OSI interface module User's Manuals.

2.2

Communication Profile

The communication services and protocols supported are those defined for MAP3.0.

LAYERS

Application

Presentation

Session

Transport

Network

Data Link

MAC

Physical

STANDARDS

MMS IS

MMS DIS

ACSE

Kernel

ASN1

BCS

TP4

ES/IS

LLC1

Token Bus

CSMA-CD

SERVICES

ISO 9506/1

ISO 8649

ISO 8822

ISO 8824

ISO 8825

ISO 8326

ISO 8072

ISO 8348

ISO 8802.2

ISO 8802.4

ISO 8802.3

PROTOCOLS

ISO 9506/2

ISO 8650

ISO 8823

ISO 8327

ISO 8073

ISO 8473

ISO 9542

ISO 8802.2

ISO 8802.4

ISO 8802.3

BaseBand (10 Mb/s)

The communication profile parameters can be set so that the OSI module can be adapted to various types of configuration (refer to Divider D).

__________________________________________________________________________________________

2 / 2

MMS and TSX Series 7 PLCs 2

__________________________________________________________________________________________

2.3

MMS Client Function

This function lets the PL7-3/MMS application in the TSX Series 7 station initiate MMS exchanges destined for any remote device on the network.

These MMS exchanges are supported by an MMS association, DIS or IS versions, dynamically negotiated when the association is opened.

MMS associations can be opened by the TSX Series 7 station or by the remote device.

2.3-1 MMS Services Supported

Environment and General Management Services:

• Initiate

• Conclude

• Abort

• Reject

VMD Support Services:

• Status

• Unsolicited status

Variables Access Services:

• Read

• Write

• Information Report

__________________________________________________________________________________________

2 / 3

__________________________________________________________________________________________

2.3-2 MMS Variables Supported

The table below shows the characteristics of MMS variables accessed by the MMS

Client PL7-3 program:

SCOPE

VMD/DOMAIN/AA

MMS TYPE

SIMPLE TYPE:

Boolean,

Integer16, Integer32

Unsigned16, Unsigned32

FloatingPoint (simple precision),

VisibleString2N (N =1..2048),

OctetString2N (N = 1..2048)

BitStringN (N = 1..2048)

ARRAY [1..1024] :

Boolean

Integer16, Integer32

Unsigned16, Unsigned32

FloatingPoint (simple precision),

VisibleString2,

OctetString2,

BitString1

BitString16

Structure (simple type) (*)

STRUCTURE [1..16] :

Simple type

Array (simple type) (*)

The programming of these services is explained in Divider F on MMS OFBs.

(*): String type restricted to VisibleString2, OctetString2, BitString1 and BitString16.

__________________________________________________________________________________________

2 / 4

MMS and TSX Series 7 PLCs 2

__________________________________________________________________________________________

2.4

MMS Server Function

This function lets the TSX Series 7 station be seen as an MMS auto-answering device for any remote device on the network.

Cases of unsolicited transmission of variables and TSX Series 7 station status data

(InformationReport, UnsolicitedStatus), must be programmed by the MMS OFBs in the

PL7-3/MMS application.

These MMS exchanges are supported by an MMS association MMS, DIS or IS version, dynamically negotiated when the association is opened.

MMS associations can be opened by the station, the remote device or by the

TSX Series 7 PLC.

2.4-1 MMS Services Supported

Environment and General Management Services:

• Initiate

• Conclude

• Abort

• Reject

VMD Support Services:

• Status

• Unsolicited Status

• GetNameList

• Identify

Domain Management Services:

• InitiateDownLoadSequence

• DownLoadSegment

• TerminateDownLoadSequence

• InitiateUpLoadSequence

• UpLoadSequence

• TerminateUpLoadSequence

• GetDomainAttributes

• DeleteDomain

Program Invocation (PI) Management Services:

• CreateProgramInvocation

• DeleteProgramInvocation

• GetProgramInvocationAttributes

• Start

• Stop

• Resume

• Reset

__________________________________________________________________________________________

2 / 5

__________________________________________________________________________________________

Variable Access Services:

• Read

• Write

• Information Report

• GetVariableAccessAttributes

2.4-2 MMS Objects Supported

The table below shows the MMS objects supported and the PLC correspondence for each type of object.

MMS Object

VMD

TSX Series 7 Description

TSX Series 7 PLC station

DOMAIN (.APP) The station application

.APP (comprising all of the PLC application componants for a V4 level application).

.APP with additional PLC application componants for V5 level applications.

PROGRAM (PI)

VARIABLE

VMD/AA scope

VARIABLE

VMD/DOMAIN/AA scope

The PL7-3 program

(sequential command function)

System Bits (SYi)

Real-time Clock

System Words (SWi)

Internal Bits (Bi), Words (Wi) and Double Words (DWi)

Bit of an Internal Word (Wij)

Constant Words (CWi) and Double

Constant Words (CDWi)

Strings of Words (Wi), Double Words (DWi)

Constant Words (CWi) and Double

Constant Words (CDWi)

Internal Bits (Bi)

__________________________________________________________________________________________

2 / 6

TSX Series 7 PLC MMS Modelization 3

__________________________________________________________________________________________

3.1

The VMD

VMD represents the TSX Series 7 PLC station that supports the OSI module.

3.1-1 The VMD Object Description

This description is taken from the MMS standard.

Executive function

Enables the interface between the MMS model and the PLC station for access to real objects.

It corresponds to the MMS Server.

Vendor Name = TELEMECANIQUE

This attribute defines the device vendor's name.

The value of this attribute is supplied as a response to the MMS Identify service.

Model Name = TSX/PMX 47.420/425 to 107.420/455 for V5 level PLCs

TSX/PMX 47.400 to 107.420 for V4 level PLCs

This attribute defines the model of VMD device.

The value of this attribute is supplied as a response to the MMS Identify service.

Revision = TSX7 Processor version

This attribute defines the version of VMD device.

The value of this attribute is supplied as a response to the MMS Identify service.

List of Abstract Syntaxes Supported

Not used.

Logical Status = STATE_CHANGES_ALLOWED or SUPPORT_SERVICES_ALLOWED

This attribute defines the services accessible in the PLC station (logical operating mode).

The value of this attribute is supplied as a response to the MMS Status service.

__________________________________________________________________________________________

3 / 1

__________________________________________________________________________________________

* STATE_CHANGES_ALLOWED

All MMS services supported by the VMD can be executed.

* SUPPORT_SERVICES_ALLOWED

This case corresponds to a PLC memory that cannot be executed (no application in the

PLC memory).

All MMS services supported by the VMD can be executed except for Program Invocation

Management Services.

The services used to access variables are restricted (no access to DOMAIN scope variables, no access to named variables).

List of Capabilities

Not used.

Physical Status = OPERATIONAL or NEEDS-COMMISSIONING or PARTIALLY OPERATIONAL

This attribute defines the PLC station operational status (hardware operating mode).

The value of this attribute is supplied as a response to the MMS Status service.

OPERATIONAL

The PLC station is fully operational if:

• The memory is executable,

• There are no software errors,

• There are no I/O errors.

NEEDS-COMMISSIONING

The PLC station status requires operator intervention (assistance) if:

• The memory cannot be executed,

• The memory cartridge is not present.

PARTIALLY-OPERATIONAL

All other error conditions correspond to this state.

Local Detail

This (16-bit) attribute is divided into two fields (2*8 bits) and enables a more precise specification of the PLC station status.

Each bit is assigned to data that is true when the bit is set to 1.

The value of this attribute is supplied as a response to the MMS Status service.

__________________________________________________________________________________________

3 / 2

TSX Series 7 PLC MMS Modelization 3

__________________________________________________________________________________________

* PHYSICAL LOCAL DETAIL (8-bits LSB) b0 : b1 :

Non-executable memory

Cartridge absent b2 : b3 :

Software failure

I/O Error

* LOGICAL LOCAL DETAIL (8-bits MSB) b8 : Table of MMS symbols present in the OSI module b9 : OSI directory present in the OSI module

List of Program Invocations (PI) = PL7-3 Program

This attribute contains the list of VMD programs (tasks).

In the present version, there is only one program, i.e. PL7-3.

The PI name is defined in Sub-section 3.3-1.

The value of the "List Of PI" attribute is a response to the MMS GetNameList service.

List of Domains = The PLC station application

This attribute contains the list of VMD domains.

In the present version, there is only one domain, i.e. the PLC station application station

(.APP). The domain name is defined in Sub-section 3.2-1.

The value of the "List Of Domains" attribute is supplied as a response to the MMS

GetNameList service.

List of Transaction Objects

This attribute contains the list of current Transaction objects. A Transaction object is created on reception of any indication primitive for a confirmed service.

This attribute is processed locally in the MMS Server.

List of Upload State Machines (ULSM)

This attribute contains the list of ULSM objects created on reception of an indication from the Domain upload initialization service.

This attribute is processed locally in the MMS Server.

List of Other VMD Specific Objects

This attribute contains the list of other VMD objects.

These are PLC station variables (VMD) that are visible by MMS and defined in Subsection 3.4-1.

Additional details

Not used.

__________________________________________________________________________________________

3 / 3

__________________________________________________________________________________________

3.1-2 MMS Services Supported

The table below shows the MMS services assigned to the TSX Series 7 station VMD object.

MMS Services

TSX Series 7 station VMD identification

(MMS Identify service)

Read the status of the TSX Series 7 station VMD

(MMS Status service)

Access to the list of names for a class of objects (domain, PI, variable) assigned to the VMD or to a domain of the VMD or to an AA scope

(MMS GetNameList service)

Unsolicited transmission of the state of the TSX Series 7 PLC VMD

(MMS UnsolicitedStatus service) (1)

(1):

The programming of this service in the PL7-3 application is described in the appropriate

OFB Sub-section in Divider F, Section 3.

__________________________________________________________________________________________

3 / 4

TSX Series 7 PLC MMS Modelization 3

__________________________________________________________________________________________

3.2

The Domain

The domain is the PLC station application (.APP).

3.2-1 Domain Object Description

This description is taken from the MMS standard.

Domain Name = MMS or PU_MEM (default name)

This attribute clearly identifies the Domain object in the VMD.

List of Capabilities

Not used.

State

This attribute specifies the domain state.

Five states are defined by the MMS standard (LOADING, COMPLETE, UNCOMPLETE,

READY, IN_USE).

These states are processed locally in the MMS Server.

Assigned Application Association

This attribute designates the MMS assignments used to create the domain (uploading).

This attribute is processed locally in the MMS Server.

MMS Deletable = TRUE

This attribute specifies that the Domain is deletable by the MMS DeleteDomain service.

The value of this attribute is provided on response from the MMS GetDomainAttributes service.

Sharable = FALSE

This attribute indicates that the domain is only used by the PL7-3 program in the

TSX Series 7 PLC MMS model.

Domain Content

Not used.

__________________________________________________________________________________________

3 / 5

__________________________________________________________________________________________

List of Subordinate Objects

This attribute contains a list of references to MMS objects that are part of the Domain.

This list contains the station application (Domain) variables that can be accessed by

MMS as defined in Divider A, Sub-section 3.4-2.

List of Program Invocation References

This attribute contains a list of references to programs (tasks) that use the Domain. This list comprises the PI corresponding to the name of the PL7-3 program defined in

Divider A, Sub-section 3.3-1.

Upload In Progress

This attribute specifies the number of domain uploads (saves) in progress.

It is processed locally in the MMS Server.

Additional Detail

Not used.

3.2-2 MMS Services Supported

The table below shows the MMS services assigned to the PLC station Domain application.

MMS Services

Upload the station Domain application

MMS services: InitiateUploadSequence

UploadSegment

TerminateUploadSequence)

Delete the station Domain application

MMS services: DeleteDomain

Download the station Domain application

MMS services: InitiateDownloadSequence

DownloadSegment

TerminateDownloadSequence)

Access to the characteristics of station Domain application

MMS services: GetDomainAttributes

__________________________________________________________________________________________

3 / 6

TSX Series 7 PLC MMS Modelization 3

__________________________________________________________________________________________

3.3

The Program

The program represents the sequential control function, i.e. the PL7-3 program.

3.3-1 PI (Program Invocation) Object Description

This description is taken from the MMS standard.

PI Name = MMS or PI_PL73 (default name)

This attribute unambiguously identifies the PI object

State

This attribute specifies the state of the PI object

Nine states are defined by the MMS standard (IDLE, STARTING, RUNNING, STOPPED,

RESUMING, RESETTING, UNRUNNABLE, NON EXISTENT and STOPPING).

These states are processed locally in the MMS Server.

List of Domains Reference = MMS or PU_MEM

This attribute contains the list of references of the domains assigned to PI.

The domain assigned to PI. PL7-3 is the PLC station application.

MMS Deletable = TRUE

This attribute indicates that the program is deletable by the MMS DeleteProgramInvocation service.

The value of this attribute is supplied on response from the MMS

GetProgramInvocationAttributes service.

Reusable = TRUE

This attribute indicates that the program is executed permanently, without needing to be restarted.

Monitor = FALSE

This attribute indicates that execution of PI will not be tested by the event management mechanisms when it exits the RUNNING state.

__________________________________________________________________________________________

3 / 7

__________________________________________________________________________________________

Start Arguments

Not used.

Additional Detail

Not used.

3.3-2 MMS Services Supported

The table below shows the MMS services assigned to the PL7-3 program PI object.

Create PL7-3 PI

MMS service:

Delete PL7-3 PI

MMS service:

Start PL7-3 PI execution

MMS service:

Stop PL7-3 PI execution

MMS service:

Resume PL7-3 PI execution

MMS service:

Reset to the start of PL7-3 PI

MMS service:

Access to PL7-3 PI characteristics

MMS service:

MMS Services

CreateProgramInvocation

DeleteProgramInvocation

Start

Stop

Resume

Reset

GetPIAttributes

__________________________________________________________________________________________

3 / 8

TSX Series 7 PLC MMS Modelization 3

__________________________________________________________________________________________

3.4

The Variables

These represent the device objects that can be accessed in read/write modes.

The variables supported by the MMS Server are:

MMS Object

NamedVariable

Access

By the variable name

UnnamedVariable By the variable address

A named variable is assigned to a scope.

The MMS Server supports the following scopes:

MMS Scope

VMD_specific

DOMAIN_specific

AA_specific

TSX7 Objects

Variables assigned to the

TSX7 PLC station

Variables assigned to the station application .APP

Variables assigned to an

MMS association/application

The rules for storing MMS variables in the PLC memory are described in the table in

Divider F, Sub-section 3.2-2. They are identical to the rules that apply to storing remote

MMS variables in PL7-3 objects.

Named variables are assigned an "Automatic/Programmed" attribute.

Programmed variable

A programmed variable supports the Coherence and Sequencing Management Services:

• The Coherence Service ensures coherent access to MMS/PL7-3 variables via the

MMS Server Read or Write services, regardless of the length of the variable.

• The Sequencing Service ensures synchronization between an access to an MMS/

PL7-3 variable by the MMS Server Read or Write services and its use in PL7-3.

Access to a "programmed" variable requires programming an MSEMA OFB in the PL7-3 application.

__________________________________________________________________________________________

3 / 9

__________________________________________________________________________________________

"Automatic" variables

An "Automatic" variable does not support the Sequencing Management Service, and supports Coherence Management only if the number of PL7-3 objects that compose the

MMS variable does not exceed the values given in the table below:

Objects Maximum number of PL7-3 objects composing the variable

System bit

Internal bit - word

System word

Real-time clock

Double words

Constant double words

Words

Constant words

Bits

496

Access to an "Automatic" variable does not require programming a MSEMA OFB in the

PL7-3 application.

3.4-1 Objects Assigned to the PLC Station

The following objects, not present in the PL7-3 Configuration mode, are assigned to the

PLC station (VMD scope):

PL7-3 Objects PLC Variables

Date_time

System_bit

SY50 to SY57

SY0 to SY128

The scope of system bits can be changed in the AA scope, using PL7-MMS (refer to

Divider E, Sub-section 3.3).

__________________________________________________________________________________________

3 / 1 0

TSX Series 7 PLC MMS Modelization 3

__________________________________________________________________________________________

3.4-2 Objects Assigned to the Station Application

The following objects, that can be configured in PL7-3 Configuration mode, are assigned to the station application (DOMAIN scope):

Objects PLC Variable

Internal_Bit

Internal_Word

Internal_Double_Word

Constant_Word

Constant_Double_Word

System_Word

Internal_Word_Bit

String of Internal_Words

(2048 words max.)

String of Constant_Words

(2048 words max.)

String of Internal_Double_Words

(1024 double_words max.)

String of Constant_Double_Words

(1024 double_words max.)

String of Internal_Bits

(2048 bits max.)

B0 to B3935 (1)

W0 to W32596

DW0 to DW32595

CW0 to CW26206

CDW0 to CDW26205

SW0 to SW127

Wi,j (j: 0 to F)

W0 to W32596

W0 to W26206

DW0 to DW32595

CDW0 to CDW26205

B0 to B3935

(1) The upper limit of object indexes depends on the configuration established in PL7-3

Configuration mode.

The scope of system bits can be changed in the VMD and AA scopes, using PL7-MMS

(refer to Divider E, Sub-section 3.3).

__________________________________________________________________________________________

3 / 1 1

__________________________________________________________________________________________

3.4-3 Unnamed Variable Object Description

An unnamed variable is designated in the PLC by a "PLC Variable" (e.g.: W10, B7, etc.).

This reference is used to designate the MMS unnamed variable. It is the symbolic address of the MMS variable.

The description below is taken from the MMS standard.

Address = PLC variable

This attribute designates the location of the actual variable in the device.

MMS Deletable = FALSE

This attribute indicates that an unnamed variable cannot be deleted.

Access Method = PUBLIC

This attribute indicates that an unnamed variable is always allowed public access.

Type Description

This attribute designates the type of unnamed variable for its MMS access.

The MMS types that correspond to the accessed objects are listed below:

Unnamed Variable

SYi

Wi,j

DWi

CWi

CDWi

SWi

MMS Type

Boolean

Integer16

Integer32

Integer16

Integer32

Integer16

__________________________________________________________________________________________

3 / 1 2

TSX Series 7 PLC MMS Modelization 3

__________________________________________________________________________________________

3.4-4 Named Variable Object Description

A named variable is designated in the PLC by a symbol. The symbol is defined in the

PLC application and managed in the station symbol data base under XTEL. The table of application symbols is built by PL7-MMS (refer to Divider E).

The description below is taken from the MMS standard.

Variable Name =

This attribute designates the named variable.

MMS Deletable = FALSE

This attribute indicates that the named variable cannot be deleted.

Type Description

This attribute designates the type of named variable by its MMS access.

The MMS types corresponding to the accessed objects are shown opposite:

__________________________________________________________________________________________

3 / 1 3

__________________________________________________________________________________________

Named Variable Type MMS Type

System_Bit

Internal_Bit

Internal_Bit_Word

Internal_Word

Internal_Double_Word

Constant_Word

Constant_Double_Word

System_Word

Date_Time

String of Internal_Words

String of Constant_Words

(2048 Words max.)

String of Internal_Double_Words

String of Constant_Double_Words

(1024 Double_Words max.)

String of Internal_Bits

(2048 bits max.)

Boolean (default)

BitString1

Boolean (default)

BitString1

Boolean (default)

BitString1

Integer16 (default)

Unsigned16,

BitString16,

OctetString2,

VisibleString2

Integer32(default)

Unsigned32,

FloatingPoint

Integer16 (default)

Unsigned16,

BitString16,

OctetString2,

VisibleString2

Integer32 (default)

Unsigned32,

FloatingPoint

Integer16 (default)

Unsigned16,

BitString16,

OctetString2,

VisibleString2

Generalized_time (1)

OctetString2N (N=1 to 2048),

VisibleString2N (N=1 to 2048),

ARRAY [1..1024]:

Integer16,

Unsigned16,

BitString16,

VisibleString2

OctetString2,

STRUCTURE [1..16]:

Type simple,

Array (simple type) (*)

ARRAY [1..1024]:

Integer32(default)

Unsigned32,

FloatingPoint

BitStringN (N=1..2048),

ARRAY [1..1024]:

Boolean,

BitString1

__________________________________________________________________________________________

3 / 1 4

TSX Series 7 PLC MMS Modelization 3

__________________________________________________________________________________________

(1) The Generalized_time type follows MMS recommendations MMS. The named variable takes the predefined name M_DAYTIM.

(*) Type string limited to VisibleString2, OctetString2, BitString1 and BitString16.

Access Method = PUBLIC

This attribute specifies that a named variable is always available for public access.

3.4-5 Supported MMS Services

The table below lists the MMS services assigned to Variable objects.

MMS Server Services

Read one or more variables (16 max.)

MMS Service:

Write one or more variables (16 max.)

MMS Service:

Read

Write

Access to the attributes of one or more variables (16 max.)

MMS Service: GetVariableAccessAttributes

Unsolicited transmission of one or more variables

MMS Service: InformationReport (1)

(1): The programming of this service in the PL7-3 application is described in Divider F,

Sub-section 3.8.

__________________________________________________________________________________________

3 / 1 5

__________________________________________________________________________________________

3 / 1 6

Conventions 4

__________________________________________________________________________________________

Conventions

The following sections will describe the following elements for each service:

• Service parameters,

• The service processing procedure used by the OSI module and the PLC.

4.1

"Argument" Parameter

Defines the parameters of the request (REQ) and the indication (IND) for the service.

The values described are those sent by the MMS Client TSX Series 7 PLC (REQ) and expected (or possible) received by the MMS Server TSX Series 7 PLC.

For services with requests (REQ) that can be initiated by the MMS Server (Abort, Reject,

DownloadSegment, TerminateSequence, UnsolicitedStatus, InformationReport) the values described are those provided by the MMS Server to the remote MMS user.

4.2

"Result(+)" Parameter

Defines the response (RSP) and confirm (CNF) parameters that apply when the requested service is successful.

The values described are those sent by the MMS Client TSX Series 7 PLC (REQ) and expected (or possible) received by the MMS Server TSX Series 7 PLC.

4.3

"Result(-)" Parameter

Defines the error causes and codes assigned to a negative response to a service request.

Only additional error codes specific to this implementation are described.

For other error conditions, refer to the MMS standard.

4.2

Procedure

Each service uses execution functions in the MMS Server resulting in actions performed by the OSI interface module and the TSX Series 7 PLC.

This description informs the user of the responses to expect from the MMS Server to the

PLC for each MMS service (in nominal operation).

The procedures that apply to PL7-3/MMS when using MMS OFBs are described in

Divider F, Section 3.

__________________________________________________________________________________________

4 / 1

__________________________________________________________________________________________

4 / 2

Context Management 5

__________________________________________________________________________________________

Context Management

MMS communication is performed in three phases:

• The connection opening phase (association)

• The message exchange phase

• The connection closure phase

The context management services apply to the first and the last of these phases.

5.1

Initiate Service

The Initiate service lets a calling MMS user to build an environment for communication with the MMS Server depending on the respective resources and availability.

This service must be completed successfully before the calling MMS user can invoke or process MMS services in this environment.

5.1-1 MMS Calling Mode

This service lets the PL7-3/MMS application open an association with a remote MMS application.

a. Argument

Local Detail Calling = 7168

The maximum size in bytes proposed for MMS PDUs (Protocol Data Units).

Proposed Max Serv Outstanding Calling = 2 (M between 2 and 5)

The maximum number of transactions per association that the local application can manage in Server mode after receiving indication of confirmed services.

Proposed Max Serv Outstanding Called = 2 (M between 2 and 5)

The maximum number of transactions per association that the local application proposes to have managed by the remote MMS Server on receiving indication of confirmed services.

The value of M depends on the number of associations configured in PL7-OSI (refer to

PICS Appendix G, Sub-section 1.4).

__________________________________________________________________________________________

5 / 1

__________________________________________________________________________________________

Proposed Data Structure Nesting Level = 2

Maximum nesting levels when defining all types of data:

• Simple type data (Nest=0),

• Tables of simple type data elements (Nest=1),

• Simple data field arrays (Nest=1),

• Tables of data field arrays (Nest=2),

• Tables of simple data elements (Nest=2).

Proposed Version Number = 1 (IS)

MMS protocol version level.

Proposed Parameter CBB = VNAM-STR1-STR2

Set of conformity blocks negotiated for the supported variables.

VNAM corresponds to support for named variables,

STR1 corresponds to support for tables,

STR2 corresponds to support for structures.

Services Supported Calling = Services supported by the local MMS application.

Set of services that the local MMS application supports for this association. An MMS service is "supported" by an MMS application if it can receive the primitive (IND) and generate a response (RSP) when using a confirmed service.

This parameter is represented by a string of bits (85) where each bit represents a service.

The services "supported" by the local MMS application are defined in Divider A, Subsection 2.4.

b. Result(+)

The RESULT(+) parameter is not described in this specific case as all parameters are negotiated, therefore there are no restrictions other than the need to respect MMS standard negotiation rules.

c. Result(-)

Refer to the MMS standard.

All types of error are returned to the PL7-3/MMS application.

__________________________________________________________________________________________

5 / 2

Context Management 5

__________________________________________________________________________________________

5.1-2 MMS Called Mode

This service lets an MMS user open an MMS association with the TSX Series 7 PLC.

A a. Argument

The ARGUMENT parameter is not described in this specific case, as all parameters are negotiated, therefore there are no specific restrictions.

b. Result(+)

The calling MMS user proposes their operating values as the argument for the INITIATE

INDICATION service.

The table below shows the values of the parameters negotiated by the MMS Server and sent in INITIATE RESPONSE(+) after receiving the connection request from the MMS

Server.

Local Detail Called = Minimum (7168, Proposed Max Segment Size)

Negotiated size of MMS PDUs (Protocol Data Units).

If the Local Detail Calling parameter is not present in the connection request, the value returned is 7168 (bytes).

Negotiated Max Serv Outstanding Calling = Proposed Max Serv Outstanding

Calling

The maximum number of transactions that the calling MMS user can manage at any time on this association following the reception of confirmed service indications.

Negotiated Max Serv Outstanding Called = Minimum (M, Proposed Max Serv

Outstanding Called)

The maximum number of transactions that the local application proposes to have managed by the remote MMS Server on receiving indication of confirmed services.

The value of M depends on the number of associations configured in PL7-OSI (refer to

PICS Appendix G, Sub-section 1.4).

Negotiated Data Structure Nesting Level = Minimum (2, Proposed Data

Structure Nesting Level)

__________________________________________________________________________________________

5 / 3

__________________________________________________________________________________________

Maximum nesting levels when defining all types of data:

• Simple type data (Nest=0),

• Tables of simple type data elements (Nest=1),

• Simple data field arrays (Nest=1),

• Tables of data field arrays (Nest=2),

• Tables of simple data elements (Nest=2).

Negotiated Version Number = Minimum (0,1) (DIS,IS)

MMS protocol version.

Negotiated Parameter CBB = Intersection (VNAM-VADR-STR1-STR2-VALT,

Proposed Parameter CBB)

Set of conformity blocks negotiated for the supported variables.

VNAM corresponds to support for named variables,

STR1 corresponds to support for tables,

STR2 corresponds to support for structures.

VALT corresponds to alternate access for variables STR1 and STR2.

Services Supported Called = Services supported by the local application

Set of services that the local MMS Server supports for this association. An MMS service is "supported" by an MMS application if it can receive the primitive (IND) and generate a response (RSP) when using a confirmed service.

This parameter is represented by a string of bits (86) where each bit represents a service.

The services "supported" by the local MMS application are defined in Divider A, Subsection 2.4.

c. Result(-)

Refer to the MMS standard.

d. Procedure

Processing of this service is entirely local in the MMS Server of the OSI interface module.

__________________________________________________________________________________________

5 / 4

Context Management 5

__________________________________________________________________________________________

5.2

Conclude Service

The Conclude service performed negotiated deletion of the MMS communication environment, between the MMS caller and the MMS Server (called). This service ensures that there are not losses of data during transmission when the environment is closed.

Once this service is performed successfully, no new MMS service can be invoked on this association.

5.2-1 MMS Calling Mode

This service lets the PL7-3/MMS application close an MMS association opened with a remote MMS application.

a. Argument

None.

b. Result(+)

None.

c. Result(-)

Refer to the MMS standard.

All types of error are returned to the PL7-3/MMS application.

5.2-2 MMS Called Mode

This service lets the MMS user close an MMS association opened on a TSX Series 7

PLC.

a. Argument

None.

b. Result(+)

None.

c. Result(-)

Refer to the MMS standard.

d. Procedure

Processing of this service is entirely local in the MMS Server of the OSI interface module.

__________________________________________________________________________________________

5 / 5

__________________________________________________________________________________________

5.3

Abort Service

The Abort service immediately interrupts exchanges without any negotiation on the

MMS communication environment, between the MMS user and MMS Server. This service may cause information to be lost during transmission.

This service is not confirmed.

Once invoked successfully, no new MMS service can be invoked using this association.

5.3-1 MMS Calling Mode

This service lets the PL7-3/MMS application immediately interrupt any MMS association opened with a remote MMS application.

a. Argument

Locally Generated = TRUE or FALSE

This parameter indicates whether the Abort request is local (TRUE), i.e. generated by the TSX Series 7 PLC or remote (FALSE), i.e. generated by the remote application.

5.3-2 MMS Called Mode

This service lets the MMS user close an MMS association opened on a TSX Series 7

PLC.

a. Argument

Locally Generated = TRUE or FALSE

This parameter indicates whether the Abort request is local (TRUE), i.e. generated by the TSX Series 7 PLC or remote (FALSE), i.e. generated by the remote application.

When the MMS Server invokes the service, the value of the parameter received by the

MMS user for ABORT INDICATION will be FALSE.

b. Procedure

Processing of this service is entirely local in the MMS Server of the OSI interface module.

__________________________________________________________________________________________

5 / 6

Context Management 5

__________________________________________________________________________________________

5.4

Reject Service

The Reject service is invoked by the MMS service provider that notifies an MMS user of a protocol error detected by the communication protocol.

This service is not confirmed.

5.4-1 MMS Client Mode a. Argument

Detected Here = TRUE or FALSE

This parameter indicates that the protocol error was detected by the local system

(TRUE) or remote system (FALSE).

Original Invoke ID

This parameter indicated (where possible) the invocation number of the PDU (Protocol

Data Unit) found in error.

Reject PDU Type

Specifies the type of PDU found in error.

This value is returned to the PL7-3/MMS application.

Refer to the MMS standard.

Reject Code

Reason for rejection by the PDU depending in its type.

This value is returned to the PL7-3/MMS application.

Refer to the MMS standard.

__________________________________________________________________________________________

5 / 7

__________________________________________________________________________________________

5.4-2 MMS Server Mode a. Argument

Detected Here = TRUE or FALSE

This parameter indicates that the protocol error was detected by the local TSX Series 7 system (TRUE) or the remote MMS application (FALSE).

Original Invoke ID

This parameter indicates (where possible) the invocation number of the PDU (Protocol

Data Unit) in error.

Reject PDU Type

Specifies the type of PDU found in error.

Refer to the MMS standard.

Reject Code

Reason for rejection by the PDU depending on its type.

Refer to the MMS standard.

b. Procedure

Processing of this service is entirely local in the MMS Server of the OSI interface module.

__________________________________________________________________________________________

5 / 8

VMD Support Services 6

__________________________________________________________________________________________

VMD Support Services

The VMD support services let the MMS user:

• Know the status (solicited and unsolicited) of the TSX Series 7 station,

• Know the identity and the characteristics of the TSX Series 7 PLC,

• Acquire the list of names of the various MMS objects in the TSX Series 7 PLC.

In MMS Client mode, the PL7-3/MMS application can:

• Request the status of a remote device,

• Receive the unsolicited status of a remote device.

6.1

Status Service

6.1-1 MMS Client Mode

The Status service lets the PL7-3/MMS application know the status of a remote device.

a. Argument

Extended Derivation = FALSE

A simple type approach is used when addressing the remote MMS application to determine the status of the device (no extended tests, such as self-test types requested).

b. Result(+)

VMD Logical Status

VMD Physical Status

The values expected for these parameters are those defined as possible by the MMS standard.

These values are returned to the PL7-3/MMS application.

Local Detail

The value of this string of 128 bits depends on the implementation of the remote device.

This value is returned to the PL7-3/MMS application.

c. Result (-)

Refer to the MMS standard.

All error types are returned to the PL7-3/MMS application.

__________________________________________________________________________________________

6 / 1

__________________________________________________________________________________________

6.1-2 MMS Server Mode

The Status Service lets the calling MMS user know the status of the TSX Series 7 PLC station.

a. Argument

Extended Derivation

Not used.

b. Result(+)

VMD Logical Status

VMD Physical Status

These paramters are described in Divider A, Sub-section 3.1.

Local Detail

This paramter is described in Divider A, Sub-section 3.1.

c. Result(-)

Refer to the MMS standard.

d. Procedure

The MMS Server sends a UNI-TE READ_CPU request to the PLC to find out the status of the TSX Series 7 PLC station.

__________________________________________________________________________________________

6 / 2

VMD Support Services 6

__________________________________________________________________________________________

6.2

Unsolicited Status Service

6.2-1 MMS Client Mode

The Unsolicited Status service lets the PL7-3/MMS application receive unsolicited status information from a remote device.

This service is not confirmed.

a. Argument

VMD Logical Status

VMD Physical Status

The values expected for these parameters are those defined as possible in the MMS standard.

These values are returned to the PL7-3/MMS application.

Local Detail

The value of this string of 128 bits depends on the implementation of the remote device.

This value is returned to the PL7-3/MMS application.

6.2-2 MMS Server Mode

The Unsolicited Status service lets the MMS Server send the unsolicited status of the

TSX Series 7 PLC station.

This service is not confirmed.

a. Argument

VMD Logical Status

VMD Physical Status

These parameters are described in Divider A, Sub-section 3.1.

Local Detail

This parameter is described in Divider A, Sub-section 3.1.

__________________________________________________________________________________________

6 / 3

__________________________________________________________________________________________

6.3

Identify Service

The Identify service lets a calling MMS user acquire data on the identity and characteristics of the TSX Series 7 PLC station.

This service is only supported in MMS Server mode.

a. Arguments

None.

b. Result(+)

Vendor Name

Model Name

Revision

These parameters are described in Divider A, Sub-section 3.1-1.

List of Abstract Syntaxes

Not used.

c. Result(-)

Refer to the MMS standard.

d. Procedure

The MMS Server sends a UNI-TE READ_CPU request to the PLC to find out the identity of the TSX Series 7 PLC station.

__________________________________________________________________________________________

6 / 4

VMD Support Services 6

__________________________________________________________________________________________

6.4

GetNameList Service

The GetNameList service lets the MMS user that invokes the service gain access to all or part of the list of MMS object names defined in the TSX Series 7 PLC station.

This service is only supported in MMS Server mode.

a. Argument

Extended Object Class = Object-Class

This parameter defines the "extended" class of object names that should be sent back by the MMS SERVER. The expected value designates the "MMS 9506 Standard" class.

Object Class = Named Variable or Domain or Program Invocation

Specifies the class of object names that should be returned by the MMS Server.

These objects are described in Divider A, Section 3.

CS Object Class

Not used.

Object Scope = VMD-specific or DOMAIN-specific or AA-specific

The scope of the objects whose names are returned.

The scope of PLC objects is described in Divider, Sub-section 3.4.

Domain Name

Domain name when Object Scope equals DOMAIN-specific.

The domain name is specified in Divider A, Sub-section 3.2-1.

Continue After

Designates the name of the object after which the names in the list should be sent back.

b. Result(+)

List of Identifier

__________________________________________________________________________________________

6 / 5

__________________________________________________________________________________________

This parameter contains the list of object name of the class and scope specified by the

Object Class and Object Scope parameters, within the limits defined by the Continue

After parameter.

If no object exists, the list will be blank.

More Follows = TRUE or FALSE

This parameter indicates whether it is necessary (TRUE) to perform new requests using the GetNameList service to obtain the full list of names required.

c. Result(-)

Error Class = VMD-STATE

Error Code = VMD-STATE-CONFLICT

Additional Code

TEMPORARILY_UNAVAILABLE (1)

Loading table of symbols

Error Class = ACCESS

Error Code = OBJECT_NON_EXISTENT

Additional Code

INVALID_DOMAIN_NAME (1)

Domain name does not designate a domain that exists.

Error Code = OBJECT_ACCESS_UNSUPPORTED

Additional Code

INVALID_EXTENDED_OBJECT_CLASS (1)

Value of the "Extended Object Class" parameter is incorrect

INVALID_OBJECT_CLASS (2)

Value of the "ObjectClass" parameter is incorrect

INVALID_OBJECT_SCOPE (3)

Value of the "Object Scope" parameter is incorrect

Error Class = SERVICE

Error Code = CONTINUATION-INVALID

The "Continue After" parameter does not designate a known object.

d. Procedure

This service is processed locally in the OSI interface module.

__________________________________________________________________________________________

6 / 6

Domain Management Services 7

__________________________________________________________________________________________

Domain Management Services

The domain management services let the MMS user gain access to the PLC station

(.APP), i.e.:

• Download the station application to the TSX Series 7 PLC

• Archive the station application from the TSX Series 7 PLC

• Acquire the characteristics of the station application

• Delete the station application

7.1

InitiateDownLoadSequence Service

This service is invoked by the calling MMS user to request that the MMS Server create the named domain and start the download sequence.

This service is only supported in MMS Server mode a. Argument

Domain Name

This parameter is described in Sub-section 3.2-1.

List of Capabilities

Not used.

Sharable = FALSE

Refer to the description of the DOMAIN object in Divider A, Sub-section 3.2-1.

b. Result(+)

None.

__________________________________________________________________________________________

7 / 1

__________________________________________________________________________________________ c. Result(-)

Error Class = DEFINITION

Error Code = OBJECT_EXIST

Additional Code

DOMAIN_ALREADY_EXIST (1)

The station application cannot be downloaded (the PLC is in RUN)

Error Code = OBJECT-UNDEFINED

Additional Code

INVALID_DOMAIN_NAME (1)

Incorrect domain name

Error Class = OTHERS

Error Code = INITIATE_DOWNLOAD_SEQUENCE (2)

Additional Code INVALID_SHARABLE_ATTRIBUTE

(2)

The "Sharable" parameter should be set to FALSE

Error Class = SERVICE

Error Code = OBJECT_STATE CONFILICT

Additional Code = INVALID_DOMAIN_STATE (2)

The domain state is incorrect

Error Class = VMD_STATE

Error Code = DOMAIN_TRANSFER_PROBLEM

Additional Code = DOWNLOAD_IMPOSSIBLE (6)

Remote downloading refused by the PLC d. Procedure

The OSI module MMS Server processes this service using the following operations:

• PLC reservation (UNI-TE RESERVE request),

• Acquisition of the station application status (UNI-TE IDENTIFICATION_OBJECT request (appli_station)),

• Initialize downloading to the PLC (UNI-TE OPEN_DOWNLOAD_SEQUENCE.req

request)

__________________________________________________________________________________________

7 / 2

Domain Management Services 7

__________________________________________________________________________________________

7.2

DownLoadSegment Service

This service is invoked by the MMS Server so that the calling MMS user can transfer a segment of station application (.APP) data to it for downloading.

This service is only supported in MMS Server mode.

a. Argument

Domain Name

This parameter is described in Divider A, Sub-section 3.2-1.

b. Result(+)

Load Data

Data (byte string) to load.

More Follows = TRUE or FALSE

This parameter indicates that there is more (TRUE) or no more (FALSE) data to download.

c. Result(-)

Refer to the MMS standard.

d. Procedure

The OSI module MMS Server processes this service using the following operations:

• Sending a DOWNLOAD_SEGMENT.req until a DOWNLOAD_SEGMENT.cnf is received with the parameter More Follows - FALSE,

• Segmenting data received with DownLoadSegment.Cnf into

N UNI-TE WRITE_DOWNLOAD_SEGMENT requests that are then sent to the PLC.

__________________________________________________________________________________________

7 / 3

__________________________________________________________________________________________

7.3

TerminateDownLoadSequence Service

This service is invoked by the MMS Server to indicate to the calling MMS user that the download sequence is complete.

This service is only supported in MMS Server mode.

a. Argument

Domain Name

This parameter is described in Divider A, Sub-section 3.2-1.

Discard = TRUE or FALSE (DIS) or SERVICE ERROR (IS)

The DIS version of this parameter indicates that a problem was (TRUE) or was not

(FALSE) detected during a domain download action.

If the value is TRUE, the station application is not validated.

The IS version of this parameter is a Service Error typr.

Error Class = VMD_STATE

Error Code = DOMAIN_TRANSFER_PROBLEM

Additional Code = INCONSISTENT_DATA (2)

The downloaded data is incoherent because:

• Their length is null,

• The PLC declared them incoherent during downloading,

• The PLC declared then invalid at the end of the download procedure.

Additional Code = WRITE_SEG_IMPOSSIBLE (4)

The PLC cannot write the downloaded data.

Additional Code = READ_SEG_IMPOSSIBLE (5)

The PLC cannot read the data.

Error Code = VMD_STATE_CONFLICT

No Additional Code, the PLC has lost the reservation.

Error Class = OTHERS

Error Code = DATE_CODED (1)

Downloaded data in coded format is not supported.

__________________________________________________________________________________________

7 / 4

Domain Management Services 7

__________________________________________________________________________________________ b. Result(+)

None.

c. Result(-)

Refer to the MMS standard.

d. Procedure

The OSI module MMS Server uses the following operations to process the service:

• On receiving DownLoadSegment.Cnf with the "More Follows = FALSE" parameter, t he sy st em s ends t he PLC a close download seq uenc e (UNI-TE

CLOSE_DOWNLOAD_SEQUENCE request),

• Releases PLC reservation (UNI-TE RELEASE request),

• Sends a TERMINATE_DOWNLOAD_SEQUENCE.req request,

• Receives TERMINATE_DOWNLOAD_SEQUENCE.cnf

__________________________________________________________________________________________

7 / 5

__________________________________________________________________________________________

7.4

InitiateUpLoadSequence Service

This service is invoked by the calling MMS user to request that the MMS Server initiate the upload sequence on the station application (.APP).

This service is only supported in MMS Server mode.

a. Argument

Domain Name

This parameter is described in Divider A, Sub-section 3.2-1.

b. Result(+)

ULSM ID

Identifies the Upload State Machine object. The MMS Server only supports a single upload at one time.

List of Capabilities

Not used.

c. Result(-)

Error Class = ACCESS

Error Code = OBJECT_NON_EXISTENT

Additional Code

DOMAIN_NON_EXISTENT (2)

Incorrect domain name or invalid station application.

__________________________________________________________________________________________

7 / 6

Domain Management Services 7

__________________________________________________________________________________________

Error Class = SERVICE

Error Code = PRIMITIVES_OUT_OF_SEQUENCE

Error Code = OBJECT_STATE_CONFLICT

Additional Code

UPLOAD_IMPOSSIBLE (6)

"Protected" station application

Error Code = PRIMITIVES_OUT_OF_SEQUENCE

A save action is already in progress

A d. Procedure

The OSI module MMS Server uses the following operations to process the service:

• PLC reservation (UNI-TE RESERVE request),

• Acquisition of the station application status (UNI-TE IDENTIFICATION_OBJECT request (appli_station)),

• Initialization of the PLC upload sequence (UNI-TE OPEN_UPLOAD_SEQUENCE.req

request).

7.5

UpLoadSegment Service

This service is invoked by the calling MMS user to request that the MMS Server transfer a data segment from the station application (.APP) to be saved.

This service is only supported in MMS Server mode.

a. Argument

ULSM

Identifies the number of the save in progress.

__________________________________________________________________________________________

7 / 7

__________________________________________________________________________________________ b. Result(+)

Load Data

Data (byte string) to save.

More Follows = TRUE or FALSE

This parameter indicates that the remains (TRUE) or not (FALSE) data to save.

c. Result(-)

Error Class = ACCESS

Error Code = OBJECT_NON_EXISTENT

Additional Code

USLM_NON_EXISTENT (5)

The designated USLM does not exist

Error Class = SERVICE

Error Code = PRIMITIVE_OUT_OF_SEQUENCE

Save is completed or Uploadsegment.cnf was received previously

Error Class = VMD_STATE

Error Code = DOMAIN_TRANSFER_PROBLEM

Additional Code = READ_DATA_SEGMENT_IMPOSSIBLE (5)

The PLC cannot read the data.

d. Procedure

The OSI module MMS Server uses the following operations to process the service:

• Stringing the data received from the PLC in response to the N

UNI-TE READ_UPLOAD_SEGMENT requests (up to the maximum size of the MMS

PDU) and sending UploadSegment.Rsp to the remote MMS system.

__________________________________________________________________________________________

7 / 8

Domain Management Services 7

__________________________________________________________________________________________

7.6

TerminateUpLoadSequence Service

This service is invoked by the calling MMS user to indicate to the MMS SERVER, the end of the upload sequence.

This service is only supported in MMS Server mode.

A a. Argument

ULSM ID

Identifies the number of the save to complete.

b. Result(+)

None c. Result(-)

Error Class = ACCESS

Error Code = OBJECT_NON_EXISTENT

Additional Code

USLM_NON_EXISTENT (5)

The designated USLM does not exist

Error Class = VMD_STATE

Error Code = DOMAIN_TRANSFER_PROBLEM

Additional Code

UPLOAD_NON_FINISHED (3)

The finished indication precedes the end of the upload

__________________________________________________________________________________________

7 / 9

__________________________________________________________________________________________ d. Procedure

The OSI module MMS Server uses the following operations to process the service:

• On reception of TerminateUploadSegment.Ind, send the end of upload message to the PLC (UNI-TE CLOSE_UPLOAD_SEQUENCE request),

• Release PLC reservation (UNI-TE RELEASE request).

7.7

DeleteDomain Service

This service lets the calling MMS user to request that the MMS Server delete the station application (.APP).

This service is only supported in MMS Server mode.

a. Argument

Domain name

This parameter is described in Divider A, Sub-section 3.2-1.

b. Result(+)

None c. Result(-)

Error Class = DEFINITION

Error Code = OBJECT_UNDEFINED

Additional Code

DOMAIN_UNDEFINED (2)

The designated domain does not exist

__________________________________________________________________________________________

7 / 1 0

Domain Management Services 7

__________________________________________________________________________________________

Error Class = SERVICE

Error Code = OBJECT_STATE_CONFLICT

Additional Code

DOMAIN_NOT_DELETABLE (1)

The domain cannot be deleted

INVALID_DOMAIN_STATE (2)

The domain state does not allow deletion

UPLOAD_IN_PROGRESS (5)

Domain upload in progress

A d. Procedure

The OSI module MMS Server uses the following operations to process the service:

• Reserving the PLC (UNI-TE RESERVE request),

• Acq ui ring th e st ation ap pl i cation (DOMAIN) st at e, usi ng t he

UNI-TE IDENTIFICATION_OBJECT(appli_Station) request sent to the PLC,

• Acquiring the program (PI) state, using the UNI-TE STATUS request sent to the PLC,

• Invalidating the station application (UNI-TE INVALID_APPLI (appli_station) request,

• Physically deleting the station descriptor (UNI-TE OPEN_DOWNLOAD request followed by the UNI-TE WRITE DOWNLOAD request from 64 bytes to 0,

• Releasing PLC reservation (UNI-TE RELEASE request).

__________________________________________________________________________________________

7 / 1 1

__________________________________________________________________________________________

7.8

GetDomainAttributes Service

This service lets the MMS user request that the MMS Server provide the value of all attributes in the specified domain.

This service is only supported in MMS Server mode.

a. Arguments

Domain Name

This parameter is described in Divider A, Sub-section 3.2-1.

b. Result(+)

List of Capabilities

Not used.

State

MMS Deletable

Sharable

List of PIs

Upload In Progress

These parameters are described in Sub-section 3.2-1.

c. Result(-)

Error Class = ACCESS

Error Code = OBJECT_NON_EXISTENT

Additional Code

DOMAIN_NON_EXISTENT (2)

Incorrect domain name d. Procedure

The OSI module MMS Server uses the following operations to process the service:

• Acquisition of the state of the station application using the

UNI-TE IDENTIFICATION_OBJECT(appli_station) request sent to the PLC and the program (UNI-TE STATUS request),

• Acquisition of the state of the application using the UNI-TE STATE request sent to the

PLC.

__________________________________________________________________________________________

7 / 1 2

Program Invocation Management Services 8

__________________________________________________________________________________________

Program Invocation Management Services

The program invocation management services let the MMS user access the PL7-3 sequential control program, i.e. to:

• Create and delete the PL7-3 program,

• Start and stop the PL7-3 program,

• Acquire PL7-3 program characteristics.

8.1

CreateProgramInvocation Service

This service lets the calling MMS user create a PI in the MMS Server. This service is only supported in MMS Server mode.

a. Argument

Program Invocation Name

List of Domain Names

Reusable

This parameter is described in Divider A, Sub-section 3.3-1.

Monitor

Not used.

b. Result(+)

None.

__________________________________________________________________________________________

8 / 1

__________________________________________________________________________________________ b. Result(-)

Error Class = ACCESS

Error Code = OBJECT_NON_EXISTENT

Additional Code

DOMAIN_NON_EXISTENT (2)

Incorrect domain name assigned

Error Class = DEFINITION

Error Code = OBJECT_EXIST

Additional Code

PI_ALREADY_EXISTS (2)

The designated PI already exists

Error Code = OBJECT_UNDEFINED

Additional Code

INVALID_PI_NAME (4)

The assigned PI name is incorrect

Error Class = SERVICE

Error Code = OBJECT_STATE_CONFLICT

Additional Code

INVALID_DOMAIN_STATE (2)

Incorrect assigned domain state

Error Class = OTHERS

Error Code = CREATE_PROGRAM_INVOCATION

Additional Code

INVALID_REUSABLE_ATTRIBUTE (3)

The value of this parameter must be TRUE

Error Class = VMD_STATE

Error Code = VMD_STATE_CONFLICT

No Additional Code

The PI cannot be created in the PLC

__________________________________________________________________________________________

8 / 2

Program Invocation Management Services 8

__________________________________________________________________________________________ d. Procedure

The OSI module MMS Server uses the following operations to process the service:

• PLC reservation (UNI-TE RESERVE request),

• Acquisition of the station application (UNI-TE IDENTIFI-CATION_OBJET(appli_station) request) and pr ogram (UNI-TE STATUS request) state,

• Validating the PL7-3 program (UNI-TE VALID_APPLI(appli_PL7) request),

• Releasing PLC reservation (UNI-TE RELEASE request).

8.2

DeleteProgramInvocation Service

This service lets the MMS delete a PI that exists in the MMS Server.

This service is only supported in MMS Server mode.

a. Argument

PI Name

This parameter is described in Divider A, Sub-section 3.3-1.

b. Result(+)

None.

__________________________________________________________________________________________

8 / 3

__________________________________________________________________________________________ c. Result(-)

Error Class = DEFINITION

Error Code = OBJECT_UNDEFINED

Additional Code

PI_UNDEFINED (2)

PI does not exist

Error Class = SERVICE

Error Code = OBJECT_STATE_CONFLICT

Additional

Class = VMD_STATE

Error Code = VMD_STATE_CONFLICT

No Additional Code

PI cannot be deleted from the PLC d. Procedure

The OSI module MMS Server processes the service using the following operations:

5 PLC reservation (UNI-TE RESERVE request),

5 Acquisition of the program status (UNI-TE STATUS request),

• Invalidating the PL7-3 program (UNI-TE INVALID_APPLI(appli_PL7) request),

• Releasing the PLC reservation (UNI-TE RELEASE request).

__________________________________________________________________________________________

8 / 4

Program Invocation Management Services 8

__________________________________________________________________________________________

8.3

Start Service

This service lets the MMS user start the PL7-3 program. PI goes from IDLE to RUNNING state.

This service is only supported in MMS Server mode.

a. Argument

PI Name

This parameter is described in Divider A, Sub-section 3.3-1.

Execution Argument

Not used.

b. Result(+)

None.

c. Result(-)

Error Class = ACCESS

Error Code = OBJECT_ACCESS_UNSUPPORTED

Additional Code = EXEC_ARGUMENT_UNSUPPORTED (9)

The argument execution parameter is not supported

Error Code = OBJECT_NON_EXISTENT

Additional Code

PI_NON_EXISTENT (3)

The designated PI does not exist

Error Class = OTHERS

Service Specific Information = (PI status)

Incorrect PI status

Error Class = VMD_STATE

Error Code = VMD_STATE_CONFLICT

Sans Additionnal Code

The PLC will not change to RUNNING state d. Procedure

The OSI module MMS Server uses the following operations to process the service:

• Reservation of the PLC (UNI-TE RESERVE request),

• Acquisition of the PL7-3 program status (UNI-TE STATUS request),

• Transmission to the PLC of the UNI-TE RUN request,

• Release the PLC reservation (UNI-TE RELEASE request).

__________________________________________________________________________________________

8 / 5

__________________________________________________________________________________________

8.4

Stop Service

This service lets the MMS user stop the PL7-3 program. PI goes from RUNNING to

STOPPED state.

This service is only supported in MMS Server mode.

a. Argument

PI Name

This parameter is described in Divider A, Sub-section 3.3-1.

b. Result(+)

None.

c. Result(-)

Error Class = ACCESS

Error Code = OBJECT_NON_EXISTENT

Additional Code

PI_NON_EXISTENT (3)

Designated PI does not exist

Error Class = OTHERS

Service Specific Information = (PI status)

Incorrect PI status

Error Class = VMD_STATE

Error Code = VMD_STATE_CONFLICT

No Additionnal Code

The PLC will not go to STOPPED d. Procedure

The OSI module MMS Server uses the following operations to process the service:

• Reservation of the PLC (UNI-TE RESERVE request),

• Acquisition of the PL7-3 program status (UNI-TE STATUS request),

• Transmission to the PLC of the UNI-TE RUN request,

• Release the PLC reservation (UNI-TE RELEASE request).

__________________________________________________________________________________________

8 / 6

Program Invocation Management Services 8

__________________________________________________________________________________________

8.5

Resume Service

This service lets the MMS user resume the PL7-3 program when it is stopped. PI goes from STOPPED to RUNNING state.

This service is only supported in MMS Server mode.

a. Argument

PI Name

This parameter is described in Divider A, Sub-section 3.3-1.

Execution Argument

Not used.

b. Result(+)

None.

c. Result(-)

Error Class = ACCESS

Error Code = OBJECT_ACCESS_UNSUPPORTED

Additional Code = EXEC_ARGUMENT_UNSUPPORTED (9)

The argument execution parameter is not supported

Error Code = OBJECT_NON_EXISTENT

Additional Code

PI_NON_EXISTENT (2)

Designated PI does not exist

Error Class = OTHERS

Service Specific Information = (PI status)

Incorrect PI status

Error Class = VMD_STATE

Error Code = VMD_STATE_CONFLICT

No Additionnal Code

The PLC will not go to RUNNING state d. Procedure

The OSI module MMS Server uses the following operations to process the service:

• Reservation of the PLC (UNI-TE RESERVE request),

• Acquisition of the PL7-3 program status (UNI-TE STATUS request),

• Transmission to the PLC of the UNI-TE RUN request,

• Release the PLC reservation (UNI-TE RELEASE request).

__________________________________________________________________________________________

8 / 7

__________________________________________________________________________________________

8.6

Reset Service

This service lets the MMS user re-initialize the PL7-3 program after stopping it. PI goes from STOPPED to IDLE state.

This service is only supported in MMS Server mode.

a. Argument

PI Name

This parameter is described in Divider A, Sub-section 3.3-1.

b. Result(+)

None.

c. Result(-)

Error Class = ACCESS

Error Code = OBJECT_NON_EXISTENT

Additional Code

PI_NON_EXISTENT (3)

Designated PI does not exisst

Error Class = OTHERS

Service Specific Information = (PI status)

Incorrect PI status

Error Class = VMD_STATE

Error Code = VMD_STATE_CONFLICT

No Additionnal Code

The PLC will not go to IDLE state d. Procedure

The OSI module MMS Server uses the following operations to process the service:

• Reservation of the PLC (UNI-TE RESERVE request),

• Acquisition of the PL7-3 program status (UNI-TE STATUS request),

• Invalidation of the PL7-3 program (UNI-TE INVALID_APPLI(appli_PL7) request,

• Validation of the PL7-3 program (UNI-TE VALID_APPLI(appli_PL7) request,

• Release the PLC reservation (UNI-TE RELEASE request).

__________________________________________________________________________________________

8 / 8

Program Invocation Management Services 8

__________________________________________________________________________________________

8.7

GetProgramInvocationAttributes Service

This service lets the MMS user request that the MMS Server supply the value of all of the attributes of the specified program.

This service is only supported in MMS Server mode.

a. Argument

PI Name

This parameter is described in Divider A, Sub-section 3.3-1.

b. Result(+)

State

List of Domain Names

MMS Deletable

Reusable

This parameter is described in Divider A, Sub-section 3.3-1.

c. Result(-)

Error Class = ACCESS

Error Code = OBJECT_NON_EXISTENT

Additional Code

PI_NON_EXISTENT (3)

Designated PI does not exist

A d. Procedure

The OSI module MMS Server uses the following operations to process the service:

• Reservation of the PLC (UNI-TE RESERVE request),

• Acquisition of the PL7-3 program status (UNI-TE STATUS request),

• Release the PLC reservation (UNI-TE RELEASE request).

__________________________________________________________________________________________

8 / 9

__________________________________________________________________________________________

8 / 1 0

Variable Access Services 9

__________________________________________________________________________________________

Variable Access Services

The variable access services let the MMS user access PLC application variables, i.e.

to:

• Read or write one or more PL7-3 program variables,

• Acquire the characteristics of one or more PL7-3 program variables,

• Receive unsolicited variables from the PL7-3/MMS program.

In MMS Client mode, the PL7-3/MMS application can:

• Read and write remote MMS application variables,

• Receive unsolicited variables from the remote MMS application MMS.

9.1

Variable Access Specification Parameters

The table below shows the possible values for the Variable Access Specification parameter in the READ, WRITE and INFORMATION REPORT requests.

Variable Access Specification

Kind of Access = List of Variable

This parameter indicates access to a list of variables.

Kind of Access = List of Variable

Variable Specification

Kind of Variable = NAMED or ADDRESS

In MMS Client mode, the type of variable is always NAME.

In the MMS Server mode, the ADDRESS variable type is restricted to simple type variable READ/WRITE services.

Kind of Variable = NAMED

Name Scope = VMD-Specific or DOMAIN-Specific or AA-Specific

Scope of the named variable.

The scope of PLC variables is described in Divider A, Sub-section 3.4.

Notes:

Select access is only possible in MMS Server mode for READ and WRITE services.

Select access to a "Programmed" variable requires programming a MSEMA OFB in the PL7-3 application.

__________________________________________________________________________________________

9 / 1

__________________________________________________________________________________________

Domain Identifer

Domain name when DOMAIN-Specific.

The domain name is described in Divider A, Sub-section 3.2-1.

Item Identifer

Name of the variable.

The named variable is described in Divider A, Sub-section 3.4-4.

Kind of Variable = ADDRESS

Kind of Address = SYMBOLIC-ADDRESS

The unnamed variable uses a symbolic address.

Symbolic Address

Unnamed objects and the symbolic addressing they support are described in

Divider A, Sub-section 3.4-3.

Kind of Access = List of Variable

Alternate Access

Component Name

Not used.

Kind of selection = Select Alternate Access or Select Access

This parameter indicates whether the specification allows for:

• Select Access,

• Select Alternate Access for Nesting Levels greater than 1.

Access Selection = Component or Index or Index Range (low, size)

Indicates the select access choice made:

• Fields in a structure

• Index in a table

• Field of indexes in a table (low index, size of range).

__________________________________________________________________________________________

9 / 2

Variable Access Services 9

__________________________________________________________________________________________

9.2

Access Result Parameters

The table below describes the possible values of the "Access Result" parameter for the

READ, WRITE and INFORMATION REPORT services.

Access Result

Success = TRUE or FALSE

This parameter indicates that access to each variable was made correctly.

Data Access Error

If Success = FALSE, this parameter indicates the reason for the failure to access each variable.

The various possible values are given in Sub-section 9.2-2.

Data

Kind of Data = SIMPLE or ARRAY or STRUCTURE

If Success = TRUE, this parameter gives the result of access to each variable.

Kind of Data = Simple

Class Size

Octet_string

Boolean

Integer

Unsigned

Bit-string

Floating-point

Visible-string

Generalized_time

4096 bytes max.

16, 32 bits

2048 bits max.

32 bits

4096 bytes max.

Simple type variable.

Kind of Data = ARRAY

List of Data

Table type variable. The table elements can be simple or structure type variables (refer to Divider A, Sub-section 2.3-2, for information on the types supported in MMS Client and

Server modes).

__________________________________________________________________________________________

9 / 3

__________________________________________________________________________________________

Kind of Data = STRUCTURE

List of Data

Structure type variable. The structure fields can be simple or table type fields (refer to

Divider A, Sub-section 2.3-2, for information on the types supported in MMS Client and

Server modes).

9.2-2 Error Codes

The "Data Access Error" codes for the "Access Result" parameter may be returned in response to the Read or Write services when a problem occurs that inhibits execution of access to one or more variables.

Description Values

Data Access Error

Table of symbols not loaded or currently being downloaded to the module.

Access to the programmed variable interrupted after a reset of the

MSEMA OFB.

Format of the symbolic address of a variable (VADR) not supported or not present in the PL7-3 configuration.

MMS type data not supported.

Incoherence between the definition of the variable in the table of server symbols and the definition of data or of alternate access in the

Write request:

- The type of variable is different from the that of the data,

- For a table or structure type variable, the number of elements or fields of the variable is different from that of the data,

- The number of alternative accesses to the variable is incoherent in relation to the data description.

__________________________________________________________________________________________

9 / 4

Variable Access Services 9

__________________________________________________________________________________________

Valeurs

Data Access Error

Meaning

Incoherence between the definition of the variable in the table of server symbols and the definition of data or of alternate access in the

Read or Write request:

- Alternate access to a variable that is not a table or structure type,

- Alternate access by index or index range that exceeds the limits of a table defined in the table of symbols,

- Alternate access to structure field name that does not exist in the definition of the variable in the table of symbols,

- Alternate access by index or index range, to a variable defined as a structure in the table of symbols,

- Alternate access by component to a variable defined as a table in the table of symbols.

Problems when elaborating the Information_Report.req primitive

(memory, etc.). Contact Telemecanique technical support.

Attribute used for defining the variable in the Read or Write requests not supported (values not supported in "Kind of Access", "Scope",

"Kind of Address"),

- Write access not supported for PL7-3 CWi, CDWi and Wi,j objects,

- Alternate access in write is not supported for Boolean table or

Bitstring1 type variables,

- Alternate access to variables by address (VADR) not supported.

Access to a named variable not defined in the table of server symbols.

The name of the domaine assigned to a named variable of domain scope is invalid.

__________________________________________________________________________________________

9 / 5

__________________________________________________________________________________________

9.3

Read Service

9.3-1 MMS Client Mode

This service lets the PL7-3/MMS application read one or more variables from a remote

MMS application.

a. Argument

Specification with Result = FALSE

This parameter indicates that the "Variable Access Specification" parameter must not be a part of the Result(+) response.

Variable Access Specification

This parameter is described in Divider A, Sub-section 9.1-1.

a. Result(+)

Variable Access Specification

This parameter must not be present.

List of Access Result

Contains the list of requested variable values (at most the value of 4 variables).

c. Result(-)

Refer to the MMS specification.

All types of errors are returned to the PL7-3/MMS application.

__________________________________________________________________________________________

9 / 6

Variable Access Services 9

__________________________________________________________________________________________

9.3-2 MMS Server Mode

This service is used by an MMS user to request that the MMS Server return the value of one or more variables assigned to the VMD (the TSX Series 7 PLC station) or to the

DOMAIN (the station application .APP) or association AA.

a. Argument

Specification with Result = TRUE or FALSE

This parameter indicates that the "Variable Access Specification" parameter must

(TRUE) or not (FALSE) be a part of the response Result(+).

Variable Access Specification

This parameter is described in Divider A, Sub-section 9.1-1.

b. Result(+)

Variable Access Specification

This parameter is present if the value of the "Specification with Result" argument is

TRUE.

List of Access Result

Contains the list of requested variable values (at most, the value of 16 variables).

A c. Result(-)

Error Class = ACCESS

Error Code = OBJECT_ACCESS_UNSUPPORTED

Additional Code

INVALID_KIND_OF ACCESS (5)

Incorrect "Kind of Access" parameter

INVALID_KIND_OF_VARIABLE (8)

Incorrect "Kind of Variable" parameter

__________________________________________________________________________________________

9 / 7

__________________________________________________________________________________________

Error Class = APPLICATION_REFERENCE

Error Code = CONTEXT_UNSUPPORTED

One of the CBB parameters used in the Read_Response (STR1, STR2, VALT, ...) parameter was not negociated when the association was first opened

Additional Code = (local error returned by MMS provider)

MM_041_MAX_NEST_EXCEEDED (41)

MM_042_VNAM_CBB_VIOL (42)

MM_043_VADR_CBB_VIOL (43)

MM_046_VALT_CBB_VIOL (46)

MM_049_STR1_CBB_VIOL (49)

MM_050_STR2_CBB_VIOL (50) d. Procedure

The OSI module MMS Server uses the following operations to process the service:

• Access in the OSI module to the named variables table of symbols,

• Tr ans missi on of t he UNI-TE R EAD _SYSTEM _BI T (for s yst em bits),

READ_SYSTEM_WORD (for system words) or READ_OBJECTS (for all other objects) to the PLC.

For "Programmed" variables, the UNI-TE request is only sent if an access authorization has been sent previously by an MSEMA OFB. If this is not the case, the MMS service will await execution. Communication on this association is then interrupted until the access authorization is received.

__________________________________________________________________________________________

9 / 8

Variable Access Services 9

__________________________________________________________________________________________

9.4

Write Service

9.4-1 MMS Client Mode

This service is used by the PL7-3/MMS application to modify one or more remote MMS application variables.

a. Argument

Variable Access Specification

This parameter is described in Divider A, Sub-section 9.1-1.

List of Data

This parameter contains the list of values to write (up to 4 values of variables).

b. Result(+)

List of Write Result

For each variable, this parameter indicates that the write was successful or the cause of failure.

Success = TRUE or FALSE

Data Access Error (if Success = FALSE)

Refer to the MMS standard for the error codes used.

A c. Result(-)

Refer to the MMS standard.

All error types are returned to the PL7-3/MMS application.

__________________________________________________________________________________________

9 / 9

__________________________________________________________________________________________

9.4-2 MMS Server Mode

This service is used by an MMS user to request that the MMS Server modify the values of one or more variables assigned to the VMD (the TSX Series 7 station), the DOMAIN

(the .APP station application) or to the AA association.

a. Argument

Variable Access Specification

This parameter is described in Divider A, Sub-section 9.1-1.

List of Data

This parameter contains the list of values to write (up to 16 values of variables).

b. Result(+)

List of Write Result

For each variable, this parameter indicates that the write was successful or the cause of failure.

Success = TRUE or FALSE

Data Access Error (if Success = FALSE)

Refer to the MMS standard for the error codes used.

c. Result(-)

Error Class = ACCESS

Error Code = OBJECT_ACCESS_UNSUPPORTED

__________________________________________________________________________________________

9 / 1 0

Variable Access Services 9

__________________________________________________________________________________________

Additional Code

INVALID_KIND_OF ACCESS (5)

Incorrect "Kind of Access" parameter

Error Class = OTHERS

Error Code = WRITE

Additional Code

DATA_VAR_SPEC_MISMATCH (1)

The number of variables does not correspond to the nbr. of data objects to write

A d. Procedure

The OSI module MMS Server uses the following operations to process the service:

• Access in the OSI module to the named variables table of symbols,

• Transmis sion of th e UNI- TE W RITE_SYSTEM _BIT ( for sy stem bits),

WRITE_SYSTEM_WORD (for system words) or WRITE_OBJECTS (for all other objects) to the PLC.

9.5

InformationReport Service

9.5-1 MMS Client Mode

This service is used by the PL7-3/MMS application to receive an unsolicited variable from a remote MMS application.

This service is not confirmed.

a. Argument

Variable Access Specification

This parameter is described in Divider A, Sub-section 9.1.

List of Access Result

Contains the list of values for the expected variable.

__________________________________________________________________________________________

9 / 1 1

__________________________________________________________________________________________

9.5-2 MMS Server Mode

This service lets the MMS Server send one or more unsolicited variables to a remote

MMS application.

This service is not confirmed.

a. Argument

Variable Access Specification

This parameter is described in Divider A, Sub-section 9.1-1.

List of Access Result

Contains the list of values for the expected variable.

9.6

GetVariableAccessAttributes Service

This service is used by an MMS user to request that the MMS Server return the attributes of a variable.

This service is only supported in MMS Server mode.

a. Argument

Kind of Variable = NAMED or UNNAMED

This parameter indicates whether a named or unnamed variable is selected.

Name

Address

These parameters are described in Divider A, Sub-section 9.1-1.

__________________________________________________________________________________________

9 / 1 2

Variable Access Services 9

__________________________________________________________________________________________ b. Result(+)

MMS Deletable = FALSE

These variables cannot be deleted.

Address

Specifies the address of the PUBLIC variable.

Type Specification

Describes type of variable, for a description of types refer to Sub-section 3.4-4.

A c. Result(-)

Error Class = ACCESS

Error Code = OBJECT_ACCESS_UNSUPPORTED

Additional Code

INVALID_OBJECT_SCOPE (3)

Incorrect "Name Scope" parameter

INVALID_ADDRESS (7)

Incorrect "ADDRESS" parameter

Error Code = OBJECT_NON_EXISTENT

Additional Code

DOMAIN_NON_EXISTENT (2)

Designated domain does not exist

VARIABLE_NON_EXISTENT (4)

Designated variable does not exist

Error Class = VMD_STATE

Error Code = VMD_STATE_CONFLICT

Additional Code

TEMPORARILY_UNAVAILABLE (1)

Cannot access table of symbols

__________________________________________________________________________________________

9 / 1 3

__________________________________________________________________________________________ d. Procedure

The OSI module MMS Server uses the following operations to process the service:

• For a named variable, access in the OSI module to the named variables table of symbols.

__________________________________________________________________________________________

9 / 1 4

Appendix 10

__________________________________________________________________________________________

10.1 Error Codes

General error codes

These error may be received with negative responses to a number of different services:

Error_Class = SERVICE_PREEMPT

Error_Code = TIMEOUT

The PLC does not answer.

Error_Class = RESOURCE

Error_Code = MEMORY_UNAVAILABLE

Insufficient memory resources available to process the message.

Error_Class = VMD_STATE

• Error_Code = VMD_OPERATIONAL_PROBLEM

The PLC has refused a message (internal message system problem).

• Error_Code = VMD_STATE_CONFLICT

- Additional_Code = TEMPORARILY_NON_EXECUTABLE (2)

The PLC state will not allow the service to be executed immediately (PLC already reserved, table of symbols being downloaded, etc.)

- No Additional_Code

The service cannot be executed as the PLC status will not allow it (reservation lost, inability to access PLC status, etc.).

Specific error codes

These error codes may be received in specific cases (on rece ption of

Download_Segment.ind or Terminate_Download_Sequence.ind, that are not supported in Client mode).

Error_Class = APPLICATION_REFERENCE

Error_Code = CONTEXT_UNSUPPORTED

Additional_Code = CLIENT_DOWNLOAD_UNSUPPORTED (256)

Downloading is not supported in MMS Client mode.

__________________________________________________________________________________________

1 0 / 1

__________________________________________________________________________________________

Codes

Error_Class = VMD_STATE

• Error_Code = VMD_STATE_CONFLICT

TEMPORARILY_UNAVAILABLE

TEMPORARILY_NON_EXECUTABLE

• Error_Code = VMD_OPERATIONAL_PROBLEM 2

• Error_Code = DOMAIN_TRANSFER_PROBLEM 3

INCONSISTENT_DATA

UPLOAD_NON_FINISHED

WRITE_SEG_IMPOSSIBLE

READ_DATA_SEGMENT_IMPOSSIBLE

DOWNLOAD_IMPOSSIBLE

Value Description

Access to variables is impossible as the table of symbols is being downloaded.

The service is temporaily non executable.

Incoherent downloaded data.

Upload interrupted prior to completion.

Cannot write data to the PLC.

Cannot read data from the

PLC.

Download operation refused by the PLC.

Error_Class = APPLICATION_REFERENCE

• Error_Code = CONTEXT_UNSUPPORTED

MM_041_MAX_NEST_EXCEEDED

MM_042_VNAM_CBB_VIOL

MM_043_VADR_CBB_VIOL

MM_046_VALT_CBB_VIOL

MM_049_STR1_CBB_VIOL

MM_050_STR2_CBB_VIOL

CLIENT_DOWNLOAD_UNSUPPORTED

256

Contents of Read_Response incompatible with the parameters negociated when the association was opened.

Downloading not supported in Client mode.

Error_Class = DEFINITION

• Error_Code = OBJECT_UNDEFINED

INVALID_DOMAIN_NAME

DOMAIN_UNDEFINED

PI_UNDEFINED

INVALID_PI_NAME

• Error_Code = OBJECT_EXISTS

DOMAIN_ALREADY_EXIST

PI_ALREADY_EXIST

Incorrect domain name.

Domain does not exist.

PI does not exist.

Incorrect PI name.

The domain already exists.

The PI already exists.

__________________________________________________________________________________________

1 0 / 2

Appendix 10

__________________________________________________________________________________________

Codes

Error_Class = RESOURCE

• Error_Code = MEMORY_UNAVAILABLE

Value

Description

Not enough memory available to execute the service.

Error_Class = SERVICE 4

• Error_Code = PRIMITIVES_OUT_OF_SEQUENCE 1 Incorrect sequencing of archive storage primatives.

• Error_Code = OBJECT_STATE_CONFLICT

DOMAIN_NOT_DELETABLE

INVALID_DOMAIN_STATE

INVALID_PI_STATE

PI_NOT_DELETABLE

UPLOAD_IN_PROGRESS

UPLOAD_IMPOSSIBLE

• Error_Code = CONTINUATION_INVALID

The "Deletable" attribute in the domain takes the value

FALSE.

The state of the domain does not allow service execution.

The state of PI does not allow service execution.

The "Deletable" attribute in the PI takes the value FALSE.

The uploading in progress inhibits service execution.

Uploading is impossible as the PLC application is protected.

The "Continue After" parameter is GetNameList.req is invalid.

Error_Class = SERVICE_PREEMPT

• Error_Code = TIMEOUT

1 The PLC does not respond to the requests sent to it.

Error_Class = ACCESS 7

• Error_Code = OBJECT_ACCESS_UNSUPPORTED 1

INVALID_EXTENDED_OBJECT_CLASS 1

INVALID_OBJECT_CLASS 2

"Extended_Object_Class" or "Object_Class" parameters in

GetNameList.req are invalid as they are not supported.

INVALID_OBJECT_SCOPE 3 The "Scope" parameter in

GetNameList.req or in

GetVarAccessAttributes.req

is invalid as it is not supported.

__________________________________________________________________________________________

1 0 / 3

__________________________________________________________________________________________

Codes

INVALID_KIND_OF_ACCESS

INVALID_ADDRESS

INVALID_KIND_OF_VARIABLE

EXEC_ARGUMENT_UNSUPPORTED

Value Description

The value of the "Kind of Access" parameter in a

Read.req or a Write.req is not supported.

The value of the "Address" parameter in Get Var Access

Attributes is not supported.

The value of the "Kind of

Variable" parameter in Get

Var Access Attributes is not supported.

The "Exec Argument" parameter in a Start.req or a

Resume.req is not supported.

• Error_Code = OBJECT_NON_EXISTENT

INVALID_DOMAIN_NAME

DOMAIN_NON_EXISTENT

PI_NON_EXISTENT

VARIABLE_NON_EXISTENT

USLM_NON_EXISTENT

Incorrect domain name.

Domain does not exist.

PI does not exist.

Variable does not exist in the table of symbols.

Machine to upload to does not exist.

Error_Class = CONCLUDE

• Error_Code = FURTHER_COMMUNICATION_

REQUIRED

1 Association cannot be closed by Conclude as communication is still in progress.

Error_Class = Others

• Error_Code = DATA_CODED

1 The downloaded data is in coded format.

• Error Code = WRITE_CLASS

DATA_VAR_SPEC_MISMATCH

1 The number of variables is different from the number of data objects in the Write request.

• Error_Code = INITIATE DOWNLOAD_SEQ

INVALID_SHARABLE_ATTRIBUTE

2 The "Sharable" attribute in the domain has the value

True.

These error codes given as a • Service Specific Information =

<Program Invocation State> response to program management requests take the value of the PI state defined in the MMS standard.

__________________________________________________________________________________________

1 0 / 4

________________________________________________________

Set-Up and Methodology B

___________________________________________________________________________

Page B

Presentation and Set-Up

1.1

General

1.1-1 Features Supported by PL7-OSI 3.0

1.2

Configuration Required for PL7-OSI 3.0

1.3

Checking the Hardware

1.4

Connection

1.5

Installing the Software

1.5-1 Initial Preparations

1.5-2 Installation Procedure

1.6

Rules for Access

__________________________________________________________________________________________________

Methodology

2.1

Methodology Proposal for Setting-up an Application 2/1

2.1-1 Device Addresses

2.1-2 Communication Layout

2.1-3 List of MMS Variables

2.1-4 List of MMS Services Used for Each Association

2.1-5 General Methodology

2.1-6 PL7-OSI Application Design Methodology

2.1-7 PL7-MMS Application Design Methodology

2.1-8 PL7-3 Application Design Methodology

2/2

2/3

2/4

2/5

2/6

2/7

2/8

1/1

1/2

1/3

1/4

1/6

___________________________________________________________________________

B / 1

___________________________________________________________________________

B / 2

Presentation and Set-Up 1

__________________________________________________________________________________________

1.1

General

This manual describes the set-up and operation of the PL7-OSI 3.0 software

(ref. TXT L SSP30 V5E) on a terminal with OS/2 (version 1.2 minimum) and the X-TEL

Software Workshop installed. These terminals can be:

• FTX 507,

• IBM PS/2 or Compatible microcomputer with a 80386 or better microprocessor.

This program is used to design and operate applications that require the use of

TSX ETH 200 OSI interface modules.

1.1-1 Features Supported by PL7-OSI 3.0

Setting-up PLCs to use an OSI network requires:

• Selecting a communication profile common to all devices (the OSI stack) and uploading this profile to the communication modules,

• Selecting the network operating parameters and loading the corresponding configuration into the interface modules,

• Selecting MMS variables available to the network from the variables available to a device.

These features are supported in PL7-OSI 3.0 by five software sub-sets:

• PL7-OSI supports, for each station:

- Assistance with configuration parameter entry, via menus and on-line help and documentation features,

- Assistance with debugging,

- Configuration transfer between the PLC memory, the module memory and disk storage,

- Configuration documentation,

- Configuration storage to disk,

- Configuration information print-out.

• PL7-MMS supports, for each station:

- Entry of MMS symbols visible to client stations on the network,

- Transfer of selected symbols between the PLC memory and the disk,

- Documentation of the MMS symbol data base,

- Database storage to disk,

- Database print-out.

__________________________________________________________________________________________

1 / 1

__________________________________________________________________________________________

• OSI-LOADER supports configuration and execution of the communication profile uploading, via the programming port, to TSX ETH 200 modules connected to an 802.3

standard netwok.

• OFB MMSLD, a PLC operating system extension, automatically loads OSI parameters and the table of MMS symbols into the network interface module each time this is required.

• MMS OFB library, a set of OFBs that perform MMS services (Read/Write Variables,

Device control, etc.) for PLC stations connected to the network.

1.2

Configuration Required for PL7-OSI 3.0

The PL7-OSI 3.0 program is designed to run on FTX 507 terminals or IBM PS/2 or compatible PCs with the following systems installed:

• OS/2 (version 1.2 minimum) Operating System,

• X-TEL Software Workshop (ref. TXT L BASE V5),

• PL7-NET (ref. TXT L PL7 NET V5E), to build a network layout and use the

OSI-LOADER function of PL7-OSI 3.0 from the X-TEL Software Workshop,

• PL7-3 software for programming the application for each network station.

This means that the system requires at least 4 Mbytes of RAM memory installed and

40 Mbytes of hard disk space available).

Important

Telemecanique cannot guarantee correct operation of this software on all microcomputers or compatible PCs on the market with the above-mentioned characteristics.

1.3

Checking the Hardware

The TXT L SSP 30 V5 software package comprises:

• A 3 1/2" diskette, ref. TXT LF SSP V5,

• A 3 1/2" diskette, ref. TXT LF MMS V5,

• A 3 1/2" diskette, ref. TXT LF STK V5,

• A 3 1/2" diskette, ref. TXT LF FB SSP V5,

• A software protection key module,

• A program license contract,

• This documentation set, ref. TXT DM SSP V5E.

__________________________________________________________________________________________

1 / 2

Presentation and Set-Up 1

__________________________________________________________________________________________

To use the PL7-OSI 3.0 software, the user requires the following hardware:

• An FTX 507 terminal or an IBM PS/2 or compatible PC (refer to the required configuration described in Sub-section 1.2),

• A terminal/PLC connection cable when an FTX 507 terminal is used,

• If an IBM PS/2 or compatible PC is used, a TSX TAC 03) terminal/PLC connection kit is required, comprising:

- An RS-232C/ Current Loop converter,

- A Converter/PC connection cable with a 9-pin connector,

- A Converter/PC connection cable with a 25-pin connector,

• If an IBM PS/2 or compatible PC is TSX SCC 02 key module holder.

Only a V4.4 level or higher TSX 47, 67, 87 or 107-40 PLC must be used.

1.4

Connection

The connections that are specific to the terminal (monitor, keyboard, mouse, printer, key module holder, etc.) are assumed to have already been made according to the documentation supplied by the terminal manufacturer. This sub-section only describes the fitting of the software key module.

To do this, insert the software key into the vacant slot in the software key module holder.

This operation must always be performed with the terminal powered-down.

Note:

The software key module contains the right of use required to run the PL7-PMS program. The Key

Manager supplied with the X-TEL Software Workshop lets the user transfer this right of use to the

Work Key Module so that only a single key is required (work key) once again releasing a slot in the key module holder.

For more information on the use of the Key Manager, refer to the X-TEL Software Workshop documentation (ref. TXT DM XTEL V5E), Divider C Section 9.

__________________________________________________________________________________________

1 / 3

__________________________________________________________________________________________

1.5

Installing the Software

1.5-1 Initial Preparations

Before installing the PL7-OSI 3.0 program on the hard disk, always:

• Read the licence and guarantee certificates that give the conditions of use and detail the restrictions that apply to copying and installing this program,

• Make a copy of the diskettes required for installation and only use this copy to avoid accidental damage to the original diskette.

Important

The PL7-OSI 3.0 program diskettes are supplied write protected. Do not change the position of the write protect tab on these diskettes.

1.5-2 Installation Procedure

The following operations should be performed before installing the PL7-OSI 3.0

program:

• Check that the X-TEL Software Workshop is already installed:

• If so, install PL7-OSI 3.0 following the installation procedure described below,

• Otherwise, first install the X-TEL Software Workshop (refer to the X-TEL documentation (TXT DM XTEL V5E) Divider B Sub-section 5.

• Close all work sessions in progress.

PL7-OSI 3.0 Program Installation

1 Open an OS/2 full screen session,

2 Insert the PL7-OSI 3.0 diskette, TXT LF SSP V5 into the diskette drive,

3 Type the drive identification letter (a: or b:) where the diskette is located and press

<Enter> to confirm,

4 Follow the prompts displayed on-screen,

Once the installation procedure is completed, remove the program diskette and insert the next diskette, TXT LF MMS V5 into the diskette drive,

__________________________________________________________________________________________

1 / 4

Presentation and Set-Up 1

__________________________________________________________________________________________

6 Type Install again, then press <Enter> to confirm,

7 Follow the procedure displayed on-screen,

8 Repeat the above procedure to install diskettes TXT LF STK 30 V5 and

TXT LF FB SSP V5,

9 Once the installation procedure for these four diskettes is completed and this is the last installation to perform, run the configuration check. Press <Enter> to confirm,

& Remove the diskette from the drive and return to the X-TEL Software Workshop by pressing <Ctrl><Esc>.

__________________________________________________________________________________________

1 / 5

__________________________________________________________________________________________

1.6

Rules for Access

PL7-MMS and PL7-OSI programs are accessed by opening the "Tools" window for the

Station where data will be modified. To do this:

1 Select the Telemecanique item from the desktop and double click on it to confirm the selection,

Open the user window by double clicking on the XTEL item,

3 Enter the user identification information r equired (user's name and password), then select <Enter> to confirm. The Volumes window will be displayed,

4 Open a Volume by double clicking on the icon for the required volume in the application,

5 Open a Project by double clicking on the icon for the required project in the application,

6 Open a Station by double clicking on the icon for the station where variables will be configured,

7 Follow the procedure displayed on-screen,

Open the window for the required function: PL7-MMS or PL7-OSI by double clicking on its icon. If the icon is not present in the Functions secondary window even if the program was previously installed, then the function was not defined for this station.

If so, proceed as follows:

• Pull-down the Define menu and select New,

• Click on MMS or OSI in the list of functions available and confirm the selection made,

9 For improved ease of use, enlarge the PL7-MMS or PL7-OSI window by clicking on the Maximize arrow in the top right of the screen.

__________________________________________________________________________________________

1 / 6

Methodology 2

__________________________________________________________________________________________

2.1

Methodology Proposal for Setting-up an Application on a TSX/PMX PLC Connected to an OSI Network

The methodology proposal described here is designed to assist the user during the generation, debug, storage and documentation phases of application development. As this is a methodology example only, the various operations are described without detailing the operating modes required. For more information, refer to Divider H.

Important: The user must load the OSI Stack into the TSX ETH 200 modules using

OSI-LOADER. This operation is only performed once, the OSI Stack is then stored in the interface module memory.

The failure LED will blink until the stack is loaded (refer to the TSX ETH 200 Interface

Module User's Manual).

FTX 507

ETHERNET

APRIL R6S0

APRIL 7000

TSX 7

R6S1

TSX 7

__________________________________________________________________________________________

2 / 1

__________________________________________________________________________________________

2.1-1 Device Addresses

Device XWAY Network/ MMS Address

Station Address

R6S0 06/00 R6S0_MMS

00000001

0001

Application name

PSEL

SSEL

TSEL

4954454C454D4543412E060001 NSAP

_______________________________________________________________________________________

R6S1 06/01 R6S1_MMS

00000001

0001

Application name

PSEL

SSEL

0001 TSEL

4954454C454D4543412E060101 NSAP

_______________________________________________________________________________________

APRIL APRIL_S1C

00000001

0000

0101

Application name

PSEL

SSEL

TSEL

4954454C454D4543412E060101 NSAP

_______________________________________________________________________________________

APRIL APRIL_S1S

00000002

0000

Application name

PSEL

SSEL

0101 TSEL

4954454C454D4543412E060101 NSAP

_______________________________________________________________________________________

__________________________________________________________________________________________

2 / 2

Methodology 2

__________________________________________________________________________________________

2.1-2 Communication Layout

R6S0

R6S1

APRIL B

C0 = association open by R6S0 to R6S1

C1 = association open by R6S1 to R6S0

C0 = association open by R6S1 to APRIL

C0 = association open by APRIL to R6S1

2.1-3 List of MMS Variables

Refer to the detailed description in the example in the Appendix.

R6S0_MMS

MT5_W50

MD_W120

MABIT_50

MADW_200

R6S1_MMS

MT5_W50

MBIT_B10

MMOT_W100

MT250_DW1000

MT_500W

MUMOT_W15

US_X900

VOITURE

VSTRING

APRIL_S1C

RUN_API

__________________________________________________________________________________________

2 / 3

__________________________________________________________________________________________

2.1-4 List of MMS Services Used for Each Association

R6S1 APRIL

Association

MMS Service

INITIATE

WRITE

READ (2 times)

INFO REPORT (2 fois)

STATUS

UNSOL.STATUS

CONCLUDE/ABORT

R6S0

INITIATE

WRITE

READ (2 times)

CONCLUDE/ABORT

INITIATE

INFO REPORT

READ

CONCLUDE/ABORT

INITIATE

READ

IDENTIFICATION

WRITE

READ

CONCLUDE/ABORT

__________________________________________________________________________________________

2 / 4

Methodology 2

__________________________________________________________________________________________

2.1-5 General Methodology

▲

Program Installation

XTEL-CONF

TSX/PMX V5 Stations

Define the I/O

Parameter the Application

TSX/PMX V4 Stations

Build the Application

Layout

XTEL-MEM

PL7-OSI

PL7-MMS

Enter the Addresses of Applications in the Layout:

Create the OSI Directory see note 1 see note 2

Enter MMS Variables for

Applications in the Layout:

Create the MMS Directory

OFF-LINE

Application

Design

PL7-OSI

Application

Design

PL7-MMS

Application

Design

PL7-3+OFB MMS

TSX/PMX V5 Stations TSX/PMX V4 Stations

Build the PLC

Application

XTEL-MEM

▼

▲ > see

Note 3

Transfer to PLC

PL7-3

Debug Mode

Debug the

Application

Update

Application File

Documentation File

Debug the

OSI Modules

Update

Application File

Documentation File

PL7-OSI

ON-LINE

▼

__________________________________________________________________________________________

2 / 5

__________________________________________________________________________________________

Note 1:

Refer to the OSI-PRJ directory entry function, Divider D, Sub-section 3.1-2.

In the example, the OSI-PRJ directory contains the names of the R6S0_MMS, R6S1_MMS,

APRIL_S1C applications with the corresponding addresses.

Refer to the device address tables.

These entries are performed once for all of the stations in the project.

Note 2:

Refer to the MMS directory editing function, Divider E, Sub-section 3.1.

In the example, the MMS directory contains the names of the MMS variables with their detailed characteristics (scope, type, length).

Refer to the list of MMS variables table.

These entries are performed once for all of the stations in the project.

Note 3:

All of these operations must be performed for each station.

_______________________________________________________________________________________

2.1-6 PL7-OSI Application Design Methodology

OSI

Directory

Define Remote

MMS Varaibles

Define Local

MMS Variables (1)

Generate the

MMS Configuration (2)

Design

PL7-MMS

Application

Download the

PLC Memory (3)

Document the

Application (4)

(1) Div. E S-Sect. 3.2/3.3

see Note 5

(2) Div. E S-Sect. 3.4

(3) Div. E S-Sect. 4.1

(4) Div. E Sect. 5

(5) Div. E S-Sect. 3.2

TSX/PMX V5 Stations TSX/PMX V4 Stations

Integrate .BIN into the Application File (5)

Possible update of other Applications if the MMS-PRJ

Directory is Modified

Note 5:

In the example, the MMS MBIT_BIO variable is a local variable for the R6S1_MMS application and a remote variable for the R6S0-MMS application.

__________________________________________________________________________________________

2 / 7

__________________________________________________________________________________________

2.1-8 PL7-3 Application Design Methodology

Integrate the MMSLD

OFB in PL7-3

PL7-3

Configuration Mode

Program the

Application

PL7-3

Programming Mode

Conception

Application

PL7-3

PL7-3 .BIN Files

Document the

Application

STATION .DOC File

TSX/PMX V5 Stations

Store and

Integrate the Application

File (STORE)

TSX/PMX V4 Stations

Integrate .BIN

into the

Application

STATION .BIN

and

STATION .APP Files

__________________________________________________________________________________________

2 / 8

________________________________________________________

OSI-LOADER C

___________________________________________________________________________

General

1.1

Program Functions

Page

1/1

__________________________________________________________________________________________________

OSI-LOADER

2.5-1 Selecting an Operating File

2.5-2 Editing an Operating File

2/1

2/2

2/3

2/4

2/5

2/9

2/10

2/11

2/12

___________________________________________________________________________

C / 1

___________________________________________________________________________

C / 2

General 1

__________________________________________________________________________________________

1.1

Program Functions

To connect a TSX Series 7 PLC to an OSI/MMS network, the communication interface module installed in the PLC must comprise OSI/MMS software.

This program is loaded in the TSX ETH 200 modules by OSI-LOADER, a project level tool in the X-TEL Software Workshop.

__________________________________________________________________________________________

1 / 1

__________________________________________________________________________________________

1 / 2

OSI-LOADER 2

__________________________________________________________________________________________

2.1

Program Presentation

OSI-LOADER is a project level tool, a part of the PL7-OSI 3.0 software package

(ref. TXT L SSP30 V5).

This program lets the user configure and execute an upload to the TSX ETH 200 modules of the OSI-MMS executable program.

It is only used in an 802.3 (ETHERNET) type network environment.

The configuration procedure covers generating an xxx.EXP operating file containing the description of the stations to load. The actual upload procedure transfers the OSI-MMS program to the stations defined in the operating file (xxx.EXP).

2.2

Requirements for Running OSI-LOADER

OSI-LOADER in the X-TEL Software Workshop environment requires that PL7-NET be installed and that the ETHERNET network that OSI-LOADER will load to be defined.

For more information on PL7-NET operation, refer to the specific User's Manual for this tool.

2.3

Program Functions

The main OSI-LOADER functions are:

Operating file configuration

Creation and modification of an xxx.EXP operating file that defines the stations that

OSI/MMS is uploaded to.

Loading stations

Uploading to the stations defined in the xxx.EXP operating file.

Deleting files

Deleting previously generated xxx.EXP operating files.

__________________________________________________________________________________________

2 / 1

__________________________________________________________________________________________

2.4

Selecting the OSI-LOADER Program

The OSI-LOADER program is run by opening the OSI-LOADER window under the project in which the stations will be loaded. To do this:

1 Open the Desktop Manager window by double clicking on its icon and select the

Telemecanique option by double clicking on its icon,

2 Open the user window by double clicking on XTEL or use the XTEL Browser,

3 Enter the appropriate user parameters (user name and password) and validate so that the Volumes window is displayed,

Open a Volume by double clicking on the icon of the appropriate application volume,

5 Open a Project by double clicking on the icon of the project in the application or use the XTEL Browser,

6 Open the OSI-LOADER window by double clicking on its function icon. If the icon is not displayed in the Project Tools secondary window, even after the program has been installed, then the function has not yet been defined in the project. To define the function:

• Pull down the Define menu and select New,

• Click on OSI-LOADER, in the list of functions available, then validate the selection made,

For greater visual comfort, select a full screen OSI-LOADER session by clicking on the Maximize icon in the top right corner of the window.

Primary Window

__________________________________________________________________________________________

2 / 2

OSI-LOADER 2

__________________________________________________________________________________________

Diagram

Configuration Load Utilities Exit Help

Generate… Load… View…

Delete...

Operating File [EXP]…

Configuration

Load

Create and modify an xxx.EXP file

Transfer the OSI-MMS program to the stations configured in an operating file

Utilities

Exit

Help

View and delete an operating file

Quit OSI-LOADER

Calls-up on-line help

2.5

Generating an Operating File - Configuration Menu

The Configuration menu lets the user create or modify an operating file (xxx.EXP). The operating file downloads the OSI Stack to the stations.

Depending on whether the xxx.EXP filename specified when the function was selected, corresponds to an existing file or a new file, this file will be created or modified.

The sequence of actions to perform to create or modify an xxx.EXP file is shown below:

1 Specify the name of an operating file,

2 Enter (or modify) a list of stations to upload. Each station in the list is defined in a structured approach by:

• The network it is connected to,

• Its station name, taken from the list of stations previously defined for the selected network,

• The location of the TSX ETH 200 module in the station PLC rack,

• The type of OSI-MMS profile to use.

3 Save the operating file (xxx.EXP).

__________________________________________________________________________________________

2 / 3

__________________________________________________________________________________________

2.5-1 Selecting an Operating File

After selecting Configuration, then Generate, the dialog box shown below is displayed:

This screen displays:

• A File Name field that displays the operating file name with an .EXP extension, that will be created or modified when a Save is performed.

• A list of known operating files (items) available to for project.

• OK, Cancel and Help buttons.

The filename can be entered by:

• Clicking on the data entry field and typing the file name directly from the keyboard.

• Selecting a file from the list of operating files available for the project, using the following procedure:

- Double clicking on the file to select,

- Highlighting the file to select using the Cursor Keys and pressing <Enter> to confirm the selection made.

A filename will always be displayed by default in the window, according to the following rules:

- If there is no operating file, the default filename is the project name followed by an

.EXP extension,

- Otherwise, the name of the first file in the list is displayed in this field.

Cancel

Help

Calls-up a screen allowing the user to edit the contents of the operating file.

Cancels the configuration action.

Displays on-line help on generating operating files.

__________________________________________________________________________________________

2 / 4

OSI-LOADER 2

__________________________________________________________________________________________

2.5-2 Editing an Operating File

Once a filename selection is confirmed, the following screen is selected:

This screen will list the various stations defined in the previously selected operating file.

The Edit functions are selected using the buttons located at the bottom of the screen.

There are two possible cases:

• If the filename does not correspond to an existing filename and the list displays no existing station; then Create is selected,

• Otherwise, the list will display all of the stations already defined for this file; then Modify is selected. Each station in the list is identified by three components: the network name, the station name and the OSI-MMS profile designation.

Add

Delete

Cancel

Exit

Starts the definition procedure for a new station, calling-up a sequence of four dialog boxes.

These dialog boxes allow the user to select, in sequence, the network name, station name on the network, the module location and finally the OSI-MMS profile designation.

Deletes a station from the list.

Saves the modifications made (generates the operating file).

Cancels the Edit function and returns the user to the previous screen.

Exit the operating file configuration function and returns the user to the OSI-LOADER action bar.

__________________________________________________________________________________________

2 / 5

__________________________________________________________________________________________

Adding a station to the list

Preliminary remark:

Establishing an upload configuration is equivalent to making a list of stations to load, that are known to a previously defined 802.3 network. Therefore to use OSI-LOADER, it is essential to first define the network layout.

To do this, PL7-NET must be installed and the network must have been defined in the

Networks secondary window within the currently developed Project.

Given these requirements, one of the error messages listed below may be displayed when the user confirms the modifications made by selecting Add:

Message:

Description:

Message:

Description:

"No valid network defined for this project"

No network is defined, or the network defined is not an 802.3 type.

"No valid station defined for this network"

A valid network has been defined, but no station is "connected" in the network layout definition.

If the definition of the network layout is correct, it is possible to add a station to the list.

As described above, the station is described by the network name, the station name, the interface module location (or module number) and the OSI-MMS profile to load. These four parameters are selected successively, via four dialog boxes.

The procedure is the same for each of the four dialog boxes, make a selection from a list displayed and confirm the selection made. Once this is done a dialog box is displayed. This procedure is repeated until the profile selection is complete. Confirming the last selection, returns the user to the configuration screen. The newly defined station is displayed at the end of the list.

__________________________________________________________________________________________

2 / 6

OSI-LOADER 2

__________________________________________________________________________________________

The four dialog boxes comprise the same four buttons:

OK Confirms the selection made and opens the next window (except when the Profiles window is opened, as this is the last screen and confirming the selections made in the profiles window returns the user to the Configuration screen).

Cancel

Exit

Cancels the action and returns the user to the previous screen.

Exits the configuration function and returns the user to the

OSI-LOADER action bar.

Help Displays a help screen for the current selection (network, station, module or profile).

The four screens are illustrated below:

__________________________________________________________________________________________

2 / 7

__________________________________________________________________________________________

Remarks on the profile selection dialog box:

• This dialog box summarizes the three previous selections (network, station and module).

• In the current version, only one OSI-MMS profile is available: The MMS-IS profile.

__________________________________________________________________________________________

2 / 8

OSI-LOADER 2

__________________________________________________________________________________________

2.6

Loading Stations Defined in an Operating File

To load a set of stations, simply select the previously configured operating file, from the open dialog box and confirm the selection made.

OK Loads the stations defined in the file specified in the File Name field, once the user has confirmed the request.

__________________________________________________________________________________________

2 / 9

__________________________________________________________________________________________

2.7

Viewing Operating Files

To view an operating file, simply select the file name from the list of files displayed in the dialog box shown below and confirm the selection:

Cancel

Displays the .EXP file view screen.

Cancels the action, no file is displayed and the user is returned to the primary window.

The operating file is viewed in its original format. The user can scroll its contents using the vertical scroll bars. The Cancel button lets the user exit the View mode and return to the OSI-LOADER primary window.

__________________________________________________________________________________________

2 / 1 0

OSI-LOADER 2

__________________________________________________________________________________________

2.8

Deleting Operating Files

To delete an operating file, simply select the file name from the list of files displayed in the dialog box shown below and confirm the selection:

Cancel

Deletes the file whose name is shown in the "File Name to Delete" field, once the user has confirmed the request.

If the filename is invalid, the message

"No file selected, or filename entered does not exist!" is displayed.

Cancels the action, no files are deleted.

__________________________________________________________________________________________

2 / 1 1

__________________________________________________________________________________________

2.9

Help

The Help item in the pulldown menu lets the user access the OSI-LOADER help screens from the root directory.

The About... item in the pulldown menu displays:

__________________________________________________________________________________________

2 / 1 2

________________________________________________________

PL7-OSI D

___________________________________________________________________________

Section Page

__________________________________________________________________________________________________

General

1.1

Presentation

1.2

PL7-OSI Objectives

1.3

PL7-OSI Functions

1.4

Accessing PL7-OSI

1/1

1/2

1/3

__________________________________________________________________________________________________

Selecting the Working Memory - Memory Menu

2/1

__________________________________________________________________________________________________

Configuring the Station - Configuration Menu

3.1-1 Project Directory Description

3.1-2 OSI_PRJ Directory Entry Function

3.1-3 OSI_PRJ Directory Restore Function

3.1-4 OSI_PRJ Directory Save Function

3/1

3/2

3/4

3/6

3/7

3.2-1 Selecting and Generating the Module File (xxx.CPL)

3.2-2 Setting OSI Layer Parameters

3.2-3 Defining the Local Application

3.2-4 Selecting Remote Applications

3.3-1 Creating an OSI.BIN File

3.3-2 Modifying and Viewing an OSI.BIN File

3/8

3/11

3/12

3/14

3/16

3/17

3/19

__________________________________________________________________________________________________

Transferring Binary and Module Files - Transfer Menu

4/1

4/3

4/4

4/6

___________________________________________________________________________

D / 1

___________________________________________________________________________

Page

Documenting and Printing

5.1

Generating Documentation

5.2

View

5.3

5.4

Enter Information

5.5

Documenting a Module

Deleting Files - Configuration Set-Up - Help

6/1

6/2

6.3 Restoring/Saving the OSI.BIN File 6/4

_______________________________________________________________________________

6.3-1 Restore

6.3-2 Save

6/4

6/5

6.4

Help 6/6

5/1

5/2

5/3

5/6

Appendix

Directory File Format 7/1

___________________________________________________________________________

D / 2

General 1

__________________________________________________________________________________________

1.1

Presentation

PL7-OSI is a Station level function tool, a sub-set of the PL7-OSI 3.0 program. It is run in the X-TEL Software Workshop environment.

Program functions are shared between two components:

• The network interface module configuration and documentation program, designed to run on an FTX 507 station with the X-TEL Software Workshop,

• The PL7-3 Optional Function Blocks (OFBs) that are run on TSX and PMX Series 7

PLCs.

The following sections describe the functions and operating modes of the network configuration program.

The OFB program is described separately in Divider F.

1.2

PL7-OSI Objectives

PL7-OSI lets the user design and load an OSI configuration for every TSX ETH 200 network interface module in a station.

The configuration of an OSI interface module requires the definition of three sub-sets of data:

• The OSI layer parameters,

• The definition of the single local application corresponding to the PL7-3/MMS application implemented on the station,

• The list of remote applications that the application must identify.

The list of remote applications is established by selecting from the list of all applications available to the project stored in the OSI Project directory. Therefore, PL7-OSI also supports creation and modification of the OSI Project directory, in addition to setting network interface module parameters.

PL7-OSI lets the user describe the OSI configuration of the modules in the station. It also supports up/downloading of configuration files for each of the interface modules. Like all other Software Workshop tools, PL7-OSI also generates the files required for documenting the application.

__________________________________________________________________________________________

1 / 1

__________________________________________________________________________________________

1.3

PL7-OSI Functions

PL7-OSI supports the following functions:

Configuring the OSI_PRJ project level applications directory

Create, modify or view an OSIPRJ.REP directory file containing the MMS applications for the project. This file can be saved (Save function) and restored (Restore function), allowing back-up copies to be made.

Configuring a module file

Create, modify or view a module (coupler) type file (xxx.CPL) for use with TSX ETH 200 network interface modules.

This type of file comprises:

• The OSI layer parameters,

• The definition of the local application that the module is assigned to operate with in

MMS Client mode,

• The list of remote applications that are visible to the local application, if it is to operate in MMS Client mode.

This file (xxx.CPL) can be loaded directly into the module.

Configuring the OSI.BIN file

Create, modify or view an OSI.BIN binary file. This file comprises 1 to 4 interface module partitions and can be up/downloaded to and from the dedicated OSI field in the PLC memory.

Uploading a module (.CPL) file

Uploading a module xxx.CPL file to the memory in a TSX ETH 200 module from the workstation.

Uploading an OSI.BIN file

Uploading an OSI.BIN binary file to the dedicated OSI field in the PLC memory from the workstation.

Downloading an OSI.BIN file

Downloading (saving) the contents of the dedicated OSI field from the PLC memory to the workstation.

__________________________________________________________________________________________

1 / 2

General 1

__________________________________________________________________________________________

Comparison

Comparing the OSI.BIN file in the local workstation memory with the contents of the dedicated OSI memory field in a target PLC.

Station documentation

Creating documentation on a binary (.BIN) file.

Module documentation

Creating a module configuration documentation file.

Deleting a file

Deleting a configuration or documentation type file.

Setting-up the dedicated OSI field in the PLC memory

Modify or view the configuration parameters of the dedicated OSI memory field in a PLC.

The access to these functions depends on the selection, made by the designer, of the working memory. There are three possible selections:

• Local memory (the workstation disk),

• PLC memory,

• Module memory.

1.4

Accessing PL7-OSI

PL7-OSI is accessed by opening the OSI window in the station where network interface module are to be configured.

Primary window

__________________________________________________________________________________________

1 / 3

__________________________________________________________________________________________

Diagram

Memory

Local

PLC

Module

Configuration (2/3) Transfer

OSI Directory ➙ Disk ➙ PLC

Module ➙

PLC (3)

Documentation (3) Utilities (3) Exit

Generate

PLC ➙ Disk (3) View

Disk ➙ Module (2) Print

Delete ➙

Debug(1)

Restore

Resume

Compare (3) Enter Data ➙ Save

Documentation

(1) Options that cannot be selected when Local Memory is selected

(2) Options that cannot be selected when PLC Memory is selected

(3) Options that cannot be selected when Module Memory is selected

Memory

Configuration

Selects the working memory.

Enter, Save/Restore the project level application directory file

(OSIPRJ.REP). Configures the OSI modules and generates xxx.CPL

or xxx.BIN files.

Transfer Up/Download and Compare xxx.BIN files in the PLC memory OSI field.

Upload xxx.CPL files to a module (depending on the working memory).

Documentation Generates and prints a documentation text file on the xxx.BIN file generated by the tool.

Utilities • Deletes xxx.BIN, xxx.CPL, xxx.OSI, xxx.CRT, xxx.TIT, xxx.DOC files from the workstation disk,

• Save/Restore OSI.BIN files,

• Interactive debugging of the configuration parameters of a module in the PLC memory dedicated OSI field (BIN).

Exit Exits PL7-OSI.

__________________________________________________________________________________________

1 / 4

Selecting the Working Memory - Memory Menu 2

__________________________________________________________________________________________

2.1

Memory Menu

The PL7-OSI main menu lets the user select the working memory.

The functions that can be accessed depend on the selections made.

• Selecting Local memory lets the user access all functions except for the Debug function. It is possible to define module configurations and generate the OSI.BIN file without the need to establish connection with the PLC.

The application directory file can only be accessed when the Local memory option is selected.

• Selecting PLC memory requires connection to the PLC processor. The Up/Download,

Documentation and Debug functions are accessible (and this is the only way to access the Debug function), in the PLC working memory environment.

__________________________________________________________________________________________

2 / 1

__________________________________________________________________________________________

The table below summarizes the functions that can be accessed using the three types of working memory.

FUNCTIONS

Operations on the OSI directory

Configuration\Module\TSX ETH 200

Configuration\PLC

Transfer\Disk ➙ PLC

Transfer\PLC ➙ Disk

Transfer\Disk ➙ PLC

Transfer\Compare

Documentation\Station

Documentation\Module

Utilities\Delete

Utilities\Debug

Restore/Save OSI.BIN

Yes

WORKING MEMORY

Local

Yes

PLC

Module

Yes

For V5 level stations, an additional restriction applies:

The Configuration\Module and Configuration\PLC and Restore (OSI.BIN) functions cannot be accessed if the user has not first used XTEL-CONF to define the location of the network interface module.

__________________________________________________________________________________________

2 / 2

Configuring the Station - Configuration Menu 3

__________________________________________________________________________________________

Configuring the Station - Configuration Menu

The Configuration menu lets the user:

• Create, Modify and View the OSI_PRJ directory for all of the MMS applications in the project.

• Define or Modify the parameters of the TSX ETH 200 OSI module, Define the local

MMS application and the remote MMS applications. Once these definitions are made, a Module (xxx.CPL) type file will be generated.

• Generate the OSI.BIN binary file that contains the configuration of all of the PLC's interface modules. The OSI binary file is intended to be uploaded to the dedicated OSI field in the PLC memory.

3.1

OSI_PRJ Directory

This function is used to create, modify and view the Directory of remote MMS applications for the project.

The directory is shared by all of the stations in the project. The OSI Directory function is the station level access point. It is important to check data coherence when the directory is modified.

__________________________________________________________________________________________

3 / 1

__________________________________________________________________________________________

3.1-1 Describing the Project Directory

The OSI_PRJ Project Directory

• Comprises the description of each MMS application in the project,

• Is described by the OSIPRJ.REP file and is located at project level in the X-TEL Software

Workshop file structure and is unique to each project,

• It can be accessed by all TSXV4/V5 type stations in the project (TSXV4, TSXV5,

PMXV4, PMXV5),

• It can comprise up to 1024 OSI remote applications,

• Supports the OK, Cancel and Help buttons.

The OSIPRJ.REP file is an ASCII file that contains a succession of descriptions of MMS remote applications. It is sorted in rising alphabetical order.

Each of the applications is described by the following parameters (some parameters are optional).

APPLICATION NAME: Identifies an application.

Value = 32 alphanumeric characters.

AP TITLE (optional):

AE QUALIFIER (optional):

Application Process identifier.

Value = 8 x 4 bytes max. in hexadecimal notation.

Application Entity identifier.

Value = 4 bytes max. in hexadecimal notation.

PSEL (Presentation SELector): Access to presentation layer services.

Value = 16 bytes max. in hexadecimal notation.

SSEL (Session SELector): Access to session layer services.

Value = 16 bytes max. in hexadecimal notation.

TSEL (Transport SELector): Access to transport layer services.

Value = 32 bytes max. in hexadecimal notation.

NSAP: Access to network layer services.

(Network Service Access Point) Value = 20 bytes max. in hexadecimal notation.

__________________________________________________________________________________________

3 / 2

Configuring the Station - Configuration Menu 3

__________________________________________________________________________________________

Reminders on addressing rules:

To establish an MMS assignment, system addressing is performed from the physical layer level (the Medium Access Control (MAC) data link sub-level) to the program task level (application level).

Addressing a Local Module:

• APPLICATION NAME:

Logical name that identifies an OSI application.

• AP TITLE and AE QUALIFIER:

The parameters are optional.

• Presentation Address:

The presentation address PSAP (Presentation Service Access Point) is a concatenated character string combining the presentation selector (PSEL) and the previous session address (SSAP). It is a character string of 1 to 16 bytes with a default value of 00 00 00 01.

• Session Address:

The session address SSAP (Session Service Access Point) is a concatenated character string combining the session selector (SSEL) and the previous transport address (TSAP). It is a character string of 1 to 16 bytes with a default value of 00 01.

• Transport Address:

The transport address TSAP (Transport Service Access) is a concatenated character string combining the transport selector (TSEL) and the previous network address

(NSAP). It is a character string of 1 to 16 bytes with a default value of 00 01.

• Network Address:

The network address conforms to the hierarchical layout defined in the ISO 8348/AD2 standard and supports all of its formats. The maximum size supported by the NSAP

(Network Service Access Point) is 20 bytes. The NASP address default value is the local NASP format, described as follows:

49: identifies the local NASP format,

54 45 4C 45 4D 45 43 41 2E: ASCII character string abbreviation for

Telemecanique,

00FE: with 00 the default network number and FE the default station number

(from 0 to 63),

01: NSEL identifying a terminal system.

The NSAP network address must be unique to each system and it identifies a single system connected to the network.

The OSI-MMS profile supports a single local MMS application, defined by the parameters:

APPLICATION NAME, AP TITLE (Application Process Title), AE QUALIFIER (Application Entity Qualifier), PSAP, LSAP (Link Service Access), MAC Address (Medium

Access Control).

__________________________________________________________________________________________

3 / 3

__________________________________________________________________________________________

Remote System Addressing

The same local addressing parameters are used, i.e. NSAP, TSEL, SSEL, PSEL, AE

QUALIFIER, AP TITLE and APPLICATION NAME.

The OSI Project Directory is created by the PL7-OSI designer, locally from the station.

To do this the Entry function is used, allowing access to the OSIPRJ.REP file at project level. This lets the user describe the remote applications using specific data entry fields.

3.1-2 OSI_PRJ Directory Edit Function

Once this function is selected, the following data entry screen is displayed:

This screen displays the OSI_PRJ Directory information, listing the names of the remote applications stored in the OSIPRJ.REP file.

The fields below this display the values of each of the addressing parameters of the remote application selected in the top box.

__________________________________________________________________________________________

3 / 4

Configuring the Station - Configuration Menu 3

__________________________________________________________________________________________

This field is arranged in three columns that, from left to right, give the:

• Designation of the parameter in column 1,

• Value taken by the parameter in column 2, displayed in a field that can be edited,

• Limit values (number of characters or number of bytes) and the format (character or hexadecimal) of the value entered.

The functions available at Application level are mentioned in the top right part of the screen, these comprise:

• Adding a new remote application,

• Modifying a previously entered application,

• Deleting a previously created application.

These three functions are only effective locally. They do not change the OSIPRJ.REP

file. Only the user confirmation by selecting OK will modify the file.

The functions available at all levels are shown across the bottom of the screen. They are:

• OK: Confirm data entry,

• Cancel,

• Help.

Add Lets the user create a new remote application. Procedure:

• Enter a new application name in the Application Name field, the other fields are cleared,

• Fill-in the other fields,

• Click on Add once the entries are made.

The formats of the various parameters are checked. If an error is found, a message is displayed an the cursor is placed on the field where the error was found.

If no errors are found, the data entered is saved and the application is added to the list in the OSI_PRJ Directory field.

Modify Lets the user modify a remote application that was previously defined in the

OSI_PRJ directory. Procedure:

• Select an application from the list in the OSI_PRJ Directory field, by double clicking on it. The various fields will display the values for the selected application.

• Make the required modifications to the various fields.

• Click on Modify, the values entered are checked as described for Add.

__________________________________________________________________________________________

3 / 5

__________________________________________________________________________________________

Delete Lets the user delete a remote application from the OSI directory. Procedure:

• Select the application to delete from the list in the OSI_PRJ Directory field.

• Click on Delete. The selected application will be deleted.

OK This function saves the remote application data as entered, in the OSIPRJ.REP

file in the OSI_PRJ directory.

Note that this action overwrites the existing OSIPRJ.REP file stored at project level.

If a Modify or Delete action was performed, a message informs the user that there may be incoherent data in the stations. The user is then returned to the

PL7-OSI main menu.

Cancel By clicking on this button, the user is returned to the PL7-OSI main menu and

any modifications made will be lost.

3.1-3 OSI_PRJ Directory Restore Function

This function lets the user import an ASCII file that meets the OSIPRJ.REP file format requirements, from a diskette or hard disk. When this action is performed, it overwrites the existing OSIPRJ.REP file.

__________________________________________________________________________________________

3 / 6

Configuring the Station - Configuration Menu 3

__________________________________________________________________________________________

Selecting Restore displays the following window:

Simply type the complete name (file name and access path) of the file to import, in the entry line and select the OK button to confirm.

The user will be prompted to confirm creation of the OSIPRJ.REP file. Once confirmed, any previous OSIPRJ.REP file will be overwritten with the newly imported one.

A message informs the user of the progress of the function. If a syntax error is found in the source file, the error is displayed along with the program line where it occurred.

Selecting the Cancel button lets the user abort the function without creating a new file.

3.1-4 OSI_PRJ Directory Save Function

This function lets the user copy the OSIPRJ.REP file to a file on diskette or hard disk with a user specified name. This function is the reverse of the Restore function.

This function is selected in the same way as the Restore function. Enter the full name

(file name and access path) of the target file, in the entry line and confirm the entry made.

A message informs the user of the progress of the function.

__________________________________________________________________________________________

3 / 7

__________________________________________________________________________________________

3.2

Configuring a TSX ETH 200 Module

This function lets the user create, modify or view an xxx.CPL file.

This file comprises the configuration of a TSX ETH 200 module. It is intended to be uploaded to the module. The xxx.CPL file is also used when the station PLC is configured, when the OSI.BIN file is generated (refer to Sub-section 3.3).

The module configuration data comprises three sub-sets:

• OSI layer parameters,

• Definition of the local MMS application,

• List of remote applications that the module defines an association with.

The data is defined using data entry screens that are specific to each set of data. A first screen lets the user select the name of the module file. These screens are defined below.

3.2-1 Selecting and Generating the Module File (xxx.CPL)

Once the \Configuration\Module\ETH200 selection is made from the PL7-OSI main menu, the following screen is displayed:

__________________________________________________________________________________________

3 / 8

Configuring the Station - Configuration Menu 3

__________________________________________________________________________________________

This screen comprises three parts:

• Select File. At left, this section comprises a first field that displays the name of the module file (xxx.CPL) that will be created or modified and a frame that comprises the list of xxx.CPL files available.

It is up to the user to enter the file name, either directly from the keyboard, or by selecting a file from the list of those available.

When there are no xxx.CPL files listed, the default file name that is displayed is a name made up from the station name (Stattion_Name.CPL). If there are already files available, the default display will be the first file in the list of files.

• Select modification. At right, this section comprises three items:

• OSI layer parameters,

• Local application definition,

• Remote application selection.

This part lets the user pre-select the sets of parameters that require definition or modification, simply click on the corresponding items.

• Modify default configuration. At lower right, this section comprises two fields:

Revert to the standard configuration and Save new configuration.

- The Revert to standard configuration option lets the user return to the default module configuration and use the standard parameter values defined by Telemecanique.

This option is useful if a previous modification was made to the standard configuration using the Save new configuration option.

- The Save new configuration option lets the user modify the standard default configuration defined by Telemecanique and use the configuration corresponding to the selected xxx.CPL file.

The configuration saved using this option only affects the parametering of the OSI layers and the definition of the local application.

The Save new configuration option can only be accessed after selecting one of the

Select modification items.

Creating the Module (.CPL) File

When creating the file (the file name selected is not the same as an existing file) and if no modification selections have been made, selecting OK will immediately create the designated file with a default configuration. The OSI layer parameters are initialized with default values and the local application is also defined with default parameters. No remote applications are assigned to the module. The default configuration only allows operation in MMS Server mode.

__________________________________________________________________________________________

3 / 9

__________________________________________________________________________________________

Modifying a Module (.CPL) File

If the file name selected is the same as an existing file, the user must select the modifications to make in the appropriate display box. Otherwise an error message will be displayed when the user selects OK.

If the OSI_PRJ remote applications directory for the project was modified since the last time the module file was generated, and it comprises a list of remote applications, the following warning is displayed when the user selects OK.

D Yes

Generates the .CPL file when the default configuration is selected (as described previously).

Starts the configuration screen display sequence, according to the modification selections made.

Aborts the module configuration action and returns the user to the PL7-OSI main menu.

__________________________________________________________________________________________

3 / 1 0

Configuring the Station - Configuration Menu 3

__________________________________________________________________________________________

3.2-2 Setting OSI Layer Parameters

If any modification to OSI layer parameters was specified in the previous screen, selecting OK will display the screen shown below:

This screen comprises:

• The parameter edit field. This field is divided into groups of parameters for each OSI profile layer,

• The control buttons.

Editing parameters

The parameter editing field comprises four columns, arranged from left to right:

• Column 1:

• Column 2:

OSI parameter name,

Numerical value of the parameter to edit,

• Column 3:

• Column 4:

Value measurement unit,

Value numerical base symbol (D for Decimal, H for Hex).

A value is edited by clicking first on the field to modify, in Column 2, then typing in the new value from the keyboard. The column widths shown on screen are constant, but the entry field is restricted to the maximum number of digits allowed for each entry. If the field will accept more digits than the column width will display, it is possible to shift the display

(horizontal scroll) to the left or to the right, using the left and right cursor keys.

A check is performed on the value of the parameters, when the user exits the screen.

It is impossible to exit the screen when an error is found and an error message is displayed. The "Syntax Error" message means that there is at least one syntax error in one of the values. The error message "Values out of bounds" is self-explicit.

__________________________________________________________________________________________

3 / 1 1

__________________________________________________________________________________________

Button actions

Modify

Cancel

Saves the parameter values, then calls-up the next data entry field, if other modifications were selected in the first screen, or generates the .CPL file once all selected modifications have been made. In this case, the user is returned to the PL7-OSI main menu as soon as generation is complete.

Aborts the set parameter action. The user is returned to the previous screen. The modification selections made previously are lost.

3.2-3 Defining the Local Application

If "Define Local Applications" was selected, the following screen is displayed:

This screen displays the application parameters APPLIC. NAME (Application Name),

AP_TITLE, AE QUALIFIER, PSEL, SSEL, TSEL and NSAP across the top of the screen, in the usual three column layout. If the .CPL file being configured has not yet been generated, the APPLIC. NAME and PSEL fields take the default values.

The screen comprises three parts:

• The top part shows the parameters that define the application, using the standard three column layout,

An "OSI_PRJ Directory" button lets the user access the OSI_PRJ directory by selecting an application that will become the local MMS application.

• The lower part that is reserved for the definition of the number of MMS assignments that the local application can open or accept,

• The control buttons.

__________________________________________________________________________________________

3 / 1 2

Configuring the Station - Configuration Menu 3

__________________________________________________________________________________________

Define Local Application (upper part)

The parameters required to define the application are APPLIC. NAME, PSEL, SSEL,

TSEL and NSAP. The values of the AP TITLE and AE QUALIFIER parameters are optional.

When a .CPL file is created, these required parameters take the current default values.

The "OSI_PRJ Directory" button lets the user select an application from those defined in the OSI_PRJ directory. To do this, click on the "OSI_PRJ Directory" button. The upper part of the OSI_PRJ screen displays the list of applications present in the directory.

To display the parameters of an application, click on its name in the list. The lower

"Complete Address" field on-screen will display these parameters. Click on the Select button to validate the selection made.

An alternative method for selecting an application requires double-clicking on the selected application. The parameters of the selected application will then be displayed in the Local Application definition window.

It is also possible to enter parameter values that do not correspond to to an application in the OSI_PRJ directory. These values are entered directly into the Local Application definition fields.

Defining the number of assignments

The user must declare the number of assignments that can be open between the local application and the remote applications, defining the number of assignments opened on the initiative of the local application and those accepted by the local application. The total number of assignments is restricted to 322.

The value of Max Serv Outstanding Calling/Called depends on the total number of assignments configured in PL7-OSI (number of assignments opened at the initiative of the local application plus the number of assignments accepted by the local application).

M = max (Negotiated Max Serv Outstanding Called) = proposed Max Serv Outstanding Calling

4 8 12 16 21 24 28 32 Total number of assignments configured in PL7-OSI

OK Saves the parameter values, then calls-up the next data entry screen, if other modifications were selected in the first screen, or generates the

.CPL file once all selected modifications have been made. In this case, the user is returned to the PL7-OSI main menu as soon as generation

Cancel is complete.

Aborts the parametering action. The user is returned to the previous screen. The modification selections made previously are lost.

__________________________________________________________________________________________

3 / 1 3

__________________________________________________________________________________________

3.2-4 Selecting Remote Applications

If "Select Remote Applications" was selected, the following screen is displayed:

The screen comprises three parts:

• The "OSI_PRJ Directory" frame that displays a list of remote applications in the OSI directory,

• The "List of Selected Applications" frame that shows a list of remote applications that the local application can establish assignments with. This frame also includes the Add and Delete buttons,

• The "Complete Address" frame listing the parameter values for an application.

The purpose of this screen is to select from the "OSI_PRJ Directory" frame, the remote applications that will be selected for the specific module.

Adding a Remote Application

There are two ways to proceed:

First procedure:

• Click in the "OSI_PRJ Directory" frame and select the appropriate application. Once it is selected, its parameters are displayed in the "Complete Address" frame.

• Click on Add in the "List of Selected Applications" frame, the name of the application will be displayed in the frame and, at the same time, the "Complete Address" field will be cleared.

Second procedure:

• Double click on the application to select in the "OSI_PRJ Directory" frame. The name of the selected application is immediately displayed in the "List of Selected Applications" frame.

__________________________________________________________________________________________

3 / 1 4

Configuring the Station - Configuration Menu 3

__________________________________________________________________________________________

Deleting a Selected Application

• Click on the application to delete in select in the "List of Selected Applications" frame,

• Click on the Delete button.

Remark

From this screen, it is not possible to delete or modify a Remote Application in the

OSI_PRJ directory ("OSI_PRJ Directory" and "Complete Address" frames). To make these modifications, the user must exit module configuration and return to the

PL7-OSI main menu and select Configure\OSI Directory, then Data Entry.

To complete the Remote Applications selection procedure, use the buttons located at the bottom of the screen.

Button action

Cancel

Generates the xxx.CPL file and returns the user to the PL7-OSI main menu as soon as generation is complete.

Aborts the remote application selection action. The user is returned to the first "Configuring a TSX ETH 200 Module" screen.

The selections made previously are lost.

__________________________________________________________________________________________

3 / 1 5

__________________________________________________________________________________________

3.3

Configuring the PLC

This function lets the user:

• Create the structure of an OSI.BIN file from one or more Module (xxx.CPL) type files,

• Modify the communication parameters of modules in the OSI partition of an existing

OSI.BIN file,

• View the OSI partition of an existing OSI.BIN file.

This function is a Create action when the OSI.BIN file does not exist. It is a Modify or

View action once the file exists.

The OSI.BIN file that is generated, is used to save the directory and configurations for the interface modules in a station, when it is loaded into the dedicated OSI field in the

PLC memory of the station.

An OSI.BIN file comprises a header, directory or module configurations and memory partitions that each comprise a module configuration.

The number of possible partitions depends on the type of target station:

• TSX 47-420/47-455, PMX 47-420/47-455 stations will only support a single OSI module,

• TSX 67-40, PMX 67-40 stations will support one or two OSI modules,

• TSX 87-40, PMX 87-40, TSX 107-40 and PMX 107-40 stations will support up to four

OSI modules.

These are maximum values that apply to the various models, given that other network interface modules such as FIPWAY, ETHWAY, MAPWAY, etc. must be taken into account when determining the maximum number of connections supported by a station.

__________________________________________________________________________________________

3 / 1 6

Configuring the Station - Configuration Menu 3

__________________________________________________________________________________________

The sequence of actions to perform to Create, Modify or View an OSI.BIN file is described below:

1.1 Create - Assign one or more module files to one or more slot numbers in the target PLC rack (Create OSI.BIN File screen),

1.2 Modify or View - Modify or View the communication parameters of one or more modules from the configuration stored in the OSI.BIN binary file displayed on-

2 screen (Modify OSI.BIN File screen),

Generate or Regenerate the OSI.BIN file as required, if any modifications were made to an existing configuration.

3.2-1 Creating an OSI.BIN File

The PLC configuration function is a create action when the OSI.BIN file does not yet exist. The following screen is displayed:

This screen lets the user assign a slot number in the rack to a previously created module file.

Simply click on a module file name in the "Select File" frame., then click on the slot number in the "Select Slot Number" frame, to assign the file to the module location.

The assignment is shown on-screen by the newly selected file name being displayed in the appropriate column.

Note that if an OSI.BIN file containing .CPL files is displayed, the filename.CPL is replaced by TSX ETH 200, corresponding to the type of module.

For a V5 level station, the slots in the rack that can be accessed are determined by the

3 / 1 7

__________________________________________________________________________________________

Deleting a Module-Slot assignment

To undo an assignment made, click on the appropriate slot number and the following screen is displayed:

Click on the DELETE Module option, then on OK and the user will be returned to the previous screen. The file name will have been deleted from the slot.

Note: The Modify option in the module configuration is not available when first creating the OSI.BIN file.

To exit the "Create OSI.BIN File" screen, click on the OK or Cancel buttons at the bottom of the screen.

Cancel

Generates the OSI.BIN file. A message indicates that the file will be created and saved and requests user confirmation before proceeding.

Select Enter to exit this screen.

Aborts the configuration action. This selection must be confirmed by the user.

Help Calls-up the help screens on module assignment.

__________________________________________________________________________________________

3 / 1 8

Configuring the Station - Configuration Menu 3

__________________________________________________________________________________________

3.3-2 Modifying and Viewing an OSI.BIN File

When the selected OSI.BIN file already exists, the Configuration\PLC option calls-up the following screen:

This screen is almost identical to the "Create the OSI.BIN File" screen. The screen title is different and the slots assigned are marked with the type of module and not the module file name as used previously.

The Modify function provides the user with the same features as the Create OSI.BIN file function described above. In addition, it lets the user access the module configuration screens described in Sub-section 3.2.

To modify a module configuration, click on the slot number assigned to it, then click on the Modify option in the newly displayed screen.

Once confirmed by selecting OK, this window is replaced by the "Modify Module File" window.

__________________________________________________________________________________________

3 / 1 9

__________________________________________________________________________________________

This screen lets the user select the type of modifications to make. The procedure used is the same as that described in Sub-section 3.2 for configuring a module.

If modifications are made to the configuration, the corresponding module file is regenerated, once the action is confirmed by the user. At the end of the PLC configuration session, the user is also prompted to accept OSI.BIN file regeneration.

Remark

It is only possible to modify the configuration of a module from the PLC configuration function, if the module was already declared in the OSI.BIN partition during a prior session.

Cancel

Regenerates the OSI.BIN file. A message warns the user that the file will be regenerated and requests user confirmation before proceeding, as described for creating an OSI.BIN file.

Aborts the configuration action. This action must be confirmed by the user from the dialog box that is displayed.

__________________________________________________________________________________________

3 / 2 0

Transfefring Binary and Module Files - Transfer Menu 4

__________________________________________________________________________________________

Transferring Binary and Module Files - Transfer Menu

This function lets the user transfer an OSI.BIN or Module (.CPL) file, generated by the

Configuration function, from the terminal hard disk to the PLC or module memory. It can also be used to transfer the contents of the dedicated OSI field in the PLC memory to an OSI.BIN file in the workstation.

This function also supports comparisons between an OSI.BIN file on disk and the contents of the dedicated OSI field in the PLC memory.

4.1

Uploading to the PLC

This function lets the user transfer the OSI.BIN file to the PLC memory.

Remark

An upload can only be performed if the dedicated OSI field was assigned previously in the PLC memory. To perform the assignment, use the following tools:

• For a V4 level station

XTEL-MEM will generate an application file for configuring the memory (xxx.APP

file). This configuration must include a dedicated OSI field.

XTEL-TRANSFER can then be used to upload to the PLC memory, the newly generated xxx.APP file.

• For a V5 level station

XTEL-CONF is used to create the memory structure for the application file. This tool is used to reserve the necessary PLC memory for the OSI.BIN file.

XTEL-TRANSFER can then be used to upload to the PLC memory, the memory structure and its associated application files (such as OSI.BIN), if they exist.

__________________________________________________________________________________________

4 / 1

__________________________________________________________________________________________

To perform the upload, the workstation must be connected to the PLC.

Once the Disk->PLC action is selected from the pulldown menu, for:

• V4 level stations, the following dialog box is displayed:

Yes Starts the transfer. A message is displayed to inform the user that the operation is complete and that it was performed correctly.

If the message "PLC not mapped for this application" is displayed, use

XTEL-MEM and XTEL-TRANSFER to change the memory mapping for the application in the PLC memory.

As a rule, if the transfer could not be executed, the action is completed with the message "File OSI.BIN could not be uploaded correctly to PLC memory" and the user is returned to the main menu.

No Aborts the upload action and returns the user to the PL7-OSI main menu.

• For a V5 level station, The XTEL-TRANSFER screen is displayed with its dialog box:

The OSI function is automatically selected, select Transfer to start the transfer action.

As described previously, for the transfer to be successful, XTEL-TRANSFER must first have been used to transfer the memory structure for the application that was developed using XTEL-CONF.

__________________________________________________________________________________________

4 / 2

Transfefring Binary and Module Files - Transfer Menu 4

__________________________________________________________________________________________

4.2

Downloading from the PLC

This function transfers the contents of the dedicated OSI field from the PLC memory to the OSI.BIN file on the workstation hard disk.

To perform the download, the workstation must be connected to the PLC.

• For a V4 level station, once the PLC ➙ Disk option is selected from the pulldown menu, the Transfer File dialog box is displayed. The sequence of actions is the same as for an Upload.

• For a V5 level station, the XTEL-Transfer screen is displayed with the OSI function selected. Confirmation of the transfer warns the user that the OSI.BIN file present in the workstation will be replaced with the contents of the PLC's OSI memory field.

__________________________________________________________________________________________

4 / 3

__________________________________________________________________________________________

4.3

Uploading to a Module

This function transfers a module (.CPL) type file, describing the configuration, to the module memory.

Selecting a file to upload

After selecting the Disk->Module option from the pulldown menu, the File Selection dialog box is displayed.

The user can specify the name of the module (.CPL) file to transfer to the module memory.

To do so, click on the name of the file to upload, in the list of files displayed. The selected file name is displayed in the "Files Selected" field. The user can also use the cursor keys to move the selection bar in the list of files and then press <Enter> to confirm the selection made.

__________________________________________________________________________________________

4 / 4

Transfefring Binary and Module Files - Transfer Menu 4

__________________________________________________________________________________________

OK Proceeds to the next phase: selecting the rack location to upload to, once the user has confirmed the action.

Cancel Cancels file selection, the user is returned to the PL7-OSI main menu.

Selecting the module location

After confirming the module (.CPL) file, the following screen is displayed:

This screen lets the user select the slot in the PLC rack where the target interface module is located. The selection is made by clicking on the slot number. Once the selection is made the slot column changes color. Once the target module location has been selected, the transfer can be made.

For V5 level stations, the slots that can be selected are those defined in the I/O configuration established using XTEL-CONF.

OK Starts the transfer once the slot number is selected.

If the transfer fails, the cause of failure is displayed and the user is returned to the Select File window after acknowledging the error message.

Cancel Cancels the operation, the user is returned to the File Selection window and no transfer is made.

Warning:

The configuration loaded in the module is automatically overwritten with the configuration loaded in the PLC if the MMSLD OFB is configured in the PL7-3 application.

__________________________________________________________________________________________

4 / 5

__________________________________________________________________________________________

4.4

Comparing the PLC Memory with the OSI .BIN File

This function compares the dedicated OSI field in the PLC memory with the OSI.BIN file stored on disk in the workstation.

To perform the comparison, the workstation must be connected to the PLC.

After selecting Compare from the pulldown menu, the following dialog box is displayed.

Click on Yes, comparison is completed when one of two messages is displayed:

"The OSI.BIN file and the binary file in the PLC are identical" or

"The OSI.BIN binary file and the binary file in the PLC are different".

__________________________________________________________________________________________

4 / 6

Documenting and Printing 5

__________________________________________________________________________________________

Documenting and Printing

The following procedure applies for creating documentation on the configuration of OSI modules in the station:

• Prepare the documentation title page (create an OSI.TIT file),

• Prepare the documentation footer (create an OSI.CRT file),

• Create the application documentation (for storage in an OSI.DOC file), from the

OSI.TIT and OSI.CRT files created previously and the OSI.BIN file that contains the configuration,

• View the finished documentation on-screen or print it out.

The first two steps are performed in the Documentation function (first option in the pulldown menu), the third in the Print function.

5.1

Generating Documentation

Selecting the Generate option starts creation of the documentation for the station OSI application.

It requires that the user first create the title page and footer, described respectively in the OSI.TIT and OSI.CRT files.

The documentation uses the information contained in the OSI.BIN file.

__________________________________________________________________________________________

5 / 1

__________________________________________________________________________________________

5.2

View

Selecting this function lets the user immediatly view on-screen, the newly generated documentation.

The user can scroll the documentation vertically and horizontally. The format displayed corresponds to what can be printed-out.

5.3

Print

When this function is selected, it first displays the list of printer that can be used for printing out the station documentation file.

The user then free to select from the list of printers connected to the workstation, the one to use for printing out the documentation file. Simply click on the <OK> button to confirm the selection and start printing.

The <Cancel> button lets the user cancel the printing in progress.

Remark

The station documentation file generated by PL7-OSI (the OSI.DOC file) can be printed out separately and it can also be integrated into the complete documentation file for a V4 or V5 level station.

The integration is performed by XTEL-DOC and it is transparent to PL7-OSI.

__________________________________________________________________________________________

5 / 2

Documenting and Printing 5

__________________________________________________________________________________________

5.4

Enter Information

Entering the title page

When this menu is selected, its data entry fields display the contents of the OSI.TIT file, if it already exists. Else all fields are blank.

Access to a predefined field is by mouse or keyboard and Tab key. Within a field, the user can move between columns and lines using the mouse or the cursor keys.

Various entries are possible:

• Title

• Company

• Department

• Manager

• REV.

• DATE

• REVISION

• DESIGNER

• EXECUTED by

: Application title (64 chars. max.),

: Company name (16 chars. max.),

: Department name in the Company (16 chars. max.),

: Manager's name (16 car. max.),

: File revision level (3 chars. max.),

: File creation or modification date (8 chars. max.)

: Comments on the revision made (32 chars. max.),

: Designer's name (12 chars. max.),

: User's name (12 chars. max.),

__________________________________________________________________________________________

5 / 3

__________________________________________________________________________________________

The OSI.TIT file generated is an editable ASCII file.

OK Saves the contents of the screen to the OSI.TIT file and exits the screen.

Cancel

Write

Exits the screen without saving the OSI.TIT file.

Writes the contents of the screen to the yyy.TIT file specified in a dialog box (the default name is OSI.TIT). This command does not exit the screen.

Read Reads a yyy.TIT file stored during a previous session. The file name is specified in a dialog box (the default name is OSI.TIT).

Entering the custom footer

This screen lets the user customize the footer that appears at the bottom of every documentation file page. Two strings of characters can be filled-in by the user:

• A string of 25 characters at the top of the footer,

• A string of 45 characters at the bottom of the footer.

The fields are filled-in with the contents of the OSI.CRT file, if it already exists.

The documentation footer provides the following information:

• Application name,

• Printed item name,

• Document version number,

• Print-out date,

• Relative page numbering by item,

• Absolute page numbering.

__________________________________________________________________________________________

5 / 4

Documenting and Printing 5

__________________________________________________________________________________________

OK Saves the contents of the screen to the OSI.CRT file and exits the screen.

Cancel Exits the screen without saving the OSI.CRT file.

Write

Read

Writes the contents of the screen to a yyy.CRT file specified in a dialog box (the default file name is OSI.CRT). This command does not exit the screen.

Reads a yyy.CRT file saved during a previous session. Its name is specified in a dialog box (the default file name is OSI.CRT).

__________________________________________________________________________________________

5 / 5

__________________________________________________________________________________________

5.5

Documenting a Module

Documenting a module comprises presenting in a printable ASCII format, the contents of an xxx.CPL configuration file. The file generated will retain the name of the xxx.CPL

file and take the "OSI" extension.

As usual with a "Select File" dialog box, the user can select a file from the list of module

(.CPL) type files known to the station by:

• Double clicking on the file to select,

• Using the cursor keys to select the required file and pressing <Enter>.

If there are no .CPL files available, the Select File box is replaced by the message "No files to select!".

Cancel

Formats an xxx.OSI ASCII file from the selected xxx.CPL file.

Cancels the action. No xxx.OSI file is generated.

__________________________________________________________________________________________

5 / 6

Deleting Files - Configuration Set-Up - Help 6

__________________________________________________________________________________________

6.1

Utilities - Deleting Files

The Delete utility lets the user delete all of the files generated by PL7-OSI.

Once this option is selected, simply click on the type of file to delete. Regardless of the file type (except for OSI.BIN files), the procedure is the same:

Select the file from the dialog box that opens and confirm the selection.

Once the file is deleted, control returns to the updated dialog box. This operation can be repeated as many times as there are files to delete.

For the OSI.BIN file, which is a special case as there is only one such file, the file selection step is of course unnecessary.

If no file can be deleted in the selected type, the selection is dimmed and cannot be accessed.

For example, the screen that is displayed after selecting Module File... (.CPL) is shown below:

__________________________________________________________________________________________

6 / 1

__________________________________________________________________________________________

OK Deletes the file listed in the "Files selected" field, after requesting user confirmation.

Cancel Cancels the action. No files are deleted.

6.2

Utilities - Debugging an OSI Configuration

This option allows the user to modify, for debug purposes, the OSI parameters of a module, previously loaded into the dedicated OSI field of the PLC memory.

Once confirmed, the new configurations are automatically transferred by OFB into the appropriate modules.

Remark

These configurations are not saved locally in the xxx.CPL files.

This function displays an on-screen representation of a PLC rack and uses the procedure for modifying a PLC configuration (PLC Configuration function for OSI.BIN

files, as described in Sub-section 3.3-2).

__________________________________________________________________________________________

6 / 2

Deleting Files - Configuration Set-Up - Help 6

__________________________________________________________________________________________

Click on the PLC slot number where the module, whose parameters require modification is located, to access the module parameter setup screens.

Cancel

Help

Calls-up the screen shown above.

No modifications are made.

Select the module configuration action to access the modification screen. Refer to Subsection 3.3-2.

__________________________________________________________________________________________

6 / 3

__________________________________________________________________________________________

6.3

Utilities - Restoring/Saving an OSI.BIN File

The Restore function allows the user to import an OSI.BIN binary file from a diskette or hard disk, into the station memory field. The newly imported file replaces the existing

OSI.BIN file.

The Save function allows the user to copy the OSI.BIN file from the station to another directory on the hard disk or diskette.

6.3-1 Restore

If the Restore option is selected, type the source file name in the field displayed by the dialog box:

OK Copies the selected file to the OSI.BIN file, once the action is confirmed by the user when prompted by the following message:

"This action will overwrite the existing OSI.BIN file. Please confirm the operation."

Cancel Cancels the action and returns the user to the PL7-OSI main menu.

For V5 level stations, if the I/O configuration was not previously defined using

XTEL-CONF, it is not possible to restore the OSI.BIN file. In addition, a coherence check is performed to ensure that the module locations defined in the restored file do indeed correspond to the I/O configuration.

__________________________________________________________________________________________

6 / 4

Deleting Files - Configuration Set-Up - Help 6

__________________________________________________________________________________________

6.3-2 Save

If the Save option is selected, type the target file name in the field displayed by the dialog box and validate it:

If the file already exists, the user will be warned by a message and a request to confirm.

__________________________________________________________________________________________

6 / 5

__________________________________________________________________________________________

6.4

Help

The Help option in the pulldown menu lets the user access to root directory of PL7-OSI help screens.

The About... option displays information on the current version of the installed software.

__________________________________________________________________________________________

6 / 6

Appendix 7

__________________________________________________________________________________________

Appendix

Directory File Format

The OSIPRJ.REP file can be created using a standard text editor. The file can then be added to the X-TEL data base using the Restore function (refer to Divider D, Sub-section

3.1-3).

To be used with the X-TEL Software Workshop, the directory file must comply with certain rules:

• The file comprises lines that describe remote applications,

• An application is described by a string of variables within a / character as prefix and suffix,

• The values are those of the parameters that define an application and they must be placed in the line in the following sequence: Application_Name, Ap_Title, Ae_Qualifier,

Psel, Ssel, Tsel, Nsap,

• The values of any optional parameters can be omitted, however the / separator characters must be retained,

• A # character placed at the start of the line indicates that the line is a comment.

Exemple:

#OSI_PRJ Directory

#Format:

#/APPLICATION_NAME/AP_TITLE/AE_QUALIFIER/PSEL/SSEL/TSEL/NSAP/

/APPLICATION1///00000004/0003/0001/39840F454E45000000010001410901/

/APPLICATION2///00000003/0001/0001/39840F544E45000000010001010101/

/APPLICATION3/123//00000004/0001/0001/39840F544E45000000010003000601/

<EOF>

__________________________________________________________________________________________

7 / 1

__________________________________________________________________________________________

7 / 2

________________________________________________________

PL7-MMS E

___________________________________________________________________________

Section

1 General

1.1

PL7-MMS Presentation

1.2

PL7-MMS Function

1.2-1 Creating the Project Level Directory of Variables

1.2-2 Creating, Viewing, Uploading and Documenting

Station Variables at Project Level

1.2-3 Converting an Application

1.3

Accessing PL7-MMS

Page

1/1

1/2

1/3

1/5

2 Selecting the Working Memory - Memory Menu

2.1

Memory Menu 2/1

3 Configuring Variables

3.1

Editing the MMS Directory at Project Level

3.1-1 Defining Remote Variables

3.1-2 Defining Structures Associated with Remote Variables

3.2

Configuring Remote Variables

3.3

Configuring Local Variables

3.3-1 Defining Local Variables

3.3-2 Defining Structures Associated with Local Variables

3.4

Generating an MMS.BIN Binary File

3/1

3/2

3/6

3/11

3/14

3/18

3/20

4 Transferring Binary Files

4.1

Uploading to the PLC

4.2

Downloading from the PLC

4.3

Comparing the PLC Memory with a Binary File

4/1

4/2

4/3

___________________________________________________________________________

E / 1

________________________________________________________

___________________________________________________________________________

Section

5 Documenting and Printing

5.1

Generating the Documentation

5.2

View

5.3

5.4

Entering Information

Page

5/1

5/2

5/3

6 Viewing MMS Binary Files - Deleting Files - Help

6.1

Viewing MMS Binary Files

6.1-1 Viewing a Binary File on the Workstation

Disk

6.1-2 Viewing the Bianry File Stored in the PLC

6.2

Deleting Files

6.3

Saving/Retrieving MMS Binary Files

6.4

Help

7 Appendix

Project Directory File Format 7/1

6/1

6/3

6/4

6/5

___________________________________________________________________________

E / 2

General 1

__________________________________________________________________________________________

1.1

PL7-MMS Presentation

PL7-MMS is a Station level function tool, a sub-set of PL7-OSI 3.0.

PL7-MMS lets the user define all of the MMS variables at project level, in the XTEL context, that are visible to all stations. It also supports the selection, for a given station, of "client" variables, i.e. remote variables that are visible to the station. In addition, it also lets the user define, for a given station, "server" symbols, i.e. local symbols (in the selected station) that are visible to other stations.

The MMS variable management function is provided by two software sub-sets:

• PL7-MMS variable definition software, implemented on an FTX 507 station running the XTEL Software Workshop,

• PL7-3 (OFB) Optional Function Block software implemented on the TSX and PMX

Series 7 PLCs.

The following Sub-sections describe the functions and operating modes of PL7-MMS software.

The OFB software is described separately in Divider F.

1.2

PL7-MMS Functions

1.2-1 Creating the Project Level Directory of Variables

Configuring an MMS project directory

Creation or modification of the MMS project directory. This directory is a single ASCII file for all of the stations in the same project. This file is saved at project level in the XTEL file structure.

This file can also be created by other tools such as text editors, word processors, etc.

In this case, the file must be restored to the XTEL base using the "Restore" command.

__________________________________________________________________________________________

1 / 1

__________________________________________________________________________________________

1.2-2 Creating, Viewing, Uploading and Documenting Station Variables at Project Level

Configuring an MMS binary file

Creating or modifying the MMS binary file (MMS.BIN) with the configuration of station symbole, visible to the other stations and/or remote symbols. The MMS.BIN file can be loaded into the station PLC.

Uploading an MMS binary file

Loading the MMS.BIN file into the dedicated MMS field in the PLC memory, from the workstation disk (using XTEL-TRANSFER for V5 level stations).

Downloading an MMS binary file

Downloading (backing-up) an MMS.BIN file from the dedicated MMS field in the PLC memory to the workstation disk (using XTEL-TRANSFER for V5 level stations).

Comparing files

Comparing the MMS.BIN file with the dedicated MMS field in the PLC memory to check that they are identical.

Viewing an MMS binary file

On-screen viewing of the contents of an MMS.BIN file stored on the workstation hard disk or of the dedicated MMS field in the PLC memory.

Documenting the station

Creating the documentation for an MMS.BIN file.

Creating the MMS. DOC file and the option to create MMS.TIT and MMS.CRT ASCII files.

Deleting a file

Deleting configuration or documentation files.

__________________________________________________________________________________________

1 / 2

General 1

__________________________________________________________________________________________

1.2-3 Converting an Application

This function is used to convert all or part of the files that make up a V43 or V5 level MMS application for migration to V52 level.

This function can be invoked in a number of cases:

• When the program is first started, the presence of an MMS Server base with a version level prior to V52 is detected. A message prompts the user to perform the conversion.

If the MMS function detects a binary file with a version level prior to V52, it will be converted automatically. The conversion also comprises files related to the current application.

The presence of an MMS Server base with a version level prior to V52 inhibits all MMS program functions except the Exit and Conversion functions.

• While MMS is being used, if the program detects the presence of a binary file with a version level prior to V52. The user will be prompted to perform a conversion but this does not inhibit the other functions of PL7-MMS.

As appropriate, the conversion will be performed on the station MMS Server base, the station MMS.BIN binary file or on the documentation file. There are six possible cases:

• First time PL7-MMS V52 is run on the current station

The program detects an MMS Server base and/or an MMS.BIN file with a version level prior to V52.

Action:

Result:

Select the Utilities/Conversion function, then invoke Conversion.

The MMS Server base will be updated along with its binary file, if this is necessary.

• Using the PL7-MMS V52 Documentation/Generate function

This function detects a V52 level base but the MMS.BIN binary file present in the station has a version level prior to V52.

Action:

Result:

Select the Utilities/Conversion function, then invoke the Conversion and

Documentation/Generate actions.

The MMS.BIN file is updated to V52 level and the documentation is generated.

• Using the PL7-MMS V52 Transfer/Disk --> PLC function

This function detects a V52 level base but the MMS.BIN binary file present in the station has a version level prior to V52.

Action:

Result:

Select the Utilities/Conversion function, then invoke the Conversion and

Transfer/Disk --> PLC actions.

The MMS.BIN file is updated to V52 level and the transfer is performed.

__________________________________________________________________________________________

1 / 3

__________________________________________________________________________________________

• Using the PL7-MMS V52 Transfer/PLC --> Disk function

This function detects a V52 level local base and MMS.BIN binary file, but the MMS.BIN

file present in the PLC has a version level prior to V52.

Action: Save the local binary file, if necessary, prior to invoking

Transfer/PLC -> Disk.

Result: The local V52 level MMS.BIN file is replaced by the MMS.BIN binary file with a version level prior to V52, taken from the PLC.

• Using the PL7-MMS V52 Utilities/View function in local memory

This function detects a V52 level base but the MMS.BIN binary file present in the station has a version level prior to V52.

Action : Select the Utilities/Conversion function, then invoke the Conversion and

Utilities/View actions.

Result : The MMS.BIN file is updated to V52 level and viewing of the file is allowed.

• Selecting the PL7-MMS V52 Utilities/View function in PLC memory

This function detects a V52 level base but the MMS.BIN binary file present in the PLC has a version level prior to V52.

Action : Save the local binary file, if necessary, prior to invoking

Transfer/PLC -> Disk. Then invoke the Utilities/Conversion and

Utilities/View (in local memory) or Transfer/Disk --> PLC (in PLC memory) actions.

Result: The MMS.BIN file is updated to V52 level and viewing of the file is allowed.

__________________________________________________________________________________________

1 / 4

General 1

__________________________________________________________________________________________

1.3

Accessing PL7-MMS

The user can access the MMS variable configuration software by opening the MMS window corresponding to the station for which MMS variable should be defined.

Primary window

Ecran principal PL7 MMS

Remark

To define variables for the entire project or to define variables for a station, the user must use the PL7-MMS program corresponding to a station in the project.

Menu levels

Memory Configuration (1)

Local

Transfer Documentation (1) Utilities

Conversion

MMS Project Directory Disk ➙ PLC Generate

PLC Remote Variables PLC ➙ Disk View

View

Delete (1)

Local Variables Compare Print Restore (1)

PLC Conf.

Enter Information Save (1)

(1) Options that cannot be selected when PLC memory is selected

Memory Selects the working memory.

Configuration Configures MMS variables, calls-up XTEL-SDBASE, generates the MMS.BIN file.

Transfer Uploads, downloads and compares MMS. BIN files between the dedicated MMS field and the PLC memory and vice versa. These actions are performed via XTEL-TRANSFER for V5 level stations and via PL7-MMS functions for V4 level stations.

__________________________________________________________________________________________

1 / 5

__________________________________________________________________________________________

Documentation Creates customized documentation for the MMS application and allows the user to view and print this documentation.

Utilities • Displays a binary file:

- Present on-disk, if the working memory is the local memory,

- Present in the PLC, if the working memory is the PLC memory.

• Deletes the MMS.BIN, MMS.SCY, MMS.CST, MMS.CRT,

MMS.TIT, MMS.DOC and MMS.STR files from the workstation disk.

• Saves and Restores MMS.BIN files.

Exit

Help

Quits PL7-MMS.

Calls-up on-line help screens.

__________________________________________________________________________________________

1 / 6

Selecting the Working Memory - Memory Menu 2

__________________________________________________________________________________________

2.1

Memory Menu

The PL7-MMS main menu lets the user select one of two working environments: Local memory, where the workstation disk is used or PLC memory.

When Local memory is selected, all functions can be accessed. The configuration of local or remote MMS symbols, project level directory configuration and the documentation can be defined without requiring connection to a PLC.

When PLC memory is selected, MMS variable configuration and file delete, save and restore actions cannot be performed. Naturally workstation connection to the PLC must be established in local mode via the PLC programming port, or in remote mode via station connection to a network.

Inhibited functions are dimmed in the main menu.

The table below summarizes the functions available in the various environments.

FUNCTIONS

MMS Variable Configuration

Transfer\Disk ➙ PLC

Transfer\PLC ➙ Disk

Transfer\Compare

Documentation

Utilities\View

Utilities\Delete

Utilities\Restore

Utilities\Save

Utilities\Conversion

WORKING MEMORY

Yes

Local

Yes

PLC

Yes

__________________________________________________________________________________________

2 / 1

__________________________________________________________________________________________

2 / 2

Configuring Variables 3

__________________________________________________________________________________________

Configuring Variables

The purpose of this function is to establish the list of variables for the entire project, i.e.

for all stations in the XTEL project. Then for each station, the user will need to establish a list of remote variables that are visible to the station along with a list of local variables that are visible to other stations.

The remote or local variables can be simple or structured types. When they are structured, the structure format must be described.

The Configuration action also allows the user to generate an MMS.BIN binary file that can be loaded into the PLC.

3.1

Editing the MMS Directory at Project Level

Selecting Configuration\MMS Project Directory will display the following menu:

This function lets the user establish a list of simple or structured variables for the entire project.

The Define Remote Variables sub-menu lets the user define a list of project variables.

The Define Structures sub-menu lets the user describe the format of structures assigned to STRUCT type variables.

__________________________________________________________________________________________

3 / 1

__________________________________________________________________________________________

3.1-1 Defining Remote Variables

Selecting Define Remote Variables will display the following menu.

Selecting Enter, displays the Variable Editor with the following screen

The records, where they exist, are shown as a list in alphabetical order.

The various fields in a record can be filled-in and comprise:

Application Name

This field identifies the MMS application that the variable belongs to. An application name comprises alphanumeric characters and is restricted to a maximum length of 32 characters.

Variable Name

This field identifies the MMS variable. A variable name comprises the following characters: A to Z, a to z, 0 to 9 and $, _

A variable name cannot begin with a number and is restricted to a maximum length of

32 characters.

Scope

This field defines the scope of the MMS variable. The values allowed are VMD, DOMAIN and AA.

__________________________________________________________________________________________

3 / 2

Configuring Variables 3

__________________________________________________________________________________________

Dom/Appli Name

If the scope of the variable is defined as DOMAIN, this field must be filled-in to indicate the name of the domain. A domain name comprises the following characters: A to Z, a to z, 0 to 9 and $, _

A domain name cannot begin with a number and is restricted to a maximum length of

32 characters.

If the scope of the variable is defined as AA this field must be filled-in to indicate the name of the application that has the right to access the variable.

Type

This field defines the type of MMS variable.

Type Inf

For some types, additional information is required. This is the purpose of the Type_Inf field. E.g. when using a Table type variable, the Type_Inf field indicates the number of elements in the table.

Type of MMS Variables - Simple Type

BOOL

INT16

INT32

UINT16

UINT32

BSTR

VSTR

OSTR

STRUCT

FLOAT

: Boolean

: 16-bit signed integer

: 32-bit signed integer

: 16-bit unsigned integer

: 32-bit unsigned integer

: BitString

: VisibleString (character string)

: OctetString (byte string)

: Structure

: Floating point simple precision

Type_Inf

1...2048

2...4096-even

Type of MMS Variables - Table Type

AR-BOOL

AR-INT16

AR-INT32

AR-UINT16

AR-UINT32

AR-BSTR1

: Boolean table

: 16-bit signed integer table

: 32-bit signed integer table

: 16-bit unsigned integer table

: 32-bit unsigned integer table

: BitString1 table

AR-VSTR2

AR-OSTR2

: VisibleString (character string) table

: OctetString (byte string) table

AR-STRUCT : Structure table

AR-FLOAT : Floating point simple precision table

Type_Inf

Number of table elements up to a maximum

MAX = 1024

__________________________________________________________________________________________

3 / 3

__________________________________________________________________________________________

Once all record fields are filled-in, the user can select the following actions:

Add

To add the new MMS variable to the existing list.

Modify

To replace the selected record with the newly entered one.

Delete

To delete the record selected from the list.

A single click on a record in the list will select it. A double click will select it and allow the user to fill-in the data entry fields. This operation provides the user with an easy way of changing a field in the record.

The list can display up to 512 MMS variables. The Next and Return buttons are used to view all of the variables, when their total number exceeds 512. The maximum number of variables is restricted to 2048.

Once data entry is complete, the following functions can be selected:

To validate all of the modifications made. Selecting OK will generate the project file. This file is an ASCII file that contains all of the records.

Once generation is complete, a message indicates that the MMS Project directory has been generated and a new screen displayed.

Cancel

To Quit the editor without making any changes. This action must be confirmed.

__________________________________________________________________________________________

3 / 4

Configuring Variables 3

__________________________________________________________________________________________

Selecting Retrieve will display the following window so that the user can designate a file by its name and access path.

This function lets the user import variables defined in a generic file stored in Telemecanique format. A Retrieve action will overwrite any existing MMS_PRJ.REP project directory.

__________________________________________________________________________________________

3 / 5

__________________________________________________________________________________________

In the same way, a project directory can be saved for reuse from another station, for example.

Enter the directory path and name:

3.1-2 Defining Structures Associated with Remote Variables

Selecting Define Structures will display the following menu.

Selecting Enter, displays the structured variables format entry screen:

__________________________________________________________________________________________

3 / 6

Configuring Variables 3

__________________________________________________________________________________________

The screen will then display two lists:

• A list of structures: To add or modify a structure name, to delete or select a structure,

• A list of elements in the structure to describe the format of the structure selected from the list of structures.

Important:

The user must define a structure for each structured type variable (STRUCT) in the project directory. The name of the structure built must be the same as the name of the

MMS variable defined in the project directory.

The principle is to create a list of structure names and then, for each structure, configure a list of elements that compose the structure.

To prepare the list of structures, the following actions are allowed:

Add

Modify

Delete

Adds a new structure name to the list.

Modifies the name of the structure selected from the list.

Deletes the name of the structure from the list.

After entering a structure name, the user must describe the elements that form the structure by filling-in the various fields:

Element Name This field lets the user give each element in the structure a different name. An element name comprises alphanumeric characters and is restricted to a maximum length of 32 characters.

Type

Type Info

This field defines the type of element in the structure.

For some types, additional information is required. This is the purpose of the Type_Inf field.

E.g. when using a Table type variable, the Type_Inf field indicates the number of elements in the table.

__________________________________________________________________________________________

3 / 7

__________________________________________________________________________________________

Type of MMS Structure Elements - Simple Type Type_Inf

BOOL

INT16

INT32

UINT16

UINT32

BSTR

VSTR

OSTR

STRUCT

FLOAT

: Boolean

: 16-bit signed integer

: 32-bit signed integer

: 16-bit unsigned integer

: 32-bit unsigned integer

: BitString

: VisibleString (character string)

: OctetString (byte string)

: Structure

: Floating point simple precision

1...2048

2...4096-even

Type of MMS Structure Elements - Table Type

AR-BOOL

AR-INT16

AR-INT32

AR-UINT16

AR-UINT32

AR-BSTR1

: Boolean table

: 16-bit signed integer table

: 32-bit signed integer table

: 16-bit unsigned integer table

: 32-bit unsigned integer table

: BitString1 table

AR-BSTR16 : BitString16 table

AR-VSTR2 : VisibleString (character string) table

AR-OSTR2 : OctetString (byte string) table

AR-STRUCT : Structure table

AR-FLOAT : Floating point simple precision table

Type_Inf

Number of table elements up to a maximum

MAX = 1024

Once all record fields for an element selected from the list are filled-in, the user can select the following actions:

Modify To replace the element selected from the list with the element described in the various data entry screens.

Delete

Insert before

To delete the element selected from the list.

To add the new element to the list before the element selected in the list.

Insert after To add the new element to the list after the element selected in the list.

The user can declare all elements forming each structure and their types in the same way.

__________________________________________________________________________________________

3 / 8

Configuring Variables 3

__________________________________________________________________________________________

Warning

A structured MMS variable comprises a series of simple type elements. To program reading or writing of a structured variable using the MREAD or MWRIT OFBs (refer to Divider F), ensure that a string of Wi words is reserved for them and respect the memory organization conventions are follows:

Each element in a structured variable is aligned with the start of a Wi word, regardless of the actual space required to store the field value.

Warning

If the MMS variable type is AR_STRUCT (and not STRUCT), the description of the structured variable as entered after selecting the Define Structures action from the menu, must not comprise AR_x type elements. The Type_Inf field in the description of the variable after selecting Define Remote Variables from the menu must contain the number of elements from the AR_STRUCT table (the number of structures).

This number is restricted to 16 elements, given that the maximum size of a

STRUCTURE or an AR_STRUCTURE can never exceed 4 Kbytes.

Example:

ALARM_TEMPERATURE

{ Number

Status

: Integer16

: BitString18

Location

Identification

: OctetString6

: Array of 3 Boolean }

If the MMS variable: ALARM_TEMPERATURE is assigned to the PL7-3 variable W0 the result is:

Number

Status

Location

Identification

Placed in word W0.

Placed in words W1 and W2 using bits W1,0...W1,15 and W2,0...W2,1.

Placed in words W3, W4 and W5.

Placed in word W6 using bits W6,0...W6,2.

Once data entry is complete for the list of structures and their elements, the following functions can be selected:

To validate all of the modifications made. Selecting OK will generate the project file. This file is an ASCII file that contains all of the structures and their formats.

Once generation is complete, a message indicates that the MMS Project directory has been generated and a new screen displayed.

Cancel

To Quit the editor without making any changes. This action must be confirmed.

__________________________________________________________________________________________

3 / 9

__________________________________________________________________________________________

Selecting Retrieve will display the following window so that the user can designate a file by its name and access path.

This function lets the user import structures defined in a generic file stored in

Telemecanique format. A Retrieve action will overwrite any existing structures file present at project level.

In the same way, a structures file can be saved for reuse from another station, for example.

__________________________________________________________________________________________

3 / 1 0

Configuring Variables 3

__________________________________________________________________________________________

Enter the directory path and name:

3.2

Configuring Remote Variables

Selecting Configuration - Remote Variables will call-up an XTEL-SDBASE screen to allow the user to modify data base symbols.

This function lets the user declare, for the currently selected station, a list of remote MMS variables to be read or written. These variables will be taken from the variables available in the project directory.

Remote variables all also referred to as "Client" variables.

To configure a remote variable, simply associate a project directory variable to a symbol designating a CWi object in the data base. This symbol is called a PL7-3 Alias. The Alias is used by PL7-3 OFBs to access MMS variables.

__________________________________________________________________________________________

3 / 1 1

__________________________________________________________________________________________

The configuration procedure is as follows:

1. Create a PL7-3 Alias in the PL7-3 window. To do this, enter a CWi in the Variable column and an associated symbol in the Symbol column. The variable entered can have a comment of up to 24 characters.

2. The newly defined symbol is then repeated in the Symbol data entry field in the top

MMS screen, once the user has confirmed the previous data entry made. There are two possible cases:

• The symbol is already assigned to an MMS variable in the MMS project directory and this variable and its characteristics will be displayed in the MMS window,

• The symbol is not assigned to an MMS variable so that the user can select the

Application Name field, and then press <Spacebar> followed by <Enter> to display a window with a list of all of the variables in the project directory. At this point simply select a variable from the list so that it will be automatically assigned to the newly entered symbol.

The symbol can be selected faster if the user knows the name of the application where the variable is located.

From the window that displays the list of variables, the user can enter the

Application Name in a dedicated field and confirm the entry.

The list will then start its display from the first variable belonging to this application.

Warning

A PL7-3 Alias is always a symbol assigned to a CW object.

PL7-MMS creates the constant source file MMS.CST, in a fully user-transparent manner. This file contains the PL7-3 Aliases with as the value of each Alias, the position in the table of remote symbols of the MMS variable that it is assigned to.

__________________________________________________________________________________________

3 / 1 2

Configuring Variables 3

__________________________________________________________________________________________

MMS.CST file example:

Alarm

LED

Pressure

= 0

= 1

= 2

The MMS.CST file must be read by the READ function accessed via 3 - CONSTANT in

PL7-3.

To ensure that each Alias generated in PL7-MMS exists in the PL7-3 base, the tool automatically generates an MMS.SCY file that contains each Alias and its corresponding CWi.

MMS.SCY file example:

CW10 = Alarm

CW11 = Led

CW12 = Pressure

The constant words used are not necessarily consecutive in memory.

The MMS.SCY file can be merged with the other symbols in XTEL-SDBASE in the Local station, if the user has any doubt whether all symbols are valid. Therefore, to program a read action, simply designate the variable with the XTEL-SDBASE Alias that represents it in PL7-3. Programming exchange OFBs is simplified in this way and is performed using symbolic programming. The Alias is entered as an input parameter for the MREAD, MWRITE and MURCV OFBs.

Important

The maximum number of remote variables is set to 512 per station.

Warning

Any modification to the Project Directory, variables or structures can create incoherences between the files of station variables or structures. No automatic check is performed to ensure coherence between project files and station files. The user must always ensure coherence.

In the same way, the user must ensure data coherence in constant word (CST/SCY) files and the structure definition files. For this reason, it is recommended that all files be saved each time a Save action is performed.

__________________________________________________________________________________________

3 / 1 3

__________________________________________________________________________________________

3.3

Configuring Local Variables

Selecting Configuration - Local Variables will display the following menu.

3.3-1 Defining Local Variables

Selecting Define Local Variables will call-up an XTEL-SDBASE screen so that the user can manage data base symbols.

This function is designed to allow the user to declare, for the station being programmed, the list of local MMS variables that are visible to, and accessible by other stations in the project. These variables can be read or written by other stations, including stations outside of the XTEL project.

The local variables are also referred to as Servers.

To configure a local variable, simply assign a symbol designating an MMS variable to a symbol designating a PL7-3 object in the data base.

The configuration procedure is described below:

1. Enter the values for the VALUE, SYMBOL and COMMENT in the PL7-3 view:

VALUE: The name of a PL7-3 object (Wi, CWi, etc.) in 21 alphanumeric characters,

SYMBOL: An MMS variable alias for use by XTEL-SDBASE in 8 alphanumeric characters,

COMMENT: Lets the user assign a comment of up to 32 alphanumeric characters to the MMS variable.

2. Once the symbol is defined, it is automatically copied to the symbol window in the

MMS view.

• If this symbol is already assigned to an MMS variable, then the MMS variable and its characteristics are displayed in the MMS view,

• If this symbol is not assigned to an MMS variable, then the Variable Name,

Scope, Type, Type_Inf and Application Name fields are blank and must be filledin.

__________________________________________________________________________________________

3 / 1 4

Configuring Variables 3

__________________________________________________________________________________________

The various fields in an MMS variable record comprise:

Variable Name

This field identifies the MMS variable. A variable name comprises the following characters: A to Z, a to z, 0 to 9 and $, _

A variable name cannot begin with a number and is restricted to a maximum length of

32 characters.

Scope

This field defines the scope of the MMS variable. The values allowed are VMD, DOMAIN and AA. When an AA (Association) scope is selected, the user must give an application name in the appropriate field. In this case only the designated application can access the variable. The scope of a designated variable is filled-in implicitly with default values selected according to the PL7-3 object.

PL7-3 Object

SYi

Bi, Wi,j

Wi, SWi, CWi

DWi, CDWi

Array of Bi

Array of Wi, CWi

Array of DWi, CDWi

Default MMS Scope

VMD

DOMAIN

Type

This field lets the user define the type of MMS variable. The type field is filled-in implicitly with default values selected according to the PL7-3 view Value field. This field can be modified to select table type variables or to enter other valid types.

• Valid simple types are:

BOOL, INT16, INT32, UINT16, UINT32,

BSTR, VSTR, OSTR, STRUCT, FLOAT.

• Valid table types are:

AR-BOOL, AR-INT16, AR-INT32, AR-UINT16, AR-UINT32,

AR-BSTR1, AR-BSTR16, AR-VSTR2, AR-OSTR2, AR-STRUCT, AR-FLOAT.

Access Mode

This field identifies the access mode selected for a local variable in the MMS application defined in the PLC. Its value is AUTO (the default value to ensure that the Server

Automatic level as defined for V51 is provided) or PROG.

__________________________________________________________________________________________

3 / 1 5

__________________________________________________________________________________________

Type Inf

For some types, additional information is required. This is the purpose of the Type_Inf field.

E.g. when using a Table type variable, the Type_Inf field indicates the number of elements in the table.

PL7-3 Object

SYi

Bi, Wi,j

Wi, SWi, CWi

DWi, CDWi

Array of Bi

Array of Wi, CWi

Array of DWi, CDWi

Default MMS Type

Boolean

Integer16

Integer32

Array of Boolean

Array of Integer16

Array of Integer32

MMS Default Type

Boolean

Integer16

Integer32

Array of Boolean

Array of Integer16

Array of Integer32

Valid Corresponding Types

BitString1

Unsigned16, BitString16

OctetString2, VisibleString2

Unsigned32

Floating Point Simple Precision

Array of BitString1, BitStringN

Array of Unsigned16

Array of BitString16

Array of VisibleString2

Array of OctetString2

OctetString2N, VisibleString2N

Array of Unsigned32

Array of Floating Point

__________________________________________________________________________________________

3 / 1 6

Configuring Variables 3

__________________________________________________________________________________________

MMS Type

BitString

OctetString

VisibleString

Array of OctetString2

Array of VisibleString2

Array of Boolean

Arrary of BitString1

Array of Integer16

Array of Unsigned16

Array of BitString16

Array of Integer 32

Array of Unsigned32

Array of Float

Max. Number of Elements

1...2048

2...4096 - Even

2...1024 - Even

1024

Application Name

This field identifies the remote application that is attempting to access the variable. This field must be filled-in when a variable is assigned an AA (Association) scope. Only an application name designated in this way can access this variable. An application name comprises alphanumeric characters and is restricted to a maximum length of 32 characters.

__________________________________________________________________________________________

3 / 1 7

__________________________________________________________________________________________

3.3-2 Defining Structures Associated with Local Variables

Selecting Define Structures displays the structured variables format entry screen:

The procedure for entering structures associated with local variables is the same as that described for remote variables (refer to Sub-section 3.1-2).

The screen displays two lists:

• A list of structures: To add or modify a structure name, to delete or select a structure,

• A list of elements in the structure to describe the format of the structure selected from the list of structures.

Warning

The user must define a structure for each structured type variable (STRUCT) in the project directory. The name of the structure built must be the same as the name

of the MMS variable defined in the project directory.

The principle is to create a list of structure names and then, for each structure, configure a list of elements that compose the structure.

To prepare the list of structures, the following actions are allowed:

Add Adds a new structure name to the list.

Modify Modifies the name of the structure selected from the list.

Delete Deletes the name of the structure from the list.

__________________________________________________________________________________________

3 / 1 8

Configuring Variables 3

__________________________________________________________________________________________

After entering a structure name, the user must describe the elements that form the structure by filling-in the various fields:

Element Name This field lets the user give each element in the structure a different name. An element name comprises alphanumeric characters and is restricted to a maximum length of 32 characters.

Type

Type Inf

This field defines the type of element in the structure.

For some types, additional information is required. This is the purpose of the Type_Inf field.

E.g. when using a Table type variable, the Type_Inf field indicates the number of elements in the table.

The list of valid types is the same as that described in Sub-section 3.1-2 for remote variables.

Once all record fields for an element selected from the list are filled-in, the user can select the following actions:

Modify To replace the element selected from the list with the element described in the various data entry screens.

Delete To delete the element selected from the list.

Insert before To add the new element to the list before the element selected in the list.

Insert after To add the new element to the list after the element selected in the list.

The user can declare all elements forming each structure and their types in the same way.

Warning

If the MMS variable type is AR_STRUCT (and not STRUCT), the description of the structured variable as entered after selecting the Define Structures action from the menu, must not comprise AR_xxx type elements. The Type_Inf field in the description of the variable after selecting Define Remote Variables from the menu must contain the number of elements from the AR_STRUCT table (the number of structures, refer to Sub-section 3.1-2).

__________________________________________________________________________________________

3 / 1 9

__________________________________________________________________________________________

Once data entry is complete for the list of structures and their elements, the following functions can be selected:

To validate all of the modifications made. Selecting OK will generate the project file. This file is an ASCII file that contains all of the records.

Once generation is complete, a message indicates that the MMS Project directory has been generated and a new screen displayed.

Cancel

To Quit the editor without making any changes. This action must be confirmed.

3.4

Generating an MMS.BIN Binary File

After editing the variables and executing the exit procedure from the editor, the following prompt is displayed:

Yes

No file will be generated and the user will return to the main menu,

Generates the binary file once the validity of the variables has been checked.

If they are correct, the binary file is generated and a message displayed.

If the validity check fails, a message is displayed telling the user the cause of the failure.

For example when creating a (remote or local) structured variable, STRUCT and the format of the structure has not been defined, the following message is displayed:

"At least one structured variable is incorrect and was not generated in the binary file".

Once confirmed by the operator, the message:

"Binary file generated correctly" indicates that the binary file was generated correctly and the faulty variable put aside.

__________________________________________________________________________________________

3 / 2 0

Transferring Binary Files 4

__________________________________________________________________________________________

Transferring Binary Files

This function lets the user transfer a binary file, generated by the Configuration function, from the terminal hard disk to the PLC or module memory. It can also be used to transfer the contents of the dedicated MMS field in the PLC memory to an MMS.BIN file in the workstation.

This function also supports comparisons between an MMS.BIN binary file on disk and the contents of the dedicated MMS field in the PLC memory.

4.1

Uploading to the PLC

This function lets the user transfer the MMS.BIN binary file to the PLC memory.

Remark

An upload can only be performed if the dedicated OSI field was assigned previously in the PLC memory. To perform the assignment, use the following tools:

• For a V4 level station

XTEL-MEM will generate an application file for configuring the memory (xxx.APP

file). This configuration must include a dedicated OSI field.

XTEL-TRANSFER can then be used to upload to the PLC memory, the newly generated xxx.APP file.

• For a V5 level station

XTEL-CONF is used to create the memory structure for the application file. This tool is used to reserve the necessary PLC memory for the OSI.BIN file.

XTEL-TRANSFER can then be used to upload to the PLC memory, the memory structure and its associated application files (such as OSI.BIN), if they exist.

To perform the upload, the workstation must be connected to the PLC.

__________________________________________________________________________________________

4 / 1

__________________________________________________________________________________________

Once the Disk->PLC action is selected from the pulldown menu, the following dialog box is displayed:

Yes Starts the transfer. The message "Transferring..." is displayed to inform the user that the operation is being performed and once it is complete, the message "Binary file transferred correctly" is displayed.

No Aborts the upload action and returns the user to the PL7-MMS main menu.

When execution is complete, the message "Binary file correctly uploaded to the PLC" is displayed.

4.2

Downloading from the PLC

This function transfers the contents of the dedicated MMS field from the PLC memory to the MMS.BIN file on the workstation hard disk.

To perform the download, the workstation must be connected to the PLC.

Once the PLC ➙ Disk option is selected from the pulldown menu, the PLC ➙ Disk

Transfer dialog box is displayed. The sequence of actions is the same as for an Upload.

__________________________________________________________________________________________

4 / 2

Transferring Binary Files 4

__________________________________________________________________________________________

4.3

Comparing the PLC Memory with a Binary File

This function compares the dedicated MMS field in the PLC memory with the MMS.BIN

file stored on disk in the workstation.

To perform the comparison, the workstation must be connected to the PLC.

The procedure is the same as Uploading or Downloading the PLC.

After selecting Compare from the pulldown menu, the comparison is completed when one of two messages is displayed:

"The MMS.BIN file and the binary file in the PLC are identical" or

"The MMS.BIN binary file and the binary file in the PLC are different".

__________________________________________________________________________________________

4 / 3

__________________________________________________________________________________________

4 / 4

Documenting and Printing 5

__________________________________________________________________________________________

Documenting and Printing

The following procedure applies for creating documentation on the configuration of

MMS variables in the station:

• Prepare the documentation title page (create an MMS.TIT file),

• Prepare the documentation footer (create an MMS.CRT file),

• Create the application documentation (for storage in an MMS.DOC file), from the

MMS.TIT and MMS.CRT files created previously and the MMS.BIN file that contains the local/remote I/O descriptions and the MMS.CST, MMS.SCY and MMS.STR files,

• View the finished documentation on-screen or print it out.

5.1

Generating the Documentation

Selecting the Generate option starts creation of the documentation for the station MMS application.

It requires that the user first create the title page and footer, described respectively in the MMS.TIT and MMS.CRT files.

The documentation uses the information contained in the MMS.BIN file that contains the list of variables defined for the station.

The documentation displays the list of MMS variables in two parts, local variables and remote variables (either of these two parts may be absent).

Each variable is described with all of its MMS characteristics, its attributes and links with the PL7-3 application (aliases and variables)

This information is taken from the MMS.CST and MMS.SCY files and from the

MMS.STR file when structured variables are used.

__________________________________________________________________________________________

5 / 1

__________________________________________________________________________________________

5.2

View

Selecting this function lets the user immediatly view on-screen, the newly generated documentation.

The user can scroll the documentation vertically and horizontally. The format displayed corresponds to what can be printed-out.

5.3

Print

When this function is selected, it first displays the list of printers that can be used for printing out the station documentation file.

The <Cancel> button lets the user cancel the printing in progress.

Remark

The station documentation file generated by the station MMS function (the

MMS.DOC file) can be printed out separately and it can also be integrated into the complete documentation file for a V4 or V5 level station.

The integration is performed by XTEL-DOC and it is transparent to PL7-MMS.

__________________________________________________________________________________________

5 / 2

Documenting and Printing 5

__________________________________________________________________________________________

5.4

Entering Information

Entering the title page

When this menu is selected, its data entry fields display the contents of the MMS.TIT file, if it already exists. Else all fields are blank.

Access to a predefined field is by mouse or keyboard and Tab key. Within a field, the user can move between columns and lines using the mouse or the cursor keys.

Various entries are possible:

• Title

• Company

• Department

• Manager

• REV.

• DATE

• REVISION

• DESIGNER

• EXECUTED by

: Application title (64 chars. max.),

: Company name (16 chars. max.),

: Department name in the Company (16 chars. max.),

: Manager's name (16 car. max.),

: File revision level (3 chars. max.),

: File creation or modification date (8 chars. max.)

: Comments on the revision made (32 chars. max.),

: Designer's name (12 chars. max.),

: User's name (12 chars. max.),

The MMS.TIT file generated is an editable ASCII file.

OK Saves the contents of the screen to the MMS.TIT file and exits the screen.

Cancel Exits the screen without saving the MMS.TIT file.

__________________________________________________________________________________________

5 / 3

__________________________________________________________________________________________

Entering the custom footer

This screen lets the user customize the footer that appears at the bottom of every documentation file page. Two strings of characters can be filled-in by the user:

• A string of 25 characters at the top of the footer,

• A string of 45 characters at the bottom of the footer.

The fields are filled-in with the contents of the MMS.CRT file, if it already exists.

The documentation footer provides the following information:

• Application name,

• Printed item name,

• Document version number,

• Print-out date,

• Relative page numbering by item,

• Absolute page numbering.

Cancel

Saves the contents of the screen to the MMS.CRT file and exits the screen.

Exits the screen without saving the MMS.CRT file.

__________________________________________________________________________________________

5 / 4

Viewing MMS Binary Files - Deleting Files - Help 6

__________________________________________________________________________________________

6.1

Viewing MMS Binary Files

The View utility lets the user view variables in an MMS binary file.

If the working environment is the local memory, the binary file viewed is the MMS.BIN

file on disk. If the working environment is the PLC memory, this function will view the contents of the dedicated MMS field in the PLC memory.

6.1-1 Viewing a Binary File on the Workstation Disk

The selected working memory is the local memory (Memory option in the main menu).

Viewing local variables

Once the View option is selected from the pulldown menu, a window is displayed showing a list of local MMS variables.

__________________________________________________________________________________________

6 / 1

__________________________________________________________________________________________

This screen displays the list of local variables stored in the MMS.BIN file. Each line in the list displays the following information:

<PL7_3Object>/<MMSVar>/<Scope>/<Name>/<Type>/<TypeInf>/<Access>/

For example:

W1/Index_01/DOMAIN/MMS/INT16//AUTO/

In the case of structured variables, the structure format is also given and the memory organization that applies to each element, for example:

W10/Product/VMD//STRUCT//AUTO/

{

+0/BOOL/Valid

+1/VSTR 12/Name

+7/INT16/Number

}

Viewing remote variables

Simply selecting Remote Variables will display a list of remote variables. This screen displays the list of remote variables stored in the MMS.BIN file. Each line in the list displays the following information:

<PL7_3Object>/<Alias>/<MMSVar>/<Scope>/<Name>/<Type>/<TypeInf>/

For example:

W1/Index_01/Num_File/DOMAIN/Public/INT16//

In the case of structured variables, the structure format is also given and the memory organization that applies to each element, for example:

W2/Index_02/File/DOMAIN/Public/STRUCT//

{

+0/INT16

+1/BSTR 18

+6/AR-BOOL 3

}

__________________________________________________________________________________________

6 / 2

Viewing MMS Binary Files - Deleting Files - Help 6

__________________________________________________________________________________________

6.1-2 Viewing a Binary File Stored in the PLC

To view the MMS contents of the PLC, select MMS memory as the working memory, then click on the View option in the Utilities menu.

The function will read the PLC memory contents and display the view screen.

6.2

Deleting Files

The Delete utility lets the user delete all of the files generated by PL7-MMS.

Once this option is selected, simply click on the type of file to delete. Regardless of the file type, the procedure is the same: select the file from the dialog box that opens and confirm the selection. Once the file is deleted, control returns to the updated dialog box.

This operation can be repeated as many times as there are files to delete.

When there are no more files of a given type to delete, the corresponding option is deleted.

__________________________________________________________________________________________

6 / 3

__________________________________________________________________________________________

6.3

Saving/Retrieving MMS.BIN Files

Selecting the Retrieve action displays a sub-menu that allows the user to designate the type of file to retrieve.

After selecting the action, simply click on the required type of file. The procedure is the same for all file types. The user must always give the access path and the name of the file to copy to the MMS field.

__________________________________________________________________________________________

6 / 4

Viewing MMS Binary Files - Deleting Files - Help 6

__________________________________________________________________________________________

In the same way, MMS .BIN, .SCY, .CST or .STR files (for local structures) can be saved for use with another station for example.

Regardless of the type of file used, the procedure is always the same. The user must enter the full path name and target file name.

6.4

Help

The Help option in the pulldown menu lets the user access to root directory of PL7-MMS help screens.

The About... option displays information on the current version of the installed software.

__________________________________________________________________________________________

6 / 5

__________________________________________________________________________________________

6 / 6

Appendix 7

__________________________________________________________________________________________

Appendix

Project Directory File Format

Variables File Format

The MMS_PRJ.REP file can also be created or modified using a standard text editor.

In this case, it must correspond to the preset Telemecanique format.

Compatibility rules:

• Records must be stored in alphabetical order based on application name, followed by the MMS variable name,

• A record contains all of the fields required to describe the variable. Each field is separated by a / ,

• // indicates an omission,

• # at the start of a line indicates a comment,

• The end of each record is indicated by the <Carriage Return> <Line Feed> characters.

Format:

/<AppName>/<MMSName>/<Scope>/<DomainName or AppName>/<Type>/

Structures File Format

The MMS_PRJ.STR file can also be created or modified using a standard text editor. In this case, it must correspond to the preset Telemecanique format.

Compatibility rules:

• Structures must be stored in alphabetical order based on the structure name,

• A structure element contains its name, type and where necessary the TypeInf field.

The various fields that describe the structure elements are separated by a / ,

• // indicates an omission,

• The end of each record is indicated by the <Carriage Return> <Line Feed> characters.

Format:

TEMP_ALARM

{

Number/INT16//

States/BSTR/18/

Location/OSTR/6/

Identification/AR-BOOL/3/

}

__________________________________________________________________________________________

7 / 1

__________________________________________________________________________________________

7 / 2

________________________________________________________

MMS OFBs F

___________________________________________________________________________

Section

1 General

1.1

PL7-OSI 3.0 OFB Presentation

1.2

Installing OFBs

1.3

Configuring OFBs

1.4

Using OFBs

Page

1/1

1/2

1/4

2 MMSLD OFB

2.1

Using the MMSLD OFB

2.1-1 Application Modification

2.1-2 Module Memory Loss

3 MMS Services OFBs

3.1

Reminders on MMS Application Design

3.2

Programming MMS OFBs

3.2-1 Characteristics Common to all MMS OFBs

3.2-2 Implementation Principles

3.3

MCNCT OFB: Association Management

3.3-1 Function

3.3-2 PL7-3 Interface

3.3-3 Using the MCNCT OFB

3.3-4 Programming the MCNCT OFB

3.4

MREAD OFB: Read MMS Client Variables

3.4-1 Function

3.4-2 PL7-3 Interface

3.4-3 Using the MREAD OFB

3.4-4 Programming the MREAD OFB

3.5

MWRIT OFB: Write MMS Client Variables

3.5-1 Function

3.5-2 PL7-3 Interface

3.5-3 Using the MWRIT OFB

3.5-4 Programming the MWRIT OFB

2/1

___________________________________________________________________________

F / 1

3/11

3/15

3/1

3/2

3/4

3/21

3/26

3/28

3/32

________________________________________________________

___________________________________________________________________________

Section

3.6

MURCV OFB: Unsolicited Data (Client Mode)

3.6-1 Function

3.6-2 PL7-3 Interface

3.6-3 Using the MURCV OFB

3.6-4 Programming the MURCV OFB

3.7

MRSTA OFB: Device Status (Client Mode)

3.7-1 Function

3.7-2 PL7-3 Interface

3.7-3 Using the MRSTA OFB

3.7-4 Programming the MRSTA OFB

3.8

MUSND OFB: Sending Unsolicited Data (Server Mode)

3.8-1 Function

3.8-2 PL7-3 Interface

3.8-3 Using the MUSND OFB

3.8-4 Programming the MUSND OFB

3.9

MSSTA OFB: Sending Device Status (Server Mode)

3.9-1 Function

3.9-2 PL7-3 Interface

3.9-3 Using the MSSTA OFB

3.9-4 Programming the MSSTA OFB

4 MSEMA OFB: Synchronizing Access to an MMS Server

Variable

4.1

Function

4.2

PL7-3 Interface

4.3

Using the MSEMA OFB

4.4

Programming the MSEMA OFB

Page

3/34

3/38

3/40

3/42

3/44

3/48

3/50

3/53

4/1

4/2

4/6

5 Appendix

5.1

Error Handling

5.2

MMS Service Execution Error Indications (IND)

5.3

Error Codes Returned to Status by MMSLD V2.0

5.4

Adding an MMS Variable to an Existing Project

5/1

5/3

5/5

5/6

___________________________________________________________________________

F / 2

General 1

__________________________________________________________________________________________

1.1

PL7-OSI 3.0 OFB Presentation

The PL7-OSI 3.0 V2 OFB library comprises the MMSLD OFB and MMS service OFBs.

The MMSLD OFB is an executable PLC program that automatically monitors uploads the OSI configuration and the table of MMS local variables to the OSI modules

(TSX ETH 200). Uploading is performed from the dedicated OSI and MMS fields in the

PLC memory.

The MMS Service OFBs are an extension of PL7-3 language. They implement the Client functions and some Server functions for TSX ETH 200 modules.

The MCNCT, MREAD, MWRIT, MURCV, MRSTA OFBs are dedicated to MMS Client functions while MUSND and MSSTA OFBs are dedicated to MMS Server unsolicited services.

The MMS Client services that can be programmed in a PL7-3 application via the

TSX ETH 200 module Client function are:

Initiate, Conclude, Abort

Using the MCNCT OFB that allows the PL7-3 application to open, close or interrupt an assignment to a remote MMS Server application, it also enables the user to identify an assignment opened by a remote application.

Read, Write

Using the MREAD and MWRIT OFBs that allow the PL7-3 client application to read or write 1 to 4 variables to a remote device.

Status, UnsolicitedStatus

Using the MRSTA OFB that allows the user to acquire the status of remote device, as an explicit or unsolicited request.

Receiving unsolicited data: InformationReport

Using the MURCV OFB.

The MMS Server services that can be programmed into a PL7-3 application are:

Send unsolicited data: InformationReport, UnsolicitedStatus

Using the MUSND and MSSTA OFBs that when executed send data or status information to a remote MMS client device via the Server functions of OSI/MMS V2 interface modules.

The functions and programming modes for each OFB is described in the remaining sections of this divider.

MMS OFBs are supplied with the PL7-OSI 3.0 software on a separate diskette using the same rights of access. They are part of the MMS family.

__________________________________________________________________________________________

1 / 1

__________________________________________________________________________________________

1.2

Installing OFBs

The MMS OFBs must be installed on the workstation hard disk in order to be used. The installation procedure is described in Divider B, Section 1.

1.3

Configuring OFBs

Before using an OFB in an application program, it must first be configured. This operation is performed using PL7-3.

Configuration comprises:

• Declaring the type of OFB so that the executable code can be loaded into the OFB program field in memory,

• Defining the number of OFBs used in order to define the OFB constants and data fields in memory.

To perform these actions:

• Select PL7-3 and select 1 - Configuration from the main menu,

• From the Configuration Mode selection screen, select 5 - Optional Function Blocks.

The OFB Configuration screen displays a list of OFB types already declared and the number of OFBs per type.

• If the OFB is not present in this list, press the [New OFB] dynamic function key. A new screen lets the user view the list of OFBs available on the hard disk. Use the

[PREV FAM] and [NEXT FAM] dynamic function keys to select the required MMS family and use [INS] to select the type of OFB required for the application.

__________________________________________________________________________________________

1 / 2

General 1

__________________________________________________________________________________________

• After confirming the selections made, the OFB Configuration screen is displayed once again. The [MODIFY] command lets the user define the number of OFBs to use for the declared type. The user should configure an OFB for each network interface module in the station. For example, a station with four interface modules should have four MMSLD OFBs.

For further information refer to the PL7-3 Operating Modes documentation

(TXT DM PL7 3 V5E).

__________________________________________________________________________________________

1 / 3

__________________________________________________________________________________________

1.4

Using OFBs

To implement an MMS OFB, the user must perform the steps listed below:

1. Configure the module using PL7-OSI. Configure the MMS Client and MMS Server symbol data bases using PL7-MMS.

2. Define the local XTEL-SDBASE symbols used by the application so that the OFB inputs can be symbolically wired.

3. Configure and program the OFB using PL7-3.

Configure the number of times (instances) each OFB must be used.

Initialize the constants assigned to the MMS Client identifiers by executing a PL7-3

Read command on the MMS.CST file.

4. How to program each OFB is described in detail in Divider F, Section 3.

__________________________________________________________________________________________

1 / 4

MMSLD OFB 2

__________________________________________________________________________________________

2.1

Using the MMSLD OFB

The MMSLD OFB operates in implicit execution mode: the application designer does not program it in the PL7-3 application. It will run regardless of PLC state (Run or Stop).

The MMSLD OFB executes its upload function under the following conditions:

• When the OSI/MMS configuration of the application STATION.APP is modified by the designer,

• When the contents of the memory are lost due to a failure or an interface module replacement.

2.1-1 Application Modification

When the dedicated OSI or MMS fields in the PLC memory are modified, this field is automatically uploaded to the assigned interface module memory.

Loading a new application (STATION.APP) or binary file (OSI.BIN or MMS.BIN) modifies either of the dedicated OSI or MMS fields and therefore causes uploading to the module memory.

2.1-2 Module Memory Loss

The MMSLD OFB continually monitors the TSX ETH 200 modules present in the PL7-3 application I/O configuration.

Monitoring the interface comprises detecting loss or alteration to OSI parameters or of the table of symbols in the interface module memory. If the OSI or MMS configuration is lost, the MMSLD OFB automatically loads the interface module memory from the dedicated OSI and MMS fields in the PLC memory.

__________________________________________________________________________________________

2 / 1

__________________________________________________________________________________________

2 / 2

MMS Services OFBs 3

__________________________________________________________________________________________

3.1

Reminders on MMS Application Design

A TSX/PMX station that uses MMS services to communicate with other stations, via one or more TSX ETH 200 modules is considered in XTEL as a Local Application that establishes exchanges with Remote Applications. In normal operation, associations are opened between the Local Application and Remote Applications. Each of these associations is a communication channel that is used to exchange data in Client/Server mode. The data exchanges are established with MMS variables identified with symbols common to all of the applications.

MMS application development implies declaration and definition at project level of each

Remote Application and of each MMS variable assigned to each Remote Application.

Once the common data base is established, each station - application - developed, will be configured so that the Remote Applications that are visible to it are designated. In addition, its Local Application characteristics are configured in each OSI module.

PL7-OSI is the tool used to perform the configuration tasks.

In parallel, PL7-MMS lets the user establish, for each station, the link between the MMS name of each MMS variable as seen by the Local Application, and a symbol ("Alias") in the PL7 local data base (in XTEL-SDBASE).

If the variable takes a value that is significant in the Local Application (application PL7-3 object) that will be read or written by a Remote Application, it will be declared for the Local

Application as a local MMS variable and assigned to a PL7-3 variable.

If it is a variable that is significant in a Remote Application, and it will be read or written by the Local Application, it will be declared as a remote MMS variable and its "Alias" in the local data base will be assigned to a CW (Constant Word) variable, the value of which will be a pointer to the table of remote MMS variables.

Before programming the OFBs in PL7-3, it is essential to ensure coherence with the development environment, by loading the MMS.CST file and, if necessary, by merging

MMS.SCY into the station data base.

It is important to note, at MMS application programming level, the following points:

In PL7-3, the fundamental symbol data base is managed by XTEL-SDBASE at station level. This data base ensures the link between the "Alias" (symbol) and the

PL7-3 variable (object).

OFBs are programmed symbolically. The symbols used are the PL7-3 "Aliases".

When an OFB input needs to be wired with an MMS variable, the variable is designated by its "Alias" and not by its MMS symbol.

The system will manage all necessary assignments, on compilation or execution, based on the tables of variables established using PL7-MMS.

__________________________________________________________________________________________

3 / 1

__________________________________________________________________________________________

3.2

Programming MMS OFBs

This Sub-section presents some of the characteristics common to all MMS OFBs and the principles that apply to their implementation. The principles that apply to interfacing with PL7-3 data are covered in particular.

Each of the OFBs is described in detail in the following Sub-sections.

3.2-1 Characteristics Common to all MMS OFBs

a. Like all communication OFBs, MMS OFBs require more than one PLC cycle to execute.

b. Call not maintained

OFB execution is implicitly maintained by the system, therefore the user need only program execution of the block. When using Literal language, the program line could be:

! IF NOT B0 THEN EXEC OFBi(... =>...); SET B0 giving the following advantages:

* Parameters are sent only once, ensuring a considerable gain in performance.

* Programming is simplified as the programmer does not need to maintain the call to the

OFB while execution is in progress.

However, the output parameters are ignored as the variables that should be wired will not be refreshed. Therefore the outputs are public internal data interprets as results.

Correct programming practice could be:

! IF NOT B0 THEN EXEC OFBi(... => ...); SET B0

! <WAIT>

! IF NOT OFBi, READY THEN JUMP L10

Note

The OFBs have a Bit type output parameter, the Error bit that is used for diagnostic purposes. This bit must not be wired. Error must be used as an internal result parameter.

__________________________________________________________________________________________

3 / 2

MMS Services OFBs 3

__________________________________________________________________________________________ c. Diagnostics characteristics

The OFBs can be used by APPLIDIAG. For this reason, they all have a bit type output,

ERROR and an internal public data bit INHIB.

When ERROR is set to 1, it indicates an error found by the function block. The error is indicated in one or more WORD and DWORD type data, STATUS and STATUSn. The number of STATUSi words and the meanings assigned to their states are described in detail in the description of each OFB.

INHIB is a public internal data bit that can be used to inhibit the indication of errors. If an error occurs, the OFB can continue execution as ERROR and STATUS always remain at 0.

d. RESET and READY bits

As the MMS OFBs are executed over a number of PLC cycles, the RESET input parameter can be used to interrupt OFB execution while it awaits the response to a message. In the same manner, OFBs have a public internal data bit READY that indicates execution in progress.

The READY bit

! IF NOT B0.MCNCT0,READY

THEN EXEC MCNCT0(;Initiate;CplMap;ORDO_APP;200=> ...);

SET B0

! <WAIT>

! IF NOT MCNCT0, READY THEN JUMP L500

! IF MCNCT0, ERROR THEN JUMP L999

! <The association is open. It will be repeated until closed>

! <by ORDO.>

! IF [MCNCT0, STATE=0] THEN MCNCT0,CHANNEL->ORDO

! <Program continues...>

The RESET action

The bit type RESET input is used to interrupt execution when the bit is set to 1. Any messages in progress are lost. The READY and ERROR bits are set to 1. STATUS indicates a user requested stoppage. The OFB is ready to be executed again. Writing the RESET input by UNI-TE request is allowed, i.e. using APPLIDIAG or PL7-3 Adjust and Data modes for example, with the PLC running or stopped.

A RESET action on an idle OFB (READY bit at 1) will reset the ERROR and STATUS public internal data to 0 along with any data interpreted as an output.

__________________________________________________________________________________________

3 / 3

__________________________________________________________________________________________

3.2-2 Implementation Principles

MMS Client/Server communication is implemented in three phases:

• Open a transmission channel that associates the Client to the Server,

• Perform exchanges on this temporary point-to-point data link,

• Close the association.

Remark

Before attempting to close an association, ensure that all exchanges in progress are completed: test the READY bits of the MMS OFBs to ensure that they are at 1.

The functions implied by these three phases are performed by MMS OFBs.

Association identification

• Case 1: The application initiates the call

The MCNCT OFB associates an MMS Client and Server, i.e. the PL7-3 application assigns the TSX/PMX PLC to a remote device, via a TSX ETH 200 module located in the PLC rack.

MCNCT requires as input parameters, the name of the remote MMS application to assign and the number of the interface module slot location in the rack.

Any subsequent exchanges between the two applications are performed via the opened channel (until it is closed). The OFBs that manage the exchange will always refer to this channel, therefore it need only be identified by a simple logical reference.

The MCNCT OFB will assign the logical identifier to the association. The reference is provided in the internal data CHANNEL once the communication channel opening procedure is complete. For simplicity, the reference is the same as the OFB instance number.

To close the association, use the same instance of the OFB.

Note that between the opening and the closing of an association, the MCNCT OFB monitors any change of state in the association caused by the remote device (Abort) or any interface module failure.

To sum up:

The logical number of an association in the calling application is the instance number of the MCNCT OFB that opened it.

An MCNCT OFB manages a single association at a time.

__________________________________________________________________________________________

3 / 4

MMS Services OFBs 3

__________________________________________________________________________________________

• Case 2: The application receives the call

In this case the OFB's ACCEPT parameter is used to retrieve the reference of the communication channel.

To ensure that the correct identifier is used for an association solicited by a remote station, the MCNCT OFBs must be programmed sequentially in Accept mode.

The first Accept must be Ready before starting the execution of the second, and so on, to ensure that the first does indeed receive the association opened by the remote station, and that the second also receives the second association opened by the remote station, and so on.

Remark

Setting SY0 to 1 and resetting the OFBs will cause incoherence between the state of the associations monitored by the OFBs and the true status of the module. Any associations that are opened must therefore be closed first (by conclude or abort) before selecting SY0 = 1.

Remote MMS variables and PL7-3

• Identification of MMS variables

The MMS variables are designated to the OFBs by XTEL-SDBASE symbols (Aliases) assigned to them when the variables are defined using PL7-MMS. These symbols let the OFBs (MREAD, MWRIT and MURCV) that use remote MMS variables to retrieve the complete definition. This is only possible if the MMS.CST file was loaded in PL7-3.

Therefore:

Before programming MMS OFBs always initialize PL7-3 constants using the READ command in PL7-3 to read the MMS.CST file.

• Exchanging the values of remote MMS variables

The MMS variables can be simple type (Boolean, Integer16, etc.) and also simple tables (refer to the table of MMS types).

The OFB input parameters can only be simple bit, word and double word types and not table types. To avoid this problem, the values of MMS variables are sent to the

OFBs according to the following principle:

- A remote MMS variable is defined as an OFB input with three input parameters, one that identifies the variable and the two others that define the size and the address of the buffer where the value of the variable is stored.

In the PL7-3/OFB interface, a remote MMS variable is designated as follows:

__________________________________________________________________________________________

3 / 5

__________________________________________________________________________________________

Mxxx word

VARi word

SIZEi

DATAi ptr_word

F i

Where

VARi Wired with the variable identifier (XTEL-SDBASE Alias).

SIZEi Buffer size (reception) or size of the data to send (transmission). Expressed in bytes.

DATAi Start of buffer address, always a word type.

In transmission mode, the buffer can be located in the system word (SWi), constant word (CWi) or internal word (Wi) fields.

In reception mode (write) only the internal word field (Wi) can be used.

In all cases, the fields used for other word type objects are illegal (register words, common words, Grafcet words).

Decimal integer index between 0 and 3: The Client mode OFBs MREAD and

MWRIT can handle up to 4 variables, except for MURCV that can only be assigned to a single variable.

__________________________________________________________________________________________

3 / 6

MMS Services OFBs 3

__________________________________________________________________________________________

Correspondence between PL7-3 Types and MMS remote variables

The table below shows the MMS types supported and the correspondence established between PL7-3 types (Note: the MREAD and MWRIT OFBs used in the examples are described in later sections).

MMS Type PL7-3 Correspondence

Boolean

Buffer

Size

2 LSB of a word

Example:

! EXEC MREAD(;Server;Vbool;2;W0=>)

! W0,0->B0

Unsigned16

Integer16

Unsigned32

Integer32

BitStringN

PL7-3 word objects

Example:

! EXEC MREAD(;Server;Vint16;2;W0=>)

! W0,0->COM0,0

Double length word objects

Example:

! EXEC MREAD(;Server;Vint32;4;CDW0=>)

Bits from words, where the first bit in the string is stored in the LSB of the first word, the second in the MSB of the first word.

Bit i is stored in the bit of word [j],k where i is the bit number, from 0 to N-1 j = i / 16 k = i mod 16

Example:

! B0->W0,0;B1->W0,1;B2->W0,2;B3->W0,3

! EXEC MWRIT(;Server;Vbool4;2;W0=>)

((N-1)/16

+1)*2 with N>0

OctetStringN Succession of words, where the first byte in the string is stored in the LSB of the first word, the second in the MSB of the first word.

Byte i is stored in the bit of word 256 k of word j where i is the byte number, from 0 to N-1 j = i / 2 k = i mod 2

((N-1)/2

+1)*2 with N>0 or

N/2+

N mod 2

__________________________________________________________________________________________

3 / 7

__________________________________________________________________________________________

MMS Type

OctetStringN

(Continued)

Array of

BitString16

Array of

Unsigned16

Array of

Integer16

Array of

Unsigned32

Array of

Integer32

PL7-3 Correspondence

Example:

! <Write a byte table>

! <{0,1,2,3) -> Vtab(4)>

! H'0100'->W0;H'0302'->W1

! EXEC MWRIT(;Server;Vtab4;4;W0=>)

! <Write a string of 5 chars.>

! <"ABCDE" -> Vstr(5)>

! M'AB'->W0,M'CD'->W1;M'E'->W2

! EXEC MWRIT(;Server;Vstr4;6;W0=>)

Succession of words (stored in the same way as BitStringN)

Example:

! <Read a table of 8 elements>

! EXEC MREAD(;Server;Vtab8;16;W0=>)

Succession of words (stored in the same way as Integer16)

Example:

! <Read a table of 3 elements>

! EXEC MREAD(;Server;Vtab3;6;W0=>)

Succession of double words (stored in the same way as Integer32)

Example:

! <Read a table of 3 elements>

! EXEC MREAD(;Server;Vtab3;12;W0=>)

Buffer

Size

Nbr. of elements x2

Nbr. of elements x4

(*) Warning: The sequence in which the listings are saved in the PLC words is not standardized. For dialog with devices from other vendors, it may be necessary to change the order of the bits by changing the application program in one of the devices to ensure coherence.

__________________________________________________________________________________________

3 / 8

MMS Services OFBs 3

__________________________________________________________________________________________

MMS local variables and PL7-3

• Identifying MMS variables

The local MMS variables as seen by a PL7-3 application use XTEL-SDBASE Aliases in the same way as MMS remote variables, but unlike these, the symbols of local variables are assigned to local application PL7-3 objects (bits, words, double words or tables of these elements).

• MMS local variables

MMS local variables correspond to three different types of elements in PL7-3. The

OFBs that MMS local variables are wired to, at present the MUSND OFB, comprising three possible input parameters for variable identification and one parameter per type of element (bit, word, double word) that can correspond to the type of MMS variable.

Naturally it is only possible to wire one of the three inputs to designate a variable.

In addition, to define a table type, another input is dedicated to the number of elements in the variable.

In the PL7-3/OFB interface, an MMS local variable is designated as shown below:

MUSND

VARi_B ptr_bit

SIZEi_W ptr_word

VARi_DW

SIZEi ptr_dword word

Where i

VARi_B is wired with the XTEL-SDBASE Alias corresponding to the variable when it corresponds to a bit type element.

VARi_W is wired with the XTEL-SDBASE Alias corresponding to the variable when it corresponds to a word type element.

VARi_DW is wired with the XTEL-SDBASE Alias corresponding to the variable when it corresponds to a double word type element.

SIZEi is the data size, expressed as a number of elements. It equals 1 by default.

a decimal integer from 1 to 3: the MUSND block can handle up to 4 variables at one time.

Important: Only one of the VARi inputs should be wired.

__________________________________________________________________________________________

3 / 9

__________________________________________________________________________________________

Correspondence between PL7-3 types and MMS local variables

PL7-3 Object Assigned MMS

Type

BitString1

Input Used

(VARi_x)

VARi_B System bits (SYn)

Internal bits (Bn)

String of N successive objects of the previous type

System Words (SWn)

Internal Words (Wn)

Constant Words (CWn)

String of N successive objects of the previous type

Internal Double Words (DWn)

Constant Double Words (CDWn)

String of N successive objects of the previous double word type

Array of

BitString1

BitString16

Array of

BitString16

BitString32

Array of

BitString32

VARi_B

VARi_W

VARi_DW

Size

(SIZEi)

1 or not wired

Exclusions: Types of PL7-3 objects that cannot be used as MMS variables:

• Discrete I/O bits (Ixy,n and Oxy,n)

• Bits assigned to Grafcet (Xi; XMj; Xj,1 and Xj,o)

• Module error bits (Ixy,S and Oxy,S)

• Indexed bits

• Register words (IWxy,1)

• Common words (COMi,j and COMxi,j with x = A, B, C or D)

• Words assigned to Grafcet (Xi,V; Xj,i,V; Xj,I,V and Xj,O,V)

• Indexed words

Important

It is not possible to wire a pointer type input to a bit (VARi_B) using a bit taken from a word.

__________________________________________________________________________________________

3 / 1 0

MMS Services OFBs 3

__________________________________________________________________________________________

3.3

MCNCT OFB: Association Management

3.3-1 Function

The MCNCT OFB manages the association between the PL7-3 application and a remote application. It lets the user open connection (MMS Initiate service), identify an association opened by a remote application (Accept command) and close it normally

(Conclude service) or close it urgently (Abort service). Finally it informs the PL7-3 program on the status of the connection: open, closed by the local or remote station.

The ACCEPT command is required to identify an association opened by a remote device when execution of an OFB is required on this association. If the PLC is only a server for the association, this command need not be used.

3.3-2 PL7-3 Interface

RESET bit

COMMAND word

APPLI

MODULE

TIMEOUT ptr_dword word word

MCNCT bit

INHIB STATE bit word

READY CHANNEL bit word

STATUS IND word word

ERROR

__________________________________________________________________________________________

3 / 1 1

__________________________________________________________________________________________

Input Parameters

RESET

COMMAND

APPLI

Type

Bit

Word

Ptr_Word

Access

R/RW

R/R

Description

Interrupt OFB execution (READY at 0). Connection remains in critical state (STATE at -1).

Warning: A RESET on an idle OFB (READY at 1) that also indicates an open association (STATE at 0) will place the association in a critical state.

It is recommended that RESET NOT BE USED

WHEN READY=1 AND STATE=0, even to reset the

Type of service to execute, depending on value:

0: Open association (Initiate Service)

1: Identify association (Accept Service)

2: Close association (Conclude Service)

Name of the remote application to reach.

Pointer on a field where the first word contains the size (in bytes) of the field, the next words the characters for the remote association name.

MODULE

TIMEOUT

Word

R/R

Module position in the main PLC rack (slots 0 to 7).

Timeout for a response from a remote device. Expressed in tenths of a millisecond. This time is used by all confirmed services exchanged.

Allowed values: 0 to 32767,

Default value: 100,

Value 0: Infinate wait state,

Special case of restarts after TimeOut, refer to code ind. =/1002, in the Appendix, Divider F,

Sub-section 5.2.

Output Parameters

ERROR

Type

Bit

Access

R/R

Description

Execution error detected by the OFB.

__________________________________________________________________________________________

3 / 1 2

MMS Services OFBs 3

__________________________________________________________________________________________

Public Internal Data

STATUS

READY

INHIB

Type

Word

Bit

Access

R/R

Description

IF ERROR is at 1. Identifies execution errors. Each

R/R

RW/RW

OFB status:

READY = 1: OFB ready for execution,

Inhibits error indication:

ERROR and STATUS remain at 0, OFB execution is

CHANNEL Word R/R Logical identifier assigned to the connection by the

OFB after opening.

The identifier is the instance number of the MCNCT

OFB that controls the connection. This reference identifies the association in the exchanges on this channel. It must be provided as an input to other

STATE Word R/R Connection state:

0: Association open

1: Association closed by a local Conclude

2: Association closed by a remote Conclude

3: Association closed by a local Abort

-1: Association does not exist

__________________________________________________________________________________________

IND Word R/R MMS Service execution error indicator (indicated by

STATUS bits 8 to 11). Refer to Appendix, Div. F/5.

APPLIDIAG Interface: STATUS bit information

Bit Description Corrective action

Bit 0 Unknown command

The COMMAND code is not 0,1,2 or 3

Bit 1 Error reading application name.

An error occurred when reading the application name (size exceeds 32 characters, access error or parameter setting error).

Check the APPLI parameter

Bit 2 Association already open.

An association with an application with the same name as the one set in

APPLI is already open using the same channel number

(OFB instance number).

No corrective action is required (DO

NOT RESET the OFB). Exchanges can continue

__________________________________________________________________________________________

3 / 1 3

__________________________________________________________________________________________

APPLIDIAG Interface: STATUS bit information (cont'd)

Corrective Action Bit Description

Bit 3 Association number already used.

The channel number (OFB instance number) already identifies an association between the PLC and a remote application with a different name than the one declared in APPLI.

Bit 4

Bit 5

Association already closed. An attempt to close (using Conclude or Abort services) was made with an instance number (channel number) that is no longer assigned.

Association to identify does not exist.

An identification (Accept service) request was attempted on a connection that was not opened by a remote application.

Bit 7

Bit 8

Bit 9

Association monitoring interrupted by a RESET.

MMS error detected by the local module (Bit 8).

MMS error detected by the remote module (Bit 9).

Bit 10 Error during MMS service execution

(Bit 10).

Bit 11 MMS Service rejected (Bit 11).

Bit 12 Error accessing the module.

The module is missing, unplugged, in error or is not the right type

(TSX ETH 200).

Bit 13 Communication error.

The exchange failed for one of the reasons listed below:

1. No response to the request before timeout. The PLC master task is overloaded.

2. The module rejected the request because it was being configured or does not have a loaded MMS Client configuration.

Close the previous association using a

Conclude or Abort service.

Reset OFB outputs (RESET).

Check the application name provided

(APPLI parameter).

Check the next two bits to identify the type of error.

Analyze the IND parameter to determine the cause of the error.

Check the module and/or the slot number in the rack sent to the OFB

(MODULE input parameter).

Increase the master task cycle time or reduce the PLC load (in case 1).

Check the module configuration (in case 2).

Bit 14 Processing interrupted.

OFB execution was interrupted by setting its RESET input to 1 by SY0, a software error or a power break.

Bit 15 System error.

The OFB does not have the system resources required for execution.

Reduce the number of OFBs configured (of all types).

__________________________________________________________________________________________

3 / 1 4

MMS Services OFBs 3

__________________________________________________________________________________________

3.3-3 Using the MCNCT OFB

To implement the MCNCT OFB, follow the steps described below:

1. Configure the module using PL7-OSI,

2. Define the local application XTEL-SDBASE symbols ready for symbolic assignment of OFB inputs.

Using symbolic programming makes for clearer and easily portable applications.

3. Configure and program the OFB using PL7-3.

Allow for the number of instances, taking into account that an MCNCT instance only manages one association at a time and that the instance number is used as the logical identifier (Channel Number) for the association (communication channel used between the local application and the remote application). All Client and Server OFBs that exchange data on this channel use the channel number as an input.

Initialize the constants assigned to the remote MMS identifiers by executing a PL7-3

READ command on the MMS.CST file.

Programming the MCNCT OFB is described in detail in the next Sub-section.

3.3-4 Programming the MCNCT OFB a. Opening an association

This function uses the MMS Initiate service.

Connection is opened by executing the MCNCT OFB with the COMMAND input set to 0.

The other inputs to set are:

APPLI (name of the application to open the association with),

MODULE (slot number of the communication module),

TIMEOUT

Execution results:

Association opened:

ERROR = 0

CHANNEL = Association Number (OFB instance number),

STATE = 0

Opening failed:

ERROR = 1

STATUS gives the reason for the failure

STATE gives the state of the connection

__________________________________________________________________________________________

3 / 1 5

__________________________________________________________________________________________

Note

Any attempt to open an association that is already open will fail (ERROR = 1) except if the value of APPLI is the same on the second attempt as the first. In this case, exchanges remain authorized on the channel. Otherwise the result is the same as failing to close the first connection: all exchanges are impossible. Before being able to reuse the channel, the association must be closed

(using Conclude or Abort services) and identification performed.

Programming example

The READY bit

! IF NOT B0.MCNCT0,READY

THEN EXEC MCNCT0(;Initiate;CplMap;ORDO_APP;200=> ...);

SET B0

! <WAIT>

! IF NOT MCNCT0, READY THEN JUMP L500

! IF MCNCT0, ERROR THEN JUMP L999

! <The association is open. It will be identified until closed>

! <by ORDO.>

! IF [MCNCT0, STATE=0] THEN MCNCT0,CHANNEL->ORDO

! <Program continues...>

Data used

Symbol

Initiate

Conclude

Abort

CplMap

Ordo

Ordo_app

Variable

CW0

CW1

CW2

CW3

CW10

W10

CW11

CW12

Value

M'ORDO'

__________________________________________________________________________________________

3 / 1 6

MMS Services OFBs 3

__________________________________________________________________________________________ b. Identifying an association opened by a remote application

The Accept command (non MMS) is used by the local application to identify an association opened by a remote application. Connection is opened by executing the

MCNCT OFB with the COMMAND input set to 1.

The other input to set are:

APPLI (name of the application to open the association with),

MODULE (slot number of the communication module),

TIMEOUT

Execution results:

Association identified:

ERROR = 0

CHANNEL = Association Number (OFB instance number),

STATE = 0

Identification failed:

ERROR = 0

STATUS gives the reason for the failure

STATE gives the state of the connection

Note

Any attempt to identify a previously identified association will always fail (ERROR = 1) except if the value of APPLI is the same on the second attempt as the first. In this case, exchanges remain authorized on the channel. Otherwise the result is the same as failing to close the first connection: all exchanges are impossible. Before being able to reuse the channel, the association must be closed (using Conclude or Abort services) and identification performed.

Programming example

Using number 2 to identify a connection opened by a remote "Supervisor" device. The module used is located in slot 4 of the main PLC rack. The timeout is 2 seconds.

! IF NOT B0.MCNCT2,READY

THEN EXEC MCNCT2(;Accept;CplMap;SUPER_APP;200=> ...);

SET B0

! <WAIT>

! IF NOT MCNCT2, READY THEN JUMP L500

! IF MCNCT2, ERROR THEN JUMP L999

! <The association is identified. It will be identified until>

! <closed by SUPERVI.>

! IF [MCNCT2, STATE=0] THEN MCNCT2,CHANNEL->SUPER

! <Program continues...>

__________________________________________________________________________________________

3 / 1 7

__________________________________________________________________________________________

Data used

Symbol

Initiate

Conclude

CplMap

Super

Super_ap

Variable

CW0

CW1

CW2

CW10

W20

CW20

CW21

Value

Channel Num. = 2

M'SUPERVISOR'

F c. Closing an association

This function uses the MMS Conclude service.

Connection is closed by executing the MCNCT OFB with the COMMAND input set to 2.

The other inputs are ignored.

Execution results:

Association closed:

ERROR = 0

STATE = 1

Closure failed:

ERROR = 0

STATUS gives the reason for the failure

STATE gives the state of the connection

Generally a failure is caused by:

• Services still being processed on the association,

• Association already closed.

Note

If an open association fails to close, exchanges remain authorized although ERROR and STATUS will indicate an error.

An association closure is not executed immediately. The Conclude service is executed over a number of cycles. During the time between requesting closure and its becoming effective, reception of data (solicited or not) is allowed to complete requests in progress. All new service requests (read or write) are refused. If a write request is in progress when the Conclude request is made, the

Conclude request will be rejected. STATE changes state once execution of the Conclude request is confirmed.

__________________________________________________________________________________________

3 / 1 8

MMS Services OFBs 3

__________________________________________________________________________________________

Programming example

Concluding connection 0.

! IF NOT B1.MCNCT0,READY

THEN EXEC MCNCT0(;Conclude;;;=> );SET B1

! <WAIT>

! IF NOT MCNCT0, READY THEN JUMP L500

! IF MCNCT0, ERROR THEN JUMP L999

! <The association is closed.>

! IF [MCNCT2, STATE=0] THEN MCNCT2,CHANNEL->SUPER

! <Program continues...>

For data used, refer to page 3/16.

d. Emergency shutdown of an association

This function uses the MMS Abort service.

Connection is closed by executing the MCNCT OFB with the COMMAND input set to 3.

The other inputs are ignored.

Execution results:

Association closed:

ERROR = 0

STATE = 2

Closure failed:

ERROR = 1

STATUS gives the reason for the failure

STATE gives the state of the connection

An Abort service is only refused if the association is already closed.

Note

Although the Abort service is executed over a number of cycles, closure is performed urgently. As soon as this request is received, all exchanges (read or write) in progress are cancelled. Any new requests received will be rejected.

__________________________________________________________________________________________

3 / 1 9

__________________________________________________________________________________________

Programming example

Aborting connection 0.

! IF NOT B2.MCNCT0,READY

THEN EXEC MCNCT0(;Abort;;;=> ); SET B2

! <WAIT>

! IF NOT MCNCT0, READY THEN JUMP L500

! IF MCNCT0, ERROR THEN JUMP L999

! <The association is closed.>

For data used, refer to page 3/16.

F e. Monitoring function

This function cannot be programmed. It is implicit when the OFB is executed to open or identify an association and as long as the association remains open.

The OFB monitors the status of the module and the association.

Events detected are:

Module disconnected or failure

Association closed by the remote device

When one of these events occurs, ERROR is set to 1. STATUS will give the cause and

STATE will give the state of the association.

Note

During monitoring, the MCNCTi,READY bit is at 1. This means that the OFB remains accessible to execute Conclude or Abort services.

Remark

When a Reset is performed on an MCNCT block while an association is being monitored, the association will enter a critical state (STATE = -1) and all current transactions on the association will be lost.

__________________________________________________________________________________________

3 / 2 0

MMS Services OFBs 3

__________________________________________________________________________________________

3.4

MREAD OFB: Read MMS Client Variables

3.4-1 Function

The MREAD OFB supports the MMS_READ service. It will read 1 to 4 variables from a remote application.

The variables are MMS Client variables defined with PL7-MMS. At OFB level, the variables are identified by their XTEL-SDBASE symbols (Aliases).

3.4-2 PL7-3 Interface

RESET

CHANNEL bit word

VAR0...3

SIZE0...3

DATA0...3

DATA3 word word ptr_word word word ptr_word

MREAD bit

INHIB RC0...3

bit word

READY RC0...3

bit word

STATUS IND word word

ERROR

__________________________________________________________________________________________

3 / 2 1

__________________________________________________________________________________________

Input Parameters

COMMAND

Type

Bit

Word

DATA0..DATA3 Ptr_Word

Access

R/RW

R/R

Description

Interrupts OFB execution or resets STATUS.

Association number (communication channel

XTEL-SDBASE Alias of variables to read.

Size in bytes of the reception buffers.

Pointer to reception buffers.

Output Parameters

ERROR

Type

Bit

Access

R/R

Description

Execution error detected by the OFB.

Public Internal Data

STATUS

Type

Word

READY Bit

INHIB

RC0...RC3

IND

Bit

Word

Access

R/R

Description

IF ERROR is at 1. Identifies execution errors.

Each bit indicates an error.

R/R

RW/RW

OFB status:

READY = 1: OFB ready for execution,

Inhibits error indication:

ERROR and STATUS remain at 0, OFB execution is

R/R

Length of data if read action was correct. Else, cause

MMS Service execution error indicator (indicated by

STATUS bits 8 to 11). Refer to Appendix, Div. F,

Sub-section 5.2.

__________________________________________________________________________________________

3 / 2 2

MMS Services OFBs 3

__________________________________________________________________________________________

Meaning of RCi data on error

-100

-101

-102

-103

-104

-105

-106

-107

-108

-109

-110

-4

-5

-6

-7

-8

>= 0

-1

-2

-3

No errors.

VARi input not set.

VARi is set but a corresponding SIZEi or DATAi input is not set.

Access to a non configured field.

Access to a write protected segment (CW, SW, etc.).

Reception buffer assigned to VARi causes overlap.

Reception buffer assigned to VARi is too small.

VARi input not defined.

VARi type incompatible with its definition in the function field

Object invalidated

Hardware-fault

Temporarily-unavailable

Object-access-denied

Object-undefined

Invalid-address

Type-unsupported

Type-inconsistent

Object-Attribute-inconsistent

Object-access-unsupported

Object-non-existent

__________________________________________________________________________________________

3 / 2 3

__________________________________________________________________________________________

APPLIDIAG Interface: STATUS Details

Bit Description Corrective Action

Bit 0

Bit 1

Bit 2

Bit 3

Bit 4

Bit 5

Association not open or being closed.

Association not available for exchanges.

Error accessing the MMS function field.The PL7-MMS function field is not configured or loaded.

Check the CHANNEL parameter or the status of the association

(MCNCTi,STATE and MCNCTi,STATUS variables, i = Association Number).

Configure and/or load an MMS field.

Error accessing the variable description. Error reading the description of variables (invalid descriptor, variable not defined, etc.).

The RCi data indicates the affected input parameter.

Error accessing data. Access protected or illegal, settings, capacity overflow, etc. The RCi data indicate the parameter that caused the error.

Access refused by the server. Error accessing MMS variables (variable not defined, access protected, etc...) The

RCi data indicate the parameter that caused the error.

Allocation error. There is not enough space in the PL7-MMS field to perform memory allocation.

Check the VARi input parameters and/ or the definition of variables using

PL7-MMS. Ensure that the constants file MMS.CST is loaded.)

Check the DATAi parameters.

Check the VARi and DATAi parameters. Check the definition of variables with PL7-MMS (coherence with their definition in the remote station).

Reduce the size of variables to read or reduce the number of OFBs in the application that can perform dynamic memory allocations in the PL7-MMS field.

Bit 6 Request too large.

The variables requested in read cause the request to exceed 4096 bytes.

Reduce the number of variables to read in the request or reduce the size of the data to read.

Bit 8

Bit 9

MMS error detected by the module

(Bit 8).

MMS error detected by the remote module (Bit 9).

Check the next two bits to identify the type of error.

Bit 10 Error during MMS service execution

(Bit 10).

Bit 11 MMS Service rejected (Bit 11).

Analyze the IND parameter to determine the cause of the error.

Bit 12 Error accessing the module.

The module is missing, unplugged, in error or is not the right type

(TSX ETH 200).

Check the module and/or the slot number in the rack sent to the OFB (MOD-

ULE input parameter).

__________________________________________________________________________________________

3 / 2 4

MMS Services OFBs 3

__________________________________________________________________________________________

APPLIDIAG Interface: STATUS Details

Bit Description Corrective Action

Bit 13 Communication error. The exchange failed for one of the reasons listed below:

1. No response to the request before timeout. The PLC master task is overloaded.

2. The module rejected the request because it was being configured or does not have a loaded MMS Client configuration.

Increase the master task cycle time or reduce the PLC load (in case 1).

Check the module configuration (in case

2).

Bit 14 Processing interrupted. OFB execution was interrupted by setting its RE-

SET input to 1 by SY0, a software error or a power break.

Reduce the number of OFBs configured

(of all types).

Bit 15 System error.The OFB does not have the system resources required for execution.

__________________________________________________________________________________________

3 / 2 5

__________________________________________________________________________________________

3.4-3 Using the MREAD OFB

To implement the MREAD OFB, first open (or identify) an association with the remote application by executing an instance of the MCNCT OFB.

3.4-4 Programming the MREAD OFB

The MREAD OFB reads 1 to 4 MMS Client variables from a remote application. This implies that:

• The local application is aware of these variables, i.e. that they have been defined for the station using PL7-MMS,

• A communication channel is open with the remote application, i.e. that an MCNCT

OFB has already opened an association (Initiate service) or identified an association opened by the remote application (Accept service).

The identification of each MMS variable is passed to the MREAD OFB via an

XTEL-SDBASE symbol (Alias) that links it to the MMS symbol (refer to Sub-section 3.4).

The Alias is taken to the VARi parameter.

Each of the values from the variables to read are stored in a reception buffer that is defined for the OFB by the input parameters:

• DATAi: Address of the first reception buffer word,

• SIZEi: Size, in bytes, of the reception buffer.

(The DATAi and SIZEi parameters correspond to the VARi parameter, where i is between 0 and 3).

The number of the association used by the request is taken to the CHANNEL parameter.

Execution results:

Read performed correctly:

ERROR = 0

RC0..RC3 specify by their values, the size in bytes of the data received

Read failed:

ERROR = 1

RC0..RC3 specify the reason for the failure

__________________________________________________________________________________________

3 / 2 6

MMS Services OFBs 3

__________________________________________________________________________________________

Programming example

Reading two variables "NB-STATION" an integer and "LIST-STATIONS" a table of three bytes. These variables are identified by the symbols STATION and STATIONS. The first variable is stored after W0 (2 byte field). The second after W1 (4 byte field). The exchange used the association designated 1.

! IF NOT B1.MREAD0,READY.[MCNCT1,STATE=0]

THEN EXEC MREAD0(;1;STATION;2;NB_ST;STATIONS;

4;;LST_ST;;;;;;=>); SET B1

! <WAIT>

! IF NOT MCNCT0, READY THEN JUMP L500

! IF MCNCT0, ERROR THEN JUMP L999

! <The two variables are read.>

! <W0 contains the value of "NB-STATIONS";

! <W1 contains the first two bytes of "LIST_STATIONS";

! <The LSB of W2 contains the third byte.

! <Program continues...>

Data used

Symbol

Nb_st

Lst_st

Remote

Station

Stations

Variable

W10

CW100

CW101

Value

1 (Channel Num. = 1)

From PL7-MMS

__________________________________________________________________________________________

3 / 2 7

__________________________________________________________________________________________

3.5

MWRIT OFB: Write MMS Client Variables

3.5-1 Function

The MWRIT OFB supports the MMS_WRITE service. It will write 1 to 4 variables to a remote application.

The variables are MMS Client variables defined with PL7-MMS. At OFB level, the variables are identified by their XTEL-SDBASE symbols (Aliases).

3.5-2 PL7-3 Interface

RESET

CHANNEL bit word

VAR0...3

SIZE0...3

DATA0...3

word word ptr_word word word ptr_word

MWRIT bit

INHIB RC0 bit word

READY RC3 bit word

STATUS IND word word

ERROR

__________________________________________________________________________________________

3 / 2 8

MMS Services OFBs 3

__________________________________________________________________________________________

Input Parameters

CHANNEL

SIZE0...SIZE3

Type

Bit

Word

DATA0..DATA3 Ptr_Word

Access

R/RW

R/R

Description

Interrupts OFB execution or resets STATUS.

Association number (communication channel

XTEL-SDBASE Alias of variables to read.

Size in bytes of the data to send. (Optional: If the parameter is not set, the exact size of the variable is used. When this input is used, additional control is

Pointer to transmission buffers.

Output Parameters

ERROR

Type

Bit

Access

R/R

Description

Execution error detected by the OFB.

Public Internal Data

STATUS

Type

Word

READY

INHIB

RC0...RC3

IND

Bit

Word

Access

R/R

Description

IF ERROR is at 1. Identifies execution errors.

Each bit indicates an error.

R/R

RW/RW

OFB status:

READY = 1: OFB ready for execution,

Inhibits error indication:

ERROR and STATUS remain at 0, OFB execution is

R/R

Cause of the Write error.

MMS Service execution error indicator (indicated by

STATUS bits 8 to 11). Refer to Appendix, Div. F,

Sub-section 5.2.

__________________________________________________________________________________________

3 / 2 9

__________________________________________________________________________________________

Meaning of RCi data on error

-100

-101

-102

-103

-104

-105

-106

-107

-108

-109

-110

-4

-5

-6

-7

-8

>= 0

-1

-2

-3

No errors.

VARi input not set.

VARi is set but a corresponding SIZEi or DATAi input is not set.

Access to a non configured field.

Access to a write protected segment (CW, SW, etc.).

Reception buffer assigned to VARi causes overlap.

Reception buffer assigned to VARi is too small.

VARi input not defined.

VARi type incompatible with its definition in the function field

Object invalidated

Hardware-fault

Temporarily-unavailable

Object-access-denied

Object-undefined

Invalid-address

Type-unsupported

Type-inconsistent

Object-Attribute-inconsistent

Object-access-unsupported

Object-non-existent

__________________________________________________________________________________________

3 / 3 0

MMS Services OFBs 3

__________________________________________________________________________________________

APPLIDIAG Interface: STATUS Details

Bit Description Corrective Action

Bit 0

Bit 1

Bit 2

Bit 3

Bit 4

Bit 5

Association not open or being closed.

Association not available for exchanges.

Error accessing the MMS function field.The PL7-MMS function field is not configured or loaded.

Check the CHANNEL parameter or the status of the association

(MCNCTi,STATE and MCNCTi,STATUS variables, i = Association Number).

Configure and/or load an MMS field.

Error accessing the variable description. Error reading the description of variables (invalid descriptor, variable not defined, etc.).

The RCi data indicates the affected input parameter.

Check the VARi input parameters and/ or the definition of variables using

PL7-MMS. Ensure that the constants file MMS.CST is loaded.)

Error accessing data. Access protected or illegal, settings, capacity overflow, etc. The RCi data indicate the parameter that caused the error.

Access refused by the server. Error accessing MMS variables (variable not defined, access protected, etc...) The

RCi data indicate the parameter that caused the error.

Allocation error. There is not enough space in the PL7-MMS field to perform memory allocation.

Check the DATAi parameters.

Check the VARi and DATAi parameters. Check the definition of variables with PL7-MMS (coherence with their definition in the remote station).

Reduce the size of variables to read or reduce the number of OFBs in the application that can perform dynamic memory allocations in the PL7-MMS field.

Bit 8

Bit 9

MMS error detected by the module

(Bit 8).

MMS error detected by the remote module (Bit 9).

Check the next two bits to identify the type of error.

Analyze the IND parameter to determine the cause of the error.

Bit 10 Error during MMS service execution

(Bit 10).

Bit 11 MMS service rejected (Bit 11)

Bit 13 Communication error. The exchange failed for one of the reasons listed below:

1. No response to the request before timeout. The PLC master task is overloaded.

2. The module rejected the request because it was being configured or does not have a loaded MMS Client configuration.

Increase the master task cycle time or reduce the PLC load (in case 1).

Check the module configuration (in case

2).

__________________________________________________________________________________________

3 / 3 1

__________________________________________________________________________________________

APPLIDIAG Interface: STATUS Details

Bit Description Corrective Action

Bit 14 Processing interrupted. OFB execution was interrupted by setting its RE-

SET input to 1 by SY0, a software error or a power break.

Bit 15 System error.The OFB does not have the system resources required for execution.

Reduce the number of OFBs configured

(of all types).

3.5-3 Using the MWRIT OFB

To implement the MWRIT OFB, first open (or identify) an association with the remote application by executing an instance of the MCNCT OFB.

3.5-4 Programming the MWRIT OFB

The MWRIT OFB reads 1 to 4 MMS Client variables from a remote application. This implies that:

• The local application is aware of these variables, i.e. that they have been defined for the station using PL7-MMS,

• A communication channel is open with the remote application, i.e. that an MCNCT

OFB has already opened an association (Initiate service) or identified an association opened by the remote application (Accept service).

The identification of each MMS variable is passed to the MWRIT OFB via an

XTEL-SDBASE symbol (Alias) that links it to the MMS symbol (refer to Sub-section 3.4).

The Alias is taken to the VARi parameter.

__________________________________________________________________________________________

3 / 3 2

MMS Services OFBs 3

__________________________________________________________________________________________

Each of the values from the variables to read are stored in a reception buffer that is defined for the OFB by the input parameters:

• DATAi: Address of the first transmission buffer word,

• SIZEi: Size, in bytes, of the transmission buffer. This input may not be used. If it is, the

OFB will perform a coherence check on the size of the type of MMS variable defined with PL7-MMS.

(The DATAi and SIZEi parameters correspond to the VARi parameter, where i is between 0 and 3).

The number of the association used by the request is taken to the CHANNEL parameter.

Execution results:

Write performed correctly:

ERROR = 0

RC0..RC3 are at 0

Write failed:

ERROR = 1

RC0..RC3 specify the reason for the failure

Programming example

Writing the variable "ASM-FINI" to 1. A Boolean type, this variable is identified by the symbol ASM_FIN. The transmission buffer (the exchange fields are always word types) is W100 (Aux). The exchange is performed on association 0.

! IF NOT B1.MWRIT0,READY.[MCNCTO,STATE=0] THEN SET AUX,0;

THEN EXEC MWRIT0(;0;ASM_FIN;1; AUX;;;;;;;;;=>); SET B1

! <WAIT>

! IF NOT MWRIT0, READY THEN JUMP L500

! IF MWRIT0, ERROR THEN JUMP L999

! <The variable "ASM_FIN" is set to 1.

! <Program continues...>

Data used

Symbol Variable Value

Aux

Asm_fini

W100

CW102

1 (after SET AUX, 0_

Assigned by PL7-MMS

__________________________________________________________________________________________

3 / 3 3

__________________________________________________________________________________________

3.6

MURCV OFB: Unsolicited Data (Client Mode)

3.6-1 Function

The MURCV OFB supports the MMS INFORMATION REPORT service. This lets a

Client application receive unsolicited data sent by a remote Server application. The application is in stand-by with the MURCV OFB.

The variables are MMS Client variables defined with PL7-MMS. At OFB level, the variables are identified by their XTEL-SDBASE symbols (Aliases).

3.6-2 PL7-3 Interface

RESET

CHANNEL

VAR

SIZE

BUFFER bit word word word ptr_word

MURCV bit

INHIB RC bit word

READY bit

STATUS IND word word

__________________________________________________________________________________________

3 / 3 4

MMS Services OFBs 3

__________________________________________________________________________________________

Input Parameters

CHANNEL

BUFFER

Type

Bit

Word

Ptr_Word

Access

R/RW

R/R

Description

Interrupts OFB execution or resets STATUS.

Association number (communication channel

R/R

XTEL-SDBASE Alias of variables to read.

Size in bytes of the reception field.

Pointer to reception field.

Output Parameters

ERROR

Type

Bit

Access

R/R

Description

Execution error detected by the OFB.

Public Internal Data

STATUS

Type

Word

READY

INHIB

IND

Bit

Word

Access

R/R

Description

IF ERROR is at 1. Identifies execution errors.

Each bit indicates an error.

R/R

RW/RW

OFB status:

READY = 1: OFB ready for execution,

Inhibits error indication:

ERROR and STATUS remain at 0, OFB execution is

R/R

Length of data if read action was correct. Else, cause

MMS Service execution error indicator (indicated by

STATUS bits 8 to 11).

Refer to the Appendix, Divider F, Sub-section 5.2.

__________________________________________________________________________________________

3 / 3 5

__________________________________________________________________________________________

Meaning of RC data on error

-100

-101

-102

-103

-104

-105

-106

-107

-108

-109

-110

When an error occurs that is linked to the description of MMS variables, data access or refusal by the server to allow access, as shown by bits 2, 3 and 4, the RC data specifies the cause of the error.

-4

-5

-6

-7

-8

>= 0

-1

-2

-3

No errors.

VARi input not set.

VARi is set but a corresponding SIZEi or DATAi input is not set.

Access to a non configured field.

Access to a write protected segment (CW, SW, etc.).

Reception buffer assigned to VARi causes overlap.

Reception buffer assigned to VARi is too small.

VARi input not defined.

VARi type incompatible with its definition in the function field

Object invalidated

Hardware-fault

Temporarily-unavailable

Object-access-denied

Object-undefined

Invalid-address

Type-unsupported

Type-inconsistent

Object-Attribute-inconsistent

Object-access-unsupported

Object-non-existent

__________________________________________________________________________________________

3 / 3 6

MMS Services OFBs 3

__________________________________________________________________________________________

APPLIDIAG Interface: STATUS Details

Bit Description Corrective Action

Bit 0

Bit 1

Association not open or being closed.

Association not available for exchanges.

Error accessing the MMS function field.The PL7-MMS function field is not configured or loaded.

Check the CHANNEL parameter or the status of the association

(MCNCTi,STATE and MCNCTi,STATUS variables, i = Association Number).

Configure and/or load an MMS field.

Bit 2

Bit 3

Bit 4

Bit 5

Bit 8

Bit 9

Error accessing the variable description. Error reading the description of variables (invalid descriptor, variable not defined, etc.).

Check the VAR input parameters and/ or the definition of variables using

PL7-MMS. Ensure that the constants file MMS.CST is loaded.)

Error accessing data. Access protected or illegal, settings, capacity overflow, etc.

Check the BUFFER parameter.

Access refused by the server. Error accessing MMS variables (variable not defined, access protected, etc...).

Check the VAR and BUFFER parameters. Check the definition of variables with PL7-MMS (coherence with their definition in the remote station).

Allocation error. There is not enough space in the PL7-MMS field to perform memory allocation.

Reduce the size of variables to read or reduce the number of OFBs in the application that can perform dynamic memory allocations in the PL7-MMS field.

MMS error detected by the module

(Bit 8).

MMS error detected by the remote module (Bit 9).

Check the next two bits to identify the type of error.

Bit 10 Error during MMS service execution

(Bit 10).

Bit 11 MMS Service rejected (Bit 11).

Analyze the IND parameter to determine the cause of the error.

Check the configuration and/or the status of the module.

Bit 13 Communication error. The module rejected the request because it was being configured or has failed.

Bit 14 Processing interrupted. OFB execution was interrupted by setting its RESET input to 1 by SY0, a software error or a power break.

Bit 15 System error.The OFB does not have the system resources required for execution.

Reduce the number of OFBs configured (of all types).

__________________________________________________________________________________________

3 / 3 7

__________________________________________________________________________________________

3.6-3 Using the MURCV OFB

To implement the MURCV OFB, first open (or identify) an association with the remote application by executing an instance of the MCNCT OFB.

3.6-4 Programming the MURCV OFB

The MURCV OFB lets a Client PL7-3 application stand-by to receive the value of an

M MS v ar ia bl e sen t b y a re mo te Se rv er a ppl i ca tion (MMS Service:

INFORMATION_REPORT). The MMS variable was defined with PL7-MMS as a Client variable.

This OFB operates in the same way as MREAD except that data can be received over a longer length of time. Only one variable can be received each time the OFB is executed.

The identification of each MMS variable is passed to the MURCV OFB via an

XTEL-SDBASE symbol (Alias) that links it to the MMS symbol (refer to Sub-section 3.4).

The Alias is taken to the VARi parameter.

Each of the values from the variables to read are stored in a reception buffer that is defined for the OFB by the input parameters:

• BUFFER: Address of the first reception buffer word,

• SIZE: Size, in bytes, of the reception buffer.

(The DATAi and SIZEi parameters correspond to the VARi parameter, where i is between 0 and 3).

The number of the association used by the request is taken to the CHANNEL parameter.

Execution results:

Read performed correctly:

ERROR = 0

RC specifies the size in bytes of the data received

Read failed:

ERROR = 1

RC specifies the reason for the failure

__________________________________________________________________________________________

3 / 3 8

MMS Services OFBs 3

__________________________________________________________________________________________

Programming example

Waiting to receive a synchronization variable sent by a sequencer. The "START-

PRODUCING" Boolean type variable is followed by the number of parts to produce,

"PARTS". The program sets to OFBs to receive these two variables.

! IF NOT B1.MURCV0,READY.MURCV1,READY.[MCNCT0,STATE=0]

THEN EXEC MURCV0(;ORDO;START;2;AUX0=>);

THEN EXEC MURCV1(;ORDO;START;2;AUX1=>);

SET B1

! <WAIT>

! IF NOT MURCV0, READY THEN JUMP L200

! IF MCNCT0, ERROR THEN JUMP L999

! <The "START_PRODUCING" was received.

! <If it is true, the program starts producing parts.

! <Else, it will stop waiting for "PARTS".

! IF AUX0,F

THEN JMP L10

THEN EXEC MURCV1(1=>); JUMP L200

! L10:

! <Start-Producing>

! <Non blocking wait for the "PARTS" variable.

! IF NOT MURCV1, READY THEN JUMP L200

! IF MURCV1, ERROR THEN JUMP L999

! <etc.

! <L200:

! <Program continues...>

Data used

Symbol

Aux0

Aux1

Ordo

Start

Parts

Variable

W10

CW103

CW104

Value

0 (Channel Num. = 0)

From PL7-MMS

Remark

When a Reset action on an MURCV OFB is performed while waiting to receive data, the OFB attempts to warn the module that it is no longer waiting, by sending a message without confirm. The RESET action takes about 2 milliseconds to perform.

__________________________________________________________________________________________

3 / 3 9

__________________________________________________________________________________________

3.7

MRSTA OFB: Device Status (Client Mode)

3.7-1 Function

The MRSTA OFB supports the MMS_STATUS service or reception of

UNSOLICITED_STATUS. It lets a Client application read the status of a remote Server device. The Client can either send a request or wait for transmission from the Server.

3.7-2 PL7-3 Interface

RESET

CHANNEL

UNSOL bit word bit

MRSTA bit

ERROR

INHIB PHYSIC bit word

READY LOGIC bit word

STATUS LOCDET word bit

IND word

DETAIL

word [8]

Input Parameters

CHANNEL

UNSOL

Type

Bit

Word

Bit

Access

R/RW

R/R

Description

Interrupts OFB execution or resets STATUS.

Association number (communication channel

At 1, unsolicited read.

At 0, solicited read (default).

__________________________________________________________________________________________

3 / 4 0

MMS Services OFBs 3

__________________________________________________________________________________________

Output Parameters

ERROR

Type

Bit

Access

R/R

Description

Execution error detected by the OFB.

Public Internal Data

STATUS

READY

INHIB

PHYSIC

LOGIC

LOCDET

DETAIL

IND

Type

Word

Access

R/R

Description

IF ERROR is at 1. Identifies execution errors.

Each bit indicates an error.

Bit

Word

Bit

Table of

8 words

Word

R/R

RW/RW

OFB status:

READY = 1: OFB ready for execution,

Inhibits error indication:

ERROR and STATUS remain at 0, OFB execution is

R/R

Physical status of the remote device.

Logical status of the remote device.

R/R

Indicates that the optional status (local detail) is present (LOCDET at 1) or not.

This optional field receives the additional status information for PHYSIC and LOGIC. This field de-

MMS Service execution error indicator (indicated by

STATUS bits 8 to 11). Refer to Appendix F/5.

LOGIC and PHYSIC States

This data indicates the state of the device, as specified by the MMS standard.

__________________________________________________________________________________________

3 / 4 1

__________________________________________________________________________________________

APPLIDIAG Interface: STATUS Details

Bit

Bit 0

Description

Association not open or being closed.

Association used not available for exchanges.

Corrective Action

Check the CHANNEL parameter or the status of the association

(MCNCTi,STATE and MCNCTi,STATUS variables, i = Association Number).

Check the next two bits to identify the type of error.

Bit 8

Bit 9

MMS error detected by the module

(Bit 8)

MMS error detected by the remote module (Bit 9).

Bit 10 Error during MMS service execution

(Bit 10)

Bit 11 MMS Service rejected (Bit 11).

Bit 13 Communication error. The module rejected the request because it was being configured, unplugged or has failed.

Bit 14 Processing interrupted. OFB execution was interrupted by setting its RESET input to 1 by SY0, a software error or a power break.

Bit 15 System error. The OFB does not have the system resources required for execution.

Analyze the IND parameter to determine the cause of the error.

Check the module configuration and/ or status.

Reduce the number of OFBs configured

(of all types).

3.7-3 Using the MRSTA OFB

To implement the MRSTA OFB, first open (or identify) an association with the remote application by executing an instance of the MCNCT OFB.

3.7-4 Programming the MRSTA OFB

The MRSTA OFB lets a Client application read the status of a remote Server device, as defined in the MMS standard. The value of the UNSOL input determines the read mode.

At 0 (default mode), reading is explicitly requested (MMS Service: Status). At 1, unsolicited read is supported and the OFB will wait for the Unsolicited Status request.

__________________________________________________________________________________________

3 / 4 2

MMS Services OFBs 3

__________________________________________________________________________________________

The number of the association used by the request is taken to the CHANNEL parameter.

Execution results:

Data received correctly:

ERROR = 0

PHYSIC and LOGIC contain the physical and logical status of the remote device.

If LOCDET = 1, DETAIL contains additional information.

Read failed:

ERROR = 1

STATUS details the cause of failure

Programming example

The PL7-3 application and the MMS Client await remote device change of state from a robot. The event is indicated using the MMS Unsolicited Status service.

! IF NOT B1.MRSTA0,READY.[MCNCT,STATE=0]

THEN EXEC MRSTA0(;Robot;1=>); SET B1

! <WAIT>

! IF NOT MRSTA0, READY THEN JUMP L200

! IF MRSTA0, ERROR THEN JUMP L999

! <The status data was received.>

! <Analyze status. If incorrect restart the OFB.

! IF [MRSTA0,LOGIC=1]

THEN JUMP L200

! L200:

ELSE RESET B1; JUMP L500

! <Program continues...>

Data used

Symbol

Robot

Variable

W12

Value

Channel number = Inst. MCNCT2

Remark

When a Reset action on an MRSTA OFB is performed while waiting to receive data, the OFB attempts to warn the module that it is no longer waiting, by sending a message without confirm. The RESET action takes about 2 milliseconds to perform

__________________________________________________________________________________________

3 / 4 3

__________________________________________________________________________________________

3.8

MUSND OFB: Sending Unsolicited Data (Server Mode)

3.8-1 Function

The MUSND OFB supports the MMS INFORMATION REPORT service. This lets an

MMS Server application send unsolicited data to a Client application.

The variables are MMS Server variables defined with PL7-MMS. At OFB level, the variables are identified by their XTEL-SDBASE symbols (Aliases).

3.8-2 PL7-3 Interface

MUSND bit

RESET

CHANNEL word ptr_bit

VAR0_B

VAR0_W

VAR0_DW

NBELT0

VAR0…3_B

VAR0…3_W ptr_word ptr_dword word

VAR0…3_DW

NBELT3

RC0…3 bit

READY bit

STATUS word bit

RC0…3 word

IND word

ERROR

__________________________________________________________________________________________

3 / 4 4

MMS Services OFBs 3

__________________________________________________________________________________________

Input Parameters

Type

Bit

Word CHANNEL

VAR0_t to 3_t Ptr_Bit

NBELT 0...3

Word

Access

R/RW

R/R

Description

Interrupts OFB execution or resets STATUS.

Association number (communication channel

XTEL-SDBASE Alias of variables to send.

(Set by type)

Number of elements to send.

Output Parameters

ERROR

Type

Bit

Access

R/R

Description

Execution error detected by the OFB.

Public Internal Data

STATUS

Type

Word

READY

INHIB

RC0 to 3

IND

Bit

Word

Access

R/R

Description

IF ERROR is at 1. Identifies execution errors.

Each bit indicates an error.

OFB status:

READY = 1: OFB ready for execution,

RW/RW Inhibits error indication:

ERROR and STATUS remain at 0, OFB execution is

Length of data if read action was correct. Else, cause R/R

R/R MMS Service execution error indicator (indicated by

STATUS bits 8 to 11). Refer to Appendix, F/5.

__________________________________________________________________________________________

3 / 4 5

__________________________________________________________________________________________

Meaning of RC data on error

Value

>= 0

-1

-2

-3

-4

-5

-6

Description

No errors.

Not used (no VARi_t input used).

Only one VARi_t input should be used.

PL7-3 object not supported.

Access exceeds limits (overflows configured field).

Memory resource not available (copy bit type object).

Maximum size for table of set objects exceeded

The following limits apply:

• Bit : 1024

• Word : 1024

• DWord : 1024

__________________________________________________________________________________________

3 / 4 6

MMS Services OFBs 3

__________________________________________________________________________________________

APPLIDIAG Interface: STATUS Details

Bit

Bt 0

Description

Association not open or being closed.

Association not available for exchanges.

Corrective Action

Check the CHANNEL parameter or the status of the association

(MCNCTi,STATE & MCNCTi,STATUS variables, i = Association Number).

Check the variables.

Bit 1

Bit 2

Error accessing data. Access protected or illegal, settings, capacity overflow, etc.

The RCi data indicate the parameter that caused the error.

Access refused by the server.

Error accessing MMS variables

( variabl e not defined, access protected, etc...) The RCi data indicate the parameter that caused the error.

Allocation error. There is not enough space in the PL7-MMS field to perform memory allocation.

Check the VARi parameters. Check the definition of variables with PL7-

MMS (coherence with their definition in the module).

Bit 3

Bit 4

Bit 8

Bit 9

Request too large. The maximum request length is 4096 bytes, else the variables requested in read cause the request to exceed 4096 bytes.

MMS error detected by the module

(Bit 8).

MMS error detected by the remote module (Bit 9).

Bit 10 Error during MMS service execution

(Bit 10).

Bit 11 MMS Service rejected (Bit 11).

Bit 13 Communication error. The exchange failed for one of the reasons listed below:

1. No response to the request before timeout. The PLC master task is overloaded.

2. The module rejected the request because it was being configured or does not have a loaded MMS Client configuration.

Reduce the size of variables to read or reduce the number of OFBs in the application that can perform dynamic memory allocations in the PL7-MMS field.

Reduce the number of variables to read in the request or reduce the size of the data to read.

Check the next two bits to identify the type of error.

Analyze the IND parameter to determine the cause of the error.

Increase the master task cycle time or reduce the PLC load (in case 1). Check the module configuration (in case 2).

Bit 14 Processing interrupted. OFB execution was interrupted by setting its RESET input to 1 by SY0, a software error or a power break.

Bit 15 System error. The OFB does not have the system resources required for execution.

Reduce the number of OFBs configured

(of all types).

__________________________________________________________________________________________

3 / 4 7

__________________________________________________________________________________________

3.8-3 Using the MUSND OFB

To implement the MUSND OFB, first open (or identify) an association with the remote application by executing an instance of the MCNCT OFB.

3.8-4 Programming the MUSND OFB

The MUSND OFB lets a Server PL7-3 application send, at its own initiative, the values of 1 to 4 MMS Server variables to a remote Client application. MUSND corresponds to the MURCV OFB in a PL7-3 Client application.

MMS variables are defined with PL7-MMS in the same way as MMS server variables.

This OFB operates in the same way as MWRIT (in Client mode) except that the setting of Server variables (MUSND) is different from that of Client variables (MWRIT). (Refer to Sub-section 3.4).

The XTEL-SDBASE Alias for the MMS variables to send values for are set to the

VARi_B, VARi_W or VARi_DW inputs depending on the types of variables used (refer to Divider F, Sub-section 3.2). The size of data to send is set to the SIZEi inputs and expressed as a number of elements.

The number of the association used by the request is taken to the CHANNEL parameter.

__________________________________________________________________________________________

3 / 4 8

MMS Services OFBs 3

__________________________________________________________________________________________

Execution results:

Data sent correctly:

ERROR = 0

RCi = 0

Read failed:

ERROR = 1

RCi specifies the reason for the failure

Programming example

Send the "SUPERVISOR" application "FAILURE" variables (bit B100) and "CAUSE", the cause of the failure (word W100). "FAILURE" is a Boolean type with FAIL as its symbol. "CAUSE" is a "1 byte string" identified by CAUSE. Finally the association is identified by the variable SUPER (opened by MCNCT1).

! <If FAIL is at 1, a failure was found; CAUSE gives the cause.

! <The program warns the supervisor.

! IF FAIL.NOT B1.MUSNDV0,READY.[MCNCT0,STATE=0]

THEN EXEC MUSND0(;SUPER;FAIL;;;CAUSE=>);

SET B1

! <WAIT>

! IF NOT MUSND0, READY THEN JUMP L500

! IF MUSND0, ERROR THEN JUMP L999

! <Program continues...>

Data used

Symbol

SUPER

FAIL

CAUSE

Variable

W11

B100

W100

Value

1 to trigger send

__________________________________________________________________________________________

3 / 4 9

__________________________________________________________________________________________

3.9

MSSTA OFB: Sending Device Status (Server Mode)

3.9-1 Function

The MSSTA OFB supports the MMS UNSOLICITED_STATUS service. It lets an MMS

Server application send the status of its device to a Client. Transmission can be cyclic or triggered.

3.9-2 PL7-3 Interface

RESET

CHANNEL

TCYCLE bit word word

MSSTA bit

INHIB PHYSIC bit word

READY LOGIC bit word

STATUS IND word word

ERROR

__________________________________________________________________________________________

3 / 5 0

MMS Services OFBs 3

__________________________________________________________________________________________

Input Parameters

CHANNEL

TCYCLE

Type

Bit

Word

Access

R/RW

R/R

Description

Interrupts OFB execution or resets STATUS.

Association number (communication channel

Sample and change status time (in MAST cycles).

At 0, only one transmission will be made.

Output Parameters

ERROR

Type

Bit

Access

R/R

Description

Execution error detected by the OFB.

Public Internal Data

STATUS

Type

Word

READY

INHIB

PHYSIC

LOGIC

IND

Bit

Word

Access

R/R

Description

IF ERROR is at 1. Identifies execution errors.

Each bit indicates an error.

R/R

RW/RW

OFB status:

READY = 1: OFB ready for execution,

Inhibits error indication:

ERROR and STATUS remain at 0, OFB execution is

R/R

Physical status of the remote device.

Logical status of the remote device.

MMS Service execution error indicator (indicated by

STATUS bits 8 to 11). Refer to Appendix F/5.

LOGIC and PHYSIC States

This data indicates the state of the device, as specified by the MMS standard.

__________________________________________________________________________________________

3 / 5 1

__________________________________________________________________________________________

APPLIDIAG Interface: STATUS Details

Bit

Bit 0

Signification

Association not open or being closed.

Association not available for exchanges.

Corrective Action

Check the CHANNEL parameter or the status of the association

(MCNCTi,STATE & MCNCTi,STATUS variables, i = Association Number).

Check that the TCYCLE parameter does not exceed 32767.

Bit 1

Bit 8

Bit 9

TCYCLE parameter exceeds limits.

The value of TCYCLE exceeds 32767 cycles.

MMS error detected by the module

(Bit 8).

MMS error detected by the remote module (Bit 9).

Bit 10 Error during MMS service execution

(Bit 10).

Bit 11 MMS Service rejected (Bit 11).

Check the next two bits to identify the type of error.

Analyze the IND parameter to determine the cause of the error.

Bit 13 Communication error.The exchange failed for one of the reasons listed below:

1. No response to the request before timeout. The PLC master task is overloaded.

2. The module rejected the request because it was being configured or does not have a loaded MMS Server configuration.

Increase the master task cycle time or reduce the PLC load (in case 1).

Check the module configuration (in case 2).

Bit 14 Processing interrupted. OFB execution was interrupted by setting its RESET input to 1 by SY0, a software error or a power break.

Bit 15 System error.

The OFB does not have the system resources required for execution.

Reduce the number of OFBs configured

(of all types).

__________________________________________________________________________________________

3 / 5 2

MMS Services OFBs 3

__________________________________________________________________________________________

3.9-3 Using the MSSTA OFB

To implement the MRSTA OFB, first open (or identify) an association with the remote application by executing an instance of the MCNCT OFB.

3.9-4 Programming the MSSTA OFB

The MSSTA OFB lets a PL7-3 MMS Server application send its status to a Client application.

There are two ways to use the OFB:

• The status is sent on change of state. The status is polled per iodically (every TCYCLE cycles of the master task).

The OFB execution command is only sent once.

Periodic transmission of the status information can be stopped by executing the OFB with RESET set to 1.

• The Status is only sent when the OFB is executed. To do so, set TCYCLE to 0.

The number of the association used by the request is taken to the CHANNEL parameter.

Programming example

Sending the status to the SUPERVISOR application on change of state, polled every 50 master task cycles.

! IF NOT B1.MSSTA0,READY.[MCNCT1,STATE=0]

THEN EXEC MSSTA0(;SUPER;50=>); SET B1

! <WAIT>

! IF NOT B2 THEN EXEC MSSTA(1;;=>); SET B2

! IF MSSTA0, ERROR THEN JUMP L999

! <Program continues...>

Data used

Symbol

SUPER

Variable

W1!

Value

1 Channel number = Inst. MCNCT1

__________________________________________________________________________________________

3 / 5 3

__________________________________________________________________________________________

3 / 5 4

MSEMA OFB: Synchronizing Access to an MMS Server Variable 4

__________________________________________________________________________________________

4.1

Function

The MSEMA OFB is used to "synchronize" access to a Local (Server) PLC MMS

Variable, by a remote (Client) device and its usage in the local PL7-3 application.

The OFB manages a semaphore that indicates that a Local MMS variable, for which read/write access is expected, is available for use in the application.

The semaphore management is essentially used for writing variables with a size that exceeds 128 bytes: writing these variable by the remote device via the TSX ETH 200 interface requires a number of PLC cycles. The semaphore is therefore used to inhibit any access to the variable while it is being written.

The Local MMS variables that a semaphore must be assigned to are the ones configured in Programmed Mode using PL7-MMS V2.5 .

If, when access to a variable is requested by a remote device, the interface is found to not have an assigned semaphore, the MMS service requested for this variable

(Read/Write) will be put on hold until the MSEMA OFB is executed for this variable.

__________________________________________________________________________________________

4 / 1

__________________________________________________________________________________________

4.2

PL7-3 Interface

Inputs

RESET

MSEMA

: bit ERROR : bit

CHANNEL : word

VAR_B : ref_bit

VAR_W : ref_word

VAR_DW : ref_dword

Outputs

Internal

Public

Data

INHIB : bit

STATUS : word

READY : bit

STATUS : word

IND

: word

__________________________________________________________________________________________

4 / 2

MSEMA OFB: Synchronizing Access to an MMS Server Variable 4

__________________________________________________________________________________________

Input parameters

Parameters Type

RESET Bit

Access

R/RW (1)

Description

Setting RESET to 1 will interrupt OFB execution (READY bit at 0) or resetting STATUS to zero (READY bit at 1).

By default RESET =0

CHANNEL

VAR_t with t = B,

W or DW

Word ref_t

R (1)

R (2)

R (1)

R (2)

Number of the association open for MMS exchanges.

By default CHANNEL = -1.

MMS Server variable to assign to the semaphore.

By default, these inputs are considered as not being wired.

Output parameters

)

Parameters Type

ERROR Bit

R (2)

Internal public data

Parameters Type

INHIB Bit

Access

R (1)

Access

R/W (1)

R/W (2)

Description

Error detected by the OFB (if INHIB = 0).

STATUS

IND

READY

Word

Bit

R (1)

R (2)

R (1)

R (2)

R (1)

R (2)

R (1)

R (2)

Description

Inhibits error indication.

ERROR and STATUS always stay at zero.

By default INHIB = 0.

Identifies a detected error.

See list of indicated errors on page 4/5

Cause of a protection failure.

(see list of possible causes on page 4/4

Valid only if READY = 1.

Indicates an MMS service failure.

(indicated by STATUS bits 8 to 11).

When READY is at 0, the Server variable has not yet been written or read by the

Client device.

On a rising edge on READY, the variable is written r read and is available; READY stays at 1 until the OFB is next executed.

(1): access by program.

(2): access by request.

__________________________________________________________________________________________

4 / 3

__________________________________________________________________________________________

Meaning of RC data on error

Value

>=0

Description

No errors.

-1

-2

-3

-103

The VAR input is not used.

Only one VAR_x input should be used.

PL7-3 object not supported

Object-access-denied:

Access is not allowed to association scope variables.

-108

-110

Object-Attribute-inconsistent:

The variable is not programmed.

Object-non-existent

The variable is not present in the table of symbols.

__________________________________________________________________________________________

4 / 4

MSEMA OFB: Synchronizing Access to an MMS Server Variable 4

__________________________________________________________________________________________

APPLIDIAG Interface: STATUS Details

Bit Description

Bit 0=1 The association is not open or being closed.

The association used (CHANNEL parameter) is not available for exchanges.

Bit 1=1 Error accessing data.

The parameter given in the VAR_B,

VAR_W or VAR_DW input is incorrect.

Bit 2=1 Access to the variable refused by the interface.

The variable to associate to the semaphore (VAR_x input) does not exist or is not in program mode.

Corrective action

Check the CHANNEL parameter or the association status (MCNCTi, STATE and MCNCTi, STATUS variables, where i is the association number).

Analyze the value of the RC parameter to determine the cause of the error.

Bits 3 to 7

Non used.

Bit 8=1 MMS error detected by the interface.

Bit 9=1 Error detected by the remote station.

The interface or the remote station detected an error in MMS service processing.

Access the next two bits to determine the type of error.

Bit 10=1 Error during MMS service execution.

Bit 11=1

MMS service execution ended on an error condition.

Analyze the IND parameter to determine the cause of the error.

Bit 12 Not used.

Bit 13=1 Communication error.

Exchange with the interface failed.

Check the configuration and/or the interface status.

Bit 14=1 Processing interrupted.

OFB execution was interrupted during execution by a RESET action, an

SY0, SY1 request, a program error or a power failure.

Bit 15=1 System error.

The OFB lacks the system resources

Reduce the number of OFBs configured (all families combined).

required for execution.

__________________________________________________________________________________________

4 / 5

__________________________________________________________________________________________

4.3

Using the MSEMA OFB

To implement the MSEMA OFB, first open (or identify) an association with the remote application by executing an instance of the MCNCT OFB.

Also ensure that the local variable used as a parameter for MSEMA was declared with the "PROG" access mode in PL7-MMS.

4.4

Programming the MSEMA OFB

The MSEMA OFB ensures that the PL7-3 application is informed of a read or write request affecting one of its local variables, sent by a remote application.

An instance of the MSEMA OFB can control a single variable. The name of the local

MMS variable is set to one of the VAR_B, VAR_W, VAR_DW inputs depending on the type of the variable (refer to Divider F, Sub-section 3.2).

The number of the association used by the request is taken to the CHANNEL parameter.

Case 1

To guarantee a coherent value for a variable with a size between 120 bytes and 4Kbytes, as it is modified, for the same MMS service request, over a number of PLC cycles

(coherence management).

For each variable that is considered "sensitive", an instance of the MSEMA OFB must be programmed in the PL7-3 application and the value of the READY bit tested. Testing the READY bit will indicate whether access is completed:

• The value has been completely updated by the interface (MMS Write Service), the

PL7-3 program can read and process it,

• The value has been completely returned to the remote station (MMS Read Service), the PL7-3 program can modify it once again.

Case 2

To avoid loosing intermediate values for a variable accessed in "bursts" by a remote station (sequence management).

Program as many instance EXECs for the MSEMA OFB for the same variable deemed to be "sensitive" as there are MMS services likely to cause simultaneous access. Testing the READY bit enables "separating" values that came to the interface in a batch:

The first EXEC of the OFB releases the first value that can be taken into account by the

PL7-3 application (MMS Write Service), by restarting the next EXEC, the interface will release the next value of the same variable that it will have saved because there was no associated EXEC, and so on.

__________________________________________________________________________________________

4 / 6

MSEMA OFB: Synchronizing Access to an MMS Server Variable 4

__________________________________________________________________________________________

Execution results:

• Ready goes to 0:

The designated variable is being accessed by the interface following a read/write request from the remote station.

• Ready goes from 0 to 1:

The variable is no longer being accessed, the PL7-3 application can use it.

Programming example:

Ensuring coherence for a variable of over 128 bytes.

The remote supervisor sends a WRITE that contains a sequence initializing a number of processes (symbolized by the INITSEQ local variable) to a server PLC using an association previously identified by an Accept (symbolized by PLCRCV2).

IF NOT B100 THEN

EXEC MSEMA0( ; PLCRCV2 ; ; INITSEQ ; =>) ;

SET B100; !

!< Wait until finished writing INIT values >

MSEMA0.READY

→

B200;

IF RE(B200) THEN JUMP PROCESS-INITSEQ

IF MSEMA0,ERROR THEN JUMP PROCESS-ERROR

Ensuring sequencing for a variable written in bursts.

The remote supervisor sends a number of WRITEs of the same variable (symbolized by

COLOR) with different value, for processing in sequence by a server PLC. They are sent using an association previously identified by an Accept (symbolized by PLCRCV2).

!< RECEIVE COLOR >

IF NOT B100 THEN EXEC MSEMA0( ; PLCRCV2 ; ; COLOR ; =>) ;

SET B100;

!< Wait end of processing for a color >

MSEMA0.READY

→

B200;

IF RE(B200) THEN JUMP PROCESS-COLOR

IF MSEMA0,ERROR THEN JUMP PROCESS-ERROR

!< PROCESS-COLOR >

! ——— succession of PL7-3 instructions ———

! IF COUNTER=0 THEN JUMP RECEIVE-COLOR

__________________________________________________________________________________________

4 / 7

__________________________________________________________________________________________

Remarks

• If 2 EXECs of MSEMA are programmed on the same variable and in the same

MAST cycle:

EXEC MSEMA1 (VARIABLE1);

...............

EXEC MSEMA0 (VARIABLE1); regardless of the instance number programmed first in the PL7-3 application, the lowest instance number value will always be executed first. The instances are stored in rising number order in the processor execution queues and executed at the end of the MAST cycle, in that order.

• If 2 EXECs of MSEMA are programmed on two different variables in the same

MAST cycle:

EXEC MSEMA0 (VARIABLE1);

...............

EXEC MSEMA0 (VARIABLE2); it is always the last programmed variable that will be taken into account. The parameters taken into account previously will be overwritten and the execution at the end of the MAST cycle will affect the last values of the stored parameters.

__________________________________________________________________________________________

4 / 8

Appendix 5

__________________________________________________________________________________________

5.1

Error Handling

Status:

Ind:

RCi:

Identifies the type of error (it can be accessed using APPLIDIAG).

There are two possible classes:

• OFB programming errors.

• MMS communication errors.

For the "MMS communication error class" the IND parameter identifies the cause of the MMS error.

If b8 = 1, the values of IND are given by the list of "MMS service execution errors" in Sub-section 4.2.

If b9 = 1, the IND errors are Error class\Error Code (MSB\LSB) from the

MMS standard or from the implementation of the remote service (corresponds to "PDU MMS Error".

Identifies MMS communication errors.

There are two possible classes:

If b8 = 1, error detected by the local module.

If b9 = 1, error detected by the remote module.

Identifies an error that occurred when accessing an MMS variable.

If b4 = 1, RCi contains the error type

(Refer to the list of RCi for each service).

(Corresponds to "Data access failure MMS").

__________________________________________________________________________________________

5 / 1

__________________________________________________________________________________________

Error analysis diagram

Corrective action First level diagnostics

▼

ERROR Bit =1

YES

Second level diagnostics

NONE

STATUS bits

0,1,2,3,5,6,7,12,

13,14,15=1

YES OFB programming error

See local application

STATUS bit 8 =1

YES

Local error see IND

See local application

STATUS bit 9 =1

YES

Remote error see IND

STATUS bit 4 =1

YES

Remote error accessing a variable see RCI

See remote applications

See

remote applications

__________________________________________________________________________________________

5 / 2

Appendix 5

__________________________________________________________________________________________

5.2

MMS Service Execution Error Indications (IND)

Value

1000

1001

2001

1002

1003

Description

Indicates the services were still being processed when a Conclude was sent. Wait until the end of processing before handling Conclude.

Indicates that the maximum number of services confirmed during processing on this association was exceeded. The maximum number of possible confirmed services depends on the number of associations defined in PL7-OSI (refer to Divider D, Sub-section 3.2-3).

Indicates that the maximum "Nesting_Level" value negotiated when the association was opened was exceeded. Example, a Write.req service used to write a table of structures was sent when the negotiated

"Nesting_Level" was 1.

Indicates that a named variable is being accessed when the VNAM parameter is not supported on the association.

Indicates that an "Array" type is specified when the STR1 parameter is not supported by the association.

Indicates that a "Structure" type is specified when the STR2 parameter is not supported by the association.

Service cannot be processed in the current module state. The service request must be repeated until no error condition occurs.

No module resources for processing the service. This may occur, for example, if the PL7-3 application opens more associations than are configured in the module.

The time-out for an MMS response from the remote device is exceeded

(Time_Out). When this error occurs, close the affected association using

ABORT as the module may be in an incoherent state. Also check that the remote device is still operational then, if necessary, increase the value of the Time_Out parameter in the MCNCT OFB prior to reopening the association.

The module does not have any open association with the references requested (APPLI and/or CHANNEL parameters). This may occur, for example, in one of the following cases:

• Send "Accept.req" without any association opened by the remote device,

• Send "Conclude.req" or "Abort.req" on an association that is not open,

• Send a confirmed service on an association that is not open.

__________________________________________________________________________________________

5 / 3

__________________________________________________________________________________________

Value Description

1004

1005

1006

1007

1008

1009

1011

1012

2000

The module already has an association open with the requested references (APPLI and CHANNEL parameters). This occurs if the PL7-3 application send two consecutive open association requests with the same MCNCT OFB instance number without first closing the previous instance.

Error code corresponding to a WARNING, the association can be used.

The module already has an association open with the same reference for the CHANNEL parameter and with a different reference for the APPLI parameter. This occurs if the PL7-3 application open an association with

Appli1 then using the same instance of the MCNCT OFB, opens an association with Appli2 without first closing the previous instance.

The association with the requested references (APPLI and CHANNEL parameters) has already been identified in the module. This occurs if the

PL7-3 application sends two consecutive "Accept" requests to Appli1 with the same instance of the MCNCT OFB.

Error code corresponding to a WARNING, the association can be used.

The value of the MCNCT OFB APPLI parameter used to send "Initiate.req" is not recognized by the module. Check the configuration of Remote

Application uploaded to the module.

The PL7-3 application is attempting to perform an "Accept" on an association that it opened and that is illegal.

"Abort.ind" returned by the module (this is not an error, only an indication).

The module is not yet operational for executing a service. Repeat the service request until no error code occurs (repeat execution of the affected

MMS service OFB).

Flow control returned that indicates an unconfirmed service that cannot be processed by the module. Repeat the service request until no error code occurs (repeat execution of the affected MMS service OFB).

Protocol error. Contact Telemecanique technical support.

__________________________________________________________________________________________

5 / 4

Appendix 5

__________________________________________________________________________________________

5.3

Error Codes Returned to Status by MMSLD V2.0

Bit

Bit 0

Bit 1

Bit 2

Bit 3

Bit 4

Bit 5

Bit 6

Description

Gate allocation error in the PLC message system. No message system resources available.

Corrective Action

No message system resources are available in the PLC processor. The

OFB can no longer dialog with the module. This situation can resolve itself after a few seconds.

MMS application failed or non-existent.

OSI application failed or non-existent.

Check that the MMS.BIN application is correctly loaded in the PLC processor an that there is a table of symbols for local variables.

Check that the OSI.BIN application is correctly loaded in the PLC processor.

Module failure.

Check the module terminal block, check that the module is installed in the configured location in the rack.

Interface error during message exchange.

Error loading the OSI configuration in the module.

Error loading the MMS table of symbols in the module.

These errors are caused by an interruption in the dialog between the PLC and the module. If on restart there are no serious errors, the OFB returns to normal operation (uploading the module) without further operator intervention.

Remarks:

• Setting the INHIB input to 1 resets the ERROR bit to 0 and the STATUS word takes the value 0,

• Resetting the INHIB input to 0 allow updating of the ERROR and STATUS outputs in the event of an error.

__________________________________________________________________________________________

5 / 5

__________________________________________________________________________________________

5.4

Adding an MMS Variable to an Existing Project

1. Adding a local variable to STATION 1:

• Start PL7-PMS on STATION 1

- MENU: C

ONFIGURATION

OCAL

ARIABLES

EFINE LOCAL VARIABLES

Enter the full characteristics of the variable, refer to Divider E, Sub-section 3.3.

- MENU: Configure/PLC

Generate the .BIN file

- MENU: T

RANSFER

ISK

→

PLC

Transfer the .BIN file to the PLC.

2. Adding a remote variable to STATION 2:

• Start PL7-PMS on STATION 2

- MENU: C

ONFIGURE

/MMS P

ROJECT

IRECTORY

EFINE REMOTE VARIABLES

Enter the full characteristics of the variable, refer to Divider E, Sub-section 3.1.

- MENU: C

ONFIGURE

EMOTE VARIABLES

Refer to Divider E, Sub-section 3.2.

Enter:

. CWi variables,

. The SDBASE "Alias" symbol

From the "D

EFINE

EMOTE

MMS V

ARIABLES

" window:

Select the associated MMS variable.

- MENU: C

ONFIGURE

/PLC

Generate the .BIN file

- MENU: T

RANSFER

ISK

→

PLC

Transfer the .BIN file to the PLC.

• Start PL7-3 on STATION 2

- Read the MMS.CST constants file

(READ function in selection: 3-CONSTANTS in PL7-3).

__________________________________________________________________________________________

5 / 6

________________________________________________________

General Appendix G

___________________________________________________________________________

Section

1 PICS

1.1

Information Relative to Implentation (PICS)

1.2

Supported MMS Services (PICS Service CBBs)

1.3

Supported MMS Parameters (Parameter CBBs)

1.4

Characteristics Specific to Implementation

(PICS Local Implementation Values)

Page

1/1

1/3

1/4

1/5

___________________________________________________________________________

G / 1

________________________________________________________

___________________________________________________________________________

G / 2

PICS 1

__________________________________________________________________________________________

1.1

Information Relative to Implementation (PICS)

Implementation's Vendor name

Implementation's Model Name

Implementation's Revision Identifier

Telemecanique

System Dependent

2.0

System Dependent Machine Name(s) and

Version Number(s)

Operating System(s)

MMS abstract syntax

MMS Version Number Supported

System Dependent

ISO/DIS 9506

ISO/IS 9506

0 and 1

Not supported MMS Companion Standard abstract syntaxes

MMS Companion Standard

Version Number Supported

Calling MMS-user

Called MMS-user

Not supported

Yes

Not Used List of Standardized Names

RequestDomainDownload

RequestDomainUpload

LoadDomainContent

StoreDomainContent

DeleteDomain

GetDomainAttributes

CreateProgramInvocation

DeleteProgramInvocation

Start

Stop

Resume

Reset

Kill

GetProgramInvocationAttributes

Server

DefineEventCondition

DeleteEventCondition

__________________________________________________________________________________________

1 / 1

__________________________________________________________________________________________

GetEventConditionAttributes

ReportEventConditionstatus

AlterEventConditionMonitoring

TriggerEvent

DefineEventAction

DeleteEventAction

GetEnventActionAttributes

ReportEventActionStatus

DefineEventEnrollement

DeleteEventEnrollement

AlterEventEnrollement

ReportEventEnrollementStatus

GetEventEnrollementAttributes

AcknowledgeEventNotification

AttachToEventCondition

EventNotification

GetAlarmSummary

GetAlarmeEnrollementSummary

ReadJournal

WriteJournal

InitializeJournal

CreateJournal

DeleteJournal

ReportJournalStatus

ObtainFile

__________________________________________________________________________________________

1 / 2

PICS 1

__________________________________________________________________________________________

1.2

Supported MMS Services (PICS Service CBBs)

Service Conformance Building Block

Initiate

Conclude

Cancel

UnsolicitedStatus

Status

GetNameList

Identify

Rename

GetcapabitlityList

Read

Write

InformationReport

GetVariableAccessAttributes

DefineNamedVariable

Server, Client or Both

Both

Server

Both

Server

DefineScatteredAccess

GetScatteredAccessAttributes

DeleteVariableAccess

DefineNamedVariableList

GetNamesVariableList

DeleteNamedVariableList

DefineNameType

GetNamedTypeAttributes

DeleteNamedType

Input

Outpout

TakeControl

RelinquishControl

DefineSemaphore

DeleteSemaphore

ReportSemaphoreStatus

__________________________________________________________________________________________

1 / 3

__________________________________________________________________________________________

Supported MMS Services (PICS Service CBB's)

ReportPoolSemaphoreStatus

ReportSemaphoreEntryStatus

AttachToSemaphore

InitiateDownloadSequence

DownloadSegment

TerminateDownloadSequence

InitiateUploadSequence

UploadSegment

TerminateUploadSequence

Server

1.3

Supported MMS Parameters (Parameter CBBs)

Parameter Conformance Building Block Server, Client or Both

STR1 (Support for ARRAYs) Yes

STR2 (Support for STRUCTUREs) Yes

NEST (Maximum Data Structure

Nesting Level)

NEST = 2 (1)

VNAM (Support for NAMED variables) Yes

VADR (Support for UNNAMED and

SINGLE variables)

VALT (Support for Alternate Access)

Yes*

VSCA (Support for Scarattered Access) No

TPY (Support for a Third Party File

Server

REAL (Support for REAL) No

ACKEC (Support of Acknowledgement No

Event Condition Parameter)

CEI (Support forEvaluation Interval

Parameter

* Read/Write Server only: No alternative access for writing a field with a Boolean or BitString1 table element type structure.

(1) Tables of tables and structures that have a structure as a field are not supported.

__________________________________________________________________________________________

1 / 4

PICS 1

__________________________________________________________________________________________

1.4

Characteristics Specific to Implementation (PICS Local

Implementation Values)

Local Implementation Value

Range of values for floating point numbers

Support

IEEE 754 (Single)

Supported values of the floating point exponent width IEEE 754 (Single)

Supported values of the floating point format width

Range of values for signed integer

Range of values for unsigned integer

Maximum length for-BIT STRING in bits

IEEE 754 (Single)

[-2147483648..2147483647]

[0..2147483647]

2048

4096

Symbolic

Maximum length for OCTET STRING in octet

Address formats for VADR horizontal CBB

Maximum Input Time Out in seconds

Level of support for time

Granularity of time in milliseconds

Uninterruptible access to variable

Date and time

Length of variable less than 120 bytes

Priority processing for semaphores

Capabilities of VMD

Local Detail

File Name Syntax

Yes refer to Document

Range of Maximum Services Outstanding Calling [0..2] ME[2..5]

Range of Maximum Services Outstanding Called [0..2] ME[2..5]

Execution Argument

Additionnal Code in Error Type Yes refer to Document

Additionnal Detail in Error Type

Method for Extended Derivation of

Status Information

Local Detail Calling/Called

Load Data Format

Maximum number of Upload State machines

[64..7168]

TSX PLC application format

__________________________________________________________________________________________

1 / 5

__________________________________________________________________________________________

1 / 6

________________________________________________________

Application Example H

___________________________________________________________________________

Section

1 Application Example

1.1

Presentation

1.2

R6S0 Device Application

1.2-1 Hardware Configuration

1.2-2 Master Task Program, Main Program Module:

MAST/MAIN

1.2-3 OSI Addresses, TSX ETH 200 Module

1.2-4 PL7-3 Constants

1.2-5 List of MMS Variables

1.2-6 List of PL7-3 Symbols

1.3

R6S1 Device Application

1.3-1 Hardware Configuration

1.3-2 Master Task Program, Main Program Module:

MAST/MAIN

1.3-3 OSI Addresses, TSX ETH 200 Module

1.3-4 PL7-3 Constants

1.3-5 List of MMS Variables

1.3-6 List of PL7-3 Symbols

Page

1/1

1/2

1/8

1/9

1/10

1/12

1/13

1/20

1/22

1/25

___________________________________________________________________________

H / 1

________________________________________________________

___________________________________________________________________________

H / 2

Application Example 1

1.1

Presentation

The example described in this Section is the one presented in the Methodology Section,

Divider B, Sub-section 2.1.

Remider of the OSI network layout

FTX 507

ETHERNET

APRIL R6S0

APRIL 7000

R6S1

TSX 7 TSX 7

1.2

R6S0 Device Application

1.2-1 Hardware Configuration

Rack reference: TSX RKN 82F

_____________________________________________________________________

RACK

0/1

PS M 0 1 2 3 4 5 6 7

___________________________________________________________________________

1 / 1

1.2-2 Master Task Program, Main Program Module: MAST/MAIN

<initialize variables for MCNCT0 (manage association C0)

! IF SY0+SY1 THEN 2->Mod_cnc0

W1 : Mod_cnc0

<initialize variables for INITIATE C0

! IF RE(I5,0) THEN 0->Com_cnc0

W0 : Com_cnc0

<initialize variables for CONCLUDE C0

! IF RE(I5,2) THEN 2->Com_cnc0

W0 : Com_cnc0

<initialize variables for ABORT C0

! IF RE(I5,3) THEN 3->Com_cnc0

W0 : Com_cnc0

<manage association C0 to R6S1

! IF RE(I5,0)+RE(I5,2)+RE(I5,3)

THEN EXEC MCNCT0(Res_cnc0;Com_cnc0;Mod_cnc0;R6s1;500=>Err_cnc0)

OFB: I/O PARAMETERS

Res_cnc0

Com_cnc0

Mod_cnc0

R6s1

500

MCNCT0

RESET : bit

COMMAND : word

MODULE : word

APPLI : pt_w

TIMEOUT : word

ERROR : bit Err_CNC0

CW0

: Res_cnc0

: Com_cnc0

: Mod_cnc0

: R6s1 remote application (R6S1)

: Err_cnc0

<display status connection C0

! Ste_cnc0->O4,0[4]

MCNCT0,STATE : Ste_cnc0

<if association C0 open, O3,0 blinks

! IF [Ste_cnc0=0] THEN SY6->O3,0

MCNCT0,STATE : Ste_cnc0

___________________________________________________________________________

1 / 2

Application Example 1

<display MWRITE0

! MWRIT0,READY.NOT MWRIT0,ERROR->O4,4

<write a W and a bit to R6S1 (C0) and restart soon as ready + count

! IF I5,4.MWRIT0,READY.[MCNCT0,STATE=0]

THEN INC W100;EXEC MWRIT0(B4;MCNCT0,CHANNEL;CW11;;W100;CW10;;W10;;;;;;=>);

INC W3;RESET B4

MCNCT0,CHANNEL

CW11

W100

CW10

W10

OFB: I/O PARAMETERS

RESET : bit

CHANNEL : word

VAR0 : word

SIZE0 : word

DATA0 : pt_w

MWRIT0

VAR1 : word

SIZE1 : word

DATA1 : pt_w

VAR2 : word

SIZE2 : word

DATA2 : pt_w

VAR3 : word

SIZE3 : word

DATA3: pt_w

ERROR : bit

MCNCT0,STATE

W100

: Ste_cnc0 W100

: Val_w100 value to write to remote w100

: Res_wri0

MCNCT0,CHANNEL : Cha_cnc0

CW11 : Word_w100 remote variable (R6S1)

CW10

W10

: Bit_b10 remote variable (R6S1)

: Val_b10 value to write to R6S1

___________________________________________________________________________

1 / 3

<display MREAD0

! MREAD0,READY.NOT MREAD0,ERROR->O3,7

<read W and bit written to R6S1 (C0) by previous OFB and restart ..

! IF I5,4.MREAD0,READY.[MCNCT0,STATE=0]

THEN EXEC MREAD0(B5;MCNCT0,CHANNEL;CW11;2;W110;CW10;2;W11;;;;;;=>);

INC W4;RESET B5

MCNCT0,CHANNEL

CW11

W110

CW10

W11

OFB: I/O PARAMETERS

MREAD0

RESET : bit

CHANNEL : word

VAR0 : word

SIZE0 : word

DATA0 : pt_w

VAR1 : word

SIZE1 : word

DATA1 : pt_w

VAR2 : word

SIZE2 : word

DATA2 : pt_w

VAR3 : word

SIZE3 : word

DATA3: pt_w

ERROR : bit

MCNCT0,STATE

: Ste_cnc0

: Res_rea0

MCNCT0,CHANNEL : Cha_cnc0

CW11 : Word_w100 remote variable (R6S1)

W110 : Res_w100 result read W100 from R6S1

CW10

W11

: Bit_b10 remote variable (R6S1)

: Res_b10 result read from R6S1

___________________________________________________________________________

1 / 4

Application Example 1

<display MREAD1 (structure + table)

! MREAD1,READY.NOT MREAD1,ERROR->O3,4

<read structure + a table of 250 DW from R6S1 (C0) + count

! IF I5,A.MREAD1,READY.[Ste_cnc0=0]

THEN EXEC MREAD1(;Cha_cnc0;Voit;14;Res_voit;T250_dw;1000;Res_dw;;;;;;=>);

INC W5

OFB: I/O PARAMETERS

MCNCT0,STATE

MCNCT0,CHANNEL

CW13

W122

CW15

W100

Cha _cnc0

Voit

Res voit

T250_dw

1000

Res_dw

RESET : bit

CHANNEL : word

VAR0 : word

SIZE0 : word

DATA0 : pt_w

MREAD1

VAR1 : word

SIZE1 : word

DATA1 : pt_w

VAR2 : word

SIZE2 : word

DATA2 : pt_w

VAR3 : word

SIZE3 : word

DATA3: pt_w

ERROR : bit

: Ste_cnc0

: Cha_cnc0

: Voit remote variable (R6S1)

: Res_voit result read structure from R6S1

: T250_dw remote variable (R6S1)

: Res_dw result read 250 dw from R6S1

___________________________________________________________________________

1 / 5

<display MURCV0

! MURCV0,READY.NOT MURCV0,ERROR->O3,6

<receive unsolicited data (information report) from R6S1 (C0)+ count

! IF I5,6.MURCV0,READY.[Ste_cnc0=0]

THEN EXEC MURCV0(Res_urc0;Cha_cnc0;Umot_w15;2;Res_uw15=>);INC W7

Res_urc0

Cha_cnc0

Umot_w15

Res_uw15

OFB: I/O PARAMETERS

RESET : bit

CHANNEL : word

VAR : word

SIZE : word

MURCV0

BUFFER : pt_w

ERROR : bit

MCNCT0,STATE

MCNCT0,CHANNEL

CW12

W20

: Ste_cnc0

: Res_urc0

: Cha_cnc0

: Umot_w15 remote variable (R6S1)

: Res_uw15 result receive info report

<Visu MURCV1

! MURCV1,READY.NOT MURCV1,ERROR->O3,5

<receive unsolicited data (information report) from R6S1 (C0) + count

! IF I5,7.MURCV1,READY.[Ste_cnc0=0]

THEN EXEC MURCV1(Res_urc1;0;Bit_b10;2;Res_b10=>);INC W6

Res_urc1

Bit_b10

Res_b10

OFB: I/O PARAMETERS

RESET : bit

CHANNEL : word

VAR : word

SIZE : word

BUFFER : pt_w

MURCV1

ERROR : bit

MCNCT0,STATE

CW10

W11

: Ste_cnc0

: Res_urc1

: Bit_b10 remote variable (R6S1)

: Res_b10 result read from R6S1

___________________________________________________________________________

1 / 6

Application Example 1

<read STATUS of R6S1 from C0

! IF I5,8.MRSTA0,READY.[Ste_cnc0=0]

THEN EXEC MRSTA0(Res_ssta;Cha_cnc0;=>)

OFB: I/O PARAMETERS

Res_ssta

Cha_cnc0

RESET : bit

CHANNEL : word

UNSOL : bit

MRSTA0

ERROR : bit

MCNCT0,STATE

MCNCT0,CHANNEL

: Ste_cnc0

: Res_ssta

: Cha_cnc0

<receive unsolicited STATUS sent by R6S1 to C0

! IF I5,9.MRSTA1,READY.[Ste_cnc0=0] THEN SET B13;

EXEC MRSTA1(Res_ssta;Cha_cnc0;B13=>)

OFB: I/O PARAMETERS

Res_ssta

Cha_cnc0

B13

RESET : bit

CHANNEL : word

UNSOL : bit

MRSTA1

ERROR : bit

MCNCT0,STATE

MCNCT0,CHANNEL

: Ste_cnc0

: Res_ssta

: Cha_cnc0

<display status (STATUS —>Physic ) remote device

! (MRSTA1,PHYSIC)->Physic;Physic,0->O3,1

W21 : Physical status remote device

<increment W120 for read from R6S1

! INC DW_120

W120 : DW_120 variable read by R6S1

___________________________________________________________________________

1 / 7

1.2-3 OSI Adresses, TSX ETH 200 Module

Network layer

_____________________________________________________________________

Values

CONFIGURATION TIMER (S)

NPDU LIFETIME (500 MS)

4954454C454D4543412E060001

Transport layer

_____________________________________________________________________

Values

RETRY TIMER (MS)

MAX RETRIES

WINDOW INFO TIMER (MS)

MAX CREDIT

2000

0001

Session layer

_____________________________________________________________________

Values

DISCONNECT TIME OUT (S) 60

0001

Application layer

_____________________________________________________________________

Values

APPLICATION NAME

AP TITLE (H)

AE QUALIFIER (H)

R6S0_MMS

00000001

MMS ASSOCIATIONS OPEN

MMS ASSOCIATIONS ACCEPTED

: 16

___________________________________________________________________________

1 / 8

Application Example 1

Remote applications

_________________________________________________________________

APPLICATION NAME

AP TITLE

AE QUALIFIER

PSEL

SSEL

TSEL

: R6S1_MMS

: 00000001

: 0001

: 4954454C454D4543412E060101

1.2-4 PL7-3 Constants

CW0 -> CW31 Application constant NB CW CONFIG. : 100

_______________________________________________________________

Constant Value

CW0 =8

CW5 =0

CW6 =0

CW7 =0

CW8 =0

CW9 =0

CW10 =0

CW11 =1

CW12 =3

CW13 =4

CW14 =0

CW15 =2

CW16 =0

CW17 =0

CW19 =0

CW20 =0

CW21 =0

CW22 =0

CW23 =0

CW24 =0

CW25 =0

CW26 =0

CW27 =0

CW28 =0

CW29 =0

CW30 =0

CW31 =0

CW1 = R6S1_MMS

___________________________________________________________________________

1 / 9

1.2-5 List of MMS Variables

List of Local MMS variables

________________________________________________________________

PL7_3 Object

MMS_Name

Scope

Type

: W50

: MT5_W50

: VMD

: AR-INT16 5

________________________________________________________________

PL7_3 Object

MMS_Name

Scope

Domain Name

Type

: W120

: MD_W120

: DOMAIN

: MMS

: AR-INT16 500

________________________________________________________________

PL7_3 Object

MMS_Name

Scope

Appli_Name

Type

: B50

: MABIT_50

: AA

: R6S1_MMS

: BOOL

________________________________________________________________

PL7_3 Object

MMS_Name

Scope

Appli_Name

Type

: DW200

: MADW_200

: AA

: R6S1_MMS

: AR-INT32 5

________________________________________________________________

___________________________________________________________________________

1 / 1 0

Application Example 1

List of remote MMS variables

________________________________________________________________

MMS Var

Scope

Type

Alias

PL7_3 Object

MMS Var Rank

: MBIT_B10

: VMD

: BOOL

: Bit_b10

: CW10

: 0

________________________________________________________________

MMS Var

Scope

Type

Alias

PL7_3 Object

MMS Var Rank

: MMOT_W100

: VMD

: INT16

: Mot_w100

: CW11

: 1

________________________________________________________________

MMS Var

Scope

Type

Alias

PL7_3 Object

MMS Var Rank

: MT250_DW1000

: VMD

: AR-UINT32 250

: T250_dw

: CW15

: 2

________________________________________________________________

MMS Var

Scope

Type

Alias

PL7_3 Object

MMS Var Rank

: MUMOT_W15

: VMD

: INT16

: Umot_w15

: CW12

: 3

________________________________________________________________

MMS Var

Scope

: VOITURE

: VMD

Type : STRUCT

Structure Description {

+0 INT16

+1 VSTR 10

+6 BOOL

}

Total size

Alias

PL7_3 Object

MMS Var Rank

: 7

: Voit

: CW13

: 4

________________________________________________________________

___________________________________________________________________________

1 / 1 1

1.2-6 List of PL7-3 Symbols

Variable Symbol

B50

CW0

CW10

CW11

CW12

CW13

CW15

DW200

W10

W11

W20

W21

W50

W100

DW1000

MCNCT0,IND

Res_tdw

Ind_cnc0

MCNCT0,CHANNEL Cha_cnc0

MCNCT0,INHIB Inh_cnc0

MCNCT0,READY

MCNCT0,STATE

MCNCT0,STATUS

Rea_cnc0

Ste_cnc0

Sts_cnc0

Com_cnc0

W110

W120

W122

W1000

Mod_cnc0

Tim_cnc0

Val_b10

Res_b10

Res_uw15

Physic

T5_w50

Val_w100

Res_w100

Dmot_120

Res_voit

Res_dw

Res_cnc0

Err_cnc0

Res_wri0

Res_rea0

Res_urc0

Res_urc1

Res_ssta

Seconde

Abit_50

R6s1

Bit_b10

Mot_w100

Umot_w15

Voit

T250_dw

Atdw_200

Display Comment spec. AA variable read by R6S1 remote application (R6S1) remote variable (R6S1) remote variable (R6S1) remote variable (R6S1) remote variable (R6S1) remote variable (R6S1) spec. AA variable read by R6S1 result read from R6S1 value to write to R6S1 result read from R6S1 resultat reception info report physical status of remote device variable written and read by R6S1 value to write to remote w100 result read W100 from R6S1 variable read by R6S1 result read structure from R6S1 result read 250 dw from R6S1

___________________________________________________________________________

1 / 1 2

Application Example 1

1.3

R6S1 Device Application

1.3-1 Hardware Configuration

Rack reference: TSX RKN 82F

_____________________________________________________________________

RACK

0/1

1 3

PS M 0 1 2 3 4 5 6 7

1.3-2 Master Task Program, Main Program Module: MAST/MAIN

<accept association C0 opened by R6S0

! IF RE(I2,0) THEN EXEC MCNCT0(Res_cnc0;1;7;R6s0;500=>Err_cnc0)

OFB: I/O PARAMETERS

Res_cnc0

R6s0

500

MCNCT0

RESET : bit

COMMAND : word

MODULE : word

APPLI : pt_w

TIMEOUT : word

ERROR : bit Err_CNC0

CW0

: Res_cnc0 reset ofb

: R6s0 remote application (R6S0)

: Err_cnc0

<if association C0 open, O3,0 blinks

! IF [MCNCT0,STATE=0] THEN SY6->O3,0

<send (info rep.) to R6S0 (C0) word w15 every second (after ACCEPT)

! IF I2,1.MUSND0,READY.SY6.[MCNCT0,STATE=0]

THEN INC W15;EXEC MUSND0(B6;MCNCT0,CHANNEL;;W15;;1;;;;;;;;;;;;=>)

___________________________________________________________________________

1 / 1 3

MCNCT0,CHANNEL

W15

OFB: I/O PARAMETERS

MUSND0

RESET : bit

CHANNEL : word

VAR0_B : pt_b

VAR0_W : pt_w

VAR0_DW : pt_d

NBELT0 : word

VAR1_B : pt_b

VAR1_W : pt_w

VAR1_DW : pt_d

NBELT1 : word

VAR2_B : pt_b

VAR2_W: pt_W

VAR2_DW : pt_d

NBELT2: word

VAR3_B: pt_b

VAR3_W: pt_w

VAR3_DW: pt_d

NELBELT3: word

ERROR : bit

W15

: Umot_w15 word sent by unsolicited /sec

: Res_snd0 reset ofb

<send (info rep.) to R6S0 (C0) bit B10 every second (after ACCEPT)

! IF I2,2.MUSND1,READY.NOT SY6.[MCNCT0,STATE=0]

THEN SY5->B10;EXEC MUSND1(B6;MCNCT0,CHANNEL;B10;;;1;;;;;;;;;;;;=>)

MCNCT0,CHANNEL

B10

OFB: I/O PARAMETERS

MUSND1

RESET : bit

CHANNEL : word

VAR0_B : pt_b

VAR0_W : pt_w

VAR0_DW : pt_d

NBELT0 : word

VAR1_B : pt_b

VAR1_W : pt_w

VAR1_DW : pt_d

NBELT1 : word

VAR2_B : pt_b

VAR2_W: pt_W

VAR2_DW : pt_d

NBELT2: word

VAR3_B: pt_b

VAR3_W: pt_w

VAR3_DW: pt_d

NELBELT3: word

ERROR : bit

B10 : Bit_b10

B6 : Res_snd0 reset ofb

___________________________________________________________________________

1 / 1 4

Application Example 1

<send UNSOL. STATUS to R6S0(C0) and monitor /10 cycles (after ACCEPT)

! IF I2,3.MSSTA0,READY.[MCNCT0,STATE=0]

THEN EXEC MSSTA0(Res_sta0;MCNCT0,CHANNEL;10=>)

Res sta0

MCNCT0,CHANNEL

OFB: I/O PARAMETERS

RESET : bit

CHANNEL : word

TCYCLE : word

MSSTA0

ERROR : bit

B7 : Res_sta0 reset ofb

<initialize variables to INITIATE association C1

! IF RE(I2,4) THEN 0->Com_cnc1

W1 : Com_cnc1

<initialize variable for CONCLUDE C1

! IF RE(I2,6) THEN 2->Com_cnc1

W1 : Com_cnc1

<initialize variable for ABORT C1

! IF RE(I2,7) THEN 3->Com_cnc1

W1 : Com_cnc1

<manage association C1 to R6S0

! IF RE(I2,4)+RE(I2,6)+RE(I2,7) THEN

EXEC MCNCT1(Res_cnc1;Com_cnc1;7;R6s0;500=>Err_cnc1)

Res_cnc1

Com_cnc1

R6s0

500

OFB: I/O PARAMETERS

MCNCT1

RESET : bit

COMMAND : word

MODULE : word

APPLI : pt_w

TIMEOUT : word

ERROR : bit Err_CNC1

CW0

: Res_cnc1 reset ofb

: Com_cnc1

: R6s0 remote application (R6S0)

: Err_cnc1

<display status association C1

! MCNCT1,STATE->O3,C[4]

<if association C1 open o3,1 blinks

! IF [MCNCT1,STATE=0] THEN SY6->O3,1

___________________________________________________________________________

1 / 1 5

<display MWRIT0

! MWRIT0,READY.NOT MWRIT0,ERROR->O3,4

<write a table of 5 W in R6S0 (C1) and count

! IF I2,8.MWRIT0,READY.[MCNCT1,STATE=0]

THEN INC Val_w50;EXEC MWRIT0(Res_rea0;MCNCT1,CHANNEL;T5_w50;10;Val_w50;;;;;;;;;=>);

INC W4

OFB: I/O PARAMETERS

Res_read

MCNCT1,CHANNEL

T5_W50

VAL_w50

RESET : bit

CHANNEL : word

VAR0 : word

SIZE0 : word

DATA0 : pt_w

MWRIT0

VAR1 : word

SIZE1 : word

DATA1 : pt_w

VAR2 : word

SIZE2 : word

DATA2 : pt_w

VAR3 : word

SIZE3 : word

DATA3: pt_w

ERROR : bit

W60

B11

CW10

: Val_w50 values to write to R6S0

: Res_rea0 reset ofb

: T5_w50 remote variable (R6S0)

<display MREAD1

! MREAD1,READY.NOT MREAD1,ERROR->O3,8

<read a table of 500 W specific MMS domain in R6S0 (C1) and count

! IF I2,A.MREAD1,READY.[MCNCT1,STATE=0]

THEN EXEC MREAD1(B12;MCNCT1,CHANNEL;Dmot_120;1000;Res_d120;;;;;;;;;=>);

INC W6

___________________________________________________________________________

1 / 1 6

Application Example 1

B12

MCNCT1,CHANNEL

Dmot_120

1000

Res_d120

OFB: I/O PARAMETERS

RESET : bit

CHANNEL : word

VAR0 : word

SIZE0 : word

DATA0 : pt_w

MREAD1

VAR1 : word

SIZE1 : word

DATA1 : pt_w

VAR2 : word

SIZE2 : word

DATA2 : pt_w

VAR3 : word

SIZE3 : word

DATA3: pt_w

ERROR : bit

CW31

W120

: Dmot_120 remote variable (R6S0)

: Res_d120 result read from R6S0

<display MREAD0

! MREAD0,READY.NOT MREAD0,ERROR->O3,7

<read tab 5 W + 1 BIT + tab 5 DW AA spec. from R6S0(C1)and count

! IF I2,9.MREAD0,READY.[MCNCT1,STATE=0]

THEN EXEC MREAD0(B12;MCNCT1,CHANNEL;CW10;10;W70;CW29;2;W110;CW30;20;W30;;;=>);

INC W5

OFB: I/O PARAMETERS

B12

MCNCT1,CHANNEL

CW10

W70

CW29

W110

CW30

W30

MREAD0

RESET : bit

CHANNEL : word

VAR0 : word

SIZE0 : word

DATA0 : pt_w

VAR1 : word

SIZE1 : word

DATA1 : pt_w

VAR2 : word

SIZE2 : word

DATA2 : pt_w

VAR3 : word

SIZE3 : word

DATA3: pt_w

ERROR : bit

CW10

W70

CW29

W110

CW30

: T5_w50 remote variable (R6S0)

: Res_w50 result read from R6S0

: Abit_50 remote variable (R6S0)

: Res_ab50 result read from R6S0

: Atdw_200 remote variable (R6S0)

___________________________________________________________________________

1 / 1 7

<open association C2 with APRIL

! IF RE(I2,F) THEN EXEC MCNCT2(B12;0;7;April_s;500=>)

B12

April_s

500

OFB: I/O PARAMETERS

MCNCT2

RESET : bit

COMMAND : word

MODULE : word

APPLI : pt_w

TIMEOUT : word

ERROR : bit

CW20 : April_s remote application (APRIL)

<send (info report) to APRIL (C2) w15 every second

! IF I2,B.MUSND1,READY.SY6.[MCNCT2,STATE=0]

THEN INC W15;EXEC MUSND1(B6;MCNCT2,CHANNEL;;W15;;1;;;;;;;;;;;;=>)

OFB: I/O PARAMETERS

MCNCT0,CHANNEL

W15

RESET : bit

CHANNEL : word

VAR0_B : pt_b

VAR0_W : pt_w

VAR0_DW : pt_d

MUSND1

NBELT0 : word

VAR1_B : pt_b

VAR1_W : pt_w

VAR1_DW : pt_d

NBELT1 : word

VAR2_B : pt_b

VAR2_W: pt_W

VAR2_DW : pt_d

NBELT2: word

VAR3_B: pt_b

VAR3_W: pt_w

VAR3_DW: pt_d

NELBELT3: word

ERROR : bit

W15

: Umot_w15 word sent by unsolicited /sec

: Res_snd0 reset ofb

___________________________________________________________________________

1 / 1 8

Application Example 1

<accept on association C3 opened by APRIL

! IF RE(I2,E) THEN EXEC MCNCT3(B12;1;7;April_c;500=>B13)

B12

April_c

500

OFB: I/O PARAMETERS

MCNCT3

RESET : bit

COMMAND : word

MODULE : word

APPLI : pt_w

TIMEOUT : word

ERROR : bit B13

CW40 : April_c remote application (APRIL)

<display MREAD2

! MREAD2,READY.NOT MREAD2,ERROR->O3,5

<read bit %MX28 from APRIL (C3) and count (after ACCEPT)

! IF I2,D.MREAD2,READY.[MCNCT3,STATE=0]

THEN EXEC MREAD2(B12;MCNCT3,CHANNEL;Mx28;2;Res_apri;;;;;;;;;=>);

INC W3

OFB: I/O PARAMETERS

B12

MCNCT3,CHANNEL

Mx28

Res_april

MREAD2

RESET : bit

CHANNEL : word

VAR0 : word

SIZE0 : word

DATA0 : pt_w

VAR1 : word

SIZE1 : word

DATA1 : pt_w

VAR2 : word

SIZE2 : word

DATA2 : pt_w

VAR3 : word

SIZE3 : word

DATA3: pt_w

ERROR : bit

CW33

W115

: Mx28 remote variable (APRIL 7000)

: Res_apri result read run bit (APRIL)

<animation variable read by R6S0

! INC W600;INC W1000

<animation variable read by R6S0

! INC Voit

W122 : Voit structure read by R6S0

___________________________________________________________________________

1 / 1 9

1.3-3 OSI Addresses, TSX ETH 200 Module

Network layer

____________________________________________________________________

Values

CONFIGURATION TIMER (S)

NPDU LIFETIME (500 MS)

4954454C454D4543412E060101

Transport layer

___________________________________________________________

Parameters Values

RETRY TIMER (MS)

MAX RETRIES

WINDOW INFO TIMER (MS)

MAX CREDIT

2000

0001

Session layer

____________________________________________________________________

Values

DISCONNECT TIME OUT (S) 60

0001

Application layer

____________________________________________________________________

Values

APPLICATION NAME

AP TITLE (H)

AE QUALIFIER (H)

MAX CREDIT

R6S1_MMS

2000

00000001

MMS ASSOCIATIONS OPEN : 16

MMS ASSOCIATIONS ACCEPTED : 16

___________________________________________________________________________

1 / 2 0

Application Example 1

Remote applications

_________________________________________________________________

APPLICATION NAME : R6S0_MMS

AP TITLE :

AE QUALIFIER

PSEL

: 00000001

SSEL

TSEL

: 0001

: 4954454C454D4543412E060001

APPLICATION NAME : APRIL_S1S

AP TITLE :

AE QUALIFIER

PSEL

: 00000002

SSEL

TSEL

: 0000

: 0101

: 49415052494C00000000EDA0011501

APPLICATION NAME : APRIL_S1C

AP TITLE :

AE QUALIFIER

PSEL

: 00000001

SSEL

TSEL

: 0000

: 0101

: 49415052494C00000000EDA0011501

___________________________________________________________________________

1 / 2 1

1.3-4 PL7-3 Constants

CW0 -> CW49 application constants NB CW CONFIG.: 128

_______________________________________________________________

Constant Value

CW0 =8

CW5 =0

CW6 =0

CW7 =0

CW8 =0

CW9 =0

CW10 =5

CW11 =0

CW12 =0

CW13 =0

CW14 =0

CW15 =0

CW16 =0

CW17 =0

CW18 =0

CW19 =0

CW20 =9

CW27 =0

CW28 =0

CW29 =0

CW30 =1

CW31 =2

CW32 =2

CW33 =4

CW34 =5

CW35 =3

CW36 =0

CW37 =0

CW38 =0

CW39 =0

CW40 =9

CW46 =0

CW47 =0

CW48 =0

CW49 =0

CW1 = R6S0_MMS

CW21 = APRIL_S1S

CW41 = APRIL_S1C

1.3-5 List of MMS Variables

List of local MMS variables

________________________________________________________________

PL7_3 Object

MMS_Name

Scope

Type

: M DAYTIME

: VND

: GENERALIZED_TIME

________________________________________________________________

PL7_3 Object

MMS_Name

Scope

Type

: W50

: MT5_W50

: VMD

: AR-INT16 5

________________________________________________________________

PL7_3 Object

MMS_Name

Scope

Type

: B10

: MBIT_B10

: VMD

: BOOL

1 / 2 2

Application Example 1

________________________________________________________________

PL7_3 Object

MMS_Name

Scope

Type

: W100

: MMOT_100

: VMD

: INT16

________________________________________________________________

PL7_3 Object

MMS_Name

Scope

Type

: DW1000

: MT 250_DW1000

: VMD

: AR-UINT32 250

________________________________________________________________

PL7_3 Object

MMS_Name

Scope

Type

: W200

: MT 500W

: VMD

: AR-INT16 500

________________________________________________________________

PL7_3 Object

MMS_Name

: W15

: MUMOT_15

Scope : VMD

Type : INIT16

________________________________________________________________

PL7_3 Object

MMS_Name

Scope

Type

: W900

: VOITURE

: VMD

: STRUCT

Structure description {

+0 INIT16 NB GATE

+1 VSTR 10 COLOR

+6 BOOL RADIO

Total size

}

: 7

________________________________________________________

PL7_3 Object

MMS_Name

: W910

: VSTRING

Scope

Type

: VMD

: VSTR 20

_ ______________________________________________________________

___________________________________________________________________________

1 / 2 3

List of remote MMS variables

___________________________________________________

MMS Var : MABIT_50

Appli_Name

Scope

Type

: R6S1_MMS

: AA

: BOOL

Alias

PL7_3

MMS Var Rank

: Abit_50

: CW29

: 0

_________________________________________________________

MMS Var

Appli_Name

: MADW_200

: R6S1_MMS

Scope

Type

Alias

: AA

: AR-INT32 5

: Atdw_200

PL7_3 Object : CW30

MMS Var Rank : 1

_________________________________________________________

MMS Var

Scope

Domain Name

Type

Alias

PL7_3 Object

: MD_W120

: DOMAIN

: MMS

: AR-INT16 500

: Dmot_120

: CW31

MMS Var Rank : 2

_________________________________________________________

MMS Var : MT250_DW1000

Scope

Type

Alias

: VMD

: AR-UINT32 250

: Mtdw1000

PL7_3 Object : CW35

MMS Var Rank : 3

_________________________________________________________

MMS Var

Scope

Type

: RUN_API

: VMD

: BSTR 1

Alias

PL7_3 Object

MMS Var Rank

: Mx28

: CW33

: 4

_________________________________________________________

MMS Var

Scope

: MT5_W50

: VMD

Type

Alias

PL7_3 Object

: AR-INT16 5

: T5_w50

: CW10

MMS Var Rank : 5

___________________________________________________

___________________________________________________________________________

1 / 2 4

Application Example 1

1.3-6 List of PL7-3 Symbols

Variable

CW40

DW30

W15

W50

W60

W70

W100

W110

W115

W120

W200

W122

W900

W910

DW1000

CW0

CW10

CW20

CW29

CW30

CW31

CW33

CW35

B10

B11

Symbol

April_c

Res_adw

Com_cnc0

Com_cnc1

Umot_w15

At5_w50

Val_w50

Res_w50

Mot_w100

Res_ab50

Res_apri

Res_d120

T_500w

Voit

Us_w900

Vstring

T250_dw

Res_cnc0

Err_cnc0

Res_snd0

Res_sta0

Res_cnc1

Err_cnc1

Bit_b10

Res_rea0

R6s0

T5_w50

April_s

Abit_50

Atdw_200

Dmot_120

Mx28

Mtdw1000

Display Comment reset ofb reset ofb reset ofb reset ofb reset ofb remote application (R6S0) remote variable (R6S0) remote application (APRIL) remote variable (R6S0) remote variable (R6S0) remote variable (R6S0) remote variable (APRIL 7000) remote variable (R6S0) remote application (APRIL) result read from R6S0 word sent by unsolicited /sec table 5 W written & read by april values to write to R6S0 result read from R6S0 word written and read by R6S0 result read from R6S0 result read run bit (APRIL) result read from R6S0 table of 500 W read by APRIL structure read by R6S0 visible string 20 read by APRIL tab DW1000->DW1250 rd. by R6S0

___________________________________________________________________________

1 / 2 5

___________________________________________________________________________

1 / 2 6

مرحباً! أنا روبوت دردشة يعمل بالذكاء الاصطناعي تم تدريبي خصيصًا لمساعدتك في Schneider Electric PL7OSI. لقد قمت بمراجعة المستند بدقة ويمكنني مساعدتك في تحديد موقع المعلومات التي تحتاجها بالضبط أو شرح المحتوى بعبارات واضحة و بسيطة. سواء كنت تبحث عن إرشادات حول ميزات معينة أو خطوات استكشاف الأخطاء وإصلاحها أو الاستخدام العام، فلا تتردد في طرح أسئلتك. كلما قدمت المزيد من التفاصيل حول مخاوفك أو احتياجاتك، زادت دقة و فعالية مساعدتي لك!