Select development environment
Visual Basic
uses new DLL
2k/XP/Vista

uses old DLL
98/ME
 
2k/XP/Vista
 
VB.NET
uses new DLL
2k/XP/Vista

 




 
VC++ Console
uses new DLL
2k/XP/Vista

uses old DLL
98/ME
 
2k/XP/Vista
 
VC++ GUI
uses new DLL
* 2k/XP/Vista

uses old DLL
98/ME
 
2k/XP/Vista
 
C# (.NET)
uses new DLL
2k/XP/Vista
 




 
LabView
uses new DLL
2k/XP/Vista

uses old DLL
98/ME
 
2k/XP/Vista
                                               * for VC++ GUI, new DLL, use VC++ Console samples for reference
NOTE:  Read about using old and new DLL API together HERE


DLL Related information for the software developer
Differences between old and new DLLs
read about it
complete API Documentation
for the new DLL
frequently asked questions
FAQ Here
Most recent Driver, DLL, .INI, .Inf, Docs, etc. linked to below
click this link
NOTE: Use browser BACK ARROW to return to here from the links above








































DLL Related information for the software developer
This simplified interface of the new DLL contains function calls prefixed with "EX_" which are designed to be used together. The advantage of the new DLL is that it groups several function calls together within the DLL.

An example of the simplification can be noticed by the number of calls required in the original DLL for the initialization or scanning process. While the original DLL would require several calls into the DLL to start either of those processes, the new DLL requires only a single call for each,  EX_Connect()  and  EX_Run()  if the default configuration  ( single device connected, single channel scan, 100Hz )  will work for you. The use of these two calls will connect to the first M30x device that is found, and start a single channel scan at 100Hz.

An example of the versatility of the new DLL can be realized by the scanning related options. The scan can be configured to only log data to disk, log data to memory which can be read by the application, or do both. There are also options to run a scan that stops automatically and even beep the PC speaker when it stops. These options are explained within the  API documentation here  or by following the link provided further up this page.

The links for the new DLL take you to links to  mini applications  that show the use of various single and multiple calls into the DLL. For example one mini application might show how to connect and get a single conversion - not much more than a single page of code. Another might show how to connect and do a multi-channel, digital-input type scan with memory and data logging. Another shows how to use a configuration file to configure the device, saving function calls into the DLL that might otherwise be required.

The applications provided in the links above to the new DLL can often be made to work with Win98/ME simply by replacing the reference to "LL_USB2k.DLL" within the sample applications with reference to "LL_USB.DLL". The exception is the .NET sample applications which require the .NET environment available within WinXP and Vista.

Please note that although most of the sample applications contain a copy of the DLL, that DLL may not be the most current, but instead the one that was used at the time the application was created. You can get the  most recent DLL here,  or by following the link provided further up this page.

The new DLL still has all the API of the original old style DLL, so you can use the new DLL with your old applications - as long as the new device driver is used with it.

BACK TO TOP









































Using old and new DLL API together
The newest DLL is backward compatible. In other words, although new entry points are frequently added to make the interface simpler, all the original entry points are still available. The links that go to either the new DLL or old DLL, also contain the API for each one, although the DLL is the same for each. The differences between the links is the applications. The old DLL links will contain sample applications that make use of only the old entry points, while the new DLL links will make use of the entry points provided later within the DLL.

For example, although the API for the new DLL linked to further up this page makes no mention of SP_SystemCalibration, it can be found by following the link to the old DLL - within the API documentation provided there. If you'd like to do a system calibration, while using the new API, you can initialize using the new API call, EX_Connect to connect, and then use SP_SystemCalibration later to do a system calibration. It should be noted, in regard to this particular function, that a system calibration is performed by the DLL during the call to EX_Connect but you can still do it again anytime while not scanning. The best way to think about it all, is that the newest functions are "wrappers" around the older functions. The DLL itself often uses the older functions internally - combining many of them into a single function call preceded by EX_

For your convenience, below are links to the API for both the old and new DLL.
    old API
    new API

BACK TO TOP










































VisualBasic source code download options Win98/WinME
Source Code Download
includes device driver, DLL, and sample app

instructions for opening archive
(plain text style format)
Documentation
view online with web browser
Documentation
download archive










































VC++ Console source code download options Win98/WinME
Source Code Download
includes device driver, DLL, and sample app

instructions for opening archive
(plain text style format)
Documentation
view online with web browser
Documentation
download archive










































VC++ GUI source code download options Win98/WinME
Source Code Download
includes device driver, DLL, and sample app

instructions for opening archive
(plain text style format)
Documentation
view online with web browser
Documentation
download archive










































VC++ GUI source code download options Win2k/XP
Source Code Download
includes device driver, DLL, and sample app

instructions for opening archive
(plain text style format)
Documentation
view online with web browser
Documentation
download archive










































LabView source code download options Win98/WinME
Source Code Download
includes device driver, DLL, and sample app

instructions for opening archive
(plain text style format)
Documentation
view online with web browser
Documentation
download archive










































VisualBasic source code download options Win2k/XP
Source Code Download
includes device driver, DLL, and sample app

instructions for opening archive
(plain text style format)
Documentation
view online with web browser
Documentation
download archive


Model 302 interface for the Model 35B Thermocouple amplifier
note: this example for Model 302
A sample application written in Visual Basic to interface the Model 302 USB Data Aquisition System
to the 35B Thermocouple Amplifier - source code is provided
VB302 sample appApplication documentation










































VC++ Console source code download options Win2k/WinXP
Source Code Download
includes device driver, DLL, and sample app

instructions for opening archive
(plain text style format)
Documentation
view online with web browser
Documentation
download archive










































VC++ GUI source code download options Win2k/WinXP
Source Code Download
includes device driver, DLL, and sample app
Documentation
view online with web browser
Documentation
download archive










































LabView source code download options Win2k/XP
Source Code Download
includes device driver, DLL, and sample app

instructions for opening archive
(plain text style format)
Documentation
view online with web browser
Documentation
download archive