Manual DeviceNet Fraba Posital
Manual DeviceNet Fraba Posital
USER MANUAL
Page1
CONTENTS
Page 2
1. Introduction ..................................................... 4 Clamp flange (C10) ..............................................37
1.1 Control and Information Protocol (CIP) ............ 5 Clamp flanch (S), 5 pin connector ........................38
1.2 Object modell ................................................... 6 Hollow Shaft (B) ...................................................39
Page3
1. Introduction
Absolute rotary encoders provide a definite value The integrated CAN-Bus interface of the absolute
for every possible position. All these values are rotary encoder supports all of the DeviceNet
reflected on one or more code discs. The beams of functions. The following modes can be
infrared LEDs are sent through code discs and programmed and enabled or disabled:
detected by Opto-Arrays. The output signals are - Polled Mode
electronically amplified and the resulting value is - Change of State
transferred to the interface. The protocol supports the programming of the
following additional functions:
The absolute rotary encoder has a maximum Code sequence (Complement)
resolution of 65536 steps per revolution (16 Bit). Resolution per revolution
The Multi-Turn version can detect up to 16384 Total resolution
revolutions (14 Bit). Therefore the largest resulting Preset value
resolution is 30 Bit = 1.073.741.824 steps. The Baudrate
standard Single-Turn version has 12 Bit, the MAC-ID
standard Multi-Turn version 24 Bit.
The general use of absolute rotary encoders with
DeviceNet interface is guaranteed.
Page 4
1.1 Control and Information Protocol (CIP)
The DeviceNet specification defines the CIP (Common Industrial Protocol) make for the
Application Layer and the Physical Layer. The user available four essential functions:
Data Link layer is based on the CAN-
specification. For the optimal industrial control • Unique control service
will be defined two different messaging types. • Unique communication service
I/O messaging (Implicit Messaging ) and explicit • Unique allocation of messaging
messaging.With Implicit Messaging becoming • Common knowledge base
I/O data exchanged in realtime and with Explicit
Messaging becoming data exchanged to
configure a device.
Page5
1.2 Object modell
DeviceNet describes all data and functions of a device considering as object model. By means of that
object-oriented description a device can be defined complete with single objects. A object is defined across
the centralization by associated attributes (e.g. processdata), his functions (read- or write access of a
single attribute) as well as by the defined behaviour.
Page 6
2. Data Transmission
The data transmission in the DeviceNet network CAN-ID Message Header Message Body
is realised by message telegrams. Basically, 11 Bit 1 Byte 7 Byte
these telegrams can be divided into the CAN-ID
and 8 following bytes as shown in the table
below:
Attribute
Access Name Data Type Description
ID
1 hex Get Number of Attributes USINT Number of supported Attributes
2 hex Get Attribute Array of USINT List of supported Attribute
3 hex Get Position value DINT current position
70 hex Get / Set Code sequence Boolean Controls the code sequence
clockwise or counterclockwise
71 hex Get / Set resolution per revolution INT resolution for one revolution
72 hex Get / Set total resolution DINT total measurable resolution
73 hex Get / Set preset value DINT setting a defined position value
6E hex Get / Set Baudrate Adjustment of the Baudrate
6F hex Get / Set MAC ID Adjustment of the MAC ID
Page 7
2.2 Definition of the CAN-ID
DeviceNet is based on the standard CAN- CAN-Identifier consists of the Message Group,
protocol and used a 11Bit (2048 specifiable Message ID and the MAC ID of the device.
messages) messages identifier. For the By our absolute rotary encoder it is a matter of a
identification of a device in a DeviceNet network Group 2 Messages. In the table below a user
are 6Bit enough because a network belongs 64 can see the importance CAN-IDs for a certain
nodes. That nodes will be call MAC-ID. The communication type.
.
10 9 8 7 6 5 4 3 2 1 0 Identity Hex
Usage Range
0 Group 1 Source MAC ID GROUP 1 Message 000-3ff
Message ID
0 1 1 0 1 Source MAC ID Slave’s I/O Change of State or Cyclic Message
0 1 1 1 1 Source MAC ID Slave’s I/O Poll Response or Change of State/Cyclic
Acknowledge Message
1 0 MAC ID Group 2 GROUP 2 Messages 400 - 5ff
Message
ID
1 0 Destination MAC 0 1 0 Master’s Change of State or Cyclic Acknowledge
ID Message
1 0 Source MAC ID 0 1 1 Slave’s Explicit/Unconnected Response Messages
1 0 Destination MAC 1 0 0 Master’s Explicit Request Message
ID
1 0 Destination MAC 1 0 1 Master’s I/O Poll Command/Change of State/Cyclic
ID Message
1 0 Destination MAC 1 1 0 Group 2 Only Unconnected Explicit Request Message
ID (reserved)
1 0 Destination MAC 1 1 1 Duplicate MAC ID Check Messages
ID
Page 8
3. Programmable Parameters
3.1. Encoder parameters
3.1.1. Operating Parameter
The parameter resolution per revolution is used to steps per revolution. Each value between 1 and
program the encoder to set a desired number of the maximum (see type shield) can be realised
When the value is set larger than 4096 (8192 for a be skipped while rotating the shaft. So, it is
13/25 Bit encoder), the process value of the recommended, to keep the measuring steps per
encoder will not be single stepped and values will revolution below 4096 (8192) measuring steps.
Page 9
3.1.3. Total resolution
This value is used to program the desired number (25 bit = 33,554,432 steps). Please note the value
of measuring steps over the total measuring range. written on the type shield.
This value must not exceed the total resolution of
the encoder with 24 bit = 16,777,216 steps
The preset value is the desired position value, encoder is set to the desired process value by
which should be reached at a certain physical the parameter preset. The preset value must not
position of the axis. The position value of the exceed the parameter total measuring units
Page 10
3.1.5. MAC-ID
Each node in a Device Net network is identified 64 nedoes. The MAC-ID can only be adjusted
using a MAC-ID (Media Access Control via explicit messaging. The default MAC-ID is
Identifier). Every device needs an explicit and setting on d63.
unique MAC-ID. A Device Net netwok supports
3.1.6. Baudrate
Device Net supports three different baurates that baudrate has to be the same as the Device Net
are being showed in the below table. The network baudrate. The default baudrate is
baudrate can be changed via explicit messages setting 125kBaud.
and stored in the EEPROM with a save
command. It is to insure that the selective
0x Baudrate in kBaud
0 125
1 250
2 500
Page11
4. Operating Mode
4.1. Polled Mode
For switching the polled mode on the following following example a master MAC ID of 0A hex and
telegrams are needed. Further it is assumed in the a slave MAC ID of 03 hex.
1. Allocate Polling
Byte Offset Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
0 Frag [0] XID MAC ID
1 R/R [0] Service [4B]
Class ID [03]
Instance ID [01]
Allocation Choice [03]
0 0 Allocator MAC ID
Definition CAN ID
10 9 8 7 6 5 4 3 2 1 0 Identity Hex
Usage Range
1 0 Destination MAC 1 1 0 Group 2 Only Unconnected Explicit Request
ID Message (reserved)
Example:
CAN-ID Byte 0 Byte 1 Byte 2 Byte 3 Byte 4 Byte 5
41E 0A 4B 03 01 03 0A
Definition CAN-ID
10 9 8 7 6 5 4 3 2 1 0 Identity Hex
Usage Range
1 0 Destination MAC 1 0 0 Master´s Explicit Request Message
ID
Page12
Example:
CAN-ID Byte 0 Byte 1 Byte 2 Byte 3 Byte 4 Byte 5 Byte 6
41C 0A 10 05 01 09 00 00
Example:
CAN-ID Byte 0 Byte 1 Byte 2 Byte 3 Byte 4 Byte 5 Byte 6
41C 0A 10 05 02 09 00 00
Release Polling
Byte Offset Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
0 Frag [0] XID MAC ID
1 R/R [0] Service [4C]
Class ID [03]
Instance ID [01]
Release Choice [03]
Example:
CAN-ID Byte 0 Byte 1 Byte 2 Byte 3 Byte 4
41E 0A 4C 03 01 03
Page 13
4.2. Change of State Mode
The absolute rotary encoder sends data, without position value is not changing. This results in a
any request from the host, when the actual process reduced bus loading.
value is changing. No telegram will occur when the
Allocate COS
Byte Offset Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
0 Frag [0] XID MAC ID
1 R/R [0] Service [4B]
Class ID [03]
Instance ID [01]
Allocation Choice [51]
0 0 Allocator MAC ID
Example:
CAN-ID Byte 0 Byte 1 Byte 2 Byte 3 Byte 4 Byte 5
41E 0A 4B 03 01 51 0A
Example:
CAN-ID Byte 0 Byte 1 Byte 2 Byte 3 Byte 4 Byte 5 Byte 6
41C 0A 10 05 01 09 00 00
Example:
CAN-ID Byte 0 Byte 1 Byte 2 Byte 3 Byte 4 Byte 5 Byte 6
41C 0A 10 05 04 09 00 00
Page 14
Release Master / Slave Connection Set
Release COS
Byte Offset Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
0 Frag [0] XID MAC ID
1 R/R [0] Service [4C]
Class ID [03]
Instance ID [01]
Release Choice [51]
Example:
CAN-ID Byte 0 Byte 1 Byte 2 Byte 3 Byte 4
41E 0A 4C 03 01 51
Page 15
4.3. Saving Parameter
The parameters of the absolute rotary encoder are examination, those values can be saved in the
saved in a non-volatile FLASH memory. Because FLASH memory. After successful saving of the
of a limited number of writing cycles (≈ 1,000), it is parameter the encoder sends his MAC-ID on the
useful to transmit the modified parameter in the bus. To get the process value a new allocation of
first step only in the RAM area. After adjusting and the slave is required.
Example:
(MAC-ID Master: 0A hex, MAC-ID Slave: 03 hex)
CAN-ID Byte 0 Byte 1 Byte 2 Byte 3
41C 0A 32 23 01
Page 16
6. Installation
6.1. Electrical connection
The rotary encoder is connected by three cables. There is a resistor provided in the connection cap,
The power supply is achieved with a two-wire which must be used as a line termination on the
connection cable through one PG 9. Each one of last device
the twisted-pair and shielded bus lines are guided
in and out through two PG 9 on the right side (as Resistor:
seen on clamps)
Last Device Device X
RT RT RT
ON
ON ON
78
78
23
23
23
Clamp Description
⊥ Ground
+ 24 V Supply voltage
- 0 V Supply voltage
CG CAN Ground
CL CAN Low
CH CAN High
CG CAN Ground
CL CAN Low
CH CAN High
Page 17
6.2. Setting of the baudrate
6.3 Cabel
6.3 Connector
4 3
1 2
5 pin connector
Page 18
7. Power On
7.1. Operating Mode
7.2. Programming
If some parameters should not be modified you format. In the examples, the CAN ID and MAC ID
can skip over this chapter. are 0A (hex) and for the slave 03 (hex).
The following numbers are given in hexadecimal The changeable values are written in an italics.
Page 19
Absolute rotary encoder to master: Confirmation
CAN ID MAC ID Service Code
Byte0 Byte1
41B 0A 90
Page 20
7.2.4. Preset Value
Page 21
7.2.5. MAC-ID
7.2.6. Baudrate
X Baudrate
o 125kbaud
1 250kbaud
2 500kbaud
Page 22
7.2.7. Parameter Saving
If the transfer has been successful, the absolute If the transfer is not successful, an error
rotary encoder responds after 3-4s with the message will be sent. The service code used to
Duplicate MAC-ID. After that the master must save the parameter set is manufacturer specific.
reallocate the slave.
Page 23
8. RsNetworx
8.1. EDS Wizard
The EDS File contains information about device which can be used to configure the device in the
specific parameters as well as possible network, for example with RsNetworx from
operating modes of the encoder. With this file Rockwell.
you have a data sheet in an electronic format,
To install the EDS file the EDS Wizard has to be be chosen and after that the button weiter. In the
started, that can be done in the menu Tools/EDS next step the Register a directory of EDS files
Wizard. If the EDS Wizard is activated has to be chosen and with Browse the path of
successfully the Register an EDS File(s) has to the EDS file(s). That is indicated in picture 1.2.
Page 24
1.2 EDS Wizard
The Wizard finds all EDS files that are discarded (see picture 1.3) pictures can be selected for the
in the choosing path and operates a test to using nodes. With the button weiter the
check the EDS files on errors. In the next step installation can be continued and finished.
Page 25
1.3 EDS Wizard
After a successful installing of the EDS file the KFD is being used. In the next step the window
next step is to choose the suitable driver. With Configure Drivers in the menu Communications/
Start/Programme/Rockwell Software/RSLinx in Configure Drivers has to be started. In the drop
the menu the programm RSLinx can be started. down Menü Available Driver Types the driver typ
With this programm the suitable driver can be 1770-KFD has to be chosen and confirmed with
chosen. For this example the driver typ 1770- the button Add New. (See picture 1.4)
Page 26
1.4 Cofigure Drivers
If the suitable driver is chosen it can be registered (picture 1.5). In the next step a
configured in the window Driver Configuration. In requested name can be registered.
this step the correct baudrate has to be
Page 27
8.3 Network Connection
This chapter will explain how to switch a network has been choosen, this is explained in chapter
online and how to parametrise a encoder. In the 6.2, the network is online. After that RsNetworx
menu Network/ Online the window Browse for searches in the network for connecting nodes.
network will be opened. If the driver 1770-KFD That is also being showed in picture 1.6.
Page 28
1.7 Upload Parameter
After a successful upload of the parameters, pushed. It should be noticed that the
those can be configured as the picture 1.8 below configuration parameters are not stored in the
shows. A download of the configured EEPROM. To store the parameters in the
parameters can be realized with the yellow EEPROM the window in the menu Device/Class
arrow that is showing down and is placed at the Instance Editor has to be opened. The entries
top right in the configuration window. An upload that are necessary to store the parameters are
can be realized with the arrow beside the being showed in the picture 1.9 below. At last
download arrow which is showing up. To show the button execute has to be executed to store
the position value the button Monitor has to be the parameters in the EEPROM.
Page 29
1.8 Configure Parameters
Page 30
9. Technical Data
9.1 Electrical Data
Page 31
9.3 Minimum (mechanical) lifetime
9. 4 Environmental Conditions
Page 32
Mechanical Drawings
Page 33
Hollow shaft (B)
Mounting instructions
The clamp ring may only be tightened if the shaft of Allowed shaft movements of the drive element are
the driving element is in the hollow shaft. listed in the table.
The diameter of the hollow shaft can be reduced to
12mm, 10 mm or 8 mm by using an adapter (this axial radial
reducing adapter can be pushed into the hollow static ± 0,3 mm ± 0,5 mm
shaft). dynamic ± 0,1 mm ± 0,2 mm
Page 34
Connection cap with 5pin round connector, Micro style
Page 35
Synchro flange (S)
Two types available
Synchro flange d / mm l / mm
Typ S06 6f6 10
Typ S10 10h8 20
L in mm
Single-Turn axial 53
radial 53
Multi-Turn axial 62
radial 62
Seite 36
Clamp flange (C10)
L in mm
Single-Turn axial 53
radial 53
Multi-Turn axial 62
radial 62
Page 37
Clamp flanch (S), 5 pin connector
The dimensions of the housing from type Clamp
flange 5 pin connector are the same like the type
synchro flange.
L im mm
Single-Turn axial 53
radial 53
Multi-Turn axial 62
radial 62
Page 38
Hollow Shaft (B)
L
Single-Turn axial 72
radial 72
Multi-Turn axial 81
radial 81
Page 39
Heavy Duty version
Page 40
Heavy Duty version with full shaft Flangetype l [mm]
Clampflange available in two versions. Standard 10
Optional 4
72
Singleturn=66, Multiturn=90
Ø63
3,3
1,3
Ø12 F7
Ø60
20
20
73
Ø3.2
an Momentenst黷ze
Anlagekante
12,5
32
21,5 IN OUT
Max. Welleneinstecktiefe = 30
Min. Welleneinstecktiefe = 15
Page 41
10. Versions / Order Description
Page 42
Connection caps
Description Type
Description Type
Shaft coupling** Drilling: 10 mm GS 10
Drilling:: 6 mm GS 06
Clamp disc** 4 pcs. / AWC SP 15
Clamp ring** 2 pcs. / AWC SP H
Reducing adapter *** 15 mm to 12 mm RR12
Reducing adapter *** 15 mm to 10 mm RR10
Reducing adapter *** 15 mm to 8 mm RR8
User Manual* Installation and configuration manual, German UMD-DA
User Manual* Installation and configuration manual, English UME-DA
Page 43
Diskette mit EDS-File**
Encoder with connection cap EDS-File**
SAG-D2B1B-0012-xxxx-OCC SAG -D2B1B-1213-0013-xxxx-OCC.eds
SAG -D2B1B-0013-xxxx-OCC SAG -D2B1B-1213-0013-xxxx-OCC.eds
SAG -D2B1B-0016-xxxx-OCC SAG -D2B1B-0016-xxxx-OCC.eds
SAG -D2B1B-1212-xxxx-OCC SAG -D2B1B-1213-0013-xxxx-OCC.eds
SAG -D2B1B-1213-xxxx-OCC SAG -D2B1B-1213-0013-xxxx-OCC.eds
SAG -D2B1B-1216-xxxx-OCC SAG -D2B1B-1216-xxxx-OCC.eds
SAG -D2B1B-1412-xxxx-OCC SAG -D2B1B-1412-xxxx-OCC.eds
SAG -D2B1B-1413-xxxx-OCC SAG -D2B1B-1413-xxxx-OCC.eds
SAG -D2B1B-1416-xxxx-OCC SAG -D2B1B-1416-xxxx-OCC.eds
Encoder without connection cap EDS-File**
SAG -D2B1B-0012-xxxx-xxx SAG -D2B1B-1213-0013-xxxx-xxx.eds
SAG -D2B1B-0013-xxxx- xxx SAG -D2B1B-1213-0013-xxxx-xxx.eds
SAG -D2B1B-0016-xxxx- xxx SAG -D2B1B-0016-xxxx- xxx.eds
SAG -D2B1B-1212-xxxx- xxx SAG -D2B1B-1213-0013-xxxx-xxx.eds
SAG -D2B1B-1213-xxxx- xxx SAG -D2B1B-1213-0013-xxxx-xxx.eds
SAG -D2B1B-1216-xxxx- xxx SAG -D2B1B-1216-xxxx- xxx.eds
SAG -D2B1B-1412-xxxx- xxx SAG -D2B1B-1412-xxxx- xxx.eds
SAG -D2B1B-1413-xxxx- xxx SAG -D2B1B-1413-xxxx- xxx.eds
SAG -D2B1B-1416-xxxx- xxx SAG -D2B1B-1416-xxxx- xxx.eds
We do not assume responsibility for technical inaccuracies or omissions. Specifications are subject to
change without notice.
Page 44