[Halld-level1] [New Logentry] Problem with rocfcal10 crate

[Curtis A. Meyer]

Thanks to everyone who helped to resolve this.It was indeed a painful and
unexpected issues during our short run and knowing it is resolved prior to
our net run is very important.

Curtis
---------
Curtis A. Meyer			MCS Associate Dean for Faculty and Graduate Affairs
Wean:    (412) 268-2745	Professor of Physics
Doherty: (412) 268-3090	Carnegie Mellon University
Fax:         (412) 681-0648	Pittsburgh, PA 15213
curtis.meyer at cmu.edu	http://www.curtismeyer.com/



> On Dec 22, 2016, at 8:10 PM, somov at jlab.org wrote:
> 
> Problem with rocfcal10 crate <https://logbooks.jlab.org/entry/3449311>
> Lognumber 3449311 <https://logbooks.jlab.org/entry/3449311>. Submitted by somov <https://logbooks.jlab.org/user/somov> on Thu, 12/22/2016 - 20:08. 
> Logbooks:	HDLOG <https://logbooks.jlab.org/book/hdlog> HDTRIGGER <https://logbooks.jlab.org/book/hdtrigger>
> Entry Makers:	Alex Somov, Ed Jastrzembski
> The problem with the slow readout of the rocfcal 10 crate seems to be solved
> now. The problem appeared to be not simply to debug (as it depended on
> running conditions) and was caused by fadc 250 in slot 13.
> 
> fadc (serial ACDI-461) was replaced by ACDI-416. 
> 
> Data recorded with the rocfcal10 crate during the beam run should not be corrupted.
> 
> (Ed is planning to add some diagnostic features for fadc250 in the future).
> 
> I am planning to run a few more comprehensive checks with
> this crate in January. 
> 
> FCAL high voltages are switched OFF.
> 
> Many thanks to Ed, Bryan, and William for their help.
> 
> Happy Holidays !
> 
> _______________________________________________
> Halld-level1 mailing list
> Halld-level1 at jlab.org <mailto:Halld-level1 at jlab.org>
> https://mailman.jlab.org/mailman/listinfo/halld-level1 <https://mailman.jlab.org/mailman/listinfo/halld-level1>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.jlab.org/pipermail/halld-level1/attachments/20161222/f9a086ae/attachment-0002.html>