Dear sir /mamm
I have connected the Ni-9184 chassis with 3 modules of 9403 & 1 module of 9201& provided the internet. Installeds driver provided by your CD but still in Ni- max only 9184 is showing but other modules are not being connected. Please help in resolving the issue. As well as i request you to provide telephonic support to us.
I have multiple USB-6210 DAQ devices. I am using Visual Studio to create a GUI for data capturing. Only one DAQ is connected to the PC at one time.
When the DAQ device is first connected to a computer it is given a default name. For example, the first one connected will be Dev1 and the next one will be Dev2. I want each of the devices to perform the same way when using my VS program. To do this, I need to figure out how to get the name of the connected device (or a list of connected devices) to tell it to look for that device's PFI0 port for example. I don't want to have to change the program for each device or look elsewhere for it like in the device manager. I want the program to recognize that there is a connected device and know what its name is.
Help very appreciated.
Hello,
I am working on project to design Synchronizer for my PIV system on LabView. What I have to do is: to generate two synchronized signal one to trigger laser(signal 1) and other for camera(signal 2). The signals will have some time delay between them and signal 1 will go on independently. I have made labview code for this (attached). I have used case structure(signal 2 generator inside this) within while loop to do this. Signal 1 is generated, for while loop iteration divisible by two the case structure condition becomes true and generating signal 2, wait time for loop is 500ms . This gives time delay between two signal as one second (we can control time delay by controlling divisor factor used to for while loop iteration)
The problem is I am unable to write these two signals to my NI USB6212.
Please Help!!
Code is attached.
Thanks in advance..
I have a Compact DAQ (cDAQ-9189) with eight NI-9237 modules. This is connected directly to a computer via ethernet cable (i.e. local link mode). I can see the cDAQ as well as the modules in NI MAX, and the self test works fine. I can also ping the device via commandline window. However, when I try to use the DAQ Assistant, it says no supported devices found.
Is there some step that I am missing to get LabView to see the cDAQ?
we have pci-6221 Multifunction DAQ card
using labview2011 NI-DAQmx-14.5, win7 32bit
in Measurement& Automation Explorer we see this pic
小弟把实验室的数据采集卡拔插了以后，开机就检测不到数据采集卡了，型号是PCI6259，然后看设备管理器里面有个未知设备PCI，我就重新加载驱动，选择了PCI6259设备，然后在MAX里面看到PCI6259，接着自检成功，自校准一直失败，没辙了，求大佬帮忙啊，自校准一直失败，没法用啊。
这问题再不解决小弟就要爆炸了，这几天做实验着急，早知道不动那个采集卡了。
Hello all,
I have a PXI-6229 DAQ card, and want to use the digital and analog outputs to modulate a laser. I am considering purchasing the laser but want to make sure the card can drive it. The laser has both digital and analog modulation. The digital modulation has a 200 Ohm input impedance and requires a TTL signal. The analog modulation can be configured in two ways: either with a 50 Ohm input impedance requiring 0-1V, or with a 1.2 kOhm input impedance requiring 0-5V.
Can anyone help me determine if the DAQ card could drive these loads? It seems like both output channels can provide enough current, but the concern I have is that the 50 kOhm pull-down resistor on the digital channel (according the 6229 manual) would draw all the current, instead of it going to the load. This is also a concern for the analog output channel, but I don't see any mention of a pull-down resistor in the manual.
Any insight you can provide is much appreciated!
I'm pretty new to DAQmx and I'm trying to configure a driver session for a PCI-6023E. In the driver setup, how do I determine what the driver setup string is and what the resource descriptor string is?
I would like to identify hardware and LabVIEW code to implement a continuous Digital-to-Analog conversion that occurs on a trigger. It's a continuous process, so I cannot pause to re-load the buffer at any time.
I'm machining a grid pattern line-by-line, each analogue value is clocked-out of the DAC when an in-position trigger is received from a motion system.
To make the problem slightly more tricky, the motion system occasionally produces an extra unwanted pulse at the end of a Scan Line. To compensate for this, each line is zero padded at the end (zero equates to no mark on the workpiece).
e.g. DAC values might be:
Line0: 8 2 2 4 4 4 2 2 8 0 (9 pulses received, zero goes unused)
Line1: 7 3 3 5 5 5 3 3 7 0 (10 pulses received, the extra unwanted pulse clocks out a zero)
Line2: 9 1 1 2 2 4 1 1 9 0 (9 pulses received, zero goes unused)
LabVIEW can interrogate the motion system to find out when each line has completed, or a separate digital trigger pulse could be created to signal the end of a Scan Line. End-of-line signal could trigger a flipper over to a second buffer, or in the case of a circular buffer, the end-of-line signal could move a pointer to the start of the next line. e.g. Line0 end-of-line signal could move the memory location pointer from "8" to "7". Line1 end-of-line signal could move the memory location pointer from "0" to "9".
The whole time the system is running, we can write more data to the buffer and the process will continue indefinitely. The actual line length may be up to 16,000 points.
At present I have a PCIe-6341 with a buffer of 8192 elements. I re-load the complete buffer by pausing the process at the end of the Scan Line, it's way too slow and I'm limited to 8192 elements per line.
Hi
I just purchased LabVIEW Home Bundle. I am trying to figure out how to make the Home Bundle acquire measurements from a NI USB 6001. I am building a small test stand for our rocket club to test motors on. We got the local maker space to build the stand and someone suggested the Home Bundle and let us use the 6001.
There appears to be no drivers for any USB DAQ boards. Can anyone advise me how to interface the software with the hardware. All the previous versions of LabVIEW I've been shown have a DAQ Assist to set up the interface. I've also seen even earlier versions have ways to call USB devices. They appear to be absent from Home Bundle.
Any advice would be appreciated.
Rick
熱電対およびNI9211、NI cDAQ9172 で温度計測を行いたいと考えています。
Windows7がインストールされたPCにLabview8.2.1およびSignal Express 2.0をインストールしてK熱電対・NI9211およびNI cDAQ9172をPCに接続したところ、NI9172は検出はできましたがNI9211が見つからず、NI MAXやSignal Expressで物理チャンネル指定を行おうとしても”対応するデバイスが見つかりません”と表示されます。
NI9211の動作にはLabviewおよびデバイスドライバのインストールディスクに含まれているもの以外にもドライバ等が必要なのでしょうか。
ご回答お待ちしております。
熱電対およびNI9211、NI cDAQ9172 で温度計測を行いたいと考えています。
Windows7がインストールされたPCにLabview8.2.1およびSignal Express 2.0をインストールしてK熱電対・NI9211およびNI cDAQ9172をPCに接続したところ、NI9172は検出はできましたがNI9211が見つからず、NI MAXやSignal Expressで物理チャンネル指定を行おうとしても”対応するデバイスが見つかりません”と表示されます。
NI9211の動作にはLabviewおよびデバイスドライバのインストールディスクに含まれているもの以外にもドライバ等が必要なのでしょうか。
ご回答お待ちしております。
追記）
インストールメディアにデフォルトで付属していたMAX4.2およびDAQmx8.5を使用しています。またcDAQ9172はデバイスマネージャ内でNIのデータ収集デバイスとして認識されていることを確認しましたが、MAXのツリーには表示されておりません。
My computer version is windows10 (64 bits), and I install labview2018 64 bits, NI MAX 18.0.
I want to know the file directory of nicaiu.dll which nidaqmx-python uses. (Because I want to know which dll I used in my code, lib64 version or lib32 version. )
Maybe in C:\Program Files (x86)\National Instruments\Shared\ExternalCompilerSupport\C\lib64\msvc or C:\Program Files (x86)\National Instruments\Shared\ExternalCompilerSupport\C\lib32\msvc or D:\Program Files (x86)\National Instruments\Shared\ExternalCompilerSupport\C\lib64\msvc ?
So how can I get it?
print(sys.version)
returns:
3.6.9 |Anaconda, Inc.| (default, Jul 30 2019, 14:00:49) [MSC v.1915 64 bit (AMD64)]
Hi,
I'm trying to understand why several BNC-2110 boxes look different from one another, and what internal differences (if any) exist for those boards.
The attached photo shows the front panels of the two boxes, with their serial & model numbers below. The red rectangles in each photo highlight the differences that are important to me right now. Please explain the internal differences between these products, and how I can access the CTR0 output signal using the 2110 on the left, which lists PFI12 /P2.4 instead of CTR0 on its front panel.
Thanks, in advance, for your help,
Bruce
Hi,
I have tried searching this online but I only found a recommended solution for Windows base OS and not for Linux. Is anyone know how can I check the functionality on my newly installed Ni-DAQmx board to my Linux PC?
thanks,
Dexter
Why isn't the cDAQ 9191 signal strength LED light on?
cDAQ-9189 ETHERNET Chassis is configured with a static IP 192.168.1.10 , sub net 255.255.255.0 and default gateway 192.168.1.1 and host PC is configured with IP 192.168.1.5, sub net 255.255.255.0 ,default gateway 192.168.1.1.
Chassis is detected in MAX and is reserved to the host PC. All the modules are detected and self test is passed. Laptop OS is windows 10 , DAQ MX 17.6, Labview 2017 is used for the development. I am running the code since last 3 months from the development laptop and have not faced any issues in communication with the chassis. After the application was built the same was tested from the development laptop.
Now i have a brand new windows 10 updated , 8 GB ,1 TB laptop which i want to use at customer place to which the application is installed and since then i have trouble with communication losses to the chassis.
I ran ping test in command window alongside with application running, to look for any losses and found that the error is "General failure" and this lasts for couple of seconds and again the ping test is back to OK. This causes the acquisition loops to throw error and crash the application.
I tried the same ping test after installing the full Labview development platform and DAQMX 17.6, to this laptop and run the code itself but the issue is not solved. If i switch to the other lenovo laptop, everything works fine and good and i never saw this behavior. This is happening in a random fashion . Some times the application will run smoothly for 1 hr and more and sometimes will not last for more than 10 minutes. I don''t see any memory build up or processor build up.
We have updated the firmware in chassis as well.
The screen shot was taken when IP was set to 169.254.175.48.
There is only one laptop communicating to this chassis .
Any ideas or updates are welcome .
Thank you.
Hi,
For ~2 years I have been using a K-type thermocouple with a USB-6002 to log temperatures from a hotplate in a basic labview program.
About 2 weeks ago the temperature measurement started showing a few random negative numbers (see attached graph).
The problem has steadily got worse, and I'd say now every 1 in 5 measurements gives a negative number. All other measurements seem fine, giving a stable correct temperature.
I have tried a new thermocouple, I have tried a different USB-6002, and I have tried using different AI ports, but I still have the problem.
I have made no changes to my labview program, but my tests so far seem to point to a software related problem.
I'm using labview 17.0 (64-bit).
Thanks for any help,
Graham
I am working with a USB-6356. All the channel except one seem fine. On channel ai3, if I short AI3+ and AI3- to AIGND I will see a large DC offset (~9V).
If I drive that channel using one of the analog outputs, connecting AO0 to AI3+ and AOGND to AI3- I can see my signal (100mV singe wave), but it rides at 9V.
If I connect to any other channel in the same way it works fine (a sine wave around 0V)
I am using a PCI-6229 card . This is my default multifunction card for many projects.
Was just reading the User Manual for a specific topic clarity and was wondering what is the difference between the three grounds as presented by the card. AI GND / AO GND / D GND
While which to use for what is obvious there also is a mention in the user manual which says that all these three are connected on the board.
I always have signal conditioners connected to all my I/Os and so the loading on the pins is well below even the normal rating ... like DO pins are not loaded beyond 2mA at any time. This being the case what will happen if I refer an Analog Channel with DGND instead of AI GND ?
Just curious.