Schneider Electric PL7 Micro/Junior/Pro, Communication applications, Volume 2 User Guide

PL7 Micro/Junior/Pro

Communication applications

Volume 2

07/2008 eng www.schneider-electric.com

2

Document Set

At a Glance This manual has 3 volumes: z z z

Volume 1 z z

Common communication function

Remoting of Nano PLCs z z

Communication by character mode

Communication by Uni-telway bus

Volume 2 z Communication by Modbus z z

Communication by modem

Communication by Modbus plus z Communication by FIPIO bus

Volume 3 z z z

Communication by FIPWAY network

Communication by ETHERNET network

Multi-network architecture

Document Set

35013154.02 07/2208

3

Document Set

4

35013154.02 07/2208

Table of Contents

About the Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Part I

Communication via Modbus . . . . . . . . . . . . . . . . . . . . . . 15

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

Chapter 1

General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

About Modbus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Compatibilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Compatibility between a TSX 37/57 PLC and a series 1000 PLC. . . . . . . . . . . . 20

Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Operating Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Chapter 2

Configuring Modbus communication . . . . . . . . . . . . . . . . . . . . 25

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

How to access the Modbus PCMCIA card parameters . . . . . . . . . . . . . . . . . . . . 26

How to access the terminal port parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

How to Access Parameters for TSX SCY 11601/21600/21601 Modules . . . . . . 28

Modbus Configuration Screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Accessible Modbus Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Application linked Modbus Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Modbus Parameters relating to transmission . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Chapter 3

Programming Modbus communication . . . . . . . . . . . . . . . . . . 37

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

Modbus Master Communication Function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Modbus Slave Communication Function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Using the SEND_REQ communication function . . . . . . . . . . . . . . . . . . . . . . . . . 42

Example 1: SEND_REQ function with Echo request . . . . . . . . . . . . . . . . . . . . . 43

Example 2: SEND_REQ function with Word read request. . . . . . . . . . . . . . . . . 44

Example 3: SEND_REQ Function with Bit Read Request . . . . . . . . . . . . . . . . . 46

Example 4: READ_VAR function for reading bits . . . . . . . . . . . . . . . . . . . . . . . . 48

Chapter 4

Debugging Modbus communication. . . . . . . . . . . . . . . . . . . . . 49

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

35013154.02 07/2208

5

6

Modbus debug screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Modbus Master debugging screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Debug screen in Modbus slave type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

How to test a communication channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Chapter 5

Language objects associated with Modbus communication 55

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

Implicit exchange language object for a Modbus function . . . . . . . . . . . . . . . . . . 56

Explicit exchange language objects for a Modbus function . . . . . . . . . . . . . . . . . 58

Explicit exchange management and report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Language objects associated with the configuration . . . . . . . . . . . . . . . . . . . . . . 62

System objects of the Modbus function on Terminal port . . . . . . . . . . . . . . . . . . 64

Part II

Communication via Modem . . . . . . . . . . . . . . . . . . . . . . . 65

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Chapter 6

Communication via Modem . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

6.1

Introduction to communication via Modem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Modems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Standard configuration for communication via modem . . . . . . . . . . . . . . . . . . . . 70

Other configurations for communication via modem . . . . . . . . . . . . . . . . . . . . . . 71

Principles of communication between two stations . . . . . . . . . . . . . . . . . . . . . . . 73

6.2

Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Hardware Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Software compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

6.3

Setting up communication via Modem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Set up methodology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Setting up UNI-TELWAY communication between PLCs via the TSX MDM 10 card

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Communication between PLCs using an external modem . . . . . . . . . . . . . . . . . 83

Setting up communication from PL7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

How to configure the Uni-telway driver with a modem. . . . . . . . . . . . . . . . . . . . . 86

How to Configure Modem Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

How to Modify the Modem Link Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Chapter 7

Configuring Modem communication . . . . . . . . . . . . . . . . . . . . 89

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

How to access PCMCIA modem card parameters . . . . . . . . . . . . . . . . . . . . . . . 90

Modem configuration screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Parameters in Uni-telway mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Parameters in character mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Modem parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

35013154.02 07/2208

Modem parameters for a called station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Modem parameters for a calling station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Chapter 8

Programming Modem communication . . . . . . . . . . . . . . . . . . 101

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

CALL_MODEM communication function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Modem specific management parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Coding of exchanges. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Guide to choosing connection parameters in Uni-telway mode . . . . . . . . . . . . 109

Guide to choosing connection parameters in character mode . . . . . . . . . . . . . 112

Examples of connection, disconnection, and reset with a remote station . . . . . 114

Examples of communication between two PLCs . . . . . . . . . . . . . . . . . . . . . . . 116

Chapter 9

Debugging Modem communication . . . . . . . . . . . . . . . . . . . . 119

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Modem debugging screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

Debugging parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

Chapter 10

Language objects associated with Modem communication 123

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

Language objects in implicit exchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

Language objects for explicit exchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

Explicit exchange management and reports . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

Language objects associated with configuration. . . . . . . . . . . . . . . . . . . . . . . . 130

Chapter 11

Appendices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

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

AT commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

A/ - Command re-execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

AT = x - Write to the selected S register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

AT? - Read the selected S register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

A - Answer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

Cn - Checking for carrier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

Dn - Dialing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

En - Local command echo. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

Hn - Disconnection (hang up) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

In - Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

Ln - Loudspeaker volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

Mn - Loudspeaker command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

Nn - Activation of automatic mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

On- Return to on-line data mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

P - Default adjustment of pulse dialing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

Qn - Activation / deactivation of result codes . . . . . . . . . . . . . . . . . . . . . . . . . . 152

Sn - S register read / write. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

T - Default adjustment of tone dialing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154

Vn - Form of the result codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

35013154.02 07/2208

7

8

Wn - Error correction messages control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

Xn - Extended result codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

Yn - Disconnection after prolonged inactivity. . . . . . . . . . . . . . . . . . . . . . . . . . . 161

Zn - Software reset of modem and restoration of profile . . . . . . . . . . . . . . . . . . 162

&Cn - RLSD Option (detection of DCD carrier) . . . . . . . . . . . . . . . . . . . . . . . . . 163

&Dn - DTR Option (Data Terminal Ready) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164

&Fn - Restoration of the factory configuration (profile) . . . . . . . . . . . . . . . . . . . 165

&Gn - Selection of guard tone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

&Kn – Flow control. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

&Pn - Selection of pulse dialing close/open report . . . . . . . . . . . . . . . . . . . . . . 168

&Qn - Synchronous/asynchronous mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

&Rn - RTS/CTS option. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

&Sn - DSR Monitoring (Data Station Ready) . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

&V - Display of current configuration and stored profiles. . . . . . . . . . . . . . . . . . 172

&Wn – Storage of the current configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

&Yn - Designation of a default profile on reset . . . . . . . . . . . . . . . . . . . . . . . . . 174

&Zn – Storage of telephone numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

%Cn - Activation / deactivation of data compression. . . . . . . . . . . . . . . . . . . . . 176

%En - Activation/deactivation of line quality monitoring or automatic resynchroni-

zation or fallback/increase of transfer rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177

%L - Level of line signal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178

%Q - Quality of line signal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

\Kn - BREAK control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180

\Nn - Operating mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182

Values of the registers of the TSX MDM 10 card in a PLC . . . . . . . . . . . . . . . . 183

Part III

Communication via Modbus Plus . . . . . . . . . . . . . . . . . 185

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

Chapter 12

General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188

Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189

Integration into an X-WAY architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190

Integration into a Modbus Plus architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . 193

Chapter 13

Peer Cop service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195

Peer Cop Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195

Chapter 14

Configuring Modbus Plus communication . . . . . . . . . . . . . . 199

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199

How to access the Modbus Plus PCMCIA card parameters . . . . . . . . . . . . . . . 200

Modbus Plus configuration screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201

Functions accessible from Modbus Plus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202

Modbus Plus configuration parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203

Configuring the specific inputs and outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204

35013154.02 07/2208

Chapter 15

Programming Modbus Plus communication . . . . . . . . . . . . . 207

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207

Read and write service on local segment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208

Exchange service on remote Modbus Plus networks . . . . . . . . . . . . . . . . . . . . 210

Examples of Exchanges on Remote Networks . . . . . . . . . . . . . . . . . . . . . . . . . 212

Diagnostic service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215

Global data exchange service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217

Chapter 16

Debugging Modbus Plus communication . . . . . . . . . . . . . . . 219

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219

Modbus Plus debugging screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220

Modbus Plus debugging screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221

Chapter 17 Language objects associated with Modbus Plus

communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223

Implicit Exchange Language Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224

Explicit exchange language object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227

Explicit exchange management and report . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229

Language objects associated with configuration. . . . . . . . . . . . . . . . . . . . . . . . 230

Part IV

Communication via FIPIO bus . . . . . . . . . . . . . . . . . . . 233

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233

Chapter 18

Communication via FIPIO bus. . . . . . . . . . . . . . . . . . . . . . . . . 235

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235

18.1

Introduction to Fipio communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237

Addressing of Remote Module Language Objects on a FIPIO Bus . . . . . . . . . 238

18.2

Characteristics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241

Hardware compatibility relating to the bus manager . . . . . . . . . . . . . . . . . . . . . 242

Software compatibility relating to the bus manager. . . . . . . . . . . . . . . . . . . . . . 243

Software compatibility: Network transparency . . . . . . . . . . . . . . . . . . . . . . . . . 244

Software compatibility: communication with the exterior. . . . . . . . . . . . . . . . . . 246

Compatibility information relating to TBX devices . . . . . . . . . . . . . . . . . . . . . . . 248

Compatibility information relating to Momentum devices . . . . . . . . . . . . . . . . . 250

Compatibility information relating to the programming terminal . . . . . . . . . . . . 251

Compatibility information relating to other devices . . . . . . . . . . . . . . . . . . . . . . 252

FIPIO bus operating mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254

Network cycle time: mono task application . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256

Network cycle time: multitasking application . . . . . . . . . . . . . . . . . . . . . . . . . . . 258

Example of calculating the network cycle times of a multitasking application. . 261

Chapter 19

Configuring Fipio communication . . . . . . . . . . . . . . . . . . . . . 263

35013154.02 07/2208

9

10

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263

19.1

General information on configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264

Configuration mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264

19.2

Fipio bus configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265

How to access the FIPIO configuration screen . . . . . . . . . . . . . . . . . . . . . . . . . 266

FIPIO bus configuration screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267

How to add a device on to the bus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269

How to modify/delete/move/duplicate a bus device . . . . . . . . . . . . . . . . . . . . . . 272

How to access the FIPIO bus properties screen . . . . . . . . . . . . . . . . . . . . . . . . 274

FIPIO bus properties configuration screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275

Properties of the Fipio Bus: General Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276

Properties of the Fipio bus: Expert tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278

Expert Tab: Manual Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279

19.3

Configuration of devices on the Fipio bus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282

How to access the FIPIO configuration screen . . . . . . . . . . . . . . . . . . . . . . . . . 283

Configuration screen of a FIPIO device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284

How to access the different parameters according to device type. . . . . . . . . . . 286

19.4

Input/output management by the PL7 tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . 287

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287

How to access PL7 task configuration in FIPIO mode. . . . . . . . . . . . . . . . . . . . 288

Configuration screen of a FIPIO processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289

FIPIO input/output management using PL7 tasks . . . . . . . . . . . . . . . . . . . . . . . 290

19.5

Confirmation of the Fipio bus configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291

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

Confirming the configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292

Confirmation refused, examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294

Chapter 20

Programming Fipio communication . . . . . . . . . . . . . . . . . . . 297

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297

FIPIO error processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298

Examples of explicit exchange saturation detection . . . . . . . . . . . . . . . . . . . . . 300

Chapter 21

Debugging a Fipio communication . . . . . . . . . . . . . . . . . . . . 303

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303

Debugging mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304

How to access the remote device debugging screens. . . . . . . . . . . . . . . . . . . . 305

FIPIO bus device debugging screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306

Chapter 22

Fipio communication diagnostics . . . . . . . . . . . . . . . . . . . . . 309

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309

Diagnostics mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310

How to access the FIPIO bus monitoring screen. . . . . . . . . . . . . . . . . . . . . . . . 311

Diagnostics screen: FIPIO bus monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312

How to access the device monitoring screen. . . . . . . . . . . . . . . . . . . . . . . . . . . 314

35013154.02 07/2208

Diagnostics screens: device monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315

How to access the monitoring screen for one device . . . . . . . . . . . . . . . . . . . . 317

Diagnostics screen: single device monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . 318

How to access the communication error history screen . . . . . . . . . . . . . . . . . . 320

Diagnostics screen: communication error history . . . . . . . . . . . . . . . . . . . . . . . 321

Chapter 23

Language objects associated with Fipio communication . . 323

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323

Language objects in implicit exchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324

Language object for explicit exchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325

Explicit exchange management and reports . . . . . . . . . . . . . . . . . . . . . . . . . . . 328

Chapter 24

Fipio communication standard profiles . . . . . . . . . . . . . . . . . 329

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329

24.1

Introduction to standard Fipio communication profiles . . . . . . . . . . . . . . . . . . . 330

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330

Standard profiles: general . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331

Designation of a standard profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332

List of the standard profiles proposed in catalog by PL7. . . . . . . . . . . . . . . . . . 334

24.2

Configuration of the Fipio bus standard profiles . . . . . . . . . . . . . . . . . . . . . . . . 336

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336

Configuration screen of a standard profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337

How to modify the parameters of a standard profile . . . . . . . . . . . . . . . . . . . . . 339

Adjustment mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341

24.3

Debugging the Fipio bus standard profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342

Debugging screen of a standard profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343

How to modify the debugging parameters of a standard profile . . . . . . . . . . . . 345

24.4

Language objects associated with the Fipio bus standard profiles . . . . . . . . . . 347

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347

Summary of the objects which can be accessed via the standard profiles . . . . 348

Language objects in implicit exchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351

Language object for explicit exchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353

Language objects associated with configuration. . . . . . . . . . . . . . . . . . . . . . . . 356

Chapter 25

Fipio Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357

25.1

Introduction to Fipio Agents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358

FIPIO Agent: General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359

Periodic data exchange. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360

Special cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362

Communication from an FIPIO Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364

25.2

Configuration of Fipio Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366

How to access the FIPIO Agent parameters via PCMCIA cards. . . . . . . . . . . . 367

35013154.02 07/2208

11

FIPIO Agent configuration screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368

25.3

Debugging Fipio Agents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369

FIPIO Agent debugging screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369

25.4

Language objects associated with the Fipio Agents . . . . . . . . . . . . . . . . . . . . . 370

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370

Language objects in implicit exchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371

Language object for explicit exchange. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372

Explicit exchange management and reports . . . . . . . . . . . . . . . . . . . . . . . . . . . 373

Language objects associated with configuration . . . . . . . . . . . . . . . . . . . . . . . . 374

Index

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375

12

35013154.02 07/2208

About the Book

At a Glance

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

Validity Note The updated version of this publication takes into account the functionalities of PL7

V4.5.

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

35013154.02 07/2208

13

About the Book

14

35013154.02 07/2208

Communication via Modbus

I

Introduction

Subject of this part

What's in this

Part?

This part introduces the principles of configuring and communicating with Modbus via PL7 software.

This part contains the following chapters:

Chapter

1

2

3

4

5

Chapter Name

General

Configuring Modbus communication

Programming Modbus communication

Debugging Modbus communication

Language objects associated with Modbus communication

Page

17

25

37

49

55

15

35013154.02 07/2008

Communication via Modbus

16

35013154.02 07/2008

General

1

Introduction

Aim of this

Chapter

What's in this

Chapter?

This Chapter introduces Modbus communication and its services.

This chapter contains the following topics:

Topic

About Modbus

Compatibilities

Compatibility between a TSX 37/57 PLC and a series 1000 PLC

Performance

Operating Mode

Page

18

19

20

22

23

35013154.02 07/2008

17

Modbus communication: General

About Modbus

Introduction

Associated manuals

Communication by Modbus allows data to be exchanged between all devices connected to the bus. Modbus is a protocol which creates a hierarchical structure

(one master and several slaves).

z z

The master manages all exchanges according to two types of dialog: the master exchanges data with the slave and awaits a response, the master exchanges data with all slaves and does not await a response

(general broadcast).

For further information, you may consult the following manuals:

Title

Modbus - User guide

Micro PLCs - Installation manual

Premium PLCs - Installation manual

Description

Detailed description of Modbus protocol

Hardware implementation

See manual TSX DM 37_T3.

Hardware implementation

See manual TSX DM 57_T4.

18

35013154.02 07/2008

Modbus communication: General

Compatibilities

Hardware

Software

This communication type is available for z Premium PLCs through: z z a PCMCIA TSX SCP 111 card associated with the RS232 physical layer, a PCMCIA TSX SCP 112 card associated with 20 mA current loops, z z a PCMCIA TSX SCP 114 card associated with RS422 and RS485 physical layers, a Built-in Link with a TSX SCY 11601/21600 / 21601 module associated with the RS485 physical layer.

z z z

Version V3.3 Micro is configured in slave mode through the terminal port associated with the RS485 physical layer.

Version V5.0 micro is configured in master mode (TSX 37-10/21/22 only) or in slave mode through the terminal port associated with the RS485 physical layer.

The micro supports the PCMCIA cards described above.

The maximum frame size is 256 bytes.

PCMCIA cards and the TSX SCY 11601/21600 / 21601 module's built-in link can process 8 communication functions at once in Modbus master mode.

Modbus master mode is only available on the Terminal Port from version V4.2 of the

PL7 software. It is not possible to download a Modbus master configured application to a Micro of version V5.0 or below.

The PL7 program's MAST task can, in Modbus master mode, process up to 4 communication functions at once via the Terminal Port. In addition, an error code is sent.

The READ_VAR communication function can read up to 1000 consecutive bits in any remote device. To read more than 1000 bits, the SEND_REQ communication function must be used.

Note: Nano, Micro and Premium PLCs cannot send more than 1000 bits after a read request.

35013154.02 07/2008

19

Modbus communication: General

Compatibility between a TSX 37/57 PLC and a series 1000 PLC

At a Glance

Memory addressing

The READ_VAR and WRITE_VAR functions are used to read and write objects contained in series 1000 PLCs. These include words, double words, floating points and character strings.

The address of the object in the series 1000 PLC memory determines the type of the object to be accessed.

This table shows the access addresses for a series 1000 APRIL5000 PLC with memory extension.

Type of variable APRIL5000 with extension

PLC address

%M internal bits

%MW data words

%MD data words

%FD data words

%CH data words

%M0

%M4095

%MW0

%MW24999

%MD25000

%MD26998

%FD27000

%FD28998

%CH29000

%CH43903

Access address (in hexadecimal)

A000

AFFF

0

61A7

61A8

6976

6978

7146

7148

AB7F

Programming rules

When you wish to access the objects of a series 1000 PLC, the index of the first object to read (or write) is the access address.

Example: z Read %M0 bit z

