James N

YES! I poked around ni.com but didn't find any discussions there. Thanks, Chris. -James

I've lost access to a couple functions in the Configuration File VIs between LV8.6 and LV2009... In 8.6 we use "Config Data Get File Path.vi" to return the configuration file path from the config file refnum. This VI no longer exists and the equivalent VI in LV2009 is "private" in an lvlib, so I can't use it. Same goes for "Config Data Write To File.vi", which we use to write data to the file on the disk without closing the config file refnum. It can be worked around but it's not elegant... grumble grumble.. -James

I was working on something today and thought a "Concatenate Inputs Horizontally" would come in handy some times.. That way I could get rid of these 3 transpose array functions. I'm usually not on the cutting edge of thought... something like this hasn't been discussed before, has it? -James

Yeah, Cluster Function just rolls off the tounge.. Queue T. Pi Project Destroyer Bundle by Pain Booly-Eon Flux Pleasument & Domination Explorer Now, how many standard NI/LabVIEW terms work... Quick Drop Gigahertz Digitizer Switch Executive -James

QUOTE (crelf @ Nov 26 2008, 03:57 PM) Awww... come on. I got to play opposite Tim on stage at NI-Week 2003. I thought I was playing the straight man. Tim and everyone was fun to work with that year. He even recongized me this year.. not by name.. but good enough for me. It was my best http://digital.ni.com/demo.nsf/websearch/cab99ea348a950ef86256d830000df07?opendocument' target="_blank">15 minutes of fame. And that evening everyone offered to buy me drinks at Buffalo Billards.. up until about 10pm.. hhmmm. -James

QUOTE (jdunham @ Oct 6 2008, 12:54 AM) Me too. There are several groups of LabVIEW developers at my company. Another guy started out his repo with the lock-modify-unlock method and convinced me with a demo. Now I'll have to convince my guys. Along this line.... I found this site that details how to alter existing repository files with the svn:needs-lock property. http://www.orcaware.com/svn/wiki/Automatic...k-modify-unlock -James

QUOTE (Ton @ Sep 16 2008, 11:37 PM) Is this true with any underscore directory name? We've started using the directory name "_Core" for some common files. Would this directory be ignored with a mass compile? And I suppose it would not automatically show up in the palettes either, right? Are there any other LabVIEW idiosyncrasies with "_" directories? -James

QUOTE (JFM @ Aug 28 2008, 01:30 AM) I will third that. For example, we have a standard VI that creates a directory. The auto error handler will post an error if the directory already exists... well... OK. That's what I wanted.. a directory there. If it's already there, then good! As I type this I realize that if I know an error routinely happens, I should avoid it. I should probably check if the directory exists first. So maybe the auto error will point out places that I should correct.. like jdunham does. Thanks a lot.. now I feel compeled to turn on the automatic error handling... -James [edit] I just check the VI that initializes paths. I do check if the directory already exists. Sometimes I'm good and don't even know it.

QUOTE (crelf @ Aug 14 2008, 03:56 PM) I was just ribbing you. I'm would never mean to suggest any unethical business practices are occuring. Please don't take it that way. I agree, if someone produces a great product or does a great job, by all means, praise that effort publicly. I was just looking for ideas from those who haven't mastered the chainsaw, but are still plugging away with axes. -James

QUOTE (crelf @ Aug 14 2008, 11:28 AM) I guess these's something to this thing call VIPM... hmmm. I suppose we'll have to break down and take a look at it sometime. Yeah, I kinda figured VIPM would be one of the responses to my question. As it should be. Anybody else not in cahoots with JKI? -James

Our department uses Subversion and TortoiseSVN with about 10 developers. Love it! I would use it if I were alone on a deserted island (aside from the inherent technical challenges on a deserted island). Another Side Topic (if I may): How do people handle LabVIEW versions in their SCC? I don't think this has been discussed here.. I didn't read every post completely. I'm primarily talking about the migrating a Reuse Library to newer versions of LabVIEW while minimizing the affect to older LabVIEW code which must be maintained and/or is still being developed. I don't really think I want multiple directories in my repository, such as "LabVIEW8.2", "LabVIEW8.5", etc., branching the library with each new LabVIEW version. I know there's no reason to mass compile a library just for the sake of mass compiling it, but as new VIs are added or older VIs are modified and saved in newer versions of LabVIEW.. this will affect down-level users. Thoughts.. -James

With the Vision Acquisition Software installed, you should just be able to plug in the camera (and power of course) and the system should recognize the camera. It may take a few seconds. You should then be able to launch Measurement & Automation Explorer and see the camera under Devices and Interfaces. Here's a great resource for GigE http://zone.ni.com/devzone/cda/tut/p/id/5651 Also, never over look the examples. Launch LabVIEW and click Help>Find Examples. Browse "Hardware Input and Output>IMAQdx" There may also be some issue with your network card. The camera documentation should detail any special needs for setting up the network card. -James

You can right click on the graph and select Data Operations > Make Current Value Default. Then save the VI. This will also save any data stored in the graph. So you may want to select Data Operations > Clear Graph first. -James

Mine has it.. I don't think I did anything special. Just drag the icon in the web address to the shortcut bar. -James

There is a Vision Acquisition assistant. This and the example VIs will get you a long way. -James