Hello,

I have problem with PROFISafe telegram 30 on 1512F CPU. I try to write STO into telegram 30 by safety program directly and thru function from LDrvSafe library but values in PLC tags remain FALSE. If I map output of function to "non safe" range of outputs, I get correct value (TRUE) in PLC tags.

I add few printscreens into attachment.

Any idea what is wrong?

Thank you

Tomas

Hello,

thank you for reply. With FB you mean feedback block? Visible feedback block is used for second drive (there is 8 pieces of same drive). I spend a lot of time to check, if there is some another point where this bite is written.

Hello,

I had time for some experiment. I used CPU with FW 2.9.7 (older generation of CPU) and results are same as with CPU FW 3.1. When I try to write bit in Telegram 30, in PLC tags remain in FALSE. If same data type is used in non FS area, correct bit is set to TRUE. This behavior doesnt make sense for me

Hello,

same picture here! Have you found a solution?

Are you using V18?

I noticed that I also do not see the "STO active" in Status-Tlg30 coming from the drive. And my Feedbacck-FB of course needs the "STO acitve" to be TRUE before activating the drive. But I worked around that, and it still does not work.

Any suggestions?

Georg

Hello, yes we find solution. Reason for this issue was safety error on communication. When we were able to reset this error (safety function ACK_GL), QBAD signal in F-I/O data block go to FALSE and communication start to work.

I have both V18 and V19, behaviour is same

We found the Datablock of our Profisafe Telegram 30, and there we see QBAD is TRUE. But we cannot resolve it with ACK_GL.

What was your reason for the communication error?

We tried another CPU as a reference test, and it works fine. There must be some wrong configuration in our original CPU. We checked IP-Adress, Profinet-Name, Profisafe-Adress, Telegram30-Adresses, and it all looks good.

Any idea?