LabVIEW
All VIs and ctls missing in EXE
At least for test builds, always disable the "Allow future versions of the Runtime to load this application" checkbox! It's in many cases more trouble than any advantage and for testing purposes absolutely useless anyways.
As to static VI references in static VI referenced VIs, I never tried that but it is clearly not the problem here. The VIs are apparently directly included as subVIs. And at least the Fit Window to largest Dec.vi is as far as I remember not a Polymorphic VI, so that should also not be a possible problem.
@JB wrote:
As a first step, I was just hoping that someone else had experienced this problem, which is why I didn't give any more details about the application. Even if I doubt that they are really useful, here are a few :
- several hundred VIs
- some are called dynamically
- many are reentrant (asynchronous control of 4 test stations on an assembly line)- self-made QMH framework
- DAQmx, NI-XNET (LIN), CANopen, Modbus
- JKI State Machine, LabVIEW State Diagram, Enhanced State Diagram
Our applications are for internal use only. Apart from the fact that this is the first application I've developed with LV21 and the first use of Enhanced State Diagram for one state machine, it's not very different from the previous ones in terms of structure and hierarchy.
Compared with others, the executable seems rather large (60MB). ALL the VIs and ALL the ctls are missing.
Same part of code in the development environment :
If no-one has had to deal with this problem, I'd have no choice but to make bits of applications to try and identify the cause of the problem.
Thanks for the info. It's just enough for a super sleuth to add comments. I was always a fan of Velma Dinkley.
You stated that all controls are missing but...I see type def'd constants so at least those controls are in the build. (You also have several enum constants that are not type def'd! This is bad)
The missing OpenG vi is the next clue.. OpenG installs in a version specific <LabVIEW> folder. Jinkies! A Clue!
The third red box contains what appears to be mutation code generated by a save for previous process.
So, second try ...~~~~Oh 8-Ball, did some developer backsave the main vi breaking all the links to the desired LabVIEW Development IDE version specific depenants? ~~~~
It appears likely. (And someone is not going to be happy about it)
@JÞB wrote:
@JB wrote:
As a first step, I was just hoping that someone else had experienced this problem, which is why I didn't give any more details about the application. Even if I doubt that they are really useful, here are a few :
- several hundred VIs
- some are called dynamically
- many are reentrant (asynchronous control of 4 test stations on an assembly line)- self-made QMH framework
- DAQmx, NI-XNET (LIN), CANopen, Modbus
- JKI State Machine, LabVIEW State Diagram, Enhanced State Diagram
Our applications are for internal use only. Apart from the fact that this is the first application I've developed with LV21 and the first use of Enhanced State Diagram for one state machine, it's not very different from the previous ones in terms of structure and hierarchy.
Compared with others, the executable seems rather large (60MB). ALL the VIs and ALL the ctls are missing.
Same part of code in the development environment :
If no-one has had to deal with this problem, I'd have no choice but to make bits of applications to try and identify the cause of the problem.
Thanks for the info. It's just enough for a super sleuth to add comments. I was always a fan of Velma Dinkley.
You stated that all controls are missing but...I see type def'd constants so at least those controls are in the build. (You also have several enum constants that are not type def'd! This is bad)
The missing OpenG vi is the next clue.. OpenG installs in a version specific <LabVIEW> folder. Jinkies! A Clue!
The third red box contains what appears to be mutation code generated by a save for previous process.
So, second try ...~~~~Oh 8-Ball, did some developer backsave the main vi breaking all the links to the desired LabVIEW Development IDE version specific depenants? ~~~~
It appears likely. (And someone is not going to be happy about it)
"You stated that all controls are missing but...I see type def'd constants so at least those controls are in the build."
Yes, good point. But most are missing.
"(You also have several enum constants that are not type def'd! This is bad)"
All these constants are automatically generated by NI's State Diagram Toolkit and can't be edited otherwise by modifying the states with the editor of this toolkit.
"The missing OpenG vi is the next clue.. OpenG installs in a version specific <LabVIEW> folder. Jinkies! A Clue!"
Like any other packages, even our own libraries which we manage with VIPM Pro, OpenG is installed for every used LV version. A self-made tool is used to display the hierarchy of the projects in a tree indicator and to save it to a spreadsheet file. This is quite useful to check the dependencies. From vi.lib, user.lib and specific to the project, ALL VIs are missing in the executable.
"The third red box contains what appears to be mutation code generated by a save for previous process."
This is also part of NI's State Diagram Toolkit.
"So, second try ...~~~~Oh 8-Ball, did some developer backsave the main vi breaking all the links to the desired LabVIEW Development IDE version specific depenants? ~~~~
It appears likely. (And someone is not going to be happy about it)"
This isn't the case. The application runs in development mode and all the dependencies have been checked with our tool.
Thank you for your time.
