WEG DeviceNet CFW500 User manual

DeviceNet
CFW500
User’s Manual
Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [email protected]

DeviceNet User’s Manual
Series: CFW500
Language: English
Document Number: 10002253313 / 00
Publication Date: 05/2013
Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [email protected]

CONTENTS
CONTENTS ...............................................................................................................................3
ABOUT THIS MANUAL............................................................................................................5
ABBREVIATIONS AND DEFINITIONS........................................................................................... 5
NUMERICAL REPRESENTATION ................................................................................................ 5
DOCUMENTS............................................................................................................................ 5
1INTRODUCTION TO THE DEVICENET COMMUNICATION.........................................6
1.1 C AN................................................................................................................................. 6
1.1.1 D at a F r am e................................................................................................................ 6
1.1.2 Remote Frame........................................................................................................... 6
1.1.3 Access to the Network ............................................................................................... 6
1.1.4 Error Control.............................................................................................................. 6
1.1.5 CAN and DeviceNet.................................................................................................... 7
1.2 DEVICENET NETWORK CHARACTERISTICS...................................................................... 7
1.3 PHYSICAL LAYER ............................................................................................................ 7
1.3.1 D at a L in k L ay er.......................................................................................................... 8
1.3.2 Network and Transport Layer ..................................................................................... 8
1.3.3 Application Layer – CIP Protocol................................................................................. 9
1.3.4 Configuration File (EDS).............................................................................................. 9
1.3.5 Communication Modes .............................................................................................. 9
1.3.6 Set of Predefined Master/Slave Connections ............................................................. 10
2DEVICENET COMMUNICATION ACCESSORY...........................................................11
2.1 PLUG-IN MODULE CFW500-CCAN .................................................................................. 11
2.2 CONNECTOR PINOUT.................................................................................................... 11
2.3 POWER SUPPLY ............................................................................................................ 11
2.4 INDICATIONS................................................................................................................. 11
2.5 MODULE CONFIGURATION............................................................................................ 12
2.6 ACCESS TO THE PARAMETERS...................................................................................... 12
3DEVICENET NETWORK INSTALLATION .....................................................................13
3.1 BAUD RATE................................................................................................................... 13
3.2 ADDRESS IN THE DEVICENET NETWORK ....................................................................... 13
3.3 TERMINATION RESISTOR............................................................................................... 13
3.4 C A BL E........................................................................................................................... 13
3.5 CONNECTION IN THE NETWORK.................................................................................... 13
4PROGRAMMING..............................................................................................................15
4.1 SYMBOLS FOR THE PROPERTIES DESCRIPTION ............................................................ 15
P0105 – 1ST/2ND RA MP SEL E CT I ON ............................................................................................ 15
P0220 – LOCAL/REMOTE SELECTION SOURCE........................................................................ 15
P0221 – SPEED REFERENCE SELECTION – L OC AL SITUATION.................................................. 15
P0222 – SPEED REFERENCE SELECTION – REMOTE SITUATION............................................... 15
P0223 – FORWARD/REVERSE SELECTION – LOCAL SITUATION ................................................ 15
P0224 – RUN / STOP SELECTION – LOCAL SITUATION................................................................ 15
P0225 – JOG SEL ECTION – LOCAL SI TU ATION.......................................................................... 15
P0226 – FORWARD/REVERSE SELECTION – REMOTE SITUATION ............................................. 15
P0227 – RUN / STOP SELECTION – REMOTE SITUATION ............................................................. 15
P0228 – JOG SEL ECTION – REM OT E SIT UA TI ON ....................................................................... 15
P0313 – COMMUNICATION ERROR AC TI ON.............................................................................. 15
P0680 – STATUS WORD ........................................................................................................... 16
Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [email protected]

