Phoenix DX Series Instruction Manual

3 to 3500 hp; modbus rtu protocol; modbus tcp protocol; modbus usd protocol

Advertisement

Quick Links

PHOENIX AC DRIVE
DX, EX, DS & ES
3 TO 3500 HP
MODBUS RTU PROTOCOL
MODBUS TCP PROTOCOL
MODBUS USD PROTOCOL

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the DX Series and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Summary of Contents for Phoenix DX Series

  • Page 1 PHOENIX AC DRIVE DX, EX, DS & ES 3 TO 3500 HP MODBUS RTU PROTOCOL MODBUS TCP PROTOCOL MODBUS USD PROTOCOL...
  • Page 2: Table Of Contents

    Modbus TCP Header Description Ethernet TCP Message Framing ETHERNET FRAME MODBUS FUNCTION FORMATS Ethernet Frame Encapsulation Field Contents in Modbus Messages Function Codes PHOENIX AC DRIVE FUNCTION FORMATS MODBUS USD Function Formats MODBUS RTU Function Formats MODBUS USD Alternate Function Format 6-4...
  • Page 3 LIST OF FIGURES AND TABLES FIGURE TITLE PAGE RS-485 4-Wire Multi Drop Hookup RS-422 4-Wire Point-to-Point Hookup Quasi – RS 232 Hookup Installation of Isolated RS-422/485 Board 2-4 Installation of Removable RS-232 Isolated Communication Interface with Cable Installation of Isolated RS-422/485 Board 2-6 Installation of Removable USB-RS-485 Isolated Communications Interface Ethernet Frame...
  • Page 4: Introduction

    INTRODUCTION 1.0 INTRODUCTION The US DRIVES PHOENIX digital AC drive has an optional isolated serial communication interface that enables the user to control and setup the drive using a host computer, such as an IBM compatible PC. The drive’s serial interface may be configured to support either the RS-422 or RS-485 interconnect standard.
  • Page 5 INTRODUCTION END OF INTRODUCTION SECTION...
  • Page 6: Hardware Interface

    This direct connection generates RS-232C levels of proper hookup for 4-Wire RS-485 Multi-Drop between approximately +3.7 volts to -3.7 volts. Note that the a host PC and a number of PHOENIX drives is shown isolated RS-422/485 common on the PHOENIX control in Figure 2-1.
  • Page 7: Rs-232 Isolated Communications

    Interface, user’s can use the PC’s RS-232C serial port. The Communication Interface isolates the PC from the Phoenix AC Drive and no external power supply is needed. This comes with D9 female connector, 10’ cable, and removable RS-232 Isolated Communication interface.
  • Page 8 HARDWARE INTERFACE Figure 2.3 Figure 2.2 Figure 2.1...
  • Page 9 HARDWARE INTERFACE Isolated Communication Card 3000-4135-1 Installation of Isolated RS-422/485 Board (with Control Board 3000-4100 & 3000-4130) Figure 2.4...
  • Page 10 HARDWARE INTERFACE Removable USB/RS-485 Isolated Communications Interface with Cable P/N: 3000-4226-USB Installation of Removable USB-RS-485 Isolated Communications Interface with Cable P/N: 3000-4226-USB (with Control Board 3000-4100 & 3000-4130) Figure 2.5...
  • Page 11 HARDWARE INTERFACE Isolated Communication Card 3000-4135 Installation of Isolated RS-422/485 Board (with Control Board 3000-4101 & 3000-4131) Figure 2.6...
  • Page 12 HARDWARE INTERFACE Removable USB/RS-485 Isolated Communications Interface with Cable P/N: 3000-4226-USB Installation of Removable USB/RS-485 Isolated Communications Interface with Cable P/N: 3000-4226-USB (with Control Board 3000-4101 & 3000-4131) Figure 2.7...
  • Page 13 HARDWARE INTERFACE ND OF ARDWARE NTERFACE...
  • Page 14: Modbus Rtu Protocol Description

    ASCII or RTU. Phoenix AC drives use RTU mode, but select the serial port communication parameters (baud rate, parity mode, etc.), during configuration of each drive. The mode and serial parameters must be the same for all devices on a Modbus network.
  • Page 15: Rtu Mode

    3.2.1 RTU Mode Error Check Field Longitudinal Redundancy Check (LRC) The Phoenix AC drive are setup to communicate on a Modbus network using RTU (Remote Terminal Unit) mode, each eight-bit byte in a message contains two 3.3 Modbus Message Framing four-bit hexadecimal characters.
  • Page 16: Ascii Framing

    In ASCII mode, which is not incorporated in Phoenix recording, or verifying the program within the slave. AC drives, messages start with a colon (: character...
  • Page 17: Contents Of The Error Checking Field

    3.3.6 Contents of the Error Checking 3.4.1 Parity Checking Field Users can configure Phoenix AC drives for Even or Odd Parity checking, or for No Parity checking. This will RTU Mode determine how the parity bit will be set in each character.
  • Page 18: Crc Checking

    MODBUS RTV PROTOCAL DESCRIPTION 3- 5 If No Parity checking is specified, no parity bit is transmitted and no parity check can be made. additional stop bit is transmitted to fill out the character frame. 3.4.2 CRC Checking In RTU mode, messages include an error-check field that is based on a CRC method.
  • Page 19 MODBUS RTV PROTOCAL DESCRIPTION END OF MODBUS RTU PROTOCAL DESCRIPTION...
  • Page 20: Modbus Tcp Protocol

    MODBUS TCP PROTOCOL DESCRIPTION 4.0 MODBUS TCP PROTOCAL The Modbus RTU frame request and responses as Modbus TCP message framing is inserted into DESCRIPTION application data location. The Modbus RTU message This section describes general form frame start, stop, and cRC are not included into the encapsulation of Modbus request and response when Modbus TCP frame.
  • Page 21: Ethernet Tcp Message Framing

    MODBUS TCP PROTOCOL DESCRIPTION 4.4 Ethernet TCP Message Framing The Modbus RTU frame request and response as Ethernet TCP message frame is inserted into the application data location. The Modbus RTU message frame start and stop is not included into the Ethernet TCP frame.
  • Page 22: Modbus Function Formats

    MODBUS FUNCTION FORMATS 5.2 Function Codes 5.0 MODBUS FUNCTION FORMATS The listing below shows some function codes 5.1 Field Contents in Modbus Messages supported by Modicon controllers. The following tables show examples of a Modbus Code Name query and normal response. Both examples show the Read Coil Status field contents in hexadecimal, and also show how a Read Input Status...
  • Page 23 MODBUS FUNCTION FORMATS END OF MODBUS FUNCTION FORMATS...
  • Page 24: Phoenix Ac Drive Function Formats

    CRC Hi CRC Hi describes the specified parameter value on the Phoenix drive. This is for only parameters that have The example above is reading drive 1 parameter names for values. The value name can be 9 or 16 M05P09 BASE MOTOR FREQ. The response is 60.0 characters.
  • Page 25 Function Code 04 – Read Parameter Name Force Data Lo Character Value CRC Lo CRC Lo This function reads the parameter name that describes CRC Hi CRC Hi the specified parameter on the Phoenix drive. Response Broadcast is not supported. Query Modbus Phoenix Format Format...
  • Page 26: Modbus Rtu Function Formats

    CRC Hi CRC Hi Function Code 03 – Read Parameter Value Response This function reads the data value the specified parameters on the Phoenix drive. Up to a maximum of Modbus Phoenix sixteen parameter values can be returned in the Format...
  • Page 27 PHOENIX AC DRIVE FUNCTION FORMATS Query Function Code 16 – Write Parameter Value This function writes the data value to the specified Modbus Phoenix Format Format Example parameter of the Phoenix Drive. Broadcast is Slave Address Drive Address supported. Function Code...
  • Page 28: Modbus Usd Alternate Function Format

    Read Parameter Name Write Parameter Name Write Parameter Value Function Code 67 - Read Parameter Value This function reads the data value and decimal point position of the specified parameter on the Phoenix drive. Broadcast is not supported. Query Phoenix Format...
  • Page 29 PHOENIX AC DRIVE FUNCTION FORMATS END OF PHOENIX AC DRIVE FUNCTION FORMATS...
  • Page 30 80 hexadecimal higher than the value would MEMORY PARITY ERROR be for a normal response. The Phoenix AC drive exception response uses some With the function code’s MSB set, the master’s of the existing Modbus exception codes and also has application program can recognize the exception three new exception codes.
  • Page 31: Exception Response

    EXCEPTION RESPONSE END OF EXCEPTION RESPONSE...
  • Page 32: Crc Generation

    CRC GENERATION 8.0 CRC GENERATION Step 5 Repeat Steps 3 and 4 until eight shifts have been performed. When this is done, a complete eight- The Cyclical Redundancy Check (CRC) field is two bit byte will have been processed. bytes, containing a 16-bit binary value. The CRC value is calculated by the transmitting device, which Step 6 Repeat Steps 2…5 for the next eight-bit byte...
  • Page 33 CRC GENERATION The function takes two arguments: unsigned char puchMsg; /* A pointer to the message buffer */ unsigned short usDataLen; /* The quantity of bytes in the message buffer */ The function returns the CRC as a type unsigned short. CRC Generation Function unsigned short CRC16 (puchMsg, usDataLen) unsigned char *puchMsg;...
  • Page 34 CRC GENERATION High Order Byte Table /* Table of CRC values for high-order byte */ static unsigned char auchCRCHi [ ] = 0x00, 0xC1, 0x81, 0x40, 0x01, 0xC0, 0x80, 0x41, 0x01, 0xC0, 0x80, 0x41, 0x00, 0xC1, 0x81, 0x40, 0x01, 0xC0, 0x80, 0x41, 0x00,...
  • Page 35 CRC GENERATION Low Order Byte Table /* Table of CRC values for low-order byte */ static unsigned char auchCRCLo [ ] = 0x00, 0xC0, 0xC1, 0x01, 0xC3, 0x03, 0x02, oxC2, 0xC6, 0x06, 0x07, 0xC7, 0x05, 0xC5, 0xC4, 0x04, 0xCC, 0x0C, 0x0D, 0xCD, 0x0F, 0xCF,...
  • Page 36: Parameter Conversion

    Register Address Hi Menu Number Register Address Lo Parameter Number 9.2 Parameter to Register Address Conversion The US Drives Phoenix two digit Menu number and Parameter number sometimes needs converted to a register address in third party software programs. The conversion formula is:...
  • Page 37 PARAMETER CONVERSION END OF PARAMETER CONVERSION...
  • Page 38: Introduction

    APPENDIX / BASIC TCP/IP DESCRIPTION Each layer has a different responsibility. 1.0 INTRODUCTION 1. The link layer, sometimes called the data-link 1.1 Introduction layer or network interface layer, normally includes the device driver in the operating system and the corresponding network Connectivity is required either too exchange billing interface cad in the computer.
  • Page 39: Network Layer

    APPENDIX / BASIC TCP/IP DESCRIPTION an Ethernet, both running FTP, Figure etc) while the latter handles one specific user 1.2 shows the protocols involved. application (FTP, Telnet, etc.). handles FTP protocol user application This figure shows some layers and protocols in the processes details application...
  • Page 40: Ip Address Classes

    APPENDIX / BASIC TCP/IP DESCRIPTION the Internet Protocol Address, the IP Address or the bits are divided into a subnet ID and a host ID. This Internet Address. These terns are interchangeable. makes sense for class A and B networks, since no Each packet sent across the internet contains the IP one attaches as many hosts to these networks as is address of the source of the packet and the IP...
  • Page 41: The Transport Layer

    APPENDIX / BASIC TCP/IP DESCRIPTION hardware does understand software- specific and unique place in the “domain name maintained IP addresses. IP uses ARP to translate the space.” DNS makes it possible for us to use 32-bit IP address to a physical address that matches identifiers such as zworld.com to refer to an IP the addressing scheme of the underlying hardware address on the Internet.
  • Page 42 APPENDIX / BASIC TCP/IP DESCRIPTION The network interface sends and receives frames on The numbers at the bottom of the headers and trailer behalf of IP, ARP, and RARP. There must be some of the Ethernet frame in Figure 4.2 are the typical form of identification in the Ethernet header sizes of the headers in bytes.
  • Page 43 APPENDIX / BASIC TCP/IP DESCRIPTION THIS PAGE INTENTIONALLY LEFT BLANK...
  • Page 44 "THE HIGH HORSEPOWER DESIGN EXPERTS" Products Designed And Manufactured In The United States Of America US Drives Inc. 2221 Niagara Falls Boulevard P.O. Box 281 Niagara Falls, NY 14304-0281 Tel: (716) 731-1606 Fax: (716) 731-1524 Visit us at www.usdrivesinc.com MODP0917 Printed in U.S.A. Data Subject to Change Without Notice...

This manual is also suitable for:

Ex seriesEs seriesDs series

Table of Contents