08-01-2007 01:23 AM - edited 08-01-2007 01:23 AM
The VI and the executable version both work well on the Development computer, needless to say.
Are there hidden port identifications or ather aspects that require to be matched?
Message Edited by Midlothian on 08-01-2007 01:26 AM
Message Edited by Midlothian on 08-01-2007 01:28 AM
08-01-2007 01:31 AM
When it "runs" on the deployed laptop the charts and the gauges show no signals despite all passing self-test and showing good SignalExpress traces on the desired channel names.
08-03-2007 04:39 AM
It could be a number of reasons.
Why not try some error handling?
If you place error clucters through the DAQ assistants, merge them and stop the while loop (and display a simple error handler box) you might have a better idea of what is actually going on.
The DAQmx vi's could be erroring out and you wouldn't know anything about it.
AdamB
08-03-2007 10:07 AM
Thanks,
The problem turned out to be related the the driver installation on the deployed laptop.
The DAQ's were working on SignalExpress and individually on the self-test but not together due to a service/device name error.