Donk

Ok. I only have one working MCC 152 in house and it's currently being used. I should be able to check some time Monday. I should have a schematic for you by then also. thanks for your help.

Thanks @Nick Wright. The ULN2801 outputs are driving solenoids. Unfortunately, the schematic terminates at a connector without showing the coils. However I'm just using the built in suppression diodes from the ULN2801. The coils are 24VDC. I'm almost done for the day, but if I can find time, would a schematic without the connectors, and showing the coils help? I could probably have one to you on Monday.

No, I'm having problems with RPi 3 B+. Both are in identical systems. The only reason some are RPi 3 is the shortage a few years back. We had spare unused 3's for a different project. The RPi 4 is set to 5V, the chip is very hot, but is still working. The 3's were setup the same way, but I saw Display Names post and decided to see if his suggestions would help. So I changed to 3.3 (seeing the open collector outputs won't care either way) Digital in's are open collector, internal pull up (internal to MCC-152). Thanks donk

Hi again, I now have two more bad MCC-152s on my desk since I asked this question. This is the same machine as the previous post. I seem to be having a similar issue to what is described here. The i2c expander is getting red hot when W3 is set to 5v. I did change to 3.3v which seemed to slow down the failure, but I may have already weakened the chip by overheating before changing to 3.3. I currently use 3 inputs and 4 outputs. The outputs are sent directly to a ULN2801. Two of the inputs are connected to the open collector outputs of a LM393 comparator. The other to an open collector opto-isolator. The inputs are set as pull up, only internal pull ups are used. I also notice an oddity when polling the inputs, but I can't determine any pattern causing it's occurrence, all the digital inputs read high. This is physically impossible, a spare unused input tied low also reads high. The only way to "clear" this is to toggle an output. I'm working around this now, but I am wondering is it somehow related. I also have an identical system, except using a Pi 4, which hasn't exhibited the problem. Thanks

Fausto, Thanks. Nothing worked. Found a spare MCC152 and everything worked. The board in question is in the garbage. thanks again, donk

Good Morning, As requested $ cat /etc/os-release PRETTY_NAME="Raspbian GNU/Linux 11 (bullseye)" NAME="Raspbian GNU/Linux" VERSION_ID="11" VERSION="11 (bullseye)" VERSION_CODENAME=bullseye ID=raspbian ID_LIKE=debian HOME_URL="http://www.raspbian.org/" SUPPORT_URL="http://www.raspbian.org/RaspbianForums" BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs" $ cat /proc/cpuinfo | grep Model Model : Raspberry Pi 3 Model B Plus Rev 1.3

I'm leaving for the weekend, but SPI and I2C are enabled. Yes both were installed previously, and worked. Thanks, donk

pi@afspi02:~$ sudo daqhats_read_eeproms Reading... Found EEPROM at address 0 Found EEPROM at address 1 Done pi@afspi02:~$ uname -a Linux afspi02 6.1.21-v7+ #1642 SMP Mon Apr 3 17:20:52 BST 2023 armv7l GNU/Linux pi@afspi02:~$ cat /etc/debian_version 11.8 The open button on the MCC 152 window does nothing. It does work for the MCC128. When running my application I get the error code "Could not communicate with the device."

I have an MCC152, that previously worked. I ran an update yesterday. SPI is still on, I2C is off, Today I get the error "Can't Open MCC152". The board is detected, and the eeprom can be read. Is it toast, or is there something else I should check?