Hanna Instruments HI 504 - Manual (Page 35)

69 68
Here is the format for answer to NNEVN:
“NN0” if there is no new event, otherwise:
“NNnew_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
”
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 character.
“new_events_no” is the number of new events and its
format is the ASCII format for a number (“1”, “2”.... “99”,
“100”).
When a NNEVF or NNEVN command is
received by the instrument, the new events list is reset and
a following NNEVN command will be answered
with “NN0” if no event took place in the
meantime. Thus, if the answer to NNEVN com-
mand is not received correctly, to update a remote monitor
for events, the NNEVF command for the whole
event log file must be used.
Note After a reset of the instrument, the answer to NNEVN
is the same as NNEVF (all events are new).
Note A modified record due to the closing of an error is not trans-
mitted by NNEVN, so again the NNEVF com-
mand is needed.
A small subset of the event log file, with information about
the active errors, can be downloaded through the
NNAER command, always available, even during con-
trolling. The answer is:
“NNC
1
C
2
C
3
C
4
C
5
C
6
”
where C
1
C
2
are the ASCII representation of byte B
1
described
below (e.g. B
1
= 0xF3 C
1
= “F”, C
2
= “3”), C
3
C
4
are the
ASCII representation of byte B
2
described below (e.g. B
2
= 0x1D
C
3
= “1”, C
4
= “D”), C
5
C
6
are the ASCII representation of
byte B
3
described below (e.g. B
3
= 0xBE C
5
= “B”, C
6
=
“E”).
• 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) ERNN (e.g. “ER01” for Setp.1 alarm)
event_code
i
(setup) SCNN (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”)
end_date
i
(not active err.) ddmmyy (“020798” for July 2, 1998)
end_time
i
(active errors) N (just the letter “N”)
end_time
i
(not active err.) hhmm (e.g. “0920” for 9:20 am)
desA
i
(errors) N (just the letter “N”)
desA
1
(setup) P
1
P
2
C
1
C
2
C
3
C
4
(setup item format, prev. value)
desA
i
(calibration) “XXPHX”, “XOrPX”, “XX^CX”, “UOLtX”,
“0-201”, “4-201”, “0-202”, “4-202”
desA
i
(cleaning) “AdCL” for advanced cleaning,
“SICL” for simple cleaning
desB
i
(errors) N (just the letter “N”)
desB
1
(setup) P
1
P
2
C
1
C
2
C
3
C
4
(setup item format, new value)
desB
i
(calibration) N (just the letter “N”)
desB
i
(cleaning) N (just the letter “N”)
See above in this section for the description of setup item
format “P
1
P
2
C
1
C
2
C
3
C
4
”.
Events are logged in the event log file in chronological order,
i.e. record number 1 refers to the oldest event. When the
event log file is full, the oldest event is replaced with the
oncoming one.
In order to speed up the updating of a remote monitor for the
events, the NNEVF command is supported by
NNEVN, the new event request command, which is
answered with the list of events occurred since the last recep-
tion of a NNEVF or NNEVN command.