-
Notifications
You must be signed in to change notification settings - Fork 8
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
Minimal functionality when using reset after power cycling camera #12
Comments
I don't believe I have tested power-cycling the camera without restarting the IOC. I will try it soon. It seems strange that you can't set parameters. In terms of restoring the current settings to the device after a power-cycle, it is a more general problem in EPICS, not just restricted to GigE cameras or ADAravis. When a device is power-cycled without rebooting the IOC we need to push the most recent EPICS PV values down to the device. I have been thinking that this is probably something we could use the autosave module for. The autosave file is designed to have all of the important settings that need to be pushed to the device to restore operation on an IOC reboot. It seems like we could just use autosave to read that file (before it gets corrupted with the new values) and push to the device without doing a reboot. I believe that Michael Davidsaver's branch of aravisGigE had a fix for rebooting GigE cameras, but specific to that driver. I want a more general solution. |
Hello, I have the same problem with a Prosilica camera (the reconnect button has no effect on a disconnected camera), and additionally, if reconnect is pressed whilst the camera is connected, it locks up the camera parameters. Images are still streamed, but parameter changes no longer have an effect. When this happens the following error message appears in the IOC console:
I can confirm that the reconnect functionality works with the same camera when using the aravisGigE module. Thanks, James |
What version of the aravisGigE module are you using? Is it the master branch or one of the releases in https://github.com/areaDetector/aravisGigE, or is it a branch from Michael Davidsaver? |
It appears to be a very old version from March 2015. It is using a Diamond release number (0-3-5dls6) so I am not sure how well it maps to the versions from GitHub. Looking in the git log, the merges seem to come from the master branch. |
I have changed the master branch of ADAravis and ADCore so that one can now do the following without restarting the IOC:
ADAravis required the following changes:
ADCore required the following changes:
The following steps are needed to do this:
|
There are some improvements that should be done.
|
Thanks @MarkRivers this is working great! The beamline and can now move their cameras around as they please and then reconnect in the IOC with no issues. Using autosave to restore settings on reconnect is a nice addition, but just being able to reconnect is a already huge UX improvement in our case. |
Dear Mark, Might it be a good idea to include "configMenu_settings.req" in "ADAutoSaveMenu.req"? Best regards, |
@devilkingsatan666 thanks for pointing that out. I had added configMenu.db to my local commonPlugins.cmd, but not to EXAMPLE_commonPlugins.cmd. I have now added that and made some other minor fixes and pushed to the master branch.
I was including configMenu.req rather than configMenu_settings.req in ADAutoSaveMenu.req. This is the difference between those files:
So the difference is that configMenu_settings.req also saves the enableSave PV, while configMenu.req does not. Since that PV is present and exposed in the OPI "more" screen I have changed ADAutoSaveMenu.req to include configMenu_settings.req instead. |
This issue is resolved, closing it. |
Hi, @MarkRivers !
I have found that when we power cycle a GigE camera, the reset process seems to work and it can acquire frames, but most of the parameters do not work. They get reset to 0 / No / N.A., so we can't see what the values on the camera are, and setting things has no effect, for example AcquireTime, although the readbacks update in the IOC.
Is this something you have seen before?
We are running a version based on R2-1
The text was updated successfully, but these errors were encountered: