DeviceNet Modules HE800DNM650 & HE800DNS600 MAN0577-03-En User Manual for HE800DNM650/HEDNM650 & HE800DNS600/HEDNS600 DeviceNet Master and Slave SmartStack™ Modules Page 1 of 98 EO 09-0009
DeviceNet Modules HE800DNM650 & HE800DNS600 MAN0577-03-En 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.
DeviceNet Modules HE800DNM650 & HE800DNS600 MAN0577-03-En 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
DeviceNet Modules HE800DNM650 & HE800DNS600 MAN0577-03-En TABLE OF CONTENTS PREFACE ..................................................................................................................................................... 2 LIMITED WARRANTY AND LIMITATION OF LIABILITY ............................................................................. 2 CHAPTER 1: INTRODUCTION .................................................................................................................... 7 1.
DeviceNet Modules HE800DNM650 & HE800DNS600 MAN0577-03-En 6.7. Automatic Network Scan ............................................................................................................ 45 6.8. Start/Stop Communication ......................................................................................................... 48 6.9. Diagnostic Functions .................................................................................................................. 48 6.10. Live List .............
DeviceNet Modules HE800DNM650 & HE800DNS600 MAN0577-03-En 9.2 Building Explicit Messages......................................................................................................... 85 9.3 How to Interpret Explicit Response Messages .......................................................................... 86 9.4 Explicit Message Errors ............................................................................................................. 87 APPENDIX: ....................................
DeviceNet Modules HE800DNM650 & HE800DNS600 MAN0577-03-en 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.
DeviceNet Modules HE800DNM650 & HE800DNS600 1.3 MAN0577-03-en 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.
DeviceNet Modules HE800DNM650 & HE800DNS600 1.6 Status LED definitions Signal LED Colour NET RED GREEN MOD RED GREEN RDY YELLOW RUN GREEN 1.
DeviceNet Modules HE800DNM650 & HE800DNS600 MAN0577-03-en 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.
DeviceNet Modules HE800DNM650 & HE800DNS600 MAN0577-03-en Fig 2.2 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. Fig 2.3 The installation program copies the program files, GSD or EDS files and Bitmaps to the PC.
DeviceNet Modules HE800DNM650 & HE800DNS600 MAN0577-03-en Fig 2.4 Fig 2.5 Finally the following files are entered in the system Registry.
DeviceNet Modules HE800DNM650 & HE800DNS600 MAN0577-03-en NOTES Page 13 of 98 EO 09-0009
DeviceNet Modules HE800DNM650 & HE800DNS600 MAN0577-03-en 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.
DeviceNet Modules HE800DNM650 & HE800DNS600 MAN0577-03-en Select the COMM Tab. From here select the appropriate DeviceNet Module and click OK. Figure 3.3 The selected module is now visibly attached to the main unit and can be configured. Figure 3.
DeviceNet Modules HE800DNM650 & HE800DNS600 MAN0577-03-en Select the CONFIG button adjacent to the module. Then select the MODULE SETUP tab. 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.
DeviceNet Modules HE800DNM650 & HE800DNS600 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. Figure 3.
DeviceNet Modules HE800DNM650 & HE800DNS600 3.3 MAN0577-03-en 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 File > New > DeviceNet • Copy EDS file of the DeviceNet device (Slave), if the device is not in the selection list. File > Copy EDS • Choose Horner DeviceNet Master and provide MAC ID.
DeviceNet Modules HE800DNM650 & HE800DNS600 MAN0577-03-en • Create a new project File > New > DeviceNet • Choose DeviceNet Master (*1) and provide MAC ID address Insert > Master • Choose Horner DeviceNet device (Slave) and provide Mac address Insert > Device • Assign the input and output modules (*2) Mark the Device (left Mouse click), then • Set device assignment if no automatic assignment has occurred Mark the Device (left Mouse click), then • Save project File > Save • Download Mark
DeviceNet Modules HE800DNM650 & HE800DNS600 3.
DeviceNet Modules HE800DNM650 & HE800DNS600 MAN0577-03-en 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.
DeviceNet Modules HE800DNM650 & HE800DNS600 4.3 MAN0577-03-en 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.
DeviceNet Modules HE800DNM650 & HE800DNS600 MAN0577-03-en 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.
DeviceNet Modules HE800DNM650 & HE800DNS600 MAN0577-03-en 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).
DeviceNet Modules HE800DNM650 & HE800DNS600 MAN0577-03-en 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.
DeviceNet Modules HE800DNM650 & HE800DNS600 4.9 MAN0577-03-en 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. I/O connection Poll Bit Strobe Change of State Cyclic Table 6: Overview I/O 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).
DeviceNet Modules HE800DNM650 & HE800DNS600 4.10 MAN0577-03-en 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.
DeviceNet Modules HE800DNM650 & HE800DNS600 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.
DeviceNet Modules HE800DNM650 & HE800DNS600 4.14 • MAN0577-03-en 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.
DeviceNet Modules HE800DNM650 & HE800DNS600 MAN0577-03-en In case of manual addressing (that means auto addressing is deactivated) the configuration window looks like: Figure 5: Settings > Device Configuration In the column I Addr and O Addr, the addresses where to locate the data in the process image must be assigned. Remember that these addresses correspond to the application on the HOST side.
DeviceNet Modules HE800DNM650 & HE800DNS600 MAN0577-03-en CHAPTER 5: SETTINGS 5.1 Device Assignment The Device Assignment setting determines how the System Configurator communicates with the device. This is set in the device arrangement via the menu Settings > Device Assignment. The following possibilities are available: CIF Device Driver CIF Serial Driver CIF TCP/IP Driver CIF Device Driver: • Not supported do not choose this driver.
DeviceNet Modules HE800DNM650 & HE800DNS600 MAN0577-03-en The connection must first be established using the switching surface Connect COM1, Connect COM2, Connect COM3 or Connect COM4. They can be used depending on which COM interfaces are installed and free on the PC. The System Configurator sends a request to the corresponding COM interface and polls the Firmware of the device. A display of the Firmware will indicate when a device is connected.
DeviceNet Modules HE800DNM650 & HE800DNS600 5.3 MAN0577-03-en Bus Parameter In the menu Settings > Bus Parameter the basic settings for the DeviceNet network must be done. Figure 9: Settings > Bus Parameters Mainly, this concerns the determination of the Baudrate. The DeviceNet board supports the baudrates 125kbit/s, 250kbit/s and 500kbit/s. Normally DeviceNet components use the autobaud detection to get the baudrate automatically.
DeviceNet Modules HE800DNM650 & HE800DNS600 MAN0577-03-en Figure 10: Settings > Master Settings • Startup behaviour after system initialization If Automatic release of the communication by the device is selected, the Master starts with the data transfer on the bus when initialisation is finished. If Controlled release of the communication by the application program is selected, the user has to start the data transfer on the bus, by a defined release procedure.
DeviceNet Modules HE800DNM650 & HE800DNS600 • MAN0577-03-en Handshake of the process data With these different modes the handshake of the process data is selected for the Master. The selection of this mode is important for the correct data exchange between the application and the device. Please refer to the tool kit or the device driver manual for the detailed description of these modes.
DeviceNet Modules HE800DNM650 & HE800DNS600 MAN0577-03-en The following table shows the different storing of the various data types in the Byte- or Word-oriented process image: IEC address in Byte mode IEC address in Word mode Offset address in the Dualport memory Data in the Process image QB 0 QB 0 0 0000 0000 1 0000 0000 2 1110 0010 Output of QB2 / QB1 to a single Byte module: D7 D6 D5 D4 D3 D2 D1 D0 1 1 1 0 0 0 1 0 3 0000 0000 QB 1 QB 2 QB1 QB 3 Output to an I/O module QB 4 QB 5 QB2
DeviceNet Modules HE800DNM650 & HE800DNS600 MAN0577-03-en The following table is meant to clarify the method of addressing: Byte Addressing Byte 0 IB 0 Byte 1 IB 1 Byte 2 IB 2 Byte 3 IB 3 Byte 4 IB 4 Byte 5 IB 5 Word Addressing IW 0 Word 0 IB 0 IW 0 IW 2 Word 1 IB 1 IW 1 IW 4 Word 2 IB 2 IW 2 - Figure 11: Image of the method of addressing for input Byte Addressing Byte 0 QB 0 Byte 1 QB 1 Byte 2 QB 2 Byte 3 QB 3 Byte 4 QB 4 Byte 5 QB 5 Word Addressing QW 0 Word 0 QB 0
DeviceNet Modules HE800DNM650 & HE800DNS600 5.6 MAN0577-03-en Project Information When a project is created, the project information can be typed into the Settings > Project Information menu. This entry can then be read when this menu is called up. Figure 13: Settings > Project Information Click the OK button to save the Project Information. 5.7 Path In the menu Settings > Path the path directory of the EDS files is shown (EDS File directory).
DeviceNet Modules HE800DNM650 & HE800DNS600 MAN0577-03-en The language of the System Configurator can be set. Select the desired language and confirm the entry with the OK button. A message appears that the System Configurator must be started again in order to activate the selected language. Please carry this out. After restarting the System Configurator, the language will have changed to the one selected. Note: Up to now not all languages are available for all fieldbuses! 5.
DeviceNet Modules HE800DNM650 & HE800DNS600 • MAN0577-03-en Logic Network View visible When this is selected possibility of diverting to the network mode without having to install the HSyCon with OPC. It is also possible to use the Watch List from the network mode. • Fast start ON/OFF Only valid for the OPC Server. • TAG tracing ON/OFF Only valid for the OPC Server. • OPC tracing ON/OFF Only valid for the OPC Server.
DeviceNet Modules HE800DNM650 & HE800DNS600 MAN0577-03-en CHAPTER 6: ONLINE FUNCTIONS 6.1. Introduction In this section all the functions that directly affect the Horner DeviceNet Modules are described, e.g. HE800DNS600 and HE800DNM650. Note: This will permit interruption of Devicenet communication and outputs can be switched ON or OFF. 6.2. Online to the Module First, the desired device must be chosen for downloading by a left mouse click on the symbol of the device. 6.3.
DeviceNet Modules HE800DNM650 & HE800DNS600 MAN0577-03-en Before the download is executed, the configuration is tested by the Configurator. The most common cause of error is overlapping of addresses in the process data image. This can be checked by calling up the address table with the View > Address Table menu point. If the issue of addresses in the process data image should be carried out automatically, then the Auto Addressing button in the Master Configuration window must be activated.
DeviceNet Modules HE800DNM650 & HE800DNS600 MAN0577-03-en Figure 21: Online > Firmware / Reset Click the button Reset to reset the device. 6.6. Device Info First the desired device must be chosen with a left mouse click on the symbol of the device. Then select the Online > Device Info menu in order to obtain further information on the selected device. The manufacturer date, the device number and the serial number of the device is retrieved and shown.
DeviceNet Modules HE800DNM650 & HE800DNS600 MAN0577-03-en 6.7. Automatic Network Scan After the Master device is configured, it is possible to scan the DeviceNet network for other devices (automatic network scan). This allows a very fast configuration, and detailed parameters for these devices can be changed later. To start an automatic network scan, please proceed as followed: 1. Create a new project: Select the menu File > New and DeviceNet. 2.
DeviceNet Modules HE800DNM650 & HE800DNS600 MAN0577-03-en Figure 24: Online > Automatic Network Scan (during scan) The network scan will take approx. 30 seconds. The network scan is still in progress and could not be interrupted until the status, shown in the field “Current Status”, is “Ready!”. When the scan is done, the devices found can be seen at the corresponding MAC ID address in the table. The master reads the following objects from the DeviceNet device (Slave) during the scan: Element Class.
DeviceNet Modules HE800DNM650 & HE800DNS600 MAN0577-03-en Example: Figure 25: Online > Automatic Network Scan (after scan) In our example in the figure above the automatic network scan detected a Horner device at MAC ID 1.
DeviceNet Modules HE800DNM650 & HE800DNS600 MAN0577-03-en Figure 26: Information on a device in the automatic scan window If this configuration is the required one, click on Automatic Configuration and select Yes when prompted. Afterwards the Automatic Configuration Window can be closed by clicking on Close. If the devices that were found in the configuration are not required, just click Close. To manually insert the devices, please go on with section Insert Device (Slave) on page 24. 6.8.
DeviceNet Modules HE800DNM650 & HE800DNS600 6.10. MAN0577-03-en Live List Select the menu Online > Live List for an overview of all devices physically present in the actual network constellation. Present devices are drawn in black, all other non present devices are drawn in grey. The live list works online. If a station is connected or disconnected, the result can be seen as soon as HSyCon collects the latest live list from the Master board.
DeviceNet Modules HE800DNM650 & HE800DNS600 6.13. MAN0577-03-en The Debug Window When started the debug session the configuration window changes into the debug window. The devices and the line between them are displayed in green or red colour depending on the established network communication. Figure 29: The Debug window If diagnostic information is available for a specific device, next to the device icon the text Diag appears in red.
DeviceNet Modules HE800DNM650 & HE800DNS600 MAN0577-03-en The individual bits in the Device Diagnostic have the following meaning: Device status flags in the Device Diagnostic Meaning No response The Device is configured but is not present in the network. Please check the physical connection between the Master and this Node. Check also the chosen baudrate and if this baudrate is supported by this device.
DeviceNet Modules HE800DNM650 & HE800DNS600 MAN0577-03-en 6.15. Global State Field First select the Master device by clicking on it. With the menu option Online > Global State Field opens a window in that cyclically statistic about the bus status and attached devices is put out.
DeviceNet Modules HE800DNM650 & HE800DNS600 MAN0577-03-en The first row displays the main state of the Master. It can have the state OPERATE or STOP. The next row display individual bus errors. A pending error is displayed with a red field. The meaning of the individual abbreviations is described in the following. Status Bits Meaning PDUP The device is involved in the duplicate MAC-ID check procedure, to check if other devices with the same address are connected to the network.
DeviceNet Modules HE800DNM650 & HE800DNS600 6.16. MAN0577-03-en Device Diagnostic After the debug started from this time HSyCon requests the status of all devices from the Master. If there is an error on a device the bus line to this Slave is drawn in red colour otherwise it is green. HSyCon also displays the letters Diag, if the device signals diagnostic information. Click on the device for more information. To activate the debug mode select the menu Online > Start Debug Mode.
DeviceNet Modules HE800DNM650 & HE800DNS600 6.17. MAN0577-03-en Extended Device Diagnostic The Extended Device Diagnostic helps to find bus and configuration errors when the HSyCon menu functions are of no further help. First the desired device must be chosen with a left mouse click on the symbol of the device. Then select the menu Online > Extended Device Diagnostic. This menu opens a list of diagnostic structures.
DeviceNet Modules HE800DNM650 & HE800DNS600 6.19. MAN0577-03-en Extended Device Diagnostic Device (Slave) PLC_TASK DNS_TASK Task / Task State Page PLC_Task Common Variables (Device) 94 DNS_Task Common Variables 95 DNS_TASK Receive Queue (Device) 96 DNS_TASK Transmit Queue (Device) 97 Table 16: Extended Device Diagnostic Device (Slave) 6.20.
DeviceNet Modules HE800DNM650 & HE800DNS600 6.21. MAN0577-03-en I/O Monitor This is an easy way of viewing and changing the first 32 Bytes of the process data image. Figure 34: Online > IO Monitor DEC/HEX converts the display of the input data. The output data are always in the decimal form. Enter the output value and then press Update. Always the first 32 input and output Bytes of the process description are shown, also when these Bytes have not been occupied by the configuration.
DeviceNet Modules HE800DNM650 & HE800DNS600 Fieldbus From Version PROFIBUS-DP Master 1.040 (Kombimaster) bzw. 1.140 (DP-Master) InterBus Master 2.040 CANopen Master 1.040 DeviceNet Master 1.058 MAN0577-03-en Table 18: Firmware for I/O Watch functions The following table lists the typical steps to use the I/O Watch monitor.
DeviceNet Modules HE800DNM650 & HE800DNS600 MAN0577-03-en 4. Left click on the module desired and the tags (I/Os) will be displayed in the center window of the Logical Network View. 5. Select with the left mouse button the tag/symbol desired and drag and drop them in the right window of the Logical Network View (IO Watch). 6. In the right window select the desired tag with the left mouse click to highlight it then right mouse click to open a menu. Select Start. A new window called IO Watch appears. 7.
DeviceNet Modules HE800DNM650 & HE800DNS600 MAN0577-03-en This menu selection enables the user to get/receive attribute related information from a Slave device. The user should be familiar with the supported Class, Instance, and Attribute entrees for the Slave device. These entries should be available within the suppliers data sheet for the Slave product. The return value will be represented in Hexadecimal. Clicking the ASCII button will change this value to ASCII text.
DeviceNet Modules HE800DNM650 & HE800DNS600 6.27. MAN0577-03-en Message Monitor The Message Monitor permits access to the Mailbox of the CIF. The usage of the Message Monitor assumes advanced knowledge from the user. First the Horner device must be chosen with a left mouse click on the symbol of the Horner device. Then call up the Online > Message Monitor menu. Figure 39: Online > Message Monitor A Message can be saved and retrieved and has the file suffix *.MSG.
DeviceNet Modules HE800DNM650 & HE800DNS600 MAN0577-03-en It is recommend to create a sub-directory MSG and to store the messages in it. Figure 40: Save a Message 6.28. Message Monitor for testing explicit messaging of DeviceNet In the following, the Message Monitor for reading and writing data via DeviceNet at the Master is described.
DeviceNet Modules HE800DNM650 & HE800DNS600 MAN0577-03-en CHAPTER 7: FILE, PRINT, EXPORT, EDIT AND VIEW 7.1. File 7.1.1. Open An existing project can be opened with File > Open. 7.1.2. Save and Save As When the file name is known, the configuration can be saved under the File > Save menu, otherwise the File > Save As menu must be selected. 7.1.3. Close The current project can be closed with File > Close. 7.2.
DeviceNet Modules HE800DNM650 & HE800DNS600 MAN0577-03-en The scope can be given with the Device Selection menu point. The following can be chosen: • All • From Station address to Station address • Selection of a device by means of its description If no option is selected and the OK button is pressed nothing will be printed out. It is like clicking the Cancel button. 7.3. Export Functions 7.3.1. DBM Export Select the File > Export > DBM menu in order to save the previously saved project file (*.
DeviceNet Modules HE800DNM650 & HE800DNS600 MAN0577-03-en 7.3.2.1. DataType Code D7 D6 D5 SubFlag Data Direction D4 D3 D2 D1 D0 D1 D0 Data Format according EN standard 0 blank space 1 Boolean 2 Integer 8 3 Integer 16 4 Integer 32 5 Unsigned Integer 8 6 Unsigned Integer 16 7 Unsigned Integer 32 8 Float 9 ASCII 10 String 14 Bit 0 emty space 1 input 2 output 0 start of a module 1 submodule Table 21: CSV Export > DataType Code 7.3.2.2.
DeviceNet Modules HE800DNM650 & HE800DNS600 MAN0577-03-en The DataPosition of the first module is 26 (M1). In the following field the DataType, DataSize and DataPosition of the following modules are shown. Note: If two or more Slave devices are connected to the Master, these are displayed in the next lines of the table. 7.4.
DeviceNet Modules HE800DNM650 & HE800DNS600 MAN0577-03-en 7.4.1. Delete To delete a Slave device, select the device by clicking on it. Then select the menu Edit > Delete. Before HSyCon deletes the Slave a security question appears. Figure 44: Security question delete device Note: When a device is deleted, the settings and the configuration of this device are deleted. 7.4.1. Replace With the menu Edit > Replace the Slave device can be replaced. Look in section Replace Slave at page 25. 7.5.
DeviceNet Modules HE800DNM650 & HE800DNS600 MAN0577-03-en Figure 46: View > Address Table 7.6. View Menu HSyCon 7.6.1. Logical Network View In the menu View > Logical Network View the user can activate or deactivate the network view by selecting its (with hook) or by not selecting it (without hook). The network view is used for example for the Start Options. 7.6.2. Toolbars In the menu View > Toolbars the user has the possibility to activate or deactivate the Toolbars Standard and Fieldbus.
DeviceNet Modules HE800DNM650 & HE800DNS600 MAN0577-03-en CHAPTER 8: ERROR NUMBERS 8.1. CIF Device Driver (Dual-port memory) Error Numbers (-1-49) This is the list of error numbers of dual-port memory access using the CIF Device Driver. Error Number Description -1 Driver: Board not initialized The communication board is not initialized by the driver. No or wrong configuration found for the given board, check the driver configuration. Driver function used without calling DevOpenDriver() first.
DeviceNet Modules HE800DNM650 & HE800DNS600 Error Number Description -15 Device: Error in dual port memory flags -16 Device: Send mailbox is full -17 MAN0577-03-en Device: Function PutMessage timeout No message could be send during the timeout period given in the DevPutMessage() function. If an interrupt is used, check the interrupt on the device and in driver setup.
DeviceNet Modules HE800DNM650 & HE800DNS600 Error Number Description -20 Device: Reset command timeout MAN0577-03-en The board is ready but not all tasks are running, because of an initialisation error. No data base is loaded into the device or a wrong parameter can causes that a task can't initialise. The device needs longer than the timeout period given in the DevReset() function. Using device interrupts. The timeout period can differ between fieldbus protocols.
DeviceNet Modules HE800DNM650 & HE800DNS600 Error Number Description -30 User: Driver not opened (device driver not loaded) MAN0577-03-en The device driver could not be opened. Device driver not installed. Wrong parameters in the driver configuration. If the driver finds invalid parameters for a communication board and no other boards with valid parameters are available, the driver will not be loaded.
DeviceNet Modules HE800DNM650 & HE800DNS600 MAN0577-03-en 8.2. CIF Serial Driver Error Numbers (-20 .. -71) This is the list of error numbers using the serial driver. Error Number Description -20 Driver: No COM port found or COM port already in use.
DeviceNet Modules HE800DNM650 & HE800DNS600 Error Number Description -50 User: Send message, timeout error -51 User: Could not send a message MAN0577-03-en Cable not connected. Wrong cable. Device does not respond.
DeviceNet Modules HE800DNM650 & HE800DNS600 MAN0577-03-en 8.3. RCS Error Numbers (4 .. 93) This is the list of error numbers returned by the RCS (Realtime Communication System), that is the operating system of Horner devices. The error number is returned in an answer message. Command messages and answer messages are used to communicate between the application (e.g. the System Configurator) and the Horner device. An example of this communication is the download of a configuration.
DeviceNet Modules HE800DNM650 & HE800DNS600 Error Number Description 40 No command free 41 Command unknown 42 Command mode unknown 43 Wrong parameter in the command 44 Message length does not match to the parameters of the command 45 Only a MCL does use this command to the RCS 50 FLASH occupied at the moment 51 Error deleting the FLASH 52 Error writing the FLASH 53 FLASH not configured 54 FLASH timeout error 55 Access protection error while deleting the FLASH 56 FLASH size does n
DeviceNet Modules HE800DNM650 & HE800DNS600 MAN0577-03-en 8.4. Database Access Error Numbers (100 .. 130) The following table lists the error numbers of the database access errors Error Number Description 100 Database already opened 101 Dataset could not be opened 103 Error while opening database occurred 104 No valid path name 105 No connection to data base. Call function DbOpen(). 106 Error in parameter 107 Error during opening a table 108 Nullpointer occurred 109 Table not opened.
DeviceNet Modules HE800DNM650 & HE800DNS600 MAN0577-03-en 8.5. Online Data Manager Error Numbers (1000 .. 1018) The following table lists the error numbers of the Online Data Manager. Error Number Description 1000 Driver OnlineDataManager not opened 1001 Initialization of the OnlineDataManager has failed 1002 No DriverObject found. OnlineDataManager Sub DLL not found. 1003 No DeviveObject found. Device not found.
DeviceNet Modules HE800DNM650 & HE800DNS600 MAN0577-03-en 8.7. Driver Functions Error Numbers (2501 .. 2512) The following table lists the error numbers of the Driver Functions of the Online Data Manager. Error Number Description 2501 OnlineDataManager Sub DLL not found 2502 Function missing 2503 'Read Thread' not created 2504 'Write Thread' not created 2505 'IO Thread' not created 2510 Function failed 2512 Assign reports error.
DeviceNet Modules HE800DNM650 & HE800DNS600 MAN0577-03-en 8.9. Data Base Functions Error Numbers (4000 .. 4199) The following table lists the error numbers of the converting functions.
DeviceNet Modules HE800DNM650 & HE800DNS600 Error Number Description 4030 Path too long 4031 Directory changed 4032 Directory created 4034 Length of converting stream is 0 4035 Non equal data set found 4036 Non equal data set found 4037 Non equal data set found 4038 Data set has length 0 4039 The function DbmInit has assigned a Zero pointer during RCS initialisation 4040 Printer not ready 4041 The data base is used from another function 4042 New length of data base is smaller than
DeviceNet Modules HE800DNM650 & HE800DNS600 Error Number Description 4061 The data base was transmitted into the FLASH 4062 Set 0 contains no structure definition 4063 Set 0 can not be deleted 4064 Error during execution of a ODBC data base access 4065 Initializing of DBM through RCS had no success 4066 Passed data length incorrect 4067 Sorting function not linked 4068 Error in function parameter MAN0577-03-en 4069 Error from ODBC table 4070 No free handle available.
DeviceNet Modules HE800DNM650 & HE800DNS600 MAN0577-03-en Error Number Description 4082 More than 32 tables should be created 4083 No entry in element szSourceFile 4084 ODBC connection initialisation not possible. This could happen when in file ODBCINST.INI in section [Microsoft Access Driver (*.mdb)] is no valid path to ODBCJT16/32.DLL.
DeviceNet Modules HE800DNM650 & HE800DNS600 MAN0577-03-en 8.10. Converting Functions Error Numbers (5001 .. 5008) The following table lists the error numbers of converting functions. Error Number Description 5000 Function PackLongToByteShort: Not enough space in pvD (Number of elements greather than reserved memory) 5001 Function PackLongToByteShort: Not enough space in pvD.
DeviceNet Modules HE800DNM650 & HE800DNS600 MAN0577-03-en CHAPTER 9: EXPLICIT MESSAGING USING DNM650 9.1 General The DNM650 supports both POLLED and EXPLICIT connections. Explicit Messaging requires a great deal of overhead in both the DNM650 and the OCS. Multiple PLC scans may be required to access the required data between the OCS and the DNM650. As a result, Explicit Messages should be reserved for access to infrequently needed data, such as configuration or tuning parameters only.
DeviceNet Modules HE800DNM650 & HE800DNS600 REGISTER %AQ1 %AQ2 %AQ3 %AQ4 DESCRIPTION Start of Transmit Buffer Number of Bytes to Transmit Start of Receive Buffer Receive Buffer Allocation Size MAN0577-03-en VALUE 101 7 51 20 In the following example we want to write the polled expected packet rate to the node at MACID 3, we also want to locate the transmit buffer at %R101, the receive buffer at %R51, we will also allocate 20 bytes to the receive buffer.
DeviceNet Modules HE800DNM650 & HE800DNS600 MAN0577-03-en Note: The number of bytes received value is the number of bytes of the message placed in the receive buffer including the two bytes devoted to the number of bytes received. 9.4 Explicit Message Errors In the case that an Explicit Message requests a function that cannot be performed by the referenced node, an Explicit Error Message will be returned.
DeviceNet Modules HE800DNM650 & HE800DNS600 MAN0577-03-en APPENDIX: A. EXTENDED DEVICE DIAGNOSTIC MASTER On the following pages the task state structures of the DeviceNet Master are described. A.1. PLC_TASK Common Variables Figure 47: PLC_TASK Common Variables Variable Meaning Version Compiled Hardware Task State Task State Handshake Counter Counter for the performed process data handshakes Handshake Mode This value represents the actual handshake mode between application and CIF.
DeviceNet Modules HE800DNM650 & HE800DNS600 Variable MAN0577-03-en Meaning Received message number of received CAN-Messages Sent messages number of sent CAN-Messages Receive overruns this counter is incrementing when to many incoming CAN messages overload the Master.
DeviceNet Modules HE800DNM650 & HE800DNS600 A.3. MAN0577-03-en DNM_TASK Device Running States Figure 49: DNM_Task Device Running States To handle the Slave devices in their different states the Master device has a Slave device handler running, where each Slave device has its own actual running state. HSyCon interprets what the actual state of each Slave and enters these states on the screen in textual form. A.4. DNM_Task Global State Field See section Global State Field at page 52. A.5.
DeviceNet Modules HE800DNM650 & HE800DNS600 A.6. MAN0577-03-en DNM_Task Receive Queue Figure 51: DNM_Task Receive Queue The Receive Queue is used to monitor the receive transmission queue of the internal CAN controller. Variable Meaning bRear A pointer to where the next message will be dequeue from the queue body bFront A pointer to where the next message will be stored bInner The actual number of stored messages Table 45: Receive Queue A.7.
DeviceNet Modules HE800DNM650 & HE800DNS600 MAN0577-03-en The Transmit Queue is used to monitor the transmission queue of the internal CAN controller.
DeviceNet Modules HE800DNM650 & HE800DNS600 A.9. MAN0577-03-en DNM_Task Timeout Counter Figure 54: DNM_Task Timeout Counter The Timeout Counter shows the number of timeouts for each Slave device configured in the DeviceNet bus system. A.10. DNM_Task Init Counter Figure 55: DNM_Task Init Counter The Device init counter is incremented whenever the Slave device is initialized.
DeviceNet Modules HE800DNM650 & HE800DNS600 MAN0577-03-en B. EXTENDED DEVICE DIAGNOSTIC DEVICE (SLAVE) On the following pages the task state structures of DeviceNet Slaves are described. B.1. PLC_Task Common Variables (Device) Figure 56: PLC_Task Common Variables (Slave) Variable Meaning Version Compiled Hardware Task State Task State Handshake Counter Counter for the performed process data handshakes Handshake Mode This value represents the actual handshake mode between application and CIF.
DeviceNet Modules HE800DNM650 & HE800DNS600 MAN0577-03-en B.2.
DeviceNet Modules HE800DNM650 & HE800DNS600 MAN0577-03-en B.3. DNS_TASK Receive Queue (Device) Figure 58: DNS_TASK Receive Queue (Device) The Receive Queue is used to monitor the receive transmission queue of the internal CAN controller.
DeviceNet Modules HE800DNM650 & HE800DNS600 MAN0577-03-en B.4.
DeviceNet Modules HE800DNM650 & HE800DNS600 MAN0577-03-en NOTES Page 98 of 98 EO 09-0009
