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 2021 2022 2023 <2024> 2025 | 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 2021 2022 2023 <2024> 2025 |
<== Date ==> | <== Thread ==> |
---|
Subject: | RE: Asyn device support does not reconnect |
From: | Mark Rivers via Tech-talk <tech-talk at aps.anl.gov> |
To: | Miroslaw Dach <mdach at lbl.gov>, EPICS Tech-Talk <tech-talk at aps.anl.gov> |
Date: | Sat, 9 Nov 2024 00:22:30 +0000 |
Hi Mirek,
You need to be specific about what you mean by “connection with the camera is lost”. There are at least 2 cases:
I just tested ADVimba for case 1, unplugging the Ethernet cable for about 15 seconds. After a few seconds, these messages appear on the IOC console: 2024/11/08 18:04:53.889 ADVimba::connectionCallback calling disconnect() 2024/11/08 18:04:54.139 13VMB1:cam1:PoolPollStats devAsynInt32::reportQueueRequestStatus queueRequest error port VMB1 not connected When this happens the green Connected message on the OPI screen changes to red Disconnected. This alerts the user to the problem. After reconnecting the Ethernet cable the following message appears on the IOC console: 2024/11/08 18:05:05.896 ADVimba::connectionCallback calling connect() The Disconnected message on the OPI screen changes back to Connected. I am then able to operate the camera again normally. Do you see the same thing? If the camera is power-cycled (case 2) then the same messages appear on the console and on the OPI screen. I find that I can still communicate with the camera. However, it does not stream
images correctly. I think that power-cycling the camera leads to the same issues that Matt raised for the Galil controller. When the camera is power cycled its settings (readout region, exposure time, trigger
mode, etc.) will be back to power-up defaults and completely out of sync with the EPICS settings. How do you propose that it should work in this case? The simplest thing to do it to restart the IOC.
In ADCore R3-12 I added the following: ADAutoSaveMenu.req
In principle this should allow you to download the last autosaved settings after the camera is power-cycled. However, this has not been extensively tested, and when I just tried saving
with configMenu I got a failure. I need to track that down. Mark From: Tech-talk <tech-talk-bounces at aps.anl.gov>
On Behalf Of Miroslaw Dach via Tech-talk Hi All, We are using in ALS various drivers which are based on Asyn. Some of them do not auto reconnect. I wanted to consult with you what could be done in order to make them auto reconnect. 1. Galil (Galil-4-0-02) motion controller driver. When the connection is lost it reconnects and crashes straight after with the message: free(): invalid size or munmap_chunk(): invalid pointer example: Disconnected from DMC4040 Rev 1.3i-SER at 131.243.196.71 2. Vimba ccd camera driver simply does not reconnect when the connection with the camera is lost. We use the driver for the Manta G-235B camera (with the Allied Vision 1800 U-501 NIR cheap) and also older cameras Manta_G-145 . We used before the Prosilica driver what was doing the auto connect but Vimba does not do that. 3. Custom stream device support driver which uses the call: drvAsynIPPortConfigure("custom_device", "HW_dev:8003",0,0,0) The ioc does not reconnect when the underlying hardware is off for a longer time (2-3 hours) and powered back. Best Regards Mirek |