Schneider Electric Software Communication Application-Specific Functions, Micro/Junior/Pro, 4.5 User Guide

PL7 Junior/Pro

Communication Applications

Vol. 3

July 2006 eng

2

35011050 01 July 2006

Document Set

At a Glance This manual comprises 3 volumes: z

Vol. 1 z

Common Communication Function z z z

Remote Nano PLCs

Communication in Character Mode z

Communication via Uni-telway bus

Vol. 2 z z z z

Communication via Modbus

Communication via Modem

Communication via Modbus plus

Communication via FIPIO bus z

Vol. 3 z

Communication via FIPWAY network z z

Communication via ETHERNET network

Multinetwork architecture

Document Set

35011050 01 July 2006

3

Document Set

4

35011050 01 July 2006

Table of Contents

About the Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Part I Communication via FIPWAY network . . . . . . . . . . . . . . 13

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Chapter 1 Communication via Fipway network: General . . . . . . . . . . . . . 15

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

1.1

Introduction to Fipway communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Summary description of the FIPWAY network . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Communication function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Using common words . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Using shared tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

1.2

Characteristics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Hardware compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Software compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Operating mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Chapter 2 Configuring Fipway communication. . . . . . . . . . . . . . . . . . . . . 29

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

How to access the FIPWAY configuration screen. . . . . . . . . . . . . . . . . . . . . . . . 30

FIPWAY configuration screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

FIPWAY parameters linked to the telegrams and to the physical layer . . . . . . . 32

FIPWAY parameters linked to the common data . . . . . . . . . . . . . . . . . . . . . . . . 33

Example of configuration of shared table service . . . . . . . . . . . . . . . . . . . . . . . . 35

Chapter 3 Debugging Fipway communication . . . . . . . . . . . . . . . . . . . . . 37

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

FIPWAY debugging screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

FIPWAY debugging parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Requests available for the communication channel test . . . . . . . . . . . . . . . . . . . 41

How to test a channel with Identification and Mirror requests . . . . . . . . . . . . . . . 42

How to test a channel with requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

35011050 01 July 2006

5

6

Chapter 4 Language objects associated with FIPWAY

communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Language object for implicit exchange. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Language objects in explicit exchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Explicit exchange management and reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Language objects associated with the configuration . . . . . . . . . . . . . . . . . . . . . . 52

Part II Communication via ETHERNET network . . . . . . . . . . . . 53

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Chapter 5 Communication via Ethernet network . . . . . . . . . . . . . . . . . . 55

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

About ETHERNET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

General Information about the TSX ETY Modules. . . . . . . . . . . . . . . . . . . . . . . . 57

Details of Available Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Chapter 6 Facilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

6.1

TCP/IP Messaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Summary of TCP/IP Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Address Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Sub addressing and subnetwork mask . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

UNI-TE communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Modbus communication on the TCP/IP profile. . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Architecture supported by a Modbus communication on the TCP/IP profile.. . . . 73

Modbus messaging on the TCP/IP profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Managing the TCP connections for X-Way UNI-TE and Modbus . . . . . . . . . . . . 76

Opening a connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Closing a connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

What happens when a connection is broken . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

6.2

IO Scanning Facility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

IO Scanning Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Read and write zones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Scanning Period. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

6.3

BOOTP/DHCP Address Server Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

At a Glance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

BOOTP and DHCP Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

BOOTP Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

BOOTP and DHCP Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

6.4

SNMP Facility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

SNMP Communication on UDP/IP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

35011050 01 July 2006

6.5

Global Data Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Global Data Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

6.6

Managing Faulty Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Replacing Faulty Remote Stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

6.7

Time Synchronization Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Time Synchronization Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

6.8

HTTP on-board server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Embedded HTTP Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

HTTP Server Home Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

HTTP Server Index Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

HTTP Server Security Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Address Server Page for the HTTP Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

HTTP Server Rack Display Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

HTTP Server Data Editor Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Ethernet Module Diagnostic Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

NTP Diagnostics Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

HTTP Server User Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

6.9

Bandwidth Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

Bandwidth Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

6.10

ETHWAY Facility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

ETHWAY profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

Chapter 7 Configuration parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

7.1

Configuration parameters for TCP/IP facilities . . . . . . . . . . . . . . . . . . . . . . . . . 134

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

Configuration Parameters Linked to TCP/IP Utilities. . . . . . . . . . . . . . . . . . . . . 135

Configuration Parameters for IP Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

Connection configuration parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

Ethernet configuration parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

7.2

Configuration parameters for the IO Scanning facility. . . . . . . . . . . . . . . . . . . . 141

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

Configuration Parameters Linked to the IO Scanning Utility . . . . . . . . . . . . . . . 142

Configuration of general parameters for IO Scanning facility . . . . . . . . . . . . . . 144

Configuration of scanned peripheral devices . . . . . . . . . . . . . . . . . . . . . . . . . . 145

7.3

Configuration Parameters for the Address Server Utility. . . . . . . . . . . . . . . . . . 147

At a Glance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

Configuration Parameters Linked to the Address Server Utility . . . . . . . . . . . . 148

Address Server Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

7.4

Configuration parameters for the SNMP facility . . . . . . . . . . . . . . . . . . . . . . . . 150

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

Configuration Parameters Linked to the SNMP Utility. . . . . . . . . . . . . . . . . . . . 151

Configuration of the SNMP Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152

7.5

Configuration Parameters of the Global Data Utility . . . . . . . . . . . . . . . . . . . . . 154

At a Glance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154

35011050 01 July 2006

7

8

Configuration Parameters Linked to the Global Data Utility. . . . . . . . . . . . . . . . 155

Configuring the General Parameters for the Global Data Utility . . . . . . . . . . . . 157

Configuration of the Variables Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

7.6

Configuration Parameters of the Time Synchronization Service . . . . . . . . . . . . 159

At a Glance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

Configuration Parameters Linked to the Time Synchronization Service (NTP) . 160

Using the Time Synchronization Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

Configuration of the Time Synchronization Service (NTP) . . . . . . . . . . . . . . . . 164

7.7

ETHWAY profile configuration paramaters . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

Configuration Parameters Linked to the ETHWAY Profile. . . . . . . . . . . . . . . . . 168

Configuration of ETHWAY data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

Chapter 8 TSX ETY 110 Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

8.1

General points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

TSX ETY 110 Module : General points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

Performances. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

Module TSX ETY 110 operating modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176

Common functions on the ETHWAY and TCP/IP profile . . . . . . . . . . . . . . . . . . 177

8.2

Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178

Module configuration screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

Type of communication according to chosen configuration . . . . . . . . . . . . . . . . 181

Messaging configuration on the TCP/IP or ETHWAY profile . . . . . . . . . . . . . . . 182

Configuration of SNMP facility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184

Configuration of the Bridge function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186

Example of proprietary architecture ETHWAY. . . . . . . . . . . . . . . . . . . . . . . . . . 187

Example of the ETHWAY architecture connected to TCP/IP. . . . . . . . . . . . . . . 190

Example of connection to a non private TCP/IP network. . . . . . . . . . . . . . . . . . 193

Example of communication between Premium and Quantum . . . . . . . . . . . . . . 195

8.3

Debugging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197

Module debugging screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198

General debugging parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200

Debugging parameters for TCP/IP facilities. . . . . . . . . . . . . . . . . . . . . . . . . . . . 201

How to test TCP/IP communication with a Ping request . . . . . . . . . . . . . . . . . . 202

Debugging parameters of ETHWAY facilities . . . . . . . . . . . . . . . . . . . . . . . . . . 203

Requests available for the communication channel test . . . . . . . . . . . . . . . . . . 204

How to test a channel with Identification and Mirror requests . . . . . . . . . . . . . . 205

How to test a channel with requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207

8.4

Language objects associated with the TSX ETY 110 module . . . . . . . . . . . . . . 209

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209

Implicit Exchange Language Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210

35011050 01 July 2006

Language objects in explicit exchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213

Explicit exchange management and report . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215

Language objects associated with configuration. . . . . . . . . . . . . . . . . . . . . . . . 216

Chapter 9 TSX ETY 410•, TSX ETY PORT, TSX ETY 510• and

TSX WMY 100 modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219

At a Glance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219

9.1

General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220

At a Glance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220

General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221

Characteristics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222

Type of Supported Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225

Performance of IO Scanning Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227

Global Data Utility Performances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230

Operating Modes for TSX ETY 410•, TSX ETY PORT, TSX ETY 510• and

TSX WMY 100 Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232

9.2

Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234

At a Glance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234

Migration of Applications using TSX ETY 410/5101 Modules. . . . . . . . . . . . . . 235

Module Configuration Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236

Type of Communication According to Connection Configuration . . . . . . . . . . . 238

Configuration of TCP/IP Messaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243

IO Scanning Utility Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245

BOOTP Server Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248

DHCP Address Server Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250

Configuring the Global Data Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252

Configuration of the SNMP Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255

Configuring the Time Synchronization Service . . . . . . . . . . . . . . . . . . . . . . . . . 257

Configuring the Bandwidth Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262

Configuration of the Bridge Function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264

9.3

Debugging. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265

At a Glance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265

Module Debugging Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266

General debugging parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268

Debugging parameters for TCP/IP facilities . . . . . . . . . . . . . . . . . . . . . . . . . . . 269

How to test TCP/IP communication with a Ping request . . . . . . . . . . . . . . . . . . 270

Requests available for the communication channel test . . . . . . . . . . . . . . . . . . 271

How to test a channel with Identification and Mirror requests . . . . . . . . . . . . . . 272

How to test a channel with requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273

Debugging Parameters for the IO Scanning Utility . . . . . . . . . . . . . . . . . . . . . . 275

Debugging Parameters for the Global Data Utility . . . . . . . . . . . . . . . . . . . . . . 276

Bandwidth Monitoring Diagnostic Parameters . . . . . . . . . . . . . . . . . . . . . . . . . 277

9.4

Language objects associated with TSX ETY 410•, TSX ETY PORT,

TSX ETY 510• and TSX WMY 100 Modules. . . . . . . . . . . . . . . . . . . . . . . . . . . 278

At a Glance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278

35011050 01 July 2006

9

10

Implicit Exchange Language Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279

Explicit Exchange Language Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281

Explicit exchange management and report . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283

Language Objects Associated with Configuration . . . . . . . . . . . . . . . . . . . . . . . 284

9.5

Questions/Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286

Questions/Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286

Part III Multi-network architectures . . . . . . . . . . . . . . . . . . . . . . 289

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289

Chapter 10 Multi-network architectures: General . . . . . . . . . . . . . . . . . . 291

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291

General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292

Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293

Main address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295

Addresses of a multi-module station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297

Message handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298

Common word service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299

Shared table exchange service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300

Chapter 11 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301

Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302

Configuration of mono-network services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303

Configuration of multi-network services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304

How to configure a module as a bridge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306

Examples of bridge stations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308

Examples of partial routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313

35011050 01 July 2006

About the Book

At a Glance

Document Scope This manual deals with the software implementation of the communication application.

Validity Note The update of this publication includes the functions of the PL7 V4.5

Related

Documents

Title of Documentation

Hardware Implementation Manual

Reference Number

TSX DM 57 •• E

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

35011050 01 July 2006

11

About the Book

12

35011050 01 July 2006

Communication via FIPWAY network

I

Introduction

Subject of this part

What's in this

Part?

This part introduces the principles of configuring and using FIPWAY communication via PL7 software.

This part contains the following chapters:

Chapter

1

2

3

4

Chapter Name

Communication via Fipway network: General

Configuring Fipway communication

Debugging Fipway communication

Language objects associated with FIPWAY communication

Page

15

29

37

45

13

35011050 01 July 2006

FIPWAY communication

14

35011050 01 July 2006

Communication via Fipway network: General

1

Introduction

Subject of

Chapter

What's in this

Chapter?

This Chapter introduces communication via the Fipway network and its services.

This chapter contains the following sections:

Section

1.1

1.2

Topic

Introduction to Fipway communication

Characteristics

Page

16

24

15

35011050 01 July 2006

Fipway Communication: General

1.1

Introduction to Fipway communication

Introduction

Aim of this

Section

What's in this

Section?

This Section gives a summary description of the Fipway network and its associated services.

This section contains the following topics:

Topic

Summary description of the FIPWAY network

Communication function

Using common words

Using shared tables

Page

17

18

20

22

16

35011050 01 July 2006

Fipway Communication: General

Summary description of the FIPWAY network

Introduction

Associated manuals

To decentralize the periphery, intelligence and services over large distances,

Schneider Automation offers the local industrial network FIPWAY.

The FIPWAY network complies totally with the FIP standard with access via a bus arbiter.

A FIPWAY communication channel comprises three basic functions: z the inter-station messaging function which routes messages, z z the send/receive telegram function, a function for the production/consumption of common words (%NW) or shared tables.

If you require further information you should consult the following manuals:

Title

FIPWAY network - User guide

Micro PLCs - Installation manual

Premium TSX PLCs - Installation manual

Description

Detailed description of FIPWAY network and hardware installation

Hardware installation

Hardware installation

35011050 01 July 2006

17

Fipway Communication: General

Communication function

Introduction

Message handling

Common words

FIPWAY communication offers the following services: z the message handling service, z z the common words service, the shared table service.

The PCMCIA card message handling service is used: z z to exchange messages between two stations on the network, to broadcast messages to all stations on the network, z z the transmission and reception of telegrams between the stations at addresses 0 to 15.

to return to the device messages to be routed to another network (routing function).

The exchange of messages between the PLC and the PCMCIA card is done synchronously.

The common words service is made up of a set of dedicated %NW words.

Depending on its software configuration, each station on the network can access the database in read or write mode.

Updating takes place implicitly at the beginning of the cycle for reading and at the end of the cycle for writing. The application program simply consists of writing or reading these words.

The word addressing is as follows:

%NW{n,s}k

The following table describes the parameters for addressing common words: s k

Parameters n

Description

Network number

Station number

Number of the word

Note: The network number is used to select the network on which the common words are exchanged in the case of a multi-network configuration.

18

35011050 01 July 2006

Shared table

Fipway Communication: General

This service is used to exchange a table of internal %MW words split into as many zones as there are stations in the FIPWAY network.

The principle is based on the broadcast, by each PLC, of a word memory zone to the other stations in the network.

Updating takes place implicitly and independently from the execution cycle of the application program. The program simply consists of writing or reading %MW words.

Note: You must take care not to create memory conflicts between stations when configuring and assigning zones.

35011050 01 July 2006

19

Fipway Communication: General

Using common words

Introduction

Mono-network architecture

The following examples show the use of the common word service in the case of a mono-network and multi-network architecture.

The example is as follows:

FIPWAY

Station 1

%NW{1}0

%NW{1}1

%NW{1}2

%NW{1}3

Station 2

%NW{2}0

%NW{2}1

%NW{2}2

%NW{2}3

Station 3

%NW{3}0

%NW{3}1

%NW{3}2

%NW{3}3

Table of common words exchanged by stations 1, 2, 3

Three PLCs connected to a FIPWAY network exchange data between themselves via the intermediary of the common word service.

This service corresponds to the exchange of 4 words (%NW) per PLC.

20

35011050 01 July 2006

Multi-network architecture

The example is as follows:

2 4 5

Fipway Communication: General

Network #3

Network #1 Network #2

%NW{1.2}0

%NW{1.2}1

%NW{1.2}2

%NW{1.2}3

%NW{2.4}0

%NW{2.4}1

%NW{2.4}2

%NW{2.4}3

%NW{3.5}0

%NW{3.5}1

%NW{3.5}2

%NW{3.5}3

In a multi-network architecture, the common words are accessible via the network address of each module.

Reading and writing common words

The application program manages the content of the different common words: z z reading common words from remote stations, writing common words from the local station.

The syntax for writing or reading a common word is identical to that of internal words: z %MW10:=%NW{2.1}0

: reading a common word z %NW{2.2}3:= 357

: writing a common word

35011050 01 July 2006

21

Fipway Communication: General

Using shared tables

Introduction

Example

Three TSX 37 or TSX 57 PLCs connected to a FIPWAY network must exchange data between themselves (production parameter, action reports…) via the intermediary of the shared table service.

This service corresponds to the exchange of 32 words (%MW) per station. There can be 32 stations on the FIPWAY network.

The following illustration shows the example:

FIPWAY network 17

{17.1} {17.2} {17.3}

Station 1 exchanges a of 10 word table from %MW200 to %MW300 of station 2 and

%MW400 of station 3.

Station 2 exchanges a 20 word table from %MW310 to %MW210 of station 1 and

%MW410 of station 3.

Station 3 exchanges a 5 word table from %MW430 to %MW230 of station 1 and

%MW330 of station 2.

22

35011050 01 July 2006

Fipway Communication: General

Word production The following chart shows the production synoptic of the shared table.

Station 1

%MW200

Station 2

%MW300

Station 3

%MW400

10 words produced

%MW209

%MW210

%MW309

%MW310

%MW409

%MW410

20 words produced

%MW229

%MW230

%MW234

%MW329

%MW330

%MW334

%MW429

%MW430

5 words produced

%MW434 z z

Note: z From the address at the beginning of the configured table, the station reserves a table of 128 words dedicated to the shared table. The sum of the words produced by the other stations must be less than 128 words. If the length is less than 128, the unused words must not be written by the application program.

the data produced must be consecutive.

it is not necessary to have identical lengths.

35011050 01 July 2006

23

Fipway Communication: General

1.2

Characteristics

Introduction

Aim of this

Section

What's in this

Section?

This Section introduces the characteristics and constraints of using Fipway communication.

This section contains the following topics:

Topic

Hardware compatibility

Software compatibility

Performance

Operating mode

Page

25

26

27

28

24

35011050 01 July 2006

Fipway Communication: General

Hardware compatibility

General

Availability

Capacity

The binary output of the network is 1 Mbits/s.

The length of a segment depends on the type of branching. The maximum length is

1000 meters without a repeater.

When using repeaters (optic or electric), the maximum length between the two furthest stations depends on the number of repeaters which must be crossed.

The maximum length in km is calculated with the following formula:

L = 22 - (0,5 * R) where R is the number of repeaters crossed by the FIP data between the two stations.

The FIPIO bus is connected to the Hirschmann optic transmitters, with the

TSX FPP 200 PCMCIA card.

This type of communication is available for these PLCs: z

Premium via the intermediary of: z z z the TSX FPP 20 PCMCIA card, the TSX FPP 200 PCMCIA card.

Micro accepts the PCMCIA cards described below (TSX 37-21/22 PLCs).

A FIPWAY network segment is used to connect 36 devices. The devices for a

FIPWAY network can be: z z stations with the constraint of a maximum of 32 stations per segment, repeaters with the constraint of a maximum of 32 repeaters per segment,

On all the segments, a maximum of 64 stations can be connected to the network.

35011050 01 July 2006

25

Fipway Communication: General

Software compatibility

Message handling

Common words

Shared table

The maximum frame size depends on the type of transaction: z

For a message, the maximum frame is 128 bytes.

z

For a telegram, the maximum frame is 16 bytes.

Equally, the PCMCIA cards can process: 8 communication functions simultaneously

(8 in receive and 8 in send mode).

z for messages, 8 communication functions simultaneously (8 in send and 8 in receive mode).

z for telegrams, one single communication function (one in send and one in receive mode).

The common words service is supported by the stations at addresses between

0 and 31.

This database is made up of a maximum of 128 words for all the stations.

Each station can produce a maximum of between 0 and 4 common words and consume the other common words on the network.

The shared table service is supported by the stations at addresses between

0 and 31.

This database is made up of a maximum of 128 words for all the stations.

Each station can produce a maximum of between 1 and 32 words (defined in configuration mode) and consume the other words on the network.

26

35011050 01 July 2006

Fipway Communication: General

Performance

Transaction time The following table gives the transaction time between two stations:

Sending station Cyclic

Periodic 50 ms

Receiving station

Cyclic

50 ms

120 ms

Periodic 50 ms

-

160 ms

The telegram exchange time between two stations is 21 ms.

35011050 01 July 2006

27

Fipway Communication: General

Operating mode

Introduction

General chart

The following chart describes the operating modes of the TSX FPP 20 card.

The operating mode is as follows:

Module stopped

Module off

Power up

Operation

Module configured

Reset

Communication function

Module in self-test phase

Module not configured Self-tests OK

Configuration z z z z

After power-up the module self-tests. During this phase the LED indicators flash.

If there is no configuration, the card operates in message handling mode, and it can receive a PL7 configuration.

If there is a PL7 application in the PLC, the configuration of the application is transmitted to the module and the module starts up.

In case of power outage, the PLC processor performs a warm restart. The module then re-launches its self-test procedure.

28

35011050 01 July 2006

Configuring Fipway communication

2

Introduction

Subject of this

Chapter

What's in this

Chapter?

This Chapter describes the Configuration process during set-up of Fipway communication.

This chapter contains the following topics:

Topic

How to access the FIPWAY configuration screen

FIPWAY configuration screen

FIPWAY parameters linked to the telegrams and to the physical layer

FIPWAY parameters linked to the common data

Example of configuration of shared table service

Page

30

31

32

33

35

35011050 01 July 2006

29

Configuration

How to access the FIPWAY configuration screen

Introduction

How to access the link

This operation describes how to access the configuration parameters of the

FIPWAY link via the intermediary of the PCMCIA cards for Premium PLCs.

The following table shows the procedure for accessing the FIPWAY link:

Step

1

2

Action

Access the communication channel configuration screen.

Select the communication channel from the drop-down menu CHANNEL 1

Example

CHANNEL 0

CHANNEL 1

CHANNEL 1

(No PCMCIA submodule)

(Link not configured) MAST

3 Select one of the following PCMCIA cards from the drop-down menu: z TSX FPP 20 FIPWAY PCMCIA CARD z TSX FPP 200 FIPWAY PCMCIA CARD

Example

CHANNEL 1

CHANNEL 1 (No PCMCIA submodule)

(Link not configured)

TSX SCP 114 PCMCIA CARD RS485 MP

TSX FPP 20 PCMCIA FIPWAY CARD

TSX FPP 200 PCMCIA FIPWAY CARD

TSX FPP 10 PCMCIA FIPIO CARD

TSX MBP 100 PCMCIA MODBUS+ CARD

TSX MDM 10 PCMCIA MODEM CARD

30

35011050 01 July 2006

Configuration

FIPWAY configuration screen

Introduction

Illustration

This screen, split into two zones, is used to declare the communication channel and to configure the necessary parameters for a FIPWAY link.

The screen dedicated to FIPWAY communication looks like this:

1

2

TSX 57352 [RACK 0 POSITION 0]

Configuration

Designation: PROCESSOR TSX P 57352

CHANNEL 1

CHANNEL 1

FIPWAY

TSX FPP 20 PCMCIA FIPWAY CARD

MAST

Telegram

Telegram Management

Event processing 63

Physical layer

FIP

CB

Common Data

None

Common words:

Shared table (ST)

Bridge

Network Number

Table start address %MW

Produced zone address %MW

Length of produced zone in words

1

0

0

1

Elements and functions

This table describes the different zones that make up the configuration screen:

Address Zone

1 common

2 specific

Function

See (Communication applications Volume 1 - Overwiew of configuration screen).

is used to select or complete the parameters of a FIPWAY link.

It is split into three types of information: z Telegram management parameters, z z the parameters for the physical layer, the parameters for the common data.

35011050 01 July 2006

31

Configuration

FIPWAY parameters linked to the telegrams and to the physical layer

Introduction

Telegram window

Once the communication channel has been configured, complete the parameters dedicated to the telegrams and to the physical layer.

They are split into two windows: z the Telegram window, z the Physical layer window.

The window looks like this:

Telegram

Telegram Management

Event processing 63

It is used to complete: z

Telegram management : if the box is checked, the card is used to manage the z telegrams (default setting).

Event processing : this option is accessible only if telegram management has been activated. This option is used to manage the telegrams via an event task. If the box is checked, you must complete the number of the task where the telegrams will be processed.

The possible values are: z z z between 0 and 15 for Micro PLCs, between 0 and 31 for Premium PLCs of type TSX 57-10, between 0 and 63 for Premium PLCs of type TSX 57-20 and higher.

Note: If there is a PCMCIA in the module TSX SCY 21600/21601, telegram management is obligatory.

Physical layer window

The window looks like this:

Physical layer

FIP

CB

It is used to select the physical layer used for the communication.

Note: Only the physical layer specific to FIP is available.

32

35011050 01 July 2006

Configuration

FIPWAY parameters linked to the common data

Introduction

None

Common words

The window looks like this:

Common Data

None

Common Words

Shared table (ST)

Bridge

Network Number

Table start address %MW

Produced zone address %MW

Length of produced zone in words

1

0

0

1

It can be used to: z z z activate or deactivatethe exchange management of common data select the type of common data to exchange, complete the parameters necessary for this type of exchange.

Select this button if you wish to disable the management of common data in the application.

Select this button if you wish to have management of common data by common words (%NW).

When selecting this field, you must enter the local Network number to which the database is connected.

Note: The local network number corresponds to the number coded on the PCMCIA card.

Shared table Select this button if you wish to have management of common data by shared table.

When selecting this field, you must complete the following parameters: z

Table start address : this parameter shows the start of the table of internal words reserved in the PLC.

z

The 128 words following the start of the table will be reserved for the shared table function and are common to all stations.

Produced zone address : this parameter shows the address of the start of the zone of internal words produced by the station.

z

The address entered must take into account zones of internal words of the other stations. You must avoid an overlap of word zones between two stations.

Length of produced zone : this parameter shows the length (in words) of the table of internal words produced by the PLC (from 1 to 32 words).

35011050 01 July 2006

33

Configuration

Bridge This button is used to configure the routing function between networks.

See

Multi-network architectures, p. 289

34

35011050 01 July 2006

Configuration

Example of configuration of shared table service

Introduction The example shows how the stations are configured for using the shared table service.

These configurations use the example described in using shared tables.

Configuration of station 1

The example shows the configuration for station 1.

Common Data

None

Common Words

Shared table (ST)

Bridge

Network Number

Table start address %MW

Produced zone address %MW

Length of produced zone in words

17

200

200

10

Configuration of station 2

The example shows the configuration for station 2.

Common Data

None

Common Words

Shared table (ST)

Bridge

Network Number

Table start address %MW

Produced zone address %MW

Length of produced zone in words

17

300

310

20

The zone produced by the station starts at address %MW310.

The corresponding zone of %MW300 to %MW309 is reserved for the words produced by station 1.

35011050 01 July 2006

35

Configuration

Configuration of station 3

The example shows the configuration for station 3.

Common Data

None

Common Words

Shared table (ST)

Bridge

Network Number

Table start address %MW

Produced zone address %MW

Length of produced zone in words

17

400

430

5

The zone produced by the station starts at address %MW430.

The corresponding zone of %MW400 to %MW409 is reserved for the words produced by station 1.

The corresponding zone of %MW410 to %MW429 is reserved for the words produced by station 2.

36

35011050 01 July 2006

Debugging Fipway communication

3

Introduction

Subject of this

Chapter

What's in this

Chapter?

This Chapter describes the Debugging process during set-up of Fipway communication.

This chapter contains the following topics:

Topic

FIPWAY debugging screen

FIPWAY debugging parameters

Requests available for the communication channel test

How to test a channel with Identification and Mirror requests

How to test a channel with requests

Page

38

39

41

42

44

35011050 01 July 2006

37

Debugging

FIPWAY debugging screen

Introduction

Illustration

This screen, split into two zones, is used to debug a FIPWAY link.

The screen dedicated to FIPWAY communication looks like this:

1

2

TSX 57352 [RACK 0 POSITION 1]

Debugging

Designation: TSX P 57352 PROCESSOR Version: 3.3

CHANNEL 1

CHANNEL 1

FIPWAY

TSX FPP 20 PCMCIA FIPWAY CARD

MAST

Channel Information

Network address

Station Address

23 Bus arb.

8

Bridge

Common data Common Words

Channel Test

Identification

Message Errors

Messages sent and not acknowledged

Message Refused

Receive Response

Reset Counters

Counters

Reset Counters

Enter Request

Mirror

ASCII Hex.

Stations

DIAG...

DIAG...

0

0

Elements and functions

This table describes the different zones that make up the debugging screen:

Address Zone

1 common

2 specific

Function

See (Communication applications Volume 1 - Description of communication debugging screens).

is used to access the debugging parameters of a FIPWAY link.

It is split into three windows: z z z information on the channel, information on the message errors, the possibility of testing the communication channel.

38

35011050 01 July 2006

Debugging

FIPWAY debugging parameters

Introduction

Channel information

Message errors

The specific part is split into three windows: z z z the Channel information window, the Message errors window, the Channel test window.

The window looks like this:

Channel Information

Network address

Station Address

23 Bus arb.

8

Bridge

Common data Common Words

It shows information concerning the communication channel: z

Network address : this field indicates the network address coded on the PCMCIA card.

z z

Station address : this field indicates the station address coded on the PCMCIA card.

Common data : this field shows the type of common data selected in configuration mode.

z z

B.A.

: this field indicates if the local PCMCIA card is the bus arbiter of the FIPWAY network. In this case, the box is shaded.

Router : this field indicates if the local PCMCIA card is configured as a Bridge

(router). In this case, the box is shaded.

The window looks like this:

Message Errors

Messages sent and not acknowledged

Messages Refused

Reset Counters

0

0

This window displays the PCMCIA card error counters: z z

Messages sent and not acknowledged ,

Messages refused .

The button Reset Counters resets these counters.

35011050 01 July 2006

39

Debugging

Channel test The window looks like this:

Channel Test

6

14

Identification

Counters

Reset Counters

Enter Request

Mirror

Stations

Receive Response

...TSX FPP20.../...

ASCII Hex.

This window is used to test a communication channel by sending a request to one of the stations on the network.

40

35011050 01 July 2006

Debugging

Requests available for the communication channel test

Introduction

Test conditions

Available requests

This page describes the different possibilities for testing a communication channel from the debugging screen.

Sending a request to an unconnected station results in an error message.

The Channel Test window allows the following requests: z

Identification : prompts the Identification request to be sent to the designated slave, z z

Counters : prompts the Read error counters request to be sent to the designated station,

Reset Counters : prompts the designated station’s error counters to be reset to zero, z z

Enter request : allows a UNI-TE request, other than those provided by the command buttons, to be sent to the designated station. Selecting this function gives access to a screen that allows you to select the parameters that are specific to the request (request code must be coded in hexadecimal),

Mirror : allows a mirror request to be sent to the designated station. Selecting this function gives access to a screen that allows you to select the length of the character string to be sent (a maximum of 80 characters ). The PLC then sends this character string (ABCD….) to the destination device. The latter automatically sends the character string that was received back to the sender.

35011050 01 July 2006

41

Debugging

How to test a channel with Identification and Mirror requests

Introduction This page indicates the procedure for testing a communication channel by means of

Identification and Mirror requests.

How to identify a station

The following procedure is used to identify a designated station.

Step

1

2

Actions

Select the address of the station to be interrogated using the Station field.

Click on the Identification button.

Result

The response appears in the Receive Response window:

Receive Response

...TSX FPP20.../...

ASCII Hex.

42

35011050 01 July 2006

Debugging

How to send the

Mirror request

The following procedure is used to send the Mirror request and thus to test the routing of information between two devices.

Step

1

2

Action

Select the address of the station to be interrogated using the Station field.

Click on the Mirror button.

Result

The following window appears:

Mirror Request

Length of data to be sent

Send Cancel

8

3

4

Enter the length of data to be sent (maximum 80 characters).

Click on the Send button.

Result

The response appears in the Receive Response window:

Receive Response

ABCDEFGH

ASCII Hex.

The response contains: z the character string ABCDEFGH that corresponds to the length of data sent 8.

35011050 01 July 2006

43

Debugging

How to test a channel with requests

Introduction

How to send a request

This page indicates the procedure for testing a communication channel from the debugging screen using different requests.

The following procedure is used to send a request, other than those provided by the command buttons, to a designated station.

Step

1

2

Action

Select the address of the station to be interrogated using the Station field.

Click on the Enter Request button.

Result

The following window appears:

Enter Request

Request Code (Hexadecimal)

fa

Data (Hexadecimal)

1234db

3

4

5

Send Cancel

The data sent in this example is coded on 3 bytes.

Enter the function code (coded in hexadecimal on one byte), corresponding to the request that you want to send.

Enter the data to be sent by coding all the data in hexadecimal. Enter the data continuously without any intervening spaces.

Click on the Send button.

Result

The response appears in the Receive Response window:

Receive Response

1234DB

ASCII Hex.

the response from the example has data on 3 bytes (12 43 DB).

44

35011050 01 July 2006

Language objects associated with

FIPWAY communication

4

Introduction

Aim of this section

What's in this

Chapter?

This chapter introduces the language objects linked to FIPWAY communication.

This chapter contains the following topics:

Topic

Language object for implicit exchange

Language objects in explicit exchange

Explicit exchange management and reports

Language objects associated with the configuration

Page

46

48

51

52

45

35011050 01 July 2006

FIPWAY language objects

Language object for implicit exchange

Introduction

Bit objects

This page describes all the language objects for implicit exchange in FIPWAY communication that can be displayed or modified by the application program.

(Communication applications Volume 1 - Default exchanges)

The table below shows the different bit objects for implicit exchange.

Object (1) Function

%Ixy.MOD.ERR Module error bit

%Ixy.i.ERR

Channel error bit

