netSLAVE DTM

Transcription

netSLAVE DTM

Operating Instruction Manual
netSLAVE DTM for Hilscher NETX Slave Devices
Configure Hilscher Slave Devices
Language: English (EN)
www.hilscher.com
Table of Contents • 2
netSLAVE DTM
Table of Contents
1
INTRODUCTION.........................................................................................................5
1.1
About this Manual .......................................................................................................5
1.1.1
1.1.2
1.1.3
1.2
Legal Notes.................................................................................................................8
1.2.1
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.3
Configuration Steps ..................................................................................................17
2.1.1
Setting Driver and Selecting Device...................................................................19
SETTINGS ................................................................................................................20
3.1
Overview Settings.....................................................................................................20
3.2
Driver ........................................................................................................................21
3.2.1
3.2.2
3.2.3
3.3
Selecting the Driver ............................................................................................21
Configuring the Driver ........................................................................................22
cifX Device Driver ...............................................................................................22
Device Assignment ...................................................................................................23
3.3.1
3.3.2
4
General Device Information................................................................................13
Navigation Area ..................................................................................................13
Dialog Pane ........................................................................................................14
Controls and Dialog Buttons...............................................................................15
Status Bar...........................................................................................................16
GETTING STARTED.................................................................................................17
2.1
3
Requirements .....................................................................................................11
Dialog Structure of the netSLAVE DTM....................................................................12
1.4.1
1.4.2
1.4.3
1.4.4
1.4.5
2
Copyright ..............................................................................................................8
Important Notes ....................................................................................................8
Exclusion of Liability .............................................................................................9
Warranty ...............................................................................................................9
Export Regulations .............................................................................................10
Registered Trademarks......................................................................................10
About netSLAVE DTM ..............................................................................................11
1.3.1
1.4
Online Help...........................................................................................................6
List of Revisions ...................................................................................................6
Conventions in this Manual ..................................................................................7
Scanning for Devices .........................................................................................23
Selecting the Device (with firmware) ..................................................................24
CONFIGURATION ....................................................................................................25
4.1
Overview Configuration ............................................................................................25
4.1.1
4.2
Parameters of the Protocol – Overview Configuration Parameters ...................26
Real-Time Ethernet Systems ....................................................................................27
4.2.1
4.2.2
4.2.3
EtherCAT Slave Parameters ..............................................................................27
EtherNet/IP Adapter Parameters........................................................................29
Open Modbus/TCP Parameters .........................................................................32
Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D 65795 Hattersheim
Edition 7 – Oi:DTMNSL#EN – 2009/05
netSLAVE DTM
4.2.4
4.2.5
4.2.6
4.3
6
Powerlink Controlled Node/Slave Parameters ...................................................34
PROFINET IO-Device Parameters.....................................................................36
SERCOS III Slave Parameters...........................................................................38
Fieldbus Systems .....................................................................................................39
4.3.1
4.3.2
4.3.3
4.3.4
4.3.5
5
PROFIBUS-DP Slave Parameters .....................................................................39
CANopen Slave Parameters ..............................................................................41
DeviceNet Slave Parameters .............................................................................43
CompoNet Slave Parameters.............................................................................45
CC-Link Slave Parameters.................................................................................48
DIAGNOSIS ..............................................................................................................50
5.1
Overview Diagnosis ..................................................................................................50
5.2
Firmware Diagnosis ..................................................................................................51
5.3
General Diagnosis ....................................................................................................52
EXTENDED DIAGNOSIS ..........................................................................................55
6.1
Overview Extended Diagnosis..................................................................................55
6.1.1
6.1.2
6.1.3
6.1.4
6.1.5
6.1.6
6.1.7
EtherNet/IP Adapter ...........................................................................................56
Open Modbus/TCP.............................................................................................57
PROFINET IO Device.........................................................................................58
SERCOS III ........................................................................................................59
PROFIBUS Slave ...............................................................................................60
CC-Link Slave.....................................................................................................61
CANopen Slave ..................................................................................................62
6.2
Task Information .......................................................................................................63
6.3
IniBatch Status..........................................................................................................64
6.4
Code Diagnosis ........................................................................................................65
6.5
TCPUDP ...................................................................................................................66
6.5.1
6.5.2
6.5.3
6.5.4
6.5.5
6.6
IP Information .....................................................................................................66
IP Packet Counter ..............................................................................................67
IP Code Diagnosis..............................................................................................68
TCP_UDP Information........................................................................................69
TCP_UDP Code Diagnosis ................................................................................70
EtherNet/IP Adapter..................................................................................................71
6.6.1
6.6.2
6.6.3
6.7
EIS_ENCAP_TASK ............................................................................................72
EIS_OBJECT_TASK ..........................................................................................74
EIS_AP_TASK....................................................................................................76
Open Modbus/TCP ...................................................................................................77
6.7.1
6.8
OMB ...................................................................................................................78
PROFINET IO Device...............................................................................................83
6.8.1
PNS_IF ...............................................................................................................84
6.9
SERCOS III...............................................................................................................86
6.10
PROFIBUS Slave .....................................................................................................87
6.10.1
6.11
PROFIBUS_FSPMS...........................................................................................88
CC-Link Slave...........................................................................................................91
netSLAVE DTM
6.11.1
6.11.2
6.12
7.1
Connecting/Disconnecting Device ..........................................................................112
7.2
Download Configuration .........................................................................................113
7.3
License ...................................................................................................................114
Which licenses are present in the Device? ......................................................115
How to order a license......................................................................................116
How to get the License and transfer it to the Device........................................121
ERROR NUMBERS ................................................................................................122
8.1
Error Code Definition ..............................................................................................122
8.2
Overview Error Numbers ........................................................................................123
8.3
General Hardware Error Codes ..............................................................................124
8.3.1
8.3.2
8.3.3
8.4
RCX Errors - MID_SYS Task Error Codes.......................................................124
RCX Errors - Common Status Codes...............................................................126
RCX Errors - Status & Error Codes..................................................................127
ODM Error Codes ...................................................................................................128
8.4.1
8.4.2
8.4.3
9
CANOPEN_SLAVE ..........................................................................................107
CANOPEN_APS...............................................................................................110
ONLINE FUNCTIONS .............................................................................................112
7.3.1
7.3.2
7.3.3
8
CCLINK_SLAVE.................................................................................................92
CCLINK_APS ...................................................................................................103
CANopen Slave ......................................................................................................106
6.12.1
6.12.2
7
General ODM Error Codes...............................................................................128
General ODM Driver Error Codes ....................................................................129
ODM cifX Driver Specific Errors .......................................................................130
8.5
Error Codes cifX Device Driver ...............................................................................134
8.6
ODM DBM V4 Error Codes.....................................................................................136
LISTS ......................................................................................................................142
9.1
List of Figures .........................................................................................................142
9.2
List of Tables ..........................................................................................................143
10
GLOSSARY.............................................................................................................146
11
APPENDIX ..............................................................................................................150
11.1
User Rights .............................................................................................................150
11.1.1
11.1.2
Settings.............................................................................................................150
Configuration ....................................................................................................150
11.2
References .............................................................................................................151
11.3
Contacts..................................................................................................................152
Introduction • 5
netSLAVE DTM
1
1.1
Introduction
About this Manual
This manual describes how to set up and configure NETX Slave devices,
which are described with GSDML files. These devices can be configured by
use of the NETX Slave DTM within a FDT Framework.
The manual provides information on how to set and configure the device
parameters of a NETX Slave device using the netSLAVE DTM, and what
can be read from the diagnosis panes.
Note: This manual includes already the descriptions for the Firmware
Download, which is specified for future application.
Dialog Panes
The table below gives an overview for the individual dialog panes
descriptions:
Section
Subsection
Manual
Page
Settings
Overview Settings
20
Driver
21
Device Assignment
23
Configuration
Overview Configuration
25
Diagnosis
Overview Diagnosis
50
Firmware Diagnosis
51
General Diagnosis
52
Overview Extended Diagnosis
55
Extended Diagnosis
Table 1: Descriptions Dialog Panes
Introduction • 6
netSLAVE DTM
1.1.1
Online Help
The netSLAVE 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
Component
Chapt
er
Revision
21.08.08 1.0.0.17
1.0.0.17
netSlaveDTM.dll
netSlaveGUI.ocx
All
created
2
01.09.08 1.0.0.17
1.0.0.17
netSlaveDTM.dll
netSlaveGUI.ocx
1.4
2.1
3
4
5.3
6
7.3
12.1
Section ‚ Dialog Structure of the ..’ actualized,
Section ‚Configuration Steps’ actualized,
Chapter ‚SETTINGS’ actualized,
Chapter ‚CONFIGURATION’ actualized,
Sections ‚General Diagnosis’ actualized,
Chapter „Extended Diagnosis“ revised,
Section ‚License’ added,
Section ‚User Rights’ actualized,
3
16.12.08 1.0.0.52
1.0.0.52
netSlaveDTM.dll
netSlaveGUI.ocx
4
Chapter ‚CONFIGURATION’ actualized. (Values for NT added).
4
15.01.09 1.0.0.52
1.0.0.52
netSlaveDTM.dll
netSlaveGUI.ocx
6
Chapter ‚Extended Diagnosis’ actualized.
5
05.02.09 1.0.0.63
1.0.0.63
netSlaveDTM.dll
netSlaveGUI.ocx
4.3.1
Section ‚PROFIBUS DP Slave Parameters’ actualized.
6
04.05.09 1.0.0.77
1.0.0.77
netSlaveDTM.dll
netSlaveGUI.ocx
All,
1.2.6
1.4.4.1
1.4.5
4.1
4.2
4.3
10
Descriptions to firmware download deleted,
Section “Registered Trademarks” actualized,
Section “ General Buttons” actualized,
Section “Station Bar” actualized,
Section “ Overview Configuration” actualized,
Section “ Real-Time Ethernet Systems” actualized,
Section “Fieldbus Systems” actualized,
Chapter “Glossar” actualized.
7
28.05.09 1.0.0.80
1.0.0.80
netSlaveDTM.dll
netSlaveGUI.ocx
4.2
4.3
Section “ Real-Time Ethernet Systems” actualized,
Section “Fieldbus Systems” actualized.
Index
Date
1
Version
Introduction • 7
netSLAVE DTM
1.1.3
Conventions in this Manual
Operation instructions, a result of an operation step or notes are marked as
follows:
Operation Instructions:
¾ <instruction>
Or
1. <instruction>
2. <instruction>
Results:
° <result>
Notes:
Important: <important note>
Note: <note>
<note, were to find further information>
Introduction • 8
netSLAVE DTM
1.2
1.2.1
Legal Notes
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.
Introduction • 9
netSLAVE DTM
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.
Introduction • 10
netSLAVE DTM
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 and Windows® XP are registered trademarks of Microsoft
Corporation.
EtherCAT® is a registered trademark of Beckhoff Automation GmbH, Verl,
Germany, formerly Elektro Beckhoff GmbH.
Modbus® is a registered trademark of Schneider Automation
Introduction • 11
netSLAVE DTM
1.3
About netSLAVE DTM
You can use the netSLAVE DTM to configure the NETX Slave device
within a 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 netSLAVE DTM
To configure a NETX Slave device with the DTM the following requirements
have to be accomplished:
• In the device the firmware must be loaded
(The firmware is loaded to the device using
netXConfiguration Tool or cifX Driver Setup Utility.)
the
program
Information to the programs netXConfiguration Tool or cifX Driver
Setup Utility you find in the corresponding manuals on the CD Rom
deliverd with your device.
• Installed FDT/DTM V1.2 compatible Frame application
• Loaded DTM in the the Device Catalog of the FDT frame application
Introduction • 12
netSLAVE DTM
1.4
Dialog Structure of the netSLAVE 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
utility.
General Device Information
Navi
gation
Area
Dialog Pane
OK
Cancel
Apply
Help
Status Line
Figure 1: Dialog Structure of netSLAVE DTM
Introduction • 13
netSLAVE DTM
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
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
Introduction • 14
netSLAVE DTM
1.4.3
Dialog Pane
At the dialog pane the setting, the configuration or the diagnostic pane is
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 Driveron page 21.
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 Assignmenton page 23.
Configuration
In the Configuration pane the parameters of the currently loaded
firmware are displayed and can be edited there, provided that a
firmware has already been loaded. For further information see
section Overview Configuration on page 25.
Diagnosis
Diagnosis/
Extended Diagnosis
At the Diagnosis panes diagnosis information can be read. For
further information, refer to section Overview Diagnosis on page
50 or section Overview Extended Diagnosis on page 55.
Table 4: Overview Dialog Panes
Note: Accessing the Diagnosis panes of the netSLAVE DTM requires an
online connection from the netSLAVE DTM to the NETX Slave device .
For further information, refer to section Connecting/Disconnecting Device
on page 107.
Introduction • 15
netSLAVE DTM
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.
No: The changes are not saved or the changed values are not applied on
the frame application database.
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
Introduction • 16
netSLAVE DTM
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
Field
Icon / Meaning
1
DTM Connection States
Connected: Icon closed = Device is online
Disconnected: Icon opened = Device is offline
2
Data Source States
Data set: The displayed data are read out from the instance data set
(database).
Device: The displayed data are read out from the device.
3
States of the instance Date Set
Valid Modified: Parameter is changed (not equal to data source).
4
Changes directly made on the Device
Load/configure diagnosis parameters: Diagnosis is activated.
6
Device Diagnosis Status
Save operation succeeded: The save operation has been successful.
Further messages due to successful handling of device data.
Save operation failed: The save operation has failed.
Further fail operation messages due to incorrect communication due to
malfunction in the field device or its peripherals.
Table 7: Status Bar Icons [1]
Offline State
Save operation
succeeded
Online State and
Diagnosis
Figure 4: Status Bar Display Examples
Getting Started • 17
netSLAVE DTM
2
2.1
Getting Started
Configuration Steps
The following table describes the steps to configure a device with
netSLAVE DTM as it is typical for many cases. At this time it is
presupposed that the hardware installation was done.
For detailed information see Page
section
#
Step
Short Description
1
Create new project /
Open existing project
Depending of the frame application.
For the configuration software:
- select File > New or File > Open.
2
Insert Slave device into
configuration
Depending of the FDT Container:
For netDevice:
- in the Device Catalog under Gateway StandAlone Slave click to the Slave device,
- and insert the device via drag and drop
to the line in the network view.
-
-
3
Open the Slave DTM
configuration dialog
Open the Slave DTM configuration dialog.
- Double click to the device icon of the Slave.
- The Slave DTM configuration dialog is displayed.
-
-
4
Select driver
In the Slave DTM configuration dialog:
- select Settings > Driver,
- select a driver,
- therefore check the appropriate checkbox.
- if necessary, configure the driver settings.
Setting Driver and Selecting
Device
19
Driver
21
(See User Manual netFrame)
5
Assign Slave device
(with firmware)
Assign the device to this driver.
- select Settings > Device Assignment,
- select the button Scan,
- select a Slave device (with firmware),
- therefore check the appropriate checkbox,
- select the button Apply.
Selecting the Device (with
firmware)
24
6
Configure Slave device
- select Configuration,
- set the configuration parameters for the Slave to
be used,
- close the Slave DTM configuration dialog via
the button OK.
25
7
Save project
Depending of the frame application.
For the configuration software:
- select File > Save.
(See User Manual netFrame)
-
8
Connect device
Depending of the FDT Container.
For netDevice:
- right click to the device icon,
- select context menu entry Device > Connect.
Connecting/Disconnecting
Device
107
More see next page
netSLAVE DTM
#
Step
Short Description
For detailed information see Page
section
9
Diagnosis
For netDevice:
- select context menu entry Diagnosis.
- The Slave DTM diagnosis dialog is displayed.
- Continue with further device diagnosis,
- close the Slave DTM diagnosis dialog via
the button OK.
Overview Diagnosis
50
10
Disconnect
For netDevice:
- select Device > Disconnect.
Connecting/Disconnecting
Device
107
Table 8: Getting Started - Configuration Steps
netSLAVE DTM
2.1.1
Setting Driver and Selecting Device
Requirements:
(The firmware is loaded
to the device using
the
program
The following steps are needed to establish a connection from the
netSLAVE DTM to the NETX Slave 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 firmware).
4. Select the device and apply the selection.
An overview of the descriptions for these steps you find in the section
Overview Settings on page 20.
5. In the DTM interface dialog select the OK button, to apply the selection
and to close the DTM interface dialog.
6. Put a right-click on the NETX Slave device icon.
7. Select the Connect command from the context menu.
° Now the NETX Slave device is online.
° The NETX Slave device now is connected to the netSLAVE DTM via
an online connection. In the network view the device description at the
device icon is displayed with a green colored background.
Settings • 20
netSLAVE DTM
3
3.1
Settings
Overview Settings
Settings Dialog Panes
The table below gives an overview for the individual Settings dialog panes
descriptions:
Section
Subsection
Manual
Page
21
Driver
Selecting the Driver
21
Configuring the Driver
22
cifX Device Driver
22
23
Device Assignment
Scanning for Devices
23
Selecting the Device (with firmware)
24
Table 9: Descriptions Settings
Figure 5: 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 17.
Settings • 21
netSLAVE DTM
3.2
Driver
The Driver dialog pane displays the driver/s to be used for a netSLAVE
DTM to device communication connection.
Figure 6: 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
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 7: Driver Selection List - recognized or installed Drivers
2. Check the checkbox for the driver/s in the selection list.
Figure 8: Driver Selection List - Driver/s selected
Settings • 22
netSLAVE DTM
3.2.2
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 9: Navigation Area – Settings
To configure a driver:
1. Select Settings > Driver > [Name of the assigned driver].
° The corresponding driver dialog pane is displayed.
2. 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.
3.2.3
cifX Device Driver
In the netSLAVE 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 netSLAVE DTM is installed in the
same PC as the NETX Slave device .
Note: To establish a connection from a DTM to a NETX Slave device via
the cifX Device Driver, the cifX Device Driver must be installed and the
driver must have access to the NETX Slave device.
Settings • 23
netSLAVE DTM
3.3
Device Assignment
Note: In the Device Assignment you first must assign the NETX Slave
device to the netSLAVE DTM by checking the check box. This is essential
to establish an online connection from the netSLAVE DTM to the NETX
Slave device later, as described in section Connecting/Disconnecting
Device on page 107.
Therefore in the Device Assignment dialog pane you scan for the NETX
Slave device and select it.
3.3.1
1. Select Settings > Device Assignment in the navigation area.
° The dialog pane Device Assignment is displayed.
Parameter
Meaning
Range of
Value/Value
Device selection
Selecting suitable only or all devices.
suitable only, all
Device
Device class of the NETX Slave Device s.
Hardware Port
0/1/2/3
Indicates, which hardware is assigned to which
communication interface.
Serial number
Serial number of the device
Driver
Name of the driver
Channel Protocol Indicates, 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: PROFIBUS Slave
(Example for NETX PROFIBUS Slave Firmware)
Access path
(under Device
selection last
column on the
right)
Depending on the used driver in the column Access path
different data to the device are displayed.
For the cifX Device Driver the following data are displayed:
a.) For devices without firmware: …\cifX[0toN]_SYS,
b.) For devices with firmware: …\cifX[0toN]_Ch[0to3].
cifX[0toN] = Board number 0 to N
Ch[0to3] = Channel number 0 to 3
Access path
(at the lower side
of the dialog
pane)
If under Device selection the check box for a device is
checked, under Access path (at the lower side of the dialog
pane) the driver identification or depending on the used driver
additional data to the device.
For the cifX Device Driver the following data are displayed:
a.) For devices without firmware: …\cifX[0toN]_SYS,
b.) For devices with firmware: …\cifX[0toN]_Ch[0to3].
cifX[0toN] = Board number 0 to N
Ch[0to3] = Channel number 0 to 3
Depending on the
device and on the
driver:
board or channel
number, IP address
or COM interface
driver identification
(ID)
depending on the
device and on the
driver:
board or channel
number, IP address
or COM interface
Table 11: Parameters of the Device Assignment
Settings • 24
netSLAVE DTM
2. Select the list box entry suitable only or all.
3. Select the Scan button, to start the scanning process.
° Under Device Selection are displayed:
For selection suitable only - all devices, which can be connected to the
netSLAVE DTM via the preselected driver.
For selection all - all devices, which are attainable in the network and
which can be connected to a single DTM each via the preselected
drivers.
3.3.2
Selecting the Device (with firmware)
Note: A connection with the netSLAVE DTM can only be established with
one NETX Slave device .
To select the physical NETX Slave device (with firmware):
1. In the Device Assignment pane in the selection list Device selection
check the check box for the device.
Figure 10: Device Assignment - Selecting the Device (* The name of the device class is
displayed.) – Example for a device with 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.
3. Or select the OK button, to apply the selection and to close the DTM
interface dialog.
4. Connect the DTM to the device using the context menu (right mouse
click).
For further information how to establish an online connection from the
netSLAVE DTM to the NETX Slave device, refer to section
Connecting/Disconnecting Device on page 107.
Configuration • 25
netSLAVE DTM
4
4.1
Configuration
The current parameters of the selected firmware protocol are displayed in
the Configuration pane. The configuration parameters can be edited.
¾ Click in the navigation area to the Configuration folder to open the
Configuration pane.
Figure 11: Navigation Area - Configuration
Configuration
§
In the Configuration pane the current
parameters of the selected firmware protocol
are displayed.
Parameters of the
Protocol
Default
Figure 12: netX Configuration Tool - Configuration Pane
The descriptions of the user interface of the single protocols are listed in
the table in the next subsequent section. The table also contains the page
number of each section with the description.
Default
With the Default button the parameters can be reset to the default state.
Enable
If ‘Enabled’ is unchecked, the default value is used.
Error during Data Input
Error
Action
Parameter validation error! Input field cannot be empty.
Enter data.
Input validation error! Input field accepts only digits.
Enter only digits.
Input validation error! Input field accepts only digits and letters
from A to F.
Enter only digits and
letters from A to F.
Table 12: Error during Data Input
netSLAVE DTM
4.1.1
Parameters
Parameters
of
the
Protocol
–
Overview
Configuration
Any Parameters of the Protocol are described in the subsections listed
in the table hereafter.
Section
Subsection
Page
Real-Time Ethernet
Systems
EtherCAT Slave Parameters
27
EtherNet/IP Adapter Parameters
29
Open Modbus/TCP Parameters
32
Powerlink Controlled Node/Slave Parameters
34
PROFINET IO-Device Parameters
36
SERCOS III Slave Parameters
38
PROFIBUS-DP Slave Parameters
39
CANopen Slave Parameters
41
DeviceNet Slave Parameters
43
CompoNet Slave Parameters
45
CC-Link Slave Parameters
48
Fieldbus Systems
Table 13: Descriptions Configuration Parameters Real-Time Ethernet Systems or Fieldbus
Systems
netSLAVE DTM
4.2
4.2.1
Real-Time Ethernet Systems
EtherCAT Slave Parameters
Parameter
Meaning
Range of Value/Value
Communication start application controlled or automatic
Application controlled,
Automatic
Default CIFX RE/ECS
Automatic
Interface
Bus Startup
Watchdog Time Watchdog time within which the device watchdog must be
[ms]
retriggered from the application program while the application
program monitoring is activated.
When the watchdog time value is equal to 0 the application
program monitoring is deactivated.
[0, 20 … 65535] ms,
default = 1000 ms,
0 = Off
I/O Data Status Status of the input or the output data.
None, (1 Byte, 4 Byte)
For each input and output data the following status information (in Default: None
Byte) is memorized in the dual-port memory:
Status 0 = None (default)
Status 1 = 1 Byte (for future use)
Ident
Enabled
If ‘Enabled’ is unchecked, for the single Ident parameters each
the respective default value is used.
Vendor ID
Identification number of the manufacturer
0x00000000 ...
0xFFFFFFFF (hex)
Primary Vendor ID:
0x00000044 (hex)
Default: Secondary
Vendor ID:
CIFX RE/ECS,
COMX RE/ECS,
NETX 50 RE/ECS,
NETX 100 RE/ECS,
NETX 500 RE/ECS:
0xE0000044 (hex)
Product Code
Product code of the device as specified by the manufacturer
0x00000000 ...
0xFFFFFFFF (hex),
Default:
CIFX RE/ECS:
0x00000001 (hex),
COMX RE/ECS:
0x00000003 (hex),
NXSB 100 RE/ECS:
0x00000006 (hex),
NETX 500 RE/ECS:
0x00000009 (hex),
NETX 100 RE/ECS:
0x0000000C (hex),
NETX 50 RE/ECS:
0x0000000A (hex),
NT 100: 0x000D
For more see next page
netSLAVE DTM
Parameter
Meaning
Ident (Fortsetzung)
Revision
Number
Revision number of the device as specified by the manufacturer
0x00000000 ...
0xFFFFFFFF (hex),
Default:
CIFX RE/ECS,
COMX RE/ECS:
0x00020001 (hex),
NETX 500 RE/ECS,
NETX 100 RE/ECS,
NETX 50 RE/ECS:
0x00010000 (hex)
Serial Number
0x00000000 ...
0xFFFFFFFF (hex)
Length of the input data in Byte
NXSTK 50-RE/ECS,
NIC 50-RE/ECS:
0 … 400* Byte
Default: 4 Byte
Data
Input Data
Bytes
CIFX RE/ECS:
0 … 200** Byte
Default: 4 Byte
Default in XML-Datei:
200
Output Data
Bytes
Length of the output data in Byte
NXSTK 50-RE/ECS,
NIC 50-RE/ECS:
0 … 400* Byte
Default: 4 Byte
CIFX RE/ECS:
0 … 200** Byte
Default: 4 Byte
Default in XML-Datei:
200
* Sum: The maximum length of input and of output together is equal 400 Bytes,
Table 14: EtherCAT Slave Parameters
Note: To configure the Master, an XML file (device description file) is
required. The settings in the used Master must comply with the settings in
the Slave to establish communication. Important parameters are: Vendor
ID, Product Code, Serial Number, Revision Number, Output and Input
Data Bytes.
Note: If the XML file Hilscher cifX RE ECS V2.2.x.xml is use/updated, the
firmware with the version 2.2.x must be use/updated.
For CIFX RE/ECS please note also:
Note: **The loadable firmware supports for the number of cyclic input data
and for cyclic output data in total up to 400 bytes. If more than 200 bytes
for input data or for output data should be exchanged via EtharCAT, then
a customer specific XML file is necessary. Additionally the following
formular applies: (number of input bytes + 3)/4 + (number of output bytes
+ 3)/4 must be less or equal to 100.
netSLAVE DTM
4.2.2
EtherNet/IP Adapter Parameters
Parameter
Meaning
Automatic
Default CIFX RE/EIS:
Automatic
Interface
Bus Startup
[ms]
[0, 20 … 65535] ms,
default = 1000 ms,
0 = Off
Ident
Enabled
If ‘Enabled’ is unchecked, for the single Ident parameters each
the respective default value is used.
Vendor ID
0x00000000 ...
0x0000FFFF (hex),
Hilscher:
0x00000011B (hex)
Product Code
0x00000000 ...
0x0000FFFF (hex),
Default
CIFX RE/EIS:
0x00000101 (hex),
COMX RE/EIS:
0x00000103 (hex),
NETX 500 RE/EIS:
0x00000105 (hex),
NETX 100 RE/EIS:
0x00000109 (hex),
NETX 50 RE/EIS:
0x00000107 (hex),
NT 100:
0x00000010F (hex)
Product Type
Communication Adapter
0x00000000 ...
0x0000FFFF (hex),
Default:
0x00000000C (hex)
Major Rev
Major Revision
0 ... 255,
Default: 1
Minor Rev
Minor Revision
0 ... 255,
Default: 1
Device name
Device name of the device station as character string,
e. g. EtherNet/IP Adapter (Slave).
0 - 31 ASCII characters
netSLAVE DTM
Parameter
Meaning
IP Address
Valid IP address for the device
If ‘Enabled’ is unchecked (Default setting), the device obtains its
IP Address from a DHCP server or also from a BOOTP server, if
this one is checked.
If ‘Enabled’ is checked, the device uses the manually entered
value.
Valid IP address
Default: unchecked
Netmask
Valid Network mask for the device
Netmask from a DHCP server or also from a BOOTP server, if
this one is checked.
value.
Valid network mask
Default: unchecked
Gateway
Valid Gateway address for the device
Gateway Address from a DHCP server or also from a BOOTP
server, if this one is checked.
value.
Valid gateway address
Default: unchecked
Bus
There are three methods available, how the device can obtain its
IP Address, Netmask and Gateway Address, one of which must
be selected.
These methods can also be combined.
The device performs the following sequence in order to obtain the
addresses:
1. from a DHCP server if DHCP is checked (if a DHCP server
provides the requested addresses to the device, then the device
uses these addresses)
2. from a BootP server if BootP is checked (if a BootP server
3. the addresses manually set are used. If the IP Address is set
manually also the Network Mask must be set manually. The
manually set Gateway Address is optional.
If no DHCP server and no BootP server and no manually set
addresses exist, then the protocol is not ready for initialization or
for operation.
Flags
BootP:
If checked, the device obtains its IP Address, Netmask, Gateway
Address from a BOOTP server.
Default: unchecked
DHCP:
Address from a DHCP server.
Default: checked
100Mbit: Speed Selection,
Default: unchecked
If checked, the device will operate at 100 MBit/s, else at 10
MBit/s. This parameter will not be in effect, when auto-negotiation
is active.
FullDuplex: Duplex Operation,
If checked, full-duplex operation will be used. The device will
operate in half-duplex mode, if this parameter is set to zero. This
parameter will not be in effect, when auto-negotiation is active.
Default: unchecked
Auto-neg.: Auto-Negotiation,
If checked, the device will auto-negotiate link parameters with the
remote hub or switch.
Default: checked
netSLAVE DTM
Parameter
Meaning
Data
Input Data
Bytes
Maximum allowed length of the input data in Byte. This parameter 0 … 504 Byte
should be equal to or higher than the complete projected input
Default
data length, otherwise the EtherNet/IP device will reject the cyclic CIFX RE/EIS: 32 Byte
communication requests.
Output Data
Bytes
Maximum allowed length of the output data in Byte. This
0 … 504 Byte
parameter should be equal to or higher than the complete
Default
projected output data length, otherwise the EtherNet/IP device will CIFX RE/EIS: 32 Byte
reject the cyclic communication requests.
Table 15: EtherNet/IP Adapter Parameters
Note: To configure the Scanner/Master, an EDS file (device description
file) is required. The settings in the used Scanner/Master must comply
with the settings in the Adapter/Slave to establish communication.
Important parameters are: Input, Output Data Bytes, Vendor ID, Product
Type, Product Code, Major Rev, Minor Rev, IP Address and Netmask.
netSLAVE DTM
4.2.3
Open Modbus/TCP Parameters
Parameter
Meaning
Automatic
Default CIFX RE/OMB:
Automatic
Interface
Bus Startup
[ms]
[0, 20 … 65535] ms,
default = 1000 ms,
0 = Off
Mode
I/O Mode (default),
Message Mode
Mode of data exchange:
Message-Mode or IO-Mode
Swap
Data-storage mode:
Data will not be swapped or Data will be swapped.
Data will be swapped
(default),
Data will not be
swapped
Map FC1
and FC3
If unchecked, data are read from the intput area using FC1, FC3
and FC23.
If checked, data are read from the output area using FC1, FC3
and FC23. FC1 then can be used instead of FC2 and FC3 instead
of FC4.
Default
CIFX RE/OMB:
unchecked/no
alternative mapping
Server Connections
0 ... 4 ... 16
Bus
Open Server
Sockets
Number of sockets to provide for server requests*
*A value of 0 means that the Open Modbus/TCP task exclusive works as Client,
while a Value of 16 means that the Open Modbus/TCP task exclusive works as
Server in Message-Mode.
The parameters Send Timeout, Connect Timeout and Close Timeout are for the
Timeout between the Open Modbus/TCP Task and the TCP Task.
OMB Open
Time
Connection remain open time
Only for client jobs in message-mode. The connection to the
destination-device stays open, until timeout is expired. Value is
multiplied with 100 ms.
100 ... 1000 ...
6000000
Note: This timeout starts, after receiving the answer to a
command
Answer
Timeout
100 ... 2000 ...
Only for client jobs in message-mode. After expiration of this time, 6000000
the job will be canceled and an error is send to the application.
Value is multiplied with 100 ms.
Telegram Timeout
Note: This timeout starts after command is send to the destination
device via TCP
Send Timeout
TCP Task SendTimeout Parameter
0 ...
Parameter for TCP task (in milliseconds) . Used OMB task
internal. It specifies the timeout for trying to send messages via
TCP/IP
2.000.000.000
If the value 0 is selected, the default value of 31000 milliseconds
is used.
netSLAVE DTM
Parameter
Meaning
Connect
Timeout
TCP Task Connect Timeout Parameter
0 ...
Parameter for TCP task (in milliseconds). Used OMB task
internal. It specifies the timeout for trying to establish a
connection with the TCP task.
2.000.000.000
is used.
Close Timeout
TCP Task Close Timeout Parameter
0 ...
Parameter for TCP task (in milliseconds). Used OMB task
internal. It specifies the timeout for trying to close a connection
with the TCP task.
2.000.000.000
is used.
IP Address
IP Address from a DHCP or BOOTP server.
value.
Valid IP address
Default: unchecked
Net Mask
Netmask from a DHCP or BOOTP server.
value.
Valid network mask
Default: unchecked
Gateway
Gateway Address from a DHCP or BOOTP server.
value.
Valid gateway address
Default: unchecked
There are three methods available, how the device can obtain its
IP Address, Netmask and Gateway Address, one of which must
be selected.
These methods can also be combined.
The device performs the following sequence in order to obtain the
addresses:
1. from a DHCP server if DHCP is checked (if a DHCP server
2. from a BootP server if BootP is checked (if a BootP server
3. the addresses manually set are used. If the IP Address is set
manually also the Network Mask must be set manually. The
manually set Gateway Address is optional.
If no DHCP server and no BootP server and no manually set
addresses exist, then the protocol is not ready for initialization or
for operation.
Flags
BootP:
Address from a BOOTP server.
Default: unchecked.
DHCP:
Address from a DHCP server.
Default: unchecked.
Table 16: Open Modbus/TCP Parameters
netSLAVE DTM
4.2.4
Powerlink Controlled Node/Slave Parameters
Parameter
Meaning
Automatic
Default CIFX RE/PLS:
Automatic
Interface
Bus Startup
Watchdog Time [ms] Watchdog time within which the device watchdog must be
retriggered from the application program while the
application program monitoring is activated.
[0, 20 … 65535] ms,
default = 1000 ms,
0 = Off
I/O Data Status
Status of the input or the output data.
For each input and output data the following status
information (in Byte) is memorized in the dual-port memory:
Default: None
Disable HostDecides, whether host-triggered update for input data
Triggered Input Data exchange is enabled (hook checked) or disabled (hook
Exchange
unchecked).
Default: unchecked
Decides, whether host-triggered update for output data
exchange is enabled (hook checked) or disabled (hook
unchecked).
Default: unchecked
Disable HostTriggered Output
Data Exchange
Ident
If ‘Enabled’ is unchecked, for the single Ident parameters
each the respective default value is used.
Enabled
Vendor ID
0x00000000 ...
0xFFFFFFFF (hex),
Hilscher:
0x00000044 (hex)
0x00000000 ...
0xFFFFFFFF (hex),
0x00000000 (hex)
Serial Number
Product Code
Product code of the device as specified by the manufacturer 0x00000000 ...
0xFFFFFFFF (hex),
Default:
CIFX RE/PLS:
0x00000001 (hex),
COMX RE/PLS:
0x00000003 (hex),
NETX 500 RE/PLS:
0x00000106 (hex),
NETX 100 RE/PLS:
0x00000109 (hex) ,
NETX 50 RE/PLS:
0x00000107 (hex)
Revision Number
Revision number of the device as specified by the
manufacturer
0x00000000 ...
0xFFFFFFFF (hex),
0x00000000 (hex)
netSLAVE DTM
Parameter
Meaning
Node Id
EPL Node ID (EPL = Ethernet Powerlink)
1...239, Default
CIFX RE/PLS: 1
DNS Node Name
DNS-compatible name of the Powerlink Controlled
Node/Slave
Gateway Address
Gateway address for IP stack
192.168.100.254
Input Data Bytes
Length of the input data in byte
1… 1490 Byte,
Default: 4 Byte
Output Data Bytes
Length of the output data in byte
1… 1490 Byte,
Default: 4 Byte
Disable PDO
Mapping Version
Check
Decides, whether PDO mapping version is checked (hook
checked) or not checked (hook unchecked).
Default: checked
Configure Default
Objects
Decides, whether default objects are created (hook
checked) or not (hook unchecked).
Default: checked
Bus
Data
If the objects will be created, the old set of previously
existing objects will be cleared
Delete Application
Objects
Decides, whether application objects are deleted (hook
checked) or not (hook unchecked).
Default: checked
Table 17: Powerlink Controlled Node/Slave Parameters
Note: To configure the Managing Node/Master, an XDD file (device
description file) is required. The settings in the used Managing
Node/Master must comply with the settings in the Controlled Node/Slave,
to establish communication. Important parameters are: Vendor ID, Product
Code, Serial Number, Revision Number, Node ID, Output and Input
length.
netSLAVE DTM
4.2.5
PROFINET IO-Device Parameters
Parameter
Meaning
Automatic
Default CIFX RE/PNS:
Automatic
Interface
Bus Startup
Watchdog Time [ms] Watchdog time within which the device watchdog must be
retriggered from the application program while the
application program monitoring is activated.
When the watchdog time value is equal to0 the application
I/O Data Status
Status of the input or the output data.
For each input and output data the following status
information (in Byte) is memorized in the dual-port memory:
[0, 20 … 65535] ms,
default = 1000 ms,
0 = Off
Default: None
Ident
Enabled
If ‘Enabled’ is unchecked, for the single Ident parameters
each the respective default value is used.
Vendor ID
Identification number of the manufacturer, assigned by
PROFIBUS Nutzerorganisation e. V.
0x00000000 ...
0xFFFFFFFF (hex),
Hilscher:
0x00000011E (hex)
Device ID
Identification number of the device, freely eligible by the
manufacturer, fixed for every device.
0x00000000 ...
0x0000FFFF (hex),
CIFX RE/PNS:
0x00000103 (hex),
COMX RE/PNS:
0x00000101 (hex),
NXSB 100 PNS:
0x00000104 (hex),
NETX 50 RE/PNS:
0x00000109 (hex),
NETX 100 RE/PNS:
0x00000108 (hex),
NETX 500 RE/PNS:
0x00000107 (hex),
NT 100 (Gateway)
0x00000010B (hex),
Device Type
Description of the device type, freely eligible
Character string,
0 ... 25 characters
Order ID
Hilscher device number or order description of the customer
for its device
Character string,
0 ... 20 characters,
e. g.:
CIFX 50-RE: 1251 100,
NXSB 100: 5720.000
Name of Station
Station name of the PROFINET IO-Device station. It has to
match the station name configured in the PROFINET IOController for this device. Must be DNS compatible name.
Character string,
1 ... 240 characters,
Default:
See GSDML-File
Type of Station
Type name of the PROFINET station; name can be
assigned freely.
Character string,
1 ... 240 characters
Default:
See GSDML-File
netSLAVE DTM
Parameter
Meaning
Maximum allowed length of the input data in Byte. This
projected input data length, otherwise the IO Device will
0 … 1024 Byte
Maximum allowed length of the output data in Byte. This
projected output data length, otherwise the IO Device will
0 … 1024 Byte
Data
Input Data Bytes
Output Data Bytes
CIFX RE/PNS:
Default: 2 Byte
CIFX RE/PNS:
Default: 2 Byte
Table 18: PROFINET IO-Device Parameters
Note: To configure the Controller, a GSDML file (device description file) is
required. The settings in the used Controller must comply with the settings
in the Device to establish communication. Important parameters are:
Station Name, Vendor ID, Device ID, Input and Output Data Bytes.
Note: Under Name of Station, the name must be typed which was also
used in the configuration file of the master of this device. If no name
chosen freely is used in the configuration file, then the name from the
GSDML file is used.
netSLAVE DTM
4.2.6
SERCOS III Slave Parameters
Parameter
Meaning
Automatic
Default CIFX RE/S3S:
Automatic
Interface
Bus Startup
[ms]
When the watchdog time value is equal to0 the application
[0, 20 … 65535] ms,
default = 1000 ms,
0 = Off
Bus
Device Address Address for the SERCOS III Slave.
The address range is from 1 to 127.
IP-Adresse
Netzmaske
Gateway
Flags
(BootP, DHCP)
[1 … 127],
Default
CIFX RE/S3S: 1
The SERCOS III Slave does not support to set the IP Address,
Network Mask and Gateway Address or the transmission
methods DHCP und BootP.
Data
Object
Dictionary
Location of the Object Dictionary for Service Channel: local or
host
The object dictionary is a collection of objects (parameters, IDN)
which are created by the firmware.
At the setting "local" all changes are lost after the restart in the
object list.
local, host
0= local
1= Host (not supported
yet)
Default = 0
Table 19: SERCOS III Slave Parameters
Note: To configure the Master, an XML file (device description file) is
the Slave to establish communication.
netSLAVE DTM
4.3
4.3.1
Fieldbus Systems
PROFIBUS-DP Slave Parameters
Parameter
Meaning
Automatic (Default)
Interface
Bus Startup
[ms]
[0, 20 … 65535] ms,
default = 1000 ms,
0 = Off
For each input and output data the following status information (in
Default: None
Ident
Ident Number
PROFIBUS Identification Number
0x00000000 ...
0x0000FFFF (hex),
Default:
CIFX DP/DPS:
0x000000B69 (hex),
NT 100:
0x000000C0E (hex)
Bus
Station Address PROFIBUS address of the device
0 … 126
Baudrate
9,6 kBit/s
19,2 kBit/s
93,75 kBit/s
187,5 kBit/s
500 kBit/s
1,5 MBit/s
3 MBit/s
6 MBit/s
12 MBit/s
31,25 kBit/s
45,45 kBit/s
Auto-Detect
Default CIFX DP/DPS:
Auto-Detect
Network Baud Rate
netSLAVE DTM
Parameter
Meaning
Bus (continued)
Flags
DPV1 Enable:
If checked, DPV1 is supported or the DPV1 functions are
activated.
Sync supported:
If checked, the Slave stack supports the SYNC command or the
SYNC mode is activated.
Default
CIFX DP/DPS:
checked
Freeze supported:
If checked, the Slave stack supports the FREEZE command or
the FREEZE mode is activated.
Fail safe supported:
If checked, the FAILSAFE operation is supported or the
FAILSAFE mode is activated.
Address change not allowed:
If checked, the Slave stack supports the Set Slave Address
command. The bus address can be changed via the Master.
Default
CIFX DP/DPS:
unchecked
Data
Output
or
Input
Module:
for output modules
for input modules
1…4
5…8
Type:
Byte or Word
„Byte“,
„Word“(Default)
each with consistency
Size:
The number of Bytes or Words in the module.
0, 1, 2, 3, 4, 8, 12,
16, 20, 32, 64 (Byte,
Word)
Output Data
Bytes
Total of the output identifier bytes of the modules 1 to 4
0 … 244, Default:
CIFX DP/DPS: 2
Input Data
Bytes
Total of the input identifier bytes of the modules 5 to 8
0 … 244, Default:
CIFX DP/DPS: 2
Configuration
Data
Configuration data for the output and input identifier bytes.
Default: A1, 91 hex
The identifier bytes consists of the Type and the Size.
The identifier bytes are the general identifier bytes according to
the PROFIBUS standard.
Table 20: Parameters - PROFIBUS-DP Slave
Note: The input and output modules each work with ’consistency’.
Note: To configure the Master, a GSD file (device description file) is
the Slave to establish communication. Important parameters are: Station
Address, Ident Number, Baudrate and Config Data (the configuration data
for the output and input length).
netSLAVE DTM
4.3.2
CANopen Slave Parameters
Parameter
Meaning
Automatic (Default)
Interface
Bus Startup
[ms]
[0, 20 … 65535] ms,
default = 1000 ms,
0 = Off
Default: None
Ident
Enabled
If ‘Enabled’ is unchecked, for the single Ident parameters each the
respective default value is used.
Vendor ID
0x00000000 ...
0x0000FFFF (hex),
Hilscher:
0x00000044 (hex)
Product Code
0x00000000 ...
0xFFFFFFFF (hex),
Default:
CIFX CO/COS:
0x001314C4 (hex),
NETX 50 CO/COS:
0x002206F0 (hex),
NETX 100 CO/COS:
0x0021DFE0 (hex),
NETX 500 CO/COS:
0x0021B8D0 (hex)
Revision
Number
Revision number of the device as specified by the manufacturer
0x00000000 ...
0xFFFFFFFF (hex),
Default:
CIFX CO/COS,
NETX 500 CO/COS,
NETX 100 CO/COS,
NETX 50 CO/COS,
0x00020000 (hex)
Serial Number
0x00000000 ...
0xFFFFFFFF (hex)
Node ID of CANopen slave
1 … 127, Default:
CIFX CO/COS: 2
Baud rate of CANopen connection
1 MBaud
800 KBaud
500 KBaud
250 KBaud
125 Kbaud
100 KBaud
50 KBaud
20 KBaud
10 Kbaud
Default:
CIFX CO/COS:
1 MBaud
Bus
Node Address
Baudrate
Available Baud Rate:
netSLAVE DTM
Parameter
Meaning
Data
Send Object
Send Object: Send object index
/Receive Object Receive Object: Receive object index
0x00002000 ...
0x00002003 (hex)
0x00002200 ...
0x00002203 (hex)
Size:
Number of data Bytes to send per send object
or number of data Bytes to receive per send object.
0 … 128
Output Data
Bytes
Total output data Bytes of all send objects
0 … 512, Default:
CIFX CO/COS:
32 Bytes
Input Data
Bytes
Total intput data Bytes of all receive objects
0 … 512, Default:
CIFX CO/COS:
32 Bytes
Table 21: CANopen Slave Parameters
Note: To configure the Master, an EDS file (device description file) is
the Slave to establish communication. Important parameters are: Node
Address and Baudrate.
netSLAVE DTM
4.3.3
DeviceNet Slave Parameters
Parameter
Meaning
Automatic (Default)
Interface
Bus Startup
[ms]
[0, 20 … 65535] ms,
default = 1000 ms,
0 = Off
Default: None
Ident
Enabled
Vendor ID
0x00000000 ...
0x0000FFFF (hex),
Hilscher:
0x00000011B (hex)
Product Code
Product code of the device
0x00000000 ...
0xFFFFFFFF (hex),
Default
CIFX DN/DNS:
0x0000001C (hex),
NETX 500 DN/DNS:
0x00000029 (hex),
NETX 100 DN/DNS:
0x00000027 (hex),
NETX 50 DN/DNS:
0x00000025 (hex)
Serial Number
0x00000000 ...
0xFFFFFFFF (hex)
Product Type
0x00000000 ...
0x0000FFFF (hex),
Default:
0x00000000C (hex)
Minor Rev
Minor Revision
1 ... 255,
Default: 1
Major Rev
Major Revision
1 ... 255,
Default: 1
Product Name
The variable Product Name is a text string that should represent a 0 ... 31 ASCII
short description of the product/product family.
Characters
netSLAVE DTM
Parameter
Meaning
MAC ID
This parameter defines the DeviceNet address of the device
within the network.
0 … 63
Baudrate
Baud rate of DeviceNet connection
500 kBaud,
250 kBaud,
125 kBaud,
Default
CIFX DN/DNS:
500 kBaud
Config Flags
The variable ConfigFlags defines configuration parameters.
0 … 31
Defaul: 0
Bus
Ignore Address Switch: ignore address switch,
Continue On Bus Off: continue operation after BUS OFF event,
Continue On Loss NP: continue operation in case of loss of
network voltage,
Receive Idle Clear Data: set receive data to 0 in the "Receive idle"
mode,
Receive Idle User Data: transfer user defined receive data in the
"Receive idle“ mode.
If a flag is unchecked, the default value is used.
Data
Produced Size
ProducedSize sets the number of send bytes.
Consumed Size ConsumedSize sets the number of receive bytes.
0 … 255,
Default
CIFX DN/DNS: 2
0 … 255,
Default
CIFX DN/DNS: 2
Table 22: DeviceNet Slave Parameters
the Slave to establish communication. Important parameters are: MAC ID,
Baudrate, Produced Size, Consumed Size, Vendor ID, Product Type,
Product Code, Major Rev, Minor Rev.
netSLAVE DTM
4.3.4
CompoNet Slave Parameters
Parameter
Meaning
Automatic (Default)
Interface
Bus Startup
[ms]
[0, 20 … 65535] ms,
default = 1000 ms,
0 = Off
Default: None
Ident
Enabled
Vendor ID
If the value 0x00000000 (hex) is entered, the software uses the
internal Hilscher ID 0x0000011B (hex).
Product Code
Product code of the device
The software uses the entered value.
Serial Number
internal device serial number.
Product Type
value 0x0000000C (hex).
Major Rev
Major Revision
If the value 0 is entered, the software uses the value 1.
Minor Rev
Minor Revision
If the value 0 is entered, the software uses the value 1.
Product Name
0x00000000 ...
0x0000FFFF (hex),
Hilscher:
0x0000011B (hex)
0x00000000 ...
0xFFFFFFFF (hex),
Default:
CIFX CP/CPS:
0x00000201 (hex),
NETX 50 CP/CPS:
0x00000203 (hex),
NETX 100 CP/CPS:
0x00000204 (hex),
NETX 500 CP/CPS:
0x00000205 (hex)
0x00000000 ...
0xFFFFFFFF (hex)
0x00000000 ...
0x0000FFFF (hex),
Default:
0x0000000C (hex)
0 ... 255,
Default: 1
0 ... 255,
Default: 1
The variable Product Name is a text string that should represent a 0 ... 31 ASCII
Characters
short description of the product/product family.
If no product name is entered, the device uses an internal default
name.
netSLAVE DTM
Parameter
Meaning
Node Type
Node Type of the CompoNet Slave
Word MIX
Word IN
Word OUT
Bit MIX
Bit IN
Bit OUT
Default:
Word MIX
Node Address
Node Address of the CompoNet Slave
Default: 2
MAC ID
The MAC ID defines the CompoNet address of the device within
the network.
The MAC ID is calculated from the selected Node Type and from
the selected Node Address according to the following table. In
this field the MAC ID is only displayed.
0 … 383,
Default: 2 (when using
the default values for
node type and node
address)
Bus
Baudrate
Node Type
Node Address
MAC ID
Word IN
0-0x3F
0x0-0x3F (0-63)
Word OUT
0-0x3F
0x40-0x7F (64-127)
Word MIX
0-0x3F
0x0-0x3F (0-63)
Bit IN
0-0x7F
0x80-0xFF (128-255)
Bit OUT
0-0x7F
0x100-0x17F (256-383)
Bit MIX
0-0x7F
0x80-0xFF (128-255)
Baud rate of the CompoNet connection
Slave,
Slave,
Slave,
Slave,
Slave,
Slave,
Slave
Auto-Detect,
93,75 kbps,
1,5 Mbps,
3 Mbps,
4 Mbps
Default: Auto-Detect
netSLAVE DTM
Parameter
Meaning
Produced Data sets the number of send points (Bits).
Node Type „Bit“:
2, 4 (Points), Default: 2
Node Type „Word“:
8, 16, 32, 48, 64, 80, 96,
112, 128, 144, 160, 170,
192, 208, 224, 240, 256
(Points), Default:16
Data
Produced Data
Produced data can be selected for the Node Type „IN“ and
„MIXED“, for „OUT“ it is grayed out.
Size
(Produced
Data)
The number of bytes in the module for the produced data.
Consumed
Data
Consumed Data sets the number of receive points (Bits).
Size
(Consumed
Data)
The number of bytes in the module for the consumed data.
1 … 32 (Bytes)*
[*= 8 … 256 Points]
Default
Node Type „Bit“: 1
Node Type „Word“: 2
Consumed data can be selected for the Node Type „OUT“ and
„MIXED“, for „IN“ it is grayed out.
Node Type „Bit“:
2, 4 (Points), Default: 2
Node Type „Word“:
8, 16, 32, 48, 64, 80, 96,
112, 128, 144, 160, 170,
192, 208, 224, 240, 256
(Points), Default:16
1 … 32 (Bytes)*
[*= 8 … 256 Points]
Default
Node Type „Bit“: 1
Node Type „Word“: 2
Table 23: CompoNet Slave Parameters
the Slave to establish communication. Important parameters are: Node
Mode, MAC ID, Baudrate, Produced Data, Consumed Data, Vendor ID,
Product Type, Product Code, Major Rev, Minor Rev.
netSLAVE DTM
4.3.5
CC-Link Slave Parameters
Parameter
Meaning
Automatic,
Default CIFX CC/CCS:
Automatic
Interface
Bus Startup
[ms]
[0, 20 … 65535] ms,
default = 1000 ms,
0 = Off
Default: None
Ident
Enabled
Vendor Code
Code for the Vendor
0 ... 65535 bzw.
0x00000000 ...
0x0000FFFF (hex),
Hilscher:
0x00000352 (hex)
Model Type
Model type
0 ... 255,
Default
CIFX CC/CCS: 1,
NETX 50 CC/CCS,
NETX 100 CC/CCS,
NETX 500 CC/CCS: 2
Software
Version
Software version
0 ... 63,
Default: 2
Bus
Station Address Station address of CC-Link Slave
1 ... 64
Note: The number of occupied stations plus station address must
not exceed the parameter range
Baud Rate
Network transmission rate
Hold last
Hold Clear Mode; Behavior in case of bus error
received Output Clear output data (unchecked)
Data
Hold last received output data (checked)
156 kBaud (Default)
625 kBaud
2500 kBaud
5 MBaud
10 MBaud
Defualt: unchecked
netSLAVE DTM
Parameter
Meaning
CC-Link
Version
CC-Link Version 1
CC-Link Version 2
1 (Default)
2
Station Type
Type of CC-Link station
Data
Remote I/O Station:
Remote Device Station
Number of
Stations
Number of occupied stations
Extension
Cycle
Number of extension cycles
Remote I/O Station:
Remote Device Station:
0 (Default)
1
1 (Default)
1 ... 4
Allowed numbers for CC-Link version 1:
Single/One cycle
1
Allowed numbers for CC-Link version 2:
IO-Data Bytes
Single/One cycle
Double/Two cycles
Quadruple/Four cycles
Octuple/Eight cycles
1 (Default)
2
4
8
Firmware/stack works according to CC-Link Version 2.0
input data
output data
0 … 368 Bytes
0 … 368 Bytes
Firmware/stack works according to CC-Link Version 1.11
input data
output data
0 … 48 Bytes
0 … 48 Bytes
Default: 4
Table 24: CC-Link Slave Parameters
Note: To configure the Master, a CSP file (device description file) is
the Slave to establish communication.
Important parameters are: Slave Station Address, Baudrate, Station Type
and Vendor Code. For CC-Link Version 2.00 are important: number of
cycles as well as number of extension cycles.
Diagnosis • 50
netSLAVE DTM
5
5.1
Diagnosis
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.
For further information to the Extended Diagnosis refer to section
Overview Extended Diagnosis on page 55.
Diagnosis Panes
The table below gives an overview for the individual Diagnosis dialog
panes descriptions for the respective communication system.
Communication System
Section
Page
EtherNet/IP Adapter
Firmware Diagnosis
51
Open Modbus/TCP
General Diagnosis
52
PROFINET IO-Device
SERCOS III Slave
CC-Link Slave
CANopen Slave
Table 25: Descriptions of the Diagnosis Panes
Note: Accessing the Diagnosis panes of the netSLAVE DTM requires an
online connection from the netSLAVE DTM to the NETX Slave device .
on page 107.
Figure 13: Navigation Area - Diagnosis
Diagnosis • 51
netSLAVE DTM
5.2
Firmware Diagnosis
In the dialog Firmware Diagnosis the actual task information of the
firmware is displayed.
Under Firmware or Version the name of the firmware and version
(including the date) are indicated.
Figure 14: Firmware Diagnosis Example PROFINET IO Device (*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
Status
Status of the task
Table 26: Description Table Task Information
Diagnosis • 52
netSLAVE DTM
5.3
General Diagnosis
Information regarding the Device State and other general diagnosis
parameters are displayed in the General Diagnosis dialog.
Figure 15: General Diagnosis
Diagnosis • 53
netSLAVE DTM
Indication
Meaning
Device State
Communicating
Communicating: Shows that the NETX Slave stack executes the
network communication.
Run
Device is configured: Shows that the NETX Slave stack has been
configured correctly.
Ready
Ready: Shows that the NETX Slave stack has been started correctly.
The NETX Slave stack waits for a configuration.
Error
Error: Shows that the NETX Slave 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 NETX Slave stack is in data exchange. In a
cyclic data exchange the input data or the output data of the Slave are
transmitted to the Master.
Idle
Idle: Shows that the NETX Slave stack is in idle mode.
Stop
Stop: Shows that the NETX Slave stack is in Stop state: There is no
cyclic data exchange at the network. The NETX Slave stack was
stopped by the application program or it changed to the Stop state
because of a bus error.
Offline
Offline: The NETX Slave is offline pending it does not have a valid
configuration.
Configuration State
Configuration
locked
Configuration locked: Shows that the NETX Slave stack configuration
is locked, to avoid the configuration data are typed over.
New Configuration pending
New Configuration pending: Shows that a new NETX Slave stack
configuration is available.
Reset required
Reset required: Shows that a firmware reset is required as a new
NETX Slave 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 27: Indication General Diagnosis
Diagnosis • 54
netSLAVE DTM
Parameter
Meaning
Communication Error
Indicates the name of the communication error. If the cause of
error is resolved, the value is set to zero again.
Watchdog time
Indicates the watchdog time in ms.
Error Count
This field holds the total number of errors detected since powerup, 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 28: Parameter General Diagnosis
Extended Diagnosis • 55
netSLAVE DTM
6
6.1
Extended Diagnosis
Overview Extended Diagnosis
The Extended Diagnosis of the netSLAVE DTM helps to find
communication and configuration errors. Therefore it contains a list of
diagnosis structures as online counter, states and parameters.
Overview Dialog Panes “Extended Diagnosis”
For an overview of the descriptions of the dialogue windows under
Extended Diagnosis for every commmunication system refer to the
following subsections.
Subsection/
Communication System
Manual
Page
EtherNet/IP Adapter
56
Open Modbus/TCP
57
SERCOS III
59
PROFINET IO Device
58
PROFIBUS Slave
60
CC-Link Slave
61
CANopen Slave
62
Table 29: Overview Extended Diagnosis
Note: Accessing the Extended Diagnosis dialog panes of the netSLAVE
DTM requires an online connection from the netSLAVE DTM to the NETX
Slave device .
on page 107.
Figure 16: Navigation Area - Extended Diagnosis
netSLAVE DTM
6.1.1
EtherNet/IP Adapter
Dialog Panes “Extended Diagnosis” EtherNet/IP Adapter
The table below gives an overview for the Extended Diagnosis dialog
panes descriptions:
Navigation Area
EtherNet/IP Adapter
Folder Name in the
Navigation Area
Dialog Pane
Manual
Page
RX-SYSTEM
Task Information
63
IniBatch Status
64
DPM_COM0_SMBX
Task Information
63
DPM_COM0_RMBX
Task Information
63
EIS_CL1_TASK
Task Information
63
EIS_ENCAP_TASK
Task Information
63
Encap Command Counter
72
Packet Counter
73
Code Diagnosis
65
Task Information
63
Object Request Counter
74
Outgoing Connection
75
Ingoing Connection
75
Code Diagnosis
65
Task Information
63
IP Information
66
IP Packet Counter
67
IP Code Diagnosis
68
TCP_UDP Information
69
TCP_UDP Code Diagnosis
70
Task Information
63
Common Diagnostic
76
General State
76
Code Diagnosis
65
EIS_OBJECT_TASK
EIS_TCPUDP
EIS_AP_TASK
Table 30: Descriptions of the Dialog Panes Extended Diagnosis EtherNet/IP Adapter
netSLAVE DTM
6.1.2
Open Modbus/TCP
Dialog Panes “Extended Diagnosis” Open Modbus/TCP
panes descriptions:
Navigation Area Open
Modbus/TCP
Folder Name in the
Navigation Area
Dialog Pane
Manual
Page
RX-SYSTEM
Task Information
63
IniBatch Status
64
DPM_COM0_SMBX
Task Information
63
DPM_COM0_RMBX
Task Information
63
TCPUDP
Task Information
63
IP Information
66
IP Packet Counter
67
IP Code Diagnosis
68
TCP_UDP Information
69
70
Task Information
63
OMB Information
78
OMB Client
79
OMB Server
80
OMB IO
81
OMB Code Diagnosis
82
Task Information
63
OMB
OMB_AP
Table 31: Descriptions of the Dialog Panes Extended Diagnosis Open Modbus/TCP
netSLAVE DTM
6.1.3
PROFINET IO Device
Dialog Panes “Extended Diagnosis” PROFINET IO Device
panes descriptions:
Navigation Area
PROFINET IO Device
Folder Name in the
Navigation Area
Dialog Pane
Manual
Page
RX-SYSTEM
Task Information
63
IniBatch Status
64
DPM_COM0_SMBX
Task Information
63
DPM_COM0_RMBX
Task Information
63
TCPUDP
Task Information
63
IP Information
66
IP Packet Counter
67
IP Code Diagnosis
68
TCP_UDP Information
69
70
Task Information
63
PROFINET Stack State
84
Station Description
85
PNS_IF
Table 32: Descriptions of the Dialog Panes Extended Diagnosis PROFINET IO Device
netSLAVE DTM
6.1.4
SERCOS III
Dialog Panes “Extended Diagnosis” SERCOS III
panes descriptions:
Navigation Area
SERCOS III
Folder Name in the
Navigation Area
Dialog Pane
Manual
Page
RX-SYSTEM
Task Information
63
IniBatch Status
64
DPM_COM0_SMBX
Task Information
63
DPM_COM0_RMBX
Task Information
63
SC3S_SVC
Task Information
63
SC3S_RTD
Task Information
63
SC3S_AP
Task Information
63
Table 33: Descriptions of the Dialog Panes Extended Diagnosis SERCOS III
netSLAVE DTM
6.1.5
PROFIBUS Slave
Dialog Panes “Extended Diagnosis” PROFIBUS Slave
panes descriptions:
Navigation Area
PROFIBUS Slave
Folder Name in the
Navigation Area
Dialog Pane
Manual
Page
RX-SYSTEM
Task Information
63
IniBatch Status
64
DPM_COM0_SMBX
Task Information
63
DPM_COM0_RMBX
Task Information
63
PROFIBUS_DL
Task Information
63
PROFIBUS_FSPMS
Task Information
63
Extended Diagnosis
88
Config Data
89
Parameter Data
90
Code Diagnosis
65
Task Information
63
PROFIBUS_APS
Table 34: Descriptions of the Dialog Panes Extended Diagnosis PROFIBUS Slave
netSLAVE DTM
6.1.6
CC-Link Slave
alog Panes “Extended Diagnosis” CC-Link Slave
panes descriptions:
Navigation Area
CC-Link Slave
Folder Name in the
Navigation Area
Dialog Pane
Manual
Page
RX-SYSTEM
Task Information
63
IniBatch Status
64
DPM_COM0_SMBX
Task Information
63
DPM_COM0_RMBX
Task Information
63
CCLINK_SLAVE
Task Information
63
Configuration
92
Commands
94
Interrupts
95
XC receive area
96
XC config area
97
XC status area
98
XC management area
99
XC triple buffer area
101
XC reserved area
102
Task Information
63
Slave configuration
103
Commands
104
DPM data exchange
105
CCLINK_APS
Table 35: Descriptions of the Dialog Panes Extended Diagnosis CC-Link Slave
netSLAVE DTM
6.1.7
CANopen Slave
Dialog Panes “Extended Diagnosis” CANopen Slave
panes descriptions:
Navigation Area
CANopen Slave
Folder Name in the
Navigation Area
Dialog Pane
Manual
Page
RX-SYSTEM
Task Information
63
IniBatch Status
64
DPM_COM0_SMBX
Task Information
63
DPM_COM0_RMBX
Task Information
63
CANOPEN_DL
Task Information
63
CANOPEN_SLAVE
Task Information
63
Common Diagnostic
76
Commands
108
Task Information
63
Slave configuration
110
Commands
111
CANOPEN_APS
Table 36: Descriptions of the Dialog Panes Extended Diagnosis CANopen Slave
netSLAVE DTM
6.2
Task Information
Figure 17: Extended Diagnosis > [Folder Name] > Task Information Example Display
Name
Description
Identifier
Identification number of the task
Major version
Task version, contains incompatible changes
Minor version
Task version, contains compatible changes
Maximum package size
Maximum package size, which the task sends
Default Queue
Queue handle, which is accessible via DPM by
mailbox.
UUID
Unique user ID, 16 Byte indicator used for task
identification and its affiliation e. g. to a stack (therein
different identification data are coded in).
Init result
Error Code, 0= no Error
The description of the error codes can be found in this
manual or in the corresponding software reference
manuals.
Table 37: Extended Diagnosis > [Folder Name] > Task Information
netSLAVE DTM
6.3
IniBatch Status
Figure 18: Extended Diagnosis > [Folder Name] > IniBatch Status Example Display
Name
Description
Communication Channel
Number of the communication channel used by the device.
Current State
0 =Idle;
1 =IniBatch packets in progress;
2 =Retrying to send last packet;
3 = Error
IniBatch Result
0 = Ok;
1 = No DBM file;
2 = No Packet table;
3 = No data set available;
4 = Data set is shorter than packet length;
5 = Packet Buffer is shorter than Packet length;
6 = Invalid packet destination;
7 = Logical queue not defined
8 = Send packet failed;
9 = Too many retries;
10 = Error in confirmation packet status
OpenDbm Result
Error when opening the IniBatch data base
Under "OpenDbm Result" the error code is typed in, when
"IniBatch Result" == "No DBM file" (1) is.
SendPacket Result
Error when sending a packet
Under "SendPacket Result" the error code is typed in, when
"IniBatch Result" == “send packet failed" (8) is.
Confirmation Result
Confirmation error when sending packets
Under "Confirmation Result" the package specific error code
from the ulSta is typed in, when "IniBatch Result " == "Error in
confirmation packet status" (10) is.
Last Packet Number
Value depends by the communication system.
Last Packet Command
Last Packet Length
Last Packet Destination
Table 38: Extended Diagnosis > [Folder Name] > IniBatch Status
The task status "Confirmation Result" is bus specific. The other task
statuses are rcx-related error codes.
netSLAVE DTM
6.4
Code Diagnosis
Figure 19: Extended Diagnosis >
EtherNet/IP Adapter
Name
[Folder Name] > Code Diagnosis
Example Display
Description
Info Counter
Counter for information reports
Warning
Counter
Counter for warning reports
Error Counter
Counter for errors
Error Level
Level of the last occurred error
Error Code
Code of the last occurred error
Parameter
Additional information to the error
Line number
Line number inside the software module
Module
Software module
Table 39: Extended Diagnosis > [Folder Name] > Code Diagnosis
netSLAVE DTM
6.5
6.5.1
TCPUDP
IP Information
Figure 20: Extended Diagnosis >
EtherNet/IP Adapter
[Folder Name] > IP Information Example Display
Name
Description
Task State
Actual state of the protocol process:
0 = Task not initialized
1 = Task is running
2 = Task initialized
3 = Initialization error
Error Counter
Counter for errors
Last Error
Last occurred error (Description see appropriate
manual)
IP Address
IP address of the Slave station.
Net Mask
Network mask of the Slave station.
Gateway
Gateway address of the Slave station.
Table 40: Extended Diagnosis > [Folder Name] > IP Information
netSLAVE DTM
6.5.2
IP Packet Counter
Figure 21: Extended Diagnosis > [Folder Name] > IP Packet Counter Example Display
EtherNet/IP Adapter
Name
Description
Packet Recv TCP
Counter for received TCP packets
Packet Recv UDP
Counter for received UDP packets
Packet Recv ICMP
Counter for received ICMP packets
Packet Recv IP Header Err
Counter for received IP packets with errors
Packet Recv ARP
Counter for received ARP packets
Packet Recv Unknown
Counter for received packets of an unknown type
Table 41: Extended Diagnosis > [Folder Name] > IP Packet Counter
netSLAVE DTM
6.5.3
IP Code Diagnosis
Figure 22: Extended Diagnosis > [Folder Name] > IP-Code Diagnosis Example Display
EtherNet/IP Adapter
Name
Description
Info Counter
Warning Counter
Error Counter
Counter for errors
Severity Level
Code
Parameter
Module
Software module
Line number
Table 42: Extended Diagnosis > [Folder Name] > IP-Code Diagnosis
netSLAVE DTM
6.5.4
TCP_UDP Information
Figure 23: Extended Diagnosis > [Folder Name] > TCP_UDP-Information Example Display
EtherNet/IP Adapter
Name
Description
Task State
1 = Task is running
Error Count
Counter for errors
Last Error
Last occurred error (Description see appropriate
manual)
Table 43: Extended Diagnosis > [Folder Name] > TCP_UDP-Information
netSLAVE DTM
6.5.5
Figure 24: Extended Diagnosis > [Folder Name] > TCP_UDP Code Diagnosis Example
Display EtherNet/IP Adapter
Name
Description
Info Counter
Warning Counter
Error Counter
Counter for errors
Severity Level
Code
Parameter
Module
Software module
Line number
Table 44: Extended Diagnosis > [Folder Name] > TCP_UDP Code Diagnosis
netSLAVE DTM
6.6
EtherNet/IP Adapter
Figure 25: Navigation Area - Extended Diagnosis EtherNet/IP Adapter
netSLAVE DTM
6.6.1
6.6.1.1
EIS_ENCAP_TASK
Encap Command Counter
Figure 26: Extended Diagnosis > EIS_ENCAP_TASK > Encap Command Counter
Name
Description
NOP
Counter incoming encapsulation telegrams
List Target
List Identity
List Services
List Interfaces
Register Session
Unregister Session
Process data
Unit Date RR Data telegrams
Unknown Command
Good Reply
Error Reply
Table 45: Extended Diagnosis > EIS_ENCAP_TASK > Encap Command Counter
netSLAVE DTM
6.6.1.2
Packet Counter
Figure 27: Extended Diagnosis > EIS_ENCAP_TASK > Packet Counter
Name
Description
[Service]
Diagnosis counter of the encapsulation layer. Indicates
the services processed. (The services of the single
packets are described in the API manual.)
Table 46: Extended Diagnosis > EIS_ENCAP_TASK > Packet Counter
netSLAVE DTM
6.6.2
6.6.2.1
EIS_OBJECT_TASK
Object Request Counter
Figure 28: Extended Diagnosis > EIS_OBJECT_TASK > Object Request Counter
The Object Request Counter table indicates the respective number of
services sent to different objects.
Name
Description
Identity Get Attribute Single
Counter for the Get Attribute Single services to the identity
object.
Identity Get Attribute All
Counter for the Get Attribute All services to the identity
object.
Identity Reset
Counter for the Reset services to the identity object.
Identity unknown Command
Counter for the Unknown Command services to the
identity object.
Assembly Get Attribute Single Counter for the Get Attribute Single services to the
assembly object.
[Object] [Service]
Counter for the [Object] services to the [Service] object.
Table 47: Extended Diagnosis > EIS_OBJECT_TASK > Object Request Counter
netSLAVE DTM
6.6.2.2
Outgoing Connection
Figure 29: Extended Diagnosis > EIS_OBJECT_TASK > Outgoing Connection
Name
Description
Issue Open
Counter for open issues
Issue Close
Counter for closed issues
Open Connections
Actual open connection
Last error instance
Last error instance
Last GRC
Last General Status Code
Last ERC
Last Extended Status Code
Table 48: Extended Diagnosis > EIS_OBJECT_TASK > Outgoing Connection
6.6.2.3
Ingoing Connection
Figure 30: Extended Diagnosis > EIS_OBJECT_TASK > Ingoing Connection
Name
Description
Last Errors Address
IP Address
Last GRC
Last General Status Code
Last ERC
Last Extended Status Code
Actual Connection
Actual open connection
Table 49: Extended Diagnosis > EIS_OBJECT_TASK > Ingoing Connection
netSLAVE DTM
6.6.3
6.6.3.1
EIS_AP_TASK
Common Diagnostic
Figure 31: Extended Diagnosis > EIS_AP_TASK > Common Diagnostic
Name
Description
Status field
Communication change of state
Bus state
Communication state
Communication Error
Unique error number according to protocol stack
(not supported yet)
Version
Version number of this diagnosis structure
Watchdog time
Configured watchdog time
Protocol Class
Protocol class:
MASTER, SLAVE, CLIENT, SERVER, GATEWAY
Error Counter
Total number of detected error since power-up or reset
Table 50: Extended Diagnosis > EIS_AP_TASK > Common Diagnostic
6.6.3.2
General State
Figure 32: Extended Diagnosis > EIS_AP_TASK > General State
Name
Description
Error Code
Table 51: Extended Diagnosis > EIS_AP_TASK > General State
netSLAVE DTM
6.7
Open Modbus/TCP
netSLAVE DTM
6.7.1
6.7.1.1
OMB
OMB Information
Figure 34: Extended Diagnosis > OMB > OMB Information
Name
Description
Task State
1 = Task is running
4 = Waiting for configuration
Error Count
Counter for errors
Last Error
Last occurred error (Description see appropriate manual)
Socket Status
The socket status informs about the TCP sockets. More
exactly, it contains the information whether sockets are
open or closed in a bit-coded manner. The coding is as
follows:
The socket number corresponds to the position of the bit
within the variable, i.e. bit 0 represents socket # 0 and bit
15 represents socket # 15. The coding is in that way that a
bit value of 1 means the respective socket is open and a
value of 0 indicates it is not open.
Cyclic Event Count
The cyclic event counter represents the number of cyclic
events that have occurred.
Idle Count
The idle count is currently not used.
Table 52: Extended Diagnosis > OMB > OMB Information
netSLAVE DTM
6.7.1.2
OMB Client
Figure 35:Extended Diagnosis > OMB > OMB Client
Name
Description
Messages Send to User
Number of messages send from the OMB client to the
user.
Messages Recv from User
Number of messages received from the user.
FC[N] Count
Number of access events to the respective function code.
FC = Function code
Possible values for N = 0 1, 2, 3, 4, 5, 6, 7, 15, 16, 23
Table 53: Extended Diagnosis > OMB > OMB Client
netSLAVE DTM
6.7.1.3
OMB Server
Figure 36:Extended Diagnosis > OMB > OMB Server
Name
Description
Messages Send to TCP task
Number of messages send from the OMB server to the
TCP task.
Messages Recv from TCP
task
Number of messages received from the TCP task.
FC[N] Count
FC = Function code
Table 54: Extended Diagnosis > OMB > OMB Server
netSLAVE DTM
6.7.1.4
OMB IO
Figure 37:Extended Diagnosis > OMB > OMB IO
Name
Description
Messages Send to TCP task
Number of messages send from the OMB server to the
TCP task.
Messages Recv from TCP
task
Number of messages received from the TCP task.
FC[N] Count
FC = Function code
Modbus address
Address within the Modbus Data model or memory map
(Range 0 ... 65535).
Data count
Data counter
Function code
The Modbus standard function codes for send and receive
operations:
FC1: Read coils
FC2: Read input discretes
FC3: Read multiple registers
FC4: Read input registers
FC5: Write coil
FC6: Write single register
FC15 : Force multiple coils
FC16: Write multiple registers
FC23: Read/Write multiple registers
The first data of the last sent function code (telegram) are
displayed.
Data
Error Count
Counter for errors
Last Error
Last occurred error (Description see appropriate manual)
Table 55: Extended Diagnosis > OMB > OMB IO
netSLAVE DTM
6.7.1.5
OMB Code Diagnosis
Figure 38:Extended Diagnosis > OMB > OMB Code Diagnosis Example Display
Name
Description
Information Counter
Warning Counter
Error Counter
Counter for errors
Severity Level
0 = None
1 = Information
2 = Warning
3 = Error
4 = Fatal Error
Code
Parameter
Module
Software module
Line number
Table 56: Extended Diagnosis > OMB > OMB Code Diagnosis
netSLAVE DTM
6.8
PROFINET IO Device
Figure 39: Navigation Area - Extended Diagnosis PROFINET IO Device
Note: The folder Extended Diagnosis > Os SockPrc to Pnio_Api are
only displayed, if the device has been configured.
netSLAVE DTM
6.8.1
6.8.1.1
PNS_IF
PROFINET Stack State
Figure 40: Extended Diagnosis > PNS_IF > PROFINET Stack State
Name
Description
Summary
Summary of the PROFINET IO stack status
Device information is set
Manufacturer information about the device, which is
defined in the GSDML file.
PROFINET stack is started
Status of the PROFINET IO stack: started
Device instance is opened
Device instance of the PROFINET IO stack: opened
API is added
API of the PROFINET IO stack: opened
Module 0 is plugged
Module 0 of the PROFINET IO stack: plugged
Module 0 and Submodule 1 are
plugged
Module 0 and Submodule 1 of the PROFINET IO
stack: plugged
Network Communication is
allowed
Network Communication: allowed
Network Communication is
enabled
Network Communication: enabled
Last Error Code of PROFINET
Stack
Last occurred error of the PROFINET IO stack
Last Error Code of RCX/API Task Last occurred error of the RCX/API task
Configuration State
Configuration of the PROFINET IO stack
Link State
State of the physical network connection of the
PROFINET IO stack
Table 57: Extended Diagnosis > PNS_IF > PROFINET Stack State
netSLAVE DTM
6.8.1.2
Station Description
Figure 41: Extended Diagnosis > PNS_IF > Station Description
Name
Description
Station name
The Station name contains the name of the station
provided by engineering.
Station type
The Station type contains the type of the station
provided by manufacturer of the device.
IP Address
Network mask
Gateway address
New configuration is available
From the following parameters at least one has
changed: Station name, station type, IP configuration.
New station name
Station name has changed.
Save Station name remanently
The new station name shall be stored remanently.
New station type
Station typehas changed.
Save Station type remanently
The new station type shall be stored remanently.
New IP configuration
IP configuration has changed.
Save IP configuration remanently The new IP configuration shall be stored remanently.
Table 58: Extended Diagnosis > PNS_IF > Station Description
netSLAVE DTM
6.9
SERCOS III
netSLAVE DTM
6.10 PROFIBUS Slave
netSLAVE DTM
6.10.1
6.10.1.1
PROFIBUS_FSPMS
Extended Diagnosis
Figure 44:Extended Diagnosis > PROFIBUS_FSPMS > Extended Diagnosis
Name
Description
Node ID
PROFIBUS address of the device,
Range of value: 0 … 125
Ident Number
PROFIBUS Identification Number,
Range of value: 0 … 65535, Default: 0x0A12
Baud Rate
9,6 kBit/s
19,2 kBit/s
93,75 kBit/s
187,5 kBit/s
500 kBit/s
1,5 MBit/s
Output Length
Number of the output bytes
Input Length
Number of the input bytes
3 MBit/s
6 MBit/s
12 MBit/s
31,25 kBit/s
45,45 kBit/s
Auto detect
Table 59: Extended Diagnosis > PROFIBUS_FSPMS > Extended Diagnosis
netSLAVE DTM
6.10.1.2
Config Data
Figure 45:Extended Diagnosis > PROFIBUS_FSPMS > Config Data
Name
Description
Configuration
Data Length
Number of the configuration data in byte
Configuration
Data
Left value: numbering of every configuration data byte
Describes how many bytes of the configuration data are valid.
Right value: value of the respective configuration data byte
Table 60: Extended Diagnosis > PROFIBUS_FSPMS > Config Data
Note: To view the Value column completely, double click to the right
border of the column head. Move to the left or the right column side using
the scroll bar.
netSLAVE DTM
6.10.1.3
Parameter Data
Figure 46:Extended Diagnosis > PROFIBUS_FSPMS > Parameter Data
Name
Description
Parameter
Data Length
Number of the parameter data in byte
Parameter
Data
Left value: numbering of every parameter data byte
Describes how many bytes of the parameter data are valid.
Right value: value of the respective parameter data byte
Table 61: Extended Diagnosis > PROFIBUS_FSPMS > Parameter Data
Note: To view the Value column completely, double click to the right
border of the column head. Move to the left or the right column side using
the scroll bar.
netSLAVE DTM
6.11 CC-Link Slave
netSLAVE DTM
6.11.1
CCLINK_SLAVE
6.11.1.1
Configuration
Figure 48: Extended Diagnosis > CCLINK_SLAVE > Configuration
Name
Slave station address
Description
Station address of CC-Link Slave
Note: The number of occupied stations plus station
address must not exceed the parameter range
Range of value: 1 ... 64
Baudrate
0 = Not configured;
1 = 156kBaud;
2 = 625kBaud;
3 = 2500kBaud;
4 = 5MBaud;
5 = 10MBaud
Station type
0 = Not configured;
1 = Remote I/O Station;
2 = Remote Device Station;
3 = Intelligent Device Station
Remote I/O Station: 1 (Default)
Remote Device Station: 1 ... 4
CC Link Version
0 = Not configured;
1 = Version 1 Mode;
2 = Version 2 Mode
Extension cycle
Number of extension cycles
0 = Not configured;
1 = Single/One cycle;
2 = Double/Two cycles;
3 = Quadruple/Four cycles;
4 = Octuple/Eight cycles
Allowed numbers for CC-Link version 1: Single
Allowed numbers for CC-Link version 2: Single, Double,
Quadruple, Octuple
More see next page
netSLAVE DTM
Name
Description
Input data in case of error
0 = Not configured;
1 = Clear;
2 = Hold
Vendor code
Vendor code (If corresponding bit in ulCcLinkFlags
parameter is set)
Range of value: 0 ... 65535, Default: 0x0352
Model type
Model type (If corresponding bit in ulCcLinkFlags
parameter is set)
Range of value: 0 ... 255
SW Version
Software version (If corresponding bit in ulCcLinkFlags
parameter is set)
Range of value: 0 ... 63, Default: 1
I/O bit data count (bytes)
to be defined
I/O register data count (bytes)
to be defined
Table 62: Extended Diagnosis > CCLINK_SLAVE > Configuration
netSLAVE DTM
6.11.1.2
Commands
Figure 49: Extended Diagnosis > CCLINK_SLAVE > Commands
Name
Description
[Service]
Diagnosis counter of the encapsulation layer. Indicates the services
processed. (The services of the single packets are described in the API
manual.)
Get packet
failed
Number of errors during requesting a packet
Send packet
failed
Number of errors during sending a packet
Table 63: Extended Diagnosis > CCLINK_SLAVE > Commands
netSLAVE DTM
6.11.1.3
Interrupts
Figure 50: Extended Diagnosis > CCLINK_SLAVE > Interrupts
Name
Description
[Service]
manual.)
Table 64: Extended Diagnosis > CCLINK_SLAVE > Interrrupts
netSLAVE DTM
6.11.1.4
XC receive area
Figure 51: Extended Diagnosis > CCLINK_SLAVE > XC receive area
ID
Value
Description
CCLS_RX_TIMESTAMP_NS
0x00000000
RX_TIMESTAMP_NS
CCLS_RX_TIMESTAMP_S
0x00000000
RX_TIMESTAMP_S
CCLS_RCVD_TEST_DATA_OF_MSTPATD
0x00000000
RCVD_TEST_DATA_OF_
MSTPATD
CCLS_RX_FRAME_FIN_OK_JUMP_LABEL
0x00000000
RX_FRAME_FIN_OK_JUMP_
LABEL
Table 65: Extended Diagnosis > CCLINK_SLAVE > XC receive area
netSLAVE DTM
6.11.1.5
XC config area
Figure 52: Extended Diagnosis > CCLINK_SLAVE > XC config area
ID
Value
Description
CCLS_SLAVE_STATION_ADDR
0x00000000
SLAVE_STATION_ADDR
CCLS_NUMBER_OF_OCCUPIED_STATIONS
0x00000000
NUMBER_OF_OCCUPIED_
STATIONS
CCLS_VENDOR_CODE
0x00000000
VENDOR_CODE
CCLS_MODEL_CODE
0x00000000
MODEL_CODE
CCLS_SOFTWARE_VERSION
0x00000000
SOFTWARE_VERSION
CCLS_SLAVE_POLLING_TIMEOUT
0x00000000
SLAVE_POLLING_TIMEOUT
CCLS_MASTER_DATA_REFRESH_TIMEOUT
0x00000000
MASTER_DATA_REFRESH_
TIMEOUT
CCLS_CONSECUTIVE_TRANSMISSION_MONITO
RING_TIMEOUT
0x00000000
CONSECUTIVE_TRANSMISSION_MONITORING_
TIMEOUT
CCLS_INTERRUPTS_ENABLE
0x00000000
INTERRUPTS_ENABLE
CCLS_SYSTIME_BORDER_COPY
0x00000000
SYSTIME_BORDER_COPY
Table 66: Extended Diagnosis > CCLINK_SLAVE > XC config area
netSLAVE DTM
6.11.1.6
XC status area
Figure 53: Extended Diagnosis > CCLINK_SLAVE > XC status area
ID
Value
Description
CCLS_RX_MESSAGE_BUF_STATUS
0x00000000
RX_MESSAGE_BUF_STATUS
CCLS_TX_MESSAGE_BUF_STATUS
0x00000000
TX_MESSAGE_BUF_STATUS
CCLS_CONNECTION_STATE
0x00000000
CONNECTION_STATE
CCLS_MASTER_STATUS
0x00000000
MASTER_STATUS
CCLS_SLAVE_STATUS
0x00000000
SLAVE_STATUS
Table 67: Extended Diagnosis > CCLINK_SLAVE > XC status area
netSLAVE DTM
6.11.1.7
XC management area
Figure 54: Extended Diagnosis > CCLINK_SLAVE > XC management area
netSLAVE DTM
ID
Value
Description
CCLS_SLAVE_FRAMES_FC_FD_TRANSMITTED_
OK
0x00000000
SLAVE_FRAMES_FC_FD_
TRANSMITTED_OK
CCLS_SLAVE_FRAMES_FE_FF_TRANSMITTED_
OK
0x00000000
SLAVE_FRAMES_FE_FF_
TRANSMITTED_OK
CCLS_MASTER_FRAMES_FA_RECEIVED_OK
0x00000000
MASTER_FRAMES_FA_
RECEIVED_OK
CCLS_MASTER_FRAMES_FC_RECEIVED_OK
0x00000000
MASTER_FRAMES_FC_
RECEIVED_OK
CCLS_MASTER_FRAMES_FD_RECEIVED_OK
0x00000000
MASTER_FRAMES_FD_
RECEIVED_OK
CCLS_MASTER_FRAMES_FE_RECEIVED_OK
0x00000000
MASTER_FRAMES_FE_
RECEIVED_OK
CCLS_MASTER_FRAMES_FF_RECEIVED_OK
0x00000000
MASTER_FRAMES_FF_
RECEIVED_OK
CCLS_SLAVE_FRAMES_FC_RECEIVED_OK
0x00000000
SLAVE_FRAMES_FC_
RECEIVED_OK
CCLS_SLAVE_FRAMES_FD_RECEIVED_OK
0x00000000
SLAVE_FRAMES_FD_
RECEIVED_OK
CCLS_SLAVE_FRAMES_FE_RECEIVED_OK
0x00000000
SLAVE_FRAMES_FE_
RECEIVED_OK
CCLS_SLAVE_FRAMES_FF_RECEIVED_OK
0x00000000
SLAVE_FRAMES_FF_
RECEIVED_OK
CCLS_UNKNOWN_FRAMES_RECEIVED_OK
0x00000000
UNKNOWN_FRAMES_
RECEIVED_OK
CCLS_SLAVE_POLLING_TIMEOUT_ERRORS
0x00000000
SLAVE_POLLING_
TIMEOUT_ERRORS
CCLS_MASTER_DATA_REFRESH_TIMEOUT_ER
RORS
0x00000000
MASTER_DATA_REFRESH_
TIMEOUT_ERRORS
CCLS_CONSECUTIVE_TRANSMISSION_MONITO
RING_TIMEOUT_ERRORS
0x00000000
CONSECUTIVE_TRANSMISSION_MONITORING_
TIMEOUT_ERRORS
CCLS_CRC_ERRORS
0x00000000
CRC_ERRORS
CCLS_ABORT_ERRORS
0x00000000
ABORT_ERRORS
CCLS_FORMAT_ERRORS
0x00000000
FORMAT_ERRORS
CCLS_LENGTH_ERRORS
0x00000000
LENGTH_ERRORS
CCLS_URX_FIFO_OVERFLOW_ERRORS
0x00000000
URX_FIFO_OVERFLOW_
ERRORS
CCLS_MESSAGES_DROPPED_DUE_MESSAGE_
BUF_FULL
0x00000000
MESSAGES_DROPPED_
DUE_MESSAGE_BUF_FULL
Table 68: Extended Diagnosis > CCLINK_SLAVE > XC management area
netSLAVE DTM
6.11.1.8
XC triple buffer area
Figure 55: Extended Diagnosis > CCLINK_SLAVE > XC triple buffer area
ID
Value
Description
CCLS_TRIPBUF_RXPDO_XPEC
0x00000000
TRIPBUF_RXPDO_XPEC
CCLS_TRIPBUF_RXPDO_LAST
0x00000000
TRIPBUF_RXPDO_LAST
CCLS_TRIPBUF_RXPDO_ARM
0x00000000
TRIPBUF_RXPDO_ARM
CCLS_TRIPBUF_RXPDO_UPDATED
0x00000000
TRIPBUF_RXPDO_UPDATED
CCLS_TRIPBUF_TXPDO_XPEC
0x00000000
TRIPBUF_TXPDO_XPEC
CCLS_TRIPBUF_TXPDO_LAST
0x00000000
TRIPBUF_TXPDO_LAST
CCLS_TRIPBUF_TXPDO_ARM
0x00000000
TRIPBUF_TXPDO_ARM
CCLS_TRIPBUF_TXPDO_UPDATED
0x00000000
TRIPBUF_TXPDO_UPDATED
Table 69: Extended Diagnosis > CCLINK_SLAVE > XC triple buffer area
netSLAVE DTM
6.11.1.9
XC reserved area
Figure 56: Extended Diagnosis > CCLINK_SLAVE > XC reserved area
ID
Value
Description
CCLS_XPEC2ARM_INTERRUPTS
0x00000000
XPEC2ARM_INTERRUPTS
CCLS_ARM2XPEC_INTERRUPTS
0x00000000
ARM2XPEC_INTERRUPTS
CCLS_HELP
0x00000000
HELP
CCLS_SR_CONFIG
0x00000000
SR_CONFIG
CCLS_SR_STATUS
0x00000000
SR_STATUS
Table 70: Extended Diagnosis > CCLINK_SLAVE > XC reserved area
netSLAVE DTM
6.11.2
6.11.2.1
CCLINK_APS
Slave configuration
Figure 57: Extended Diagnosis > CCLINK_APS > Slave Configuration
Name
Description
Flags
to be defined
Database
found
to be defined
Warmstart
configuration
to be defined
Initialization
state
0 = Idle;
1 = Send initialize request;
2 = Wait for initialize confirmation;
3 = Send register request;
4 = Wait for register confirmation;
5 = Send get buffer request;
6 = Wait for get buffer confirmation;
7 = Send bus parameter request;
8 = Wait for bus parameter confirmation;
9 = Complete;
10 = Failed
Initialization
result
to be defined
Table 71: Extended Diagnosis > CCLINK_APS > Slave Configuration
netSLAVE DTM
6.11.2.2
Commands
Figure 58: Extended Diagnosis > CCLINK_APS > Commands
Name
Description
[Service]
manual.)
Get packet
failed
Send packet
failed
Table 72: Extended Diagnosis > CCLINK_APS > Commands
netSLAVE DTM
6.11.2.3
DPM data exchange
Figure 59: Extended Diagnosis > CCLINK_APS > DPM data exchange
Name
Description
Input block size
to be defined
Input block mode
to be defined
Output block size
to be defined
Output block mode
to be defined
Input data count
to be defined
Output data count
to be defined
Input data update
count
to be defined
Output data update
count
to be defined
Table 73: Extended Diagnosis > CCLINK_APS > DPM data exchange
netSLAVE DTM
6.12 CANopen Slave
netSLAVE DTM
6.12.1
6.12.1.1
CANOPEN_SLAVE
Common Diagnostic
Figure 61: Extended Diagnosis > CANOPEN_SLAVE > Common Diagnostic
Name
Description
Last received COB-ID
Last received CAN-Message Header-ID
CAN telegrams sent
Number of sent CAN-Messages
CAN telegrams received
Number of received CAN-Messages
Number of detected CAN errors
Number of detected CAN errors
Bauderate
Baud rate of CANopen connection
Available Baud Rate:
1 MBaud
800 KBaud
500 KBaud
250 KBaud
125 KBaud
100 KBaud
50 KBaud
20 KBaud
10 KBaud
Table 74: Extended Diagnosis > CANOPEN_SLAVE > Common Diagnostic
netSLAVE DTM
6.12.1.2
Commands
Figure 62: Extended Diagnosis > CANOPEN_SLAVE > Commands n
netSLAVE DTM
Name
Description
[Service]
manual.)
Get packet
failed
Send packet
failed
Table 75: Extended Diagnosis > CANOPEN_SLAVE > Commands
netSLAVE DTM
6.12.2
6.12.2.1
CANOPEN_APS
Slave configuration
Figure 63: Extended Diagnosis > CANOPEN_APS > Slave Configuration
Name
Description
Flags
Bit0
set: Configuration data base found
not set: No configuration data base found
Bit1
set: Configuration by packets
not set: No packets for configuration
Database
found
Yes: Configuration data base found
No: No configuration data base found
Warmstart
configuration
Yes: Configuration by packets
No: No packets for configuration
Initialization
state
0 = Idle;
1 = Send initialize request;
2 = Wait for initialize confirmation;
3 = Send register request;
4 = Wait for register confirmation;
5 = Send get buffer request;
6 = Wait for get buffer confirmation;
7 = Send bus parameter request;
8 = Wait for bus parameter confirmation;
9 = Complete;
10 = Failed
Initialization
result
Fehlercode der Initialisierung, 0 = kein Fehler
Table 76: Extended Diagnosis > CANOPEN_APS > Slave Configuration
netSLAVE DTM
6.12.2.2
Commands
Figure 64: Extended Diagnosis > CANOPEN_APS > Commands
Name
Description
[Service]
manual.)
Get packet
failed
Send packet
failed
Table 77: Extended Diagnosis > CANOPEN_APS > Commands
Online Functions • 112
netSLAVE DTM
7
7.1
Online Functions
Connecting/Disconnecting Device
Note: Several netSLAVE DTM functions e. g. Diagnosis or the
configuration download in the FDT Framework require an online
connection from the netSLAVE DTM to the NETX Slave device .
Connecting Device
Requirements:
(The firmware is loaded
to the device using
the
program
The following steps are needed to establish a connection from the
netSLAVE DTM to a NETX Slave device :
Under Settings in the Driver pane:
Under Settings in the Device Assignment pane:
3. Scan for the device/s (with firmware).
An overview of the descriptions for these steps you find in the section
Overview Settings on page 20.
5. In the DTM interface dialog select the OK button, to apply the selection
and to close the DTM interface dialog.
6. Put a right-click on the NETX Slave device icon.
7. Select the Connect command from the context menu.
° Now the NETX Slave device is online.
° The NETX Slave device now is connected to the netSLAVE DTM via
an online connection. In the network view the device description at the
device icon is displayed with a green colored background.
netSLAVE DTM
Disconnecting Device
To disconnect an online connection from the NETX Slave device
netSLAVE DTM take the following steps:
to a
1. In the DTM interface dialog select the OK button, to close the DTM
interface dialog.
2. Right-click on the NETX Slave device icon.
3. Select the Disconnect command from the context menu.
° Now the NETX Slave device is disconnected from the DTM.
7.2
Download Configuration
Note: To download configuration parameter data to the NETX Slave
device an online connection from the netSLAVE DTM to the NETX Slave
device is required.
Further information can be found in the Connecting/Disconnecting Device
section on page 112.
To transfer the configuration with the corresponding parameter data to the
NETX Slave device you download the data to it using the frame application
of the configuration software.
netSLAVE DTM
7.3
License
In the License pane you can:
• check, which licenses are present in the device,
• order licenses,
• transfer license files to the device.
Figure 65: License Pane
netSLAVE DTM
7.3.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
netSLAVE DTM
7.3.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.3.2.1
Assigning the Device to the DTM
Note: You first need to assign the 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 icon.
¾ Select Settings > Driver in the navigation area.
¾ In the Driver pane check the checkbox for the driver/s.
¾ 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.
¾ 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 20.
netSLAVE DTM
7.3.2.2
Selecting the License
1. Open the License pane:
¾ Therefore open the the context menu, via right mouse click to the
device icon.
¾ From the context menu select Additional Functions > License.
In the License pane:
¾ Under License click to the Master Protocols folder to expand it.
¾ In the column Order check the checkbox for the desired number of
licenses:
1 General Master License or 2 General Master Licenses.
And/Or:
2. Under License click to the Utilies folder to expand it.
3. In the column Order check the checkbox for:
SYCON.net, OPC Server, QVis or CoDeSys.
netSLAVE DTM
7.3.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
netSLAVE DTM
7.3.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 66: Example: ordering E Mail License request
¾ Send the ordering E Mail License request.
° The order process is complete.
netSLAVE DTM
7.3.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 67: 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.
netSLAVE DTM
7.3.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.
¾ 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.
Error Numbers • 122
netSLAVE DTM
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.
netSLAVE DTM
8.2
Overview Error Numbers
Module
Error Code Region
General Hardware Error Codes/
RCX Operating System
RCX Errors - MID_SYS Task Error Codes: 0xC02B0001L to
0x8004BFFF to 0xC02B4B54L
RCX Errors - Common Status Codes: 0x00000000L to
0xC000F006L
RCX Errors - Status & Error Codes: 0x00000000L to
0xC0000008
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 78: Error Code Regions
The fieldbus specific error codes are described in the manuals of the
corresponding protocol tasks.
netSLAVE DTM
8.3
8.3.1
General Hardware Error Codes
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_
ROUTER_IN_TABLE
0xC02B000BL
No such 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_
DENIED_IN_LOCKED_STATE
0xC02B001AL
Access denied due to current
operating conditions.
TLR_E_MID_SYS_INVALID_ FIRMWARE_SIZE
0xC02B001BL
Firmware does not fit into flash.
TLR_E_MID_SYS_MODULE_
RELOCATION_DISTANCE_ TOO_LONG
0xC02B001CL
The relocation distance is too
long.
More see next page
netSLAVE DTM
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_
INVALID
0xC02B4444L
File Transfer Packet invalid.
TLR_E_MID_SYS_FILE_TRANSFER_
NOT_ACTIVE
0xC02B5342L
File Transfer is not active.
TLR_E_MID_SYS_FILE_TRANSFER_ INVALID
0xC02B5257L
File Transfer has invalid type
code.
TLR_E_MID_SYS_FILE_CRC_
REPEATEDLY_WRONG
0xC02B4352L
File Transfer was tried
repeatedly with a wrong CRC.
TLR_E_MID_SYS_FILE_TRANSFER_
TYPE_NOT_AVAILABLE
0xC02B4353L
Transfer Type is not available.
TLR_E_MID_SYS_PATH_INVALID
0xC02B5555L
File Path submitted in File
Transfer was invalid.
TLR_E_MID_SYS_DRIVER_
CFG_TABLE_INIT_FUNCTION_ MISSING
0xC02BFFFFL
Driver Configuration Table Init
Function missing.
TLR_E_MID_SYS_CONFIGURATION_ LOCKED
0xC02B4B54L
Configuration has been locked.
Table 79: RCX Errors - MID_SYS Task Error Codes (from Operating System)
netSLAVE DTM
8.3.2
RCX Errors - Common Status Codes
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 80: RCX Errors - Common Status Codes (from Operating System)
netSLAVE DTM
8.3.3
RCX Errors - Status & Error Codes
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 81: RCX Errors - Status & Error Codes (from Operating System)
8.3.3.1
RCX Errors - Status & Error Codes – Slave State
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 82: RCX Errors - Status & Error Codes – Slave State (from Operating System)
netSLAVE DTM
8.4
8.4.1
ODM Error Codes
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_COMCATEGORIE_
MANAGER_FAILED
0x8004C712
Component Category Manager
could not be instantiated
CODM3_E_COMCATEGORIE_
ENUMERATION_FAILED
0x8004C713
Driver could not be enumerated
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_
THREAD_STOP_EVENT
0x8004C751
Error creating device thread stop
event
CODM3_E_CLIENT_NOT_ REGISTERED
0x8004C752
Client is not registered at the
ODM
CODM3_E_NO_MORE_ CLIENTS
0x8004C753
Maximum number of clients
reached
CODM3_E_MAX_CLIENT_
CONNECTIONS_REACHED
0x8004C754
Maximum number of client
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 83: ODM Error Codes - General ODM Error Codes
netSLAVE DTM
8.4.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_
PARAMETERS_MISMATCH
0x8004C7A3
Parameters differ from requested
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 84: ODM Error Codes - General ODM Driver Error Codes
netSLAVE DTM
8.4.3
ODM cifX Driver Specific Errors
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
netSLAVE DTM
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
0x8004C034
DMA Write I/O timeout
0x8004C035
DMA PCI transfer timeout
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
netSLAVE DTM
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
load firmware file
DRV_E_FW_FILE_NO_ MEMORY
0x8004C070
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
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
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
More see next page
netSLAVE DTM
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 85: ODM CifX Driver Specific Errors
netSLAVE DTM
8.5
Error Codes cifX Device Driver
Note: The cifX Device Driver is not available for all devices.
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
netSLAVE DTM
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 86: Error Codes cifX Device Driver
netSLAVE DTM
8.6
ODM DBM V4 Error Codes
Value
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
_IN_OLD_HEADER_FORMAT
0XC004C813
Error in a file containing the
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_
FORMAT
0XC004C818
Unsupported DataType
CDBM_W_CLASS_DELETED _FORMAT
0X8004C819
Using an Object which is
marked as deleted
(Warning)
CDBM_W_CLIENT_ DISCONNECTED
0X8004C81A
(Warning)
Description
A Client has already an
outstanding connection to a
Table. The connection is now
destroyed.
CDBM_E_STRUCTURE_ DEFINITION_INVALID
0XC004C81B
A structure definition of an
Element in a Table is invalid
CDBM_E_NO_DATA_AVAILABLE
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
_INTO_CLIENT_TYPE
0XC004C821
The data can't be converted
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
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
(Informational)
More see next page
netSLAVE DTM
Value
CDBM_E_NO_MORE_RECORDS
_IN_TABTYPE
0XC004C82C
Table type 3 can contain only
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_
STRUCTURE_WHILE_ RECORDS_EXIST
0XC004C83B
It's not allowed to change the
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_UN SUPPORTED_IN_RCS
0XC004C83E
The data type is unsupported
in the RCS file format
CDBM_I_COUNT_OF_TABLES _EXCEEDS_
RCS_RANGE
0X4004C83F
The count of Tables exceeds
the RCS range of Tables. This
can cause problems if the file
is downloaded to RCS
Systems
(Informational)
Description
More see next page
netSLAVE DTM
Value
CDBM_I_COUNT_OF_TABLES
_EXCEEDS_OLDDBM_RANGE
0X4004C840
CDBM_UNSUPPORTED_DATATYPE
_IN_RCS_MODE
0XC004C841
The Data type is not
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_
IS_EMPTY_STRING
0XC004C850
The toggle string for this
value is empty.
CDBM_VARIANT2BYTEARRAY _ERROR
0XC004C851
Error during conversion of
Variant to byte array
(Informational)
Description
The count of Tables exceeds
the DBM32.DLL range of
Tables. This can cause
problems if the file is used
with older Tools using the
DBM32.DLL
More see next page
netSLAVE DTM
Value
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_
DOESNT_CORRESPOND_ WITH_ELEMENT
0XC004C853
When reading the records of
Table type 1 elementwise the
record number must
correspond with the element
number
CDBM_TABTYPE1_NO_DATA_
FOUND_FOR_RECORD
0XC004C854
When reading the records of
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_
ELEMENT_NE_RECORD
0XC004C855
When writing the records of
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_
ELEMENT_NOT_FOUND
0XC004C856
When writing the records of
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_
EXCEEDS_RCS_RANGE
0X4004C857
The Table name exceeds the
maximum length of RCS
compatible Table names
CDBM_W_CUT_STRING
0X8004C858
(Informational)
(Warning)
CDBM_I_STRING_TOO_ SHORT
0X4004C859
(Informational)
CDBM_I_STRING_TOO_ LONG
0X4004C85A
(Informational)
CDBM_E_STRING_TOO_ SHORT
0XC004C85B
(Error)
Description
The string exceeds the
maximum length and will be
limited to the maximum length
The string is below the
minimum length. The
minimum length will be
reduced.
The string is exceeding the
maximum. The maximum
length will be extended.
The string is below the
minimum length.
The string is exceeding the
maximum length
CDBM_E_STRING_TOO_ LONG
0XC004C85C
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_
STRUCTURED_RECORDS
0XC004C85E
Method
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
(Error)
More see next page
netSLAVE DTM
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_
TABLE_DOESNT_SUPPORT _LENGTH
0XC004C86A
A Table without structure
information doesn’t support a
record length
CDBM_E_DISABLED_WHILE_ TRANSACTION_
IS_OPEN
0XC004C86B
The Method is disabled while
a transaction is open. Please
close this one first and call
the Method again.
CDBM_E_UNABLE_TO_CALL_
READ_ON_LINKED_LIST
0XC004C86C
The Method is disabled on a
LinkedList type. Please use
the IRecordCollection on this
type.
CDBM_E_ELEMENT_HAS_
NO_SUBSTRUCTURE
0XC004C86D
An Element from a Table has
no substructure
CDBM_STRUCT_ERROR_
FROM_VAR_CHANGE_TYPE
0XC004C86E
Error from calling
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
netSLAVE DTM
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 87: ODM DBM V4 Error Codes
netSLAVE DTM
9
9.1
Lists • 142
Lists
List of Figures
Figure 1: Dialog Structure of netSLAVE DTM
12
Figure 2: Navigation Area
13
Figure 3: Status Bar – Status Fields 1 to 6
16
Figure 4: Status Bar Display Examples
16
Figure 5: Navigation Area - Settings
20
Figure 6: Driver Selection List
21
Figure 7: Driver Selection List - recognized or installed Drivers
21
Figure 8: Driver Selection List - Driver/s selected
21
Figure 9: Navigation Area – Settings
22
Figure 10: Device Assignment - Selecting the Device (* The name of the device class is displayed.) –
24
Example for a device with firmware/one Device is selected
Figure 11: Navigation Area - Configuration
25
Figure 12: netX Configuration Tool - Configuration Pane
25
Figure 13: Navigation Area - Diagnosis
50
Figure 14: Firmware Diagnosis Example PROFINET IO Device (*The name of the Firmware is displayed.) 51
Figure 15: General Diagnosis
52
55
Figure 17: Extended Diagnosis > [Folder Name] > Task Information Example Display
63
Figure 18: Extended Diagnosis > [Folder Name] > IniBatch Status Example Display
64
Figure 19: Extended Diagnosis > [Folder Name] > Code Diagnosis Example Display EtherNet/IP Adapter 65
Figure 20: Extended Diagnosis > [Folder Name] > IP Information Example Display EtherNet/IP Adapter 66
Figure 21: Extended Diagnosis > [Folder Name] > IP Packet Counter Example Display EtherNet/IP Adapter
67
Figure 22: Extended Diagnosis > [Folder Name] > IP-Code Diagnosis Example Display EtherNet/IP Adapter
68
Figure 23: Extended Diagnosis > [Folder Name] > TCP_UDP-Information Example Display EtherNet/IP
69
Adapter
Figure 24: Extended Diagnosis > [Folder Name] > TCP_UDP Code Diagnosis Example Display EtherNet/IP
70
Adapter
Figure 25: Navigation Area - Extended Diagnosis EtherNet/IP Adapter
71
Figure 26: Extended Diagnosis > EIS_ENCAP_TASK > Encap Command Counter
72
Figure 27: Extended Diagnosis > EIS_ENCAP_TASK > Packet Counter
73
Figure 28: Extended Diagnosis > EIS_OBJECT_TASK > Object Request Counter
74
Figure 29: Extended Diagnosis > EIS_OBJECT_TASK > Outgoing Connection
75
Figure 30: Extended Diagnosis > EIS_OBJECT_TASK > Ingoing Connection
75
Figure 31: Extended Diagnosis > EIS_AP_TASK > Common Diagnostic
76
Figure 32: Extended Diagnosis > EIS_AP_TASK > General State
76
77
Figure 34: Extended Diagnosis > OMB > OMB Information
78
Figure 35:Extended Diagnosis > OMB > OMB Client
79
Figure 36:Extended Diagnosis > OMB > OMB Server
80
Figure 37:Extended Diagnosis > OMB > OMB IO
81
Figure 38:Extended Diagnosis > OMB > OMB Code Diagnosis Example Display
82
Figure 39: Navigation Area - Extended Diagnosis PROFINET IO Device
83
Figure 40: Extended Diagnosis > PNS_IF > PROFINET Stack State
84
Figure 41: Extended Diagnosis > PNS_IF > Station Description
85
86
87
Figure 44:Extended Diagnosis > PROFIBUS_FSPMS > Extended Diagnosis
88
netSLAVE DTM
Lists • 143
Figure 45:Extended Diagnosis > PROFIBUS_FSPMS > Config Data
Figure 46:Extended Diagnosis > PROFIBUS_FSPMS > Parameter Data
Figure 48: Extended Diagnosis > CCLINK_SLAVE > Configuration
Figure 49: Extended Diagnosis > CCLINK_SLAVE > Commands
Figure 50: Extended Diagnosis > CCLINK_SLAVE > Interrupts
Figure 51: Extended Diagnosis > CCLINK_SLAVE > XC receive area
Figure 52: Extended Diagnosis > CCLINK_SLAVE > XC config area
Figure 53: Extended Diagnosis > CCLINK_SLAVE > XC status area
Figure 54: Extended Diagnosis > CCLINK_SLAVE > XC management area
Figure 55: Extended Diagnosis > CCLINK_SLAVE > XC triple buffer area
Figure 56: Extended Diagnosis > CCLINK_SLAVE > XC reserved area
Figure 57: Extended Diagnosis > CCLINK_APS > Slave Configuration
Figure 58: Extended Diagnosis > CCLINK_APS > Commands
Figure 59: Extended Diagnosis > CCLINK_APS > DPM data exchange
Figure 61: Extended Diagnosis > CANOPEN_SLAVE > Common Diagnostic
Figure 62: Extended Diagnosis > CANOPEN_SLAVE > Commands n
Figure 63: Extended Diagnosis > CANOPEN_APS > Slave Configuration
Figure 64: Extended Diagnosis > CANOPEN_APS > Commands
Figure 65: License Pane
Figure 66: Example: ordering E Mail License request
Figure 67: Example: order data form netX License Order Form
9.2
89
90
91
92
94
95
96
97
98
99
101
102
103
104
105
106
107
108
110
111
114
119
120
List of Tables
Table 1: Descriptions Dialog Panes
Table 2: General Device Information
Table 3: Hide/display Navigation
Table 4: Overview Dialog Panes
Table 5: General Buttons
Table 6: Table Line – Buttons
Table 7: Status Bar Icons [1]
Table 8: Getting Started - Configuration Steps
Table 9: Descriptions Settings
Table 10: Driver Selection List Parameters
Table 11: Parameters of the Device Assignment
Table 12: Error during Data Input
Table 13: Descriptions Configuration Parameters Real-Time Ethernet Systems or Fieldbus Systems
Table 14: EtherCAT Slave Parameters
Table 15: EtherNet/IP Adapter Parameters
Table 16: Open Modbus/TCP Parameters
Table 17: Powerlink Controlled Node/Slave Parameters
Table 18: PROFINET IO-Device Parameters
Table 19: SERCOS III Slave Parameters
Table 20: Parameters - PROFIBUS-DP Slave
Table 21: CANopen Slave Parameters
Table 22: DeviceNet Slave Parameters
Table 23: CompoNet Slave Parameters
Table 24: CC-Link Slave Parameters
Table 25: Descriptions of the Diagnosis Panes
Table 26: Description Table Task Information
5
13
13
14
15
15
16
18
20
21
23
25
26
28
31
33
35
37
38
40
42
44
47
49
50
51
netSLAVE DTM
Lists • 144
Table 27: Indication General Diagnosis
Table 28: Parameter General Diagnosis
Table 29: Overview Extended Diagnosis
Table 30: Descriptions of the Dialog Panes Extended Diagnosis EtherNet/IP Adapter
Table 31: Descriptions of the Dialog Panes Extended Diagnosis Open Modbus/TCP
Table 32: Descriptions of the Dialog Panes Extended Diagnosis PROFINET IO Device
Table 33: Descriptions of the Dialog Panes Extended Diagnosis SERCOS III
Table 34: Descriptions of the Dialog Panes Extended Diagnosis PROFIBUS Slave
Table 35: Descriptions of the Dialog Panes Extended Diagnosis CC-Link Slave
Table 36: Descriptions of the Dialog Panes Extended Diagnosis CANopen Slave
Table 37: Extended Diagnosis > [Folder Name] > Task Information
Table 38: Extended Diagnosis > [Folder Name] > IniBatch Status
Table 39: Extended Diagnosis > [Folder Name] > Code Diagnosis
Table 40: Extended Diagnosis > [Folder Name] > IP Information
Table 41: Extended Diagnosis > [Folder Name] > IP Packet Counter
Table 42: Extended Diagnosis > [Folder Name] > IP-Code Diagnosis
Table 43: Extended Diagnosis > [Folder Name] > TCP_UDP-Information
Table 44: Extended Diagnosis > [Folder Name] > TCP_UDP Code Diagnosis
Table 45: Extended Diagnosis > EIS_ENCAP_TASK > Encap Command Counter
Table 46: Extended Diagnosis > EIS_ENCAP_TASK > Packet Counter
Table 47: Extended Diagnosis > EIS_OBJECT_TASK > Object Request Counter
Table 48: Extended Diagnosis > EIS_OBJECT_TASK > Outgoing Connection
Table 49: Extended Diagnosis > EIS_OBJECT_TASK > Ingoing Connection
Table 50: Extended Diagnosis > EIS_AP_TASK > Common Diagnostic
Table 51: Extended Diagnosis > EIS_AP_TASK > General State
Table 52: Extended Diagnosis > OMB > OMB Information
Table 53: Extended Diagnosis > OMB > OMB Client
Table 54: Extended Diagnosis > OMB > OMB Server
Table 55: Extended Diagnosis > OMB > OMB IO
Table 56: Extended Diagnosis > OMB > OMB Code Diagnosis
Table 57: Extended Diagnosis > PNS_IF > PROFINET Stack State
Table 58: Extended Diagnosis > PNS_IF > Station Description
Table 59: Extended Diagnosis > PROFIBUS_FSPMS > Extended Diagnosis
Table 60: Extended Diagnosis > PROFIBUS_FSPMS > Config Data
Table 61: Extended Diagnosis > PROFIBUS_FSPMS > Parameter Data
Table 62: Extended Diagnosis > CCLINK_SLAVE > Configuration
Table 63: Extended Diagnosis > CCLINK_SLAVE > Commands
Table 64: Extended Diagnosis > CCLINK_SLAVE > Interrrupts
Table 65: Extended Diagnosis > CCLINK_SLAVE > XC receive area
Table 66: Extended Diagnosis > CCLINK_SLAVE > XC config area
Table 67: Extended Diagnosis > CCLINK_SLAVE > XC status area
Table 68: Extended Diagnosis > CCLINK_SLAVE > XC management area
Table 69: Extended Diagnosis > CCLINK_SLAVE > XC triple buffer area
Table 70: Extended Diagnosis > CCLINK_SLAVE > XC reserved area
Table 71: Extended Diagnosis > CCLINK_APS > Slave Configuration
Table 72: Extended Diagnosis > CCLINK_APS > Commands
Table 73: Extended Diagnosis > CCLINK_APS > DPM data exchange
Table 74: Extended Diagnosis > CANOPEN_SLAVE > Common Diagnostic
Table 75: Extended Diagnosis > CANOPEN_SLAVE > Commands
Table 76: Extended Diagnosis > CANOPEN_APS > Slave Configuration
Table 77: Extended Diagnosis > CANOPEN_APS > Commands
Table 78: Error Code Regions
Table 79: RCX Errors - MID_SYS Task Error Codes (from Operating System)
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
72
73
74
75
75
76
76
78
79
80
81
82
84
85
88
89
90
93
94
95
96
97
98
100
101
102
103
104
105
107
109
110
111
123
125
netSLAVE DTM
Lists • 145
Table 80: RCX Errors - Common Status Codes (from Operating System)
Table 81: RCX Errors - Status & Error Codes (from Operating System)
Table 82: RCX Errors - Status & Error Codes – Slave State (from Operating System)
Table 83: ODM Error Codes - General ODM Error Codes
Table 84: ODM Error Codes - General ODM Driver Error Codes
Table 85: ODM CifX Driver Specific Errors
Table 86: Error Codes cifX Device Driver
Table 87: ODM DBM V4 Error Codes
Table 88: Settings (D = Displaying, X = Editing, Configuring)
Table 89: Configuration (D = Displaying, X = Editing, Configuring)
126
127
127
128
129
133
135
141
150
150
Glossary • 146
netSLAVE DTM
10 Glossary
Auto-Negotiation
Auto-Negotiation is a feature of an interface: An interface with AutoNegotiation will automatically determine a set of correct communication
parameters.
Baud rate
Data transmission speed of a communication channel or interface.
Coil
A coil (in the meaning defined by Modbus terminology) is a single bit in
memory that can be accessed (i.e. read or write) via Modbus.
CIFX
Communication InterFace based on netX
CSP
electronic device data sheet, required for each CC-Link device
Device Description File
A file containing configuration information about a device being a part of a
network that can be read out by masters for system configuration. Device
Description Files use various formats which depend on the communication
system. Often these formats are based on XML such as EDS_files or
GSDML_files. Contains configuration information
DPM
Dual-Port Memory
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.
EDS
Electronic Data Sheet
XML based device description file.
EDS file
A special kind of Device Description File used by EtherNet/IP.
EtherCAT
A communication system for industrial Ethernet designed and developed by
Beckhoff Automation GmbH.
EtherNet/IP
Rockwell. It partly uses the CIP (Common Industrial Protocol).
Glossary • 147
netSLAVE DTM
Ethernet Powerlink
B&R. It partly uses CANopen technologies.
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.
Full duplex
Full duplex denominates a telecommunication system between two
communication partners which allows simultaneous communication in both
directions is called a full-duplex telecommunication system. At such a
system, it is possible to transmit data even if currently data are received.
Full-duplex is the opposite of Half_duplex.
Function code
A function code (in the meaning defined by Modbus terminology) is a
standardized method to access (i.e. read or write) coils or registers via
Modbus.
Gateway
A device interfacing between two different communication standards.
GSD
General Station Description, Device description file
GSD file
A special kind of Device Description File used by PROFIBUS (GSD =
General Station Description).
GSDML
General Station Description Markup Language
XML based device description file.
GSDML file
A special kind of XML-based Device Description File used by PROFINET.
Half duplex
Half duplex denominates a telecommunication system between two
communication partners which does not allow simultaneous, but
alternating, communication in both directions is called a half-duplex
telecommunication system. At such a system, receiving data inhibits the
transmission of data. Half-duplex is the opposite of _Full_duplex.
Hub
A network component connecting multiple communication partners with
each other. A hub does not provide own intelligence, thus it does not
analyze the data traffic and sends received data to all connected
communication partners. A hub can be used for setting up a star topology.
Glossary • 148
netSLAVE DTM
Industrial Ethernet
See Real-Time Ethernet
Master
Master devices initiate the data traffic on the bus. In the communication
protocol Master devices are called active participants. A master may send
messages without external request.
netX
networX on chip, next generation of communication controllers
Object Dictionary
An object dictionary is a storage area for device parameter data structures.
It is accessed in standardized manner.
Open Modbus/TCP
A communication system for Industrial Ethernet designed and developed by
Schneider Automation and maintained by the Modbus-IDA organization
based on the Modbus protocols for serial communication.
PROFINET
A communication system for Industrial Ethernet designed and developed by
PROFIBUS International. It uses some mechanisms similar to those of the
PROFIBUS field bus.
RE
RE stands for Real Time Ethernet
Real-Time Ethernet
Real-Time Ethernet (Industrial Ethernet) is an extension of the Ethernet
networking technology for industrial purposes with very good Real-Time
features and performance. There is a variety of different Real-Time
Ethernet systems on the market which are incompatible with each other.
The most important systems of these are
•
EtherCAT
•
EtherNet/IP
•
Ethernet Powerlink
•
Open Modbus/TCP
•
PROFINET
•
SERCOS III
Register
A register (in the meaning defined by Modbus terminology) is a 16-bit wide
storage area for data which can be accessed and addressed as a unit by
some of the Modbus Function Codes.
Glossary • 149
netSLAVE DTM
SERCOS III
Bosch-Rexroth and supported by SERCOS International.
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.
Switch
A network component connecting multiple communication partners (or even
entire branches of a network) with each other. A switch is an intelligent
network component which analyzes network traffic in order to decide on its
own. For the connected communication partners a switch behaves
transparently.
SYNC
Sychronisation cycle of the master
TCP/IP
Transport Control Protocol/Internet Protocol connection-orientated, secure
transfer protocol as basis for the Internet-protocols
Watchdog Timer
A watchdog timer provides an internal supervision mechanism of a
communication system. It supervises that an important event happens
within a given timeframe (the watchdog time which can be adjusted
accordingly, for instance by a parameter in the _Warmstart message) and
causes an alarm otherwise (usually this is accomplished by changing the
operational state of the communication system to a more safe state).
XDD file
A special kind of Device Description file used by Ethernet Powerlink.
XML
XML means Extended Markup Language. It is a symbolic language for
structuring data systematically. XML is standard maintained by the W3C
(World-wide web consortium). Device Description Files often use XMLbased formats for storing the device-related data appropriately.
Appendix • 150
netSLAVE DTM
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
netSLAVE 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
e
Planning
Engineer
Administrator
D
D
X
X
X
-
-
X
X
X
-
-
X
X
X
D
D
X
X
X
-
-
X
X
X
-
-
X
X
X
Driver
Device Assignment
Selecting the Device (with
firmware)
Table 88: Settings (D = Displaying, X = Editing, Configuring)
11.1.2
Configuration
Observer
Configuration
D
Operator
D
Maintenanc
e
Planning
Engineer
X
Administrator
X
Table 89: Configuration (D = Displaying, X = Editing, Configuring)
X
Appendix • 151
netSLAVE DTM
11.2 References
[1]
Device Type Manager (DTM) Style Guide, Version 1.0 ; FDT-JIG - Order No.
<0001-0008-000>
[2]
EtherNetIP Adapter Protocol API, Revision 5
[3]
Open Modbus/TCP Protocol API, Revision 3
[4]
PROFINET IO RT Device Protocol API, Revision 11
[5]
SERCOS III Slave Protocol API, Revision 5
[6]
PROFIBUS-DP Slave Protocol API, Revision 7
[7]
CC-Link Slave Protocol API, Revision 2
[8]
CANopen Slave Protocol API, Revision 3
Appendix • 152
netSLAVE DTM
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
Subsidiaries
China
Japan
Hilscher Ges.f.Systemaut. mbH
Shanghai Representative Office
200010 Shanghai
Phone: +86 (0) 21-6355-5161
Hilscher Japan KK
Tokyo, 160-0022
Phone: +81 (0) 3-5362-0521
Support
Phone: +81 (0) 3-5362-0521
Phone: +86 (0) 21-6355-5161
Support
France
Switzerland
Hilscher France S.a.r.l.
69500 Bron
Phone: +33 (0) 4 72 37 98 40
Hilscher Swiss GmbH
4500 Solothurn
Phone: +41 (0) 32 623 6633
Support
Support
Phone: +33 (0) 4 72 37 98 40
Phone: +49 (0) 6190 9907-99
India
Hilscher India Pvt. Ltd.
New Delhi - 110 025
Phone: +91 9810269248
USA
Italy
Support
Hilscher Italia srl
20090 Vimodrone (MI)
Phone: +39 02 25007068
Phone: +1 630-505-5301
Hilscher North America, Inc.
Lisle, IL 60532
Phone: +1 630-505-5301
Support
Phone: +39/02 25007068

netSLAVE DTM

Transcription

Similar documents

Reference as PDF

Apresentação do PowerPoint

Reference project – infrastructure / drainage

Supplemental First Diagnosis Cancer Benefit Policy

Credibility Breadth and depth Ease of use What is STATdx™?

Why the client is attracted to a counter

【公告】影像資料庫Statdx，開放試用!(即日起至2016/10/06)。

Transatlantic Slave Trade

Ultrasound in Tropical Diseases