PanelView Plus 6 1000 on the case sealer, application came out of View Studio ME v8 or v9, it's been on the wall since before my time. Controller's a CompactLogix 1769-L33ER. The alarm list on the terminal stamps events 11 minutes earlier than the same event in the PLC fault log, and the gap keeps growing. QA picked it up because the terminal alarm and the SCADA alarm for the same jam are 11 minutes apart on paper.
I set the terminal clock by hand from Terminal Settings, Time/Date back in January and it's drifted out again since, so I power cycled it twice on the off chance. No change, not that I expected one. One of the lads reckoned battery, but it doesn't lose the time on a power cycle, it just drifts.
Is there anything in an application that old that'll pull the time off the L33ER, or am I setting that clock by hand forever?
We had a Plus 6 lose time and that one was the battery, but it went back to 2007 on every power cycle, it didn't drift. Yours keeps time through a power cycle, so I think you can leave the battery alone.
Does the terminal show a battery warning on the Terminal Settings screen at all? Photo of ours attached, the warning sits at the bottom.
no warning. And the L33 is 3 minutes off the SCADA as well, now I look. So nobody's on the same time. Which one's right, I couldn't tell you.
Three clocks, three answers. The terminal keeps its own RTC and it drifts, they all do, a few minutes a year is normal. Nothing you set by hand will hold.
The ME way is Global Connections. In View Studio, Global Connections, Remote Date and Time section, tie Year, Month, Day, Hour, Minute, Second to six DINT tags in the L33ER that you fill from the controller clock with a GSV, WallClockTime, LocalDateTime. The terminal reads those, if I remember right about once a minute, and sets itself. New MER and load.
Then the L33ER needs a source of its own. Logix has no NTP client. Have the SCADA write the controller clock once a day through the driver and an SSV. Time hardware exists, you won't buy it for a sealer.
Did the Global Connections part and a GSV rung into six DINTs, new MER, loaded it. Terminal snapped to the L33 time inside a minute. Now those two agree with each other and both disagree with the SCADA by 3 minutes.
One down. Who owns the SCADA box, does it get time from the domain?
SCADA box gets time from the domain, so that one's the reference. The SCADA guy added a daily write of the controller clock through the driver, an SSV on the PLC side takes it. This morning all three are inside a second of each other.
So the terminal was running on its own RTC and drifting, and the L33 had no time source either. Global Connections, Remote Date and Time from six DINTs out of a GSV WallClockTime, plus the SCADA setting the L33 clock once a day.
I'm still not sure about one bit, the GSV LocalDateTime gives seven values and I don't know whether the terminal wants the seconds or ignores them. It's right either way.
Thanks rsdave and sparkymike.
Same chain on most of ours. The GSV rung is the part people forget to add.