Mike Ashe

You mentioned that it crashes the second time through the loop. I assume that it happens the same way if you run two copies, one after the other in a flat sequence. Also, what compiler are you using?

It's been done, several times, several different architectures. Since you are new to LabVIEW you might want to pick up a couple of LabVIEW books. The first original LabVIEW book was written by Gary Johnson. I believe he included a whole library to do exactly what you are asking. There is a new version coming out in July, if you can wait that long: LabVIEW Graphical Programming Cheers

Bad form NI, bad form ... It would be nice to get them to reverse this, or to give us a nice batch editor for doing our own. However, you can copy the constant from 7.1 and add it into the menus in 8. I know, we shouldn't have to, but it's a work around.

You might also want to check out: LabVIEW Webcam Library And if you haven't found it already, here is a college lab in running a USB webcam with LabVIEW, pretty nifty: U of Texas Lab Assignment: LabVIEW USB Webcam Cheers

My closest approach to Mel is through my wife, whose first cousin has been a cameraman, director of photography and lately director (Craig Dibona at IMDB). As for Mel movies, I still like Cisco Kid & Spaceballs Then again, Blazing Saddles, well ... Too bad the LAVA avatar can't fade from Kermit to Mel and back ...

Try this post: Kernel32.dll call to get volume info Cheers, PS: A little use of the Search feature makes it easy to find stuff like this.

Actually, now I think .NET might be a better way to go. Look at some of the recent blogs bythe LabVIEW developers. Search ni.com I thought I recalled seeing something recent. Hope it wasn't my old memory playing tricks.

For short to medium lists I use the listboxes, but for long lists I have only used tables/arrays for some time now. I never quite noticed a hang, but there has been an obvious performance lag for some time now. In a few cases where I really wanted certain listbox features and better performance I kept most of the list off screen in arrays and only parsed out a portion to display in the listbox at any one time. This takes a bit more housekeeping, but worked around the bug Michael points out.

Kermit, I mean crelf, what happened to the bowtie? Is the green cast from an over-indulgence of Veggemite? ;-)

I've used them very little myself so far, but I can see how they make life easier for beginners and also for when you need something quick that happens to fall in the configuration range of an available node. I like the potential for salable aftermarket addons based on nodes.

Did you check to see if the Triggering Modes are the same between the VI and Vision Assistant? Did you try to acquire images / video in MAX? Lastly, did you try some of the builtin example VIs that ship with IMAQ Vision?

I believe a boolean from a DLL is actually a 32 bit integer. I don't recall if it is signed or unsigned. Try both and run and look at the number you get out. Should be 0 or 1.

This was a good example of how to ask for homework help and actually get it. Good job to Filenapper! Perhaps we should point some of the HH's here as a good real life example. :-)

I'll third this. Do you mean the VI doesn't run at all or it runs incorrectly? Is it broken, if so did you click on the run arrow anyway to get LabVIEW's error/warning listings? For that matter, did you turn warnings on on the PC's that it does work on. Perhaps you might have some useful information there.

It's not the barbie size, but the succulence of the shrimp and sauce ... I wonder if barbies get better looking with :beer: :beer: :beer: the way Barbi's do? :laugh:

After adding the Scripting INI entries you can put a VI property node down and get a reference to the Front Panel, then wire up another property node to the ref and you can get an array of references to all the decorations, then iterate through those in a loop to get/set the size, position, and colors of decorations. Enjoy!

Once upon a time, back in BioBench development we did the header as a "trailer". The last 4 bytes of the file gave the header size, which we would read off the _end_ of the file by rewinding the file index pointer that far. That way we had an arbitrary length "header" on an arbitrary length file. The header gave descriptions and indexes back into the file for channels, data, etc. When we started to append new data, we would first read the "trailer" into memory, then append new data starting where the old header-trailer started. When we finished with data we would measure the size of the new header-trailer, write the trailer-header, then write the size. Only downside is if you have a power loss during your data run. YMMV

Yep, but a Tribble would be an even better icon, as this code is definitely born pregnant !

Download File:post-45-1149250373.llb Has anyone figured out how to read the value of a wire at runtime using scripting without attaching a probe? In the a few other threads others showed how to use GetProperty and SetProperty with the index of the property retrieved and looked up first in a variant from GetPropertyCallData. I'd like to use this technique to look at the counter in a loop or selector on a case or the wires (if any) going into or coming out from them and see if it fires or the count or the wire value. I'd like to do this by programmatically reading the property of the terminal or wire without making changes to the code. I can already get the effect on the wire by adding custom probes dynamically using scripting, but I'd like to avoid that. Along those same lines, does anyone know what: clumpNum short count fire count Properties really do and how to use them? I've attached a small sandbox with some of my play dough in it. Don't expect elegance, it's just a hack to experiment. Thanks!

The image of Scotty in "The Voyage Home" (aka Save the Whales) where he picks up the Apple mouse, turns it over, holds it up to his mouth and says, "Computer!" ... Even funnier is that we actually now have real transparent aluminum ... I'm still holding out for a lightsaber ... On another note: I had a medium sized post all ready, throwing in my 2 cents on this community.ni.com bit and the power went out here. I literally had my finger over the mouse to hit "Add Post". Too bad, as it was a gem if I do say so myself. I won't try to reconstruct it. Lets just say I've had a couple of good cups of coffee and a long coffe break walk since then and am feeling a bit more charitable, so Colin and NI get off easier. To summarize, Colin, NI sounds like Microsoft when you do what you have done here on this forum and then do what you've done on your new "community" site. Yes, I know, and want to believe that you (NI) wants to "partner", but frankly, NI has a pretty pee poor record when it comes to partnering with anyone it sees as smaller than itself and proclaiming loudly that "hey, we're really good guys, ... trust me" just rings hollow. I'll probably mousey on over to your new site, but so far it's a PR flop. Sorry, but you did say you come here for honesty. I'd like to be shown that NI can change back, at least some. I really would.

The Katinator 2006 ... My wife, as a major cat hater, heard me talk about reading this and she approved buying the kit in August for my 9 year old son. Easiest toy (dual meaning intended) acquisition approval in a long time and I didn't even have to negotiate jewelry or spa days. Son and I are excited. Thanks guys :worship:

Actually, most of what I have read leans towards Asperger's Syndrome, a high functioning form of autism. Although the two syndromes may also be found together. "Remember, luminous beings are we, not this crude matter ..."

Very interesting demo. This is along the lines of what I was thinking, only much more complex. I think it would be easier to do the coding if the person was not in the scene. It would also take a lot less computing resources. I agree that letting the person see themselves is "neat" and "gee whiz" but I was thinking of more of a serious coding tool improvement. I can see a VI hierarchy really looking like a tree, with zooming, color coding of branches. I can also see some really bad code, so the style guides would need some rework and a lot of effort to stay with good style.

I have not yet had a project that used PDAs so I cannot suggest image processing libs for that platform. Nor do I get into C# much, LabVIEW is my baby. That said, I think the best available is the Intel libraries I mentioned earlier. They are free, mature and you know that they will work with LabVIEW, because someone else has already done it. The downside with any external image lib is that it will take you some real work to make all the lib wrapper VIs. Try Googling on Intel Imaging Library open source or look here: Intel Open Source Computer Vision Library If you just want to do very simple watermarking, use the image reading VIs, convert to flattened pixmap, then do the same with a black & white image of your logo, then add, then convert back to image. Simple. Good luck.