Universal Library

The Universal Library is free to use and no license is required.

Was this answer helpful? Yes (2) / No (0)

Measurement Computing is currently researching the demand for .NET 5/6 (CORE) support within our customer base. Based on our findings we will start investigating the process and changes needed to our Universal Library for .NET 5/6 (CORE) support. Please check back periodically for updates.

Was this answer helpful? Yes (6) / No (1)

Yes, the Universal Library supports analog input triggering when using the USB-1604HS-2AO.

Was this answer helpful? Yes (2) / No (0)

The 4 example programs that support the USB-PDISO8 model are named: ULDI04, ULDI05, ULDO04, ULDO05. When you installed the Universal Library, the C# examples were installed here: C:\Users\Public\Documents\Measurement Computing\DAQ\C#

Was this answer helpful? Yes (2) / No (0)

We have since documented and posted examples of how to access data from a WebDAQ programmatically, via the WebDAQ-specific API (which is called the REST API): https://www.mccdaq.com/downloads/WebDAQ/REST-API/

Was this answer helpful? Yes (3) / No (0)

The WebDAQ logger Series does not work with the Universal Library. The WebDAQ does not have an API. All of its software is installed on the unit itself, and its configuration and data retrieval is performed via a web browser on your PC/device.

Was this answer helpful? Yes (3) / No (0)

Sample all channels at the highest rate then subsample for lower rates.

Was this answer helpful? Yes (3) / No (1)

The E-1608 hardware architecture allows only one sample rate during a scan, which applies to all channels. This is true of all of our devices.

Was this answer helpful? Yes (3) / No (0)

Hello, The binary file format of Demo.dat is not published, though is available by contacting tech support. Note that you could collect some data using the UL example program named ULFI01, which saves data to this same legacy file format.

Was this answer helpful? Yes (3) / No (0)

Hi John - The example program is indeed the correct usage. Thank you for passing along this documentation error, which we will log for correction.

Was this answer helpful? Yes (4) / No (0)

Hello - Universal Library & InstaCal version 6.51 and higher were fully tested with Win10-64. MCCDAQ.DLL is part of this package.

Was this answer helpful? Yes (3) / No (1)

Measurement Computing manufactures many products that can output waveforms. Writing a program to do so can be done but is not as simple as one might think. To assist our customers we have created a KnowledgeBase article outlining the steps on how to get this done here: http://kb.mccdaq.com/KnowledgebaseArticle50503.aspx?Keywords=Analog+output+scan My recommendation would be to use our TracerDAQ PRO Virtual Instrument application. One of the supported applications is a “Function Generator” that is all set to go out of the box and supports a “Sweep” function. http://mccdaq.com/daq-software/tracerdaq-pro.aspx

Was this answer helpful? Yes (3) / No (0)

All MCC products ship with our I/O library called the Universal Library. The Universal Library is a programming API for C®, C++®, C#®, Visual Basic®, and Visual Basic® .NET™ using Visual Studio® and other IDEs.

Was this answer helpful? Yes (3) / No (0)

Oops. My Bad. Gave the call to AoOutScan the file size, not the buffer size. fix is int)Math.Min(HBDNumSamples,BuffSize), as in: ULStat = HBDDaqBoard.AOutScan(HBD_LowChan, HBD_HighChan, (int)Math.Min(HBDNumSamples,BuffSize), ref DataRate, Gain, HBDMemHandle, Options); I have to handles files smaller than the buffer size, and larger (some WAY large, run for two or three minutes at 11009 sample/sec/channel)

Was this answer helpful? Yes (3) / No (0)

We tested this hardware model today using the current UL version (6.52), and curIndex does wrap as expected … at the buffer size. Perhaps you are outputting on multiple channels, and have added a multiplier to set the needed buffer size (since all of these numbers are not per-channel).

Was this answer helpful? Yes (3) / No (0)

The USB-1608FS-Plus or the USB-1608G series are both cable of handling 6 channels at 30 kS/sec each. We have not had any problems to date regarding PCs having issues running our 1608 DAQ devices. With that said you should not have any issues running a continuous analog input scan on 6 channels using our Universal Library. Data storage is left up to the end user. Please refer to our knowledge base article which can be viewed here: http://kb.mccdaq.com/KnowledgebaseArticle50453.aspx?Keywords=USB-1608G This KB article demonstrates how to continuously collect data using the USB-1608G.

Was this answer helpful? Yes (3) / No (0)

MCC does not have support for JavaScript. The programming languages C++, C# and VB are supported for execution on Windows. The Java programming language is supported for execution on Android, but Java is not at all related to JavaScript.

