LabVIEW
.net based camera may not be restarted when 3D plot is present
@Bob_Schor wrote:
That is really strange. See that function call three inches from the left edge of the Block Diagram, inside the second loop? Could that be the problem? [I'm, of course, guessing where the trouble might be, as my ability to deduce how you coded your VI is not perfect ...].
Translation: post your code.
Search LabVIEW like a graph! Why not post that VI? It will save anybody willing to help you a 10 min. advance. Probably result sin more people willing to try to help.
> The screenshot will still be OK to illustrate the problem, which seems to be of a more general nature, I guess.
Only if you assume it's a general problem. It's possible...
> Others may have noticed similar behavior in their specific contexts. Can we agree on that ?
Sure, it's possible.
My guess would be it's a very specific problem. And without knowing the specifics, it will be hard to help.
AFAIK, the 3D graphs don't use .net at all. So to me they seem to be completely unrelated. However, the camera might use OpenGL or use the video card in some other way. So that might interfere somehow.
Could you make sure it's not a timing issue? You seem to think it's the presence of the code on your diagram, but when you put it on your diagram like you did, both will execute when the VI runs. The graph might consume CPU time, effecting the .net code. Maybe you can use a temporary sequence structure to force execution (all combinations).
The 3D graphs do however use OpenGL heavily. So I would guess the camera .Net driver somehow hooks into OpenGL too, for whatever reasons and that makes it not work properly. Maybe a resource reference count issue that prevents the.Net camera object that the driver creates to unload when you close it in the application.
Have you checked if your .Net objects implement a specific Dispose() method that may need to be called before closing the .Net reference with the LabVIEW refnum close? And you do close of any and every .Net refnum properly after use, don't you?
It might be a problem with the way LabVIEW loads OpenGL and keeps it in memory once a 3D graph is present, but most likely the issue is in the camera driver itself which assumes a few things:
- That it is the only OpenGL consumer
- That an application doesn't usually unload an object hierarchy dynamically without closing/shutting down completely, where Windows resource management automatically makes sure that everything is closed down forcefully and all allocated handles are released.
@JesusJesus wrote:
Good night, I could say how to use my camera Thorlabs 1548 in LabView with .NET as I can not capture an image for processing in a script Matlab.
Post new questions in new threads.