P0681 – MOTOR SPEED IN 13 BITS........................................................................................... 17
P0684 – DEVICENET CONTROL WORD...................................................................................... 18
P0685 – DEVICENET SPEED REFERENCE ................................................................................. 18
P0695 – DIGITAL OUTPUT SETTING.......................................................................................... 19
P0696 – VALU E 1 FOR ANALOG OUTPUTS ................................................................................ 20
P0697 – VALU E 2 FOR ANALOG OUTPUTS ................................................................................ 20
P0698 – VALU E 3 FOR ANALOG OUTPUTS ................................................................................ 20
P0700 – CAN PROTOCOL......................................................................................................... 21
P0701 – CAN ADDRESS............................................................................................................ 21
P0702 – CAN BAUD RATE......................................................................................................... 21
P0703 – BU S OF F RESET.......................................................................................................... 22
P0705 – CAN CONTROLLER STATUS........................................................................................ 22
P0706 – RECEIVED CAN TELEGRAM COUNTER........................................................................ 23
P0707 – TRANSMITTED CAN TELEGRAM COUNTER.................................................................. 23
P0708 – BUS OFF ERROR COUNTER ........................................................................................ 23
P0709 – LOST CAN MESSAGE COUNTER.................................................................................. 23
P0710 – DEVICENET I/O INSTANCES ........................................................................................ 24
P0711 – DEVICENET READING #3............................................................................................. 27
P0712 – DEVICENET READING #4............................................................................................. 27
P0713 – DEVICENET READING #5............................................................................................. 27
P0714 – DEVICENET READING #6............................................................................................. 27
P0715 – DEVICENET WRITING #3.............................................................................................. 27
P0716 – DEVICENET WRITING #4.............................................................................................. 27
P0717 – DEVICENET WRITING #5.............................................................................................. 27
P0718 – DEVICENET WRITING #6.............................................................................................. 27
P0719 – DEVICENET NETWORK STATUS................................................................................... 28
P0720 – DEVICENET MASTER STATUS ..................................................................................... 28
5SUPPORTED OBJECT CLASSES..................................................................................29
5.1 IDENTITY CLASS (01H)................................................................................................... 29
5.2 MESSAGE ROUTER CLASS ( 02H ) .................................................................................... 29
5.3 DEVICENET CLASS (03H)................................................................................................ 29
5.4 ASSEMBLY CLASS (04H) ................................................................................................ 29
5.5 CONNECTION CLASS (05H) ............................................................................................ 30
5.5.1 Instance 1: Explicit Message..................................................................................... 30
5.5.2 Instance 2: Polled..................................................................................................... 30
5.5.3 Instance 4: Change of State/Cyclic............................................................................ 31
5.6 MOTOR DATA CLASS (28H) ............................................................................................ 31
5.7 C ON TROL SUP ERVI SOR CLASS (29H)............................................................................. 31
5.8 AC/DC DRIVE CLASS (2AH)............................................................................................. 32
5.9 ACKNOWLEDGE HANDLER CLASS (2BH)........................................................................ 32
5.10 MANUFACTURER SPECIFIC CLASSES......................................................................... 33
6FAULTS AND ALARMS RELATED TO THE DEVICENET COMMUNICATION.........34
A133/F233 – CAN INTERFACE WITHOUT POWER SUPPLY......................................................... 34
A134/F234 – BU S OF F .............................................................................................................. 34
A136/F236 – ID L E MA ST ER ....................................................................................................... 34
A137/F237 – DEVICENET CONNECTION TI M EO UT ..................................................................... 35
Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [email protected]

ABOUT THIS MANUAL
This manual provides the necessary information for the operation of the CFW500 frequency converter using the
DeviceNet protocol. This manual must be used together with the CFW500 user manual.
ABBREVIATIONS AND DEFINITIONS
ASCII
American Standard Code for Information Interchange
CAN
Controller Area Network
CiA
CAN in Automation
CIP
Common Industrial Protocol
PLC
Programmable Logic Controller
HMI
Human-Machine Interface
ODVA
Open DeviceNet Vendor Association
ro
Read only
rw
Read/write
NUMERICAL REPRESENTATION
Decimal numbers are represented by means of digits without suffix. Hexadecimal numbers are represented with
the letter ‘h’ after the number.
DOCUMENTS
The DeviceNet protocol was developed based on the following specifications and documents:
Document
Version
Source
CAN Specification
2.0
CiA
Volume One
Common Industrial Protocol (CIP) Specification
3.2
ODVA
Volume Three
DeviceNet Adaptation of CIP
1.4
ODVA
In order to obtain this documentation, consult ODVA, which is nowadays the organization that keeps, publishes
and updates the information related to the DeviceNet network.
Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [email protected]

1INTRODUCTION TO THE DEVICENET COMMUNICATION
In order to operate the equipment in a DeviceNet network, it is necessary to know the manner this
communication is performed. Therefore, this section brings a general description of the DeviceNet protocol
operation, containing the functions used by the CFW500. Refer to the protocol specification for a detailed
description.
1.1 CAN
DeviceNet is a network based on CAN, i.e., it uses CAN telegrams for exchanging data in the network.
The CAN protocol is a serial communication protocol that describes the services of layer 2 of the ISO/OSI model
(data link layer)
1
. This layer defines the different types of telegrams (frames), the error detection method, the
validation and arbitration of messages.
1.1.1 Data Frame
CAN network data is transmitted by means of a data frame. This frame type is composed mainly by an 11 bit
2
identifier (arbitration field), and by a data field that may contain up to 8 data bytes.
Identifier
8 data bytes
11 bits
byte 0
byte 1
byte 2
byte 3
byte 4
byte 5
byte 6
byte 7
1.1.2 Remote Frame
Besides the data frame, there is also the remote frame (RTR frame). This type of frame does not have a data
field, but only the identifier. It works as a request, so that another network device transmits the desired data
frame. The DeviceNet communication protocol does not use this type of frame.
1.1.3 Access to the Network
Any device in a CAN network can make an attempt to transmit a frame to the network in a certain moment. If
two devices try to access the network simultaneously, the one that sends the message with the highest priority
will be able to transmit. The message priority is defined by the CAN frame identifier, the smaller the value of this
identifier, the higher the message priority. The telegram with the identifier 0 (zero) is the one with the highest
priority.
1.1.4 Error Control
The CAN specification defines several error control mechanisms, which makes the network very reliable and
with a very low undetected transmission error rate. Every network device must be able to identify the
occurrence of these errors, and to inform the other elements that an error was detected.
A CAN network device has internal counters that are incremented every time a transmission or reception error is
detected, and are decremented when a telegram is successfully transmitted or received. If a considerable
amount of errors occurs, the device can be led to the following states:

Error Active:
the internal error counters are at a low level and the device operates normally in the CAN
network. You can send and receive telegrams and act in the CAN network if it detects any error in the
transmission of telegrams.

Warning:
when the counter exceeds a defined limit, the device enters the warning state, meaning the
occurrence of a high error rate.

Error Passive:
when this value exceeds a higher limit, the device enters the error passive state, and it stops
acting in the network when detecting that another device sent a telegram with an error.

Bus Off:
finally, we have the bus off state, in which the device will not send or receive telegrams any more.
The device operates as if disconnected from the network.
1
In the CAN protocol specification, the ISO11898 standard is referenced as the definition of the layer 1 of this model (physical layer).
2
The CAN 2.0 specification defines two data frame types, standard (11 bit) and extended (29 bit). For this implementation, only the standard
frames are accepted.
Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [email protected]

1.1.5 CAN and DeviceNet
Only the definition of how to detect errors, create and transmit a frame, are not enough to define a meaning for
the data transmitted via the network. It is necessary to have a specification that indicates how the identifier and
the data must be assembled and how the information must be exchanged. Thus, the network elements can
interpret the transmitted data correctly. In that sense, the DeviceNet specification defines exactly how to
exchange data among the devices and how every one must interpret these data.
There are several other protocols based on CAN, as DeviceNet, CANopen, J1939, etc., which use CAN frames
for the communication. However, those protocols cannot be used together in the same network.
1.2 DEVICENET NETWORK CHARACTERISTICS
Introduced in 1994, DeviceNet is an implementation of the Common Industrial Protocol (CIP) for industrial
communication networks. Developed originally by Allen-Bradley, it had its technology transferred to the ODVA
that, since then, keeps, publishes and promotes DeviceNet and other networks based on the CIP
3
protocol.
Furthermore, it uses the Controller Area Network (CAN) protocol for the data link and access to the medium,
layers 2 and 1 of the OSI/ISO model, respectively.
Used mainly for the connection of industrial controllers and I/O devices, the protocol follows the model
producer-consumer, supports multiple communication modes and has priority between messages.
It is a system that can be configured to operate in master-slave architecture as well as in a distributed point-to-
point architecture. Besides, it defines two kinds of messages, I/O (process data) and explicit (configuration and
parameter setting). It also has mechanisms to detect duplicated addresses and for node isolation in case of
critical faults.
A DeviceNet network canhave up to 64 devices, addressed from 0 to 63. Any of them can be used. There is no
restriction, although the 63 should be avoided because it is usually used for commissioning.
1.3 PHYSICAL LAYER
DeviceNet uses a network topology of the trunk/derivation type that allows the signal wiring as well as the power
wiring to be present in the same cable. This power is supplied by a power supply connected directly to the
network, which feeds the CAN transceivers of the nodes, and has the following characteristics:
24 Vdc;
DC output isolated from the AC input;
Current capacity compatible with the installed equipment.
The used Baud rate depends on the size (cable length) of the network, as showed in the table 1.1.
Table 1.1: Network size x Baud rate
Baud Rate
Network
Size
Derivation
Maximum
Total
125 kbps
500 m
6 m
156 m
250 kbps
250 m
78 m
500 kbps
100 m
39 m
In order to avoid reflections in the line, it is recommended the installation of termination resistors at the line
extremes, because the absence of them may cause intermittent errors. This resistor must have the following
characteristics, according to the protocol specification:
121 Ω;
0.25 W;
1% tolerance.
3
CIP actually represents a family of networks. DeviceNet, EtherNet/IP and ControlNet use CIP in the application layer. The difference among
them is primordially in the data link and physical layers.
Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [email protected]

For DeviceNet, several types of connectors can be used, sealed ones as well as open ones. The definition of the
type to be used depends on the application and on the equipment operation environment. The CFW500 uses a
5 wire plug-in connector, and its pinout is showed in the section 2. For a complete description of the
connectors used with DeviceNet, consult the protocol specification.
1.3.1 Data Link Layer
The DeviceNet data link layer is defined by the CAN specification, which defines two possible states; dominant
(logic level 0) and recessive (logic level 1). A node can bring the network to the dominant state if it transmits any
information. Thus, the bus will only be in the recessive state if there where no transmitting nodes in the dominant
state.
CAN uses the CSMA/NBA to access the physical medium. This means that a node, before transmitting, must
verify if the bus is free. In case it is, then the node can initiate the transmission of its telegram. In case it is not,
then the node must await. If more than one node access the network simultaneously, a priority mechanism
takes action to decide which one will have priority over the others. This mechanism is not destructive, i.e., the
message is preserved even if there is a collision between two or more telegrams.
CAN defines four types of telegrams (
data , remote , overload and error ). Among them, DeviceNet uses only the
data frame and the error frame .
Data is moved using the data frame. This frame structure is showed in the figure 1.1.
Interframe
Space 1 bit 11 bits 1 bit 6 bits 0-8 bytes 15 bits 1 bit 1 bit 1 bit 7 bits ≥ 3 bits
Start of Frame
Identifier
RTR bit
Control Field
Data Field
CRC Sequence
CRC Delimiter
ACK Slot
ACK Delimiter
End of Frame
Interframe Space
Figure 1.1: CAN data frame
Errors, however, are indicated by means of the error frames. CAN has a very robust error verification and
confinement. This assures that a node with problems does not impair the communication in the network.
For a complete description of the errors, consult the CAN specification.
1.3.2 Network and Transport Layer
DeviceNet requires that a connection be established before data exchange with the device takes place. In order
to establish this connection each DeviceNet node must implement the
Unconnected Message Manager
(UCMM) or the
Group 2 Unconnected Port . These two allocation mechanisms use messages of the explicit type
to establish a connection, which will then be used for process data exchange between one node and the other.
This data exchange uses messages of the I/O type (refer to item 1.3.5).
The DeviceNet telegrams are classified in groups, which define specific functions and priorities. Those telegrams
use the identifier field (11 bits) of the CAN data frame to uniquely identify each one of the messages, thus
assuring the CAN priority mechanism.
A DeviceNet node can be a client, a server or both. Furthermore, clients and servers can be producers and/or
consumers of messages. In a typical client node, for instance, its connection will produce requests and will
consume answers. Other client or server connections will only consume messages. In other words, the protocol
allows several connection possibilities among the devices.
The protocol also has a resource for detection of nodes with duplicated addresses (Mac ID). Avoiding that
duplicated addresses occur is, in general, more efficient than trying to locate them later.
Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [email protected]

1.3.3 Application Layer – CIP Protocol
In the application layer, DeviceNet uses the
Common Industrial Protocol (CIP). It is a protocol strictly orientated
to objects, used also by ControlNet and EtherNet/IP. In other words, it is independent from the physical medium
and from the data link layer. The figure 1.2 presents the structure of this protocol.
Figure 1.2:CIP protocol structure in layers
The CIP has two main purposes:
Transport of I/O devices control data.
Transport of configuration and diagnosis information of the system being controlled.
A DeviceNet node (master or slave) is then molded by a set of CIP objects, which encapsulate data and
services, thus determining its behavior.
There are obligatory objects (eachdevice must have) and optional objects. Optional objects are those that mold
the device according to the category (called profile) to which they belong, as: AC/DC drive, bar code reader or
pneumatic valve. For being different, each one of these will contain a group of also different objects.
For more information refer to the DeviceNet specification. It presents the complete list of devices already
standardized by the ODVA, as well as the objects that compose them.
1.3.4 Configuration File (EDS)
Each device in a DeviceNet network has an EDS configuration file that contains information about the device
operation and must be registered in the network configuration software, for programming of devices present in
the DeviceNet Network.
The EDS configuration file is supplied together with the product, and it can also be obtained from the
website.It is necessary to observe the equipment software version, in order to use an EDS file that is
compatible with that version.
1.3.5 Communication Modes
The DeviceNet protocol presents two basic types of messages, I/O and explicit. Each one of them is adequate
to a specific kind of data, as described below:
Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [email protected]

I/O: it is a kind of synchronous telegram dedicated to the movement of priority data between one producer
and one or more consumers. They are divided according to the data exchange method. The main types
are:

Polled: it is a communication method where the master sends one telegram to each of the slaves of its
list (scan list). As soon as receiving the request, the slave responds promptly to the request from the
master. This process is repeated until all be consulted, restarting the cycle.

Bit-strobe: it is a communication method where the master sends to the network a telegram containing
8 data bytes. Each bit from those 8 bytes represents a slave that, if addressed, responds according to
the programmed.

Change of State: it is a communication method where the data exchange between master and slave
occurs only when changes in the monitored/controlled values happened, until a certain time limit. When
this limit is reached, the transmission and reception will occur even if there were no changes. The
configuration of this time variable is done in the network configuration program.

Cyclic: it is another communication method very similar to the previous one. The only difference stays in
the production and consume of messages. In this type, every data exchange occurs in regular time
intervals, whether or not they had been changed. This time period is also adjusted in the network
configuration software.
Explicit: it is a kind of general purpose telegram and without priority. It is mainly used for asynchronous
tasks like the parameter settings and the configuration of the equipment.
NOTE!
The CFW500 frequency converter does not provide the bit-strobe communication method.
1.3.6 Set of Predefined Master/Slave Connections
DeviceNet uses fundamentally a point-to-point message model. However, it is quite common to use a
predefined communication model based on the master/slave mechanism.
This model uses a simplified message movement of the I/O type, very common in control applications. An
advantage of this method is that the necessary requests to run it are generally less than for the UCMM. Even
simple devices with limited resources (memory, 8 bit processor) are capable of executing the protocol.
Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [email protected]

