Re: Can't enable custom frame rates for a basler camera in area detector

[Mark Rivers via Tech-talk <tech-talk at aps.anl.gov>]

Hi Abdalla.


> We tried area detector previously to control Basler cameras from Pylon and it was working.


Can you explain what you mean by that sentence?  My understanding is that Pylon is a software suite from Basler that includes both an SDK and a viewer.  How was areaDetector being used "from Pylon"?


> We revisited the setup again but with one problem which is we can’t set specific frame rate from the ADAravis.adl GUI, frame rate enable PV value is No and does not change.


This sounds like you are using ADAravis?  If the FrameRateEnable is No then the frame rate will be controlled by the AcquireTime and the maximum readout rate of the camera.  What AcquireTime are you using?  FrameRateEnable is designed to allow you to use a slower frame rate than the AcquireTime would generate, for example if AcquireTime=0.1 you could set FrameRateEnable=Yes and FrameRate=2 to only get 2 frames/s rather than 10 frames/s.


FrameRateEnable is mapped to one of the following GenICam feature names:

AcquisitionFrameRateEnable

AcquisitionFrameRateEnabled


Some cameras use one name, some use the other, and some cameras may provide this feature at all.


> The camera is running with maximum acquisition rate of 32 FPS but ImageJ viewer is seeing only 1 FPS


How are you determining what actual frame rate camera is running?  What is the ArrayRate_RBV PV on the main ADAravis.adl window?  If that is 32 then indeed ADAravis is receiving 32 frames/s from the camera.



> but If I go to NDPluginBaseFull.adl and set the max array rate it will give me the correct “frame rate”.


Which plugin are you doing that for?  NDPluginStdArrays, NDPluginPva, etc.?  I suggest you set MinCallbackTime, MaxArrayRate and MaxByteRate all to 0 so that the plugin itself is not throttling the rate at all.


> Seems the camera is running at 32 FPS but only getting one of them each second. Pylon software is working perfectly with the camera, frame rate can be enabled and set with no problems.

There could be several issues that would cause the ADAravis to only get 1 frame/s.  It could be dropping frames for some reason, a plugin could be throttling the frames, etc.

Please send screen shots of the following when you believe the camera is acquiring at 32 frames/s.
- Your main ADAravis.adl screen
- The screen with the plugin you are using for the viewer, i.e. NDStdArrays.adl or NDPva.adl
- The camera-specific *-features_*.adl screen that contains the AcquisitionFrameRateEnable or  AcquisitionFrameRateEnabled PV

Mark


________________________________
From: Tech-talk <tech-talk-bounces at aps.anl.gov> on behalf of Abdalla Ahmad via Tech-talk <tech-talk at aps.anl.gov>
Sent: Sunday, January 10, 2021 4:36 AM
To: tech-talk at aps.anl.gov
Subject: Can't enable custom frame rates for a basler camera in area detector


Hi



We tried area detector previously to control Basler cameras from Pylon and it was working. We revisited the setup again but with one problem which is we can’t set specific frame rate from the ADAravis.adl GUI, frame rate enable PV value is No and does not change. The camera is running with maximum acquisition rate of 32 FPS but ImageJ viewer is seeing only 1 FPS, but If I go to NDPluginBaseFull.adl and set the max array rate it will give me the correct “frame rate”. Seems the camera is running at 32 FPS but only getting one of them each second. Pylon software is working perfectly with the camera, frame rate can be enabled and set with no problems.



Best Regards,

Abdalla.