Bosch Rexroth ID 40 User manual

PORTUGUESA ESPAÑOL ITALIANO FRANÇAIS ENGLISH DEUTSCH
3 842 530 344/2014-05
Replaces: 2014-01
EN
Manual
ID 40
4.1
Edition

2/176
Bosch Rexroth AG, MIT: ID 40, 3 842 530 344/2014-05
The data specified only serve to describe
the product. No statements concerning
a certain condition or suitability for a
certain application can be derived from our
information. The information given does
not release the user from the obligation of
own judgment and verification. It must be
remembered that our products are subject
to a natural process of wear and aging.
This document, as well as the data,
specifications and other information set
forth in it, are the exclusive property of
Bosch Rexroth AG. It may not be
reproduced or given to third parties
without the consent of Bosch Rexroth AG.
This manual was originally written in
German.
PROOF COPY 1 | 20.05.2014 | FOR INTERNAL USE ONLY

3/176
3 842 530 344/2014-05, MIT: ID 40, Bosch Rexroth AG
Inhalt
1 About this manual 9
1.1 Scope of Application 9
1.2 Layout of this manual 9
1.3 Display 10
1.3.1 Numbers 10
1.3.2 Operating states 10
1.3.3 Information 10
1.4 Safety instructions 11
1.5 New in the 4.x versions of the ID 40/SLK software 11
2 Introduction 12
2.1 ID 40/MDT mobile data tag 12
2.2 ID 40/SLK read/write head 13
2.2.1 SLK operating states 14
2.2.2 Status display 18
2.3 Data transmission between SLK and MDT 20
2.3.1 Position of MDT and SLK during data transmission 20
2.3.2 Static and dynamic data transmission 21
2.3.3 Direct and parameterized data transmission 22
2.3.4 Securing data transmission 22
3 Installing MDT and SLK 23
3.1 Mounting the MDT on the workpiece pallet 23
3.2 Mounting the SLK on transfer section profiles 23
3.3 Antenna orientation 24
3.4 SLK electrical connection 25
3.4.1 Supply voltage 25
3.4.2 Connecting the fieldbus 26
3.4.3 Serial interface 27
3.4.4 Turning on the SLK 28
4 MDT memory structure 29
4.1 ID 40/MDT storage 29
4.2 Organization of MDT memory 30
4.2.1 MDT user data area 31
4.2.2 MDT system data area 31
4.2.3 MDT register area 32
5 SLK memory structure 34
5.1 Map of MDT user data area 35
5.2 Map of MDT register area 35
5.2.1 Map of MDT status register 35
5.2.2 Map of MDT pointer registers 35
5.2.3 Map of MDT ID code 35
5.2.4 MDT counter 35
5.2.5 MDT formatting 35
5.2.6 Map of MDT software version 37
5.3 SLK register area 37
5.3.1 Actual link state 37
5.3.2 Commanded link state 38
PROOF COPY 1 | 20.05.2014 | FOR INTERNAL USE ONLY
ENGLISH

4/176
Bosch Rexroth AG, MIT: ID 40, 3 842 530 344/2014-05
5.3.3 Auto mode 38
5.3.4 SLK operative flag 39
5.3.5 Look ahead function 39
5.3.6 SLK device information 39
6 Accessing data on the ID 40/MDT 40
6.1 Command-oriented data transmission 40
6.2 Event-oriented data transmission 40
6.3 Direct data exchange with MDT 40
6.4 Parameterized data exchange with MDT 41
6.4.1 Prefetch 41
6.4.2 Pretransmit 42
6.5 Default process for SLK-MDT communication 44
6.6 “Open transfer” and “Close transfer” functions 44
6.7 Auto reconnect function 45
6.8 Auto disconnect function 46
6.9 MDT lifeguarding 47
7 Profibus DP 49
7.1 Overview 49
7.2 Command-oriented data exchange 49
7.2.1 Profibus commands 52
7.3 Event-oriented data exchange 54
7.3.1 Status information in event-oriented data channel 54
7.3.2 Data array for event-oriented data channel 55
7.4 SLK address table 56
7.5 Profibus error codes 57
7.6 Profibus Diagnostic Service 57
7.7 Addressing data in the ID 40 system 58
7.8 Profibus GSD file 59
7.8.1 Distribution of SLK module configuration 59
7.8.2 Sample I/O module configuration 59
7.9 Sample applications 60
7.9.1 “Manual workstation” application 60
7.9.2 “Outfeed” application 62
7.9.3 “Workstation” application 63
7.9.4 “Resetting SLK” application 65
7.9.5 Handling “E00” errors 65
8 Interbus 66
8.1 Overview 66
8.2 Addressing data in the ID 40 system 66
8.3 Command-oriented data exchange 67
8.3.1 PCP communication 68
8.3.2 PCP channel objects 69
8.3.3 Example: writing bytes to MDT 71
8.4 Event-oriented data exchange 72
8.4.1 Status information in the process data channel 72
8.4.2 Data array for event-oriented data channel 73
8.5 Commanded link state via process data channel 74
8.5.1 Output map structure 74
8.5.2 Sample sequence 74
PROOF COPY 1 | 20.05.2014 | FOR INTERNAL USE ONLY

