Rudy noticed that these sensors were down.  After resetting power on both:

200m: TRH30 9.49 65.31 8 0 1238 129 26\r\n

(fan has low current)

300m: TRH16 -40.14 0.00 9 0 0 0 30\r\n

(sensor is essentially dead)

Both sensors are going through frequent reset cycles as well.  I don't know if we even have replacement sensors ready to go.  (Or whether we should bother with fixing this with one week left in the project, officially.)

(It probably is obvious, but there have been a lot of thunderstorms today that may have helped these sensors die.  Both sonics at each level are still chugging away, though they all are reporting a 0x0f in the status, which may indicate wet transducers?)

 

2 Comments

  1. 300m was being repeatedly power cycled by the check_trh.sh script until May 24, 05:16 UTC:

    From /var/log/isfs/dsm.log, the rserial proc received a HUP signal, perhaps from a human, since it was just before some rserials:

    May 24 05:16:48 300m root: Ifan is 9 . Power cycling port 5
    May 24 05:16:51 300m root: eio 5 0; sleep 2; eio 5 1 status= 0
    May 24 05:16:59 300m root: received Hangup signal, isig=1 
    May 24 05:17:12 300m dsm[12360]: NOTICE|added rserial connection for device /dev/ttyS2
    May 24 05:17:20 300m dsm[12360]: NOTICE|added rserial connection for device /dev/ttyS5

    Since the power cycles don't seem to help, I'll leave it off.

    The 200m TRH is  being repeatedly power cycled, due to Ifan < 10:

    May 24 18:06:11 200m root: Ifan is 8 . Power cycling port 5
    May 24 18:06:14 200m root: eio 5 0; sleep 2; eio 5 1 status= 0
    May 24 18:06:27 200m root: Ifan is 9 . Power cycling port 5
    May 24 18:06:30 200m root: eio 5 0; sleep 2; eio 5 1 status= 0
    ...

    If T and RH with low Ifan is better than nothing, perhaps the check_trh.sh script should be stopped on this dsm, or reduce the value of the limit check from 10 mA to something like 5 and kill/restart it?  On the dsms, the script is in /usr/local/isff/scripts/check_trh.sh.  To run that script on a dsm, do

    check_trh.sh 5 < /dev/null 2>&1 | logger -p local5.warn > /dev/null 2>&1 &

    See /usr/local/isff/projects/CABL/ISFF/scripts/dsm/other.sh. The "5" parameter is the ttyS port number.

     

  2. Steve Oncley AUTHOR

    Yes, the "human" was me.  With UCAR VPN dropping my connection from home every 3 minutes, I was trying to clean up processes that might have been left running....