Re: Image Acquisition Issue with AreaDetector/ADAravis

[Jörn Dreyer via Tech-talk <tech-talk at aps.anl.gov>]

Hi Grass,

did you check with arv-tools-0.8 if the cameras are visible by the system? This should give some otput at least for the fake camera.
Regarding the USB camera you could check whether the access rights on the device file used are set up correctly.
Most recent Lnux distributions dont allow any user than root to get access to devices. You need to setup udev rules to grant access to
some group (e.g. plugdev) that your user running the IOC is a member of.

Regards,

Jörn

Am Dienstag, 11. März 2025, 23:56:33 Mitteleuropäische Normalzeit schrieb Wang, SuYin Grass via Tech-talk:
> I am using AreaDetector and ADAravis to collect images.
> 
> The issue arises when I attempt to set
> $(P)cam1:Acquire parameter to Acquire (1)
> While  $(P)cam1:AcquireBusy changes to Acquiring (1),
> $(P)cam1:DetectorState_RBV remains Idle (0),
> and $(P)cam1:NumImagesCounter_RBV does not increase.
> This behavior suggests that the image acquisition process is not proceeding as expected.
>  I tested it with two different camera on a RHEL8 system, and got  the same problem.
> 
> The setups I am working with are as follows:
> 
>   1.  arv-fake-gv-camera-0.8: This module creates a simulated camera at the local IP address 127.0.0.1.
>   2.  USB Camera Grasshopper3 GS3-U3-23S6M: This camera is connected via USB, and its firmware version is 2.30.3.00.
> 
> The software versions in use are:
> 
>   *   SDK version: 0.8.20
>   *   Driver version: 2.2.1
>   *   ADCore version: 3.12.1
> 
> Interestingly, I have the same IOCs setup on multiple different workstations. Image collection works correctly on some workstations, but not on the other. There are no error messages in the IOCs that indicate what might be causing the issue.
> I am seeking guidance on how to debug this problem, specifically to understand why the detector state does not change and why images are not being collected. Are there specific logs or diagnostic tools that you recommend using to identify the root cause of this issue?
> Thank you!
> Grass
>