Labview executable doesn't port

[Chris E]

I've written a Labview executable (based around DAQmx) which works nicely on the PC I developed it with.  When I install the EXE on another machine I get an Error 200284.  The operating system and PC are almost identical.  I have a clean install of the same version of NI-DAQ on both.  The only difference is that the functional one uses a PCI-6034E card to talk to the SCXI chassis whereby the disfunctional one has a PCI-MIO-16XE-50.

Would this cause a problem?

[hannahW]

Hi Chris,

I have found a knowledge base article which describes this error and gives a suggested workaround. As the systems are not exactly the same, this is the likely cause of the error - related to timing.

http://digital.ni.com/public.nsf/websearch/001DA4DB6A31CF8886256D33006FA857?OpenDocument

Check the sampling rate that you have set up - problems that could arise from this are described in the following KB:

http://digital.ni.com/public.nsf/websearch/FEF778AD990D5BD886256DD700770103?OpenDocument

Also, as you are using two different PC's with two different cards, make sure the setup in MAX is the same - i.e device number. If you have used global tasks set up in MAX, make sure you have passed the configuration over to the second PC.

Let me know if you are still having problems, and post the code so that I can take a look at it.

Hannah
NIUK & Ireland

[Chris E]

I'm using virtual channels to get over the problems of having different hardware set-ups so the hardware configuration differences are invisible to my software. The software is non-specific:  it will use any virtual channel that is an analogue input.  I have read the error messages and I'm begining to think it's related to the way in which I'm using the 'DAQmx flatten channel string.vi' to turn an array of virtual channels into a comma delimited list.

The functional machine works with any number of channels selected whereas the dysfunctional one falls down if any more then one channel is used.  I wonder if the different hardware configurations are causing clashes between the multiplexer and ADC.

My sample rate is very low (typically 100 S/s) and I've set up the software to disallow silly combinations of samples per scan and scans per second.

[hannahW]

Hi Chris,

How have you got the SCXI system setup on the second machine? Is it the same as for the first.

Is there any way you can post the code on the forum - this would be most helpful in determining where the problems lie.

Also - can you take some screen shots of MAX - or generate the MAX report ("Help>>System Information and Support" and generate the simple reports) for both PC's - this will provide me with more detailed information for both PCs.

Thanks

Hannah

[Chris E]

With it being Labview I'm not sure quite how I'd go about posting it,  we're talking about a large and multi-layered block diagram.  Sasha at Newbury might have a copy of it,  its called Homer DAQ 1.0g otherwise I might be able to e-mail the file.

Both PCs have identical drivers installed at identical versions.  The only differences are that one is a 1.7 GHz P4 and the other a 2.0 GHz and that one has Labview installed but the other doesn't but that should be immaterial as I've used the application builder to turn my diagram into an .EXE.  Both PCs are clean setups meaning the last thing that they had a complete re-format of the hard drives to remove any NI legacy problems as I've had that nightmare before.  It's really,  really strange.

It's strange that we've been using the program for about a year on the Labview equipped PC without any issues.  I want to set up the program on another machine so I can develop something else with the Labview one.

[hannahW]

Hi Chris,

Sorry for the wait, I've been away on holiday

I've asked Sacha if he has the code, but he says he no longer has a copy of it. It would be useful to look at the code in more detail, so I can see the where the problems may be coming from - if it is the DAQmx flatten channel string.

If you can provide me with your e-mail address, then we can continue this via e-mail which will make it easier to pass code around.

Regards

Hannah
NIUK & Ireland