-
Notifications
You must be signed in to change notification settings - Fork 91
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to set value of ChunkModeActive #337
Comments
Hi, you can achieve it by the following line:
By the way, which version of Harvester are you using now? You can check the value by executing the following command:
There you will find a line for |
Hi, thank you for the quick response! Unfortunately, the code line results in an error message telling me that the node does not exist:
By the way, this does not happen with similar looking commands like |
Maybe you should ask DaHeng if the camera support toggling chunk data. Perhaps the device may not support it. By the way, could you show me the whole traceback message where you get the following message, please?
|
The camera is not by DaHeng but SVS Vistek, but yes, I can ask their support. The full traceback message is:
|
Hi, thank you for the update. However, the traceback you pasted above is not the one I asked. I need a traceback when you get the following message:
|
Oh, sorry, my mistake. There it is:
|
Hello again,
I received an answer from the camera developer: It seems that the camera does not support chunk data. Do you know if there is anything else (apart from setting the chunk mode) that I could do to fix the error? Thank you! |
Our camera also doesn't support Chunk transfers. And ia.remote.node_map.ChunkModeActive does not exist. Sticking with harvesters 1.3.2 until we can figure this out. Note: Moving this post to here since it fits more than issue #360
|
Note that according to SFNC 2.5 and SFNC 2.7 (the ones I've checked), ChunkModeActive is only a recommended (not mandatory) parameter. |
The following change fixes this issue. Found some misplaced whitespace which caused the "no way to check chunk availability" to be treated as if chunk support was available. I'll create a merge request though it'd be great if a 1.3.9 could be created as well, since I have additional issues with 1.4.0 (#368) PS C:\Users\jcormier\Documents\harvesters> git diff -U4
diff --git a/src/harvesters/core.py b/src/harvesters/core.py
index 6f35d90..7623ecc 100644
--- a/src/harvesters/core.py
+++ b/src/harvesters/core.py
@@ -2172,9 +2172,9 @@ class ImageAcquirer:
if _is_logging_buffer:
_logger.warning(
'no way to check chunk availability: {0}'.format(
_family_tree(buffer)))
- return
+ return
else:
if _is_logging_buffer:
_logger.debug('contains chunk data: {0}'.format(
_family_tree(buffer))) |
Fix chunk data detection. Fixes Issue #337
* master: Fix chunk data detection. Fixes Issue #337 Announce the release of version 1.4.0 Give it tests Give it a line-break Resolve issue #351 Call it an issue instead of a bug Announce the release of version 1.3.8 Resolve issue #345 Announce the release of version 1.3.7 Update bug_report.md Migrate to the genicam package version 1.2 # Conflicts: # src/harvesters/core.py
Hi all, I'm having the same issue with a Daheng Imaging camera model I am using the experimental ARM64/AArch64 @kazunarikudo : is there any ETA on when 1.4.2 will be released? It would be nice to have this critical bug fix in as soon as possible. Thank you all again for your hard work on this project! |
@JeremyKeusters Hi, thank you for trying out Harvester and I am sorry for having kept you waiting. I will try to release 1.4.2 in the following days. Regards, Kazunari. |
@JeremyKeusters Hi again Jeremy, I have just prepared a trial branch for you: https://github.com/genicam/harvesters/tree/draft/1.4.2-beta Could you try that branch when you can and tell me if it does not break your application, please? If it works, then I will release it and upload the packages to PyPI. Thank you. |
Hi @kazunarikudo thanks for your quick replies and effort. I have tested this and it seems to solve the issue (just like 1.4.1 did), nothing else is broken on my side. |
@JeremyKeusters Hi Jeremy, thanks for testing it. I appreciate that.
Sure. I yanked that version due to a defect that I had introduced. I was going to introduce a feature that involves a dedicated thread and I set the feature enabled by default; this is failure number 1. In addition, the thread was not a daemon thread; this is failure number 2. These two failures made some applications hang up because the thread had kept running after the parent application was terminated. In version 1.4.2 I have disabled the feature by default and I have made the thread a daemon thread so that the thread can be terminated once the parent application is terminated. |
Thanks for the clarification @kazunarikudo . Looking forward to the release of version 1.4.2! |
Dear developers,
When trying to run
with ia.fetch() as buffer:
as shown in your example code [1], I receive the errorRuntimeException: Invalid layout of buffer attached to chunk parser! : RuntimeException thrown (file 'ChunkAdapterGEV.cpp', line 99)
, just as described in your FAQs [2]. There, you recommend to set ChunkModeActive to "off" as a workaround. Unfortunately, I cannot find an explanation on how to do this, i.e. an exemplary piece of code where the value of ChunkModeActive is changed correspondingly.I'd appreciate if you could help me there! Thanks!
[1] https://github.com/genicam/harvesters#harvester-on-ipython
[2] https://github-wiki-see.page/m/genicam/harvesters/wiki/FAQ
The text was updated successfully, but these errors were encountered: