WEG DeviceNet CFW500 User Manual

WEG DeviceNet CFW500 User Manual

Variable frequency drives
Table of Contents

Advertisement

DeviceNet
CFW500
User's Manual
Phone: 800.894.0412 - Fax: 888.723.4773 - Web: www.clrwtr.com - Email: info@clrwtr.com

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the DeviceNet CFW500 and is the answer not in the manual?

Questions and answers

Summary of Contents for WEG DeviceNet CFW500

  • Page 1 DeviceNet CFW500 User’s Manual Phone: 800.894.0412 - Fax: 888.723.4773 - Web: www.clrwtr.com - Email: info@clrwtr.com...
  • Page 2 DeviceNet User’s Manual Series: CFW500 Language: English Document Number: 10002253313 / 00 Publication Date: 05/2013 Phone: 800.894.0412 - Fax: 888.723.4773 - Web: www.clrwtr.com - Email: info@clrwtr.com...
  • Page 3: Table Of Contents

    CONTENTS CONTENTS ..........................3 ABOUT THIS MANUAL......................5 ABBREVIATIONS AND DEFINITIONS ................... 5 NUMERICAL REPRESENTATION ....................5 DOCUMENTS ..........................5 INTRODUCTION TO THE DEVICENET COMMUNICATION......... 6 CAN..........................6 1.1.1 Data Frame ........................ 6 1.1.2 Remote Frame ......................6 1.1.3 Access to the Network ....................6 1.1.4 Error Control......................
  • Page 4 P0681 – MOTOR SPEED IN 13 BITS ................... 17 P0684 – DEVICENET CONTROL WORD..................18 P0685 – DEVICENET SPEED REFERENCE ................. 18 P0695 – DIGITAL OUTPUT SETTING ..................19 P0696 – VALUE 1 FOR ANALOG OUTPUTS ................20 P0697 – VALUE 2 FOR ANALOG OUTPUTS ................20 P0698 –...
  • Page 5: About This Manual

    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 Controller Area Network CAN in Automation Common Industrial Protocol...
  • Page 6: Introduction To The Devicenet Communication

    1 INTRODUCTION 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.
  • Page 7: Can And Devicenet

    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.
  • Page 8: Data Link Layer

    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.
  • Page 9: Application Layer - Cip Protocol

    1.3.3 Application Layer – CIP Protocol Common Industrial Protocol In the application layer, DeviceNet uses the (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 medi u m and from the data link layer.
  • Page 10: Set Of Predefined Master/Slave Connections

    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 ...
  • Page 11: Devicenet Communication Accessory

    Information on the installation of this module can be obtained in the guide that comes with the kit. PLUG-IN MODULE CFW500-CCAN WEG part number: 11593087  Composed by the CAN communication module (drawing at the left), ...
  • Page 12: Module Configuration

    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. ...
  • Page 13: Devicenet Network Installation

    3 DEVICENET 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.
  • Page 14 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.
  • Page 15: Programming

    4 PROGRAMMING Next, only the CFW500 frequency converter parameters related to the DeviceNet communication will be presented. SYMBOLS FOR THE PROPERTIES DESCRIPTION Read-only parameter Parameter that can be changed only with a stopped motor Parameter visible on the HMI if the product has the CAN interface installed P0105 –...
  • Page 16: P0680 - Status Word

    Table 4.1: P0313 options Options Description 0 = Inactive No action is taken and the drive remains in the existing status. A stop command with deceleration ramp is executed and the 1 = Disable via Run/Stop motor stops according to the programmed deceleration ramp. The drive is disabled by removing the General Enabling and the 2 = Disable via General Enable motor coasts to stop.
  • Page 17: P0681 - Motor Speed In 13 Bits

    Table 4.2: P0680 parameter bit functions Bits Values Bits 0 to 3 Reserved. Bit 4 0: The fast stop command is not active. Active quick stop 1: The drive is executing the fast stop command. Bit 5 0: The drive is configured to use the first ramp values, programmed in P0100 and P0101, as the motor Second ramp acceleration and deceleration ramp times.
  • Page 18: P0684 - Devicenet Control Word

    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: Access groups via HMI: Description:...
  • Page 19: P0695 - Digital Output Setting

    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). →...
  • Page 20: P0696 - Value 1 For Analog Outputs

    Table 4.4: P0695 parameter bit functions Bits Values Bit 0 0: DO1 output open. DO1 setting 1: DO1 output closed. Bit 1 0: DO2 output open. DO2 setting 1: DO2 output closed. Bit 2 0: DO3 output open. DO3 setting 1: DO3 output closed.
  • Page 21: P0700 - Can Protocol

    P0700 – CAN PROTOCOL Range: Default: 2 1 = CANopen 2 = DeviceNet Properties: Access groups via HMI: Description: It allows selecting the desired protocol for the CAN interface. If this parameter is changed, the change takes effect only if the CAN interface is not powered, it is in auto-baud or after the equipment is switched off and on again.
  • Page 22: P0703 - Bus Off Reset

    P0703 – BUS OFF RESET Range: 0 = Manual Default: 0 1 = Automatic Properties: Access groups via HMI: Description: It allows programming the inverter behavior when detecting a bus off error at the CAN interface: Table 4.5: Options for the parameter P0703 Option Description bus off...
  • Page 23: P0706 - Received Can Telegram Counter

    P0706 – RECEIVED CAN TELEGRAM COUNTER Range: Default: - 0 to 65535 Properties: Access groups via HMI: Description: This parameter works as a cyclic counter that is incremented every time a CAN telegram is received. It informs the operator if the device is being able to communicate with the network. This counter is reset every time the device is switched off, a reset is performed or the parameter maximum limit is reached.
  • Page 24: P0710 - Devicenet I/O Instances

    P0710 – DEVICENET I/O INSTANCES Range: Default: 0 0 = ODVA Basic Speed (2 words) 1 = ODVA Extended Speed (2 words) 2 = Manuf.Spec. 2W (2 words) 3 = Manuf.Spec. 3W (3 words) 4 = Manuf.Spec. 4W (4 words) 5 = Manuf.Spec.
  • Page 25 Monitoring (Input) Instance Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 Drive State Speed Actual (low byte) Speed Actual (high byte) Control (Output) Instance Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2...
  • Page 26 Control: Bits (Byte 0) Values Bit 0 0: It stops the motor. Run Fwd 1: It runs the motor clockwise. Bit 1 0: It stops the motor. Run Rev 1: It runs the motor counterclockwise. Bit 2 0: No function. Fault Reset 1: If in a fault condition, then it executes the inverter reset.
  • Page 27: P0711 - Devicenet Reading #3

    P0711 – DEVICENET READING #3 P0712 – DEVICENET READING #4 P0713 – DEVICENET READING #5 P0714 – DEVICENET READING #6 Range: Default: 0 (disabled) 0 to 1199 Properties: CFG, CAN Access groups via HMI: Description: These parameters allow the user to program the content of input words 3 to 6 (input: slave sends to the master).
  • Page 28: P0719 - Devicenet Network Status

    NOTE! The 0 (zero) value disables the word writing. The amount of output words, however, always remains the same as it was programmed in parameter P0710. P0719 – DEVICENET NETWORK STATUS Range: 0 = Offline Default: - 1 = Online, Not Connected 2 = Online, Connected 3 = Timed-out Connection 4 = Connection Failure...
  • Page 29: Supported Object Classes

    5 SUPPORTED OBJECT CLASSES Any DeviceNet equipment is modeled as a set of objects. The objects are responsible for defining the function that each device will have. In other words, depending on the objects the device implements, it may be a communication adapter, an AC/DC drive, a photoelectric sensor, etc.
  • Page 30: Connection Class (05H)

    Table 5.5: Instances of the Assembly class Instances Size Description 2 words ODVA Basic Speed Control Output 2 words ODVA Basic Speed Control Input 2 words ODVA Extended Speed Control Output 2 words ODVA Extended Speed Control Input 2 – 6 words Manufacturer Specific Output 2 –...
  • Page 31: Instance 4: Change Of State/Cyclic

    5.5.3 Instance 4: Change of State/Cyclic Table 5.8: Connection class – Instance 4: Change of State/Cyclic Attribute Method Name Description State Object state Instance Type I/O or explicit Transport Class Trigger Defines the connection behavior Produced Connection ID CAN ID field for transmission Consumed Connection ID CAN ID field value representing received msg Initial Comm.
  • Page 32: Ac/Dc Drive Class (2Ah)

    Table 5.12: Control Supervisor Class instance attributes Attribute Method Name Min./Max Default Description Get/Set Run1 Run Fwd Get/Set Run2 Run Rev Get/Set NetCtrl 0 = Local control 1 = Remote control State 0 = Vendor specific 1 = Startup 2 = Not Ready 3 = Ready 4 = Enabled 5 = Stopping...
  • Page 33: 5.10 Manufacturer Specific Classes

    5.10 MANUFACTURER SPECIFIC CLASSES The Manufacturer Specific Classes are used for mapping all CFW500 parameters. These classes allow the user to read from and write to any parameter through the network. The Manufacturer Specific Classes use DeviceNet explicit messages. There are separate ranges for each group of parameters, as presented in Table 5.16: Table 5.16: Manufacturer Specific Classes Class Name...
  • Page 34: Faults And Alarms Related To The Devicenet Communication

    6 FAULTS AND ALARMS RELATED TO THE DEVICENET COMMUNICATION A133/F233 – CAN INTERFACE WITHOUT POWER SUPPLY Description: It indicates that the CAN interface does not have power supply between the pins 1 and 5 of the connector. Actuation: In order that it be possible to send and receive telegrams through the CAN interface, it is necessary to supply external power to the interface circuit.
  • Page 35: A137/F237 - Devicenet Connection Timeout

    In this case the alarm A136 – or the fault F236, depending on the P0313 programming, will be signalized through the HMI. In case of alarms, If the master is set in the mode again (normal equipment operation status), the alarm indication will be removed from the HMI. Possible Causes/Correction: Adjust the switch that commands the master operation mode for execution ( ) or set the correspondent...

Table of Contents

Save PDF