5/176
3 842 530 344/2014-05, MIT: ID 40, Bosch Rexroth AG
8.6 SLK address table 75
8.7 Interbus error codes 76
8.8 Sample applications 77
8.8.1 “Manual workstation” application 77
8.8.2 “Outfeed” application 79
8.8.3 “Workstation” application 80
8.8.4 “Resetting SLK” application 83
8.8.5 Handling “E00” errors 84
9 CANopen 85
9.1 Overview 85
9.2 Object directory 85
9.3 Command-oriented data exchange 86
9.4 Event-oriented data exchange 86
9.5 MDT data transmission with transfer buffers 87
9.5.1 Transfer buffer parameters (objects 2100–2103) 88
9.5.2 Object mapping in the transfer buffer (objects 2110–2113) 89
9.5.3 SLK address table 91
9.5.4 Transfer buffers (objects 2120–2123) 92
9.5.5 Direct data exchange 92
9.5.6 Prefetch data exchange 92
9.5.7 Pretransmit data exchange 93
9.6 ID 40 objects (manufacturer-specific profile area) 94
9.6.1 Saving objects (saving parameters) 97
9.6.2 MDT user memory (objects 2200–220E) 97
9.6.3 SLK register area (object 2600) 97
9.6.4 MDT register area (object 2800) 97
9.7 Standardized device profile 98
9.8 SDO communication 98
9.8.1 SDO 1 98
9.8.2 SDO 2 99
9.8.3 SDO timeout client (object 2020) 99
9.9 PDO communication 100
9.9.1 PDO mapping 101
9.9.2 PDO communication parameters 103
9.9.3 PDO transmission types 104
9.9.4 Transmit PDO status (objects 2030 – 2033) 104
9.9.5 Receive PDO status (objects 2040 – 2041) 104
9.9.6 SYNC synchronization protocol 105
9.10 CANopen error codes 106
9.11 Emergency object protocol (EMCY) 106
9.12 NMT protocols 106
9.13 Error control protocols 106
9.14 Node guarding protocol 106
9.15 Heartbeat protocol 107
9.16 Boot-up protocol 107
9.17 Communication profile area 107
9.17.1 Device type (object 1000) 107
9.17.2 Error register (object 1001) 107
9.17.3 Manufacturer status register (object 1002) 107
PROOF COPY 1 | 20.05.2014 | FOR INTERNAL USE ONLY
ENGLISH

