Versions Compared

Key

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

...

Occasionally after power cycling the camera or everything if there was a power outage the USB fiber extender will come back in a bad state where it won't communicate with the camera. One time we saw these errors in /var/log/messages when the VLS camera broke:

Code Block
May 27 14:03:38 daq-rix-andor-01 kernel: usb 1-2.4.1: usbfs: interface 0 claimed by usbfs while 'andor' sets config #1
May 27 14:03:39 daq-rix-andor-01 kernel: usb 1-2.4.1: usbfs: interface 0 claimed by usbfs while 'andor' sets config #1

This seems to happen to the direct beam path andor an order of magnitude more often than the one on the VLS. Too recover from this when it happens do the following procedure:

...

For camera communication errors ("Unknown" in EDM "Model Number" field) can look for "USB disconnect" error messages in /var/log/messages.  Can see device numbers with "lsusb | grep Andor" and compare to device numbers in /var/log/messages.

Workaround for RIX ANDOR-DIR hang

This is for when the camera is visible with "lsusb | grep Andor" (note uppercase "A") but the camera isn't communicating:

  • Execute the following command on daq-rix-andor-01 as superuser: ~ddamiani/reset_andor.sh 1-2
  • Restart one IOC (e.g. DIR), wait for it to finish
  • Restart the second IOC, wait for it to finish

...