-
Notifications
You must be signed in to change notification settings - Fork 2
Revise beam current showing 0 troubleshooting instructions #115
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
| - Visit the beamline - (possibly with electronics if suspecting a hardware problem). | ||
| Software usually doesn't just stop normally when other things are working - right? :smile: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Meh this whole step isn't really that good - most of the time it's "tell DSG to visit the beamline". I'm not sure there's really much that we'd do on the beamline without DSG involvement in this case.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You probably mean TOF signal when you say PPP above? The PPP is the proton charge, the TOF signal is the frame sync. If you get frames but no beam current in DAE but accelerator has beam current, then that is a PPP issue. One issue we have had a few times at start of cycle has been scaling issues on PPP signal leading to ibex dashboard showing higher than ISIS accelerator delivering
| - [ ] data/transfer lights on a DAEII, flickering & transfer lights inactive not a good sign. Could be the link to the PC if transfer lights are not showing activity. | ||
| - [ ] If frame/raw counts are not showing up, a good diagnostic is to put the DAE into "Internal Test Clock". If this works and frames appear, it is likely that there may be a problem with a Time of Flight signal (this often affects more than one beamline. | ||
| - Most importantly, ask the scientists if anything happened around the time of the problem, in a recent case they mentioned someone had moved a cable on an ADC (although this was not the problem!). | ||
| - Look at the lights on the ADC or detector input module cards on the DAE. If no lights flickering, there is no data coming in and this is a good indicator that the HT might be off (a few lights might mean shutter closed or beam off). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Look at the lights on the ADC or detector input module cards on the DAE. If no lights flickering, there is no data coming in and this is a good indicator that the HT might be off
It feels like "get DSG involved" is a few steps before this...
|
Re-ran CI once cloudflare stopped wobbling. |
|
@Chsudeepta could you confirm why this was merged with outstanding review comments from both me and Freddie? |
|
Tracking this here |
No description provided.