Skip to content
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

Update from 1-9-1 #1

Open
kgofron opened this issue May 21, 2019 · 2 comments
Open

Update from 1-9-1 #1

kgofron opened this issue May 21, 2019 · 2 comments

Comments

@kgofron
Copy link
Member

kgofron commented May 21, 2019

The update from 1-9-1 did not work properly

#!/ad-nfs/epics/prod/Deb8/production/areaDetector/AD#!/epics/src/areaDetector-1-9-1/bin/linux-x86_64/prosilicaApp
< unique.cmd
< envPaths
=====
#!/epics/src/areaDetector-1-9-1/bin/linux-x86_64/prosilicaApp
errlogInit(20000)
< envPaths
< unique.cmd
@jwlodek
Copy link
Member

jwlodek commented May 21, 2019

The script relies on finding 'AD' in the existing binary name, so because the binary is

#!/epics/src/areaDetector-1-9-1/bin/linux-x86_64/prosilicaApp

it wasn't able to identify the camera type. I could try to make it so that the script tries to figure out the camera type in some other way. areaDetector 1-9-1 had all the drivers in one bin folder which is different than the new individual drivers, which is why the script method is incorrect.

Essentially it finds ADProsilica in the binary path, and then takes the remainder of the path to the binary and appends it to the new binary location

@kgofron
Copy link
Member Author

kgofron commented May 21, 2019

I copied the whole ioc from 10id.
I think that it is not worth rewriting the script for AD 1-9-1 conversion. The old ioc has many more problems than that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants