LAVA 1.0 Content

QUOTE (Anders Björk @ Mar 17 2008, 09:05 AM) I can't be certain. My experience is based on using USB hubs and multiple USB DAQ devices. Depending on the version of the drivers, which devices saw the power hit, which one came up first.... I have seen the devie ID's change. In both cases, I had to write work-arounds (to figure out which device was which) based on the I?O they supported or by device serial number. In both cases the app had to be restarted (to invoke my ID work-arounds). Restarting apps in production enviornments is generally conciderd "un-cool". Just trying to help, Ben

I have seen USB devices change their device ID with power disturbances. Provided everything is on a UPS, those issues may be of no concern. Ben

QUOTE (jdebuhr @ Mar 12 2008, 05:45 PM) That's great that they are bugging you! Speaking from experience, but don't push them. I tried teaching my son Quick Basic so he code up a ninja fighting game when he was too young. Let them pull. Ben

QUOTE (Ki Hean Kim @ Mar 14 2008, 10:07 AM) Welcome to LAVA! Yes 3rd party hardware is quite the challenge since they seldom know about LV. BUt once you fihgt your way through the first one you find yourself elevated to a higher level and the next one is easier since you have to become confident with both sides of the fence. Have fun! Ben

I almost always use the most recent release when I start a project. But since many of my projects are long term engagements, I have active contracts servicing applications from 6.1 - 8.5. I will only bump version in mid-development if I need a bug fix or need to implement drivers for 3rd party hardware. Ben

QUOTE (Phillip Brooks @ Mar 14 2008, 07:17 AM) Imagine laws written in garphical form rather than jots and tiddles. "You are charged with violating Lawagram 3 sub-case 2..." Art galleries could double as law schools... Ben

QUOTE (ned @ Mar 13 2008, 08:15 AM) I noticed the same thing, but given the option of it showing nothing and showing old stuff, I'll go with the extra. I am not even sure what drives the start time for the "Get New..." so maybe it is working correctly. Ben

QUOTE (crelf @ Mar 12 2008, 01:23 PM) :thumbup: Ben

QUOTE (Neonuro @ Mar 12 2008, 12:25 PM) Welcome to LAVA! If you have not used LV since version 5.X then have two words for you. "Control references" You will love them and everything that hangs off of them. Ben

QUOTE (alfa @ Mar 12 2008, 02:47 AM) The only reply that comes to mind is "there is nothing new under the sun." Ben

QUOTE (Götz Becker @ Mar 12 2008, 07:05 AM) Thank you very much! Waxing philosophical: The world of LabVIEW is very much like wondering in a golden wood. There are wonders and adventures evrywhere you turn. Few of us* have the capacity to turn over every rock and look behind every tree. But as a team we can share the mysteries and pitfalls we encounter in our adventures as we seek out the gloden blooms that sprout around every corner." "Wax off" Ben *Yair is an exception.

QUOTE (vt92 @ Mar 11 2008, 07:25 PM) Call NI, they are glad to help you.... I use NI USB-6259 but that's much more than you need...

QUOTE (Götz Becker @ Mar 12 2008, 05:55 AM) Benchmark regularly as you go. Please let us know if you find something the rest of should hear about. Thank you, Ben

QUOTE (Yen @ Mar 11 2008, 01:49 PM) At first glance I would be thinking "one who VIagrams" How about "VIagraph" for the captured image and then anyone or thing that produces a "VIagraph" would be a "VIagrapher". If "microscopy" is a legitimate word then .... Ben

QUOTE (wytze @ Mar 11 2008, 01:17 PM) Welcome to LAVA Wytze! I don't know how closely the UCXX work with each other but Christian Altenbach is from UCLA and one of the LabVIEW Champions. If the various UCXX's work together, he may be a resource to you and yours. Ben

QUOTE (crelf @ Mar 11 2008, 10:15 AM) "problem" sigular? Woo-whooo! I'm down to one. Wait until my wife hears the news. I will keep trying. On this same topic. I was involved with helping an in-house group of LV developers fix their code so it could ship (you know, "make it work"). While doing so, I watched one of their developers coding using the auto-tool selection. What seemed extremely un-natural was watching someone VIagraming with one hand in his pocket. So are any of YOU "pocket-programmers"? Ben

