LAVA 1.0 Content

QUOTE (bazookazuz @ Aug 12 2008, 10:41 AM) Developing a new XControl from scratch can give one an insight into that mystery. Ben

QUOTE (Darren @ Aug 12 2008, 10:56 AM) Wow! Does that include drivers, DSC etc? If this is true, I may be able to get by with only 4 PC and could switch from version to version with out having to boot into a new partion. Hopeful, Ben

Thanks! I couldn't find it on any of the readme's (which is logical the old behaviour should be mentioned) Ton

"The sound of silence" by ear-plugs and sound deadening head phones. (It worked for Tomi). Ben

QUOTE (P. Rosegger @ Aug 11 2008, 06:11 PM) Hello, You can download the driver for the EPOS drives on the homepage from maxonmotor. http://www.maxonmotor.com/downloads.asp I use the EPOS with RS232 driver. I know that Alexander Rudolph from NI Switzerland has worked together with maxonmotor on the current driver. He also made some exhibition examples using EPOS, with CAN interface. You should contact him regarding this issue. (firstname.surname@ni.com) I don't know wheather he was using the PDO's for communication or not. Martin

There is no such thing as "one size fits all" when it comes to office furnishings. We can't all wear the same size pants or skirt, so why would anyone expect us all to fit in the same floor chair? Step1 Be realistic about your physique. Smaller people are not always comfortable in huge chairs and petite chairs can be a squeeze for large folks. Step2 Create a checklist. When you conduct your sit-and-spin test, you will want to consider these fit points: distance from floor, lumbar support, seat padding, arm height and head room. Step3 Check-list in hand, visit a store that sells office chairs( ). Put together a line-up of the four or five chairs that look best to you. At this point, disregard price as a fit factor. Step4 Sit in each chair. Rate each chair for fit based on the criteria on you list. Be very specific in your evaluation. For example, don't simply confirm that your feet reach the floor when you sit; make sure your legs are resting at a comfortable angle. Step5 Check the floor chair for adjustments. Can it be made to fit you perfectly by pushing buttons and pulling levers? Step6 Put the chairs that pass the fit test through a spin test. Sit in the chair and take it for a spin, roll it on a hard surfaced floor and try to scoot it on carpet. Turn it quickly in a different direction. Test it to see how easily it spins left and right. This might sound like child's play, but when you're on task, you probably move in ways that would surprise you. Step7 When a chair has passed the fit test and the spin test, you can consider it for beauty. You may find you are so pleased with the way it fits and moves that you don't care if it's built like the back end of the Scotts Bluff bus.

How to Keep Your Color Bright The colors of a new are always brightest when the t-shirt is newest. Over a long period of time and many washes, the colors will begin to fade. However, there are a number of ways to keep the colors bright and to keep fading to a minimum. One of the fading factors is UV light. Direct sunlight will eventually fade the colors of s( ). For this reason, dry a t-shirt indoors to preserve the bright colors. It's also a good idea not to stay in bright sunlight while you are wearing the t-shirt. This can fade the shirt just as quickly as hanging it in the sun can do. Also consider where you store your t-shirts. If there is direct sunlight shining into your closet, that can fade your t-shirts as well as anything else being stored there. A t-shirt with a bright color should only be washed with other clothes that have the same or a similar color. Washing the shirt with very different colors can mute the colors of all of the items as the dyes are mixed together. If the t-shirt has color like nothing else in your wardrobe, wash it by itself. 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. Because there is usually a little bit of dye that is lifted from clothing when it is washed, there are specific products that can capture that dye and prevent clothes from being dulled by the dye from other garments. One of these is dye grabber sheets. These are placed into the washing machine when the clothes are loaded. The sheet will absorb the dyes and leave the clothing looking far less faded. Another way to ensure brighter colors is to use a common household ingredient to the wash. Many people regularly use vinegar in the wash to keep dyes from being lifted out of fabric and colors looking bright. To use vinegar in the wash, get a supply of white vinegar. This is an inexpensive type of vinegar available at any grocery store. Measure one cup of the vinegar and pour it into the washer along with the detergent. You don't have to use less detergent than usual when you do this. The result will be s that keep their bright colors longer. The detergent generally takes care of any vinegar odor, and using a dryer sheet can also be helpful. When drying, use a tumble dry mode instead of a heat dry mode. This will keep some fading from occurring and keep the colors looking brighter.

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) 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) 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) 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) 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) 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) 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) 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) 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) 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) 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) QUOTE (Norm Kirchner @ Aug 9 2008, 06:57 PM) Denial is the primary indicator of a problem .... Hello my name is justin, and I love beer 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) 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) 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) 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