To configure Profinet slave communication for Fanuc robots: First, ensure the robot has the Profinet option. Then, access the robot’s I/O configuration menu. Set the Profinet parameters such as IP address and subnet mask. Map the robot’s I/O signals to the Profinet data area. Test the connection to make sure proper communication between the robot and other Profinet – enabled devices.
- Overview
PROFINET I/O is a communication method based on industrial Ethernet, which can be used as a slave and a master (such as PLC). When the robot is a slave, it can support up to 128 bytes of input/output (DI/DO, GI/GO, UI/UO), where the Rack number is 102 and the Slot number is 1 when the signal is configured. - Software and hardware confirmation
2.1 Software confirmation
The software needs to be installed: R834-Dual Chan.Profinet; confirm whether this software is installed in the I/O menu. If not, you need to add optional functions. For each version of the flash package and option addition, you can reply to Fanuc Flash in the background for more details.
2.2 Hardware confirmation
The Molex board, also known as the Fanuc Profinet board, needs to be installed; the hardware is connected when the Profinet slave communicates, and the PLC is connected to the Port1/Port2 of the board Chain2 through the Profinet communication line. - Software settings on the robot side
3.1 Address setting
1) MENU→I/O→PROFINET (M)→Select channel 2→Select button F[5] to change the channel to valid. The icon of channel 2 becomes bright, indicating that the channel is successfully enabled.
2) Use the DISP button on the teach pendant to switch the cursor to the right and change the IP address and name.
3.2 Input and output module settings
Set the content of IO-Device, including Slot Type and Slot Size. Click the DISP button to move the cursor to the window on the right, click the up and down buttons, and move the cursor to Slot1. Click the EDIT (F4) button to open the setting screen of Slot1. In the Slot1 setting screen, move the cursor to SlotType, click the EDIT button, and the model selection window pops up. Select Input Output slot and click the APPLY button. Set Slot1 to input/output module. Similarly, follow the same steps to set Slot Size to 8 bytes (i.e. DI and DO are 8 bytes respectively). Return to Figure 5.IO-Device setting interface, select F1 SAVE, and then restart for the setting to take effect. Note: Here, an 8-byte input and output slot is used as an example. The actual setting needs to be exactly the same as that on the PLC side.
3.3 Signal allocation
Select the signal type to be allocated in IO using the menu key. For example, if it is DIDO, select Digital. The signal allocation method for the Profinet communication robot as the master station is 102 for the rack and 1 for the slot. The starting point can be defined by yourself, and the signal range can also be modified by yourself. - Software settings on the PLC side
1) The PLC technician at the customer site imports the robot’s GSD file in Botu (taking Siemens PLC as an example);
2) Set the robot’s IP address, subnet gateway, name, and input/output byte count (the same as the settings on the robot side). The input/output module is added in the device view, and the address and name are modified in the network view. Finally, compile and download the connection. - Common problems and solutions
5.1 The Profinet interface does not display
Fault phenomenon: When the robot imports the image file of other robots, the Profinet interface may not be opened (that is, click PROFINET (M), no response);
Fault cause: Firmware version problem
Solution: Upgrade the TP firmware to solve it.
5.2 Unable to enter Profinet
Fault phenomenon: Click PROFINET (M), and the progress window of entering Profinet is displayed, but the interface cannot be entered;
Fault cause: Software and hardware problems
Solution: In most cases, it is a hardware problem of the board. Replace the new board, but you need to confirm whether the firmware version is consistent. If it is inconsistent, you need to update the firmware version.
5.3 Communication lights up red
Fault phenomenon: The IO device indicator lights up red, which means that communication is not possible;
Fault cause: Inconsistent settings between the robot and PLC side, GSD file version problem, network cable problem, firmware version problem, board card dialing, etc. Solution:
(1). Confirm whether the IP address, name, IO type and PLC side settings are consistent;
(2). Check whether the GDS file on the PLC side is consistent with the control cabinet model. For example, the R30ib model control cabinet should use the GSDML-V2.3-Fanuc-A05B2600R834V830-20140601.xml file in the Product/R834/r30ib_r834_140812 compressed package in the 7dc3 series flash package, while the R30ib/plus model control cabinet should use the GSDML-V2.3-Fanuc-A05B2600R834V830-20140601.xml file in the 7df1 series flash package. Product/R834/r30ib_r834_140812, where A/B cabinets use the file GSDML-V2.33-Fanuc-A05B2600R834V910-20180517.xml Mate cabinets use the file GSDML-V2.33-Fanuc-A05B2600R834V910M-20180411.xml SCARA robot control cabinet uses the file GSDML-V2.33-Fanuc-A05B2600R834V910C-20180502.xml
(3). Replace the network cable;
(4). Confirm the firmware version;
(5). Confirm the board dial code, 1246 is ON, 35 is OFF.
5.4 The robot IP cannot be scanned during Target Configuration
Fault phenomenon: During configuration, the robot IP cannot be scanned during Target Configuration;
Fault cause: PC and robot connection problem Solution:
(1) Recheck the IP settings;
(2) Replace the network cable;
(3) Delete the task and create a new task;
(4) Turn off all anti-virus software and firewalls. If it still doesn’t work, change a PC.
5.5 Connection error
Fault phenomenon: When clicking Connection, an error message appears;
Fault cause: PC and robot connection problem Solution:
(1) Re-tighten the network cable;
(2) Check whether the network port is plugged in correctly;
(3) Turn off all anti-virus software and firewalls. If it still doesn’t work, change a PC.