Meaning

This bit set to 1, indicates a module error (at least one of the channels has an error, for instance.

This bit set to 1, indicates a line fault.

Key

(1) Address xy.i

z x: corresponds to the rack number z z y: corresponds to the module number i: corresponds to the channel number

46

35011050 01 July 2006

Word objects

FIPWAY language objects

The table below shows the different word objects for implicit exchange.

Object (1)

%IWxy.i.0

%IWxy.i.1

...

%IWxy.i.5

Function

Network status

Common data refresh flags

...

Common data refresh flags z z z z z z z z

Meaning z x0 = 1: if at least one of the stations is present z z x0 = 1: the common words or the words from the shared table from station 0 are refreshed.

...

x7 = 1: the common words or the words from the shared table from station 7 are refreshed.

x8 = 1: the common words or the words from the shared table from station 0 are refreshed.

...

x15 = 1: the common words or the words from the shared table from station 7 are refreshed.

...

z z x0 = 1: the common words or the words from the shared table from station 48 are refreshed.

...

x7 = 1: the common words or the words from the shared table from station 55 are refreshed.

x8 = 1: the common words or the words from the shared table from station 56 are refreshed.

...

x15 = 1: the common words or the words from the shared table from station 63 are refreshed.

Key

(1) Address xy.i

z x: corresponds to the rack number z z y: corresponds to the module number i: corresponds to the channel number

Common words The following table describes the words of the input channels:

Object

%NW{n.s}0 to

%NW{n.s}3

Function

Common words

Meaning corresponds to the exchanged common data

35011050 01 July 2006

47

FIPWAY language objects

Language objects in explicit exchange

Introduction This page describes all the language objects for explicit exchange in FIPWAY communication that can be displayed or modified by the application program.

(Communication applications Volume 1 - Specified exchanges: General points)

48

35011050 01 July 2006

Word objects

FIPWAY language objects

The table below shows the different word objects for explicit exchange.

Object (1) Function

%MWxy.MOD.2

Module status

%MWxy.i.2

%MWxy.i.3

%MWxy.i.4

%MWxy.i.5

%MWxy.i.6

Standard channel status

Specific channel status

Error counters

Error counters

Network/station address z z z z z z z z

Meaning x0 = 1: defective module x1 = 1: functional error (error between the processor and the module, adjustment or configuration error, etc.) x2 = 1: terminal block fault (not connected) x3 = 1: self-tests running x4 = 1: reserved x5 = 1: error in hardware or software configuration (the module present is not that declared in the configuration, the sub-modules are not compatible) x6 = 1: missing module x7 = 1: error in one of the sub-modules z z z z z z z x0 = 1: only station on the network x1 = 1: not used x2 = 1: transmission line error x3 = 1: not used x4 = 1: internal software fault x5 = 1: hard- or software error or absence of configuration x6 = 1: communication problem with the processor x7 = 1: application fault (double address station) z

Byte 0: z x0 = 0: if bridge (0 if not router)

Byte 1: z z z

= 16#00: unsupported bus arbiter function

= 16#03: active bus arbiter function

= 16#20: bus arbiter function in standby

Unacknowledged messages

Refused messages

Byte 0: station number

Byte 1: network number

35011050 01 July 2006

49

FIPWAY language objects

Object (1)

%MWxy.i.7

%MWxy.i.8

...

%MWxy.i.11

Function

Common words or shared table information

Status of stations from 0 to 15

...

Status of stations from 48 to 63 z z z z z z z z z z z z z z z z z z z z z z

...

Meaning

Byte 0: z z

= 16#00: inactive service

= 16#01: read/write of common words z z

= 16#02: reading of common words

= 16#03: participation in the exchange of a shared table (operation without error)

= 16#04: overlap of the exchange zone of a z z shared table

= 16#05: exchange error of a shared table

Byte 1: size x0 = 1: station 0 present (= 0 absent) x1 = 1: station 1 present (= 0 absent) x2 = 1: station 2 present (= 0 absent) x3 = 1: station 3 present (= 0 absent) x4 = 1: station 4 present (= 0 absent) x5 = 1: station 5 present (= 0 absent) x6 = 1: station 6 present (= 0 absent) x7 = 1: station 7 present (= 0 absent) x8 = 1: station 8 present (= 0 absent) x9 = 1: station 9 present (= 0 absent) x10 = 1: station 10 present (= 0 absent) x11 = 1: station 11 present (= 0 absent) x12 = 1: station 12 present (= 0 absent) x13 = 1: station 13 present (= 0 absent) x14 = 1: station 14 present (= 0 absent) x15 = 1: station 15 present (= 0 absent) x0 = 1: station 48 present (= 0 absent)

...

x7 = 1: station 55 present (= 0 absent) x8 = 1: station 56 present (= 0 absent)

...

x15 = 1: station 63 present (= 0 absent)

Key

(1) Address xy.i

z x: corresponds to the rack number z z y: corresponds to the module number i: corresponds to the channel number

50

35011050 01 July 2006

FIPWAY language objects

Explicit exchange management and reports

Introduction

Word objects

This page describes all the language objects that manage explicit exchanges.

(Communication applications Volume 1 - Exchange and report management)

The table below shows the different word objects for the management of explicit exchanges.

Object (1) Function

%MWxy.MOD.0 Module exchanges in progress

%MWxy.MOD.1 Module report

%MWxy.i.0

%MWxy.i.1

Channel exchanges in progress

Channel report z z z z

Meaning z z z x0 = 1: status reading in progress x1 = 1: sending of command parameters to the communication module x2 = 1: sending of adjustment parameters to the communication module x1 = 0: command parameters received and accepted by the module x2 = 0: adjustment parameters received and accepted by the module z z z x0 = 1: status reading in progress x1 = 1: sending of command parameters to the communication channel x2 = 1: sending of adjustment parameters to the communication channel x1 = 0: command parameters received and accepted by the communication channel x2 = 0: adjustment parameters received and accepted by the communication channel

Key

(1) Address xy.i

z z z x: corresponds to the rack number y: corresponds to the module number i: corresponds to the channel number

35011050 01 July 2006

51

FIPWAY language objects

Language objects associated with the configuration

Introduction

Internal constants

This page describes all the configuration language objects for FIPWAY communication that can be displayed by the application program.

The following table describes the internal constants:

Object Function

%KWxy.i.0

Type

%KWxy.i.1

Physical layer

%KWxy.i.2

Supported services

Meaning

Byte 0 = 4 for FIPWAY communication

Byte 0: station address z z

= 0: FIP physical layer

= 1: WORLD FIP physical layer byte 1: reserved

Byte 0: common data z = 16#00: none z = 16#01: common words z = 16#02: shared table

Byte 1: telegrams z z

= 16#00: unsupported services

= 16#01: supported

Address of the beginning of the shared table %KWxy.i.3

Shared table information

%KWxy.i.4

Common words and shared table

Byte 0: the number of common words or size of production zone of the shared table

Byte 1: Address (in bytes) of the beginning of the production zone of the shared table

52

35011050 01 July 2006

Communication via ETHERNET network

II

Introduction

Subject of this part

What's in this

Part?

This part introduces the Communication function on the Micro/Premium PLCand describes its implementation with PL7 software.

This part contains the following chapters:

Chapter Chapter Name

5 Communication via Ethernet network

6

7

Facilities

Configuration parameters

8

9

TSX ETY 110 Module

TSX ETY 410•, TSX ETY PORT, TSX ETY 510• and TSX WMY 100 modules

Page

55

61

133

171

219

53

35011050 01 July 2006

ETHERNET communication

54

35011050 01 July 2006

Communication via Ethernet network

5

Introduction

Subject of this chapter

What's in this

Chapter?

This chapter introduces communication via Ethernet network and its facilities.

This chapter contains the following topics:

Topic

About ETHERNET

General Information about the TSX ETY Modules

Details of Available Functions

Page

56

57

59

35011050 01 July 2006

55

General points

About ETHERNET

Introduction

Associated manuals

ETHERNET communication is essentially used for the following applications: z co-ordination between PLCs, z z z local or centralized monitoring, communication with production management data processing, communication with remote inputs/outputs.

Two communication profiles are supported by the ETHERNET network modules: z the ETHWAY profile, which restarts all the devices of the X-WAY communication architecture: z

X-WAY addressing system, z z z z

UNI-TE messaging, distributed databases (common words).

TCP/IP profile on ETHERNET allowing communication in: z

UNI-TE messaging with all of the X-WAY architecture,

Modbus messaging.

The ETHERNET network modules also support the SNMP standard network management protocol as an agent.

If you require fuller information you should consult the following manuals:

Title

ETHERNET network - Reference manual

Premium TSX PL7s - Set up manual

Momentum Bases - Set up manual

Description

Detailed description of the ETHERNET network

Hardware set up

Hardware and software set up of the

Momentum TSX

56

35011050 01 July 2006

General points

General Information about the TSX ETY Modules

At a Glance ETHERNET network communication is available for Premium PLCs using: z

TSX ETY 110 and TSX ETY 110 WS modules, z z

TSX ETY 410•, TSX ETY PORT and TSX ETY 510• modules, the TSX ETY 210 module.

They have several types of interface.

The TSX ETY 110 module

Connection can be made: z to an ETHWAY profile network supporting the following utilities: z common words, z z

UNI-TE messaging, to a TCP/IP profile network supporting the following utilities: z z

UNI-TE and Modbus messaging,

SNMP management.

For the

TSX ETY 110 WS module

Connection can be made: z to an ETHWAY profile network supporting the following utilities: z common words, z z

UNI-TE messaging, to a TCP/IP profile network supporting the following utilities: z z

UNI-TE and Modbus messaging,

SNMP management.

z z

TCP direct access, access to the Web-user pages HTTP server.

TSX ETY 410• and

TSX ETY PORT modules

Connection can be made: z to a TCP/IP profile network supporting the following utilities: z

UNI-TE and Modbus messaging, z z z z z z

SNMP management, input/output management (I/O Scanner),

IP address management (BOOTP/DHCP), access to the embedded Web server, common data exchange between stations (Global Data), diagnostics from Web pages.

35011050 01 July 2006

57

General points

The

TSX ETY 510• module

Connection can be made: z to a TCP/IP profile network, which is necessary when using FactoryCast and which supports the following utilities: z

UNI-TE and Modbus messaging, z

SNMP management, z z z z z z z z time synchronization (NTP), input/output management (I/O Scanner),

IP address management (BOOTP/DHCP), access to the embedded Web server, common data exchange between stations (Global Data), diagnostics from Web pages, access to the Web-user pages HTTP server, with direct TCP access.

The TSX ETY 210 module

Connection can be made: z to an ETHWAY profile network supporting the following utilities: z z common words,

UNI-TE messaging.

z to a TCP/IP profile network supporting the following utilities: z

UNI-TE and Modbus messaging, z z

SNMP management, specific to redundancy.

58

35011050 01 July 2006

General points

Details of Available Functions

At a Glance Depending on the type of ETHERNET module selected, certain functions will or will not be accessible.

Selection Guide The summary table below shows the various selections possible:

Function TSX ETY 110 TSX ETY 110 WS TSX ETY 410• /

TSX ETY PORT

Connection at 10 Mbits/s in Half/Full

Duplex in Half/Full Duplex in Half/Full

Duplex

Connection at 100 Mbits/s -

TCP/IP utility

SNMP utility:

Standard MIB

MIB Ethernet Transparent

Factory

IO Scanner Utility

Address Server utility

(BOOT/DHCP)

-

-

X

-

X

-

-

-

-

X

X in Half Duplex

X

X

X

X

X

UNI-TE messaging

Modbus messaging

ETHWAY profile

Software loading via FTP

(firmware)

X

X

X

X

X

X

X

X

-

X

X

X

-

-

-

X

X

X

TSX ETY 510• TSX ETY 210

X

X

X

X

-

X

X

X in Half/Full

Duplex in Half Duplex

X

X

X

X

-

-

-

-

-

-

in Half/Full

Duplex

X

X

X

X

X

X

Embedded HTTP server -

Global Data -

Diagnostics from Web pages

User WEB pages HTTP server

-

Redundancy

TCP direct access

Time synchronization utility

-

Legend

X

-

-

-

Available

Not available

-

-

X

X

-

-

-

-

-

X

X

X

-

-

-

X

35011050 01 July 2006

59

General points

60

35011050 01 July 2006

Facilities

6

Introduction

Subject of this chapter

What's in this

Chapter?

This chapter introduces the main points of the different facilities used by the modules.

This chapter contains the following sections:

Section

6.1

6.2

6.3

6.4

6.5

6.6

6.7

6.8

6.9

6.10

Topic

TCP/IP Messaging

IO Scanning Facility

BOOTP/DHCP Address Server Utility

SNMP Facility

Global Data Utility

Managing Faulty Devices

Time Synchronization Service

HTTP on-board server

Bandwidth Monitoring

ETHWAY Facility

Page

62

82

89

95

98

101

102

103

130

131

35011050 01 July 2006

61

Facilities

6.1

TCP/IP Messaging

Introduction

Subject of this sub-chapter

What's in this

Section?

This sub-chapter mentions the functions and characteristics of the TCP/IP profile.

This section contains the following topics:

Topic

Summary of TCP/IP Characteristics

Address Management

IP Address

Sub addressing and subnetwork mask

UNI-TE communication

Modbus communication on the TCP/IP profile

Architecture supported by a Modbus communication on the TCP/IP profile.

Modbus messaging on the TCP/IP profile

Managing the TCP connections for X-Way UNI-TE and Modbus

Opening a connection

Closing a connection

What happens when a connection is broken

Page

63

64

66

68

70

71

73

74

76

77

79

80

62

35011050 01 July 2006

Facilities

Summary of TCP/IP Characteristics

TCP/IP

Communication

Profile

OSI Model

7 - Application layer

4 - Transport layer

The following diagram illustrates the make-up of a typical TCP/IP stack.

Direct access

UNI-TE

X-WAY addressing

TCP

Modbus

ETHERNET

HTTP BOOTP

UDP

SNMP

ETHWAY

UNI-TE

COM

3 - Network layer

2 - Link layer

1 - Physical layer

IP

ETHERNET II / 802.3

Adressing

X-WAY

Communication

Port

The communication port reserved for the TSX ETY module is the TCP 502 port.

When a client wants to access the module server, s/he should go to this port.

Timeout on TCP

Connection

If a TCP connection cannot be established (when the destination is absent for example), the timeout error occurs after 80 seconds.

Each communication function timeout must be set to a value higher than 80 seconds if the first exchange was not successfully completed.

"Keep Alive"

Frame

The TCP layer sends a frame almost every 2 hours so that breaks in connection can be detected (i.e. cable disconnection, detection of power outage from the client by a server etc.).

The use of this mechanism is detailed in the chapter called Managing the TCP

connections for X-Way UNI-TE and Modbus, p. 76 in this part.

35011050 01 July 2006

63

Facilities

Address Management

At a Glance When implementing ETHERNET modules, you can manage the following addresses: z

MAC address, z z

IP address,

X-WAY address,

CAUTION

Address duplication

Two devices with the same address can generate unpredictable events on the network.

Failure to follow this precaution can result in injury or equipment damage.

MAC Address

IP Address

General case

This address is unique for each ETHERNET module. It is defined in the factory by the module manufacturer.

Exception

For the TSX ETY 110 module, this address is derived from the X-WAY address using the code selectors situated on the front panel of the module.

It is defined in the following way:

00.80.F4.00.<network number>.<station number>

Note: Given the risk of possible duplicate addresses, you must ensure that it conforms to the company’s addressing scheme.

General case

You define this address yourself when configuring the module. On the same local network, this address must be unique.

Exception

For the TSX ETY 110 module, this address can be derived from the MAC address.

For TSX ETY 410•, PORT and 510• modules, in the absence of PL7 confirmation, this address is derived by default from the MAC address.

64

35011050 01 July 2006

Facilities

X-WAY Address General case

All devices have an X-WAY address linked to the IP address by the module configuration. This address must be unique within the entire X-WAY architecture.

Exception

For the TSX ETY 110 module, the X-WAY address is defined using the code selectors on the module. These selectors code the network number and the station number.

35011050 01 July 2006

65

Facilities

IP Address

At a Glance

Address

Composition

Each device connected to the network should have a unique IP address .

When the type of network environment is open, the uniqueness of the address is guaranteed by the authorized organism in the country where the network is located by assigning it a network identifier.

If the type of environment is closed, the uniqueness of the address is managed by the company's network manager.

This address is made up of two identifiers, one of which identifies the network, the other identifies the connected machine.

An IP address is defined on 32 bits. It is made up from 4 decimal numbers, each coded on a bit (example: 140.186.90.3).

Depending on the network span, four address classes can be used: z

Class A applies to large span networks, which have a large number of connected z stations.

Class B applies to medium span networks, which have fewer connected stations.

z z

Class C applies to small span networks, which have few connected stations.

Class D is used for multicast.

66

35011050 01 July 2006

Structure

Facilities

Depending on the class, an address is structured in the following way:

Class A

0

7 bits

Network identifier

24 bits

Machine identifier

Class B

1 0

Class C

1 1 0

Class D

1 1 1 0

14 bits

Network identifier

21 bits

Network identifier

28 bits

Network/machine identifier

16 bits

Machine identifier

8 bits

Machine identifier

The following table displays the spaces reserved for the different IP address classes:

B

C

Class

A

D

Range

0 .0.0.0 to 127 .255.255.255

128 .0.0.0 to 191 .255.255.255

192 .0.0.0 to 223 .255.255.255

224 .0.0.0 to 239 .255.255.255

35011050 01 July 2006

67

Facilities

Sub addressing and subnetwork mask

Introduction

Sub addressing

In an open environment, after a network identifier has been obtained from the accredited body, the local system administrator is able to manage several subnets.

This will allow local networks to be installed without changing anything for the outside world which will still only be able to see the network indicated by the network identifier.

This sub addressing function is possible by splitting the machine identifier into the following: z a subnet identifier, z a machine identifier.

Example: sub addressing for a class B address (IP address in question:

140.186.90.3)

16 bits 8 bits 8 bits

Network identifier =

140.186

Subnetwork identifier = 90

Machine identifier = 3

68

35011050 01 July 2006

Mask

Facilities

The subnet mask is used to find out the number of bits allocated respectively to the network identifier and the subnet indicator (bits to 1), and then to the machine identifier (bits to 0).

The value of the subnet mask must be chosen to comply with the IP address class.

It will have the value (xxx: value chosen left up to the user): z z z for a class A address: 255.xxx.xxx.xxx, for a class B address: 255.255.xxx.xxx, for a class C address: 255.255.255.xxx.

Example: class C subnet mask (IP address in question :192.186.90.3)

16 bits

Network identifier =

192.186

8 bits

Subnetwork identifier = 90

8 bits

Machine identifier = 3

Subnetwork mask

(24 bits to 1)

= 255.255.255

Machine identifier

(8 bits to 0)

Note: This division allows 254 possible subnets with 254 machines per subnet.

35011050 01 July 2006

69

Facilities

UNI-TE communication

Introduction

Synchronous exchanges

Asynchronous exchanges

Two data exchange services are offered according to the server type

(Communication applications Volume 1 - Server Function) used : z z either data exchanges sychronized on the MAST task, or data exchanges performed by the end task in the following modes : z z asynchronous server, asynchronous client.

In server mode

All UNI-TE requests from the PLC are supported by the ETHERNET module.

In client mode

This type of exchange allows the following UNI-TE requests to be sent out: z z

READ_VAR

,

WRITE_VAR

, z z z

SEND_REQ

,

DATA_EXCH

,

...

z z z z z z z

In server mode

This facility allows messages to be exchanged using the following requests:

READ_OBJECT

WRITE_OBJECT

READ_GENERIC_OBJECT

WRITE_GENERIC_OBJECT

MIRROR

READ_OBJECT_LIST

WRITE_OBJECT_LIST

The consistency of the data read or written can be guaranteed (guarantee that the request is sent in one cycle) by setting the system bit %S91 to 1.

In this configuration a jitter phenomenon of 1.5 ms can appear on the MAST task.

In client mode

This facility allows messages to be exchanged using the following requests: z READ_Asyn

: allows up to 507 (%MW) words or 8112 (%M) bits to be read by the asynchronous messaging (Communication applications Volume 1 - Server z

Function) channel.

WRITE_Asyn

: allows up to 510 (%MW) words or 8160 (%M) bits to be written by the asynchronous messaging channel.

70

35011050 01 July 2006

Facilities

Modbus communication on the TCP/IP profile

Introduction This service is used for Modbus protocol communication between a

Premium TSX PLC and a Quantum TSX PLC or a different Premium TSX PLC and control routine software on a PC or other devices conforming to the Modbus protocol.

Client scheduler

Modbus

Protocol

TCP/IP ETHERNET

Quantum

Server

Modbus

Protocol

Premium 1

Client/Server

Modbus

Protocol

Premium 2

Client/Server

The same module can communicate with a remote device in client mode (for example a Quantum PLC) and other remote devices in server mode (for example a control routine PC).

The Premium 1 PLC is the client to the Quantum PLC. It opens the TCP-IP connection and sends Modbus messages to the Quantum.

The Premium 2 PLC is the server to the scheduler. The scheduler has opened a

TCP/IP connection and is sending Modbus messages to the TSX Premium 2.

35011050 01 July 2006

71

Facilities

Precautions for use

The profile pair UNI-TE and Modbus is not supported on the same Premium remote station.

Special case for the TSX ETY 110 module

The Client/Server modes are exclusive to a given remote device to improve communication performance. PLC applications and the network architectures will have to be designed so that switching from one mode to another between the same two devices is done as little as possible.

Furthermore, frequent switching could lead to messages being lost: z

If the Premium PLC communicates in server mode with a Quantum PLC after opening the TCP/IP connection, sending a message through the PL7 client z application will cause the TCP/IP server connection to close after any server transactions that are in progress have been processed.

If after opening the TCP/IP connection the Premium PLC communicates in client mode with a Quantum PLC, a request to open the connection coming from the

Quantum will cause the TCP/IP connection to close with the possible loss of any client transactions in progress.

72

35011050 01 July 2006

Facilities

Architecture supported by a Modbus communication on the TCP/IP profile.

Introduction The following diagram illustrates the architecture supported.

Programming terminal

Scheduler

Modbus

Communication UNI-TE Communication

Ethernet

Quantum

Bridge

Ethernet

Modbus series

Modbus Modbus

Modbus

Premium Premium

Slave 1

Modbus Plus

Fipway

Modbus Slave n

Accessibility The Modbus protocol guarantees interoperability between the Premium station and the Quantum station on a TCP/IP Ethernet network.

On the other hand access from a Premium PLC to a Modbus Plus network connected to the Quantum PLC is not possible via TCP/IP.

In the same way the Modbus protocol cannot cross X-Way Premium bridges.

Communication between a Premium PLC on the Ethernet network with a remote device connected to a Modbus series bus is possible if you use a series linked

Ethernet/Modbus gateway (type 174 CEV 300 10).

Special case for the TSX ETY 110 module

For a TSX ETY 110 module, communication between a Premium PLC on the

Ethernet network with a device connected to the Modbus series bus is not possible.

35011050 01 July 2006

73

Facilities

Modbus messaging on the TCP/IP profile

At a Glance

Installation principle

Sending communication functions

Data exchange

The communication functions are the same as those described in the communication functions on Modbus.

Although a remote Modbus station does not have an X-Way format address, each communication function will use an X-Way format address to designate a remote IP station.

For each remote Modbus station, you must configure the pair in the correspondence table (IP address, {network.station} X-WAY) where: z network: network number of the local X-Way station, z station: 100 to 164 = logical number of the X-Way station.

Example: the X-Way address {2.108} is associated with the IP address

139.160.2.8.

This address will only be used by the local Premium module. It is not sent over the network.

In the case of a remote TSX Premium station configured with the Modbus protocol, it is advisable to give an X-Way station address that is the same as the number of the local station, incremented by 100.

When communication functions are sent by the application to a remote device connected to a Modbus bus via a serial link Ethernet/Modbus gateway, the function address must be as follows:

ADR#{network number, station number}0.0.Modbus address of destination

The network number and station number correspond to the X-Way address of the

Ethernet/Modbus 174 CEV••• gateway. The Modbus destination address corresponds to the Modbus slave address.

Example: a

READ_VAR

function is sent to slave 10 on the Modbus serial bus. The gateway IP address is 139.160.2.8 and the X-Way address {2.108}.

READ_VAR(ADR#{2.108}0.0.10, ...)

The following requests are addressed to the device with which you wish to perform variable read or write operations.

Modbus requests

Read bits

Function code

16#01

Communication function

READ_VAR

74

35011050 01 July 2006

Modbus requests

Read words

Write a bit or n bits

Write a word or n words

Read input bits

Read input words

Function code

16#03

16#05 or 16#0F

16#10

16#02

16#04

Facilities

Communication function

READ_VAR

WRITE_VAR

WRITE_VAR

SEND_REQ

SEND_REQ

Correspondence of object types

This table describes object type correspondence between a Premium PLC and a

Momentum or Quantum PLC.

Premium objects

%MW: internal words

%M: internal bits

%IW: input words

%I: input bits

Quantum or Momentum objects

4x... memory area

0x... memory area

3x... memory area

1x... memory area

35011050 01 July 2006

75

Facilities

Managing the TCP connections for X-Way UNI-TE and Modbus

Introduction The connection can be opened either by the local PLC or by a remote station which wants to communicate with the local PLC.

A connection is characterized by the pair:

(local TCP port, local IP address; remote TCP port, remote IP address)

Note: Managing the connections is transparent for the user.

76

35011050 01 July 2006

Facilities

Opening a connection

Introduction

With a remote device

A connection can be opened: z either by a request from a remote device, z or by a request from the local PLC.

The module prepares for a connection coming from a remote device.

When the connection is received, verification of the IP address of the remote machine is done if and only if access check is activated. This test consists of checking that this address is on a list of remote machines authorized to connect.

If the test is positive the connection is opened. If not the connection remains closed.

With a local PLC When a message is sent out by a communication function, if there is no connection with the remote device, this is opened automatically internally by the module to the remote 502 port.

35011050 01 July 2006

77

Facilities

Examples Example of connections

Premium

{1,1}

192.168.1.1

Ethernet: TCP/IP

Premium

{1,2}

192.168.1.2

Premium: Bridge

{1,3}

192.168.2.4

{1,4}

192.168.1.4

PC

Fipway

In the example opposite, four TCP connections are open for communication between the terminal and the PLC stations or between two PLC stations.

The terminal is always able to open connections.

Either of two PLCs CANopen the connection between them (the client PLC).

78

35011050 01 July 2006

Facilities

Closing a connection

Introduction Connections can be closed in two different ways: z by the remote station which decides to end communication and sends a TCP/IP z connection closure, by the local PLC when the maximum number of open connections has been reached (the connection that has been open the longest is then closed).

Closure of a connection is indicated to the PLC application by an error report

(message refused) on any exchanges in progress.

35011050 01 July 2006

79

Facilities

What happens when a connection is broken

Introduction

Reconnecting the cable

Server remote device

A break in connection can be of two types: z disconnection of the network cable (cable disconnected or cut…..) z disappearance of the remote device (break down, power cut…).

Loss of connection is detected after 2 hours by the Keep Alive request.

If within this time the connection is re-established, re-starting communications is different according to the type of break.

In this case the break in connection is caused by a network cable but the two stations remain operational.

When the cable is reconnected communication between the ETY module and the remote device will start again on the TCP/IP connection that was opened previously.

The remote device that disappeared was the server.

Client 1

Remote device

2

Server

3

1 The client ETY module is still sending out data on the old connection (which remains half open).

2 The server receiving the information without associated connection sends out a Reset command and closes the old connection.

3 The client ETY module opens a new connection.

80

35011050 01 July 2006

Client remote device

Facilities

The remote device that disappeared was the client.

Remote device

Server

1

Client

2

3

1 The client opens a new connection.

2 The server ETY module receives the request to open a new connection.

3 The server ETY module closes the old connection (if there is nothing in progress) and authorizes the new one.

35011050 01 July 2006

81

Facilities

6.2

IO Scanning Facility

Introduction

Aim of this

Section

What's in this

Section?

This sub-chapter presents the functions and characteristics of the IO Scanning facility.

This section contains the following topics:

Topic

IO Scanning Service

Read and write zones

Scanning Period

Page

83

86

88

82

35011050 01 July 2006

Facilities

IO Scanning Service

At a Glance

Recommendations for use

The input/output scanner is used, periodically, to read or write remote inputs/outputs on the ETHERNET network without specific programming.

This service comprises the following essential elements: z z a read zone which groups together all the remote inputs values, a write zone which groups together all the remote outputs values, z scanning periods which are independent of the PLC cycle and are dedicated to each remote device.

Scanning is only performed when the PLC is in Run mode.

This service operates with all devices supporting Modbus communication on the

TCP/IP profile in server mode.

The exchange mechanism, which is transparent to the user, is carried out with the following requests: z z z read requests, or write requests, or read and write requests.

Note: Certain types of scanned devices, such as TSX ETY modules (See Modbus

messaging on the TCP/IP profile, p. 74

), only support read requests or write requests (simultaneous read/write requests are not supported).

35011050 01 July 2006

83

Facilities

Operation The following diagram shows how the scanning of remote inputs/outputs works.

Application memory (%MW)

Read zone Write zone

2

1

3

Device input words Device output words

1.

As soon as the PLC switches to Run mode, the module opens up one connection per scanned device.

2.

Then the module periodically reads inputs words, and periodically writes output words for each device.

3.

If the PLC switches to Stop mode, the connections to each device are closed.

84

35011050 01 July 2006

Summary of functionality

Facilities

The IO scanning service functionality is: z to manage the connection with each remote device (one connection per device z scanned), to scan the inputs/outputs of the device using Modbus read/write requests on the

TCP/IP profile, z z to update the read and write zones in the application memory, to refresh the status bits for each remote device.

Note: These bits show whether the module's input/output words have been refreshed.

35011050 01 July 2006

85

Facilities

Read and write zones

At a Glance These two zones in the application memory, managed by the Ethernet module, are tables of internal words (%MW), which contiguously group all input and output word values for connected remote devices.

Remote input and output type of devices are supplied with: z input words used to send back the values of the inputs to the module, z output words used to assign the value of the outputs to the remote device.

Note: Refer to the documentation for each device for the number and details of input and output words to be managed.

86

35011050 01 July 2006

Example

Facilities

The Ethernet module scans three devices: z a Momentum at the address IP1 (type 170 AA1 140 00: 16 analogue inputs): this z module has 16 input words and 4 output words.

a Momentum at the address IP2 (type 170 AA1 340 00: 16 discrete inputs): this module has one input word.

z a Premium PLC at the address IP3 with the zone %MW1000 to %MW1125 reserved as input words.

The read zone begins at %MW100 and the write zone at %MW400.

Read zone

Application memory

Write zone

16 input words for device at IP 1 address

%MW100 to

%MW115

%MW400 to

%MW403

4 output words for device at IP 1 address

1 input word for device at IP 2 address

125 input words for device at IP 3 address

%MW116

%MW117 to

%MW241

Note: The fields dedicated to remote devices must not have any overlap. Equally, the read and write zones must not have any overlap.

Note: scanned devices (read or write) must be located on the same network as the scanner device. Crossing a bridge is not allowed.

Note: a Momentum 170 can be read-scanned by several modules, but only one module is allowed to write-scan it.

35011050 01 July 2006

87

Facilities

Scanning Period

At a Glance Remote input/outputs are scanned periodically depending on the application requirements.

A scanning period is defined for each device through configuration, according to the update speed: z z z fast, normal, slow.

Note: The lower the scanning period, the faster the input/outputs are updated.

However, this speed increases the network load.

Note: %SW8 and %SW9 do not stop remote station scanning, but inhibit the copying of I/Os to and from the application variables.

88

35011050 01 July 2006

Facilities

6.3

BOOTP/DHCP Address Server Utility

At a Glance

Aim of this

Section

What's in this

Section?

This Section introduces the functions and characteristics for the BOOTP/DHCP address server utility.

This section contains the following topics:

Topic

BOOTP and DHCP Utilities

BOOTP Client

BOOTP and DHCP Servers

Page

90

91

93

35011050 01 July 2006

89

Facilities

BOOTP and DHCP Utilities

At a Glance

BOOTP Utility

DHCP Utility

BOOTP (Bootstrap Protocol) and DHCP (Dynamic Host Configuration Protocol) are the start up protocols for terminals or stations without disks via centralized management of network parameters.

They are mainly used to supply an IP address to a station, which starts on the network.

The TSX ETY 410•/PORT/510• module can be configured either as a BOOTP or

DHCP server, or as a BOOTP client.

This comprises the following essential elements: z client stations, which only have their own MAC address as information, and which z need to be automatically configured in order to start up, a server, which has a table (BOOPTAB) containing the IP address configuration for each client station.

It has the same following elements: z client stations, which only have their own MAC address or their Name (Role

Name) as information, and which need to be automatically configured in order to start up, z a server, which has a table (BOOPTAB) containing the IP address configuration,

Name, the Netmask and the Gateway for each client station.

90

35011050 01 July 2006

Facilities

BOOTP Client

At a Glance In this context, the module, configured as a BOOTP client, transmits requests on the network every second while it is starting up until it obtains a reply.

The remote device acting as the BOOTP server responds to this request and assigns to the client module: z an IP address, z z the gateway IP address, the corresponding subnetwork mask.

Note: the display of this information from within a browser connected to the rack display (See

HTTP Server Rack Display Page, p. 117 ) HTML pages on the web is

sometimes inaccurate. Therefore you must connect to a PL7 software application on the PLC concerned in order to obtain the real values.

Note: If the BOOTP server is missing or if there is no reply, the client module does not start.

35011050 01 July 2006

91

Facilities

Example The following diagram shows the routing of requests during start-up of a station on the network:

Remote station

BOOTP server containing the following table:

MAC1 Address IP1 Address

MAC2 Address IP2 Address

MAC3 Address IP3 Address

... ...

ETHERNET

Bridge

BOOTP relay

ETHERNET

BOOTP request:

MAC1 Address

BOOTP 2 Client BOOTP 1 Client

92

35011050 01 July 2006

Facilities

BOOTP and DHCP Servers

At a Glance In this context, the module is used as a server for starting-up client stations.

In listen mode, the server responds to the clients’ requests and sends them their

IP address configuration.

To do this, the server device has a table, which groups: z

In the case of a BOOTP server: z z correspondence between the MAC addresses and the IP addresses.

In the case of a DHCP server: z correspondence between the MAC addresses or the Names (Role Names) of the client stations and the IP addresses, z z the Netmask and the Gateway,

The names and access paths to the parameter files (see Replacing Faulty

Remote Stations, p. 101 ).

Note: The BOOTP server (present on TSX ETY modules) only provides the network configuration data for the client stations connected to the local network.

Precautions for

Use

When a module is used as a server for starting scanned stations (See IO Scanning

Facility, p. 82 ), you must avoid configuring the PLC in

automatic start in RUN mode . If you do not, there is a risk that stations such as the Momentum 170s will not be able to obtain their IP address when the BOOTP server restarts.

35011050 01 July 2006

93

Facilities

Example using a

BOOTP/DHCP

Server

The following diagram shows the routing of requests when responding to a start-up request from the server:

DHCP 2 Client

BOOTP 1 Client

ETHERNET

DHCP response

DHCP request

Response to BOOTP request:

IP1 Address

Subnetwork mask

Gateway address

DHCP server containing the following table:

MAC1 Address IP1 Address

Role Name2 IP2 Address

MAC3 Address IP3 Address

... ...

Note: The subnetwork mask and the address of the gateway belong to the BOOTP server.

The BOOTP server can broadcast a reply. The focus is on updating the switches.

94

35011050 01 July 2006

Facilities

6.4

SNMP Facility

SNMP Communication on UDP/IP

At a Glance The SNMP (Simple Network Management Protocol) standard defines network management solutions in terms of protocol and the exchange of supervised data.

The SNMP structure relies on the following essential elements: z

The Manager allows entire or partial network supervision, z z

One or more Agents . Each supervised device has a software module named

Agent used by the SNMP protocol.

A MIB (Management Information Base) is a data base or collection of objects.

The SNMP module agent is implemented on the TSX ETY modules. This allows a

Manager to access MIB-II standardized objects from the agent TSX ETY via the

SNMP protocol. The MIB-II allows management of TCP/IP communication layers.

On the TSX ETY 410•/PORT/510• module, it is possible to also access objects from the MIB Ethernet Transparent Factory, which provide specific information on Global

Data, I/O Scanning and Messaging utilities.

Branching view of the MIB Ethernet Transparent Factory: experimental private enterprises schneidergroup transparentFactoryEthernet switch port502Messaging ioScanning globalData web addressServer deviceProfile

The source file of the private MIB Ethernet Transparent Factory is available on the

TSX ETY 410•/PORT/510• module. It can be downloaded from an internet navigator by clicking on the "Download MIB file" link on the HTTP server index page (See

Ethernet Module Diagnostic Pages, p. 121 ). This file may be compiled by the main

SNMP Managers on the market.

35011050 01 July 2006

95

Facilities

The SNMP

Protocol

The SNMP protocol defines 5 types of message between the agent and the manager. These messages are encapsulated in the UDP datagrams.

Messages from the manager to an agent: z z

Get_Request

: message used to obtain the value of one or more variables.

Get_Next_Request

: obtains the value of the next variables.

z Set_Request

: sets the value of a variable.

Messages from an agent to the manager: z Get_Response

: allows the agent to re-send the value of the requested variable.

z Trap

: allows asynchronous event signaling by the agent.

96

35011050 01 July 2006

Description of the Utilities

Facilities

The SNMP manager transmits read or write requests (

Set_Request

,

Get_Request

,

Get_Next_Request

, etc.) for objects defined in the

MIB - II SNMP, and the SNMP agent of the TSX ETY module responds.

SNMP Manager

Get_Response

Trap

Set_Request

Get_Request

Get_Next_Request

SNMP Agent

TSX ETY PLC Station

The module's SNMP agent transmits events (Traps) to the Manager. The managed

Traps systems are as follows: z Coldstart Trap

: z z

For the TSX ETY 110 module, the event is transmitted following a module supply Reset.

For TSX ETY 410•/PORT/510• modules, the event is transmitted following a module supply Reset, or following a processor Reset, or following the z downloading of an application to the PLC.

Authentication Failure Trap

: event transmitted following an authentication problem. The Community Name field in the received message is different to the one configured on the module. This trap can be checked when configuring the TSX ETY module.

35011050 01 July 2006

97

Facilities

6.5

Global Data Utility

Global Data Utility

At a Glance The aim of the Global Data utility, which is supported by the

TSX ETY 410•/PORT/510• modules, is to provide an automatic data exchange for

PLC application co-ordination.

98

35011050 01 July 2006

Operation

Facilities

The communication modules are grouped together in a Distribution Group to exchange the variables used for PLC co-ordination.

Each communication module publishes a local application variable for the other communication modules in the Distribution Group.

Each communication module can also subscribe to the application variables published by all other modules belonging to the Distribution Group, whatever its location.

An Application Variable is a group of contiguous words from a PLC (%MW).

The Global Data utility should be configured (See Configuring the Global Data Utility,

p. 252 ) to determine the location and the number of application variables published

and subscribed by each communication module. Once the module is configured, exchanges between the communication modules sharing the same Distribution

Group are automatically carried out when the PLC is in RUN mode.

Illustration:

Distribution Group

Multicast IP: 255 255 255 251

Data distribution

Intranet control

35011050 01 July 2006

2...n stations

Data distribution

Distribution Group

Multicast IP: 255 255 255 250

A Distribution Group is a group of communication modules identified by the same multicast IP address. Exchanges in "multicasting" are used to distribute Global Data.

Several independent Distribution Groups can co-exist on the same subnetwork with their own multicast address.

A Publication/Subscription protocol on UDP/IP is used for data distribution.

The publication of a variable is synchronized at the start of the PLC cycle.

Subscribed variables are copied to the PLC application memory at the end of the cycle.

99

Facilities

Health Bits

Multicast

Filtering

Operating Mode

Limits

The PLC memory zones, which receive the various subscribed variables, should not be recovered

A Health bit (Status bit) is associated with each application variable.

This status bit indicates the validity of each subscribed variable: it is at 1 if the variable has been published and received in the configured validity time limit (See

Configuring Global Data, p. 254 ), otherwise it is at 0.

The Global Data utility uses Multicasting .

As a result of this broadcasting approach, the multicast frames transmitted by a module are repeated on all switch ports, which creates network congestion.

When the switches possess this function, Multicast Filtering allows multicast frame spreading to be limited to only the ports that require it.

The protocol used to establish the list of ports involved in data traffic is GMRP .

The operating modes are as follows: z

Stopping the PLC stops Global Data exchanges.

z

The use of the I/O forcing system bits (%S9, %SW8, %SW9) does not stop

Global Data exchanges.

There are no theoretical limits for the number of stations sharing a Distribution

Group. The main limitation is the number of variables exchanged in the Distribution

Group (64 variables).

100

35011050 01 July 2006

Facilities

6.6

Managing Faulty Devices

Replacing Faulty Remote Stations

At a Glance

Objective

Operation

The objective of this utility is to provide automatic recovery of remote I/O module parameters or intelligent modules connected to a Transparent Factory Ethernet subsegment. This applies when exchanging a faulty module with a functioning module.

The objective of this utility is: z z to supply an IP address to a remote station based on the Name given to this station ( Role Name ) to give a remote station the capacity to store parameters and also to recover them, if required.

This utility requires the use of the DHCP address server (See BOOTP/DHCP

Address Server Utility, p. 89 ) and the FTP/TFTP server of the

TSX ETY 410•/PORT/510• modules.

It can manage up to 96 remote stations.

Utility operating principle:

Initially:

1.

The valid remote station obtains an IP address from the name that has been given to it (Role Name).

2.

The valid station gives its configuration parameters to the server.

Secondly:

This station breaks down. It is replaced with a non-configured device of the same type, which has the same name as the station it replaces:

1.

It then transmits a DHCP request to the server.

2.

It receives its configuration file, which was saved first on the server.

3.

The remote station restarts automatically.

Note: The Role Name is limited to 16 characters in ASCII.

35011050 01 July 2006

101

Facilities

6.7

Time Synchronization Service

Time Synchronization Service

General The time service synchronizes computer clocks over the Internet. For example, the time of one client is synchronized either with another server or to a referenced time source like a radio or satellite receiver.

Typical time service configurations utilize multiple redundant servers and diverse network paths to achieve high accuracy and reliability. Time service accuracy can be within a millisecond on LANs and up to a few tens of milliseconds on WANs.

Use the time service for z z z event recording—sequence events event synchronization—trigger simultaneous events alarm and I/O synchronization—time stamp alarms

Time Synchronization and Time

Stamps

On an Ethernet network, all controllers should be synchronized with the same clock time, which is provided by an NTP server. In each application program, events or application data (IO values for example) can be time stamped using the application stacks.

The Premium Ethernet interface module, an ETY 5103, connects to an NTP time server and provides the source-time synchronization signal, which is sent to the

CPU.

To read the clock, a function block is used in the controller’s project (application program).

CPS CPU ETY NTP

Server

Clock

System

Counter

NTP

Client

NTP Request

NTP Response

Ethernet

Network

Modicon Quantum System R_NTPC

EN EN0

OUT1

OUT2

STATUS

102

35011050 01 July 2006

Facilities

6.8

HTTP on-board server

Introduction

Subject of this sub-chapter

What's in this

Section?

This sub-chapter mentions the functions and characteristics of the on-board server.

This section contains the following topics:

Topic

Embedded HTTP Server

HTTP Server Home Page

HTTP Server Index Page

HTTP Server Security Page

Address Server Page for the HTTP Server

HTTP Server Rack Display Page

HTTP Server Data Editor Page

Ethernet Module Diagnostic Pages

NTP Diagnostics Page

HTTP Server User Pages

Page

104

106

109

111

114

117

119

121

127

129

35011050 01 July 2006

103

Facilities

Embedded HTTP Server

At a Glance Some modules include an embedded Web server, which allows: z access to PLC data, z diagnostics to be carried out on the entire configuration.

All the processor or module data is presented as standard Web pages in HTML format. It can therefore be accessed by any market Internet browser that can run embedded JAVA code.

Function

Server

Predefined pages

Client pages

Client site size

Minimum FactoryCast version

-

-

-

-

-

None of the functions supplied by the Web site require any prior configuration or programming within the module.

The summary table below shows the various selections possible.

According to the type of module, the ergonomics of these functions can change:

TSX ETY 110 TSX ETY 110 WS TSX ETY 410•

TSX ETY PORT

X X

-

X

1.2 Mb

V 2.0

-

-

-

X

TSX ETY 510• TSX ETY 210

X

X

X

6.5 Mb

V 2.2.2

-

-

-

-

-

-

Legend

X Available

Not available

Embedded

Server Functions

The functions available on an embedded server are generally as follows: z statistics: this page shows the ETHERNET network statistics, z security: this page is used to modify the user name and the password to access the site, z z z z address server: if the module is used as an address server, this page enables you to display and modify the server table, displaying the rack: this page enables you to display the configuration of the PLC which is controlling the module, data editor: this page allows you to display PLC data.

diagnostics functions: these pages allow network diagnostics.

104

35011050 01 July 2006

Facilities

Connections to a

TSX ETY Module

The module Web-site shows static and dynamic pages (PLC data). To refresh dynamic pages, an X-WAY connection is automatically created between the Web browser and the module.

Note: The browser connection X-WAY address is automatically derived from the module’s address by taking the same network number and a station number between 54 and 63. It is therefore essential to leave at least one X-WAY address free in this range of values.

The number of connections is regulated: z it is not possible to connect several browsers on a given PC to the same TSX ETY module, z z up to 10 PCs connected simultaneously to one module, on a TSX ETY 410•/PORT/510•, it is possible to connect a browser and another application (for example: an XIP driver).

35011050 01 July 2006

105

Facilities

HTTP Server Home Page

At a Glance

How to Access the Home Page

This page is the Web site home page. It allows you to select: z the site language: by default the page is displayed in English, z to access the site utilities page.

The following procedure shows you how to access the web site home page.

Step

1

2

Action

Open your usual browser.

Enter the IP address of the ETHERNET module in the line provided.

106

35011050 01 July 2006

Illustration

Facilities

The home page of a TSX ETY 410• or TSX ETY PORT looks like this, for example. e Welcome to the Premium Web Server – Microsoft Internet Explorer

File Edit View Go to Favorites ?

Back

Address e

Forward

X

Stop Refresh Home http://139.160.234.18/index_french.htm

Search Favorites History Channels e

Full scr.

Links

Schneider

S Electric

Fast Ethernet: Administration using the Web

for Premium

Diagnostics and Configuration

Operating System: Windows 98

Screen Resolution: 1024 x 768

Browser: Microsoft Internet Explorer 4 e

English German Italian Spanish

Copyright © 2000, Schneider Automation SA. All rights reserved.

e Internet zone z z

Note: the TSX ETY 510• home page has several differences:

The heading is: FactoryCast Web Server .

Two hypertext links accessing client pages are offered: z Protected user pages z Unprotected user pages

See the FactoryCast documentation for information on creating pages.

35011050 01 July 2006

107

Facilities

Language

Management

The site is multilingual. The language is selected by clicking on the link in the home page and it remains the language for subsequent connections.

Note: Some displays are in the language of the Windows installation (e.g. address bar, etc.)

108

35011050 01 July 2006

Facilities

HTTP Server Index Page

At a Glance

How to Access the Page

This page displays the various utilities supported by the ETHERNET module and the link to access the required utility.

The following procedure shows how to access the index page from the home page.

Step

1

Action

Click on the Diagnostics and Configuration link on the home page.

2

3

Result : a window requesting the user name and password appears.

Enter the user name and password using the correct case (i.e. upper or lower case).

Note : the default values of the fields are: z for the user name: USER z for the password: USER

Confirm with OK .

35011050 01 July 2006

109

Facilities

Illustration The index page of a TSX ETY 410• or TSX ETY PORT looks like this, for example. e Welcome to the Premium Web Server – Microsoft Internet Explorer

File Edit View Go to Favorites ?

Back

Address

Forward e

X

Stop Refresh Home Search http://139.160.234.18/secure/system/index_french.htm

Favorites History Channels

Links e

Schneider

S Electric

Fast Ethernet: Administration using the Web

for Premium

Home

Security

Address Server

Rack Viewer

Data Editor

Ethernet Module e

Copyright © 2000, Schneider Automation SA. All rights reserved.

Open page http://139.160.2

e

Internet zone

110

35011050 01 July 2006

Facilities

HTTP Server Security Page

At a Glance

How to Access the Page

This page can be used to modify: z the user name and the password for accessing the index page, z the password for writing variables in the data editor

The user name and passwords are a maximum of 15 characters in non-extended

ASCII.

The following procedure shows how to access the security page from the index page.

Step

1

Action

Click on the Security link.

35011050 01 July 2006

111

Facilities

Illustration The security page of a TSX ETY4102 or a TSX ETY PORT looks like this, for example.

Access Rights

User:

New Password:

Confirmation of Password:

Change Password

Data Editor Write Password:

User:

New Password:

Confirmation of New Password:

Change Write Password

How to Modify

HTTP Access

Rights

Home Statistics Bootp Server Rack Viewer Data Editor

Copyright © 2000, Schneider Automation SA. All rights reserved.

The procedure is as follows:

Step

1

2

3

4

Action

Enter the new User name.

Enter the new password.

Confirm the new password.

Confirm the modification using the Change password button.

5

Result: an Ethernet Configuration page appears.

Click on the Reboot Device button to recognize the modification in the module.

112

35011050 01 July 2006

How to modify the Write password

Facilities

The procedure is as follows:

Step

1

Action

Enter the current password using the right case (i.e. upper or lower case).

2

3

4

Note: the default value of this field is: USER.

Enter the new password.

Confirm the new password.

Confirm the modification with the Change password button.

Result: an Ethernet Configuration page appears to indicate that the password has been modified.

35011050 01 July 2006

113

Facilities

Address Server Page for the HTTP Server

At a Glance This page is used to display or modify the correspondence table between the MAC addresses or the Name (Role Name) and the IP addresses of the module if the latter is configured as a BOOTP server. See

BOOTP/DHCP Address Server Utility, p. 89

.

This function is useful when replacing a failed remote device (e.g. replacing a faulty

Momentum module).

Note: This page does not allow the addition of new inputs, nor the modification of the Name (Role name) for a remote device.

How to Access the Page

The following procedure shows how to access the Address server page from the index page.

Step

1

Action

Click on the Address server link.

114

35011050 01 July 2006

Illustration

Facilities

The Address Server page of a TSX ETY4102 or a TSX ETY PORT looks like this, for example.

Entry

1

1

Name

ENTRY_1

Address Server Configuration

IP Address MAC Address Gateway

192.168.2.7

00005410033A 255.255.252.0

192.168.2.6

255.255.252.0

Netmask

192.168.2.1

192.168.2.1

Update the address server table

New IP Address:

New Netmask:

Entry modification

Entry to be changed: 1

New Ethernet Address:

New Gateway Address:

Change entry

Home | Statistics | Security | Bootp Server | Rack Viewer | Data Editor

FactoryCast ™ , Schneider Automation SA. All rights reserved.

35011050 01 July 2006

115

Facilities

How to Modify the Table

The procedure is as follows:

Step

1

2

3

4

5

6

Action

Enter the entry number to be modified in the field provided.

Enter the new IP address to be modified in the field provided.

Enter the new MAC address to be modified in the field marked: New Ethernet

Address .

Is the server locked in operation?

z If so: enter the password associated to the address server then go to step 5.

z If not: go to step 5.

Confirm the modification with the Change entry button.

Click on the Refresh Address server table button to display the modification on the screen.

Recognition of

Modifications

Configuration modifications are recognized either after a cold restart of the PLC, or on the next loading of the PLC application.

116

35011050 01 July 2006

Facilities

HTTP Server Rack Display Page

At a Glance This page allows you to carry out diagnostics on the modules in the local rack configuration that includes the ETHERNET module.

By clicking on a module in the configuration, you obtain a set of diagnostic information on this module: z

LED status display, z z the type and the version of the module as well as its position in the rack, information specific to the functions of the module.

Note: For further information, refer to the FactoryCast User Guide documentation.

How to Access the Page

The following procedure indicates how to access the rack display page from the index page.

Step

1

Action

Click on the Rack Display link.

35011050 01 July 2006

117

Facilities

Illustration The TSX ETY 410 rack display page looks like this, for example.

0

3

5

5

7

2

0

T

S

X

F i

1 2

1

0

E

T

Y

4

T

S

X

3 4

6

0

0

A

E

Y

1

T

S

X

5 6 7 8 9 10 11 12 13 14

Home Statistics Server Bootp Data editor Graphical Editor Alarm Indicator

Copyright © 2000, Schneider Automation SA. All rights reserved.

118

35011050 01 July 2006

Facilities

HTTP Server Data Editor Page

At a Glance This page is used to create animation tables containing lists of PLC variables to be displayed or modified.

Variables can only be accessed via addresses.

This function is useful when running diagnostics on an application.

Note: Write access is managed by password. For further information, refer to the

FactoryCast User Guide documentation.

How to Access the Page

The following procedure indicates how to access the data editor page from the index page.

Step

1

Action

Click on the Data Editor link.

35011050 01 July 2006

119

Facilities

Illustration The Data Editor page of a TSX ETY 410• or TSX ETY PORT looks like this, for example.

<new> Save Delete...

5

6

3

4

1

2

7

8

9

10

11

12

13

14

15

The name of the PLC program is STATION:0.0.

Variable Address Data type

Find… Insert...

Cut… Paste… Password

Value Format State

The list of variables is not available. Cannot find variables.

120

35011050 01 July 2006

Facilities

Ethernet Module Diagnostic Pages

Home Page This page contains a list of links for accessing the different diagnostic pages for the

Ethernet module: z z

Global Data Utility

I/O Scanning utility z z

Messaging utility

Bandwidth monitoring utility z

Ethernet module statistics

A link also allows the downloading of the private MIB source file.

View of the Diagnostics Utilities home page: e Welcome to the Premium Web Server – Microsoft Internet Explorer

File Edit View Go to Favorites ?

Back

Address e

Forward

X

Stop Refresh Home Search http://139.160.234.18/secure/system/index_french.htm

Favorites History Channels

Links e

Schneider

S Electric

Ethernet Module Diagnostic

Global Data

I/O Scanning

Messaging

Bandwidth

Statistics

Download MIB file e

Copyright © 2001, Schneider Automation SA. All rights reserved.

Open page http://139.160.2

e

Internet zone

Click on a link to access the desired diagnostics page.

35011050 01 July 2006

121

Facilities

Global Data Page Information on the general diagnostics of Global Data can be found above this page: z

State z z

Number of publications per second

Number of subscriptions per second

This page also shows a table that lists all published and subscribed variables in the same distribution group. Each variable is identified by its Identifier.

z z z z

Green for the subscribed variables

Yellow for the published variables

White for all unconfigured variables

Red for variables with communication faults

View of the Global Data diagnostics page: e Welcome to the Premium Web Server – Microsoft Internet Explorer

File Edit View Go to Favorites ?

Back

Address e

Forward

X

Stop Refresh Home Search http://139.160.234.18/secure/system/index_french.htm

Favorites

GLOBAL DATA DIAGNOSTIC

History Channels

Links e

Global Data Status: OK

Number of subscriptions per sec. : 300 | Number of publications per sec. : 100

Global Data Status

16

32

48

64

Not configured Sub Variable Pub Variable

Home | Ethernet Module

Fault e Open page http://139.160.2

e

Internet zone

1

17

33

49

122

35011050 01 July 2006

I/O Scanning

Page

Facilities

Information on the general diagnostics of the I/O Scanning utility can be found above this page: z z z

State

Number of transactions per second

Number of connections per second

This page also displays a summary of the status of all modules: z

Green for the scanned modules z z z

White for the unconfigured modules

Red for faulty modules

Black for the modules which are temporarily unscanned .

View of the I/O Scanning diagnostics page: e Welcome to the Premium Web Server – Microsoft Internet Explorer

File Edit View Go to Favorites ?

Back

Address e

Forward

X

Stop Refresh Home Search http://139.160.234.18/secure/system/index_french.htm

Favorites History Channels

Links e

I/O SCANNING DIAGNOSTICS

I/O Scanning Status: OK

Number of transactions per sec. : 1000 | Number of connections: 20

Scanned Stations Status

48

64

16

32

Not configured Scanned Unscanned

Home | Ethernet Module e Open page http://139.160.2

Fault e

Internet zone

33

49

1

17

35011050 01 July 2006

123

Facilities

Messaging Page This page provides current information on the open TCP connection on port 502.

The number of sent/received messages on the port can be found at the top of this page.

A table provides, for each connection (numbered from 1 to 64): z

The remote IP Address z

The remote TCP port z z z z

The local TCP port

The number of messages sent from this connection

The number of messages received from this connection

The error number on this connection

View of the messaging diagnostics page: e Welcome to the Premium Web Server – Microsoft Internet Explorer

File Edit View Go to Favorites ?

Back

Address e

Forward

X

Stop Refresh Home Search http://139.160.234.18/secure/system/index_french.htm

Favorites

MESSAGING DIAGNOSTICS

History Channels

Links e

Number of Messages sent: 150 | Number of Messages received: 50

1

2

3

4

Conn.# Remote addr.

Remote port Local Port

1920 502

Mess.

sent

20

Mess.

received

Err.

sent.

12 0 192.160.10.20

139.160.235.90

2020

192.160.10.21

502

502

3000

0

3

30

60

02

0

139.160.234.20

1050

5 139.160.234.18

5120

502

502

15

0

42

39

0

1 e Open page http://139.160.2

Home | Ethernet Module e

Internet zone

124

35011050 01 July 2006

Facilities

Bandwidth monitoring page

This page displays the load distribution of the TSX ETY 410•/PORT/510• module between the Global Data utilities, I/O Scanning, Messaging and other utilities.

View of the Bandwidth monitoring page: e Welcome to the Premium Web Server – Microsoft Internet Explorer

File Edit View Go to Favorites ?

Back

Address

Forward e

X

Stop Refresh Home Search http://139.160.234.18/secure/system/index_french.htm

Favorites History Channels

Links e

BANDWIDTH MONITORING

Global data: 30% | I/O Scanner: 20% | Messaging: 40% | Others: 10% e Open page http://139.160.2

Home | Ethernet Module e

Internet zone

35011050 01 July 2006

125

Facilities

At a Glance This page shows the ETHERNET network statistics. It is used to perform diagnostics on a disturbed network.

View of the TSX ETY4102 or the TSX ETY PORT statistics pages: e Premium Ethernet Module Statistics - Microsoft Internet Explorer

File Edit View Go to Favorites ?

Back

Address e

Forward

X

Stop Refresh Home Search http://139.160.234.18/secure/system/ethernet.htm

Favorites History Channels Full scr.

Mail Print

Links e

Status

Reference

Rack

Slot

Software version

0

2

10 Mb/s

TSX ETY 410

0.6

ETHERNET MODULE STATISTICS

Name

MAC Address

IP Address

Subnetwork mask

Gateway

139.160.234.18

00 80 f4 01 00 41

139.160.234.18

255.255.255.0

139.160.234.1

Send statistics

Sent

Re-Sent

Loss of data carrier

Late collisions

Buffer errors

Underflow

0

0

0

0

887

0

Receive statistics

Received

Frame errors

Overflow errors

CRC errors

Buffer errors

0

0

883999

0

0

Other faults

Missing packets

Collisions

Transmission timeouts 0

Memory errors 0

0

0

Resets 0

Zero Counters e Applet launched

Home Bootp Server Rack Viewer Data Editor Graphical Editor Alarm Indicator

Copyright © 2000, Schneider Automation SA. All rights reserved.

e

Internet zone

126

35011050 01 July 2006

Facilities

NTP Diagnostics Page

NTP Diagnostic

Dialog

Time synchronization service parameters:

Parameter

NTP status

NTP server status

NTP requests

NTP responses

Number of errors

Last error code

Date

Time

Time zone

DST

Description

Service is correctly configured (OK)

NTP client is connected to the NTP server, and if the server is

Primary or Standby

Total number of client requests sent to the NTP server

Total number of server responses sent from the NTP server

Total number of unanswered NTP requests

Last error code received from the NTP client

Date in d/m/y format

Time

Time zone plus or minus Universal Time, Coordinated (UTC)

Daylight saving time (DST) parameter is either

1.

on (enabled)

2.

off (disabled)

The dialog:

NTP Diagnostics

NTP Status:

NTP Server Status

OK

Link to the NTP Server: ###

Server: Primary

NTP Request Statistic

Number of Requests: 2

Number of Responses: 2

NTP Date and Time

Server Time Quality within

Date:

Time Zone:

05 Apr 2004 Time: 16:51:15

(GMT-05:00)Eastern Standard Time[New York]

Number of Errors:

Last Errors:

DST Status:

0

0

0

ON microsec/sec

35011050 01 July 2006

127

Facilities

Last Error Field Last Error field displays values, which indicate the type of error.

Type of Error

Component OK and running

Excessive network traffic or server overload

Bad parameters in the configuration

Component is disabled

Incorrect IP

Time zone file absent

Syntax error in the customrules file

Value

0

1

3

4

9

14

15

128

35011050 01 July 2006

Facilities

HTTP Server User Pages

At a Glance It is possible to create complete pages about certain modules. To do this, the

FactoryCast software and a guide for creating and publishing user pages are delivered with these modules.

Note: The TSX ETY5102 module is delivered with the FactoryCast V2.2.2 (or above) CD and the accompanying guide for creating and publishing user pages.

There are two types of pages: z z pages that are protected by passwords, and pages that are not protected by passwords.

How to Access

Protected User

Pages

The following procedure shows how to access the protected user pages from the home page.

Step

1

2

Action

Click on the Protected user pages link.

Result : the dialog box for entering the password appears.

Enter your user name and password, then confirm.

Result : the first branch page on the created site appears.

How to Access

Unprotected

User Pages

The following procedure shows how to access the unprotected user pages from the home page.

Step

1

Action

Click on the Unprotected user pages link.

Result : the first branch page on the created site appears.

35011050 01 July 2006

129

Facilities

6.9

Bandwidth Monitoring

Bandwidth Monitoring

At a Glance

Operation

Ethernet Transparent Factory offers two types of utilities: z

Real time utilities, which must have a performance guarantee and predictable behavior: z periodic utilities: I/O Scanner and Global Data, z z non-periodic utilities: Messaging on port 502 (UNI-TE, Modbus).

Non real time utilities: Web utilities and network management utilities

Once the I/O Scanner and Global Data utilities have been configured, it is possible to estimate the load percentage of the TSX ETY 410•/PORT/510• module for each of the utilities.

The Bandwidth Monitoring function carries out this estimation during configuration.

In online mode, it shows the actual distribution of the utilities (on the diagnostic module screen as well as on the Diagnostic Services° Web Page "Bandwidth

Monitoring."

In order to estimate this load, the PL7 software asks you to complete two pieces of information during configuration (See

Configuring the Bandwidth Utility, p. 262

): z z an estimation of the number of messaging transactions per second, the PLC cycle time.

With the help of this information the PL7 software is able to show how the

TSX ETY 410•/PORT/510• module will be used: z z z z display of the load percentage of the module to process the I/O Scanning configuration, display of the load percentage of the module to process the Global Data configuration, display of the load percentage of the module to process the messaging module, display of the load percentage of the module to process the remaining non real time utilities,

Note: During the configuration phase, these pieces of information are only estimates. The actual distribution is displayed in offline mode.

130

35011050 01 July 2006

Facilities

6.10

ETHWAY Facility

ETHWAY profile

Introduction

Common words

The ETHWAY profile offers the following data exchange facilities: z z data exchanges synchronized on the MAST task, or data exchanges in : z z z asynchronous server mode, asynchronous client mode.

or common data exchanges (common words).

In the following only common exchanges of data will be described. For the description of synchronous and asynchronous exchanges refer to

UNI-TE communication, p. 70 .

All the common words make up a database distributed amongst all or part of the devices on the same network.

Depending on the number of stations transmitting common words on the network, you can have at the most: z

4 common words per station for 64 active stations, z z z z

8 common words per station for 32 active stations,

16 common words per station for 16 active stations,

32 common words per station for 8 active stations,

64 common words per station for 4 active stations.

Note: The common words facility itself can take up a large part of the messaging bandwidth of the module if there are a number of stations connected and if the configured PLC cycle time is very short. In fact the common words are transmitted at each PLC cycle if there are changes in state and every 10 cycles if the value has not been modified.

You must therefore make sure that you do not exceed the module's maximum capacity.

Updating the (%NW) common words is done automatically. The application program consists simply of writing or reading these words.

Examples z

%NW{1.7}0:= %MW10 (writing a value for transmission) z

%MW50:=%N{1.8}2 (receiving a value)

35011050 01 July 2006

131

Facilities

132

35011050 01 July 2006

Configuration parameters

7

Introduction

Subject of this chapter

What's in this

Chapter?

This chapter introduces the configuration parameters for the different facilities used by the modules.

This chapter contains the following sections:

Section

7.1

7.2

7.3

7.4

7.5

7.6

7.7

Topic

Configuration parameters for TCP/IP facilities

Configuration parameters for the IO Scanning facility

Configuration Parameters for the Address Server Utility

Configuration parameters for the SNMP facility

Configuration Parameters of the Global Data Utility

Configuration Parameters of the Time Synchronization Service

ETHWAY profile configuration paramaters

Page

134

141

147

150

154

159

167

133

35011050 01 July 2006

Configuration parameters

7.1

Configuration parameters for TCP/IP facilities

Introduction

Subject of this sub-chapter

What's in this

Section?

This sub-chapter introduces the configuration parameters linked to the TCP/IP facility.

This section contains the following topics:

Topic

Configuration Parameters Linked to TCP/IP Utilities

Configuration Parameters for IP Addresses

Connection configuration parameters

Ethernet configuration parameters

Page

135

136

138

140

134

35011050 01 July 2006

Configuration parameters

Configuration Parameters Linked to TCP/IP Utilities

At a Glance The TSX ETY modules are comprised of configuration parameters linked to TCP/IP utilities.

Depending on the TSX ETY module selected, some configuration parameters cannot be accessed on the configuration screen. They are either not shown on the screen or are grayed out.

Availability of

Parameters

Parameters

X-WAY Address

IP Address

Connections

ETHERNET

The following table shows, for each ETHERNET module, the parameters that can be accessed from the configuration screen and the values that they can have.

TSX ETY 110

Default IP address

Configured IP Address

Subnetwork mask

Gateway address

Client/Server configuration

Connections which can be opened

Access control

Correspondence table X-WAY Address

IP Address

Protocol

Direct

Mode

ETHERNET II

802.3

X

X

X

X

By code selectors

X

-

X from 1 to 32

X

-

X

X

UNI-TE or Modbus

X

X

X

X

X

X

X

TSX ETY 410•/

PORT/510•

By PL7

X

X

X

-

X

UNI-TE or Modbus

X

Mono- or Multiconnections

-

Legends:

X Accessible

Not accessible

35011050 01 July 2006

135

Configuration parameters

Configuration Parameters for IP Addresses

At a Glance

By Default

This zone allows the IP address of a module to be defined in three distinct ways: z z z either using a default configuration, by manual configuration, or by using a configuration supplied by a BOOTP/DHCP server device.

Selecting the IP Address by default field allows the module's IP address to be calculated from the code selectors. See Common functions on the ETHWAY and

TCP/IP profile, p. 177 .

In this instance, you must code the network and station numbers on the code selectors located on the front of the module.

With this coding, the IP address is automatically derived by the system and the

IP Address , Subnetwork mask and Gateway Address fields are not significant and are grayed out.

Note: The default parameters should not be selected when the module is connected to a closed or private network.

Configured Selecting the Configured field allows manual configuration according to your own requirements: z module IP address, z z the subnetwork mask, which defines the part allocated to the subnetwork identifier in the IP address, the IP address of the default gateway, to which messages for other networks are transmitted.

Note: If the module is connected to an existing TCP/IP network, the IP addresses are administered globally, therefore the IP parameters must be configured.

Otherwise there is a risk of disturbance on the existing network caused by possible double allocation of the IP addresses.

136

35011050 01 July 2006

Client/Server

Configuration

Configuration parameters

Selecting the Client/Server configuration field allows the module's IP address to be configured from a remote device acting as a BOOTP server. See BOOTP and

DHCP Utilities, p. 90

.

In this instance, the IP address , Subnetwork mask and Gateway Address fields are not significant and are grayed out.

35011050 01 July 2006

137

Configuration parameters

Connection configuration parameters

Introduction

Connections which can be opened

This field enables you to : z configure the number of connections that can be opened by the module, z z activate an access check service, list the remote devices which can be connected to the module according to the communication protocol.

The Connections that can be opened field gives the maximum number of devices that can be connected in parallel to the module: z z

The default value is 8 connections.

The value is between 1 and 32 connections.

Note: You are recommended to set this parameter to the useful value in order to optimize the communication resources for each connection point.

Access control The Access check box is used to activate or deactivate the check on remote devices that want to open a TCP connection to the module.

z

If the box is checked, access check management is activated and the

Access column in the table is de-grayed (active).

If the module is operating in server mode, only the remote devices selected by the Access box in the table are authorized to be connected as a client and then to communicate.

z

If the box is unchecked, check management does not operate and the

Access column in the table is grayed out (not active).

If the module is operating in server mode, third party remote devices can be connected as a client and then communicate with the module without having to be declared in the table.

Note: The access check only works on the TCP/IP profile and is used for the module to operate in server mode.

138

35011050 01 July 2006

Function table

Configuration parameters

This table enables you: z to list the remote devices with which the local module wishes to open a TCP z connection and then transmit (module operating in client mode), to provide a cross reference between the X-WAY address {network, station} and the IP address , z z z the network number must be less than or equal to 127, the station number is between 0 and 63 for a connection in UNITE or between

100 and 163 for a connection in Modbus.

to specify the communication protocol for each remote device during the connection using a scrolling menu: z z

UNI-TE (default value),

Modbus , z z when managing access checks, to nominate the remote devices authorized to open a TCP connection and then to send to the local module (module operating in server mode), for each remote IP address, to choose the Connection mode using a scrolling menu : z

Monoconnection : the module only allows one connection with the same z remote IP address,

Multiconnection : the module allows only one connection with the same remote IP address in client mode and several connections with the same remote IP address in server mode.

35011050 01 July 2006

139

Configuration parameters

Ethernet configuration parameters

Introduction This field is used to define the format of the Ethernet frame via TCP/IP: z the Ethernet II format: complying with the FRC 894 standard (the most commonly z used), the 802.3 format: complying with the FRC 1042 standard. This format is to be selected if the remote devices use this format.

140

35011050 01 July 2006

7.2

Configuration parameters

Configuration parameters for the IO Scanning facility

Introduction

Subject of this sub-chapter

What's in this

Section?

This sub-chapter introduces the configuration parameters linked to the IO Scanning facility.

This section contains the following topics:

Topic

Configuration Parameters Linked to the IO Scanning Utility

Configuration of general parameters for IO Scanning facility

Configuration of scanned peripheral devices

Page

142

144

145

35011050 01 July 2006

141

Configuration parameters

Configuration Parameters Linked to the IO Scanning Utility

At a Glance The TSX ETY modules are comprised of configuration parameters for the IO

Scanning utility.

Depending on the TSX ETY module selected, some configuration parameters cannot be accessed on the configuration screen. They are either not shown on the screen or are grayed out.

142

35011050 01 July 2006

Configuration parameters

Availability of

Parameters

Parameters

Input fallback

The following table shows, for each ETHERNET module, the parameters that can be accessed from the configuration screen and the values that they can have.

TSX ETY 110

Scanning adjustment Fast

Normal

Slow

Master %MW zones

Peripherals scanned

Read Ref.

Write Ref.

IP Address

Unit ID

Repetitive rate

Master RD ref.

Slave RD ref.

RD count

Master WR ref.

Slave WR ref.

WR count

Description

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

X

X

X

TSX ETY 410•/

PORT/510•

Fallback to 0/

Maintain set at 10 ms from 15 to 240 ms from 150 to 1000 ms

X

X

X

X

None/Fast/Normal/

Slow automatic

X

X automatic

-

Legends:

X Accessible

Not accessible

35011050 01 July 2006

143

Configuration parameters

Configuration of general parameters for IO Scanning facility

Introduction

Input fallback

Adjusting the scanning

To configure the IO Scanning service some parameters are general at the remote inputs/outputs: z z z the input fallback mode, adjusting the scanning periods, the read and write zones.

This sub window is used to configure the behavior of inputs when the inputs have not been refreshed (example : PLC set to Stop, device disconnection, …) : z z

Fallback to 0

Maintain

This sub window is used to configure the scanning period in milliseconds : z the Fast period : this period cannot be configured (field grayed out) and is set at

10 ms.

z z the Normal period : this period can be configured from 30 - 240 ms by increments of 15 ms.

the Slow period : this period can be configured from 150 - 1000 ms by increments of 50 ms.

Note: The value of the Normal period cannot be less than the value of the Slow period.

Master %MW fields

This sub window is used to define the internal word formats from the (%MW) memory application dedicated to the read and write zones.

For that you have to enter the following: z for the read zone Read Ref.

, the address of the start of the internal words table z for reading inputs, for the writing field Write Ref.

, the address of the start of the internal words table for writing outputs.,

The length of the tables has a maximum exchange capacity of: z

2 Kwords for the read zone, z

2 Kwords for the write zone.

Note: The tables must not overlap each other and an overrun check is carried out in the global validation.

144

35011050 01 July 2006

Configuration parameters

Configuration of scanned peripheral devices

At a Glance

The IP Address and Unit ID fields

The IP Address field is used to list the devices which must be scanned by the

ETHERNET module.

The Unit ID field is used to associate the slave address of the device connected to an ETHERNET/Modbus gateway with the IP address. See Architecture supported

by a Modbus communication on the TCP/IP profile., p. 73 .

z z values are from 0 to 255, the default value is 255.

Repetitive rate

Scanned peripheral devices are configured in a table which is used: z z to list remote devices to be scanned, using the IP address, to specify the scanning period allotted to it for each remote device, z z to configure, for each device, the amount of space the input and output words take up in the read and write zones, to add comments for each device.

The Repetitive rate field is used to associate an IP address with its scanning period.

See

IO Scanning Facility, p. 82

.

The type of period is selected using a pull-down menu and can have the following values: z

NONE : this selection is used to deactivate scanning of the corresponding IP address, z z z

FAST : for fast scanning periods,

NORMAL : for nominal scanning periods,

SLOW : for slow scanning periods.

Note: When NONE is selected, the internal words reserved for the corresponding

IP address are saved in the read and write zones but are not updated.

35011050 01 July 2006

145

Configuration parameters

Master RD ref. and master WR ref.

These parameters give the addresses of the beginning of each range reserved for the device.

These parameters cannot be accessed. They are calculated automatically as the sum of: z z the address of the beginning of the Read Ref.

table and the Write Ref.

table, and the length of the RD count and WR count fields.

Example

The ETHERNET module scans two devices: z a Momentum at the address IP1, which has 4 input words.

z a Momentum at the address IP2, which has one input word.

Furthermore, the read field address starts at %MW100.

In this case, master RD ref.

for the address IP1 equals 100. The internal word range reserved for the address IP1 starts at %MW100 and is made up of 4 words.

Therefore, master RD ref.

for the address IP2 equals 104. The internal word range reserved for the address IP2 starts at %MW104 (=%MW100 + 4 input words).

Slave RD ref. and slave WR ref.

These fields correspond to the indices of the first word to be read and written for remote devices to be scanned.

z z slave RD ref.

: specifies the address of the first word to be read slave WR ref.

: specifies the address of the first word to be written

RD count and

WR count

These fields contain the number of words to be transmitted per device in read and write.

These values conveyed by the Modbus requests vary: z z from 0 to 125 for the RD count field (if it equals 0,the read request is not sent), from 0 to 100 for the WR count field (if it equals 0,the write request is not sent),

Note: If the device to be scanned does not respond to the Modbus (17) read/write requests, the remote device must be configured over two lines, one for reading with the WR count value at zero, and the other for writing with the RD count value at zero.

Description

146

Note: These two fields cannot both have the value 0. Otherwise, the remote device will not be managed.

This field is not used by the module. It is only used to locate the device in the configuration more easily.

It has a maximum size of 32 characters.

35011050 01 July 2006

7.3

Configuration parameters

Configuration Parameters for the Address Server

Utility

At a Glance

Aim of this

Section

What's in this

Section?

This Section introduces the configuration parameters linked to the BOOTP/DHCP address server.

This section contains the following topics:

Topic

Configuration Parameters Linked to the Address Server Utility

Address Server Configuration

Page

148

149

35011050 01 July 2006

147

Configuration parameters

Configuration Parameters Linked to the Address Server Utility

At a Glance The TSX ETY modules are comprised of configuration parameters linked to the address server utility.

Depending on the TSX ETY module selected, some configuration parameters cannot be accessed on the configuration screen. They are either not shown on the screen or are grayed out.

Availability of

Parameters

Parameters

The following table shows, for each ETHERNET module, the parameters that can be accessed from the configuration screen and the values that they can have.

TSX ETY 110

HTTP modification Locked in operation

Password

BOOTP/DHCP address table

-

-

-

X

X

TSX ETY 410•/

PORT/510•

X

-

Legends:

X Available

Not available

148

35011050 01 July 2006

Configuration parameters

Address Server Configuration

At a Glance

Utility

Parameters linked to the address server are divided into 3 categories: z

The type of server: BOOTP or DHCP z z rights to modify the utility via the HTTP server, the table of addresses for which service is provided.

This zone allows the type of server to be selected (BOOTP or DHCP): z z

The BOOTP mode can be used when the "Replace faulty remote stations" is not wanted.

The DHCP mode is essential if the "Replace faulty remote stations" utility is required.

Note: BOOTP mode is the mode automatically selected if the applications have been created with PL7 (version V4.0 and later) and configure the

TSX ETY 410•/PORT/510• modules.

HTTP modification

Address Tables

This zone is used to define the access rights to the DHCP or BOOTP address table via the HTTP server.

The access rights are configured by two parameters: z the Locked in operation check box: which activates or deactivates access z control to the table, the Password field: the table is accessed via the HTTP server by means of a password of no more than 8 ASCII characters.

Depending on the selection made in the Utility zone,

The BOOTP table can be used: z to list, by their MAC address, the remote stations which need the BOOTP server to start up, z to provide a correspondence between the MAC and IP addresses,

The DHCP table can be used: z to list, by their MAC address or by name (16 character ASCII), the remote stations which need the DHCP server to start up, z to supply a connection between the MAC address or the name and the IP address of the remote station, the Netmask and the Gateway.

35011050 01 July 2006

149

Configuration parameters

7.4

Configuration parameters for the SNMP facility

Introduction

Subject of this sub-chapter

What's in this

Section?

This sub-chapter introduces the configuration parameters linked to the SNMP facility.

This section contains the following topics:

Topic

Configuration Parameters Linked to the SNMP Utility

Configuration of the SNMP Utility

Page

151

152

150

35011050 01 July 2006

Configuration parameters

Configuration Parameters Linked to the SNMP Utility

At a Glance The TSX ETY modules are comprised of configuration parameters linked to the

SNMP utility.

Depending on the TSX ETY module selected, some configuration parameters cannot be accessed on the configuration screen. They are either not shown on the screen or are grayed out.

Availability of

Parameters

Parameters

IP Address Managers

Agent

Community names

Security

The following table shows, for each ETHERNET module, the parameters that can be accessed from the configuration screen.

TSX ETY 110

Location (SysLocation)

Contact (SysContact)

SNMP Manager

Set

Get

Trap

Enable "Authentication Failure" trap

X

X

X

X

-

X

X

X

X

X

X

X

X

X

X

X

TSX ETY 410•/

PORT/510•

-

Legends:

X Accessible

Not accessible

35011050 01 July 2006

151

Configuration parameters

Configuration of the SNMP Utility

At a Glance Parameters linked to the SNMP module are divided into 4 categories: z the IP addresses of the SNMP module administrative devices, z z z the agents, the community names, security.

Note: Only 7-bit ASCII characters can be used in the character string entry fields.

Administrators

IP Addresses

Agent

This zone allows the completion of the SNMP administrators IP addresses. The modules authorize a maximum of two administrators.

These addresses are used during possible transmission of events (TRAP). See

SNMP Communication on UDP/IP, p. 95

.

This zone allows the localization and identification of an agent from the SNMP administrator.

It comprises two fields: z

The Location (SysLocation) field: indicates the physical location of the device z

(32 characters maximum).

The Contact (SysLocation) field: indicates the personnel to contact for device z management and the method of contact (32 characters maximum).

It is possible to select information assignment by a "SNMP Manager" tool for network management, rather than by PL7 software. To do this, check the SNMP

Manager box.

152

35011050 01 July 2006

Community

Name

Security

Configuration parameters

This zone allows the definition of a community name by utility family Set, Get and

Trap.

It comprises three fields: z

The Set field defines the community name for the Set utility (16 characters maximum). The default value of the field is Public .

z z

The Get field defines the community name for the Get utility (16 characters maximum). The default value of the field is Public .

The Trap field defines the community name for the Trap utility (16 characters maximum). The default value of the field is Public .

The purpose of these fields is to define the access rights for SNMP agent MIB objects (local module) in relation to requests transmitted by the administrator.

Example

If the administrator transmits a SetRequest request with the community name Test and the module has the community name Public , the request will not be executed.

This zone contains the Enable "Authentication Failure" trap check box.

Enabling this box allows the transmission of an event (TRAP) of an authentication failure to be confirmed from the SNMP agent to the administrator that originally posted the request.

In this way, the agent warns the administrator that the request has been refused following an identification error (community name configured in the administrator is different to the one configured in the agent).

CAUTION

Modifications to the SNMP parameters

The SNMP administrator is able to modify the value of certain parameters, which can be configured by PL7 (Enabling "Authentication failure", Location, Contact. etc.)

When there is a cold start, warm restart or application download, the values initially configured in PL7 are then restored.

Failure to follow this precaution can result in injury or equipment damage.

35011050 01 July 2006

153

Configuration parameters

7.5

Configuration Parameters of the Global Data

Utility

At a Glance

Aim of this

Section

What's in this

Section?

This Section introduces the configuration parameters linked to the Global Data utility.

This section contains the following topics:

Topic

Configuration Parameters Linked to the Global Data Utility

Configuring the General Parameters for the Global Data Utility

Configuration of the Variables Table

Page

155

157

158

154

35011050 01 July 2006

Configuration parameters

Configuration Parameters Linked to the Global Data Utility

At a Glance The TSX ETY modules are comprised of configuration parameters linked to the

Global Data utility.

Availability of

Parameters

Parameters

Global Data configuration

Table of variables

Group address

Distribution Period

Validity time out

Multicast Filtering

%MW Zone

Ident

Type

Symbol

Address

Length

-

Legends:

X Accessible

Not accessible

-

-

-

-

-

-

-

-

-

-

TSX ETY 110 TSX ETY 410•/

PORT/510•

X

X

X

X

X

X

X

X

X

X

35011050 01 July 2006

155

Configuration parameters

Properties The following table provides the Global Data utility properties.

Type

Number max. of publications

Size of a variable at publication

Number max. of subscriptions

Maximum variable size at subscription

Value

1

1 to 512 words

64

Total of 2K words

The application variables are stored in a contiguous %MW zone.

Each published or subscribed application variable in a Distribution Group is linked to a Global Data.

Each Global Data has a unique identification ( Ident.

) on the inside of a Distribution

Group. This identification corresponds to the status bit position in the Global Data status bit zone.

The link between published/subscribed application variable and Global Data is established during the configuration phase.

156

35011050 01 July 2006

Configuring the General Parameters for the Global Data Utility

Configuration parameters

At a Glance

Group Address

Distribution

Period

The following parameters can be entered in the Global Data Configuration zone of the configuration (See

Configuring the Global Data Utility, p. 252 ) screen:

z z

Group address

Distribution period z z z

Validity time out

Multicast filtering

%MW Zone

This zone allows the multicast IP address (class D) to be entered for the group to which the station belongs. The value 239.255.255.255 is the default value.

This zone allows the distribution period of the publication to be selected. The publication is synchronized with the PLC master task. The publication can be performed at each cycle of the Mast task (default value), or every n cycles of the

Mast. task.

Validity Time Out This zone allows the validity "time-out" value to be adjusted.

An associated status bit (%IW zone) is linked to each Global Data and allows monitoring if the data has been published and received by the end of the time indicated in this window. If yes, the value is 1, otherwise the bit is set to 0.

Multicast

Filtering

This check box activates the multicast filtering.

This function allows the reduction of data flow on large networks. Multicast filtering requires the use of commutators that support this function (GMRP IEEE 802.1D protocol).

%MW Zone This zone allows the configuration of the start word address in the memory zone reserved for variables. According to the variable used, the end zone word address is calculated automatically by the program and displayed. An error appears if the maximum length is exceeded.

35011050 01 July 2006

157

Configuration parameters

Configuration of the Variables Table

At a Glance

Ident. Zone

Type Zone

The Table of variables zone of the Global Data configuration screen enables you to configure the station variables.

Several zones are available: z

Ident.

z z z z

Type

Symbol and button labeled Update symbols

Address

Length

This column, numbered from 1 to 64 , indicates the identification numbers of the configurable variables.

This column enables you to choose the type of each variable: z

NONE : variable that is neither published nor subscribed z z

PUB : published variable

SUB : subscribed variable

Symbol Zone

Address zone

Length Zone

This column enables you to display the symbol given to a %MW zone, defined in the

PL7 application variables editor.

Use the Update symbols button to update the value following a modification.

This column displays the zone start address of a variable in %MW.

The word index of the preceding variables is automatically updated according to the length and the choice of address of the first word of the zone (See %MW Zone,

p. 157

).

In this column enter the length of the variable wanted in number of words. The %MW zone is thus updated.

Error Monitoring There is no monitoring of consistency between the configurations of the different stations.

In the case of a configuration error, the %MWxy.i.13 internal word indicates the type of error (see

Internal Words, p. 281 ).

158

35011050 01 July 2006

7.6

Configuration parameters

Configuration Parameters of the Time Synchronization Service

At a Glance

Aim of this

Section

What's in this

Section?

This section introduces the configuration parameters linked to the time synchronization service, which uses the Network Time Protocol (NTP).

This section contains the following topics:

Topic

Configuration Parameters Linked to the Time Synchronization Service (NTP)

Using the Time Synchronization Service

Configuration of the Time Synchronization Service (NTP)

Page

160

163

164

35011050 01 July 2006

159

Configuration parameters

Configuration Parameters Linked to the Time Synchronization Service (NTP)

List of

Parameters

Time Zones

Available

Configure or change the following parameters on the NTP Configuration page.

1.

IP address of primary NTP server z

Enter a valid IP address

2.

IP address of secondary NTP server z

Enter a valid IP address

3.

Polling Period (in seconds)

Enter a value z min = 1sec z z max = 120sec default = 5 sec

4.

Time Zone z

Select from drop-down menu z

Universal Time, Coordinated (GMT) = default

Custom time zone

5.

Automatically adjust clock for daylight saving change z

Parameter is selected by default (check mark appears) if daylight saving time is chosen.

Select one from drop-down menu.

Time Zone Description

Custom

(GMT-12:00) Dateline Standard Time [Eniwetok Kwajalein]

(GMT-11:00) Samoa Standard Time [Midway Is Samoa]

(GMT-10:00) Hawaiian Standard Time [Hawaii Honolulu]

(GMT-09:00) Alaskan Standard Time [Anchorage]

(GMT-08:00) Pacific Standard Time [Los Angeles Tijuana]

(GMT-07:00) Mexican Standard Time [Chihuahua La Paz Mazatlan]

(GMT-07:00) Mountain Standard Time [Arizona Phoenix]

(GMT-07:00) Mountain Standard Time [Denver]

(GMT-06:00) Central Standard Time [Chicago]

(GMT-06:00) Mexico Standard Time [Tegucigalpa]

(GMT-06:00) Canada Central Standard Time [Saskatchewan Regina]

(GMT-06:00) Central America Standard Time [Mexico_city]

(GMT-05:00) SA Pacific Standard Time [Bogota Lima Quito]

(GMT-05:00) Eastern Standard Time [New York]

No

No

Yes

No

Yes

Yes

No

Yes

Yes

No

No

Yes

Yes

DST

Available

Yes

No

160

35011050 01 July 2006

35011050 01 July 2006

Configuration parameters

Time Zone Description

(GMT-05:00) Eastern Standard Time [Indiana (East)] [Indianapolis]

(GMT-04:00) SA Western Standard Time [Caracas La Paz]

(GMT-04:00) Pacific SA Standard Time [Santiago]

(GMT-03:30) Newfoundland Standard Time [Newfoundland St Johns]

(GMT-03:00) E. South America Standard Time [Brasilia Sao_Paulo]

(GMT-03:00) SA Eastern Standard Time [Buenos Aires Georgetown]

(GMT-02:00) Mid-Atlantic Standard Time [South_Georgia]

(GMT-01:00) Azores Standard Time [Azores Cape Verde Island]

(GMT)

(GMT0)

Universal Coordinated Time [Casablanca, Monrovia]

Greenwich Mean Time [Dublin Edinburgh Lisbon London]

(GMT+01:00) Romance Standard Time [Amsterdam CopenHagen Madrid

Paris Vilnius]

(GMT+01:00) Central European Standard Time [Belgrade Sarajevo Skopje

Sofija Zagreb]

(GMT+01:00) Central Europe Standard Time [Bratislava Budapest Ljubljana

Prague Warsaw]

Yes

Yes

(GMT+01:00) W. Europe Standard Time [Brussels Berlin Bern Rome

Stockholm Vienna]

(GMT+02:00) GTB Standard Time [Athens Istanbul Minsk]

(GMT+02:00) E. Europe Standard Time [Bucharest]

Yes

Yes

Yes

(GMT+02:00) Egypt Standard Time [Cairo] Yes

(GMT+02:00) South Africa Standard Time [Johannesburg Harare Pretoria] No

(GMT+02:00) FLE Standard Time [Helsinki Riga Tallinn]

(GMT+02:00) Israel Standard Time [Israel Jerusalem]

(GMT+03:00) Arabic Standard Time [Baghdad]

(GMT+03:00) Arab Standard Time [Kuwait Riyadh]

Yes

Yes

Yes

No

(GMT+03:00) Russian Standard Time [Moscow St. Petersburg Volgograd] Yes

(GMT+03:00) E. Africa Standard Time [Nairobi] No

(GMT+03:30) Iran Standard Time [Tehran]

(GMT+04:00) Arabian Standard Time [Abu Dhabi Muscat]

Yes

No

(GMT+04:00) Caucasus Standard Time [Baku Tbilisi]

(GMT+04:00) Afghanistan Standard Time [Kabul]

(GMT+05:00) Ekaterinburg Standard Time [Ekaterinburg]

(GMT+05:00) West Asia Standard Time [Islamabad Karachi Tashkent]

Yes

No

Yes

No

No

Yes

No

Yes

Yes

Yes

Yes

Yes

No

DST

Available

No

No

161

Configuration parameters

Time Zone Description

(GMT+05:30) India Standard Time [Bombay Calcutta Madras New Delhi]

(GMT+06:00) Central Asia Standard Time [Almaty Dhaka]

(GMT+06:00) Sri Lanka Standard Time [Columbo]

(GMT+07:00) SE Asia Standard Time [Bangkok Hanoi Jakarta]

No

No

(GMT+08:00) China Standard Time [Beijing Chongqing Hong Kong Urumqi] No

(GMT+08:00) W. Australia Standard Time [Perth] No

DST

Available

No

Yes

(GMT+08:00) Singapore Standard Time [Singapore]

(GMT+08:00) Taipei Standard Time [Taipei]

(GMT+09:00) Tokyo Standard Time [Osako Sapporo Tokyo]

(GMT+09:00) Korea Standard Time [Seoul]

No

No

No

No

(GMT+09:00) Yakutsk Standard Time [Yakutsk]

(GMT+09:30) Cen. Australia Standard Time [Adelaide]

(GMT+09:30) AUS Central Standard Time [Darwin]

(GMT+10:00) E. Australia Standard Time [Brisbane]

(GMT+10:00) AUS Eastern Standard Time [Canberra Melbourne Sydney]

(GMT+10:00) West Pacific Standard Time [Guam Port Moresby]

(GMT+10:00) Tasmania Standard Time [Hobart]

(GMT+10:00) Vladivostok Standard Time [Vladivostok]

(GMT+11:00) Central Pacific Standard Time [Magadan Solomon Is New

Caledonia]

(GMT+12:00) New Zealand Standard Time [Auckland Wellington] Yes

Yes

No

Yes

Yes

Yes

Yes

Yes

No

No

(GMT+12:00) Fiji Standard Time [Fiji Kamchatka Marshall Is] No

162

35011050 01 July 2006

Configuration parameters

Using the Time Synchronization Service

Establishing

Accuracy at

Power Up

Obtaining and

Maintaining

Accuracy

Before starting a system, the Ethernet network must be configured for a predefined interval within which the accuracy is established. Accuracy is established at powerup—the Ethernet module boots and then obtains the time from the NTP Server.

Several updates may be required to achieve peak accuracy. Once an accurate time is obtained, the time synchronization service sets the STATUS in the associated time service register.

The time service clock starts at 0 and increments until the Ethernet network time is fully updated from the module.

Model

Premium with PL7

Starting Date

January 1st 1980 00:00:00.00

z z z

Clock accuracy is not affected by issuing Stop/Run commands on the PLC

Clock updates are not affected by issuing Stop/Run commands on the PLC

Mode transitions do not affect the accuracy of the Ethernet network

Reinitializing the

Time Service

Register

After a download or an NTP server swap, the status clock value associated with the time service register in the CPU is reinitialized.

Two polling periods elapse before an accurate time is re-established.

35011050 01 July 2006

163

Configuration parameters

Configuration of the Time Synchronization Service (NTP)

Configuring the

Time Service with the NTP

Configuration

Page

You must use the module’s embedded Web page to configure the time service. No other method is available.

NTP Configuration

NTP Server Configuration

IP Address of Primary NTP Server:

IP Address of Secondary NTP Server:

Polling Period:

Time Zone

(GMT-05:00)Eastern Standard Time[New York]

15

192.168.5.100

0.0.0.0

sec

Automatically adjust clock for daylight saving change

Save Cancel Disable NTP

Time Service

Command

Buttons

Execute the following commands

Command Button Description

Save Stores new NTP (time service) configuration. Previous configuration is no longer valid.

Cancel

Disable NTP

Cancels new NTP (time service) configuration. Previous configuration is valid

IP of Primary and Standby set = 0.

NTP server not polled

Time in controller not updated.

164

35011050 01 July 2006

Configuration parameters

Changing Time

Service

Parameters

To make any changes to the time synchronization service,

Step

1

2

Action

Enter changes in the appropriate field on the NTP Configuration page for one or all of the configurable parameters.

Click Save.

Important

Information about the Time

Service

Note: About the Time Service

1.

Enable/Disable Daylight Savings Time parameter

If the Enable/Disable check box is selected, the module automatically corrects the local time to account for daylight savings time. Therefore, requiring no action, as the daylight savings time start and end are automatically changed each year.

2.

Polling Time Parameter

The time (in seconds) is the time between time updates from the NTP server.

The default is 5 Seconds.

3.

Storing the Time Service Configuration

The last time service configuration is saved internally in the Ethernet module.

4.

Replacing the Ethernet Module

If the Ethernet module has to be replaced, the stored configuration is lost, and the system returns to the default configuration.

35011050 01 July 2006

165

Configuration parameters

Customizing

Time Zone

Parameters

If you want a time zone not listed in the time zone table,

Step Action

1 Write the text rules for the custom time zone.

Comment

2 Using an FTP client, store your rules in the file:

/FLASH0/wwwroot/conf/NTP/customrules user ID: ntpupdate password: ntpupdate

3 When the rules are written, choose the drop down menu on the NTP Configuration web page, and configure (or reboot) the module by selecting

Time Zone = Custom

Root directory to store 'customrules' is set by the FTP server as

/FLASH0/wwwroot/conf/NTP

The NTP component looks for customrules, calls the tz compiler and generates a new file called

'tz_custom'. This file is binary file and should not be edited.

If the tz compiler detects a syntax error in customrules, the error is logged in the file:

/FLASH0/wwwroot/conf/NTP/ error.log

1.

NTP component is not launched

2.

NTP Status field in diagnostic web page displays NOT OK.

4 If you want more information, the syntax to write those rules along with a few examples are found in the module in

/FLASH0/wwwroot/conf/NTP/instructions.txt

166

35011050 01 July 2006

7.7

Configuration parameters

ETHWAY profile configuration paramaters

Introduction

Subject of this sub-chapter

What's in this

Section?

This sub-chapter introduces the configuration parameters linked to the ETHWAY profile.

This section contains the following topics:

Topic

Configuration Parameters Linked to the ETHWAY Profile

Configuration of ETHWAY data

Page

168

169

35011050 01 July 2006

167

Configuration parameters

Configuration Parameters Linked to the ETHWAY Profile

At a Glance

Availability of

Parameters

Parameters

ETHWAY data

(common words)

The TSX ETY modules have associated with them configuration parameters for the

ETHWAY profile.

Depending on the TSX ETY module selected, some configuration parameters cannot be accessed on the configuration screen. They are either not shown on the screen or are grayed out.

The following table shows, for each ETHERNET module, the parameters that can be accessed from the configuration screen and the values that they can have.

TSX ETY 110

None

Common read words

Common read/write words

Word size/station 4

8

16

32

64

Network address

X

X

X

X

X

X

X

X

X

-

-

-

-

-

-

-

-

-

TSX ETY 410•/

PORT/510•

-

Legends:

X Accessible

Not accessible

168

35011050 01 July 2006

Configuration parameters

Configuration of ETHWAY data

Introduction

None

The ETHWAY data parameters are used to configure the common words by: z selecting the type of service supported, z z the number of words allocated per station, the network address of the local station.

The selection of this field invalidates the management of common words in the application.

The module does not manage the common database.

Common reading words

The application has read only access to the common words.

Common reading

/writing words

The application has read and write access to the common words.

Size of words/ station

This field can be accessed when selecting reading/writing words .

Common reading words or Common

Filling in this field configures the number of common words managed by the local module.

Note: The size of common words must be the same for each network station.

Network address This field can be accessed when selecting Common reading words or Common reading/writing words .

Filling in this field identifies the network which supports the common words service.

35011050 01 July 2006

169

Configuration parameters

170

35011050 01 July 2006

TSX ETY 110 Module

8

Introduction

Subject of this chapter

What's in this

Chapter?

This chapter describes the implementation of a TSX ETY 110 module.

This chapter contains the following sections:

Section

8.1

8.2

8.3

8.4

Topic

General points

Configuration

Debugging

Language objects associated with the TSX ETY 110 module

Page

172

178

197

209

35011050 01 July 2006

171

TSX ETY 110

8.1

General points

Introduction

Subject of this sub-chapter

What's in this

Section?

This sub-chapter introduces Ethernet communication from the TSX ETY 110 coupler and its characteristics.

This section contains the following topics:

Topic

TSX ETY 110 Module : General points

Characteristics

Performances

Module TSX ETY 110 operating modes

Common functions on the ETHWAY and TCP/IP profile

Page

173

174

175

176

177

172

35011050 01 July 2006

TSX ETY 110

TSX ETY 110 Module : General points

Introduction The communication channel of the ETHERNET TSX ETY 110 module offers two connection types : z connection to an ETHWAY network with common word and X-WAY messaging facilities on an ETHWAY profile, z connection to a TCP/IP network with X-WAY UNI-TE and Modbus messaging facility on a TCP/IP profile,

Because it functions as an SNMP agent, the module can be supervised by one or two SNMP managers.

Architecture type This module can be used in three different situations: z in a closed proprietary ETHWAY architecture z z in a proprietary ETHWAY architecture connected to a TCP/IP network by an intermediate gateway in open TCP/IP architecture via direct connection to the network.

According to your choice of architecture, the recommended method of use is different. See

Example of proprietary architecture ETHWAY, p. 187

.

z z

Note: When the ETHERNET network load passes 30%, it is recommended that you use : the TCP/IP profile instead of the ETHWAY profile, switch type accessories, routers to reduce the load.

35011050 01 July 2006

173

TSX ETY 110

Characteristics

Messaging

Maximum capacity of the module

The TSX ETY 110 module supports: z maximum 32 parallel connections on TCP/IP, z but only one connection to a remote device.

The maximum frame size depends on the type of transaction : z

In synchronous messaging, the maximum frame size is 256 bytes.

z

In asynchronous messaging, the maximum frame size is 1 Kbyte.

The number of communication functions handled simultaneously depends on the type of profile: z z where a TCP/IP profile is used, maximum 16 simultaneous messages, where an ETHWAY profile is used, maximum 16 simultaneous messages.

The module provides the following capacities: z z z in the case of ETHWAY messaging : 130 messages per second, in the case of X-Way messaging on TCP/IP : 140 messages per second,

in the case Modbus messaging on TCP/IP : 100 messages per second.

z z

Note: A message can be: sending a communication function, the response to a communication function.

Common words A common word message is equivalent to 0.5 data messages.

Example of application dimensioning :

5 stations exchange common words every 100 ms and X-Way messaging on

TCP/IP.

The flow of common words received by each module is 50 messages per second of common words, around 25 messages per second on TCP/IP.

So the remaining maximum capacity on each module on TCP-IP is:

140 – 25 + 115 messages per second

174

35011050 01 July 2006

TSX ETY 110

Performances

Example The performances below are given for a communication between two PLCs equipped with TSX 57-30 processors.

The values are expressed in ms and represent an average period of time described in the table.

Opening time of a TCP/IP connection

Transaction time for a UNI-TE request of 128 bytes in 50 ms periodic mode (MAST task)

Transaction time for a UNI-TE request of 128 bytes in 4 ms cyclic mode

(MAST task)

Transfer time for common words (turnaround ) in 50 ms periodic mode

Module feed-through time

10 ms

150 ms

80 ms

250 ms

15 to 30 ms

The transaction time takes into account the time it takes to send a message and receive a reply.

35011050 01 July 2006

175

TSX ETY 110

Module TSX ETY 110 operating modes

Introduction

General chart

The following graph describes the TSX ETY 110 module’s operating modes.

Module stopped Module off

Power up

Operation

Module configured Function of communication

Module at self-test stage

Reset

Configuration Module not configured

Self-tests OK z z z

After power-up the module self-tests. During this stage the warning indicators flash.

The module does not operate with a default configuration. This has to be transmitted to it by the local PLC’s PL7 application.

The configuration values are given in the list of %KW language objects.

The network, station address is given by the code selectors on the front panel.

When the configuration is received, the module resets the current communication to zero before configuring itself (terminates current exchanges, shuts down TCP connections).

176

35011050 01 July 2006

TSX ETY 110

Common functions on the ETHWAY and TCP/IP profile

Duplicate MAC address

Managing IP parameters

Detecting a duplicate MAC address (defined by the code selector) between stations which have a Schneider MAC address is done when the device is switched on.

So that this detection is operational, the connection cable to the network must be plugged in before being switched on.

The RUN and ADR LEDs light up on the front panel of the module when a duplicate is detected.

In a closed architecture you may choose not to configure IP parameters and to keep the default values.

In an open TCP/IP architecture, the IP parameters (IP address, subnet mask, gateway address) must be configured.

The default value of the local IP address is derived from the MAC address (its uniqueness is not guaranteed in an open TCP/IP architecture). It is a class A IP address.

MAC Address

16# 00 80 F4 00 <network address> <station address>

Default IP address

16# 54 00 <network address> <station address>

The default value of the subnet mask is 0.0.0.0 (no subnet knowledge).

The default value of the default gateway is 0.0.0.0 (no IP gateway knowledge).

35011050 01 July 2006

177

TSX ETY 110

8.2

Configuration

Introduction

Subject of this sub-chapter

What's in this

Section?

This sub-chapter describes the implementation of the TSX ETY 110 module during its configuration.

This section contains the following topics:

Topic

Module configuration screen

Type of communication according to chosen configuration

Messaging configuration on the TCP/IP or ETHWAY profile

Configuration of SNMP facility.

Configuration of the Bridge function

Example of proprietary architecture ETHWAY

Example of the ETHWAY architecture connected to TCP/IP

Example of connection to a non private TCP/IP network

Example of communication between Premium and Quantum

Page

179

181

182

184

186

187

190

193

195

178

35011050 01 July 2006

TSX ETY 110

Module configuration screen

Introduction

Illustration

This screen, split into six areas, is used to register the communication channel and to configure the necessary parameters for an ETHERNET link.

The screen dedicated to ETHERNET communication looks like this :

1

TSX SAY 110 [RACK 0 POSITION 1]

Configuration

Designation : TCP/IP ETHWAY MODULE

2

3

4

Configuration of Connections

Connections allowed

8

Net.Sta

36.2

36.10

Access control

3

4

1

2

IP address

139.160.65.109

139.160.65.110

Protocol

UNITE

Access

IP address configuration

IP default address

Configured

IP address

Subnetwork mask

Gateway address

139 160 65 106

255 255 252 0

139 160 64 1

Client/Server

Ethernet configuration

Ethernet II 802.3

Ethway data

None

Common words R

Common words R/W

No. of words/station

4 8

Bridge ...

16 32 64

Network address

Advanced

SNMP ...

0

5

6

35011050 01 July 2006

179

TSX ETY 110

Elements and functions

This table describes the different areas that make up the configuration screen:

Area common specific

Address Function

1 common section at the communication configuration screens

(Communication applications Volume 1 - Overwiew of configuration screen)

2

3 is used to configure TCP/IP connections. See Connection

configuration parameters, p. 138

.

is used to configure the IP address of the module. See

Configuration Parameters for IP Addresses, p. 136

.

4

5

6 is used to configure the ETHERNET type of frame. See Ethernet

configuration parameters, p. 140

.

is used to configure the ETHWAY profile. See Configuration of

ETHWAY data, p. 169

.

is used to configure the SNMP facility. See Configuration of the

SNMP Utility, p. 152 .

180

35011050 01 July 2006

TSX ETY 110

Type of communication according to chosen configuration

Introduction Depending on the configuration of the TSX ETY 110 module, you can carry out messaging : z z either on the ETHWAY profile, or on the TCP/IP profile.

Module in client mode

When the module is the client, the ETHWAY or TCP/IP profile is fixed by the configuration of stations in the module’s connection table.

The following table specifies which profile is used according to the configuration of the table.

Communication profile

If the address of the remote station is … referenced in the table.

not referenced in the table.

TCP/IP ETHWAY

Note: If no station is recorded in the table, the communication profile is ETHWAY.

Module in server mode

When the module is the server, the ETHWAY or TCP/IP profile is fixed according to the client device : z

If the client transmits on the ETHWAY profile, the module responds on the

ETHWAY profile.

z

If the client transmits on the TCP/IP profile, the module responds on the TCP/IP profile.

Note: Where access control is activated, compatibility must be ensured between the client and server’s connection tables. If the client’s address is referenced in the server’s table, the client must communicate on the TCP/IP profile.

35011050 01 July 2006

181

TSX ETY 110

Messaging configuration on the TCP/IP or ETHWAY profile

Introduction In order to use the TSX ETY 110 module to communicate on ETHERNET, it is necessary to adjust the configuration parameters.

182

35011050 01 July 2006

How to configure the module

Before configuring data module, access the configuration screen.

Start of messaging configuration

TSX ETY 110

Do you want the module to communicate on the profile … ?

ETHWAY

TCP/IP

Select the number of

Connections which can be opened

Fill in the fields of the connection table for each remote server device

Adr X-WAY

IP Address

Protocol

Does the module exchange common words?

Yes

Select the common words exchanged in read or read/write

No

Select the number of words exchanged per station and the number of the network.

Select the check box

Access control

In the connections table, select the

Access check box of each remote client device

Yes

If the module is a server, do you want to have access control?

No

Do you want to address the module by default?

Yes

Select the box

Default IP address

No Select the box

Configured

Fill in the fields

IP Address

Subnetwork mask

Gateway Address

Select the

ETHERNET Configuration

End of messaging configuration

35011050 01 July 2006

183

TSX ETY 110

Configuration of SNMP facility.

Introduction In order to use the TSX ETY 110 module as an SNMP agent, it is necessary to regulate the configuration parameters of the SNMP facility.

How to access the SNMP facility

The procedure for accessing the configuration parameters of the SNMP facility is as follows.

Step

1

2

Action

Access the module configuration screen.

Click on the SNMP button.

Result

The following window appears.

SNMP Configuration

IP address managers

IP address manager 1 196 211 185 50

Agent

Location (SysLocation)

Contact (SysContact)

Factory

Manager

Community names

Set public

Get public

Trap public

IP address manager 2 0 0 0 0|

Security

Enable “Authentification Failure”trap

OK Cancel

Ready

184

35011050 01 July 2006

TSX ETY 110

How to configure

SNMP

The procedure for configuring the SNMP facility is as follows.

Step

1

2

3

4

5

Action

Input the addresses of SNMP managers : z z

IP Manager 1 addresses

IP Manager 2 addresses

Fill in the fields : z z

Location (SysLocation)

Contact (SysLocation) .

If you want to set access rights, fill in the community names : z z z

Set

Get

Trap

If you want to activate transmission of an event to the module, check off the

Activate "Authentication Failure" trap box.

Accept the configuration with the OK button.

35011050 01 July 2006

185

TSX ETY 110

Configuration of the Bridge function

Introduction The TSX ETY 110 module can be used as an X-WAY bridge station. This guarantees clear communication between different networks.

Note: To find out about the implementation of this function, refer to the multinetwork communication part (See

Multi-network architectures, p. 289 ).

Subsequently, only the procedure for access to the bridge function will be developed.

How to access the bridge function

The procedure for accessing the configuration parameters of the bridge function is as follows.

Step

1

2

Action

Access the module configuration screen.

Select the Bridge button.

186

35011050 01 July 2006

TSX ETY 110

Example of proprietary architecture ETHWAY

Introduction The following figure illustrates the implementation of a TSX ETY 110 data module in a proprietary ETHWAY architecture.

Scheduler

Programming terminal

X-WAY: {1.3}

IP: 84.0.1.3

ETHERNET

1

X-WAY: {1.4}

IP: 84.0.1.4

1

Premium

X-WAY: {1.2}

IP: 84.0.1.2

Station 2

2 Premium

X-WAY: {1.1}

IP: 84.0.1.1

Station 1

FIPWAY

1 ETHWAY or TCP/IP TCP/IP communication

2 ETHWAY communication

35011050 01 July 2006

187

TSX ETY 110

Recommended method of use z z z z

The IP addressing is not set by the administrator (default value). It is derived from the values set on the module’s code selector.

Communication between the PLCs is by means of ETHWAY facilities (COM,

UNI-TE).

Communication between the PLC and the scheduler or the programming terminal makes use of ETHWAY facilities or UNI-TE on TCP/IP.

The format of the frames used is ETHERNET II.

Note: In the sequence of examples, it is assumed that the communication with the terminals is done on TCP/IP.

Configuration of the local address of the data module from station 2

In a closed environment, it is possible not to administrate the IP addresses; mode

Default IP address is selected.

IP address configuration

IP default address

Configured

IP address

Subnetwork mask

Gateway address

0

0

0

0

0

0

0

0

0 0 0 0

Client/Server configuration

Configuration of the connections of the data module from station 2

The field to input is the X-WAY address of the remote stations with which one wishes to communicate (X-WAY 1.3 address), the other fields are automatically initialized.

Access protection is disabled by default and the maximum number of connections is 32.

Configuration of Connections

Connections allowed

32

Net.Sta

1.3

Access

Control:

3

4

1

2

IP address

84.0.1.3

Protocol

UNITE

Access

Note: As the PLC is always the server with regard to the programming terminal, this does not have to be registered.

ETHERNET configuration of the data module from station 2

The ETHERNET frame format selected for TCP/IP is Ethernet II because in the example the terminals use this format.

Ethernet Configuration

Ethernet II 802.3

188

35011050 01 July 2006

TSX ETY 110

Configuration of the common words of the data module from station 2

Station 2 exchanges 16 common R/W words with the other PLCs connected to the network.

Ethway data

None

Common words R

Common words R/W

No. of words/

4 8

Bridge ...

16 32 64

Network address 5

The configuration required is: z the type of facility, z z the length of the common words, the network number.

35011050 01 July 2006

189

TSX ETY 110

Example of the ETHWAY architecture connected to TCP/IP

Introduction The following figure illustrates the implementation of a TSX ETY 110 data module in an ETHWAY architecture connected to a TCP/IP network.

Scheduler {1.3}

140.252.1.11

190

ETHERNET

Gateway

140.252.2.255

Network 1: 140.252 factory level

Programming terminal

{1.4}

140.252.2.4

Sub-network 140.252.2.0

cellular level

Station 2

ETHERNET

2

{1.2}

140.252.2.2

1 ETHWAY or TCP/IP TCP/IP communication

2 ETHWAY communication

1

Station 1

{1.1}

140.252.2.1

35011050 01 July 2006

Recommended method of use

TSX ETY 110 z z z z z

IP addressing is administrated globally, because it is connected to an existing factory TCP/IP network.

Communication between the PLCs, at the cellular level, is by means of ETHWAY facilities (COM, UNI-TE).

Communication between the PLC and the programming terminal, at the cellular level, makes use of ETHWAY facilities or UNI-TE on TCP/IP.

Communication between the PLC and the scheduler makes use of UNI-TE functionality on TCP/IP.

The format of the frames used is ETHERNET II.

Note: The ETHWAY functionality at cellular level is identical to the functionality described in the previous example. This example only describes the communication between the scheduler at factory level and a PLC Premium at cellular level.

Configuration of the local address of the data module from station 2

As it is necessary to administrate the IP addresses, configured IP address mode is selected.

IP address configuration

IP default address

Configured

IP address

Subnetwork mask

Gateway address

140 252 2

255 255 0

10

0

140 252 2 255

Client/Server configuration

You should enter the IP parameters listed below. These values are taken from the installation’s global addressing scheme managed by the network manager.

It is possible to ensure its uniqueness by having the network ID (140.252) assigned by an accredited body.

The network at cellular level is an IP sub-network. This permits the attribution of a unique network ID (140.252) for the whole of the architecture. The sub-networks are then defined by the user of the sub-network mask 255.255.0.0.

The class of address chosen (here class B) depends on the number of machines and the number of networks in the installation.

35011050 01 July 2006

191

TSX ETY 110

Configuration of the connections of the data module from station 2

You must input both the X-WAY address and the IP address of the devices with which the module must communicate.

Configuration of Connections

Connections allowed

5

Net.Sta

1.3

1.4

Access: control

3

4

1

2

IP address

140.252.1.11

140.252.2.4

Protocol

UNITE

UNITE

Access

Click on the Access control button to activate this control, then check off the corresponding box in the column Access

The maximum number of connections in the application can be adjusted.

ETHERNET configuration of the data module from station 2

The ETHERNET frame format selected for TCP/IP is Ethernet II because in the example the terminals use this format.

Ethernet Configuration

Ethernet II 802.3

192

35011050 01 July 2006

TSX ETY 110

Example of connection to a non private TCP/IP network

Introduction The following figure illustrates the implementation of a TSX ETY 110 data module connected to an existing TCP/IP network.

Scheduler Programming and debugging terminal

{1.3}

140.252.2.11

Gateway

140.252.2.255

{1.4}

140.252.2.9

{1.2}

140.252.2.10

1

ETHERNET TCP/IP

1

{1.1}

140.252.2.8

1

FIPWAY

1 TCP/IP Communication

Recommended method of use z z z z

IP addressing must be administrated because you are connecting to a non private TCP/IP network.

Communication between the PLCs makes use of the UNI-TE facilities on TCP/IP.

Communication between the PLC and the scheduler or the programming terminal makes use of UNI-TE facilities on TCP/IP.

The format of the frames used is ETHERNET II.

35011050 01 July 2006

193

TSX ETY 110

Configuration of the local address of the data module

The IP addresses must be set, Configured IP address is selected, you must enter the IP parameters.

IP address configuration

IP default address

Configured

IP address

Subnetwork mask

Gateway address

140 252 2

255 255 0

10

0

140 252 2 255

Client/Server configuration

Configuring the connections of the data module

You must input both the X-WAY address and the IP address of the devices with which the module must communicate.

Configuration of Connections

Connections allowed

5

Net.Sta

1.3

1.4

Access control

3

4

1

2

IP address

140.252.1.11

140.252.2.4

Protocol

UNITE

UNITE

Access

Click on the Access control button to activate this control, then check off the corresponding box in the column Access .

The maximum number of connections allowed in the application can be adjusted.

ETHERNET configuration of the data module

The ETHERNET frame format selected for TCP/IP is Ethernet II because in the example the terminals use this format.

Ethernet Configuration

Ethernet II 802.3

194

35011050 01 July 2006

TSX ETY 110

Example of communication between Premium and Quantum

Introduction The following figure illustrates the implementation of a TSX ETY 110 module to communicate with a Quantum PLC.

Programming and debugging terminal

{1.3}

140.252.2.11

Gateway

140.252.2.255

{1.101}

140.252.2.8

1 1

ETHERNET TCP/IP

Network 1 X-WAY

140.52

2

{1.2}

140.252.2.10

Modbus Plus

FIPWAY

Recommended method of use z z

The IP addressing is administrated because of the risk of duplicating IP addresses with default values.

Communication between the PLCs makes use of the Modbus facilities on

TCP/IP.

35011050 01 July 2006

195

TSX ETY 110

Configuration of the local address of the data module

The IP address must be set, Configured IP address is selected, you must enter the

IP parameters.

IP address configuration

IP default address

Configured

IP address

Subnetwork mask

Gateway address

140 252 2

255 255 0

10

0

140 252 2 255

Client/Server configuration

Configuring the connections of the data module

You must input both the X-WAY address and the IP address of the devices with which the module must communicate.

Configuration of Connections

Connections allowed

5

Net.Sta

1.3

1.101

Access control

3

4

1

2

IP address

140.252.2.11

140.252.2.8

Protocol

UNITE

MODBUS

Access

Click on the Access control button to activate this control, then check off the corresponding box in the column Access .

The maximum number of connections in the application can be adjusted.

Note: Communication with the Quantum PLC requires the configuration of the

Modbus protocol.

ETHERNET configuration of the data module

The ETHERNET frame format selected for TCP/IP is Ethernet II because in the example the terminals use this format.

Ethernet Configuration

Ethernet II 802.3

196

35011050 01 July 2006

TSX ETY 110

8.3

Debugging

Introduction

Subject of this sub-chapter

What's in this

Section?

This sub-chapter describes the debugging of the TSX ETY 110 module.

This section contains the following topics:

Topic

Module debugging screen

General debugging parameters

Debugging parameters for TCP/IP facilities

How to test TCP/IP communication with a Ping request

Debugging parameters of ETHWAY facilities

Requests available for the communication channel test

How to test a channel with Identification and Mirror requests

How to test a channel with requests

Page

198

200

201

202

203

204

205

207

35011050 01 July 2006

197

TSX ETY 110

Module debugging screen

Introduction

Illustration

This screen, split into five areas, is used to debug an ETHERNET link.

The screen dedicated to ETHERNET communication looks like this :

1

4

2

TSX SAY 110 [RACK 0 POSITION 5]

Debug

Designation : TCP/IP ETHWAY MODULE Version 2.0

RUN ERR

Station Address IP address

IP address

Subnetwork mask

Gateway address

196 211 185 22

255 255 255 0

196 211 185 55

Common data

Bridge

ADR

Network address 5

IP address module

Communication test

196.211.185.21

MAC address

Number of open 0

Ping

Response reception

Time

Size

Addresses

Message traffic (msg./min)

64

2000 ms

Bytes msg./min

Station test

Identification

Enter Request

Station no.

Counters

Reset counters

Mirror

Response reception

Message errors

ASCII words

None

DIAG...

Hex.

19

Reset counters

Min.

0 Avg.

0 Max.

0 Reset

Messages sent and not acknowledged

Messages refused

0

0

5

3

198

35011050 01 July 2006

Elements and functions

TSX ETY 110

This table describes the different areas that make up the configuration screen:

Address Area

1

2

3

4

5 common

Message traffic

(See Message

traffic, p. 200 )

Message errors

(See Message

errors, p. 200 )

TCP/IP facilities

(See Debugging parameters for

TCP/IP

facilities, p. 201 )

ETHWAY facilities (See

Requests available for the communication channel test,

p. 204 )

Function common section at the communication debugging screens

(Communication applications Volume 1 - Description of communication debugging screens) is used to view graphically the number of messages handled by the module: used to view the number of unacknowledged or refused messages.

used to : z z view configuration of TCP/IP facilities, test communication on the TCP/IP profile.

used to : z z view configuration of ETHWAY facilities, test communication on the ETHWAY profile.

35011050 01 July 2006

199

TSX ETY 110

General debugging parameters

Introduction

Message traffic

The general debugging parameters are grouped into two windows : z the Message traffic window, z the Message errors window.

The window looks like this :

Message traffic (msg./min)

6000 msg./min

Message errors

Min.

493 Avg.

849 Max.

1206 Reset

It shows graphically the number of messages per minute handled by the module

(sending and receiving).

This number can be compared to the maximum flow rate offered by the module

(7800 or 8400 messages of 128 bytes per minute) in order to determine whether the latter is working in a normal use range or in overload.

The Reset button resets to zero the three counters Min.

, Av.

and Max.

.

The window looks like this :

Message errors

Reset counters

Messages sent and not acknowledged

Messages refused

12

2

The message errors window shows the number of unacknowledged messages on

ETHWAY and the number of refused messages on ETHWAY or TC/IP.

You can reset these counters to zero by clicking on the Init counters button.

200

35011050 01 July 2006

TSX ETY 110

Debugging parameters for TCP/IP facilities

Introduction

IP Address

The debugging parameters for TCP/IP facilities are grouped in two windows : z the IP Address window, z the Communication test window.

The window looks like this :

IP address

IP address

Subnetwork mask

Gateway address

IP address module

196 211 185 22

255 255 255 0

196 211 185 55

MAC address

It shows the configuration data for the IP address: z z z

IP Address

Subnetwork mask

Gateway Address : gateway address

Communication test

The window looks like this :

Communication test

196.211.185.21

Number of connections open 0

Ping

Response reception

Time

Size 64 ms

Bytes

Addresses

This window is used to test the IP communication with another station registered in the table of remote devices.

35011050 01 July 2006

201

TSX ETY 110

How to test TCP/IP communication with a Ping request

Introduction

Steps to follow

This page indicates the procedure to be followed to test a TCP/IP communication by means of a Ping request.

The following procedure allows the sending of the Ping request and thus tests the routing of information between two devices.

Step

1

2

3

Action

Select the address of the station to be interrogated with the help of the

Addresses field.

Select the number of bytes to be transmitted using the Size field. This specifies the length of the message to be sent between 64 and 1472 bytes.

Press the button Ping .

Result

The reply appears in the field Time :

Response reception

Time

Size 64

17 ms

Bytes

The time returned corresponds to the turnaround time for the message in ms.

Type of response The following table groups together the different types of response to the Ping request.

If the response is… then … positive The window indicates the turnaround time for the message in ms.

negative z z a window with the message Timeout specifies the absence of response from the remote device.

a window with the message Host unreachable specifies that the remote device has not been reached in the network architecture.

202

35011050 01 July 2006

TSX ETY 110

Debugging parameters of ETHWAY facilities

Introduction

Station address

Station test

The debugging parameters for TCP/IP facilities are grouped in two windows : z the IP Address station window, z the Station test window.

The window looks like this :

Station Address

Network address 5

Common data

Bridge words

None

19

It shows the configuration data : z

Network address and Station : shows the network and station address coded z on the module’s code selectors

Common data : shows the type of facility selection in configuration mode for z common data

Bridge : if the box is checked off, it shows that the station has been registered as an X-WayBridge.

The window looks like this :

Station test

10

Identification Counters

Enter Request Reset counters

Mirror

Response reception

Station no.

ASCII Hex.

This window is used to test a communication channel by sending a request to one of the existing stations on the network.

35011050 01 July 2006

203

TSX ETY 110

Requests available for the communication channel test

Introduction

Test conditions

Available requests

This page describes the different possibilities for testing a communication channel from the debugging screen.

Sending a request to an unconnected station results in an error message.

Window Test station allows the following requests : z

Identification (See

How to identify a station, p. 205 ) : prompts the Identification

request to be sent to the designated remote station, z z z

Counters : prompts the sending of the request for the Reading of the error counters to the designated station,

Counters : prompts the designated station’s error counters to be reset to zero,

Request input (See

How to test a channel with requests, p. 207 ): allows a

z

UNI-TE request, other than those provided by the command buttons, to be sent to the designated station. The choices available in this function give access to a screen that allows you to select the parameters that are specific to the request

(request code must be coded in hexadecimal),

Mirror (See

How to send the Mirror request, p. 206 ): allows a mirror request to

be sent to the designated station. Selecting this function gives access to a screen that allows you to select the length of the character string to be sent (a maximum of 80 characters ). The PLC then sends this character string (ABCD….) to the destination device. This automatically sends the character string that was received back to the sender.

204

35011050 01 July 2006

TSX ETY 110

How to test a channel with Identification and Mirror requests

Introduction This page indicates the procedure to follow to test a communication channel by means of Identification and Mirror requests.

How to identify a station

The following procedure allows the identification of a designated station.

Step

1

2

Actions

Select the address of the station to be interrogated with the help of the field

Station .

Click on the button Identification .

Result

The response appears in the window Receive Response :

Response reception

..’.TSX ETY 110..!....

ASCII Hex.

35011050 01 July 2006

205

TSX ETY 110

How to send the

Mirror request

The following procedure allows the sending of the Mirror request and thus tests the routing of information between two devices.

Step

1

2

Action

Select the address of the station to be interrogated with the help of the field

Station .

Click on the button Mirror .

Result

The following window appears :

Mirror Request

Length of data to be sent 8

Send Cancel

3

4

Input the length of data to be sent (maximum 80 characters).

Click on the button Send .

Result

The response appears in the window Receive Response :

Response reception

ABCDEFGH

ASCII Hex.

The response contains: z the character string ABCDEFGH that corresponds to the length of data sent 8.

206

35011050 01 July 2006

TSX ETY 110

How to test a channel with requests

Introduction This page indicates the procedure to follow to test a communication channel from the debugging screen through different requests.

35011050 01 July 2006

207

TSX ETY 110

How to send a request

208

The following procedure allows a request, other than those provided by the command buttons, to be sent to a designated station. In this example, the request sent is used to read 10 words (from %MW1 to %MW10).

Step

1

2

Action

Select the address of the station to be interrogated with the help of the field

Station .

Click on the button Input Request .

Result

The following window appears :

Enter Request

Request code (hexadecimal)

Data (Hexadecimal)

680701000A00

36

3

4

5

Send Cancel

The data sent in this example is coded on 6 bytes.

Input the function code (coded in hexadecimal on one byte), corresponding to the request that you want to send.

For this example the read request code is 16#36.

Input the data to be sent by coding all the data in hexadecimal. The data is sent non-stop without any time intervals between them. When the data is coded on one word, the most significant and least significant bytes are reversed.

For this example the data is as follows : z 16#68 : on one byte, defines the segment (internal data), z z z

16#07 : on one byte, defines the object type (words),

16#0100 : on one byte, defines the first word to read,

16#0A00 : on one byte, defines the number of words to read.

Click on the button Send .

Result

The response appears in the Receive Response window :

Response reception

07 00 C2 92 20 24

Ascii Hexa

The response from the example has data on 21 bytes.

z 16#07 : corresponds to object type (words), z z

16#00C2 : corresponds to the value of the first word (the most significant and least significant bytes are reversed, its value is 16#C200),

...

35011050 01 July 2006

8.4

TSX ETY 110

Language objects associated with the

TSX ETY 110 module

Introduction

Subject of this sub-chapter

What's in this

Section?

This sub-chapter presents the different language objects specific to the

TSX ETY 110 module.

This section contains the following topics:

Topic

Implicit Exchange Language Objects

Language objects in explicit exchange

Explicit exchange management and report

Language objects associated with configuration

Page

210

213

215

216

35011050 01 July 2006

209

TSX ETY 110

Implicit Exchange Language Objects

At a Glance

Bit Objects

This page describes all the implicit exchange (Communication applications Volume

1 - Default exchanges) language objects for ETHERNET communication with the

TSX ETY 110 module that can be displayed or modified by the application program.

The table below shows the various bit objects for implicit exchange.

Object (1)

%Ixy.MOD.E

RR

Function

Module error bit

%Ixy.i.ERR

Channel error bit

Meaning

This bit set to 1 indicates a module error (at least one of the channels has an error, for instance)

This bit set to 1 indicates a line fault.

Legend

(1) Address xy.i

z x: corresponds to the rack number z z y: corresponds to the module number i: corresponds to the channel number

210

35011050 01 July 2006

Word Objects

TSX ETY 110

The table below shows the various word objects for implicit exchange.

Object (1)

%IWxy.i.0

%IWxy.i.1

...

%IWxy.i.4

Function

Network status

Common data update indicators

...

Common data update indicators z z z z z z z z z z z z

...

Meaning z x0 = 1: if common words are received from at least one of the remote stations x0 = 1: station 0 common words are updated.

...

x7 = 1: station 7 common words are updated.

x8 = 1: station 8 common words are updated.

...

x15 = 1: station 15 common words are updated.

x0 = 1: station 48 common words are updated.

...

x7 = 1: station 55 common words are updated.

x8 = 1: station 56 common words are updated.

...

x15 = 1: station 63 common words or shared table words are updated.

Legend

(1) Address xy.i

z x: corresponds to the rack number z z y: corresponds to the module number i: corresponds to the channel number

35011050 01 July 2006

211

TSX ETY 110

Common Words Common words are exchanged on the ETHWAY profile and their number depends on the size of words per configured station.

The following table describes the common words:

Object (1)

%NW{n.s}0 to

%NW{n.s}64

Function

Common words

Meaning corresponds to exchanged common data

Legend

(1) Address n.s

z n: corresponds to the network number z s: corresponds to the station number

WARNING

The update bit switches to 1 at the beginning of the PLC cycle if it receives common words from the corresponding station. At the end of the cycle the update bits automatically return to 0.

Consequently, common words can only be considered valid if the update bit of the corresponding station is set to 1.

After power up, common words are set to value 0.

Failure to follow this precaution can result in death, serious injury, or equipment damage.

212

35011050 01 July 2006

TSX ETY 110

Language objects in explicit exchange

Introduction

Word objects

35011050 01 July 2006

This page describes all the language objects for explicit exchange (Communication applications Volume 1 - Specified exchanges: General points) for ETHERNET communication with the TSX ETY 110 module that can be displayed or modified by the application program.

The table below shows the different word objects for explicit exchange.

Object (1) Function

%MWxy.MOD.2 Module status

%MWxy.i.2

%MWxy.i.3

%MWxy.i.4

Standard channel status

Specific channel status z z z z z z z z

Meaning x0 = 1 : defective module x1 = 1 : functional error (error between the processor and the module, adjustment or configuration error, …) x2 = 1 : terminal block fault (not connected) x3 = 1 : self-tests running x4 = 1 : reserved x5 = 1 : error in hardware or software configuration (the module present is not that declared in the configuration, the sub-modules are not compatible) x6 = 1 : missing module x7 = 1 : error in one of the sub-modules z z z z x0 à x3 = 0 : reserved x4 = 1 : module error or self-tests running x5 et x6 = 0 : reserved x7 = 1 : application error (error in the configuration)

Byte 0 : z x0 = 1 : if X-WAY bridge (0 if not bridge)

Byte 1 : number of TCP connections open

Unacknowledged messages on ETHWAY

%MWxy.i.5

%MWxy.i.6

%MWxy.i.7

Error counters on

ETHWAY

Error counters on

ETHWAY

Network/station address

Information on common words or shared tables

Refused messages on ETHWAY

Byte 0 : station number

Byte 1 : network number

Byte 0 : z = 16#00 : inactive facility z = 16#01 : read/write of common words z = 16#02 : reading of common words

Byte 1 : size of common words produced

213

TSX ETY 110

Object (1)

%MWxy.i.8

%MWxy.i.9

and %Mwxy.i.10

%MWxy.i.11

and %Mwxy.i.12

Function

Counter of messages on TCP/IP

Message counters on the link level

Message counters on the link level

Meaning

Number of messages refused on X-WAY on TCP/IP

Number of messages received on the link level

Number of messages sent on the link level

Key

(1) Address xy.i

z x : corresponds to the rack number z z y : corresponds to the module number i : corresponds to the channel number

214

35011050 01 July 2006

TSX ETY 110

Explicit exchange management and report

Introduction

Word objects

This page describes all the language objects that manage explicit exchanges

(Communication applications Volume 1 - Exchange and report management).

The table below shows the different word objects for the management of explicit exchanges.

Object (1) Function

%MWxy.MOD.0 Module exchanges in progress

%MWxy.MOD.1 Module report

%MWxy.i.0

%MWxy.i.1

Channel exchanges in progress

Channel report z z z z

Meaning z z z x0 = 1 : status reading in progress x1 = 1 : sending of command parameters to the communication module x2 = 1 : sending of adjustment parameters to the communication module x1 = 0 : command parameters received and accepted by the module x2 = 0 : adjustment parameters received and accepted by the module z z z x0 = 1 : status reading in progress x1 = 1 : sending of command parameters to the communication channel x2 = 1 : sending of adjustment parameters to the communication channel x1 = 0 : command parameters received and accepted by the communication channel x2 = 0 : adjustment parameters received and accepted by the communication channel

Key

(1) Address xy.i

z x : corresponds to the rack number z z y : corresponds to the module number i : corresponds to the channel number

35011050 01 July 2006

215

TSX ETY 110

Language objects associated with configuration

Introduction

Internal constants

This page describes all the configuration language objects for ETHERNET communication with the TSX ETY 110 module that can be displayed by the application program.

The following table describes the internal constants:

Object Function

%KWxy.i.0

Type

%KWxy.i.1

Physical layer

%KWxy.i.2

Supported facilities

%KWxy.i.4

Common words

%KWxy.i.5

%KWxy.i.6

X-WAY network address

Type of ETHERNET driver for TCP/IP

%KWxy.i.7

TCP/IP configuration : address type

%KWxy.i.8

and

%KWxy.i.9

Local IP address

Meaning

Byte 0 = 11 for ETHWAY communication

Byte 1 : reserved

Byte 0 : reserved

Byte 1 : reserved

Byte 0 : common data z x0 = 1 : activation of ETHWAY common words z z z x1 = 0 : reserved x2 = 1 : common read only words x3 = 1 : common R/W words z x4 to x7 = 0 : reserved

Byte 1 : reserved

Byte 0 : number of common words

Byte 1 : reserved

Byte 0 : network number (0 by default)

Byte 1 : reserved

Byte 0 : z = 16#00 : AUI (default value) z = 16#01 : RJ45

Byte 1 : z = 16#00 : ETHERNET II (default value) z = 16#01 : 802.3

Byte 0 : reserved

Byte 1 : inherited address z = 16#00 : default address z z

= 16#01 : from the application-specific function

= 16#03 : from a server

Example with the address 139.160.650.109

Byte 0 = 109 (least significant bit)

Byte 1 = 65

Byte 2 = 160

Byte 3 = 139 (most significant bit)

216

35011050 01 July 2006

TSX ETY 110

Object

%KWxy.i.10

and

%KWxy.i.11

%KWxy.i.12

and

%KWxy.i.13

Function

IP address of gateway Example with the address 139.160.65.1

Byte 0 = 1

Byte 1 = 65

Byte 2 = 160

Byte 3 = 139

Subnetwork mask

Meaning

Example with the address 255.255.255.0

Byte 0 = 0

Byte 1 = 255

Byte 2 = 255

Byte 3 = 255

35011050 01 July 2006

217

TSX ETY 110

218

35011050 01 July 2006

TSX ETY 410•, TSX ETY PORT,

TSX ETY 510• and TSX WMY 100 modules

9

At a Glance

Aim of this

Chapter

What's in this

Chapter?

This chapter describes how to install TSX ETY 410•, TSX ETY PORT,

TSX ETY 510• and TSX WMY 100 modules.

The TSX WMY module offers the same services than the other modules, except the following ones : z z z z

IO Scanning,

Global Data,

Address server,

Bandwidth Monitoring.

This chapter contains the following sections:

Section Topic

9.1

General

9.2

9.3

9.4

Configuration

Debugging

9.5

Language objects associated with TSX ETY 410•, TSX ETY PORT,

TSX ETY 510• and TSX WMY 100 Modules

Questions/Answers

Page

220

234

265

278

286

219

35011050 01 July 2006

TSX ETY 410•, TSX ETY PORT, TSX ETY 510• and TSX WMY 100

9.1

General

At a Glance

Aim of this

Section

What's in this

Section?

This section introduces ETHERNET communication from a TSX ETY 410• ,

TSX ETY PORT, TSX ETY 510• or TSX WMY 100 module, and their properties.

The TSX WMY module offers the same services than the other modules, except the following ones : z

IO Scanning, z z z

Global Data,

Address server,

Bandwidth Monitoring.

This section contains the following topics:

Topic

General

Characteristics

Type of Supported Connections

Performance of IO Scanning Utility

Global Data Utility Performances

Operating Modes for TSX ETY 410•, TSX ETY PORT, TSX ETY 510• and

TSX WMY 100 Modules

Page

221

222

225

227

230

232

220

35011050 01 July 2006

TSX ETY 410•, TSX ETY PORT, TSX ETY 510• and TSX WMY 100

General

At a Glance The communication channel of the ETHERNET TSX ETY 410•/PORT/510• or

TSX WMY 100 module offers connection to a TCP/IP network supporting the UNI-

TE messaging utility and Modbus on a TCP/IP profile.

The four modules, TSX ETY 410• , TSX ETY PORT also offer the following utilities: z z

Thanks to their SNMP agent functionality, the modules can be supervised by one or two SNMP managers.

They are able to perform the role of the BOOTP/DHCP server or the BOOTP client (no address server for TSX WMY 100).

z z z z

Using their IO Scanning utility, they can drive remote inputs/outputs on the

ETHERNET network (no IO Scanning for TSX WMY 100).

They integrate an embedded HTTP server.

Thanks to the Global Data utility, the modules allow the exchange of data between IEC standard PLC stations (no Global Data for TSX WMY 100).

The Bandwidth monitoring utility, which makes it possible to check how resources are shared between the utilities on the module (no Bandwidth Monitoring for

TSX WMY 100).

z

The Replace faulty device utility, which allows the device configuration to be saved in the module. In case of breakdown, another installed blank module can be restarted with the configuration parameters of the previous one.

The time synchronization utility makes it possible to update the PLC clocks to z

UTC (Universal Time Coordinated) from a data source.

In addition, the TSX ETY 510• and TSX WMY 100 modules offer the option of creating user Web pages.

35011050 01 July 2006

221

TSX ETY 410•, TSX ETY PORT, TSX ETY 510• and TSX WMY 100

Characteristics

Maximum

Capacity of the

Module

The maximum frame size depends on the type of transaction: z

In synchronous messaging, the maximum frame size is 256 bytes.

z

In asynchronous messaging, the maximum frame size is 1 KBytes.

TSX ETY 410•, TSX ETY PORT, TSX ETY 510• and TSX WMY 100 modules allow you: z z to manage 64 TCP connections using the port 502 messaging utility, to scan up to a maximum of 64 devices using the IO Scanning utility (No IO z

Scanning for TSX WMY 100), to act as the DHCP or BOOTP server for a maximum of 96 devices requiring this utility (No Address server for TSX WMY 100),

In conjunction with a processor dedicated to this sort of handling, the module can be used: z for synchronous X-WAY messaging on TCP/IP (UNI-TE server): 800 messages per second z in the case of asynchronous X-WAY messaging on TCP/IP: between 600 and

1200 messages per second

These numbers vary depending on the size of the messages, the number of clients and the application execution time.

222

35011050 01 July 2006

TSX ETY 410•, TSX ETY PORT, TSX ETY 510• and TSX WMY 100

IO Scanning

Utility

Note: No IO Scanning for TSX WMY 100

The module can scan a maximum of 64 remote devices.

For the same station, the application can process: z z a maximum total volume of inputs to be scanned of 2 Kwords, a maximum total volume of outputs to be scanned of 2 Kwords.

When using the IO Scanning utility, the PLC cycle is impacted by about 1 ms per volume of 512 I/O words scanned.

In the same way, the size of the application is impacted by 6 KBytes per configured

TSX ETY 410•/PORT/510• module.

Global Data

Utility

Note: No Global Data for TSX WMY 100

The user interface is a %MW zone defined in configuration.

z z

Each module can issue a variable of between 1 and 512 words,

Each module can subscribe to 1 to 64 variables. The total data cannot exceed 2

Kwords.

Time synchronization service

The time synchronization service is available on the TSX ETY 5103 with a processor version of V5.8 or later and PL7 version V4.5.

Replace Faulty

Equipment

The module reserves a 512 KBytes zone for this function.

z z

Up to 96 remote devices can be configured in the DHCP address server utility.

The 96 remote devices should share the 512 KBytes reserved for their parameters.

35011050 01 July 2006

223

TSX ETY 410•, TSX ETY PORT, TSX ETY 510• and TSX WMY 100

Compatibility The modules TSX ETY 410• , TSX ETY PORT and TSX ETY 510• are based on the modules TSX ETY 410 and TSX ETY 5101 . They have new utilities, yet remain compatible with TSX ETY 410 and TSX ETY 5101 modules.

The TSX ETY 410• , TSX ETY PORT and TSX ETY 510• modules can only be configured in a Premium with a V5.1 or higher processor.

The functional level of the TSX ETY 410•/510• modules requires version V4.1 of the

PL7 software. For the TSX ETY PORT, version V4.3 of the PL7 software is required with a version V5.5 processor or higher. Otherwise (PL7 V4.0, TSX ETY 410/5101), the new utilities (Global data, Bandwidth monitoring, DHCP server) will not be available.

Note: If the module physically present is a TSX ETY 410 or a TSX ETY 510 and the configured module is a TSX ETY 410•, the application will function normally if the utilities of the TSX ETY 410• are not used. Otherwise, the module will remain faulty.

224

35011050 01 July 2006

TSX ETY 410•, TSX ETY PORT, TSX ETY 510• and TSX WMY 100

Type of Supported Connections

At a Glance Number of maximal HTTP connections.

TSX ETY 410•

TSX ETY PORT

TSX ETY 510•

TSX WMY 100

8

8

16

16

The TSX ETY 410•/PORT/510• and TSX WMY 100 modules authorize a maximum of 64 parallel connections on TCP/IP.

Connection to a

Premium

Between two Premium PLCs using UNI-TE messaging on the TCP/IP profile, the

TSX ETY 410•/PORT/510• or TSX WMY 100 module only allows one connection in client/server mode.

ETHERNET

A UNI-TE client/server messaging connection

Premium with a

TSX ETY 410•/PORT/510• module or TSX WMY 100.

Premium with a

TSX ETY 410•/PORT/510• or

TSX ETY 110 module

35011050 01 July 2006

225

TSX ETY 410•, TSX ETY PORT, TSX ETY 510• and TSX WMY 100

Connection to a

Quantum

Between a Premium PLC and a Quantum PLC using Modbus messaging on the

TCP/IP profile, the TSX ETY 410•/PORT/510• or TSX WMY 100 module allows: z z a single connection in Modbus client mode, a single connection in Modbus server mode.

Example

ETHERNET

A Modbus client messaging connection

Connection to a

Third Party

Device

Premium with a

TSX ETY 410•/PORT/510• module or TSX WMY 100.

A Modbus server messaging connection

Quantum

Between a Premium PLC and a third party device, the TSX ETY 410•/PORT/510• and TSX WMY 100 module allows: z a single connection in UNI-TE or Modbus client mode, z several connections in UNI-TE or Modbus server mode.

Example

ETHERNET

A UNI-TE or Modbus messaging connection in client mode

Premium with a

TSX ETY 410•/PORT/510• module or TSX WMY 100.

Several UNI-TE or Modbus messaging connections in server mode with different

X-WAY addresses

PC (third party device)

226

35011050 01 July 2006

Performance of IO Scanning Utility

TSX ETY 410•, TSX ETY PORT, TSX ETY 510• and TSX WMY 100

At a Glance

Restart Time for an IO Scanning

Configuration

This time corresponds to the time between the power up of the complete configuration and the moment when all the remote inputs/outputs become operational (the status bits are activated, the word bits %IWxy.i.l to %IWxy.i.4 = 1).

Values are given in seconds: z

T= 35s, if the TSX ETY 410•/PORT/510• module is used as a BOOTP server to z connect the scanned devices.

T = 17s, if the scanned devices use another BOOTP/DHCP server.

Input/Output

Restart Time

Note: No IO Scanning for TSX WMY 100

The performances presented below are the performances of module

TSX ETY 410•/PORT/510• while using the IO Scanning utility.

This time corresponds to the time between the power up of the remote inputs/ outputs and the moment when all the status bits are activated (word bits %IWxy.i.l to %IWxy.i.4 = 1).

The value is given in seconds: z

T = 5 s

35011050 01 July 2006

227

TSX ETY 410•, TSX ETY PORT, TSX ETY 510• and TSX WMY 100

Application

Response Time

This time corresponds to the elapsed time between the acquisition of a remote input and the positioning of a remote output.

This is a logic response time, which does not take filtering time and actuator and sensor interface response times into account.

This is an example of time elapsed from acquiring an input to the positioning of an output:

I

1

O

1

MAST cycle time:

20 ms or 80 ms

I

1

Response time

O

1

228

35011050 01 July 2006

220

210

200

190

180

170

0

100

90

80

70

60

50

0

TSX ETY 410•, TSX ETY PORT, TSX ETY 510• and TSX WMY 100

Response time with a cycle of 20 ms

Max. T

10 20 30

Response time with a cycle of 80 ms

Min. T

40 50 60

Number of devices scanned

Max. T

Min. T

10 20 30 40 50 60

Number of devices scanned

35011050 01 July 2006

229

TSX ETY 410•, TSX ETY PORT, TSX ETY 510• and TSX WMY 100

Global Data Utility Performances

At a Glance

Definition

Note: No Global Data for TSX WMY 100

The values presented below are given to evaluate the Global Data utility performance.

Global Data return time :

This time corresponds to the time elapsed between the publication of a variable value by the local PLC application, the subscription by a remote PLC application, the publication of the same value by the remote PLC application and the subscription by the local PLC application.

230

35011050 01 July 2006

Values

60

50

40

30

20

10

TSX ETY 410•, TSX ETY PORT, TSX ETY 510• and TSX WMY 100

Measurement conditions: z z

The cycle time for local and remote PLC applications are identical.

Only one variable is exchanged in each direction.

Result:

PLC cycle time

>= 10 ms

= 5 ms

Illustration:

Return time

3 times the PLC cycle time

5 to 6 times the PLC cycle time

0 5 10 15

Cycle time in ms

20

35011050 01 July 2006

231

TSX ETY 410•, TSX ETY PORT, TSX ETY 510• and TSX WMY 100

Operating Modes for TSX ETY 410•, TSX ETY PORT, TSX ETY 510• and

TSX WMY 100 Modules

At a Glance The following diagram describes the TSX ETY 410•/PORT/510• and TSX WMY 100 module operating modes.

General Diagram

Stop module Module off

Power up

Operation

Module configured Communication function

Module in self-test phase

Reset

Configuration Module not configured

Self-tests OK z z z z

After power-up, the module carries out self-testing. During this phase, the

STS LED is lit. After the self tests, the RUN LED lights up.

The module does not operate with a default configuration. This has to be transmitted to it by the local PLC’s PL7 application.

The configuration values are given in the %KW language object list and in particular provide the IP address and the X-WAY address of the module.

The configuration is retransmitted upon every PLC restart (warm or cold).

When the configuration is received, the module resets the current communication to zero before configuring itself (terminates current exchanges, shuts down TCP connections).

The module is now operational. The RUN and STS LEDs are lit up.

The IO Scanning function starts when the PLC transfers to RUN mode. It stops when it transfers to STOP mode.

232

35011050 01 July 2006

Special Cases

TSX ETY 410•, TSX ETY PORT, TSX ETY 510• and TSX WMY 100

If a TSX ETY 410•/PORT/510• or TSX WMY 100 module is not configured in the PL7 application (RUN LEDs go out and ERR LEDs flash), it takes the IP address constructed from its MAC address:

085.016.xxx.yyy where xxx and yyy are the last two numbers of the MAC address.

Example

The module’s MAC address is (in hexadecimal): 00 80 F4 01 12 20

In this case the default IP address is (in decimal): 085.016.018.032

The module also transmits BOOTP/DHCP requests to obtain another IP address.

These requests are sent until a BOOTP/DHCP server responds or until configured via PL7.

If the module detects a duplicated IP address, the STS LED flashes 4 times during a minute (as does that of the module having the same IP address).

35011050 01 July 2006

233

TSX ETY 410•, TSX ETY PORT, TSX ETY 510• and TSX WMY 100

9.2

Configuration

At a Glance

Aim of this

Section

What's in this

Section?

This section describes the implementation of the TSX ETY 410•, TSX ETY PORT,

TSX ETY 510• or TSX WMY 100 modules during its configuration.

The TSX WMY module offers the same services than the other modules, except the following ones : z

IO Scanning, z z z

Global Data,

Address server,

Bandwidth Monitoring.

This section contains the following topics:

Topic

Migration of Applications using TSX ETY 410/5101 Modules

Module Configuration Screen

Type of Communication According to Connection Configuration

Configuration of TCP/IP Messaging

IO Scanning Utility Configuration

BOOTP Server Configuration

DHCP Address Server Configuration

Configuring the Global Data Utility

Configuration of the SNMP Utility

Configuring the Time Synchronization Service

Configuring the Bandwidth Utility

Configuration of the Bridge Function

Page

235

236

238

243

245

248

250

252

255

257

262

264

234

35011050 01 July 2006

TSX ETY 410•, TSX ETY PORT, TSX ETY 510• and TSX WMY 100

Migration of Applications using TSX ETY 410/5101 Modules

Procedure To migrate an application based on a TSX ETY 410/5101 , to an application based on a TSX ETY 410•/PORT/510• in order to benefit from the new utilities, follow the procedure below:

Step

1

2

3

4

Action

Make sure you have: z PL7 version V4.1 or higher (V4.3 for a TSX ETY PORT), z z a processor of V5.1 version or higher (5.5 for a TSX ETY PORT), a TSX ETY 410•/PORT/510• module.

Open the application in the PL7 software.

Click on the TSX ETY 410 or TSX ETY 5101 module in configuration mode:

In the Module Utilities zone, certain utilities are grayed out.

Click on New utilities :

Illustration

Module utilities

IO Scanning

Address Server

Global Data

Bandwidth

New utilities

The application recognizes the modification. The new utilities are now accessible.

35011050 01 July 2006

235

TSX ETY 410•, TSX ETY PORT, TSX ETY 510• and TSX WMY 100

Module Configuration Screen

At a Glance

Illustration

2

3

This screen, separated into two zones, allows the declaration of the communication channel and the configuration of the necessary parameters for an ETHERNET link.

1

The screen dedicated to ETHERNET communication is displayed as follows:

TSX ETY 410 [RACK 0 POSITION 2]

Configuration

Designation: TCP/IP 10/100 MODULE

4

5

Module IP address

IP address Subnetwork mask

139, 160, 234, 18 255 , 255 , 255 , 0

Gateway address

139 , 160, 234,1

Module utilities

IO Scanning

Address Server

Global Data

Bandwidth

Messaging

XWAY address

Network

I/O Scanning Address Server

10

Ethernet configuration

Ethernet II

Station

IP address configuration

Configured

IP address

Subnetwork mask

Gateway address

139 160 234 18

255 160 255 0

139 160 234 1

Client/Server configuration

40

802.3

SNMP Global Data Bandwidth Bridge

7

8

9

10

3

4

1

2

5

6

11

12

Configuration of Connections

Xway

Addr.

5.123

4.15

IP address

4.10

139.160.234.10

4.11

139.160.234.11

5.121

4.12

4.13

139.160.234.21

139.160.234.12

139.160.234.13

5.122

139.160.234.22

139.160.234.23

139.160.234.14

Access control

Protocol Access

UNITE

UNITE

MODBUS

UNITE

UNITE

MODBUS

UNITE

UNITE

UNITE

UNITE

Mode

MULTI

MONO

MULTI

MULTI

MONO

MULTI

MULTI

MONO

MONO

MONO

MONO

MONO

6

7

10

9

8

236

35011050 01 July 2006

Elements and

Functions

TSX ETY 410•, TSX ETY PORT, TSX ETY 510• and TSX WMY 100

This table describes the different zones, which make up the configuration screen:

Zone common specific

6

7

2

3

Address Function

1 common part of the configuration screens (Communication applications Volume 1 - Overwiew of configuration screen) for communicating allows the display of the module address.

allows configuration of the TCP/IP utilities. See Configuration

parameters for TCP/IP facilities, p. 134 .

4

5 allows configuration of the IO Scanning utility (except TSX WMY

100). See Configuration parameters for the IO Scanning facility,

p. 141

.

allows configuration of the address server (except TSX WMY 100).

See Configuration Parameters for the Address Server Utility,

p. 147

.

8

9

10 allows selection of the utilities used by the module.

allows configuration of the SNMP utility. See Configuration

parameters for the SNMP facility, p. 150

.

allows configuration of the Global Data utility (except TSX WMY

100). See Configuration Parameters of the Global Data Utility,

p. 154

.

allows configuration of the Bandwidth management utility (except

TSX WMY 100).

allows configuration of the module in Bridge.

the time synchronization utility (See Configuration Parameters

Linked to the Time Synchronization Service (NTP), p. 160 ) is

configured from Web pages built into the Ethernet module.

35011050 01 July 2006

237

TSX ETY 410•, TSX ETY PORT, TSX ETY 510• and TSX WMY 100

Type of Communication According to Connection Configuration

At a Glance Depending on the connection configuration of the TSX ETY 410•/PORT/510• or

TSX WMY 100 module, you can carry out messaging: See Connection configuration

parameters, p. 138

z in mono-connection z in multi-connection.

According to the type of protocol and access control management, multi-connection mode requires a specific configuration of the correspondence table.

Note: In the following, only examples of multi-connection will be dealt with.

Furthermore, the emphasis is placed on communication between the module and a remote PC device containing several applications.

Configuration

Rules

Several connections can be configured with the same IP address. They must be defined with the same protocol, the same access rights, and the same connection mode.

In the case of a Modbus connection, only two connections can be configured with the same IP address. Addresses associated with these connections are: z z an X-WAY address (for example: {2.103}) for the Modbus client connection, an X-WAY address equal to {x.x} for Modbus server connections.

238

35011050 01 July 2006

TSX ETY 410•, TSX ETY PORT, TSX ETY 510• and TSX WMY 100

Multi-connection in UNI-TE

Protocol with

Access

Management

In this example, the PC contains four applications with a unique X-WAY address and one single IP address: z z

The module opens a connection and communicates with the server application with the address {1.1}.

Each of the other client applications with the address {1.2}, {1.3}, {1.4} is authorized to open a connection and communicate with the module.

Exchanges are carried out according to the UNI-TE protocol and the module’s access control utility is enabled.

Premium client/ server

139.160.65.157

Server application

{1.1}

Client application

{1.2}

139.160.65.156

Client application

{1.3}

Client application

{1.4}

PC

In order to implement this example, you must: z activate connection management by checking the module’s Access control box, z configure communication from the module to the PC’s server application in the table z z z z

X-WAY address : 1.1

IP address : 139.160.65.156

Protocol : UNI-TE

Access : authorized (cell checked) z z

Mode : Multi configure communication of each of the PC’s client applications to the server module in the table: z

X-WAY address : 1.2 and 1.3 and 1.4

z z

IP address : 139.160.65.156

Protocol : UNI-TE z z

Access : authorized (cell checked)

Mode : Multi

35011050 01 July 2006

239

TSX ETY 410•, TSX ETY PORT, TSX ETY 510• and TSX WMY 100

Multi-connection in UNI-TE protocol without access management

This example is the same as the previous one, except that access control is not configured.

In this case, if the application {1.1} is the only server application, the module’s correspondence table only contains the following line: z z z z z

X-WAY address : 1.1

IP address : 139.160.65.156

Protocol : UNI-TE

Access : the cell is grayed out

Mode : Multi

240

35011050 01 July 2006

TSX ETY 410•, TSX ETY PORT, TSX ETY 510• and TSX WMY 100

Multi-connection in Modbus

Protocol with

Access

Management

In this example, the PC contains four applications. The server application has an imaginary X-WAY address and the other client applications do not need an X-WAY address: z

The module opens a connection and communicates with the server application with the imaginary address {1.103}.

z

Each of the client applications has no address but is authorized to open a connection and communicates with the module.

Exchanges are carried out according to the Modbus protocol and the module’s access control utility is enabled.

139.160.65.156

Premium client/ server

139.160.65.157

Server application

{1.103}

Client application

Client application}

Client application

PC

In order to implement this example, you must: z z activate connection management by checking the module’s Access control box, configure communication from the module to the PC’s server application in the table z

X-WAY address : 1.103 (address between 100 and 163) z z

IP address : 139.160.65.156

Protocol : Modbus z z z

Access : the cell is grayed out

Mode : Multi configure communication of all the PC’s client applications to the server module in the table: z z z

X-WAY address : x.x (this address allows you to specify that other applications exist for the same IP address)

IP address : 139.160.65.156

Protocol : Modbus z z

Access : authorized (allows you to specify that other applications are authorized to connect and communicate)

Mode : Multi

35011050 01 July 2006

241

TSX ETY 410•, TSX ETY PORT, TSX ETY 510• and TSX WMY 100 z z z z

Note: If you want to prevent connection by client applications you must configure z X-WAY address : x.x (this address allows you to specify that other applications exist for the same IP address)

IP address

Protocol

Access

Mode

: 139.160.65.156

: Modbus

: not authorized (cell unchecked)

: Multi

Multi-connection in Modbus protocol without access management

This example is the same as the previous one, except that access control is not configured.

In this case, if the application {1.103} is the only server application, the module’s correspondence table only contains the following line: z z z z z

X-WAY address : 1.103

IP address : 139.160.65.156

Protocol : Modbus

Access : the cell is grayed out

Mode : Multi

242

35011050 01 July 2006

TSX ETY 410•, TSX ETY PORT, TSX ETY 510• and TSX WMY 100

Configuration of TCP/IP Messaging

At a Glance In order to use the TSX ETY 410•/PORT/510• or TSX WMY 100 module to communicate on ETHERNET, it is necessary to adjust the messaging configuration parameters (See

Configuration parameters for TCP/IP facilities, p. 134 ).

How to Access the Messaging

Step

1

2

The procedure for accessing the configuration parameters for TCP/IP utilities is as follows.

Action

Access the module configuration screen.

Select the Messaging tab.

Result

Messaging I/O Scanning Address Server

SNMP

XWAY address

Global Data Bandwidth

Configuration of connections

Access control

Network 10

IP address configuration

Configured

IP Address

Subnetwork mask

Gateway Address

139 160 234 18

255 160 255 0

139 160 234 1

Client/Server configuration

Ethernet Configuration

Ethernet II

Station 40

802.3

1

2

3

4

5

6

7

8

9

10

11

12

XWAY

Addr.

IP Address

4.10

139.160.234.10

4.11

139.160.234.11

5.121

4.12

4.13

5.122

139.160.234.22

5.123

4.15

139.160.234.21

139.160.234.12

139.160.234.13

139.160.234.23

139.160.234.14

Protocol

UNITE

UNITE

UNITE

MODBUS

MODBUS

UNITE

UNITE

UNITE

UNITE

UNITE

Access

Bridge

Mode

MULTI

MONO

MULTI

MULTI

MONO

MULTI

MULTI

MONO

MONO

MONO

MONO

MONO

35011050 01 July 2006

243

TSX ETY 410•, TSX ETY PORT, TSX ETY 510• and TSX WMY 100

How to Configure

Messaging

The following procedure gives the configuration principles.

Start of messaging configuration

Enter the X-WAY Address by filling in the numbers relating to the network and station

Fill in the fields of the connection table for each remote server device

X-WAY Addr.

IP Address

Protocol

Mode

If the module is a server, do you want to set access control?

No

Yes Select the check box

Access control

In the connection table, select the

Access check box of each remote client device

Select the box

Configured

Is the module a BOOTP client?

Yes

Select the box

Client/Server configuration

No

Fill in the fields

IP Address

Subnetwork mask

Gateway Address

Select the

ETHERNET configuration

End of messaging configuration

244

35011050 01 July 2006

IO Scanning Utility Configuration

TSX ETY 410•, TSX ETY PORT, TSX ETY 510• and TSX WMY 100

At a Glance

Note: No IO Scanning for TSX WMY 100

In order to use the TSX ETY 410•/PORT/510• module to control remote I/Os, it is necessary to adjust the configuration parameters of the IO Scanning utility.

How to Access

IO Scanning

Step

1

2

The procedure for accessing the configuration parameters for the IO Scanning utility is as follows.

Action

Access the module configuration screen.

In the Module utilities zone select the IO Scanning check box.

3

Illustration

Module utilities

IO Scanning

Address Server

Global Data

Bandwidth

The IO Scanning tab is no longer grayed out.

Select the IO Scanning tab.

Result

Messaging ID Scanning Address Server

Input fallback

Fallback to 0

Maintain

Scanning adjustment (ms)

Slow:

750

Normal:

105

Fast:

10

Scanned peripherals

IP address Unit

139.160.234.30

139.160.234.31

139.160.234.32

139.160.234.33

139.160.234.34

139.160.234.35

139.160.234.36

ID

255

0

88

22

10

10

233

Repetitive rate

FAST

NORMAL

SLOW

NORMAL

NONE

NORMAL

FAST

FAST

NORMAL

NONE

Master

RD ref.

282

304

305

314

322

322

344

Slave

RD ref.

0

20

40

60

80

23

56

RD count

22

01

22

125

9

8

0

SNMP

From 0

Global Data to 468

Bandwidth

Write Ref.

From

Master

WR ref.

0

32

132

148

150

159

181

Slave

WR ref.

100

200

300

400

50

700

800

WR count

32

100

16

2

9

22

0

Description

Device number 1

Device number 2

Momentum

0

Bridge to 180

35011050 01 July 2006

245

TSX ETY 410•, TSX ETY PORT, TSX ETY 510• and TSX WMY 100

How to Configure

IO Scanning

The following procedure gives the configuration principles for the IO Scanning utility.

Step

1

2

3

6

7

4

5

8

9

10

11

Action

Select the Input fallback mode.

If they are used, set the scanning periods (See

Adjusting the scanning, p. 144

) to: z the Normal period, z the Slow period.

Set the address of the beginning of the internal words (See Master %MW

fields, p. 144 ) (in the application memory) which are dedicated to I/O scanning:

z z

Read Ref.

Write Ref.

For each device, enter the IP address .

Enter for each device, if necessary, the Unit ID (See The IP Address and Unit

ID fields, p. 145 ) Modbus slave address.

For each device, select the period in which it will be scanned.

For each device, enter the read destination address in Slave RD ref.

(See

Slave RD ref. and slave WR ref., p. 146

).

For each device, enter the number of words to be sent in read format in

RD count (See

RD count and WR count, p. 146

).

For each device, enter the read destination address in Slave WR ref.

(See

Slave RD ref. and slave WR ref., p. 146

).

For each device, enter the number of words to be sent in write format in

WR count (See

RD count and WR count, p. 146 ).

For each device enter, if necessary, a comment in Description .

246

35011050 01 July 2006

TSX ETY 410•, TSX ETY PORT, TSX ETY 510• and TSX WMY 100

How to Configure a Specific Read and Write

Scenario

When scanned, certain devices, such as TSX ETY modules, do not support simultaneous read/write requests. In this case, to carry out an I/O read/write, the following procedure must be performed.

Step

1

2

10

11

12

13

8

9

6

7

3

4

5

14

Action

Enter the IP address for the device

If necessary, enter the device’s Unit ID (See The IP Address and Unit ID fields,

p. 145 ) Modbus slave address.

Select the period which scans the device.

Enter the read destination address in the device’s Slave RD ref.

(See Slave

RD ref. and slave WR ref., p. 146

).

Enter the number of words to be sent in read format in the device’s RD count

(See

RD count and WR count, p. 146 ).

Enter 0 in Slave WR ref.

(See

Slave RD ref. and slave WR ref., p. 146 ).

Enter 0 in WR count (See

RD count and WR count, p. 146 ).

On the following line, enter the same IP address

Enter, if necessary, the same Unit ID (See The IP Address and Unit ID fields,

p. 145 ) Modbus slave address.

Select the same period.

Enter 0 in Slave RD ref.

(See

Slave RD ref. and slave WR ref., p. 146

).

Enter 0 in RD count (See

RD count and WR count, p. 146 ).

Enter the write destination address in Slave WR ref.

(See Slave RD ref. and

slave WR ref., p. 146 ).

Enter the number of words to be sent in write format in WR count (See RD

count and WR count, p. 146

).

35011050 01 July 2006

247

TSX ETY 410•, TSX ETY PORT, TSX ETY 510• and TSX WMY 100

BOOTP Server Configuration

At a Glance

Note: No Address server for TSX WMY 100

In order to use the TSX ETY 410•/PORT/510• module as a BOOTP server, it is necessary to adjust the configuration parameters of the BOOTP utility (See Address

Server Configuration, p. 149 ).

How to Access the BOOTP

Server

The procedure for accessing the configuration parameters for the BOOTP server utility is as follows.

Step Action

1 Access the module configuration screen.

2 In the Module utilities zone, select the Address Server check-box.

Illustration

Module utilities

IO Scanning

Address Server

Global Data

Bandwidth

3

The Address Server tab is no longer grayed out.

Select the Address Server tab.

Result

Messaging

Utility

BOOTP

IO Scanning

Address Server

DHCP

Client/Server address table

7

8

5

6

9

3

4

1

2

MAC Address

00.54.1.05.F5

00.54.1.05.F4

00.54.1.05.E2

00.54.1.05.13

00.54.1.05.22

Name

SNMP Global Data

HTTP modification

√ Locked in operation

IP Address

139.160.234.30

139.160.234.31

139.160.234.32

139.160.234.33

139.160.234.34

Netmask

Bandwidth

SUN

Gateway

Bridge

Password

4 In the Utility zone, set the radio button to BOOTP

248

35011050 01 July 2006

TSX ETY 410•, TSX ETY PORT, TSX ETY 510• and TSX WMY 100

How to Configure the BOOTP

Server

The following procedure gives the configuration principles for the BOOTP server.

Fill in the fields of the BOOTP table for each device

(which require the module as BOOTP server)

MAC Addresses

IP Address

Do you want modification by the

HTTP server to be subject to a password?

Yes

Check the box

Locked in operation

Enter the password

No

End of BOOTP server configuration

35011050 01 July 2006

249

TSX ETY 410•, TSX ETY PORT, TSX ETY 510• and TSX WMY 100

DHCP Address Server Configuration

At a Glance

Note: No Address server for TSX WMY 100

In order to use the TSX ETY 410•/PORT/510• module as a DHCP server, it is necessary to adjust the configuration parameters of the DHCP utility (See Address

Server Configuration, p. 149 ).

How to Access the DHCP Server

Step

1

2

The procedure for accessing the configuration parameters for the DHCP server utility is as follows.

Action

Access the module configuration screen.

In the Utility zone, select the BOOTP checkbox.

3

Illustration

Module utilities

IO Scanning

Address Server

Global Data

Bandwidth

The BOOTP Server tab is no longer grayed out.

Select the Address Server tab.

Result

Messaging

Utility

BOOTP

IO Scanning Address Server

DHCP

Client/Server address table

MAC Address

7

8

5

6

9

3

4

1

2 00.54.1.05.F4

00.54.1.05.E2

Name device_IO_1 device_IO_2

SNMP Global Data

HTTP modification

√ Locked in operation

IP Address

139.124.10.50

139.124.10.51

139.124.10.52

139.124.10.53

139.124.10.54

Netmask

255.255.0.0

255.255.0.0

255.255.0.0

255.255.0.0

255.255.0.0

Bandwidth

BISCUIT

Gateway

139.124.10.1

139.124.10.1

139.124.10.1

139.124.10.5

139.124.10.1

Bridge

Password

4 In the Utility zone, set the radio button to DHCP

250

35011050 01 July 2006

TSX ETY 410•, TSX ETY PORT, TSX ETY 510• and TSX WMY 100

How to Configure the DHCP Server

The following procedure gives the configuration principles for the DHCP server.

Fill in the fields of the DHCP table for each device

(requiring the module as DHCP server)

MAC Address or Name

IP Address

Netmask

Gateway

Do you want modification by the

HTTP server to be subject to a password?

Yes

Check the box

Locked in operation

Enter the password

End of DHCP server configuration

No

35011050 01 July 2006

251

TSX ETY 410•, TSX ETY PORT, TSX ETY 510• and TSX WMY 100

Configuring the Global Data Utility

At a Glance

Note: No Global Data for TSX WMY 100

In order to use the TSX ETY 410•/PORT/510• module to use the Global Data utility, it is necessary to adjust the configuration parameters (See Configuration

Parameters Linked to the Global Data Utility, p. 155

).

252

35011050 01 July 2006

TSX ETY 410•, TSX ETY PORT, TSX ETY 510• and TSX WMY 100

How to Access the Global Data

Utility

To access the Global Data utility, proceed in the following way:

Step Action

1 Access the module configuration screen

2 In the Module utilities zone select the check box labeled Global Data

3

Illustration

Module utilities

IO Scanning

Address Server

Global Data

Bandwidth

The Global Data tab is no longer grayed out

Select the tab labeled Global Data

Result

Messaging IO Scanning

Global data configuration

Group address 239 255

Address Server

255 255

SNMP

Validity time out

Global Data

300

Multicast Filtering ms

Bandwidth

Distribution Period

%MW zone 500

Bridge

2 to

Cycle

712

Table of variables

Ident.

4

5

6

7

8

1

2

3

Type

SUB

SUB

NONE

SUB

SUB

PUB

NONE

NONE

Symbol

Data_1

Published

Address

%MW500

%MW533

%MW583

%MW683

%MW693

Length

33

50

100

10

20

Update symbols

35011050 01 July 2006

253

TSX ETY 410•, TSX ETY PORT, TSX ETY 510• and TSX WMY 100

Configuring

Global Data

To configure the Global Data utility execute the following steps in the configuration

Step

1

2

3

4

zone:

Global data

Action

Indicate the Distribution Group Address of the group which the station belongs to, between 224.0.0.0 and 239.255.255.255.

Adjust the Distribution Period between 1 and 50 PLC cycles.

Enter the %MW exchange zone start address in the: %MW zone entry field.

Define the Validity time out . This value can be adjusted from 50 to 1000 ms

(in increments of 50ms).

Table of variables

To configure Global Data in the Table of Variables zone, follow the instructions below:

Step

1

4

5

6

8

9

2

3

7

Action

Choose the identification ( Ident.

) of the Global Data to be published (only one possible).

Warning : make sure that the variable identification is not already used by another station.

select the PUB type from the drop-down list.

In the Length field, enter the number of %MW words (up to a maximum of

512). The end %MW value of the zone is then updated in the Global data configuration zone.

Choose the identification ( Ident.

) of a Global Data to be subscribed to.

select the SUB type from the drop-down list.

In the Length field, enter the number of %MW words (up to a maximum of

512). The end %MW value of the zone is then updated in the Global data configuration zone.

NB: the total size of the subscribed zone cannot exceed 2 Kwords.

To view the associated Symbol , click the Update symbols button (the symbol is entered in the PL7 symbol editor).

Redo steps 4 to 7 for each Global Data to subscribe (up to a maximum of 64).

If necessary, check the Multicast Filtering box.

254

35011050 01 July 2006

Configuration of the SNMP Utility

TSX ETY 410•, TSX ETY PORT, TSX ETY 510• and TSX WMY 100

At a Glance In order to use the TSX ETY 410•/PORT/510• or TSX WMY 100 module as an

SNMP agent, it is necessary to adjust the configuration parameters of the SNMP utility (See

Configuration of the SNMP Utility, p. 152 ).

How to Access the SNMP Utility

Step

1

2

The procedure for accessing the configuration parameters for the SNMP utility is as follows.

Action

Access the module configuration screen.

Select the SNMP tab.

Result

Messaging ID Scanning Address Server

IP Address Managers

IP Address manager 1 139 160 234 50

Agent

Location (SysLocation)

Contact (SysContact)

Community names

Set Public

Get

Trap

Public

Public

SNMP

Schneider Electric Sophia

Global Data

IP Address manager 2

Security

Bandwidth

139 160 234 53

Bridge

SNMP Manager

Enable “Authentication Failure” trap

35011050 01 July 2006

255

TSX ETY 410•, TSX ETY PORT, TSX ETY 510• and TSX WMY 100

How to Configure

SNMP

The following procedure gives the configuration principles for the SNMP utility.

Step

1

2

3

4

Action

Enter the SNMP manager addresses: z z

Manager 1 IP addresses

Manager 2 IP addresses

Fill in the fields: z z

Location (SysLocation)

Contact (SysLocation) .

Or alternatively check the SNMP Manager box to indicate that the information will be completed by the SNMP in use.

If you want to set access rights, fill in the community names: z z z

Set

Get

Trap

If you want to activate transmission of an event to the module, check the

Activate "Authentication Failure" trap box.

256

35011050 01 July 2006

TSX ETY 410•, TSX ETY PORT, TSX ETY 510• and TSX WMY 100

Configuring the Time Synchronization Service

Configuring the

Time Service with the NTP

Configuration

Page

You must use the module’s embedded Web page to configure the time service. No other method is available.

NTP Configuration

NTP Server Configuration

IP Address of Primary NTP Server:

IP Address of Secondary NTP Server:

Polling Period:

Time Zone

(GMT-05:00)Eastern Standard Time[New York]

15

192.168.5.100

0.0.0.0

sec

Automatically adjust clock for daylight saving change

Save Cancel Disable NTP

Time Service

Command

Buttons

Execute the following commands

Command Button Description

Save Stores new NTP (time service) configuration. Previous configuration is no longer valid.

Cancel

Disable NTP

Cancels new NTP (time service) configuration. Previous configuration is valid

IP of Primary and Standby set = 0.

NTP server not polled

Time in controller not updated.

35011050 01 July 2006

257

TSX ETY 410•, TSX ETY PORT, TSX ETY 510• and TSX WMY 100

Configurable

Time Service

Parameters

Changing Time

Service

Parameters

Configure or change the following parameters on the NTP Configuration page.

1.

IP address of primary NTP server z

Enter a valid IP address

2.

IP address of secondary NTP server z

Enter a valid IP address

3.

Polling Period (in seconds)

Enter a value z min = 1sec z z max = 120sec default = 5 sec

4.

Time Zone z

Select from drop-down menu z

Universal Time, Coordinated (GMT) = default

Custom time zone

5.

Automatically adjust clock for daylight saving change z

Parameter is selected by default (check mark appears) if daylight saving time is chosen.

To make any changes to the time synchronization service,

Step

1

2

Action

Enter changes in the appropriate field on the NTP Configuration page for one or all of the configurable parameters.

Click Save.

Important

Information about the Time

Service

Note: About the Time Service

1.

Enable/Disable Daylight Savings Time parameter

If the Enable/Disable check box is selected, the module automatically corrects the local time to account for daylight savings time. Therefore, requiring no action, as the daylight savings time start and end are automatically changed each year.

2.

Polling Time Parameter

The time (in seconds) is the time between time updates from the NTP server.

The default is 5 Seconds.

3.

Storing the Time Service Configuration

The last time service configuration is saved internally in the Ethernet module.

4.

Replacing the Ethernet Module

If the Ethernet module has to be replaced, the stored configuration is lost, and the system returns to the default configuration.

258

35011050 01 July 2006

Customizing

Time Zone

Parameters

Time Zone

Parameters

35011050 01 July 2006

TSX ETY 410•, TSX ETY PORT, TSX ETY 510• and TSX WMY 100

If you want a time zone not listed in the time zone table,

Step Action

1 Write the text rules for the custom time zone.

Comment

2 Using an FTP client, store your rules in the file:

/FLASH0/wwwroot/conf/NTP/customrules user ID: ntpupdate password: ntpupdate

3 When the rules are written, choose the drop down menu on the NTP Configuration web page, and configure (or reboot) the module by selecting

Time Zone = Custom

Root directory to store 'customrules' is set by the FTP server as

/FLASH0/wwwroot/conf/NTP

The NTP component looks for customrules, calls the tz compiler and generates a new file called

'tz_custom'. This file is binary file and should not be edited.

If the tz compiler detects a syntax error in customrules, the error is logged in the file:

/FLASH0/wwwroot/conf/NTP/ error.log

1.

NTP component is not launched

2.

NTP Status field in diagnostic web page displays NOT OK.

4 If you want more information, the syntax to write those rules along with a few examples are found in the module in

/FLASH0/wwwroot/conf/NTP/instructions.txt

Select one from drop-down menu.

Time Zone Description

Custom

(GMT-12:00) Dateline Standard Time [Eniwetok Kwajalein]

(GMT-11:00) Samoa Standard Time [Midway Is Samoa]

(GMT-10:00) Hawaiian Standard Time [Hawaii Honolulu]

(GMT-09:00) Alaskan Standard Time [Anchorage]

(GMT-08:00) Pacific Standard Time [Los Angeles Tijuana]

(GMT-07:00) Mexican Standard Time [Chihuahua La Paz Mazatlan]

(GMT-07:00) Mountain Standard Time [Arizona Phoenix]

(GMT-07:00) Mountain Standard Time [Denver]

(GMT-06:00) Central Standard Time [Chicago]

(GMT-06:00) Mexico Standard Time [Tegucigalpa]

Yes

No

Yes

Yes

No

No

No

Yes

Yes

DST

Available

Yes

No

259

TSX ETY 410•, TSX ETY PORT, TSX ETY 510• and TSX WMY 100

Time Zone Description

(GMT-06:00) Canada Central Standard Time [Saskatchewan Regina]

(GMT-06:00) Central America Standard Time [Mexico_city]

(GMT-05:00) SA Pacific Standard Time [Bogota Lima Quito]

(GMT-05:00) Eastern Standard Time [New York]

(GMT-05:00) Eastern Standard Time [Indiana (East)] [Indianapolis]

(GMT-04:00) SA Western Standard Time [Caracas La Paz]

(GMT-04:00) Pacific SA Standard Time [Santiago]

(GMT-03:30) Newfoundland Standard Time [Newfoundland St Johns]

(GMT-03:00) E. South America Standard Time [Brasilia Sao_Paulo]

(GMT-03:00) SA Eastern Standard Time [Buenos Aires Georgetown]

(GMT-02:00) Mid-Atlantic Standard Time [South_Georgia]

(GMT-01:00) Azores Standard Time [Azores Cape Verde Island]

(GMT)

(GMT0)

Universal Coordinated Time [Casablanca, Monrovia]

Greenwich Mean Time [Dublin Edinburgh Lisbon London]

(GMT+01:00) Romance Standard Time [Amsterdam CopenHagen Madrid

Paris Vilnius]

(GMT+01:00) Central European Standard Time [Belgrade Sarajevo Skopje

Sofija Zagreb]

(GMT+01:00) Central Europe Standard Time [Bratislava Budapest Ljubljana

Prague Warsaw]

Yes

Yes

(GMT+01:00) W. Europe Standard Time [Brussels Berlin Bern Rome

Stockholm Vienna]

(GMT+02:00) GTB Standard Time [Athens Istanbul Minsk]

(GMT+02:00) E. Europe Standard Time [Bucharest]

Yes

Yes

Yes

(GMT+02:00) Egypt Standard Time [Cairo] Yes

(GMT+02:00) South Africa Standard Time [Johannesburg Harare Pretoria] No

(GMT+02:00) FLE Standard Time [Helsinki Riga Tallinn]

(GMT+02:00) Israel Standard Time [Israel Jerusalem]

(GMT+03:00) Arabic Standard Time [Baghdad]

(GMT+03:00) Arab Standard Time [Kuwait Riyadh]

Yes

Yes

Yes

No

(GMT+03:00) Russian Standard Time [Moscow St. Petersburg Volgograd] Yes

(GMT+03:00) E. Africa Standard Time [Nairobi] No

(GMT+03:30) Iran Standard Time [Tehran]

(GMT+04:00) Arabian Standard Time [Abu Dhabi Muscat]

Yes

No

No

Yes

No

Yes

Yes

Yes

Yes

Yes

No

No

Yes

No

No

DST

Available

No

Yes

260

35011050 01 July 2006

35011050 01 July 2006

TSX ETY 410•, TSX ETY PORT, TSX ETY 510• and TSX WMY 100

Time Zone Description

(GMT+04:00) Caucasus Standard Time [Baku Tbilisi]

(GMT+04:00) Afghanistan Standard Time [Kabul]

(GMT+05:00) Ekaterinburg Standard Time [Ekaterinburg]

(GMT+05:00) West Asia Standard Time [Islamabad Karachi Tashkent]

(GMT+05:30) India Standard Time [Bombay Calcutta Madras New Delhi]

(GMT+06:00) Central Asia Standard Time [Almaty Dhaka]

(GMT+06:00) Sri Lanka Standard Time [Columbo]

(GMT+07:00) SE Asia Standard Time [Bangkok Hanoi Jakarta]

No

No

(GMT+08:00) China Standard Time [Beijing Chongqing Hong Kong Urumqi] No

(GMT+08:00) W. Australia Standard Time [Perth] No

Yes

No

No

Yes

DST

Available

Yes

No

(GMT+08:00) Singapore Standard Time [Singapore]

(GMT+08:00) Taipei Standard Time [Taipei]

(GMT+09:00) Tokyo Standard Time [Osako Sapporo Tokyo]

(GMT+09:00) Korea Standard Time [Seoul]

No

No

No

No

(GMT+09:00) Yakutsk Standard Time [Yakutsk]

(GMT+09:30) Cen. Australia Standard Time [Adelaide]

(GMT+09:30) AUS Central Standard Time [Darwin]

(GMT+10:00) E. Australia Standard Time [Brisbane]

(GMT+10:00) AUS Eastern Standard Time [Canberra Melbourne Sydney]

(GMT+10:00) West Pacific Standard Time [Guam Port Moresby]

(GMT+10:00) Tasmania Standard Time [Hobart]

(GMT+10:00) Vladivostok Standard Time [Vladivostok]

(GMT+11:00) Central Pacific Standard Time [Magadan Solomon Is New

Caledonia]

Yes

No

Yes

Yes

Yes

Yes

Yes

No

No

(GMT+12:00) New Zealand Standard Time [Auckland Wellington]

(GMT+12:00) Fiji Standard Time [Fiji Kamchatka Marshall Is]

Yes

No

261

TSX ETY 410•, TSX ETY PORT, TSX ETY 510• and TSX WMY 100

Configuring the Bandwidth Utility

At a Glance

Note: No Bandwidth Monitoring for TSX WMY 100

In order to use the TSX ETY 410•/PORT/510• module with the Bandwidth utility, it is necessary to adjust the configuration parameters of this utility.

Accessing

Bandwidth

Step

1

2

The procedure for accessing the configuration parameters for the Bandwidth utility is as follows.

Action

Access the module configuration screen.

In the Module utilities zone, select the Bandwidth checkbox.

3

Illustration

Module utilities

IO Scanning

Address Server

The Bandwidth tab is no longer grayed out.

Select the Bandwidth tab.

Result

Global Data

Bandwidth

Messaging

MAST task

Periodic

Cyclic

IO Scanning

Time period

Address Server

10 ms

SNMP Global Data

Messaging flux estimation

Bandwidth

0

Bridge

Number of messaging transactions per second

Distribution estimation

Estimation of the bandwidth distribution

12 % IO scanning 50 % Global data 55 % Messaging 21

Update distribution estimation

% Other

262

35011050 01 July 2006

TSX ETY 410•, TSX ETY PORT, TSX ETY 510• and TSX WMY 100

Using the

Bandwidth Utility

Step

1

2

3

To use the Bandwidth utility, proceed in the following way:

Action

Once you have configured the I/O scanning and/or Global data utilities, enter the estimated messaging flux to be processed by the module in the Number of messaging transactions per second window.

If the Mast task is cyclic, enter the value in the Time period window (if the task is periodic, the value is read directly in the configuration).

To view the bandwidth distribution estimation, click the button Update distribution estimation .

A graphic appears.

Illustration

Distribution estimation

Estimation of the bandwidth distribution

12 % IO scanning 12 % Global data 55 % Messaging 21

Update distribution estimation

% Other

4 If the module load is exceeded, the message: "Module load cannot exceed 100%" appears.

Redo steps 1 to 3 to adjust the configuration parameters until the module load is correct.

35011050 01 July 2006

263

TSX ETY 410•, TSX ETY PORT, TSX ETY 510• and TSX WMY 100

Configuration of the Bridge Function

At a Glance The TSX ETY 410•/PORT/510• or the TSX WMY 100 modules can be used as an

X-WAY bridge station. This guarantees transparent communication between different networks.

Note: To find out about the implementation of this function, refer to the multinetwork communication part (See

Multi-network architectures, p. 289 ).

Only the procedure for accessing the bridge function is explained here.

How to Access the Bridge

Function

The procedure for accessing the configuration parameters for the bridge function is as follows.

Step

1

2

Action

Access the module configuration screen.

Select the Bridge tab.

264

35011050 01 July 2006

TSX ETY 410•, TSX ETY PORT, TSX ETY 510• and TSX WMY 100

9.3

Debugging

At a Glance

Aim of this

Section

What's in this

Section?

This section describes the implementation of the TSX ETY 410•, TSX ETY PORT,

TSX ETY 510• or TSX WMY 100 module during debugging.

The TSX WMY module offers the same services than the other modules, except the following ones : z

IO Scanning, z z z

Global Data,

Address server,

Bandwidth Monitoring.

This section contains the following topics:

Topic

Module Debugging Screen

General debugging parameters

Debugging parameters for TCP/IP facilities

How to test TCP/IP communication with a Ping request

Requests available for the communication channel test

How to test a channel with Identification and Mirror requests

How to test a channel with requests

Debugging Parameters for the IO Scanning Utility

Debugging Parameters for the Global Data Utility

Bandwidth Monitoring Diagnostic Parameters

Page

266

268

269

270

271

272

273

275

276

277

35011050 01 July 2006

265

TSX ETY 410•, TSX ETY PORT, TSX ETY 510• and TSX WMY 100

Module Debugging Screen

At a Glance This screen, separated into six zones, allows debugging via an ETHERNET link.

Illustration

4

The screen dedicated to ETHERNET communication is displayed as follows:

1 3 5

TSX ETY 4102/3 [RACK 0 POSITION 2]

Debugging

Designation: FACTORYCAST MODULE Version: 2.0

RUN

Address information

Address

IP servie

Communication test

Remote IP Address

Message traffic (msg./min)

Min.

0

MAC address 00.80.F4.01.00.41

Subnetwork mask

Gateway Address

Avg.

IP Address

1330

Ping

139.160.234.18

255.255.255.0

139.160.234.1

Max.

Time

4000

2660 msg/min.

Reset ms

ERR STS DIAG...

Messages

Open connections

Non-authorized access

Messages refused

Messages received

Messages sent

Band width

IO Scanning

2

0

0

703

702

Reset counters

IO Scanning activated

Global Data

Global Data activated

Not configured

Scanned

16

32

Unscanned

Faulty or missing

48

64

Not configured

SUB variable

PUB variable

Fault

16

32

48

64

XWAY test station

Local address 10.40

Station number 0

Response reception

Ascii Hexa

Identification

Mirror

Enter request

1

17

33

49

1

17

33

49

2

Elements and

Functions

266

8 7 6

This table describes the different zones that make up the debugging screen:

Address Zone

1 common

2

Function common part of the debugging screens (Communication applications Volume 1 - Description of communication debugging screens) for communicating allows the graphical display of the number of messages processed by the module:

3

Message traffic

(See Message

traffic, p. 268

)

Messages (See

Messages,

p. 268

) allows the display of the number of unacknowledged or refused messages and connections.

35011050 01 July 2006

35011050 01 July 2006

TSX ETY 410•, TSX ETY PORT, TSX ETY 510• and TSX WMY 100

Address Zone

4 TCP/IP utilities

(See Debugging parameters for

TCP/IP facilities,

p. 269 )

5

6

XWAY test station (See

Requests available for the communication channel test,

p. 271 )

IO Scanning (See

Debugging

Parameters for the IO Scanning

Utility, p. 275 )

7 Global Data (See

Debugging

Parameters for the Global Data

Utility, p. 276 )

8 Bandwidth (See

Bandwidth

Monitoring

Diagnostic

Parameters,

p. 277 )

Function allows: z z display of TCP/IP utilities configuration, communication testing of the TCP/IP profile.

allows UNI-TE communication testing on the TCP/IP profile.

allows display of the status for each remote input/output module (Except TSX WMY 100).

allows display of the status for Global Data variables (Except

TSX WMY 100).

allows access to the Bandwidth diagnostics

(Except TSX WMY 100)

267

TSX ETY 410•, TSX ETY PORT, TSX ETY 510• and TSX WMY 100

General debugging parameters

Introduction

Message traffic

The general debugging parameters are grouped into two windows : z the Message traffic window, z the Messages window,

The window looks like this :

Message trafic (msg./min.)

4000 msg.min

Messages

Min 0 Avg 1243 Max 2486 RESET

It shows graphically the number of messages per minute handled by the module

(sending and receiving). For a better view, the scale automatically adapts according to flow rate fluctuations.

The Reset button resets to zero the three counters Min.

, Av.

and Max.

.

The window looks like this :

Messages

Connections allowed

Access denied

Messages refused

Messages received

Messages sent

1

0

0

6632

6628

Reset Counters

This window relates to the TCP/IP messaging facility: z number of connections open, z z

number of non authorized accesses, number of messages refused, received, and sent.

You can reset these counters to zero by clicking on the Init counter button.

268

35011050 01 July 2006

TSX ETY 410•, TSX ETY PORT, TSX ETY 510• and TSX WMY 100

Debugging parameters for TCP/IP facilities

Introduction

Address information

The debugging parameters for TCP/IP facilities are grouped in two windows : z the Address information window, z the Communication test window.

The window looks like this :

IP address

IP Address module

MAC address 00.80.F4.01.00.05

IP Address 222.111.3.88

Subnetwork mask

Gateway address

255.255.255.0

222.111.3.0

It shows the configuration data for the IP address: z

MAC address : unique and fixed address for a module z z z

IP Address

Subnetwork mask

Gateway Address : gateway address

Communication test

The window looks like this :

Communication test

Remote IP address

222.111.3.88

Ping Time 1 ms

This window is used to test the IP communication with another station.

35011050 01 July 2006

269

TSX ETY 410•, TSX ETY PORT, TSX ETY 510• and TSX WMY 100

How to test TCP/IP communication with a Ping request

Introduction

Steps to follow

This page indicates the procedure to be followed to test a TCP/IP communication by means of a Ping request.

The following procedure allows the sending of the Ping request and thus tests the routing of information between two devices.

Step

1

2

Action

Input the address of the station to be interrogated with the help of the field

Remote IP address .

Press the button Ping .

Result

The reply appears in the field Time :

Time 1 ms

The time returned corresponds to the turnaround time for the message in ms.

Type of response The following table groups together the different types of response to the Ping request.

If the response is… then … positive The window indicates the turnaround time for the message in ms.

negative a window with the message Host unreachable specifies that the remote device has not been reached in the network architecture.

270

35011050 01 July 2006

TSX ETY 410•, TSX ETY PORT, TSX ETY 510• and TSX WMY 100

Requests available for the communication channel test

Introduction

Test conditions

Available requests

This page describes the different possibilities for testing a communication channel from the debugging screen.

Sending a request to an unconnected station results in an error message.

The test is applied to stations from the same local network.

Window X-WAY Station test allows the following requests : z

Identification (See

How to identify a station, p. 272

) : prompts the Identification z request to be sent to the designated remote station,

Mirror (See

How to send the Mirror request, p. 272

) : allows a mirror request to be sent to the designated station. Selecting this function gives access to a screen that allows you to select the length of the character string to be sent (a maximum of 80 characters ). The PLC then sends this character string (ABCD….) to the destination device. This automatically sends the character string that was z received back to the sender.

Request input (See

How to test a channel with requests, p. 273 ) : allows a

UNI-TE request, other than those provided by the command buttons, to be sent to the designated station. Selecting this function gives access to a screen that allows you to select the parameters specific to the request (the request code must be coded in hexadecimal).

Note: The UNITE server of the TSX ETY or TSX WMY 100 data module is the destination of the first two requests. The processor server is the destination of the third.

35011050 01 July 2006

271

TSX ETY 410•, TSX ETY PORT, TSX ETY 510• and TSX WMY 100

How to test a channel with Identification and Mirror requests

Introduction This page indicates the procedure to follow to test a communication channel by means of Identification and Mirror requests.

How to identify a station

The following procedure allows the identification of a designated station.

Step Actions

1 Select the address of the station to be interrogated with the help of the field Station number .

2 Click on the button Identification .

Result

The response appears in the Receive Response window :

Response reception

..’.TSX ETY 410..!....

ASCII Hex.

How to send the

Mirror request

The following procedure allows the sending of the Mirror request and thus tests the routing of information between two devices.

Step Action

1 Select the address of the station to be interrogated with the help of the field Station .

2 Click on the button Mirror .

Result

The following window appears :

Mirror Request

Length of data to be sent 8

Send Cancel

3 Input the length of data to be sent (maximum 80 characters).

4 Click on the button Send .

Result

The response appears in the Receive Response window :

Response reception

ABCDEFGH

ASCII Hex.

The response contains: z the character string ABCDEFGH that corresponds to the length of data sent 8.

272

35011050 01 July 2006

TSX ETY 410•, TSX ETY PORT, TSX ETY 510• and TSX WMY 100

How to test a channel with requests

Introduction This page indicates the procedure to follow to test a communication channel from the debugging screen through different requests.

How to send a request

The following procedure allows a request, other than those provided by the command buttons, to be sent to a designated station. In this example, the request sent is used to read 10 words (from %MW1 to %MW10).

Step Action

1 Select the address of the station to be interrogated with the help of the field Station .

2 Click on the button Input Request .

Result

The following window appears :

Enter Request

Request code (hexadecimal)

Data (hexadecimal)

680701000A00

36

Send Cancel

The data sent in this example is coded on 6 bytes.

3 Input the function code (coded in hexadecimal on one byte), corresponding to the request that you want to send.

For this example the read request code is 16#36.

4 Input the data to be sent by coding all the data in hexadecimal. The data is sent non-stop without any time intervals between them. When the data is coded on one word, the most significant and least significant bytes are reversed.

For this example the data is as follows : z z z z

16#68 : on one byte, defines the segment (internal data),

16#07 : on one byte, defines the object type (words),

16#0100 : on one byte, defines the first word to read,

16#0A00 : on one byte, defines the number of words to read.

35011050 01 July 2006

273

TSX ETY 410•, TSX ETY PORT, TSX ETY 510• and TSX WMY 100

Step Action

5 Click on the Send button.

Result

The response appears in the Receive Response window :

Response reception

07 00 C2 92 20 24 40 00

ASCII Hex.

The response from the example has data on 21 bytes.

z z

16#07 : corresponds to object type (words),

16#00C2 : corresponds to the value of the first word (the most significant and least significant bytes are z reversed, its value is 16#C200),

...

274

35011050 01 July 2006

TSX ETY 410•, TSX ETY PORT, TSX ETY 510• and TSX WMY 100

Debugging Parameters for the IO Scanning Utility

At a Glance

IO Scanning

Note: No IO Scanning for TSX WMY 100

When the IO Scanning utility is activated, the status of each configured device is displayed on the screen.

The window is displayed as below:

IO Scanning

√

IO Scanning activated

Not configured

Scanned

16

Unscanned

Faulty or missing

32

48

64

1

17

33

49

A device referenced in the IO Scanning configuration tab can have the following states: z z

Scanned : green,

Not configured : white, z z

Unscanned : black (caused by IO Scanning utility not being activated, none selected in configuration),

Faulty or absent : red,

Note: In the cases of Not configured and Unscanned , no Modbus request is generated towards the device.

35011050 01 July 2006

275

TSX ETY 410•, TSX ETY PORT, TSX ETY 510• and TSX WMY 100

Debugging Parameters for the Global Data Utility

At a Glance

Global Data

Note: No Global Data for TSX WMY 100

When the Global Data utility is activated, the status of a Global Data variable is displayed on the screen.

The window is displayed as below:

Global Data

√

Global Data activated

Not configured

SUB variable

PUB variable

Fault

16

32

48

64

1

17

33

49

A Global Data variable can have the following status: z

Not configured : white, z z z

PUB variable : published variable, black,

SUB variable : subscribed variable received in the validity timeout limit, green,

Fault : subscribed variable not received in the validity time out limit, red.

276

35011050 01 July 2006

TSX ETY 410•, TSX ETY PORT, TSX ETY 510• and TSX WMY 100

Bandwidth Monitoring Diagnostic Parameters

At a Glance

Bandwidth

Note: No Bandwidth Monitoring for TSX WMY 100

When bandwidth monitoring is activated, the load of module

TSX ETY 410•/PORT/510• is displayed on the screen.

The window is displayed as below:

Distribution of Utilities

20 % IO scanning 30 % Global data

OK

40 % Messaging 10 % Others (idle)

This graphic displays the actual load distribution, between I/O Scanning , Global

Data, Messaging and other utilities: z z z z

%IO Scanning : yellow,

% Global Data : blue,

% Messaging : green,

% Others : gray.

Return to configuration (See

Module Configuration Screen, p. 236

) if you wish to modify this distribution.

35011050 01 July 2006

277

TSX ETY 410•, TSX ETY PORT, TSX ETY 510• and TSX WMY 100

9.4

Language objects associated with TSX ETY 410•,

TSX ETY PORT, TSX ETY 510• and TSX WMY 100

Modules

At a Glance

Aim of this

Section

What's in this

Section?

This section presents the different language objects specific to TSX ETY 410•,

TSX ETY PORT, TSX ETY 510• or TSX WMY 100 modules.

This section contains the following topics:

Topic

Implicit Exchange Language Objects

Explicit Exchange Language Objects

Explicit exchange management and report

Language Objects Associated with Configuration

Page

279

281

283

284

278

35011050 01 July 2006

TSX ETY 410•, TSX ETY PORT, TSX ETY 510• and TSX WMY 100

Implicit Exchange Language Objects

At a Glance

Bit Objects

Note: For TSX WMY 100, all IO Scanning and GlobalData objects have a reserved status.

This page describes all the implicit exchange (Communication applications

Volume 1 - Default exchanges) language objects for ETHERNET communication with the TSX ETY 410•/PORT/510• module that can be displayed or modified by the application program.

The table below shows the various implicit exchange bit objects.

Object (1) Function

%Ixy.MOD.ERR Module error bit

%Ixy.i.ERR

Channel error bit

Meaning

This bit set to 1 indicates a module error (at least one of the channels has an error, for instance)

This bit set to 1 indicates a line fault.

Legend

(1) Address xy.i

z x: corresponds to the rack number z y: corresponds to the module number z i: corresponds to the channel number

35011050 01 July 2006

279

TSX ETY 410•, TSX ETY PORT, TSX ETY 510• and TSX WMY 100

Word Objects The table below shows the various implicit exchange word objects.

Object (1)

%IWxy.i.0

%IWxy.i.1

...

%IWxy.i.4

%IWxy.i.5

%IWxy.i.6

to

%IWxy.i.9

Function

Reserved

Refresh remote input/ output indicators

(IO Scanning utility)

...

Refresh remote input/ output indicators

(IO Scanning utility)

Reserved

Global Data validity indicators z z z z

z z z z z z z z

-

Meaning z z x0 = 1: status bit for device 1, specifying that it has been scanned.

...

x7 = 1: status bit for device 8, specifying that it has been scanned.

x8 = 1: status bit for device 9, specifying that it has been scanned.

...

x15 = 1: status bit for device 16, specifying that it has been scanned.

...

z z x0 = 1: status bit for device 49, specifying that it has been scanned.

...

x7 = 1: status bit for device 56, specifying that it has been scanned.

x8 = 1: status bit for device 57, specifying that it has been scanned.

...

x15 = 1: status bit for device 64, specifying that it has been scanned.

z x0 = 1: status bit indicating that the Ident. 1 has been received.

...

x15 = 1: status bit indicating that the Ident. 16 has been received.

...

x63 = 1: status bit indicating that the Ident. 64 has been received.

Legend

(1) Address xy.i

z x: corresponds to the rack number z z y: corresponds to the module number i: corresponds to the channel number

280

35011050 01 July 2006

TSX ETY 410•, TSX ETY PORT, TSX ETY 510• and TSX WMY 100

Explicit Exchange Language Objects

At a Glance

Internal Words

Note: For TSX WMY 100, all IO Scanning and GlobalData objects have a reserves status.

This page describes all the explicit exchange (Communication applications Volume

1 - Specified exchanges: General points) language objects for ETHERNET communication with the TSX ETY 410•/PORT/510• or TSX WMY 100 module that can be displayed or modified by the application program.

The following table describes the internal words:

Object (1)

%MWxy.i.2

%MWxy.i.3

%MWxy.i.4

%MWxy.i.5

%MWxy.i.6

%MWxy.i.7

and %Mwxy.i.8

Function

%MWxy.MOD.2 Module status z z z z z z z z

Meaning x0 = 1: defective module x1 = 1: functional error (error between the processor and the module, adjustment or configuration error, etc.) x2 = 1: terminal block fault (not connected) x3 = 1: self-tests running x4 = 1: reserved x5 = 1: error in hardware or software configuration (the module present is not that declared in the configuration, the submodules are not compatible) x6 = 1: module missing x7 = 1: error in one of the sub-modules

Channel standard status z z z z x0 to x3 = 0: reserved x4 = 1: module error or self-tests running x5 and x6 = 0: reserved x7 = 1: application error (error in the configuration)

Specific channel status Byte 0: z x0 = 1: if X-WAY bridge (0 if not bridge)

Byte 1: number of TCP connections open

Error counters Number of connection requests refused

Error counters

Network/station address

Message counters on the link layer

Number of messages refused

Byte 0: station number

Byte 1: network number

Number of messages sent on the link layer

35011050 01 July 2006

281

TSX ETY 410•, TSX ETY PORT, TSX ETY 510• and TSX WMY 100

Object (1)

%MWxy.i.9

and %Mwxy.i.10

%MWxy.i.11

%MWxy.i.12

%MWxy.i.13

%MWxy.i.14

%Mwxy.i.15

Function

Message counters on the link layer

Activity of the IO

Scanning utility

IO Scanning utility connections

Global Data distributed configuration error

Module loading rate

Module loading rate

Meaning

Number of messages received on the link layer

Number of frames received per second for the IO

Scanning utility

Number of active connections for the IO

Scanning utility (corresponds to the number of refreshed status bits) x0 and x1:

00 : no error detected.

01 : one piece of Global Data is published with a different length to that of the corresponding

Subscription (even Ident.) in the same

Distribution Group.

10 : two pieces of Global Data are published with the same Ident. in the same Distribution Group.

Byte 0: z I/O Scanning loading rate

Byte 1: z Global Data loading rate

Byte 0: z Messaging loading rate

Byte 1: z Other utilities loading rate

Legend

(1) Address xy.i

z x: corresponds to the rack number z z y: corresponds to the module number i: corresponds to the channel number

282

35011050 01 July 2006

TSX ETY 410•, TSX ETY PORT, TSX ETY 510• and TSX WMY 100

Explicit exchange management and report

Introduction

Word objects

This page describes all the language objects that manage explicit exchanges

(Communication applications Volume 1 - Exchange and report management).

The table below shows the different word objects for the management of explicit exchanges.

Object (1) Function

%MWxy.MOD.0 Module exchanges in progress

%MWxy.MOD.1 Module report

%MWxy.i.0

%MWxy.i.1

Channel exchanges in progress

Channel report z z z z

Meaning z z z x0 = 1 : status reading in progress x1 = 1 : sending of command parameters to the communication module x2 = 1 : sending of adjustment parameters to the communication module x1 = 0 : command parameters received and accepted by the module x2 = 0 : adjustment parameters received and accepted by the module z z z x0 = 1 : status reading in progress x1 = 1 : sending of command parameters to the communication channel x2 = 1 : sending of adjustment parameters to the communication channel x1 = 0 : command parameters received and accepted by the communication channel x2 = 0 : adjustment parameters received and accepted by the communication channel

Key

(1) Address xy.i

z x : corresponds to the rack number z z y : corresponds to the module number i : corresponds to the channel number

35011050 01 July 2006

283

TSX ETY 410•, TSX ETY PORT, TSX ETY 510• and TSX WMY 100

Language Objects Associated with Configuration

At a Glance

Internal

Constants

This page describes all the configuration language objects for ETHERNET communication with the TSX ETY 410•/PORT/510• or TSX WMY 100 module that can be displayed by the application program.

The following table describes the internal constants:

Object

%KWxy.i.0

%KWxy.i.1

Function

Type

Physical layer

%KWxy.i.2

Reserved

%KWxy.i.3

Reserved

%KWxy.i.4

Reserved

%KWxy.i.5

X-WAY network address

-

-

-

Meaning

Byte 0 = 11 for ETHERNET communication

Byte 1: reserved

Byte 0: fixed at 16#01 (corresponds to GPX2)

Byte 1: reserved

Byte 0: network number (0 by default)

Byte 1: reserved

%KWxy.i.6

%KWxy.i.7

%KWxy.i.8

and

%KWxy.i.9

%KWxy.i.10

and

%KWxy.i.11

Type of ETHERNET driver for TCP/IP

TCP/IP configuration: address type

Byte 0: fixed at 16#01 (corresponds to RJ45) z = 16#01 : RJ45

Byte 1: z z

= 16#00 : ETHERNET II (default value)

= 16#01 : 802.3

Byte 0: reserved

Byte 1: inherited address z = 16#01 : from the application-specific function z = 16#03 : from a server

Local IP address Example with the address 139.160.650.109

Byte 0 = 109

Byte 1 = 65

Byte 2 = 160

Byte 3 = 139

IP address of gateway Example with the address 139.160.65.1

Byte 0 = 1

Byte 1 = 65

Byte 2 = 160

Byte 3 = 139

284

35011050 01 July 2006

35011050 01 July 2006

Object

%KWxy.i.12

and

%KWxy.i.13

Function

TSX ETY 410•, TSX ETY PORT, TSX ETY 510• and TSX WMY 100

Subnetwork mask

%KWxy.i.14 Utilities used

%KWxy.i.15 TCP utilities used

Meaning

Example with the address 255.255.255.0

Byte 0 = 0 (least significant)

Byte 1 = 255

Byte 2 = 255

Byte 3 = 255 (most significant)

Byte 0: z z x0 = 1: IO Scanning utility is used x1 = 1: BOOTP server utility is used z z x2 = 1: global data utility is used x3 = 1: the utility to adjust bandwidth is used

Byte 1: reserved

Byte 0: z x0 = 1: Modbus communication on TCP/IP is z used x1 = 1: access control is activated

Byte 1: reserved

285

TSX ETY 410•, TSX ETY PORT, TSX ETY 510• and TSX WMY 100

9.5

Questions/Answers

Questions/Answers

General

286

Below you will find a list of the most frequently asked questions and answers regarding communication by Ethernet network.

Can a Momentum be searched by several ENTs at a time?

Yes, in read only. Only one IO Scanner at a time should access the ENT in write mode.

Do I have to configure the IO Scanner connections in the connections table

("Messaging" tab)?

No.

What should I do if the TSX ETY 410•/PORT/510• or TSX WMY 100 module displays the LED status "Not configured" (Flashing ERR)?

z z

Check that it is configured in PL7.

Check that there is no other module with the same X-WAY network number in the z

PLC configuration.

If the module is configured in "Client/Server address", make sure that a BOOTP server is operational and accessible.

What should I do if the module displays a correct LED status (STS=RUN=ON) but does not respond to requests?

Try a Ping command to this IP address, from a device on the same network: z

No response: z z

Check the network configuration: wiring, status of "hubs", IP addresses, masks and gateways if there are routers in the configuration.

Correct response to the Ping: z

Check the module's X_WAY address.

z z

Check whether access control is activated or not.

Try to connect to the Rack Viewer page by http. If this connection works, check the X-WAY address of the client application.

Can I change the MAC address of the module?

No. This is fixed for every Ethernet device to guarantee its unicity.

How can I find out the speed with which the module communicates?

Via an internet browser, by connecting to the Ethernet Module Statistics page.

What should I do if the messaging EFs do not get a response?

35011050 01 July 2006

35011050 01 July 2006

TSX ETY 410•, TSX ETY PORT, TSX ETY 510• and TSX WMY 100 z z z

Check that the X-WAY destination address is part of the IP/X-WAY connections table.

Check that the configuration of the destination module does not prohibit this connection (access control).

In debug mode, try the "Ping" command towards the IP address of the destination

PLC, then try an "Identification" request towards the destination address, if it is part of the same X-WAY network.

What should I do if I receive the 0xFF12 refusal code on the messaging EFs?

This code indicates that the module is full. Reduce the transition rate.

What should I do if the READ_ASYNC, WRITE_ASYN messaging EFs do not get a response (time out)?

Check that the "mast" tasks of the client and server PLCs are configured to

"periodic", with a sufficient period to ensure that the PLCs do not overrun.

When should I configure my connections to "Mono-Connection"?

When this connection has to be established to a TSX ETY 110, MODBUS protocol.

The destination PLC of my messages is a bridge. Which Xway destination address should I configure in the connections table?

The X-WAY address of the first communication module of the PLC bridge (it is the address of the processor's PCMCIA card, if there is one present).

I have changed the IP addresses in the Address Server and IO Scanner configuration. Should I restart my client/server devices?

Yes. The devices only receive their IP address when starting up. This restart should be carried out once the TSX ETY 410•/PORT/510• module has been reconfigured

(fixed RUN and STS LEDs).

In the module configuration screens, the last entry inserted into one of the grids has not been taken into account on validation. Why?

You need to remove the focus (the scale indicator) from the last cell of the grid in which new data has been entered in order to take this modification into account.

Why is the Bridge tab grayed out when I use a TSX / PMX / PCX processor of type 571xx and 572xx?

These processors do not manage bridge data.

Why is the Bridge tab grayed out when I have already changed the position of the processor?

After this type of modification, you have to validate the new hardware configuration to access and modify the bridge data managed globally at processor level.

287

TSX ETY 410•, TSX ETY PORT, TSX ETY 510• and TSX WMY 100

The momentum 170 ENT modules do not manage to obtain their client/server address from the address server of the TSX ETY 410•, TSX ETY PORT,

TSX ETY 510• or TSX WMY 100 modules.

z z

Check in the TSX ETY 410•/PORT module configuration that the subnetwork mask is correct for the IP address class.

Check the software version of the 170 ENT module.

288

35011050 01 July 2006

Multi-network architectures

III

Introduction

Aim of this part

What's in this

Part?

This part introduces the principles of configuring and using a multi-network architecture via PL7 software.

This part contains the following chapters:

Chapter

10

11

Chapter Name

Multi-network architectures: General

Configuration

Page

291

301

35011050 01 July 2006

289

Multi-network architectures

290

35011050 01 July 2006

Multi-network architectures:

General

10

Introduction

Subject of this chapter

What's in this

Chapter?

This chapter introduces multi-network architectures and associated services.

This chapter contains the following topics:

Topic

General

Functions

Main address

Addresses of a multi-module station

Message handling

Common word service

Shared table exchange service

Page

292

293

295

297

298

299

300

35011050 01 July 2006

291

Multi-network architectures: General

General

Introduction A multi-network architecture is made up of several networks. Two levels of architecture are distinguished: z

Multi-module architectures in which there are several networks but where no communication between these different segments is provided by the z communication system.

Multi-network architectures composed of several network segments interconnected by bridge stations. Transparency of communication is then provided between the group of equipment present in this type of architecture.

This Chapter describes the set-up of the bridge function in a Premium PLC station, as well as the use of communication services in a multi-network architecture. The multi-network architecture complies with X-Way communication standards.

To set up stations on different networks, refer to the documentation corresponding to the module being used.

292

35011050 01 July 2006

Multi-network architectures: General

Functions

Introduction

Terminal stations

Intermediary stations

An X-WAY multi-network automation architecture is composed of several levels of networks interconnected via intermediary stations.

In a multi-network architecture, there must be one logic link between two terminal stations.

Example

Terminal stations

Station {1.1} Station {1.2} network #1 network #2

2

1

3

Station {1.3} and {2.1}

1

Intermediate stations

2

4

Station {1.4} and {3.1}

1 network #3

2

Station {2.2}

Terminal stations

Station {3.2}

A terminal station is addressed by the module (network address, station address).

The terminal stations receive the messages destined for their network address as well as the messages for general broadcast, and send all the messages destined for a remote station to their network connection.

An intermediary station has as many network addresses as it does connection points to different networks. One of its addresses is considered as the main address; it guarantees access to all the communication entities of a bridge station.

The intermediary stations are classified into two categories: z z

Multi-module stations

Bridge stations

35011050 01 July 2006

293

Multi-network architectures: General

Multi-module stations

These manage several network modules; they guarantee all the mono-network services on the different network segments (common words, telegrams, message handling). They do not provide the function of routing between the different network connections.

Note: The telegram exchange service is provided exclusively on the FIPWAY link managed by a Premium or Micro processor.

Bridge stations They supply the same services as the multi-module stations and guarantee transparency of communication between the different network connections.

294

35011050 01 July 2006

Multi-network architectures: General

Main address

Introduction

Rule

A station which is configured in bridge mode has as many addresses as it does network connection points.

The network address which corresponds to the network module with the lowest module address (module the farthest to the left in the station rack) is regarded as the main address of the station.

Using the main address of a station guarantees access to a bridge station.

A bridge station must always be accessed by its main address.

35011050 01 July 2006

295

Multi-network architectures: General

Examples of addressing network #1

The example shows the communication between stations connected on the Fipway networks.

Ethernet

0

1

5 2

2

4 5

R2 R1

Uni-Telway

56

C

Fipway network #11

3 4

B

Fipway network #12

7

0

5 4

5

Fipway network #13

R3

6 Fipway network #21

A z z z z

For a communication from station A to station R2, the main address of station R2 is {11.3}.

For a communication from station A to station R1, the main address of station R1 is {12.7}.

For a communication from station A to station R3, the main address of station R3 is {13.5}.

For a communication from station A to station C, the address of station C is

{12.7}5.0.56.

296

35011050 01 July 2006

Multi-network architectures: General

Addresses of a multi-module station

Introduction

Rule

Example

A station which is configured in multi-module mode has as many addresses as it does network connection points.

There is no main address for the station. It will be addressed according to the network which communicates with it.

A multi-module station must always be accessed via the network address which corresponds to the network module enabling entry to the station.

In the following example, station R1 does not have the bridge function between its modules 2, 4 and 5.

Ethernet

2

2

4 5

R1

7

Fipway network #12

7

B

5 4 Fipway network #13

A z z

For a communication from station A to station R1, the address is {13.5}SYS.

For a communication from station B to station R1, the address is {12.7}SYS.

35011050 01 July 2006

297

Multi-network architectures: General

Message handling

With multimodule stations

Messages destined for a network are sent to the module connected to the destination network. The configuration phase is used to determine the destination module.

Exception

Messages destined for an unknown network address are sent to the station network with the main address, as well as messages whose the network number equals 0.

Example network #3

2

4

READ_VAR(ADR#{3.2}4.1,...)

With bridge stations

READ_VAR(ADR#{2}SYS,...)

READ_VAR(ADR#{1.2}SYS,...)

READ_VAR(ADR#{15.2}SYS,...)

4 network #1

All the messages destined for network #3 are sent to address module 4, and those for which the destination network is 1 to the network link integrated in the processor.

All messages of which the network number address is not equal to 1 or 3 are sent to the processor which manages the main network.

In a multi-module architecture, communication is limited to one single network level.

Messages destined for a network are sent to the module which has access to this network. The configuration phase is used to determine the networks accessible to each station module.

Exception

Messages whose network number is equal to 0 are sent to the station’s main address network.

298

35011050 01 July 2006

Multi-network architectures: General

Common word service

Introduction

Example

Exchanges of common words are only mono-network; they are linked to each module. There can therefore be as many zones of common words as there are network modules in a station.

The access syntax to common words in a configuration is the following:

%NW {N° network. N° station} N° of word

Exchanges of common words are managed by the PLC system.

The update bits associated with each zone of exchanged words are %IWxy.i.1 à

%IWxy.i.4. Please refer to language objects of each module.

In the example below, the station has two common word production zones.

Common word zone

%NW{3.2}0...3

2 network #3

4

%NW{3.2}0...3

%NW{1.4}0...3

4 network #1

Common word zone

%NW{1.4}0...3

The network number allows the accessed zone to be distinguished.

On network #3, it produces 4 mots: %NW {3.2}0..3. The update bits are stored in words: %IW 4.1.1.., %IW 4.1.2.

On network #1, it produces 4 mots: %NW {1.4}0..3. The update bits are stored in words: %IW 0.1.1.., %IW 0.1.2.

35011050 01 July 2006

299

Multi-network architectures: General

Shared table exchange service

Introduction

Example

Exchange of shared tables and the exchange of common words are self-exclusive.

Exchanges of shared tables are only possible in a mono-network architecture.

The exchange zone is in the %MWs defined by the PL7 application. In a multinetwork application, there can be several shared tables with one per network.

A refresh bit which indicates the producer status of a common word zone is associated with each table zone. The bit i = 1 if the station has produced its shared table zone. This information is updated periodically by the system.

In the following example, the station has two shared table zones.

Network #3 shared table

%MW10

%MW20

...

%MW30

...

%MW137

2

4 network #3

%MW200

%MW210

...

%MW230

...

%MW337

4

Network #1 shared table network #1

The zone between the words %MW10 and %MW137 corresponds to the shared table exchanged on network 3.

Only the words %MW20 to %MW30 are produced on the network by the station; the other words are the image of words sent by the other stations.

The zone between the words %MW200 and %MW337 corresponds to the shared table exchanged on network 1.

Only the words %MW210 to %MW230 are produced on the network by the station; the other words are the image of words sent by the other stations.

300

35011050 01 July 2006

Configuration

11

Introduction

Subject of this chapter

What's in this

Chapter?

This chapter describes the Configuration process during set-up of multi-network architectures and associated services.

This chapter contains the following topics:

Topic

Configuration

Configuration of mono-network services

Configuration of multi-network services

How to configure a module as a bridge

Examples of bridge stations

Examples of partial routing

Page

302

303

304

306

308

310

301

35011050 01 July 2006

Multi-network architectures: Configuration

Configuration

Introduction In an intermediary station, the management of several network modules requires a configuration phase to distribute the operating characteristics to the different network entities.

Station {1.1} Terminal stations Station {1.2}

1 network #1

Intermediate stations

4

Station {1.4} and {3.1}

2

Station {2.2}

Terminal stations network #3 1

2

Station {3.2}

PL7 Station configuration

302

CAUTION

Coherence of routing data

Multi-network routing information is put together at station level during

PL7 configuration of each bridge. No verification of the coherence of the routing data of one network architecture is made.

Failure to follow this precaution can result in injury or equipment damage.

35011050 01 July 2006

Multi-network architectures: Configuration

Configuration of mono-network services

Introduction The PL7 configuration screen of the application-specific function (FIPWAY,

ETHERNET) is used to enter the information necessary for the operation of the different types of exchange on the network: telegrams, common words, shared tables, mono-station message handling.

Exchanges of common words and shared tables are exclusive to one network.

However, it is possible to combine them in a multi-module configuration. For example, a station can participate in an exchange of common words on one network, and in a shared table exchange on its second network attachment.

Telegrams can be used only on the Fipway channel managed by the PCMCIA card of the processor reception channel.

35011050 01 July 2006

303

Multi-network architectures: Configuration

Configuration of multi-network services

Introduction

Illustration

In a station which supports several network modules, each network connection point is regarded as an address for the station. During configuration of each module, it is necessary to define the list of accessible network numbers for each connection point.

Depending on the processor which has been chosen in the hardware configuration, a bridge station can only manage 3 or 4 network modules; the table will therefore have a maximum of 4 elements.

1

2

A specific screen is used for entering the routing data for all the network modules of a station.

3

4

Bridge Configuration

Data module Data module Data module Data module

2 3 4

FIPWAY

12

Save

ETHWAY

1

11

FIPWAY

13

21

Delete

Select accessible networks

Access. networks Avail. networks

12

Cancel

8

9

6

7

10

4

5

2

3

Accept Cancel

304

35011050 01 July 2006

Elements and functions

Multi-network architectures: Configuration

This table describes the different areas that make up the configuration screen:

2

3

Address Zone

1 module slot

Network type

List of

Accessible

Networks

Function allows you to view the position of the module in the rack.

allows you to view the network type.

It is used: z z for the non grayed out Module zone, to enter the list of networks accessible from this module, for the grayed out Module zones, to view the list of networks accessible to these modules,

4 Select

Accessible

Networks is used to select the networks accessible to a module configured as a bridge.

A list of numbers from 1 to 127 represents the networks available for a connection point. Each network number selected as being accessible is removed from the list of available networks in order to avoid configuration errors.

35011050 01 July 2006

305

Multi-network architectures: Configuration

How to configure a module as a bridge

Introduction Before configuring the module as a bridge, access the Bridge Configuration screen.

Note: Access to this screen depends on the type of module configured in the station. Refer to the module which you are configuring.

Procedure The following procedure is used to configure the station module as a bridge.

Step

1

Action

Double-click on the zone in reverse video.

Result

The Select accessible networks window appears.

Select accessible networks

Access. networks Avail. networks

12

8

9

6

7

10

4

5

2

3

Accept Cancel

2

3

4

5

If the list of networks accessible to the module is empty, the window appears automatically (without double-clicking).

Double-click on the network number in the drop-down list Available networks .

Result

The network number is assigned to the drop-down list Accessible networks .

Perform operation 3 as many times as is necessary to define all the networks which are accessible to the module.

Then proceed to step 5.

Confirm the selection by clicking on Ok .

Confirm the bridge configuration by clicking on Save .

306

35011050 01 July 2006

Multi-network architectures: Configuration

How to delete the bridge function

It is possible to delete the module bridge function.

Step

1

2

3

Action

Access the Bridge Configuration screen.

Click on Delete .

Confirm the deletion by clicking on Save .

How to delete access to a network

It is possible to delete access to one network only.

Step

1

2

3

Action

Access the Bridge Configuration screen.

Double-click on the zone in reverse video.

Double-click on the network number in the drop-down list Accessible networks .

4

5

Result

The network number is reassigned to the drop-down list Available networks .

Confirm the selection by clicking on Ok .

Confirm the bridge configuration by clicking on Save .

35011050 01 July 2006

307

Multi-network architectures: Configuration

Examples of bridge stations

Introduction network #1

Each station must be configured in order to define the list of accessible networks.

ETHERNET

0

1

5

2

2

4 5

UNI-TELWAY

R2 R1

C

FIPWAY network #11

3 4

B

FIPWAY network #12

7

0

5 4

5

FIPWAY network #13

R3

6

A

FIPWAY network #21

Configuration of station R1

The module at slot 2 can only access network #12.

The module at slot 4 can access networks #1 and #11.

The module at slot 5 can access networks #13 and #21.

The bridge configuration of the station is therefore as follows:

Bridge Configuration

Data module Data module Data module Data module

2 3 4

FIPWAY

12

ETHWAY

1

11

FIPWAY

13

21

Save Delete Cancel

308

35011050 01 July 2006

Multi-network architectures: Configuration

Configuration of station R2

The module at slot 0 can only access network #11.

The module at slot 5 can access networks #1, #2, #13 and #21.

The bridge configuration of the station is therefore as follows:

Bridge Configuration

Data module Data module Data module Data module

0 5

FIPWAY ETHWAY

11 1

12

13

21

Save Delete Cancel

Configuration of station R3

The module at slot 0 can access networks #13, #2, #1 and #11.

The module at slot 5 can only access network #21.

The bridge configuration of the station is therefore as follows:

Bridge Configuration

Data module Data module Data module Data module

0 5

FIPWAY

1

11

12

13

FIPWAY

21

Save Delete Cancel

35011050 01 July 2006

309

Multi-network architectures: Configuration

Examples of partial routing

Introduction During configuration of a module as a bridge, it is possible not to assign it all the accessible networks, but to assign only a part of them to it. This selection defines a partial routing.

Illustration network #1

Each station must be configured in order to define the list of accessible networks.

ETHERNET

0

1

5

2

2

4 5

UNI-TELWAY

R2 R1

C

FIPWAY network #11

3 4

B

FIPWAY network #12

7

0

5 4

5

FIPWAY network #13

R3

6

A

FIPWAY network #21

310

35011050 01 July 2006

Multi-network architectures: Configuration

Configuration of station R1

The module at slot 2 does not participate in data routing.

The module at slot 4 can access networks #1 and #11,

The module at slot 5 can access networks #13 and #21.

The bridge configuration of the station is therefore as follows:

Bridge Configuration

Data module Data module Data module Data module

4 5

ETHWAY

1

11

FIPWAY

13

21

Save Delete Cancel

Configuration of station R2

The module at slot 0 can only access network #11.

The module at slot 5 can access networks #1, #13 and #21. Network #12 is inaccessible.

The bridge configuration of the station is therefore as follows:

Bridge Configuration

Data module Data module Data module Data module

0 5

FIPWAY ETHWAY

11 1

13

21

Save Delete Cancel

35011050 01 July 2006

311

Multi-network architectures: Configuration

Configuration of station R3

The module at slot 0 can access networks #13, #1 and #11. Network #12 is no longer accessible.

The module at slot 5 can only access network #21.

The bridge configuration of the station is therefore as follows:

Bridge Configuration

Data module Data module Data module Data module

0 5

FIPWAY

1

11

13

FIPWAY

21

Save Delete Cancel

312

35011050 01 July 2006

Index

A

Accessing the configuration

FIPWAY, 30

address

IP, 66

Adressing

Multi-network architectures, 295

B

bandwidth, 130

BOOTP, 89

Bridge, 289

Broken connection, 80

C

Characteristics

ETHERNET (TSX ETY 410•, TSX ETY

PORT, TSX ETY 510• and TSX WMY

100), 222

Fipway, 24

characteristics

TCP/IP, 63

Common words, 20

Multi-network architectures, 299

Communication channel test

FIPWAY, 41

Compatibility

FIPWAY, 25

Fipway, 26

35011050 01 July 2006

A C

Configuration

Bandwidth, 262

BOOTP, 248

DHCP, 250

Ethernet (TSX ETY 110), 178

ETHERNET (TSX ETY 410•, TSX ETY

PORT, TSX ETY 510• and TSX WMY

100), 234

Fipway, 29

Global Data, 252

IO Scanning, 245

Multi-network architectures, 301

configuration

BOOTP, 147

DHCP, 147

Global Data, 154

Configuration parameters

FIPWAY, 32, 33

Configuration screen

ETHERNET (TSX ETY 110), 179

FIPWAY, 31

configuration screen

ETHERNET (TSX ETY 410), 236

Connection closure, 79

Connection opening, 77

connections

ETHERNET (TSX ETY 410•/PORT/510• and TSX WMY 100), 225

313

Index

D

debugging

ETHERNET (TSX ETY 410•, TSX ETY

PORT, TSX ETY 510• and TSX WMY

100), 265

Global Data, 276

IO Scanning, 275

Debugging parameters

FIPWAY, 39

Debugging screen

ETHERNET (TSX ETY 110), 198

FIPWAY, 38

debugging screen

ETHERNET (TSX ETY 410•), 266

DHCP, 89

Diagnostics

Bandwidth, 277

E

ETHERNET, 53

Introduction, 56

Modbus, 71

UNI-TE, 70

Ethernet

Configuration parameters, 133

Facilities, 61

Ethernet (TSX ETY 110)

characteristics, 174

Debugging, 197

general points, 172

ETHWAY

TCP/IP, 131

ETHWAY Profile

Configuration, 167

Exchange management

FIPWAY, 51

Explicit exchange

ETHERNET (TSX ETY 110), 213

ETHERNET (TSX ETY 410•/PORT/510• and TSX WMY 100), 281

FIPWAY, 48

314

F

FAST, 102

faulty device, 101

FIPWAY, 13

function blocks

FAST, 102

MAST, 102

G

General

ETHERNET (TSX ETY 410•, TSX ETY

PORT, TSX ETY 510• and TSX WMY

100), 220

Fipway, 15

Multi-network architectures, 291

General points

Ethernet, 55

Global Data, 98

H

HTTP, 103, 104

address server, 114

Data editor, 119

Ethernet module diagnostics, 121

Rack display, 117

security, 111

user pages, 129

I

Identification

ETHERNET, 272

Ethernet, 205

FIPWAY, 42

Implicit exchange

ETHERNET (TSX ETY 410•/PORT/510• and TSX WMY 100), 279

FIPWAY, 46 implicit exchange

ETHERNET (TSX ETY 110), 210

Introduction

Fipway, 16

35011050 01 July 2006

IO Scanning, 82

Configuration, 141

L

Language objects

ETHERNET (TSX ETY 110), 209

ETHERNET (TSX ETY 410•,TSX ETY

PORT, TSX ETY 510• and TSX WMY

100), 278

FIPWAY, 45

M

Management of exchanges

ETHERNET (TSX ETY 110), 215

ETHERNET (TSX ETY 410), 283

MAST, 102

migration, 235

Mirror

ETHERNET, 272

Ethernet, 205

FIPWAY, 42

Multi-network architectures, 289

O

Operating mode

ETHERNET (TSX ETY 410•,TSX ETY

PORT, TSX ETY 510• and TSX WMY

100), 232

FIPWAY, 28

P

parameters

setting daylight savings time, 165, 258

setting NTP server IP address, 165, 258

setting synchronization period, 165, 258 setting time zone, 165, 258

Partial routing, 310

Performance

Fipway, 27

TSX ETY 410• module, 227

Ping, 202, 270

35011050 01 July 2006

Q

questions/answers, 286

R

Read

IO Scanning, 86

Report

ETHERNET (TSX ETY 110), 215

ETHERNET (TSX ETY 410), 283

FIPWAY, 51

Requests

Ethernet, 207, 273

FIPWAY, 44

Index

S

Services

FIPWAY, 18

Shared tables, 22

Multi-network architectures, 300

SNMP, 95

Configuration, 150

Sub addressing

Subnetwork mask, 68

T

TCP/IP, 62

Configuration, 134

ETHWAY, 131

time zones, 160, 259

customizing, 166, 259

traps

setting, 165, 258

TSX ETY 110, 171

TSX ETY 110 Coupler

Performances, 175

TSX ETY 410•, 219

TSX ETY 510•, 219

TSX ETY PORT, 219

TSX WMY 100, 219

tz compilers, 166, 259

315

Index

W

Web pages

NTP Configuration, 164, 257

Write

IO Scanning, 86

316 35011050 01 July 2006