Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

ProblemSolution
Camera is not connecting/configuring

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

Another possible cause is the camera link box (black box with two LEDs) is not powered. Both LEDs should be green. The bottom one can be red upon turning on but once connected to the daq and received configuration, it will turn green.

still not connecting/ configuring check camera directly from the nodefind 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 -Scat /proc/datadev_1
Check locLinkRdylink up
If not lockedin locked in then check XPMs, fibers and transceivers

(Opal and Piranha do not use kcuSim or kcuStatus, only HSD and timing (To Be Verified))

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:

laneexponentlane mask (hex of exponent)
02^0=10x01
12^1=20x02
22^2=40x04
32^3=80x08
42^4=160x10
52^5=320x20
62^6=640x40


...