READ_VAR(ADR#0.1.3, ‘%M’, 16#A000 , 1, ...)

Read word %MD25000

READ_VAR(ADR#0.1.3, ‘%MW’, 16#61A8 , 2, ...)

Moreover, these communication functions cannot be used to exchange double words or character strings via the Modbus protocol. If needed, it is possible to perform the transfer in %MW form, the application must determine the direction in which the words are stored .

The diagnostics functions can be accessed via the SEND_REQ function.

20

35013154.02 07/2008

Compatibility between a

TSX 37/57 PLC and a Quantum

PLC or

Micrologic device

Descriptive table:

%M0

%MW0

Quantum

00001

40001

Modbus communication: General

Micrologic

%M1

%MW1

35013154.02 07/2008

21

Modbus communication: General

Performance

At a Glance

Exchange time for 1 word

The following tables enable you to evaluate typical exchange times according to different criteria.

The results displayed correspond to an average operation period of the READ_VAR function in ms.

Number of objects read: 1 word

Speed in bits/s T cycle (ms) Average duration (ms)

TSX SCP 114

Average duration (ms)

TSX SCY 11601/21600/21601

4800 cyclic 105 120

4800

4800

9600

9600

9600

19200

19200

19200

10

50 cyclic

10

50 cyclic

10

50

133

152

74

86

149

57

60

100

140

172

90

110

172

75

90

118

Exchange time for 100 words

Number of objects read: 100 words

Speed in bits/s T cycle (ms) Average duration (ms)

TSX SCP 114

Average duration (ms)

TSX SCY 11601/21600/21601

4800

4800

4800 cyclic

10

50

616

637

700

630

650

730

9600

9600

9600

19200

19200

19200 cyclic

10

50 cyclic

10

50

357

367

405

215

216

251

375

390

425

228

239

280

22

35013154.02 07/2008

Modbus communication: General

Operating Mode

At a Glance

General Graph

The following graphics show operating modes for PCMCIA Modbus cards, built-in links in TSX SCY11601/21600/21601 modules and for the Terminal Port.

The operating mode is as follows:

Module Stop

No current

Apply voltage

Operation

Module configured

Communication function

Auto-testing

Reset

Module not configured!

Auto-tests OK

Configuration z z z z

After applying voltage, the module carries out auto-tests. Display indicators flash during this phase.

If there is no PL7 application in the PLC, the module awaits configuration.

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

When there is a power outage, the PLC procesor carries out a hot restart. The module then restarts its auto-test procedures.

35013154.02 07/2008

23

Modbus communication: General

24

35013154.02 07/2008

Configuring Modbus communication

2

Introduction

Subject of

Chapter

What's in this

Chapter?

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

This chapter contains the following topics:

Topic

How to access the Modbus PCMCIA card parameters

How to access the terminal port parameters

How to Access Parameters for TSX SCY 11601/21600/21601 Modules

Modbus Configuration Screen

Accessible Modbus Functions

Application linked Modbus Parameters

Modbus Parameters relating to transmission

Page

26

27

28

29

30

31

33

35013154.02 07/2008

25

Modbus configuration

How to access the Modbus PCMCIA card parameters

Introduction

How to access the link

This operation describes how to access the configuration parameters of the Modbus link via the intermediary of PCMCIA cards for Premium PLCs.

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

Step

1

2

Action

Access the communication channel configuration screen.

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

Example

CHANNEL 1

CHANNEL 1 (No PCMCIA submodule)

CHANNEL 0

CHANNEL 1

MAST

3 Select one of the following PCMCIA cards from the drop-down menu: z z z

TSX SCP 111 PCMCIA CARD RS232 MP

TSX SCP 112 PCMCIA CARD BC MP

TSX SCP 114 PCMCIA CARD RS485 MP

Example

CHANNEL 1

CHANNEL 1 TSX SCP 114 PCMCIA CARD RS485 MP

(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

4 Select the link from the drop-down menu MODBUS/JBUS LINK:

Example

CHANNEL 1:

CHANNEL 1 TSX SCP 114 PCMCIA CARD RS 485 MP

(Link not configured)

(Link not configured)

UNI-TELWAY LINK

CHARACTER MODE LINK

MODBUS/JBUS LINK

MAST

26

35013154.02 07/2008

Modbus configuration

How to access the terminal port parameters

Introduction

How to access the link

This operation describes how to access the configuration parameters of the Modbus link via the intermediary of the terminal port of the Micro PLC.

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

Step

1

2

Action

Access the communication channel configuration screen.

Select the link from the drop-down menu MODBUS/JBUS LINK:

Example

VOIE 0:

CHANNEL 0 Terminal Port

UNI-TELWAY LINK

UNI-TELWAY LINK

CHARACTER MODE LINK

MODBUS/JBUS LINK

MAST

35013154.02 07/2008

27

Modbus configuration

How to Access Parameters for TSX SCY 11601/21600/21601 Modules

At a Glance This part describes how to access the configuration parameters of the Modbus link from TSX SCY 11601/21600/21601 modules for the Premium.

Note: For the TSX SCY 11601, given that there is only one channel (CHANNEL 0) and one link (MODBUS/JBUS) channel 0 is configured by default.

Note: If one of the communication channels of module TSX SCY 21600/21601 is faulty (ERR LEDs flashing), the other channel will not operate even if it is configured properly.

How to Access the Link

The following table shows the steps to follow in order to access the Modbus link:

Step

1

2

Action

Access the configuration screen for the communication channel of the selected module

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

Example

CHANNEL 0

CHANNEL 0

CHANNEL 1

(No PCMCIA sub-module)

(Link not configured) MAST

3 From the drop-down menu select the link MODBUS/JBUS LINK:

Example

CHANNEL 1:

CHANNEL 0 (No PCMCIA sub-module)

(Link not configured)

(Link not configured)

UNI-TELWAY LINK

CHARACTER MODE LINK

MODBUS/JBUS LINK

MAST

28

35013154.02 07/2008

Modbus configuration

Modbus Configuration Screen

At a Glance

Illustration

This screen is split into two and enables the declaration of the communication channel and configuration of parameters necessary for a Modbus/Jbus link.

The Modbus Communication Screen looks like this:

TSX 57252 [RACK 0 POSITION 0]

Configuration

Designation: TSX P 5725 PROCESSOR

1

2

CHANNEL 1:

CHANN TSX SCP 114 PCMIA RS485 MP CARD

MODBUS/JBUS LINK MAST

Type

Master

Configuration

Master

Number of retries

100 Response Time

Slave

Slave number

(PSR) Current Loop

Multidrop

98

3

X 10 ms

Point-to-Point

Transmission Speed

9600 Bits/s

Delay between characters

Default 4 ms

Data

ASCII (7 bits)

RTU (8 bits)

Stop

1 bit

2 bits

Parity

Even Odd None

RTS / CTS Delay

0 X100 ms Data Carrier (DCD)

Nodes and

Functions

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

Address Zone

1 common

2 specific

Function

(See : PL7 Micro/Junior/Pro ; Communication applications ;

Volume 1) allows you to select or complete the parameters of a Modbus z z link.

It is broken down into two types of information: application parameters, transmission parameters.

35013154.02 07/2008

29

Modbus configuration

Accessible Modbus Functions

At a Glance

Accessible

Functions

Functions

Master

Slave

(PSR) Current Loop

Transmission Speed

Delay between characters

Data

Stop

Parity

RTS/CTS delay

Data Carrier (DCD)

Management

*Only on TSX 37-10/21/22

Depending on the communication media chosen, certain parameters cannot be modified. These are grayed out.

The summary table below shows the various possible choices:

SCP 111

Yes

Yes

No

Yes z z z z z z z

Yes

ASCII

RTU

1 bit

2 bits odd even none

Yes

Yes

SCP 112

Yes

Yes

Yes

Yes z z z z z z z

Yes

ASCII

RTU

1 bit

2 bits odd even none

No

No

SCP 114

Yes

Yes

No

Yes z z z z z z z

Yes

ASCII

RTU

1 bit

2 bits odd even none

No

No

SCY 11601/21600/

21601

Terminal Port

Yes Yes*

Yes

No

Yes

Yes

No

Yes

Yes

RTU only z z z z z z z

Yes

ASCII

RTU

1 bit

2 bits odd even none

No

No z z z z z

No

No

1 bit

2 bits odd even none

Specific

Functions

Note: In the Data window for the Terminal Port, both options are possible but only the RTU format can function through the Terminal Port.

The additional Immediate server function is only available where a TSX SCP 114 card has been inserted into TSX SCY 21600/21601 modules.

30

35013154.02 07/2008

Modbus configuration

Application linked Modbus Parameters

At a Glance

Type Parameter

After configuring the communication channel, you need to enter the application parameters.

z z z z

These are split into four windows: the Type window, the Master window, the Slave and the

window,

(PSR) Current Loop window.

The window looks like this:

Type

Master z z

It enables you to select the type of Modbus Protocol the module uses: z Master : selects Modbus Master where the station is master,

Slave : selects Modbus Slave where the station is slave,

Immediate Server : allows UNI-TE requests to be directed to the SERVER function and not to the processor's main server.

Note: The Immediate Server parameter requires the SERVER (PL7 Micro/Junior/

Pro ; Communication applications ; Volume 1) communication function to be programmed in PL7.

It is valid until the box is checked.

Type

Slave Immediate server

35013154.02 07/2008

31

Modbus configuration

Master Function This window is only accessible by selecting Master :

Master

Number of retries 3

Response time 100 X 10 ms

This allows you to enter: z the Number of retries : number of connection attempts made by the master before defining the slave as absent.

z z z the default value is 3, values between 0 and 15, z value 0 indicates no retries by the Master.

Response Time : time elapsed between the request made by the Master and a repeat attempt if the slave does not respond. It corresponds with the maximum time between the transmission of the last character of the Master's request and receipt of the first character of the request sent back by the slave.

z the default value is 1s (100*10ms), z values between 10ms and 10s,

Slave Function This window is only accessible by selecting Slave :

Slave

Slave number 7

This allows you to fill in the Slave Number of the device: z TSX SCY 21600/21601: z the default value is 98, z z values between 1 and 98,

TSX SCY 11601: z z the default value is 247, possible values lie between 1 and 247.

Current Loop

Function

The window looks like this:

(PSR) Current Loop

Multidrop Point-to-Point

It allows you to select a: z z

Multidrop (Current Loop) communication,

Point-to-Point (Current Loop) communication.

32

35013154.02 07/2008

Modbus configuration

Modbus Parameters relating to transmission

At a Glance

Transmission

Speed

After configuring the communication channel, you need to enter the transmission parameters.

z z z z z

These are split into six windows: the Transmission speed window, the Delay between characters window, the windows specific to the the

Parity window,

RTS/CTS delay

Data

window.

and Stop ,

The window looks like this:

Transmission Speed

9600 Bits/s z z

This window is used to select the transmission speed of the Modbus protocol used by the module, and is compliant with the other devices: the default speed is 9600 bits/s, the other speeds available are 1200, 2400, 9600 and 19200 bits/s, z speeds of 300 and 600 bits/s are only available with the PCMCIA card

TSX SCP 111.

35013154.02 07/2008

33

Modbus configuration

Delay between characters

The window looks like this:

Delay between characters

Default 4 ms

This is the end delimiter detection delay plus the maximum time between two characters received. It is managed when the PLC is receiving messages, whether it be a master or slave.

You are advised to use the default values on configurations that do not have a modem or other intermediary device. Otherwise, you must use higher values.

Note: The default value depends on the transmission speed selected.

Note: There is one restriction on the 'Delay between characters' value on channel 0 of TSX SCY 11601/21600/21601 modules (see table below).

The table below gives the maximum values of the delay between characters depending on the transmission speed:

Speed (bits/s)

1200

2400

4800

9600

19200

Max. delay between characters (ms)

212

106

53

26

13

23

23

22

Max. delay between characters

(number of characters)

23

23

34

35013154.02 07/2008

Data

Stop

Parity

35013154.02 07/2008

Modbus configuration

The window looks like this:

Data

ASCII (7 bits)

RTU (8 bits)

The Data field can be used to enter the type of coding used for Modbus communication. This field is to be configured as a function of the other devices: z RTU z

mode: the characters are coded on 8 bits, z z the start and end of frame delimiters are detected by a silence of 3.5 characters, z frame integrity is checked using the CRC checksum contained in the frame.

ASCII mode: z z the characters are coded on 7 bits, the start delimiter is detected by receiving the characters ":" or by a silence longer than the delay between characters.

The end delimiter is detected by a CR and LF (carriage return and line feed) or by a silence longer than the delay between characters.

Note: The value 1000 in ASCII mode corresponds to an infinite delay between characters.

The window looks like this:

Stop

1 bit

2 bits

The Stop field is used to enter the number of stop bits used to communicate on

Modbus. The possible values are 1 or 2 stop bits. This field is to be configured as a function of the other devices.

Note: The default value is 1 stop bit.

The window looks like this:

Parity

Even Odd None

This field is used to define whether or not a parity bit is to be added, and, if so , what its type will be. The possible values are Even, Odd or none (Even by default). This field is to be configured as a function of the other devices.

35

Modbus configuration

RTS / CTS Delay The window looks like this:

RTS / CTS Delay

1 X100 ms

Data Carrier

(DCD)

Before sending a character string, the module activates the RTS (Request To Send) signal and waits for the CTS (Clear To Send) signal to be activated.

This allows you to enter: z the maximum waiting time between the two signals. If this time expires, the request is not sent to the bus. z the value is expressed in hundredths of milliseconds, z z z z the default value is 0 ms, the value must be between 0 s and 10 s, the value 0 specifies that there is no management of the delay between the two signals.

carrier management (DCD signal, Data Carrier Detected) is only used when communicating with a controlled carrier modem: z z if this option is selected, characters can only be received if the DCD carrier signal has been detected, if this option is not selected, all characters received are taken into account.

36

35013154.02 07/2008

Programming Modbus communication

3

Introduction

Subject of section

What's in this

Chapter?

This section describes the Programming process during set-up of Modbus communication.

This chapter contains the following topics:

Topic

Modbus Master Communication Function

Modbus Slave Communication Function

Using the SEND_REQ communication function

Example 1: SEND_REQ function with Echo request

Example 2: SEND_REQ function with Word read request

Example 3: SEND_REQ Function with Bit Read Request

Example 4: READ_VAR function for reading bits

Page

38

40

42

43

44

46

48

35013154.02 07/2208

37

Modbus programming

Modbus Master Communication Function

At a Glance This page describes the services available on the Micro or Premium master stations of a Modbus link. For more information regarding Modbus function codes, please refer to the Modbus user guide TSX DG MDB F.

Note: the data entry help function does not work with Modbus addressing on a

Micro.

Data Exchanges The following requests are addressed to the slave device with which you wish to carry out variable read or write operations.

These requests use the READ_VAR , WRITE_VAR and SEND_REQ communication functions. See (PL7 Micro/Junior/Pro ; Communication applications ; Volume 1) and

(PL7 Micro/Junior/Pro ; Communication applications ; Volume 1).

Modbus request

Read bits

Read words

Write one or n bits

Write one or n words

Read input bits*

Read input words*

* except on Terminal port

Function code

16#01

16#03

16#05 or 16#0F

16#06 or 16#10

16#02

16#04

Communication function

READ_VAR

READ_VAR

WRITE_VAR

WRITE_VAR

SEND_REQ

SEND_REQ

Note: write utilities can be sent in transmission. In this case no response is returned to the transmitter. We therefore recommend that you configure a time-out to acknowledge the activity bit of the function.

Example of

Reading Words

The following example applies to reading word 4 (%MW4) in the Modbus slave 3.

READ_VAR (ADR#0.1.3, ‘%MW’,4,1,%MW100:1,%MW200:4)

38

35013154.02 07/2208

Modbus programming

Diagnostics and

Maintenance

The diagnostics and maintenance information of Modbus slaves uses the

SEND_REQ communication function. (See : PL7 Micro/Junior/Pro ; Communication applications ; Volume 1)

Modbus request Communication function

Exception status

Diagnostics

Event counter

Connection event

Slave identification

Function code / subfunction code

16#07

16#08 / 16#xx

16#0B

16#0C

16#11

SEND_REQ

SEND_REQ

SEND_REQ

SEND_REQ

SEND_REQ

35013154.02 07/2208

39

Modbus programming

Modbus Slave Communication Function

At a Glance This page describes the services managed by the slave modules for a Modbus link.

Data Exchanges The slave module manages the following requests:

Modbus request

Read n output bits

Read n input bits

Read n output words

Read n input words

Write an output bit

Write an output word

Write n output bits

Write n output words

Function code / subfunction code

16#01

16#02

16#03

16#04

16#05

16#06

16#0F

16#10

PLC object

%M

%M

%MW

%MW

%M

%MW

%M

%MW

40

35013154.02 07/2208

Modbus programming

Diagnostics and

Maintenance

The diagnostics and maintenance information which are accessible from a Modbus link are shown below:

Designation

Read exception status

Echo

Initialize module

Read the diagnostic registers of the PLC

Change end of frame delimiter (ASCII mode)

Switch to listening mode

Reset counters

Number of messages received without CRC error

Number of frames received with CRC error

Number of exceptional responses

Number of messages addressed to the PLC

Number of broadcast messages received

Number of correct responses

Number of messages received in listening mode

Number of invalid characters received

Read event counter

Read connection event

Function code / subfunction code

16#07

16#08 / 16#00

16#08 / 16#01

16#08 / 16#02

16#08 / 16#03

16#08 / 16#04

16#08 / 16#0A

16#08 / 16#0B

16#08 / 16#0C

16#08 / 16#0D

16#08 / 16#0E

16#08 / 16#0F

16#08 / 16#10

16#08 / 16#11

16#08 / 16#12

16#0B

16#0C

Read identification

Note : The slave request response returns the same elements as the UNI-TE identification request (see the subchapter

General Use Requests in the TSX DR NET manual).

16#11

35013154.02 07/2208

41

Modbus programming

Using the SEND_REQ communication function

At a Glance The UNI-TE Action-object request (request code 16#9F) is used to transmit all

Modbus (See : PL7 Micro/Junior/Pro ; Communication applications ; Volume 1) functions.

After executing this request, the report is always 16#CF00 .

To check the exchange, it is also necessary to test the content of the first word in the reception table.

Possible values of the first word: z z

0: indicates that the exchange has been performed,

1: indicates that the exchange has not been performed,

The transmission buffer should contain the following information: z z z z z z first word: z Byte 0: function code, z Byte 1: sub-function code, second word: Modbus function identifier, which is always 16#0296 third word = 0: reserved fourth word: Modbus function parameters fifth word: Modbus function parameters n th word: Modbus function parameters

Note: this function is not available in Modbus master mode on the Terminal port.

42

35013154.02 07/2208

Modbus programming

Example 1: SEND_REQ function with Echo request

At a Glance

Question

This example concerns the Echo diagnostics function. This function requests that the interrogated slave return the message sent by the master in full.

The communication function is as follows:

SEND_REQ(ADR#0.1.x,16#9F,%MW10:10,%MW50:30,%MW100:4)

Before sending the function it is necessary to initialize the following words:

Words

%MW10

%MW11

%MW12

Value

:= 0

Description

:= 16#0008 corresponds to the Echo function (byte 0 = 16#08, byte 1

=16#00

:= 16#0296 corresponds to the identification of the Modbus function reserved

%MW13 := 16#1234 corresponds to the Echo function parameter. For this example, the slave must return the value 16#1234

%MW103 := 8 (bytes) length of the data to be transmitted in bytes

Response

%MW50

:= 0 if action taken

:= 1 if action not taken

The slave response, contained in the %MW50:30 reception buffer, is of type:

%MW51 Description

:= 16#0008 corresponds to the Echo function (byte 0 = 16#08, byte 1 =16#00)

%MW52 to %MW79 contain the Modbus response data. For this example

%MW52:= 1234

:= 16#0007 incorrect request parameters

:= 16#0004 incorrect question parameters

:= 16#0688 byte 0 =16#80 + function code (16#08 for Echo) byte 1 = 16#06 Modbus error code (the slave is busy)

:= 16#0188 byte 0 =16#80 + function code (16#08 for Echo) byte 1 = 16#01 Modbus error code (the function is unknown)

:= 16#0388 byte 0 =16#80 + function code (16#08 for Echo) byte 1 = 16#03 Modbus error code (the data is invalid)

35013154.02 07/2208

43

Modbus programming

Example 2: SEND_REQ function with Word read request

At a Glance

Question

The example deals with the reading of 4 input words at address 10 of a third-party device. These words are then copied in %MW52:5.

The communication function is as follows:

SEND_REQ(ADR#0.1.x,16#9F,%MW10:10,%MW50:30,%MW100:4)

Before sending the function it is necessary to initialize the following words:

Words Value Description

%MW10

%MW11

%MW12

%MW13

%MW14

:= 16#0004

:= 16#0296

:= 0

:= 16#0A00

:= 16#0400 corresponds to the read function of n input words (byte 0 =

16#04, byte 1 = 16#00) corresponds to the identification of the Modbus function reserved address of the first word to read (1) number of words to read (1)

%MW103 := 10 (bytes) length of the data to be transmitted in bytes

Note: (1) the most significant bytes and the least significant bytes must be inverted.

44

35013154.02 07/2208

Modbus programming

Response

%MW50

:= 0 if action taken

:= 1 if action not taken

The slave response, contained in the %MW50:30 reception buffer, is of type:

%MW51 Description

:= 16#0004 corresponds to the read function of n input words (byte 0 = 16#04, byte 1

= 16#00)

%MW52 to %MW79 contain the Modbus response data: z %MW52:= PF

0

0A z z byte 0 = 16#0A: length received in bytes (10 bytes) byte 1 = PF

0

: most significant byte of first word z %MW53:= PF

1

pf

0 z z byte 0 = pf

0

: least significant byte of first word byte 1 = PF

1

: most significant byte of second word z %MW54:= PF

2

pf

1 z z byte 0 = pf

1

: least significant byte of second word byte 1 = PF

2

: most significant byte of third word

:= 16#0007 incorrect request parameters

:= 16#0004 incorrect question parameters

:= 16#0688 byte 0 =16#80 + function code (16#08 for Echo) byte 1 = 16#06 Modbus error code (the slave is busy)

:= 16#0188 byte 0 =16#80 + function code (16#08 for Echo) byte 1 = 16#01 Modbus error code (the function is unknown)

:= 16#0388 byte 0 =16#80 + function code (16#08 for Echo) byte 1 = 16#03 Modbus error code (the data is invalid)

Note: to retrieve the words read, use the instruction ROR1_ARB.

35013154.02 07/2208

45

Modbus programming

Example 3: SEND_REQ Function with Bit Read Request

At a Glance

Question

The example shows the reading of 2 output bits from address 0 by a third-party device whose slave address is 5.

The communication function is as follows:

SEND_REQ(ADR#3.0.5,16#9F,%MW300:50,%MW400:50,%MW450:4)

Before sending the function it is necessary to initialize the following words:

Words Value of the words

%MW300 := 16#0001

Description

%MW301 := 16#0296

%MW302 := 0

%MW303 := 16#0000

%MW304 := 16#0200

%MW453 :=10 (bytes)

Corresponds to the read function of n output bits (byte 0 =

16#01, byte 1 = 16#00)

Corresponds to the identification of the Modbus function

Reserved

Address of the first bit to read (1)

Number of bits to read (1)

Length of the data to be transmitted in bytes

Legend:

(1) The most significant bytes and the least significant bytes must be inverted.

46

35013154.02 07/2208

Response

Modbus programming

The slave response, contained in the %MW400:50 reception buffer, is of type:

Word

%MW400

%MW401 if %MW400:= 0

%MW401 if %MW400:= 1

%MW402

Value Description

:= 0 if action taken

:= 1 if action not taken

:= 16#0001 Corresponds to the read function of n output bits

(byte 0 = 16#01, byte 1 = 16#00)

:= 16#0007 Incorrect request parameters

:= 16#0004 Incorrect question parameters

:= 16#0681 Byte 0 =16#80 + function code (16#01) z z z

Byte 1 =

16#06 Modbus error code (the slave is busy)

16#01 Modbus error code (the function is unknown)

16#03 Modbus error code (the data is invalid)

:= 16#xx01 Contains the Modbus response data:

Byte 0 = 16#01: length received in bytes (1 byte)

Byte 1 = 16#xx: value of the bits

For example, if bit 1 = 1 and bit 2 = 1, then byte 1 = 16#03

35013154.02 07/2208

47

Modbus programming

Example 4: READ_VAR function for reading bits

General

Example with

READ_VAR

Exchanges with Modbus slave devices are programmed using the READ_VAR and

WRITE_VAR communication functions only (the SEND_REQ function is not supported on the TER port).

Description of the objects used in the example:

Object

%MW0:X0

%M20

%MW100:10

Description

Request transmission request

Requesting

Reception buffer

%MW200..203

Report zone:

%MW200 Session number and activity bit (X0)

%MW201 Error code

%M30

%MW204

%MW202 Time-out in units of 100 ms

Bit set to 1 after a successful exchange

Counter of requests sent

%MW205

%MW206

%MW207

Counter of successful requests

Counter of unsuccessful requests

Error code of the last unsuccessful request

Example of the program:

!(* Reading of bits %M0 to %M8 from the Nano at address 37 *)

IF %MW0:X0 AND NOT %M20 THEN

%MW200:4:=0;%MW202:=50;SET %M20;

READ_VAR(ADR#0.0.37,’%M’,0,8,%MW100:10,%MW200:4);

(*8 bits %M0..%M7 are read in the slave 37 and placed in the

%MW100 word of the master*)

END_IF;

!(* Analysis of the results *)

IF %M20 AND NOT %MW200:X0 THEN

INC %MW204;RESET %M20;RESET %MW0:X0;

IF %MW201=0 THEN INC %MW205;SET %M30;

ELSE INC %MW206;%MW207:=%MW201;RESET %M30;

END_IF;

48

35013154.02 07/2208

Debugging Modbus communication

4

Introduction

Subject of

Chapter

What's in this

Chapter?

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

This chapter contains the following topics:

Topic

Modbus debug screen

Modbus Master debugging screen

Debug screen in Modbus slave type

How to test a communication channel

Page

50

51

52

53

35013154.02 07/2008

49

Modbus debugging

Modbus debug screen

At a Glance

Illustration

This screen is split into two and enables the declaration of the communication channel and gives access to the debug parameters for a Modbus link.

The Modbus Communication Screen looks like this:

1

2

TSX 57352 [RACK 0 POSITION 1]

Debug

Designation: TSX P 5735 PROCESSOR Version: 3.0

DIAG...

CHANNEL 1

CHANN TSX SCP 111 RS232 MP PCMCIA CARD

MODBUS/JBUS LINK DIAG...

Type:

Slave

Counters

Received without CRC error

Received with exception code

Received in broadcast mode

Slave BUSY or LOM

0

0

0

0

Received with CRC error

Message for the CPU

Sent with NACK

Character error

Reset counters

Channel test

Slave

Identification

1

Enter request

Response reception

ASCII Hexa

0

0

0

0

Nodes and

Functions

This table describes the different zones which make up the debug screen:

Address Zone

1 common

2 specific

Function

(See : PL7 Micro/Junior/Pro ; Communication applications ;

Volume 1) z z gives access to the debug parameters of a Modbus link.

It differs according to the type of Modbus function configured: either Modbus master, or Modbus slave.

50

35013154.02 07/2008

Modbus debugging

Modbus Master debugging screen

At a Glance

Type Window

Counters

Window

Channel Test window z z

The specific part is divided into three windows: the Type window, the Counters window, z the Channel test window.

The window looks like this:

Type

Master

It recalls the type of Modbus function configured (master).

The window looks like this:

Counters

Received without CRC error

Received with exception code

Transmission in progress

Retries

0

0

0

0

Received with CRC error

Sent without response

Received with NACK

Character error

Reset counters

0

0

0

0

This window displays the different counters (in slave configuration).

the Reset Counters button resets these counters to zero.

Where Modbus is on the Terminal Port, this window displays the status of the system words (See

System objects of the Modbus function on Terminal port, p. 64

) used by this function. These may also be viewed with a variables animation table.

The window looks like this:

Channel test

Slave

Response reception

Identification

1

Enter request

ASCII Hexa

This window enables you to test communication channels by transmitting a request to one of the slave stations present on the bus.

For the TSX SCY 11601 module's built in channel, the slave number values to be searched lie between 1 and 247. The values for other channels supporting

MODBUS/JBUS Master lie between 1 and 98.

Note: This window is not available when Modbus is in use on the Terminal Port.

35013154.02 07/2008

51

Modbus debugging

Debug screen in Modbus slave type

At a Glance

Type Window

Counters

Window z z z

The specific part is divided into three windows: the Type window, the Counters window, the Channel test window: this window cannot be used in this mode.

The window is as below:

Type

Slave

It recalls the type of Modbus function configured (slave).

The window is as below:

Counters

Received without CRC error

Received with exception code

Reception broadcast

Slave BUSY or LOM

0

0

0

0

Received with CRC error

Message for the CPU

Sent with NACK

Character error

Reset counters

0

0

0

0

This window displays the different counters (in slave configuration).

the Reset counters button resets these counters to zero.

Counter Slave Busy or LOM: z Slave Busy: this counter is incremented by the slave when it receives a request from the master while in the process of processing another request. This happens z when the master sends a request. It does not wait for a response from the slave and may send another request,

Slave LOM: (Listen Only Mode) is the operating mode of a slave which is only in listen mode. It never responds to frames sent by the master. In this case, this counter indicates the number of frames received by the slave.

52

35013154.02 07/2008

Modbus debugging

How to test a communication channel

Introduction This page shows the procedure for testing a communication channel from the debugging screen.

How to identify a station

The following procedure is used to identify a designated station.

Step

1

2

Actions

Select the address of the slave to be interrogated using the Slave field.

Click on the Identification button.

Result

The response appears in the Receive Response window:

Receive response

.....TSX 3721...!0....

Ascii Hex.

35013154.02 07/2008

53

Modbus debugging

How to send a request

3

4

5

6

The following procedure is used to send a request, other than those provided by the command buttons, to a designated station. The example deals with transmission of the Echo request (function code: 08; sub-function code: 00; data to be sent 1144).

Step

1

2

Action

Select the address of the slave to be interrogated using the Slave field.

Click on the Enter Request button.

Result

The following window appears:

Enter Request

Function code (hexadecimal) 03

Code in functions and/or data (hexadecimal)

001144

Send Cancel

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

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

Enter the data to be sent by encoding all the data in hexadecimal on 2 bytes

(4 characters). Enter the data continuously without any intervening spaces.

Click on the Send button.

Result

The response appears in the Receive Response window:

Channel test

Slave

Identification

1

Enter Request

Receive response

08 00 00 00 11 44

Ascii Hex.

z z

The response contains: z the function code on 2 bytes (08 00), the sub-function code on 2 bytes (00 00), the data on 2 bytes (11 44),

54

35013154.02 07/2008

Language objects associated with

Modbus communication

5

Introduction

Subject of this

Section

What's in this

Chapter?

This Chapter introduces the language objects linked to Modbus communication.

This chapter contains the following topics:

Topic

Implicit exchange language object for a Modbus function

Explicit exchange language objects for a Modbus function

Explicit exchange management and report

Language objects associated with the configuration

System objects of the Modbus function on Terminal port

Page

56

58

61

62

64

55

35013154.02 07/2008

Modbus language objects

Implicit exchange language object for a Modbus function

At a Glance

Bit objects

This page describes all implicit exchange language objects for a Modbus function, which can be displayed or modified by the application program. See (PL7 Micro/

Junior/Pro ; Communication applications ; Volume 1).

The table below shows the different implicit exchange bit objects.

Object (1) Function

%Ixy.MOD.ERR

Module error bit

%Ixy.i.ERR

Channel error bit

Meaning

When this bit is at 1, it indicates a module error

(at least one of the channels is faulty, etc.)

When this bit is at 1, it indicates a line fault.

Key

(1) xy.i address z z z x: corresponds to the rack number y: corresponds to the module number i: corresponds to the channel number

Word objects in

Modbus master mode

The table below shows the different implicit exchange word objects.

Object (1)

%IWxy.i.0

Function

Input signals

Meaning

Common signals (2): z z z z x0 = 1: DCD signal x1 = 1: RI signal x2 = 1: CTS signal x3 = 1: DSR signal

Key

(1)

(2) z z z xy.i address x: corresponds to the rack number y: corresponds to the module number i: corresponds to the channel number only on RS232

Note: These objects are not available on the Terminal port

56

35013154.02 07/2008

Modbus language objects

Word objects in

Modbus slave mode

The language objects are identical to those of the Modbus master function. Only the objects defined in the following tables are different.

The table below shows the different implicit exchange word objects.

Object (1) Function

%IWxy.i.0

Input signals

Meaning

Specific data z x8 = 1: listen only mode

Key

(1) z z z xy.i address x: corresponds to the rack number y: corresponds to the module number i: corresponds to the channel number

Note: These objects are not available on the Terminal port

35013154.02 07/2008

57

Modbus language objects

Explicit exchange language objects for a Modbus function

At a Glance This page describes all explicit exchange language objects for a Modbus master function, which can be displayed or modified by the application program. See (PL7

Micro/Junior/Pro ; Communication applications ; Volume 1).

Word objects in master mode

The table below shows the different explicit exchange word objects.

Object (1) Function

%MWxy.MOD.2

Module status

%MWxy.i.2

%MWxy.i.3

%MWxy.i.4

%MWxy.i.5

%MWxy.i.6

%MWxy.i.7

Channel standard status

Specific channel status

Error counter (2)

Error counter (2)

Error counter (2)

Error counter (2)

Meaning z z z z z z x0 = 1: defective module (3) x1 = 1: functional fault (fault between the processor and the module, adjustment or configuration fault, etc.) x2 = 1: terminal strip error (not connected) x3 = 1: self-tests in progress (3) x4 = 1: reserved x5 = 1: hardware or software configuration fault

(the module present is not the one declared in the configuration, the sub-modules are not compatible) x6 = 1: module missing (3) x7 = 1: fault in one of the sub-modules z z z z z z z z z z x0 = 1: no device is working on the channel x1 = 1: a device on the channel is faulty x2 = 1: terminal strip error (not connected) x3 = 1: timeout error (faulty wiring) x4 = 1: self-tests in progress x5 = 1: hardware or software configuration fault

(the channel present is not the one declared in the configuration) x6 = 1: communication fault x7 = 1: application fault (error in the configuration, adjustment error, etc.)

Byte 0 = 16#06 for the Modbus master function

Number of responses received without CRC error

Number of messages received with CRC error

Number of responses received with an exception code

Number of master messages sent without response

58

35013154.02 07/2008

35013154.02 07/2008

(2)

(3)

(4)

(5)

Object (1)

%MWxy.i.8

%MWxy.i.9

%MWxy.i.10

%MWxy.i.11

%MWxy.i.15

Function

Error counter (2)

Error counter (2)

Error counter (2)

Error counter (2)

Command (2)

Modbus language objects

Meaning

Number of transmissions broadcast

Number of receipts with NACK

Number of master messages repeated

Number of character errors z z z z z x0 = 1: Reset counter x8 = 1: DTR signal ON (5) x9 = 1: DTR signal OFF (5) x14 = 1: change from Modbus to character mode (modem) (4) x15 = 1: change from character mode (modem) to Modbus (4)

Key

(1) xy.i address z z z x: corresponds to the rack number y: corresponds to the module number i: corresponds to the channel number

These objects are not available on the Terminal port

These objects are not managed by TSX SCY 11601/21600/21601 modules.

These objects are not available on the TSX SCY 11601 module.

Modbus on RS232.

59

Modbus language objects

Word objects in

Modbus slave mode

The language objects for the Modbus slave function are identical to those of the

Modbus master function.

Only the objects defined in the following table are different.

Object (1) Function Meaning

%MWxy.MOD.2

Module status z z z z z z x0 = 1: defective module (2) x1 = 1: functional fault (fault between the processor and the module, adjustment or configuration fault, etc.) x2 = 1: terminal strip error (not connected) x3 = 1: self-tests in progress (2) x4 = 1: reserved x5 = 1: hardware or software configuration fault

(the module present is not the one declared in the configuration, the sub-modules are not compatible) x6 = 1: module missing (2) x7 = 1: fault in one of the sub-modules

%MWxy.i.2

Channel standard status z z z z z z z z z z x0 = 1: no device is working on the channel x1 = 1: a device on the channel is faulty x2 = 1: terminal strip error (not connected) x3 = 1: timeout error (faulty wiring) x4 = 1: self-tests in progress x5 = 1: hardware or software configuration fault

(the channel present is not the one declared in the configuration) x6 = 1: communication fault x7 = 1: application fault (error in the configuration, adjustment error, etc.)

%MWxy.i.3

Byte 0 = 16#07 for the Modbus slave function

%MWxy.i.7

%MWxy.i.8

%MWxy.i.10

Specific channel status

Error counter

Error counter

Error counter

Number of messages for the CPU

Number of broadcast receipts

Number of messages received during Slave busy or LOM

Key

(1)

(2) xy.i address z z z x: corresponds to the rack number y: corresponds to the module number i: corresponds to the channel number

These objects are not managed by TSX SCY 11601/21600/21601 modules.

60

35013154.02 07/2008

Modbus language objects

Explicit exchange management and report

At a Glance

Word objects

This page describes all language objects which manage explicit exchanges.

(See : PL7 Micro/Junior/Pro ; Communication applications ; Volume 1)

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

Object (1) Function Meaning

%MWxy.MOD.0

Exchanges in progress on module z x0 = 1: reading statuses

%MWxy.MOD.1

%MWxy.i.0

Module report

Exchanges in progress on channel z z z x0: status read report (0 = ok) x0 = 1: reading statuses x1 = 1: sending command parameters to the communication channel

%MWxy.i.1

Channel report z z x0: status read report (0 = ok) x1 = 0: command 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

35013154.02 07/2008

61

Modbus language objects

Language objects associated with the configuration

At a Glance This page describes all configuration language objects enabling Modbus communication which can be displayed by the application program.

Objects for the

Modbus master function (where

Terminal Port is inoperative)

The following table describes internal constants for the Modbus master function

(except on the Terminal Port):

Object

%KWxy.i.0

%KWxy.i.1

%KWxy.i.2

Function

Type

Speed / Format

Meaning

Byte 0 = 16#06 for Modbus master function

Byte 1: reserved z z z z

Byte 0 = speed z 128 = 300 bits/s, 129 = 600 bits/s z

(only for TSX SCP 111)

00 = 1200 bits/s, ..., 04 = 19200 bits/s

Byte 1 = format x8: bit number (1 = 8 bits, 0 = 7 bits) x9: parity management (1 = with, 0 = without) x10: Parity Type (1 = odd, 0 = even) x11: stop bit (1 = 1 bit, 0 = 2 bits)

Value in ms from 2 ms to 10 000 ms

%KWxy.i.3

%KWxy.i.4

%KWxy.i.5

Delay between characters

Wait Time

Retries and Signal

Management

RTS / CTS Delay

Wait Time in ms from 10 ms to 10 000 ms

Byte 0 = number of retries (3 by default)

Byte 1 = Signal Management z x8 = 1 if PSR signal management

(TSX SCP 112) z x10 = 1 if DCD Data Carrier management

(TSX SCP 111)

Delay time in hundredths of ms, only for

TSX SCP 111 (default value 0 ms)

62

35013154.02 07/2008

Modbus language objects

Objects for

Modbus master function on

Terminal Port

The following table describes internal constants for the Modbus master function on the Terminal Port:

Object Function Meaning

%KW0.0.0

Type/Speed

%KW0.0.1

%KW0.0.2

Format/delay between characters

Number of retries/ response time

Byte 0 = 16#06 for Modbus master function

Byte 1 = Transmission Speed: z 00 = 1200 bits/s, ..., 04 = 19200 bits/s

Byte 0 = format z z z z x0: number of bits (1 = 8 bits, 0 = 7 bits) x1: parity management (1 = with, 0 = without) x2: Parity Type (1 = odd, 0 = even) x3: stop bit (1 = 1 bit, 0 = 2 bits) z z z z z

Byte 1 = delay between characters depending on the speed:

1200: from 29 ms to 255 ms

2400: from 15 ms to 255 ms

4800: from 7 ms to 255 ms

9600: from 4 ms to 255 ms

19200: from 2 ms to 255 ms

Byte 0 = number of retries (0 to 15)

Byte 1 = response time (200 ms to 10 s)

Objects for

Modbus slave function (where

Terminal Port is inoperative)

The language objects for the Modbus slave function are identical to those of the

Modbus master function.

Only the objects in the following table differ:

Object Function Meaning

%KWxy.i.0

Type

%KWxy.i.3

Slave Addresses

Byte 0 = 16#7 for Modbus slave function

Byte 1: reserved

Byte 0: slave number value (0 to 98) z Byte 0: z for TSX SCY21600/21601, the slave number value is between 0 and 98.

z z for TSX SCY 11601, the slave number value is between 0 and 247.

Byte 1: reserved

Objects for

Modbus slave function on

Terminal Port

The language objects for the Modbus slave function are identical to those of the

Modbus master function on the Terminal Port.

Only the objects in the following table differ:

Object Function Meaning

%KW0.0.0

%KW0.0.2

Type

Slave Number

Byte 0 = 16#7 for Modbus slave function

Byte 0: slave number value (1 to 98)

35013154.02 07/2008

63

Modbus language objects

System objects of the Modbus function on Terminal port

At a Glance

Bit objects

In Modbus mode on the Terminal port, the Micro uses the system objects below for the communication diagnostics.

Table of bit objects

Object

%S80

%S81

Description

Global reset to 0 of the communication counters

Reset to 0 of the Modbus system words on Terminal port This system bit is set to 1 by the application and reset to 0 by the system

Word objects

Note: The system words are also reset to 0 when there is a cold start (%S0 =1).

Table of word objects

Objects Description

%SW100 Number of messages received without CRC error

%SW101 Number of messages received with CRC error

%SW102 Number of messages received with an exception code

%SW103 Number of master messages sent without response

%SW104 Number of transmissions broadcast

%SW102 Number of receipts with NACK

%SW106 Number of master messages repeated

%SW107 Number of character errors

64

35013154.02 07/2008

Communication via Modem

II

Introduction

Subject of this part

What's in this

Part?

This part introduces the principles of configuring and communicating using a

TSX MDM 10 modem via PL7 software.

This part contains the following chapters:

Chapter

6

7

8

9

10

11

Chapter Name

Communication via Modem

Configuring Modem communication

Programming Modem communication

Debugging Modem communication

Language objects associated with Modem communication

Appendices

Page

67

89

101

119

123

133

35013154.02 07/2008

65

Communication via Modem

66

35013154.02 07/2008

Communication via Modem

6

Introduction

Subject of this

Chapter

What's in this

Chapter?

This Chapter introduces communication using a TSX MDM 10 modem and its services.

This chapter contains the following sections:

Section

6.1

6.2

6.3

Topic

Introduction to communication via Modem

Characteristics

Setting up communication via Modem

Page

68

74

79

35013154.02 07/2208

67

General

6.1

Introduction to communication via Modem

Introduction

Subject of

Section

What's in this

Section?

This Section presents a summary description of communication using a

TSX MDM 10 modem and its associated services.

This section contains the following topics:

Topic

Modems

Standard configuration for communication via modem

Other configurations for communication via modem

Principles of communication between two stations

Page

69

70

71

73

68

35013154.02 07/2208

General

Modems

Introduction

Associated manuals

A large number of applications use communication via modem.

Communication via the TSX MDM 10 modem can be used to access remote stations using the switched public telephone network in order to carry out checks, diagnostics or long distance control.

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

Title

Micro PLCs - Installation manual

Premium TSX PLCs - Installation manual

Description

Hardware installation

Hardware installation

35013154.02 07/2208

69

General

Standard configuration for communication via modem

Introduction The standard configuration allows for communication between stations or other devices connected to a switched telephone network.

Configuration and services

The following diagram shows the standard configuration for communication via modem and the different services.

Programming terminal

Telephone

Fax

Pocket size receiver

Programming

Debugging

Commands

Switched telephone network

Sending back alarms and measurements

Remote station 1

Variable exchanges

Commands

Alarms and measurements

Remote station n

70

35013154.02 07/2208

General

Other configurations for communication via modem

Introduction

External

CALL_MODEM function

From a local network station, it is possible to call a remote station on the switched telephone network via another station with a modem connection.

A CALL_MODEM communication function is sent by a network station.

Programming terminal Calling station

Station 1.3

External CALL_MODEM function

CALL_MODEM(ADR#{1.1}0.1.SYS, ..

FIPWAY 1 network

Station 1.1

Master

Called station

Address slave

1 and 2

Switched telephone network

Once a link has been established, communication is possible in both directions while respecting transparency rules.

Moreover, a slave station on the switched telephone network can access the entire network architecture while respecting addressing rules.

35013154.02 07/2208

71

General

Local

CALL_MODEM function

A CALL_MODEM communication function is sent by the station supporting the

TSX MDM 10 card.

Programming terminal

Station 1.3

Local CALL_MODEM function

CALL_MODEM(ADR#0.1.SYS, ...

FIPWAY 1 network

Called station

Station 1.1

Calling station

Master

Address slave

1 and 2

Switched telephone network

72

35013154.02 07/2208

General

Principles of communication between two stations

Introduction The call direction is from station A to station B:

Operation

Station A station where call is to be made (transmitter)

Switched telephone network

Station B called station

(receiver)

The following table describes the different stages of communication between two stations:

Phase

1

2

3

4

5

6

Description

While idle, all modems are by default awaiting a possible connection request.

Station A sends a call request to number X on station B using AT commands

(or using the CALL_MODEM communication function in the case of a PLC).

An exchange procedure between the modems results in the line being established point by point between station A and station B. Connection is established if the correct password is used (if password management is employed).

Stations A and B then dialog according to the protocol chosen on calling, whether Uni-telway or character mode. Communication is carried out using the standard communication functions. Each station can initiate exchanges.

In Uni-telway mode, by default, the calling station is the slave and the station called is the master. To ensure compatibility with existing applications, it is possible to set the parameters of the CALL_MODEM communication function so that the local station remains in master Uni-telway mode.

Station A sends a request for disconnection to its local modem.

Stations A and B return to their initial state, and are able to initiate another call.

35013154.02 07/2208

73

General

6.2

Characteristics

Introduction

Subject of

Section

What's in this

Section?

This Section introduces the characteristics and constraints of communicating using a TSX MDM 10 modem.

This section contains the following topics:

Topic

Hardware Compatibility

Software compatibility

Page

75

77

74

35013154.02 07/2208

General

Hardware Compatibility

About PLCs This type of communication is available for PLCs that are at least version V3.3.

z z

Premium via the PMMCIA TSX MDM 10 card,

Micro accepting the PCMCIA described below.

The card can also be inserted in PCs that have type 3 PCMCIA card slots.

Note: for certain types of CPU, it is recommended that a PCMCIA memory card

( CALL_MODEM communication function occupying 25 Kb of program memory space) is used.

Networks and

Devices

The TSX MDM 10 communication card only connects to the STN - (Switched

Telephonic Network).

It cannot be connected: z z z to specialized links, to NNIS (Numerical Network for Integrating Services) networks, to the GSM (Global System for Mobile) network.

Third-party modem compatibility is guaranteed for modems that are designed for

COM 1 switched telephonic network. See Communication between PLCs using an

external modem, p. 83 .

35013154.02 07/2208

75

General

About Protocols The TSX MDM 10 card supports the two character formats 10 or 11 bits.

For 11 bit communication between modems, compatibility is only guaranteed with modems designed for the COM 1 telephone network.

The TSX MDM 10 is incompatible with configured third-party modems: z z with parity, with data compression and error correction.

In ASCII, the TSX MDM 10 card allows: z z in called mode: z z transmission of data coded on 7 bits reception of data coded on 8 bits.

in calling mode: z transmission of data coded on 7 or 8 bits, z reception of data coded on 7 or 8 bits.

76

35013154.02 07/2208

General

Software compatibility

X-WAY transparency

Transmission

The modem card provides X-WAY transparency, and supports two types of protocol: z z

Uni-telway master or slave protocol, character mode protocol.

When a local network station communicates with a remote station on the switched telephone network, the calling station must be in master mode, and the called station in slave mode.

The speed of transmission varies between 4800 bits/s and 9600 bits/s. The size of the frames sent is 256 bytes in total (240 bytes usable in Uni-telway mode, and 200 bytes in character mode).

Only one communication function can be active at a time on the TSX MDM 10 card.

The application must manage line disconnection. Only the station which initiated connection using External CALL_MODEM (see External CALL_MODEM function,

p. 71 ) has the right to disconnect the line.

The CALL_MODEM communication function ensures disconnection.

The TSX MDM 10 card defines a set operation for the INPUT_CHAR instruction.

When the INPUT_CHAR function is activated, the frame end character must be received before the end of the task cycle.

If several cycles are needed to receive this character, the character string is lost.

35013154.02 07/2208

77

General

The application Modem configuration requires PL7 software from version V3.3 onwards.

CAUTION

Downloading the application

The modem card cannot be used to up- or download a PL7 application.

If loading is initiated by mistake, a failure message will appear on connection and the PLC application will be lost.

However, it is always possible to load an application via the terminal port.

Failure to follow these instructions can result in injury or equipment damage.

The station called can recognize a maximum of 8 calling stations for Micro PLCs, and 16 for Premium PLCs where the password service is used. Only the

TSX MDM 10 card ensures the management of passwords. For third party devices, passwords are managed according to the coding protocol for password exchanges.

See

Coding of exchanges, p. 107 .

78

35013154.02 07/2208

General

6.3

Setting up communication via Modem

Introduction

Subject of

Section

What's in this

Section?

This Section introduces a summary description of setting up communication via a

TSX MDM 10 modem.

This section contains the following topics:

Topic

Set up methodology

Setting up UNI-TELWAY communication between PLCs via the TSX MDM 10 card

Page

80

81

Communication between PLCs using an external modem

Setting up communication from PL7

How to configure the Uni-telway driver with a modem

How to Configure Modem Connection

How to Modify the Modem Link Parameters

83

84

86

87

88

35013154.02 07/2208

79

General

Set up methodology

Introduction Functions supported by the TSX MDM 10 card can immediately process, without prior configuration, the most common operations as follows: z z communication between PLCs with a TSX MDM modem card, communication from PL7 software to a PLC with a TSX MDM 10 modem card.

80

35013154.02 07/2208

General

Setting up UNI-TELWAY communication between PLCs via the TSX MDM 10 card

Introduction The two stations are connected to the switched telephone network by TSX MDM 10 cards.

Switched telephone network Calling station Called station

Calling station The calling station is a PLC with a TSX MDM 10 card.

Step

1

2

3

Action z z z z

Declare the TSX MDM 10 card by default.

Default values:

Uni-telway protocol transmission speed of 9600 bits/s automatic switch to slave mode on addresses 1 and 2 no password management

Confirm configuration.

Program the CALL_MODEM communication function to call the remote station.

CALL_MODEM(ADR#0.1.SYS, 1, %MB100:20, 0, 0, %MW256:4)

Values: z z z z z address: ADR#0.1.SYS

command: 1 connection option: 0 slave mode: 0 report: %MWx:4

35013154.02 07/2208

81

General

Called station The called station is a PLC with a TSX MDM 10 card.

Step

1

2

Action

Declare the TSX MDM 10 card by default.

z z z z

Default values:

Uni-telway protocol transmission speed of 9600 bits/s automatic switch to master mode on addresses 1 and 2 no password management

Confirm configuration.

82

35013154.02 07/2208

General

Communication between PLCs using an external modem

Introduction One of the stations is a PLC connected to the telephone network via an external modem.

The other station is a PLC connected to the telephone network via the TSX MDM 10 card.

Description of the hardware configuration:

Calling station

PLC with a TSX

SCP 111 card

Switched telephone network

External modem from COM1

Called station

PLC with a TSX

MDM 10 card

TSX MDM 10 card end

TSX SCP 111 card end

The TSX MDM 10 card is configured with the default values from the configuration screen in Uni-telway mode.

The TSX SCP 111 is configured with the default values from the configuration screen in Uni-telway master mode, where the number of slaves is equal to 2 and the wait timeout must be set to the default value (2 s).

z z z

The external modem from COM1 is configured with the following AT commands: z AT&F&K%C0 where: z z

&F: sends the default configuration,

&K: flow control deactivated, z %C0: data compression deactivated

ATS0=2 : sets 2 rings before automatic reply

AT&D0 : if the DTR signal has not been set to 1 in the TSX SCP 111 card

AT&D2 : if the DTR signal has been set to 1 in the TSX SCP 111 card

35013154.02 07/2208

83

General

Setting up communication from PL7

Introduction One of the stations is a PC with PL7 software, and is connected to the telephone z z network either by: an external modem from COM1, a PCMCIA card from COM1, z or the TSX MDM 10 card if the PC has three PCMCIA slots.

The other station is a PLC connected to the telephone network via the TSX MDM 10 card.

External modem or PCMCIA modem card

Switched telephone network

Calling station

PC with PL7

Called station

PLC with TSX

MDM 10

Note: the two stations communicate in Uni-telway mode only.

Calling station The calling station is a PC with PL7 software.

Step

1

Action z z z z z

Declare the Uni-telway driver with the following values. See How to configure

the Uni-telway driver with a modem, p. 86 .

slave mode addresses 1 and 2 transmission speed of 9600 bits/s modem option selected without parity

84

35013154.02 07/2208

General

Called station The called station is a PLC with a TSX MDM 10 card.

Step

1

2

Action

Declare the TSX MDM 10 card by default: z z z z

Uni-telway protocol transmission speed of 9600 bits/s automatic switch to master mode on addresses 1 and 2 no password management

Confirm configuration.

Operation from the calling station

The following table describes the how the calling station operates from the PL7 application:

Phase

1

2

Description

When the PL7 application is started in online mode, the external modem or the

PCMCIA modem card automatically dials the telephone number of the remote station, establishes the link, then responds to prompts.

Operation is then identical to how PL7 functions when directly connected to a terminal port. All functions are available, except for application downloading.

35013154.02 07/2208

85

General

How to configure the Uni-telway driver with a modem

At a Glance

Procedure

This procedure can configure the Uni-telway driver in the Windows XP Professional and Windows VISTA Professional Edition 32 systems to communicate through a modem.

This procedure describes the different steps of the configuration:

Step

1

2

3

4

5

6

Action

Click on the Drivers XWAY icon in the Windows configuration panel).

In the UNITELWAY DRIVER tab, click on the Configuration button

Select the Communications Port and click on Modify .

In the Modem Communication box of the Uni-Telway tab, check the Use

Modem box and configure the modem connection. See How to Configure

Modem Connection, p. 87

.

Where necessary, modify the link parameters. See How to Modify the Modem

Link Parameters, p. 88 .

Click on the OK , OK , OK buttons.

86

35013154.02 07/2208

General

How to Configure Modem Connection

At a Glance

Procedure

This procedure can configure the modem connection in the

Windows XP Professional and Windows VISTA Professional Edition 32 systems in order to initialize the communication.

This procedure describes the different steps of the configuration:

Step

1

Action

Once the Use Modem box is checked,

Result

Modem Communication

Use Modem

Hayes

Tel No.

Password

AT&F&KDT

2668

User

2

3

OK Cancel

Obtain the parameters of the telephone number fields, the Hayes

Initialization string and the password.

Note:

The AT initialization command obtained is AT&F&KDT for the COM1 modems

(with &F: default configuration, &K: flow control deactivated, DT: dialing).

The telephone number is that of the station to be called (in this example 2668).

The password is that to be sent to the remote equipment when the latter is configured with a list of callers provided with a password (see List of

passwords, p. 97 ).

Confirm with the OK button.

35013154.02 07/2208

87

General

How to Modify the Modem Link Parameters

At a Glance

Procedure

This procedure can configure the transmission parameters on Windows

XP Professional and Windows VISTA Professional Edition 32 systems for modem communication.

This procedure describes the different steps of the configuration:

Step

1

Action

Select the tab Link Parameters .

Result

Station Parameters

Uni-telway Link Parameters Advanced

Speed

9600 bits/s

Self-adaptation

Valid

Data

7 bits

8 bits

1

Parity

Impair

Pair

Without

RTS/CTS Delay

Use CTS 1

Default second

Stop Bits

1 bit

2 bits

X 100 ms

OK Cancel

2

3 z z

Configure the transmission parameters:

Parity

The data bits and the stop bits :identical to parameters of the contacted station z the other parameters : unmodified

Confirm with the OK button.

88

35013154.02 07/2208

Configuring Modem communication

7

Introduction

Subject of this

Chapter

What's in this

Chapter?

This Chapter describes the Configuration process when setting up a TSX MDM 10 modem.

This chapter contains the following topics:

Topic

How to access PCMCIA modem card parameters

Modem configuration screen

Parameters in Uni-telway mode

Parameters in character mode

Modem parameters

Modem parameters for a called station

Modem parameters for a calling station

Page

90

91

92

94

96

97

98

89

35013154.02 07/2008

Modem configuration

How to access PCMCIA modem card parameters

Introduction

How to access the link

This operation describes how to access configuration parameters for the modem link via PCMCIA cards.

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

Step

1

2

Action

Access the communication channel configuration screen.

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

Example

CHANNEL 1:

CHANNEL 1 (No PCMCIA submodule)

MAST

3 Select the PCMCIA card from the drop-down menu TSX MDM 10 PCMCIA

MODEM CARD

Example

CHANNEL 1

CHANNEL 1 (No PCMCIA submodule)

(Link not configured) MAST

TSX FPP 200 PCMCIA FIPWAY CARD

TSX FPP 10 PCMCIA FIPIO CARD

TSX MBP 100 PCMCIA MODBUS+ CARD

TSX MDM 10 PCMCIA MODEM CARD

FCS SCP 111 PCMCIA CARD RS232 OPEN

FCS SCP 114 PCMCIA CARD RS485 OPEN

90

35013154.02 07/2008

Modem configuration

Modem configuration screen

Introduction

Illustration

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

The screen dedicated to modem communication looks like this:

TSX 57352 [RACK 0 POSITION 0]

Designation: TSX P PROCESSOR 57352

1

2

CHANNEL 1:

CHANNEL 1

UNI TELWAY LINK

TSX MDM 10 PCMIA MODEM CARD

MAST

Unitelway

Calling slave mode

Server address (AD0)

Number of server addresses (AD0)

1

2

Transmission Speed

9600 Bits/s

Wait timeout (ms)

Default 1000

Data

7 bits

8 bits

Parity

Even Odd

Stop

1 bit

2 bits

Without

Modem ...

Character mode …

Elements and functions

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

Address Zone

1 common

Function

See (See : PL7 Micro/Junior/Pro ; Communication applications ;

Volume 1).

2 specific is used to select or complete modem link parameters.

It is split into three different types of information: z parameters concerning communication using Uni-telway protocol, z parameters concerning communication using character mode protocol z parameters concerning the modem

35013154.02 07/2008

91

Modem configuration

Parameters in Uni-telway mode

Introduction

Calling slave mode parameters

Transmission speed

The Uni-telway protocol is proposed by default.

To use a modem with the Uni-telway protocol, the Uni-telway transmission parameters must be completed.

z z z z z z

They are split into six windows: the Calling slave mode window the Transmission speed window the Wait timeout window the Data window the Stop window the Parity window

The window looks like this:

Calling slave mode

Server address (AD0) 1

Number of server addresses (AD0) 2

It is used to select card addresses: z Server address (AD0) : selects the standard address used in Uni-telway slave z mode

Number of addresses : selects the address number used in Uni-telway mode: z z the default value is 2.

if it is a calling station , you are advised to leave 2 as the value in this field.

The window looks like this:

Transmission Speed

9600 Bits/s z z

It is used to set the transmission speed: possible values are 4800 bits/s and 9600 bits/s.

you are advised to adjust transmission speed according to the remote devices.

92

35013154.02 07/2008

Wait timeout

Data

Stop

Parity

Modem configuration

The window looks like this:

Wait timeout (ms)

Default 1000 z z z

Wait timeout is the maximum waiting time for a link acknowledgment message from a remote device (not to be confused with the application response to READ_VAR , for example): possible values are 30 ms and 30 s.

the default value is 1 s.

you are advised to adjust the transmission time to the transmission speed, and to increase the timeout over long distances (e.g. inter-continental links) or in the event of a poor quality telephone link.

The field cannot be modified. The Uni-telway protocol imposes use of 8 data bits per character.

You are advised to adjust this field according to the remote device. Generally the

Uni-telway protocol imposes use of 1 data bit per character.

Note: This field becomes unmodifiable if parity is odd or even.

The window looks like this:

Parity

Even Odd Without z z z

This field is used to define the addition or non-addition of a parity bit, and its type.

Possible values are Even, Odd, or none.

The default value is odd. Generally, parity is odd

You are advised to adjust this field according to the remote device. Generally, parity is odd for Uni-telway protocol.

35013154.02 07/2008

93

Modem configuration

Parameters in character mode

Introduction

Illustration

Parameters in character mode are used to configure the character mode protocol if the PL7 application uses this type of communication.

The configuration screen appears when Character mode is selected:

ASCII Configuration

Transmission Speed

9600 Bits/s

Data

7 bits

8 bits

Parity

Even Odd

Stop

1 bit

2 bits

Without

Stop on reception

Stop

CR LF 13

Character included

OK Cancel

Transmission speed

Data

Stop

Parity z z z

It is used to set the transmission speed: the default speed is 9600 bits/s.

possible values are 4800 bits/s and 9600 bits/s.

you are advised to adjust transmission speed according to the remote devices.

z z

The Data field is used to enter the number of data bits for coding a character: z characters are coded on 7 or 8 bits.

the default value is 8 bits.

you are advised to adjust the number of data bits according to the remote devices.

z z z

The Stop field is used to set the number of stop bits employed for detecting the end of a frame: possible values are 1 or 2 bits.

the default value is 1 bit.

you are advised to adjust the number of stop bits according to the remote devices.

z z

This field is used to define the addition or non-addition of a parity bit, and its type.

z Possible values are Even, Odd, or none.

The default value is odd.

You are advised to adjust the parity according to the remote devices.

94

35013154.02 07/2008

Stop on reception

Modem configuration z z z

The following parameters are used to define the end of message character(s): z Stop (cannot be modified): is used to activate stop on reception by an end character,

CR

LF

: is used to detect the end of a message by a carriage return,

: is used to detect the end of a message by a line feed, an entry field: is used to identify an end character which is different from a CR or

LF character, using a decimal value.

z

The possible values are: z 0 to 255 if the data is coded onto 8 bits, z 0 to 127 if the data is coded onto 7 bits,

Character included (cannot be modified): is used to include the character at the end of the reception table for the PL7 PLC application.

35013154.02 07/2008

95

Modem configuration

Modem parameters

Introduction

Illustration z z z z

The modem configuration screen is used to configure: password management, dialing mode, call parameters, connection parameters.

The configuration screen appears when the Modem button is selected:

Modem configuration

Called

Password check

Password list:

10

11

12

13

14

15

16

8

9

6

7

3

4

1

2

5

Calling

Station password:

Call parameters

Dialing time (sec):

Delay between calls (sec):

Number of redial attempts:

60

60

3

Dial mode

Tone dial

Pulse dial

Connection parameters

Maximum connection time (s): 0

Maximum time between 2 frames (sec): 0

OK Cancel

Modem configuration is split into two windows: z z a a

Called window

Calling window

96

35013154.02 07/2008

Modem configuration

Modem parameters for a called station

Introduction

Verifying the password

List of passwords z z

They are split into two parts: a Verify password field a Password list

If the box is checked, password management by the called station is enabled.

By default, password testing is disabled.

If password management is used, each called station has a list of a maximum of 8 or 16 passwords which can be used to identify 8 or 16 separate devices (only authorizes connection for these 8 or 16 devices).

The size of a word must not exceed 8 characters max. (characters = upper and lower case letters, numbers or special characters).

35013154.02 07/2008

97

Modem configuration

Modem parameters for a calling station

Introduction

Station password

Call parameters

Dial mode z z z z

They are split into two parts: a Station password field a Call parameters window a Dial mode window a Connection parameters window

Each station has its own password. It is used to identify the station. During a connection request, the calling station sends its password so that the called station can identify it and then authorize the connection.

For communication with other devices, the exchange protocol, described in exchange coding (See

Coding of exchanges, p. 107

), must be supported by the remote device.

These include all the parameters necessary in order to make a call: z Dialing time seconds.

(60 seconds by default): corresponds to the duration of a call in z Delay between calls (60 seconds by default): corresponds to the calling station waiting time, in seconds, between two connection attempts. If a connection attempt fails, the PLC attempts another call after the waiting time if the number of redials has not been exceeded.

z Number of redial attempts (3 redial attempts by default): is used to set the number of call attempts in the event of failed connection attempts. If the last call fails, the CALL_MODEM function, which launched the connection attempts, sends back an error report. If the number of redial attempts configured is 0, no redial attempts will be made.

z z

The dial modes are: either tone dial, or dialing.

98

35013154.02 07/2008

Connection parameters

Modem configuration

These include all the necessary parameters for a connection: z Maximum connection time (0 seconds by default): z is used to define the connection time in seconds. After this time has elapsed, the current connection will be stopped. This control is necessary if the sender z station is not able to disconnect from the line following an application error switching to STOP, or a system error.

z if the number of redial attempts configured is 0, this control will not be active.

Maximum time between two frames (0 seconds by default): z z if the time between two frames (in seconds) is greater than this maximum time, the connection will be broken off. This control is necessary in the event of an unused connection.

if the configured value is equal to 0 or greater than 360 seconds, communication will be broken off after 360 seconds.

35013154.02 07/2008

99

Modem configuration

100

35013154.02 07/2008

Programming Modem communication

8

Introduction

Subject of this

Chapter

What's in this

Chapter?

This chapter describes the Programming process for the setting up communication via a TSX MDM 10 modem.

This chapter contains the following topics:

Topic

CALL_MODEM communication function

Modem specific management parameters

Coding of exchanges

Guide to choosing connection parameters in Uni-telway mode

Guide to choosing connection parameters in character mode

Examples of connection, disconnection, and reset with a remote station

Examples of communication between two PLCs

Page

102

104

107

109

112

114

116

101

35013154.02 07/2008

Modem Programming

CALL_MODEM communication function

Introduction

Syntax

The CALL_MODEM communication function is used to manage connection with the

TSX MDM 10 card.

z z

It provides the option to: z connect a line between a TSX MDM 10 card and another TSX MDM 10 card, or a remote third party modem, z disconnect a line which has been established or is in the process of being established, reset the TSX MDM 10 card if necessary (following a protocol error, for example), send AT commands.

The syntax of the CALL_MODEM communication function is presented in the following format:

CALL_MODEM (ADR#0.1.SYS, 1, %MB100:20, 0, 0, %MW256:4)

The following table describes the different parameters of the function:

Parameter

ADR#0.1.SYS

1

%MB100:20

0

0

%MW256:4

Description

Broadcast address: z z z processor slot: 0 or 1,

PCMCIA channel: 1, system channel.

Command

These bytes can contain two types of information: z z either a telephone number for the station called, or an AT command to be sent.

Connection options

Choice between Uni-telway master or slave mode

Activity bit, exchange report, length

102

35013154.02 07/2008

Modem Programming

Description of parameters

Parameter

Command

Telephone number or

AT command

Connection option

Uni-telway slave or master mode

See the following table:

Type

Word

Meaning z z z z value = 1: connection command, value = 2: disconnection command, value = 3: reset modem command, value = 4: AT command to be sent.

Byte table The table’s maximum size of 24 bytes is given by the last %MWk+3 management parameter (as shown in the example for %MW259 below).

If %MWk+3 = 0, the size is 24 bytes.

word z z z z z z value = 0: connection in Uni-telway mode, with password, value = 1: connection in ASCII mode, with password, value = 2: connection in Uni-telway mode, without password, value = 3: connection in ASCII mode, without password, value = 4: connection in Uni-telway mode without character string transmission on connection request, value = 5: connection in ASCII mode without character string transmission on connection request.

word z z value = 0: connection in Uni-telway slave mode, value not equal to 0: connection in Uni-telway master mode z byte 0 (least significant) corresponds to the number of slave addresses z value = 1: for Ad0 value = 2: for Ad0 and Ad1 byte 1 (most significant) corresponds to address Ad0 for the Uni-telway slave (from 1 to 98)

35013154.02 07/2008

103

Modem Programming

Modem specific management parameters

Introduction A detailed description of these parameters is available in the common section. See

(PL7 Micro/Junior/Pro ; Communication applications ; Volume 1).

This document only describes parameters specific to communication via a modem.

z z

These parameters are:

Timeout, operation report.

CALL_MODEM function timeout

Timeout of the function is a time used to check for the absence of response to the

CALL_MODEM function.

This time, (increment of a 100 ms time base), is a combination of different parameters configured via the Modem Configuration screen.

It is advisable to allocate the following minimum value to this parameter:

Minimum timeout = the number of redial attempts * dialing time + (number of redial attempts - 1) * delay between redial attempts

Operation report Operation reports are specific to the modem and only significant if the z z communication report has the following values:

16#00,

16#FF.

104

35013154.02 07/2008

Modem Programming

Communication report = 16#00

In this case, the exchange is correct.

In this case, the operation report (most significant byte) is:

Value

16#00

16#01

16#02

16#03

16#04

16#05

16#06

16#07

16#09

16#0A

16#0B

16#0C

Meaning

Command executed

Non processed request

Incorrect response

Connection in progress by a remote modem

Connection in progress by a local CALL_MODEM function

Connection in progress by an external CALL_MODEM function

Connection request by a local CALL_MODEM function

Connection request by an external CALL_MODEM function

Remote station busy

Disconnection by a remote modem

Disconnection due to protocol error

Disconnection by timeout

35013154.02 07/2008

105

Modem Programming

Communication report = 16#FF

In this case, the message is refused.

In this case, the operation report (most significant byte) is:

16#08

16#0B

16#0C

16#0D

16#0F

16#11

16#12

16#14

Value

16#01

16#02

16#03

16#04

16#05

16#06

16#07

16#15

16#16

16#17

Meaning

Lack of resources on connection to processor

Lack of line resources

Device missing on line

Line error

Length error

Communication channel faulty

Addressing error

Application fault

No system resources

Inactive communication function

Destination missing

Intra-station routing problem or non configured channel

Address format not handled

Lack of destination resource

Non operational connection

Absence of resource on the local channel

Non-authorized access

Incompatible network configuration

106

35013154.02 07/2008

Modem Programming

Coding of exchanges

At a Glance

Format of the string

When a connection request is made, a 32-byte character string may be sent on the line by the calling station to initialize the connection.

z z z z z z z

The character string which may be sent on the line is in the following format: the Start of the frame field, of 2 bytes in length, containing the value 16#531B, the Password field, of 8 bytes in length, containing the value of the station z password (8 characters), the Type field, (protocol type) of 1 byte in length, containing 16#00 for Uni-telway z mode or 16#01 for ASCII mode, the UTW field, (Unitelway mode) of 1 byte in length, containing 16#00 for a master or 16#01 for a slave, the Slave address field, with the slave address stated in 1 byte , the Number of slaves

1 byte ,

field, stating the number of slave address scanned in the the the

Reserved field, containing

Checksum field, of

Start of the frame

1 byte in length, which checks the frame,

field, of

15 bytes

2 bytes

, all reserved and equal to 0,

in length, containing the value 16#451B, z z

Note: This coding of this string depends on the following parameters:

Station password of the modem configuration screen,

Mode and Options of the communication function.

The "Checksum" is performed over 1 byte, without taking into consideration the value of the most significant byte.

Note: The password must not exceed 8 characters in length .

35013154.02 07/2008

107

Modem Programming

Processing of the string

The following table lists different processing scenarios:

Calling station (TSX MDM 10) z z if the station is configured by default, the modem transmits no character string on the line: z connection without password ( CALL_MODEM z function with option 4),

Slave Uni-telway protocol with addresses Ad0 = 1 and Ad1 = 2.

in all other scenarios, the station sends the character string.

Station called (TSX MDM 10)

Scenario where password management is not configured z the station waits for 5 seconds. If no character string has been received on the line, it switches to Uni-telway master mode and scans the slave addresses Ad0 = 1 z and Ad1 = 2, otherwise the station tests the Password field equal to

FFFFFFFF in hexadecimal: z if the test is valid, the station tests the Type, Mode z and Number of addresses fields, and switches to the corresponding mode.

If the test is invalid, the line is closed.

Scenario where password management is configured z the station tests the received password: z if the password received does not correspond to any password in the list, the line is closed.

z if the test is valid, the station tests the Type, Mode and Number of addresses fields, and switches to the corresponding mode.

108

35013154.02 07/2008

Modem Programming

Guide to choosing connection parameters in Uni-telway mode

Introduction z z

The Uni-telway master or slave mode, as well as the addresses used, depend on the following parameters: the parameters of the Calling mode field in the configuration screen, the Mode parameter for the CALL_MODEM communication function.

Communication between two

TSX MDM 10 cards

Calling: TSX MDM 10

Screen parameters

Usage parameters for the calling station:

CALL_MODEM mode

Designation

Case 1

By default:

Ad0 = 1 and address number = 2

By default: value 0

Case 2

Ad0 = n and address number = 2

By default: value 0

Case 3

By default:

Ad0 = 1 and address number = 2

Value xx

Byte 0 = 02

Byte 1 = 50

Slave to be scanned at address 50 to 51

Becomes Uni-telway slave with addresses Ad0 = 1 and

Ad1 = 2

Becomes Uni-telway slave with addresses Ad0 = n and

Ad1 = n+1

Becomes Uni-telway master and scans addresses 50 and 51

Called: TSX MDM 10

Screen parameters

Designation

Usage parameters for the called station:

Case 1

By default:

Ad0 = 1 and address number = 2

Becomes Uni-telway master and scans addresses 1 and 2

Case 2

Immaterial

Becomes Uni-telway master and scans addresses n and n+1

Case 3

Immaterial

Becomes slave which responds on addresses 50 and 51

The following is a list of comments relating to the various possible cases: z case 1 is the most common (for communication between two TSX MDM 10 z devices), case two is used to attribute a different slave address to each calling station z

(useful in multi-station architecture), case 3 is used to communicate with devices configured in Uni-telway slave mode.

35013154.02 07/2008

109

Modem Programming

Communication with a third party device

Calling: TSX MDM 10

Screen parameters

CALL_MODEM mode

Designation

Usage parameters for the calling station (TSX MDM 10 card):

Case 1

By default:

Ad0 = 1 and address number = 2

By default: value 0

Case 2

Ad0 = n and address number = 2

Case 3

By default:

Ad0 = 1 and address number = 2

By default: value 0

Value xx

Byte 0 = 02

Byte 1 = 50

Slave to be scanned at address 50 to 51

Becomes Uni-telway slave with addresses Ad0 = 1 and

Ad1 = 2

Becomes Uni-telway slave with addresses Ad0 = n and

Ad1 = n+1

Becomes Uni-telway master and scans addresses 50 and 51

Usage parameters for the called station (third party device):

Called: third party device Case 1

Designation Becomes Uni-telway master and scans addresses 1 and 2

Case 2

Becomes Uni-telway master and scans addresses n and n+1

Case 3

Becomes slave which responds on addresses 50 and 51 z z z

The following is a list of comments relating to the various possible cases: case 1 is not significant, for case 2, the initialization protocol must be implemented (exchange coding), for case 3, the initialization protocol must be implemented (exchange coding).

110

35013154.02 07/2008

Modem Programming

Communication from a third party device

Usage parameters for the calling station (third party device):

Calling: third party device Case 1

Designation Becomes slave which responds on addresses 1 and 2

Case 2

Becomes slave which responds on addresses n and n+1

Case 3

Becomes a Uni-telway master and scans addresses configured on the TSX MDM 10 card

Called: TSX MDM 10

Screen parameters

Designation

Usage parameters for the called station (TSX MDM 10 card):

Case 1

By default:

Ad0 = 1 and address number = 2

Case 2

Requires the configuration

Ad0 = n and address number = 2

Case 3

Immaterial

Becomes Uni-telway master and scans addresses Ad0 = 1 and Ad1

= 2

Becomes Uni-telway master and scans addresses Ad0 = n and Ad1

= n+1

Becomes a Uni-telway slave with the configured addresses z z

The following is a list of comments relating to the various possible cases: cases 1 and 2 are not significant, for case 3, the initialization protocol must be implemented (exchange coding).

35013154.02 07/2008

111

Modem Programming

Guide to choosing connection parameters in character mode

Introduction z z

The character mode depends on the following parameters: the configuration screen parameters, the Option parameter for the CALL_MODEM communication function.

Communication between two

TSX MDM 10 cards

Calling: TSX MDM 10

Screen parameters

CALL_MODEM option

Usage parameters for the calling station:

Configuration in character mode (data coded on 8 bits)

Character mode protocol

Usage parameters for the called station:

Called: TSX MDM 10

Screen parameters Configuration in character mode is identical to that of calling station

Note: In this configuration, the character string, described in the exchange coding, is transmitted on the line.

Communication with a third party device

Calling: TSX MDM 10

Screen parameters

CALL_MODEM option

Usage parameters for the calling station (TSX MDM 10 card):

Configuration in character mode (data coded on 8 bits)

Character mode protocol

Usage parameters for the called station (third party device):

Called: third party device

Screen parameters Implementation of initialization protocol (exchange coding)

Note: In this configuration, the character string, described in the exchange coding, is transmitted on the line.

112

35013154.02 07/2008

Modem Programming

Communication from a third party device

Usage parameters for the calling station (third party device):

Calling: third party device

Screen parameters Configuration in character mode (data coded on 8 bits)

Designation Implementation of initialization protocol (exchange coding) for sending the character string

Usage parameters for the called station (TSX MDM 10 card):

Called: TSX MDM 10

Screen parameters Configuration in character mode is identical to that of calling station

Note: In this configuration, the character string, described in the exchange coding, is transmitted on the line.

35013154.02 07/2008

113

Modem Programming

Examples of connection, disconnection, and reset with a remote station

Introduction

Example 1

The following examples are to assist with installation of the various CALL_MODEM services.

Connection in Uni-telway slave mode, without password:

CALL_MODEM(ADR#0.1.SYS, 1, %MB100:20, 2, 0, %MW256:4)

The following table describes the different parameters of the function:

Parameter

ADR#0.1.SYS

1

%MB100:20

2

0

%MW256:4

Description

Modem address

Connection

Telephone number of called station

Uni-telway mode, without password

Uni-telway slave mode

Activity bit, exchange report, length

Example 2 Connection in Uni-telway slave mode, with password:

CALL_MODEM(ADR#0.1.SYS, 1, %MB100:20, 0, 0, %MW256:4)

The following table describes the different parameters of the function:

Parameter

ADR#0.1.SYS

1

%MB100:20

0

0

%MW256:4

Description

Modem address

Connection

Telephone number of called station

Uni-telway mode, with password

Uni-telway slave mode

Activity bit, exchange report, length

114

35013154.02 07/2008

Example 3

Example 4

Modem Programming

Disconnection request:

CALL_MODEM(ADR#0.1.SYS, 2, %MB100:20, 2, 0, %MW256:4)

The following table describes the different parameters of the function:

Parameter

ADR#0.1.SYS

2

%MW256:4

Description

Modem address

Disconnection

Activity bit, exchange report, length

Note: In this example details of the telephone number, the Uni-telway slave mode and password are unnecessary. The line is interrupted.

Request to reset modem:

CALL_MODEM(ADR#0.1.SYS, 3, %MB100:20, 2, 0, %MW256:4)

The following table describes the different parameters of the function:

Parameter

ADR#0.1.SYS

3

%MW256:4

Description

Modem address

Modem reset

Activity bit, exchange report, length

Note: In this example details of the telephone number, the Uni-telway slave mode and password are unnecessary. The modem is reset.

A reset does not interrupt a connection request in progress

35013154.02 07/2008

115

Modem Programming

Examples of communication between two PLCs

Introduction

Connection phase z z z

The following example describes the different phases of a communication between two Micro PLCs linked by the telephone network: the connection phase, the data exchange phase, the disconnection phase.

The calling station makes the call in Uni-telway slave mode without password management:

CALL_MODEM(ADR#0.1.SYS, 1, %MB50:4, 2, 0, %MW1024:4)

The following table describes the different parameters of the function:

Parameter

Address

Command 1

Telephone number %MB50:4

Option 2

Mode

Report

Variable

ADR#0.1.SYS

0

%MW1024:4

Description

Modem address

Processor slot: 0 or 1

PCMCIA channel: 1

System server: SYS

Connection command

Telephone number of called station (in bytes)

Connection in Uni-telway mode, without password

Connection in Uni-telway slave mode

%MW1026 = 300, corresponds to a 30 second time-out.

%MW 1027 = 4, corresponds to the length in bytes of the telephone number to call (4 bytes in the example).

116

35013154.02 07/2008

Modem Programming

Data exchange phase

The calling station reads the called station’s internal words, %MW100 to %MW199.

This latter station is considered the Uni-telway master:

READ_VAR(ADR#0.1.1, ‘%MW’, 100, 100, %MW200:100, %MW1094:4)

The following table describes the different parameters of the function:

Parameter

Address

Type of object

Number of first object

Consecutive numbers

Content of response

Report

Variable

ADR#0.1.1

‘%MW’

100

100

%MW200:100

%MW1094:4

Description

Address of the Uni-telway master station to be scanned

Internal words

Shows the index of the first internal word to be read (%MW100)

Specifies the number of internal words to be read

(100 words)

Table of words containing the value of objects read

Disconnection phase

The calling station disconnects the line:

CALL_MODEM(ADR#0.1.SYS, 2, %MB50:4, 2, 0, %MW1028:4)

The following table describes the different parameters of the function:

Parameter

Address

Command 2

Telephone number %MB50:4

Option 2

Mode

Report

Variable

ADR#0.1.SYS

0

%MW1028:4

Description

Modem address

Processor slot: 0 or 1

PCMCIA channel: 1

System server: SYS

Disconnection command

Telephone number of called station (in bytes)

Connection in Uni-telway mode, without password

Connection in Uni-telway slave mode

%MW1030 = 300, corresponds to a 30 second time-out.

%MW 1031 = 4, corresponds to the length in bytes of the telephone number to call (4 bytes in the example).

35013154.02 07/2008

117

Modem Programming

118

35013154.02 07/2008

Debugging Modem communication

9

Introduction

Subject of this

Chapter

What's in this

Chapter?

This Chapter describes the Debugging process when setting up a TSX MDM 10 modem.

This chapter contains the following topics:

Topic

Modem debugging screen

Debugging parameters

Page

120

121

35013154.02 07/2008

119

Modem debugging

Modem debugging screen

Introduction

Illustration

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

The screen dedicated to Modbus communication looks like this:

1

2

TSX 57252 [RACK 0 POSITION 0]

Debugging

Designation: TSX P 57252 PROCESSOR Version: 3.3

DIAG...

CHANNEL 1 TSX MDM 10 PCMCIA MODEM CARD

UNI-TELWAY LINK MAST

Communication mode

Command

Transparent

Order to dial

Yes

No

Called phone number

Password received

Number of redial attempts

Time between redial attempts

Remaining dialing time

Remaining connection time

0

0

0

0

DIAG...

Mode

Calling

Local EF “Call_Modem”

External EF “Call_Modem”

Called

Cause of disconnection

EF “Call_Modem”

Protocol error

Modem (CD)

Connection timeout

Timeout between 2 frames

Password error

Elements and functions

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

Address Zone

1 common

2 specific

Function

See (See : PL7 Micro/Junior/Pro ; Communication applications

; Volume 1).

is used to access the debugging parameters for a Modem link.

120

35013154.02 07/2008

Modem debugging

Debugging parameters

Introduction z z z z

The specific part is split into several windows: the Communication mode window, the Order to dial window, the Mode window, z the Cause of disconnection a field grouping.

window,

Communication mode z z

This is used to identify the state of connection: command: connection request in progress (connection being established), transparent: connection established.

Order to dial This indicates if a CALL_MODEM communication function has been received by the

TSX MDM 10 card and is being processed.

Mode

Cause of disconnection

This is used to specify the connection mode: z calling: the station initiated the call. The screen shows whether the CALL_MODEM communication function has been sent by the local station or by a remote station via a network, z called: the station is the call receiver.

z z z z

This indicates the causes of a line disconnection: z EF CALL_MODEM: the local station has initiated the disconnection using the

CALL_MODEM function, protocol error: a protocol error is the cause of the disconnection, modem (CD): the remote modem has initiated the disconnection, connection timeout: the duration of the connection has overrun, z timeout between 2 frames: the delay between 2 frames has overrun, password error: the password received is invalid - it does not appear in the local station list.

Additional fields They provide the following information: z z number of redial attempts: indicates the number of redial attempts remaining, time between redial attempts: indicates the time remaining between redial attempts, z z remaining dialing time: indicates the remaining dialing time, remaining connection time: indicates the remaining connection time (if the local station is connected).

35013154.02 07/2008

121

Modem debugging

122

35013154.02 07/2008

Language objects associated with

Modem communication

10

Introduction

Subject of this

Section

What's in this

Chapter?

This Chapter introduces language objects associated with communication via a

TSX MDM 10 modem.

This chapter contains the following topics:

Topic

Language objects in implicit exchange

Language objects for explicit exchange

Explicit exchange management and reports

Language objects associated with configuration

Page

124

125

129

130

123

35013154.02 07/2008

Modem language objects

Language objects in implicit exchange

Introduction

Bit objects

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

Micro/Junior/Pro ; Communication applications ; Volume 1)

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 is faulty,…)

This bit set at 1 indicates a faulty 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.

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

Object (1)

%IWxy.i.0

%IWxy.i.1

Function

Not used

General status of slaves

Meaning

x0 = 1: if at least one slave does not respond

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.

124

35013154.02 07/2008

Modem language objects

Language objects for explicit exchange

Introduction

Word objects

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

Micro/Junior/Pro ; Communication applications ; Volume 1)

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

to

%MWxy.i.7

%MWxy.i.8

Standard channel status

Specific channel status

Not used

Slave address

Meaning z z z z z z 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 z z z z z z x0 = 1: single station on the network, x1 = 1: not used, x2 = 1: transmission line error, x3 = 1: not used, x4 = 1: internal software fault, x5 = 1: error in hard- or software configuration, or configuration missing, x6 = 1: communication error with the processor, x7 = 1: application fault (double address station).

0 for Uni-telway master mode

1 for Uni-telway slave mode

-

Standard address of calling slave

35013154.02 07/2008

125

Modem language objects

Object (1)

%MWxy.i.12

Function

Modem status

%MWxy.i.13

to

%MWxy.i.16

%MWxy.i.17

Current password

Modem state

Meaning z z z z z z z z z z z z z z z z z z x0 = 0: command mode (to establish a connection), x0 = 1: transparent mode (connection established), x1 = 0: calling mode (transmitter station), x1 = 1: called mode (receiver station), x2 = 1: connection request, x3 = 1: dialing request, x4 = 1: disconnection request, x5 = 1: connection via CALL_MODEM local function, x6 = 1: connection via CALL_MODEM external function, x7 = 1: connection via a remote modem, x2 = 0: disconnection via CALL_MODEM local function, x9 = 1: disconnection via CALL_MODEM external function, x10 = 1: disconnection using timeout, x11 = 1: disconnection due to protocol error, x12 = 1: disconnection via a remote modem, x13 = 1: disconnection following password error, x14 = 1: disconnection caused by configured timeout, x15 = 1: modem error.

Transmitter (calling) station password z z z z z z z z z x0 = 1: initialization of the card active, x1 = 1: command mode active, x2 = 1: transparent mode active, x3 = 1: dialing in progress, x4 = 1: disconnecting, x5 = 1: call in progress, x6 = 1: busy, x12 = 1: card initialization error, x13 = 1: card initialization request.

126

35013154.02 07/2008

35013154.02 07/2008

Modem language objects

%MWxy.i.21

to

%MWxy.i.32

%MWxy.i.33

%MWxy.i.34

%MWxy.i.35

%MWxy.i.36

%MWxy.i.37

%MWxy.i.38

Object (1)

%MWxy.i.18

%MWxy.i.19

%MWxy.i.20

Function

Dialing state

State of called unit

Connection state

Telephone number

Meaning z z z z z z z z z z z z z z z z z z z z z z z z x0 = 1: dialing in progress, x1 = 1: AT D command transmission (dialing), x2 = 1: connection received, x3 = 1: password test running, x4 = 1: valid password received, x5 = 1: protocol mode can be activated, x6 :not used, x7 = 1:Carriage Return not detected, x8 = 1: DCD signal missing, x9 = 1: dialing time overrun, x10 = 1: general input/output error, x11 = 1: illegal command, x12 = 1: disconnection while dialing.

x0 = 1: call in progress, x1 = 1: AT A command transmission (answer), x2 = 1: connection received, x3 = 1: password test running, x4 = 1: password received, x5 = 1: password not received, x6 = 1: Carriage Return not detected, x10 = 1: general input/output error, x11 = 1: illegal command.

z x0 = 1: DTR signal active, x1 = 1: AT H command transmission

(hang up), x2 = 1: awaiting disconnection.

Telephone number of called station

Remaining number of redial attempts

Delay between remaining calls

Remaining dialing time

Remaining time between 2 messages

Input character trace

Remaining number of calls to be made

Remaining delay value between calls is between

0 and 255 (between 30 s and 180 s)

Remaining dialing time value is between 40 and

255 seconds

Remaining time value between two frames

Remaining connection time

Display of remaining connection time

Offset of last character received, between 0 and

99 bytes

127

Modem language objects

Object (1)

%MWxy.i.39

to

%MWxy.i.88

%MWxy.i.89

Function Meaning

Input character trace Trace of 100 input characters

%MWxy.i.90

to

%MWxy.i.139

Output character trace Offset of last character transmitted, between 0 and 99 bytes

Output character trace Trace of 100 output characters

Key

(1) z z z

Address xy.i

x: corresponds to the rack number, y: corresponds to the module number, i: corresponds to the channel number.

128

35013154.02 07/2008

Modem language objects

Explicit exchange management and reports

Introduction

Word objects

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

(See : PL7 Micro/Junior/Pro ; Communication applications ; Volume 1)

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

Object (1) Function

%MWxy.MOD.0 Module exchanges in progress

Meaning z z z x0 = 1: reading status in progress x1 = 1: sending of command parameters to the communication module x2 = 1: sending of adjustment parameters to the communication module

%MWxy.MOD.1 Module report

%MWxy.i.0

%MWxy.i.1

Channel exchanges in progress

Channel report z z 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: reading status in progress x1 = 1: sending of command parameters to the communication channel x2 = 1: sending of adjustment parameters to the communication channel z z 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

35013154.02 07/2008

129

Modem language objects

Language objects associated with configuration

Introduction

Internal constants

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

The following table describes the internal constants:

Object

%KWxy.i.0

%KWxy.i.1

%KWxy.i.2

%KWxy.i.3

Function

Type

Speed / format

Timeout

Slave address

Meaning

0 for Uni-telway mode

Byte 0 = speed z 16#00 = 1200 bits/s, ..., 16#03 = 9600 bits/s

Byte 1: format z z z z x8: bit number (1 = 8 bits, 0 = 7 bits) x9 = 1: parity management x10: Parity type (1 = odd, 0 = even) x11: stop bit (1 = 1 bit, 0 = 2 bits)

Value of timeout

Byte 0: standard slave address

Byte 1: number of consecutive addresses

(from 1 to 3)

%KWxy.i.4

Not used

%KWxy.i.5

RTS/CTS delay Value of delay in hundredths of a millisecond

%KWxy.i.6

Speed / Format in ASCII mode

Byte 0 = speed in ASCII mode z 16#00 = 1200 bits/s, ...,16#03 = 9600 bits/s z z z z

Byte 1: format in ASCII mode x8: bit number (1 = 8 bits, 0 = 7 bits) x9 = 1: parity management x10: Parity type (1 = odd, 0 = even) x11: stop bit (1 = 1 bit, 0 = 2 bits)

%KWxy.i.7

Stop Bits received Byte 0 z z x0 = 1: end character enabled x1 = 1: end character included

Byte 1: value of frame end character

%KWxy.i.8

Not used

%KWxy.i.9

Number of redial attempts

%KWxy.i.10

Delay between redial attempts

Value between 0 and 10 redial attempts

Byte 0: delay between redial attempts in seconds, value between 30 and 180 seconds in increments of

30 s

130

35013154.02 07/2008

Modem language objects

Object Function Meaning

%KWxy.i.11

Dial mode z z z

Byte 0: type of dialing z x0 = 0: tone dial x0 = 1: pulse dial x1 = 0: password test x1 = 1: no password test

Byte 1: dialing time value between 30 and 180 seconds in increments of 30 s

%KWxy.i.12

Maximum time between

2 messages

Message transfer check, value in seconds between

0 and 32767 seconds

%KWxy.i.13

Maximum connection time

%KWxy.i.14 to 17

Passwords z z

Value between 0 and 32767 seconds

= 0: no connection time control

> 0: connection time control

148 byte string

Micro internal constants

The following table describes internal constants for Micro PLCs:

Object

%KWxy.i.18 to 49

%KWxy.i.50 to 123

Function

List of passwords

Modem string

Meaning

List of 8 passwords, with a maximum of 8 characters per password

148 byte string

Premium internal constants

The following table describes internal constants for Premium PLCs:

Object

%KWxy.i.18 to 81

%KWxy.i.82 to 155

Function

List of passwords

Modem string

Meaning

List of 16 passwords, with a maximum of 8 characters per password

148 byte string

35013154.02 07/2008

131

Modem language objects

132

35013154.02 07/2008

Appendices

11

Introduction

Subject of this

Chapter

What's in this

Chapter?

This Chapter introduces AT commands associated with the TSX MDM 10 modem.

This chapter contains the following topics:

Topic

AT commands

A/ - Command re-execution

AT = x - Write to the selected S register

AT? - Read the selected S register

A - Answer

Cn - Checking for carrier

Dn - Dialing

En - Local command echo

Hn - Disconnection (hang up)

In - Identification

Ln - Loudspeaker volume

Mn - Loudspeaker command

Nn - Activation of automatic mode.

On- Return to on-line data mode

P - Default adjustment of pulse dialing

Qn - Activation / deactivation of result codes

Sn - S register read / write

T - Default adjustment of tone dialing

Vn - Form of the result codes

Wn - Error correction messages control

148

149

150

151

144

145

146

147

Page

135

137

138

139

140

141

142

152

153

154

155

156

35013154.02 07/2008

133

Appendices

Topic

Xn - Extended result codes

Yn - Disconnection after prolonged inactivity

Zn - Software reset of modem and restoration of profile

&Cn - RLSD Option (detection of DCD carrier)

&Dn - DTR Option (Data Terminal Ready)

&Fn - Restoration of the factory configuration (profile)

&Gn - Selection of guard tone

&Kn – Flow control

&Pn - Selection of pulse dialing close/open report

&Qn - Synchronous/asynchronous mode

&Rn - RTS/CTS option

&Sn - DSR Monitoring (Data Station Ready)

&V - Display of current configuration and stored profiles

&Wn – Storage of the current configuration

&Yn - Designation of a default profile on reset

&Zn – Storage of telephone numbers

%Cn - Activation / deactivation of data compression

%En - Activation/deactivation of line quality monitoring or automatic resynchronization or fallback/increase of transfer rate

%L - Level of line signal

%Q - Quality of line signal

\Kn - BREAK control

\Nn - Operating mode

Values of the registers of the TSX MDM 10 card in a PLC

169

170

171

172

173

174

175

176

177

Page

157

161

162

163

164

165

166

167

168

178

179

180

182

183

134

35013154.02 07/2008

Appendices

AT commands

Introduction

Available commands

The modem will respond to the commands described below. The parameters which can be associated with each command are given in the command description. The default values indicated for each configuration command are those used by the

Rockwell factory profile.

The following table recapitulates the AT commands supported by the TSX MDM 10:

Sn

T

Vn

Wn

Xn

Yn

Zn

&Cn

&Dn

&Fn

&Gn

Nn

On

P

Qn

Hn

In

Ln

Mn

A

Cn

Dn

En

Command

A/

AT = x

AT?

Description

Command re-execution

Write to the selected S register

Read the selected S register

Answer

Checking for carrier

Dialing

Local command echo

Disconnection (hang up)

Identification

Loudspeaker volume

Loudspeaker command

Loudspeaker activation

Return to on-line data mode

Default adjustment of pulse dialing

Activation / deactivation of result codes

S register read / write

Default adjustment of tone dialing

Form of the result codes

Error correction messages control

Extended result codes

Disconnection after prolonged inactivity

Software reset of modem and restoration of profile

RLSD Option (detection of DCD carrier)

DTR Option (Data Terminal Ready)

Restoration of the factory configuration (profile)

Selection of guard tone

35013154.02 07/2008

135

Appendices

%L

%Q

\Kn

\Nn

\Vn

Command

&Kn

&Pn

&Qn

&Rn

&Sn

&V

&v1

&Wn

&Yn

&Zn

%Cn

%En

Description

Flow control

Selection of pulse dialing close/open report

Synchronous/asynchronous mode

RTS/CTS option

DSR check (Data Station Ready)

Display of current configuration and stored profiles

Display of statistics from last connection)

Storage of current configuration

Designation of a default profile on reset

Storage of telephone numbers

Activation / deactivation of data compression

Activation/deactivation of line quality monitoring and automatic resynchronization attempt or of fallback/increase of transfer rate

Level of line signal

Quality of line signal

"Break" control

Operating mode

Validation of single line connection messages

136

35013154.02 07/2008

Appendices

A/ - Command re-execution

Introduction The modem behaves as though the last command line had been returned by the

DTE. "A/" repeats all the commands contained in the command buffer.

The principal use of this command is to be able to renew a call (using the dial command) which has not finished following an engaged signal or no reply. This command must appear alone on the command line and must finish with the character "/". It must not finish with a carriage return.

35013154.02 07/2008

137

Appendices

AT = x - Write to the selected S register

Introduction

Result codes

This command writes the value x in the S register which is currently selected. It is possible to select an S register with the ATSn command.

All S registers will send back an OK if x is a number.

Code

OK

Description

For all arguments

138

35013154.02 07/2008

Appendices

AT? - Read the selected S register

Introduction

Result codes

This command reads and displays the selected S register. It is possible to select an

S register with the ATSn command.

All S registers will send back an OK if x is a number.

Code

OK

Description

For all arguments

35013154.02 07/2008

139

Appendices

A - Answer

Introduction The modem connects and attempts to answer the call received if all the necessary conditions have been fulfilled.

Once contact has been made, the modem connects in answer mode.

140

35013154.02 07/2008

Appendices

Cn - Checking for carrier

Introduction

Result codes

This command is included solely for reasons of compatibility; its only effect is to return a result code. The only valid parameter is 1.

The following table lists the possible command responses.

Code

OK

ERROR

Description n = 1

If n is not equal to 1

35013154.02 07/2008

141

Appendices

Dn - Dialing

Introduction This command asks the modem to unhook, to dial the number corresponding to the dialing string entered and to attempt to establish a connection. In the absence of a dialing string, the modem unhooks and attempts to make contact in send mode.

Dialing Modifiers The valid parameters for the dialing string are described in the following table: For reasons of clarity, it is possible to use certain punctuation symbols such as brackets, hyphens or spaces. These symbols are not processed by the command.

*

#

Code

0 - 9

A - D

L

P

T

R

S = n

!

W

@

,

Description

Numbers 0 to 9 in MFDT

The "asterisk" symbol (tone dialing only)

The "hash" symbol (tone dialing only)

Letters A, B, C and D in MFDT. In certain countries, these letters cannot be sent during dialing.

Redial the last number: the modem redials the last valid telephone number.

The L must come immediately after the D and all subsequent characters are ignored.

Selects pulse dialing: pulse dialing dials the numbers which follow until a 'T' is reached. This applies to current and subsequent dialing. In certain countries, the dialing mode cannot be changed once the first number has been dialed.

Selects tone dialing: tone dialing dials the numbers which follow until a 'P' is reached. This applies to current and subsequent dialing. In certain countries, the dialing mode cannot be changed once the first number has been dialed.

This command will be accepted but it will have no effect.

Dialing of number stored in directory (n = 0 to 19) (see command &Z).

Quick hang up: the modem hangs up during the period defined by the value of

S29. In certain countries, a limit may be imposed on this period.

Waiting for tone: the modem waits for the tone before dialing the digits which come after the 'W'.

Waiting for silence: the modem waits until there are at least 5 seconds of silence in the call frequency band before dialing the dialing string. If the modem does not detect these 5 seconds of silence after a period defined by the call abandon timer (S7), the modem ends the call attempt with a NO ANSWER message. If the detection of an engaged line is validated, the modem can end the call with the result code BUSY. If the answer tone comes while this parameter is being carried out, the modem makes contact.

Dialing pause: the modem pauses for the period indicated by S8 before dialing the digits which come after the ','.

142

35013154.02 07/2008

Appendices

Code Description

;

^

Returns to command mode. Added to the end of the dialing string, this parameter returns the modem to command mode once it has processed the part of the string which precedes ','. This enables new AT commands to be sent while off-hook. The new AT commands can be set on the source command line after ',' or entered on new command lines. The modem does not attempt to establish the connection until the new dial command is sent without the end symbol ','. Use 'H' to abandon dialing in progress and hang up.

Switch call tone: only applies to the dialing attempt in progress.

Ignored: can be used to format the dialing string.

( )

Ignored: can be used to format the dialing string.

<space> Ignored: can be used to format the dialing string.

<i> Invalid symbol: will be ignored.

35013154.02 07/2008

143

Appendices

En - Local command echo

Introduction

Parameters

According to the parameter indicated, the modem activates or deactivates the appearance of the characters on the DTE. The parameter value, if valid, is written in the S14 bit.

The parameters are.

Code

E0

E1

Description

Deactivates command echo.

Activates command echo (default value)

Result codes The following table lists the possible command responses.

Code

OK

ERROR

Description n = 0 or 1.

If n is not equal to 0 or 1.

144

35013154.02 07/2008

Appendices

Hn - Disconnection (hang up)

Introduction

Parameters

This command launches a hanging up sequence; it is possible that it is not available in certain countries.

The parameters are:

Code

H0

H1

Description

The modem frees the line if it is currently connected, and ends all attempts

(AT&T) in progress. Any processing which is particular to a country, to the modulation or to the error correction protocol (S38) is carried out outside the

H0 command.

Only in STN mode; if the modem is on-hook, it unhooks and goes into command mode. The modem hangs up at the end of the time period defined by S7.

Result codes The following table lists the possible command responses.

Code

OK

ERROR

Description n = 0 or 1.

If n is not equal to 0 or 1.

35013154.02 07/2008

145

Appendices

In - Identification

Introduction

Parameters

The modem reports the result corresponding to the entered command parameter to the DTE.

I4

I5

I6

Code

I0

I1

I3

The parameters are:

Description

Gives the product code (e.g. '14400').

Gives the pre-calculated checksum of the read-only memory ROM (e.g. '007').

Gives the firmware revision level (e.g. 'V1.000S').

Gives the identification string defined by the OEM (e.g. 'RC96ACL').

Gives the country code (e.g. '022').

Gives the model of the modem data pumping device.

Result codes The following table lists the possible command responses.

Code

OK

ERROR

Description n = 0 to 6.

If n is not in the range 0 to 6.

146

35013154.02 07/2008

Appendices

Ln - Loudspeaker volume

Introduction

Parameters

The modem adjusts the loudspeaker volume control according to the parameter entered. The parameter value, if valid, is written in bits 0 and 1 of S22.

The parameters are:

Code

L0

L1

L2

L3

Description

Low or deactivated volume.

Low volume (default value).

Medium volume.

High volume.

Result codes The following table lists the possible command responses.

Code

OK

ERROR

Description n = 0 to 3.

If n is not in the range 0 to 3.

35013154.02 07/2008

147

Appendices

Mn - Loudspeaker command

Introduction

Parameters

This command controls the moment at which the loudspeaker is active or deactivated. The parameter value, if valid, is written in bits 2 and 3 of S22.

The parameters are:

Code

M0

M1

M2

M3

Description

The loudspeaker is always deactivated.

The loudspeaker is activated during establishment of the call but deactivated during reception of the carrier (default value).

The loudspeaker is always activated.

The loudspeaker is deactivated during reception of the carrier and during dialing.

Result codes The following table lists the possible command responses.

Code

OK

ERROR

Description n = 0 to 3.

If n is not in the range 0 to 3.

148

35013154.02 07/2008

Appendices

Nn - Activation of automatic mode.

Introduction

Parameters

This command activates or deactivates detection of automatic mode. The parameter value, if valid, is written in bit 1 of S31.

The parameters are:

Code

N0

N1

Description

Detection of automatic mode is deactivated (equivalent to giving the 0 value to the sub-parameter +MS). The handshaking which follows is made according to the content of S37 or, if S37 is at 0, according to the most recently detected

DTE baud rate.

Detection of automatic mode is activated (equivalent to giving the value 1 to the sub-parameter +MS). The handshaking which follows is made according to the automatic mode algorithm supported by the modem, in other words according to the content of S37 or, if S37 is 0, by starting at 28800 b/s V.34 (RC288). This command also equates to F0 (RC144) (default value).

Result codes

Observations

The following table lists the possible command responses.

Code

OK

ERROR

Description n = 0 to 1.

If n is not in the range 0 to 1.

1.

The Nn and S37=x commands have priority over the values of the +MS command. When the N0 or N1 command is sent, the sub-parameters of +MS are updated to reflect the values of Nn and S37 (see descriptions of the +MS command and of the S37 register).

For example: z N1S37=10 updates the sub-parameters of the +MS command as follows: z

+MS=10,1,300,12000

N037=10 updates the sub-parameters of the +MS command as follows:

+MS=10,0,12000,12000

2.

It is recommended to use the +MS command rather than the Nn and S37=x commands. The Nn and S37=x commands are supported to ensure compatibility with the existing communication software.

35013154.02 07/2008

149

Appendices

On- Return to on-line data mode

Introduction

Parameters

This command determines the way in which the modem sets in on-line data mode.

If the modem is in the on-line command mode, this command sets it in on-line data mode with or without a resynchronization attempt.

If the modem is in off-line command mode (no connection), ERROR is displayed as the response.

The parameters are:

Code

O0

O1

Description

Switches to on-line data mode without resynchronization attempt. The processing is determined by the call establishment task. In general, if there is a connection, this command reconnects the DTE to the remote modem after an escape (+++).

In STN mode only; switches to on-line data mode after a resynchronization attempt.

Result codes The following table lists the possible command responses.

Code Description

CONNECT n = 0 to 3.

ERROR If n is not in the range 0 to 3.

150

35013154.02 07/2008

Appendices

P - Default adjustment of pulse dialing

Introduction

Result codes

This command imposes pulse dialing until the receives the next 'T' dialing modifier or the next 'T' command. It sets bit 5 of S14. On execution of a dialing command which expressly indicates the dialing mode of the call in question (e.g. ATDT…), this command is canceled so that all subsequent dialing will be tone dialing (see 'T' command).

In certain countries, this command may not be authorized.

The following table lists the possible command responses.

Code

OK

Description

-

35013154.02 07/2008

151

Appendices

Qn - Activation / deactivation of result codes

Introduction

Parameters

According to the parameter indicated, the command activates or deactivates sending of result codes to the DTE. The parameter value, if valid, is written in S14.

The parameters are:

Code

Q0

Q1

Description

Sends the result codes to the DTE (default value).

Does not send result codes to the DTE.

Result codes The following table lists the possible command responses.

Code

OK

ERROR

Description n = 0 to 1.

If n is not in the range 0 to 1.

152

35013154.02 07/2008

Appendices

Sn - S register read / write

Introduction

Parameters

The modem selects an S register, performs a read or write operation on an S register or reports the value of an S register.

The parameters are:

Code n n = v n?

Description

Sets the S register as the default register.

Attributes the value v to the S register n.

Indicates the value of the register S n. The n parameter can be omitted, in which case it is the value of S0 which is read. S can be omitted, in which case it is the value of the last consulted S register (default register) which is read.

Examples

Result codes z z z z

ATS7 sets S7 as the default register.

ATS38 sets S38 as the default register.

AT=40 gives the default register the value of 40.

ATS=20 gives the value 20 to S0.

If the number n is outside the range of available S registers, the modem sends back an ERROR message. The value 'v' is rollover 256. If the result is outside the permitted range for a given S register, the values are still stored but from a functional point of view, it is the upper and lower limits which are used.

The input and output values are always in decimal format. Note that some S registers are read-only. In these cases, a write operation to an S register appears to be accepted but the value is in fact not written.

35013154.02 07/2008

153

Appendices

T - Default adjustment of tone dialing

Introduction

Result codes

This command imposes MFDT dialing until the next 'P' dialing modifier or the next

'P' command is received. The modem sets an S register bit to '1' to indicate that all subsequent dialing will be tone dialing. Note that the DP command has priority over this command. It clears bit 5 of S14. In certain countries, this command may not be used (see P command).

The following table lists the possible command responses.

Code

OK

Description

-

154

35013154.02 07/2008

Appendices

Vn - Form of the result codes

Introduction

Parameters

This command chooses to send the result codes to the DTE in abbreviated form or in complete form. The parameter value, if valid, is written in bit 3 of S14.

The parameters are:

Code

V0

V1

Description

Presents the result codes in abbreviated form (numerical). There is no line change before the result code given in abbreviated form.

Presents the result codes in complete form (text) (default value).

Result codes The following table lists the possible command responses.

Code

OK

ERROR

Description n = 0 to 1.

If n is not in the range 0 to 1.

35013154.02 07/2008

155

Appendices

Wn - Error correction messages control

Introduction

Parameters

This command controls the format of CONNECT messages. The parameter value, if valid, is written in bits 2 and 3 of S31 (also see description of S95).

The parameters are:

Code

W0

W1

W2

Description

On connection, the modem only indicates the baud rate of the DTE (e.g.

CONNECT 9600). Subsequent responses are deactivated (default value).

On connection, the modem indicates the line baud rate, the error correction protocol and the baud rate of the DTE respectively. Subsequent responses are deactivated.

On connection, the modem indicates the baud rate of the DCE (e.g. CONNECT

2400). Subsequent responses are deactivated.

Result codes The following table lists the possible command responses.

Code

OK

ERROR

Description n = 0 to 2.

If n is not in the range 0 to 2.

156

35013154.02 07/2008

Appendices

Xn - Extended result codes

Introduction

Parameters

35013154.02 07/2008

This command selects the set of messages that the modem will use to inform the

DTE of the command results. The table indicates the messages which are activated for each value of X.

If the modem is in fax mode (+FCLASS=1 or 2), the only message sent to indicate that a connection has been made is CONNECT without any indication of baud rate.

The parameters are:

Code

X0

X1

X2

X3

X4

Description

Deactivates detection of engaged tones except if this is imposed by the national requirements; only sends the result codes OK , CONNECT , RING , NO CARRIER ,

ERROR and NO ANSWER .The blind dialing mode is activated/deactivated by the national parameters. If detection of the engaged tone is in use and if such a tone is detected, it is the response NO CARRIER which is sent back instead of BUSY .If dial tone detection is in use or selected and if no such tone is detected, it is the response NO CARRIER which is sent back instead of NO DIAL TONE .The binary value 000 is written in bits 6, 5 and 4 of S22 respectively.

Deactivates detection of engaged tones except if this is imposed by the national requirments; only sends the result codes OK , CONNECT , RING , NO CARRIER , ER-

ROR , NO ANSWER and CONNECT XXXX (XXXX = baud rate). Blind dialing mode is activated/deactivated by the national parameters. If detection of the engaged tone is in use and if such a tone is detected, it is the response NO CARRIER which is sent back instead of BUSY .If dial tone detection is in use or selected and if no such tone is detected, it is the response NO CARRIER which is sent back instead of NO

DIAL TONE .The binary value 100 is written in bits 6, 5 and 4 of S22 respectively.

Deactivates detection of engaged tones except if this is imposed by national requirements; only sends the result codes OK , CONNECT , RING , NO CARRIER , ER-

ROR , NO DIAL TONE , NO ANSWER and CONNECT XXXX .If detection of the engaged tone is in use and if such a tone is detected, it is the response NO CAR-

RIER which is sent back instead of BUSY .If dial tone detection is in use or selected and if no such tone is detected, it is the response NO CARRIER which is sent back instead of NO DIAL TONE .The binary value 101 is written in bits 6, 5 and

4 of S22 respectively.

Activates detection of engaged tones; only sends the result codes OK , CONNECT ,

RING , NO CARRIER , ERROR , NO DIAL TONE , NO ANSWER et CONNECT

XXXX .Blind dialing mode is activated/deactivated by the national parameters.If dial tone detection is in use and if no such tone is detected, it is the reply NO

CARRIER which is sent instead of NO DIAL TONE .The binary value 110 is written in bits 6, 5 and 4 of S22 respectively.

Activates detection of engaged tones; sends all messages. The binary value 111 is written in bits 6, 5 and 4 of S22 (default value) respectively.

157

Appendices

Result codes The following table lists the possible command responses.

Code

OK

ERROR

Description n = 0 to 4.

If n is not in the range 0 to 4.

Table of result codes

The n value

17

18

19

20

22

14

15

16

23

24

32

33

35

40

8

9

10

11

12

13

2

3

4

5

6

7

0

1

Abbreviated form

Complete form n = 0

OK

CONNECT

RING

NO CARRIER

ERROR

CONNECT 1200

NO DIAL TONE

BUSY

NO ANSWER

CONNECT 0600

CONNECT 2400

CONNECT 4800

CONNECT 9600

CONNECT 7200

CONNECT 12000

CONNECT 14400

CONNECT 19200

CONNECT 38400

CONNECT 57600

CONNECT 115200

CONNECT 230400

1

X

CONNECT 75RTX / 1200RX 1

1

1

1

1

1

CONNECT 1200TX / 75RX

DELAYED

BLACKLISTED

FAX

DATA

CARRIER 300

1

4

4

X

X

X

X

1

1

1

1

1

X

X

X

X

X

1

3

3 n = 2

X

X

X

X

X

X

X

X

X

4

4

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

3 n = 1

X

X

X

X

X

X

X

X

X

4

4

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

3

3 n = 3

X

X

X

X

X

X

X

X

X

4

4

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

Note

-

-

-

-

-

-

-

-

-

-

-

-

Note 4

-

-

-

-

-

-

-

-

-

-

-

-

-

-

n = 4

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

158

35013154.02 07/2008

Appendices

91

150

151

152

153

154

77

78

79

80

81

84

63

64

66

67

69

70

56

57

58

59

61

62

50

51

52

53

54

55

47

48

49

Abbreviated form

44

45

46

Complete form n = 0

CARRIER 1200 / 75

CARRIER 75 / 1200

CARRIER 1200

CARRIER 2400

CARRIER 4800

CARRIER 7200

CARRIER 9600

CARRIER 12000

CARRIER 14400

CARRIER 16800

CARRIER 19200

CARRIER 21600

CARRIER 24000

CARRIER 26400

CARRIER 28800

CONNECT 16800

CONNECT 21600

CONNECT 24000

CONNECT 26400

CONNECT 28800

COMPRESSION: CLASS 5

COMPRESSION: V.24 bis

COMPRESSION: NONE

PROTOCOL: NONE

PROTOCOL: LAPM

CARRIER 31200

CARRIER 33600

PROTOCOL: ALT X

PROTOCOL: ALT-CELLULAR X

CONNECT 33600 1

X

X

X

1

1

X

X

X

X

X

X

X

1

1

1

CONNECT 31200

CARRIER 32000

CARRIER 34000

CARRIER 36000

CARRIER 38000

CARRIER 40000

1

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X n = 1

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X n = 3

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X n = 2

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

Note

Note 2

Note 2

Note 2

Note 2

Note 2

Note 2

-

-

-

Note 2

Note 2

-

-

-

-

-

-

-

-

-

-

Note 2

Note 2

Note 2

-

Note 3

Note 3

-

-

Note 3

Note 3

Note 4

Note 4

Note 4

Note 4

Note 4 n = 4

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

35013154.02 07/2008

159

Appendices

169

170

171

172

173

174

175

176

177

+ F4

161

162

165

166

167

168

Abbreviated form

155

156

157

158

159

160

Complete form

CARRIER 42000

CARRIER 44000

CARRIER 46000

CARRIER 48000

CARRIER 50000

CARRIER 52000

CARRIER 54000

CARRIER 56000

CONNECT 32000

CONNECT 34000

CONNECT 36000

CONNECT 38000

CONNECT 40000

CONNECT 42000

CONNECT 44000

CONNECT 46000

CONNECT 48000

CONNECT 50000

CONNECT 52000

CONNECT 54000

CONNECT 56000

+FCERROR n = 0

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X n = 1

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X n = 2

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X n = 3

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

2

3

4

Observations

1 An ‘X’ in the column means that the message in question (in its text form or only numerical) is generated when the corresponding value ‘n’ (indicated at the top of column) has been selected with the ATXn command. If the column is blank, no message is generated for this table slot. A number sends back a less explicit message (in complete or abbreviated form) which will be sent to the table slot in question.

RC288 modems and higher.

RC336 modems and higher.

RC56 modems.

n = 4

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

Note

Note 4

Note 4

Note 4

Note 4

Note 4

Note 4

Note 4

Note 4

Note 4

Note 4

Note 4

Note 4

Note 4

Note 4

Note 4

Note 4

Note 4

Note 4

Note 4

Note 4

Note 4

-

160

35013154.02 07/2008

Appendices

Yn - Disconnection after prolonged inactivity

Introduction

Parameters

This command activates/deactivates generation and response to a disconnection after prolonged inactivity. The parameter value, if valid, is written in bit 7 of S21.

The parameters are:

Code

Y0

Y1

Description

Deactivates disconnection after prolonged inactivity.

Activates disconnection after prolonged inactivity. In error correction mode, the modem sends an inactivity signal of four seconds before hanging up. In the same mode, the modem responds to the receipt of a prolonged inactivity signal

(for example a 'break' signal of more than 1.6 seconds) by hanging up.

Result codes The following table lists the possible command responses.

Code

OK

ERROR

Description n = 0 to 1.

If n is not in the range 0 to 1.

35013154.02 07/2008

161

Appendices

Zn - Software reset of modem and restoration of profile

Introduction

Parameters

The modem executes a software reset and reestablishes the configuration profile defined by the parameter.

In the absence of a parameter, zero is assumed.

The parameters are:

Code

Z0

Z1

Description

Software reset of modem and reestablishment of stored profile 0.

Software reset of modem and reestablishment of stored profile 1.

Result codes The following table lists the possible command responses.

Code

OK

ERROR

Description n = 0 to 1.

If n is not in the range 0 to 1.

162

35013154.02 07/2008

Appendices

&Cn - RLSD Option (detection of DCD carrier)

Introduction

Parameters

The modem monitors the carrier detection output according to the parameter entered. The parameter value, if valid, is written in bit 5 of S21.

The parameters are:

Code

&C0

&C1

Description

Carrier detection is active all the time (default value).

Carrier detection depends on the carrier status.

Result codes The following table lists the possible command responses.

Code

OK

ERROR

Description n = 0 to 1.

If n is not in the range 0 to 1.

35013154.02 07/2008

163

Appendices

&Dn - DTR Option (Data Terminal Ready)

Introduction

Parameters

This command interprets loss of the DTR signal sent by the DTE, according to the parameter entered. The parameter value, if valid, is written in bits 3 and 4 of S21.

The parameters are:

Code

&D0

&D1

&D2

&D3

Description

Loss of the DTR signal is interpreted as follows according to the &Q value in progress (default value): z &Q0,&Q5, &Q6: ignores the DTR signal (assumed activated) and enables operation with DTEs which do not support DTR signals.

z &Q1, &Q4: loss of the DTR signal causes the modem to hang up. There is no repercussion on automatic answer.

z &Q2, &Q3: loss of the DTR signal causes the modem to hang up. Automatic answer is inhibited.

Loss of the DTR signal is interpreted as follows according to the &Q value in progress: z &Q0, &Q1, &Q4, &Q5, &Q6: loss of the DTR signal is interpreted by the modem as though the synchronous escape sequence had been entered.

The modem returns to asynchronous command mode without z disconnection.

&Q2, &Q3: loss of the DTR signal causes the modem to hang up. Automatic answer is inhibited.

Loss of the DTR signal is interpreted as follows according to the &Q value in progress: z &Q0 to &Q6: loss of the DTR signal causes the modem to hang up.

Automatic answer is inhibited.

Loss of the DTR signal is interpreted as follows according to the &Q value in progress: z &Q0, &Q1, &Q4, &Q5, &Q6: loss of the DTR signal causes the modem to reset the software as though it had received the Z command. The value of z

&Y defines the profile which is loaded.

&Q2, &Q3: loss of the DTR signal causes the modem to hang up. Automatic answer is inhibited.

Note: If &Q5, &Q6, +FCLASS=1 is in use, the result is identical to the &Q0 command.

164

35013154.02 07/2008

Appendices

&Fn - Restoration of the factory configuration (profile)

Introduction

Parameters

The modem loads the defined factory default configuration according to the parameter entered. The default Rockwell values corresponding to the 0 (&F0) profile are used for each command and in the S register descriptions. Two profiles are available. A configuration profile is made up of a sub-set of S registers.

The parameters are:

Code

&F0

&F1

Description

Reestablishes the factory profile 0 (default value).

Reestablishes the factory profile 1.

35013154.02 07/2008

165

Appendices

&Gn - Selection of guard tone

Introduction

Parameters

The modem generates the guard tone selected by this command according to the parameter entered (differential phase shift modulation modes only). The parameter value, if valid, is written in bits 6 and 7 of S23.

The parameters are:

Code

&G0

&G1

&G2

Description

Deactivates the guard tone (default value for US models).

Deactivates the guard tone.

Selects a guard tone of 1800 Hz (default value for W-class models).

Result codes

Note: In certain countries, this command may not be authorized.

The following table lists the possible command responses.

Code

OK

ERROR

Description n = 0 to 2.

If n is not in the range 0 to 2.

166

35013154.02 07/2008

Appendices

&Kn – Flow control

Introduction

Parameters

This command defines the DTE/DCE (terminal/modem) flow control mechanism.

The parameter value, if valid, is written in bits 0, 1 and 2 of S39.

The parameters are:

Code

&K0

&K3

&K4

&K5

&K6

Description

Deactivates flow control.

Activates RTS/CTS flow control - hardware flow control (default value for data modem modes).

Activates XON/XOFF flow control – software flow control.

Activates transparent XON/XOFF flow control.

Activates RTS/CTS flow control and XON/XOFF flow control at the same time

(default value for fax-modem modes).

Result codes The following table lists the possible command responses.

Code

OK

ERROR

Description n = 0, 3 to 6.

If n is not equal to 0 or 3 to 6.

35013154.02 07/2008

167

Appendices

&Pn - Selection of pulse dialing close/open report

Introduction

Parameters

This command determines the close/open report used during pulse dialing. It only has an effect if the appropriate bit activating this command is set by the program

ConfigurACE.

If the command is activated, it has priority over the close/open reports defined by the

OEM parameters in ConfigurACE. The default value depends on the country. The parameter value, if valid, is written in bits 3 and 4 of S28.

The parameters are:

Code

&P0

&P1

&P2

&P3

Description

Selection of 39%-61% as close/open report at 10 pulses per second

(default value).

Selection of 33%-67% as close/open report at 10 pulses per second.

Selection of 39%-61% as close/open report at 20 pulses per second.

Selection of 33%-67% as close/open report at 20 pulses per second.

Result codes The following table lists the possible command responses.

Code

OK

ERROR

Description n = 0 to 3.

If n is not in the range 0 to 3.

168

35013154.02 07/2008

Appendices

&Qn - Synchronous/asynchronous mode

Introduction

Parameters

This command monitors the authorized connection modes. It is used in association with S36 and S48 (see also command \N).

The parameters are:

Code

&Q0

&Q1

&Q2

&Q4

&Q5

&Q6

Description

Selects direct asynchronous mode.

Selects

Selects

Selects automatic synchronous mode. The binary value 100 is written in bits 3,

1 and 0 of S27 respectively.

The modem attempts to establish a link with error correction. The mode can be configured with S36 to determine if, in case of failure, the modem hangs up or if it falls back to an asynchronous connection. The binary value 101 is written in bits 3, 1 and 0 of S27 (default value) respectively.

Selects normal asynchronous mode (with baud rate buffer). The binary value

110 is written in bits 3, 1 and 0 of S27 respectively.

Result codes The following table lists the possible command responses.

Code

OK

ERROR

Description n = 0, 1, 2, ,4, 5, 6.

If n is not equal to 0, 1, 2, 4, 5, or 6.

35013154.02 07/2008

169

Appendices

&Rn - RTS/CTS option

Introduction

Parameters

This command selects the mode for monitoring of the ready to send signal (Clear to

Send - CTS) by the modem. The operation of the CTS signal is modified if hardware flow control is selected (see command &K).

The parameters are:

Code

&R0

&R1

Description

In synchronous mode, the CTS signal follows the RTS status (request to send); the RTS-CTS delay is defined by S26. In asynchronous mode, CTS operates according to V.25 handshaking.

In synchronous mode, CTS is always active (the RTS transitions are ignored).

In asynchronous mode, CTS does not become inactive unless it is imposed by flow control (default value).

Result codes The following table lists the possible command responses.

Code

OK

ERROR

Description n = 0 to 1.

If n is not in the range 0 to 1.

170

35013154.02 07/2008

Appendices

&Sn - DSR Monitoring (Data Station Ready)

Introduction

Parameters

This command selects the way in which the modem monitors the DSR signal (Data

Station Ready). The parameter value, if valid, is written in bit 6 of S21.

The parameters are:

Code

&S0

&S1

Description

The DSR signal is always active (default value).

The DSR signal becomes active after the detection of an answer tone and inactive after the loss of the carrier.

Result codes The following table lists the possible command responses.

Code

OK

ERROR

Description n = 0 to 1.

If n is not in the range 0 to 1.

35013154.02 07/2008

171

Appendices

&V - Display of current configuration and stored profiles

Introduction

Result codes

This command gives the current configuration (active), the profiles (defined by the user) and the first four stored telephone numbers.

The profiles and the stored telephone numbers are not displayed if the NVRAM memory is not installed or if it is detected as being non operational by the NVRAM test during the reset process.

The following table lists the possible command responses.

Code

OK

Description

-

Example The example

AT&V

ACTIVE PROFILE :

B0 E1 L1 M1 N1 QO T V1 W0 X4 Y0 &C0 &D0 &G2 &J0 &K3 &Q5 &R1

&S0 &T4 &X0 &Y0

S00:002 S01:000 S02:043 S03:013 S04:010 S05:008 S06:002

S07:030 S08:002 S09:006S10:014 S11:255 S12:050 S18:000 S25:005

S26:001 S36:007 S37:000 S38:020 S46:138

S48:007 S95:000

PROFILE 0 STORED :

B0 E1 L1 M1 N1 QO T V1 W0 X4 Y0 &C0 &D0 &G2 &J0 &K3 &Q5 &R1

&S0 &T4 &X0

S00:002 S02:043 S06:002 S07:030 S08:002 S09:006 S10:014

S11:095 S12:050 S18:000

S36:007 S37:000 S40:105 S41:003 S46:138 S95:000

PROFILE 1 STORED :

B0 E1 L1 M1 N1 QO T V1 W0 X4 Y0 &C0 &D0 &G2 &J0 &K3 &Q5 &R1

&S0 &T4 &X0

S00:002 S02:043 S06:002 S07:030 S08:002 S09:006 S10:014

S11:095 S12:050 S18:000

S36:007 S37:000 S40:105 S41:003 S46:138 S95:000

TELEPHONE NUMBERS :

0 = 1 =

2 = 3 =

OK

172

35013154.02 07/2008

Appendices

&Wn – Storage of the current configuration

Introduction

Parameters

Saves the current configuration (active profile), including the S registers, in one of the two user profiles in NVRAM memory, according to the value of the parameter.

This command will result in an ERROR response if the NVRAM memory is not installed or if it is detected as being non operational by the test.

The current configuration is made up of a list of storable parameters, as illustrated by the &V command. These values are reassigned to the active configuration on receipt of a Zn command or on power-up (see &Yn command).

The parameters are:

Code

&W0

&W1

Description

Stores the active configuration as profile 0.

Stores the active configuration as profile 1.

Result codes The following table lists the possible command responses.

Code

OK

ERROR

Description n = 0 to 1.

If n is not in the range 0 to 1.

35013154.02 07/2008

173

Appendices

&Yn - Designation of a default profile on reset

Introduction

Parameters

Selects the user profile to be loaded after a hardware reset.

The parameters are:

Code

&Y0

&Y1

Description

The modem uses profile 0.

The modem uses profile 1.

Result codes The following table lists the possible command responses.

Code

OK

ERROR

Description n = 0 to 1.

If n is not in the range 0 to 1.

174

35013154.02 07/2008

Appendices

&Zn – Storage of telephone numbers

Introduction

Parameters

The modem can store a maximum of 20 telephone numbers. Each telephone number can be up to 45 digits.

The parameters are:

Code Description

&Zn = x n = 0 to 19 (W-class) and x = number string (needs 2048 bytes of NVRAM).

Result codes The following table lists the possible command responses.

Code

OK

ERROR

Description n = 0 to 19 and x less than or equal to 45 digits.

If n is greater than 19 or x greater than 45 digits.

35013154.02 07/2008

175

Appendices

%Cn - Activation / deactivation of data compression

Introduction

Parameters

Activates / deactivates data compression The parameter value, if valid, is written in bits 0 and 1 of S41.

The parameters are:

Code

%C0

%C1

%E2

%E3

Description

Deactivates data compression.

Activates MNP 5 data compression.

Activates V.42 bis data compression.

Activates V.42 bis and MNP 5 data compression.

Result codes The following table lists the possible command responses.

Code

OK

ERROR

Description n = 0 to 3.

If n is not in the range 0 to 3.

176

35013154.02 07/2008

Appendices

%En - Activation/deactivation of line quality monitoring or automatic resynchronization or fallback/increase of transfer rate

Introduction

Parameters

Determines whether or not the modem automatically monitors the line quality and requests resynchronization (%E1) or a fallback when the line quality is insufficient or an increase in the transfer rate when the line quality is sufficient (%E2). This only applies to switched lines. The parameter value, if valid, is written in bits 2 and 6 of

S41.

The resynchronization attempt, if it is activated, lasts a maximum of 30 seconds.

The parameters are:

Code

%E0

%E1

%E2

Description

Deactivates line quality monitoring and automatic resynchronization attempt

(default value).

Activates line quality monitoring and automatic resynchronization attempt.

Activates line quality monitoring and transfer rate fallback/increase.

Result codes The following table lists the possible command responses.

Code

OK

ERROR

Description n = 0 to 2.

If n is not in the range 0 to 2.

35013154.02 07/2008

177

Appendices

%L - Level of line signal

Introduction

Result codes

Sends back a value which indicates the level of signal received. The returned value is a direct indication of the level of reception at the modem data pumping device, and not at the telephone line connector.

For example, 009 = -9 dBm, 043 = -43 dBm, and so on.

The following table lists the possible command responses.

Code

OK

Description n = 0 to 1.

178

35013154.02 07/2008

Appendices

%Q - Quality of line signal

Introduction

Result codes

Indicates the line quality (DAA function, network access connector). Sends back most significant byte of EQM value. Depending on the EQM value, there can be a resynchronization attempt or a fallback/increase of transfer rate, triggered by &E1 or

%E23.

The following table lists the possible command responses.

Code

OK

ERROR

Description

If connected.

If not connected or connected at 300 b/s, in V.23 or in fax mode.

Example AT&Q

015

35013154.02 07/2008

179

Appendices

\Kn - BREAK control

Introduction

Parameters of case 1

According to the parameter entered, controls the modem response to a break signal received from the DTE, from the remote modem or from the \B command. The value of the parameter, if valid, is written in bits 3, 4 and 5 of S40. The response is different according to the case.

Code

\K0

\K1

\K2

\K3

\K4

\K5

The first case is that of the modem which receives a break from the DTE when it is in data transfer mode:

Description

Switches to on-line command mode, no break sent to the remote modem.

Empties the data buffers and sends a break to the remote modem.

As \K0.

Immediately sends a break to the remote modem.

As \K0.

Sends a break to the remote modem in sequence with the transmitted data

(default value).

Parameters of case 2

Code

\K0

\K1

\K2

\K3

\K4

\K5

The second case is that of the modem which is in on-line command mode (awaiting

AT commands) during a connection, and which receives a \B command for it to send a break to the remote modem:

Description

Empties the data buffers and sends a break to the remote modem.

Empties the data buffers and sends a break to the remote modem.

Immediately sends a break to the remote modem.

Immediately sends a break to the remote modem.

Sends a break to the remote modem in sequence with the data.

Sends a break to the remote modem in sequence with the data.

180

35013154.02 07/2008

Parameters of case 3

Appendices

Code

\K0

\K1

\K2

\K3

\K4

\K5

The third case is that of the modem which receives a break from the remote modem during a connection without error correction:

Description

Empties the data buffers and sends a break to the DTE.

Empties the data buffers and sends a break to the DTE.

Immediately sends a break to the DTE.

Immediately sends a break to the DTE.

Sends a break to the DTE in sequence with the received data.

Sends a break to the DTE in sequence with the received data (default value).

Result codes The following table lists the possible command responses.

Code

OK

ERROR

Description n = 0 to 5.

If n is not in the range 0 to 5.

35013154.02 07/2008

181

Appendices

\Nn - Operating mode

Introduction

Parameters

This command defines the preferred error correction mode to negotiate during a subsequent connection. It is assigned by the configuration of the OEM firmware.

The parameters are:

Code

\N0

\N1

\N2

\N3

\N4

\N5

Description

Selects normal mode with baud rate buffer (without error correction mode)

(equivalent to &Q6).

Serial interface selected – selects direct mode and is equivalent to the operating mode (equivalent to &Q0). Parallel interface selected – as \N0.

Select reliable mode (with error correction). The modem attempts first to establish an LAPM correction then an MNP connection. If it fails, the modem hangs up (equivalent to &Q5, S36=4 and S48=7).

Selects automatic reliable mode. This mode is identical to \N2 mode apart from the fact that if the modem does not manage to establish a reliable connection, it falls back to normal mode (equivalent to &Q5, S36=7 and S48=7).

Selects LAPM error correction mode. If it fails, the modem hangs up

(equivalent to &Q5, and S48=0).

Selects MNP error correction mode. If it fails, the modem hangs up (equivalent to &Q5, S36=4 et S48=128).

Result codes The following table lists the possible command responses.

Code

OK

ERROR

Description n = 0 to 5.

If n is not in the range 0 to 5.

182

35013154.02 07/2008

Appendices

Values of the registers of the TSX MDM 10 card in a PLC

Introduction

Registers

The default values of the TSX MDM 10 card are stored in ROM memory and loaded during power-up or by the ATZn command.

S26

S36

S37

S38

S46

S48

S95

S09

S10

S11

S12

S18

S25

The default values are shown in the following table:

S03

S04

S05

S06

Register

S00

S01

S02

S07

S08

Function

Rings to auto-answer

Ring counter

Escape character

Carriage Return character

Line Feed Character

Backspace character

Wait time for dial tone

Wait time for carrier

Pause time for dial delay modifier

Carrier detect response time 006

Carrier loss disconnect time 014

DTMF tone duration 070

Escape code guard time

Test timer

Delay to DTR off

050

000

005

013

010

008

005

Values

000

000

043

050

002

RTS to CTS delay

LAPM failure control

Line connection speed

000

007

000

Delay before forced hangup 020

Data compression control 136

V.42 negotiation control

Result code messages control

007

000

35013154.02 07/2008

183

Appendices

184

35013154.02 07/2008

Communication via Modbus Plus

III

Introduction

Subject of this part

What's in this

Part?

This part introduces the principles of configuring and communicating with Modbus

Plus via PL7 software.

This part contains the following chapters:

Chapter

12

13

14

15

16

17

Chapter Name

General

Peer Cop service

Configuring Modbus Plus communication

Programming Modbus Plus communication

Debugging Modbus Plus communication

Language objects associated with Modbus Plus communication

Page

187

195

199

207

219

223

185

35013154.02 07/2008

Communication via Modbus Plus

186

35013154.02 07/2008

General

12

Introduction

Aim of this

Chapter

What's in this

Chapter?

This Chapter introduces Modbus Plus communication and its services.

This chapter contains the following topics:

Topic

Introduction

Compatibility

Integration into an X-WAY architecture

Integration into a Modbus Plus architecture

Page

188

189

190

193

35013154.02 07/2008

187

Modus Plus communication: General

Introduction

Introduction Modbus Plus communication is used to exchange data between all devices connected by the bus.

The Modbus Plus protocol is based on the principle of a logical token bus (Logical

Token passing). Each station of one network is identified by an address between 1 and 64 and each station accesses the network after reception of a token. Duplicated addresses are not valid.

Network example

Modbus Plus

2 12

Premium Quantum

Token bus (logic ring)

Associated manuals

A Modbus Plus communication channel comprises three main functions: z point to point data exchanges via the messaging service, using the Modbus z protocol, broadcast exchanges of global data between all the stations participating in this z exchange, multidrop exchanges of specific data via the Peer Cop services.

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

Title

Modbus Plus Network - Installation and planning manual

Micro PLCs - Installation manual

Premium TSX PLCs - Installation manual

Description

Detailed description of the set-up procedure for the Modbus Plus network

Hardware installation

Hardware installation

188

35013154.02 07/2008

Modus Plus communication: General

Compatibility

Hardware

Software z z

This type of communication is available for PLCs of at least version V3.0:

Premium via the intermediary of the TSX MBP100 PCMCIA card,

Micro accepting the PCMCIA card described below.

Note: This type of communication is not available with TSX SCY 21601 modules.

Premium and Micro PLCs do not support redundancy with the TSX MBP 100 card.

The PCMCIA TSX MBP 100 card can process 4 communication functions at the same time.

The maximum size of the number of objects per communication function is 125 useful data words (maximum frame of 256 bytes).

In the event of communication of a Premium and Micro PLC with a Quantum PLC, it is necessary to shift addressing. To access a Quantum object with address n, the communication function on the Premium side must have the address n-1.

The Peer Cop service is only supported by Premium PLCs.

During configuration of inputs and outputs for the Peer Cop service, it is possible to allocate up to 32 internal words to each connection point in the local bus. The total number of words must not exceed 500 internal words.

35013154.02 07/2008

189

Modus Plus communication: General

Integration into an X-WAY architecture

Introduction A Modbus Plus segment can be integrated into an X-WAY network architecture.

Communications between stations on the different networks are possible under certain conditions of use.

Communication to a Modbus Plus network

A client application connected to a FIPWAY or ETHERNET TCP/IP network can communicate with a Modbus Plus station via the Modbus protocol.

In this case, you must indicate the X-WAY network address of the Premium PLC which is connected on the Modbus Plus segment as well as on the FIPWAY network, and the number of the destination Modbus Plus station.

The syntax is as follows:

{network number, station number} 0.1. Modbus Plus station number

190

35013154.02 07/2008

Example

Modus Plus communication: General

In this example, the FIPWAY station {5.3} has a Modbus Plus connection and therefore, any remote FIPWAY station which wishes to communicate with a Modbus

Plus station (for example station 5) must use this address.

READ_VAR(ADR#{5.3}0.1.5, '%MW', 100, 10,%MW200:10, %MW300:4)

Configuration example

READ_VAR(ADR#{5.3}0.1.5, '%MW', 100,

10,%MW200:10, %MW300:4)

Premium

3

FIPWAY #5

Quantum

8

Modbus Plus

Quantum

5

Note: Routing between FIPWAY and Modbus Plus is carried out by the automatic system. In a network architecture, it is not necessary to declare a bridge station.

Communication from a Modbus

Plus network

If a Modbus Plus segment is integrated into an X-WAY architecture, a Quantum station cannot communicate with stations connected to another network in this architecture (for example FIPWAY or ETHERNET TCP/IP). Communication is only possible with the local Premium.

35013154.02 07/2008

191

Modus Plus communication: General

Example The Quantum PLC sends a write request to modify 5 words in the PL7 application

(%MW10, .etc.), but it does not have access to the other stations on Fipway.

Premium

3

FIPWAY #5

Quantum

5 Modbus Plus

MBP-MSTR write

5

10

RP=5.0.0.0.0

192

35013154.02 07/2008

Modus Plus communication: General

Integration into a Modbus Plus architecture

Introduction

Premium to

Quantum

Quantum to

Premium

In a Modbus Plus architecture, a Quantum PLC application can communicate with a Premium PLC and vice versa.

Communication from a Premium PLC to a remote station is described in the exchange service on remote networks.

Communication from a Quantum PLC to a Premium PLC is available via MSTR blocks.

In this case, the Premium or Micro are servers; therefore, all Modbus Plus stations connected to a network architecture, up to a maximum of 5 levels, can communicate with them.

Example

1

Premium

2

Quantum

3 Modbus Plus

35013154.02 07/2008

Bridge Plus

Modbus Plus

5

Bridge Plus

8 Modbus Plus

Quantum

4

Quantum

MSTR read

The Quantum station sends a read request to the Premium station using an address path: 8.5.1.0.0 (routing path).

The MSTR function block is used to read or write internal words of a Premium or

Micro station. The parameter of the slave register of the MSTR function block directly indicates the address of the internal word %MW of the PL7 application. This function block is also used to read or reset the statistics counters of a Premium or

Micro station. This request is executed directly by the PCMCIA card which responds directly.

193

Modus Plus communication: General

194

35013154.02 07/2008

Peer Cop service

13

Peer Cop Service

Introduction The Peer Cop service is an automatic exchange mechanism between stations connected to the same local Modbus Plus segment.

This service is used to maintain constant control over inputs / outputs which have been remoted by implicit exchanges.

The Premium PLCs support two types of Peer Cop transfer: z z specific inputs specific outputs

Specific Inputs and Outputs

Report

The specific inputs and outputs are point to point services which use the multicast protocol (multistations). Each message contains one or several destination addresses for sending the data. This function is used to exchange data to several stations without repetition.

Three types of report are associated with the specific inputs and outputs: z z z activity bit: provides information on the availability and validity of the status bits status bits (to the number of one bit per station): z ensure coherence between the number of specific inputs configured and the number of specific inputs received z indicate if the specific inputs have been received during the Timeout presence bits (to the number of one bit per station): indicate if the specific inputs have been refreshed

Note: the presence bits are only valid for the specific inputs.

195

35013154.02 07/2208

Communication Modbus Plus: Peer Cop service

Example for the

Inputs

The data blocks are copied in full from the PCMCIA card to the internal word space, reserved during configuration.

Max. 500 characters

In the following example, the address of the first internal word is %MW10.

Internal words PCMCIA card Modbus Plus network

%MW10

3 words from station 1

%MW13

32 words from station 5

%MW45

20 words from station 6

%MW65

12 words from station 8

%MW77

32 words from station 9 copy

Peer Cop data specific inputs

Station 1

Station 5

Station 6

Station 62

%MW150

3 words from station 62

Activity bit

%IW0.1.6

%IW0.1.7

...

%IW0.1.14

copy

Status bits

Presence bits

196

35013154.02 07/2208

Communication Modbus Plus: Peer Cop service

Example for the

Outputs

The data blocks are copied in full from the internal word space, reserved during configuration, to the PCMCIA card. The reports are copied from the PCMCIA card to the language objects.

In the following example, the address of the first internal word is %MW10.

PCMCIA card Modbus Plus network

Max. 500 characters

Internal words

%MW10

3 words from station 1

%MW13

32 words of station 5

%MW45

20 words of station 6

%MW65

12 words from station 8

%MW77

32 words from station 9 copy

Specific outputs

Peer Cop data

Station 1

Station 5

Station 6

Station 62

%MW150

3 words from station 62

%IW0.1.6

%IW0.1.7

...

%IW0.1.14

copy

Activity bit

Status bits

Station 1

Station 5

Station 6

Station 62

35013154.02 07/2208

197

Communication Modbus Plus: Peer Cop service

198

35013154.02 07/2208

Configuring Modbus Plus communication

14

Introduction

Subject of

Chapter

What's in this

Chapter?

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

This chapter contains the following topics:

Topic

How to access the Modbus Plus PCMCIA card parameters

Modbus Plus configuration screen

Functions accessible from Modbus Plus

Modbus Plus configuration parameters

Configuring the specific inputs and outputs

Page

200

201

202

203

204

199

35013154.02 07/2008

Modbus Plus configuration

How to access the Modbus Plus PCMCIA card parameters

Introduction

How to access the link

This operation describes how to access the configuration parameters of the Modbus

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

The following table shows the procedure for accessing the Modbus Plus link:

Step

1

2

Action

Access the communication channel configuration screen.

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

Example

CHANNEL 1:

CHANNEL 1

CHANNEL 1

(No PCMCIA submodule)

MAST

3 Select the PCMCIA card from the drop-down menu TSX MBP 100 MODBUS+

PCMCIA CARD :

Example

CHANNEL 1

CHANNEL 1 (No PCMCIA submodule)

(Link not configured)

TSX FPP 200 FIPWAY PCMCIA CARD

TSX FPP 10 FIPIO PCMCIA CARD

TSX FPP 100 MODBUS+ PCMCIA CARD

TSX MDM 10 MODEM PCMCIA CARD

FCS SCP 111 RS232 OPEN PCMCIA CARD

FCS SCP 114 RS485 OPEN PCMCIA CARD

200

35013154.02 07/2008

Modbus Plus configuration

Modbus Plus configuration screen

Introduction

Illustration

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

The screen dedicated to Modbus Plus communication looks like this:

TSX 57302 [RACK 0 POSITION 0]

Configuration

Designation: PROCESSOR TSX P 57302

1

CHANNEL 1:

CHANNEL 1

MODBUS+

TSX MBP 100 MODBUS+ PCMCIA CARD

MAST

2

Station number: : 1

Peer Cop

Value of Timeout:

Input fallback mode

Maintain

Reset to 0

500 (ms)

Specific Inputs

Specific outputs

Elements and functions

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

Address Zone

1 common

2 specific

Function

(See : PL7 Micro/Junior/Pro ; Communication applications ;

Volume 1) is used to select or complete the parameters of a Modbus Plus link.

z z

It is split into two types of information: station addressing, the parameters concerning the Peer Cop service.

35013154.02 07/2008

201

Modbus Plus configuration

Functions accessible from Modbus Plus

Introduction

Accessible functions

Depending on the chosen communication supports, some parameters cannot be modified. They appear grayed out.

The summary table below shows the various choices possible:

Functions

Station number

Peer Cop

Input fallback mode

Specific inputs

Specific outputs

TSX MPB 100

For processors of at least version V3.0

For processors of at least version V3.3

Accessible if the Peer Cop box is checked

Accessible if the Peer Cop box is checked

Accessible if the Peer Cop box is checked

202

35013154.02 07/2008

Modbus Plus configuration

Modbus Plus configuration parameters

Introduction

Addressing parameter

Peer Cop parameters

Once the communication channel has been configured, complete the parameters dedicated to the Modbus Plus link.

z z

They are split into two windows: the Station number window, the Peer Cop window,

The window looks like this:

Station number: : 1

This parameter is used to define the address (or connection point) of the station on the Modbus Plus network.

The window is only accessible by checking the box Peer Cop :

Peer Cop

Value of Timeout:

Input fallback mode

Maintain

Reset to 0

500 (ms)

Specific Inputs

Specific outputs

It can be used to: z complete the Timeout value : Input refresh time in milliseconds. It is used to specify the maximum time during which the inputs from remote stations must be updated in the PCMCIA card. In the event that data is not refreshed within the time allowed, an error is detected.

z the default value is 20 ms, z the values range from 20 ms to 2 s, z z z the increment is 20 ms.

define the Input Fallback mode : z maintained, z cleared.

access the values of the specific inputs and specific outputs . Peer Cop

service, p. 195

35013154.02 07/2008

203

Modbus Plus configuration

Configuring the specific inputs and outputs

Introduction

Configuration rules

Specific inputs

If you have checked the box Peer Cop , you must specify the start address and the size of the data to be exchanged.

These data are stored in the internal words of the application. Peer Cop service,

p. 195

The input words zone cannot be superimposed on the output words zone.

The internal words corresponding to the specific inputs or outputs are stored continuously.

The maximum size of the specific data must not exceed 1000 words (max. 500 words for the inputs and max. 500 words for the outputs).

After selection of the button Specific inputs , the following window will appear:

Peer Cop input

Station

8

9

6

7

10

3

4

1

2

5

Ref.

%MW10

%MW15

%MW24

%MW56

%MW84

%MW88

%MW104

%MW117

%MW149

Length (0..32)

5

9

32

28

4

16

13

32

19

Validate

Cancel

Address of 1st %MW

%MW 10 z z

For each connection point of the local bus segment, the user must define: the start address in the table of internal words (%MW),

The size of the exchanges from 0 to 32 words per station on the local bus segment.

204

35013154.02 07/2008

Station

8

9

6

7

10

3

4

1

2

5

Ref.

%MW100

%MW105

%MW111

%MW126

%MW158

%MW184

%MW187

%MW199

%MW220

Length (0..32)

5

6

15

32

26

3

12

21

1

Modbus Plus configuration

Specific outputs After selection of the button Specific outputs , the following window will appear:

Peer Cop outputs

Validate

Cancel

Address of 1st %MW

%MW 100 z z

For each connection point of the local bus segment, the user must define: the start address in the table of internal words (%MW),

The size of the exchanges from 0 to 32 words per station on the local bus segment.

35013154.02 07/2008

205

Modbus Plus configuration

206

35013154.02 07/2008

Programming Modbus Plus communication

15

Introduction

Subject of

Chapter

What's in this

Chapter?

This Chapter describes the Programming process during set-up of Modbus Plus communication.

This chapter contains the following topics:

Topic

Read and write service on local segment

Exchange service on remote Modbus Plus networks

Examples of Exchanges on Remote Networks

Diagnostic service

Global data exchange service

Page

208

210

212

215

217

207

35013154.02 07/2008

Modbus Plus programming

Read and write service on local segment

Introduction A Micro or Premium PLC can exchange data with stations connected to the local

Modbus Plus network.

Data exchanges The functions READ_VAR and WRITE_VAR are used to access remote stations on the same local segment, bits, internal words or input and output words in read / write mode.

These exchanges are explicit exchanges managed by the application.

The addressing from a Premium station will be for example: z in read mode z

READ_VAR (ADR#0.1.10, '%MW', 10, 20, %MW10:20, %MW100:4) in write mode

WRITE_VAR (ADR#0.1.10, '%MW', 10, 20, %MW10:20, %MW100:4)

The following table describes the different parameters of the function:

Parameter

ADR#0.1.10

'%MW'

10

20

%MW10:20

%MW100:4

Description z z z

Address of destination device for the message: processor slot: 0 or 1

PCMCIA channel: 1 destination station number: 10

Type of object to be read or written, for example: internal words

Address of first word to be read or written

Number of words to be read or written

For reading: content of response

For writing: value of words to be written

Activity bit, exchange report, length

208

35013154.02 07/2008

Modbus Plus programming

Correspondence of object type

The tables describe the correspondence of object types between the Premium and

Quantum PLCs.

The Premium PLC is the sender of the request and the Quantum PLC replies:

Type of PL7 object Responding Quantum object READ_VAR or WRITE_VAR function

'%MW'

'%M'

'%IW'

'%I' internal words internal bits input words input bits

4x... memory area

0x... memory area

3x... memory area

1x... memory area

The Quantum PLC is the sender via an MSTR function block and the Premium PLC replies:

MSTR function block

READ

WRITE

Responding Premium object

%MW

%MW

Example

1

The Premium PLC application writes 10 internal words in the Quantum PLC at address 2 and reads 5 input words in the Quantum PLC at address 5:

2 5

Quantum

WRITE_VAR(ADR#0.1.2, ‘%MW’, 10, 5, %MW100:5, %MW200:4)

READ_VAR(ADR#0.1.5, ‘%IW’, 5, 8, %MW100:5, %MW200:4)

The internal words to be written in station 2 are at address 10.

The internal words to be read in station 5 are at address 5.

Quantum

35013154.02 07/2008

209

Modbus Plus programming

Exchange service on remote Modbus Plus networks

Introduction

Access to a remote station.

A Micro or Premium PLC can exchange data with stations connected to other

Modbus Plus segments via BP85 Bridge Plus bridges.

To access a station connected to another network segment, it is necessary to indicate the full address path (routing path) in the information sent.

Beforehand, indicate, in the request, the address of the first destination connection point on the local bus.

Next, clarify, in the data to be sent, each address of the devices which will allow the passage of the exchanges to the destination station.

Data exchanges This type of exchange is accessible via the function SEND_REQ . To differentiate the reading and writing of data from a remote station, a request code is associated to the function SEND_REQ . These exchanges are explicit exchanges managed by the application.

The addressing from a Premium station will be for example: z in read mode

SEND_REQ (ADR#0.1.61, 16#36, %MW300:50, %MW450:150, z

%MW600:4) in write mode

SEND_REQ (ADR#0.1.61, 16#37, %MW300:50, %MW450:150,

%MW600:4)

The following table describes the different parameters of the function:

Parameters

ADR#0.1.61

16#36

16#37

%MW300:50

%MW450:150

%MW600:4

Description

Address of destination device for the message: z z z processor slot: 0 or 1

PCMCIA channel: 1 number of the destination connection point on the local bus:

61

Request code for reading objects

Request code for writing objects

Address path, length, data to be sent

Address, length of data to be received

Activity bit, exchange report, length

210

35013154.02 07/2008

Data coding

Modbus Plus programming

The data of read / write requests are encoded in internal words, to be sent in the following way:

%MW300

Third address

Second address

Fifth address

%MW301

Fourth address

Type

%MW302

Segment

%MW303 %MW304

%MW306 to

%MW349

Address of first word

Size of data Data

35013154.02 07/2008

211

Modbus Plus programming

Examples of Exchanges on Remote Networks

At a Glance

22

The following illustration shows the two types, which are processed below:

Modbus Plus

Premium

13

Quantum

61

BP85

Bridge Plus

12 30 15 25

Quantum

62

Quantum

BP85

Bridge Plus

4 7

Quantum

9

22

Slave

A

1

Bridge multiplexer

2 3 4

Modem

Modem

Master

A

Modem

Slave

49

Slave

69

BP85

Bridge Plus

212

35013154.02 07/2008

Example 1

Modbus Plus programming z z z

Reading, using a Premium PLC, of 120 internal words at address 80 of the Quantum station (local address 62) requires:

The routing path to access the Quantum station: 61, 30, 22, 62, 0.

The read request code: 16#36.

The actual size of data to be transferred (latched in %MW603): 10 bytes.

SEND_REQ(ADR#0.1.61, 16#36, %MW300:5, %MW450:120, %MW600:4)

Coding of the data to be transferred:

Parameters

%MW300

%MW301

%MW302

%MW303

%MW304

No data

Values

0x161E

0x003E

0x0768

80

120

Description

Second and third crossing point addresses (30, 22)

Fourth and fifth crossing point addresses (62, 0)

Segment 104 and type 7 (according to the type of variable to be read or written)

Address of the first internal word to be read in the Quantum station

Size of data to be read (in words)

Note: After the execution of the SEND_REQ function, it is necessary to reclassify the bytes in the correct order.

35013154.02 07/2008

213

Modbus Plus programming

Example 2 z z z z z

Writing, using a Premium PLC, of 50 internal words at address 560 of slave 49 connected to port 4 of the multiplexer bridge requires:

The routing path to access the slave: 61, 25, 4, 49, 0.

The write request code: 16#37.

The actual size of the data to be transmitted (memorized in %MW603): 110 bytes.

The values of the data to be written (latched in %MW305 to %MW354).

The response (latched in %MW450:1): does not contain any data to be received, but should have a minimum length of a word.

SEND_REQ(ADR#0.1.61, 16#37, %MW300:55, %MW450:1, %MW600:4)

Coding of the data to be transferred:

Parameters

%MW300

%MW301

%MW302

%MW303

%MW304

%MW305 to

%MW354

%MW603

Values

0x0419

0x0071

0x0768

560

50

110

Description

Second and third crossing point addresses (25, 4)

Fourth and fifth crossing point addresses (49, 0)

Segment 104 and type 7 (according to the type of variable to be read or written)

Address of the first internal word to be written in the Quantum station

Size of the data to be written (in words)

Data to be written

Actual size of the data to be transmitted with this function (in bytes)

214

35013154.02 07/2008

Modbus Plus programming

Diagnostic service

Introduction A Micro or Premium PLC can read or reset local or remote default counters on a local Modbus Plus network.

Data exchanges This type of exchange is accessible via the function SEND_REQ . To differentiate the reading and writing of data from a remote station, a request code is associated to the function SEND_REQ .

The addressing from a Premium station will be for example: z Reading counters z

SEND_REQ (ADR#0.1.5, 16#A2, %MW100:1, %MW200:20, %MW300:4) resetting counters

SEND_REQ (ADR#0.1.5, 16#A4, %MW100:1, %MW200:1, %MW300:4)

The following table describes the different parameters of the function:

Parameters

ADR#0.1.5

16#A2

16#A4

%MW100:1

%MW200:20

%MW200:1

%MW300:4

Description

Address of destination device for the message: z z z processor slot: 0 or 1

PCMCIA channel: 1 number of the destination connection point on the local bus: 5

Request code for reading counters

Request code for resetting counters

No data to send

No response on reception

Content of error counters

Activity bit, exchange report, length

Note: The length parameter in the report words is initialized at 0 before the request is sent.

35013154.02 07/2008

215

Modbus Plus programming

Counter list The following table shows the counters.

15

16

17

18

19

20

11

12

13

14

7

8

9

10

5

6

3

4

1

2

Number of the counter

Meaning

Retransmit deferral error counter

Receive buffer DMA overrun error counter

Repeated command received counter

Frame size error counter

Receiver collision abort error counter

Receiver alignment error counter

Receiver CRC error counter

Bad-packet-length error counter

Bad link address error counter

Transmit buffer DMA underrun error counter

Bad internal packet length error counter

Bad mac function code error counter

Communication retry counter

Communication failed error counter

Good receive packet success counter

No response received error counter

Exception response received error counter

Unexpected path error counter

Unexpected response error counter

Forgotten transaction error counter

216

35013154.02 07/2008

Modbus Plus programming

Global data exchange service

Introduction The global data exchange service is a simple exchange mechanism which is used to send broadcast messages between stations connected on the same Modbus Plus network.

During an exchange, a station which has the token can broadcast words destined for other stations connected on the network. A receiving station takes the content of words transmitted by the sending station, stores them in its PCMCIA card and sends them back to the network. The same applies to each station when the token is passed.

Precautions for use

For Premium and Micro PLCs, this service is provided by particular communication functions ( WRITE_GDATA and READ_GDATA ) periodically taken on by the application. It is not integrated in the Peer Cop transactions.

A Premium or Micro PLC can broadcast a maximum of 32 words.

Writing global data

Note: Data transfer from one station to another is automatic.

To read the global data which is sent, the application of the receiving station must read its PCMCIA card.

This type of exchange is accessible via the function WRITE_GDATA .

The addressing from a Premium station will be for example:

WRITE_GDATA (ADR#0.1.SYS, %MW100:x, %MW200:4)

The following table describes the different parameters of the function:

Parameters

ADR#0.1.SYS

%MW100:x

%MW200:4

Description z z

Broadcast address: z processor slot: 0 or 1

PCMCIA channel: 1 system channel: transmission for all the stations on the network

Content of the global data to be transmitted (x = 1 to 32 words)

Activity bit, exchange report, length

35013154.02 07/2008

217

Modbus Plus programming

Reading global data

This type of exchange is accessible via the function READ_GDATA .

The addressing from a Premium station will be for example:

READ_GDATA (ADR#0.1.10, %MW30:32, %MW300:4)

The following table describes the different parameters of the function:

Parameters

ADR#0.1.10

%MW30:32

%MW300:4

Description z z z

Address of device sending the message: processor slot: 0 or 1

PCMCIA channel: 1 number of station sending data: 10

Content of global data

Activity bit, exchange report, length

Note: The length of the global data actually read is contained in the activity report length word (e.g.: %MW304). One length = 0 means that there is no new global data available in the station specified in the request.

218

35013154.02 07/2008

Debugging Modbus Plus communication

16

Introduction

Subject of

Chapter

What's in this

Chapter?

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

This chapter contains the following topics:

Topic

Modbus Plus debugging screen

Modbus Plus debugging screen

Page

220

221

35013154.02 07/2008

219

Modbus Plus debugging

Modbus Plus debugging screen

Introduction

Illustration

This screen, split into two zones, is used to declare the communication channel and to access the debugging parameters for a Modbus Plus link.

The screen dedicated to Modbus Plus communication looks like this:

TSX 57302 [RACK 0 POSITION 0]

Debugging

Designation: PROCESSOR TSX P 57302 Version: 3.0

1 DIAG...

CHANNEL 1

CHANNEL 1

MODBUS*

TSX MBP 100 PCMCIA CARD MODBUS*

MAST DIAG...

2

Station number:

RAZ counters

1

8

9

6

7

10

3

4

1

2

5

Debug values

Counter labels

Retransmit deferral error

Receive buffer DMA overrun error

Repeated command received

Frame size error

Receiver collision abort error

Receiver alignment error

Receiver CRC error

Bad-packet-length error

Bad link address error

Transmit buffer DMA underrun error

0

0

0

0

0

0

0

Value

0

0

0

Elements and functions

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

Address Zone

1 common

2 specific

Function

(See : PL7 Micro/Junior/Pro ; Communication applications ;

Volume 1) is used to access the debugging parameters of a Modbus Plus link.

220

35013154.02 07/2008

Modbus Plus debugging

Modbus Plus debugging screen

Introduction

Station numbering z z

The specific part is split into two windows: the Station numbering window, the Debugging value window.

z z

The window, identical to that in configuration, is used to select: either the local station, or the remote station.

Debugging value The window looks like this:

8

9

6

7

10

3

4

1

2

5

Debug values

Counter labels

Retransmit deferral error

Receive buffer DMA overrun error

Repeated command received

Frame size error

Receiver collision abort error

Receiver alignment error

Receiver CRC error

Bad-packet-length error

Bad link address error

Transmit buffer DMA underrun error

0

0

0

0

0

0

0

0

0

Value

0

This window displays the different fault counters of a station connected to the

Modbus Plus network.

By default, the screen proposes the default counters of the local station. It is possible to view the fault counters of a local station or of a remote station.

Note: To access the fault counters of a remote station, you must first select the number of the remote station.

the Reset Counters button resets the counters.

35013154.02 07/2008

221

Modbus Plus debugging

222

35013154.02 07/2008

Language objects associated with

Modbus Plus communication

17

Introduction

Subject of this section

What's in this

Chapter?

This Chapter introduces the language objects associated with Modbus Plus communication.

This chapter contains the following topics:

Topic

Implicit Exchange Language Object

Explicit exchange language object

Explicit exchange management and report

Language objects associated with configuration

Page

224

227

229

230

35013154.02 07/2008

223

Modbus Plus language objects

Implicit Exchange Language Object

At a Glance

Bit Objects

This page describes all implicit exchange language objects for Modbus Plus communication, which can be displayed or modified by the application program (PL7

Micro/Junior/Pro ; Communication applications ; Volume 1).

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, when set to 1, indicates a module error (at least one of the channels has an error)

When this bit is at 1, it indicates a line fault.

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

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

Object (1)

%IWxy.i.0

%IWxy.i.1

Function

Requests

Reserved

Meaning

Status of communication paths z z z z

Byte 0: number of communication functions processed simultaneously in client mode x0 = 1: communication function 1 x1 = 1: communication function 2 x2 = 1: communication function 3 x3 = 1: communication function 4 z z z z

Byte 1: number of communication functions processed simultaneously in server mode x8 = 1: communication function 1 x9 = 1: communication function 2 x10 = 1: communication function 3 x11 = 1: communication function 4

-

224

35013154.02 07/2008

35013154.02 07/2008

Modbus Plus language objects

Object (1)

%IWxy.i.2 to

%IWxy.i.5

%IWxy.i.6

Function

Periodic exchanges

Status bit availability

Status of the specific inputs

%IWxy.i.7 to

%IWxy.i.9

Status of the specific inputs

%IWxy.i.10

Status of the specific inputs

New presence of specific inputs

%IWxy.i.11 to

%IWxy.i.13

New presence of specific inputs

%IWxy.i.14

New presence of specific inputs

Meaning

When set to 1, the bit from rank j indicates that the station’s global data is operational, and that the station takes part in the token exchange.

z where j = 0 to 15 of word %IWxy.i.2:xj for stations

1 to 16, z where j = 0 to 15 of word %IWxy.i.3:xj for stations z

17 to 32, where j = 0 to 15 of word %IWxy.i.4:xj for stations

33 to 48, z where j = 0 to 15 of word %IWxy.i.5:xj for stations

49 to 64.

Example: bit 5 of word %IWxy.i.3:x5 indicates that station 22 takes part in global data exchange.

The bit from rank j is reset to 0 when the global data is read by the application (GetGlobalData, command 0x0A) or in the case of a STOP/RUN by the PLC.

Byte 0: the specific inputs of all remote stations are z z z available x0 = 0: the specific inputs are not available x0 = 1: the specific inputs are available x1 to x7: reserved

Byte 1: a bit at 1 indicates the presence of a station that is transmitting specific inputs. Stations 1 to 8.

A bit at 1 indicates the presence of a station that is transmitting specific inputs. Stations 9 to 56.

Byte 0: a bit at 1 indicates the presence of a station that is transmitting specific inputs. Stations 57 to 64.

Byte 1: a bit at 1 indicates the presence of new specific inputs. Stations 1 to 8.

A bit at 1 indicates the presence of new specific inputs. Stations 9 to 56.

Byte 0: a bit at 1 indicates the presence of new specific inputs. Stations 57 to 64.

Byte 1: not used

225

Modbus Plus language objects

Object (1) Function

%IWxy.i.15

Status bit availability

%IWxy.i.16 to

%IWxy.i.18

Status of the specific outputs

Status of the specific inputs

%IWxy.i.19

Status of the specific inputs

Meaning z z z

Byte 0: the specific outputs are available for all remote stations x0 = 0: the specific outputs are not available x0 = 1: the specific outputs are available x1 to x7: reserved

Byte 1: a bit at 1 indicates the presence of a station that is receiving specific outputs. Stations 1 to 8.

A bit at 1 indicates the presence of a station that is receiving specific outputs. Stations 9 to 56.

Byte 0: a bit at 1 indicates the presence of a station that is receiving specific outputs. Stations 57 to 64.

Byte 1: not used

Key

(1) z z z

Address xy.i

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

226

35013154.02 07/2008

Modbus Plus language objects

Explicit exchange language object

Introduction

Word objects

35013154.02 07/2008

This page describes all the language objects for explicit exchange in Modbus Plus communication that can be displayed or modified by the application program (PL7

Micro/Junior/Pro ; Communication applications ; Volume 1).

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

Status of link layer

Specific channel status

Peer Cop

Meaning z z z z z z 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 the one declared in the configuration, the submodules are not compatible) x6 = 1: module missing x7 = 1: error in one of the sub-modules z z z 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: hardware or software error or no configuration x6 = 1: processor communication error x7 = 1: application fault (double station address)

Byte 0 z z z

= 0: initialization phase

= 3: awaiting token phase

= 4..10: normal status z z z z

Byte 0 z = 0: station being tested

= 32: normal status

= 64: no token

= 96: only station (idem x0 of %MWxy.i.2)

= 128: two stations have the same number

(idem x7 of %MWxy.i.2)

227

Modbus Plus language objects

Object (1)

Key

(1)

Function Meaning

Address xy.i

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

228

35013154.02 07/2008

Modbus Plus language objects

Explicit exchange management and report

Introduction

Word objects

This page describes all the language objects that manage explicit exchanges

(See : PL7 Micro/Junior/Pro ; Communication applications ; Volume 1).

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

Object (1) Function

%MWxy.MOD.0 Module exchanges in progress

Meaning z z z x0 = 1: reading status in progress x1 = 1: sending of command parameters to the communication module x2 = 1: sending of adjustment parameters to the communication module

%MWxy.MOD.1 Module report

%MWxy.i.0

%MWxy.i.1

Channel report z z x1 = 0: command parameters received and accepted by the module x2 = 0: adjustment parameters received and accepted by the module

Channel exchanges in progress z z z x0 = 1: reading status in progress x1 = 1: sending of command parameters to the communication channel x2 = 1: sending of adjustment parameters to the communication channel z z 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

35013154.02 07/2008

229

Modbus Plus language objects

Language objects associated with configuration

Introduction

Internal constants

230

This page describes all the configuration language objects in Modbus Plus communication that can be displayed by the application program.

The following table describes the internal constants:

Object

%KWxy.i.0

%KWxy.i.1

%KWxy.i.2

Function

Type

Station Address

Peer Cop

Meaning

Byte 0 = 14 for Modbus PLUS communication

Byte 0: station address

Byte 0 = 1: no Peer Cop service

Byte 0 = 2: Peer Cop service

Timeout behavior Byte 1 = 1: cleared inputs

Byte 1 = 2: inputs maintained at the last value

%KWxy.i.3

Destination address for specific inputs

Address of first internal word %MW used for receiving specific inputs

%KWxy.i.4

Source address of specific outputs

Address of first internal word %MW used for sending specific outputs

%KWxy.i.5

Size of specific outputs for nodes 1 and 2

%KWxy.i.6

Size of specific outputs for nodes 3 and 4 z z

Number of specific output words to be sent to connection point 1 and 2 byte 0: connection point 1 byte 1: connection point 2

Number of specific output words to be sent to connection points 3 and 4 z z byte 0: connection point 3 byte 1: connection point 4

...

...

%KWxy.i.3

6

...

Size of specific outputs for nodes 63 and 64

%KWxy.i.3

7

Size of specific inputs for nodes 1 and 2 z z

Number of specific output words to be sent to connection points 63 and 64 byte 0: connection point 63 byte 1: connection point 64

Number of specific input words to be received by connection points 1 and 2 z z byte 0: connection point 1 byte 1: connection point 2

%KWxy.i.3

8

...

Size of specific inputs for nodes 3 and 4

...

Number of specific input words to be received by connection points 3 and 4 z byte 0: connection point 3 z byte 1: connection point 4

...

35013154.02 07/2008

Modbus Plus language objects

Object

%KWxy.i.6

8

Function

Size of specific inputs for nodes 63 and 64

%KWxy.i.6

9

Timeout of Peer Cop service

Meaning z z

Number of specific input words to be received by connection points 63 and 64 byte 0: connection point 63 byte 1: connection point 64

Time interval of Timeout z byte 0 = 1 to 100: from 20 ms to 2 s

35013154.02 07/2008

231

Modbus Plus language objects

232

35013154.02 07/2008

Communication via FIPIO bus

IV

Introduction

Subject of this part

What's in this

Part?

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

This part contains the following chapters:

Chapter

18

19

20

21

22

23

24

25

Chapter Name

Communication via FIPIO bus

Configuring Fipio communication

Programming Fipio communication

Debugging a Fipio communication

Fipio communication diagnostics

Language objects associated with Fipio communication

Fipio communication standard profiles

Fipio Agent

Page

235

263

297

303

309

323

329

357

35013154.02 07/2008

233

Communication via FIPIO

234

35013154.02 07/2008

Communication via FIPIO bus

18

Introduction

Subject of this

Chapter

What's in this

Chapter?

This Chapter introduces communication via the FIPIO bus and its services.

This chapter contains the following sections:

Section

18.1

18.2

Topic

Introduction to Fipio communication

Characteristics

Page

236

241

35013154.02 07/2208

235

General

18.1

Introduction to Fipio communication

Introduction

Aim of this

Section

What's in this

Section?

This Section provides a summary description of the Fipio bus and its associated services.

This section contains the following topics:

Topic

Introduction

Addressing of Remote Module Language Objects on a FIPIO Bus

Page

237

238

236

35013154.02 07/2208

General

Introduction

Introduction

Associated manuals

Communication via FIPIO is part of Schneider Automation’s global WORLDFIP package.

FIPIO is a field bus used to delocalize the inputs/outputs of a PLC station and its industrial periphery to be as close as possible to the working part.

The FIPIO protocol uses producer/consumer exchanges (e.g.: common words) and the bus is managed via a bus arbiter.

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

Title

FIPIO bus - Reference manual

Micro PLCs - Installation manual

Premium TSX PLCs - Installation manual

Description

Detailed description of the FIPWAY bus and hardware installation

Hardware installation

Hardware installation

Note: refer to the separate documentation pertaining to each device connected to the FIPIO bus for details on their installation.

35013154.02 07/2208

237

General

Addressing of Remote Module Language Objects on a FIPIO Bus

At a Glance

Illustration

The addressing of the main bit and word objects of remote modules on the FIPIO bus is performed on a geographical basis. That means that it depends on: z z z the connection point,

The type of module (base or extended),

The channel number.

Addressing is defined in the following way:

% I, Q, M, K

Symbol Type of object

X, W, D, F

Format

\ p.2.c

\ m

Address of module/channel and connection point

Rack n°

• i •

Channel

No.

r

Rank

238

35013154.02 07/2208

General

Syntax The table below describes the different elements that make up addressing.

Family

Symbol

Type of object

Format (size)

Module/channel address and connection point p

2 c

Module position m

Channel No.

i

Rank

W

D

F

Element Values Meaning

% -

I

Q

M

K

-

-

-

-

Image of the physical input of the module,

Image of the physical output of the module,

This information is exchanged automatically for each cycle of the task to which they are attached.

Internal variable

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

Internal constant

This configuration information is available as read only.

X -

16 Bit

32 Bit

32 Bit

Boolean

For Boolean objects the X can be omitted.

Single length.

Double length.

Floating point. The floating point format used is the IEEE Std 754-1985 standard (equivalent to IEC 559).

0 or 1

-

Position number of the processor in the rack.

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

1 to 127 Connection point number.

r

0 or 1

0 to 127 or MOD

0: base module, 1: extension module.

MOD: channel reserved for managing the module and parameters common to all the channels.

0 to 255 or ERR

ERR: indicates a module or channel fault.

35013154.02 07/2208

239

General

Examples The table below shows some examples of addressing objects.

Object

%MW\0.2.1\0.5.2

%I\0.2.1\0.7

Meaning

Status word at rank 2 of the image bit of input 5 of the remote input base module situated at connection point 1 on the FIPIO bus.

Image bit of input 7 of remote input base module situated at connection point 1 on the FIPIO bus.

%Q\0.2.1\1.2

Image bit of output 2 of the remote output extension module situated at connection point 1 on the FIPIO bus.

%I\0.2.2\0.MOD.ERR Fault information for Momentum module situated at connection point

2 on the FIPIO bus.

%Q\1.2.3\0.0.ERR

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

0

TSX 57253 FIPIO manager

1 TBX LEP 030 0 TBX DES 1622

2 170 FNT 110 01 0 170 AAI 030 00

3 TSX FPP 010 0 T CCX 17 20 F

1 TBX DSS 1622

240

35013154.02 07/2208

General

18.2

Characteristics

Introduction

Aim of this

Section

What's in this

Section?

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

This section contains the following topics:

Topic

Hardware compatibility relating to the bus manager

Software compatibility relating to the bus manager

Software compatibility: Network transparency

Software compatibility: communication with the exterior

Compatibility information relating to TBX devices

Compatibility information relating to Momentum devices

Compatibility information relating to the programming terminal

Compatibility information relating to other devices

FIPIO bus operating mode

Network cycle time: mono task application

Network cycle time: multitasking application

Example of calculating the network cycle times of a multitasking application

Page

242

243

244

246

248

250

251

252

254

256

258

261

35013154.02 07/2208

241

General

Hardware compatibility relating to the bus manager

General

Availability

Capacity

The binary flow of the bus is 1 Mbits/s and it can extend to a length of up to 15 Km, with four optical or electric repeaters (TSX FP ACC 6).

The FIPIO bus links up to Hirshmann optical transmitters, which allows medium redundancy architectures to be created.

This type of communication is available via built-in links on Premium PLCs from version V3.0 onwards.

The PLCs with built-in FIPIO links are the following: z z

TSX type processors: z TSX P57 153, z z

TSX P57 253, TSX P57 2823,

TSX P57 353/353A z TSX P57 453/453A, TSX P57 4823/4823A.

PCX type processors: z PCX57353.

The bus manager can also be a PLC of the following type: z z

TSX 47-107 version 5.3 minimum,

S1000.

Processors with built-in FIPIO links are used to manage 128 connection points

(TSX P57 153 = 64) on the bus (addresses 0 to 127).

The bus manager is connected to address 0, and address 63 is reserved for the programming and diagnostics terminal.

These processors have a RAM memory for saving the configurations of devices connected to the bus. This memory has a maximum capacity of 94,320 bytes and

213,104 for (TSX P57 453/453A/4823/4823A) processors.

242

35013154.02 07/2208

General

Software compatibility relating to the bus manager

Explicit exchange limits

Reminders

X-TEL software

Processors with a built-in FIPIO link can simultaneously activate 24 explicit exchange functions.

An exchange request addressed to a FIPIO device can take several MAST task cycles. Thus, it is absolutely necessary to manage the exchange management parameter words for all exchanges of explicit variables including

READ_STS %CH@channel and READ_STS %CH@MOD .

For example, if 24 functions are being processed simultaneously or if 25 functions are triggered in the same task cycle, the 25th, or any new function, will not be served and will terminate in error.

For a READ_STS exchange, if the twenty-fifth exchange is impossible, the report signals a communication fault in the word: %MW\p.2.c\m.v.2.

For WRITE_CMD , READ_PARAM , WRITE_PARAM , RESTORE_PARAM exchanges, the report signals a communication fault in the word %MW\p.2.c\m.v.1. A likely cause is a lack of system resources to provide the service.

The system word %SW155 contains the number of explicit exchanges in progress.

Bit %SW116: x2 switches to 1 if the maximum number of simultaneous explicit exchanges is reached or exceeded.

When the bus manager is a series 7 PLC (TSX 47-107), the configuration of the bus and the manager is performed by the X-TEL software workbench, of version 6.0 or later.

35013154.02 07/2208

243

General

Software compatibility: Network transparency

Introduction

Transparency restrictions

Exchanges from a remote station to the FIPIO bus or vice versa are possible under certain conditions.

Inter-station communication with FIPIO is only available if the bus arbiter is a

Premium PLC, of at least version V3.3.

Exchanges from a third-party device to a PLC connected as a FIPIO slave are only possible if the PLC is a Premium of V3.3 at least. Communication with a Micro PLC is not possible.

A FIPIO agent does not communicate with the exterior.

Only one programming terminal can be connected to the FIPIO bus. If it is present in the configuration, it must be connected to the default connection port (63).

This programming terminal cannot be used to load the application onto the FIPIO bus arbiter.

244

35013154.02 07/2208

Illustration

General

The following illustration shows the different exchanges possible between a FIPIO bus and a network or another bus.

FIPAWAY, ETHERNET, Uni-telway, ...

Premium V3.3

Third party device

0

Micro

Premium V3.3

Magelis

35013154.02 07/2208

63

Programming terminal

245

General

Software compatibility: communication with the exterior

Introduction To communicate from a station connected to the FIPIO bus to an outside device, the transmitter station must address the master PLC and not the destination device

(requests are not routed directly).

Example

Note: the master PLC application transfers these requests to the destination device.

In the following example, an exchange from the FIPIO bus to the Uni-telway bus has to be performed. For a transfer in the opposite direction, the procedure is identical.

Premium master, Serie 7

Step 2

Step 1

0

Uni-telway

6

Ad0 = 1

Ad1 = 2

Ad2 = 3

63

Step 1 The transmitter station, connected to connection port 6 on FIPIO, sends the request to the master PLC. The destination address is the master PLC address.

WRITE_VAR (ADR#\6.1.0\SYS, %MW,0,10, %MW:10, %MW100:4)

The master PLC generates the report.

246

35013154.02 07/2208

Step 2

General

When the master PLC application receives the request from the transmitter station, it directs it to the destination device in accordance with the Uni-telway protocol.

WRITE_VAR (ADR#0.0.1, '%MW', 100, 10, %MW10:10, %MW40:4)

The report is sent to the master PLC.

35013154.02 07/2208

247

General

Compatibility information relating to TBX devices

Introduction

Rules of use

Addressing

The following compatibility information relates to: z z the addressing supported by the different connectable devices, the memory space that the devices take up in the configuration RAM.

If a device linked to a connection port is modular, it must be homogeneous at an application-specific level. Discrete base and extension or analog base and extension (not a mixture of discrete and analog).

The device is only controlled by one PL7 task (FAST or MAST) (no assigning of channel groups of the same TBX to different tasks).

The FIPIO addressing depends on the type of device:

Types of device

Compact TBXs

Sealed TBXs

Modular TBXs

TBX SAP 10

FIPIO addresses

1...31

1...62, 64...127

1...62, 64...127

1...62, 64...127

Comments

TBX C•

TBX E•

TBX LEP 020, TBX LEP 030

AS-i gateway

248

35013154.02 07/2208

Maximum configuration

General

The number of modules of the same reference connected to the FIPIO bus in a configuration is limited. The values in the table below are expressed in bytes.

Module Base

AES 200, ASS 400

AMS 620

1332

1332

1152

Extension Maximum number of connection points

TSX P57

153

TSX P57

253/2823/

353

TSX P57

453/4823

272 For 2 or 4 channels

62 70 125

528

-

For 8 channels

59 59

For 10 or 12 channels

50

31

50

31

126

114

31 CEP 1622, CSP 1622,

CSP 1625

DES •••, DMS •••, DSS •••

SAP 10

1152

1088

144

-

62

52

81

52

126

117

35013154.02 07/2208

249

General

Compatibility information relating to Momentum devices

Introduction

Rules of use

Addressing

Maximum configuration

The following compatibility information relates to: z z the addressing supported by the different connectable devices, the memory space that the devices take up in the configuration RAM. installing Momentum devices on FIPIO is only possible with the communication module: 170 FNT 110 01.

A Momentum device can have addresses from 1 to 62 or 64 to 127.

The number of modules of the same reference connected to the FIPIO bus in a configuration is limited. The values in the table below are expressed in bytes.

Module Base

ADI, ADM, ADO

ARM 370 30

ANR 120 90

AAI 520 40 00

AMM 090 00, AAI 030 00,

AAO 120 00, AAO 921 00

AAI 140 00

FED C32

FED C32P

FED M32

FED M32P

FRD C2

FSD C8

FSD C8P

FSD M8

FSD M8P

2304

1280

2304

1424

2448

832

896

1808

1040

1952

832

832

832

1808

1808

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

Extension Maximum number of connection points

TSX P57

153

TSX P57

253/2823/

353

TSX P57

453/4823

62

62

62

52

52

98

98

98

52

52

98

98

98

98

98

62

38

62

40

62

40

62

52

62

48

40

73

40

66

38

113

105

52

90

48

92

126

92

126

87

126

126

117

126

109

250

35013154.02 07/2208

General

Compatibility information relating to the programming terminal

Introduction

Rules of use

The following compatibility information relates to: z z the addressing supported by the different connectable devices, the memory space that the devices take up in the configuration RAM.

A programming terminal fitted with the TSX FPC 10 card or the PCMCIA card

TSX FPP 20 must be connected to the FIPIO address 63.

PL7 operates in connected mode with the FIPIO manager PLC.

If the manager PLC has an application in which one or several agent devices are configured: z z

PL7 communicates with the Micro/Premium FIPIO agent PLCs.

MMI 17 communicates with the CCX-17.

It is not possible to download a PL7 application to the manager from a programming terminal. However, it is possible to download a PL7 application to a FIPIO agent

PLC.

35013154.02 07/2208

251

General

Compatibility information relating to other devices

Introduction

Addressing

The following compatibility information relates to: z z the addressing supported by the different connectable devices, the memory space that the devices take up in the configuration RAM.

The FIPIO addressing depends on the type of device:

Types of device

Lexium 15/17D

ATV-16/58/68

CCX 17

Magelis

FipConnect products

FIPIO addresses Comments

1...62

The speed controllers are fitted with an

AM0 FIP 001V000card, of version V1.2 or later.

1...62

The speed controllers are fitted with a

TSX FPP 10 card, of version V1.8 or later.

1...62

The consoles have to be of version V2.4 or later and are fitted with the TSX FPP 10 card of version V1.8 or later.

1...62

1...62, 64...127

The consoles are fitted with a TSX FPP 10 card of version V1.8 or later.

apart from limitations specific to the product used

252

35013154.02 07/2208

Maximum configuration

General

The number of modules of the same reference connected to the FIPIO bus in a configuration is limited. The values in the table below are expressed in bytes.

Module Base Extension Maximum number of connection points

TSX P57

153

TSX P57

253/

2823/353

TSX P57

453/4823

48 48 62

52 52 62

ATV 16

ATV 58/58F with the

VW-A58301 card

ATV 58/58F PKW with the

VW-A58311 card

ATV 68

CCX 17

EEF 08D2, EEF 16D2

1952

1808

1280

ESF 08T22 EMF 16DT2

FED C32

FED C32P

FED M32

FED M32P

FRD C2

FSD C8

FSD C8P

FSD M8

FSD M8P

Micro Premium Agent

1952

1424

ADVANTYS STB NFP 2112 02 832

1424

2448

832

896

1808

1040

1280

1952

832

1808

1280

2304

ADVANTYS STB NFP 2112 08 896

ADVANTYS STB NFP 2112 32 1280

Lexium 15

Lexium 17D

-

62

52

62

62

38

62

52

62

40

62

4

62

62

62

62

48

62

62

62

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

62 62 62

66

38

113

105

52

90

52

73

40

62

4

98

48

62

113

105

73

66

66

126

87

126

126

117

126

62

4

98

98

126

92

109

62

126

126

126

126

126

35013154.02 07/2208

253

General

FIPIO bus operating mode

Introduction The FIPIO bus operating mode is linked to the processor operating mode and to the physical state of the bus.

If the number of physical errors detected by the processor is endangering the nominal operation of the devices connected to the bus, the processor stops all bus activity. In this case, the devices connected apply the fallback values to the inputs/ outputs.

Operating mode The operating mode is as follows:

Phase

1

2

3

4

5

6

Description

Cold restart of the processor with a FIPIO application: the bus is started automatically; the I/Os are monitored and commanded.

Downloading an FIPIO application: the bus is started automatically; the inputs/ outputs are monitored and commanded.

If the processor detects serious physical errors, the FIPIO bus is stopped automatically. The connected devices apply the fallback values; the processor no longer monitors the inputs/outputs. A serious physical error is for example the disconnection of the line plug, the disconnection of the FIPIO terminal block on the processor, etc…

Following an automatic stop (serious errors detected by the processor): z the bit %SW144:x2 is set; the processor periodically carries out a restart attempt, trying to monitor and command the inputs/outputs of the connected devices. This is automatic mode.

z the bit %SW144:x2 is cleared; to restart the bus, there a user action must be performed via the program or via the programming terminal. Set bits

%SW144:x0 and %SW144:x1 to 1. This is manual mode.

Warm restart: the bus is restarted automatically if it has not been stopped voluntarily by an action on the system word %SW144 bits 0 and 1. The bus is returned to the state it was in before the power outage.

If %S0 = 1 the system words are initialized, and if the bus had been stopped, it is restarted.

254

35013154.02 07/2208

General

Information on manual mode

Information on automatic mode

If the FIPIO bus is stopped without a voluntary action on the system word %SW144, this means that the processor has detected physical errors which prevent the nominal operation of the bus and the connected devices.

In this case, and only in this case, , if bit %SW144:x2 is set to 1 (automatic start), the processor will make periodic and automatic attempts to restart the exchanges on the bus.

If bit %SW144:x2 is at 0 following the stopping of the bus owing to physical errors, it is necessary to reset bits %SW144 x:0 and %SW144 x:1 via the program or via the programming terminal in order to restart the FIPIO bus. In this case, the bus will restart if, and only if, the physical error which caused the stop has disappeared .

Example

If %SW144:x0 is set to 0 (via the programming terminal or via the program) the production/consumer function (PC) stops. No more variables or messages are exchanged on the bus.

If %SW144:x1 is set to 0 (via the programming terminal or via the program) the bus arbiter function (BA) stops. There is no more scanning of variables or messages on the bus.

To completely and voluntarily stop the activity on the FIPIO bus, it is necessary to simultaneously set bits 0 and 1 of the system word %SW144 to 0 via the programming terminal or via the program.

if bit %SW144 x:2 = 1 on disconnection/reconnection of the processor FIPIO terminal block, the bus will be restarted automatically.

The devices will be monitored once again and will be able to apply the program values.

if bit %SW144 x:2 = 1 on disconnection/reconnection of the processor FIPIO bus, the connected devices on the bus will be neither monitored, nor will they be able to apply the program values.

The devices will be monitored once again if the user sets bits %SW144:x0 and

%SW144:x1 = 1.

35013154.02 07/2208

255

General

Network cycle time: mono task application

Introduction

Calculation of the network cycle time

The network cycle time for a mono task application is calculated for the following configuration: z z the length of the bus is 1 Km, the values corresponding to the reversal and silence times and the bandwidths are default values (automatic mode).

For an application which has all the devices configured in the same task, the value of the network cycle time of the task, in milliseconds, is obtained, for information purposes only, by the following formula:

TCR_TASK= 1,45 +

Σ(

K x number of equipments of the same family)

Value of coefficient K

Coefficient K will be defined as follows:

1,5

1,5

0,6

1,5

0,4

0,6

1,5

0,6

0,6

0,6

0,6

Coefficient K

0,5

0,9

0,4

Family

TBX

TBX

Momentum

Momentum

ATV-16

ATV-58

CCX 17

CCX 17-32

TSX 37/57

AS-i gateway

Magelis

STD_P

STD_P

STD_P

Device

Discrete

Analog

Discrete

Analog

All

All

All

All

All

TSX SAP 10

All

FRD

FSP

FED

256

35013154.02 07/2208

Example The configuration of the example is as follows: z z

All the elements are configured in the MAST task in the application.

The configuration comprises: z 10 discrete TBXs, z z

11 analog TBXs,

12 discrete Momentums.

The calculation of the cycle time for the Mast task is as follows:

TCR_MAST = 1.45 + ((0.5 x 10) + (0.9 x 11) + (0.4 x 12)) = 21.15 ms

The network cycle time is about 21 ms.

General

35013154.02 07/2208

257

General

Network cycle time: multitasking application

Introduction

Convention

For a multitasking application with two periodic tasks, and if the devices are configured in each of the tasks, the value of the network cycle times depends on the configuration of the different tasks.

The cycle time values calculated with the following algorithm are the maximum values. The actual values are less than or equal to these values.

The following table shows all the parameters involved in the calculation of the network cycle time.

Parameter

P max

P min

T max

T min

R

NE max

NE min

NE_Equip

TCR_T max

TCR_T min

Definition

Value of the largest task period (MAST or FAST)

Value of the smallest task period (MAST or FAST)

Task with period P max

Task with period P min

Ratio between the periods (This ratio must be a whole number; it will be rounded off to the nearest whole number if necessary).

Number of devices from the same family configured in T max

Number of devices from the same family configured in T min

Equivalent number of devices from the same family

Network cycle time for the task T max

Network cycle time for the task T min

258

35013154.02 07/2208

General

Calculation algorithm

To calculate the network cycle time, the algorithm is as follows:

Stage

1

Description

Calculation of R

2

3

4

R =

Pmin

Calculation of NE_Equip (for each device family)

NE_Equip =

( (

R

×

NEmin

)

+ NEmax

)

Calculation of TCR_T max

TCR_Tmax = 1,45 +

∑

(

K

×

NE_Equip

)

Calculation of TCR_T min

TCR_Tmin =

R

35013154.02 07/2208

259

General

Value of coefficient K

Coefficient K will be defined as follows:

1,5

0,4

0,6

1,5

0,4

0,6

1,5

1,3

1,5

0,6

0,6

0,6

1,5

1,5

0,6

Coefficient K

0,5

0,9

0,4

0,6

Family

TBX

TBX

Momentum

Momentum

ATV-16

ATV-58

CCX 17

CCX 17-32

TSX 37/57

AS-i gateway

Magelis

STD_P

STD_P

STD_P

ADVANTYS STB NFP 2212 02

ADVANTYS STB NFP 2212 08

ADVANTYS STB NFP 2212 32

Lexium 15

Lexium 17D

All

All

All

All

FRD

FSP

FED

All

All

Device

Discrete

Analog

Discrete

Analog

All

All

All

All

All

TSX SAP 10

Interpretation of the results

To refresh the inputs/outputs on the bus, the following constraints are imposed: z z

For the periodic tasks in controlled mode, the network cycle time of the task must be less than the task period.

For the periodic tasks in free mode, the network cycle time of the task must be less than the task watchdog.

260

35013154.02 07/2208

General

Example of calculating the network cycle times of a multitasking application

Introduction

Convention

Algorithm

The configuration of the example is as follows: z z

Task periods: z z

MAST: 60 ms

FAST: 15 ms

The configuration comprises: z 6 discrete TBXs configured in the MAST task and 4 discrete TBXs configured z in the FAST task,

6 analog TBXs configured in the MAST task and 4 analog TBXs configured in z z the FAST task,

6 discrete Momentums configured in the MAST task and 4 discrete

Momentums configured in the FAST task,

6 analog Momentums configured in the MAST task and 4 analog Momentums configured in the FAST task,

Depending on the configuration, the application of conventions involves: z z z

P max

= 60 and P min

= 15

T max

= T

MAST

and T min

= T

FAST

TCR_T max

= TCR_T

MAST

and TCR_T min

= TCR_T

FAST

The following table shows the algorithm:

Stage

1

2

3

4

Description

Calculation of R

R = 60 / 15 = 4

Calculation of the equivalent number of devices

NE_TBX_TOR = (R * 4 + 6) = 22

NE_TBX_ANA = (R * 4 + 6) = 22

NE_MOMENTUM_TOR = (R * 4 + 6) = 22

NE_MOMENTUM_ANA = (R * 4 + 6) = 22

Calculation of the network cycle times TCR_T

MAST

TCR_T

MAST

= 1.45 + ((0.5 * 22) + (0.9 * 22) + (0.4 * 22) + (0.6 * 22))

TCR_T

MAST

= 54.25 ms

Calculation of the network cycle times TCR_T

FAST

TCR_T

FAST

= 54.25 / 4

TCR_T

FAST

= 13.56 ms

35013154.02 07/2208

261

General

Conclusions The network cycle times of each equal: z z

TCR_T

MAST

= 55 ms,

TCR_T

FAST

= 14 ms.

The time period for MAST and FAST tasks are sufficient to refresh the inputs/ outputs.

262

35013154.02 07/2208

Configuring Fipio communication

19

Introduction

Subject of this

Chapter

What's in this

Chapter?

This chapter describes the Configuration process during set-up of Fipio communication.

This chapter contains the following sections:

Section

19.1

19.2

19.3

19.4

19.5

Topic

General information on configuration

Fipio bus configuration

Configuration of devices on the Fipio bus

Input/output management by the PL7 tasks

Confirmation of the Fipio bus configuration

Page

264

265

282

287

291

35013154.02 07/2208

263

Fipio Configuration

19.1

General information on configuration

Configuration mode

Introduction

Methodology

The creation of an application to implement a FIPIO bus requires the configuration of several elements via the PL7 software.

The following methodology reviews the different phases involved in configuring the

FIPIO bus:

Configuring points of connection and bus properties

This phase is used to define the type of device connected to the bus, bus management (e.g.: length, bandwidth, etc.

Configuring each device connected to the bus.

This phase is used to configure each device (e.g.: PLC task managing devices, inputs, outputs, etc.).

Adapting PL7 tasks according to the bus topology.

This phase is used to define the management of input/outputs on the bus by PL7 tasks (e.g.: cyclic or periodic task, controlled or free mode, etc.

264

35013154.02 07/2208

19.2

Fipio bus configuration

Introduction

Aim of this

Section

What's in this

Section?

This section introduces the Fipio bus configuration principles.

This section contains the following topics:

Topic

How to access the FIPIO configuration screen

FIPIO bus configuration screen

How to add a device on to the bus

How to modify/delete/move/duplicate a bus device

How to access the FIPIO bus properties screen

FIPIO bus properties configuration screen

Properties of the Fipio Bus: General Tab

Properties of the Fipio bus: Expert tab

Expert Tab: Manual Mode

Fipio Configuration

Page

266

267

269

272

274

275

276

278

279

35013154.02 07/2208

265

Fipio Configuration

How to access the FIPIO configuration screen

Introduction

How to access the link

This operation describes how to access the configuration via the the Premium PLCs provided with a built-in link.

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

Step

1

2

Action

Access the hardware configuration screen

Double click on the FIPIO connector.

266

35013154.02 07/2208

Fipio Configuration

FIPIO bus configuration screen

Introduction

Illustration

This screen is used: z z to register devices which are connected to the bus, to parameter the bus properties.

The screen dedicated to FIPIO communication looks like this:

FIPIO Configuration

TSX 57252 V3.0

Bus length: 0

1

15 km

Logical address Communicator Standard module Extension module

0

Fipio manager TSX 57252

63 Privileged terminal

127

35013154.02 07/2208

267

Fipio Configuration

Elements and functions

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

Zone

Bus length

Logical address

Communicator

Standard module

Extension module

Function

This cursor is used to adjust the bus length. The default value is

1 Km.

This zone defines the address for each device.

This zone specifies the type of device which enables communication between the manager and the standard device.

Where the standard device has no need for a communicator, this zone is empty.

This zone specifies the standard device connected to the bus.

This zone gives information on whether an extension is associated to the standard device.

Grayed out rectangles on the bus indicate the two reserved addresses: z z

0 for the bus manager,

63 for the privileged terminal.

The available connection points are indicated by a small circle and dotted lines.

268

35013154.02 07/2208

How to add a device on to the bus

Fipio Configuration

35013154.02 07/2208

269

Fipio Configuration

Procedure This operation is used to logically add a device connected to the FIPIO bus.

Step

1

2

Action

Access the FIPIO configuration screen.

Result : the Add/Modify a device screen appears.

Connection point

Connection point number

Comment

1

1

0 TBX DSS 1622

Families

2

ADVANTYS STB

ATV-16

ATV-58

ATV-58F

ATV-68

CCX-17

CCX17-32

INDUCTEL

LEXIUM

MAGELIS

MOMENTUM

PASSERELLE

SIMULATION

STD_P

TBX

1.0

TBX AES 400

TBX AMS 620

TBX ASS 200

TBX CEP 1622

TBX CSP 1622

TBX CSP 1625

TBX DES 1622

TBX DES 1633

TBX DES 16C22

4 ENT.ANA.MULTI-RANGE

6 ENT.HN 2 ANALOG OUTPUTS

2 ISOLATED ANALOG OUTPUTS

TBX7 MONOBLOC 16 E 24VCC

TBX7 MONOBLOC 16SS 24Vcc

TBX7 MONOBLOC 16SR 24Vcc

TBX7 EMB. 16E 24VCC

TBX7 EMB. 16E 48VCC

TBX7 EMB. 16E CF 24VCC

Communicator

TBX LEP 030 TBX7 MOD.COM.FIP TOR+ANA

OK

4

5

6

7

3 Enter the connection point number which corresponds to the address.

By default, the PL7 software offers the first consecutive address which is free

Add a comment to the device connected to the connection point.

This field has a maximum length of 80 characters and is optional.

In the Family field, select the type of equipment to be connected to the bus.

Select the standard module and/or the extension module.

In the Communicator field, select the type of element enabling communication on the FIPIO bus.

For certain types of device, this window does not appear.

270

35013154.02 07/2208

Step

8

Action

Confirm with Ok .

Result: the module is registered.

Fipio Configuration

35013154.02 07/2208

271

Fipio Configuration

How to modify/delete/move/duplicate a bus device

Procedure for modifying a device

This operation is used to logically modify a device connected to the FIPIO bus.

Step

1

2

3

4

Action

Access the FIPIO configuration screen.

Double click on connection point corresponding to the device which is to be modified.

z z z z

Modify the component parts of the device: standard module, extension module, the communicator, the comment.

It is not possible to modify the family or the connection point number.

Confirm with Ok .

Procedure for deleting a device

This operation is used to logically delete a device connected to the FIPIO bus.

Step

1

2

3

4

Action

Access the FIPIO configuration screen.

Select the connection point to be deleted.

A dotted line square surrounds the selected connection point.

Select the Edit

→

Delete the device command.

Confirm the deletion with Yes .

272

35013154.02 07/2208

Fipio Configuration

Procedure for moving a device

Moving a device is not a physical move on the bus but a logic change of the device address. This involves modifying the address of I/O objects in the program and moving variables associated to these objects. On global confirmation of the configuration, the application program will be modified automatically to match the move.

Step

1

2

3

4

5

Action

Access the FIPIO configuration screen.

Select the connection point to be moved.

A dotted line square surrounds the selected connection point.

Select the Edit

→

Move a device command.

Supply the destination connection point number.

Confirm the move with the Ok button.

Procedure for duplicating a device

This function is similar to the function to move a device.

Step

1

2

3

4

5

Action

Access the FIPIO configuration screen.

Select the connection point to be moved.

A dotted line square surrounds the selected connection point.

Select the Edit

→

Duplicate a device command.

Supply the destination connection point number.

Confirm the move with the Ok button.

35013154.02 07/2208

273

Fipio Configuration

How to access the FIPIO bus properties screen

Introduction

How to access the link

This operation describes how to access the bus properties screen via Premium

PLCs with an integral link.

The following table shows the procedure:

Step

1

2

3

Action

Access the FIPIO configuration screen.

Right-click at the bottom of the FIPIO configuration screen.

Select the command FIPIO Bus Properties from the contextual menu.

274

35013154.02 07/2208

Fipio Configuration

FIPIO bus properties configuration screen

Introduction

Illustration

On a FIPIO bus, a single PLC allows the exchange of inputs/outputs; this is the bus arbiter. It manages the bus accesses of each connected device.

The screen attached to the properties therefore allows you to adapt the management parameters according to the devices which are connected.

The screen dedicated to the properties of the FIPIO bus looks like this:

FIPIO bus properties

General Expert

Profile

Fip

World Fip

Bus length

0

5

15 km

OK Cancel Apply Help

Elements and functions

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

Tab

General

Expert

Function

This tab is used to: z choose the type of profile managed by the bus arbiter, z adjust the bus length.

This tab is used for choosing the management mode. In the case where the management is manual, it is used to further adjust the management parameters according to the devices which are connected.

35013154.02 07/2208

275

Fipio Configuration

Properties of the Fipio Bus: General Tab

At a Glance

The Profile

With this tab, you can access three types of information: z z z

The profile,

The RAM Fip,

The bus length.

The profile is chosen according to the devices which are connected to the Fipio bus.

It can be in either of two versions: z z

FIP: z z

This profile is chosen by default.

It is compatible with all the devices of Schneider and partners.

WorldFip: z The selection of this mode allows you to operate the Fipio bus in accordance with the EN 50170 standard.

z z

Note: The WorldFip profile mode can be used with the following restrictions:

No TSX FP ACC6 or TSX FP ACC8 repeaters,

Use of TBX LEP 020 version 1.4 minimum and TBX LEP 030 version 1.2 minimum, z Use of the PCMCIA TSX FPP 10 card, version 1.8 minimum.

RAM Fip This is the memory used by the configured Fipio devices in relation to the memory available in the processor.

276

35013154.02 07/2208

The bus length

Fipio Configuration

With this cursor you can increase or decrease the bus length. The default value is

1 Km and the adjustment increment is 1 Km.

This length must be adjusted because it is taken into account in the calculation of the propagation time for the variables and messages on the bus and consequently in the calculation of the network cycle times.

Note: at each modification of the length of the Fipio bus, all the connected devices must be powered off, then on after the new project has been downloaded (in the

PLC).

35013154.02 07/2208

277

Fipio Configuration

Properties of the Fipio bus: Expert tab

Introduction With this tab, you have access to the management mode concerning the calculation of: z z reversal and silence time, bandwidths.

Note: at each modification of the parameters below, all the connected devices must be powered off, then on after the new application has been downloaded (in the PLC).

The automatic mode

Note: this mode is advocated.

The reversal and silence times and the bandwidths cannot be modified. They are calculated according to the bus parameters and device configuration data.

The manual mode

CAUTION

No monitoring is carried out in manual mode. Modifying these parameters can cause the device connected to the bus not to work.

Failure to follow these instructions can result in injury or equipment damage.

This mode is used to enter the reversal and silence times and the bandwidths.

It is mainly reserved for specific applications requiring these values to be modified

(example: use of Hirschmann transmittors).

278

35013154.02 07/2208

Fipio Configuration

Expert Tab: Manual Mode

At a Glance By selecting the manual mode, you have access to the following information: z z

The reversal and silence times,

The aperiodic bandwidths.

Illustration:

Bus properties

General Expert

Mode

Automatic

Manual

Silence time T0 ( μ s):

Slot time TR ( μ s):

Bandwidth

Aperiodic variables (kbits/s):

Message handling (kbits/s):

255

30

5

20

OK Cancel Help

35013154.02 07/2208

279

Fipio Configuration

Aperiodic variables

The following table gives a description of the times:

Reference

Silence time delay T0

Reversal time TR

Description

This defines the maximum time between the transmission of the last byte of a frame and the transmission of the first byte of the following frame.

This time is expressed in micro-seconds.

Its value must be greater than the reversal time TR and less than 255.

This defines the minimum time between the transmission of the last byte of a frame and the transmission of the first byte of the following frame.

This time is expressed in micro-seconds.

Its value must be greater than or equal to 1 and less than the silence time T0.

Note: in the case of using an OZD FIP G3, it is essential to adjust the value of

T0 = 255s and TR = 30s for all configurations.

280

35013154.02 07/2208

Aperiodic

Bandwidths

Fipio Configuration

There are two types of exchange on a Fipio bus: z z

Exchanges of cyclic variables which are reserved for the process data,

Exchanges of aperiodic variables which concern the configuration of connected devices, the adjustment and the messaging.

A decrease or increase of the bandwidth of the aperiodic exchanges (Variables and

Messages) slows down or accelerates the output of the configuration or adjustment variables which can circulate on the bus. The same applies to a decrease or increase of the aperiodic bandwidth of the messaging facility.

The following table gives a description of the aperiodic bandwidths:

Reference

Aperiodic variables

Messaging

Description

This defines the output of the aperiodic variables which can circulate on the bus.

This bandwidth is expressed in Kbits/s.

Its value can be adjusted from 1 to 200 Kbits/s.

This defines the output of the aperiodic messages which can circulate on the bus.

This bandwidth is expressed in Kbits/s.

Its value can be adjusted from 1 to 200 Kbits/s.

Note: an increase in the aperiodic bandwidth increases the network cycle time.

35013154.02 07/2208

281

Fipio Configuration

19.3

Configuration of devices on the Fipio bus

Introduction

Aim of this

Section

What's in this

Section?

This section introduces the configuration principles for Fipio bus devices.

This section contains the following topics:

Topic

How to access the FIPIO configuration screen

Configuration screen of a FIPIO device

How to access the different parameters according to device type

Page

283

284

286

282

35013154.02 07/2208

Fipio Configuration

How to access the FIPIO configuration screen

Introduction

How to access the link

When a device has been registered, it is possible to access its configuration as in the case of a rack module.

This screen is used to select the task which exchanges the inputs/outputs: FAST or

MAST, to modify the configuration or adjustment parameters specific to the module.

The following table shows the procedure for accessing the configuration of a device on FIPIO:

Step

1

2

Action

Access the FIPIO configuration screen

Double click on the standard module to be configured.

35013154.02 07/2208

283

Fipio Configuration

Configuration screen of a FIPIO device

Introduction

Illustration

This screen, split into several areas, is used to register the communication channel and to configure the parameters of the device selected for a FIPIO communication.

The screen looks like this:

1

2

FSD M8 P [FIPIO18 MODULE 0]

Configuration

Designation: EQP STD MOD 8MP

3

4

Channel

Local configuration

Task: MAST

Default configuration

Parameters

%KW\0.2.18\0.0.0

%KW\0.2.18\0.0.1

%KW\0.2.18\0.0.2

%KW\0.2.18\0.0.3

%KW\0.2.18\0.0.4

%KW\0.2.18\0.0.5

%KW\0.2.18\0.0.6

%KW\0.2.18\0.0.7

Symbol

Base

Decimal

Value

0

0

16#8040

16#0

0

0

0

16#4

284

35013154.02 07/2208

Fipio Configuration

Elements and functions

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

Address Zone

1 Title bar

2

3

Description

This zone defines the module reference and its physical position in the module.

Module This zone is used to input information with the aid of dropdown lists: z parameter type: z z the Configuration mode, the Adjustment mode (which can be accessed by certain device types), z z the Debugging mode (can only be accessed in online mode).

channel type (inputs or outputs) when the designated device has inputs and outputs.

Communication channel This zone is used to assign devices to either the MAST task or the FAST task, with the aid of a dropdown list.

Some device types have access to a Local configuration check box. If the box is checked off, the channel parameters can not be accessed.

4 Channel parameters This zone is used for device parametering. According to certain device types, this zone can not be accessed.

Note: for further information on configuration parameters, adjustment parameters and debugging parameters, refer to the documentation specific to each device.

35013154.02 07/2208

285

Fipio Configuration

How to access the different parameters according to device type

How to access the inputs/ outputs

The following procedure provides information on how to access the input or output parameters of a module. It is enabled in both offline and online mode.

Step

1

2

Action

Access the configuration screen of a FIPIO device.

Select input part or output part from the module zone’s dropdown list.

How to adjust the configuration parameters

The following procedure describes how to modify the adjustment parameters of a module. It is enabled in both offline and online mode.

Step

1

2

3

4

5

6

Action

Access the configuration screen of a FIPIO device.

Select adjustment mode from the module zone’s dropdown list.

Select the cell relating to the entry parameter.

Enter the parameter.

Enable by clicking on Input .

Enable the assignment.

How to assign a module to a PL7 task

The following procedure describes how to assign a module to a PL7 task. It is only enabled in offline mode.

Step

1

2

3

Action

Access the configuration screen of a FIPIO device.

Select MAST

→

or FAST Task from the dropdown list.

Enable the assignment.

286

35013154.02 07/2208

19.4

Fipio Configuration

Input/output management by the PL7 tasks

Introduction

Aim of this

Section

What's in this

Section?

This Section introduces the configuration principles for PL7 tasks in FIPIO mode.

This section contains the following topics:

Topic

How to access PL7 task configuration in FIPIO mode.

Configuration screen of a FIPIO processor

FIPIO input/output management using PL7 tasks

Page

288

289

290

35013154.02 07/2208

287

Fipio Configuration

How to access PL7 task configuration in FIPIO mode.

Introduction

Procedure

FIPIO Bus and device configuration modifies the task network cycle times in accordance with the input/output updating of each PL7 task.

These modifications can result in constraints on: z z task type (cyclic or periodic), as well as its execution time and watchdog,

FIPIO input/output processing in relation to the task cycle (controlled or free).

The PL7 software is used then to manage the inputs/outputs according to the MAST or FAST tasks and their network cycle time.

The following table shows the procedure for accessing the MAST and FAST tasks in FIPIO mode:

Step

1

2

Action

Access the hardware configuration screen

Double click on the processor.

288

35013154.02 07/2208

Fipio Configuration

Configuration screen of a FIPIO processor

Introduction

Illustration

This screen, split into various areas, is used to manage the FIPIO inputs/outputs according to: z z z z task type (MAST or FAST), use type (cyclic or periodic) and duration, watchdog, task network cycle time.

Only the section relating to FIPIO mode is presented below.

The screen looks like this:

TSX 57252 [RACK 0 POSITION 1]

Configuration

Designation: TSX P processor 57252

Operating Mode

Run/Stop input

Auto start in Run

%MWi Reset on cold restart

Memory Card

None

Tasks

MAST

Cyclic

Periodic

Watchdog

FAST

Period:

Watchdog

250

0 ms ms

FIPIO Mode

Network cycle time (calculated)

Controlled

Free

4 ms

100

5 ms ms

FIPIO Mode

cycle

Controlled

Free

0 ms

The FIPIO Mode window

You can access two types of information via the FIPIO Mode window: z z

Mode (controlled or free): is used to link input/output updating to the task cycle.

Network cycle time (calculated): this time represents the network cycle time associated with a task.

35013154.02 07/2208

289

Fipio Configuration

FIPIO input/output management using PL7 tasks

Introduction The FIPIO input/output management modes are dependent upon the type of task execution (cyclic or periodic).

Controlled FIPIO mode

This mode can only be accessed via a PL7 task declared as periodic.

Tasks

MAST

Cyclic

Periodic

Watchdog

FAST

Period:

Watchdog

150

250 ms

FIPIO Mode

Network cycle ms

Controlled

Free

4 ms

100

5 ms ms

FIPIO Mode

Network cycle

Controlled

Free

0 ms

In this mode, input/output refreshing is correlated with the task period. The system guarantees input/output updating during one period only. Only the inputs/outputs associated with this task are refreshed.

Choosing this mode imposes the following constraint:

The PLC task period (MAST or FAST) must be greater than or equal to the network cycle time

Free FIPIO mode This mode can be accessed via a periodic or cyclic declared PL7 task.

Tasks

MAST

Cyclic

Periodic

Watchdog 250

0 ms

FIPIO Mode

Network cycle ms

Controlled

Free

4 ms

FAST

Period:

Watchdog 100

5 ms ms

FIPIO Mode

Network cycle

Controlled

Free

0 ms

In this mode, no constraints are imposed on the task period. The PLC task period

(MAST or FAST) can be less than the network cycle time.

In this case, the task can be carried out without updating the inputs/outputs.

Selecting this mode provides the possibility of having the shortest possible task times for an application where the rate is critical.

290

35013154.02 07/2208

19.5

Fipio Configuration

Confirmation of the Fipio bus configuration

Introduction

Aim of this

Section

What's in this

Section?

This Section introduces the main instances of Fipio bus configuration refusal.

This section contains the following topics:

Topic

Confirming the configuration

Confirmation refused, examples

Page

292

294

35013154.02 07/2208

291

Fipio Configuration

Confirming the configuration

Introduction

Confirmation refused

On completion of the FIPIO bus configuration, and in order to be recognized in the new application, the global bus configuration must be confirmed.

The PL7 then checks the constraints associated with this new application. If the imposed constraints are not respected, no scanning table is created.

A message window opens in this case.

FIPIO Configuration

?

Cannot generate the scan table for

FIPIO I/Os

Close

Recommendations>>

How to access the recommendations

The configuration remains unconfirmed (Bus X physical configuration and FIPIO physical configuration) as long as the problem is not corrected by the user. This configuration can not be transferred into the PLC.

The Recommendations button enlarges the dialogue box where the reasons for refusal as well as useful corrective measures are located.

Step

1

Action

Select the Recommendations button.

292

35013154.02 07/2208

Result

Fipio Configuration

The characteristics of each configured task (MAST and FAST) are displayed.

FIPIO Configuration

Cannot generate the scan table for

FIPIO I/Os

?

Close

Recommendation>>

Periodic Mast task in controlled mode

Period: 100 ms

Network cycle time: 177 ms

The network cycle time is greater than the period.

To correct this you can:

- configure this task period at a value greater than 177ms

- reduce the number of devices configured in this task.

- switch this task to free mode

If a task’s constraints are not respected, the cause of the failure and corrective recommendations complete the characteristics.

Depending on the recommendations, there are two possible measures for correcting the configuration, these are as follows: z z

Access the configuration screen of the processor to modify the PL7 task management parameters.

Access the FIPIO configuration screen to modify device distribution in the MAST or FAST tasks.

35013154.02 07/2208

293

Fipio Configuration

Confirmation refused, examples

Introduction

Example 1

The following examples concern the main refusals encountered.

The MAST or FAST task has been configured in controlled periodic mode.

The network cycle time is greater than the period.

FIPIO Configuration

Cannot generate the scan table for

FIPIO I/Os

?

Close

Recommendation>>

Periodic Mast task in controlled mode

Period: 100 ms

Network cycle time: 177 ms

The network cycle time is greater than the period.

To correct this you can:

- configure this task period at a value greater than 177ms

- reduce the number of devices configured in this task.

- switch this task to free mode

294

35013154.02 07/2208

Fipio Configuration

Example 2 The MAST task has been configured in cyclic mode.

The network cycle time is greater than the watchdog.

FIPIO Configuration

Cannot generate the scan table for

FIPIO I/Os

?

Close

Recommendation>>

Cyclic Mast task

Watchdog: 100 ms

Network cycle time: 177 ms

The network cycle time is greater than the watchdog.

To correct this you can:

- configure the watchdog of this task period at a value greater than 177ms

- reduce the number of devices configured in this task.

Example 3 The MAST or FAST task has been configured in free periodic mode.

The network cycle time is greater than the watchdog.

FIPIO Configuration

Cannot generate the scan table for

FIPIO I/Os

?

Close

Recommendation>>

Periodic Mast task in free mode

Period: 50ms

Watchdog: 100 ms

Network cycle time: 177 ms

The network cycle time is greater than the watchdog.

To correct this you can:

- configure the watchdog of this task period at a value greater than

177ms

- reduce the number of devices configured in this task.

35013154.02 07/2208

295

Fipio Configuration

296

35013154.02 07/2208

Programming Fipio communication

20

Introduction

Subject of this

Chapter

What's in this

Chapter?

This Chapter describes the Programming process during set-up Fipio communication.

This chapter contains the following topics:

Topic

FIPIO error processing

Examples of explicit exchange saturation detection

Page

298

300

35013154.02 07/2208

297

Fipio Programming

FIPIO error processing

Introduction FIPIO error processing can be performed with the debugging and diagnostics screens.

It can however be useful to perform this processing using a program.

298

35013154.02 07/2208

Algorithm

Fipio Programming

The algorithm shown is an example of a FIPIO bus error detection and management application algorithm

Test bit %S10

(general input/output error)

%S10 = 0 ?

Yes

Find error on the FIPIO bus via

%S118

No No input/output error

Find faulty point of

connection via

%I\p2c\m.MOD.ERR = 1

%S118 = 0?

Yes

No Test error on bus X via

%S119

Find the word from %SW128 to

%SW143, which is different from FFFF

Find the faulty point of connection using the

%SWi:x word bit which is different from 0

There are two different methods for finding the faulty point of connection.

The recommended method is to find it by using system words %SW128 to

%SW143.

Diagnose the connection point using the

READ_STS %CH\p.2.c\0.MOD function

Find the faulty channel via

%I\p.2.c\m.v.ERR = 1

Diagnose the channel via the

READ_STS %CH\p.2.c\m.v.ERR

function

35013154.02 07/2208

299

Fipio Programming

Examples of explicit exchange saturation detection

Introduction The following examples are given in structured text language, but they can be translated into all the PL7 languages.

They only have to be taken into account if the PL7 application may activate more that 24 explicit functions at the same time and if you want to reiterate a request in the event of explicit exchange saturation.

Management of the READ_STS module

IF (NOT (%MW\0.2.1\0.MOD:x0)) THEN (*no request in progress*)

SET %M0; (*request latch*)

(*bit reset to 0 indicating saturation of explicit exchanges*)

%SW116:=%SW116 AND 2#1111111111111011;

READ_STS %CH\0.2.1\0.MOD;

IF (%SW116:x2) THEN

RESET %M0; (*READ_STS retried, saturation has occurred*)

(*%MW\0.2.1\0.MOD.2:x1 signals a functional error*)

END_IF;

END_IF;

IF(%M0 AND NOT (%MW\0.2.1\0.MOD:x0)) THEN

(*%MW\0.2.1\0.MOD.2 can be used*)

RESET %M0;

END_IF;

300

35013154.02 07/2208

Management of the READ_STS channel

Fipio Programming

IF (NOT (%MW\0.2.1\0.0:x0)) THEN (*no request in progress*)

SET %M1; (*request latch from channels 0 to 7*)

(*bit reset to 0 indicating saturation of explicit exchanges*)

%SW116:=%SW116 AND 2#1111111111111011;

READ_STS %CH\0.2.1\0.0;

IF (%SW116:x2) THEN

RESET %M1; (*READ_STS retried, saturation has occurred*)

(*%MW\0.2.1\0.0.2:x6 signals a communication error*)

END_IF;

END_IF;

IF(%M1 AND NOT (%MW\0.2.1\0.0:x0)) THEN

(*%MW\0.2.1\0.0.2 can be used*)

RESET %M1;

END_IF;

READ_PARAM at connection point

02

IF (NOT (%MW\0.2.2\0.0:x2)) THEN (*no request in progress*)

SET %M2; (*request latch from channels 0 to 7*)

(*bit reset to 0 indicating saturation of explicit exchanges*)

%SW116:=%SW116 AND 2#1111111111111011;

READ_PARAM %CH\0.2.2\0.0; (*request from the parameters*)

IF ((%MW\0.2.2\0.0.1:x) AND (%SW116:x2)) THEN

(*exchange refused*)

RESET %M2; (*saturation of explicit exchanges*)

END_IF;

END_IF;

IF(%M2 AND NOT (%MW\0.2.2\0.0:x2)) THEN

(*reading finished parameters*)

RESET %M2;

END_IF;

35013154.02 07/2208

301

Fipio Programming

WRITE_PARAM at connection point 02

IF (NOT (%MW\0.2.2\0.0:x2)) THEN (*no request in progress*)

SET %M3; (*request latch from channels 0 to 7*)

(*bit reset to 0 indicating saturation of explicit exchanges*)

%SW116:=%SW116 AND 2#1111111111111011;

WRITE_PARAM %CH\0.2.2\0.0, (*parameter transmitting*)

IF ((%MW\0.2.2\0.0.1:x2) AND (%SW116:x2)) THEN

(*exchange refused*)

RESET %M3; (*saturation of explicit exchanges*)

END_IF;

END_IF;

IF(%M3 AND NOT (%MW\0.2.2\0.0:x2)) THEN

(*end of parameter transmission*)

RESET %M3;

END_IF;

WRITE_CMD at connection point

02

IF (NOT (%MW\0.2.2\0.0:x1)) THEN (*no request in progress*)

SET %M3; (*request latch from channels 0 to 7*)

(*bit reset to 0 indicating saturation of explicit exchanges*)

%SW116:=%SW116 AND 2#1111111111111011;

WRITE_CMD %CH\0.2.2\0.0; (*command transmitting*)

IF ((%MW\0.2.2\0.0.1:x1) AND (%SW116:x2)) THEN

(*exchange refused*)

RESET %M3; (*saturation of explicit exchanges*)

END_IF;

END_IF;

IF(%M3 AND NOT (%MW\0.2.2\0.0:x1)) THEN

(*end of command transmission*)

RESET %M3;

END_IF;

302

35013154.02 07/2208

Debugging a Fipio communication

21

Introduction

Subject of this

Chapter

What's in this

Chapter?

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

This chapter contains the following topics:

Topic

Debugging mode

How to access the remote device debugging screens

FIPIO bus device debugging screen

Page

304

305

306

35013154.02 07/2208

303

Fipio Debugging

Debugging mode

Introduction

Inaccessible functions

Debugging mode can only be accessed in online mode.

This mode: z z uses a red square to display when a device is faulty from the FIPIO configuration screen, and adjusts and debugs the devices connected to the FIPIO bus from their application screen.

The following functions can not be accessed from the FIPIO configuration screen in online mode: z z z z adding on a device in online mode, duplicating or moving a device, modifying a device, deleting a device.

A message displayed in the status bar of the PL7 window gives the reason why access is denied.

304

35013154.02 07/2208

Fipio Debugging

How to access the remote device debugging screens

Introduction

Procedure

This operation describes how to access the debugging screen of a device connected to the FIPIO bus.

The following table shows the procedure:

Step

1

2

3

4

Action

Connect with the manager PLC.

Access the hardware configuration screen

Double click on the FIPIO connector.

Double click on the standard module to debug.

35013154.02 07/2208

305

Fipio Debugging

FIPIO bus device debugging screen

Introduction

Illustration

1

By opening the application screen of a device in debugging mode, the following functions can be accessed: z z z z z parameter display module configuration, reading, writing, and saving adjustment parameters, reading, writing, and forcing the inputs/outputs, aperiodic status data reading, command word writing,

The screen dedicated to devices looks like this:

TSX DMS 1025 [FIPIO1 MODULE 0]

Debugging

Designation: TBX7 EMB.8E/2SR24Vdc Version: 1.0

Global unforcing

RUN

Inputs

ERR IO DIAG...

2

Chan.

0

1

4

5

2

3

6

7

Symbol

0

0

0

0

0

0

0

0

State Error

DIAG...

DIAG...

DIAG...

DIAG...

DIAG...

DIAG...

DIAG...

DIAG...

Channel control

Forcing

F4 Force to 0

F5 Force to 1

F6 Unforce x

306

35013154.02 07/2208

Elements and functions

Fipio Debugging

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

Address Zone

1 common

2 specific

Function

See (See : PL7 Micro/Junior/Pro ; Communication applications

; Volume 1).

is used to access device debugging or device adjustment parameters.

The accessible parameters are device type functions.

Specific parameters

For input/output type modules, the specific zone displays the value and state of each of the module channels in real time and provides access to the commands from one channel.

For the other module types, the specific zone displays the bus management periodic exchange data.

35013154.02 07/2208

307

Fipio Debugging

308

35013154.02 07/2208

Fipio communication diagnostics

22

Introduction

Subject of this

Chapter

What's in this

Chapter?

This Chapter describes the Diagnostics process during set-up of Fipio communication.

This chapter contains the following topics:

Topic

Diagnostics mode

How to access the FIPIO bus monitoring screen

Diagnostics screen: FIPIO bus monitoring

How to access the device monitoring screen

Diagnostics screens: device monitoring

How to access the monitoring screen for one device

Diagnostics screen: single device monitoring

How to access the communication error history screen

Diagnostics screen: communication error history

Page

310

311

312

314

315

317

318

320

321

35013154.02 07/2208

309

Fipio Diagnostics

Diagnostics mode

Introduction In online mode it is possible to perform general diagnostics on the bus errors and device faults.

This diagnostic is possible by using screens available in the PL7 or the bits and system words managed by the application software.

Two modes are available: z z

FIPIO bus monitoring, device monitoring with or without a fault history.

Communication counters

Every configured connection point (including connection points 0 and 63) has a report variable. This variable contains the communication counter and performance values.

This variable has: z z z the activity counters numbered from 16#00 to 16#20 and standardized as

WORLDFIP, the error counters numbered from 16#21 to 16#7F and standardized as

WORLDFIP, the manufacturer counters numbered 16#80 to 16#FF these counters are not standardized as WORLDFIP.

The error counters change when there are communication errors on the FIPIO bus.

Diagnostics screens

Four screens display the status of the various counters and thus the communication errors: z z z z

The FIPIO bus monitoring screen provides a global view of the FIPIO bus, it displays the communication errors on the whole bus.

The Device monitoring screen provides a synthesis per connection point; it features all the connection points and indicates the status of the error counters per connection point.

The Device monitoring at connection point n screen shows all the counters and their status at a given connection point.

The Communication fault history screen is a fault history, which dates and retains the fault counter statuses to provide a trace.

Only one screen of each type can be open (one per connection point for the third type). If you try to open a screen which is already open, it will appear instantaneously.

310

35013154.02 07/2208

Fipio Diagnostics

How to access the FIPIO bus monitoring screen

Introduction

Procedure

This operation describes how to access the FIPIO bus monitoring screen. It only applies to online mode.

The following table shows the procedure:

Step

1

2

3

4

Action

Connect with the manager PLC.

Access the hardware configuration screen

Double click on the FIPIO connector.

Right click on the screen background.

5

Result : a contextual menu appears.

Fipio bus monitoring

Device monitoring

Fipio bus properties

Select the FIPIO bus monitoring command.

35013154.02 07/2208

311

Fipio Diagnostics

Diagnostics screen: FIPIO bus monitoring

Introduction

Illustration

This screen gives the user a global view of the bus and indicates the communication faults on the bus.

The screen has a list of all the bus communication error counters and indicates their status.

The screen dedicated to devices looks like this:

Fipio bus monitoring

Counter Label

34

35

36

37

39

2F

30

32

33

2B

2C

2D

2E

21

22

23

24

Channel 1 No Echo fault

Channel 1 Hyper current fault

Channel 1 Hypo current fault

Channel 1 Cross talk fault

Frame fragment fault

FCS fault

Frame length fault

Pierced frame fault

Coding fault

Overrun fault

Non identified frame type fault

Message recept queue full fault

Message recept queue full fault

Incorrect ADPU length fault

Received APDU type fault

Elementary cycle time exceed

Underrun fault

Elements and functions

Each line has: z z z an icon representing the state of the error counter (the reference state being the state at screen opening): z white for normal state, z red for a faulty counter having changed since the reference state, the hexadecimal counter number, the counter labels (given by the WORLDFIP standard).

312

35013154.02 07/2208

Fipio Diagnostics

Diagnostics On screen opening or on reset request, the report variables from all the connection points are read by a cyclic communication (one per second).

The counter values from each report variable are stored to create a reference state.

The time between reading and rereading the same variable is equal to the number of configured devices + 2 (0 and 63) in seconds.

As soon as the error counter value becomes different from its reference value, the counter icon goes red, regardless of the connection point. Reading the counter labels provides the type of error detected.

Example

Counter 21 goes red. This means that at least one counter 21 from all the counter

21s has changed.

Bus monitoring via the application

In PL7, the %SW150 and %SW151 system words indicate the number of frames sent and received by the channel manager.

If one of these two counters stops, it indicates that the FIPIO channel manager function has stopped.

The user is made aware of this stop in the configuration screen in online mode, when the background of connection point 0 goes red.

How to reset the reference state

The following procedure shows how to reset the reference state

Step

1

Action

Right click on the screen background.

2

Result : a contextual menu appears.

Reset

Select the Reset command.

35013154.02 07/2208

313

Fipio Diagnostics

How to access the device monitoring screen

Introduction

Procedure

This operation describes how to access the FIPIO bus device monitoring screen. It only applies to online mode.

The following table shows the procedure:

Step

1

2

3

4

Action

Connect with the manager PLC.

Access the hardware configuration screen

Double click on the FIPIO connector.

Right click on the screen background.

5

Result : a contextual menu appears.

Fipio bus monitoring

Device monitoring

Fipio bus properties

Select the Device monitoring command.

314

35013154.02 07/2208

Fipio Diagnostics

Diagnostics screens: device monitoring

Introduction

Illustration

This screen is used to access the monitoring of all the configured devices.

The screen has a list of all the configured connection points as well as points 0 and

63.

The screen dedicated to devices looks like this:

Monitoring of …

21

22

24

26

13

15

17

20

27

30

4

6

7

10

2

3

0

1

55

56

63

78

39

40

53

54

79

80

35

36

37

38

31

32

33

34

93

94

95

96

89

90

91

92

97

100

85

86

87

88

81

82

83

84

116

124

125

126

127

110

111

112

114

106

107

108

109

101

103

104

105

Elements and functions

The following elements are associated with each connection point: z z one icon showing: z whether the connection point needs to be monitored. If the box is checked, the z device is monitored.

whether the connection point is faulty. The icon goes red if an error is detected.

the connection point number.

35013154.02 07/2208

315

Fipio Diagnostics

Diagnostics

How to disable device monitoring

On screen opening or on reset request, the report variables from all the connection points are read by a cyclic communication (one per second).

The counter values from each report variable are stored to create a reference state.

The time between reading and rereading the same variable is equal to the number of configured devices + 2 (0 and 63) in seconds.

A connection point is considered faulty if the value of one of the error counters has changed since the reference state. When the point is faulty, the icon turns red.

Diagnostics are only sent back if there is a communication between the bus manager and the faulty connection point. Errors correspond to the WORLDFIP standard defined error counters.

The following procedure describes how to disable the device monitoring on the bus.

Step

1

Action

Click on the checkbox belonging to the connection point to be disabled.

Result :

The box is no longer checked. In this case this connection’s report variable is no longer read and its reference state is reset.

How to reset the reference state

The following procedure shows how to reset the reference state

Step

1

Action

Right click on the screen background.

2

Result : a contextual menu appears.

Device monitoring

Communication errors log

Monitoring

Reset

Select the Reset command.

316

35013154.02 07/2208

Fipio Diagnostics

How to access the monitoring screen for one device

Introduction

Procedure

This operation describes how to access the monitoring screen for a single FIPIO bus device and how to display its error counters.

It only applies to online mode.

The following table shows the procedure:

Step

1

2

Action

Access the Device monitoring screen.

Select the connection point number to be accessed.

3

4

Result : the number is highlighted.

Right click on the screen background.

Result : a contextual menu appears.

Device monitoring

Communication errors log

Monitoring

Reset

Select the Single device monitoring command.

35013154.02 07/2208

317

Fipio Diagnostics

Diagnostics screen: single device monitoring

Introduction

Illustration

This screen is used to display the status details of all the counters from a particular connection point.

It features all three zones corresponding to each type of counter: z z z activity, error, manufacturer

The screen dedicated to devices looks like this:

Device Monitoring at Connection Point 2

Activity counter

21

22

23

Initial value

6E34

72D8

0000

Previous value

6C8D

7114

0000

Current value

71B5

7673

0000

Label

Counter frames response received

Counter frames response returned

Fast aperiodic specified requests

Activity counter

2B

2C

2D

2E

21

22

23

24

2F

30

35

39

Initial value Previous value

0000

0000

0000

0000

0000

0000

0000

0000

0000

0000

0000

0000

0000

0000

0000

0000

007E

0000

0000

0060

0000

0000

0000

0000

Current value

0000

0000

0000

0000

007e

0000

0000

0060

0000

0000

0000

0000

Label

Channel 1 No Echo fault

Channel 1 Hyper current fault

Channel 1 Hypo current fault

Channel 1 Cross talk fault

Frame fragment fault

FCS fault

Frame length fault

Pierced frame fault

Coding fault

Overrun fault

Incorrect ADPU length fault

Underrun fault

Activity counter

80

Initial value Previous value

0001 0000

Current value

0000

Label

Counter not listed

318

35013154.02 07/2208

Elements and functions

Fipio Diagnostics

The following elements are associated with each counter: z z z z z z one icon indicating the state of the counter since the reference state: z z white: no change, green: change in the activity or manufacturer counters, z red: change in the error counters (the current value is different from the reference state).

the hexadecimal counter number, its hexadecimal reference value, its hexadecimal value during the last read, its current hexadecimal value, its label according to the WORLDFIP standard or the Counter not listed label for the manufacturer part.

Diagnostics On screen opening or on reset request, the report variables from all the connection points are read by a cyclic communication (one per second).

The counter values from each report variable are stored to create a reference state.

A connection point is considered faulty if the value of one of the error counters has changed since the reference state. When the point is faulty, the icon turns red.

Diagnostics are only sent back if there is a communication between the bus manager and the faulty connection point. Errors correspond to the WORLDFIP standard defined error counters.

How to reset the reference state

The following procedure shows how to reset the reference state

Step

1

Action

Right click on the screen background.

2

Result : a contextual menu appears.

Reset

Select the Reset command.

35013154.02 07/2208

319

Fipio Diagnostics

How to access the communication error history screen

Introduction

Procedure

This operation describes how to access the FIPIO bus communication error history screen.

It only applies to online mode.

The following table shows the procedure:

Step

1

2

Action

Access the Device monitoring screen.

Right click on the screen background.

Result : a contextual menu appears.

Device Monitoring

Communication errors history

Monitoring

Reset

3 Select the Communication error history command.

320

35013154.02 07/2208

Fipio Diagnostics

Diagnostics screen: communication error history

Introduction

Illustration

This screen has a list of the communication errors from the connection points (plus

0 and 63), which are configured and declared monitored in the Device monitoring screen.

The screen dedicated to devices looks like this:

Communication errors history

Date Time Connection point

14/10/1998 14:39:49 2

14/10/1998 14:39:49 2

Counter

2B

2E

Value Label

007E Frame fragment fault

0060 Pierced frame fault

Elements and functions

How to pause/ resume the history

Every time an error counter from a connection point changes, a line is added. It features: z z z z z the current date and time of the programming terminal, the decimal connection point number, the hexadecimal error counter number, the hexadecimal counter value, the counter label according to the WORLDFIP standard.

This command is used to stop and resume screen updating.

Step

1

Action

Right click on the screen background.

2

Result : a contextual menu appears.

Pause History

Reset history

Clear history

Cpy

Sort

Automatic stop of history

Reset

Select the Pause history command or Resume history command.

35013154.02 07/2208

321

Fipio Diagnostics

How to clear history

This command can be accessed if the Pause history function is confirmed. It is used to delete all the lines from the screen.

Step

1

2

Action

Access the contextual menu.

Select the Clear history command

How to sort the history

This command can be accessed if the Pause history function is confirmed. It is used to sort all the history lines either by date and time or by connection point or counter.

Step

1

2

Action

Access the contextual menu.

Select the Sort

→ by date and time command.

How to copy the history

This command can be accessed if the Pause history function is confirmed. It is used to copy lines selected in text format onto the clipboard.

Step

1

2

Action

Access the contextual menu.

Select the Sort

→ by date and time command.

How to automatically stop the history

When this function is selected, it is used to stop the history when it has reached a maximum number of lines (4000 lines). A message pops up to indicate that this stop has occurred. When the function is not selected and when the maximum number has been reached, new added lines replace the first ones (turning mode).

Step

1

2

Action

Access the contextual menu.

Select the Automatic history stop command

Result : selecting the command checks the function.

How to reset the reference state

The following procedure shows how to reset the reference state

Step

1

2

Action

Access the contextual menu.

Select the Reset command.

322

35013154.02 07/2208

Language objects associated with

Fipio communication

23

Introduction

Subject of this

Section

What's in this

Chapter?

This Chapter introduces language objects associated with Fipio communication.

This chapter contains the following topics:

Topic

Language objects in implicit exchange

Language object for explicit exchange

Explicit exchange management and reports

Page

324

325

328

323

35013154.02 07/2208

Fipio language objects

Language objects in implicit exchange

Introduction

Bit objects

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

(PL7 Micro/Junior/Pro ; Communication applications ; Volume 1)

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

Object (1) Function

%I\p.2.c\0.MOD.ERR

Module error bit

%I\p.2.c\m.i.ERR

%I\p.2.c\m.i.r

%Q\p.2.c\m.i.r

Channel error bit

Bit exchange

Bit exchange

Meaning

This bit set to 1, indicates a module error (at least one of the channels is faulty,…)

This bit set at 1 indicates a faulty channel.

Image of the module’s physical inputs (input acquisition)

Image of the module’s physical outputs

(output command)

Key

(1) z z z z p.2.c\m.i.r Address p: corresponds to the processor’s slot c: corresponds to the connection point number m: corresponds to the module position number i: corresponds to the channel number

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

Object (1) Function

%IW\p.2.c\m.i.r

Word exchange

%QW\p.2.c\m.i.

r

Word exchange

Meaning

Image of the module’s physical inputs (input acquisition)

Image of the module’s physical outputs (output command)

Key

(1) z z z p.2.c\m.i.r Address z p: corresponds to the processor’s slot c: corresponds to the connection point number m: corresponds to the module position number i: corresponds to the channel number

324

35013154.02 07/2208

Fipio language objects

Language object for explicit exchange

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

: PL7 Micro/Junior/Pro ; Communication applications ; Volume 1)

35013154.02 07/2208

325

Fipio language objects

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

Object (1)

%MW\p.2.c\0.i.2

%MW\p.2.c\1.i.2

Function

%MW\p.2.c\0.MOD.2 Module status

Meaning

Least significant byte: corresponds to standard.

z z z z z z z z x0 = 1: internal error x1 = 1: functional error x2 = 1: terminal block fault x3 = 1: standard module self-testing x4 = 1: reserved (= 0) x5 = 1: configuration error x6 = 1: missing module x7 = 1: extension module error

Extension module channel status z z z z z z z z

Most significant byte: corresponds to extension x8 = 1: internal error x9 = 1: functional error x10 = 1: terminal block fault x11 = 1: extension module self-testing x12 = 1: reserved (= 0) x13 = 1: configuration error x14 = 1: missing module x15 = 1: reserved (= 0)

Standard module channel status z z z z z z z z

Least significant byte: corresponding to standard x0 = 1: external error 4 x1 = 1: external error 3 x2 = 1: external error 2 x3 = 1: external error 1 x4 = 1: internal error x5 = 1: hardware configuration error x6 = 1: communication error x7 = 1: application error z z z z z z z z

Least significant byte: corresponding to extension x0 = 1: external error 4 x1 = 1: external error 3 x2 = 1: external error 2 x3 = 1: external error 1 x4 = 1: internal error x5 = 1: hardware configuration error x6 = 1: communication error x7 = 1: application error

Key

326

35013154.02 07/2208

Example

Object (1)

(1)

Fipio language objects

Function Meaning z z z p.2.c\m.i.r Address z p: corresponds to the processor’s slot c: corresponds to the connection point number m: corresponds to the module position number i: corresponds to the channel number

Note: for each connected device, refer to the corresponding documentation for details of task status words.

The example focuses on the channel level diagnostics for a TBX TOR device:

Object

%MW\p.2.c\0.i.2

%MW\p.2.c\1.i.2

Function

Channel status

Meaning z z

Least significant byte: z z z z z x0 = 1: tripped output x1 = 1: globally tripped x2 = 1: terminal block fault x3 = 1: external supply fault x4 = 1: channel configured but not physically present z x5 = 1: channel present but different from that configured x6 = 1: communication error x7 = 1: application error

35013154.02 07/2208

327

Fipio language objects

Explicit exchange management and reports

Introduction

Word objects

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

: PL7 Micro/Junior/Pro ; Communication applications ; Volume 1)

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

Object (1)

%MW\p.2.c\

0.MOD.0

%MW\p.2.c\

0.MOD.0

%MW\p.2.c\

0.i.0

%MW\p.2.c\

0.i.1

Function

Module exchanges in progress

Module report

Channel exchanges in progress

Channel report

Meaning z z z x0 = 1: reading status in progress x1 = 1: sending of command parameters to the communication module x2 = 1: sending of adjustment parameters to the communication module z z x1 = 0: command parameters received and accepted by the module x2 = 0: adjustment parameters received and accepted by the module z z z z z x0 = 1: reading status in progress x1 = 1: sending of command parameters in progress x2 = 1: sending of adjustment parameters in progress x3 to x14: reserved (= 0) x15 = 1: sending of configuration parameters in progress z z z z z x0 = 0: status reading OK x1 = 0: command parameters received and accepted by the device x2 = 0: adjustment parameters received and accepted by the device x3 to x14: reserved (= 0) x15 = 0: configuration parameters received and accepted by the device

Key

(1) z z z z p.2.c\m.i.r Address p: corresponds to the processor’s slot c: corresponds to the connection point number m: corresponds to the module position number i: corresponds to the channel number

328

35013154.02 07/2208

Fipio communication standard profiles

24

Introduction

Subject of this

Chapter

What's in this

Chapter?

This chapter introduces devices compatible with the standard communication profiles for use with the Fipio bus and its services.

This chapter contains the following sections:

Section

24.1

24.2

24.3

24.4

Topic

Introduction to standard Fipio communication profiles

Configuration of the Fipio bus standard profiles

Debugging the Fipio bus standard profiles

Language objects associated with the Fipio bus standard profiles

Page

330

336

342

347

35013154.02 07/2208

329

Standard profiles

24.1

Introduction to standard Fipio communication profiles

Introduction

Aim of this

Section

What's in this

Section?

This Section provides a summary description of the standard profiles of the Fipio bus and its associated services.

This section contains the following topics:

Topic

Standard profiles: general

Designation of a standard profile

List of the standard profiles proposed in catalog by PL7

Page

331

332

334

330

35013154.02 07/2208

Standard profiles

Standard profiles: general

Introduction A device conforming to the standard Fipio communication profiles can be linked to a Fipio bus, to exchange the input/output variables.

Data exchanges with devices are used to: z z z exchange inputs/outputs, write configuration or adjustment parameters, diagnose a connected device.

There are three types of standard profile: z z z

FRDP: Fipio Reduced Device Profile

FSDP: Fipio Simple Device Profile

FEDP: Fipio Extended Device Profile

Volume of data exchanged

The device profiles, which conform to a standard profile are a function of the number of inputs and outputs to be exchanged.

The table below describes the words managed by the different standard profiles:

Profile

Process data input acquisition output control

Configuration (optional)

Adjust (optional)

Commands specific command

Diagnostics input validity specific status

FRD

-

-

2 words

2 words

-

1 byte

-

FSD

8 words

8 words

16 words

32 words

-

1 byte

-

FED

32 words

32 words

30 words

30 words

8 words

1 byte

8 words

35013154.02 07/2208

331

Standard profiles

Designation of a standard profile

Introduction

How the reference is made up

FRD profile

A device conforming to the standard Fipio communication profiles is defined by assigning one of the STD_P family standard profiles to it at the Fipio connection point.

The family consists of a standard profile reference list.

Each reference is made up of several significant codes: z z z z the standard profile used: z FRD z z

FSD

FED the connected device structure: z C: Compact z M: Modular the number and type of objects exchanged with the manager: corresponds to the input/output exchange volume in 16 bit words z 2 words z z

8 words

32 words

P: corresponds to the presence of configuration or adjustment parameters

(chosen).

the reference is made up of the following:

Profile

FRD

Structure

C

Number of objects Parameter

2 -

P

FSD profile the reference is made up of the following:

Profile

FSD

Structure

C

M

Number of objects Parameter

8 -

P

332

35013154.02 07/2208

FED profile

Standard profiles the reference is made up of the following:

Profile

FED

Structure

C

M

Number of objects Parameter

32 -

P

35013154.02 07/2208

333

Standard profiles

List of the standard profiles proposed in catalog by PL7

Introduction During FIPIO configuration, you can connect standard profiles in accordance with device type.

Compact device The following table gives a list of the compact standard profiles:

Reference

FRD C2

FRD C2 P

FSD C8

Designation

EQP RED CMPCT 2M

EQP STD CMPCT 2M P

STD DEV CMPCT 2W P

Language interface

32 bits %I, 32 bits %Q

32 bits %I, 32 bits %Q

16 configuration words, 32 adjustment words

8 words %IW, 8 words %QW

FSD C8 P

FED C32

EQP STD CMPCT 8M

STD DEV CMPCT 8W

EQP STD CMPCT 8M P

STD DEV CMPCT 8W P

8 words %IW, 8 words %QW

16 configuration words, 32 adjustment words

32 words %IW, 32 words %QW

FED C32 P

EQP STD CMPCT 32M

STD DEV CMPCT 32W

EQP STD CMPCT 32M P

STD DEV CMPCT 328W P

32 words %IW, 32 words %QW

30 configuration words, 30 adjustment words

Modular device The following table gives a list of the modular standard profiles:

Reference

FSD M8

FSD M8 P

FED M32

FED M32 P

Designation

EQP STD MOD 8M

STD DEV MOD 8W

EQP STD MOD 8M P

STD DEV MOD 8W P

Language interface

8 words %IW, 8 words %QW

8 words %IW, 8 words %QW

16 configuration words, 32 adjustment words

32 words %IW, 32 words %QW EQP STD MOD 32M

EXTENDED DEV MOD 32W

EQP STD MOD 32M P

EXTENDED DEV MOD

328W P

32 words %IW, 32 words %QW

30 configuration words, 30 adjustment words

334

35013154.02 07/2208

Momentum

Device

Standard profiles

In the Momentum family, where an analog input/output base is not available in the catalog, it is then necessary to select one of the OTHER_FxD_[P] standard profile references.

The choice criteria are as follows:

Reference

OTHER_FRD

OTHER_FRDP

OTHER_FSD

OTHER_FSDP

OTHER_FED

OTHER_FEDP

Language interface

32 bits %I, 32 bits %Q

8 words %IW, 8 words %QW

32 words %IW, 32 words %QW

Communicator The communicators are as follows:

Reference

OTHER

TSX FPP10

170 FNT 110 01

Language interface other communication module

FIPIO TSX communication module

FIPIO TSX communication module for the TS Momentum

35013154.02 07/2208

335

Standard profiles

24.2

Configuration of the Fipio bus standard profiles

Introduction

Aim of this

Section

What's in this

Section?

This Section introduces the configuration principles for the Fipio bus standard profiles.

This section contains the following topics:

Topic

Configuration screen of a standard profile

How to modify the parameters of a standard profile

Adjustment mode

Page

337

339

341

336

35013154.02 07/2208

Standard profiles

Configuration screen of a standard profile

Introduction

Illustration

The configuration screen of a standard profile reuses the parameters of all other devices configured on the FIPIO bus (see Configuration screen of an FIPIO device).

However, some parameters are exclusive to it. In the rest of this document, only the part specific to the standard profiles is explained.

The screen dedicated to the device looks like this:

1

2

3

4

FSD M8 P [FIPIO18 MODULE 0]

Configuration

Designation: EQP STD MOD 8MP

Channel 0

Local configuration

Task: MAST

Default configuration

Parameter

%KW\0.2.18\0.0.0

%KW\0.2.18\0.0.1

%KW\0.2.18\0.0.2

%KW\0.2.18\0.0.3

%KW\0.2.18\0.0.4

%KW\0.2.18\0.0.5

%KW\0.2.18\0.0.6

%KW\0.2.18\0.0.7

Symbol

Base

Decimal

Value

0

0

16#8040

16#0

0

0

0

16#4

35013154.02 07/2208

337

Standard profiles

Elements and functions

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

2

3

Address Description

1 The Local configuration check box is only available for the FSD C8 P and FSD

M8 P profiles.

If the box is checked, the configuration and adjustment parameters are not sent to the device connected to the bus (to ensure rapid start-up of the device). The device starts up or initializes with its own parameters.

In the configuration screen, if the box is checked, the parameters of the channel cannot be accessed.

4

The Default configuration button is used to return to the original configuration.

The Standard is used to select the display standard of the value of the selected word.

z z

Three types are available: z Decimal

Hexadecimal

Binary

This list displays the configuration words %KW or the adjustment words %MW which correspond to the registered standard profile.

For each word, there is an associated Symbol and a Value .

338

35013154.02 07/2208

Standard profiles

How to modify the parameters of a standard profile

Introduction

How to modify the display standard

The following procedures apply to the configuration or adjustment parameters.

The following procedure shows the selection of the display standard. For the example, the chosen standard is binary.

Step

1

2

Action

Select the cell Value of the word to be modified.

Select from the dropdown menu Standard

→

Binary .

Result : the cell displays 2#1011 .

How to enter a value on the keyboard

The following procedure shows how to key a value into a cell.

Step

1

2

Action

Select the Value cell of the word to be modified.

How to enter a value on the keyboard.

Note:

Keyboard entry depends on the display standard.

35013154.02 07/2208

339

Standard profiles

How to enter a value in binary form

The following procedure shows how to enter a value in binary form.

Step

1

Action

Double click on the Value cell of the word to be modified.

Result : the following window appears.

Property of: %KW\0.2.5\0.0.7

2

3

09:

08:

07:

06:

05:

04:

03:

02:

01:

00:

15:

14:

Bits of word

13:

12:

11:

10:

Select the bits which must be set to 1.

Close the window Property of: ...

by selecting the cross in the left-hand corner.

Result : The closure validates the entered value and displays it according to the standard.

340

35013154.02 07/2208

Standard profiles

Adjustment mode

Introduction

Illustration

Adjustment mode is accessed from the hardware configuration menu of the application browser. The principal is the same as for configuration mode, and the adjustment words are %MW.

There are 32 possible words for the FSD and FRD profiles and 30 words for the FED profiles.

The adjustment screen dedicated to the device looks like this:

FSD C8 P [FIPIO5 MODULE 0]

Configuration

Designation: EQP STD CMPCT 8MP

Channel 0

Local configuration

Task: MAST

Default configuration

Parameter

%KW\0.2.5\0.0.0

%KW\0.2.5\0.0.1

%KW\0.2.5\0.0.2

%KW\0.2.5\0.0.3

%KW\0.2.5\0.0.4

%KW\0.2.5\0.0.5

%KW\0.2.5\0.0.6

%KW\0.2.5\0.0.7

Base

Decimal

Symbol

0

0

0

0

0

0

0

0

Value

35013154.02 07/2208

341

Standard profiles

24.3

Debugging the Fipio bus standard profiles

Introduction

Aim of this

Section

What's in this

Section?

This Section introduces the debugging principles Fipio bus standard profiles.

This section contains the following topics:

Topic

Debugging screen of a standard profile

How to modify the debugging parameters of a standard profile

Page

343

345

342

35013154.02 07/2208

Standard profiles

Debugging screen of a standard profile

Introduction The debugging screen of a standard profile reuses the parameters of all other devices configured on the FIPIO bus (see Debugging screen of an FIPIO device).

However, some parameters are exclusive to it. In the rest of this document, only the part specific to the standard profiles is explained.

Note: The adjustment parameters cannot be accessed.

Illustration The screen dedicated to the device looks like this:

FED C32 P [FIPIO4 MODULE 0]

Debugging

Designation: EQP STD CMPCT 32MP Version: 1.0

RUN ERR IO

1

2

3

Channel 0

Variables

Outputs

Reference

%QW\0.2.4\0.0.0

%QW\0.2.4\0.0.1

%QW\0.2.4\0.0.2

%QW\0.2.4\0.0.3

%QW\0.2.4\0.0.4

%QW\0.2.4\0.0.5

%QW\0.2.4\0.0.6

%QW\0.2.4\0.0.7

%QW\0.2.4\0.0.8

%QW\0.2.4\0.0.13

%QW\0.2.4\0.0.14

%QW\0.2.4\0.0.15

DIAG...

Task: MAST

Label

Base

Hexadecimal

Symbol Value

16#1

16#30

16#24

16#C00

16#0

16#0

16#3C10

16#30

16#0

16#0

16#0

16#0

DIAG...

35013154.02 07/2208

343

Standard profiles

Elements and functions

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

Address Description

1

2

This dropdown list allows the choice of periodic exchange: z z of the input parts, of the output parts.

The Standard window is used to select the display standard of the value of the z z z selected word.

Three types are available:

Decimal

Hexadecimal

Binary

3 This list displays the input words %IW or the output words %QW which correspond to the registered standard profile.

For each word there is an associated Wording , a Symbol and a Value .

344

35013154.02 07/2208

Standard profiles

How to modify the debugging parameters of a standard profile

Introduction

How to modify the display standard

The following procedures apply to the debugging parameters.

The following procedure shows the selection of the display standard. For the example, the chosen standard is binary.

Step

1

2

Action

Select the Value cell of the word to be modified.

Select from the dropdown menu Standard

→

Binary .

Result : the cell displays 2#1011 .

How to enter a value on the keyboard

The following procedure shows how to key a value into a cell.

Step

1

2

Action

Select the Value cell of the word to be modified.

How to enter a value on the keyboard.

Note:

Keyboard entry depends on the display standard.

35013154.02 07/2208

345

Standard profiles

How to enter a value in binary form

The following procedure shows how to enter a value in binary form. It is only valid for the output parts.

Step

1

Action

Double click on the Value cell of the word to be modified.

Result : the following window appears.

Property of: %KW\0.2.5\0.0.7

09:

08:

07:

06:

05:

04:

03:

02:

01:

00:

15:

14:

Bits of word

13:

12:

11:

10:

2

3

Select the bits which must be set to 1.

Close the window Property of: ...

by selecting the cross in the left-hand corner.

Result : The closure validates the entered value and displays it according to the standard.

346

35013154.02 07/2208

24.4

Standard profiles

Language objects associated with the Fipio bus standard profiles

Introduction

Aim of this

Section

What's in this

Section?

This section introduces the language objects associated with the Fipio bus standard profiles.

This section contains the following topics:

Topic

Summary of the objects which can be accessed via the standard profiles

Language objects in implicit exchange

Language object for explicit exchange

Language objects associated with configuration

Page

348

351

353

356

35013154.02 07/2208

347

Standard profiles

Summary of the objects which can be accessed via the standard profiles

Introduction

FRD profile

The following tables show the language objects associated with each profile contained in the PL7 catalogue.

The following table relates to the FRD profiles

Input acquisition

Output command

Configuration words

FRD C2

%I\p.2.c\0.0

%I\p.2.c\0.31

%Q\p.2.c\0.0

%Q\p.2.c\0.31

-

Status: management of exchanges

Exchange report

Status: channel standard

Validity of inputs

Status: channel specific

Command words

Adjustment words

%MW\p.2.c\0.i.0

-

-

%MW\p.2.c\0.i.1

%MW\p.2.c\0.i.2

-

%MW\p.2.c\0.i.3

FRD C2 P

%I\p.2.c\0.0

%I\p.2.c\0.31

%Q\p.2.c\0.0

%Q\p.2.c\0.31

%KW\p.2.c\0.i.0

%KW\p.2.c\0.i.15

%MW\p.2.c\0.i.0

%MW\p.2.c\0.i.1

%MW\p.2.c\0.i.2

%MW\p.2.c\0.i.3

-

-

%MW\p.2.c\0.i.4

%MW\p.2.c\0.i.35

348

35013154.02 07/2208

FSD profile The following table relates to the FSD profiles

Input acquisition

Output command

Configuration words

FSD C/M8

%IW\p.2.c\0.0

%IW\p.2.c\0.7

%QW\p.2.c\0.0

%QW\p.2.c\0.7

-

Status: management of exchanges

Exchange report

Status: channel standard

Validity of inputs

Status: channel specific

Command words

Adjustment words

%MW\p.2.c\0.i.0

%MW\p.2.c\0.i.1

%MW\p.2.c\0.i.2

%MW\p.2.c\0.i.3

-

-

-

Standard profiles

FSD C/M8 P

%IW\p.2.c\0.0

%IW\p.2.c\0.7

%QW\p.2.c\0.0

%QW\p.2.c\0.7

%KW\p.2.c\0.i.0

%KW\p.2.c\0.i.15

%MW\p.2.c\0.i.0

%MW\p.2.c\0.i.1

%MW\p.2.c\0.i.2

%MW\p.2.c\0.i.3

-

-

%MW\p.2.c\0.i.4

%MW\p.2.c\0.i.35

35013154.02 07/2208

349

Standard profiles

FED profile The following table relates to the FED profiles

Input acquisition

Output command

Configuration words

FED C/M32

%IW\p.2.c\0.0

%IW\p.2.c\0.31

%QW\p.2.c\0.0

%QW\p.2.c\0.31

-

Status: management of exchanges

Exchange report

Status: channel standard

Validity of inputs

Status: channel specific

Command words

Adjustment words

%MW\p.2.c\0.i.0

%MW\p.2.c\0.i.1

%MW\p.2.c\0.i.2

%MW\p.2.c\0.i.3

%MW\p.2.c\0.i.4

%MW\p.2.c\0.i.11

%MW\p.2.c\0.i.12

%MW\p.2.c\0.i.19

-

FED C/M32 P

%IW\p.2.c\0.0

%IW\p.2.c\0.31

%QW\p.2.c\0.0

%QW\p.2.c\0.31

%KW\p.2.c\0.i.0

%KW\p.2.c\0.i.29

%MW\p.2.c\0.i.0

%MW\p.2.c\0.i.1

%MW\p.2.c\0.i.2

%MW\p.2.c\0.i.3

%MW\p.2.c\0.i.4

%MW\p.2.c\0.i.11

%MW\p.2.c\0.i.12

%MW\p.2.c\0.i.19

%MW\p.2.c\0.i.20

%MW\p.2.c\0.i.49

350

35013154.02 07/2208

Standard profiles

Language objects in implicit exchange

Introduction

Bit objects

This page describes all the language objects for implicit exchange associated with the standard profiles for FIPIO communication that can be displayed or modified by the application program. (PL7 Micro/Junior/Pro ; Communication applications ;

Volume 1)

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

Object (1)

%I\p.2.c\0.MOD

.ERR

Function

Module error bit

%I\p.2.c\m.i.ER

R

%I\p.2.c\0.0 to

%I\p.2.c\0.31

%Q\p.2.c\0.0 to

%Q\p.2.c\0.31

Channel error bit

Bit exchange

Bit exchange

Meaning

This bit set to 1, indicates a module error (at least one of the channels is faulty,…)

This bit set at 1 indicates a faulty channel.

Acquiring input bits for FRD profiles

Acquiring output bits for FRD profiles

Key

(1) p.2.c Address z z p: corresponds to the processor’s slot c: corresponds to the connection point number

35013154.02 07/2208

351

Standard profiles

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

Object (1)

%IW\p.2.c\0.0.

0 to

%IW\p.2.c\0.0.

7

Function

FSD word exchange

%QW\p.2.c\0.0.

0 to

%QW\p.2.c\0.0.

7

%IW\p.2.c\0.0.

0 to

%IW\p.2.c\0.0.

31

FSD word exchange

FED word exchange

%QW\p.2.c\0.0.

0 to

%QW\p.2.c\0.0.

31

FED word exchange

Meaning

Acquiring input words for FSD profiles

Acquiring output words for FSD profiles

Acquiring input words for FED profiles

Acquiring output words for FED profiles

Key

(1) p.2.c\m.i.r Address z z z z p: corresponds to the processor’s slot c: corresponds to the connection point number m: corresponds to the module position number i: corresponds to the channel number

352

35013154.02 07/2208

Standard profiles

Language object for explicit exchange

Introduction This page describes all the language objects for explicit exchange associated with the standard profiles for FIPIO communication that can be displayed or modified by the application program. (See : PL7 Micro/Junior/Pro ; Communication applications

; Volume 1)

35013154.02 07/2208

353

Standard profiles

Word objects common to all the profiles

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

Object (1)

%MW\p.2.c\0.MO

D.2

Function

Module status

Meaning

Least significant byte: corresponds to standard.

z z z z z z z z x0 = 1: internal error x1 = 1: functional error x2 = 1: terminal block fault x3 = 1: standard module self-testing x4 = 1: reserved (= 0) x5 = 1: configuration error x6 = 1: missing module x7 = 1: extension module error z z z z z z z z

Most significant byte: corresponds to extension x8 = 1: internal error x9 = 1: functional error x10 = 1: terminal block fault x11 = 1: extension module self-testing x12 = 1: reserved (= 0) x13 = 1: configuration error x14 = 1: missing module x15 = 1: reserved (= 0)

%MW\p.2.c\0.i.2

Standard module channel status z z z z z z z z

Least significant byte: corresponding to standard x0 = 1: external error 4 x1 = 1: external error 3 x2 = 1: external error 2 x3 = 1: external error 1 x4 = 1: internal error x5 = 1: hardware configuration error x6 = 1: communication error x7 = 1: application error

%MW\p.2.c\0.i.3

Validity of inputs For FRD, FSD and FED profiles the least significant byte is specific to the connected device.

Refer to the documentation for the device.

Key

(1) z z z z p.2.c\m.i.r Address p: corresponds to the processor’s slot c: corresponds to the connection point number m: corresponds to the module position number i: corresponds to the channel number

354

35013154.02 07/2208

Standard profiles

Note: For each connected device, refer to the corresponding documentation for details of task status words.

Internal words for FRD and FSD profiles

The following table shows the internal words specific to FRD and FSD profiles:

Object

%MW\p.2.c\0.i.4

to

%MW\p.2.c\0.i.35

Function

Adjustment parameters

Meaning

32 specific adjustment words.

Parameters which can be accessed in read and write format via the WRITE_PARAM , READ_PARAM ,

SAVE_PARAM and RESTORE_PARAM functions.

Key

(1) p.2.c\m.i.r Address z z z z p: corresponds to the processor’s slot c: corresponds to the connection point number m: corresponds to the module position number i: corresponds to the channel number

Internal words for the FED profiles

The following table shows the internal words specific to the FED profiles:

Object

%MW\p.2.c\0.i.4

to

%MW\p.2.c\0.i.11

%MW\p.2.c\0.i.12

to

%MW\p.2.c\0.i.19

%MW\p.2.c\0.i.20

to

%MW\p.2.c\0.i.49

Function Meaning

Specific status 8 specific status words.

Parameters which can be accessed in read format via the READ_STATUS function.

Specific channel level command

8 specific command words.

Parameters which can be accessed in write format by the WRITE_CMD function.

Adjustment parameters

32 specific adjustment words.

Parameters which can be accessed in read and write format via the WRITE_PARAM , READ_PARAM ,

SAVE_PARAM and RESTORE_PARAM functions.

Key

(1) z z z z p.2.c\m.i.r Address p: corresponds to the processor’s slot c: corresponds to the connection point number m: corresponds to the module position number i: corresponds to the channel number

35013154.02 07/2208

355

Standard profiles

Language objects associated with configuration

Introduction

Internal constants

This page describes all the configuration language objects associated with the

FIPIO communication agents that can be displayed by the agent application program.

The following table describes the internal constants:

Object

%KW\p.2.c\

0.0.0 to

%KW\p.2.c\

0.15

%KW\p.2.c\

0.0.0 to

%KW\p.2.c\

0.29

Function

Configuration words at channel level

Configuration words at channel level

Meaning

They contain channel parameters set via the configuration editor for FRD and FSD profiles.

They contain channel parameters set via the configuration editor for FED profiles.

356

35013154.02 07/2208

Fipio Agent

25

Introduction

Subject of this

Chapter

What's in this

Chapter?

This Chapter introduces the Agent devices on the Fipio bus and its services.

This chapter contains the following sections:

Section

25.1

25.2

25.3

25.4

Topic

Introduction to Fipio Agents

Configuration of Fipio Agents

Debugging Fipio Agents

Language objects associated with the Fipio Agents

Page

358

366

369

370

35013154.02 07/2208

357

Fipio Agent

25.1

Introduction to Fipio Agents

Introduction

Aim of this

Section

What's in this

Section?

This section provides a summary description of the agents on the Fipio bus and their associated services.

This section contains the following topics:

Topic

FIPIO Agent: General

Periodic data exchange

Special cases

Communication from an FIPIO Agent

Page

359

360

362

364

358

35013154.02 07/2208

Fipio Agent

FIPIO Agent: General

Introduction The Micro or Premium PLCs, equipped with the PCMCIA TSX FPP 10 card on their built-in communication channel, are agents on the FIPIO bus.

The FIPIO function agent is used to perform two types of data exchange: z z periodic exchanges of information with the manager (shared variables type), aperiodic exchanges of messages with the manager, from CCX 17 devices or with other agents.

Note: this function is available with the TSX FPP 10 card, minimum version V1.8.

35013154.02 07/2208

359

Fipio Agent

Periodic data exchange

Introduction Each FIPIO Agent PLC uses 64 consecutive %MW words to exchange the periodic data. z z

The 32 first words are reserved for transmitting the information to the manager.

The 32 remaining words are reserved for receiving the information.

Note: the status %MW words and the command %MW are not significant.

360

35013154.02 07/2208

Fipio Agent

Viewing the exchanges

The following chart illustrates the exchanges between an FIPIO Agent and a

Premium manager.

TSX 57 FIPIO bus manager

1

TSX 57 Agent

Language view of the manager

%IW\0.2.1\0.0.0

%IW\0.2.1\0.0.15

%IW\0.2.1\0.0.16

%IW\0.2.1\0.0.31

%QW\0.2.1\0.0.0

%QW\0.2.1\0.0.15

%QW\0.2.1\0.0.16

%QW\0.2.1\0.0.31

2

3

TSX 37 Agent

%IW\0.2.4\0.0.0

%IW\0.2.4\0.0.15

%IW\0.2.4\0.0.16

%IW\0.2.4\0.0.31

%QW\0.2.4\0.0.0

%QW\0.2.4\0.0.15

%QW\0.2.4\0.0.16

%QW\0.2.4\0.0.31

Language view of the agent

%MW...

%MW...+31

%MW...+32

%MW...+63

%MW...

%MW...+31

%MW...+32

%MW...+63

4

35013154.02 07/2208

361

Fipio Agent

Special cases

Introduction A Premium PLC which is registered as an FIPIO Agent can communicate with a

TSX 47-107 or APRIL 5000 manager.

For these uses, an FIPIO Agent is registered on the bus by registering a standard profile to the connection point.

The registered standard profile is as follows: z z z

Device family: STD_P

Standard: FED M32

Communicator: TSX FPP 10

362

35013154.02 07/2208

Fipio Agent

Exchanges with a TSX 47-107

The following chart illustrates the exchanges between an FIPIO Agent and a

TSX 47-107 manager.

Language view of the agent

TSX 47-107 FIPIO bus manager

2

3

4

1

TSX 57 Agent

TSX 37 Agent

Language view of the manager

RIWA1,0,0

RIWA1,0,15

RIWB1,0,16

RIWB1,0,31

ROWA1,0,0

ROWA1,0,15

ROWB1,0,16

ROWB1,0,31

RIWA4,0,0

RIWA4,0,15

RIWB4,0,16

RIWB4,0,31

ROWA4,0,0

ROWA4,0,15

ROWB4,0,16

ROWB4,0,31

%MW...

%MW...+31

%MW...+32

%MW...+63

%MW...

%MW...+31

%MW...+32

%MW...+63

35013154.02 07/2208

363

Fipio Agent

Communication from an FIPIO Agent

Introduction

Addressing

A PLC registered as an FIPIO Agent can communicate: z z with the server of the bus manager, with the server of another FIPIO Agent.

The syntax of an address is as follows:

ADR#\0.1.4\SYS

The following table describes the addressing parameters:

Parameter

0.1.4

SYS

Description z z z

0: corresponds to the module sending the request

1: corresponds to the channel sending the request

4: corresponds to the destination connection point corresponds to the server address.

364

35013154.02 07/2208

Example

Fipio Agent

Example of access the system of the different PLCs

Manager

ADR#\1.1.0\SYS

Accessing the manager server

0

ADR#\0.1.1\SYS

Accessing the

FIPIO Agent 1 server

1

ADR#\0.1.4\SYS

Accessing the

FIPIO Agent 4 server

ADR#\0.1.4\SYS

Accessing the

FIPIO Agent 4 server 4

63

The FIPIO Agent PLC at address 1 reads 10 words in the FIPIO Agent PLC at address 4.

READ_VAR(ADR#\0.1.4\SYS, ‘%MW’, 0, 10, %MW10:10, %MW100:4)

35013154.02 07/2208

365

Fipio Agent

25.2

Configuration of Fipio Agents

Introduction

Aim of this

Section

What's in this

Section?

This Section introduces the configuration principles for Fipio Agents.

This section contains the following topics:

Topic

How to access the FIPIO Agent parameters via PCMCIA cards

FIPIO Agent configuration screen

Page

367

368

366

35013154.02 07/2208

Fipio Agent

How to access the FIPIO Agent parameters via PCMCIA cards

Introduction

How to access the link

The creation of an application setting up FIPIO Agents requires the configuration of the communication channel of the PLC registered as an FIPIO Agent.

This operation describes how to access the configuration parameters of the FIPIO

Agent link via the PCMCIA TSX FPP card for Micro/Premium PLCs.

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

Step

1

2

Action

Access the communication channel configuration screen.

From the dropdown menu, select the communication channel CHANNEL 1

Example

CHANNEL 1

CHANNEL 1

CHANNEL 1

(No PCMCIA submodule)

MAST

3 Select one of the following PCMCIA cards from the dropdown menu: z TSX FPP 10 PCMCIA CARD FIPIO

Example

CHANNEL 1

CHANNEL 1 (No PCMCIA submodule)

(Link not configured) MAST

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

35013154.02 07/2208

367

Fipio Agent

FIPIO Agent configuration screen

Introduction

Illustration

This screen, split into two areas, is used to register the communication channel and to configure the necessary parameters for a FIPIO Agent link.

The screen dedicated to communication looks like this:

1

TSX 3722 [POSITION 00.0..1]

Configuration

Designation: PROCESSOR 37222

CHANNEL 1

CHANNEL 1

FIPIO AGENT

TSX FPP 10 PCMCIA FIPIO CARD

MAST

2

Connection Point Address

Table Start Address %MW 0

1

Elements and functions

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

Address Zone

1 common

2 specific

Function

See (See : PL7 Micro/Junior/Pro ; Communication applications

; Volume 1).

is used to select and complete the following parameters: z z connection point address the beginning address of the table.

the beginning address of the table.

This parameter indicates the address of the table to be reserved for the periodic data exchanges between the bus manager and the FIPIO Agent.

The table has 64 words: z z

32 words for the inputs (%IW\p.2.c\m.i.r),

32 words for the outputs (%QW\p.2.c\m.i.r).

368

35013154.02 07/2208

Fipio Agent

25.3

Debugging Fipio Agents

FIPIO Agent debugging screen

Introduction

Illustration

This screen, split into two areas, is used to debug a FIPIO Agent.

The screen dedicated to debugging looks like this:

TSX 3722 [POSITION 00.0..1]

Debugging

Designation: PROCESSOR 37222 Version: 3.4

1

CHANNEL 1

CHANNEL 1

FIPIO

TSX FPP 10 PCMCIAFIPIO CARD

MAST

2

FIPIO function status

State of output %MW

Active

Active

Table addresses:

OUTPUT from: %MW300 to %MW331

INPUT from: %MW322 to %MW363

Access values via animation tables

DIAG...

DIAG...

Elements and functions

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

Address Zone

1 common

2 specific

Function

See (See : PL7 Micro/Junior/Pro ; Communication applications

; Volume 1).

is used to access the debugging parameters of a FIPIO Agent.

No data can be accessed from this screen.

35013154.02 07/2208

369

Fipio Agent

25.4

Language objects associated with the Fipio

Agents

Introduction

Aim of this

Section

What's in this

Section?

This Section introduces the language objects associated with Fipio Agents.

This section contains the following topics:

Topic

Language objects in implicit exchange

Language object for explicit exchange

Explicit exchange management and reports

Language objects associated with configuration

Page

371

372

373

374

370

35013154.02 07/2208

Fipio Agent

Language objects in implicit exchange

Introduction

Bit objects

This page describes all the language objects for implicit exchange associated with the FIPIO communication agents that can be displayed or modified by the agent’s application program. (PL7 Micro/Junior/Pro ; Communication applications ;

Volume 1)

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 is faulty,…)

This bit set to 1, indicates a line fault.

Key

(1) z z xy.i Address z x: corresponds to the rack number (-) y: corresponds to the module number (0/1) i: corresponds to the channel number (1)

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

Object (1)

%IWxy.i.0

Function Meaning

Agent function status Byte 0: z = 16#01: IDLE function z z

= 16#02: RUN function

= 16 #03: STOP function

Strategy to be applied to outputs

Byte 1: z z z

= 16#01: safety

= 16#02: %MW value valid

= 16 #03: fallback

Key

(1) z z xy.i Address z x: corresponds to the rack number (-) y: corresponds to the module number (0/1) i: corresponds to the channel number (1)

35013154.02 07/2208

371

Fipio Agent

Language object for explicit exchange

Introduction

Word objects

This page describes all the language objects for explicit exchange associated with the FIPIO communication agents that can be displayed or modified by the application program. (See : PL7 Micro/Junior/Pro ; Communication applications ;

Volume 1)

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

Object (1) Function

%MWxy.MOD.2

Module status

%MWxy.i.2

Standard channel status

Meaning z z z z z z z z 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

Byte 0: z x0 = 1: input words are disabled when the manager is in RUN z x1 = 1: output words are disabled when the agent is in RUN z x4 = 1: internal error of TSX FPP 10 card or card z not yet started by the manager x5 = 1: configuration error (the configured data module is different from that present) x6 = 1: communication error on FIPIO x7 = 1: application error (%MW table overrun)

Byte 1: reserved

Key

(1) xy.i Address z z z x: corresponds to the rack number (-) y: corresponds to the module number (0/1) i: corresponds to the channel number (1)

372

35013154.02 07/2208

Fipio Agent

Explicit exchange management and reports

Introduction

Word objects

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

: PL7 Micro/Junior/Pro ; Communication applications ; Volume 1)

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

Object (1)

%MWxy.MOD.0

%MWxy.MOD.1

%MWxy.i.0

Function

Module exchanges in progress

Module report

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

Channel exchanges in progress z z z x0 = 1: reading status in progress x1 = 1: sending of command parameters to the communication channel x2 = 1: sending of adjustment parameters to the communication channel

%MWxy.i.1

Channel report z z x1 = 0: command parameters received and accepted by the communication channel x2 = 0: adjustment parameters received and accepted by the communication channel

Key

(1) z z z xy.i address x: corresponds to the rack number (-) y: corresponds to the module number (0/1) i: corresponds to the channel number (1)

35013154.02 07/2208

373

Fipio Agent

Language objects associated with configuration

Introduction

Internal constants

This page describes all the configuration language objects associated with the

FIPIO communication agents that can be displayed by the agent application program.

The following table describes the internal constants:

Object Function

%KWxy.i.0

Type

%KWxy.i.1

Reserved

%KWxy.i.2

Connection point address

%KWxy.i.3

Table start address

Meaning

Byte 0 = 16#09: for the FIPIO Agent function

-

Byte 0 = 16#01 to 16#7F: corresponds to addresses

1 to 127

Byte 0: least significant byte of the address

Byte 1: most significant byte of the address

374

35013154.02 07/2208

Index

A

Accessible Functions

Modbus, 30

Accessing configuration

Modem, 90

Accessing the configuration

FIPIO, 266, 283

Modbus, 26, 27

Modbus Plus, 200

Accessing the configuration screen

FIPIO Agent, 367

Accessing the debugging screen

FIPIO, 305

Accessing the diagnostics screen, 311

Addressing

FIPIO Bus, 238

Momentum, 238

TBX, 238

Adjustment mode

Standard profile, 341

AT Commands, 133

B

Bus properties

FIPIO, 275

C

CALL_MODEM, 102

Characteristics

Modem, 74

35013154.02 07/2008

Communication channel test

Modbus, 53

Communication function

Modbus, 38

Compatibility

FIPIO, 242, 243

Modbus Plus, 189

Modem, 77

compatibility

modem, 75

Configuration

Modbus, 25

Modbus Plus, 199

Modem, 89

Configuration access

Modbus, 28

Configuration Parameters

Modbus, 31, 33

Configuration parameters

Modbus Plus, 203

Modem, 92, 94, 96

Configuration Screen

Modbus, 29

Configuration screen

FIPIO, 267, 284, 289

FIPIO Agent, 368, 369

Modbus Plus, 201

Modem, 91

Standard profile, 337, 343

configuring, 263

configuring devices, 282

configuring Fipio Agent, 366

A C

375

Index

configuring standard profiles, 336

D

Data exchange

FIPIO Agent, 360

Modbus Plus, 210

Debug parameters

Modbus, 52

Debug screen

Modbus, 50

Debugging

Modbus, 49

Modbus Plus, 219

Modem, 119

debugging devices, 303

debugging Fipio Agent, 369

Debugging Parameters

Modbus, 51

Debugging parameters

Modbus Plus, 221

Modem, 121

Debugging screen

FIPIO, 306

Modbus Plus, 220

Modem, 120

debugging standard profiles, 342

Diagnostics

Modbus Plus, 215

diagnostics, 309

Diagnostics screen, 312

Driver

Modem, 86

E

Error processing using the program, 298

Exchange management

FIPIO, 328

FIPIO Agent, 373

Modbus Plus, 229

Modem, 129

376

Explicit exchange

FIPIO, 325

FIPIO Agent, 372

Modbus, 58

Modbus Plus, 227

Modem, 125

Standard profiles (FIPIO), 353

F

FIPIO, 233

Fipio Agent, 357

Fipio management, 297

G

General

FIPIO, 235

Modbus, 17

Modbus Plus, 187

Modem, 67

Global data, 217

I

Implicit Exchange

Modbus Plus, 224

Implicit exchange

FIPIO, 324

FIPIO Agent, 371

Modbus, 56

Modem, 124

Standard profiles (FIPIO), 351

Input/output management

FIPIO, 290

Introduction

Modbus Plus, 188

Modem, 68

L

Language objects

Modbus, 55

Modbus Plus, 223

Modem, 123

35013154.02 07/2008

M

Management of exchanges

Modbus, 61

Management parameters

Modem, 104

Modbus, 15

Compatibilities, 19

Introduction, 18

Modbus Plus, 185

MODEM, 65

O

Operating Mode

Modbus, 23

Operating mode

FIPIO, 254

Modem, 73

P

parameter settings, 323

Fipio Agent, 370

standard profiles, 347

Peer Cop, 195

Performance

Fipio, 256, 258

Modbus, 22

Programming

Modbus, 37

Modbus Plus, 207

Modem, 101

programming, 297

programming Modbus, 40

R

Read mode

Modbus Plus, 208

Report

FIPIO, 328

FIPIO Agent, 373

Modbus, 61

Modbus Plus, 229

Modem, 129

35013154.02 07/2008

S

Set-up

Modem, 79

Specific inputs, 204

Specific outputs, 204

standard profiles, 329

system objects

Modbus, 64

T

tasks, 241

W

Write mode

Modbus Plus, 208

X

X-WAY

Modbus Plus, 190

Index

377

Index

378

35013154.02 07/2008