Hi Rainer,
I talked with security team and we are not doing any traffic inspection so should not add any delay.
I have tried NxView.exe --open and I got a pop up window: “could not find camera 192…”
We managed to identify a problem from your Wireshark captures that explains your issue: NxLib opens the projector once on startup to read the projector’s EEPROM and then again when you open the camera using the Open command. Here NxSimple is much faster than NxView; too fast in fact for the microprocessor in the projector, which is not ready yet for a new connection from the Open command. That is why NxSimple worked when you inserted the delay. I have attempted a proper fix which I will send to you via PM. It would be great if you could try it and let me know whether it works.
Thank you for finding this issue, which we are now tracking as #5632.
Hi Raphael,
Thank you for the fix. I’ve tested it, and I can confirm that it works perfectly.
I really appreciate the detailed explanation of the issue. Let me know if there’s anything else I can help with or test further.
Glad to hear that the fix works for you. I think your work is done here, thank you again for you cooperation and your patience. I will finalize the fix for the next minor release, and maybe upcoming bugfix releases. You can check the changelog of new versions for mentions of #5632.
Thanks!
Could you provide an estimation of when the next minor release containing the fix will be available?
The next official release is scheduled for May, so I would expect it in June or early July. The fix is also marked to be included in the next releases of the 4.0 and 4.1 versions, for which we do not yet have a date.
Every release is announced in the Announcements category. If you subscribe to this category, you will not miss the release.
Actually there is a monthly review of bugfixes to be backported. The next is in two weeks. We can give you a quick update then, if we have collected enough fixes to make a release then.
Yes, that works perfectly. Looking forward to the update in two weeks. Thank you!
This is now fixed in Ensenso SDK 4.1.1023.
1 Like