PLCDontUQuitOnMe
Member
OP
That being said, I dont understand the need for this feature. IMO plc and hmi programs must be stored on a central server, with version control etc. And with this always current backup, there will be no need to upload from a hmi.
While that would be ideal, as an end user at a plant, things don't always go as planned. I am quite diligent with backups to the server. However, I have maintenance employees who are able to make changes to the AB HMIs, I have engineers bringing in contractors occasionally who may make changes to these as well. I can tell these people until I'm blue in the face to get backups to me or put them on the network, however it doesn't always happen.
So when I go to an AB HMI and am going to make changes, I can verify that the file running on the HMI matches the backup on the network, and I can use the backup on the network, but how do I know someone didn't change something on a screen, download it back to the HMI without changing the file name? Now I change the backup off the network and dump in my changes and overwrite theirs...it's a big issue. That is why I always upload from the HMI, which guarantees I have the latest and greatest.
With our Siemens HMIs, I have to trust the backup on the network is actually what's in the machine. This isn't a huge problem for me because I'm generally the only one who touches the Siemens hardware in the plant, but I can imagine the nightmare if I had others making changes and not putting the backup on the network. It would be a disaster of people overwriting other's changes to the HMI. At least with AB and the ability to upload, it guarantees you have the actual latest version.