Page History

...

FEB	FEB SN	Flange Board (HW)	Flange Channel	I At Boot (AnaN, AnaP, Digi)	I Mod ON	I Mod ON + Config	Ctrl Ch (dpm / ch) (1 is top cob)	Fiber (ctrl / Data)	jTag OK	Feb Address	Data Taking	Comment
L0-1t	12	2	2	0.242 - 1.212 - 1.250	0.292 - 2.317 - 1.392	0.292 - 2.833 - 1.322	0 / 3	C / G	Y	0	OK	Lost clock after few hrs up
L2-3t	17	3	0	0.256 - 1.248 - 1.239	0.317 - 2.319 - 1.314	0.313 - 3.112 - 1.313	0 / 8	D / H	Y	2	OK
L5t	05	0	0	0.236 - 1.216 - 1.287	0.272 - 2.101 - 1.334	0.271 - 2.715 - 1.334	1 / 5	A / E	Y	6	OK	Lost clock after few hrs up. Also lost clock at the transition between download and prestart
L6t	16	0	1	0.249 - 1.222 - 1.362	0.313 - 2.743 - 1.434	0.308 - 3.539 - 1.434	1 / 4	A / E	Y	8	OK	Lost clock during download.
L4b ( In EPICS is L4t)	08	0 (??)	2 (??)	0.248 - 1.241 - 1.248			0 / 4	C / G	Y	5	OK	Only 2 HV pins on one hybrid (instead of 4)
L4t ( In EPICS is L4b)	11	1	0	0.252 1.153 1.374	0.307 - 2.8755 - 1.448	0.304 - 3.564 - 1.449	1 / 8	B / F	Y	4	OK
L5b	20	1	1	0.246 - 1.169 - 1.243	0.306 - 2.242 - 1.346	0.302 - 3.063 - 1.321	1 / 7	B / F	Y	7	OK
L6b	04	1	2	0.248-1.199-1.278	0.307 - 2.705 -1.345	0.304 - 3.525 - 1.348	1 / 6	B / F	Y	9	OK
L0-1b	07	2	0	0.241 - 1.284 - 1.313	0.293 - 2.235 - 1.394	0.293 - 2.931 - 1.394	0 / 5	C / G	Y	1	OK
L2-3b	01	3	1	0.220 - 1.330 - 1.388	0.311 - 2.452 - 1.456	0.305 - 3.286 - 1.456	0 / 7	D / H	Y	3	OK

This table shows a visual of the connections from the cooling plate to the flange, looking from the detector toward the flange. X indicates no connection.

Flange Board Number
	3	2	1	0
FEB	L23T	L1B	L4T	L5T
	L23B	X	L5B	L6T
	X	L1T	L6B	L4B

Current Issues with Back-end.

List of issues we observed during local data taking relative to the Back - End.
NOTICE!!! The dpm numbers in the daq map after 7 are off by one. Example: DataDpm[13] in the DAQ Map is hostname dpm14.

1) dpm[6] seems like it has broken data channels

...

=> Removed connections via breakout box

2) daq-map sometimes shows "Not found" data links

...

Code Block
python SvtCodaDummy.py --local --env JLAB

Start data taking with Coda

Here are the instructions to how to start Coda with clasrun user

Code Block

python SvtCodaDummy.py --local --env JLAB
1) Open a terminal on clonfarm1
> bash
> sconda    #setup conda
> crogue    #activates rogue environment
> startCodaRun    #starts Rogue Coda Run Gui

2) Open a terminal on clon10new
> bash
> sconda; crogue; startCodaDummy   #starts the dummy rogue server

3) Open a terminal on clonfarm1
> runcontrol -rocs

Then:

connectconfigure (hdice1_clonfarm1_clon10new to run with both cobs, hdice1_clonfarm1 to run with top cob, hdice1_clon10new to run with bottom cob)download (for both cobs use hps_v2_noThr.trg)PrestartGo

Coda informations:

We are using conda release 1.4.0, installed in

...

Code Block
sh /data/hps/slac_svt/copy_libraries.sh

Coda / Rogue Errors

WARN: HeartBeat

Error:

setHeartError: 0 >sys 0, mask 21<

WARN: HeartBeat[0]: heartbeat=1628785839(1628785839) heartmask=21

UDP_cancel: cancel >inf:clonfarm1 sys 0, mask 21<

TcpServer(external): wait: request in progress

Effect:

rol BUSY

Causes: multiple. Suggest to add printouts around rogueCodaTrigger and rogueCodaEvent in the hpssvt1.c ROL

1) RssiContributor::acceptFrame[X]: error mistatch in batcher sequence 000000dc : 00000000

This is in the event builder and indicates that we are dropping packets.

This is raised in RssiContributor.cc in the event_builder by acceptFrame thread

Effect:

rol BUSY

Causes: Dropped frames.

Fix: Reset COBs

2) ROL crashes during download→prestart phase showing readback errors on the FEBs

This usually indicates that the FEBs lost clock

Effect: not possible to run

Causes: FEBs lost clock

Fix: Recycle FEBs and run control

Search/Navigation:

Related:

Versions Compared

Old Version 47

New Version 48

Key