rQx
Lifetime Supporting Member
Hi!
I have a Wincc Flexible 2008 Runtime system with archives connected to a s7-1200. This system logs "on change" and this is controlled by the s7-1200 every minute. It saves the logs on a network drive. My customer just called me and said that it had stopped logging 5 days ago. He just stopped the RT and started it again and the logs continued.
Have anyone had the same problem?
If the RT have problems logging a value (maybe the network drive was down), how does it handle it?
Would it just try again next minute and skip the last value and continue to do so until it succeed?
Does it have a memory where it keep the old log values and write them all?
Or does it stop the logging?
Maybe some buffer got overloaded or something and it all just froze?
I really don't have that deep understanding how the logging works inside the RT.
/Tim
I have a Wincc Flexible 2008 Runtime system with archives connected to a s7-1200. This system logs "on change" and this is controlled by the s7-1200 every minute. It saves the logs on a network drive. My customer just called me and said that it had stopped logging 5 days ago. He just stopped the RT and started it again and the logs continued.
Have anyone had the same problem?
If the RT have problems logging a value (maybe the network drive was down), how does it handle it?
Would it just try again next minute and skip the last value and continue to do so until it succeed?
Does it have a memory where it keep the old log values and write them all?
Or does it stop the logging?
Maybe some buffer got overloaded or something and it all just froze?
I really don't have that deep understanding how the logging works inside the RT.
/Tim