Bret.PID.Analyzers

@Fausto We were able to determine that the pump was causing the issue with the 1608; disconnecting it stopped the disconnection issue, and the 1608 seems to work consistently now. The pump will be given its own power supply to buffer it from the rest of the system. Thank you for the help! We are unfortunately having a new issue with the DIO-24/37 board that we are using, where Windows is saying that there is a power surge being detected whenever we try to use it to turn a heater on. Should I start a new conversation, or can I describe the issue in this thread here?

Thank you for the quick response! I'm using Windows 10 Pro and Instacal 6.74. We're using in-house software called Peakworks. The serial number of the board is 193334E-07L 24240EB. The board has worked fine in this application in the past. The board is inside a unit which sits in a standard office environment. There is a continuous pump inside the unit the board is in, as well as two heaters that run on 220V (this unit is bound for somewhere outside of the US). The board is powered by a powered USB hub, which in turn is running off of a 5V 3.5A power supply. There's no EMF shielding internally, but there hasn't ever been a need for it. The case for the unit that everything is in is aluminum and grounded, so that provides shielding from external sources. The only thing that I can think of that might interact negatively is the pump, which runs off of the 5V supply as well, but it only draws about 190mA, with the entire system drawing at most 1A, so I there shouldn't be any issues with sagging voltages.

Hello! We're using a USB-1608FS-PLS-OEM as a DAQ for a piece of our software. We have encountered what seems to be a disconnect occurring with the board while using our software multiple times, where we will suddenly start receiving obviously bad values (for example, a sensor that should be reading 24 C will start reading -899 C). When we go to Instacal to check on the board, it says that it no longer sees the board and has us remove it from the list. The only way to undo this is to cycle power to the 1608FS and add it back to the board list after Instacal detects it again. I've tried installing a replacement board, but it's doing the exact same thing. I also noticed that the registry update that's typically required for new boards happened for the USB-DIO24/37 that's also part of the system setup, but not for the 1608FS. Is there a way to check if this is the issue? And if it's not, what could be the problem? Any help would be greatly appreciated. Thank you! -Bret

Hello @Fausto! Apologies, I thought I had posted this in the correct place. The board was purchased new for this unit, but has otherwise been working correctly. We unfortunately do not have another USB-DIO24/37 to swap it with. The other thing supporting the idea that the output is damaged is that there are several other pins being used by that port (Port A), and they all function as needed. The unit also uses a USB-1608FS-OEM, so I asked the programmer to move that command to an output on there to be able to test further. I also need to make a modification to the amplifier board that output is going to today, so I should be able to try and test that input to see if there's something wrong on the amplifier board's end as well. I've been able to get it to switch correctly on the test rig I have, but that also can provide a great deal more current than the pins on the DIO24/37 can. I'll be able to report back with more info that might help later. Thank you! -Bret

Hello, we're using a USB-DIO24/37 as a controller in a product for an automated process. I've run into an issue where for some reason the pin being used to activate a gain stage on an amplifier board isn't switching. The outputs are all set to be pulled down when not activated, and I usually see the 5V when I turn a point on and off. When I measure the output for the pin controlling the amp board gain though, it only goes to about 70mV. We tried moving the board to a different input that uses a different pin to activate this feature, but it garnered the same result. Furthermore, when I measure this output while not connected to the board, it's still reading about 70mV. This is the first time I've seen this happen in years of using this board like this, and I'm concerned that the output may have been damaged by an issue with the amplifier board. Is it safe to assume this, or is there something I might need to change to revert this? Thank you!

Apologies for the late reply! That was one of the first things I tried on the advice of a coworker, no results. We'll be sending back the board today or later this week, I'm assuming that there's probably just a bad component but it's probably best to have MCC look at it. Thank you again! -Bret

I reinstalled the 32-bit version of the OS, and got the same end result, no recognition. After leaving it with people more familiar with Raspberry Pi hardware and them not being able to get any farther, I think it's time to request an RA # for the board. Oh well. Thank you for the help and info! -Bret

Hello, and thank you for the reply! I was actually able to try a different hat, the MCC 152, and the Pi was able to see it successfully, but I'll try the 32-bit OS as well. I have the board at Address 0 (no jumpers) already, and I've been using the daqhats_read_eeproms command, and it hasn't provided any success, so as mentioned I'll try the 32-bit OS.

Hello, I have an MCC 118 that I'm using with a Raspberry Pi Model B with the 64-bit Raspberry Pi OS installed. I'm trying to set this up in order to test a program that uses it as a signal source, but I'm having an issue with getting the Pi to recognize the hat. I've gone through the entire process at https://mccdaq.github.io/daqhats/install.html, but when I get to the point of either using the MCC DAQ HAT Manager software or the command daqhats_read_eeproms, it never seems to be able to read the board. The command brings back "0 boards found," and the manager doesn't add any hats to the list, and says there's nothing found when I open the ACC 118 app. I have the hat completely pressed in, and the power LED is on, so I think there should be enough of a connection for this to be readable. I've tried it with both no jumpers and one jumper in the A0 position, but I still get the same results. I've also uninstalled and reinstalled the daqhats resources folder, but this changed nothing. Is there something else that I may be missing? Thank you!