Unsupported cDAQ module

I've been using a NI cDAQ-9172 with several operational modules. I installed a new NI 9213 TC module (the only one in the crate), and MAX is saying the module is unsupported. If I switch to a different slot in the crate, the problem moves witht the 9213 module. I'm running 8.6.1 and have not had any problems with drivers for other 9000 series I/O modules. Any suggestions?
Greg
Greg R.

Well, it looks like LV 8.6.1 ships with DAQmx 8.8. So that should have worked. I loaded DAQmx 9.0 and rebooted, and now all my modules are recognized. So either the reboot did it or 9.0.
Thanks much!
Greg R.

Similar Messages

How to read data simultaneously from different cdaq modules?

Is there a way to synchronize input from separate cdaq modules?
I need to read a voltage on an NI-9219 analog input channel and a
frequency on an NI-9211 channel. As far as I can tell a single "task" can
only read input from channels on one module. Is there a way to build a task that reads data from multiple modules?
Seems to me that buffered input is useless when multiple tasks are employed. With multiple tasks you get arrays of data that are sequential, not simultaneous. Is this correct? I'm thinking that the only way to
get synchronized readings is to read each channel individually inside a
loop. But this restricts the program to low speed data
acquisition with measurements that are spaced unevenly. Right?
I want to create a data file with three columns: time, voltage,
frequency. What's the best way to get these readings at the same
instant?
Referrence to a help document or tutorial would be great.
thanks!

Synchronizing measurements of different types using separate cDAQ modules can be done by making sure that the physical channels for each module IO control are selected (and separated by commas). Please review the following Developer Zone article illustrating how this can be accomplished. Cheers
1. NI-DAQmx: NI CompactDAQ Module Synchronization: http://zone.ni.com/devzone/cda/epd/p/id/5259
Regards,
Ali M
Applications Engineer
National Instruments

Accessing cDAQ-modules from 2 different computers ??

I am maybe asking a hopeless stupid question here, but working from the thesis that there is no such thing, here goes;
If I have a NI cDAQ-9188XT with a NI-9401 DIO module, where I use 4 lines for digital output and 4 lines for digital input,
is it possible in any was to access these 8 lines from 2 different computers more or less simultaneously ?

Yes, but not directly.
Set up one computer to directly talk to the cDAQ. From that computer, either update deployed shared variables for other PCs to read or setup a network with another form of communication such as network streams or TCP/IP. The first method doesn't require the second computer but is lossy (it won't check to see if other applications read the updated variable).

Find cDAQ modules and channels

I have searched around previous posts, but can't seem to find quite what I am looking for.
In most of my experience, I have set up some DAQ and once the modules and channels are all in place, that is where they stay forever.
Since I know things aren't going to move, I create tasks in DAQmx.
I'm working on a new setup now, but the issue is that in the cDAQ things will not be in the same place every time.
The application is to read a number of strain gages, which will be connected to NI 9235 modules.
There will be anywhere from 1 to 3 modules hooked up, and they can be in any of the 8 available slots of the cDAQ 9172 chasis.
Also, within a given module, anywhere from 1 to 8 channels will be connected.
So basically, I guess my questions are at run time:
1) How many modules are connected, and where?
2) In each module how many channels are live and how many are empty.
From there, I can use the DAQmx palette to take care of things.
Thanks!
Cory K
Solved!
Go to Solution.

Alright I'm making slow but steady progress on this.
I seem to be stuck on the actual task of actually aquiring the measurements from the gages.
Ideally, I would like to acquire 1 sample per channel at a rate specificed by the user on the front panel.
However, for some reason it will not allow me to use "NChan 1Samp", it keeps telling me this
I have attached my code if someone wouldn't mind taking a look at it.
Cory K
Attachments:
Rings.vi ‏28 KB

9207 Cdaq module

Hello,
Where can I get the following drivers:
NI 9207 16 ch V/C input module
NI 9403 32 channel TTl DIO module
9208 16ch current input module
ni 9263 4 ch analog output module
which will be used in a CDAQ-9174 chassis.
thanks

You just need to install the DAQmx driver:
http://www.ni.com/drivers/
Adnan Zafar
Certified LabVIEW Architect
Coleman Technologies

CDAQ module for high speed pulse counting

I need to know a USB module which can be used for pulse counting. The pulses are generated from an encoder attached with an stepper motor. It generates 15 pulses per step.Pulse amplitude is 0 to 5V. I am using a compact DAQ system (ni 9178).

