700-Bubbler-Man Rev 12 13 Feb 2020
Page 48/51
showing a health status indicator of 7, that indicates a failure of the Datalogger to fully communicate
with the Bubbler and a site visit is required to determine the cause.
If using a non-AXIOM data logger the most common health status indicator will be 4. A “4” means
the Bubbler is still operating normally, but the Bubbler’s SD card’s
13
’ time stamp will not be accurate.
If your data logger can be programmed to set the Bubbler’s date and time every 24 hours (as the
Axiom does), the appearance of this indicator can be mitigated.
Also, for non-AXIOM data loggers, if any configuration change was made or the Bubbler was
rebooted (after a power cycle, for example), the aXCON! command should be issued to clear those
status codes.
B.5.2 Determining Individual Status Codes when Several Indicated
A value returned other than one of the values listed in the table in section B.5 indicates multiple
status/error flags. There are two methods which can be used to determine which health
status/error messages are indicated: converting to binary or calculating.
Method 1) Convert to Binary
Convert the status value to binary – easily done by inputting the value into a programmer calculator
and converting it or using an on-line binary converter. Each health status/error indicator is
identified by a binary Bit. The Bits relate to the place numbers read from right to left, starting at Bit
0, followed by 1,2,3, etc.. A place number which has a “1” indicates that Bit is set. Set Bits identify
the health status/error indicators which have been flagged.
Example: The healthstatus/error indicator value returned is 1031 after a measurement
command followed by a send data command:
0D0! +5.23+0+23.5+7-1.3+20+30+12.5+1031
1031 converts to the binary sequence 0100 0000 0111 showing Bits 0,1,2, and 10 are set.
The health status/errors indicated by the set Bits are found in the following table:
13
The SD card is used by FTS factory personnel for troubleshooting.
To Next Page
Loading...
