WinCC OA diagnosing communication failure

Discussion about recent product features & solutions!
3 posts • Page 1 of 1
ccmelo
Posts:4
Joined: Mon Oct 13, 2025 4:00 pm

WinCC OA diagnosing communication failure

Post by ccmelo »

I am currently working on a project that involves developing an animation in WINCCOA 3.20, and I need to incorporate a reliable method for diagnosing communication failures. Understanding how to effectively diagnose these failures is crucial for the functionality of my animation.


Could you please share any best practices, tools, or methodologies that you use to diagnose communication issues?

I was thinking about using the _aut_inv_, but i dont think its going to work.

Any insights or resources would be greatly appreciated, as they will help ensure that my project runs smoothly.


Thank you for your assistance!

leoknipp
Posts:2928
Joined: Tue Aug 24, 2010 7:28 pm

Re: WinCC OA diagnosing communication failure

Post by leoknipp »

What kind of communication failures are you talking about?
If your question is related to a communication of field devices/PLC connections it depends on the driver which possibilities you have to check if the communication is working or not.
Without detailed knowledge for the project configuration we cannot provide further information.

If you need assistance in engineering your project please get in contact with your common WinCC OA support.

Best Regards
Leopold Knipp
Senior Support Specialist

gschijndel
Posts:376
Joined: Tue Jan 15, 2019 3:12 pm

Re: WinCC OA diagnosing communication failure

Post by gschijndel »

Using the '_aut_inv' ('_invalid' or '_bad') attribute should be possible, but (most) drivers do not set it by default.
You should check if your driver has a 'set invalid bit' setting (connection dpe or config file), which must be set to have the '_aut_inv' bit be set on connection loss.

3 posts • Page 1 of 1