AMETEK 1986 DN User Manual

I

NSTRUCTION

MANUAL

DeviceNet

Resolver Based Products

This manual covers 1986DN,

Series 956

1980DN, 1990DN and 925DN
units with built in resolvers.

Contents

Chapter 1: Overview ............................... 3

Chapter 2: DeviceNet Information ......... 4

2.1 LED Operation ...............................................................4

2.2 I/O Messaging ................................................................4

2.3 Data Format ...................................................................4

Chapter 3: Getting Started ..................... 5

3.1 Establishing DeviceNet Communications ..................5

3.2 Configure the Node Address and Baud Rate .............5

3.3 Parameter Configuration ..............................................5

3.3.1 Scale Factor........... .............................................5

3.3.2 Counting Direction ...............................................5

3.3.3 Position Offset .....................................................6

3.3.4 Setpoints .............................................................6

Chapter 4: DeviceNet Object Model ....... 7

4.1 Object Model ..................................................................7

4.1.1 Objects Present in the DeviceNet Resolver ........7

4.1.2 Objects That Effect Behavior ...............................7

4.1.3 Object Interfaces .................................................7

4.1.4 Identificatoin of I/O Assembly Instances ..............7

4.1.5 Format of I/O Assembly Data Attributes ..............8

4.2 Standard Objects ..........................................................9

4.2.1 Identity Object (Class ID = 1) ..............................9

4.2.2 Message Router Object (Class ID = 2) ................9

4.2.3 DeviceNet Object (Class ID = 3) .........................9

4.2.4 Connection Object (Class ID = 5) ........................9

4.2.5 Parameter Object (Class ID = 15) .......................11

4.3 Application Specific Objects ........................................17

4.3.1 Position Object (Class ID = 100) .........................17

4.3.2 Setpoint Object (Class ID = 101) .........................17

4.3.3 RPM Object (Class ID = 102) ..............................17

4.4 Configuration Notes ......................................................18

This manual will instruct the user in programming
the GEMCO DeviceNet Resolver based products. It
is intended to cover the DeviceNet Resolver related
items only. Other, product specific, information may
be available in separate literature shipped with the
product.

Ametek has checked the accuracy of this manual
at the time it was printed. Any comments you
may have for the improvement of this manual are
welcomed.

Ametek reserves the right to revise and redistribute
the entire contents or selected pages of this manual.
All rights to the contents of this manual are reserved
by Ametek.

Appendix .................................................. 19

Product and EMC Specifications, Approvals ....................19

2

1080 N. Crooks Road • Clawson, MI 48017 • 800.635.0289 • 248.435.0700 • Fax [phone] • www.AMETEKAPT.com

Chapter 1: Overview

S2

Red

RH RL

B/R

B/W

White

Green

S1S3

GND

CHAS

Shield

S4

B/G

The DeviceNet Resolver combines the reliability
and resolution of continuous resolver position
sensing with the added flexibility of DeviceNet
communications. The resolver technology is the
same as other GEMCO resolvers which have been
proven in rugged applications like stamping press
automation. The rugged housing construction
is ideal for harsh industrial environments. All
embedded electronics are SMT constructed for the
ultimate reliability.

The DeviceNet Resolver plugs in, as a node on any
control system with a DeviceNet Scanner. Additional
resolvers are added by simply plugging into the
network. Continuous rotary positions data with
12-Bit resolution is provided. In addition, eight (8)
built-in user programmable setpoints are transmitted
over the network thus allowing direct control of
critical functions. All programming is done over the
DeviceNet network.

The DeviceNet Resolver provides flexibility and
cost savings when compared to other methods
of continuous position sensing. Each encoder is
easy to mount and wire using mini-change plug
connectors and avoiding cumbersome traditional
resolver cables. Since every DeviceNet network
is bus powered, there is no need for a separate
power supply. There are no port concentrators
to buy since all of the sensing and network
electronics are embedded within the resolver
housing. The DeviceNet Resolver and DeviceNet
scanner card are competitively priced with a plain
resolver and PLC resolver input card. Additional
DeviceNet Resolver units can be added on the
same DeviceNet network without adding additional
scanner cards. This approach is very useful when
more than one resolver per system is needed.

