09-16-2024 05:27 AM
I am currently battling with an error 1502 during a RTEXE build spec
A VI broke during the build process from being saved without a block diagram. Either open the build specification to include the block diagram of that VI or enable debugging to include the block diagrams of all VIs in the build. Report this error to National Instruments technical support. <Call Chain>Error 1502 occurred at AB_Source_VI.lvclass:Close_Reference.vi -> AB_Build.lvclass:Save.vi -> AB_Build.lvclass:Copy_Files_Core_Old.vi -> AB_Build.lvclass:Copy_Files.vi -> AB_Application.lvclass:Copy_Files.vi -> AB_Build.lvclass:Build.vi -> AB_Application.lvclass:Build.vi -> AB_RTEXE.lvclass:Build.vi -> AB_Engine_Build.vi -> AB_Build_Invoke.vi -> AB_Build_Invoke.vi.ProxyCaller Possible reason(s): LabVIEW: (Hex 0x5DE) Cannot save a bad VI without its block diagram. ========================= LabVIEW: (Hex 0x5DE) Cannot save a bad VI without its block diagram. [] SourceItem[543] sourcePath:xxxxx destPath:D:xxxxx saveLevel:0x42003 saveTime:3 [AB_L END](286.230)(846336): 16/09/2024 11:01:08
When I open the vi it is runnable and I cannot see anything which might be causing a problem.
Enabling debugging does allow the compile to finish but when I deploy it to my target I am getting this error in the logs
09/16/2024 06:35:13 0 1003 41 LabVIEW: (Hex 0x3EB) The VI is not executable. This error may occur because the VI is either broken or contains a subVI that LabVIEW cannot locate. Select <b>File>>Open</b> to open the VI and verify that you can run it.
I have tried clearing compiled object cache and mass compiling
I am currently in the process of trying to get to a minimal section of code which shows the problem but it is very time consuming.
Does anyone have any advice on:
- What could be causing this
- Possible fixes/work arounds
- Anywhere I can look at for better debugging information, at the moment I have no idea at all what is causing the problem.
09-16-2024 10:30 AM
It appears that I had two separate issues:
That second point, whilst it has got me going again, isn't ideal as it has increased my build times significantly. has anyone got any suggestions on how to identify what is causing the issue