Skip to end of metadata
Go to start of metadata

Mostly clean-up today, then Dan and I left to go home.  Gary is still on site, nominally assisting ISS.  We heard yesterday that our air shipment has been received in Porto.  INEGI will deliver the two boxes to the ops center by the time we return in Jan.

rsw01: added Bulgin caps, but realized we needed Binder caps as well.  Stole from motes we intended to use elsewhere.

rsw02: fired up and had 3 issues.  Can't see GPS (on an Titan DSM – shouldn't "rs G" still work?).  Seems to be plugged in with daughter board to front panel properly.  RMY at 20m is spiking – about 1 in 10 samples is bad in the brisk winds we had at the time.  They are detected (diagnostic flag is "A", not "0"), so can be removed, but still not what we want.  This sensor had spikes when tested in the ops center as well, though they had gone away when I took it out of the shipping box. Likely this is a weak transducer.  We could replace it, but eventually won't have any spares.  Finally, mote#12 would start up, then die (no blinking LEDs).  Replacing with a different mote worked fine.  We think that this is the second mote this has happened to.

rsw03: brief stop to read Setra serial number (and get berries from the tree)

rsw04: installed 4-component radiometers and soil sensors at darkhorse, though tower is not yet up.  This will require a 15m cable to the soil mote.

tse12: back to finish up from last night.  Installed soil sensors.  Raised the Ubiquiti to have better line of sight to rne02.  Found that EC100 again was in ASCII mode, so had to drop the box to reprogram through the USB port.  In general, we need to be more rigorous in our prep.  (I think this will be my job in Jan.)

I've created a table of the sites in the EOL Perdigao web page, with some comments.

We left the ops center with 4? towers prepped, primarily the tnw07 60m tower for when INEGI returns.

 

2 Comments

  1. Titans/vipers run  /etc/init.d/gpsclock on bootup.  It, in turn runs the gps_nmea_sysclock nidas program. That program keeps checking for GPS lock, and waits for as long as the value of the lock timeout ( "-l N") parameter, which defaults to 10 minutes. Only after that time does /etc/init.d/tee-gps run, which feeds GPS data to nidas and the gpsd daemon. So you won't see GPS data in the nidas archive, or with "rs G" until the GPS has lock (or 10 minutes have elapsed) after bootup.

    Without a console I don't think you'll see the messages from gps_nmea_syslock when it is looking for lock.  Perhaps the output of that program should be put in the system log, with something like the following in /etc/init.d/gpsclock

    gps_nmea_sysclock $GPS_DEVICE 2>&1 | logger -s -p daemon.info || exit 2

  2. On 11 Dec, I weighed the soil samples Steve took and which he started baking the previous day:

    SiteTray#Tray (tare)wet+tray (no ring)dry+tray (no ring)
    tse1219.3 g114.8 g108.5 g
    rsw0429.3 g106.2 g91.9 g