By using the DeviceNet Resolver it’s possible
to eliminate stand alone programmable limit
switches and other added electronic modules.
This means savings on equipment and installation
with the added benefits of improved reliability and
productivity.

1990DN Wiring Diagram

1080 N. Crooks Road • Clawson, MI 48017 • 800.635.0289 • 248.435.0700 • Fax [phone] • www.AMETEKAPT.com

3

Chapter 2: DeviceNet Information

The DeviceNet Resolver operates as a “Group
2 only slave” device. It operates as an input only
device on the DeviceNet network. All device
configurations are accomplished by using any
DeviceNet software configuration tool.

The DeviceNet Resolver is capable of
communicating at all three DeviceNet baud rates,
125K, 250K, and 500K. The node address can
be set to any address, 0 - 63. There are several
parameters: scale factor, counting direction, and
8 programmable setpoint that are configured or
modified by the user through the Parameter Object.
(See section 4.0: DeviceNet Resolver Object
Model).

2.1: LED Operation

The DeviceNet Resolver is equipped with a Network
Status LED. The network Status LED operates as
follows:

Bit Strobe Message

A bit strobed message connection is a very fast
method by which a master sends one bit (Bit Strobe
Command) out on the network and receives up to
8 bytes of data (Bit Strobe Response) from each
slave device that supports a Bit Strobe Message
Connection. The DeviceNet Resolver disregards the
command message. No user-defined configuration
is required.

Polled I/O Message

A polled message connection is used for devices
that have inputs and outputs. It can also be used for
“Input Only” devices. The master sends out a Polled
Command to each individual device and the device
responds with an 8 byte Polled Response. The
Polled message connection is not the most efficient
message connection to use for “Input Only” devices
because there is a Command message sent to and
a Response message sent from each device. This
creates a lot of unnecessary network traffic.

Solid Green = Allocated by Master
Flashing Green = Passed Duplicate MAC ID Test

and is awaiting to be allocated by Master
Solid Red = Fatal error. Requires user intervention.
Check for duplicate MAC ID or baud rate
communication rate setting.

2.2: I/O Messaging

The DeviceNet Resolver supports Bit-Strobe
Message Connection as well as a Polled I/O
Message connection. The DeviceNet Resolver does
not support Cyclic I/O or Change-of-State Message
Connections.

Setpoint Data Position Data

0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15

Position Data RPM Data

16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31

RPM Data Not Used

32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47

Not Used

48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63

2.3: Data Format

The setpoint status is supplied in the first 8 bits
of the I/O message. One bit for each setpoint,
“0 = off” and “1 = on”. The next 16 bits will provide
the scaled resolver position information (4095
maximum). And finally, the next 16 bits will provide
the RPM data (1024 maximum). The entire I/O
message is 40 bits long. You will need to reserve 40
bits in your controller I/O image table.

4

1080 N. Crooks Road • Clawson, MI 48017 • 800.635.0289 • 248.435.0700 • Fax [phone] • www.AMETEKAPT.com

Chapter 3: Getting Started

3.1: Establishing DeviceNet
Communications

NOTE: This manual assumes that the network is
configured in accordance with the DeviceNet wiring
specification.

1. Remove the DeviceNet Resolver from the box
and connect your DeviceNet cable to the 5-pin
mini connector on the back of the resolver
according to the DeviceNet wiring specifications.

2. Make sure that there is power on the DeviceNet
network when you connect the DeviceNet
Resolver to the network.

3. The DeviceNet Resolver will undergo an
initialization sequence, flashing the network
status LED. The LED will first turn green then red
and then flash green. At this point, the DeviceNet
Resolver has passed its duplicate MAC ID test
and is ready to be allocated by a master.

4. If the network status LED stays solid red, remove
the DeviceNet Resolver from the network and
then reconnect. If the LED is still solid red, then
go to section 3.2: Configure the Node Address
and Baud Rate.

3.2: Configure the Node

Address and Baud Rate

1. When the network status is flashing green you
may change the device node address (MAC ID)
and the baud rate using any DeviceNet software
configuration tool. Defaults are node address 63
and 125K baud.

