ComAp IM-NT - History Related Functions

InteliMains
NT
, SW version 3.0
InteliMains-NT-BTB-3.0-Reference Guide.pdf, ©ComAp – June 2013
63
7.11 History Related functions
7.11.1 History Records Adjustment
It is possible to change History records content. Each record contains date, time and cause of the
record as obligatory columns. The rest of columns are configurable.
The history record structure has two parts. The upper part is so-called fast and is written into the
history memory immediately in the moment when the written event occurs. The rest of the record may
be written with a delay max. 100ms. The fast part is intended for fast changing values as e.g. currents,
voltages or power. The parts are separated by a line in the record content list.
1. Values selection tree
2. Buttons for adding/removing values into/from the record structure
3. Buttons for ordering of the values in the record structure
4. Fast history separator. The fast part is located above the separator
5. Estimated number of records depending on record size
6. Record capacity usage indicator
NOTE:
Values that are displayed in green color are recomended to be placed in the fast part.
If the checkbox Add modules to history automatically.. in the Modules tab is checked then all values of
a module are automatically added into the history record when the module is inserted into the
configuration.
7.11.2 Time Stamp function
The controller allows user to define when the history records are written even though there is no other
reason for history record (so called Time Stamp).
It is possible to disable time stamping function (for example when time stamping is not needed and
just floods the history). It may be conditioned by activation of logical Binary Input function
(TIME STAMP ACT) or it may be enabled always.
Period of time stamping may be adjusted from 1 to 240 minutes.
NOTE:
Beware of History flooding by to many Time Stamps (vital information may be overwritten).
7.11.3 Time and Date Intercontroller Sharing
Time and Date are used mainly for History records. These values are shared between controllers that
are connected to CAN. When the value is changed in one controller, it sends its new value to all other
controllers that are connected to the same CAN bus and they update their time and date values and
setpoints accordingly.