The counters are on the cDAQ chassis backplane (there are 4 of them on the 9178). So, in order to use an external signal with the counters you would need a way to route the signal to the backplane. Your available options are:
1. Any digital I/O module with 8 or less lines on it (some modules are input-only or output-only--input modules can be used for counter input tasks only, output modules can be used for counter output tasks only). Modules with over 8 lines transfer the data serially to the chassis backplane and so do not support routing signals through to the counters.
2. The 2 PFI lines on the 9178 (I should have mentioned this earlier, this might be a good option for you to route your encoder pulses without having to purchase an additional module if you only need 2 inputs--that is, no Z index signal). The bandwidth on the chassis PFI lines is lower than that of the 9401 and 9402, I believe the chassis PFI lines should take signals up to ~1 MHz.
3. An analog module with triggering capabilities (at this time only the 9205 and 9206) can route a digital signal (the 9205 and 9206 have a PFI line) or an "analog comparison event" (see my post here) to the counter terminals.
In case 1 above, you configure this by selecting the counter using the module's name (e.g. "cDAQ1Mod2/ctr0"). Default input terminals will be used (check the device pinouts for your module in Measurement and Automation Explorer) or you can select which terminals to use for your inputs using a DAQmx channel property node.
In cases 2 and 3, you would need to select the counter as the internal backplane counter (e.g. "cDAQ1/_ctr0"). You will need to select which terminal your signal is coming from (since the internal backplane counter does not have default terminals. This same method can be used to count internal signals (e.g. sample clocks, counter outputs, etc.) without having to use any of the 3 routing options mentioned above.
Best Regards,
John Passiak

CDAQ module to genarete 5 to 2000Hz signals

Hi,
I am looking for a cDAQ output module which can generate 0 to 2000Hz frequency signals
Thanks
Prashant
Solved!
Go to Solution.

Hello UPRR,
As long as the module has an update rate higher than 20kS/s then you should be fine. so NI 9263, NI 9264, NI 9265 and NI 9269 should be fine for you.
Regards,
Miriam
Field Applications Engineer
NI Colombia
CLD

NI 9205 module not working

Hey,
I had a question about a specific module on a NI chassis. The NI cDAQ 9172 chasis, more specifically the Analog input slot wont show up on measurement and automation under the Devices tab. The analog output as well as the counter slots in the chassis show up and work fine. To trouble shoot I tried putting one of the analog output slots (NI 9263) in the Analog input slot and the chassis picks up this fine in Measurement and Automation under the Devices tab. Im not sure whats wrong as the analog input slot was working fine then all of a sudden stopped working.

Hi nicksony231,
It sounds like there maybe an issue with the 9205 module itself. Can you try opening Windows Device Manager and see if you can find the device there? When you are in Device Manager, you can expand the "Data Acquisition Devices" and you should see all your CDAQ modules listed there. If you don't see the 9205 there then you may want to try another slot and see if it shows up then. If it still doesn't show up, then you can call 866.ASK.MY.NI and we can create an RMA if need be.
Thanks nicksony231!
Best Regards,
Brandon G
National Instruments
Precision DC Hardware Engineer

Multiple concurrent LabVIEW apps sharing card resources in one cDAQ chassis

I'm looking for help, reallly a yes/no answer and/or pointers/suggestions as to the feasability of as well as how to have multiple LabVIEW apps run concurrently and share resources (cards) from a single cDAQ module. The background is that I have an array identical of LabVIEW test systems that are used to perform testing in environmental chambers, and there are many different standardized tests that they run, ideally some (that use different resources) at the same time. The problem is that different tests use different subsets of the cDAQ resouces, but the goal is to be able to run multiple tests/apps (for example, for multiple pieces of equipment in the environmental chamber) at the same time). Can LabVIEW apps be structured such that they can share a module in a cDAQ chassis? For example, if I have 20 thermocouples connected to the chassis that can all be scanned/read at the same rate (around once/second), can one app read some of them and another app read others of them virtually concurrently, perhaps by sharing a common task?
Any advice as to how something like this could/should be done would be appreciated.
Thanks.

I would also make a separate application to handle the DAQ stuff. Depending on what you need, I would likely use a combination of TCP/IP, UDP, and shared variables to send commands, stream data, and get latest data.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines

Single Wire CAN cDAQ

I have would like to use cDAQ for a set of testers that will be built. These testers need to talk to various hardware and I wanted it to be flexible so I choose cDAQ because modules can be swapped out for I/O that is needed. I saw that high speed CAN, low speed CAN, and even LIN is available in a cDAQ form factor, but single-wire CAN is not.
Is there an option for a single-wire CAN cDAQ module that I am not finding? Why would NI not support a single-wire CAN interface on cDAQ when they do on PXI/PCI?
Unofficial Forum Rules and Guidelines - Hooovahh - LabVIEW Overlord
If 10 out of 10 experts in any field say something is bad, you should probably take their opinion seriously.

Our solution if anyone else is looking to do the same is to use an Intrepid neoECU hardware, which is a scriptable device with high speed/single wire CAN, LIN, and general purpose I/O. It comes with some examples and one of them is a CAN gateway to convert high speed CAN messages to single wire CAN and backward.
We have this little device sit between a cDAQ high speed CAN device (NI 9862) and a signle wire CAN hardware to test. We talk high speed CAN over 9862 and the neoECU sends out single wire CAN. Obviously there are limits because the baud rate for high speed CAN is higher and you can over load the single wire bus, but if you just are aware, or setup filters on the neoECU it works fine.
This device can also be used as a LIN gatway as well sending LIN data back on high speed CAN but we haven't tested that part yet. One downside is to program the deice you need to have a license of Vehicle Spy which is Intrpids CAN software. It does have a trial and that maybe all you need.
Unofficial Forum Rules and Guidelines - Hooovahh - LabVIEW Overlord
If 10 out of 10 experts in any field say something is bad, you should probably take their opinion seriously.

CB-68LPR to NI cDAQ 9172

How would I wire from CB-68LPR to NI cDAQ-9172 ?

The CB-68LPR cannot be connected to the cDAQ modules. You will need to connect your signals directly to each module. You can find the pinouts for the module on the module, in the manual, or by right-clicking the device in MAX and selecting "Pinouts".
Otherwise, you will need to pay a third-party company to create a custom cable for you that will go between the terminal block and the modules.
Seth B.
Staff Test Engineer | National Instruments
Certified LabVIEW Developer
Certified TestStand Developer
“Engineers like to solve problems. If there are no problems handily available, they will create their own problems.”- Scott Adams

Multiple channels in one task with ch to ch config

Hi,
Normally the way I acquire sample from more than one channel on a cDAQ system is like this:
1, I create virtual channels for my AIs in MAX
2, in LabVIEW I use channel constants and merging them using comma as a separator (eg. with the concatenate string node).
3, the I configure the sample clock using the comma separted channels as an input
4, start the task
5, acquire samples
6, stop and clear the task
This worked just fine so far as I acquired samples from my cDAQ modules with the same speed and all of them were simple analog inputs. But I have to implement a strain gage measurement (NI 9237) now and I'd like to use the bridge offset nulling calibration VI to get rid of the offset I have. That complicates my structure.
It seems the VI I have created runs just fine but I am wondering if this is a legit solution as I used the sample clock twice. (the VI uses simulated channels for now)
Attached the VI (LV2012) and its block diagram image as well.
Please advise. Thanks!
i-
Attachments:
Strain_test.gif ‏14 KB
Strain_test.vi ‏36 KB

I have failed to realize that the offset nulling VI has another input called "skip unsupported channels". This is false by default, but setting it true resolves the problem without changing my structure at all.
Well done, kudos to myself
Attachments:
Strain_test2.gif ‏8 KB

Hangs on Waiting for UDev uevents to be processed

On startup it hangs on "Waiting for UDev uevents to be processed". Sometimes an extra row saying "[ 6.423351] firewire_ohci: Failed to set Link Power Status" is shown, and sometimes the screen goes all black before it hang.
Last time I was logged in I made some upgrades (pacman -Syu), so I guess that could have caused this problem but I'm not sure how to fix it.
What should I do?

This is most probably a kernel bug. More specifically, a problem in a module that is being loaded on boot by udev. You can boot into your system by appending "init=/bin/bash" to your kernel commandline (in GRUB). First of all I'd uninstall any third-party (unsupported) kernel modules that you might have installed. If that does not work I'd revert to a previous kernel version and file a bug.

DAQ Assistant Tasks

How do I create a task in LabView DAQ Assistant for one of our cDAQ modules without actually being connected to the cDAQ module?
Solved!
Go to Solution.

You can simulate a large scope of instrument supported by DAQmx with Measurement & Automation Explorer.
Right click on NI-DAQmx Peripherals then Create new then Simulate and choose in the list of supported device.
For cDAQ, your chassis in first then your module.
Excuse me but I don't have an english version of MAX and so, I don't have the correct translation of command...
When your simulated device is configured, you ca use it with the LabVIEW DAQ Assistant.

Signal express record from 3rd party VI driver

Hi,
Highlight - Can I record data from a 3rd party VI driver in signal express?
Detail - I am tasked with developing a 'easy to use' data logging system for both voltage and temperature. Voltage will be logged via a NI cDAQ module, no problem here, temperature however will be logged from a LakeShore temperature controller, ie from a third party driver. My first thoughts were to use Signal express rather than coding my own GUI, obviously SE is easy to use for cDAQ Voltage modules.... but has it been crippled to prevent the use of VI drivers for third party kit?
Ideally I would like multiple series plotted and recorded by Signal Express, some from the cDAQ modules and some from one or more Lakeshore temperature controller and monitors, is this fundamentally possible in Signal Express? I can see that SE seems to have the ability to run labview VI's so I am hopefull!
I am using NI 2013 - full bells and whistles.
Cheers,
Chris

Hello wonderwizard,
Yes you can use a Plug & Play Instrument driver. Some examples have already been created and mentioned in this Knowledge Base Article.
http://digital.ni.com/public.nsf/allkb/BC2CE741752EE09086256FFE00779D67?OpenDocument
Hope this helps.
Shazil M.
CLAD
Applications Engineer
National Instruments UK & Ireland

Unsupported cDAQ module

Similar Messages

Maybe you are looking for