coxy134
Member
First hello to everyone
Right as for the daft question.........
My company has a policy that we must verify our PLC's programme every couple of years.
Few days ago as per company protocal I start up RS500 using a backup file, connect across network, go online (providing verifcation accepts)and then do a save as then date our files as thus.
e.g (plcname)_(version number)_(date)
e.g PUMPCONTROL_V1.0_180919
Monday I connected to a PLC with an image file dated 160316, did "a save as" using above naming protocol, did not upload or download, ticked yes to save data values and saved as 160919.
Tuesday went online using the filed saved as on Monday (160919) and came up saying files did not match?
Tried the old file 160316 and went online no probs.
compared both files and only difference were data tables?
Did a "save as" once again while online and saved as 170919, went back online and all ok??
Have I done something wrong that mondays file would not work on Tuesday?
Done this hundreds of times no issue!
Thanks
Right as for the daft question.........
My company has a policy that we must verify our PLC's programme every couple of years.
Few days ago as per company protocal I start up RS500 using a backup file, connect across network, go online (providing verifcation accepts)and then do a save as then date our files as thus.
e.g (plcname)_(version number)_(date)
e.g PUMPCONTROL_V1.0_180919
Monday I connected to a PLC with an image file dated 160316, did "a save as" using above naming protocol, did not upload or download, ticked yes to save data values and saved as 160919.
Tuesday went online using the filed saved as on Monday (160919) and came up saying files did not match?
Tried the old file 160316 and went online no probs.
compared both files and only difference were data tables?
Did a "save as" once again while online and saved as 170919, went back online and all ok??
Have I done something wrong that mondays file would not work on Tuesday?
Done this hundreds of times no issue!
Thanks