I'm on placement here and got handed this because nobody else was around. Went to go online with the bagger controller today to look at a fault, 1756-L71, and Studio 5000 v32 gave me the correlate box. The offline file doesn't match, upload or download, and the option to just go online is greyed out.
The file I have is the one on the shared drive, Bagger_2022.ACD, last saved in 2022. Nobody here admits to changing anything, I asked the two guys on days and got shrugs.
I haven't clicked either button. My guess is the controller memory has gotten corrupted somehow. Is it safe to download the 2022 file to put it back to known good, or am I missing something obvious?
Do not download. Nothing is corrupt, the controller simply holds a different edit of the project than your file. What firmware is the L71 on, and what does the correlate box list for the two sides? It shows the last edit time and, if I remember right, the name of the PC that did it. Thats your contractor or your colleague.
Firmware 32.011. The box says offline file last edited 2022-06-14 on ENG-LAPTOP-2, controller last edited last month, on a machine called CONTRACTOR-DELL something. We had a contractor in last month for the metal detector, so that'll be him, and there are three laptops floating around maintenance besides. I guess that means my file is useless now?
Upload to a new file. Never over your only copy.
Carl's right, and here's the order. Pick Upload, and when it asks for the file, Save As a new name, Bagger_2026-09_upload.ACD, so the 2022 file stays untouched. Then Tools, Compare, or the Logix Designer Compare Tool from the start menu, old file against the upload. It lists every rung and tag that differs. Most likely the contractor added the metal detector reject logic and nothing else, in which case the upload is your new master and the 2022 file goes in an archive folder with a note. If the compare shows things you don't understand, ask before you decide which is the master. Someone did a decent article on keeping the master straight: https://plctr.com/best-practices-for-plc-program-documentation/