Page 2: Preface
Preface About This Guide The MD520 series AC drive is a general‑purpose high‑performance current vector control AC drive. It is designed to control and regulate the speed and torque of three‑ phase AC asynchronous motors. The AC drive can be used to drive textile machines, paper machines, wire drawing machines, machine tools, packaging machines, food machines, fans, water pumps, and other automated production equipment.
Page 3 This document is not delivered with the product. You can obtain the PDF version of this document by the following method: www.inovance.com Log in to Inovance's website ( ), choose Support > Download, perform keyword search, and download the PDF file.
Page 4: Table Of Contents
Table of Contents T T a a b b l l e e o o f f C C o o n n t t e e n n t t s s Preface ................1 Safety Precautions .
Page 5 Table of Contents 5.5 Data Transmission Formats ..........79 5.6 PZD Data .
Page 6 9.7.1 Using an MD500‑EN1 Expansion Card on an Allen‑Bradley L16ER Master ..241 9.7.2 Using an MD500‑EN1 Expansion Card on an Inovance AM600 Master ..253 9.8 Fault Diagnosis.
Page 7: Safety Precautions
Malfunction or component damage caused by improper usage is not covered by warranty. 4. Inovance shall take no responsibility for any personal injuries or property loss caused by noncompliance with this guide or improper use of this product. Safety Levels and Definitions indicates that failure to comply with the notice will result in severe personal injuries or even death.
Page 8 Safety Precautions Before unpacking, check whether the packing is intact without damage, water seepage, ● damp, and deformation. Unpack the package in sequence. Do not hit the package with force. ● Check the surface of the equipment and accessories for any damage or rust. ●...
Page 9 Safety Precautions Read through the user guide and safety precautions before installation. ● Do not install this product in places subject to strong electric field or strong ● electromagnetic wave interference. Before installation, make sure that the installation position is mechanically strong ●...
Page 10 Safety Precautions Never connect the power cable to an output terminal. Failure to comply may result in ● product damage or even fire. When connecting a drive with the motor, ensure that the phase sequences of the drive ● and motor are consistent to prevent motor reverse rotation. Ensure that the diameter and shielding of the cables used meet corresponding ●...
Page 11 Safety Precautions Never touch the product shell, fan, or resistor to check the temperature. Failure to ● comply may result in burn. Prevent metal or other objects from falling into the product during operation. Failure to ● comply may result in product damage or fire. Maintenance Do not allow non‑professionals to perform equipment installation, wiring, maintenance, ●...
Page 12 Safety Precautions Disposal Scrap the equipment or product in accordance with relevant national regulations and ● standards. Failure to comply may result in property damage, personal injury, or even death. Recycle retired equipment by observing industry waste disposal standards to avoid ●...
Page 13: Parameter Communication Addresses
Parameter Communication Addresses Parameter Communication Addresses Parameter Data The parameters involve basic function parameters and monitoring parameters, which are stored in the corresponding parameter group. Basic function parameters are stored in groups F, A, B, C, and H, as listed in the following table. F0, F1, F2, F3, F4, F5, F6, F7, F8, F9, FA, FB, FC, FD, FE, Parameter data Group F (read/...
Page 14: Modbus-Specific Parameter Communication Addresses
Parameter Communication Addresses Writing basic function parameters and saving them upon power failure indicate frequent operations on the EEPROM, which reduces its service life. Therefore, you can modify some basic function parameters in the RAM through communication without storing them. For parameters in group F, you can change F in higher bits of the parameter address into 0 to obtain the corresponding RAM address.
Page 15 Parameter Communication Addresses Parameter Address Parameter Description Parameter Address Parameter Description 1002H Bus voltage 1012H PLC process 1003H Output voltage 1013H Pulse input frequency (unit: 0.01 kHz) 1004H Output current 1014H Feedback speed (unit: 0.1 Hz) 1005H Output power 1015H Remaining running duration 1006H Output torque...
Page 16 Parameter Communication Addresses Table 1–2 Description of Modbus‑specific parameter addresses Parameter Address Parameter Description Frequency reference 1 set through 1000H Communication reference (decimal) communication –10000 to +10000 The communication reference is a relative value (percentage). 10000 corresponds to 100.00%, and –10000 corresponds to –100.00%.
Page 17 Parameter Communication Addresses Parameter Address Parameter Description Read AC drive state 1 3000H 1: Running in forward direction 2: Running in reverse direction 3: Stopped 4: Auto‑tuning 5: Faulty Read AC drive state 2 7044H Bit0: Running state Bit1: Forward/Reverse direction Bit2: Whether a fault occurs Bit3: Whether the output frequency reaches the frequency reference...
Page 18 Parameter Communication Addresses Parameter Address Parameter Description AC drive fault description 8000H 2: Overcurrent 5: Overvoltage 8: Pre‑charge power fault 9: Undervoltage 10: AC drive overload 11: Motor overload 12: Input phase loss 13: Output phase loss 14: Overheat 15: External fault 17: Pre‑charge circuit exception 18: Current sampling exception 19: Motor auto‑tuning exception...
Page 19 Parameter Communication Addresses Parameter Address Parameter Description Continued Continued Continued 51: Pole position auto‑tuning error 55: Master‑slave control fault 56: Self‑check fault 1 57: Self‑check fault 2 58: Self‑check fault 3 59: Self‑check fault 4 61: Braking overload 62: Braking transistor fault 63: External alarm 82: Pre‑charge contactor fault 85: Timing fault...
Page 20: List Of Communication Protocols
List of Communication Protocols List of Communication Protocols The MD520 series AC drive supports seven communication protocols in the form of external communication expansion modules. For details, see the following table. Communication Protocol Communication Hardware RS485 communication Modbus External communication...
Page 21: Modbus Communication
Modbus Communication Introduction With the RS485 communication interface, the MD520 series AC drive connects as a communication slave to the PC/PLC control network with a single master and multiple slaves, which allows centralized control by using a PC or PLC. You can set the operation commands, modify or read parameters, and read the operating status and fault information of the AC drive through the communication protocol.
Page 22 Modbus Communication Figure 3‑1 Modbus communication interface Table 3–1 Function description of MD38TX1 terminals Function Terminal ID Terminal Name Terminal Layout 485+ RS485 RS485 communication communication signal (positive) terminal with isolation input 485– RS485 RS485 communication communication signal (negative) terminal with isolation input CGND Reference ground of...
Page 23 Modbus Communication Table 3–2 Jumper on the MD38TX1 expansion card Terminal Terminal Name Function Jumper/DIP Switch Position RS485 communication Connect the terminal terminal resistor setting resistor. jumper Disconnect the terminal resistor. The jumper setting is based on the top view of the expansion card with the main wir‑ ing terminal as the bottom side.
Page 24 Modbus Communication Figure 3‑3 Daisy chain Figure 3‑4 Branch connection It is recommended that the distance between the bus and the node do not exceed 3 ‑23‑...
Page 25 Modbus Communication Figure 3‑5 Star topology (prohibited) 3. Terminal wiring Terminal wiring for nodes with CGND ● MD38TX1 provides three cables, which connect to terminals RS485+, RS485–, and CGND respectively. Check that the RS485 field bus has these three cables and the wiring terminals are not connected reversely or incorrectly.
Page 26 Modbus Communication Recommended cable 1: Multi‑core twisted pair cables. Use one twisted pair ■ to connect RS485+ and RS485– and twist the remaining pairs into one to connect CGND. Recommended cable 2: Shielded twisted pair cables. Use the twisted pair ■...
Page 27: Transmission Mode
Modbus Communication Transmission Mode The RS485 communication network adopts the asynchronous serial half‑duplex transmission mode. Data is transmitted frame by frame in the form of packets agreed in the Modbus RTU protocol. An interval that is longer than the transmission time of 3.5 bytes on the communication data line marks the start of a new communication frame.
Page 28 Modbus Communication Similarly, multi‑write can be performed on up to 12 consecutive parameters at a time. If a slave detects a communication frame error or reading/writing failure caused by other reasons, it returns an error frame. Note No response is returned for CRC check error. The slave read response error command is 0x83, the write response error command is 0x86, and the multi‑write response error command is 0x90.
Page 29 Modbus Communication Table 3–4 Data frame fields Frame header (START) Idle time longer than the transmission time of 3.5 characters Slave address (ADR) Communication address range: 1 to 247 Command code (CMD) 03: Read slave parameters; 06: Write to slave parameters; 10: Multi‑write to slave parameters Parameter address (H) Internal parameter address of the AC drive, in hexadecimal...
Page 30 Modbus Communication the message after being calculated by the TX device. The RX device recalculates a CRC value for the received message, and compares the calculated value with the CRC value in the received CRC field. If the two CRC values are inconsistent, a transmission error occurs.
Page 31: Related Parameters
Modbus Communication Definition of communication parameter addresses: The parameters can be read and written (except those which cannot be changed because they are only for factory use or monitoring). Related Parameters Table 3–5 Parameters related to Modbus communication Parameter Default Value Range Description rame...
Page 32: Communication Configurations
3.6.1 Configuration of RS485 Communication Between AC Drive and H5U Software Acquisition and Hardware Connection 1. Log in to the official website of Inovance (https://newweb.inovance.com/hc/ serviceSupport/download) to obtain the H5U programming software. 2. Connect RS485+ and RS485– on the H5U terminal to RS485+ and RS485– on the AC drive, as shown in the following figure.
Page 33 Modbus Communication 2. Click on the left to go to the PLC configuration interface, select the protocol and data format, and click " " O O K K " " . 3. Click , then click " " A A d d d d M M o o d d b b u u s s C C o o n n f f i i g g " " and " " O O K K " " . is displayed.
Page 34 Modbus Communication After the read and write settings, click " " O O K K " " to return to the programming interface. Instances 1. Write the frequency (F0‑03 is set to 9). Data conversion: Multiply the desired frequency value a by 100, convert it to an integer, and then write it into 1000H.
Page 35 Modbus Communication by 10. According to the communication configuration, the D component address of the bus voltage is D300. Convert D300 to a floating‑point number and then divide this value by 10. The following figure shows the configuration and the program. 4.
Page 36 Modbus Communication 7. Read the DI state. Convert the DI state address U007 to 7007 based on the conversion rule, and convert the read value into a binary value. The LSB indicates DI1, the second bit indicates DI2, and so on. 8.
Page 37: Configuration Of Rs485 Communication Between Ac Drive And Am600
Modbus Communication Table 3–6 Common problems and solutions Problem Solution Failure to write Check F0‑03 to confirm that the address in the configuration frequency table is correct (when F0‑03 is 0, the address is the address of F0‑08; when F0‑03 is 9, the address is 1000H or 7310H). Check whether the terminal resistor is ON.
Page 38 Modbus Communication MD520 supports one RS485 interface, which is located on the MD38TX1 ● communication card, as shown in the following figure. Hardware connection procedure: 1. Take COM1 as an example. Connect one end of the network cable to CN1 of AM600 through the DB9 terminal, strip the other end of the cable and connect the RS485+, RS485–, and GND0 wires to RS485+, RS485–, and GND terminals of the AC drive, as shown in the following figure.
Page 39 Modbus Communication 2. Insert the terminal resistor jumper cap J3 on the expansion card to the right. AC Drive Configuration Set the following parameters on the AC drive: Set F0‑02 to 2 (set the command source to communication), and set F0‑03 to 9 (set the main frequency reference source to communication).
Page 40 Modbus Communication 3. Select AM600-CPU1608TP/TN, set Language to " " S S t t r r u u c c t t u u r r e e d d T T e e x x t t ( ( S S T T ) ) " " , and click "...
Page 41 Modbus Communication 6. Double‑click " " N N e e t t w w o o r r k k C C o o n n f f i i g g u u r r a a t t i i o o n n " " on the left, choose Serial Port > COM 0 on the right, and double‑click MODBUS.
Page 42 Modbus Communication 9. Add configuration information on the Modbus Slave Communication Configuration tab page. 10. Configure the register in the displayed window. The control word read address of the AC drive is 3000H, the write address is 2000H, and the frequency address is 1000H.
Page 43 Modbus Communication 11. On the Internal I/O Mapping tab page, map the variable in the PLC to the address of the AC drive. 12. Select the variable to be mapped. 13. Compile the program to check whether there are errors. If no error is found, log in to the PLC, download the program, and click Execute to execute the program.
Page 44 Modbus Communication ‑43‑...
Page 45: Canopen & Canlink Communication
The CANopen communication protocol is an international standard protocol. The CANlink communication protocol is a dedicated protocol independently developed by Inovance based on CAN bus application. This protocol can be used for communication with only Inovance PLCs such as H2U, H3U, and AM600.
Page 46 CANopen & CANlink Communication Sync mode ● Object Dictionary The object dictionary is an ordered set of parameters and variables. It is essentially a grouping of objects accessible through the network in an ordered predefined fashion. It includes all parameters of device profile and device network state. Each object within the object dictionary is addressed using a 16‑bit index and a 8‑bit sub‑index.
Page 47 CANopen & CANlink Communication TPDO1 — 0x180+Node‑Id TPDO2 — 0x280+Node‑Id TPDO3 — 0x380+Node‑Id TPDO4 — 0x480+Node‑Id EMCY object: 0x80+Node‑Id ● Node‑Id: Device ID (station address), which is defined by FD‑02 Communication objects are defined as follows: Network management (NMT) object ●...
Page 48 CANopen & CANlink Communication network device address, which occupies one byte. When it is 0, the message is a broadcast message for all slave devices in the network. For example, the command for setting a device with device address "6" to operable state is "0x0000x010x06".
Page 49: Networking And Interfaces
Communication Interface The MD38CAN1 card is a communication expansion card designed for CANopen/ CANlink communication of the MD520 series AC drives. It enables the AC drive to access the high‑speed CANopen/CANlink communication network and implements control of the field bus.
Page 50 CANopen & CANlink Communication Figure 4‑3 MD38CAN1 terminal layout Table 4–7 Function description of MD38CAN1 terminals Function Terminal ID Terminal Terminal Layout Name CANH Positive Connect to the CAN input positive end of the CAN bus. CANL Negative Connect to the CAN input negative end of the CAN bus.
Page 51 CANopen & CANlink Communication Table 4–8 Jumper on the MD38CAN1 expansion card Terminal Terminal Name Function Jumper/DIP Switch Position CAN terminal Connect the resistor terminal resistor. Disconnect the terminal resistor. The jumper setting is based on the top view of the expansion card with the main wir‑ ing terminal as the bottom side.
Page 52 CANopen & CANlink Communication Transmission Distance The CANopen/CANlink bus transmission distance is directly related to the baud rate and communication cable. The following table describes the relationship between the maximum bus length and the baud rate. Table 4–9 Relationship between the bus length and baud rate Baud Rate (bit/s) Length (m) 500k...
Page 53: Related Parameters
CANopen & CANlink Communication Related Parameters Table 4–10 Related parameters Parameter Parameter Description Default Value Value Range Name FD‑00 5005 Baud rate Ones: Modbus This parameter 0: 300 bit/s defines the rate 1: 600 bit/s of data 2: 1200 bit/s transmission 3: 2400 bit/s between the...
Page 54 CANopen & CANlink Communication Parameter Parameter Description Default Value Value Range Name FD‑10 Communication 1: CANopen This parameter protocol 2: CANlink defines the CAN communication protocol. The value 1 indicates CANopen communication. The value 2 indicates CANlink communication. FD‑14 0 to 65535 Number of CAN This parameter frames received...
Page 55: Application
CANopen & CANlink Communication Application 4.4.1 Data Frame Structure The AC drive parameters specify the mapping mode between parameters and object dictionary indexes, which facilitates operations on the parameters. Mapping between the parameters and CANopen object dictionary indexes is described as follows: Mapping mode ●...
Page 56: Operation Instance (Sdo)
CANopen & CANlink Communication 4.4.2 Operation Instance (SDO) Take reading F0‑17 as an example. The parameter address is 0xF011, the corresponding object dictionary index is 0x20F0, and the sub‑index is 0x12. 1. The communication master uses the CANopen SDO to perform the read operation on the AC drive.
Page 57 CANopen & CANlink Communication CAN Frame CANopen Data Description DATA0 Success: 0x4B 8‑byte frame data Return value of the Failure: 0x80 command code DATA1 Parameter group Low‑order byte of (0xF0 for group F0) index DATA2 0x20 High‑order byte of index DATA3 Parameter No.
Page 58 CANopen & CANlink Communication If the operation fails, the return value of the command code is "0x80"; the index remains unchanged; DATA4, DATA5, DATA6, and DATA7 are the SDO operation failure error code. Table 4–16 SDO returned during the write operation CAN Frame CANopen Data Description...
Page 59: Operation Instance (Pdo)
CANopen & CANlink Communication To set the command source to the operating panel, write 0 to F0‑02. The master sends a CANopen message as described in the following table. Table 4–19 Message sent from the master to write to F0‑02 Message ID (Hex) Data (Hex) 0x606...
Page 60 CANopen & CANlink Communication RPDO TPDO Address of Parameter in Address of Parameter in Group AF Group AF RPDO3 AF‑16 TPDO3 AF‑48 Sub‑index 1 Sub‑index 1 AF‑17 AF‑49 AF‑18 AF‑50 Sub‑index 2 Sub‑index 2 AF‑19 AF‑51 AF‑20 AF‑52 Sub‑index 3 Sub‑index 3 AF‑21 AF‑53...
Page 61: Communication Configurations
4.5.1 Configuration of CANlink Communication Between AC Drive and Software Acquisition and Hardware Connection 1. Log in to the official website of Inovance (https://newweb.inovance.com/hc/ serviceSupport/download) to obtain the H5U programming software. 2. Connect the H5U to the CN1 interface of the MD38CAN1 expansion card installed on the MD520 using twisted pair cables.
Page 62 CANopen & CANlink Communication 2. Click on the left, set as follows, and click " " O O K K " " . Protocol: Select CANlink. Station No.: Select Upper computer setting. (Note that the CANlink station number of the PLC cannot be the same as that of the AC drive.) Baud Rate: Select Upper computer setting.
Page 63 CANopen & CANlink Communication As shown in the preceding figure, send the bus voltage, output voltage, and output frequency of the AC drive to D300, D302, and D304 of the PLC. Configure the TX register address and D component correctly as needed. After the read and write settings, keep clicking "...
Page 64 CANopen & CANlink Communication the bus voltage is D300. Convert D300 to a floating‑point number and then divide this value by 10. The following figure shows the configuration and the program. 4. Read the output voltage. Convert the output voltage address U003 to 7003 based on the conversion rule. The read value is the actual output voltage.
Page 65 CANopen & CANlink Communication 7. Read the DI state. Convert the DI state address U007 to 7007 based on the conversion rule, and convert the read value into a binary value. The LSB indicates DI1, the second bit indicates DI2, and so on. The following figure shows the configuration and the program.
Page 66: Configuration Of Canopen Communication Between Ac Drive And H5U
Make sure that the D component is not occupied. 4.5.2 Configuration of CANopen Communication Between AC Drive and Software Acquisition and Hardware Connection 1. Log in to the official website of Inovance (https://newweb.inovance.com/hc/ serviceSupport/download) to obtain the H5U programming software and the latest EDS file.
Page 67 CANopen & CANlink Communication Master-Slave Configuration 1. Open AutoShop, click " " N N e e w w P P r r o o j j e e c c t t " " , check that " " S S e e r r i i e e s s a a n n d d m m o o d d e e l l s s " " is H5U, and click "...
Page 68 This step is to map data in the PDO, that is, the value to be read or written. The D component is used as a bridge to implement data exchange between the PLC and the AC drive. The H5U high‑performance small PLC of Inovance automatically performs I/O mapping based on the configured PDOs. Therefore, you only need to click I/O mapping to determine the D component to perform the read and write operations.
Page 69 CANopen & CANlink Communication 2. Implement start/stop control on the AC drive (F0‑02 is set to 2). Assign a value to the D component corresponding to the control word of the desired station to control forward running, reverse running, and stop of the AC drive through communication.
Page 70 CANopen & CANlink Communication 5. Read the output current. According to the conversion rule, the actual output current is the read output current divided by 100. The program is as follows: 6. Read the AC drive state. Read D7426 to directly obtain current state of the AC drive (1: Running in forward direction;...
Page 71 CANopen & CANlink Communication Common Problems and Solutions The must‑dos are listed as follows: 1. Check the wiring. Check whether the wrong pins are wired as CANH and CANL to the PLC. 2. Check the value of FD‑10. 1 indicates CANopen and 2 indicates CANlink. 3.
Page 72: Communication Faults
Predefined error code: See fault codes of the AC drive. ● Fault Codes The following table lists the standard fault codes of the MD520 series AC drive. For details, see the MD520 user guide. ‑71‑...
Page 73: Simple Diagnosis
CANopen & CANlink Communication Table 4–26 Fault information AC Drive Fault Information AC Drive Fault Information 2: Overcurrent 42: Excessive speed deviation 5: Overvoltage 43: Motor overspeed 8: Pre‑charge power fault 45: Motor overtemperature 9: Undervoltage 47: STO fault 10: AC drive overload 51: Pole position auto‑tuning error 11: Motor overload 55: Master‑slave control fault...
Page 74 CANopen & CANlink Communication Check whether the terminal resistor is only connected to both ends of the bus. Power off all devices and check whether the resistance between CANH and CANL of the bus is between 50 Ω and 60 Ω by using a multimeter. Check whether CANH and CANL of a node are reversely connected and whether CGND of the bus interface is connected (typically CGND of all devices are connected together and not grounded).
Page 75: Profinet Communication
V2.31-inovancemd500-20180705.xml. Installation The MD500‑PN1 card is embedded in the MD520 series AC drive. Before installation, cut off the power supply of the AC drive and wait for about 10 minutes until the charging indicator of the AC drive becomes off. Then, insert the MD500‑PN1 card into the AC drive and fasten the screws to prevent the signal socket between boards from being damaged by the pulling force of the external signal cable.
Page 76: Interface Layout And Description
PROFINET Communication Figure 5‑2 Connecting ground terminals of the MD500‑PN1 card and AC drive Interface Layout and Description The following figure shows the interface and indicator layout of the MD500‑PN1 card. The pin header J1 on the back of the MD500‑PN1 card is used to connect the AC drive. The MD500‑PN1 card provides two network ports (J2 and J3) for communication with the PROFINET card (PLC).
Page 77 PROFINET Communication Symbol Hardware Name Function It indicates the power status. ON indicates normal, and OFF indicates Power indicator abnormal (check whether the installation is correct). Status indicator of communication with PLC (PLCLINK) For details, see " Table 5–2 " on page 77 Status indicator of communication with AC drive (DSPLINK)
Page 78: Topology
PROFINET Communication Table 5–2 Status indicators of the MD500‑PN1 card State Description Indicator Solution Steady green Normal MAC address Steady yellow Replace the MD500‑PN1 card. abnormal Blinking yellow AC drive faulty Clear the AC drive fault. Abnormal Set F0‑28 to 1 and check Steady red communication with whether the AC drive supports...
Page 79 PROFINET Communication Figure 5‑5 Star topology ‑ ‑...
Page 80: Data Transmission Formats
PROFINET Communication Figure 5‑6 Tree topology Data Transmission Formats The MD500‑PN1 card transmits data using PZD formats with different lengths as required. You can set the functions supported by each PZD format during configuration. The following table lists the functions supported by each data format. ‑79‑...
Page 81 PROFINET Communication Data Format Data Length Supported Functions Standard telegram 1 PZD‑2/2 Setting of AC drive command and frequency Reading of AC drive state and running frequency Standard telegram 2 PZD‑4/4 Setting of AC drive command and frequency Periodic writing of two function parameters Reading of AC drive state and running frequency...
Page 82: Pzd Data
PROFINET Communication Data Format Data Length Supported Functions Standard telegram 6 PZD‑12/12 Setting of AC drive command and frequency Periodic writing of ten function parameters Reading of AC drive state and running frequency Periodic reading of ten function parameters Supplementary telegram PZD‑2/6 Setting of AC drive command and frequency...
Page 83 PROFINET Communication Table 5–4 Master Transmit Data PZD AC Drive Response Data PZD PZD1 PZD1 AC drive command AC drive running word (command state, which is source set to described as follows communication, that by bit: is, F0‑02 = 2) Bit0: 0: Stopped;...
Page 84: Related Parameters
PROFINET Communication Related Parameters AC Drive PN Card Configuration After installation, the MD500‑PN1 expansion card can communicate with the AC drive properly only after F0‑28 is set to 1. Parameter Parameter Value Range Setpoint Description Name F0‑28 Serial 0: Modbus Select the communication protocol...
Page 85: Communication Configurations
Before using the PROFINET master, you need to configure the GSDML file of the slave to add the corresponding slave device to the system of the master. If the file exists, skip step 2. You can obtain the GSDML file from Inovance or its agent. The configuration procedure is as follows: 1.
Page 86 PROFINET Communication Click Configure a device, as shown in the following figure. For a new project, click Add new device (marked with a red circle in the following figure). For an existing project, click Configure networks (marked with a green circle in the following figure).
Page 87 PROFINET Communication Select a PLC on the displayed page. Set the article number and firmware version of the PLC correctly to avoid download failure. Click Add or double‑click the selected master, as shown in the following figure. ‑ ‑...
Page 88 PROFINET Communication Now the master is established. 2. Install the GSDML file. (Skip this step if the GSDML file has been installed.) Choose Options > Manage general station description files (GSD). Select the path (English path required) for storing the GSDML file, select the GSDML file to be installed, and click Install.
Page 89 PROFINET Communication The GSDML file name varies with the AC drive series. For details, see the corresponding user guide. After the installation is successful, click Close. 3. Configure a slave. ‑ ‑...
Page 90 PROFINET Communication Click Device configuration on the interface. Click Network view. Select the Ethernet interface of the PLC, and choose Properties > General. ‑89‑...
Page 91 PROFINET Communication Set the IP address and subnet mask of the PLC master, and click Add new subnet. Locate MD500 under Hardware catalog on the right, and double‑click MD500PN. ‑ ‑...
Page 92 PROFINET Communication Click Not assigned to select the master system for the slave. Select the slave, and choose Properties > General. Then, choose PROFINET interface [X1] > Ethernet addresses and set the IP address. ‑91‑...
Page 93 PROFINET Communication Scroll down the screen to locate PROFINET. Deselect Generate PROFINET device name automatically and enter a name in PROFINET device name. (Or you can keep the option selected to allow the system to generate a device name automatically.) 4.
Page 94 PROFINET Communication 5. Configure PZDs. The PZD1 and PZD2 configurations are fixed and cannot be modified by users. PZD3 to PZD12 are for customized periodic data exchange. They can be set in hardware configuration. PZDx(master‑>slave) indicates the address used by the master to write to the slave, and PZDx(slave‑>master) indicates the address used by the master to read the slave.
Page 95 PROFINET Communication Switch to Network view. To add more stations, repeat the preceding steps. If the configuration is the same, select and copy a configured slave and modify the IP address and device name (note that the device name cannot be duplicate). 6.
Page 96 PROFINET Communication On the displayed page, devices of the same type are listed. Select the slave to be assigned with a device name based on its unique MAC address. The MAC address of the MD500‑PN1 card can be found on its housing. Then, click Assign name. ‑95‑...
Page 97 PROFINET Communication If information similar to that shown in the following figure is displayed, the device name is assigned successfully. The displayed PROFINET device name must be consistent with that displayed in the preceding figure. After assigning the device name, close the window or select another device from the PROFINET device name drop‑down list to assign device names for other stations.
Page 98: Mrp Function Of The Md500-Pn1 Card
PROFINET Communication To ensure normal operation of the PLC, function blocks such as OB82, 83, 86, and 122 need to be added during programming. The content of the function blocks can be compiled according to actual needs or left blank. 5.8.2 MRP Function of the MD500-PN1 Card The Media Redundancy Protocol (MRP) function is implemented by the MRP ring network in PROFINET.
Page 99: Fault Diagnosis
PROFINET Communication Each device in the ring network must be configured as an MRP manager or client. ● Configuration of the topological structure is not required during MRP ● configuration. You can configure the topological structure after the MRP configuration is complete if needed. Do not connect devices without the MRP function configured to the ring network.
Page 100 PROFINET Communication Symptom Solution After the AC drive is 1. Check that F0‑28 is set to 1. powered on, only the 2. Check the AC drive type. This user guide only describes the power indicator (D4) is on, usage of MD520. For other AC drive models, contact the indicating that the technical engineers to obtain the correct user guide.
Page 101 PROFINET Communication Symptom Solution Check whether the operated address is correct. For example, if the I address and Q address of the station are both 520 to 531 (note that the I and Q addresses may start from different numbers), the PZD1 and PZD2 data written into the AC drive No data can be are stored in QW520 and QW522, respectively.
Page 102 PROFINET Communication The MD500‑PN1 card can be replaced directly when the slave node is faulty (only when the MD500‑PN1 card is faulty) without device configuration again. The prerequisites for directly replacing the MD500‑PN1 card are as follows: The alternative component and the component to be replaced are both the ●...
Page 103 PROFINET Communication In the topology view, click and drag the interface to the interface of another device that is directly connected to this interface, and release the mouse button. Note that the preceding connection must be consistent with the actual network connection of devices.
Page 104 PROFINET Communication Click the General tab, select Support device replacement without exchangeable medium, and click OK, as shown in the following figure. According to the actual network connections, double‑click Port 1 or Port 2 of the PLC, and switch to the Topology tab. Select the port of the slave connected to the ‑103‑...
Page 105 PROFINET Communication PLC from the Partner port drop‑down list (the default option is Any partner, which must be changed to the actual connected port), and click OK. Then click the corresponding ports of the slave to set the topology. The operations are similar to the preceding steps.
Page 106: Ethercat Communication
(ECAT card for short) operates at the I/O layer and features high efficiency, flexible topology, and easy operation. It is installed on the MD520 series AC drive to improve the communication efficiency and implement AC drive networking, enabling the AC drive to be a slave controlled by the fieldbus master.
Page 107: Interface Layout And Description
EtherCAT Communication Figure 6‑2 Connecting ground terminals of the MD500‑ECAT card and AC drive Interface Layout and Description The following figure shows the interface and indicator layout of the MD500‑ECAT card. The pin header J7 on the back of the MD500‑ECAT card is used to connect the AC drive.
Page 108 Master Check whether the master and upstream disconnected or Steady off network port are connected correctly. working in Initial mode Steady off Normal ESC internal Steady red Contact Inovance for technical support. exception ‑107‑...
Page 109: Topology
EtherCAT Communication Topology After enabling communication between the ECAT card and the AC drive, connecting the ECAT card to the ECAT master correctly and completing relevant communication configuration can enable the communication between the ECAT card and ECAT master and the AC drive networking function. The ECAT card supports various topological structures including star, bus, and tree topologies and their combinations.
Page 110 EtherCAT Communication Data Sent by the Master (RPDO) Table 6–3 Master transmit data RPDO RPDO Description RPDO1 AC drive command word (command source set to communication, that is, F0‑02 = 2) 1: Run in forward direction ● 2: Run in reverses direction ●...
Page 111: Sdo Mailbox Data
EtherCAT Communication TPDO2 AC drive running frequency (unit: 0.01 Hz) The current AC drive running frequency is returned. The returned data is 16‑bit signed data and the received data is 16‑bit unsigned data. Variables must be mapped to the 16‑bit signed data. TPDO3 to TPDO12 Parameter read in real time.
Page 112 EtherCAT Communication Parameter Parameter Setpoint Description Value Range Name F0‑28 Serial 0: Modbus Select the communication protocol special protocol communication Communication card network card network bridge protocol bridge protocol as the serial communication protocol. F0‑02 0: Operating Command Set the panel source command...
Page 113 EtherCAT Communication Communication Control Parameters Table 6–5 Communication control parameters Parameter Parameter Value Range Decimal Address Name U3‑16 Frequency 29456 –Maximum frequency to reference +Maximum frequency 0.01 Hz U3‑17 0000: Stop 0004: Jog in 29457 Control according to the command reverse stop mode direction...
Page 114 EtherCAT Communication 17; otherwise, an operation exception will occur. Besides, if any non‑zero value is written to the high‑order 8 bits of U3‑17, the AC drive will report the communication fault Err164. Communication Monitoring Parameters Table 6–6 Communication monitoring parameters Parameter Parameter Name Unit...
Page 115 EtherCAT Communication Parameter Parameter Name Unit Decimal Address U0‑27 1 Hz 28699 Pulse input frequency U0‑28 Communication 0.01% 28700 reference U0‑29 0.01 Hz 28701 Encoder feedback speed U0‑30 0.01 Hz 28702 Main frequency X U0‑31 Auxiliary frequency Y 0.01 Hz 28703 Any memory address 1 28704...
Page 116 EtherCAT Communication Parameter Parameter Name Unit Decimal Address U0‑66 100: CANopen 28738 Expansion card 200: PROFIBUS DP model 400: PROFINET 500: EtherCAT 600: EtherNet/IP U0‑67 0.01 28739 Expansion card version U0‑68 28740 AC drive state U0‑69 0.01 Hz 28741 Running frequency U0‑70 1 RMP 28742...
Page 117: Communication Configurations
6.8.1 Communication Instance of Controlling MD520 with an Omron Controller This section takes Omron's NX701 master as an example to describe how to configure and use the MD520 series AC drives. 1. Create a project. Device: Select the actual controller model.
Page 118 EtherCAT Communication 3. Import the XML configuration file. Double‑click EtherCAT on the left, select and right‑click the master, click Install (File) in the ESI Library window, select the MD500‑ECAT card XML configuration file and import it. 4. Scan for devices. Switch the controller to the online running mode.
Page 119 EtherCAT Communication Scan for devices and add slaves. Choose Configurations and Setup > EtherCAT, right‑click the master device, and choose Compare and Merge with Actual Network Configuration. The controller automatically scans all slaves in the network (a fault will be reported if any station number is 0). After the scanning is complete, click Apply in the displayed Apply actual network configuration dialog box.
Page 120 EtherCAT Communication 5. Set the parameters. Switch the controller to the offline mode. ‑119‑...
Page 121 EtherCAT Communication Set the PDO mapping (I/O mapping). 6. Edit the PLC program. ‑ ‑...
Page 122 EtherCAT Communication 7. Download the program to the controller. After the configuration and programming are complete, switch the controller back to the online state, and download the program to the controller. ‑121‑...
Page 123: Communication Instance Of Controlling Md520 With An H5U Controller
Controller This section takes the H5U master as an example to describe how to configure and use the MD520 series AC drives. 1. Open the software and create an H5U project Select H5U Series in the Series and models drop‑down list, as shown in the following figure.
Page 124 EtherCAT Communication 2. Import the EtherCAT configuration file of MD520. Right‑click EtherCAT Devices and choose Import Device XML. If an MD520 EtherCAT configuration file of another version exists, delete the existing configuration file before importing a new one. See the following figure. ‑123‑...
Page 125 EtherCAT Communication 3. Add an MD520 AC drive slave. Double‑click EtherCAT under Config on the left to open network configuration, and drag the device in the network device list to add the AC drive slave. 4. Set the PDO parameters. Click Process Data, and click Add to add the TPDO mapping as required.
Page 126 EtherCAT Communication NOTE: Control Command of the RPDO and Inverter State of the RPDO cannot be changed and they must be set as the first entries. Otherwise, an operation exception will occur. 5. Scan for the H5U PLC. Choose Tools > Communication Settings, select a communication mode between the PC and PLC (Ethernet or USB), and scan for the PLC.
Page 127: Communication Instance Of Controlling Md520 With An Am600 Controller
Controller This section takes the AM600 master as an example to describe how to configure and use the MD520 series AC drives. 1. Open the software and create an AM600 project. Select AM600-CPU1608TP/TN in the Device drop‑down list, as shown in the following figure.
Page 128 EtherCAT Communication 2. Add an MD520 AC drive slave. Open network configuration, and import the EtherCAT configuration file of MD520. If any configuration file of another version exists, delete the existing configuration file before importing a new one. Drag the device in the network device list to add the AC drive slave, as shown in the following figure.
Page 129 EtherCAT Communication 3. Set the PDO parameters. Right‑click the position marked with a red arrow in the following figure to add the TPDO mapping as required. Control Command of the RPDO and Inverter State of the RPDO cannot be changed and they must be set as the first entries. Otherwise, an operation exception will occur.
Page 130 EtherCAT Communication Scan for devices. Download the project to the PLC. You can view TPDO data and write RPDO data in real time through EtherCAT I/O mapping. ‑129‑...
Page 131: Communication Instance Of Controlling Md520 With A Beckhoff Controller
EtherCAT Communication You can view and directly write parameter values through the online CoE. 6.8.4 Communication Instance of Controlling MD520 with a Beckhoff Controller This section takes Beckhoff's TwinCAT master as an example to describe the configuration of the MD500‑ECAT card. ‑...
Page 132 EtherCAT Communication Select a 100M Ethernet network adapter with an Intel chip. Other network adapters may not support EtherCAT. 1. Install TwinCAT. Windows XP: tcat_2110_2230 is recommended. ● Windows 7 32‑bit: tcat_2110_2248 is recommended. ● 2. Copy the EtherCAT configuration file (MD500_1Axis_V1.03.xml) of MD520 to the TwinCAT installation directory.
Page 133 EtherCAT Communication 4. Install the TwinCAT network adapter driver. Choose TWINCAT > Show Real Time Ethernet Compatible Devices…. In the displayed dialog box, select the local network adapter under Incompatible devices, and click Install. After installation, the installed network adapter is displayed under Installed and ready to use devices.
Page 134 EtherCAT Communication 5. Search for devices. a. Create a project, right‑click Devices, and then click Scan to search for devices, as shown in the following figure. ‑133‑...
Page 135 EtherCAT Communication b. Click OK. c. Click OK. ‑ ‑...
Page 136 EtherCAT Communication d. Click Yes. e. Click OK. f. Click No. Now the device search is complete, as shown in the following figure. ‑135‑...
Page 137 EtherCAT Communication 6. Set the PDO parameters. a. Configure TPDOs. Select 0x1A00. The first two entries are default TPDOs and cannot be changed. Right‑click the position marked with a red arrow in the following figure to add the TPDO mapping as required. ‑...
Page 138 EtherCAT Communication b. Configure RPDOs. Select 0x1600. The first two entries are default RPDOs and cannot be changed. Right‑click the position marked with a red arrow in the following figure to add the RPDO mapping as required. c. View the SDO data list. After the OP state is activated, you can view real‑time data in the SDO data list or double‑click the object dictionary to modify the SDO data.
Page 139 EtherCAT Communication d. Activate the configuration and switch to the running mode. Click . The following dialog box is displayed. Click OK. Click OK to enter the OP state. ‑ ‑...
Page 140 EtherCAT Communication e. Control the AC drive through PDO. Write corresponding values through the configured RPDO to control the AC drive. ‑139‑...
Page 141: Fault Diagnosis
EtherCAT Communication Fault Diagnosis 6.9.1 ECAT Card Communication Faults The following table describes the faults that may occur during use of the MD500‑ECAT card and the AC drive. ‑ ‑...
Page 142 The D7 indicator An ESC internal on the Contact Inovance for technical support. exception occurs. ECAT card is steady red. The MD500‑ECAT card can be replaced directly when the slave node is faulty (only when the MD500‑ECAT card is faulty) without device configuration again.
Page 143 EtherCAT Communication 1. The wiring sequence remains unchanged before and after replacing the MD500‑ ECAT card. 2. The XML file version of the new MD500‑ECAT card is the same as that of the original card. 3. If a station alias is used for configuring the MD500‑ECAT card, the alias of the new device must be consistent with that of the original device.
Page 144: Profibus Dp Communication
Installation The MD38DP2 card is embedded in the MD520 series AC drive. Before installation, cut off the power supply of the AC drive and wait for about 10 minutes until the charging indicator of the AC drive becomes off.
Page 145: Interface Layout And Description
PROFIBUS DP Communication Figure 7‑2 Connecting ground terminals of the MD38DP2 card and AC drive Interface Layout and Description Figure 7‑3 Interface layout of the MD38DP2 card ‑ ‑...
Page 146 PROFIBUS DP Communication DIP Switch MD38DP2 DIP switch description Digit Description Function PROFIBUS DP card type OFF: MD38DP2 (default) switchover ON: MD38DP1 The addresses of stations 1 to 125 can be set by the 7‑ digit binary DIP switch. For example: Address DIP PROFIBUS DP Switch Setting (digit 8: least 2 to 8...
Page 147 PROFIBUS DP Communication Figure 7‑4 DB9 terminal pins Control Terminals Table 7–1 Function description of control terminals Category Symbol Terminal Name Function 1, 2, 7, and 9 Unconnected internally Positive pole of the data line PROFIBUS Data line B communica Request to send signal tion Isolated 5 V power ground...
Page 148: Topology And Transmission Distance
PROFIBUS DP Communication Category Symbol Terminal Name Function Steady ON: The AC drive is powered on. ● OFF: The AC drive is disconnected from ● D4 (red) Power indicator the power supply or the PROFIBUS DP card is installed incorrectly. Steady ON: Communication between the ●...
Page 149 PROFIBUS DP Communication Figure 7‑5 Connection between the PROFIBUS DP card and PROFIBUS master Terminal resistors must be connected at both ends of the PROFIBUS bus and DIP switches must be set correctly according to the marks on the wiring terminals. After terminal resistors are connected correctly, the resistance between A1 and B1 should be 110 Ω...
Page 150: Protocol Description
PROFIBUS DP Communication Type A Type B Cable Parameter Impedance 135 Ω to 165 Ω (f = 3 to 20 MHz) 100 Ω to 130 Ω (f > 100 kHz) Capacitor < 30 pF/m < 60 pF/m Not specified < 110 Ω/km Resistor Cross‑sectional area ≥...
Page 151 PROFIBUS DP Communication Figure 7‑6 PPO data formats PKW Data PKW data is used by the master to read/write to a single parameter of the AC drive. The communication address of the AC drive parameter is directly determined by the communication data.
Page 152 PROFIBUS DP Communication PKW Data Sent by the Master PKW Data Returned by the AC Drive High‑order 4 bits: ● Command code0: No request1: Read parameter High‑order 4 bits: Response code0: No data2: Modify parameter ● request1: Operation succeeded7: data (The preceding Operation failed command code is in Low‑order 8 bits: High‑order bits of...
Page 153 PROFIBUS DP Communication Figure 7‑8 Example PKW data sent by the master when modifying an AC drive parameter PKW data exchange with the AC drive is performed cyclically. Continuous write command (PKE = 0x20xx) on the EEPROM will significantly shorten the service life of the AC drive's main control chip.
Page 154 PROFIBUS DP Communication Master Transmit Data PZD AC Drive Response Data PZD AC Drive Parameters Read in AC Drive Running Frequency AC Drive Command Real Time PZD1 PZD2 PZD3 to PZD12 Data Sent by the Master Master Transmit Data PZD AC drive command word (command source set to communication) 0: No command...
Page 155: Related Parameters
PROFIBUS DP Communication AC Drive Response Data PZD Function parameter values (group F and group A) and monitoring parameter values (group U) read in real time FE‑22 to FE‑31 correspond to PZD3 to PZD12. For the configuration, see PZD data configuration. PZD3 to PZD12 After communication with the PLC is established, FE‑02 to FE‑11 display the parameter values written into PZD3 to PZD12.
Page 156: Communication Control Parameters
PROFIBUS DP Communication 7.6.2 Communication Control Parameters Parameter Parameter Value Range Hexadecimal Decimal Address Name Address U3‑16 Frequency H7310 29456 –Maximum reference frequency to +Maximum frequency Unit: 0.01 Hz U3‑17 0001: Run in H7311 29457 Control command forward direction 0002: Run in reverse direction 0003: Jog in forward direction...
Page 157: Communication Configurations
Before using the PROFIBUS master, you need to configure the GSD file of the slave to add the corresponding slave device to the system of the master. If the file exists, skip step 2. You can obtain the GSD file from Inovance or its agent. The configuration procedure is as follows: 1.
Page 158 PROFIBUS DP Communication Click Install. After the installation is complete, the PROFIBUS DP module MD38DP2 is displayed, as shown in the following figure. ‑157‑...
Page 159 PROFIBUS DP Communication Note: If any master or slave already exists on the HW.config interface, close the current interface by clicking the X button (marked with a red circle as shown in the following figure) before importing the GSD file. In this case, you can save the original project.
Page 160 PROFIBUS DP Communication Select the original configuration project, and click OK to open it. 3. Configure the actual hardware system, as shown in the following figure. ‑159‑...
Page 161 PROFIBUS DP Communication In the preceding figure, station 4 is MD38DP1, which is only used as an example. For details about its usage, see the MD380 Series PROFIBUS User Guide. MD38DP1 and MD38DP2 can coexist on the same network. 4. Configure data features of the slave. After the PPO type is added, the address assigned by the PLC to the slave is displayed, as shown in the following figure.
Page 162 PROFIBUS DP Communication PZDx(master‑>slave) indicates the address used by the master to write to the slave, and PZDx(slave‑>master) indicates the address used by the master to read the slave. PZD3 to PZD12 are displayed in decimal and can be modified. For example, to set PZD3(master->slaver) to F0‑12, enter 61452.
Page 163: Configuring A Slave On The S7-1200 Master In Tia Portal V13
PROFIBUS DP Communication After the preceding steps, the PROFIBUS slave is configured. Now, you can compile programs in S7‑300 to control the AC drive. 7.7.2 Configuring a Slave on the S7-1200 Master in TIA Portal V13 1. Open TIA Portal V13, create a project, and add an S7‑1200 master according to actual situations.
Page 164 PROFIBUS DP Communication Since the S7‑1200 CPU has no PROFIBUS interface, you need to add a PROFIBUS communication module. In this example, a CM1243‑5 master module is added. After adding the PROFIBUS master module, click Network view. Select the communication module, click Properties and then General, and click Add new subnet to create a PROFIBUS network.
Page 165 PROFIBUS DP Communication 2. Install the GSD file. Skip this step if a GSD file has been installed. If a GSD file is not installed yet, Not yet installed will be displayed in the Status column. Select the GSD file and click Install. (Note that an error will occur if the installation path contains Chinese characters.) ‑...
Page 166 PROFIBUS DP Communication When the interface shown in the following figure is displayed, the installation is complete. Click Close. During installation of the GSD file, the PORTAL will automatically close the configuration interface. After the installation is complete, double‑click Devices & networks on the left to open the original configuration interface.
Page 167 PROFIBUS DP Communication Choose Hardware catalog > Other field devices > PROFIBUS-DP > General. You can find the MD38DP2 in the list, which is the same as that in STEP 7. You need to fully expand the subordinate directories as shown in the following figure. ‑...
Page 168 PROFIBUS DP Communication 3. Start the configuration. On the Hardware catalog tab page, double‑click MD38DP2 or drag it to Network view under Devices & networks, and click Not assigned under the slave to select the corresponding PROFIBUS network. Select the slave, click Properties and then General, and set the slave number.
Page 169 PROFIBUS DP Communication Click General DP parameters, and select DPV0 from the DP interrupt mode drop‑ down list, as shown in the following figure. ‑ ‑...
Page 170 PROFIBUS DP Communication Click Device view, and select a proper PPO type under Hardware catalog. The addresses assigned for each segment are displayed as follows. The PKW address is marked with a red circle in the following figure. If the selected PPO has no PKW, the column is blank.
Page 171 PROFIBUS DP Communication 5. Compile and download the configuration. If the settings of multiple slaves are the same, select a configured slave, press Ctrl +C and then Ctrl+V (or right‑click the configured slave and choose Copy and then Paste) to connect more slaves to the network, and then modify their station numbers.
Page 172: Performing Periodic Read/Write Operations On The Ac Drive Slave
PROFIBUS DP Communication Set the interface for the PC the communicate with the PLC as required on the displayed interface. In this example, a local network port is selected. Then click Start search to search for the PLC. If no accessible device is found, the connection between the PC and PLC is faulty. Eliminate the fault first.
Page 173 PROFIBUS DP Communication 1. Directly use the MOVE command to enable the AC drive to run in forward direction at the target frequency of 30 Hz (F0‑02 = 2, F0‑03 = 9), as shown in the following figure. Other data is written in a similar way. The read data can also be transmitted from the PIW register to the common Q, I, L, M, or D register using the MOVE command for parsing.
Page 174: Performing Aperiodic Read/Write Operations On The Ac Drive Slave
PROFIBUS DP Communication LADDR: Starting address configured in the Q block of the module, which must ● be in hexadecimal format. RET_VAL: Return value. If an error occurs during function activation, the return ● value contains an error code. If no error occurs, 0 is returned. RECORD: Source area of the user data to be written.
Page 175 PROFIBUS DP Communication After M0.0 is set, the function block reads F0‑02 (Index 0 has been set to F0‑02 before) of the AC drive No. 3 and saves it in QW6. The fields are defined as follows: REQ: Command enable. When this field is set to 1, the function block is enabled. ●...
Page 176 PROFIBUS DP Communication VALID: New data record received and valid. ● BUSY: When the value is ON, the operation is not completed. ● ERROR: Error flag. When the value is ON, an error occurs. ● STATUS: Block status or error information. ●...
Page 177: Fault Diagnosis
PROFIBUS DP Communication Note that before running an organization block, you need to download data blocks (above the function block, DB1 and DB2 in this example) to the PLC. Otherwise, an error indicating that the DB blocks are not loaded will be reported. SFB53 is used to perform operations on the EEPROM.
Page 178 PROFIBUS DP Communication Symptom Solution 1. Check that the cable is properly connected. 2. Check the DIP switches on the PROFIBUS DP interfaces. The DIP switches on the PROFIBUS DP interfaces at both ends of the network must be set to ON, and the DIP switches on other PROFIBUS DP After the interfaces must be set to OFF.
Page 179 PROFIBUS DP Communication Symptom Solution Check whether the operated address is correct. No matter whether the PPO type used contains the PKW area, the address for the read and write operations is located in the second row (also the last row). For example, if the I address and Q address in the last row of the station are both 520 to 531 (note that the I and Q addresses may start from different numbers),...
Page 180 PROFIBUS DP Communication Symptom Solution 1. Disconnect the power supply, and measure the After communication is resistance between A1 and B1 of the PROFIBUS DP established, the communication is slave interface at the farthest end with a multimeter. normal when the AC drive is not The resistance should be 100±20 Ω.
Page 181 PROFIBUS DP Communication Symptom Indicator※ Status Solution The master is not Blinking at 5 Hz Yellow (D3) Check the master state. running. Check that the slave The connection address is correct and the between the MD38DP2 Yellow (D3) PROFIBUS cable is expansion card and the connected properly.
Page 182 PROFIBUS DP Communication Symptom 2: The file cannot be interpreted. ● Possible cause: During the GSD file transmission, the file name is changed manually or by the transmission tool. In this case, the file name fails to meet the PROFIBUS requirements. Solution: Change the GSD file name to MD38DP2.GSD.
Page 183 PROFIBUS DP Communication Possible cause: The GSD file is modified. Solution: Use a correct GSD file. Other cases ● Some versions of STEP 7 and PORTAL do not support a path that contains Chinese for installing the GSD file. In this case, store the GSD file in a path that does not contain Chinese characters.
Page 184: Md-Si-Dp1 Communication
CAN communication Installation The MD‑SI‑DP1 expansion card is embedded in the MD520 series AC drive. Before installation, cut off the power supply of the AC drive and wait for about 10 minutes until the charging indicator of the AC drive becomes off. Then, insert the MD‑SI‑DP1 card into the AC drive and fasten the screws to prevent the signal socket between boards from being damaged by the pulling force of the external signal cable.
Page 185 MD‑SI‑DP1 Communication Figure 8‑1 Installation of MD‑SI‑DP1 Figure 8‑2 Connecting ground terminals of the MD‑SI‑DP1 card and AC drive Do not install or disassemble this card with power on. ‑ ‑...
Page 186: Interface Layout And Description
MD‑SI‑DP1 Communication Interface Layout and Description Figure 8‑3 Interface layout of the MD‑SI‑DP1 card DIP Switch Digit Description Function PROFIBUS DP card OFF: MD‑SI‑DP1 (default) type switchover ON: Reserved The addresses of stations 1 to 125 can be set by the 7‑digit binary DIP switch.
Page 187 MD‑SI‑DP1 Communication The change of digit 1 is valid upon the next power‑on. The change of slave addresses takes effect immediately after setting. Standard 9-pin PROFIBUS Interface The MD‑SI‑DP1 expansion card is connected to the PROFIBUS master using the standard DB9 socket. The pin signal definition and pin arrangement of the standard DB9 socket are the same as those of Siemens' DB9 socket, as shown in the following figure.
Page 188: Topology And Transmission Distance
MD‑SI‑DP1 Communication Category Symbol Terminal Name Function Steady ON: The AC drive is powered on. ● OFF: The AC drive is disconnected from the ● D4 (red) Power indicator power supply or the PROFIBUS DP card is installed incorrectly. Steady ON: Communication between the ●...
Page 189 MD‑SI‑DP1 Communication terminal resistors are connected correctly, the resistance between A1 and B1 should be 110 Ω upon power‑off. For devices connected at both ends of the PROFIBUS network, the communication cables must be connected from their PROFIBUS DP terminals to the channels marked with "IN" (channels corresponding to A1/B1). Otherwise, terminal resistors cannot be connected.
Page 190: Protocol Description
MD‑SI‑DP1 Communication Protocol Description Data Transmission Formats In the PROFIdrive protocol, the PPO is used as the data transmission format. PPOs are classified into PPO1, PPO2, PPO3, PPO4, and PPO5, all of which are supported by the MD38DP2 expansion card. The following table lists the functions supported by each data format.
Page 191 MD‑SI‑DP1 Communication PKW Data PKW data is used by the master to read/write to a single parameter of the AC drive. The communication address of the AC drive parameter is directly determined by the communication data. The functions of PKW data are as follows: Reading function parameters of the AC drive ●...
Page 192 MD‑SI‑DP1 Communication Application The following figure shows the PKW data sent by the master and PKW response data returned by the AC drive when the master reads the AC drive parameter F0‑08. Figure 8‑7 Example PKW data sent by the master when reading an AC drive parameter The following figure shows the PKW data sent by the master and PKW response data returned by the AC drive when the master modifies the AC drive parameter F0‑08.
Page 193 MD‑SI‑DP1 Communication Parameter Group Address F0 to FF 0x00 to 0x0F A0 to AF 0x40 to 0x4F For example, the RAM address of F0‑10 is 0x000A. PZD Data The PZD data enables the master to modify and read AC drive data in real time and perform periodic data exchange.
Page 194: Related Parameters
MD‑SI‑DP1 Communication Master Transmit Data PZD Function parameter values (group F and group A) modified in real time, not written into EEPROM FE‑02 to FE‑11 correspond to PZD3 to PZD12. For the configuration, see PZD data configuration. PZD3 to PZD12 After communication with the PLC is established, FE‑02 to FE‑...
Page 195 MD‑SI‑DP1 Communication Parameter Value Range Setpoint Description Parameter Name Select the special 0: Modbus protocol Serial communication card 1: Communication communication network bridge as the F0‑28 card network protocol serial communication bridge protocol protocol. Communication Control Parameters Parameter Parameter Value Range Hexadecimal Decimal Address Name...
Page 196 MD‑SI‑DP1 Communication Parameter Parameter Value Range Hexadecimal Decimal Address Name Address U3‑20 0 to 7FFF, H7314 29460 AO2 control indicating 0% to 100% U3‑21 0 to 7FFF, H7315 29461 FMP control indicating 0% to 100% U3‑23 Signed data, 1 RPM H7317 29463 Speed control When the MD‑SI‑DP1 expansion card is used, the written PZD1 and PZD2 are mapped...
Page 197 MD‑SI‑DP1 Communication Parameter Parameter Name Unit Hexadecimal Decimal Address Address U0‑19 0.01 Hz H7013 28691 Feedback speed (Hz) U0‑20 Remaining running 0.1 min H7014 28692 duration U0‑21 0.001 V H7015 28693 AI1 voltage before correction U0‑22 0.001 V H7016 28694 AI2 voltage before correction 0.001 V...
Page 198 MD‑SI‑DP1 Communication Parameter Parameter Name Unit Hexadecimal Decimal Address Address U0‑44 H702C 28716 DI state display 2 U0‑45 H702D 28717 Fault information U0‑58 H703A 28730 Z signal counter U0‑59 Frequency 0.01% H703B 28731 reference (%) U0‑60 0.01% H703C 28732 Running frequency H703D 28733 U0‑61...
Page 199: Communication Configurations
Before using the PROFIBUS master, you need to configure the GSD file of the slave to add the corresponding slave device to the system of the master. If the file exists, skip step 2. You can obtain the GSD file from Inovance or its agent. The configuration procedure is as follows: 1.
Page 200 MD‑SI‑DP1 Communication Click Install. After the installation is complete, the PROFIBUS DP module MD38DP2 is displayed, as shown in the following figure. ‑199‑...
Page 201 MD‑SI‑DP1 Communication Note: If any master or slave already exists on the HW.config interface, close the current interface by clicking the X button (marked with a red circle as shown in the following figure) before importing the GSD file. In this case, you can save the original project. If an alarm indicating that system data cannot be created is displayed, click OK.
Page 202 MD‑SI‑DP1 Communication Select the original configuration project, and click OK to open it. 3. Configure the actual hardware system, as shown in the following figure. ‑201‑...
Page 203 MD‑SI‑DP1 Communication In the preceding figure, station 4 is MD38DP1, which is only used as an example. For details about its usage, see the MD380 Series PROFIBUS User Guide. MD38DP1 and MD38DP2 can coexist on the same network. 4. Configure data features of the slave. After the PPO type is added, the address assigned by the PLC to the slave is displayed, as shown in the following figure.
Page 204 MD‑SI‑DP1 Communication PZDx(master‑>slave) indicates the address used by the master to write to the slave, and PZDx(slave‑>master) indicates the address used by the master to read the slave. PZD3 to PZD12 are displayed in decimal and can be modified. For example, to set PZD3(master->slaver) to F0‑12, enter 61452.
Page 205: Configuring A Slave On The S7-1200 Master In Tia Portal V13
MD‑SI‑DP1 Communication After the preceding steps, the PROFIBUS slave is configured. Now, you can compile programs in S7‑300 to control the AC drive. 8.7.3 Configuring a Slave on the S7-1200 Master in TIA Portal V13 1. Open TIA Portal V13, create a project, and add an S7‑1200 master according to actual situations.
Page 206 MD‑SI‑DP1 Communication Since the S7‑1200 CPU has no PROFIBUS interface, you need to add a PROFIBUS communication module. In this example, a CM1243‑5 master module is added. After adding the PROFIBUS master module, click Network view. Select the communication module, click Properties and then General, and click Add new subnet to create a PROFIBUS network.
Page 207 MD‑SI‑DP1 Communication 2. Install the GSD file. Skip this step if a GSD file has been installed. If a GSD file is not installed yet, Not yet installed will be displayed in the Status column. Select the GSD file and click Install. (Note that an error will occur if the installation path contains Chinese characters.) ‑...
Page 208 MD‑SI‑DP1 Communication When the interface shown in the following figure is displayed, the installation is complete. Click Close. During installation of the GSD file, the PORTAL will automatically close the configuration interface. After the installation is complete, double‑click Devices & networks on the left to open the original configuration interface.
Page 209 MD‑SI‑DP1 Communication Choose Hardware catalog > Other field devices > PROFIBUS-DP > General. You can find the MD38DP2 in the list, which is the same as that in STEP 7. You need to fully expand the subordinate directories as shown in the following figure. ‑...
Page 210 MD‑SI‑DP1 Communication 3. Start the configuration. On the Hardware catalog tab page, double‑click MD38DP2 or drag it to Network view under Devices & networks, and click Not assigned under the slave to select the corresponding PROFIBUS network. Select the slave, click Properties and then General, and set the slave number.
Page 211 MD‑SI‑DP1 Communication Click General DP parameters, and select DPV0 from the DP interrupt mode drop‑ down list, as shown in the following figure. ‑ ‑...
Page 212 MD‑SI‑DP1 Communication Click Device view, and select a proper PPO type under Hardware catalog. The addresses assigned for each segment are displayed as follows. The PKW address is marked with a red circle in the following figure. If the selected PPO has no PKW, the column is blank.
Page 213 MD‑SI‑DP1 Communication 5. Compile and download the configuration. If the settings of multiple slaves are the same, select a configured slave, press Ctrl +C and then Ctrl+V (or right‑click the configured slave and choose Copy and then Paste) to connect more slaves to the network, and then modify their station numbers.
Page 214: Performing Periodic Read/Write Operations On The Ac Drive Slave
MD‑SI‑DP1 Communication Set the interface for the PC the communicate with the PLC as required on the displayed interface. In this example, a local network port is selected. Then click Start search to search for the PLC. If no accessible device is found, the connection between the PC and PLC is faulty. Eliminate the fault first.
Page 215 MD‑SI‑DP1 Communication 1. Directly use the MOVE command to enable the AC drive to run in forward direction at the target frequency of 30 Hz (F0‑02 = 2, F0‑03 = 9), as shown in the following figure. Other data is written in a similar way. The read data can also be transmitted from the PIW register to the common Q, I, L, M, or D register using the MOVE command for parsing.
Page 216: Performing Aperiodic Read/Write Operations On The Ac Drive Slave
MD‑SI‑DP1 Communication LADDR: Starting address configured in the Q block of the module, which must ● be in hexadecimal format. RET_VAL: Return value. If an error occurs during function activation, the return ● value contains an error code. If no error occurs, 0 is returned. RECORD: Source area of the user data to be written.
Page 217 MD‑SI‑DP1 Communication After M0.0 is set, the function block reads F0‑02 (Index 0 has been set to F0‑02 before) of the AC drive No. 3 and saves it in QW6. The fields are defined as follows: REQ: Command enable. When this field is set to 1, the function block is enabled. ●...
Page 218 MD‑SI‑DP1 Communication VALID: New data record received and valid. ● BUSY: When the value is ON, the operation is not completed. ● ERROR: Error flag. When the value is ON, an error occurs. ● STATUS: Block status or error information. ●...
Page 219: Diagnosis
MD‑SI‑DP1 Communication Note that before running an organization block, you need to download data blocks (above the function block, DB1 and DB2 in this example) to the PLC. Otherwise, an error indicating that the DB blocks are not loaded will be reported. SFB53 is used to perform operations on the EEPROM.
Page 220 MD‑SI‑DP1 Communication RET_VAL: Error code (negative) when an invocation error occurs or actual length ● of transmitted data (positive) when no error occurs. RECORD: Target area of the read diagnosis data. The value must be 9 bytes. ● Otherwise, an error is reported during invocation. The 9 bytes are defined as follows: Bytes 0–2: Station status Byte 3: Master number...
Page 221: Fault Diagnosis
MD‑SI‑DP1 Communication Fault Diagnosis 8.8.1 Troubleshooting The following table describes the faults that may occur during use of the MD‑SI‑DP1 expansion card and the AC drive. Symptom Solution 1. Check that F0‑28 is set to 1. After the AC drive is powered on, 2.
Page 222 MD‑SI‑DP1 Communication Symptom Solution 1. Check that the cable is properly connected. 2. Check the DIP switches on the PROFIBUS DP interfaces. The DIP switches on the PROFIBUS DP interfaces at both ends of the network must be set to ON, and the DIP switches on other PROFIBUS DP After the interfaces must be set to OFF.
Page 223 MD‑SI‑DP1 Communication Symptom Solution Check whether the operated address is correct. No matter whether the PPO type used contains the PKW area, the address for the read and write operations is located in the second row (also the last row). For example, if the I address and Q address in the last row of the station are both 520 to 531 (note that the I and Q addresses may start from different numbers),...
Page 224 MD‑SI‑DP1 Communication Symptom Solution 1. Disconnect the power supply, and measure the After communication is resistance between A1 and B1 of the PROFIBUS DP established, the communication is slave interface at the farthest end with a multimeter. normal when the AC drive is not The resistance should be 100±20 Ω.
Page 225 MD‑SI‑DP1 Communication Symptom Indicator※ Status Solution The master is not Blinking at 5 Hz Yellow (D3) Check the master state. running. Check that the slave The connection address is correct and the between the MD‑SI‑DP1 Yellow (D3) PROFIBUS cable is expansion card and the connected properly.
Page 226 MD‑SI‑DP1 Communication Symptom 2: The file cannot be interpreted. ● Possible cause: During the GSD file transmission, the file name is changed manually or by the transmission tool. In this case, the file name fails to meet the PROFIBUS requirements. Solution: Change the GSD file name to MD38DP2.GSD.
Page 227 MD‑SI‑DP1 Communication Possible cause: The GSD file is modified. Solution: Use a correct GSD file. Other cases ● Some versions of STEP 7 and PORTAL do not support a path that contains Chinese for installing the GSD file. In this case, store the GSD file in a path that does not contain Chinese characters.
Page 228: Ethernet/Ip Communication
V1.00.eds. Installation The MD500‑EN1 card is embedded in the MD520 series AC drive. Before installation, cut off the power supply of the AC drive and wait for about 10 minutes until the charging indicator of the AC drive becomes off. Then, insert the MD500‑EN1 card into the AC drive and fasten the screws to prevent the signal socket between boards from being damaged by the pulling force of the external signal cable.
Page 229: Interface Layout And Description
EtherNet/IP Communication Figure 9‑2 Connecting ground terminals of the MD500‑EN1 card and AC drive Interface Layout and Description " Table 9–1 " on page 229 shows the hardware layout of the MD500‑EN1 card. The pin header J7 on the back of the MD500‑EN1 card is used to connect the AC drive. The MD500‑EN1 card provides two network ports (J4 and J6) for communication with the "...
Page 230 EtherNet/IP Communication Table 9–1 Hardware description of the MD500‑EN1 card Symbol Hardware Name Function Pin header It connects to the AC drive. The MD500‑EN1 card is connected to the EtherNet/IP master using the standard Ethernet RJ45 socket (direction‑insensitive). The pin signal Network ports definitions are the same as those of the standard Ethernet pins.
Page 231: Topology
EtherNet/IP Communication State Description Indicator Solution The expansion card is in DHCP mode. D4 is steady off, and Waiting for obtaining Assign an IP address to the device by using D7 is blinking red. IP address BOOTP or DHCP. Check whether the network cable is D4 is blinking green, Connection disconnected and whether the master is...
Page 232: Protocol Description
EtherNet/IP Communication Figure 9‑5 Star topology Protocol Description 9.5.1 I/O Messages The MD500‑EN1 expansion card supports 24 I/O messages for data transmission, of which 12 are master‑to‑slave messages and 12 are slave‑to‑master messages. The I/O messages enable the master to modify and read AC drive data in real time and perform periodic data exchange.
Page 233: Data Sent By The Master
EtherNet/IP Communication AC Drive Parameters Read in AC Drive Running Frequency AC Drive State Real Time Input I/O Messages[0] Input I/O Messages[1] Input I/O Messages[2–11] 9.5.2 Data Sent by the Master The following table describes the data sent by the master. I/O Message Data Sent by the Master AC drive command word (command source set to...
Page 234: Related Parameters
EtherNet/IP Communication I/O Message Data Returned by the AC Drive AC drive running state, which is described as follows by bit: Bit0: 0: Stopped; 1: Running Bit1: 0: Running in forward direction; 1: Running in reverse direction I/O Messages 0 Bit2: 0: Not faulty;...
Page 235: Md500-En1 Card Ip Address Configuration
EtherNet/IP Communication Parameter Parameter Setpoint Description Value Range Name F0‑28 Serial 0: Modbus Select the communication protocol special protocol communication Communication card network card network bridge protocol bridge protocol as the serial communication protocol. F0‑02 0: Operating Command Set the panel source command...
Page 236 EtherNet/IP Communication Value Range Description Parameter No. Parameter Name Defines the DHCP function of the EtherNet/IP expansion card. After 0: Disabled the DHCP function is FD‑37 DHCP function 1: Enabled enabled, the following IP address configuration parameters are invalid. Defines the IP address of the Expansion card IP FD‑38 to FD‑41...
Page 237 EtherNet/IP Communication Setpoint Parameter Function Most significant byte of the FD‑46 gateway Second most significant byte FD‑47 of the gateway Third byte of the gateway FD‑48 Least significant byte of the FD‑49 gateway When the DHCP or BOOTP function is used, the MAC address of the expansion card is required.
Page 238: Parameters Related To Ac Drive Communication Card
EtherNet/IP Communication Note The expansion card implements active conflict detection upon power‑on and ● DHCP IP address assignment, and it implements passive detection at other times. If the same dynamic (static) IP address is separately assigned to two devices, which are then connected to a network, neither of the two expansion cards will report an IP address conflict.
Page 239: Communication Monitoring Parameters
EtherNet/IP Communication Parameter No. Parameter Value Range Decimal Address Name U3‑18 29458 DO control Bit0: DO1 output control Bit1: DO2 output control Bit2: Relay 1 output control Bit3: Relay 2 output control U3‑19 29459 AO1 control 0 to 7FFF, indicating 0% to 100% U3‑20 29460 AO2 control...
Page 240 EtherNet/IP Communication Parameter Parameter Name Unit Decimal Address U0‑18 28690 Pulse input 0.01 kHz frequency U0‑19 0.01 Hz 28691 Feedback speed U0‑20 Remaining running 0.1 min 28692 duration U0‑21 0.001 V 28693 AI1 voltage before correction U0‑22 0.001 V 28694 AI2 voltage before correction U0‑23...
Page 241 EtherNet/IP Communication Parameter Parameter Name Unit Decimal Address U0‑58 28730 Z signal counter U0‑59 0.01% 28731 Frequency reference U0‑60 0.01% 28732 Running frequency U0‑61 28733 AC drive state U0‑62 28734 Current fault code U0‑63 0.01% 28735 Data sent by master during point‑point communication U0‑64...
Page 242: Communication Configurations
EtherNet/IP Communication Parameter Parameter Name Unit Decimal Address U0‑87 28759 Maximum forwarding errors of EtherCAT port per unit time U0‑88 28760 Maximum error count of EtherCAT data frame processing unit per unit time 28761 U0‑89 Maximum link loss of the EtherCAT port per unit time Communication Configurations 9.7.1 Using an MD500-EN1 Expansion Card on an Allen-Bradley L16ER...
Page 243 EtherNet/IP Communication Step 1: Create a project. Open Studio 5000 and create a project. Select 1769-L16ER-BB1B under CompactLogix 5370 Controller as the controller model. ‑ ‑...
Page 244 EtherNet/IP Communication Step 2: Import the EDS file. Choose Tools > EDS Hardware Installation Tool. Click Next, and select Register an EDS file(s). ‑243‑...
Page 245 EtherNet/IP Communication Select the EDS file in your computer and click Next. Then keep clicking Next until the Finish button appears, click Finish. Step 3: Set the IP address for the expansion card. Take a static IP address as an example.
Page 246 EtherNet/IP Communication Locate EIP_Card and click Create. On the displayed configuration interface, enter the configured IP address and specify the name. ‑245‑...
Page 247 EtherNet/IP Communication Click Change, select INT from the SINT drop‑down list on the right, click OK, ignore the warning and click Yes. Choose LOGIC > Monitor Tags. ‑ ‑...
Page 248 EtherNet/IP Communication Unfold MD500:C.Data, and select Hex in the Style column. The parameters under MD500:C.Data are related to PDO mapping. Every two parameters form a group. 0–23 are I/O Messages Mapping(T‑>O), and 24–27 are I/O Messages Mapping(O‑>T). As shown in the figure, Data[0] is 0x44, and Data[1] is 0x70, indicating that TPDO1 is mapped to U0‑68.
Page 249 EtherNet/IP Communication After the configuration is complete, click the button marked with the red square in the figure below to search for the device. In this example, USB is used to connect the device. Select the device and click Download to download the code to the PLC. Step 5: Transmit data using explicit messages.
Page 250 EtherNet/IP Communication Click Create. ‑249‑...
Page 251 EtherNet/IP Communication Click ... on the right under MSG. Set the parameters according to the following figure. ‑ ‑...
Page 252 EtherNet/IP Communication Set Service Type to Get Attribute Single for reading parameters or Set Attribute Single for writing to parameters. Class is fixed to 0x93, Attribute is fixed to 0x9, and Instance is the decimal value converted from the parameter to be read. For example, FD‑13, that is, FD0D, needs to be converted to the decimal value 64781, as shown in the preceding figure.
Page 253 EtherNet/IP Communication Set FD‑37 to 1 to enable the DHCP function, power on the AC drive again, and connect the PC and AC drive to the same network. Choose BootP-DHCP Tool from the start menu, and select the network adapter. After power‑on, you can find the device request in the BootP DHCP EtherNet/IP Commissioning Tool.
Page 254: Using An Md500-En1 Expansion Card On An Inovance Am600 Master
EtherNet/IP Communication The IP address is written to the device. 9.7.2 Using an MD500-EN1 Expansion Card on an Inovance AM600 Master In this example, InoProShop V1.5.2 is used, the master is AM600, and the IP address and other information have been configured in advance according to the guide. You can use either network port on the expansion card.
Page 255 EtherNet/IP Communication Step 1: Create a project. Open InoProShop and create a project. Select the device model AM600‑CPU1608TP/ Step 2: Import the EDS file and add a slave. Click Network Configuration on the left, click the PLC, select EtherNet/IP Master, and click Import EDS File to import the EDS file for the EtherNet/IP expansion card.
Page 256: Fault Diagnosis
EtherNet/IP Communication Convert the parameter address into a decimal value and enter the value. For example, for F0‑12, enter 61452. Retain the default values for unneeded mappings. Step 4: Configure the IP address for the master. Scan the network for the master to be configured. Assign an IP address to the network port of the master.
Page 257 Check whether there is another device with the Bit2 An IP conflict occurs. same IP address as this device. The MAC address is lost or Contact Inovance for Bit1 not programed. technical support. Contact Inovance for An Ethernet hardware error Bit0 technical support.
Page 258 *19011716A00*...

Inovance MD520 Series Communications Manual

Quick Links

Troubleshooting

Need help?

Questions and answers

Related Manuals for Inovance MD520 Series

Summary of Contents for Inovance MD520 Series

Table of Contents