46 47
buf1 ASCII string for a float (example: “7.01”)
buf2 ASCII string for a float (example: “4.01”)
When some of the above items is missing (for example buf3 when
a 2-point calibration is performed) it is indicated with a “N” letter.
2) Instrument configured for ORP:
If mV is not calibrated: “NN<STX>0<ETX>”
If calibration has been performed: “NN<STX>1 date time N N N
buf1 buf2 N<ETX>”
The items in italic are separated by blank spaces and have the
following formats:
date ddmmyy (“020498” for April 2, 1998)
time hhmm (“1623” for 4:23 pm)
buf1 ASCII string for a float (example: “0”)
buf2 ASCII string for a float (example: “1900”)
None of the items above can be missing when the Instrument is
configured to measure and control ORP (as it always has to be
calibrated on two points).
The event log file is requested through the NNEVF<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.
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.
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”)
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”
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<CR> command is supported by
NNEVN<CR>, the new event request command, which is
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
