LAVA 1.0 Content

When washing the ( ), use a color-safe detergent. These may be color-safe bleaches or just detergent that is made for keeping colors from fading. The washing itself should be done in cold water to prevent too much of the dye from being lifted out of the material. Hot water will take it out far too quickly and will cause a faded look after a few washings. Use short washing cycles if the t-shirt isn't terribly dirty as well to reduce the time that the t-shirt will be wet.

One question before I install this on my development machine.

Does installing the toolkits still uninstall the toolkits in other LabVIEW versions?

Ton

QUOTE (crelf @ Aug 12 2008, 01:33 AM)

Admin Note: this LAVAcr submission has been moved from the submission queue to the http://forums.lavag.org/Code-Repository-In-Development-f83.html' target="_blank">Code Repository In-Development area due to inactivity timeout.

Note from the author:

Thanks for putting this online while I had not the time to put development time in this tool. :thumbup:

I have some issues with my computer at this moment involving LabVIEW and other pieces of software.

This tool will get updates in the (near?) future. Don't hesitate to give feedback here.

Ton

QUOTE (crelf @ Aug 11 2008, 08:52 PM)

When I'm in a deeply creative mood, I can't go past the 1985 Dire Straits classic http://en.wikipedia.org/wiki/Brothers_in_Arms_%28album%29' rel='nofollow' target="_blank">Brothers in Arms.

Very good choice. This used to me driving music on my way from college back home.

For coding I either go with the iTunes Party mix (ranging from Frank Sinatra to Journey, with some Pearl Jam and Jerry Jeff Walker thrown in), but when it gets really tough and I need to tune out the surrounding cube land, I put on the noise cancelling head phones and embarassingly enough pick the Sound of Music sound track. For some reason it works for me. Don't question results. (I guess now I will find out how many of my coworker actually read LAVA.)

QUOTE (Yair @ Aug 11 2008, 12:58 PM)

P.S. Christian, nice work on the CVT and the components in general. I think creating tools like this is very useful. Any reason why these components don't ship as standard in vi.lib?

Thank you. These are not included in the standard product for several reason. The quick reasons are documentation, testing, maintenance, support, forward compatibility, etc. It takes a lot more time and effort to add a feature or set of VIs into LabVIEW and maintain them long term than my group can provide. We are not part of R&D and don't pretend to develop products. Our goal is to share with the wider LabVIEW community things we learn and code we develop while working with customers and integrators on individual applications. In short we have the same motivation as the LAVA community; to improve the experience of LabVIEW users by sharing what we know and do.

In addition we like to use what we publish on DevZone as a trial run and sounding board for possible new features and VIs to be added to LabVIEW and other products in the future. By not including the VIs in LabVIEW right away we're not committing to a particular functionality or API until we feel it is ready for the product. Some of the code we have developed has made it into examples shipped with LabVIEW. Specifically the LabVIEW Touchpanel module 8.6 includes a reference design based on code we published last year. However, in general what we do and the feedbapck we provide to R&D makes its way into the product in other more hidden ways, e.g. by improving current features or adding new features that may look different from the original solution we provide. For example, the cRIO I/O Engine (CIE) we published last year has just been surplanted by the Scan Engine and RIO Scan Interface released in version 8.6. This effectively negates the need for one of the reference designs we published last year, which is exactly what my group likes to see.

QUOTE (Darren @ Aug 11 2008, 03:08 PM)

I use SCC in the LabVIEW project, but our server is pretty snappy. I'm not too familiar with LabVIEW launch time speed issues, but I think I've heard people blame slow SCC servers and weird licensing network problems for slow LabVIEW launches in the past.

-D

Close LV and then re-open took less than a second. I'll try to rember to look it again tomorow AM to see how it acts after another re-boot.

Ben

BTW: Darren, The gentleman that said "Hi" to you on my behalf was one of my bosses, Dr. Greg Cala (the fifth person in the world to earn his CLA).

QUOTE (Yair @ Aug 11 2008, 02:04 PM)

By the way, this still seems to suck.

Examples:

• "kermit mel" still does not find the thread we discussed earlier.
  
• "search sucks" still does not find this thread.
  
• "labview tool suggestion" (what I was actually looking for) does not find http://forums.lavag.org/A-LabVIEW-tool-suggestion-t8976.html' target="_blank">this thread.
  

All of them seem to work fine through labviewsearch.com. Maybe the internal search engine just isn't indexing the content?

I have to second Yair's comments. I have a very difficult time trying to find things I know are on LAVA. With few exceptions, if the post did not occur recently (so that I can find it in the recent threads) I try once with my best guess and give up afterwards.

I would be linking more LAVA threads on the Dark-Side if I could find them quickly.

Ben

QUOTE (ASTDan @ Aug 11 2008, 02:25 PM)

:worship:

Wow

A Kool-Aid Kid

Thanks you Dan! I now know what to do with that ability to put a custom string under my icon.

Ben

QUOTE (Darren @ Aug 11 2008, 01:28 PM)

Change the setting to "Load Palettes on Launch" if you want all Quick Drop info to be ready to use when LabVIEW launches. Depending on how many toolkits, modules, add-ons, etc. you have installed, your launch time will increase a certain amount. I've never seen a 45-second wait, though. Is your computer reasonably fast?

-D

Without changing anything, an un-official time check showed it took 39 seconds. I have every possilble add-on loaded. Relativle new machine.

Ben

QUOTE (Jon Sjöstedt @ Aug 11 2008, 04:01 AM)

Clarification attempt: I am not looking for OOP design elements in general. I am specifically interested in a way to access data in pointer-style (=refnum?). Dataprotection is desireable if possible. I have noted the very elegant LV2-style singleton design (which uses no magic *OOP-package or LVOOP) and need to complete it with a non-singleton datastorage. Hope this was more clarifying than confusing...

Shameless Plug: You may also want to look at the Current Value Table implementation, available on ni.com.

Current Value Table (CVT) Component

A Current Value Table for LabVIEW

It uses the FGV design to implement data storage for any number of tags or values in your application. The data or values are accessed by name or by index (refnum), your choice. In the current design you must initialize the CVT at the beginning of your application with the list of variables you will be using. This list is passed as an array of clusters to the Init VI and can be created dynamically, defined statically (constant), or read from a file. The current implementation includes support for scalar Boolean, Doubles, I32, Strings, and Enums. It can be easily extended to other data types. Arrays are a bit more tricky and are not included in the published code. I do have a trial implementation for arrays that I can send you or post on request.

Please provide any feedback or suggestions for the CVT in the provided discussion forum. General questions I can answer here.

QUOTE (ASTDan @ Aug 10 2008, 11:29 AM)

Jeff K said at the keynote he helped make the kool-aid.

Does that make him Kool-Aid man?

Regardless of what you call him he is "way Kool" in my book! Check-out the "extra" signature on this certificate.

http://lavag.org/old_files/monthly_08_2008/post-29-1218458154.jpg' target="_blank">

Ben

JGCode has solicited your help on VMware issues.

Ton

QUOTE (ASTDan @ Aug 11 2008, 03:06 AM)

My intended use is desktop sharing i.e. my customers can look at my desktop when talking about requirements.

Another use could be colaberation. I have noticed people are working remotly more and more. What tools do they use to comunicate effectly beyond cell phones etc.

Dan

At work we use LogMeIn.com to control remote desktop computers, works super, even through our company proxy (both ways).

You have FogCreek Copilot

I have used a program that captured my desktop and converted it into a webcam driver to share via skype, msn and others.

Ton

QUOTE (crelf @ Aug 9 2008, 04:07 AM)

I agree - the first step is to admit that you have a problem.

...it's your choice of beer that's the problem

QUOTE (Norm Kirchner @ Aug 9 2008, 06:57 PM)

Hi Justin, Welcome.

We've all been at the point of drinking second grade beer.

You should have picked another Heineken brand. (flash alert)

Ton

QUOTE (Val Brown @ Aug 8 2008, 03:41 PM)

OK, here I am "old school" anthem ringing in my ears but isn't this supposed to be GRAPHICAL programming? I really don't want to use the keyboard at all -- except to document what I do -- so having to type anything seems like a far slower way for me to go, because of how I have to move off my trackpad. Now part of that might also be that I always program on my MacBook Pro so I don't use a mouse.

<caveat re: mouse. There's still a bit of a problem I'm having at times with right clicks on my MBP running XP under Fusion but that's a different issue for a different thread>

So the bottom line for me is that QD will probably be SA (slow addition) to my use patterns. Despite that I think it's a great idea, esp for those who are more used to STILL using text-based programming.

end of post from old school whose off to pursue other options... :beer:

I am old school when it comes to the auto-tool select mainly because it was so slow...

