WAGO 750, 750-342 Series Manual

Download

Page 1

Modular I/O-System ETHERNET TCP/IP

750-342

Manual

Technical description, installation and configuration

Version 2.1.1

Page 2

ii • General

WAGO-I/O-SYSTEM 750

ETHERNET TCP/IP

WAGO Kontakttechnik GmbH & Co. KG

Hansastraße 27 D-32423 Minden

Phone: +49 (0) 571/8 87 – 0 Fax: +49 (0) 571/8 87 – 1 69

E-Mail: info@wago.com Web: http://www.wago.com

Technical Support

Phone: +49 (0) 571/8 87 – 5 55 Fax: +49 (0) 571/8 87 – 85 55

E-Mail: support@wago.com

Every conceivable measure has been taken to ensure the correctness and completeness of this documentation. However, as errors can never be fully excluded we would appreciate any information or ideas at any time.

E-Mail: documentation@wago.com We wish to point out that the software and hardware terms as well as the

trademarks of companies used and/or mentioned in the present manual are generally trademark or patent protected.

This product includes software developed by the University of California, Berkley and ist contributors.

Page 3

Table of Contents • iii

WAGO-I/O-SYSTEM 750 ETHERNET TCP/IP

TABLE OF CONTENTS

1 Important Notes ..........................................................................................1

1.1 Legal Principles........................................................................................1

1.1.1 Copyright.............................................................................................1

1.1.2 Personnel Qualification .......................................................................1

1.1.3 Conforming Use of Series 750 ............................................................2

1.1.4 Technical Condition of the Devices ....................................................2

1.2 Standards and Regulations for Operating the 750 Series.........................2

1.3 Symbols....................................................................................................3

1.4 Safety Information....................................................................................4

1.5 Font Conventions .....................................................................................5

1.6 Number Notation......................................................................................5

1.7 Scope........................................................................................................1

1.8 Important Comments for Starting up........................................................5

1.9 Abbreviation.............................................................................................6

2 The WAGO-I/O-SYSTEM 750..................................................................7

2.1 System Description...................................................................................7

2.2 Technical Data..........................................................................................8

2.3 Manufacturing Number..........................................................................14

2.4 Component Update.................................................................................15

2.5 Storage, Assembly and Transport ..........................................................15

2.6 Mechanical Setup...................................................................................16

2.6.1 Installation Position...........................................................................16

2.6.2 Total Expansion.................................................................................16

2.6.3 Assembly onto Carrier Rail...............................................................17

2.6.3.1 Carrier rail properties....................................................................17

2.6.3.2 WAGO DIN Rail ..........................................................................18

2.6.4 Spacing ..............................................................................................18

2.6.5 Plugging and Removal of the Components.......................................19

2.6.6 Assembly Sequence...........................................................................20

2.6.7 Internal Bus/Data Contacts................................................................21

2.6.8 Power Contacts..................................................................................22

2.6.9 Wire connection.................................................................................23

2.7 Power Supply .........................................................................................24

2.7.1 Isolation.............................................................................................24

2.7.2 System Supply...................................................................................25

2.7.2.1 Connection....................................................................................25

2.7.2.2 Alignment .....................................................................................26

2.7.3 Field Supply.......................................................................................28

2.7.3.1 Connection....................................................................................28

2.7.3.2 Fusing............................................................................................29

2.7.4 Supplementary power supply regulations..........................................32

2.7.5 Supply example .................................................................................33

2.7.6 Power Supply Unit.............................................................................34

2.8 Grounding...............................................................................................35

2.8.1 Grounding the DIN Rail ....................................................................35

2.8.1.1 Framework Assembly...................................................................35

Page 4

iv • Table of Contents

WAGO-I/O-SYSTEM 750

ETHERNET TCP/IP

2.8.1.2 Insulated Assembly.......................................................................35

2.8.2 Grounding Function...........................................................................36

2.8.3 Grounding Protection ........................................................................37

2.9 Shielding (Screening).............................................................................38

2.9.1 General...............................................................................................38

2.9.2 Bus Conductors..................................................................................38

2.9.3 Signal Conductors..............................................................................38

2.9.4 WAGO Shield (Screen) Connecting System.....................................39

2.10 Assembly Guidelines/Standards.............................................................39

3 Fieldbus Coupler.......................................................................................40

3.1 Fieldbus coupler 750-342.......................................................................40

3.1.1 Description.........................................................................................40

3.1.2 Hardware............................................................................................41

3.1.2.1 View..............................................................................................41

3.1.2.2 Device supply................................................................................42

3.1.2.3 Fieldbus connection......................................................................42

3.1.2.4 Display elements...........................................................................43

3.1.2.5 Configuration interface.................................................................43

3.1.2.6 Hardware address (MAC-ID) .......................................................44

3.1.3 Operating system...............................................................................44

3.1.4 Process image ....................................................................................45

3.1.4.1 Example of a process input image ................................................46

3.1.4.2 Example of a process output image ..............................................47

3.1.4.3 Process Data Architecture.............................................................48

3.1.5 Data Exchange...................................................................................48

3.1.5.1 Memory areas................................................................................49

3.1.5.2 Addressing ....................................................................................50

3.1.5.2.1 Addressing the I/O modules..........................................................50

3.1.5.3 Data exchange between MODBUS/TCP master and I/O modules51

3.1.6 Starting up a Fieldbus Node ..............................................................52

3.1.6.1 Note the MAC-ID and establish the fieldbus node.......................52

3.1.6.2 Connecting PC and fieldbus node.................................................52

3.1.6.3 Determining IP addresses .............................................................53

3.1.6.4 Allocating the IP address to the fieldbus node .............................53

3.1.6.5 Testing the function of the fieldbus node .....................................56

3.1.6.6 Reading out the information as HTML pages...............................57

3.1.7 LED Display......................................................................................58

3.1.7.1 Fieldbus status...............................................................................58

3.1.7.2 Node status – Blink code from the 'I/O' LED ...............................59

3.1.7.3 Supply voltage status ....................................................................66

3.1.8 Fault behavior....................................................................................66

3.1.8.1 Fieldbus failure .............................................................................66

3.1.8.2 Internal bus fault ...........................................................................66

3.1.9 Technical Data...................................................................................67

4 Fieldbus Communication..........................................................................69

4.1 ETHERNET ...........................................................................................69

4.1.1 General...............................................................................................69

Page 5

Table of Contents • v

WAGO-I/O-SYSTEM 750 ETHERNET TCP/IP

4.1.2 Network Architecture – Principles and Regulations .........................70

4.1.2.1 Transmission Media......................................................................71

4.1.2.2 Network Topologies......................................................................73

4.1.2.3 Coupler Modules...........................................................................76

4.1.2.4 Important Terms............................................................................77

4.1.3 Network Communication...................................................................79

4.1.3.1 Protocol layer model.....................................................................79

4.1.3.2 Communication Protocols.............................................................81

4.1.3.2.1 ETHERNET..................................................................................82

4.1.3.3 Channel access method.................................................................82

4.1.3.3.1 IP-Protocol....................................................................................83

4.1.3.3.1.1 RAW IP.................................................................................... 87

4.1.3.3.1.2 IP Multicast..............................................................................87

4.1.3.3.2 TCP Protocol.................................................................................87

4.1.3.3.3 UDP...............................................................................................88

4.1.3.3.4 ARP...............................................................................................88

4.1.3.4 Administration and Diagnosis Protocols ......................................89

4.1.3.4.1 BootP (Bootstrap Protocol)...........................................................89

4.1.3.4.2 HTTP (HyperText Transfer Protocol)..........................................90

4.1.3.4.3 DHCP (Dynamic Host Configuration Protocol)...........................91

4.1.3.4.4 DNS (Domain Name Systems) .....................................................92

4.1.3.4.5 SNTP-Client (Simple Network Time Protocol)............................92

4.1.3.4.6 FTP-Server (File Transfer Protocol).............................................92

4.1.3.4.7 SMTP (Simple Mail Transfer Protocol) .......................................94

4.1.3.5 Application Protocols ...................................................................94

4.2 MODBUS Functions..............................................................................95

4.2.1 General...............................................................................................95

4.2.2 Use of the MODBUS Functions........................................................97

4.2.3 Description of the MODBUS Functions ...........................................98

4.2.3.1 Function Code FC1 (Read Coils)..................................................99

4.2.3.2 Function Code FC2 (Read Input Discretes)................................100

4.2.3.3 Function Code FC3 (Read multiple registers) ............................101

4.2.3.4 Function code FC4 (Read input registers) ..................................102

4.2.3.5 Function Code FC5 (Write Coil) ...............................................103

4.2.3.6 Function Code FC6 (Write single register)................................104

4.2.3.7 Function code FC7 (Read Exception Status)..............................105

4.2.3.8 Function Code FC11 (Get comm event counter)........................106

4.2.3.9 Function Code FC15 (Force Multiple Coils).............................107

4.2.3.10 Function Code FC16 (Write multiple registers) ........................108

4.2.3.11 Function Code FC23 (Read/Write multiple registers)................108

4.2.4 MODBUS Register Mapping ..........................................................110

4.2.5 Internal Variables ............................................................................111

4.2.5.1 Description of the internal variables...........................................113

4.2.5.1.1 Watchdog (Fieldbus failure) .......................................................113

4.2.5.1.2 Watchdog Register:.....................................................................113

4.2.5.2 Diagnostic Functions ..................................................................118

4.2.5.3 Configuration Functions .............................................................118

4.2.5.4 Firmware Information.................................................................120

4.2.5.5 Constant Registers .....................................................................122

Page 6

vi • Table of Contents

WAGO-I/O-SYSTEM 750

ETHERNET TCP/IP

5 I/O Modules .............................................................................................124

5.1 Overview ..............................................................................................124

5.1.1 Digital Input Modules......................................................................124

5.1.2 Digital Output Modules...................................................................126

5.1.3 Analog Intput Modules....................................................................127

5.1.4 Analog Output Modules ..................................................................128

5.1.5 Special Modules ..............................................................................129

5.1.6 System Modules...............................................................................130

5.2 Process Data Architecture for MODBUS/TCP....................................131

5.2.1 Digital Input Modules......................................................................131

5.2.2 Digital Output Modules...................................................................133

5.2.3 Analog Input Modules.....................................................................137

5.2.4 Analog Output Modules ..................................................................138

5.2.5 Specialty Modules ...........................................................................139

5.2.6 System Modules...............................................................................151

6 Application Examples.............................................................................152

6.1 Test of MODBUS protocol and fieldbus nodes ...................................152

6.2 Visualization and control using SCADA software...............................152

7 Use in Hazardous Environments ...........................................................155

7.1 Foreword ..............................................................................................155

7.2 Protective measures..............................................................................155

7.3 Classification meeting CENELEC and IEC.........................................155

7.3.1 Divisions..........................................................................................155

7.3.2 Explosion protection group .............................................................156

7.3.3 Unit categories.................................................................................157

7.3.4 Temperature classes.........................................................................157

7.3.5 Types of ignition protection ............................................................158

7.4 Classifications meeting the NEC 500...................................................159

7.4.1 Divisions..........................................................................................159

7.4.2 Explosion protection groups............................................................159

7.4.3 Temperature classes.........................................................................160

7.5 Identification ........................................................................................161

7.5.1 For Europe.......................................................................................161

7.5.2 For America.....................................................................................162

7.6 Installation regulations.........................................................................163

8 Glossary....................................................................................................165

9 Literature List .........................................................................................177

10 Index.........................................................................................................178

Page 7

Important Notes • 1 Legal Principles

WAGO-I/O-SYSTEM 750 ETHERNET TCP/IP

1 Important Notes

This section provides only a summary of the most important safety requirements and notes which will be mentioned in the individual sections. To protect your health and prevent damage to the devices, it is essential to read and carefully follow the safety guidelines.

1.1 Legal Principles

1.1.1 Copyright

This manual including all figures and illustrations contained therein is subject to copyright. Any use of this manual which infringes the copyright provisions stipulated herein, is not permitted. Reproduction, translation and electronic and phototechnical archiving and amendments require the written consent of WAGO Kontakttechnik GmbH & Co. KG, Minden. Non-observance will entail the right of claims for damages.

WAGO Kontakttechnik GmbH & Co. KG reserves the right of changes serving technical progress. All rights developing from the issue of a patent or the legal protection of utility patents are reserved to WAGO Kontakttechnik GmbH & Co. KG. Third-party products are always indicated without any notes concerning patent rights. Thus, the existence of such rights must not be excluded.

1.1.2 Personnel Qualification

The use of the product described in this manual requires special qualifications, as shown in the following table:

Activity Electrical specialist

Instructed personnel*)

Specialists**) having qualifications in PLC programming

Assembly

X X

Commissioning

X X

Programming

Maintenance

X X

Troubleshooting

Disassembly

X X

*) Instructed persons have been trained by qualified personnel or electrical specialists.

**) A specialist is someone who, through technical training, knowledge and experience, demonstrates the ability to meet the relevant specifications and identify potential dangers in the mentioned field of activity.

All personnel must be familiar with the applicable standards. WAGO Kontakttechnik GmbH & Co. KG declines any liability resulting from

Page 8

2 • Important Notes Standards and Regulations for Operating the 750 Series

WAGO-I/O-SYSTEM 750

ETHERNET TCP/IP

improper action and damage to WAGO products and third party products due to non-observance of the information contained in this manual.

1.1.3 Conforming Use of Series 750

The couplers and controllers of the modular I/O System 750 receive digital and analog signals from the I/O modules and sensors and transmit them to the actuators or higher level control systems. Using the WAGO controllers, the signals can also be (pre-)processed.

The device is designed for IP20 protection class. It is protected against finger touch and solid impurities up to 12.5mm diameter, but not against water penetration. Unless otherwise specified, the device must not be operated in wet and dusty environments.

1.1.4 Technical Condition of the Devices

For each individual application, the components are supplied from the factory with a dedicated hardware and software configuration. Changes in hardware, software and firmware are only admitted within the framework of the possibilities documented in the manuals. All changes to the hardware or software and the non-conforming use of the components entail the exclusion of liability on the part of WAGO Kontakttechnik GmbH & Co. KG.

Please direct any requirements pertaining to a modified and/or new hardware or software configuration directly to WAGO Kontakttechnik GmbH & Co. KG.

1.2 Standards and Regulations for Operating the 750 Series

Please observe the standards and regulations that are relevant to your installation:

• The data and power lines must be connected and installed in compliance with the standards to avoid failures on your installation and eliminate any danger to personnel.

• For installation, startup, maintenance and repair, please observe the accident prevention regulations of your machine (e.g. BGV A 3, "Electrical Installations and Equipment").

• Emergency stop functions and equipment must not be made ineffective. See relevant standards (e.g. DIN EN 418).

• Your installation must be equipped in accordance to the EMC guidelines so that electromagnetic interferences can be eliminated.

• Operating 750 Series components in home applications without further measures is only permitted if they meet the emission limits (emissions of interference) according to EN 61000-6-3. You will find the relevant information in the section on "WAGO-I/O-SYSTEM 750" Æ "System Description" Æ "Technical Data".

Page 9

Important Notes • 3 Symbols

WAGO-I/O-SYSTEM 750 ETHERNET TCP/IP

• Please observe the safety measures against electrostatic discharge

according to DIN EN 61340-5-1/-3. When handling the modules, ensure that the environment (persons, workplace and packing) is well grounded.

• The relevant valid and applicable standards and guidelines concerning the

installation of switch cabinets are to be observed.

1.3 Symbols

Danger Always observe this information to protect persons from injury.

Warning Always observe this information to prevent damage to the device.

Attention

Marginal conditions that must always be observed to ensure smooth and efficient operation.

ESD (Electrostatic Discharge) Warning of damage to the components through electrostatic discharge. Observe the precautionary measure for handling components at risk of electrostatic discharge.

Note Make important notes that are to be complied with so that a trouble-free and efficient device operation can be guaranteed.

Additional Information

References to additional literature, manuals, data sheets and INTERNET pages.

Page 10

4 • Important Notes Safety Information

WAGO-I/O-SYSTEM 750

ETHERNET TCP/IP

1.4 Safety Information

When connecting the device to your installation and during operation, the following safety notes must be observed:

Danger The WAGO-I/O-SYSTEM 750 and its components are an open system. It must only be assembled in housings, cabinets or in electrical operation rooms. Access is only permitted via a key or tool to authorized qualified personnel.

Danger All power sources to the device must always be switched off before carrying out any installation, repair or maintenance work.

Warning

Replace defective or damaged device/module (e.g. in the event of deformed contacts), as the functionality of fieldbus station in question can no longer be ensured on a long-term basis.

Warning

The components are not resistant against materials having seeping and insulating properties. Belonging to this group of materials is: e.g. aerosols, silicones, triglycerides (found in some hand creams). If it cannot be ruled out that these materials appear in the component environment, then the components must be installed in an enclosure that is resistant against the above mentioned materials. Clean tools and materials are generally required to operate the device/module.

Warning Soiled contacts must be cleaned using oil-free compressed air or with ethyl alcohol and leather cloths.

Warning Do not use contact sprays, which could possibly impair the functioning of the contact area.

Warning

Avoid reverse polarity of data and power lines, as this may damage the devices.

ESD (Electrostatic Discharge)

The devices are equipped with electronic components that may be destroyed by electrostatic discharge when touched.

Page 11

Important Notes • 5 Font Conventions

