Home > Labview Error > Labview Error 1502

Labview Error 1502

I would open a service request and send your files (if they are able to be loaded without drivers, custom code, etc) to support for evaluation. Eingabe 2013 Ausgabe 2020???? -------------------------------------------------------------------------- Bitte stellt mir keine Fragen über PM, dafür ist das Forum da - andere haben vielleicht auch Interesse an der Antwort !! -------------------------------------------------------------------------- 23.09.2013, 08:44 I would LOVE to be able to isolate this issue so I could submit it to get it fixed. remove unreferenced members. weblink

This time the supposedly offending item was "Begin.VI". What needs to happen is to figure out why not having the block diagram causes the error. but a descriptive message would be appreciated I do not know why LabVIEW cannot return better diagnostic information when this happens? When editing VIs in this specific instance, you get some strange behaviours (e.g.

vBulletin v3.6.4, Copyright ©2000-2016, Jelsoft Enterprises Ltd. INFO: Dieses Forum nutzt Cookies... Well... "Development Environment is required to fix error" and "Dynamically launched VI cannot run because it is broken" (or whatever) are cases where LabVIEW is not descriptive enough in my book. Laut der Dokumentation ist die korrekte Form ein großes Y.

You made no other changes to the code? Sign in here. Hier war immer ein Problem in der Vorschau. The solution I found was to revert to an older copy of Begin.VI that had been successfully built in the past, build it (successfully), re-implement the exact same changes, then build

Sign In Sign In Remember me Not recommended on shared computers Sign in anonymously Sign In Forgot your password? They said the issue was that during the build process it looks at all the VIs that are dependencies and determines if the code is broken. Well, LabVIEW has a LOT of error information and much of it has gotten fairly descriptive over time. https://lavag.org/topic/18763-error-code-1502-when-building-application/ Regarding the error 6, I have a pretty good handled on it now and I know what to do to get rid of it (basically target build should be short [ie:

Between this error (1502) and error 6 (file I/O=Path too long), building an executable is getting really difficult. He use a lot of classes and he keep getting error 1502 (Cannot save a bad VI without its block diagram.) [Note: Everything run fine in the IDE, nothing broken]. Ernster Nachsatz: wer braucht eigentlich diese „Neuerungen“? He use a lot of classes and he keep getting error 1502 (Cannot save a bad VI without its block diagram.) [Note: Everything run fine in the IDE, nothing broken].

Hope that this helps! https://lavag.org/topic/11989-argh-exe-builder-says-my-vi-is-broken-but-its-not/ What were the circumstances where the error occurred? Sign In Sign In Remember me Not recommended on shared computers Sign in anonymously Sign In Forgot your password? If the VI is not listed in the Project Files section, then select Dependencies.

This will be my preferred approach in the future, obviously. http://edsdefence.com/labview-error/labview-error-10.php Sorry I wasn't very clear. This can be done bynavigating to the Advancedsection ofthe build specification, and check Enable debugging.Please let me know whether this works for you. In our case, the error was associated with a modified (and renamed) copy of HolonomicDrive.VI we had placed in our project.

George Share this post Link to post Share on other sites Antoine Chalons 60 The 500 club Members 60 640 posts Location:Geneva Area Version:LabVIEW 2016 Since:1999 Posted February 24, 2010 I've been working with NI tech support to try and resolve the error. Answered Your Question? 1 2 3 4 5 Document needs work? check over here Also maintenance of all that information has to be a real nightmare by now.

I've recently been building and resolving these errors (I always get it with the package manager).   Orphaned VIs or those in a conditional disable are usually the culprits. Have you been able to build an exe from this source code earlier or is it the first time you try to build? 1 person likes this Share this post Link Ja und nach einem halben Tag Installation - man kann ja zwischendurch den Raum mit Weihwasser sprengen und andere Sicherungsmaßnahmen durchführen, ja und nach der Installation von Vision, ja und nach

In between emails from NI, I started rebuilding the code from the ground up with a lot of copy paste and some changes with the benefit of hindsight.

This error is commonly caused by building an application from a VI that has code which will never execute; for example, having a constant wired to the selector terminal of a Share this post Link to post Share on other sites Create an account or sign in to comment You need to be a member in order to leave a comment Create Method Name: Save:Target Instrument Is anyone know how to fix this? We had some debug code that we were disabling by putting a case statement around it and setting the control to FALSE using a constant.

In the past, for me, these issues have been caused by e.g. Very strange. I hope I'm not re-telling his story wrong but I would suggest searching for the disabled diagram structure and see if there is any broken code in any of them. this content Again, reporting this information also helps with tracking down the problem.