I have plans to make QD part of my normal routine since I can take it with me via the ini settings. In fact I intend to write a QD tutor this week-end that will display one of my short-cutted operators (choosen at random) and watch the key-board to see if I hit the correct keys. When I get through it with making mistakes I'll start working on the speed. When I am coding I first pull-up the image of it in my head, then go naviagting for it. Sometimes when I am after the Add, I occationally clcik on the add icon that is part of the Numeric select palette before I realize I have to drop down one more palette. I see no reason to define short-cuts for all operators, just the ones I use most often. To define short-cuts for all would force me to use mre than three keys in the short-cut and would defeat the purpose of speed.

So the same reason I don't use the auto-tool select is behind my intent to adopt QD, SPEED.

Ben

QUOTE (TobyD @ Aug 8 2008, 11:43 AM)

At the end of http://zone.ni.com/devzone/cda/tut/p/id/7423' target="_blank">this article there is a txt file that you can download to setup some common shortcuts. I have found most of them to be fairly intuitive.

I think I am really going to like the quick drop feature once I get used to it. Right now it slows me down, but as I start remembering names/shortcuts I can see it as a real time saver. :thumbup:

Thanks for the tips. I am going through the process of defining my own short cuts because typing the actual name is just not part of my brain.

The For loop threw me because it seems to take more mouse clicks to complete it placement.

I think that dragging around a memory stick with the ini text to use these short-cuts on most of the machines I touch should be possible. For those sites where I am not permitted to bring in memory sticks or any type of media, I'll have to resort to the tried and true mentod of navigating palettes.

Epiphany:

While defining my shot-cuts, I suddenly realized, I do not know what the official names of all of the operators I generally use! Talk about being visually oriented!

Ben

QUOTE (Darren @ Aug 7 2008, 05:29 PM)

If you are in fact using LabVIEW 8.6, why are you going to the palettes to drop a For Loop?

...

OK Wire-Slinger, help me out with this Quick Drop stuff.

To answer your Q, it looks like I have to define all of my own short-cuts to use it, Correct? That is reason enough not to QD on first open but proceeding...

Please talk to me about your exact key strokes you use.

ctrl-space bings up the QD screen.

then "SW" (my short-cut for Structure While loop) but then what are your key-strokes and mouse clicks from there?

Ben

I like this one:

Licensing

LabVIEW supports both single-seat and volume licenses. Single-seat licensing is the use of LabVIEW

by an individual user. Single-seat licenses may be used on one computer by many users or by one user

on up to three computers.

So I do not longer deed debug deployment licences - that saves me some money...

Just got LV 8.6 open and went to diagram and found very plesent suprise. The defualt palette is now "Programming" so it doesn't take multiple wigles and clicks to get to a For Loop.

Big thimbs up for that one.

:thumbup:

Ben

QUOTE (Val Brown @ Aug 7 2008, 03:19 PM)

I found the same serial number worked across all toolkits -- except Adaptive Filter Toolkit -- even though I did have to install each separately.

Thanks Val!

It is probably an issue with my serial number since LV 8.6 registered OK. Support is checking with R&D about what could be up. I suspect the "integrators" license number has something to do with it.

Oh Bother!

Ben

Is anyone else having trouble registering all of the add-ons that come with the suite?

LV 8.6 registered OK but now it looks like I am going to have to enter a new key for each.

Ben

QUOTE (mross @ Aug 6 2008, 08:55 AM)

OK. I had a bunch of E Series VI's builtwith Traditional DAQ, when I replaced that board with an M Series I had to redo all the Traditional E Series Vis with DAQmx. I conflated that to get the incorrect idea that DAQmx won't support E Series. But really Traditional DAQ won't support M Series, my mistake. I haven't actually written DAQmx to support E Series so I spoke out of ignorance. Thanks very much for the correction.

Mike

Now i am feeling good..

I don't have any faith in the unbelivable things.

[it is good to know that you have an E Series DAQ board becasue this means the normal recommendations touse DAQmx VI's will be wrong. DAQmx is for M Series hardware].

Mike,

can you throw some more light on this part..Why cant DAQmx support E series cards?

QUOTE (Maca @ Aug 6 2008, 03:09 AM)

EJW's idea is FAR better than the two examples I gave in my first post (However I still don't like the express VI's), If i was you I would use his code.

Just a question however where you said "control voltage" do you mean an analogue output or a digital output? I had assumed that is was a digital output, where as EJW is outputting a constant voltage from the DAC.

Hi,

There are couple of example under LabVIEW which can provide u a readymade solutions. U may have to tweak it a little bit to meet your requirement (Probably). I suggest you not use those express vi's.

Go to LabVIEW and "Help->Find Examples" then select the vi which you are looking for