Unload All Modules sometimes doesn't work with LabVIEW

[bmihura]

TestStand's File >> Unload All Modules (and its RunState.Engine.UnloadAllModules() function) sometimes works and sometimes doesn't (with LabVIEW). When it doesn't, I have to quit LabVIEW to make TestStand unload LabVIEW VIs, otherwise I can't edit them.

Is there an "Unload All Modules" command that works all the time?

[Norbert_B]

Unloading the modules simply removes the access handle on the module. If the module is unlocked is decided by the runtime/development environment of the module.

Have you tried if Ctrl+m works on the "locked" modules after unloading all modules in TestStand?

Norbert

[bmihura]

I've also been using Ctrl-M over the past few months, and when the "Unload All Modules" doesn't work, neither does Ctrl-M. And vice versa.

[Norbert_B]

Is it possible that those modules are used somewhere else as well?

Do you possibly have a running sequence, aka "execution", in background (e.g. a callback sequence calling those modules)?

Norbert

[bmihura]

As far as I know, there are no modules, LabVIEW or TestStand, being used elsewhere. My TestStand main screen says "NI TestStand - Sequence Editor [Edit]", which usually means it's done and can release modules. But sometimes it won't let go and I have to restart LabVIEW to edit the VIs.

[Norbert_B]

Hm, i assume that you have callbacks defined which do call those modules. Possible callbacks to look first are: SequenceFileLoad/Unload, FrontEndCallback.

Another possible reason is that there are components running in the LV RTE (runtime engine) calling into the VIs you try to debug/modify in the development environment.

Can you pinpoint the "lock" to specific sequences/modules? Do they lock only after specific sequences/modules have been executed?

Norbert