Copy config to another pc

[Justin D]

Anthony,

In order to find the source of this error you really need to look at the source code.  The error is clearly occurring in the "Config Data Registry" vi.  If you put a breakpoint in this VI you should be able to find out exactly where this error is being thrown.  If you post this vi here I can take a look at it and see what the problem might be but realistically if there's someone there that knows how to use Labview they would be the best one to find out exactly what's going wrong (since we don't have your exact hardware setup).

I hope this helps,

Justin D.

Applications Engineer

National Instruments

[Cytokin]

Unfortunately, the person who knows LabView has asked me for help. What vi do you want? Can I email it to you?

Thanks!
Anthony

[Justin D]

Anthony,

The VI of interest would be "Config Data Registry.vi" because this is where it seems to be crashing.  If you attach this vi to this discussion forum thread I'll take a look at it and see if I can find any clues as to what could be going wrong.

Justin D.
Applications Engineer
National Instruments

[Cytokin]

That .vi file is embedded in a .llb file. Do you want me to post the whole llb file? or is there a way to pull the .vi file out of the .llb? ..... sorry.

Anthony

[Matt_S.]

Hi Anthony,

You should be able to just open the VI and save it somewhere else (like your desktop), then post it here.

Let us know if that doens't work out for you.

Regards,
Matt S.

[Cytokin]

Here is the VI. Thanks!

[Justin D]

Anthony,

The error that you are getting is a custom error that you guys construct in your program.  The reason none of us had seen this before is that it is totally proprietary to your VI.  Error "0" really has nothing to do with it.  You guys just never gave it an error number so it defaulted to 0.  Here's the relevant piece of code that does this...

It looks like this error is thrown when the "config data" that you are looking for is not found in the 1D array of config data that's stored in a shift register in your while loop.  Why this condition is occuring....I really don't know.  That would be best determined by someone who really knows this application since this error is not a LabVIEW generated error.

I hope this helps,

Justin D.

Applications Engineer

National Instruments

[Justin D]

For some reason that image didn't post.  Here's a link to the image.

ftp://ftp.ni.com/outgoing/custom_error.JPG