Mike Ashe

You might also want to look in the examples for Queued Message Logging, see: C:\Program Files\National Instruments\LabVIEW 7.1\examples\general\queue.llb\Queue Message Logging.vi If you look this up with the example finder you'll get a couple more VIs open, or just look through the library above. With a little tweaking you can have the logger change file names based on various criteria. I've done this a couple different ways, like sensing when you pass midnight, close the old file and open a new log file with today's date. Etc.

Awesome little nuggets, and with replies, controls, a graphic of the patterns. Thanks guys, more reason to stick to LAVA!

- code reuse - easier to read non-trivial size projects - looking like at least a journey(wo)man programmer instead of an amateur thats enough for now, there are other reasons, but those are sufficent

Ditto on the first two responders comments about the avatar. Change it please. I believe according to the terms of use of LAVA that foul language, etc, is cause for being deleted and banned. Take the hint.

Go to NI's website and read some of the whitepapers on NI's GOOP. They currently pass ba value only. There is no pass by reference. Not yet. Some people are already at work on wrapping NI's new stuff inside of some of the open source pass-by-reference toolkits available. Keep your eyes open.

Lots of us here are familiar with or have used VEE. It is okay, but isn't a general purpose language. Although LabVIEW is mostly used in test & measurement, it is also a GP language. VEE was hampered in it's implementationa nd graphical syntax by the patents on the basic G language. It has never measured up to LabVIEW. (pun intended)

Did they talk about why? Even if NI wasn't going to support it it would be nice if they released it as an unsupported kit, or better yet, but heaven forbid ... open source ...

Yep, it's a joke, don't worry about the punchline, it was codekill anyway... Okay, you caught me on that one... I thought that someone else on the forums was saying that Qubix had been canceled? I hope not.

Another One Hit Wonder Homework Hustler ! (OHWHH) Normal practice here on the forum has been to quickly roast such newbie's, but my coffee was pretty good this morning and I'm about to go for my second cup, so I'll be kind NI makes a vision toolkit that has a VI in it that does what you what. It is the IMAQ Vision Toolkit. I assume that since you are working IRIS recognition in LabVIEW that you already have the toolkit. The workstation that I am on at the moment does not have that Toolkit, but if you have it I suggest that you go through the palettes very slowly from start to finish til you find it. I believe it is called something like "IMAQ - Unwrap Meter.vi" or something like that. It is used to unwrap a portion of a circular annulus, before useing OCR to read numbers off of a meter. Seems like I recall someone else working on something like this here on the forums before. So try to search the forums here for appropriate keyworks. Lastly, why don't you post a VI showing us what you have already tried and explain what troubles you are still having. Then we can offer specific advice. (Okay, for the regulars, I know, I know, I'm breaking my own rules here, "don't feed the bears", but the java was rich today...)

If NI Week were held at Christmas they could change the blue ballons to red and add some costuming and we'd have Santa and the Head Elf ... :laugh:

Obviously NI has left out the by-reference method of GOOP in this version of their OOP. You can download and still use several of the other GOOP implementations, such as the SciWare GOOP Developer 2.0 which is free to try and even to use for non-commercial use. This uses the Open Source GOOP Template. Putting the OSGT together with NI's new offering might yield some interesting results. Rumor has it that this is already being thought about and worked on.

Try loking in the LabVIEW examples on graphing and displaying data. You should find multiple examples that you can modify easily to get what you want. If you are still having problems after that, post a VI showing what you have tried, and tell us about the remaining problems and we could give specific advice then.

A few years ago I was involved with an astronomy project that used both Red Hat and Mandrake, switching back and forth a couple of times in the years I was involved. Everyone liked the ease of Mandrakes' install and the extra attention to useability. But eventually they settled (at least when I left) on Red Hat because Mandrake had made an implimentation decision that caused issues with extremely large data structures, like astronomy images tend to be. YMMV

An image, of an image, of J.K. I know some of us are starved, not being able to BE at NIWeek, but surely you've met and talked with Jeff a couple of times or more by now?

Sad to say that you are not the only one missing NIWeek. Even worse, I've received a couple of calls on the cellphone today from people down in Austin rubbing it in, "Hey Mike, did you heard the announcement about..." Where's the emoticon for roll tapping your fingers on the desk with your chin in your hand ...

Trying mighty hard to get some more people here interacting with the larger LabVIEW community and to use some of the open source and free tools. Funny, that is sometimes such an uphill struggle at some of the larger companies...

Welcome aboard! Glad to have you. Be sure to read some of the introductions, such as: How To Use The LAVA Forums Out of curiosity, what do you typically use LabVIEW for? You have been programming for several years, so you're not a newbie to LabVIEW.

That's "Katinator", with a "K" My son turns 9 in Sept and he (okay, "we") have been promised this as the main gift :thumbup: Son will use the LEGO supplied software, and Dad will be checking daily for when this toolkit is available for download.

As others have pointed out, so close ... But instead of concentrating on what is still missing, I hope to see (and soon contribute) some examples of nifty things that people have been able to do with the new functionality. I guess my reaction is the same as it was when shared variables came out. Initially, I and many others, said, "Its just a glorified global", but they have been quite useful, even if they are not everything we wanted them to be in the first incarnation. I'm sure we will see improvements and additions to the new OOP soon. Til then, I'm still going to have fun with the new toys in 8.20 and Mindstorms as well.

You might be able to do something like this with scripting.

A couple of us were working on something like this using VI Scripting. Dropped development as soon as I saw the 8.2 beta but couldn't say why. I'm very glad to finally see this feature, we've been waiting for this for a while. Thanks NI!

This is so very cool! Of course, sometimes it's also very scary

Yes, Mike, a big congrats from us all. You need to speed back up though, Crelf is probably already looming in your rear view mirror. I took a minor pause after reaching 500 and he went by so fast I didn't see a thing, just heard the sonic boom and smelled the kerosene from the afterburners. Seriously, though, I really appreciate your foresight in getting the LAVA website and forums going and maintaining them in ever increasing functionality. Although I earned my Premium strictly through posting (thereby proving it could be done, nice to be the first on that), I will be posting a donation this next invoice cycle.

You get some sympathy, but not much from this corner. I'm going to be stuck in Owego, NY for NIWeek and today we sort of had to go home early. The Hammer of Thor took out the power station here at my current client in mid afternoon. Awefully glad the storm only lasted a few minutes. It was pretty impressive to see the lights go out and stay out, then flash as the lightning hit the power station repeatedly. Had a lot of people scrambling to disconnect their laptops, PC's and test systems. I still like the idea of Mid-Winter LAVA Conference to compensate those of us who can't make NIWeek this year.

Hmm ... your attachment doesn't appear to show up. I did try your cast -> string -> cast -> target and that seems to work fine as well. Funny that NI has not provided a conversion to more|less specific VISA type. Wasn't the promise of VISA that if we all used it we would have a single type & interface. Well, time to put this into the next request list to NI.