crelf

Have a look at the attached VI - should give you something to get started with.

Graph to display all previous activity.vi

Like Asbo, I code on too many different PCs for a single non-standard setup to be helpful (again, like Asbo, doing so is nonproductive). especially when I'm coding on someone else's PC (to help them with something) and they've changed a lot of the standard setup

I have moved from working in a team of four LabVIEW programmers (to just one)

Sounds to me like you'll need LAVA more than ever Congrats, and good luck in the new position!

Quick clarification on the "Report to Moderator" link that appears on all posts: please use this to draw the moderators' and administrators' attention to a post for any reason - doing so puts your request into a queue that all moderators are able to actively work through, and are able to track/sign-off/etc, so it's a lot easier for us to work with something in that system than it is if you PM one of us individually.

We don't always read every post to LAVA (shocking, I know ), but the "Report to Moderator" isn't only to report objectionable content: it's the best way to let us know if you need us to move/rename/edit a thread of your own too.

Done. In future, go ahead and use the "Report to Moderator" button.

I wanted to ping you guys in case you could think of anyone that might spring to mind: we’re looking to hire another systems engineer/technical lead (someone with a little PM background would be great too) with a strong technical background. Do you know of anyone who might be interested? Of most importance is getting people who know test, and know how to own the technical solution of projects, who are driven, positive people who are good to work with. Also, a medical background is, while not required, a big advantage.

PS: They don’t need to be LabVIEW superstars – just people who really know test – we can train them to the level of LabVIEW and TestStand that we need.

If you know someone, please PM me.

Doing things right from the beginning (or as soon as possible for retroactive situations) ALWAYS pays off in the long run. If not then we all ought to just be jusing shifts and FGVs, typedef clusters....

I'm all for doing things right, but let's look at the economy of doing this: NI is suggesting that plugins have thier code in vi.lib, but are they requiring it? What is the impact if we keep OpenG in user.lib? What are the risks of the migration - what might break, on different OSes, different versions of LabVIEW, etc? What is the time impact of moving everything over to vi.lib and testing it thoroughly on different OSes and versions of LabVIEW (keeping in mind that every minute it takes is a minute taken away from OpenG code development)? We haven't seen much new stuff come from OpenG in a long time, and I know that we're working hard (ie: mostly JGCode) to get all our ducks in a row so that we can have a good platform to grow going forward, but is this idea worth spending time on if it means pushing out new features even further?

PS: I have no philosophical issue with OpenG being in vi.lib.

Has anyone got experience with the TSVN Toolbar for LabVIEW from ViewPoint Systems? The features seem pretty neat (user manual here), but I'm wondering why I hadn't heard of it before now...

When you registered for LAVA, we asked you what version of LabVIEW you use the most: this is to help others frame their replies to your questions, and helps them to recognize that they shouldn't post a LabVIEW 2011 VI in a response to your threads if you've listed your main version as 8.2.

We added LabVIEW 2011 to the list in August, so now's a good time to update your profile to reflect the version of LabVIEW you use the most. Edit your profile here (and why not make sure all you other details are current, including yout avatar?)

That's a good link from asbo - since you access your UUTs through separate input/output resources, then you'll want the parallel process model.

Is it possible you're going into an infinite (or very very large) loop? Maybe a divide by zero going into the N terminal of a for loop?

...or you're reying to get more data into that task than the buffer can hold?

Use the right tool for the job: www.ni.com/teststand

In several other countries, it's illegal to be in the "fast" lane if you're not passing, and there's often a significant $ ticket if you get caught.

This sounds like a good project to learn about image acquisition. Christopher Relf (http://lavag.org/user/181-crelf/) has written a book about this subject. I'm sure he would appreciate a plug for his book. It's probably one of many places you could start.

Thanks for the plug - there's actually a section in it that talks about OCR, and uses licenses plates as an example.

The ASCII characters themselves are the same (eg: 0xF0 on a Windows PC is the same on a Mac), but it's the local representation that's different. I think you should be able to keep evereything in hex representation, so you don't have to deal with the issue?

Sorted

Oh dear, what have you done?!?

Crelf is correct (when is the man ever wrong?)

It's a pity that my missus isn't a member of LAVA.

OpenG accepts all types of re-use components as possible submissions.

Right, and I'm totally enthusiastic to see more of them - in general, custom controls (XControls or otherwise) is an area that's under represented in OpenG IMHO, and I'd love to see what people come up with as submissions.

I think including more XControls in OpenG is a great idea - but I don't think that a separate XControl package is the right way to go: I prefer my XControls to be in the packages that their technologies support (eg: an IP address XControl in a networking package). That said, I'm open to others' ideas...

So I finally got a day off yesterday and ... started skimming through my copy of Standard Mathematical Tables and Formulae...

Wait, what?!?

This begs the question, can I smell the color of a fruit?

Only as well as you can taste it

Extended into the physical/philosophical world, the idea is the same: armed with the knowledge of only the destination, one cannot know the path of the journey. Therefore, the ends may, or may not, justify the means.

I took François to mean that i.e. new version of the same package (therefore, new package).

Sorry, I didn't mean editing the existing package, I meant rebuilding it and deprecating the previous. A previous post looked like there would be 2 packges both being supported simultaneously. I think we're all on the same page now.

I think this is one of the biggest steps in recent memory to advance the professionalism of LabVIEW as a programming language: announced today, the LabVIEW software validation tools are now included with the developer suite! This means that anyone who purchases or renews their license for Developer Suite now has access to the following products at no additional charge: LabVIEW VI Analyzer Toolkit, LabVIEW Unit Test Framework, and the LabVIEW Desktop Execution Trace Toolkit.

Read more about this announcement here.

Hey Mike - nice hat!

Now that the new version of LAVA is so feature rich, it's easy to see that not everyone has assigned a photo/picture as their avatar! It's doesn't have to be a photo of yourself, just some image that describes you - so go forth and update 'em: let's see how creative you can get