WAGO-I/O-SYSTEM 750 ETHERNET TCP/IP

1.5 Font Conventions

italic

Names of paths and files are marked in italic. e.g.: C:\Programs\WAGO-IO-CHECK

italic

Menu items are marked in bold italic. e.g.: Save

A backslash between two names characterizes the selection of a menu point from a menu. e.g.: File \ New

END

Press buttons are marked as bold with small capitals e.g.:

ENTER

< >

Keys are marked bold within angle brackets e.g.: <F5>

Courier

The print font for program codes is Courier. e.g.: END_VAR

1.6 Number Notation

Number code Example Note

Decimal 100 Normal notation Hexadecimal 0x64 C notation Binary '100'

'0110.0100'

Within ', Nibble separated with dots

1.7 Scope

This manual describes the fieldbus coupler for ETHERNET 10/100 MBit/s of the WAGO-I/O-SYSTEM 750.

1.8 Important Comments for Starting up

Attention

For the start-up of the coupler 750-341 important notes are to be considered, because it strongly differentiates in some points of starting up the WAGO ETHERNET coupler 750-342. Read for this the chapter: “Starting up EHTERNET TCP/IP fieldbus nodes“.

Page 12

6 • Important Notes Abbreviation

WAGO-I/O-SYSTEM 750

ETHERNET TCP/IP

1.9 Abbreviation

Analog Input

Analog Output

Digital Input

Digital Output

I/O

Input/Output

Identifier

Page 13

System Description • 7 Technical Condition of the Devices

WAGO-I/O-SYSTEM 750 ETHERNET TCP/IP

2 The WAGO-I/O-SYSTEM 750

2.1 System Description

The WAGO-I/O-SYSTEM 750 is a modular, fieldbus independent I/O system. It is comprised of a fieldbus coupler/controller (1) and connected fieldbus modules (2) for any type of signal. Together, these make up the fieldbus node. The end module (3) completes the node.

Fig. 2-1: Fieldbus node g0xxx00x

Couplers/controllers for fieldbus systems such as PROFIBUS, INTERBUS, ETHERNET TCP/IP, CAN (CANopen, DeviceNet, CAL), MODBUS, LON and others are available.

The coupler/controller contains the fieldbus interface, electronics and a power supply terminal. The fieldbus interface forms the physical interface to the relevant fieldbus. The electronics process the data of the bus modules and make it available for the fieldbus communication. The 24 V system supply and the 24 V field supply are fed in via the integrated power supply terminal. The fieldbus coupler communicates via the relevant fieldbus. The programmable fieldbus controller (PFC) enables the implementation of additional PLC functions. Programming is done with the WAGO-I/O-PRO 32 in accordance with IEC 61131-3.

Bus modules for diverse digital and analog I/O functions as well as special functions can be connected to the coupler/controller. The communication between the coupler/controller and the bus modules is carried out via an internal bus.

The WAGO-I/O-SYSTEM 750 has a clear port level with LEDs for status indication, insertable mini WSB markers and pullout group marker carriers. The 3-wire technology supplemented by a ground wire connection allows for direct sensor/actuator wiring.

Page 14

8 • The WAGO-I/O-SYSTEM 750 Technical Data

WAGO-I/O-SYSTEM 750

ETHERNET TCP/IP

2.2 Technical Data

Mechanic

Material Polycarbonate, Polyamide 6.6 Dimensions W x H* x L

* from upper edge of DIN 35 rail

- Coupler/Controller (Standard)

- Coupler/Controller (ECO)

- Coupler/Controller (FireWire)

- I/O module, single

- I/O module, double

- I/O module, fourfold

- 51 mm x 65 mm x 100 mm

- 50 mm x 65 mm x 100 mm

- 62 mm x 65 mm x 100 mm

- 12 mm x 64 mm x 100 mm

- 24 mm x 64 mm x 100 mm

- 48 mm x 64 mm x 100 mm Installation on DIN 35 with interlock modular by double featherkey-dovetail Mounting position any position Marking marking label type 247 and 248

paper marking label 8 x 47 mm

Connection

Connection type CAGE CLAMP® Wire range 0.08 mm² ... 2.5 mm², AWG 28-14 Stripped length 8 – 9 mm,

9 – 10 mm for components with pluggable wiring (753-xxx)

Contacts

Power jumpers contacts blade/spring contact

self-cleaning

Current via power contacts

max

10 A

Voltage drop at I

max

< 1 V/64 modules

Data contacts slide contact, hard gold plated

1.5 µm, self-cleaning

Climatic environmental conditions

Operating temperature 0 °C ... 55 °C,

-20 °C … +60 °C for components with extended

temperature range (750-xxx/025-xxx) Storage temperature -20 °C ... +85 °C Relative humidity 5 % to 95 % without condensation Resistance to harmful substances acc. to IEC 60068-2-42 and IEC 60068-2-43 Maximum pollutant concentration at

relative humidity < 75%

≤ 25 ppm

S ≤ 10 ppm

Special conditions Ensure that additional measures for components are

taken, which are used in an environment involving:

– dust, caustic vapors or gasses

– ionization radiation.

Page 15

Technical Data • 9 Technical Condition of the Devices

WAGO-I/O-SYSTEM 750 ETHERNET TCP/IP

Safe electrical isolation

Air and creepage distance acc. to IEC 60664-1 Degree of pollution

acc. To IEC 61131-2

Degree of protection

Degree of protection IP 20

Electromagnetic compatibility Immunity to interference for industrial areas acc. to EN 61000-6-2 (2001) Test specification Test values Strength

class

Evaluation criteria

EN 61000-4-2 ESD 4 kV/8 kV (contact/air) 2/3 B EN 61000-4-3

electromagnetic fields

10 V/m 80 MHz ... 1 GHz 3 A

EN 61000-4-4 burst 1 kV/2 kV (data/supply) 2/3 B

-/- (line/line) Data: 1 kV (line/earth) 2

0.5 kV (line/line) 1 DC

supply:

0.5 kV (line/earth) 1

1 kV (line/line) 2

EN 61000-4-5 surge

AC supply:

2 kV (line/earth) 3

EN 61000-4-6 RF disturbances

10 V/m 80 % AM (0.15 ... 80 MHz)

3 A

Emission of interference for industrial areas acc. to EN 61000-6-4 (2001) Test specification Limit values/[QP]*) Frequency range Distance

79 dB (µV) 150 kHz ... 500 kHz EN 55011 (AC supply,

conducted)

73 dB (µV) 500 kHz ... 30 MHz 40 dB (µV/m) 30 MHz ... 230 MHz 10 m EN 55011 (radiated) 47 dB (µV/m) 230 MHz ... 1 GHz 10 m

Emission of interference for residential areas acc. to EN 61000-6-3 (2001) Test specification Limit values/[QP]*) Frequency range Distance

66 ... 56 dB (µV) 150 kHz ... 500 kHz 56 dB (µV) 500 kHz ... 5 MHz

EN 55022 (AC supply, conducted)

60 dB (µV) 5 MHz ... 30 MHz 40 ... 30 dB (µA) 150 kHz ... 500 kHz EN 55022 (DC supply/data,

conducted)

30 dB (µA) 500 kHz ... 30 MHz 30 dB (µV/m) 30 MHz ... 230 MHz 10 m EN 55022 (radiated) 37 dB (µV/m) 230 MHz ... 1 GHz 10 m

Page 16

10 • The WAGO-I/O-SYSTEM 750 Technical Data

WAGO-I/O-SYSTEM 750

ETHERNET TCP/IP

Mechanical strength acc. to IEC 61131-2 Test specification Frequency range Limit value

5 Hz ≤ f < 9 Hz

1.75 mm amplitude (permanent)

3.5 mm amplitude (short term)

9 Hz ≤ f < 150 Hz

0.5 g (permanent) 1 g (short term)

IEC 60068-2-6 vibration

Note on vibration test: a) Frequency change: max. 1 octave/minute b) Vibration direction: 3 axes

15 g IEC 60068-2-27 shock Note on shock test:

a) Type of shock: half sine b) Shock duration: 11 ms c) Shock direction: 3x in positive and 3x in negative direction for each of the three mutually perpendicular axes of the test specimen

IEC 60068-2-32 free fall 1 m

(module in original packing)

*) QP: Quasi Peak

Note: If the technical data of components differ from the values described here, the technical data shown in the manuals of the respective components shall be valid.

Page 17

Technical Data • 11 Technical Condition of the Devices

WAGO-I/O-SYSTEM 750 ETHERNET TCP/IP

For Products of the WAGO-I/O-SYSTEM 750 with ship specific approvals, supplementary guidelines are valid:

Electromagnetic compatibility Immunity to interference acc. to Germanischer Lloyd (2003) Test specification Test values Strength

class

Evaluation criteria

IEC 61000-4-2 ESD 6 kV/8 kV (contact/air) 3/3 B IEC 61000-4-3

electromagnetic fields

10 V/m 80 MHz ... 2 GHz 3 A

IEC 61000-4-4 burst 1 kV/2 kV (data/supply) 2/3 A

0.5 kV (line/line) 1 IEC 61000-4-5 surge AC/DC

Supply:

1 kV (line/earth) 2

IEC 61000-4-6 RF disturances

10 V/m 80 % AM (0.15 ... 80 MHz)

3 A

Type test AF disturbances (harmonic waves)

3 V, 2 W - A

Type test high voltage 755 V DC

1500 V AC

- -

Emission of interference acc. to Germanischer Lloyd (2003) Test specification Limit values Frequency range Distance

96 ... 50 dB (µV) 10 kHz ... 150 kHz 60 ... 50 dB (µV) 150 kHz ... 350 kHz

Type test (EMC1, conducted) allows for ship bridge control applications

50 dB (µV) 350 kHz ... 30 MHz 80 ... 52 dB (µV/m) 150 kHz ... 300 kHz 3 m

52 ... 34 dB (µV/m) 300 kHz ... 30 MHz 3 m

Type test (EMC1, radiated) allows for ship bridge control applications

54 dB (µV/m) 30 MHz ... 2 GHz 3 m

außer für: 24 dB (µV/m) 156 MHz ... 165 MHz 3 m

Mechanical strength acc. to Germanischer Lloyd (2003) Test specification Frequency range Limit value

2 Hz ≤ f < 25 Hz

± 1.6 mm amplitude (permanent)

25 Hz ≤ f < 100 Hz

4 g (permanent)

IEC 60068-2-6 vibration (category A – D)

Note on vibration test: a) Frequency change: max. 1 octave/minute b) Vibration direction: 3 axes

Page 18

12 • The WAGO-I/O-SYSTEM 750 Technical Data

WAGO-I/O-SYSTEM 750

ETHERNET TCP/IP

Range of application

Required specification emission of interference

Required specification immunity to interference

Industrial areas EN 61000-6-4 (2001) EN 61000-6-2 (2001) Residential areas EN 61000-6-3 (2001)*) EN 61000-6-1 (2001)

The system meets the requirements on emission of interference in residential areas with the fieldbus coupler/controller for:

ETHERNET LonWorks CANopen DeviceNet MODBUS

750-342/-841/-842/-860 750-319/-819 750-337/-837 750-306/-806 750-312/-314/ -315/ -316

750-812/-814/ -815/ -816

With a special permit, the system can also be implemented with other fieldbus couplers/controllers in residential areas (housing, commercial and business areas, smallscale enterprises). The special permit can be obtained from an authority or inspection office. In Germany, the Federal Office for Post and Telecommunications and its branch offices issues the permit.

It is possible to use other field bus couplers/controllers under certain boundary conditions. Please contact WAGO Kontakttechnik GmbH & Co. KG.

Maximum power dissipation of the components

Bus modules 0.8 W / bus terminal (total power dissipation,

system/field) Fieldbus coupler/controller 2.0 W / coupler/controller

Warning

The power dissipation of all installed components must not exceed the maximum conductible power of the housing (cabinet).

When dimensioning the housing, care is to be taken that even under high external temperatures, the temperature inside the housing does not exceed the permissible ambient temperature of 55 °C.

Page 19

Technical Data • 13 Technical Condition of the Devices

WAGO-I/O-SYSTEM 750 ETHERNET TCP/IP

Dimensions

24V 0V

100

Side view

Dimensions in mm

Fig. 2-2: Dimensions g01xx05e

Note: The illustration shows a standard coupler. For detailed dimensions, please refer to the technical data of the respective coupler/controller.

Page 20

14 • The WAGO-I/O-SYSTEM 750 Manufacturing Number

WAGO-I/O-SYSTEM 750

ETHERNET TCP/IP

2.3 Manufacturing Number

The manufacturing number indicates the delivery status directly after production. This number is part of the lateral marking on the component. In addition, starting from calender week 43/2000 the manufacturing number is also printed on the cover of the configuration and programming interface of the fieldbus coupler or controller.

Hansastr. 27 D-32423 Minden

ITEM-NO.:750-333

PROFIBUS DP 12 MBd /DPV1

0V Power Supply Electronic

PATENTS PENDING

II3GD DEMKO 02 ATEX132273 X EEx nA II T4

24V DC

AWG 28-14

55°C max ambient

LISTED 22ZA AND 22XM

72072

0103000203-B000000

Hansastr. 27 D-32423 Minden

ITEM-NO.:750-333

PROFIBUS DP 12 MBd /DPV1

0V Power Supply Electronic

PATENTS PENDING

II3GD DEMKO 02 ATEX132273 X EEx nA II T4

24V DC

AWG 28-14

55°C max ambient

LISTED 22ZA AND 22XM

72072

0103000203-B060606

FWL

Power Supply Field

24 V

-B060606

PROFIBUS

WAGO - I/O - SYSTEM

750-333

01030002 03-B 060606 72072

Manufacturing Number

Calendar

week

Year Software

version

Hardware

version

Firmware Loader

version

Internal

Number

Fig. 2-3: Example: Manufacturing Number of a PROFIBUS fieldbus coupler 750-333

g01xx15e

The manufacturing number consists of the production week and year, the software version (if available), the hardware version of the component, the firmware loader (if available) and further internal information for WAGO Kontakttechnik GmbH.

Page 21

Component Update • 15 Technical Condition of the Devices

WAGO-I/O-SYSTEM 750 ETHERNET TCP/IP

2.4 Component Update

For the case of an Update of one component, the lateral marking on each component contains a prepared matrix.

This matrix makes columns available for altogether three updates to the entry of the current update data, like production order number (NO; starting from calendar week 13/2004), update date (DS), software version (SW), hardware version (HW) and the firmware loader version (FWL, if available).

Update Matrix

Current Version data for: 1. Update 2. Update 3. Update Production Order

Number

Å Only starting from

calendar week 13/2004

Datestamp

Software index

Hardware index

Firmware loader index

FWL

Å Only for coupler/

controller

If the update of a component took place, the current version data are registered into the columns of the matrix.

Additionally with the update of a fieldbus coupler or controller also the cover of the configuration and programming interface of the coupler or controller is printed on with the current manufacturing and production order number.

The original manufacturing data on the housing of the component remain thereby.

2.5 Storage, Assembly and Transport

Wherever possible, the components are to be stored in their original packaging. Likewise, the original packaging provides optimal protection during transport.

When assembling or repacking the components, the contacts must not be soiled or damaged. The components must be stored and transported in appropriate containers/packaging. Thereby, the ESD information is to be regarded.

Statically shielded transport bags with metal coatings are to be used for the transport of open components for which soiling with amine, amide and silicone has been ruled out, e.g. 3M 1900E.

Page 22

16 • The WAGO-I/O-SYSTEM 750 Mechanical Setup

WAGO-I/O-SYSTEM 750

ETHERNET TCP/IP

2.6 Mechanical Setup

2.6.1 Installation Position

Along with horizontal and vertical installation, all other installation positions are allowed.

Attention In the case of vertical assembly, an end stop has to be mounted as an additional safeguard against slipping. WAGO item 249-116 End stop for DIN 35 rail, 6 mm wide WAGO item 249-117 End stop for DIN 35 rail, 10 mm wide

2.6.2 Total Expansion

The length of the module assembly (including one end module of 12mm width) that can be connected to the coupler/controller is 780mm. When assembled, the I/O modules have a maximum length of 768mm.

Examples:

• 64 I/O modules of 12mm width can be connected to one coupler/controller.

• 32 I/O modules of 24mm width can be connected to one coupler/controller.

Exception:

The number of connected I/O modules also depends on which type of coupler/controller is used. For example, the maximum number of I/O modules that can be connected to a Profibus coupler/controller is 63 without end module.The maximum total expansion of a node is calculated as follows:

Warning The maximum total length of a node without coupler/controller must not exceed 780mm. Furthermore, restrictions made on certain types of couplers/controllers must be observed (e.g. for Profibus).

Page 23

Mechanical Setup • 17 Assembly onto Carrier Rail

WAGO-I/O-SYSTEM 750 ETHERNET TCP/IP

2.6.3 Assembly onto Carrier Rail

2.6.3.1 Carrier rail properties

All system components can be snapped directly onto a carrier rail in accordance with the European standard EN 50022 (DIN 35).

Warning WAGO supplies standardized carrier rails that are optimal for use with the I/O system. If other carrier rails are used, then a technical inspection and approval of the rail by WAGO Kontakttechnik GmbH should take place.

Carrier rails have different mechanical and electrical properties. For the optimal system setup on a carrier rail, certain guidelines must be observed:

• The material must be non-corrosive.

• Most components have a contact to the carrier rail to ground electro-

