Last seen: Sep 22, 2026
Trend the count against the run bit for a week. You'll see every jog on it.
Fair enough on the buffer, our short stops were always a guess.
That swing is never a sensor. What happens on a bad day that doesn't happen on a good one?
We did ours off the run bit in the SCADA for two years and it was fine. You put a 5 second filter on the transition so short jams roll up, and a dropd...
Built it over the weekend. One UDT called Stn_Data with Count, Rejects, RunMinutes, a 20 character name string and a DINT for the last stamp, then Sta...
FactoryTalk Historian SE, and the point list in it was typed in by hand by whoever set it up. That's half the reason it's a mess, nobody has touched t...
Card in slot 4 is a 1769-IQ16F. The crib spare is an IQ16F as well, so both of the cards I tried were the fast version and the project has plain IQ16 ...
Six modules and no change to the count for two years, so I don't think we're over anything. Pulled the ECR off and refitted it anyway, no difference. ...
v33 here. Tree says 1769-IQ16, Series A, and the Connection tab says Module Fault, 16#0114, something about an electronic keying mismatch and a produc...
Coast time with the heaviest wheel goes in the validation file, not the bench number.
Keep that trend screenshot with the project. Next person will want it.
The other three haven't had antivirus put on them yet. Give it time.
Sounds like the watchdog tripping on a late Second update. I reckon 3 s is tight for a terminal that's also drawing screens. Compare against the last ...