石鑫华视觉
Windows系统下（Linux和MAC系统下请自行了解清楚）NI的各种软件、模块、工具包、驱动程序，使用NI许可证管理器来激活的，绝大部分的都可以使用NI Lincense Activator来激活，以下链接可下载：
NI序列号Serial Number生成激活工具NI License Activator，LabVIEW/VBAI/VDM/VAS等软件模块工具包破解工具不限版本
http://pcmv.cn/thread-490-1-1.html
视觉论坛的各种资源，除了视觉相关的模块有使用外，大部分的都不会使用，所以仅提供资源不能提供技术支持。资源的下载地址一般会同时提供NI官方地址和百度网盘的下载地址。某些工具包NI的地址失效或没有NI的下载地址，那视觉论坛也没有办法，只能尝试使用百度网盘地址下载；如果百度网盘的下载地址失效过期，可联系论坛客服更新。现在NI的下载服务器对我国IP地址不是很友好，有些时候速度很慢或大的资源下载很容易出错，这样会造成安装过程各种类型报错而无法安装。建议在下载完成后，对下载资源做校验和验证（NI一般会提供MD5或SHA256等），与官方或视觉论坛提供的校验和对比，一致就可以安装，如果不一致，则需要重新下载。视觉论坛早期下载的资源，那时候NI没有这么多限制，基本上都是正常下载的资源；后期下载的资源，都与NI的正确校验和对比过，保证是正确的资源才上传到百度网盘，所以百度网盘的资源基本上是正确的。校验和工具下载地址：
文件Hash计算器FHash,文件校验和验证下载文件正确性验证，MD5值计算、SHA1值计算、SHA256值计算、CRC32值计算
http://pcmv.cn/thread-26524-1-1.html
NI-DAQmx Base 15.0 Download Windows32/64Eng NI-DAQmx基本版15.0Windows系统版下载
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机器上，因此相同的代码可在三个操作系统上运行。
Windows
15.0
MD5: 3c628c2a27a27952792b9e6c3ed00651（官方正确）
SHA1: e9cf5e444fc1a99463d2ec79a04bb64ab02ca8be
SHA256: 557f17fd8c1e4dbcd8bbd98b82dc46c7ea52af13d502032057509bb45ae9b949
CRC32: 7cb14c72
NI-DAQmx Base 15.0 Download Windows32/64Eng NI-DAQmx基本版15.0Windows系统版下载
http://pcmv.cn/thread-25300-1-1.html?fromuid=9
(出处: 视觉论坛VISIONBBS|视觉之家VISIONHOME)
NI-DAQmx Base 15.0.0 Readme
Windows XP SP3, Windows 8/7/Vista x86, and Windows 8/7/Vista x64 (LabVIEW and ANSI C API support)
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 / USB-6218 BNC
USB-9211A
USB-9215A
USB-9233
USB-9234
USB-6008/9 / USB-6008/9 OEM
USB-6501 / USB-6501 OEM
Choosing Which API to Use
Support in NI-DAQmx Base 15.0.0
Device Support
Fixed Issues
Known Issues
Error Codes
Choosing Which API to Use
NI-DAQmx
You are using Windows 8/7/Vista/XP. NI-DAQmx is the recommended driver software package for these operating systems.
You are using a device supported by NI-DAQmx and a development environment supported by NI-DAQmx. Refer to the NI-DAQmx Readme for up-to-date information on supported development environments.
NI-DAQmx Base 15.0.0
You are using an operating system not supported by NI-DAQmx, such as Mac OS X.
NI-DAQmx Base 14.0
You are using an operating system not supported by NI-DAQmx, such as Mac OS X.
NI-DAQmx Base 3.6
You are using an operating system not supported by NI-DAQmx, such as Mac OS X.
You are developing a DAQ application for a Windows Mobile device with LabVIEW 2012 Touch Panel Module with Windows CE 4.2.
NI-DAQmx Base 3.4.5
You are using an operating system not supported by NI-DAQmx, such as Mac OS X.
You are developing a DAQ application for a Windows Mobile device with LabVIEW 2011 Mobile or Touch Panel Module with Windows Mobile 5.0 or Windows CE 4.2.
NI-DAQmx Base 3.4
You are using an operating system not supported by NI-DAQmx, such as Mac OS X.
You are using a device which is only supported by NI-DAQmx Base 3.4.
You are developing a DAQ application for a Windows Mobile device with LabVIEW 2010 Mobile or Touch Panel Module with Windows Mobile 5.0 or Windows CE 4.2.
NI-DAQmx Base 3.3
You are using an operating system not supported by NI-DAQmx, such as Mac OS X.
You are using a device which is only supported by NI-DAQmx Base 3.3.
You are developing a DAQ application for a Windows Mobile device with LabVIEW 2009 Mobile or Touch Panel Module with Windows Mobile 5.0 or Windows CE 4.2.
NI-DAQmx Base 3.2
You are using an operating system not supported by NI-DAQmx, such as Mac OS X.
You are using a device which is only supported by NI-DAQmx Base 3.2.
You are developing a DAQ application for a Windows Mobile device with LabVIEW 8.6 Mobile or Touch Panel Module.
NI-DAQmx Base 3.1
You are using an operating system not supported by NI-DAQmx, such as Mac OS X.
You are using a device which is only supported by NI-DAQmx Base 3.1.
You are developing a DAQ application for a Windows Mobile device with LabVIEW 8.5.1 PDA Module or Touch Panel Module.
NI-DAQmx Base 2.2
You are using an operating system not supported by NI-DAQmx, such as Mac OS X or Linux.
You are using a device which is only supported by NI-DAQmx Base 2.2.
You are developing a DAQ application for a Windows Mobile device with LabVIEW 8.2.1 PDA Module.
NI-DAQmx Base 2.1
You are developing a DAQ application for a Windows Mobile device with LabVIEW 8.2 PDA Module.
You are developing a DAQ application for Ardence RTX with the LabVIEW 8.2 Real-Time Module for RTX and M Series or NI 671x/673x devices.
NI-DAQmx Base 2.0
You are developing a DAQ application for a Windows Mobile device with LabVIEW 8.0 PDA Module.
You are developing a DAQ application for Ardence RTX with the LabVIEW 8.0 Real-Time Module for RTX and M Series or NI 671x/673x devices.
NI-DAQmx Base 1.5.1 for RTX
You are developing a DAQ application for Ardence RTX with the LabVIEW 7.1 Real-Time Module for RTX and M Series or NI 671x/673x devices.
NI-DAQmx Base 1.0.x
You are developing a DAQ application for PocketPC 2003 with LabVIEW 7.1 PDA, E Series devices, or NI CF-6004.
Support in NI-DAQmx Base 15.0.0Application Software and Programming Language Support
| NI Application Software | Versions Supported by NI-DAQmx Base 15.0.0 |
| LabVIEW | 2012, 2012 SP1, 2013, 2013 SP1, 2014, 2014 SP1, 2015 |
| Programming Language | Versions Supported by NI-DAQmx Base 15.0.0 |
| ANSI C | Windows Desktop only |
Device Support
| Devices | Description |
| NI USB-6008 | 12-bit, 10 kS/s, 8 AI channel, 12 DIO line, 1 event counter device |
| NI USB-6008 OEM | 12-bit, 10 kS/s, 8 AI channel, 12 DIO line, 1 event counter device |
| NI USB-6009 | 14-bit, 48 kS/s, 8 AI channel, 12 DIO line, 1 event counter device |
| NI USB-6009 OEM | 14-bit, 48 kS/s, 8 AI channel, 12 DIO line, 1 event counter device |
| NI USB-6501 | 24 DIO line, 1 event counter device |
| NI USB-6501 OEM | 24 DIO line, 1 event counter device |
| NI USB-6210 | 16-Bit, 250 kS/s, 16 AI channels, 4 DI, 4 DO, 2 counters |
| NI USB-6211 | 16-Bit, 250 kS/s, 16 AI channels, 2 AO, 4 DI, 4 DO, 2 counters |
| NI USB-6211 OEM | 16-Bit, 250 kS/s, 16 AI channels, 2 AO, 4 DI, 4 DO, 2 counters |
| NI USB-6212 | 16-Bit, 400 kS/s, 16 AI channels, 2 AO, 32 DIO, 2 counters |
| NI USB-6212 OEM | 16-Bit, 400 kS/s, 16 AI channels, 2 AO, 32 DIO, 2 counters |
| NI USB-6212 BNC | 16-Bit, 400 kS/s, 16 AI channels, 2 AO, 32 DIO, 2 counters |
| NI USB-6212 Mass Termination | 16-Bit, 400 kS/s, 16 AI channels, 2 AO, 24 DIO, 2 counters |
| NI USB-6215 | 16-Bit, 250 kS/s, 16 AI channels, 4 DI, 4 DO, 2 counters, isolated |
| NI USB-6216 | 16-Bit, 400 kS/s, 16 AI channels, 2 AO, 32 DIO, 2 counters |
| NI USB-6216 OEM | 16-Bit, 400 kS/s, 16 AI channels, 2 AO, 32 DIO, 2 counters |
| NI USB-6216 BNC | 16-Bit, 400 kS/s, 16 AI channels, 2 AO, 32 DIO, 2 counters |
| NI USB-6216 Mass Termination | 16-Bit, 400 kS/s, 16 AI channels, 2 AO, 24 DIO, 2 counters |
| NI USB-6218 | 16-Bit, 250 kS/s, 32 AI channels, 2 AO, 8 DI, 8 DO, 2 counters, isolated |
| NI USB-6218 OEM | 16-Bit, 250 kS/s, 32 AI channels, 2 AO, 8 DI, 8 DO, 2 counters, isolated |
| NI USB-6218 BNC | 16-Bit, 250 kS/s, 32 AI channels, 2 AO, 8 DI, 8 DO, 2 counters, isolated |
| NI USB-6218 OEM | 16-Bit, 250 kS/s, 32 AI channels, 2 AO, 8 DI, 8 DO, 2 counters, isolated |
| NI USB-9211A | 4 AI Channels, 24-bit thermocouple input module |
| NI USB-9215A | 4 AI Channels, ±10 VDC, 16-bit simultaneous sampling analog input module |
| NI USB-9215A BNC | 4 AI Channels, ±10 VDC, 16-bit simultaneous sampling analog input module |
| NI USB-9233 | 4 AI Channels, ±5 VAC, 24-bit simultaneous sampling DSA module with IEPE |
| NI USB-9234 | 4 AI Channels, ±5 VAC/VDC, 24-bit simultaneous sampling DSA module with IEPE |
Operating System Requirements
Windows
| Minimum Processor | RAM | Operating System |
| Pentium III/800 MHz or equivalent | 256 MB | Windows XP |
| Pentium IV 1 GHz or equivalent | 1 GB | Windows 8/7/Vista x86/x64 |
Fixed Issues
| CAR ID | Summary |
| 414157 | USB sleeves should not show up in the firmware update utility. |
| 496047 | NI-DAQmx Base leaves top level directory behind on uninstallation. |
NI-DAQmx Base 15.0.0 Known Issues
USB Support
Miscellaneous
USB Support on the Desktop
NI-DAQmx Base Compatibility with NI-DAQmx
You must have version 8.7.2 of NI-DAQmx installed to use NI-DAQmx Base 15.0.0 with an NI USB DAQ device on Windows. Any other version of NI-DAQmx automatically downloads incompatible firmware that NI-DAQmx Base 15.0.0 does not support.
NI-DAQmx Base does NOT support digital reference triggering on the USB-621x devices
Aborting a USB task may cause the USB device to become unresponsive
Aborting a USB task before the DAQmx Base Stop Task.vi is called may cause the USB device to become unresponsive. As a result, subsequent attempts to communicate with the USB device may fail. To resolve this, if the LED is no longer blinking on the USB device, unplug and re-plug in the USB device to reset the firmware. Additionally, you may need to run lsdaq and/or close and re-open LabVIEW in order to reset the software.
Launching the NI-DAQmx Base Configuration Tool While a Task is Running
Do not launch the NI-DAQmx Base Configuration Utility while an acquisition task is in progress as this might cause the running task to hang.
Using Multiple USB Devices
You can use multiple USB devices concurrently, providing that they are accessed from within the same process.
Hotplug USB Support
If a USB device is added or removed, you must update the device list either by selecting Refresh Device in the NI-DAQmx Base Configuration Utility or by launching (or re-launching) LabVIEW prior to using the device. Note that updating the device list might change the device order (such as, "Dev1" becomes "Dev2").
USB-9211A Sample Process
When performing a thermocouple task, the USB-9211A automatically reads both the Cold-Junction and Autozero channels and uses these values when calculating the temperature every time the scan list is sampled. Both reads count towards the overall sample rate. Thus the effective maximum sample rate for thermocouple tasks is 12/(N+2) S/sec where N equals the number of channels being read. For example, if three channels are being read by a thermocouple task, the maximum sample rate is then 12/(3 + 2) = 2.4 S/sec. Higher sample rates might be obtained by reading the desired thermocouple channel as a voltage channel in an Analog Input task. However, as an Analog Input task, the resulting units are volts, and temperature calculation is not performed by the driver.
The Cold-Junction Compensation sensor can be read by using physical channel 4 as a voltage channel. The Autozero channel is not available as a physical channel.
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.
USB Devices Might Not Be Available After Hibernation
After resuming from hibernation, USB devices might not register in NI-DAQmx Base. Physically re-inserting the USB devices or refreshing the Windows Device Manager allows NI-DAQmx Base to detect the USB devices again.
USB-9211A and USB-9215A Channel Voltage Range
The USB-9211A and USB-9215A devices do not provide a user-configurable channel range. The following table lists the supported channel ranges per device:
| Device | Supported Channel Range |
| USB-9211A | ±80 mV |
| USB-9215A | ±10 V |
Building C Examples with Visual Studio .NET
To build DAQmx Base examples in Visual Studio.NET, complete the following steps:
Launch Start»Program Files»Microsoft Visual Studio .Net 2003»Visual Studio .Net Tools»Visual Studio .NET 2003 Command Prompt.
Type ">cd C:Program Filesundefinedational InstrumentsundefinedI-DAQmx BaseExamples".
Select the example type: ai, ao, ctr, or dio.
Type ">nmake examplename.mak".
Miscellaneous
NI-DAQmx Base does not support power management. Your system should not be set to hibernate or sleep while hardware supported by NI-DAQmx Base is present in the system.
NI-DAQmx Base 3.6 for Windows returns an error, "Error 42 occurred at RLP Invoke Node. Possible reason(s): Unable to enable interrupt events for this device. Refer to the DAQmx Base ReadMe for more information about this error.", when used with PCI/PXI/PCIe boards. Refer to KB 5ZBD9VG2 for more information.
NI-DAQmx Base uses polynomial scaling (voltage to temperature) for thermocouple measurements, but the temperature range that the software supports is not consistent with the minimum accurate range of the inverse polynomial coefficients used for several thermocouple types. For more information, visit ni.com/info and enter rditml.
The minimum sample rate for E Series devices is 1.2 Hz. NI-DAQmx Base only uses the 20 MHz clock and E Series devices have 24-bit counters, which limits the minimum sample rate to 1.2 Hz (20 MHz/224). For lower sample rates the timebase divisor overflows 224. When this value is loaded into the 24-bit counter, only the lower 24 bits are used, resulting in a much faster sampling rate than expected.
M Series finite pulse train generation is allowed by the NI-DAQmx Base API but does not behave as expected. In finite pulse train mode the selected counter only generates a single pulse regardless of the number of pulses requested. Single pulse and continuous pulse generations behave as expected.
When a new device is added or removed, select Start»Programs»National Instruments»NI-DAQmx Base»NI-DAQmx Base List Devices.
Make note of the device name (such as, Dev1) as this is the name you need to specify when creating channels in the program. A device name might change each time a device is added or removed.
To use static tasks created with the NI-DAQmx Base Configuration Utility, type the desired task name into the Task Constant or Task Control.
When using any NI-DAQmx Base control from the control palette, make sure the Allow Undefined Names attribute is enabled. To enable the Allow Undefined Names attribute, right-click the control and select I/O Name Filtering. Place a checkmark in the Allow Undefined Names checkbox and click OK.
The NI-DAQmx Base installer does not overwrite existing task configuration files. To restore the task list to the default tasks, import the configuration file installed in the static example directory.
Using DAQmxBase CreateTask, DAQmxBase Create Virtual Channel, and DAQmxBase Clear Task in a loop leaks approximately 110 Bytes per iteration. If you pass in a string for the taskName parameter in DAQmxBase Create Task, the memory leak does not occur.
If, when building an executable or shared object project using NI-DAQmx Base VIs, the Application Builder catches an error, you must restart LabVIEW before running any NI-DAQmx Base VI.
DAQmxBaseIsTaskDone and DAQmxBase Is Task Done do not currently support analog input.
If your machine enters Hibernate/Sleep, restart your C application, LabVIEW-built application, or LabVIEW development environment to properly communicate with your DAQ device.
NI-DAQmx Base is not multi-thread safe. In LabVIEW, use the error cluster to force execution order. In C, use only one thread to make API calls; especially for task/channel creation and deletion.
NI-DAQmx Base Error Codes
[/table]
| Error Code | Description |
| –223700 | 200 kS/s, 12-bit, 16 AI channels, two AO channels, 8 DIO lines, two counter/timers. |
| –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 prior to 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 or more counter timebase properties. The conflicting properties must satisfy the following constraints: |
| |
| |
| |
| –200714 | Acquisition has stopped because the driver could not transfer the data from the device to the computer memory fast enough. This was caused by computer system limitations Reduce your sample clock rate the number of channels in the task or the number of programs your computer is executing concurrently. |
| –200608 | Acquisition cannot be started, because the selected buffer size is too small. Increase the buffer size. |
| –200565 | Specified digital channel contains more bits than supported by the 8-bit version of DAQmxBase Port Write. Use the version of DAQmxBase Port Write that supports wider digital ports. |
| –200564 | Specified digital channel contains more bits than supported by the 32-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 the task already contains channels with a different channel type. Create one task for each channel type. |
| –200558 | One task cannot contain multiple independent devices. Create one task for each 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 this property. |
| –200527 | Requested values of the Minimum and Maximum properties for the counter channel are not supported for the given type of device. The values that can be specified for Minimum and Maximum depend on the counter timebase rate. |
| –200526 | Write cannot be performed because this version of DAQmxBase Write does not match 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 not match 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 all channels 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 the data written. |
| –200523 | Read cannot be performed because this version of DAQmxBase Read only returns data from a single channel, and there are multiple channels in the task. 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 every colon (":") in the input string. Or, if a name is specified after the colon, 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 the same 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 the task. |
| –200474 | Specified operation did not complete, because the specified timeout expired. |
| –200473 | Read cannot be performed when the Auto Start property is false and the task is not running or committed. |
| –200459 | Write failed, because there are no output channels in this task to which data can be written. |
| –200452 | Specified property is not supported by the device or is not applicable to the task. |
| –200430 | I/O type of the physical channel does not match the I/O type required for the 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-bandwidth limitations, the driver could not read data from the device fast enough to keep up with the device throughput. Reduce the sample rate, or reduce the number of programs your computer is executing concurrently. |
| –200341 | Generation was configured to use only onboard memory, but the corresponding buffer is larger than onboard memory. Buffer size is provided implicitly 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 both an 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 the destination are the same terminal. In many cases, such as when configuring an external clock or a counter source, you must select a PFI, PXI Trigger, or RTSI line as the source terminal. |
| –200287 | Attempted to write to an invalid combination of position and offset. The position and offset specified a sample prior to the first sample generated (sample 0). Make sure any negative write offset specified selects a valid sample 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 or read later in your program. To make the samples available sooner, increase the sample rate. If your task uses a start trigger, make sure that your start trigger is configured correctly. It is also possible that you configured the task 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. The acquisition has stopped, therefore the sample specified by the combination of position and offset will never be available. Specify a position and offset which selects a sample up to, but not beyond, the final sample acquired. The final sample acquired can be determined by 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 Create Channel, you must use the name assigned to that channel. |
| –200261 | An attempt has been made to use an analog trigger in multiple situations with differing properties. Change the analog trigger properties so they are the same, or do not use an 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 triggering hardware. |
| –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 to help for valid terminal names. |
| –200012 | Specified physical channel does not support digital output. |
| –89136 | Specified route cannot be satisfied, because the hardware does not support it. |
| –89131 | An attempt has been made to perform a route when the source and the destination are the same terminal. In many cases, such as when configuring an external clock or a counter source, you must select a PFI, PXI Trigger, or RTSI line as the source terminal. |
| –89120 | Source terminal to be routed could not be found on the device. Make sure the terminal name is valid for the specified device. |
| –50256 | USB Device error: feature not supported. |
NI-DAQmx Base Warning Codes
[table]
| Error Code | Description |
| 209800 | DAQmxBase Read did not complete before the arrival of the next sample clock which indicates that your program is not keeping up with the hardware clock. For tasks using sample clock timing slow down the hardware clock or else change your application so that it can keep up with the hardware clock. |
| 209802 | DAQmxBase Wait for Next Sample Clock detected one or more missed sample clocks since the last call to Wait for Next Sample Clock which indicates that your program is not keeping up with the sample clock. To remove this warning slow down the sample clock or else change your application so that it can keep up with the sample clock. |
| 233700 | Internal software warning. |