Baumer GXP5W User manual

Baumer IVO GmbH & Co. KG
Dauchinger Strasse 58-62
DE-78056 Villingen-Schwenningen
Phone [phone]
Fax [phone].11 · 174.02.035/4
[email protected] Subject to technical and design modifications.
www.baumer.com Errors and omissions excepted.
Manual
Absolute Encoder with CANopen Lift Protocol
Firmaware version from 1.00

Manual_GXP5_417_Lift_EN.doc 2/41 Baumer IVO GmbH & Co. KG
04.05.11 Villingen-Schwenningen, Germany
Contents
Page
1. Introduction 3
1.1. Scope of delivery 3
1.2. Product assignment 3
2. Safety Precautions and Operating Information 4
3. CAN Bus and CANopen Communication 5
3.1. CAN bus 5
3.1.1. CAN bus properties 5
3.2. CANopen 6
3.3. CANopen in lift construction 6
3.4. CANopen communication 7
3.4.1. Communication profile 7
3.4.2. CANopen message structure 7
3.4.3. Service data communication 8
3.4.4. Process data communication 9
3.4.5. Emergency service 10
3.4.6. Network management services 11
3.4.7. Layer setting services 13
3.5. CANopen Lift encoder according to Appl. Profile DSP417 17
3.5.1. Object overview 17
3.5.2. Detailed object description 20
4. Diagnosis and Important Information 34
4.1. Error diagnosis field bus communication 34
4.2. Troubleshooting with field bus 34
4.3. Important information on sensor 35
5. Applications 36
5.1. Setting and reading objects 36
5.2. Configuration 37
5.3. Operation 38
6. Connection Assignment and Commissioning 40
6.1. Mechanical attachment 40
6.2. Electrical connection 40
6.2.1. Description of connections 40
6.2.2. Connection assignment of M12 plug 40
6.2.3. Connection assignment of D-SUB plug 41
6.3. Display elements (status display) 41

Manual_GXP5_417_Lift_EN.doc 3/41 Baumer IVO GmbH & Co. KG
04.05.11 Villingen-Schwenningen, Germany
Disclaimer of liability
The present manual was compiled with utmost care, errors and omissions reserved. For this reason
Baumer IVO GmbH & Co. KG rejects any liability for the information compiled in the present manual.
Baumer IVO nor the author will accept any liability for direct or indirect damages resulting from the use of the
present information.
At any time we should be pleased receiving your comments and proposals for further improvement of the
present document.
1. Introduction
1.1. Scope of delivery
Please check the delivery upon completeness prior to commissioning.
Depending on encoder configuration and part number delivery is including:
•Encoder
•CD with describing file and manual (also available as download in the Internet)
1.2. Product assignment
Shaft encoder
Product Product Code Device Name Eds File Product Family
GXP5W 0x28 GXP5 GXP5_417.eds Multiturn
X 700 0x28 GXP5 GXP5_417.eds Multiturn
GXP5W with the Product Code 0x28 is an absolute encoder with a CANopen interface and an implemented
application profile DSP417 (Application Profile for Lift Control Systems).
LIFT

Manual_GXP5_417_Lift_EN.doc 4/41 Baumer IVO GmbH & Co. KG
04.05.11 Villingen-Schwenningen, Germany
2. Safety Precautions and Operating Information
Additional information
•The manual is a supplement to the documentation which already exists (catalogs, product information
and assembly manuals).
•It is imperative that the manual is read before commissioning.
Proper use
•The encoder is a precision measuring device. It is used exclusively for the detection of angle positions
and rotations, and the processing and provision of the measured values as electrical output signals for
the next device. The encoder may only be used for this purpose.
Commissioning
•The encoder may only be installed and assembled by a qualified electrician.
•Observe the operating manual of the machine manufacturer.
Safety precautions
•Check all electrical connections before commissioning the system.
•If assembly, electrical connection or other work on the encoder and on the system are not carried out
properly, malfunction or failure of the encoder may result.
•The endangering of persons, damage to the system and damage to operating equipment due to the
failure or malfunction of the encoder must be prevented with suitable safety measures.
•The encoder may not be operated outside the specified limits (see additional documentation).
Failure to observe the safety precautions can lead to malfunctions, damage and injuries!
Transport and storage
•The encoder may only be transported and stored in the original packaging.
•Do not drop the encoder or subject it to major jolts or impacts.
Assembly
•Avoid impacts or shocks to the housing and shaft.
•Do not torque the housing.
•Do not produce a rigid connection between the encoder and drive shafts.
•Do not open the encoder or modify it mechanically.
The shaft, ball bearings, glass plate or electronic parts can be damaged. Safe operation is then no longer
ensured.
Electrical commissioning
•Do not modify the encoder electrically.
•Do not carry out wiring work while the encoder or system is energized.
•The electrical connection may not be connected or disconnected while energized.
•Install the entire system so that it is EMC-compliant. The installation environment and wiring affect the
EMC of the encoder. Install the encoder and the supply lines in separate locations or at a great distance
from wiring with a high interference level (frequency converters, contactors etc.).
•For consumers with high interference levels, provide a separate power supply for the encoder.
•Complete screen the encoder housing and the connection cables.
•Connect the encoder to protective ground and use shielded cables. The cable shield must be connected
to the screw cable terminal or plug. Connection of the protective ground at both ends, the housing via the
mechanical attachment, and the cable shield via devices connected downstream should be aimed for. If
problems occur with ground loops, grounding should be carried out on at least one end.
Failure to observe the above can lead to malfunctions, damage and injuries!