magnetic disturbances. In order to avoid corrosion, this tin-plated carrier rail contact must not form a galvanic cell with the material of the carrier rail which generates a differential voltage above 0.5 V (saline solution of

0.3% at 20°C) .

• The carrier rail must optimally support the EMC measures integrated into the system and the shielding of the bus module connections.

• A sufficiently stable carrier rail should be selected and, if necessary, several mounting points (every 20 cm) should be used in order to prevent bending and twisting (torsion).

• The geometry of the carrier rail must not be altered in order to secure the safe hold of the components. In particular, when shortening or mounting the carrier rail, it must not be crushed or bent.

• The base of the I/O components extends into the profile of the carrier rail. For carrier rails with a height of 7.5 mm, mounting points are to be riveted under the node in the carrier rail (slotted head captive screws or blind rivets).

Page 24

18 • The WAGO-I/O-SYSTEM 750 Mechanical Setup

WAGO-I/O-SYSTEM 750

ETHERNET TCP/IP

2.6.3.2 WAGO DIN Rail

WAGO carrier rails meet the electrical and mechanical requirements.

Item Number Description

210-113 /-112 35 x 7.5; 1 mm; steel yellow chromated; slotted/unslotted 210-114 /-197 35 x 15; 1.5 mm; steel yellow chromated; slotted/unslotted 210-118 35 x 15; 2.3 mm; steel yellow chromated; unslotted 210-198 35 x 15; 2.3 mm; copper; unslotted 210-196 35 x 7.5; 1 mm; aluminum; unslotted

2.6.4 Spacing

The spacing between adjacent components, cable conduits, casing and frame sides must be maintained for the complete field bus node.

Fig. 2-4: Spacing g01xx13x

The spacing creates room for heat transfer, installation or wiring. The spacing to cable conduits also prevents conducted electromagnetic interferences from influencing the operation.

Page 25

Mechanical Setup • 19 Plugging and Removal of the Components

WAGO-I/O-SYSTEM 750 ETHERNET TCP/IP

2.6.5 Plugging and Removal of the Components

Warning Before work is done on the components, the voltage supply must be turned off.

In order to safeguard the coupler/controller from jamming, it should be fixed onto the carrier rail with the locking disc To do so, push on the upper groove of the locking disc using a screwdriver.

To pull out the fieldbus coupler/controller, release the locking disc by pressing on the bottom groove with a screwdriver and then pulling the orange colored unlocking lug.

Fig. 2-5: Coupler/Controller and unlocking lug g01xx12e

It is also possible to release an individual I/O module from the unit by pulling an unlocking lug.

Fig. 2-6: removing bus terminal p0xxx01x

Danger Ensure that an interruption of the PE will not result in a condition which could endanger a person or equipment! For planning the ring feeding of the ground wire, please see chapter 2.6.3.

Page 26

20 • The WAGO-I/O-SYSTEM 750 Mechanical Setup

WAGO-I/O-SYSTEM 750

ETHERNET TCP/IP

2.6.6 Assembly Sequence

All system components can be snapped directly on a carrier rail in accordance with the European standard EN 50022 (DIN 35).

The reliable positioning and connection is made using a tongue and groove system. Due to the automatic locking, the individual components are securely seated on the rail after installing.

Starting with the coupler/controller, the bus modules are assembled adjacent to each other according to the project planning. Errors in the planning of the node in terms of the potential groups (connection via the power contacts) are recognized, as the bus modules with power contacts (male contacts) cannot be linked to bus modules with fewer power contacts.

Attention Always link the bus modules with the coupler/controller, and always plug from above.

Warning Never plug bus modules from the direction of the end terminal. A ground wire power contact, which is inserted into a terminal without contacts, e.g. a 4-channel digital input module, has a decreased air and creepage distance to the neighboring contact in the example DI4.

Always terminate the fieldbus node with an end module (750-600).

Page 27

Mechanical Setup • 21 Internal Bus/Data Contacts

WAGO-I/O-SYSTEM 750 ETHERNET TCP/IP

2.6.7 Internal Bus/Data Contacts

Communication between the coupler/controller and the bus modules as well as the system supply of the bus modules is carried out via the internal bus. It is comprised of 6 data contacts, which are available as self-cleaning gold spring contacts.

Fig. 2-7: Data contacts p0xxx07x

Warning Do not touch the gold spring contacts on the I/O modules in order to avoid soiling or scratching!

ESD (Electrostatic Discharge) The modules are equipped with electronic components that may be destroyed by electrostatic discharge. When handling the modules, ensure that the environment (persons, workplace and packing) is well grounded. Avoid touching conductive components, e.g. gold contacts.

Page 28

22 • The WAGO-I/O-SYSTEM 750 Mechanical Setup

WAGO-I/O-SYSTEM 750

ETHERNET TCP/IP

2.6.8 Power Contacts

Self-cleaning power contacts , are situated on the side of the components which further conduct the supply voltage for the field side. These contacts come as touchproof spring contacts on the right side of the coupler/controller and the bus module. As fitting counterparts the module has male contacts on the left side.

Danger The power contacts are sharp-edged. Handle the module carefully to prevent injury.

Attention Please take into consideration that some bus modules have no or only a few power jumper contacts. The design of some modules does not allow them to be physically assembled in rows, as the grooves for the male contacts are closed at the top.

Fig. 2-8: Example for the arrangement of power contacts g0xxx05e

Recommendation With the WAGO ProServe® Software smartDESIGNER, the assembly of a fieldbus node can be configured. The configuration can be tested via the integrated accuracy check.

Page 29

Mechanical Setup • 23 Wire connection

WAGO-I/O-SYSTEM 750 ETHERNET TCP/IP

2.6.9 Wire connection

All components have CAGE CLAMP® connections. The WAGO CAGE CLAMP® connection is appropriate for solid, stranded

and fine–stranded conductors. Each clamping unit accommodates one conductor.

Fig. 2-9: CAGE CLAMP® Connection g0xxx08x

The operating tool is inserted into the opening above the connection. This opens the CAGE CLAMP®. Subsequently the conductor can be inserted into the opening. After removing the operating tool, the conductor is safely clamped.

More than one conductor per connection is not permissible. If several conductors have to be made at one connection point, then they should be made away from the connection point using WAGO Terminal Blocks. The terminal blocks may be jumpered together and a single wire brought back to the I/O module connection point.

Attention If it is unavoidable to jointly connect 2 conductors, then a ferrule must be used to join the wires together. Ferrule: Length 8 mm Nominal cross section

max.

1 mm2 for 2 conductors with 0.5 mm2 each WAGO Product 216-103 or products with comparable properties

Page 30

24 • The WAGO-I/O-SYSTEM 750 Power Supply

WAGO-I/O-SYSTEM 750

ETHERNET TCP/IP

2.7 Power Supply

2.7.1 Isolation

Within the fieldbus node, there are three electrically isolated potentials.

• Operational voltage for the fieldbus interface.

• Electronics of the couplers/controllers and the bus modules (internal bus).

• All bus modules have an electrical isolation between the electronics

(internal bus, logic) and the field electronics. Some digital and analog input modules have each channel electrically isolated, please see catalog.

Fig. 2-10: Isolation g0xxx01e

Attention The ground wire connection must be present in each group. In order that all protective conductor functions are maintained under all circumstances, it is recommended that a ground wire be connected at the beginning and end of a potential group. (ring format, please see chapter "2.8.3"). Thus, if a bus module comes loose from a composite during servicing, then the protective conductor connection is still guaranteed for all connected field devices.

When using a joint power supply unit for the 24 V system supply and the 24 V field supply, the electrical isolation between the internal bus and the field level is eliminated for the potential group.

Page 31

Power Supply • 25 System Supply

WAGO-I/O-SYSTEM 750 ETHERNET TCP/IP

2.7.2 System Supply

2.7.2.1 Connection

The WAGO-I/O-SYSTEM 750 requires a 24 V direct current system supply (-15% or +20 %). The power supply is provided via the coupler/controller and, if necessary, in addition via the internal system supply modules (750-613). The voltage supply is reverse voltage protected.

Attention

The use of an incorrect supply voltage or frequency can cause severe damage to the component.

Fig. 2-11: System Supply g0xxx02e

The direct current supplies all internal system components, e.g. coupler/controller electronics, fieldbus interface and bus modules via the internal bus (5 V system voltage). The 5 V system voltage is electrically connected to the 24 V system supply.

Fig. 2-12: System Voltage g0xxx06e

Page 32

26 • The WAGO-I/O-SYSTEM 750 Power Supply

WAGO-I/O-SYSTEM 750

ETHERNET TCP/IP

Attention Resetting the system by switching on and off the system supply, must take place simultaneously for all supply modules (coupler/controller and 750-613).

2.7.2.2 Alignment

Recommendation A stable network supply cannot be taken for granted always and everywhere. Therefore, regulated power supply units should be used in order to guarantee the quality of the supply voltage.

The supply capacity of the coupler/controller or the internal system supply module (750-613) can be taken from the technical data of the components.

Internal current consumption*)

Current consumption via system voltage: 5 V for electronics of the bus modules and coupler/controller

Residual current for bus terminals*)

Available current for the bus modules. Provided by the bus power supply unit. See coupler/controller and internal system supply module (750-613)

*) cf. catalogue W4 Volume 3, manuals or Internet

Example

Coupler 750-301: internal current consumption:350 mA at 5V residual current for bus modules : 1650 mA at 5V sum I(5V)

total

: 2000 mA at 5V

The internal current consumption is indicated in the technical data for each bus terminal. In order to determine the overall requirement, add together the values of all bus modules in the node.

Attention If the sum of the internal current consumption exceeds the residual current for bus modules, then an internal system supply module (750-613) must be placed before the module where the permissible residual current was exceeded.

Example:

A node with a PROFIBUS Coupler 750-333 consists of 20 relay modules (750-517) and 10 digital input modules (750-405).

Current consumption: 20* 90 mA = 1800 mA 10* 2 mA = 20 mA Sum 1820 mA

The coupler can provide 1650 mA for the bus modules. Consequently, an internal system supply module (750-613), e.g. in the middle of the node, should be added.

Page 33

Power Supply • 27 System Supply

WAGO-I/O-SYSTEM 750 ETHERNET TCP/IP

Recommendation With the WAGO ProServe® Software smartDESIGNER, the assembly of a fieldbus node can be configured. The configuration can be tested via the integrated accuracy check.

The maximum input current of the 24 V system supply is 500 mA. The exact electrical consumption (I

(24 V)

) can be determined with the following formulas:

Coupler/Controller

I(5 V)

total

= Sum of all the internal current consumption of the connected

bus modules + internal current consumption coupler/controller

750-613

I(5 V)

total

= Sum of all the internal current consumption of the connected

bus modules

Input current I(24 V) =

5 V / 24 V * I(5 V)

total

/ η

η = 0.87 (at nominal load)

Note If the electrical consumption of the power supply point for the 24 V-system supply exceeds 500 mA, then the cause may be an improperly aligned node or a defect.

During the test, all outputs, in particular those of the relay modules, must be active.

Page 34

28 • The WAGO-I/O-SYSTEM 750 Power Supply

WAGO-I/O-SYSTEM 750

ETHERNET TCP/IP

2.7.3 Field Supply

2.7.3.1 Connection

Sensors and actuators can be directly connected to the relevant channel of the bus module in 1-/4 conductor connection technology. The bus module supplies power to the sensors and actuators. The input and output drivers of some bus modules require the field side supply voltage.

The coupler/controller provides field side power (DC 24V). In this case it is a passive power supply without protection equipment. Power supply modules are available for other potentials, e.g. AC 230 V. Likewise, with the aid of the power supply modules, various potentials can be set up. The connections are linked in pairs with a power contact.

Fig. 2-13: Field Supply (Sensor/Actuator) g0xxx03e

The supply voltage for the field side is automatically passed to the next module via the power jumper contacts when assembling the bus modules .

The current load of the power contacts must not exceed 10 A on a continual basis. The current load capacity between two connection terminals is identical to the load capacity of the connection wires.

By inserting an additional power supply module, the field supply via the power contacts is disrupted. From there a new power supply occurs which may also contain a new voltage potential.

Page 35

Power Supply • 29 Field Supply

WAGO-I/O-SYSTEM 750 ETHERNET TCP/IP

Attention Some bus modules have no or very few power contacts (depending on the I/O function). Due to this, the passing through of the relevant potential is disrupted. If a field supply is required for subsequent bus modules, then a power supply module must be used. Note the data sheets of the bus modules.

In the case of a node setup with different potentials, e.g. the alteration from DC 24 V to AC 230V, a spacer module should be used. The optical separation of the potentials acts as a warning to heed caution in the case of wiring and maintenance works. Thus, the results of wiring errors can be prevented.

2.7.3.2 Fusing

Internal fusing of the field supply is possible for various field voltages via an appropriate power supply module.

750-601 24 V DC, Supply/Fuse 750-609 230 V AC, Supply/Fuse 750-615 120 V AC, Supply/Fuse 750-610 24 V DC, Supply/Fuse/Diagnosis 750-611 230 V AC, Supply/Fuse/Diagnosis

Fig. 2-14: Supply module with fuse carrier (Example 750-610) g0xxx09x

Page 36

30 • The WAGO-I/O-SYSTEM 750 Power Supply

WAGO-I/O-SYSTEM 750

ETHERNET TCP/IP

Warning In the case of power supply modules with fuse holders, only fuses with a maximum dissipation of 1.6 W (IEC 127) must be used.

For UL approved systems only use UL approved fuses.

In order to insert or change a fuse, or to switch off the voltage in succeeding bus modules, the fuse holder may be pulled out. In order to do this, use a screwdriver for example, to reach into one of the slits (one on both sides) and pull out the holder.

Fig. 2-15: Removing the fuse carrier p0xxx05x

Lifting the cover to the side opens the fuse carrier.

Fig. 2-16: Opening the fuse carrier p0xxx03x

Fig. 2-17: Change fuse p0xxx04x

After changing the fuse, the fuse carrier is pushed back into its original position.

Page 37

Power Supply • 31 Field Supply

WAGO-I/O-SYSTEM 750 ETHERNET TCP/IP

Alternatively, fusing can be done externally. The fuse modules of the WAGO series 281 and 282 are suitable for this purpose.

Fig. 2-18: Fuse modules for automotive fuses, Series 282 pf66800x

Fig. 2-19: Fuse modules with pivotable fuse carrier, Series 281 pe61100x

Fig. 2-20: Fuse modules, Series 282 pf12400x

Page 38

32 • The WAGO-I/O-SYSTEM 750 Power Supply

WAGO-I/O-SYSTEM 750

ETHERNET TCP/IP

2.7.4 Supplementary power supply regulations

The WAGO-I/O-SYSTEM 750 can also be used in shipbuilding or offshore and onshore areas of work (e.g. working platforms, loading plants). This is demonstrated by complying with the standards of influential classification companies such as Germanischer Lloyd and Lloyds Register.

Filter modules for 24-volt supply are required for the certified operation of the system.

Item No. Name Description

750-626 Supply filter Filter module for system supply and field supply (24 V,

0 V), i.e. for field bus coupler/controller and bus power supply (750-613)

750-624 Supply filter Filter module for the 24 V- field supply

(750-602, 750-601, 750-610)

Therefore, the following power supply concept must be absolutely complied with.

Fig. 2-21: Power supply concept g01xx11e

Note Another potential power terminal 750-601/602/610 must only be used behind the filter terminal 750-626 if the protective earth conductor is needed on the lower power contact or if a fuse protection is required.

Page 39

Power Supply • 33 Supply example

WAGO-I/O-SYSTEM 750 ETHERNET TCP/IP

2.7.5 Supply example

Note The system supply and the field supply should be separated in order to ensure bus operation in the event of a short-circuit on the actuator side.

750-630750-400 750-410 750-401

750-613

750-512 750-512750-616 750-513 750-610 750-552 750-600750-612 750-616

2) 2)

24V

10 A

L1 L2 L3 N PE

230V

Main ground bus

Shield (screen) bus

System Supply

Field Supply

1) Separation module recommended

2) Ring-feeding recommended

a) Power Supply

on coupler / controller via external Supply Module

b) Internal System

Supply Module

c) Supply Module

passive

iagnostics

Supply Module

with fuse carrier/ d

Fig. 2-22: Supply example g0xxx04e

Page 40

34 • The WAGO-I/O-SYSTEM 750 Power Supply

WAGO-I/O-SYSTEM 750

ETHERNET TCP/IP

2.7.6 Power Supply Unit

The WAGO-I/O-SYSTEM 750 requires a 24 V direct current system supply with a maximum deviation of -15% or +20 %.

A buffer (200 µF per 1 A current load) should be provided for brief voltage dips. The I/O system buffers for approx 1 ms.

The electrical requirement for the field supply is to be determined individually for each power supply point. Thereby all loads through the field devices and bus modules should be considered. The field supply as well influences the bus modules, as the inputs and outputs of some bus modules require the voltage of the field supply.

Note The system supply and the field supply should be isolated from the power supplies in order to ensure bus operation in the event of short circuits on the actuator side.

WAGO products Article No.

Description

787-903 Primary switched - mode, DC 24 V, 5 A

wide input voltage range AC 85-264 V PFC (Power Factor Correction)

787-904 Primary switched - mode, DC 24 V, 10 A

wide input voltage range AC 85-264 V PFC (Power Factor Correction)

787-912 Primary switched - mode, DC 24 V, 2 A

