Sign In Sign Up Browse Back Browse Forums Downloads Gallery Staff Online Users Activity Back Activity All Activity My Activity Streams Unread Content Content I Started Search Jump to content Application Sign In Sign Up Browse Back Browse Forums Downloads Gallery Staff Online Users Activity Back Activity All Activity My Activity Streams Unread Content Content I Started Search Chief Delphi > FIRST Very strange. I just know NI is going to tell me to rebuild the project if I call them. Source
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 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. Share this post Link to post Share on other sites curiouspuya 4 More Active Members 4 47 posts Location:Sydney Version:LabVIEW 2013 Since:1997 Posted May 30, 2011 Hi all, So was NI looked at the problem and found that it was caused by a known bug in LV. http://digital.ni.com/public.nsf/allkb/8683D4C66F5CA50E86257341007CF34D
Sch... Jump to content Application Builder, Installers and code distribution Existing user? Sign In Now Sign in to follow this Followers 0 Go To Topic Listing Application Builder, Installers and code distribution All Activity Home Software & Hardware Discussions LabVIEW (By Category) Application The original code has one DVR of an object that gets passed into multiple loops.
Which version of LabVIEW are you using? Does it use classes, variables, drivers, Mathscript etc? 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 This seems small initially, but is a huge difference in the code. (This was a decision made after spending some time trying to comprehend the Actor Framework.) There was a lot
Puya Share this post Link to post Share on other sites hooovahh 509 Im no supervising technician Im a technical supervisor Moderators 509 2,295 posts Location:Detroit MI Version:LabVIEW 2015 Posted Added info: went through all of my code and eliminated everything that had a constant connected to a case selector. (confusing because that's never been an issue before) Also went through ayeckley03-22-2010, 12:18 PMFWIW, had the same problem (Error 1502) occur again yesterday. More hints Since the block diagrams are around, the error doesn't apply.
Share this post Link to post Share on other sites Tim_S 47 The 500 club Members 47 725 posts Location:Michigan Version:LabVIEW 2012 Since:1994 Posted February 18, 2015 I ran into The strange thing is we went for weeks just deploying the code to RAM with no errors; we only had problems when we performed a Build. Gottfried PD. Very often it is a class VI that is not actually used in the main code (say a test VI that has been broken as the API changed, and the dev
Share this post Link to post Share on other sites rolfk 369 LabVIEW Aficionado Members 369 2,613 posts Location:Netherlands Version:LabVIEW 2011 Since:1992 Posted March 10, 2010 Well... "Development Environment is I have some libraries with templates (.vit files) that are part of the project. I built an executable in another project that uses similar DAQ calls. At some point we attemped building with our modified copy again and it built successfully.
But I have been guilty myself sometimes to not create to meaningful error messages when developing a new component, but instead use a catch everything single message, of course with the http://robertwindows.com/labview-error/labview-error-1172-net.html If you can please create a service request (referencing this discussion forum) we can further investigate your problem to make LabVIEW a better product. 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 I built an executable in another project that uses similar DAQ calls.
It's just a feeling I had, maybe this issue is totally disconnected from that... Well, LabVIEW has a LOT of error information and much of it has gotten fairly descriptive over time. Jetzt steh ich vor einem neuen Problem: Das Vi "In String suchen" von der NI-Palette macht äußert dubiose Sachen. http://robertwindows.com/labview-error/labview-error-6.html This really need to get fixed.
Oops, I never realized that native English speaker never got that "pb" abbreviation. Eventually the problem went away on its own (after we'd identified the source of the error by selectively deleting subVIs and attempting to build until the error went away). Mit anderen Worten nach dem letzten Neustart sitzt man(n) vor dem Bildschirm und … ein Entzückensschrei entfährt meiner Kehle so ungewollt und spontan, feuchte Augen blicken auf … ein neues Icon
Tried all the possible fixes I could find in the NI forum to no avail. In the same week. Another option is to enable debugging. PJM Share this post Link to post Share on other sites gmart 9 Very Active NI 9 148 posts Version:LabVIEW 8.6 Since:2000 Posted February 24, 2010 I have a very
And once inside a product only bug reports or improvement requests (through the proper channels though) will really be effective. I can't see anything odd in the project. If this is the cause, a few ways to avoid this error include removing the case structure, changing the constant to a control, or placing a diagram disable structure around the Check This Out Hi PJM, what is pb? "pb" is a usual abbreviation for "problem", so I think that means "to isolate the lvclass that causes the issue" being french helps understanding other french
Inside of the unexecuted case were some unused LV Analysis Vis. First time was solved by replacing a subVI (which was just updating a cluster) by its code and deleting the subVI. If you get the VI search dialogue popping up (and you're fast enough) you can click on the dialogues' title bar to freeze it so you can see the VI its Gruß Markus (23.09.2013 08:44 )sccompu schrieb: Hallo zusammen, der Support hat geantwortet: Parameter "%y" in "%Y" ändern und alles funktioniert wieder.
The only thing that changed between the build working and not working was the installation of SP1? Register a new account Sign in Already have an account? He spent several days trying to fix this, without success. Was the user's destination path for his built very long?
PJM Share this post Link to post Share on other sites jgcode 319 LabVIEW Renegade Moderators 319 2,397 posts Location:Australia Version:LabVIEW 2009 Posted February 25, 2010 ...was to isolate the Very strange. Do you know if you did anything like that beforehand? Very often it is a class VI that is not actually used in the main code (say a test VI that has been broken as the API changed, and the dev
der Dateidialog hinter einem Floating-Fenster von LV verstecken kann. Or sign in with one of these services Sign in with Facebook Sign in with Twitter Sign in with LinkedIn Sign Up All Content All Content This Topic This Forum Advanced I had enable debugging turned on for quite a while, so it's possible that could have broken things and I wouldn't have seen it. The rewrite eliminated that DVR and creates multiple objects for each loop.
George Are you using JKI RCF or are you playing with home-made VIs in another context than the main LabVIEW instance? Share this post Link to post Share on other sites PJM_labview 32 The 500 club Members 32 777 posts Version:LabVIEW 2009 Since:1998 Posted February 25, 2010 I have one of