2DEVICENET COMMUNICATION ACCESSORY
In order to make the DeviceNet communication possible with the product, it is necessary to use the CAN
communication kit described next. Information on the installation of this module can be obtained in the guide
that comes with the kit.
2.1 PLUG-IN MODULE CFW500-CCAN
WEG part number: 11593087
Composed by the CAN communication module (drawing at the left),
mounting instruction and fixing screw.
The interface is electrically isolated and with differential signal, which
grants more robustness against electromagnetic interference.
External 24V supply.
It allows the connection of up to 64 devices to the same segment. More
devices can be connected by using repeaters4.
A maximum bus length of 1000 meters.
2.2 CONNECTOR PINOUT
The CAN communication module presents a 5-wire plug-in connector with the following pinout:
Table 2.1: CAN interface connector pinout
Pin Name Function
1 V- Power supply negative pole
2 CAN_L CAN_L communication signal
3 Shield Cable shield
4 CAN_H CAN_H communication signal
5 V+ Power supply positive pole
NOTE!
It is recommended to connect the GND pin of the CFW500-CCAN module to protective earth. This is
necessary to connect the cable shield with the earth.
2.3 POWER SUPPLY
The CAN interface needs an external power supply between the pins 1 and 5 of the network connector. The
individual consumption and input voltage data are presented in the next table.
Table 2.2: CAN interface supply characteristics
Supply Voltage (VDC)
Minimum Maximum Recommended
11 30 24
Current (mA)
Typical Maximum
30 50
2.4 INDICATIONS
Details on the alarms, communications failures and communication states are made through the keypad (HMI)
and product parameters.
4The maximum number of devices that can be connected to the network depends also on the used protocol.
Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [email protected]

2.5 MODULE CONFIGURATION
In order to configure the DeviceNet module follow the steps indicated below:
With the frequency converter powered off install the plug-in module CFW500-CCAN.
Make sure it is properly fitted into the connector and secured by the screw.
Power up the inverter.
Verify the content of the parameter P0027 making sure the accessory was correctly recognized. If
necessary, refer to the installation guide.
Set the CAN protocol for DeviceNet by means of the parameter P0700.
Adjust the address of the inverter in the network through the parameter P0701.
Valid values: 0 to 63.
Set the Baud Rate in P0702. Valid values:
0 = Auto
1 = Auto
2 = 500kbps
3 = 250kbps
4 = 125kbps
5 = Auto
6 = Auto
7 = Auto
8 = Auto
At the parameter P0710, configure the most suitable I/O instance for the application (this choice will impact
the number of words exchanged with the network master). The very same number of words must be
adjusted at the network master. Finally, program a value different from 0 in the parameters P0711 to P0718.
Valid values: 0 a 1199.
Cycle the power of the CFW500, so that the changes become effective.
Connect the network cable to the module.
Register the configuration file (EDS file) in the network configuration software.
Add the CFW500 to the scan list of the master.
In the network configuration software, choose a method of data exchange with the master, i.e.,
polled ,
change of state or cyclic . The CFW500 DeviceNet module supports all these I/O data types, besides the
explicit (acyclic data).
If everything is configured correctly the parameter P0719 will indicate the “
Online Connected” state.
Observe also the parameter that indicates the network master status, P0720. There will only be effective
data exchange when the master status is
Run .
2.6 ACCESS TO THE PARAMETERS
After the EDS file registration in the network configuration software, the user will get access to the equipment
complete parameter list, which can be accessed via
explicit messages . This means that it is possible to perform
the drive programming and configuration through the network configuration software.
In order to get application details of this resource, refer to the network master programming documentation
(PLC, PC, etc.).
Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [email protected]

3DEVICENET NETWORK INSTALLATION
The DeviceNet network, such as several industrial communication networks, for being many times applied in
aggressive environments with high exposure to electromagnetic interference, requires that certain precautions
be taken in order to guarantee a low communication error rate during its operation. Recommendations to
perform the connection of the product in this network are presented next.
3.1 BAUD RATE
Equipments with DeviceNet interface generally allow the configuration of the desired baud rate, ranging from
125Kbit/s to 500Kbit/s. The
baud rate that can be used by equipment depends on the length of the cable used
in the installation. The next table shows the baud rates and the maximum cable length that can be used in the
installation, according to the ODVA recommendation5.
Table 3.1: Supported baud rates and installation size
Baud Rate Cable Length
500 Kbit/s 100 m
250 Kbit/s 250 m
125 Kbit/s 500 m
All network equipment must be programmed to use the same communication baud rate. At the CFW500
frequency converter the baud rate configuration is done through the parameter P0702.
3.2 ADDRESS IN THE DEVICENET N ET WORK
Each DeviceNet network device must have an address or MAC ID, and may range from 0 to 63. This address
must be unique for each equipment. For CFW500 frequency converter the address configuration is done
through the parameter P0701.
3.3 TERMINATION RESISTOR
The CAN bus line must be terminated with resistors to avoid line reflection, which can impair the signal and
cause communication errors. The extremes of the CAN bus must have a termination resistor with a 121Ω/
0.25W value, connecting the CAN_H and CAN_L signals.
3.4 CABLE
The connection of CAN_L and CAN_H signals must done with shielded twisted pair cable. The following table
shows the recommended characteristics for the cable.
Table 3.2: DeviceNet cable characteristics
Cable length
(m)
Resistance per
meter (mOhm/m)
Conductor cross
section (mm2)
0 ... 40 70 0.25 ... 0.34
40 ... 300 <60 0.34 ... 0.60
300 ... 600 <40 0.50 ... 0.60
600 ... 1000 <26 0.75 ... 0.80
It is necessary to use a twisted pair cable to provide additional 24Vdc power supply to equipments that need
this signal. It is recommended to use a certified DeviceNet cable.
3.5 CONNECTION IN THE NETWORK
In order to interconnect the several network nodes, it is recommended to connect the equipment directly to the
main line without using derivations. During the cable installation the passage near to power cables must be
avoided, because, due to electromagnetic interference, this makes the occurrence of transmission errors
possible. In order to avoid problems with current circulation caused by difference of potential among ground
connections, it is necessary that all the devices be connected to the same ground point.
5Different products may have different maximum allowed cable length for installation.
Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [email protected]

