Re: Image Acquisition Issue with AreaDetector/ADAravis

["Wang, SuYin Grass via Tech-talk" <tech-talk at aps.anl.gov>]

Here is a link for details and screenshots. 

https://anl.box.com/s/78yqih6cjxvs1kk4f5h9vdsw1vowphmz

Mark River kindly stopped by and took a look at the USB cameras and give us some good advice on debugging.

Here is a quick summary of the setup for USB camera. 

• The arv-tool can see the usb camera​
• The arv-camera-test-0.8 get proper frame size​
• IOC can change the frame size: if frame size is changed with ioc, the frame size read from arv-camera-test-0.8 also changes.​
•  The udev setting is under "/etc/udev/rules.d/aravis.rules"​
•  USB-FS set to 1000MB:​
• add this line to /etc/rc.local​
• echo 1000 > /sys/module/usbcore/parameters/usbfs_memory_mb

There are also a few check for debugging :

1. Set Trigger mode "Off"​
2. Set Exposure auto "Off"​
3. Set Array callbacks "Yes"​
4. Set Poll features to "1 second"​
5. Test different frame size​
6. Set Gain auto "Off"​
7. Check the pixel format

Make sure using USB3​:

In the Featurs Screen #1​ :

Check the DeviceMaxThroughput, this should be around 384M​

In the Featurs Screen #3​ :

Check the U3VCurrentSpeed, It should set to SuperSpeed

Note that the USB camera might not get enough power if ​

• The usb cable is too long​
• There are multiple camera plugged to the same usb card. ​

In our case there are two usb cameras plugged to one usb card. Both camera were working before. Each usb camera gets an external power through an extension cable, so the power shouldn't be an issue​

We removed one camera, and left only one camera connected, but still have the same problem​

We moved the test camera to a different workstation (38-am), but still have the same problem​, that might rule out the bad USB card

Any advice?

 

Thank you!

Grass

---

From: Mark Rivers <rivers at cars.uchicago.edu>
Sent: Wednesday, March 12, 2025 12:07 AM
To: Wang, SuYin Grass <grass at anl.gov>
Cc: tech-talk at aps.anl.gov <tech-talk at aps.anl.gov>
Subject: Re: Image Acquisition Issue with AreaDetector/ADAravis

 

Hi Grass, Can you send a screenshot of the OPI screen when using the USB camera? Mark Sent from my iPhone On Mar 11, 2025, at 5: 56 PM, Wang, SuYin Grass via Tech-talk <tech-talk@ aps. anl. gov> wrote:  I am using AreaDetector and ADAravis

ZjQcmQRYFpfptBannerStart

This Message Is From an External Sender

This message came from outside your organization.

 

ZjQcmQRYFpfptBannerEnd

Hi Grass,

Can you send a screenshot of the OPI screen when using the USB camera?

Mark

Sent from my iPhone

On Mar 11, 2025, at 5:56 PM, Wang, SuYin Grass via Tech-talk <tech-talk at aps.anl.gov> wrote:



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