Hey guys, after trying many different things we found that the issue was our network switch. After swapping our 100Mbps switch for a 1000Mbps the Profinet communication was correctly established.
Posts by luccaleao
-
-
well KRC5 is pretty new and not many people had chance to try it out.
but... so far when using two or more virtual adapters on KLI, there was always a separate network configuration for each of them. and that was true even when both are using single physical port (X66). so... you may want to check that. did you change anything about KLI setup? are filters setup correctly?
also under diagnostic, usually near the bottom of the list should be KLI settings including ProfiNet... you should check real setting there. also are you sure you are using correct GSDML? using older ones is possible but there are restrictions. manual goes over this.
I setup the filters as instructed by the operation manual. virtual5 (Profinet) interface is "Target IP address" and virtual6 (Windows) is "Accept all".
I also tried another KLI port to my switch, so now I am using both XF5 (KLI 2) and XF6 (KLI 1) physical inputs. Still no success.
I could not found the KLI settings on diagnostics but I did find this port list in Online access diagnostics. It seems ports 1 and 2 are disconnected. Could this be related to my issue?
-
I am facing a very similar issue, except with KRC5 and Profinet 6.0.2. The device is unreachable on Tia portal even though it shows up on the Accessible Devices window.
What exactly did you do to make it work?
-
Not willing to look nearer onto blurred images on external links, but on some versions you can switch the profinet versions on the Kuka profinet configuration page, try the other versions, if possible.
Look into the profinet documentation of the installed profinet, there must be a PDF document somewhere on drive d:. In this document there is a table for the settings of each kss version, for the correct GSDML file and profinet version.
Didn't have such a new version, so can't look on real robot.
Do you mean compatibility mode? If so then the only option available to me is KRC5-Profinet 6.0, since that was the .kop file that was provided to us by kuka.
Unfortunately the provided Profinet documentation did not include instructions for my specific GSDML version (GSDML-V2.4), as it only provides settings for up to version GSDML-V2.32.
is that what "sem ProfiSafe" means? it looks good... don't see anything obvious... KRC name matches, addresses are in same subnet, mapping looks fine... did you reboot both?
also KRC5 has several KLI ports. are you sure you are using correct one?
I rebooted both PLC and KRC5 after downloading and transferring the project.
I have my switch connected to the KRC5 XF6 which is a KLI 1 port. According to the manual:
• KLI 1: Interface to the PLC (e.g. Profinet with ProfiSafe or EtherNet/IP with CIP Safety)
• KLI 2: Interface to the terminal (e.g. Profinet or Ethernet/IP)Right now I have two different network interfaces set: one for WINDOWS (virtual6) and one for Profinet (virtual5). Do I need to use two different KLI ports for this configuration?
-
is that what "sem ProfiSafe" means?
Yes, it translates to "no Profisafe". I forgot to swap that image after I changed my software language, sorry
-
Hello everyone,
For the past few days I have been trying to set up Profinet communication between my KUKA KR4 Agilus KRC5 Controller and Siemens PLC, but ran into some problems.
These are my robot specifications:
-Kuka KR4 Agilus
-KRC5 Controller KSS 8.7.1
-Base system version KS V8.7.338
-WorkVisual 6.0.17
-Profinet version: KUKA.PROFINET S V6.0.2
My PLC is Siemens S7-1200, CPU 1214C. It's IP address is 172.31.1.222 and the robot PROFINET (virtual5) is 172.31.1.147. The KRC5 is connected to a switch through the KLI 6 port and the PLC is also connected to the switch. I can ping both IPs from my machine
These are the steps I have followed so far on robot side:
1. Downloaded the project in Workvisual, added a PROFINET module.
2. Set the device name to krc5, activated device stack (since I want it to be a slave device) with 0 safe IOs, and 256 standard IOs.
3. Mapped the PROFINET IOs to KRC IOs -> addresses 20.0 .... 51.7 to $OUT[1] .... $OUT[256] and addresses 21.0 .... 52.7 to $IN[1] .... $IN[256]. See 2nd attached pic.
4. Compiled and transferred to controller.
Then I took these steps in TIA Portal V15.1:
1. Added GSDML File to my catalog GSDML-V2.4-KUKA-KR C5-20201026.xml
2. Added the KRC5 device and connected it to my PLC through PN/IE_1.
3. Set the IP address of the robot Profinet interface (172.31.1.147) and device name krc5. Same as in the WorkVisual configuration.
4. Removed the 64 safe IOs from the krc5 device.
5. Changed the I address range from 16...47 to 21...52 and the Q address from 16...47 to 20...51 to match the address ranges in WorkVisual project.
6. Compiled and downloaded to PLC -> Go Online.
Following these steps I am receiving the following errors on HMI:
KSS00099: PNIO-DEV Read/write error.
KSS11011: Impossible to establish a connection between PLC and krc5 Slot 1 in 20000ms
KSS11011: Impossible to establish a connection between PLC and krc5 Slot 0 in 20000ms
On TIA Portal I can see both PLC and krc5 as accessible devices. But when I go Online there is a red warning next to krc5 that reads "not reachable".
One other thing I tried was use the default addresses of the device on tia portal (16...47), but that did not work either.
Any help is greatly appreciated.
-
Hello all,
I have recently started working with a Kuka KR4 robot with C5 controller. I have wired the Smart Pad, data and motor cables to the controller as shown in the attached picture. I have not yet been able to move the robot or make the requirement axes adjustments.
The warning interface on the Smart Pad shows the following error messages when I turn it on:
KSS00020: External Emergency stop
KSS00001: Emergency Stop
Since my safety PLC is not yet available, I was able to bypass the external emergency stop by activating Start Up Mode on the main menu, but the Emergency Stop warning KSS00001 remains.
Pressing or turning the Emergency device on the SmartPad has no effect on these warnings whatsoever. Could it be there is any local emergency wiring that I overlooked?
Any help with this situation is greatly appreciated.