EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  <20212022  2023  2024  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  <20212022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: ADVimba disconnect
From: Mark Rivers via Tech-talk <tech-talk at aps.anl.gov>
To: John Dobbins <john.dobbins at cornell.edu>
Cc: "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov>
Date: Fri, 30 Apr 2021 16:02:07 +0000
Hi John,


The ADVimba driver does not implement the connect() and disconnect() methods to actually disconnect the driver from the camera.  When you do a "disconnect" you are currently only disconnecting the driver from device support, so records won't talk to the driver.


We probably should implement the connect() and disconnect() methods in the driver.  But this has some problems, some of which are discussed in this Github issue for ADAravis:

https://github.com/areaDetector/ADAravis/issues/12


For example, how should ADVimba behave if you do the following:


- Disconnect the camera from ADVimba

- Use their Vimba Viewer software to change some settings

- Disconnect Vimba Viewer

- Reconnect ADVimba

Should ADVimba:
- Pull the new settings from the camera and update the EPICS PVs
or
- Push all of the existing EPICS PV values down to the camera

Neither is trivial to implement.  And this problem is much more general than just ADVimba, or just areaDetector drivers.  Can we make a general solution for EPICS IOCs to handle devices that have been power-cycled or otherwise reset without restarting the IOC?

One thought I had was to use the functions in autosave for this.  autosave is already saving the settings that should be pushed to the device when the IOC starts up.  We could arrange for drivers to optionally push all of those values to the device when it detects or is told that the device has been reset.

Mark

________________________________
From: Tech-talk <tech-talk-bounces at aps.anl.gov> on behalf of John Dobbins via Tech-talk <tech-talk at aps.anl.gov>
Sent: Friday, April 30, 2021 9:21 AM
To: tech-talk at aps.anl.gov
Subject: ADVimba disconnect

All,

Apologies if I have overlooked something in the documentation.

I am using ADVimba 1.1 ADCore 3.7, SDK 1.8

Under asynRecord I select noAutoConnect and then disconnect.  The IOC then reports 'disconnected', however when I then start the Vimba Viewer software supplied by Allied Vision, that software reports the camera as unavailable, i.e. still connected.

Do others see this?

John Dobbins

Research Support Specialist
Cornell High Energy Synchrotron Source
Cornell University

www.chess.cornell.edu<http://www.chess.cornell.edu>




References:
ADVimba disconnect John Dobbins via Tech-talk

Navigate by Date:
Prev: Re: Larger build products in base-7.0.5 Johnson, Andrew N. via Tech-talk
Next: Re: Larger build products in base-7.0.5 Kevin Peterson via Tech-talk
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  <20212022  2023  2024 
Navigate by Thread:
Prev: ADVimba disconnect John Dobbins via Tech-talk
Next: Larger build products in base-7.0.5 Kevin Peterson via Tech-talk
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  <20212022  2023  2024 
ANJ, 30 Apr 2021 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·