Figure 3.1: DeviceNet network installation example
To avoid voltage difference problems between the power supplies of the network devices, it is recommended
that the network is fed by only one power supply and the signal is provided to all devices through the cable. If it
is required more than one power supply, these should be referenced to the same point.
The maximum number of devices connected to a single segment of the network is limited to 64. Repeaters can
be used for connecting a bigger number of devices.
Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [email protected]

4PROGRAMMING
Next, only the CFW500 frequency converter parameters related to the DeviceNet communication will be
presented.
4.1 SYMBOLS FOR THE PROPERTIES DESCRIPTION
RO
Read-only parameter
CFG
Parameter that can be changed only with a stopped motor
CAN
Parameter visible on the HMI if the product has the CAN interface installed
P0105 – 1ST/2ND RAMP SELECTION
P0220 – LOCAL/REMOTE SELECTION SOURCE
P0221 – SPEED REFERENCE SELEC TION – LOCAL SITUATION
P0222 – SPEED REFERENCE SELEC TION – REMOTE SITUATION
P0223 – FORWARD/REVERSE SELECTION – L OCAL SITU ATION
P0224 – RUN/STOP SELECTION – L OC AL SITUATION
P0225 – JOG SELECTION – LOCAL SITUATION
P0226 – FORWARD/REVERSE SELECTION – REMOTE SITUATION
P0227 – RUN/STOP SELECTION – REMOTE SITUATION
P0228 – JOG SELECTION – REMOTE SITUATION
These parameters are used in the configuration of the command source for the CFW500 frequency converter
local and remote situations. In order that the device be controlled through the DeviceNet interface, the options
‘CANopen/DeviceNet/Profibus DP’ available in these parameters, must be selected.
The detailed description of these parameters is found in the CFW500 programming manual.
P0313 – COMMUNICATION ERROR ACTION
Range: 0 = Inactive Default: 1
1 = Disable via Run/Stop
2 = Disable via General Enable
3 = Change to Local
4 = Change to Local keeping commands and reference
5 = Causes a Fault
Properties: CFG
Access groups via HMI: NET
Description:
It allows the selection of the action to be executed by the device, if it is controlled via network and a
communication error is detected.
Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [email protected]

Table 4.1: P0313 options
Options
Description
0 = Inactive
No action is taken and the drive remains in the existing status.
1 = Disable via Run/Stop
A stop command with deceleration ramp is executed and the
motor stops according to the programmed deceleration ramp.
2 = Disable via General Enable
The drive is disabled by removing the General Enabling and the
motor coasts to stop.
3 = Change to Local
The drive commands change to Local.
4 = Change to Local keeping
commands and reference
The drive commands change to Local, but the status of the
enabling and speed reference commands received via network
are kept, providing that the drive has been programmed to use in
Local mode the commands via HMI, or 3-wire start/stop and
speed reference via either HMI or electronic potentiometer.
5 = Causes a Fault
Instead of an alarm, the communication error causes an drive
fault, so that a drive fault reset becomes necessary in order to
restore normal operation.
The following events are considered communication errors:
CANopen/DeviceNet communication:
A133 alarm/F233 fault: CAN interface not powered.
A134 alarm/F234 fault:
bus off .
A135 alarm/F235 fault: CANopen communication error (
Node Guarding/Heartbeat ).
A136 alarm/F236 fault: DeviceNet master in
Idle mode.
A137 alarm/F237 fault: Detected timeout in one or more DeviceNet I/O connections.
The actions described in this parameter are executed by means of the automatic writing of the selected actions
in the respective bits of the interface control words. Therefore, in order that the commands written in this
parameter be effective, it is necessary that the device be programmed to be controlled via the used network
interface (with exception of option “Causes a Fault”, which blocks the equipment even if it is not controlled by
network). This programming is achieved by means of parameters P0220 to P0228.
P0680 – STATUS WORD
Range: 0000h to FFFFh Default: -
Properties: RO
Access groups via HMI: NET
Description:
It allows the device status monitoring. Each bit represents a specific status:
Bits
15
14
13
12
11
10
9
8
7
6
5
4
3 to 0
Function
Fault condition
(PID) Automatic
Undervoltage
LOC/REM
JOG
Speed direction
Active General
Enable
Motor Running
Alarm condition
In configuration
mode
Second ramp
Active fast stop
Reserved
Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [email protected]

