[Primexd] [New Logentry] Status of channels

[gleasonc at jlab.org]

Logentry Text:
--
Four channels were checked for signal today. The result is summarized below. First, the signal was checked at the end of the cable that plugs into the fadc. If we see a signal here, it is reasoned that the fadc channel is bad. If there is no signal at the end of the cable, we then plug the scope directly into the base. If there is a signal coming out of the base, we can reason that the cable is bad. It is likely that one of the end of the cables needs to be replaced. 

In summary, there are 3 bad fadc channels and 1 bad cable. Chris will repair try to repair the cable during the next access. Two of these fadc channels have been known to be bad for a long time. 

X	Y		crate		slot	channel	Base	comm	Signal at fadc?	Signal at base?                Fix
-24	7	D2	2	BOT	            10	3	23138	7499540	      yes	                         yes                    bad fadc channel	
13	5	D2	2	MID	            18	1	21694	7497657	      yes	                         yes                    bad fadc channel	
1	-23	D2	2	BOT	              8	0	22963	7500800	      yes	                         yes                    bad fadc channel	
26	0	D2	2	BOT	              9	13	23286	7566021	       no	                         yes .               	bad cable

One base was also replaced today. It was replaced due to losing communications with epics and it was not brought back online with a power cycle.

X	Y	Reason	Base ID	New Base ID	Old CAN ID	New CAN ID
22	-3	comm	22085	22435	7505612	7531904

After turning on the FCAL after the access, there is one channel showing up with 0 HV (X,Y)=(4,-8). This channel was working fine before I entered the FCAL. I think it will return to operational in the next 24 hours or so. 


---

This is a plain text email for clients that cannot display HTML.  The full logentry can be found online at https://logbooks.jlab.org/entry/3637827
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.jlab.org/pipermail/primexd/attachments/20181212/4a5d1259/attachment.html>