Steve noticed that ports ttyS11 and ttyS12 are no longer reporting any data on rsw04.  After getting rsw04 updated and clearing off the USB yesterday and restarting DSM, those ports are still not reporting.  They were working until Feb 25.  ttyS10 was out for a while also, but it came back this morning at 2017 03 10 12:16:47.339, before the reboot.

[daq@ustar raw_data]$ data_stats rsw04_20170[23]*.dat
2017-03-10,15:58:41|NOTICE|parsing: /home/daq/isfs/projects/Perdigao/ISFS/config/perdigao.xml
Exception: EOFException: rsw04_20170310_155028.dat: open: EOF
sensor                              dsm sampid    nsamps |------- start -------|  |------ end -----|    rate      minMaxDT(sec) minMaxLen
rsw04:/dev/gps_pty0                  35     10   3944084 2017 02 03 09:44:08.995  03 10 15:58:31.569    1.29  0.015 1090606.000   51   73
rsw04:/var/log/chrony/tracking.log   35     15    133438 2017 02 03 09:44:53.133  03 10 15:58:25.024    0.04  0.000 1090616.750  100  100
rsw04:/dev/ttyS11                    35    100  38021353 2017 02 03 09:44:08.517  02 25 09:48:48.136   20.00 -0.016       0.992   60   77
rsw04:/dev/ttyS12                    35    102  38021782 2017 02 03 09:44:12.831  02 25 09:48:48.206   20.00 -0.107       1.390   40  125
rsw04:/dev/dmmat_a2d0                35    208  39114544 2017 02 03 09:44:08.570  03 10 15:58:31.363   12.84  0.034 1090604.875    4    4
rsw04:/dev/ttyS10                    35  32768    767733 2017 02 03 09:44:13.130  03 10 15:58:31.137    0.25 -0.031 1132080.875   12  104

Steve tried connecting to the ports directly yesterday and did not see anything.  After the reboot, I still don't see anything either.  This is a viper, so I'm thinking ports 11 and 12 are on the second emerald serial card, and these log messages are relevant:

[   41.641774] emerald: NOTICE: version: v1.2-522
[   41.842945] emerald: INFO: /dev/emerald0 at ioport 0x200 is an EMM=8
[   41.871947] emerald: WARNING: /dev/emerald1: Emerald not responding at ioports[1]=0x240, val=0x8f
[   41.881346] emerald: WARNING: /dev/emerald1: Emerald not responding at ioports[2]=0x2c0, val=0x8f
[   41.890757] emerald: WARNING: /dev/emerald1: Emerald not responding at ioports[3]=0x300, val=0x8f

 

4 Comments

  1. Gordon Maclean

    serial ports ttyS5 - ttyS12 are the 8 ports on the first emerald.

    What does "sudo cktty 11 12" report?

    1. Steve Oncley

       11: uart:ST16654 port:F1000130 irq:3 tx:3 rx:5860440 RTS|CTS|DTR|DSR|CD|RI

      12: uart:ST16654 port:F1000138 irq:3 tx:14 rx:4683916 fe:68 RTS|CTS|DTR

  2. Steve Oncley

    As of a little over an hour ago, all of these sensors are now reporting.  I'm not sure what/who happened (I was in a meeting).

     

  3. Gordon Maclean

    The framing errors (fe:68)  on 12 (licor?) are a little concerning, especially if they continue to grow. Seems that something was amiss (cable disconnected, etc) for a short time.

    The "irqs" command is also useful on emerald ports. If the interrupts on "PC104 serial" are high, then somethings is amiss.  I would expect interrupts to be less than 200/sec.

    Back in Manitou days a floating RTS/CTS line on the LICORS caused many hundreds of interrupts/sec.