| Quote: |
|
The DAQ is doing the same thing it was doing a little over a week ago. Namely, it seems to reset itself or otherwise get flustered every minute or so, rendering any useful data requests futile. Let me remind everyone what happened last time:
- Found the problem, tried to fix it using DAQ Reload, etc.
- Thought that the DAQ Rate might have been the issue, so I opened daqconfig and removed some channels
- Restarted daqd
- daqd didn't seem to stay alive---problem
- Got Frank
- Frank observed the issue and saw that I wasn't just drooling on fb0
- Rebooted fb0
- fb0 complained about something on boot and forced a disk check
- A day passed
- Followed some instructions for removing the problem (mainly "yes, yes, yes, yes")
- I mistakenly allowed it to reboot again without changing some manual settings that I needed to have
- fb0 complained about something on boot and forced a disk check
- A day passed
- Frank did some magic in the recovery menu and then reboots fb0
- Everything worked for a week and a half or so
- Step 1
I'm not sure if Frank got an intuitive grasp on what was wrong last time, but it appears to be the same issue. I imagine that going through this list (perhaps with some omissions) will fix the problem again, but that will take a day or so and it may only last a few days after. Suggestions?
|
The realtime stuff all seems to be working fine, it's just the frames that aren't getting written. Running dataviewer on FB1 I can get realtime data for our channels. If I try to get data from the past you get:
Connecting to NDS Server fb0 (TCP port 8088)
Connecting.... done
T0=10-12-10-19-19-05; Length=60 (s)
No data found
Also, the installation of dataviewer on WS2 doesn't seem to work - does anyone know about this? Last thing I knew was that it wasn't installed at all on WS2. It opens fine, but when you try to get data it comes up with "incomplete installation" in the terminal window. |