NIMax NI cDAQ-9174 Simulation

Hi everyone
I am trying to simulate a NI cDAQ-9174 in NIMax.
I am right clickiing on devices and interfaces, creating a new simulation, selecting compactDAQ Chassisand choosing NI cDAQ-9174.
I get an error message that says "Create new failed. The required device information was not present on the target. Please update, install, or re-install the software associated with this device".
I assumed I didnt have the relevant driver installed so I went to the NI website and went to NI cDAQ-9174 Support, and under drivers it just has NI-DAQmx 14.5.1 listed, which I already have installed on my machine.
Any ideas why the new simulation device won't install?

Hi Dawud,
no problem with my MAX5.3.3 (with LabVIEW2011).
It seems you did not install the complete DAQmx driver with all needed parts…

Similar Messages

Memory Overflow cDAQ 9174

I running into an error (-200361) when I run my state diagram using a cDAQ 9174 chassis. I have a 9214 is slot 1, a 9237 in slot 2 and, 9207 in slot 4. I have tried a couple of workarounds to get this VI to work, but I have not yet been able to figure it out. I have a hard time believing this is hardware related and am thoroughly convinced it is because of the way I have wired this VI together. I have looked at all the links provided in all of the responses I could find to similar problems without resolution. What data is being written so fast that the processor is unable to keep up? See the attached VI.
Solved!
Go to Solution.

I made the above mentioned changes, cleaned up some unecessary/repeated functions and am now faced with lossy data. You can see in the attached picture, every few seconds or so the data reports zero. What is happening that is causing this?
Attachments:
LossyData.jpg ‏356 KB
ThermistorStateMachine.vi ‏129 KB

USB 9162 VS cDAQ 9174

Bonjour,
J'ai déjà crée deux autres post sur mon problème mais cette fois je m'attaque au produit lui même!!!
http://forums.ni.com/t5/Discussions-de-produit-de-NI/Probl%C3%A8me-DAQmx-buffer-convertion/td-p/1187...
http://forums.ni.com/t5/Discussions-de-produit-de-NI/cDAQ-rapidit%C3%A9/m-p/1184553#M35939
Mon application met 250 ms à faire un traitement du signal lorsqu'elle fonctionne avec le NI USB 9162, et lorsqu'elle fonctionne avec le cDAQ 9174, elle met 750ms!!! Avec exactement les mêmes paramètres d'acquisition, de traitement et d'affichage.
Vous voyez le problème??
D'où ma question: le transfert de données par le hi-speed USB 9162 est-il plus rapide que celui sur le cDAQ 9174??
Si c'est le cas, comment ça se fait? Et y a t-il un moyen d'overclocker le cDAQ?
Je souligne le problème, car si celui-ci s'avère exacte, l'utilité de mon matériel serait remis en cause et cela m'amènerait à revoir mon jugement sur NI !!!
Merci
Arnaud

En faite cela concerne simplement le temps d'acquisition, car j'ai essayé sans le traitement du signal et le problème est toujours le même.
En faite, au départ je suis parti d'un vi express!! Ensuite j'ai généré le code pour comprendre comment cela fonctionné et pour avoir accès au paramètres style sensibilité!!
En générant le code, un sous-vi se crée (voir mon autre post 1er lien) ou on retrouve tout les bloc DAQmx (créer,..., supprimer), et avec les différents essais je m'aperçois que c'est se vi qui est plus lent ou du moins c'est se qui se passe qui est plus lent en fonction du USB-9162 ou du cDAQ 9174!!!
D'ou la question sur la rapidité d'echange des données entre les deux USB!!!!

I2c Using cDAQ 9174

I am trying to communicate to an mpu6050 on a g-521 breakout board. I have a cDAQ 9174 with a 9205, 9211, and a 9401 c series modules. I am trying to talk to it using I2c protocol. I am just getting started here and havnt found much information on this. Can anybody give me somewhere to start?
Thank you

Defested wrote:
I am trying to communicate to an mpu6050 on a g-521 breakout board. I have a cDAQ 9174 with a 9205, 9211, and a 9401 c series modules. I am trying to talk to it using I2c protocol. I am just getting started here and havnt found much information on this. Can anybody give me somewhere to start?
NI 9401c can be used to implement the digital communication protocol (I2C in your case)
Here you should look at: SPI and I2C Driver API
I am not allergic to Kudos, in fact I love Kudos.
Make your LabVIEW experience more CONVENIENT.

How to create a trigger using 9211 modules with cDAQ-9174?

