SYSMAC CS/CJ-series CS1W-PRM21/CJ1W-PRM21

SYSMAC CS/CJ-series CS1W-PRM21/CJ1W-PRM21
SYSMAC CS/CJ-series
CS1W-PRM21
CJ1W-PRM21
PROFIBUS Master Units
Operation Manual
Revised July 5, 2005
iv
Notice:
OMRON products are manufactured for use by a trained operator and only for the purposes described
in this manual.
The following conventions are used to classify and explain the precautions in this manual. Always
heed the information provided with them.
!DANGER
Indicates information that, if not heeded, is likely to result in serious injury or loss of life.
!WARNING
Indicates information that, if not heeded, could possibly result in serious injury or loss of
life.
!Caution
Indicates information that, if not heeded, could possibly result in minor or relatively serious
injury, damage to the product or faulty operation.
OMRON Product References
All OMRON products are capitalized in this manual. The first letter of the word Unit is also capitalized
when it refers to an OMRON product, regardless of whether it appears in the proper name of the product.
The abbreviation Ch appears in some displays and on some OMRON products. It often means word
and is abbreviated as Wd in the documentation.
The abbreviation PLC means Programmable Logic Controller.
Visual Aids
The following headings appear in the left column of the manual to help you locate different types of
information.
Note Indicates information of particular interest for efficient and convenient operation of the product.
1, 2, 3...Indicates various lists such as procedures, checklists etc.
v
Trademarks and Copyrights
PROFIBUS, PROFIBUS FMS, PROFIBUS DP, PROFIBUS DP-V1, and PROFIBUS PA are trademarks of PROFIBUS International.
Microsoft, Windows, Windows NT, Windows 2000, Windows XP, Windows Explorer and ActiveX are
trademarks of Microsoft Corporation.
Sycon and CIF are trademarks of Hilscher GmbH.
HART® is a registered trademark of HART Communication Foundation.
Other product names and company names in this manual are trademarks or registered trademarks of
their respective companies.
The copyright of the PROFIBUS Master Unit belongs to OMRON Corporation.
 OMRON, 2005
All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form, or
by any means, mechanical, electronic, photocopying, recording, or otherwise, without the prior written permission of
OMRON.
No patent liability is assumed with respect to the use of the information contained herein. Moreover, because OMRON is constantly striving to improve its high-quality products, the information contained in this manual is subject to change without
notice. Every precaution has been taken in the preparation of this manual. Nevertheless, OMRON assumes no responsibility
for errors or omissions. Neither is any liability assumed for damages resulting from the use of the information contained in
this publication.
vi
TABLE OF CONTENTS
About this Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ix
PRECAUTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
1
Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xiv
2
General Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xiv
3
Safety Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xiv
4
Operating Environment Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xv
5
Application Precautions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xvi
6
Conformance to EC Directives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xviii
SECTION 1
Features and Specifications . . . . . . . . . . . . . . . . . . . . . . . . . .
1
1-1
Overview of PROFIBUS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2
1-2
Setting up a PROFIBUS DP Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7
1-3
PROFIBUS Master Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10
1-4
CX-Profibus Configurator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
18
1-5
Basic Operating Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
23
SECTION 2
Installation and Wiring . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
25
2-1
Unit Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
26
2-2
Installing the CS1/CJ1W-PRM21 Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
30
2-3
Initial Setup Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
33
2-4
Setting up a Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
35
2-5
Defining PROFIBUS DP in the Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
39
SECTION 3
Configuration Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
41
3-1
Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
42
3-2
CX-Profibus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
51
3-3
CS1/CJ1W-PRM21 PROFIBUS Master DTM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
63
3-4
C200HW-PRM21 PROFIBUS DP Master DTM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
83
3-5
Generic Slave Device DTM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
92
SECTION 4
Allocated CIO and DM Words . . . . . . . . . . . . . . . . . . . . . . . 105
4-1
Overview of Word Allocations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
106
4-2
Allocated CIO Area Words . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
108
vii
TABLE OF CONTENTS
SECTION 5
FINS Commands and Responses. . . . . . . . . . . . . . . . . . . . . . 121
5-1
FINS Commands and Responses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
122
5-2
Command / Response Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
125
SECTION 6
Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
6-1
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
142
6-2
Setting up a network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
142
6-3
Configuring the Slave Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
149
6-4
Configuring the Master . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
154
6-5
I/O Communication Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
162
6-6
Operating the Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
176
6-7
Monitoring the Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
185
SECTION 7
Troubleshooting and Maintenance . . . . . . . . . . . . . . . . . . . . 193
7-1
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
194
7-2
Troubleshooting Using LED Indicators. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
195
7-3
Troubleshooting Using Error Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
201
7-4
Troubleshooting the Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
204
7-5
Troubleshooting Using the Error Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
214
7-6
Troubleshooting FINS Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
216
7-7
Maintenance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
217
7-8
Replacing the Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
218
Appendices
A
Bus Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
219
B
Slave Diagnostics Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
223
C
I/O Data Conversions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
233
D
Configurator Error and Warning Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
237
E
Memory Card Backup Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
243
F
Application Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
245
G
C200HW-PRM21 Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
247
Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255
Revision History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
viii
About this Manual
This manual describes the CS1W-PRM21 and CJ1W-PRM21 PROFIBUS DP and PROFIBUS DP-V1
Master Units. The Unit version number on the side case of the housing indicates supported functionality. If no version number is shown, the version number is 1.0. The following table lists the functions
supported per version number.
Unit name
CJ1W-PRM21
CS1W-PRM21
Unit Version
Supporting
DTM version
Functions supported
1.0
0.1.0.1
V2.xx
PROFIBUS DP (Class 1) Master
2.0
V2.xx
PROFIBUS DP (Class 1) Master
PROFIBUS DP-V1 (Class 1) Master
Additional PROFIBUS DP acyclic services
Unit version 2.0 includes the same functions as Unit version 1.0, in addition to new PROFIBUS DP-V1
related functions. Unit version 2.0 will eventually replace Unit version 1.0.
Note
Unless stated otherwise, specifications, descriptions and images in this manual apply to both
Unit versions of the CS1W-PRM21 and CJ1W-PRM21 Units. The indication PROFIBUS Master Unit(s) will be used when referring to both unit types.
This manual describes how to install and operate the CS1W-PRM21 and CJ1W-PRM21 Units. Both
Units serve the same purpose: enable devices of various manufacturers to intercommunicate without
making any special interface adaptations. They are technically the same; they differ only in their physical dimensions and weight and the way they are connected to the backplane.
This manual also describes - to a lesser extent - how to configure the C200HW-PRM21 PROFIBUS
DP Master Unit using the CX-Profibus Configurator. For more information on the C200HW-PRM21
PROFIBUS DP Master Unit, refer to the C200H-series PROFIBUS DP Master Units Operation Manual
([email protected]).
Please read this manual carefully so that you understand the information provided before installing or
using the PROFIBUS Master Unit. Start with the precautions in the following section. They describe
the operating environment and application safety measures which must be observed prior to and when
using the PROFIBUS Master Unit.
The sections of this manual are as follows:
Section 1 introduces the PROFIBUS Master Units and CX-Profibus.
Section 2 describes the installation and setup of the PROFIBUS Master Units.
Section 3 describes the installation of CX-Profibus and provides a overview.
Section 4 describes how the Units interface to the PLC CPU.
Section 5 describes the FINS commands supported by the PROFIBUS Master Units.
Section 6 describes the operational aspects of the PROFIBUS Master Units.
Section 7 provides procedures for troubleshooting the PROFIBUS network and the Units.
The Appendices contain information supplementary to the information in the main body of the manual. They are referred to in the various sections as required.
ix
Contents
Cat. No.
CS-series
Programmable Controllers
Operation Manual
Manual
SYSMAC CS-series
CS1G/[email protected]@-E
Products
Describes the installation and operation of
the CS-series PLCs.
[email protected]
CJ-series
Programmable controllers
operation Manual
SYSMAC CJ-series
[email protected]@
Describes the installation and operation of
the CJ-series PLCs.
[email protected]
CS/CJ-series
Programmable Controllers
Programming Manual
SYSMAC CS/CJ-series
CS1G/[email protected]@-E, [email protected]@
Describes the ladder diagram programming [email protected]
instructions supported by CS/CJ-series
PLCs.
CS/CJ-series
Programmable Controllers
Instructions Reference Manual
SYSMAC CS/CJ-series
CS1G/[email protected]@-E, [email protected]@
Describes the ladder diagram programming [email protected]
instructions supported by CS-series and
CJ-series PLCs.
CS/CJ Series Communication
Commands Reference Manual
SYSMAC CS1G/[email protected]@- Describes the C-series (Host Link) and
E CPU Units
FINS communications commands used
with CS/CJ-series PLCs.
CX-Programmer
Operation Manual
SYSMAC [email protected]@-E
CX-Programmer
Provides information on how to use the CX- [email protected]
Programmer, programming software which
supports CS1/CJ1-series PLCs.
CX-Server
Run Time User Manual
CX-Server
Provides information on how to use the CX- [email protected]
Server communication driver software
which supports CS1/CJ1-series PLCs.
C200H-series PROFIBUS DP
Master Units
Operation Manual
SYSMAC C200H-series
C200HW-PRM21
Describes the Installation and Operation of [email protected]
the C200HW-PRM21 PROFIBUS DP Master Units.
CJ-series PROFIBUS DP
Slave unit
Operation Manual
SYSMAC CJ1-series
CJ1W-PRT21
Describes the Installation and Operation of [email protected]
the CJ1W-PRT21 PROFIBUS DP Slave
Units.
GT1-series PROFIBUS DP
Multiple I/O Terminal
Operation Manual
PRT1-COM & GT1-series
Describes the Installation and Operation of [email protected]
the PROFIBUS DP PRT1-COM and GT1series I/O Units.
C200H-series PROFIBUS DP
Slave unit
Operation Manual
Describes the Installation and Operation of [email protected]
SYSMAC C200H-series
C200HW-PRT21 PROFIBUS the C200HW-PRT21 PROFIBUS DP Slave
Units.
DP Slave unit
F150-series PROFIBUS DP
Vision Sensor
Operation Manual
F150-C15E-3-PRT21
PROFIBUS DP Vision Sensor
CS/CJ-series Ethernet Units
Operation Manual
SYSMAC CS/CJ-series
Describes the installation and operation of
CS1W-ETN01/ETN11
the CS1W-ETN01 (10Base-5), CS1WCJ1W-ETN11 Ethernet Units ETN11 (10Base-T), and CJ1W-ETN11
Ethernet Units.
[email protected]
Describes the Installation and Operation of [email protected]
the F150 PROFIBUS Vision Sensor.
[email protected]
CS/CJ-series Serial Communi- SYSMAC CS/CJ-series
cations Boards and Serial
CS1W-SCB21/41, CS1WCommunications Units
SCU21, CJ1W-CSU41
Operation Manual
Describes the use of Serial Communications Units and Boards to perform serial
communications with external devices.
CS/CJ1-series Devicenet Units SYSMAC CS/CJ1-series
Operation Manual
CS1W-DRM21/CJ1WDRM21
Describes the Installation and Operation of [email protected]
the CS1W-DRM21/CJ1W-DRM21
Devicenet units.
x
[email protected]
!WARNING Failure to read and understand the information provided in this manual may result in personal injury or death, damage to the product, or product failure. Please read each section
in its entirety and be sure you understand the information provided in the section and
related sections before attempting any of the procedures or operations given.
xi
xii
PRECAUTIONS
This section provides general precautions for using the PROFIBUS Master Units, Programmable Controllers and related
devices.
The information contained in this section is important for the safe and reliable operation of the PROFIBUS Master
Units. You must read this section and understand the information contained before attempting to set up or operate
a PROFIBUS Master Unit and PLC system.
1
2
3
4
5
6
Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
General Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Safety Precautions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Operating Environment Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Application Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Conformance to EC Directives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-1
Applicable Directives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-2
Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-3
Conformance to EC Directives . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xiv
xiv
xiv
xv
xvi
xviii
xviii
xviii
xviii
xiii
Intended Audience
1
1
Intended Audience
This manual is intended for the following personnel, who must also have a
knowledge of electrical systems (an electrical engineer or the equivalent).
• Personnel in charge of installing FA systems.
• Personnel in charge of designing FA systems.
• Personnel in charge of managing FA systems and facilities.
2
General Precautions
The user must operate the product according to the performance specifications described in the operation manuals.
Before using the product under conditions which are not described in the
manual or applying the product to nuclear control systems, railroad systems,
aviation systems, vehicles, combustion systems, medical equipment, amusement machines, safety equipment, and other systems, machines, and equipment that may have a serious influence on lives and property if used
improperly, consult your OMRON representative.
Make sure that the ratings and performance characteristics of the product are
sufficient for the systems, machines, and equipment, and be sure to provide
the systems, machines, and equipment with double safety mechanisms.
This manual provides information for programming and operating OMRON
PROFIBUS Master Units. Be sure to read this manual before attempting to
use the Unit and keep this manual close at hand for reference during operation.
!WARNING It is extremely important that all PLC Units be used for their specified purposes and under the specified conditions, especially in applications that can
directly or indirectly affect human life. You must consult your OMRON representative before using a PLC System in the above-mentioned applications.
3
Safety Precautions
!WARNING Do not attempt to take any Unit apart while the power is being supplied. Doing
so may result in electric shock.
!WARNING Never touch any of the terminals while power is being supplied. Doing so may
result in serious electrical shock or electrocution.
!WARNING Do not attempt to disassemble, repair, or modify any Units. Any attempt to do
so may result in malfunction, fire, or electric shock.
!WARNING Do not touch the Power Supply Unit while power is being supplied or immediately after power has been turned OFF. Doing so may result in electric shock.
!Caution Tighten the screws on the terminal block of the AC Power Supply Unit to the
torque specified in the operation manual. Loose screws may result in burning
or malfunction.
xiv
Operating Environment Precautions
4
!WARNING The CPU Unit refreshes I/O even when the program is stopped (i.e., even in
PROGRAM mode). Confirm safety thoroughly in advance before changing the
status of any part of memory allocated to I/O Units, Special I/O Units, or CPU
Bus Units. Any changes to the data allocated to any Unit may result in unexpected operation of the loads connected to the Unit. Any of the following operation may result in changes to memory status.
• Transferring I/O memory data to the CPU Unit from a Programming
Device.
• Changing present values in memory from a Programming Device.
• Force-setting/-resetting bits from a Programming Device.
• Transferring I/O memory files from a Memory Card or EM file memory to
the CPU Unit.
• Transferring I/O memory from a host computer or from another PC on a
network.
!WARNING Execute online edits only after confirming that no adverse effects will be
caused by extending the cycle time. Otherwise, the input signals may not be
readable.
4
Operating Environment Precautions
!Caution Do not operate the Unit in the following places:
• Locations subject to direct sunlight.
• Locations subject to temperatures or humidities outside the range specified in the specifications.
• Locations subject to condensation as the result of severe changes in temperature.
• Locations subject to corrosive or flammable gases.
• Locations subject to dust (especially iron dust) or salt.
• Locations subject to exposure to water, oil, or chemicals.
• Locations subject to shock or vibration.
Provide proper shielding when installing in the following locations:
• Locations subject to static electricity or other sources of noise.
• Locations subject to strong electromagnetic fields.
• Locations subject to possible exposure to radiation.
• Locations near to power supply lines.
!Caution The operating environment of the PLC system can have a large effect on the
longevity and reliability of the system. Unsuitable operating environments can
lead to malfunction, failure and other unforeseeable problems with the PLC
system. Ensure that the operating environment is within the specified conditions at installation time and remains that way during the life of the system.
Follow all installation instructions and precautions provided in the operation
manuals.
xv
Application Precautions
5
5
Application Precautions
Observe the following precautions when using the PROFIBUS Master Unit.
!WARNING Failure to abide by the following precautions could lead to serious or possibly
fatal injury. Always heed these precautions.
• Always connect to a class-3 ground (100
Units.
Ω or less) when installing the
!Caution Failure to abide by the following precautions could lead to faulty operation or
the PLC or the system or could damage the PLC or PLC Units. Always heed
these precautions.
• Install double safety mechanisms to ensure safety against incorrect signals that may be produced by broken signal lines or momentary power
interruptions.
• When adding a new device to the network, make sure that the baud rate
is the same as other nodes.
• When adding a new slave device to the network, make sure that the
PROFIBUS Master Unit is in the OFFLINE state, to prevent unexpected
results when starting up the slave device.
• Use specified communications cables.
• Do not extend connection distances beyond the ranges given in the specifications.
• Always turn OFF the power supply to the personal computer, Slaves, and
Communications Units before attempting any of the following.
• Mounting or dismounting the PROFIBUS Master Unit, Power Supply
Units, I/O Units, CPU Units, or any other Units.
• Assembling a Unit.
• Setting DIP switches or rotary switches.
• Connecting or wiring the cables.
• Connecting or disconnecting connectors.
• Be sure that the terminal blocks, connectors, Memory Units, expansion
cables, and other items with locking devices are properly locked into
place. Improper locking may result in malfunction.
• Be sure that all the mounting screws, terminal screws, Unit mounting
screws, and cable connector screws are tightened to the torque specified
in the relevant manuals. Incorrect tightening torque may result in malfunction.
• Leave the label attached to the Unit when wiring. Removing the label may
result in malfunction if foreign matter enters the Unit.
• Remove the label after the completion of wiring to ensure proper heat dissipation. Leaving the label attached may result in malfunction.
• Always use the power supply voltage specified in this manual.
• Double-check all the wiring and connection of terminal blocks and connectors before mounting the Units.
• Use crimp terminals for wiring. Do not connect bare stranded wires
directly to terminals.
xvi
Application Precautions
5
• Observe the following precautions when wiring the communications
cable.
• Separate the communications cables from the power lines or high-tension lines.
• Do not bend the communications cables.
• Do not pull on the communications cables.
• Do not place heavy objects on top of the communications cables.
• Be sure to wire communications cable inside ducts.
• Use appropriate communications cables.
• Take appropriate measures to ensure that the specified power with the
rated voltage and frequency is supplied in places where the power supply
is unstable. An incorrect power supply may result in malfunction.
• Install external breakers and take other safety measures against short-circuits in external wiring. Insufficient safety measures against short-circuits
may result in burning.
• Double-check all the wiring and switch settings before turning ON the
power supply.
• Check the user program for proper execution before actually running it on
the Unit. Not checking the program may result in an unexpected operation.
• Confirm that no adverse effect will occur in the system before attempting
any of the following. Not doing so may result in an unexpected operation.
• Changing the operating mode of the PC.
• Force-setting/force-resetting any bit in memory.
• Changing the present value of any word or any set value in memory.
• After replacing Units, resume operation only after transferring to the new
CPU Unit and/or Special I/O Units the contents of the DM Area, HR Area,
and other data required for resuming operation. Not doing so may result
in an unexpected operation.
• When transporting or storing the product, cover the PCBs with electrically
conductive materials to prevent LSIs and ICs from being damaged by
static electricity, and also keep the product within the specified storage
temperature range.
• When transporting the Unit, use special packing boxes and protect it from
being exposed to excessive vibration or impacts during transportation.
• Do not attempt to disassemble, repair, or modify any Units.
• Do not attempt to remove the cover over the non-used connector hole on
the front of the CS1W-PRM21 Unit.
xvii
Conformance to EC Directives
6
6
Conformance to EC Directives
6-1
Applicable Directives
• EMC Directives
• Low voltage directive EN 61131-2:1994+A12:2000
6-2
Concepts
EMC Directives
OMRON Units complying with EC Directives also conform to related EMC
standards making them easier to incorporate in other Units or machines. The
actual products have been checked for conformity to EMC standards. (See
the following note.) Whether the products conform to the standards in the system used by the customer, however, must be checked by the customer.
EMC-related performance of OMRON Units complying with EC Directives will
vary depending on the configuration, wiring, and other conditions of the equipment or control panel in which OMRON devices are installed. The customer
must, therefore, perform final checks to confirm that units and the overall system conforms to EMC standards.
Note Applicable EMS (Electromagnetic Susceptibility) and EMI (Electromagnetic
Interference standards in the EMC (Electromagnetic Compatibility) standards
are as follows:
Unit
CS1W-PRM21
CJ1W-PRM21
6-3
EMS
EN 61000-6-2:2001
EMI
EN 61000-6-2:2001
Conformance to EC Directives
Units that meet EC directives also meet the common emission standard
(EN50081-2). The measures necessary to ensure that the standard is met will
vary with the overall configuration. You must therefore confirm that EC directives are met for the overall configuration, particularly any radiated emission
requirement (10 m).
xviii
SECTION 1
Features and Specifications
This section provides an introductory overview of PROFIBUS, its functions and how to setup and configure a network. It
also addresses the PROFIBUS Master Units and the configurator, their features and specifications.
1-1
1-2
1-3
1-4
1-5
Overview of PROFIBUS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-1-1 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-1-2 PROFIBUS Communication Protocol . . . . . . . . . . . . . . . . . . . . . . .
1-1-3 Device Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-1-4 Bus Access Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-1-5 Diagnostic functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-1-6 Protection Mechanisms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-1-7 Network Operation Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Setting up a PROFIBUS DP Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-2-1 Configuring the PROFIBUS Master . . . . . . . . . . . . . . . . . . . . . . . . .
1-2-2 FDT/DTM Technology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-2-3 GSD file Technology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PROFIBUS Master Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-3-1 PROFIBUS Master Unit Features. . . . . . . . . . . . . . . . . . . . . . . . . . .
1-3-2 Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-3-3 Comparison with Previous Model . . . . . . . . . . . . . . . . . . . . . . . . . .
CX-Profibus Configurator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-4-1 CX-Profibus Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-4-2 Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Basic Operating Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-5-1 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-5-2 Preparations for Communications . . . . . . . . . . . . . . . . . . . . . . . . . .
1-5-3 Procedures Prior to Starting Communications . . . . . . . . . . . . . . . . .
2
2
2
4
4
5
6
6
7
7
7
8
10
10
11
16
18
18
21
23
23
24
24
1
Overview of PROFIBUS
1-1
1-1-1
Section 1-1
Overview of PROFIBUS
Introduction
Standard EN50170
PROFIBUS (PROcess FIeldBUS) is an open fieldbus standard for a wide
range of applications in manufacturing, processing and building automation.
The Standard, EN 50170 (the Euronorm for field communications), to which
PROFIBUS adheres, guarantees vendor independence and transparency of
operation. It enables devices of various manufacturers to intercommunicate
without having to make any special interface adaptations.
The PROFIBUS family comprises three mutually compatible versions:
PROFIBUS FMS, PROFIBUS DP and PROFIBUS PA.
PROFIBUS FMS
FMS means Fieldbus Message Specification. This version is the general-purpose solution for high-level extensive and complex communication tasks.
Powerful services open up a wide range of applications and provide great
flexibility.
PROFIBUS DP
DP means Decentralized Periphery. PROFIBUS DP is optimized for high
speed and low-cost interfacing. It is specially designed for communication
between automation control systems and distributed I/O at the device level.
PROFIBUS PA
PA means Process Automation. It permits sensors and actuators to be connected to one common bus even in areas where intrinsically safe products are
required. It also permits data and power to be supplied over the bus using
2-wire technology according the international standard IEC 1158-2.
Uniform Bus Access
Protocol
PROFIBUS DP and PROFIBUS FMS use the same transmission technology
and uniform bus access protocol. Consequently, both versions can be operated simultaneously on the same bus. FMS field devices, however, cannot be
controlled by DP masters and vice versa.
!Caution It is not possible to exchange one of these family members by another family
member. This will cause faulty operation.
The rest of this section describes the PROFIBUS DP Protocol architecture.
1-1-2
PROFIBUS Communication Protocol
OSI reference model
ISO-7498
In general, the PROFIBUS communication protocol is based on the Open
System Interconnection (OSI) reference model in accordance with the international standard ISO-7498 (see the following illustration). The model defines
7 layers of communication functions, three of which - layers 1, 2, and 7 - are
used in PROFIBUS.
• Layer 1, the Physical Layer of this model, defines the physical transmission characteristics.
• Layer 2, the Data Link Layer of this model, defines the bus access protocol. This protocol also includes data security and the handling of transmission protocols and telegrams.
• Layer 7, the Application Layer of this model, defines the application functions. This Layer is only applicable to PROFIBUS FMS.
2
Overview of PROFIBUS
Section 1-1
.
DP-Profiles
DP-Extensions
User Interface Layer
DP Basic Functions
(7) Application Layer
(6) Presentation Layer
(5) Session Layer
NOT DEFINED
(4) Transport Layer
(3) Network Layer
(2) Data Link Layer
Fieldbus Data Link (FDL)
(1) Physical Layer
RS485 / Fibre Optics
PROFIBUS DP
In the rest of this manual, only PROFIBUS DP is considered.
OSI Layer 1, 2 and User
Interface
PROFIBUS DP uses layers 1 and 2, and the user interface. Layers 3 to 7 are
not defined for PROFIBUS DP. The user interface Layer defines the interface
functions for specific application areas, i.e. the PROFIBUS DP basic functions
and communication profiles.This streamlined architecture ensures fast and
efficient data transmission. The application functions which are available to
the user, as well as the system and device behaviour of the various PROFIBUS DP device types, are specified in the user interface.
OSI Layer 1: Transmission
Medium
RS-485 transmission technology or fibre optics are available for transmission.
RS-485 transmission is the most frequently used transmission technology. Its
application area includes all areas in which high transmission speed and simple inexpensive installation are required. PROFIBUS modules are interconnected by single twisted-pair shielded copper wires.
RS-485 Technology
The RS-485 transmission technology is very easy to handle. Installation of the
twisted pair cable does not require expert knowledge. The bus structure permits addition and removal of devices or step-by-step commissioning of the
system without influencing the other devices. Later expansions have no effect
on devices which are already in operation.
RS-485 Transmission
Speed
Transmission speeds between 9.6 kbit/s and 12 Mbit/s can be selected as
shown in the table below. One unique transmission speed must selected for
all devices on the bus when the system is commissioned.
Cable length
Baud rate (kbit/s)
Distance / segment (m)
9.6
1200
19.2
1200
45.45
1200
93.75
1200
187.5
1000
500
400
1500
200
3000
100
6000
100
12000
100
The maximum cable length values depend on the transmission speed and are
based on type-A cable (see Cable Type on page 37). The length can be
increased by the use of repeaters.However, it is not recommended to use
more than three repeaters in series in a PROFIBUS network.
3
Overview of PROFIBUS
1-1-3
Section 1-1
Device Types
PROFIBUS distinguishes between master devices and slave devices.
Master Devices
Master devices determine the data communication on the bus. A Master can
send messages without an external request, as long as it holds the bus
access right (the token). Masters are also referred to as active devices in the
PROFIBUS standard.
There are two types of master devices:
Class 1 Master (DPM1)
A PROFIBUS DP Class 1 Master (DPM1) device is a central controller, which
exchanges information with the decentralized devices (i.e. DP slaves) within a
specified message cycle.
Class 2 Master (DPM2)
PROFIBUS DP class 2 Master (DPM2) devices are programmers, configuration devices or operator panels. They are used during commissioning, for configuration of the DP system, or for operation and monitoring purposes.
The CS1W-PRM21 and the CJ1W-PRM21 are both PROFIBUS DP Class 1
Master devices.
Slave Devices
Slave devices are peripheral devices. Typical slave devices include input/output devices, valves, drives, and measuring transmitters. They do not have bus
access rights and they can only acknowledge received messages or send
messages to the master when requested to do so. Slave devices are also
called passive devices
Device Profile
To enable the exchange of devices from different vendors, the user data has
to have the same format. The PROFIBUS DP protocol does not define the format of user data, it is only responsible for the transmission of this data. The
format of user data may be defined in so called profiles. Profiles can reduce
engineering costs since the meaning of application-related parameters is
specified precisely. Profiles have been defined for specific areas like drive
technology, encoders, and for sensors / actuators.
PROFIBUS DP-V1
PROFIBUS DP-V1 is an extension to the PROFIBUS DP protocol standard. It
defines acyclic message services between a PROFIBUS DP-V1 Master and a
PROFIBUS DP-V1 slave device. These acyclic message services allow
exchange of extended parameter settings as well as extended diagnostics
and alarm information, during regular I/O data exchange. PROFIBUS DP-V1
devices must at least support PROFIBUS DP.
PROFIBUS DP-V1 services are designated as MSACn services (MasterSlave Acyclic, Class n), in which n designates the Master Class (i.e. 1 or 2).
The CS1W-PRM21 and the CJ1W-PRM21 both support PROFIBUS DP-V1
Class 1 Master functions as of Unit version 2.0.
1-1-4
Bus Access Protocol
OSI Layer 2: Bus Access
Protocol
The PROFIBUS bus access protocol is implemented by OSI layer 2. This protocol also includes data security and the handling of the transmission protocols and messages.
Medium Access Control
The Medium Access Control (MAC) specifies the procedures which determine
when a device is permitted to transmit data. A token passing procedure is
used to handle the bus access between master devices, and a polling procedure is used to handle the communication between a master device and its
assigned slave device(s).
4
Overview of PROFIBUS
Section 1-1
Token Passing
The token passing procedure guarantees that the bus access right (the token)
is assigned to each master within a precisely defined time frame. The token
message, a special message for passing access rights from one master to the
next master, must be passed around the logical token ring - once to each
master - within a specified target rotation time. Each master executes this procedure automatically.
Polling Procedure
The polling or master-slave procedure permits the master, currently in possession of the token, to access its assigned slaves. The figure below shows a
possible configuration The configuration shows three active devices (masters)
and six passive devices (slaves).
Token Passing
DPM1
DPM2
DPM 1
Active stations
Master devices
Polling
PROFIBUS
Passive stations
Slave devices
The three masters form a logical token ring. When an active device receives
the token message, it can perform its master role for a certain period of time.
During this time it can communicate with all assigned slave devices in a master-slave communication relationship, and a DPM2 master can take the initiative to communicate with DPM1 master devices in a master-master
communication relationship.
Multi-peer Communication
In addition to logical peer-to-peer data transmission, PROFIBUS DP provides
multi-peer communication (broadcast and multicast).
Broadcast
Communication
In the case of broadcast communication a master device sends an unacknowledged message to all other devices (masters and slaves).
Multicast Communication
In the case of multicast communication a master device sends an unacknowledged message to a predetermined group of slave devices.
1-1-5
Diagnostic functions
Extended Diagnostics
Extended diagnostic functions defined in PROFIBUS DP enable the fast location of error at slave devices. Diagnostic messages are transmitted over the
bus and collected at the master. Three diagnostic message types are defined:
Device Related
Diagnostics
• Messages concerning the general operational status of the whole device,
e.g. over temperature, low voltage.
Module Related
Diagnostics
• Messages indicating that an error is present in a specific I/O range of a
device, e.g. an 8-bit output module.
Channel Related
Diagnostics
• Messages indicating an error at a given input or output, e.g. short circuit
on Output 5.
5
Overview of PROFIBUS
1-1-6
Section 1-1
Protection Mechanisms
Monitoring Time
PROFIBUS DP provides effective protection functions against parameterization errors or failure of the transmission equipment. Time monitoring is provided both at the master and the slave devices. The monitoring interval is
specified when the system is configured.
Monitoring at the Master
The PROFIBUS Master monitors data transmission of the slaves with the
Data-Control-Timer. A separate control timer is used for each slave. This
timer expires if response data is not correctly transmitted by the slave within
the monitoring interval. The user is informed when this happens. If the automatic error reaction (Auto-CLEAR) has been enabled, the PROFIBUS Master
exits its OPERATE state, switches the outputs of all assigned slaves to the
fail-safe status and changes to the CLEAR state.
Monitoring at the Slave
Slave devices use a watchdog to detect failures of the master or the bus. If
data communication with the master does not occur within the set watchdog
time interval, a slave automatically switches its outputs to the fail-safe mode.
Also, access protection is provided for the inputs and outputs of the slaves
operating in multi-master systems. Only authorized masters can access their
slaves.
1-1-7
Network Operation Modes
PROFIBUS DP distinguishes four different network operation modes:
OFFLINE
• Communication with all PROFIBUS DP participants (masters and slaves)
is stopped. The Master ceases to access the PROFIBUS network.
STOP
• Communication between the master and its slaves is stopped. Only communication between the master and other masters is still possible.
CLEAR
• The master tries to set parameters, check the configuration, and perform
data exchange with its associated slaves. Data exchange involves reading the inputs of the PROFIBUS DP slaves and writing zeros to the outputs of the slaves.
OPERATE
• The master exchanges data with its assigned slaves, inputs are read and
outputs are written. Also, the master cyclically sends its local status to all
its assigned PROFIBUS DP slaves (using a broadcast message).
The PROFIBUS Master Unit will always be in one of these four modes. Mode
transitions from one mode to another will be performed via intermediate
modes. For example, a mode transition from OFFLINE to OPERATE, will be
performed as OFFLINE →STOP →CLEAR →OPERATE.
Auto-CLEAR
Fail-safe State
6
If an error occurs during the data exchange phase of the master, the ‘AutoCLEAR’ function determines the subsequent actions. If this function has been
disabled, the master remains in the OPERATE mode. If the function has been
enabled, the master automatically changes the network to the CLEAR mode,
in which the outputs of the assigned PROFIBUS DP slaves are switched to
zero, i.e. the ‘fail-safe’ state. The master continues to read the inputs of the
slaves.
Setting up a PROFIBUS DP Network
1-2
1-2-1
Section 1-2
Setting up a PROFIBUS DP Network
Configuring the PROFIBUS Master
In order to operate a PROFIBUS network, each master in the network needs
to be configured. This process of configuration involves
• setting up the network topology, i.e. assigning the slave devices with
which the master will be exchanging data,
• defining the parameterization data, which the master will send to each of
the slave devices, before process data exchange can commence
• defining the configuration data, i.e. defining the process data, which will
be exchanged,
• setting up the bus parameters, which define the baud rate and the bus
timing parameters.
• downloading the configuration setup to the master device.
Configuration Technology
The configuration process is usually facilitated by a special Computer based
program, often referred to as a configurator. The configurator requires special
configuration files, defining the configuration options for each device, which is
to participate in data exchange. The files must be provided by the manufacturer of the device.
Two types of configuration technology exist:
• Configuration technology based on FDT/DTM technology
• Configuration technology based on GSD-files
1-2-2
FDT/DTM Technology
FDT/DTM Technology
The newer configuration tools are based on FDT/DTM technology.
FDT/DTM Concept
The FDT/DTM concept specifies the interfaces between the engineering systems called Field Device Tools (FDT), and the device-specific software components called Device Type Managers (DTM).
The FDT/DTM concept separates the device dependent functionality (which is
in the DTM) from the application. It provides separate interfaces for device
configuration, monitoring and maintenance solutions, which before largely
depended on the manufacturer of the application. Because of this concept,
FDT/DTM technology is not limited to PROFIBUS applications. In concept,
any type of network can be configured and accessed, provided the appropriate DTMs are available.
FDT Container Application
A FDT container application facilitates configuration of network devices and
parameterizing and/or manipulating their operational modes. All device
dependent functionality is concentrated in the DTM.
FDT container applications can be stand-alone tools, or can be part of other
engineering tools such web browsers providing FDT interfaces.Since FDT
standardizes the interfaces, it allows devices from different manufacturers to
be integrated in any automation system, regardless of the fieldbus system.
CX-Profibus is an example of a FDT container application. It is described in
detail in the following sections.
Device DTM
DTMs are provided by the manufacturer of the device. A DTM is comparable
to a printer driver, which allows interactive configuration and diagnostics.
7
Setting up a PROFIBUS DP Network
Section 1-2
The DTM provides not only the configuration, manipulation and monitoring
functions for a device including the user interface functions, it also provides
the connection technology to the device.
DTM Properties
In general, a DTM is a Microsoft COM-component, which can be executed
from within a FDT container application. A DTM is not a stand-alone tool, it
requires a FDT container application to be executed. The DTM provides a
number of interface functions, through which it can be controlled and
accessed in order to transfer data to or from the DTM.
A DTM provides all the options for configuration and monitoring of a device,
which it can present to the user through its own user interface.
ActiveX User Interface
The user interface for a DTM is provided using ActiveX windows. Control of
these windows is done by the DTM, but the FDT container application can
request specific user input from the DTM, based on which the DTM will provide the necessary ActiveX windows. In general multi-language user interface
windows, including DTM specific Help files are supported by the DTM.
XML based Data Transfer
Data transfer to and from a DTM is provided using XML-documents. The
XML-documents are standardized for the communication between the FDT
container application and for communication between DTMs.
An additional specification covers the definition of XML-data formats for the
transfer of application specific data, such as PROFIBUS data.
Communication DTM
In general, a device configuration DTM is accompanied by a communication
DTM. This specific DTM facilitates device specific communication, e.g. for
downloading a configuration to a PROFIBUS Master Unit and/or for retrieving
monitoring information from PROFIBUS Master Unit. It may incorporate the
specific communication protocol, or rely on other available drivers.
CX-Profibus
CX-Profibus is a FDT container application. Together with this container application, OMRON provides four DTMs:
• A DTM to facilitate configuration and operation of the CS1/CJ1W-PRM21
PROFIBUS DP-V1 Master Units (As of Unit version 2.0)
• A DTM to facilitate configuration of the CS1/CJ1W-PRM21 PROFIBUS
DP Master Units (Unit version 1.0)
• A DTM to facilitate configuration of the C200HW-PRM21 PROFIBUS DP
Master Unit
• A DTM to facilitate integration of GSD file based devices into CX-Profibus
(see section 1-2-3 GSD file Technology for more information)
1-2-3
GSD file Technology
GSD file Technology
The older and most commonly used configuration technology is the based on
GSD files (General Slave Data file). A GSD file is a text file, containing the
characteristic features and configuration options of a device. The device data
base file of each device is loaded in the configurator and downloaded to the
master device.
GSD files are usually supplied with a Unit, or can be downloaded from the
Internet, either from the manufacturer's site, or from the GSD library of the
PROFIBUS International at http://www.profibus.com.
8
Setting up a PROFIBUS DP Network
GSD File Language
Section 1-2
The language used in the GSD file is indicated by the last letter of the file
extension, *.GS?:
Default
= GSD
English
= GSE
German
= GSG
Italian
= GSI
Portuguese
= GSP
Spanish
= GSS
The GSD files are prepared individually by the vendor for each type of device,
according to a fixed format. Some parameters are mandatory, some have a
default value and some are optional. The device data base file is divided into
three parts:
General Section
• General specifications
This section contains the vendor name, the device name, hardware- and software release versions, device type and identification number, protocol specification and supported baud rates.
DP-master Section
• DP master-related specifications
This section contains all parameters which only apply to DP master devices
(e.g. maximum memory size for the master parameter set, maximum number
of entries in the list of active devices, or the maximum number of slaves the
master can handle).
DP-slave Section
• DP slave-related specifications
This section contains all specification related to slaves (e.g. minimum time
between two slave poll cycles, specification of the inputs and outputs, and
consistency of the I/O data).
For PROFIBUS DP-V1 devices this section also specifies what services for
PROFIBUS DP-V1 are supported.
DTM versus GSD File
When comparing the two configuration technologies, a GSD file only provides
information on the device characteristics and configuration options. It has no
GUI of its own, nor can it connect to the device itself. A GSD file always
requires a separate configurator program to interpret the data. In the FDT/
DTM concept all these device related functions are included in the DTM. The
DTM can be executed from any program, which provides FDT interfaces.
Sending PROFIBUS DP-V1 commands to a device from the configuration tool
is only possible using DTM technology. The GSD file does not provide this
means.
9
PROFIBUS Master Unit
1-3
1-3-1
Section 1-3
PROFIBUS Master Unit
PROFIBUS Master Unit Features
PROFIBUS Master Unit
The PROFIBUS Master Unit is a CPU Bus Unit, which can be installed on a
CS1/CJ1 PLC System. There are two available models of the PROFIBUS
Master Unit: the CS1W-PRM21 for connection to a CS1 PLC System and the
CJ1W-PRM21 for connection to a CJ1 PLC System. Both models provide
identical functionality.
CPU Bus Unit
A total of up to 16 CPU Bus Units can be mounted on the CPU Rack or an
Expansion Rack. The total of 16 must include all PROFIBUS Master Units
and all other CPU Bus Units
Unit Control and Status
Up to 25 words of control and status words are exchanged between the
PROFIBUS Master Unit and a dedicated CIO memory area, of which the location is related to the Unit Number. Control bits, allow the PLC program to
switch the Unit between OFFLINE, STOP, CLEAR and OPERATE mode,
which represent the main PROFIBUS DP modes of operation. The control
words also allow for user initiated transmission of a Global-Control message
over the PROFIBUS network to any group of slave devices.
The remaining CIO words provide status and diagnostics information on the
Unit itself, the PROFIBUS network and the slave devices allocated to the
PROFIBUS Master Unit.
I/O Data
The total size of I/O data however, must not exceed the maximum I/O size of
up to 7168 words, which it can exchange with the PLC memory. The I/O data
can be distributed over up to two input areas and two output areas. Each of
the input and output areas can be mapped to any location in the DM Area,
CIO Area, WR Area, HR Area, or the EM banks.
FINS Messages
The PROFIBUS Master Unit supports FINS message exchange with the PLC
CPU to allow the transfer of Slave diagnostics data, the Error log, or to enable
or disable communication with specific allocated slave devices, so that they
can temporarily be taken out of the network for maintenance, without the
PROFIBUS Master Unit reporting an error.
As of Unit version 2.0 additional FINS commands have been implemented to
allow the user to send acyclic PROFIBUS DP and PROFIBUS DP-V1 messages over the PROFIBUS network. These messages can be initiated from
the program running in the PLC CPU, and can be used to change slave
device addresses, read slave device configuration, but also to send and
receive extended parameter data information.
PROFIBUS DP Functions
The PROFIBUS Master Unit supports all mandatory services defined in the
PROFIBUS DP standard EN50170, Volume 2 for Master - Slave Communication. These functions includes the following services:
•
•
•
•
•
Set_Prm
Chk_Cfg
Slave_Diag
Data_Exchange
Global-Control (FREEZE, UNFREEZE, SYNC, UNSYNC, CLEAR)
The PROFIBUS Master Unit supports cyclic Master - Slave communications
for networks with up to 125 slave devices. With each slave device it can
exchange up to 244 bytes of input data and up to 244 bytes of output data.
For diagnostics purposes the PROFIBUS Master Unit collects all Slave Diagnostics messages, which it can transfer to the PLC memory, using FINS com-
10
PROFIBUS Master Unit
Section 1-3
mands. From every allocated slave device it can receive up to 244 bytes of
diagnostics data.
Configuration
Before the PROFIBUS Master Unit can control the PROFIBUS network, it
must be configured, using the dedicated configuration program CX-Profibus.
Without this configuration, the Unit will not be able to achieve data exchange.
The configurator is explained in section 1-4 CX-Profibus Configurator
Troubleshooting
Functions
The PROFIBUS Master Unit is provided with a variety of troubleshooting functions for prompt recovery in case of errors:
• Extensive self-diagnostic function at startup
• Data exchange flags, indicating if I/O data is being exchanged with the
slave devices
• Diagnostics flags, indicating if new Slave diagnostics data is available
• Extensive status and error flags, indicating the status of the Unit and the
PROFIBUS network
• Error log for recording error history data.
1-3-2
Specifications
The CS1W-PRM21 and CJ1W-PRM21 are remote I/O Communication units
providing PROFIBUS DP and PROFIBUS DP-V1 Master capabilities. The
Unit version number on the side case of the housing indicates supported functionality. If no version number is shown, the version number is 1.0. The following table lists the functions supported per version number.
PROFIBUS Master Unit Model
Applicable
PLC
CS Series
CJ Series
Unit
classification
CPU Bus Unit
CPU Bus Unit
Note
Model name
CS1W-PRM21
CJ1W-PRM21
Unit Version
Supporting
DTM version
Functions supported
1.0
0.1.0.1
V1.xx
PROFIBUS DP (Class 1) Master
2.0
V2.xx
PROFIBUS DP (Class 1) Master
PROFIBUS DP-V1 (Class 1) Master
1.0
0.1.0.1
V1.xx
PROFIBUS DP (Class 1) Master
2.0
V2.xx
PROFIBUS DP (Class 1) Master
PROFIBUS DP-V1 (Class 1) Master
1. Unit version 2.0 includes the same functions as Unit version 1.0, in addition
to new PROFIBUS DP-V1 related functions, and is backward compatible
with Unit version 1.0. Unit version 2.0 will eventually replace Unit version
1.0.
2. DTM version 1.xx provides a minor update to version 0.1.0.1. Version 1.xx
does not provide the PROFIBUS DP-V1 functions.
3. Unless stated otherwise, specifications, descriptions and images in this
manual apply to both Unit versions of the CS1W-PRM21 and CJ1WPRM21 Units. The indication PROFIBUS Master Unit(s) will be used when
referring to both unit types.
General Specifications
General specifications of the CS/CJ-series PROFIBUS Master Units conform
to the general specifications for the SYSMAC CS/CJ-series CPU Units.
11
PROFIBUS Master Unit
Section 1-3
Functional Specifications
Item
Front case
Environment
Installation
PROFIBUS Master Unit types
Specification
CS1W-PRM21
CJ1W-PRM21
Applicable PLC series
CS-series
CJ-series
Mounting position
• CPU Rack,
• CPU Rack,
• CS Expansion Rack (Excluding • CJ1 Expansion Rack
a C200H Expansion I/O Rack or
SYSMAC BUS Slave Rack.)
• CS1D Duplex
Unit classification
CPU Bus Unit
Applicable unit numbers
0 to F (Hex)
Maximum number of Units per PLC
16
Current consumption
400 mA max at 5 Vdc
Dimensions (W x H x D)
35 x 130 x 101 mm
31 x 90 x 65 mm
Weight
187g (typical)
100g (typical)
Ambient temperatures
Operating temperature: 0 to 55° C
Storage temperature: –20 to 75° C
Ambient operating humidity
10% to 90% (with no condensation)
Vibration resistance
Conforms to IEC60068-2-6, test Fc.
10 to 54.8Hz, 0.25-mm amplitude, 54.8 to 300Hz, acceleration:
29.4 m/s2 in X, Y, and Z directions for 120 minutes each.
(Total time: 12 linear sweeps x 10 minutes / sweep = 120 minutes)
Shock resistance
Conforms to IEC60068-2-27, test Ea.
196 m/s2 three times each in X, Y, and Z directions
Dielectric strength
600 VAC (between isolated circuits)
Conformance to EMC and Electrical
safety standards
EN61000-6-2: 2001
EN61000-6-4: 2001/CISPR11
EN61131-2:1994+a12:2000
Settings
Unit Number rotary switch, range: 0 ~ F (Hex)
Indicators
7 LEDs, indicating Unit status and PROFIBUS status:
Unit status:
RUN (Green LED)
ERC (Red LED)
Host PLC status:
ERH (Red LED)
Configuration status:
PRM (Green LED)
PROFIBUS status:
BST (Green LED)
COMM (Green LED)
BF (Red LED)
PROFIBUS Connector
9-pin sub-D female connector (#4/40 UNC thread)
CIO Area words allocated for the CPU
Bus Unit
Fixed allocation of 25 words per Unit.
CIO 1500 + (25 x Unit number)
Memory area allocation
CIO words provide:
• 2 words for software switches
• 1 word for the Global-Control
• 21 words for the Unit and Slave statuses
12
DM Area words allocated for the CPU
Bus Unit.
Fixed allocation of 100 words per Unit.
DM 30000 + (100 x Unit number)
DM Area allocated to the Unit is reserved for future use.
I/O Data allocations
Maximum total size: 7168 words
I/O Data words can be allocated to up to 2 input areas and 2 output
areas.
Input areas and output areas can be mapped to CIO, DM, WR, and HR
Areas, as well as EM banks.
Mapping must be defined through configurator
PROFIBUS Master Unit
Section 1-3
Error log FINS messaging
Item
Specification
Reading slave device diagnostics
The MEMORY AREA READ (0101) FINS command can be used to
obtain the last received Slave Diagnostics message.
Reading and controlling the error log
Catalogues the history of error events. The Unit supports the following
Error Log related FINS commands:
• ERROR LOG READ
• ERROR LOG CLEAR
Device state changes
Allocated slave devices can be disabled and enabled in order to temporarily remove them from data exchange services. The internal error log
records the history of error events. The Unit supports the following
FINS commands to implement this:
• RUN
• STOP
PROFIBUS DP messages
(See Note)
The PROFIBUS MESSAGE SEND (2809) can be used to send PROFIBUS DP and PROFIBUS DP-V1 messages over the PROFIBUS network from the CS1/CJ1 PLC CPU.The following services can be
initiate, using this FINS command:
PROFIBUS DP services:
• Get_Cfg
• Set_Slave_Add
• Rd_Inp
• Rd_Outp
PROFIBUS DP-V1 services:
• MSAC1 - Read
• MSAC1 - Write
Error history size and storage
The PROFIBUS Master Unit supports storage of up to 80 error events,
including time stamps in volatile memory.
16 error events can be logged in non-volatile memory
Protocol Specification
Item
EN50170, Volume 2
Protocol type supported
PROFIBUS DP, PROFIBUS DP-V1
PROFIBUS Unit types
PROFIBUS DP-V1 Class 1 Master
PROFIBUS Media type
RS-485, galvanically isolated from the PLC
PROFIBUS Connector
9-pin sub-D female connector (#4/40 UNC thread)
Termination according to EN50170 provided by the cable connector
Unit device address range
0 ~ 125, set through the configurator
125 max, address range 0 ~ 125
Number of slave devices supported
PROFIBUS interface
Specification
Applicable standards
baud rates supported
Selectable through the configurator:
• 9.6 kbit/s
• 19.2 kbit/s
• 45.45 kbit/s
• 93.75 kbit/s
• 187 kbit/s
• 500 kbit/s
• 1.5 Mbit/s
• 3 Mbit/s
• 6 Mbit/s
• 12 Mbit/s
Bus timing definitions
Calculated by the configurator
13
PROFIBUS Master Unit
Section 1-3
PROFIBUS Services
Item
Specification
PROFIBUS DP Master Class 1 - Slave
cyclic services
•
•
•
•
•
Set_Prm
Chk_Cfg
Data_Exchange
Slave_Diag
Global-Control - CLEAR
PROFIBUS DP Master Class 1 - Slave
acyclic services available to the PLC
Acyclic message services, initiated through FINS. Can be addresses to
one slave device at a time (See Note).
Supported PROFIBUS DP services:
• Get_Cfg
• Set_Slave_Add
• Rd_Inp
• Rd_Outp
Global-Control, initiated from CIO Word.
Can be addressed to all or a specified group of slave devices.
Supported commands:
• SYNC
• UNSYNC
• FREEZE
• UNFREEZE
PROFIBUS DP Master - Master services Not supported
PROFIBUS DP-V1 Master Class1 Slave acyclic message services (See
Note)
MSAC1 - Read
MSAC1 - Write
Number of I/O module definitions
4000 max. over all configured slave devices
I/O Data
Number of I/O data supported by Master Up to 244 bytes input and 244 bytes output max. per slave device
(defined by slave device)
Total sum of all I/O Data must not exceed 7168 words
Number of diagnostics data supported
by Master
Up to 244 bytes of diagnostics max. per slave device
Diagnostic data is collected at the Unit, and can be obtained from the
Unit using FINS messaging
Note These functions are implemented as of CS1/CJ1W-PRM21, Unit version 2.0
14
PROFIBUS Master Unit
Section 1-3
External Dimensions
CS1W-PRM21
3
35
PRM21
101
CS
RUN
ERH ERC
PRM BST
COMM BF
ISOM
RUN
ERC
BST
BF
6543
DCB
UNIT
No. 210FE
A987
94
130
BUS
25
11
(UNIT: mm)
CJ1W-PRM21
31
PRM21
RUN
3
ERC
PRM COMM
ERH
BST
65
BF
01
EF 2
789A
3456
UNIT
NO.
BCD
54
90
BUS
25
11
(UNIT: mm)
15
PROFIBUS Master Unit
1-3-3
Section 1-3
Comparison with Previous Model
The following table provides a comparison between the CS1W-PRM21/
CJ1W-PRM21 PROFIBUS DP-V1 Master Units and their predecessor, the
PROFIBUS DP Master used in a CS-series PLC
Item
C200HW-PRM21
CS1/CJ1W-PRM21 (Unit version 2.0)
Unit classification
C200H Special I/O Unit
CPU Bus Unit
Mounting position
•
•
•
•
• CPU Rack,
• CS/CJ-series Expansion Rack
• CS1W-PRM21 can be mounted on CS1D
CPU Rack,
C200H I/O Expansion Rack,
CS-series Expansion Rack
Can not be mounted on a CS1D PLC
Applicable Unit numbers
0 to F (Hex)
0 to F (Hex)
Maximum number of Units
per PLC
16
16
Allocated CIO Area words
2,000 to 2,004 + (10 x unit number)
1,500 to 1,524 + (25 x unit number)
Up to 4 CIO words contain:
Up to 25 CIO words contain:
• Command settings
• Command settings
• Unit Status and error flags
• Unit Status and error flags
• Error reporting from the PROFIBUS inter- • PROFIBUS status and error flags
face
• Slave status flags
Allocated DM Area words
D20000 to D20017 + (100 x unit number)
D30000 to D30099 + (100 x unit number)
The area contains user defined memory
Not used on the Unit. Reserved for future
mapping of I/O data
use
At start up this area is transferred to the Unit
I/O Data allocations
Maximum total size: 300 words per Unit
I/O Data words can be allocated to up to 2
input areas and 2 output areas
I/O size per area: up to 200 words
Mapping / area size set in DM words:
• CIO: CIO 0000 to CIO 0235
• CIO: CIO 0300 to CIO 0511
• CIO: CIO 1000 to CIO 1063
• HR: HR000 to HR099
• DM: D00000 to D05999
Default mapping (DM words contain 0000):
• Output area: CIO 0050 to CIO 0099
• Input area: CIO 0350 to CIO 0399
• Diagnostic flags: CIO 0200 to CIO 0215
Message communications
Message communication using IOWR and
IORD PLC instructions:
• IOWR to send Global-Control command
• IORD to read slave diagnostics
FINS message communication not supported
16
Maximum total size: 7168 words per Unit
I/O Data words can be allocated to up to 2
input areas and 2 output areas
I/O size per area: up to 7168 words
Mapping and area size set by the configurator:
• CIO: CIO 0000 to CIO 6143
• WR: W000 to W511
• HR: HR000 to HR511
• DM: D00000 to D32767
• EM: E00000 to E32767 (Banks 0 to C)
Default mapping: Not supported
Note Diagnostics flags: available in allocated CIO Area words
FINS message communication. Commands
supported:
• MEMORY AREA READ to read slave
device diagnostics message
• ERROR LOG READ, to read the Unit’s
error log
• ERROR LOG CLEAR to clear the Unit’s
error log
• RUN to enable communication with a
slave device
• STOP to disable communication with a
slave device
• PROFIBUS MESSAGE SEND to send
messages over PROFIBUS network (See
Note).
PROFIBUS Master Unit
Section 1-3
Item
Configuration connection
method
C200HW-PRM21
Serial connection (RS232) directly to connector on the front of the Unit
CS1/CJ1W-PRM21 (Unit version 2.0)
Serial connection directly via PLC CPU, or
via other I/O Units.
No separate connector on the front of the
Unit
PROFIBUS Media type
RS-485, galvanically isolated from the PLC
RS-485, galvanically isolated from the PLC
PROFIBUS Connector
9-pin sub-D female connector (#4/40 UNC
thread)
Termination provided through a switch on
the unit according to EN50170
9-pin sub-D female connector (#4/40 UNC
thread)
Termination must be provided by the cable
connector according to EN50170
Unit device address range
0 ~ 125, set through the configurator
125 max, address range 0 ~ 125
0 ~ 125, set through the configurator
125 max, address range 0 ~ 125
baud rates supported
Selectable through the configurator:
• 9.6 kbit/s
• 19.2 kbit/s
• 93.75 kbit/s
• 187 kbit/s
• 500 kbit/s
• 1.5 Mbit/s
• 3 Mbit/s
• 6 Mbit/s
• 12 Mbit/s
Selectable through the configurator:
• 9.6 kbit/s
• 19.2 kbit/s
• 45.45 kbit/s
• 93.75 kbit/s
• 187 kbit/s
• 500 kbit/s
• 1.5 Mbit/s
• 3 Mbit/s
• 6 Mbit/s
• 12 Mbit/s
Bus timing definitions
Calculated by the configurator
Number of slave devices
supported on the network
Calculated by the configurator
Master Class 1 - Slave cyclic • Set_Prm
services
• Chk_Cfg
• Data_Exchange
• Slave_Diag
• Global-Control - CLEAR
•
•
•
•
•
Master Class 1 - Slave acyclic services
•
•
•
•
• Get_Cfg
• Set_Slave_Add
• Rd_Inp
• Rd_Outp
(See Note)
Master Class 1 - Slave services available to the PLC
Global-Control, initiated from CIO Word:
Can be addressed to one or all slave
devices or a specified group of slaves
devices Supported commands:
• SYNC
• UNSYNC
• FREEZE
• UNFREEZE
• CLEAR
Global-Control, initiated from CIO Word:
Can be addressed to all slave devices or a
specified group of slaves devices
Supported commands:
• SYNC
• UNSYNC
• FREEZE
• UNFREEZE
Master - Master services
Not supported
Not supported
PROFIBUS DP-V1 Master
Class 1 - Slave services
Not supported
MSAC1 - Read
MSAC1 - Write
Error reporting
Error numbers are transferred to CIO word
Internal logging not supported
80 error events can be logged in volatile
memory.
16 error events can be logged in non-volatile
memory
Errors can be retrieved through FINS messages
Get_Cfg
Set_Slave_Add
Rd_Inp
Rd_Outp
Set_Prm
Chk_Cfg
Data_Exchange
Slave_Diag
Global-Control - CLEAR
Note These functions are implemented as of CS1/CJ1W-PRM21, Unit version 2.0
17
CX-Profibus Configurator
1-4
1-4-1
Section 1-4
CX-Profibus Configurator
CX-Profibus Features
CX-Profibus
The PROFIBUS Master Unit requires a configuration before it can exchange
I/O data with the slave devices. For this purpose OMRON provides the CXProfibus Configuration program, which runs under Microsoft Windows™ NT
4.0, Windows™ 2000 or Windows™ XP
Together with CX-Profibus, OMRON provides four DTM COM Objects:
•
•
•
•
A DTM to configure the CS1/CJ1W-PRM21 PROFIBUS DP-V1 Master
A DTM to configure the CS1/CJ1W-PRM21 PROFIBUS DP Master
A DTM to configure the C200HW-PRM21 PROFIBUS DP Master
A DTM to allow the handling of classic GSD files in CX-Profibus
The following provides a quick overview of the functions.
CX-Profibus FDT
Container Application
CX-Profibus provides an FDT environment in which DTMs can be executed.
The main function of CX-Profibus is to facilitate the DTMs and the data
exchange between them. It provides:
• Network setup functions: A tree view shows the relations between the
DTMs, i.e. the relation between the Master and slave devices.
• Device Catalogue functions: A Device Catalogue containing the installed
DTMs is maintained, to which the user can add new DTMs or delete
them. Device DTMs can be added to the network from this Catalogue.
• Project maintenance functions: CX-Profibus provides the functions to create, save and open project files. It facilitates user access control, which
limits of use to authorized personnel only, using password protection.
• Additional functions: CX-Profibus provides additional functions like printing, error logging, FDT Communication logging and help files.
CS1/CJ1W-PRM21 DTM
The two CS1/CJ1W-PRM21 DTMs provided to configure the CS1/CJ1WPRM21 PROFIBUS DP Master Units and the CS1/CJ1W-PRM21 PROFIBUS
DP-V1 Master Units both provide the same basic PROFIBUS DP functions.
These DTMs consist of three parts:
• The Settings User Interface, which handles the configuration for the
PROFIBUS Master Unit. This includes the bus parameters settings, the I/
O data mappings and Master specific settings. The Settings DTM provides its own user interface.
• The Monitoring User Interface, which handles the status monitoring and
control over the PROFIBUS Master Unit, when it is on-line and communicating over the PROFIBUS network. It provides its own user interface to
read out Master status flags and Error log, as well as Slave status flags
and the Slave diagnostics messages received by the Unit. It also allows
the user to send Global-Control messages over the network and to
change the PROFIBUS Master Unit’s mode on the PROFIBUS network.
• The communication interface between the CS1/CJ1W-PRM21 DTMs and
CX-Server. CX-Server, provided with the CX-Profibus package, is the
driver for communication between the PC and the PLC CPU.
18
CX-Profibus Configurator
CS1/CJ1W-PRM21
PROFIBUS DP-V1 DTM
Section 1-4
In addition to the PROFIBUS DP functions, the CS1/CJ1W-PRM21 PROFIBUS DP-V1 DTM provides:
• A communication channel to the user to change a remote slave device
address. This channel has its own user interface.
• Communication channels to facilitate data transfer, PROFIBUS DP-V1
MSAC1 acyclic message transfer between a PROFIBUS DP-V1 slave
device DTM and the physical slave device.
C200HW-PRM21 DTM
The C200HW-PRM21 DTM allows configuration of the C200HW-PRM21
PROFIBUS DP Master Unit. This predecessor of the CS1/CJ1W-PRM21 can
be used on existing C200H PLC CPU Systems as well as CS1 PLC Systems,
except for the CS1D.
The C200HW-PRM21 DTM consist of three parts:
• The Settings User Interface, which handles the settings for the C200HWPRM21 PROFIBUS DP Master Unit, including the bus parameters settings, and the I/O data mappings.
• The Monitoring User Interface, to handle the Unit’s status monitoring. The
DTM’s user interface displays the Master status and Slave status.
• The communication interface between the two DTMs mentioned above
and the serial communication driver, to the C200HW-PRM21 PROFIBUS
DP Master Unit.
Note
1. This Operation Manual does not contain a detailed description of the
C200HW-PRM21 Unit, only a description of the DTM. For more details on
the C200HW-PRM21 refer to C200H-series PROFIBUS DP Master Units
Operation Manual ([email protected]).
2. The C200HW-PRM21 Unit and DTM do not support PROFIBUS DP-V1.
Generic Slave DTM
The Generic Slave DTM allows the handling of classic GSD files of up to GSD
revision 3 within CX-Profibus. Upon allocating a slave device, for which only a
GSD file is available to a Master Unit in the network, this DTM will be invoked.
This DTM consists of two parts:
• The Settings User Interface will provide the user interface to display the
device’s information and the selectable values, as defined in the GSD.
After making the necessary configuration settings, and saving them,
these will be transferred to the Master DTM.
• The Monitoring User Interface will provide a diagnostics interface to the
user, allowing him to check the Slave’s status. This DTM obtains the necessary information from the PROFIBUS Master Unit’s monitoring DTM.
Note The Generic Slave DTM provides parameter settings related to PROFIBUS
DPV1. However, it does not support PROFIBUS DP-V1 communication.
Downloading the
Configuration
After setting up the configuration, it must be downloaded to the PROFIBUS
Master Unit. The type of serial connection to use for downloading, depends
on the Unit:
• CS1/CJ1W-PRM21: Connection to the Unit is achieved through the serial
port of the PLC CPU, using CX-Server. CX-Server also allows routing the
download through multiple systems, if supported by these systems. The
CS1/CJ1W-PRM21 does not support message routing.
• C200HW-PRM21: Connection to the C200HW-PRM21 is achieved
through a serial RS-232c Connection between one of the PC’s Serial
COM Ports and the dedicated configuration connector at the front of the
19
CX-Profibus Configurator
Section 1-4
Unit. For details, refer to the C200HW-PRM21 Manual: W349-E2-2. The
figure below shows the connection methods, for both types.
Serial connection to CS/CJ-series
PROFIBUS DP Master Unit
Serial connection to C200H-series
PROFIBUS DP Master Unit
CX-Profibus
Configurator
CS/CJ-series
PROFIBUS DP
Master Unit
COM Port on PC
Peripheral Bus or
Host LINK
OMRON
SYSMAC CS1G
PROGRAMMABLE
CONTROLLER
COM Port on PC
OMRON
SYSMAC CS1G
PROGRAMMABLE
CONTROLLER
Peripheral or RS232C
Port of CPU Unit
PROFIBUS Network
20
C200H-series
PROFIBUS DP
Master Unit
CX-Profibus
Configurator
Configuration Port on
PROFIBUS DP
Master Unit
PROFIBUS Network
CX-Profibus Configurator
1-4-2
Section 1-4
Specifications
Functional Specifications
Operating environment
Item
Specification
Model number
WS02-9094G
Hardware platform
•
•
•
•
•
•
•
Operating System
• MS
• MS
• MS
Note
Connection to CS1/CJ1W-PRM21
• Peripheral or RS-232C port of PC with PLC CPU. Serial communications mode: Peripheral bus, Host Link, Toolbus, supported by CXServer.
• Communication cable: Cable CS1W-CN226 to connect to the peripheral port on the CPU (Not included in package).
Personal computer: IBM PC/AT or compatible
Processor: Pentium 500 MHz or higher
Memory: 256 Mbytes
Hard disk: A minimum of 256 Mbytes
CD-ROM drive
Graphics resolution: 800 x 600 pixels minimum
Serial port: RS-232C
Windows NT4.0, SP6
Windows 2000, SP2
Windows XP
Internet Explorer 5.01 is also required.
Connection to C200HW-PRM21
• RS-232C port of PC with Configuration port on the Unit.
General Project functions
File handling: CX-Profibus supports overall handling of project files as
well as network data.
• New:
Start a new project.
• Open:
Open an existing project file.
• Save (As): Save a project file.
• Export:
Export project data to HTML.
• Properties:Edit project property information.
User management: Functionality of CX-Profibus can be limited as
defined by several password protected access levels:
• Administrator
• Planning engineer
• Maintenance
• Operator
• Observer
Network setup functions
CX-Profibus provides network tree view, from which hierarchy between
Master and slave devices can clearly be distinguished.
CX-Profibus
The following network functions are available:
• Network DTMs (i.e. devices) can be added or deleted, using drag and
drop from the Device Catalogue.
• Network DTMs can be copied and moved from one location to another
in the network view.
• DTM names can be edited by the user.
• Any change to the parameters of a DTM is clearly marked in the tree
view, until the project is downloaded to the Master Unit.
Device Catalogue functions
The Device Catalogue maintains the installed device DTMs. After installation of a new DTM, the user must refresh the database. The Device
Catalogue provides the following functions:
• Update Device Catalogue.
• Add device DTMs to the network directly.
• Install a GSD file. This function allows copying of GSD files to a specific directory, after which they are available for the Generic Slave
DTM.
Support functions
CX-Profibus provides the following additional support functions:
• Context sensitive help functions.
• Error logging.
• Monitoring of FDT communication between DTMs.
• Multi-language support.
21
CX-Profibus Configurator
Section 1-4
Generic Slave DTM
C200HW-PRM21 DTM
CS1/CJ1W-PRM21 DTM
Item
22
Specification
Device setup
Device setup allows the user to:
• Select the PROFIBUS Master Unit’s unit number.
• Configure the communication link between the PC and the Unit. This
function invokes the user interface of CX-Server.
• Test the Units communication link and read out the Unit’s information.
Master setup
It allows enabling of Auto Addressing, to facilitate I/O data mapping, as
well as defining the Unit’s behaviour in case of
• a network malfunction.
• a PLC mode change between PROGRAM and RUN/MONITOR mode.
Bus parameter setup
The bus parameter setup allows the selection of baud rate and calculation and editing of specific bus parameters.
Slave area setup
The Slave area setup allows the user to define the I/O Data mapping of
the I/O Data from each of the slave devices on to the PLC memory
areas.
Monitoring functions
• Master status read out.
• Slave status and slave diagnostics read-out.
• Read out of the Unit’s error log.
Additional Master functions
• Set remote slave address.
• Provide communication channels for PROFIBUS DP-V1 MSAC1 messages.
Note These functions are implemented as of Unit version 2.0.
Support functions
• Context sensitive help functions.
• Multi-language support.
Bus parameter setup
The bus parameter setup allows the selection of baud rate and calculation and editing of specific bus parameters.
Address mapping setup
The address mapping setup shows an overview of the mapping of the I/
O data of each Slave on to the Unit’s memory. The mapping can be
accomplished automatically, but the function also allows editing of individual address mappings.
Monitoring functions
• Master status read out.
• Slave status read-out.
Support functions
• Context sensitive help functions.
• Multi-language support.
General functions
The Generic Slave DTM reads the contents of a specific GSD file located
in a special sub-directory, and displays the setup options to the user. It
supports
• GSD file revisions 1 and 2 (PROFIBUS DP functionality).
• GSD file revisions 3 (PROFIBUS DP-V1 functionality).
I/O configuration setup
The I/O configuration setup function allows:
• Selection of device address.
• Enable/disable watchdog.
• Overview of available I/O modules.
• Selection of I/O modules, including Addition, Insertion and Removal of
multiple modules.
Parameter setup
The Parameter setup function:
• Setting of common as well as module dependent parameters.
• Setting of PROFIBUS DP Extension parameters.
• Setting of PROFIBUS DP-V1 dependent parameters.
Group setting
The Group setup function allows definition of the group to which the
associated slave device will belong.
Monitoring functions
The Monitoring functions provides a display of
• Standard Slave diagnostics flags.
• Extended diagnostics messages.
Support functions
• Context sensitive help functions.
• Multi-language support.
Basic Operating Procedure
1-5
1-5-1
Section 1-5
Basic Operating Procedure
Overview
The following diagram provides an overview of the installation procedures.
For experienced installation engineers, this may provide sufficient information. For others, cross-references are made to various sections of this manual
where more explicit information is given.
Mount the PROFIBUS Master Unit on
to the PLC
(See section 2-2 Installing the CS1/
CJ1W-PRM21 Units)
Select a unique Identity Number (0 - F)
for the Unit using the rotary switch on
the front of the Unit
(See section 2-3 Initial Setup
Procedure)
Connect the PROFIBUS Master unit to
the PROFIBUS network
(See section 2-4 Setting up a Network)
Switch on the power supply for the PLC
and create a PLC I/O table in CXProgrammer. See CX-Programmer
User Manual (Reference No. W361).
Configure the PROFIBUS Master Unit
using CX-Profibus on the PC.
(See sections 3-3 CS1/CJ1W-PRM21
PROFIBUS Master DTM and 6-4
Configuring the Master)
Download configuration data to
PROFIBUS Master Unit.
(See sections 3-3-3 Connecting to the
CS1/CJ1W-PRM21) and 6-4-5
Downloading the Configuration)
PROFIBUS DP starts communicating,
confirmed by the COMM LED
continuously lit. Check status of other
LED Indicators (See sections 6-5 I/O
Communication Characteristics, 6-6
Operating the Network and 6-7
Monitoring the Network)
23
Basic Operating Procedure
1-5-2
Section 1-5
Preparations for Communications
1,2,3...
1. Mount the Master Unit on the PLC system (refer to 2-2 Installing the CS1/
CJ1W-PRM21 Units).
• Treat the Unit as a CPU Bus Unit.
• It can be mounted to a CPU Rack or Expansion Rack.
• Number of Units: 16 (Max).
2. Set the Unit No. (UNIT No.) for the PROFIBUS Master Unit (refer to 2-3-1
Selecting a unit number).
3. Connect a PC or a Programming Device to the PLC and turn ON the power
supply to the PLC.
4. Generate the I/O tables and restart the PLC (refer to 2-3-2 Creating an I/O
table).
5. Install CX-Profibus, and the DTMs on to the PC.
1-5-3
Procedures Prior to Starting Communications
Use the following procedure to configure the Unit using CX-Profibus:
1,2,3...
1. Wire the network, to connect the PROFIBUS Master Unit to the slave devices.
2. Turn ON the PLC power supply and the power supplies of the slave device
on the network.
3. In CX-Profibus, create a network and define the parameters and I/O configurations for the PROFIBUS Master Unit settings and the allocated slave
devices. Determine the baud rate and the bus parameter setup. Make sure
that the “Go to OPERATE mode“ option is selected, to force the Unit to OPERATE mode upon a PLC mode change to RUN / MONITOR mode.
4. Download the network configuration to the PROFIBUS Master Unit. After
downloading the configuration, CX-Profibus will restart the PROFIBUS
Master Unit.
5. After restarting the PROFIBUS Master Unit it will automatically start communication.
24
SECTION 2
Installation and Wiring
This section shows the PROFIBUS device and identifies its controls and indicators. It contains the procedures for installing
the CS1/CJ1W-PRM21 PROFIBUS Master Unit on the PLC System and setting up the PROFIBUS network.
2-1
2-2
2-3
2-4
2-5
Unit Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-1-1 Nomenclature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-1-2 Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-1-3 Switch Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-1-4 PROFIBUS Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installing the CS1/CJ1W-PRM21 Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-2-1 Handling Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-2-2 Mounting the CS1W-PRM21 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-2-3 Mounting the CJ1W-PRM21 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Initial Setup Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-3-1 Selecting a unit number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-3-2 Creating an I/O table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Setting up a Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-4-1 Network Structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-4-2 Bus Termination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-4-3 PROFIBUS Cable Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-4-4 Shielding Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Defining PROFIBUS DP in the Software . . . . . . . . . . . . . . . . . . . . . . . . . . . .
26
26
27
28
29
30
30
30
32
33
34
34
35
35
37
38
39
39
25
Unit Components
2-1
2-1-1
Section 2-1
Unit Components
Nomenclature
The illustration below shows the Status LED indicators, the Unit number
selector switch, and a 9-pin female sub-D connector on the front side of the
CS1W-PRM21 and the CJ1W-PRM21 Units. Each of these components are
explained in the following sections
CS1W-PRM21
PRM21
CS
RUN
ERC
BST
BF
ERH
PRM
COMM
6543
DCB
UNIT
No. 210FE
A987
BUS
Indicators
Unit number switch
This switch sets the Unit Number of the
PROFIBUS DP Master Unit as a one-digit
hexadecimal number
PROFIBUS DP Connector
9-Pin Sub-D, female connector, #4/40 UNC thread
Connect the PROFIBUS DP network cable to this
connector. Termination must be provided with the
cable connector
CJ1W-PRM21
PRM21
RUN
ERC
PRM COMM
ERH
BST
Indicators
BF
EF01
6789
4
23 5
UNIT
NO.
Unit number switch
This switch sets the Unit Number of the
PROFIBUS DP Master Unit as a one-digit
hexadecimal number
C
AB D
BUS
PROFIBUS DP Connector
9-Pin Sub-D, female connector, #4/40 UNC thread
Connect the PROFIBUS DP network cable to this
connector. Termination must be provided with the
cable connector
26
Unit Components
2-1-2
Section 2-1
Indicators
The CS1/CJ1W-PRM21 PROFIBUS Master Units are each fitted with seven
LEDs to indicate the operational mode and status of the Unit and the PROFIBUS network
CS1W-PRM21
PRM21
RUN
ERC
BST
BF
CJ1W-PRM21
PRM21
CS
RUN
ERC
PRM COMM
ERH
BST
BF
ERH
PRM
COMM
Indicator Specifications
Indicator
Colour
RUN
Green
ERC
(PROFIBUS Master Unit
Error)
Red
ERH
(PLC Error)
Red
PRM
(Parameter database)
Green
BST
(Bus status)
Green
COMM
(I/O Data communication)
Green
BF
(Bus Fail)
Red
Status
Meaning
Not lit
• Startup test failed, Unit not operational.
• Operation stopped, due to a fatal error.
Lit
Initialization successful, Unit is in normal operation.
Not lit
Unit is in normal operation.
Lit
One of the following errors occurred:
• Startup error.
• Non-volatile memory error (checksum failed, write-verify failed).
• Invalid PROFIBUS parameter configuration setting.
• Fatal error in program execution.
Not lit
PLC CPU in normal operation.
Lit
One of the following errors occurred:
• PLC CPU Bus error.
• Cyclic Refresh Monitor Time-out.
Not lit
PROFIBUS Parameter configuration is not available or incorrect.
Flashing
PROFIBUS Parameter configuration is being transferred to the Unit
and is not yet available.
Lit
PROFIBUS Parameter configuration is correct, and operational.
Not lit
The PROFIBUS Master Unit is in OFFLINE or STOP mode.
Flashing
The PROFIBUS Master Unit is in CLEAR mode.
Lit
The PROFIBUS Master Unit is in OPERATE mode.
Not lit
No PROFIBUS data exchange with any of the allocated slaves.
Flashing
Fatal error occurred (ERC LED is ON). Unit initialization failed.
Lit
PROFIBUS data exchange ongoing with at least one allocated slave.
Not lit
No PROFIBUS communication errors occurred.
Flashing
At least one allocated slave is not in data exchange with the Unit.
Lit
An error occurred in the PROFIBUS interface of the Unit (see section 72 Troubleshooting Using LED Indicators).
Note Unless otherwise specified, the frequency of a flashing LED is 1 Hz (50% duty
cycle).
27
Unit Components
2-1-3
Section 2-1
Switch Settings
Setting the Unit Number
The unit number is used to identify individual CPU Bus Units when more than
one CPU Bus Unit is mounted to the same PLC. The unit number must be
unique for each CPU Bus Unit. Selecting a non-unique number for a CPU Bus
Unit will prevent the PLC System from starting correctly.
CS1W-PRM21
CJ1W-PRM21
01
EF 2
789A
3456
DCB
65432
UNIT
No. 10FE
Setting range:
0 ~ F (Hexadecimal)
UNIT
NO.
A987
BCD
1. Turn OFF the power supply before setting the Unit number.
2. Set the switch to the new Unit number. Use a small screwdriver to make
the setting, taking care not to damage the rotary switch. The unit number
is factory-set to 0.
3. Turn ON the power again.
Note Always turn OFF the power to the PLC CPU before changing the Unit number
setting. The Unit only reads the Unit number setting during the initialization
following a power-up, but not following a software reset.
Note If the unit number is being set for the first time or changed, then an I/O table
must be created for the PLC.
Unit Number and CPU Bus
Unit Word Allocations
With CS/CJ-series PLCs, words are automatically allocated in the CIO Area
and the DM Area. The PROFIBUS Master Unit uses these words for receiving
control data from the CPU Unit and for notifying the CPU Unit of PROFIBUS
Master Unit and communications status. The word addresses in the allocated
areas for the CPU Bus Unit are important when creating the user program for
using the PROFIBUS Master Unit. This must be considered when setting the
unit number.
The CIO and DM Word allocations are discussed in detail in 4-2 Allocated
CIO Area Words. The tables below show the relation between the unit number and the allocated CIO Area and DM Area words.
Unit No.
(decimal)
0 (0)
28
Allocated words
CIO1500 to CIO1524
Unit No.
(decimal)
8 (8)
Allocated words
CIO1700 to CIO1724
1 (1)
CIO1525 to CIO1549
9 (9)
CIO1725 to CIO1749
2 (2)
CIO1550 to CIO1574
A (10)
CIO1750 to CIO1774
3 (3)
CIO1575 to CIO1599
B (11)
CIO1775 to CIO1799
4 (4)
CIO1600 to CIO1624
C (12)
CIO1800 to CIO1824
5 (5)
CIO1625 to CIO1649
D (13)
CIO1825 to CIO1849
6 (6)
CIO1650 to CIO1674
E (14)
CIO1850 to CIO1874
7 (7)
CIO1675 to CIO1699
F (15)
CIO1875 to CIO1899
Unit Components
Section 2-1
DM Area Allocations
Unit No.
(decimal)
0 (0)
2-1-4
Allocated words
D30000 to D30099
Unit No.
(decimal)
8 (8)
Allocated words
D30800 to D30899
1 (1)
D30100 to D30199
9 (9)
D30900 to D30999
2 (2)
D30200 to D30299
A (10)
D31000 to D31099
3 (3)
D30300 to D30399
B (11)
D31100 to D31199
4 (4)
D30400 to D30499
C (12)
D31200 to D31299
5 (5)
D30500 to D30599
D (13)
D31300 to D31399
6 (6)
D30600 to D30699
E (14)
D31400 to D31499
7 (7)
D30700 to D30799
F (15)
D31500 to D31599
PROFIBUS Connector
The PROFIBUS connector on the font of the Unit is a 9-pin female sub-D connector, as recommended by the PROFIBUS standard EN 50170.
5
9
6
1
Pin No.
Signal
1
Shield
2
--
3
RxD/TxD-P
4
RTS
5
DGND
6
VP
7
--
8
RxD/TxD-N
9
-
Description
Shield/protective ground
Receive/Transmit data - plus (B wire)
Control signal for repeaters (direction control) (TTL)
Data ground (reference potential for VP)
Supply voltage of the terminator resistance (5 Vdc)
Receive/Transmit data - minus (A wire)
-
The signal RTS (TTL signal) is for the direction control of repeaters, which do
not have a self-controlling capability.
The signals DGND and VP are used to power the bus terminator located in
the cable connector.
Note The orientation of the sub-D connector allows the use of PROFIBUS connectors with a 90° angle cable outlet, e.g ERNI, Delconec and Phoenix.
Note The 9-pin sub-D connector uses #4/40 UNC thread, for mechanical fixation of
the cable connector. Make sure that if non-standard PROFIBUS connectors
are used, the corresponding thread is used on the cable connector.
29
Installing the CS1/CJ1W-PRM21 Units
2-2
2-2-1
Section 2-2
Installing the CS1/CJ1W-PRM21 Units
Handling Precautions
When installing the PROFIBUS Master Unit on the PLC system, observe the
following handling precautions
• Always turn OFF the power supply to the PLC before mounting or dismounting a Unit or connecting or disconnecting cables.
• Provide separate conduits or ducts for the I/O lines to prevent noise from
high-tension lines or power lines.
• Leave the label on top of the Unit attached when wiring. Removing the
label prior to wiring may result in malfunction if foreign matter enters the
Unit.
• Remove the label after the completion of wiring to ensure proper heat dissipation. Leaving the label attached may result in malfunction.
2-2-2
Mounting the CS1W-PRM21
The CS1W-PRM21 PROFIBUS Master Unit can be mounted to any slot in
either a CS-series CPU Rack, a CS-series Expansion CPU Rack or a CS1
Duplex CPU Rack. The CS-series PLC supports up to 7 Expansion CPU
Racks, in addition to the CPU rack.
The number of slots to which PROFIBUS Master Unit can be mounted
depends on the Backplane. Up to 16 PROFIBUS Master Units can be
mounted to a single PLC system. If it is mounted in combination with other
CPU Bus Units (e.g., Ethernet Units), the maximum total number of CPU Bus
Units that can be mounted is 16.
.
PS
CPU
CS1W-BC023 / BC033 / BC053 / BC083 / BC103 CPU Backplane
CS-series CPU Rack
Can mount to any position,
with 2, 3, 5, 8, or 10 slots.
2, 3, 5, 8, or 10 slots
(Expansion Backplane not possible with 2-slot CPU Backplane.)
CS1W-BI033 / BI053 / BI083 / BI103 CS-series Expansion Backplane
PS
CS-series Expansion Rack
Up to 16 Units can be mounted
to the slots shown in the diagrams
on the left.
Can mount to any position,
with 3, 5, 8, or 10 slots.
3, 5, 8, or 10 slots
C200H Expansion I/O Backplane
PS
C200H Expansion Rack
PROFIBUS DP Master Unit cannot be
mounted to any slots.
CPU: CPU Unit
PS: Power Supply Unit
Note The CS1W-PRM21 PROFIBUS Master Unit’s maximum current consumption
is 400 mA. Make sure that the total current consumption of all the Units connected to the same CPU Backplane or Expansion Backplane does not exceed
the output capacity of the Power Supply Unit.
30
Installing the CS1/CJ1W-PRM21 Units
Mounting Procedure
Section 2-2
Mount the CS1W-PRM21 PROFIBUS Master Unit to the Backplane using the
following procedure.
!Caution Always turn OFF the power supply to the PC before mounting or dismounting
a Unit or connecting or disconnecting cables.
1,2,3...
1. Hook the claw on the top of the Unit onto the Backplane.
Claw
Backplane
2. Insert the Unit into Backplane connectors and securely tighten the screw
at the bottom of the Unit. Tighten the screws to a torque of 0.4 N•m.
3. When removing the Unit, first loosen the screw at the bottom of the Unit.
Fixing screws
Note When mounting the Unit, provide the clearance shown below to facilitate easy
mounting or dismounting.
Duct
20 mm min.
Backplane
20 mm min.
Duct
Philips screwdriver
31
Installing the CS1/CJ1W-PRM21 Units
2-2-3
Section 2-2
Mounting the CJ1W-PRM21
The PROFIBUS Master Unit can be mounted to any slot in either a CJ-series
CPU Rack, or a CJ-series Expansion CPU Rack. The CJ-series PLC supports
up to 4 Expansion CPU Racks, in addition to the CPU rack.
The number of slots to which PROFIBUS Master Unit can be mounted in any
of the positions shown below using the sliders on the top and bottom of the
Unit. Up to 16 PROFIBUS Master Units can be mounted to a single PLC. If it
is mounted in combination with other CPU Bus Units (e.g., Ethernet Units),
the maximum total number of CPU Bus Units that can be mounted is 16.
PLC CPU rack
10 Units max.
End cover
P C I
S P C
U
Expansion Backplane
10 Units max.
End cover
P I
S I
Expansion Backplane
10 Units max.
End cover
Up to 16 PROFIBUS DP
Master Units can be
mounted.
P I
S I
Expansion Backplane
10 Units max.
End cover
P I
S I
PS: Power Supply Unit
CPU: CPU Unit
IC: I/O Control Unit
II: I/O Interface Unit
Note The CJ1W-PRM21 PROFIBUS Master Unit’s maximum current consumption
is 400 mA. Make sure that the total current consumption of all the Units connected to the same CPU Backplane or Expansion Backplane does not exceed
the output capacity of the Power Supply Unit.
32
Initial Setup Procedure
Section 2-3
Mounting Procedure
Mount the CJ1W-PRM21 PROFIBUS Master Unit to the PLC using the following procedure.
1. Carefully align the connectors to mount the PROFIBUS Master Unit.
Connector
PA205R
SYSMAC
CJ1G-CPU44
POWER
PRM21
RUN
ERR/ALM
RUN
INH
PRPHL
PROGRAMMABLE
CONTROLLER
ERC
PRM
COMM
ERH
BST
BF
COMM
OPEN
01
EF 2
789A
3456
UNIT
NO.
BCD
MCPWR
BUSY
L1
AC100-240V
INPUT
L2/N
PERIPHERAL
BUS
RUN
OUTPUT
AC240V
DC24V
PORT
2. Move the yellow sliders on the top and bottom of the Unit until they click
into position, to lock.
Slider
PA205R
SYSMAC
CJ1G-CPU44
PROGRAMMABLE
CONTROLLER
RUN
ERR/ALM
INH
PRPHL
Lock
PRM21
RUN
ERC
PRM
COMM
ERH
BST
BF
COMM
OPEN
789A
3456
01
EF 2
POWER
UNIT
NO.
BCD
L1
Release
MCPWR
BUSY
AC100-240V
INPUT
L2/N
PERIPHERAL
BUS
RUN
OUTPUT
AC240V
DC24V
BUS
PORT
Note If the sliders are not securely locked, the PROFIBUS Master Unit functions
may not operate correctly.
To dismount the Unit, move the sliders to the “Release” direction.
2-3
Initial Setup Procedure
After mounting the PROFIBUS Master Unit to its PLC System, the following
Initial Setup Procedure must be applied to allow the Unit to start up properly
and to be configured for operation.
• A unique unit number must be selected, before the PLC’s power supply is
turned on.
• An I/O table must be created in the PLC, in order to register the Unit on
the PLC CPU.
33
Initial Setup Procedure
2-3-1
Section 2-3
Selecting a unit number
1. Make sure that the PLC Power Supply is turned OFF before setting the
Unit number.
2. Set the switch to the desired unit number. Use a small screwdriver to make
the setting, taking care not to damage the rotary switch. The unit number
is factory-set to 0. Make sure that the unit number is unique on the PLC,
i.e. there must be no other CPU Bus Units with the same unit number.
3. Turn ON the PLC Power Supply.
After setting the unit number, the PLC CPU must now register the PROFIBUS
Master Unit, by creating an I/O table.
2-3-2
Creating an I/O table
An I/O table is used to identify Units connected to the PLC and to allocate I/O
to them. The I/O table is stored within the PLC CPU, and loaded at start up. If
any change is made to the Unit configuration of a CS/CJ-series PC, the I/O
table must be created again to register the Units to the CPU Unit.
Connecting a
Programming Device
To create the I/O table, connect a Programming Device (such as a Programming Console or CX-Programmer) to the PLC.
Applicable Programming
Devices
The following Programming Devices can be used with CS/CJ-series PLCs.
Programming Console
Model number
C200H-PRO27-E
Key Sheet (required)
CS1W-KS001-E
Recommended cable (required)
CS1W-CN224 (cable length: 2.0 m)
CS1W-CN624 (cable length: 6.0 m)
CX-Programmer and CX-Net
Model number: [email protected]@-EV2
The operations are explained here using a Programming Console. For details
regarding the CX-Programmer and the CX-Net, refer to the CX-Programmer
User’s Manual.
CX-Net is software that comes with CX-Programmer and is automatically
installed when CX-Programmer is installed.
Connecting Programming
Devices
To connect a Programming Console, attach a CS/CJ-series Key Sheet and
then connect the Console to the CPU Unit’s peripheral port. (It cannot be connected to the RS-232C port.)
Procedure for Creating an
I/O Table
The procedure for creating an I/O table is shown here, taking as an example
an I/O table that is generated automatically for a PLC connected online. In this
example, a Programming Console is used for creating the I/O table. For an
explanation of how to create an I/O table using a CX-Programmer, refer to the
CX-Programmer User’s Manual.
Use the following procedure to create the I/O table.
34
Setting up a Network
Section 2-4
Initial screen
SHIFT
CH
*DM
000000 I/O TBL ?
CHG
000000 I/O TBL
WRIT
????
WRITE
Password
000000CPU BU ST?
0:CLR 1:KEEP
or
(Save or clear the CPU Bus Unit System Setup.)
000000 I/O TBL
WRIT OK
After creating the I/O table, the Unit is ready to be configured for first use on
the PROFIBUS network.
Note After mounting the Unit and starting it up for the first time, the Unit’s Configuration is empty. This will cause the red ERC LED on the front of the Unit to be
switched ON. In this situation, the Unit can still be configured.
2-4
2-4-1
Setting up a Network
Network Structure
Communication Medium
The PROFIBUS standard defines the use of EIA RS-485 as the main communication transport medium. The PROFIBUS Master Unit is designed to interface directly to this type of medium. This section will discuss the setup of
networks based on this medium.
Note The other communication medium specified for PROFIBUS is optical fibre.
The PROFIBUS Master Units does not provide a direct interface to this type of
medium. However, by using third party couplers an interface between EIA RS485 and optical fibre networks can be made.
Linear Bus Topology
PROFIBUS DP defines the use of the Linear Bus Network Topology. The Bus
must be terminated at both ends, and must not contain network branches.
The total cable length of the bus depends on the cable and the selected baud
rate. Also, RS-485 specifies a maximum of up to 32 devices - master and
slave devices - per line segment. If more than 32 devices are to be connected, or if the total length of the segment must be extended beyond its maximum, repeaters must be used to link the separate segments.
35
Setting up a Network
Section 2-4
Note Repeaters are devices which connect two segments. They do not have a
device address of their own, but they do count in the total number of devices
in a segment.
Repeaters
A maximum of up to three repeaters between two devices in a network can be
used, i.e. a network can consist of up to 4 segments. The maximum number
of PROFIBUS devices in such a network is then 122. The figure below shows
an example of a two-segment network.
OMRON
SYSMAC CS1G
P R O G R A MMA B LE
C O N T R O LLE R
Termination
Station 1
Termination
Termination
Repeater
Station 2
Station 3
Station 31
Termination
Station 63
Tree Topology
Station 33
Station 32
The use of repeaters allows the extension of three or more Linear Bus segments into a Tree topology. In a tree topology more than three repeaters are
allowed, provided that there are no more than three repeaters between any
two devices in the network. The following figure presents an example of a network with more than three segments and repeaters.
Segment 1
Max. 31 stations
Segment 2
Max. 31 stations
M/S
M/S
R
Segment 3
Max. 28 stations
R
M/S
Segment 4
Max. 31 stations
R
R
Segment 5
Max. 30 stations
M/S
M/S
R
Master or slave station
Repeater
Termination
Max. total number of stations = 126
36
M/S
R
Segment 6
Max. 31 stations
M/S
Setting up a Network
Section 2-4
Cable Type
The PROFIBUS standard EN 50170 specifies Type A shielded, twisted- pair
cable as the recommended cable type for use in an RS-485 based PROFIBUS network. This cable type has the following characteristics:
Characteristic
Value
Impedance
135 - 165 ohms
Capacitance per unit length
< 30 pF/m
Loop resistance
110 ohms/km
Core diameter
0.64 mm
Core cross section
0.34 mm2
Note The PROFIBUS standard EN 50170 also specifies a Type B cable with different cable characteristics. Use of Type B cable is no longer recommended.
Maximum PROFIBUS
Cable Length
The transmission speed defines the maximum advised cable distance or
cable segment in metres before the use of a repeater is recommended. The
cable lengths specified in the following table are based on PROFIBUS type A
cable.
Baud rate
(kbit/s)
Distance/segment
(m)
Baud rate
(kbit/s)
Distance/segment
(m)
9.6
1200
500
400
19.2
1200
1500
200
45.45
1200
3000
100
93.75
1200
6000
100
187.5
1000
12000
100
Note If network extension beyond the range of the advised cable length is required,
the use of fibre optic cable to cross the larger distance should be considered.
Stub Lines
2-4-2
Passive Stub lines (branches from the main line) should be avoided for data
transmission speeds of more than 500 kbit/s. Except at end devices with termination, it is recommended to always use plug connectors that permit two
data cables to be connected directly to the plug. This method allows the bus
connector to be plugged and unplugged at all times without interrupting data
communication between other devices.
Bus Termination
Termination Resistors
VP
390 Ohm
B-Line
220 Ohm
The bus terminator connects the two data lines via a 220 ohm resistor which,
in turn, is connected to VP 5Vdc and DGND via two 390 ohm resistors. Powering the terminator resistor via VP 5V and DGND ensures a defined idle state
potential on the data lines.
To ensure the correct functioning up to the highest baud rate, the bus cable
must be terminated at both its ends.
A-Line
390 Ohm
DGND
Network
In order to minimize cable reflections and ensure a defined signal level on the
data lines, the data transfer cable must be terminated at both ends with a terminating resistor combination. The bus termination diagram is shown on the
left.
A missing bus termination can cause errors during data transfer. Problems
can also arise if too many bus terminators are fitted, since each bus terminator represents an electrical load and reduces the signal levels and thus the
signal-to-noise ratio. Too many or missing bus terminators can also cause
37
Setting up a Network
Section 2-4
intermittent data transfer errors, particularly if the bus segment is operated
close to the specified limits for maximum numbers of devices, maximum bus
segment length and maximum data transfer rate.
Inductors
110 mH
B-Line
Network
A-Line
110 mH
2-4-3
In addition to the bus termination, additional precautions must be taken to
ensure proper operation at high baud rates, i.e. baud rates of 500 kbit/s and
higher. Due to the capacitive load of the device and the resulting cable reflections, bus connectors must be provided with built-in series inductors, of 110
mH each, as shown in the figure on the left.
Installing the inductors applies to all devices on the network, and not only to
the devices at both ends of the bus cable.
PROFIBUS Cable Connector
Bus Cable Connector
The plug connector to be used on the CS/CJ-series PROFIBUS Master Unit is
a 9-pin male sub-D type, preferably encased in metal and having a facility to
connect the shield of the cable to the case or to pin 1. The cable should be
connected to the receive / transmit lines, pin 3 (B-line) and pin 8 (A-line).
The use of special PROFIBUS DP cable connectors, which are available from
several manufacturers, is highly recommended. Various models are widely
available, with or without the bus termination and inductors built-in. If provided
in the connector, the Bus termination can often be enabled or disabled
through a switch on the connector.
The special PROFIBUS DP cable connectors often provide a convenient way
of connecting the cables. The figure on the left, provides an example of such
a bus cable connector.
A standard 9-pin sub-D plug can only be used if the PROFIBUS Master Unit is
not at the start or the end of a bus segment, or on a stub line at a baud rate of
500 kbit/s or less.
To next
station
From
previous
station
The two PROFIBUS data lines are designated A and B. There are no regulations on which cable core colour should be connected to which of the two data
terminals on each PROFIBUS device; the sole requirement is to ensure that
the same core colour is connected to the same terminal (A or B) for all
devices throughout the entire system (across all devices and bus segments).
The PROFIBUS Organization recommends the following rule for data line
colour codes: PROFIBUS cables in general will use the colours red and green
for the data lines, with the following assignment:
• Data cable wire A - green
• Data cable wire B - red
This rule applies to both the incoming and the outgoing data lines.
38
Defining PROFIBUS DP in the Software
2-4-4
Section 2-5
Shielding Precautions
Cable Shield Connection
Inside cabinet
Ground Rail
To ensure electro-magnetic compatibility (EMC), the shield of the cable
should be connected to the metal case of the plug connector.
If the Unit is installed in a control cabinet, the bus cable shield should be
brought into physical contact with a grounding rail using a grounding clamp or
similar device. The cable shield should continue in the cabinet right up to the
PROFIBUS device.
Ensure that the PLC and the control cabinet in which it is mounted have the
same ground potential by providing a large-area metallic contact to ground,
e.g. galvanized steel to ensure a good electrical connection. Grounding rails
should not be attached to painted surfaces.
For further information regarding PROFIBUS network installation, please refer
to “Installation Guideline for PROFIBUS DP/FMS” (PNO Order No. 2.112),
which is available at every regional PROFIBUS Organization. The information
covers:
Outside cabinet
• Commissioning of PROFIBUS equipment.
• Testing the PROFIBUS cable and bus connectors.
• Determining loop resistance.
• Testing for correct bus termination.
• Determining the segment length and cable route.
• Other test methods.
• Example of an equipment report in the PROFIBUS guideline.
2-5
Defining PROFIBUS DP in the Software
Defining the Configuration
After making the physical connections of the network, the configuration then
has to be defined in the software. OMRON provides a dedicated PC-based
configuration program, called CX-Profibus, as well as the required DTMs for
this purpose. It must be used to:
• Define the master(s).
• Assign slaves to their respective master(s).
• Assign slaves to groups for broadcast/multicast messages.
• Enter bus parameters, e.g. baud rate, target rotation time etc.
Downloading the
Configuration
The system must be downloaded to the Master Unit after configuring it at the
PC. This is made possible by either connecting the serial COM port of the PC
to the CS1/CJ1 PLC with a serial interface cable, or use an ethernet connection between the PC and the CS1/CJ1 PLC via an ethernet unit or Controller
Link unit.
39
SECTION 3
Configuration Software
This section contains the procedures for installing the configuration software. It also presents an overview of the
Configuration software and discusses the main aspects of defining a PROFIBUS configuration. A more detailed description
of the use of the Configuration software can be found in SECTION 6 Operation.
3-1
3-2
3-3
3-4
3-5
Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-1-1 Installation Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-1-2 Installation Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-1-3 Installing the C200HW-PRM21 DTM . . . . . . . . . . . . . . . . . . . . . . .
CX-Profibus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-2-1 Starting CX-Profibus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-2-2 CX-Profibus Main Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-2-3 Device Catalogue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-2-4 Updating the Device Catalogue . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-2-5 Adding Devices to the Network . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-2-6 Saving and Opening Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-2-7 Exporting to HTML . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-2-8 Error Logging and FDT Monitoring. . . . . . . . . . . . . . . . . . . . . . . . .
3-2-9 Access Control and User Management. . . . . . . . . . . . . . . . . . . . . . .
CS1/CJ1W-PRM21 PROFIBUS Master DTM . . . . . . . . . . . . . . . . . . . . . . . .
3-3-1 Configuration User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-3-2 Diagnostics User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-3-3 Connecting to the CS1/CJ1W-PRM21 . . . . . . . . . . . . . . . . . . . . . . .
C200HW-PRM21 PROFIBUS DP Master DTM . . . . . . . . . . . . . . . . . . . . . .
3-4-1 Configuration User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-4-2 Diagnostics User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-4-3 Connecting to the C200HW-PRM21 . . . . . . . . . . . . . . . . . . . . . . . .
Generic Slave Device DTM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-5-1 Configuration User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-5-2 Diagnostics User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
42
42
42
50
51
51
52
55
57
57
58
58
59
61
63
63
74
80
83
83
88
91
92
93
101
41
Installation
3-1
3-1-1
Section 3-1
Installation
Installation Requirements
CX-Profibus Configuration software is required to configure the PROFIBUS
Master Unit before operating the network. Without a valid configuration the
PROFIBUS Master Unit will not be able to achieve data communication with
the slave devices on the network.
The following are the minimum requirements for a PC to install the CX-Profibus configurator software:
• PC Pentium III or higher, 500 MHz minimum
• Operating System:
Windows 2000 SP2 / Windows NT 4.0, SP6 /
Windows XP
• RAM:
256 MB minimum
• Hard disk space:
256 MB minimum
• Graphics resolution:
1024 x 768 pixels minimum
• Serial port:
RS-232C; COM1 to COM4 supported
• CD-ROM drive
• Communication cable: Cable CS1W-CN226 to connect to the peripheral
port on the CPU (Not included with CX-Profibus)
3-1-2
Installation Procedure
This section explains how to install the CX-Profibus Configuration software
and its components for the PROFIBUS Master Unit.
CX-Profibus CD-ROM
CX-Profibus is provided on a CD-ROM, which contains the following components:
• Microsoft .NET Framework
• CX-Profibus FDT Container application.
• CS1/CJ1W-PRM21 Configuration DTMs.
• CX-Server, to allow communication between the PC and the PLC.
• C200HW-PRM21 Configuration DTM.
• Generic Slave Device DTM, to allow slave configuration using GSD files.
• Additional GSD files for several OMRON slave devices.
Note
1. Any older version of CX-Profibus installed on the system, must be uninstalled, prior to installing the newer version.
2. Provided with the CD-ROM is a 16-digit installation key, which can be
found on a label on the CD-ROM box. The key is unique to the CD-ROM
and is required to allow full installation of the software. The key is also used
as reference when registering the purchased software with OMRON.
3. If during installation the 16-digit License code was not entered, the program will run in demo mode, i.e. it provides all functionality, but for a limited
period of 30 days. After this period has expired, the License code must be
provided to the program, to allow continuation of use.
4. During the limited period of 30 days, the valid License code, as shown on
the CD-ROM case can be entered at anytime when the program is running,
by selecting the License button in the About dialog window.
5. Administrator rights are required to install CX-Profibus.
42
Installation
Section 3-1
6. The operations and displays shown in the following procedure may differ
slightly depending on the version of Windows software being used. The
displays for Windows 2000 are shown here.
1,2,3...
1. Exit all other Windows-based programs.
2. Insert the setup disk (CD-ROM) into the CD-ROM drive.
3. Double-click Setup.exe.
The setup program for CX-Profibus will start. A progress dialog window is displayed, indicating progress of the setup as the program is loaded.
4. During the preparation, the InstallShield wizard will determine if the Microsoft .NET framework needs to be installed. This package is required
during installation and for executing CX-Profibus. If already installed, the
installation will be skipped, and the process will proceed with step 7. Installation of the Microsoft .NET framework first displays the License statement
(shown below) to which the user must agree. Next, press the Install button
to continue.
43
Installation
Section 3-1
5. After starting the Microsoft .NET framework installation process, a window
will be displayed showing the progress of this installation.
6. Completion of the Microsoft .NET framework installation is indicated by
displaying the message window below.
7. After installing the Microsoft .NET framework, CX-Profibus and its components will be installed. The installation welcome window as shown below
will be displayed. Click the Next button to continue.
8. After the welcome window the window containing the License statement
for CX-Profibus is displayed. The License window is shown below. Please
read the License carefully, before selecting the Yes button to accept the
44
Installation
Section 3-1
License. If the License is not accepted - by selecting the No button -, the
installation will be terminated.
9. After accepting the License statement, the window below is displayed to
allow you to enter your name, your Company name and the 16-digit License key provided on the back side of the CD-ROM case.
Note 1) If an incorrect 16-digit License code is entered, the program will
display an error message, after which it allows you to re-enter the
number again.
2) If no License code is entered, the program will still be installed, but
it will run only for 30 days after installation. After this 30-day trial
period, you will have to enter the required 16-digit License code in
order to be able to run the program.
10. After entering the information a window will be displayed, allowing you to
verify the entered information before installation commences. If the infor-
45
Installation
Section 3-1
mation is correct, select the Yes button. Selecting the No button will revert
you to the previous window.
11. After entering the correct License code, the installation process will first require you to select the language to be installed for CX-Profibus and its
components. The windows shown below will be displayed, offering the
choice of available languages. Select the desired language package and
press the Next button.
12. You are now required to specify the destination directory for the configurator files. If the default directory shown in the window is acceptable, click the
Next Button. To specify a different directory, click the Browse Button,
specify the desired directory, and click the Next Button. If a new directory
is specified, the software will create it automatically.
46
Installation
Section 3-1
13. Specify a Program Folder to which a shortcut to the program will be added.
The default Program Folder is OMRON\CX-Profibus. You can specify any
one of the other available Program Folders listed in the Existing Folders
frame. After making the desired selection, select the Next button. The installation will now be performed, the files will be copied to the destination
folder and the necessary registry entries will be made...
14. A window is displayed showing the progress of the installation.,
15. After completing the CX-Profibus installation, the setup program will
launch the CX-Server installation. The window shown below will be displayed. Select the Yes button to continue.
16. The CX-Server installation program will detect whether CX-Server has
been installed or not on the PC. If a newer version of CX-Server has been
installed by another CX-Suite application program, the installation of CXServer for CX-Profibus will be skipped. If an older CX-Server version has
been installed, the installation will be performed. The window shown below
47
Installation
Section 3-1
will be displayed, prompting the user for a selection of language to be used
with CX-Server.
17. After selecting the language and pressing the OK button, the welcome and
licence window shown below will be displayed. Please take note of the recommendations, and make sure all other windows programs are closed before continuing.
18. .After pressing the Next button, the user is prompted for the directory in
which to install CX-Server. Press the Next button to continue with the default directory, or the Browse button to select another directory.
19. .Next the user is prompted to select the additional driver software for CXServer. None of these additional drivers are required to accomplish serial
communication between the PC and the PLC CPU. Whether or not to in-
48
Installation
Section 3-1
stall additional components, depends on hardware installed on your PC.
Press the Next button to continue. The installation will now be performed.
20. After completing the installation, a notification will be displayed, allowing
the user to view the CX-Server release notes. Press the Finish button
when donw.
21. Finally, after completing the CX-Server installation, CX-Profibus installation is complete. The window shown below is displayed, to notify the user.
Click the Finish Button to finalize installation and view the readme.txt file
49
Installation
Section 3-1
for CX-Profibus, containing last minute information on the installed program components
22. In order to be ensured of OMRON support for the program as well as information on updates, please fill out the registration card supplied with the
software package and return it to the OMRON regional sales office or to
your local OMRON representative.
3-1-3
Installing the C200HW-PRM21 DTM
The first version of CX-Profibus, i.e. CX-Profibus 1.0 did not include the
C200HW-PRM21. Instead, this component could be downloaded from the
OMRON Internet website. To install the C200HW-PRM21 separately from
CX-Profibus perform the following procedure:
1,2,3...
1. Select from the task bar the Start - Run option and browse for the downloaded setup file, named OMRON C200HW-PRM21 DTM setup.exe.
2. Press the OK button to run the setup and follow the instructions as presented during the installation.
50
CX-Profibus
3-2
3-2-1
Section 3-2
CX-Profibus
Starting CX-Profibus
Starting CX-Profibus
Select Program, OMRON, and CX-Profibus, from the Start Menu if the
default program folder name is used.
At startup, the CX-Profibus splash screen will appear, on top of which a login
window as shown below will be displayed.
Login Window
The Login window provides the selection of the access level as well as the
entry of the password belonging to the access level selected.
Default Password
The default password at the first start up of CX-Profibus is “password” and is
applicable to all access levels. Type in “password” (without the quotes) at the
password entry line and select OK.
!Caution If access limitation to CX-Profibus is required by the application, the password
should be changed as soon as possible. Changing passwords is only possible
on the Administrator level. Refer to Changing the Passwords for an explanation on how to change passwords.
Generating the Device
Catalogue
After entering the correct password, CX-Profibus will start up and open. The
first time CX-Profibus is started, the Device Catalogue will still be empty.
Therefore, the following window will be displayed on top of the CX-Profibus
application window.
Select Yes to generate the Device Catalogue for the first time. This action
may take several minutes depending on the number of installed DTMs.
After updating the Device Catalogue, it will open in the CX-Profibus application window.
51
CX-Profibus
3-2-2
Section 3-2
CX-Profibus Main Window
The main application window of CX-Profibus will open with a New Project.
After the first start up, the Device Catalogue will be opened automatically. If
not, the Device Catalogue may be opened from the menu.
The figure below shows the opened CX-Profibus application window with a
Project already containing a network, and the Device Catalogue window
opened.
Tool Bar
Network view
Device Catalogue
Error Log and FDT Monitoring view
DTM view
Status Bar
The main components in this window are
• The Network view.
• The DTM / Catalogue view.
• The Error Log view.
• The FDT Monitoring view (not shown in the figure above).
• The Main menu.
• The Tool Bar and the Status Bar.
Network view
The Network view displays the structure of the PROFIBUS network in a tree
view format. The tree has at least three levels:
• The Project Level.
• The master level.
• The slave level.
52
CX-Profibus
Section 3-2
The highest level of the tree is the project. The next level is the PROFIBUS
Master level. On this level one or more PROFIBUS Master devices can be
allocated. The third level contains the slave DTMs.
The PROFIBUS network must be assembled in the Network view, i.e. the various DTMs are added to the network via this window. From the Network view
the individual DTM User Interfaces can be opened, and accessed.
CX-Profibus supports context menu in the Network view, which are made visible when selecting a device DTM and right clicking the mouse. The contents
of the menu may depend on the functionality supported by the DTM.
DTM / Device Catalogue
Window
The DTM / Device Catalogue window will hold the Device Catalogue as well
as every opened DTM User Interface. The window is an MDI type window, or
Multiple Document Interface. One or more user interface windows can be
opened, re-sized and moved inside this window.
Error Log view
The Error Log view at the bottom of the CX-Profibus application window displays the error messages reported by DTMs to CX-Profibus. A Time stamp, a
Date stamp and the DTM name are added to the message.
The contents of the window can be cleared, or copied to the clipboard, to
allow pasting it into another document.
The Error Log view is opened by default, when starting CX-Profibus.
FDT Monitoring view
The FDT Monitoring view at the bottom of the CX-Profibus application window
displays the FDT-DTM communication function calls between CX-Profibus
and the DTMs. A Time stamp, a Date stamp, the type of information and the
DTM name are added to the message.
The sequence of messages can be used to troubleshoot problems that may
occur when using third party DTMs in CX-Profibus.
The contents of the window can be cleared, or copied to the clipboard, to
allow pasting it into another document.
The FDT Monitoring view is not opened by default, when starting CX-Profibus.
It can be opened through the View - FDT Monitoring menu option.
Main Menu
Menu
File
The main menu of CX-Profibus, provides all the necessary functionality to
handle a complete project. The table below lists the main menu and their sub
menu items.
Command
Description
CTRL-N
Creates a new Project.
Open
CTRL-O
Opens an existing Project.
Save
CTRL-S
Save As...
Edit
Short Key
New
---
Saves the displayed Project to a file.
The Save as command is the same as Save, but the Filename Specification Window is always displayed.
Export Project to HTML
---
Exports Project data in HTML format and launches the browser.
Project Properties...
---
Opens an edit window to add or edit Project information.
Recently used File List
---
Lists the recently used Project files.
Exit
---
Exits CX-Profibus.
Cut
CTRL-X
Copy
CTRL-C
Copies devices to the clipboard.
Paste
CTRL-V
Copies devices from the clipboard to the cursor position.
Cuts devices and pastes them to the clipboard.
53
CX-Profibus
Section 3-2
Menu
View
Device
Tools
Window
Help
Command
Short Key
Network view
---
Description
Hides or un-hides the Network view.
Device Catalogue
---
Opens or closes the Device Catalogue.
Tool Bar
---
Hides or un-hides the Tool Bar.
Status Bar
---
Hides or un-hides the Status Bar.
Error Logging
---
Hides or un-hides the Error Logging window.
FDT Monitoring
---
Hides or un-hides the FDT Monitoring view.
Add Device...
---
Opens up the Device Catalog Add window, from which devices can be
added to the selected network tree.
Upload Parameters
---
Uploads the parameters from a device to its associated DTM.
Download Parameters
---
Downloads the parameters from DTM to its associated device.
Export to HTML
---
Exports the properties and parameters of the selected DTM, or the network to a HTML file and opens the default browser.
Properties
---
Displays the properties of the selected DTM, or the network.
User Management...
---
Displays the user management (i.e password management) window.
Cascades all open DTM User Interfaces.
Cascade
---
Tile Horizontally
---
Tiles all open DTM User Interfaces horizontally.
Tile Vertically
---
Tiles all open DTM User Interfaces vertically.
Close All
---
Closes all open DTM User Interfaces.
Contents
---
Opens the Help dialog and lists the Help file contents.
Index
---
Opens the Help dialog and lists the Help Index.
About CX-Profibus...
---
Opens the About dialog window for CX-Profibus.
Tool Bar
The tool bar provides quick access buttons to the user for frequently used
menu commands. The table below lists the toolbar buttons.
Icon
Status Bar
Description
Equivalent menu command
Creates a new project.
File-New
Opens an existing project file.
File-Open
Saves the displayed project to a file.
File-Save
Connects the configurator to the selected devices.
Device-Go Online
Downloads the parameters to the device.
Device-Download Parameters
Uploads the parameters from the device.
Device-Upload Parameters
Opens the Device Catalogue.
View-Device Catalogue
The status bar displays the current user role, i.e. the login level.
In case the Error Log view has been closed, the status bar will additionally
display a
symbol to indicate that new errors are available in the Error Log
view. Double-clicking the symbol will open the Error Log view.
54
CX-Profibus
3-2-3
Section 3-2
Device Catalogue
Device Catalogue Main
Components
The Device Catalogue is one of the main components in CX-Profibus. Its
main functions are
• to maintain a list of installed DTM and GSD files.
• to provide convenient sorting and categorizing of the list.
• to allow updating the list, after installation of new DTMs or GSD files.
• to provide detailed information on selected DTMs
The main layout of the Device Catalogue is shown below.
Device name
DTM categories
File date
Version number
Vendor name
Update Device Catalogue
Install a new GSD file
Add selected device to the network
Invoking the Device
Catalogue
The Device Catalogue window is opened by either selecting the
icon in
the CX-Profibus toolbar or by selecting the View - Device Catalogue menu
option. Both options have toggle function: selecting one of them again will
close the Device Catalogue.
DTM view Layout
The left view allows selection of specific groups of DTMs to be displayed. The
right view lists the DTMs, which are installed on the PC and which are available for setting up a network. A selection of DTMs is made by selecting a specific group in the left view.
Note The list makes no distinction between normal DTMs and GSD files which
have been loaded through the Generic Slave Device DTM.
55
CX-Profibus
Section 3-2
DTM List Window
The list items in the right view are described in the following table.
Column
The Device column contains the names of the DTMs, as provided by
the DTM or the GSD file. If the device is defined by a GSD file, the
Generic Slave Device DTM reads out the GSD file entry “Model
Name”. The string provided by this variable is the name displayed in
the list.
Version
The version number defines the revision number of the device. If the
device is defined by a GSD file, the Generic Slave Device DTM reads
out the GSD file entry “Revision”. The string provided by this variable is
the version number displayed in the list.
Date
For DTMs, Date is the date associated with the revision. For GSD file
based slaves, the date listed in this column is the date the GSD file
was last modified.
Vendor
DTM Group Selection
Window
Description
Device
The Vendor name is provided by the DTM or the GSD files.
The left view allows selection of specific groups of device DTMs with common
attributes, e.g. Vendor name, Protocol type etc. If a group is selected, all
device DTMs which belong to that group will be listed in the right view. The
table below lists the possible groups that can be selected.
List item
Device
Types
Vendors
Sub groups, which can be selected are all available vendors. This
information is provided by each DTM. It allows the user to select a
group of devices from one vendor.
Groups
Sub groups are the device types, e.g. digital I/O, analog I/O etc.
Protocols
Note
Description
Sub groups, which can be selected are:
• Communication DTMs, e.g. PROFIBUS Master devices
• Gateways, e.g. to another network type
• Modular devices
• Other devices, e.g. slave devices
Sub groups which can be selected are all the communication protocols
found in the Device Catalogue.
1. The sub groups will be displayed by clicking on the + sign next to each
main group
2. Selecting the main group displays all devices in the group.
Additional DTM
Information
56
In order to obtain more information of a specific DTM, right-click the DTM in
the list, and from the pop-up menu, select DTM Information. This opens a
CX-Profibus
Section 3-2
window with additional DTM information. The figure below provides an example for the CJ1W-PRM21 PROFIBUS Master DTM.
3-2-4
Updating the Device Catalogue
If a new DTM has been installed, it will not automatically be included in the
Device Catalogue. In order to add newly installed DTMs to the list, the Device
Catalogue must be updated by selecting the Update button at the bottom of
the window.
Updating the Device
Catalogue
Updating the Device Catalogue may take some time, depending on the
amount of DTMs installed. A dialogue window with a progress bar will be
shown during the update process. After updating the Device Catalogue, it will
be stored on hard disk. The next time CX-Profibus is started the updated list
will be used.
Installing GSD Files
The Device Catalogue also allows the installation, i.e. copying of new GSD
files into the GSD directory for the Generic Slave Device DTM. Selecting the
Install GSD Files... button displays the standard Windows File selection window. After selecting the GSD file, and selecting the Open button in the File
selection window, the GSD file will be copied to the GSD file directory under
CX-Profibus.
After copying the GSD file, a warning window will be displayed, indicating that
the Device Catalogue needs to be updated. This can be accomplished by
selecting the Yes button in the warning window.
Note
1. Updating the Device Catalog after copying GSD file can only be done if
there is a new project opened, i.e. with no DTMs allocated to the network.
This is to prevent corruption of an existing network in case a GSD file is
removed or replaced.
2. The Install GSD Files... option allows installation of more than one file at
the same time.
3-2-5
Adding Devices to the Network
Setting up a network in CX-Profibus involves adding and configuring single
device DTMs. The device DTMs as listed in the Device Catalogue can be
added to the network in three ways:
• Using the context menu
A context menu will pop up when selecting the CS1/CJ1W-PRM21
57
CX-Profibus
Section 3-2
PROFIBUS Master DTM and right clicking the mouse. By selecting the
menu option Add Device, a simplified Device Catalogue is displayed,
allowing only a selection of DTMs which can be added to the PROFIBUS
Master DTM.
• Using the Drag & Drop function
A Device DTM listed in the standard Device Catalogue window can be
dragged and dropped from the Device Catalogue to a desired position in
the Network view.
• Using the Add Device button
A device DTM selected in the Device Catalogue can be added to a
selected Master DTM in the Network view by clicking the Add Device button in the Device Catalogue window.
3-2-6
Saving and Opening Projects
A project, containing various DTMs can be saved and opened to and from
hard disk. Saving a project file is accomplished by selecting the File - Save or
File - Save As... menu option. This will display the standard Windows File
selection window, allowing the user to enter a file name.
The Project File is saved with the extension *.CPR.
Saving the data is initiated from CX-Profibus, but every DTM must support the
save function as well. The settings of each DTM are added to the Project file
by the DTM itself.
A Project file can be opened using the File - Open menu option. This will
open the standard Windows File selection window, after which the Project file
can be selected and opened.
Note When opening a Project file, the network tree view is constructed. However,
for performance reasons, the DTMs are not directly instantiated. The advantage is that the tree view is constructed fast, but opening a DTM from the tree
view may take longer, depending on the performance of the PC used.
A Project File can also be opened from Windows Explorer. Double-clicking a
file with the extension *.CPR will invoke CX-Profibus and open the selected
file.
3-2-7
Exporting to HTML
CX-Profibus provides automatic generation of project documentation upon
command of the user. The documentation is generated in HTML format, and
can cover either single DTMs or the whole project. After generation of the
HTML document, it will automatically launch the default Internet browser, to
display the result.
Exporting Project to HTML
Exporting the project information to HTML can be achieved in two ways.
• Select the main menu File - Export Project as HTML option.
A window will pop up displaying the progress of the export process.
• select Export to HTML option from the context menu
First select the project level in the Network view, then right click the
mouse to display the context menu. A window will pop up displaying the
progress of the export process.
58
CX-Profibus
Section 3-2
After exporting the information, the default browser is launched, showing the
result of the export process. Links are available to open the information pages
for the individual DTMs.
The extent of the information made available depends on the individual
DTMs. This can range from device type and version information up to all settings and selections made for the device.
Exporting DTM
Information to HTML
1,2,3...
Exporting single DTM information to HTML is achieved by the following
sequence.
1. Select the DTM in the Network view.
2. Right click the mouse to bring up the context menu.
3. Select the Export to HTML option from the context menu.
A window will pop up displaying the progress of the export process. When finished, CX-Profibus will launch the default browser to display the result. In this
case however, no links will be available to other DTMs in the network.
3-2-8
Error Logging and FDT Monitoring
CX-Profibus provides two logging windows at the bottom of the application
window. Both windows are used for displaying events.
Error Log view
The Error Log view displays error messages reported by the DTMs and by the
CX-Profibus FDT container application. All messages include the Time and
Date of occurrence, as well as the DTM Name, as shown in the Network view.
Purpose of the Error Log
The purpose of the Error Log view is error reporting as well as troubleshooting. The contents of the window can be copied to the clipboard, to allow it to
be pasted into another document or into an E-mail. The errors themselves as
well as the sequence of errors may hold additional clues in case of problems.
Error Log Format
The format used in the Error Log view is
Time: <Time> Date: <Date> - <DTM name> <message>
The message displayed, originates from the DTM in which the error occurred.
The figure below shows an example of an error message sequence. This
example sequence is generated after attempting to change a slave address to
that of another slave already assigned to the same Master Unit.
By right-clicking the mouse cursor in the Error Log view, a context menu is
displayed. This context menu provides the options listed below.
59
CX-Profibus
Section 3-2
Error Log view Context Menu
Menu item
Clear all entries
Description
Clears the entire Error Log view.
Equivalent menu command
---
Copy to clipboard
Copies the entire contents of the Error Log view to the clipboard.
---
Hide
Hides the Error Log view.
View - Error Logging
FDT Monitoring view
The FDT Monitoring view displays the communication between the FDT Container application (i.e. CX-Profibus) and any of the DTMs. The communication
is listed as a sequence of function calls from the CX-Profibus to a DTM and
vice versa.
Note The FDT Monitoring view is hidden by default. After starting CX-Profibus, the
window will be displayed, by selecting the View - FDT Monitoring option from
the main menu.
The purpose of the FDT Monitoring view is troubleshooting in case problems
occur with third party DTMs. The contents of the window can be copied to the
clipboard, to allow it to be pasted into another document or into an E-mail.
The messages themselves as well as the sequence of messages may hold
additional clues in case of problems.
The format used in the FDT Monitoring view is
Time: <Time> Date: <Date> - <Information Type> <message>
The message may include the name of the DTM involved in the communication.
The figure below shows an example of an FDT Monitoring message
sequence. This example sequence is generated when opening a CJ1WPRM21 PROFIBUS Master Unit DTM.
By right-clicking the mouse cursor in the FDT Monitoring view, a context
menu is displayed. This context menu provides the options listed below.
FDT Monitoring view Context Menu
Menu item
Description
Equivalent menu command
Clear all entries
Clears the entire FDT Monitoring view.
---
Copy to clipboard
Copies the entire contents of the FDT Monitoring view to the clipboard.
---
Hide
Hides the FDT Monitoring view.
View - FDT Monitoring
60
CX-Profibus
3-2-9
Section 3-2
Access Control and User Management
The FDT Standard defines four access levels and two attributes for FDT Container applications, which can be used to restrict access to the program or
certain features thereof for unauthorized personnel. The actual use of the
restrictions also depends on the application.
CX-Profibus implements the four levels as well as one of the attributes. These
levels are listed below.
• Observer
• Operator
• Maintenance
• Planning Engineer
• Administrator
The access rights per level are defined in the table below.
Observer
Operator
Maintenance
Planning
Engineer
Administrator
New file
Allowed
Allowed
Allowed
Allowed
Allowed
Open file
Allowed
Allowed
Allowed
Allowed
Allowed
Save File
Not allowed
Not allowed
Not Allowed
Allowed
Allowed
Save As...
Not allowed
Not allowed
Allowed
Allowed
Allowed
Properties
View only
View only
Edit
Edit
Edit
Allowed
Export to HTML
Allowed
Allowed
Allowed
Allowed
Open
Allowed
Allowed
Allowed
Allowed
Allowed
Add GSD files
Not allowed
Not allowed
Not allowed
Allowed
Allowed
Update
Not allowed
Not allowed
Not allowed
Allowed
Allowed
Allowed
Allowed
Allowed
Allowed
Allowed
Master settings
View only
View only
Edit
Edit
Edit
View only
View only
Edit
Edit
Edit
Go online
Allowed
Allowed
Allowed
Allowed
Allowed
Monitoring
Allowed
Allowed
Allowed
Allowed
Allowed
Change state and
send commands
Not allowed
Not allowed
Allowed
Allowed
Allowed
Communication
settings
Export to HTML
Allowed
Allowed
Allowed
Allowed
Allowed
Properties
View only
View only
Edit
Edit
Edit
Open
Allowed
Allowed
Allowed
Allowed
Allowed
Device settings
View only
View only
Edit
Edit
Edit
Go online
Allowed
Allowed
Allowed
Allowed
Allowed
Monitoring
Allowed
Allowed
Allowed
Allowed
Allowed
Add DTMs
Not allowed
Not allowed
Not allowed
Allowed
Allowed
Allowed
User
Network
Management
PROFIBUS Master DTM
Open
Generic
Slave DTM
Device
Project File
Catalogue access
Function
Delete DTMs
Not allowed
Not allowed
Not allowed
Allowed
Properties
View only
View only
Edit
Edit
Edit
Export to HTML
Allowed
Allowed
Allowed
Allowed
Allowed
Change password
Not allowed
Not allowed
Not allowed
Not allowed
Allowed
61
CX-Profibus
Section 3-2
User Management
To change access rights or to change the passwords for the various access
levels, first login into the Administrator level. This allows you to select the
Tools - User Management option from the main menu in CX-Profibus. Other
access levels do not have access to this menu option. The selection opens
the User Accounts window, as shown below.
Changing Access Rights
By selecting the check box next to a level, the Administrator can grant access
rights to CX-Profibus, i.e. the checked levels can start and access CX-Profibus. If a check box is not selected, the corresponding level can not be used to
start CX-Profibus, and it will not appear in the drop down list in the login window.
For example, in the window below the Observer and Maintenance levels are
unchecked.
The next time CX-Profibus is started, the Observer and Maintenance access
levels are not available in the login window, as shown below.
The Administrator level has always access and can not be disabled in the
User Accounts window.
Changing the Passwords
62
In order to change a specific password, select the Change password button
in the User Account window, next to the related access level. The level must
be enabled by selecting the check box to the left of it. Pressing the Change
password button opens a window allowing the entry of a new password. As
an example the window below shows the Change password window for the
CS1/CJ1W-PRM21 PROFIBUS Master DTM
Section 3-3
Planning Engineer. You can now enter the new password, confirm it by re-typing the password and select the OK button to activate the new password.
Note If access protection is not important for the application, you can define an
empty string as a password, i.e. when entering the new password, simply
press the return button on your PC. When starting CX-Profibus, the login window can be passed by pressing the return button on your PC, without entering
a password.
3-3
CS1/CJ1W-PRM21 PROFIBUS Master DTM
CS1/CJ1W-PRM21 Master
DTM
To allow configuration and data monitoring from within CX-Profibus two CS1/
CJ1 PROFIBUS Master DTMs are installed, together with CX-Profibus. Each
DTM shows up in the Device Catalogue under two different names.
DTM Name
CS1W-PRM21 PROFIBUS Master
CJ1W-PRM21 PROFIBUS Master
CS1W-PRM21 PROFIBUS DP-V1 Master
CS1W-PRM21 PROFIBUS DP-V1 Master
Functions
• I/O Configuration of PROFIBUS DP
and PROFIBUS DP-V1 master Units
• Monitoring of PROFIBUS DP and
PROFIBUS DP-V1 master Units
• I/O Configuration of PROFIBUS DP
and PROFIBUS DP-V1 master Units
• Monitoring of PROFIBUS DP and
PROFIBUS DP-V1 master Units
• Provide an Acyclic communication
channel with PROFIBUS DP-V1
slave devices.
The PROFIBUS Master DTM has two main user interface components.
• DTM Configuration User Interface
This user interface facilitates configuration of the Master Unit.
• DTM Diagnostics User Interface
The DTM Diagnostics User Interface facilitates Unit status determination,
slave status determination and changing the Unit’s PROFIBUS operational mode.
This section provides an overview of the PROFIBUS Master DTM, and discusses both user interfaces.
3-3-1
Configuration User Interface
Opening the
Configuration DTM
The configuration DTM is opened by
• Selecting the Master DTM in the Network view, and double-clicking the
left mouse button.
• Selecting the Master DTM in the Network view, and right-clicking the
mouse. From the context menu, select Configuration. The Master DTM
Configuration User Interface, which is displayed in the CX-Profibus DTM
view is shown below.
63
CS1/CJ1W-PRM21 PROFIBUS Master DTM
Section 3-3
Note The Configuration User Interface for each of the two CS1/CJ1 PROFIBUS
Master DTMs contains the same views and setting options.t
Master DTM Configuration
User Interface
The Master DTM Configuration User Interface contains four tabs:
• Device Setup tab
• Master Setup tab
• Bus Parameters tab
• Slave Area tab
The four tabs are discussed below.
Configuration Interface
Buttons
The Master DTM Configuration User Interface contains four general buttons.
They are listed in the table below, together with the action taken when pressing them.
Button
64
Action
OK
Evaluate, and save the changes made (if any) and close the user
interface.
Note If any invalid settings have been made, a warning message
will be displayed, allowing cancellation of the command.
Cancel
Closes the user interface without saving.
Note If any changes were made, a warning message is displayed,
allowing cancellation of the command.
Help
Launch context sensitive Help for the Active tab.
Save
Evaluate changes and save them.
CS1/CJ1W-PRM21 PROFIBUS Master DTM
Section 3-3
!Caution Save in the context of the buttons means that the changes made by the user
are saved in the DTM only, i.e. the changes are not permanently saved in the
Project yet. This is indicated by the asterisk next to the DTM in the Network
view. The next time in the same session the GUI is opened, the changes will
still be there. In order to save the changes permanently, e.g. to hard disk,
Click the File - Save option from the main menu of CX-Profibus.
Device Setup Tab
The Device setup tab (see figure above) provides the controls to achieve
communication between the PC and the PROFIBUS Master Unit. It allows
setting of the unit number to identify it on the PLC system and the device
address to identify it on the PROFIBUS network. It also will invoke the CXServer interface to setup and test the communication between the PC and the
PLC to which the Unit is attached.
The Device Setup tab has the following components.
Settings Box
The Settings box contains the setting the user must make before setting up
the communication and before testing the communication.
Control
Configure Button
Description
Station Address
Address of the Unit in the PROFIBUS network. Default value is
1, but is should be changed if there is already another device
with that number.
Unit Number
This number must be the same as the number selected with the
Unit Number Selector switch on the front of the Unit (refer to
2-3-1 Selecting a unit number). This number is used in the communication between the PC and the PLC to transmit the messages to the targeted PROFIBUS Master Unit
The Configure button invokes the CX-Server communications settings dialog. CX-Server is the driver software, providing the communication functionality between a PC and the PLC CPU. It is the basis for the OMRON’s CX-Suite
programs.
CX-Server is provided with CX-Profibus, but it may already be installed on the
PC, if other programs, for example CX-Programmer have been installed.
Note The CX-Server is designed to manage the communication between the PC
and the PLC and also configure the connected PLC. CX-Server currently supports CS1G-H, CS1H, CS1H-H, CJ1G-H, CJ1H-H CJ1M and CS1G/CJ1G
PLC types.
Section 3-3-3 Connecting to the CS1/CJ1W-PRM21 will provide more details
on how to configure CX-Server.
Test Button
The purpose of the Test button is to test the communication setup, after CXServer has been configured. If the PC and the PLC are connected, selecting
the Test button, will invoke a FINS request message to the PROFIBUS Master
Unit via the PLC, to read its name and firmware version. If the request succeeds, both will be displayed in the Device Information Box.
If the FINS request fails (no response), an error message will be displayed in
the Error Log view. In this case the Firmware version field will revert back to
its default contents, i.e. “--- “.
Device Information Box
The Device Information Box contains information obtained from the PROFIBUS Master Unit, through the communication.
65
CS1/CJ1W-PRM21 PROFIBUS Master DTM
Item
Section 3-3
Description
OMRON Corporation
This is fixed text, indicating the Manufacturer of the PROFIBUS
Master Unit.
Description
This string will contain the name of the Unit, i.e. CJ1W-PRM21
or CS1W-PRM21.
Firmware Version
This string displays the firmware version, currently in the
PROFIBUS Master Unit.
Master Setup Tab
The Master Setup tab contains settings regarding the behaviour of the
PROFIBUS Master Unit itself. The Master Setup tab is shown below.
Action to PLC Mode
Transition Box
The Action to PLC Mode Transition Box defines the behaviour of the Unit on
the PROFIBUS network, in case a PLC mode change occurs. The check
boxes define how the Unit should behave in case the PLC mode is changed
from RUN / MONITOR mode to PROGRAM mode, or vice versa. Refer to
section 1-1-7 Network Operation Modes for more information on PROFIBUS
operational modes.
Change PLC to RUN/
MONITOR Mode
The table below defines the behaviour in case the PLC changes to RUN /
MONITOR mode.
Control
Change PLC to PROGRAM
Mode
66
Description
Keep Current Mode
Unit keeps the current mode if the PLC goes to RUN /
MONITOR mode (e.g. stay in CLEAR mode).
Go to OPERATE Mode
(default setting)
The Unit goes to the OPERATE mode whenever the PLC
goes to the RUN / MONITOR mode.
The table below defines the behaviour in case the PLC changes to PROGRAM mode.
CS1/CJ1W-PRM21 PROFIBUS Master DTM
Control
Auto-CLEAR Box
Description
Keep Current Mode
Unit keeps the current mode if the PLC goes to PROGRAM modem (e.g. stay in OPERATE mode).
Go to CLEAR Mode
(default setting)
The Unit goes to the CLEAR mode whenever the PLC
goes to the PROGRAM mode.
Auto-CLEAR defines the Unit’s behaviour in case an error occurs in one of the
allocated slave devices, which causes it to stop data exchange with the Master Unit. If Auto-CLEAR is enabled, the Unit will automatically transition to the
CLEAR state and force all its allocated slave devices to the ‘safe’ state, i.e. all
outputs are set to 0, using the Global-Control CLEAR command.
Control
Support Box
Section 3-3
Description
Auto-CLEAR Mode ON
Selected Unit transitions to the CLEAR mode in the event
of a network error, e.g. because one or more configured
slaves are not in the Data Exchange mode.
Auto-CLEAR Mode OFF
(default setting)
Selected Unit does not transition to CLEAR mode, but
attempts to re-parameterize the slave device.
The Auto Addressing in the Support Box defines the I/O Mapping process
when adding/removing I/O modules or when editing an existing I/O Mapping.
Refer to section 6-5-2 Mapping I/O Data for more details on I/O mapping.
Control
Description
Auto Addressing enabled I/O data mapping will be done by the Master DTM by allocating the I/O data in ascending order of slave device
address and selected I/O modules. No memory allocation
gaps are left behind.
Auto Addressing
disabled
Bus Parameters Tab
New I/O modules are appended to the existing mapping.
Changed I/O modules will be re-allocated to the end of the
list. Memory allocation gaps can be left behind.
The Bus Parameters tab contains the parameters for the communication on
the PROFIBUS network. The Bus Parameters tab is shown below.
The Bus Parameters are a number of settings which define the communication behaviour and timing on the PROFIBUS network. The Bus Parameters
depend on the selected baud rate, certain slave communication parameters
as well as the number of I/O data bytes exchanged between the Master Unit
and each of the slave devices.
The required combination of Bus Parameters is calculated by the program,
based on the dependencies mentioned above. However, the user can change
selected Bus Parameter manually if the application requires this.
67
CS1/CJ1W-PRM21 PROFIBUS Master DTM
Section 3-3
!Caution Changing the calculated Bus Parameters manually is not recommended, and
should only be performed if this is really necessary. Changing the Bus Parameters to an invalid combination, may result in Unit malfunctioning and unexpected behaviour.
Note When making changes to Bus Parameters, selecting the Optimize buttons,
allows toggling between the optimized values and the changed values.
Selecting an other baud rate after changing parameters, will reset the Bus
Parameters to default values for the new baud rate.
The table below lists the parameters, shown in the Bus Parameter tab.
Item
Description
Baud rate
Defines the transmission rate on the PROFIBUS DP Network. The following baud
rate values are defined by the PROFIBUS DP standard:
• 9.6 kBits/s
• 19.2 kBits/s
• 45.45 kBits/s
• 93.75 kBits/s
• 187.5 kBits/s
• 500 kBits/s
• 1500 kBits/s (default value)
• 3000 kBits/s
• 6000 kBits/s
• 12000 kBits/s
68
Unit
Editable
by User
--
Yes
CS1/CJ1W-PRM21 PROFIBUS Master DTM
Item
Description
Optimize
Section 3-3
Unit
Editable
by User
The Optimize setting defines whether parameters can be changed by the user.
• By Standard
Forces the user to use the default (optimized) settings.
• By User
Makes selected fields editable.
Note 1. If the By User option is selected and changes have been made, it is
still possible to switch between Optimize settings, without the changes
being lost.
2. If the By User option is selected and the baud rate is changed, the parameters will be optimized to the new baud rate.
--
Yes
Slot Time
The maximum time a Master Unit must wait for a response to a request message.
tBIT
Yes
Min. Station Delay
of Responders
The minimum allowed time for a slave device before it will generate a response to
a request message.
tBIT
Yes
Max. Station Delay The maximum allowed time for a slave device to generate a response to a
of Responders
request message.
tBIT
Yes
Quiet Time
tBIT
No
The time a transmitting device must wait after the end of a message frame, before
enabling its receiver.
Setup Time
The time between an event and the necessary reaction.
tBIT
No
Min. Slave Interval
The Minimum Slave Interval defines the poll cycle, i.e. the minimum time between
two consecutive Data_Exchange Cycles to the same slave device. The Minimum
Slave Interval must be smaller than the Target Rotation Time.
tBIT
Yes
Calculated Minimum Slave Interval in milliseconds.
ms
No
Target Rotation
Time
The anticipated time for one token cycle, including allowances for high and low
priority transactions, errors and GAP maintenance. Do not change the value
below the calculated value, to avoid bus communication interruptions.
tBIT
Yes
Max Retry Limit
Maximum number of request transmission retries by this master if a device does
not reply to a request.
--
Yes
Highest Station
Address
The HSA defines the Highest Station Address of Master devices on the network,
of which the Master device will request the FDL status, when updating the active
device list (See GAP Update Factor).
If new slaves are added to the network, this field shows the highest device
address. The Master will periodically check whether new active devices have
been added between its own address and the Highest Station Address. If any
devices are detected, GAP is updated.
Permissible values are in the range of 0 to 126.
--
Yes
GAP Update
Factor
The GAP update factor defines the amount of updates of the active devices (i.e.
Master devices) list times during one token rotation cycle.
To update the list, the Master device will transmit FDL_Status_request messages
to ascending device addresses until it finds a next Master device, or until it
reaches the Highest Station Address (See HSA above).
The GAP Update Factor is fixed to 1.
--
No
Poll Timeout
The maximum time interval that this master device may need for the execution of
a master-master function.
ms
No
Data Control Time
The cycle time in which the master updates its Data Transfer List, in which it
keeps an overview of all slave states. Data Control Time is based on the
Watchdog time TWD: Data Control Time = 7*TWD.
ms
No
Watchdog Control
The Watchdog Control Time defines the time for a slave device to set its outputs
to a fail-safe state, if during that time no communication between the Master
device and that slave device was detected. The Watchdog is automatically set for
all configured slaves, based on the value of TTR.
ms
Yes
69
CS1/CJ1W-PRM21 PROFIBUS Master DTM
Slave Area Tab
Section 3-3
The Slave Area tab displays the mapping of the I/O data from/to the allocated
slave devices on to the PLC memory areas. The mapping can be made automatically, but can also be changed by the user, before downloading.
The Slave Area tab is shown below. Only the Output Allocation tab is shown.
Allocation Areas
The Slave Area allocation tabs define how the I/O data of each of the slave
devices is mapped on to the PLC memory. The Slave area tab contains two
tabs, one for Output Allocation and one for Input Allocation. Each tab contains
an overall module list, showing all the output or input data per slave, along
with the Module names, sizes, data types and start addresses. This data has
been transferred to the Master DTM by each of the allocated slave DTMs. If
no slave devices have been allocated, or configured, the list will be empty.
Module List Box
The Module List Box list contains the following information (refer to figure
above, the table applies to the lists in the Input and Output Allocation tabs).
Column
#Addr.
Index
I/O Mapping Areas
70
Description
Station address on the network, obtained from the slave DTM.
Index number of the I/O module.
Device
Device name, obtained from DTM.
Module
System generated name.
Size
Module data size, unit of type mentioned in next column.
Type
Module data type, e.g. Byte, Word etc.
Addr
Mapped address area in PLC memory. For example: CIO3200,
equals CIO Area, start address 3200.
Each Output/Input Allocation tab also contains two areas on to which the I/O
data can be mapped. The areas will in turn be mapped to the PLC memory.
By default all data is mapped to Area 1, in order of ascending slave device
address.
CS1/CJ1W-PRM21 PROFIBUS Master DTM
Note
Section 3-3
1. When mapping, the modules are copied from the module list to the mapping Area and not moved. This means that the module list acts as a resource for the two Mapping Areas, below the module list.
2. When adding/removing slaves/modules, and Auto Addressing has been
enabled, the modules in the Areas will be remapped. This usually results in
I/O data being re-mapped. Therefore it is recommended to select all slaves
and modules, before setting up the PLC memory mapping configuration.
!Caution The default mapping of areas on to the PLC memory is the same default mapping as used in the CS1/CJ1W-DRM21 Devicenet Master/Slave Unit. Care
should be taken to avoid data overlap, if such a Unit is part of the same PLC
CPU system as the CS1/CJ1W-PRM21 PROFIBUS Master Unit.
Mapping Area Controls
Each mapping Area in the Allocation tab is equipped with four controls and an
information field located below the Area. The controls and information field
are listed and explained in the table below.
Control
Note
Description
Area box
Selects the PLC memory area to which the associated
I/O Area will be mapped. Possible options are:
• Not Used (List must be empty).
• CIO
• DM
• Work
• HR
• EM Bank 0 to 12 (Decimal)
(See Note 1).
Start Address box
In this field the user can enter the start address in the
PLC memory of the mapped data block.
Length box
The length box allows the user to select the number of
visible rows. The minimum and the default value is 100
words. If more than 100 words are configured, the minimum Length value will be that number.
The user can set the Length value to up to 7168 words.
Occupied: field
This field display the actual length of the data block (not
necessarily the same as the amount of data in it). This
length includes both data and any gaps between modules. Gaps may only be there if Auto-Addressing option
in the Master Setup tab is disabled.
(See also Note 2).
Compress button
Pressing the Compress button will compress the Area
list associated with it, i.e. this action will remove all gaps
from the mapping list by moving all mapped I/O modules
as close to the start of the memory area as possible.
(See Notes 3 and 4).
1. If the selected PLC memory area, on to which the data must be mapped is
not supported by the PLC CPU, a warning message will be displayed upon
downloading the configuration.
2. If an invalid setting is made the Occupied length value will change its colour to red, indicating an invalid setting. In addition, a warning message will
be displayed, upon saving the changes. Invalid settings are for example
• The start address and length definitions of the data block will cause it
to exceed the area in the PLC.
• The data mapping of two or more I/O Areas (Output and/or Input) will
be overlapping each other partly or totally in the PLC memory.
71
CS1/CJ1W-PRM21 PROFIBUS Master DTM
Section 3-3
3. The Compress button will be disabled, i.e. grayed out, when Auto-Addressing (see Master Setup Tab on page 66) has been enabled.
4. Before Compressing, the Master DTM will display a warning message
prompting the user for confirmation of the action.
Changing Mapped Data
Allocations
By default, the data is mapped to Area 1 in both the Output and Input Allocation tabs. It is however possible to map a part of the data to the second area in
the same tab. For example, an application may require to store all byte data in
one location and all word data in another.
Moving data mapped in one Area to another Area is done from the module
list. The procedure is as follows.
1,2,3...
1. Find the module which must be mapped to a desired Area in the module
list, and select it.
2. Left-click the module and drag it, while holding the Left mouse button, to
the desired Area. This can be the end of the list or any empty space in the
list in which it will fit (See Note).
3. Release the mouse button. The module data is copied in the desired Area
and appended to the already existing list. The same entry in the other list
is now deleted.
4. Finally, the PLC memory address to which the module is mapped is now
updated in the module list.
Note
1. If Auto-Addressing is enabled (see Master Setup tab in this section), any
empty spaces evolving out of moving of modules to another Area will be
removed by compressing the list. Modules located to a higher address will
be moved to a lower address to fill up the gap.
2. If Auto-Addressing is disabled, compressing the list can be accomplished
by pressing the Compress button, after all modifications to the mapping
have been made.
Additional functions
Two additional functions are provided to the user, via the DTM context menu:
• Slave DTM Address Assignment.
• Set Device Station Address (only available on DTM version 2.xx and for
CS1/CJ1W-PRM21 Unit versions 2.0).
To select these options perform the following steps:
1,2,3...
1. Select the Master DTM in the Network view.
2. Right click the mouse, and select the Additional functions entry from the
context menu.
3. Select the desired function.
72
CS1/CJ1W-PRM21 PROFIBUS Master DTM
Slave DTM Address
Assignment
Section 3-3
Selecting the Slave DTM Address Assignment displays a list of DTMs
assigned to the PROFIBUS Master DTM, together with their Station address:
When assembling the network, the PROFIBUS Master DTM will automatically
assign a station address to each new slave DTM. The purpose of the Slave
DTM Address Assignment function is to allow the user to change the DTM
address of one or more devices, to make it the same as the actual physical
address of the device on the network.
In order to change an address perform the following steps:
1,2,3...
1. Select the slave device in the list.
2. Enter the new address in the field Address in the lower right corner of the
window.
3. Press the Set button. The Status field will display the status of this service.
Set Device Station
Address
The Set Device Station Address function is provided for slave devices of
which the PROFIBUS address is not set through switches, but by using the
PROFIBUS DP Set Slave Address service. Slave devices which support this
service also provide a means to store the address in internal non-volatile
memory. In case this non-volatile memory does not contain an entry, the
slave device will assume the default address 126.
Note
1. The PROFIBUS DP Set Slave Address service is supported by the CS1/
CJ1W-PRM21 Units as of Unit version 2.0.
2. In order to be able to change a device’s address, the CS1/CJ1W-PRM21
PROFIBUS Master DTM must be on-line.
Selecting the Set Device Station Address displays the window shown below:
73
CS1/CJ1W-PRM21 PROFIBUS Master DTM
Section 3-3
In order to change the address of a slave device perform the following steps
(Make sure that the DTM is on-line with the CS1/CJ1W-PRM21 Unit):
1,2,3...
1. Enter the device’s current address and its PROFIBUS Ident Number.
The PROFIBUS Ident Number can be found in the Generic Slave DTM or
through the device’s documentation. By default the device’s current address will be 126. If necessary, change this to the actual current address.
2. Enter the new device address in the New Address field.
3. Optionally, select the Lock checkbox, if the address change must be made
permanent.
4. Press the Set button to invoke the PROFIBUS DP Set Slave Address service. The Status field will display the status of this service.
!WARNING Selecting the Lock option makes any future changes of the address impossible, even after power-down/power-up of the slave device.
Note After successful completion of the address change, the device DTM address
in the Network view has to be changed as well.
3-3-2
Diagnostics User Interface
Diagnostics User Interface
The PROFIBUS Master DTM provides a second user interface, to display the
Diagnostics information available in the PROFIBUS Master Unit. This information concerns
• Unit and PROFIBUS DP Interface status flags.
• Slave status flags and common slave diagnostics.
• The Unit’s Error Log.
Furthermore, the Diagnostics User Interface allows changing the Master’s
PROFIBUS operational mode and the transmission of Global-Control messages.
In order to access the Diagnostics User Interface, the DTM has to be on-line,
i.e. a communication channel between the DTM and the PROFIBUS Master
Unit must have been established.
Opening the DTM
Diagnostics User Interface
1,2,3...
In order to open the DTM Diagnostics User Interface perform the following
sequence.
1. To go on line, perform one of the following actions.
• Select the DTM in the Network view.
• Select the Device - Go Online option from the main menu, or from the
DTM context menu, or
• Select the
button from the Tool Bar.
2. A communication channel will be opened through CX-Server. The name of
the DTM in the Network view, will turn to Italic font, to indicate that the Unit
is on-line.
3. Select the Device - Diagnosis option from the main menu, or from the
DTM context menu. The Diagnostics User Interface will now be displayed.
74
CS1/CJ1W-PRM21 PROFIBUS Master DTM
Section 3-3
The figure below shows an example of the DTM Diagnostics User Interface.
The DTM Diagnostics User Interface contains two tabs:
• The Monitor tab
This tab displays all Master Unit status and error information as well the
overall slave status information, which resides in the Master Unit.
• The Online Operations tab
This tab contains controls to initiate state changes in the Master Unit as
well as transmit Global-Control messages over the PROFIBUS network.
Monitor Tab
The DTM Diagnostics User Interface - Monitor tab contains three sub-tabs:
• Master Status tab.
• Slave Status tab.
• Error History tab.
Also, the Diagnostics data refreshing mode can be selected.
• Automatic
The Diagnostics data is constantly retrieved from the Unit.
• Manual
The Diagnostics data is retrieved only once from the Unit, when pressing
the Manual button.
Master Status Tab
The Master Status tab (shown in the figure above) contains Diagnostics information regarding the Master Status. Each of the four status boxes, is related
to one of the Unit’s status words in the PLC CIO Area Memory (see sections
4-2-3 Unit Status (Word n+4) to 4-2-6 Slave Status (Word n+7)).
The status is indicated by red or green LED indicators. Red indicates an error
situation, green indicates a status indication. The LED indicators are listed in
the table below.
75
CS1/CJ1W-PRM21 PROFIBUS Master DTM
Master Status 2
Master Status 1
LED Indicator
Section 3-3
Description
OPERATE
Master Unit is in OPERATE mode.
STOP
Master Unit is in STOP mode.
CLEAR
Master Unit is in CLEAR mode.
OFFLINE
Master Unit is in OFFLINE mode.
Data Exchange
When set to ON, it indicates that the Master Unit is in Data Exchange with all its
allocated and enabled slave devices.
Auto-Clear enabled
Auto-Clear function has been enabled in the downloaded configuration.
Valid Configuration
The Master Unit contains a valid configuration.
Disturbed Bus error
When turned ON, the Disturbed Bus error indicates that distorted messages
have been received by the Unit. This may occur if the network is not properly
terminated or a cable is used, which is too long for the selected baud rate.
PROFIBUS Protocol Error
When turned ON, the PROFIBUS Protocol Error indicates that an error has
occurred in the protocol handling, e.g. a transmitted token frame could not be
read back. The Master Unit has switched to OFFLINE.
Double Master address Error
Indicates that a second Master with the same address has been detected on the
Bus. The Master Unit has switched to OFFLINE.
Hardware error
When turned ON, the Hardware Error indicates that an error has occurred on
the bus, e.g. message exceeding 256 bytes, broken messages, faulty bus timing, or devices beyond the HSA have been detected. The Master Unit has
switched to OFFLINE.
Mode Command Error
When set to ON, it indicates that two switches in the CIO switch word (see section 4-2-1 Software Switches 1 (Word n)) were set simultaneously.
Parameter error
The Parameter set error indicates if an error has been detected in the contents
of the Parameters set while configuring the PROFIBUS interface, using these
parameters.
Unit Error
A Unit error indicates that a new error has been set in the Unit Status word (see
section 4-2-3 Unit Status (Word n+4)).
Master Error
A Master Error indicates that a new error has been set in the Master Status 2
word (see section 4-2-5 Master Status 2 (Word n+6)).
Slave
Status
Unit Status
Local Parameter Storage Error An error has occurred when storing the configuration to non-volatile memory.
76
Local Parameter Load Error
An error has occurred when loading the configuration from non-volatile memory.
File Read error
When turned ON, this LED indicates that a transfer from Memory Card to the
Unit has failed. The Unit must be re-configured.
Unit Memory error
When turned ON, it indicates that an error has occurred when writing the Error
Log to the Non-volatile memory.
Error Log Updated
The Error Log contains new entries, since the last time it was read or cleared.
Parameter Storage in
Progress
Configuration Parameters are being transferred to or from the Unit.
Slave Diagnostics Received
When turned ON, it indicates that new slave diagnostics have been received.
All Slaves in Data Exchange
When turned ON, it indicates that all slaves are in Data exchange with the Master Unit.
CS1/CJ1W-PRM21 PROFIBUS Master DTM
Section 3-3
Slave Status Tab
The Slave Status tab displays a comprehensive overview of the status of the
allocated slaves. An example of the Slave Status tab is shown below.
LED Indicator Colours
The LED indicators in the Slave Status Flags box, indicate per slave its status,
using colours. Four colours are associated with status conditions. The LED
indicator colours are listed below.
Indicator
Colour
Slave Status
Grey
Associated device does not exchange Diagnostics with this Master
Unit, i.e.
• Slave not allocated to this Master Unit, or
• Device is this Master Unit, or
• Device is another master device.
Red
The slave device is not communicating with the Master Unit. It may
be disconnected, or the Master is in OFFLINE or STOP mode.
Orange
The slave device is communicating with the PROFIBUS Master
Unit, but it is not in Data Exchange, due to incorrect parameter settings. See the slave diagnostics for more information.
Yellow
The slave device is in data exchange with the PROFIBUS Master
Unit, but it has reported diagnostics data. See the slave diagnostics
for more information.
Green
The slave device is in data exchange with the PROFIBUS Master
Unit. No diagnostics reported.
Clear Diagnostics Button
Pressing the Clear Diagnostics button will clear all new diagnostics data
flags in the Unit. If all slaves are in data exchange, pressing the button will
result in all LED indicators turning green.
Retrieving Slave
Diagnostics
Provided that the Master Unit is not in OFFLINE or STOP mode, the diagnostics of a specific slave device can be obtained from the LED indicators. Moving the mouse cursor over the LED, will change the cursor from a normal
77
CS1/CJ1W-PRM21 PROFIBUS Master DTM
Section 3-3
arrow pointer to a hand. Left clicking the mouse will then transmit FINS messages to retrieve the diagnostics data of the specified slave device.
The retrieved information is displayed in the Slave Diagnostics Data area.
The data displayed is the same as displayed with in the Diagnostics User
Interface of the Generic Slave DTM. Refer to section 3-5-2 Diagnostics User
Interface, for an explanation of the LED indicators.
Error History Tab
The Error History tab lists the contents of the Error Log stored in the PROFIBUS Master Unit. The Error History tab is shown below.
The Error Log entries are described in section 7-5-2 Error Codes. Refer to this
section for details.
Clear Button
Pressing the Clear Button, initiates an ERROR LOG CLEAR FINS command.
All error messages in the Unit and the displayed list will be cleared.
Online Operations
Tab
The Online Operations tab is the second main tab in the DTM Diagnostics
User Interface. It contains the necessary controls to
• Switch the Master Unit to PROFIBUS Operational modes
• Select one or more groups, and Global-Control Commands and transmit
Global-Control message over the PROFIBUS network.
78
CS1/CJ1W-PRM21 PROFIBUS Master DTM
Section 3-3
The Online Operations tab is shown below.
PROFIBUS
Communication Group
These buttons can be used to force the Unit to change its operating mode.
The four operational modes are
• OFFLINE mode.
• STOP mode.
• CLEAR mode.
• OPERATE mode.
The mode changes are implemented through FINS messages to the Unit’s
software switches in the CIO Memory Area (see section 4-2-1 Software
Switches 1 (Word n)).
!Caution When initiating a mode change, it may interfere with attempts from the PLC
Program to write to the same software switches. Care should be taken to
avoid these situations.
Global-Control Messages
Global-Control messages (See section 6-6-3 Transmitting Global-Control
Commands) can be initiated by the user from the Online Operations tab. The
user can select the Global-Control commands.
• Freeze.
• Unfreeze.
• Sync.
• UnSync.
All commands can be transmitted independent from each other, i.e. all can be
send at the same time. However, their effects are not independent, as for
example sending Freeze and Unfreeze at the same time results in an
Unfreeze command at the slaves.
79
CS1/CJ1W-PRM21 PROFIBUS Master DTM
Section 3-3
Selecting the Groups
Specific groups to send the Global-Control command to can be defined, by
selecting the appropriate checkbox. Selecting the All Slaves checkbox can
will disable the individual check boxes, and result in a Global-Control command to all slave devices.
Transmit Global-Control
Command
In order to transmit the Global-Control, press the Transmit button. The command will be transmitted only once. Both the Global-Control command contents, group select and the transmit command are transferred to the Unit
through its CIO words (see section 4-2-1 Software Switches 1 (Word n) and
section 4-2-2 Global-Control Message (Word n+2)).
!Caution When transmitting a Global-Control command, it may interfere with attempts
from the PLC Program to write to the same software switches. Care should be
taken to avoid these situations.
3-3-3
Connecting to the CS1/CJ1W-PRM21
Configuring
Communication
The PROFIBUS Master DTM uses CX-Server to connect to the Unit for both
downloading a configuration as well as monitoring the Master Unit. To setup
the communication to the Unit, perform the following procedure.
1,2,3...
1. Open the Master DTM Configuration Interface, Device Setup tab (see section 3-3-1 Configuration User Interface).
2. Select the Unit Number. It must match the unit number set on the PROFIBUS Master Unit, through the rotary switch on the front.
3. Select the Configure button to start CX-Server.
CX-Server
Up on pressing the Configure button, CX-Server is launched and displays the
CX-Server User Interface as shown below.
Configuring CX-Server
In order to configure CX-Server for communication with the Unit, perform the
following procedure.
1,2,3...
80
1. Select the type of PLC to which the Unit is attached, from the Device Type
drop down selection box.
CS1/CJ1W-PRM21 PROFIBUS Master DTM
Section 3-3
2. Press the Settings button next to the PLC type selected. The PLC settings
window (see figure below) is displayed.
3. In this window make the proper adjustments if necessary. The selections
made, must match the physical configuration of the PLC system. When
done, press the OK button.
4. Select the Network Type to be used as connection between the PC and
the Unit. The available options may include other PLC systems or Communication Units, which are setup to act as a gateway. Refer to CX-Server
Runtime User Manual (W391) for details on configuring CX-Server.
Note 1) For further explanation, only the direct connections between the
PC and the PLC on which the Unit is attached are considered.
These include ToolBus and SYSMAC WAY.
2) Select the Settings button next to the Network Type selected, to
display the Network settings window, and select the Driver tab
(Toolbus is shown as example below).
5. Make the necessary selections to facilitate communication between the
PC and the PLC CPU to which the PROFIBUS Master Unit is attached, and
press the OK button.
Testing CX-Server Setup
After making the settings, press the OK button to close the CX-Server interface. In order to verify that the communication has been setup correctly, press
the Test button in the Device Setup tab of the DTM Configuration User Inter-
81
CS1/CJ1W-PRM21 PROFIBUS Master DTM
Section 3-3
face. This will initiate a FINS command to read the Unit’s profile, i.e. the name
of the Unit and the firmware version.
If the communication has been setup correctly, the response of the FINS
command will yield the required information, which will be displayed in the
Device Information box, in the Description and Firmware Version fields. If
the communication is not setup correctly, the two fields will contain three
dashes, i.e. “---”, and an Error message will be displayed in the Error Log view
of CX-Profibus. The communication settings must be changed to the correct
value first.
When CX-Server has been setup correctly, it can be used for
• Configuration download
• Monitoring purposes
Note Since CX-Server is the common driver software for connection between PCbased CX- programs (e.g. CX-Programmer, CX-Supervisor, etc.) and the
CS1/CJ1-series PLC, all these programs can communicate simultaneously
with the PLC. However, the settings for CX-Server made through each of
these programs have to be exactly the same, to allow simultaneous communication.
Downloading Parameters
1,2,3...
In order to download the parameter sets to the PROFIBUS Master Unit, perform the following sequence.
1. Select the DTM in the Network view and right-click the mouse to display
the context menu.
2. Select Download Parameters from the menu, to initiate a download. A
communication channel through CX-Server will be opened automatically.
Alternatively, the following can be done.
1. Select the DTM in the Network view and press the Download button in the
toolbar to start the download process.
Monitoring
For monitoring, an online connection with the Unit must be made first. To
achieve this perform the following sequence.
1,2,3...
1. To go on line, perform one of the following actions.
• Select the DTM in the Network view.
• Select the Device - Go Online option from the main menu, or the DTM
context menu, or
• Select the
button from the Tool Bar.
2. A communication channel will be opened through CX-Server. The name of
the DTM in the Network view, will turn to Italic font, to indicate that the Unit
is on-line.
3. From the context menu, select the Diagnosis option. The DTM’s Diagnostics User Interface will be displayed.
82
C200HW-PRM21 PROFIBUS DP Master DTM
3-4
Section 3-4
C200HW-PRM21 PROFIBUS DP Master DTM
C200HW-PRM21 Master
DTM
To allow configuration and data monitoring for a C200HW-PRM21 from within
CX-Profibus a C200HW-PRM21 PROFIBUS DP Master DTM is available,
which can be operated from CX-Profibus.
The C200HW-PRM21 PROFIBUS DP Master DTM has two main user interface components.
• DTM Configuration User Interface
This user interface facilitates configuration of the Master Unit.
• DTM Diagnostics User Interface
The DTM Diagnostics User Interface facilitates Unit status determination,
and the slave status determination.
This section provides an overview of the C200HW-PRM21 PROFIBUS DP
Master DTM, and discusses both user interfaces.
3-4-1
Configuration User Interface
The configuration DTM is opened by
• Selecting the C200HW-PRM21 Master DTM in the Network view, and
double-clicking the left mouse button.
• Selecting the Master DTM in the Network view, and right-clicking the
mouse. From the context menu, select Configuration.
The Master DTM Configuration User Interface, which is displayed in the CXProfibus DTM view is shown below.
Master DTM Configuration
User Interface
The Master DTM Configuration User Interface consist of two tabs:
• Bus Parameters tab
• Address Table tab
The two tabs are discussed below.
83
C200HW-PRM21 PROFIBUS DP Master DTM
Configuration Interface
Buttons
Section 3-4
The Master DTM Configuration User Interface contains four general buttons.
They are listed in the table below, together with the action taken when pressing them.
Button
Action
OK
Evaluate, and save the changes made (if any) and close the user
interface.
Note If any invalid settings have been made, a warning message
will be displayed, allowing cancellation of the command.
Cancel
Closes the user interface without saving.
Note If any changes were made, a warning message is displayed,
allowing cancellation of the command.
Apply
Evaluate, and save the changes made (if any).
Note If any invalid settings have been made, a warning message
will be displayed, allowing cancellation of the command.
Help
Launch context sensitive Help for the Active tab.
!Caution Saving the changes in the context of the buttons means that the changes
made by the user are saved in the DTM only, i.e. the changes are not permanently saved in the Project yet. This is indicated by the asterisk next to the
DTM in the Network view. The next time in the same session the GUI is
opened, the changes will still be there. In order to save the changes permanently, e.g. to hard disk, Click the File - Save option from the main menu of
CX-Profibus.
Bus Parameters Tab
The Bus Parameters tab contains the parameters for the communication on
the PROFIBUS network. The Bus Parameters tab is shown below.
The Bus Parameters are settings, which define the communication behaviour
and timing on the PROFIBUS network. The Bus Parameters depend on the
selected baud rate, slave communication parameters as well as the number
of I/O data bytes exchanged between the Master Unit and each of the slave
devices.
84
C200HW-PRM21 PROFIBUS DP Master DTM
Section 3-4
The required combination of Bus Parameters is calculated by the program,
based on the dependencies mentioned above. However, the user can change
selected Bus Parameter manually if the application requires this.
!Caution Changing the calculated Bus Parameters manually is not recommended, and
should only be performed if this is really necessary. Changing the Bus Parameters to an invalid combination, may result in Unit malfunctioning and unexpected behaviour.
Note The bus parameter calculations as performed by the C200HW-PRM21 DTM
will differ from the calculations performed by the predecessor program
Sycondp, due to updated insights in bus calculation algorithms.
The table below lists the parameters, shown in the Bus Parameter tab.
Item
Description
Unit
Editable
by User
Profile
Provides pre-selected settings for either a PROFIBUS DP or a PROFIBUS PA
network. The following selections are possible from the drop-down list:
• PROFIBUS DP (Default bit-rate: 1500 kbit/s)
• PROFIBUS PA (Default bit-rate: 93.75 kbit/s)
--
Yes
Baud rate
Defines the transmission rate on the PROFIBUS DP Network. The following baud
rate values are defined by the PROFIBUS DP standard:
• 9.6 kBits/s
• 19.2 kBits/s
• 93.75 kBits/s
• 187.5 kBits/s
• 500 kBits/s
• 1500 kBits/s (default value)
• 3000 kBits/s
• 6000 kBits/s
• 12000 kBits/s
--
Yes
Slot Time
The maximum time a Master Unit must wait for a response to a request message.
tBIT
Yes
Min. Station Delay
of Responders
The minimum allowed time for a slave device before it will generate a response to
a request message.
tBIT
Yes
Max. Station Delay The maximum allowed time for a slave device to generate a response to a
of Responders
request message.
tBIT
Yes
Quiet Time
The time a transmitting device must wait after the end of a message frame, before
enabling its receiver.
tBIT
Yes
Setup Time
The time between an event and the necessary reaction.
tBIT
Yes
Station Address
This value defines the device address of the C200HW-PRM21 PROFIBUS DP
Master unit. Permissible values are in the range of 0 to 125.
An attempt to change the address in to a value which is already occupied will
result in an error message.
Target Rotation
Time
The anticipated time for one token cycle, including allowances for high and low
priority transactions, errors and GAP maintenance.
tBIT
Yes
Token Rotation Time in ms.
ms
No
--
Yes
GAP Update
Factor
The GAP update factor defines the amount of updates of the active devices (i.e.
Master devices) list times during one token rotation cycle.
To update the list, the Master device will transmit FDL_Status_request messages
to ascending device addresses until it finds a next Master device, or until it
reaches the Highest Station Address (See HSA below).
Permissible values are in the range of 0 to 255.
85
C200HW-PRM21 PROFIBUS DP Master DTM
Item
Description
Max Retry Limit
Section 3-4
Unit
Editable
by User
Maximum number of request transmission retries by this master if a device does
not reply to a request.
--
Yes
Highest Station
Address
The HSA defines the Highest Station Address of Master devices on the network,
of which the Master device will request the FDL status, when updating the active
device list (See GAP Update Factor).
If new slaves are added to the network, this field shows the highest device
address.The Master will periodically check whether new active devices have
been added between its own address and the Highest Station Address.
Permissible values are in the range of 0 to 126.
--
Yes
Data Control Time
The cycle time in which the master updates its Data Transfer List, in which it
keeps an overview of all slave states. Data Control Time is based on the
Watchdog time TWD: Data Control Time = 6*TWD.
ms
Yes
Min. Slave Interval
The Minimum Slave Interval defines the poll cycle, i.e. the minimum time between
two consecutive Data_Exchange Cycles to the same slave device. The Minimum
Slave Interval must be smaller than the Target Rotation Time.
µs
Yes
Watchdog Control
Override slave specific Watchdog control time.
This setting - when selected - allows the user to set one Watchdog Control Time
for the whole network and override the Watchdog Control Time provided by the
Slave DTM.
--
Yes
The Watchdog Control Time defines the time for a slave device to set its outputs
to a fail-safe state, if during that time no communication between the Master
device and that slave device was detected. The Watchdog is automatically set for
all configured slaves, based on the value of TTR.
ms
Calculated Timing
The Calculated Timing is the time that the Sender spends at idle after the receipt
of the last Bit of a telegram on the Bus, until the first Bit of a new telegram is sent
on the Bus.
These values are calculated by the DTM and only displayed for information
purposes.
tBIT
No
Auto-Clear ON
When selected, the Unit transitions to the CLEAR mode in the event of a network
error, e.g. because one or more configured slaves are not in the Data Exchange
mode.
--
Yes
Adjusting Bus Parameters
If the bus configuration is changed and these changes have effects on the
Bus Parameters, a note symbol ! appears next to the concerned parameters of which displayed values are not longer valid. Usually in these cases the
displayed values are too small and will eventually lead to communication
problems.
The marked parameters need to be recalculated, which can be accomplished
by pressing the Adjust button at the bottom right of the Bus Parameter tab.
After re-calculation the note symbol will disappear.
Note In case of large networks, it may be required to increase the Watchdog time to
allow the network to become fully operational.
Address Table Tab
The Address Table tab displays the mapping of the I/O data from/to the allocated slave devices on to the internal I/O memory of the Unit. The mapping
can be made automatically, but can also be changed by the user, before
downloading.
The Address Table tab is shown below, containing example data.
86
C200HW-PRM21 PROFIBUS DP Master DTM
Section 3-4
Note The mapping in the Address Table tab does not define the mapping on to the
PLC memory areas. This is done by making the appropriate settings in the
unit’s DM areas (see Appendix G-2 Word allocations).
Address Table Tab
The Address Table tab contains an overall module list, showing all input and
output data per slave, along with the Module names, sizes, data types and
start addresses. This data has been obtained by the Master DTM by each of
the allocated slave DTMs. If no slave devices have been allocated, or configured, the list will be empty.
Memory Layout
The Memory Layout box list contains the following information.
Column
#Addr.
Device Name
Module Name
IType
IAddr (Word)
OType
OAddr (Word)
Note
Description
Station address on the network, obtained from the slave DTM.
Device name, obtained from DTM.
System generated name.
Defines the Type of the Input:
• IB: Input Byte type
• IW: Input Word type
Start Address of the Input data of the Module, relative to the start
of the internal memory of the Unit, containing the Input Data block.
IAddr is expressed in Words.
Defines the Type of the Output:
• QB: Output Byte type
• QW: Output Word type
Start Address of the Output data of the Module, relative to the start
of the internal memory of the Unit, containing the Output Data
block. OAddr is expressed in Words.
1. Modules consisting of one single byte will occupy a full word address.
2. A total of up to 512 Input bytes and 512 Output bytes can be mapped on
to the Unit’s internal memory. Therefore, the maximum permissible address value is 255 (Words). However, the C200HW-PRM21 to PLC memory mapping is limited to a total of 300 I/O Words.
87
C200HW-PRM21 PROFIBUS DP Master DTM
Section 3-4
Address Table Tab
Controls
The Address Table Tab contains three controls, related to the I/O mapping.
The controls are discussed below.
Enable Auto Addressing
The C200HW-PRM21 DTM provides Auto Addressing to facilitate easy mapping of I/O Modules. When enabled, the I/O Modules are mapped in ascending station address order, while preserving the Module sequence as selected
per Slave DTM.
This means that when a new module is added for a particular slave device,
the new module will be inserted in the already mapped I/O Modules right after
the previous module of the same slave device. The consecutive modules,
which were already mapped will move to higher addresses.
Changing Mapped
Addresses
In case Auto Addressing is not enabled, the user is allowed to change individual mapped addresses by first double-clicking the left mouse button on the
mapped address, after which the address can be manually changed. The
change will take effect, when selecting either the OK or the Apply button.
Note
1. In case a changed address overlaps another address in the I/O Mapping,
a warning message will be displayed indicating the location of the overlap.
The overlap is however not automatically corrected.
2. In case the entered mapping address is located outside the range of internal memory (e.g. an input address of 256 or higher), an error message is
displayed and the change is reverted.
3. Enabling Auto-Addressing again will result in all changes being lost. When
enabling Auto-Addressing, a Warning message will be displayed, notifying
the user of these consequences.
Sorting the Displayed
Modules
The I/O Modules list can be sorted for more convenient views. Two options
are available:
• Sort by station address
Sorting by station address groups all I/O modules for each slave device
together. This view is more convenient in case Auto Addressing is
enabled.
• Sort by data address
Sorting by data address lists the I/O Modules in ascending order, Input
data first. This view is more convenient in case Auto Addressing is disabled and addresses have been changed manually.
3-4-2
Diagnostics User Interface
Diagnostics User Interface
The C200HW-PRM21 PROFIBUS DP Master DTM provides a second user
interface, to display the Diagnostics information available in the Unit. This
information concerns
• Unit and PROFIBUS DP Interface status flags.
• Slave status flags.
In order to access the Diagnostics User Interface, the DTM has to be on-line,
i.e. a communication channel between the DTM and the PROFIBUS DP Master Unit must have been established.
Opening the DTM
Diagnostics User Interface
1,2,3...
In order to open the DTM Diagnostics User Interface perform the following
sequence.
1. To go on line, perform one of the following actions.
• Select the DTM in the Network view.
88
C200HW-PRM21 PROFIBUS DP Master DTM
Section 3-4
• Select the Device - Go Online option from the main menu, or from the
DTM context menu, or
• Select the
button from the Tool Bar.
2. A communication channel will be opened through the CIF driver, provided
this driver has been assigned to the DTM. Refer to section 3-4-3 Connecting to the C200HW-PRM21 on how to assign this driver. After going on line
The name of the DTM in the Network view, will turn to Italic font, to indicate
that the Unit is on-line.
3. Select the Device - Diagnosis option from the main menu, or from the
DTM context menu. The Diagnostics User Interface will now be displayed.
The figure below shows an example of the DTM Diagnostics User Interface.
The C200HW-PRM21 DTM Diagnostics User Interface contains five fields of
information. These fields are described in the table below.
Master Operation
Mode
LED Indicator /
Information Field
Description
Operate
Master Unit is in OPERATE mode, i.e. the Master Unit exchanges I/O data with
its slave devices.
Clear
Master Unit is in CLEAR mode, i.e the Master Unit reads input data from the
assigned slave devices, but it sends zeros as output data to the slave devices.
Stop
Master Unit is in STOP mode, i.e. the Master Unit may only communicate with
other Master devices and not with the assigned slave devices.
Offline
Master Unit is in OFFLINE mode, and not active on the PROFIBUS network.
89
C200HW-PRM21 PROFIBUS DP Master DTM
Station Error
--
90
Description
Timeout
This indicator will be set to ON, when due to the number of rejected PROFIBUS
messages, the Master supervisory timeout has expired. This usually indicates a
short-circuit in the PROFIBUS network. The amount of timeout events is displayed in the Bus Monitoring field.
The indicator will be set to ON upon the first occurrence of the timeout. It will not
be reset, until power-down.
Not Ready
The Not Ready notification indicates that the application program has not
started or it has stopped the PROFIBUS DP Master. If this bit is set, the application is not ready to receive data.
Auto-Clear
Set to ON indicates that an Auto-Clear event has occurred, i.e. data exchange
with at least one of the slave devices has stopped. The Master Unit has been
switched to CLEAR mode.
Slave Error
When set to ON, it indicates that at least one of the slaves has encountered an
error and is not exchanging I/O data with the Master unit. Refer to the LED indicators in the Station status field to determine which slave devices encountered
the error.
Fatal Error
A Fatal Error has occurred in the PROFIBUS DP Master Unit, due to the large
amount of network errors. No further bus communication is possible.
Control Error
The Control Error indicates that an error has been encountered in the downloaded parameter set. No communication is possible.
Error Event
When set to ON, The Error Event indicates that the device has detected network
short circuits. The number of detected events is displayed in the Short Circuit
Counter. The bit will be set up on the first detected event and will not be reset,
until power-down or reset of the PROFIBUS DP Master Unit.
Short Circuit Counter
The Short Circuit Counter displays the number of short circuit error events on
the PROFIBUS network, which were detected by the Master Unit.
Range of Value: 0 to 65535
Transmission Rejected Count
The Transmissions Rejected Count displays the number of rejected messages.
A possible reason for this is, that the Master itself can not receive the token anymore.
Range of Value: 0 to 65535
Any Slave Indicator
The LED indicators in the Station status field display the status of each slave
station on the network per address. The colour of the LED indicator indicates the
specific status of the slave device:
• Grey:
The slave device is not configured for this Master Unit.
• Green:
This slave device is exchanging I/O data with the Master Unit.
• Yellow:
New Diagnostic is available from this slave device. Open the Slave
DTM to determine the actual Diagnostics data. Opening this DTM
will clear the LED indicator, and turn to another colour until the
next Diagnostics message is received from the specified slave
device.
• Blue:
The slave device was configured, but not found on the network.
• Red:
The slave station has returned a Set_Prm or Chk_Cfg error and is
not in data exchange with the Master unit.
Station Address
The Station address field displays the address of the first slave device (i.e. with
the lowest address) which reported an error. The error is specified in the Error
Event field.
Error Event
The Error Event field displays the error which occurred during communication
between the master unit and the slave device as specified in the Station
Address field.
Connected
When set to ON, this LED indicates that the C200HW-PRM21 DTM is online
and exchanging data with the C200HW-PRM21 PROFIBUS DP Master unit.
Station status
Bus Monitoring
Station Status
LED Indicator /
Information Field
Section 3-4
C200HW-PRM21 PROFIBUS DP Master DTM
3-4-3
Section 3-4
Connecting to the C200HW-PRM21
Configuring
Communication
For the purpose of downloading a configuration as well as monitoring the
C200HW-PRM21 PROFIBUS DP Master DTM uses a dedicated serial driver
to connect to the Unit through one of the serial ports on the PC. To setup this
driver for communication to the Unit, perform the following procedure.
1,2,3...
1. Open the device’s context menu by
• Selecting the C200HW-PRM21 Master DTM in the Network view, and
clicking the right mouse button.
• Selecting the C200HW-PRM21 Master DTM in the Network view and
from the main menu selecting Device.
2. From the context menu select Additional Functions - Device Assignment. The driver window will open in the DTM view, as shown below.
3. Make sure that the serial cable is attached between the PC’s Serial COM
Port, then in the driver window select the Connect button, associated with
the COM Port to which the C200HW-PRM21 is connected.
4. If connection is successful, the Error Field next to the selected button will
remain 0. The other fields will contain Name and Version information of the
firmware on board the C200HW-PRM21 PROFIBUS DP Master Unit.
In case of connection error, the Error Field will contain an error code, which
can be used to determine the communication problem. Refer to Appendix
G-3 CIF Driver error messages for descriptions on most common driver error numbers.
5. To assign the driver to the selected port and C200HW-PRM21, the checkbox to the left of the COM Port must now be selected, after which the OK
button must be pressed to close the window.
Downloading Parameters
In order to download the parameter sets to the C200HW-PRM21 PROFIBUS
DP Master Unit, perform the following sequence.
91
Generic Slave Device DTM
1,2,3...
Section 3-5
1. Select the DTM in the Network view and right-click the mouse to display
the context menu.
2. Select Download Parameters from the menu, to initiate a download. A
communication channel through the CIF driver will be opened.
Alternatively, the following can be done.
Select the DTM in the Network view and press the Download button in the
toolbar to start the download process.
Note In case the driver assignment has not been done prior to attempting the
download, an error message will be displayed.
Monitoring
For monitoring, an online connection with the Unit must be made first. To
achieve this perform the following sequence.
1,2,3...
1. To go on line, perform one of the following actions.
• Select the DTM in the Network view.
• Select the Device - Go Online option from the main menu, or the DTM
context menu, or
• Select the
button from the Tool Bar.
2. A communication channel will be opened through the CIF Driver. The
name of the DTM in the Network view, will turn to Italic font, to indicate that
the Unit is on-line.
3. From the context menu, select the Diagnosis option. The DTM’s Diagnostics User Interface will be displayed.
3-5
Generic Slave Device DTM
Most of the current PROFIBUS DP slave devices are supplied with a GSD file
in order to allow a configurator to setup a configuration for that particular slave
device. OMRON’s Generic Slave Device DTM is provided to allow integration
of the GSD file based configuration options into an FDT Container application,
like CX-Profibus.
The GSD files are stored in a separate sub-directory under CX-Profibus.
Upon updating the Device Catalogue, the Generic Slave Device DTM will
scan this sub-directory and present an entry in the Device Catalogue for each
of the GSD files found.
Upon adding the GSD based slave device to the network, an instance of the
Generic Slave Device DTM will be made in the PC memory, which will read
the GSD file contents. The instance of the Generic Slave Device DTM will provide the user interface necessary to make the settings for the associated
slave device.
92
Generic Slave Device DTM
3-5-1
Section 3-5
Configuration User Interface
Opening the
Configuration DTM
The configuration DTM is opened by
• Selecting the slave DTM entry in the Network view, and double-clicking
the left mouse button.
• Selecting the slave DTM in the Network view, and right-clicking the
mouse. From the context menu, select Configuration.
The slave DTM Configuration User Interface, which is displayed in the CXProfibus DTM view is shown below. The figure shows the user interface for an
OMRON CJ1W-PRT21 PROFIBUS DP Slave Unit. By default the Configuration tab is opened.
In general, the Configuration User Interface for the Generic Slave Device
DTM, contains three tabs. Above these tabs the Device, the Manufacturer, the
GSD file and the Unit’s PROFIBUS Ident number are displayed.
Note The three tabs allow the user to set the slave parameters and configure the
I/O for a standard PROFIBUS DP slave device. For slave devices which support the extension PROFIBUS DP-V1, to additional tabs will be displayed.
These tabs are discussed later.
Configuration Tab
The Configuration tab contains the Device settings and the I/O module configuration.
Device Settings
The Device Settings contain the device address, i.e. the Unit’s PROFIBUS
address and the Watchdog time for the Unit. The device address is normally
set automatically by the Master DTM, when the slave DTM is added to its tree.
However, the user has the opportunity to change the address. The changed
address will be transferred to the Master DTM.
93
Generic Slave Device DTM
Section 3-5
Note In case a changed address is invalid, for example if there is already another
slave device with the same new address, the Master DTM will set the number
back to its old value.
The Watchdog value is the value used by the slave device to monitor communication from the Master Unit. If no messages are sent to the slave by its Master within the Watchdog timeout time, the slave device will stop data exchange
and switch back to the fail safe mode.
Note In the current version of CX-Profibus, the Watchdog setting made in the
Generic Slave DTM is overruled by the Watchdog setting in the Master DTM
(see also section 6-4-2 Setting the Bus Parameters).
Module Configuration
The I/O module configuration defines the I/O Data which the slave will be
exchanging with the Master Unit, when it is in data exchange mode. The
upper window in the Configuration tab contains all possible modules, which
are in the GSD file. The lower window holds all selected I/O modules.
The user has to select the modules, which are associated with the physical
configuration of the slave device. Selecting, i.e. copying the module from the
upper window of the lower window can be done in several ways.
• Double-click the left mouse button on the selected module in the upper
window.
• Select the module in the upper window and click the Insert button or
Append button. Insert will insert the module above the row selected in the
lower window. Append will add the module to the end of the selected
module list.
Note
1. The user can select multiple rows (in both windows) by simultaneously
holding the SHIFT or CTRL key on the keyboard and selecting the rows
using the left mouse button.
2. The amount of I/O modules and data which can be selected depends on
the slave device. The four rows of information above the module display
the maximum amounts as well as the selected totals.
Removing one or more selected modules from the list is done by
• double-clicking the left mouse button on the module in the lower window.
• selecting the module in the lower window and click the Remove button. In
this case selecting multiple modules is also possible.
94
Generic Slave Device DTM
Section 3-5
Parameter Tab
The Parameter tab lists all settings to be made for the Parameter message.
The Parameter tab is shown below (Example shown is the Parameter tab for
an OMRON CJ1W-PRT21 PROFIBUS DP Slave Unit).
Common Parameters
The PROFIBUS DP parameter message contains a number of settings for the
slave device. It is transmitted to the slave device before the I/O configuration
message. In most cases a slave device requires a block of Common Parameter settings, i.e. settings which apply to the whole device.
Module Parameters
However, there are also more sophisticated - modular - devices which require
parameter settings per I/O module selected. The specific parameters blocks
can be selected from the drop-down list at the top of the Parameter tab. In the
figure above, the Common parameters are shown. This particular device does
not support module parameters, so the parameters shown are the only ones.
The Parameter list consist of a left column containing the name of the Parameter and a right column containing the settings options. In order to change the
parameter setting, double-click the row, with the left mouse button. Depending on the type of parameter and the selection options, either the field can be
edited directly, or a drop-down list with options will appear.
Note The parameter settings must be performed carefully. In general, the slave
device will reject the parameter message, if it contains any faulty parameter.
Consequently, the slave device will not reach I/O data exchange with the
PROFIBUS Master.
The parameter values are by default displayed in Hexadecimal format. By
checking the check box at the bottom, the values are converted to decimal
values.
95
Generic Slave Device DTM
Section 3-5
Group Tab
In the Group tab the user can define to which group the slave device will
belong. This group definition is used to define multi-cast groups of slave
device to which a Global-Control message can be transmitted. The window is
shown below.
Selecting the Groups
The user can check the check boxes for each group the slave device will
belong to. The group setting is transferred to the slave device as part of the
parameter message.
The three tabs discussed above, allow for making all the standard PROFIBUS
DP settings for a slave device. For slave devices supporting PROFIBUS DPV1, two additional tabs will show up. These tabs will appear, if the GSD file
parameter GSD_Revision is set to 3 or higher. The additional tabs are discussed below.
Extensions Tab
96
The Extensions tab contains a number of settings, which define additional
behaviour of the CS1/CJ1W-PRM21 PROFIBUS Master Unit with respect to a
particular PROFIBUS DP-V1 slave device. Although this specific behaviour is
defined in the PROFIBUS DP extensions standard (PROFIBUS DP-V1) it
does not necessarily require PROFIBUS DP-V1 capabilities from the PROFIBUS Master Units. The Extension tab is shown below.
Generic Slave Device DTM
Auto-Clear Processing
Section 3-5
The Auto-Clear processing box defines whether or not the PROFIBUS Master
Unit should ignore a failure of this particular slave, when Auto-CLEAR has
been enabled in the Master Unit (See Auto-CLEAR Box on page 67 in section
3-3-1 Configuration User Interface). When Ignore Auto-CLEAR has been
selected, a failure of this particular slave device (i.e. the slave device requests
new parameters, or fails to respond) will not activate the Auto-CLEAR mode.
The Master Unit will however, service the slave device.
This feature can be used with slaves which can fail during operation, but for
which failure it is not necessary to switch the entire network to Auto-CLEAR
mode.
Control
Configuration Data
Convention
Description
Process Auto-CLEAR
When Auto-CLEAR has been enabled in the PROFIBUS
Master Unit, a failure of this particular slave will cause an
Auto-CLEAR event.
Ignore Auto-CLEAR
When Auto-CLEAR has been enabled in the PROFIBUS
Master Unit, a failure of this particular slave will not cause
an Auto-CLEAR event. The Master will however service
the slave device (e.g. send new parameters).
The Configuration Data Convention setting defines how the slave device will
handle the special identifier format data parts of the Check I/O configuration
message. The slave can perform the check either according to the original
PROFIBUS DP standard, or according to the PROFIBUS DP-V1 standard.
This allows PROFIBUS DP slaves to use either standard PROFIBUS DP data
types or extended PROFIBUS DP-V1 data types.
97
Generic Slave Device DTM
Section 3-5
Control
Fail-Safe Behaviour
Description
DPV1 Compliant
The Check I/O configuration message will contain PROFIBUS DP-V1 Data type definitions in the special identifier
format data parts and the slave device will perform the
check on this assumption.
EN50170 Compliant
The Check I/O configuration message will contain standard PROFIBUS DP Data type definitions as well as vendor specific data types and the slave device will perform
the check on this assumption.
The Fail-Safe Behaviour box defines whether or not the PROFIBUS Master
Unit will in CLEAR mode send an empty output data message to the slave
device or a data message containing zeros. Depending on the PROFIBUS DP
slave device, an empty data message, may be required, if the slave device
performs user specific functions in CLEAR mode, and during which the outputs can not be set to zero.
Control
Error on Cyclic Data
Exchange
Description
Send zeros in Clear
mode
When in CLEAR mode, the PROFIBUS Master Unit will
send a full output data message to the slave device, but
the message will contain all zeros.
Send no data in Clear
mode
When in CLEAR mode, the PROFIBUS Master Unit will
send an empty output data message (i.e. no data bytes,
only the message header) to the slave device.
The Error on Cyclic Data Exchange settings box, defines the behaviour of the
PROFIBUS Master Units on the PROFIBUS network with respect to this particular slave device, in case it fails to respond during I/O data exchange.
Depending on the setting, the Master Unit will either continue sending I/O
data exchange messages to the slave device, or abort I/O data exchange,
and continue with requesting the slave diagnostics data. When continuing
sending I/O data exchange data, the slave’s diagnostics data will not be
updated.
Control
Description
Continue if slave not
responding
The PROFIBUS Master Unit will continue to send I/O data
exchange messages, when the slave device fails to
respond. The diagnostics data of the slave will not be
updated.
Abort if slave not
responding
The PROFIBUS Master Unit will abort the data exchange
with the slave device, and continue to send diagnostics
request message to the slave, until it responds. The diagnostics data of the slave will be updated accordingly.
Note A slave’s failure to respond during I/O data exchange will always be reported
to the PLC CPU, by resetting the corresponding Slave Data_Exchange Active
flags in the CIO Words (see section 4-2-8 Slave Data_Exchange Active Flags
(Word n+9 to Word n+16)). If Auto-CLEAR has been enabled, the failure to
respond will result in the PROFIBUS Master Unit switching to CLEAR mode,
based on this CIO flag.
Diagnostics Update Delay
98
The Diagnostics Update Delay defines the number of PROFIBUS DP cycles
during which the PROFIBUS Master Unit will ignore diagnostics message
returned from the slave containing the Prm_Req flag. This flag indicates that
the Master Unit should re-parameterize the slave, but in the case of reduced
performance slave devices, the returned flag also indicates that the slave
Generic Slave Device DTM
Section 3-5
device is still processing the last received parameter message and has as yet
not approved nor rejected that message.
During the Diagnostics Update Delay period the PROFIBUS Master Unit will
continue requesting its diagnostics data. Also during this period, the diagnostics data received from this slave will not be updated in the PLC CPU.
DPV1 Tab
PROFIBUS DP-V1 defines extended communication functions between a
PROFIBUS DP-V1 master and a PROFIBUS DP-V1 slave device. These
extensions include:
• Acyclic communications between master and slave, to allow re-parameterization, during I/O data exchange.
• Extended alarm reporting and acknowledgement.
Settings related to these extensions are sent to the slave device through the
Set_Prm message.
Note The CS1/CJ1W-PRM21 PROFIBUS DP Master units will automatically disable the DP-V1 settings to avoid the slave devices to use PROFIBUS DP-V1
functions. Only the CS1/CJ1W-PRM21 PROFIBUS DP-V1 Master Units will
use the settings below.
The DPV1 settings window is shown below.
Enable DPV1
This checkbox enables or disables the DPV1 functions for the specific slave
device. The Master DTM will clear this setting prior to download.
Max. Channel Data Length
This parameter defines the maximum size in bytes of the acyclic message
exchanged with the PROFIBUS DP-V1 Master Unit. The size ranges from 4
99
Generic Slave Device DTM
Section 3-5
bytes to 244 bytes. The actual upper limit of the number is defined by the
buffer capacity of the slave device.
Max. Alarm PDU Length
This parameter defines the maximum size of an Alarm message sent from the
slave device to the PROFIBUS DP-V1 Master Unit. The Master Unit uses this
number to reserve buffers to handle the alarms. The maximum alarm message size ranges from 4 bytes to 63 bytes
Alarms
The Alarms box defines the types of alarms the slave device will report, as
well as the alarm handling capacity of the master device. The settings in this
box are conveyed to the slave device through the Set_Prm message sent by
the PROFIBUS DP-V1 Master Unit.
Control
Extra Alarm SAP
Description
Alarm mode
The Alarm mode indicates to the slave device the amount
of alarms the PROFIBUS DP-V1 Master Unit can process
simultaneously. The following standard selections are
available:
• 1 alarm of each selected type
• 2 alarms in total
• 4 alarms in total
• 8 alarms in total
• 12 alarms in total
• 16 alarms in total
• 24 alarms in total
• 32 alarms in total
Pull Plug alarm
When set, this checkbox enables the signalling of a pull/
plug alarm type, i.e. the removal/insertion of a hardware
I/O module.
Process alarm
When set, this checkbox enables the signalling of a process alarm type, i.e. an alarm related to the process connected to the I/O.
Example: Upper Limit exceeded alarm.
Diagnostic alarm
When set, this checkbox enables the signalling of a diagnostic alarm, i.e. an alarm related to the functioning of a
specific I/O module in a slot.
Example: Short circuit detected.
Manufacturer specific
alarm
When set, this checkbox enables the signalling of a Manufacturer specific alarm.
Status alarm
When set, this checkbox enables the signalling of a Status
alarm, i.e. an alarm related to an internal state change in a
module.
Example: Change to Run state, Stop state.
Update alarm
When set, this checkbox enables the signalling of an
Update alarm, i.e. an alarm indicating a change in the
parameters related to a specific module, either by local or
remote access.
For acyclic data exchange between a PROFIBUS DP-V1 Master Unit (Class
1) and a PROFIBUS DP-V1 slave device one specific SAP (Service Access
Point, the PROFIBUS definition for a message identifier) is defined by the
PROFIBUS DP Extension standard. By default SAP 51 is used for acyclic
data exchange with the PROFIBUS DP-V1 Master Unit (Class 1).
For efficiency reasons however, acknowledgement of alarms, can be performed using a different, dedicated SAP or message identifier, SAP50. This
will allow other acyclic communication (e.g. re-parameterization of the slave
device) to continue without interference.
100
Generic Slave Device DTM
Section 3-5
Control
3-5-2
Description
Alarm acknowledge via
SAP 51
When selected, the PROFIBUS DP-V1 Master Unit will
acknowledge each received alarm using SAP 51 message identifier (default).
Alarm acknowledge via
SAP 50
When selected, the PROFIBUS DP-V1 Master Unit will
acknowledge each received alarm using SAP 50 message identifier.
Diagnostics User Interface
The Generic Slave Device DTM provides a Diagnostics User Interface to display diagnostics data sent by the slave device to the PROFIBUS Master Unit.
In general a slave device can send two type of diagnostics.
Basic Diagnostics
• Basic Diagnostics
The first six bytes of each diagnostic message sent by a slave device
contain mandatory status and error flags. The flags are defined by the
PROFIBUS standard. refer to Appendix B Slave Diagnostics Message for
a detailed overview of diagnostics. The basic diagnostics information is
displayed in the Diagnostic tab of the Diagnostics User Interface.
Extended Diagnostics
• Extended Diagnostics
Depending on the type of slave device, it may additionally send Extended
diagnostic bytes in a format defined in the PROFIBUS standard. The
Extended diagnostics usually contain device specific diagnostics information. The Extended diagnostics information is displayed in the Extended
Diagnostics tab of the Diagnostics User Interface.
Updating the Diagnostics
The Diagnostics User Interface contains two tabs. It also contains an Update
button, which will - when pressed - refresh the diagnostics data, by retrieving
it from the PROFIBUS Master Unit. A Green LED indicator in the lower left
corner will indicate whether or not the device is on-line.
Diagnostics Tab
The Diagnostics tab displays basic diagnostics for the slave. An example of
the Diagnostic tab is shown below. The diagnostics information is displayed
as red and green LED indicators. Red LED indicators refer to error events.
Green LED indicator refer to status situations.
101
Generic Slave Device DTM
Section 3-5
The LED indicators are listed in the table below.
Name
Master lock
Parameter fault
Invalid slave response
Function Not supported
Extended diagnostics
Configuration fault
Station not ready
Station not existent
Slave deactivated
Sync mode
Freeze mode
Watchdog on
Slave device
Static diagnostics
Re-parameterization
requested
Extended diagnostics
overflow
Description
The slave device has been parameterized by another master.
The last received parameter data from the Master Unit have been rejected. The parameter
data in the slave device differ from the parameter sent by the Master Unit.
The slave has returned an invalid response to a Master request message.
The Master Unit has sent a message to the slave device, which is not supported by the
device.
The diagnostics message returned by the slave device contains extended diagnostics, i.e. it
contains more than the mandatory 6 bytes.
The last received configuration data from the Master Unit have been rejected. The configuration data in the slave device differ from the configuration sent by the Master Unit.
The slave device is not yet ready for data transfer (the parameters data and the configuration
data have been accepted).
The slave does not respond to any of the request messages sent by the master. If set the
diagnostic bits contains the state of the last diagnostic message or the initial value.
When set to ON, it indicates that the slave device has been disabled (i.e. using the STOP
FINS command). The slave device is allocated to the Master Unit, but removed from cyclic
processing.
When set to ON, the slave device has been set to the Sync mode, using the global command.
When set to ON, the slave device has been set to the Freeze mode, using the global command.
The watchdog has been enabled at the slave device (through the appropriate setting in the
parameterization message).
Indicates that the device is a slave device.
When set, the slave device reports static diagnostics, i.e. the error event is serious enough
that the diagnostics is continuously reported. No data exchange will be performed.
When set, the slave indicates that it requires a new parameter setting. The slave device is
not in Data_Exchange with the Master Unit. The indicator remains ON as long as the slave
device has not been parameterized successfully.
The slave device has more diagnostics to report than it can fit into its transmission buffer.
Diagnostics information is being lost.
Extended Diagnostics
Tab
102
The Extended Diagnostic tab contains any extended diagnostics reported by
the slave device. The figure below shows an example of Extended diagnostics.
Generic Slave Device DTM
Section 3-5
The first row of the Extended diagnostics window contains the raw data as
received from the slave device. Depending on the GSD file, it may provide
text strings for each Extended diagnostics events entry, i.e. if the event occurs
and the diagnostics information is received by the DTM, it can display a text
string in stead of only the raw bytes. This makes troubleshooting the device
easier.
If the strings are not supported, the user must determine the event from the
raw data bytes.
103
SECTION 4
Allocated CIO and DM Words
This section describes the words allocated to the CS1/CJ1W-PRM21 PROFIBUS Master Unit in the CIO and DM Areas.
These words facilitate controlling the Unit and accessing the Unit and network statuses.
4-1
4-2
Overview of Word Allocations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
106
4-1-1
CIO Area Word Allocations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
107
4-1-2
DM Area Word Allocations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
107
Allocated CIO Area Words . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
108
4-2-1
Software Switches 1 (Word n) . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
109
4-2-2
Global-Control Message (Word n+2) . . . . . . . . . . . . . . . . . . . . . . . .
110
4-2-3
Unit Status (Word n+4). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
113
4-2-4
Master Status 1 (Word n+5) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
114
4-2-5
Master Status 2 (Word n+6) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
116
4-2-6
Slave Status (Word n+7) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
117
4-2-7
Actual Bus Cycle Time (Word n+8) . . . . . . . . . . . . . . . . . . . . . . . . .
118
4-2-8
Slave Data_Exchange Active Flags (Word n+9 to Word n+16) . . . .
118
4-2-9
Slave New Diagnostics Flags (Word n+17 to Word n+24). . . . . . . .
119
105
Overview of Word Allocations
4-1
Section 4-1
Overview of Word Allocations
The words shown in the following diagram are allocated according to the unit
number setting. For each CPU Bus Unit, there are 25 words allocated in the
CIO Area and 100 words allocated in the DM Area.
First word allocated in the CIO Area: n = CIO 1,500 + (25 x unit number)
First word allocated in the DM Area: m = D30,000 + (100 x unit number)
PLC CPU Unit
PROFIBUS DP Master unit
Unit Number: 0
Local memory
CPU Bus Unit CIO Area
CIO 1500
CIO 1501
Unit #0
Software switches
25 words
(I/O refresh) status
CIO 1524
CIO 1525
CIO 1526
Unit #1
25 words
25 words
CIO 1549
CIO 1875
Unit #15
25 words
CIO 1899
CPU Bus Unit DM Area
Local memory
D30000
D30001
Unit #0
100 words
No exchange
Reserved for future use
100 words
D30099
D30100
D30101
Unit #1
100 words
D30199
D31500
Unit #15
100 words
D31599
Note
1. The allocated DM words are not used by the PROFIBUS Master Unit. However, exchange of data to the allocated DM words is reserved for future
use, and it is therefore not recommended to use the allocated DM words
for other purposes.
2. The allocation scheme as shown above does not apply to the C200HWPRM21 PROFIBUS DP Master Unit. Word allocations for this Unit are listed in section G-2 Word allocations.
106
Overview of Word Allocations
4-1-1
Section 4-1
CIO Area Word Allocations
Software switches, PROFIBUS Master Unit status, and Slave Status data are
allocated in the CIO Area according to the unit number, as shown below. Software switches are bits used as commands from the PLC CPU to the PROFIBUS Master Unit to enable executing Unit functions.
Unit number
4-1-2
Allocated words
Unit number
Allocated words
0
CIO 1500 to CIO 1524
8
CIO 1700 to CIO 1724
1
CIO 1525 to CIO 1549
9
CIO 1725 to CIO 1749
2
CIO 1550 to CIO 1574
10
CIO 1750 to CIO 1774
3
CIO 1575 to CIO 1599
11
CIO 1775 to CIO 1799
4
CIO 1600 to CIO 1624
12
CIO 1800 to CIO 1824
5
CIO 1625 to CIO 1649
13
CIO 1825 to CIO 1849
6
CIO 1650 to CIO 1674
14
CIO 1850 to CIO 1874
7
CIO 1675 to CIO 1699
15
CIO 1875 to CIO 1899
DM Area Word Allocations
The DM area words which are allocated for the PROFIBUS Master Unit are
not used, i.e. no data is exchanged between an allocated DM area and the
Unit. However, the allocated area is reserved for use in a future extension of
the Unit. Therefore, using this area for user data is not recommended.
Unit number
Allocated words
Unit number
Allocated words
0
D30000 to D30099
8
D30800 to D30899
1
D30100 to D30199
9
D30900 to D30999
2
D30200 to D30299
10
D31000 to D31099
3
D30300 to D30399
11
D31100 to D31199
4
D30400 to D30499
12
D31200 to D31299
5
D30500 to D30599
13
D31300 to D31399
6
D30600 to D30699
14
D31400 to D31499
7
D30700 to D30799
15
D31500 to D31599
107
Allocated CIO Area Words
4-2
Section 4-2
Allocated CIO Area Words
For each CPU Bus Unit, the CS/CJ-series PLC allocates up to 25 words in the
CIO area. Data is stored in the offset position defined by the unit number and
shown in the following figure, starting from the first allocated word to the Unit
in the CIO Area. First word n = CIO 1500 + (25 x Unit number).
CIO WORDS
Word Bit 15
n
Bit 00
Data direction
Software switches 1
n+1
Reserved
n+2
Global-Control command
n+3
Reserved
n+4
Unit status word
n+5
Master status word 1
n+6
Master status word 2
n+7
Slave status word
n+8
Actual bus cycle time
CPU Unit to PROFIBUS Unit
CPU Unit to PROFIBUS Unit
n+9
n+10
n+11
n+12
n+13
Slave Data-Exchange Active flags
n+14
PROFIBUS Unit to CPU Unit
n+15
n+16
n+17
n+18
n+19
n+20
n+21
Slave New-Diagnostics flags
n+22
n+23
n+24
The CIO Words contain two Reserved Words:
• CIO Word n+1 is reserved for future extension of switch functions.
• CIO Word n+3 is reserved for future extension of data to be transferred to
the Unit.
These words are reserved for future use, and it is therefore not recommended
to use them for temporary data storage by a user program. The Unit will
ignore the bits in these words, and consequently not change them, i.e. the
Unit will not set the bits to OFF. The other CIO Words are explained in the following sections.
108
Allocated CIO Area Words
4-2-1
Section 4-2
Software Switches 1 (Word n)
All the switches of Software Switch 1 execute a function when turned ON by
the user (in any PLC mode). The Unit will turn the switch to OFF, after the
command has been executed. All flags are set to OFF at Power-ON/Reset.
The Unit state is not restored after a Power-Down of the Unit.
Note If multiple bits in the range of Bit 00 to 03 are set simultaneously, the command is ignored, the bits are set to OFF again and the Mode command error
flag in Master status 2 word is set, see 4-2-5 Master Status 2 (Word n+6).
15 14 13 12 11 10 9
8
7
6
5
4
3
2
1
0
Word n
OPERATE mode
STOP mode
CLEAR mode
OFFLINE mode
Transmit Global-Control message
Clear new-diagnostics flags
Word n [n = CIO 1,500 + (25 x unit number)]
Bit
00
Name
Switch Master to
OPERATE mode
Status
OFF→
ON
OFF
01
Switch Master to
STOP mode
OFF→
ON
OFF
02
Switch Master to
CLEAR mode
OFF→
ON
OFF
03
Switch Master to
OFFLINE mode
OFF→
ON
OFF
Controlled
Unit operation
by
User
Switches the Unit to the OPERATE mode. If the Unit is already in this
mode, no action will be taken.
In OPERATE mode the PROFIBUS Master Unit will parameterize all
allocated slave devices, and commence I/O Data-Exchange.
See Note 1 and 2.
Unit
If the PROFIBUS Master Unit has entered the OPERATE mode, the
Unit will set this bit to OFF again.
User
Switches the Unit to the STOP mode. If the Unit is already in this mode,
no action will be taken.
In STOP mode, the Unit will be online, connected to the network, but
not communicate with its slave devices.
See Note 1 and 2.
Unit
If the PROFIBUS Master Unit has entered the STOP mode, the Unit will
set this bit to OFF again.
User
Switches the Unit to the CLEAR mode. If the Unit is already in this
mode, no action will be taken.
In CLEAR mode the PROFIBUS Master Unit will parameterize all allocated slave devices, and it will read the input data of the slave devices,
but it will send zeros or empty output messages to slave devices.
See Note 1 and 2.
Unit
If the PROFIBUS Master Unit has entered the CLEAR mode, the Unit
will set this bit to OFF again.
User
Switches the Unit to the OFFLINE mode. If the Unit is already in this
mode, no action will be taken.
In the OFF-LlNE mode the Unit will be disconnected from the network.
See Note 1 and 2.
Unit
If the PROFIBUS Master Unit has entered the OFFLINE mode, the Unit
will set this bit to OFF again.
109
Allocated CIO Area Words
Bit
04
Name
Status
Transmit GlobalControl message
OFF→
ON
OFF
05
to
07
08
09
to
15
Reserved by system
---
Clear new diagnos- OFF→
tics bits
ON
OFF
---
Reserved by system
Note
Section 4-2
Controlled
Unit operation
by
User
Upon setting this switch the Unit will transmit one Global-Control message over the network. The contents of the message is defined in CIO
Word n+2, see 4-2-2 Global-Control Message (Word n+2).
See Note 3.
Unit
The bit will be turned OFF by the Unit if the Global-Control message
has been transmitted.
--These bits are ignored in the Unit. If set, they will be immediately
returned to OFF.
User
Unit
---
Upon setting this switch the Unit will clear all new diagnostics bit flags in
CIO Word n+17 to n+24. These bits indicate reception of new slave
diagnostics data.
Clearing the bit flags provides a clear indication for new messages to
arrive.
If the bit flags have been cleared, the Unit will reset this bit to OFF.
These bits are ignored in the Unit. If set, they will immediately be set to
OFF by the Unit.
1. When switching the PROFIBUS Master Unit from one mode to another, it
will internally implement the mode transition via the intermediate modes,
e.g. from OFFLINE to OPERATE, will be performed as OFFLINE →STOP
→ CLEAR → OPERATE. See also section 1-1-7 Network Operation
Modes.
2. If two or more mode switches, i.e. Bit 00 to 03, have been set at the same
time, or the Unit can not implement the mode change due to an invalid configuration, the command will be ignored and the Mode command error flag
in the Master Status 2 word (CIO Word n+6) will be turned ON. See also
section 4-2-5 Master Status 2 (Word n+6).
3. If the PROFIBUS Master Unit is not in the correct mode, i.e. the Unit is in
OFFLINE or STOP mode, the Transmit Global-Control message command
will be ignored, but the bit will remain ON. The command will be sent when
the Unit transitions to the correct mode, unless the user clears the Bit. No
error indication will be generated.
4-2-2
Global-Control Message (Word n+2)
A PROFIBUS Global-Control message can be transmitted by the Unit on user
demand to either
Global-Control Multicast
Command
• one or more groups of slave devices allocated to the PROFIBUS Master
Unit (Multicast command), or
Global-Control Broadcast
Command
• all slave devices allocated to the PROFIBUS Master Unit (Broadcast command).
The number of the group to which each slave device belongs, is defined in its
parameterization message. Only the slave devices assigned to the groups to
which the Global-Control message is addressed will process the command.
Group Address Setting
The group address to send the message to is specified in bit 00 through bit
07. Selecting specific groups of slave devices (i.e. a Multicast command),
requires setting of one or more bits in this range to ON. Selecting all slaves
(i.e. a Broadcast command) requires all bits in this range to be set to OFF.
The Global-Control command flags are specified in the bit 10 through bit 13.
110
Allocated CIO Area Words
Section 4-2
Transmitting the message is done by setting the Transmit Global-Control
message switch, bit 04 in CIO Word n, see 4-2-1 Software Switches 1 (Word
n).
15 14 13 12 11 10 9
Word n+2
8
7
6
5
4
3
2
1
0
Group select:
Group 1
Group 2
Group 3
Group 4
Group 5
Group 6
Group 7
Group 8
Unfreeze
Freeze
Unsync
Sync
Word n+2 [n = CIO 1,500 + (25 x unit number)]
Bit
00
to
07
Name
Reserved by system
---
Controlled
Unit operation
by
User
Each bit in this range represents one of up to 8 groups of slaves. Bits 00
to Bit 07 will be included within the Global-Control message as group
address indicators.
If a Group number bit is set, the slave devices assigned to this group
number will process the Global-Control command.
User
If a Group number bit is not set, the slave devices assigned to this
group number will ignore the Global-Control command, except if none
of the Group address bits are set, i.e. Bit 00 to Bit 07 are all set to OFF.
This selection defines a Broadcast command, causing all slave devices
allocated to the PROFIBUS Master Unit to process the Global_ Control
command.
--These bits are reserved by the system and will ignored by the Unit.
Unfreeze
ON
User
OFF
User
ON
User
OFF
User
Group address
Status
ON
OFF
08
to
09
10
11
Freeze
If the Unfreeze bit is set, the Unfreeze command will be send to the targeted slave devices.
The Unfreeze command releases the targeted slave devices from the
Freeze mode (see below).
The bit set to OFF indicates that the Unfreeze command will not be
transferred to the slave devices.
The Freeze command forces the slave devices into the Freeze mode. In
this mode a slave device will not update its inputs to the Master and
continue to transmit the input data acquired before the Freeze command.
If the slave device is already in the Freeze mode, a new Freeze command will force the slave to update its inputs only once and continue to
transmit the new input data to the Master.
The bit set to OFF indicates that the Freeze command will not be transferred to the slave devices.
111
Allocated CIO Area Words
Bit
12
Name
Unsync
Status
ON
OFF
13
Sync
ON
OFF
14
to
15
Reserved by system
Freeze Mode
Sync Mode
112
---
Section 4-2
Controlled
Unit operation
by
User
If the Unsync bit is set, the Unsync command will be send to the targeted slave devices.
The Unsync command releases the targeted slave devices from the
Sync mode (see below).
User
The bit set to OFF indicates that the Unsync command will not be transferred to the slave devices.
User
The Sync command forces the slave devices into the Sync mode. In
this mode the slave device will not update its outputs and continues to
use the output data received before the Sync command.
If the slave device is already in the Sync mode, a new Sync command
will force the slave to update its outputs only once, with the most recent
output data received from the Master.
User
The bit set to OFF indicates that the Sync command will not be transferred to the slave devices.
--These bits are reserved by the system and will ignored by the Unit.
The user can set the Freeze and Unfreeze bits at the same time, and both will
be transmitted to the targeted slave devices at the same time but the resulting
action at the slave device is defined in the PROFIBUS standards.
Bit 10
Bit 11
OFF
OFF
OFF
ON
ON
OFF
ON
ON
Resulting action at slave
No change in function
Slave device will be in Freeze mode
Slave device will be in Unfreeze mode
Slave device will be in Unfreeze mode
The user can set the Sync and Unsync bits at the same time, and both will be
transmitted to the targeted slave devices at the same time, but the resulting
action at the slave device is defined in the PROFIBUS standards.
Bit 12
Bit 13
OFF
OFF
OFF
ON
ON
OFF
ON
ON
Resulting action at slave
No change in function
Slave device will be in Sync mode
Slave device will be in Unsync mode
Slave device will be in Unsync mode
Allocated CIO Area Words
4-2-3
Section 4-2
Unit Status (Word n+4)
The Unit status word contains all the status and error flags concerning the
Unit itself, as well as error flags, which indicate the presence of error flags in
the Master and Slave Status Words. All bits are controlled by the Unit.
15 14 13 12 11 10 9
8
7
6
5
4
3
2
1
0
Word n+4
Unit error flag
Master error flag
Error log contains new errors
Parameter transfer in progress
Local parameter storage error
Local parameter load error
File read error
Error log storage error
Word n+4 [n = CIO 1,500 + (25 x unit number)]
Bit
00
Name
Unit error flag
Status
---
Controlled
Unit operation
by
Unit
The Unit error flag collects the status of all error flags in CIO Word n+4.
The bit flag is turned ON by the Unit if Bit 01, Bit 03, Bit 06, Bit 07, Bit 09
or Bit 13 in CIO Word n+4 is set to ON.
Unit
Bit 00 is turned OFF by the Unit if Bit 01, Bit 03, Bit 06, Bit 07, Bit 09 and
Bit 13 in CIO Word n+4 are set to OFF.
Unit
The Master error flag collects the error flags in the Master status 2
Word, i.e. CIO Word n+6. Master status word 2 contains all error flags
related to the PROFIBUS Master functions.
Bit 01 is turned ON if any of the flags in Master status word 2, i.e. CIO
Word n+6 is set to ON, see 4-2-5 Master Status 2 (Word n+6).
Unit
Bit 01 is turned OFF if none of the flags in Master status word 2, i.e. CIO
Word n+6 is set to ON.
--This bit will be set to OFF by the Unit.
ON
Unit
OFF
Unit
ON
OFF
01
Master error flag
ON
OFF
02
03
Reserved by system
Error log contains
new errors
This bit indicates new errors in the error log since the last time the error
log was cleared or read. It is set to ON if the error log contains one or
more new errors.
The bit flag is set to OFF by the Unit if the error log is
• cleared using the ERROR LOG CLEAR FINS command, or
• read, using the ERROR LOG READ FINS command.
04
Parameter transfer
in progress
ON
Unit
The Parameter transfer in progress indicates transfer of Configuration
and setup data
• from the PC to the Unit’s internal volatile memory, or
• from the Unit’s internal volatile memory to non-volatile memory, or
• from the flash card to the Unit’s internal volatile memory.
05
Reserved by system
OFF
Unit
---
---
During this transfer no other transfer of data can be started in parallel.
When set to OFF, this bit indicates that no Configuration data transfer is
in progress.
This bit will be set to OFF by the Unit.
113
Allocated CIO Area Words
Bit
06
Name
Local parameter
storage error
Status
OFF
---
Controlled
Unit operation
by
Unit
The local parameter storage error flag will be turned ON if an error
occurred during an attempt to write the Configuration and setup data to
internal non-volatile memory.
If the error occurred, the data in the non-volatile memory may be corrupted and a new Configuration must be downloaded to the Unit.
Unit
When set to OFF, this bit indicates that the Configuration and setup
data has been transferred to the non-volatile memory successfully.
Unit
The Local parameter load error flag will be turned ON if an error
occurred during an attempt to transfer the Configuration and setup data
from non-volatile to volatile memory.
Unit
The flag will be turned OFF if a successful load attempt is made.
--This bit will be set to OFF by the Unit.
ON
Unit
OFF
---
Unit
---
ON
Unit
OFF
Unit
---
---
ON
OFF
07
08
09
10
to
12
13
14
to
15
Local parameter
load error
Reserved by system
File read error
Reserved by system
Error log storage
error
Reserved by system
4-2-4
Section 4-2
ON
The File read error flag will be turned ON if an error occurred during an
attempt to transfer the Configuration and setup data from a flash card in
the PLC CPU to the Unit’s non-volatile memory. The error can be
caused by an error in the File or an error during transfer.
The flag will be turned OFF if a successful load from flash card is made.
These bits will be set to OFF by the Unit.
The Error log storage error flag will be turned ON if an error occurred
during an attempt to write the Error log to internal non-volatile memory.
If the error occurred, the Error log data in the non-volatile memory may
be corrupted. Upon a restart the Unit will attempt to repair the Error log.
When set to OFF, this bit indicates that the Error log has been transferred to the non-volatile memory successfully.
These bits will be set to OFF by the Unit.
Master Status 1 (Word n+5)
The Master Status 1 word collects all status information related to the PROFIBUS Master function. Any errors related to the PROFIBUS Master function
are collected in the Master status 2 word.
15 14 13 12 11 10 9
8
7
6
5
4
3
2
1
0
Word n+5
Unit in OPERATE mode
Unit in STOP mode
Unit in CLEAR mode
Unit in OFFLINE mode
Unit in Data-Exchange
Auto-Clear enabled
Unit contains a valid configuration
114
Allocated CIO Area Words
Section 4-2
Word n+5 [n = CIO 1,500 + (25 x unit number)]
Bit
00
01
Name
Unit in OPERATE
mode
Status
---
Controlled
Unit operation
by
Unit
Indicates that the Unit is in OPERATE mode.
In OPERATE mode the PROFIBUS Master Unit will parameterize all
allocated slave devices, and commence I/O Data-Exchange.
Unit
Indicates that the Unit is not in OPERATE mode.
Unit
Indicates that the Unit is in STOP mode.
In STOP mode, the Unit will be ONLINE, connected to the network, but
not communicate with its slave devices.
Unit
Indicates that the Unit is not in STOP mode.
Unit
Indicates that the Unit is in CLEAR mode.
In CLEAR mode the PROFIBUS Master Unit will parameterize all allocated slave devices. If this is accomplished successfully, it will read all
input data of the allocated slave devices, but it will send zeros or empty
output messages to all slave devices.
Unit
Indicates that the Unit is not in CLEAR mode.
Unit
Indicates that the Unit is in OFFLINE mode.
In the OFF-LlNE mode the Unit will be disconnected from the network.
Unit
Indicates that the Unit is not in OFFLINE mode.
Unit
If set to ON, this bit indicates that the Unit is in Data_Exchange with at
least one allocated and enabled slave device.
Unit
If set to OFF, this bit indicates that the Unit is not in Data_Exchange
with at any of the allocated and enabled slave devices.
Unit
If set to ON, this bit indicates that the Auto-CLEAR function has been
enabled. In case an error occurs in one of the allocated slave devices
during Data_Exchange, this function forces the Unit to the CLEAR
mode, in which it will force all allocated slave devices to a Fail Safe
mode.
Unit
If set to OFF, the Auto-CLEAR function has been disabled. If in this case
an error occurs in an allocated slave device, the PROFIBUS Master Unit
will continue Data_Exchange with the remaining slave devices.
--This bit will be set to OFF by the Unit.
ON
Unit
OFF
Unit
---
---
ON
OFF
Unit in STOP mode ON
02
Unit in CLEAR
mode
03
Unit in OFFLINE
mode
04
Unit in
Data_Exchange
OFF
ON
OFF
ON
OFF
ON
OFF
05
Auto-CLEAR
enabled
ON
OFF
06
07
08
to
15
Reserved by system
Unit contains a
valid configuration
Reserved by system
If set to ON, this bit indicates that the Unit contains a valid Configuration. With this Configuration it can parameterize the allocated slave
devices and achieve Data_Exchange.
If this bit is set to OFF, the Unit does not contain a valid Configuration or
transfer of a new Configuration is in progress.
These bits will be set to OFF by the Unit
115
Allocated CIO Area Words
4-2-5
Section 4-2
Master Status 2 (Word n+6)
The Master Status 2 word collects all error information on the Unit master
function. The status information is collected in the Master Status 1 word.
The contents of the Master Status 2 word (Word n+6) are:
15 14 13 12 11 10 9
8
7
6
5
4
3
2
1
0
Word n+6
Disturbed bus error
PROFIBUS protocol error
Double Master address error
Hardware error
Mode command error
Parameter error
Word n+6 [n = CIO 1,500 + (25 x unit number)]
Bit
Name
Status
00
Disturbed Bus error ON
01
PROFIBUS protocol error
02
Double Master
address error
03
04
to
11
116
Hardware error
Reserved by system
OFF
ON
OFF
ON
OFF
ON
OFF
---
Controlled
Unit operation
by
Unit
When turned ON, the Disturbed Bus error indicates that distorted messages have been received by the Unit. This may occur if the network is
not properly terminated or a cable is used, which is too long for the
selected baud rate.
Unit
Indicates that no Disturbed Bus error has occurred.
Unit
The PROFIBUS Protocol error flag will be turned ON if an error has
occurred in the protocol handling, e.g. a transmitted token frame could
not be read back.
Note In case this error occurs, the Unit will automatically switch to
OFFLINE mode.
Unit
Indicates that no PROFIBUS protocol error has occurred.
Unit
The Double Master Address error flag will be turned ON if there is
another master on the bus with the same with the same device address
as the CS1/CJ1W-PRM21.
Note In case this error occurs, the Unit will automatically switch to
OFFLINE mode.
Unit
Indicates that no Double Master Address error has occurred.
Unit
The Hardware error flag will be turned ON if an error has occurred on
the bus, e.g. message exceeding 256 bytes, broken messages, faulty
bus timing or devices beyond the HSA have been detected.
Note In case this error occurs, the Unit will automatically switch to
OFFLINE mode.
Unit
Indicates that no Hardware error has occurred.
--These bits will be set to OFF by the Unit.
Allocated CIO Area Words
Bit
12
Name
Mode command
error
Status
ON
Section 4-2
Controlled
Unit operation
by
Unit
This bit will be turned ON, if
• more than one command mode switch has been set, i.e. Bit
00 to Bit 03 in Word n has been set, or
• a mode command switch is set while the previous command
is in progress, or
• a mode transition command is given and the Unit has
detected that it does not (yet) have a valid configuration or it
detected an internal error, either of which prevented it from
reaching that mode, e.g. Invalid Parameter set and transition to OPERATE mode.
13
Parameter error
14
to
15
Reserved by system
4-2-6
OFF
ON
Unit
Unit
OFF
---
Unit
---
If this bit is turned ON, it will remain so until a valid command is sent to
the Unit. The invalid mode command will be ignored.
If the bit flags have been cleared, the Unit will reset this bit to OFF.
The Parameter set error will be turned to ON if an error has been
detected in the contents of the Parameters set while configuring the
PROFIBUS interface, using these parameters.
If the bit flags have been cleared, the Unit will reset this bit to OFF.
These bits will be set to OFF by the Unit.
Slave Status (Word n+7)
The Slave Status word collects all the information on the slave devices allocated to the Unit Master. It summarizes the slave information of the Slave
Data_Exchange Active flags, see 4-2-8 Slave Data_Exchange Active Flags
(Word n+9 to Word n+16)) and the Slave New-Diagnostics flags, see 4-2-9
Slave New Diagnostics Flags (Word n+17 to Word n+24).
15 14 13 12 11 10 9
8
7
6
5
4
3
2
1
0
Word n+7
Slaves in data exchange
Slave diagnostics received
Word n+7 [n = CIO 1,500 + (25 x unit number)]
Bit
00
Name
All slaves in
Data_Exchange
mode
Status
ON
OFF
01
to
03
Reserved by system
---
Controlled
Unit operation
by
Unit
All slave devices, which are allocated to the PROFIBUS Master Unit are
and enabled are in Data_Exchange with the PROFIBUS Master Unit. All
slaves which are in Data exchange are indicated in CIO Word n+9 to
n+16, see 4-2-8 Slave Data_Exchange Active Flags (Word n+9 to Word
n+16).
Unit
When turned OFF, this bit indicates that at least one slave device is not
in Data_Exchange with the PROFIBUS Master Unit.
--These bits are reserved for future use and are always set to OFF by the
Unit.
117
Allocated CIO Area Words
Bit
04
Name
Status
New slave diagnos- ON
tics received
OFF
05
to
15
Reserved by system
4-2-7
---
Section 4-2
Controlled
Unit operation
by
Unit
At least one of the slave devices, allocated to the PROFIBUS Master
Unit indicates that new Diagnostics data is available. The slaves which
indicates this data are indicated in CIO Word n+17 to n+19, see 4-2-9
Slave New Diagnostics Flags (Word n+17 to Word n+24).
Unit
When turned OFF, this bit indicates that none of the slave device has
returned new diagnostics messages, since the last time the flags were
cleared.
--These bits are reserved for future use and are always set to OFF by the
Unit.
Actual Bus Cycle Time (Word n+8)
The actual bus cycle time word indicates the current bus cycle time expressed
in BCD in 0.1 ms units. The maximum value is, therefore, 999.9 ms. Values
larger than 999.9 ms are set at 9999.
4-2-8
Slave Data_Exchange Active Flags (Word n+9 to Word n+16)
The Slave Data_Exchange Active flags indicate for each slave device if it is in
Data_Exchange mode with the PROFIBUS Master Unit. The flags are allocated to a block of eight CIO words, and each bit in the block corresponds to a
device address.
15 14 13 12 11 10 9
8
7
6
5
4
3
2
1
0
Word n+9
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
Slave station 00 ~ 15
Word n+10
31
30
29
28
27
26
25
24
23
22
21
20
19
18
17
16
Slave station 16 ~ 31
Word n+11
47
46
45
44
43
42
41
40
39
38
37
36
35
34
33
32
Slave station 32 ~ 47
Word n+12
63
62
61
60
59
58
57
56
55
54
53
52
51
50
49
48
Slave station 48 ~ 63
Word n+13
79
78
77
76
75
74
73
72
71
70
69
68
67
66
65
64
Slave station 64 ~ 79
Word n+14
95
94
93
92
91
90
89
88
87
86
85
84
83
82
81
80
Slave station 80 ~ 95
Word n+15
111 110 109 108 107 106 105 104 103 102 101 100 99
98
97
96
Slave station 96 ~ 111
Word n+16
125 124 123 122 121 120 119 118 117 116 115 114 113 112
Slave station 112 ~ 125
When a slave device is in Data_Exchange with the PROFIBUS Master Unit to
which it has been allocated, it is exchanging I/O Data with the PROFIBUS
Master Unit.
If the PROFIBUS Master Unit is in CLEAR mode, it will read the slave’s input
data, but send zeros or an empty message as output data.
If the PROFIBUS Master Unit is in OPERATE mode, it will read the slave’s
input data, and send any output data provided by the PLC CPU
118
Allocated CIO Area Words
Section 4-2
Word n+9 to n+16 [n = CIO 1,500 + (25 x unit number)]]
Bit
–
Name
Slave
Data_Exchange
Active flags
Status
ON
OFF
4-2-9
Controlled
Unit operation
by
Unit
If the bit corresponding to a slave device address is ON, it indicates that
this slave device
• is allocated to the PROFIBUS Master Unit, and
• is exchanging I/O Data with PROFIBUS Master Unit.
In this case, the PROFIBUS Master Unit must be in the CLEAR mode or
the OPERATE mode.
Unit
If the bit corresponding to a slave device address is OFF, it indicates
that the slave is not in Data_Exchange with this PROFIBUS Master
Unit, due to the fact that
• the slave device is not allocated to this PROFIBUS Master Unit, or
• the slave device has been allocated to this PROFIBUS Master Unit,
but is forced out of Data_Exchange mode, due to a communication
error, or
• the slave device has been allocated to this PROFIBUS Master Unit,
but is not responding,
• the slave device has been allocated to this PROFIBUS Master Unit,
but is it has temporarily been disabled,
• the PROFIBUS Master Unit is not in CLEAR or OPERATE mode
Slave New Diagnostics Flags (Word n+17 to Word n+24)
The Slave New Diagnostics flags indicate for each slave device if it sent a
new diagnostics message to the PROFIBUS Master Unit, since the last time it
was read or cleared by the CS/CJ-series PLC. The flags are allocated to a
block of eight CIO words, and each bit in the block corresponds to a device
address.
15 14 13 12 11 10 9
8
7
6
5
4
3
2
1
0
Word n+17
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
Slave station 00 ~ 15
Word n+18
31
30
29
28
27
26
25
24
23
22
21
20
19
18
17
16
Slave station 16 ~ 31
Word n+19
47
46
45
44
43
42
41
40
39
38
37
36
35
34
33
32
Slave station 32 ~ 47
Word n+20
63
62
61
60
59
58
57
56
55
54
53
52
51
50
49
48
Slave station 48 ~ 63
Word n+21
79
78
77
76
75
74
73
72
71
70
69
68
67
66
65
64
Slave station 64 ~ 79
Word n+22
95
94
93
92
91
90
89
88
87
86
85
84
83
82
81
80
Slave station 80 ~ 95
Word n+23
111 110 109 108 107 106 105 104 103 102 101 100 99
98
97
96
Slave station 96 ~ 111
Word n+24
125 124 123 122 121 120 119 118 117 116 115 114 113 112
Slave station 112 ~ 125
119
Allocated CIO Area Words
Section 4-2
Word n+17 to n+24 [n = CIO 1,500 + (25 x unit number)]
Bit
–
Name
Slave New Diagnostics flags
Status
ON
OFF
Controlled
Unit operation
by
Unit
If the bit corresponding to a slave device address is ON, it indicates that
this slave device
• is allocated to the PROFIBUS Master Unit, and
• has sent new diagnostics message to the PROFIBUS Master Unit.
In this case, the PROFIBUS Master Unit must be in CLEAR mode or
OPERATE mode.
Unit
If the bit corresponding to a slave device address is OFF, it indicates
that
• the slave device has not sent a new diagnostics message to the
PROFIBUS Master Unit, since the last time it was read or cleared, or
• the slave device has not been allocated to this PROFIBUS Master
Unit, or
• the PROFIBUS Master Unit is not in CLEAR or OPERATE mode
Note
120
In case an allocated slave device is not responding, and therefore not sending a diagnostics message, the PROFIBUS Master
Unit itself will provide a diagnostics message to the PLC CPU
containing the mandatory first 6 bytes. This diagnostics message will then indicate that the slave is not responding.
SECTION 5
FINS Commands and Responses
This section describes the FINS message service communications commands concept as well as the commands supported
by the CS1/CJ1W-PRM21 PROFIBUS Master Units.
5-1
5-2
FINS Commands and Responses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-1-1 FINS Message Service Communications . . . . . . . . . . . . . . . . . . . . .
5-1-2 Command Code List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-1-3 Response Code List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-1-4 Sending FINS using CMND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Command / Response Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-2-1 MEMORY AREA READ (0101) . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-2-2 RUN (0401) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-2-3 STOP (0402) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-2-4 CONTROLLER DATA READ (0501) . . . . . . . . . . . . . . . . . . . . . . .
5-2-5 ERROR LOG READ (2102) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-2-6 ERROR LOG CLEAR (0203) . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-2-7 PROFIBUS MESSAGE SEND (2809). . . . . . . . . . . . . . . . . . . . . . .
122
122
123
123
124
125
125
126
127
128
128
130
130
121
FINS Commands and Responses
5-1
5-1-1
Section 5-1
FINS Commands and Responses
FINS Message Service Communications
FINS
FINS (Factory Intelligent Network Services) commands are message service
communications commands developed by OMRON for Factory Automation
control devices. They do not depend on a particular transmission path, and
can be used for reading from and writing to PLC memory or the Unit’s memory, sending or receiving acyclic messages over a network, or for controlling
various operations.
The FINS communications can be issued from a CPU Unit, Special I/O Unit,
or host computer, and they can also be sent to any of these. The specific
commands that can be sent depend on the destination.
When the source of the commands is a PLC CPU Unit, the FINS commands
are sent by means of CMND(490). For details on FINS commands, refer to
the Communications Commands Reference Manual (W342)
Note The C200HW-PRM21 does not support FINS commands.
The CS1/CJ1W-PRM21 PROFIBUS Master Units support two types of FINS
messages:
1. FINS commands targeted at the Unit itself, with the purpose of sending or
retrieving data or invoking control actions.
2. FINS commands facilitating data transfer using PROFIBUS services, targeted at a specific slave device connected to the same PROFIBUS network as the PROFIBUS Master Unit.
Note FINS commands of the second type are supported as of Unit version 2.0.
The figure below depicts the FINS command structure for the CS1/CJ1WPRM21 PROFIBUS Master units.
CPU Unit
CMD (490)
Instruction
CMD (490)
Instruction
(2809 Hex)
PROFIBUS Master Unit
FINS message
FINS
PROFIBUS message
PROFIBUS network
FINS
message
function
PROFIBUS
message
function
PROFIBUS message
FINS messages are defined through their command and response codes.
Command Codes
Command codes are represented by a 2-byte hexadecimal code. FINS commands always begin with a 2-byte command code; any parameters required
follow the command code.
Response Codes
The response code consists of a 2-byte hexadecimal code indicating the
results of command execution. The first byte provides the main response
code (MRES), which classifies the results, the second byte provides the subresponse code (SRES), which contains details about the results.
122
FINS Commands and Responses
5-1-2
Section 5-1
Command Code List
The command codes listed in the following table are supported by the PROFIBUS Master Unit. A PLC program can send these to the Unit.
Command code
Name
Page
MRC
SRC
01
01
MEMORY AREA READ
125
04
01
RUN
126
02
STOP
127
128
05
01
CONTROLLER DATA READ
21
02
ERROR LOG READ
128
03
ERROR LOG CLEAR
130
09
PROFIBUS MESSAGE SEND (See Note)
130
28
Note FINS command 2809 has been implemented as of Unit version 2.0.
5-1-3
Response Code List
Response codes are 2-byte codes which indicate the results of command
execution. They are returned in the response following the command code.
The first byte of a response code is the MRES (main response code), which
categorizes the results of command execution. The second byte is the SRES
(sub-response code) which specifies the results.
Command Response
code
code
MRC:
SRC:
MRES:
SRES:
Main request code
Sub-request code
Main response code
Sub-response code
MRC SRC MRES SRES
The MRES codes are shown in the following table along with the results they
indicate. Refer to Communications Commands Reference Manual (W342) for
details on response codes including the SRES.
MRES
Execution results
00
Normal completion
01
Master Unit error
02
Slave device error
04
Service not supported
10
Command format error
11
Parameter error
20
Read not possible
22
Status error
Note If the FINS command was not completed normally, the 2-byte Response code
will be unequal 0000. In that case, the Response frame will not contain any
further data. Data can only be returned - depending on the command - when
the Response code is 0000.
123
FINS Commands and Responses
5-1-4
Section 5-1
Sending FINS using CMND
The CMND instruction can be executed from the user program in a CS/CJseries PLC. CMND sends “n” bytes of command data beginning with S (the
beginning send word for storing command data at the source node) to destination node N. In return, “m” bytes of response data are stored at the source
node beginning with D (the beginning receive word for storing response data).
15
S
S: Source node beginning send word
D: Destination node beginning receive word
C: Source node first control data word
n
+2
Command
…
(S –1)
15
Destination node N
Source node
0
…
CMND
S
D
C
"n" bytes
of command
data
0
Response
C
D
"m" bytes
of
response
data
…
"n" bytes of command data
0000 to 07C6 (Hex): 0 to 1,990 words
15
Analysis
(D –1)
0
Execution
m
+2
C+1
"m" bytes of response data
0000 to 07C6 (Hex): 0 to 1,990 words
15
C+2
11
0
87
0
0
15
C+4
10 8 7
0
0
3
Number of retries
0 to F (Hex): 0 to 15 retries
Destination network address
00 (Hex): Local network
01 to 7F (Hex): 1 to 127
15
87
0
0
0
C+3
0: Response required
1: Response not required
Destination unit address
00 (Hex):
PC's CPU Unit
01 (Hex):
Computer (user program)
10 to 1F (Hex): Unit nos. 0 to 15
E1 (Hex):
Inner Board
FE (Hex):
Unit connected to network
Destination node N
00 to 20 (Hex): 0 to 32
The same data can be broadcast to all nodes
on the network by setting the destination node address
to FF (Hex).
The range of node addresses will vary for networks
other than Controller Link Networks.
15
10 8 7
3
0
C+5
Response monitor time
0000 (Hex): 2 s
0001 to FFFF (Hex): 0.1 to 6,553.5 s
(Unit: 0.1 s)
If the baud rate is slow, then setting a
small value may generate an error. The
standard is approximately 4 seconds at
1 Mbps or 8 seconds at 500 Kbps.
Note With the message service, there is no guarantee that a message to a destination node will reach its destination. It is always possible that the message may
be lost in transit due to noise or some other condition. When using the message service, it is advisable to prevent this situation from occurring by performing resent processing at the node where instructions are issued. With the
CMND instruction, resent processing is performed automatically once the
number of retries has been set, so be sure to specify a number other than “0”
for the number of retries.
124
Command / Response Reference
5-2
Section 5-2
Command / Response Reference
This section describes the FINS commands that can be sent to the PROFIBUS Master Units and the responses to each command.
The command, response, and (where applicable) the results storage blocks
are given with the commands in graphic form as shown in the following diagram. If the data is fixed, it is included in the blocks. If the data is variable, it is
described following the blocks. Each box represents 1 byte; two boxes represent 1 word. The following diagram shows 2 bytes, or 1 word.
Two bytes
Response codes applicable to the command are described at the end of the
command description.
5-2-1
MEMORY AREA READ (0101)
The MEMORY AREA READ command is used to the last diagnostics data
message the PROFIBUS Master Unit received from the specified slave
device. The command frame requires three byte data type specifier, specifying the information, and one byte specifying the slave device address.
The number of items to read must be 244 - the maximum data size of the
PROFIBUS DP diagnostics message - or less.
Command Format
01
01
Command
code
81
FF
00
Data specifier
No. of items
(binary)
Device address
Response Format
01
01
Command
code
Parameters
Response
code
Diagnostics data
(for number of items)
Data specifier code (command)
Defines the data to be retrieved from the Unit. Always set to 81 FF 00 (Hex).
Slave device address (command)
Defines the slave device network address. Set to 00 ~ 7D (Hex).
Number of items to read (command)
Defines the number of bytes to read. Set to 1 ~ F4 (Hex).
Response Codes
The following end codes can be returned by the Unit in response to the RUN
command:
Response code
Description
0000
Normal completion.
0203
Slave device not allocated to the PROFIBUS Master.
0402
Service not supported by Unit model / version.
125
Command / Response Reference
Section 5-2
Response code
5-2-2
Description
1001
Command too large.
1002
Command too short.
110C
• Invalid start address code word (non-specified code used).
• Invalid target slave address (exceeds 125).
2208
Unit is not in correct mode, e.g. it is in OFFLINE or STOP
mode.
RUN (0401)
Initiates a state change within the PROFIBUS Master Unit. This command will
enable a pre-allocated slave device in the PROFIBUS Master Unit. The targeted slave device will be added to the Unit’s list of active devices and will be
parameterized by the Unit.
The configured slave devices are by default enabled, but can temporarily be
disabled, i.e. removed from the active device list (see 5-2-3 STOP (0402)).
The targeted slave device is defined by the device code in the command.
Command Format
04
01
Command
code
Device
code
Mode
Response Format
04
01
Command
code
Parameters
Response
code
Device code (command)
Defines the slave device to be enabled state as follows:
High byte:
Always set to 81(Hex).
Low byte:
00 ~ 7D (Hex): Defines the slave device network address.
Mode (command)
Always set to 01 (Hex).
Response Codes
The following end codes can be returned by the Unit in response to the RUN
command:
Response code
126
Description
0000
Normal completion.
0203
Slave device not allocated to the PROFIBUS Master.
0402
Service not supported by Unit model / version.
1001
Command too large.
1002
Command too short.
110C
• Mode code setting not supported (code exceeds 01).
• Invalid device code (High byte not equal to 81)
• Invalid target slave address (exceeds 125).
Command / Response Reference
5-2-3
Section 5-2
STOP (0402)
Initiates a state change within the PROFIBUS Master Unit. This command will
disable a pre-allocated slave device in the PROFIBUS Master Unit. The targeted slave device will temporarily be removed from the Unit’s list of active
devices. The Unit will Unlock the slave device and stop communication with it.
Note The configured slave devices are by default enabled. A disabled slave device
can be enabled using the RUN command (see 5-2-2 RUN (0401)).
The targeted slave device is defined by the device code in the command.
Command Format
04
02
Command
code
Device
code
Response Format
04
02
Command
code
Parameters
Response Codes
Response
code
Device code (command)
Defines the slave device to be enabled state as follows:
High byte:
Always set to 81(Hex).
Low byte:
00 ~ 7D (Hex): Defines the slave device network address.
The following end codes can be returned by the Unit in response to the STOP
command:
Response code
Description
0000
Normal completion.
0203
Slave device not allocated to the PROFIBUS Master.
0402
Service not supported by Unit model / version.
1001
Command too large.
1002
Command too short.
110C
• Mode code setting not supported (code exceeds 01).
• Invalid device code (High byte not equal to 81)
• Invalid target slave address (exceeds 125).
127
Command / Response Reference
5-2-4
Section 5-2
CONTROLLER DATA READ (0501)
Reads the model name and version number data from the PROFIBUS Master
Unit.
Command Format
05
01
Command
code
Response Format
05
01
Command
code
Parameters
Response
code
20 bytes
20 bytes
Model
Version
Model, Version (Response)
The PROFIBUS Master Unit model and version are returned as ASCII characters occupying 20 bytes each (i.e., 20 characters each). If all bytes are not
used, the remaining bytes will be all spaces (ASCII 20 Hex).
Example Model:
Version:
CS1W-PRM21, CJ1W-PRM21
V2.00
Response Codes
Response code
5-2-5
Description
0000
Normal completion.
1001
Command too large
ERROR LOG READ (2102)
Reads a specified number of error records from the error log.
Command Format
21
02
Command Beginning Number
code
record
of records
number
Response Format
21
02
Command Response
code
code
Parameters
10 bytes
Maximum
number
of stored
records
Number
of stored
records
Number
of records
10 bytes each
Error log
records
First Record Number (Command)
The first record to be read. The first record number can be specified in the
range between 0000 and 0050 (0 to 80 decimal) where 0000 is the oldest
record in the Error Log, since the last performed ERROR LOG READ command.
128
Command / Response Reference
Section 5-2
Number of Records (Command, Response)
The number of records to read is specified between 0001 and 0050 (1 to 80
decimal) in the command. The response returns the actual number of records
read.
Maximum Number of Stored Records (Response)
The maximum number of records that can be stored in the error log. In a
PROFIBUS Master Unit, the maximum number of stored records is fixed at 50
(80 decimal).
Number of Stored Records (Response)
The number of records stored at the time the command is executed.
Error Log Data (Response)
The specified number of error log records from the starting record number is
returned sequentially.
The total number of bytes in the error log is calculated as the number of
records x 10 bytes/record. Each error log record thus consist of 10 bytes, configured as follows:
1st byte
Error
code
10th byte
Detailed
information
Month
Year
Hour
Day
Second
Minutes
Error Code, Detailed Information
Details of the error stored in the record. Refer to SECTION 7 Troubleshooting
and Maintenance for details.
Minute, Second, Day, Hour, Year, Month
Indicate the time at which the error stored in the record occurred.
Precautions
The total number of records to be returned is either the number specified in
the command, or the number of available new records in the Error Log, whichever is smaller.
If more then one record is read, the records are returned in a oldest-to-newer
sequence, i.e. the oldest record is the first in the response message.
Response Codes
Response code
Description
0000
Normal completion.
1001
Command too large.
1002
Command too small.
1103
Beginning record number is out of range.
110C
The number of read records is 0.
129
Command / Response Reference
5-2-6
Section 5-2
ERROR LOG CLEAR (0203)
Clears the number of records stored in the PROFIBUS Master Unit error log.
Command Format
21
03
Command
code
Response Format
21
03
Command Response
code
code
Response Codes
Response code
5-2-7
Description
0000
Normal completion.
250F
Memory writing error. Error Log was not cleared normally.
260B
Cannot Clear the Error Log. The error cause still exists.
PROFIBUS MESSAGE SEND (2809)
The PROFIBUS MESSAGE SEND FINS command provides a means to initiate transmission and reception of standard PROFIBUS DP and DP-V1 service over the PROFIBUS network via the CS1/CJ1W-PRM21 PROFIBUS
Master Unit. The general command / response structures are shown below.
Command Format
PROFIBUS service data
28
09
Command
code
Device
address
PROFIBUS command
specific data
Device Service
Access Point
Response Format
28
09
Command
code
Parameters
130
Response
code
PROFIBUS service data
The PROFIBUS service data part in both the command and response
depends on the PROFIBUS service to be transmitted / received, and will
therefore be different in length and contents for every service. Also, the
response error codes will depend on the services requested. The common
parameters are described below. Each supported service will be described
separately after the common parameters.
Command / Response Reference
Section 5-2
Destination Address (Command)
The address of the device on the PROFIBUS network, to which the PROFIBUS message will be sent. The valid address range is 0 to 7E (Hex).
Device Service Access Point (Command)
The Device Service Access Point is a 1 byte number, identifying the PROFIBUS service to the slave device, as defined by the PROFIBUS standard.
The table below lists the PROFIBUS services supported using the PROFIBUS MESSAGE SEND FINS command.
PROFIBUS Service
DSAP
(Hex)
Description
Page
Set_Slave_Add
37
Change the address of a slave device.
Rd_Inp
38
Read the Input data of a slave device.
131
133
Rd_Outp
39
Read the Output data of a slave device.
134
Get_Cfg
3B
Read the PROFIBUS DP I/O Configuration of a slave device.
135
MSAC1_Read
33
Read PROFIBUS DP-V1 data from a
PROFIBUS DP-V1 slave device.
136
MSAC1_Write
33
Write PROFIBUS DP-V1 data to a
PROFIBUS DP-V1 slave device.
138
Set_Slave_Add Service
The PROFIBUS DP Set_Slave_Add service allows a PROFIBUS Master Unit
to change the address of a remote slave device. It is defined for slave devices
of which the PROFIBUS address can not be set through switches. Slave
devices which support this service also provide a means to store the address
in internal non-volatile memory. In case this non-volatile memory does not
contain an entry, the slave device will assume the default address 126.
The figures below show the command and response message formats.
Command Format
28
09
Command
code
Device
address
PROFIBUS
Ident Number
Device Service
Access Point
Response Format
28
Additional slave data
Address
change lock
New device
address
09
Command Response
code
code
Parameters
Destination Address (Command)
The address of the device on the PROFIBUS network, to which the PROFIBUS message will be sent. The valid address range is 0 to 7E (Hex).
Device Service Access Point (Command)
The Device Service Access Point for the Set_Slave_Add PROFIBUS service
must be set to 37 (Hex).
131
Command / Response Reference
Section 5-2
PROFIBUS Ident Number (Command)
The PROFIBUS Ident Number is a 1 word identifier, issued by PROFIBUS
International, which identifies the slave device type and model. The number
can be obtained form the slave device GSD file or from the slave documentation.
New Device Address (Command)
Contains the new address of the device. The valid address range is 0 to 7E
(Hex).
Address Change Lock (Command)
Enables address lock, after changing it. Valid range:
• 00 Disable Address Lock
• 01: Enable Address Lock
!WARNING Enabling Address Lock makes any future changes of the address impossible,
even after power-down/power-up of the slave device.
Response Codes
Response code
132
Description
0000
Normal completion
1001
Command too large, i.e. > 124 words
1002
Command too short, i.e. < 4 words.
110C
•
•
•
•
2208
PROFIBUS Master unit not in correct mode, i.e. it is in
OFFLINE mode.
0001
• The slave has deactivated this service.
• The slave has not responded to the request.
• The slave does not have sufficient memory space for the request data.
• New Address is same as current master address.
0402
Service is not supported: Device Service Access Point is
invalid.
Device Address Invalid, i.e. > 7E (Hex)
New Device Address Invalid, i.e. > 7E (Hex)
Address change lock invalid, i.e. not equal to 00 or 01.
Invalid target slave address (exceeds 125).
Command / Response Reference
Section 5-2
Rd_Inp Service
The PROFIBUS DP Rd_Inp service allows a PROFIBUS Master Unit to read
the current input data of any slave device, even if it is not allocated to the Master Unit.
The figures below show the command and response message formats.
Command Format
28
38
09
Command
code
Device
address
Device Service
Access Point
Response Format
28
09
Command
code
Parameters
Response
code
Device
Data length
address (Bytes)
Input data
Destination Address (Command, Response)
The address of the device on the PROFIBUS network, to which the PROFIBUS message will be sent. The valid address range is 0 to 7E (Hex). The
most significant byte in the Response Format is set to 00.
Device Service Access Point (Command)
The Device Service Access Point for the Rd_Inp PROFIBUS service must be
set to 38 (Hex).
Data length (Bytes) (Response)
This parameter defines the number of Input data bytes returned by the slave
device. The number ranges from 0 to 244 bytes. The most significant byte is
set to 00.
Input data (Response)
Input data returned by the slave device.
Response Codes
Response code
Description
0000
Normal completion
1001
Command too large, i.e. > 2 words
1002
Command too short, i.e. < 2 words.
110C
Device Address Invalid, i.e. > 7E (Hex)
2208
PROFIBUS Master unit not in correct mode, i.e. it is in
OFFLINE mode.
0001
• The slave has deactivated this service.
• The slave has not responded to the request.
• The slave does not have sufficient memory space for the request data.
• Destination address is same as current master address.
0402
Service is not supported: Device Service Access Point is
invalid.
133
Command / Response Reference
Section 5-2
Rd_Outp Service
The PROFIBUS DP Rd_Outp service allows a PROFIBUS Master Unit to read
the current output data of any slave device, even if it is not allocated to the
Master Unit.
The figures below show the command and response message formats.
Command Format
28
39
09
Command
code
Device
address
Device Service
Access Point
Response Format
28
09
Command
code
Parameters
Response
code
Device
Data length
address (bytes)
Output data
Destination Address (Command, Response)
The address of the device on the PROFIBUS network, to which the PROFIBUS message will be sent. The valid address range is 0 to 7E (Hex). The
most significant byte in the Response Format is set to 00.
Device Service Access Point (Command)
The Device Service Access Point for the Rd_Outp PROFIBUS service must
be set to 39 (Hex).
Data length (Bytes) (Response)
This parameter defines the number of Output data bytes returned by the slave
device. The number ranges from 0 to 244 bytes. The most significant byte is
set to 00.
Output Data (Response)
Output data returned by the slave device.
Response Codes
Response code
134
Description
0000
Normal completion
1001
Command too large, i.e. > 2 words
1002
Command too short, i.e. < 2 words.
110C
Device Address Invalid, i.e. > 7E (Hex)
2208
PROFIBUS Master unit not in correct mode, i.e. it is in
OFFLINE mode.
0001
• The slave has deactivated this service.
• The slave has not responded to the request.
• The slave does not have sufficient memory space for the request data.
• Destination address is same as current master address.
0402
Service is not supported: Device Service Access Point is
invalid.
Command / Response Reference
Section 5-2
Get_Cfg Service
The PROFIBUS DP Get_Cfg service allows a PROFIBUS Master Unit to read
the I/O Configuration data of any slave device, even if it is not allocated to the
Master Unit.
The figures below show the command and response message formats.
Command Format
28
3B
09
Command
code
Device
address
Device Service
Access Point
Response Format
28
09
Command
code
Parameters
Response
code
Device
Data length I/O Configuration
address (bytes)
data
Destination Address (Command, Response)
The address of the device on the PROFIBUS network, to which the PROFIBUS message will be sent. The valid address range is 0 to 7E (Hex). The
most significant byte in the Response Format is set to 00.
Device Service Access Point (Command)
The Device Service Access Point for the Get_Cfg PROFIBUS service must be
set to 3B (Hex).
Data length (Bytes) (Response)
This parameter defines the number of I/O Configuration bytes returned by the
slave device. The number ranges from 0 to 244 bytes. The most significant
byte is set to 00.
I/O Configuration data (Response)
I/O Configuration data returned by the slave device. The I/O Configuration
bytes are coded according to the PROFIBUS standard.
Response Codes
Response code
Description
0000
Normal completion
1001
Command too large, i.e. > 2 words
1002
Command too short, i.e. < 2 words.
110C
Device Address Invalid, i.e. > 7E (Hex)
2208
PROFIBUS Master unit not in correct mode, i.e. it is in
OFFLINE mode.
0001
• The slave has deactivated this service.
• The slave has not responded to the request.
• The slave does not have sufficient memory space for the request data.
• Destination address is same as current master address.
0402
Service is not supported: Device Service Access Point is
invalid.
135
Command / Response Reference
Section 5-2
MSAC1_Read Service
The PROFIBUS DP-V1 MSAC1_Read service allows a PROFIBUS DP-V1
Master Unit to read (parameter) data acyclically from a PROFIBUS DP-V1
slave device, which is allocated to that Master unit.
The figures below show the command and response message formats.
Command Format
28
09
33
Command
code
Device
address
00
5E
Function
code
Slot
number
Device Service
Access Point
Response Format
Data length
(bytes)
Index number
Upon normal completion of the MSAC1_Read command service two types of
response frames can be returned:
• A normal data response frame containing the requested data.
• A normal response frame containing PROFIBUS error codes, indicating
that the PROFIBUS service was not completed correctly, although the
FINS message was completed normally.
Both response frames are shown below.
28
09
00
5E
Command Response
code
code
Function
code
28
00
09
Command Response
code
code
Actual data
length read
(bytes)
Data
DE
Function
code
Error
decode
Error
code 2
Error
code 1
Parameters
Destination address (Command, Response)
The address of the device on the PROFIBUS network, to which the PROFIBUS message will be sent. The valid address range is 0 to 7E (Hex). The
most significant byte in the Response Format is set to 00.
Device Service Access Point (Command)
The Device Service Access Point for the MSAC1_Read PROFIBUS service
must be set to 33 (Hex).
Function code (Command, Response)
The function code is defined by the PROFIBUS standard and defines the type
of MSAC1 message. In the command it must be fixed to 005E (Hex). The
response will contain either 005E (Hex) indicating a normal PROFIBUS completion, or 00DE (Hex), indicating PROFIBUS errors.
136
Command / Response Reference
Section 5-2
Slot number (Command)
The parameter Slot_Number is used in the destination device for addressing
the desired data slot (typically an I/O module). The number ranges from 0 to
254.
Index number (Command)
The parameter Index is used in the destination device for addressing the
desired data block within a specified slot. The number ranges from 0 to 254.
Data length (Bytes) (Command)
The Data length indicates the number of bytes, which have to be read. If the
actual data block length is less than requested, the length in the response will
be the actual length of the data block. If the actual data block length is greater
or equal than requested, the response will contain the requested length of
data. The number ranges from 0 to 240.
Data (Response)
Requested data block as retrieved from the PROFIBUS DP-V1 slave device.
Error decode (Response)
The Error decode byte defines the type of errors reported in the Error code 1
and Error code 2, e.g. a PROFIBUS DP-V1 error.This response will only be
returned if the FINS message was delivered successfully, but the PROFIBUS
service returned an error. Refer to Appendix B-5 PROFIBUS DP-V1 Error
codes for more information.
Error code 1, Error code 2 (Response)
The contents of the Error code bytes depends on the contents of the Error
decode byte and the slave device. Refer to Appendix B-5 PROFIBUS DP-V1
Error codes for more information.
Response Codes
Response code
Description
0000
Normal completion
1001
Command too large, i.e. > 5 words
1002
Command too short, i.e. < 5 words.
110C
•
•
•
•
2208
PROFIBUS Master unit not in correct mode, i.e. it is in
OFFLINE mode.
0001
• The slave has deactivated this service.
• The slave has not responded to the request.
• The slave does not have sufficient memory space for the
request data.
• Destination address is same as current master address.
0402
Service is not supported:
• Device Service Access Point is invalid.
• The Function code is invalid
Device Address Invalid, i.e. > 7E (Hex).
The slot number is invalid, i.e. > FE (Hex).
The Index number is invalid, i.e. > FE (Hex).
The Data Length is invalid, i.e. > F0 (Hex)
137
Command / Response Reference
Section 5-2
MSAC1_Write Service
The PROFIBUS DP-V1 MSAC1_Write service allows a PROFIBUS DP-V1
Master Unit to write (parameter) data acyclically to a PROFIBUS DP-V1 slave
device, which is allocated to that Master unit.
The figures below show the command and response message formats.
Command Format
28
09
33
Command
code
Device
address
00
5F
Function
code
Data
Slot
number
Device Service
Access Point
Response Format
Data length
(bytes)
Index number
Upon normal completion of the MSAC1_Write command service two types of
response frames can be returned:
• A normal data response frame, signalling successful completion of both
the FINS command and the PROFIBUS service.
• A normal response frame containing PROFIBUS error codes, indicating
that the PROFIBUS service was not completed correctly, although the
FINS message was completed normally.
Both response frames are shown below.
28
09
00
5F
Command Response
code
code
Function
code
28
00
09
Command Response
code
code
Actual length
of data written
(bytes)
DF
Function
code
Error
decode
Error
code 2
Error
code 1
Parameters
Destination address (Command, Response)
The address of the device on the PROFIBUS network, to which the PROFIBUS message will be sent. The valid address range is 0 to 7E (Hex). The
most significant byte in the Response Format is set to 00.
Device Service Access Point (Command)
The Device Service Access Point for MSAC1 PROFIBUS services must be
set to 33 (Hex).
Function code (Command, Response)
The Function code is defined by the PROFIBUS standard and specifies the
type of MSAC1 message. For the MSAC1_Read service it must be fixed to
005F (Hex). The Response Format will contain either 005F (Hex) indicating a
normal PROFIBUS completion, or 00DF (Hex), indicating PROFIBUS errors.
138
Command / Response Reference
Section 5-2
Slot number (Command)
The parameter Slot number is used in the destination device for addressing
the desired data slot (typically an I/O module). The number ranges from 0 to
254.
Index number (Command)
The parameter Index is used in the destination device for addressing the data
block within a specified slot to which the data must be written. The number
ranges from 0 to 254.
Data length (Bytes) (Command, Response)
The Data length indicates the number of bytes, which must be written. If the
actual data block length is less than the length of the data written, the
response will contain an error code in the Error code 1 byte. If the actual data
block length is greater or equal than the length of the data block written, the
response will contain the actual number of bytes written. The data length
number ranges from 0 to 240.
Data (Command)
Data to be written to the PROFIBUS DP-V1 slave device.
Error decode (Response)
The Error decode byte defines the type of errors reported in the Error code 1
and Error code 2, e.g. PROFIBUS DP-V1 error. This response will only be
returned if the FINS message was delivered successfully, but the PROFIBUS
service returned an error. Refer to Appendix B-5 PROFIBUS DP-V1 Error
codes for more information.
Error code 1, Error code 2 (Response)
The contents of the Error code bytes depends on the contents of the Error
decode byte and the slave device. Refer to Appendix B-5 PROFIBUS DP-V1
Error codes for more information.
Response Codes
Response code
Description
0000
Normal completion
1001
Command too large, i.e. > 125 words
1002
Command too short, i.e. < 5 words.
110C
•
•
•
•
2208
PROFIBUS Master unit not in correct mode, i.e. it is in
OFFLINE mode.
0001
• The slave has deactivated this service.
• The slave has not responded to the request.
• The slave does not have sufficient memory space for the
request data.
• Destination address is same as current master address.
0402
Service is not supported:
• Device Service Access Point is invalid.
• The Function code is invalid
Device Address Invalid, i.e. > 7E (Hex).
The slot number is invalid, i.e. > FE (Hex).
The Index number is invalid, i.e. > FE (Hex).
The Data Length is invalid, i.e. > F0 (Hex)
139
SECTION 6
Operation
This section describes how to operate the CS1/CJ1W-PRM21 PROFIBUS Master Unit in a Network. It will discuss setting
up a network, configuring all the connected devices and starting the network. Furthermore, it provides information the I/O
data exchange performance and it also provides information on how to monitor a network, using the Unit and CX-Profibus.
6-1
6-2
6-3
6-4
6-5
6-6
6-7
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Setting up a network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-2-1 Adding Devices to the Network . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-2-2 Changing Device and DTM Addresses . . . . . . . . . . . . . . . . . . . . . .
Configuring the Slave Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-3-1 Defining the I/O configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-3-2 Setting Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-3-3 Selecting the Group Assignment . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring the Master . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-4-1 Setting the Master Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-4-2 Setting the Bus Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-4-3 Defining and Changing I/O Mapping . . . . . . . . . . . . . . . . . . . . . . . .
6-4-4 Configuring CX-Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-4-5 Downloading the Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . .
I/O Communication Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-5-1 I/O Data Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-5-2 Mapping I/O Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-5-3 Supported Data Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-5-4 Exchanging I/O Data over PROFIBUS . . . . . . . . . . . . . . . . . . . . . .
6-5-5 PLC Cycle Time Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-5-6 I/O Response Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-5-7 System Startup Time. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Operating the Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-6-1 User Access to the Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-6-2 Changing PROFIBUS Mode of the Master Unit . . . . . . . . . . . . . . .
6-6-3 Transmitting Global-Control Commands . . . . . . . . . . . . . . . . . . . . .
6-6-4 Using Auto-CLEAR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-6-5 Initiating PROFIBUS DP-V1 Services. . . . . . . . . . . . . . . . . . . . . . .
Monitoring the Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-7-1 Monitoring the Master Unit and the Network . . . . . . . . . . . . . . . . .
6-7-2 Monitoring Slave Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-7-3 Using the Error Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
142
142
144
146
149
149
152
153
154
155
157
158
159
161
162
162
162
169
170
172
172
175
176
176
177
179
183
184
185
185
189
190
141
Introduction
6-1
Section 6-1
Introduction
This section discusses the operational aspects of using the PROFIBUS Master Unit and the configuration software. The section has been setup, to follow
the general process flow of setting up and configuring a network, downloading
the configuration, and operating the PROFIBUS network.
Note
1. In case Error messages are displayed, while using CX-Profibus, refer to
Appendix D Configurator Error and Warning Messages for more information on errors.
2. This section does not discuss how to operate the C200HW-PRM21
PROFIBUS DP Master Unit. For more information on how to operate this
type of unit, refer to the C200H-series PROFIBUS Master Units Operation
Manual ([email protected]).
Example
6-2
To illustrate the explanations, examples are marked with the word Example in
the side line.
Setting up a network
Starting CX-Profibus
Setting up a network involves setting up a configuration in CX-Profibus and
downloading it to the PROFIBUS Master Unit. To start CX-profibus, select
Program, OMRON, and CX-Profibus, from the Start Menu if the default program folder name is used.
The Login Window will be displayed. Login as either Administrator or Planning Engineer.
Note The default password for all levels is “password”.
CX-Profibus will now start, displaying the main window, as shown below.
142
Setting up a network
Section 6-2
Before starting the assembly of the network in CX-Profibus, make the following preparation steps.
1,2,3...
1. Open the Device Catalogue: Either select the View - Device Catalogue
menu option, or press the
Catalogue is shown below.
button in the Tool Bar. The opened Device
2. Check the list of available DTMs, and verify that all the devices that need
to be added to the Network - both master and slave devices - are among
the DTMs in the list.
3. If one or more of the DTMs is missing, these DTMs must first be installed
and the Device Catalogue updated.
Note
1. Non-GSD file based DTMs are usually provided with their own setup program. Installation of these DTMs must be performed outside CX-Profibus,
e.g. from Windows Explorer.
2. In case of DTM installations outside CX-Profibus, always initiate an update
of the Device Catalogue, before assembling a network. Without this update the newly installed DTM will not appear in the list of devices. To Update the Device Catalogue, press the Update button in the Device
Catalogue main window.
3. An Update must also be performed when an already existing DTM is upgraded. Without the update, the old version number will still be shown in
the list. Failure to update the Device Catalogue in this case may also result
in undesired behaviour, when adding these DTMs to the Network.
Installing New GSD Files
1,2,3...
GSD file based DTMs can be installed from within the Device Catalogue main
window. To do so, follow the procedure below.
1. Press the Install GSD File... button at the bottom of the Device Catalogue
main window (refer to figure above). The standard windows File - Open
window will be displayed.
2. In the File - Open window browse to the sub-directory containing the GSD
file, select the (one or more) GSD file(s) and press the Open button in the
143
Setting up a network
Section 6-2
window. The GSD file(s) will be copied to a sub-directory of the CX-Profibus directory.
3. After completing the copy, a window will be displayed, asking the user permission for an update of the Device Catalogue (see figure below). If more
GSD files need to be installed, select the No button and continue with installation of GSD file. Otherwise, select the Yes button.
Note Updating the Device Catalogue may take several minutes, depending on the
number of installed GSD files.
6-2-1
Adding Devices to the Network
If the Device Catalogue is up to date, it can be used to setup the network. Setting up a network in CX-Profibus starts with adding single device DTMs to the
Network view. First the CS1/CJ1W-PRM21 Master DTM must be added to the
main branch of the project Network. To do so, one of three procedures as outlined below must be used to add the DTM.
Using the Context Menu
1,2,3...
1. Select the top of the network to which the DTM must be added, i.e. select
MyNetwork in the Network view.
2. Right click the mouse and a context menu will be displayed.
3. From the menu select Add Device.
4. A simplified Device Catalogue is displayed. The list only contains the devices which can be inserted at the selected network location (see figure below, only Master devices are listed).
5. From the displayed list, select the device DTM to be added and select the
OK button. The Device DTM will be added to the network.
144
Setting up a network
Section 6-2
Using Drag & Drop
1,2,3...
1. Open the Device Catalogue: Either select the View - Device Catalogue
menu option, or press the
button in the Tool Bar.
2. Select a device DTM in the Device Catalogue.
3. Left click the mouse and Drag the mouse pointer to the desired location in
the network, i.e. MyNetwork in the Network view.
4. Release the mouse button and the device DTM will be added to that location.
Note Master DTMs can only be added to the main branch of the Network.
Slave Device DTMs can only be added to Master DTMs. Whether or
not a DTM can be added to the branch is indicated by the cursor:
indicates no addition,
indicates that addition is allowed.
Using the Add Device Button
1,2,3...
1. Select the top of the network to which the DTM must be added, i.e. select
MyNetwork in the Network view.
2. Open the device Catalogue: Either select the View - Device Catalogue
menu option, or press the
button in the Tool Bar.
3. Select the device that must be added to the network.
4. Select the Add Device button at the bottom of the Device Catalogue window. The device DTM is added to the network.
Note If a DTM is selected in the Device Catalogue, which can not be added to the current location in the network, the Add Device button will
be disabled, which is shown as a grayed out button.
Note When adding a CS1/CJ1W-PRM21 Master DTM to the network, it is automatically assigned the PROFIBUS network address 1. This address can be
changed, after opening the CS1/CJ1W-PRM21 Master DTM.
After adding the Master DTM to the Network view, repeat (one of) the procedures as outlined above to add slave DTMs to the Master DTM. In the procedures above, the highest level for adding slave DTMs is the Master DTM.
Note When adding slave DTMs to the CS1/CJ1W-PRM21 Master DTM, they are
automatically assigned their PROFIBUS network addresses, in ascending
order, i.e. the first slave is assigned address 2, the second address 3, etc.
The addresses can be changed in the slave DTM User Interface.
145
Setting up a network
Example
Section 6-2
The figure below shows an example network consisting of a CJ1W-PRM21
PROFIBUS Master and three OMRON slave devices.
Note that the slave DTMs all have the automatically assigned network
addresses, displayed to the left of the device name.
6-2-2
Changing Device and DTM Addresses
In order to achieve communication between the Master Unit and its allocated
slave devices, the latter must have the same physical network address as set
in the configuration. The network address on the slave devices are usually set
• through dip-switches or rotary switches on the device, or
• remotely, using the dedicated Set_Slave_Add PROFIBUS service and
stored in the device.
The physical address setting may differ from the slave DTM address, which
was automatically assigned by the Master DTM.
Changing the Slave
Device Address
Slave devices which are not equipped with switches to set the address, must
support the Set_Slave_Add PROFIBUS service. Typical device types supporting this address setting method are PROFIBUS PA devices or IP65
devices.
The default address for these devices is 126. This allows them to communicate with a Master unit, with the purpose of changing the address. I/O data
exchange with slave address 126 is not allowed. Usually, these slave devices
also provide a means to store the remotely set address in local non-volatile
memory.
As of Unit version 2.0, the CS1/CJ1W-PRM21 PROFIBUS Master units support the Set_Slave_Add PROFIBUS service, which can be initiated from the
Master DTM. This service can be sent to any slave on the network, even if it is
not allocated to the Master DTM.
In order to change a slave device’s address remotely, first make sure that the
Master DTM is on-line with the Master. Next, open the Set Device Station
Address window:
1,2,3...
1. Select the DTM in the Network view.
2. Right click the mouse, and select the Additional functions entry from the
context menu.
3. Select the Set Device Station Address option
The window as shown below is displayed.
146
Setting up a network
Section 6-2
In order to change the address of a slave device perform the following steps:
1,2,3...
1. Enter the device’s current address and its PROFIBUS Ident Number.
The PROFIBUS Ident Number can be found in the Generic Slave DTM or
through the device’s documentation. By default the device’s current address will be 126. If necessary, change this to the actual current address.
2. Enter the new device address in the New Address field.
3. Optionally, select the Lock checkbox, if the address change must be made
permanent.
4. Press the Set button to invoke the PROFIBUS DP Set Slave Address service. The Status field will display the status of this service.
!WARNING Selecting the Lock option makes any future changes of the address impossible, even after power-down/power-up of the slave device.
Note After successful completion of the address change, the device DTM address
in the Network view has to be changed as well.
Changing the Slave DTM
Address
When assembling the PROFIBUS configuration in the Network view, the Master DTM automatically assigns addresses in ascending order to the slave
DTMs. If the physical address on the slave device differs from the DTM
address, the DTM address must be changed to match that setting.
Changing the DTM address can be done in two ways.
• Change the DTM address through the Generic Slave DTM
• Change the DTM address through the Slave DTM Address Assignment
table via the Master DTM.
Changing the DTM
address via the Generic
Slave DTM
The first option, using the Generic Slave DTM is illustrated in the example
below.
Example
Assume that the F150-PRT Vision system in the previous example, has an
actual network address of 10, instead of 4, which was automatically assigned.
In order to change the network address of the F150-PRT (or any other slave
device), perform the procedure outlined below.
1,2,3...
1. Open the Configuration User Interface for the slave device, by selecting it
in the Network view, and double-clicking the left mouse button.
2. Select the Station Address field at the top of the Configuration tab (see figure below) and change the value to 10.
147
Setting up a network
Section 6-2
3. Select the OK or Apply button at the bottom of the window. The OK button
will close the DTM Configuration User Interface.
Note If, when pressing the Apply or OK button, no I/O modules have been selected
as yet, a warning message will be displayed. The I/O modules can be
selected later. Pressing the OK button with the warning, will apply the
changed device address.
After changing the address in the slave DTM Configuration User Interface, the
updated address will be shown in the Network view, next to the device name.
Changing the DTM
address via the Master
DTM
1,2,3...
The slave DTM address can also be changed via the Master DTM. To accomplish this, first open the Slave DTM Address Assignment table.
1. Select the Master DTM in the Network view.
2. Right click the mouse, and select the Additional functions entry from the
context menu.
3. Select the Slave DTM Address Assignment function.
148
Configuring the Slave Devices
Section 6-3
The window as shown below will be displayed.
In order to change the slave DTM address perform the following steps.
1,2,3...
1. Select the slave device in the list.
2. Enter the new address in the field Address in the lower right corner of the
window.
Press the Set button. The Status field will display the status of this service
After changing the slave DTM address, the new address will also be shown in
the Network view.
6-3
Configuring the Slave Devices
After adding each of the slave DTMs to the network, configurations have to be
selected for each of them. Setting up a configuration involves
• Selecting the proper I/O modules, which define the I/O data to be
exchanged when operational.
• Setting up the device parameters, which will be send to the device to
make or verify its settings.
• Selecting the group assignment, which defines the group of slave devices
each slave belongs to and to allow sending Global-Control commands to
this particular group.
All these settings will be downloaded to the Master Unit, which will send the
data to the individual slave devices over the PROFIBUS network.
6-3-1
Defining the I/O configuration
Opening the DTM
Configuration User
Interface
In order to define the I/O configuration, the DTM Configuration User Interface
must be opened. To do this, either
• select the device in the Network view and double-click the left mouse button.
• select the device in the Network view, right click the mouse and select
Configuration from the context menu.
149
Configuring the Slave Devices
Example
Section 6-3
The figure below, shows the DTM User Interface for the CJ1W-PRT21 PROFIBUS DP slave device.
The DTM Configuration User Interface displays two lists.
• The Available Modules list, which contains the I/O modules the user can
select.
• The Configured Modules list, which contains all the I/O modules selected
by the user.
Adding/Inserting I/O
Modules
To select the I/O modules, perform one of the following procedures.
• Select the I/O module that needs to be added in the Available Modules
list, and double-click it with the left mouse button. If more than one module must be added, repeat this step for the other modules.
• Select the I/O module that needs to be added in the Available Modules
list, and press either the Insert or Append button. This method allows
selection of more than one module, by pressing either the Shift or the Ctrl
key on the keyboard, while selecting the modules.
Note
1. When pressing the Insert button, the selected I/O module will be inserted
above the selected module in the Configured Modules list.
2. The selected I/O modules are sent to the slave device, in the same sequence as selected in the user interface. Depending on the device, the sequence may be checked by the slave device. If an incorrect sequence is
sent, the I/O configuration is rejected. This is for example the case with the
OMRON PRT1-COM Multiple I/O PROFIBUS DP Interface.
3. A mandatory I/O module sequence is sometimes indicated in the GSD file,
by using non-PROFIBUS standard GSD file keywords (i.e. only interpreted
by a specific configurator). The Generic Slave DTM does not check such
keywords. In this case, refer to the manual of the specific device for details.
150
Configuring the Slave Devices
Section 6-3
4. Also in this window are the maximum values, which can be set, and the totals of I/O data that actually have been set. If - while selecting I/O modules
- one of the maximum values is exceeded, a warning message will be displayed.
Example
For the CJ1W-PRT21, the first four I/O modules have been selected, see figure below.
Removing I/O Modules
To remove I/O modules from the Configured Modules list, perform one of the
following procedures.
• Select the I/O module that needs to be removed from the Configured
Modules list, and double-click it with the left mouse button. If more than
one module must be added, repeat this step for the other modules.
• Select the I/O module that needs to be removed from the Configured
Modules list, and press either the Remove button. This method allows
selection of more than one module, by pressing either the Shift or the Ctrl
key on the keyboard, while selecting the modules.
Watchdog Settings
Apart from the I/O module selection, the Configuration tab also contains the
settings for two other parameters.
1. Enable Watchdog Control
This parameter will enable/disable the monitoring of the Master-Slave
communication in the slave device. If enabled, the slave will stop I/O data
exchange with the Master, if the Master has not send any request message
to the slave, within the configured Watchdog time. Furthermore, the slave
will
• switch its outputs to a known state.
• signal its change of state in a diagnostics message, the next time the
Master addresses the slave.
151
Configuring the Slave Devices
Section 6-3
• request re-parameterization from the Master, before resuming I/O data
exchange.
If disabled, the slave will remain in data exchange, even if the Master is not
communicating, thus maintaining its outputs in the latest known state,
based on the last I/O data exchange message.
2. Watchdog Interval
This value is the watchdog timeout related to the Master-Slave communication time out.
Note Enabling the Watchdog Control is highly recommended for safe operation of
the network.
!Caution In the current version of CX-Profibus, the watchdog value for each of the slave
devices is overruled by the value determined by the Master DTM. Therefore,
changing the value in the Generic Slave DTM has no effect.
When done, making the I/O configuration settings, press the Apply button at
the bottom of the window. Next, select the Parameter tab, to make the necessary parameter selections.
6-3-2
Setting Parameters
The parameters are sent by the Master Unit to the slave device prior to establishing I/O data exchange. The slave device will reject incorrect parameters
and not establish I/O data exchange, unless the parameters are changed.
In general there will be two types of parameters.
• Common Parameters
Most of the slave devices require at least the common parameters. These
parameters apply to the whole slave device.
• Module Parameters
Modular slaves often apply parameters related to a specific I/O module,
e.g. the physical slave device consist of a number of hardware modules,
each defining an amount of I/O data, requiring its I/O module selection
and requiring its own parameters.
152
Configuring the Slave Devices
Example
Section 6-3
The Parameter tab of the CJ1W-PRT21 is shown in the figure below. It lists
the common parameters for the CJ1W-PRT21.
In the figure above, the parameter captions are listed in the left column and
the options can be set in the right column. In order to change settings, doubleclick the required parameter row with the left mouse button. Depending on the
parameter type, either a drop-down lists will become available for selection or
a value can be entered.
Example
In the figure above, the parameter setting allowing the user to define the target location of the output data in the PLC memory has been selected.
Note Readable captions and/or convenient selection items are not always provided
with the parameters. Depending on the slave device and the GSD file implementation, setting the parameter values may require the help of the user documentation for that slave.
6-3-3
Selecting the Group Assignment
The group assignment is sent to the slave devices as part of the parameter
message. The group assignment is used as an address within the GlobalControl command message (see section 6-6-3 Transmitting Global-Control
Commands), to address a specific group of slaves, or all slaves. To set a
slave device’s group address, perform the following steps.
1,2,3...
1. Open the Configuration User Interface of the Generic Slave DTM the specific slave device.
2. Select the Group tab.
3. Select the checkbox next to the group numbers for all the groups to which
the slave device will belong.
4. Select the Apply button at the bottom of the User Interface.
153
Configuring the Master
Example
Section 6-4
Assigning slave devices to groups is application dependent. The figure below
shows the Group selection tab for the CJ1W-PRT21, which has been
assigned to groups 1, 2 and 4.
After making the group assignment, press the OK button to save the changes
and close the DTM Configuration User Interface.
6-4
Configuring the Master
Opening the Master DTM
Configuration Interface
After configuring all the slave DTMs, the CS1/CJ1W-PRM21 Master DTM
must be configured. In order to open the Master DTM Configuration Interface
do either one of the following.
• Select the CS1/CJ1W-PRM21 Master DTM in the Network view and double-click the left mouse button.
• Select the CS1/CJ1W-PRM21 Master DTM in the Network view, and
right-click the mouse. From the context menu, select Configuration.
154
Configuring the Master
Section 6-4
The DTM Configuration User Interface is shown below.
Master Address
In the first tab, the device address and the unit number must be set. The
device address can be set in the range from 0 to 125.
Unit Number
The setting of the unit number is required to setup communication with the
Unit through CX-Server. The setting in the user interface must match the setting made with the rotary switch on the front of the Unit.
Note The device address is normally assigned automatically. Only in the case
where there are other devices in the network which have the same address,
the device address of the CS1/CJ1W-PRM21 Master DTM may need to be
changed.
After making the changes, select the Save button in the lower right corner of
the user interface to accept the changes. Next select the Master Setup tab, to
display the Master Setup options.
6-4-1
Setting the Master Parameters
Master Setup Tab
The Master Setup tab defines
• the behaviour of the Master Unit, when the PLC CPU switches its mode
between RUN / MONITOR and PROGRAM mode.
• The behaviour of the Master Unit in case an error occurs in one of the
slave devices allocated to the Master Unit.
• The method of I/O data mapping.
155
Configuring the Master
Section 6-4
The figure below shows the Master Setup tab.
Unit Behaviour upon PLC
Mode Changes
The user can select the way the Unit will behave if the PLC mode is changed.
The default settings are:
• Set the Unit’s operational mode to CLEAR (i.e. set all outputs to a safe
state), when switching the PLC CPU to PROGRAM mode.
• Set the Unit’s operational mode to OPERATE (i.e. start I/O data exchange
with the slave devices), when switching the PLC CPU to RUN / MONITOR
mode.
Note
1. The advantage of this setting is that the user does not have program the
starting of the network. The disadvantage is that the moment at which the
network is started is out of direct control of the PLC user program. I/O data
exchange is started, while the program may still be initializing its memory.
Depending on the application this may have unexpected effects.
2. To avoid potential problems at startup, it is recommended to set the network operational mode to ‘keep current mode’ in case the PLC mode in
case the PLC mode changes to RUN / MONITOR and to set the operational mode to CLEAR in case the PLC mode changes to PROGRAM. This requires the PLC user program to switch the network to OPERATE, after
startup. Refer to section 6-6-2 Changing PROFIBUS Mode of the Master
Unit for a programming example.
3. A side effect of the default settings can be that the network is started right
after downloading the parameters to the CS1/CJ1W-PRM21 PROFIBUS
Master Unit. After downloading the parameters, the CS1/CJ1W-PRM21
Master DTM will restart the Unit and switch the PLC mode back from PROGRAM mode to the mode it had before downloading. This can be RUN /
MONITOR mode.
Auto-CLEAR behaviour
The Auto-CLEAR behaviour defines how the CS1/CJ1W-PRM21 PROFIBUS
Master Unit will behave in case one of its allocated slave devices fails during I/
O data exchange. This option can be enabled if the application in which the
Master Unit is used warrants safety precautions to be taken to prevent unexpected behaviour of the application.
If Auto-CLEAR has been enabled, the Master Unit will automatically transition
to the CLEAR state and set the allocated slave device outputs to the safe
state. Refer to section 6-6-4 Using Auto-CLEAR, for a description of how to
use the Auto-CLEAR function.
156
Configuring the Master
Auto-Addressing
Section 6-4
Auto-Addressing defines whether or not the CS1/CJ1W-PRM21 Master DTM
will automatically map the I/O data in such a way that no gaps exist in the I/O
data. If enabled, the user does not need to handle the exact mapping of I/O
data on to the PLC memory areas. Refer to section 6-4-3 Defining and
Changing I/O Mapping for more information on I/O data mapping.
After making the changes, select the Save button in the lower right corner of
the user interface to accept the changes. Next select the Bus Parameter tab
to display the Bus Parameters.
6-4-2
Setting the Bus Parameters
The Bus Parameter setup tab contains all the settings required to setup the
communication cycles on the network. The settings depend on the selected
baud rate, the number of slaves, the amount of I/O data per slave, etc.
By default, the CS1/CJ1W-PRM21 Master DTM will calculate the bus parameters, based on this information.
!Caution Although the user can decide to modify some of these parameters, it is not
recommended to do that. Making the wrong configuration may lead to unexpected behaviour.
Example
An example of the Bus Parameter tab is shown below.
The baud rate has been set to 1500 kBit/s. The amount of slaves and the
amount of I/O data, results in a poll cycle time of approximately 3.8 ms (Min
Slave Interval).
After making the changes, select the Save button in the lower right corner of
the user interface to accept the changes. Next select the Slave Area tab to
display the I/O Mapping.
157
Configuring the Master
6-4-3
Section 6-4
Defining and Changing I/O Mapping
The I/O data of all slaves can be mapped on to the PLC memory areas.
through two Output Ares and two Input Areas. The Output data can be distributed over two Output Areas, each of which can be mapped on to PLC memory. Similarly, the Input data can be distributed over two Input Areas, each of
which can be mapped on to PLC memory.
Example
The figure below shows the CS1/CJ1W-PRM21 Master DTM’s Slave Area tab
for an example network with a CJ1W-PRT21, a CPM1A-PRT21, and an F150PRT Vision system.
By default all Output data is mapped on to Output Area 1, and all Input data is
mapped on to Input Area 1. Each of these Areas can be mapped on to PLC
memory independently of each other.
Changing the mapping can be achieved using drag & drop. The module which
is mapped to Area 1 and which must be mapped to Area 2, can be copied
there by dragging it from the overall module list on top to Area 2.
The I/O mapping concept is discussed in section 6-5-2 Mapping I/O Data.
Note
1. By default the Auto-Addressing option will be enabled (see section 6-4-1
Setting the Master Parameters). If any I/O modules are moved from one
Area to another, the I/O modules in first Area are re-mapped to close all
the gaps between mappings.
2. Prior to download, the CS1/CJ1W-PRM21 Master DTM will check the
mappings for possible Area overlaps, PLC memory overlaps and non-existing EM banks. If an error is detected, download will be aborted and the
necessary correction must be made first.
!Caution When mapping the I/O Areas, make sure that the I/O data will not overlap the
Unit’s own CIO Area or the CIO Area of any other special CPU Unit. The CS1/
CJ1W-PRM21 Master DTM does not check this. Failure to avoid this, will lead
to unpredictable behaviour of the Unit.
158
Configuring the Master
6-4-4
Section 6-4
Configuring CX-Server
Configuring
Communication
The CS1/CJ1W-PRM21 Master DTM uses CX-Server to connect to the Unit
for both downloading a configuration as well as monitoring the Master Unit. In
order to setup the communication to the Unit, perform the following procedure.
1,2,3...
1. Open the CS1/CJ1W-PRM21 Master DTM Configuration Interface, Device
Setup tab.
2. Make sure that the Unit Number has been set to the unit number set on the
PROFIBUS Master Unit, through the rotary switch on the front.
3. Select the Configure button to start CX-Server.
CX-Server
Up on pressing the Configure button, CX-Server is launched and displays the
CX-Server User Interface as shown below.
Configuring CX-Server
In order to configure CX-Server for communication with the Unit, perform the
following procedure.
1,2,3...
1. Select the type of PLC to which the Unit is attached, from the Device Type
drop down selection box.
2. Press the Settings button next to the PLC type selected. The PLC settings
window (see figure below) is displayed.
3. In this window make the proper adjustments if necessary. The selections
made, must match the physical configuration of the PLC system. When
done, press the OK button.
159
Configuring the Master
Section 6-4
4. Select the Network Type to be used as connection between the PC and
the Unit. The available options may include other PLC systems or Communication Units, which are setup to act as a gateway. Refer to CX-Server
Runtime user Manual (W391) for details on configuring CX-Server.
Note 1) For further explanation, only the direct connections between the
PC and the PLC on which the Unit is attached are considered.
These include ToolBus and SYSMAC WAY.
2) Select the Settings button next to the Network Type selected, to
display the Network settings window, and select the Driver tab
(Toolbus is shown as example below).
3) Although SYSMAC WAY can be used for the majority of applications, it is limited in a sense that it can not handle the absolute
maximum of I/O configuration and parameters, i.e. it can not handle a slave device which requires 244 I/O modules and 244 parameter bytes. Toolbus does not have that limitation.
5. Make the necessary selections to facilitate communication between the
PC and the PLC CPU to which the PROFIBUS Master Unit is attached, and
press the OK button.
Testing CX-Server setup
After making the settings, press the OK button to close the CX-Server interface. In order to verify that the communication has been setup correctly, press
the Test button in the Device Setup tab of the DTM Configuration User Interface. This will initiate a FINS command to read the Unit’s profile, i.e. the name
of the Unit and the firmware version.
If the communication has been setup correctly, the response of the FINS command will yield the required information, which will be displayed in the Device
Information box, in the Description and Firmware Version fields. If the communication is not setup correctly, the two fields will contain three dashes, i.e.
“---”, and an Error message will be displayed in the Error Log view of CX-Profibus. The communication settings must be changed to the correct value first.
Refer to Appendix D Configurator Error and Warning Messages for more
information on communication and download errors.
Note Since CX-Server is the common driver software for connection between PCbased CX- programs (e.g. CX-Programmer, CX-Supervisor, etc.) and the
CS1/CJ1-series PLC, all these programs can communicate simultaneously
with the PLC. However, the settings for CX-Server made through each of
these programs have to be exactly the same, to allow simultaneous communication.
160
Configuring the Master
6-4-5
Section 6-4
Downloading the Configuration
Downloading Parameters
1,2,3...
In order to download the parameter sets to the CS1/CJ1W-PRM21 PROFIBUS Master Unit, the following sequence must be performed.
1. Select the CS1/CJ1W-PRM21 Master DTM in the Network view and rightclick the mouse to display the context menu.
2. Select Download Parameters from the menu, to initiate a download. A
communication channel through CX-Server will be opened automatically.
3. When communication is achieved with the PLC, a warning window will be
displayed, notifying the user that the PLC will be switched to PROGRAM
mode. If the user confirms this, the download will continue.
4. The downloading process is handled by the CS1/CJ1W-PRM21 Master
DTM. The CS1/CJ1W-PRM21 Master DTM will switch the Master Unit to
OFFLINE, commence the download, and after successful download, issue
a command to the Master Unit to store the parameter sets in the Unit. A
window is displayed to show the progress of the download.
5. After storage has been completed, the CS1/CJ1W-PRM21 Master DTM
will issue a command to restart the CS1/CJ1W-PRM21 PROFIBUS Master
Unit. The new parameter sets will then become effective.
6. After restarting the Unit, a warning window will be displayed, allowing the
user to switch the PLC CPU back to its original mode.
Note
1. When switching the PLC CPU back to its original mode, after download,
the PROFIBUS Master Unit will behave according to the setting made in
the Master Setup Tab (see section 6-4-1 Setting the Master Parameters)
If the Action to PLC mode change has been set to go to OPERATE mode,
when the PLC switches to RUN/MONITOR mode, the last action of the
download process may start up the network. Therefore, if this is not desired, care must be taken to select the right setting.
2. In case of a failure in the download process, refer to section 7-4-1 Troubleshooting Parameter Download, to establish the cause and the remedy.
3. After successfully downloading the configuration to the CS1/CJ1WPRM21 PROFIBUS Master Unit, the user can make a backup of the configuration on a memory card, which can be inserted in the PLC CPU. This
backup can facilitate configuration of a replacement Unit, without the need
of a PC. Refer to Appendix E Memory Card Backup Functions for the backup/restore procedure.
161
I/O Communication Characteristics
6-5
6-5-1
Section 6-5
I/O Communication Characteristics
I/O Data Configuration
I/O Data Configuration
Each slave device defines its I/O data size, sequence and format by means of
I/O modules, each of which consists of one or more bytes, containing a
PROFIBUS defined coding scheme. The I/O modules can define input data,
or output data or both input and output data. The I/O modules are used to
configure the I/O data exchange process in the Master Unit and also to verify
the amount of I/O data to be exchanged with the slave device.
For modular slave devices the I/O modules are selected by the user from a list
of available modules. The modules usually have to be consistent with the
physical I/O of the slave device. For non-modular slave devices there is only
one I/O module, and can therefore not be selected by a user.
The selected I/O module bytes are sent over the PROFIBUS network to the
slave device at startup, using a Chk_Cfg message. The slave device has to
check and approve the I/O modules sent by the Master Unit, before I/O data
exchange can be established.
I/O Data Range Supported
The CS1/CJ1W-PRM21 PROFIBUS Master Unit supports up to 4000 I/O
modules, which can define a total of up to 7168 words of input data and/or
output data. The I/O module selection made per slave by the user is also used
to setup the I/O mapping, i.e. the definition of which I/O modules are mapped
to which PLC memory location.
This section discusses the aspects of I/O data exchange between the CS1/
CJ1W-PRM21 PROFIBUS Master Unit and the PLC CPU.
6-5-2
Mapping I/O Data
I/O Mapping Concept
The CS1/CJ1W-PRM21 PROFIBUS Master Unit provides an I/O mapping
concept, based on the I/O module selection for each slave device. Each
selected I/O module can - depending on whether it defines input and/or output
data - be mapped to one of two input and/or output areas. Each of the two
input and output areas can be mapped to any PLC memory area location,
independent of each other. The I/O mapping must be setup using the CS1/
CJ1W-PRM21 Master DTM, as provided with CX-Profibus.
Mapping the I/O modules involves two steps:
• Allocate each I/O module to one or more of the Input/Output areas.
• Allocate each Input/Output area to PLC memory.
Default I/O Mapping
Algorithm
When setting up the network, i.e. selecting the slave devices and I/O modules
per slave, all input modules will - by default - be allocated to Input area 1, all
output modules will be allocated to Output area 1. The following rules apply
when allocating the I/O modules to the areas:
• I/O modules are mapped starting at the lowest address of an Input/Output
area.
• I/O modules are mapped in ascending order according to slave device
address.
• I/O modules per slave device, are mapped in the order in which they were
selected, when setting up the slave device.
Furthermore, Input area 1 is by default mapped to CIO 3300, whereas Output
area 1 is by default mapped to CIO 3200.
162
I/O Communication Characteristics
Example
Section 6-5
The default mapping algorithm is illustrated in the figure below, with the following configuration:
• Slave device 1: One input/output module, one output modules.
• Slave device 2: One input module.
• Slave device 3: One output module.
• Slave device 4: Two input modules.
PLC CPU Unit
PROFIBUS DP Master Unit
Output area
Output area
Output area 1
Output area 1
Output area 2
Output area 2
Input area
Input area
Slave 1: Module 1
Slave 1: Module 2
Slave 3: Module 1
CIO 3200
CIO 3400
CIO 3300
Input area 1
Input area 1
Input area 2
Input area 2
Slave 1: Module 1
Slave 2: Module 1
Slave 4: Module 1
Slave 4: Module 2
CIO 3500
Note
1. The end address of each Input/Output area in the PLC memory, depends
on the size of the allocated I/O data.
2. If more than 100 words of input or output have been configured for the
slave, overlap of memory areas will occur in the PLC, if default I/O mapping
is used as shown above.
!Caution The default mapping of areas on to the PLC memory is the same default mapping as used in the CS1/CJ1W-DRM21 Devicenet Master/Slave Unit. Care
should be taken to avoid data overlap, if such a Unit is part of the same PLC
CPU system as the CS1/CJ1W-PRM21 PROFIBUS Master Unit.
The CS1/CJ1W-PRM21 PROFIBUS Master Unit, will assemble the correct
PROFIBUS data messages from the storage order in the Input and Output
memory areas.
Auto Addressing
The default allocation of I/O modules, i.e. I/O modules are mapped in ascending order of slave addresses and module selection, uses the concept of Auto
Addressing of the CS1/CJ1W-PRM21 Master DTM. Auto Addressing will
(re)allocate I/O modules according to the algorithm explained above in each
area.
If a configuration has been selected, which is changed later - for example - by
adding an I/O module to one of the slaves, the Auto Addressing feature will
add that module to the default area, between the already selected modules of
that particular slave device.
163
I/O Communication Characteristics
Section 6-5
!Caution When an I/O module is added to or deleted from a configuration at a later
point in time, Auto Addressing will cause a change in the addresses of subsequent I/O modules in an Input/Output area. This will cause I/O data of (a part
of the) slave devices to be re-mapped to different locations in the PLC memory. In order to avoid unexpected results, the PLC user program may have to
be adapted as well.
Note
1. Auto Addressing will not change the allocation of I/O modules to a certain
area, i.e. a module allocated to Input/Output area 2, will not be re-allocated
to area 1, if Auto Addressing is enabled.
2. Auto Addressing will not change the start address of the areas.
3. Auto Addressing is by default enabled, when starting a new project. It is
however, disabled for existing projects to avoid unwanted re-mapping.
Example
The figure below shows an example of the effects of Auto Addressing on
(re)allocation of I/O modules. In the original I/O configuration on the left, the
first slave - an OMRON CJ1W-PRT21 - consisted of two I/O modules. In new
configuration one I/O module was inserted, and subsequent modules were reallocated in the process.
Initial I/O Configuration
One I/O module of two output
words was inserted, and re-allocated
subsequent I/O modules.
Note The start address of Output area 1 in the example remains the same, after
adding an I/O module.
Re-allocating I/O Modules
1,2,3...
After setting up the initial I/O configuration, the I/O modules can be remapped to the second Input/Output area. This can be accomplished by using
drag & drop to move the I/O modules. To accomplish this, perform the following sequence.
1. Open the CS1/CJ1W-PRM21 Master DTM - Configuration User Interface.
2. Select the Slave Area tab. The window shows two sub tabs: One for Output
Allocation and one for Input Allocation. The following points apply to each
of these tabs.
3. After setting up the initial I/O configuration, all I/O modules will be shown
in the overall list in the upper half of the Slave Area tab. This is a pick list
164
I/O Communication Characteristics
Section 6-5
from which modules can be selected. The allocated I/O modules are listed
in area 1, the column on the left of the lower half of the window.
Note The I/O modules in the pick list, all remain there. The allocated I/O
modules are copies of the modules selected from the pick list.
4. In order to move an I/O module from one area to another, select the module in the pick list.
5. Hold the left mouse button and drag the I/O module to the Input/Output
area of choice. Release the left mouse button to drop the module in place.
Note The area to place the module in must be empty. The area to put the
modules in does not need to be selected first.
Auto Addressing and Reallocating I/O Modules
Auto Addressing (re)allocates I/O modules in all Input/Output areas. If - after
setting up the initial I/O configuration - two or more I/O modules are moved
from one area to another, Auto Addressing maintains the same sequence, i.e.
the slave device with the lowest address and its I/O modules in the selected
sequence are allocated before a slave device with a higher address.
Example
In the figure below two output modules from the initial I/O configuration (top
window) have been re-allocated to Output area 2 (bottom window)
Initial I/O configuration
The first Output modules
of slave device #2 and #3
were moved to Output area 2.
165
I/O Communication Characteristics
Section 6-5
The example shows that the sequence of slave addresses is maintained, the
sequence of I/O modules selected is maintained and the I/O modules are allocated to the lowest address of the area.
Enable/Disable Auto
Addressing
The Auto Addressing feature can be disabled in the CS1/CJ1W-PRM21 Master DTM. In order to do that, perform the following sequence.
1,2,3...
1. Open the CS1/CJ1W-PRM21 Master DTM - Configuration User Interface.
2. Select the Master Setup tab.
3. Enable/Disable Auto Addressing by selecting/deselecting the Auto Addressing checkbox in the Support box.
4. When Auto Addressing is being enabled, a warning message is displayed,
informing the user of the effects of enabling Auto Addressing.
!Caution Enabling Auto Addressing has the immediate effect of re-allocating I/O modules of an existing configuration, within each Input/Output area. The I/O modules are re-mapped according to the algorithm described above.
Note Disabling Auto Addressing has no immediate effect on an existing I/O mapping.
I/O Mapping Without Auto
Addressing
A disabled Auto Addressing feature has the following effects on I/O mapping:
• When adding new slave devices or new I/O modules to an existing slave
configuration, the I/O modules will be mapped to the first I/O areas, but
the modules will be appended to the existing I/O mapping.
• When deleting a slave device from the network configuration, or deleting
I/O modules from a slave device, the deleted I/O modules will leave gaps
behind in the already existing I/O mapping. If after deleting an I/O module
a slave device still has more than one module configured, but these modules are not in the same place, the DTM will attempt to remap them
together.
• Changing the address of a slave device, of which already an I/O mapping
exists, has no effect on the existing mapping
• Selecting an additional I/O module for a slave device, in the presence of
already allocated I/O modules, will cause a complete re-map of all existing modules if the total I/O does not fit within the space it is already occupying. The modules are re-mapped to the next available location in the
area, leaving behind a gap in the existing I/O mapping. Subsequent I/O
modules of other slave device will remain mapped as before the module
addition.
• When moving an I/O module from one area to another, they can be
located anywhere with in the target area. They are not re-mapped to the
start of that.
• When moving an I/O module from one area to another, the module leaves
behind a gap in the I/O mapping of the first area.
Note
1. Gaps in the I/O mapping still contribute to the total size of an area, although
they do not contain valuable data. They therefore decrease the total I/O capacity of the CS1/CJ1W-PRM21 PROFIBUS Master Unit, and unnecessarily occupy PLC memory.
2. In the I/O data exchange with the PLC CPU, these gaps will contain zeros.
166
I/O Communication Characteristics
Example
Section 6-5
The figure below illustrates the effects of re-allocating I/O modules, when Auto
Addressing has been disabled.
Initial I/O Configuration
Note: Auto-addressing is disabled
Output module 2 of slave device
#2 was moved to Output area 2,
location CIO 3401, leaving behind
a gap in Output area 1.
Removing Gaps from the I/
O Mapping
Since gaps in the I/O mapping are generally undesirable, the CS1/CJ1WPRM21 Master DTM provides a means to remove all gaps, after finalizing the
I/O mapping procedure. This removal is accomplished by compressing the I/O
modules in a particular area.
Compressing the I/O
Mapping
Compressing re-allocates all I/O modules in an area as close to the start of
the area as possible. Compressing an area does not change the sequence of
the slave devices and/or the I/O modules. It only removes the unused memory
gaps. Compressing can be initiated for each area individually.
In order to compress an area, perform the following sequence.
1,2,3...
1. Open the CS1/CJ1W-PRM21 Master DTM - Configuration User Interface,
and select the Slave Area tab.
2. Select the Output Allocation tab or the Input Allocation tab, to display the
areas to compress.
3. To compress the area, press the Compress button at the bottom.
4. After finalizing the compress action, select the Save button at the lower
right corner, to save the changes made.
167
I/O Communication Characteristics
Section 6-5
Note Compressing an Input/Output area has no effect on the start address of the
area.
Example
The figure below, shows the effects on the previous example, after pressing
the Compress button in both Output areas.
Selecting the I/O Area
Start Address
After finalizing the mapping of the I/O modules on to the various I/O areas, the
addresses to which the areas will be mapped in the PLC memory need to be
defined. To define the area mapping, perform the following settings.
1,2,3...
1. For each area, which contains I/O modules, select the PLC memory area.
2. For that area, set the address to which the first location of the Input/Output
area will be mapped. The Input/Output area will occupy the PLC memory
area, from this start address to ascending memory locations.
3. The total size per Input/Output area can be found for each area, next to the
PLC memory area selection box (see for example, the figure above, in
which Output area 1 occupies 6 words).
Note
1. The CS1/CJ1W-PRM21 Master DTM will check whether two or more selected mappings on to the PLC memory will be overlapping. In that case,
the start address set, will be shown in red.
2. Upon downloading the configuration to the CS1W/CJ1W-PRM21 PROFIBUS Master Unit, the Master DTM will also check if the PLC memory areas
selected do exist in the PLC CPU model, connected to the Master Unit
(e.g. are any selected EM-banks present).
3. If any mapping error is discovered by the Master DTM, an error message
is displayed, and download is terminated.
168
I/O Communication Characteristics
6-5-3
Section 6-5
Supported Data Types
The CS1/CJ1W-PRM21 PROFIBUS Master Units perform an interface function between a PROFIBUS network and the CS1/CJ1 PLC CPU. On both
sides of the interface different formats for data and data storages are used.
To ensure that I/O data transferred through the interface can be used on both
sides of the interface without additional formatting, the CS1/CJ1W-PRM21
PROFIBUS Master Units perform the necessary data formatting. This ensures
that I/O data in the PLC CPU memory can be processed by standard PLC
Instructions, and that the I/O data transferred to / from the PROFIBUS DP
slaves over the network is compliant with the PROFIBUS DP definitions.
The table below lists the I/O data formats supported by both the PROFIBUS
network and PLC CPU. Appendix C I/O Data Conversions defines the conversion of I/O data in detail.
Data Type
Size
[bytes]
PROFIBUS DP
CS/CJ-series PLC
Single 8-bit Integer
signed/unsigned
1
Supported.
Data is transmitted on a byte-by-byte
basis.
Not supported
Minimum is 16-bit words. Two bytes will
be formatted in one word. Words containing odd bytes will be padded with
zeros.
Single 16-bit Integer
signed/unsigned
2
Supported.
Data is transmitted on a Most-Significant-Byte First basis.
Supported.
Single 16-bit integers are transferred to
memory words in PLC memory.
Single 32-bit Integer
signed/unsigned
4
Supported.
Data is transmitted on a Most-Significant-Byte First basis.
Supported.
Data is stored with the Least-SignificantWord at the lowest address.
Floating point
4
Supported.
Data is transmitted on a Most-Significant-Byte First basis.
Supported.
Data is stored with the Least-SignificantWord at the lowest address.
Visible string
--
Supported.
Length of string is fixed by I/O configuration. Data is transmitted on a left-to-right
basis (i.e. first character is transmitted
first).
Supported.
First characters are stored at the lowest
address. String is padded with a zero
byte or a zero word, depending on the
number of characters.
Byte string
--
Supported.
Length of string is fixed by I/O configuration. Data is transmitted on a left-to-right
basis (i.e. first character is transmitted
first).
Supported.
First bytes are stored at the lowest
address. String is padded with a zero
byte or a zero word, depending on the
number of characters.
Date / Clock time
7
Supported.
Not Supported.
Date/Time format contains absolute time Date/Time format is transferred to PLC
with respect to start of century. Date/
memory as string of words.
Time is coded in individual bytes.
Time of day
6
Supported.
Time of day format contains time since
midnight.
Not Supported.
Time of day format is transferred to PLC
memory as string of words.
Time difference
6
Supported.
Time difference format is the same as
Time of day format, but contains a time
difference.
Not Supported.
Time difference format is transferred to
PLC memory as string of words.
169
I/O Communication Characteristics
6-5-4
Section 6-5
Exchanging I/O Data over PROFIBUS
The cyclic refresh cycles of the PLC CPU and the I/O data exchange cycles of
the PROFIBUS network are two asynchronous processes, for which the CS1/
CJ1W-PRM21 PROFIBUS Master Unit performs the interface function.
PLC Cyclic Refresh vs.
PROFIBUS I/O Exchange
Cycle
In general, all I/O data exchanged during a PROFIBUS I/O data exchange
cycle must be exchanged with the PLC CPU, as soon as possible after the
end of each PROFIBUS DP I/O data exchange cycle is signalled.
In order to transfer I/O data between the Unit and the PLC CPU, the Unit, has
to request a transfer of I/O data. The actual transfer of I/O data will then be
performed during the next PLC cyclic refresh, which depends on the PLC user
program.
PLC Cyclic Refresh Rules
To avoid missing I/O data as much as possible, the CS1/CJ1W-PRM21 uses
the following rules for cyclic refresh with the PLC CPU.
• The PROFIBUS Master Unit estimates - based on the actual PLC cycle
and the last cyclic refresh - when a new cyclic refresh from the PLC CPU
can be expected and requests a refresh of I/O data, shortly before that.
• If the end of PROFIBUS DP I/O data exchange is signalled, before the
request based on the estimation is issued, the PROFIBUS Master Unit
will immediately request a cyclic refresh.
• If the end of PROFIBUS DP I/O data exchange is signalled, after the
request has been issued or during the cyclic refresh, the PROFIBUS Master Unit will request a cyclic refresh, as soon as the requested cyclic
refresh has been finished.
The implementation of these rules are illustrated in the figures below for two
distinctive cases.
PROFIBUS DP Cycle >
PLC Cyclic Refresh
The figure below shows the effects of these rules for the case in which the
PROFIBUS DP I/O data exchange cycle > PLC cyclic refresh.
Unit requests
cyclic refresh
Unit requests
cyclic refresh
Unit requests
cyclic refresh
Instruction
Execution
PLC Cycle
Unit requests
cyclic refresh
Unit requests
cyclic refresh
Instruction
Execution
Instruction
Execution
Instruction
Execution
Instruction
Execution
CIO Refresh
Output data refresh
O
O+1
Input data refresh
PROFIBUS Cycle
O+2
I
Cycle n
O+4
I+1
Cycle n+1
End of PROFIBUS DP cycle
170
O+3
I+2
Cycle n+2
End of PROFIBUS DP cycle
End of PROFIBUS DP cycle
I/O Communication Characteristics
Section 6-5
PROFIBUS DP I/O data exchange cycle > PLC cyclic refresh results in the following I/O transfer characteristics.
• Not all output data is guaranteed to be transmitted over the PROFIBUS
network (referring to the figure above: Output data marked with “O” is
overwritten by “O+1” and therefore lost).
• Input data is always sent to the PLC CPU.
Note
1. PLC cyclic refresh times may vary, depending on the execution of the user
program. If variation is too large, this may result in I/O data being lost.
2. To prevent output data not being transmitted over the PROFIBUS network,
the PROFIBUS DP cycle time must made at least two times the PLC cyclic
refresh time. This can be accomplished by changing the Target Token Rotation time in the Master DTM Configuration User Interface (see section 64-2 Setting the Bus Parameters).
PROFIBUS DP Cycle <
PLC Cyclic Refresh
The figure below shows the effects of the cyclic refresh rules for the case in
which the PROFIBUS DP I/O data exchange cycle < PLC cyclic refresh.
Unit requests
cyclic refresh
Unit requests
cyclic refresh
Unit requests
cyclic refresh
Instruction
Execution
PLC Cycle
Instruction
Execution
Unit requests
cyclic refresh
Unit requests
cyclic refresh
Instruction
Execution
Instruction
Execution
Instruction
Execution
CIO Refresh
Output data refresh
O
Input data refresh
PROFIBUS Cycle
O+1
I
Cycle n
I+1
Cycle
n+1
Cycle
n+2
O+2
I+2
Cycle
n+3
I+3
Cycle
n+4
O+3
I+4
Cycle
n+5
O+4
I+5
Cycle
n+6
I+6
Cycle
n+7
I+7
I+8
Cycle
n+8
PROFIBUS DP I/O data exchange cycle < PLC cyclic refresh results in the following I/O transfer characteristics.
• All output data sent by the PLC CPU is transmitted over the PROFIBUS
network.
• Not all Input data is transferred to the PLC CPU (referring to the figure
above: Input data marked with I+1, I+4, I+6 and I+8 are lost).
Note To prevent input data not being transferred to the PLC CPU, the PLC cyclic
refresh time must be at least two times the PROFIBUS DP cycle time.
171
I/O Communication Characteristics
6-5-5
Section 6-5
PLC Cycle Time Performance
The cyclic refresh time is the time required for I/O data to be exchanged
between the PLC CPU Unit and the PROFIBUS Master Unit. The PLC CPU
Unit cyclic refresh time is increased when a PROFIBUS Master Unit is
mounted, as shown below.
PLC CPU type
CS1/CJ1G-H CPU
CS1/CJ1H-H CPU
CJ1M
Note
PROFIBUS Master Unit cyclic refresh time (ms)
0.5 + 0.001 × the number of I/O words (See notes)
0.3 + 0.001 × the number of I/O words (See notes)
0.5 + 0.001 × the number of I/O words (See notes)
1. The number of words refreshed is the total number of words in the I/O area
that are used by the slave devices, including any unused words that may
be present in I/O mapping gaps (refer to section 6-5-2 Mapping I/O Data).
2. The number of words refreshed also includes the 25 CIO status and command words.
3. If FINS message communications is being performed, add the number of
words used in the message communications to the above number of words
when messages are being processed.
4. For details about cyclic refresh time or PLC cycle time, refer to operation
manual of the PLC.
Note To avoid missing input data or output data, the PLC cyclic refresh time must
be at least 3 ms.
6-5-6
I/O Response Time
The maximum I/O response time is defined as the time from the moment an
input on a slave device with the lowest PROFIBUS address is switched ON
(OFF) until the moment the output on a slave device with the highest PROFIBUS address is switched ON (OFF).
PROFIBUS DP Cycle >
PLC Cyclic Refresh
The figure below shows the timing in case the PROFIBUS DP cycle > PLC
cyclic refresh.
Instruction
Execution
PLC Cycle
Instruction
Execution
Instruction
Execution
Instruction
Execution
Instruction
Execution
Instruction
Execution
Instruction
Execution
Instruction
Execution
Slave I/O data refresh
PROFIBUS Cycle
Slave I/O data refresh
TPB,Cyc
TPB,Cyc
TPLC,Cyc
TIN
ON
172
TPLC,Cyc
TPB,Cyc
TM,Proc
TM,Proc + TM, Rrf
TPLC,Rf
TPB,Cyc
TOUT
ON
I/O Communication Characteristics
Section 6-5
TIN
Slave device Input ON (OFF) delay.
TPB,Cyc
PROFIBUS I/O data exchange cycle time
(See Appendix A Bus Parameters)
TM,Proc
I/O Processing time in the Master Unit. Minimum value is 430 µs,
but may increase with increasing I/O data size.
TM,Rrf
Master request cyclic refresh until actual start of cyclic refresh.
TPLC,Cyc PLC cycle time (See section 6-5-5 PLC Cycle Time Performance).
TPLC,Rf
PLC cyclic refresh time (See section 6-5-5).
TOUT
Slave device Output ON (OFF) delay.
The total I/O response time is the sum of all components:
TIO = TIN + 4*TPB,Cyc + 2*TM,Proc + TM,Rrf + 2*TPLC,Cyc + TPLC,Rf + TOUT
Note The calculation assumes the presence of only one Master Unit on the PROFIBUS network.
PROFIBUS DP Cycle <
PLC Cyclic Refresh
PLC Cycle
The figure below shows the timing in case the PROFIBUS DP cycle < PLC
cyclic refresh.
Instruction
Execution
Instruction
Execution
Instruction
Execution
Instruction
Execution
TPLC,Cyc
TPLC,Cyc
Instruction
Execution
Slave I/O data refresh
PROFIBUS Cycle
Slave I/O data refresh
TPB,Cyc
TPB,Cyc
TPB,Cyc
TM,Proc + TM,Rrf
TIN
ON
TM,Proc
TPB,Cyc
TOUT
TPLC,Rf
TIN
Slave device Input ON (OFF) delay.
TPB,Cyc
PROFIBUS I/O data exchange cycle time
(See Appendix A Bus Parameters)
TM,Proc
I/O Processing time in the Master Unit.
ON
TM,Rrf
Master request cyclic refresh until actual start of cyclic refresh.
TPLC,Cyc PLC cycle time (See section 6-5-5 PLC Cycle Time Performance).
TPLC,Rf
PLC cyclic refresh time (See section 6-5-5).
TOUT
Slave device Output ON (OFF) delay.
The total I/O response time is the sum of all components:
TIO = TIN + 4*TPB,Cyc + 2*TM,Proc + TM,Rrf + 2*TPLC,Cyc + TPLC,Rf + TOUT
173
I/O Communication Characteristics
Section 6-5
Note The calculation assumes the presence of only one Master Unit on the PROFIBUS network
Minimum I/O Response
Time
The minimum response time, i.e. the time from an input on a slave device
being set to the time the output on the same slave device is set is calculated,
based on the figure below. The following assumptions are made:
• The slave device is the first one in the PROFIBUS I/O data exchange.
• The input data is available right before the internally generated cyclic
refresh request is set. In this case, a complete cyclic refresh will take
place (See section 6-5-4 Exchanging I/O Data over PROFIBUS)
PLC Cycle
Instruction
Execution
Instruction
Execution
TPB,Cyc
TPLC,Cyc
Instruction
Execution
Master Unit processing
PROFIBUS Cycle
Slave I/O data refresh
TIN
TM,proc
TOUT
TM,proc
TM,Rrf
TPLC,Rf
TI/O
ON
TIN
Slave device Input ON (OFF) delay.
TPB,Cyc
PROFIBUS I/O data exchange cycle time
(See Appendix A Bus Parameters)
TM,Proc
I/O Processing time in the Master Unit.
ON
TM,Rrf
Master request cyclic refresh until actual start of cyclic refresh.
TPLC,Cyc PLC cycle time (See section 6-5-5 PLC Cycle Time Performance).
TPLC,Rf
PLC cyclic refresh cycle time (See section 6-5-5).
TOUT
Slave device Output ON (OFF) delay.
The total I/O response time is the sum of all components:
TIO = TIN + TPB,Cyc + 2*TM,Proc + TM,Rrf + TPLC,Cyc + TPLC,Rf + TOUT
174
I/O Communication Characteristics
6-5-7
Section 6-5
System Startup Time
Startup Time Definition
The system startup time is the delay from the time the CS1/CJ1W-PRM21
PROFIBUS Master Unit is turned ON, or reset, until I/O data exchange with all
slave devices has been established. For this, the following is assumed:
• The Master Unit has been configured to go to OPERATE mode, if the PLC
mode is set to RUN / MONITOR mode.
• All slave devices are powered up and initialized before the Master Unit is
turned ON.
• All slave devices are assumed to go to I/O data exchange without delays.
The total system startup time is the sum of the following components:
• Master Unit startup checking.
• Initialization of communication with PLC CPU.
• Master Unit I/O configuration initialization, after which the Master Unit
goes to OPERATE.
• One PROFIBUS DP cycle to request slave diagnostics.
• One PROFIBUS DP cycle to transmit parameter messages to all slave
devices.
• One PROFIBUS DP cycle to transmit the I/O configuration messages to
all slave devices.
• One PROFIBUS DP cycle to request slave diagnostics.
The average time for the first three actions - assuming a maximum I/O configuration - is approximately 2 seconds. The remaining time depends on the
PROFIBUS settings.
For a maximum I/O configuration, with 125 slave devices, 56 words I/O each,
(i.e. the total I/O size amounts up to 7000 words) one PROFIBUS DP cycle
lasts approximately 70 ms. A complete start up cycle will then last approximately 280 ms.
The total system start up time, from Unit reset until I/O data exchange, will
then be 2.3 seconds.
175
Operating the Network
6-6
6-6-1
Section 6-6
Operating the Network
User Access to the Network
There are several ways through which a user can have access to and control
over the PROFIBUS network.
• Through a PLC user program
A PLC user program can set the operational mode of the Unit, send Global-Control commands, read Master and slave status / diagnostics information, and access the Unit’s Error Log. Furthermore, the I/O data
transferred between the PROFIBUS network and the PLC memory, and
can be used by the user program.
• Through CX-Profibus
The CS1/CJ1W-PRM21 Master DTM Diagnosis User Interface provides
the user with buttons to set the operational mode of the Unit, send GlobalControl commands, read Master and slave status information, and access
the Unit’s Error Log.
• Through any other CX-Server based program, capable of accessing PLC
memory areas and communicating through FINS messages, e.g. CX-Programmer, CX-Supervisor, etc.
This section will explore both means to control the CS1/CJ1W-PRM21
PROFIBUS Master Unit.
The CS1/CJ1W-PRM21 Master DTM Diagnosis User Interface provides the
means to control the Master Unit directly from CX-Profibus, running on a PC.
Access to the Unit
For access to the Unit’s controls, an online connection with the Unit has to be
established first. To achieve this perform the following sequence.
1,2,3...
1. To go on line, select the DTM in the Network view, and perform one of the
following actions.
• Select the Device - Go Online option from the main menu, or the DTM
context menu, or
• Select the
button from the Tool Bar.
2. A communication channel will be opened through CX-Server. The name of
the DTM in the Network view, will turn to Italic font, to indicate that the Unit
is on-line.
3. From the context menu, select the Diagnosis option. The DTM’s Diagnostics User Interface will be displayed.
4. Select the Online Operations tab, for the Units controls.
!Caution Controlling the CS1/CJ1W-PRM21 PROFIBUS Master Unit from the CS1/
CJ1W-PRM21 Master DTM Diagnosis User Interface, may interfere with a
PLC user program running at the same time. This can result in unexpected
behaviour. It is recommended to change the PLC CPU mode to PROGRAM
mode to avoid this interference, during the use of the CS1/CJ1W-PRM21
Master DTM Diagnosis User interface.
176
Operating the Network
6-6-2
Section 6-6
Changing PROFIBUS Mode of the Master Unit
PROFIBUS DP Network
Modes
The PROFIBUS standard defines four different network modes, in which a
Master Unit can operate. The modes are:
• OFFLINE
The PROFIBUS Master Unit does not access the network, nor does it
respond to messages.
• STOP
The PROFIBUS Master Unit is on-line, but does not communicate with its
slave devices. It does communicate with other Master Units, in that it
passes the token message.
• CLEAR
The PROFIBUS Master Unit is on-line and communicates with its slave
devices. It will parameterize all allocated slave devices, but only read their
input data. The Master Unit does not send valid output data to the slave
devices. Instead it will send empty output data messages or messages
containing zeros.
• OPERATE
The PROFIBUS Master Unit is on-line and communicates with its slave
devices. It will parameterize all allocated slave devices, and exchange all
I/O data for which it has been configured.
Normal Operating Modes
The OPERATE mode is the mode used for normal network operation. The
CLEAR mode is the mode used for situations which require a safety state to
fall back to (see section 6-6-4 Using Auto-CLEAR).
Changing the Mode from
the CS1/CJ1W-PRM21
Master DTM
In order to change the Unit’s operational mode, open the CS1/CJ1W-PRM21
Master DTM Diagnosis User Interface. The figure below shows this Online
Operations tab. Press the desired mode button in the upper left corner of the
window.
Example
In order to change the network to OPERATE mode, i.e. start I/O data
exchange, press the OPERATE button. The OPERATE status of the Master
Unit can be retrieved from the Monitor - Master status tab in the same user
interface.
Changing the Mode Using
the PLC Program
The Unit’s operational mode can also be changed from the PLC user program, by setting the appropriate bit in the Software Switches 1 Word (CIO
Word n, see section 4-2-1 Software Switches 1 (Word n)).
177
Operating the Network
Example
Section 6-6
Below is an example ladder program, which changes the operational mode to
OPERATE, if the current mode is not OPERATE and non of the other mode
switches are set. The unit number for the example Unit is 0.
000000
(000000)
A200.11
SET
W0.00
P_First_Cycle
Go to OPERATE
First Cycle
Flag
000001
(000002)
W0.00
1505.05
1505.01
1500.00
1504.01
SET
1500.00
Go to
Valid Cfg
OPERATE
STOP
mode
Set OPERATE
Set
No errors
OPERATE
1505.03
OFFLINE
mode
000002
(000010)
1505.00
W0.00
RSET
W0.00
Go to OPERATE
OPERATE Go to
mode
OPERATE
Note If an attempt is made to change the operational mode, while a previous
change command is still being processed, the new command is ignored, and
the Mode command error bit flag (bit 12) in the Master Status 2 word (CIO
word n+6, see section 4-2-5 Master Status 2 (Word n+6)) will be set.
Indirect Mode Changes
The Unit’s operational mode can also be changed in indirect ways, i.e. without
direct user or program interference.
• Mode changes caused by Auto-CLEAR
When the Auto-CLEAR function has been enabled, and one or more of
the slave devices on the network stop I/O data exchange, the Master
Unit’s operational mode will automatically change from OPERATE to
CLEAR. This is discussed in section 6-6-4 Using Auto-CLEAR.
• Mode changes caused by PLC mode changes
An operational mode change will take place if the PROFIBUS Master Unit
has been configured to change its operational mode together with the
PLC mode, i.e. OPERATE when the PLC mode is set to RUN/MONITOR
and CLEAR mode, when the PLC mode is changed to PROGRAM mode.
Refer to section 6-4-1 Setting the Master Parameters for more information.
178
Operating the Network
6-6-3
Section 6-6
Transmitting Global-Control Commands
Global-Control commands
The CS1/CJ1W-PRM21 PROFIBUS Master Units support the transmission of
Global-Control commands. These messages are unconfirmed broadcast
messages (i.e. the slave devices do not send a response message), which
can be used to synchronize I/O data related events two more slave devices.
I/O Data Synchronization
Two types of synchronization can be achieved.
1. Synchronization of input data
The inputs on one or more slave devices are read at the same time. The
synchronized data is transferred to the Master Unit during the next I/O data
exchange cycle. The commands are defined as Freeze and Unfreeze.
2. Synchronization of output data
The outputs on one or more slave devices are set at the same time. The
synchronized data has been transferred to the slave devices during the
previous I/O data exchange cycle. The commands are defined as Sync
and Unsync.
Note
1. The CS1/CJ1W-PRM21 PROFIBUS Master Unit also uses Global-Control
commands to broadcast its own operational mode to other devices on the
network. These Global-Control commands are sent automatically, without
user interference
• to all devices on the network (i.e. not to specific groups),
• always at the start of every I/O data exchange cycle, and
• only when the Master Unit is either in OPERATE or in CLEAR mode
2. The user can only initiate transmission of Freeze/Unfreeze and Sync/Unsync to either all slave devices or specific groups of slave devices. These
Global-Control commands are transmitted separately from the automatically transmitted messages, at the end of the PROFIBUS I/O data exchange cycle.
Group Address Setting
User initiated Global-Control commands can be transmitted to either all slave
devices allocated to a Master Unit, or to one or more of up to eight groups of
slave devices. The group addresses are defined by up to eight bits in a group
address byte, which is part of the Global-Control command.
Note If a Global-Control command is targeted to all slave devices, all the group bits
in the group address bytes are set to 0.
Setting the Group
Address of a Slave Device
In order for a specific slave device to belong to a certain group, the group
assignment for the slave has to be defined through the Generic Slave DTM
Configuration User Interface. A slave device can belong to one or more
groups at the same time, or to no specific group at all. The group assignment
is sent to the slave devices as part of the parameter message.
To define the group assignment of a slave device, through the Generic Slave
DTM, refer to section 6-3-3 Selecting the Group Assignment.
Freeze / Unfreeze
commands
Sending a Global-Control - Freeze command to a slave device has the following effect
• The slave device will continue to read its physical inputs, but not send this
data to the PROFIBUS Master Unit.
• Instead, it will continue to transfer the input data to the Master Unit from
the moment the Global-Control - Freeze command was received.
• If a new Global-Control - Freeze command is sent, the slave device will
update its PROFIBUS input buffers only once, with the most recent physi-
179
Operating the Network
Section 6-6
cal input data, and continue to transfer this data to the Master Unit with
subsequent I/O data exchange messages.
• If a Global-Control - Unfreeze command is sent, the slave device will
revert back to its original situation, and transfer updated input information
to the Master Unit with subsequent I/O data exchange messages.
Note If a Global-Control command contains both a Freeze and an Unfreeze command, the Unfreeze will prevail.
The figure shown below illustrates the Freeze / Unfreeze feature as implemented by the CS1/CJ1W-PRM21 PROFIBUS Master Unit.
Global-Control Freeze command
Global-Control Freeze command
Global-Control Unfreeze command
Instruction
Execution
PLC Cycle
Instruction
Execution
Freeze
transmitted
Instruction
Execution
Instruction
Execution
Freeze
transmitted
Unfreeze
transmitted
PROFIBUS
Cycle
Slave
PROFIBUS
Input Buffers
Slave Input
Refresh Cycle
Freeze command freezes
slave input refresh process.
Last input data transferred to
transmit buffer will be
transferred over PROFIBUS.
Freeze command causes
immediate update of transmit
buffer. Last sampled data will be
transferred over PROFIBUS.
Unfreeze command cancels
Freeze command and causes
immediate update of transmit
buffer. Input refresh process
started again.
Note The Global-Control command as set in the CIO words is transferred to the
Unit together with the I/O data, but the Global-Control command is sent over
the PROFIBUS network, following the I/O data. The Freeze command forces
an immediate update of the PROFIBUS transmission buffers in the slave
device, with the last input value sampled. This input data is then transferred to
the PROFIBUS Master Unit, with the next I/O data exchange cycle.
Sync / Unsync commands
Sending a Global-Control - Sync command to a slave device has the following
effect
• The slave device will update its physical outputs only once with the last
received PROFIBUS output data, despite new output data being received
from the PROFIBUS Master Unit.
• If a new Global-Control - Sync command is sent, the slave device will
update its physical outputs only once, with the most recent received out
put data.
• If a Global-Control - Unsync command is sent, the slave device will revert
back to its original situation, and transfer updated output information to
the Master Unit with each subsequent I/O data exchange message.
180
Operating the Network
Section 6-6
Note If a Global-Control command contains both a Sync and an Unsync command,
the Unsync will prevail.
The figure shown below illustrates the Sync / Unsync feature as implemented
by the CS1/CJ1W-PRM21 PROFIBUS Master Unit.
Global-Control Sync command
PLC Cycle
Instruction
Execution
Sync
transmitted
Global-Control Unsync command
Instruction
Execution
Instruction
Execution
Sync
transmitted
Instruction
Execution
Unsync
transmitted
PROFIBUS Cycle
Slave Output
Refresh Cycle
Sync command causes
immediate refresh of
slave outputs, and
freezes slave output
refresh process.
Sync command causes
immediate refresh of
slave outputs with last
received PROFIBUS
output data.
Unsync command
cancels Sync command
and causes immediate
refresh of slave outputs
and with last received
PROFIBUS output data.
Note The Global-Control command as set in the CIO words is transferred to the
Unit together with the I/O data, but the Global-Control command is sent over
the PROFIBUS network, following the I/O data. This means that the outputs of
the targeted slave device will be updated with the values sent to the slave
prior to the Global-Control command.
Transmitting GlobalControl Commands
In order to transmit a Global-Control command the user has to define the
group address and the command (e.g. Freeze, Sync). These two parameters
must be entered in Global-Control command word (CIO Word n+2, see section 4-2-2 Global-Control Message (Word n+2)).
After setting these parameters, the Global-Control command must be transmitted over the PROFIBUS network. This is accomplished by setting the
Transmit Global-Control command bit (bit 04) in the Software Switches 1 word
(CIO Word n, see section 4-2-1 Software Switches 1 (Word n)). Setting this bit
will transmit the message only once. After transmission has been completed,
bit 04 in the Software Switches 1 word will be reset again.
PLC User Program
Transmitting a Global-Control command from a PLC user program can be
accomplished using the steps described above.
Example
Below is an example ladder program, which transmits one Global-Control Freeze command to Group 2. The unit number for the example Unit is 0.
181
Operating the Network
Section 6-6
000000
(000000)
W0.01
1500.00
1500.04
@MOV
(021)
#0002
Send
Freeze
OPERATE Transmit
mode
GC
command
1500
Set Group Address
@SET
1502.11
Set Freeze cmd bit
@SET
1500.04
Transmit GC command
@RSET
W0.01
CX-Profibus
Send Freeze
CX-Profibus also provides a means to transmit Global-Control commands
from the PC, through the CS1/CJ1W-PRM21 Master DTM Diagnosis User
Interface - Online Operations tab. This means uses the same CIO words as
described above
To accomplish a Global-Control command transmission, per from the following sequence.
1,2,3...
1. Make sure the CS1/CJ1W-PRM21 Master DTM is online with the PROFIBUS Master Unit.
2. Open the CS1/CJ1W-PRM21 Master DTM Diagnosis User Interface.
3. Select the Online Operations tab.
4. Select the commands to be transmitted (e.g. Freeze, Sync) using the
checkboxes.
5. Select the groups to transmit the Global-Control command to.
6. Press the Transmit button to transfer the command to the Unit’s CIO area,
and to set bit 04 in the Software Switches 1 word.
7. The Transmit button will be disabled until the command has been transmitted.
Note The time between pressing the Transmit button in the CS1/CJ1W-PRM21
Master DTM user interface and the Global-Control command actually being
transmitted over the PROFIBUS network, will be (much) longer than when the
Global-Control command is initiated from a PLC user program, due to the
additional communication between the PC and the PLC CPU.
182
Operating the Network
6-6-4
Section 6-6
Using Auto-CLEAR
Auto-CLEAR Feature
The CS1/CJ1W-PRM21 PROFIBUS Master Units support the Auto-CLEAR
function as defined in the PROFIBUS standard. This feature - when enabled will switch the PROFIBUS Master Unit to CLEAR mode automatically, in case
one of the slave devices fails on the network. The purpose of this, is to force
the PROFIBUS network to a safe state.
When in CLEAR mode, the PROFIBUS Master Unit will read each slave’s
input data, but not send output data. Depending on the slave device, the Master will instead send either empty output data messages or output data messages containing all zeros.
Enabling Auto-CLEAR
The Auto-CLEAR function can only be enabled through CX-Profibus. The controls to enable it can be found in the CS1/CJ1W-PRM21 Master DTM - Master
Setup tab (see section 6-4-1 Setting the Master Parameters).
Note The Auto-CLEAR function will only be active if the Master Unit has been
switched to OPERATE mode.
Transition Conditions
An automatic transition to CLEAR mode will take place in the following situations.
1. During network startup at least one slave device rejects its parameter or
I/O configuration message or fails to respond. All slave devices which have
already reached data exchange with the Master will be switched to CLEAR
mode again. Also, slave device which remain in not ready state during a
time period which exceeds the Data Control Time (See section 6-4-2 Setting the Bus Parameters), will cause the Master Unit to switch to CLEAR
mode.
2. After successful network start up, there is no I/O data exchange with at
least one slave device for a period of time which exceeds the Data Control
Time.
Note
1. Slave devices which have either been disabled in the Master Unit, or slave
devices for which the Ignore Auto-CLEAR flag has been set (see section
3-5-1 Configuration User Interface, Extensions Tab), will not cause a transition to Auto-CLEAR, not even when they fail on the network.
2. In case a slave device requires more time than the Data Control Time to
validate its parameter or configuration message, premature triggering of
Auto-CLEAR can be avoided by increasing the Watchdog Control Time in
the Bus parameter set (see 6-4-2 Setting the Bus Parameters). Increasing
the Watchdog time will consequently increase the Data Control Time
Resume OPERATE mode
after Auto-CLEAR
1,2,3...
The CS1/CJ1W-PRM21 PROFIBUS DP does not automatically resume normal operation after an Auto-CLEAR has been initiated. In order to resume
normal I/O data exchange, perform the following sequence.
1. Determine which slave device failed during network startup or data exchange. To do this, use the CS1/CJ1W-PRM21 Master DTM Monitoring
User Interface or the slave DTM (see sections 6-7-1 Monitoring the Master
Unit and the Network and 6-7-2 Monitoring Slave Status) to determine the
slave and its type of failure.
2. Remove the cause of the failure.
3. Press the OPERATE Button in the Master Units Monitoring window.
Alternatively, the Master can also be switched to OPERATE from the PLC program.
183
Operating the Network
6-6-5
Section 6-6
Initiating PROFIBUS DP-V1 Services
As of Unit version 2.0, the CS1/CJ1W-PRM21 PROFIBUS Master units provide a means to initiate PROFIBUS DP-V1 services from the PLC CPU.
These services allow for reading and writing (parameter) data from and to
PROFIBUS DP-V1 slave devices. This data exchange is performed acyclically, i.e. only once, in between the cyclic I/O data exchange messages.
The services are initiated using the PROFIBUS MESSAGE SEND FINS command (see section 5-2-7 PROFIBUS MESSAGE SEND (2809)). The example
below shows a ladder program initiating a PROFIBUS DP-V1 MSAC1_Read
service to retrieve data from a slave device.
Example
In the example below, a PROFIBUS DP-V1 MSAC1_Read service is send to
PROFIBUS DP-V1 slave device at address 2, requesting up to 10 data bytes
from slot number 1 (first I/O module), and index 0. The service is processed
successfully and the device returns 4 data bytes.
CIO1530.00
CIO1534 .02
@CMND
CJ1W-PRM21
In OPERATE
mode
184
Slave #2 in
data exchange
S
D00006
FINS command data source address
D
D00100
FINS Response data destination
address
C
D00000
CMND control data
87
S:
S + 1:
S + 2:
S + 3:
S + 4:
D00006
D00007
D00008
D00009
D00010
15
2
0
0
0
0
8
2
0
1
0
D:
D + 1:
D + 2:
D + 3:
D + 4:
D + 5:
D00100
D00101
D00102
D00103
D00104
D00105
15
2
0
0
0
0
0
8
0
0
0
0
0
C:
C + 1:
C + 2:
C + 3:
C + 4:
C + 5:
D00000
D00001
D00002
D00003
D00004
D00005
15
0
0
0
0
0
0
0
0
0
0
0
0
0
0
3
5
0
0
9
3
E
0
A
0
0
5
0
0
0
9
0
E
4
0
0
0
1
5
1
0
0
A
2
E
1
0
0
87
Command code : 2809 (Hex) PROFIBUS MESSAGE SEND
Slave device #2, Device Service Access Point: 33
Function code : 005E (Hex)
Slot number : 1, Index: 0
Requested data length : 10 bytes
0
87
Command code : 2809 (Hex) PROFIBUS MESSAGE SEND
Response code : Normal completion
Function code : 005E (Hex)
Actual data length : 4 bytes
Data
0
Number of command data bytes : 000A (Hex), 10 bytes
Number of response data bytes : 0012 (Hex), 18 bytes
Destination address : 0000 (Hex): Local network
0011 (Hex): PRM21 Unit number
Retries , ports
Monitoring timeout : 2 sec (default )
Monitoring the Network
6-7
6-7-1
Section 6-7
Monitoring the Network
Monitoring the Master Unit and the Network
Both the CS1/CJ1W-PRM21 Master DTM and the Generic Slave DTM provide
special user interfaces to facilitate status debugging and diagnostics determination. This section and the next will discuss the use and the features of these
diagnosis user interfaces.
CS1/CJ1W-PRM21 Master
DTM Diagnosis User
interface
The CS1/CJ1W-PRM21 Master DTM Diagnosis - Monitor User Interface provides a means to
• Monitor the CS1/CJ1W-PRM21 Master Unit status.
• Monitor an overview of the status of all allocated slave devices.
• Monitor standard slave diagnostics.
• Monitor the Unit’s Error Log
The Error Log is discussed in section 6-7-3 Using the Error Log.
The information is obtained directly from the Master Unit, using FINS commands. The Master DTM reads the Unit’s CIO words from the PLC memory,
as well as the standard slave device diagnostics bytes as received by the
Master Unit.
To open the CS1/CJ1W-PRM21 Master DTM Diagnosis - Monitor User Interface, perform the following steps.
1,2,3...
1. Make sure the Master DTM is online with the Master Unit. To go on line,
select the DTM in the Network view, and perform one of the following actions.
• Select the Device - Go Online option from the main menu, or the DTM
context menu, or
• Select the
button from the Tool Bar.
2. A communication channel will be opened through CX-Server. The name of
the DTM in the Network view, will turn to Italic font, to indicate that the Unit
is on-line.
3. From the context menu, select the Diagnosis option. The DTM’s Diagnostics User Interface will be displayed.
4. Select the Monitor tab, for status monitoring.
Using Auto-Update or
Manual Refresh
The information displayed in the CS1/CJ1W-PRM21 Master DTM Diagnosis Monitor User Interface can be updated either Automatically or Manually.
• Automatic update
Select the Automatic checkbox in the upper right corner of the Monitor
tab. The refresh cycle will be approximately 0.5 to 1 second, depending
on the PC System. The Manual button will be disabled
• Manual update
Press the Manual button in the upper right corner of the Monitor tab, to
force a refresh of the window contents.
Reading the Master Unit’s
Status
The Master status sub-tab displays the status of the Master Unit itself. The
LED indicators are directly related to the four CIO status words of the Unit
(see sections 4-2-3 to 4-2-6). They can be used to
• Obtain the status of the Master Unit and the network.
• Determine errors in the unit or the network.
• Troubleshoot the Master Unit and the network.
185
Monitoring the Network
Section 6-7
The Master Status 1 box indicates the Master Unit’s status. The Master Status
2 box and the Unit Status box all indicate errors. These LED indicators are
discussed in section 7-4-2 Troubleshooting the Network using CX-Profibus.
The Slave Status box indicates the overall status of the allocated slave
devices.
Master Status 1
Main indicators in this box are the LED indicators for operational status of the
Master Unit. They indicate whether the Master Unit is in
• OFFLINE mode,
• STOP mode,
• CLEAR mode, or in
• OPERATE mode
The Data Exchange LED indicates if I/O data exchange is taking place with at
least one slave device.
The Auto Clear enabled LED and Valid Configuration LED provide feedback
on the I/O configuration downloaded to the Unit.
Example
The figure below shows an example of the Master Status tab, in the case of a
fully functional network, i.e. there are no errors and all slave devices are
exchanging I/O data with the Master Unit.
Slave Status
The Slave Diagnostics Received LED indicates if any of the allocated slave
device have returned diagnostics information to the Master Unit. In order to
determine which slave reported diagnostics, select the Slave Status tab next
to the Master status tab.
Slave Status Overview
The CS1/CJ1W-PRM21 Master DTM Diagnosis User Interface provides a
comprehensive overview of the slave device status, without having the user to
open all the slave DTMs. The overview is presented in the Monitoring - Slave
Status tab of the user interface, and displays only the standard PROFIBUS
186
Monitoring the Network
Section 6-7
diagnostics flags. An example is shown in the figure below. For the extended,
non-standard diagnostics see section 6-7-2 Monitoring Slave Status.
The upper half of the window - the Slave Status Flags box - presents the status of each slave device using coloured LED indicators. The colours are listed
in the table below.
Indicator
Colour
Slave Status
Grey
Associated device does not exchange Diagnostics with this Master
Unit, i.e.
• Slave not allocated to this Master Unit, or
• Device is this Master Unit, or
• Device is another master device.
Example figure: Slave device 0 is not allocated.
Red
The slave device is not communicating with the PROFIBUS Master
Unit. It may be disconnected, or the Master is in OFFLINE or STOP
mode.
Example figure: Slave device 6 is not responding.
Orange
The slave device is communicating with the PROFIBUS Master
Unit, but it is not in Data Exchange, due to incorrect parameter settings. See the slave diagnostics for more information.
Yellow
The slave device is in data exchange with the PROFIBUS Master
Unit, but it has reported diagnostics data. See the slave diagnostics
for more information.
Example figure: Slave device 14 has returned diagnostics.
Green
The slave device is in data exchange with the PROFIBUS Master
Unit. No diagnostics reported.
Example figure: Slave device 2 is in I/O data exchange.
Any other colour than green or grey, indicates that new diagnostics have been
received from the associated slave device, since the last time the diagnostics
was monitored.
187
Monitoring the Network
Section 6-7
The newly received diagnostics can be viewed, by clicking with the left mouse
button on the LED indicator, indicating diagnostics. The mouse pointer will
change in to a hand icon, when positioned over the LED indicator.
Reading Standard Slave
Diagnostics
Clicking the LED indicator with the left mouse button has the following effects
• The address of the associated slave device will be displayed in the Slave
Diagnostics Data box in the lower half of the window.
• The standard diagnostics flags of the associated slave device will be displayed. LED indicators representing a status are coloured green, LED
indicators representing a potential problem are coloured red.
• The colour of the LED indicator for the specific slave device in the Slave
Status Flags box will change colour, if no new diagnostics is available, i.e.
a yellow LED will turn to green.
• The New Diagnostics Received LED indicator in the Slave Diagnostics
Data box will be set to ON.
Note If the Auto-Update refresh mode has been selected, the New Diagnostics
Received LED indicator, will be ON only during one update cycle, provided no
new diagnostics are received after displaying.
The standard diagnostics for a slave device displayed in the Slave Diagnostics
Data box can be used to
• Troubleshoot the device, the configuration or the network connection
Troubleshooting the device and the connection is discussed in section 74-2 Troubleshooting the Network using CX-Profibus.
• Determine the status of the slave device
• Determine if the slave device has reported extended diagnostics
If extended diagnostics have been reported to the Master Unit, the
Extended diagnostics received LED indicator will be on.
Refer to section 7-4-2 Troubleshooting the Network using CX-Profibus for a
discussion on the errors reported by the slave and how to correct them.
Clearing Diagnostics
Flags
Since all slave devices will have to return their status in the diagnostics message after parameterization, all the LED indicators associated with the slave
devices allocated to the Master Unit, will indicate received diagnostics right
after network startup.
If all slave devices have established I/O data exchange with the Master Unit,
this information may be less relevant. To detect new diagnostics, received during I/O data exchange, the user can clear all current new diagnostics flags by
pressing the Clear Diagnostics button in the window, thus making it easy to
spot newly received, more relevant diagnostics afterwards.
Note Pressing Clear Diagnostics button will cause all yellow LED indicators to turn
green.
188
Monitoring the Network
6-7-2
Section 6-7
Monitoring Slave Status
The Generic Slave DTM provides a Diagnosis User Interface with two tabs:
• Standard diagnostics tab, displaying the same information for the associated slave device as in the Slave Diagnostics Data box in the Master DTM
Monitoring User Interface.
• The Extended Diagnostics tab, displaying the extended diagnostics
reported by the slave device. The interpretation of this diagnostics information depends on the type of slave device.
Standard Slave
Diagnostics Example
As an example, the standard slave device diagnostics information window is
shown below. For more information regarding interpretation of the LED indicators, refer to section 6-7-1 Monitoring the Master Unit and the Network.
Extended Slave
Diagnostics
Extended diagnostics data are often - not always - provided by a slave device
to indicate additional slave specific diagnostics, error and alarm information,
which can not be contained in the standard data part of the diagnostics message. These extended diagnostics data bytes are sent by the slave in a diagnostics message following the standard data part.
For slave devices supporting extended diagnostics data, the associated GSD
files often - again, not always - provide language dependent text strings to
facilitate interpretation of the diagnostics codes, sent by the slave device.
The Generic Slave DTM provides an easy to use interface, which facilitates
the displaying of such extended diagnostics data strings.
The presence of extended diagnostics as part of the diagnostics data message, is indicated by
• the LED indicator marked Extended Diagnostics received in the Master
DTM - Monitor tab, Slave Status tab (refer to section 6-7-1 Monitoring the
Master Unit and the Network).
• the LED indicator in the Diagnostics tab of the slave Diagnostics User
Interface (see for example, the figure above).
Also, if no extended diagnostics are available, the Extended Diagnostics tab
will be disabled, and inaccessible.
To display the extended diagnostics, click on the Extended diagnostics tab in
the Slave Diagnostics User Interface.
189
Monitoring the Network
Example
6-7-3
Section 6-7
The figure below shows an example of the extended diagnostics window, containing extended diagnostics data. The first row in the diagnostics window
shows the raw data bytes, the second and third row show the actual message
contained within the extended diagnostics message.
Using the Error Log
Error Log Concept
The CS1/CJ1W-PRM21 PROFIBUS Master Units are equipped with an error
logging mechanism, which will internally store error events. Most of the errors,
which are stored in the Unit’s Error Log are stored in volatile memory, i.e.
when power to the Unit is switched off, the errors are lost.
Severe errors however, are also stored in non-volatile memory, i.e. these error
reports are still available after cycling the power down and up again. The
errors which can be logged are listed in section 7-5-2 Error Codes.
The CS1/CJ1W-PRM21 PROFIBUS Master Units can log up to 80 error
events, 16 of which can be logged in non-volatile memory.
Detecting New Errors in
the Error Log
If a new error event is logged in the Error Log of the Unit, a bit flag 03 is set in
the Units Status Word (CIO word n+4, see section 4-2-3 Unit Status (Word
n+4)).
This bit flag can be evaluated by the user, through the CS1/CJ1W-PRM21
Master DTM Diagnosis User Interface. In order to view the bit flag, perform
the following actions.
1,2,3...
1. Open the CS1/CJ1W-PRM21 Master DTM Diagnosis User Interface,
2. Select the Monitor - Master Status tab
3. If the Automatic checkbox in the Refresh box has not been selected, press
the Manual button to refresh the status.
The figure below shows as an example this Error Log Updated bit flag, indicating that a new error event has been logged.
190
Monitoring the Network
Reading the Error Log
Section 6-7
The Error Log can now be retrieved from the Unit, and displayed through the
CS1/CJ1W-PRM21 Master DTM Diagnosis User Interface. To retrieve and
view the Unit’s Error Log,
1,2,3...
1. Open the CS1/CJ1W-PRM21 Master DTM Diagnosis User Interface.
2. Select the Monitor - Error History Tab tab.
3. If the Automatic checkbox in the Refresh box has not been selected, press
the Manual button to retrieve the Error Log contents from the Unit.
As an example, the contents of the Error Log as it is displayed is shown in the
figure below. In this case a Hardware Error has been detected on the PROFIBUS network.
Note Reading the Error Log contents will not clear it.
Clearing the Error Log
1,2,3...
In order to clear the Error Log, perform the following actions.
1. Open the CS1/CJ1W-PRM21 Master DTM Diagnosis User Interface.
2. Select the Monitor - Error History Tab tab.
3. Press the Clear button in the lower right corner of the window.
191
Monitoring the Network
Section 6-7
This will clear not only the Error Log stored in volatile memory, but also the
error log events stored in the non-volatile memory.
Note Clearing the Error Log is not possible, if an error, which was just added to the
Error Log is still active. The cause of the active error has to be removed first
before the Error Log can be cleared. Attempting to clear the Error Log, while
an error is still active, does not result in an Error message from the CS1/
CJ1W-PRM21 Master DTM.
Accessing the Error Log
from the PLC CPU
192
The CS1/CJ1W-PRM21 Master DTM Diagnosis User Interface uses FINS
messages to read the CIO bit flags and access/clear the Error Log contents. A
user program running in the PLC CPU can use these same means to detect
new errors in the Error Log as well as read and clear them. Refer to sections
5-2-5 ERROR LOG READ (2102) and 5-2-6 ERROR LOG CLEAR (0203) for
details on FINS commands.
SECTION 7
Troubleshooting and Maintenance
This section describes the troubleshooting procedures and maintenance operations for the CS1/CJ1W-PRM21, needed to
keep the PROFIBUS network optimally working.
7-1
7-2
7-3
7-4
7-5
7-6
7-7
7-8
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Troubleshooting Using LED Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-2-1 LED Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-2-2 Unit Start-up Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-2-3 Unit Operational Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-2-4 Unit Configuration Errors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-2-5 Network Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Troubleshooting Using Error Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-3-1 Unit Status Word. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-3-2 Master Status 2 Word . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Troubleshooting the Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-4-1 Troubleshooting Parameter Download . . . . . . . . . . . . . . . . . . . . . . .
7-4-2 Troubleshooting the Network using CX-Profibus . . . . . . . . . . . . . .
7-4-3 Troubleshooting I/O Communication. . . . . . . . . . . . . . . . . . . . . . . .
Troubleshooting Using the Error Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-5-1 Error Log Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-5-2 Error Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Troubleshooting FINS Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-7-1 Cleaning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-7-2 Inspection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Replacing the Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-8-1 Replacement Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-8-2 Setting the Unit after Replacement. . . . . . . . . . . . . . . . . . . . . . . . . .
7-8-3 Addition/Replacement of Units on the PROFIBUS Network . . . . .
194
195
195
195
197
198
199
201
201
202
204
204
205
210
214
214
215
216
217
217
217
218
218
218
218
193
Overview
7-1
Section 7-1
Overview
The CS1/CJ1W-PRM21 PROFIBUS Master Unit and the Configuration software package provides extensive means for troubleshooting, which can be
used to quickly determine errors in the Unit, in the configuration, in the network, and/or in remote slave devices, allocated to the Unit.
Troubleshooting on the
Master Unit
For troubleshooting purposes, the following error indicators can be used:
• LED indicators on the front of the Unit
Three red error LED indicators and four status LED indicators show Unit
and network status and errors.
• CIO Words
Unit Status (CIO Word n + 4) containing status and error flags of the Unit,
and Master Status 2 (CIO Word n+6) containing error information about
the PROFIBUS network and the PROFIBUS functions of the Unit.
• The Error Log collects error codes for various error events. Serious errors
are stored in non-volatile memory and can be retrieved, even after a Unit
power down.
• FINS command provide defined response codes, which can indicate specific errors.
Note n = CIO 1500 + (25 x unit number).
This section provides a number of procedures for troubleshooting, based on
the error indicators listed above.
Troubleshooting the
Configuration Software
The Configuration software, i.e. CX-Profibus, the PROFIBUS Master DTM
and the Generic Slave DTM provide several mechanisms for error detection
and correction:
• Errors occurring in CX-Profibus are displayed in pop-up message windows and/or the error log window. The contents of the error log window
can be copied to the clipboard to allow analysis afterwards.
• CX-Profibus provides a FDT communication log window, which can be
copied to the clipboard. Analysis of this communication may provide additional information in case errors occur.
Troubleshooting the
network
The PROFIBUS Master DTM and the Generic Slave DTM diagnostics information windows, which can display:
• Indications of errors in the PROFIBUS interface of the Unit
• Indications of errors in the communication between the PROFIBUS Master Unit and remote slave devices.
• Indications of errors in the remote slave devices, allocated to the PROFIBUS Master Unit.
The CX-Profibus and DTM capabilities for troubleshooting are extensively discussed in SECTION 6 Operation.
194
Troubleshooting Using LED Indicators
7-2
7-2-1
Section 7-2
Troubleshooting Using LED Indicators
LED Indicators
This section presents a number of easy to use procedures to troubleshoot
possible errors using the LED indicators on the front of the Unit (see figure
below).
CS1W-PRM21
PRM21
RUN
ERC
BST
BF
CJ1W-PRM21
PRM21
CS
RUN
ERC
PRM COMM
ERH
BST
BF
ERH
PRM
COMM
The possible errors which could occur have been categorized and for each
category a group of two or three LED indicators can be used to troubleshoot
the problem:
• Unit start-up errors
These include errors in the PLC CPU, as well as errors in the Unit, which
prevents the combination from starting up correctly. Use RUN, ERC, and
ERH indicators to troubleshoot the errors.
• Operational errors
These include PLC errors, PLC Bus errors, and error log problems, all
during operations. Use RUN, ERC, and ERH indicators to troubleshoot
the errors.
• Configuration problems
These include errors during or after downloading a new configuration as
well as errors in the configuration after startup. Use ERC and PRM indicators to troubleshoot the errors.
• I/O data communication errors
These include errors in the PROFIBUS interface or on the network. Use
BST, COMM and BF indicators to troubleshoot.
7-2-2
Unit Start-up Errors
Unit start-up errors are errors which occur at starting up the system and which
prevent the Unit from functioning correctly in the PLC system. Usually these
errors also cause the CS/CJ PLC CPU ERR/ALM indicator to be lit or flashing.
For more information on error indications in the PLC, refer to the CS1 Series
CPU Unit Operation Manual (W339) or the CJ Series CPU Unit Operation
Manual (W393) for more details.
The error determination procedure uses the table below. To determine the
error
• First find the status of the RUN LED indicator (left column).
• Move one column to the right and find the ERH LED indicator status.
• Move one column to the right and find the ERC LED indicator status.
The probable error causes are then listed to the right of the third column.
195
Troubleshooting Using LED Indicators
Section 7-2
Unit Start up Errors
RUN
Not lit
ERH
Not lit
Lit
Lit
Not lit
ERC
Not lit
Probable cause
Correction
Power is not being supplied to the CPU
Supply power. Make sure that the correct
Unit or the power supply voltage is too low. voltage is being supplied.
The CPU Unit or Backplane is faulty.
Replace the CPU Unit or the Backplane.
The mounting screws on the PROFIBUS
Master Unit are loose (CS Series) or the
sliders are not properly locked into place
(CJ Series).
Tighten the mounting screws to the specified torque (CS Series) or lock the sliders
into place (CJ Series).
The PROFIBUS Master Unit is faulty.
Replace the PROFIBUS Master Unit.
Lit
The PROFIBUS Master Unit is faulty
(COMM LED indicator is also flashing).
Replace the PROFIBUS Master Unit.
Not lit
The I/O tables are not registered in the
CPU Unit.
Register the I/O tables.
The same unit number is being used on
another Unit as well.
Correct the unit number. Make sure that all
unit numbers used in the system are
unique.
The PLC CPU Unit is faulty.
Restart the CPU Unit. If the problem persists, replace the CPU Unit.
Lit
Not a valid combination at startup.
Not lit
Unit is functionally correct. If there are still problems, check on the other LED indicators.
Lit
During startup the checksum of the Error
Log stored in non-volatile memory was
found to be corrupted.
Send a ERROR LOG CLEAR FINS command to the Unit.
Restart the Unit.
During startup the checksum of the Param- Re-download the Parameter sets from CXeter sets stored in non-volatile memory was Profibus or the Memory Card.
found to be corrupted.
If the problem persists, replace the PROFIBUS Master Unit.
Lit
---
During startup the Parameter set stored in
non-volatile memory was correct, but the
contents contains errors preventing the
PROFIBUS interface to be initialized correctly.
Check the Parameter set in CX-Profibus
and re-download the Parameter sets from
CX-Profibus.
If the problem persists, replace the PROFIBUS Master Unit.
Memory in the CPU Unit is faulty.
Restart the CPU Unit. If the problem persists, replace the CPU Unit.
The CPU Unit is faulty.
Restart the CPU Unit. If the problem persists, replace the CPU Unit.
Note If startup errors prevent the Unit from functioning correctly, the PRM, BST and
BF LED indicators will remain OFF.
196
Troubleshooting Using LED Indicators
7-2-3
Section 7-2
Unit Operational Errors
Unit Operational errors are errors which can occur during normal operation,
i.e. after normal startup.
The error determination procedure uses the table below. To determine the
error, first find the status of the RUN LED indicator (left column). Then move
one column to the right and find the status of the ERH LED indicator. Then
move again one column to the right and find the status of the ERC LED indicator. The probable error causes are listed to the right of the third column.
Unit Operational Errors.
RUN
Not lit
ERH
Not lit
Lit
Lit
Not lit
ERC
Not lit
Probable cause
Correction
Power is not being supplied to the CPU
Supply power. Make sure that the correct
Unit or the power supply voltage is too low. voltage is being supplied.
The CPU Unit or Backplane is faulty.
Replace the CPU Unit or the Backplane.
The mounting screws on the PROFIBUS
Master Unit are loose (CS Series) or the
sliders are not properly locked into place
(CJ Series).
Tighten the mounting screws to the specified torque (CS Series) or lock the sliders
into place (CJ Series).
A fatal error has occurred in the Unit, preventing it from running any program.
Restart the CPU Unit. If the problem persists, replace the PROFIBUS Master Unit.
Lit
A fatal error has occurred in the Unit’s program. The appropriate error code is stored
in the error log.error
Restart the CPU Unit. If the problem persists, replace the PROFIBUS Master Unit.
Not lit
Not a valid combination during operation.
Lit
Not a valid combination during operation.
Not lit
Unit is functionally correct. If there are still problems, proceed to check on the other LED
indicators.
Lit
A write-verify check failed, while writing the Send a ERROR LOG CLEAR FINS comerror log to the non-volatile memory.
mand to the Unit. Restart the Unit.
A write-verify check failed, while writing the Check the Parameter set in CX-Profibus
(new) configuration to the non-volatile
and re-download the Parameter sets from
memory.
CX-Profibus.
If the problem persists, replace the PROFIBUS Master Unit.
Lit
Not Lit
Memory in the CPU Unit is faulty.
Restart the CPU Unit. If the problem persists, replace the CPU Unit.
The CPU Unit is faulty.
Restart the CPU Unit. If the problem persists, replace the CPU Unit.
A cyclic Monitor time out has occurred, i.e a Restart the CPU Unit. If the problem persists, replace the PROFIBUS Master Unit.
timeout on exchange of data between the
Unit and the PLC CPU.
Lit
Not a valid combination during operation.
Note If operational errors prevent the Unit from functioning correctly, the PRM,
BST, COMM and BF LED indicators will remain OFF.
197
Troubleshooting Using LED Indicators
7-2-4
Section 7-2
Unit Configuration Errors
Unit configuration errors are errors which occur during download of the new
configuration, or after restarting the Unit, following a download. The error can
be determined by examining the ERC and the PRM LED indicators.
The error determination procedure uses the table below. To determine the
error
• First find the status of the ERC LED indicator (left column).
• Move one column to the right and find the PRM LED indicator status.
The probable error causes are then listed to the right of the third column.
Unit Configuration Errors
ERC
Not Lit
Lit
PRM
Probable cause
Correction
Not Lit
Not a valid combination.
Lit
No errors. The PROFIBUS DP Parameter set is ready for use.
Flashing
No errors. A new configuration is being downloaded from the configurator or from the Memory Card.
Not Lit
An error has occurred while writing the Parameter sets to the non-volatile memory.
Re-download the Parameter sets from CX-Profibus or the Memory Card.
If the problem persists, replace the PROFIBUS
Master Unit.
During startup the checksum of the Parameter
sets stored in non-volatile memory was found to
be corrupted.
Re-download the Parameter sets from CX-Profibus or the Memory Card.
If the problem persists, replace the PROFIBUS
Master Unit.
During startup the Parameter set stored in nonvolatile memory was correct, but the contents
contains errors preventing the PROFIBUS interface to be initialized correctly.
Check the Parameter set in CX-Profibus and redownload the Parameter sets from CX-Profibus.
If the problem persists, replace the PROFIBUS
Master Unit.
Lit
Not a valid combination.
Note
1. The table above assumes that the RUN LED indicator is ON and the ERH
indicator is OFF. Otherwise, refer to section 7-2-2 Unit Start-up Errors, or
section 7-2-3 Unit Operational Errors.
2. If the PRM LED indicator is OFF or Flashing, the BST, COMM and BF LED
indicators remain OFF.
198
Troubleshooting Using LED Indicators
7-2-5
Section 7-2
Network Errors
Network errors are errors which occur when attempting to startup a network,
i.e. the PROFIBUS Master Unit has been switched to CLEAR or OPERATE
mode. The Unit will parameterize the slave devices and start data exchange.
An error in this process can be determined by examining the BST, COMM and
BF LED indicators.
The error determination procedure uses the table below. To determine the
error
• First find the status of the BST LED indicator (left column).
• Move one column to the right and find the COMM LED indicator status.
• Move one column to the right and find the BF LED indicator status.
The probable error causes are then listed to the right of the third column.
Network Errors
BST
Not lit
COMM
Not lit
BF
Probable cause
Correction
Not lit
The PROFIBUS Master Unit is in OFFLINE Switch the Unit to either CLEAR or OPERor STOP mode. No communication over the ATE mode.
network.
Lit
A hardware error has occurred in the
PROFIBUS interface of the Unit, or a master device has been detected beyond the
Highest Station Address. The Unit has
switched to OFFLINE.
This indicates faulty wiring, broken message, short-circuits, faulty bus timings, or
an active device has been detected beyond
the Highest Station Address setting (HSA).
• Check the network wiring, and make
sure it is correct (not too long, long stub
lines, etc.)
• Check for short-circuits.
• Check the bus timing set in CX-Profibus.
• Check the HSA setting in the DTM’s Bus
Parameter tab. Set it to the highest master address which is on the network.
• Check if any other faulty devices are on
the same network.
• Switch the Unit to CLEAR / OPERATE
mode again.
A protocol error has occurred in the PROFI- • Check the network wiring, and other
BUS interface of the Unit, the Unit has
master devices on the network. Make
switched to OFFLINE.
sure they are all correct.
•
Check
if any other faulty devices are on
This indicates lost tokens.
the same network.
• Switch the Unit to CLEAR / OPERATE
mode again.
A Double-Address error has occurred on
the network, i.e. there is a second master
device with the same PROFIBUS address
on the network. the Unit has switched to
OFFLINE.
Lit
Not lit
Not a valid combination.
Lit
Not a valid combination.
• Check the master devices on the network. Make sure they all have unique
network addresses.
• After correction, switch the Unit to
CLEAR / OPERATE mode again.
199
Troubleshooting Using LED Indicators
BST
COMM
Flashing/ Not lit
Lit
Lit
BF
Probable cause
Section 7-2
Correction
Not lit
Not a valid combination.
Lit
A Bus disturbance error has been detected. • Switch the Unit to OFFLINE mode.
This indicates a termination error (termina- • Terminate the network at the appropriate
places (see section 2-4-2 Bus Termination resistors are missing, or inductors are
tion).
not used), or two slave devices with the
same address.
• Check if any other faulty devices are on
the same network.
• Switch the Unit to CLEAR / OPERATE
mode again.
Flashing
• None of the allocated slave devices
responds to the master’s request messages.
• None of the slaves is in I/O data
exchange with the Master Unit.
This may indicate a loose network connector on the Master Unit, or a broken cable.
Not-Lit
There are no errors. The Unit is in CLEAR or OPERATE mode and exchanging data.
Lit
Not a valid combination.
Flashing
At least one slave device has responded to
the master’s request messages and is not
in Data Exchange. There is also at least
one slave which has either
• not responded to the master’s requests
messages, or
• been parameterized incorrectly.
• Switch the Unit to OFFLINE mode.
• Check the network wiring.
• Check if any other faulty devices are on
the same network.
• Check if actual slave addresses match
the configured addresses.
• Check if the slave parameter settings
are correct. If necessary change them,
and download them again.
• Switch the Unit to CLEAR / OPERATE
mode again.
• Switch the Unit to OFFLINE mode.
• Check the network wiring.
• Check if any other faulty devices are on
the same network.
• Check if the slave parameter settings
are correct. Re-download after correction.
• Switch the Unit to CLEAR / OPERATE
mode again.
Note The table above assumes that the RUN and the PRM LED indicators are ON
and the ERH indicator is OFF. Otherwise, refer to section 7-2-2 Unit Start-up
Errors, section 7-2-3 Unit Operational Errors or section 7-2-4 Unit Configuration Errors.
200
Troubleshooting Using Error Status
7-3
Troubleshooting Using Error Status
Error status in CIO Words
7-3-1
Section 7-3
The PROFIBUS Master Unit provides error status indications to the PLC CPU
Unit in the Unit Status Word and the Master Status Word 2, which are part of
the CIO Words.
Unit Status Word
The Unit status word (CIO Word n+4) contains status and error indications on
the Unit itself. The figure below shows the Unit Status Word Layout. The corresponding bit flag will turn ON if an error event has occurred.
15 14 13 12 11 10 9
8
7
6
5
4
3
2
1
0
Word n+4
Unit error flag
Master error flag
Error log contains new errors
Parameter transfer in progress
Local parameter storage error
Local parameter load error
File read error
Error log storage error
Note n = CIO 1500 + (25 x unit number).
Bit
Name
Description / Correction
00
Unit error flag
If this bit is set, one of the other error flags in the Unit Status Word is set. Refer to
these bits for error determination.
01
Master error flag
If this bit is set, one of the error flags in the Master Status 2 Word is set. Refer to
these bits for error determination.
03
Error Log contains new
errors
There are new errors available in the Error Log, since the last time the error log was
read. Reading the error log (using the ERROR LOG READ FINS command) will
clear this bit flag.
04
Parameter transfer in
progress
A Parameter transfer is in progress either from the configurator to the Unit or
between the Unit and the Memory Card.
06
Local parameter storage
error
An error has occurred, when writing the configuration to the non-volatile memory.
To correct this:
• Restart the Unit.
• Re-download the configuration.
• If the problem persists, replace the PROFIBUS Master Unit.
07
Local parameter load error
An error has occurred, when loading the configuration from the non-volatile memory to the volatile memory at start up.
Most likely causes:
• A failure or interruption during the writing process.
• A faulty parameter setting, which makes initialization of the PROFIBUS interface
not possible.
To correct this:
• Check the parameter settings for incorrect values.
• Restart the Unit.
• Re-download the configuration.
• If the problem persists, replace the PROFIBUS Master Unit.
201
Troubleshooting Using Error Status
09
File read error
Section 7-3
An error has occurred, when loading the configuration from the non-volatile memory to the volatile memory at start up. Most likely cause is a failure or interruption
during the writing process.
Most likely causes:
• A failure or interruption during the writing process.
• A failure during the reading process.
• A faulty Memory Card.
To correct this:
• Check the Memory Card for faults.
• Restart the PLC Unit, to re-download the configuration.
• If the problem persists, use CX-Profibus to re-download the configuration.
• If the problem persists, replace the PROFIBUS Master Unit.
13
7-3-2
Error Log storage error
An error has occurred, when writing the error log to the non-volatile memory, or
when reading the error log from non-volatile memory during start up.
Most likely causes: A failure or interruption during the writing process.
To correct this:
• Send an ERROR LOG CLEAR FINS command to the Unit.
• Restart the Unit.
• If the problem persists, replace the PROFIBUS Master Unit.
Master Status 2 Word
The Master Status 2 Word (CIO Word n+6) contains error indications on the
PROFIBUS interface and network. The figure below shows the Master Status
2 Word layout. The corresponding bit flag will turn ON if an error event has
occurred.
15 14 13 12 11 10 9
8
7
6
5
4
3
2
1
0
Word n+6
Disturbed bus error
PROFIBUS protocol error
Double Master address error
Hardware error
Mode command error
Parameter error
Note n = CIO 1500 + (25 x unit number).
Bit
00
Name
Disturbed bus Error
Description / Correction
An error has occurred in the PROFIBUS interface, with distorted messages
received by the PROFIBUS Master Unit.
Most likely causes:
• No or invalid termination or no inductors used at high baud rates.
• Faulty wiring.
To correct this:
• Check the termination on the appropriate devices.
• Restart the PLC Unit, to re-download the configuration.
• If the problem persists, use CX-Profibus to re-download the configuration.
• If the problem persists, replace the PROFIBUS Master Unit.
202
Troubleshooting Using Error Status
01
PROFIBUS protocol error
Section 7-3
An error has occurred in the PROFIBUS interface, with distorted messages
received by the PROFIBUS Master Unit.
Most likely causes:
• Lost token messages (the token is not returned).
To correct this:
• Check the master devices on the network, and make sure they are all working
correctly.
• After correction, switch the Unit to CLEAR / OPERATE mode again.
02
Double master address
error
A second master device with the same network address has been detected on the
PROFIBUS network. The PROFIBUS Master Unit has switched to OFFLINE.
To correct this:
• Check the master devices on the network and ensure that they have unique
device addresses.
• After correction, switch the Unit to CLEAR / OPERATE mode again.
03
Hardware error
A hardware error has occurred in the PROFIBUS interface of the Unit. The PROFIBUS Master Unit has switched to OFFLINE.
Most likely causes:
• Faulty wiring,
• Broken messages,
• Short-circuits, or
• Faulty bus timings.
• A master device has been detected beyond the Highest Station Address (HSA).
To correct this:
• Check the network wiring, and make sure it is correct.
• Check for short-circuits.
• Check the bus timing set through CX-Profibus.
• Check if any other faulty devices are on the same network.
• After correction, switch the Unit to CLEAR / OPERATE mode again.
12
Mode command error
An error has occurred when setting two or more mode switches in Switch Word
(CIO Word n). The flag will be set to ON, until the correct command, i.e. one mode
switch has been issued.
13
Parameter error
An error has occurred initializing the PROFIBUS interface, after reading the parameter sets from the non-volatile memory to the volatile memory.
Most likely cause: A faulty parameters has been downloaded to the Unit.
To correct this: Check the parameter settings in CX-Profibus and correct them if
necessary. After correction, perform a download of the new parameters to the Unit.
203
Troubleshooting the Network
7-4
7-4-1
Section 7-4
Troubleshooting the Network
Troubleshooting Parameter Download
The PROFIBUS Master DTM provides clear error messages if downloading of
the parameters to the PROFIBUS Master Unit fails. Failure can be due to
either
• Errors or inconsistencies in the slave parameter sets, which are checked
prior to download.
• The Master DTM being unable to establish communication with the CS1/
CJ1W-PRM21 PROFIBUS Master Unit.
• A communication interruption of the process during download.
Errors in Slave Parameter
Sets
The error messages displayed will provide a clear indication of the problem.
A download initiated by the user, starts with a check on the slave parameter
sets. The Master DTM will check
• The total number of slave devices assigned, which must be at least one
slave device.
• The total number of I/O modules per slave, which must be at least one I/O
module per slave.
• The maximum size of the I/O data size, which must not exceed 7168
words.
• The maximum number of I/O modules, which must not exceed 4000.
• Any existing overlap in the I/O Areas configured.
• Any existing overlap in the allocated PLC memory areas.
• Availability of EM banks should any of the I/O Areas be mapped to one of
the EM Banks. Availability of the EM banks depends on the PLC CPU
type.
Anyone of these errors will abort the download process without consequences for the CS1/CJ1W-PRM21 PROFIBUS Master Unit.
The error messages associated with these failures are listed in Appendix D-2
Error Messages - Configuration. The list also provides remedies.
Errors when Establishing
Communication
If no errors occurred during the checking phase, the Master DTM will try to
establish communication with the CS1/CJ1W-PRM21 PROFIBUS Master Unit
through CX-Server. If this fails, an error message will be displayed, indicating
a communication problem (see Appendix D-3 Error Messages - Communication). A failure to establish communication prior to download will have no consequences for the CS1/CJ1W-PRM21 PROFIBUS Master Unit. The list
provided in Appendix D-3 Error Messages - Communication also provides
possible remedies.
Errors During Download
If none of the first two processes result in a failure, downloading will commence. As soon as downloading has started, the data in the volatile memory
of the CS1/CJ1W-PRM21 PROFIBUS Master Unit will be overwritten.
Recovery After Failing
Download
If a failure occurs during the download process, which prevents the Master
DTM from completing the process, the user must restart the Unit manually.
Restarting the Master Unit will abort the download process in the Master Unit
and recover the previous configuration from its non-volatile memory.
204
Troubleshooting the Network
7-4-2
Section 7-4
Troubleshooting the Network using CX-Profibus
CX-Profibus
Troubleshooting
CX-Profibus provides several means to troubleshoot either the CS1/CJ1WPRM21 PROFIBUS Master Unit, the slave devices or the network. The means
all rely on features discussed in the previous section.
Troubleshooting the
Master Unit
To troubleshoot the Master Unit or the network, the Master DTM Diagnosis
User Interface provides a help in determining problems. The figure below
shows the Monitor - Master Status tab of the Master DTM Diagnosis User
Interface.
The LED indicators shown in the (example) figure above are all related to bit
flags in the Unit Status Word, the Master Status Word 1, the Master Status
Word 2, and the Slave Status Word (see section 4-2 Allocated CIO Area
Words).
The table below lists combinations of LED indicators with information on possible problems.
205
Troubleshooting the Network
LED Indicators
Section 7-4
Description / Correction
Local Parameter Storage Error
(Valid Configuration Indicator will
be OFF)
An error has occurred, when writing the configuration to the non-volatile memory.
To correct this:
• Restart the Unit.
• Re-download the configuration.
• If the problem persists, replace the PROFIBUS Master Unit.
Local Parameter Load Error
(Valid Configuration Indicator will
be OFF)
An error has occurred, when loading the configuration from the non-volatile memory
to the volatile memory at start up.
Most likely causes:
• A failure or interruption during the writing process.
• A faulty parameter setting, which makes initialization of the PROFIBUS interface
not possible.
To correct this:
• Check the parameter settings for incorrect values.
• Restart the Unit.
• Re-download the configuration.
• If the problem persists, replace the PROFIBUS Master Unit.
File read error is ON
(Valid Configuration Indicator will
be OFF)
An error has occurred, when loading the configuration from the non-volatile memory
to the volatile memory at start up.
Most likely causes:
• A failure or interruption during the writing process.
• A failure during the reading process.
• A faulty Memory Card.
To correct this:
• Check the Memory Card for faults.
• Restart the PLC Unit, to re-download the configuration.
• If the problem persists, use CX-Profibus to re-download the configuration.
Parameter error: ON
(Valid Configuration Indicator will
be OFF)
An error has occurred initializing the PROFIBUS interface, after reading the parameter sets from the non-volatile memory to the volatile memory.
Most likely cause:
• A faulty parameters has been downloaded to the Unit.
To correct this:
• Check the parameter settings in CX-Profibus and correct them if necessary. After
correction, perform a download of the new parameters to the Unit.
Disturbed bus Error: ON
An error has occurred in the PROFIBUS interface, with distorted messages received
by the PROFIBUS Master Unit.
Most likely causes:
• No or invalid termination or no inductors used at high baud rates.
• Faulty wiring.
To correct this:
• Check the termination on the appropriate devices.
• Restart the PLC Unit, to re-download the configuration.
• If the problem persists, use CX-Profibus to re-download the configuration.
• If the problem persists, replace the PROFIBUS Master Unit.
206
Troubleshooting the Network
LED Indicators
PROFIBUS protocol error: ON
(OFFLINE indicator will be ON)
Section 7-4
Description / Correction
An error has occurred in the PROFIBUS interface, with distorted messages received
by the PROFIBUS Master Unit.
Most likely causes:
• Lost token messages (the token is not returned).
To correct this:
• Check the master devices on the network, and make sure they are all working correctly.
• After correction, switch the Unit to CLEAR / OPERATE mode again.
Double master address error: ON
(OFFLINE indicator will be ON)
A second master device with the same network address has been detected on the
PROFIBUS network. The PROFIBUS Master Unit has switched to OFFLINE.
To correct this:
• Check the master devices on the network and ensure that they have unique
device addresses.
• After correction, switch the Unit to CLEAR / OPERATE mode again.
Hardware error: ON
(OFFLINE indicator will be ON)
A hardware error has occurred in the PROFIBUS interface of the Unit. The PROFIBUS Master Unit has switched to OFFLINE.
Most likely causes:
• Faulty wiring,
• Broken messages,
• Short-circuits, or
• Faulty bus timings.
• A master device has been detected beyond the Highest Station Address (HSA).
To correct this:
• Check the network wiring, and make sure it is correct.
• Check for short-circuits.
• Check the bus timing set through CX-Profibus.
• Check if any other faulty devices are on the same network.
• After correction, switch the Unit to CLEAR / OPERATE mode again.
• Auto-Clear enabled: ON
This combination indicates that one of the slave devices on the network failed, causing an automatic transition to the CLEAR mode.
• CLEAR: ON
• Slave Diagnostics received: ON Check the Monitor - Slave Status tab, to see which slave failed.
• OPERATE: ON
• Slave Diagnostics received is:
ON
• Data Exchange: OFF
• Auto-Clear enabled: OFF
Troubleshooting the Slave
Devices
The Master Unit is still in OPERATE mode, but not exchanging data with all its slave
devices. One or more of the slave devices on the network failed.
Check the Monitor - Slave Status tab, to see which slave failed.
If the Master Status tab indicates problems related to slave devices, their status can be obtained by checking the Slave Status tab. The figure below shows
this tab. As an example a failure of slave device 2 is shown.
207
Troubleshooting the Network
Section 7-4
The LED indicators in the upper half of the Slave Status tab shown in the figure above, indicates the status of the slave devices, by using different colours
(see section 6-7-1 Monitoring the Master Unit and the Network, Slave Status
Overview).
In case an LED indicator is either Red or Orange, additional information can
be obtained from the PROFIBUS Master Unit, by using the mouse pointer to
click on the coloured LED indicator. The basic diagnostics information, for the
selected slave device is retrieved from the Master Unit and displayed in the
lower half of the Slave Status tab. The table below lists the LED indicators,
which are of interest for troubleshooting.
LED Indicator
Description / Correction
Station non-existent
The slave device does not respond to any of the request messages sent by the Master Unit.
• Make sure that the slave device is powered correctly.
• Check the wiring and make sure that the slave device and the Master Unit are connected.
Station not ready
The slave is communicating, but not ready for data transfer.
• Check the slave device and make sure that it is working properly.
• Check any loose modules, in case the slave device is a modular device.
• Consult the operation manual of the slave device. Check if additional action must be taken to
initiate I/O data exchange (e.g. reset the device after a malfunction).
Configuration fault
The I/O configuration sent by the Master Unit is rejected by the slave device. The Parameter
request used LED indicator will also be ON.
• Check the selected I/O modules in the Slave DTM. Make sure they match the expected total
I/O number and sequence.
• Consult the operation manual of the slave device. Check if additional modules must be
selected (e.g. empty i/O modules for power modules in a modular slave).
208
Troubleshooting the Network
LED Indicator
Extended diagnostics
received
Section 7-4
Description / Correction
The slave device has returned extended diagnostics information. This does not necessarily indicate a malfunction. The Master DTM does not display the extended diagnostics returned by a
slave device. Open the associated Slave DTM to check on the contents of the extended diagnostis.
Function not supported
The Master Unit has sent a message to the slave device, which is not supported by that device.
Invalid slave response
This bit is set by the Master Unit if the slave has returned an invalid response to a master
request message.
Parameter fault
The parameters sent by the Master Unit are rejected by the slave device. The Parameter
request used LED indicator will also be ON.
• Check the common parameter settings in the Slave DTM. Make sure the parameters are
within range, and match the physical configuration of the slave device.
• Consult the operation manual of the slave device. Check if additional parameters must be
selected (e.g. parameters associated with selected I/O modules).
Master lock
The slave device is parameterized and locked by another Master Unit on the network. The
Parameter request used LED indicator will also be ON.
• Remove the slave device from either one of the two Master Units on the network.
• Switch off the other Master Unit.
Parameter request used The slave device is not in I/O data exchange with the Master Unit and has requested new
parameters.
• Check the parameters and the I/O configuration for the slave device and make sure they are
correct (Check the Parameter fault, Configuration fault and Master Lock LED indicators).
Static diagnostics
The slave device is sending static diagnostics, and is not exchanging I/O data. This usually indicates a problem at the slave device which prevents it from reading its inputs or setting its outputs.
• Check the slave device and make sure that it is working properly.
• Check any loose modules, in case the slave device is a modular device.
• Check the wiring of the I/O at the slave device. Slaves can often detect short-circuits on their
physical I/O.
• Consult the operation manual of the slave device. Check if additional action must be taken to
initiate I/O data exchange (e.g. reset the device after a malfunction).
Station type
This LED indicator only indicates the device type (i.e. slave device) and does not indicate a
problem.
Watchdog On
This LED indicator only indicates that the Watchdog has been enabled at the slave device and
does not indicate a problem.
Freeze mode
This LED indicator only indicates the slave device has received a Global-Control Freeze command and does not indicate a problem.
Sync mode
This LED indicator only indicates the slave device has received a Global-Control Sync command and does not indicate a problem.
Slave deactivated
This LED indicator indicates the slave device has been disabled in the Master Unit and does not
indicate a problem.
Extended diagnostics
overflow
The slave device has more diagnostics to report than it can hold in its buffer. This is usually an
indication for problems.
• Check the slave device’s extended diagnostics information. Open the associated Slave DTM
to check on the contents of the extended diagnostics, if this has been returned.
• Check the slave device and make sure that it is working properly.
• Check any loose modules, in case the slave device is a modular device.
• Check the wiring of the I/O at the slave device. Slaves can often detect short-circuits on their
physical I/O.
• Consult the operation manual of the slave device. Check if additional action must be taken to
initiate I/O data exchange (e.g. reset the device after a malfunction).
209
Troubleshooting the Network
7-4-3
Section 7-4
Troubleshooting I/O Communication
This section deals with troubleshooting the I/O communication on the network
from a behaviour point of view. The column on the left describes the general
perceived problem to the user. The columns on the right list the possible
causes and their remedies.
Communication Problems
Problem
PROFIBUS Master Unit is
configured, but none of the
slaves are exchanging
data.
210
Probable cause
Correction
No power is supplied to the system.
• Verify that power is supplied to the system.
• All LED indicators on the system are OFF.
A PLC CPU (startup) error occurred.
• The ERH indicator is ON, the other LED
indicators are OFF.
• The ERR/ALM LED indicator on the PLC
CPU is ON.
• Determine error in the PLC CPU (Refer to
the CS1 Series CPU Unit Operation Manual (W339) or the CJ Series CPU Unit
Operation Manual (W393)).
The stored configuration contains a checksum error (storing configuration was interrupted or failed).
• After restarting the Unit, the ERC LED
indicator is ON, and the PRM LED indicator is OFF.
• Unit Status error flag may provide more
information (CIO Word n+4, bit 06, bit 07,
bit 09, see Note).
• Re-download the configuration.
• If the problem persists, replace the Unit.
The configuration contains timing errors.
• After restarting the Unit, the ERC LED
indicator is ON, and the PRM LED indicator is OFF.
• Verify that the Bus parameter sets are correct.
• Re-download the configuration.
• If the problem persists, replace the Unit.
The PROFIBUS Master Unit is in either
OFFLINE or STOP mode.
• The BST LED indicator is OFF
The Unit may have been configured to
maintain its current mode (last mode was
OFFLINE, during download).
• The BF LED indicator is ON: A PROFIBUS
interface error has occurred: see Master
Status 2 error flags (CIO Word n+6, bit 00
~ 03, see Note) for details.
Determine the mode of the Unit: Check the
Master Status 1 Word (CIO Word n+5, bit 00
to bit 03, see Note). If Unit is in OFFLINE or
STOP mode:
• Verify that the master does not use the
same address as another Master Unit on
the network. Otherwise, correct the Master
Unit’s PROFIBUS address.
• Set CLEAR or OPERATE switch in CIO
Word n (see Note).
• Change the configuration to set the Unit
OPERATE mode when switching the PLC
to RUN/MONITOR mode (see Master
DTM, Master Setup Tab). Download the
configuration, and switch the PLC to RUN/
MONITOR mode.
Network cabling is not correct.
• BF LED indicator is ON.
• Master Status 2 error flag may provide
more information (CIO Word n+6, bit 00 ~
03, see Note).
• CIO Words n+9 to n+16 show which
slaves have problems.
Verify that the network installation is correct:
• Verify that all slaves are powered up and
functioning correctly.
• Verify that all slave devices are correctly
connected to the network.
• Verify that any repeaters used are functioning correctly.
• Check the cable length versus the
selected baud rate.
• Verify that any stubs used are not too
long.
• Verify that termination (resistors and
inductors) are properly set and used.
Troubleshooting the Network
Problem
PROFIBUS Master Unit is
configured. Some, but not
all slaves exchange data.
Section 7-4
Probable cause
Correction
Network cabling is not correct.
• BF LED indicator is ON or Flashing.
• Master Status 2 error flag may provide
more information (CIO Word n+6, bit 00 ~
03, see Note).
• CIO Words n+9 to n+16 show which
slaves have problems.
Verify that the network installation is correct:
• Verify that all slaves are powered up and
functioning correctly.
• Verify that all slave devices are correctly
connected to the network.
• Verify that any repeaters used are functioning correctly.
• Check the cable length versus the
selected baud rate.
• Verify that any stubs used are not too
long.
• Verify that termination (resistors and
inductors) are properly set and used.
Configuration is not correct.
• BF LED indicator is Flashing.
• CIO Words n+9 to n+16 show which
slaves have problems.
• Use CX-Profibus and DTMs to determine
slave diagnostics.
Verify that the configuration is correct:
• Verify that address of targeted slave
device matches the configured address.
• Verify that the slave parameter and configuration settings are correct.
• Verify that the watchdog setting for the
slave device is not too low.
The configuration contains timing errors.
• Verify that the Bus parameter sets are correct. If necessary, increase Target Rota• BF LED indicator is Flashing.
tion Time and/or Min. Slave Interval
• Slaves are sometimes briefly in and out of
parameters.
data exchange.
• Re-download the configuration.
• If the problem persists, replace the Unit.
A second master device (with its own slave
devices) is on the same network, interfering
with this Master Unit.
• The baud rate settings of both masters is
different.
• The total Target Rotation Time set to both
masters is too small (i.e. not the sum of
both individual time values).
• Verify that all masters on the network are
set to the same baud rate.
• Verify that the total Target Rotation Time
for all masters on the network is set to the
sum of all individual masters.
Use the FINS RUN command to enable the
Specific slave devices are configured and
slave devices.
allocated to the Master Unit, but the slave
which is not exchanging data may have been
disabled using the FINS STOP command.
211
Troubleshooting the Network
Problem
Section 7-4
Probable cause
PROFIBUS Master Unit is No power is supplied to the system. All LED
configured. All slaves were indicators on the system are OFF.
in data exchange, but it has
A PLC CPU error occurred.
now stopped.
• The ERH indicator is ON, the other LED
indicators are OFF.
• The ERR/ALM LED indicator on the PLC
CPU is ON.
PROFIBUS Master Unit is
configured. After switching
the Master Unit to OPERATE, the Unit itself or other
Units on the PLC CPU
showed unexpected behaviour.
212
• Determine error in the PLC CPU (Refer to
the CS1 Series CPU Unit Operation Manual (W339) or the CJ Series CPU Unit
Operation Manual (W393)).
A Unit error occurred.
• The ERC indicator is ON, the other LED
indicators are OFF.
• The ERR/ALM LED indicator on the PLC
CPU is ON.
• Restart the Unit, and read the error log to
determine the type of error.
The PROFIBUS Master Unit is in either
OFFLINE or STOP mode.
• The BST LED indicator is OFF
• The BF LED indicator is ON: A PROFIBUS
interface error has occurred: see Master
Status 2 error flags (CIO Word n+6, bit 00
~ 03, see Note) for details.
Determine the mode of the Unit: Check the
Master Status 1 Word (CIO Word n+5, bit 00
to bit 03, see Note). If Unit is in OFFLINE or
STOP mode:
• Verify that the master does not use the
same address as another Master Unit on
the network. Otherwise, correct the Master
Unit’s PROFIBUS address.
• Set CLEAR or OPERATE switch in CIO
Word n (see Note).
Network cabling is not correct.
• BF LED indicator is ON.
• Master Status 2 error flag may provide
more information (CIO Word n+6, bit 00 ~
03, see Note).
Verify that the network installation is correct:
• Verify that the network is still in tact, and
connected to the Unit.
• Verify that any repeaters used are functioning correctly.
The I/O data mapping of the Master Unit may Verify the I/O Mapping of the Master Unit:
overwrite either its won or other Unit CIO/DM • Ensure that the I/O data of the Master
Areas settings:
Unit, does not overwrite its own CIO
words.
•
Ensure that the I/O data of the Master
• Master Unit operational mode changes
Unit, does not overwrite CIO words or DM
unexpectedly.
words of other Special I/O or Special CPU
• Global-Control commands are transmitted
Units (e.g. Ethernet Units)
unexpectedly.
• Other Special I/O Units or Special Bus
Units change behaviour unexpectedly.
The bus parameter used on the network are
wrong.
• I/O data exchange between the Master
Unit and the PLC stops.
•
PROFIBUS Master Unit is
configured. All slaves were
in data exchange, but all
outputs are now set to
zeros. Inputs can still be
read.
Correction
• Verify that power is supplied to the system.
Verify that the correct bus parameters have
been used.
• (If necessary) Restart the Unit and force it
to OFFLINE immediately, or
• Disconnect the network cable first and
restart the Unit.
• Download the correct Bus parameters.
• If Auto-CLEAR is enabled, correct the netThe Master Unit is in CLEAR mode.
work problem first.
• The BST LED indicator is Flashing.
•
Set OPERATE switch in CIO Word n (see
• The CLEAR switch has been set in the
Note) to force the Unit to the OPERATE
Switch word 1 (CIO Word n, bit 02, see
mode.
Note)
• The Unit has been configured for AutoCLEAR and an error occurred on the Network with one or more slave devices.
Troubleshooting the Network
Problem
Section 7-4
Probable cause
PROFIBUS Master Unit is The specified slave devices may be in Sync
configured. All slaves are in mode.
data exchange, but the outputs of some slave devices
are not updated.
The specified slave device may have its
watchdog disabled and is disconnected from
the network, due to a cabling problem.
• BF LED indicator is Flashing.
• CIO Words n+9 to n+16 (see Note) show
which slaves have problems.
• Use CX-Profibus and DTMs to determine
slave diagnostics.
PROFIBUS Master Unit is The specified slave devices may be in
configured. All slaves are in Freeze mode.
data exchange, but the
inputs of some slave
devices are not updated.
The specified slave device may have its
watchdog disabled and is disconnected from
the network, due to a cabling problem.
• BF LED indicator is Flashing.
• CIO Words n+9 to n+16 (see Note) show
which slaves have problems.
• Use CX-Profibus and DTMs to determine
slave diagnostics.
Correction
Send a Global-Control Unsync command to
the targeted slave or group of slaves. Use
either the Global-Control feature in CIO
Words. Refer to 4-2-2 Global-Control Message (Word n+2).
Verify that the specified slave device is still
connected to the network.
Send a Global-Control Unfreeze command to
the targeted slave or group of slaves. Use
either the Global-Control feature in CIO
Words. Refer to 4-2-2 Global-Control Message (Word n+2).
Verify that the specified slave device is still
connected to the network.
Note n = CIO 1500 + (25 x unit number).
213
Troubleshooting Using the Error Log
7-5
7-5-1
Section 7-5
Troubleshooting Using the Error Log
Error Log Overview
The PROFIBUS Master Unit maintains an Error Log, which contains the
reports on specific error events.
Logged Errors
The following errors are recorded in the error log.
• Errors in network operation
• Errors in data transfers
• Error in the CPU Unit
Error Log Records
Each error is recorded as one record in an error log table. Each record contains:
• A main error code (see 7-5-2 Error Codes)
• A detailed error code (see 7-5-2 Error Codes)
• A time stamp (from the clock in the CPU Unit)
Error Log Location
When an error is detected, the error codes and time stamp are recorded in an
error log record, which is stored in the error login volatile memory (i.e. RAM
memory) inside the PROFIBUS Master Unit. Serious errors are also recorded
in non-volatile memory (i.e. Flash ROM).
A total of 80 error records can be logged in volatile memory.
Up to 16 more serious system errors are also copied to non-volatile memory.
Adding Error Records to
the Error Log
When adding a new record to the error log and the error log is full, the latest
error will replace the oldest error in the log. At power up / reset, the non-volatile error log will first be copied to the volatile error log.
The contents of the non-volatile error log will be corrupted if the Unit is interrupted (i.e. power-down / reset), while writing to the error log.
If an error in the non-volatile error log is detected at power up / reset, the Unit:
1. Will try to repair the contents of the error log.
2. If the log remains corrupted, the Error Log Storage Error bit in the Unit Status Word (CIO Word n+4, Bit 13) will be set. In this case, the error and the
flag can only be cleared through the FINS command ERROR LOG
CLEAR. The start-up procedure will be completed normally.
If, during normal operation, writing errors to the error log fails, the Unit will set
the Error Log Storage Error bit in the Unit Status Word (CIO Word n+4, Bit
13).
Note n = CIO 1500 + (25 x unit number).
Reading the Error Log
The error records in the error log can be read with the FINS command
ERROR LOG READ. The error log can be read from the PLC, via CX-Profibus, and via CX-Programmer.
Clearing the Error Log
Sending the FINS command ERROR LOG CLEAR to the Unit clears both the
non-volatile and the volatile error logs.
(See 5-2-5 ERROR LOG READ (2102) and 5-2-6 ERROR LOG CLEAR
(0203)).
214
Troubleshooting Using the Error Log
7-5-2
Section 7-5
Error Codes
The error codes are described in the following table. The detailed error code
will provide detailed information on an error.
Error
code
0001
Meaning
Detailed error code
1st byte
Watchdog timer error in CPU
Unit.
00
Correction
2nd byte
00
Replace the PLC CPU Unit.
Nonvolatile
Saved
0002
CPU Unit service monitor error.
Actual monitoring time ms (Hex)
Check the operating environment. Saved
000E
PLC Bus error.
00
00
Replace the CPU Unit.
0202
PROFIBUS parameter set
invalid.
00
80: Bus param- • Check the parameter settings.
eter error
• Re-download the configuration
if necessary.
00 ~ 7D: Slave
parameter error
---
020C
Protocol error.
00
00 ~ 7D: Failing Master
Address
Check the master devices on the
network, and make sure they are
all working correctly.
---
0211
Duplicate master address.
00
00 ~ 7D: Failing Master
Address
Check the master devices on the
network and ensure that they
have unique device addresses.
---
0219
Hardware error.
00
00
• Check the network wiring, and --make sure it is correct.
• Check for short-circuits.
• Check the bus timing set
through CX-Profibus.
• Check the HSA setting in CXProfibus, and make sure it is
set to the master device with
the highest address on the network.
• Check if any other faulty
devices are on the same network.
• Verify that the Highest Station
Address setting includes any
other master address on the
bus.
0601
CPU Bus Unit fatal error.
Error address in program.
Restart the CPU Unit. If the problem persists, replace the PROFIBUS Master Unit.
Saved
0602
CPU Bus Unit memory error.
01: Read error.
02: Write error.
Restart the CPU Unit. If the problem persists, replace the PROFIBUS Master Unit.
Saved
Note
02: Network
Parameter.
06: Error log.
Saved
1. The time information from the CPU Unit is used in the PROFIBUS Master
Unit.
2. An error record is not created in non-volatile memory when the error concerns an Error Log Write error.
215
Troubleshooting FINS Commands
7-6
Section 7-6
Troubleshooting FINS Commands
Any problems in FINS communications can be determined using the
response codes when the CMND(490) instruction has been used. The table
below lists response codes returned by the PROFIBUS Master Unit, after execution of FINS commands, the probable cause of errors, and recommended
remedies. Refer to the Communications Commands Reference Manual
(W342) for further information on response codes.
Main code
Subcode
Probable cause
Correction
00: No errors
00
---
---
02: Remote node
error
03
A FINS command was sent to read/write
specific slave data or to control a slave,
but the specified slave is not allocated to
the PROFIBUS -DP Master Unit.
Specify only addresses of allocated slaves in
the FINS command.
04: Service not
supported.
02
A FINS command, which is not supported
by the Unit/Model has been sent.
Check the command code and be sure the
command is supported by the Unit.
10: Command format error
01
The command is longer than the max. per- Check the command format of the command
missible length.
and set it correctly.
02
The command is shorter than min. permis- Check the command format of the command
sible length.
and set it correctly.
03
The first word is in an inaccessible area or Set a first word that is in an accessible area.
the bit number is not 00.
The bit number must be 00 for Ethernet Units.
0C
Parameters are set incorrectly in the command data.
• Non-specified code used.
• Invalid slave address (exceeds 125).
• Invalid code in program number
(exceeds 128)
• The number of read records is 0.
Check the command data and correct any
parameters that are incorrect.
22: Status error
(operating mode
disagreement)
08
A FINS command was sent to retrieve
slave data, but the Master Unit is in the
wrong mode to access the slave device.
Change Master mode to either CLEAR or
OPERATE, before re-sending the FINS command.
25: Unit Error
0F
An attempt to clear the Error Log failed.
Re-send the ERROR LOG CLEAR FINS command. If the problem persist, non-volatile memory may be corrupted. Replace the Unit.
11: Parameter
error
26: Environment
05
error (no such Unit)
0B
216
No need to sent the FINS command again,
A FINS command was sent to enable or
disable a slave device from the poll list, but unless a change to the slave state needs to be
the targeted slave is already in that mode. made.
Cannot clear the Error Log. The Error
cause still exists.
Remove the error cause and Re-send the
ERROR LOG CLEAR FINS command.
Maintenance
7-7
Section 7-7
Maintenance
This section describes the routine cleaning and inspection recommended as
regular maintenance.
7-7-1
Cleaning
Clean the PROFIBUS Master Unit regularly as described below in order to
keep it in an optimum operating condition.
• Regularly wipe the Unit with a dry, soft cloth.
• If a spot cannot be removed with a dry cloth, dampen the cloth with a neutral cleaner, wring out the cloth and wipe the Unit.
!Caution Never use volatile solvents such as paint thinner, benzine or chemical wipes.
These substances could damage the surface of the Unit.
7-7-2
Inspection
Be sure to inspect the system periodically to keep it in optimum operating condition. In general, inspect the system once or twice a year, but more frequently if the system is used in high temperature or high humidity
environments or dirty/dusty conditions.
Inspection Equipment
Prepare the following equipment before inspecting the system.
Required Equipment
Philips type screwdriver, multimeter, alcohol, and a clean cloth.
Optional Test Equipment
Depending on system conditions, a synchroscope, oscilloscope, thermometer
or hygrometer (to measure humidity) might be needed.
Inspection Procedure
Check the items in the following table and correct any that are below standard.
Item
Environmental
conditions
Installation
Standard
Equipment
0° C to 55° C
Thermometer
Ambient humidity
10% to 90%
Hygrometer
Dust/dirt accumulation
None
---
Are the units installed securely?
No looseness
---
Are the communications connectors fully inserted?
No looseness
---
Are the external wiring screws
tight?
No looseness
---
Ambient temperature
Are the connecting cables undam- No damage
aged?
---
217
Replacing the Unit
7-8
7-8-1
Section 7-8
Replacing the Unit
Replacement Precautions
The PROFIBUS Master Unit is a Network device. If the Unit is damaged, it will
effect the entire Network, so always ensure repairs are undertaken immediately. It is recommended to have a spare PROFIBUS Master Unit on hand so
that repairs may be conducted quickly.
Replacement Precautions
Observe the following precautions when replacing the Unit.
• Always turn OFF the power before replacing the Unit.
• Ensure that the new Unit is not faulty.
• If a poor connection is suspected of causing the malfunction, clean the
connectors using a clean, soft cloth and industrial-grade alcohol. Remove
any lint or threads left from the cloth, and remount the Unit.
• When returning a faulty Unit for repair, always attach a detailed fault
report to the Unit and return it to the nearest OMRON dealer.
Note
1. In order to prevent faulty operation be sure to turn off the power to all master and slave devices before replacing the Unit.
2. When replacing the Unit, do not reconnect it to the Network before carrying
out the procedures listed below.
7-8-2
Setting the Unit after Replacement
After replacing a PROFIBUS Master Unit - before re-applying the power - set
the unit number to the same unit number as the previous Unit.
After re-applying the power, the configuration settings, present in the previous
Unit, must also be transferred to the new Unit. There are two methods to
accomplish this.
• Start up CX-Profibus and reload the original project from the stored location, and download it to the new Unit.
• Use a Memory Card to store the all the Unit’s settings, before replacement, and restore it to the new Unit after replacement.
After configuring the new Unit, re-connect it to the network, and restart operation.
7-8-3
Addition/Replacement of Units on the PROFIBUS Network
The PROFIBUS network allows to connect and disconnect devices while in
operation.
Connecting /
Disconnecting Devices
Connecting / disconnecting any device in a PROFIBUS network is liable to
result in a temporary increase of the communication cycle time. An existing
slave device can only be replaced by the same type of device with the same
configuration. Any change to this configuration is likely to require a new configuration. Changing a device with a different device (type and/or configuration) will have a significant influence on the performance on the PROFIBUS
network.
Adding a Device
The addition of a new device to an existing configuration will require a new
configuration file to be downloaded in the PROFIBUS Master Unit, which will
temporarily disable all communication by this Unit on PROFIBUS.
218
Appendix A
Bus Parameters
A-1
Bus Parameters
The PROFIBUS Bus Parameters define both the baud rate and the bus timing settings, necessary to perform
the exchange of messages over PROFIBUS. The Bus Parameters settings must be determined for each and
every Master device on the bus, and usually depend on
• the number of I/O data bytes per slave device,
• the number of slave devices connected to the master,
• the number of other masters on the bus.
The Bus Parameter settings consist for one part of a number of settings, which are directly entered into the
PROFIBUS interface hardware registers. These settings implement the necessary timing to enable the transfer
of a single message between the PROFIBUS Master Unit and a slave device. The other part of the Bus Parameters must be calculated. These parameters implement the overall cyclic timing as well as the watchdog time to
monitor the communication.
The calculation is performed by the PROFIBUS Master Unit DTM. The software implements a formula to calculate the settings which will be downloaded to the PROFIBUS Master Unit. Most of the parameters have baud
rate dependent default values. Some of the parameters can be tuned by the user. However, this is not recommended, since the communication may not function correctly, due to incorrect settings or too small timing margins.
This appendix defines the parameters which are shown by the PROFIBUS Master Unit DTM, and provides the
formula used for the timing calculations.
A-2
Bus Parameter definitions
The figure below shows the PROFIBUS Master Unit DTM, Bus Parameter tab, in which the bus parameter settings can be made.
219
Appendix A
Bus Parameters
The table below defines the bus parameter settings options, shown in the figure. The Unit tBIT is defined as the
transmission time for one bit at the selected baud rate.
Item
Symbol
Description
Unit
Editable
by User
Baud rate
--
Defines the transmission rate on the PROFIBUS DP Network. The following baud rate values are defined by the
PROFIBUS DP standard:
• 9.6
• 19.2
• 45.45
• 93.75
• 187.5
• 500
• 1500 (default value)
• 3000
• 6000
• 12000
kBits/s
Yes
Optimize
--
-The Optimize setting defines whether or not selected
parameters can be changed by the user.
• By Standard
Forces the user to use the default (optimized) settings.
• By User
Makes selected fields editable.
Yes
Note 1. If the By User option is selected and changes
have been made, it is still possible to switch
between Optimize settings, without the changes
being lost.
2. If the By User option is selected and the baud
rate is changed, the parameters will be optimized to the new baud rate.
Slot Time
TSL
The maximum time a Master Unit must wait for a response tBIT
to a request message.
Yes
Min. Station Delay of
Responders
min T SDR
The minimum allowed time for a slave device before it will
generate a response to a request message.
tBIT
Yes
Max. Station Delay of
Responders
max TSDR
The maximum allowed time for a slave device to generate a tBIT
response to a request message.
Yes
Quiet Time
TQUI
The time a transmitting device must wait after the end of a
message frame, before enabling its receiver.
tBIT
No
Setup Time
TSET
The time between an event and the necessary reaction.
tBIT
No
Min. Slave Interval
--
The Minimum Slave Interval defines the poll cycle, i.e. the
minimum time between two consecutive Data_Exchange
Cycles to the same slave device. The Minimum Slave
Interval must be smaller than the Target Rotation Time.
ms
Yes
Calculated Minimum Slave Interval in milliseconds.
ms
No
Target Rotation Time
TTR
The anticipated time for one token cycle, including
allowances for high and low priority transactions, errors
and GAP maintenance. Do not set the value below the
calculated value, to avoid bus communication
interruptions.
tBIT
Yes
Max Retry Limit
--
Maximum number of request transmission retries by this
master if a device does not reply to a request.
--
Yes
220
Appendix A
Bus Parameters
Item
Symbol
Description
Highest Station Address
HSA
-The HSA defines the Highest Master device address on
the network, of which the Master device will request the
FDL status, when updating the active device list (See GAP
Update Factor).
Shows the device address of the master. If new slaves are
added to the network, this field shows the highest device
address.The Master will periodically check whether new
active devices have been added between address its own
address and the Highest Station Address. If any devices
are detected, GAP is updated.
Permissible values are in the range of 0 to 126.
Yes
GAP Update Factor
G
The GAP update factor defines the amount of updates of
the active devices (i.e. Master devices) list times during
one token rotation cycle.
To update the list, the Master device will transmit
FDL_Status_request messages to ascending device
addresses until it finds a next Master device, or until it
reaches the Highest Station Address (See HSA below).
The GAP Update Factor is fixed to 1.
--
No
Poll Timeout
--
The maximum time interval that this master device may
need for the execution of a master-master function.
ms
No
Data Control Time
--
The cycle time in which the master updates its Data
Transfer List, in which it keeps an overview of all slave
states. Data Control Time is based on the Watchdog time
TWD: Data Control Time = 7*TWD.
ms
No
Watchdog Control
TWD
The Watchdog Control Time defines the time for a slave
device to set its outputs to a fail-safe state, if during that
time no communication between the Master device and
that slave device was detected. The Watchdog is
automatically set for all configured slaves, based on the
value of TTR.
ms
Yes
A-3
Unit
Editable
by User
Determining the Bus Parameters
The bus parameters defined in the previous paragraph are used to configure the PROFIBUS DP hardware
interface and to calculate the cycle time for I/O data exchange as well as the watchdog value. Most of the
parameters, set in the Bus Parameter Tab are directly transferred to the interface hardware registers. The table
below, lists these parameters, along with their default value for the available baud rates. These values are also
the minimum values for each parameter at a given baud rate.
Baud rate
TQUI
TSET
TSL
[kBits/s]
[tBIT]
[tBIT]
[tBIT]
G
Retry Limit
Poll
Timeout
min TSDR
max TSDR
[ms]
[tBIT]
[tBIT]
9.6
0
1
100
1
1
10
11
60
19.2
0
1
100
1
1
10
11
60
45.45
0
95
640
1
1
10
11
400
93.75
0
1
100
1
1
10
11
60
187.5
0
1
100
1
1
10
11
60
500
0
1
200
1
1
10
11
100
1500
0
1
300
1
1
10
11
150
3000
3
4
400
1
2
10
11
250
6000
6
8
600
1
3
10
11
450
12000
9
43
1000
1
4
10
11
1600
221
Appendix A
Bus Parameters
The parameters to calculate are:
• Min. Slave Interval (tBIT)
• Target Rotation Time ( tBIT)
• Watchdog timeout (ms)
• Data Control Time (ms)
These four values depend on the number of slave devices allocated to the PROFIBUS Master Unit, the number
of I/O bytes each of the slave devices will exchange with the Master Unit, and how many other Master Units are
on the PROFIBUS network at the same time. Furthermore, the Unit will require additional time to process the
PROFIBUS I/O data and exchange this with the PLC CPU.
Based on this, the Min. Slave Interval value for one Master Unit can be calculated as follows:
Min. Slave Interval = A1 + (B1 * slave devices) + (C1 * bytes to transfer) +
(bits per µs)*((A2 * slave devices) + B2 * modules) + (C2 * Words to exchange)[1]
in which:
A1, B1, C1 are constants (in tBIT) determining the PROFIBUS DP cycle time on the bus,
A2, B2, C2 are constants (in µs) , determining the cycle time between the Unit and the PLC CPU,
slave devices are the devices allocated to this Master Unit only,
modules are the total number of I/O modules, selected for the slave devices.
TTR = ∑(Min. Slave IntervalMaster)
[2]
The total Target Rotation Time is calculated as the sum of all individual Min. Slave Interval values for each
Master Unit on the PROFIBUS network.
From the total Target Rotation Time the Watchdog time for each slave device is calculated as follows:
TWD = 3 * TTR / Baud rate
in which:
[3]
TTR is the total Target Rotation Time in tBIT,
Baud rate is the selected baud rate value.
The Watchdog Time value is in turn used to calculate the total Data Control Time:
[4]
Data Control Time = 7 * TWD
Based on measurements, the following values have been determined for the 6 factors in equation [1]:
Baud rate
A1
B1
C1
[kBits/s]
[tBIT]
[tBIT]
[tBIT]
[tBIT]
[ms]
9.6
414
280
11
1250
130
19.2
418
280
11
1250
65.1
45.45
1942
361
11
1250
27.5
93.75
450
280
11
1250
13.3
187.5
1390
310
10
1250
6.67
500
2183
310
10
1850
3.7
1500
4339
310
11
4800
3.2
3000
11578
410
5
9600
3.2
6000
23556
800
10
19200
3.2
12000
47112
1600
20
38400
3.2
A2: 65.1 µs, B2: 2 µs, C2: 0.5 µs
222
Minimum Min. Slave Interval
Appendix B
Slave Diagnostics Message
B-1
Slave Diagnostics Data Message
Every PROFIBUS DP slave device has to support the transfer of a-cyclic diagnostics message. The contents
of these messages allow a PROFIBUS Master Unit to assess the status of the slave device in every state of the
communication. The diagnostics message format is defined in the PROFIBUS standard.
The slave diagnostics message consists of at least 6 mandatory bytes. If supported, the slave can send additional extended diagnostics bytes in the same message. The extended diagnostics format is defined in the
PROFIBUS standard. The extended bytes are usually only included in the diagnostics message if an event has
occurred, which results in extended diagnostics.
In some cases the PROFIBUS Master Unit will itself form a slave Diagnostics message. This is the case if the
slave device is not responding to any request sent by the Master Unit. The format of the message will be the
same as a message sent by a slave device, but the contents has been sent by the Master Unit.
The last received diagnostics message for each slave device allocated to the PROFIBUS Master Unit can at
any time be retrieved from the Unit through the MEMORY AREA READ FINS command.
B-2
MEMORY AREA READ (0101)
In order to retrieve the last received slave diagnostics message from the PROFIBUS Master Unit, the PLC
CMND(490) can be used to transmit a MEMORY AREA READ FINS command to the PROFIBUS Master Unit.
The MEMORY AREA READ command format is given below.
Command Format
01
01
Command
code
81
FF
00
No. of items
(binary)
Slave station address
Data specifier
Response format
01
01
Command
code
End code
Diagnostics data
(for number of items)
Parameters
• Data specifier code (command)
Defines the data to be retrieved from the Unit. Always set to 81 FF 00 (Hex).
• Slave device address (command)
Defines the slave device network address. Set to 00 ~ 7D (Hex).
• Number of items to read (command)
Defines the number of bytes to read. Set to 1 ~ F4 (Hex).
The diagnostics message is returned from the slave device as a sequence of bytes. When transferred to the
PLC memory, the format is converted to words. The format is shown in the figure below. The location in the
PLC memory, designated as D is the Destination location as specified in the CMND (490) instruction.
223
Appendix B
Slave Diagnostics Message
D
Byte 1
Byte 2
D+1
Byte 3
Byte 4
D+2
Byte 5
Byte 6
D+3
Byte 7
Byte 8
D+4
Byte 9 Byte 10
The first 6 bytes or 3 words - Word D ~ Word D+2 - are mandatory bytes, which will always be sent by the
slave device. Any additional, i.e. extended diagnostics bytes start at Word D+3. The contents of the first six
bytes is defined by the PROFIBUS standard. The contents of the extended diagnostics information is slave
device dependent, but the format is defined in the PROFIBUS standard.
The first 6 bytes and the Extended diagnostics format are explained below.
B-3
Standard Diagnostics Data Bytes
Slave Diagnostics Byte 1
A layout of Byte 1 is shown below. This byte is mapped to the high-byte of Word D.
7
6
5
4
3
2
1
0
Byte 1
Diag.Station_Non_Existent
Diag.Station_Not_Ready
Diag.Cfg_Fault
Diag.Ext_Diag
Diag.Not_Supported
Diag.Invalid_Slave_Response
Diag.Prm_Fault
Diag.Master_Lock
Bit
00
Name
Diag.Station_Non_Existent
01
02
Diag.Station_Not_Ready
Diag.Cfg_Fault
03
Diag.Ext_Diag
04
Diag.Not_Supported
224
Description
This bit is set by the Master Unit if the slave does not respond to any of the
request messages sent by the master. If this bit is set the diagnostic bits contains
the state of the last diagnostic message or the initial value. The slave device sets
this bit to zero in case of a correct response.
This bit indicates that the slave device is not yet ready for data transfer.
Set by the slave device, this bit indicates that the last received configuration data
from the Master Unit are rejected. The configuration data in the slave device differ from the configuration sent by the Master Unit.
This bit indicates that the diagnostics message returned by the slave device contains extended diagnostics, i.e. it contains more than the mandatory 6 bytes.
In case the Master Unit sent a message to the slave device, which is not supported by that device, this bit will be set by the slave device.
Appendix B
Slave Diagnostics Message
Bit
05
Name
Diag.Invalid_Slave_Response
06
Diag.Prm_Fault
07
Diag.Master_Lock
Description
This bit is set by the Master Unit if the slave has returned an invalid response to a
Master request message. The slave device will set this bit to 0.
Set by the slave device, this bit indicates that the last received parameter data
from the Master Unit have been rejected. The parameter data in the slave device
differ from the parameter sent by the Master Unit.
This bit indicates that the slave device has been parameterized by another master. The bit is set by the Master Unit, if the address in byte 4 differs from 255 and
from the Master Unit’s own address. The slave device sets this bit to zero.
Slave Diagnostics Byte 2
A layout of Byte 2 is shown below. This byte is mapped to the low-byte of Word D.
7
6
5
4
3
2
1
0
Byte 2
Diag.Prm_Req
Diag.Stat_Diag
Reserved
Diag.WD_On
Diag.Freeze_Mode
Diag.Sync_Mode
Diag.Deactivated
Bit
00
Name
Diag.Prm_Req
01
Diag.Stat_Diag
02
03
Reserved
Diag.WD_On
04
Diag.Freeze_Mode
05
Diag.Sync_Mode
06
07
Reserved
Diag.Deactivated
Description
This bit is set by the slave device and indicates that it needs to be (re-)aparameterized. The slave device is not in Data_Exchange with the Master Unit. The bit
remains on as long as it has not been parameterized successfully.
This bit indicates static diagnostics at the slave device. The Master Unit will
repeatedly request diagnostics data. As long as this bit is set, Data_Exchange
with the Master Unit is not being performed.
This bit is reserved and always set to 1 by the slave device.
If the watchdog has been enabled at the slave device (through the appropriate
setting in the parameterization message) this bit will be set.
If the slave device has been set to the Freeze mode, using the global command,
this bit will be set to on. The bit will be set to off, if an Unfreeze command has
been received.
If the slave device has been set to the Sync mode, using the global command,
this bit will be set to on. The bit will be set to off, if an Unsync command has been
received.
This bit is reserved.
This bit is set by the Master Unit, indicating that the slave device has been disabled (i.e. using the STOP FINS command). The slave device is allocated to the
Master Unit, but removed from cyclic processing.
Slave Diagnostics Byte 3
A layout of Byte 2 is shown below. This byte is mapped to the high-byte of Word D + 1.
7
6
5
4
3
2
1
0
Byte 3
Diag.Ext_Diag_Overflow
225
Appendix B
Slave Diagnostics Message
Bit
00
~
06
07
Name
Description
These bits are reserved and always set to 0 by the slave device.
Reserved
Diag.Ext_Diag_Overflow
If set, this bit indicates that there exists more diagnostic information than specified in Ext_Diag_Data. This bit will - for example - be set if the slave device has
more diagnostics available than it can enter in its send buffer. This bit will also be
set if the Master Unit receives more diagnostic information than it can enter in its
diagnostic buffer.
Slave Diagnostics Byte 4
Slave Diagnostics Byte 4 is mapped to the low byte of Word D+1. This byte contains the PROFIBUS address
of the Master Unit, which parameterized the slave. If the slave is not parameterized correctly, the byte contains
FF (Hex) or 255 (Decimal).
Slave Diagnostics Bytes 5 to 6
Slave Diagnostics Bytes 5 and 6 are mapped to Word D+2. They contain the PROFIBUS Ident Number of the
slave device. The Ident number uniquely identifies the type of device. The Ident Number is a 16-bit code
issued by the PROFIBUS Organization. For example, the Ident number of the CJ1W-PRT21 PROFIBUS DP
slave is 0602 (Hex).
B-4
Extended Diagnostics Data Bytes
The afore mentioned 6 diagnostics bytes are a mandatory minimum, which is supported by every PROFIBUS
DP slave device. Depending on the device however, it may also support extended diagnostics information,
which is coded into the bytes following the first 6 mandatory bytes. The number of extended bytes depends on
the coding and the events that have occurred in the slave device. Normally, they will not be added to the standard diagnostics message, i.e. the first 6 mandatory bytes, if no event occurred.
There are three types of extended diagnostics information:
• Device related diagnostics
• Module related diagnostics
• Channel related diagnostics
The Module related diagnostics, are usually followed by the Channel related diagnostics. Both the Device
related diagnostics and the Module / Channel related diagnostics can occur in one message.
Device Related Diagnostics
The Device related diagnostics data block consist of a header byte followed by one or more device dependent
diagnostics data bytes. The header byte indicates the type of diagnostics data and the total length of the data
block. The header byte layout is shown below.
7
0
6
0
5
4
3
2
1
0
Block Length
226
Appendix B
Slave Diagnostics Message
Bit
00
~
05
06
~
07
Name
Description
These bits contain the length of the Device related diagnostics data block, including the header byte. The Device diagnostics will follow this header byte.
Maximum length of the block, including the header is 63 bytes.
Interpretation of the diagnostics bytes in this block is device dependent.
Fixed to 00.
The combination of bit 6 and 7 indicate the type of diagnostics, i.e. 00 indicates
Device related diagnostics data.
Block length
Reserved
Note The Device related diagnostics as defined above is according to the PROFIBUS-DP standard. With the
release of the PROFIBUS DP-V1 standard, the Device related diagnostics contents has been re-defined
to accommodate diagnostics from slave devices supporting PROFIBUS DP-V1.
Module Related Diagnostics
The Module or Identifier related diagnostics data block consist of a header byte followed by one or more bytes
containing flags, which indicate if there is diagnostics pending related to the I/O configuration modules. Each
flag is related to the corresponding I/O module, defined during configuration. Non-used flags are always set to
0.
The figure below shows the header byte, and one module diagnostics byte. Depending on the number of I/O
modules configured, there may be more bytes.
7
Header Byte 0
6
1
5
4
3
2
1
0
Block Length
7
6
5
4
3
2
1
0
Module Diagnostics Byte
Module 0 Diagnostics
Module 1 Diagnostics
Module 2 Diagnostics
Module 3 Diagnostics
Module 4 Diagnostics
Module 5 Diagnostics
Module 6 Diagnostics
Module 7 Diagnostics
Header byte
Bit
00
~
05
06
~
07
Name
Block length
Reserved
Description
These bits contain the length of the Module related diagnostics data block,
including the header byte. The Module diagnostics flags will follow this header
byte. Maximum length of the block, including the header is 63 bytes.
Fixed to 01.
The combination of bit 6 and 7 indicate the type of diagnostics, i.e. 01 indicates
Module related diagnostics data.
227
Appendix B
Slave Diagnostics Message
Module Diagnostics byte
Bit
00
Name
Module 0 Diagnostics
01
Module 1 Diagnostics
02
Module 2 Diagnostics
03
Module 3 Diagnostics
04
Module 4 Diagnostics
05
Module 5 Diagnostics
06
Module 6 Diagnostics
07
Module 7 Diagnostics
Description
When set, this bit indicates that there is Diagnostics information pending related
to configuration module 0, i.e. the first configuration module.
When set, this bit indicates that there is Diagnostics information pending related
to configuration module 1.
When set, this bit indicates that there is Diagnostics information pending related
to configuration module 2.
When set, this bit indicates that there is Diagnostics information pending related
to configuration module 3.
When set, this bit indicates that there is Diagnostics information pending related
to configuration module 4.
When set, this bit indicates that there is Diagnostics information pending related
to configuration module 5.
When set, this bit indicates that there is Diagnostics information pending related
to configuration module 6.
When set, this bit indicates that there is Diagnostics information pending related
to configuration module 7.
Consecutive bytes contain the diagnostics flags for Module 8 through 15, 16 through 23, etc.
The Module related diagnostics information is usually followed by the Channel related diagnostics, which contain the actual diagnostics data per module.
Channel Related Diagnostics
Channel related diagnostics contain diagnostics information related to a specific channel in a configured I/O
module, e.g. over peak current detected on current input channel 2, module 0.
The Channel related diagnostics information entry in the diagnostics message, always consists of three bytes,
which are outlined below. From these bytes the actual event can be deducted.
7
Module Identifier byte 1
6
0
5
4
3
2
1
0
Module number
7
6
5
4
3
2
1
0
Channel Identifier byte
Channel number
I/O type
7
6
5
4
3
2
1
0
Error Identifier byte
Error type number
Channel size type
Module Identifier byte
Bit
00
~
05
06
~
07
228
Name
Module number
Description
These bits contain the number of the configuration module, to which the channel,
reporting diagnostics belongs. The module number ranges from 0 to 63.
Reserved
Fixed to 10.
The combination of bit 6 and 7 indicate the type of diagnostics, i.e. 10 indicates
Channel related diagnostics data.
Slave Diagnostics Message
Appendix B
Channel Identifier byte
Bit
00
~
05
06
~
07
Name
Channel number
Description
These bits contain the number of the channel, which reports the diagnostics. The
channel number ranges from 0 to 63.
I/O type
Bit 6 and 7 indicate the type of I/O channel, from which the diagnostics data is
sent.
• 00: Reserved
• 01: Input
• 10: Output
• 11: Input/Output
Error Identifier byte
Bit
00
~
04
Name
Error number
05
~
07
Channel size type
Description
These bits contain the number of the error which occurred at the channel. The
error number ranges from 0 to 31, and can have the following meaning:
• 0: Reserved
• 1: Short circuit
• 2: Under voltage
• 3: Over voltage
• 4: Overload
• 5: Over temperature
• 6: Line break
• 7: Upper limit value exceeded
• 8: Lower limit value exceeded
• 9: Error
• 10 ~ 15: Reserved
• 16 ~ 31: Manufacturer specific
Bit 5, 6 and 7 indicate the size of the channel, from which the diagnostics data is
sent.
• 000: Reserved
• 001: Bit
• 010: 2 Bit
• 011: 4 Bit
• 100: Byte
• 101: Word
• 110: 2 Words
• 111: Reserved
229
Appendix B
Slave Diagnostics Message
Example of Extended Diagnostics
Below an example of Extended diagnostics data is given, using the definitions above. The 6 mandatory bytes
preceding them are not shown.
7
0
6
0
5
0
4
0
3
0
2
1
1
0
0
0 Header byte
Device specific
Device related diagnostics:
Device specific contents
diagnostics field
of length 3
0
1
0
0
0
1
1 Header byte
0
Module 1 has diagnostics
1
Module related diagnostics:
1
Channel related diagnostics:
Channel related diagnostics:
Module 14 has diagnostics
1
0
0
0
0
0
0
1 Module 1
0
1
0
0
0
1
0
0 Channel 4 (Input)
0
1
1
0
0
1
0
0 Overload, bit oriented
1
0
0
0
1
1
1
0 Module 14
0
0
0
0
1
0
0
0 Channel 8
1
0
0
0
0
1
1
1 High Limit exceeded, byte oriented
The figure above shows the extended diagnostics of a slave device, which contains:
• Device related diagnostics:
One header byte and three device specific diagnostics bytes are shown in this example. The contents of
the diagnostics is device specific.
• Module related diagnostics:
One header byte and three module diagnostics bytes. The first of three bytes indicates pending diagnostics in module1, the next byte indicates pending diagnostics in module14.
• Channel related diagnostics:
Two channel related diagnostics entries are shown: One for module 1 and one for module 14. In module 1,
Input channel 4, has detected an overload. In module 14, channel 8, has detected an high-limit exceeded
event.
B-5
PROFIBUS DP-V1 Error codes
The Error codes returned by a PROFIBUS DP-V1 slave device are defined in the PROFIBUS DP-V1 Extension
to the PROFIBUS standard. This section lists the Error codes, which can be returned as a result of a PROFIBUS DP-V1 MSAC1 services. From these codes, the user can determine the cause of the failure.
The figure below shows the two of the three Error code bytes, returned by a PROFIBUS DP-V1 slave device, in
case an MSAC1 service resulted in an error. The third byte, Error code 2, which is not shown below will always
contain user specific error codes.
7
6
5
4
3
2
1
0
Error decode byte
Error decode
7
6
5
4
3
2
1
0
Error code 1 byte
Error code
Error class
230
Appendix B
Slave Diagnostics Message
Error decode byte
Bit
00
~
07
Name
Error decode
Description
The code determines the protocol type of the slave which returned the error
code. Since this error scheme can also be used in network applications containing protocol converters (i.e. gateways), non-PROFIBUS protocols are also
defined in this list.
• 0 to 127: Reserved
• 128: PROFIBUS DP-V1
• 129 to 253: Reserved
• 254: PROFIBUS FMS
• 255: HART®
In case the Error decode byte is 128, i.e. PROFIBUS DP-V1, the Error code 1 byte can have the possible values defined in the table below.
Error code 1 byte
0~9
10
Error class code
Reserved
Application
11
Access
12
Resource
13~15
User specific
Error code
Description
-•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
0: Read error
1: Write error
2: Module failure
3 to 7: Reserved
8: Version conflict
9: Feature not supported
10 to 15: User specific
0: Invalid index
1: Write length error
2: Invalid slot
3: Type conflict
4: Invalid area
5: State conflict
6: Access denied
7: Invalid range
8: Invalid parameter
9: Invalid type
10 to 15: User specific
0: Read constrain conflict
1: Write constrain conflict
2: Resource busy
3: Resource unavailable
4 to 7: Reserved
8 to 15: User specific
Error codes related to the application, i.e. the
slave device it self or I/O modules connected to
this device.
Error codes related to accessing the requested
data area in the slave device or I/O modules
connected to the slave device.
Error codes related to resources inside the
slave device which are required to process the
requested data, e.g. functions required to
implement a requested action.
--
Error code 2 byte
This error code will always contain user specific error codes. If necessary, refer to the slave device’s documentation for decoding the returned byte.
231
Appendix C
I/O Data Conversions
C-1
I/O Data type definitions
Standard PROFIBUS DP defines two types of I/O data.
• 8-bit bytes sized data.
• 16-bit word sized data.
The standard for PROFIBUS extension, also referred to as PROFIBUS DP-V1, defines the following additional
data types:
• 8-bit byte signed / unsigned Integer data.
• 16-bit word signed / unsigned Integer data.
• 32-bit double word signed / unsigned Integer data.
• 32-bit single precision floating point (IEEE754 format).
• ASCII Text strings of indeterminate length (in 8-bit bytes).
• 7 byte Date format.
• 6 byte Time of Day format.
• 6 byte Time Difference format.
The CS1/CJ1-series PLC defines similar data types, which however differ in size and/or storage format in the
PLC memory. Since the PROFIBUS Master Units provides an interface between a PROFIBUS network and the
CS1/CJ1-series PLC, the Unit will provide the necessary conversions to ensure that the I/O data on the
PROFIBUS network is transferred to the PLC memory in the correct format. This Appendix explains the conversions in detail.
C-2
Integer Data Conversions
8-bit Byte Data
The CS1/CJ1-series PLC memory layout is word oriented, and does not support storage of single 8-bit byte
data types. The PROFIBUS Master will therefore convert a stream consisting of one or more bytes of data into
words. The figure below shows the conversion in graphic format.
PLC Data area
Bit 15
Word 0
PROFIBUS
Bit 00
Byte 2
Byte 1
Bit 07
Bit 00
Byte 1
Byte 2
Word m
Byte n
Byte
sequence
Byte n-1
Byte n-1
Byte n
Note m = (n-1)/2, rounded to the next lowest integer.
A sequence of bytes transmitted over the PROFIBUS network is copied to the PLC memory in the following
procedure.
• The first two bytes are stored in the lowest word of the destination data block in PLC memory word. Every
consecutive two bytes are stored in the next higher words.
233
Appendix C
I/O Data Conversions
• Odd byte numbers are copied to the Least Significant byte of a PLC memory word.
• Even byte numbers are copied to the Most Significant Byte of a PLC memory word.
• If the total number of bytes is an odd number, the Most Significant Byte of the last word is filled with 0.
16-bit Word Data
16-bit word data is transferred over the PROFIBUS network with the Most Significant Byte first. The PROFIBUS Master Unit will ensure that a word transmitted or received over PROFIBUS is mapped to one word in the
PLC memory area. The figure below shows the conversion in graphic format.
PLC Data area
PROFIBUS
Bit 07
Bit 00
Byte 1 (MSB)
Byte 2 (LSB)
Bit 15
Word 0
Word 0
Bit 00
Byte 1 (MSB)
Byte 2 (LSB)
32-bit Double Word Data
32-bit double word data is transferred over PROFIBUS with the Most Significant Byte first. The PROFIBUS
Master Unit will ensure that a double word transmitted or received over PROFIBUS is mapped on to CS1/CJ1series double word format in the PLC memory area. The figure below shows the conversion in graphic format.
PLC Data area
PROFIBUS
Bit 07
Bit 15
Bit 00
Bit 00
Byte 1 (MSB)
Word 0
Byte 3
Byte 4 (LSB)
Byte 2
Word 1
Byte 1 (MSB)
Byte 2
Byte 3
Double Word 0
Byte 4 (LSB)
C-3
Floating Point Data Conversions
PROFIBUS defines the IEEE 754 format single precision floating point data type. It is transferred over the network as a 4 byte data, Most Significant Byte first. In the PLC memory area the same data type and size is
defined, but data of this type is stored with the Most Significant bytes on the higher memory location and the
Least Significant Bytes on the lower memory location. The figure below shows the conversion in graphic format.
PLC Data area
PROFIBUS
Bit 07
Bit 15
Bit 00
Word 0
Byte 3
Byte 4 (LSB)
Word 1
Byte 1 (MSB)
Byte 2
Bit 00
Byte 1 (MSB)
Byte 2
Byte 3
Byte 4 (LSB)
234
Single precision
floating point
(IEEE754)
Appendix C
I/O Data Conversions
C-4
Text String Data Conversion
PROFIBUS defines ASCII text strings data type. It is transferred over the network as a string of characters. In
order to maintain a readable string in the PLC memory, the data is converted to fit the odd character in the
Most Significant Byte of the words, and the even characters in the Least Significant Byte of the words. The
string is stored on ascending word addresses in PLC memory. The figure below illustrates the conversion.
PLC Data area
PROFIBUS
Bit 07
Bit 00
Char 1
Bit 15
Word 0
Char 2
Bit 00
Char 1
ASCII Text string
Char 2
Char n-1
Char n
Word m
Char n-1
Char n
Note m = (n-1)/2, rounded to the next lowest integer.
If the number of text characters is even, all bytes will fit in the words, but one additional word will be set to
0000. If the number of bytes is odd, the last byte of the sequence will be mapped to the high-byte of the last
word. The low-byte of the last word will be padded with a 0.
C-5
Date / Clock Time Data Conversions
Date, Time and Time Difference data types as defined in PROFIBUS are not supported by the CS1/CJ1-series
PLC. To ensure that workable data is transferred from PROFIBUS to the PLC memory, these data types are
treated as 16-bit word data. The figure below illustrates the conversion.
PLC Data area
PROFIBUS
Bit 07
Bit 15
Bit 00
Word 0
Byte 1 (MSB)
Byte 2 (LSB)
Word 1
Byte 3
Byte 4
Word 2
Byte 5
Byte 6
Word 3
Byte 7
00
Bit 00
Byte 1 (MSB)
Time [ms]
Byte 2 (LSB)
Byte 3
Time [min]
Byte 4
Time [hrs]
Byte 5
Date [day of week/month]
Byte 6
Date [month]
Byte 7
Date [year]
Date and Time information is coded as defined by the PROFIBUS DP standard. The figure and the table below
define the format as it is stored in the PLC memory.
Word 0
15 14 13 12 11 10 9 8 7 6
Time [ms]
Word 1
Time [min]
Word 2 Day [wk]
Day [month]
Word 3
Year
SU
5
4
3
2
1
0
Time [hrs]
Month
Note The grey areas in the figure above denote reserved bits, which are always set to 0.
235
Appendix C
I/O Data Conversions
Word
Bits
0
00 ~ 15
Type
1
00 ~ 04
Hours
0 ~ 23
07
Daylight saving time indication
0: Standard time
1: Daylight saving time
Minutes
0 ~ 59
Month of the year
0 ~ 12
Time
08 ~ 13
2
3
236
00 ~ 05
Date
Description
Milliseconds
Range
0 ~ 59999
08 ~ 12
Day of the month
0 ~ 31
13 ~ 15
Day of the week
0~7
08 ~ 14
Year
0 ~ 99
Appendix D
Configurator Error and Warning Messages
D-1
Warning Messages
The table below lists the Warning messages which can be displayed by the PROFIBUS Master Unit DTM.
These messages usually indicate that the user is about to perform an action, which will have significant impact,
or an action which is only partly supported by the Unit. The user is given a chance to abort the function if the
impact is undesirable.
Number
Message
Description
When occurring
00
Change the PLC to PROGRAM
mode?
In order to start downloading a configuration, the At the start of downloadPLC must be set to PROGRAM mode, to prevent ing, in case the PLC is in
RUN/MONITOR mode.
I/O data being exchanged with the Unit, during
the change of the configuration.
• Yes Change state and download configuration.
• No
Stop download.
01
DPV1 Slave/slaves is assigned to
master. DPV1 slaves are not fully
supported.
The PROFIBUS Master Unit supports only basic At the start of downloadDPV0 functions. This means that the DPV1 slave ing, in case one of the
can still be operated, but the DPV1 functionality slaves is a DPV1 slave.
is not possible:
• OK Close message box.
02
Return the PLC to [mode] mode?
After download with PLC previously in RUN or
MONITOR the PLC can be returned to RUN or
MONITOR mode
• Yes
Change state.
• No
PLC remains in PROGRAM mode.
• Cancel PLC remains in PROGRAM mode.
After completing the
download.
03
PROFIBUS I/O Data "area overlapping" and/or "exceeding memory range" Save anyway?
One or more of the I/O Data mappings is incorrect. Either the I/O data or a part of the I/O data
is mapped beyond an existing memory area, or
two or more mappings are overlapping in memory.
• Yes
Save settings.
• No
Do not save settings.
• Cancel Do not save settings.
Closing the Configuration User Interface with
invalid configuration or
saving invalid settings
04
Settings have been changed.
Would you like to save?
One or more settings have been changed, but
not yet saved.
• Yes
Save data and close DTM.
• No
Do not save data and close DTM.
• Cancel Do not close the DTM.
Closing the Configuration User Interface without saving the changes.
05
Settings have been changed.
Would you like to leave without
saving?
Closing the GUI without saving the configuration. Closing the Configuration User Interface with• Yes
Do not save data and close DTM.
out saving the changes.
• No
Do not save data and do not close
DTM.
06
Compressing will re-allocate slave Each of the slave I/O data mapping areas can be
compressed, by pressing the Compress button.
configuration in [memory area].
This will result in the DTM filling up all the gaps in
Continue?
the mapping, by moving I/O data from higher
addresses closer to the start address of the mapNote [Memory Area] = Input ping area.
Area 1/ Input Area 2/ Out- • Yes
Compress memory area.
put Area 1/ Output Area 2
• No
Do nothing.
When pressing the
Compress button in the
Slave Area tab, I/O Allocation.
237
Appendix D
Configurator Error and Warning Messages
Number
Message
Description
When occurring
07
[IO area] must be empty. Move all “Not used” item in the start address combo box in When selecting the “Not
output/input allocation tabs can only be selected Used” item from the
modules into other area
if there are no I/O module mapped in that area.
memory area box.
Note [IO area] = output area1/
•
OK
Close
message
box.
Move
modules
output area2/ input area1/
to other I/O area first.
input area2
08
Slave_User_data part of the
PROFIBUS slave parameter set
will be ignored. See slave [no][name]
Note
Slave_User_data part of the slave parameter set
will not be used. The additional user parameters
in the slave parameter set are not supported by
the PROFIBUS Master Unit.
• OK
[no] = slave address
[name] = slave DTM name
When adding a slave
DTM to the network,
which defines additional
user parameters.
Close message box
09
Auto addressing will reallocate
When selecting the Auto-Addressing check box
slave I/O mapping. Would you like in the Master Setup tab, all slave I/O data mapto proceed?
pings will be compressed in each of the I/O mappings. The slave I/O mapping will be changed.
• Yes Update slave I/O module mapping and
check checkbox.
• No
Do not update slave I/O module map
ping and uncheck checkbox.
When checking the
Auto-Addressing checkbox on the Master Setup
tab.
10
Settings cannot be uploaded, unit The settings uploaded were not used by stack
must be restarted. Would you like • Yes: Restart the unit and upload the settings.
to continue?
• No: Do nothing.
When attempting to
upload settings.
11
Upload is not supported.
When attempting to
upload settings.
12
After locking address it cannot be When sending Set Device Station Address com- When ‘Lock’ check box
in the Set Device Station
changed any more. Would you like mand with 'Lock' check box is checked, the
to proceed?
address will be stored permanently in the Slave Address GUI is checked.
device and can not be changed anymore.
• Yes: Lock option is checked.
• No: Lock option is unchecked.
13
DPV1 alarms are not supported
Alarm settings set by the Slave DTM are not sup- Downloading settings
by the Master Unit and will be dis- ported and will be reset.
and one of the alarm bits
abled.
are set in Slave Parame• OK: Close message box.
ter Set.
14
Publisher functionality is not sup- Publisher functionality set by the Slave DTM is
ported by the Master Unit and will not supported and will be reset.
be disabled.
• OK: Close message box.
Downloading settings
and the Publisher bit is
set in Slave Parameter
Set.
15
Isochronous mode is not supIsochronous mode set by the Slave DTM is not
ported by the Master Unit and will supported and will be reset.
be disabled.
• OK: Close message box.
Downloading settings
and the Isochronous
mode bit is set in Slave
Parameter Set.
238
Upload is not supported
• OK: Close message box.
Appendix D
Configurator Error and Warning Messages
D-2
Error Messages - Configuration
The table below lists the Error messages which can be displayed by the PROFIBUS Master Unit DTM in case
there are configuration errors. Usually, these are detected either when entering, or up on download. The table
suggests corrections to the problems in the right most column.
Number
Message
00
Total I/O area size exceeds maximum
Description
01
PROFIBUS I/O Data area overlap- Input/Output areas are overlapping
ping
within the current configuration.
02
PROFIBUS I/O Data exceeds
memory range
Input / Output area exceeds memory Change the configuration to be
range (combination of start address within the memory area and retry
and length).
download.
03
Slaves should have unique
addresses
Unique bus addresses must be
assigned for each slave.
04
DTM cannot be added to the net- The slave DTM cannot be conwork, it is not a PROFIBUS device nected, e.g. if adding HART device
DTM.
DTM
Avoid using non-PROFIBUS DP
DTMs.
05
Max. number of slaves configured. DTM can not be added, since the
New slave cannot be added
master has already the maximum
number of slaves (125) assigned.
Do not add any more DTMs. If more
are still needed, a second PROFIBUS Master Unit on the same PLC
system may be solution.
06
Slave address overlap detected.
New address assigned: [new
address]
Changing the address of an existing
slave results in an address overlap.
07
Invalid data set received from a
slave DTM. Slave parameter
changes ignored
An internal error has occurred preAdd a new slave DTM into the netventing the master DTM to obtain the work (or change the modules of the
slave's parameter set.
existing slave) with correct slave
parameter set.
08
Set Parameters failed. Slave cannot be configured
An internal error has occurred preventing the master DTM from setting/changing the slave's bus
address.
09
No slaves assigned. Download
aborted
No slaves have been assigned to the Retry download when at least one
slave has been assigned.
master. At least one slave must be
assigned.
10
Slave(s) has no modules. Download aborted
A slave (or slaves) has no modules.
11
Configured EM bank (banks) is
not available in the connected
PLC.Download aborted
The configured EM bank (banks) are Change the configuration to use only
not available in the connected PLC. memory areas available in the PLC
and retry download.
12
Connected unit is busy. Download Unit is busy with parameter storage.
aborted
13
Slave configuration too big
Reduce the configuration.
The total number of configured
parameter bytes and configuration
bytes does not fit into the FINS message for downloading.
14
Maximum number of modules
exceeded
The total number of configured I/O
modules over all allocated slave
devices can not exceed 4000.
Do not add any more modules to the
configuration.
15
PROFIBUS Master is not in correct mode. Please set the PROFIBUS Master in one of the following
modes: STOP, CLEAR or OPERATE.
The Set Device Station Address
command can not be executed
because the PROFIBUS Master is
not in correct mode, i.e. the Master
Unit is OFFLINE.
Set the PROFIBUS Master into one
of the following modes: STOP,
CLEAR or OPERATE.
The I/O configuration exceeds the
maximum limit of 7168 (or 7k)
words).
Correction
Change configuration to reduce the
amount of I/O data to 7168 words
maximum or less.
Check the Input/Output areas and
make sure they are not overlapping.
Retry download.
Change the addresses of the slaves
and ensure no duplicates are
present. Retry download.
Automatically recovers.
Non recoverable. Master DTM tries
to assign a new bus address to the
slave DTM, but the slave DTM’s
database is locked.
Retry download when modules have
been added to the slave(s) having no
modules.
Retry download when parameter
storage has finished.
239
Appendix D
Configurator Error and Warning Messages
Number
Message
Description
Correction
16
• Check target Slave device on the
Master Unit indicated failure of Set When sending Set Device Station
PROFIBUS network.
Device Station Address.
Address command, one of the following problems occurred:
• Check specified Slave address.
• The slave has deactivated this
• Check Slave timeout parameter
service.
• The slave has not responded to
the request.
• The slave does not have sufficient
memory space for the request
data.
17
'New address' and/or 'Ident number (hex)' are/is empty.
No data is entered in the New
Address and Ident Number fields.
18
Slave/Master DTM does not
accept the specified address.
The DTM has not accepted the new
address setting. Possible cause is
that the slave DTM data set has
been locked for parameter changes.
19
Master Unit version and DTM ver- The selected DTM is not suitable to Please use the DTM as specified in
sion do not match. Please select configure the connected PROFIBUS the error message.
Master.
DTM that can be used with the
connected device [xxxx].
D-3
Fill-in both the 'New address' and the
'Ident number (hex)' fields.
Error Messages - Communication
The table below lists the Error messages related to CX-Server communication between the PROFIBUS Master
Unit DTM and the PLC.
Number
50
240
Message
Communication Failure with Unit
Description
Correction
The communication between the PC • Ensure there are no problems
with the connection between the
and the Unit on the PLC could not be
Personal Computer and the PLC.
achieved.
• Ensure the Master Unit has been
correctly mounted - Refer to section 2-2 Installing the CS1/CJ1WPRM21 Units for detailed information.
• Make sure the Device settings are
correct.
• Perform one of the following successfully to confirm the problem
has been solved:
* Download configuration
* Communication Test in Device
Settings tab
* Update monitoring data (Slave
Diagnostics, clearing error log).
Appendix D
Configurator Error and Warning Messages
Number
Message
Description
Correction
51
Communication Failure with PLC
The communication between the PC • Ensure there are no problems
and the PLC could not be achieved.
with the connection between the
Personal Computer and the PLC.
• Make sure the Device Settings
are correct.
• When problem has been
removed, disconnect and re-connect. Perform one of the following
successfully to confirm the problem has been solved:
* Update monitoring data (Slave
Diagnostics, clearing error log).
* Changing the master state
52
CX-Server could not be configured
Configuration of CX-Server failed.
• Make sure the settings within the
Device Set-up tab are correct.
Select the Test Button to check
this.
• Make sure the Personal Computer
COM port selected within the
Device Set-up Configuration is not
in use by another application. If it
is close the connection from
within the other application.
• Restart CX-PROFIBUS.
• Restart Personal Computer to
ensure COM port is released.
• Ensure the correct version of CXServer is installed on the Personal
Computer. Refer to the Master
Manual for installation details.
When the problem has been
removed, perform one of the following successfully to confirm the
problem has been solved:
* Select the Configure Button in
the Device Set-up tab
* Select the Test Button in the
Device Set-up tab
53
CX-Server could not be initialized
Initialization of CX-Server was not
possible.
• Ensure the correct version of CXServer is installed on the Personal
Computer. Refer to the Master
Manual for installation details.
D-4
Error Messages - System
The table below lists the Error messages related to the System on which the DTM is installed.
Number
Message
Description
Correction
100
Connected device can not be con- Incorrect firmware type.
figured with this DTM
Make sure the unit connected is a
CS1W-PRM21 or CJ1W-PRM21.
Make sure the Unit number in the
Device set-up corresponds to the
physical unit.
101
Incorrect version of CX-Server.
Make sure the correct CX-Server
version is installed. Version must be
1.7 and up.
Incorrect version of CX-Server.
241
Appendix D
Configurator Error and Warning Messages
Number
Message
102
[Name of the function] called with
improper parameters
Container called a function with
NULL pointer.
There must be problem in the container. Reinstall CX-PROFIBUS, if
problem persists contact supplier.
103
Received XML Document does
not fit it's XML schema
Container called a function with an
improper XML document.
There must be a problem in container program. Reinstall CX-PROFIBUS, if problem persists contact
supplier.
104
Ole Register Drop Target Failed
An internal error has occurred.
Reinstall CX-PROFIBUS, if problem
persists contact supplier.
105
Undefined control type
An internal error has occurred.
Reinstall CX-PROFIBUS, if problem
persists contact supplier.
106
Communication failure with the
DTM
An internal error has occurred.
Reinstall CX-PROFIBUS, if problem
persists contact supplier.
107
GUI could not be closed
An internal error has occurred.
Reinstall CX-PROFIBUS, if problem
persists contact supplier.
242
Description
Correction
Appendix E
Memory Card Backup Functions
E-1
Outline of Functions
The PROFIBUS Master Unit stores the following setup data in the internal non-volatile memory (Flash ROM).
• Bus Parameters set
• Allocated slave parameter sets.
All these parameter sets can be backed up to and restored from a Memory Card mounted to the CPU Unit. If
the parameter data of a good functioning PROFIBUS Master Unit has been saved on a Memory Card, this
saved data can be used to perform a quick configuration, when replacing the PROFIBUS Master Unit, without
the direct use of the Configuration software. The data can be backed up to a Memory Card only. It cannot be
backed up to a EM file.
The backup process does not only involve the backup of the PROFIBUS Master parameter data, but also the
parameter data of any other Special CPU Bus Unit on the same PLC, as well as the PLC program, parameter
area data, and I/O memory data. This function can be executed in any operating mode.
When performing a backup from the PROFIBUS Master Unit to the Memory Card, the parameter sets are
stored in the file BACKUPnn.PRM, where nn is the Unit number in 2-digit hexadecimal.
Note This function is not supported by CS-series CS1 CPU Units that are pre-EV1.
Note With the release of CS1/CJ1W-PRM21 PROFIBUS DP-V1 Master Units, Unit version 2.0, the parameter
sets, which are written to the Memory Card have been changed slightly. A Unit with Unit version 2.0 can
still restore its parameter sets from a Memory Card written with an older CS1/CJ1W-PRM21, but an
older CS1/CJ1W-PRM21 will not restore its data from a Memory card, written with a newer CS1/CJ1WPRM21 Unit.
E-2
Backing Up Unit Setup Files
In order to save the Unit’s parameter sets to the Memory Card mounted to the CPU Unit, perform the following
procedure (see figure below).
1. Make sure that the parameter sets in the Unit are correct and that the Unit starts up normally, and insert a
Memory Card into the Card slot.
2. Turn ON pin 7 of the DIP switch on the front of the CPU Unit (behind the cover above the Memory Card slot).
3. Press and hold the Memory Card power supply switch for 3 seconds. When the switch is pressed, the MCPWR Indicator on the front of the CPU Unit will flash once and then remain lit while the data is being written.
The indicator will go OFF after the data has been written properly. During the transfer to the Memory Card,
the Parameter Transfer in Progress bit in Unit Status Word (CIO Word n+4) will turn ON.
243
Appendix E
Memory Card Backup Functions
Pin 7: ON
MCPWR
BUSY
Memory Card
E-3
Memory Card
LED indicators
Press and hold the
Memory Card Power
Switch for three seconds.
(This example shows a
CS-series CPU Unit.)
Restoring Unit Setup Files
In order to restore the Unit’s parameter sets from the Memory Card mounted to the CPU Unit, perform the following procedure.
1. Power down the PLC and insert a Memory Card into the Card slot.
2. Turn ON pin 7 of the DIP switch on the front of the CPU Unit (behind the cover above the Memory Card slot).
3. Turn ON the PLC’s power supply.
4. When the PLC’s power is turned ON, the MCPWR Indicator on the front of the CPU Unit will light and flash
once. The MCPWR Indicator will remain lit while the data is being read. The Indicator will go OFF after the
data has been read properly. During the Data Transfer, the PRM LED on the front of the Unit will flash, and
the Parameter Transfer in Progress bit in Unit Status Word (CIO Word n+4) will turn ON.
5. Restart the PLC.
Note 1. Data will not be read from the Memory Card to the CPU Unit if pin 1 of the DIP switch is ON (writeprotecting program memory).
2. A CS1-H, CJ1-H, or CJ1M CPU Unit will remain in PROGRAM mode after the simple backup operation has been performed and cannot be changed to MONITOR or RUN mode until the power supply
has been cycled. After completing the backup operation, turn OFF the power supply to the CPU Unit,
change the settings of pin 7, and then turn the power supply back ON.
6. File backups may take from several seconds to several minutes. Refer to CS/CJ-series Programming
Manual (W394) for information on execution times.
7. If an error occurred in the transfer from the Memory Card to the Unit, the File Read Error bit in Unit
Status Word (CIO Word n + 4, bit 09) will turn ON. To correct this, re-perform the Restore action. If
the problem persist, use CX-Profibus to download the original settings from the PC.
244
Appendix F
Application Notes
F-1
Introduction
This appendix contains an application note regarding the use of a special ladder program to detect any CS1/
CJ1W-PRM21 PROFIBUS Master Unit failures. This programs specifically covers failures due to faulty bus
parameters, set by the user.
F-2
Application Note Background
The CS1/CJ1W-PRM21 Master DTM allows the user to change certain bus parameter, in order to further optimize the PROFIBUS network performance. The risk however in doing this is that certain combinations may
lead to failures in the communication, either direct, or at a later point in time. The direct result of this failure is
that communication between the Master Unit and the PLC CPU - the PLC I/O refresh cycle - will take longer
than anticipated.
A ladder program can now be used to detect this, if the application warrants this safety measure. It relies on
the fact that non-used software switches (see section 4-2-1 Software Switches 1 (Word n)) when set by the
user program, are always reset by the Master Unit.
F-3
Application Program
The ladder program, as shown in the figure below, will regularly set switch number 15 in the Software Switches
1 word (CIO Word n, where n in the example is 1500), and start a counter. The counter will count the amount
of PLC I/O refresh cycles, before the Master Unit resets the switch. If the counter reaches the maximum value
(e.g. 40 as in the example ladder program), without the switch being reset, a PLC error will be generated.
The counter must be configured by the user, and depends on the PROFIBUS cycle. The longer that cycle is,
the longer the counter has to count up. It is recommended to include a safety margin to avoid the PLC error
being generated too soon. An estimate for the value can be made using the formula below.
2*TTR
Timer value = Max ( 40, ----------------------- )
min. PLC Cycle
In the ladder program shown as example below, the minimum value of 40 has been used. The unit number for
the example Unit is 0.
245
Appendix F
Application Notes
000000
(000000)
1500.15
CIOn_bit15
TestFlag
000001
(000002)
++
(590)
W0
Number of PLC cycles without refresh
Refresh
Counter
>=
FALS
(325)
(007)
W0
1
Refresh
Counter
&40
000002
(000004)
1500.15
#0000
@MOV
(021)
CIOn_bit15
#0
TestFlag
W0
Number of PLC cycles without refresh
Refresh
Counter
000003
(000006)
246
CF113
1500.15
TestFlag
P_On
CIOn_bit15 .
Always
ON Flag
TestFlag
Appendix G
C200HW-PRM21 Notes
G-1
Introduction
This appendix contains notes on the use of the C200HW-PRM21 PROFIBUS DP Master unit on a CS1 PLC
System. The C200HW-PRM21 is a special I/O Unit, originally designed for the C200H-series PLC, but can also
be used on the CS1-series PLC systems.
G-2
Word allocations
This section provides a brief overview of the memory allocations required by the C200HW-PRM21 for Unit settings and Control and status words. For more details refer to the C200HW-PRM21 PROFIBUS DP Master Unit
Operation Manual ([email protected]).
MACH No
Unit settings area
Control and Status Area
Error flag
Restart flag
0
DM20000 to DM20017
CIO2000 to CIO2004
AR418.00
AR502.00
1
DM20100 to DM20117
CIO2010 to CIO2014
AR418.01
AR502.01
2
DM20200 to DM20217
CIO2020 to CIO2024
AR418.02
AR502.02
3
DM20300 to DM20317
CIO2030 to CIO2034
AR418.03
AR502.03
4
DM20400 to DM20417
CIO2040 to CIO2044
AR418.04
AR502.04
5
DM20500 to DM20517
CIO2050 to CIO2054
AR418.05
AR502.05
6
DM20600 to DM20617
CIO2060 to CIO2064
AR418.06
AR502.06
7
DM20700 to DM20717
CIO2070 to CIO2074
AR418.07
AR502.07
8
DM20800 to DM20817
CIO2080 to CIO2084
AR418.08
AR502.08
9
DM20900 to DM20917
CIO2090 to CIO2094
AR418.09
AR502.09
A
DM21000 to DM21017
CIO2100 to CIO2104
AR418.10
AR502.10
B
DM21100 to DM21117
CIO2110 to CIO2114
AR418.11
AR502.11
C
DM21200 to DM21217
CIO2120 to CIO2124
AR418.12
AR502.12
D
DM21300 to DM21317
CIO2130 to CIO2134
AR418.13
AR502.13
E
DM21400 to DM21417
CIO2140 to CIO2144
AR418.14
AR502.14
F
DM21500 to DM21517
CIO2150 to CIO2154
AR418.15
AR502.15
Unit Settings
The Unit settings are located in the DM area in the PLC memory. The exact location of the block of settings
depends on the Machine Number setting, as set prior to power-up on the front of the Unit using the rotary
switch.
The Unit settings define
• the I/O mapping areas and the mapping of the slave status data,
• the data exchange procedure (synchronous or asynchronous)
• the Units behaviour in case of a fatal PLC error (CLEAR or HOLD outputs)
The Unit can be operated in a default mode, i.e. all DM settings set to 0000. The table below lists the contents
of the Unit settings.
247
Appendix G
C200HW-PRM21 Notes
Word m [m = DM 20000 + (100 x Machine number)]
DM
word
m
Function
Number of output data areas
Value
0000
Default mapping.
PLC addresses CIO0050 to CIO0099 are mapped to Unit output
buffer bytes 000 to 099
0001
One user-defined output data area.
DM word m+1, m+2 and m+3 define the first area.
0002
Two user-defined output data areas.
DM word m+4, m+5 and m+6 define the second area.
Other
m+1
m+2
Description
Output Area 1:
0000 to 0510
Start address in the Unit output Other
buffer
Default mapping (see 0000)
Byte 000 ~ 510 (even) in output buffer of the Unit
Setting error, output area is ignored (See Note 1)
0000 to 5999 D00000 ~ D05999
Output Area 1:
Start address in the Unit output A000 to A235 CIO0000 ~ CIO0235
buffer
A300 to A511 CIO0300 ~ CIO0511
B000 to B099 HR000 ~ HR099
C000 to C063 CIO1000 ~ CIO1063
Other
Setting error, output area is ignored (See Note 1)
0000 to 0100
0000 ~ 0100 words to be transferred from PLC to the Unit output buffer (See Note 1 and 2)
m+3
Output Area 1:
Size
m+4
Output Area 2:
See m+1
Start address in the Unit output
buffer
m+5
See m+2
Output Area 2:
Start address in the Unit output
buffer
m+6
Output Area 2:
Size
See m+3
m+7
Number of input data areas
0000
Default mapping.
PLC addresses CIO0050 to CIO0099 are mapped to Unit input
buffer bytes 000 to 099
0001
One user-defined input data area.
DM word m+8, m+9 and m+10 define the first area.
0002
Two user-defined input data areas.
DM word m+11, m+12 and m+13 define the second area.
m+8
m+9
Other
Default mapping (see 0000)
Input Area 1:
Start address in the Unit input
buffer
0000 to 0510
Byte 000 ~ 510 (even) in input buffer of the Unit
Other
Setting error, input area is ignored (See Note 1)
Input Area 1:
Start address in the Unit input
buffer
0000 to 5999
D00000 ~ D05999
A000 to A235 CIO0000 ~ CIO0235
A300 to A511 CIO0300 ~ CIO0511
B000 to B099 HR000 ~ HR099
C000 to C063 CIO1000 ~ CIO1063
Other
Setting error, input area is ignored (See Note 1)
0000 to 0100
0000 ~ 0100 words to be transferred from PLC to the Unit input
buffer (See Note 1 and 2)
Other
Setting error, input area is ignored (See Note 1)
m+10
Input Area 1:
Size
m+11
Input Area 2:
Start address in the Unit input
buffer
See m+8
m+12
Input Area 2:
Start address in the Unit input
buffer
See m+9
248
Appendix G
C200HW-PRM21 Notes
DM
word
Function
Value
m+13
Input Area 2:
Size
See m+10
m+14
Slave status data mapping
0001
m+15
Start address in user-defined
mapping mode
(Area size = 16 words)
Description
User-defined mapping. Area defined by DM m+15.
Other
Default mapping to CIO0200 to CIO0215
0000 to 5984
D00000 ~ D05984
A000 to A220 CIO0000 ~ CIO0220
A300 to A496 CIO0300 ~ CIO0496
B000 to B084 HR000 ~ HR084
C000 to C048 CIO1000 ~ CIO1048
m+16
m+17
Data Exchange procedure
Other
Default mapping to CIO0200 to CIO0215
0000
Fieldbus cycle asynchronous with PLC cycle (Default)
The fieldbus cycles are triggered independently (i.e. asynchronous) of the PLC cycle, providing optimal I/O response time
when the PLC cycle time is at least twice the fieldbus cycle time.
Other
Fieldbus cycle synchronous with PLC cycle
The fieldbus cycles are triggered at the end of an I/O refresh
and are therefore synchronised with the PLC cycle. If the fieldbus cycle time exceeds the PLC program execution time, the
next fieldbus cycle will not be triggered until the completion of
the next I/O refresh. This method ensures synchronization
between PLC cycle and fieldbus cycle.
Fatal PLC error handling (asyn- 0000
chronous data exchange
mode)
Other
CLEAR outputs
All output data sent to the slaves will be cleared.
HOLD outputs
All output data sent to the slaves will remain the same as before
the occurrence of the Fatal PLC error.
Note 1. Setting errors are indicated in CIO n+2. Additionally, t he ERR LED will be flashing to indicate a nonfatal error.
2. If the specified number of words would make the area exceed the boundaries of the available buffer,
DM, LR, CIO or HR areas, the actual number of transferred words will be limited as to remain within
all of these boundaries.
3. The Unit does not check the validity of the contents of any PLC data area, from which output data is
to be transferred. Any data present in the area will be transferred to the output buffer of the Unit.
4. If multiple fieldbus masters (e.g. PROFIBUS DP, Devicenet, SYSMAC BUS) are mounted on the
same PLC system, only one of them can be used in default mapping mode. The Unit does not check
if the mapped PLC input area is in use by other Units. If so, this Unit’s data may overwrite another
Unit’s data, or vice versa.
5. If the settings cause two destination areas to overlap, the data of the higher number area will overwrite the lower. This practice must be avoided by the user.
249
Appendix G
C200HW-PRM21 Notes
Control Words
The control words for the C200HW-PRM21 PROFIBUS DP Master Unit to allow the PLC CPU program to initiate actions with respect to the PROFIBUS network. In general the following features are provided:
• Change the state of the Unit with respect to transfer of I/O data.
• Clear the mailbox.
• Transmit a Global_Control command over the PROFIBUS network, with specified settings.
The table below lists the two control words and their description of individual bits.
Word n [n = CIO 2000 + (10 x Machine number)]
CIO
Word
n
Bit
00
01
Name
Run
Value
OFF
No exchange of I/O data between PLC and remote I/O, and no
processing of mailbox commands will take place. A transition
from ON to OFF will clear or hold the outputs depending on the
value set in DM m+17. Holding remote outputs is only available in
asynchronous data exchange mode.
ON
Unit in normal operation; exchange of I/O data with PLC, and processing of mailbox commands are enabled.
I/O Communication inhibit OFF
ON
02
03~06
Not Used
07
Issue Control command
08
Not Used
09
Clear_Data
10
11
12
13
14, 15
250
Input Mailbox clear
Unfreeze
Freeze
Unsync
Sync
Not Used
Description
I/O communication is enabled.
I/O communication is disabled. A transition from OFF to ON
changes the PROFIBUS DP network state from ‘Operate’ via
‘Clear’ to ‘Stop’. All remote outputs will therefore be reset.
OFF
No specific action.
ON
Each I/O refresh, one unprocessed response (if available) is
removed from the input mailbox.
OFF
No control commands are issued.
ON
Each I/O refresh, one control command is issued. The control
command is specified by CIO n.09~13, and the destination is
specified by CIO n+1.
OFF
Clear_Data bit will not be set in next Global_Control message.
ON
Set Clear_Data bit in next Global_Control message: Clear output
data at slave device.
OFF
Unfreeze will not be set in next Global_Control message.
ON
Set Unfreeze bit in next Global_Control message: Unfreeze input
data at slave device (See Note 1).
OFF
Freeze bit will not be set in next Global_Control message.
ON
Set Freeze bit in next Global_Control message: Freeze input data
at slave device (See Note 1).
OFF
Unsync bit will not be set in next Global_Control message.
ON
Set Unsync bit in next Global_Control message: Unsync output
data at slave device (See Note 1).
OFF
Sync bit will not be set in next Global_Control message.
ON
Set Sync bit in next Global_Control message: Sync output data at
slave device (See Note 1).
Appendix G
C200HW-PRM21 Notes
CIO
Word
n+1
Bit
00~06
Name
Value
Station address
07
Not Used
08
Group 1
09
Group 2
10
Group 3
11
Group 4
12
Group 5
13
Group 6
14
Group 7
15
Group 8
Description
00~ 7D
Selected slave device address.
7F
Target Global_Control message to all slave devices, which comply with the selected group bits (See bit 08 ~ 15)
--
Select individual groups of slave devices, by setting bits associated with the group.
Set all group bits to 00 to select all slaves.
Note 1. The Clear_Data command will always clear the output data, whether the Freeze command is activated or not.
2. When activated simultaneously, Unsync has priority over Sync, and Unfreeze has priority over
Freeze.
Status Words
The status words for the C200HW-PRM21 PROFIBUS DP Master Unit to allow the PLC CPU program to determine the status of the Unit as well as the PROFIBUS network. In general the following features are provided:
• Change the state of the Unit with respect to transfer of I/O data.
• Clear the mailbox.
• Transmit a Global_Control command over the PROFIBUS network, with specified settings.Send
The table below lists the two control words and their description of individual bits
CIO
Word
n+2
Bit
00
Name
Value
Input data transferred OFF
ON
01
Not Used
02
Auto-Clear
03
No data
Description
No input data has been transferred to the mapped PLC data area(s)
during the last I/O refresh.
Input data has been transferred to the mapped PLC data area(s) during
the last I/O refresh.
OFF
Not in Auto_clear mode.
ON
The master branched into Auto_clear mode, because of a remote node
error.
OFF
All remote nodes are in data exchange mode. This bit is also cleared
during a database download or when a P-DP H/W failure is detected
(CIO n+2.06 is set).
ON
At least one remote node is not in the data exchange mode or reports a
fatal error.
OFF
No error
ON
Malfunctioning of the PROFIBUS DP hardware.
04~05 Not Used
06
07
08
P-DP H/W failure
Wrong CPU unit
DM setting error
(exceeding max.
words)
OFF
No error
ON
The Unit is mounted to a PLC type which does not support the
C200HW-PRM21.
OFF
No error
ON
The input/output area mapping, defined by the Unit’s DM settings,
exceeds the maximum allowed number of words (300 words).
251
Appendix G
C200HW-PRM21 Notes
CIO
Word
Bit
Name
Value
n+2
09
(cont’d)
DM setting error (out- OFF
put area mapping)
ON
10
DM setting error
OFF
(input area mapping) ON
11
12
13
Control command not OFF
processed
Output mailbox full
Reply in input mailbox
14~15 Network state
n+3
n+4
No error
There is an error in the output area mapping. The mapping contains an
incorrect value for either:
• the start address in the output buffer in the Master,
• the start address of the output area(s) in the PLC,
• or the size of the output area(s), or the specified size exceed the
boundaries of available buffer, DM, LR, CIO or HR areas.
No error
There is an error in the input area mapping. The DM settings contain
an incorrect value for either:
• the start address in the input buffer in the Master,
• the start address of the input area(s) in the PLC,
• or the size of the input area(s), or the specified size exceed the
boundaries of available buffer, DM, LR, CIO or HR areas.
The output mailbox was able to receive and process the previously
issued control command message.
ON
The issued control command could not be processed because the output mailbox was full (see section 5-2) or the RUN-bit was not set or the
bus communication was inhibited.
OFF
The output mailbox is able to receive (and process) a message. This
message can be a control command issued via CIO n or any PROFIBUS command by using the IOWR instruction.
ON
The output mailbox is full and cannot receive new messages.
OFF
The input mailbox does not contain a response message to a command message issued with IOWR.
ON
The input mailbox contains a response message to a command message issued with IOWR.
00
Offline: Communication with all DP participants is stopped.
01
Stop: Only communication with DP-Master (class 2) is possible.
10
Clear: The master tries to set parameters, check configuration and perform data exchange with its associated DP-slaves; the slaves’ inputs
are transferred to the input buffer, their outputs are cleared.
11
Operate: The master exchanges data with the assigned DP-slaves.
00~07 Error number
--
Error numbers CIO n+3 contains error messages related to either a
specific slave device or the Unit itself. For detailed error code, refer to
the C200HW-PRM21 PROFIBUS DP Master Unit Operation Manual
([email protected]).
08~15 Station address
00~7D
The Error number is related to a specific slave device, as indicated by
the station number.
FF
The Error number is related to the Unit itself.
00~11 Message length
12~15 Unit number
G-3
Description
001~12 When CIO n+2.13 is set (Reply in output mailbox), this CIO word con8
tains the length of the message that can be retrieved with an IORD
0~F
instruction. Combined with the Unit number, this constitutes the correct
source information for the IORD instruction. Refer to the C200HWPRM21 PROFIBUS DP Master Unit Operation Manual ([email protected]).
CIF Driver error messages
This section lists the most common error messages encountered with the serial communication driver for the
C200HW-PRM21. Extended error messages are available through the Help files of the C200HW-PRM21 DTM.
252
Appendix G
C200HW-PRM21 Notes
Error Number
Description
-20
No COM port found or COM port already in use
-21
COM port already opened
-22
Function call into driver has failed
-23
Internal driver error
-24
Could not create read thread
-25
Could not create read event
-26
Could not create write event
-27
Could not create timer event
-28
Error by writing data
-29
Wrong COM state
-30
COM state error is set
-31
COM buffer setup failed
-32
COM set timeout failed
-33
Receive buffer overrun
-34
Receive buffer full
-35
Send busy
-36
Error during close driver
-40
COM port not opened
-41
Invalid handle value
-42
Invalid COM number
-43
Size parameter invalid
-44
Size parameter zero
-45
Buffer pointer is NULL
-46
Buffer too short
-47
Setup error
-50
Send message, timeout error
-51
Could not send a message
-52
Send message, no device connected
-53
Error by send message, message receiving
-54
Telegram collision
-55
Telegram, no acknowledgement received
-56
Telegram, noise
-57
Telegram, data overrun
-58
Telegram, parity error
-59
Telegram, framing error
-60
User: Telegram, unknown error
-70
Timeout by receive a message
-71
No message received
253
Index
A
About
Manual, ix
Adding Devices to the Network, 144
Application, 245
Auto addressing
See I/O data, Mapping
Auto-CLEAR, 6, 67
Behaviour, 97
Enable, 183
Feature, 183
Resume OPERATE mode after, 183
Transition conditions, 183
B
Basic Operating Procedure, 23
Broadcast communication
See Global Control
Bus access protocol, 4
Bus connector, 38
See Wiring
Bus parameters, 219
Baud rate, 220
Data control time, 221
Definitions, 219
Determining bus parameters, 221
GAP update factor, 221
Highest station address, HSA, 221
Max retry limit, 220
Max Tsdr, 220
Min slave interval, 220
Min Tsdr, 220
Poll timeout, 221
Quiet time, 220
Setup time, 220
Slot time, 220
Target rotation time, 220
Watchdog control, 221
Bus termination
See Wiring
C
C200HW-PRM21 DTM, 19
Address table tab, 86
Adjusting bus parameters, 86
Auto addressing, 88
Bus parameter tab, 84
Changing address mapping, 88
CIF error messages, 252
CIO Control words, 250
CIO status words, 251
Configuration user interface, 83
Configuring communication, 91
Connecting, 91
Diagnostics user interface, 88
Downloading parameters, 91
Installation, 50
Memory layout, 87
Monitoring, 92
Sorting I/O modules, 88
Unit DM settings, 247
Word allocations, 247
Cable
see Wiring
CIO Area
See I/O Allocations, CIO Area
Configuring the PROFIBUS DP Master
See C200HW-PRM21 DTM, Configuration
See CS1/CJ1W-PRM21 DTM, Configuration
CS1/CJ1W-PRM21
External dimensions, 15
Functional Specifications, 12
Protocol Specification, 13
Specifications, 11
CS1/CJ1W-PRM21 dimensions, 15
CS1/CJ1W-PRM21 DTM, 18
Address, 155
Auto addressing, 157
Auto Update, 185
Auto-CLEAR, 156
Bus parameter, 157
Changing mode, 177
Diagnosis User Interface, 185
Downloading the configuration, 161
Error Log, 190
Access from PLC program , 192
Clearing, 191
Concept, 190
Detecting new errors, 190
Reading, 191
I/O Mapping, 158
Manual refresh, 185
Master parameters, 155
Master setup tab, 155
Master Status, 186
Monitoring, 185
Reading the Master status, 185
Set device station address, 72, 148
Slave DTM Address assignment, 72, 148
Slave status, 186
Storing the configuration, 161
Unit description, 160
Unit firmware version, 160
Unit number, 155
Unit PLC behaviour, 156
CX-Profibus
CD-ROM, 42
255
Index
Default password, 51
Device Catalogue
See Device Catalogue
DTM view, 53
Error Log view, 53
FDT Monitoring view, 53
Features, 18
Generic slave DTM
See Generic slave DTM
Installation
Procedure, 42
Requirements, 42
Login window, 51
Main Menu, 53
Main window, 52
Master DTM
See C200HW-PRM21 DTM
See CS1/CJ1W-PRM21 DTM
Network view, 52
Specifications, 21
Starting, 51
Status Bar, 54
Tool Bar, 54
CX-Server
Configuring, 159
CPU selection, 159
Network type, 160
Testing the setup, 160
D
Data conversion
See I/O data, Types, Conversion
Device address, 146
Device Catalogue
Additional DTM Information, 56
DTM group selection window, 56
DTM view layout, 55
Generating the Device Catalogue, 51
Installing GSD files, 57
Invoking, 55
Main components, 55
Open, 143
Updating, 57
Device DTM , 7
Device profile, 4
Diagnostic functions, 5
Diagnostics
Channel Related, 5
Device Related, 5
Module Related, 5
Diagnostics Update Delay, 98
DM Area
See I/O Allocations, DM Area
256
Downloading the configuration, 19
DTM
non-GSD based, 143
PROFIBUS DP-V1 services, 19
E
EC Directives
Low voltage, EN 61131-2:1994+A12:2000, xviii
EMC Directives
EMI directive, xviii
EMS directive, xviii
Environment, 12
Error codes, 215
Error log, 214
Adding records, 214
Clearing, 214
Error codes, 215
Error log location, 214
Error log records, 214
Logged errors, 214
Reading Error log, 214
Error messages
Communication, 240
Configuration, 239, 245, 247
System, 241
Error on Cyclic Data Exchange, 98
Exchanging I/O data, 170
I/O response time, 172
Minimum I/O response time, 174
PLC cycle time performance, 172
PLC cyclic refresh, 170
PLC vs. PROFIBUS, 170, 171
F
Fail-safe, 6, 98
FDT/DTM
Communication DTM, 8
Device DTM, 7
DTM properties, 8
DTM versus GSD file, 9
FDT Container application, 7
FDT/DTM Concept, 7
FDT/DTM technology, 7
User interface, 8
XML based data transfer, 8
FINS communication
Command codes, 123
Command reference
CONTROLLER AREA READ (0501), 128
ERROR LOG CLEAR (0203), 130
ERROR LOG READ (2102), 128
MEMORY AREA READ (0101), 125
PROFIBUS MESSAGE SEND (2809), 130
Index
RUN (0401), 126
STOP (0402), 127
Message communication, 122
PROFIBUS DP services
Get_Cfg service, 135
Rd_Inp service, 133
Rd_Outp service, 134
Set_Slave_Add service, 131
PROFIBUS DP-V1 services
MSAC1_Read, 136
MSAC1_Write, 138
PROFIBUS services, 130
Response codes, 123
Sending, using CMND, 124
Troubleshooting, 216
Freeze
See Global Control
G-H
Generic Slave DTM, 19
Extended diagnostics, 189
Extensions
Alarm SAP, 100
Alarms, 100
Auto-Clear behavior, 97
Configuration processing, 97
Diagnostics Update Delay, 98
DPV1 enable, 99
Error on Cyclic Data Exchange, 98
Fail-safe behavior, 98
Max. Alarm PDU length, 100
Max. channel data length, 99
Standard diagnostics, 189
Generic slave DTM
Configuring, 149
Group assignment, 153
I/O Configuration, 150
Appending, 150
Defining, 149
Inserting, 150
Removing, 151
Parameters, 152
Common, 152
Module, 152
Watchdog, 151
Global Control
Broadcast message, 110
Commands, 179
Freeze/Unfreeze, 79, 179
I/O synchronization, 179
Multicast message, 110
Selecting groups
in CIO words, 110
in CX-Profibus, 80
Sync/Unsync, 79, 179, 180
Transmitting commands, 181
CIO Words, via, 110
CX-Profibus, via, 80, 182
PLC program, via, 181
GSD file
DP-master section, 9
DP-slave section, 9
DTM versus GSD file, 9
General section, 9
GSD file technology, 8
Installing new, 143
Language, 9
HSA
See Bus parameters
I
I/O Allocations
CIO Area
Actual bus cycle time (Word n+8), 118
Global Control message (Word n+2), 110
Master status word 1 (Word n+5), 114
Master status word 2 (Word n+6), 116
Reserved words, 108
Slave Data_Exchange flags (Word N+9~n+16), 118
Slave New diagnostics flags (Word n+17~n+24), 119
Slave status word (Word n+7), 117
Software switches 1 (Word n), 109
Unit status word (Word n+4), 113
CIO/DM Area Overview, 106
DM Area
Allocations, 107
I/O data
Configuration, 162
Mapping
Algorithm, 162
Area start address, 168
Auto addressing
Default behaviour, 163
Enable/disable, 166
Mapping without, 166
Re-allocating modules, behaviour when, 165
Compressing, 167
Concept, 162
Re-allocating modules, 164
Removing gaps, 167
Supported I/O range, 162
Types, 169, 233
Conversion, 233
Date/Time, 169, 235
Floating point, 169, 234
Integer, 169, 233, 234
Text string, 169, 235
Time difference, 169
Time of day, 169
I/O table
257
Index
Creating, 34
Installation
Handling precautions, 30
Mounting
CJ1W-PRM21, 32
CS1W-PRM21, 30
Installing new GSD files, 143
L-M
LED indicators, 27
Specifications, 27
See also Troubleshooting, LED indicators
Low voltage directive, xviii
Maintenance, 217
Cleaning, 217
Inspection, 217
Equipment, 217
Procedure, 217
Manual
About, ix
Revision history, 261
Master devices
See PROFIBUS, Master
Master DTM
Configuration, 7
See C200HW-PRM21 DTM
See CS1/CJ1W-PRM21 DTM
Medium Access Control, 4
Memory card
Backing up Unit setup files, 243
Backup functions, 243
Restoring Unit setup files, 244
Message communication
See FINS communication
Min slave interval, 220
Monitoring
CS1/CJ1-PRM21 Master Unit, 6
Monitoring Time, 6
Slave device, 6
Monitoring slave status, 189
Multicast communication
See Global Control
N
Network operation modes
CLEAR, 6
OFFLINE, 6
OPERATE, 6
STOP, 6
Network structure, 35
Linear bus topology, 35
Repeaters, 36
258
Tree topology, 36
O-P
OMRON
Copyright notice, vi
Operation modes
SeeNetwork Operation modes, 6
OSI reference model, 2
ISO-7498, 2
Layer 1, Physical Layer, 2
Layer 2, Data Link Layer, 2
Layer 7, Application Layer, 2
Password
Default, 51
PLC cycle time performance, 172
Polling procedure, 5
Precautions
Application, xvi
General, xiv
Operating Environment, xv
Safety, xiv
PROFIBUS
Device profile, 4
Master
Class 1 Master (DPM1), 4
Class 2 Master (DPM2), 4
Network
Changing mode, 177
Indirect mode changes, 178
Mode changes, 177
Monitoring, 185
Operational modes, 6
User access, 176
PROFIBUS DP, Decentralized Periphery, 2
PROFIBUS DP-V1, 4
PROFIBUS FMS, Fieldbus Message Specification, 2
PROFIBUS PA, Process Automation, 2
Protocol Specification, 13
R
RS-485
Cable length, 3
Cable Type, 37
Transmission medium, 3
Transmission speed, 3
See also Wiring
S
Safety Precautions, xiv
Setting up a network, 142
shock resistance, 12
Slave devices, 4
Index
Slave diagnostics
Data, 223
Extended data, 226
Channel related, 228
Device related, 226
Example, 230
Module related, 227
Reading
MEMORY AREA READ, 223
Standard data, 224
startup times, 175
Sync
See Global Control
system
startup times, 175
System startup time, 175
T
Target rotation time
See also Bus parameters
Token passing, 5
Trademarks, vi
Transmission medium, 3
RS-485, 3
Transmission speed, 3
LED indicators, using, 195
U
Unit number
CPU Bus Unit allocations, 28
Setting, 28
See also CS1/CJ1W-PRM21 DTM
Unit replacement, 218
Precautions, 218
Replacing PROFIBUS Units, 218
Unit setup, 218
V-W
vibration resistance, 12
Warning messages, 237
Watchdog control
See Bus parameters
Wiring
Bus connector, 38
Bus termination, 37
Inductors, 38
Resistors, 37
Cable length, 3
Cable shield connection, 39
Troubleshooting
CS1/CJ1-PRM21 Master Unit, 194
CX-Profibus, 194
Error codes, 215
Error log, 214
Adding records, 214
Clearing, 214
Error log location, 214
Error log records, 214
Logged errors, 214
Reading Error log, 214
Error status, 201
CIO words, 201
Unit status word, 201
FINS Commands, 216
LED indicators, using, 195
Network
CS1/CJ1W-PRM21 DTM, 205
CX-Profibus, using, 205
I/O communication, 210
LED indicators, using, 199
Slave devices, 207
Overview, 194
PROFIBUS network, 194
Unit configuration
LED indicators, using, 198
Unit operational errors
LED indicators, using, 197
Unit startup
259
Index
260
Revision History
A manual revision code appears as a suffix to the catalog number on the front cover of the manual.
Cat. No. W409-E2-03
Revision code
The following table outlines the changes made to the manual during each revision. The page numbers of a
revision refer to the previous version.
Revision Code
Date
Revised Content
01
March, 2004
Initial version.
02
February, 2005
Page
Page
Page
Page
Page
Page
Page
Page
Page
Page
Page
Page
Page
Page
Page
Page
Page
Page
Page
Page
Page
ix: Added line on C200HW-PRM21 to About section.
8: Added C200HW-PRM21 DTM to bullet list.
11: Added Vibration, Shock and Dielectric strength data to table.
16: Added C200HW-PRM21 DTM to bullet list.
16: Added description of C200HW-PRM21 DTM.
17: Added C200HW-PRM21 DTM downloading description.
17: Updated figure.
18: Added C200HW-PRM21 connection method to table.
19: Added C200HW-PRM21 DTM to table.
20: Improved Basic Operations flow chart.
28: Renamed section 2.2.
40: Added C200HW-PRM21 DTM to bullet list.
48: Added section 3-1-3.
61: Renamed section 3.3.
76: Renamed section 3.3.3.
79: Renumbered section 3.4 to section 3.5.
79: Added new section 3.4.
92: Added note on C200HW-PRM21 word allocations.
108: Added note on C200HW-PRM21 and FINS.
118: Added note on operation of the C200HW-PRM21.
223: Added Appendix G.
261
Revision History
Revision Code
03
262
Date
July, 2005
Revised Content
Changed title of document.
Corrected PROFIBUS DP naming to comply with PROFIBUS standards.
Corrected terminology regarding views, tabs and windows.
Changed Unit naming from PROFIBUS DP Master to PROFIBUS Master.
Page vi: Added HART Trademark.
Page ix: Added function/version number table and description.
Page 4: Added description on PROFIBUS DP-V1.
Page 5: Removed text in brackets from Multicast command description.
Page 5: Changed Extensive Diagnostics to Extended Diagnostics.
Page 5: Edited description on Extensive Diagnostics.
Page 8: Added new DTM to CX-Profibus DTM list.
Page 8: Updated name of PROFIBUS organization.
Page 9: Added paragraph on PROFIBUS DP-V1 services to DP slave section.
Page 10: Added paragraph on extended services to FINS messages.
Page 10: Changed first specification table to include version numbers.
Page 12: Added support of acyclic message services to table.
Page 14: Added PROFIBUS MESSAGE SEND FINS to table.
Page 15: Added support of acyclic message services to comparison table.
Page 16: Added DTM to bullet list.
Page 16: Changed description of CS1/CJ1W-PRM21 DTM.
Page 16: Changed naming of DTM parts from DTM to user interface.
Page 16: Added description on additional PROFIBUS DP-V1 DTM functions.
Page 17: Changed naming of DTM parts from DTM to user interface.
Page 17: Added Note to Generic Slave DTM description.
Page 19: Added PROFIBUS DP-V1 functions to specification table.
Page 40: Added Note 1 on uninstalling previous versions of CX-Profibus.
Page 54: Changed first line description in upper table for Version.
Page 61: Changed section 3.3. title.
Page 61: Added new DTM names to section 3.3 in table format.
Page 62: Added note below Configuration DTM view image.
Page 70: Added description of new functions to end of section 3.3.1.
Page 95: Updated note PROFIBUS DP-V1 tab.
Page 118: Added explanation and figure on FINS over PROFIBUS.
Page 119: Added note below table.
Page 123: Changed example version number to 2.00.
Page 125: Added section 5.2.7.
Page 132: Renamed and rewrote section 6.6.2.
Page 217: Added section B-5 on PROFIBUS DP-V1 error codes.
Page 224: Added warnings to table.
Page 225: Added errors to table.
Page 229: Added Note on backward compatibility for Memory Card.
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