Table 4.2: P0680 parameter bit functions
Bits
Values
Bits 0 to 3
Reserved.
Bit 4
Active quick stop
0: The fast stop command is not active.
1: The drive is executing the fast stop command.
Bit 5
Second ramp
0: The driveis configured to use the first ramp values, programmed in P0100 and P0101, as the motor
acceleration and deceleration ramp times.
1: The drive is configured to use the second ramp values, programmed in P0102 and P0103, as the motor
acceleration and deceleration ramp times.
Bit 6
In configuration mode
0: The drive is operating normally.
1: The drive is in the configuration mode. It indicates a special condition during which the drive cannot be
enabled:
Executing the self-tuning routine
Executing the oriented start-up routine
Executing the HMI copy function
Executing the flash memory card self-guided routine
There is a parameter setting incompatibility
There is no power at the drive power section
Bit 7
Alarm condition
0: The drive is not in alarm condition.
1: The drive is in alarm condition.
Note: The alarm number can be read by means of the parameter P0048 – Present Alarm.
Bit 8
Motor Running
0: The motor is stopped.
1: The drive is running the motor at the set point speed, or executing either the acceleration or the
deceleration ramp.
Bit 9
Active General Enable
0: General Enable is not active.
1: General Enable is active and the drive is ready to run the motor.
Bit 10
Speed direction
0: The motor is running in the reverse direction.
1: The motor is running in the forward direction.
Bit 11
JOG
0: Inactive JOG function.
1: Active JOG function.
Bit 12
LOC/REM
0: Drive in Local mode.
1: Drive in Remote mode.
Bit 13
Undervoltage
0: No Undervoltage.
1: With Undervoltage.
Bit 14
Manual/ Automatic
0: PID in manual mode.
1: PID in Automatic mode.
Bit 15
Fault condition
0: The drive is not in a fault condition.
1: The drive has detected a fault.
Note: The fault number can be read by means of the parameter P0049 – Present Fault.
P0681 – MOTOR SPEED IN 13 BITS
Range: - 32768 to 32767 Default: -
Properties: RO
Access groups via HMI: NET
Description:
It allows monitoring the motor speed. This word uses 13-bit resolution with signal to represent the motor rated
frequency (P0403):
P0681 = 0000h (0 decimal) →motor speed = 0
P0681 = 2000h (8192 decimal) →motor speed = rated frequency
Intermediate or higher speed values in rpm can be obtained by using this scale. E.g.60Hz rated frequency if the
value read is 2048 (0800h), then, to obtain the speed in Hz one must calculate:
8192 => 60 Hz
2048 => Frequency in Hz
Frequency in Hz = 60 ×2048
8192
Frequency in Hz = 30 Hz
Negative values in this parameter indicate that the motor is running in the reverse direction.
Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [email protected]

NOTE!
The values transmitted over the network have a scale limitation, allowing a maximum of 4 times the
synchronous speed of the motor, with saturation in 32767 (or -32768).
P0684 – DEVICENET CONTROL WORD
Range: 0000h a FFFFh Default: 0000h
Properties:NET
Access groups via HMI: NET
Description:
It is the device DeviceNet interface control word. This parameter can only be changed via
CANopen/DeviceNet/Profibus DP interface. For the other sources (HMI, etc.) it behaves like a read-only
parameter.
In order to have those commands executed, it is necessary to program the equipment to be controlled via
CANopen/DeviceNet/Profibus DP. This programming is achieved by means of parameters P0105 and P0220 to
P0228.
Each bit of this word represents a command that can be executed.
Bits 15 to 8 7 6 5 4 3 2 1 0
Function
Reserved
Fault reset
Quick stop
Second ramp
LOC/REM
JOG
Speed direction
General enable
Run/Stop
Table 4.3: P0684 parameter bit functions
Bits Values
Bit 0
Run/Stop
0: It stops the motor with deceleration ramp.
1: The motor runs according to the acceleration ramp until reaching the speed reference value.
Bit 1
General enable
0: It disables the drive, interrupting the supply for the motor.
1: It enables the drive allowing the motor operation.
Bit 2
Speed direction
0: To run the motor in a direction opposed to the speed reference.
1: To run the motor in the direction indicated by the speed reference.
Bit 3
JOG
0: It disables the JOG function.
1: It enables the JOG function.
Bit 4
LOC/REM
0: The drive goes to the Local mode.
1: The drive goes to the Remote mode.
Bit 5
Second ramp
0: The drive uses the first ramp values, programmed in P0100 and P0101, as the motor acceleration
and deceleration ramp times.
1: The drive is configured to use the second ramp values, programmed in P0102 and P0103, as the
motor acceleration and deceleration ramp times.
Bit 6
Quick stop
0: It does not execute the quick stop command.
1: It executes the quick stop command.
Note: This function is not allowed with control types (P0202) V/f or VVW.
Bit 7
Fault reset
0: No function.
1: If in a fault condition, then it executes the reset.
Bits 8 to 15 Reserved.
P0685 – DEVICENET SPEED REFERENCE
Range: -32768 to 32767 Default: 0
Properties:NET
Access groups via HMI: NET
Description:
It allows programming the motor speed reference via the DeviceNet interface. This parameter can only be
changed via CANopen/DeviceNet/Profibus DP interface. For the other sources (HMI, etc.) it behaves like a read-
only parameter.
Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [email protected]

