ULx for NI LabVIEW™

Apologies, the link the first answer proposed has a folders for Archives 6.51, 6.565, 6.60 and 6.61. In what folder do I find ULx vers. 2.22? Also, newer version works in Labview but they keep throwing warnings that ULx 2.22 is expected.

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

The specific ULx version you are asking for is in version 6.60. As for the warnings you see, all of the ULx versions were saved (by us) in a much older version of LabVIEW, so that users of any LabVIEW version back to 2010 can be used. Once you re-save your/all ULx VIs from within your current LabVIEW version, the warnings will go away.

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

ULx is only available as part of the free MCCDAQ software suite. Any version of ULx >= 2.21 will work in LabVIEW 2017. If you prefer to stay with ULx 2.21, it is available as part of MCCDAQ 6.60 which is now about 4 years old, and can be found on our FTP’s archive area here: ftp://ftp.mccdaq.com/Archive/MCCDAQ_CD/

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

In general, re-installing InstaCal is not a solution to a LabVIEW error. Error 10001 is not very common, and usually means that more than one program is trying to access the device, or that you have created a runtime and there is a mismatched file version. Below is some general advice, and if this does not resolve it, please contact tech support with more details. * Do not have LabVIEW and InstaCal open at the same time. * InstaCal is meant to be run once per PC (you should not have to run it again, even after a reboot). * If you created a LabVIEW runtime, install the same exact version# of InstaCal onto the runtime PC, that was on the development PC.

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

We expect to release and post for download, within a week or so, MCCDAQ software suite 6.72. This will contain an updated version of ULx compatible with LabVIEW 2020.

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

NI has not yet created a .NET VI conversion utility for NXG. MCC ULx support for NXG will depend on NI releasing its conversion support for .NET. MCC has requested that this conversion utility be added, and NI has ensured us that it is on their NXG roadmap. Please contact National Instruments if you would like them to prioritize that effort.

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

MCC added support for LabVIEW 2019 about a month ago. ULx 2.24 and InstaCal 6.71 are available together as part of the free MCCDAQ software suite rev 6.71 available from our download area here: https://www.mccdaq.com/Software-Downloads

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

The main cause of the error you see relates to “Composite”. None of the Composite VIs will work with the USB-1208LS hardware model, since that model cannot sample DI and CI channels synchronously (at the same clocked rate) as AI channels. Instead, start with the examples in Measure Voltage.llb, specifically the one named: ULx Acq&Graph Voltage-Int Clk-Dig Start.vi However, since the USB-1208LS hardware offers only level triggering (not edge triggering) you will have to make a change on the example’s block diagram. i.e. select Basic Digital Level, and then specify either High or Low for the level. Then connect your trigger signal to pin 18 of the USB-1208LS.

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

It is not compatible with LabVIEW NXG at this time, but I have forwarded your request to our Engineering team for consideration in future releases.

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

For the USB-1602HS hardware, gating is not supported. i.e. the hardware design of this model has no “gate” triggering capability. As for the Composite triggers, before selecting composite, you must first configure your input channel(s) via Create Channel to be Composite Input (instead of Analog Input). Composite usually means a combination of AI, DI, and CI channels all sampled synchronously at the same rate, but if only analog inputs are needed, that can be done also.

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

For LabVIEW 2018, we just recently posted a beta ULx driver on our FTP site here: ftp://ftp.mccdaq.com/Customer/beta/Beta_ULx_for_LabVIEW_2018/ Be sure to read the readme for installation instructions, as the installation is different from our normal release.

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

The ULx For NI LabVIEW software is included on the MCC DAQ CD and is available for download at the following link: https://www.mccdaq.com/Software-Downloads

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

We actually do have a released LabVIEW 2017 driver, ULx ver 2.21. Below is the download link (it has its own installer). Be sure to read the readme first (for installation directions) https://www.mccdaq.com/downloads/interim_download/ULx_for_LabVIEW_2017/ Ver 2.22 is expected out soon, and since it will be part of the MCCDAQ CD 6.60 download, we will soon disable the above link.

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

Hello Fabrice - To read a temperature channel on any of the TEMP/TC series devices, you can run the example on your hard drive that is located at the path below. The example program is named: ULx Acq Temperature Sample.vi --- C:\Program Files\National Instruments\LabVIEW 201x\examples\ULx\Analog In\Measure Temperature.LLB

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

Once you Install the latest ULx driver, then open the following LLB of examples on your hard drive: C:\Program Files\National Instruments\LabVIEW 2016\examples\ULx\Analog In\Measure Voltage.LLB. The best example to start with is named: ULx Acq&Graph Voltage-Int Clk.vi The example defaults to sampling a single channel, but from the front panel, following the instructions in the FAQ at the link below, you can browse and select multiple channels with the mouse: http://kb.mccdaq.com/KnowledgebaseArticle50375.aspx

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

The installation drive letter should not matter, since our ULx installer learns that from the Windows registry. Instead, the issue is likely that you are using too old of a CD to install from. Version 6.53 of our MCCDAQ CD was the first to include LabVIEW 2016 support. You can download the latest free MCCDAQ CD from our website at: http://www.mccdaq.com/software.aspx

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

RS422 is an electrical standard of +/- 6V and is differential. The miniLAB 1008’s digital I/O bits are TTL/CMOS and single-ended. Therefore before even considering software, the miniLAB 1008 hardware is not suitable for communicating to RS422 devices. Strictly on the software question, looking at the 37 pin D connector, pin 4 is bit 6 of port B, while pin 35 is bit 2 of port A. Since you are using two different ports (A and B) you can use one for output and one for input. First, test each direction independently with our provided examples: ULx Read Dig Port.vi and ULx Write Dig Port.vi. Once you have both working independently, then combine the two programs. Since we do not promote our hardware as emulating a serial port, we do not have an example program that does so.

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

There are no LabVIEW VIs that will allow you to read the 5 volt source that is supplied on pins 18 & 46. One method that has been used in the past to monitor the 5 volts is to loop back into an available analog input and read the analog input.

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

The link below is to MCC DAQ CD Version 6.34 from September 2014. It has 2 LabVIEW drivers on it. One is ULx 2.06, the last version to support LabVIEW 8.5, 8.6, and 2009. The other is the much older legacy UL for LabVIEW driver frozen in 2006. http://www.mccdaq.com/downloads/Archive/MCCDAQCD_compatible_with_LabVIEW_6.0-2009/

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

Our ULx for LabVIEW driver does not have a way to select between SE and DIFF. This setting must be made by the user in InstaCal, before launching LabVIEW. The setting only needs to be made once.

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

First, make sure that your DAQ device supports hardware/clock paced analog output. Then locate on your hard drive (at a path similar to below) the following example: ULx Cont Gen Voltage Wfm-Int Clk.vi C:\Program Files (x86)\National Instruments\LabVIEW 201x\examples\ULx\Analog Output\

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

Is there a way to read the actual output status?

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

Hello Emmanuel - MCC’s hardware does not support reading back values written to the output. If the error code (returned from the data write) is 0, then the output was successful.

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

I think you are talking about using the digital outputs (8 on FirstPortA and 8 on FirstPortB) on the USB-1208LS, which is an older hardware model (that uses a real 8255 IC; newer models emulate the 8255). The issue you report is limited to just a couple of older DAQ models. A workaround is to, at the start of your app, write out benign values to both FirstPortA and FirstPortB, before you start to write new values to either port. Any further writes will not impact (reset) values written prior, since the direction of both ports were set (automatically for you by ULx) in the first two writes.

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

Most analog output examples that get installed with ULx demonstrate hardware paced/clocked mode. But if you only want to send out an occasional D/A value, which the DAQ device will hold until you update it at some later time, then software paced mode is more appropriate. We have posted such an example at the link below: http://kb.mccdaq.com/KnowledgebaseArticle50451.aspx

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

We do offer Linux drivers for many of our USB and Ethernet DAQ devices but, unfortunately, our ULx for NI LabVIEW does not include support for NI LabVIEW for Linux. Our ULx for NI LabVIEW is only supported under Windows® 10/8/7/Vista®/XP SP2, 32-bit or 64-bit Windows based operating systems.

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

Error 10003 usually means that the timeout has been reached. You set the timeout via the ULx Read VI. The default is 10 seconds, which matches what you report. So instead of leaving the timeout pin unwired (as shown in the video), wire up a constant of something > 10.

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

The USB-2408 (and USB-2416) series can measure both temperature and voltage. All channels on these models are designated as voltage, so be sure to choose “AI Voltage”. There is an FAQ on our knowledgebase with an example: http://kb.mccdaq.com/KnowledgebaseArticle50481.aspx

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

Hello Isaac, Error 100000 usually means that your InstaCal and ULx versions are too far apart from each other, age wise. The fix is to upgrade both at the same time, from the same MCCDAQ CD/download.

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

Hello Isaac, The ULx for NI LabVIEW is necessary for the support of Measurement Computing Data Acquisition products within the LabVIEW environment. Our Data Acquisition products are not directly compatible with National Instrument’s NI-DAQmx drivers.

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

It sounds like you want to perform Analog Input, but you are presented only with Analog Output channels, or vice-versa. The USB-1208FS DAQ model you are using has both types of channels (though you should select AI Voltage, not AI Current input, since the USB-1208FS only measures voltage. What likely happened is that you changed the Create Channel VI’s channel type, from Analog Output to Analog Input, but you did so after wiring in a channel selector. Try deleting the physical channel selector (purple) to the left of the Create Channel VI, and then recreating it. It should then locate the proper channels. Otherwise, try our function-specific examples that get installed as part of ULx.

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

Hello Stephen - On September 25th, MCC released ULx driver version 2.12 that adds support for LabVIEW 2015. Below is a link to download the new support, along with a readme file covering installation. This driver is fully released (not a beta), but the installer for it differs slightly from our regular MCCDAQ CD download, so be sure to read the short readme file before installing the software. Our larger (MCCDAQ CD) download is expected to be update in the November/December timeframe, once CD version 6.51 is released, at which time the following link will be deactivated. http://www.mccdaq.com/downloads/interim_download/ULx_2.12/

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

1) Yes, this is possible. Basically you chain together (i.e. in one task) multiple Create Channel VIs, each with a channel(s) and range combination. 2) No, this is not possible. The limitation is hardware, not software.

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

Hello Alex - You say you installed UL 6.35, but be sure you also installed ULx (ver 2.10 is part of the same MCCDAQ CD download). To use MCC brand hardware in LabVIEW, you use our ULx VIs. Many examples are installed on your hard drive, but note that since the USB-2408 can measure both voltage and thermocouples, you need to run the voltage examples, not the temperature examples. Here are two FAQs that should be helpful: http://kb.mccdaq.com/KnowledgebaseArticle50481.aspx and http://kb.mccdaq.com/KnowledgebaseArticle50432.aspx

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

Most likely what happened is that you created the constant (or control) for the “physical channels” input before setting the Polymorphic VI Selector to “AI Temperature”. The default is “AI Voltage”, and since the USB-TC does not measure voltage, no channels would be shown in the list.

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

Hello - It sounds like you missed a step or two in the EXE creation process. In the ULx help file, search on “Building the application installer”, and carefully follow steps 1 thru 12. Please feel free to contact us if you have any issues.

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

MCC’s ULx for LabVIEW includes an example named ULx Acq Temperature Sample.vi which works fine with the USB-TC, but it only samples just one reading on only a single channel. Common needs are to expand the number of channels and to sample continuously. The USB-TC is only software paced, so a software timed loop is needed. You can configure the Create Channel VI to specify a range of channels, and then the Read VI can output a one-dimensional array … one sample per channel. At the link below is such an example, that samples 5 channels at a 1 Hz rate. It does not graph the data, or log to disk, but you can use LabVIEW’s built in VIs to achieve those. http://kb.mccdaq.com/KnowledgebaseArticle50417.aspx

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

Hello Frabre - The hardware in itself does not support an analog edge trigger. Therefore, the ULx driver does not support an analog trigger. The USB-202 only supports a digital trigger that can be configured for edge or level sensitivity (rising, falling, high, or low). Please feel free to contact us if you have any additional questions.

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

A ULx driver compatible with LabVIEW 2014 is expected to be posted for download by mid-September.

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

Hello - The structure of the data array for our Tin function call is not a perfect match for what LabVIEW is looking for. The TinScan call places the data into one column, verses a row, with a column of data per channel. LabVIEW does not know how to parse this data. However, there are ways to get it to work and display multiple channels. For your convenience, I’m going to email you an example VI to help with your programming. Please check your inbox and let us know if we can help out in any other way.

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

Hello Murray - There are three likely causes to the problem you report: 1) You did not run InstaCal (Inscal32.exe) on your target machine, so that the DAQ device was recognized on the target machine. 2) You did not follow the detailed steps listed in the ULx help file for: Building a stand-alone Windows application. The results of which automatically pick up a “browse” file and deploy it on the target PC’s hard drive. The file name follows the following format: ULx_BrowseXXX.LLB where, for example, XXX=110 for LabVIEW ver 11. 3) You have duplicate copies of CBW32.DLL on the target PC’s hard drive.

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

The message you receive probably means the file was not fully downloaded, or got corrupted during the download. We have not had other recent complaints. But to be sure, I downloaded Version 6.31 myself from this link, and it runs OK. ftp://ftp.mccdaq.com/downloads/MCCDaqCD/ I recommend you download it by saving it to your hard drive first. Then before running it, check the file size. The file size should be exactly 279,810,048 bytes.

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

Hello Swank - If the LabVIEW version you just installed happens to be version 2013, be sure to install the very latest ULx (2.03), otherwise ULx won’t be installed for that LabVIEW installation. Normally a copy of ULx is installed for each and every LabVIEW on the PC, from 8.5 upward. Therefore you don’t need to move ULx VIs from one version of LabVIEW to another. Also note that the ULx VIs installed were all saved in 8.5 format, so you will get warnings when you open them in a newer version of LabVIEW. Either ignore the warnings, or re-save all upon exiting. BSODs are not at all common, and may be a sign that something is corrupt (best to uninstall and reinstall).

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

The reason the palette menu did not install for you is that most likely you did not actually unzip the beta zip file, before running the MSI (i.e. running the MSI file from within the Zip file will not install any of the files that are outside the MSI file). As for the USB-310x hardware series specifically, yes the range must be set in InstaCal.

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

Oh yes, the task note. If only that was retrievable from a block palette, because I did not find it in any example. Because the palette menu does not install with ULX for LV13. And I also presume that the card configuration (e.g. 0/10V, -10/10V, 0/20mA for each output of an USB3016) can only be set (and queried) with Instacal, or?

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

ULx for NI LabVIEW does not offer a way to provide the developer with full information about what DAQ device(s) are connected, or what features the device(s) have. What is supported is: The Create Channel VI presents (to the operator) only channels that exist on the DAQ device(s) that are present in the system. Once a task is created, the Task Node VI from the ULx VI palate can be used to read back the model name & serial number.

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

No, the ULx for NI LabVIEW is not compatible with the Real-Time version of LabVIEW.

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

MCC now has a beta ULx driver for LabVIEW 2013. A FAQ with more information is available on our knowledgebase at: http://kb.mccdaq.com/

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

It sounds like you cannot install ULx onto LabVIEW 2012 since your CD is too old. You need version 6.25 or higher to obtain ULx 2.02. Download the latest MCCDAQ CD from our website, and update InstaCal, and install ULx 2.02. In this way you do not have to use our Legacy UL for LabVIEW driver which has been frozen for many years and is not recommended for new applications. The try ULx examples named ULx Write Dig Port.vi & ULx Read Dig Port.vi

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