Horner APG HE800DNS600, HEDNS600 User Manual
MAN0577-03-En
HE800DNM650 & HE800DNS600
DeviceNet Modules
User Manual for
HE800DNM650/HEDNM650 &
HE800DNS600/HEDNS600
DeviceNet
Master and Slave SmartStack™ Modules
Page 1 of 98
EO 09-0009
MAN0577-03-En
HE800DNM650 & HE800DNS600
DeviceNet Modules
PREFACE
This manual explains how to use the Horner APG HSyCon software product.
Copyright © 2001 Horner APG, LLC., 640 North Sherman Drive, Indianapolis, Indiana 46201-3899. All rights
reserved. No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval
system, or translated into any language or computer language, in any form by any means, electronic,
mechanical, magnetic, optical, chemical, manual or otherwise, without the prior agreement and written
permission of Horner APG, LLC.
Information in this document is subject to change without notice and does not represent a commitment on
the part of Horner APG, LLC.
Windows 95, Windows 98, and Windows NT are registered trademarks of Microsoft
Corporation.
DeviceNet is a trademark of Open DeviceNet Vendors Association (ODVA).
Profibus is a trademark of Siemens.
Cscape, CsCAN, and SmartStack are trademarks of Horner APG, LLC.
For user manual updates and technical support contact :
Horner APG
Technical Support (317) 916-4274 Technical Support +353-21-4321266
web-site www.horner-apg.com. web-site www.horner-apg.com
(USA) Horner APG (Europe)
LIMITED WARRANTY AND LIMITATION OF LIABILITY
Horner APG, LLC. ("HE-APG") warrants to the original purchaser that the Operator Station manufactured by HE is free from defects
in material and workmanship under normal use and service. The obligation of HE-APG under this warranty shall be limited to the
repair or exchange of any part or parts which may prove defective under normal use and service within two (2) years from the date
of manufacture or eighteen (18) months from the date of installation by the original purchaser whichever occurs first, such defect to
be disclosed to the satisfaction of HE-APG after examination by HE-APG of the allegedly defective part or parts. THIS WARRANTY
IS EXPRESSLY IN LIEU OF ALL OTHER WARRANTIES EXPRESSED OR IMPLIED INCLUDING THE WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR USE AND OF ALL OTHER OBLIGATIONS OR LIABILITIES AND HE-APG NEITHER
ASSUMES, NOR AUTHORIZES ANY OTHER PERSON TO ASSUME FOR HE-APG, ANY OTHER LIABILITY IN CONNECTION
WITH THE SALE OF THE Operator Station. THIS WARRANTY SHALL NOT APPLY TO THE Operator Station OR ANY PART
THEREOF WHICH HAS BEEN SUBJECT TO ACCIDENT, NEGLIGENCE, ALTERATION, ABUSE, OR MISUSE. HE MAKES NO
WARRANTY WHATSOEVER IN RESPECT TO ACCESSORIES OR PARTS NOT SUPPLIED BY HE. THE TERM "ORIGINAL
PURCHASER", AS USED IN THIS WARRANTY, SHALL BE DEEMED TO MEAN THAT PERSON FOR WHOM THE Operator
Station IS ORIGINALLY INSTALLED. THIS WARRANTY SHALL APPLY ONLY WITHIN THE BOUNDARIES OF THE
CONTINENTAL UNITED STATES.
In no event, whether as a result of breach of contract, warranty, tort (including negligence) or otherwise, shall HE-APG or its
suppliers be liable of any special, consequential, incidental or penal damages including, but not limited to, loss of profit or revenues,
loss of use of the products or any associated equipment, damage to associated equipment, cost of capital, cost of substitute
products, facilities, services or replacement power, down time costs, or claims of original purchaser's customers for such damages.
Page 2 of 98
EO 09-0009
MAN0577-03-En
HE800DNM650 & HE800DNS600
DeviceNet Modules
List of Revisions
Index Date Version Chapter Revision
21-May-04 01 All Initial Release
18-Mar-07 02 3 Added Cscape Configuration Section
10-Jul-08 03 9 Added Explicit Messaging chapter
Page 3 of 98
EO 09-0009
MAN0577-03-En
HE800DNM650 & HE800DNS600
DeviceNet Modules
TABLE OF CONTENTS
PREFACE ..................................................................................................................................................... 2
LIMITED WARRANTY AND LIMITATION OF LIABILITY ............................................................................. 2
CHAPTER 1: INTRODUCTION .................................................................................................................... 7
1.1 Scope ........................................................................................................................................... 7
1.2 Introduction ................................................................................................................................... 7
1.3 Installing and Removing a SmartStack Module ........................................................................... 8
1.4 Installing SmartStack Modules ..................................................................................................... 8
1.5 Removing SmartStack Modules ................................................................................................... 8
1.6 Status LED definitions .................................................................................................................. 9
1.7 Main Functions ............................................................................................................................. 9
CHAPTER 2: INSTALLATION .................................................................................................................... 10
2.1 System Requirments .................................................................................................................. 10
2.2 System Installation ..................................................................................................................... 10
2.3 Installation of the System Configurator HSyCon ........................................................................ 11
CHAPTER 3: GETTING STARTED – CSCAPE CONFIGURATION .......................................................... 15
3.1 Scope ......................................................................................................................................... 15
3.2 Configuring Cscape. ................................................................................................................... 15
3.3 Configuring a SmartStack DeviceNet Master with any DeviceNet Slave .................................. 19
3.4 Configuring a SmartStack DeviceNet Slave with any DeviceNet Master .................................. 19
3.5 Configuring a Horner DeviceNet Master with a Horner DeviceNet Slave .................................. 21
CHAPTER 4: CONFIGURATION OF DEVICENET WITH HSYCON ......................................................... 22
4.1 Setting up the DEVICENET Configuration ................................................................................. 22
4.2 EDS Files (Electronic Data Sheet Files) Introduction ................................................................ 22
4.3 EDS Files and HSyCon .............................................................................................................. 23
4.4 Insert Master .............................................................................................................................. 23
4.5 Insert Device (Slave) .................................................................................................................. 24
4.6 Replace Slave ............................................................................................................................ 25
4.7 Device Configuration .................................................................................................................. 25
4.8 MAC ID (Device network address) ............................................................................................. 26
4.9 Actual chosen IO Connection ..................................................................................................... 27
4.10 Connection Object Instance Attributes ....................................................................................... 28
4.11 UCMM Check ............................................................................................................................. 28
4.12 Fragmented Timeout .................................................................................................................. 28
4.13 Parameter Data .......................................................................................................................... 28
4.14 Process Data Configuration ....................................................................................................... 30
CHAPTER 5: SETTINGS ............................................................................................................................ 32
5.1 Device Assignment .................................................................................................................... 32
5.2 COM Serial Driver ...................................................................................................................... 32
5.3 Bus Parameter ........................................................................................................................... 34
5.4 DeviceNet Master ....................................................................................................................... 34
5.5 Device (Slave) ............................................................................................................................ 38
5.6 Project Information ..................................................................................................................... 39
5.7 Path ............................................................................................................................................ 39
5.8 Language ................................................................................................................................... 39
5.9 Start Options .............................................................................................................................. 40
CHAPTER 6: ONLINE FUNCTIONS .......................................................................................................... 42
6.1. Introduction ................................................................................................................................. 42
6.2. Online to the Module .................................................................................................................. 42
6.3. Downloading the Configuration .................................................................................................. 42
6.4. Firmware Download ................................................................................................................... 43
6.5. Firmware / Reset ........................................................................................................................ 43
6.6. Device Info ................................................................................................................................. 44
Page 4 of 98
EO 09-0009
MAN0577-03-En
HE800DNM650 & HE800DNS600
DeviceNet Modules
6.7. Automatic Network Scan ............................................................................................................ 45
6.8. Start/Stop Communication ......................................................................................................... 48
6.9. Diagnostic Functions .................................................................................................................. 48
6.10. Live List ...................................................................................................................................... 49
6.11. Change MAC-ID ......................................................................................................................... 49
6.12. Debug Mode ............................................................................................................................... 49
6.13. The Debug Window .................................................................................................................... 50
6.14. Device Diagnostic ...................................................................................................................... 50
6.15. Global State Field ....................................................................................................................... 52
6.16. Device Diagnostic ...................................................................................................................... 54
6.17. Extended Device Diagnostic ...................................................................................................... 55
6.18. Extended Device Diagnostic Master .......................................................................................... 55
6.19. Extended Device Diagnostic Device (Slave) .............................................................................. 56
6.20. User Data Transfer ..................................................................................................................... 56
6.21. I/O Monitor .................................................................................................................................. 57
6.22. I/O Watch ................................................................................................................................... 57
6.23. DeviceNet Services .................................................................................................................... 59
6.24. Get Device Attribute ................................................................................................................... 59
6.25. Set Device Attribute ................................................................................................................... 60
6.26. Change MAC-ID ......................................................................................................................... 60
6.27. Message Monitor ........................................................................................................................ 61
6.28. Message Monitor for testing explicit messaging of DeviceNet .................................................. 62
CHAPTER 7: FILE, PRINT, EXPORT, EDIT AND VIEW ........................................................................... 63
7.1. File 63
7.1.1. Open .............................................................................................................................................. 63
7.1.2. Save and Save As ......................................................................................................................... 63
7.1.3. Close .............................................................................................................................................. 63
7.2. Print ................................................................................................................................................... 63
7.3. Export Functions ............................................................................................................................... 64
7.3.1. DBM Export .................................................................................................................................... 64
7.3.2. CSV Export .................................................................................................................................... 64
7.3.2.1. DataType Code ........................................................................................................................... 65
7.3.2.2. DataPosition Code ...................................................................................................................... 65
7.4. Edit 66
7.4.1. Delete ............................................................................................................................................. 67
7.4.1. Replace .......................................................................................................................................... 67
7.5. View of the Configuration .................................................................................................................. 67
7.5.1. Device Table .................................................................................................................................. 67
7.5.2. Address Table ................................................................................................................................ 67
7.6. View Menu HSyCon .......................................................................................................................... 68
7.6.1. Logical Network View ..................................................................................................................... 68
7.6.2. Toolbars ......................................................................................................................................... 68
7.6.3. Status Bar ...................................................................................................................................... 68
CHAPTER 8: ERROR NUMBERS .............................................................................................................. 69
8.1. CIF Device Driver (Dual-port memory) Error Numbers (-1-49) .................................................. 69
8.2. CIF Serial Driver Error Numbers (-20 .. -71) .............................................................................. 73
8.3. RCS Error Numbers (4 .. 93) ...................................................................................................... 75
8.4. Database Access Error Numbers (100 .. 130) ........................................................................... 77
8.5. Online Data Manager Error Numbers (1000 .. 1018) ................................................................. 78
8.6. Message Handler Error Numbers (2010 .. 2027) ....................................................................... 78
8.7. Driver Functions Error Numbers (2501 .. 2512) ......................................................................... 79
8.8. Online Data Manager Subfunctions Error Numbers (8001 .. 8035) ........................................... 79
8.9. Data Base Functions Error Numbers (4000 .. 4199).................................................................. 80
8.10. Converting Functions Error Numbers (5001 .. 5008) ................................................................. 84
CHAPTER 9: EXPLICIT MESSAGING USING DNM650 .......................................................................... 85
9.1 General ....................................................................................................................................... 85
Page 5 of 98
EO 09-0009
MAN0577-03-En
HE800DNM650 & HE800DNS600
DeviceNet Modules
9.2 Building Explicit Messages ......................................................................................................... 85
9.3 How to Interpret Explicit Response Messages .......................................................................... 86
9.4 Explicit Message Errors ............................................................................................................. 87
APPENDIX: ................................................................................................................................................. 88
A. EXTENDED DEVICE DIAGNOSTIC MASTER ................................................................................ 88
A.1. PLC_TASK Common Variables ................................................................................................. 88
A.2. DNM_TASK Common Variables ................................................................................................ 88
A.3. DNM_TASK Device Running States .......................................................................................... 90
A.4. DNM_Task Global State Field .................................................................................................... 90
A.5. DNM_Task Communication Error .............................................................................................. 90
A.6. DNM_Task Receive Queue ....................................................................................................... 91
A.7. DNM_Task Transmit Queue ...................................................................................................... 91
A.8. DNM_Task DeviceNet Command Counters .............................................................................. 92
A.9. DNM_Task Timeout Counter ..................................................................................................... 93
A.10. DNM_Task Init Counter .............................................................................................................. 93
B. EXTENDED DEVICE DIAGNOSTIC DEVICE (SLAVE) .................................................................. 94
B.1. PLC_Task Common Variables (Device) .................................................................................... 94
B.2. DNS_Task Common Variables .................................................................................................. 95
B.3. DNS_TASK Receive Queue (Device) ........................................................................................ 96
B.4. DNS_TASK Transmit Queue (Device) ....................................................................................... 97
Page 6 of 98
EO 09-0009
DeviceNet Modules
MAN0577-03-en
HE800DNM650 & HE800DNS600
CHAPTER 1: INTRODUCTION
1.1 Scope
This manual shows how to connect and configure the DeviceNet Master or Slave Smartstack Modules.
HSyCon, a Windows-based software package, is an easy-to-use configuration package for use with the
SmartStack COM range of fieldbus modules and Cscape or Cbreeze, a Windows™ based package for
use with the OCS/ TIU ranges. The software user’s guide is contained in this manual.
A basic level of understanding of Microsoft Windows™ technology and operation is assumed. The
manual assumes that the user is familiar with Windows 95, Windows 98, Windows NT, Win 2000 or XP.
1.2 Introduction
The Fieldbus Smartstack module range require only three stages to get them operational, these are:
1. Physical installation and connection.
2. Configuration of the fieldbus interface.
3. Configuration of Cscape / Cbreeze to map the fieldbus data.
The system is comprised of two separate software software functions, the fieldbus interface software
running independently in the COM module and the OCS/TIU firmware running in the main module. Data
and commands are exchanged via a dual port ram interface. The configuration of the COM module is via
the RS232 serial port on the module. For correct operation the number of registers assigned in the OCS
must match the number required by the Master or Slave module configuration.
The Smartstack module should be configured with the OCS/TIU software first as otherwise it will be held
in reset and cannot be configured.
Page 7 of 98
EO 09-0009
DeviceNet Modules
MAN0577-03-en
1.3 Installing and Removing a SmartStack Module
The following section describes how to install and remove a SmartStack Module.
Caution: To function properly and avoid possible damage, do not install more than four
SmartStack Modules per OCS or RCS.
Do not attempt to install or remove a SmartStack module with the units powered on.
1.4 Installing SmartStack Modules
1. Hook the tabs. Each SmartStack Module has two tabs that fit into slots located on the OCS.
(The slots on the OCS are located on the back cover.)
2. Press the SmartStack Module into the “locked” position, making sure to align the SmartStack
Module fasteners with the SmartStack receptacles on the OCS.
1.5 Removing SmartStack Modules
1. Using a flathead screwdriver, lever up the end of the SmartStack Module (opposite end to tabs) and
swing the module out.
2. Lift out the tabs of the module.
SmartStack Tab
Figure 2.1 – Installing a SmartStack Module in an OCS
HE800DNM650 & HE800DNS600
Fastener
Mating Pins
OCS Back Cover
Page 8 of 98
EO 09-0009
DeviceNet Modules
MAN0577-03-en
1.6 Status LED definitions
Signal LED Colour State Definition
NET RED
ON Critical Link Failure
Flashing Connection Time out
OFF Device Not Powered
GREEN
ON ON-LINE Link OK
Flashing ON-LINE, Not connected
OFF Device Not Powered
MOD RED
ON Unrecoverable Fault
FLASHING Minor Fault
OFF No Power
GREEN
ON Normal Operation
FLASHING Configuration Failure
OFF No Power
RDY YELLOW
ON COM ready
FLASHING CYCLIC Bootstrap Loader Active
FLASHING NON CYCLIC Hardware or System Error
OFF Hardware Error
RUN GREEN
ON Communication Running
FLASHING NON CYCLIC Parameter Error
OFF Communication Stopped
Status Signals of the DNM650 and DNS600
1.7 Main Functions
The main functions of the DEVICENET System Configurator are:
• Universal Fieldbus Configurator - Configuration of the complete Fieldbus range with one package.
• Documents Fieldbus system - detailed documentation of the Fieldbus network may be printed.
• Standardised configuration files – allows use of protocol specific standardised configuration files.
• Diagnostic tool – upon configuration download the software may be switched into diagnostic mode.
HE800DNM650 & HE800DNS600
Page 9 of 98
EO 09-0009
DeviceNet Modules
MAN0577-03-en
HE800DNM650 & HE800DNS600
CHAPTER 2: INSTALLATION
2.1 System Requirments
• PC with 486-, Pentium processor or higher.
• Windows 95/98/ME, Windows NT/2000/XP.
• Free disk space: 30 - 80 Mbyte.
• CD ROM drive.
• RAM: min. 16 Mbyte.
• Graphic resolution: min. 800 x 600 pixel.
• Windows 95: Service Pack 1 or higher.
• Windows NT: Service Pack 3 or higher.
• Keyboard and Mouse.
2.2 System Installation
It is recommended that all application programs on the system are closed before installation begins.
Insert the Cscape CD in the local CD ROM drive. The HSycon installation program will start automatically
when installation of Cscape is complete (see Fig 2.1)
Fig 2.1
Note: Administrator privileges are required on Windows NT/2000/XP systems for installation.
The installation program asks for the components to install. Answer these questions with Yes or No. Tick
‘No’ for the OPC Server function, it is not included with this installation pack.
Page 10 of 98
EO 09-0009
DeviceNet Modules
MAN0577-03-en
2.3 Installation of the System Configurator HSyCon
Follow the instructions of the installation program by selecting the Language, Fieldbus system to be
installed and answer all the questions with OK or NEXT.
HE800DNM650 & HE800DNS600
Fig 2.2
Fig 2.3
The installation program copies the program files, GSD or EDS files and Bitmaps to the PC.
Page 11 of 98
EO 09-0009
DeviceNet Modules
MAN0577-03-en
HE800DNM650 & HE800DNS600
Fig 2.4
Fig 2.5
Finally the following files are entered in the system Registry.
• System DLLs
• The application
Page 12 of 98
EO 09-0009
DeviceNet Modules
MAN0577-03-en
HE800DNM650 & HE800DNS600
NOTES
Page 13 of 98
EO 09-0009
DeviceNet Modules
MAN0577-03-en
HE800DNM650 & HE800DNS600
CHAPTER 3: GETTING STARTED – CSCAPE CONFIGURATION
3.1 Scope
This chapter describes the procedures for configuring the DeviceNet Master and slaves. This includes
loading EDS files, saving, downloading and assigning I/O.
3.2 Configuring Cscape.
The following describes the steps involved to setup Cscape. Attach the communications module to the
appropriate OCS unit. Open Cscape. All I/O is setup through the I/O Configure Menu in Cscape:
Figure 3.1
The following window is displayed. Select the CONFIG button adjacent to the first empty slot (nearest the
main unit).
Figure 3.2
Page 15 of 98
EO 09-0009
DeviceNet Modules
MAN0577-03-en
Select the COMM Tab. From here select the appropriate DeviceNet Module and click OK.
HE800DNM650 & HE800DNS600
Figure 3.3
The selected module is now visibly attached to the main unit and can be configured.
Figure 3.4
Page 16 of 98
EO 09-0009
DeviceNet Modules
MAN0577-03-en
Select the CONFIG button adjacent to the module. Then select the MODULE SETUP tab.
HE800DNM650 & HE800DNS600
Figure 3.5
Configure the Inputs and Outputs.
NOTE:
INPUTS: means data coming FROM the Network VIA the DNM/DNS Module to the OCS Registers.
OUTPUTS: means data going TO the NETWORK VIA the DNM/DNS Module from the OCS Registers.
In Figure 3.5 above, For both Inputs and Outputs, 8 %R registers are used. The OCS %R registers are
retentive, general purpose, 16 bit registers.
Page 17 of 98
EO 09-0009
DeviceNet Modules
MAN0577-03-en
It is VERY important that the number of registers used for both Inputs and Outputs in Cscape is
identical to the number setup in the Hsycon software when setting up the DNM650 and DNS600
modules. See Figure 3.6 below.
HE800DNM650 & HE800DNS600
Figure 3.6
Page 18 of 98
EO 09-0009
DeviceNet Modules
MAN0577-03-en
3.3 Configuring a SmartStack DeviceNet Master with any DeviceNet Slave
Table 4 below describes the steps to configure a Horner Smartstack DeviceNet Master to any DeviceNet
Device (Slave).
Action Menu in the System Configurator
Create a new project
•
Copy EDS file of the DeviceNet device (Slave), if the
•
device is not in the selection list.
Choose Horner DeviceNet Master and provide MAC ID.
•
Choose DeviceNet device and provide MAC ID address
•
Assign the input and output modules (*1)
•
Assign the offset addresses
•
Assign the Device Parameter data, if the Device needs
•
Parameter data
Set the Bus parameter Mark the Master (left Mouse click), then
•
Set device assignment if no automatic assignment has
•
occurred
Save project
•
Download Mark the Master (left Mouse click), then
•
Live list Mark the Master (left Mouse click), then
•
Start Debugger Mark the Master (left Mouse click), then
•
Device diagnostic Mark the Slave (left Mouse click), then
•
Stop Debugger
•
Global Diagnostic Mark the Master (left Mouse click), then
•
Transfer user data:
•
Write output, read input
HE800DNM650 & HE800DNS600
File > New > DeviceNet
File > Copy EDS
Insert > Master
Insert > Device
Mark the Device (left Mouse click), then
Settings > Device Configuration
Mark the Device (left Mouse click), then
Settings > Device Configuration >
Parameter Data
Settings > Bus Parameters
Mark the Master (left Mouse click), then
Settings > Device Assignment
File > Save
Online > Download
Online > Live List
Online > Start Debug Mode
Online > Device Diagnostic
Online > Stop Debug Mode
Online > Global State Field
Mark the Master (left Mouse click), then
Online > I/O Monitor
Table 4: Steps to Configure DNM650 with any DeviceNet Slave.
Note (*1): The Offset addresses assigned in the Slave configuration are always related to the Master.
3.4 Configuring a SmartStack DeviceNet Slave with any DeviceNet Master
Table 5 below describes the steps to configure a Horner DeviceNet Slave to any DeviceNet Master as it is
typical for many cases.
Action Menu in the System Configurator
Page 19 of 98
EO 09-0009
DeviceNet Modules
MAN0577-03-en
HE800DNM650 & HE800DNS600
Create a new project
•
Choose DeviceNet Master (*1) and provide MAC ID
•
address
Choose Horner DeviceNet device (Slave) and
•
provide Mac address
Assign the input and output modules (*2)
•
Set device assignment if no automatic assignment
•
has occurred
Save project
•
Download Mark the Slave (left Mouse click), then
•
Device diagnostic Mark the Slave (left Mouse click), then
•
Transfer user data:
•
Write output, read input
File > New > DeviceNet
Insert > Master
Insert > Device
Mark the Device (left Mouse click), then
Settings > Device Configuration
Mark the Device (left Mouse click), then
Settings > Device Assignment
File > Save
Online > Download
Online > Device Diagnostic
Mark the Device (left Mouse click), then
Online > I/O Monitor
Table 5: Steps to configure a DNS600 with any DeviceNet Master.
Note (*1): Insert a Horner SmartStack DeviceNet Master (HE800DNM650). This Master is a place holder
and it is not necessary to match the connected Master.
Note (*2): The Offset addresses assigned in the Slave configuration are always related to the DeviceNet
Master.
Page 20 of 98
EO 09-0009
DeviceNet Modules
MAN0577-03-en
3.5 Configuring a Horner DeviceNet Master with a Horner DeviceNet Slave
Table 6 below describes the steps to configure a SmartStack DeviceNet Master to a Smartstack
DeviceNet slave :
Action Menu in the System Configurator
Create a new project
•
Choose Horner DeviceNet Master and provide MAC ID address
•
Choose Horner DeviceNet Device (Slave) and provide MAC ID
•
address
Assign the input and output modules Mark the Device (left Mouse click), then
•
Assign the offset addresses (*1)
•
Set the Bus parameter Mark the Master (left Mouse click), then
•
Set device assignment for the Master if no automatic assignment
•
has occurred
Set device assignment for the Device (Slave) if no automatic
•
assignment has occurred
Save project
•
Download to the Master Mark the Master (left Mouse click), then
•
Download to the Device (Slave) Mark the Device (left Mouse click), then
•
Live list Mark the Master (left Mouse click), then
•
Start Debugger Mark the Master (left Mouse click), then
•
Device diagnostic Mark the Device (left Mouse click), then
•
Stop Debugger
•
Global Diagnostic Mark the Master (left Mouse click), then
•
Transfer user data:
•
Write output, read input
HE800DNM650 & HE800DNS600
File > New > DeviceNet
Insert > Master
Insert > Device
Settings > Device Configuration
Settings > Bus Parameters
Mark the Master (left Mouse click), then
Settings > Device Assignment
Mark the Device (left Mouse click), then
Settings > Device Assignment
File > Save
Online > Download
Online > Download
Online > Live List
Online > Start Debug Mode
Online > Device Diagnostic
Online > Stop Debug Mode
Online > Global State Field
Mark the Master (left Mouse click), then
Online > I/O Monitor
Table 6: Steps to configure a DNM650 with DNS600’s.
Note (*1): The Offset addresses assigned in the Slave configuration are always related to the DeviceNet
Master.
Page 21 of 98
EO 09-0009
DeviceNet Modules
MAN0577-03-en
HE800DNM650 & HE800DNS600
CHAPTER 4: CONFIGURATION OF DEVICENET WITH HSYCON
4.1 Setting up the DEVICENET Configuration
To create a new configuration, choose the File > New menu. This will offer a selection list of fieldbus
systems. Choose DEVICENET. If only the DeviceNet fieldbus system is installed, the configuration
window will open directly. The name of the configuration file can be allocated when the configuration is
finished or with File > Save As.
4.2 EDS Files (Electronic Data Sheet Files) Introduction
An Electronic Data Sheet (EDS) provides information necessary to access and alter the configurable
parameters of a device. An Electronic Data Sheet (EDS) is an external file that contains information
about configurable attributes for the device, including object addresses of each parameter.
The application objects in a device represent the destination addresses for configuration data. These
addresses are encoded in the EDS. The figure below shows a general block diagram of a sample EDS.
EDS
General Device
Information
Device Parameter 1
Standard Device Profile
Device Parameter X
Standard Device Profile
Vendor-Specific
Device Parameter 1
Vendor-Specific
Device Parameter X
Optional
Figure 1: General block diagram of an EDS file
Page 22 of 98
EO 09-0009
DeviceNet Modules
MAN0577-03-en
4.3 EDS Files and HSyCon
When HSyCon is started, it automatically retrieves all the EDS files stored in the EDS directory. The
device names are placed in an internal list. During the configuration, the device-specific data is retrieved
directly from the EDS files.
If a DeviceNet device does not appear in the selection list (Insert Master or Insert Device), the required
EDS file may be copied into the EDS directory with File > Copy EDS. Another method is to copy the
EDS file into the HSyCon EDS directory with Windows Explorer and then access the EDS files in the EDS
directory with Settings > Path and OK.
Horner devices: The EDS files for Horner devices are included and already installed.
Other devices: The respective device manufacturer provides the EDS files for other devices.
The EDS files of some vendors are available on the DeviceNet homepage http://www.odva.org
or visit the homepage of the manufacturer.
The EDS directory is adjustable. In order to alter the directory from a previous setting in another
directory, use the menu Settings > Path. All EDS files must be placed in this directory.
4.4 Insert Master
To insert a Master into the configuration, choose the Insert > Master menu, this will open the selection
window, or click on the symbol :
HE800DNM650 & HE800DNS600
Insert > Master Symbol
Figure 1: Symbol Insert > Master
The mouse pointer automatically changes to the Insert Master pointer.
Insert Master Mouse
Pointer
Figure 2: Mousepointer insert Master
Click on the position where the Master should be inserted. The dialog box from which one or more
Masters can be chosen opens. The following types of Masters may be selected:
Page 23 of 98
EO 09-0009
DeviceNet Modules
MAN0577-03-en
HE800DNM650 & HE800DNS600
Figure 3: Selectable Master types
Select a Master device from the Available Masters list by clicking on it. By clicking the Add button the
Master is shown in the list Selected Masters. Click the OK button, the Master will be inserted at the top
of the configuration.
This example shows an HE500DNM650-001. The Master gets the description Master at first. This may
be changed in the Description field. The MAC ID of the Master may also be changed here.
4.5 Insert Device (Slave)
To insert a DeviceNet Slave in the configuration select the Insert > Device menu to open the selection
window or click on the following Icon:
Insert > Device Symbol
Table 4: Insert > Device Symbol
The mouse cursor changes automatically to the insert device cursor.
Insert Device Mouse
Pointer
Table 5: Insert Device Mouse Pointer
Click on the position at which the new device should be inserted. A dialogue box appears from which one
or more devices may be chosen.
Page 24 of 98
EO 09-0009
DeviceNet Modules
MAN0577-03-en
HE800DNM650 & HE800DNS600
Figure 2: Insert > Device (Slave)
The list on the left displays all the Slave devices whose EDS files have been put in the EDS directory. A
filter may be used to limit the selection list of the manufacturer. Further information on a Slave is shown
below the selection list (Available devices) when it is selected (one mouse click). Apart from the vendor
name and the description especially the ID-Code, the I/O-Code, the file name and the file revision are
given. The Slave appears on the right-hand list with a mouse click or with the Add button.
All devices in the right-hand list are assigned to the current insert point that is also shown in this window.
If the Slaves in the right-hand list are chosen one after the other (a mouse click), then every Slave can be
assigned a name in the Description field.
With each new selected device in the right list the MAC ID is incremented by one but it can be changed
by the user in the field MAC ID.
Note: It is possible to select the same device more than once, however, each device must have a unique
MAC ID to distinguish it in the network.
4.6 Replace Slave
To replace an existing Slave device first mark the device to be replaced. Then proceed as described in
the section 4.5 Replace Master.
4.7 Device Configuration
To enter the Device Configuration set the focus on the device (left mouse click) and select the menu
Settings > Device Configuration or set the focus on the device (left mouse click) and use the right
mouse button at the device or simply double-click on the device.
The device’s I/O are assigned to logical addresses in the process data image of the Master
configuration. Note that the device offsets set here will be used in the application to read inputs and write
outputs.
in the device
Page 25 of 98
EO 09-0009
DeviceNet Modules
MAN0577-03-en
HE800DNM650 & HE800DNS600
Figure 3: Settings > Device Configuration
Note 1: The offset addresses set in this window are for the addressing of the input data and output data
in the Master. These address settings (offsets) are not the settings in the DeviceNet device (Slave). The
DeviceNet device (Slave) organizes its data itself.
Note 2: The input data and the output data from the bus are transferred directly to the dual-port memory
in the DeviceNet Slave. These offset addresses are related to the Master.
The File Name displayed is the EDS file for the device.
The Description and MAC ID fields display the entries made during the selection phase of the Slave
device. Both entries can be set/changed here.
The checkbox Activate Device in actual configuration decides, whether the Master tries to establish
the communication with the Node or not. If a Node is physically not present in the network but will be
present in future then the checkbox should not be checked. This suppresses unnecessary requests by
the Master to devices that do not exist, but the device insertion reserves process data in the process data
image of the Master.
4.8 MAC ID (Device network address)
The network address of a device serves to distinguish itself on a DeviceNet fieldbus system from any
other device or Slave on this network. This should be a unique number for each device. A valid MAC-ID
address is within a range of 0 to 63 and can be re-entered and changed in the MAC-ID box in the Device
Configuration Dialog.
Page 26 of 98
EO 09-0009
DeviceNet Modules
MAN0577-03-en
4.9 Actual chosen IO Connection
DeviceNet allows several kinds of I/O connections between devices. Please note that a device does not
have to support all types of IO connections.
The different connections types are :
• Polled I/O Connection - One poll command from the Master sends a number of output data to a
single, specific device (point-to-point). The device receives (consumes) the poll command and
processes the output data. If it has input data configured for this poll connection it reacts by sending
(producing) back a number of input data and/or status information to the Master. Before a polled I/O
connection is initiated by the Master, it reads the Consumed and Produced Connection Size of the
data from the Slave first and compares each value with the internally configured one. If the Master
detects differences the connection cannot be established. Sending a poll command can happen at
any time the Master wants to and has timer or event dependencies. A device has to respond if it has
consumed and understood the poll command request of the Master, even if it has no input data.
Otherwise the Master will report a timeout error. Polling data to many devices has the disadvantage
that the network traffic rate is very high and most data which is transferred has not changed since the
last transmission. Furthermore the higher the bus load more communication errors can occur if the
bus is disturbed by external influences.
HE800DNM650 & HE800DNS600
I/O connection
Poll
Bit Strobe
Change of State
Cyclic
Table 6: Overview I/O Connections
• Bit Strobe I/O Connection - Bit strobe command and response messages rapidly move small
amounts of I/O data between the Master device and one/some/all Slave devices. The bit strobe
message contains a bit string of 64 bits of output data, one output bit per possible device. Each bit is
assigned to one device address in the network. This service has broadcast functionality that means
more than one Slave device can be addressed by one command. Because all addressed Slave
devices get this command at the same time, this command is normally used to synchronize data
transfer to several Slave devices. A Slave device can take its corresponding output bit as a real
output information to give it to the peripheral connections (e.g. an LED) and/or use the bit as a trigger
to send back its input data with a poll response message. The data that can be send back from each
Slave after a bit strobe command was received is limited to 8 bytes in length. Bit strobe connections
reduce the bus loading.
• Change of State/Cyclic I/O Connection - The Master device sends a number of output data to a
single, specific device (point-to-point). Data production is triggered by either a determined changed
value in the output data or the cyclic timer expiration. Depending on how the Slave behaviour is
configured, the Slave can send back an acknowledge message, containing a number of input data
and/or status information. The Slave device sends a number of input data to the Master, if the data is
either changed or the cyclic timer has expired. The Master itself can acknowledge this message with
output data if configured.
• Change of state only production of data hold down the bus load as small as possible, while data than
can be transmitted as fast as possible by each device because bus conflicts are less possible. High
performance data transmission can be achieved with comparatively low baud rates.
Page 27 of 98
EO 09-0009
DeviceNet Modules
MAN0577-03-en
4.10 Connection Object Instance Attributes
The Production Inhibit Time, one for each connection, configures the minimum delay time between new
data production in multiples of a millisecond. The timer is reloaded each time new data production
through the established connection occurs. While the timer is running the device suppresses new data
production until the timer has expired. This method prevents that the device is overloaded with to fast
incoming requests.
The value 0 defines no inhibit time and data production can and will be done as fast as possible. If in
polled mode for example a Production Inhibit Time of 1000dec is configured, then the poll request
message to the device will be sent every second.
The Expected Packet Rate, one for each connection, is always transferred to the device before starting
and doing the I/O transfer . The value is used by the device later to reload its 'Transmission Trigger' and
'Watchdog Timer'. The 'Transmission Trigger Timer' is used in a 'cyclic' I/O connection to control the time
when the data shall be produced. Expiration of this timer then is an indication that the associated
connection must transmit the corresponding I/O message. In 'change of state' connections the timer is
used to avoid the watchdog timeout in this connection, when a production has not occurred since the
timer was activated or reloaded.
Note: the Production Inhibit Time is verified against the Expected Packet Rate. If the Expected Packet
Rate value is unequal zero, but less than the Production Inhibit Time value, then an error window is
opened when pressing the OK button or changing to a wrong value.
The Watchdog Timeout Action defines the device behaviour when the watchdog timer in the device
expires. The following values are defined and their functionality is closer described in the DeviceNet
specification.
• Transition to Timed Out: The connection transitions to the Timed Out state and remains in this state
until it is Reset or Deleted.
HE800DNM650 & HE800DNS600
• Auto Delete: The connection class automatically deletes the connection if it experiences an
Inactivity/Watchdog timeout.
• Auto Reset: The connection remains in the established state and immediately restarts the
Inactivity/Watchdog timer.
4.11 UCMM Check
The UCMM Check box is used for modules that require the use of UCMM messaging format. Class
1,2,and 3 are supported. Check the documentation for the Slave device to identify if this box must be
checked.
4.12 Fragmented Timeout
If a transmission of I/O data or explicit message is greater than 8 bytes in length, it must be transmitted
on DeviceNet in a fragmented manner. The maximum time the Master will wait until a Slave has to
respond during the fragmented transmissions is the fragmented timeout.
4.13 Parameter Data
The button Parameter Data can be selected in the Device Configuration window to edit the parameter
data.
If default parameters are configured in the EDS file for this Node, they are inserted automatically when
the menu is chosen the first time.
Page 28 of 98
EO 09-0009
DeviceNet Modules
MAN0577-03-en
Some of devices need some further parameterisation data, to change for example a measurement
limitation or a value range. These data is Node specific and their functionality can not be explained at this
point.
The explanation can be normally found in the corresponding Node manual.
This window below shows an example of parameter data of a device.
HE800DNM650 & HE800DNS600
Figure 4: Settings > Device Configuration > Parameter Data
Two tables are available: one table with all available parameters and one table for customized
parameters. These parameters can be selected from the available parameters to that table.
Page 29 of 98
EO 09-0009
DeviceNet Modules
MAN0577-03-en
HE800DNM650 & HE800DNS600
4.14 Process Data Configuration
• Fixed I/O data transferred
DeviceNet handles I/O data transparent as a byte string without defining any data type in the
transferred data. To be operative it defines only the number of bytes in consumed and produced
direction that shall be transferred across a connection, nothing else. But HSyCon and the firmware
now allows to assign modular each byte or a bunch of bytes of the transparent string to different data
types. A list of the supported data types of the connection can be found in the middle table of the
window called
The following data types are supported:
• Bit, Byte, Word, Dword, Byte Array
If the data type Byte Array is chosen the number of bytes that shall be reserved for this data type can
be entered in the Data Count column in the lower table. Any other data type has its fixed length that
can not be changed. The data types are distinguished in process output and process input data in the
view of the Master device.
A double-click on a predefined data type or a click in the Add to configured I/O data button will
insert the chosen data type in the lower table called Configured I/O connection data. This table
contains all data that shall be really transferred across the connection. HSyCon will add separately
the number of used bytes of each configured I/O data and forms the values Consumed and
Produced Connection Size automatically. Both values indicates the sum of bytes which shall be
sent by the Master as outputs (Consumed by the device) and received by the Master as inputs
(Produced by the device).
Available Predefined Connection Data Types.
• Assigning the process data offset addresses
The I/O offset addresses of each placed data type in the connection data table can be freely
configured in a range of 0 to 3583 or they are set automatically by HSyCon. To enable or disable free
configuration use the flag Auto Addressing in the menu Settings - Auto Addressing. If enabled
HSyCon will place all configured I/O data, without spaces in physical order one after another based
on the rising MAC-ID order. This is done during the download procedure. The assigned addresses
can be checked then in the overview Address Table of the menu View. If the addresses are entered
manually the default address 0 in the input address respectively the output address must be
overwritten. Depending on the Addressing mode in the DNM Master Settings the addresses are
byte addresses or word addresses. This is described in the chapter Addressing mode.
Page 30 of 98
EO 09-0009
Loading...