-
Notifications
You must be signed in to change notification settings - Fork 2
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
PEARL Pressure Controller: Test Hardware #6762
Comments
Minor issue spotted - |
@rerpha I'll have a look at that issue this afternoon. |
Device was tested this morning on WISH. Communicated fine apart from issue described above (fixed in PR). Configs and scripts written on WISH with scientist, and scientist is happy that system was behaving as expected. |
@rerpha @Tom-Willemsen As far as we know this has worked fine other than the minor error code fix in the PR? |
Yes |
As a: developer
I would like communicate with both PEARL and WISH to arrange a time to test the Pearl pressure controller. This should be done after testing with the emulator #7114
Acceptance Criteria
Extra Information
Why it is needed?
In order to correctly develop the IOC and OPI, testing of the hardware is required to ensure that work completed as part of #6040 works as expected.
Testing the hardware will also gain insight into what is device specific controller logic and what needs to be developed further using DB logic as the separation between the two is not incredibly clear in the Manual.
Once a clear separation of logic is known and documented, work can continue with adding functionality to PEARLPC OPI device screen which reflects LabView VI functionality.
Where required files/links are
\\isis\shares\ISIS_Experiment_Controls\Manuals\PEARL Pressure Controller\PEARL handbook_v3_5.docx
C:\LabVIEW Modules\Instruments\PEARL\PEARL Pressure Cell Controller
C:\Instrument\Apps\EPICS\support\PearlPressureController\master
C:\Instrument\Apps\EPICS\ioc\master\PEARLPC
C:\Instrument\Dev\ibex_gui\base\uk.ac.stfc.isis.ibex.opis\resources
The text was updated successfully, but these errors were encountered: