SERCOS III Master Devices

Operating Instruction Manual

DTM for SERCOS III Master Devices

Configure Hilscher Master Devices Beta Version

Language: English (EN)

www.hilscher.com SERCOS III Master DTM Table of Contents • 2

Table of Contents

1 INTRODUCTION...... 5 1.1 About this Manual ...... 5 1.1.1 Online Help...... 6 1.1.2 List of Revisions ...... 6 1.1.3 Conventions in this Manual ...... 7 1.2 Legal Notes...... 8 1.2.1 Copyright ...... 8 1.2.2 Important Notes...... 8 1.2.3 Exclusion of Liability ...... 9 1.2.4 Warranty ...... 9 1.2.5 Export Regulations ...... 10 1.2.6 Registered Trademarks...... 10 1.3 About SERCOS III Master DTM ...... 11 1.3.1 Requirements ...... 11 1.4 Dialog Structure of the SERCOS III Master DTM ...... 12 1.4.1 General Device Information...... 13 1.4.2 Navigation Area...... 13 1.4.3 Dialog Panes ...... 14 1.4.4 Controls and Dialog Buttons...... 15 1.4.5 Status Bar...... 16

2 GETTING STARTED...... 18 2.1 Configuration Steps ...... 18 2.1.1 Setting Driver and Selecting Device...... 21 2.1.2 Configuring Device Parameters ...... 22

3 SETTINGS ...... 23 3.1 Overview Settings...... 23 3.2 Driver ...... 24 3.2.1 Selecting the Driver ...... 24 3.2.2 Configuring the Driver ...... 25 3.2.3 cifX Device Driver...... 26 3.3 Device Assignment ...... 27 3.3.1 Scanning for Devices ...... 28 3.3.2 Selecting the Device (with or without firmware) ...... 31 3.3.3 Selecting the Device once more (with Firmware)...... 32 3.4 Firmware Download...... 34

4 CONFIGURATION ...... 39 4.1 Overview Configuration ...... 39 4.2 General Settings ...... 40 4.3 Master Settings...... 41 Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Table of Contents • 3 4.3.1 Start of Bus Communication...... 42 4.3.2 Application Monitoring ...... 42 4.3.3 Process Image Storage Format ...... 43 4.3.4 Module Alignment...... 43 4.3.5 Process Data Handshake...... 44 4.4 Slave Table...... 45 4.5 Process Data ...... 47 4.6 Address Table...... 48 4.6.1 Auto Addressing, Display Mode, CSV Export ...... 49

5 DIAGNOSIS ...... 50 5.1 Overview Diagnosis ...... 50 5.2 Firmware Diagnosis ...... 51 5.3 General Diagnosis ...... 52 5.4 Master Diagnosis ...... 55

6 ADDITIONAL TOOLS...... 56 6.1 Overview Additional Tools ...... 56 6.2 Packet Monitor...... 57 6.2.1 Packet Header...... 58 6.2.2 Sending Packet ...... 59 6.2.3 Receiving Packet...... 60 6.3 IO Monitor ...... 61

7 ONLINE FUNCTIONS ...... 62 7.1 Connecting/Disconnecting Device ...... 62 7.2 Network Scan ...... 64 7.2.1 Display of the Network Scan function...... 65 7.3 Download Configuration ...... 66 7.4 Start /Stop Communication...... 67 7.5 License ...... 68 7.5.1 Which licenses are present in the Device? ...... 69 7.5.2 How to order a license...... 70 7.5.3 How to get the License and transfer it to the Device...... 75

8 ERROR NUMBERS ...... 76 8.1 Error Code Definition ...... 76 8.2 Overview Error Numbers ...... 77 8.3 General Hardware Error Codes ...... 78 8.3.1 RCX Errors - MID_SYS Task Error Codes...... 78 8.3.2 RCX Errors - Common Status Codes...... 80 8.3.3 RCX Errors - Status & Error Codes...... 81 8.4 SERCOS III Master Status/Error Codes ...... 82 8.4.1 Status/Error Codes of SERCOS III Master CP Task...... 82

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Table of Contents • 4 8.4.2 Status/Error Codes of SERCOS III Master SVC Task ...... 86 8.4.3 Status/Error Codes of SERCOS III Master AP Task...... 87 8.5 ODM Error Codes ...... 93 8.5.1 General ODM Error Codes...... 93 8.5.2 General ODM Driver Error Codes ...... 94 8.5.3 ODM cifX Driver Specific Errors...... 95 8.6 Error Codes cifX Device Driver...... 99 8.7 ODM DBM V4 Error Codes...... 101

9 GLOSSARY...... 107

10 LISTS ...... 108 10.1 List of Figures ...... 108 10.2 List of Tables ...... 109

11 APPENDIX ...... 110 11.1 User Rights ...... 110 11.1.1 Settings...... 110 11.1.2 Configuration ...... 110 11.2 References ...... 111 11.3 Contacts...... 112

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Introduction • 5 1 Introduction 1.1 About this Manual This manual provides information on how to set and configure the device parameters of a SERCOS III Master using the SERCOS III Master DTM, and what can be read from the diagnosis panes.

Dialog Panes The table below gives an overview for the individual dialog panes descriptions:

Section Subsection Page Settings Overview Settings 23 Driver 24 Device Assignment 27 Firmware Download 34 Configuration Overview Configuration 39 General Settings 40 Master Settings 41 Slave Table 45 Process Data 47 Address Table 48 Diagnosis Overview Diagnosis 50 Firmware Diagnosis 51 General Diagnosis 52 Master Diagnosis 55 Additional Tools Overview Additional Tools 56 Packet Monitor 57 IO Monitor 61 Table 1: Descriptions Dialog Panes

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Introduction • 6 1.1.1 Online Help The SERCOS III Master DTM contains an integrated online help facility. ¾ To open the online help, click on the Help button or press the F1 key.

1.1.2 List of Revisions

Index Date Version Component Chapter Revision 1 2009-03-31 0.900.x.x SIIIMasterDTM.dll all created 0.900.x.x SIIIMasterGUI.ocx

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Introduction • 7 1.1.3 Conventions in this Manual Operation instructions, a result of an operation step or notes are marked as follows:

Operation Instructions: ¾

1. 2.

Results: °

Notes:

Note:

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Introduction • 8 1.2 Legal Notes

1.2.1 Copyright © 2008-2009 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 may 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 loss of earnings resulting from the use of the information contained in this publication.

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Introduction • 9 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: • for military purposes or in weapon systems; • for the design, construction, maintenance or operation of nuclear facilities; • in air traffic control systems, air traffic or air traffic communication systems; • in life support systems; • 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 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. It 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.

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Introduction • 10 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 software 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® 2000/Windows® XP are registered trademarks of Microsoft Corporation. SERCOS interface® is a trademark of SERCOS International e. V., Suessen, Germany. All other mentioned trademarks are property of their respective legal owners.

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Introduction • 11 1.3 About SERCOS III Master DTM You can use the SERCOS III Master DTM to configure the SERCOS III Master device within an FDT Framework. 1.3.1 Requirements

System Requirements • Windows® 2000/ Windows® XP • CD ROM drive • Graphic resolution: min. 1024 x 768 pixel • Keyboard and Mouse

Requirements SERCOS III Master DTM To configure a SERCOS III Master device with a DTM the following requirements have to be accomplished: • Completed hardware installation of a DTM-compatible SERCOS III Master device, inclusive loaded firmware and loaded cifX configuration file • Installed FDT/DTM V 1.2 compliant frame application • Loaded DTM in the Device Catalog of the FTD Framework

For more information to the hardware installation, please refer to the user manual CIFX Cards Real-Time-Ethernet, Installation, Operation and Hardware Description on the product CD of your cifX card.

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Introduction • 12 1.4 Dialog Structure of the SERCOS III Master 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, 2. The Navigation Area (area on the left side), 3. The Dialog Pane (main area on the right side), 4. The general buttons OK, Cancel, Apply, Help, 5. The Status Line containing information e. g. the online-state of the DTM.

General Device Information

Navi gation Dialog Pane Area

OK Cancel Apply Help

Status Line

Figure 1: Dialog Structure of SERCOS III Master DTM

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Introduction • 13 1.4.1 General Device Information

Parameter Meaning IO Device Name of the device Vendor 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 at the left side of the dialog provides a tree structure to navigate through the panes of the DTM.

Navigation Area

Settings Ä Driver Device Assignment Firmware Download Configuration

Figure 2: Navigation Area

¾ To access a DTM pane select the respective item of the navigation tree structure.

The Navigation Area can be hidden or it can be displayed again.

Control Meaning

Window button to hide the navigation area, (at the right side of the navigation title bar). Show navigation area button to open the navigation area, (at the lower left corner of the dialog pane). Table 3: Hide / display Navigation

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Introduction • 14 1.4.3 Dialog Panes At the dialog pane the Settings, Configuration, Diagnostis/Extended Diagnosis or the Additional Tools panes are opened via the corresponding folder in the navigation area.

Settings Driver On the pane Driver you can select a driver from the driver list. For further information, refer to section Driver on page 24. Device Assignment On the pane Device Assignment you select the device and assign the device to the driver. For further information, refer to section Device Assignment on page 27. 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 34. Configuration General Settings The General Settings pane displays general SERCOS II Master information. For more information, refer to section General Settings on page 40. Slave Table The Slave Table pane informs about the slaves connected to the master and their settings. For more information, refer to section Slave Table on page 45. Process Data The Process Data serves for the SERCOS III Master DTM as an external process data interface. For further information, refer to section Process Data on page 47. Address Table The Address Table shows a list of all dpram address used in the process data image. For further information, refer to section Address Table on page 48. Diagnosis Diagnosis At the Diagnosis panes diagnosis information can be read. For further information, refer to section Overview Diagnosis on page 50. Additional Tools Packet Monitor/ Under Additional Tools the Packet Monitor and the IO Monitor IO Monitor are provided for test and diagnosis purposes. For further information, refer to section Packet Monitor on page 57 or section IO Monitor on page 61. Table 4: Overview Dialog Panes

Note: Accessing the Diagnosis panes of the SERCOS III Master DTM requires an online connection from the SERCOS III Master DTM to the SERCOS III Master device.

For further information, refer to section Connecting/Disconnecting Device on page 62.

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Introduction • 15 1.4.4 Controls and Dialog Buttons In this section, you will find general information on controls and buttons. 1.4.4.1 General Buttons The table below explains the general buttons in the DTM user interface.

Button Meaning OK To confirm your latest settings, click on the OK button. All changed values will be applied on the frame application database. The dialog then closes. Cancel To cancel your latest changes, click on the Cancel button. 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. Apply To confirm your latest settings, click on the Apply button. All changed values will be applied on the frame application database. The dialog remains opened. Help To open the DTM online help, click on the Help button. Table 5: General Buttons

1.4.4.2 Table Line Buttons ¾ To select, create or delete a line in a table use the buttons shown in the table below.

Button Meaning To select the first line of a table use the button First Line.

To select the previous line of a table use the button Previous Line.

To select the next line of a table use the button Next Line.

To select the last line of a table use the button Last Line.

The button Create a new Line inserts new lines into the table.

The button Delete selected Line deletes the selected line from the table.

Table 6: Table Line – Buttons

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Introduction • 16 1.4.5 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.

Figure 3: Status Bar – Status Fields 1 to 6

Status Icon / Meaning Field 1 DTM Connection States Connecting: Icon going closed = Device is going online

Connected: Icon closed = Device is online

Disconnecting: Icon going opened = Device is going offline

Disconnected: Icon opened = Device is offline

Disconnected – disturbed: Icon with lightening = Device communication disturbed 2 Data Source States Data set: The displayed data are read out from the instance data set (database). Data set locked: The displayed data are read out from the instance data set (database). Database is locked with password. Device: The displayed data are read out from the device.

Device locked: The displayed data are read out from the device. Device is locked with password. 3 States of the instance Date Set - All data loaded Valid Modified: Parameter is changed (not equal to data source).

Invalid Modified: Invalid value (e. g. not plausible).

- Initial data set: Parameter value is equal to data source value (data base or field device). 4 Changes directly made on the Device Changes have only an impact on the device and not on the instance data set. Instance data set and the device may not be consistent any more. Load/configure diagnosis parameters: Diagnosis is activated.

5 Direct Mode active Direct Mode active

More see next page

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Introduction • 17

Status Icon / Meaning Field

6 Device Diagnosis Status Device Failure: Incorrect communication due to malfunction in the field device or its peripherals. Maintenance required: Although the communication is error-free, the wear reserve is nearly exhausted or a function will soon be restricted due to operational conditions. Off-specification: The device is operating outside its specified range or internal diagnosis indicates deviations from measured or set values due to internal problems in the device or process characteristics. Device OK: Communication is error-free.

Functional Check: Communication temporarily incorrect (e.g. frozen) due to on-going work on the device. Diagnosis deactivated

Table 7: Status Bar Icons [1]

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Getting Started • 18 2 Getting Started 2.1 Configuration Steps The following table describes the steps to configure a device with SERCOS III Master DTM as it is typical for many cases. At this time it is assumed that the hardware installation was done.

# Step Short Description For detailed information see Page section 1 Add SERCOS III Slave Add the Slave in the Device Catalog by importing - in the Device Catalog the device description file to the Device Catalog. (See User Manual netDevice Depending of the FDT Container. and netProject) For netDevice: - Network > Import Device Descriptions. 2 Load device catalog Depending of the FDT Container: - For netDevice: (See User Manual netDevice - select Network > Device Catalog, and netProject) - select button Reload Catalog. 3 Create new project / Depending of the frame application. - Open existing project For the configuration software: (See User Manual of the - select File > New or File > Open. Frame Application) 4 Insert Master or Slave Depending of the FDT Container: - into configuration For netDevice: (See User Manual netDevice - in the Device Catalog click to the Master, and netProject) - and insert the device via drag and drop to the 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. 5 Open the Master DTM Open the Master DTM configuration dialog. - - configuration dialog - Double click to the device device icon of the Master. - The Master DTM configuration dialog is displayed. 6 Select driver In the Master DTM configuration dialog: Setting Driver and Selecting 21 - select Settings > Driver, Device - select a driver, Driver 24 - therefore check the appropriate checkbox. - if necessary, configure the driver settings. 7 Assign Master device Assign the device to this driver. Selecting the Device (with or 31 (with or without In the Master DTM configuration dialog: without firmware) firmware) - select Settings > Device Assignment, - select a Master device (with or without firmware), - therefore check the appropriate checkbox, - select the button Apply. 8 Select and download If not yet a firmware was loaded to the device. Firmware Download 34 firmware In the Master DTM configuration dialog: - select Settings > Firmware Download, - select the button Browse.., - select a firmware file, - select the button Open, - select the buttons Download and Yes. More see next page

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Getting Started • 19

# Step Short Description For detailed information see Page section 9 Assign Master device In the Master DTM configuration dialog: Selecting the Device once 32 once more (with - select Settings > Device Assignment, more (with Firmware) firmware) - select the button Scan, - select the Master device (with loaded firmware), - therefore check the appropriate checkbox, - select the button Apply, - close the Master DTM configuration dialog via the button OK. 10 Configure Slave device Configure the Slave device. - - Double click to the device device icon of the (See User Manual Generic Slave. Slave DTM for SERCOS III - The Slave DTM configuration dialog is displayed. Slave Devices) In the Slave DTM configuration dialog: - select Configuration >General, - set the Watchdog control and Interval, - select Configuration >Electronic Label, - check device-specific information, - select Configuration >FSP IO, - set the module Parameters, - Select Configuration >FSP Drives, - perform detailed parameterization, - close the Slave DTM configuration dialog via the button OK. 11 Configure Master device Configure the Master device. Configuring Device 22 - Double click to the device icon of the Parameters Master. - The Master DTM configuration dialog is displayed. In the Master DTM configuration dialog: - select Configuration > General General Settings 39 Settings, - set the general parameters, - select Configuration > Master Settings, Master Settings 41 - set the master settings, - select Configuration > Slave Table, Slave Table 45 - configure slave-specific settings, - select Configuration > Process data, Process Data 47 - set the process data, - select Configuration > Address table, Address Table 48 - set the device address, if necessary, - close the Master DTM configuration dialog via the button OK. 12 Save project Depending of the frame application. - For the configuration software: (See User Manual of the - select File > Save. Frame Application) 13 Connect Master device Depending of the FDT Container. Connecting/Disconnecting 62 For netDevice: Device - right click to the device device icon of the Master, - select context menu entry Device > Connect. 14 Download Configuration Depending of the FDT Container. Download Configuration 66 For netDevice: - right click to the device device icon of the Master, - select context menu entry Device > Download. More see next page

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Getting Started • 20

# Step Short Description For detailed information see Page section 15 Diagnosis Depending of the FDT Container. Overview Diagnosis 50 For netDevice: - right click to the device device icon of the Master, - select context menu entry Diagnosis. - The Master DTM diagnosis dialog is displayed. - Continue with further device diagnosis, - close the Master DTM diagnosis dialog via the button OK. 16 IO Monitor Depending of the FDT Container: IO Monitor 61 For netDevice: - right click to the device device icon of the Master, - select context menu entry Diagnosis, - select Additional Tools > IO Monitor. - Check the input or output data. 17 Disconnect Depending of the FDT Container. Connecting/Disconnecting 62 For netDevice: Device - right click to the device device icon of the Master, - select Device > Disconnect. Table 8: Getting Started - Configuration Steps

Note: Alternatively you can scan the network structure using the context menu entry Additional Functions > Network Scan. Then you can download the configuration to the Master device. Via the context menu entry Additional Functions > Live List you can display the devices present at the bus.

For more information refer to section Network Scan on page 64 or to section Display of the Network Scan function on page 65.

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Getting Started • 21 2.1.1 Setting Driver and Selecting Device The following steps are needed to establish a connection from the SERCOS III Master DTM to the SERCOS III Master device: Under Settings in the Driver pane: 1. Select one or several driver/s. 2. Configure the driver, if necessary. Under Settings in the Device Assignment pane: 3. Scan for the device/s (with or without firmware). 4. Select the device (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 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.

An overview of the descriptions for these steps you find in the section Overview Settings on page 23.

8. In the DTM interface dialog select the OK button, to apply the selection and to close the DTM interface dialog. 9. Put a right-click on the SERCOS III Master device icon. 10. Select the Connect command from the context menu. ° The SERCOS III Master device now is connected to the SERCOS III Master DTM via an online connection. In the network view the device description at the device device icon of the Master is displayed with a green colored background.

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Getting Started • 22 2.1.2 Configuring Device Parameters The following steps are required to configure the parameters of the SERCOS III Master device using the SERCOS III Master DTM: 1. Set the general settings: ¾ Select Configuration > General Settings in the navigation area. 2. Set the master settings: ¾ Select Configuration > Master Settings in the navigation area. 3. Set the the entries of the slave table: ¾ Select Configuration > Slave Table in the navigation area. 4. Set the process data: ¾ Select Configuration > Process Data in the navigation area. 5. Check the addresses of the devices: ¾ Select Configuration > Address Table in the navigation area.

For more information refer to section Overview Configuration on page 39, to section General Settings on page 40, to section Master Settings on page 41, to section Slave Table on page 45, to section Process Data on page 47 and to section Address Table on page 48.

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Settings • 23 3 Settings 3.1 Overview Settings

Settings Dialog Panes The table below gives an overview for the individual Settings dialog panes descriptions:

Section Subsection Page Driver 24 Selecting the Driver 24 Configuring the Driver 25 cifX Device Driver 26 Device Assignment 27 Scanning for Devices 28 Scanning for all Devices or for suitable only 30 Selecting the Device (with or without firmware) 31 Selecting the Device once more (with Firmware) 32 Firmware Download 34 Table 9: Descriptions Settings

Figure 4: Navigation Area - Settings

Note: To edit the Settings dialog panes you need User Rights for “Maintenance”.

Notice the descriptions in the section Configuration Steps on page 18.

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Settings • 24 3.2 Driver The Driver dialog pane displays the driver/s to be used for a SERCOS III Master DTM to device communication connection.

Figure 5: Driver Selection List

Parameter Meaning Driver Name of the driver Version Version of the driver ID ID of the driver (driver identification) Table 10: Driver Selection List Parameters

3.2.1 Selecting the Driver To establish a connection you need to select a driver first.

Note: Not all the drivers displayed necessarily support the device. The used driver must be supported by the device or must be available for the device.

To select the driver/s to be used: 1. Select Settings > Driver in the navigation area. ° The available drivers are listed on the Driver dialog pane.

Figure 6: Driver Selection List - recognized or installed Drivers

2. Check the checkbox for the driver/s in the selection list.

Figure 7: Driver Selection List - Driver/s selected

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Settings • 25 3.2.2 Configuring the Driver All drivers for which you can access to an individual driver dialog pane are displayed in the navigation area under the Driver entry. In the driver dialog panes you can configure the driver settings. For some drivers no individual driver dialog panes exist, since no driver settings are required, e. g. for the cifX Device Driver.

Note: At the driver dialog panes under Settings > Driver the driver settings can be configured.

Figure 8: Navigation Area – Settings

To configure a driver: 3. Select Settings > Driver > [Name of the assigned driver]. ° The corresponding driver dialog pane is displayed. 4. Configure the driver settings. ¾ To get detailed information how to configure the single drivers, please refer to the corresponding description of the driver.

You can access to the single descriptions of the drivers as online help via the DTM user interface (F1 key).

To access to the online help with the descriptions of the drivers: ¾ Select Settings > Driver > [Name of the assigned driver]. ¾ Press the F1 key.

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Settings • 26 3.2.3 cifX Device Driver In the SERCOS III Master 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 is used, if the SERCOS III Master DTM is installed in the same PC as the SERCOS III Master device.

Note: To establish a connection from a DTM to a NETX Master device via the cifX Device Driver, the cifX Device Driver must be installed and the driver must have access to the NETX Master device.

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Settings • 27 3.3 Device Assignment

Note: To establish a connection from the SERCOS III Master DTM to a SERCOS III Master device, you first must assign a SERCOS III Master device to the SERCOS III Master DTM. Therefore you must assign the SERCOS III Master device to the selected driver.

Therefore in the Device Assignment dialog pane you scan for the SERCOS III Master 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/s (with or without firmware) and select it/them, 2. then you download a firmware to the device and 3. subsequently you scan for the device/s (with firmware) once more and select it/them again.

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Settings • 28 3.3.1 Scanning for Devices 1. Select Settings > Device Assignment in the navigation area. ° The dialog pane Device Assignment is displayed.

Figure 9: Device Assignment - detected Devices (* The name of the device class is displayed.) – Example for a device without firmware

2. Select the list box entry suitable only. 3. Select the Scan button, to start the scanning process. ° Under Device Selection all devices are displayed, which can be connected to the SERCOS III Master 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[0toN]_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 …\cifX[0toN]_Ch[0to3] is displayed.

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Settings • 29

Parameter Meaning Range of Value / Value Device selection Selecting suitable only or all devices. suitable only, all Device Device class of the SERCOS III Master Devices. Hardware Port Shows, which hardware is assigned to which communication 0/1/2/3 interface. Serial number Serial number of the device Driver Name of the driver Channel Protocol 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: SERCOS III Master (Example for SERCOS III Master Firmware) Access path Depending on the used driver in the column Access path Depending on the (under Device different data to the device are displayed. device and on the selection last For the cifX Device Driver the following data are displayed: driver: column on the a.) For devices without firmware: …\cifX[0toN]_SYS, board or channel right) b.) For devices with firmware: …\cifX[0toN]_Ch[0to3]. number, IP address or COM interface cifX[0toN] = Board number 0 to N Ch[0to3] = Channel number 0 to 3 Access path If under Device selection the check box for a device is driver identification (at the lower side checked, under Access path (at the lower side of the dialog (ID) of the dialog pane) the driver identification or depending on the used driver depending on the pane) additional data to the device. device and on the For the cifX Device Driver the following data are displayed: driver: a.) For devices without firmware: …\cifX[0toN]_SYS, board or channel b.) For devices with firmware: …\cifX[0toN]_Ch[0to3]. number, IP address cifX[0toN] = Board number 0 to N or COM interface Ch[0to3] = Channel number 0 to 3 Table 11: Parameters of the Device Assignment

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Settings • 30

3.3.1.1 Scanning for all Devices or for suitable only

all 4. In the Device Assignment pane select the list box entry all. 5. Select the Scan button, to start the scanning process.

Figure 10: Device Assignment - detected Devices (* The name of the device class is displayed.) Example for Devices without Firmware

° Under Device Selection 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. In the Device Assignment pane select the list box entry suitable only. 2. Select the Scan button, to start the scanning process. ° Under Device Selection all devices are displayed, which can be connected to the SERCOS III Master DTM 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.

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Settings • 31 3.3.2 Selecting the Device (with or without firmware)

Note: A connection with the SERCOS III Master DTM can only be established with one SERCOS III Master device.

To select the physical SERCOS III Master device (with or without firmware): 1. In the Device Assignment pane in the selection list Device selection check the check box for the device.

Figure 11: 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 displayed. 2. Select the Apply button, to apply the selection.

Note: Before an online connection from the SERCOS III Master DTM to the SERCOS III Master 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 Firmware Download on page 34 or to section Selecting the Device once more (with Firmware) on page 32.

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Settings • 32 3.3.3 Selecting the Device once more (with Firmware) To select the SERCOS III Master device (with firmware) once more, proceed as described hereafter:

all 1. In the pane Device Assignment select the list box entry all. 2. Select the button Scan. ° Under Device Selection all devices are displayed, which are attainable in the network and which can be connected to a DTM via the preselected drivers. 3. In the Device Assignment pane in the selection list Device selection check the check box for the device.

Figure 12: Device Assignment - Selecting the Device (* The name of the device class is displayed.) – Example for Devices with and without Firmware / one Device is selected

Note: After the firmware download has been completed, for the devices which have been detected via the cifX Device Driver the following data are displayed: - In the column Channel Protocol: the data for the firmware for the used channel - In the column Access path or under Access path (below in the dialog pane): the data: …\cifX[0toN]_Ch[0to3]. cifX[0toN] = board number 0 to N Ch[0to3] = channel number 0 to 3

4. Select the Apply button, to apply the selection. 5. Or select the OK button, 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).

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Settings • 33

Or:

suitable only 1. In the pane Device Assignment select the list box entry suitable only. 2. Select the button Scan. ° Under Device Selection all devices are displayed, which can be connected to the SERCOS III Master DTM via the preselected drivers. 3. In the Device Assignment pane in the selection list Device selection check the check box for the device.

Figure 13: Device Assignment - Selecting the Device (* The name of the device class is displayed.) – Example for a device with firmware / one Device is selected

For further information how to establish an online connection from the SERCOS III Master DTM to the SERCOS III Master device, refer to

section Connecting/Disconnecting Device on page 62.

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Settings • 34 3.4 Firmware Download To load the firmware to the device: 1. In the navigation area select Settings > Firmware Download. ° The dialog Firmware-Download pane is displayed.

Figure 14: Firmware Download

Parameter Meaning Name Name of the Firmware Version Version and Build Version of the Firmware Browse… Button to select the firmware file. Download Button to download the firmware. Table 12: Parameter Firmware Download

2. Select the button Browse. ° The selection window Select Firmware File is displayed.

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Settings • 35

Figure 15: Selection Window Select Firmware File

Parameter Meaning Range of Value / Value Files of Type „All Files (*.*)“, if before in the Device Assignment pane the All Files (*.*), list box entry all has been selected. Firmware Files (*.nxm), „ Firmware Files (*.nxm)“ or Firmware Files (*.nxf), if before in Firmware Files (*.nxf) the Device Assignment pane the list box entry suitable only has been selected. Recent folder Path of the recently opened folder Firmware As soon as the firmware file has been selected, under Name, Version, Build Firmware the name, the version and the build version as well Version, Device Class for as the device class for the selected firmware is displayed. the selected firmware Help Button, to open the online help of the DTM. Table 13: 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.

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Settings • 36

Note: After in the Device Assignment pane the list box entry all/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 p) 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: There is a restricted A validation is made, if the validation, if the firmware file is suitable for the selected firmware is SERCOS III Master DTM. applied for the download. *These settings in the selection window Select Firmware File can also be changed manually.

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. In the selection window select the Open button. ° A validation is made, if the selected firmware file is suitable for the SERCOS III Master DTM. ° In the dialog pane Firmware Download during the validation the button Download is grayed out. ° The selection window is closed. 5. In the dialog pane Firmware Download click to the Download button, 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 is displayed.

Figure 16: Request Select Firmware File - Example

¾ Answer to the request with No.

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Settings • 37

Figure 17: Firmware Download – Download

° The request Do you really want to download the firmware? is displayed.

Figure 18: Firmware-Download – Question)

6. Select the Yes button.

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Settings • 38

° During the download a progress bar is displayed, in the status line a clock / green hook device icon is displayed and the button Download is grayed out.

Figure 19: Clock Symbol and Hook Symbol green

Figure 20: Clock Symbol and Hook Symbol green

¾ If necessary, cancel the download via Cancel.

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Configuration • 39 4 Configuration 4.1 Overview Configuration

Configuration Steps The following steps are required to configure the parameters of the SERCOS III Master device using the SERCOS III Master DTM: 1. Set the general settings. 2. Set the master settings. 3. Check the slave table: 4. Check the process data. 5. Check the address table

Configuration Dialog Panes The table below gives an overview for the Configuration dialog panes descriptions:

Section Page General Settings 40 Master Settings 41 Slave Table 45 Process Data 47 Address Table 48 Table 14: Descriptions of the Dialog Panes Configuration

Figure 21: Navigation Area - Configuration

Take care of the descriptions in the section Configuration Steps on page 18.

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Configuration • 40 4.2 General Settings The General Settings dialog page shows some basic settings such as the current device name, the description of the SERCOS III Master and the communication cycle time. To access the dialog page ‘General Settings’: ¾ Select Configuration > General in the navigation area. ° The dialog page ‘General Settings’ appears.

Figure 22: Configuration > General Settings (*The current device name is displayed.)

The fields contained there have the following meaning:

Parameter Meaning Range of Value / Value Name Network name of the SERCOS III Master station. Must be a 1 - 240 characters DNS compatible name. Description Symbolic Name of the SERCOS III Master DTM. (string) Communication Communication cycle time of SERCOS III network. This 31.25 µs cycle time parameter describes the basic cycle time for communication. 62.5 µs The communication cycle time (tScyc) defines the time intervals 125 µs for the transmission of cyclic data. It is relevant for communication phases CP3 and CP4. It corresponds to IDN S- 250 µs up to 0-1002 as described in the SERCOS III specification. 65000 µs in steps of 250 µs Communication The communication mode decides between bus synchronous or Free run mode free running bus-independent operation. Bus synchronous Target phase The communication phase to be set NRT, CP0, CP1, CP2, CP3, CP4 Table 15: Configuration > General - Settings

¾ Edit the text in the Description field. ¾ Choose the desired communication cycle time of your SERCOS III network.

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Configuration • 41 4.3 Master Settings The Master Settings dialog page shows some more special settings. To access the dialog page ‘Master Settings’: ¾ Select Configuration > Master Settings in the navigation area. ° The dialog page ‘Master Settings’ appears.

Figure 23: Master Settings

The following adjustments can be made here: • Start of bus communication • Application monitoring • Process image storage format • Module Alignment • Process data handshake

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Configuration • 42 4.3.1 Start of Bus Communication

Figure 24: Master Settings > Start of Bus Communication

If Automatically by device is selected, the netX SERCOS III Master device starts with the data exchange on the bus after the initializing 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.3.2 Application Monitoring

Figure 25: Master Settings > 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 0 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. 0 ms Table 16: 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.

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Configuration • 43 4.3.3 Process Image Storage Format

Figure 26: Master Settings > Process Image Storage Format

The Process Image Storage Format determines how the data words are stored in the process image. For the data type Word it is possible to choose Big Endian or Little Endian.

Storage format (word module) Big Endian MSB/LSB = higher/lower = Motorola format = Big Endian Little Endian LSB/MSB = lower/higher = Intel format = Little Endian Table 17: Master Settings Pane Parameters - Process Image Storage Format

Note: The setting options under Process Image Storage Format for client specific variants of the configuration software can differ from the setting options displayed here.

4.3.4 Module Alignment

Figure 27: Master Settings > Module Alignment

The Module Alignment defines the addressing mode of the process data image. The addresses (offsets) of the process data are always interpreted as byte addresses. The Module Alignment then defines the addressing mode, Byte boundaries or 2 Byte boundaries.

Parameter Meaning Byte boundaries The modul address can start at any byte offset. 2 Byte boundaries The modul address can only start at even byte offsets. Table 18: Parameters Master Settings > Module Alignment

Note: The setting options under Module Alignment for client specific variants of the configuration software can differ from the setting options displayed here.

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Configuration • 44 4.3.5 Process Data Handshake

Figure 28: Master Settings > Process Data Handshake

The various types of Process Data Handshakes are used for setting the handshake of the process data for the netX SERCOS III Master device. The selection of the used process data handshake is important for the correct data exchange between the application program and the device. The used handshake of the process data needs to be supported by the used application program. Only the Bus synchronous, host controlled handshake is supported.

Note: The setting options under Process Data Handshake for customer specific variants of the configuration software can differ from the setting options displayed here.

Note: Maybe the choice is restricted to fewer options here.

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Configuration • 45 4.4 Slave Table The Slave Table dialog page shows a table containing some basic information about the slaves administered by the SERCOS III Master such as the current slave device name, its address, vendor and the description of the SERCOS III Slave. To access the dialog page ‘Slave Table’: ¾ Select Configuration > Slave Table in the navigation area. ° The dialog page ‘Slave Table’ appears.

Figure 29: Configuration > General Settings (*The current device name is displayed.)

The fields contained there have the following meaning: • Optional Mark this field when the slave is optional. • Topology Address This field contains the topology address of the specific slave. This field is not editable. • Slave Address This field contains the slave address of the specific slave. This field is editable. • Slave

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Configuration • 46 This field contains the name of SERCOS III slave as specified by the manufacturer or vendor of the slave.. This field is not editable. • Description This field contains a brief description of the SERCOS III Slave. This field is editable. • Vendor This field contains the vendor of the SERCOS III Slave This field is not editable.

The navigation buttons below the table have the following meaning: • 1st Puts the currently marked entry to the top of the list. • up Moves the currently marked entry one line higher. • down Moves the currently marked entry one line lower. • last Puts the currently marked entry to the bottom of the list.

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Configuration • 47 4.5 Process Data For the SERCOS III Master DTM the Process Data pane serves as an external process data interface, e. g. for data transfer to a PLC unit. The process data pane lists the slave devices connected to the master, as well as the configured modules or input or output signals of the devices. This makes the fieldbus structure visible. For the configured modules or signals names can be set. In addition signal data available to the OPC server can be checked.

Figure 30: Process Data

Column Meaning Type Device labeling provided by the hardware: Also description of the modules or input or output signals configured to the device. The value enclosed in brackets after the text signifies the hexadecimal representation of the slave address. Tag Device name provided by the hardware (not changeable in the FDT container) or name for the modules configured to the device or for the input or output signals (changeable). OPC Option which module or signal data shall be provided for the OPC server. Table 19: Process Data

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Configuration • 48 4.6 Address Table The Address Table dialog pane shows a list of all devices with their corresponding addresses used in the process data image. The displayed addresses refer to the used SERCOS III. To configure the address data: ¾ Select Configuration > Address Table in the navigation area.

Figure 31: Configuration > Address Table (In the Figure shown here, in the column Device or Name example devices are displayed.)

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Configuration • 49 4.6.1 Auto Addressing, Display Mode, CSV Export

Auto Addressing

Figure 32: Configuration > Address Table - Auto Addressing

The Auto Addressing is used by default. For manual addressing the check-box must be unchecked.

Note: Currently manual addressing is not supported.

Display Mode ¾ Use the Display Mode drop-down list to select data decimal or hexadecimal display mode.

Figure 33: Configuration > Address Table - Display Mode

CSV Export The CSV Export option allows to export input and output addresses as CSV file (CSV = comma separated value). Therefore: ¾ Click to the CSV Export button. ° A file saving dialog opens. ¾ Save the data as *.CSV file. You can open the generated data by means of a spreadsheet application.

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Diagnosis • 50 5 Diagnosis 5.1 Overview Diagnosis The dialog Diagnosis serves to diagnose the device behavior and communication errors. For diagnosis the device must reside in online state. The Extended Diagnosis helps to find communication and configuration errors, when default diagnosis fails.

Extended Diagnosis is presently not available in the current version of the SERCOS III Master DTM.

Diagnosis Panes The table below gives an overview for the individual Diagnosis dialog panes descriptions: Section Page Firmware Diagnosis 51 General Diagnosis 52 Master Diagnosis 55

Table 20: Descriptions of the Diagnosis Panes

Note: Accessing the Diagnosis panes of the SERCOS III Master DTM requires an online connection from the SERCOS III Master DTM to the SERCOS III Master device.

For further information, refer to section Connecting/Disconnecting Device on page 62.

Figure 34: Navigation Area - Diagnosis

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Diagnosis • 51 5.2 Firmware Diagnosis In the dialog Firmware Diagnosis the current task information of the firmware is displayed. Under Firmware or Version the name of the firmware and version (including the date) are indicated.

Figure 35: 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 Task Task number Name of task Name of the task Version Version of the task Prio Priority of the task Description Description of the task State Status of the task Table 21: Description Table Task Information

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Diagnosis • 52 5.3 General Diagnosis Information regarding the Device State and other general diagnosis parameters are displayed in the General Diagnosis dialog.

Figure 36: General Diagnosis

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Diagnosis • 53

Indication Meaning Device State Communicating Communicating: Shows that the SERCOS III stack executes the network communication.

Run Device is configured: Shows that the SERCOS III stack has been configured correctly.

Ready Ready: Shows that the SERCOS III stack has been started correctly. The SERCOS III stack waits for a configuration.

Error Error: Shows that the SERCOS III stack records a device status error. For further information to the error characteristics and the number of counted errors refer to the extended diagnosis.

Network State Operate Operate: Shows that the SERCOS III stack is in data exchange. In a cyclic data exchange the input data or the output data of the SERCOS III Slave are transmitted to the SERCOS III Slave.

Idle Idle: Shows that the SERCOS III stack is in idle mode.

Stop Stop: Shows that the SERCOS III stack is in Stop state: There is no cyclic data exchange at the SERCOS III network. The SERCOS III stack was stopped by the application program or it changed to the Stop state because of a bus error. Offline Offline: The SERCOS III Master is offline pending it does not have a valid configuration.

Configuration State Configuration Configuration locked: Shows that the SERCOS III stack configuration locked is locked, to avoid the configuration data are typed over.

New Configura- New Configuration pending: Shows that a new SERCOS III stack tion pending configuration is available.

Reset required Reset required: Shows that a firmware reset is required as a new SERCOS III stack configuration has been loaded into the device.

Bus ON Bus ON: Shows wether the bus communication was started or stopped. I. e., whether the device is active on the bus or no bus communication to the device is possible and no response telegrams are sent. Table 22: Indication General Diagnosis

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Diagnosis • 54

Parameter Meaning Communication Error Communication Error: Shows the message text of the communication error. If the cause of the current error is resolved, „ – “ is displayed. Watchdog time Watchdog time: Shows the watchdog time in ms. Error Count 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 if they were network related or caused internally. Table 23: Parameter General Diagnosis

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Diagnosis • 55 5.4 Master Diagnosis Information regarding the Slave State, slave errors and slaves configured, active or in diagnostic are displayed in the Master Diagnosis dialog.

Figure 37: Master Diagnosis

Parameter Meaning Range of Value / Value Slave State Shows if slave state is ok or not. UNDEFINED, OK, The slave state field for master diagnosis FAILED shows whether the master is in cyclic data exchange to all configured slaves. In case there is at least one slave missing or if the slave has a diagnostic request pending, the status is set to FAILED. For protocols that support non-cyclic communication only, the slave state is set to OK as soon as a valid configuration is found. Slave Error Log Shows if the Slave Error Log Indicator is EMPTY, AVAILABLE Indicator available. The error log indicator field holds the number of entries in the internal error log. If all entries are read from the log, the field is set to zero. Configured Slaves Shows number of configured slaves. Number of configured slaves in the network according to the slave list derived from the configuration database created by the configuration software . The list includes the slaves to which the master has to open a connection. Active Slaves Shows number of active slaves. Number of slaves in data exchange mode. The list includes the slaves to which the master has successfully opened a connection. Slaves With Diagnostic Shows number of slaves with diagnostic. Number of Slaves with diagnosis or error slaves. Table 24: Parameter Master Diagnosis

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Additional Tools • 56 6 Additional Tools 6.1 Overview Additional Tools Under Additional Tools the Packet Monitor and the IO Monitor are provided for test and diagnosis purposes.

Additional Tools Panes The table below gives an overview for the individual Additional Tools dialog panes descriptions:

Section Page Packet Monitor 57 IO Monitor 61 Table 25: Descriptions of the Diagnosis Panes

Note: Accessing the Additional Tools panes of the SERCOS III Master DTM requires an online connection from the SERCOS III Master DTM to the SERCOS III Master device.

For further information, refer to section Connecting/Disconnecting Device on page 62.

Figure 38: Navigation Area - Additional Tools

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Additional Tools • 57 6.2 Packet Monitor The Packet Monitor serves for test and diagnosis purposes. Packets, i.e. messages can be sent once or cyclically to the connected device controlled by the user and packets received can be displayed. The minimum packet size amounts 40 Byte for the packet header. The sending and reception data are added. ¾ Open the Packet Monitor via Additional Tools > Packet Monitor.

Figure 39: Packet Monitor

Display Mode switches the representation of the send and reception data between decimal and hexadecimal. ¾ Select the button Reset Counter to reset the packet counter.

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Additional Tools • 58 6.2.1 Packet Header The packet header of the send or the reception packets contains the elements described in the following table.

Element Description Dest Destination Queue Handle Contains the identifier of the receiver (destination task queue of the netX firmware) of packets (requests) of the application (configuration software). Src Source Queue Handle Contains the identifier of the sender (sending task) of response packets (responses) of the netX firmware to the application (configuration software). Dest ID Destination Queue Reference Contains the identifier of the receiver of unsolicited sent packets (messages) of the netX firmware to the application (configuration software). Src ID Source Queue Reference Contains the identifier of the sender of unsolicited sent response packets (responses) of the application (configuration software) to the netX firmware. Len Packet Data Length (in Bytes) Length of the send and receive data ID Packet Identification As Unique Number Identifies identical data packets among each other. State Status / Error Code Transmits status or error codes to the packet sender. Cmd Command / Response Command response data of the data receiver Ext Reserved Field for extensions Rout Routing Information Internal value of the netX firmware Table 26: Descriptions Packet Header

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Additional Tools • 59

6.2.2 Sending Packet

Figure 40: Packet Header and Send Data

Packet Header The Packet Header shows the elements of the packet header of the sending packet, which is transmitted from the application (configuration software) to the mailbox of the device.

For further information refer to section Packet Header on page 58.

Auto Increment ID is an increment for identifier of identical data packets and increments the ID by 1 for each newly sent packet. ¾ Enter the values for the elements of the packet header.

Send Data ¾ Under Send Data enter the send data of the packet, which shall be transmitted from the application (configuration software) to the mailbox of the device.

Sending Packets once or cyclic ¾ To send packet once, select the button Put packet. ¾ To send packet cyclic, select the button Put cyclic.

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Additional Tools • 60 6.2.3 Receiving Packet

Figure 41: Packet Header and Receive Data

Packet Header The Packet Header shows the elements of the packet header of the receiving packet, which is transmitted back from the device to the application (configuration software).

For further information refer to section Packet Header on page 58.

Receive Data The Receive Data area shows the receive data of the packet, which is transmitted back from the device to the application (configuration software).

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Additional Tools • 61 6.3 IO Monitor The IO Monitor serves for test and diagnosis 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.

Note: Only change and write output data, if you know that no plant 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.

Figure 42: 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. Clear clears displayed error messages. ¾ Enter the output value and select the button Update. ° Always the data of the process image are displayed, also when these Bytes have not been reserved by the configuration.

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Online Functions • 62 7 Online Functions 7.1 Connecting/Disconnecting Device

Note: Several SERCOS III Master DTM functions e. g. Diagnosis or the configuration download in the FDT Framework require an online connection from the SERCOS III Master DTM to the SERCOS III Master device.

Connecting Device The following steps are needed to establish a connection from the SERCOS III Master DTM to a SERCOS III Master device: Under Settings in the Driver pane: 1. Select one or several driver/s. 2. Configure the driver, if necessary. Under Settings in the Device Assignment pane: 3. Scan for the device/s (with or without firmware). 4. Select the device (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 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.

An overview of the descriptions for these steps you find in the section Overview Settings on page 23.

8. In the DTM interface dialog select the OK button, to apply the selection and to close the DTM interface dialog. 9. Put a right-click on the SERCOS III Master device icon. 10. Select the Connect command from the context menu. ° The SERCOS III Master device now is connected to the SERCOS III Master DTM via an online connection. In the network view the device description at the Master device icon is displayed with a green colored background.

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Online Functions • 63

Disconnecting Device To disconnect an online connection from the SERCOS III Master device to a SERCOS III Master DTM take the following steps: 1. In the DTM interface dialog select the OK button, to close the DTM interface dialog. 2. Right-click on the SERCOS III Master device icon. 3. Select the Disconnect command from the context menu. ° Now the SERCOS III Master device is disconnected from the DTM.

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Online Functions • 64 7.2 Network Scan With Network Scan... it is possible to find out automatically which types SERCOS III devices are attached to the SERCOS III Master device. To scan the network structure, proceed as follows: 1. Connecting Device:

Note: Accessing the display window for Network Scan... requires an online connection from the SERCOS III Master DTM to the SERCOS III Master device.

For further information refer to section Connecting/Disconnecting Device on page 62.

2. Select Network Scan... from the context menu (right mouse click). ° A window with data of the found devices is displayed. 3. Select the Create Devices button. ° The configuration software scans, which SERCOS III devices are attached to the SERCOS III Master device.

For further information refer to section Display of the Network Scan function on page 65.

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Online Functions • 65 7.2.1 Display of the Network Scan function A window similar to the following appears:

Figure 43: Hardware Devices found by Network Scan Function

Parameter Description Station Address SERCOS III station address, which displays the logical sequence of the devices within a SERCOS III network. Device Type ID Identification (ID) Sub Device Type The sub device type of the device type, if applicable Device Class The device class DTM Device The device name taken from the DTM Quality Associated quality information Action The action performed with the corresponding device (for instance, addition or removal of the device) Table 27: Display for Network Scan – Table above

The lower table in the display window of the Network Scan function compares possible differences in device information taken from • The hardware device (displayed in central column of 3) • and the DTM (displayed in right column of 3) The left column contains which information is compared between the information sources ‘Hardware Device’ and ‘DTM’.

Note: If a field contains the text ‘n/a’, the corresponding information is not applicable in the current context.

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Online Functions • 66 7.3 Download Configuration

Note: To download configuration parameter data to the SERCOS III Master device an online connection from the SERCOS III Master DTM to the SERCOS III Master device is required.

Further information can be found in the Connecting/Disconnecting Device section on page 62.

To transfer the configuration with the corresponding parameter data to the SERCOS III Master device you download the data to it using the frame application of the configuration software.

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Online Functions • 67 7.4 Start /Stop Communication You can manually start or stop the communication between a SERCOS III Master device and SERCOS III Slave devices. • Start Communication is enabled, if the communication has been stopped before or if the configuration requires this (Controlled release of communication). • Stop Communication is enabled, if the communication has been started. To start or to stop the communication, proceed as follows:

Start Communication 4. Connecting Device:

Note: To start the communication of the device at the bus manually, an online connection from the SERCOS III Master DTM to the SERCOS III Master device is required.

Further information can be found in the Connecting/Disconnecting Device section on page 62.

5. Select Additional Functions > Service > Start Communication from the context menu (right mouse click). ° The device communicates at the bus.

Stop Communication 6. Select Additional Functions > Service > Stop Communication from the context menu (right mouse click). ° The communication of the device at the bus is stopped.

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Online Functions • 68 7.5 License In the License pane you can: • check, which licenses are present in the device, • order licenses, • transfer license files to the device.

Figure 44: License Pane

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Online Functions • 69 7.5.1 Which licenses are present in the Device? Check in the License pane which licenses are present in the device. ¾ Therefore click to the Master Protocols or Utilities folder to expand it. ° The column Existing indicates which licenses are present in the device.

License for Protocols 1 General Master License. On the device maximally 1 communication protocol with master function can be implemented.

2 General Master Licenses. On the device maximally 2 communication protocols with master function can be implemented.

License for Utilities SYCON.net, OPC Server, QVis bzw. CoDeSys

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Online Functions • 70 7.5.2 How to order a license To order a license proceed as follows: • Assign the device to the DTM, • Select the required licenses, • Enter the ordering data and • Send your order via E Mail, Fax or Telephone.

7.5.2.1 Assigning the Master device to the DTM

Note: You first need to assign the Master device to the DTM. Only after this the device data and the available licenses are displayed in the License dialog.

1. Open the DTM configuration dialog via double click to the device device icon of the Master. 2. Select one or several driver/s. ¾ Select Settings > Driver in the navigation area. ¾ In the Driver pane check the checkbox for the driver/s. 3. Configure the driver, if necessary. ¾ Im Navigationsbereich Einstellungen > Treiber > [Name des zugewiesenen Treibers] aufrufen. ¾ Select Settings > Driver > [Name of the assigned driver] in the navigation area. ¾ In the drive dialog pane configure the driver settings. 4. Scan for the device/s. ¾ Select Settings > Device Assignment in the navigation area. ¾ In the Device Assignment pane select the list box entry suitable only or all. ¾ Select the Scan button, to start the scanning process. 5. Select the device and apply the selection. ¾ In the Device Assignment pane in the selection list Device selection check the check box for the device. ¾ Select the Apply button, to apply the selection. 6. Close the DTM configuration dialog via OK.

For details to the device assignment, refer to section Overview Settings on page 23.

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Online Functions • 71

7.5.2.2 Selecting the License 1. Open the License pane: ¾ Therefore open the the context menu, via right mouse click to the device device icon of the Master. ¾ From the context menu select Additional Functions > License. In the License pane: 2. Under License click to the Master Protocols folder to expand it. 3. In the column Order check the checkbox for the desired number of licenses: 1 General Master License or 2 General Master Licenses. And / Or: 4. Under License click to the Utilies folder to expand it. 5. In the column Order check the checkbox for: SYCON.net, OPC Server, QVis or CoDeSys.

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Online Functions • 72

7.5.2.3 Entering the Order Data 1. In the License pane under Name enter any obligatory order data. 2. Select in the list field [subsidiary] the entry for the subsidiary to which the order shall be send.

Device Data (order data read from the device) The following order data read from the device are displayed in the License pane: • Manufacturer • Device number • Serial number • Chiptype • Step (chip revision) • Romcode revision • Checksum (checksum of the device data)

Data to manage the Order Mandatory data to the order request (editable fields in the License pane): • Licensetype (User Single Device Lizenz): • First Name • Surname • E Mail (E-Mail address, to which the license download link shall be send.) • Telephone • Fax • Company • Addresse • Country • City, State, Zip Additional order data, not mandatory (editable fields in the License pane): • Order number • Value added tax identification number

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Online Functions • 73

7.5.2.4 Ordering the License by E Mail ¾ Click to the buttonE Mail. ° A prepared ordering E Mail License request is opened, to the E Mail address of the subsidiary, to which the order shall be send. ° This ordering E Mail contains the automatically generated file EmailOrderRequest_[Devicenumber]_[Serialnumber].xml with a summary info of the order information.

Figure 45: Example: ordering E Mail License request

¾ Send the ordering E Mail License request. ° The order process is complete.

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Online Functions • 74

7.5.2.5 Or ordering the License by Fax or by Telephone: ¾ Click to the button Print Fax Form or Telephone.

Note: If your browser does not display the order data or the window Move Element or Copy Element are displayed, check the safety settings of your system.

° The summary of the ordering data PrintOrderRequest_ [Devicenumber]_[Serialnumber].html netX License Order Form is opend in a browser window.

Figure 46: Example: order data form netX License Order Form

¾ Print out the order data form netX License Order Form and send it by fax. Or: ¾ Keep ready the order data form and communicate the order data via telephone. ° The order process is complete.

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Online Functions • 75 7.5.3 How to get the License and transfer it to the Device Licenses are deliverd as license files.

Note: License files can only be delivered via E Mail.

° The license file is delivered via E Mail. The E Mail contains a link to download the license file.

After the license file has been delivered you transfer the received license file into the device. 1. Download the license file *.nxl to your system. ¾ Therefore open the E Mail. ¾ Click to the Link for the Download of the license file and download it to your system.

2. Transfer the license file *.nxl to the device. ¾ In the License pane click to the button Download License. ¾ In the file selection window Open select the license file netX License Files (*.nxl) and click to the button Open. ° Then the license is present in the device an will be activated at the next reset of the device.

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Error Numbers • 76 8 Error Numbers 8.1 Error Code Definition 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 definition: COM Errors are HRESULTs, which are 32 bit values using the following layout: 3 3 2 2 2 2 2 2 2 2 2 2 1 1 1 1 1 1 1 1 1 1 1 0 9 8 7 6 5 4 3 2 1 0 9 8 7 6 5 4 3 2 1 0 9 8 7 6 5 4 3 2 1 0 +---+-+-+------+------+ |Sev|C|R| Facility | Code | +---+-+-+------+------+

where Sev - is the severity code: 00 - Success 01 - Informational 10 - Warning 11 - 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.

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Error Numbers • 77 8.2 Overview Error Numbers

Module Error Code Region General Hardware Error Codes / RCX Errors - MID_SYS Task Error Codes: 0xC02B0001L to RCX Operating System 0x8004BFFF to 0xC02B4B54L RCX Errors - Common Status Codes: 0x00000000L to 0xC000F006L RCX Errors - Status & Error Codes: 0x00000000L to 0xC0000008 SERCOS III Master Status/Error Status/Error Codes of SERCOS III Master CP Task: Codes 0xC0700001L to 0xC0700063L Status/Error Codes of SERCOS III Master SVC Task: 0xC0710001L to 0xC0710022L Status/Error Codes of SERCOS III Master AP Task: 0xC0720001L to 0xC0720007L 0xC0724000L to 0xC0724070L (XML structure related messages) ODM Server General ODM Error Codes: 0x8004C700 to 0x8004C761

General ODM Driver Error Codes: 0x8004C7A0 to 0x8004C7C2 ODM Drivers ODM cifX Driver Specific Errors: 0x8004C001 to 0x8004C0A4 Error Codes cifX Device Driver Error Codes cifX Device Driver: 0x00000000 to 0x800C002D DBM ODM DBM V4 Error Codes: 0xC004C810 to 0xC004C878 Table 28: Error Code Regions

The communication system-specific error codes are described in the manuals of the corresponding protocol tasks.

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Error Numbers • 78 8.3 General Hardware Error Codes

8.3.1 RCX Errors - MID_SYS Task Error Codes

ID of the Error Code Value Description TLR_E_MID_SYS_QUE_ UNKNOWN 0xC02B0001L Queue unknown. TLR_E_MID_SYS_QUE_ IDX_UNKNOWN 0xC02B0002L Queue table index does not exist. TLR_E_MID_SYS_TSK_ UNKNOWN 0xC02B0003L Task unknown. TLR_E_MID_SYS_TSK_ IDX_UNKNOWN 0xC02B0004L Task table index does not exist. TLR_E_MID_SYS_TSK_ HANDLE_INVALID 0xC02B0005L Task handle invalid. TLR_E_MID_SYS_TSK_INFO_ IDX_UNKNOWN 0xC02B0006L Task info field index unknown. TLR_I_MID_SYS_FILE_ RETRANSMIT 0x402B0001L The last data block was invalid, please retransmit. TLR_E_MID_SYS_FILE_ XFR_TYPE_INVALID 0xC02B0007L Requested transfer type invalid. TLR_E_MID_SYS_FILE_ REQUEST_INCORRECT 0xC02B0008L Request is incorrectly formatted i.e. wrong parameters. TLR_E_MID_SYS_UNKNOWN_ PORT_INDEX 0xC02B0009L Unknown port index. TLR_E_MID_SYS_ROUTER_ TABLE_FULL 0xC02B000AL Router Table is full. TLR_E_MID_SYS_NO_SUCH_ 0xC02B000BL No such router in table. ROUTER_IN_TABLE TLR_E_MID_SYS_INSTANCE_ NOT_NULL 0xC02B000CL Mid_Sys Instance is not 0. TLR_E_MID_SYS_COMMAND_ INVALID 0xC02B000DL Invalid command. TLR_E_MID_SYS_TSK_ INVALID 0xC02B000EL Invalid task handle. TLR_E_MID_SYS_TSK_NOT_ A_USER_TASK 0xC02B000FL Access denied. Not a user task (See Config-File). TLR_E_MID_SYS_LOG_QUE_ NOT_SETTABLE 0xC02B0010L Logical queue handle not settable. TLR_E_MID_SYS_LOG_QUE_ NOT_INVALID 0xC02B0011L Logical queue handle invalid. TLR_E_MID_SYS_LOG_QUE_ NOT_SET 0xC02B0012L Logical queue handle has not been set. TLR_E_MID_SYS_LOG_QUE_ ALREADY_USED 0xC02B0013L Logical queue handle is already in use. TLR_E_MID_SYS_TSK_NO_ DEFAULT_QUEUE 0xC02B0014L Task has no default process queue. TLR_E_MID_SYS_MODULE_ INVALID 0xC02B0015L Firmware Module is invalid. CRC-32 check failed. TLR_E_MID_SYS_MODULE_ NOT_FOUND 0xC02B0016L Firmware Module has not been found. Maybe it has not been downloaded before. TLR_E_MID_SYS_MODULE_ RELOC_ERROR 0xC02B0017L Firmware Module has an invalid reloc table. TLR_E_MID_SYS_MODULE_ NO_INIT_TBL 0xC02B0018L Firmware Module has no init table. TLR_E_MID_SYS_MODULE_ NO_ENTRY_POINT 0xC02B0019L Firmware Module has no code entry point. TLR_E_MID_SYS_ACCESS_ 0xC02B001AL Access denied due to current DENIED_IN_LOCKED_STATE operating conditions. TLR_E_MID_SYS_INVALID_ FIRMWARE_SIZE 0xC02B001BL Firmware does not fit into flash. TLR_E_MID_SYS_MODULE_ 0xC02B001CL The relocation distance is too RELOCATION_DISTANCE_ TOO_LONG long. More see next page

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Error Numbers • 79

ID of the Error Code Value Description TLR_E_MID_SYS_SEC_ FAILED 0xC02B001DL Access to the security flash failed. TLR_E_MID_SYS_SEC_ DISABLED 0xC02B001EL Security flash is disabled at firmware. TLR_E_MID_SYS_FILE_ TRANSFER_IN_USE 0xC02B524CL File Transfer in use. TLR_E_MID_SYS_FILE_ TRANSFER_PACKET_ 0xC02B4444L File Transfer Packet invalid. INVALID TLR_E_MID_SYS_FILE_TRANSFER_ 0xC02B5342L File Transfer is not active. NOT_ACTIVE TLR_E_MID_SYS_FILE_TRANSFER_ INVALID 0xC02B5257L File Transfer has invalid type code. TLR_E_MID_SYS_FILE_CRC_ 0xC02B4352L File Transfer was tried REPEATEDLY_WRONG repeatedly with a wrong CRC. TLR_E_MID_SYS_FILE_TRANSFER_ 0xC02B4353L Transfer Type is not available. TYPE_NOT_AVAILABLE TLR_E_MID_SYS_PATH_INVALID 0xC02B5555L File Path submitted in File Transfer was invalid. TLR_E_MID_SYS_DRIVER_ 0xC02BFFFFL Driver Configuration Table Init CFG_TABLE_INIT_FUNCTION_ MISSING Function missing. TLR_E_MID_SYS_CONFIGURATION_ LOCKED 0xC02B4B54L Configuration has been locked. Table 29: RCX Errors - MID_SYS Task Error Codes (from Operating System)

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Error Numbers • 80 8.3.2 RCX Errors - Common Status Codes

ID of the Error Code Value Description TLR_S_OK 0x00000000L Operation succeeded. TLR_E_FAIL 0xC0000001L Common error, detailed error information optionally present in the data area of packet. TLR_E_UNEXPECTED 0xC0000002L Unexpected failure. TLR_E_OUTOFMEMORY 0xC0000003L Ran out of memory. TLR_E_UNKNOWN_COMMAND 0xC0000004L Unknown Command in Packet received. TLR_E_UNKNOWN_DESTINATION 0xC0000005L Unknown Destination in Packet received. TLR_E_UNKNOWN_DESTINATION_ID 0xC0000006L Unknown Destination Id in Packet received. TLR_E_INVALID_PACKET_LEN 0xC0000007L Packet length is invalid. TLR_E_INVALID_EXTENSION 0xC0000008L Invalid Extension in Packet received. RCX_COMM_WATCHDOG_TIMEOUT 0xC000000CL Watchdog error occurred. RCX_COMM_INIT_FAULT 0xC0000100L General initialization fault. RCX_COMM_DATABASE_ACCESS_ FAILED 0xC0000101L Database access failture. RCX_COMM_CONFIGURATION_ FAULT 0xC0000120L General configuration fault. RCX_COMM_INCONSISTENT_ DATA_SET 0xC0000121L Inconsistent configuration data. RCX_COMM_DATA_SET_MISMATCH 0xC0000122L Configuration data set mismatch. RCX_COMM_INSUFFICIENT_ LICENSE 0xC0000123L Insufficient license. RCX_COMM_PARAMETER_ERROR 0xC0000124L Parameter error. RCX_COMM_INVALID_NETWORK_ ADDRESS 0xC0000125L Network address invalid. RCX_COMM_NETWORK_FAULT 0xC0000140L General communication fault. RCX_COMM_CONNECTION_ CLOSED 0xC0000141L Connection closed. RCX_COMM_CONNECTION_ TIMEOUT 0xC0000142L Connection timeout. RCX_COMM_LONELY_NETWORK 0xC0000143L Lonely network. RCX_COMM_DUPLICATE_ NODE 0xC0000144L Duplicate network address. RCX_COMM_CABLE_ DISCONNECT 0xC0000145L Cable disconnected. TLR_S_FRAGMENTED 0x0000F005L Fragment accepted. TLR_E_RESET_REQUIRED 0xC000F006L Reset required. Table 30: RCX Errors - Common Status Codes (from Operating System)

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Error Numbers • 81 8.3.3 RCX Errors - Status & Error Codes

ID of the Error Code Value Description RCX_S_OK 0x00000000 SUCCESS, STATUS OKAY RCX_S_QUE_UNKNOWN 0xC02B0001 UNKNOWN QUEUE RCX_S_QUE_INDEX_UNKNOWN 0xC02B0002 UNKNOWN QUEUE INDEX RCX_S_TASK_UNKNOWN 0xC02B0003 UNKNOWN TASK RCX_S_TASK_INDEX_UNKNOWN 0xC02B0004 UNKNOWN TASK INDEX RCX_S_TASK_HANDLE_INVALID 0xC02B0005 INVALID TASK HANDLE RCX_S_TASK_INFO_IDX_UNKNOWN 0xC02B0006 UNKNOWN INDEX RCX_S_FILE_XFR_TYPE_INVALID 0xC02B0007 INVALID TRANSFER TYPE RCX_S_FILE_REQUEST_INCORRECT 0xC02B0008 INVALID FILE REQUEST RCX_S_UNKNOWN_DESTINATION 0xC0000005 UNKNOWN DESTINATION RCX_S_UNKNOWN_DESTINATION_ID 0xC0000006 UNKNOWN DESTINATION ID RCX_S_INVALID_LENGTH 0xC0000007 INVALID LENGTH RCX_S_UNKNOWN_COMMAND 0xC0000004 UNKNOWN COMMAND RCX_S_INVALID_EXTENSION 0xC0000008 INVALID EXTENSION Table 31: RCX Errors - Status & Error Codes (from Operating System)

8.3.3.1 RCX Errors - Status & Error Codes – Slave State

ID of the Error Code Value Description RCX_SLAVE_STATE_UNDEFINED 0x00000000 UNDEFINED RCX_SLAVE_STATE_OK 0x00000001 OK RCX_SLAVE_STATE_FAILED 0x00000002 FAILED (at least one slave) Table 32: RCX Errors - Status & Error Codes – Slave State (from Operating System)

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Error Numbers • 82 8.4 SERCOS III Master Status/Error Codes

8.4.1 Status/Error Codes of SERCOS III Master CP Task

ID of the Error Code Value Description TLR_E_SIII_MA_CP_COMMAND_INVALID 0xC0700001L Invalid command value. TLR_E_SIII_MA_CP_INVALID_STARTUP_PARA 0xC0700002L Invalid Startup parameter. METER TLR_E_SIII_MA_CP_WAITING_FOR_TOPOLOG 0xC0700003L Waiting for Topology Detect Y_DETECT (CP0). TLR_E_SIII_MA_CP_LLD_NOT_STARTED 0xC0700004L LLD not started. TLR_E_SIII_MA_CP_INIT_CALLBACK_HP_FAILE 0xC0700005L Initialization of HP Callback D Failed. TLR_E_SIII_MA_CP_INIT_CALLBACK_DEVSTAT 0xC0700006L Initialization of DevStatus US_FAILED Callback Failed. TLR_E_SIII_MA_CP_INIT_CALLBACK_TOPOLO 0xC0700007L Initialization of Topology Detect GY_DETECT_FAILED Callback Failed. TLR_E_SIII_MA_CP_CONFIGURATION_BUFFER 0xC0700008L Configuration Buffer is already _ALREADY_OPEN open. TLR_E_SIII_MA_CP_CONFIGURATION_BUFFER 0xC0700009L Configuration Buffer is not open. _IS_NOT_OPEN TLR_E_SIII_MA_CP_INVALID_SLAVE_ADDRES 0xC070000AL Invalid slave address. S TLR_E_SIII_MA_CP_TELEGRAM_OFFSET_CAN 0xC070000BL Telegram offset cannot be set to NOT_BE_IN_MDT_TELEGRAM MDT telegram. TLR_E_SIII_MA_CP_TELEGRAM_OFFSET_CAN 0xC070000CL Telegram offset cannot be set to NOT_BE_IN_AT_TELEGRAM AT telegram. TLR_E_SIII_MA_CP_TELEGRAM_OFFSET_HAS 0xC070000DL Telegram offset has invalid _INVALID_TELEGRAM_NO telegram number. TLR_E_SIII_MA_CP_TELEGRAM_OFFSET_HAS 0xC070000EL Telegram offset has invalid _INVALID_OFFSET offset in frame. TLR_E_SIII_MA_CP_MDT_SVCH_TELEGRAM_O 0xC070000FL MDT ServiceChannel Telegram FFSET_CANNOT_BE_IN_AT_TELEGRAM offset cannot be set to AT telegram. TLR_E_SIII_MA_CP_MDT_SVCH_TELEGRAM_O 0xC0700010L MDT ServiceChannel Telegram FFSET_HAS_INVALID_TELEGRAM_NO offset has invalid telegram number. TLR_E_SIII_MA_CP_MDT_SVCH_TELEGRAM_O 0xC0700011L MDT ServiceChannel Telegram FFSET_HAS_INVALID_OFFSET offset has invalid offset in frame. TLR_E_SIII_MA_CP_AT_SVCH_TELEGRAM_OF 0xC0700012L AT ServiceChannel Telegram FSET_CANNOT_BE_IN_MDT_TELEGRAM offset cannot be set to MDT telegram. TLR_E_SIII_MA_CP_AT_SVCH_TELEGRAM_OF 0xC0700013L AT ServiceChannel Telegram FSET_HAS_INVALID_TELEGRAM_NO offset has invalid telegram number. TLR_E_SIII_MA_CP_AT_SVCH_TELEGRAM_OF 0xC0700014L AT ServiceChannel Telegram FSET_HAS_INVALID_OFFSET offset has invalid offset in frame. TLR_E_SIII_MA_CP_DEV_CTRL_TELEGRAM_O 0xC0700015L DeviceControl Telegram offset FFSET_CANNOT_BE_IN_AT_TELEGRAM cannot be set to AT telegram. TLR_E_SIII_MA_CP_DEV_CTRL_TELEGRAM_O 0xC0700016L DeviceControl Telegram offset FFSET_HAS_INVALID_TELEGRAM_NO has invalid telegram number. TLR_E_SIII_MA_CP_DEV_CTRL_TELEGRAM_O 0xC0700017L Device Control Telegram offset FFSET_HAS_INVALID_OFFSET has invalid offset in frame. TLR_E_SIII_MA_CP_DEV_STATUS_TELEGRAM 0xC0700018L DeviceControl Telegram offset _OFFSET_CANNOT_BE_IN_MDT_TELEGRAM cannot be set to MDT telegram. More see next page Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Error Numbers • 83

ID of the Error Code Value Description TLR_E_SIII_MA_CP_DEV_STATUS_TELEGRAM 0xC0700019L DeviceStatus Telegram offset _OFFSET_HAS_INVALID_TELEGRAM_NO has invalid telegram number. TLR_E_SIII_MA_CP_DEV_STATUS_TELEGRAM 0xC070001AL DeviceStatus Telegram offset _OFFSET_HAS_INVALID_OFFSET has invalid offset in frame. TLR_E_SIII_MA_CP_SLAVE_ALREADY_IN_CON 0xC070001BL Slave already in configuration. FIGURATION TLR_E_SIII_MA_CP_SLAVE_NOT_IN_CONFIGU 0xC070001CL Slave is not in configuration. RATION TLR_E_SIII_MA_CP_INITCMD_SEGMENT_DOE 0xC070001DL InitCmd Segment does not S_NOT_MATCH_FIRST_PACKET match the first packet. TLR_E_SIII_MA_CP_LLD_TO_BE_IMPLEMENTE 0xC070001EL Unimplemented function D detected. TLR_E_SIII_MA_CP_LLD_UNKNOWN_ERROR 0xC070001FL Unknown Error. TLR_E_SIII_MA_CP_LLD_OUT_OF_MEMORY 0xC0700020L Out of memory. TLR_E_SIII_MA_CP_LLD_INVALID_SERVICE_C 0xC0700021L Invalid Service Channel HANNEL Number. TLR_E_SIII_MA_CP_LLD_INVALID_DEVICE 0xC0700022L Invalid Slave Address. TLR_E_SIII_MA_CP_LLD_INVALID_PHASE_TRA 0xC0700023L Invalid Phase transition. NSITION TLR_E_SIII_MA_CP_LLD_NO_CONFIGURATION 0xC0700024L No Configuration data for _DATA_FOR_CP3_4 CP3/CP4 available. TLR_E_SIII_MA_CP_LLD_INVALID_MDT0_SIZE 0xC0700025L Invalid MDT0 length. TLR_E_SIII_MA_CP_LLD_INVALID_MDT1_SIZE 0xC0700026L Invalid MDT1 length. TLR_E_SIII_MA_CP_LLD_INVALID_MDT2_SIZE 0xC0700027L Invalid MDT2 length. TLR_E_SIII_MA_CP_LLD_INVALID_MDT3_SIZE 0xC0700028L Invalid MDT3 length. TLR_E_SIII_MA_CP_LLD_INVALID_AT0_SIZE 0xC0700029L Invalid AT0 length. TLR_E_SIII_MA_CP_LLD_INVALID_AT1_SIZE 0xC070002AL Invalid AT1 length. TLR_E_SIII_MA_CP_LLD_INVALID_AT2_SIZE 0xC070002BL Invalid AT2 length. TLR_E_SIII_MA_CP_LLD_INVALID_AT3_SIZE 0xC070002CL Invalid AT3 length. TLR_E_SIII_MA_CP_LLD_INVALID_DEVICE_CO 0xC070002DL Device Control Offset cannot NTROL_OFFSET_TEL_TYPE be placed into AT telegram. TLR_E_SIII_MA_CP_LLD_INVALID_DEVICE_CO 0xC070002EL Telegram Number in Device NTROL_OFFSET_TEL_NO Control Offset is invalid. TLR_E_SIII_MA_CP_LLD_INVALID_DEVICE_CO 0xC070002FL Frame Offset in Device NTROL_OFFSET_OFS_TOO_LOW Control Offset is too low. TLR_E_SIII_MA_CP_LLD_INVALID_DEVICE_CO 0xC0700030L Frame Offset in Device NTROL_OFFSET_OFS_TOO_HIGH Control Offset is too high. TLR_E_SIII_MA_CP_LLD_INVALID_DEVICE_CO 0xC0700031L Frame Offset in Device NTROL_OFFSET_OFS_NOT_EVEN Control Offset is not word- aligned (16bit word). TLR_E_SIII_MA_CP_LLD_INVALID_DEVICE_ST 0xC0700032L Device Status Offset cannot ATUS_OFFSET_TEL_TYPE be placed into MDT telegram. TLR_E_SIII_MA_CP_LLD_INVALID_DEVICE_ST 0xC0700033L Telegram Number in Device ATUS_OFFSET_TEL_NO Status Offset is invalid. TLR_E_SIII_MA_CP_LLD_INVALID_DEVICE_ST 0xC0700034L Frame Offset in Device Status ATUS_OFFSET_OFS_TOO_LOW Offset is too low. TLR_E_SIII_MA_CP_LLD_INVALID_DEVICE_ST 0xC0700035L Frame Offset in Device Status ATUS_OFFSET_OFS_TOO_HIGH Offset is too high. TLR_E_SIII_MA_CP_LLD_INVALID_DEVICE_ST 0xC0700036L Frame Offset in Device Status ATUS_OFFSET_OFS_NOT_EVEN Offset is not word-aligned (16bit word). More see next page

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Error Numbers • 84

ID of the Error Code Value Description TLR_E_SIII_MA_CP_LLD_INVALID_MDT_SVC_C 0xC0700037L MDT Service Channel Offset HANNEL_OFFSET_TEL_TYPE cannot be placed into AT telegram. TLR_E_SIII_MA_CP_LLD_INVALID_MDT_SVC_C 0xC0700038L Telegram Number in MDT HANNEL_OFFSET_TEL_NO Service Channel Offset is invalid. TLR_E_SIII_MA_CP_LLD_INVALID_MDT_SVC_C 0xC0700039L Frame Offset in MTD Service HANNEL_OFFSET_OFS_TOO_LOW Channel Offset is too low. TLR_E_SIII_MA_CP_LLD_INVALID_MDT_SVC_C 0xC070003AL Frame Offset in MDT Service HANNEL_OFFSET_OFS_TOO_HIGH Channel Offset is too high. TLR_E_SIII_MA_CP_LLD_INVALID_MDT_SVC_C 0xC070003BL Frame Offset in MDT Service HANNEL_OFFSET_OFS_NOT_EVEN Channel Offset is not word- aligned (16bit word). TLR_E_SIII_MA_CP_LLD_INVALID_AT_SVC_CH 0xC070003CL AT Service Channel Offset ANNEL_OFFSET_TEL_TYPE cannot be placed into MDT telegram. TLR_E_SIII_MA_CP_LLD_INVALID_AT_SVC_CH 0xC070003DL Telegram Number in AT ANNEL_OFFSET_TEL_NO Service Channel Offset is invalid. TLR_E_SIII_MA_CP_LLD_INVALID_AT_SVC_CH 0xC070003EL Frame Offset in AT Service ANNEL_OFFSET_OFS_TOO_LOW Channel Offset is too low. TLR_E_SIII_MA_CP_LLD_INVALID_AT_SVC_CH 0xC070003FL Frame Offset in AT Service ANNEL_OFFSET_OFS_TOO_HIGH Channel Offset is too high. TLR_E_SIII_MA_CP_LLD_INVALID_AT_SVC_CH 0xC0700040L Frame Offset in AT Service ANNEL_OFFSET_OFS_NOT_EVEN Channel Offset is not word- aligned (16bit word). TLR_E_SIII_MA_CP_LLD_INVALID_MDT_RTDAT 0xC0700041L MDT Connection Offset A_OFFSET_TEL_TYPE cannot be placed into AT telegram. TLR_E_SIII_MA_CP_LLD_INVALID_MDT_RTDAT 0xC0700042L Telegram Number in MDT A_OFFSET_TEL_NO Connection Offset is invalid. TLR_E_SIII_MA_CP_LLD_INVALID_MDT_RTDAT 0xC0700043L Frame Offset in MDT A_OFFSET_OFS_TOO_LOW Connection Offset is too low. TLR_E_SIII_MA_CP_LLD_INVALID_MDT_RTDAT 0xC0700044L Frame Offset in MDT A_OFFSET_OFS_TOO_HIGH Connection Offset is too high. TLR_E_SIII_MA_CP_LLD_INVALID_MDT_RTDAT 0xC0700045L Frame Offset in AT A_OFFSET_OFS_NOT_EVEN Connection Offset is not word- aligned (16bit word). TLR_E_SIII_MA_CP_LLD_INVALID_AT_RTDATA 0xC0700046L AT Connection Offset cannot _OFFSET_TEL_TYPE be placed into MDT telegram. TLR_E_SIII_MA_CP_LLD_INVALID_AT_RTDATA 0xC0700047L Telegram Number in AT _OFFSET_TEL_NO Connection Offset is invalid. TLR_E_SIII_MA_CP_LLD_INVALID_AT_RTDATA 0xC0700048L Frame Offset in AT _OFFSET_OFS_TOO_LOW Connection Offset is too low. TLR_E_SIII_MA_CP_LLD_INVALID_AT_RTDATA 0xC0700049L Frame Offset in AT _OFFSET_OFS_TOO_HIGH Connection Offset is too high. TLR_E_SIII_MA_CP_LLD_INVALID_AT_RTDATA 0xC070004AL Frame Offset in MTD _OFFSET_OFS_NOT_EVEN Connection Offset is not word- aligned (16bit word). TLR_E_SIII_MA_CP_LLD_OVERLAPPING_REGI 0xC070004BL Overlapping regions detected ONS_DETECTED_IN_MDT_FRAMES within MDT frames. TLR_E_SIII_MA_CP_LLD_OVERLAPPING_REGI 0xC070004CL Overlapping regions detected ONS_DETECTED_IN_AT_FRAMES within AT frames. More see next page

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Error Numbers • 85

ID of the Error Code Value Description TLR_E_SIII_MA_CP_LLD_INVALID_SLAVE_ADD 0xC070004DL Invalid Slave Address in RESS_IN_CP3_4_CONFIG CP3/CP4 configuration data. TLR_E_SIII_MA_CP_LLD_CONFIGURE_NOT_AL 0xC070004EL Configuring CP3/CP4 not LOWED_IN_CURRENT_STATE allowed in current state. TLR_E_SIII_MA_CP_LLD_BUILDING_COPY_RO 0xC070004FL Building of copy routines UTINES_FAILED failed. TLR_E_SIII_MA_CP_LLD_INVALID_MDT_CONN 0xC0700050L Invalid MDT Connection CTRL_PROCESS_IMAGE_OFFSET Control Process Image Offset. TLR_E_SIII_MA_CP_LLD_INVALID_MDT_RTDAT 0xC0700051L Invalid MDT RtData Process A_PROCESS_IMAGE_OFFSET Image Offset. TLR_E_SIII_MA_CP_LLD_INVALID_AT_CONNCT 0xC0700052L Invalid AT Connection Control RL_PROCESS_IMAGE_OFFSET Process Image Offset. TLR_E_SIII_MA_CP_LLD_INVALID_AT_RTDATA 0xC0700053L Invalid AT RtData Control _PROCESS_IMAGE_OFFSET Process Image Offset. TLR_E_SIII_MA_CP_CONFIGURATION_NOT_P 0xC0700054L Configuration not possible in OSSIBLE_IN_CURRENT_STATE current master state. TLR_E_SIII_MA_CP_PHASE_CHANGE_IN_PRO 0xC0700055L Phase Change is in progress. GRESS TLR_E_SIII_MA_CP_REQUESTED_PHASE_IS_A 0xC0700056L Requested Phase is already LREADY_CURRENT_PHASE current phase. TLR_E_SIII_MA_CP_FINISH_CONFIGURATION_ 0xC0700057L Finish configuration download DOWNLOAD_FIRST first. TLR_E_SIII_MA_CP_NO_CONFIGURATION_FO 0xC0700058L No configuration for CP3 R_CP3_AVAILABLE available. TLR_E_SIII_MA_CP_NO_CONFIGURATION_FO 0xC0700059L No configuration for CP4 R_CP4_AVAILABLE available. TLR_E_SIII_MA_CP_INCOMPLETE_INITCMD_D 0xC070005AL Incomplete InitCmd Download OWNLOAD detected. TLR_E_SIII_MA_CP_INVALID_TRANSITION_FLA 0xC070005BL Invalid transition flags GS specified in InitCmd download. TLR_E_SIII_MA_CP_INVALID_INITCMD_LENGT 0xC070005CL Invalid length specified in H InitCmd download. TLR_E_SIII_MA_CP_PHASE_INDS_RECEIVER_ 0xC070005DL Phase Indication Receiver List LIST_IS_FULL is full. TLR_E_SIII_MA_CP_APP_NOT_REGISTERED 0xC070005EL Application queue is not registered. TLR_E_SIII_MA_CP_APP_REGISTERED_ALREA 0xC070005FL Application queue is DY registered already. TLR_I_SIII_MA_CP_BUS_IS_OFF 0x40700060L Please issue the BusOn command, since the bus is off. TLR_E_SIII_MA_CP_NO_DIAG_ENTRY_AVAILA 0xC0700061L No further diagnostic entries BLE currently available. TLR_E_SIII_MA_CP_LOCKED_DUE_TO_ERROR 0xC0700062L Locked due to error in _IN_PREVIOUS_PHASE_SWITCH previous phase switch. TLR_E_SIII_MA_CP_LOCKED_DUE_TO_DPM_ 0xC0700063L Locked due to error on DPM WATCHDOG_ERROR watchdog. Table 33: Status/Error Codes of SERCOS III Master CP Task

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Error Numbers • 86 8.4.2 Status/Error Codes of SERCOS III Master SVC Task

ID of the Error Code Value Description TLR_E_SERCOSIIIMASTER_SVC_COMMAND_I 0xC0710001L Invalid command value. NVALID TLR_E_SERCOSIIIMASTER_SVC_SLAVE_HS_TI 0xC0710002L Slave SVC Handshake MEOUT Timeout. TLR_E_SERCOSIIIMASTER_SVC_SLAVE_BUSY 0xC0710003L Slave SVC Busy Timeout. _TIMEOUT TLR_E_SERCOSIIIMASTER_SVC_SLAVE_ERR 0xC0710004L Slave SVC Error. OR TLR_E_SERCOSIIIMASTER_SVC_TRANSFER_A 0xC0710005L SVC-Transfer aborted. BORTED TLR_E_SERCOSIIIMASTER_SVC_INTERN_LOC 0xC0710006L Service Channels internally KED locked. TLR_E_SERCOSIIIMASTER_SVC_SLAVE_VALI 0xC0710015L SVC valid timeout. D_TIMEOUT TLR_E_SERCOSIIIMASTER_SVC_MACRO_STE 0xC0710010L SVC Macro FSM: OpenIdn P_OPENIDN_FAILED Failed. TLR_E_SERCOSIIIMASTER_SVC_MACRO_STE 0xC0710011L SVC Macro FSM: P_READATTR_FAILED ReadAttribute Failed. TLR_E_SERCOSIIIMASTER_SVC_MACRO_STE 0xC0710012L SVC Macro FSM: Get P_GETLL_FAILED ListLength Failed. TLR_E_SERCOSIIIMASTER_SVC_MACRO_STE 0xC0710013L SVC Macro FSM: Data P_ACCESSDATA_FAILED access failed. TLR_E_SERCOSIIIMASTER_SVC_INTERNAL_E 0xC0710014L Internal Error. RROR TLR_E_SERCOSIIIMASTER_SVC_INVALID_SEN 0xC0710016L Invalid Sender. DER TLR_E_SERCOSIIIMASTER_SVC_ABORT_ALRE 0xC0710017L Abort Already Running. ADY_RUNNING TLR_E_SERCOSIIIMASTER_SVC_INVALID_ELE 0xC0710018L The parameter element is MENT wrong. TLR_E_SERCOSIIIMASTER_SVC_INVALID_SLA 0xC0710019L The parameter slave address VE_ADDRESS is wrong. TLR_E_SERCOSIIIMASTER_SVC_ATOMIC_TRA 0xC071001AL Atomic transfer in use. NSFER_IN_USE TLR_E_SERCOSIIIMASTER_SVC_ABORT_NOT 0xC071001BL Abort not possible. _POSSIBLE TLR_E_SERCOSIIIMASTER_SVC_DESTID_UNE 0xC071001CL Unexpected DestId. XPECTED TLR_E_SERCOSIIIMASTER_SVC_SEQUENCE_ 0xC071001DL Unexpected SVC sequence. UNEXPECTED TLR_E_SERCOSIIIMASTER_SVC_CLOSED 0xC071001EL SVC is closed. TLR_E_SERCOSIIIMASTER_SVC_PARAMETER 0xC071001FL SVC parameter is _UNEXPECTED unexpected. TLR_E_SERCOSIIIMASTER_SVC_INVALID_PRI 0xC0710020L Invalid priority. ORITY TLR_E_SERCOSIIIMASTER_SVC_INVALID_ISLI 0xC0710021L IsList parameter is wrong. ST TLR_E_SERCOSIIIMASTER_SVC_MACRO_TRA 0xC0710022L A macro transfer is already NSFER_IN_USE started. Table 34: Status/Error Codes of SERCOS III Master SVC Task

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Error Numbers • 87 8.4.3 Status/Error Codes of SERCOS III Master AP Task

ID of the Error Code Value Description TLR_E_SIII_MA_AP_COMMAND_INVALID 0xC0720001L Invalid command value. TLR_E_SIII_MA_AP_INVALID_STARTUP_PARA 0xC0720002L Invalid Startup parameter. METER TLR_E_SIII_MA_AP_MDT_PROCESS_DATA_IM 0xC0720003L Output Process Data Image AGE_SIZE_NOT_POSSIBLE Size not possible (MDT). TLR_E_SIII_MA_AP_AT_PROCESS_DATA_IMA 0xC0720004L Input Process Data Image GE_SIZE_NOT_POSSIBLE Size not possible (AT). TLR_E_SIII_MA_AP_LLD_NOT_STARTED 0xC0720005L SercosIII LLD not started. TLR_E_SIII_MA_AP_SET_PHASE_NOT_ALLOW 0xC0720006L Set Phase command not ED_DURING_CFG_LOADING allowed during configuration loading. TLR_E_SIII_MA_AP_PACKET_CFG_INTERFACE 0xC0720007L Configuration via packets is _NOT_AVAILABLE_DURING_CFG_LOADING not available during configuration loading. TLR_E_SIII_MA_AP_XML_CLOSING_TAG_DOE 0xC0724000L XML structure: Closing Tag S_NOT_MATCH_OPENING_TAG does not match opening tag. TLR_E_SIII_MA_AP_XML_UNEXPECTED_OPEN 0xC0724001L XML structure: Unexpected ING_TAG_IN_NUMBER_FIELD opening tag in number field. TLR_E_SIII_MA_AP_XML_UNEXPECTED_SINGL 0xC0724002L XML structure: Unexpected E_TAG_IN_NUMBER_FIELD single tag in number field. TLR_E_SIII_MA_AP_XML_CLOSING_TAG_DOE 0xC0724003L XML structure: Closing tag S_NOT_MATCH_NUMBER_FIELD_TAG does not match number field tag. TLR_E_SIII_MA_AP_XML_NUMBER_FIELD_IS_I 0xC0724004L XML structure: Number Field NVALID is invalid. TLR_E_SIII_MA_AP_XML_UNEXPECTED_OPEN 0xC0724005L XML structure: Unexpected ING_TAG_IN_STRING_FIELD opening tag in string field. TLR_E_SIII_MA_AP_XML_UNEXPECTED_SINGL 0xC0724006L XML structure: Unexpected E_TAG_IN_STRING_FIELD single tag in string field. TLR_E_SIII_MA_AP_XML_CLOSING_TAG_DOE 0xC0724007L XML structure: Closing tag S_NOT_MATCH_STRING_FIELD_TAG does not match string field tag. TLR_E_SIII_MA_AP_XML_UNEXPECTED_OPEN 0xC0724008L XML structure: Unexpected ING_TAG_IN_DATA_FIELD opening tag in data field. TLR_E_SIII_MA_AP_XML_UNEXPECTED_SINGL 0xC0724009L XML structure: Unexpected E_TAG_IN_DATA_FIELD single tag in data field. TLR_E_SIII_MA_AP_XML_CLOSING_TAG_DOE 0xC072400AL XML structure: Closing tag S_NOT_MATCH_DATA_FIELD_TAG does not match data field tag. TLR_E_SIII_MA_AP_XML_DATA_FIELD_IS_NOT 0xC072400BL XML structure: Data field is _A_HEX_STRING not a hex string. TLR_E_SIII_MA_AP_XML_UNEXPECTED_OPEN 0xC072400CL XML structure: Unexpected ING_TAG_IN_SIIICFG_BLOCK opening tag in SIIICfg block. TLR_E_SIII_MA_AP_XML_UNEXPECTED_SINGL 0xC072400DL XML structure: Unexpected E_TAG_IN_SIIICFG_BLOCK tag in SIIICfg block. TLR_E_SIII_MA_AP_XML_UNEXPECTED_CLOSI 0xC072400EL XML structure: Unexpected NG_TAG_IN_SIIICFG_BLOCK closing tag in SIIICfg block. TLR_E_SIII_MA_AP_XML_UNEXPECTED_OPEN 0xC072400FL XML structure: Unexpected ING_TAG_TAG_IN_SIIICFG_BLOCK_SLAVE_PA closing tag in SIIICfg block RT (Slave Part). TLR_E_SIII_MA_AP_XML_CLOSING_TAG_DOE 0xC0724010L XML structure: Closing tag S_NOT_MATCH_SIIICFG_TAG does not match SIIICfg tag. More see next page

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Error Numbers • 88

ID of the Error Code Value Description TLR_E_SIII_MA_AP_XML_FILE_IS_NOT_A_SIIIC 0xC0724011L XML structure: XML file does FG_XML not contain a SIIICfg xml. TLR_E_SIII_MA_AP_XML_UNEXPECTED_SINGL 0xC0724012L XML structure: Unexpected tag E_TAG_IN_STD_PARAMS_MASTER_BLOCK in std_params_master block. TLR_E_SIII_MA_AP_XML_STD_PARAMS_MAST 0xC0724013L XML structure: Incomplete ER_BLOCK_IS_INCOMPLETE std_params_master block. TLR_E_SIII_MA_AP_XML_DUPLICATE_TAG_IN_ 0xC0724014L XML structure: Duplicate tag in STD_PARAMS_MASTER_BLOCK std_params_master block. TLR_E_SIII_MA_AP_XML_CLOSING_TAG_DOE 0xC0724015L XML structure: Closing tag does S_NOT_MATCH_STD_PARAMS_MASTER_TAG not match std_params_master tag. TLR_E_SIII_MA_AP_XML_UNEXPECTED_SINGL 0xC0724016L XML structure: Unexpected E_TAG_IN_PARAMS_MASTER_BLOCK single tag in params_master block. TLR_E_SIII_MA_AP_XML_DUPLICATE_TAG_IN_ 0xC0724017L XML structure: Duplicate tag in PARAMS_MASTER_BLOCK params_master block. TLR_E_SIII_MA_AP_XML_UNEXPECTED_OPEN 0xC0724018L XML structure: Unexpected ING_TAG_IN_PARAMS_MASTER_BLOCK opening tag in params_master block. TLR_E_SIII_MA_AP_XML_CLOSING_TAG_DOE 0xC0724019L XML structure: Closing tag does S_NOT_MATCH_PARAMS_MASTER_TAG not match params_master tag. TLR_E_SIII_MA_AP_XML_PARAMS_MASTER_B 0xC072401AL XML structure: Incomplete LOCK_IS_INCOMPLETE params_master block. TLR_E_SIII_MA_AP_XML_UNEXPECTED_OPEN 0xC072401BL XML structure: Unexpected ING_TAG_IN_SYS_IDN_ENTRY_BLOCK opening tag in sys_idn_entry block. TLR_E_SIII_MA_AP_XML_DUPLICATE_TAG_IN_ 0xC072401CL XML structure: Duplicate tag in SYS_IDN_ENTRY_BLOCK sys_idn_entry block. TLR_E_SIII_MA_AP_XML_UNEXPECTED_SINGL 0xC072401DL XML structure: Unexpected E_TAG_IN_SYS_IDN_ENTRY_BLOCK single tag in sys_idn_entry block. TLR_E_SIII_MA_AP_XML_CLOSING_TAG_DOE 0xC072401EL XML structure: Closing tag does S_NOT_MATCH_SYS_IDN_ENTRY_TAG not match sys_idn_entry tag. TLR_E_SIII_MA_AP_XML_SYS_IDN_ENTRY_BL 0xC072401FL XML structure: Incomplete OCK_IS_INCOMPLETE sys_idn_entry block. TLR_E_SIII_MA_AP_XML_UNEXPECTED_OPEN 0xC0724020L XML structure: Unexpected ING_TAG_IN_SYS_GLOBAL_IDNS_BLOCK opening tag in sys_global_idns block. TLR_E_SIII_MA_AP_XML_UNEXPECTED_SINGL 0xC0724021L XML structure: Unexpected E_TAG_IN_SYS_GLOBAL_IDNS_BLOCK single tag in sys_global_idns block. TLR_E_SIII_MA_AP_XML_CLOSING_TAG_DOE 0xC0724022L XML structure: Closing tag does S_NOT_MATCH_SYS_GLOBAL_IDNS_TAG not match sys_global_idns tag. TLR_E_SIII_MA_AP_XML_SYS_GLOBAL_IDNS_ 0xC0724023L XML structure: Incomplete BLOCK_IS_INCOMPLETE sys_global_idns block. TLR_E_SIII_MA_AP_XML_UNEXPECTED_OPEN 0xC0724024L XML structure: Unexpected ING_TAG_IN_MASTER_BLOCK opening tag in master block. TLR_E_SIII_MA_AP_XML_UNEXPECTED_SINGL 0xC0724025L XML structure: Unexpected E_TAG_IN_MASTER_BLOCK single tag in master block. TLR_E_SIII_MA_AP_XML_CLOSING_TAG_DOE 0xC0724026L XML structure: Closing tag does S_NOT_MATCH_MASTER_TAG not match master tag. TLR_E_SIII_MA_AP_XML_MASTER_BLOCK_IS_ 0xC0724027L XML structure: Incomplete INCOMPLETE master block. TLR_E_SIII_MA_AP_XML_DUPLICATE_TAG_IN_ 0xC0724028L XML structure: Duplicate tag in MASTER_BLOCK master block. Table 35: PNIO APCFG Status/Error Codes

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Error Numbers • 89

ID of the Error Code Value Description TLR_E_SIII_MA_AP_XML_UNEXPECTED_SINGL 0xC0724029L XML structure: Unexpected E_TAG_IN_TELEGRAM_ASSIGNMENT_BLOCK single tag in telegram assignment block. TLR_E_SIII_MA_AP_XML_UNEXPECTED_OPEN 0xC072402AL XML structure: Unexpected ING_TAG_IN_TELEGRAM_ASSIGNMENT_BLOC opening tag in telegram K assignment block. TLR_E_SIII_MA_AP_XML_DUPLICATE_TAG_IN_ 0xC072402BL XML structure: Duplicate tag TELEGRAM_ASSIGNMENT_BLOCK in telegram assignment block. TLR_E_SIII_MA_AP_XML_CLOSING_TAG_DOE 0xC072402CL XML structure: Closing tag S_NOT_MATCH_TELEGRAM_ASSIGNMENT_TA does not match telegram G assignment tag. TLR_E_SIII_MA_AP_XML_TELEGRAM_ASSIGN 0xC072402DL XML structure: telegram MENT_IS_INCOMPLETE assignment block is incomplete. TLR_E_SIII_MA_AP_XML_UNEXPECTED_SINGL 0xC072402EL XML structure: Unexpected E_TAG_IN_STD_PARAMS_SLAVE_BLOCK single tag in std_params_slave block. TLR_E_SIII_MA_AP_XML_UNEXPECTED_OPEN 0xC072402FL XML structure: Unexpected ING_TAG_IN_STD_PARAMS_SLAVE_BLOCK opening tag in std_params_slave block. TLR_E_SIII_MA_AP_XML_DUPLICATE_TAG_IN_ 0xC0724030L XML structure: Duplicate tag STD_PARAMS_SLAVE_BLOCK in std_params_slave block. TLR_E_SIII_MA_AP_XML_CLOSING_TAG_DOE 0xC0724031L XML structure: Closing tag S_NOT_MATCH_STD_PARAMS_SLAVE_TAG does not match std_params_slave tag. TLR_E_SIII_MA_AP_XML_STD_PARAMS_SLAV 0xC0724032L XML structure: E_BLOCK_IS_INCOMPLETE std_params_slave block is incomplete. TLR_E_SIII_MA_AP_XML_UNEXPECTED_SINGL 0xC0724033L XML structure: Unexpected E_TAG_IN_PARAMS_SLAVE_BLOCK single tag in params_slave block. TLR_E_SIII_MA_AP_XML_UNEXPECTED_OPEN 0xC0724034L XML structure: Unexpected ING_TAG_IN_PARAMS_SLAVE_BLOCK opening tag in params_slave block. TLR_E_SIII_MA_AP_XML_DUPLICATE_TAG_IN_ 0xC0724035L XML structure: Duplicate tag PARAMS_SLAVE_BLOCK in params_slave block. TLR_E_SIII_MA_AP_XML_CLOSING_TAG_DOE 0xC0724036L XML structure: Closing tag S_NOT_MATCH_PARAMS_SLAVE_TAG does not match params_slave tag. TLR_E_SIII_MA_AP_XML_PARAMS_SLAVE_BL 0xC0724037L XML structure: params_slave OCK_IS_INCOMPLETE block is incomplete. TLR_E_SIII_MA_AP_XML_UNEXPECTED_SINGL 0xC0724038L XML structure: Unexpected E_TAG_IN_SLAVE_BLOCK single tag in slave block. TLR_E_SIII_MA_AP_XML_UNEXPECTED_OPEN 0xC0724039L XML structure: Unexpected ING_TAG_IN_SLAVE_BLOCK opening tag in slave block. TLR_E_SIII_MA_AP_XML_DUPLICATE_TAG_IN_ 0xC072403AL XML structure: Duplicate tag SLAVE_BLOCK in slave block. TLR_E_SIII_MA_AP_XML_CLOSING_TAG_DOE 0xC072403BL XML structure: Closing tag S_NOT_MATCH_SLAVE_TAG does not match slave tag. TLR_E_SIII_MA_AP_XML_SLAVE_BLOCK_IS_IN 0xC072403CL XML structure: slave block is COMPLETE incomplete. TLR_E_SIII_MA_AP_XML_UNEXPECTED_SINGL 0xC072403DL XML structure: Unexpected E_TAG_IN_IDN_ENTRY_DATA_BLOCK single tag in idn_entry block. More see next page

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Error Numbers • 90

ID of the Error Code Value Description TLR_E_SIII_MA_AP_XML_UNEXPECTED_OPEN 0xC072403EL XML structure: Unexpected ING_TAG_IN_IDN_ENTRY_DATA_BLOCK opening tag in idn_entry block. TLR_E_SIII_MA_AP_XML_DUPLICATE_TAG_IN_ 0xC072403FL XML structure: Duplicate tag IDN_ENTRY_DATA_BLOCK in idn_entry block. TLR_E_SIII_MA_AP_XML_CLOSING_TAG_DOE 0xC0724040L XML structure: Closing tag S_NOT_MATCH_IDN_ENTRY_DATA_TAG does not match idn_entry tag. TLR_E_SIII_MA_AP_XML_IDN_ENTRY_BLOCK_ 0xC0724041L XML structure: idn_entry block DATA_IS_INCOMPLETE is incomplete. TLR_E_SIII_MA_AP_XML_IDN_ENTRY_BLOCK_ 0xC0724042L XML structure: idn_entry block HAS_INVALID_ATTRIBUTE has invalid attribute. TLR_E_SIII_MA_AP_XML_IDN_ENTRY_DATA_B 0xC0724043L XML structure: idn_entry block LOCK_HAS_INVALID_DATA has invalid data. TLR_E_SIII_MA_AP_XML_IDN_ENTRY_DATA_B 0xC0724044L XML structure: idn_entry block LOCK_CONTAINS_NON_HEX_DIGIT_CHARACT contains non-hex digit ERS characters. TLR_E_SIII_MA_AP_XML_UNEXPECTED_SINGL 0xC0724045L XML structure: Unexpected E_TAG_IN_IDN_ENTRY_BLOCK single tag in idn_entry block. TLR_E_SIII_MA_AP_XML_UNEXPECTED_OPEN 0xC0724046L XML structure: Unexpected ING_TAG_IN_IDN_ENTRY_BLOCK opening tag in idn_entry block. TLR_E_SIII_MA_AP_XML_DUPLICATE_TAG_IN_ 0xC0724047L XML structure: Duplicate tag IDN_ENTRY_BLOCK in idn_entry block. TLR_E_SIII_MA_AP_XML_CLOSING_TAG_DOE 0xC0724048L XML structure: Closing tag S_NOT_MATCH_IDN_ENTRY_TAG does not match idn_entry tag. TLR_E_SIII_MA_AP_XML_IDN_ENTRY_BLOCK_ 0xC0724049L XML structure: idn_entry block IS_INCOMPLETE is incomplete. TLR_E_SIII_MA_AP_XML_UNEXPECTED_SEQU 0xC072404AL XML structure: Unexpected ENCE_OF_TAGS_IN_IDN_ENTRY_BLOCK sequence of tags in idn_entry block. TLR_E_SIII_MA_AP_XML_UNEXPECTED_SINGL 0xC072404BL XML structure: Unexpected E_TAG_IN_IDN_CONFIG_BLOCK single tag in idn_config block. TLR_E_SIII_MA_AP_XML_UNEXPECTED_OPEN 0xC072404CL XML structure: Unexpected ING_TAG_IN_IDN_CONFIG_BLOCK opening tag in idn_config block. TLR_E_SIII_MA_AP_XML_CLOSING_TAG_DOE 0xC072404DL XML structure: Closing tag S_NOT_MATCH_IDN_CONFIG_TAG does not match idn_config tag. TLR_E_SIII_MA_AP_XML_UNEXPECTED_SINGL 0xC072404EL XML structure: Unexpected E_TAG_IN_CONNECTION_ENTRY_BLOCK single tag in connection_entry block. TLR_E_SIII_MA_AP_XML_UNEXPECTED_OPEN 0xC072404FL XML structure: Unexpected ING_TAG_IN_CONNECTION_ENTRY_BLOCK opening tag in connection_entry block. TLR_E_SIII_MA_AP_XML_DUPLICATE_TAG_IN_ 0xC0724050L XML structure: Duplicate tag CONNECTION_ENTRY_BLOCK in connection_entry block. TLR_E_SIII_MA_AP_XML_CLOSING_TAG_DOE 0xC0724051L XML structure: Closing tag S_NOT_MATCH_CONNECTION_ENTRY_TAG does not match connection_entry tag. TLR_E_SIII_MA_AP_XML_CONNECTION_ENTR 0xC0724052L XML structure: Y_BLOCK_IS_INCOMPLETE connection_entry block is incomplete. More see next page

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Error Numbers • 91

ID of the Error Code Value Description TLR_E_SIII_MA_AP_XML_UNEXPECTED_SINGL 0xC0724053L XML structure: Unexpected E_TAG_IN_CONNECTIONS_BLOCK single tag in connections block. TLR_E_SIII_MA_AP_XML_UNEXPECTED_OPEN 0xC0724054L XML structure: Unexpected ING_TAG_IN_CONNECTIONS_BLOCK opening tag in connections block. TLR_E_SIII_MA_AP_XML_CLOSING_TAG_DOE 0xC0724055L XML structure: Closing tag S_NOT_MATCH_CONNECTIONS_TAG does not match connections tag. TLR_E_SIII_MA_AP_XML_UNEXPECTED_SINGL 0xC0724056L XML structure: Unexpected E_TAG_IN_CONFIG_BLOCK single tag in config block. TLR_E_SIII_MA_AP_XML_UNEXPECTED_OPEN 0xC0724057L XML structure: Unexpected ING_TAG_IN_CONFIG_BLOCK opening tag in config block. TLR_E_SIII_MA_AP_XML_DUPLICATE_TAG_IN_ 0xC0724058L XML structure: Duplicate tag CONFIG_BLOCK in config block. TLR_E_SIII_MA_AP_XML_CLOSING_TAG_DOE 0xC0724059L XML structure: Closing tag S_NOT_MATCH_CONFIG_TAG does not match config tag. TLR_E_SIII_MA_AP_XML_CONFIG_BLOCK_IS_I 0xC072405AL XML structure: config block is NCOMPLETE incomplete. TLR_E_SIII_MA_AP_XML_UNEXPECTED_SEQU 0xC072405BL XML structure: Unexpected ENCE_OF_TAGS_IN_CONFIG_BLOCK sequence of tags in config block. TLR_E_SIII_MA_AP_XML_INVALID_DATA_LENG 0xC072405CL XML structure: Invalid Data TH_OF_SYS_IDN_ENTRY Length of Sys Idn Entry. TLR_E_SIII_MA_AP_XML_DUPLICATE_TAG_IN_ 0xC072405DL XML structure: Duplicate tag SYS_GLOBAL_IDNS_BLOCK in sys_global_idns block. TLR_E_SIII_MA_AP_XML_UNSUPPORTED_IDN 0xC072405EL XML structure: Unsupported _IN_SYS_GLOBAL_IDNS_BLOCK IDN in sys_global_idns block. TLR_E_SIII_MA_AP_XML_INVALID_IDN_DATA_I 0xC072405FL XML structure: Invalid IDN N_SYS_GLOBAL_IDNS_BLOCK data in sys_global_idns block. TLR_E_SIII_MA_AP_XML_INVALID_TELEGRAM 0xC0724060L XML structure: Invalid _NUMBER_IN_TELEGRAM_ASSIGNMENT Telegram Number in Telegram Assignment. TLR_E_SIII_MA_AP_XML_INVALID_TELEGRAM 0xC0724061L XML structure: Invalid _OFFSET_IN_TELEGRAM_ASSIGNMENT Telegram Offset in Telegram Assignment. TLR_E_SIII_MA_AP_XML_INVALID_VALUE_IN_ 0xC0724062L XML structure: Invalid Value ACTIVE_FIELD in Active Field. TLR_E_SIII_MA_AP_XML_INVALID_SERCOS_A 0xC0724063L XML structure: Invalid DDRESS SERCOS Address in Configuration. TLR_E_SIII_MA_AP_XML_INVALID_VALUE_IN_ 0xC0724064L XML structure: Invalid Value HOTPLUG_FIELD in Hot Plug Field. TLR_E_SIII_MA_AP_XML_INVALID_VALUE_IN_ 0xC0724065L XML structure: Invalid Value NRT_SUPPORT_FIELD in NRT Support Field. TLR_E_SIII_MA_AP_XML_IDN_DATA_LENGTH_I 0xC0724066L XML structure: IDN Data NVALID Length invalid. TLR_E_SIII_MA_AP_XML_IDN_PHASE_TRANSI 0xC0724067L XML structure: IDN Phase TION_INVALID Transition invalid. TLR_E_SIII_MA_AP_XML_IDN_ELEMENT_INVA 0xC0724068L XML structure: IDN Element LID invalid. TLR_E_SIII_MA_AP_XML_CONNECTION_NUMB 0xC0724069L XML structure: Connection ER_INVALID Number invalid. More see next page

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Error Numbers • 92

ID of the Error Code Value Description TLR_E_SIII_MA_AP_XML_CONNECTION_TELE 0xC072406AL XML structure: Connection GRAM_OFFSET_INVALID Telegram Offset invalid. TLR_E_SIII_MA_AP_XML_CONNECTION_TELE 0xC072406BL XML structure: Connection GRAM_NUMBER_INVALID Telegram Number invalid. TLR_E_SIII_MA_AP_XML_CONNECTION_TELE 0xC072406CL XML structure: Connection GRAM_TYPE_INVALID Telegram Type invalid. TLR_E_SIII_MA_AP_XML_CONNECTION_LENG 0xC072406DL XML structure: Connection TH_INVALID Length invalid. TLR_E_SIII_MA_AP_XML_CONNECTION_RTDA 0xC072406EL XML structure: Connection TA_DPM_OFFSET_INVALID RtData DPM Offset invalid. TLR_E_SIII_MA_AP_XML_CONNECTION_CCTR 0xC072406FL XML structure: Connection L_DPM_OFFSET_INVALID CCtrl DPM Offset invalid. TLR_E_SIII_MA_AP_XML_INVALID_SEQUENCE 0xC0724070L XML structure: Invalid _OF_TAGS_IN_SIIICFG_BLOCK sequence of tags in SIIICfg Block. Table 36: Status/Error Codes of SERCOS III Master AP Task

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Error Numbers • 93 8.5 ODM Error Codes

8.5.1 General ODM Error Codes

Symbol Value Description CODM3_E_INTERNALERROR 0x8004C700 Internal ODM Error ODM3_E_DESCRIPTION_ NOTFOUND 0x8004C701 Description not found in ODM database CODM3_E_WRITEREGISTRY 0x8004C710 Error writing to the registry CODM3_E_BAD_REGULAR_ EXPRESSION 0x8004C711 Invalid regular expression CODM3_E_COMCATEGORY_ 0x8004C712 Component Category Manager MANAGER_FAILED could not be instantiated CODM3_E_COMCATEGORY_ 0x8004C713 Driver could not be enumerated ENUMERATION_FAILED by the Category Manager CODM3_E_CREATE_LOCAL_BUFFER 0x8004C714 Error creating local buffers CODM3_E_UNKNOWNHANDLE 0x8004C715 Unknown handle CODM3_E_QUEUE_LIMIT_ REACHED 0x8004C717 Queue size limit for connection reached CODM3_E_DATASIZE_ZERO 0x8004C718 Zero data length passed CODM3_E_INVALID_DATA 0x8004C719 Invalid data content CODM3_E_INVALID_MODE 0x8004C71A Invalid mode CODM3_E_DATABASE_READ 0x8004C71B Error reading database CODM3_E_CREATE_DEVICE_THREAD 0x8004C750 Error creating device thread CODM3_E_CREATE_DEVICE_ 0x8004C751 Error creating device thread stop 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_ 0x8004C754 Maximum number of client CONNECTIONS_REACHED connections 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 Process is not registered as a server on this device CODM3_E_DEVICE_ NO_MESSAGE 0x8004C75D No message available CODM3_E_TRANSFER TIMEOUT 0x8004C760 Message transfer timeout CODM3_E_MESSAGE_ INSERVICE 0x8004C761 Message in service Table 37: ODM Error Codes - General ODM Error Codes

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Error Numbers • 94 8.5.2 General ODM Driver Error Codes

Symbol 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_ 0x8004C7A3 Parameters differ from requested PARAMETERS_MISMATCH device CODM3_E_DRV_BROWSE_ NO_DEVICES 0x8004C7A4 No devices found CODM3_E_DRV_CREATE_ DEVICE_INST 0x8004C7A5 Device instance could not be created CODM3_E_DRV_DEVICE_ NOMORE_TX 0x8004C7A6 Device connection limit reached CODM3_E_DRV_DEVICE_ DUPLICATE_TX 0x8004C7A7 Duplicate transmitter ID CODM3_E_DRV_DEVICE_ NOT_CONFIGURED 0x8004C7A8 Device is not configured CODM3_E_DRV_DEVICE_ COMMUNICATION 0x8004C7A9 Device communication error CODM3_E_DRV_DEVICE_ NO_MESSAGE 0x8004C7AA No message available CODM3_E_DRV_DEVICE_ NOT_READY 0x8004C7AB Device not ready CODM3_E_DRV_INVALID CONFIGURATION 0x8004C7AC Invalid driver configuration CODM3_E_DRV_DLINVALID MODE 0x8004C7C0 Invalid download mode CODM3_E_DRV_DLIN PROGRESS 0x8004C7C1 Download is active CODM3_E_DRV_ULIN PROGRESS 0x8004C7C2 Upload is active Table 38: ODM Error Codes - General ODM Driver Error Codes

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Error Numbers • 95 8.5.3 ODM cifX Driver Specific Errors

ID of the Error Code Value DESCRIPTION DRV_E_BOARD_NOT_ INITIALIZED 0x8004C001 DRIVER Board not initialized DRV_E_INIT_STATE_ ERROR 0x8004C002 DRIVER Error in internal init state DRV_E_READ_STATE_ ERROR 0x8004C003 DRIVER Error in internal read state DRV_E_CMD_ACTIVE 0x8004C004 DRIVER Command on this channel is activ 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 mode 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 0x8004C00C DEVICE Not running (running flag failed) DRV_E_DEV_WATCHDOG_ FAILED 0x8004C00D DEVICE Watchdog test failed DRV_E_DEV_OS_VERSION_ ERROR 0x8004C00E DEVICE Signals wrong OS version DRV_E_DEV_SYSERR 0x8004C00F DEVICE Error in dual port flags DRV_E_DEV_MAILBOX_ FULL 0x8004C010 DEVICE Send mailbox is full DRV_E_DEV_PUT_ TIMEOUT 0x8004C011 DEVICE PutMessage timeout DRV_E_DEV_GET_ TIMEOUT 0x8004C012 DEVICE GetMessage timeout DRV_E_DEV_GET_ NO_MESSAGE 0x8004C013 DEVICE No message available DRV_E_DEV_RESET_ TIMEOUT 0x8004C014 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 0x8004C016 DEVICE I/O data exchange failed DRV_E_DEV_EXCHANGE_ TIMEOUT 0x8004C017 DEVICE I/O data exchange timeout DRV_E_DEV_COM_MODE_ UNKNOWN 0x8004C018 DEVICE I/O data mode unknown DRV_E_DEV_FUNCTION_ FAILED 0x8004C019 DEVICE Function call failed DRV_E_DEV_DPMSIZE_ 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 More see next page Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Error Numbers • 96

ID of the Error Code Value Description DRV_E_USR_NOT_ INITIALIZED 0x8004C020 USER Board not initialized (DevInitBoard not called) DRV_E_USR_COMM_ ERR 0x8004C021 USER IOCTRL function failed DRV_E_USR_DEV_ NUMBER_INVALID 0x8004C022 USER Parameter DeviceNumber invalid DRV_E_USR_INFO_AREA_ INVALID 0x8004C023 USER Parameter InfoArea unknown DRV_E_USR_NUMBER_ INVALID 0x8004C024 USER Parameter Number invalid DRV_E_USR_MODE_ INVALID 0x8004C025 USER Parameter Mode invalid DRV_E_USR_MSG_BUF_ NULL_PTR 0x8004C026 USER NULL pointer assignment DRV_E_USR_MSG_BUF_ TOO_SHORT 0x8004C027 USER Message buffer too small DRV_E_USR_SIZE_ INVALID 0x8004C028 USER Parameter Size invalid DRV_E_USR_SIZE_ ZERO 0x8004C02A USER Parameter Size with zero length DRV_E_USR_SIZE_ TOO_LONG 0x8004C02B USER Parameter Size too long DRV_E_USR_DEV_ PTR_NULL 0x8004C02C USER Device address null pointer DRV_E_USR_BUF_ PTR_NULL 0x8004C02D USER Pointer to buffer is a null pointer DRV_E_USR_SENDSIZE_ TOO_LONG 0x8004C02E USER Parameter SendSize too large DRV_E_USR_RECVSIZE_ TOO_LONG 0x8004C02F 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 0x8004C032 DMA Memory allocation error DRV_E_DMA_TIMEOUT_CH4 0x8004C033 DMA Read I/O timeout DRV_E_DMA_TIMEOUT_CH5 0x8004C034 DMA Write I/O timeout DRV_E_DMA_TIMEOUT_CH6 0x8004C035 DMA PCI transfer timeout DRV_E_DMA_TIMEOUT_CH7 0x8004C036 DMA Download timeout DRV_E_DMA_DB_DOWN_FAIL 0x8004C037 DMA Database download failed DRV_E_DMA_FW_DOWN_FAIL 0x8004C038 DMA Firmware download failed DRV_E_CLEAR_DB_FAIL 0x8004C039 DMA Clear database on the device failed DRV_E_DEV_NO_VIRTUA L_MEM 0x8004C03C DMA USER Virtual memory not available DRV_E_DEV_UNMAP_ VIRTUAL_MEM 0x8004C03D DMA USER Unmap virtual memory failed DRV_E_GENERAL_ERROR 0x8004C046 DRIVER General error DRV_E_DMA_ERROR 0x8004C047 DRIVER General DMA error DRV_E_WDG_IO_ERROR 0x8004C048 DRIVER I/O WatchDog failed DRV_E_WDG_DEV_ ERROR 0x8004C049 DRIVER Device Watchdog failed DRV_E_USR_DRIVER_ UNKNOWN 0x8004C050 USER Driver unknown DRV_E_USR_DEVICE_ NAME_INVALID 0x8004C051 USER Device name invalid DRV_E_USR_DEVICE_ NAME_UKNOWN 0x8004C052 USER Device name unknown More see next page

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Error Numbers • 97

ID of the Error Code Value DESCRIPTION DRV_E_USR_DEVICE_ FUNC_NOTIMPL 0x8004C053 USER Device function not implemented DRV_E_USR_FILE_OPEN _FAILED 0x8004C064 USER File could not be opened DRV_E_USR_FILE_SIZE_ ZERO 0x8004C065 USER File size zero DRV_E_USR_FILE_NO_ MEMORY 0x8004C066 USER Not enough memory to load file DRV_E_USR_FILE_READ_ AILED 0x8004C067 USER File read failed DRV_E_USR_INVALID_ FILETYPE 0x8004C068 USER File type invalid DRV_E_USR_FILENAME_ INVALID 0x8004C069 USER Invalid filename DRV_E_FW_FILE_OPEN_ FAILED 0x8004C06E 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 0x8004C071 USER Firmware file read failed DRV_E_FW_INVALID_ FILETYPE 0x8004C072 USER Firmware file type invalid DRV_E_FW_FILENAME_ INVALID 0x8004C073 USER Firmware file name not valid DRV_E_FW_DOWNLOAD_ ERROR 0x8004C074 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 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_READ_ FAILED 0x8004C07B USER Configuration file read failed DRV_E_CF_INVALID_FILETYPE 0x8004C07C USER Configuration file type invalid DRV_E_CF_FILENAME_ INVALID 0x8004C07D USER Configuration file name not valid DRV_E_CF_DOWNLOAD_ ERROR 0x8004C07E USER Configuration file download error 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_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

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Error Numbers • 98 More see next page

ID of the Error Code Value DESCRIPTION DEV_E_CF_INVALID_INPUT_ OFFSET 0x8004C097 CONFIG Input offset is invalid DEV_E_CF_NO_INPUT_SIZE 0x8004C098 CONFIG Input size is 0 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 0x8004C09F CONFIG Module definition is missing DEV_E_CF_MISMATCH_ EMPTY_SLOT 0x8004C0A0 CONFIG Empty slot mismatch DEV_E_CF_MISMATCH_ INPUT_OFFSET 0x8004C0A1 CONFIG Input offset mismatch DEV_E_CF_MISMATCH_ OUTPUT_OFFSET 0x8004C0A2 CONFIG Output offset mismatch DEV_E_CF_MISMATCH_ DATA_TYPE 0x8004C0A3 CONFIG Data type mismatch DEV_E_CF_MODULE_ DEF_MISSING_NO_SI 0x8004C0A4 CONFIG Module definition is missing,(no Slot/Idx) Table 39: ODM CifX Driver Specific Errors

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Error Numbers • 99 8.6 Error Codes cifX Device Driver

Note: The cifX Device Driver is not available for all devices.

ID of the Error Code Value Description CIFX_NO_ERROR 0x00000000 no error CIFX_INVALID_POINTER 0x800A0001 An invalid pointer (NULL) was passed to the function CIFX_INVALID_BOARD 0x800A0002 No board with the given name / index available CIFX_INVALID_CHANNEL 0x800A0003 No channel with the given index is available CIFX_INVALID_HANDLE 0x800A0004 An invalid handle was passed to the function CIFX_INVALID_PARAMETER 0x800A0005 Invalid parameter passed to function CIFX_INVALID_COMMAND 0x800A0006 Command parameter is invalid CIFX_INVALID_BUFFERSIZE 0x800A0007 The supplied buffer does not match the expected size CIFX_INVALID_ACCESS_SIZE 0x800A0008 Invalid Access Size (e.g. IO Area is exceeded by Offset and size) CIFX_FUNCTION_FAILED 0x800A0009 Generic Function failure CIFX_FILE_OPEN_FAILED 0x800A000A A file could not be opened CIFX_FILE_SIZE_ZERO 0x800A000B File size is zero CIFX_FILE_LOAD_INSUFF_MEM 0x800A000C Insufficient memory to load file CIFX_FILE_READ_ERROR 0x800A000E Error reading file data CIFX_FILE_TYPE_INVALID 0x800A000F The given file is invalid for the operation CIFX_FILE_NAME_INVALID 0x800A0010 Invalid filename given CIFX_FUNCTION_NOT_ AVAILABLE 0x800A0011 Function is not available on the driver CIFX_BUFFER_TOO_SHORT 0x800A0012 The passed buffer is too short, to fit the device data CIFX_MEMORY_MAPPING_ FAILED 0x800A0013 Error mapping dual port memory

CIFX_DRV_NOT_INITIALIZED 0x800B0001 Driver not initialized CIFX_DRV_INIT_STATE_ ERROR 0x800B0002 Driver init state error CIFX_DRV_READ_STATE_ ERROR 0x800B0003 Driver read state error CIFX_DRV_CMD_ACTIVE 0x800B0004 Command is active on device CIFX_DRV_DOWNLOAD_ FAILED 0x800B0005 General error during download CIFX_DRV_WRONG_DRIVER _VERSION 0x800B0006 Wrong driver version

CIFX_DRV_DRIVER_NOT _LOADED 0x800B0030 CIFx driver is not running CIFX_DRV_INIT_ERROR 0x800B0031 Failed to initialize the device CIFX_DRV_CHANNEL_ NOT_INITIALIZED 0x800B0032 Channel not initialized (xOpenChannel() not called) More see next page

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Error Numbers • 100

ID of the Error Code Value Description CIFX_DRV_IO_CONTROL _FAILED 0x800B0033 IOControl call failed CIFX_DRV_NOT_OPENED 0x800B0034 Driver was not opened

CIFX_DEV_DPM_ACCESS _ERROR 0x800C0010 Dual port memory not accessable (board not found) CIFX_DEV_NOT_READY 0x800C0011 Device not ready (ready flag failed) CIFX_DEV_NOT_RUNNING 0x800C0012 Device not running (running flag failed) CIFX_DEV_WATCHDOG _FAILED 0x800C0013 Watchdog test failed CIFX_DEV_SYSERR 0x800C0015 Error in handshake flags CIFX_DEV_MAILBOX_FULL 0x800C0016 Send mailbox is full CIFX_DEV_PUT_TIMEOUT 0x800C0017 Send packet timeout CIFX_DEV_GET_TIMEOUT 0x800C0018 Receive packet timeout CIFX_DEV_GET_NO _PACKET 0x800C0019 No packet available CIFX_DEV_RESET _TIMEOUT 0x800C0020 Reset command timeout CIFX_DEV_NO_COM _FLAG 0x800C0021 Communication flag not set CIFX_DEV_EXCHANGE _FAILED 0x800C0022 I/O data exchange failed CIFX_DEV_EXCHANGE _TIMEOUT 0x800C0023 I/O data exchange timeout CIFX_DEV_COM_MODE _UNKNOWN 0x800C0024 Unknown I/O exchange mode CIFX_DEV_FUNCTION _FAILED 0x800C0025 Device function failed CIFX_DEV_DPMSIZE _MISMATCH 0x800C0026 DPM size differs from configuration CIFX_DEV_STATE_ MODE_UNKNOWN 0x800C0027 Unknown state mode CIFX_DEV_HW_PORT _IS_USED 0x800C0028 Output port already in use CIFX_DEV_CONFIG_ LOCK_TIMEOUT 0x800C0029 Configuration locking timeout CIFX_DEV_CONFIG_ UNLOCK_TIMEOUT 0x800C002A Configuration unlocking timeout CIFX_DEV_HOST_STATE _SET_TIMEOUT 0x800C002B Set HOST state timeout CIFX_DEV_HOST_STATE _CLEAR_TIMEOUT 0x800C002C Clear HOST state timeout CIFX_DEV_INITIALIZATION _TIMEOUT 0x800C002D Timeout during channel initialization Table 40: Error Codes cifX Device Driver

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Error Numbers • 101 8.7 ODM DBM V4 Error Codes

ID of the Error Code Value Description CDBM_E_MD5_INVALID 0XC004C810 Checksum invalid CDBM_E_INTERNALERROR 0XC004C811 Internal Error CDBM_W_WRITEREGISTRY 0X8004C812 Error writing to the registry CDBM_E_UNEXPECTED_VALUE 0XC004C813 Error in a file containing the _IN_OLD_HEADER_FORMAT old DBM Header format. CDBM_E_CHECKSUM_INVALID 0XC004C814 The Checksum of the old Header is invalid CDBM_E_DB_ALREADY_LOADED _FORMAT 0XC004C815 A database is already loaded CDBM_E_NO_VALID_TRANSACTION 0XC004C816 No valid transaction handle given CDBM_E_STD_STRUCT_ ERROR 0XC004C817 An error occured during validation of data CDBM_E_UNSUPPORTED _DATA_TYPE_ 0XC004C818 Unsupported DataType FORMAT CDBM_W_CLASS_DELETED _FORMAT 0X8004C819 Using an Object which is (Warning) marked as deleted CDBM_W_CLIENT_ DISCONNECTED 0X8004C81A A Client has already an (Warning) 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 0XC004C81C 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 Toggle string found for this number CDBM_E_ELEMENT_OUT_ OF_RANGE 0XC004C81F An element wasn’t found in the Record of a Table CDBM_E_ELEMENT_NOT _IN_TABLE 0XC004C820 The element is not part of the Table CDBM_E_CANNOT_CONVERT 0XC004C821 The data can't be converted _INTO_CLIENT_TYPE into the Client type CDBM_E_TRANSACTION_ ALREADY_OPEN 0XC004C822 A transaction is already open. Please close this one first before opening a new one. CDBM_I_OLD_WITHOUT_ HEADER 0X4004C823 Use of an old DBM file Format (Informational) without Header CDBM_E_HR_FROM 0XC004C824 An HRESULT was received from a Subroutine CDBM_E_PARAMETER 0XC004C825 A Parameter is invalid CDBM_E_NOTIMPL 0XC004C826 Method is currently not implemented CDBM_E_OUTOFMEMORY 0XC004C827 Out of memory CDBM_E_NO_OPEN_ TRANSACTION 0XC004C828 No transaction open CDBM_E_NO_CONTENTS 0XC004C829 No contents available CDBM_REC_NO_NOT_ FOUND 0XC004C82A Record not found CDBM_STRUCTURE_ELEMENT _NOT_FOUND 0XC004C82B Element of the Structure not found More see next page Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Error Numbers • 102

ID of the Error Code Value Description CDBM_E_NO_MORE_RECORDS 0XC004C82C Table type 3 can contain only _IN_TABTYPE one record CDBM_E_WRITE 0XC004C82D The data in the VARIANT must be given in a SafeArray CDBM_E_WRITE_NO_PARRAY 0XC004C82E The VARIANT contains no valid [parray] element CDBM_E_WRITE_CANT_ACCESS_DATA 0XC004C82F 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_I1 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_UI1 or VT_I1. 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_ 0XC004C83B It's not allowed to change the STRUCTURE_WHILE_ RECORDS_EXIST structure while Records exist in the Table CDBM_NEW_STRUCT_ NEEDS_TYPE 0XC004C83C In a newly added structure the data type must be set also CDBM_VALUE_ERROR 0XC004C83D Range error while validating a value CDBM_DATATYPE_UNSUPPORTED_IN_RCS 0XC004C83E The data type is unsupported in the RCS file format CDBM_I_COUNT_OF_TABLES_EXCEEDS_ 0X4004C83F The count of Tables exceeds RCS_RANGE (Informational) the RCS range of Tables. This can cause problems if the file is downloaded to RCS Systems More see next page

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Error Numbers • 103

ID of the Error Code Value Description CDBM_I_COUNT_OF_TABLES 0X4004C840 The count of Tables exceeds _EXCEEDS_OLDDBM_RANGE (Informational) the 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 _IN_RCS_MODE compatible with the old database format CDBM_WRITE_UNSTRUC TURED_1 0XC004C842 The data of an unstructured record can only be written with the 'Write' Method not with 'WriteElement'. CDBM_READ_UNSTRUC TURED_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 0XC004C845 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 0XC004C847 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 CDBM_ERROR_FROM_VAR _CHANGE_TYPE 0XC004C848 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 0XC004C84B 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_ 0XC004C850 The toggle string for this IS_EMPTY_STRING value is empty. CDBM_VARIANT2BYTEARRAY _ERROR 0XC004C851 Error during conversion of Variant to byte array

More see next page

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Error Numbers • 104

ID of the Error Code Value Description CDBM_E_SET_ELEM_ PROP_DEPENDENCY 0XC004C852 The Toggle Type needs also the additional string and the additional number entrys in the Method SetElementProperties CDBM_E_TABTYPE1_REC_ 0XC004C853 When reading the records of DOESNT_CORRESPOND_ WITH_ELEMENT Table type 1 elementwise the record number must correspond with the element number CDBM_TABTYPE1_NO_DATA_ 0XC004C854 When reading the records of FOUND_FOR_RECORD Table type 1 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 ELEMENT_NE_RECORD Table type 1 elementwise and structure definitions are present it's only allowed to write the corresponding element number in each record CDBM_E_TABTYPE1_WRITE_ 0XC004C856 When writing the records of ELEMENT_NOT_FOUND Table type 1 with an array and structure definitions are present it's assumed that a corresponding element number of this record exist CDBM_I_TABLE_NAME_ 0X4004C857 The Table name exceeds the EXCEEDS_RCS_RANGE (Informational) maximum length of RCS compatible Table names CDBM_W_CUT_STRING 0X8004C858 The string exceeds the (Warning) maximum length and will be limited to the maximum length CDBM_I_STRING_TOO_ SHORT 0X4004C859 The string is below the (Informational) minimum length. The minimum length will be reduced. CDBM_I_STRING_TOO_ LONG 0X4004C85A The string is exceeding the (Informational) maximum. The maximum length will be extended. CDBM_E_STRING_TOO_ SHORT 0XC004C85B The string is below the (Error) minimum length. CDBM_E_STRING_TOO_ LONG 0XC004C85C The string is exceeding the (Error) maximum length CDBM_E_WRONG_TYPE_ FOR_WRITE 0XC004C85D Writing on the Element type with the given Data type is not implemented CDBM_E_NO_APPEND_IN_ 0XC004C85E Method STRUCTURED_RECORDS IDbmRecord::AppendData is not allowed for structured records CDBM_E_DATA_ UNAVAILABLE 0XC004C85F No data available CDBM_E_CANT_ CONVERT_INTO 0XC004C860 Unable to convert the value into the Element type More see next page

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Error Numbers • 105

ID of the Error Code Value Description CDBM_E_DBM_FILE_ OVERFLOW 0XC004C861 You try to write a RCS like database which needs too mutch 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 0XC004C864 Error in the file. CDBM_E_MD5SUM_ INVALID 0XC004C865 MD5 sum invalid CDBM_E_STRUCT_ LENGTH 0XC004C866 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_ 0XC004C86A A Table without structure TABLE_DOESNT_SUPPORT _LENGTH information doesn’t support a record length CDBM_E_DISABLED_WHILE_ TRANSACTION_ 0XC004C86B The Method is disabled while IS_OPEN a transaction is open. Please close this one first and call the Method again. CDBM_E_UNABLE_TO_CALL_ 0XC004C86C The Method is disabled on a READ_ON_LINKED_LIST LinkedList type. Please use the IRecordCollection on this type. CDBM_E_ELEMENT_HAS_ 0XC004C86D An Element from a Table has NO_SUBSTRUCTURE no substructure CDBM_STRUCT_ERROR_ 0XC004C86E Error from calling FROM_VAR_CHANGE_TYPE VariantChangeType CDBM_E_FOREIGNKEY_DEF 0XC004C86F 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 'eDbmTableTypeLinkedList' 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 'eDbmTableTypeLinkedList' CDBM_DATATYPE_NOT_ IMPLEMENTED 0XC004C873 This data type is currently not implemented More see next page

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Error Numbers • 106

ID of the Error Code Value Description CDBM_INSERT_POS_ NOT_FOUND 0XC004C874 The position of the Record where the new one should be inserted wasn’t found CDBM_E_INSERT_REC_QI 0XC004C875 Error during insertion of a Record CDBM_E_TAB_PROP 0XC004C876 Invalid Property in Table CDBM_E_KEY_NOT_FOUND 0XC004C877 The KEY wasn’t found in the Table CDBM_E_KEY_INVALID 0XC004C878 The KEY is invalid for this operation Table 41: ODM DBM V4 Error Codes

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Glossary • 107 9 Glossary

AT Acknowledge Telegram (originally Antriebstelegramm which is the German expression for “Drive Telegram”)) The Acknowledge Telegram (AT) is a special telegram used for transmission of real-time data from the slaves to the master and to other slave devices (if cross communication is used). The format of the AT is predefined within the SERCOS III specification.

DTM Device Type Manager The Device Type Manager (DTM) is a software module with graphical user interface for the configuration and/or for diagnosis of devices. FDT Field Device Tool FDT specifies an interface, in order to be able to use DTM (Device Type Manager) in different applications of different manufacturers. Master SERCOS III Master devices initiate the data traffic on the bus. In the SERCOS III protocol Master devices are called active participants. A master may send messages without external request. MDT Master Data Telegram The Master Data Telegram (MDT) is a special telegram used for transmission of real-time data from the master to the slaves. The format of the MDT is predefined within the SERCOS III specification.

SDDML SDDML = SERCOS III Device Description Markup Language SERCOS III

Slave Slave devices are peripheral devices, like for example I/O devices or drives. Slave devices are also called passive participants. They do not receive the bus access authorization. That means, they may only accept received messages from the Master or send a message to the Master after enquiry of the Master.

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Lists • 108 10 Lists 10.1 List of Figures Figure 1: Dialog Structure of SERCOS III Master DTM 12 Figure 2: Navigation Area 13 Figure 3: Status Bar – Status Fields 1 to 6 16 Figure 4: Navigation Area - Settings 23 Figure 5: Driver Selection List 24 Figure 6: Driver Selection List - recognized or installed Drivers 24 Figure 7: Driver Selection List - Driver/s selected 24 Figure 8: Navigation Area – Settings 25 Figure 9: Device Assignment - detected Devices (* The name of the device class is displayed.) – Example for a device without firmware 28 Figure 10: Device Assignment - detected Devices (* The name of the device class is displayed.) Example for Devices without Firmware 30 Figure 11: Device Assignment - Selecting the Device (* The name of the device class is displayed.) – Example for a device without firmware / one Device is selected 31 Figure 12: Device Assignment - Selecting the Device (* The name of the device class is displayed.) – Example for Devices with and without Firmware / one Device is selected 32 Figure 13: Device Assignment - Selecting the Device (* The name of the device class is displayed.) – Example for a device with firmware / one Device is selected 33 Figure 14: Firmware Download 34 Figure 15: Selection Window Select Firmware File 35 Figure 16: Request Select Firmware File - Example 36 Figure 17: Firmware Download – Download 37 Figure 18: Firmware-Download – Question) 37 Figure 19: Clock Symbol and Hook Symbol green 38 Figure 20: Clock Symbol and Hook Symbol green 38 Figure 21: Navigation Area - Configuration 39 Figure 22: Configuration > General Settings (*The current device name is displayed.) 40 Figure 23: Master Settings 41 Figure 24: Master Settings > Start of Bus Communication 42 Figure 25: Master Settings > Application Monitoring 42 Figure 26: Master Settings > Process Image Storage Format 43 Figure 27: Master Settings > Module Alignment 43 Figure 28: Master Settings > Process Data Handshake 44 Figure 29: Configuration > General Settings (*The current device name is displayed.) 45 Figure 30: Process Data 47 Figure 31: Configuration > Address Table (In the Figure shown here, in the column Device or Name example devices are displayed.) 48 Figure 32: Configuration > Address Table - Auto Addressing 49 Figure 33: Configuration > Address Table - Display Mode 49 Figure 34: Navigation Area - Diagnosis 50 Figure 35: Firmware Diagnosis (*The name of the Firmware is displayed.) 51 Figure 36: General Diagnosis 52 Figure 37: Master Diagnosis 55 Figure 38: Navigation Area - Additional Tools 56 Figure 39: Packet Monitor 57 Figure 40: Packet Header and Send Data 59 Figure 41: Packet Header and Receive Data 60 Figure 42: IO Monitor 61 Figure 43: Hardware Devices found by Network Scan Function 65 Figure 44: License Pane 68 Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Lists • 109 Figure 45: Example: ordering E Mail License request 73 Figure 46: Example: order data form netX License Order Form 74

10.2 List of Tables Table 1: Descriptions Dialog Panes 5 Table 2: General Device Information 13 Table 3: Hide / display Navigation 13 Table 4: Overview Dialog Panes 14 Table 5: General Buttons 15 Table 6: Table Line – Buttons 15 Table 7: Status Bar Icons [1] 17 Table 8: Getting Started - Configuration Steps 20 Table 9: Descriptions Settings 23 Table 10: Driver Selection List Parameters 24 Table 11: Parameters of the Device Assignment 29 Table 12: Parameter Firmware Download 34 Table 13: Parameters Select Firmware File 35 Table 14: Descriptions of the Dialog Panes Configuration 39 Table 15: Configuration > General - Settings 40 Table 16: Range of Value / Value for the Watchdog time 42 Table 17: Master Settings Pane Parameters - Process Image Storage Format 43 Table 18: Parameters Master Settings > Module Alignment 43 Table 19: Process Data 47 Table 20: Descriptions of the Diagnosis Panes 50 Table 21: Description Table Task Information 51 Table 22: Indication General Diagnosis 53 Table 23: Parameter General Diagnosis 54 Table 24: Parameter Master Diagnosis 55 Table 25: Descriptions of the Diagnosis Panes 56 Table 26: Descriptions Packet Header 58 Table 27: Display for Network Scan – Table above 65 Table 28: Error Code Regions 77 Table 29: RCX Errors - MID_SYS Task Error Codes (from Operating System) 79 Table 30: RCX Errors - Common Status Codes (from Operating System) 80 Table 31: RCX Errors - Status & Error Codes (from Operating System) 81 Table 32: RCX Errors - Status & Error Codes – Slave State (from Operating System) 81 Table 33: Status/Error Codes of SERCOS III Master CP Task 85 Table 34: Status/Error Codes of SERCOS III Master SVC Task 86 Table 35: PNIO APCFG Status/Error Codes 88 Table 36: Status/Error Codes of SERCOS III Master AP Task 92 Table 37: ODM Error Codes - General ODM Error Codes 93 Table 38: ODM Error Codes - General ODM Driver Error Codes 94 Table 39: ODM CifX Driver Specific Errors 98 Table 40: Error Codes cifX Device Driver 100 Table 41: ODM DBM V4 Error Codes 106 Table 42: Settings (D = Displaying, X = Editing, Configuring) 110 Table 43: Configuration (D = Displaying, X = Editing, Configuring) 110

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Appendix • 110 11 Appendix 11.1 User Rights User-rights are set within the FDT-container. Depending on the level the configuration is accessible by the user or read-only. To access the Settings, Configuration and Diagnosis panes of the SERCOS III Master DTM you do not need special user rights. Also all users can select the decimal or hexadecimal Display mode or sort table entries.

Note: To edit, set or configure the parameters of the Settings and Configuration panes, you need user rights for Maintenance, for Planning Engineer or for Administrator.

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

Observer Operator Maintenanc Planning Adminis- e Engineer trator Driver D D X X X Selecting the Driver - - X X X Configuring the Driver - - X X X Device Assignment D D X X X Scanning for Devices - - X X X Selecting the Device (with or - - X X X without firmware) Selecting the Device once more - - X X X (with Firmware) Firmware Download D D X X X Table 42: Settings (D = Displaying, X = Editing, Configuring)

11.1.2 Configuration

Observer Operator Maintenanc Planning Adminis- e Engineer trator General Settings D D X X X Master Settings D D X X X Slave Table D D X X X Process Data D D X X X Address Table D D X X X Table 43: Configuration (D = Displaying, X = Editing, Configuring)

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Appendix • 111 11.2 References

[1] Device Type Manager (DTM) Style Guide, Version 1.0 ; FDT-JIG - Order No. <0001-0008-000> [2] SERCOS III Master Protocol API, Hilscher 2008-2009 [3] SERCOS III Communication V1.1.1.5, SERCOS International 2007

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta SERCOS III Master DTM Appendix • 112 11.3 Contacts

Headquarter

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: [email protected] Support Phone: +49 (0) 6190 9907-99 E-Mail: [email protected]