2. If you change the node address, the DeviceNet
Resolver will undergo the initialization sequence
and assume the new node address.

3. If you change the baud rate, the new baud
rate will not take effect until power is cycled to
the DeviceNet Resolver and the initialization
sequence occurs.

4. Confirm the new node address and baud rate are
set correctly by using the software configuration
tool to scan the network for the DeviceNet
Resolver.

3.3: Parameter Configuration

After the baud rate and node address have been
established, the device parameters are ready to be
configured. The parameters must be configured in

the following sequence:

3.3.1: Scale Factor

The scale factor range is from 2 to 4096. The scale
factor can not exceed 4096. The scale factor is
configured through the Parameter Object. The
default scale factor is 4096.

NOTE: Changing the scale factor will result in
clearing the position offset and resetting all of the
setpoint values to zero. Therefore, the scale factor
should be set prior to configuring any setpoints or
position offset.

Set Parameter Instance 2 Attribute ID 1 Desired
Value. Desired Value = 2 to 4096.

3.3.2: Counting Direction

The DeviceNet Resolver can be configured to count
(increment) in either direction. The default direction
is clockwise.

Set Parameter Instance 3 Attribute ID 1 Desired
Value. Desired Value = 0 for clockwise, 1 for
counter clockwise.

1080 N. Crooks Road • Clawson, MI 48017 • 800.635.0289 • 248.435.0700 • Fax [phone] • www.AMETEKAPT.com

5

3.3.3: Position Offset

The indicated position of the resolver can be
changed to synchronize or “zero” the resolver to the
machine it is attached to. The resolver position can
be changed by moving the resolver at the desired
position and writing the desired indicated position to
attribute 1 of the Position Object. All setpoints will be
based on this offset position. A valid position value

3.3.4: Setpoints

As indicated the DeviceNet Resolver has 8
programmable setpoints. Each setpoint is
individually programmed through the Parameter
Object. Each setpoint has an “On Position” value
and an “Off Position” value. All setpoint defaults are
set to 0. Each setpoint has only one “On” and

one “Off” per revolution.

can range between, and include, zero and the scale
factor. (i.e. 0 < position < scale factor).

NOTE: The setpoints can be changed after the
scale factor has been established. The setpoints
cannot be configured outside the scale factor range.

Setpoint 1 “On” Position Set Parameter Instance 5 Attribute ID 1 Desired On Position Value

Setpoint 1 “Off” Position Set Parameter Instance 6 Attribute ID 1 Desired Off Position Value

Setpoint 2 “On” Position Set Parameter Instance 7 Attribute ID 1 Desired On Position Value

Setpoint 2 “Off” Position Set Parameter Instance 8 Attribute ID 1 Desired Off Position Value

Setpoint 3 “On” Position Set Parameter Instance 9 Attribute ID 1 Desired On Position Value

Setpoint 3 “Off” Position Set Parameter Instance 10 Attribute ID 1 Desired Off Position Value

Setpoint 4 “On” Position Set Parameter Instance 11 Attribute ID 1 Desired On Position Value

Setpoint 4 “Off” Position Set Parameter Instance 12 Attribute ID 1 Desired Off Position Value

Setpoint 5 “On” Position Set Parameter Instance 13 Attribute ID 1 Desired On Position Value

Setpoint 5 “Off” Position Set Parameter Instance 14 Attribute ID 1 Desired Off Position Value

Setpoint 6 “On” Position Set Parameter Instance 15 Attribute ID 1 Desired On Position Value

Setpoint 6 “Off” Position Set Parameter Instance 16 Attribute ID 1 Desired Off Position Value

Setpoint 7 “On” Position Set Parameter Instance 17 Attribute ID 1 Desired On Position Value

Setpoint 7 “Off” Position Set Parameter Instance 18 Attribute ID 1 Desired Off Position Value

Setpoint 8 “On” Position Set Parameter Instance 19 Attribute ID 1 Desired On Position Value

Setpoint 8 “Off” Position Set Parameter Instance 20 Attribute ID 1 Desired Off Position Value

6

1080 N. Crooks Road • Clawson, MI 48017 • 800.635.0289 • 248.435.0700 • Fax [phone] • www.AMETEKAPT.com