Manual_GXP5_417_Lift_EN.doc 5/41 Baumer IVO GmbH & Co. KG
04.05.11 Villingen-Schwenningen, Germany
3. CAN Bus and CANopen Communication
3.1. CAN bus
The CAN bus (CAN: Controller Area Network) was originally developed by Bosch and Intel for fast,
inexpensive data transmission in motor vehicle technology. Today the CAN bus is also used in industrial
automation.
The CAN bus is a field bus (the standards are defined by the association CAN in Automation (CiA)) via which
devices, actuators and sensors of different manufacturers can communicate with each other.
3.1.1. CAN bus properties
• Data rate of 1 Mbaud with a network range of up to 40 m (130 ft)
• Network connected at both ends
• Bus medium twisted-pair cables
• Real-time capability: defined maximum wait time for high-priority messages.
• Theoretically 127 nodes to a bus, however physically only 32 (due to the driver used).
• Securing of network-wide data consistency. Faulty messages are made known to all network nodes as
faulty.
• Message-oriented communication
The message is marked with an identifier. All network nodes check whether the message is relevant for
them using the identifier.
• Broadcasting, multicasting
All network nodes receive every message simultaneously, enabling synchronization.
• Multi-master capability
Every node in the field bus can send and receive data independently without being dependent on a priority
of the master. Each can begin its message if the bus is not busy. In the case of simultaneous transmission
of messages, the node with the highest priority prevails.
• Assignment of priorities to messages
The identifier specifies the priority of the message. As a result, important messages can be transmitted
quickly via the bus.
• Residual error probability
Safe-guarding methods in the network reduce the probability of an undetected, faulty data transmission to
below 10 -11. A virtually 100 % reliable transmission can be assumed.
• Operation monitoring
Localization of defective or failed stations. The CAN protocol contains an operation monitoring function of
network nodes. The operation of defective network nodes is restricted, or they are completely decoupled
from the network.
• Data transmission with a short error recovery time
Due to several error detection mechanisms, falsified messages are recognized with a high probability. If an
error is detected, then the message is automatically retransmitted.
Several network nodes are interconnected via a bus cable. Each network node can send and receive
messages. The data are transmitted serially between the network nodes.
Examples of network nodes for CAN bus devices are:
• Automation devices, e.g. PLC
• PCs
• Input/output modules
• Drive controllers
• Analysis devices, e.g. a CAN monitor
• Operating and input devices as human-machine interface (HMI)
• Sensors and actuators

Manual_GXP5_417_Lift_EN.doc 6/41 Baumer IVO GmbH & Co. KG
04.05.11 Villingen-Schwenningen, Germany
3.2. CANopen
Under the technical direction of the Steinbeis Transfer Center for Automation, the CANopen profile was
developed on the basis of the Layer 7 specification CAL (CAN Application Layer). Compared to CAL,
CANopen only contains the functions suitable for this application. CANopen therefore represents a subset of
CAL optimized for the application and enables simplified system design and the use of simplified devices.
CANopen is optimized for rapid data exchange in real-time systems.
The CAN in Automation (CiA) organization is responsible for the applicable standards of the corresponding
profiles.
CANopen enables:
• Simple access to all device and communication parameters
• Synchronization of several devices
• Automatic network configuration
• Cyclical and event-controlled process data traffic
CANopen consists of four communication objects (COB) with different properties:
• Process data objects for real-time data (PDO)
• Service data objects for parameter and program transmission (SDO)
• Network management (NMT, Heartbeat)
• Predefined objects (for synchronization, emergency message)
All device and communication parameters are structured in an object directory. An object comprises the
name of the object, data type, number of sub-indices, structure of the parameters and the address.
According to the CiA, this object directory is divided into three different parts: communication profile, device
profile and a manufacturer-specific profile (see Object directory).
3.3. CANopen in lift construction
CANopen is a standardized application for distributed, industrial automation systems based on CAN and on
the communication standard CAL. CANopen is a standard of the CAN in Automation (CiA) and already found
extremely broad acceptance shortly after it became available. In Europe CANopen can be considered the
decisive standard for the realization of industrial CAN-based system solutions.
The responsibility was turned over to the organization CAN-in-Automation, which coordinates all work on the
CANopen system worldwide. Within the CiA a special interest group (SIG) "Lift" was founded. The task of this
SIG is the checking of the existing profiles for their suitability for lift construction and their expansion or
redefinition. Within the SIG "Lift" various working groups for the individual profiles were specified.