wide input voltage range AC 85-264 V PFC (Power Factor Correction)

288-809 288-810 288-812 288-813

Rail-mounted modules with universal mounting carrier AC 115 V / DC 24 V; 0,5 A

AC 230 V / DC 24 V; 0,5 A AC 230 V / DC 24 V; 2 A AC 115 V / DC 24 V; 2 A

Page 41

Grounding • 35 Grounding the DIN Rail

WAGO-I/O-SYSTEM 750 ETHERNET TCP/IP

2.8 Grounding

2.8.1 Grounding the DIN Rail

2.8.1.1 Framework Assembly

When setting up the framework, the carrier rail must be screwed together with the electrically conducting cabinet or housing frame. The framework or the housing must be grounded. The electronic connection is established via the screw. Thus, the carrier rail is grounded.

Attention Care must be taken to ensure the flawless electrical connection between the carrier rail and the frame or housing in order to guarantee sufficient grounding.

2.8.1.2 Insulated Assembly

Insulated assembly has been achieved when there is constructively no direct conduction connection between the cabinet frame or machine parts and the carrier rail. Here the earth must be set up via an electrical conductor.

The connected grounding conductor should have a cross section of at least 4 mm2.

Recommendation The optimal insulated setup is a metallic assembly plate with grounding connection with an electrical conductive link with the carrier rail.

The separate grounding of the carrier rail can be easily set up with the aid of the WAGO ground wire terminals.

Article No. Description

283-609 Single-conductor ground (earth) terminal block make an automatic

contact to the carrier rail; conductor cross section: 0.2 -16 mm2 Note: Also order the end and intermediate plate (283-320)

Page 42

36 • The WAGO-I/O-SYSTEM 750 Grounding

WAGO-I/O-SYSTEM 750

ETHERNET TCP/IP

2.8.2 Grounding Function

The grounding function increases the resistance against disturbances from electro-magnetic interferences. Some components in the I/O system have a carrier rail contact that dissipates electro-magnetic disturbances to the carrier rail.

Fig. 2-23: Carrier rail contact g0xxx10e

Attention Care must be taken to ensure the direct electrical connection between the carrier rail contact and the carrier rail.

The carrier rail must be grounded.

For information on carrier rail properties, please see chapter 2.6.3.2.

Page 43

Grounding • 37 Grounding Protection

WAGO-I/O-SYSTEM 750 ETHERNET TCP/IP

2.8.3 Grounding Protection

For the field side, the ground wire is connected to the lowest connection terminals of the power supply module. The ground connection is then connected to the next module via the Power Jumper Contact (PJC). If the bus module has the lower power jumper contact, then the ground wire connection of the field devices can be directly connected to the lower connection terminals of the bus module.

Attention Should the ground conductor connection of the power jumper contacts within the node become disrupted, e.g. due to a 4-channel bus terminal, the ground connection will need to be re-established.

The ring feeding of the grounding potential will increase the system safety. When one bus module is removed from the group, the grounding connection will remain intact.

The ring feeding method has the grounding conductor connected to the beginning and end of each potential group.

Fig. 2-24: Ring-feeding g0xxx07e

Attention The regulations relating to the place of assembly as well as the national regulations for maintenance and inspection of the grounding protection must be observed.

Page 44

38 • The WAGO-I/O-SYSTEM 750 Shielding (Screening)

WAGO-I/O-SYSTEM 750

ETHERNET TCP/IP

2.9 Shielding (Screening)

2.9.1 General

The shielding of the data and signal conductors reduces electromagnetic interferences thereby increasing the signal quality. Measurement errors, data transmission errors and even disturbances caused by overvoltage can be avoided.

Attention Constant shielding is absolutely required in order to ensure the technical specifications in terms of the measurement accuracy.

The data and signal conductors should be separated from all high-voltage cables.

The cable shield should be potential. With this, incoming disturbances can be easily diverted.

The shielding should be placed over the entrance of the cabinet or housing in order to already repel disturbances at the entrance.

2.9.2 Bus Conductors

The shielding of the bus conductor is described in the relevant assembly guidelines and standards of the bus system.

2.9.3 Signal Conductors

Bus modules for most analog signals along with many of the interface bus modules include a connection for the shield.

Note For better shield performance, the shield should have previously been placed over a large area. The WAGO shield connection system is suggested for such an application. This suggestion is especially applicable when the equipment can have even current or high impulse formed currents running through it (for example through atmospheric end loading).

Page 45

Assembly Guidelines/Standards • 39 WAGO Shield (Screen) Connecting System

WAGO-I/O-SYSTEM 750 ETHERNET TCP/IP

2.9.4 WAGO Shield (Screen) Connecting System

The WAGO Shield Connecting system includes a shield clamping saddle, a collection of rails and a variety of mounting feet. Together these allow many dfferent possibilities. See catalog W4 volume 3 chapter 10.

Fig. 2-25: WAGO Shield (Screen) Connecting System p0xxx08x, p0xxx09x, and p0xxx10x

Fig. 2-26: Application of the WAGO Shield (Screen) Connecting System p0xxx11x

2.10 Assembly Guidelines/Standards

DIN 60204, Electrical equipping of machines DIN EN 50178 Equipping of high-voltage systems with electronic

components (replacement for VDE 0160)

EN 60439 Low voltage – switch box combinations

Page 46

40 • Fieldbus coupler 750-342 Description

WAGO-I/O-SYSTEM 750

ETHERNET TCP/IP

3 Fieldbus Coupler

3.1 Fieldbus coupler 750-342

3.1.1 Description

The fieldbus coupler 750-342 displays the peripheral data of all I/O modules in the WAGO-I/O-SYSTEM 750 on ETHERNET.

All sensor input signals are grouped in the coupler (slave) and transferred to the higher ranking controls (master) via the fieldbus. Process data linking is performed in the higher ranking controls. The controls put out the resulting data to the actuators via the bus and the node.

To be able to transmit process data via ETHERNET, the coupler supports a series of network protocols. Process data are exchanged with the aid of the MODBUS/TCP protocol.

Once the ETHERNET TCP/IP fieldbus coupler is connected, the coupler detects all I/O modules connected to the node and creates a local process image on this basis, which can be a mixed arrangement of analog (word-byword data exchange) and digital (bit-by-bit data exchange) modules.

The local process image is subdivided into an input and an output data area. The data of the analog modules are mapped into the process image in the order

of their position downstream of the bus coupler. The bits of the digital modules are grouped into words and also mapped into

the process image as soon as mapping of the analog modules is completed. When the number of digital I/O’s exceeds 16 bits, the coupler automatically starts the next word.

Also note that all process images start at WORD 0. Information on configuration, status and the I/O data of the fieldbus node are

stored in the fieldbus coupler as HTML pages. These pages can be seen via a standard WEB browser by typing the IP address, that you assigned the coupler, into the Address field of your web browser.

Page 47

Fieldbus coupler 750-342 • 41 Hardware

WAGO-I/O-SYSTEM 750 ETHERNET TCP/IP

3.1.2 Hardware

3.1.2.1 View

24V 0V

01 02

750-342

LINK

TxD/RxD

I/O

ETHERNET

ERROR

status voltage supply

-power jumper contacts

-system data contacts supply

24V 0V

supply via power jumper contacts 24V

power jumper contacts

fieldbus

connection

RJ 45

configuration

interface

flap

open

Fig. 3.1-1: Fieldbus coupler ETHERNET TCP/IP G034200e

The fieldbus coupler is comprised of:

• Supply module which includes the internal system supply as well as power jumper contacts for the field supply via I/O module assemblies.

• Fieldbus interface with the bus connection RJ 45

