Download Print this page

Epson EM07ZS1647F User Manual

Rc+ option fieldbus i/o.
Hide thumbs

Advertisement

EPSON RC+ Option
Fieldbus I/O
Rev.6
EM07ZS1647F

Advertisement

Troubleshooting

   Related Manuals for Epson EM07ZS1647F

   Summary of Contents for Epson EM07ZS1647F

  • Page 1

    EPSON RC+ Option Fieldbus I/O Rev.6 EM07ZS1647F...

  • Page 3

    EPSON RC+ Option Fieldbus I/O Rev.6 Copyright © 2005-2007 SEIKO EPSON CORPORATION. All rights reserved. Fieldbus I/O Rev.6...

  • Page 4

    FOREWORD This manual contains important information necessary to use the EPSON RC+ option Fieldbus I/O properly and safely. This manual is intended for personnel who perform any operations that use the pendant, such as teaching robot points. Please thoroughly read this and other related manuals before and while using the equipment.

  • Page 5

    TRADEMARKS Microsoft, Windows, and Windows logo are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. Other brand and product names are trademarks or registered trademarks of the respective holders. TRADEMARK NOTATION IN THIS MANUAL Microsoft®...

  • Page 6

    MANUFACTURER & SUPPLIER Japan & Others SUPPLIERS North & South America EPSON AMERICA, INC. Europe SEIKO EPSON CORPORATION Suwa Minami Plant Factory Automation Systems Dept. 1010 Fujimi, Fujimi-machi, Suwa-gun, Nagano, 399-0295 JAPAN : +81-266-61-1802 : +81-266-61-1846 Factory Automation/Robotics 18300 Central Avenue...

  • Page 7: Safety Precautions

    Before Reading This Manual This section describes what you should know before reading this manual. Safety Precautions Installation and transportation of robots and robotic equipment shall be performed by qualified personnel and should conform to all national and local codes. Please carefully read this manual and other related manuals before installing the robot system or before connecting cables.

  • Page 8

    Fieldbus I/O Rev.6...

  • Page 9: Table Of Contents

    1. Introduction ... 1 1.1 Overview of Fieldbus I/O... 1 1.2 DeviceNet ... 2 Overview of DeviceNet ... 2 Features of DeviceNet... 2 General Specifications... 4 1.3 PROFIBUS DP ... 5 Overview of PROFIBUS DP ... 5 Features of PROFIBUS DP ... 5 General Specifications...

  • Page 10

    2.9.4 Board Installation ... 57 2.9.5 Master Mode ... 60 2.9.6 Slave Mode ... 64 2.10 EPSON RC+ Fieldbus I/O Installation ... 67 Fieldbus I/O Software Configuration ... 67 3. Operation ... 69 3.1 Fieldbus I/O Addressing in SPEL+ ... 69 3.2 SPEL+ Fieldbus I/O Commands...

  • Page 11

    Table of Contents 5. Maintenance Parts List ... 151 Appendix A applicomIO Upgrade ... 153 Fieldbus I/O Rev.6...

  • Page 12

    Table of Contents Fieldbus I/O Rev.6...

  • Page 13: Introduction

    For each fieldbus on the RCxxx controller, there is at least one board installed. You can use more that one fieldbus type on the same controller. You can also use multiple boards for the same fieldbus type. The EPSON RC+ software key Fieldbus I/O Option must be enabled to use this option.

  • Page 14: Devicenet

    DeviceNet. Large Numbers of Inputs/Outputs For EPSON RC+ standard I/O and expansion I/O, the number of inputs/outputs is limited to 512 inputs and 512 outputs. When configuring a device to be a master of fieldbus I/O, you can control more than 16,000 total inputs and outputs.

  • Page 15

    A DeviceNet master can control up to 64 nodes (max. 2 kbytes) on one network. A PLC is typically configured as a master and controls all nodes in factory automation system, but EPSON RC+ is also capable of being a master. DeviceNet network configuration is specified by configuration management software. This software is normally provided by a master device manufacturer.

  • Page 16: General Specifications

    1. Introduction General Specifications Electrical Specifications Item Supply Voltage Power Consumption Ambient Temperature Relative Humidity DeviceNet Communication Specifications Item Supported Connection Baud Rates Transfer Distance Maximum Nodes Data Length / Frame Bus Access Error Detection Cable Communications Power Supply Voltage * When thin cable is used for trunk line, the maximum network length is 100 m.

  • Page 17: Profibus Dp

    1.3 PROFIBUS DP Overview of PROFIBUS DP PROFIBUS DP is one of fieldbus networks that provide easy interconnection between control devices (PLC, PC, sensor, actuator, etc.). PROFIBUS DP was co-developed by Siemens, Bosch, and ABB as an open communication standard to connect various field devices (sensor, actuator, robot controller, etc.). Because of the open communication standard, PROFIBUS DP can easily construct multi-vendor system with various devices developed around the world.

  • Page 18: Fieldbus I/o Rev

    PROFIBUS DP master can control up to 126 stations (max. 2 kbytes) on one network. A PLC is typically configured as a master and controls all devices in factory automation system, but EPSON RC+ is also capable of being a master. PROFIBUS DP network configuration is specified by configuration management software.

  • Page 19: General Specifications

    General Specifications Electrical Specifications Supply Voltage Power Consumption Ambient Temperature during Operation 5-40 deg C Relative Humidity during Operation PROFIBUS DP Communication Specifications Item Connection Method Baud Rates Transfer Distance Maximum Stations Data Length / Frame 244 bytes Cable Fieldbus I/O Rev.6 Item 5 V DC (supplied from a controller) 5.5 W...

  • Page 20: Ethernet/ip

    1. Introduction 1.4 EtherNet/IP Overview of EtherNet/IP EtherNet/IP is a fieldbus network that provides easy interconnection between control devices (PLC, PC, sensor, actuator, etc.). EtherNet/IP was developed by Allen-Bradley as an open communication standard to connect various field devices (sensor, actuator, robot controller, etc.). communication standard, EtherNet/IP users can easily construct a multi-vendor system with various devices developed around the world.

  • Page 21

    Large Numbers of Inputs/Outputs For EPSON RC+ standard I/O and expansion I/O, the number of inputs/outputs is limited to 512 inputs and 512 outputs. When configuring a device to be a master of fieldbus I/O, you can control more than 16,000 total inputs and outputs.

  • Page 22: General Specifications

    1. Introduction General Specifications Electrical Specifications Item Supply Voltage Power Consumption Ambient Temperature Relative Humidity EtherNet/IP Communication Specifications Item Supported Connection Baud Rates Maximum Nodes Data Length / Frame Access Control Type Cable Specification 5 V DC (supplied from a controller) 5.5 W 5-40 deg C 20-80%...

  • Page 23: Installation

    Use the configuration management software for configuring a master and slaves (scan list). For details, please refer to the configuration management software manual. To configure EPSON RC+ as a master, refer to the section 2.7 DeviceNet Board Installation later in this chapter. 9. Configure EPSON RC+.

  • Page 24: Devicenet Network Construction

    2. Installation 2.2 DeviceNet Network Construction Network Configuration A DeviceNet network is configured as shown in the following figure. Attach a terminating Ground to resistor on each end 100 Ω or less. of the trunk line. Trunk Line Trunk Line T-branch Drop Drop Line Drop...

  • Page 25

    11.2 to 12.1 mm outside diameter Shield Wire Communication Cable Signal Wire Type Signal wire Power wire Shield wire Terminating Resistor To reduce reflections of communication signal, terminating resistors should be attached on both ends of the trunk line. For DeviceNet, nodes have no terminating resistor on the ends. Attach 121 Ω...

  • Page 26

    2. Installation Maximum Network Length (Maximum Trunk Length) The maximum network length is the longest distance either between terminating resistors or between the two most distant nodes on the network. Terminating Resistor The maximum network length is restricted by the type of cable and the baud rate. Baud Rate 500 kbps 250 kbps...

  • Page 27

    Total Drop Line Length The total drop line length is the total distance of all drop lines on one network. Terminating Resistor In the figure above, the total drop line length is 17 m. The maximum total drop line length is restricted by baud rate as shown in the table below. The cable thickness is not related to the restriction.

  • Page 28

    2. Installation If the current capacity consumed on the network exceeds the restriction of cable current capacity, it is possible to install more than one power supply on the network. If you attempt to install two or more power supplies on the network, take necessary measures (pulling out a fuse on the power supply tap, etc.) to avoid conflicts between power outputs from multiple power supplies.

  • Page 29

    (2) Carefully expand the meshes of the braided shield. Under the braided shield, there is one exposed bare twisted shield wire other than the signal wires and power wires that are wrapped with aluminum tape. The shield wire is slightly harder than the mesh. (3) Cut off the expanded braided shield and remove the aluminum tape around the signal wires and power wires.

  • Page 30

    2. Installation (7) Tighten each screw securing the wires on the connector. Tighten the screw securing the wire at a correct tightening torque (0.25 to 0.3 N·m). To prevent thick cable from coming out due to cable tension, install enough thick cable length to allow for stretch.

  • Page 31: How To Setup A Profibus Dp Network

    Use the configuration management software for configuring a master and slaves (scan list). For details, please refer to the configuration management software manual. To configure EPSON RC+ as a master, refer to the section 2.8 PROFIBUS DP Board Installation later in this chapter. 8. Configure EPSON RC+.

  • Page 32: Profibus Dp Network Construction

    2. Installation 2.4 PROFIBUS DP Network Construction Network Configuration A PROFIBUS DP network is configured as shown in the following figure. Terminating Resistor ON Slave Terminating Resistor ON Slave Station There are four types of stations (devices): master, slave, repeater, and configurator. The master controls a network and gathers its slaves.

  • Page 33

    It is recommended that a 9-pin D-Sub connector be used for protecting rating IP 20. For IP 65/67, M12 connector in accordance with IEC 947-5-2, Han-Bird connector in accordance with DESINA, and Siemens hybrid connector are available. Pin assignment (9-pin D-Sub) Pin No.

  • Page 34

    2. Installation PROFIBUS DP requires approximately 1ms at 12 Mbps for the transmission of 512 bits input data and 512 bits output data distributed over 32 stations. The following figure shows typical PROFIBUS DP transmission times depending on the number of stations and baud rate. The maximum cable length is restricted by the baud rate.

  • Page 35

    Procedure for Modifying and Installing Communication Cables The following procedure explains how to modify and install a Woodhead 9-pin D-Sub connector (MA9D00-32). Follow the steps described below to modify communication cables and connect them to the connector. Be careful not to injure your hands or fingers on any sharp blades or tools used to modify the cable.

  • Page 36: How To Setup A Ethernet/ip Network

    Use the configuration management software for configuring a master and slaves (scan list). For details, please refer to the configuration management software manual. To configure EPSON RC+ as a master, refer to the section 2.9 EtherNet/IP Board Installation later in this chapter. 7. Configure EPSON RC+.

  • Page 37: Ethernet/ip Network Construction

    2.6 EtherNet/IP Network Construction Network Configuration A EtherNet/IP network is configured as shown in the following figure. Network inside the factory, etc Node There are two types of the node: master and slave. The master controls a network and gathers data from its slaves.

  • Page 38: Devicenet Board Installation

    2. Installation 2.7 DeviceNet Board Installation Following two types can be used for the fieldbus I/O option DeviceNet. - PCU-DVNIO - PCI-DVNIO 2.7.1 Board Appearance Part names and functions of the scanner board are shown in the following figure. For details of the status display LEDs (Module/NetWork LED and IO LED), refer to the 4. Troubleshooting in this manual.

  • Page 39: Specifications

    2.7.2 Specifications Part Number Modes Baud rates Interface Supported Devices Maximum Nodes Connection Types Explicit Messaging EDS Support Input Data Size Output Data Size Automatic Detection 2.7.3 Software Installation Before installing any boards in your controller, you must install the applicomIO console application and drivers for the type of board you will be using.

  • Page 40

    2. Installation (6) Allow the default components to be installed. (7) Select the protocol: DeviceNet you will be using. If you also use PROFIBUS DP, select Profibus-DP as well. Select which type of device data files to install (EDS for DeviceNet, GSD for PROFIBUS DP).

  • Page 41: Board Installation

    2.7.4 Board Installation Make sure that the power is turned OFF before installing/removing any boards or connecting/disconnecting any cables. connecting/disconnecting any cables with the power ON is extremely hazardous WARNING and may result in electric shock and/or malfunction of equipment. (1) Configure the board address jumper (JP1) on each board.

  • Page 42

    2. Installation is shown in the Board Type: box. Then, click the OK button. When installing more than two fieldbus boards in the system, add all the boards using this dialog. The following dialog will appear when no board is detected. Ensure that the board is correctly inserted and that the board configuration is correct.

  • Page 43: Master Mode

    2.7.5 Master Mode (1) Ensure that the board is connected to the fieldbus. Then, start the applicomIO console application. (2) Register the device information (EDS file) that is necessary for the network setup. Select the [Equipment Library] tab at the center of the dialog’s right side and click the Add icon.

  • Page 44

    2. Installation (6) Configure the baud rate, MAC ID (master address), and so on for the DeviceNet network. The load on a bus can be controlled by the baud rate and interscan delay settings. NOTE When the load exceeds 60%, the DeviceNet network communication will be unstable, for example: more communication errors.

  • Page 45

    (9) Drag each device you want to scan from the Network Detection tab to the Master item in the list on the right. (10) The following dialog will appear. Select the Connection Configuration tab to verify the connection configuration. Change the configuration if necessary. NOTE Not every slave device supports all connection types.

  • Page 46

    2. Installation The Expert Mode button will appear when the applicomIO Console application is used in the expert mode. To configure details of “Change Of State” and “Cyclic”, click the Expert Mode button and display the Expert Mode dialog. NOTE Never disable Ack.

  • Page 47

    To create a new EDS file based on the data from the device, click the Create New EDS File button. When a new EDS file is created, the following dialog will appear to verify the contents of the file. (12) Select the Equipment Library tab on the center left of the console window and click the Add button to register the new EDS file in the system.

  • Page 48

    2. Installation (13) Select File | Download in Flash to register the configuration in the fieldbus board. After a few seconds, the board's state will show green in the status bar. (14) Now, the fieldbus board is ready to operate as a master. Close the applicomIO Console application.

  • Page 49: Slave Mode

    2.7.6 Slave Mode (1) Ensure that the board is connected to the fieldbus. Then, start the applicomIO console application. (2) Click on the “Protocol list” under the board that was just added. (3) Select Protocol | Properties. (4) Configure the baud rate, MAC ID (slave address), and so on for the DeviceNet network.

  • Page 50

    2. Installation (6) The DeviceNet Local Slave property sheet will appear. Select the Equipment (device) ID. It must be the same number as the Master ID in step (4). (7) Click on the Connection Configuration tab. Check the Polling check box and configure how many inputs and outputs for the slave device.

  • Page 51

    (9) Select File | Download in Flash to register the configuration in the fieldbus board. After a few seconds, the board's state will show green in the status bar. (10) Close the applicomIO console application. (11) The default slave EDS file is created. The path is: C:\Program Files\Woodhead\Direct-link\ApplicomIO2.3\ConfigIO \Config01\applicomio.eds.

  • Page 52

    2. Installation EDS File Generated by applicomIO® Console Version : 2.2 [File] [Device] [IO_Info] Copy the EDS file to the system where the master is located. Add the new slave device to the master using the new EDS file. (12) On the master system, scan the network for new devices. The new slave device should be detected.

  • Page 53: Profibus Dp Board Installation

    2.8 PROFIBUS DP Board Installation Following two board types can be used for the fieldbus I/O option PROFIBUS DP. - PCU-DPIO - PCI-DPIO 2.8.1 Board Appearance Part names and functions of the scanner board are shown in the following figure. For details of the status display LEDs, refer to the 4.

  • Page 54: Specifications

    2. Installation 2.8.2 Specifications Part Number Modes Baud Rates Interface Output Current Capacity Supported Devices Maximum Stations GDS Support PROFIBUS DP Class 1 PROFIBUS DP Class 2 Input Data Size Output Data Size Automatic Detection 2.8.3 Software Installation Before installing any boards in your controller, you must install the applicomIO console application and drivers for the type of board you will be using.

  • Page 55

    (6) Allow the default components to be installed. (7) Select the protocol: PROFIBUS DP you will be using. If you also use DeviceNet, select DeviceNet as well. Select which type of device data files to install (GSD for PROFIBUS DP, EDS for DeviceNet). (8) Complete the installation.

  • Page 56: Board Installation

    2. Installation 2.8.4 Board Installation Make sure that the power is turned OFF before installing/removing any boards or connecting/disconnecting any cables. connecting/disconnecting any cables with the power ON is extremely hazardous WARNING and may result in electric shock and/or malfunction of equipment. (1) Configure the board address jumper (JP1) on each board.

  • Page 57

    (8) The following dialog will appear. Check that “PCI-DPIO” or “PCU-DPIO” (“PCI-DVNIO” in case of DeviceNet) is shown in the Board Type: box. Then, click the OK button. When installing more than two fieldbus boards in the system, add all the boards using this dialog.

  • Page 58: Master Mode

    2. Installation 2.8.5 Master Mode (1) Ensure that the board is connected to the fieldbus. Then, start the applicomIO console application. (2) Register the device information (GSD file) that is necessary for the network setup. Select the [Equipment Library] tab at the center of the dialog’s right side and click the Add icon.

  • Page 59

    (5) Select the “Profibus, Master/Slave” in the Channel Properties dialog and click the OK button. (6) Click on the “Protocol list” under the board that was just added. (7) Select Protocol | Properties. (8) Configure the baud rate, Master Profibus Address (master address), number of repeaters, and so on for the PROFIBUS DP network.

  • Page 60

    2. Installation (9) Click the Network Detection tab on the center left of the console window. (10) Click the Read Network Configuration button to display the Network Detection dialog and read in the devices on the fieldbus. (11) Drag each device you want to scan from the Network Detection tab to the Master item in the list on the right.

  • Page 61

    2. Installation (12) The following dialog will appear. The device name is shown on the dialog title bar. Click the OK button. When the system cannot identify the device you want to use (its GSD file is not registered), the following dialog will appear. In this case, obtain the GSD file from the device manufacturer and register it.

  • Page 62

    2. Installation (13) Select the Equipment Library tab on the center left of the console window and click the Add button to register the new GSD file in the system. (14) Select File | Download in Flash to register the configuration in the fieldbus board. After a few seconds, the board's state will show green in the status bar.

  • Page 63: Slave Mode

    2.8.6 Slave Mode (1) Ensure that the board is connected to the fieldbus. Then, start the applicomIO console application. (2) Select Description | Properties. (3) Select the “Profibus, Slave” in the Cannel Properties dialog and click the OK button. NOTE Though you can select the “Profibus, Master/Slave”...

  • Page 64

    2. Installation (6) Configure the baud rate, Master Profibus Address (slave address), number of repeaters, and so on for the PROFIBUS DP network. In this example, the Master Profibus Address (slave address) is set to 005. NOTE Specify an unused address on the network for a slave device as well as other devices. (7) Double-click the “Local DP Slave”...

  • Page 65: Gsd File

    For details of the PROFIBUS DP network configuration, contact the manufacturer of the master device you use. If you use EPSON RC+ as a master device, you do not need to register EPSON RC+ since the said GSD file was installed.

  • Page 66: Devicenet Board Installation

    2. Installation 2.9 EtherNet/IP Board Installation Following two board types can be used for the fieldbus I/O option EtherNet/IP. - PCU-ETHIO 2.9.1 Board Appearance Part names and functions of the scanner board are shown in the following figure. For details of the status display LEDs, refer to the 4.

  • Page 67: Software Installation

    2.9.3 Software Installation Before installing any boards in your controller, you must install the applicomIO console application and drivers for the type of board you will be using. (1) Start the controller. (2) Run the C:\Install\FieldBus\Install\applicomIO\Disk1\Setup.EXE from the install folder in the controller to start the installation. (3) Select the desired language for the installer.

  • Page 68

    2. Installation (7) Select the protocol: Ethernet you will be using. If you also use DeviceNet, select DeviceNet as well. If you also use PROFIBUS DP, select Profibus-DP as well. Select which type of device data files to install (GSD for PROFIBUS DP, EDS for DeviceNet).

  • Page 69: Board Installation

    2.9.4 Board Installation Make sure that the power is turned OFF before installing/removing any boards or connecting/disconnecting any cables. connecting/disconnecting any cables with the power ON is extremely hazardous WARNING and may result in electric shock and/or malfunction of equipment. (1) Configure the board address jumper (JP1) on each board.

  • Page 70

    2. Installation (8) The following dialog will appear. Check that “PCI/PCU-ETHIO (“PCI-DVNIO” in case of DeviceNet, and ”“PCI- DPIO” or “PCU-DPIO” in case of PROFIBUS-DP) is shown in the Board Type: box. Then, click the OK button. When installing more than two fieldbus boards in the system, add all the boards using this dialog.

  • Page 71

    (10) Click the OK button. The following dialog will appear. Configure the IP address for the EtherNet/IP board. Select the IP address from Static, DHCP, or BOOTP at Configuration. Do not select Flash Memory. When you select Static, set the values for each item. (11) After all the boards are added, the system should be restarted.

  • Page 72: Master Mode

    2. Installation 2.9.5 Master Mode (1) Ensure that the board is connected to the fieldbus. Then, start the applicomIO console application. (2) Register the device information (EDS file) that is necessary for the network setup. Select the [Equipment Library] tab at the center of the dialog’s right side and click the Add icon.

  • Page 73

    (3)-3 Check the device information in EDS, and click the Next button. (3)-4 Click the Complete button to register the EDS file. (4) Click the Network Detection tab on the center left of the console window. (5) Click the Read Network Configuration button to display the Network Detection dialog and read in the devices on the fieldbus.

  • Page 74

    2. Installation (6) Drag each device you want to scan from the Network Detection tab to the Master item in the list on the right. (7) Following dialog appears. Uncheck the Link Parameter box and assign a value from 1 to 127. This number is called as device ID and necessary to create SPEL+ programs.

  • Page 75

    2. Installation After a few seconds, the board's state will show green in the status bar. Now, the fieldbus board is ready to operate as a master. Close the applicomIO Console application. Fieldbus I/O Rev.6...

  • Page 76: Slave Mode

    [Output]-[Instance] : 001 [Output]-[Size] [Input]-[Instance] [Input]-[Size] Value of Configuration | Size is not available for EPSON RC+. Set “0” (Words) for this box. NOTE Make sure that the input/output size settings do not exceed 14 kbytes in total. The input/output sizes of each node may be restricted depending on the master.

  • Page 77

    (6) Drag EtherNet/IP Local Slave from Equipment Library to the Master item in the list on the right. Window in step 5 appears. Configure by the procedures from step 7. You can create up to 32 Local Slaves if necessary. (7) Select File | Download in Flash to register the configuration in the fieldbus board.

  • Page 78

    2. Installation (9) The default slave EDS file is created. The path is: C:\Program Files\Woodhead\Direct-link\ApplicomIO2.3\ConfigIO \Config01\applicomio.eds. You may make a copy of the default slave EDS file and modify it to create your original EDS file if necessary. Edit the copy of the slave EDS file using Notepad. You may want to change the VendName and ProductTypeStr.

  • Page 79: Epson Rc+ Fieldbus I/o Installation

    Read Configuration Use this button to read the Fieldbus configuration for the selected Before continuing, you must click the Read Configuration button for each bus. This instructs EPSON RC+ to read the device configurations. If the configuration for a board is ever changed, you must Read Configuration again.

  • Page 80

    2. Installation Fieldbus I/O Rev.6...

  • Page 81: Operation

    NOTE scan rate, number and types of devices, number of SPEL+ tasks, communication error, etc. When the fastest and most consistent response times are required, please use EPSON Standard digital I/O, which incorporates interrupt driven inputs and outputs. Fieldbus I/O Rev.6 Returns the status of the specified fieldbus.

  • Page 82: Outputs Off By Emergency Stop And Reset Instruction

    Reset instruction is executed. For details of the configuration, refer to the chapter SPEL+ Options in the EPSON RC+ User's Guide. A command that was issued just before an emergency stop can be executed after the NOTE emergency stop condition is cleared.

  • Page 83: Using Fbusio_sendmsg

    3.5 Using FbusIO_SendMsg FbusIO_SendMsg is used to send an explicit message to a device and return a reply. This command operates according to the protocol. The syntax is as follows: FbusIO_SendMsg bus, device, msgParam, sendBytes(), recvBytes() There are two arrays passed to the function. The sendData array contains the data that is sent to the device in bytes.

  • Page 84: Using Slave Mode

    3. Operation 3.6 Using Slave Mode In slave mode, the EPSON RC+ system is a slave on the bus. Outputs from the master are inputs in EPSON RC+, and inputs to the master are outputs in EPSON RC+. Uses for slave mode: •...

  • Page 85: Devices Available For Fieldbus I/o Option

    TDN-8C0-108 Woodhead TDN-808-118 Woodhead 750-346 WAGO 750-431 WAGO 750-530 WAGO 42GNP-9000-QD1 Allen-Bradley JUSP-NS300 YASKAWA ELECTRIC SGDH YASKAWA ELECTRIC RC170 SEIKO EPSON Model Number TDP-8C0-B18-02 Woodhead TDN-808-B18-02 Woodhead 750-343 WAGO 750-431 WAGO 750-530 WAGO JUSP-NS500 YASKAWA ELECTRIC SGDH YASKAWA ELECTRIC RC170 SEIKO EPSON 3.

  • Page 86: Fieldbus I/o Response Performance

    3. Operation 3.9 Fieldbus I/O Response Performance As mentioned previously, respond times for fieldbus I/O can vary and depend on several factors. The values in this section are shown for reference not for guaranteed performance. DeviceNet Test Environment Evaluation Result RC520 Controller: Pentium III 850 MHz 128 MB memory Fieldbus I/O: PCI-DVNIO board Master (MAC ID: 0)

  • Page 87: Profibus Dp

    PROFIBUS DP Test Environment Terminating Resistor Evaluation Result Fieldbus I/O Rev.6 RC520 Controller: Pentium III 850 MHz 128 MB memory Fieldbus I/O: PCI-DPIO board Master (station address: 0) Baud rate: 12 Mbps, 9.6 kbps Connected Slave: Woodhead 16-inpout module (TDP-8C0-B18-02) Node address: 2 Connection Image Power Supply...

  • Page 88

    3. Operation Fieldbus I/O Rev.6...

  • Page 89: Troubleshooting

    4. Troubleshooting 4.1 DeviceNet Troubleshooting Exclusion Every system has its special environment, conditions, specifications, and usages. This guide is provided as a general reference for troubleshooting a DeviceNet network. Every effort has been made to ensure the information is accurate. However, we do not guarantee the complete accuracy of the information and thus we decline any liability for damages or costs incurred by the use of this troubleshooting.

  • Page 90: Examining A Problem

    4. Troubleshooting (DeviceNet) 4.1.1 Examining a Problem 4.1.1.1 Scanner Board Diagnostic LEDs The DeviceNet board used with EPSON RC+ has two status display LEDs. The layout of the LEDs is shown in the following figure. PCU-DVNIO 4-pin Terminal Watchdog Port (Do not use this port.)

  • Page 91

    4.1.1.2 Check Network Status (1) Master Status: MS/NS LEDs MS (Module Status) NS (Network Status) (2) Node Number of Absent Slaves Absent slaves are disconnected from or not added to the network. 1. See the status flag regarding to the removal and addition if the master has status information.

  • Page 92: Problems And Countermeasures

    Refer to the respective device manuals. [Refer to the section 4.1.2.4 Master: Configuration Error.] When EPSON RC+ was configured as a master: - Slave disconnected from the network (Remote I/O communication error) - Slave not added to the network (Scan list collation...

  • Page 93

    ♦ Process Flowchart Master LED Examining a MS: Green ON NS: Red Blinking trouble. See 4.1.1. Examining Details of Trouble. MS: Green ON NS: Red ON MS: Green ON NS: OFF MS: Red Blinking MS: OFF NS: Green Blinking MS: OFF NS: OFF MS: Red ON Other...

  • Page 94

    4. Troubleshooting (DeviceNet) 4.1.2.1 Master: Communication Error Master Unit LED Green Light ON 4.1.2.1.1 Slave: Not Operating Master LED Condition Absent Slave LED Condition ♦ Process Flowchart Check No Problem Is power supplied to slaves? Replace the unit. Error Red Light Communication - Slave disconnected from the network Blinking...

  • Page 95

    ♦ Causes of Error Possible Cause Slave power OFF Broken unit 4.1.2.1.2 Slave: Communication Error Detection / Busoff Detection / Not-added Master LED Condition (1) Absent Slave LED Condition (Communication error detection) (2) Absent Slave LED Condition (Busoff detection) (3) Absent Slave LED Condition (Slave not added to the network) Fieldbus I/O Rev.6 4.

  • Page 96

    4. Troubleshooting (DeviceNet) ♦ Process Flowchart Check - Unconnected terminating resistor No Problem - Unconnected or loose connector/signal wire No Problem communications power supply. No Change No Change (Replace deteriorated cable). Check for noise influence. No Change The trouble unit is not found. Rarely Does an error occur immediately? Divide the network and...

  • Page 97

    ♦ Causes of Error Possible Cause Disconnected terminating resistors Cable disconnection Disconnected connector Disconnected signal wire Loose connector Loose signal wire Voltage drop of communications power supply Noise (external cause) Broken unit No cause is identified. Fieldbus I/O Rev.6 4. Troubleshooting (DeviceNet) Examination Method (1) Check that terminating resistors are connected to...

  • Page 98

    4. Troubleshooting (DeviceNet) 4.1.2.2 Master: Busoff Detection Master Unit LED Green Light ON Error Red Light Busoff detection Duplicate MAC ID Description Communication stopped due to critical error. The MAC ID configuration was duplicated. (This error occurs only during unit start-up) Fieldbus I/O Rev.6...

  • Page 99

    ♦ Process Flowchart Check - Unconnected terminating resistor - Unconnected or loose connector/signal wire No Problem No Problem communications power supply. No Change No Change (Replace deteriorated cable). Check for noise influence. No Change The trouble unit is not found. Rarely Does an error occur immediately? Divide the network and...

  • Page 100

    4. Troubleshooting (DeviceNet) ♦ Causes of Error Possible Cause Disconnected terminating resistors Cable disconnection Disconnected connector Disconnected signal wire Loose connector Loose signal wire Voltage drop of communications power supply Noise (external cause) Broken unit No cause is identified. Examination Method (1) Check that terminating resistors are connected to both ends of the network.

  • Page 101

    4.1.2.3 Master: Unestablished Communication Master Unit LED Green Light ON ♦ Process Flowchart Check No Problem communications power supply - Unconnected terminating resistor No Problem - Unconnected or loose connector/signal wire Check that power is supplied to all slaves. No Problem Check for master unit configuration.

  • Page 102

    (2) Check that the configuration data were written in flash. For details, refer to the section 4.1.3.6 EPSON RC+ Master Configuration. Countermeasure Check voltage of the power supply. Fix the problem. How to find the trouble...

  • Page 103

    4.1.2.4 Master: Configuration Error Master Unit LED Light Blinking Fieldbus I/O Rev.6 Error Configuration error Matter Slave error detection 4. Troubleshooting (DeviceNet) Description - Slave disconnected from the network (Remote I/O communication error) - Slave not added to the network (Scan list collation error) - Duplicate MAC ID: The MAC ID configuration was duplicated.

  • Page 104

    4. Troubleshooting (DeviceNet) ♦ Process Flowchart Check configuration (scan list configuration). No Problem - Unconnected terminating resistor - Unconnected or loose connector/signal wire No Problem communications power supply. No Problem No Change (Replace deteriorated cable). No Change No Change The trouble unit is not found. Rarely Does an error occur immediately? Analyze the network with NetMeter.

  • Page 105

    (2) Check that the configuration data were written in flash. (3) Check that the network load is within allowable range. For details, refer to the section 4.1.3.6 EPSON RC+ Master Configuration. (1) Check that terminating resistors are connected to both ends of the network.

  • Page 106

    4. Troubleshooting (DeviceNet) 4.1.2.5 Absent Slave Master Unit LED Light ♦ Process Flowchart Check No Problem communications power supply - Unconnected terminating resistor No Problem - Unconnected or loose connector/signal wire Check that power is supplied to all slaves. No Problem Check for master unit configuration.

  • Page 107

    (2) Check that the configuration data were written in flash. For details, refer to the section 4.1.3.6 EPSON RC+ Master Configuration. Countermeasure Check voltage of the power supply. Fix the problem. How to find the trouble...

  • Page 108

    4. Troubleshooting (DeviceNet) 4.1.2.6 Uninitialized Network Master Unit LED Light OFF Light OFF Uninitialized network ♦ Process Flowchart Check No Problem communications power supply - Unconnected terminating resistor No Problem - Unconnected or loose connector/signal wire Check that power is supplied to all slaves. No Problem Check for master unit configuration.

  • Page 109

    (2) Check that the configuration data were written in flash. For details, refer to the section 4.1.3.6 EPSON RC+ Master Configuration. Countermeasure Check voltage of the power supply. Fix the problem.

  • Page 110: Procedures For Examining Possible Causes

    4. Troubleshooting (DeviceNet) 4.1.3 Procedures for Examining Possible Causes 4.1.3.1 Connection Problem (Disconnected Terminating Resistors, Cable Disconnection, Disconnected Connector, Disconnected Signal Wire) (1) Ensure that two terminating resistors are connected to both ends of the network. (2) Turn OFF the communications power supply. (3) Measure resistance between CAN_H and CAN_L wires of the absent slave using the tester.

  • Page 111

    ♦ Process Flowchart Check for cable laying. Check that Problem exists. terminating resistors (Add terminating resistors.) are connected. Normal Turn OFF communications power supply. Out of 50 to 70 Ω (Error) Measure resistance with tester. 50 to 70 Ω Normal See 4.1.3.2.

  • Page 112

    4. Troubleshooting (DeviceNet) 4.1.3.2 Loose Connector and Signal Wire Check for the connections of the following parts on the connector and cable. (1) Crimp Terminal (2) Connection of connector and signal wire (3) Connection of connector and unit (T-branch tap) Connector on the node (mask) side Screw...

  • Page 113

    4.1.3.3 Noise Intrusion Verify how an error occurrence condition changes while taking the following countermeasures. ♦ Ground of FG (DRAIN) wire Normal Grounding: Ground the DeviceNet network at only one point. Power Supply Tap CAN H Shield (S) CAN L Communications Countermeasure 1: Disconnect the wire between V- and FG.

  • Page 114

    4. Troubleshooting (DeviceNet) Countermeasure 2: Disconnect the shield wire to isolate it from the ground. When noise intrudes the ground line because a noise source such as an inverter is installed near the communications power supply, disconnect the shield wire of the communication cable and isolate it from the ground to restrain noise intrusion.

  • Page 115

    ♦ Communications Power Supply When sharing one power source with the communications power supply and I/O devices, provide respective power sources separately. Separating power source prevents noise caused by I/O device operations from affecting communication. Communications Power Supply 24V Disconnect I/O devices from the communications power supply. Fieldbus I/O Rev.6 4.

  • Page 116

    4. Troubleshooting (DeviceNet) 4.1.3.4 Broken Unit Examination (Dividing Network Examination) When you cannot quickly find the trouble point due to a broken unit, connection failure including loose connector, or cable partial disconnection, divide the network to find the trouble point. Verify how error occurrence conditions change while taking the following countermeasures.

  • Page 117

    (2) Separate each slave from the network Check for each slave. The trouble point is where error condition changes into normal condition. Master Branch Tap Communications Power Supply 4.1.3.5 Network Configuration and Specifications (1) Maximum Network Length and Drop Line Length Check that the cables used on the network meet the following specifications.

  • Page 118

    4. Troubleshooting (DeviceNet) 4.1.3.6 EPSON RC+ Master Configuration For details of EPSON RC+ master configuration, refer to the section 2.5 DeviceNet Board Installation. The following section describes the procedure for verifying the scanner board condition with applicomIO Console application. 4.1.3.6.1 Verifying applicomIO Console application condition The status bar at the bottom of the window shows the applicomIO Console application status.

  • Page 119

    When the load exceeds 60%, the DeviceNet network communication will be unstable. (For example, more communication errors) For the procedure for master configuration, refer to respective master device manuals. For EPSON RC+ master configuration, refer to the section 2.5.5 Master Mode. Fieldbus I/O Rev.6...

  • Page 120

    4. Troubleshooting (DeviceNet) (2) Select the DeviceNet (Scanner) tab. The window changes as shown below. The scanner board status is shown in the “Code No. => Comment” form. The code numbers are shown in the following table. MAC ID : MAC ID specified for the scanner board Module/NetWork LED IO LED : Module Status (MS) LED status...

  • Page 121

    Fieldbus I/O Rev.6 Status Code General Protocol Non-resident dialogue software. Additional information: Initialize the applicomIO® interface before use by running the PcInitIO Targeted applicomIO® card invalid or incorrectly initialized by the function IO_Init Synchronization problem on the line. Additional information: The DeviceNet master is "off line"...

  • Page 122

    4. Troubleshooting (DeviceNet) (3) When you click the I/O button on the upper left of the window, the window changes as shown below. Each slave device status is shown in the right side of the window. A green circle indicates that the communication of the corresponding device is normal, and a red circle indicates that there is a communication error.

  • Page 123: Profibus Dp Troubleshooting

    4.2 PROFIBUS DP Troubleshooting Exclusion Every system has its special environment, conditions, specifications, and usages. This guide is provided as general reference for troubleshooting a PROFIBUS DP network. Every effort has been made to ensure the information is accurate. However, we do not guarantee the complete accuracy of the information and thus we decline any liability for damages or costs incurred by the use of this troubleshooting.

  • Page 124: Examining A Problem

    4. Troubleshooting (PROFIBUS DP) 4.2.1 Examining a Problem 4.2.1.1 Scanner Board Diagnostic LEDs The PROFIBUS DP board used with EPSON RC+ has two status display LEDs. The layout of the LEDs is shown in the following figure. PCU-DPIO 4-pin Terminal Watchdog Port (Do not use this port.)

  • Page 125

    First of all, you should check the current condition of the network. There are different specifications of status display LED on a device in the PROFIBUS DP standard. This section explains how to check the network status assuming that EPSON RC+ is configured as a master or slave.

  • Page 126: Problems And Countermeasures

    4. Troubleshooting (PROFIBUS DP) 4.2.2 Problems and Countermeasures Master Unit LED Light Light Light Light Light Light ON Error Green Normal - Normal condition Light communication Blinking Green Ready for - Normal condition Light ON communication [Refer to the section 4.2.2.1 Master Communication Communication Error.] Light...

  • Page 127

    ♦ Process Flowchart Master LED BF: OFF Examining a ST: Red Blinking trouble. See 4.2.1 Examining Details of Trouble. BF: OFF ST: Red ON BF: OFF ST: OFF BF: Red ON Other Fieldbus I/O Rev.6 4. Troubleshooting (PROFIBUS DP) Absent Slave LED BF: OFF ST: Green ON BF: OFF...

  • Page 128

    4. Troubleshooting (PROFIBUS DP) 4.2.2.1 Master: Communication Error Master Unit LED Light 4.2.2.1.1 Master/Slave: Communication Error Master LED Condition Absent Slave LED Condition (Communication error) Error Communication - Slave disconnected from the network Light error (Remote I/O communication error) - Slave not added to the network (Scan list Blinking collation error) - Nonstandard wiring...

  • Page 129

    ♦ Process Flowchart Check - Unconnected terminating resistor No Problem - Unconnected or loose connector/signal wire No Problem No Change No Change (Replace deteriorated cable). Check for noise influence. No Change The trouble unit is not found. Rarely Does an error occur immediately? Consult the PROFIBUS manufacturer.

  • Page 130

    4. Troubleshooting (PROFIBUS DP) ♦ Causes of Error Possible Cause Disconnected terminating resistors Cable disconnection Disconnected connector Disconnected signal wire Loose connector Loose signal wire Electrical surges of device power supply Noise (external cause) Broken unit No cause is identified. Examination Method (1) Check that terminating resistors are connected to...

  • Page 131

    4.2.2.1.2 Slave: Data Link Error Master LED Condition Absent Slave LED Condition (Data link error) ♦ Process Flowchart Check - Unconnected terminating resistor No Problem - Unconnected or loose connector/signal wire No Change (Replace deteriorated cable). No Change Check for noise influence. The trouble unit is not found.

  • Page 132

    4. Troubleshooting (PROFIBUS DP) ♦ Causes of Error Possible Cause Disconnected terminating resistors Cable disconnection Disconnected connector Disconnected signal wire Loose connector Loose signal wire Noise (external cause) Broken unit No cause is identified. Examination Method (1) Check that terminating resistors are connected to both ends of the network.

  • Page 133

    4.2.2.1.3 Slave: Uninitialized Network Master LED Condition Absent Slave LED Condition (Uninitialized Network) ♦ Process Flowchart Check Measure voltage of all No Problem slave power supplies. Check the following: - Unconnected terminating resistor No Problem - Unconnected or loose connector/signal wire - Cable disconnection Replace moving cable.

  • Page 134

    4. Troubleshooting (PROFIBUS DP) ♦ Causes of Error Possible Cause Electrical surges of device power supply Disconnected terminating resistors Cable disconnection Disconnected connector Disconnected signal wire Loose connector Loose signal wire Broken unit Examination Method Measure voltage of device power supply at the trouble unit.

  • Page 135

    4.2. 2.1.4 Slave: Physical Error Master LED Condition Absent Slave LED Condition (Physical error) ♦ Process Flowchart Check Measure voltage of all No Problem slave power supplies. Normal Communication? Consult the PROFIBUS manufacturer. ♦ Causes of Error Possible Cause Electrical surges of device power supply Broken unit...

  • Page 136

    4. Troubleshooting (PROFIBUS DP) 4.2.2.2 Master: Data Link Layer Error Master Unit LED Light ♦ Process Flowchart Check - Unconnected terminating resistor No Problem - Unconnected or loose connector/signal wire No Change (Replace deteriorated cable). No Change The trouble unit is not found. Rarely Does an error occur immediately? Consult the PROFIBUS manufacturer.

  • Page 137

    ♦ Causes of Error Possible Cause Disconnected terminating resistors Cable disconnection Disconnected connector Disconnected signal wire Loose connector Loose signal wire Noise (external cause) Broken unit No cause is identified. Fieldbus I/O Rev.6 4. Troubleshooting (PROFIBUS DP) Examination Method (1) Check that terminating resistors are connected to both ends of the network.

  • Page 138

    4. Troubleshooting (PROFIBUS DP) 4.2.2.3 Master: Uninitialized Network Master Unit LED Light ♦ Process Flowchart Check No Problem Check for master device configuration. No Problem Consult the PROFIBUS manufacturer. Error Light Uninitialized network Problem exists. (Fix it.) Measure voltage of all slave power supplies.

  • Page 139

    ♦ Causes of Error Possible Cause Electrical surges of master device power supply Master device configuration error Broken master unit Fieldbus I/O Rev.6 4. Troubleshooting (PROFIBUS DP) Examination Method Measure voltage of device power supply at the master unit. → It should be within the range of sufficient voltage for device operation.

  • Page 140

    4. Troubleshooting (PROFIBUS DP) 4.2.2.4 Master: Configuration Error Master Unit LED Red Light ♦ Process Flowchart Check - Unconnected terminating resistor No Problem - Unconnected or loose connector/signal wire No Change The trouble unit is not found. Rarely Does an error occur immediately? Consult the PROFIBUS manufacturer.

  • Page 141

    ♦ Causes of Error Possible Cause Disconnected terminating resistors Cable disconnection Disconnected connector Disconnected signal wire Loose connector Loose signal wire Broken unit No cause is identified. Fieldbus I/O Rev.6 4. Troubleshooting (PROFIBUS DP) Examination Method (1) Check that terminating resistors are connected to both ends of the network.

  • Page 142: Procedures For Examining Possible Causes

    4. Troubleshooting (PROFIBUS DP) 4.2.3 Procedures for Examining Possible Causes 4.2.3.1 Connection Problem (Disconnected Terminating Resistors, Cable Disconnection, Disconnected Connector, Disconnected Signal Wire) (1) Ensure that two terminating resistors are connected to both ends of the network. (2) Turn OFF all device power supplies. (3) Measure resistance between A1 and B1 wires of the absent slave using the tester.

  • Page 143

    ♦ Process Flowchart Check for cable laying. Check that Problem exists. terminating resistors (Add terminating resistors.) are connected. Normal Turn OFF all units. Out of 100 to 120 Ω (Error) Measure resistance with tester. 100 to 120 Ω Normal See 4.2.3.2. Approx.

  • Page 144

    4. Troubleshooting (PROFIBUS DP) 4.2.3.2 Loose Connector and Signal Wire Check for the connections of the following parts on the connector and cable. (1) Connection of connector and signal wire (2) Connection of connector and unit 4.2.3.3 Noise Intrusion Verify how error occurrence condition changes while taking the following countermeasures. ♦...

  • Page 145

    Countermeasure 1: Improve FG. Grounding Screw Slave Device Countermeasure 2: Disconnect the FG wire to isolate it from the ground. When noise intrudes the ground line because a noise source such as an inverter is installed near the grounding point, disconnect the shield wire of the signal cable and isolate it from the ground to restrain noise intrusion.

  • Page 146

    4. Troubleshooting (PROFIBUS DP) 4.2.3.4 Broken Unit Examination (Dividing Network Examination) When you cannot quickly find the trouble point due to broken unit, connection failure including loose connector, or cable partial disconnection, divide the network to find the trouble point. Verify how error occurrence conditions change while taking the following countermeasures.

  • Page 147

    4.2.3.5 Network Configuration and Specifications (1) Maximum Cable Length Check that the cables used on the network meet the following specifications. Baud Rates 12 Mbps 6 Mbps 3 Mbps 1500 kbps 500 kbps 187.5 kbps 93.75 kbps 19.2 kbps 9.6 kbps (2) Terminating Resistor Ensure that two terminating resistors are connected to both ends of the network.

  • Page 148

    4. Troubleshooting (PROFIBUS DP) 4.2.3.6 EPSON RC+ Master Configuration For details of EPSON RC+ master configuration, refer to the section 2.6 PROFIBUS DP Board Installation. The following section describes the procedure for verifying the scanner board condition with the applicomIO Console application.

  • Page 149

    4.2.3.6.2 Verifying the PROFIBUS DP network condition The applicomIO Console application has the following functions: Network Monitor function: Monitoring error condition detected on the Diagnostic function: (1) Select the Network Detection tab in the left center of the applicomIO Console application.

  • Page 150

    4. Troubleshooting (PROFIBUS DP) (3) Select the Protocol | Diagnostic on the applicomIO Console application menu. Click the magnifying grass button on the Diagnostic window. Then, select the slave you want on the device tree in the left side of the window. The window changes as shown below.

  • Page 151

    (4) When you click the I/O button, the window changes as shown below. The status of each slave device is shown in the right side of the window. A green circle indicates that the communication of the corresponding device is normal, and a red circle indicates that there is a communication error.

  • Page 152: Ethernet/ip Troubleshooting

    4. Troubleshooting (EtherNet/IP) 4.3 EtherNet/IP Troubleshooting Exclusion Every system has its special environment, conditions, specifications, and usages. This guide is provided as a general reference for troubleshooting a EtherNet/IP network. Every effort has been made to ensure the information is accurate. However, we do not guarantee the complete accuracy of the information and thus we decline any liability for damages or costs incurred by the use of this troubleshooting.

  • Page 153: Examining A Problem

    4.3.1 Examining a Problem 4.3.1.1 Scanner Board Diagnostic LEDs The EtherNet/IP board used with EPSON RC+ has two status display LEDs. The layout of the LEDs is shown in the following figure. PCU-ETHIO 4-pin Terminal Watchdog Port (Do not use this port.)

  • Page 154

    4. Troubleshooting (EtherNet/IP) 4.3.1.2 Check Network Status (1) Master Status: MS/NS LEDs MS (Module Status) NS (Network Status) (2) Node Number of Absent Slaves Absent slaves are disconnected from or not added to the network. 1. See the status flag regarding to the removal and addition if the master has status information.

  • Page 155: Problems And Countermeasures

    4.3.2 Problems and Countermeasures Master Unit LED Green Green Normal Light ON Light ON communication Green Green During connection Light ON Light establishment Blinking Green Red Light Communication Light ON Blinking timeout Green Light OFF IP address not Light ON defined Red Light No Matter...

  • Page 156: Procedures For Examining Possible Causes

    4. Troubleshooting (EtherNet/IP) 4.3.3 Tests and diagnostics 4.3.3.1 The diagnostic tool After configuring the EtherNet/IP master, adding and configuring the devices of your network and downloading your configuration in the board, the statuses of all devices can be tested with the diagnostic tool. tart this tool with the menu command “Protocol/Diagnostic…”...

  • Page 157

    1. Diagnostic of the TCP/IP layer This screen is used to display the exchange statuses regarding the TCP/IP layer. Configuration Type Address From IP address Sub-Network Mask Gateway IP Address Primary DNS Address Secondary DNS Address IP address of the secondary DNS server. Host Name Domain Name Fieldbus I/O Rev.6...

  • Page 158

    4. Troubleshooting (EtherNet/IP) TCP tab Passive connections Active connections Current connections Bytes received Bytes transmitted Retries on time-out IP tab Packets received Packets transmitted Errors Number of passive connections. Number of active connections. Number of current connections. Number of bytes received. Number of bytes transmitted.

  • Page 159

    2. Diagnostic of server devices Requests Requests / s Useful bytes Useful bytes / s Requests in error Fieldbus I/O Rev.6 4. Troubleshooting (EtherNet/IP) Number of requests. umber of requests per second. Number of useful data bytes. Number of useful data bytes per second. Number of requests in error.

  • Page 160

    4. Troubleshooting (EtherNet/IP) 3. Overall device diagnostics View the diagnostic information on a device in the configuration by selecting the node which corresponds to the device. IP Address From Requests Requests / s Useful bytes Useful bytes / s Connections Time-out errors Frame errors Refusal errors...

  • Page 161

    4.3.3.1.2 TCP/IP tool By clicking in the you the following options. ICMP (ping) See also: To display the help, select [Start]-[Program]-[Direct-Link]-[applicomIO 2.3]- 1. Resolution of IP address or name DNS functionality is available on the applicomIO solution. It is available through the diagnostic tool, DNS tab.

  • Page 162

    4. Troubleshooting (EtherNet/IP) 2. Ping ICMP ECHO "PING" functionality is available on the applicomIO solution. It is available through the diagnostic tool, ICMP tab. (1) Entry field for the IP address or name of the remote station. (2) Field showing result obtained: - Status 0 - Status 33 (3) Command field:...

  • Page 163: Maintenance Parts List

    5. Maintenance Parts List Part Name DeviceNet board PROFIBUS DP board EtherNet/IP board Fieldbus I/O Rev.6 5. Maintenance Parts List Code Specifications R13B040701 R13B040702 R12B040719...

  • Page 164

    5. Maintenance Parts List Fieldbus I/O Rev.6...

  • Page 165: Appendix A Applicomio Upgrade

    Appendix A applicomIO Upgrade (1) Start the controller (2) Insert the setup CD that is packaged with the product to the CD-Rom drive on the controller. Setup program starts automatically. (3) Select the desired language for the installer. (4) Select Products Installation. (5) Select Installation.

  • Page 166

    Appendix A applicomIO Upgrade (7) Following dialog appears. Select the option above. (If the option below is selected, the transition of the current setting will not be executed.) (8) Uninstall the current applicomIO before upgrading. Following dialog appears. Click the OK button. Following dialog appears.

  • Page 167

    Appendix A applicomIO Upgrade (10) Select the protocol and the device data file. (11) Complete the installation. (12) The message to ensure the restart appears. Click the Yes button. (13) When a service pack is attached to the CD-ROM, install the service pack. (14) After completing the installation of the service pack, shutdown the computer.

  • Page 168

    Appendix A applicomIO Upgrade Fieldbus I/O Rev.6...

This manual also for:

Rc+

Comments to this Manuals

Symbols: 0
Latest comments: