Category(s) Selected [start over]

KnowledgeBase [see results below]. To refine your results, select another category.

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

使用DAQmx模拟触发的意外延迟 当我使用M系列DAQ设备的模拟边沿开始触发(DAQmx驱动)时，程序运行比不使用触发要长250-300毫秒。为什么会有这样的现象，是否有什么方法可以解决这个问题？ URL: http://digital.ni.com/public.nsf/allkb/5A341AF57090C4E6862574A0003F2D5A

Why Do I See Spurious Returns When Using Multiple Wait on IRQ Nodes on VxWorks Real Time Targets? The NI-RIO 2.3 driver with LabVIEW 8.5 supports multiple Wait on IRQ nodes in a single VI. Unfortunately, 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. URL: http://digital.ni.com/public.nsf/allkb/A868BA261986A486482573380077794D

当我在VxWorks Real Time Targets环境下使用多个Wait on IRQ节点时，为何会得到假的返回值？ NI-RIO 2.3搭配LabVIEW 8.5的使用可以支持在单一VI中使用多个Wait on IRQ节点。然而，当我使用CRIO-901x控制器时，会从"Wait on IRQ" 节点得到假的返回值。这个现象并不会发生在cRIO-9000x或其他Pharlap的Real-Time控制器。这个问题为何发生呢？ URL: http://digital.ni.com/public.nsf/allkb/4F849B6417C2C27E862574DB00348222

當我在VxWorks Real Time Targets環境下使用多個Wait on IRQ節點時，為何會得到假的回傳值？ NI-RIO 2.3搭配LabVIEW 8.5的使用可以支援在單一VI中使用多個Wait on IRQ節點。然而，當我使用CRIO-901x控制器時，會從"Wait on IRQ" 節點得到假的回傳值。這個現象並不會發生在cRIO-9000x或其他Pharlap的Real-Time控制器。這個問題發生的緣由為何呢？ URL: http://digital.ni.com/public.nsf/allkb/95BC4E473B7C6313862573AD00070404