User Guide

69
answered with the list of events occurred since the last recep-
tion of a NNEVF<CR> or NNEVN<CR> command.
Here is the format for answer to NNEVN<CR>:
“NN<STX>0<ETX>” if there is no new event, otherwise:
“NN<STX>new_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.
“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<CR> or NNEVN<CR> command is
received by the instrument, the new events list is reset and
a following NNEVN<CR> command will be answered
with “NN<STX>0<ETX>” if no event took place in the
meantime. Thus, if the answer to NNEVN<CR> com-
mand is not received correctly, to update a remote monitor
for events, the NNEVF<CR> command for the whole
event log file must be used.
Note After a reset of the instrument, the answer to NNEVN<CR>
is the same as NNEVF<CR> (all events are new).
Note A modified record due to the closing of an error is not trans-
mitted by NNEVN<CR>, so again the NNEVF<CR> com-
mand is needed.
A small subset of the event log file, with information about
the active errors, can be downloaded through the
NNAER<CR> command, always available, even during con-
trolling. The answer is:
“NN<STX>C
1
C
2
C
3
C
4
C
5
C
6
<ETX>”
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”).