I am trying to create posttriggered acquisition with an analog trigger using 9211 modules that are reading 4 thermocouples. I would like the data aquisition to start once a temperature of 90 degrees C is reached. I am not sure what I should put for the source of my trigger in my VI. Are these modules capable of using triggers, and if so, how do I go about creating one? Attached is the VI, thanks.
Attachments:
Thermocouple.vi ‏151 KB

The 9211 doesn't have any analog triggering capabilities. You'll have to implement the trigger in SW (like this example).
Best Regards,
John Passiak

Slow Log Rate Needed using cDAQ-9174

All,
I am logging strain data for a thermal sweep we are doing on one of our products. The sweep occurs over a long period of time (48 hours) so I realistically want to log one signal per second. I tried using a continuous sample and then subsetting it, but I can't get it to 1 sample per minute which is where I want it to be. Does anyone have any suggestions on using the subset (or another method) to slow down the capturing of data for the log?
Thanks,
Adam

Nice, sounds like you've figured it out.
The 9235 does indeed have a minimum sample rate of 794 S/s when using the internal timebase.
For future knowledge, here's what I would do to simplify things a little:
Set your "Samples to Read" to match your "Sample Rate".
-Since we have a limitation of nothing less than 794 S/s just set them both to 1k for simplicity.
Create an Amplitudes and Levels step and select your strain channels as the "Export to DC Value"
-This is a step I use for almost every test, strain especially. It will take your raw Waveform signal and turn it into a Scalar signal. Honestly not sure whats going on behind the scenes here but there's some averaging it does between the samples to read and the sample rate. Basically it works out to be a smoothing filter which yields a much cleaner signal for your final output signal.
To determine your actual sample RATE when recording scalar signals, divide the samples to read into the sample rate.
In our case 1000 samples to read divided by 1000 Hz is 1 S/s. Try it, I think it'll be inline with what you're looking for. I just ran a test file to be sure and with the above settings I recorded for 10 seconds and got 10 data points in my data file.
I never save my data to log file either, I save to ASCII exclusively but the results should be the same whether you use the "Record" option or "Save to ASCII" step.
Hope that helps!

Why can't I see a simulated device in myDAQ assistant?

I have created a simulated device (cdaq 9174) in NI MAX.
I am using the DAQ assistant symbol in labview to create a voltage signal simulation.
When I get to the "select physical channels to add to the task" screen in the DAQ assistant, my simulated device is not showing up, even though I can see it in NI MAX.
Any trouble shooting suggestions?

Hi Dawud,
you should stick with your original thread instead of scattering the problem in different places…
Did you also simulate some modules in this cDAQ chassis?
Why don't you supply a MAX screenshot with your question?

Ran updates, LabVIEW & MAX will no longer recognize my cDAQ?

As stated, I ran updates yesterday through NI Update Service... it suggested SP1, and a couple of others. Ran them, and today my computer doesn't see my cDAQ (9174).
Running...
Win7 Pro 64bit
LabVIEW Professional Ver. 12.0.1f2 (32-bit)
MAX Ver. 5.4.0f0
Tried to run my VI I was working on day before... obviously, if it's not seeing the cDAQ then it can't get data... ran MAX and it still shows up on the list, but doesn't' register as being hooked up. I tried powering it down and back up, rebooted computer, restarted LabVIEW, unhooked the unit from the hub it's normally hooked to and retried everything above with it plugged directly into my laptop.... nada.
I'm at a bit of a loss here. Anyone have any suggestions? I'm going to take the laptop over to my other systems and see if it recognizes any of them.
Thanks!
Chad