Was this answer helpful? Yes (2) / No (0)

The UL does include both 32-bit and 64-bit .LIB files for Microsoft C/C++, which you will find on your system at the following location: C:\Users\Public\Documents\Measurement Computing\DAQ\C. For other brand compilers, you likely need to use a utility from them to create a .LIB from either ourCBW32.DLL or CBW64.DLL.

Was this answer helpful? Yes (3) / No (1)

Currently, there is no method for extracting the current calibration date from your USB-TC. If you forward your serial number to [email protected] we can look up the last known calibration date for your USB-TC.

Was this answer helpful? Yes (2) / No (0)

Hello Josep, Compatibility with DEV C++ and our Universal Library has never been confirmed by Measurement Computing. However, as long as you can call in to a Windows 32bit API, you should have no problem interfacing with our Universal Library.

Was this answer helpful? Yes (2) / No (0)

Hello - Reading the CJC directly is possible through our Universal Library. Please refer to our knowledgebase article at the below link for details: http://kb.mccdaq.com/KnowledgebaseArticle50172.aspx

Was this answer helpful? Yes (3) / No (0)

However, beginning with the recently released version UL 6.50, there is now formal support via the AInputMode method (or via the AChanInputMode method for models with per-channel configuration).

Was this answer helpful? Yes (2) / No (0)

Historically this setting is made manually in InstaCal, since it affects the field wiring, and is unlikely to be changed often. Users of older versions of the UL would call the little known cbSetConfig function in CBW32.DLL. However, beginning with the recently released version UL 6.50, there is now more formal support via BoardConfig.SetNumAdChans in MCCDAQ.DLL.

Was this answer helpful? Yes (2) / No (0)

Hello Fazlollah, The USB-230 series supports a fixed +- 10 volt input range. Because of this you cannot just simply develop software code to allow the USB-230 to measure a current signal. To read your biosensor you will need some type of external signal conditioning. Now assuming that your biosensor outputs a 4-20 mA signal you could use a simple 249 ohm current shunt resistor across one of the differential inputs. This will create a 1-5 volt voltage drop across the shunt resistor. Which can then easily be read by any one of the USB-230 series DAQ devices. You can then write some software code to scale the voltage signal back into engineering units.

Was this answer helpful? Yes (2) / No (0)

6.35 is the current driver release, with 6.50 coming out later this month. The rate at which digital inputs can be sampled is hardware limited, so a new version of our driver will not help. The USB-1608FS-PLUS’s digital inputs can be read up to 200 times per second. A different model to consider is the USB-1608G, as its digital inputs can be read at up to 4000 times per second. Note that the USB-1608G’s analog inputs are multiplexed rather than simultaneous.

Was this answer helpful? Yes (2) / No (0)

You can, I added a script to compile with MinGWs GCC to the sample folder: @echo off if (%1)==() goto syntax gcc -x c -g -L.. "%1" -lcbw64 -o "%~dpn1.exe" > err.log type err.log|more goto end :syntax echo - echo - Compiles a file with MinGWs gcc, linking Universal Library echo - echo - Syntax: echo - MakeGCC filename :end

Was this answer helpful? Yes (2) / No (0)

MCC does not offer support for MinGW compilers or for Fortran. The 3rd party Linux drivers you reference will not be leverageable onto Windows, given the IO needs of the USB bus and DAQ devices.

Was this answer helpful? Yes (2) / No (0)

MCC’s current offering of Digital I/O devices are software polled only. They cannot notify the PC of a certain data change or pattern match.

Was this answer helpful? Yes (5) / No (0)

First, try our non-scanning example (ULDI01) to make sure there is no electric issue (i.e. make sure you can predictably read the expected 0 and 1 values when you connect proper logic low and logic high voltages). Then move on to the higher speed scanning example (ULDI03). Note that the digital I/O on the PCI-2500 series are 3.3V logic. They can tolerate 5V logic but avoid using pull resistors up to 5V.

Was this answer helpful? Yes (2) / No (0)

Hello Pavel - the new version of the Universal Library (Version 6.50) resolves this issue. It can be downloaded from: http://www.mccdaq.com/software.aspx

Was this answer helpful? Yes (4) / No (0)

That's good news. Please let me know as soon as new UL version will be released. Thank you.

Was this answer helpful? Yes (3) / No (0)

Hello Pavel - We have performed additional testing, and the combined load and initialization time can be as long was what you reported. As a result, we expect to be able to reduce this (to well under 1 second) in an upcoming UL version.

Was this answer helpful? Yes (4) / No (0)

The delay applies before reaching InitInstance() in my application and it is the same even when I temporary uninstall the board's driver. When I remove all universal library functions and cbw32.lib from my project, there is no delay. I think the source of this delay is in slow loading cbw32.dll file. Regards Pavel

Was this answer helpful? Yes (2) / No (0)

Hello Pavel - 7.5 seconds sounds much too long for simply loading CBW32.DLL. 1-2 seconds is more typical. Perhaps your program is trying to call a function in the DLL as the program is loading. The first time a function (that accesses DAQ hardware) in the DLL is called, there is hardware initialization that is performed, which takes about 4-5 seconds. In summary, there are probably 2 delays at work here. We can’t reduce either, but perhaps you can postpone the second one, by not calling a DLL function until your program is fully loaded.

Was this answer helpful? Yes (2) / No (1)

Hello Demir - Unfortunately, our Universal Library no longer supports Borland compilers. A possible workaround would be to use the Implib.exe program within Borland to create an Import library file that would call into our C++ DLL that is provided with our Universal Library drivers.

Was this answer helpful? Yes (3) / No (0)

Hello -The PCI-DIO series does not support clocked pacing/reads. So software paced reads must be used. Calling the Universal Library’s DIn function in a tight loop, one 8-bit port can be polled every 20-25 uS (40 KHz – 50 KHz).

Was this answer helpful? Yes (3) / No (0)

The function cbDBitOut() can be a bit confusing but it does works for all three ports. Please refer to our knowledgebase article below for help in clarifying how the cbDBit() functions works. http://kb.mccdaq.com/KnowledgebaseArticle50121.aspx?Keywords=dbitout. You first need to configure the direction for all three ports, i.e. input or output. After the ports have been configured you can then run the cbDBitOut() function. To access FirstportB and C all you have to do is to offset the Bitnum + n. FirstportA = 0-7. FirstportB = 8-15 and FirstportC would = 16-23. Please contact technical support if you have any additional questions.

Was this answer helpful? Yes (4) / No (1)

Yes it is thread safe but an annoying problem is the inability to use the UL in multiple applications on the same system. For example, say you want to run multiple instances of the same (or different) application even though each instance uses their own modules (board IDs) subsequent applications will clobber I/O modules used in previous instances on the first call into UL. I have been able to prevent this by making an out of process COM wrapper around the UL !!! The idea is that my wrapper initiates the UL one time upon the first caller then closes it when the last application closes regardless of order. A bit tricky for sure! It is unfortunate that UL does not handle this !!! Presently I can handle SB-1208, USB-SWITCHSENSe and USB/PCI/PCIe-DIO24 with my 'wrapper' which soon will be ported to .NET.

Was this answer helpful? Yes (3) / No (0)

The recent release of UL version 6.50 added Device Discovery, whereby the user no longer has to run InstaCal (not applicable for PCI/PCIe devices). Using Device Discovery, the UL can now support multiple applications running on the same PC, each interfacing with its own USB DAQ device(s). Each application, as its first UL call, must call IgnoreInstaCal. Next call GetDaqDeviceInventory which returns a list of DAQ devices found on the PC (model and factory serial number). Lastly, call CreateDaqDevice for each DAQ device that the application is to use.

Was this answer helpful? Yes (3) / No (0)

Hello GGEE - Yes, the Universal Library is thread safe. Multiple different DAQ devices can be accessed from one program, and separate threads in the program can be used. Also separate threads can access the same DAQ device. Note that one specific scenario is not supported: Multiple programs running on the PC, that each access the Universal Library … not even if each program accesses a different DAQ device.

Was this answer helpful? Yes (7) / No (0)

Hello Fintest - All of the UL examples installed as part of MCCDAQ CD should work OK with C# Express 2012. Be sure to re-boot after installing the UL. Also, if the error string contains the word “null”, it's a sign of duplicate DLLs (CBW32.DLL) per a FAQ on our knowledgebase. If you’re still having difficulty, please contact MCC Technical Support.

Was this answer helpful? Yes (2) / No (0)

UL version 6.50 contains new capability for programmers called Device Discovery. If an application is written to take advantage of this new Device Discovery capability, running InstaCal to discover devices is no longer required.

Was this answer helpful? Yes (4) / No (0)

Hi Chris – Thank you for your feedback. We realize the need/benefit for this and plan to address it in a future version.

Was this answer helpful? Yes (2) / No (0)

It seems that your "universal" library is the software for the universe 20 years ago under MS-DOS. Plug and Play meens, I get a e.g. USB-1208FS out of a tray connect it and run my software. Another user has a different module. Also I cannot manipulate the CF.CFG because it is written in a non structured format like XML. Another point is the missing object oriented way of the UL. _mccAD = New MccDaq.MccBoard(0) Dim dummy(5) As MccDaq.MccBoard For i As Integer = 0 To dummy.Length - 1 dummy(i) = New MccDaq.MccBoard(i) If dummy(i).BoardName.ToUpper.Contains("USB-QUAD08") Then _mccENC = New MccDaq.MccBoard(i) End If If dummy(i).BoardName.ToUpper.Contains("USB-1208FS") Then _mccAD = New MccDaq.MccBoard(i) End If Next If you want to use _mccAD further in this code the Visual Studio 2010 IDE vanishes without a trace... Please provide the UL with a function, which lists the available modules without running INSTACAL first. Regards Chris

Was this answer helpful? Yes (2) / No (0)

Hello Chris - To achieve your goal, the following is recommended: It Is assumed that InstaCal was run prior by the user, such that all boards had been recognized and that InstaCal has already added them to its board list (stored in CB.CFG). First use BoardName, with each possible board #. If no board entry is in CB.CFG for that board #, you will receive an empty string. Keep track of which board #s return a populated string. Note that being listed in CB.CFG does not mean that the board is physically present in the system (for example, a USB board may have been unplugged by the user). In order to verify the board is truly present, you must perform a function that the model supports, such as AIn or DIn, and if the function returns an error code of 0, then the board is physically present.

Was this answer helpful? Yes (2) / No (1)

Thank you for your inquiry. DASYLab is not capable of creating a DLL file or an executable. In order to deploy your DASYLab program you will need to use a DASYLab Run Time license which installs the necessary files and allows for the execution of your DASYLab applications on target systems.

Was this answer helpful? Yes (2) / No (0)

Yes, our Universal Library C examples can be used in any version of Visual Studio (certainly versions 6.0 thru 2013). We provide both 32-bit and 64-bit DLLs, as well as supporting files.

Was this answer helpful? Yes (9) / No (0)

Hello Spinner - We will not support Windows 7 or Windows 8 for PC-104. We do, however, offer 2 USB products with the same form factor as PC-104 that are supported in Windows 7 and Windows 8. Please take a look at the USB-7202 (http://www.mccdaq.com/usb-data-acquisition/USB-7202.aspx) and the USB-7204 (http://www.mccdaq.com/usb-data-acquisition/USB-7204.aspx)

Was this answer helpful? Yes (2) / No (0)

Hi Spinner - Thank you for your inquiry. The current software that ships with our PCIe products supports both Windows XP and Windows 7/8.

Was this answer helpful? Yes (3) / No (0)

To make lib for Embarcadero C++ do: For 32 Bit 1.) copy DLL file from c:\Program Files (x86)\Measurement Computing\DAQ\cbw32.dll to some directory 2.) use embarcadero tool implib: implib cbw32bc.lib cbw32.dll (for 32 bit version) Move or copy cwb32bc to c:\Users\Public\Documents\Measurement Computing\DAQ\C3.) use MakeBC32.bat to compile samples on c:\Users\Public\Documents\Measurement Computing\DAQ\C\Sample32 Note MakeBC32.bat is installed during regular instalation of Universal library. However there is missing cbw32bc.lib and support for 64 bit: cbw64bc.lib, makeBC64.bat ! 4. What is solutions for 64 bit ? for 64 bit MKEXP.EXE is the 64-bit Windows counterpart of IMPLIB.EXE Have someone suitable .bat file to compile and link? Measurement computing please add support also for Embarcadero compilers!

Was this answer helpful? Yes (4) / No (0)

Hello Nivram - MCC does not provide or test LIB files for Embarcadero C++. You should be able to create your own LIB file, using a tool/utility provided by Embarcadero that creates a LIB file based on a particular DLL. The DLL to reference is either CBW32.DLL or CBW64.DLL, depending on whether you want to make a 32-bit or 64-bit application (both should run on 64-bit Windows). Both DLLs are installed as part of InstaCal/UL. The header file (cbw.h) is also installed by the UL.

Was this answer helpful? Yes (2) / No (0)

Our apologies, but the last version of the UL that supported Delphi was Version 6.1. You may still download this archived version from our ftp site at the following link: ftp://ftp.mccdaq.com/Archive/MCCDAQ_CD/Archive_6.10/

Was this answer helpful? Yes (9) / No (0)