Hello, 

We have a system using a D445 Control Unit and running 6 servos. During power up the unit will go into stop mode intermittently. When checking the fault buffer there is a abundance of "Technological Alarms" that lead to a "Message Buffer Overflow" This system has been in use for many years. 

Our current solution is to power cycle until the system comes up accordingly. I have attached the diagnostic buffers from the SIMOTION and SINAMICS CPU. Power cycling is not always successful on the first try. Sometimes we have to power cycle 5 times and sometimes once. I did check the 24V supply and I am seeing around 23.4V. 

Any ideas?

Thanks

-Ross

Create a simple program with only delay of, say, 30 seconds. Place it at beginning of the Startup Task program list. Maybe it will help.

jacek d

Create a simple program with only delay of, say, 30 seconds. Place it at beginning of the Startup Task program list. Maybe it will help.

 Hello, 

Jacek, Siemens Tech Support had the same idea. Looks like the root problem is the the "pstartupcheck" was not in the Task Execution for startup so it is allowing the SIMOTION to go into run before the SINAMICS which is causing all the "Technology Errors". Going to try adding "pstartupcheck" first and if that fails, I will try the basic delay. 

Thanks again Jacek

-Ross

jacek d

Create a simple program with only delay of, say, 30 seconds. Place it at beginning of the Startup Task program list. Maybe it will help.

 Jacek, 

I tried a 30 sec delay and even a 100 sec delay neither worked to prevent the abudance of "Technological Alarms" which cause the message buffer overflow error. 

Any other ideas?

-Ross

Another idea -  the program tries to access TOs before they are ready. Leave this delay as is. Let the Simotion to start. Block all tasks execution after switching to RUN till a device variable stateOfDpInterfaceSynchronization = DP_INTERFACES_SYNCHRONIZED

It is also possible that whatever you run in the Technological Fault Task takes too much time.