Hi Sandeep,
Ø
On doing the $(P)$(R)GC_AcquisitionStart.PROC before $(P)$(R)Acquire Start makes the camera streaming on Software Trigger.
Ø
Earlier, I ignored to PROC $(P)$(R)GC_AcquisitionStart and was only relying on
$(P)$(R)Acquire to get the thing working.
This does not make any sense to me. When you set $(P)$(R)Acquire to 1 that calls pCamera_->StartContinuousImageAcquisition() in the Vimba SDK:
https://github.com/areaDetector/ADVimba/blob/17dcdb1b0a86db808e200232f8b68d5900c30a8f/vimbaApp/src/ADVimba.cpp#L588
It should never be necessary to directly manipulate the $(P)$(R)GC_AcquisitionStart GenICam feature, that is handled by the Vimba SDK.
You say you are using “Software Trigger”, but you have not shown us a screen shot of the original ADVimba screen which shows the trigger information, so we can’t tell if you are doing it correctly. I have attached a screen shot of ADVimba.adl
from one of our cameras.
I just tested with one of our Allied Vision cameras with ADVimba and I was able to acquire in Software Trigger mode without needing to write to $(P)$(R)GC_AcquisitionStart GenICam. It is a different model from yours, but I don’t think
that should matter.
Mark
From: Sandeep Kumar Malu - STFC UKRI <sandeep-kumar.malu at stfc.ac.uk>
Sent: Tuesday, November 15, 2022 12:57 AM
To: Mark Rivers <rivers at cars.uchicago.edu>
Cc: tech-talk at aps.anl.gov
Subject: Re: Allied Vision Alvium Camera streaming issue
Thank you for the suggestions. Its working with passive scan. On doing the
$(P)$(R)GC_AcquisitionStart.PROC before $(P)$(R)Acquire Start makes the camera streaming on Software Trigger.
Earlier, I ignored to PROC
$(P)$(R)GC_AcquisitionStart and was only relying on $(P)$(R)Acquire to get the thing working.
Hi Sandeep,
I get this message on IOC start
2022/11/14 05:13:00.331 Param[ACQ_PERIOD] GenICamFeature::write: node AcquisitionFrameRate is not writable
2022/11/14 05:13:00.359 Param[GC_FRAMERATE_ENABLE] GenICamFeature::write: node AcquisitionFrameRateEnable is not writable
2022/11/14 05:13:00.387 VimbaFeature:writeEnumIndex: ERROR calling SetValue error=-11
Those messages are not serious. They just mean that the camera is not currently in a mode where you are allowed to change AcquisitionFrameRate. That typically happens because AcquisitionFrameRateAuto is true. You can ignore them for
now.
I have 2 suggestions for investigating the problem of the camera not acquiring frames.
-
In the upper-right corner of the OPI screen Status rate is set to Passive. You should set it to 1 second. Then you will get statistics about dropped frames, underrun frames, etc. That is important information.
-
The screen you are using appears to be one that you manually edited from the ADVimba.adl that is in the ADVimba distribution. Please run with the original screen, which has some additional diagnostic information, and send a screen shot of that.
Mark
I have Allied Vision Alvium G1-2460m Camera and using ADVimba driver to interface the same. I can write/read all other camera parameters but can't see
image streaming (the array counter is not running up). I have followed
this link to create template files. I get this message on IOC start
2022/11/14 05:13:00.331 Param[ACQ_PERIOD] GenICamFeature::write: node AcquisitionFrameRate is not writable
2022/11/14 05:13:00.359 Param[GC_FRAMERATE_ENABLE] GenICamFeature::write: node AcquisitionFrameRateEnable is not writable
2022/11/14 05:13:00.387 VimbaFeature:writeEnumIndex: ERROR calling SetValue error=-11
The contents of st.cmd are
# ADVimba driver
#########################
ADVimbaConfig("TEST1-CAM:CAM", 192.168.0.30, 0, 0,0)
dbLoadRecords("/usr/local/epics/support/areaDetector/current/ADVimba/db/vimba.template", "P=TEST1-CAM:,R=cam1:,PORT=TEST1-CAM:CAM")
dbLoadRecords("/usr/local/epics/support/areaDetector/current/ADGenICam/db/AVT_AlviumG1.template", "P=TEST1-CAM:,R=cam1:,PORT=TEST1-CAM:CAM")
# standard arrays plugin
###############################
NDStdArraysConfigure("TEST1-CAM:Image", 3, 0, "TEST1-CAM:CAM", 0, 0)
dbLoadRecords("/usr/local/epics/support/areaDetector/current/ADCore/db/NDStdArrays.template", "P=TEST1-CAM:,R=image1:,PORT=TEST1-CAM:Image,ADDR=0,TIMEOUT=1,NDARRAY_PORT=TEST1-CAM:CAM,TYPE=Int8,FTVL=UCHAR,NELEMENTS=24551424")
FYI, The software trigger source is selected which should capture the frame on every software trigger. Detector state is
always in waiting state. I have attached opi screenshot to confirm that camera interface works well. Any suggestions would be appreciated.
This email and any attachments are intended solely for the use of the named recipients. If you are not the intended recipient you must not use, disclose, copy or distribute this email or any of its attachments and should notify
the sender immediately and delete this email from your system. UK Research and Innovation (UKRI) has taken every reasonable precaution to minimise risk of this email or any attachments containing viruses or malware but the recipient should carry out its own
virus and malware checks before opening the attachments. UKRI does not accept any liability for any losses or damages which the recipient may sustain due to presence of any viruses.
|