more quick actions
minimize quick actions
Topic starter
Archiving system variables may be necessary for debug/diagnostic purpose or for archiving alarm counters.
However, in redundant environments or multistation projects in general, this seems to be quite complicated.
Regarding the specific nature of these internal and local variables what is the good configuration for archiving local system variables?
I guess it is mandatory to include the station id in the archive table?
How do the stations behave when playing back the recorded data, i.e. displaying it in a trend viewer? I mean will the historical server return all values recorded on all stations?
Is it even feasible what I am asking for?
Posted : 16/04/2013 6:17 pm
I think you have to create a set of variables for each station.
AUDIT.STATION1.LOCALHOST.RESSOURCE.RAM for example which is produced by station 1 and the result of the basic expression = SYSTEM.LOCALHOST.RESSOURCE.RAM
All these variables are then archived and clearly retrieved with log viewer and trend viewer.
Posted : 16/04/2013 6:28 pm
If you need to archive SYSTEM variable local to each station in your architecture, I agree with Ludo on that.
Another reflexion on SYSTEM variable is that some SYSTEM variable can be modify so as to be produce by a server list and consume by a client list.
The variable created when configuring native driver in PcVue for instance are in that category.
But there is no list that I know of that that specify which of the SYSTEM variable falls into that category.
Posted : 16/04/2013 7:47 pm