Page History

The data from the Licor at 16 meters went bad on Oct 2, while our system was not reachable over the network.

http://www.eol.ucar.edu/isf/projects/BEACHON_SRM/isfs/qcdata/plots/2011/10/02/co2_20111002.png^{Image Removed}

The ldiag value averages went from the typical 248-255 range to 216, a jump downwards of 32:around 216.

http://www.eol.ucar.edu/isf/projects/BEACHON_SRM/isfs/qcdata/plots/2011/10/02/licor_20111002.png^{Image Removed}

This CWEX11 logbook entry has some information about the licor diagnostic value:

https://wiki.ucar.edu/x/nougB^{Image Removed}

This morning at around 10:40 MDT, I logged in and looked at the high rate data with rserial. (The 16 meter licor is serial port 11) The diagnostic value is 215 = 11010111 binary. Bit 5 is 0 indicating the PLL is not OK.

32=2^5, so it looks like bit 5 in the diagnostic value has become 0, which is a problem in the PLL/chopper motor. According to the manual:

PLL - Phase Lock Loop offset, indicates the status of the chopper motor. If not OK, there may be a problem with the chopper motor in the sensor head.

Also just noticed there is not data on the plots from the 2 meter licor since 04:00 MDT this morning. That appears to be a moisture issue. I just logged in and did rserial (serial port 2):

rs 2 
255\t0.11124\tOverflow\t0.11690\tOverflow\t2.77\t76.0\t\n
255\t-45877.11718\tOverflow\t-37005.95312^D\tOverflow\t2.78\t76.0\t\n
255\t-59961.00781\tOverflow\t-110557.73437\tOverflow\t2.77\t76.0\t\n
255\t0.86791\tOverflow\t0.94173\tOverflow\t2.79\t76.0\t\n

The \t are tabs between the values. 255 is the ldiag value, indicating a high AGC value, but all other diagnostic bits are OK. The second and fourth values in a message are the raw values for co2 and h2o, which look crazy, and the calibrated values are "Overflow". This will probably clear up when things dry outI will look at some high rate values of ldiag to make sure bit 5 is 0.