User Guide

67
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) Process controller 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 a 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 Process Control-
ler is configured to measure and control ORP (as it always has to be
calibrated on two points).
Note When the “measurement input selection” item is set to “Digi-
tal Transmitter” the last calibration data retrieved through
this command refer to Digital Transmitter and is stored in that
device.
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”).