Omron DeviceNet 3G8F7-DRM21-E Operation Manual
Cat. No. W381-E1-02
3G8F7-DRM21-E
DeviceNet PCI Board
OPERATION MANUAL
3G8F7-DRM21-E DeviceNet PCI Board
Operation Manual
Revised July 2005
iv
Notice:
r
f
OMRON products are manufactured for use according to proper procedures by a qualified operator
and only for the purposes described in this manual.
The following conventions are used to indicate and classify precautions in this manual. Always heed
the information provided with them. Failure to heed precautions can result in injury to people or damage to property.
!DANGER Indicates an imminently hazardous situation which, if not avoided, will result in death or
serious injury. Additionally, there may be severe property damage.
!WARNING Indicates a potentially hazardous situation which, if not avoided, could result in death or
serious injury. Additionally, there may be severe property damage.
!Caution Indicates a potentially hazardous situation which, if not avoided, may result in minor or
moderate injury, or property damage.
OMRON Product References
All OMRON products are capitalized in this manual. The word “Unit” is also capitalized when it refers to
an OMRON product, regardless of whether or not it appears in the proper name of the product.
The abbreviation “Ch,” which appears in some displays and on some OMRON products, often means
“word” and is abbreviated “Wd” in documentation in this sense.
Visual Aids
The following headings appear in the left column of the manual to help you locate different types of
information.
OMRON, 2000
All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form, o
by any means, mechanical, electronic, photocopying, recording, or otherwise, without the prior written permission o
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.
Note Indicates information of particular interest for efficient and convenient opera-
tion of the product.
1,2,3... 1. Indicates lists of one sort or another, such as procedures, checklists, etc.
v
vi
TABLE OF CONTENTS
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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii
7 Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviii
SECTION 1
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1-1 Product Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1-2 DeviceNet PCI Board. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1-3 Scanner SDK Functions and Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1-4 Scanner SDK Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1-5 System Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1-6 Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1-7 Board Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1-8 Preparation for Operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
SECTION 2
Software Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2-1 Installation Procedure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
2-2 Installing the Board in the Computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
2-3 Installing the Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
2-4 Installing the Scanner SDK Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
2-5 DeviceNet Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
SECTION 3
Using API Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
3-1 Application Development Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
3-2 API Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
3-3 Checking Events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
3-4 Checking for Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
3-5 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
3-6 Using I/O Communications Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
3-7 Using the Explicit Message Client Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
3-8 Using the Explicit Message Server Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
3-9 Reset Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
3-10 Error Log Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
3-11 PC Watchdog Timer Management Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
vii
TABLE OF CONTENTS
SECTION 4
API Function Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
4-1 Function Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
4-2 Board Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
4-3 Board Management API Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
4-4 Master Function API Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
4-5 Slave Function API Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
4-6 Explicit Message API Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
4-7 Maintenance API Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
SECTION 5
Sample Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
5-1 Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
5-2 Using DeviceNet Scanner Demo. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
SECTION 6
Communications Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
6-1 Remote I/O Communications Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
SECTION 7
Error Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
7-1 LED Indicators and Error Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
7-2 Identifying Errors Detected by Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
7-3 Error Log Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Revision History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
viii
About this Manual:
This manual describes the installation and operation of the 3G8F7-DRM21-E DeviceNet PCI Board
and includes the sections described below.
Please read this manual carefully and be sure you understand the information provided before
attempting to install and operate the 3G8F7-DRM21-E DeviceNet PCI Board.
Section 1 provides an overview of the DeviceNet PCI Board’s functions, specifications, and system
configurations.
Section 2 explains how to set the DeviceNet PCI Board’s board ID, install the Board in the computer,
and connect the communications cable.
Section 3 explains how to install the DeviceNet PCI Board’s drivers and Scanner SDK software.
Section 4 provides flowcharts showing how to use the API functions as well as precautions to observe
when using the API functions. Refer to this section when actually writing the applications required to
use the DeviceNet PCI Board.
Section 5 provides details on the various API functions in the BusDScan.DLL that are used with the
DeviceNet PCI Board.
Section 6 describes the sample programs that have been provided as reference when writing programs for the DeviceNet PCI Board.
Section 7 describes communications timing in remote I/O communications and message communications.
Section 8 describes troubleshooting and error processing procedures needed to identify and correct
errors that can occur during DeviceNet PCI Board operation.
Trademarks and Copyrights
COMBICON is a registered trademark of the Phoenix Contact Company.
DeviceNet is a registered trademark of the Open DeviceNet Vendor Association, Inc.
Pentium is a trademark of the Intel Corporation.
Windows, Windows 95, Windows 98, Windows NT, and Windows 2000 are registered trademarks of
the Microsoft Corporation.
Other product names and company names in this manual are trademarks or registered trademarks of
their respective companies.
The copyright of the DeviceNet PCI Board and related software belongs to OMRON Corporation.
!WARNING Failure to read and understand the information provided in this manual may result in per-
sonal 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.
ix
Read and Understand this Manual
Please read and understand this manual before using the product. Please consult your OMRON
representative if you have any questions or comments.
Warranty and Limitations of Liability
WARRANTY
OMRON's exclusive warranty is that the products are free from defects in materials and workmanship for a
period of one year (or other period if specified) from date of sale by OMRON.
OMRON MAKES NO WARRANTY OR REPRESENTATION, EXPRESS OR IMPLIED, REGARDING NONINFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR PARTICULAR PURPOSE OF THE
PRODUCTS. ANY BUYER OR USER ACKNOWLEDGES THAT THE BUYER OR USER ALONE HAS
DETERMINED THAT THE PRODUCTS WILL SUITABLY MEET THE REQUIREMENTS OF THEIR
INTENDED USE. OMRON DISCLAIMS ALL OTHER WARRANTIES, EXPRESS OR IMPLIED.
LIMITATIONS OF LIABILITY
OMRON SHALL NOT BE RESPONSIBLE FOR SPECIAL, INDIRECT, OR CONSEQUENTIAL DAMAGES,
LOSS OF PROFITS OR COMMERCIAL LOSS IN ANY WAY CONNECTED WITH THE PRODUCTS,
WHETHER SUCH CLAIM IS BASED ON CONTRACT, WARRANTY, NEGLIGENCE, OR STRICT
LIABILITY.
In no event shall the responsibility of OMRON for any act exceed the individual price of the product on which
liability is asserted.
IN NO EVENT SHALL OMRON BE RESPONSIBLE FOR WARRANTY, REPAIR, OR OTHER CLAIMS
REGARDING THE PRODUCTS UNLESS OMRON'S ANALYSIS CONFIRMS THAT THE PRODUCTS
WERE PROPERLY HANDLED, STORED, INSTALLED, AND MAINTAINED AND NOT SUBJECT TO
CONTAMINATION, ABUSE, MISUSE, OR INAPPROPRIATE MODIFICATION OR REPAIR.
x
Application Considerations
SUITABILITY FOR USE
OMRON shall not be responsible for conformity with any standards, codes, or regulations that apply to the
combination of products in the customer's application or use of the products.
At the customer's request, OMRON will provide applicable third party certification documents identifying
ratings and limitations of use that apply to the products. This information by itself is not sufficient for a
complete determination of the suitability of the products in combination with the end product, machine,
system, or other application or use.
The following are some examples of applications for which particular attention must be given. This is not
intended to be an exhaustive list of all possible uses of the products, nor is it intended to imply that the uses
listed may be suitable for the products:
• Outdoor use, uses involving potential chemical contamination or electrical interference, or conditions or
uses not described in this manual.
• Nuclear energy control systems, combustion systems, railroad systems, aviation systems, medical
equipment, amusement machines, vehicles, safety equipment, and installations subject to separate
industry or government regulations.
• Systems, machines, and equipment that could present a risk to life or property.
Please know and observe all prohibitions of use applicable to the products.
NEVER USE THE PRODUCTS FOR AN APPLICATION INVOLVING SERIOUS RISK TO LIFE OR
PROPERTY WITHOUT ENSURING THAT THE SYSTEM AS A WHOLE HAS BEEN DESIGNED TO
ADDRESS THE RISKS, AND THAT THE OMRON PRODUCTS ARE PROPERLY RATED AND
INSTALLED FOR THE INTENDED USE WITHIN THE OVERALL EQUIPMENT OR SYSTEM.
PROGRAMMABLE PRODUCTS
OMRON shall not be responsible for the user's programming of a programmable product, or any
consequence thereof.
xi
Disclaimers
CHANGE IN SPECIFICATIONS
Product specifications and accessories may be changed at any time based on improvements and other
reasons.
It is our practice to change model numbers when published ratings or features are changed, or when
significant construction changes are made. However, some specifications of the products may be changed
without any notice. When in doubt, special model numbers may be assigned to fix or establish key
specifications for your application on your request. Please consult with your OMRON representative at any
time to confirm actual specifications of purchased products.
DIMENSIONS AND WEIGHTS
Dimensions and weights are nominal and are not to be used for manufacturing purposes, even when
tolerances are shown.
PERFORMANCE DATA
Performance data given in this manual is provided as a guide for the user in determining suitability and does
not constitute a warranty. It may represent the result of OMRON's test conditions, and the users must
correlate it to actual application requirements. Actual performance is subject to the OMRON Warranty and
Limitations of Liability.
ERRORS AND OMISSIONS
The information in this manual has been carefully checked and is believed to be accurate; however, no
responsibility is assumed for clerical, typographical, or proofreading errors, or omissions.
xii
PRECAUTIONS
This section provides general precautions for using the DeviceNet PCI Board and related devices.
The information contained in this section is important for the safe and reliable application of the DeviceNet PCI
Board. You must read this section and understand the information contained before attempting to set up or
operate a DeviceNet PCI Board as part of a control system.
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. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii
6-1 Applicable Directives. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii
6-2 Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii
6-3 Conformance to EC Directives . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviii
7 Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviii
xiii
Intended Audience 1
1 Intended Audience
This manual is intended for the following personnel, who must also have
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 installing and operating the DeviceNet
PCI Board. Be sure to read this manual before operation and keep this manual close at hand for reference during operation.
!WARNING It is extremely important that all control products be used for the specified pur-
pose and under the specified conditions, especially in applications that can
directly or indirectly affect human life. You must consult with your OMRON
representative before applying an OMRON control system to the abovementioned applications.
3 Safety Precautions
!WARNING Never attempt to disassemble the Board or touch the Board while power is
being supplied. Doing so may result in serious electrical shock or electrocution.
!WARNING Provide safety measures in external circuits, i.e., not in the Programmable
Controller (CPU Unit including associated Units; referred to as “PLC”), in
order to ensure safety in the system if an abnormality occurs due to malfunction of the PLC or another external factor affecting the PLC operation. Not
doing so may result in serious accidents.
1,2,3... 1. Emergency stop circuits, interlock circuits, limit circuits, and similar safety
measures must be provided in external control circuits.
2. The PLC will turn OFF all outputs when its self-diagnosis function detects
any error or when a severe failure alarm (FALS) instruction is executed. As
a countermeasure for such errors, external safety measures must be provided to ensure safety in the system.
xiv
Operating Environment Precautions 4
3. The PLC outputs may remain ON or OFF due to deposition or burning of
the output relays or destruction of the output transistors. As a countermeasure for such problems, external safety measures must be provided to ensure safety in the system.
4. When the 24-VDC output (service power supply to the PLC) is overloaded
or short-circuited, the voltage may drop and result in the outputs being
turned OFF. As a countermeasure for such problems, external safety measures must be provided to ensure safety in the system.
!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 PLC on a
network.
!Caution Confirm safety at the destination node before transferring a program to
another node or changing contents of the I/O memory area. Doing either of
these without confirming safety may result in injury.
4 Operating Environment Precautions
Do not install the PCI Board in any of the following locations.
• 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.
xv
Application Precautions 5
5 Application Precautions
Observe the following precautions when using the DeviceNet PCI Board.
• Install failsafe safety mechanisms to provide safety in the event of incorrect signals that may result from signal line disconnections or power interruptions.
• Always use the power supply voltage specified in this manual.
• Mount the Board only after checking the connectors and terminal blocks
completely.
• 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.
• Always connect to a ground of 100
ing to a ground of 100
• Install external breakers and take other safety measures against short-circuiting in external wiring. Insufficient safety measures against short-circuiting may result in burning.
• Always turn OFF the power supply to the computer or slave before
attempting any of the following. Not turning OFF the power supply may
result in malfunction or electric shock.
• Mounting or dismounting DeviceNet PCI Board.
• Setting rotary switches.
• Assembling the Boards.
• Connecting cables or wiring the system.
• Connecting or disconnecting the connectors.
• Do not attempt to disassemble, repair, or modify any product.
• Be sure that all the board mounting screws, cable screws, and cable connector screws are tightened to the torque specified in the relevant manuals. Incorrect tightening torque may result in malfunction.
• Use crimp terminals for wiring. Do not connect bare stranded wires
directly to terminals.
• Double-check all the wiring and switch settings before turning ON the
power supply.
• Wire all connections correctly.
• Observe the following precautions when wiring the 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.
• Place communications cables in ducts.
• Use the specified communications cables.
• Always wire communications and signal lines within the specified connection distances.
• Before touching the Board, be sure to first touch a grounded metallic
object in order to discharge any static built-up. Not doing so may result in
malfunction or damage.
Ω or less may result in electric shock.
Ω or less when installing. Not connect-
xvi
Conformance to EC Directives 6
• Test the operation of the ladder program and other user programs completely before starting actual system operation.
• Always transfer the contents of any required DM Area words, HR Area
words, parameters, or other data to CPU Units, CPU Bus Units, and Special I/O Units before restarting operating after replacing any of these
Units.
• Be sure that the communications cable connectors, and other items with
locking devices are properly locked into place. Improper locking may
result in malfunction.
• Do not touch circuit boards or the components mounted to them with your
bare hands. There are sharp leads and other parts on the boards that
may cause injury if handled improperly.
• 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 or storing circuit boards, cover them in antistatic material to protect them from static electricity and maintain the proper storage
temperature.
• Always enable the scan list before operating the control system.
• Check the baud rate of any new node added to an existing network to be
sure that it agrees with the rest of the network.
6 Conformance to EC Directives
6-1 Applicable Directives
•EMC Directives
6-2 Concepts
EMC Directives
OMRON devices that comply with EC Directives also conform to the related
EMC standards so that they can be more easily built into other devices 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 the OMRON devices that comply with EC Directives will vary depending on the configuration, wiring, and other conditions of
the equipment or control panel in which the OMRON devices are installed.
The customer must, therefore, perform final checks to confirm that devices
and the overall machine conform to EMC standards.
Note Applicable EMC (Electromagnetic Compatibility) standards are as follows:
EMS (Electromagnetic Susceptibility): EN61131-2
EMI (Electromagnetic Interference): EN61000-6-4
(Radiated emission: 10-m regulations)
xvii
Components 7
6-3 Conformance to EC Directives
DeviceNet products that meet EC directives must be installed as follows:
1,2,3... 1. Used reinforced insulation or double insulation for the DC power supplies
used for the communications power supply, internal circuit power supply,
and the I/O power supplies.
2. DeviceNet products that meet EC directives also meet the common emission standard (EN61000-6-4). When DeviceNet products are built into
equipment, however, the measure necessary to ensure that the standard
is met will vary with the overall configuration of the control panel, the other
devices connected to the control panel, and other conditions. You must
therefore confirm that EC directives are met for the overall machine or device, particularly for the radiated emission requirement (10 m).
The following examples show means of reducing noise.
1,2,3... 1. Noise from the communications cable can be reduced by installing a ferrite
core on the communications cable within 10 cm of the DeviceNet PCI
Board.
Ferrite Core (Data Line Filter): 0443-164151 (manufactured by Nisshin Electric Co.)
Impedance Specifications
25 MHz: 156 Ω
100 MHz: 250 Ω
7 Components
33 mm
13 mm
30 mm
29 mm
2. Keep DeviceNet communications cables as short as possible and ground
to 100
Ω min.
Be sure that you have received the following components.
• One PCI Board (with communications connector)
• One installation disk (CD-ROM) for Scanner SDK
• One operation manual (this manual)
• One User Registration Card (which also serves as the software usage
license agreement)
xviii
SECTION 1
Introduction
This section provides an overview of the DeviceNet Scanner SDK functions, specifications, and system configurations.
1-1 Product Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1-2 DeviceNet PCI Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1-3 Scanner SDK Functions and Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1-4 Scanner SDK Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1-4-1 I/O Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1-4-2 Message Communications Function . . . . . . . . . . . . . . . . . . . . . . . . . 5
1-4-3 Maintenance Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1-5 System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1-6 Specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1-6-1 DeviceNet PCI Board General Specifications . . . . . . . . . . . . . . . . . 8
1-6-2 DeviceNet Communications Specifications . . . . . . . . . . . . . . . . . . . 8
1-6-3 Scanner SDK Communications Specifications. . . . . . . . . . . . . . . . . 9
1-6-4 Development Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1-6-5 Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1-7 Board Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1-8 Preparation for Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1
Product Configuration Section 1-1
1-1 Product Configuration
The 3G8F7-DRM21-E DeviceNet PCI Board includes the PCI Board (hardware) and the Scanner SDK software on CD-ROM.
3G8F7-DRM21-E DeviceNet PCI Board Scanner
PCI Board Scanner SDK
1-2 DeviceNet PCI Board
The PCI Board is used as an interface to other software, such as the
DeviceNet Configurator, NetXServer, and Analyzer.
DeviceNet PCI Board Scanner
WS02-CFDC1-E DeviceNet
Configurator
WS02-NXD@-1 NetXServer
for DeviceNet
WS02-ALDF-E DeviceNet
Analyzer
DeviceNet Scanner SDK
DeviceNet Configurator
NetXServer for DeviceNet
DeviceNet Analyzer
DeviceNet Scanner SDK The DeviceNet Scanner SDK (this product) is a library for developing applica-
tions that operate as DeviceNet Masters or Slaves. It is supplied as a DLL file
for a Windows environment.
Use the Scanner SDK to develop Master/Slave applications with industryleading performance and functions.
2
Scanner SDK Functions and Features Section 1-3
DeviceNet Configurator The DeviceNet Configurator is a Windows-based application that supports
construction of DeviceNet networks. The Configurator is used not only for setting parameters and monitoring OMRON Master and Slave devices, but also
for setting parameters for slaves from other manufacturers, simply by installing
the EDS files.
The Configurator provides extensive support for managing networks, from
design through to maintenance.
NetXServer for DeviceNet The NetXServer is middleware that operates in a Windows environment. The
NetXServer collects I/O data from a DeviceNet network and provides it to
monitoring and other applications. It operates as a DDE server.
NetXServer enables I/O data monitoring without affecting Master or Slave
communications.
The following two types of NetXServer are available:
DDE Edition: For monitoring I/O data using a DDE client (e.g., Microsoft
Excel)
SDK Edition: Library for developing monitoring applications using NetXServer
functions
DeviceNet Analyzer The DeviceNet Analyzer is a Windows-based application for analyzing mes-
sage frames on a DeviceNet network.
The DeviceNet Analyzer can display the message frames being transmitted
on a network and indicate traffic status. It can be used to find the source of
errors and for developing DeviceNet-compatible devices.
1-3 Scanner SDK Functions and Features
DeviceNet
Communications
Functions
Note The DeviceNet network is capable of exchanging I/O with distant Slaves
DeviceNet
Communications Features
The Scanner SDK is equipped with the following communications functions.
• I/O communications functions that exchange I/O data with other
DeviceNet nodes:
DeviceNet Master function
DeviceNet Slave function
• DeviceNet explicit messaging functions (client and server functions)
In addition to the communications functions above, the Scanner SDK has a
status function that reads the status of the node (Master/Slave) and the network and an error log function that records errors and their time of occurrence.
through a single cable. Moreover, Slaves and other Masters can be controlled
and monitored by sending and receiving explicit messages. Refer to the
DeviceNet Operation Manual (W267) for more details.
In this manual, the “client” is the node that sends a message requesting services and the “server” is the node that receives the message, performs the
requested processing, and returns a response.
The Scanner SDK has the following features:
Exchange I/O Data with DeviceNet Slaves
The status of I/O points on DeviceNet Slaves is mirrored in the DeviceNet PCI
Board. I/O can be performed with a specified Slave by calling the functions for
reading and writing I/O data.
3
Scanner SDK Functions Section 1-4
Use Other Vendor’s DeviceNet-compatible Devices
DeviceNet is a worldwide standard, so any manufacturer’s Slave can be connected as long as it is DeviceNet compatible.
I/O Capacity of 37,800 Bytes for Up To 63 Slaves
The Scanner SDK provides 37,800 bytes for I/O allocation to up to 63 Slaves
(input: 25,200 bytes; output: 12,600 bytes).
Use API Functions to Control Devices
All Scanner SDK functions are provided as API functions. User applications
are created using the API functions.
Check Events with Windows Messaging or Polling
Events can be checked in two ways: automatic notification by Windows messaging and monitoring (polling) of the Board’s event queue by user applications. Use the method most appropriate for each application.
Computer
Application program
API functions
One-cable, reduced
wiring
Max. network length
of 500 m
Output Slave
PCI Board
DeviceNet
communications
cable
T-branch Tap
Relay
Solenoid
Other company's Slaves
can be connected.
T-branching and multidrop wiring can be
combined freely.
Input Slave
Switch
Sensor
Connect up to 63 DeviceNet
Slaves.
1-4 Scanner SDK Functions
1-4-1 I/O Communications
Master Function The Scanner SDK Master function provides two 200-byte input areas (100
words or 1,600 points) and one 200-byte output area (100 words or 1,600
points) for allocation to each slave.
I/O communications are executed according to the scan list registered by the
Scanner SDK. Scan lists record information such as the number of input and
output bytes for each slave.
4
Scanner SDK Functions Section 1-4
Maximum Numbers of I/O Points and Slaves
The following table shows the max. number of I/O points, max. number of
Slaves, and max. number of I/O connections allowed by the Scanner SDK’s
Master function.
Item Specification
Max. number of I/O
points
Max. number of I/O
points per Slave
Max. number of Slaves 63 Slaves (Node addresses 0 to 63 can be used.)
Max. number of I/O connections per Slave
Note Two input areas have been provided for each slave, but normally only the first
area is used. If two connections are used at the same time, then the second
input area can be used.
Slave Function The Scanner SDK Slave function provides two 200-byte input areas (100
words or 1,600 bits) and one 200-byte of output area (100 words or 1,600
bits). The following methods can be used to register the Master in the slave
scan list.
1,2,3... 1. Use functions to register Masters individually or in a group.
2. Register Masters in a group by specifying a parameter file that was created
with the OMRON DeviceNet Configurator.
A slave scan list must be registered in the Scanner SDK for nodes to operate
as Slaves.
Input: 25,200 bytes (= 12,600 words or 201,600 points)
Output: 12,600 bytes (= 6,300 words or 100,800 points)
Input: 200 bytes × 2 (= 100 words × 2 or 1,600 points × 2)
Output: 200 bytes (= 100 words or 1,600 points)
2 max.
Maximum Numbers of I/O Points and Masters
The following table shows the max. number of I/O points and max. number of
Masters allowed by the Scanner SDK’s Slave function.
Item Specification
Max. number of I/O points Input: 200 bytes × 2 (= 100 words × 2 or 1,600 points × 2)
Output: 200 bytes (= 100 words or 1,600 points)
Max. number of Masters 1 Master
Note Two input areas have been provided, but normally only the first area is used. If
two connections are used at the same time, then the second input area can
be used.
1-4-2 Message Communications Function
Explicit Message
Communications
The DeviceNet PCI Board supports explicit message communications.
As a client, the DeviceNet PCI Board can send explicit messages to control or
monitor other nodes in the DeviceNet network when necessary.
As a server, the DeviceNet PCI Board can receive explicit messages from
other nodes. (The requested processing and responses must be handled in
user applications.)
Explicit message communications can be used to freely communicate with
DeviceNet-compatible devices produced by other companies.
5
Scanner SDK Functions Section 1-4
Maximum Number of
Connections
The following table shows maximum number of connections allowed.
Item Specification
Max. number of client connections
Max. number of server connections
63 connections (1 connection per server)
4 connections (1 connection per client)
1-4-3 Maintenance Functions
Read Status Functions The DeviceNet PCI Board can read the following information, including set-
tings and the operating status of the nodes (Master/Slaves) and network.
• Scanner SDK’s DLL version
• DeviceNet PCI Board’s driver version
• Whether or not the DeviceNet PCI Board is installed
• Network status
• Operational status in the network/status in remote I/O communications
• Communications status
• Whether or not each Slave is registered in the scan list
• Each Slave’s device status
Reset Function The DeviceNet PCI Board can be reset (initialized) with a command from the
computer.
Communications Cycle
Time Management
This function can set the communications cycle time (interval between the
exchange of the Slave’s I/O) and read or clear the minimum and maximum
values.
Error Log The DeviceNet PCI Board has an error log function that records information
on errors that occur during operation. The error log can be checked to pinpoint errors for faster error processing and recovery.
PC Watchdog Timer
Management
Remote I/O can be made to stop automatically if the application that controls
the DeviceNet PCI Board stops for some reason. The Board’s PC watchdog
timer is refreshed regularly from the computer (application) to notify the Board
that the application is operating normally.
6
System Configuration Section 1-5
1-5 System Configuration
The following diagram shows the various device connections allowed.
Trunk line
(A cable with terminators
connected on both ends.)
DeviceNet Cable
Slave connected by
the multi-drop method
Slave connected by the T-branch
method using a T-branch Tap
T-branch Tap with
terminator installed
PCI
Board
Drop line
(A cable branching from the
trunk line, 6 m max.)
Input Slave
Output Slave
Output Slave
Input Slave
Note Refer to the following manuals for information on Slaves.
• DRT2 Series DeviceNet Slave Operation Manual (W404)
• C200HW-DRT21, CQM1-DRT21, and DRT1 Series DeviceNet Slave
Operation Manual (W347)
• DRT1-COM and GT1 Series DeviceNet MULTIPLE I/O TERMINAL Operation Manual (W348)
Baud Rate and Distance The following table shows the relationship between the baud rate and commu-
nications distance in the DeviceNet network.
Slave Connection
Methods
Baud rate Maximum network length Drop line
Thick cable Thin cable
500 kbps 100 m max. 100 m max. 6 m max. 39 m max.
250 kbps 250 m max. 78 m max.
125 kbps 500 m max. 156 m max.
length
Slave devices can be connected in two ways. These connection methods can
be combined in the same network.
Method Description
T-branch Method Slaves are connected to a drop line from the trunk line or
branch line created with a T-branch Tap.
Multi-drop Method Slaves are directly connected to the trunk line or the drop line.
Total drop line
length
Note Refer to the DeviceNet Operation Manual (W267) for details on connection
methods and grounding.
7
Specifications Section 1-6
1-6 Specifications
1-6-1 DeviceNet PCI Board General Specifications
Item Specifications
Dimensions 119.9 × 106.7 mm (W × H)
Operating voltage range 5 VDC ± 5% (3.3 VDC is not used.)
Current consumption Internal power supply: 290 mA max. at 5 VDC
Vibration resistance
Shock resistance
Ambient temperature Operating: 0 to 55°C
Humidity 10% to 90% (with no condensation)
Atmosphere Must be free from corrosive gas
Weight 91 g max.
Max. number of Boards 3 Boards/computer max.
Communications power supply: 30 mA max. at 24 VDC
2
10 to 57 Hz, 0.075-mm double amplitude, 57 to 150 Hz, acceleration: 9.8 m/s
directions for 80 minutes each (Time coefficient; 8 minutes × coefficient factor 10 = total time
80 minutes)
DIN Track installation: 2 to 55 Hz, 2.94 m/s2 in X, Y, and Z directions for 20 minutes each
147 m/s2 three times each in X, Y, and Z directions
Storage: –20 to 60°C
in X, Y, and Z
The DeviceNet PCI Board conforms to PCI Local Bus Specification Rev. 2.
1-6-2 DeviceNet Communications Specifications
Item Specification
Communications protocol DeviceNet
Connection forms Multi-drop and T-branch connections can be used for trunk or drop lines.
Terminators must be connected at both ends of the trunk line.
Baud rate 500 kbps, 250 kbps, or 125 kbps (Specified with the SCAN_Online function.)
Communications media Special 5-wire cables (2 signal lines, 2 power lines, 1 shield line)
Communications distances
Communications power supply 11 to 24 VDC, 30 mA (supplied through the communications connector)
Max. number of Slaves 63 Slaves
Communications cycle time (see
note 2)
Error control checks CRC error check, node address duplication check, scan list verification
Cable 5 conductors (two signal wires, two power supply wires, and one shield wire)
500 kbps Network length: 100 m max.
Drop line length: 6 m max.
Total drop line length: 39 m max.
250 kbps Network length: 250 m max. (see note 1)
Drop line length: 6 m max.
Total drop line length: 78 m max.
125 kbps Network length: 500 m max. (see note 1)
Drop line length: 6 m max.
Total drop line length: 156 m max.
Set between 1 and 500 ms with the SCAN_SetScanTimeValue() function.
Note Indicates the max. length when thick cables are used. Reduce the network
length to 100 m max. when using thin cables. When using both thick and thin
cables together, refer to the DeviceNet Operation Manual (W267) for details
on the maximum network length.
8
Specifications Section 1-6
1-6-3 Scanner SDK Communications Specifications
Item Specifications
Supported I/O connections • Bit Strobe
• Polling
•Cyclic
• Change of State (COS)
• Explicit Peer-to-peer Messaging
Communications cycle time (See note.) 2 to 500 ms (Can be specified using API functions.)
Number of server nodes capable of simultaneous
communications as explicit clients
Number of client nodes capable of simultaneous
communications as explicit servers
Data length for explicit messages Client:
Response monitoring time for explicit messages (for
clients)
Retries for explicit messages 0 (Retries must be performed by the user application.)
63 nodes
4 nodes
Explicit message request: 552 bytes
Explicit message response: 552 bytes
Server:
Explicit message request: 552 bytes
Explicit message response: 552 bytes
2 s (default) (Can be specified using API functions.)
Note The communications cycle time is the maximum time from when remote I/O
communications are executed by the Master to a Slave until remote I/O communications are executed again for the same Slave.
Minimum System
Requirements
Hardware Requirements
IBM PC/AT or Compatible
• At least one PCI bus slot (PCI bus Rev. 2.0 or later)
• 5 MB min. free hard disk space
(plus additional space for the user program)
• One CD-ROM drive is required to install the software.
• VGA or better display functions.
The processor, memory capacity, and other specifications not listed above
should conform to the recommendations for the operating system used.
OS
Microsoft Windows 95, 98, Me, NT 4.0, 2000, or XP.
Windows 3.1 and Windows NT 3.5 are not supported.
1-6-4 Development Environment
Recommended
Development Environment
Other Development
Environments
Microsoft Visual C++ (Ver. 6.0 or later.)
• Microsoft Visual Basic
Some functions are limited. Refer to Precautions when Using Other
Development Environments under 3-1 Application Development Environments for details.
• Borland C++ Builder
Refer to Refer to Precautions when Using Other Development Environ-
ments under 3-1 Application Development Environments for details.
9
Board Components Section 1-7
1-6-5 Dimensions
The following diagram shows the dimensions of the DeviceNet PCI Board.
(The height of components on the Board is within specifications for a single
PCI slot.)
21.6 mm
14.7 mm
106.7 mm
126.4 mm
132.3 mm
119.9 mm
1-7 Board Components
LED indicators (MS and NS)
These are the DeviceNet MS
(module status) and NS (network status) indicators.
Board ID switch
When two or more DeviceNet PCI
Boards are installed in a computer,
the computer uses the board ID
settings to distinguish the Boards
from each other. Set unique decimal board IDs between 0 and 7.
(The height of the component surface
will fit in one PCI bus slot.)
Communications connector
Connects the Board to the DeviceNet
communications cable.
PCI interface
Connects the Board to the
computer's PCI slot.
10
Preparation for Operation Section 1-8
LED Indicators The following table explains the operation of the LED indicators.
Indicator status Meaning
MS NS
OFF OFF Boot program initialization is in progress.
Flashing green OFF Scanner firmware initialization is in progress.
Lit green OFF Waiting for online request.
Lit green Flashing green A connection was established and I/O communi-
cations are in progress.
Waiting for a connection from the Master.
Lit green Lit green I/O communications or message communications
Board ID When two or more DeviceNet PCI Boards are installed in a computer, the
computer uses the board ID settings to distinguish the Boards from each
other. Specify the board ID in API functions to identify the desired board.
Set the board ID in decimal as shown in the following diagram. The allowed
setting range is 0 to 7. (The factory setting is 0.)
Up to 3 DeviceNet PCI Boards can be installed in one computer.
are in progress.
Note Any board ID from 0 to 7 can be set, as long as the ID is not set on another
DeviceNet PCI Board in the computer. (It is physically possible to set board
IDs 8 and 9, but the Board cannot be used properly with these settings.)
1-8 Preparation for Operation
Hardware Settings If more than one DeviceNet PCI Board is being installed in one computer, set
the board IDs on the Boards’ rotary switches so that the different Boards can
be distinguished from one another. Refer to 2-2 Installing the Board in the
Computer for details.
Always set the rotary switches before turning ON the computer.
Installation on Computer Install the Board in the computer. Refer to 2-2 Installing the Board in the Com-
puter for details.
Software Installation Install the DeviceNet PCI Board driver and software required to use the Board
from the computer. Refer to 2-3 Installing the Drivers and 2-4 Installing the
Scanner SDK Software for details.
Writing the Program Write the programs (user applications) that make software settings and con-
trol the Board. Refer to SECTION 3 Using API Functions through SECTION 7
Error Processing for details.
Reference Information Refer to 2-5 DeviceNet Connections for information on communications cable
connections.
Refer to the DeviceNet Operation Manual (W267) for information on wiring
DeviceNet networks.
Refer to the DeviceNet Slave Operation Manuals (W404 and W347) and the
DeviceNet MULTIPLE I/O TERMINAL Operation Manual (W348) for information on Slaves.
11
Preparation for Operation Section 1-8
12
SECTION 2
Software Installation
This section explains how to install the DeviceNet PCI Board in a computer, how to install the software, and how to connect
the communications cables.
2-1 Installation Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
2-2 Installing the Board in the Computer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
2-3 Installing the Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
2-4 Installing the Scanner SDK Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
2-5 DeviceNet Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
2-5-1 Attaching Connectors to the DeviceNet Cable . . . . . . . . . . . . . . . . . 29
2-5-2 Connecting Communications Cables . . . . . . . . . . . . . . . . . . . . . . . . 31
13
Loading...