Page History

...

Problem

Solution

Camera is not connecting/configuring

Select Open console in ProcStat and click on the camera
Press cntrl-X and observe the log

still not connecting/ configuring check camera directly from the node

find the node running the camera
> grep #piranha# #TMO.cnf# (replace detector and cnf file with appropriate values)
note node name and lane
ex: "{ host: 'drp-srcf-cmp007', id:'tmo_atmpiranha_0', flags:'spu', env:epics_env, cmd:drp_cmd0+' -l 0x1 -D piranha4'},"

> ssh X drp-srcf-cmpXXX

check file system

> ls -al (...)

if command reports nothing, then file system is currupted and computer needs restarting:
> /cds/group/pcds/admin/ipmicreds/psipmi power reset

check kcu linkup

> kcuSim -S
Check locLinkRdy
If not lockedin then check XPMs, fibers and transceivers

Mona: Is this true? Matt W. said that nodes with Opal for example, don't have kcu* tools. Maybe kcuSim only works on Wav8?

check devGui

Stop any other running instance of DAQ using same platform number

Open devGui directly on the node:

> cd cameralink-gateway

check cameralink version:
must be v8.2.3 (as for 2024-06-03)
If not,
> git pull --rebase
> git checkout v8.2.3
> git submodules update

> cd cameralink-gateway/software
> python scripts/devGui --pgp4 0 --laneConfig 0=Piranha4 --pcieBoardType Kcu1500 --enLclsII 1 --enableConfig 0 --startupMode 1 --enVcMask 0

Replace detector name with: Piranha4 or Opal1000
(remove --enVcMask 0 if you want to talk to the FEB, this allows to run the DAQ at the same time)
Also remember that:

lane	exponent	lane mask (hex of exponent)
0	2^0=1	0x01
1	2^1=2	0x02
2	2^2=4	0x04
3	2^3=8	0x08
4	2^4=16	0x10
5	2^5=32	0x20
6	2^6=64	0x40

...

Page tree

Versions Compared

Old Version 5

New Version 6

Key