Jump to content

dime-ler

Members
  • Posts

    3
  • Joined

  • Last visited

dime-ler's Achievements

Newbie

Newbie (1/4)

0

Reputation

  1. Here's what I get when I run the above code: pi@telpi4:~ $ python mcc134.py Addr 0: Board not responding.
  2. Here are the outputs of both commands: pi@raspberrypi:~ $ sudo daqhats_read_eeproms Reading... Found EEPROM at address 0 Done pi@raspberrypi:~ $ sudo daqhats_list_boards Found 1 board(s): Address: 0 Type: MCC 134 Hardware version: 1 Name: MCC 134 Thermocouple Input HAT
  3. I have a MCC134 HAT connected to a Raspberry Pi 4 running 64-bit Raspberry Pi OS Bullseye. The address pins on the MCC134 board are not jumped to place the board in "address 0" mode. I have ensured the latest SW is installed on the Pi, and have installed the daqhats library as recommended in the daqhats GitHub README. I have also confirmed SPI & I2C are enabled on the Pi. When trying to run the following Python script: from daqhats.mcc134 import mcc134 from daqhats.hats import hat_list print(hat_list()) m = mcc134(0) I get the following output: HatInfo(address=0, id=323, version=1, product_name='MCC 134 Thermocouple Input HAT')] Traceback (most recent call last): File "/home/pi/code/ctp-automation/main.py", line 6, in <module> m = mcc134(0) File "/home/pi/code/ctp-automation/daqhats/mcc134.py", line 121, in __init__ raise HatError(self._address, "Board not responding.") daqhats.hats.HatError: Addr 0: Board not responding the library can read the HAT installed and can recognize that it is a MCC 134 Thermocouple Input HAT, but is unable to open the board for communication. One suggestion I've seen for MCC 118 boards with this issue is to update the firmware, but there is no firmware for the MCC 134 listed along with firmware for the other boards in the daqhats GitHub. Any troubleshooting help is appreciated.
×
×
  • Create New...