• Display elements (LED's) for status display of the operation, the bus

communication, the operating voltages as well as for fault messages and diagnosis

• Configuration Interface

• Electronics for communication with the I/O modules (internal bus) and the

fieldbus interface

Page 48

42 • Fieldbus coupler 750-342 Hardware

WAGO-I/O-SYSTEM 750

ETHERNET TCP/IP

3.1.2.2 Device supply

The supply is made via terminal bocks with CAGE CLAMP® connection. The device supply is intended both for the system and the field units.

Fig. 3.1-2: Device supply G034201e

The integrated internal system supply module generates the necessary voltage to supply the electronics and the connected I/O modules. The fieldbus interface is supplied with electrically isolated voltage from the internal system supply module.

3.1.2.3 Fieldbus connection

Connection to the fieldbus is by an RJ45 connector. A category 5, shielded/unshielded twisted pair cable (S-UTP) with an impedance of 100 Ohm ±15% is mandatory as a connecting line for the 10BaseT Interface. The connection point is physically lowered for the coupler/controller to fit in an 80 mm high switch box once connected. The electrical isolation between the fieldbus system and the electronics is achieved by means of DC/DC converters and optocouplers in the fieldbus interface.

Contact Signal

1 TD + Transmit + 2 TD - Transmit 3 RD + Receive + 4 free 5 free 6 RD - Receive 7 free 8 free

Fig. 3.1-3: RJ45-connector and RJ45 connector configuration

Page 49

Fieldbus coupler 750-342 • 43 Hardware

WAGO-I/O-SYSTEM 750 ETHERNET TCP/IP

Attention! Only for use in LAN, not for connection to telecommunication circuits!

3.1.2.4 Display elements

The operating condition of the fieldbus coupler or node is signaled via light diodes (LED).

24V

I/O

24V

LINK

TxD/RxD

ERROR

I/O

ETHERNET

LINK

TxD/RxD

ERROR

ETHERNET

Fig. 3.1-4: Display elements 750-342 g012946x

LED Color Meaning

ON green Fieldbus initialization is correct LINK green Link to a physical network exists TxD/RxD green Data exchange taking place ERROR red Error on the fieldbus IO red /green

/ orange

The 'I/O'-LED indicates the operation of the node and signals faults encountered

A green Status of the operating voltage – system B or C green Status of the operating voltage – power jumper contacts

(LED position is manufacturing dependent)

3.1.2.5 Configuration interface

The configuration interface used for the communication with WAGO-I/OCHECK or for firmware download is located behind the cover flap.

Configuration interface

open

flap

Fig. 3.1-5: Configuration interface g012945e

The communication cable (750-920) is connected to the 4 pole header.

Warning

The communication cable 750-920 must not be connected or disconnected while the coupler/controller is powered on!

Page 50

44 • Fieldbus coupler 750-342 Operating system

WAGO-I/O-SYSTEM 750

ETHERNET TCP/IP

3.1.2.6 Hardware address (MAC-ID)

Each WAGO ETHERNET fieldbus coupler is provided from the factory with a unique and internationally unambiguous physical ETHERNET address, also referred to as MAC-ID (Media Access Control Identity). This address is to be found on the rear of the coupler and on an adhesive tear-off label on the side of the coupler. The address has a fixed length of 6 Bytes (48 Bit) and contains the address type, the manufacturer’s ID, and the serial number.

3.1.3 Operating system

Following is the configuration of the master activation and the electrical installation of the fieldbus station to start up the system.

After switching on the supply voltage, the coupler determines the I/O modules and the present configuration.

In the event of a fault, the coupler changes to the "Stop" condition. The "I/O" LED flashes red. After a fault free start up, the coupler changes to the "Fieldbus start" status and the "I/O" LED lights up green.

Stop

red “I/O” LED indicates

blink code

Switching on the

supply voltage

Test o.k.?

Yes

Fieldbus coupler is

in operating mode

“I/O” LED is shining green

Initialization,

Determination of the I/O modules

and the configuration,

“I/O” LED is blinking red

Fig. 3.1-6: Operating system 750-342 g012920e

Page 51

Fieldbus coupler 750-342 • 45 Process image

WAGO-I/O-SYSTEM 750 ETHERNET TCP/IP

3.1.4 Process image

After switching on, the coupler recognizes all I/O modules plugged into the node which supply or wait for data (data width/bit width > 0). Analog and digital I/O modules can be mixed on the same node.

Attention For the number of input and output bits or bytes of the individually activated I/O modules, please refer to the corresponding I/O module description.

The coupler produces an internal process image from the data width and the type of I/O module as well as the position of the I/O modules in the node. It is divided into an input and an output data area.

The data of the digital I/O modules is bit orientated, i.e. the data exchange is made bit for bit. The analog I/O modules are representative for all byte orientated I/O modules, i.e. those where the data exchange is made byte for byte. These I/O modules include for example the counter modules, I/O modules for angle and path measurement as well as the communication modules.

The data of the I/O modules is separate from the local input and output process image in the sequence of their position after the coupler in the individual process image. First, all the byte oriented bus modules and then the bit oriented bus modules are stored in the process image. The bits of the digital modules are grouped to form bytes. As soon as the number of digital I/O’s exceeds 8 bits, the coupler automatically starts the next byte.

Attention A process image restructuring may result if a node is changed. In this case the process data addresses also change in comparison with earlier ones. In the event of adding modules, take the process data of all previous modules into account.

The coupler provides a storage area of 256 words each (word 0 - 255) for the physical input and output data.

Access from the fieldbus side is fieldbus specific. For the ETHERNET TCP/IP fieldbus coupler, a MODBUS/TCP master accesses the data via implemented MODBUS functions. Here decimal and/or hexadecimal MODBUS addresses are used.

More information A detailed description of these fieldbus-specific data access operations is given in the section “MODBUS functions”.

More Information You can find the fieldbus specific process data architecture for all I/O Modules in the chapter „Fieldbus specific Process Data Architecture“.

Page 52

46 • Fieldbus coupler 750-342 Data exchange

WAGO-I/O-SYSTEM 750

ETHERNET TCP/IP

3.1.4.1 Example of a process input image

The following figure is an example of a process input image. The configuration comprises of 16 digital and 8 analog inputs. The process image thus has a data length of 8 words for the analog and 1 word for the digital inputs, i.e. 9 words in total.

Bit1

Bit2

0x0003

0x0002

0x0001

0x0000

0x0005

0x0004

0x0007

0x0006

0x0008

0x0001

0x0000

0x0003

0x0002

0x0005

0x0004

0x0007

0x0006

0x0009

0x0008

Word2

Word1

Word2

Word1

Word2

Word1 Word2

Word1

Word2

Word1

Word2

Word1

121

1212121

LINK

TxD/RxD

ERROR

Ethernet

750

-342

I/O

ßI/OßSYSTE M

AI AI

Word2Word2

Word1

Word2Word2

Word1

Highbyte

Lowbyte

DI:Digitale Eingangsklemme AI: Analoge Eingangsklemme

Prozessabbild der Eingänge

(Bit)

MODBUS-

Adressen

MODBUS-Adressen

Prozessabbild der Eingänge

(Word)

Eingangsklemmen 750- 400 400 467 467 400 467 400 400 467

Fig. 3.1-7: Example of a process input image G012914e

Page 53

Fieldbus coupler 750-342 • 47

Data exchange

WAGO-I/O-SYSTEM 750 ETHERNET TCP/IP

3.1.4.2 Example of a process output image

The following example for the process output image comprises of 2 digital and 4 analog outputs. It comprises of 4 words for the analog and 1 word for the digital outputs, , i.e. 5 words in total.

In addition, the output data can be read back by means of an offset of 200hex (0x0200) added to the MODBUS address.

Bit 1

Bit 2

Word2

Word1

Word2

Word1

Word2

Word1

Word2

Word1

Word2

Word1

Word2

Word1

0x0003 / 0x0203

0x0002 / 0x0202

0x0001 / 0x0201

0x0000 / 0x0200

0x0004 / 0x0204

0x0203

0x0202

0x0201

0x0200

0x0204

0x0000 / 0x0200

0x0001 / 0x0201

0x0200

0x0201

Highbyte

Lowbyte

Highbyte

Lowbyte

LINK

ETHERNET

TxD/RxD

I/O

0-341

MODBUS-Adressen

Prozessabbild der Ausgänge

(Word)

Prozessabbild der Eingänge

(Word)

Prozessabbild der Ausgänge

(Bit)

Prozessabbild der Eingänge

(Bit)

Ausgangsklemmen 750-501 550 550

DO: Digitale Ausgangsklemme AO: Analoge Ausgangsklemme

Fig. 3.1-8: Example of a process output image G015015e

Page 54

48 • Fieldbus coupler 750-342 Data exchange

WAGO-I/O-SYSTEM 750

ETHERNET TCP/IP

3.1.4.3 Process Data Architecture

With some I/O modules, the structure of the process data is fieldbus specific. In the case of an Ethernet TCP/IP coupler/controller, the process image uses a word structure (with word alignment). The internal mapping method for data greater than one byte conforms to the Intel format.

More Information You can find the fieldbus specific process data architecture for all I/O Modules of the WAGO-I/O-SYSTEM 750 and 753 in the chapter „ Process Data Architecture for ETHERNET“.

3.1.5 Data Exchange

Process data exchange with the ETHERNET TCP/IP fieldbus coupler occurs via the MODBUS/TCP protocol.

MODBUS/TCP works according to the master/slave principle. The master is a superimposed control unit, i.e. a PC or a PLC device. The ETHERNET TCP/IP couplers of the WAGO-I/O-SYSTEM are slave devices.

The master makes a query for communication. Through adressing, this query can be sent to a specific node. The nodes receive the query and return a response to the master, depending on the kind of query.

A coupler can communicate with a certain number of simultaneous connections (socket connections) to other network subscribers:

• 1 connection for HTTP (reading HTML pages from coupler) and

• 5 connections via MODBUS/TCP (reading or writing input and output

data from coupler). The maximum number of simultaneous connections cannot be exceeded. If further connections are to be made, terminate existing connections beforehand.

For a data exchange, the ETHERNET TCP/IP fieldbus coupler is equipped with two interfaces:

• the interface to fieldbus (-master) and

• the interface to the bus modules.

Data exchange takes place between MODBUS master and the bus modules. The master accesses the bus module data via implemented MODBUS functions.

Page 55

Fieldbus coupler 750-342 • 49

Data exchange

WAGO-I/O-SYSTEM 750 ETHERNET TCP/IP

3.1.5.1 Memory areas

memory area

for input data

I/O modules

input

modules

word 255

output

modules

word 0

word 255

fieldbus master

word 0

memory area

for output data

fieldbus coupler

Fig. 3.1-9: Memory areas and data exchange for a fieldbus coupler g012939e

The coupler process image contains the physical data of the bus modules in a storage area for input data and in a storage area for output data (word 0 ... 255 each).

(1) The input module data can be read from the fieldbus side. (2) In the same manner, writing on the output modules is possible from the

fieldbus side.

In addition, all output data of the ETHERNET TCP/IP coupler are mirror imaged on a storage area with the address offset 0x0200. This allows to read output values back by adding 0x0200 to the MODBUS address.

Page 56

50 • Fieldbus coupler 750-342 Data exchange

WAGO-I/O-SYSTEM 750

ETHERNET TCP/IP

3.1.5.2 Addressing

3.1.5.2.1 Addressing the I/O modules

The arrangement of the I/O modules in a node is optional. When addressing, first of all the more complex modules (modules occupying 1

or more bytes) are taken into account in accordance with their physical order behind the fieldbus coupler. As such, they occupy the addresses starting with word 0. Following this, the data of the other modules (modules occupying less than 1 byte) follow, grouped into bytes. In accordance with the physical byte-wise order this data is used to fill up the bytes. As soon as a full byte is occupied by the bit-oriented modules, the next byte is automatically started.

Attention For the number of input and output bits and/or bytes of the individual activated bus modules, please refer to the pertaining descriptions of the bus modules.

Attention Once a node is modified, a new architecture of the process image can result. As such, the address of the process data will alsochange. In the event of adding modules, the process data of all previous modules has to be taken into account.

Data width ≥ 1 Word / channel Data width = 1 Bit / channel

Analog input modules Digital input modules Analog output modules Digital output modules Input modules for thermal elements Digital output modules with diagnosis (2 Bit / channel) Input modules for resistance sensors Power supply modules with fuse holder / diagnosis Pulse width output modules Solid State power relay Interface module Relay output modules Up/down counter I/O modules for angle and path measurement

Table 3.1.1: I/O module data width

Page 57

Fieldbus coupler 750-342 • 51

Data exchange

WAGO-I/O-SYSTEM 750 ETHERNET TCP/IP

3.1.5.3 Data exchange between MODBUS/TCP master and I/O modules

The data exchange between the MODBUS/TCP master and the I/O modules is made by the implemented MODBUS functions in the coupler with reading and writing in bits or bytes.

The controller handles four different types of process data:

• Input words

• Output words

• Input bits

• Output bits

The word for word access to the digital input and output modules is made in accordance with the following table:

Digital Inputs/Outputs

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

Process data word

Bit 15

Bit 14

Bit 13

Bit 12

Bit 11

Bit 10

Bit9 Bit8 Bit7 Bit 6 Bit 5 Bit 4 Bit 3 Bit2 Bit1 Bit

High-Byte Low-Byte

Byte

D1 D0

Table 3.1.2: Allocation of digital inputs/outputs to process data word acc. Intel format

The outputs can be read back by adding 0x0200 to the MODBUS address.

0x000

0x0FF

0x000

(0x200)

0x0FF

(0x2FF)

PII = Process Input

Image

PIO = Process Output

Image

MODBUS master

PII

PIO

I/O modules

Inputs

Outputs

Fieldbus Coupler

Fig. 3.1-10: Data exchange between the MODBUS master and I/O modules g012927e

Starting from address 0x1000 there are the register functions. The register functions made available in the coupler, can be addressed by the MODBUS master along with the implemented MODBUS function codes (read/write). To this effect, the individual register address is entered in place of the address of a module channel.

More information You can find a detailed description of the MODBUS addressing in the chapter „MODBUS Register Mapping“.

Page 58

52 • Fieldbus coupler 750-342 Starting up a Fieldbus Node

WAGO-I/O-SYSTEM 750

ETHERNET TCP/IP

3.1.6 Starting up a Fieldbus Node

This chapter shows the step-by-step procedure for starting up a WAGO ETHERNET TCP/IP fieldbus node. The following also contains a description of how to read out the coupler-internal HTML pages.

Attention This description is given as an example and is limited to the execution of a local startup of an individual ETHERNET fieldbus node with a computer running under windows which is not connected to a network. Direct Internet connection should only be performed by an authorized network administrator and is, therefore, not described in this manual.

The procedure contains the following steps:

1. Noting the MAC-ID and establishing the fieldbus node

2. Connecting the PC and fieldbus node

3. Determining the IP address

4. Allocation of the IP address to the fieldbus node

5. Function of the fieldbus tests

6. Reading out information as HTML pages

3.1.6.1 Note the MAC-ID and establish the fieldbus node

Before establishing your fieldbus node, please note the hardware address (MAC-ID) of your ETHERNET fieldbus coupler. This is located on the rear of the fieldbus coupler and on the self-adhesive tear-off label on the side of the fieldbus coupler.

MAC-ID of the fieldbus coupler will be in this format:

----- ----- ----- ----- ----- -----.

3.1.6.2 Connecting PC and fieldbus node

Connect the assembled ETHERNET TCP/IP fieldbus node via a hub or directly to the PC using a 10Base-T cable.

Attention For a direct connection, a crossover cable is required instead of a parallel cable.

Now start the PC, functioning as master and BootP server, and switch on the voltage supply on the fieldbus coupler (DC 24 V power pack). Once the operating voltage has been switched on, the initialization starts. The fieldbus coupler determines the configuration of the bus modules and creates the process image.

During the startup the 'I/O' LED (Red) flashes at high frequency. When the 'I/O' LED and the 'ON' LED light up green, the fieldbus coupler is ready for operation. If an error has occurred during startup, it is indicated as an error code by the 'I/O'-LED flashing (red).

Page 59

Fieldbus coupler 750-342 • 53

Starting up a Fieldbus Node

WAGO-I/O-SYSTEM 750 ETHERNET TCP/IP

3.1.6.3 Determining IP addresses

If your PC is already connected to an ETHERNET network, it is very easy to determine the IP address of your PC. To do this, proceed as follows:

1. Go to the Start menu on your screen, menu item Settings and click on Control Panel.

2. Double click the icon Network. The network dialog window will open.

3. - Under Windows NT: Select the register: Protocols and mark the entry TCP/IP protocol.

- Under Windows 9x: Select the register: Configuration and mark the entry TCP/IP network card.

Attention If the entry is missing, please install the respective TCP/IP component and restart your PC. The Windows-NT installation CD, or the installations CD for Windows 9x is required for the installation.

4. Subsequently, click the button "Properties...". The IP address and the subnet mask are found in the ‘IP address’ tab.If applicable, the gateway address of your PC is found in the ‘Gateway’ tab.

5. Please write down the values: IP address PC: ----- . ----- . ----- . ----Subnet mask: ----- . ----- . ----- . ----Gateway: ----- . ----- . ----- . -----

6. Now select a desired IP address for your fieldbus node.

Attention When selecting your IP address, ensure that it is in the same local network in which your PC is located.

7. Please note the IP address you have chosen: IP address fieldbus node: ----- . ----- . ----- . -----

3.1.6.4 Allocating the IP address to the fieldbus node

The following describes how to allocate the IP address for the fieldbus node using the WAGO BootP server by way of an example. You can download a free copy from WAGO over the Internet under: http://www.wago.com/wagoweb/usa/eng/support/downloads/index.htm.

Page 60

54 • Fieldbus coupler 750-342 Starting up a Fieldbus Node

WAGO-I/O-SYSTEM 750

ETHERNET TCP/IP

Note

The IP address can be allocated under other operating systems (i.e. under Linux) as well as with any other BootP servers.

Attention The IP address can be allocated in a direct connection via a crossover cable or via a parallel cable and a hub. An allocation over a switch is not possible.

BootP table

Attention

Prerequisite for the following steps is the correct installation of the WAGO BootP server.

1. Go to the Start menu, menu item Programs / WAGO Software / WAGO BootP Server and click on WAGO BootP Server configuration.

An editable table will appear: "bootptab.txt". This table displays the data basis for the BootP server. Directly following the list of all notations used in the BootP table there are two examples for the allocation of an IP address.

"Example of entry with no gateway" and "Example of entry with gateway".

Fig. 3.1-11: BootP table p012908e

The examples mentioned above contain the following information:

Declaration Meaning

node1, node2

Any name can be given for the node here.

ht=1 Specify the hardware type of the network here.

The hardware type for ETHERNET is 1. (The numbers are described in RFC1700)

ha=0030DE000100 ha=0030DE000200

Specify the hardware address or the MAC-ID of the ETHERNET fieldbus coupler (hexadecimal).

ip= 10.1.254.100 ip= 10.1.254.200

Enter the IP address of the ETHERNET fieldbus coupler (decimal) here.

T3=0A.01.FE.01 Specify the gateway IP address here.

Write the address in hexadecimal form.

sm=255.255.0.0 In addition enter the Subnet-mask of the subnet (decimal), where the

ETHERNET fieldbus coupler belongs to.

Page 61

Fieldbus coupler 750-342 • 55

Starting up a Fieldbus Node

WAGO-I/O-SYSTEM 750 ETHERNET TCP/IP

No gateway is required for the local network described in this example. Therefore, the first example: "Example of entry with no gateway" can be used.

2. Move the mouse pointer to the text line: "node1:ht=1:ha=0030DE000100:ip=10.1.254.100" and mark the 12 character hardware address which is entered after ha=... Enter the MAC-ID of your own network coupler.

3. If you want to give your fieldbus node a name, delete the name "node1" and enter any name in its place.

4. To assign the coupler a desired IP address, mark the IP address specified in the example which is entered after ip=... Replace it with the IP address you have selected.

5. Because the second example is not necessary at present, insert a “#” in front of the text line of the second example: "# node2:hat=1:ha=003 0DE 0002 00:ip=10.1.254.200:T3=0A.01.FE.01", so that this line will be ignored.

Note

To address more fieldbus nodes, enter a corresponding text line showing the corresponding entries for each node.

6. Save the altered settings in this text file "bootptab.txt". To do this go to the

File menu, menu item Save, and close the editor.

BootP Server

7. Now open the dialog window for the WAGO BootP server by going to the Start menu on your screen surface, menu item Program / WAGO Software / WAGO BootP Server and click on WAGO BootP Server.

8. Click on the "Start" button in the opened dialog window. This will activate the inquiry/response mechanism of the BootP protocol. A series of messages will be displayed in the BootP server. The error messages indicate that some services (i.e. port 67, port 68) in the operating system have not been defined.

Fig. 3.1-12: Dialog window of the WAGO BootP server with messages g012909d

Page 62

56 • Fieldbus coupler 750-342 Starting up a Fieldbus Node

WAGO-I/O-SYSTEM 750

ETHERNET TCP/IP

9. Now it is important to restart the coupler by resetting the hardware . This ensures that the new IP address will be accepted by the coupler. To do this, cycle power to the fieldbus coupler for approx. 2 seconds.

Following this, the IP address in the coupler is permanently stored and maintained even once the coupler is removed or following a longer voltage failure.

10. Subsequently, click on the "Stop" button and then on the "Exit" button, to

close the BootP Server again.

3.1.6.5 Testing the function of the fieldbus node

1. To test the communication with the coupler and the correct assignment of

the IP address call up the DOS prompt under Start menu / Program / MS- DOS Prompt.

2. Enter the command: "ping" with the IP address you have assigned in the following form: ping [space] XXXX . XXXX . XXXX . XXXX (=IP address). Example: ping 10.1.254.202

Fig. 3-13: Example for the function test of a fieldbus node P012910d

3. When the Return key has been pressed, your PC will receive a response from the coupler, which will then be displayed in the DOS prompt. If the error message: "Timeout" appears instead, please compare your entries again to the allocated IP address.

4. When the test has been performed successfully, you can close the DOS prompt. The network node has now been prepared for communication.

Page 63

Fieldbus coupler 750-342 • 57

Starting up a Fieldbus Node

WAGO-I/O-SYSTEM 750 ETHERNET TCP/IP

3.1.6.6 Reading out the information as HTML pages

The information saved in the fieldbus coupler can be read as an HTML page using a web browser.

• Information on the fieldbus node (Terminal Status):

- Number of digital, analog or complex modules

- Representation of the process image

• Information on the fieldbus coupler (Coupler and Network Details):

- Order number

- Firmware version

- MAC-ID

- IP address

- Gateway address (if applicable)

- Subnet mask

- Number of transmitted and received packets

• Diagnostic information on the fieldbus coupler (Coupler Status):

- Error code

- Error argument

- Error description

Fig. 3-14: Reading out the information via the HTTP protocol

G012916d

Please proceed as follows:

1. Open a web browser such as Microsoft Internet-Explorer, Netscape Navigator, ...

2. Simply enter the IP address of your fieldbus node in the address field of the browser and press the Return key. The first HTML page with the information on your fieldbus coupler will be displayed in the browser window. Use the hyperlinks to find out more information.

Attention

If the pages are not displayed after local access to the fieldbus node, then define in your web browser that, as an exception, no proxyserver is to be used for the IP address of the node.

Page 64

58 • Fieldbus coupler 750-342 LED Display

WAGO-I/O-SYSTEM 750

ETHERNET TCP/IP

3.1.7 LED Display

The coupler possesses several LED’s for displaying the coupler operating status and the complete node status.

24V

I/O

24V

LINK

TxD/RxD

ERROR

I/O

ETHERNET

LINK

TxD/RxD

ERROR

ETHERNET

Fig. 3-15: Display elements 750-342 G012946x

The LEDs can be divided into three groups. The first group of LEDs display the status of the Ethernet fieldbus. It contains

the solid color LEDs, labelled as: ‘ON‘ (green), ‘LINK‘ (green), ‘TxD/RxD‘ (green) and ‘ERROR‘ (red).

The second group of LEDs is a three-color LED (red/green/orange). This LED is labelled ‘I/O’, and displays the status of the internal bus and i. e. the status of the fieldbus node.

The third group uses solid colored green LEDs. They are located on the righthand side of the coupler power supply. These display the status of the supply.

3.1.7.1 Fieldbus status

The operating status of the communication via ETHERNET is signalled by means of the top LED group (ON, LINK, TxD/RxD and ERROR).

LED Meaning Trouble shooting ON

green Fieldbus initialization is correct OFF Fieldbus initialization is not correct,

no function or self-test

Check the supply voltage (24V and 0V), check the IP configuration

LINK

green Link to a physical network exists OFF No link to a physical network Check the fieldbus connection.

TxD/RxD

green Data exchange taking place OFF No data exchange

ERROR

red Error on the fieldbus OFF No error on the fieldbus, normal operation

Page 65

Fieldbus coupler 750-342 • 59

LED Display

WAGO-I/O-SYSTEM 750 ETHERNET TCP/IP

3.1.7.2 Node status – Blink code from the 'I/O' LED

The ‘I/O‘-LED displays the communication status of the internal bus. Additionally, this LED is used to display fault codes (blink codes) in the event of a system error.

LED Meaning Trouble shooting I/O

Green Fieldbus coupler operating perfectly Red a) During startup of fieldbus coupler:

Internal bus being initialized, Startup displayed by LED flashing fast for approx. 1-2 seconds

Red b) After startup of fieldbus coupler:

Errors, which occur, are indicated by three conse cutive flashing sequences. There is a short pause between each sequential flash.

Evaluate the fault message (fault code and fault argument).

The coupler starts up after switching on the supply voltage. The "I/O" LED blinks. The "I/O" LED has a steady light following a fault free run-up. In the case of a fault the "I/O" LED continues blinking. The fault is cyclically displayed by the blink code.

Detailed fault messages are displayed with the aid of a blink code. A fault is cyclically displayed with up to 3 blink sequences.

• The first blink sequence (approx. 10 Hz) starts the fault display.

• The second blink sequence (approx. 1 Hz) following a pause. The

number of blink pulses indicates the fault code.

• The third blink sequence (approx. 1 Hz) follows after a further pause.

The number of blink pulses indicates the fault argument.

Page 66

60 • Fieldbus coupler 750-342 LED Display

WAGO-I/O-SYSTEM 750

ETHERNET TCP/IP

“I/O”-LED is blinking

Test o.k.?

Yes

“I/O”-LED is shining

ready for operation

2nd break

1st break

“I/O” LED 1st flash sequence

(Introduction of the error indication)

“I/O” LED 2nd flash sequence

Error code

(Number of flash cycles)

“I/O” LED 3rd flash sequence

Error argument

(Number of flash cycles)

Coupler/Controller starts up

Switching on

the power supply

Fig. 3.1-16: Signalling of the LED for indication of the node status g012911e

After clearing a fault, restart the coupler by cycling the power.

Page 67

Fieldbus coupler 750-342 • 61

LED Display

WAGO-I/O-SYSTEM 750 ETHERNET TCP/IP

