GPIB Local Slow Control (LSC) Server Information
What can the GPIB LSC do?
- Able to control most GPIB boards.
- Currently able to control:
- Trigger Conditioner Boards
- Trigger Logic Board
- Front End Boards
- Can be easily extended to control:
- RTF (Receiver/Trigger/Filter) Board
How does the GPIB LSC do this?
- Receives change of run state commands from Run Control.
- The change of run state commands includes pointers to configuration files.
- The configuration files are configuration manager generated.
- Here are a couple sample configuration files:
- Verifies that the change of run state command with the InterLock Manager.
- Writes the appropriate commands to the GPIB boards.
- Have successfully changed settings on the Trigger Conditioner and Trigger Logic boards across the UCSB network.
- Expect to verify that settings can be remotely changed on the Front End Board before the DAQ review.
What if an error occurs?
- Many failures are reported to the Run Control Server
- For example, attempting to write an invalid command to a GPIB board would return a failure to the Run Control Server.
- As we learn the causes for errors, we can make the GPIB LSC correct its own errors.
- We should start to implement this in the near future.
- Errors will be sent to the Error Manager.
- Error Bridge to send the errors has already been implemented.
- However, the GPIB LSC does not yet utilize the Error Bridge to send errors to the Error Manager.
Where can I find documentation on the actual GPIB boards?
Last updated 11/13/01. Questions? Comments? Email: firstname.lastname@example.org.
- Trigger Conditioner board design and diagnostics information is available.
- Trigger Logic board design and diagnostics information is available.
- RTF (Receiver/Trigger/Filter) board documentation can be found here.
- Front End board documentation can be found here.
- Other GPIB documentation can be found here.