6/176
Bosch Rexroth AG, MIT: ID 40, 3 842 530 344/2014-05
9.17.4 Pre-defined error field (object 1003) 108
9.18 Electronic data sheet (EDS) 108
9.19 Overview of ID 40 CANopen support 108
9.20 Sample applications 110
9.20.1 “Manual workstation” application 110
9.20.2 “Outfeed” application 112
9.20.3 “Workstation” application 113
9.20.4 “Resetting SLK” application 116
9.20.5 Handling “E00” errors 116
10 Web interface 117
10.1 Overview 117
10.2 Requirements 117
10.3 Setting up the network connection to the ID 40/SLK 118
10.3.1 Setting up the connection via serial cable 118
10.3.2 Setting up a network connection 122
10.3.3 Establishing “ID 40” network connection 127
10.3.4 Terminating “ID 40” network connection 129
10.3.5 Troubleshooting PPP connection to ID 40/SLK 129
10.4 HTTP connection to ID 40/SLK 132
10.4.1 Troubleshooting the ID 40/SLK network connection 132
10.5 The ID 40/SLK website 136
10.5.1 Navigating and using the ID 40/SLK website 136
10.5.2 ID 40/SLK homepage 139
10.5.3 MDT register page 140
10.5.4 SLK register page 141
10.5.5 MDT data page 142
10.5.6 Fieldbus settings page 143
10.5.7 Systems statistics page 143
10.5.8 System log and settings page 144
10.6 Tips and tricks 145
10.6.1 Bookmarks 145
10.6.2 Directly retrieving the syslog 145
10.7 Web access from application programs 146
10.7.1 Web interface data formats 146
10.7.2 Web interface write commands 147
10.7.3 Web interface read commands 148
11 Start-up and parameterization 152
11.1 Starting up Profibus DP 152
11.1.1 Configuring through the web interface 152
11.1.2 Configuring with Profibus master 153
11.1.3 Starting the Profibus master 153
11.2 Starting up Interbus 153
11.2.1 Outgoing remote bus configuration 153
11.2.2 Configuring the maximum PDU size of the PCP channel 154
11.2.3 Configuring with the IBS CMD SWT G4 software 155
11.2.4 Showing Interbus status on the display 155
11.3 Starting up CANopen 156
11.3.1 Configuring the bus parameters 156
11.3.2 ID 40/SLK-CAN boot-up behavior 157
PROOF COPY 1 | 20.05.2014 | FOR INTERNAL USE ONLY

7/176
3 842 530 344/2014-05, MIT: ID 40, Bosch Rexroth AG
11.3.3 Showing CANopen status on the display 157
11.3.4 Configuring the second SDO channel 158
11.4 Adjusting the baud rate of the serial interface 158
12 Diagnostics 159
12.1 Troubleshooting guide 159
12.1.1 Important information that can indicate errors 159
12.1.2 Fatal system errors 159
12.1.3 Diagram of possible causes of errors 161
12.2 Diagnostics using the web interface 162
12.3 SLK software upgrade via serial interface 162
13 Technical data 163
13.1 Cables, connector pin assignments 164
13.2 SLK nameplate 165
13.3 Data transmission times between MDT and controller 166
13.3.1 Transmission times with Profibus 166
13.4 Compatibility 167
13.4.1 Compatibility with older software versions 167
13.4.2 Compatibility with ID 80/E and MTS 2 167
14 Overview for ordering ID 40 modules 168
15 Service and support 170
15.1 Technical support 170
15.2 Internet 170
15.3 Site 170
16 Appendix 171
16.1 ID 40 system link model 171
16.2 Abbreviations and terms 173
16.3 References 175
PROOF COPY 1 | 20.05.2014 | FOR INTERNAL USE ONLY
ENGLISH

8/176
Bosch Rexroth AG, MIT: ID 40, 3 842 530 344/2014-05
PROOF COPY 1 | 20.05.2014 | FOR INTERNAL USE ONLY

About this manual 9/176
3 842 530 344/2014-05, MIT: ID 40, Bosch Rexroth AG
1 About this manual
1.1 Scope of Application
This manual describes the following system components of the ID 40 identification
and data memory system:
•ID 40/MDT2K mobile data tag
•ID 40/MDT8K mobile data tag
•ID 40/MDT32K mobile data tag
•ID 40/SLK-PDP read/write head
•ID 40/SLK-IBS read/write head
•ID 40/SLK-CAN read/write head
The functions described refer to the 4.x versions of the ID 40/SLK software.
Refer to the following documents for more information on the ID 40 system:
Table 1: Required and supplementary documentation
Document Edition Order no.
ID 40 brochure en 3 842 528 602
ID 40/SLK assembly instructions de/en/fr/it/es/pt 3 842 527 942
ID 40/MDT assembly instructions de/en/fr/it/es/pt 3 842 527 943
Programming manual
ID 40 function blocks for Rexroth CL and
PCL controllers
en 3 842 406 191 *)
Programming manual
ID 40 function blocks for Siemens S7
controllers
en 3 842 406 190 *)
Operating instructions for ID 40 configura-
tion and diagnostic program
en 3 842 406 119 *)
*) Manual is part of the software CD-ROM and is not available in print form.
1.2 Layout of this manual
This manual is structured so each chapter builds on the previous chapter. It
is recommended that readers who are unfamiliar with identification systems
read through this entire manual. Readers who have experience with the ID80/E
identification system can skip Chapters 3 and 4.
•Chapter 2 contains an introduction to the ID 40 identification system and describes
how the mobile data tag and read/write head function.
•Chapter 3 shows the critical steps for installing the ID 40 on transfer systems.
•Chapter 4 describes how the mobile data tag stores information.
•Chapter 5 describes how the read/write head stores information.
•Chapter 6 explains how the read/write head works as well as how data is
exchanged via the fieldbuses.
•Chapter 7 describes how data is exchanged via Profibus DP.
•Chapter 8 describes how data is exchanged via Interbus-S.
•Chapter 9 describes how data is exchanged via CANopen.
PROOF COPY 1 | 20.05.2014 | FOR INTERNAL USE ONLY
ENGLISH

10/176 About this manual
Bosch Rexroth AG, MIT: ID 40, 3 842 530 344/2014-05
•Chapter 10 describes the web interface for MDT data diagnostics and start-up
support.
•Chapter 11 explains the steps for starting up the ID 40 on fieldbus systems.
•Chapter 12 shows control procedures using some typical applications. The
corresponding ID 40 code sequences for the Profibus system are also listed.
•Chapter 13 can be used as a reference for running system diagnostics. It also
contains a troubleshooting guide.
•Chapter 14 contains all technical data.
•Chapter 15 contains an overview for ordering available system components.
•The appendix (Chapter 16) contains a glossary of all technical terms and the link
model for the ID 40 system.
1.3 Display
1.3.1 Numbers
•Decimal numbers are written without a suffix,
e.g., 123
•Hexadecimal numbers are written with the prefix “0x",
e.g., 0x0002001C
•Data blocks are written with their address and length in bytes as
<address>/<length>,
e.g., 0x00000815/25
1.3.2 Operating states
•The operating states of the read/write head are written in uppercase and in italics,
e.g., CONNECTED
1.3.3 Information
Symbol Meaning
Information marked with the “Caution” symbol must be strictly observed
for your safety.
Important information is marked with the “Info” symbol. It is intended to
provide support and should be observed.
fIndividual, independent action
1.
2.
3.
Numbered instruction:
The numbers indicate that the actions must be carried out one after the
other.
PROOF COPY 1 | 20.05.2014 | FOR INTERNAL USE ONLY

About this manual 11/176
3 842 530 344/2014-05, MIT: ID 40, Bosch Rexroth AG
1.4 Safety instructions
The MDT mobile data tag and SLK read/write head together form the ID 40
identification system and may only be used for this purpose in an industrial setting in
accordance with Class A of the EMC Act. The manufacturer's declaration documents
the ID 40 identification system's compliance with the requirements of the relevant
standards. Country-specific features and regulations have to be additionally taken
into account, if applicable.
Only specially trained personnel may install and operate the system. The relevant
safety instructions must be observed. In particular, measures must be taken to
prevent danger to personnel and equipment in the case of a defect in the
identification system. This includes maintaining the permissible ambient conditions
and the use of an approved power supply. Details on this can be found in the
Technical data chapter.
The function of the identification system and all connected components must be
checked at regular intervals. If there are any indications that the identification
system is not working properly, it must be taken out of operation and secured
against unauthorized use.
Operating personnel should receive training from supervisors that includes safety
precautions and operating the ID 40 in accordance with this manual.
The manufacturer does not accept any liability or warranty claims for damages
arising from improper use or intervention that is unauthorized or not described in
this manual.
1.5 New in the 4.x versions of the ID 40/SLK software
•TCP/IP connection via RS232 interface for supporting web-based system and MDT
diagnostics, see Chapter 10 “Web interface".
•Access to MDT and SLK data via web browser, also in Chapter 10 “Web interface".
•Access to MDT and SLK data via user application program using the web interface,
see Chapter 10.7 “Web access from application programs".
•The commands for opening and closing transfer are no longer needed, since the
presence of the MDT is now monitored. It is no longer possible to switch the MDT
unnoticed, see Chapter 6.9 “MDT lifeguarding".
Intended use
Safety precautions for
normal operation
Instructions for operators
Liability and warranty
PROOF COPY 1 | 20.05.2014 | FOR INTERNAL USE ONLY
ENGLISH