Fault message of the ‘I/O‘-LED

1 st flash sequence: Start of the Fault message 2 nd flash sequence: Fault code 3 rd flash sequence: Fault argument

Fault code 1: "Hardware and Configuration fault" Fault argument Fault description Trouble shooting

- Invalid checksum within the parameter range of fieldbus coupler

Turn off the power supply of the node, exchange the bus coupler and turn the power supply on again.

1 Overflow of the internal buffer

memory for the inline code

Turn off the power supply of the node, reduce number of I/O modules and turn the power supply on again. If the error still exists, exchange the bus coupler.

2 I/O module(s) with unsupported

data type

Detect faulty I/O module as follows: turn off the power supply. Place the end module in the middle of the fieldbus node. Turn the power supply on again. – If the LED is still blinking, turn off the power supply and place the end module in the middle of the first half of the node (towards the coupler). – If the LED doesn’t blink, turn off the power supply and place the end module in the middle of the second half of the node (away from the coupler). Turn the power supply on again. Repeat this procedure until the faulty I/O module is detected. Replace the faulty I/O module. Ask about a firmware update for the fieldbus coupler.

3 Unknown program module type

of the flash program memory

Turn off the power supply of the node, exchange the bus coupler and turn the power supply on again.

4 Fault when writing data within

the flash memory

Turn off the power supply of the node, exchange the bus coupler and turn the power supply on again.

5 Fault when deleting a flash

sector

Turn off the power supply of the node, exchange the bus coupler and turn the power supply on again.

6 Changed I/O module

configuration determined after AUTORESET

Restart the fieldbus coupler by turning the power supply off and on again.

Page 68

62 • Fieldbus coupler 750-342 LED Display

WAGO-I/O-SYSTEM 750

ETHERNET TCP/IP

7 Fault when writing data in the

serial EEPROM

Turn off the power supply of the node, exchange the bus coupler and turn the power supply on again.

8 Invalid Hardware Firmware

combination

Turn off the power supply of the node, exchange the bus coupler and turn the power supply on again.

9 Invalid checksum within the

serial EEPROM

Turn off the power supply of the node, exchange the bus coupler and turn the power supply on again.

10 serial EEPROM initialization

fault

Turn off the power supply of the node, exchange the bus coupler and turn the power supply on again.

11 Fault when reading out data from

the EEPROM

Turn off the power supply of the node, exchange the bus coupler and turn the power supply on again.

12 Timeout when writing data in the

EEPROM

Turn off the power supply of the node, exchange the bus coupler and turn the power supply on

again. 13 - not used - 14 Maximum number of Gateway or

Mailbox I/O modules exceeded

Turn off the power supply of the

node, reduce number of Gateway

or Mailbox I/O modules and turn

the power supply on again.

Fault code 2 -not used- Fault argument Fault description Trouble shooting

- not used -

Page 69

Fieldbus coupler 750-342 • 63

LED Display

WAGO-I/O-SYSTEM 750 ETHERNET TCP/IP

Fault code 3: "Internal bus protocol fault" Fault argument Fault description Trouble shooting

- Internal bus communication malfunction; faulty device can’t be detected

If the fieldbus node comprises internal system supply modules (750-613), make sure first that the power supply of these modules is functioning. This is indicated by the status LEDs. If all I/O modules are connected correctly or if the fieldbus node doesn’t comprise 750-613 modules you can detect the faulty I/O module as follows: turn off the power supply of the node. Place the end module in the middle of the fieldbus node. Turn the power supply on again. – If the LED is still blinking, turn off the power supply and place the end module in the middle of the first half of the node (towards the coupler). – If the LED doesn’t blink, turn off the power supply and place the end module in the middle of the second half of the node (away from the coupler). Turn the power supply on again. Repeat this procedure until the faulty I/O module is detected. Replace the faulty I/O module. If there is only one I/O module left but the LED is still blinking, then this I/O module or the coupler is defective. Replace defective component.

Page 70

64 • Fieldbus coupler 750-342 LED Display

WAGO-I/O-SYSTEM 750

ETHERNET TCP/IP

Fault code 4: "Internal bus physical fault" Fault argument Fault description Trouble shooting

- Error in internal bus data communication or interruption of the internal bus at the coupler

Turn off the power supply of the node. Place an I/O module with process data behind the coupler and note the error argument after the power supply is turned on. If no error argument is given by the I/O LED, replace the coupler. Otherwise detect faulty I/O module as follows: turn off the power supply. Place the end module in the middle of the fieldbus node. Turn the power supply on again. – If the LED is still blinking, turn off the power supply and place the end module in the middle of the first half of the node (towards the coupler). – If the LED doesn’t blink, turn off the power supply and place the end module in the middle of the second half of the node (away from the coupler). Turn the power supply on again. Repeat this procedure until the faulty I/O module is detected. Replace the faulty I/O module. If there is only one I/O module left but the LED is still blinking, then this I/O module or the coupler is defective. Replace defective component.

n* Interruption of the internal bus

after the n

process data module.

Turn off the power supply of the node, exchange the (n+1)th process data module and turn the power supply on again.

Fault code 5: "Internal bus initialization fault" Fault argument Fault description Trouble shooting

n* Error in register communication

during internal bus initialization

Turn off the power supply of the node and replace n

process data module and turn the power supply on again.

Page 71

Fieldbus coupler 750-342 • 65

LED Display

WAGO-I/O-SYSTEM 750 ETHERNET TCP/IP

Fault code 6: "Fieldbus specific faults" Fault argument Fault description Trouble shooting

1 No BootP server reply Check the settings of BootP server. 2 Not identified ETHERNET

coupler

Turn off the power supply of the node, exchange fieldbus coupler and turn the power supply on again.

3 Invalid MACID Turn off the power supply of the

node, exchange fieldbus coupler and turn the power supply on again.

4 TCP/IP initialization error Restart the fieldbus coupler by

turning the power supply off and on again. If the error still exists, exchange the bus coupler.

Fault code 7 -not usedFault argument Fault description Trouble shooting

- not used -

Fault code 8 -not usedFault argument Fault description Trouble shooting

- not used -

Fault code 9 "CPU Trap Error" Fault argument Fault description Trouble shooting

1 Illegal Opcode 2 Stack overflow 3 Stack underflow 4 NMI

Error in the program sequence. Contact the WAGO I/O-Support

* The number of blink pulses (n) indicates the position of the I/O module. I/O modules without data are not counted (e.g. supply module without diagnosis)

Example for a fault message; Fault: The 13th I/O module has been removed

1. The "I/O" LED starts the fault display with the first blink sequence (approx. 10 flashes/second).

2. The second blink sequence (1 flash/second) follows the first pause. The "I/O" LED blinks four times and thus signals the fault code 4 (internal bus data fault).

3. The third blink sequence follows the second pause. The "I/O " LED blinks twelve times. The fault argument 12 means that the internal bus is interrupted after the 12th I/O module.

Page 72

66 • Fieldbus coupler 750-342 Fault behavior

WAGO-I/O-SYSTEM 750

ETHERNET TCP/IP

3.1.7.3 Supply voltage status

There are two green LED’s in the coupler supply section to display the supply voltage. The left LED (A) indicates the 24 V supply for the coupler. The right hand LED (B or C) signals the supply to the field side, i.e. the power jumper contacts.

LED Meaning Trouble shooting A

green Operating voltage for the system exists. OFF No operating voltage for the system. Check the supply voltage (24V and 0V).

B or C

green Operating voltage for the power jumper contacts exists. OFF No operating voltage for the the power jumper

contacts.

Check the supply voltage (24V and 0V).

3.1.8 Fault behavior

3.1.8.1 Fieldbus failure

A field bus failure is given i. e. when the master cuts-out or the bus cable is interrupted. A fault in the master can also lead to a fieldbus failure.

A field bus failure is indicated when the red "ERROR"-LED is illuminated. If the watchdog is activated, the fieldbus coupler firmware evaluates the

watchdog-register in the case of fault free communication, and the coupler answers all following MODBUS TCP/IP requests with the exception code 0x0004 (Slave Device Failure).

More information For detailed information on the Watchdog register see Chaper "MODBUS Functions"; "Watchdog (Fieldbus failure)".

3.1.8.2 Internal bus fault

An internal bus fault is created, for example, if an I/O module is removed. If this fault occurs during operation the output modules behave in the same manner as an I/O module stop. The "I/O" LED blinks red. The coupler generates a fault message (fault code and fault argument). After clearing the internal bus fault, restart the coupler by cycling the power. The coupler starts up. The transfer of the process data is then resumed and the node outputs are correspondingly set.

Page 73

Fieldbus coupler 750-342 • 67

Technical Data

WAGO-I/O-SYSTEM 750 ETHERNET TCP/IP

3.1.9 Technical Data

System data

Number of nodes limited by ETHERNET specification Transmission medium

Twisted Pair S-UTP 100 Ω cat. 5 Buscoupler connection RJ45 Max. length of fieldbus segment 100 m between hub station and 750-342;

max. length of network limited by ETHERNET

specification Baud rate 10 Mbit/s Protocols MODBUS/TCP, MODBUS/UDP, HTTP, BootP

Technical Data

No. of I/O modules with bus extension

250 Fieldbus

Input process image max. Output process image max.

max. 512 Byte

max. 512 Byte Configuration via PC Max. no. of socket connections 1 HTTP, 5 MODBUS/TCP Voltage supply DC 24 V (-25 % ... + 30 %) Input currentmax 500 mA at 24 V Efficiency of the power supply 87 % Internal current consumption 200 mA at 5 V Total current for I/O modules 1800 mA at 5 V Isolation 500 V system/supply Voltage via power jumper contacts DC 24 V (-25 % ... + 30 %) Current via power jumper

contactsmax

DC 10 A

Dimensions (mm) W x H x L 51 x 65* x 100 (*from upper edge of DIN 35 rail) Weight ca. 195 g

Accessories

Miniature WSB quick marking system

Standards and Regulations (cf. Chapter 2.2)

EMC CE-Immunity to interference acc. to EN 50082-2 (96) EMC CE-Emission of interference acc. to EN 50081-1 (93) EMC marine applications-Immunity to

interference

acc. to Germanischer Lloyd (1997)

EMC marine applications-Emission of interference

acc. to Germanischer Lloyd (1997)

Approvals (cf. Chapter 2.2)

Page 74

68 • Fieldbus coupler 750-342 Technical Data

WAGO-I/O-SYSTEM 750

ETHERNET TCP/IP

CULUS

(UL508) ABS (American Bureau of Shipping) 1) BV (Bureau Veritas) 1)

DNV (Det Norske Veritas) 1) Cl. B

GL (Germanischer Lloyd) 1) Cat. A, B, C, D KR (Korean Register of Shipping) 1) LR (Lloyd's Register) 1) Env. 1, 2, 3, 4

NKK

NKK (Nippon Kaiji Kyokai) 1) RINA (Registro Italiano Navale) 1)

CULUS

(UL1604) Class I Div2 ABCD T4A DEMKO II 3 G EEx nA II T4

Conformity Marking

Consider chapter: „Supplementary power supply regulations”!

Page 75

Fieldbus Communication • 69 ETHERNET

WAGO-I/O-SYSTEM 750 ETHERNET TCP/IP

4 Fieldbus Communication

4.1 ETHERNET

4.1.1 General

ETHERNET is a technology, which has been proven and established as an effective means of data transmission in the field of information technology and office communication. Within a short time ETHERNET has also made a successful breakthrough in the area of private PC networks throughout the world.

This technology was developed in 1972 by Dr. Robert M. Metcalfe, David R. Boggs, Charles Thacker, Butler W. Lampson, and Xerox (Stanford, Ct.). Standardization (IEEE 802.3) took place in 1983.

ETHERNET predominantly uses coaxial cables or twisted pair cables as a transmission medium. Connection to ETHERNET, often already existing in networks, (LAN, Internet) is easy and the data exchange at a transmission rate of 10 Mbps or for some couplers/controllers also 100 Mbps is very fast.

ETHERNET has been equipped with higher level communication software in addition to standard IEEE 802.3, such as TCP/IP (Transmission Control Protocol / Internet Protocol) to allow communication between different systems. The TCP/IP protocol stack offers a high degree of reliability for the transmission of information.

In the ETHERNET based (programmable) fieldbus couplers and controllers developed by WAGO, usually various application protocols have been implemented on the basis of the TCP/IP stack.

These protocols allow the user to create applications (master applications) with standardized interfaces and transmit process data via an ETHERNET interface.

In addition to a series of management and diagnostic protocols, fieldbus specific application protocols are implemented for control of the module data, depending upon the coupler or controller, e. g. MODBUS TCP (UDP), EtherNet/IP, BACnet, KNXNET/IP, PROFINET, Powerlink, Sercos III or others.

Information such as the fieldbus node architecture, network statistics and diagnostic information is stored in the ETHERNET (programmable) fieldbus couplers and controllers and can be viewed as HTML pages via a web browser (e.g., Microsoft Internet-Explorer, Netscape Navigator) being served from the HTTP server in the couplers and controllers.

Furthermore, depending on the requirements of the respective industrial application, various settings such as selection of protocols, TCP/IP, internal clock and security configurations can be performed via the web-based management system. However, you can also load web pages you have created yourself into the couplers/controllers, which have an internal file system, using FTP.

Page 76

70 • Fieldbus Communication ETHERNET

WAGO-I/O-SYSTEM 750

ETHERNET TCP/IP

The WAGO ETHERNET TCP/IP fieldbus node does not require any additional master components other than a PC with a network card. So, the fieldbus node can be easily connected to local or global networks using the fieldbus connection. Other networking components such as hubs, switches or repeaters can also be used. However, to establish the greatest amount of “determinism” a switch is recommended.

The use of ETHERNET as a fieldbus allows continuous data transmission between the plant floor and the office. Connection of the ETHERNET TCP/IP fieldbus node to the Internet even enables industrial processing data for all types of applications to be called up world-wide. This makes site independent monitoring, visualization, remote maintenance and control of processes possible.

4.1.2 Network Architecture – Principles and Regulations

A simple ETHERNET network is designed on the basis of one PC with a network interface card (NI), one crossover connection cable (if necessary), one ETHERNET fieldbus node and one 24 V DC power supply for the coupler/controller voltage source.

Each fieldbus node consists of a (programmable) fieldbus coupler or controller and a number of needed I/O modules.

Sensors and actuators are connected to the digital or analog I/O modules on the field side. These are used for process signal acquisition or signal output to the process, respectively.

Fig. 4-1. Connection Example and Principle of a Fieldbus Node for a Network Architecture

1Netwerkknotene

Fieldbus communication between master application and (programmable) fieldbus coupler or controller takes place using the implemented fieldbus specific application protocol, e. g. MODBUS TCP (UDP), EtherNet/IP, BACnet, KNXNET/IP, PROFINET, Powerlink, Sercos III or others.

Page 77

Fieldbus Communication • 71 ETHERNET

WAGO-I/O-SYSTEM 750 ETHERNET TCP/IP

4.1.2.1 Transmission Media

General ETHERNET transmission standards

For transmitting data the ETHERNET standard supports numerous technologies with various parameters (e.g., transmission speed, medium, segment length and type of transmission).

1Base5 Uses a 24 AWG UTP (twisted pair cable) for a 1Mbps baseband signal for

distances up to 500 m (250 m per segment) in a physical star topology.

10Base2 Uses a 5 mm 50 Ohm coaxial cable for a 10Mbps baseband signal for distances

of up to 185 m in a physical bus topology (often referred to as Thin ETHERNET or ThinNet).

10Base5 Uses a 10 mm 50 Ohm coaxial cable for a 10Mbps baseband signal for distances

of up to 500 m in a physical bus topology (often referred to as Thick ETHERNET).

10Base-F Uses a fiber-optic cable for a 10Mbps baseband signal for distances of up to

4 km in a physical star topology. (There are three sub-specifications: 10Base-FL for fiber-optic link, 10Base-FB for fiber-optic backbone and 10Base-FP for fiber-optic passive).

10Base-T Uses a 24 AWG UTP or STP/UTP (twisted pair cable) for a 10Mbps baseband

signal for distances up to 100 m in a physical star topology.

10Broad36 Uses a 75 Ohm coaxial cable for a 10Mbps baseband signal for distances of up

to 1800 m (or 3600 m with double cables) in a physical bus topology.

100BaseTX Specifies a 100 Mbps transmission with a twisted pair cable of Category 5 and

RJ45-connectors. A maximum segment of 100 meters may be used.

Tab. 4-1: ETHERNET Transmission Standards

Beyond that there are still further transmission standards, for example: 100Base-T4 (Fast ETHERNET over twisted conductors), 100Base-FX (Fast ETHERNET over fiber-optic cables) or P802.11 (Wireless LAN) for a wireless transmission.

The media types are shown with their IEEE shorthand identifiers. The IEEE identifiers include three pieces of information. The first item, for example, “10”, stands for the media. The third part of the identifier provides a rough indication of segment type or length. For thick coaxial cable, the “5” indicates a 500 meter maximum length allowed for individual thick coaxial segments. For thin coaxial cable, the “2” is rounded up from the 185 meter maximum length for individual thin coaxial segments. The “T” and “F” stand for ‘twisted pair’ and ‘fiber optic’, and simply indicate the cable type.

Page 78

72 • Fieldbus Communication ETHERNET

WAGO-I/O-SYSTEM 750

ETHERNET TCP/IP

