Jonathan MA Tech

@Carlos Betancourt Right click each .llb file in C:\Program Files (x86)\National Instruments\LabVIEW <Version>\vi.lib\ULx\ , go to properties and uncheck "Read-only". Per my parallel thread.

In this NI forum thread from 2012, Nextal's problem appears to have been fixed by unchecking "Read-only" on an LLB file. Right clicking each .llb in C:\Program Files (x86)\National Instruments\LabVIEW <Version>\vi.lib\ULx\ , going to properties and unchecking "Read-only" solved my problem. Why were the files marked as Read-only? Would be great if the installer did all the things.

Thank you for the reference. But the solution there is unacceptable. In the past I've had the "While loading ______ LabVIEW reported 95 warnings. That's not that big a deal. The permission issue when saving is new and is a problem. When I'm working on our larger LabVIEW application and changing multiple VIs (not necessarily involving ULx, I need to be able to "Save All" without picking apart what is and is not ULx code. I want to have the library installed and to use the VIs that are in the functions pallet - not having to resave them in my own project's folder. What you're suggesting is NOT normal practice. I think there is something different, either with a new LabVIEW version or Windows 11 that changed the permissions of the .llb files so that LabVIEW cannot overwrite the files in a new version. Could you work on fixing this please?

I have LabVIEW 2024 (32-bit) and am trying to get ULx for LabVIEW installed with it. After installing LabVIEW, I used the MCCDAQ Software CD v6.75 to install InstaCal (but not ULx for LabVIEW) and then installed ULx for LabVIEW v2.29 as described by here. And I am having the same issue described here with icons not showing up in the functions pallet and have applied @Fausto's fix. The ULx_LV.dll and example files were there already but I had to copy the ULx.mnu and help files manually. Unfortunately, I had an additional issue: When I place one of the ULx VIs onto a block diagram and try to close and save things, I get this error. When I click OK, I get the a dialog prompting me to name the file. If I click OK to that, it asks me if I want to replace the file. If I click OK to that it takes me back to the "Cannot save VI......You do not have permission" error. This makes it so that I cannot properly close larger software projects. How should I proceed?

It turns out the noise being introduced by this part of the system is less than 20 mV which is insignificant for us. And there was other noise being introduced upstream that we'll be looking at but that's a different discussion. Thanks for the info, help and asking good questions.

We now know that the A/D the customer has is a MC PCI-DAS 6036. Are there any gotchas when interfacing the Analog Output of the USB-3105 with the Analog Input of the PCI-DAQ 6039?

Both our legacy equipment and new equipment use single ended though I don't know about our customer's system. We have been considering some kind of ground problem.

What is the impedance on the MC USB-3105 Analog Output channels? I can't find it in any manual or data sheet. We have a customer that used to use an A/D converter (that we don't know much of anything about) to receive analog voltage signals from our legacy equipment specified to have 100 ohms of impedance on analog output channels. When our customer recently switched to our newer equipment that uses the MC USB-3105 to output analog data for backwards compatibility they started seeing noise on their end. How might impedance affect the noise on other generic A/D converters? What else should we consider?

I need to download InstaCal and your LabVIEW API for commercial use. I went to https://www.mccdaq.com/ and navigated to SUPPORT -> Downloads -> MCC Software -> InstaCal Software. After filling out the form I get to where I could download InstaCal but directly underneath I see it says: Use of Site. National Instruments ("NI") authorizes you to view and download the materials at this Web/FTP site ("Site") only for your personal, non-commercial use, provided that you.... How can I download InstaCal and the LabVIEW API for commercial use as before?