12/176 Introduction
Bosch Rexroth AG, MIT: ID 40, 3 842 530 344/2014-05
2 Introduction
The ID 40 identification system was designed for automated assembly lines. It
functions as an electronic tag and is used to track product- and order-related data
with the workpiece on a workpiece pallet.
The ID 40 identification system consists of the following primary components:
•MDT mobile data tag
•SLK read/write head
Fig. 1: MDT mobile data tag and SLK read/write head
2.1 ID 40/MDT mobile data tag
The MDT mobile data tag contains re-writable memory where data can be read and
written without contact. It is assigned to an individual workpiece by being mounted
on the workpiece pallet and stores the production data for that workpiece.
By mounting the MDT on the workpiece pallet, the flow of information is
continuously synchronized with the flow of materials, and the workpiece data can be
accessed directly by each process station.
This data includes:
•Workpiece type
•Complete assembly plan
•Production status
•Next processing step
PROOF COPY 1 | 20.05.2014 | FOR INTERNAL USE ONLY

Introduction 13/176
3 842 530 344/2014-05, MIT: ID 40, Bosch Rexroth AG
•Serial number
•Order number
•Workpiece pallet number
•Process station settings
•Test results
•Quality data
The MDT is supplied with inductive power by the read/write head and does not use
any batteries. The MDT is passive outside of the range of a read/write head.
The latest FRAM memory technology is used in the ID 40/MDT, ensuring large
memory capacity at low volume. The FRAM memory stores the data for a virtually
unlimited amount of time without additional buffer batteries. Unlike other memory
technologies, FRAMs can be re-written up to 10 billion times.
2.2 ID 40/SLK read/write head
Unlike the mobile data tag, the ID 40/SLK read/write head is placed in a single
location on the assembly line. With the ID 40/SLK, data is exchanged with the MDT
without contact. It is directly connected as part of a fieldbus system and allows a
user controller to access the workpiece data. The read/write head comes in Profibus
DP, Interbus-S and CANopen versions.
Fig. 2: ID 40 on TS 2plus transfer system
The SLK sends data from the fieldbus master to the MDT or, when given a read
command, from the MDT to the fieldbus.
Parameters can also be set for data transfers, wherein write and read commands
are saved to the SLK to be automatically executed when the next MDT arrives.
Parameters are typically set for the SLK when the system is initialized, but can be set
at any time as long as an MDT is not in the HF field of the SLK, or the HF field is off.
The SLK generates a high-frequency alternating field (HF field) that is needed to
provide the MDT with inductive power. No-contact data transmission with the MDT
also occurs through this HF field, which is generated using a ferrite antenna under
the dark, plastic cover.
PROOF COPY 1 | 20.05.2014 | FOR INTERNAL USE ONLY
ENGLISH

