<html><body><div style="font-family: times new roman,new york,times,serif; font-size: 12pt; color: #000000"><div>Hello,<br></div><div>After our email, DSG looked at the data available on EPICS for tile 66 with all PMTs stuck at zero. We saw that it is getting the correct low voltage and the PMTs are getting the correct high voltage. We also saw that the FPGA is reading out temperatures. From this, it leads DSG to believe that it is a problem with the hardware responsible for reading the PMT data. </div><div><br data-mce-bogus="1"></div><div><br data-mce-bogus="1"></div><div>Hello Ben,<br data-mce-bogus="1"></div><div>From your email below, it seems that there is an issue with communicating to the tile in question. What would cause a board to stop working correctly at seemingly random time?<br></div><div><br data-mce-bogus="1"></div><div>You mentioned that a power-cycle of LV and the DAQ should fix the issue. Has this been the procedure to fix a "frozen" tile that is not responding in the past?<br data-mce-bogus="1"></div><div><br data-mce-bogus="1"></div><div>Best regards,<br data-mce-bogus="1"></div><div>Tyler<br data-mce-bogus="1"></div><div><br data-mce-bogus="1"></div><div><br data-mce-bogus="1"></div><div><br></div><div data-marker="__HEADERS__"><span style="color: rgb(0, 0, 255);" data-mce-style="color: #0000ff;"><b>From: </b>"Benjamin Raydo" <braydo@jlab.org></span><br><span style="color: rgb(0, 0, 255);" data-mce-style="color: #0000ff;"><b>To: </b>"Valery Kubarovsky" <vpk@jlab.org>, tlemon@jlab.org</span><br><span style="color: rgb(0, 0, 255);" data-mce-style="color: #0000ff;"><b>Sent: </b>Thursday, February 22, 2018 11:28:40 AM</span><br><span style="color: rgb(0, 0, 255);" data-mce-style="color: #0000ff;"><b>Subject: </b>Re: [Dsg-rich] scalers for PMTs on one RICH tile not updating</span><br></div><br><div data-marker="__QUOTED_TEXT__"><span style="color: rgb(0, 0, 255);" data-mce-style="color: #0000ff;">Hi Tyler and Valery,</span><br><br><span style="color: rgb(0, 0, 255);" data-mce-style="color: #0000ff;">I just checked the tile status and see that the link is up to the unit, but it failed to identify the ASIC configuration (so the system doesn't know whether it is a 2 or 3 ASIC tile, so it puts 0) - you can see that in the status printout below for SSP slot 5 fiber 1 (#ASIC is 0, but ChUp is 1 saying a tile exists). This is observed from time-to-time and likely can be fixed by restarting the DAQ, but a power cycle of the low voltage for that tile and CODA restart may be necessary to fix this. This behavior is on the list of issues to clean up - please keep me informed if it becomes a serious problem for you all and I may be able to make it more of a priority.</span><br><br><span style="color: rgb(0, 0, 255);" data-mce-style="color: #0000ff;">Thanks,</span><br><span style="color: rgb(0, 0, 255);" data-mce-style="color: #0000ff;">Ben</span><br><br><br><span style="color: rgb(0, 0, 255);" data-mce-style="color: #0000ff;">clasrun@clondaq6:clasrun> tcpClient rich4 'sspRich_PrintFiberStatus(5)'</span><br><span style="color: rgb(0, 0, 255);" data-mce-style="color: #0000ff;">SSP RICH Fiber Status (slot=5):</span><br><span style="color: rgb(0, 0, 255);" data-mce-style="color: #0000ff;">------------------------------------------------------------------------</span><br><span style="color: rgb(0, 0, 255);" data-mce-style="color: #0000ff;"> Fiber Rst ChUp HrdErr FrmErr ErrCnt EvtEn Valid #ASIC FWRev </span><br><span style="color: rgb(0, 0, 255);" data-mce-style="color: #0000ff;">------------------------------------------------------------------------</span><br><span style="color: rgb(0, 0, 255);" data-mce-style="color: #0000ff;"> 0 0 1 0 0 0 1 1 3 00000001</span><br><span style="color: rgb(0, 0, 255);" data-mce-style="color: #0000ff;"> 1 0 1 0 0 0 1 1 0 00000001</span><br><span style="color: rgb(0, 0, 255);" data-mce-style="color: #0000ff;"> 2 0 1 0 0 0 1 1 3 00000001</span><br><span style="color: rgb(0, 0, 255);" data-mce-style="color: #0000ff;"> 3 0 1 0 0 0 1 1 3 00000001</span><br><span style="color: rgb(0, 0, 255);" data-mce-style="color: #0000ff;"> 4 0 1 0 0 0 1 1 2 00000001</span><br><span style="color: rgb(0, 0, 255);" data-mce-style="color: #0000ff;"> 5 0 1 0 0 0 1 1 3 00000001</span><br><span style="color: rgb(0, 0, 255);" data-mce-style="color: #0000ff;"> 6 0 1 0 0 0 1 1 3 00000001</span><br><span style="color: rgb(0, 0, 255);" data-mce-style="color: #0000ff;"> 7 0 1 0 0 0 1 1 3 00000001</span><br><span style="color: rgb(0, 0, 255);" data-mce-style="color: #0000ff;"> 8 0 1 0 0 0 1 1 3 00000001</span><br><span style="color: rgb(0, 0, 255);" data-mce-style="color: #0000ff;"> 9 0 1 0 0 0 1 1 3 00000001</span><br><span style="color: rgb(0, 0, 255);" data-mce-style="color: #0000ff;"> 10 0 1 0 0 0 1 1 3 00000001</span><br><span style="color: rgb(0, 0, 255);" data-mce-style="color: #0000ff;"> 11 0 1 0 0 0 1 1 3 00000001</span><br><span style="color: rgb(0, 0, 255);" data-mce-style="color: #0000ff;"> 12 0 1 0 0 0 1 1 3 00000001</span><br><span style="color: rgb(0, 0, 255);" data-mce-style="color: #0000ff;"> 13 0 1 0 0 0 1 1 3 00000001</span><br><span style="color: rgb(0, 0, 255);" data-mce-style="color: #0000ff;"> 14 0 1 0 0 0 1 1 3 00000001</span><br><span style="color: rgb(0, 0, 255);" data-mce-style="color: #0000ff;"> 15 0 0 0 0 0 0 0 0 00000000</span><br><span style="color: rgb(0, 0, 255);" data-mce-style="color: #0000ff;"> 16 0 1 0 0 0 1 1 3 00000001</span><br><span style="color: rgb(0, 0, 255);" data-mce-style="color: #0000ff;"> 17 0 1 0 0 0 1 1 3 00000001</span><br><span style="color: rgb(0, 0, 255);" data-mce-style="color: #0000ff;"> 18 0 1 0 0 0 1 1 3 00000001</span><br><span style="color: rgb(0, 0, 255);" data-mce-style="color: #0000ff;"> 19 0 1 0 0 0 1 1 2 00000001</span><br><span style="color: rgb(0, 0, 255);" data-mce-style="color: #0000ff;"> 20 0 1 0 0 0 1 1 2 00000001</span><br><span style="color: rgb(0, 0, 255);" data-mce-style="color: #0000ff;"> 21 0 1 0 0 0 1 1 3 00000001</span><br><span style="color: rgb(0, 0, 255);" data-mce-style="color: #0000ff;"> 22 0 1 0 0 0 1 1 3 00000001</span><br><span style="color: rgb(0, 0, 255);" data-mce-style="color: #0000ff;"> 23 0 1 0 0 0 1 1 3 00000001</span><br><span style="color: rgb(0, 0, 255);" data-mce-style="color: #0000ff;"> 24 0 1 0 0 0 1 1 3 00000001</span><br><span style="color: rgb(0, 0, 255);" data-mce-style="color: #0000ff;"> 25 0 1 0 0 0 1 1 3 00000001</span><br><span style="color: rgb(0, 0, 255);" data-mce-style="color: #0000ff;"> 26 0 1 0 0 0 1 1 3 00000001</span><br><span style="color: rgb(0, 0, 255);" data-mce-style="color: #0000ff;"> 27 0 1 0 0 0 1 1 3 00000001</span><br><span style="color: rgb(0, 0, 255);" data-mce-style="color: #0000ff;"> 28 0 1 0 0 0 1 1 2 00000001</span><br><span style="color: rgb(0, 0, 255);" data-mce-style="color: #0000ff;"> 29 0 1 0 0 0 1 1 3 00000001</span><br><span style="color: rgb(0, 0, 255);" data-mce-style="color: #0000ff;"> 30 0 1 0 0 0 1 1 3 00000001</span><br><span style="color: rgb(0, 0, 255);" data-mce-style="color: #0000ff;"> 31 0 1 0 0 0 1 1 3 00000001</span><br><br><br>----- Original Message -----<br>From: "Valery Kubarovsky" <vpk@jlab.org><br>To: "Benjamin Raydo" <braydo@jlab.org><br>Sent: Thursday, February 22, 2018 8:59:15 AM<br>Subject: Fwd: [Dsg-rich] scalers for PMTs on one RICH tile not updating<br><br>Ben,<br>Please reply to DSG group about the reasons why we have sometimes frozen scalers. <br>Thanks,<br>Valery<br><br><br>Begin forwarded message:<br><br>> From: Tyler Lemon <tlemon@jlab.org><br>> Date: February 22, 2018 at 08:22:50 EST<br>> To: dsg-rich <dsg-rich@jlab.org><br>> Subject: [Dsg-rich] scalers for PMTs on one RICH tile not updating<br>> <br>> Hello,<br>> <br>> DSG noticed this morning that there is there is a group of three PMTs on the scaler map EPICS screen that are not updating. They have all been at zero for a few hours this morning. Attached is a screenshot with the three PMT scalers as zero. <br>> <br>> The PMTs in question are PMT 182, 183, and 184. They all look to be on the same electronic board (tile 66) that is read out in SSP slot 5, fiber 1. The temperatures for this board are still being read.<br>> <br>> Scalers for PMTs not updating for long periods until the IOC is rebooted or something else is done seems to be a common occurrence.<br>> <br>> What would be causing the scalers to stop updating while the temperatures are still read?<br>> <br>> Best regards,<br>> Tyler<br>> _______________________________________________<br>> Dsg-rich mailing list<br>> Dsg-rich@jlab.org<br>> https://mailman.jlab.org/mailman/listinfo/dsg-rich<br></div></div></body></html>