We plan to have a large number of stand-alone installations each running an identical small (MachineHMI v10) application. One thing I haven’t yet worked out with regard to Tatsoft, is how you go about updating the application on a remote installation from a development machine while retaining the tag values and history of the remote installation.
That is, having made changes to the application, how do you ‘download’ the updated application to a remote installation without losing its configuration, history etc.
If anyone can point me to documentation that outlines this process it would be appreciated. I have looked, but didn’t find anything that clearly described this process.
I found this page in the documentation but .. as far as I can tell .. it doesn’t have an option that describes my requirement. Hopefully it does .. and it just isn’t clear to me yet.
In this case, the update process is quite simple, the only required change is replacing the .dbsln project file.
You can replace the project file directly on the remote installation, and this will not affect tag values, historical data, or local configurations, because the .db files handle those separately:
.dBAlarm stores alarm values;
.dBHistorian stores historical data;
.dbRetentive keeps the last value of tags before the solution shuts down.