Gordon Nov 9

Chris substituted Paroscientific 6000 nano-barometers for the Vaisala PTBs at site 10 and at 1 meter on the main tower.

He will add a Paro 6000 to site 5 later today. Site 5 doesn't currently have a barometer, and he needs to modify the 1m boom.

The barometers were reporting at 1 Hz in some other units than millibars:

*000111.95841\r\n
*000111.95840\r\n
*000111.95839\r\n
*000111.95844\r\n

I sent them the commands documented in http://wiki.eol.ucar.edu/sew/ISFS/SensorInformation/NanoParo, so that they report at about 13 Hz, in millibars.

With this modification, site 5 becomes a Aph station, rather than a Ah. On that DSM, I've left its hostname as Ah5, and just added the barometer to the catalog for Ah_DSMs.

For a short period of time I ran an Aph config on 5, which garbled up the sensor <-> id mapping:

  • 0.5m TRH on port 1 ingested as barometer, id: 5,10
  • 2m TRH on port 5 ingested as 0.5m TRH, id: 5,40
  • handar on port 6 ingested as 2m TRH, id: 5,50
  • PWR mote on port 7 ingested as Handar, id: 5,60

Depending on whether the data records parse with the wrong sensor tag, data will need to be edited out. I believe they are all in the file Ah5_20121109_180123.dat, and the real-time isfs file. The file Ah5_20121109_182039.dat has the correct config (Ah_DSM with the barometer added to port 8)

Updated the XML on the servers (gully, flux and at EOL). On the servers, Ah5 is now an Aph_DSM.