Broken build moving from DQMH 3.0 to DQMH 4.2

[danny_t]

So its been a very long day for me and I have had enough, maybe tomorrow morning the solution will pop out at me but in case anybody has any suggestions :-

It may not even be a DQMH problem but here we go....

I have a working project LabVIEW 2017 DQMH 3.0 I have not touched the project for six months. Project has 8 DQMH modules and a main and was built into an executable. I had a some changes to do and decided to move up to latest release of DQMH at the same time.  Updated DQMH via the VI package manger then for each module ran the DQMH Module Validate made all the changes except -

---

"DQMH 4.1 provides a new optional 'wait' input on Request and Wait for Reply events. This module contains the following Request and Wait for Reply events that do not contain this feature: "

---

I implemented the other changes I wanted they all worked fine in the development mode but now I can no longer build. I get the unhelpful Error 1502 -  A VI broke during the build process from being saved without a block diagram. 

I have tried building just the DQMH modules and get the same error when trying to save the main.vi .

As files in source control on a seperate PC I used the VI package manager to roll back the version of DQMH installed and rolled the code back to the last built version and I and getting the same build error.

I create the DQMH CM example project and built that that worked fine.

I have tried a build with all the Remove unused members etc un-ticked. 

I have also tried forcing do not removed block diagrams in the build options.

Absolutly any suggestion on what might be the problem, how to narrow it down would be appreciated. 

[ChrisFarmerWIS]

Things to try:

1. Create a brand new build spec and try building it
2.  Does "Generate Preview" work?
3. Create a new project, and re-create the project piece by piece
4. Check dependencies - make sure there are no VIs in your project that you don't use or need, and make sure there are no VIs that are missing, or have a conflict
5. Update to LabVIEW 2017 f4 patch

[joerg.hampel]

Usually, the error message also reports which VI is broken. Did you get that too in your error message? And if so, which VI was it?

[Darren · Accepted solution]

Also, search your code for conditional disable structures and see if any of them contain a RUN_TIME_ENGINE==TRUE frame with broken code.

[danny_t]

Darren,

Thank you for that 🙂

I had manually made the changes in most of my VI to move the Show Panel, Hide Panel and Show Display etc from the MHL into the EHL. I also adopted the change of dropping the un-needed (well maybe) Error flows to the RHS of the EHL frame and in doing so missed the broken Error wires in the RUN_TIME_ENGINE==TRUE.

So it was sort of a DQMH question in the end 🙂

All is built and being tested as an executable now. I spent so many hours on it yesterday I'm kicking myself just now.

Thanks for all other suggests as well everyone.

Christopher.  I have  found the f4 Patch details patch but cannot find a patch download or patch runtime download anywhere. "LabVIEW 2017 sp1 f4 patch" in Google or the NI site fails to find anything

[ChrisFarmerWIS]

Hi Danny,

The f4 patch is an obscure one.  For some reason, it doesn't appear on the list of patches in NI Update Service.

I did however find the f4 runtime patch when I opened NI Package Manager.

In the end, I downloaded it from here:

https://www.ni.com/en-au/support/downloads/software-products/download.labview.html#305508

Make sure you select the correct Windows version/patch/bitness.

[FabiolaDelaCueva]

Danny,

Glad you were able to figure it out, those bugs are a headache.

We created a VI Analyzer test to look for broken code inside the Conditional Diagram Disabled structures because we have been bitten by that before. If you use VI Analyzer on your daily work, you may want to consider adding a similar test.

Regards,

Fab