Kyle,
Yes, I have taken the hub out of the equation. Correct, I have plugged this laptop into my other control pannels that are running cDAQ's and they are not recognized either.
Other computers question... I have two laptops that I use in lab, the one currently in question (call it laptop1) was working fine until I ran the suggested updates on it... SP1, and some others and that brings us to where we are now. My other laptop (laptop2) was working fine until I started running the suggested updates on it, and now it's doing the same thing.
FYI, I have a support ticket open with NI, (Ref#-7383377).... Leah, has had me uninstall the DAQmx drivers and install the newer drivers... still no recognition in MAX and now my computer doesn't chime when I plug in the unit directly.
Nor does the cDAQ show up in the device manager anywhere.
Tried something....
I have a spare cDAQ that hasn't been used yet.. I plugged it in and it seem to recognize it until I ran MAX and it doesn't show up in there either. It did chime when I plugged it in, and it told me it was installing drivers.... Seemed to work for a second, but now it's telling me that it's an "Unknown Device" under the Universal Serial Buss controllers.
Still no joy in the device manager with my original cDAQ. I plugged in the spare, it did it's thing... I unplugged it, and plugged the original back in, I got a chime, but no recognition... after that, no more chimes and doesn't show up in the Device Mngr at all.
Other ideas?
Thanks!
Chad

Triggering frequency measurement with 9402 and cDAQ

Hi all,
I'm trying to take a speed measurement off of a shaft using a hall effect sensor and a 9402 module in a 4 module cDAQ 9174 chassis. I've used the low frequency measurement example using DAQmx but if the shaft isn't spinning I get a timeout error.
Two questions, is there a way to use the Express VI's to accomplish this and how do I create a trigger to start the measurement?
-Ian

Why not clear the timeout and report 0 RPM. The timeout is 0 rmp but you dont want to wait forever and block program flow.
Paul Falkenstein
Coleman Technologies Inc.
CLA, CPI, AIA-Vision
Labview 4.0- 2013, RT, Vision, FPGA

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

MyDAQ recognized as USB flash firmware

When I look in my Device Manager, my myDAQ is recognized as USB flash firmware, and it is also not recognized in any LabView instruments as it says "No Supported Devices." I've tried updating the driver for the USB, and I've also tried stopping and restarting the NI Device Loader in Services. Neither have worked.
What should I do?
If you ask for information please tell me the steps on how to get it.
Thank You
Emily
Solved!
Go to Solution.

MAX Configuration Report
3/3/2014 5:00:35 PM
MAX Summary
My System
Data Neighborhood
Devices and Interfaces
Network Devices
NI cDAQ-9174 "cDAQ1"
Scales
Software
LabVIEW 2013
LabVIEW Run-Time 2011 SP1 f2
LabVIEW Run-Time 2012 SP1 f3
LabVIEW Run-Time 2013
LabWindows/CVI Run-Time 2010 SP1
Measurement & Automation Explorer 5.5
Measurement Studio for VS2010
DotNET
Common
Common (64-bit)
NI ELVISmx 4.5
NI I/O Trace 3.1.1
NI PXI Platform Services 3.2.3
NI System Configuration 5.5
NI-DAQmx ADE Support 9.8
NI-DAQmx Device Driver 9.8
NI-DAQmx MAX Configuration 9.8
NI-PAL 2.9.1
NI-USI 1.0.2
My System
Operating System
Windows 7 Professional Service Pack 1 (6.01.7601)
Processor
Intel(R) Core(TM) i5-2410M CPU @ 2.30GHz / Intel64 Family 6 Model 42 Stepping 7 / GenuineIntel / 2294 MHz
Memory
5.91 GB of RAM
Disk Space
C:\ 390 GB of 679 GB free
Back to top
NI cDAQ-9174 "cDAQ1"
Property
Value
ProductType
cDAQ-9174
DevSerialNum
0x190B806
DevNotPresent
1
Back to top
Software
Name
Version
Description
Path
CVI Run-Time
10.0.1.434
The LabWindows/CVI Run-Time Engine is necessary to run executables or use DLLs you create with LabWindows/CVI, and it must be present on any target computer on which you want to run your executable program.
C:\Windows\SysWOW64\CVIRTE.DLL
NI-DAQmx Device Driver
9.8.0f0
NI-DAQmx Device Driver
C:\Program Files (x86)\National Instruments\NI-DAQ
NI-DAQmx ADE Support
9.8.0
NI-DAQmx Application Development Environment Support
C:\Program Files (x86)\National Instruments\NI-DAQ
NI-DAQmx MAX Configuration
9.8.0
NI-DAQmx MAX Configuration Support
C:\Program Files (x86)\National Instruments\NI-DAQ
NI I/O Trace
3.1.1f0
Monitors National Instruments API calls
C:\Program Files (x86)\National Instruments\NI IO Trace\NI IO Trace.exe
LabVIEW
13.0.0
Graphical Programming for Measurement & Instrumentation
C:\Program Files (x86)\National Instruments\LabVIEW 2013\labview.exe
LabVIEW Run-Time 2011 SP1 f2
11.0.1
LabVIEW Run-Time Engine
C:\Program Files (x86)\National Instruments\Shared\LabVIEW Run-Time\2011
Measurement & Automation Explorer
5.5.0f0
Use Measurement & Automation Explorer to manage your National Instruments products and services
C:\Program Files (x86)\National Instruments\MAX\nimax.exe
Measurement Studio
Visual Studio 2010 Support - See individual versions below.
National Instruments Measurement Studio Tools for Visual Studio 2010
DotNET
DotNET Software
Common
13.0.40.190
Facilitates the exchange of data between the acquisition, analysis, and user interface portions of an application.
C:\Program Files (x86)\National Instruments\MeasurementStudioVS2010\DotNET\Assemblies\Current\NationalInstruments.Common.dll
Common (64-bit)
13.0.40.190
Facilitates the exchange of data between the acquisition, analysis, and user interface portions of an application.
C:\Program Files (x86)\National Instruments\MeasurementStudioVS2010\DotNET\Assemblies\Current\NationalInstruments.Common.dll
NI-USI
1.0.2
NI Universal Storage Interface
C:\Program Files (x86)\National Instruments\Shared\USI
NI ELVISmx
4.5.0f2
NI ELVISmx
C:\Program Files (x86)\National Instruments\NI ELVISmx
NI PXI Platform Services
3.2.3
Support for NI PXI and PXIe Controllers and Chassis
C:\Program Files (x86)\National Instruments\PXI
NI-PAL Software
2.9.1
NI-PAL Library for Windows
C:\Windows\SysWOW64
NI System Configuration
5.5.0f0
Discover and configure systems and devices
C:\Windows\SysWOW64\nisyscfg.dll
LabVIEW Run-Time 2012 SP1 f3
12.0.1
LabVIEW Run-Time Engine
C:\Program Files (x86)\National Instruments\Shared\LabVIEW Run-Time\2012
LabVIEW Run-Time 2013
13.0.0
LabVIEW Run-Time Engine
C:\Program Files (x86)\National Instruments\Shared\LabVIEW Run-Time\2013

Frequency counter unreliable using rotary vane anemometer

I have set up an anemometer to measure air flow speed, with the signal being acquired by a 9402 module in a cDAQ-9174 chassis (4 slot). I am using Signal Express 2011 to program the instrument.
I have set up a frequency counter task, using a maximum frequency of 1.8 kHz a minimum frequency of 250 mHz, rising edge and 1-counter (low frequency). The output is scaled using y = 0.0111x + 0. This gives 20 m/s when the frequency is 1.8 kHz.
The readings given by Signal Express give a very noisy signal, at a frequency much higher than the bandwidth of the anemometer. The range is in the order of 20% of the mean. I have attached a PDF of the signal, for two different air flow sources, the seproj file and the tdms file for one of the runs. I have also observed that the counter output is rounded to the nearest multiple of 10, e.g. 490, 470, 480, 480, 470, etc.
Is this consistent with a digital bounce issue? Is this consistent with an earthing issue? Is this consistent with a sample rate issue? Any other ideas for investigating this issue?
thanks
Attachments:
EXPT 20 - ANEMOMETER NOISE.pdf ‏49 KB
EXPT 20 Anemometer Noise.seproj ‏637 KB

I have logged the voltage signal coming from the anemometer, using our 9239, a report of a few cycles is attached as a PDF. The graph clearly shows a small digital bounce. The noise is small compared to the signal, is there any way it can be filtered when acquired by the 9402?
Other tests that I ran showed a background noise in the order of 50 microVolts and a frequency of 50 Hz, this is very likely a background noise from a power supply (we run at 50 Hz in Aus) but is many orders of magnitude smaller than the signal, I assume it would be ignoredby the 9402.
Attachments:
EXPT 20 Anemometer Noise Voltage.seproj ‏261 KB
EXPT 20 Anemometer Noise Voltage.pdf ‏19 KB

Counter stuck at zero

Hi,
I'm using LabVIEW 2014 on Windows 64 bit to acquire displacement data from a digital encoder as follows: Renishaw linear encoder --> NI 9411 digital in --> cDAQ-9174 --> Windows machine.
I have a VI that records the displacement at 5000 Hz. It's been working fine for weeks but suddenly, the displacement value (i.e. the count) stays stuck at zero no matter how much displacement there is.
Displacement data is also being used in a SoftMotion feedback loop. That is working fine. I am even using SoftMotion commands to create a displacement history, which looks right (this displacement history is limited to low frequency activation by the nature of SoftMotion so I created this second way of measuring displacement to get to high frequency). Point being, I'm confident the linear encoder is working fine.
I am extremely puzzled because I haven't changed anything of substance that I can think of. I did switch the cDAQ9174 to a different USB cable os I started with the hypothesis that I had screwed up connectivity somewhere in hardware. The cDAQ 9174 and the NI 9411 both pass Self Test in NI MAX. I checked continuity of the relevant cable pin by pin and it is fine. Then I started trying to get more insight into the value of the counter. I have a number of versions of this VI and they all report that the counter is flatline at zero no matter how much displacement there is in the system. I ran the VI in highlight execution mode to look for clues and I spotted something that seems slightly odd, at least to me. The counter is identified as cDAQ1/_ctr*. Does anyone know what that means?
Attached are screenshots of the VI with and without highlight execution turned on in case anyone sees anything in there that I'm missing.
Thanks,
John

Hey John,
I didn't see anything strange in your screenshots. The cDAQ1/_ctr* just means that there are more characters following "_ctr", but by default highlight execution only includes 11 characters. You can see the same behavior in a few of your other constants.
When you changed USB cables, did you change any of the inputs to the 9411? Is everything still configured to match the Connections for Counters and 9411 specifications?

Using counter and output at the same time

Hi all,
I'm using a NI 9401 high speed digital IO module (with a cDAQ 9174 chassis) that has 8 digital IO channels, to perform two tasks at once in Labview. I can get both of them to work independantly, but when I put them together to run simultaniousy in parallel, it does not work. My two tasks are simple: 1. Generate a continious pulse train square wave output using one of the counters linked to one of the output channels (PFI7) and 2. Output a 'high' (5V) with one of the other channels (PFI1) when a certain logic condition is met.
When I run my code (attached), the pulse train output works, but the output on the other channel doesn't work when the logic condition is met. I should note that the logic condition is that when RMS current exceeds 3A, I want to output a 'true'. I am measuring current using another analog input card connected to the same chassis and this part is all working well. I think the problem is that there is some sort of interference between the pulse train output which is linked to PFI7 and the other output which is PFI1.
I know there is a limitation with the 9401 card that if the channels are in two groups, 0-3 and 4-7, and you must use a whole group as either all inputs or all outputs, but I don't think this should affect me, as I am using both my channels as outputs anyway, plus I am using channels 1 and 7 anyway.
If anybody has any ideas as to what could be wrong with my code, I would greatly appreciate it.
Attachments:
DSDBI Vegetation testing program.vi ‏115 KB

OK, you've shot yourself in the foot.
It is a very bad idea to modify the shipping examples. Like testing bungee cords by juming off a cliff- sometimes you only get to try it once.
Now why on earth did you not add the DI code following the example's method of wiring the error chain and closing the task after the loop? You have duplicated code in both cases of your case structure the only difference.........(wait for it..........) There is a true constant in the true case where the false case contains a false constant. A wait for task complete is unnecessary for a 1 sample DI task- really the write just completes and the task stops all by itself. the only needed thing here is a DI Write 1 Ch 1 Sample no case structure, and wire the compare output to data to write.
You should probably add a control task vi with a "Reserve" input prior to each start task on the CO and AI Tasks and after the Create Task on the DO. Its a bit technical but the result is like taking vitamins- you'll just get better performance.
Jeff

Can I measure period with USB 6501?

Hi,
I was told that I can use the one counter in the NI USB 6501 to measure period. So, I wrote this little VI, modeled after the VI I have that measures encoder period using the counters built into the NI cDAQ 9174 with the NI 9401 digital I/O module. I have my encoder wires GND and 5VDC on terminals 1 and 2, respectively. Also, I have encoder channel A and Channel B wires connected to terminals 9 (P2.7) and 24 (P0.7) respectively. With the MAX, I can count edges with this wiring. The purpose of this VI is to display an average value of 25 period measurements of the encoder. The encoder (120 cpt) is turning at about 2-5 rev/second, so, not that fast, maybe a total of 500 period per second; should be easy for this counter. I'm just spinning it with my finger, so, not that fast.
Please advise how to use the USB 6501. I can't find any wiring instructions, other than the pinout, but, the pinout doesn't tell you which channel is the counter gate on the USB 6501, so, I found a response on MAX at channel 24.
When I run this, the array is correctly initialized to 0.5, but, then I get this error, 200431. I found some things on the forum that suggest I cannot measure period, that I can only count edges. Should I throw this 6501 away?
Thanks,
Dave
Attachments:
USB 6501 error.docx ‏24 KB
USB 6501 period measurement.vi ‏26 KB

The 9178 also only has 4 counters.
Do the 5 period measurements actually have to take place at the same time? Sometimes it might make sense to cycle through the channels to reduce the number of counters used (you wouldn't have to rewire connections or anything as the input terminals are software-defined). Switching from channel to channel in software should take on the order of ms depending on which hardware you end up using.
The 9171+(9401/9402) is a relatively cheap way to add additional counters to a system as the 9171 chassis has 4 counters just like the 9174 and 9178.
Best Regards,
John Passiak

NIMax NI cDAQ-9174 Simulation

Similar Messages

Maybe you are looking for