注册登陆后可查看附件和大图，以及购买相关内容
您需要 登录 才可以下载或查看，没有账号？注册会员
x
Windows系统下（Linux和MAC系统下请自行了解清楚）NI的各种软件、模块、工具包、驱动程序，使用NI许可证管理器来激活的，绝大部分的都可以使用NI Lincense Activator来激活：NI序列号Serial Number生成激活工具NI License Activator，LabVIEW/VBAI/VDM/VAS等软件模块工具包破解工具不限版本http://visionbbs.com/thread-490-1-1.html
视觉论坛的各种NI资源，除了视觉相关的模块有使用外，大部分的都不会使用，仅提供资源不提供技术支持。资源的下载地址一般会同时提供NI官方和百度网盘的地址。某些工具包NI地址失效或没有NI地址，只能使用百度网盘地址；如果百度网盘地址失效过期，可联系论坛客服更新。NI的服务器在美国，有时候速度很慢或下载容易出错，这样会造成安装时各种错误而无法安装。建议在下载完成后，对下载资源做校验和(NI一般会提供MD5或SHA256等)验证，与官方或视觉论坛提供的校验和对比，一致就可以安装；如不一致，则需要重新下载。视觉论坛早期下载上传的资源，基本上都是正常下载的资源；2019后下载的资源，都与NI的正确校验和对比过，保证是正确的资源才上传到百度网盘。校验和工具下载地址：文件Hash计算器FHash，文件校验和验证下载文件正确性验证，MD5值计算、SHA1值计算、SHA256值计算、CRC32值计算http://visionbbs.com/thread-26524-1-1.html
NI-DAQmx Base 14.0 Download MAC32/64Eng NI-DAQmx基本版14.0苹果系统版下载
NI-DAQmx基本版
NI-DAQmx基本版为数据采集系统提供一部分NI-DAQmx功能，适用于Mac OS、Linux和Windows操作系统。
NI-DAQmx基本版是一个驱动软件，具有NI-DAQmx的部分功能。它与LabVIEW集成，提供现成即用的LabVIEW VI和C函数示例，这类似于完整版NI-DAQmx软件。NI-DAQmx基本版是为在Mac操作系统上进行LabVIEW开发而设计的，但也可以安装在Windows和Linux机器上，因此相同的代码可在三个操作系统上运行。
14.0
MD5: 3af7802e7ddcd65380103e015ae86d99（官方正确）
SHA1: a7ab4ceb00dec675109aaec7407b225d2574e6c4
SHA256: 6c9415e6903e443c92fcded8766ed91f25a20b519bdf798ecd0ea55dd4c69418
CRC32: 989b3b64
NIDAQmx-Base-MAC14.0.0.txt
(288 Bytes, 下载次数: 0, 售价: 10 元)
README for NI-DAQmx Base 14.0.0 05-Nov-2014
Copyright 2004-2014 National Instruments Corporation. All Rights Reserved.For patents covering National Instruments products, refer to the patents.txtfile on the root directory of your CD (if applicable) and/or ni.com/patents.CVI(TM), LabVIEW(TM), Measurement Studio(TM), National Instruments(TM), NI(TM),ni.com(TM), NI-DAQ(TM), and SCXI(TM) are trademarks of National InstrumentsCorporation. Linux(r) is the registered trademark of Linus Torvalds in the U.S.and other countries. Product and company names mentioned herein are trademarksor trade names of their respective companies.
This file contains late breaking news about NI-DAQmx Base and supersedesany information found in other documentation included in the distribution.Refer to ni.com/mac for the most recent information about National InstrumentsMac OS X support.
SUPPORTED FUNCTIONALITY M Series MIO (USB-621x/PCI/PCIe/PXI/PXIe only) *NOTE* NI 623x Isolated M Seriesare not supported by NI-DAQmx Base. *Analog Input -DMA (PCI/PCIe/PXI/PXIe only) -Digital start triggering -Digital reference triggering(PCI/PCIe/PXI/PXIe only) -Analog start and referencetriggering (PCI/PCIe/PXI/PXIe only) -External clocking -Multi-channel, multi-sampleread (scaled) -Multi-channel, multi-sampleread (raw) (PCI/PCIe/PXI/PXIe only) -Multi-channel, single sampleread (scaled) *Analog Output -Digital start triggering -External clocking -Multi-channel, multi-samplewrite (scaled) -Multi-channel, single-samplewrite (scaled) *Counter Input -Simple event counting -Buffered event counting(continuous speed is limited by computer speed; reading a single largebuffer does not cause an error) -Period measurement -Buffered period measurement(USB-621x only) -Pulse width measurement -Buffered pulse widthmeasurement (USB-621x only) *Counter Output -Single pulse -Continuous pulse train -Digital start triggering *Digital I/O -Port input -Line input -Port output -Line output -Correlated DIO(PCI/PCIe/PXI/PXIe only) -speed is limited toabout 100 kHz (system dependent) because DMA is notsupported for DIO NI 6508/PCI-DIO-96 (PCI/PXI only) *Supported in NI-DAQmx Base TaskConfiguration Utility *Port Input *Port Output E Series MIO (PCI/PXI only) *Supported in NI-DAQmx Base TaskConfiguration Utility *Analog Input -DMA -Digital start and referencetriggering -Analog start and referencetriggering -External clocking -Multi-channel, multi-sampleread (scaled) -Multi-channel, multi-sampleread (raw) -Multi-channel, single sampleread (scaled) *Analog Output -External clocking -Multi-channel, multi-samplewrite (scaled) -Multi-channel, single-samplewrite (scaled) *Counter Input -Simple event counting -Buffered event counting(continuous speed is limited by computer speed; reading a single largebuffer does not cause an error) -Period measurement -Pulse width measurement *Counter Output -Single pulse -Continuous pulse train -Digital start triggering *Digital I/O (Port0 only) -Port input -Port output B Series MIO (PCI/PXI only) *Supported in NI-DAQmx Base TaskConfiguration Utility (NI 6013/6014 only) *Analog Input -DMA -Digital start and referencetriggering -Analog start and referencetriggering -External clocking -Multi-channel, multi-sampleread (scaled) -Multi-channel, multi-sampleread (raw) -Multi-channel, single sampleread (scaled) *Analog Output -External clocking -Multi-channel, multi-samplewrite (scaled) -Multi-channel, single-samplewrite (scaled) *Counter Input -Simple event counting -Buffered event counting(continuous speed is limited by computer speed; reading a single largebuffer does not cause an error) -Period measurement -Pulse width measurement *Counter Output -Single pulse -Continuous pulse train -Digital start triggering *Digital I/O (Port0 only) -Port input -Port output NI 671x/673x (PCI/PXI only) *Supported in NI-DAQmx Base TaskConfiguration Utility *Analog Output -External clocking -Multi-channel, multi-samplewrite (scaled) -Multi-channel, single-samplewrite (scaled) *Counter Input -Simple event counting -Buffered event counting(continuous speed is limited by computer speed; reading a single largebuffer does not cause an error) -Period measurement -Pulse width measurement *Counter Output -Single pulse -Continuous pulse train -Digital start triggering *Digital I/O (Port0 only) -Port input -Port output NI USB-9211A *Supported in NI-DAQmx Base TaskConfiguration Utility *Analog Input -Multi-channel, multi-sampleread (scaled) -Multi-channel, single sampleread (scaled) NI USB-9215A *Supported in NI-DAQmx Base TaskConfiguration Utility *Analog Input -Multi-channel, multi-sampleread (scaled) -Multi-channel, single sampleread (scaled) NI USB-9233 *Analog Input -Multi-channel, multi-sampleread (scaled) NI USB-9234 *Analog Input -Multi-channel, multi-sampleread (scaled) -Software selectable AC couplingand IEPE excitation per channel NI USB-6008/9, USB-6008/9 OEM *Supported in NI-DAQmx Base TaskConfiguration Utility *Analog Input -Digital start triggering -Multi-channel, multi-sampleread (scaled) -Multi-channel, single sampleread (scaled) *Analog Output -Multi-channel, multi-samplewrite (scaled) -Multi-channel, single-samplewrite (scaled) *Counter Input -Simple event counting (fallingedge only) *Digital I/O -Line input -Port input -Port output -Line output NI USB-6501, USB-6501 OEM *Supported in NI-DAQmx Base TaskConfiguration Utility *Counter Input -Simple event counting (fallingedge only) *Digital I/O -Line input -Port input -Port output -Line output NI S Series *Analog Input -DMA -Digital start and referencetriggering -Analog start and referencetriggering -External clocking -Multi-channel, multi-sampleread (scaled) -Multi-channel, multi-sampleread (raw) -Multi-channel, single sampleread (scaled)
Check the installed documentation for a list of supported functions andparameters.
SUPPORTED PCI/PCIe/PXI/PXIe DEVICES (Refer to SUPPORTED FUNCTIONALITYfor device-specific details)
OPERATING SYSTEM SUPPORT NI-DAQmx Base 14.0.0 supports: openSUSE Linux 12.3 and 13.1, Red Hat Enterprise Linux WS 6 (x86/x86_64), Scientific Linux 6.x, and Mac OS X v10.8.x (x86_64) - v10.9.x (x86_64).
NOTE: For information about NI-DAQmx Base for Linux, refer to ni.com/infoand enter BaseGSGML.
SYSTEM REQUIREMENTS (Minimum System) Mac OS X v10.8.x - v10.9.x Disk Space: * Minimum Install/HardwareSupport: 297 MB * Additional C Interface Support:20 MB * Additional LabVIEW Support foreach version installed: 45 MB
INSTALLER NOTES Install your hardware first before installing the driver software. To install NI-DAQmx Base, run NI-DAQmx_Base_14.0.0.pkg.
The installer installs the following: 1. NI-VISA. 2. All needed shared object files and documentation for supportedPCI/PCIe/PXI/PXIe hardware. 3. Shared tools for device detection and configuration. 4. LabVIEW 2011 (SP1), 2012(SP1), 2013 (SP1), and 2014 support and/or C APIfunctionality. 5. USB device support.
To uninstall NI-DAQmx Base, refer to /Applications/NationalInstruments/NI-DAQmx Base/Uninstall.txt
DEVICE CONFIGURATION Any time a new device is added or removed, run the following: /Applications/National Instruments/NI-DAQmx Base/lsdaq.app
Make note of the device name (Dev1 for example) as this is the name youneed to specify when creating channels in your program. A device name maychange each time a device is added or removed.
EXAMPLES This release includes examples for each measurement type that demonstratesappropriate functionality. Examples for LabVIEW are located in /examples/daqmxbase.They are not included in the NI Example Finder. C examples are installed by default to /Applications/NationalInstruments/NI-DAQmx Base/examples. The make files take care of linking to thenecessary libraries. Be sure to run the device configuration utility (lsdaq)before running the examples to determine the correct device name. To compile andrun an AI example in Terminal: $ cd /Applications/National Instruments/NI-DAQmx Base/examples/ai $ make $ ./acquireNScans
DOCUMENTATION Documentation located in ‘/Applications/National Instruments/NI-DAQmxBase/documentation’ includes the DAQmx Base C Function Reference, the hardwarereferences and supporting PDFs. LabVIEW help files are accessible from the LabVIEW Help menu.
KNOWN ISSUES
LabVIEW API:
Using DAQmxBase CreateTask, DAQmxBase Create Virtual Channel, andDAQmxBase Clear Task in a loop leaks approximately 110 bytes per iteration. Ifyou pass in a string for the taskName parameter in DAQmxBase Create Task, thememory leak does not occur.
DAQmxBase Is Task Done does not currently support analog input.
Some parameters that aren’t available in the LabVIEW API interface can beaccessed through the NI-DAQmx Base Task Configuration Utility (triggerhysteresis, convert clock rate, etc.). The utility can be launched from theTools menu and allows you to statically configure tasks. To use static tasks,call DAQmxBase Create Task with the ‘task to copy’ input with the name of yourstatic task. You can modify the static task with configuration functions orjust call Start, Read/Write, Stop afterwards. Refer to the SUPPORTEDFUNCTIONALITY section for the devices the utility supports.
If, when building an executable or shared object project using NI-DAQmxBase VIs, the Application Builder catches an error, you must restart LabVIEWbefore running any NI-DAQmx Base VI.
C API:
Using DAQmxBaseCreateTask, a DAQmxBaseCreateXXChannel function, andDAQmxBaseClearTask in a loop leaks approximately 110 bytes per iteration. Ifyou pass in a string for the taskName parameter in DAQmxBaseCreateTask, thememory leak does not occur.
DAQmxBaseIsTaskDone currently does not support analog input.
Some parameters that aren’t available in the C API interface can beaccessed through the NI-DAQmx Base Task Configuration Utility (triggerhysteresis, convert clock rate, etc.). The utility is named mxbaseconfig andallows you to statically configure tasks. To use static tasks, callDAQmxBaseLoadTask instead of DAQmxBaseCreateTask. You can then modify thestatic task with configuration functions or just call Start, Read/Write, Stopafterwards. Refer to the SUPPORTED FUNCTIONALITY section for the devices theutility supports.
All APIs: NI-DAQmx Base does not support power management. Your system should not beset to hibernate or sleep while hardware supported by NI-DAQmx Base is presentin the system.
Aborting a USB task before the DAQmx Base Stop Task.vi is called may causethe USB device to become unresponsive. As a result, subsequent attempts tocommunicate with the USB device may fail. To resolve this, if the LED is nolonger blinking on the USB device, unplug and re-plug in the USB device toreset the firmware. Additionally, you may need to run lsdaq and/or close andre-open LabVIEW in order to reset the software.
NI-DAQmx Base uses polynomial scaling (voltage to temperature) forthermocouple measurements, but the temperature range that the software supportsis not consistent with the minimum accurate range of the inverse polynomialcoefficients used for several thermocouple types. For more information aboutthis, visit ni.com/info and enter “rditml”.
M Series finite pulse train generation is allowed by the NI-DAQmx Base APIbut does not behave as expected. In finite pulse train mode the selectedcounter only generates a single pulse regardless of the number of pulsesrequested. Single pulse and continuous pulse generations behave as expected.
NI-DAQmx Base is not multi-thread safe. In LabVIEW, use the error clusterto force execution order. In C, use only one thread to make API calls;especially for task/channel creation and deletion.
NI-DAQmx Base is designed to complete one process/task per boardfunctionality at a time. You can have one task that does DIO and another taskthat does AI on the same board at the same time. You cannot, however, run twoAI tasks on the same board at the same time.
Currently, only the factory calibration constants are loaded and used.Self-calibration and the use of self-calibration constants are not supported.
For E Series and NI 67xx boards, only Port0 of DIO is currently supported.
There are three ways to configure tasks in NI-DAQmx Base. The firstmethod, which is preferred, involves dynamically creating the task using CreateTask followed by Create Virtual Channel. The second and third methods both usethe NI-DAQmx Base Configuration Utility; the difference between the second andthird method is how the utility is launched and used. Refer to the SUPPORTEDFUNCTIONALITY section for the devices the utility supports. To use the second method, launch the utility from the Tools menu in LabVIEW.Launching the utility from the Tools menu in LabVIEW includes any other tasksthat may be in memory in LabVIEW at the time the utility is launched. Anychanges made with the LabVIEW launched utility immediately takes effect inLabVIEW and on any C program launched after the utility is exited. The third method involves running ‘mxbaseconfig’ from/Applications/National Instruments/NI-DAQmx Base to launch the utility. The‘mxbaseconfig’ utility is a separate application with the same features as the LabVIEWlaunched utility, but is designed for use with the C API and also as a tool forLabVIEW built executables. The ‘mxbaseconfig’ utility saves its data to thesame configuration file as the LabVIEW launched version, but changes made withthis version are only be seen in LabVIEW if LabVIEW is restarted.
If your machine entersHibernate/Sleep, restart your C or LabVIEW-built application, or LabVIEW toproperly communicate with your DAQ device.
When doing Analog Triggering for M Series, use either APFI 0 or APFI 1 asthe trigger source, otherwise you will get an error.
When setting a DMA buffer size, set it >= 8K. This setting is requiredby Apple according to QA1197.
Hardware: USB-621x Supported Devices NI-DAQmx Base 14.0.0 supports the USB-6210, USB-6211, USB-6211 OEM,USB-6212, USB-6212 OEM, USB-6212 BNC, USB-6212 Mass Termination, USB-6215,USB-6216, USB-6216 OEM, USB-6216 BNC, USB-6216 Mass Termination,USB-6218,USB-6218 OEM, and USB-6218 BNC devices.
USB-621x Supported Functionality NI-DAQmx Base 14.0.0 does NOT support reference trigger capabilities onthe USB-621x devices.
USB-9211A Sample Process When performing a thermocouple task, the USB-9211A automatically readsboth the Cold-Junction and Autozero channels and uses these values when calculatingthe temperature every time the scan list is sampled. Both reads count towardsthe overall sample rate. Thus the effective maximum sample rate forthermocouple tasks is 12/(N+2) S/sec where N equals the number of channelsbeing read. For example, if three channels are being read by a thermocoupletask, the maximum sample rate is then 12/(3 + 2) = 2.4 S/sec. Higher samplerates might be obtained by reading the desired thermocouple channel as avoltage channel in an Analog Input task. However, as an Analog Input task, theresulting units are volts, and temperature calculation is not performed by thedriver. The Cold-Junction Compensation sensor can be read by using physicalchannel 4 as a voltage channel. The Autozero channel is not available as aphysical channel.
USB-9211A and USB-9215A Channel Voltage Range The USB-9211A and USB-9215A devices do not provide a user-configurablechannel range. The following lists the supported channel ranges per device: USB-9211A ±80 mV USB-9215A ±10 V
USB-92xx LED Might Blink Sporadically The USB-92xx LED might not blink at a steady rate when acquiring data.Sporadic blinking is normal and does not affect data acquisition.
SUPPORT We’d like your feedback and bug reports about this release. To provide feedback,visit http://www.ni.com/ask
CHANGES FROM PREVIOUS VERSIONS +3.7.0 --> 14.0.0 *Added LabVIEW 2014 support *Removed LabVIEW 2010 (SP1)support *Added 64-bit application supportfor Mac OS X +3.6.0 --> 3.7.0 *Added LabVIEW 2013 support *Removed LabVIEW 2009 (SP1)support +3.5.0 --> 3.6.0 *Added LabVIEW 2012 support *Removed LabVIEW 8.6(.1) support *Added Thunderbolt adapter support +3.4.5 --> 3.5.0 *Added 64-bit kernel support forMac OS X v10.6 and v10.7 +3.4.0 --> 3.4.5 *Added LabVIEW 2011 suppport *Removed LabVIEW 8.5(.1) support +3.3.0 --> 3.4.0 *Added LabVIEW 2010 support *Removed LabVIEW 8.2(.1) support +3.2.0 --> 3.3.0 *Added LabVIEW 2009 support *Added support for the USB-6212and USB-6216 devices +3.1.0 --> 3.2.0 *Added LabVIEW 8.6 support *Added support for the USB-9234 *Added support for USB-621x OEMdevices *Added DAQmxBase Properties *Removed LabVIEW 8.0 support +2.1.0 --> 3.1.0 * Added LabVIEW 8.5(.1) support * Added support for USB-621x and USB-9233 devices +2.0.0 --> 2.1.0 * Added Universal Binary support. * Added LabVIEW 8.2 support. * Removed LabVIEW 7.0 and LabVIEW7.1 support. +1.5.0 --> 2.0.0 * Added PCIe M Series support. * Added LabVIEW 8.0 support. * LabVIEW 8.0 Run-time Engine isnow used for the C API and utility apps. * Added DAQmxBase Export Signal.viand DAQmxBase Wait for Next Sample Clock.vi to the LabVIEWAPI. +1.4.0 --> 1.5.0 * Added M Series support. +1.3.1b3 --> 1.4.0 * Added NI USB-6008/9 support. * Added NI USB-6501 support. +1.2b3 --> 1.3.1b3 * Added support for the 671x and673x boards. * Added NI USB-9215 support. * Added NI USB-9211 support. * Added beta support for S Seriesboards (AI functionality only).
BUG FIXES The following items are the IDsand titles of a subset of issues fixed between NI-DAQmx Base 3.7 and NI-DAQmxBase 14.0. If you have a Bug ID, you can search this list to validate that theissue has been fixed. This is not an exhaustive list of issues fixed in thecurrent version of NI-DAQmx Base. 451968 - Channel swapping onPCI/PCIe devices when restarting a task without stopping
The following items are the IDsand titles of a subset of issues fixed between NI-DAQmx Base 3.6 and NI-DAQmxBase 3.7. 125793 - Boards that use DMA foranalog input can now sample at full clock rates. 188602 - The Analog Input SamplesAvailable property now correctly works for USB-600x and USB-92xx devices. 337737 - NIDAQmxBase.h is nowinstalled in the compiler search path. 364104 - NI-DAQmx Base periodmeasurement now uses the user specified timeout. 373093 - The C API no longer hangsin Cocoa application exit. 386569 - The NI USB 6216 ScrewTerminal device is now detected correctly. 410911 - DAQmx Base utilities nolonger require SSE2 CPU registers. 411727 - Thunderbolt devices nowcorrectly work with IOMMU enabled Macs.
The following items are the IDsand titles of a subset of issues fixed in NI-DAQmx Base 3.6: 235582 - Windows Vista displayswrong text when recognizing a USB-621x device. 328636 - A hang can occur whenusing the C Interface on RHEL 6 or Scientific Linux 6. 334612 - It is possible to reach asystem state where all C applications and some DAQmx Base utilities crash onstart. 334728 - Unplugging the USB cablewhile using USB-9211A results in a LabVIEW hang on Linux. 347613 - Running the TouchPanelAcq One Sample example on a TPC-2012 and a USB-621x results in applicationhang. 353357 - Warnings occur whenbuilding C Interface examples on Mac OS X. 354377 - NMI could happen whilerunning DAQmxBase Reset Device.vi in parallel with a DIO read.
The following items are the IDsand titles of a subset of issues fixed in NI-DAQmx Base 3.5: 235032 - Added other missingfunctions in DAQmx Base C Function Reference Help. * DAQmxBaseGetChanAttribute * DAQmxBaseSetChanAttribute * DAQmxBaseReadBinaryI32 * DAQmxBaseGetReadAttribute * DAQmxBaseGetWriteAttribute * DAQmxBaseSetWriteAttribute 300522 - Some utility applicationshave incorrect version information. 326109 - DAQmxBaseGetDevSerialNumfunction not outlined in the C Function Reference Help. 328204 - LSDAQ did not notifyusers if devices with incompatible firmware were detected on Linux.
The following items are the IDsand titles of a subset of issues fixed in NI-DAQmx Base 3.4.5: No visible bug fixes were includedin this release.
The following items are the IDsand titles of a subset of issues fixed in NI-DAQmx Base 3.4: 188602 - Add 'Query AvailableSamples' property VI for AI
The following items are the IDsand titles of a subset of issues fixed in NI-DAQmx Base 3.3: 125846 - E Series DMA scale -significant performance degradation 123445 - USB-621x conversionperiod is hard-coded 125417 - Add USB-6212, USB-6216support to NI-DAQmx Base 36396 - Error reporting C examplesneeds improvement 146347 - List supportedPCI/PCIe/PXI/PXIe devices in Linux and Mac OSX readme(s) 101240 - Add Get/Set Property VIsto LabVIEW menus
The following items are the IDsand titles of a subset of issues fixed in NI-DAQmx Base 3.2: 104182 - USB-600x AO ranges arenot checked due to mismatched data types on PDA 54779 - DC offset on 6009 AIacquisition using NI-DAQmx Base 3.1 54565 - NI-DAQmx Base LinuxUNINSTALL script gives error if cancelled 44358 - AO non-regeneration notsupported in NI-DAQmx Base C interface 43821 - Error -200220 when runningdynamic task on PDA with E Series 37409 - TPC-2012 does not workwith NI-DAQmx Base
The following items are the IDsand titles of a subset of issues fixed in NI-DAQmx Base 3.1: 46IDK0IG - DAQmx Base 2.1 VIsBroken in French Mac OSX 467A4400 - LabVIEW prints too manymessages 45GE1B00 - DAQmx Base Drivers notable to be weakly linked 4EUERLIQ - NIDAQmxBase.h:incorrect declaration of DAQmxBaseReadBinaryI32 470HO4HR - USB-9211 Does not poweron when Mandriva Linux computer boots (cold start) 42A94B4W - Add quadrature encoder support to NI-DAQmx Base
ERROR & WARNING CODES These errors and warnings represent the NI-DAQmx Base supported subset ofthe Windows version of NI-DAQmx.
223700 Internal software warning.
-223700 Internal software error.
-200983 You only can get the specified property while the task is reserved,committed or while the task is running. Reserve, commit or start the task priorto getting the property.
-200797 An empty string was specified as a terminal name which is not supported.Specify a valid terminal name.
-200745 Frequency and Initial Delay property values are inconsistent with one ormore counter timebase properties. The conflicting properties must satisfy the following constraints: Counter Timebase Rate / Counter Maximum Count <= Frequency <=Counter Timebase Rate / 4 Counter Timebase Rate / Counter Maximum Count <= 1 / Initial Delay<= Counter Timebase Rate / 2 If the Counter Timebase Rate is not specified, it is inferred from theCounter Timebase Source selection.
-200608 Acquisition cannot be started, because the selected buffer size is toosmall. Increase the buffer size.
-200565 Specified digital channel contains more bits than supported by the8-bit version of DAQmxBase Port Write. Use the version of DAQmxBase Port Writethat supports wider digital ports.
-200564 Specified digital channel contains more bits than supported by the32-bit version of DAQmxBase Port Read.
-200561 Attempted writing analog data that is too large or too small.
-200559 Task cannot contain a channel with the specified channel type, because thetask already contains channels with a different channel type. Create one taskfor each channel type.
-200558 One task cannot contain multiple independent devices. Create one task foreach independent device.
-200552 Specified string is not valid, because it contains an invalid character.
-200536 Specified value is smaller than the minimum value supported for thisproperty.
-200527 Requested values of the Minimum and Maximum properties for the counterchannel are not supported for the given type of device. The values that can bespecified for Minimum and Maximum depend on the counter timebase rate.
-200526 Write cannot be performed because this version of DAQmxBase Write does notmatch the type of channels in the task. Use the version of DAQmxBase Write that corresponds to the channel type.
-200525 Read cannot be performed because this version of DAQmxBase Read does notmatch the type of channels in the task. Use the version of DAQmxBase Read that corresponds to the channel type.
-200524 Write cannot be performed, because the data does not contain data for allchannels in the task. When writing, supply data for all channels in the task.Alternatively, modify the task to contain the same number of channels as thedata written.
-200523 Read cannot be performed because this version of DAQmxBase Read onlyreturns data from a single channel, and there are multiple channels in thetask. Use the multichannel version of DAQmxBase Read.
-200498 Syntax for a range of objects in the input string is invalid. For ranges of objects, specify a number immediately before and after everycolon (":") in the input string. Or, if a name is specified after thecolon, it must be identical to the name specified immediately before the colon.Colons are not allowed within the names of the individual objects.
-200489 Specified channel cannot be added to the task, because a channel with thesame name is already in the task.
-200485 The specified task cannot be loaded, because it is not a valid task.
-200478 Specified operation cannot be performed when there are no channels in thetask.
-200474 Specified operation did not complete, because the specified timeoutexpired.
-200473 Read cannot be performed when the Auto Start property is false and thetask is not running or committed.
-200459 Write failed, because there are no output channels in this task to whichdata can be written.
-200452 Specified property is not supported by the device or is not applicable tothe task.
-200430 I/O type of the physical channel does not match the I/O type required forthe virtual channel you are creating.
-200428 Value passed to the Task/Channels In control is invalid. The value must refer to a valid task or valid virtual channels.
-200361 Onboard device memory overflow. Because of system and/or bus-bandwidthlimitations, the driver could not read data from the device fast enough to keepup with the device throughput. Reduce the sample rate, or reduce the number ofprograms your computer is executing concurrently.
-200341 Generation was configured to use only onboard memory, but thecorresponding buffer is larger than onboard memory. Buffer size is providedimplicitly when data is written or explicitly when the buffer is configured.
-200330 An attempt has been made to use the PFI0 terminal of the device for bothan analog and digital source. Use a terminal other than PFI0 as the source of your digital signal.
-200326 An attempt has been made to perform a route when the source and thedestination are the same terminal. In many cases, such as when configuring anexternal clock or a counter source, you must select a PFI, PXI Trigger, or RTSIline as the source terminal. -200287 Attempted to write to an invalid combination of position and offset. Theposition and offset specified a sample prior to the first sample generated(sample 0). Make sure any negative write offset specified selects a validsample when combined with the write position.
-200284 Some or all of the samples requested have not yet been acquired. To wait for the samples to become available use a longer read timeout orread later in your program. To make the samples available sooner, increase thesample rate. If your task uses a start trigger, make sure that your starttrigger is configured correctly. It is also possible that you configured thetask for external timing, and no clock was supplied. If this is the case,supply an external clock.
-200278 Attempted to read a sample beyond the final sample acquired. Theacquisition has stopped, therefore the sample specified by the combination ofposition and offset will never be available. Specify a position and offset which selects a sample up to, but notbeyond, the final sample acquired. The final sample acquired can be determinedby querying the total samples acquired after an acquisition has stopped.
-200265 An attempt has been made to use an invalid analog trigger source. If you explicitly named the virtual channel using DAQmxBase CreateChannel, you must use the name assigned to that channel.
-200261 An attempt has been made to use an analog trigger in multiple situationswith differing properties. Change the analog trigger properties so they are the same, or do not usean analog trigger for all situations.
-200254 Terminal for the device is invalid.
-200220 Device identifier is invalid.
-200214 Analog trigger circuitry unavailable on the device. Select a non-analog trigger type, or use a device with analog triggeringhardware.
-200170 Physical channel specified does not exist on this device. Refer to the documentation for channels available on this device.
-200099 Physical channel not specified.
-200096 Number of samples to read must be -1 or greater.
-200089 Task name specified conflicts with an existing task name.
-200082 Minimum is greater than or equal to the maximum.
-200077 Requested value is not a supported value for this property.
-200040 Source terminal to be routed could not be found on the device. Make sure the terminal name is valid for the specified device. Refer tohelp for valid terminal names.
-200012 Specified physical channel does not support digital output.
-89136 Specified route cannot be satisfied, because the hardware does not supportit.
-89131 An attempt has been made to perform a route when the source and thedestination are the same terminal. In many cases, such as when configuring anexternal clock or a counter source, you must select a PFI, PXI Trigger, or RTSIline as the source terminal. -89120 Source terminal to be routed could not be found on the device. Make surethe terminal name is valid for the specified device.
-50256 USB Device error: Feature not supported.
MHDDK ERROR & WARNING CODES 15 Resource Not Found - The application cannot get access to the hardware.Occurs if the DAQ device is not installed on the PDA or the reference to thehardware is invalid. For an invalid reference, restart LabVIEW. | 
发表于 2020-10-31 22:37:15
