Experimental Physics and
Industrial Control System

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

 

 

 

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?