Experimental Physics and
Industrial Control System

Jörn Dreyer via Tech-talk <tech-talk at aps.anl.gov> · Thu, 15 Feb 2024 09:40:48 +0100

Hi Mark,

as I mentioned before, I had the same error from a driver I wrote for another type of cameras.
I traced this down into the handleNewImageTask function. In the beginning of the while loop (line 4913 and 4914 in ADPicam.cpp) there are two unlock calls. If I comment those out, the error vanishes. These two calls should be moved towards the end of the while loop.

Regards,

Jörn

Am Mittwoch, 14. Februar 2024, 21:36:01 CET schrieb Mark Rivers via Tech-talk:
> I recommend that you open this as an issue in ADPICAM.  Please include the following:
> 
>   *   A screenshot of the top-level ADPICAM screen.
>   *   The complete output when the IOC starts up.
> 
> Mark
> 
> 
> From: Tech-talk <tech-talk-bounces at aps.anl.gov> On Behalf Of Fernando Ardana via Tech-talk
> Sent: Wednesday, February 14, 2024 4:06 AM
> To: tech-talk at aps.anl.gov
> Subject: ADPICam: epicsMutexOsdUnlock failed: ERROR Operation not permitted
> 
> 
> Hi all,
> 
> I am having some problems with the ADPICAM module. I can connect and acquire images using the sample software provide it by Princeton. In Epics the camera is detected however cannot connect to it. After running by ioc I get:
> 
> PICamConfig("PICAM", 0, 0, 0, 0)
> 
> epicsMutex pthread_mutex_unlock epicsMutexOsdUnlock failed: ERROR Operation not permitted
> 
> epicsMutex pthread_mutex_unlock epicsMutexOsdUnlock failed: ERROR Operation not permitted
> 
> Running asynReport(20) I can see the camera:
> 
> PICam:report Initialized PICam Version 5.13.3.2211
> 
> ----------------
> 
> PICam:report availableCamerasCount 1
> 
> Available Camera[0]
> 
> ---PIXIS-XO: 2KB
> 
> ---1
> 
> ---E2V 2048 x 512 (CCD 42-10)(B)
> 
> ---2702080007
> Any idea of what is wrong?
> 
> Best and thanks,
> Fernando
> 

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System