10Base-T, 100BaseTX

Either the 10BaseT standard or 100BaseTX can be used for the WAGO ETHERNET fieldbus node. The network architecture is very easy and inexpensive to assemble with SUTP cable as transmission medium or with cables of STP type. Both types of cable can be obtained from any computer dealer.

S-UTP cable (screened unshielded twisted pair) is single-shielded cable of Category 5 with overall shield surrounding all twisted unshielded conductor pairs and an impedance of 100 ohm. STP cable (shielded twisted pair) is cable of Category 5 with stranded and individually shielded conductor pairs; no overall shield is provided.

Wiring of the fieldbus nodes

Maybe, a crossover cable is required for direct connection of a fieldbus node to the network card of the PC.

Fig. 4-2: Direct Connection of a Node with Crossover Cable g012906d

If several fieldbus nodes are to be connected to a network card, the fieldbus nodes can be connected via an ETHERNET switch or hub with straight through/parallel cables.

Fig. 4-3: Connection of a Node by means of a Hub with Parallel cables g012908d

Page 79

Fieldbus Communication • 73 ETHERNET

WAGO-I/O-SYSTEM 750 ETHERNET TCP/IP

An ETHERNET switch is a device that allows all connected devices to

transmit and receive data with each other. The switch can also be viewed as a “data traffic cop” where the hub “polices” the data coming in and going out of the individual ports, so the data will only be transmitted to the required node. WAGO recommends using a switch rather then a hub, this will allow for a more deterministic architecture.

Attention

The cable length between the node and the hub cannot be longer than 100 m (328 ft.) without adding signal conditioning systems (i.e., repeaters). Various possibilities are described in the ETHERNET standard for networks covering larger distances.

4.1.2.2 Network Topologies

In the case of 10Base-T, or 100BaseTX several stations (nodes) are connected using a star topology according to the 10Base-T ETHERNET Standard.

Therefore, this manual only deals with the star topology, and the tree topology for larger networks in more detail.

Star Topology A star topology consists of a network in which all nodes are connected to a

central point via individual cables.

Fig. 4-4: Star Topology G012903e

A star topology offers the advantage of allowing the extension of an existing network. Stations can be added or removed without network interruption. Moreover, in the event of a defective cable, only the network segment and the node connected to this segment is impaired. This considerably increases the fail-safe of the entire network.

Page 80

74 • Fieldbus Communication ETHERNET

WAGO-I/O-SYSTEM 750

ETHERNET TCP/IP

Tree Topology

The tree topology combines characteristics of linear bus and star topologies. It consists of groups of star-configured workstations connected to a linear bus backbone cable. Tree topologies allow for the expansion of an existing network, and enables schools, etc. to configure a network to meet their needs.

Fig. 4-5: Tree Topology G012904e

Page 81

Fieldbus Communication • 75 ETHERNET

WAGO-I/O-SYSTEM 750 ETHERNET TCP/IP

5-4-3 Rule

A consideration in setting up a tree topology using ETHERNET protocol is the 5-4-3 rule. One aspect of the ETHERNET protocol requires that a signal sent out on the network cable must reach every part of the network within a specified length of time. Each concentrator or repeater that a signal goes through adds a small amount of time. This leads to the rule that between any two nodes on the network there can only be a maximum of 5 segments connected through 4 repeators/concentrators. In addition, only 3 of the segments may be populated (trunk) segments if they are made of coaxial cable. A populated segment is one that has one or more nodes attached to it. In Figure 5-5, the 5-4-3 rule is adhered to. The furthest two nodes on the network have 4 segments and 3 repeators/concentrators between them.

This rule does not apply to other network protocols or ETHERNET networks where all fiber optic cabling or a combination of a backbone with UTP cabling is used. If there is a combination of fiber optic backbone and UTP cabling, the rule is simply translated to 7-6-5 rule.

Cabling guidelines

"Structured Cabling" specifies general guidelines for network architecture of a LAN, establishing maximum cable lengths for the grounds area, building and floor cabling.

The "Structured Cabling" is standardized in EN 50173, ISO 11801 and TIA 568-A. It forms the basis for a future-orientated, application-independent and cost-effective network infrastructure.

The cabling standards define a domain covering a geographical area of 3 km and for an office area of up to 1 million square meters with 50 to 50,000 terminals. In addition, they describe recommendations for setting up of a cabling system.

Specifications may vary depending on the selected topology, the transmission media and coupler modules used in industrial environments, as well as the use of components from different manufacturers in a network. Therefore, the specifications given here are only intended as recommendations.

Page 82

76 • Fieldbus Communication ETHERNET

WAGO-I/O-SYSTEM 750

ETHERNET TCP/IP

4.1.2.3 Coupler Modules

There are a number of hardware modules that allow for flexible arrangement for setting up an ETHERNET network. They also offer important functions, some of which are very similar.

The following table defines and compares these modules and is intended to simplify the correct selection and appropriate application of them.

Module Characteristics/application ISO/OSI

layer

Repeater Amplifier for signal regeneration, connection on a physical level. 1 Bridge Segmentation of networks to increase the length. 2 Switch Multiport bridge, meaning each port has a separate bridge

function. Logically separates network segments, thereby reducing network traffic. Consistent use makes ETHERNET collision-free.

2 (3)

Hub Used to create star topologies, supports various transmission

media, does not prevent any network collisions.

Router Links two or more data networks.

Matches topology changes and incompatible packet sizes (e.g. used in industrial and office areas).

Gateway Links two manufacturer-specific networks which use different

software and hardware (i.e., ETHERNET and Interbus-Loop).

4-7

Tab. 4-2: Comparison of Coupler Modules for Networks

Page 83

Fieldbus Communication • 77 ETHERNET

WAGO-I/O-SYSTEM 750 ETHERNET TCP/IP

4.1.2.4 Important Terms

Data security

If an internal network (Intranet) is to be connected to the public network (e.g., the Internet) then data security is an extremely important aspect.

Undesired access can be prevented by a Firewall. Firewalls can be implemented in software or network components. They are interconnected in a similar way to routers as a switching element between Intranets and the public network. Firewalls are able to limit or completely block all access to the other networks, depending on the access direction, the service used and the authenticity of the network user.

Real-time ability

Transmission above the fieldbus system level generally involves relatively large data quantities. The permissible delay times may also be relatively long (0.1...10 seconds). However, real-time behavior within the fieldbus system level is required for ETHERNET in industry. In ETHERNET it is possible to meet the real-time requirements by restricting the bus traffic (< 10 %), by using a master-slave principle, or also by implementing a switch instead of a hub. MODBUS/TCP is a master/slave protocol in which the slaves only respond to commands from the master. When only one master is used, data traffic over the network can be controlled and collisions avoided.

Shared ETHERNET

Several nodes linked via a hub share a common medium. When a message is sent from a station, it is broadcast throughout the entire network and is sent to each connected node. Only the node with the correct target address processes the message. Collisions may occur and messages have to be repeatedly transmitted as a result of the large amount of data traffic. The delay time in a Shared ETHERNET cannot be easily calculated or predicted.

Fig. 4-6: Principle of Shared ETHERNET G012910e

Page 84

78 • Fieldbus Communication ETHERNET

WAGO-I/O-SYSTEM 750

ETHERNET TCP/IP

Deterministic ETHERNET

The TCP/IP software or the user program in each subscriber can limit transmittable messages to make it possible to determine real-time requirements. At the same time the maximum medium message rate (datagrams per second), the maximum medium duration of a message, and the minimum time interval between the messages (waiting time of the subscriber) is limited.

Therefore, the delay time of a message is predictable.

Switched ETHERNET

In the case of Switched Ethernet, several fieldbus nodes are connected by a switch. When data from a network segment reaches the switch, it saves the data and checks for the segment and the node to which this data is to be sent. The message is then only sent to the node with the correct target address. This reduces the data traffic over the network, extends the bandwidth and prevents collisions. The runtimes can be defined and calculated, making the Switched Ethernet deterministic.

Fig. 4-7: Principle of Switched ETHERNET G012909e

Page 85

Fieldbus Communication • 79 ETHERNET

WAGO-I/O-SYSTEM 750 ETHERNET TCP/IP

4.1.3 Network Communication

Fieldbus communication between master application and (programmable) fieldbus coupler or controller usually takes place using an implemented fieldbus specific application protocol, e. g. MODBUS TCP (UDP), EtherNet/IP, BACnet, KNXNET/IP, PROFINET, Powerlink, Sercos III or others.

The protocol layer model helps with an example (MODBUS and EtherNet/IP) to explain the classification and interrelationships between the communication and application protocols. In this example, the fieldbus communication can take place using either the MODBUS protocol or EtherNet/IP.

4.1.3.1 Protocol layer model

(1) Ethernet:

The Ethernet hardware forms the basis for the physical exchange of data. The exchanged data signals and the bus access procedure CSMA/CD are defined in a standard.

(1)

Ethernet

(physical interface, CSMA/CD)

(2) IP:

For the communication the Internet Protocol (IP) is positioned above the Ethernet hardware. This bundles the data to be transmitted in packets along with sender and receiver address and passes these packets down to the Ethernet layer for physical transmission. At the receiver end, IP accepts the packets from the Ethernet layer and unpacks them.

(2)

(1)

Ethernet

(physical interface, CSMA/CD)

(3) TCP, UDP: a) TCP: (Transmission Control Protocol)

The TCP protocol, which is positioned above the IP layer, monitors the transport of the data packets, sorts their sequence and sends repeat requests for missing packets. TCP is a connection-oriented transport protocol. The TCP and IP protocol layers are also jointly described as the TCP/IP protocol stack or TCP/IP stack. b) UDP: (User Datagram Protocol) The UDP layer is also a transport protocol like TCP, and is arranged above the IP layer. In contrast to the TCP protocol, UDP is not connection oriented. That means there are no monitoring mechanisms for data exchange between sender and receiver.

Page 86

80 • Fieldbus Communication ETHERNET

WAGO-I/O-SYSTEM 750

ETHERNET TCP/IP

The advantage of this protocol is in the efficiency of the transmitted data and the resultant increase in processing speed. Many programs use both protocols. Important status information is sent via the reliable TCP connection, while the main stream of data is sent via UDP.

(3)

TCP, UDP

(2)

(1)

Ethernet

(physical interface, CSMA/CD)

(4) Management, Diagnostic and Application Protocols:

Positioned above the TCP/IP stack or UDP/IP layer are correspondingly implemented management, diagnostic and application protocols that provide services that are appropriate for the application. For the management and diagnostic, these are, for example, SMTP (Simple Mail Transport Protocol) for e-mails, HTTP (Hypertext Transport Protocol) for www browsers and some others. In this example, the protocols MODBUS/TCP (UDP) and EtherNet/IP are implemented for use in industrial data communication. Here the MODBUS protocol is also positioned directly above TCP (UDP)/IP; EtherNet/IP, on the other hand, basically consists of the protocol layers Ethernet, TCP and IP with an encapsulation protocol positioned above it. This serves as interface to CIP (Control and Information Protocol). DeviceNet uses CIP in the same way as EtherNet/IP. Applications with DeviceNet device profiles can therefore be very simply transferred to EtherNet/IP.

Application device profiles

(e.g. positioning controllers, semi-

conductors, pneumatic valves) CIP application objects library CIP data management services

(explicit messages, I/O messages)

Mail client

WWW browser

...

CIP message routing, connection

management

CIP

(4)

SMTP

HTTP

...

MODBUS

Encapsulation

protocol

(3)

TCP, UDP

(2)

(1)

Ethernet

(physical interface, CSMA/CD)

ETHERNET/IP

Page 87

Fieldbus Communication • 81 ETHERNET

WAGO-I/O-SYSTEM 750 ETHERNET TCP/IP

4.1.3.2 Communication Protocols

In addition to the ETHERNET standard, the following important communication protocols are implemented in the WAGO ETHERNET based (programmable) fieldbus couplers and controllers:

• IP Version 4 (Raw-IP and IP-Multicast )

• TCP

• UDP

• ARP

The following diagram is intended to explain the data structure of these protocols and how the data packets of the communication protocols Ethernet, TCP and IP with the adapted application protocol MODBUS nested in each other for transmission. A detailed description of the tasks and addressing schemes of these protocols is contained in the following.

Fig. 4-8: Communication Protocols G012907e

Page 88

82 • Fieldbus Communication ETHERNET

WAGO-I/O-SYSTEM 750

ETHERNET TCP/IP

4.1.3.2.1 ETHERNET

ETHERNET address (MAC-ID)

Each WAGO ETHERNET (programmable) fieldbus coupler or controller is provided from the factory with a unique and internationally unambiguous physical ETHERNET address, also referred to as MAC-ID (Media Access Control Identity). This can be used by the network operating system for addressing on a hardware level. The address has a fixed length of 6 Bytes (48 Bit) and contains the address type, the manufacturer’s ID, and the serial number. Examples for the MAC-ID of a WAGO ETHERNET fieldbus coupler (hexadecimal): 00H-30H-DEH-00H-00H-01

ETHERNET does not allow addressing of different networks. If an ETHERNET network is to be connected to other networks, higherranking protocols have to be used.

Note

If you wish to connect one or more data networks, routers have to be used.

ETHERNET Packet

The datagrams exchanged on the transmission medium are called “ETHERNET packets” or just “packets”. Transmission is connectionless; i.e. the sender does not receive any feedback from the receiver. The data used is packed in an address information frame. The following figure shows the structure of such a packet.

Preamble ETHERNET-Header ETHERNET_Data Check sum

8 Byte 14 Byte 46-1500 Byte 4 Byte

Fig. 4-9: ETHERNET-Packet

The preamble serves as a synchronization between the transmitting station and the receiving station. The ETHERNET header contains the MAC addresses of the transmitter and the receiver, and a type field. The type field is used to identify the following protocol by way of unambiguous coding (e.g., 0800

hex

= Internet Protocol).

4.1.3.3 Channel access method

In the ETHERNET Standard, the fieldbus node accesses the bus using CSMA/CD (Carrier Sense Multiple Access/ Collision Detection).

• Carrier Sense: The transmitter senses the bus.

• Multiple Access: Several transmitters can access the bus.

• Collision Detection: A collision is detected.

Each station can send a message once it has established that the transmission medium is free. If collisions of data packets occur due to several stations transmitting simultaneously, CSMA/CD ensures that these are detected and the data transmission is repeated.

Page 89

Fieldbus Communication • 83 ETHERNET

WAGO-I/O-SYSTEM 750 ETHERNET TCP/IP

However, this does not make data transmission reliable enough for industrial requirements. To ensure that communication and data transmission via ETHERNET is reliable, various communication protocols are required.

4.1.3.3.1 IP-Protocol

The Internet protocol divides datagrams into segments and is responsible for their transmission from one network subscriber to another. The stations involved may be connected to the same network or to different physical networks which are linked together by routers. Routers are able to select various paths (network transmission paths) through connected networks, and bypass congestion and individual network failures. However, as individual paths may be selected which are shorter than other paths, datagrams may overtake each other, causing the sequence of the data packets to be incorrect. Therefore, it is necessary to use a higher-level protocol, for example, TCP to guarantee correct transmission.

IP addresses

To allow communication over the network each fieldbus node requires a 32 bit Internet address (IP address).

Attention

Internet addresses have to be unique throughout the entire interconnected networks.

As shown below there are various address classes with net identification (net ID) and subscriber identification (subscriber ID) of varying lengths. The net ID defines the network in which the subscriber is located. The subscriber ID identifies a particular subscriber within this network. Networks are divided into various network classes for addressing purposes:

• Class A: (Net-ID: Byte1, Host-ID: Byte2 - Byte4)

e.g.:

101 . 16 . 232 . 22

01100101 00010000 11101000 00010110 0 Net-ID Host-ID

The highest bit in Class A networks is always ‘0’. Meaning the highest byte can be in a range of ’0 0000000’ to ‘0 1111111’.

Therefore, the address range of a Class A network in the first byte is always

between 0 and 127.

Page 90

84 • Fieldbus Communication ETHERNET

WAGO-I/O-SYSTEM 750

ETHERNET TCP/IP

• Class B: (Net-ID: Byte1 - Byte2, Host-ID: Byte3 - Byte4)

e.g.:

181 . 16 . 232 . 22

10110101 00010000 11101000 00010110 10 Net-ID Host-ID

The highest bits in Class B networks are always ’10’. Meaning the highest byte can be in a range of ’10 000000’ to ‘10 111111’.

Therefore, the address range of Class B networks in the first byte is always between 128 and 191.

• Class C: (Net-ID: Byte1 - Byte3, Host-ID: Byte4)

e.g.:

201 . 16 . 232 . 22

11000101 00010000 11101000 00010110 110 Net-ID Host-ID

The highest bits in Class C networks are always ‘110’. Meaning the highest byte can be in a range of ’110 00000’ to ‘110 11111’.

Therefore, the address range of Class C networks in the first byte is always

between 192 and 223.

Additional network classes (D, E) are only used for special tasks.

Key data

Address range of the Possible number of subnetwork networks Subscribers per network

Class A

1.XXX.XXX.XXX -

126.XXX.XXX.XXX

127 (2

)

Ca. 16 Million

(224)

Class B

128.000.XXX.XXX -

191.255.XXX.XXX

Ca. 16 thousand

)

Ca 65 thousand

(216)

Class C

192.000.000.XXX -

223.255.255.XXX

Ca. 2 million

)

254 (28)

Each WAGO ETHERNET (programmable) fieldbus coupler or controller can be easily assigned an IP address via the implemented BootP protocol. For small internal networks we recommend selecting a network address from Class C.

Attention

Never set all bits to equal 0 or 1 in one byte (byte = 0 or 255). These are reserved for special functions and may not be allocated. Therefore, the address

10.0.10.10 may not be used due to the 0 in the second byte.

Page 91

Fieldbus Communication • 85 ETHERNET

WAGO-I/O-SYSTEM 750 ETHERNET TCP/IP

If a network is to be directly connected to the Internet, only registered, internationally unique IP addresses allocated by a central registration service may be used. These are available from InterNIC (International Network Information Center).

Attention

Direct connection to the Internet should only be performed by an authorized network administrator and is therefore not described in this manual.

Subnets

To allow routing within large networks a convention was introduced in the specification RFC 950. Part of the Internet address, the subscriber ID is divided up again into a subnetwork number and the station number of the node. With the aid of the network number it is possible to branch into internal subnetworks within the partial network, but the entire network is physically connected together. The size and position of the subnetwork ID are not defined; however, the size is dependent upon the number of subnets to be addressed and the number of subscribers per subnet.

1 8 16 24 32

1 0 Net-ID Subnet-ID Host-ID

Fig. 4-10: Class B address with Field for Subnet ID

Subnet mask

A subnet mask was introduced to encode the subnets in the Internet. This involves a bit mask, which is used to mask out or select specific bits of the IP address. The mask defines the subscriber ID bits used for subnet coding, which denote the ID of the subscriber. The entire IP address range theoretically lies between 0.0.0.0 and 255.255.255.255. Each 0 and 255 from the IP address range are reserved for the subnet mask.

The standard masks depending upon the respective network class are as follows:

• Class A Subnet mask:

255

.0 .0 .0

• Class B Subnet mask:

255 .255 .0 .0

• Class C Subnet mask:

255

.255 .255 .0

Depending on the subnet division the subnet masks may, however, contain other values beyond 0 and 255, such as 255.255.255.128 or 255.255.255.248. Your network administrator allocates the subnet mask number to you.

Page 92

86 • Fieldbus Communication ETHERNET

WAGO-I/O-SYSTEM 750

ETHERNET TCP/IP

Together with the IP address, this number determines which network your PC and your node belongs to.

The recipient node, which is located on a subnet initially, calculates the correct network number from its own IP address and the subnet mask. Only then does it check the node number and delivers the entire packet frame, if it corresponds.

Example of an IP address from a class B network:

IP address: 172.16.233.200 10101100 00010000 11101001 11001000 Subnet mask: 255.255.255.128 11111111 11111111 11111111 10000000 Net-ID: 172.16.00 10101100 00010000 00000000 00000000 Subnet-ID: 0.0.233.128 00000000 00000000 11101001 10000000 Host-ID: 0.0.0.72 00000000 00000000 00000000 01001000

Attention

Specify the network mask defined by the administrator in the same way as the IP address when installing the network protocol.

Gateway

The subnets of the Internet are normally connected via gateways. The function of these gateways is to forward packets to other networks or subnets.

This means that in addition to the IP address and network mask for each network card, it is necessary to specify the correct IP address of the standard gateway for a PC or fieldbus node connected to the Internet. You should also be able to obtain this IP address from your network administrator. The IP function is limited to the local subnet if this address is not specified.

IP Packet

In addition to the data units to be transported, the IP data packets contain a range of address information and additional information in the packet header.

IP-Header IP-Data

Fig. 4-11: IP Packet

The most important information in the IP header is the IP address of the transmitter and the receiver and the transport protocol used.

Page 93

Fieldbus Communication • 87 ETHERNET

WAGO-I/O-SYSTEM 750 ETHERNET TCP/IP

4.1.3.3.1.1 RAW IP

Raw IP manages without protocols such as PPP (point-to-point protocol). With RAW IP, the TCP/IP packets are directly exchanged without handshaking, thus enabling the connection to be established more quickly.

However, the connection must beforehand have been configured with a fixed IP address. The advantages of RAW IP are high data transfer rate and good stability.

4.1.3.3.1.2 IP Multicast

Multicast refers to a method of transmission from a point to a group, which is a point-to-multipoint transfer or multipoint connection. The advantage of multicast is that messages are simultaneously transferred to several users or closed user groups via one address. IP multicasting at Internet level is realised with the help of the Internet Group Message Protocol IGMP; neighbouring routers use this protocol to inform each other on membership to the group. For distribution of multicast packets in the sub-network, IP assumes that the datalink layer supports multicasting. In the case of Ethernet, you can provide a packet with a multicast address in order to send the packet to several recipients with a single send operation. Here, the common medium enables packets to be sent simultaneously to several recipients. The stations do not have to inform each other on who belongs to a specific multicast address – every station physically receives every packet. The resolution of IP address to Ethernet address is solved by the use of algorithms, IP multicast addresses are embedded in Ethernet multicast addresses.

4.1.3.3.2 TCP Protocol

As the layer above the Internet protocol, TCP (Transmission Control Protocol) guarantees the secure transport of data through the network.

TCP enables two subscribers to establish a connection for the duration of the data transmission. Communication takes place in full-duplex mode (i.e., transmission between two subscribers in both directions simultaneously). TCP provides the transmitted message with a 16-bit checksum and each data packet with a sequence number. The receiver checks that the packet has been correctly received on the basis of the checksum and then sets off the sequence number. The result is known as the acknowledgement number and is returned with the next self-sent packet as an acknowledgement. This ensures that the lost TCP packets are detected and resent, if necessary, in the correct sequence.

Page 94

88 • Fieldbus Communication ETHERNET

WAGO-I/O-SYSTEM 750

ETHERNET TCP/IP

TCP port numbers

TCP can, in addition to the IP address (network and subscriber address), respond to a specific application (service) on the addressed subscriber. For this the applications located on a subscriber, such as a web server, FTP server and others are addressed via different port numbers. Well-known applications are assigned fixed ports to which each application can refer when a connection is built up.

Examples: Telnet Port number: 23

HTTP Port number: 80

A complete list of "standardized services" is contained in the RFC 1700 (1994) specifications.

TCP segment

The packet header of a TCP data packet is comprised of at least 20 bytes and contains, among others, the application port number of the transmitter and the receiver, the sequence number and the acknowledgement number.

The resulting TCP packet is used in the data unit area of an IP packet to create a TCP/IP packet.

4.1.3.3.3 UDP

The UDP protocol, like the TCP protocol, is responsible for the transport of data. Unlike the TCP protocol, UDP is not connection-orientated; meaning that there are no control mechanisms for the data exchange between transmitter and receiver. The advantage of this protocol is the efficiency of the transmitted data and the resulting higher processing speed.

4.1.3.3.4 ARP

ARP (Address Resolution Protocol). This protocol combines the IP address with the physical MAC address of the respective Ethernet card. It is always used when data transfer to an IP address takes place in the same logical network in which the sender is located.

Page 95

Fieldbus Communication • 89 ETHERNET

WAGO-I/O-SYSTEM 750 ETHERNET TCP/IP

4.1.3.4 Administration and Diagnosis Protocols

In addition to the communication protocols described above, various fieldbus specific application protocols and a view protocols for system admimnistration and diagnosis can be implemented.

• BootP

• HTTP

• DHCP

• DNS

• SNTP

• FTP

• SMTP.

More information You can find a list of the exact available implemented protocols in the chapter "Technical Data" to the fieldbus coupler and/or controller.

4.1.3.4.1 BootP (Bootstrap Protocol)

The BootP protocol defines a request/response mechanism with which the MAC-ID of a fieldbus node can be assigned a fix IP address. For this a network node is enabled to send requests into the network and call up the required network information, such as the IP address of a BootP server. The BootP server waits for BootP requests and generates the response from a configuration database.

The dynamic configuration of the IP address via a BootP server offers the user a flexible and simple design of his network. The WAGO BootP server allows any IP address to be easily assigned for the WAGO (programmable) fieldbus coupler or controller. You can download a free copy of the WAGO BootP server over the Internet at: http://www.wago.com

More information The procedure for address allocation with the WAGO BootP Server is described in detail in the Chapter “Starting up a Fieldbus Node”.

The BOOTP Client allows for dynamic configuring of the network parameters:

Parameter Meaning

IP address of the client Network address of the (programmable) fieldbus

coupler or controller

IP address of the router If communication is to take place outside of the local

network, the IP address of the routers (gateway) is indicated in this parameter.

Subnet mask The Subnet mask makes the (programmable) fieldbus

coupler or controller able to differentiate, which parts of

Page 96

90 • Fieldbus Communication ETHERNET

WAGO-I/O-SYSTEM 750

ETHERNET TCP/IP

the IP address determine the network and which the network station.

IP addresses of the DNS servers

Here the IP addresses can be entered by maximally 2 DNS servers.

Host name Name of the host

When using the bootstrap protocol for configuring the node, the network parameters (IP address, etc... ) are stored in the EEPROM.

Note

The network configuration is only stored in the EEPROM when the BootP protocol is used, although not if configuration is done via DHCP.

The BootP protocol is activated in the (programmable) fieldbus coupler or controller by default.

When the BootP protocol is activated, the (programmable) fieldbus coupler or controller expects a BootP server to be permanently present. If, however, there is no BootP server available after a power-on reset, the network remains inactive. To operate the (programmable) fieldbus coupler or controller with the IP configuration stored in the EEPROM, you must first deactivate the BootP protocol. This is done via the web-based management system on the appropriate HTML page saved in the (programmable) fieldbus coupler or controller, which is accessed via the “Port” link. If the BootP protocol is deactivated, the (programmable) fieldbus coupler or controller uses the parameters stored in the EEPROM at the next boot cycle.

If there is an error in the stored parameters, a blink code is output via the IO LED and configuration via BootP is automatically switched on.

4.1.3.4.2 HTTP (HyperText Transfer Protocol)

HTTP is a protocol used by WWW (World Wide Web) servers for the forwarding of hypermedia, texts, images, audiodata, etc.

Today, HTTP forms the basis of the Internet and is also based on requests and responses in the same way as the BootP protocol.

The HTTP server implemented in the (programmable) fieldbus coupler or controller is used for viewing the HTML pages saved in the coupler/controller. The HTML pages provide information about the coupler/controller (state, configuration), the network and the process image. On some HTML pages, (programmable) fieldbus coupler or controller settings can also be defined and altered via the web-based management system (e.g. whether IP configuration of the coupler/controller is to be performed via the DHCP protocol, the BootP protocol or from the data stored in the EEPROM). The HTTP server uses port number 80.

Page 97

Fieldbus Communication • 91 ETHERNET

WAGO-I/O-SYSTEM 750 ETHERNET TCP/IP

4.1.3.4.3 DHCP (Dynamic Host Configuration Protocol)

The coupler’s/controller’s built-in HTML pages provide an option for IP configuration from a DHCP server, a BootP server, or the data stored in its EEPROM by default.

Note

The network configuration via DHCP is not stored in the EEPROM, this only occurs when using the BootP protocol.

The DHCP client allows dynamic network configuration of the coupler/controller by setting the following parameters:

Parameter Meaning

IP address of the client Network address of the coupler/controller IP address of the

router

If communication is to take place outside of the local network, the IP address of the routers (gateway) is indicated in this parameter.

Subnet mask The Subnet mask makes the coupler/controller able to

differentiate, which parts of the IP address determine the network and which the network station.

IP addresses of the DNS servers

Here the IP addresses can be entered by maximally 2 DNS servers.

Lease time Here the maximum duration can be defined, how long the

coupler/controller keeps the assigned IP address. The maximum lease time is 24.8 days. This results from the internal resolution of timer.

Renewing time The Renewing time indicates, starting from when the

coupler/controller must worry about the renewal of the leasing time.

Rebinding time The Rebinding time indicates, after which time the

coupler/controller must have gotten its new address.

In the case of configuration of network parameters via the DHCP protocol, the coupler/controller automatically sends a request to a DHCP server after initialisation. If there is no response, the request is sent again after 4 seconds, a further one after 8 seconds and again after 16 seconds. If all requests remain unanswered, a blink code is output via the “IO” LED. Transfer of the parameters from the EEPROM is not possible.

Where a lease time is used, the values for the renewing and rebinding time must also be specified. After the renewing time expires, the coupler/controller attempts to automatically renew the lease time for its IP address . If this continually fails up to the rebinding time, the coupler/controller attempts to obtain a new IP address. The time for the renewing should be about one half of the lease time. The rebinding time should be about 7/8 of the lease time.

Page 98

92 • Fieldbus Communication ETHERNET

WAGO-I/O-SYSTEM 750

ETHERNET TCP/IP

4.1.3.4.4 DNS (Domain Name Systems)

The DNS client enables conversion of logical Internet names such as

www.wago.com into the appropriate decimal IP address represented with

separator stops, via a DNS server. Reverse conversion is also possible. The addresses of the DNS server are configured via DHCP or web-based management. Up to 2 DNS servers can be specified. The host identification can be achieved with two functions, an internal host table is not supported.

4.1.3.4.5 SNTP-Client (Simple Network Time Protocol)

The SNTP client is used for synchronization of the time of day between a time server (NTP and SNTP server Version 3 and 4 are supported) and the clock module integrated in the (programmable) fieldbus coupler or controller. The protocol is executed via a UDP port. Only unicast addressing is supported.

Configuration of the SNTP client

The configuration of the SNTP client is performed via the web-based management system under the “Clock” link. The following parameters must be set:

Parameter Meaning

Address of the Time server

The address assignment can be made either over a IP address or a host name.

Time zone

The time zone relative to GMT (Greenwich Mean time). A range of 12 to +12 hours is acceptable.

Update Time

The update time indicates the interval in seconds, in which the synchronization with the time server is to take place.

Enable Time Client

It indicates whether the SNTP Client is to be activated or deactivated.

4.1.3.4.6 FTP-Server (File Transfer Protocol)

The file transfer protocol (FTP) enables files to be exchanged between different network stations regardless of operating system.

In the case of the ETHERNET coupler/controller, FTP is used to store and read the HTML pages created by the user, the IEC61131 program and the IEC61131 source code in the (programmable) fieldbus coupler or controller.

A total memory of 1.5 MB is available for the file system. The file system is mapped to RAM disk. To permanently store the data of the RAM disk, the information is additionally copied into the flash memory. The data is stored in the flash after the file has been closed. Due to the storage process, access times during write cycles are long.

Page 99

Fieldbus Communication • 93 ETHERNET

WAGO-I/O-SYSTEM 750 ETHERNET TCP/IP

Note

Up to 1 million write cycles are possible for writing to the flash memory for the file system.

The following table shows the supported FTP commands for accesses to the file system:

Command Function

USER Identification of the user PASS User password ACCT Account for access to certain files REIN Server reset QUIT Terminates the connection PORT Addressing of the data link PASV Changes server in the listen mode TYPE Determines the kind of the representation for the transferred file STRU Determines the structure for the transferred file MODE Determines the kind o f file transmission RETR Reads file from server STOR Saves file on server APPE Saves file on server (Append mode) ALLO Reservation of the necessary storage location for the file RNFR Renames file from (with RNTO) RNTO Renames file in (with RNFR) ABOR Stops current function DELE Deletes file CWD Changes directory LIST Gives the directory list NLST Gives the directory list RMD Deletes directory PWD Gives the actually path MKD Puts on a dirctory

The TFTP (Trival File Transfer Protocol) is not supported by some of the couplers/controllers.

More information You can find a list of the exact available implemented protocols in the chapter "Technical Data" to the fieldbus coupler and/or controller.

Page 100

94 • Fieldbus Communication ETHERNET

WAGO-I/O-SYSTEM 750

ETHERNET TCP/IP

4.1.3.4.7 SMTP (Simple Mail Transfer Protocol)

The Simple Mail Transfer Protocol (SMTP) enables sending of ASCII text messages to mail boxes on TCP/IP hosts in a network. It is therefore used for sending and receiving e-mails.

The e-mail to be sent is created with a suitable editor and placed in a mail outbasket.

A send SMTP process polls the out-basket at regular intervals and therefore finds mail waiting to be sent. It then establishes a TCP/IP connection with the target host, to which the message is transmitted. The receive SMTP process on the target host accepts the TCP connection. The message is then transmitted and finally placed in an in-basket on the target system. SMTP expects the target system to be online, otherwise no TCP connection can be established. Since many desktop computers are switched off at the end of the day, it is impractical to send SMTP mail there. For that reason, in many networks special SMTP hosts are installed in many networks, which are permanently switched on to enable distribution of received mail to the desktop computers.

4.1.3.5 Application Protocols

If fieldbus specific application protocols are implemented, then the appropriate fieldbus specific communication is possible with the respective coupler/controller. Thus the user is able to have a simple access from the respective fieldbus on the fieldbus node. There are based on ETHERNET couplers/controllers available developed by WAGO, with the following possible application protocols:

• MODBUS TCP (UDP)

• EtherNet/IP

• BACnet

• KNXnet/IP

• PROFINET

• Powerlink

• Sercos III

More information You can find a list of the exact available implemented protocols in the chapter "Technical Data" to the fieldbus coupler and/or controller.

If fieldbus specific application protocols are implemented, then these protocols are individual described in the following chapters.

WAGO 750, 750-342 Series Manual

Specifications and Main Features

Frequently Asked Questions

User Manual