Display Moreconsider hiring someone. you are not exactly following advice or reading responses and i don't have patience to pull words out of you...
>> "I followed I instructions provided by kuka."
what instructions?
>> "Tried all that and nothing works."
what is 'nothing'?
>> "X11 is disabled with a jumper on x311 and x48 unplugged to the SiB"
did you activate safety configuration after deploying and activating WoV project?
>> "Non profisafe comms are working.."
impossible... no I/O are mapped, bus may be running but no data exchange takes place. how are you testing this?
>> "Non profisafe comms are working...Profisafe wont work :("
that PLC is a safety PLC. what did you map there and how?
>> "GSDML used on plc : KRC4-Profinet_3.3"
what the heck is that? do you mean "GSDML-V2.32-KUKA-KRC4-ProfiNet_3.3-20170131.xml"?
and how is it configured? you mentioned PLC complaining about memory access. what addresses are used here?
>> "Please note that ive done profinet communication many times on this type of robot"
possible but very doubtful... no I/O are mapped
>> "I set up all reserve bits to be true. This just gives me plc memory wrote error meaning comms arent working ."
why provide digested interpretation of the message instead of actual message? did you read READ FIRST?
>> "Do i need Profinet ProfiSafe Device option installed on KRC4?"
There is no separate option just for 'ProfiSafe device'. ProfiSafe is part of ProfiNet. If ProfiNet option is installed, ProfiSafe is installed too... and yes, if you want to use ProfiNet or ProfiSafe - ProfiNet option must be installed on controller. Not just that, in this KSS it has to be installed on KRC4 controller BEFORE you do anything else:
a) take working WoV project from KRC4
b) add your modifications to WoV project (bus configuration)
c) deploying and activating project
d) activating safety configuration.
are you sure you took project from controller after the ProfiNet was installed? installing options modifies bunch of files on controller. you want all of those files in the project before you start adding your things into project.
my recommendation is to get non-safe data exchange working first. and have it tested. set bits on one end and see if they change on the other end, then reverse process. after this is done, add the safety signals.
Seems like you're more concerned about me not providing useless information rather than trying to pinpoint the issue or give an advice.
I said ive set up profinet many times before, you dont believe me. I checked the PLC error buffer, no error = comms work ok. even without mapping the IO on KRC4.
On older profinet drivers it was required to map something in order to get the driver to start, on newer stuff (3.3 i believe) you dont have to.
I said profinet was working just fine without profisafe so why go through all this headache and give you step by step instructions of what i did.
I provided you with enough information related to profisafe issues i was having. No need to be an a$$ about it.
Anyways, i came here for help and all i got was insults.... keep running your forum like you do mr moderator.
Anyways, like i said before, if anyone has the same issue, look into your failsafe Watchdog timer on your PLC. For Siemens it's F_WD_Time parameter. All i had to do was to increase the timer from 150 (GSDML default) to 250ms and everything started working, even without any io mapped.
Afterwards i successfully mapped IO and got the robot going.
Thanks