The check_trh.sh script just restarted the TRH at 100m because Ifan went below 10. After the power cycle values for Ifan were around 43 mA. After about 40 seconds they settled down to 25.
Ifan.100m has bee weird since 09:40 MDT this morning in this screen grab of ncharts.
Ifan.200m dropped from around 35 to around 23 on May 1.
Rick and I were out to do this today (5 may). Gordon had set up the config yesterday, so it was plug and play. The mast was down from about 10:12 to 11:15 to do this (it took a while to fish the data cable through).
In addition I:
- added a blue cap to the TRH bluetooth connector (I had noticed it was missing during our last trip)
- installed a "double shield" insert around the Tirga thermistor.
T.100m died on Sat (2 May) ~1600. eio doesn't revive it. However, "ddn/dup" did! I noticed that its last message at May 2 22Z was normal. I see nothing in the logs about anything odd happening at this time..
bao rad mote died between 1000-1400 on Sun (3 May), but came back. John's watchdog brought it back. The last message was at 16:11:56.3590Z, then an "Xbee reset" occurs at 19:12:00.1041 (and the reset time was set to 3 hours).
sonic data at 50, 150, and 250m missing for about an hour about 0600 today (4 May), but came back.
About a week ago, Tsoil.x.4.4cm started going bad and has been garbage for the last 3 days. This is the brown-coated probe installed rightside-up. The white epoxy upside-down Tsoil.4.4cm is okay. I note that the white epoxy probe was what went bad at ehs...
I'm preparing to add a nanobarometer to bao.5m.
The TRH at 250m went out last night for about an hour, right as the checker script was power cycling it because the temp was high:
/var/log/isfs/dsm.log:May 1 01:34:50 250m root: temperature is -61.48 . Power cycling port 5 /var/log/isfs/dsm.log:May 1 01:34:54 250m root: temperature is 168.51 . Power cycling port 5 /var/log/isfs/dsm.log:May 1 01:39:54 250m root: temperature is 168.59 . Power cycling port 5
It came back on its own. Then this morning the Ifan value went to 0. This could have been because I was testing rserial at that time. I see some of the characters I was typing in the TRH output, such as "|fgre". So perhaps I caused this second issue. At 16:48 UTC I power cycled the TRH and Ifan came back.
2015 05 01 16:14:38.1284 1 37 TRH32 9.30 97.48 39 0 1226 201 124\r\n 2015 05 01 16:14:39.1384 1.01 37 TRH32 9.30 97.48 39 0 1226 201 124\r\n 2015 05 01 16:14:40.1384 1 37 TRH32 9.30 97.48 38 0 1226 201 120\r\n 2015 05 01 16:14:40.5740 0.4357 38 \rTRH32 9.30 97.48 38 0 1226 201 119\r\n 2015 05 01 16:14:42.1484 1.574 37 TRH32 9.30 97.48 38 0 1226 201 119\r\n 2015 05 01 16:14:43.1584 1.01 37 TRH32 9.30 97.48 38 0 1226 201 119\r\n 2015 05 01 16:14:44.1584 1 37 TRH32 9.30 97.48 38 0 1226 201 119\r\n 2015 05 01 16:14:44.6040 0.4456 44 f|freTRH32 9.34 97.49 38 0 1227 201 118\r\n 2015 05 01 16:14:47.2784 2.674 34 TRH32 9.30 97.48 0 0 1226 201 0\r\n 2015 05 01 16:14:48.2784 1 34 TRH32 9.30 97.48 0 0 1226 201 0\r\n 2015 05 01 16:14:49.2884 1.01 34 TRH32 9.30 97.48 0 0 1226 201 0\r\n 2015 05 01 16:14:50.2884 1 34 TRH32 9.30 97.48 0 0 1226 201 0\r\n 2015 05 01 16:14:51.2984 1.01 34 TRH32 9.30 97.48 0 0 1226 201 0\r\n 2015 05 01 16:14:51.5941 0.2956 35 \rTRH32 9.30 97.04 0 0 1226 200 0\r\n 2015 05 01 16:14:53.3084 1.714 34 TRH32 9.34 97.49 0 0 1227 201 0\r\n 2015 05 01 16:14:54.3084 1 34 TRH32 9.30 97.48 0 0 1226 201 0\r\n 2015 05 01 16:14:55.3184 1.01 34 TRH32 9.30 97.48 0 0 1226 201 0\r\n