Studio 5000 compare before download — what do you actually look at?
The question
I got burned by a weekend download that wiped a counter someone used as a shift total. Compare is noisy. What filters do you leave on so you see the landmines and not 4,000 tag descriptions?
TS ControlsThe answer
Compare logic and data, not documentation. Watch retentive tags, MOTION_GROUP, and anything with a COP of a UDT. Upload first if you didn't lock the processor. Force a backup .ACD named with the date before you touch download. Descriptions will always look dirty. Logic that moves a DINT used as a total is the one that ruins Monday.
Replies from members
Log in to reply. Google, X or email.
Confirm your email to post. The link is in your inbox.
