How do you use projects?

[CoastalMaineBird]

One thing I still don't quite understand about the problem you're having. You say that you experience this delay when you press 'run',

--- Yes. The interface is dead during this time - no progress dialog, no hourglass cursor, you cannot switch windows, no beeps, nothing. You can switch to another program, but LabVIEW is off playing with itself and won't do anything.

When it finally starts deploying, you can cancel it. If you look at the DEPENDENCIES item, it's filled in, where it was empty before pressing RUN.

but I've never had a project check dependencies when I run a VI.

--- How do you tell it not to?

It only checks them when it builds an executable, and of course this is going to take some time.

--- It looks to me like it's checking them every time. The first time, the dependencies table is empty, and that's when it takes so long. The second time, the table is already there, and it's not quite so long, but still it's a second or so.

If your project is updating dependencies every time you run the main VI, I'd say something is wrong.

--- Yeah, I came to pretty much the same conclusion 😉

[CoastalMaineBird]

OK, now I have the real project, with the modified TEST vi in it, and it works OK. (About 1 sec between CTRL-R and the DEPLOY window appearing).

If I place the SINEWAVE vi on the diagram (even without wiring it), and close the project (to forget the dependencies), open it and run it, I'm back to 36 seconds.

And the SIM junk is back in the dependencies list: "SIM Runge-Kutta data variable step.vi" WTF? At least 90 of those things.

I remove the SINEWAVE vi, save, close and re-open the project and RUN it again, and it's down to 1 sec of dead time.

The dependencies list still shows unnecessary stuff - ALL the DAQmx variations that I'm not using, but still it's 1-2 sec of dead time, instead of 35+ sec.

< sigh >

I have a workaround (do the sinewave thing myself), so I can't spend any more time on chasing this now.

[Jaegen]

Sorry, I can't help you with the real issue ... but since no one has answered this question:  The reason you're seeing so many VIs that you don't actually use, is that you do use some polymorphic VIs, which are made up of all of these other VIs.  For some reason (which no one has ever explained to me), LV loads up every polymorphic instance, even if you're only using 1 of them.


Jaegen

[CoastalMaineBird]

For some reason (which no one has ever explained to me), LV loads up every polymorphic instance, even if you're only using 1 of them.

Yeah, I discovered that way back when I moved to MX. My VI count jumped drastically by replacing 10 VIs with a different 10 VIs.

Anyway, the DAQmx part of the dependencies doesn't really slow it down that much, it just makes the list more useless.

It's that sinewave thing that really clogs up the works.