Page History
...
Problem | Solution | ||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Camera is not connecting/configuring | Select Open console in ProcStat and click on the camera 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 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: | ||||||||||||||||||||||||
check kcu linkup | > kcuSim -Scat /proc/datadev_1 Mona: Is this true? Matt W. said that nodes with Opal for example, don't have kcu* tools. Maybe kcuSim only works on Wav8?(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 check cameralink version: > cd cameralink-gateway/software
|
...