I will be very grateful to you Visentainers, I will look forward to it.

ProfiSafe communication error
-
xlyanyura -
September 21, 2024 at 3:40 PM -
Thread is Unresolved
-
-
xlyanyura I saw you mixed a lot of information in this topic, I did my robot work following only the steps in this video. Please, pay attention in device sign in plc, and device name (usually kuka-noname) must be the same in tia and Work visual.
After you finish the setting, profinet connect automatically, but profisafe not, you have to restart the plc, or use a reset block inside the main safe program in tia.
With this video and backup you are able to put it work.
Configuration Profisafe between KUKA robot and Siemens PLC Simatic in TIA Portal plus WorkvisualVideo about Configure Profisafe via KUKA robot and Siemens PLC Simatic in TIA Portal plus Workvisual Contents are:- Adding Safety IO module of KUKA robot in ...youtu.be -
Thank you for sharing the information, especially the TIA security settings.
Please explain to me as clearly as possible why this block is needed?
Thanks. Best regards, Arsentis.
-
try Google, it can find lots of interesting things
Global Acknowledgment Instruction in Safety PLCIn this article we will talk about one useful safety PLC instruction in TIA Portal; this is the ACK_GL or Global acknowledgment function.instrumentationtools.com -
Thank you for the project Tia Visentainer_Sulivan, I downloaded the profisafe error disappeared, so the connection is established. But the errors that were there from the beginning are still there.
As a panic mode I was told to start all over again. That's where I am now. The PLC communicates with the robot, data is exchanged.
How do I get rid of those errors, where to dig, in what direction to go?
-
Arsentis as panic mode showed it is a global acknowledge, always that a safety device are not ok, plc get fail, when the safety device is ok again, you have to reset the plc, I use this block to reset.
-
you are not doing this correctly. oldest messages are at the bottom. messages that appear later may be just follow-up messages. you did not just clear some of original messages - you also introduced another one. clicking on "?" on each message will provide more info.
unfortunately some of messages are total crap - that includes ones you are trying to get rid of. they should all point to a way forward to help resolve the situation but they do not.
"IO error in safe device"? give me a break. this is yet another example of a terrible message. they could have at least specify which device is the problem. a better job would be to also specify the specific IO signal or operation but we can only hope... plenty of badly worded or not explained messages are listed in a pinned topic.
did you try going through diagnostics screens? some device is not talking and they may help identifying it.. anything that has non-zero error counters values.
and did KUKA ever come up with any response? it's been a month...
-
I took the last error away from me, it's gone, only those are left.
KUKA answered me and said that in IBN mode the cookie should move, asked about the button on the remote control if it was not clamped, and told me to make an appointment for a specialist to come and examine it.
I still have 3 errors that I can't solve, they were present when I first bought the robot.
-
Maybe some of my licenses still need to be installed?
-
I continue to study your TIA project that you shared with us to create my Profisafe project.
Can you also explain to me why you made these three schemes.- Once again, I apologize if you find my questions stupid or too simple. I am not a programmer and this is not my job, I work as a designer of industrial refrigerators and display cases. In my first post, I explained why I bought the robot, before this purchase I had not encountered robots.
- Thanks. Best regards, Arsentis.
-
program is not commented so there is no telling what it does. the rungs 2 and 3 seem to be an attempt to create custom clock 2sec on, 2 sec off. but it cannot work (at least not properly) because of double coil for "Tag_19". removing that coil from #3 would make it work correctly. here is a demo:
Online Ladder Logic Simulator: Learn & practice PLC programming!Online PLC Simulator: Master Ladder Logic programming with an interactive tool for creating, learning & sharing ladder logic diagrams. Elevate your PLC skills!app.plcsimulator.onlineor shorter
Online Ladder Logic Simulator: Learn & practice PLC programming!Online PLC Simulator: Master Ladder Logic programming with an interactive tool for creating, learning & sharing ladder logic diagrams. Elevate your PLC skills!app.plcsimulator.online -
Maybe some of my licenses still need to be installed?
No.
One attempt can be to post a picture of all messages after cold boot, before pressing any 'quit button'
-
Thank you panic mode , your link to the simulator very clearly describes the operation of the diagram.
I would really like to read the Visentainer_Sulivan comments on why this diagram was created.
Thanks. Best regards, Arsentis.
-
Network 2 and 3 are clock just to turn on and off a signal, it will be write to an output (network 1) if and input from robot get down, if emergency stop active for example.
This output goes to robot and in sps program ruturn to plc in globlal acknowledge block.
I did this just because when I turn on the robot, the plc starts to fast and get fail before robot system is working, so, robot starts with emergency stop profisafe fail, and plc in fail. But profinet starts working making possible this reset.
-
why are tags and code not commented? it could be like this.
-
I did it 5 times until work, 2 first time I commented, after not
-
I am attaching links to short videos of my errors, diagnostics, please review
-
Quote
Congratulations to all, I managed to overcome the errors thanks to the panic mode tips, I still replaced the smartpad and the errors that prevented the work from moving disappeared, so the problem was a faulty smartpad. Also thanks to Visentainer_Sulivan. who shared the winter program for the PLC, I managed to start the robot in automatic mode.
I also connected the 7th axis, which also works synchronously. Thanks to everyone who helped me figure this out.
-