08-18-2006 03:12 AM
08-18-2006 06:20 AM
hi there
i know this won't help you, but i'd switch to DAQmx. Programming is much easier and performance much better. and you can get the information you need from some device properties (see attachment)...
08-18-2006 07:22 AM
08-18-2006 07:58 AM
"Is there an easy way to reconfigure this in MAX 4.0 to use the DAQmx functionality?"
i'm sorry, i don't know...
if you can access all devices with DAQmx i'd consider to remove NI-DAQ from the system and then build up the configuration in MAX from the scratch. maybe you have to write some new code for the DMM but that should be worth the effort. the reward is a clean system/application using a single driver layer.
08-18-2006 08:30 AM
Hi again Chris
Having just checked NI's website, it appears that the 4060 is not supported by DAQmx, so it will have to stay configured as NI-Daq. All of the other PXI devices in my system are supported by DAQmx, thankfully.
Cheers for your help
Mark
08-18-2006 08:43 AM
hi there
have you looked over the NI-DMM VIs shipped with the 4060? maybe there are some useful VIs for you in that layer.
08-31-2006 06:15 AM
08-31-2006 08:00 AM
Kurt
I actually used the 'Get DAQ Device Information.vi' to retrieve the 4060 serial number in the end. I considered using ModInst to query the 4060 but dismissed it because I read that 'Currently, it only supports the NI-SCOPE driver and is released with NI-SCOPE 2.8'. This was probably true back when the article was written (April 2005) but now ModInst works just fine with my traditional NI-Daq device!
Thanks for your help
Mark