Confluence will be unusable 23-July-2024 at 06:00 due to a Crowd upgrade.
...
check the status of the data moving here: Data Mover Monitoring, this page can be seen one the main "pswww" page as well. Take out the nodes with the issue, assuming your problem is limited to a single node. If it's wider spread, it might warrant a call.
Most likely, the recorder process cannot connect to the node that you are trying to run the recording process on. This node depends on the source and is listed in your .iocrc file. You can use serverStat to check on the server health and power cycle if appropriate.
This means your recording process is up and you can connect to the PVs. If this PV does not have well-formed timestamps when you request this (necessary for cameras!), the data the process would want to record cannot be found as the timestamp us used to determine what should be recorded.
First, please make sure the image in the camViewer updates. This means the IOC is up and running. The recorder process uses a special interface on a special machine, so in addition this this, that machine needs to be up (see recorder source and DAQ won't start). If the machine is up, ssh to it (ioc-und-rec01). The data comes through a special interface, so you need to do the following check:
export PSPKG_ROOT=/reg/g/pcds/pkg_mgr
source $PSPKG_ROOT/etc/pspkg_os.sh
export EPICS_CA_AUTO_ADDR_LIST=NO
export EPICS_CA_ADDR_LIST="192.168.0.3:5068 172.21.35.255:5064"
export EPICS_CA_MAX_ARRAY_BYTES=17000000
camonitor ORTS:DMPH:695:RAW:ArrayData -#6
<hopefully data.....>
13_11:46:45:2015-Nov-13 11:46:45,[STATUS ],[STATUS_DATA],-79.95,-79.35,-79.95,-79.75,-156.15,52.25,-860.95,-870.25,-774.25,33.05,49.85,49.85,276,273,275,36,0,0,1200,00:00:04
12_15:30:30:2015-Nov-12 15:30:30,[VERBOSE ],RxDetector::FrameAcquisitionFrameProcessor(83, 0x7f55d403bc20,0x7f55d42d2230) - starting
12_15:30:30:FrameReady: Frame #84 size=7372800 timestamp=59989 ms
13_11:38:45:2015-Nov-13 11:38:45,[STATUS ],[STATUS_DATA],-79.95,-79.35,-79.95,-79.65,-109.25,-109.95,34.05,42.65,45.45,34.75,49.85,49.85,276,273,275,37,0,0,1200,20:50:31
13_11:39:45:2015-Nov-13 11:39:45,[STATUS ],[STATUS_DATA],-79.95,-79.35,-79.95,-79.65,-109.25,-109.95,34.05,42.35,45.45,34.85,49.85,49.85,276,273,275,36,0,0,1200,20:51:31
13_11:40:45:2015-Nov-13 11:40:45,[STATUS ],[STATUS_DATA],-79.95,-79.35,-79.95,-79.75,-156.15,52.05,-860.85,-870.25,-774.15,34.75,49.85,49.85,276,273,275,37,0,0,1200,00:00:04
13_11:41:45:2015-Nov-13 11:41:45,[STATUS ],[STATUS_DATA],-79.95,-79.35,-79.85,-79.65,-156.15,52.05,-860.85,-870.25,-774.15,33.95,49.85,49.85,276,273,275,36,0,0,1200,00:00:04
To recover from that, you need to stop the DAQ process (ctrl+x in the telnet localhost 30099 terminal window) and open the Rayonix software capxure.
Reboot the detector controller (there is a button for that). Re-enable cooling. You might have to quite this process and start again to see the now reasonable temperatures. Once this looks fine, you can quit this software and restart the DAQ process: (ctrl+R in the telnet localhost 30099 terminal window)
...