EPICS Home

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  2021  2022  <20232024  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  <20232024 
<== Date ==> <== Thread ==>

Subject: Problem using ADPICam driver
From: Jörn Dreyer via Tech-talk <tech-talk at aps.anl.gov>
To: tech-talk tech-talk <tech-talk at aps.anl.gov>
Date: Thu, 27 Apr 2023 14:00:22 +0200
Hello,

I have a problem using a PrincetonInstruments PIXIS camera with ADPICam. My 
IOC hangs in the Line PICamConfig("PICAM", 20, 0x5000000, 2, 0x5000000).

The out put of strrace shows:

openat(AT_FDCWD, "/dev/bus/usb/001/004", O_RDWR|O_CLOEXEC) = 23
ioctl(23, USBDEVFS_GET_CAPABILITIES, 0x5621d1320e8c) = 0
ioctl(23, USBDEVFS_CLAIMINTERFACE, 0x7ffd05254f24) = 0
timerfd_settime(13, TFD_TIMER_ABSTIME, {it_interval={tv_sec=0, tv_nsec=0}, 
it_value={tv_sec=8721277, tv_nsec=456792680}}, NULL) = 0
ioctl(23, USBDEVFS_SUBMITURB, 0x5621d130e4e0) = 0
ioctl(23, USBDEVFS_SUBMITURB, 0x5621d13287e0) = 0
read(12, "\1\0\0\0\0\0\0\0", 8)         = 8
poll([{fd=12, events=POLLIN}, {fd=13, events=POLLIN}, {fd=23, 
events=POLLOUT}], 3, 60000) = 1 ([{fd=23, revents=POLLOUT}])
ioctl(23, USBDEVFS_REAPURBNDELAY, 0x7ffd05254bb0) = 0
ioctl(23, USBDEVFS_REAPURBNDELAY, 0x7ffd05254bb0) = -1 EAGAIN (Resource 
temporarily unavailable)

That tells me, that it finds the camera but has somehow problems to 
communicate with it. Looking with the debugger where it hags, reveals that 
this happens already in the call to Picam_InitializeLibrary().
I have setup an udev rules file with the following content:

ATTRS{idVendor}=="0bd7", ATTRS{idProduct}=="a026", MODE="0666", 
GROUP="plugdev"

When I plugin the camera it gets detected by the system::
[8720825.614808] usb 1-10: config 1 interface 0 altsetting 0 bulk endpoint 
0x81 has invalid maxpacket 64
[8720825.614811] usb 1-10: config 1 interface 0 altsetting 0 bulk endpoint 0x1 
has invalid maxpacket 64
[8720825.614978] usb 1-10: config 1 interface 0 altsetting 0 bulk endpoint 
0x81 has invalid maxpacket 64
[8720825.614980] usb 1-10: config 1 interface 0 altsetting 0 bulk endpoint 0x1 
has invalid maxpacket 64
[8720825.615137] usb 1-10: New USB device found, idVendor=0bd7, 
idProduct=a026, bcdDevice= 0.00
[8720825.615139] usb 1-10: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
[8720825.615140] usb 1-10: Product: PIXIS V3.6 
[8720825.615141] usb 1-10: Manufacturer: Princeton Instruments


I tried with different USB ports, optical extender etc. With another software 
that I have the camera works perfectly delivering images. But EPICS somehow 
has a problem with the device. I am using areaDetector R3-12-1.

Any ideas whet could be causing this? It looks like some accessrights are not 
set properly, but I have no clue where.

Regards

Jörn

-- 
Dr. Jörn Dreyer
HIBEF DAQ + Controls
Institut für Strahlenpysik
Helmholtz - Zentrum Dresden - Rossendorf




Replies:
Re: Problem using ADPICam driver Mark Rivers via Tech-talk

Navigate by Date:
Prev: OMS MAXnet motorOmsAsyn module’s autosave whitetiger1123 via Tech-talk
Next: Re: Problem using ADPICam driver 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  <20232024 
Navigate by Thread:
Prev: RE: OMS MAXnet motorOmsAsyn module’s autosave Mark Rivers via Tech-talk
Next: Re: Problem using ADPICam driver 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  <20232024