14/176 Introduction
Bosch Rexroth AG, MIT: ID 40, 3 842 530 344/2014-05
The cover of the HF head lights up once data transmission with an MDT has initiated.
The light deactivates once the control system completes the data transmission with
the MDT.
The LED on the MDT lights up once it is in the HF field. The color of the LED
indicates various operating states of the MDT.
Fig. 3:
LED
HF head cover
Data transmission between SLK and MDT
2.2.1 SLK operating states
The SLK has multiple operating states, known as link states. The actual link state can
be changed by a fieldbus command from the user program as well as by the ID 40
system itself.
The actual link state can be determined by the control system at any time using the
fieldbus (for coding, see Chapter 5.3.1 “Actual link state"). An MDT entering the
HF field, for example, is signaled by a change in the actual link state. The SLK also
shows the actual link state on the status display.
The operating states of the SLK are described below. Appendix 16.1 “ID 40 system
link model” contains a detailed overview of the link state.
PROOF COPY 1 | 20.05.2014 | FOR INTERNAL USE ONLY

Introduction 15/176
3 842 530 344/2014-05, MIT: ID 40, Bosch Rexroth AG
2.2.1.1 Disconnected
DISCONNECTED is the base state once the SLK is activated and the self-test has
been completed. The SLK's HF field is not active. No data can be transmitted
between the SLK and an MDT. The SLK status display shows off. The SLK is ready to
communicate with the control system via the fieldbus.
2.2.1.2 Connecting
The SLK only switches from the operating state DISCONNECTED to CONNECTING
when commanded by the control system. The SLK's HF field is activated. The SLK
is ready to receive. The SLK status display shows wai. The next MDT that enters the
field automatically signs on to the SLK and is ready to communicate.
2.2.1.3 Preconnected
This state comes after the CONNECTING state and automatically runs once an MDT
enters the SLK's field, i.e., has signed on to the SLK. The SLK executes data transfers
parameterized beforehand through the fieldbus (prefetch and pretransmit). The
status display shows pre. Once all pre-defined transfers are complete, the link state
PRECONNECTED ends automatically. PRECONNECTED can end very quickly, so the
pre signal on the display is not always visible. If the MDT in the PRECONNECTED
state leaves the HF field early, the SLK switches to the ERROR state.
2.2.1.4 Connected
In the basic configuration, the SLK switches from PRECONNECTED to CONNECTED.
The status display shows con. The control system can now directly access the MDT
data. To do this, read/write commands are sent to the SLK through the fieldbus that
are executed immediately. Data read from the MDT is directly transmitted to the
control system.
The control system ends the CONNECTED state with a command to switch either to
DISCONNECTED or CONNECTING. Only then can the MDT leave the HF field. If the
MDT left the HF field early, the SLK switches to the ERROR state.
The SLK can also be configured so the CONNECTED state does not activate and
automatically switches back to CONNECTING or DISCONNECTED after completing
PRECONNECTED. This can be done by configuring “auto mode” (see Chapter 5.3.3
“Auto mode”).
2.2.1.5 Error
The read/write head switches to the “Error” state when it is unable to communicate
with the MDT after several attempts, e.g., because the MDT has already left the HF
field during a DISCONNECT request. The status display shows a flashing E00. This
can occur, e.g., when the MDT moves past the SLK too quickly, or when too much
data was read or written.
The ERROR state can be ended by switched to the DISCONNECTED or
CONNECTING states.
PROOF COPY 1 | 20.05.2014 | FOR INTERNAL USE ONLY
ENGLISH

16/176 Introduction
Bosch Rexroth AG, MIT: ID 40, 3 842 530 344/2014-05
The SLK does not switch to the ERROR state in the event of communication
interruptions while exchanging data with the MDT. This kind of error information is
sent by the system through the fieldbus.
2.2.1.6 Busy
The read/write head is temporarily processing link state switching requests. The
status display may show bsy.
2.2.1.7 Transitions between link states
The link state switches either by a request from the control system or when an event
defined in the following table occurs.
Operating state switches due to a command (commanded link state) from the
control system (PLC):
Table 2: Relationship between commanded link state and link state
Commanded link state to SLK Only permitted in link state
(display)
Commanded link state results
in link state (display)
CONNECT DISCONNECTED (OFF)
ERROR (E00)
CONNECTING (WAI)
DISCONNECT CONNECTED (CON)
CONNECTING (WAI)
DISCONNECTED (OFF)
RECONNECT CONNECTED (CON) CONNECTING (WAI)
ERROR DISCONNECTED (OFF)
CONNECTING (WAI)
CONNECTED (CON)
ERROR (E00)
After every commanded link state, the system checks whether or not the actual
link state corresponds to the expected state. Only then can the next step in the
process be executed.
PROOF COPY 1 | 20.05.2014 | FOR INTERNAL USE ONLY

Introduction 17/176
3 842 530 344/2014-05, MIT: ID 40, Bosch Rexroth AG
Operating state switches due to an event
Table 3: Relationship between events and link states
Event during communication Event only possible in link
state (display)
Results in link state (display)
MDT signs on to SLK CONNECTING (WAI) PRECONNECTED (PRE)
PRECONNECTED ends and auto
reconnect is active (see
Chapter 5.3.3 “Auto mode")
PRECONNECTED (PRE) CONNECTING (WAI)
PRECONNECTED ends and auto
disconnect is active (see
Chapter 5.3.3 “Auto mode")
PRECONNECTED (PRE) DISCONNECTED (OFF)
PRECONNECTED ends and auto
mode is not active (see
Chapter 5.3.3 “Auto mode")
PRECONNECTED (PRE) CONNECTED (CON)
Error during MDT sign-on CONNECTING (WAI) ERROR (E00)
Error during direct data
exchange with MDT
CONNECTED (CON)
Note:
The error is output through
the bus in the form of an error
message and does not alter
the state
CONNECTED (CON)
Error during MDT sign-off PRECONNECTED (PRE)
CONNECTED (CON)
Note:
Can occur during commanded
link states DISCONNECT,
RECONNECT, ERROR or when
PRECONNECTED ends and
auto mode is active (see
Chapter 5.3.3 “Auto mode")
ERROR (E00)
MDT leaves early CONNECTED (CON)
Note:
Can occur when a workpiece
pallet is released too early in
the application.
ERROR (E00)
Appendix 16.1 “ID 40 system link model” describes the states and state transitions
in detail.
PROOF COPY 1 | 20.05.2014 | FOR INTERNAL USE ONLY
ENGLISH

18/176 Introduction
Bosch Rexroth AG, MIT: ID 40, 3 842 530 344/2014-05
2.2.2 Status display
The 4-character status display of the ID 40/SLK shows the operating states of the
SLK, error messages and the status of the fieldbus interface. After the SLK is turned
on, the currently configured fieldbus address (node no. depending on fieldbus
system) appears on the display for a few seconds.
While running, the display is divided into two areas: Area 1 contains the first three
segments on the left, and area 2 the first segment on the right.
Area 1 Area 2
Fig. 4: ID 40/SLK read/write head status display
Area 1 shows the operating state of the SLK or an error code in the event of an error.
Area 2 shows when the SLK is ready as well as the status of the fieldbus connection
to the user controller.
In the Interbus version, area 2 is divided differently, see Chapter 11.2.4 “Interbus
status display”.
PROOF COPY 1 | 20.05.2014 | FOR INTERNAL USE ONLY

Introduction 19/176
3 842 530 344/2014-05, MIT: ID 40, Bosch Rexroth AG
The following table provides an overview:
Table 4: Overview of ID 40/SLK read/write head displays
Display range Displaying Remark Example
Area 2 System activity The SLK operating system
is active when the bar in
the fourth display seg-
ment rotates.
Area 2 Fieldbus activity The bottom half of the
display segment contains
symbols indicating the
status of the fieldbus.
Their appearance and
meaning depend on the
fieldbus. See Chapters 8
to 10 for more details.
Area 1 Actual link state See Chapter 2.2.1
“SLK operating states”
Area 1 Error state with error
number
See Chapter 12.1
“Troubleshooting guide”
for meaning
Area 1 and
area 2
Fieldbus node number Only shown during boot
up and consists of the
fieldbus code letter and
three-digit node number
Area 1 and
area 2 flashing
Fatal error,
system stopped
See Chapter 12.1.2
“Fatal system errors” for
meaning
PROOF COPY 1 | 20.05.2014 | FOR INTERNAL USE ONLY
ENGLISH

20/176 Introduction
Bosch Rexroth AG, MIT: ID 40, 3 842 530 344/2014-05
2.3 Data transmission between SLK and MDT
The data transmission between the SLK and the MDT is contactless and occurs via
a high-frequency electromagnetic field (HF field). The MDT is also powered by this
electromagnetic field. To begin exchanging data, the mobile data tag is moved into
the field of the read/write head.
Fig. 5:
LED
Display indicating mobile data tag is ready for communication
The LED on the front edge of the housing lights up orange when the MDT enters the
SLK's field. Once a secure data transmission is possible between the MDT and SLK,
the color changes. When the LED shows green, the MDT is operating correctly. When
the LED shows red, an error occurred during the last data exchange
(see Chapter 4.2.3.1 “MDT status register”).
When the data exchange between the SLK and the MDT ends, the LED color changes
to orange, then turns off once the MDT leaves the HF field.
2.3.1 Position of MDT and SLK during data transmission
Proper exchanging of data always depends on the alignment of the MDT and SLK to
one another, and on the read/write distance. MDT alignment consists of frontal and
lateral alignment.
Fig. 6: Alignment of ID 40/MDT for frontal reading and writing
PROOF COPY 1 | 20.05.2014 | FOR INTERNAL USE ONLY