Manual_GXP5_417_Lift_EN.doc 7/41 Baumer IVO GmbH & Co. KG
04.05.11 Villingen-Schwenningen, Germany
3.4. CANopen communication
3.4.1. Communication profile
The communication between the network nodes and the master (PC/controller) is carried out via object
directories and objects. The objects are addressed via a 16-bit index. The CANopen communication profile
DS 301 standardizes the various communication objects. Accordingly, they are divided into several groups:
• Process data objects (PDO) for the real-time transmission of process data
• Service data objects (SDO) for the write and read access to the object directory
• Objects for the synchronization and error display of CAN nodes:
SYNC object (synchronization object) for the synchronization of network nodes
EMCY object (emergency object) for the error display of a device or its periphery
• Network management (NMT) for the initialization and network control
• Layer setting services (LSS) for the configuration by means of a serial number, revision number etc. within
an
existing network
3.4.2. CANopen message structure
The first part of a message is the COB-ID (identifier).
Structure of the 11-bit COB-ID:
Function Code Node-ID
4-bit Function Code 7-bit Node-ID
The function code provides information on the type of message and the priority
The lower the COB-ID, the higher the priority of the message.
Broadcast messages:
Function Code COB-ID
NMT 0
SYNC 80h
Peer to peer messages:
Function Code COB-ID
Emergency 80h + Node-ID
PDO1 (tx)1) 17Bh+ Lift number * 10 + PosUnit
SDO (tx)1) 580h + Node-ID
SDO (rx)1) 600h + Node-ID
Heartbeat 700h + Node-ID
LSS (tx) 1) 7E4h
LSS (rx) 1) 7E5h 1): (tx) and (rx) from the
standpoint of the encoder
The node ID can be freely selected via the CANopen bus between 1 and 127 (if rotary switch = 0). The
encoders are shipped with a node ID = 1.
A change is made with the service data object 2101h or via LSS.
A CAN telegram consists of the COB-ID and up to 8 bytes of data:
COB-ID DLC Byte 1 Byte 2 Byte 3 Byte 4 Byte 5 Byte 6 Byte 7 Byte 8
Xxx x xx xx xx xx xx xx xx xx
The exact telegrams will be listed in detail later.

Manual_GXP5_417_Lift_EN.doc 8/41 Baumer IVO GmbH & Co. KG
04.05.11 Villingen-Schwenningen, Germany
3.4.3. Service data communication
The service data objects comply with the CiA standards. An object can be accessed via an index and
subindex. The data can be requested or, if necessary, written to the object.
General information on the SDOs
Structure of an SDO telegram:
COB-ID DLC Command Object L Object H Subinde
x
Data 0 Data 1 Data 2 Data 3
An SDO COB-ID consists of the following:
Master -> Encoder : 600h + Node-ID
Encoder -> Master : 580h + Node-ID
DLC (data length code) designates the length of the telegram. This consists of the following:
1 byte command + 2 bytes object + 1 byte subindex + number of data bytes (0 - 4).
The command byte specifies whether data are read or set and how many data bytes are concerned:
SDO Command Description Data Length
22h Download Request Max. 4 bytes Send parameters to encoder
23h Download Request 4 bytes
2Bh Download Request 2 bytes
2Fh Download Request 1 byte
60h Download Response - Confirmation of adoption to Master
40h Upload Request - Request parameters from encoder
42h Upload Response Max. 4 bytes Parameters to Master with max. 4 bytes
43h Upload Response 4 bytes
4Bh Upload Response 2 bytes
4Fh Upload Response 1 byte
80h Abort Message - Encoder signals error code to Master
An abort message indicates an error in the CAN communication. The SDO command byte is 80h. The
object and the subindex are those of the desired object. The error code is present in byte 5 - 8.
ID DLC Byte 1 Byte 2 Byte 3 Byte 4 Byte 5 Byte 6 Byte 7 Byte 8
580h + Node-
ID
8 80h Object L Object H Subinde
x
ErrByte 0 ErrByte 1 ErrByte 2 ErrByte 3
Byte 8 - 5 results in the SDO abort message (Byte 8 = MSB).
The following messages are supported:
05040001h : Command byte is not supported
06010000h : Incorrect access to an object
06010001h : Read access to Write Only
06010002h : Write access to Read Only
06020000h : Object is not supported
06090011h : Subindex is not supported
06090030h : Value outside limits
06090031h : Value too large
08000000h : General error
08000020h : Incorrect memory signature ("save")
08000021h : Data cannot be saved

