Home

DTM for Hilscher DeviceNet Slave Devices

Contents

1. Table 29 Descriptions of the Dialog Panes Extended Diagnosis Online Connection to the Device Note Accessing the Extended Diagnosis dialog panes of the DeviceNet Slave DTM requires an online connection from the DeviceNet Slave DTM to the DeviceNet Slave device For further information refer to section Connecting Disconnecting Device on page 66 DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOC0910030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Extended Diagnosis 73 113 8 2 Task Information Task states Identifier Major version Minor version Maximum Packet size Default Que Unique identifier Init result The displayed Vales depend from the corresponding task Figure 44 Extended Diagnosis gt Folder Name gt Task Information Example Display Name Description Default Queue Queue handle which is accessible via DPM by mailbox UUID Unique user ID 16 Byte indicator used for task identification and its affiliation e g to a stack therein different identification data are coded in Init result Error Code 0 no Error The description of the error codes can be found in this manual or in the corresponding software reference manuals Table 30 Extended Diagnosis gt Folder Name gt Task Information DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOC0910030I08EN
2. ccccececececececececececeaeaeaeaeecececes 100 10 5 1 Elis aio a ee nee 100 10 5 2 Generic Driver Error COdeS aii Andere 101 10 5 3 Genente Device Error OJOS a Anneliese 102 10 6 Error COdeS MeL DIVER dd eo 103 10 6 1 CIEX API Transport Error COdeS cm ccodccntacas oir ea we shavzatee sa 103 10 6 2 CIFX API Transport Header State Error Codes occoocccocccconcccocnconcncocnccncnnnnnnos 103 10 7 ODM Error Codes DBM V4 0 ccc cc ccccccecccccececececececcceneaeaeacacacuceeuceneneneaeavatererenenenens 104 11 APPENDIX er ed 108 11 1 USERS a ne 108 11 1 1 SEUNG PP eier esse 108 11 1 2 A O A 108 11 2 Fe STS CSS o ee 109 11 3 LAST Ol FIG UNC S ea in 109 11 4 ISOLDE renee A 110 11 5 A een Reese 111 11 6 BONES see cate ak ae en es se seen 113 DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOCO910030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Introduction 9 113 1 Introduction 1 1 About this Manual This manual provides information on how to set and configure the device parameters of a netX based DeviceNet Slave device within a FDT Framework using the DeviceNet Slave DTM and what can be read from the diagnosis panes In a network project the DeviceNet Slave DTM can be dropped e tothe root line Stand Alone Slave e or to the Master busline of a DeviceNet Master DTM Note This manual edition first provides information for the case if the Devic
3. Device Hardware Port Of f2 3 Slot number Channel Protocol Access path fl PROFIBUS 1 20148 CIF Device Driver PROFIBUS DP Master acis Cho Access path 368BEC5B 0692 4C0E B449 64F624E7 44F 4 ci sS Cho Figure 15 Device Assignment Selecting the Device The name of the device class is displayed Example for a device with firmware one Device is selected detected via the cifX Device Driver the following data are displayed Note After the firmware download has been completed for the devices which have been Inthe column Channel Protocol the data for the firmware for the used channel Inthe column Access path or under Access path below in the dialog pane the data cifX OtoN _Ch 0t03 cifX OtoN board number 0 to N Ch 0t03 channel number 0 to 3 Select Apply to apply the selection Or select OK to apply the selection and to close the DTM interface dialog 6 Connect the DTM to the device using the context menu right mouse click For further information how to establish an online connection from the DeviceNet Slave DTM to the DeviceNet Slave device refer to section Connecting Disconnecting Device on page 66 DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOCO910030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Settings 43 113 3 5 Firmware Download Using the Firmware Download dialog a firmware can be transferr
4. 3 In the selection window mark the firmware file to be loaded using the mouse In the selection window under Firmware the name and the version of the firmware are displayed 4 Inthe selection window select the Open button Y A validation is made whether the selected firmware file is suitable for the DeviceNet Slave DTM gt In the dialog pane Firmware Download during the validation Download is grayed out Y The selection window is closed 5 In the dialog pane Firmware Download click to the Download button DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOC0910030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Settings 46 113 to download the firmware Firmware is not valid for the selected device If a firmware file is selected which is not valid for the assigned device the request Select Firmware File will be displayed Select Firmware File Invalid Firmware For the assigned device The hardware options do not match Required LAhlopen Firmware File PROFIBLUS The protocol classes do not match Required C4Nopen Firmware File PROFIBUS DP Shall the Firmware File nevertheless be applied For the download Yes Figure 18 Request Select Firmware File Example gt Answer to the request with No Mame Name ofthe Firmware File Version Version aed Auld Version of fhe Firmware AN CAUTION The firmware downlo
5. Figure 5 Default Driver cifX Device Driver for PC cards cifX Parameter Meaning Driver Name of the driver for more details see descriptions hereafter Version ODMV3 Version of the respective driver ID of the driver driver identification Table 10 Driver Selection List Parameters To establish a connection from the DeviceNet Slave DTM to the DeviceNet Slave device verify if the default driver is checked and respectively check another driver or multiple drivers 3 3 1 Verify or adapt Driver Settings Proceed as follows 1 Select Settings gt Driver in the navigation area dv The Driver dialog pane is displayed with the available drivers and the setting for the default driver Driver MO E vesn EA CIFX Device Driver 1 101 1 9801 1368BEC5B 0E92 4C0E 8449 64F62AE7AAFA DL 35Gateway Driver for netX V3 x 0 9 1 2 78 7CD3A9 4CF6 4259 8E40 109B6A6BEA9 1 0 nets Driver 1 103 2 5183 IB54C80C7333 4135 84905 5E 12FCRSEE62 Figure 6 Default Driver cifX Device Driver for PC cards cifX example Driver river E PF O CIFX Device Driver 1 101 1 9801 358BEC 5B 0E92 4C0E B4459 64F62AE7AAFA O 35Gateway Driver for netX V3 x 0 9 12 1787CD3A9 4CF6 4259 8E4D 109B5ASBEAII nets Driver 1 103 2 5183 B54C8CC7 F333 4135 8405 6E 12FCS8EE62 Figure 7 Default Driver netX Driver for Hilscher devices except for PC cards cifX example 2 Verify that the default driver is checked gt Verify that the defaul
6. Hilscher 2009 2013 Settings 37 113 3 4 Device Assignment Note In the Device Assignment dialog pane you first must assign the DeviceNet Slave device to the DeviceNet Slave DTM by checking the check box This is essential to establish an online connection from the DeviceNet Slave DTM to the DeviceNet Slave device later as described in section Connecting Disconnecting Device on page 66 Therefore in the Device Assignment dialog pane you scan for the DeviceNet Slave device and select it If the device did not get a firmware or shall get a new firmware 1 first you scan for the device with or without firmware and select the device 2 then you download a firmware to the device and 3 subsequently you scan for the device with firmware once more and select the device again y Important For a 2 channel device consecutively channel 1 or channel 2 must be assigned to the DTM 3 4 1 Scanning for Devices 1 Select Settings gt Device Assignment in the navigation area dv The dialog pane Device Assignment is displayed Scan progress 3 5 Devices Current device AAA Device selection suitable only Device Hardware Port 0 1 2 3 Slot number Channel Protocol Access path O PROFIBLIS 1 20148 CIFX Device Driver Undefined Undefined Aci SYS Access path Figure 11 Device Assignment detected Devices The name of the device class is displayed Example for a device without firmware 2
7. Selecting the Device with or without firmware If not yet a firmware was loaded to the device Firmware Download In the Slave DTM configuration dialog select Settings gt Firmware Download select Browse select a firmware file select Open select Download and Yes In the Slave DTM configuration dialog select Settings gt Device Assignment select Scan select the Slave device with loaded firmware and defined system channel therefore check the appropriate checkbox select Apply close the Slave DTM configuration dialog via OK Selecting the Device once more with Firmware Configure the Slave device Double click to the device icon of the Slave The Slave DTM configuration dialog is displayed In the Slave DTM configuration dialog select Configuration gt General set UCMM and Fragmentation Timeout select Configuration gt Connection configure the device connection select Configuration gt Parameter set the parameter data of the device Configuring Slave 49 Parameter General Settings 51 Connection Configuration 53 select Configuration gt Device Settings Parameter 61 set the Device Settings close the Slave DTM configuration dialog via OK Device Settings 62 Configure the Master device via the DeviceNet Master DTM netx See Operating Instruction Manual DTM for DeviceNet Master devices Depending of the frame application For t
8. e USB COM connector for the USB connection and for the serial connection RS232 and e TCP IP connector for the Ethernet connection DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOC0910030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Settings 30 113 3 3 4 Configuring netX Driver The following steps are required to configure the netX Driver USB RS232 Connection To set the driver parameters for an USB RS232 connection note Note Adjust the driver parameters netX Driver USB RS232 only if they differ from the default settings After saving the changed driver parameters these parameters are used for the device assignment when scanning devices For setting the driver parameters for an USB connection or a serial connection 1 Select Settings gt Driver gt netX Driver gt USB RS232 Connection gt Set the driver netX Driver USB RS232 parameters TCP IP Connection For setting the driver parameters for a TCP IP connection 1 Select Settings gt Driver gt netX Driver gt TCP Connection Set IP Address of the device 2 gt Add an IP Range via Select IP Range 3 Under IP Range Configuration gt IP Address enter the IP Address of the device Use IP Range is unchecked Or 4 Set IP Range Check Use IP Range gt Under IP Range Configuration gt IP Address enter the start address left side and the ending address
9. Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Extended Diagnosis 74 113 8 3 IniBatch Status Task states Communication Channel Current State Error IniBatch Result Mo DBM File OpenCibm Result 24975 SendPacket Result 0 Confirmation Result Last Packet Mumber Last Packet Command Last Packet Length Last Packet Destination OOOO QQ Figure 45 Extended Diagnosis gt Folder Name gt IniBatch Status Example Display Name Deseripti n OOOO Communication Channel Number of the communication channel used by the device Current State Idle IniBatch packets in progress Retrying to send last packet Error IniBatch Result Ok No DBM file No Packet table No data set available Data set is shorter than packet length Packet Buffer is shorter than Packet length Invalid packet destination Logical queue not defined Send packet failed Too many retries Error in confirmation packet status OpenDbm Result Error when opening the IniBatch data base Under OpenDbm Result the error code is typed in when IniBatch Result No DBM file 1 is SendPacket Result Error when sending a packet Under SendPacket Result the error code is typed in when IniBatch Result send packet failed 8 is Confirmation Result Confirmation error when sending packets Under Confirmation Result the packet specific error code from the ulSta is typed in when IniBatch Result Error in confi
10. Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Getting started eee 19 118 Short Description For detailed information Page see section 5 Verify or adapt In the Slave DTM configuration dialog Settings for Driver and 25 Driver Settings select Settings gt Driver Device Assignment e Note For PC cards cifX the cifX da 27 Device Driver is preset as a default m driver For all the other Hilscher devices the netX Driver is preset as a default driver Use the cifX Device Driver if the DeviceNet Slave DTM is installed on the same PC as the DeviceNet Slave device Use the netX Driver to establish a USB Serial RS232 or TCP IP connection from the DeviceNet Slave DTM to the DeviceNet Slave device The 3SGateway Driver for netX V3 x is used only in relationship with CODESYS To search for devices you can check one or multiple drivers simultaneously Verify that the default driver is checked If necessary check another driver or multiple drivers Configure Driver If you use the netX Driver you respectively must configure it Configuring netX Driver 30 For netX Driver and communication via TCP IP set the IP address of the device Select Settings gt Driver gt netX Driver gt TCP Connection Via add an IP range Under IP Address enter the IP Address of the device or an IP range Click Save Adjust the driver parameters netX Driver USB RS232 only if they differ from the default
11. oe hilscher COMPETENCE IN COMMUNICATION Operating Instruction Manual DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices Hilscher Gesellschaft fur Systemautomation mbH www hilscher com DOC0910030I08EN Revision 8 English 2013 09 Released Public Table of Contents 2 113 Table of Contents 1 INTRODUCTION Ess 5 1 1 ABOULINIS MaNUdl e nuria eri 5 Tedi Descriptions of the Dialog Pane 2 22z00220200000000000ennnnonnnnnnennnnnn nennen 5 1 12 Onlinehelp 6 1 1 3 LISEOT REVISIONS a ea 6 1 1 4 Conventions in this Manual coi an a 7 1 2 E ea a en a a Wat 8 1 2 1 ECOPMIONL Email 8 1 2 2 Important Notes ina dsd dia 8 1 2 3 EXGlUSiOn OF iD INDY caia 9 1 2 4 Valais 9 1 2 5 EXON Requisito 10 1 2 6 Registered Trademarks ccccccsscccssecesesececsececeseeceseccsaseessaeeessueeecseeensuesensees 10 1 3 About DeviceNet Slave DTM iio sien eek Bi 11 1 3 1 Requirements ns 12 1 4 Dialog Structure of the DeviceNet Slave DTM u02220022002snnennnenenennnenenenn 13 1 4 1 General Device Information u000444400nennne nennen nennen nennen nennen nnennnnennn 14 1 4 2 Navigation ACA casino 14 1 4 3 Un A a Eo EE O E 15 1 4 4 OK Cancel ApplY anda li ne een ale ea 16 1 4 5 TOD ee Se ee ee Set Oeoe 16 1 4 6 Slalle Balz ee 17 2 GETTING STARTED 02 0022002s0ssnunsnenenennnennnnnnonnnenenennnennnnnnunnnennnennn
12. 1 1 4 Conventions in this Manual Notes operation instructions and results of operation steps are marked as follows Notes Important lt important note gt Note lt note gt S lt note where to find further information gt Operation Instructions 1 lt instruction gt 2 lt instruction gt or gt lt instruction gt Results gt lt result gt DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOC0910030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Introduction 8 113 1 2 Legal Notes 1 2 1 Copyright Hilscher 2009 2013 Hilscher Gesellschaft f r Systemautomation mbH All rights reserved The images photographs and texts in the accompanying material user manual accompanying texts documentation etc are protected by German and international copyright law as well as international trade and protection provisions You are not authorized to duplicate these in whole or in part using technical or mechanical methods printing photocopying or other methods to manipulate or transfer using electronic systems without prior written consent You are not permitted to make changes to copyright notices markings trademarks or ownership declarations The included diagrams do not take the patent situation into account The company names and product descriptions included in this document may be trademarks or brands of the respective owners and ma
13. 4 72 37 98 40 E Mail fr support hilscher com India Hilscher India Pvt Ltd New Delhi 110 065 Phone 91 11 26915430 E Mail info hilscher in Italy Hilscher Italia S r l 20090 Vimodrone Ml Phone 39 02 25007068 E Mail info hilscher it Support Phone 39 02 25007068 E Mail it support hilscher com 113 113 Japan Hilscher Japan KK Tokyo 160 0022 Phone 81 0 3 5362 0521 E Mail info hilscher jp Support Phone 81 0 3 5362 0521 E Mail jp support hilscher com Korea Hilscher Korea Inc Seongnam Gyeonggi 463 400 Phone 82 0 31 789 3715 E Mail info hilscher kr Switzerland Hilscher Swiss GmbH 4500 Solothurn Phone 41 0 32 623 6633 E Mail info hilscher ch Support Phone 49 0 6190 9907 99 E Mail ch support hilscher com USA Hilscher North America Inc Lisle IL 60532 Phone 1 630 505 5301 E Mail info hilscher us Support Phone 1 630 505 530 1 E Mail us support hilscher com DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOCO910030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013
14. Connection Configuration on page 53 Parameter on page 61 and to lt section Device Settings on page 62 of this document 4 2 2 Slave DTM at the Master busline If in the network project the DeviceNet Slave DTM is dropped to the Master busline of the DeviceNet Master DTM General 1 Set UCMM and Fragmentation Timeout gt Select Configuration gt General in the navigation area Connection 2 Configure the device connection gt Select Configuration gt Connection in the navigation area Parameter 3 Set the parameter data of the device gt Select Configuration gt Parameter in the navigation area Device Settings 4 Setthe Device Settings gt Select Configuration gt Device Settings in the navigation area gt Under Start of Bus Communication select Automatically by device or Controlled by application option gt Under Application Monitoring gt set Watchdog time Close Slave DTM Configuration Dialog 5 Click OK in order to close the Slave DTM configuration dialog and to store your configuration Confiquration Download to the DeviceNet Slave Device Note In order to transfer the configuration to the DeviceNet Slave device download the data of the configuration parameters in the DeviceNet Slave device See section Download Configuration on page 67 Further Information PEE For more information refer to section General Settings on page 51 Connection Configuration on page 53 Parameter on p
15. For COM based application like the ODM Server and ODM drivers a common error definition is used similar to the Microsoft Windows HRESULT definition Error Code Structure COM Errors are HRESULTs which are 32 bit values using the following layout 33222222222211 1 1 1 1 1 1 1 1 1098765432 10987654321 09876543210 Sev c R Facility Code where Sev ig the severity code 00 Success 01 Informational 10 Warning 71 Error C is the Customer code flag R is a reserved bit Facility is the facility code Code is the facility s status code In this common error definition several error code regions are already reserved by Windows itself the ODM and some other modules DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOCO910030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Error Codes 91 113 10 2 Overview Error Codes General Hardware Errors RCX General Task 0xC02B0001 to OxC02B4D52 RCX Operating System RCX Common Status amp Errors Codes 0x00000000 to 0xC002000C RCX Status amp Error Codes 0x00000000 to 0xC0000008 ODM Server General ODM Error Codes 0x8004C700 to 0x8004C 761 General ODM Driver Error Codes 0x8004C7A0 to 0x8004C7C2 ODM Drivers cifX Driver Specific ODM Error 0x8004C0
16. descriptions DeviceNet Slave DTM Folder Name Section Navigation Area A General Settings 3 Settings Connection Configuration 3 Configuration Poll Connection ia General Connection Pall Change of State Connection Cyclic Connection Change of state Bit Strobe Connection Cyclic Parameter Bit Strobe Parameter Device Settings Device Description Application Monitoring Device Settings Start of Bus Communication Navigation Area Configuration Table 16 Dialog Panes Configuration Notice the descriptions in the section Configuration Steps on page 18 gt Note In order to transfer the configuration to the DeviceNet Slave device download the data of the configuration parameters in the DeviceNet Slave device See section Download Configuration on page 67 DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOC0910030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Configuration 49 113 4 2 Configuring Slave Parameters dh Important For a 2 channel device consecutively channel 1 or channel 2 each must be configured individually The steps provided in the following two sections are alternatively required for the two cases listed hereafter to configure the parameters of the DeviceNet Slave device using the DeviceNet Slave DTM e Slave DTM at the Root Line Stand Alone Slave e and Slave DTM at the Master busline 4 2 1 Slave DTM at t
17. s UCM Fragmentation timeout i700 ms Enable Address Switch enabled Figure 26 General Settings Enable Address Switch Slave DTM at the Root Line Stand Alone Slave Exmaple COMX 10XX DNS DNS Enable Defines if the MAC ID is configured in the configuration software or at the Default Address address switch CIFX DN DNS Switch If checked the MAC ID is configured at the address switch COMX 100XX The parameter Enable Address Switch with the setting checked can only DN DNS i NJ 100XX be used for COMX 10XX DNS DNS DN DNS unchecked COMX 10XX DNS DNS checked Table 18 General Settings Enable Address Switch DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOC0910030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Configuration 53 113 4 4 Connection Configuration DeviceNet allows establishing several kinds of Connections between devices In DeviceNet a device Slave is mapped as a collection of objects These objects communicate via different connection types which you can adjust under Connection w Poll Connection Cyclic Connection Bit Strabe Connection Figure 27 Configuration Dialog Connection In the Connection dialog a connection type or a combination of types can be selected Please note that a device has not to support all types of lO connections Connection types which are not supported by th
18. 1 CANopen nia 20022 CIFX Device Driver Undefined Undefined cifx0_S5YS Access path IJDBBECSB 0E92 4C0E 6940 64P620E74 APA cisa Cha Figure 14 Device Assignment Selecting the Device The name of the device class is displayed Example for Devices with and without Firmware one Device is selected detected via the cifX Device Driver the following data are displayed gt Note After the firmware download has been completed for the devices which have been Inthe column Channel Protocol the data for the firmware for the used channel Inthe column Access path or under Access path below in the dialog pane the data cifX OtoN _Ch 0t03 cifX OtoN board number 0 to N Ch 0t03 channel number 0 to 3 Select Apply to apply the selection Or select OK to apply the selection and to close the DTM interface dialog 6 Connect the DTM to the device using the context menu right mouse click DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOCO910030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Settings 42 113 Or suitable only 1 Under Device Selection select suitable only 2 Select Scan gt In the table all devices are displayed which can be connected to the DeviceNet Slave DTM via the preselected drivers 3 Check the appropriate device Scan progress 5 5 Devices Current device Device selection suitable only z
19. 3 are supported The documentation of the used device gives information whether this option is to be used or not Fragmen Fragmentation Timeout Expl Message Timeout If an IO data tation transmission or an Explicit Message is larger than 8 byte this must be Timeout transferred fragmented in the DeviceNet in several telegrams The Fragmentation Timeout specifies how long the Master waits until a Slave answers a fragmented telegram Note Small values can lead to communication disturbances Enable Refer to section Enable Address Switch on page 52 of this document Address Switch Table 17 General Settings Attributes of the device identification DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOCO910030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Configuration 52 113 Mw Verify Device ID i Vendor ID w Device Type W Product Code Figure 25 General Settings Verify Device ID The function Verify Device ID compares the device description in the EDS file of the device with the existing hardware if the device characteristics of the EDS file agree with those of the hardware The check is made for the selected attributes in each case 4 3 1 Enable Address Switch EHEN 63 Enable Address Switch Baud rate FE cra Groupa vw Fragmentation timeout 1700 ms Enable Address Switch disabled een W Enable Address Switch Baud rate 125 kBits
20. UINT32 From Request Destination Queue Reference ulSrcId UINT32 From Request Source Queue Reference ulLen UINT32 Packet Data Length in Bytes 4 20 x n IfulSta RCX_S OK O Otherwise ulld UINT32 From Request Packet Identification as Unique Number ulSta UINT32 See Below Status Error Code see Section 6 UINT32 Confirmation 0x00002F0D Get I O Data Information UINT32 Extension 0x00000000 No Sequenced Packet 0x00000080 First Packet of Sequence Ox000000CO Sequenced Packet 0x00000040 Last Packet of Sequence ulRout UINT32 Z Routing Information Don t Care Don t Use tData Structure Information XT UINT32 O 10 Number n of Block Definitions Below tIoBlockfn Array of I O Block Definition Structure s CA Structure RCX DPM IO BLOCK INFO Packet Structure Reference GET DPM I O INFORMATION CONFIRMATION define RCX GET DPM IO INFO CNE RCX GET DPM IO INFO REQ 1 typedef struct RCX DPM IO BLOCK INFO Ttag JINT32 ulSubblockIndex index of sub block JINT32 ulType type of sub block JIINT16 usFlags flags of the sub block JINT16 usReserved reserved JINT32 ulOffset offset of I O data in bytes JINT32 ulLength length of I O data in bytes RCX DPM IO BLOCK INFO T Figure 58 Packet Description GET DPM IO INFO CONFIRMATION _ Futher information on the packet description for this example are comprised in the Dual Port Memory Manual in section G
21. configuration is accessible by the user or read only To access the Settings Configuration Device Description and Diagnosis panes of the DeviceNet Slave DTM you do not need special user rights Also all users can select the decimal or hexadecimal Display mode or sort table entries Configuration panes you need user rights for Maintenance for Planning Engineer or for Administrator Note To edit set or configure the parameters of the Settings and The Device Description panes do not contain any editable elements The indicated values in are only for information purposes The following tables give an overview of the user right groups and which user rights you need to configure the single parameters 11 1 1 Settings ee a ance Engineer trator Driver OK Verify or adapt Driver Settings J XXX Configuring netX Driver XX Device Assignment Selecting the Device with or without firmware Selecting the Device once more X X with Firmware Table 55 Settings D Displaying X Editing Configuring 11 1 2 Configuration e pe er ee ance Engineer trator General Setings oo loo KK x Y Connection Configuration oo ow x x x PoliComnecti n O DY XXX Oya Conmecten nm eo x h Biirobe Connection low x x Parameter Device Settings Table 56 Configuration D Displaying X Editing Configuring D X Displaying all limited Editing or Configuring DTM for H
22. dangerous environments requiring fail proof control mechanisms Use of the software in such an environment occurs at your own risk No liability is assumed for damages or losses due to unauthorized use 1 2 4 Warranty Although the hardware and software was developed with utmost care and tested intensively Hilscher Gesellschaft f r Systemautomation mbH does not guarantee its suitability for any purpose not confirmed in writing lt cannot be guaranteed that the hardware and software will meet your requirements that the use of the software operates without interruption and that the software is free of errors No guarantee is made regarding infringements violations of patents rights of ownership or the freedom from interference by third parties No additional guarantees or assurances are made regarding marketability freedom of defect of title integration or usability for certain purposes unless they are required in accordance with the law and cannot be limited Warranty claims are limited to the right to claim rectification DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOCO910030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Introduction 10 113 1 2 5 Export Regulations The delivered product including the technical data is subject to export or import laws as well as the associated regulations of different counters in particular those of Germany and the USA The so
23. in the Device Assignment pane if not yet a firmware was loaded to the device 6 Scan for the device with firmware once more 7 Select the device with firmware once more 4 An overview of the descriptions for these steps you find in the section Overview Settings on page 24 8 Inthe DTM interface dialog select the OK button to apply the selection and to close the DTM interface dialog 9 Puta right click on the DeviceNet Slave device icon 10 Select the Connect command from the context menu dv The DeviceNet Slave device now is connected to the DeviceNet Slave DTM via an online connection In the network view the device description at the device icon of the Slave device is displayed with a green colored background DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOC0910030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Online Functions 67 113 Disconnecting Device To disconnect an online connection from the DeviceNet Slave device to a DeviceNet Slave DTM take the following steps 1 In the DTM interface dialog select the OK button to close the DTM interface dialog Right click on the DeviceNet Slave device icon a Select the Disconnect command from the context menu gt In the network view the device description at the device icon of the Master is not any more displayed with a green colored background Now the DeviceNet Slave device is disc
24. load the Watchdog Time again to the fourfold value of the Expected Packet Rate DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOC0910030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Configuration 60 113 The Watchdog Timeout Action defines the device behavior when the watchdog timer in the device Slave expires The following actions are adjustable e Timeout The connection transitions to the timeout state and remains in this state until it is Reset or Deleted e Auto reset The connection remains in the established state and immediately restarts the Inactivity Watchdog timer e Auto delete The connection class automatically deletes the connection if it experiences an Inactivity Watchdog timeout To reset the defalut values from the EDS file click eu ts DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOC0910030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Configuration 61 113 4 5 Parameter In the Parameter dialog the parameter data of the device can be edited If default parameters are configured in the EDS file for this device these are inserted automatically Some of devices need further parameterization data to change for example a measurement limitation or a value range These data are device specific and their functionality can not be explained at this point The explanati
25. of output 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 in there is assigned to one device address MAC ID in the network Herewith 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 sent back from each Slave after a bit strobe command was received is limited to 8 bytes in length Bit strobe usage causes therefore a reduced bus loading than poll connections Timing Expected Packet Rate 200 ms watchdog Timeout Action Timeout Figure 37 Bit Strobe Connection Timing The Expected Packet Rate one for each connection is always transferred to the device before starting and doing the I O transfer The fourfold value is used by the device later to reload its Watchdog Timer If no data production of the remote station takes place within this time so the connection changes into a watchdog timeout error Incoming data productions of the remote station
26. on the bus after the initialization has been ended When Controlled by application is selected the application program must activate the data exchange on the bus Note The setting options under Start of Bus Communication for client specific variants of the configuration software can differ from the setting options displayed here 4 6 2 Application Monitoring Application monitoring Watchdog time 1000 ms Figure 41 Device Settings gt Application Monitoring The Watchdog time determines the time within which the device watchdog must be re triggered from the application program while the application program monitoring is activated When the watchdog time value is equal to O the watchdog is deactivated and the application program monitoring is deactivated too The permissible range of values of the watchdog time is 20 to 65535 By default the watchdog time value equals to 1000 ms Watchdog time Range of Value Value Permissible range of values 20 65535 ms Default 1000 ms The software watchdog is deactivated Table 21 Range of Value Value for the Watchdog time Note The setting options under Application Monitoring for client specific variants of the configuration software can differ from the setting options displayed here DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOCO910030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Device De
27. settings gt Note e The cifX Device Driver requires no configuration e The configuration of the 3SGateway Driver for netX V3 x is carried out via the CODESYS surface Assign Slave Assign the device to this driver Selecting the Device with 40 device with or In the Slave DTM configuration dialog or without firmware without select Settings gt Device Assignment firmware select a Slave device with or without firmware therefore check the appropriate checkbox select Apply Select and If not yet a firmware was loaded to the device Firmware Download 43 download In the Slave DTM configuration dialog firmware select Settings gt Firmware Download select Browse select a firmware file select Open select Download and Yes DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOCO910030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Getting started 20 113 Short Description For detailed information Page see section 9 41 Assign Slave device once more with firmware and system chanal Inthe Slave DTM configuration dialog select Settings gt Device Assignment select Scan select the Slave device with loaded firmware and defined system channel therefore check the appropriate checkbox select Apply close the Slave DTM configuration dialog via OK For repeated download this step is omitted Configure Slav
28. support requested data type CIFX_TRANSPORT_DEVICE_ UNKNOWN Ox800E0005L Device not availableunknown CIFX_TRANSPORT_KEEPALIVE OxXx800E000AL Device connection monitoring error Keep alive CIFX_TRANSPORT_DATA_TOO_SHORT Ox800E000BL Received transaction data too short Table 53 CIFX API Transport Header State Error Codes DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOCO910030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Error Codes 104 113 10 7 ODM Error Codes DBM V4 ODM Error Codes DBM V4 Error Code Definition Description CDBM E MD5 INVALID Checksum invalid IN OLD HEADER FORMAT Header format CDBM_E NO VALID TRANSACTION OXC004C816 No valid transaction handle given CDBM_E STD STRUCT ERROR 0XC004C817 An error occurred during validation of data CDBM_ E UNSUPPORTED _ OXC004C818 Unsupported DataType DATA_TYPE_FORMAT CDBM _W_CLASS DELETED FORMAT 0X8004C819 Using an Object which is marked as Warning deleted CDBM_W_CLIENT DISCONNECTED OX8004C81A A Client has already an outstanding connection to a Table The connection is now destroyed CDBM_E STRUCTURE_DEFINITION_ INVALID 0XC004C81B A structure definition of an Element in a Table is invalid CDBM_E NO DATA AVAILABLE OXC004C81C No data available for this operation CDBM_E NO VALID STRUCTURE 0XC004C81D No valid structure available for this operation CDBM E NO TOGGLE STRING FOUND 0XC004C81E No To
29. that the device is overloaded with to fast incoming requests The value O defines no Production Inhibit Time and data production can and will be done as fast as possible 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 to reload its Transmission Trigger and Watchdog Timer In Change of State connections the fourfold value of the Expected Packet Rate is used to build the Watchdog Timer If no data production of the remote station takes place within this time so the connection changes into a watchdog timeout error Incoming data productions of the remote station load the Watchdog Time again to the fourfold value of the Expected Packet Rate If a data production did not take place since starting the Transmission Trigger Timer as single values of the Expected Packet Rate so the device triggers a data production at the latest then automatically Note the Production Inhibit Time is verified against the Expected Packet Rate If the Expected Packet Rate value is unequal to zero but less than the Production Inhibit Time value then an error message is displayed by the application The Watchdog Timeout Action defines the device behavior when the watchdog timer in the device Slave expires The following actions are adjustable e Timeout The connection transitions to the timeout state and remains in this state until i
30. the Get DPM I O Information Request function e The used Slave device is operational How to proceed 1 In the Slave DTM under Settings gt Select the cifX device driver and assign the Slave device Alternative to the connection via the cifX device driver via the netX driver an USB serial or TCP connection can be used Packet Description Read Request Structure Information Area Variable Type Value Range Description tHead Structure Information A lDes UINT32 Destination Queue Handle 0x00000020 CHANNEL lulSre UINT32 X Source Queue Handle ulDest Id UINT32 0x00000000 Destination Queue Reference ulSrcid UINT32 Y Source Queue Reference ulLen UINT32 O Packet Data Length in Bytes F l Id UINT32 Any Packet Identification as Unique Number ulSta UINT32 0x00000000 Status ulCmd UINT32 Command Ox00002F0C Get I O Data Information ulExt UINT32 0x00000000 Reserved ulRout UIN T32 0x00000000 Routing Information Figure 55 Packet Description GET DPM IO INFO REQUEST Further information on the packet description for this example are comprised in the Dual Port Memory Manual in section Get DPM IO Info Request e g Revision 09 of the manual in section 5 3 1 DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOCO910030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Tools 85 113
31. user and packets received can be displayed Data packets comprise from a Packet Header and the Send Data or from a Packet Header and the Receive Data The packet header can be evaluated by the receiver of the packet and contain the sender and receiver address the data length an ID number status and error messages and the command or response code The minimum packet size amounts 40 Byte for the packet header The sending and receiving data are added Device Type Manager DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOCO0910030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Appendix EDS FDT MAC ID Master ODMV3 Slave 112 113 The Device Type Manager DTM is a software module with graphical user interface for the configuration and or for diagnosis of devices 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 Field Device Tool FDT specifies an interface in order to be able to use DTM Device Type Manager in different applications of different manufacturers MAC Media
32. whether they were network related or caused internally Table 27 Parameter General Diagnosis DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOC0910030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Diagnosis 71 113 7 3 Firmware Diagnosis In the dialog Firmware Diagnosis the actual task information of the firmware is displayed Under Firmware or Version the name of the firmware and version including the date are indicated Firmware Firmware Hame Version 2 1 0 Build Dake 12 5 2009 Task information Name of task O Re IDLE 0 0 63 The task identifie Task Status ok Ox00000000 1 Ris TIMER 0 0 1 The task identifie Task Status ok Ox00000000 2 RR SYSTEM 1 16 Middleware Syst Task Status ok Ox00000000 3 DPM COMO 1 0 ol TLR Router DPM Task Status ok Ox00000000 4 DPM Cond 1 0 51 TLR Router DPM Task Status ok Ox00000000 TLR_TIMER 0 0 27 The task identifie Task Status ok 0x00000000 6 DMS FAL 1 0 24 DeviceNet Slave Task Status ok Ox00000000 7 DMS AP 1 1 25 DeviceNet Slave Task Status ok Ox00000000 a CAPI OL l z 23 CAN DL Task Da Task Status ok Ox00000000 Figure 43 Firmware Diagnosis The name of the Firmware is displayed Task Information The table Task Information is listing the task information of the single firmware tasks Column Meaning Name of task Name of the task T
33. while a transaction TRANSACTION_IS_OPEN is open Please close this one first and call the Method again CDBM_E UNABLE TO_CALL_ 0XC004C86C The Method is disabled on a LinkedList READ ON_ LINKED _ LIST type Please use the IRecordCollection on this type CDBM_E ELEMENT HAS NO_ 0XC004C86D An Element from a Table has no SUBSTRUCTURE substructure CDBM_STRUCT_ERROR_FROM_ 0XC004C86E Error from calling VariantChangeType VAR_CHANGE_TYPE CDBM_E FOREIGNKEY_DEF OXC004C86F The definition of a FOREIGNKEY must contain the name of the related Table in the description and this Table must exist at this time CDBM_E FOREIGNKEY_ REF_TAB 0XC004C870 The description of a FOREIGNKEY must refer to a Table of type eDbmTableT ypeLinkedList CDBM_E KEY 0XC004C871 To create a Record Collection with a KEY it s necessary to have the data type KEY at the first position in all Records of the searched Table CDBM_E KEY _ TABLE TYPE 0XC004C872 This Method needs a Table of type eDbmTableT ypeLinkedList CDBM_DATATYPE_NOT_ IMPLEMENTED 0XC004C873 This data type is currently not implemented one should be inserted wasn t found Table 54 ODM Error Codes DBM V4 DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOCO910030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Appendix 108 113 11 Appendix 11 1 User Rights User rights are set within the FDT container Depending on the level the
34. you select the device and assign the device to the driver For further information refer to section Device Assignment on page 37 Firmware Download The dialog on the pane Firmware Download is used to load a new firmware into the device A detailed description can be found in section Firmware Download on page 43 Configuration General On the page General Settings the MAC ID can be read and the parameters UCMM Fragmentation Timeout or Verify Device ID can be preset Further information to this you find in section General Settings on page 57 Connection On the page Connection Configuration a connection type can be selected and configured Further information to this you find in section Connection Configuration on page 53 Parameters In the Parameter dialog the parameter data of the device can be edited A detailed description you find in section Parameter on page 67 Device Settings At the Device Settings pane device related settings can be made For further information refer to section Device Settings on page 62 Device Description Device The Device Info pane contains the manufacturer information about the device Further information to this you find in section Device on page 64 EDS By use of the EDS Viewer an EDS file can be searched through Further information to this you find in section EDS on page 65 Diagnosis Diagnosis At the Diagnosis panes information can be read for troubleshooting For further Extend
35. 01 to 0x8004C0A4 cifX Device Driver Generic Error Ox800A0001 bis Ox800A0017 Table 41 Overview Error Codes and Ranges The fieldbus specific error codes are described in the manuals of the corresponding protocol tasks DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOCO910030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Error Codes 92 113 10 3 General Hardware Error Codes 10 3 1 RCX General Task Errors Error Code Definition Value Description RCX E TASK UNKNOWN 0xC02B0003 Unknown Task RCX_E FILE XFR_TYPE_INVALID 0xC02B0007 Invalid Transfer Type Table 42 RCX General Task Errors DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOCO910030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Error Codes 93 113 10 3 2 RCX Common Status amp Errors Codes Error Code Definition Value Description Table 43 RCX Common Status amp Errors Codes DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOCO910030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Error Codes 94 113 10 33 RCX Status amp Error Codes Error Code Definition Value Description Table 44 RCX Status amp Error Codes 10 3 3 1 RCX Status amp Error Codes Slave State RCX_SLAVE_STATE_UNDEFINED 0x00000000 UNDEFINED RCX_SLAVE STATE FA
36. 1 Open Packet Monitor gt Tools gt Packet Monitor 2 Enter data for Packet header Send gt Packet header gt Under Dest enter or select the receiver gt Under Cmd enter the read command identification Sample Data A Receiver 0x20 Destination Que Handle Read Command 00002F0C GET DPM IO INFO REQUEST Identification Request Send Packet header Dest Src 00000000 State 00000000 Dest ID 00000000 Cmd oooozFoc Src ID oooo0000 Ext 00000000 Len 00000000 Rout 00000000 ID 00000002 Auto Increment IC Figure 56 Example Reading data via Get DPM IO Info Send gt Packet header Send gt Send Data Send data Counter 1 0030 v Put cyclic Put packet Figure 57 Example Read data via Get DPM IO Info Send gt Send Data Note Entering send data is not required for the Get DPM I O Information packet DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOC0910030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Tools 86 113 3 Sending Receiving Packets gt To send packet once select Put packet The entered values are sent from the packet monitor to the connected Slave device and received packets are displayed Packet Description Read Confirmation Structure Information Area Variable Type Value Range Description ulDes UINT32 From Request Source Queue Handle ulDestId
37. 2013 Introduction 14 113 1 4 1 General Device Information lO Device Name of the device Vendor name of the device Device ID Identification number of the device Vendor ID Identification number of the vendor Table 2 General Device Information 1 4 2 Navigation Area The Navigation Area contains folders and subfolders to open the dialog panes of the DTM Navigation Area A Settings Driver Device Assignment Firmware Download fl Configuration Figure 2 Navigation Area gt Select the required folder and subfolder gt The corresponding Dialog pane is displayed Hide display Navigation O Hiding the navigation area above right side m Show navigation area Opening the navigation area below left side DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOC0910030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Introduction 15 113 1 4 3 Dialog Panes At the dialog pane the Settings Configuration Diagnosis Extended Diagnosis or the Tools panes are opened via the corresponding folder in the navigation area Driver To establish a connection from the DeviceNet Slave DTM to the DeviceNet Slave device on the pane Driver you can verify ifthe default driver is checked and respectively check another driver or multiple drivers For further information refer to section Driver on page 27 Device Assignment On the pane Device Assignment
38. 2E USER Parameter SendSize too large DRV_E USR_RECVSIZE TOO LONG USER Parameter ReceiveSize too large DRV_E USR_SENDBUF_PTR_NULL 0x8004C030 USER Pointer to send buffer is a null pointer DRV_E USR_RECVBUF_PTR_NULL 0x8004C031 USER Pointer to receive buffer is a null pointer DRV E DMA INSUFF MEM DMA Memory allocation error DRV E DMA TIMEOUT CH4 DMA Read I O timeout DRV E DMA TIMEOUT CH5 DMA Write I O timeout DRV_E_DMA TIMEOUT CH6 DMA PCI transfer timeout DRV _E DMA TIMEOUT CH7 DMA Download timeout DRV E DMA DB DOWN FAIL DMA Database download failed DRV E DMA FW DOWN FAIL DMA Firmware download failed DRV_E CLEAR_DB_FAIL DMA Clear database on the device failed DRV_E DEV NO VIRTUAL MEM DMA USER Virtual memory not available DRV E DEV UNMAP VIRTUAL MEM DMA USER Unmap virtual memory failed DRV_E GENERAL ERROR DRIVER General error DRV_E_ DMA ERROR DRIVER General DMA error DRV_E_WDG IO ERROR DRIVER I O WatchDog failed DRV _E WDG DEV ERROR DRIVER Device Watchdog failed DRV E USR DRIVER UNKNOWN USER Driver unknown DRV E USR DEVICE NAME INVALID USER Device name invalid DRV E USR DEVICE NAME UKNOWN USER Device name unknown DRV E USR DEVICE FUNC_NOTIMPL USER Device function not implemented DRV E USR FILE OPEN FAILED USER File could not be opened DRV E USR FILE SIZE ZERO USER File size zero DRV _E USR FILE NO MEMORY USER Not enough memory to load file DRV E USR FILE READ FAILED USER File read failed DRV _E USR INVALID FILETYPE USER File type in
39. 30I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Tools Receive gt Receive data 88 113 Y Under Receive data the data of the receive packet are displayed Receive data OO 01 04 03 04 05 06 07 Og 03 0000 0004 3 oma ED GU Leo OTE wo ey ron um Counter 1 14 Figure 60 Example Reading data via Get DPM IO Info Receive gt Receive data Range of Value Sample Data Num lO Block Number n of 0 10 Block Definitions Below IO Block n I O Block Definition E Structure s RCX_DPM_IO_ BLOCK_INFO Sub block Index index of sub block Type type of sub block Daz O Flags flags of the sub O 65535 block Reserved 0 65535 Offset offset of I O datain 0 2 bytes Length length of I O data 0 2 in bytes UINT32 4 Bytes The description shows that the Slave device is configured with 02 00 00 00 Block 0 IN DPM 00 00 00 00 02 00 00 00 11 00 00 00 00 00 00 00 08 00 00 00 Intel format e 9 LSB first 8 Byte input data and 8 Byte output data DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOCO910030I08EN Revision 8 English 2013 09 Released Public Block 1 OUT DPM 00 00 00 00 02 00 00 00 12 00 00 00 00 00 00 00 08 00 00 00 Hilscher 2009 2013 Tools 89 113 9 3 10 Monitor The IO Monitor serves for test and diagnos
40. Access Control 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 Master devices initiate the data exchange at the bus The Online Data Manager Version 3 ODMV3 is an application interface The ODMV3 works as a server which can be run as an out proc server or system service Its task is to provide different applications e g SYCON net access to multiple devices and even share one device amongst several applications Slave devices are configured by the Master and perform then the communication DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOCO910030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Appendix 11 6 Contacts Headquarters Germany Hilscher Gesellschaft f r Systemautomation mbH Rheinstrasse 15 65795 Hattersheim Phone 49 0 6190 9907 0 Fax 49 0 6190 9907 50 E Mail info hilscher com Support Phone 49 0 6190 9907 99 E Mail de support hilscher com Subsidiaries China Hilscher Systemautomation Shanghai Co Ltd 200010 Shanghai Phone 86 0 21 6355 5161 E Mail info hilscher cn Support Phone 86 0 21 6355 5161 E Mail cn support hilscher com France Hilscher France S a r l 69500 Bron Phone 33 0 4 72 37 98 40 E Mail info hilscher fr Support Phone 33 0
41. DBM NO MEMORY 0x8004C084 USER Not enough memory to upload database DRV_E DBM READ FAILED 0x8004C085 USER Database read failed DRV_E DBM NO _FLASH_SEGMENT 0x8004C086 USER Database segment unknown DEV_E CF _ INVALID _DESCRIPT_VERSION 0x8004C096 CONFIG Version of the descript table invalid DEV E CF INVALID _INPUT_OFFSET 0x8004C097 CONFIG Input offset is invalid DEV E CF_NO_INPUT_SIZE 0x8004C098 CONFIG Input size is O DEV_ E CF_MISMATCH_INPUT_SIZE 0x8004C099 CONFIG Input size does not match configuration DEV E CF_INVALID_OUTPUT_OFFSET 0x8004C09A CONFIG Invalid output offset DEV E CF NO OUTPUT SIZE 0x8004C09B CONFIG Output size is 0 DEV_E_CF_MISMATCH_OUTPUT_SIZE 0x8004C09C CONFIG Output size does not match configuration DEV E CF_STN_NOT_CONFIGURED 0x8004C09D CONFIG Station not configured DEV E CF_CANNOT_GET STN CONFIG 0x8004C09E CONFIG Cannot get the Station configuration DEV E CF MODULE DEF MISSING NO Sl 0x8004C0A4 CONFIG Module definition is missing no Slot Idx Table 48 cifX Driver Specific ODM Error Codes DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOC0910030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Error Codes 100 113 10 5 Error Codes cifX Device Driver and netX Driver 10 5 1 Generic Error Codes CIFX_INVALID_POINTER Ox800A0001L Invalid pointer NULL passed to driver CIFX_INVALID BOARD Ox800A0002L No board with the given nameindex availab
42. ILED 0x00000002 FAILED at least one slave Table 45 RCX Status amp Error Codes Slave State DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOCO910030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Error Codes 95 113 10 4 ODM Error Codes 10 4 1 General ODM Error Codes CODM3_E_COMCATEGORIE_MANAGER _ 0x8004C712 Component Category Manager could not FAILED be instantiated CODM3 E COMCATEGORIE_ENUMERATION _ 0x8004C713 Driver could not be enumerated by the FAILED Category Manager CODM3 E CREATE DEVICE THREAD STOP_ 0x8004C751 Error creating device thread stop event EVENT CODM3_ E CLIENT NOT REGISTERED 0x8004C752 Client is not registered at the ODM CODM3_ E NO MORE CLIENTS 0x8004C753 Maximum number of clients reached CODM3_ E MAX CLIENT CONNECTIONS _ 0x8004C754 Maximum number of client connections REACHED reached CODM3 E ENTRY_NOT_FOUND 0x8004C755 Driver device not found CODM3 E DRIVER_NOT_FOUND 0x8004C757 The requested driver is unknown to the ODM CODM3 E DEVICE ALREADY LOCKED 0x8004C758 Device is locked by another process CODM3 E DEVICE UNLOCKED FAILED 0x8004C759 Device could not be unlocked lock was set by another process CODM3 E DEVICE LOCK NECCESSARY 0x8004C75A Operation requires a device lock to be set CODM3_E DEVICE SUBSCRIPTIONLIMIT 0x8004C75B Maximum number of servers registered for this device reached CODM3 E DEVICE NOTSUBSCRIBED 0x8004C75C P
43. MER COUMO ia ded tatamacinieiacan idscs avian 77 8 5 BAND ehe 78 8 9 1 AF Commands COUME ana A 78 8 5 2 CAN Driver Stausee A 79 9 BF A A 80 DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOC0910030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Table of Contents 4 113 9 1 OVELMIEWTOO S ss ze a zn a as a o es eee A 80 9 2 ao ee ee ae 81 9 2 1 SENANG Packet el 82 9 2 2 FRECCIVING Packe ista oia 83 9 2 3 Example Get DPM I O Information cccooccccocncocnccccnccncnconcnnnonncoonnnnonononcnnnnos 84 9 3 OE rd idence 89 10 TERRORS CODE Sessions 90 10 1 Enor Code De nto Mision re renos tae en dende bet co eine de da der ea 90 10 2 OVEIVIEW EIOr COC CS gsc sho o de ao 91 10 3 General Hardware Error Codes cccccccccccccccececcececcececececeueceneaeeaeueueueueenenenenenenes 92 10 3 1 RCX General Task Errors cccceccececececececcececuceeaecececeeaeeececueaeaeaeseceeeeaeaeaeeeeass 92 10 3 2 RCX Common Status Errors Codes 2 0 0 0 cccccececaccecececeecececececeeaececuceeeeaeeeeeeass 93 10 3 3 RCA Stalus SETOL COQES Arne erfor 94 10 4 OD IVINE TIO OC O Sut ea ee 95 10 4 1 General ODM Error Codes x ws ee ana 95 10 4 2 General ODM Driver Error Codes u 22 aan a 96 10 4 3 cifX Driver Specific ODM Error Codes 2222002220002200nennnnnennennnnnennnnn nennen 97 10 5 Error Codes cifX Device Driver and netX DIivVel
44. MSIZE_ MISMATCH 0x8004C01A DEVICE DPM size differs from configuration DRV_E DEV STATE_MODE_ UNKNOWN 0x8004C01B DEVICE State mode unknown DRV_E DEV HW_PORT_IS USED 0x8004C01C DEVICE Output port already in use DRV_E USR_OPEN_ERROR 0x8004C01E USER Driver not opened device driver not loaded DRV_E USR_INIT_DRV_ERROR 0x8004C01F USER Can t connect to device DRV_E USR_NOT_INITIALIZED 0x8004C020 USER Board not initialized DevInitBoard not called DRV_E_USR_COMM ERR USER IOCTRL function failed DRV_E_USR_DEV_NUMBER_INVALID USER Parameter DeviceNumber invalid DRV_E_USR_INFO AREA INVALID USER Parameter InfoArea unknown DRV E USR_NUMBER_INVALID USER Parameter Number invalid DRV E USR MODE INVALID USER Parameter Mode invalid DRV E USR MSG BUF NULL PTR USER NULL pointer assignment DRV E USR _ MSG BUF TOO SHORT USER Message buffer too small 3 O O O DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOCO910030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Error Codes 98 113 cifX Driver Specific ODM Error Codes Error Code Definition Description DRV E USR SIZE INVALID USER Parameter Size invalid DRV E USR SIZE ZERO USER Parameter Size with zero length DRV_E_USR_SIZE_TOO_LONG 0x8004C02B USER Parameter Size too long DRV E USR DEV PTR NULL USER Device address null pointer DRV E USR BUF PTR NULL USER Pointer to buffer is a null pointer DRV_E_USR_SENDSIZE_TOO_LONG 0x8004C0
45. Master and insert the device via drag and drop to the root line in the network view in the Device Catalog click to the Slave and insert the device via drag and drop to the Master bus line in the network view Insert Master or Slave into configuration Open the Slave DTM configu ration dialog Open the Slave DTM configuration dialog Double click to the device icon of the Slave The Slave DTM configuration dialog is displayed Verify or adapt Driver Settings In the Slave DTM configuration dialog select Settings gt Driver Note For PC cards cifX the cifX Device Driver is preset as a default driver For all the other Hilscher devices the netX Driver is preset as a default driver e Use the cifX Device Driver if the DeviceNet Slave DTM is installed on the same PC as the DeviceNet Slave device Use the netX Driver to establish a USB Serial RS232 or TCP IP connection from the DeviceNet Slave DTM to the DeviceNet Slave device e The 3SGateway Driver for netX V3 x is used only in relationship with CODESYS To search for devices you can check one or multiple drivers simultaneously Verify that the default driver is checked If necessary check another driver or multiple drivers Configure If you use the netX Driver you respectively must Driver configure it For netX Driver and communication via TCP IP set the IP address of the device Select Settings gt Driver gt netX Driver gt TC
46. NO_PACKET 0x800C0019L No packet available Table 51 Generic Device Error Codes DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOCO910030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Error Codes 103 113 10 6 Error Codes netX Driver 10 6 1 CIFX API Transport Error Codes CIFX_TRANSPORT_SEND_TIMEOUT Ox800D0001L Time out while sending data CIFX_TRANSPORT_RECV_TIMEOUT Ox800D0002L Time out waiting for incoming data CIFX_TRANSPORT_ CONNECT Ox800D0003L Unable to communicate to the deviceno answer CIFX_TRANSPORT_ ABORTED Ox800D0004L Transfer has been aborted due to keep alive timeout or interface detachment CIFX_CONNECTOR_FUNCTIONS READ ERR 0x800D0010L Error reading the connector functions OR from the DLL CIFX CONNECTOR_IDENTIFIER_TOO LONG 0x800D0011L Connector delivers an identifier longer than 6 characters CIFX_CONNECTOR_IDENTIFIER_EMPTY 0x800D0012L Connector delivers an empty dentifier CIFX_CONNECTOR_DUPLICATE_IDENTIFIER Ox800D0013L Connector identifier already used Table 52 CIFX API Transport Error Codes 10 6 2 CIFX API Transport Header State Error Codes CIFX_TRANSPORT_ERROR_UNKNOWN Ox800E0001L Unknown error code in transport header CIFX_TRANSPORT CHECKSUM ERROR Ox800E0002L CRC16 checksum failed CIFX_TRANSPORT_LENGTH_INCOMPLETE Ox800E0003L Transaction with inclomplete length detected CIFX_TRANSPORT_DATA_TYPE_UNKOWN Ox800E0004L Device does not
47. P Connection Via L add an IP range Under IP Address enter the IP Address of the device or an IP range Click Save Adjust the driver parameters netX Driver USB RS232 only if they differ from the default settings Note e The cifX Device Driver requires no configuration e The configuration of the 3SGateway Driver for netX V3 x is carried out via the CODESYS surface See Operating Instruction Manual netDevice and netProject See Operating Instruction Manual of the Frame Application See Operating Instruction Manual netDevice and netProject Settings for Driver and Device Assignment and Driver Configuring netX Driver DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOCO0O910030l108EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Getting started Assign Slave device with or without firmware Select and download firmware Assign Slave device once more with firmware and system chanal For repeated download this step is omitted Configure Slave device Configure Master device Save project Connect Slave device Download Configuration Diagnosis 22 113 Assign the device to this driver In the Slave DTM configuration dialog select Settings gt Device Assignment select a Slave device with or without firmware therefore check the appropriate checkbox select Apply
48. P state stopped by the application program or it changed to the Stop state because of a bus error The DeviceNet Slave is offline as long as it does not wt yellow In OFFLINE state have a valid configuration wer gray Not in OFFLINE state Configuration State Configuration Shows whether the DeviceNet device configuration gt yellow Configuration LOCKED locked is locked to avoid the configuration data are typed over iil Configuration not gray LocKED New Configura Shows whether a new DeviceNet device we yellow New Configuration tion pending configuration is available pending da No new Configuration Reset required Shows whether a firmware reset is required as a w yellow RESET required new DeviceNet device configuration has been loaded into the device u gray No RESET required Shows whether the bus communication was started amp green or stopped e whether the device is active on the bus or no bus communication to the device is heal gray Bus OFF possible and no response telegrams are sent Table 26 Indication General Diagnosis Parameter Communication Error Shows the name of the communication error If the cause of error is resolved the value will be set to zero again Watchdog time Shows the watchdog time in ms Error Count This field holds the total number of errors detected since power up respectively after reset The protocol stack counts all sorts of errors in this field no matter
49. RAN Slave CIFX cx Build x File name Name of the Firmware File nxf or nxm Files of type Firmware Files nod nm Cancel Recent folders Path of the last used Folder Help Firmware Firmware Name Version Device Class Figure 17 Window Select Firmware File Example CIFX Parameter Range of Value Default Value Column Name File name of the firmware file nxf nxm To sort the entries of the window Select Firmware File by name click to the column head Name Column Name of the firmware consisting of the protocol name and protocol class Firmware e g CIFX COMX COMX 51 NETJACK 10 NETJACK 50 Column Device class of the associated hardware Hardware DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOCO0O910030l108EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Settings 45 113 NETJACK 51 NETJACK 100 NETTAP 50 Gateway NETTAP 100 Gateway NETBRICK 100 Gateway Column Firmware version x X build x Version To view the tooltip information move with the mouse pointer over the selected firmware line Type Hilscher firmware file for netX based targets NAF Size 563 KB Date of change 2013 03 26 11 10 Files of Type All Files if before in the Device Assignment pane under Device All Files selection all was selected Firmware Files nxm Firmware Files nxm or Firmware Files nxf if b
50. Range error while validating a value CDBM_DATATYPE_ UNSUPPORTED_IN RCS OXC004C83E The data type is unsupported in the RCS file format CDBM_ _COUNT OF_TABLES _ 0X4004C83F The count of Tables exceeds the RCS EXCEEDS RCS RANGE range of Tables This can cause problems if the file is downloaded to RCS Systems CDBM_ _ COUNT OF_TABLES _ 0X4004C840 The count of Tables exceeds the EXCEEDS OLDDBM RANGE DBM32 DLL range of Tables This can cause problems if the file is used with older Tools using the DBM32 DLL CDBM_UNSUPPORTED DATATYPE _ 0XC004C841 The Data type is not compatible with the IN_RCS_MODE old database format CDBM_WRITE_UNSTRUCTURED 1 OXC004C842 The data of an unstructured record can only be written with the Write Method not with WriteElement CDBM READ UNSTRUCTURED 1 0XC004C843 The data of an unstructured record can only be read with the Read Method not with ReadElement CDBM_WRITE_DATA_LENGTH_ INVALID 0XC004C844 The given data length doesn t correspond with the expected data length CDBM_UNKNOWN_VIEW_MODE OXC004C845 The View Mode is unknown CDBM_E DIAG TABLE 0XC004C846 It doesn t make much sense to add or delete records from a diagnostic table because those changes are never saved CDBM_E ADR_STRING ERROR OXC004C847 The given Address string doesn t fit the required format of this type where all address bytes must be in the range between 0 and FF DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Sla
51. SB RS232 connection are made via the netX Driver USB RS232 Connection configuration dialog gt Open the USB RS232 Connection dialog via navigation area Settings gt Driver gt netX Driver 2 The USB RS232 Connection dialog is displayed LISBIRS232 Connection TCP Connection iw Enable USBIRS232 Connector Restart of ODM required Select Port com Pork Configuration Disable Port Baud Rate 115 2 kEit s Byte Size E Byte Stop Bits f Stopbit r Parity No Parity r Send Timeout 1000 ms Keep Alive Timeout 2000 ES ms Reset Timeout 10000 ms Restore Save Save All Figure 9 netX Driver gt USB RS232 Connection Parameter Range of Value Default Value Enable USB RS232 checked The netX Driver can communicate via the checked Connector Restart of USB RS232 interface unchecked ODM required unchecked The netX Driver can not communicate via the Default USB RS232 interface unchecked If the check mark for Enable USB RS232 Connector is set or removed then the ODM server must be restarted to make the new setting valid 1 Restart the ODM server via the ODMV3 Tray Application In the foot line click on EZ using the right mouse key In the context menu select Service gt Start Select Port Depending on the COM ports interfaces available on the COM 1 to COM N PC they will be listed under Select Port Port Configuration Disable Port checked No connection chec
52. State Communication Shows whether the DeviceNet device executes the F green In COMMUNICATION network communication state Not in gray COMMUNICATION state W green Configuration OK we gray Configuration not OK yellow Device READY Shows whether the DeviceNet device has been configured correctly Shows whether the DeviceNet device has been started correctly The DeviceNet device waits for a configuration r gray Device not READY Shows whether the DeviceNet device records a w red ERROR device status error For further information about the error characteristics and the number of counted d gray No ERROR errors refer to the extended diagnosis gray Network State Operate Shows whether the DeviceNet device is in data all green In OPERATION state exchange In a cyclic data exchange the input data or the output data of the DeviceNet Slave are hal gray transmitted to the DeviceNet Master in OPERATION state Shows whether the DeviceNet device is in idle state yellow In IDLE state hal gray Not in IDLE state DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOC0910030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Diagnosis 70 113 LED Meaning Color State Shows whether the DeviceNet device is in Stop w red In STOP state state There is no cyclic data exchange at the DeviceNet network The DeviceNet device was Not in STO
53. TM via the preselected drivers Note During a subsequent firmware download in the selection window Select Firmware File only firmware files from the selected folder are displayed under Files of Type Firmware Files nxm or Firmware Files nxf is displayed and the check box Validate the selected firmware file is checked DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOC0910030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Settings 40 113 3 4 2 Selecting the Device with or without firmware Note A connection with the DeviceNet Slave DIM can only be established with one DeviceNet Slave device To select the physical DeviceNet Slave device with or without firmware 1 Check the appropriate device Scan progress 5 5 Devices Current device Device selection suitable only hal Device Hardware Port 0 1 23 Slot number Channel Protocol Access path IPROFIEUS 1 20148 CIFX Device Driver PROFIBUS Master ciga SYS Access path 365BECSB 0E92 4C0E 6449 64F624E7 44F4F cies S S Figure 13 Device Assignment Selecting the Device The name of the device class is displayed Example for a device without firmware one Device is selected Under Access path below in the dialog pane the access path to the device e g the driver identification or depending on the used driver additional access data of the device are
54. USE RS232 Connection TCP Connection mw Enable TCP Connector Restart of ODM required Select IP Range IP_RANGEO db Scan Timeout 100 ms IF Range Configuration Disable IP Range IP Address Use IP Range TCP Part Address Count 192 168 1 1 50111 1 Send Timeout 1000 ms keep Alive Timeout 2000 gt ms Reset Timeout 20000 gt ms Restore Save Save Al Figure 10 netX Driver gt TCP Connection Parameter Range of Value Default Value Enable TCP Connector checked The netX Driver can communicate via the TCP IP checked Restart of ODM interface unchecked required unchecked The netX Driver can not communicate via the ei a TCP IP interface uncnecke If the check mark for Enable TCP Connector is set or removed then the ODM server must be restarted to make the new setting valid 1 Restart the ODM server via the ODMV3 Tray Application In the foot line click on E using the right mouse key In the context menu select Service gt Start Select IP Range Via Select IP Range already created IP ranges can be selected an IP range can be deleted DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOCO910030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Settings 36 113 Parameter Range of Value Default Value Scan Timeout ms With Scan Timeout can be set how long to wait for a 10 10000 ms res
55. Under Device Selection select suitable only 3 Select Scan to start the scanning process gt In the table all devices are displayed which can be connected to the DeviceNet Slave DTM via the preselected driver Note For devices which have been found via the cifX Device Driver in the column Access path the indication cifX OtoN SYS is displayed This is correct as long as a device did not get a firmware After the firmware download has been completed in the column Access path the indication AcifX OtoN Ch Oto3 is displayed DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOC0910030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Settings 38 113 Parameter Range of Value Default Value Device selection Selecting suitable only or all devices suitable only all Device class of the DeviceNet Slave devices Hardware Port Shows which hardware is assigned to which communication interface 0 1 2 3 Slot number Switch Slot Number Card ID The indication n a means that no Slot Nummer Card ID exists This will occur ifthe PC card cifX is not equipped with a Rotary Switch Slot Number Card ID or for PC cards cifX equipped with a Rotary Switch Slot Number Card ID if the rotary switch is set to the value O zero Serial number of the device Name of the driver Channel Protocol Access path last column on the right Access path at the lowe
56. able 28 Description Table Task Information DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOC0910030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Extended Diagnosis 72 113 8 Extended Diagnosis 8 1 Overview Extended Diagnosis The Extended Diagnosis of the DeviceNet Slave DTM helps to find communication and configuration errors Therefore it contains a list of diagnosis structures as online counter states and parameters Dialog Panes Extended Diagnosis The table below gives an overview for the Extended Diagnosis dialog panes descriptions Navigation Area 2 Diagnosis Extended Diagnosis E Rx SYSTEM we Task Information IniBatch Status IniBatch Status IniBatch Status IniBatch Status IniBatch Status IniBatch Status Al DPM_COMO_SMER Task Information E DPM_COMO_RMBX Task Information J DNS_FAL Task Information DNS Commmon Status AF Command Counters CAN Command Counters Timer Counter E DNS_AP Task Information Task Information Application Commands CAN Driver Status MARSHALLER Task Information PACKET_ROLTER Task Information I Tools Navigation Area Extended Diagnosis DeviceNet Slave DTM Folder Name in the Dialog Pane Page Navigation Area iach Ss m Dem COMO SMBX Taskinformation 78 AP Commands Counter 78 oamomersano R PACKET_ROUTER Task Information 73
57. ad stops the bus communication erases the configuration database and overwrites the existing Firmware in the device To complete the update and to make the device operable again please re download the configuration when this operation has Finished Download Figure 19 Firmware Download Download The request Do you really want to download the firmware is displayed Question 2 Do you really want to download the new Firmware Figure 20 Firmware Download Question DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOC0910030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Settings 47 113 gt During the download a progress bar is displayed in the status line a clock green hook symbol is displayed and Download is grayed out neilevice Device Device Name Descripiion lt Sigtos Address Nelwork JO Download active device performs initialisation 39 complete Figure 21 Clock Symbol and Hook Symbol green E E gD Firmware Download ale Figure 22 Firmware Download Progress Bar DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOC0910030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Configuration 48 113 4 Configuration 4 1 Overview Configuration Configuration Dialog Panes The table below gives an overview for the Configuration dialog panes
58. ad Parameters Select Firmware File Dialog Panes Configuration General Settings Attributes of the device identification General Settings Enable Address Switch Possible connection types Change Parameter Data Range of Value Value for the Watchdog time Descriptions of the Dialog Panes Device Description General Device Information Device Description EDS Viewer Descriptions of the Diagnosis Panes Indication General Diagnosis Parameter General Diagnosis DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOCO0O910030l108EN Revision 8 English 2013 09 Released Public 110 113 62 63 63 69 71 13 74 75 76 76 77 78 79 81 82 83 84 85 85 86 8 88 89 5 14 15 16 16 17 20 23 24 27 33 36 38 43 45 48 91 92 53 61 63 64 64 65 68 70 70 Hilscher 2009 2013 Appendix 111 113 Table 28 Description Table Task Information 71 Table 29 Descriptions of the Dialog Panes Extended Diagnosis 12 Table 30 Extended Diagnosis gt Folder Name gt Task Information 13 Table 31 Extended Diagnosis gt Folder Name gt IniBatch Status 14 Table 32 Extended Diagnosis gt DNS_FAL gt DNS Common Status 75 Table 33 Extended Diagnosis gt DNS_FAL gt AP Commands Counter 76 Table 34 Extended Diagnosis gt DNS_FAL gt CAN Command Counter 76 Table 35 Extended Diagnosis gt DNS_FAL gt Timer Counter 17 Table 36 Extended Diagnosis gt CAN_DL gt AP Command
59. age 61 and to section Device Settings on page 62 of this document DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOCO910030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Configuration 51 113 4 3 General Settings The Dialog General Settings contains the following configuration possibilities MAC ID 0 Baud rate 1125 kEits s a LICMM lGraup3 Fragmentation timeout 1700 ms Figure 23 General Settings Attributes of the device identification Slave DTM at the Root Line Stand Alone Slave MAC ID ial Baud rate 125 kBits s la net LICHIM lGraup3 Fragmentation timeout 1700 ms Figure 24 General Settings Attributes of the device identification Slave DTM at the Master busline MAC ID The MAC ID is assigned by the Master and can not be edited here Changing the MAC ID has to be made with the DeviceNet Master DTM With each device inserted into the configuration the MAC ID is increased automatically by one Slave DTM at the Root Line Stand Alone Slave The MAC ID is set in the Slave DTM Slave DTM at the Master busline The MAC ID is set in the Master DTM Baudrate Baud rate of DeviceNet connection 500 kBaud 250 kBaud 125 kBaud Default 500 kBaud UCMM If the field UCMM is selected the device is used as UCMM compatible device The option UCMM is used for devices which need the UCMM message format Group 1 2 and
60. anual Table 34 Extended Diagnosis gt DNS_FAL gt CAN Command Counter DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOC0910030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Extended Diagnosis 77 113 8 4 4 Timer Counter Task states Cyclic Timer 3006094 Figure 49 Extended Diagnosis gt DNS_FAL gt Timer Counter Name Description S Service Diagnosis counter of the FAL layer Indicates the services processed The services of the single packets are described in the API manual Table 35 Extended Diagnosis gt DNS_FAL gt Timer Counter DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOC0910030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Extended Diagnosis 8 5 CAN_DL 8 9 1 Task states Mame Data Request Positive Confirmations Negative Confirmations Can DL Indications Can DL Responses Can DL Start Request Positive Start Confirmations Negative Start Confirmations Stop Requests Positive Stop Confirmations Negative Stop Confirmations Application Register Requests Positive Application Register Conti Negative Application Register Con Set Farameter Requests Positive Set Parameter Contirmati Negative Set Parameter Confirmat Set Filter Requests Positive Set Filter Confirmations Negative Set Filter Confirmations Enable Receive I
61. cturer If User Defined is selected in Parameter Group the entries in the columns Param Name and Value are editable Otherwise the entries are fixed and can not be changed A description on how table lines can be selected inserted or deleted can be found in section Table Lines on pag 16 To reset the defalut values from the EDS file click ut ss 4 6 Device Settings At the Device Settings pane device related settings can be made These settings are assigned after a download of the configuration Information about the download you find in section Download y Configuration on page 67 Start of bus communication Automatically by device Controlled by application Application monitoring Watchdog time 1000 ms Figure 39 Configuration gt Device Settings Note The setting options at the dialog pane Device Settings for client specific variants of the configuration software can differ from the setting options displayed here DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOCO910030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Configuration 63 113 4 6 1 Start of Bus Communication Start of bus communicatior f Automatically by device C Controlled by application Figure 40 Device Settings gt Start of Bus Communication lf Automatically by device is selected the DeviceNet Slave device starts with the data exchange
62. d Requests Positive Enable Receive Id Contir Negative Enable Receive Id Confir Event Indications Event Responses Event Acknowledge Request Positive Event Confirmations Negative Event Confirmations Transmit Abort Request Positive Transmit Abort Confirmati Negative Transmit Abort Confirma Init Request Positive Init Confirmations Negative Init Confirmations Hi Priority Data Request Positive Hi Priority Data Confirmati Negative Hi Priority Data Confirma AP Commands Counter m Ou iT Daaa eee Gt Aaaa 0 PoO0o0o0or rk kb orte rm aAA A 78 113 Figure 50 Extended Diagnosis gt CAN_DL gt AP Commands Counter Name Description S O Service Diagnosis counter of the CAN layer Indicates the services processed The services of the single packets are described in the API manual Table 36 Extended Diagnosis gt CAN_DL gt AP Commands Counter DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOC0910030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Extended Diagnosis 79 113 8 5 2 CAN Driver Status Task states Can Status Ox00000006 Bus OFF False Error Warning true Error Passive true Reserved False Reserved False Reserved False Reserved False Reserved False Reserved False Reserved False Reserved False Reserved False Reserved False Reserved False Reserved False Reserved False 24 Volk Metwork Erro
63. displayed 2 Select Apply to apply the selection Note Before an online connection from the DeviceNet Slave DTM to the DeviceNet Slave device can be established a firmware must be loaded to the device and the device must be selected once more For further information refer to section to section Firmware Download on page 43 or to section Selecting the Device once more with Firmware on page 41 DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOC0910030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Settings 41 113 3 4 3 Selecting the Device once more with Firmware Note For repeated download this step is omitted To select the DeviceNet Slave device with firmware and defined system channel once more proceed as described hereafter all 1 Under Device Selection select all 2 Select Scan gt In the table all devices are displayed which are attainable in the network and which can be connected to a DIM via the preselected drivers 3 Check the appropriate device Scan progress 5 5 Devices Current device Scan Device selection lal PEPE Ea A a Access path I i Pat int eben Bann m ae ee ee m a T A DeyiceNet n a 20027 CIFX Device Driver DeviceNet Master J cif Cho O j nta 20058 nets Driver Undefined Undefined 1192 168 Ol Ethernet Ethernet na 202508 CIFX Device Driver PROFINET 10 Device ciFxz2_ChD O
64. download the firmware via Download Select Apply Scan for and select the devices with firmware and defined system channel once more For repeated download this step is omitted Select Settings gt Device Assignment Select Scan In the table check the required devices Close the DTM configuration dialog via OK Connecting the Device 8 9 gt In netDevice put a right click on the DeviceNet Slave device icon Select the Connect command from the context menu In the network view the device description at the device icon of the Slave is displayed with a green colored background The DeviceNet Slave device now is connected to the DeviceNet Slave DTM via an online connection Further Information For descriptions about these steps refer to the sections following here after DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOCO910030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Settings 27 113 3 3 Driver The Driver dialog pane displays the drivers to be used for a DeviceNet Slave DTM to establish a device communication connection Note A default driver s set in the configuration software Driver La Driver Version CIFX Device Driver 1 101 1 9801 358BEC 5B 0E92 4C 0E B449 54F62AE7AAFA O 35Gateway Driver for netX V3 x 0 9 12 787CD3A9 4CF6 4259 3E4D 109B6A6BEA9 1 O netX Driver 1 103 2 5183 B54C8CC7 F335 4135 8405 6E 12FC88EE6 2
65. e device Configure the Slave device Double click to the device icon of the Slave The Slave DTM configuration dialog is displayed In the Slave DTM configuration dialog select Configuration gt General set UCMM and Fragmentation Timeout select Configuration gt Connection configure the device connection select Configuration gt Parameter set the parameter data of the device select Configuration gt Device Settings set the Device Settings close the Slave DTM configuration dialog via OK Save project Depending of the frame application For the configuration software select File gt Save Connect Slave Depending of the FDT Container For netDevice device For netDevice right click to the device icon of the Slave 12 right click to the device icon of the Slave 13 Download Configuration select Download Depending of the FDT Container select Connect Diagnosis Depending of the FDT Container For netDevice right click to the device icon of the Slave select Diagnosis The Slave DTM diagnosis dialog is displayed 1 Check whether the communication is OK Diagnosis gt General Diagnosis gt Device status Communication must be green 2 Communication is green Open thel lO Monitor and test the input or output data 3 Communication is not green Use Diagnosis and Extended diagnosis for troubleshooting close the Slave DTM diagnosis dialo
66. e device are automatically disabled In the lower section of this dialog the possible combinations of the connection types are displayed Valid combinations Poll Bit Strobe Change of State Cyclic Change of State Poll Bit Strobe Cyclic Poll Bit Strobe Bit Strobe Poll Change of State Cyclic Figure 28 Indication of possible combinations of connection types If an invalid combination is set the following warning appears AN Warning According to the EDS File the current combination isn t walid Figure 29 Warning invalid connection type combination 4 4 1 Connection Types The following connection types are available Poll Connection Change of State Connection Cyclic Connection Bit Strobe Connection Table 19 Possible connection types DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOC0910030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Configuration 54 113 4 4 1 1 Poll Connection If the Poll Connection type was activated the elements of this connection type are editable Otherwise this dialog is disabled iM Consumption Size Bytes Connection Path Consuming POLL COS Data Path description valve Command bits 3 1 bit D is ignored W Production Connection Path Producing COS Data Path description Figure 30 Poll Connection Consumption and Production One poll command from the Master sends a n
67. e eek 48 4 2 Configuring Slave Parameters 22200224002000200002nno nenn nnnnennnn nano nenn nnnne nenne nenn nnnnnen 49 4 2 1 Slave DTM at the Root Line Stand Alone Slave cccoooccccccconccccoccnconononnononons 49 4 2 2 Slave DTM at the Master busline occcoccccoccconcccoccnnococonnccncnccnonconrnconcncnononnns 50 4 3 General SSUINGS o toda e 51 4 3 1 Enable Address SWitCh viii ee 52 4 4 Connection CONNgUralon seen 53 4 4 1 Connection TY DCS 22 ee ed 53 4 5 Bee nao APA tere ete rer ee ee ee 61 4 6 DEVICE SEUNGSE ee ee hen 62 4 6 1 Start Of Bus COMMUNICA OM od 63 4 6 2 ADPICAtiOn MONITO NO paneer Here 63 5 DEVICE DESCRIPTION ss orstoccrn tercero caco tccciatd 64 5 1 ADOUL DEVICE DESECHP LION ee 64 5 2 DEVICE ee Re ee a ER Pe 64 9 9 ED Oea a ee ee ee ee 65 6 ONGINE FUNG HONS cdi 66 6 1 Connecting Disconnecting Device 2 002220020002000nennonnnnnnnn nase nenne nano nenne nenn nennen 66 6 2 Download C ONMGUPATIOM ours a essen 67 DINGE SS bo ssi San ee o et 68 7 1 Overview DIAGNOSIS sack 68 7 2 GenerallDiagh sis nun IR ed 69 1 3 Firmware Diagnosis iii ia a iiO ib 71 8 EX TENDED DIAGNOSIS suscitada 12 8 1 Overview Extended Diagnosis sisas rail 72 8 2 TASK OI ON ee eee seed oe aca Sera 73 8 3 NBA STAU S ine ies ias 74 8 4 DNS As oi 15 8 4 1 DNS Common Stalus una 75 8 4 2 AP Commands SOU ss en 76 8 4 3 CAN Command Counter carnai a a A A E A NESA 76 8 4 4 TI
68. eNet Slave DTM is dropped to the root line Stand Alone Slave and in addition important information for the case if the DeviceNet Slave DTM is dropped to the Master busline of a DeviceNet Master DTM 1 1 1 Descriptions of the Dialog Panes The table below gives an overview for the individual dialog panes descriptions a7 a Configuration 48 5 5 5 5 5 5 Parameter 61 Device Settings 62 Device Description Device 64 EDS 65 Diagnosis 7 Table 1 Descriptions Dialog Panes DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOCO910030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Introduction 6 113 1 1 2 Online Help The generic DeviceNet Slave DIM contains an integrated online help facility gt To open the online help click on Help or press F1 gt 1 1 3 List of Revisions Index Date Version Component Chapter 7 13 04 16 DevNetSlaveDTM dil Revised DevNetSlaveGUl ocx Section Requirements Windows 8 added 13 09 16 DevNetSlaveDT M dll Note about the configuration of 2 DevNetSlaveGUl ocx channel devices added Sections Configuration Steps Settings for Driver and Device Assignment and Driver updated Section Firmware Download updated DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOCO910030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Introduction 7 113
69. eased Public Hilscher 2009 2013 Error Codes 105 113 ODM Error Codes DBM V4 Error Code Definition Description CDBM_E WRITE_CANT_ ACCESS DATA OXC004C82F Unable to access SafeArray Data in the VARIANT CDBM_E WRITE DATA 0XC004C830 To write the data of this Element it must be given as a BSTR or as an Array of VT_UI1 VT_11 CDBM_E WRITE_BSTR_E1 0XC004C831 The BSTR string must have an even length CDBM_E WRITE_BSTR_E2 0XC004C832 The BSTR string must contain only hex digits 0 9 and a A f F CDBM_E WRITE _CANT_ INTERPRET ARRAY 0XC004C833 Unable to interpret data in the SafeArray CDBM_E WRITE_VT_ERROR 0XC004C834 Data type in the SafeArray is not VT_Ul1 or VT_11 CDBM_E WRITE_LENGTH 0XC004C835 Data length is invalid for write operation of this type CDBM_WRITE_ELEMENT 0XC004C836 Element not found in the Record of the Table CDBM_MIN_MAX_ERROR 0XC004C837 Can t write data because of min underflow or max overflow CDBM_TABLE EXIST 0XC004C838 Table already exist in the database CDBM_MIN_MAX_INVALID 0XC004C839 The Min value is greater than the Max Value CDBM_DEF_MIN_MAX_INVALID 0XC004C83A The Default Value is not in the range between the Min value and the Max Value CDBM_CANT_ CHANGE STRUCTURE _ OXC004C83B It s not allowed to change the structure WHILE RECORDS EXIST while Records exist in the Table CDBM NEW_STRUCT NEEDS TYPE OXC004C83C In a newly added structure the data type must be set also CDBM VALUE ERROR 0XC004C83D
70. ed Diagnosis information refer to section Overview Diagnosis on page 68 Tools Packet Monitor Under Tools the Packet Monitor and the IO Monitor are provided for test and diagnosis IO Monitor purposes For further information refer to section Packet Monitor on page 87 or section O Monitor on page 89 Table 3 Overview Dialog Panes Note Accessing the Diagnosis panes of the DeviceNet Slave DTM requires an online connection from the DeviceNet Slave DTM to the DeviceNet Slave DTM For further information refer to section Connecting Disconnecting Device on page 66 DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOC0910030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Introduction 16 113 1 4 4 OK Cancel Apply and Help OK Cancel Apply and Help you can use as described hereafter To confirm your latest settings click OK All changed values will be applied on the frame application database The dialog then closes To cancel your latest changes click Cancel Answer to the safety query Configuration data has been changed Do you want to save the data by Yes No or Cancel Yes The changes are saved or the changed values are applied on the frame application database The dialog then closes No The changes are not saved or the changed values are not applied on the frame application database The dialog then closes Cancel Back to the DTM To confi
71. ed to the device AN CAUTION The firmware download Stops the bus communication erases the configuration data base and overwrites the existing firmware in the device To complete the update and to make the device operable again please re download the configuration when this operation has finished Note Prior to the firmware download you must select the driver and the Slave device with or without firmware For further information refer to section Overview Settings on page 24 To load the firmware to the device 1 Inthe navigation area select Settings gt Firmware Download The dialog Firmware Download pane is displayed Mame F Browse Version AN CAUTION The Firmware download stops the bus communication erases the configuration database and overwrites the existing Firmware in the device To complete the update and to make the device operable again please re download the configuration when this operation has finished Figure 16 Firmware Download Parameter Meaning SSCS Name of the Firmware Version and Build Version of the Firmware Button to select the firmware file Button to download the firmware Table 14 Parameter Firmware Download 2 Select Browse YH The selection window Select Firmware File is displayed gt Enlarge the selection window to view the columns Hardware and Version DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Device
72. efore in the Device Firmware Files nx Assignment pane under Device selection suitable only was selected Recent folders Path of the recently opened folder ee As soon as the firmware file has been selected under Firmware the Name Version Build name the version and the build version as well as the device class for the Version Device Class selected firmware is displayed for the selected firmware Help Button to open the online help of the DTM re Table 15 Parameters Select Firmware File Further descriptions to the selection window Select Firmware File are included in the context sensitive help F1 key of the Microsoft Corporation Note After in the Device Assignment pane under Device selection all or suitable only has been set during a subsequent firmware download in the selection window Select Firmware File the following data are displayed or set for list box entry gt all suitable only In the selection window all files from the only firmware files from the Select Firmware File selected folder selected folder Under Files of Type All Files Firmware Files nxm Firmware Files nxf Validation A restricted validation A validation is made whether will be performed if the firmware file is suitable for the selected firmware the DeviceNet Slave DTM is applied for the download These settings in the selection window Select Firmware File can also be changed manually
73. ennnennenn 18 2 1 COMIGUIALION Steps aa tae 18 2 1 1 Slave DTM at the Root Line Stand Alone Slave u0000240 nennen 18 2 1 2 Slave DTM at the Master busline uus2204000B0enn nennen nnennnn nennen nennen 20 3 SETTINGS rio e a a Be es 24 3 1 Overview DCI Susana ee ee 24 3 2 Settings for Driver and Device Assignment 222002220222002200nennnnnnn nenn ennnenennennn 25 3 3 OW er a Baie ee o a O E 27 3 3 1 Verify or adapt Driver Settings oooccccccnconcccocnnnoconnnnoconcnnnonanoncnnannnnnnnnonnos 27 3 3 2 GNX Device Divers sen ee 29 3 3 3 netX DIVE o 29 3 3 4 Configuring netX Diverse ze aaa Be ae 30 3 3 5 netX Driver USB RS232 Conneclion uuusesseennennnnennennnnnnennnn nennen nnnnnnnnnn 31 3 3 6 netX Driver TCP IP Connection cccccccseeccceeseeeceeseeeceeseeecseuseessaeeessageees 34 3 4 Device ASSIM dt desd Lee 37 3 4 1 Scanning Tor Devices 37 3 4 2 Selecting the Device with or without firmware 4000044400 nennen nennen 40 3 4 3 Selecting the Device once more with Firmware u000444s0 nennen nennnee nen 41 DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOCOY10030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Table of Contents 3 113 3 5 Firmware DOWNI030 ee na 43 A CONFIGURATION ze ee a ee a ee 48 4 1 OYEIMIEW GONIGUTAH ON ar
74. entifier for the receiver of unsolicited sent packets from the firmware to the application configuration software er Source Queue Reference Contains an identifier of the sender Packet Data Length in Bytes Length of the send respectively receive data Packet Identification As Identifies identical data packets among each other ea tae Number oo a Ea Extension Feld forextensons qeseve Rout Routing Inormation intemal value ofthe firmware Table 40 Descriptions Packet Header Receive Data Under Receive gt Receive Data the receiving data of the packet which is transmitted back from the device to the application configuration software are displayed DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOC0910030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Tools 84 113 9 2 3 Example Get DPM I O Information To read data from a Slave device via Get DPM I O Information Request using the packet monitor you must proceed as described below The single steps are explained with help of sample data For more information on the steps under Settings and Configuration refer to the corresponding chapters in this manual Required information is easy to find via the overview in the section Configuration Steps on page 18 Requirements The function Get DPM I O Information Request can only be used if e The used Slave device supports
75. eout The connection transitions to the timeout state and remains in this state until it is Reset or Deleted e Auto reset The connection remains in the established state and immediately restarts the Inactivity Watchdog timer e Auto delete The connection class automatically deletes the connection if it experiences an Inactivity Watchdog timeout To reset the defalut values from the EDS file click ut tales DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOC0910030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Configuration 56 113 4 4 1 2 Change of State Connection If the Change of State Connection type was activated the elements of this connection type are editable Otherwise this dialog is disabled iM Consumption Size Bytes Connection Path Consuming POLL COS Data Path description valve Command bits 3 17 Bit 0 is ignored 0 W Production Connection Path Producing COS Data Path description Figure 32 Change of State Connection Consumption and Production With this type of connection both Master and Slave send the configured amount of data max 255 Byte to the respective remote station This data production is started at change in value trigger If the data production does not take place during a defined time interval the devices trigger the data production automatically to load the Watchdog Timer of the connectio
76. essages and the command or response code The minimum packet size amounts 40 Byte for the packet header The sending and receiving data are added For further information to the packet description refer to the Protocol API Manual gt Open the Packet Monitor via Tools gt Packet Monitor Send Packet header Send data Counter 0 Dest DODODODO e SFC OOO00000 State OOO00000 Dest ID 00000000 md OOO00000 arc ID OODODOD Ext OODOC OCI Len OODODODO Rout OOOOO000 ID Ooo00000 Auto Increment Ib iw 0030 we Heceive Facket header Receive data Counter 0 pst 00 01 102 03 04 05 06 07 08 109 4 SFE NE State E Dest ID md 0014 Src ID Len Ext 0DE Rout se 0030 v Figure 52 Packet Monitor Display Mode switches the representation of the send and reception data between decimal and hexadecimal gt Select Reset Counter to reset the packet counter DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOCO910030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Tools 82 113 9 2 1 Sending Packet Send Packet header Send data Counter 0 best oo000ni o 1 2 3 4 5 Je 7 Te 3 Ja SFC o0o00000 State 000 Po Dest ID oooo0000 Crd ooo0zFoo 20 J Sre ID OO Ext 00 cil Leni fonoonn12 Rout oooooooo f ID 00000001 Auto Increment IC iw 160 hd Put cyclic Put
77. et DPM IO Info Confirmation e g Revison 09 of the manual in section 5 3 2 DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOCO910030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Tools 4 Evaluate received packet Receive gt Packet header 87 113 gt Under Dest the receiver is displayed Under State the status code or possibly an error code is displayed _ All status and error codes are either to be found in this handbook via the section Overview Error Codes auf Seite 91 in the Dual Port Memory Manual or in the DeviceNet Slave Protocol API Manual 2 Under Cmd the response identification read request is displayed Receive Packet header Dest A 00000020 Src DODODODO State B ODDDOODO Dest ID 00000000 Cmd C OO002F0D Src ID 00000000 EXE oo000000 Rout 00000000 ii Len 0000002C ID 00000002 Figure 59 Example Reading data via Get DPM IO Info Receive gt Packet header Destination Que Handle indicates that the read request could be If during the execution of the read request an error was detected an error code is GET DPM IO INFO CONFIRMAITON Sample Data A Receiver 0x20 State 00000000 executed without error displayed Response 00002F0D Identification Read Confirmation Request DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOC09100
78. f the assigned driver gt Press the Fi key DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOC0910030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Settings 25 113 3 2 Settings for Driver and Device Assignment Important For a 2 channel device consecutively channel 1 or channel 2 must be assigned to the DTM The following steps are needed to establish a connection from the DeviceNet Slave DTM to the DeviceNet Slave device Verify or adapt Driver Settings Verify the Driver Settings and adapt them if necessary 1 Open the DTM configuration dialog gt In the FDT container netDevice double click to the DeviceNet Slave device icon 2 Verify that the default driver is checked and respectively check another or multiple drivers gt Select Settings gt Driver Note For PC cards cifX the cifX Device Driver is preset as a default driver For all the other Hilscher devices the netX Driver is preset as a default driver Use the cifX Device Driver if the DeviceNet Slave DTM is installed on the same PC as the DeviceNet Slave device Use the netX Driver to establish a USB Serial RS232 or TCP IP connection from the DeviceNet Slave DTM to the DeviceNet Slave device The 3SGateway Driver for netX V3 x is used only in relationship with CODESYS To search for devices on the network you can check one or multiple drivers simultaneou
79. form For detailed descriptions of each step refer to the sections noted in the column For detailed information see section The following two cases are considered e Slave DTM at the Root Line Stand Alone Slave e and Slave DTM at the Master busline 2 Channel Devices Important For a 2 channel device consecutively channel 1 or channel 2 must be assigned to the DIM and each must be configured individually 2 1 1 Slave DTM at the Root Line Stand Alone Slave Load device Depending of the FDT Container catalog For netDevice See Operating Instruction select Network gt Device Catalog Manual netDevice and select Reload Catalog netProject Create new Depending of the frame application See Operating Instruction project Open For the configuration software Manual of the Frame existing project select File gt New or File gt Open Application Insert Slave into Depending of the FDT Container configuration For netDevice See Operating Instruction in the Device Catalog under Gateway Stand Manual netDevice and Alone Slave click to the Slave netProject and insert the Slave via drag and drop to the root line in the network view Open the Slave Open the Slave DTM configuration dialog DTM configu Double click to the device icon of the Slave ration dialog The Slave DTM configuration dialog is displayed DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOC0910030I08EN
80. ftware may not be exported to countries where this is prohibited by the United States Export Administration Act and its additional provisions You are obligated to comply with the regulations at your personal responsibility We wish to inform you that you may require permission from state authorities to export re export or import the product 1 2 6 Registered Trademarks Windows XP Windows Vista Windows 7 and Windows 8 are registered trademarks of Microsoft Corporation DeviceNet is a trademark of ODVA Open DeviceNet Vendor Association Inc CODESYS is a registered trademark of 3S Smart Software Solutions GmbH Deutschland All other mentioned trademarks are property of their respective legal owners DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOC0910030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Introduction 11 113 1 3 About DeviceNet Slave DTM You can use the DeviceNet Slave DTM to configure DeviceNet Slave devices within a FDT Framework and to view the device diagnosis In a network project the DeviceNet Slave DTM can be dropped e tothe root line Stand Alone Slave e orto the Master busline of aDeviceNet Master DTM Slave DTM at the Root Line Stand Alone Slave Insert the DeviceNet Slave DTM to the root busline if you intend to configure only one single DeviceNet Slave device Slave DTM at the Master Busline Insert the De
81. further information refer to section Connecting Disconnecting Device on page 66 Important For a 2 channel device channel 1 or channel 2 each must be connected to the DTM separately How to proceed 1 Inthe Slave DTM diagnosis dialog check whether the communication is OK Diagnosis gt General Diagnosis gt Device status Communication must be green 2 Communication is green Open the IO Monitor and test the input or output data 3 Communication is not green Use Diagnosis and Extended diagnosis for troubleshooting Extended Diagnosis The Extended Diagnosis helps to find communication and configuration errors when default diagnosis fails For further information refer to section Overview Extended Diagnosis on page 72 DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOCO910030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Diagnosis 69 113 7 2 General Diagnosis Information regarding the Device State and other general diagnosis parameters are displayed in the General Diagnosis dialog Device state er _ommurication iw Run Ready a Error Network state ad Operate ig Idle da Stop A Offline Configuration state ig Configuration locked hal New configuration pending A Reset required W Bus on Communication error Watchdog time 1000 me Error count T Figure 42 General Diagnosis LED man Color State Device
82. g via OK IO Monitor Depending of the FDT Container For netDevice right click to the device icon of the Slave select Diagnosis select Tools gt IO Monitor Check the input or output data Disconnect Depending of the FDT Container For netDevice right click to the device icon of the Slave select Disconnect Selecting the Device once more with Firmware Configuring Slave Parameter General Settings Connection Configuration Parameter Device Settings See Operating Instruction Manual ofthe Frame Application Connecting Disconnecting Device Download Configuration Overview Diagnosis IO Monitor Connecting Disconnecting Device 49 51 53 61 62 Table 7 Getting started Configuration Steps Slave DTM at the Root Line Stand Alone Slave 2 1 2 Slave DTM at the Master busline DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOCO910030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Getting started 21 113 Short Description For detailed information see section 1 Load device catalog Depending of the FDT Container For netDevice select Network gt Device Catalog select Reload Catalog Create new project Open existing project Depending of the frame application For the configuration software select File gt New or File gt Open For netDevice in the Device Catalog click to the
83. ggle string found for this number CDBM_E ELEMENT OUT OF RANGE OXC004C81F An element wasn t found in the Record of a Table The element is not part of the Table Warning CDBM_E ELEMENT_NOT_IN_ TABLE 0XC004C820 CDBM_E CANNOT CONVERT 0XC004C821 INTO_CLIENT_TYPE The data can t be converted into the Client type A transaction is already open Please 0XC004C822 CDBM_E_TRANSACTION_ ALREADY_OPEN close this one first before opening a new one CDBM_I OLD_WITHOUT_HEADER 0X4004C823 Use of an old DBM file Format without Informational Header 0XC004C824 An HRESULT was received from a Subroutine CDBM_E HR FROM 0XC004C825 0XC004C826 0XC004C827 0XC004C828 0XC004C829 0XC004C82A 0XC004C82B OXC004C82C 0XC004C82D CDBM _E PARAMETER A Parameter is invalid CDBM_E NOTIMPL CDBM_E OUTOFMEMORY CDBM_E NO OPEN _TRANSACTION CDBM_E NO CONTENTS CDBM_REC_ NO NOT FOUND CDBM STRUCTURE ELEMENT NOT FOUND CDBM_E NO MORE_RECORDS_IN_TABTYPE CDBM E WRITE Method is currently not implemented Out of memory No transaction open No contents available Record not found Element of the Structure not found Table type 3 can contain only one record The data in the VARIANT must be given in a SafeArray The VARIANT contains no valid parray element CDBM_E WRITE _ NO PARRAY 0XC004C82E DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOC0910030I08EN Revision 8 English 2013 09 Rel
84. h newly sent packet Send Data gt Under Send gt Send data enter the send data of the packet which shall be transmitted from the application configuration software to the mailbox of the device The meaning of the transmitted data depends on the command or response code DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOC0910030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Tools 83 113 Sending Packets once or cyclic gt To send packet once select Put packet gt To send packet cyclic select Put cyclic 9 2 2 Receiving Packet Hheceive Packet header Receive data Counter 0 Desti 00000001 O le 13 4 5 16 B 19 ju sc aaa ae Tamm I TO nm Dest ID oooo0000 md ooo0zFo1 20 Src ID 000 Ext O0 cll Len 00000 Rout ogo00000 ID O000003E en 3 Figure 54 Packet Header and Receive Data Packet Header Under Receive gt Packet Header the elements of the packet header of the receiving packet are displayed which are transmitted back from the device to the application configuration software The packet header of the ic packets contain the elements described in the following table Destination e Handle Contains the identifier of the receiver for the packet destination task queue of the firmware Source Queue Handle Contains the identifier of the sender of the packet sending task Destination Queue Reference Contains an id
85. he Root Line Stand Alone Slave If in the network project the DeviceNet Slave DTM is dropped to the root busline proceed as follows General 1 Set UCMM and Fragmentation Timeout gt Select Configuration gt General in the navigation area Connection 2 Configure the device connection gt Select Configuration gt Connection in the navigation area Parameter 3 Set the parameter data of the device gt Select Configuration gt Parameter in the navigation area Device Settings 4 Setthe Device Settings gt Select Configuration gt Device Settings in the navigation area gt Under Start of Bus Communication select Automatically by device or Controlled by application option gt Under Application Monitoring gt set Watchdog time Close Slave DTM Configuration Dialog 5 Click OK in order to close the Slave DTM configuration dialog and to store your configuration Configuration Download to the DeviceNet Slave Device Note In order to transfer the configuration to the DeviceNet Slave device download the data of the configuration parameters in the DeviceNet Slave device See section Download Configuration on page 67 DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOC0910030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Configuration 50 113 Further Information a For more information refer to section General Settings on page 51
86. he configuration software select File gt Save See Operating Instruction Manual of the Frame Application Depending of the FDT Container For netDevice right click to the device icon of the Slave select Connect Connecting Disconnecting Device Depending of the FDT Container For netDevice right click to the device icon of the Slave select Download Download Configuration Depending of the FDT Container For netDevice right click to the device icon of the Slave select Diagnosis The Slave DTM diagnosis dialog is displayed 1 Check whether the communication is OK Diagnosis gt General Diagnosis gt Device status Overview Diagnosis Communication must be green 2 Communication is green Open thel lO Monitor and test the input or output data 3 Communication is not green Use Diagnosis and Extended diagnosis for troubleshooting close the Slave DTM diagnosis dialog via OK DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOCO910030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Getting started 23 113 Short Description For detailed information Page see section 16 IO Monitor Depending of the FDT Container IO Monitor For netDevice right click to the device icon of the Slave select Diagnosis select Tools gt IO Monitor Check the input or output data close the IO Monitor d
87. he device Ea States of the instance Date Set NES Valid Modified Parameter is changed not equal to data source a Changes directly made on the Device A Load configure diagnosis parameters Diagnosis is activated Device Diagnosis Status Save operation succeeded The save operation has been successful ea Further messages due to successful handling of device data O Firmware Download Fimwar Downoad is ruming Save operation failed The save operation has failed ll ng malfunction in the field device or its peripherals Table 6 Status Bar Icons 1 Offline State Disconnected J Data Set Save operation i zd ea Disconnected E Data Set Ed dl Save operation succeeded Firmware Download Disconnected Data Set 5 Firmware Download Firmware Download Disconnected E Data Set successful Online State and gt Diagnosis Connected u Device T Figure 4 Status Bar Display Examples DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOC0910030108EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Getting started 18 113 2 Getting started 2 1 Configuration Steps The following overview provides to you the step sequence on how to configure a netX based DeviceNet Master device with DeviceNet Master DTM as it is typical for many cases At this time it is presupposed that the hardware installation was done The overview lists all the steps in a compressed
88. ialog via OK 17 Disconnect Depending of the FDT Container Connecting Disconnecting For netDevice Device right click to the device icon of the Slave select Disconnect Table 8 Getting started Configuration Steps Slave DTM at the Master busline DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOC0910030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Settings 24 113 3 Settings 3 1 Overview Settings Settings Dialog Panes The table below gives an overview for the individual Settings dialog panes descriptions DeviceNet Slave DTM Folder Name Manual Section eS ja Navigation Area Driver Settings Verify or adapt Driver Settings a i tay Driver cifX Device Driver mei Device Assignment its pra Configuring netX Driver Navigation Area Device Assignment Settings Example Scanning for Devices Additional drivers can be Scanning for all Devices or for suitable only displayed 7 Selecting the Device with or without firmware Selecting the Device once more with Firmware Firmware Download Table 9 Descriptions of the Dialog Panes Settings Note To edit the Settings dialog panes you need User Rights for Maintenance Notice the descriptions in the section Settings for Driver and Device Assignment on page 25 To access to the online help with the descriptions of the drivers gt Select Settings gt Driver gt Name o
89. ilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOCO910030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Appendix 11 2 References 1 Device Type Manager DTM Style Guide Version 1 0 FDT JIG Order No lt 0001 0008 000 gt 109 113 2 DeviceNet Master Protocol API Manual Revision 9 Hilscher GmbH 2013 3 DeviceNet Slave Protocol API Manual Revision 12 Hilscher GmbH 2013 11 3 List of Figures Figure 1 Dialog Structure of the DeviceNet Slave DTM Figure 2 Navigation Area Figure 3 Status Bar Status Fields 1 to 6 Figure 4 Status Bar Display Examples Figure 5 Default Driver cifX Device Driver for PC cards cifX Figure 6 Default Driver cifX Device Driver for PC cards cifX example Figure 7 Default Driver netX Driver for Hilscher devices except for PC cards cifX example 27 Figure 8 Manual Selection of multiple drivers Example Figure 9 netX Driver gt USB RS232 Connection Figure 10 Figure 11 Figure 12 Figure 13 Figure 14 Figure 15 Figure 16 Figure 17 Figure 18 Figure 19 Figure 20 Figure 21 Figure 22 Figure 23 Figure 24 Figure 25 Figure 26 Figure 27 Figure 28 Figure 29 Figure 30 Figure 31 Figure 32 Figure 33 Figure 34 Figure 35 Figure 36 Figure 37 Figure 38 netX Driver gt TCP Connection 13 14 17 17 21 27 28 32 35 Device Assignment detected Devices The name
90. is purposes It provides to view data of the process data image and to change output data easily The display is always in a Byte manner ee ee rad disturbances are caused by this All output data written by the IO Monitor are transmitted at the bus and have effect on subordinate drives IO etc Columns 10 Display mode Decimal Intput data Offset o Ga Ta E 3 4 5 6 E a 3 A OA ca 207 D 0 0 0 i 0 0 0 10 0 0 T 0 U T 0 0 U 0 20 T u T 0 U 0 0 0 U U 30 T U 0 0 U 0 U 0 U 40 0 U U 0 0 0 0 U 0 U AQ 1 U U 0 U T 0 0 0 U en In T T n T n T ao Output data Offset O Go 0 1 E E 4 A E t 8 g e IE 9 0 0 0 0 0 0 0 0 10 T 0 0 0 0 T 0 0 U 0 20 0 0 0 0 0 0 0 U 0 0 30 0 0 0 0 0 T 0 0 0 0 40 0 0 U 0 0 0 0 0 0 0 AQ 0 0 0 0 U T 0 0 U 0 An in n T T n T n T n T ar Update Figure 61 IO Monitor Columns switches the number of columns Display mode switches the representation of the input and output data between decimal and hexadecimal Offset Go moves the indication of the data to the entered offset value gt Enter the output value and select Update Always the data of the process image are displayed also when these Bytes have not been reserved by the configuration DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOC0910030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Error Codes 90 113 10 Error Codes 10 1 Error Code Definition
91. its occupied Space Parity with 1 in the transmitted information word will be odd Default RS232 Even parity The parity is even if the number of bits No Parity occupied with 1 in the transmitted information word will be even Mark Parity if the parity bit is always 1 this will be named mark parity the bit does not contain any information Space Parity if the parity bit always 0 this will be named space parity the bit represents an empty space Keep Alive Timeout The Keep Alive mechanism is used to monitor whether the 100 60 000 ms connection to the device is active Connection errors are Default RS232 and detected using a periodic heartbeat mechanism The USB 2000 ms heartbeat mechanism will be initiated after the set time has elapsed if the communication has failed Restore Resets all settings in the configuration dialog to the default values Save Saving all settings made in the configuration dialog netX Driver gt Save USB RS232 Connection i e only for the selected connection type Save All Saving all settings made in the configuration dialog netX Driver i e for all connection types Table 11 Parameters netX Driver gt USB RS232 Connection DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOCO910030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Settings 34 113 3 3 6 netX Driver TCP IP Connection The communication fro
92. ked unchecked The netX Driver tries to establish a connection unchecked Default using the configured USB RS232 interface Baud rate Transfer rate number of bits per second 9 6 19 2 38 4 57 6 or 115 2 kBit s Default RS232 115 2 kBit s The device must support the baud rate DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOCO910030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Settings 33 113 Parameter Range of Value Default Value Number of stop bits sent after the transfer of the send data Stop bit 1 1 5 2 for synchronization purposes to the receiver Default RS232 1 Send Timeout Maximum time before the transfer of the transmission data is 100 60 000 ms canceled when the send process fails for example because Default RS232 and of the transfer buffer is full USB 1000 ms Reset Timeout Maximum time for a device reset including the re 100 60 000 ms initialization of the physical interface used for the Default RS232 and communication USB 5000 ms Byte size Number of bits per byte by byte specification 7 Bit 8 Bit Default RS232 8 Bit In the error detection in data transmission using parity bits No Parity parity describes the number of bits occupied with 1 in the Odd Parity transmitted information word Even Parity No Parity no parity bit Mark Parity Odd Parity The parity is odd if the number of b
93. le CIFX_INVALID CHANNEL 0x800A0003L No channel with the given index available CIFX_CALLBACK_CREATE_EVENT FAILED CIFX_CALLBACK CREATE RECV BUFFER Table 49 Generic Error Codes DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOC0910030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Error Codes 101 113 10 5 2 Generic Driver Error Codes Error Code Definition Value Description CIFX_DRV_CHANNEL_NOT_INITIALIZED 0x800B0032L Channel not initialized xOpenChannel not called CIFX_DRV_IO_CONTROL_FAILED Ox800B0033L IOControl call failed CIFX_DRV_NOT_OPENED Ox800B0034L Driver was not opened CIFX_DRV DOWNLOAD STORAGE _UNKN 0x800B0040L Unknown download storage type OWN RAMFLASH based found CIFX_DRV DOWNLOAD FW WRONG_CHA 0x800B0041L Channel number for a firmware NNEL download not supported CIFX_DRV DOWNLOAD MODULE NO BAS 0x800B0042L Modules are not allowed without a Base EOS OS firmware Table 50 Generic Driver Error Codes DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOCO910030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Error Codes 102 113 10 5 3 Generic Device Error Codes Error Code Definition Value Description CIFX_DEV_DPM ACCESS ERROR 0x800C0010L Dual port memory not accessable board not found CIFX_DEV_MAILBOX FULL 0x800C0016L Send mailbox is full CIFX_DEV_GET_
94. load the Transmission Trigger Timer and the Watchdog Timer If no data production of the remote station takes place within this time so the connection changes into a watchdog timeout error Incoming data productions of the remote station load the Watchdog Time again to the fourfold value of the Expected Packet Rate The Watchdog Timeout Action defines the device behavior when the watchdog timer in the device Slave expires The following actions are adjustable e Timeout The connection transitions to the timeout state and remains in this state until it is Reset or Deleted e Auto reset The connection remains in the established state and immediately restarts the Inactivity Watchdog timer e Auto delete The connection class automatically deletes the connection if it experiences an Inactivity Watchdog timeout DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOC0910030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Configuration 59 113 4 4 1 4 Bit Strobe Connection If the Bit Strobe Connection type was activated the elements of this connection type are editable Otherwise this dialog is disabled Consumption Size 5 Bytes Broadcast Production Size 0 Connection Path User defined ee Path description User defined Figure 36 Bit Strobe Connection Consumption and Production Bit strobe command and response messages rapidly move small amounts
95. loss of earnings resulting from the use of the information contained in this publication DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOCO910030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Introduction 9 113 1 2 3 Exclusion of Liability The software was produced and tested with utmost care by Hilscher Gesellschaft f r Systemautomation mbH and is made available as is No warranty can be assumed for the performance and flawlessness of the software for all usage conditions and cases and for the results produced when utilized by the user Liability for any damages that may result from the use of the hardware or software or related documents is limited to cases of intent or grossly negligent violation of significant contractual obligations Indemnity claims for the violation of significant contractual obligations are limited to damages that are foreseeable and typical for this type of contract It is strictly prohibited to use the software in the following areas e for military purposes or in weapon systems e for the design construction maintenance or operation of nuclear facilities e in air traffic control systems air traffic or air traffic communication systems e in life support systems e in systems in which failures in the software could lead to personal injury or injuries leading to death We inform you that the software was not developed for use in
96. m the DTM to the device via a TCP IP Connection is used in the following two typical applications Application 1 The device has its own Ethernet interface The DTM is installed on a PC and the TCP IP connection is established from this PC to the stand alone device The IP address of the device is used Application 2 The device is installed in a remote PC The DTM is installed on an additional PC and the TCP IP connection is established from this PC to the remote PC The IP address of the remote PC is used For the TCP IP connection is made on the remote PC the cifX TCP IP server must be started The cifX TCP IP server allows the remote access to the device via a TCP IP connection Note An exe file for the cifXTCP IP server is provided on the product CD inthe Tools directory Via the TCP IP interface of the device or of the remote PC the device is configured or diagnosis is performed DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOCO910030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Settings 35 113 3 3 6 1 Driver Parameters for netX Driver TCP IP Connection The settings of the driver parameters for the TCP IP connection are made via the netX Driver TCP Connection configuration dialog gt Open the TCP Connection dialog via navigation area Settings gt Driver gt netX Driver dv The dialog netX Driver is displayed gt Select TCP Connection
97. me 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 O defines no Production 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 1000 ms 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 fourfold value is used by the device later to reload its Watchdog Timer If no data production of the remote station takes place within this time so the connection changes into a watchdog timeout error Incoming data productions of the remote station load the Watchdog Time again to the fourfold value of the Expected Packet Rate Note the Production Inhibit Time is verified against the Expected Packet Rate If the Expected Packet Rate value is unequal to zero but less than the Production Inhibit Time value then an error message is displayed by the application The Watchdog Timeout Action defines the device behavior when the watchdog timer in the device Slave expires The following actions are adjustable e Tim
98. mmunication ms Keep Alive Timeout The Keep Alive mechanism is used to monitor whether the 100 60 000 ms ms connection to the device is active Connection errors are Default TCP IP 2000 detected using a periodic heartbeat mechanism The ms heartbeat mechanism will be initiated after the set time has elapsed if the communication has failed Restore Resets all settings in the configuration dialog to the default values Save Saving all settings made in the configuration dialog netX Driver gt Save TCP IP Connection i e only for the selected connection type Save All Saving all settings made in the configuration dialog netX Driver i e for all connection types Table 12 Parameters netX Driver gt TCP Connection introduced in Windows XP SP2 a limit of concurrent half open outbound TCP IPconnections connection attempts to slow the spread of virus and malware from system to system This limit makes it impossible to have more than 10 concurrent half open outbound connections Every further connection attempt is put in a queue and forced to wait Due to this limitation a large IP range used in combination with a low scan timeout could prevent the connection establishment to a device gt Note Do not use large IP ranges in combination with a low scan timeout Microsoft DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOCO910030I08EN Revision 8 English 2013 09 Released Public
99. mplemented CDBM_E _NO_APPEND_IN 0XC004C85E Method IDbmRecord AppendData is not STRUCTURED_RECORDS allowed for structured records DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOCO910030I08EN Revision 8 English 2013 09 Released Public O Hilscher 2009 2013 Error Codes 107 113 ODM Error Codes DBM V4 CDBM_E DATA UNAVAILABLE 0XC004C85F No data available CDBM_E CANT_CONVERT_ INTO 0XC004C860 Unable to convert the value into the Element type CDBM_E DBM FILE OVERFLOW 0XC004C861 You try to write a RCS like database which needs too much bytes CDBM_E PW_ERROR 0XC004C862 Password not correct CDBM_E FILELENGTH_CORRUPT 0XC004C863 The file length doesn t correspond to the length given in the Header CDBM_E_STRUCT_TYPE 0XC0040864 Error in the file CDBM_E_MD5SUM_INVALID OXC004C865 MD5 sum invalid CDBM_E STRUCT LENGTH OXC004C866 Error in the expected and given structure length at a specific offset in the file CDBM_E APPEND 0XC004C867 Append of data is only allowed if the Record contains only one data field and the field type will support this CDBM_APPEND_NOT_ SUPPORTED 0XC004C868 Append of Data not supported by this filed type CDBM_DATA_TYPE_APPEND_ ERROR 0XC004C869 Can t append Data of this type CDBM_E UNSTRUCTURED TABLE _ 0XC004C86A A Table without structure information DOESNT_SUPPORT_LENGTH doesn t support a record length CDBM_E DISABLED WHILE _ 0XC004C86B The Method is disabled
100. n again Depending on how the device behavior is configured they can send back a confirmation message which contains any quantity of data and or status information Before a Change of State connection is initialized by the Master it reads out the consumed and produced connection size of the data from the device Slave and compares this values with the values configured in the Master during configuration If different values are determined the connection can not build up Data production only over Change of State keeps the bus load as low as possible while data than can be transmitted as fast as possible by each device because bus conflicts are less possible So you can get high performance data transmission with in comparison low baud rates Timing Production Inhibit Time 200 ms Expected Packet Rate S00 ms cachee Tuei SHE Figure 33 Change of State Connection Timing DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOC0910030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Configuration 57 113 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
101. n the driver board or channel number IP address or COM interface Hilscher 2009 2013 Settings 39 113 3 4 1 1 Scanning for all Devices or for suitable only all 1 Under Device Selection select all 2 Select Scan Scan progress 5 5 Devices Current device Scan Device selection al Device Mardare Pot ollo sit number Serial number _ Diver ___ Chemel Prato Access path Fre ae A Pre a FE O Devicellet nia 20027 CIF Device Driver Undefined Undefined dx SYS O af nia 20058 nets Driver Undefined Undefined 1192 168 1 O Ethernet Ethernets f nia 0250 CIFX Device Driver Undefined Undefined ck 54 S O 1 CANopen nia 20022 CIFA Device Driver Undefined Undefined ciFx0_54 5 Figure 12 Device Assignment detected Devices The name of the device class is displayed Example for Devices without Firmware gt In the table all devices are displayed which are attainable in the network and which can be connected to a single DTM each via the preselected drivers Note During a subsequent firmware download in the selection window Select Firmware File all files from the selected folder are displayed under Files of Type All Files is displayed and the check box Validate the selected firmware file is unchecked suitable only 1 Under Device Selection select suitable only 2 Select Scan gt In the table all devices are displayed which can be connected to the DeviceNet Slave D
102. of the IP scanning range right side 5 Click Save to save the IP address or the IP range After saving the changed driver parameters these parameters are used for the device assignment when scanning devices DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOC0910030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Settings 31 113 3 3 5 netX Driver USB RS232 Connection The communication from the DTM to the device via an USB RS232 Connection is used when the DTM is installed on a PC and between the PC and the device e an USB connection e ora serial connection RS232 exists The DTM accesses the device via the USB interface or via the RS232 interface This requires either to connect an USB port of the PC to the USB interface of the device using an USB cable or to connect a physical COM port of the PC to the RS232 interface of the device via a serial cable The netX Driver USB RS232 Connection supports all physical and virtual COM ports available on the PC Via the RS232 interface or USB interface the device is configured or diagnosis is performed DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOCO910030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Settings 32 113 3 3 5 1 Driver Parameters for netX Driver USB RS232 Connection The settings of the driver parameters for the U
103. of the device class is displayed Example for a device without firmware 3 Device Assignment detected Devices The name of the device class is displayed Example for Devices without Firmware 39 Device Assignment Selecting the Device The name of the device class is displayed Example for a device without firmware one Device is selected 40 Device Assignment Selecting the Device The name of the device class is displayed Example for Devices with and without Firmware one Device is selected 41 Device Assignment Selecting the Device The name of the device class is displayed Example for a device with firmware one Device is selected Firmware Download Window Select Firmware File Example CIFX Request Select Firmware File Example Firmware Download Download Firmware Download Question Clock Symbol and Hook Symbol green Firmware Download Progress Bar 42 43 44 46 46 46 47 47 General Settings Attributes of the device identification Slave DTM at the Root Line Stand Alone Slave 91 General Settings Attributes of the device identification Slave DTM at the Master busline 51 General Settings Verify Device ID 92 General Settings Enable Address Switch Slave DTM at the Root Line Stand Alone Slave Exmaple COMX 10XX DNS DNS Configuration Dialog Connection Indication of possible combinations of connection types Warning invalid connection
104. og panes descriptions DeviceNet Slave DTM Folder Name Section Manual Page Ss Packet Monitor IO Monitor Navigation Area _ Diagnosis Extended Diagnosis 3 Tools A Facket Monitor TO Monitor Navigation Area Tools Table 38 Descriptions of the Diagnosis Panes Online Connection to the Device Note Accessing the Tools dialog panes of the DeviceNet Slave DTM requires an online connection from the DeviceNet Slave DTM to the DeviceNet Slave device For further information refer to section Connecting Disconnecting Device on page 66 DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOCO910030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Tools 81 113 9 2 Packet Monitor The Packet Monitor serves for test and diagnosis purposes Data packets i e messages are self contained blocks of defined data length The packets are used to communicate with the firmware and they are exchanged between the application configuration software and the firmware in the device Packets can be sent once or cyclically to the connected device controlled by the user and packets received can be displayed Data packets comprise from a Packet Header and the Send Data or from a Packet Header and the Receive Data The packet header can be evaluated by the receiver of the packet and contain the sender and receiver address the data length an ID number status and error m
105. on can be found in the corresponding device manual Parameter Group ALL Display Mode Decimal jActi Clasa Inst Att Type Acc Param Name Value Min Man Description El EDS Default values Figure 38 Parameter Configuration Parameter Group ALL All parameter groups defined in the EDS file are merged in one table A parameter group defined by the user is displayed ahem In the EDS file of the device further parameter groups can be defined which are also displayed in the pull down menu Parameter Group The name of XXX this parameter group itself is also defined in the EDS file Display Mode Decimal The values Min and Max in the table are indicated in decimal notation by default By selecting the Display Mode Hexadecimal the values are shown in hexadecimal notation Hexadecimal Table 20 Change Parameter Data By using a data set the respective parameter value for the Master configuration are approved and transferred to the Slave by the Master during the initialization phase To enable or disable all of the data sets at the same time click ajaj DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOCO910030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Configuration 62 113 A description of the individual parameters indicated by Class Instance and Attribute can be referred in the device description of the manufa
106. onnected from the DTM 6 2 Download Configuration Note To download configuration parameter data to the DeviceNet Slave device an online connection from the DeviceNet Slave DTM to the DeviceNet Slave device is required Further information can be found in the section Connecting Disconnecting Device on page 66 To transfer the configuration with the corresponding parameter data to the DeviceNet Slave device you download the data to it using the frame application of the configuration software DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOCO910030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Diagnosis 68 113 7 Diagnosis 7 1 Overview Diagnosis The dialog Diagnosis serves to diagnose the device behavior and communication errors For diagnosis the device must reside in online state Diagnosis Panes The table below gives an overview for the individual Diagnosis dialog panes descriptions DeviceNet Slave DTM Folder Name Section Manual Page Navigation rea General Diagnosis ET Diagnosis Firmware Diagnosis tae General Diagnosis Firmware Diagnosis _ Extended Diagnosis Navigation Area Diagnosis Table 25 Descriptions of the Diagnosis Panes Online Connection to the Device Note Accessing the Diagnosis panes of the DeviceNet Slave DTM requires an online connection from the DeviceNet Slave DTM to the DeviceNet Slave device For
107. packet Figure 53 Send gt Packet Header and Send Data Packet Header Under Send gt Packet Header the elements of the packet header of the sending packet are displayed which is transmitted from the application configuration software to the device The packet header of the sending packets contain the elements described in the following table Element Deseption S Destination Queue Handle Contains the identifier of the receiver for the packet destination task queue of the firmware Ste Source Queue Handle Contains the identifier of the sender of the packet sending task Destination Queue Reference Contains an identifier for the receiver of unsolicited sent packets from the firmware to the application configuration software SreiD Source Queue Reference Contains an identifier of the sender Packet Data Length in Bytes Length of the send respectively receive data Packet Identification As Identifies identical data packets among each other Unique Number State Status Error Code Transmit status or error codes to the packet sender Ext Extension Field for extensions reserved Rout Routing Information Internal value ofthe firmware Table 39 Descriptions Packet Header gt Under Dest select the receiver destination task queue gt Under Cmd select the command identification Request Auto Increment ID is an increment for the identifier of the data packets and increments the ID by 1 for eac
108. ponse while a connection is established Default 100 ms IP Range Configuration Disable IP Range checked No connection checked unchecked Default unchecked The netX Driver tries to establish a connection using the configured TCP IP interface IP Address left Enter the IP address of the device if Use IP Range is not valid IP address checked Default 192 168 1 1 Enter the start address of the IP scanning range if Use IP Range is checked Use IP Range checked An IP address range is used checked unchecked Default unchecked IP Address right Enter the ending address of the IP scanning range only if valid IP address Use IP Range is checked Default 0 0 0 0 Address Count Displays the scanning range address count depending on recommended 10 the selected IP start or IP end address For this read the note given below TCP Port Identifies the endpoint of a logical connection or addresses a specific endpoint on the device or PC Default Hilscher device 50111 Send Timeout ms Maximum time before the transfer of the transmission data is 100 60 000 ms canceled when the send process fails for example because Default TCP IP 1000 of the transfer buffer is full ms unchecked Only one IP address is used O 65535 Reset Timeout ms Maximum time for a device reset including the re 100 60 000 ms initialization of the physical interface used for the Default TCP IP 2000 co
109. r False Transmit Frame Succeded o Transmit Error Summary 041532 Receive Frame Succeded o Receive Error Summary U Transmit Error Counter 125 Receive Error Counter U Arbitration Lost Inications Dropped due to Fifo Full Confirmations Dropped due to Fifo Receive Standardframes Filtered Receive extended frames Filtered Receive Standardframes passed Receive extended frames passed mAIoooacaoa oa Figure 51 Extended Diagnosis gt CAN_DL gt CAN Driver Status Name Description S CAN Status Diagnosis status of CAN specific error levels Bus Off Indicates the respective status of the CAN bus For Error Warning further information refer to the API manual ErrorPassive Reserved Diagnosis status 24 Volt Network Error Diagnosis status of DeviceNet specific error levels For further information refer to the API manual Service Diagnosis counter of CAN errors Indicates the services processed The services of the single packets are described in the API manual Table 37 Extended Diagnosis gt CAN_DL gt CAN Driver Status DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOC0910030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Tools 9 Tools 80 113 9 1 Overview Tools Under Tools the Packet Monitor and the IO Monitor are provided for test and diagnosis purposes Tools Panes The table below gives an overview for the individual Tools dial
110. r in internal read state DRV_E CMD ACTIVE 0x8004C004 DRIVER Command on this channel is active DRV_E PARAMETER_UNKNOWN 0x8004C005 DRIVER Unknown parameter in function DRV_E WRONG _DRIVER_VERSION 0x8004C006 DRIVER Version is incompatible with DLL DRV_E PCI SET_CONFIG_MODE 0x8004C007 DRIVER Error during PCI set configuration DRV_E PCI READ DPM_LENGTH 0x8004C008 DRIVER Could not read PCI dual port memory length DRV_E_PCI_SET_RUN MODE 0x8004C009 DRIVER Error during PCI set run mode DRV_E DEV DPM ACCESS ERROR 0x8004C00A DEVICE Dual port ram not accessable board not found DRV_E DEV NOT READY 0x8004C00B DEVICE Not ready ready flag failed DRV _E DEV NOT RUNNING DEVICE Not running running flag failed DRV _E DEV WATCHDOG FAILED DEVICE Watchdog test failed DRV _E DEV_OS VERSION ERROR DEVICE Signals wrong OS version DRV _E DEV SYSERR DEVICE Error in dual port flags DRV _E DEV MAILBOX FULL DEVICE Send mailbox is full DRV _E DEV PUT TIMEOUT DEVICE PutMessage timeout DRV E DEV GET TIMEOUT DEVICE GetMessage timeout DRV E DEV GET NO MESSAGE DEVICE No message available DRV E DEV RESET TIMEOUT DEVICE RESET command timeout DRV_E_DEV_NO_COM_FLAG 0x8004C015 DEVICE COM flag not set Check if Bus is running DRV E DEV EXCHANGE FAILED DEVICE 1 O data exchange failed DRV_E DEV EXCHANGE TIMEOUT DEVICE I O data exchange timeout DRV_E DEV COM MODE UNKNOWN DEVICE I O data mode unknown DRV_E DEV FUNCTION FAILED DEVICE Function call failed DRV_E DEV _DP
111. r side of the dialog pane Shows which firmware is loaded to which device channel The data for the used channel consists of the protocol class and the communication class a For devices without firmware Undefined Undefined b For devices with firmware Protocol name corresponding to the used Firmware Depending on the used driver in the column Access path different data to the device are displayed For the cifX Device Driver the following data are displayed a For devices without firmware cifX OtoN _SYS b For devices with firmware cifX OtoN _Ch 0to3 cifX OtoN Board number 0 to N Ch 0t03 Channel number 0 to 3 If in the table a device is checked under Access path at the lower side of the dialog pane the driver identification or depending on the used driver additional data to the device will be displayed For the cifX Device Driver the following data are displayed a For devices without firmware cifX OtoN _SYS b For devices with firmware cifX OtoN _Ch 0to3 cifX OtoN Board number 0 to N Ch 0t03 Channel number 0 to 3 Table 13 Parameters of the Device Assignment DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOC0910030I08EN Revision 8 English 2013 09 Released Public Depending on the device and on the driver board or channel number IP address or COM interface driver identification ID depending on the device and o
112. river 1 103 2 5183 B54C8CC7 F3335 4135 8405 6E 12FCRSEE6 2 Figure 8 Manual Selection of multiple drivers Example DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOC0910030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Settings 29 113 3 3 2 cifX Device Driver gt In the DeviceNet Slave DTM for the cifX Device Driver no driver dialog pane is available since for the cifX Device Driver no driver settings are required The cifX Device Driver will be used if the DeviceNet Slave DIM is installed in the same PC as the DeviceNet Slave device Note To establish a connection from a DTM to a Slave device via the cifX Device Driver the cifX Device Driver must be installed and the driver must have access to the Slave device 3 3 3 netX Driver The netX Driver is used to connect the DTM to the device via different connection types The DTM communicates with the device via an USB connection a serial RS232 connection or a TCP IP connection The netX Driver establishes e via the USB interface of the device and the USB port of the PC an USB connection to the device e via the RS232 interface of the device and the COM port of the PC a serial connection RS232 to the device e and via Ethernet a TCP IP connection to the device To connect the DTM to the physical layer of the device the netX Driver software works in combination with the software components
113. rm your latest settings click Apply All changed values will be applied on the frame application database The dialog remains opened Hep To open the DTM online help click Help Table 4 OK Cancel Apply and Help 1 4 5 Table Lines In the DTM dialog pane table lines can be selected inserted or deleted To select the first line of a table use First Line To select the previous line of a table use Previous Line To select the next line of a table use Next Line To select the last line of a table use Last Line Create a new Line inserts new lines into the table Delete selected Line deletes the selected line from the table Table 5 Selecting inserting deleting Table Line DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOC0910030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Introduction 17 113 1 4 6 Status Bar The Status Bar displays information about the current state of the DTM The current activity e g download is signaled graphically via icons in the status bar T Disconnected J Data Set 1 2 345 6 Figure 3 Status Bar Status Fields 1 to 6 Eom Icon Meaning DTM Connection States Connected Icon closed Device is online Disconnected Icon opened Device is offline Data Source States Data set The displayed data are read out from the instance data set database Device The displayed data are read out from t
114. rmation packet status 10 is Table 31 Extended Diagnosis gt Folder Name gt IniBatch Status The task status Confirmation Result is bus specific The other task statuses are rcx related error codes DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOCO910030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Extended Diagnosis 75 113 8 4 DNS FAL 8 4 1 DNS Common Status Task states Mame Value Mac ID U Baud Rate 500 kBaud Produced Size O Byte Consumed Size 5 Byte Watchdog Time O ms Contig Flags Summary 0x00000000 Config Flag l ISNORE_ADDR_S FALSE Config Flag 29 CONTINUE_ON BU FALSE Config Flag CONTINUE ON LO FALSE Config Flag 41 RECVIDLE_CLESR_ FALSE Config Flag S5 RECYIDLE USER FALSE Config Flagi6 24vVOCINVERT FALSE Enable Flags Summary 00000003F Enable Flag 1 WENDORID TRUE Enable Flag 2 PRODUCTTYPE TRUE Enable Flagi PRODUCTCODE TRUE Enable Flagi MAIORMINORREY TRUE Enable FlagiS SERIALNR TRUE Enable Flag 6 PRODUCTNAME TRUE Vendor ID 203 Product Type 12 Product Code 11 Minor Revision 1 Major Revision 1 Serial Number 206331153 DAS State DUP WAIT SEND Status Flags Summary Ox00000007 Status Flag 1 BUS PRM VALID TRUE Status Flags BUS START TRUE Status Flags 3 24 NETWORK TRUE Status Flags 4 WETWORK STAT FALSE Rs Interrupts U Ts Interrupts RA Cyer
115. rocess is not registered as a server on this device CODM3 E DEVICE NO MESSAGE 0x8004C75D No message available CODM3_E _TRANSFERTIMEOUT 0x8004C 760 Message transfer timeout CODM3 E MESSAGE INSERVICE 0x8004C761 Table 46 ODM Error Codes General ODM Error Codes DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOCO910030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Error Codes 96 113 10 4 2 General ODM Driver Error Codes Error Code Definition Value Description CODM3 E DRV_OPEN_ DEVICE 0x8004C7A0 Packet type unsupported by driver CODM3_ E DRV INVALID IDENTIFIER 0x8004C7A1 Invalid device identifier CODM3_E DRV DEVICE PARAMETERS _ 0x8004C7A3 Parameters differ from requested device MISMATCH CODM3_E DRV_DEVICE_NOMORE_TX 0x8004C7A6 Device connection limit reached CODM3_E_DRV_DEVICE_COMMUNICATION 0x8004C7A9 Device communication error Table 47 ODM Error Codes General ODM Driver Error Codess DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOCO910030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Error Codes 97 113 10 4 3 cifX Driver Specific ODM Error Codes cifX Driver Specific ODM Error Codes Error Code Definition Description DRV_E BOARD NOT INITIALIZED 0x8004C001 DRIVER Board not initialized DRV_E INIT_STATE_ERROR DRIVER Error in internal init state DRV E READ STATE ERROR DRIVER Erro
116. run Ta Overrun Ts Aborts Error Interrupt Bus OFF Count Reset Count Forno Ooo D Figure 46 Extended Diagnosis gt DNS_FAL gt DNS Common Status Name Description S Status Common DNS Diagnosis status Indicates the current status of the single tasks For further information refer to the API manual Table 32 Extended Diagnosis gt DNS_FAL gt DNS Common Status DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOC0910030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Extended Diagnosis 76 113 8 4 2 AP Commands Counter Task states Register Aplication Reg 2 Register plication nf Pos Register plication Inf Meg Init Reg Init Inf Pos Init Inf Meg Oh ho Ta Figure 47 Extended Diagnosis gt DNS_FAL gt AP Commands Counter Name Description Service Diagnosis counter of the FAL layer Indicates the services processed The services of the single packets are described in the API manual Table 33 Extended Diagnosis gt DNS_FAL gt AP Commands Counter 8 4 3 CAN Command Counter Task states CAN Data Ind T CAN Data Reg 1 CAN Data Inf Pos T CAN Data Inf Weg 0 Figure 48 Extended Diagnosis gt DNS_FAL gt CAN Command Counter Name Description S O Service Diagnosis counter of the FAL layer Indicates the services processed The services of the single packets are described in the API m
117. s DOCO910030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Settings select Firmware Fle Look in jj CIFX en i Marne Firmware Hardware Version p Li ECM Recent Places de ECS VAX EM mit QC JE PNM Li PNS V3 5 X 153M i oe cifx asm nod AS Interface Master CIFX px Build x Pr of cifx2dpm nxt PROFIBUS DP Master CIFX Bcx Build x p OE cifx2dps nxf PROFIBUS DP Slave CIFX x x Build x Me OME cifucos md CC Link Slave CIFX bx Build x Computer ge cifecom nxf CANopen Master CIFX pew Build x D cifcos nd CANopen Slave CIFX cx Build x a SE cifxdnm nxf DeviceNet Master CIFX px Build x Network od cifdns nxf DeviceNet Slave CIFX px Build x OE cifxdpm nxf PROFIBUS DP Master CIFX pex Build x Of cifedps nxf PROFIBUS DP Slave CIFX Dex Build x SEE cifxecm nf EtherCAT Master CIFX x Build x od cifxecs nxf EtherCAT Slave CIFX px Build x P cifxeim nxf EtherNet IP Scanner CIFX px Build x OX cifxeis nxf EtherMet IP Adapter CIFX px Build x gt cifxmpi nxf PROFIBUS MPI Messaging CIFX px Build x Of cifxomb md Open Modbus TCP Messaging CIFA ex Build x OE cifxpls nxf POWERLINE Controlled Node CIFX e x Build x gt crApnom nxt PROFINET 10 10 Controller CIFX be x Build x Of cifxpns nxf PROFINET 10 10 Device CIFX Dex Build x ot ciba3m nf SERCOS I Master CIFX px Build x OME cifusds nad SERCOS M Slave CIFX x x Build x D ciforrs md VA
118. s Counter 78 Table 37 Extended Diagnosis gt CAN_DL gt CAN Driver Status 79 Table 38 Descriptions of the Diagnosis Panes 80 Table 39 Descriptions Packet Header 82 Table 40 Descriptions Packet Header 83 Table 41 Overview Error Codes and Ranges 91 Table 42 RCX General Task Errors 92 Table 43 RCX Common Status Errors Codes 93 Table 44 RCX Status amp Error Codes 94 Table 45 RCX Status 4 Error Codes Slave State 94 Table 46 ODM Error Codes General ODM Error Codes 95 Table 47 ODM Error Codes General ODM Driver Error Codess 96 Table 48 cifX Driver Specific ODM Error Codes 99 Table 49 Generic Error Codes 100 Table 50 Generic Driver Error Codes 101 Table 51 Generic Device Error Codes 102 Table 52 CIFX API Transport Error Codes 103 Table 53 CIFX API Transport Header State Error Codes 103 Table 54 ODM Error Codes DBM V4 107 Table 55 Settings D Displaying X Editing Configuring 108 Table 56 Configuration D Displaying X Editing Configuring D X Displaying all limited Editing or Configuring 11 5 Glossary Data Packets DTM 108 Data packets i e messages are self contained blocks of defined data length The packets are used to communicate with the firmware and they are exchanged between the application configuration software and the firmware in the device Using the configuration software feature Packet Monitor Packets can be sent once or cyclically to the connected device controlled by the
119. scription 64 113 5 Device Description 5 1 About Device Description Dialog Panes Device Description The table below gives an overview for the Device Description dialog panes descriptions DeviceNet Slave DTM Folder Name Section Page Navigation area E J Configuration EDS 65 Device Description a Device EDS Navigation Area Description Table 22 Descriptions of the Dialog Panes Device Description 5 2 Device The Device Info dialog contains manufacturer information about the device which is defined in the EDS file The following information is indicated Parameter Vendor name Vendor name of the device Vendor ID Identification number of the manufacturer Product Type Communication Adapter Product Type String Product Name as string Product Code Product code of the device Product Name Name of the device The variable Product Name is a text string that should represent a short description of the product product family Table 23 General Device Information DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOCO910030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Device Description 65 113 5 3 EDS The EDS Viewer shows the content of the EDS file in a text view Under Filename the file directory path and the file name of the displayed EDS file is displayed Find what offers a search feature to search for text contents within the tex
120. sly gt Verify that the default driver for your device is checked gt f necessary check another driver or multiple drivers Configure Driver Note The cifX Device Driver requires no configuration The configuration of the 3SGateway Driver for netX V3 x is carried out via the CODESYS surface If you use the netX Driver you respectively must configure it 3 Configure the netX Driver if necessary For the driver netXDriver an individual driver dialog window can be opened where you can configure the driver gt Select Settings gt Driver gt netX Driver gt For netX Driver and communication via TCP IP set the IP address of the device Adjust the driver parameters netX Driver USB RS232 only if they differ from the default settings DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOCO910030l08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Settings 26 113 Assigning the Slave device to the DTM 4 Y YV V WV scan for and select the devices with or without firmware Select Settings gt Device Assignment Under Device selection select suitable only or all and then Scan In the table check the required devices Select Apply Select and download the Firmware lt gt Ov v Vv N Y Y WV If not yet a firmware was loaded to the device select and download the firmware Select Settings gt Firmware Download Select and
121. st correspond with the element number CDBM_TABTYPE1_ NO DATA_ OXC004C854 When reading the records of Table type 1 FOUND FOR RECORD and structure definitions are present it s assumed that for each structure element a corresponding record must exist CDBM _E TABTYPE1_ WRITE _ 0XC004C855 When writing the records of Table type 1 ELEMENT_NE_RECORD elementwise and structure definitions are present it s only allowed to write the corresponding element number in each record CDBM_E TABTYPE1_WRITE_ OXC004C856 When writing the records of Table type 1 ELEMENT NOT FOUND with an array and structure definitions are present it s assumed that a corresponding element number of this record exist CDBM_ _ TABLE NAME EXCEEDS _ 0X4004C857 The Table name exceeds the maximum RCS_ RANGE Informational length of RCS compatible Table names CDBM_W CUT_STRING 0X8004C858 The string exceeds the maximum length Warning and will be limited to the maximum length CDBM I STRING_TOO SHORT 0X4004C859 The string is below the minimum length Informational The minimum length will be reduced CDBM STRING_TOO_ LONG 0X4004C85A The string is exceeding the maximum The Informational maximum length will be extended CDBM _E STRING TOO SHORT OXC004C85B The string is below the minimum length Error CDBM_E STRING TOO LONG 0XC004C85C The string is exceeding the maximum Error length CDBM_E WRONG_TYPE_FOR_WRITE 0XC004C85D Writing on the Element type with the given Data type is not i
122. t driver for your device is checked DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOC0910030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Settings 28 113 Default Driver Pre settings in the Configuration Software For PC cards cifX the cifX Device Driver is preset as a default driver For all the other Hilscher devices the netX Driver is preset as a default driver 3 Respectively check another driver Note The driver used for the connection from the DeviceNet Slave DTM to the DeviceNet Slave device must be supported by the device and must be available for the device e Use the cifX Device Driver if the DeviceNet Slave DTM is installed on the same PC as the DeviceNet Slave device e Use the netX Driver to establish a USB Serial RS232 or TCP IP connection from the DeviceNet Slave DTM to the DeviceNet Slave device e The 3SGateway Driver for netX V3 x is used only in relationship with CODESYS The version V3 x refers to the driver version defined by 3S Smart Software Solutions GmbH gt Check the checkbox for the driver in the selection list 4 Respectively check multiple drivers To search for devices on the network you can check multiple drivers simultaneously Driver BEE Driver CIFX Device Driver 1 101 1 9801 358BEC 5B 0E92 4C 0E B449 54F62AE7AAFA O 35Gateway Driver for netX V3 x 0 9 12 787CD3A9 4CF6 4259 8E4D 109B5A6BEA9 1 netX D
123. t is Reset or Deleted e Auto reset The connection remains in the established state and immediately restarts the Inactivity Watchdog timer e Auto delete The connection class automatically deletes the connection if it experiences an Inactivity Watchdog timeout DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOC0910030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Configuration 58 113 4 4 1 3 Cyclic Connection If the Cyclic Connection type was activated the elements of this connection type are editable Otherwise this dialog is disabled i Consumption Size o Bytes Connection Path User defined hal Path description User defined gt Production Connection Path User defined Path description User defined Figure 34 Cyclic Connection Consumption and Production At this transmission type a data production takes place automatically if the Transmission Trigger Timer has expired as single value of the Expected Packet Rate Timing Expected Packet Rate 200 ms Watchdog Timeout Action Timeo O Figure 35 Cyclic Connection Timing 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 to reload its Transmission Trigger and Watchdog Timer In Cyclic connections the fourfold value of the Expected Packet Rate is used to re
124. t of the EDS file In the EDS Viewer window on the left side the line number is displayed for simple overview the further entries show the EDS file in text format Parameter Meaning O o O File directory path and the file name of the displayed EDS file Find what Search feature to search for text contents within the text of the EDS file Match whole word Search option Table 24 Device Description EDS Viewer DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOC0910030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Online Functions 66 113 6 Online Functions 6 1 Connecting Disconnecting Device gt Note Several DeviceNet Slave DTM functions e g Diagnosis or the configuration download in the FDT Framework require an online connection from the DeviceNet Slave DTM to the DeviceNet Slave device Connecting Device The following steps are needed to establish a connection from the DeviceNet Slave DTM to a DeviceNet Slave device Under Settings in the Driver pane 1 Select one or several drivers 2 Configure the driver if necessary Under Settings in the Device Assignment pane 3 Scan for the devices with or without firmware 4 Select the devices with or without firmware and apply the selection Under Settings in the Firmware Download pane if not yet a firmware was loaded to the device 5 Select and download the firmware Under Settings
125. tended Diagnosis gt CAN_DL gt AP Commands Counter Extended Diagnosis gt CAN_DL gt CAN Driver Status Packet Monitor send gt Packet Header and Send Data Packet Header and Receive Data Packet Description GET DPM lO INFO REQUEST Example Reading data via Get DPM IO Info Send gt Packet header Example Read data via Get DPM IO Info Send gt Send Data Packet Description GET DPM lO INFO CONFIRMATION Example Reading data via Get DPM IO Info Receive gt Packet header Example Reading data via Get DPM IO Info Receive gt Receive data IO Monitor 11 4 List of Tables Table 1 Descriptions Dialog Panes Table 2 General Device Information Table 3 Overview Dialog Panes Table 4 OK Cancel Apply and Help Table 5 Selecting inserting deleting Table Line Table 6 Status Bar Icons 1 Table 7 Getting started Configuration Steps Slave DTM at the Root Line Stand Alone Slave Table 8 Getting started Configuration Steps Slave DTM at the Master busline Table 9 Descriptions of the Dialog Panes Settings Table 10 Table 11 Table 12 Table 13 Table 14 Table 15 Table 16 Table 17 Table 18 Table 19 Table 20 Table 21 Table 22 Table 23 Table 24 Table 25 Table 26 Table 27 Driver Selection List Parameters Parameters netX Driver gt USB RS232 Connection Parameters netX Driver gt TCP Connection Parameters of the Device Assignment Parameter Firmware Downlo
126. tion file e Installed FDT DTM V 1 2 compliant frame application e Installed DeviceNet Master DTM If Slave DTM is dropped to the Master busline e Loaded DTM in the Device Catalog of the FTD Framework Note If the DeviceNet Slave DTM and the DeviceNet Slave device are installed on the same PC the cifX Device Driver must be installed on that PC as you can connect the DTM to the device For more information to the hardware installation please refer to the corresponding User Manual of your device DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOC0910030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Introduction 13 113 1 4 Dialog Structure of the DeviceNet Slave DTM The graphical user interface of the DTM is composed of different areas and elements listed hereafter 1 A header area containing the General Device Information The Navigation Area area on the left side The Dialog Pane main area on the right side OK Cancel Apply Help ot a EN The Status Line containing information e g the online state of the DTM General Device Information Navi gation Bros Dialog Pane OK Cancel Apply Help Status Line Figure 1 Dialog Structure of the DeviceNet Slave DTM DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOCO910030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009
127. type combination Poll Connection Consumption and Production Poll Connection Timing Change of State Connection Consumption and Production Change of State Connection Timing Cyclic Connection Consumption and Production Cyclic Connection Timing Bit Strobe Connection Consumption and Production Bit Strobe Connection Timing Parameter Configuration DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOCO910030I08EN Revision 8 English 2013 09 Released Public 92 53 53 53 54 54 56 56 58 58 59 59 61 Hilscher 2009 2013 Appendix Figure 39 Figure 40 Figure 41 Figure 42 Figure 43 Figure 44 Figure 45 Figure 46 Figure 47 Figure 48 Figure 49 Figure 50 Figure 51 Figure 52 Figure 53 Figure 94 Figure 55 Figure 56 Figure 57 Figure 98 Figure 99 Figure 60 Figure 61 Configuration gt Device Settings Device Settings gt Start of Bus Communication Device Settings gt Application Monitoring General Diagnosis Firmware Diagnosis The name of the Firmware is displayed Extended Diagnosis gt Folder Name gt Task Information Example Display Extended Diagnosis gt Folder Name gt IniBatch Status Example Display Extended Diagnosis gt DNS_FAL gt DNS Common Status Extended Diagnosis gt DNS_FAL gt AP Commands Counter Extended Diagnosis gt DNS_FAL gt CAN Command Counter Extended Diagnosis gt DNS_FAL gt Timer Counter Ex
128. umber of output data in the poll command to the device The device receives consumes the output data If it has input data configured for this poll connection it reacts by sending producing back the number of input data 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 device Slave first and compares this values with the values configured in Master If different values are detected the connection cannot be established A poll command can be sent from the Master to a device The device has to respond if it has received the poll command of the Master even if it has no input data Else 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 Timing Production Inhibit Time 400 ms Expected Packet Rate gt 00 ms Watchdog Timeout Action Timeout a Figure 31 Poll Connection Timing DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOC0910030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Configuration 55 113 The Production Inhibit Time one for each connection configures the minimum delay ti
129. valid DRV_E_USR_FILENAME_INVALID USER Invalid filename DRV_E FW FILE OPEN FAILED USER Firmware file could not be opened DRV_E FW_FILE SIZE ZERO 0x8004C06F USER Not enough memory to load firmware file DRV_E FW_FILE_NO MEMORY 0x8004C070 USER Not enough memory to load firmware file DRV_E FW FILE READ FAILED USER Firmware file read failed DRV E FW_ INVALID FILETYPE USER Firmware file type invalid DRV E FW FILENAME INVALID USER Firmware file name not valid DRV_E FW DOWNLOAD ERROR USER Firmware file download error DRV_E_FW_FILENAME_NOT FOUND 0x8004C075 USER Firmware file not found in the internal table DRV_E FW_BOOTLOADER_ACTIVE 0x8004C076 USER Firmware file BOOTLOADER active DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOCO910030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Error Codes 99 113 cifX Driver Specific ODM Error Codes DRV_E FW_NO FILE_PATH 0x8004C077 USER Firmware file no file path DRV_E CF FILE OPEN FAILED 0x8004C078 USER Configuration file could not be opend DRV_E CF FILE SIZE ZERO 0x8004C079 USER Configuration file size zero DRV_E CF FILE NO MEMORY 0x8004C07A USER Not enough memory to load configuration file DRV_E CF_FILE NO SEGMENT 0x8004C07F USER No flash segment in the configuration file DRV_E CF_DIFFERS_ FROM DBM 0x8004C080 USER Configuration file differs from database DRV_E DBM SIZE ZERO 0x8004C083 USER Database size zero DRV_ E
130. ve Devices DOC0910030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Informational Informational Error Codes 106 113 ODM Error Codes DBM V4 Error Code Definition Description CDBM_ERROR_FROM_VAR_ CHANGE_TYPE OXC004C848 Function VariantChangeType return an error when trying to convert the Parameter CDBM_E MINERROR 0XC004C849 Error while comparing the Value with the lower range CDBM_E MAXERROR 0XC004C84A Error while comparing the Value with the upper range CDBM_E RANGE ERROR OXC004C84B Value out of Range CDBM_E TABLE_TYPE1 0XC004C84C Table type 1 doesn t have a unique record length over all records CDBM_E TABLE _TYPE3_ ADDREC 0XC004C84D Table type 3 doesn t allow to insert more than one Record CDBM_E TABTYPE1 0XC004C84E It s not allowed to insert more Records than structure definitions in Table Type 1 CDBM_E TOGGLE NOT FOUND 0XC004C84F Could not find the string for this value in the list of valid toggle strings CDBM_E TOGGLE VALUE IS EMPTY STRING 0XC004C850 The toggle string for this value is empty CDBM_VARIANT2BYTEARRAY_ ERROR 0XC004C851 Error during conversion of Variant to byte array CDBM_E SET ELEM PROP_ DEPENDENCY OXC004C852 The Toggle Type needs also the additional string and the additional number entries in the Method CDBM _E TABTYPE1 REC _ OXC004C853 When reading the records of Table type 1 DOESNT CORRESPOND_ WITH ELEMENT elementwise the record number mu
131. viceNet Slave DTM to the Master busline of the DeviceNet Master DTM if within the network project the Slave device and the Master device are used i e if you intend to configure the Slave device and the Master device 2 Channel Devices must be assigned to the DTM and each must be configured individually DTM for Hilscher DeviceNet Slave Devices Configuration of Hilscher Slave Devices DOCO910030I08EN Revision 8 English 2013 09 Released Public Hilscher 2009 2013 Introduction 12 113 1 3 1 Requirements System Requirements e PC with 1 GHz processor or higher e Windows XP SP3 Windows Vista 32 bit SP2 Windows 7 32 bit SP1 Windows 7 64 bit SP1 Windows 8 32 bit or Windows 8 64 bit e Administrator privilege required for installation e Internet Explorer 5 5 or higher e RAM min 512 MByte recommended 1024 MByte e Graphic resolution min 1024 x 768 pixel e Keyboard and Mouse Note If the project file is saved and opened again or if it is used on another PC the system requirements must match Particularly the DTM must be installed on the used PC Restriction Touch screen is not supported Requirements DeviceNet Slave DTM To configure the DeviceNet Slave device with the DeviceNet Slave DIM the following requirements have to be accomplished e Completed hardware installation of a netX based DTM compatible DeviceNet Slave device inclusive loaded firmware and loaded configura
132. y be trademarked or patented Any form of further use requires the explicit consent of the respective rights owner 1 2 2 Important Notes The user manual accompanying texts and the documentation were created for the use of the products by qualified experts however errors cannot be ruled out For this reason no guarantee can be made and neither juristic responsibility for erroneous information nor any liability can be assumed Descriptions accompanying texts and documentation included in the user manual do not present a guarantee nor any information about proper use as stipulated in the contract or a warranted feature It cannot be ruled out that the user manual the accompanying texts and the documentation do not correspond exactly to the described features standards or other data of the delivered product No warranty or guarantee regarding the correctness or accuracy of the information is assumed We reserve the right to change our products and their specification as well as related user manuals accompanying texts and documentation at all times and without advance notice without obligation to report the change Changes will be included in future manuals and do not constitute any obligations There is no entitlement to revisions of delivered documents The manual delivered with the product applies Hilscher Gesellschaft f r Systemautomation mbH is not liable under any circumstances for direct indirect incidental or follow on damage or

Download Pdf Manuals

Related Search

Related Contents

VPL-HW40ES  Scala Rider FM Manual  DFP-110 User Manual  Cisco Systems Unified MeetingPlace Web Conferencing Installation and Upgrade Guide  

Copyright © All rights reserved. Failed to retrieve file