EPSON RC+ Option Fieldbus I/O Rev.
EPSON RC+ Option Fieldbus I/O Rev.
EPSON RC+ Option Fieldbus I/O Rev.6 Copyright © 2005-2007 SEIKO EPSON CORPORATION. All rights reserved. Fieldbus I/O Rev.
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.
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® Windows® 2000 Operating system Microsoft® Windows® XP Operating system Throughout this manual, Windows 2000, and Windows XP refer to above respective operating systems.
MANUFACTURER & SUPPLIER Japan & Others SEIKO EPSON CORPORATION Suwa Minami Plant Factory Automation Systems Dept. 1010 Fujimi, Fujimi-machi, Suwa-gun, Nagano, 399-0295 JAPAN TEL : +81-266-61-1802 FAX : +81-266-61-1846 SUPPLIERS North & South America EPSON AMERICA, INC. Factory Automation/Robotics 18300 Central Avenue Carson, CA 90746 USA TEL : +1-562-290-5900 FAX : +1-562-290-5999 E-MAIL : info@robots.epson.com Europe iv EPSON DEUTSCHLAND GmbH Factory Automation Division Otto-Hahn-Str.
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. Keep this manual handy for easy access at all times.
vi Fieldbus I/O Rev.
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.............................................................................
Table of Contents 2.9 DeviceNet Board Installation ................................................... 54 2.9.1 Board Appearance ........................................................................ 54 2.9.2 Specifications ................................................................................ 54 2.9.3 Software Installation...................................................................... 55 2.9.4 Board Installation ..........................................................................
Table of Contents 5. Maintenance Parts List ................................................ 151 Appendix A applicomIO Upgrade .................................... 153 Fieldbus I/O Rev.
Table of Contents x Fieldbus I/O Rev.
1. Introduction 1. Introduction 1.1 Overview of Fieldbus I/O The Fieldbus I/O option is an integrated I/O system that supports DeviceNet, PROFIBUS DP, and EtherNet/IP fieldbuses. A fieldbus is a standard of signal communications between field devices operating in a factory (sensor, actuator, robot controller, etc.) and controller (PLC or robot controller) using serial communications.
1. Introduction 1.2 DeviceNet Overview of DeviceNet DeviceNet is a fieldbus network that provides easy interconnection between control devices (PLC, PC, sensor, actuator, etc.). DeviceNet was developed by Allen-Bradley as an open communication standard to connect various field devices (sensor, actuator, robot controller, etc.). Because of the open communication standard, DeviceNet users can easily construct a multi-vendor system with various devices developed around the world.
1. Introduction Different Connection Types There are two messaging connections: I/O messaging connection and explicit messaging connection. The I/O messaging connection includes polling, strobe, cyclic, and change of state. I/O messaging connections are explained below: Polling: First, a master device sends output data to a slave device and then the slave device responds. Data is normally exchanged in every communication cycle. The communication frequency can be changed by setting.
1.
1. Introduction 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.
1. Introduction Functions of Master There are two types of PROFIBUS DP master: DPM1 and DPM2. DPM1 (DP Master Class 1) gathers and controls all stations on one PROFIBUS DP network. DPM2 (DP master Class 2) operates network configurations, network maintenance, and diagnosis. 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.
1. Introduction General Specifications Electrical Specifications Item Supply Voltage Power Consumption Ambient Temperature during Operation Relative Humidity during Operation Specification 5 V DC (supplied from a controller) 5.5 W 5-40 deg C 20-80% PROFIBUS DP Communication Specifications Item Specification Connection Method Hybrid (token passing procedure and master-slave communication) Baud Rates 9.6 kbps, 19.2 kbps, 93.75 kbps, 187.5 kbps, 500 kbps, 1500 kbps, 3 Mbps, 6 Mbps, and 12 Mbps.
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.). Because of the open communication standard, EtherNet/IP users can easily construct a multi-vendor system with various devices developed around the world.
1. Introduction 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. For a slave device, 4,040 inputs (505 bytes) and 4,072 outputs (509 bytes) are available. Different Connection Types There are two messaging connections: I/O messaging connection and explicit messaging connection.
1. Introduction General Specifications Electrical Specifications Item Specification Supply Voltage 5 V DC (supplied from a controller) Power Consumption 5.
2. Installation 2. Installation This chapter contains procedures for installing a DeviceNet, PROFIBUS DP, or EtherNet/IP network. Refer to the sections that correspond to the type of network you are installing. 2.1 How to Setup a DeviceNet Network The following is a basic procedure for setting up a DeviceNet network: 1. Choose node distribution and distribution route on your network. For details, refer to the following section 2.2 DeviceNet Network Construction. 2.
2. Installation 2.2 DeviceNet Network Construction Network Configuration A DeviceNet network is configured as shown in the following figure. Attach a terminating resistor on each end of the trunk line. Ground to 100 Ω or less.
2. Installation Thick Cable Thin Cable 11.2 to 12.1 mm outside diameter 6.
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. The longest distance is the maximum network length. Trunk Line Terminating Resistor Terminating Resistor The maximum network length is restricted by the type of cable and the baud rate.
2. Installation Total Drop Line Length The total drop line length is the total distance of all drop lines on one network. Trunk Line Terminating Resistor 2m 4m 1m 1m Terminating Resistor 2m 4m 3m 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. Baud Rate 500 kbps 250 kbps 125 kbps Max.
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.
2. Installation (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. Then, strip the insulation from the signal wires and power wires for a length sufficient to connect them to crimp terminals.
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. Use a small flat blade screwdriver that has the correct Width Thickness width and thickness. If you use a typical screwdriver whose point is narrow, you cannot deeply insert it into the hole on the connector.
2. Installation 2.3 How to Setup a PROFIBUS DP Network The following is a basic procedure for setting up a PROFIBUS DP network: 1. Choose station distribution and distribution route on your network. For details, refer to the following section 2.4 PROFIBUS DP Network Construction. 2. Choose baud rate. Choose the baud rate based on the network length. Select the fastest baud rate allowed for the length. Increasing network load due to slow baud rate may cause trouble including communication failure. 3.
2. Installation 2.4 PROFIBUS DP Network Construction Network Configuration A PROFIBUS DP network is configured as shown in the following figure. Network Cable Master 1 Terminating Resistor ON Slave Slave Slave Master 2 Slave Slave Terminating Resistor ON Repeater Terminating Resistor ON Slave Slave Slave Slave Slave Terminating Resistor ON Station There are four types of stations (devices): master, slave, repeater, and configurator. The master controls a network and gathers its slaves.
2. Installation 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.
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. Bus Cycle Time [ms] 18 14 500 kbps 10 1.5 Mbps 6 12 Mbps 2 2 10 20 30 Number of Slaves The maximum cable length is restricted by the baud rate. Baud Rate 12 Mbps 6 Mbps 3 Mbps 1500 kbps 500 kbps 187.5 kbps 93.
2. Installation 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. CAUTION Be careful not to injure your hands or fingers on any sharp blades or tools used to modify the cable. Use appropriate blades and/or other tools to modify the cable.
2. Installation 2.5 How to Setup a EtherNet/IP Network The following is a basic procedure for setting up a EtherNet/IP network: 1. Choose node distribution and distribution route on your network. For details, refer to the following section 2.6 EtherNet/IP Network Construction. 2. Lay cables. For details, refer to the following section 2.6 EtherNet/IP Network Construction. 3. Configure nodes. For details, refer to respective manuals of your desired nodes. 4. Turn ON the nodes. 5.
2. Installation 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 Ethernet switch Ethernet switch Node Node Node Node Node Node Node Waterproof Ethernet switch Node Node Waterproof Waterproof slave slave Node There are two types of the node: master and slave. The master controls a network and gathers data from its slaves.
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. PCU-DVNIO 4-pin Terminal Watchdog Port (Do not use this port.
2. Installation 2.7.2 Specifications Part Number applicom PCI-DVNIO / PCU-DVNIO Modes Master/Slave Baud rates 125, 250, 500 kbps Interface 1 DeviceNet port Supported Devices Group 2 Only Server and U.C.M.M. capable Maximum Nodes 63 Connection Types Strobe, Polling, Cyclic and Change of State Explicit Messaging Yes EDS Support Yes Input Data Size 1 to 255 bytes Output Data Size 1 to 255 bytes Automatic Detection Yes. Devices can be detected automatically. 2.7.
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). (8) Complete the installation. (9) The message to ensure the restart appears. Click the Yes button. (10) Start the C:\Install\FieldBus\Install\SP\Setup.EXE and install the service pack.
2. Installation 2.7.4 Board Installation WARNING Make sure that the power is turned OFF before installing/removing any boards or connecting/disconnecting any cables. Installing/removing any boards or connecting/disconnecting any cables with the power ON is extremely hazardous and may result in electric shock and/or malfunction of equipment. (1) Configure the board address jumper (JP1) on each board. The board number must start with 1 consecutively. Refer to the following table for JP1 configuration.
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. (9) After all the boards are added, the system should be restarted. Close the applicomIO Console application and click the OK button on the Save modification dialog.
2. Installation 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. (3) Following dialog appears. Specify the EDS file that is supplied from the device manufacturer. (4) Click on the “Protocol list” under the board that was just added.
2. Installation (6) Configure the baud rate, MAC ID (master address), and so on for the DeviceNet network. NOTE ) The load on a bus can be controlled by the baud rate and interscan delay settings. When the load exceeds 60%, the DeviceNet network communication will be unstable, for example: more communication errors. Set the configuration to minimize the load. For the procedure for verifying the load on the bus using the applicomIO Console application, refer to the 4. Troubleshooting in this manual.
2. Installation (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 ) Fieldbus I/O Rev.6 Not every slave device supports all connection types. Understand the specifications of the slave device you want to use and configure the connection correctly.
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. When the [Ack] checkbox is unchecked, a failed connection is not regarded as an error. (11) When the system cannot identify the device you want to use (its EDS file is not registered), the following dialog will appear.
2. Installation 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. Fieldbus I/O Rev.
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. 36 Fieldbus I/O Rev.
2. Installation 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. In this example, the MAC ID (slave address) is set to 005. NOTE ) Specify an unused address on the network for a slave device as well as other devices.
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. In this example, the Output Size and Input Size are set to 8 bytes. NOTE ) The load on a bus varies depending on the input/output size settings.
2. Installation (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. You may make a copy of the default slave EDS file and modify it to create your original EDS file if necessary.
2. Installation $ EDS File Generated by applicomIO® Console Version : 2.2 [File] DescText CreateDate CreateTime ModDate ModTime Revision = = = = = = "EDS for applicomIO Scanner"; 02-01-2004; 08:14:41; 02-01-2004; 08:14:41; 1.
2. 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. Troubleshooting in this manual. PCU-DPIO 4-pin Terminal Watchdog Port (Do not use this port.
2. Installation 2.8.2 Specifications Part Number applicom PCI-DPIO / PCU-DPIO Modes Master/Slave Baud Rates 9.6, 19.2, 93.75, 187.5, 500, 1500, 3000, 6000, 12000 kbps Interface 1 PROFIBUS port (EN 50 170) Output Current Capacity Maximum 150mA Supported Devices All DP Devices Maximum Stations 126 (32 per segment) GDS Support Yes PROFIBUS DP Class 1 Yes PROFIBUS DP Class 2 Yes Input Data Size 1 to 244 bytes Output Data Size 1 to 244 bytes Automatic Detection Yes.
2. Installation (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. (9) The message to ensure the restart appears. Click the Yes button. (10) Start the C:\Install\FieldBus\Install\SP\Setup.EXE and install the service pack.
2. Installation 2.8.4 Board Installation WARNING Make sure that the power is turned OFF before installing/removing any boards or connecting/disconnecting any cables. Installing/removing any boards or connecting/disconnecting any cables with the power ON is extremely hazardous and may result in electric shock and/or malfunction of equipment. (1) Configure the board address jumper (JP1) on each board. The board number must start with 1 consecutively. Refer to the following table for JP1 configuration.
2. Installation (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. The following dialog will appear when no board is detected. Ensure that the board is correctly inserted and that the board configuration is correct. (9) After all the boards are added, the system should be restarted.
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. (3) Following dialog appears. Specify the GSD file that is supplied from the device manufacturer. (4) Select Description | Properties. 46 Fieldbus I/O Rev.
2. Installation (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. Fieldbus I/O Rev.
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. 48 Fieldbus I/O Rev.
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. Then, start from step 5 (Network Detection) of this procedure. Fieldbus I/O Rev.
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. Now, the fieldbus board is ready to operate as a master. Close the applicomIO Console application. 50 Fieldbus I/O Rev.
2. Installation 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” as a slave, it might not communicate properly in some Master. To use only the slave function, select the “Profibus, Slave”.
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” item. (8) The Local DP Slave property sheet will appear. Select the Equipment (device) ID.
2. Installation (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) Now the fieldbus board is ready to operate as a slave. Close the applicomIO Console application. 2.8.7 GSD File A GSD file is a device data file for registering slave configuration data in the configurator (device or software that configures the master).
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. Troubleshooting in this manual. PCU-ETHIO 4-pin Terminal Watchdog Port (Do not use this port.
2. 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. (4) Select Install Products. (5) Select applicomIO. Do not select applicomIO ActiveX.
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). (8) Complete the installation. (9) The message to ensure the restart appears. Click the Yes button. (10) Start the C:\Install\FieldBus\Install\SP\Setup.EXE and install the service pack.
2. Installation 2.9.4 Board Installation WARNING Make sure that the power is turned OFF before installing/removing any boards or connecting/disconnecting any cables. Installing/removing any boards or connecting/disconnecting any cables with the power ON is extremely hazardous and may result in electric shock and/or malfunction of equipment. (1) Configure the board address jumper (JP1) on each board. The board number must start with 1 consecutively. Refer to the following table for JP1 configuration.
2. Installation (8) The following dialog will appear. Check that “PCI/PCU-ETHIO (“PCI-DVNIO” in case of DeviceNet, and ”“PCIDPIO” 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. The following dialog will appear when no board is detected. Ensure that the board is correctly inserted and that the board configuration is correct. (9) Click the OK button.
2. Installation (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. Close the applicomIO Console application and click the OK button on the Save modification dialog. Click the OK button on the following dialog to restart Windows.
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. (3) Following dialog appears. Register the EDS file that is supplied from the device manufacturer. (3)-1 Click Next button.
2. Installation (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. Fieldbus I/O Rev.
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. Click the OK button to complete the registration. (8) After finishing devices registration, select File | Download in Flash to register the configuration in the fieldbus board. 62 Fieldbus I/O Rev.
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.
2. Installation 2.9.6 Slave Mode (1) Ensure that the board is connected to the fieldbus. Then, start the applicomIO console application. (2) Double-click the “EtherNet/IP Local Slave” item. (3) The EtherNet/IP Local Slave property sheet will appear. Select the Number (device) ID, and check the “Active Configuration”. (4) Click on the Assembly Instance tab. Configure how many inputs and outputs for the slave device. In this example, the Sizes and Instances of Input and Output are set as follows.
2. Installation (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. After a few seconds, the board's state will show green in the status bar. (8) Close the applicomIO console application. Fieldbus I/O Rev.
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. 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.
2. Installation 2.10 EPSON RC+ Fieldbus I/O Installation After you have created your fieldbus network and installed the scanner board(s) in your controller, you must configure the EPSON RC+ Fieldbus I/O option. Before continuing, the fieldbus scanner boards must have the device configuration stored in the board's flash memory, as described in the chapter Installation. Otherwise, the fieldbus boards will function improperly and EPSON RC+ cannot control them. See the 2.
2. Installation 68 Fieldbus I/O Rev.
3. Operation 3. Operation This chapter contains information on how to use the Fieldbus I/O option after it has been installed. 3.1 Fieldbus I/O Addressing in SPEL + Each of the Fieldbus I/O commands in SPEL+ refer to one device on the network. The bit number and port number parameters refer to inputs and outputs local to the device. 3.2 SPEL+ Fieldbus I/O Commands All Fieldbus I/O commands begin with the same prefix: "FbusIO_". Here are the main commands.
3. Operation 3.3 Outputs Off by Emergency Stop and Reset Instruction You can configure the system so that all outputs including the fieldbus outputs will be turned off when the emergency stop occurs and when a Reset instruction is executed. For details of the configuration, refer to the chapter SPEL+ Options in the EPSON RC+ User's Guide. NOTE ) A command that was issued just before an emergency stop can be executed after the emergency stop condition is cleared.
3. Operation 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. This array must be dimensioned to the correct number of bytes to send.
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: • External equipment can monitor data in the controller • Remote control To use the system in slave mode, perform the following basic steps: 1. Configure local slave on the Fieldbus scanner board. Refer to the 2. Installation for instructions for the type of hardware you are using. 2.
3. Operation 3.8 Devices available for Fieldbus I/O Option The fieldbus I/O option operations were checked with the following devices. NOTE ) The following information about the devices is just for reference. This is not our guarantee of the proper operation of these devices.
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.
3. Operation PROFIBUS DP Test Environment RC520 Controller: Pentium III 850 MHz 128 MB memory Fieldbus I/O: PCI-DPIO board Master (station address: 0) Baud rate: 12 Mbps, 9.
3. Operation 76 Fieldbus I/O Rev.
4. Troubleshooting (DeviceNet) 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.
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.) Status Display LED (2) Jumper for Board Address JP1 DeviceNet Port JP1 0 LED (2) (Not in use) 1 RJ45 Connector (Not in use) C0 C1 C2 PCI-DVNIO 4-pin Terminal Watchdog Port (Do not use this port.
4. Troubleshooting (DeviceNet) 4.1.1.2 Check Network Status (1) Master Status: MS/NS LEDs LED Color Green Green MS (Module Status) NS (Network Status) Light Condition Red Red ON ON Blinking Blinking OFF OFF (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. 2. See the MS/NE LEDs of all slaves if the master has no status information.
4. Troubleshooting (DeviceNet) 4.1.
4. Troubleshooting (DeviceNet) ♦ Process Flowchart Master LED Examining a trouble. See 4.1.1. Examining Details of Trouble. MS: Green ON NS: Red Blinking Absent Slave LED Yes MS: OFF NS: OFF Yes 1 Slave: Not Operating 2 Slave: Communication Error Detection 3 Slave: Busoff Detection See 4.1.2.1.2. 4 Slave: Not Added See 4.1.2.1.1. No No MS: Green ON NS: Red Blinking Yes See 4.1.2.1.2.
4. Troubleshooting (DeviceNet) 4.1.2.1 Master: Communication Error Master Unit LED Error MS NS Green Red Light Communication Light ON Blinking error Description - Slave disconnected from the network (Remote I/O communication error) - Slave not added to the network (Scan list collation error) - Communications power supply OFF (Error detection after the communication establishment) 4.1.2.1.
4. Troubleshooting (DeviceNet) ♦ Causes of Error Possible Cause { Slave power OFF { Broken unit Examination Method Measure the power voltage of the slaves. (It should be within the range of sufficient voltage for the slave operation.) NOTE: For slaves operating with communications power supply, measure voltage at the DeviceNet connector. Slave unit replacement Countermeasure Supply power to the slave. Replace the broken slave unit with a new one. 4.1.2.1.
4. Troubleshooting (DeviceNet) ♦ Process Flowchart Check 2 3 4 Check the following: - Unconnected terminating resistor - Unconnected or loose connector/signal wire - Cable disconnection No Problem Problem exists. (Fix it.) See 4.1.3.1 and 4.1.3.2. No problem Measure voltage of communications power supply. No Problem Problem exits. (Fix it.) No problem Replace the trouble unit. No Change The problem is fixed. No change Replace moving cable (Replace deteriorated cable).
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 z No cause is identified. Fieldbus I/O Rev.6 Examination Method (1) Check that terminating resistors are connected to both ends of the network.
4. Troubleshooting (DeviceNet) 4.1.2.2 Master: Busoff Detection Master Unit LED Error MS NS Green Red Light Busoff detection Light ON ON Duplicate MAC ID 86 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.
4. Troubleshooting (DeviceNet) ♦ Process Flowchart Check 5 Check the following: - Unconnected terminating resistor - Unconnected or loose connector/signal wire - Cable disconnection No Problem Problem exists. (Fix it.) See 4.1.3.1 and 4.1.3.2. No problem Measure voltage of communications power supply. No Problem Problem exits. (Fix it.) No problem Replace the master unit. No Change The problem is fixed. No change Replace moving cable (Replace deteriorated cable).
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 z No cause is identified. 88 Examination Method (1) Check that terminating resistors are connected to both ends of the network.
4. Troubleshooting (DeviceNet) 4.1.2.3 Master: Unestablished Communication Master Unit LED Error MS NS Green Light Light ON OFF Master Unestablished communication Description Communications power supply OFF No slave ♦ Process Flowchart Check No Problem 6 Measure voltage of communications power supply at the master unit. Problem exists. (Fix it.
4. Troubleshooting (DeviceNet) ♦ Causes of Error Possible Cause { Voltage drop of communications power supply { Disconnected terminating resistors { Cable disconnection { Disconnected connector { Disconnected signal wire { Loose connector { Loose signal wire { All slaves power OFF { Master unit configuration 90 Examination Method Measure voltage of communications power supply at the master unit. → Normal: 11V or more between V+ and Vz If the voltage is 11 to 14 V, the master unit is a possible cause.
4. Troubleshooting (DeviceNet) 4.1.2.4 Master: Configuration Error Master Unit LED Error MS NS Red Light Blinking Fieldbus I/O Rev.6 No Matter Configuration error Slave error detection 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.
4. Troubleshooting (DeviceNet) ♦ Process Flowchart Check 7 Check for master unit configuration (scan list configuration). No Problem The problem is fixed. No problem Check the following: - Unconnected terminating resistor - Unconnected or loose connector/signal wire - Cable disconnection No Problem Problem exists. (Fix it.) See 4.1.3.1 and 4.1.3.2. No problem Measure voltage of communications power supply. No Problem Problem exists. (Fix it.
4. Troubleshooting (DeviceNet) ♦ Causes of Error Possible Cause { Master unit configuration { 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 z No cause is identified. Fieldbus I/O Rev.
4. Troubleshooting (DeviceNet) 4.1.2.5 Absent Slave Master Unit LED MS Light OFF Error NS Green Light Blinking Absent slave Description - No slave (Error detection before communication establishment) - Communications power supply OFF ♦ Process Flowchart Check No Problem 8 Measure voltage of communications power supply at the master unit. Problem exists. (Fix it.
4. Troubleshooting (DeviceNet) ♦ Causes of Error Possible Cause { Voltage drop of communications power supply { Disconnected terminating resistors { Cable disconnection { Disconnected connector { Disconnected signal wire { Loose connector { Loose signal wire { All slaves power OFF { Master unit configuration Fieldbus I/O Rev.6 Examination Method Measure voltage of communications power supply at the master unit.
4. Troubleshooting (DeviceNet) 4.1.2.6 Uninitialized Network Master Unit LED MS Error Description Uninitialized network Absent slave - Master unit start-up error - No slave (Error detection before communication establishment) - Communications power supply OFF NS Light OFF Light OFF ♦ Process Flowchart Check No Problem 9 Measure voltage of communications power supply at the master unit. Problem exists. (Fix it.
4. Troubleshooting (DeviceNet) ♦ Causes of Error Possible Cause { Voltage drop of communications power supply Examination Method Measure voltage of communications power supply at the master unit. → Normal: 11V or more between V+ and Vz If the voltage is 11 to 14 V, the master unit is a possible cause. Fix the problem on it. { Disconnected (1) Check that terminating terminating resistors resistors are connected to { Cable disconnection both ends of the network.
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. Tester Measure resistance between signal wires with tester.
4. Troubleshooting (DeviceNet) ♦ Process Flowchart Check for cable laying. Check that terminating resistors are connected. Problem exists. (Add terminating resistors.) Normal Turn OFF communications power supply. Measure resistance with tester. 50 to 70 Ω Out of 50 to 70 Ω (Error) Normal Resistance: over 70 Ω Yes See 4.1.3.2. Remove one terminating resistor on either side. No Resistance: under 50 Ω Under 10 Ω 10 to 50 Ω Approx.
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.
4. Troubleshooting (DeviceNet) 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 V+ CAN H Shield (S) CAN L V- V+ CAN H Shield (S) CAN L V- DeviceNet cable V+ V- S V+ V- FG Ground 100 Ω or less. Communications power supply 24 V DC Countermeasure 1: Disconnect the wire between V- and FG.
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. Power Supply Tap V+ CAN H Shield (S) CAN L V- V+ CAN H Shield (S) CAN L V- V+ V- S DeviceNet cable Disconnect here. V+ V- FG Ground 100 Ω or less.
4. Troubleshooting (DeviceNet) ♦ 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 Power Supply Tap Disconnect I/O devices from the communications power supply. Fieldbus I/O Rev.
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. How to Examine Divide the network to find which node is the cause of the problem.
4. Troubleshooting (DeviceNet) (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 PLC Terminating Resistor Branch Tap Slave Communications Power Supply Terminating Resistor Slave Slave Slave Second First Separate slaves one by one from the network. 4.1.3.
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.
4. Troubleshooting (DeviceNet) 4.1.3.6.2 Verifying the DeviceNet network condition The applicomIO Console application has a network diagnostic function (Diagnostic). The procedure for using the Diagnostic is described below. (1) Open the Diagnostic window, click the magnifying grass button, and select the “Channel” on the device tree in the left side of the window. The window changes as shown below. The CAN and DeviceNet (scanner) tabs appear on the data display in the right side of the window.
4. Troubleshooting (DeviceNet) (2) Select the DeviceNet (Scanner) tab. The window changes as shown below. MAC ID : Module/NetWork LED IO LED : applicomR Status : MAC ID specified for the scanner board : Network Status (NS) LED status Module Status (MS) LED status Scanner board status The scanner board status is shown in the “Code No. => Comment” form. The code numbers are shown in the following table. Status Code General Protocol 0 4 32 33 34 36 108 Descriptions No fault detected.
4. Troubleshooting (DeviceNet) Status Code General Protocol 45 47 53 55 65 70 79 63 66 93 99 255 Fieldbus I/O Rev.6 Descriptions 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.
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. A gray circle indicates that the corresponding device does not exist.
4. Troubleshooting (PROFIBUS DP) 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.
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.
4. Troubleshooting (PROFIBUS DP) 4.2.1.2 Check Network Status 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.
4. Troubleshooting (PROFIBUS DP) 4.2.2 Problems and Countermeasures Master Unit LED BF ST Description [Reference] Light OFF Green Light Blinking Normal communication - Normal condition Light OFF Green Light ON Ready for communication - Normal condition Light OFF Red Light Blinking Communication error [Refer to the section 4.2.2.1 Master Communication Error.
4. Troubleshooting (PROFIBUS DP) ♦ Process Flowchart Absent Slave LED Master LED Examining a trouble. See 4.2.1 Examining Details of Trouble. Yes BF: OFF ST: Red Blinking BF: OFF ST: Green ON Yes 1 Master: Communication Error See 4.2.2.1.1. 2 Slave: Communication Error See 4.2.2.1.1. 3 Slave: Data Link Error See 4.2.2.1.2. 4 Slave: Uninitialized Network See 4.2.2.1.3. 5 Slave: Physical Error See 4.2.2.1.4. 6 Master: Data Link Error See 4.2.2.2.
4. Troubleshooting (PROFIBUS DP) 4.2.2.1 Master: Communication Error Master Unit LED Error Description BF ST Light Red Communication - Slave disconnected from the network (Remote I/O communication error) OFF Light error - Slave not added to the network (Scan list Blinking collation error) - Nonstandard wiring - No or too many terminating resistors - Noise intrusion 4.2.2.1.
4. Troubleshooting (PROFIBUS DP) ♦ Process Flowchart Check 1 2 Check the following: - Unconnected terminating resistor - Unconnected or loose connector/signal wire - Cable disconnection No Problem Problem exists. (Fix it.) See 4.2.3.1 and 4.2.3.2. No problem Measure voltage of all slave power supplies. No Problem Problem exists. (Fix it.) No problem No Change Replace the trouble unit. The problem is fixed. No change Replace moving cable. (Replace deteriorated cable).
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 z No cause is identified. 118 Examination Method (1) Check that terminating resistors are connected to both ends of the network. (2) Measure resistance between signal wires with device power supply OFF.
4. Troubleshooting (PROFIBUS DP) 4.2.2.1.2 Slave: Data Link Error Master LED Condition Absent Slave LED Condition (Data link error) MS NS Light OFF Red Light Blinking Light OFF Red Light ON ♦ Process Flowchart Check 3 Check the following: - Unconnected terminating resistor - Unconnected or loose connector/signal wire - Cable disconnection No Problem Problem exists. (Fix it.) See 4.2.3.1 and 4.2.3.2. No problem Replace moving cable. (Replace deteriorated cable).
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 z No cause is identified. 120 Examination Method (1) Check that terminating resistors are connected to both ends of the network. (2) Measure resistance between signal wires with device power supply OFF.
4. Troubleshooting (PROFIBUS DP) 4.2.2.1.3 Slave: Uninitialized Network Master LED Condition Absent Slave LED Condition (Uninitialized Network) BF Light OFF ST Red Light Blinking Light OFF Light OFF ♦ Process Flowchart Check No Problem 4 Measure voltage of all slave power supplies. Problem exists. (Fix it.) No problem No Problem Check the following: - Unconnected terminating resistor - Unconnected or loose connector/signal wire - Cable disconnection Problem exists. (Fix it.) See 4.2.3.
4. Troubleshooting (PROFIBUS DP) ♦ Causes of Error Possible Cause Examination Method { Electrical surges of Measure voltage of device device power supply power supply at the trouble unit. → It should be within the range of sufficient voltage for device operation. { Disconnected (1) Check that terminating terminating resistors resistors are connected to { Cable disconnection both ends of the network.
4. Troubleshooting (PROFIBUS DP) 4.2.2.1.4 Slave: Physical Error Master LED Condition Absent Slave LED Condition (Physical error) BF Light OFF ST Red Light Blinking Red Light ON No Matter ♦ Process Flowchart Check 5 Measure voltage of all slave power supplies. No Problem Problem exists. (Fix it.) No problem Replace the unit. Normal Communication? No Yes No Consult the PROFIBUS manufacturer.
4. Troubleshooting (PROFIBUS DP) 4.2.2.2 Master: Data Link Layer Error Master Unit LED Error BF ST Light Red Data link layer OFF Light ON error Description - Nonstandard wiring - Noise intrusion ♦ Process Flowchart Check 6 Check the following: - Unconnected terminating resistor - Unconnected or loose connector/signal wire - Cable disconnection No Problem Problem exists. (Fix it.) See 4.2.3.1 and 4.2.3.2. No problem Replace moving cable. (Replace deteriorated cable).
4. Troubleshooting (PROFIBUS DP) ♦ Causes of Error Possible Cause Examination Method { Disconnected (1) Check that terminating terminating resistors resistors are connected to { Cable disconnection both ends of the network. { Disconnected (2) Measure resistance between connector signal wires with device { Disconnected signal power supply OFF. wire → Normal: 100 to 120 Ω z Measuring point: Connection of the trouble unit z For detail, refer to the section 4.2.3.1 Connection Problem.
4. Troubleshooting (PROFIBUS DP) 4.2.2.3 Master: Uninitialized Network Master Unit LED Error BF ST Light Light Uninitialized network OFF OFF Description - Master unit power error - Master unit configuration error ♦ Process Flowchart Check No Problem 7 Measure voltage of all slave power supplies. Problem exists. (Fix it.) No problem Problem exists. (Fix it.) No Problem Check for master device configuration. No problem Replace the master unit.
4. Troubleshooting (PROFIBUS DP) ♦ Causes of Error Possible Cause { Electrical surges of master device power supply Examination Method Measure voltage of device power supply at the master unit. → It should be within the range of sufficient voltage for device operation. { Master device Check that the master device was configuration error configured properly. → After changing the configuration, verify whether the problem is fixed. { Broken master Replace the broken master unit unit with a new one.
4. Troubleshooting (PROFIBUS DP) 4.2.2.4 Master: Configuration Error Master Unit LED Error BF ST Red Light No ON Matter Physical error Description - Nonstandard wiring - Signal wire connection failure - Signal wire short circuit ♦ Process Flowchart Check 8 Check the following: - Unconnected terminating resistor - Unconnected or loose connector/signal wire - Cable disconnection No Problem Problem exists. (Fix it.) See 4.2.3.1 and 4.2.3.2. No problem Replace moving cable.
4. Troubleshooting (PROFIBUS DP) ♦ Causes of Error Possible Cause { Disconnected terminating resistors { Cable disconnection { Disconnected connector { Disconnected signal wire { Loose connector { Loose signal wire { Broken unit z No cause is identified. Fieldbus I/O Rev.6 Examination Method (1) Check that terminating resistors are connected to both ends of the network. (2) Measure resistance between signal wires with device power supply OFF.
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. Tester Measure resistance between signal wires with tester.
4. Troubleshooting (PROFIBUS DP) ♦ Process Flowchart Check for cable laying. Check that terminating resistors are connected. Problem exists. (Add terminating resistors.) Normal Turn OFF all units. Measure resistance with tester. 100 to 120 Ω Out of 100 to 120 Ω (Error) Normal Resistance: over 120 Ω Yes See 4.2.3.2. Remove one terminating resistor on either side. No Resistance: under 100 Ω Under 10 Ω 10 to 100 Ω Approx. 220 Ω Measure resistance at connectors with tester.
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 Small flat-blade screwdriver with even thickness (2) Connection of connector and unit 4.2.3.3 Noise Intrusion Verify how error occurrence condition changes while taking the following countermeasures. ♦ Ground of FG wire Normal Grounding: Peel the cable covering and ground the FG wire.
4. Troubleshooting (PROFIBUS DP) Countermeasure 1: Improve FG. Peel the cable covering and secure the cable with FG clamps. Isoelectric Line Grounding Screw Grounding Screw Slave Device 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.
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. How to Examine Divide the network to find which station is a cause of a trouble.
4. Troubleshooting (PROFIBUS DP) 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 Max. Cable Length 100 m 100 m 100 m 200 m 400 m 1000 m 1200 m 1200 m 1200 m (2) Terminating Resistor Ensure that two terminating resistors are connected to both ends of the network.
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. 4.2.3.6.1 Verifying applicomIO Console application condition The status bar at the bottom of the window shows the applicomIO Console application status.
4. Troubleshooting (PROFIBUS DP) 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 network Diagnostic function: Network diagnosis (1) Select the Network Detection tab in the left center of the applicomIO Console application. (2) Click the Online Action button. The Network Monitor dialog appears. You can check the conditions of the following errors on this dialog.
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. To check the device condition in detail, click the Diagnostic button in the Equipment information group box in the right side of the window. If an error occurs, the information is displayed in red.
4. Troubleshooting (PROFIBUS DP) (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. A gray circle indicates that the corresponding device does not exist.
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.
4. Troubleshooting (EtherNet/IP) 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.
4. Troubleshooting (EtherNet/IP) 4.3.1.2 Check Network Status (1) Master Status: MS/NS LEDs LED Color Green Green MS (Module Status) NS (Network Status) Light Condition Red Red ON ON Blinking Blinking OFF OFF (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. 2. See the MS/NE LEDs of all slaves if the master has no status information.
4. Troubleshooting (EtherNet/IP) 4.3.2 Problems and Countermeasures Master Unit LED MS NS Green Green Light ON Light ON Green Green Light ON Light Blinking Green Light ON Green Light ON Red Light Blinking Red Light ON Light OFF Red Light Blinking Light OFF Light OFF Error Normal communication During connection establishment No Matter Communication timeout IP address not defined Critical error No Matter Module error No Matter error Light OFF Not initialized status Fieldbus I/O Rev.
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…” or with the button. See also: To display the help, select [Start]-[Program]-[Direct-Link]-[applicomIO 2.3][Help]. 4.3.3.1.
4. Troubleshooting (EtherNet/IP) 1. Diagnostic of the TCP/IP layer This screen is used to display the exchange statuses regarding the TCP/IP layer. Configuration Type Mode type selected in the configuration: DHCP, BOOTP, Static How the IP address has been obtained, from the server, Address From flash memory or factory address. IP address of the applicomIO master on this channel. IP address Sub-network address of the applicomIO master on this Sub-Network Mask channel.
4. Troubleshooting (EtherNet/IP) TCP tab Passive connections Active connections Current connections Bytes received Bytes transmitted Retries on time-out Number of passive connections. Number of active connections. Number of current connections. Number of bytes received. Number of bytes transmitted. Number of retries on reception of a time-out. IP tab Packets received Packets transmitted Errors 146 Number of packets received. Number of packets transmitted. Number of IP errors. Fieldbus I/O Rev.
4. Troubleshooting (EtherNet/IP) 2. Diagnostic of server devices Requests Requests / s Useful bytes Useful bytes / s Requests in error Fieldbus I/O Rev.6 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.
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 148 Requests Requests / s Useful bytes Useful bytes / s Connections Time-out errors Frame errors IP address of the device. How the IP address of the device was obtained: from the configuration from the DNS server (IP address of the device has been resolved) Number of requests. Number of requests per second.
4. Troubleshooting (EtherNet/IP) 4.3.3.1.2 TCP/IP tool By clicking in the button and selecting "TCP/IP layer", a "services" window gives you the following options. DNS ICMP (ping) See also: To display the help, select [Start]-[Program]-[Direct-Link]-[applicomIO 2.3][Help]. 1. Resolution of IP address or name DNS functionality is available on the applicomIO solution. It is available through the diagnostic tool, DNS tab. (1) Selects the type of resolution to be carried out.
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.
5. Maintenance Parts List 5. Maintenance Parts List Part Name Fieldbus I/O Rev.
5. Maintenance Parts List 152 Fieldbus I/O Rev.
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. (6) Select applicomIO. Do not select applicomIO ActiveX. Fieldbus I/O Rev.
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. Check the [Don't display this message] box and click the Yes button. (9) Install the default components. 154 Fieldbus I/O Rev.
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. Fieldbus I/O Rev.
Appendix A applicomIO Upgrade 156 Fieldbus I/O Rev.
