ICP DAS USA DB25, DN-3000, 100-700 PLCS User Manual
DN-3000
AN INTELLIGENT
MULTIPLE-FUNCTION COMMUNICATIONS
INTERFACE UNIT FOR DEVICENET
U
ICP PANEL-TEC
Post Office Box 2394
Huntsville, Alabama 35804
(205) 534-8132
ser Manual
Warranty & Notices
WARRANTY
ICP PANEL-TEC, INC. warrants that all equipment purchased hereunder is warranted on a “RETURN
TO FACTORY” basis against all defects in workmanship and materials under normal and proper use and
service in its unmodified condition for a period of one (1) year from the date of initial shipment. ICP
PANEL-TEC, INC. sole obligation under this warranty shall be limited to furnishing parts and labor to
remedy such defects; either, at the option of ICP PANEL-TEC, INC., by replacing or repairing any
defective parts which are returned to ICP PANEL-TEC, INC. factory or by making available at a
purchaser designated facility a repaired or replaced part. All replaced equipment shall become the
property of ICP PANEL-TEC, INC. The cost of freight to and from ICP PANEL-TEC, INC. will be
borne by the purchaser. If ICP PANEL-TEC, INC. determines that the equipment returned to it for
warranty correction is not defective, as herein defined, Purchaser shall pay ICP PANEL-TEC, INC., all
costs of service, parts, handling and transportation.
IMPORTANT NOTICES
By accepting and using the DN-3000 (s) CONFIGURATION EDITOR SOFTWARE and information
proprietary to ICP PANEL-TEC, INC. USA and/or its Licensers, you agree that such software and
information (Software) constitutes valuable trade secrets and proprietary information of ICP PANEL-
TEC, INC. and/or its Licenses and that you hold the software in confidence and secrecy and shall not, in
whole or part, copy or disclose to any third party or make any unauthorized use thereof. Authorized use
shall be limited to the DN-3000 (s) upon which the Software is initially supplied. You further agree that
this agreement shall insure to the benefit of ICP PANEL-TEC, INC. and any third party holding any
right, title, or interest in the software, or any software and information from which it is derived, and their
respective transferees, successors, and assigns, and that any subsequent transferee of the unit herein
decried shall be obligated to the same terms of this agreement.
This document is based on information available at the time of its publication. While efforts have been
made to render accuracy to its content, the information contained herein does not purport to cover all
details or variations in hardware or software, nor to provide for every possible contingency in connection
with installation, operation, and maintenance.
Features may be decried herein which are not present in all hardware and software systems. ICP
PANEL-TEC, INC. assumes no obligation of notice to holders of this document with respect to changes
subsequently made.
ICP PANEL-TEC, INC. makes no representation or warranty expressed, implied, or statutory, with
respect to, and assumes no responsibility for accuracy, completeness, sufficiency or usefulness of the
information contained herein.
In no event shall ICP PANEL-TEC, INC. be responsible or liable for indirect or consequential damages
that may result from installation or use of this equipment.
(C) 1997 ICP PANEL-TEC, INC.
ALL RIGHTS RESERVED
Post Office Box 2394
Huntsville, Al. 35804-2394
i
Table of Contents
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Software Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Software Start-Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Creating Project Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Project Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
DeviceNet to PLCs or Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Device Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Example Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Configuring Port #1 (DeviceNet) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Configuring Port #2 (PLCs or Devices) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Configuring Port #3 (Passthrough) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
I/O Data Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
DeviceNet to Motor Drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Device Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Example Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Configuring Port #1 (DeviceNet) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Configuring Port #2 (Motor Drives) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
I/O Data Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Upper Link Configuration (Mitsubishi Drives Only) . . . . . . . . . . . . . . . . . . . . . . 38
Exception Table (Mitsubishi Drives Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Transferring Project Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Options Settings
Setting the Project Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Selecting the Communications Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Setting the Printer Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Load Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Save Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Default Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Technical Information
Power Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
DIP Switch Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
LED Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
ii
Table of Contents
Application Notes – PLCs and Devices
Allen Bradley PLCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
GE Fanuc PLCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Idec PLCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Koyo (PLC Direct and TI) PLCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Mitsubishi PLCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Modicon PLCs (and Modbus Devices) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Omron PLCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Siemens S7-200 PLCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Square D PLCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
TI505 Series PLCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Toshiba PLCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Westinghouse PLCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Application Notes – Motor Drives
Baldor Motor Drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Mitsubishi Motor Drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Woods Motor Drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Yaskawa Motor Drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Cable Diagrams
Configuration Cable Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
PLC and Device Cable Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Motor Drive Cable Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
DeviceNet Cable Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
iii
Introduction
INTRODUCTION
The DN-3000 is an intelligent, multiple-function DeviceNet Data Transfer Unit designed for use within
the harsh industrial environment.
Using the DN-3000 Configuration Editor Software program, the DN-3000 can be programmed to run
either of the two (2) following application types:
1) DEVICENET TO PLCS OR DEVICES Allows a DeviceNet Host to read or write data registers in
one or more PLCs or Devices that use the same protocol. One of the DN-3000’s three ports can be
used as a pass-through port in which all messages received are simply passed through to one of the
connected PLCs/Devices (if supported for that PLC/Device protocol), allowing PLC programming
software, a third party’s intelligent (MMI) Man-Machine Interface terminal or a SCADA software
program to be “connected” to the same port on the PLCs/Devices used by the DN-3000.
2) DEVICENET TO MOTOR DRIVES Allows a DeviceNet Host to control and/or monitor parameters
in up to 32 Motor Drives.
This manual is presented in two sections. Each section deals with the configuration requirements for each
of the above applications: DeviceNet to PLCs and DeviceNet to Motor Drives.
Please note that the application type is selected when a new project is created using the DN-3000
configuration software and may not be changed after the project is created.
1
Software Installation
GENERAL INFORMATION
The Panel-Tec DN3000 Configuration Editor Software Program is designed to operate on an IBM or
compatible computer running MS-DOS 3.3 or higher.
While the Configuration Editor Software Program will run under “WINDOWS 3.1” in most
configurations, it is not recommended. As of this date, no problems have been reported running the
software under “WINDOWS 95”.
The configuration editor software will default during start-up to using “COMM 1” unless changed using
the OPTIONS menu. This may conflict with a mouse driver program and prevent up/down loading
configuration information to the DN-3000 interface unit.
INSTALLATION
Place the supplied program disk into drive “A” (or B).
At the MS-DOS prompt, C:> type in A: (or B:) and then press the “ENTER” key.
When the “A” (or B) prompt appears, A:> type in “INSTALL” and press the “ENTER” key.
The following message will appear;
DN3000 Configuration Editor Installation Program
Enter the drive where the editor is to be installed ==>
Enter “C” (or any other hard drive you care to use), then press the “ENTER” key.
A new message will appear:
Enter the sub-directory on drive C to install the editor into ==>
Suggested directory name is: DN3000
The next message to appear before the installation is started is:
The Editor will be installed from “A” to “C:\DN3000”
Is this correct (Y/N) ?
If the above information is correct, push the “Y” key, then the “ENTER” key and the software will be
installed. The last message to appear will be:
Installation Complete.
Enter “DN3000” to run the configuration Editor
C:\DN3000>
2
Software Information
SOFTWARE START-UP
To start the DN-3000 Configuration Editor program. First start your computer and at the MS-DOS
prompt; C:> type in “CD\DN3000” (to change the directory) then press the ENTER key. At the next
MS-DOS prompt; C:\DN3000>,
Configuration Editor Software Program.
Upon starting of the configuration software program, the first screen to appear will be the “Support
Information Page”, shown below.
type in “DN3000” and press the ENTER key to start the
After pressing the computer’s ENTER key, the support information page will disappear. Use the
computer’s LEFT/RIGHT arrow keys and move the highlighted bar (very top of the screen) between the
four (4) main system selection headers. To select any one of these main selection headers, place the
highlight bar around that desired heading and then press the computer’s ENTER key. Below is a brief
description of the main project header and each internal subheading; NOTE: These brief descriptions
listed are as the system starts without any projects opened or new projects created.
Selecting PROJECT opens a menu with the following options:
OPEN allows you to open any saved project file.
NEW allows you to create a new project file.
DOS SHELL allows you to exit to MS-DOS without closing the DN-3000 Configuration Editor
Program and return to the Configuration Editor Program by typing in EXIT and then pressing the
ENTER key.
QUIT allows you to exit the Configuration Editor Program.
3
Creating Project Files
CREATING A PROJECT FILE
To create a project file, move the highlighted bar to the “PROJECT” heading and press the computer’s
ENTER key. When the menu appears move the highlight bar to the “NEW” sub-heading and press
“PROJECT”
Menu
the computer’s ENTER key. At the “Project Name” entry area, type in your file name.
Enter your
Project’s
File Name
After entering in the project’s file name, press the ENTER key. The highlighted bar now moves to
“Project Type”. Press ENTER to open the “Project Type” window (default setting is “DeviceNet to
PLCs or Devices”). Move the highlight bar by pressing the DOWN arrow key to the project type you
wish to configure and then press the ENTER key. The software enters this selection and returns to the
“PROJECT” menu.
4
Creating Project Files
“PROJECT
TYPE”
List
PROJECT TYPES
DeviceNet to PLCs or Devices allows a DeviceNet Host to read and write registers in up to 32
PLCs or devices.
DeviceNet to Motor Drives allows a DeviceNet Host to control and/or monitor up to 32 supported
Motor Drives.
5
Creating Project Files
When the system returns to the “PROJECT’ menu, notice the additional sub-headings that were added to
the “PROJECT” menu and are now available for you to use. A brief description of each of these new
sub-headings are listed below:
Additional PROJECT
Menu Sub-Headings
CLOSE allows you to close a project file. More than one project file can be open at any time.
VIEW allows you to view; the project file name, project file type, and the current selections for each
of the DN-3000’s serial ports.
SAVE allows you to save the current project file.
SAVE AS allows to save the current open project file under a different file name.
SWITCH TO allows you to switch between the opened project files. (Multiple files can be open.)
PRINT allows you to print the project file’s configuration information.
GENERATE EDS FILE allows you to generate an EDS file for the current Project. The EDS file is
used to tell a DeviceNet configuration tool information about the DN-3000 and I/O sizes. If you are
using a DeviceNet configuration tool to set up your DeviceNet network, you should generate a new
EDS file for each project.
Use the RIGHT arrow key to move the highlight bar from the top “PROJECT” header to the top
“EDIT” header to proceed with editing the configuration information stored in the project file.
6
DeviceNet to PLCs or Devices
DEVICENET TO PLCS OR DEVICES
The ”DeviceNet to Motor Drives” application allows a DeviceNet Host device to access data registers in
up to 32 serial PLCs or Devices via Explicit Messages and/or I/O Data.
Explicit Messages allows the DeviceNet Host to issue requests to the DN-3000 to read or write specific
PLC/Device data registers. The DN-3000 converts those requests into serial communications requests in
the selected serial PLC’s or Device’s protocol.
I/O Data allows the DN-3000 to exchange a fixed set of PLC/Device data registers between a DeviceNet
Host and serial PLCs or Devices. The DN-3000 writes Output Data received from the DeviceNet Host to
fixed PLC/Device data registers (see Output Data Table in this section) in the connected serial PLCs or
Devices. Input Data is read from fixed PLC/Device data registers in the connected serial PLCs or
Devices and sent to the DeviceNet Host (see Input Data Table in this section).
Important Note: The DN-3000 can be used to access only data registers in the selected PLCs or
Devices. See the Application Notes for the selected PLC/Device for more information.
DEVICE PROFILE
The DN-3000 is based on the “PLC/Device Gateway” Device Profile, a vendor-specific extension of the
“Communications Adapter” Device Profile (described in the “ODVA DeviceNet Specifications”). This
Device Profile introduces two new vendor-specific Objects: the “PLC/Device Interface Object” and the
“PLC/Device Command Object”. Documentation on this profile and these objects are available from
Panel-Tec, Inc.
The DN-3000 is a Group 2 Only Server utilizing the Predifined Master/Slave Connection Set (as
described in the (ODVA DeviceNet Specifications”). It supports both Explicit Messaging and Polled,
Change-of-State (COS) and Cyclic I/O connections to a DeviceNet Host. It does not support Bit-Strobed
I/O connections.
To access register data via Explicit Messaging, the DeviceNet Host must issue an explicit Get_Member or
Set_Member request to the desired “PLC/Device Interface Object” Instance (based on PLC/Device
Address) of the DN-3000.
If Polled, COS and/or Cyclic I/O connections are to be used, you must first set up the I/O
configuration of the DN-3000 with the DN3000 Configuration Editor software. See I/O Data
Configuration in this section.
7
DeviceNet to PLCs or Devices
EXAMPLE APPLICATIONS
DeviceNet Host to Serial PLC with Pass-Through Connection
PLC # 1
PLC # 2
PLC # 3
NOTE: Multiple PLCs/Devices can be connected to Port 2 of a DN-3000 if:
1) All PLCs/Devices use the same protocol.
2) Each PLC/Device can be internally addressed with a network address.
3) Each PLC/Device can communicate on a RS-485/422 multi-drop communications network;
-OR- RS232 to RS485 converters (1 per PLC or Device) are used;
-OR- a 3rd Party multi-port communications expansion module (Port Expander) is used.
Supported PLC or Device
2 3
DN-3000
DeviceNet Host
DeviceNet Host to Multi-Dropped Serial PLCs
RS-422/485
Multi-Drop
Network
2 3
DN-3000
PLC # 4 PLC # 5 PLC # 6 PLC # 7
Programming
Software
(if supported)
DeviceNet Host
Up to 32
PLCs
may be
connected
8
DeviceNet to PLCs or Devices
Multiple DN-3000s with Different PLC or Device Types
DeviceNet Host
2 3 2 3 2 3 2 3 2 3
DN-3000
# 1
PLC # 1
Brand A
PLC # 2
Brand A
NOTE:
1) Each DN-3000 can support up to 32 PLCs/Devices (if they are network addressable internally).
2) The DeviceNet Host can address a maximum of 63 DN-3000 units.
3) Multiple Brands of PLCs or Devices may be addressed by the DeviceNet Host by using multiple
DN-3000s, but only one PLC/Device Protocol may be used on a single DN-3000 unit.
4) If multiple DN-3000s are to be used, each DN-3000 must be configured with a unique node
address (MAC ID) on the DeviceNet network.
DN-3000
# 2
PLC # 1
Brand S
RS-422/485 Multiple-Drop Networks
DN-3000
# 3
PLC # 1
Brand O
PLC # 2
Brand O
DN-3000
# 4
PLC # 1
Brand M
DN-3000
# 5
PLC # 1
Brand I
PLC # 2
Brand I
PLC # 3
Brand I
9
DeviceNet to PLCs or Devices
CONFIGURING PORT #1, (DEVICENET)
With the highlight bar around the “PROJECT” header use the RIGHT arrow key and move the highlight
bar to the “EDIT” header This action will close the “PROJECT” menu and open the “EDIT” menu.
DeviceNet to
PLCs or Devices
EDIT Menu
Move the highlight bar to the “Port 1 (DeviceNet)” sub-heading and press the ENTER key to open the
DeviceNet configuration screen.
10
DeviceNet to PLCs or Devices
MAC ID of DN3000
The MAC ID of the DN-3000 is its node address on a DeviceNet Network. The MAC ID of a DN-3000
can range from 0 to 63. Type the desired value in the field and press ENTER.
Baud Rate
Baud Rate determines the rate at which the DN-3000 exchanges data on a DeviceNet network. The Baud
Rate setting must be the same for all devices on the DeviceNet network. The DN-3000 supports baud
rates of 125, 250 and 500 kbps. The dot between the brackets indicates the current selection. Use the
UP/DOWN arrow keys and the SPACEBAR to select the desired baud rate.
11
DeviceNet to PLCs or Devices
CONFIGURING PORT #2 (PLCS OR DEVICES)
When the highlight bar is around the “Port 2 (PLCs/Devices)” sub-heading, press the ENTER key. This
opens a window which allows you to select the type of PLCs or devices connected to this port and check
all of the communication settings.
PORT # 2
PLC
Configuration
Window
PLC/Device Protocol
The window for PORT # 2 Configuration will open with the highlighted bar at the “PLC/DEVICE
PROTOCOL” selection heading. If the displayed Protocol is not the one wanted, simply press the
ENTER key and a smaller window will appear.
PLC/Device
Protocol
Selection
Window
12
DeviceNet to PLCs or Devices
Use your computer’s UP/DOWN arrow keys to move through the PLC/Device Protocol List. Place the
highlight bar on the desired Protocol and press the ENTER key. The software will enter this selection
and automatically close the Protocol selection window. After the selection window closes, you will need
to check the communications setting for the selected Protocol, making changes as necessary.
2 Wire RS422 or RS485 Communications
This box will only need to be checked if the communications with your PLC/Device is a 2-wire RS485 or
RS422 interface. When 2-wire communications are being used, RTS must be looped back to CTS on the
DN-3000 side of the cable. This can be done on the RS232 side by looping pins 4 and 5 or on the
RS422/485 side by looping 16 to 18 and 17 to 19.
DN3000 Address
Some PLC/Device protocols require each PLC or Device on a network to be assigned a unique address.
The DN3000 Address is the address assigned to the DN-3000 on the PLC/Device network.
Communications Settings
The communications settings are automatically set to the default values for each type of PLC/Device
when its Protocol is first selected. Before changing any of these settings, consult your PLC/Device
manual for the correct settings. To move between the communications settings, press the TAB or
ENTER keys. To select a setting, use the UP/DOWN arrow key to move to the desired setting and press
the SPACE BAR to enter or change your selection.
RTS Control (Request to Send Control)
RTS Control selection is an option provided for modems or for PLCs/Devices that require RTS to be
active only while the DN-3000 is transmitting to the PLC. If RTS/CTS is selected, the DN-3000 will
activate RTS and wait until CTS is active before transmitting to the PLC. If RTS Delay is selected, the
DN-3000 will activate RTS and wait for the specified delay time to pass before transmitting to the PLC.
Response Time-Out
The Response Time-Out tells the DN-3000 how long to wait after transmitting a request to a PLC/Device
if no response has been received from the PLC/Device. After this amount of time (specified in
milliseconds) passes with no response being received, the DN-3000 will assume that no response is
coming and will retry the request.
To save the configuration for Port #1, press the “Alt+S” keys or the F10 function key once and a small
window appears stating the information was saved. Press the ENTER key, then the ESC key to return to
the “EDIT” window.
13
DeviceNet to PLCs or Devices
CONFIGURING PORT # 3 (PASSTHROUGH)
Not all PLC/Device protocols allow for the pass-through communications. If your selected Protocol on
Port 2 is capable of pass-through communications, the “Port 3 (Passthrough)” header within the “EDIT”
menu will be black (if light gray, the PLC does not support Pass-Through communications). Place the
Highlight bar around the “Port 3 (Passthrough)” header and press the ENTER key to open this screen.
(See drawing below)
A Selected PLC or
Device Protocol
that supports
Pass-Through
Communications
For descriptions of all entry fields on this screen except for the Intermessage Time-Out, refer to
CONFIGURING PORT #2 (PLCs or Devices) in this section.
Intermessage Time-Out
The DN-3000 uses the Intermessage Time-Out to determine when a complete message has been received
on the PassThrough port. Once the first character of a message has been received, if the amount of time
specified by the Intermessage Time-Out passes with no additional characters being received, the DN-3000
will consider the message to be complete and process it.
Check over the communications settings, making corrections as needed, and save this information by
pressing the letter “S” or the F10 function key(s) once. A small window will appear stating the
information was saved. Press the ENTER key, then the ESC key to return to the “EDIT” menu.
14
DeviceNet to PLCs or Devices
I/O DATA CONFIGURATION
Using the DOWN arrow key, move the highlight bar to the “I/O Data Configuration” sub-heading
within the “EDIT” menu and press the ENTER key. This action opens the I/O Data Configuration setup
screen to allow you to set up the I/O data parameters for your project. You should have some idea of how
you want your I/O set up before selecting this option.
Use I/O Data
If your project requires the use one or more I/O connections (Polled, Change-Of-State (COS) or Cyclic
I/O) for data exchange between the DN-3000 and a DeviceNet host, you should select this option by
pressing the SPACEBAR, ‘X’ or ‘Y’ key on your keyboard. When you select “Use I/O Data”, the other
available I/O options will appear on the screen.
15
DeviceNet to PLCs or Devices
The DN-3000 supports up to a total of 64 bytes (32 words) of combined Input and Output data. Each
word (2 bytes) of Input or Output data can be configured to exchange data with any one valid data register
in any one of the PLCs/Devices connected to port 2 of the DN-3000 (see “CONFIGURING PORT 2” for
PLC/Device Protocol and communication parameters).
Use Command Block
In some projects it may be necessary to be able to access more than just the 32 PLC/Device registers that
can be configured in the Input and Output data. A Command Block reserves the first 4 words of Output
data for commands, and the first 4 words of Input data for command results. This reduces your total
number of words that can be used for register data to 24 words, but adds flexibility by allowing your
DeviceNet Host to issue commands to the DN-3000 to access any valid data registers in any PLC or
Device connected to port 2 of the DN-3000. Commands are issued by moving a command code,
PLC/Device address, file number (Allen-Bradley PLCs only), register number, and data into the first 4
words of the Output data (see “COMMAND BLOCK”).
Use Diagnostics
Diagnostics allows the DeviceNet Host to monitor PLC/Device connections to the DN-3000. The first
word of the Input data following the Command Result Block (if any) will be reserved for Diagnostics if
this option is selected. The DN-3000 keeps track of the connection status with each PLC/Device address
(0-255). Whenever an attempt to communicate with a PLC/Device is successful, the connection status for
that PLC/Device is set to ‘0’. Whenever an attempt to communicate with a PLC/Device is unsuccessful,
the connection status for that PLC/Device is set to ‘1’. Of course, returning 256 status bits would require
16 words of Input data (half of the available I/O data). Instead, only 16 bits (1 word) of are returned.
Each of the 16 bits of the Diagnostics word represents the status of 16 PLC/Device addresses, as follows:
bit 0 represents PLC/Device addresses 0, 16, 32, 48, 64, etc.; bit 1 represents PLC/Device addresses 1, 17,
33, 49, 65, etc.; and so forth. If the status of any of the PLC/Device addresses represented by a bit is ‘1’,
that bit will contain a ‘1’, otherwise, that bit will contain a ‘0’. Note that the status of a PLC/Device is set
to ‘1’ only if the DN-3000 attempts to communicate with that PLC/Device and that attempt is
unsuccessful.
Output Data Size
This determines the number of words of Output data that will be used in your project. Output data is data
that is output from your DeviceNet Host to the DN-3000 (commands, and register data to be written to
PLCs/Devices). This is also known as the Consumed I/O Data of the DN-3000. If a Command Block is
used, it will automatically reserve 4 words of Output data. The combined size of the Input and Output
data must not exceed 32 words.
Output Data
Pressing the Output Data button brings up a window allowing you to edit the configuration of the Output
data in your project. You can press the Output Data button by clicking on it with your mouse, or moving
the focus to the button with the arrow keys and pressing the SPACEBAR. See “OUTPUT DATA
TABLE”.
16
DeviceNet to PLCs or Devices
Input Data Size
This determines the number of words of Input data that will be used in your project. Input data is data
that is input to your DeviceNet Host from the DN-3000 (command results, diagnostics information, and
register data read from PLCs/Devices). This is also known as the Produced I/O Data of the DN-3000. If
a Command Block is used, it will automatically reserve 4 words of Input data for command results.
Similarly, if Diagnostics is used, it will automatically reserve 1 word of Input data. The combined size of
Input and Output data must not exceed 32 words.
Input Data
Pressing the Input Data button brings up a window allowing you to edit the configuration of the Input
data in your project. You can press the Input Data button by clicking on it with your mouse, or moving
the focus to the button with the arrow keys and pressing the SPACEBAR. See “INPUT DATA TABLE”.
17
DeviceNet to PLCs or Devices
OUTPUT DATA TABLE
Within the “I/O Data Configuration” screen, use the DOWN arrow key to move the focus to the Output
Data button and press the ENTER key. This action opens the Output Data Table setup screen to allow
you to set up the PLC/Device registers to be mapped to each word of Output data.
Output data is data received by the DN-3000 from the DeviceNet Host to be written to PLC/Device
registers. Each word of Output data (except those reserved for the Command Block) can be mapped to
specific PLC/Device registers. Output data is only written to registers when that data changes.
Use the UP/DOWN arrow keys to scroll through the list of Output data words until the highlight bar is
over the Output word you wish to edit, and press ENTER. A window will open allowing you to edit the
PLC/Device Address, File Number (Allen-Bradley PLCs only) and Register Number mapped to that
Output word.
18
DeviceNet to PLCs or Devices
Use Output Word xx
If you want to map this word of Output data to a PLC/Device register, select this option. If this option is
not selected, any data appearing in this Output word will be ignored.
PLC/Device Address
This is the Address of the PLC/Device mapped to this word of Output data. The PLC/Device Address
must be in the range 0 to 255.
File Number (Allen-Bradley PLCs only)
This is the File Number of the register in the PLC mapped to this word of Output data.
Register Number
This is the Register Number of the PLC/Device mapped to this word of Output data. Whenever the value
in this Output word changes, the DN-3000 will write that value to the register specified by the
PLC/Device Address, File Number and Register Number.
19
Loading...