Manual_GXP5_417_Lift_EN.doc 9/41 Baumer IVO GmbH & Co. KG
04.05.11 Villingen-Schwenningen, Germany
Example SDOs
Request for a value from the Master by the Slave
A frequent request is for the position. ÆObject 6383h Subindex 1
COB-ID DLC Command Object L Object H Subinde
x
Data 0 Data
1
Data
2
Data
3
600h+Node-ID 8 40h 83h 63h 01 x x x x
Response of the Slave to the request for a value
The position is 4 bytes long, and the exact values are specified under Object 6383h Subindex 1.
COB-ID DLC Command Object L Object H Subinde
x
Data 0 Data
1
Data
2
Data
3
580h+Node-ID 8 43h 83h 63h 01 a b c d
Writing of a value from the Master to the Slave
A position can be set with Preset. ÆObject 6382h
COB-ID DLC Command Object L Object H Subinde
x
Data 0 Data
1
Data
2
Data
3
600h+Node-ID 8 22h 82h 63h 01 a b c d
Response of the Slave to the writing of a value
COB-ID DLC Command Object L Object H Subinde
x
Data 0 Data
1
Data
2
Data
3
580h+Node-ID 8 60h 82h 63h 01 0 0 0 0
3.4.4. Process data communication
Process data objects are used for real-time data exchange for process data, e.g. the position or the operating
status. PDOs can be transmitted synchronously or cyclically (asynchronously). The encoder supports PDO1
.. This supplies the current encoder position and its speed, and is defined in Objects 1906h and 1B06hh.
Synchronous
To transmit the process data synchronously, a value between 1 and F0h (=240) must be entered in the object
1906h Subindex 2. If the value is now 3, the PDO is transmitted to every third Sync telegram (with a value of
1 it is transmitted to every Sync telegram) until 0 is entered in the object 2800h 0. If, for example, a 5 is
entered there, the PDO is still written to every third Sync telegram, however a total of only 5 times. In
accordance with this, the 15th Sync telegram is followed by the last PDO. The counter for the number of
PDOs to be transmitted is reset via a position change or the NMT reset. This means the position is
transmitted 5 times unless it changes. If the position changes, it is transmitted again 5 times.
In the synchronous mode, the PDOs are requested by the Master via the Sync telegram:
Byte 0 Byte 1
COB-ID = 80 0
Cyclical (asynchronous)
If the PDOs are to be transmitted cyclically, the value FFh must be written to Object 1906h Subindex 2. In
addition, the cycle time in milliseconds must be entered in the same object, Subindex 5. The entered time is
rounded off to 1ms. If the value 0 ms is saved, the PDOs are not transmitted and the function is deactivated.
Another option is provided by Object 2800h. If the value is 0, the cyclical transmission runs as described
above. If the value is 1, it is cyclically checked whether a change has been made in the value. If not, no
transmission takes place. If the value is 4, the PDO is transmitted 4 times per cycle if a change exists.

Manual_GXP5_417_Lift_EN.doc 10/41 Baumer IVO GmbH & Co. KG
04.05.11 Villingen-Schwenningen, Germany
Overview
The following table provides a summary of the various transmission types of PDOs:
1906h
Sub2 Sub5 2800h Brief Description
FFh 3ms 0 Cyclical transmission every 3 ms
FFh 5ms 2 The PDO is sent double every 5 ms if a change is present.
FFh 0ms 0 PDO transmission is deactivated
FFh 0ms 2 PDO transmission is deactivated
3 xxx 0 Transmit for every third Sync telegram
3 xxx 2Bh Every third Sync telegram, but only 43 times total (=2Bh).
PDO
PDO1 telegram structure:
ID DLC Byte 1 Byte 2 Byte 3 Byte 4 Byte 5 Byte 6
18Ch 4 Xx Xx Xx Xx Xx Xx
ID : 17Bh+ Lift number * 10 + PosUnit
Length : 6 data bytes
Byte1 - 4 : Current position in increments
Byte 5 - 6 : Speed
3.4.5. Emergency service
Internal device error or bus problems trigger an emergency message:
COB-ID DLC Byte0 Byte 1 Byte 2 Byte 3 Byte 4 Byte 5 Byte 6 Byte 7
Error Code80h+Node-ID 8
00h 01h
Error Register
1001h
Alarms 63C7h Warning 63C5h n.u.
Byte 0..1: Error Codes
Error Code (hex) Meaning
0000 Error Reset or No Error
1000 Generic Error
Byte 2: Error Register
Bit Meaning
0 Generic Error
Byte 3..4 Alarms
Bit Meaning Value = 0 Value = 1
0 Position error active No Yes
Byte 5..6 Warning
Bit Meaning Value = 0 Value = 1
2 CPU watchdog status OK Reset carried out
4 Battery charge OK Charge too low
Byte 7: Not in use

Manual_GXP5_417_Lift_EN.doc 11/41 Baumer IVO GmbH & Co. KG
04.05.11 Villingen-Schwenningen, Germany
3.4.6. Network management services
The network management can be divided into two groups:
With the NMT services for device control, the bus nodes can be initialized, started and stopped.
In addition, there are also NMT services for connection monitoring.
Description of NMT commands
The commands are transferred as unconfirmed objects and are structured as follows:
Byte 0 Byte 1 Byte 2
COB-ID = 0 Command Byte Node Number
COB-ID for NMT commands is always zero. The Node-ID is transmitted in Byte 2 of the NMT command.
Command Byte
Command Byte Description In State Event Drawing
01h Start Remote Node 1
02h Stop Remote Node 2
80h Enter Pre-Operational Mode 3
81h, 82h Reset Remote Node 4, 5
The node number corresponds to the Node-ID of the desired node. With none number = 0 all nodes are
addressed.
NMT State Event
Following initialization the encoder is in the Pre-Operational mode. In this state SDO parameters can be read
and written. To request PDO parameters, the encoder must first be run in the Operational Mode state.
Power on or Hardware Reset
Init
Pre-Operational
Operational
Stopped/Prepared
1 3
2
1
3
2
4/5
BootUp Message
4/5
4/5

Manual_GXP5_417_Lift_EN.doc 12/41 Baumer IVO GmbH & Co. KG
04.05.11 Villingen-Schwenningen, Germany
Different NMT states
Init
Following initialization the encoder sends a BootUp message on the CAN bus. Then the encoder
automatically switches into PreOperational mode.
The COB-ID of the BootUp message consists of 700h an the Node-ID.
COB-ID Byte 0
700h + Node-
ID
00
Pre-Operational Mode
In the Pre-Operational mode, SDOs can be read and written.
Operational Mode
In the Operational mode the encoder sends the desired PDOs. In addition, SDOs can be read and written.
Stopped or Prepared Mode
In the Stopped mode only NMT communication is possible. No SDO parameters can be read or written. LSS
is only possible in the Stopped mode.
State change
Start Remote Node (1)
With the Start command, the encoder is switched into the Operational mode.
COB-ID Command Byte Node Number
0 1h 0 - 127
Stop Remote Node (2)
With the Stop command the encoder is switched into the Stopped or Prepared mode.
COB-ID Command Byte Node Number
0 2h 0 - 127
Enter Pre-Operational Mode (3)
Switches into the Pre-Operational mode.
COB-ID Command Byte Node Number
0 80h 0 - 127
Reset Remote Node (4) or Reset Communication (5)
With the Reset command the encoder is reinitialized.
Reset Remote Node (4):
COB-ID Command Byte Node Number
0 81h 0 - 127
Reset Communication (5):
COB-ID Command Byte Node Number
0 82h 0 - 127

Manual_GXP5_417_Lift_EN.doc 13/41 Baumer IVO GmbH & Co. KG
04.05.11 Villingen-Schwenningen, Germany
Heartbeat
A "Heartbeat" principle is defined in the CAL with which the communication capability of CANopen devices
can be monitored. It can be ensured that the Master could react to a failure.
In Object 1017h "Producer Heartbeat Time" the time of the heartbeat can be defined. As soon as the value
has been confirmed, the heartbeat begins to transmit.
COB-ID Data/Remote Byte 0
701h d 7Fh (127d)
The heartbeat messages consist of the COB-ID and a byte. This byte is used to transmit the NMT state.
0: BootUp-Event
4: Stopped
5: Operational
127: Pre-Operational
That means the encoder is in the Pre-Operational mode (7Fh = 127).
3.4.7. Layer setting services
In the spring of 2000 a new protocol was drafted by CiA to ensure a uniform occurrence. The procedure is
described under Layer Setting Services and Protocol, CiA Draft Standard Proposal 305 (LSS).
In the standard configuration we ship the encoder with the Node-ID 1 and the baud rate 50 kBaud.
Several encoders with the same Node-ID can be connected to the bus system. To now be able to address
the individual encoders, LSS is used.
Each encoder has a unique serial number and is addressed via this number. This means any desired number
of encoders with the same Node-ID can be connected to a bus system and then initialized with LSS. Both the
Node-ID and the baud rate can be reset. LSS can only be carried out in the Stopped Mode.
Message structure
COB-ID:
Master ÆSlave : 2021 = 7E5h
Master ÅSlave : 2020 = 7E4h
After the COB-ID an LSS command specifier is transmitted.
Then up to seven data bytes are added on.
COB-ID cs Byte 1 Byte 2 Byte 3 Byte 4 Byte 5 Byte 6 Byte 7
Switch Mode Global
7E5h Æ04h Mode Reserved
Mode : 0 ÆOperation mode
1 ÆConfiguration mode
Switch Mode Selective
With the following procedure a very specific encoder can be addressed in the bus system.
7E5h Æ40h VendorID Reserved
7E5h Æ41h ProductCode Reserved
7E5h Æ42h RevisionNumber Reserved
7E5h Æ43h SerialNumber Reserved
7E4h Å44h Mode Reserved

Manual_GXP5_417_Lift_EN.doc 14/41 Baumer IVO GmbH & Co. KG
04.05.11 Villingen-Schwenningen, Germany
VendorID : ECh
ProductCode : Internal product code for the respective encoder
RevisionNumber : Current revision number of the encoder
SerialNumber : Unique, consecutive serial number
Mode : Response of the encoder is the new mode (0 = Operation mode; 1 = Configuration
mode)
Set Node-ID
7E5h Æ11h Node-ID Reserved
7E4h Å11h ErrCode Spec Error Reserved
Node-ID : The new Node-ID of the encoder
ErrorCode : 0=OK; 1=Node-ID outside range; 2..254 = reserved; 255ÆspecificError
SpecificError : If ErrorCode = 255 Æapplication-specific error code.
Set BitTiming
7E5h Æ13h tableSel tableIn
d
Reserved
7E4h Å13h ErrCod
e
SpecErro
r
Reserved
TableSel : Selects the BitTiming table 0 : Standard CiA bit timing table
1 - 127 : Reserved for CiA
128 - 255: Manufacturer-specific tables
TableInd : BitTiming entry in selected table (see table below).
ErrorCode : 0=OK; 1=BitTiming outside range; 2 - 254 = reserved; 255ÆSpecificError
SpecificError : Falls ErrorCode=255 ÆApplication-specific error code.
Standard CiA table
Baud Rate Table Index
1000 kBaud 0
800 kBaud 1
500 kBaud 2
250 kBaud 3
125 kBaud 4
100 kBaud 5
50 kBaud 6
20 kBaud 7
10 kBaud 8
Saving configuration protocol
This protocol saves the configuration parameters in the EEPROM.
7E5h Æ17h Reserved
7E4h Å17h ErrCod
e
SpecErro
r
Reserved
ErrorCode : 0=OK;1 = Saving not supported; 2 = access error; 3 - 254 =
Reserved;255ÆspecificError
SpecificError : If ErrorCode = 255 ÆApplication-specific error code.

