Experimental Physics and
Industrial Control System

I just want to confirm this issue when testing two Alvium cameras G1-500c and G1-577m. I attach the screenshots.

The trick as Sandeep later communicated is to process $(P)$(R)GC_AcquisitionStart once after iocInit.

 From Mark's comment about the code.
> 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
That just make the problem weirder.

The test with ADAravis driver showed no such issue.

On 11/14/22 09:59, Sandeep Kumar Malu - STFC UKRI via Tech-talk wrote:
> Hello
>
> 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 <https://areadetector.github.io/master/ADGenICam/ADGenICam.html#python-scripts> 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.
>
> Thanks
> Sandeep
>
> 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.
>