9/19/16

Summary: Rain from remnants of TS Julia is still intermittent and expected the rest of today.

                  Motes at 15 and 9 are not reporting, efforts are being made to fix from the command trailer instead of making another saturating boat ride.

                  Shift change: Steve S. leaves today

Actions past 24 hours:

  • Yesterday (9/19) boat tour to clear NR01 lenses

To dos:

  • Reshoot boom angles (just because...)

Sensor Status: 

  • Motes from 9 and 15 lost data starting last night. 9 fixed itself this morning. Suspect a software issue with the bluetooth module in 15 (Gary is working on this), though it is odd that its onset is coincident with rain.

T/RH:  ok
P: ok; Pirga still lower by about 1mb
2D Gill: ok
csat u,v:  ok
csat ldiag: ok
csat w, tc: ok
EC150: ok
motes: ok
Wetness: ok
radiation: ok
Tsoil: ok
Gsoil: ok
Qsoil: ok
Cvsoil: still need to have John/Steve S come up with a fix (in Boulder)

Rainr: ok
Vbatt: ok

  • No labels

1 Comment

  1. Gary Granger

    Regarding mote at S15: the log messages about connection errors were for btspp:mote-D607, but that's the mote that had been moved to another site, so of course the connection was never completing.  Unfortunately, I've noticed before that when one bluetooth connection gets hung up, it can prevent any others from being attempted, so btspp:mote-D57A was never tried.  I changed the configuration on s15 to give the m1 mote a devicename of /dev/ttyS8, since that is how m3 had been left and that seemed to work.  DSM opens ttyS7 and ttyS8 without errors, but no data ever appear, and m2 remains a bluetooth device.

    However, when I restarted dsm with the config change, it then got hung up on the btspp:mote-D57A connection, so presumably the USB bluetooth device on the dsm end was in some foul state.  I could see D57A with 'hcitool scan' while dsm was not running, but dsm could not connect.  So I next tried the steps in the JIRA issue, but I only got as far as stopping bluetoothd before the ssh connection hung.  Since then the DSM has stopped responding to pings and I cannot log back in.  Worse, the dsm was left not running, so no data are being recorded.  I suspect this is not just an interruption to the Internet connection, I suspect the dsm is hung and needs to be power cycled.

    I think the good news, though, is that when it reboots it will only try to connect to the one remaining bluetooth radio, and I think that should work.