MULTICAL® 403
Kamstrup A/S · Technical description · FILE100000166_B_EN-55121689_M1_07.2023
7.9 Info and config logger
7.9.1 Info logger
Every time the information code changes, the below-mentioned registers are logged.
Date (20YY.MM.DD) Year, month and day of logging time
Clock (hh.mm.ss) Time
Info Information code on above date
E1 Heat energy
E3 Cooling energy
It is possible to data read the latest 50 changes of the information code as well as the dates the changes were made.
When the information code is read from the display, the latest 50 changes including dates can be read. All of the 50
changes can also be read by means of the PC program LogView HCW.
Info event
Every change of a parameter of the info code results in an info event if the selected country code is configured with
the parameter. It is therefore not certain that all parameters result in an info event.
An info event results in accumulation of the info event counter as well as logging in the info logger. This does not
apply whilst the meter is in transport state or if the calculator top and base are physically separated.
Reconfiguration of active parameters of the info code will influence future info codes, whereas all logged info codes
remain as they were at the time of logging.
7.9.2 Config logger
Every time the configuration is changed, the below-mentioned register types are logged. Thus, it is possible to data
read the latest 25 changes of the config log as well as the date the change was made. The meter permits only 25
changes, unless you break the legal seal and carry out a total reset of the meter, which also resets the config log.
Note: The 25
th
change of configuration must be carried out on the installation site, i.e. either via ”SETUP loop” or via
METERTOOL HCW.
Date (20YY.MM.DD) Year, month and day of change
Time (hh.mm) Time
Configuration number The new configuration number
E1, E3 and V1 Counts are saved just after reconfiguration
Hour counter Hour counter is saved
t offset The temperature offset value is saved
The meter will always carry out a config logging if the user has had access to ”SETUP loop”, no matter whether the
user has changed the configuration or not.