Improper handling might result in incorrect operation, a short life, or even a failure of this product. Keep this manual in a safe place. Related Publications Listed below are the other materials related to the use of the DeviceNet communications card "OPC-G1-DEV." Read them in conjunction with this manual as necessary. • RS-485 Communication User's Manual) •...
Page 3
Installation and wiring • Before starting installation and wiring, turn OFF the power and wait at least five minutes for inverters with a capacity of 22 kW or below, or at least ten minutes for inverters with a capacity of 30 kW or above.
Page 4
Disposal • Treat the communications card as an industrial waste when disposing of it. Otherwise injuries could occur. Others • Never modify the communications card. Doing so could cause an electric shock or injuries. Icons The following icons are used throughout this manual. This icon indicates information which, if not heeded, can result in the product not operating to full efficiency, as well as information concerning incorrect operations and settings which can result in accidents.
Table of Contents An Example of Actual I/O Communication Data ..24 Preface ..............1 Safety precautions............1 7.3.1 Extended Speed Control Instance....24 I/O Assembly Instances Assigned to Word Chapter 1 BEFORE USING THE COMMUNICATIONS Variables (For reference) ........26 CARD..............
(2) The communications card is not damaged during transportation--no defective parts, dents or warps. (3) The model name "OPC-G1-DEV" is printed on the communications card. (See Figure 2.1.) If you suspect the product is not working properly or if you have any questions about your product, contact the shop where you bought the product or your local Fuji branch office.
Screw hole (right) Positioning cutout DIP switch (SW1) Figure 2.1 Names of Parts on DeviceNet Communications Card (OPC-G1-DEV) 2.2 DIP Switch The DIP switch specifies the communication data rate (baud rate) and the node address (MAC ID) on DeviceNet. It offers a choice of three baud rates (125 kbps, 250 kbps, and 500 kbps) and a choice of node address (MAC ID) ranging from 0 to 63.
2.3 LED Status Indicators The communications card has two LED status indicators shown below. They indicate the status of the communications card. - MS (Module Status) Indicates the hardware status of the DeviceNet communications card. - NS (Network Status) Indicates the communication status on DeviceNet. The tables below show the states of the LEDs and their meanings.
Chapter 3 INSTALLATION AND REMOVAL OF THE COMMUNICATIONS CARD Before starting installation and wiring, turn OFF the power and wait at least five minutes for inverters with a capacity of 22 kW or below, or at least ten minutes for inverters with a capacity of 30 kW or above. Make sure that the LED monitor and charging lamp are turned OFF.
Page 10
Figure 3.1 In the case of 0.4 kW positioning cutout communications card over the tab on the inverter to determine the mounting position. Insert connector CN1 on the communications card into the corresponding port on the inverter's control PCB. Note: Be sure to follow the order of Inserting first lead...
(Release knob) Figure 3.3 Mounting Completed (on B-port) 3.2 Removing the Communications Card Remove the two screws that secure the communications card and pull the release knob (shown above) to take the communications card out of the inverter.
An accident could occur. 4.1 Basic Connection Diagram FRENIC-MEGA L1/R Motor L2/S L3/T OPC-G1-DEV DeviceNet DeviceNet cable terminal block CAN L DeviceNet Shield CAN H * Mounting the communications card connects to the grounding zG.
4.2 Wiring for DeviceNet Terminal Block (1) To connect the communications card to DeviceNet, use a DeviceNet thin cable complying with the DeviceNet specifications. Also observe the wiring lengths specified in the DeviceNet specifications. The recommended DeviceNet cable is TDN24U made by SWCC Showa Device Technology, Co., Ltd.
Page 14
• For inverters with a capacity of 22 kW or below * Pass the wires from the communications card between the control circuit terminal block and the front cover. In the case of 0.4 kW • For inverters with a capacity of 30 kW or above In the case of 75 kW Figure 4.4 Examples of Wiring...
Chapter 5 CONFIGURING INVERTER'S FUNCTION CODES FOR DeviceNet COMMUNICATION Before starting DeviceNet communication between the inverter equipped with the communications card and the DeviceNet master device, configure the inverter's function codes listed in Table 5.1. Table 5.2 lists other related function codes to be configured if necessary. Table 5.1 Inverter's Function Codes for DeviceNet Communication Factory Function...
Chapter 6 ESTABLISHING A DeviceNet COMMUNICATIONS LINK This chapter guides you to establish a DeviceNet communications link in I/O Message transmission between the DeviceNet master and the inverter (slave). I/O Message is a communication process that cyclically transfers data between the DeviceNet master and slave.
Chapter 7 I/O MESSAGE 7.1 Overview I/O Message is a communication process that cyclically transfers data between the DeviceNet master and the inverter. The communications card supports two types of I/O Message connections--Poll and Change-of-State connections. It also supports five types of I/O assembly instances as data formats in I/O Message, as listed in Table 7.1.
7.2 I/O Assembly Instances: Selection and Setup 7.2.1 Basic Speed Control Instance (1) Output (from master to inverter): o31=20 Instance byte bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 Fault Reset Forward (Fixed at 00) Speed Reference (lower byte) (r/min) Speed Reference (upper byte) (r/min)
7.2.2 Extended Speed Control Instance (factory default) (1) Output (from master to inverter): o31=0 or 21 Instance byte bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 NetRef NetCtrl Fault Reset Reverse Forward (Fixed at 00) Speed Reference (lower byte) (r/min) Speed Reference (upper byte) (r/min)
7.2.3 Fuji Drive Assembly Instance (1) Output (from master to inverter): o31=100 Instance byte bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 X9 * X8 * Frequency command p.u. (lower byte) Frequency command p.u. (upper byte) FWD: 1 = Run forward command REV:...
7.2.4 User Defined Assembly Instance (1) Output (from master to inverter): o31=102 User Defined Assembly Output offers a format which allows the user to freely set or modify the function code defined by the user using the function codes o40 to o43 beforehand. Four function codes are provided for the user to define.
Page 22
Even modifying S05 or S19 data reflects its change into S01 only. To monitor speed in frequency or r/min., therefore, select communication-dedicated function code M09 or M78. For details about configuring the inverter's function codes using o48 to o51, see item (3) below. Each function code defined has its own data format.
7.2.5 Access to Function Codes (1) Request for access to function codes (from master to inverter): o31=104 This instance is provided to read or write function codes from/into the inverter. Instance byte bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1...
Page 24
User-defined function code 1: Monitored data of function code specified by o48 (e.g., speed monitor M06, M09, M79. etc.) Access to function code (number): Value specified by "Request for access to function codes" instance Access to function code (group): Value specified by "Request for access to function codes" instance Access to function code (read data): Value read from the specified function code when requested read/write is normal Access to function code (error code): Error code displayed (see Table 7.3) when requested read/write is...
7.3 An Example of Actual I/O Communication Data 7.3.1 Extended Speed Control Instance Presented herein is an actual communication data in the format of Extended Speed Control Instance, the factory default format. (1) Driving pattern example Given below is an example of the driving pattern for controlling the inverter. Its corresponding I/O data is shown in (2) below.
Page 26
Request: Run reverse command. Speed command = 300 r/min (= 012Ch). The run command and speed command via DeviceNet are enabled. 62 00 2C 01 Response: Running in the reverse direction. The actual speed has reached Reference F8 04 2C 01 Request: Run reverse command.
7.4 I/O Assembly Instances Assigned to Word Variables (For reference) Some masters assign an I/O assembly instance area to a word variable. Shown below are the formats for each I/O assembly instance assigned to a word variable. For details about the definition of bits in the formats, refer to Section 7.2 "I/O Assembly Instances: Selection and Setup."...
7.4.4 User Defined Assembly Instance (1) Output (from master to inverter): o31=102 word bit 15 bit 0 User-defined function code 1 (write) (data of function code specified by o40) User-defined function code 2 (write) (data of function code specified by o41) User-defined function code 3 (write) (data of function code specified by o42) User-defined function code 4 (write) (data of function code specified by o43) (2) Input (from inverter to master): o32=103...
Differs with the product. DWord Product Name Model name OPC-G1-DEV 11 bytes (2) Motor Data object (Class 28 hex.) This object refers to and sets up the motor rated current and voltage. When Motor 2, 3, or 4 is selected, this object automatically switches to the one for Motor 2, 3, or 4.
Page 30
(3) Control Supervisor object (Class 29 hex.) This object monitors the current run command settings and the running status of the inverter, and configures the running-related settings. Instance Attribute Name Description Value (hex.) Data size Run1 Run forward command 00: OFF Byte 01: ON Run2...
Page 31
(4) AC/DC Drive object (Class 2A hex.) This object monitors the current speed command settings and the current speed of the inverter, and configures their related settings. It also monitors the output data issued from the inverter. Instance Attribute Name Description Value (hex.) Data size...
Page 32
(5) Inverter Function Code object (Class 64 hex.) This object configures or refers to inverter's function codes. Instance corresponds to function code group and Attribute, to function code number. Example: To configure F26 data, specify 04 hex for Instance and 1A hex (=26) for Attribute. Inverter's function codes have individually specified data formats.
Page 33
Instance Attribute Name Description Value (hex.) Data size 0F (15) Inverter function code y01 0 to FFFF Word (y codes) 63 hex (99) Inverter function code y99 0 to FFFF Word 10 (16) Communication function code W01 0 to FFFF Word (W codes) 63 hex (99)
8.3 Error Code List for Explicit Message Errors If an explicit message sent from the master contains any error, the communications card responds to the master with "94" in the service code and "error code" (see Table 8.1) in the data. An error code is two bytes long, consisting of a general code and additional code.
Chapter 9 INVERTER REACTION TO DeviceNet COMMUNICATIONS ERRORS Inverter's function codes o27 and o28 specify the inverter reaction to be taken after an error occurrence. Table 9.1 lists the settings for o27 and o28. The same setting can also be made by the DeviceNet variable DNFaultMode (Class: 0x29, Instance: 0x01, Attribute: 0x10).
Chapter 10 ALARM CODE LIST The information on alarms that have occurred in the inverter can be monitored through DeviceNet. They are stored in the inverter's function codes M16 to M19 as listed in Table 10.1. The communication-dedicated function codes M16 to M19 store information on the latest alarm code, last alarm code, 2nd last alarm code, and 3rd last alarm code, respectively.
Chapter 11 TROUBLESHOOTING If any problem or error occurs during DeviceNet communication, follow the troubleshooting procedures given below. Phenomenon/Symptom Probable Causes None of the LEDs on the • The communications card is not properly mounted. communications card would • The communications card is faulty. light.
319 (Fuji Electric Group) Device type AC drive (code: 2) Product code 9219 Model name OPC-G1-DEV Applicable device profile AC Drive No. of input/output bytes Selectable between 4 and 8 bytes for input and output (independently) Applicable DeviceNet CIP Specifications Volume 1, Edition 2.2 Japanese version and Volume Specifications 3, Edition 1.1 Japanese version...
Need help?
Do you have a question about the OPC-G1-DEV and is the answer not in the manual?
Questions and answers