Experimental Physics and Industrial Control System
Sorry for never following up on this.
The problem was fixed in this commit:
https://github.com/areaDetector/ADPCO/commit/a32d740aa13244a835131c130beff0f6e55eecd7
Mark
-----Original Message-----
From: [email protected] <[email protected]> On Behalf Of Mark Rivers
Sent: Saturday, October 6, 2018 8:28 AM
To: 'Engbretson, Mark S.' <[email protected]>; [email protected]
Subject: Re: CameraLink and ADPCO
Follow-up:
The problem is with the pcaEdgePlugin that is part of the ADPCO repository. If that plugin is commented out in the startup script the PCO driver and other plugins work fine. We need to find the problem in that plugin.
________________________________
From: Mark Rivers
Sent: Friday, October 5, 2018 4:47 PM
To: 'Engbretson, Mark S.'; [email protected]
Subject: RE: CameraLink and ADPCO
Hi Mark,
Ø I am in the process of attempting a modern deployment of AD, but in all cases so far (AD 2-6 through AD 3-3-2), the images just buffer up to memory.
Can you explain what you mean by "images just buffer up to memory"?
Ø I am assuming that it broke when you implemented threading, but since PCO is derived from CameraLink, I am not sure which module or code needs to be corrected.
I'm not sure what you mean by "implemented threading". I added support for multiple threads per plugin in ADCore R3-0, but that has nothing to do with drivers.
Ø but I never understood how this worked even when it was working.
What are you referring to when you say you did not understand how it worked? The CameraLink and ADPCO driver, or threading?
Ø The last known to be working legacy version on the systems in question seem to date back to AD 2-2
ADCore R2-2 is from March 23, 2015. There are a number of working drivers (e.g. marCCD) that have no substantial changes since 2014. Thus, I don't think there were any changes to ADCore since R2-2 that should have broken the drivers you are working on.
Mark
From: Engbretson, Mark S. <[email protected]>
Sent: Friday, October 5, 2018 4:24 PM
To: [email protected]; Mark Rivers <[email protected]>
Subject: CameraLink and ADPCO
Mark -
Question.
CameraLink and ADPCO have been effectively untouched for the last 2 years. I am in the process of attempting a modern deployment of AD, but in all cases so far (AD 2-6 through AD 3-3-2), the images just buffer up to memory. The last known to be working legacy version on the systems in question seem to date back to AD 2-2.
I am assuming that it broke when you implemented threading, but since PCO is derived from CameraLink, I am not sure which module or code needs to be corrected. I know that generally, all that is required is perhaps the number of parameters tweaked, and some return values changed, but I never understood how this worked even when it was working. Any insight on what, in general, I should be looking for?
[cid:[email protected]]
- Navigate by Date:
- Prev:
Re: PINI set to YES but no VAL field in the record definition Mark Rivers via Tech-talk
- Next:
Re: Is anyone building AreaDetector with Sumo? Mark Rivers 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
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
Re: PINI set to YES but no VAL field in the record definition Mark Rivers via Tech-talk
- Next:
Sumo test Jörn Dreyer 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
2021
2022
2023
2024