You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the Issue
Device and GenTL producer were found without a problem.
Could not get ownership of device.
This error is similar to previously reported issue "Python & Critical Link GenTL (XML parser error) #368"
AccessException thrown (file 'NodeMapRef.h', line 497) is the same
However, I did not get a runtime exception thrown for XmlParser.cpp
Thanks for your bug report. It looks quite weird. I'm not sure why you get this error message, but maybe something is wrong with the provided XML file.
Could you run your script with enabled debug logging?
import logging
from harvesters.core import Harvester
FORMAT = '%(name)s - %(asctime)s: %(message)s'
logging.basicConfig(level=logging.DEBUG, format=FORMAT)
h = Harvester(logger=logging.getLogger("harvesters"))
....
In the log you will see few temporary path to the XML. Could you try to get that file as well? I just realized, that the do_clean_up flag is not propagated to the Device module. But maybe you have another option to read the camera XML...?
Describe the Issue
Device and GenTL producer were found without a problem.
Could not get ownership of device.
This error is similar to previously reported issue "Python & Critical Link GenTL (XML parser error) #368"
AccessException thrown (file 'NodeMapRef.h', line 497) is the same
However, I did not get a runtime exception thrown for XmlParser.cpp
To Reproduce
Steps to reproduce the behavior:
Followed harvesters install: https://github.com/genicam/harvesters/blob/master/docs/INSTALL.rst
And tutorial: https://github.com/genicam/harvesters/blob/master/docs/TUTORIAL.rst
up to ia = h.create()
Sample Code
I can show a piece of code that demonstrates the reported phenomenon:
Configuration
Reproducibility
This phenomenon can be stably reproduced:
Actions You Have Taken
The text was updated successfully, but these errors were encountered: