67
The event log file is requested through the
NN
EVF
<CR>
command . The maximum length of the event log file is 100
records . Here is the format for the answer:
If there is no generated error or event, the answer has
the format “
NN
<STX>0<ETX>”, otherwise:
“
NN
<STX>
events_no event_code
1
start_date
1
start_
time
1
end_date
1
end_time
1
desA
1
desB
1
...
event_code
2
start_date
2
start_time
2
end_date
2
end_time
2
desA
2
desB
2
...
event_code
m
start_date
m
start_time
m
end_date
m
end_
time
m
desA
m
desB
m
<ETX>”
where
m
is the number of events . Each token is followed
by a blank space, except the last one (“
desB
m
”), directly
followed by the <ETX> character .
“
events_no
” is the number of events and its format is the
ASCII format for a number (“1”, “2” . . . . “99”, “100”) .
The meaning of “
start_date
i
” and “
start_time
i
” is:
• for errors: date and time at which the error was generated;
• for setup events: date and time of a setup item change;
• for calibration events: date and time of a calibration;
• for cleaning events: start date and time of cleaning action .
The meaning of “
end_date
i
” and “
end_time
i
” is:
• for errors: end date and time if the error is not active
anymore;
• for setup events: no meaning;
• for calibration events: no meaning;
• for cleaning events: no meaning .
The tokens format is described here below:
event_code
i
(errors) ER
NN
(e .g . “ER01” for Setp .1 alarm)
event_code
i
(setup) S
CNN
(e .g . “Sr01” for current month)
event_code
i
(calibration)
CALE
(always the string “CALE”)
event_code
i
(cleaning)
CLEA
(always the string ”CLEA”)
start_date
i
ddmmyy (“010798” for July 1, 1998)
start_time
i
hhmm
(e .g . “1735” for 5:35 pm)
end_date
i
(active errors)
N
(just the letter “N”)