Manual_GXP5_417_Lift_EN.doc 15/41 Baumer IVO GmbH & Co. KG
04.05.11 Villingen-Schwenningen, Germany
Activate BitTiming Parameters
The new BitTiming parameters are activated with the command specifier 21.
7E5h Æ15h Switch Delay Reserved
Switch Delay : Delay of the reset in the Slave in ms.
After the delay time, the encoder signals the new baud rate.
Request VendorID
Request the VendorID of a selected encoder
7E5h Æ5Ah Reserved
7E4h Å5Ah 32-Bit Vendor ID Reserved
VendorID : = ECh
Request ProductCode
Request the ProductCode of a selected encoder
7E5h Æ5Bh Reserved
7E4h Å5Bh ProductCode Reserved
ProductCode : Manufacturer-dependent product code
Request Revision Number
Request the RevisionNumber of a selected encoder
7E5h Æ5Ch Reserved
7E4h Å5Ch 32-Bit Revision Number Reserved
RevisionNumber : Current revision
Request SerialNumber
Request the SerialNumber of a selectable encoder
7E5h Æ5Dh Reserved
7E4h Å5Dh 32-Bit Serial Number Reserved
SerialNumber : Unique consecutive serial number of the encoder

Manual_GXP5_417_Lift_EN.doc 16/41 Baumer IVO GmbH & Co. KG
04.05.11 Villingen-Schwenningen, Germany
Range Request
Encoders can also be searched for in a certain range. For this purpose, the following objects are sent
consecutively:
7E5h Æ46h VendorID Reserved
7E5h Æ47h ProductCode Reserved
7E5h Æ48h RevisionNumber LOW Reserved
7E5h Æ49h RevisionNumber HIGH Reserved
7E5h Æ4Ah SerialNumber LOW Reserved
7E5h Æ4Bh SerialNumber HIGH reserved
Each encoder with the corresponding parameters responds by transmitting the following message:
7E4h Å4Fh Reserved

Manual_GXP5_417_Lift_EN.doc 17/41 Baumer IVO GmbH & Co. KG
04.05.11 Villingen-Schwenningen, Germany
3.5. CANopen Lift encoder according to Appl. Profile DSP417
3.5.1. Object overview
According to CiA (CAN in Automation), the objects are divided into three groups:
•Standard objects:
1000h, 1001h, 1018h
•Manufacturer-specific objects:
2000h - 5FFFh
•Application-specific objects:
6000h - 67FFh
The following table shows a summary of all SDO objects supported by the device.
Object Object number in hex
Name Description of object
Type U/I = Unsigned/Integer , No. = Number of bits, ARR = Array
Attr ro = ReadOnly, wo = WriteOnly, rw = ReadWrite
Default Default value for first initialization
EE 1= If saving to EEPROM is carried out
Info Additional information
Object Name Type Attr Default EE Info
1000h Device Type U32 ro 060001A1h
20..215 Profile No. = 1A1h=417 encoder lift
216..223 Communication model
224..231 virtual device code
1001h Error Register U8 ro 00h Bit0=Generic Error
1003h Predefined Error Field ARR Contains last 8 errors or warnings
00h Largest Subindex U8 rw 00h Number of messages saved (0 - 8)
01h Last Entry U32 ro Error or warning
.. .. .. .. .. ..
08h Oldest Entry U32 ro Error or warning
1005h Sync COB-ID U32 rw 80h 1 COB-ID of Sync object
1008h Device Name U32 ro "GXP5" 1 "GXP5"
1009h Hardware Version U32 ro "1.00“ Hardware version in ASCII V 1.00
100Ah Software Version U32 ro "1.00“ Software version in ASCII V 1.00
1010h Store Parameters ARR
00h Largest Subindex U8 ro 04h Number of memory possibilities = 4
01h Save All Parameters U32 rw =“save“ (0x73617665) to save
02h Communication Parameters U32 rw =“save“ (0x73617665) to save
03h Application Parameters U32 rw =“save“ (0x73617665) to save
04h Manufacturer Specific
Parameters
U32 rw =“save“ (0x73617665) to save
1011h Restore Default Parameters ARR
00h Largest Subindex U8 ro 04h Number of reset possibilities = 4
01h All Parameters U32 rw =“load“ (0x6C6F6164) to load
02h Communication Parameters U32 rw =“load“ (0x6C6F6164) to load
03h Application Parameters U32 rw =“load“ (0x6C6F6164) to load
04h Manufacturer Specific
Parameters
U32 rw =“load“ (0x6C6F6164) to load
1014h Emergency COB-ID U32 rw 80h + Node-
ID
1 COB-ID of Emergency object
1017h Producer Heartbeat Time U16 rw 00h 1
1018h Identity Object U32 ro
00h Largest Subindex U8 ro 04h
01h VendorID U32 ro ECh 1 Vendor number assigned by CiA
02h Product Code U32 ro 1Eh 1
03h Revision Number U32 ro 00010000h Current revision number V1.00
04h Serial Number U32 ro xyz 1 Unique consecutive serial number

Manual_GXP5_417_Lift_EN.doc 18/41 Baumer IVO GmbH & Co. KG
04.05.11 Villingen-Schwenningen, Germany
1906h Transmit PDO1 Parameter REC
00h Largest Subindex U8 ro 05h
01h COB-ID U32 rw 18Ch 1 PDO ID = 17Bh + Lift No10 + PosUnit
02h PDO Type U8 rw FFh 1 FFh= cyclical
05h Event Timer U16 rw 00h 1 Cycle time in ms
1B06h Transmit PDO1 Mapping ARR Static mapping only!!
00h Largest Subindex U8 ro 02h
01h Content of PDO1 U32 ro 63830120h Position valve 32-bit
02h Content of PDO1 S16 ro 63900110h Speed 16-bit
2100h Baud Rate U8 rw 02h 1 After baud rate is set, EEPROM must be saved and
reinitialized
0=10 kBit/s
1=20 kBit/s
2=50 kBit/s
3=100 kBit/s
4=125 kBit/s
5=250 kBit/s
6=500 kBit/s
7=800 kBit/s
8=1000 kBit/s
2101h Node-ID U8 rw 01h 1 Node number 1 - 127 possible. After baud rate is set,
EEPROM must be saved and reinitialized.
2110h Customer-Specific Node-ID
Version
U32 ro 01h 1 Define treatment of Node-ID
2201h Statistics REC
00h Largest Subindex U8 ro 03h Number of subindexes
01h Number of Position Errors U32 ro 00h 1 Position check
02h Time in Seconds U32 ro 00h 1 Time since last reset
03h Number of Timer Reset
Watchdog
U32 ro 00h 1 Timer Watchdog
2300h Customer EEPROM Area ARR Any desired data can be saved
00h Largest Subindex U8 ro 08h in this object
01h Data0 U16 rw 00h 1
02h Data1 U16 rw 00h 1
03h Data2 U16 rw 00h 1
04h Data3 U16 rw 00h 1
05h Data4 U16 rw 00h 1
06h Data5 U16 rw 00h 1
07h Data6 U16 rw 00h 1
08h Data7 U16 rw 00h 1
2800h PDO1 Addition/Event Trigger U8 rw 00h 1 Repetition counter for PDO1
6001h Lift Number U8 rw 01h 1 Lift number 1 - 8 (currently only 1 possible)
6380h Operating Parameters ARR
00h Largest Subindex U8 ro 04h
01h Position Unit 1 U16 rw 04h 1
02h Position Unit 2 U16 rw 04h 1
03h Position Unit 3 U16 rw 04h 1
04h Position Unit 4 U16 rw 04h 1
Bit0 = Rotating direction 0 = CW, 1 = CCW
Bit2 = Scaling Function 0 = off, 1 = on
CW = Increasing position value during clockwise
rotation (when viewing flange)
CCW = Increasing position value during counter-
clockwise rotation (when viewing flange)
6381h Resolution ARR
00h Largest Subindex U8 ro 04h
01h Position Unit 1 U32 rw 1
02h Position Unit 2 U32 rw 1
03h Position Unit 3 U32 rw 1
04h Position Unit 4 U32 rw
8192
2000h
13Bit
1
Resolution in steps/rotation
or
mm/rotation
6382h Preset Value in Steps ARR
00h Largest Subindex U8 ro 04h
01h Position Unit 1 U32 rw 00h 1
02h Position Unit 2 U32 rw 00h 1
03h Position Unit 3 U32 rw 00h 1
04h Position Unit 4 U32 rw 00h 1
Preset in steps ÆOffset
6383h Position in Steps ARR ro
00h Largest Subindex U8 ro 04h
01h Position Unit 1 U32 ro
02h Position Unit 2 U32 ro
03h Position Unit 3 U32 ro
04h Position Unit 4 U32 ro
Position value incl. offset in steps

Manual_GXP5_417_Lift_EN.doc 19/41 Baumer IVO GmbH & Co. KG
04.05.11 Villingen-Schwenningen, Germany
6384h Encoder Meas. Step Setting ARR ro Position of Unit 1
00h Largest Subindex U8 ro 03h
01h Measuring Step U16 rw 64h 1 Unit of measuring step, multiple of 10 µm
02h Speed Measuring Step U16 rw 0Ah 1 Unit of speed, multiple of 0.1 mm/s
03h Acceleration Measuring Step U16 rw 0Ah 1 Unit of acceleration, multiple of 1 mm/s²
6390h Speed Value Car ARR
00h Largest Subindex U8 ro 04h
01h Position Unit 1 S16 ro
02h Position Unit 2 S16 ro
03h Position Unit 3 S16 ro
04h Position Unit 4 S16 ro
Speed
(see Object 6384 for unit)
63C0h Operating Status ARR
00h Largest Subindex U8 ro 04h
01h Position Unit 1 U16 ro 04h
02h Position Unit 2 U16 ro 04h
03h Position Unit 3 U16 ro 04h
04h Position Unit 4 U16 ro 04h
Bit0 = Rotating direction 0 = CW, 1 = CCW
Bit2 = Scaling Function 0 = off, 1 = on
CW = Increasing position value during clockwise
rotation (when viewing flange)
CCW = Increasing position value during counter-
clockwise rotation (when viewing flange)
63C1h Max. Resolution ARR
00h Largest Subindex U8 ro 04h
01h Position Unit 1 U32 ro 2000h
02h Position Unit 2 U32 ro 2000h
03h Position Unit 3 U32 ro 2000h
04h Position Unit 4 U32 ro 2000h
Maximum resolution in steps/rotation
63C2h Max. Rotations ARR
00h Largest Subindex U8 ro 04h
01h Position Unit 1 U16 ro 10000h
02h Position Unit 2 U16 ro 10000h
03h Position Unit 3 U16 ro 10000h
04h Position Unit 4 U16 ro 10000h
Max. number of rotations
63C4h Supported Warnings ARR
00h Largest Subindex U8 ro 04h
01h Position Unit 1 U16 ro 14h
02h Position Unit 2 U16 ro 14h
03h Position Unit 3 U16 ro 14h
04h Position Unit 4 U16 ro 14h
Following warnings are supported:
Bit2 = CPU watchdog status
Bit4 = Battery charge
63C5h Warnings ARR
00h Largest Subindex U8 ro 04h
01h Position Unit 1 U16 ro 00h
02h Position Unit 2 U16 ro 00h
03h Position Unit 3 U16 ro 00h
04h Position Unit 4 U16 ro 00h
Following warnings are evaluated:
Bit2 = CPU watchdog status
Bit4 = Battery charge
63C6h Supported Alarms ARR
00h Largest Subindex U8 ro 04h
01h Position Unit 1 U16 ro 01h
02h Position Unit 2 U16 ro 01h
03h Position Unit 3 U16 ro 01h
04h Position Unit 4 U16 ro 01h
Following alarms are supported:
Bit0=Position error
63C7h Alarms ARR
00h Largest Subindex U8 ro 04h
01h Position Unit 1 U16 ro 00h
02h Position Unit 2 U16 ro 00h
03h Position Unit 3 U16 ro 00h
04h Position Unit 4 U16 ro 00h
Following alarms are evaluated:
Bit0=Position error
63C8h Operating Time ARR
00h Largest Subindex U8 ro 4h
01h Position Unit 1 U32 ro 0h
02h Position Unit 2 U32 ro 0h
03h Position Unit 3 U32 ro 0h
04h Position Unit 4 U32 ro 0h
Time in 1/10 hours since last Reset
63C9h Offset Value ARR
00h Largest Subindex U8 ro 4h
01h Position Unit 1 U32 ro 0h
02h Position Unit 2 U32 ro 0h
03h Position Unit 3 U32 ro 0h
04h Position Unit 4 U32 ro 0h
Offset calculated from Preset Æ6382 h

Manual_GXP5_417_Lift_EN.doc 20/41 Baumer IVO GmbH & Co. KG
04.05.11 Villingen-Schwenningen, Germany
3.5.2. Detailed object description
Object 1000 Device Type
Subindex 0
Data Type Unsigned 32
Access ReadOnly
Default 060001A1h
EEPROM No
Description Information on device profile and device model
Values
20..215 Profile No.= 1A1h=417 (Application Profile for Lift Control
Systems).
216..223 Communication model
224..231 Virtual device code
Object 1001 Error Register
Subindex 0
Data Type Unsigned 8
Access ReadOnly
Default 0h
EEPROM No
Description Current Error Code
Values Bit 0 1 = Generic Error
Object 1003 Predefined Error Field
Here CiA (CAN in Automation) defines approximately 200 different Error Codes.
This document only describes the Error Codes relevant for the sensor.
This object saves the last 8 errors or warnings which have occurred.
Subindex 0
Data Type Unsigned 8
Access ReadWrite
Default 0
EEPROM No
Description Read: Number of errors or warnings
Write 0: Reset errors
Values 0 - 8
Subindex 1..8
Data Type Unsigned 32
Access ReadOnly
Default 0
EEPROM No
Description Errors or warnings which have occurred, whereby Subindex 1 is the last
entry, Subindex 2 the next to the last etc.
Values Not yet defined