Subsidiaries

China Japan Hilscher Ges.f.Systemaut. mbH Hilscher Japan KK Shanghai Representative Office Tokyo, 160-0022 200010 Shanghai Phone: +81 (0) 3-5362-0521 Phone: +86 (0) 21-6355-5161 E-Mail: [email protected] E-Mail: [email protected] Support Support Phone: +81 (0) 3-5362-0521 Phone: +86 (0) 21-6355-5161 E-Mail: [email protected] E-Mail: [email protected]

Switzerland France Hilscher Swiss GmbH Hilscher France S.a.r.l. 4500 Solothurn 69500 Bron Phone: +41 (0) 32 623 6633 Phone: +33 (0) 4 72 37 98 40 E-Mail: [email protected] E-Mail: [email protected] Support Support Phone: +49 (0) 6190 9907-99 Phone: +33 (0) 4 72 37 98 40 E-Mail: [email protected] E-Mail: [email protected]

India USA Hilscher India Pvt. Ltd. Hilscher North America, Inc. 504, 5th Floor,Elegance Tower, Mathura Road Lisle, IL 60532 Jasola District Centre Phone: +1 630-505-5301 New Delhi – 110 025 E-Mail: [email protected] Phone: +91 (91) 9810269248 Support E-Mail: [email protected] Phone: +1 630-505-5301 E-Mail: [email protected] Italy Hilscher Italia srl 20090 Vimodrone (MI) Phone: +39 02 25007068 E-Mail: [email protected] Support Phone: +39 / 02 25007068 E-Mail: [email protected]

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim Edition 1– Oi:DTMS3MX#EN – 2009/05 Beta