Problems with Profinet connection from KUKA to Siemens PLC

It's a good idea to ping the IP of the robot (192.168.1.238) to ensure you are able to reach the robot from the computer at least (since you can upload the WV project I imagine this isn't an issue, just a sanity check)

Also within TIA portal under the properties of your 64 safe digital I/O (can be seen in the device view of KRC4), make sure the F_Dest_Add matches the device number configured in WorkVisual, I believe these defaults to 7 which should work fine.

Quote from nickmichiels100

After this I placed a networkcable from the PLC to the robot (KLI port).

Did you correctly configure the KLI interface for the use of PROFINET?

Do you have the system integrators manual? The procedure on how to do this is described in the KSS8.x SI manual.

Quote from nickmichiels100

robot-forum.com/attachment/36518/

Not this one. I am not sure if it is allowed to share the manual here. You got a PM with the KSS8.2 SI manual.

Are you using the correct GSDML file? Which error messages are displayed? Did you already create the reintegration logic for the robot on the PLC side, e.g. by using ACK_GL?

you did not set things correctly....

in your case KLI has two interfaces, virtual5 and virtual6 which is fine.

virtual5 is used for ProfiNET and has network settings 172.31.1.234, 255.255.255.0

virtual6 is the windows interface using 192.168.2.238, 255.255.255.0

your PLC must be in the same network as the virtual5, not virtual 6.

PLC configured to IP address 192.168.1.240 will never be able to communicate with KRC using 172.31.1.234.

subnet mask tells how the IP addresses are used (where the split between LAN address and node address in IP address is). subnet mask value really should be looked at in the binary form - all "1"s are on the left and signify bits that form the LAN address. all "0"s must be on the right and signify bits that represent individual node within the LAN. all participants in LAN must have same subnet mask, same LAN address and unique node address.

in case of subnet mask value 255.255.255.0 that first three octets of the IP address must be the same (this is the LAN address) and the last octet must be different (this part is the node address). so perhaps try configuring PLC to use 172.31.1.240 (if robot virtual5 is to stay on 172.31.1.234),

or

change virtual5 address to 192.168.1.234 (if PLC is to stay on 192.168.1.240)

network address is one of things that need to match. there is more to this. KUKA has relevant fieldbus training. there is a reason this is a 4 day course and not 30min lunch and learn.

you still need to look at all other settings side-by-side. the pictures you posted show somewhat fragmented view of the config so one cannot tell with certainty if other things are correct or not.

1. IP addressing - matched (probably good this time, unless someone also messed with filter settings)

2. node name matched (not sure, robot side name is 'krc4', the same has to be used in S7 config but it looks like in S7 config you are using 'kuka-noname')

3. IO block size has to match (not sure, robot side is 256, plc side is ...?)

4. physical connection need to be correct (probably ok, as previously it was possible to ping virtual6 on the KLI but who knows...)

5. used GSDML need to be correct one...

6. refresh rate need to be correct... (if my memory is correct 2.3 is good for 8ms but not faster)

7. safety address must match

8. standard IO mapping need to be done on the robot side

9. safety IO need to be used in the PLC safety task

etc.

so read the manual and choose correct settings. and when posting screenshots, try to display more useful info and less space. empty space in screenshots does not help. for example pic3.jpg in your first ZIP file shows huge central part of the image dedicated to network image and tons of unused screen space while the more important part (the actually interesting info - Network overview) is squeezed into a corner. Device settings are not shown at all. How is anyone supposed to decipher what you have there if you are not going to show relevant details. this is why i put together READ FIRST to try steering people asking for help in the right direction but plenty of people just wing it, do no preparation or thinking about what may be useful.