06-30-2021 02:53 AM
I have a camera from a 3rd party that is interfaced with Labview via ActiveX Controls. I don't have a ton of experience with these controls, what I noticed however is that they run even if the VI is in edit mode. My issue is as follows: I have a quite large project that includes some of these ActiveX controls. This VI takes around 10 sec to start (both in Labview or as standalone), tested with and without ActiveX controls IF the camera is not connected to the computer.
As soon as I connect the camera and reopen the VI (again both in Labview or as standalone) the startup takes more than one minute. At the point that the Front Panel opens, the ActiveX controls are already initialized.
So my current procedure is to disconnect the camera, start my program, and reconnect the camera. This is not very convenient. I have no idea how I could resolve this problem. I tried to follow some of NI's guidelines to speed up standalone applications (Slow Startup Time of Large Stand-Alone Application Developed with LabVIEW - National Instruments), this did not help however (and again I'm also experiencing the issue when I have a non Stand-Alone Application).
Can anybody help?
06-30-2021 07:56 AM
The only recommendation I have is: Do not use those ActiveX controls!
They seem to be awfully programmed and do perform some synchronous initialization on load. Unless there is some (secret) configuration option through a registry setting or whatever for these controls that would delay their initialization to when you first execute the node, they will do their thing no matter what you try to do in LabVIEW. LabVIEW has no control whatsoever what such controls do during initialization. So there is really not much you can do on the LabVIEW side of things.
ActiveX controls sounded like a good idea when they were introduced, but turned out to be an awful thing to use. They never really took off and have since been shamefully relegated to the corner where they spend their days in misery.