-
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
Superlogics: fix various issues #7058
Comments
Question for @LilithCole ? |
Current changes on sans2d are in support/superlogics:
And in ioc/master
|
ENGINX is not using the IOC. |
|
As a developer i would like various issues with superlogics fixed before the next deployment. Currently SANS2D has a locally modified
iocBoot/iocSPRLG-IOC-01/st-common.cmd
, and modifiedsprlg.proto
insupport/superlogics
The superlogics device is also used on ENGINX, so any changes to e.g. protocol must work there too.HAS_MOD
as these are module not channels,
was not seen and and initial '>' is sent. Using a repeated%7f
worked.each module has an address. We could have HAS_MOD0, HAS_MOD1 etc or have MOD_ADDR0, MOD_ADDR1 etc. The different will be in PV names e.g. is you only have one module with address 2 should PVS have
:0:
or:2:
in them? You could use the $(MOD_ADDR0) in the PV name, so either scheme is equally possibleAcceptance criteria
The text was updated successfully, but these errors were encountered: