Hello,
I’m currently developing a camera application using Aravis and I noticed some inconsistent behavior related to the is_locked parameter in ArvGcFeatureNode
between FLIR and Allied Vision cameras.
When I connect to a FLIR camera I see certain read-only parameters have is_locked set to true
while the camera is grabbing or certain properties are not available at that moment. For ex: If PixelFormat is set to BayerRG8 then Hue and Saturation won’t be writable.
This lets me know when it’s not safe to modify certain settings.
However, with Allied Vision cameras, the is_locked
for these parameters are always False.
Questions:
- Is this a limitation of Aravis, or a reflection of the GenTL or camera’s capabilities?
- Is there a standard way to detect when parameters are locked in scenarios like this?
Any guidance or best practices for gracefully handling parameter locking across different camera vendors would be much appreciated.
Thank you in advance for your help!