Jump to content


  • Posts

  • Joined

  • Last visited


Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Donald's Achievements


Newbie (1/14)



  1. There are also some quit cheap activeX toolkits available on the net that can be interfaced in LabVIEW.
  2. FYI: If I get this error and it is not clear which file (e.g. Application Builder, not your app, ...) I use the Sysinternals free FileMonitor. it reveals on OS level the calls to missing files (the same exists for registry).
  3. I was also testing with LabVIEW 8.6 and now I understand why the substitution on the FP didn't work, I was not aware that the storage of FP strings changed since 8.6. I can live with a version indication in the VIs description this is something easy to automate. Thanks for all the tips! :thumbup:
  4. Hello All, What is the most efficient way to get some SVN properties like Revision and Author on the VI front panel (e.g. OpenG VIs)? For text files the SVN keyword substitution works very well, for binary files (like VIs) I'm not sure how to handle this without writing some automation code. I remember that there has been an article about CVS and keyword substitution in LTR once and was looking for something similar for SVN. To my surprise I did not found a clear article yet. Thanks for any tips? Donald
  5. There is a modulation toolkit available for LabVIEW. Check the National Instruments site for more information.
  6. Hello Eugene, I'm not a LVOOP user so I'm not sure if these tricks will help: Try following: - add the VIs with missing front panel as dynamic Vis to the LV build script - use some control/indicator property nodes in these Vis with missing front panel, this forces LabVIEW to load front panel Good luck.
  7. Maybe with the 2D bilinear and bicubic interpolation VI in the NI GMath library??
  8. QUOTE (Ton @ Nov 21 2008, 01:07 PM) I use this constant since LabVIEW 3 if I remember well. There are many usefull generic errors e.g. Argument Error as you know. This constant is used by a lot of VI.lib VIs, I had no idea it has been depreciated. What should be used instead of this constant? When I try to select it from the LV7.x palette (within LV 8.5) nothing happens... with Quick Drop I can still select it but quick drop takes a while to launch on older PCs... Makes no sense Thanks for reminding me it is also on the OpenG palette which I always install.
  9. Hello Anyone who found the Error Codes Ring constant on the LV8.6 palettes? I only find it on the 7.x Functions and with the quick drop tool (Ctrl-Space). Thx, Donald
  10. QUOTE (Michael_Aivaliotis @ Nov 20 2008, 10:45 PM) A fast solution for NI could be: The choice between "CleanUp All" and "CleanUp Selection". Selecting the 2 problems cases and clicking Cleanup will produce a better result with existing clean up algorythm. Often only a part of the diagram needs cleanup.
  11. Manual wiring could produce nicer code yes I agree but often I do not have the time for it, certainly during refactoring/modifing code some small changes could result sometimes in huge wiring efforts and even the danger of introducing a bug during connecting/disconnecting. Cleanup does it error free and fast(er) than I can, the style is more than acceptable for my customers who pay me per hour (and they do not care where the error cluster is connected to). Please give it a try. I also use often code that is 'in the field' since LV3.1.1 and had many revisions so not always the cleanest code (also automatic 'bad' style during upgrades 3.11-> 4.1 -> 6.1 -> 7.1 -> 8.2.1 -> 8.6 :-) ther LV compiler introduces sometimes conversion nodes- wires get hidden etc) Now I can clean it up in a split second. BTW: An extra feature could also be that only the selected code/diagram is part of the cleanup and not the complete diagram. Good comment however regarding annotations and comments that are misplaced. I did not think about this.. Yes there was no (at least not many) comments in the code I cleaned up. I need to check this. I remember a funny comment in a diagram once (I guess it was Philips R&D) IF THE CODE WAS HARD TO PROGRAM IT SHOULD BE HARD TO READ! :headbang:
  12. Hello All, This post just to share my 2 weeks of LabVIEW 8.6 wiring experience! I'm so happy with the LabVIEW 8.6 diagram cleanup feature! For me it is the best new feauture and best developers time saver since the introduction of Undo. Maybe the best rapid developers feature ever! I tortured the diagram cleanup with the worst horor diagram I've seen in 13 years of LabVIEW usage and ... yes the NI LabVIEW developers did the impossible :worship: --- the 2400x1900 multi nested sequence diagram of doom was clean(er) after 1 minute of calculations on a dual core(!) and LabVIEW did not crash!!! After 2 weeks of development (2 projects with +1500 VIs) LabVIEW 8.6 did not crash at all during development! Rapid development gets a new breeze with this function... just drop Vis wire - test - debug - and cleanup in some second! Maybe my PC mouse will last longer than one year with this feature :-) Even my test and prototype VIs are neat now Also the multi control-indicator properties dialog is a serious improvement. And on a PC were it takes at leat 20 seconds to get the properties dialog also an enormous time saver for GUI development. One little cloud : I can not build a project I can build with 8.5, something I still have to check with NI support. (saving to 8.5 solves my problem so it is not blocking the use of 8.6). Happy clean wiring, Donald
  13. Good suggestion! I'm also using more and more the lvlib public/private access scope when refactoring old(er) code in LV8+ environments. I like to protect functional globals to be used directly in the main diagram and wrap then in a public VI for each 'method' of the functional global. I must admit I have been thinking also about such a 'dynamic' glyph for reentrant VIs (a bold red R...)
  14. I'm wondering why you do not use the build-in Shared (Network) Variables for this job. I guess maybe not available on your RT platform?
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.