Bus Couplers User Guide

Bus Couplers User Guide
MachinePoint
Bus Couplers User Guide
CTC Parker Automation
50 W. TechneCenter Drive, Milford, Ohio 45150
Phone: 513-831-2340
Technical Support: 513-248-1714
A3-06207-101
Overview and Ordering Information
Copyright and Trademark Notice
Copyright © 2002 by CTC Parker Automation. All rights reserved. No part of this publication may be
reproduced, transmitted, transcribed, stored in a retrieval system, in any form or by any means,
mechanical, photocopying, recording or otherwise, without the prior written consent of CTC Parker
Automation.
While every precaution has been taken in the preparation of this manual, CTC Parker Automation and the
author assume no responsibility for errors or omissions. Neither is any liability assumed for damages
resulting from the use of the information contained herein. All product and company names are
trademarks of their respective companies and licenses.
Product Warranty Information
CTC Parker Automation provides top quality products through rigid testing and the highest quality control
standards. However, should a problem occur with your hardware or with the software protection key, CTC
Parker’s standard product warranty covers these items for 15 months from the date of shipment from
CTC. Exceptions appear below:
•
Backlight bulbs have a 90-day warranty.
•
Third-party products, such as bus cards, carry the manufacturer’s specified warranty.
•
For all displays, image retention (burn-in) is not covered by warranty.
•
Software revisions that occur within 60 days after purchase are available, under warranty,
upon request. Please review the MachineShop License Agreement for additional software
warranty information.
Should you have any questions about your application or need technical assistance, please call CTC
Parker’s Technical Support department at 513-248-1714, 8:00 a.m. to 5:00 p.m., Eastern Time. You may
call this same number after hours for emergency assistance.
Document Conventions
2
Item
Example
File names
MANUAL.DOC
Menus / Menu Items
Insert / Graphic / From file
Paths / Directories
C:\Windows\System
Hyperlinks
http://www.ctcusa.com
Program listings
MaxTsdr_9.6 = 60
MaxTsdr_93.75 = 60
Keys
<Esc> <Enter> (press first key, let go, and press
next key)
<Ctrl+Alt+Del> (press all keys at the same time)
MachinePoint Bus Couplers User Guide
Overview and Ordering Information
Warning Signs
This manual uses the following signs to indicate a safety-related warning:
Death, serious injuries or severe damage to the equipment if relevant
safety precautions are not taken.
Possible death, serious injuries or severe damage to the equipment if
relevant safety precautions are not taken.
Possible light injuries or damage to the equipment if relevant safety
precautions are not taken.
Possible damage to the automation system or the equipment if relevant
warnings are not observed.
Important information on the handling of the automation system or the
respective part in the operating manual.
Please read and follow the safety-related warnings at the end of this User
Guide.
MachinePoint Bus Couplers User Guide
3
Overview and Ordering Information
Contents
1
Overview and Ordering Information ..................................................... 7
1.1 Bus Couplers ............................................................................................................................. 9
2
PROFIBUS-DP ................................................................................ 10
2.1 Fundamentals ..........................................................................................................................10
2.2 Bus coupler MachinePoint EC DP (PROFIBUS-DP)...............................................................12
2.3 BC PROFIBUS-DP Bus Coupler .............................................................................................15
2.3.1
Display and Control Elements ..........................................................................................17
2.3.2
Setting the PROFIBUS Slave Address ............................................................................19
2.4 Compatibility of economy bus coupler EC and bus coupler BC PROFIBUS-DP ....................21
2.5 Interface Connectors ...............................................................................................................22
2.6 PROFIBUS-DP Cable Parameters ..........................................................................................23
2.7 Configuring PROFIBUS-DP.....................................................................................................24
2.8 GSD Files.................................................................................................................................25
2.9 Diagnosis on the PROFIBUS-DP ............................................................................................25
2.10 PROFIBUS-DP Response Times ..........................................................................................26
3
DeviceNet ...................................................................................... 28
3.1 Fundamentals ..........................................................................................................................28
3.2 Bus coupler MachinePoint EC CAN DN (DeviceNet)..............................................................30
3.3 DeviceNet Bus Coupler ...........................................................................................................34
3.4 Interface Connectors ...............................................................................................................39
3.5 DeviceNet Cable Parameters ..................................................................................................40
3.6 Electronic Data Sheet (EDS) ...................................................................................................41
4
Ethernet Modbus/TCP ..................................................................... 42
4.1 Fundamentals ..........................................................................................................................42
4.2 Bus Coupler Ethernet Modbus/TCP ........................................................................................52
4.3 Modbus/TCP Functions ...........................................................................................................58
5
4
Installation ..................................................................................... 74
MachinePoint Bus Couplers User Guide
Overview and Ordering Information
5.1 Mechanical Installation ............................................................................................................74
5.2 Electrical Installation ................................................................................................................78
6
7
User Lockout on BC Bus Couplers .................................................... 85
Operating Modes of BC Bus Couplers................................................ 87
7.1 Overview of Operating Modes .................................................................................................87
7.2 Setting Operating Modes .........................................................................................................88
7.3 RUN .........................................................................................................................................90
7.4 FORCE ....................................................................................................................................91
7.5 TRIGGER.................................................................................................................................94
7.6 LOCK .......................................................................................................................................96
7.7 STOP .......................................................................................................................................98
8
Service and Diagnosis Functions for BC Bus Couplers ........................ 99
8.1 Service Functions ....................................................................................................................99
8.2 What if... ?..............................................................................................................................106
9
10
Error Messages on the BC Bus Coupler Numerical Display ................. 108
Parameterisation and diagnostics functions for all bus couplers .... 109
10.1 Overview ..............................................................................................................................109
10.2 Data structure ......................................................................................................................109
10.3 Sequence.............................................................................................................................110
10.4 Function 0 – Read out group error ......................................................................................111
10.5 Function 1 – Monitor power supply of module.....................................................................112
10.6 Function 2 – Monitor overload of output driver ....................................................................113
10.7 Function 3 – Determine process data width of bus node ....................................................114
10.8 Function 4 – Read out module configuration of bus node...................................................115
10.9 Function 5 – Set preferred disconnection state...................................................................117
10.10 Function 7 – Determine system status of bus node ..........................................................120
10.11 Function 8 – Read out firmware version............................................................................121
10.12 Function 9 – Set data formats for analog modules............................................................121
10.13 Function 10 – Read out sensor information of temperature module .................................123
MachinePoint Bus Couplers User Guide
5
Overview and Ordering Information
10.14 Function 11 – Mode word for temperature module with thermocouples ...........................124
10.15 Function 17 – Read out bus address.................................................................................126
10.16 Function 18 – Switch byte swap mode on/off....................................................................127
10.17 Function 19 – Switch extended PROFIBUS-DP diagnostics function on/off.....................129
10.18 Function 20 – Delete error messages ...............................................................................130
10.19 Function 21 – Store/delete bus node configuration...........................................................131
10.20 Function 255 - Reset .........................................................................................................132
11
Technical Data and Dimensions ................................................. 133
11.1 Environmental Specifications ..............................................................................................133
11.2 Input Signal Delay................................................................................................................133
11.3 Physical Dimensions............................................................................................................135
11.4 Power Consumption ............................................................................................................136
11.5 Data Width and Examples of Address Assignment.............................................................138
12
Appendix ................................................................................ 141
12.1 Glossary...............................................................................................................................141
12.2 Trademarks..........................................................................................................................142
13
Safety-related Information......................................................... 143
13.1 Correct Use of the System...................................................................................................143
13.2 Selection and Qualification of Personnel.............................................................................143
13.3 Configuring, Programming, Installation, Commissioning, and Operation............................144
13.4 Maintenance ........................................................................................................................144
13.5 High Voltages ......................................................................................................................144
14
6
Index...................................................................................... 145
MachinePoint Bus Couplers User Guide
Overview and Ordering Information
1 Overview and Ordering Information
Bus Couplers for PROFIBUS-DP and DeviceNet
Bus couplers are used in the MachinePoint modular system to establish the connection between the I/O
modules of a bus node and the field bus. Bus couplers are available in two varieties: one with basic
economical functionality and the other with full-featured functionality.
MachinePoint module system with MachineLogic PC-based control.
EC
BC
Diagnostic LEDs
+
++
Diagnostic functions
+
++
Keypad/display for service and diagnosis on site
Field bus connection
MachinePoint Bus Couplers User Guide
++
+
+
7
Overview and Ordering Information
Properties of economy bus coupler EC and bus coupler BC
The economy bus coupler EC (EC = Economy) is the basic variant of MachinePoint bus couplers. Apart
from connections for the field bus cable and the power supply, the device also has LED displays to
diagnose the operating state of the bus node.
The bus coupler BC has extended service and diagnostics options available which can be accessed on
site via the integrated keypad and four-digit display. The bus coupler BC thus provides the user with
valuable support during the diagnosis and commissioning of installations and machine components,
before the connection to the field bus and PLC has been implemented.
The bus couplers can be interchanged. In the case of PROFIBUS-DP bus couplers, it is only necessary to
modify the appropriate master device file (GSD file).
Structure of bus nodes
1
Bus coupler
Bus couplers (BC) or economy bus couplers (EC) can be used depending on requirements.
Both variants are available for the field buses PROFIBUS-DP andDeviceNet.
2
Economy bus coupler
3
Extension modules
Up to 8 extension modules with various properties can be used per bus node.
4
Terminal expansion for modules with more than 8 I/O channels
5
Field bus cable
8
MachinePoint Bus Couplers User Guide
Overview and Ordering Information
1.1 Bus Couplers
Bus couplers
PROFIBUS-DP
DeviceNet
MachinePoint BC DP
MachinePoint BC CAN DN
Part no.:
W83-030-0000-1
Part no.:
W83-032-0000-1
MachinePoint EC DP
MachinePoint EC CAN DN
Part no.:
Part no.:
W83-030-0001-1
W83-032-0001-1
Modbus TCP
MachinePoint BC
Ethernet
Part no.:
W83-034-0000-1
MachinePoint Bus Couplers User Guide
9
PROFIBUS-DP
2 PROFIBUS-DP
PROFIBUS was designed in 1983 as an open field bus. PROFIBUS was standardized in 1991 (DIN 19
245) and became a European standard in 1996 (EN 50 170).
PROFIBUS-DP has been specially designed for remote periphery sensor and actuator technology in
production automation.
2.1 Fundamentals
• Only one master allowed.
• You can integrate a Class 2 Master for field bus diagnosis.
• Max. address range for each slave is 244 bytes.
• Individual slaves may fail or shut off during bus operation. However,
all other slaves will continue to operate.
• The complete bus topology is configured and determined in the
master configuration.
• Each slave has a unique manufacturer ID, which is assigned by the
Profibus user organisation.
MachinePoint Bus Couplers User Guide
10
PROFIBUS-DP
Bus topology
• 2-wire topology
• Drop lines at 1.5Mbaud up to 21.7 ft. (6.6m). No drop lines at
12Mbaud.
• Max. 32 slaves per bus segment allowed (including repeater).
• Total of 121 slaves possible if you use up to 3 repeaters and up to 31
slaves per bus segment.
1 Interface module
2 Stations
3 Surge impedance
4 Repeater
MachinePoint Bus Couplers User Guide
11
PROFIBUS-DP
2.2 Bus coupler MachinePoint EC DP (PROFIBUS-DP)
MachinePoint
EC DP
Wiring diagram
X1
1
LED display
2
Rotary switch for setting the slave address
3
Bus connection for PROFIBUS-DP (9 pole, DSUB socket) X1, see diagram
4
Connections for the power supply and routing X1
5
Openings for attaching the equipment label
12
MachinePoint Bus Couplers User Guide
PROFIBUS-DP
Technical data for MachinePoint EC DP
Part no.
W83-030-0001-1
Bus connection
PROFIBUS-DP (9 pole, D-SUB socket)
Power Supply
DC 24 V ± 20%
Residual ripple of power supply
max. 5%
Number of series-connected extension modules
8
See also Technical Data and Dimensions on page 133.
MachinePoint Bus Couplers User Guide
13
PROFIBUS-DP
LED displays on bus coupler EC PROFIBUS-DP
Name
Colour/status
Meaning
RUN
green
The processor of the bus coupler is running.
red/flashing
An error has occurred.
The number of flashes determines the flashing code of the error
messages.
BF
red
No bus connection (bus fail)
Breakage of the field bus cable or the master is not (or is no longer)
operating the bus.
DIA
red
Diagnostics signal
The bus coupler has sent a PROFIBUS-DP diagnostics signal to the
master.
Rotary switch for setting the slave address
on bus coupler EC PROFIBUS-DP
Rotary switch – unit place
Rotary switch – decimal place
Slave addresses can be set in a range between 0 and 99.
The set address becomes active once the operating voltage of the bus coupler has been switched on.
Bus connection on bus coupler EC PROFIBUS-DP
14
MachinePoint Bus Couplers User Guide
PROFIBUS-DP
9 pole, D-SUB
socket
1
SHLD
2
NC
3
B = RxD/TxD-P
4
CNTR-P
5
GND-EXT
6
+5V-EXT
7
NC
8
A = RxD/TxD-N
9
CNTR-N (GND-EXT)
2.3 BC PROFIBUS-DP Bus Coupler
MachinePoint BC DP
MachinePoint Bus Couplers User Guide
15
PROFIBUS-DP
MachinePoint BC DP
Part no.
W83-030-0000-1
Bus connection
PROFIBUS-DP
Power supply
24V DC +/- 20%
Residual ripple (power supply)
max. 5%
Power consumption
< 3W (without I/O modules)
Number of attachable I/O modules
8
See also Technical Data and Dimensions, page 133.
16
MachinePoint Bus Couplers User Guide
PROFIBUS-DP
2.3.1 Display and Control Elements
LED Displays on the Bus Coupler
MachinePoint BC DP
LED
Color
Meaning
RUN
yellow
Bus coupler processor running.
BF
red
No bus connection (bus fail).
Field bus cable break, or the DP master is not operating the bus
anymore.
DIA
red
Diagnosis message sent.
The bus coupler has sent a PROFIBUS-DP diagnosis message
to the DP master.
5V
yellow
Internal 5V power supply OK.
Operating Mode Display on the Bus Coupler
For an Overview of Operating Modes, see page 87.
MachinePoint Bus Couplers User Guide
17
PROFIBUS-DP
Numerical Display on the Bus Coupler
Active operating mode
RUN mode.
In RUN mode, you also can display details on the TRIGGER and
LOCK modes.
STOP mode.
In the Display, TRIGGER, FORCE and LOCK modes, the selected
channel is displayed as follows:
1. I/O module number (hexadecimal)
2. Input (E) or output (A)
3. Channel number (decimal)
Example: 2E04: module 2, input, channel 04
Errors
Error messages are displayed when errors occur.
Example E004: Internal data transfer bus coupler <---> module
interrupted.
18
MachinePoint Bus Couplers User Guide
PROFIBUS-DP
Bus Coupler Keypad
The keypad is multifunctional. The different functions are described in the
relevant sections of this User Guide.
2.3.2 Setting the PROFIBUS Slave Address
You can set slave addresses from 3 to 126.
Checking and setting
With Service function 12 as follows:
1. Select STOP mode, (then press both Address keys simultaneously.
The slave address will be displayed with a number between 3 and
126.
MachinePoint Bus Couplers User Guide
19
PROFIBUS-DP
2. If you do not want to change the address, press OK.
When you change an address, the keys should have the following
values:
Pressing the OK key stores the set slave address in the bus coupler.
To activate the new slave address
•
20
Switch the operating voltage off/on.
MachinePoint Bus Couplers User Guide
PROFIBUS-DP
2.4 Compatibility of economy bus coupler EC and
bus coupler BC PROFIBUS-DP
It is possible to interchange the bus couplers. A modification of the PROFIBUS master configuration is
required in this case. The following table outlines the differences in the main features and variations
during operation.
Features
Bus coupler EC
Bus coupler BC
DP slave address
0 - 99
3 - 126
DP identifier
055B hex
0755 hex
Switch off
parameterisation and
diagnostics functions
EC is not configured.
In systems using GSD, the BC is not
configured. Service function 5 is a
decisive factor in systems using GSD.
Store bus node
configuration
Parameterisation and
diagnostics function 21
Service function 6
Error display
RUN LED flashes red, the
number of flashes denotes the
error code.
The error number is indicated on the
display.
Set the data width for
counter and positioning
modules
Set the data width during the
configuration.
Set the data width using the
configuration and with service function
13.
MachinePoint Bus Couplers User Guide
21
PROFIBUS-DP
2.5 Interface Connectors
We recommend using ERbic® interface connectors from ERNI.
1 ERbic® PROFIBUS node grey,
2 ERbic® PROFIBUS terminator yellow,
3 Shielded cable, cable parameters see below
9-pin subminiature interface connectors
If you use other connectors, wire the bus nodes and terminators as
follows:
1 PROFIBUS node, 9-pin, subminiature, pin contact
2 PROFIBUS terminator, 9-pin, subminiature, pin contact
3 Shielded cable, cable parameters, see below
* Use direct-axis inductances of 110nH with baud rates > 1.5Mbaud
22
MachinePoint Bus Couplers User Guide
PROFIBUS-DP
2.6 PROFIBUS-DP Cable Parameters
The properties of the bus line are specified in EN 50170 as cable type A.
Parameter
Value
Surge impedance
135-165 Ω
Capacitance per unit length
<30 pF/m
Loop resistance
110 Ω/km
Core diameter
0.03 in. (0.64mm)
Core cross-section
>0.01 in. (0.34mm )
2
2
These cable parameters allow the following max. extensions of a bus
segment:
Cable lengths
MachinePoint Bus Couplers User Guide
Baud rate (kbit/s)
Max. cable length
9.6
3936 ft. (1200m)
19.2
3936 ft. (1200m)
93.75
3936 ft. (1200m)
187.5
3280 ft. (1000m)
500
1312 ft. (400m)
1500
656 ft. (200m)
12000
328 ft. (100m)
23
PROFIBUS-DP
2.7 Configuring PROFIBUS-DP
Perform the following steps:
1. Load the GSD file using the configurator or programming system.
2. Configure the PROFIBUS-DP master system:
•
Define the baud rate, highest L2 address etc.
•
Specify the bus address for the PROFIBUS-DP master.
3. Configure the I/O setup of the bus node.
4. Define the bus address.
5. Define the input/output address of the bus node.
6. Set the defined bus node address on the bus coupler.
7. Transfer the configuration into the PROFIBUS-DP master.
8. Program the PROFIBUS-DP master controller:
•
Read the PROFIBUS-DP input data.
•
Write the PROFIBUS-DP output data.
9. Start up the system.
You can download GSD files from our web site at www.ctcusa.com. Click
on the Support link, and then click on MachinePoint GSD Files.
24
MachinePoint Bus Couplers User Guide
PROFIBUS-DP
2.8 GSD Files
You can download the files for all MachinePoint units free of charge from
our web site at www.ctcusa.com. Click on the Support link.
2.9 Diagnosis on the PROFIBUS-DP
The bus coupler provides the PROFIBUS-DP standard diagnosis in bytes
1 to 6.
Byte
Bit
Abbreviation
Description
1
0
non_exist
Slave does not exist (sets master)
1
station_not_ready
Slave not ready for data exchange
2
cfg_fault
Configuration data of master and slave does not
match
3
ext_diag
There are advanced diagnosis bytes
5
invalid_slave_response
Always set to 0 by slave
4
2
6
prm_fault
Faulty parameterizing
7
master_lock
Slave parameterized by a master
0
prm_req
Slave must be re-parameterized
1
stat_diag
Static diagnosis
2
Always 1
3
wd_on
4
freeze_mode
Freeze instruction active
5
sync_mode
Sync instruction active
6
7
3
Reserved
slave_deactivated
0 ... 6
7
Watchdog monitoring active
1 if slave deactivated by master
Reserved
ext_diag_overflow
Master or slave has too much diagnosis data
Advanced Diagnosis
Byte
Description
4
Master address
5, 6
ID
.
MachinePoint Bus Couplers User Guide
25
PROFIBUS-DP
Byte
Description
7
Length of advanced diagnosis
Bit no.
9
Bit information on 24V DC module supply (as diagnosis code 1)
Reserved
8
0
.
.
5
Module 0 without voltage supply
.
.
Module 5 without voltage supply
6
Reserved
7
Reserved
Bit information module overloaded (as diagnosis code 2)
Reserved
10
11
12
0
.
.
5
Module 0 output driver overload
.
.
Module 5 output driver overload
6
Reserved
7
Reserved
Error code (corresponds to error code display on the bus coupler)
2.10 PROFIBUS-DP Response Times
The response time is defined as the total time of a message cycle
between the master and an individual slave.
A message cycle consists of a request telegram to the slave, mandatory
bus idle times and the response time of the slave.
The bus cycle time is the sum of all the message cycles.
To calculate the response time:
26
12Mbaud
28µs + 1µs/data byte to be transmitted
1.5Mbaud
224µs + 7µs/data byte to be transmitted
MachinePoint Bus Couplers User Guide
PROFIBUS-DP
Example:
10 bus nodes with 8 bytes of output data and 8 bytes of input data each.
12Mbaud:
28 + 8 + 8 = 44µs
Response time
44 * 10 = 440µs
Bus cycle time
1.5Mbaud:
224 + (7*8) + (7*8) = 336µs
336 * 10 = 3.4ms
Response time
Bus cycle time
Add a manufacturer-specific run time in the DP master (typically 1 - 3
ms).
Therefore, the duration of a bus cycle in which all slaves are contacted
once
is approx. 2 - 4 ms at 12 Mbaud.
See Section 11.2 on page 133 for Input Signal Delay information.
MachinePoint Bus Couplers User Guide
27
DeviceNet
3 DeviceNet
DeviceNet is a simple network solution. It is based on an open network
standard that is internationally recognized and used.
The DeviceNet protocol represents ISO Application Layer 7 and is based
on the Controller Area Network (CAN) data transmission protocol. CAN is
a data transmission protocol to ISO DIS 11898. It is implemented in
integrated circuits and has been marketed globally since 1994 in very
large quantities by an international consortium of companies.
3.1 Fundamentals
• Up to 64 nodes possible
• Simple linear bus topology
• Multi-cast, master-slave, multi-master possible
• Polling or event message
• Power supply and signal line in one cable
• Network length depends on transmission rate
Bus Topology
Nodes are connected by a trunk line and drop lines.
The trunk line is not split, and there is a terminating resistor at each end
of the line.
MachinePoint Bus Couplers User Guide
28
DeviceNet
MachinePoint Bus Couplers User Guide
29
DeviceNet
3.2 Bus coupler MachinePoint EC CAN DN
(DeviceNet)
MachinePoint EC
CAN DN
Wiring diagram
1
3.2.1 LED display on bus coupler
2
3.2.2 DIP switch for setting the node number
(NODE ID), the data transmission rate (BAUD) and
the diagnostics function (DIA)
3
Bus connection X2: 5 pole, open style connector
4
Connection X1 for the power supply
5
Openings for attaching the equipment label
30
MachinePoint Bus Couplers User Guide
DeviceNet
Technical data for MachinePoint EC
CAN DN
Part no.
W83-032-0001-1
Bus connection
DeviceNet
Power supply of module
DC 24 V +/- 20%
Power supply of CAN interface
DC 11 ... 30 V
(complies with CAN DeviceNet specification)
Residual ripple of power supply
max. 5%
Number of series-connected extension modules
8
See also Technical Data and Dimensions on page 133.
MachinePoint Bus Couplers User Guide
31
DeviceNet
3.2.1 LED display on bus coupler EC DeviceNet
Name
Colour/status
Meaning
RUN
green
The processor of the bus coupler is running.
red/flashing
An error has occurred.
The number of flashes determines the flashing code of the error
messages.
off
The bus coupler has not yet concluded the “DUP MAC Check”
successfully.
green/
The bus coupler is functioning on the bus but has not yet been
detected by a master or a logical connection has not yet been
established to the bus coupler.
NET
(network
status)
flashing
green
The bus coupler has been detected by a master and a logical
connection to the bus coupler has been established.
red/flashing
The master connection is in the time-out state.
red
The bus coupler has found another device with the same MAC ID
during the “DUP MAC Check”.
(module
green/
The field bus connection has been interrupted.
status)
flashing
The PLC is in STOP mode.
MOD
The master is trying to establish the link to the bus connection.
The configured I/O size in the scan list does not match (error 77 on
the scanner).
There is an error message on the display (e.g. E006 for cable
breakage).
green
The bus coupler is ready and the PLC is in RUN mode.
red
One of the extension modules has an unknown identifier.
The internal system bus has been interrupted (contact slide has been
opened).
Too many extension modules have been connected.
red/flashing
32
The internal EEPROM has an error or the bus coupler has determined
that the I/O structure has been modified since the last time the module
was switched on (E012).
MachinePoint Bus Couplers User Guide
DeviceNet
3.2.2 DIP switch
NODE ID – Setting the node number
The node number is set with DIP switches 1 to 6. The setting is binary. DIP1 is the least significant bit 20;
DIP6 is the most significant bit 25. Node numbers can be set in the range 0 to 63.
Example for the MAC IDs 1, 5 and 63
NODE ID DIP1
DIP2
DIP3
DIP4
DIP5
DIP6
1
on
off
off
off
off
off
5
on
off
on
off
off
off
63
on
on
on
on
on
on
BAUD – Setting the data transmission rate
The data transmission rate is set with DIP7 and DIP8.
BAUD
DIP7
DIP8
125 kBaud
off
off
250 kBaud
on
off
500 kBaud
off
on
invalid*
on
on
*Automatically set to 125 kBaud.
Switching the diagnostics function on/off
DIA
DIP9
Reserved
DIP10
Diagnostics function on/off
3.2.3 Bus connection on bus coupler EC DeviceNet
1
V-
CAN_GND
Ground / 0 V
2
L
CAN_L
CAN Low
3
DR
(CAN_SHLD)
Optional shield connection
4
H
CAN_H
CAN High
5
V+
CAN_V+
Power supply
Nominal value DC +24 V
(+18 V to +30 V )
MachinePoint Bus Couplers User Guide
33
DeviceNet
3.3 DeviceNet Bus Coupler
MachinePoint BC CAN DN
Blk
Blu
Bare
Wht
Red
Black
Blue
Bare
White
Red
MachinePoint BC CAN DN
Part no.
W83-032-0000-1
Bus connection
DeviceNet
Power supply to module
24V DC +/- 20%
Power supply to CAN interface
DC 11 ... 30V
(meets CAN DeviceNet specification)
Residual ripple (power supply)
max. 5%
Power consumption
< 3W (without I/O modules)
Number of attachable I/O modules
8
See also Technical Data and Dimensions on page 133.
34
MachinePoint Bus Couplers User Guide
DeviceNet
3.3.1 Display and Control Elements
LED Displays on the Bus Coupler
MachinePoint BC CAN DN
LED
Color
Meaning
NET
green/red
Network status indicates the state of the communication connection to
the master
OFF
The bus coupler is not switched on. Check the 5V LED. Or the bus
coupler has not yet successfully completed the “DUP MAC Check.”
green, flashing
The bus coupler is operating on the bus, but has not yet been detected
by the master. Or a logical connection to the bus coupler has not been
established.
Bus coupler has been detected by a master, and a logical
connectionhas been established.
green
red, flashing
red
MOD
green/red
The master connection is in a Time-Out state.
In "DUP MAC Check," the bus coupler has found another device with
the same MAC ID.
Module status indicates that the bus coupler is ready for operation.
green, flashing
Possible causes:
The field bus connection has been interrupted.
The PLC is in STOP mode (IdLE on the display).
The master is trying to establish a connection to the bus coupler.
The I/O quantity configured in the scan list is incorrect (error 77 on theb
scanner).
An error message appears on the display (e.g., E006 for broken cable)
which you can acknowledge by pressing OK.
green
red
The bus coupler is ready, and the PLC is in RUN mode.
The bus coupler has detected one of the following errors:
One of the I/O modules has an unknown ID.
The internal system bus has been interrupted (orange slide contact has
been opened).
Too many I/O modules attached (>16).
The internal EEPROM has an error, or the bus coupler has detected a
change in the I/O configuration since the last time it was switched on
(E012).
red, flashing
MachinePoint Bus Couplers User Guide
35
DeviceNet
LED
Color
Meaning
5V
RUN
yellow
yellow
The internal power supply works fine.
The CPU in the bus coupler works fine.
Operating Mode Display on the Bus Coupler
For a description of the Operating Mode Display on the Bus Coupler, see
page 17.
Numerical Display on the Bus Coupler
Active operating mode
RUN mode.
In RUN mode, you can also display details on the TRIGGER and
LOCK modes.
36
MachinePoint Bus Couplers User Guide
DeviceNet
STOP mode.
In the Display, TRIGGER, FORCE and LOCK modes, the selected
channel is displayed as follows:
1. I/O module number (hexadecimal)
2. Input (E) or output (A)
3. Channel number (decimal)
Example 2E04: module 2, input, channel 04
Errors
Error messages are displayed when errors occur.
Example E004: Internal data transfer bus coupler <---> module
interrupted.
See also Error Messages on the BC Bus Coupler Numerical Display,
page 108.
Bus Coupler Keypad
The keypad is multifunctional. The different functions are described in the
relevant sections of this User Guide.
MachinePoint Bus Couplers User Guide
37
DeviceNet
3.3.2 Setting the DeviceNet MAC ID
You can set addresses from 0 to 63.
1. Select STOP mode (see Setting Operating Modes, page 88), then
press both Address keys simultaneously.
The MAC ID will be displayed with a number between 0 and 63.
2. If you do not want to change the address, press OK.
When you change an address, the keys have the following values:
Pressing the OK key stores the set MAC ID in the bus coupler and
activates it immediately!
38
MachinePoint Bus Couplers User Guide
DeviceNet
3.3.3 Setting the Data Transmission Rate
Set the data transmission rate with Service function 12 Display/set bus
address (see page 104).
3.4 Interface Connectors
Blk
Blu
Bare
Wht
Red
Black
Blue
Bare
White
Red
According to the DN specification, the power supply to the CAN interface
must be connected via the V+ and V- terminals. The power supply rated
+24V DC must be at a level between +11V and +25V.
Terminating Resistors
A 120Ω terminating resistor must be fitted at each end of the trunk line
between CAN Low (pin2) and CAN High (pin4).
MachinePoint Bus Couplers User Guide
39
DeviceNet
3.5 DeviceNet Cable Parameters
Cable Types
Cable type
Outside
diameter
Application
Thick cable
0.5 in. (12.2mm)
Trunk line
Thin cable
0.3 in. (6.9mm)
Drop lines
The thick DeviceNet cable consists of two shielded, twisted pair lines with
a wire in the middle of the cable. Shielding is outside. The trunk line is not
split.
The thin cable is more flexible. Installation is easier, as is desired for drop
lines. It can also be used as a trunk line over short distances.
On both cable types, the blue/white twisted pair is used for signal
transmission, and the black/red pair for the power supply.
Cable Lengths
The cable length depends on the data transmission rate used.
Cable lengths
Data transmission
rate
125 kbaud
250 kbaud
500 kbaud
Thick trunk line
1640 ft. (500m)
820 ft.(250m)
328 ft. (100m)
Thin trunk line
328 ft. (100m)
328 ft. (100m)
328 ft. (100m)
Max. length of a
single drop line
19.7 ft. (6m)
19.7 ft. (6m)
19.7 ft. (6m)
Total length of all
drop lines
511.7 ft. (156m)
255.8 ft. (78m)
124.6 ft. (39m)
See Section 11.2 on page 133 for Input Signal Delay.
40
MachinePoint Bus Couplers User Guide
DeviceNet
If thin and thick cables are applied for the trunk line, the following applies:
3.6 Electronic Data Sheet (EDS)
You can download GSD/EDS files from our web site at www.ctcusa.com.
Click on the Support link, and then click on MachinePoint GSD Files.
MachinePoint Bus Couplers User Guide
41
Ethernet Modbus/TCP
4 Ethernet Modbus/TCP
4.1 Fundamentals
A simple ETHERNET network is designed on the basis of one PC with a
network card (NI), one connection cable, one ETHERNET fieldbus node
and one 24 V DC power supply for the coupler voltage source. Each
fieldbus node consists of an ETHERNET fieldbus coupler and I/O
modules. The individual bus modules are connected to the ETHERNET
fieldbus coupler via an internal bus when they are snapped onto the
carrier rail. It is possible to connect 8 extension modules to an
MachinePoint ETHERNET bus coupler.
The bus coupler detects all connected modules, creating a local process
image of them. This can consist of a mixed arrangement of analog (data
exchange of words) and digital (data exchange of bits) bus modules.
Fieldbus communication between the master application and the bus
coupler takes place via the MODBUS/TCP protocol. MODBUS/TCP maps
create an image of the distributed MODBUS protocol on ETHERNET.
The process data can be read and written via MODBUS/TCP. Numerous
applications such as HMI, SCADA, PLC, Soft PLC already use this.
Transmission Media
General ETHERNET transmission standards
For transmitting data the ETHERNET standard supports numerous
technologies with various parameters of which differ from each other
such as i.e. transmission speed, medium, segment length and type of
transmission.
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).
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).
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.
10Base-F
Uses a fiber-optic cable for a 10Mbps baseband
signal for distances of up to 4 km in a physical
star topology.
MachinePoint Bus Couplers User Guide
42
Ethernet Modbus/TCP
(There are three subspecifications: 10Base-FL for
fiber-optic link, 10Base-FB for fiber-optic
backbone and 10Base-FP for fiber-optic passive).
ETHERNET transmission standards
The four media types are shown with their IEEE shorthand identifiers.
The IEEE identifiers include three pieces of information. The first item,
«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.
Base-T (10Base-T and 100Base-T)
Base-T standard is used for the MachinePoint ETHERNET fieldbus
coupler. This allows for simple and economical network architecture
using STP/UTP cable as the transmission medium. STP is shielded
twisted pair category 5 cables (CAT 5). UTP is twisted pair without
shielding implemented.
Parameter
10Base-T
100Base-T
Medium
Twisted-Pair
Twisted-Pair
Signaling
Technology Baseband
Technology Baseband
Signaling
code Manchester encoding
code Manchester encoding
Bit rate (Mbit / s)
10/100
100
Topology
Star
Star
Max. segment length (m)
100
100
Max. packet size (Byte)
1512
1512
Min. packet size (Byte)
64
64
Important parameters of the 10Base-T and 100Base-T ETHERNET
standards
Wiring of the fieldbus nodes with Base-T technology
A crossover cable is required for direct connection of a fieldbus node to
the network card of the PC. Cabling connections are shown in the
following illustration:
MachinePoint Bus Couplers User Guide
43
Ethernet Modbus/TCP
Direct connection of a node with crossover cable
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.
Connection of nodes by means of a switch. In this case, parallel cables
have to be used.
NOTE
The cable length between the node and the hub can not 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.
Network Topologies
In the case of 10Base-T several stations (nodes) are connected using a
star to-pology 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.
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
44
MachinePoint Bus Couplers User Guide
Ethernet Modbus/TCP
segment and the node connected to this segment is impaired. This
considerably increases the fail-safe of the entire network.
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.
The 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 time interval. 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 which 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.
MachinePoint Bus Couplers User Guide
45
Ethernet Modbus/TCP
Cabling guidelines
So-called Structured Cabling specifies general guidelines for network
architecture of a LAN, establishing maximum cable lengths for the
grounds area, building and floor cabling.
Standardized in the standards EN 50173, ISO 11801 and TIA 568-A,
«Structured Cabling» forms the basis for a future-orientated, applicationindependent and cost-effective network infrastructure. 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.
CAUTION
Data security If an internal network (Intranet) is to be connected to the public
network (i.e. Internet) then data security is an extremely important aspect.
Undesired access can be prevented by means of a Firewalls which can be
implemented in software or network components. Firewalls can be configured to
limit or completely block all access to the other networks.
Direct connection to the Internet should only be performed by an authorized
network administrator and is therefore not described in this manual.
Real-time ability
In ETHERNET it is possible to meet the real-time requirements of
industrial applications. This can be done by restricting bus traffic, by
using the master-slave principle, or 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.
ETHERNET Hardware Address (MAC-ID)
As with regards to the ISO 8802 Standards, each MachinePpoint
ETHERNET bus coupler is provided ex works with an unique and
internationally unambiguous physical ETHERNET address called MAC-ID
(Media Access Control Identity). The network operating system uses this
MAC-ID for addressing fieldbus nodes on 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. In case of
MachinePoint ETHERNET bus couplers, this MAC ID has the following
form:
00-07-17-01-xx-xx
46
MachinePoint Bus Couplers User Guide
Ethernet Modbus/TCP
ETHERNET does not allow addressing of different networks. If an
ETHERNET network is to be connected to other networks, higher-ranking
protocols have to be used.
NOTE
If you wish to connect one or more data networks, routers have to be used.
ETHERNET Packet
The telegrams 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
so-called telegram (sometimes referred to as «datagram»). The following
table shows the structure of such a packet.
Preamble
Header
Data
Checksum
8 Byte
14 Byte
46-1500
Byte 4 Byte
ETHERNET-Packet
The preamble serves as a synchronization between the transmitting and
receiving station. The ETHERNET header contains the MAC-IDs 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 (i.e. 0800hex = Internet Protocol).
IP addresses
ETHERNET classes
To allow communication over the network each fieldbus node requires a
32 bit Internet address (IP address).
NOTE
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 five different network classes, as shown in the
table on the following table.
MachinePoint Bus Couplers User Guide
47
Ethernet Modbus/TCP
Network class
Bit 1
Bit 2
Bit 3
Bit 4
class A
0
class B
1
0
class C
1
1
0
class D
1
1
1
0
class E
1
1
1
1
Bit 5
0
The five ETHERNET network classes.
Classes in italic denote the commonly used classes, classes D and E are
used for special purposes only.
The free cells in the table are not relevant to the network class and are
used for network address. Therefore a different number of bits are
available for the network class (network ID) and the user address (host
ID), it depends which class is used.
Network class
Class
Network ID
Host ID
class A
1 bit
7 bit
24 bit
class B
2 bit
14 bit
16 bit
class C
3 bit
21 bit
8 bit
class D
4 bit
28 bit multicast ID
class E
5 bit
27 bit (reserved)
Segmentation of IP address into class, network and host ID.
IP addresses can be entered in decimal, octal or hexadecimal form. In
decimal form, the bytes are separated by dots (dotted decimal notation)
to show the logical grouping of individual bytes.
Each MachinePoint ETHERNET bus coupler can be easily assigned an
IP address via the implemented BootP protocol.
NOTE
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. I.e. the address 10.0.10.10 may
not be used due to the 0 in the second byte.
48
MachinePoint Bus Couplers User Guide
Ethernet Modbus/TCP
Address Combinations
The descripton above implies certain definite ranges for the individual
classes as follows:
class A: 0.0.0.0 to
127.255.255.255
class B: 128.0.0.0
to
191.255.255.255
class C: 192.0.0.0
to
223.255.255.255
class D: 224.0.0.0
to
239.255.255.255
class E: 240.0.0.0
to
247.255.255.255
Special-purpose IP addresses
The following addresses should not be used as standard IP addresses
since they are reserved for special purposes, as described below.
Loop-back function: 127.x.x.x Addresses
These class A network addresses are reserved for a loop-back function
on all computers, regardless of the network class. This loop back function
may only be used on networked computers for internal test purposes. If a
telgramm is addressed to a computer with the value 127 in the first byte,
the receiver immediately send the telegram back to the sender.
The correct installation and configuration of the TCP/IP software, for
example, can be checked in this way.
The first and second layers of the OSO/OSI model are not included in the
test and should therefore be tested separately using the ping function.
Broadcast Address: Value 255 in the byte
(010.255.255.255, 190.03.255.01, or 255,255,255,255)
Value 255 is defined as a broadcast address. The telegramm is therefore
sent to all the computers that are in the same part of the network.
Specific network ID: 0.x.x.x Addresses
Value 0 is the ID of a specific network. If the IP address starts with a
zero, the receiver is in the same network. Example: 0.1.0.50 refers to
device 1.0.50 in this network.
Subnet Mask
Large networks are divided into subnetworks by routers and gateways.
Subnet masks were introduced to encode the subnets of 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 depend on the respective network class. See the
following table:
MachinePoint Bus Couplers User Guide
49
Ethernet Modbus/TCP
Class A
255 .0 .0 .0
Class B
255 .255 .0 .0
Class C
255 .255 .255 .0
Standard subnet masks for common ETHERNET classes
For more detailed information concerning allocation of subnet masks to
bus nodes, please contact your network administrator.
NOTE
Specify the network mask defined by the administrator in the same way as the IP
address when installing the network protocol.
50
MachinePoint Bus Couplers User Guide
Ethernet Modbus/TCP
Application Protocols
In addition to the communication protocols described above, various
application protocols are implemented in the MachinePoint ETHERNET
Coupler. These protocols allow the user easy access to the fieldbus
nodes:
•
a MODBUS/TCP server
•
a DHCP server
MODBUS/TCP
MODBUS/TCP is a manufacturer-independent, open fieldbus standard
for diverse applications in manufacturing and process automation.
The MODBUS/TCP protocol is a variation of the MODBUS protocol,
which was optimized for communication via TCP/IP connections. This
protocol was designed for data exchange in the field level, i.e. for the
exchange of I/O data in the process image.
All MODBUS data packets are sent via a TCP connection with the port
number 502.
The MODBUS/TCP in the MachinePoint ETHERNET bus coupler allows
digital and analog output data to be directly read out at a fieldbus node
and special functions to be executed by way of simple function codes
from three stations simultaneously.
Dynamic Host Configuration Protocol (DHCP)
The DHCP protocol is a client/server protocol which reduces the effort of
assigning IP addresses and other networking parameters. With DHCP, a
network administrator can centrally manage and maintain all TCP/IP
configuration parameters. With DHCP, terminals (bus couplers) can be
configured dynamically and automatically. The connected DHCP clients
request IP addresses from the DHCP server, which takes the addresses
from an address pool.
DHCP an be viewed as extension of the older Bootstrap (BootP) protocol
since it supports several BootP commands as well as the BootP-relayagents, which are defined in the BootP protocol. DHCP is considered
more secure and easier to handle than the older Bootstrap protocol.
The DHCP protocol defines a request/response mechanism with which
the MAC-ID of a fieldbus node can be assigned an IP address. To do
this, a network node is enabled to send requests into the network and call
up the required network information.
The dynamic configuration of the IP address offers the user a flexible and
simple design of his network. The MachinePoint ETHERNET DHCP
server allows any IP address to be easily assigned to the MachinePoint
ETHERNET bus coupler.
MachinePoint Bus Couplers User Guide
51
Ethernet Modbus/TCP
4.2 Bus Coupler Ethernet Modbus/TCP
MachinePoint ETHERNET
Part no.
W83-034-0000-1
Bus connection
Ethernet (MODBUS/TCP) via RJ45 jack, 10/100Base-Tx
Supply voltage
DC 24 V ± 20%
Residual ripple of power supply
max. 5%
Power consumption
See Power Consumption on page 136
Number of series-connected extension
modules
8
See Data Width on page 138.
Display and Functional Elements
F
A
E
B
D
C
A. Push button (Mode) for setting the operating
modes B. Keypad C. bus connection for ETHERNET (RJ 45
socket) D. Connections for the power supply and routing E. Openings
for attaching the equipment label F. Digital display
52
MachinePoint Bus Couplers User Guide
Ethernet Modbus/TCP
Bus-specific LED displays
A
B
C
D
E
F
Label
Name
Colour
Meaning
A
RUN
green
The processor of the bus coupler is running.
B
TXD/RXD
green
Data exchange active
C
LINK
off
Bit transmission rate 10 Mbit/s (if INIT LED on)
green
Bit transmission rate 100 Mbit/s
green
Networking
off
MODBUS/TCP connection
red
MODBUS/TCP connection failure
D
INIT
E
blinking red Watchdog timeout (error code E006)
F
5V
green
MachinePoint Bus Couplers User Guide
5 V switch mode power supply active
53
Ethernet Modbus/TCP
Operating Modes LED Displays
A
B
C
D
E
F
Label
Name
Colour
Meaning
A
FORCE
yellow
Set and reset outputs
B
TRIGGER
C
LOCK
yellow
high or low state of inputs and outputs can be locked
D
STOP
red
I/O refresh disabled
E
RUN
green
Bus coupler processor running
F
MODE
54
Without function
Tip switch to select operating modes
MachinePoint Bus Couplers User Guide
Ethernet Modbus/TCP
Display of active operating mode
RUN mode
In RUN mode, information can also be displayed about the LOCK mode (see
pp. 96).
STOP mode (see page 98)
The selected channel is displayed in the following operating modes: display mode,
FORCE and LOCK.
1. Number of extension module (hexadecimal)
2. Input (E) or output (A)
3. Channel number (decimal)
Example 2E04: module 2, input, channel 04
Display of error messages
Error messages are displayed when faults occur. For a detailed
explanation of error messages, see page 108.
Example E004: Internal data transmission between the bus coupler and module has
been interrupted.
Keypad MachinePoint ETHERNET
The keypad is multifunctional. For a detailed description of the
functions in the different modes, see Service Functions on page 99.
MachinePoint Bus Couplers User Guide
55
Ethernet Modbus/TCP
PIN assignment
1
1
8
8
RJ 45 jack
Pin
Designation
Description
1
TX+
TransmitData+
2
TX-
TransmitData-
3
RX+
ReceiveData+
RX-
ReceiveData-
4
5
6
7
8
RJ 45 jack pin assignment
4.2.1 Bus Node Address Setting
Quick Start: Setting up a fieldbus node
The address can be set with service function 12. Following is a quick start
summary.
NOTE
The first 24 bits (grouped into bits of eight, separated by a dot) of the 32-bit IP
address of the bus node must be identical to the first 24 bits of the host's IP
address. The last eight bits of the IP address identifies the individual bus node in
your ETHERNET.
Press the HIGH/LOW buttons simultaneously in RUN or STOP mode.
The display indicates «S_01».
NOTE
When a client - server (bus coupler) connection is active, the display and setting of
the IP address are locked. The error code E016 (operator input inhibit) will be
56
MachinePoint Bus Couplers User Guide
Ethernet Modbus/TCP
displayed shortly.
Push the right button until «S_12» appears.
Then press the OK button.
The first byte (8 bits) of the bus address is displayed. The default value is
10.0.16.120, therefore you will see «1.010».
You can modify the bus address with the keypad on the bus coupler. The
push buttons have the following values:
After setting the first byte of your IP address, press OK. The second byte
then will be displayed.
Repeat the described procedure for the remaining three address bytes.
After setting the fourth byte and pushing OK, the selected address is
stored in the bus coupler and the display will read «_run» or «stop»
again. A new slave address is activated once the operating voltage has
been switched on/off (power cycle).
MachinePoint Bus Couplers User Guide
57
Ethernet Modbus/TCP
4.3 Modbus/TCP Functions
General Remarks on MODBUS 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.
NOTE
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. Input registers
start at base address 0x0 and output registers at 0x800. Digital inputs
and outputs start with index 0.
The data of the digital I/O modules are bit orientated, (bit-by-bit data
exchange), whereas the analog I/O modules are word orientated (wordby-word data exchange).
The data of the I/O modules arranged in the order of their position relative
to the coupler. In the process image, starting with register index 0, the
data words (16 bit) of the analog bus modules are stored first, beginning
with the analog bus module next to the MachinePoint ETHERNET bus
coupler. The data words comprising the analog process image are
followed by the process data of the bit-oriented modules, which are
stored in data words too. If a digital I/O module provides only 8 bits of
input or output data, the word register will be filled up with 8 data bits of
the next digital module.
Imaging of digital module data will always be done with a granularity of
8 bit. This means one can ignore bits 4-7 of the respective byte in the
process image of an I/O module which provides only 4 bit of data.
NOTE
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.
Furthermore, single digital input and output bits can be addressed by
means of the MODBUS/TCP functions Read Input Discretes (FC2) and
Write Coils (FC5). As with the analog module imaging, the process image
of digital inputs and outputs represents the order of the digital modules in
the extension module chain linked to the MachinePoint ETHERNET bus
coupler.
An Example Configuration
The following describes an example configuration of a MachinePoint
ETHERNET bus node along with the respective process image. In the
58
MachinePoint Bus Couplers User Guide
Ethernet Modbus/TCP
section describing the functions, all examples will refer to the example
process image presented here.
The diagnose words are activated via service function 5.
Type
Ethernet
bus coupler
extension
module 0
8I/O
EW Modul EW Modul 2
1
160
4AI 420mA
extension
module 3
4AI4AO/10V
INPUT range
2 word diagnosis
1 Byte
8 Byte
-
8 Byte
OUTPUT range
2 word diagnosis
1 Byte
-
2 Byte
8 Byte
Register address INPUT
0x0000
0x000A low byte
0x0002
-
0x0006
0x0001
Register address
OUTPUT
0x0800
0x0007 lowbyte
0x0003
0x0007
0x0004
0x0008
0x0005
0x0009
-
0x0008 highbyte
X1
0x0801
0x0009 lowbyte X2
0x0803
0x0804
0x0805
0x0806
number of coils
-
number of inputs
-
0x0000 offset
-
0x0000 offset
8 coils 0-7
0x0000 offset
-
16 coils 8-23
-
-
-
in 0- 7
Input Register
(access via function codes 0x04,
0x03 and 0x17)
Output Register
(access via function code 0x06, 0x10 and
0X17)
Address
Address
Offset
position of
ext. module
I/O Module Type
Offset
position of
ext. module
I/O Module Type
0x0800
Diagnostic (DW1)
0x0000
Diagnostic (DW1)
0x0801
Diagnostic (DW2)
0x0001
Diagnostic (DW2)
0x0802
1
4AI/4-20mA
0x0002
3
4AI4AO/0..10V
0x0803
1
4AI/4-20mA
0x0003
3
4AI4AO/0..10V
0x0804
1
4AI/4-20mA
0x0004
3
4AI4AO/0..10V
0x0805
1
4AI/4-20mA
0x0005
3
4AI4AO/0..10V
0x0806
3
4AI4AO/0..10V
0x0006
0
8 I/O, 16 O
0x0807
3
4AI4AO/0..10V
0x0007
2
16 O
0x0808
3
4AI4AO/0..10V
0x0809
3
4AI4AO/0..10V
0x0810
0
8 I/O
MachinePoint Bus Couplers User Guide
59
Ethernet Modbus/TCP
Input Discretes
(access via function code 0x02)
Output Coils
(Write access via function code 0x05 and
0x0f)
(Read access via function code 0x01)
Address
Address
Offset
0-7
position of
ext. module
I/O Module Type
0
8 I/O
position of
ext. module
I/O Module Type
0-7
0
8 I/O
8 - 15
2
16 O
16 - 23
2
16 O
Offset
Description of the MODBUS functions
MODBUS functions from the OPEN MODBUS/TCP specification are
found in the application layer of the MachinePoint ETHERNET fieldbus
coupler.
These functions allow digital or analog input and output data to be set or
to be directly read out of the fieldbus node.
60
MachinePoint Bus Couplers User Guide
Ethernet Modbus/TCP
The following functions of the Open MODBUS/TCP specifications are
supported by MachinePoint ETHERNET:
Function
code
Function
Description
HEX
FC1:
0x0001
Read coils
Read several output bits
FC2:
0x0002
Read input discretes
Read several input bits
FC3:
0x0003
Read multiple registers
Read several input/output registers
FC4:
0x0004
Read input registers
Read several input registers
FC5:
0x0005
Write coil
Write single output bit
FC6:
0x0006
Write single register
Write single output register
FC7:
0x0007
Read exception status
Not yet implemented
FC8:
0x0008
Diagnostics
Read/write diagnostic functions
FC15:
0x000F
Force multiple coils
Write several output bits
FC16:
0x0010
Write multiple registers
Write several output registers
FC23:
0x0017
Read/write multiple
registers
Read/write several input/output registers
List of the MODBUS functions supported by MachinePoint ETHERNET
bus coupler
To execute a desired function, specify the respective function code and
the address of the selected input or output channel.
The format and beginning of the addressing may vary according to the
software and the control system. All addresses then need to be converted
accordingly.
NOTE
It is recommended that analog data be accessed with register functions and
digital data with coil functions.
All MODBUS functions in the MachinePoint ETHERNET fieldbus coupler
are executed as follows:
When a function code is entered, the MODBUS master (i.e. PC) makes a
request to the coupler of the fieldbus node. Subsequently, the coupler
sends a telegram to the master as a response. If the coupler receives an
incorrect request, it sends an error telegram (exception) to the master.
The following chapters describe the telegram architecture of request,
response and exception with examples for each function code.
NOTES
(1) In the case of the read functions (FC1 – FC 4) the outputs can be additionally written and read back
by adding an offset of 800hex (0x0800) to the MODBUS address.
(2) Fieldbus nodes may send out «sampling» commands. Upon success or exception, they determine
the set of MODBUS functions which is available by the respective device. This is an opportunity to
determine the size of the data regions available on the «server» (i.e. bus coupler).
MachinePoint Bus Couplers User Guide
61
Ethernet Modbus/TCP
Function code FC1 (0x0001 - Read Coils)
The function reads the status of the output bits (coils) in slave.
Example: Read the output status of the extension module at position 0
(«module 0») and extension module at position 2 («module 2»).
Request The request determines the starting address and the number of
bits to be read.
Field name
example
0
Byte
Function code
0x01
1-2
Reference number
0x0000
3-4
Bit count
0x0018 decimal notation 24
Response The current values of the inquired bits are packed in the data
field. A '1' corresponds to the ON status and a '0' to the OFF status. The
lowest value bit of the first data byte contains the first bit of the inquiry.
The others follow in ascending order. If the number of outputs is not a
multiple of 8, the remaining bits of the last data byte are filled with zeroes
(truncated).
The status of the outputs 7 to 0 is shown as byte value. Output 7 is the bit
having the highest significance of this byte and output 0 the lowest value.
Byte
0
1
2
3
4
Field name
example
Function code
byte count of response (bit count +7)/8
Bit values
(last significant bit is the first coil)
Bit values
(last significant bit is the first coil)
Bit values
(last significant bit is the first coil)
0x01
0x03
0x2F
/ 00101111 Modul 0 X1.0 to x1.7
0x55
/ Modul 2 X1.0 to X1.7
0xAA /modul 2 X1.8 to x1.15
Exception
Byte
0
1
Field name
example
Exception function code =
function code + 0x80
Exception code
0x81
0x01 , 0x02 or 0x03
Function code FC2 (0x0002 - Read Discrete Inputs)
This function reads the input bits in the slave.
Example: Read the 8 input signals on the clamps X1.0 to X1.7 of
module 0. Connect +24VDC to clamp X1.7 first.
Remember that the the eight outputs of the MachinePoint 8I/O module
are internally connected to the eight inputs.
Requests The request determines the starting address and the number
of bits to be read.
Byte
0
1-2
3-4
62
Field name
example
Function code
Reference number
Bit count (1 to n)
n = number of connected coils
0x02
0x0000
0x0008
MachinePoint Bus Couplers User Guide
Ethernet Modbus/TCP
Response The current value of the inquired bit is packed into the data
field. A '1' corresponds to the ON status and a 0 the OFF status. The
lowest value bit of the first data byte contains the first bit of the inquiry.
The others follow in an ascending order. If the number of inputs is not a
multiple of 8, the remaining bits of the last data byte are filled with zeroes
(truncated). The status of the inputs 7 to 0 is shown as a byte value.
Input 7 is the bit having the highest significance of this byte and input 0
the lowest value.
Byte
0
1
2
3
4
Field name
example
Function code
Byte count of response (bit count +7)/8
Bit values
(last significant bit is the first coil)
Bit values
(last significant bit is the first coil)
Bit values
(last significant bit is the first coil)
0x01
0x03
0x2F
/ 00101111 Modul 0 X1.0 to x1.7
0x55
/ Modul 2 X1.0 to X1.7
0xAA /modul 2 X1.8 to x1.15
Exception
Byte
0
1
Field name
example
Exception function code =
function code + 0x80
Exception code
0x82
MachinePoint Bus Couplers User Guide
0x01 , 0x02 or 0x03
63
Ethernet Modbus/TCP
Function code FC3 (0x0003 - Read multiple registers)
The binary contents of a slave's input as well as output registers,
including control and status registers, are read using this function.
Example: Read the constant values at address 1400 , 1401,1402 and
1403
Request The request determines the start word address (start register)
and the number the register to be read. The addressing starts with 0x00
(input registers) and 0x800 (output registers), respectively. Status and
control registers are in the range 0x1000 to 0x14XX.
Byte
0
1-2
3-4
Field name
example
Function code
Reference number
Word count
0x03
0x1400
0x04
Response The reply register data is packed as 2 bytes per register. The
first byte contains the higher value bits, the second the lower values.
The contents of register 0 to 9 are displayed.
Byte
0
1-2
3-4
5-6
7-8
9 - 10
Field name
example
Function code
Byte count of response
(word count multiplied by 2)
Register value
Register value
Register value
Register value
0x03
0x0004
0x1234
0x0000
0xFFFF
0x5555
Exception
Byte
0
1
Field name
example
Exception function code =
function code + 0x80
Exception code
0x83
0x01 , 0x02 or 0x03
Function code FC4 (0x0004 - Read input registers)
This function serves to read a number of input words (also ”input
register”). This function is a subset of FC3.
Example: Read all eleven input registers
Request The request determines the address of the start word (start
register) and the quantity of the registers to be read. Addressing starts
with 0.
Byte
0
1-2
3-4
Field name
example
Function code
Reference number
Word count
0x04
0x0000
0x0B (11 decimal)
Response The register data of the answer is packed as 2 bytes per
register. The first byte has the higher value bits, the second the lower
values.
64
MachinePoint Bus Couplers User Guide
Ethernet Modbus/TCP
Byte
0
1-2
3-4
5-6
7-8
9 - 10
…
33 - 34
Field name
example
Function code
Byte count of response (word count
multiplied by 2)
Register value
Register value
Register value
Register value
...
Register value
0x04
0x0016
MachinePoint Bus Couplers User Guide
22decimal
0x0000 DW1
0x0000 DW2
0x0000 channel 1 Modul 3
0x0000 channel 1 Modul 3
...
x00AF digital input modul 0
most significant byte is not used
65
Ethernet Modbus/TCP
Exception
Byte
0
1
Field name
example
Exception function code =
function code + 0x80
Exception code
0x84
0x01 , 0x02 or 0x03
Function code FC5 (0x0005 - Write Coil)
With the aid of this function a single output bit is written.
Example: The output X1.6 of module 0 is to be set to high, the other
outputs remaining unchanged.
Request The request determines the address of the output bit.
Addressing starts with 0.
Byte
0
1-2
3
4
Field name
example
Function code
Reference number
ON = 0xFF / OFF = 0x00
Constant 0x00
0x05
0x0006 module 0 ( X1.6 ) x1xx xxxx
0xFF
0x00
Response The inquiry is echoed.
Byte
0
1-2
3
4
Field name
example
Function code
Reference number
= FF to turn coil ON,
= 00 to turn coil OFF (echoed)
Constant 0x00
0x05
0x0006
0xFF
0x00
Exception
Byte
0
1
Field name
example
Exception function code =
function code + 0x80
Exception code
0x85
0x01 , 0x02 or 0x03
Function code FC6 (0x0006 - Write single register)
This function writes a value in one single output word (also ”Output
register”).
Example: Write to the first analog output channel of module 3. The
register address of this channel is 0x0802 = 0x800 + 2
The hexadecimal equivalent for the analog value of 5V is 0x1388 or, in
decimal notation, 5000 (see manual section: description of the analog
values).
Request Addressing starts with 0. The inquiry determines the address of
the first output word to be set. The value to be set is determined in the
inquiry data field.
Byte
0
1-2
3-4
Field name
example
Function code
Reference number
Register value
0x06
0x0802
0x1388
5000 dez (5000 millivolts)
Response Echo of inquiry.
66
MachinePoint Bus Couplers User Guide
Ethernet Modbus/TCP
Byte
0
1-2
3-4
Field name
example
Function code
Reference number
Register value
0x06
0x0802
0x1388
Exception
Byte
0
1
Field name
example
Exception function code =
Function code + 0x80
Exception code
0x86
0x01 , 0x02 or 0x03
Function code FC7 (0x0007 - Read Exception Status)
This function reads the status of the first 8 coils (output discretes) of the
process output image.
Note that "Exception Status" is not in any way related to an exception
response.
Function code FC8 (0x0008 - Read/write diagnostic functions)
For explanation, please see page 71.
Function code FC15 (0x000F - Force Multiple Coils)
Using this function a number of output bits are set to 1 or 0. The
maximum number is 256 bits.
Example: In this example, output bits 0 to 23 are set, starting with offset
0x0000. The request contains 3 bytes with the value byte stream
0x0F55AA (also in binary format 00001111 01010101 10101010). The
first byte transmits 0x0F to module 0 (output terminals X1.0 to X1.7). The
following byte transmits the value 0x55 to module 2 (output terminals
X1.0 to X1.7), and the third byte transmits the value 0xAA to output
terminals X1.8 to X1.15 of module 2.
Request The first point is addressed with 0. The inquiry message
specifies the bits to be set. The requested 1 or 0 states are determined
by the contents of the inquiry data field.
Byte
0
1-2
3–4
5
6
7
8
Field name
example
Function code
Reference number
Bit count ( 1- 128 )
Byte count = (bit count + 7)/8
Data to be written
(least significant bit = first coil)
Data to be written
(least significant bit = first coil)
Data to be written
(least significant bit = first coil)
0x0f
0x0000
0x0018 dez. 24
0x03
0x0f Modul 0
0x55 Modul 2 X1.0 - X1.7
0xAA Modul 2 X1.8 – X1.15
Response
Byte
0
1-2
3–4
Field name
example
Function code
Reference number
Bit count
0x0f
0x0000
0x0018
MachinePoint Bus Couplers User Guide
67
Ethernet Modbus/TCP
Exception
Byte
0
1
Field name
example
Exception function code =
function code + 0x80
Exception code
0x8f
0x01 , 0x02 or 0x03
Function code FC16 (0x0010 - Write multiple registers)
This function writes values in a number of output words (also ”Output
register”) and control registers.
Example: Write to the first and second analog output channel of module
3 at the same time. The register address of channel one is 0x0802 =
0x800 + 2. The register address of channel 2 is 0x0803 = 0x802+1.
Analog value for channel one 4V is 0x0FA0 or decimal notation 4000,
analogue signal of channel 2 should be set to 8 voltage , 8000millivolts
=0x1F40 (see manual section: description of the analogue values)
68
MachinePoint Bus Couplers User Guide
Ethernet Modbus/TCP
Request The first point is addressed with 0. The inquiry message
determines the registers to be set. The data is sent as 2 bytes per
register. Allowed range is 0x0800 to number of outputs; n - control
register.
Byte
0
1-2
3-4
5
6-7
8-9
Field name
example
Function code
Reference number
Word count
Byte count (word count x 2)
Register value
Register value
0x10
0x0802 (first address modul 3)
0x0002
0x04
0x0FA0 4000 dec (4000 millivolts)
0x1F40
8000 dec (8000 millivolts)
Response
Byte
0
1-2
3-4
Field name
example
Function code
Reference number
Word count
0x10
0x0802
0x0002
Exception
Byte
Field name
example
0
Exception function code function code
+ 0x80
0x90
1
Exception code
0x01 , 0x02 or 0x03
Function code FC23 (0x0017 - Read/Write multiple registers)
This function reads the register values and writes the values into a
number of output words (also ”Output Register»). The Open
MODBUS/TCP specifications do not require a certain order of both
operations. With MachinePoint ETHERNET bus coupler, the output
registers are written first, followed by reading the specified input registers.
Example: Write 2 registers at reference 0x0802 and 0x0803 of value
4000dec and 8000dec (Module 3 Channel 1 and 2) and read 1 register at
reference 0x000A (returning input status MachinePoint 8/O Modul 0)
Request The first register is addressed with 0. The inquiry message
determines the registers to be read and set. The data is sent as 2 bytes
per register.
Byte
0
1-2
3-4
5-6
7-8
9
A-B
C-D
Field name
example
Function code
Reference number for read
Word count for read
Reference number for write
Word count for write
Byte count for write (word count f. write
x 2)
Register value
Register value
0x17
0x000A (decimal 10)
0x0001
0x0802
0x0002
0x04
0x0FA0 channel 1 modul address 3
0x1F40 channel 2 modul address 3
Response
Byte
0
1
Field name
example
Function code
Byte count of response (word count
0x17
0x02
MachinePoint Bus Couplers User Guide
69
Ethernet Modbus/TCP
multiplied by 2)
Register value
2-4
0x00AF (digit. input Modul with address 0)
Exception
Byte
0
1
Field name
example
Exception function code function code
+ 0x80
Exception code
0x97
0x01 , 0x02 or 0x03
NOTE
Should register areas for read and write overlap, the results are undefined.
Exceptions
If a request of a master cannot be interpreted correctly by a slave, an
error message (exception) will be deployed by the slave, according to the
Open MODBUS/TCP specifications.
All exception telegrams are singalled by adding 0x80 to the function code
of request, followed by an error byte. The exception codes listed below
are supported by MachinePoint ETHERNET bus couplers:
Exception
Code
0x01
0x02
0x03
0x04
Meaning
Illegal Function
Illegal Data Address
Illegal Data Value
Slave Device Failure (watchdog error)
Watchdog (Fieldbus failure)
The watchdog serves for monitoring the data transfer between the master
con-trols and the coupler. For this the master cyclically actuates a time
function (Time-out) in the coupler.
In the case of fault free communication, the watchdog timer does not
reach its end value. After each successful data transfer, the timer is reset.
If this time has elapsed a fieldbus failure has occurred.
In this case, the fieldbus coupler answers all following MODBUS TCP/IP
requests with the exception code 0x0004 (Slave Device Failure).
In the coupler special registers are present for the selection and status
inquiry of the watchdog by the master (Register addresses 0x1000 to
0x1008).
After switching on the supply voltage the watchdog is not yet activated.
First step is to set the time-out value (Register 0x1000). The watchdog
can be activated by writing a function code in the mask register (0x1001),
which is unequal 0. A second activation possibility is to write a value in
the toggle register (0x1003) deviating from 0.
Reading the minimum trigger time (Register 0x1004) reveals whether the
watchdog fault reaction was activated. If this time value is 0, a fieldbus
failure is assumed. The watchdog can be restarted in accordance with
the previously mentioned two possibilities or using the register 0x1007.
70
MachinePoint Bus Couplers User Guide
Ethernet Modbus/TCP
If the watchdog is started it can only be stopped by the user for safety
reasons via a certain path (register 0x1005 or 0x1008).
Watchdog Register
The watchdog registers can be addressed in the same way as the
described in MODBUS function codes (read and write). Specify the
respective register address in place of the address of a module channel.
Register
address
Access
R=read;
W=write
Default
Description
Watchdog timeout (multiple of 100 ms).
This register saves the value for time exceeded (Timeout). To be able to start, the watchdog default value must
have a value which is not equal to zero. The time is set
as a multiple of 100 ms, 0x0009 means a time out time of
0.9 s. This value cannot be changed when the watchdog
is running.
Watchdog type
0=trigger update with every function code
1=trigger update with every write function code
Watchdog state
0=not active 1=active
0x1400
R/W
0
0x1401
R/W
0
0x1402
R/W
0
Diagnostic function
The following registers can be read to determine errors and to get helpful
information from the network node:
Register
address
Access
R=read;
W=write
Default
Description
Actual system status, format acc. to diagnosis function 0
(DW 1)
Collect error, format acc. to diagnosis func. 0 (DW2)
Status of module power supply, format acc. to diagnosis
func. 1 (DW1)
Status of output drivers, format acc. to diagnosis func. 2
(DW1)
System status, format acc. to diagnosis func. 7 (DW1)
Number of connected modules, value in the range 0…8
module type at position 0/1, format acc. to diagnosis func.
4 (DW1) for n=0.
Module ID will be 0 if no module is at the respective
position.
module type at position 2/3, format same as for 0x1006
with n=2
module type at position 4/5, format same as for 0x1006
with n=4
module type at position 6/7, format same as for 0x1006
with n=6
sensor information of 4AI/PT100 module at position 0/1
format acc. to diagnosis func. 10 (DW1/Byte 2)
information on two modules are pooled. If another type of
module is present at the respective position, a 0 will be
returned as status information.
sensor information of 4AI/PT100 module at position 2/3
format same as for 0x100A
Sensor information of 4AI/PT100 module at position 4/5
0x1000
R
-
0x1001
0x1002
R
R
-
0x1003
R
-
0x1004
0x1005
0x1006
R
R
R
-
0x1007
R
-
0x1008
R
-
0x1009
R
-
0x100A
R
-
0x100B
R
-
0x100C
R
-
MachinePoint Bus Couplers User Guide
71
Ethernet Modbus/TCP
Register
address
Access
R=read;
W=write
Default
0x100D
R
-
0x100E
0x100F
0x1010
0x1011
0x1012
0x1600
0x1601
R
R
R
R
R
W
W
-
Description
format same as for 0x100A
Sensor information of 4AI/PT100 module at position 6/7
format same as for 0x100A
Firmware version, format acc. to diagnosis func. 8 (DW1)
register count of output process image
register count of input process image
Number of digital outputs (coils)
Number of digital inputs
Clear error messages, format acc. to diagnosis func. 20
Save configuration, parameters acc. to diagnosis func. 21
Configuration function
The following registers can be read or write, in order to determine the
configuration of the connected modules:
Register
address
72
Access
R=read;
W=write
Default
Description
Preference cutoff of module at pos. 0/1
The lower significant byte (LSB) represents the module at
position n and the most significant byte (MSB) represents
the module at position n+1.
Valid values are to be chosen according to diagnosis
function 5
Preference cutoff of module at pos. 2/3, format same as
with 0x1403
Preference cutoff of module at pos. 4/5, format same as
with 0x1403
Preference cutoff of module at pos. 6/7, format same as
with 0x1403
data format for analog module at pos. 0
LSB/MSB: Input/output format
Values acc. to parameters of diagnosis func. 9. If there is
no analog module present at this position or a non-valid
value is passed, the write command will be ignored.
data format for analog module at pos. 1, format same as
with 0x1407
data format for analog module at pos. 2, format same as
with 0x1407
data format for analog module at pos. 3, format same as
with 0x1407
data format for analog module at pos. 4, format same as
with 0x1407
data format for analog module at pos. 5, format same as
with 0x1407
data format for analog module at pos. 6, format same as
with 0x1407
data format for analog module at pos. 7, format same as
with 0x1407
Configuration of 4AI/TC module at position 0, format acc.
to diagnosis func. 11 (DW1)
If another type of module is present at the respective
position, the command will be ignored.
Configuration of 4AI/TC module at position 1, format
same as with 0x140F
Configuration of 4AI/TC module at position 2, format
same as with 0x140F
0x1403
R/W
0
0x1404
R/W
0
0x1405
R/W
0
0x1406
R/W
0
0x1407
R/W
depends on module
0x1408
R/W
depends on module
0x1409
R/W
depends on module
0x140A
R/W
depends on module
0x140B
R/W
depends on module
0x140C
R/W
depends on module
0x140D
R/W
depends on module
0x140E
R/W
depends on module
0x140F
R/W
0
0x1410
R/W
0
0x1411
R/W
0
MachinePoint Bus Couplers User Guide
Ethernet Modbus/TCP
Register
address
Access
R=read;
W=write
Default
Description
Configuration of 4AI/TC module at position 3, format
same as with 0x140F
Configuration of 4AI/TC module at position 4, format acc.
to diagnosis func. 11 (DW1).
If another type of module is present at the respective
position, the command will be ignored.
Configuration of 4AI/TC module at position 5, format
same as with 0x1413
Configuration of 4AI/TC module at position 6, format
same as with 0x1413
Configuration of 4AI/TC module at position 7, format
same as with 0x1413
0x1412
R/W
0
0x1413
R/W
0
0x1414
R/W
0
0x1415
R/W
0
0x1416
R/W
0
General Registers
The following registers contain constants which can be used to test the
commu-nication with the master:
Register
address
Access
R=read;
W=write
Default
Description
0x1200
constant
0x1234
Constant for bit error check
0x1201
constant
0x0000
Constant for bit error check
0x1202
constant
0xFFFF
Constant for bit error check
0x1203
constant
0x5555
Constant for bit error check
0x1204
constant
0xAAAA
Constant for bit error check
MachinePoint Bus Couplers User Guide
73
Ethernet Modbus/TCP
5 Installation
5.1 Mechanical Installation
Installation Position
Keep to vertical installation position.
74
MachinePoint Bus Couplers User Guide
Ethernet Modbus/TCP
5.1.1
Mounting dimensions and installation clearances for EC bus
coupler
5.1.2 Mounting dimensions and installation clearances for BC bus
coupler
The maximum configuration of 1 bus coupler + 8 modules should be
complied with. A further extension is not recommended.
Note
DIN rail mounting
DIN rail type TS 35 mm/7.5 should be used in accordance with DIN EN
50022.
MachinePoint Bus Couplers User Guide
75
Ethernet Modbus/TCP
Installing
A Tilt the device slightly and
place the guide (1) onto the
DIN rail (2).
B Press onto the DIN rail (2)
until the latch (3) clicks into
place.
The modules must be mounted directly adjacent to each other and
secured against slipping with an end clamp.
Dismantling
Open the orange contact slide
on the top of the module (slide
to the right).
C Place the screwdriver in the
latch (1).
D Lever the latch downwards
with the screwdriver. The
latch remains in the open
position.
E Tilt the device and remove
from the rail. Push the latch
(1) back again.
76
MachinePoint Bus Couplers User Guide
Ethernet Modbus/TCP
Interlinking Modules
The orange slide contacts on top of the module link the modules to the
bus coupler.
• Make sure that the slide contacts are open when you actuate the spring
terminals. This will reduce mechanical wear on the contact points.
• Align the modules before you close the slide contacts.
• Close the slide contacts before activating the unit. Do not use force when
closing the slide contacts.
• Do not open the slide contacts during operation.
MachinePoint Bus Couplers User Guide
77
Ethernet Modbus/TCP
5.2 Electrical Installation
5.2.1 Spring-loaded terminals for EC bus coupler
Spring-loaded terminals are used on bus coupler EC for connection of the
power supply.
1 Actuating point
2 Measuring point
3 Terminal compartment
To operate the spring-loaded terminal, a screwdriver with a .02 x .14 in
(0.6 x 3.5 mm) blade is required in accordance with DIN 5264 B. The
diameter of the shaft may not exceed the cutting width of .14 in (3.5 mm).
Opening the terminal
Press the screwdriver vertically into the actuating point (1).
Insert the wire in the terminal compartment (3).
Closing the terminal
Remove the screwdriver from the actuating point (1).
Each terminal has a measuring point (2) which is accessible with a
conventional 2 mm measuring probe.
78
MachinePoint Bus Couplers User Guide
Ethernet Modbus/TCP
5.2.2 Spring Terminals for BC Bus Couplers
Delivery condition: Terminals open
The terminals are pre-tensioned by means of a clamping key (1). The
clamping space (2) is open. Each terminal is fitted with a measuring
point, which can be accessed using a common test probe (3).
To close the terminal
MachinePoint Bus Couplers User Guide
A
Insert a wire in the
clamping space.
B
Push the clamping key in
direction B.
C
The key will be pushed up
in direction C by the
tension of the spring, and
should remain in the
terminal.
79
Ethernet Modbus/TCP
To open the terminal
Make sure that the slide contacts of the module are open before opening
the terminal. This will reduce mechanical wear on the contact points.
A
Use the screwdriver to push
the clamping key in
direction A. The clamping
key will lever the spring
terminal open and will
remain in this position.
B
Remove the cable by
pulling it in direction B.
You also can open spring terminals without a clamping key. Use a
screwdriver in place of the clamping key.
5.2.3 Conductor sizes
80
MachinePoint Bus Couplers User Guide
Ethernet Modbus/TCP
5.2.4 Connecting the Power Supply and Signal Lines
For an explanation of the numbers in this diagram, see the following
section.
MachinePoint Bus Couplers User Guide
81
Ethernet Modbus/TCP
5.2.5 Installation Guidelines
• MachinePoint modules must be installed in grounded and closed
metal cases (enclosures or cabinets). The DIN rail that carries the
modules must have a broad-surface connection to ground providing
adequate conduction. (1)
To protect the modules against electrostatic discharge, operating
personnel must discharge any electrostatic charge they may be
carrying before opening enclosures or cabinets.
• The data connecting cable between the MachinePoint bus coupler or
MachinePoint compact module and other field bus equipment must be
shielded. Both ends of the shield must be connected to the shield or
ground wire potential (PE). (2) Ensure that contact is made over a
broad surface area and is sufficiently conductive.
• The bus coupler and the 8I/O module have a connecting terminal
marked with the ground symbol. To increase interference immunity,
this terminal must be connected to ground (or PE potential) with a
conductor (3) that is as short as possible (0.1 in2/2.5mm2).
• All digital and analog I/O lines must be laid away from DC/AC
conductors > 60 V. Analog signal lines must be shielded. The shield
must be provided with a large-surface connection to ground in the
immediate vicinity of the modules. To secure the shielding, use metal
cable clips which surround a large area of the shielding and provide
for a good contact to the ground reference area.
• The potential relay terminals can be used to relay the respective
potential (4). Make sure that the load on a contact does not exceed
Imax = 8A. When looping the power supply from module to module
make sure not to exceed this maximum current.
For optimum EMC properties, the first I/O module on the right of
the bus coupler should be powered via the potential relay
terminal on the bus coupler. All other modules can be powered
individually. Always lay cables vertically downwards so that modules
can be tilted.
82
MachinePoint Bus Couplers User Guide
Ethernet Modbus/TCP
• The contact spring located in the module clamp foot is used to divert
EMC interference. This spring establishes the connection between the
PCB shield potential and the DIN rail. Fitting without a contact spring
or with a defective contact spring is not allowed.
When using modules with digital combination channels, be aware that
you cannot connect a 24V supply to the combination channel without
connecting the module to the power supply. If you do, the power
supply will be fed back via the output circuit of the module. This may
result in a malfunction or destruction of the output circuit.
In an emergency stop, do not just switch off the power supply to the
modules with combination channels. You must switch off the input
voltage and the power supply simultaneously.
The same applies to digital output signals if they have been incorrectly
connected to 24V.
MachinePoint Bus Couplers User Guide
83
Ethernet Modbus/TCP
84
MachinePoint Bus Couplers User Guide
User Lock-Out
6 User Lockout on BC Bus Couplers
Some functions that you can access via the keypad of the bus coupler
must be protected against unauthorized use since they will have a direct
impact on the operation of the controlled plant.
User lock-out function for operating modes and service functions:
FORCE, LOCK, STOP;
Service functions 1, 2, 5, 6, 9, 10
You can activate a user lock-out on Safety Level I or II. In Safety Level
II, you work with a password protection.
MachinePoint Bus Couplers User Guide
85
User Lock-Out
1. When you switch the bus coupler on, it will check whether or not a
password has been saved in the bus coupler. If it finds a password, it
will activate a user lock-out on Safety Level II.
2. If no password has been saved, you can operate the unit until the PLC
or bus is started. The user lock-out will be activated on Safety Level I
when you start up the PLC.
3. If the PLC is stopped, if a bus cable breaks, or if you enter service
function 7 with parameter 0000, the user lock-out function will be
disabled.
4. If you have to carry out maintenance work on the unit, you can use
service function 7, parameter 0015, to disable the user lock-out
function until you reset the bus coupler again.
5. You can lock the PLC with a password so that no-one can use it. To
do this, you need to use the diagnosis data (Diagnosis code 6). The
password will be saved in the bus coupler. The password must be a
four-digit number between 0000 and 9999.
6. The password can be changed at any time from the PLC.
7. If you enter the password on the bus coupler (via service function 8,
password as the parameter), the user lock-out will be deactivated. The
password will not be deleted.
If the PLC changes the password to 0000, the password protection will
be deactivated, and the password in the bus coupler will be deleted.
Confirm or cancel activation of the above operating modes and service
functions with Error code E016 (on Safety Level I) or Error code E017 (on
Safety Level II).
86
MachinePoint Bus Couplers User Guide
Operating Modes
7 Operating Modes of BC Bus Couplers
7.1 Overview of Operating Modes
Operating modes
Description
RUN
The bus interface is running, I/Os are being refreshed, active LOCK and TRIGGER
conditions are being analyzed. You can display control states of single I/O channels
on the bus coupler.
STOP
FORCE
Use this mode to set the control states of individual I/O channels. FORCE overrides
the I/O control states and lock definitions.
TRIGGER
After a trigger event, the I/O map will be saved with a memory depth of 20 bytes. The
trigger event is an I/O state change that can be defined.
LOCK
The same as FORCE, but used to permanently set the control states of individual I/O
channels. The LOCK definition will be stored permanently in the bus coupler.
RUN mode is interrupted. I/O refresh is switched off. The unit is set to a pre-set
preferred shut-off state (see Diagnosis code 5).
RUN mode is active after the bus coupler has been switched on.
The FORCE, TRIGGER and LOCK modes can be activated during RUN
mode. The RUN mode will not be interrupted.
FORCE and LOCK modes directly affect the control states of I/O
channels. Beware of dangerous operating conditions in the controlled
processes!
Take measures to prevent invalid operating conditions.
MachinePoint Bus Couplers User Guide
87
Operating Modes
7.2 Setting Operating Modes
The bus coupler is protected from unauthorized operation by means of
a user lock-out. Deactivate the user lock-out before selecting another
operating mode. (See also User Lock-Out, page 84)
Mode Key
Press the Mode key to move the
flashing light diode from selection
to selection.
Press OK to confirm the selected
operating mode.
88
MachinePoint Bus Couplers User Guide
Operating Modes
Active operating mode display
The active operating mode and its sub-modes are indicated by LEDs. In
addition, the following symbols appear on the bus coupler display:
RUN mode
STOP mode
Displaying the selected I/O channel
If you manually select a channel in RUN with Display, FORCE, TRIGGER
or LOCK mode, the following will be displayed:
1. I/O module number
(hexadecimal)
2. Input (E) or output (A)
3. Channel number (decimal)
Example: 2E04
input, channel 4
module 2,
Channel cursor display
In RUN, with FORCE, TRIGGER, LOCK, and Display modes active, the
two-color channel LED is yellow. This LED is the channel cursor and has
no effect on the control state of the respective input/output. Use the
Address keys to move the channel cursor. Each channel LED is assigned
MachinePoint Bus Couplers User Guide
89
Operating Modes
to a channel (.0-.15).
On 8-channel modules only channel LEDs .0 -.7 are active.
On analog modules, the channel LEDs 0, 2, 4, and 6 are assigned to the
inputs. LEDs 8, 10, 12, and 14 are assigned to the outputs.
7.3 RUN
In RUN mode, you can refresh I/O channels with the current PLC data.
When you are in RUN mode, you can select Display mode.
Display mode
The display on the bus coupler continuously shows the current control
state of an I/O channel.
1. Select the channel using the Address keys (the active yellow LED on
the I/O modules is the channel cursor).
The bus coupler display will show the selected channel.
1. I/O module number (hexadecimal)
2. Input (E) or output (A)
3. Channel number (decimal)
Example: 2E04
channel 4
90
module 2, input,
MachinePoint Bus Couplers User Guide
Operating Modes
The control state will be displayed after about 0.5s and updated
continuously.
For analog channels, the current/voltage will be displayed in mV or
µA.
2. Press OK to exit Display mode.
7.4 FORCE
In FORCE mode, you can set the control state of individual I/O channels.
FORCE mode directly affects the control states of I/O channels.
FORCE mode overrides control states which have been set using
LOCK mode.
Beware of dangerous operating conditions in the controlled
processes! Take measures to prevent invalid operating conditions.
Procedure
1. Press the Mode key to select FORCE.
2. Press OK to confirm your selection.
3. Select the channel using the Address keys.
MachinePoint Bus Couplers User Guide
91
Operating Modes
The selected channel will be displayed on the bus coupler. The
active yellow LED on the I/O modules is the channel cursor.
4. Select the control state using the High/Low keys.
The control state you select will become active immediately.
If you have selected an analog channel, the input/output value will be
increased/reduced by 100mV or 100 µA every time you press one of
the keys.
5. Press OK to check the FORCE state of a selected channel.
92
MachinePoint Bus Couplers User Guide
Operating Modes
The FORCE state will be displayed for approx. 0.5s after you have
pressed the OK key. For analog channels, the input/output value will
be displayed in mV or µA.
The channel LED of the forced channel is yellow, even if you move
the channel cursor to a different channel.
Resetting FORCE for all channels
•
Exit FORCE mode.
Resetting FORCE for one channel
•
Move the channel cursor to the channel that you want to reset,
and press OK three times.
Three times
The display will briefly look like the following illustration.
MachinePoint Bus Couplers User Guide
93
Operating Modes
7.5 TRIGGER
TRIGGER mode is used to display the last 20 alterations to the digital
process map stored when a trigger condition occurs.
Not for analog modules.
Procedure
1. Press the Mode key to select TRIGGER.
2. Press OK to confirm your selection.
3. Select the channel that will activate a trigger stop:
Move the channel cursor using the Address keys.
4. Set the trigger condition using the High/Low keys.
•
High key: trigger to rising edge
Low key: trigger to falling edge
You can define any number of inputs and outputs as trigger inputs.
They are linked by OR, which means that the trigger condition that is
fulfilled first ends the recording.
5. Press the Mode key to set the operating mode back to RUN, and
press OK.
The trigger function only works when RUN has been re-activated.
94
MachinePoint Bus Couplers User Guide
Operating Modes
The display will show the trigger state as follows:
•
Trigger condition defined.
The I/O maps will now be saved every time data is modified.
•
Trigger condition defined and fulfilled. The saving procedure will
be completed.
Displaying the last 20 I/O maps
6. When the trigger condition has been fulfilled, return to TRIGGER
mode.
E-00 will be displayed. The last current input map when the trigger
condition occurred will now be displayed as a yellow LED on the I/O
module.
7. Use the Left key to move back.
The display will show the next lower number E=n (n=0..19).
8. Use the Right key to move forward.
9. Use the High key to set the display to input and the Low key to set
it to output.
Resetting the trigger condition
1. Press the Mode key to select TRIGGER.
2. Press OK to confirm your selection.
If the trigger condition is not fulfilled:
3. Move the channel cursor to the channel that you want to reset, and
press OK 3 times.
Three times
This will delete one trigger condition. The display briefly will look like
the following illustration.
MachinePoint Bus Couplers User Guide
95
Operating Modes
If the trigger condition is fulfilled:
4. If a trigger condition has been fulfilled, delete all the trigger
conditions and the trigger buffer by pressing OK three times.
Trigger conditions are not permanently stored. They are, however,
retained until the bus coupler is switched off.
7.6 LOCK
In LOCK mode, you can permanently set the control state of individual
I/O channels.
Procedure
LOCK directly affects the control states of I/O channels.
Beware of dangerous operating conditions in the controlled
processes! Take measures to prevent invalid operating conditions.
1. Press the Mode key to select LOCK.
2. Press OK to confirm your selection.
3. Move the channel cursor to the desired channel using the Address
keys.
96
MachinePoint Bus Couplers User Guide
Operating Modes
4. Use the High/Low keys to select the control state.
If you have selected an analog channel, the input/output value will be
increased/reduced by 100mV or 100 µA every time you press one of
the keys. You can lock up to eight analog channels.
The selected control state will become active immediately.
The selected control state will be briefly displayed.
The LOCK setting will be permanently stored in the bus coupler
when you exit the LOCK mode. Do not switch the bus coupler off for
about 5 seconds after exiting the mode.
As in FORCE, you can check the current control state by pressing
OK. The value with which the channel is LOCKed will be displayed
when you press OK.
You can recognize LOCK by the vertical bar in the display.
MachinePoint Bus Couplers User Guide
97
Operating Modes
Resetting the LOCK state
1. Go to LOCK mode, and move the channel cursor to the channel
which you want to reset.
2. Press OK 3 times.
The display briefly will look like the following illustration.
7.7 STOP
In STOP mode, all inputs/outputs will be switched off—i.e., all outputs will
be set to zero and will no longer be refreshed. Inputs will no longer be
sent to the PLC.
If a preferred shut-off state has been set, this state is adopted in STOP
mode.
Channels whose control state has been set with LOCK will not be
overridden by the preferred shut-off state.
If you have set shut-off code 2 (via diagnosis code 5) for a module, the
I/O channels of this module will continue to be refreshed.
98
MachinePoint Bus Couplers User Guide
Service and Diagnosis Functions
8 Service and Diagnosis Functions for
BC Bus Couplers
The bus coupler and the I/O modules have extensive service, diagnosis,
and parameterizing functions.
• Service functions are carried out on the bus coupler.
• Diagnosis and parameterizing functions are carried out from the PLC
via the field bus.
8.1 Service Functions
The bus coupler gives you the option to carry out service functions via the
integrated keypad and the display.
Service
function
Profibus
DeviceNet
Modbus/TCP
1
Reserved
Reserved
Reserved
2
Reserved
Set data transmission rate
Reserved
3
Display number of assigned
I bytes
Display number of assigned
I bytes
Display number of assigned
I bytes
4
Display number of assigned
O bytes
Display number of assigned
O bytes
Display number of assigned
O bytes
5
Bus coupler diagnosis range Bus coupler diagnosis range Bus coupler diagnosis range
ON/OFF
ON/OFF
ON/OFF
6
Save specified bus node
configuration
Save specified bus node
configuration
Save specified bus node
configuration
7
User lock-out ON/OFF
User lock-out ON/OFF
User lock-out ON/OFF
8
User lock-out with password
User lock-out with password
Reserved
9
Advanced PROFIBUS-DP
diagnosis ON/OFF
Reserved
Reserved
10
Byte swap mode ON/OFF
Byte swap mode ON/OFF
Reserved
11
Delete bus coupler
EEPROM
Delete bus coupler
EEPROM
Delete bus coupler
EEPROM
12
Display/set bus address
Display/set bus address
Display/set bus address
13
Set data width of counter
and positioning modules
Set data width of counter
and positioning modules
Set data width of counter
and positioning modules
14
Reserved
Reserved
Boot Type (Fixed IP or
DHCP)
15
Reserved
Reserved
Update Firmware
MachinePoint Bus Couplers User Guide
99
Service and Diagnosis Functions
Selecting and Using a Service Function
1. Select RUN or STOP mode (see Setting Operating Modes, page 88).
2. Press the High and Low keys simultaneously.
The display will show S 00.
If Error code E016 or E017 is displayed, the user lock-out on the bus
coupler is active.
3. Use the right Address key to set the required service function.
4. Press OK.
100
MachinePoint Bus Couplers User Guide
Parameterisation and Diagnostics Functions
Service function without parameters
The value for this function will be displayed immediately. After 1s, the
display will return automatically to its initial state—e.g., service functions
3 and 4.
Service function with parameters
The currently set parameter value will be displayed.
1. Alter the value with the Address keys.
2. Press OK to confirm.
Service function 1
Reserved.
Service function 2
Service function 3
Setting the data transmission rate for DeviceNet
DeviceNet
Baud rate in kbaud
Parameter 0
125
Parameter 1
250
Parameter 2
500
Display number of assigned I bytes
Displays in bytes the size of the input address area used by the bus
node.
MachinePoint Bus Couplers User Guide
101
Service and Diagnosis Functions
Service function 4
Display number of assigned O bytes
Displays in bytes the size of the output address area used by the bus
node.
Service function 5
Bus coupler diagnosis ON/OFF
Parameter 1
The bus coupler uses the first 4 bytes of
I/O data for diagnosis data.
Parameter 0
The bus coupler does not provide
diagnosis data and does not use the 4
bytes of the I/O data.
Default setting: Parameter 1
Service function 6
Save bus node configuration
You can save the current bus node configuration as the specified
configuration. If the configuration is changed (e.g. if a slide contact is
opened accidentally) error E012 will be displayed when you switch the
bus coupler on.
Parameter 0
No specified configuration
Parameter 1
Save current configuration as specified
configuration
Default setting: Parameter 0
Service function 7
User lock-out
Parameter 0
User lock-out OFF
Parameter 1
User lock-out ON
Parameter 15
User lock-out deactivated until next
RESET
Default setting: Parameter 0 (must be confirmed with service function)
See User Lock-Out, page 102.
Service function 8
Bypass user lock-out with password
To bypass the user lock-out function, enter the password specified by the
PLC (a number between 0001-9999) as a parameter.
Parameter 1.. 9999
Operation enabled
See User Lock-Out, page 102.
102
MachinePoint Bus Couplers User Guide
Parameterisation and Diagnostics Functions
Service function 9
Advanced PROFIBUS-DP diagnosis ON/OFF
Parameter 0
Advanced PROFIBUS-DP diagnosis OFF
Parameter 1
Advanced PROFIBUS-DP diagnosis ON
Default setting: Parameter 1
Service function 10
Byte swap mode
The byte swap mode reassigns bit numbers 0-15 in the digital I/O maps
to bytes 1 and 2.
Parameter 0
OFF
Parameter 1
ON
Default setting: Parameter 0
MachinePoint Bus Couplers User Guide
103
Service and Diagnosis Functions
Service function 11
Delete bus coupler EEPROM
All settings for the bus node configuration, bus address, lock masks,
and service functions are deleted or set to the default setting.
Parameter <>15
No changes
Parameter 15
EEPROM is deleted, the default settings are set.
•
Press OK to confirm the service function.
•
The following delete message will appear:
Switch the bus coupler power supply off and on after the delete
message has disappeared.
Service function 12
Display/set bus address
Displays the bus address.
•
104
Change the bus address using the keypad on the bus coupler. The
keys have the following values:
MachinePoint Bus Couplers User Guide
Parameterisation and Diagnostics Functions
Service function 13
modules
Set data width for counter and positioning
1. Select this service function to set the module location number.
Module location number:
6
7
2. Press OK to confirm.
3. Set the required data width using the following parameters:
Parameter 1
Data width 3 words
Parameter 2
Data width 5 words
4. Turn the bus coupler off and on again. This will activate your new
settings.
Default setting: Parameter 2
Service Function 14
Set the Ethernet Boot Type
Parameter = 0
Normal boot
Parameter = 1
DHCP boot
DHCP boot mode has been selected
Display shows «___P» shortly, then «_run». To activate DHCP boot
mode, cycle power. Display reads «dhcP» now. DHCP boot mode is
enabled.
Returning to normal boot mode
Press HIGH/LOW buttons simultaneously. Display reads «_OFF». Cycle
Power. Display should indicate «_run». Normal boot mode is active
again.
Service Function 15
Firmware Update (FU)
Parameter = 15
Update firmware with next reboot
Parameter <> 15
Reserved
Display shows «___P» shortly, then «_run».
Cycle power. Display reads «FIUP».
Bus coupler has entered upload mode.
MachinePoint Bus Couplers User Guide
105
Service and Diagnosis Functions
To leave upload mode without having uploaded firmware, cycle power.
Display should read «_run».
8.2 What if... ?
. . . Error code E001 indicates that the bus coupler is operated without I/O modules?
The bus coupler will still work. You can, for example, set and save the desired base address for the next
application via the PROFIBUS-DP bus coupler keypad.
. . . Error code E002 indicates that an I/O module with an unknown ID has been detected?
The connected I/O modules include at least one whose ID is not supported by the existing firmware
version in the bus coupler. That is, one of the I/O modules is a new product that was unknown when the
bus coupler was manufactured.
. . . Error code E004 indicates that the internal system bus has been interrupted?
During operation, the orange slide contact has been opened, and this has caused internal communication
to be interrupted. A monitoring function integrated in the I/O modules switches all existing 24V outputs to
0V after the “watchdog time” (tw = 100 ms).
The bus coupler is still active on the field bus but only operates its diagnosis interface.
. . . Error code E005 indicates that too many I/O modules are connected to the bus coupler?
The maximum data width for PROFIBUS-DP is 64 bytes I/O.
. . . Error code E006 indicates that the field bus has been interrupted?
In this case, either the field bus plug has been removed from the bus coupler, or the relevant field bus
master is no longer operating the bus. The reason for Error code E006 can also be a cable break.
Any pre-defined preferred shut-off states (see Diagnosis code 5) will now be activated by the bus coupler.
On PROFIBUS-DP, it is certainly possible for part of the network to continue in operation, depending on
where the cable break has occurred.
. . . Error code E007 occurs in LOCK mode?
A write instruction into the internal EEPROM of the bus coupler could not be carried out. If this fault
occurs repeatedly, the hardware is defective. Despite this fault, the system can nevertheless continue to
be operated normally. The only thing you cannot do anymore is save new information such as a new
PROFIBUS-DP address or a modified lock mask.
. . . Error code E012 is briefly displayed when you switch the unit on?
After you have switched the unit on, the bus coupler has detected that the bus node configuration is
different from the specified configuration set with service function 6. Either you have forgotten to close
one of the orange slide contacts (e.g., after a maintenance job), or the number or order of the I/O
modules has changed since the last time the unit was switched on.
Note: If required, set a new specified configuration with service function 6.
. . . Error code E016 or E017 indicates an active user lock-out?
Ensure that the desired operation does not produce an unauthorized operating state.
Press OK to confirm the error message. Cancel the user lock-out using Service function 7 with parameter
0 or 8 with password.
. . . Error code E014 is indicated
The configuration in the PROFIBUS-DP master does not match the current I/O configuration. Also, check
the orange slide contacts and Service function 6.
. . . The red LED BF or the red LED RD is permanently ON after you have switched on the bus coupler?
106
MachinePoint Bus Couplers User Guide
Parameterisation and Diagnostics Functions
A field bus cable is faulty.
The field bus plug is not connected to the bus coupler.
The master component is not operating the field bus properly.
The slave address is set incorrectly.
. . . You have pressed the Mode key by mistake and pre-selected one of the designing modes?
The pre-selected mode indicated by the flashing LED will automatically stop flashing after 8s.
. . . Diagnosis code 2 or 0 indicates overloaded output drivers for one or more modules although none of
the relevant outputs is connected?
There is no 24V supply to the output drivers on the relevant I/O modules. Diagnosis code 2 can only work
if the I/O module has a 24V supply.
. . . You cannot operate the bus coupler?
Maybe the local operation of the bus node has been blocked by the master control via diagnosis code 6,
or the bus coupler is not ready for operation because of an error message.
If you need further help, please call CTC Parker Technical Support at 513-248-1714.
MachinePoint Bus Couplers User Guide
107
Error Messages
9 Error Messages on the BC Bus
Coupler Numerical Display
Error message
Explanation
E001
No I/O module connected.
E002
An I/O module with an ID not supported by the bus coupler has been connected.
E004
Internal data transmission (bus coupler <---> I/O module) has been interrupted (e.g.
slide contact open).
E005
The bus coupler has identified a transgression of the maximum number of I/O
modules.
E006
The field bus has been interrupted or is no longer being operated.
E007
Write access to the EEPROM in the bus coupler has failed.
E012
Current I/O configuration of bus node does not match specified configuration. Specified
configuration can be set with service function 6.
E014
A PROFIBUS-DP master has sent an incorrect I/O configuration to the bus coupler.
E016
User lock-out violated on Safety Level 1.
E017
User lock-out violated on Safety Level 2.
E018
More than 8 lock conditions set for analog channels.
E019
A module in the bus node has a 24V error.
Error messages 2,4,5:
All inputs/outputs are switched off—i.e., all outputs are set to zero and
are no longer refreshed. Inputs are no longer sent to the PLC. The
diagnosis continues to operate in the bus coupler, and diagnosis
messages are transmitted.
All other error messages: The bus node continues to operate. Press
OK or the Mode key to delete this error message.
MachinePoint Bus Couplers User Guide
108
Parameterisation and Diagnostics Functions
10 Parameterisation and diagnostics
functions for all bus couplers
The PLC can trigger parameterisation and diagnostics functions in the bus coupler. To do so, a function
code (FC) is transferred to the bus coupler (with parameters if necessary). The bus coupler carries out the
functions, creates diagnostic data (if required) and makes it available to the PLC. The data can then be
evaluated and processed in the user program.
10.1 Overview
Function 0
Read out group error
Function 1
Monitor power supply of module
Function 2
Monitor overload of output driver
Function 3
Determine process data width of bus node
Function 4
Read out module configuration of bus node
Function 5
Set preferred disconnection state
Function 6
Activate/deactivate operator input inhibit of bus node (only bus
coupler BC)
Function 7
Determine system status of bus node
Function 8
Read out firmware version
Function 9
Set data formats for analog modules
Function 10
Sensor information of a temperature module PT100/PT1000
Function 11
Mode word for temperature module with thermocouples
Functions 12..16
Reserved
Function 17
Set bus address of the bus node *
Function 18
Switch byte swap mode on/off *
Function 19
Switch extended PROFIBUS-DP diagnostics on/off
Function 20
Delete error messages
Function 21
Store/delete bus node configuration
(only bus coupler EC)
Function 255
Reset
* Not supported by Ethernet bus coupler.
The functions can be switched on and off on bus coupler BC with service
function 5, see page 102.
When the functions are switched off, no address space is occupied.
10.2 Data structure
The parameterisation and diagnostics data is always mapped on the first
2 words of output data (PLC --> bus coupler) and the first 2 words of input
data (bus coupler --> PLC).
MachinePoint Bus Couplers User Guide
109
Parameterisation and Diagnostics Functions
SPS/PLC = Programmable controller, EC/BC = Bus coupler EC / bus
coupler BC
Byte 2 of data word 2 (DW 2) is always reserved for the function code
(FC).
Output data >
< Input data
10.3 Sequence
The PLC triggers a function in which DW 2 Byte 2 of the respective
function code is sent to the bus coupler. The bus coupler carries out the
function within a bus cycle or a PLC cycle. Once the function has been
processed, the function code is repeated in the response of the bus
coupler in DW 2 Byte 2.
Important
110
If the same function is used several times in succession by the master,
the function 255 (reset) must be executed in between. This ensures
that the completed signal of the bus coupler is evaluated correctly.
MachinePoint Bus Couplers User Guide
Parameterisation and Diagnostics Functions
10.4 Function 0 – Read out group error
Function 0 supplies the group error message and the last error code.
Output data >
< Input data
Group error message
DW 1 Byte 1
Current error
Bit no.
DW 2 Byte 1
0
A module of the bus nodes reports an overload of the
output driver.
1
A module of the bus node reports an error in the 24 V
power supply.
2
An error message is generated and displayed on the bus
coupler. The error message is encoded and transferred to
DW 1 Byte 2 (see below).
Error bits from DW 1 Byte 1 are stored statically.
The error bits are deleted if the diagnostics function has been reset with
function 255 or the bus coupler has been switched off.
DW 1 Byte 2, EC (error code)
The error code is also displayed as an error message on the bus coupler.
MachinePoint Bus Couplers User Guide
111
Parameterisation and Diagnostics Functions
10.5 Function 1 – Monitor power supply of module
Function 1 provides information about the status of the power supply of
the output driver for the extension modules.
Output data >
< Input data
In the above example, the bus coupler reports an error in the power
supply for extension modules 3 and 6.
DW 1, error bits 0 - 15
Bit value
Meaning
0
Output driver of the extension module at position n is supplied
correctly with 24 V.
1
24 V supply of the module has not been connected correctly at
position n*.
* The module position n is identical to the bit position in the diagnosis
word
Location (position) of the modules by number:
112
MachinePoint Bus Couplers User Guide
Parameterisation and Diagnostics Functions
10.6 Function 2 – Monitor overload of output driver
Function 2 provides information about the status of the 24 V output driver
of the extension modules.
Output data >
< Input data
In the above example, the bus coupler reports an overload error of the
output driver for extension modules 2 and 5.
DW 1, status bits 0-15
Bit value
Meaning
0
All the output drivers of the extension module at position n* are
functioning correctly
1
At least one of the output drivers of the extension module at
position n* is overloaded
*The module position n is identical to the bit position in the diagnosis
word
Location (position) of the modules by number:
This diagnosis refers to the total module and not individual channels.
Important
It is only valid if the relevant module is supplied with 24 V. If the power
supply is not present, this diagnostics bit has no meaning.
MachinePoint Bus Couplers User Guide
113
Parameterisation and Diagnostics Functions
10.7 Function 3 – Determine process data width of
bus node
Function 3 provides the process data width of the bus node.
Output data >
< Input data
114
DW 1 Byte 1, Out
Number of output bytes
DW 1 Byte 2, In
Number of input bytes
MachinePoint Bus Couplers User Guide
Parameterisation and Diagnostics Functions
10.8 Function 4 – Read out module configuration of
bus node
Function 4 supplies the current configuration of 3 sequential extension
modules.
Output data >
< Input data
DW 2 Byte 1, n (position of first module*)
The position n of the module must be entered but the actual configuration
should be determined at positions n, n+1, n+2.
Location (position) of the modules by number:
DW 1 and DW 2, MK (module identifier)
In diagnosis words 1 and 2, the module identifiers MK are provided of the
modules which are currently connected on the bus coupler from position
n onwards.
See the manual “MachinePoint Expansion Modules” for module
identifiers.
Module identifiers
Module designation
1
MachinePoint 8 I/O
2
MachinePoint 16 I
3
MachinePoint 16 O
4
MachinePoint 8 I, 8 I/O
5
MachinePoint 4AI/4AO ± 10 V
6
MachinePoint 4AI ± 10 V
7
MachinePoint 4AI/4AO 20 mA
8
MachinePoint 4AI 20 mA
14d / 0Eh
MachinePoint PT100
10d / 0Ah (6 I/O bytes)
11d / 0Bh (10 I/O bytes)
MachinePoint COUNTER
12d / 0Ch (6 I/O bytes)
13d / 0Dh (10 I/O bytes)
MachinePoint POSITION
MachinePoint Bus Couplers User Guide
115
Parameterisation and Diagnostics Functions
116
16d / 10h
MachinePoint 4AI/4AO 4-20 mA
17d / 11h
MachinePoint 4AI 4-20 mA
19d / 13h
MachinePoint 4 O RELAY
20d / 14h
MachinePoint TC
24d / 18h
MachinePoint 4 I AC 115 V
25d / 19h
MachinePoint 4 I AC 230 V
MachinePoint Bus Couplers User Guide
Parameterisation and Diagnostics Functions
10.9 Function 5 – Set preferred disconnection state
Function 5 defines the switch-off behaviour of the outputs using a
preferred disconnection state. The preferred state is adopted:
•
on disruption of the bus voltage
•
in STOP mode.
A disconnection code (AC) can be assigned to each module which
defines its preferred disconnection state.
Output data >
< Input data
DW 1 Byte 1, AC (disconnection code)
Disconnection code
Meaning
dec.
bin.
0
0000 0000
All the digital outputs of the relevant extension module
are set to Low while all analog outputs are set to 0 V /
0 mA.
1
0000 0001
All the outputs of the relevant extension module are
set to High while all analog outputs are set to +10 V /
20 mA. (In the case of the 4AI/4AO 0...10 V module,
the outputs are set to 5 V)
2
0000 0010
All the outputs of the relevant extension module are
refreshed. On interruption of the bus connection, the
last switching state of the I/O channels is maintained.
Basic setting: Disconnection code 0 for all modules
DW 1 Byte 2, n (position of module)
The position of the modules n must be entered whose preferred
disconnection state must be defined.
Location (position) of the modules by number:
MachinePoint Bus Couplers User Guide
117
Parameterisation and Diagnostics Functions
The preferred disconnection state is superimposed by the LOCK
configuration.
Caution
When bus coupler diagnosis is ON, the bus master can initiate diagnosis
functions in the bus coupler by transmitting a diagnosis code. See
Parameterisation and Diagnostics Functions for All Bus Couplers on page
109 for more information.
118
MachinePoint Bus Couplers User Guide
Parameterisation and Diagnostics Functions
Function 6 – Activate/deactivate operator input inhibit of bus node
Only for bus coupler BC.
Function 6 activates the operator input inhibit with a password on security
level II. A 16 bit number in the decimal range 0001 to 9999 is used as a
password (PW).
Output data >
< Input data
DW 1, PW (password)
0000
Local operation of the bus coupler is enabled if an
operator input inhibit was previously active on
security level II.
0001 to 9999
Operator input inhibit is active on security level II,
with password protection.
The password is stored in the non-volatile memory of the bus coupler.
Operation is enabled once the password has been changed from (0001
to 9999) to 0000. Security level 1 and 2 is not active.
DW 1 Byte 2, EC (error code)
1
Successful
FFhex
Password outside the range
Diagnosis word 1 reports whether the password has been stored
successfully.
MachinePoint Bus Couplers User Guide
119
Parameterisation and Diagnostics Functions
10.10 Function 7 – Determine system status of bus
node
Function 7 provides the current system status of the bus node.
Output data >
< Input data
The system status is composed of several items of information:
DW 1 Byte 1, TRIGGER status or LOCK conditions
Bit no.
Bit value
Status
0
0
TRIGGER input is not defined
1
TRIGGER input is defined
0
LOCK condition is not defined
1
LOCK condition is defined
1
DW 1 Byte 2, BA (operating mode)
Value
Operating mode
6
FORCE
7
TRIGGER
8
LOCK
9
STOP
10dec
ONLINE
11dec
RUN
DW 2 Byte 1, EC (error code)
The error code is identical to the error message which is displayed on the
bus coupler.
120
MachinePoint Bus Couplers User Guide
Parameterisation and Diagnostics Functions
10.11 Function 8 – Read out firmware version
Function 8 supplies the firmware version of the bus coupler.
Output data >
< Input data
DW 1, FW (firmware version)
The firmware version has a hexadecimal code and is embedded in DW 1.
10.12 Function 9 – Set data formats for analog
modules
Function 9 sets the data format of the analog values for the analog
modules.
Output data >
< Input data
DW 1 Byte 1, n (location of module)
Data word 1 specifies the module for which the data format should be set.
Location (position) of the modules by number:
DW 1 Byte 2, I/O (selection of inputs or outputs)
0 = inputs, 1 = outputs
MachinePoint Bus Couplers User Guide
121
Parameterisation and Diagnostics Functions
DW 2 Byte 1, FC (format code)
Important
122
Format code
Data format
0
±10 V in two’s complement (-2048 .... +2047)
1
±10 V in mV (-10000 .... +10000)
2
0...20 mA in two’s complement (0...4095)
3
0...20 mA in µA (0...20000)
4
4...20 mA (S5 format for 0 ... 20 mA)
5
0 ... 10 V (in mV 0 ... 10000)
6
PT 100 in 0.1°C
7
4...20 mA S7 format
8
4...20 mA S5 format
If the data format mV or µA is used, the input signal delay of the digital
I/O modules that are operated on the same bus coupler is extended by
2 ms.
MachinePoint Bus Couplers User Guide
Parameterisation and Diagnostics Functions
10.13 Function 10 – Read out sensor information of
temperature module
Function 10 provides information about the sensors on the temperature
module.
Output data >
< Input data
DW 1 Byte 2, n (location of module)
Data word 1 specifies which temperature module the information is
expected from.
Location (position) of the modules by number:
DW 1 Byte 2, sensor information
Bit no.
Bit value
Meaning
0
0
PT100 on channel 1
1
0
1
0
1
0
1
PT1000 on channel 1
PT100 on channel 2
PT1000 on channel 2
PT100 on channel 3
PT1000 on channel 3
PT100 on channel 4
PT1000 on channel 4
1
2
3
A fault occurs at the respective channel at a constant measured value of
4500 dec. Using the sensor information, it is possible to distinguish
between a cable breakage and a short circuit.
Bit value
Meaning
0
1
Short circuit
Cable breakage or sensor not connected
MachinePoint Bus Couplers User Guide
123
Parameterisation and Diagnostics Functions
10.14 Function 11 – Mode word for temperature
module with thermocouples
Function 11 is used to configure a temperature module with
thermocouples.
Output data >
< Input data
Output data
DW 1, mode word
The parameters for characteristic curves, channel number, resolution and
number format are transferred in data word 1.
Parameter
Meaning
Characteristic
curve
K characteristic curve
J characteristic curve
L characteristic curve
Reserved
Reserved (must always be 00)
Channel
number
4 channels used
1 channel used
2 channels used
3 channels used
Resolution
0.1°C
0.2°C
Reserved
Reserved
Number format
124
SIMATIC S7
MachinePoint Bus Couplers User Guide
Parameterisation and Diagnostics Functions
SIMATIC S5
Voltage
Reserved
Basic setting: All bits = 0 (K characteristic curve; 4 channels; 0.1°C; S7)
MachinePoint Bus Couplers User Guide
125
Parameterisation and Diagnostics Functions
DW 2 Byte 2, n (location of module)
Data word 2 Byte 2 specifies which temperature module the information
applies to.
Location (position) of the modules by number:
Input data
DW 1 Byte 1, always 01
10.15 Function 17 – Read out bus address
Function 17 provides the bus address of the bus coupler. This function is
not supported by the Ethernet bus coupler.
Output data >
< Input data
DW 1 Byte 2, ADR (bus address 0 to 255)
126
MachinePoint Bus Couplers User Guide
Parameterisation and Diagnostics Functions
10.16 Function 18 – Switch byte swap mode on/off
Function 18 sets the byte swap mode. This mode modifies the
assignment of input/output data to the I/O images. See also service
function 10 on page 123.
This function is not supported by the Ethernet bus coupler.
Output data >
< Input data
DW 1 Byte 2, MOD (mode)
0
Switched off (OFF)
1
Switched on (ON) for all digital extension modules
2
Switched on (ON) for all digital extension modules and counter,
positioning and analog modules as well as diagnostics data
3
Switched on (ON) for counter, positioning and analog modules
as well as diagnostics data
Basic setting: Mode 0
Input data
DW 1 Byte 2, 0/1
0
Setting failed
1
Byte swap mode activated successfully
The setting is stored in the non-volatile memory in the bus coupler.
Important
Example
MachinePoint 16 I without byte
swap
with byte swap
Byte 1
Byte 1
Byte 2
Byte 2
Bit
Terminal
Bit
Terminal
Bit
Terminal
Bit
Terminal
8
X2.8
0
X1.0
8
X1.0
0
X2.8
9
X2.9
1
X1.1
9
X1.1
1
X2.9
10
X2.10
2
X1.2
10
X1.2
2
X2.10
MachinePoint Bus Couplers User Guide
127
Parameterisation and Diagnostics Functions
11
X2.11
3
X1.3
11
X1.3
3
X2.11
12
X2.12
4
X1.4
12
X1.4
4
X2.12
13
X2.13
5
X1.5
13
X1.5
5
X2.13
14
X2.14
6
X1.6
14
X1.6
6
X2.14
15
X2.15
7
X1.7
15
X1.7
7
X2.15
128
MachinePoint Bus Couplers User Guide
Parameterisation and Diagnostics Functions
10.17 Function 19 – Switch extended PROFIBUS-DP
diagnostics function on/off
Function 19 switches the extended PROFIBUS-DP diagnostics function
on or off.
Output data >
< Input data
Output data
DW 1 Byte 2, MOD (mode)
><1
Extended diagnostics switched OFF
1
Extended diagnostics switched ON
Basic setting: Mode 1
Input data
DW 1 Byte 2, MOD (mode)
The parameters are reflected in DW 1, Byte 2 of the input data.
See also service function 9 on page 103 and diagnostics on PROFIBUSDP on page 25.
MachinePoint Bus Couplers User Guide
129
Parameterisation and Diagnostics Functions
10.18 Function 20 – Delete error messages
Function 20 deletes the error message which is displayed on the bus
coupler. The current group message and error bits are likewise deleted
(as for function 0).
The same functions are carried out as when the error message is deleted
with the OK button of the bus coupler BC.
130
MachinePoint Bus Couplers User Guide
Parameterisation and Diagnostics Functions
10.19 Function 21 – Store/delete bus node
configuration
(Only bus coupler EC)
The actual configuration of the bus node can be stored as a setpoint
configuration. A modification of the actual configuration (e.g. by
accidentally opening a connecting slide) then leads to the bus coupler
switching on with error message E012, flashing code 4.
Output data >
< Input data
Output data
DW 1 Byte 2, MOD (mode)
><1
Delete setpoint configuration and do not carry out
any more checks
1
Store the actual configuration as a setpoint
configuration
Basic setting: 0
Input data
DW 1 Byte 2, MOD (mode)
The parameters are mirrored in DW 1 Byte 2 of the input data.
MachinePoint Bus Couplers User Guide
131
Parameterisation and Diagnostics Functions
10.20 Function 255 - Reset
The reset function causes all the error messages to be reset as when
deleting the error messages with the OK button of the bus coupler BC.
No functions are executed.
132
MachinePoint Bus Couplers User Guide
Parameterisation and Diagnostics Functions
11 Technical Data and Dimensions
11.1 Environmental Specifications
Climatic conditions
Ambient operating temperature
32° to 131°F (0 to 55°C) category KV to DIN 40040, vertical installation, free air
circulation
Storage temperature
13° to 158° F (-25 to 70°C) category HS to DIN 40040
Relative humidity
30-95% (category F to DIN 40040), no condensation
Air pressure in operation
860-1060hPa
Mechanical strength
Vibration
DIN IEC 68-2-6
10-57Hz constant amplitude 0.075mm
57-150Hz constant acceleration 1g
Electrical safety
Protection type
IP 20 to EN 60529
Clearance/creepage distance
DIN EN 61131-2 and DIN EN 50178 between electrical circuits and objects as well
as between decoupled electrical circuits corresponding to overload category II,
contamination level 2
Test voltage
350V AC/50Hz for rated equipment voltage 24V DC
Electromagnetic compatibility
Electrostatic discharge
EN 61000-4-2: 4kV contact discharge
Electromagnetic fields
EN 61000-4-3: field intensity 10V/m, 80-1000MHz
Burst
EN 61000-4-4: 2kV on DC supply lines, 1kV on I/O signal and serial interface lines
Interference emissions
EN 55011: Limit category A, Group 1
Mechanical and installation
Housing material
PA 6.0 GF20 black
Rail
DIN rail EN 50022-35
Connection system
Connection
Spring terminal
Conductor size
finely stranded*: 0.002-0.02 in. 0.14-1.5mm )
2
2
single-core: 0.01-0.04 in. (0.5-2.5mm )
2(
2
*If a wire end ferrule is used it must be pressed air-tight.
Stripping length
0.4 in. (10mm)
11.2 Input Signal Delay
MachinePoint Bus Couplers User Guide
133
Parameterisation and Diagnostics Functions
Input signal delay
Typical
2 - 4ms
(any bus coupler with three digital I/O modules)
The input signal delay is longer:
• If you use analog I/O modules on the same bus coupler (approx. 7 14ms with 2 x analog, 1 x digital)
• Every time you press a key on the bus coupler (approx. 4ms)
• When you use the advanced operating modes (e.g., LOCK 3ms)
11.2.1
Modbus/TCP Input Signal Delay
(depends on specific conditions)
Example condition
Bus coupler with 3 I/O
modules
typ. 12 ms
Bus coupler with 2 analog
and 1 digital module
approx. 12-18 ms
Individual push button
operations on the bus
coupler
approx. 12 ms
Using LOCK mode on the
bus coupler
approx. 12 ms
NOTE
The input signal delay is extended
- when using analog I/O modules on the same bus coupler
- for individual push button operations on the bus coupler
- when using extended operating modes on the bus coupler (such as LOCK)
134
MachinePoint Bus Couplers User Guide
Parameterisation and Diagnostics Functions
11.3 Physical Dimensions
11.3.1 EC Bus Couplers
1 For DIN rail EN 50022-35
11.3.2 BC Bus Couplers
1. Only for bus coupler
For DIN rail EN 50022-35
MachinePoint Bus Couplers User Guide
135
Parameterisation and Diagnostics Functions
11.4 Power Consumption
The bus coupler has an integrated power supply unit which makes the
internal 5 V power supply available for the extension modules from the 24
V supply voltage.
To determine the loading of the internal 5 V power supply, the maximum
power consumption of all the connected extension modules must be
added together.
The maximum load of the internal 5 V power supply is 5 watts.
Note
If the maximum load is exceeded, extension modules should be removed
from the bus node.
Power consumption
(internal 5 V power supply)
MachinePoint 16 I
0.275 W
MachinePoint 4 I AC 115 V
0.2 W
MachinePoint 4 I AC 230 V
0.2 W
MachinePoint 16 O
0.325 W
MachinePoint 4 O RELAY
0.25 W
MachinePoint 8 I/O
0.325 W
MachinePoint 8 I, 8 I/O
0.325 W
MachinePoint 4AI ± 10 V
0.325 W
MachinePoint 4AI 0…10 V
0.325 W
MachinePoint 4AI/4AO ± 10 V
0.325 W
MachinePoint 4AI/4AO 0…10 V
0.325 W
MachinePoint 4AI 20 mA
0.325 W
MachinePoint 4AI/4AO 20 mA
0.325 W
MachinePoint 4AI/4AO 4…20 mA
0.325 W
MachinePoint 4 AI/PT100
0.325 W
MachinePoint 4 AI/TC
0.325 W
MachinePoint COUNTER
1.1 W
MachinePoint POSITION
1.25 W
Power consumption of 24 V
To determine the power consumption of a bus node from the external 24
V power supply, the power consumption of the bus coupler and that of
the connected extension modules (external 24 V power supply) must be
added together.
136
MachinePoint Bus Couplers User Guide
Parameterisation and Diagnostics Functions
The power consumption of the bus coupler is calculated by adding the
consumption of the bus coupler (5 watts) to the total internal power
consumption (5 V power supply) of the connected extension modules.
Power consumption
(external 24 V power supply)
Bus coupler
5W + total internal power consumption (from the internal 5 V power supply) of the
connected extension modules
MachinePoint 16 I
0.25 W
MachinePoint 4 I AC 115 V
None
MachinePoint 4 I AC 230 V
none
MachinePoint 16 O
0.25 W
MachinePoint 4 O RELAY
2W
MachinePoint 8 I/O
0.25 W
MachinePoint 8 I, 8 I/O
0.25 W
Without input currents / load currents
MachinePoint 4AI ± 10 V
0.36 W
Maximum loading of analog outputs
MachinePoint 4AI 0…10 V
0.36 W
MachinePoint 4AI/4AO ± 10 V
4.3 W
MachinePoint 4AI/4AO 0…10 V
4.3 W
MachinePoint 4AI 20 mA
3.6 W
MachinePoint 4AI/4AO 20 mA
6W
MachinePoint 4AI/4AO 4…20 mA
6W
MachinePoint 4AI/PT100
3.8 W
MachinePoint 4AI/TC100
2.9 W
MachinePoint COUNTER
0.25 W
Without input currents / load currents
MachinePoint POSITION
0.25 W
Without input currents / load currents
MachinePoint Bus Couplers User Guide
Without input currents
Without load currents
Without input currents / load currents
Including load current 4 x PT 100
137
Parameterisation and Diagnostics Functions
11.5 Data Width and Examples of Address
Assignment
Module type
Byte inputs
Byte outputs
MachinePoint BC DP
4
4
If diagnosis is switched on
with service function 5,
otherwise 0
If diagnosis is switched on
with service function 5,
otherwise 0
MachinePoint EC DP
4
If configured, otherwise 0.
4
If configured, otherwise 0.
MachinePoint BC CAN
DN
4
4
If diagnosis is switched on
with service function 5,
otherwise 0
If diagnosis is switched on
with service function 5,
otherwise 0
MachinePoint EC CAN
DN
4
4
If configured, otherwise 0.
If configured, otherwise 0.
MachinePoint Ethernet
4
4
If diagnostics function is
activated, otherwise 0.
If diagnostics function is
activated, otherwise 0.
MachinePoint 16 I
Byte 1
Byte 2
Terminal assignment
X2.15 ...
X2.8
X1.7 ... X1.0
MachinePoint 16 O
Byte 1
Byte 2
Terminal assignment
X2.15 ... X2.8
X1.7 ... X1.0
Byte 1
Byte 2
Byte 1
Byte 2
Terminal assignment
not used
X1.7 ... X1.0
not used
X1.7 ... X1.0
MachinePoint 8 I 8 I/O
Byte 1
Byte 2
Byte 1
Byte 2
Terminal assignment
X2.7 ...
X2.0
X1.7 ... X1.0
not used
X1.7 ... X1.0
MachinePoint 4 I AC
115 V
unoccupied
See wiring
diagram
MachinePoint 4 I AC
230 V
unoccupied
See wiring
diagram
unoccupied
See wiring
diagram
MachinePoint 8 I/O
MachinePoint 4 O
RELAY
138
MachinePoint Bus Couplers User Guide
Parameterisation and Diagnostics Functions
Word Inputs
Word Outputs
MachinePoint 4AI ±10V
Word 1 to 4
MachinePoint 4AI/4AO
±10V
Word 1 to 4
MachinePoint 4AI
0...10 V
Word 1 to 4
MachinePoint 4AI/4AO
0…10 V
Word 1 to 4
MachinePoint 4AI 20mA
Word 1 to 4
MachinePoint 4AI/4AO
20mA
Word 1 to 4
MachinePoint 4AI/Pt100
Word 1 to 4
MachinePoint 4AI/4AO
4…20 mA
Word 1 to 4
MachinePoint 4AI/PT100
Word 1 to 4
MachinePoint 4AI/TC
Word 1 to 4
MachinePoint Counter
Word 1 to 5 or 1 to 3
depending on setting with
service function 13
Word 1 to 5 or 1 to 3
depending on setting with
service function 13
MachinePoint Position
Word 1 to 5 or 1 to 3
depending on setting with
service function 13
Word 1 to 5 or 1 to 3
depending on setting with
service function 13
MachinePoint Bus Couplers User Guide
Word 1 to 4
Word 1 to 4
Word 1 to 4
Word 1 to 4
139
Parameterisation and Diagnostics Functions
Examples of Address Assignments
The bus node with the following configuration: ....
.... uses the address range:
The 00 base addresses have been chosen as an example only and must
be adapted to the respective PLC system.
•
The bus coupler (BC) uses 4 bytes for diagnosis data if diagnosis
is switched on with service function 5. If diagnosis is switched off,
no address space is used.
•
The 8 I/O module only uses the lower byte. Bytes 08 and 04 are
not used.
1 Byte start addresses 2 Bit numbering
The maximum number of I/O bytes per bus node is 64 in each
case.
140
MachinePoint Bus Couplers User Guide
Appendix
12 Appendix
12.1 Glossary
Combination channels
I/O channels that can be used as either inputs or outputs. For example,
both an input address space and an output address space are reserved
for a process map.
Slide contacts
The orange slide contacts on top of the module that link the modules to
the bus coupler.
Potential relay terminals
Spring terminals that can be used to relay power from one module to the
next in order to reduce the number of terminal contacts.
141
MachinePoint Bus Couplers User Guide
Appendix
12.2 Trademarks
• MS-DOS is a registered trademark of Microsoft Corporation.
• WINDOWS is a registered trademark of Microsoft Corporation.
• IBM is a registered trademark of International Business Machines.
• SIMATIC and SINEC are registered trademarks of Siemens AG.
• DeviceNet is a registered trademark of the Open DeviceNet Vendor
Association (O.D.V.A.).
• All other trademarks or product names are registered trademarks of
their respective owners.
142
MachinePoint Bus Couplers User Guide
Safety-related Information
13 Safety-related Information
The term “automation system,” as used in this manual, includes control units and their components
(modules); other parts, such as racks, cables, and operator panels; and software that is used for
programming, activating, and operating the control units. This User Guide can only describe a fraction of
the automation system (for example, the modules).
Automation systems do not normally cause damage to equipment or present health hazards, provided
that they are used for their intended purpose. However, if actuators, such as engines, hydraulic units, etc.
are connected to the system, or if configuration, installation, maintenance, and operation of the complete
system or of a machine are performed incorrectly, or if instructions in this manual are ignored, or personnel
working on the system are not suitably qualified, problems may occur.
13.1 Correct Use of the System
CTC Parker automation systems are state-of-the-art products and are manufactured to recognized safety
requirements. However, dangerous situations may still occur for operators or third parties. Also, the
functioning of these systems or of other equipment may deteriorate while the systems are in operation.
The automation system must be used for its intended purpose, observing the regulations and safety
instructions given in this User Guide. Correct transport, storage, installation, operation, and maintenance
of the system are all prerequisites for smooth, safe operation of the control unit. Incidents or problems
that may affect system safety must be immediately resolved.
Automation systems are designed exclusively to control machines and systems. They are not intended for
any other use than the above. Therefore, the manufacturer accept no liability for any damages resulting from
incorrect use of the systems.
When using automation systems, all instructions given in this User Guide regarding mechanical and electrical
setup, design, and operation must be observed.
13.2 Selection and Qualification of Personnel
All configuring, programming, installation, design, operation, and
maintenance work on the automation system must be carried out by
trained personnel, such as electricians or electrical engineers.
Personnel responsible for configuring and programming the system
must be familiar with all safety-related issues in automation
technology.
System operators must be instructed on the operation of the control
unit and must be familiar with the relevant operating instructions. All
personnel responsible for installing, designing, and maintaining the
system must have had appropriate training, qualifying them to work
on automation systems.
143
MachinePoint Bus Couplers User Guide
Appendix
13.3 Configuring, Programming, Installation,
Commissioning, and Operation
In most cases, the automation system will be part of a bigger system and will be used to control machines
in that system. When configuring, installing, and commissioning automation systems to control machines, the
machine manufacturer and the user must observe the safety regulations as defined in the machinery directive
89/392/EWG. For specific applications, national accident prevention regulations, such as VBG 4.0 will apply.
Safety-related components on the controlled machine must be designed so that they operate.
independently from the control system. Operating conditions should never cause danger, not even for a
short time. In case of danger, an emergency stop must be triggered immediately. For this reason,
emergency stop components must work in any operating mode. In an emergency stop, the power supply to
all breakers controlled by the control unit must be cut off. The power supply can be cut off using a safety
relay. In addition, measures must be taken to restart an interrupted control program after voltage dips or
power failures.
To prevent an open-circuit from causing non-controllable conditions in the control unit, safety precautions
must be taken in the I/O coupling hardware and software. In addition, control elements must be installed in
a place where they are protected against inadvertent use.
13.4 Maintenance
Measuring and testing on the active system must be carried out in accordance with the regulations and
instructions of the VBG 4.0 accident prevention regulation. Appropriate power tools must be used.
The system must always be disconnected from the mains before it is opened (either disconnect the mains
plug or use a cut-out switch).
Control modules may only be replaced when the unit is switched off. Disassembly and assembly must be
carried out according to the directives for mechanical assembly.
Fuses may only be replaced with those types specified in the Technical Data and Dimensions section of this
User Guide.
Batteries may only be replaced with those types specified in the Technical Data and Dimensions section of
this User Guide. Batteries must always be disposed of as hazardous waste.
13.5 High Voltages
When opening the system cabinet or removing the system
components' casing, certain parts of the automation system are
exposed. These parts may produce dangerous, high voltages.
The user must prevent any unauthorized and incorrect access to the system (for example, by ensuring
that the control cabinet is locked).
Personnel must be familiar with all sources of danger and measures for designing and maintaining the
system in keeping with the instructions given in this manual.
144
MachinePoint Bus Couplers User Guide
Safety-Related Information
14 Index
Address assignment
PROFIBUS-DP, 138
Addressing. See Address assignment
Bus connection
MACHINEPOINT EC PROFIBUS-DP, 14
Bus coupler
MACHINEPOINT EC PROFIBUS-DP, 12
Cable length
DeviceNet, 40
PROFIBUS-DP, 23
Cable parameters
PROFIBUS-DP, 23
Channel cursor, 89
Climatic conditions, 133
Combination channels, 83
Conductor sizes, 133
Connecting the power supply, 81
Connectors
DeviceNet, 39
PROFIBUS-DP, 22
Data transmission rate
DeviceNet, 39
DeviceNet
cable length, 40
connectors, 39
data transmission rate, 39
EDS files, 41
interface connectors, 39
keypad on the bus coupler, 37
LED display on the bus coupler, 35
line length, 40
numerical display on the bus coupler, 36
operating mode display on the bus coupler, 36
setting the address, 38
setting the MAC ID, 38
terminating resistors, 39
wiring, 39
Diagnosis
bus coupler numerical display, 108
on the PROFIBUS-DP, 25
DIN rail, 75, 133
DIN rail mounting, 75
end clamps, 75
Display mode (during RUN), 90
EDS files for DeviceNet, 41
Electrical installation, 79
connecting the power supply, 81
Electrical safety, 133
EMC, 133
end clamps for DIN rail mounting, 75
Error messages
bus coupler numerical display, 108
E001 to E018, overview, 108
E002, 106
E004, 106
E005, 106
E006, 106
145
E007, 106
E012, 106
FORCE mode, 91
Ground symbol
symbol on terminal, 82
GSD files
PROFIBUS-DP, 25
Housing material, 133, 134
Input signal delay, 133
Installation guidelines, 82
Installation position, 74
Interface connectors
DeviceNet, 39
PROFIBUS-DP, 22
Interlinking modules, 77
Keypad
on the DeviceNet bus coupler, 37
on the PROFIBUS-DP bus coupler, 19
LED display on Bus coupler
MACHINEPOINT EC PROFIBUS-DP, 14
LED display on the bus coupler
DeviceNet, 35
PROFIBUS-DP, 17
Line length
DeviceNet, 40
PROFIBUS-DP, 23
LOCK mode, 96
Lock-out, 85
MACHINEPOINT EC CAN DN, 30
Technical data, 31
MACHINEPOINT EC PROFIBUS-DP, 12
Bus connection, 14
Setting the address, 14
Mechanical installation, 74
Mechanical strength, 133
Modbus function codes
0x0001 - Read Coils, 62
0x0002 - Read Discrete Inputs, 62
0x0003 - Read multiple registers, 64
0x0004 - Read input register, 64
0x0005 - Write Coil, 66
0x0006 - Write single register, 66
0x0007 - Read Exception Status, 67
0x0008 - Read/write diagnostic functions, 67
0x000F - Force Multiple Coils, 67
0x0010 - Write multiple registers, 68
0x0017 - Read/Write multiple registers, 69
Modbus Image
MODBUS functions, 60
telegram architecture, 61
Numerical display
for diagnosis on bus coupler, 108
on the DeviceNet bus coupler, 36
on the PROFIBUS-DP bus coupler, 18
Operating mode display
on the DeviceNet bus coupler, 36
on the PROFIBUS-DP bus coupler, 17
MachinePoint Bus Couplers User Guide
Appendix
Operating modes, 87
Display mode, 90
displaying the active, 89
FORCE, 91
LOCK, 96
RUN, 90
setting, 88
STOP, 98
TRIGGER, 94
Operator input inhibit
via parameterisation function, 119
Password, 85
Potential relay terminals, 82
Potentials, relaying, 82
Preferred shut-off state, 98
Process data width
PROFIBUS-DP, 138
Process Image
example, 58
granularity, 58
restructuring, 58
PROFIBUS-DP
address assignment, 138
cable length, 23
cable parameters, 23
connectors, 22
diagnosis on the, 25
GSD files, 25
interface connectors, 22
keypad on the bus coupler, 19
LED display on Bus coupler EC, 14
LED display on the bus coupler, 17
line length, 23
numerical display on the bus coupler, 18
operating mode display on the bus coupler, 17
process data width, 138
response times, 26
setting the address, 19
wiring, 22
Relaying potentials, 82
Response times
PROFIBUS-DP, 26
RUN mode, 90
Safety level I and II, 85
Safety-related information
accident prevention regulation, 144
configuring, 144
correct use of the system, 143
designing, 144
emergency stop component, 144
high voltages, 144
installation, 144
146
maintenance, 144
programming, 144
selection of personnel, 143
Sampling commands, 61
Service functions
overview, 99
selecting on bus coupler, 100
Setting
DeviceNet data transmission rate, 39
MAC ID DeviceNet, 38
operating modes, 88
PROFIBUS-DP address, 19
Setting the address
DeviceNet, 38
MACHINEPOINT EC PROFIBUS-DP, 14
PROFIBUS-DP, 19
Shield
for signal lines, 82
Slave address. See Address / Addressing
Slide contact, 77
STOP mode, 98
Stripping length, 133
Technical data
climatic conditions, 133
conductor sizes, 133
connection system, 133
electrical safety, 133
electromagnetic compatibility EMC, 133
for all modules, 133
MACHINEPOINT BC CAN DN, 34
MACHINEPOINT BC DP, 16
MACHINEPOINT BC PROFIBUS-DP, 52
MACHINEPOINT EC CAN DN, 31
MACHINEPOINT EC PROFIBUS-DP, 13
mechanical and installation, 133
mechanical strength, 133
Mechanics and installation, 134
stripping length, 133
wire end ferrule, 133
Technical Support (hotline), 107
Terminal descriptions. See Technical Data and
Dimensions
Terminating resistors
DeviceNet, 39
Trademarks, 142
TRIGGER mode, 94
Warning signs, 3
Wire end ferrule, 133
Wiring
DeviceNet, 39, 40
PROFIBUS-DP, 22
MachinePoint Bus Couplers User Guide
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertisement