-
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
Kepco BOP PSU: Investigate communications issue seen on Muon Zerofield system [Timebox: 2 days] #7778
Comments
From Ticket #7719 As a developer I would like to remove ExtraInput = ignore from the kepco protocol https://github.com/ISISComputingGroup/EPICS-kepco/blob/master/kepcoApp/protocol/kepco.proto as it potentially increases the chance of a corrupt reply being interpreted as a good one. We may also want to consider adding ;*OPC? to the end of set commands which should return 1 when it completes, however i might have already tries this and found our cards did not support it |
Impeded until can get an opportunity to test the suggested changes to the Kepco protocol file. |
One of the kepcos giving issue was right on the full/quarter range point - as additional accuracy not needed have added #7945 as this continued switching may cause a delay? |
has this been patched onto MuSR? if so, it should be added here https://github.com/ISISComputingGroup/IBEX/wiki |
As a muon (or neutron) instrument scientist, I would like the communications with my Kepco BOP PSU to be reliable.
While investigating recent zerofield issues seen on MuSR, it was discovered that the PSU occasionally sent (or a reply was misinterpreted) an invalid setpoint. e.g. actual setpoint: 0.74, readback: 9.74.
Acceptance criteria
Notes
ExtraInput = Ignore;
from the Kepco protocol file. Also see this ticket for more information.The text was updated successfully, but these errors were encountered: