chriswou

I've added some extra details. This schematic should work, correct? Total current = 64mA. Would you still recommend any extra resistors? Any other things I should take into consideration? Luckily, I have one more 2408 sitting around that I was unaware of until today. So, I'll be able to try this configuration out, but I'd like a confirmation that this looks good before I do?

I don't know why I didn't think to check the current rating for the +5V pin! I'll probably just swap J6 and run these from DGND to DIO. It'll make my life easier anyway. There was actually one fewer of each of those SSRs, but that's still above the limit. Is this constraint in the TC-AI datasheet? I'm not seeing it...

**I'm reposting this in the correct part of the forum** Not really sure what could be causing this. I'm using 7 DIO channels as indicated in the attachment. I tried to lay it out as plainly as possible. I'm controlling 8 SSRs with 7 DIO channels (DIO0 is controlling two). They are in pullup mode, which is why I'm connecting the high side of the SSRs to the +5V output from the 2408. On one of my boards, DIO4 and DIO5 went bad on me (DIO4 reads 2.18V from DGND regardless of on/off state, and DIO5 reads 0.64V at off state and 1.25V at on state). All of the other DIO channels are working as expected. I had another board that when I plugged it into this configuration, different DIO channels went bad. After I pulled it off the configuration and plugged it into my PC for testing, the whole thing seemed to have gone bad, and it even makes a humming noise when I plug the USB cable in. Very aggravating. I never got a chance to inspect which channels went bad on this one before it went completely bad, but one of them was definitely DIO0. The channels were different, so I don't think it's an issue with the SSRs themselves. According to the datasheets: 240Di45 SSRs have a control current of just 4mA each and the OAC5A SSRs are around 20mA each. 4 x 4mA + 4 x 20mA = 96mA. This is below the maximum of 150mA. This 2408 is actually just a replacement for what we've always used in the past (USB-TC-AI) because I wanted to add and analog output channel to our instrument. The key difference in the configuration here is that for the USB-TC-AI, the DIO is connected to the high side of the SSRs, and the low side is connected to GND. I also have an analog input in temperature reading mode with a thermocouple connected to it, another with a pressure transducer, and one more connected to a giant potentiometer with its own 5V power supply. These are the same as we've always used on the USB-TC-AI's. Needless to say, I'm very frustrated at this point and completely lost. Can I get some recommendations on what I can do here? I have two 2408's, one completely bricked and the other with two dead DIO ports. I'd like to be able to just send these in to be inspected if that would help in determining what's going wrong with them. If there's any more info I can give, let me know.

It seems like I'm having a different problem now. I opened the project from the JKI Dragon application (that installed with 2024), and now none of the ULx methods in the ULx VIs seem to work. They're all giving me errors. This is becoming a very tiresome issue. At least before, the VI's were usable, they just weren't in the palette, but now they're completely unusable. Any idea how to troubleshoot this? EDIT: It looks like I was able to fix this issue by closing out of Labview and opening the project back up, and when it searches for the ULx.dll file, I force it to find it in the LV 2021 folder (it started looking in the LV 8.5 folder for whatever reason). Is there any way to avoid it looking for the DLL file in the wrong location? It seems to want to do this every time.

I found the issue. The only way I can get it to work (and it actually installs the .mnu file itself) is when I uninstall ULx totally, and reinstall it by ONLY selecting the version of LV that I want it to install on. Now that I think about it, I don't think it ever actually installed on 2021 (even though I told it to). I actually just dragged all of the files over and expected it to work. I guess it just can't install on more than one version for whatever reason. I think this will be okay for now. I don't think I'll be using ULx on more than one version of LabVIEW anyway.

Which Windows OS version are you using? Windows 11 Pro Are you using Windows on a standard PC, running Windows on a MAC using Parallels Desktop or running Windows on a Virtual Machine? Standard Do other users logon to that target system with their profiles or are you the sole user account on that system? Only me. I am logged into a domain if that makes a difference. Are there other versions of LabVIEW installed on that system? Yes, and oddly enough, I tested it out on my LV 2016 32bit (I still had to add the .mnu file), and it works just fine. Could this be the issue? Should I uninstall it? I like to have it installed because I have two different software projects that each use a different version of LV. Restart your system. Afterward, using the Windows Taskbar's Search field, enter appwiz.cpl to open Windows' Control Panel - Programs and Features. Click on the Publisher header to sort by that column and then scroll to Measurement Computing Corporation. What are the versions shown for InstaCal and ULx for NI LabVIEW? Select only the ULx for NI LabVIEW program and then click the Uninstall option. ULx = 2.29 InstaCal = 6.74 If you are not using InstaCal v6.74, download and install the current version. Afterward, download and install the current version of ULx for NI LabVIEW. Restart Windows followed by LabVIEW 2021. Does the ULx for NI LabVIEW palette show the vi icons without the question mark? Uninstalled, restarted Windows, installed ULx (32-bit version), booted up LV 2021, and still questions marks. In your last response, it shows the vi's in a non-standard location. Why is that? When you right-click the item in the palette editor and select "Display path for palette file...", you get a path to the VI which is different than where the path is located. I don't know why that is, but it's like that for every item I do that for in the palette editor. It's like it saves another local VI into your user files separately from where it's located in vi.lib for some reason. My vi.lib - ULx directory resides at 'C:\Program Files (x86)\National Instruments\LabVIEW 2024\vi.lib\ULx'. Mine are there also. I don't know enough about how the palettes work to know why they're in both locations. Lastly, if you can do so, download the current release of LabVIEW (Community or other edition). Reinstall the current version of ULx for NI LabVIEW afterward. Will do.

It seems to be pointing to the correct files when I try to find them via the palette editor. When I right-click a VI in the palette, and try to open it, it gives this error:

Weird, it still isn't working. I've attached a picture. My "C:\Program Files (x86)\National Instruments\LabVIEW 2021\menus\ULx" folder wasn't created during the installation either. I'm not sure why this isn't installing correctly. I remember it used to work just fine years ago. Is there any way I can point those question marks to the correct libraries? I've used LabVIEW for years but never played around with the menus/function palettes.

I found this post, but that menu file didn't work for me. It shows up in my functions palette, but all of the VI links are blank and empty. Is there another menu file specific to LV2021 32 bit? I'm assuming it goes into the user.lib folder? The ULx files are installed, and they're already in my vi.lib folder. I just can't access them from the function palette.