Re : Re: DAQmx simulated device

[NicoLeach]

I can't  be of any help about how SCC / SCB are seen by MAX.

It's odd to be unable to see your board in MAX.
=> Can you see your board under the windows device manager?
=> Are you using a version of DAQmx newer (or eq) than 7.5 (it's the oldest I've found with a support of the 6254)

About the distribution kit size. You can choose what runtime / drivers you distribute under the "Drivers & Components" tab.
I choose to never distribute any drivers or component with my software (I'm supposed to have a real traceability of my testbenches configuration)

Nicolas.

[Humph]

Using DAQmx 8.6. I was advised to use Runtime 5 in the distribution kit (see top of this thread). Could that be a problem? If you don't distribute any components, does that mean you rely on the DAQmx installation that comes with the card? I'm going to rebuild the dist kit without DAQmx now.

[NicoLeach]

What do you mean by "Runtime 5" ?
DAQmx 8.6 (Nov 2007 supplied with CVI 8.5, Teststand v4.x ) may be a problem if you install it over a previous installation of DAQmx. (The main problem I've encountered was MAX related [my boards configs were destroyed] )

If you build without component, you rely on the DAQmx installation previously existing ont the target computer.
If you rebuild the dist kit without DAQmx driver, it won't uninstall the DAQmx you installed with yout previous dist kit.

Maybe someone from NI can join the thread to check if the problem is 'DAQmx nov07' related or not...

If nobody from NI shows up, i would advise to:
*Unplug the board
*Uninstall DAQmx
*Reinstall DAQmx (Not Nov2007 8.6 if possible)
*plug the board
*Check what MAX is able to see.

I'm afraid I won't be able to help for long today (It's about time to leave for me)

Nicolas.

[Humph]

OK. Built dist kit without DAQmx. Can now access the PCI 6254 via MAX in the target computer. Data from the channels looks good.

Running the Application still gives the rubbish numbers which change only when the mouse is moved from the active panel to the background. Remember that I've built the kit with simulated DAQmx device. Am I still missing something?

[NicoLeach]

"the rubbish numbers which change only when the mouse is moved from the active panel to the background" => Do they stay rubbish numbers when the mouse is moved?
Are you using the same identifier for the 6254 in your software and in MAX?
Are your Daqmx tasks created, defined and 'stored' under MAX (if so, you should include them in your dist kit)

Nicolas

[Humph]

Hi Nicolas,

We got it all sorted late yesterday afternoon. We adopted your solution of building a distribution kit with just the LabWindows/CVI Run-Time selected in the Drivers and Components tab of the Installer, and installed MAX from the disc that came with the device. I built a noddy system from the Acquire Internal Clock example which gave me error -210009, something about trying to digitise values before they had been scanned. So I dropped the sample rate in my application from 500K to 10K (I'm scanning 10 channels 10 times every 40 milliseconds) and it all sprang into life. It would appear that I am not handling errors correctly in my application, and the scan statement was failing due to the high scan rate, so my data area was probably being jumped upon by Windows as I moved the mouse.

Many thanks for your efforts through yesterday, it was a great help to have someone to discuss things with.