crelf

Awwwwwwww - now you're embarassing me...

Not yet Maybe you could be the start of something?

I agree, TobyS!

By Jove - he's got it! Hurrah and well done!!!

I don't know enough about your project, but if it's going along the lines that I think it is, please please please consider using TestStand. <soapbox> Every integrator that I've ever worked for has attempted to implement a test execution application/utility, and each of them has failed with a lot of money and time wasted... </soapbox>

:thumbup: This would indeed be an excellent application for OO.

You're right - the travelling salesman model is highly theoretical and I don't think it's actually what you're after in this case. I agree with the other guys: a cheap (~$1-2k) firewire camera and lens hooked into an IEEE-1349 card is your best bet. Allied Vision Technologies sells decent hardware at a good price (and they have a two week test drive programme), so as long as you've got some Vision experience and the NI-Vision toolkit, this job should be a cakewalk.

What do you mean by "inaccurate"? Is the signal offset? Is there a nonlinearity? Are you sure the inaccuracy is in the DAQ card? Could the issue be the Signal Generator? My guess would be the latter... Open up MAX, click on "MAX Help" and then do a search for "Self Calibration".

So let's assume that the real problem is that you can't write into the table and ignore the reading issue for the moment. Are you sure you have permission to write into tables? Check you persmissions. Can you upload the DB for us to look at?

You will be assimilated

Nicely done!

A quick LAVA search for "+motor +graphic" yields this thread.

Does that mean that I could step over the 5th dimension, or tunnel through it?

That's a pretty cool workaround

I think we're all a little mixed up here - is the problem that you can't write data into a table, or that you can't read it out from a table?

Don't look at me - you'll change where I am!

Bugger! :laugh: I couldn't replicate your problem - now I know why

Your verbiage may actually be the key here - you say it "saves 3 more files" and not "3 more VIs" - what are the files? Is LabVIEW saving some kind of history? Is the project itself one of those files? Is it one of the support files (eg: aliases)?

Please upload your code so we can comment.

So I just need to take a really really short walk along some sort of Planck to get there?

Defend it all you like - the NI VI Analyzer would vomit if it saw that VI :laugh: That said, I'm sure it'd be even prettier with the NI Logo execution highlighting on (labview.ini easter egg)...

Could you please mock-up a VI ro two to explain what you're asking? It'd be a whole lot easier to discuss what you're asking with something graphical to work with

Nice coding Ben!

Sorry about the wait - there's a bug in the forum software that means members of the LAVA Certified Team aren't notified when there's a new submission. As they say, "we know it's an issue, and we're working on it". I'll get one of the team to review your submission ASAP.

So how did you end up doing it? Please share your findings with us :thumbup: It's only through the sharing of our triumphs and failures that we learn for each other...