Jump to content
  • 0

MCC 134 Board Not Responding



I've got two MCC134's and I can't get either one of them to work individually or together. When I run sudo daqhats_read_eeproms it finds the boards just fine. Then when I run the MCC manager and ask it to list devices, it lists them correctly. However, when I click on open, nothing happens and I get an error that says board not responding. I've updated everything. I have no other boards installed. When using one MCC134 it's set to 0 and when trying both boards together, I had one at 0 and the other at 1 for addresses. I am using a Raspberry Pi touch screen display. I also have SPI and I2C activated. Looking for ideas????

Link to comment
Share on other sites

6 answers to this question

Recommended Posts

  • 0

Hello @ekettle.

Which Raspberry Pi module and touch screen display models are you using?

Which OS are you using?

Disconnect the touch screen display and connect an external monitor to the HDMI port.  Retest the MCC 134 boards work with the MCC DAQ HAT Manager.

(NOTE:  LCD displays that use the GPIO header (not HDMI) usually use the SPI interface and will prevent the DAQ HATs from working. Even if the display is removed, the driver is probably still loaded by /boot/config.txt and will cause issues with the DAQ HATs. If you have a problem with your device and have used a GPIO header display with your Raspberry Pi then consult your display hardware documentation for how to remove the driver.)




Link to comment
Share on other sites

  • 0

I'm using a Raspberry Pi 3 Model B+. The touch screen is the Raspberry Pi Touch Display. The display connects to the Pi via ribbon cable that connects to the DSI port. It only uses power from the GPIO port.

I'm running the Raspbian OS Version 11.

Even if I don't connect the display and just VNC into the Pi, the MCC 134 boards give the same error.

This is what is in my /boot/config.txt

# For more options and information see
# http://rpf.io/configtxt
# Some settings may impact device functionality. See link above for details

# uncomment if you get no picture on HDMI for a default "safe" mode

# uncomment the following to adjust overscan. Use positive numbers if console
# goes off screen, and negative if there is too much border

# uncomment to force a console size. By default it will be display's size minus
# overscan.

# uncomment if hdmi display is not detected and composite is being output

# uncomment to force a specific HDMI mode (this will force VGA)

# uncomment to force a HDMI mode rather than DVI. This can make audio work in
# DMT (computer monitor) modes

# uncomment to increase signal to HDMI, if you have interference, blanking, or
# no display

# uncomment for composite PAL

#uncomment to overclock the arm. 700 MHz is the default.

# Uncomment some or all of these to enable the optional hardware interfaces

# Uncomment this to enable infrared communication.

# Additional overlays and parameters are documented /boot/overlays/README

# Enable audio (loads snd_bcm2835)

# Automatically load overlays for detected cameras

# Automatically load overlays for detected DSI displays

# Enable DRM VC4 V3D driver

# Disable compensation for displays with overscan

# Enable host mode on the 2711 built-in XHCI USB controller.
# This line should be removed if the legacy DWC2 controller is required
# (e.g. for USB device mode) or if USB support is not required.


# Run as fast as firmware / board allows




Link to comment
Share on other sites

  • 0


The offending line in my /boot/config.txt seems to be


No idea what it does, but when I comment it out, my MCC134 boards start working.

Edited by ekettle
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Create New...