QUOTE (crelf @ Mar 11 2008, 09:47 AM) I still find myself in the tabbing camp. Everytime I load up a new release of LV, I try out the auto-tool. Sooner or latter I find myslef in a crunch for time and I end up shutting down the auto-tool. I actually went a day or two under LV 8.5! I just find it to be much faster to switch to the next tool while the cursor is moving to my next target, rather that waiting until after I get there. I'll keep trying the new versions, but until LV figures out what tool I will be using BEFORE I get there, I suspect I'll be repeating the phrase "Grrr... Just a second let me shut this off so I can code faster." Ben

QUOTE (ned @ Mar 11 2008, 08:15 AM) Just my 2 cents, It depends on how complicated the app is and how lazy i am that day. Data that can be manipulated from different sources have to be protected. If the app is simple (and I am in lazy mode) I can disable the control when in auto-mode. In that case, the "master" version of the data is stored in the FP opbject. If things are more complicated, then the "master" version of the data will be stored in a critial section (like an Action Engine) and all entities that are concerned with that value invoke methods to make the change. In those cases, all indicators/controls are just copies of what is in the AE. Ben

QUOTE (Götz Becker @ Mar 11 2008, 05:34 AM) It depends on my target platform. FP targets do not have a lot of memory or CPU to spare. I have seen FP-RT run for ages as long as there were no hardware I/O errors. Once hardware errors started returning non-empty "Source" fields in the error cluster, the memory requirments expanded and the app went down due to a lack of memory. In that app, I forced the "Source" filed from FP I/O to be an empty string and the app was able to handle the I/O errors gracefully. PXI RT platforms have more memory and can handle the dynamic memory req's of strings better than FP. Right up until you get to determinism. The Trace Execution Toolkit is handy to get a better feel for dynamic memory allocation etc. Ben

QUOTE (Phillip Brooks @ Mar 11 2008, 06:02 AM) :laugh: Ben

QUOTE (Aristos Queue @ Mar 10 2008, 07:28 PM) So I thought about this idea a bit and there appears to be big money in it if it ever really worked. But before we seriously try to answer the quesion "can we do it?" we should first ask "should we do it?". (I stayed awake through Jurasic Park) Since it is so far out there most of the rules and regulations that normally apply to sex seem to have some loop holes such they can't be directly applied. So... What are the ethical questions that aply? Why shouldn't we do it? Ben

QUOTE(DiDi @ Mar 10 2008, 03:44 PM) Go to Options/Enviornment/Lock automatic tool selection and uncheck. This will leave the automatic tool selection in whatever state you have it in when you exit labview.

QUOTE(BrokenArrow @ Mar 10 2008, 02:03 PM) At the bottom of one of the links provided by Toby earlier in this thread, there a a sentance that is similar to the short answer I believe I originally heard expressed by Rolf. If the reference changes from run to run, then it needs closed. At the time Rolf wrote that we had to type cast to a U32 and look at the number. Since then I BELIEVE you can probe the wire. So if it is dynamic (changes) close it. Otherwise it is your perogative. Ben

QUOTE(Michael_Aivaliotis @ Mar 10 2008, 10:54 AM) As long as I don't attempt to form the word mentally, I am probably safe. [Rant mode = True] We have a big problem looming on the horizon if any of the above ideas become reality! I blame these problems on those narrow-mind English teachers that insist we only use words that can be found in a dictionary. As a result people are hesitant to invent new words and instead adapt the meanings of existing words to new uses. [Rant mode = False] So my problem with the thoughts expressed in this thread are the new Wiki articles that will be added to support this new technology. Examples; Joy Stick as an output device Input/output device Interfacing The list goes on! I think from now on I am going to make an effort to invent new words and terms (like Action Engine ) anytime I get the chance. Or am I completely off-in-left-field and maybe I should embrace how computers and sex are so "tightly coupled". Ben

QUOTE(Phillip Brooks @ Mar 10 2008, 09:09 AM) Just when someone brings up a good marketing ploy... squash. Concidering the effect that sex had on the development of the internet, linking LabVIEW with sex may be a good idea. I can see the Wire-workers now completing a rather invloved VI and then stepping outside for a cigarette. Ben