Closed angarsky closed 1 year ago
correct me if I am wrong, have you open the camera with the VimbaViewer and at the same time try to run your code? This is not possible. Only one instance can open the camera in full access mode.
@BernardoLuck you are totally right. Thanks for the reply. Yesterday was really hard day if I missed this thing :)
Similar error here- I know the cause, there was a process that was killed with SIGKILL that did not have a chance to relinquish its claim on a camera. I have in mind a couple of possible solutions here, but importantly, unlplugging and re-plugging is NOT a solution for my usecase, as I do not have physical access to the cabling.
Is there any holes in my thinking here? Seems like my only options.
To have only one process with write access (AccessModeFull) to the camera is part of the standard and will not be changed in subsequent versions. Both USB and GigE cameras will notice on their own, if the program was stopped (missing ack from the process) and close themselves. If that is not happening with your USB cameras, you might need a firmware update.
Via hardware, the camera can be forced into a reset, if the power supply is connected or disconnected. I.e. if the camera is powered through USB and 12V is supplied to the external power input, then the camera will do a device reset to change from USB power to external power.
Read Only mode can not execute commands on the cameras, so it can not start the acquisition to get frames. It can be used to check the function and settings of the camera, but not to change them.
Hi there,
Today is my first experience with Allied Vision camera - so maybe I missed something trivial. The issue is that I can't get a frame via Python script.
The error is:
The code is pretty simple and is taken from examples and documentation:
The full error is on the screenshot.
There's a bit similar issue #47 - but it doesn't look as the same.
Thanks.