In order that the reference written in this parameter be used, it is necessary that the drive be programmed to
use the speed reference via CANopen/DeviceNet/Profibus DP. This programming is achieved by means of
parameters P0221 and P0222.
This word uses a 13-bit resolution with signal to represent the motor rated frequency (P0403).
P0685 = 0000h (0 decimal) →speed reference = 0
P0685 = 2000h (8192 decimal) →speed reference = rated frequency (P0403)
Intermediate or higher reference values can be programmed by using this scale. E.g.60Hz rated frequency, to
obtain a speed reference of 30 Hz one must calculate:
60 Hz => 8192
30 Hz => 13 bit reference
13 bit reference = 30
×
8192
60
13 bit reference = 4096
This parameter also accepts negative values to revert the motor speed direction. The reference speed direction,
however, depends also on the control word - P0684 - bit 2 setting:
Bit 2 = 1 and P0685 > 0: reference for forward direction
Bit 2 = 1 and P0685 < 0: reference for reverse direction
Bit 2 = 0 and P0685 > 0: reference for reverse direction
Bit 2 = 0 and P0685 < 0: reference for forward direction
NOTE!
The values
transmitted over the network have a scale limitation, allowing to program a speed
reference of 4 times the synchronous speed of the motor at most.
P0695 – DIGITAL OUTPUT SETTING
Range 0000h to 001Fh Default:0000h
Properties: NET
Access groups via HMI: NET
Description:
It allows the control of the digital outputs by means of the network interfaces (Serial, CAN, etc.). This parameter
cannot be changed via HMI.
Each bit of this parameter corresponds to the desired value for one digital output. In order to have the
correspondent digital output controlled according to this content, it is necessary that its function be
programmed for “P0695 Content” at parameters P0275 to P0279.
Bits
15 to 5
4
3
2
1
0
Function
Reserved
DO5 setting DO4 setting DO3 setting DO2 setting DO1 setting
=> Value corresponding to 30 Hz in a 13 bit scale
Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [email protected]

Table 4.4: P0695 parameter bit functions
Bits
Values
Bit 0
DO1 setting
0: DO1 output open.
1: DO1 output closed.
Bit 1
DO2 setting
0: DO2 output open.
1: DO2 output closed.
Bit 2
DO3 setting
0: DO3 output open.
1: DO3 output closed.
Bit 3
DO4 setting
0: DO4 output open.
1: DO4 output closed.
Bit 4
DO5 setting
0: DO5 output open.
1: DO5 output closed.
Bits 5 to 15
Reserved
NOTE!
Some of the digital outputs may not be available depending on the plug-in module.
P0696 – VALUE 1 FOR ANALOG OUTPUTS
P0697 – VALUE 2 FOR ANALOG OUTPUTS
P0698 – VALUE 3 FOR ANALOG OUTPUTS
Range: -32768 to 32767 Default: 0
Properties: NET
Access groups via HMI: NET
Description:
They allow the control of the analog outputs by means of network interfaces (Serial, CAN, etc.) These
parameters cannot be changed via HMI.
The value written in these parameters is used as the analog output value, providing that the function for the
desired analog output be programmed for “P0696 / P0697 / P0698 value”, at the parameters P0251, P0254,
P0257.
The value must be written in a 15-bit scale (7FFFh = 32767)
6
to represent 100 % of the output desired
value, i.e.:
P0696 = 0000h (0 decimal) →analog output value = 0 %
P0696 = 7FFFh (32767 decimal) →analog output value = 100 %
The showed example was for P0696, but the same scale is also used for the parameters P0697 / P0698. For
instance, to control the analog output 1 via serial, the following programming must be done:
Choose a parameter from P0696, P0697, P0698 to be the value used by the analog output 1. For this
example, we are going to select P0696.
Program the option “P0696 value” as the function for the analog output 1 in P0254.
Using the network interface, write in P0696 the desired value for the analog output 1, between 0 and 100%,
according to the parameter scale.
NOTE!
For CFW500 frequency converter, the analog output 3 represents the frequency output (FO).
6
For the actual output resolution, refer to the product manual.
Phone: [phone] - Fax: [phone] - Web: www.clrwtr.com - Email: [email protected]