jcarmody

This is what solved the issue, I just missed the significance of what you & ShaunR said until after taking an NI Machine Vision course last month. I still need to overlay the processing parts, but the big nut has been cracked. Thank you.

So you don't need LabVIEW for this particular problem; that's good. You can probably do this with LabVIEW, but it's not the best tool for the job; LabVIEW is really good for applications that interface with hardware. Can you pick a different project to familiarize yourself with it? Something with DAQ or instrument control?

Why must you use LabVIEW? This sounds like a job for Excel's VBA.

The lighting & focus are the same. I expect that the camera settings are different, but I don't know what to look for. I can LabVIEW well enough, but I've never visioned.

I asked a question on the NI site about an odd difference in images in software that I inherited - http://forums.ni.com/t5/Machine-Vision/What-s-wrong-with-this-image/m-p/3573561#U3573561 I get different images in two versions of a software my predecessor wrote, but I can't get the source code to make my desired image (the first one). I've attached the Vision Acquisition Express VI that is used in the software on my NI post. Can you tell me the difference and how I can get the nicer image?

Buy the module and ask NI.

I'd have to say that my biggest weakness is that I care too much. I will work and work and work and work until the job is done ahead of schedule and below budget with all expectations exceeded and everyone is happy. Puke!

If you have significant experience in any programming languages, but not LabVIEW specifically, I'd be satisfied (as an interviewer). Graphical programming is certainly a different kind of animal, but programming is programming, and you can add another language to your repertoire faster than you learned the first few. If you don't have significant experience programming, share with them (and with us, please) what you hope to bring to the table while you improve as a developer. I've interviewed several engineers that had the AUDACITY to put LabVIEW on their resume just because it was in a class they once took or they used someone else's stuff. Oh, the horror! I was not impressed and they were not hired. I'm thoroughly jaded...

Our Materials department tells me that "Suppliers are liars". Still, we don't do 100% inspection on incoming goods.

I had to zoom into the picture (to see your name badge) to be sure it was really you.

Now I feel like growing some hair on my face. Good job, gentlemen.

I figured that you knew, I just wanted others to see what's already been said. This is a common practice on these fora, not a commentary about you.

Cross-posted.

hooovahh's post represented my immediate reaction to your offer; I look forward to the source. Of course, why should you trust us? Once we see how you did it, we can write whatever we want as a high score to the "altervista space".

You'll add the random number and a different constant for each row you make. The random number generated will be between 0 and 1, so, for the first row you'll need to add zero; add one for the second row, etc. Try making nested loops and see what you get. Do you understand how rows & columns of a 2D array are generated in this fashion? Are you familiar with the For loop's "i" and "N" terminals? Show me your code, Wireworker, and I'll show you mine.

Where do your numbers originate? You can use nested For loops, an Addition node and a random number generator.