Error -63001 NI-RIO FPGA Communications Occurs With DMA Transfers From Host to FPGA
I am trying to do a DMA transfer from the 900x cRIO RT controller to the cRIO FPGA. The FPGA code compiles. However, when I run the code I get a Real-Time error saying the following: Error -63001: NI-RIO FPGA Communications.Framework: (Hex
URL: http://digital.ni.com/public.nsf/allkb/257AF49E2110630F8625741F0062D292
|
Error 50150 - Reboot USB 9162 after upgrading to DAQmx 8.7
Immediately following an upgrade to DAQmx 8.7 and using a USB-9162, a user may see error 50150 when attempting to use the device until they restart Measurement and Automation Explorer (MAX) or reboot. The Found New Hardware Wizard may also prompt you to reboot. USB-9162 devices should not
URL: http://digital.ni.com/public.nsf/allkb/D046874B01378D42862574170072561E
|
How Do I Acquire Data from More than One CompactDAQ Module in LabVIEW SignalExpress?
I need to acquire data from multiple modules in my cDAQ-9172 chassis using LabVIEW SignalExpress. How do I do accomplish this?
URL: http://digital.ni.com/public.nsf/allkb/7F890A8413C0544A862573F4006D4E63
|
Can I use FPGA Emulation Mode in a PXI System with a R Series Expansion Chassis for cRIO?
I have a cRIO Expansion Chassis NI-9151 connected to an R-Series PXI-7833R card. I am trying to use the "Use Target Hardware for I/O" option to emulate I/O of the modules on the cRIO expansion chassis, but instead of the actual signals, I seem to be getting random data back. Isn't this
URL: http://digital.ni.com/public.nsf/allkb/76240748163E2D33862573EF003ADB98
|
Moving CompactRIO VIs with Uncalibrated Data to FPGA Targets with Calibrated Data
In versions of NI-RIO prior to 2.4, C Series Modules only return binary (uncalibrated) data, which requires the host VI to apply calibration coefficients and convert the data to engineering units in software. After installing NI-RIO 2.4 or later, the default behavior for AI/AO modules is to
URL: http://digital.ni.com/public.nsf/allkb/254BBC14267D2972862573E000824912
|
为什么我的USB数据采集模块出现“Unable to Loacate a Driver”错误？
我刚刚购买了一个USB数据采集模块（9211或9215），并在Windows系统的计算机上安装了NI-DAQmx。当我插入我的USB模块时，我得到一个错误：“Windows was unable to locate a driver for this device.”该如何出来？
URL: http://digital.ni.com/public.nsf/allkb/01F862902AA81CE6482573A200098B96
|
NI 9237真实的激励电压与指定电压值不同
在用NI 9237创建Strain或者Custom Voltage with Excitation的DAQmx任务时，在任务中指定的激励电压与我在Ex+和Ex-两端之间测到的电压不一致。例如，在创建任务时，我指定的激励电压为6V。然而，我在Ex+和Ex
URL: http://digital.ni.com/public.nsf/allkb/3F7E5F74EE6458AB4825736F00208909
|
Channel Names Cause Incorrect Analog Output on NI USB DAQ Devices
When generating a voltage on the analog output of my USB devices (such as the USB-6008/9, cDAQ 9263) I notice that if the channels in my task have a numeric value at the end of the channel name, then I generate incorrect values. Why is this and how can I fix it?
URL: http://digital.ni.com/public.nsf/allkb/061D00FB903F2F6586257361006C5505
|
Unexpected Delay When Using DAQmx Analog Start Trigger
When I use a DAQmx analog edge start trigger with an M Series DAQ device, my program appears to last 250-300ms longer than when I do not use an analog edge start trigger. Why is this happening, and is there anything that I can do to get around it?
URL: http://digital.ni.com/public.nsf/allkb/AF8AA09A3323B0B38625734F00496E02
|
Why do I see Spurious Returns when using multiple Wait on IRQ Nodes on VxWorks Real Time Targets?
NI-RIO 2.3 with LabVIEW 8.5 supports multiple Wait on IRQ nodes in a single VI, however, I see spurious returns from the "Wait on IRQ" Method Node when using cRIO-901x Controllers. This does not occur on my cRIO-900x Controllers or any other Pharlap based Real-Time controller. Why does this
URL: http://digital.ni.com/public.nsf/allkb/A868BA261986A486482573380077794D
|
