TestPoint and CompactDAQ?

[jim@smf.org]

Hello, anyone use testpoint and able to access compactDAQ functions?  I have the 9172 chassis, 9401 DIO module, and 9215 A/D BNC module.  They all work fine in MAX and in C++ but won't recognize in testpoint...the log file says that DAQmx loaded but was unable to find any hardware....

I've used previous NI units with no problems and I'd really like to use the stuff I've already written so ...PLeeeeeeeeaaaaaassse help!

[Travis_W]

Hi Jim,

If everything is working properly in MAX as well as C++, the best way to go forward with this may be to contact Measurement Computing about what could be going wrong within TestPoint.  Their main page linked above provides directions for technical support.

Please repost with what you find out.  Thanks.

Have a great day!
Travis W

[jim@smf.org]

Travis,

Thanks for the info.  I have contacted them and it's the old story...they say to call NI regarding drivers and NI says to call CEC (or MCC as they were recently restructured).  I will certainly post if I get something working.

Thanks again,

Jim

[Travis_W]

Hi Jim,

I called over to MCC just now to follow up, and it sounds like they're aware of your issue and are currently in the processing of testing things out in R&D.  I'll let you know if I hear back from them first, otherwise I'll look forward to seeing your resolution to this issue.

Have a great day!
Travis W

[jim@smf.org]

Travis,

Regarding the NI9172 chassis and modules, the TestPoint AutoSearch function expects devices named "dev1, dev2...." whereas the default names for these modules are identified as a separate device, so, for example, the ai module could be dev1, the relay module could be dev2...etc.    I am told that a maximum of 4 devices can be used in this fashion which doesn't affect me (3 modules).  I have received permission from Robert Vice of MCC to post all of our correspondence  but the max character limit is preventing that so the best details are attached below. 

I have resolved everything except how to access the Counter/Timer functions in the 9401 DIO module from TestPoint.  Should I start a separate post for that?  Sorry, rookie forum dude here.

Here is the correspondence between MCC and myself regarding TestPoint and NI CompactDaq.  I can't thank you and Robert Vice of MCC enough for following this along for me.  If I can be of any help, please let me know.    Jim

Hello Jim,

I tested the board with my unit and it works properly under the example CEC-DIO.TST. You will need to copy the DIO module from the example and place it into your stock if you want to use it manually.

The A/D and D/A modules should work from the current stock. Unfortunately, I do not have any A/D modules to test them with the USB chassis.

Best regards,

Rob Vice
Applications Engineer
+1 (508) 946-5100 extension 2

http://forums.mccdaq.com

Thanks Robert, I'll try this out tomorrow.  If it works, I owe you a beer (understatement of the year).

Hello Jim,

I received the following information from the developer of TestPoint. I am in the process of installing the drivers to test this on my NI USB-9162 with a NI cRIO-9472 module.

When TestPoint does an auto-search for installed DAQ boards, NI boards are assumed to have device names of "dev1", "dev2", etc.

The default names for CompactDAQ modules do not follow this format.

There are two options to get around this problem:

1) Go into the NI configuration program (NI Measurement & Automation Explorer), and rename the modules from "cDAQ1Mod1" and "cDAQ1Mod2" to "dev1", "dev2".

- or -  

2) In the TESTPT.INI file, instead of just "auto" mode, change the AD settings to:

   [AD0]

   manufacturer=NI

   devicename=cDAQ1Mod1

and so forth..

Keep in mind that TP supports a maximum of 4 separate DAQ devices.  The CompactDAQ holds multiple devices in one chassis, but they are still separate devices, so we can handle 4 modules.

 The units we just purchased are the 9172 chassis, and the following:

NI 9215 with BNC 4-Ch analog input module,

NI 9481 4-Ch 30 VDC spst relay module,

NI 9401 8-Channel, 100 ns, TTL Digital Input/Output Module with C/T.

Everything works in C++, and in MAX software, but  testpoint tells me that DAQ mx drivers loaded but that no hardware was found.

We are using DAQmx v 8.1.

Thanks,  Jim

I have TestPoint version 6 running (licensed for v5 so a couple things are disabled) in both Win 98 and Win XP, both with all service pack updates. 

We recently bought National Instruments NI9172 CompactDAQ USB chassis and  A/D, DIO/CT, and Relay modules.  The DAQmx driver loads but fails to find the DAQ according to the Testpoint log file, although I can clearly see that the unit is working using NI MAX test software.   I have a lot of time invested in several critical programs and would very much like to continue with Testpoint.  I'm happy to buy an upgrade if that is the issue but obviously I don't want to buy it just to find out it doesn't work.

A wild guess is that the new system uses string id for analog channels, etc whereas past units use numeric id's.  This may or may not be relevant.  Please help!!!

Thanks for your time,

Jim Barnes
Test Engineer
Snell Memorial Foundation, Inc.
jim@smf.org
www.smf.org
916-331-5073

[Neil_S.]

Jim,

To be able to use the counters through the 9401, the 9401 must be installed in slots 5 or 6 of the cDAQ chassis.  Otherwise you will not be able to access the counters.  If you have the module installed into slot 5 or 6 you should be able to access the counters much like you would on any of our other Multifunction DAQ devices and the counters follow the same naming convention (i.e. ctr0, ctr1).  If you already have the module in slot 5 or 6 and are still running into issue we may need to look into the issue a bit further.  Let me know what you discover.

Regards,

Neil S.
Applications Engineer
National Instruments

Message Edited by Neil S. on 10-24-2006 12:54 PM

[jim@smf.org]

Neil,

Thanks so much for your reply.  Sorry for the delay, very busy couple of weeks here!  Yes I actually participated in the Lead User program for CompactDaq and am aware of the slot 5-6 requirement for CT operations.  For the NiDAQ driver and 6020e BNC unit, I had to build a function basically calling each separate code object to initialize, identify, structure, start, stop, and count from the counter.  Kind of a pain but was the only way I could get it done with the limitations of my pointed head.   I eventually made a UDO in TestPoint to go measure a pulse width which made it convenient to use.  I was just hoping not to start over from scratch again with DAQmx and CompactDaq. 

Again, I really appreciate the response and sorry for the delay for mine.  Jim