[Dsg-rich] Time for RICH Hardware Interlock configuration file debugging
Matteo Turisini
matteo.turisini at gmail.com
Tue Sep 26 10:41:21 EDT 2017
Hi Tyler,
No data taking is ongoing, you can go ahead. I'll be at the clean room at 11:00 to work on the electronic panel grounding
Matteo
> Il giorno 26 set 2017, alle ore 08:54, Valery Kubarovsky <vpk at jlab.org> ha scritto:
>
> Hello Tyler,
> Matteo was taking some calibration data during this night.
> I am at the meeting right now and can not check the status of this run.
> Matteo please reply Tyler as soon as possible and let Tyler work on cRIO.
> Thanks,
> Valery
>
> From: "Tyler Lemon" <tlemon at jlab.org>
> To: "Valery Kubarovsky" <vpk at jlab.org>, "Matteo Turisini" <matteo.turisini at gmail.com>, "dsg-rich" <dsg-rich at jlab.org>
> Sent: Tuesday, September 26, 2017 8:46:43 AM
> Subject: Re: [Dsg-rich] Time for RICH Hardware Interlock configuration file debugging
> Hello Valery and Matteo,
>
> We still have debugging to do for the cRIO. We are also going to swap the 5V power supply currently in the cRIO chassis with a different 5V supply to help with potential noise issues when the humidity sensors are used.
>
> Is there cosmic data being taken now where the cRIO should not be turned off? Please let us know.
>
> Regards,
> Tyler
>
>
>
> From: "Valery Kubarovsky" <vpk at jlab.org>
> To: "Tyler Lemon" <tlemon at jlab.org>
> Cc: "dsg-rich" <dsg-rich at jlab.org>, "Matteo Turisini" <matteo.turisini at gmail.com>
> Sent: Tuesday, September 26, 2017 8:20:54 AM
> Subject: Re: [Dsg-rich] Time for RICH Hardware Interlock configuration file debugging
>
> Hello Tyler,
> The cRIO GUI now is in the correct state. Two t-sensors are ON the others are OFF.
> However yesterday evening as I wrote I was unable to reset it.
> Did you finish to debug cRIO?
> regards,
> Valery
>
>
> From: "Tyler Lemon" <tlemon at jlab.org>
> To: "Valery Kubarovsky" <vpk at jlab.org>
> Cc: "dsg-rich" <dsg-rich at jlab.org>, "Matteo Turisini" <matteo.turisini at gmail.com>
> Sent: Tuesday, September 26, 2017 7:59:09 AM
> Subject: Re: [Dsg-rich] Time for RICH Hardware Interlock configuration file debugging
> Hello Valery,
>
> This morning, I found the RICH hardware interlock screen with a few, but not all, indicators showing "Disconnected". Is this the strange state you mean?
>
> I was able to get all indicators working properly by doing a hard reboot and the EPICS screen is operating as normal now.
>
> Tyler
>
> From: "Valery Kubarovsky" <vpk at jlab.org>
> To: "Tyler Lemon" <tlemon at jlab.org>
> Cc: "dsg-rich" <dsg-rich at jlab.org>, "Matteo Turisini" <matteo.turisini at gmail.com>
> Sent: Monday, September 25, 2017 7:10:12 PM
> Subject: Re: [Dsg-rich] Time for RICH Hardware Interlock configuration file debugging
>
> Dear Tyler,
> Please let me know what is the status of the RICH cRIO interlock?
> cRIO GUI is in the very strange state. Soft and hard reboot did not help.
> Regards,
> Valery
>
>
> From: "Tyler Lemon" <tlemon at jlab.org>
> To: "Valery Kubarovsky" <vpk at jlab.org>
> Cc: "dsg-rich" <dsg-rich at jlab.org>, "Matteo Turisini" <matteo.turisini at gmail.com>
> Sent: Monday, September 25, 2017 8:52:05 AM
> Subject: Re: [Dsg-rich] Time for RICH Hardware Interlock configuration file debugging
> Hello Valery,
>
> Thank you for your reply.
>
> We will start debugging the cRIO's configuration file now.
>
> Tyler
>
> From: "Valery Kubarovsky" <vpk at jlab.org>
> To: "Tyler Lemon" <tlemon at jlab.org>
> Cc: "dsg-rich" <dsg-rich at jlab.org>, "Matteo Turisini" <matteo.turisini at gmail.com>
> Sent: Monday, September 25, 2017 8:46:54 AM
> Subject: Re: [Dsg-rich] Time for RICH Hardware Interlock configuration file debugging
>
> Hello Tyler,
> We were taking data all weekend.
> It is good time to debug cRIO right now.
> I ended the run11544 with 28650 events.
> Valery
> From: "Tyler Lemon" <tlemon at jlab.org>
> To: "dsg-rich" <dsg-rich at jlab.org>
> Sent: Monday, September 25, 2017 8:32:15 AM
> Subject: [Dsg-rich] Time for RICH Hardware Interlock configuration file debugging
> Hello Valery,
>
> We still need to debug the RICH hardware interlock cRIO's configuration file issues that is preventing the cRIO from automatically loading interlock limits on its reboot.
>
> Is there currently cosmic data being taken? If so, what time will the run end so the cRIO program can be debugged?
>
> Please let us know.
>
> Best regards,
> Tyler
>
> _______________________________________________
> Dsg-rich mailing list
> Dsg-rich at jlab.org
> https://mailman.jlab.org/mailman/listinfo/dsg-rich
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.jlab.org/pipermail/dsg-hallb_rich/attachments/20170926/a0c27084/attachment-0002.html>
More information about the Dsg-rich
mailing list