ekettle

I'd like to use the included C example Datalogger for two MCC134's and have it display all eight channels at once. I'm not a programmer and I'm wondering if there is an easy way to do that?

@Fausto The offending line in my /boot/config.txt seems to be dtoverlay=mcp2515-can0,oscillator=16000000,interrupt=25 No idea what it does, but when I comment it out, my MCC134 boards start working.

I just tested at the end. I'll go back through though and try lines individually and then reply to this thread.

I commented out anything I thought was related to the display and now it works. Is there a display, other than through HDMI that is compatible?

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 #hdmi_safe=1 # uncomment the following to adjust overscan. Use positive numbers if console # goes off screen, and negative if there is too much border #overscan_left=16 #overscan_right=16 #overscan_top=16 #overscan_bottom=16 # uncomment to force a console size. By default it will be display's size minus # overscan. #framebuffer_width=1280 #framebuffer_height=720 # uncomment if hdmi display is not detected and composite is being output #hdmi_force_hotplug=1 # uncomment to force a specific HDMI mode (this will force VGA) #hdmi_group=1 #hdmi_mode=1 # uncomment to force a HDMI mode rather than DVI. This can make audio work in # DMT (computer monitor) modes #hdmi_drive=2 # uncomment to increase signal to HDMI, if you have interference, blanking, or # no display #config_hdmi_boost=4 # uncomment for composite PAL #sdtv_mode=2 #uncomment to overclock the arm. 700 MHz is the default. #arm_freq=800 # Uncomment some or all of these to enable the optional hardware interfaces dtparam=i2c_arm=on #dtparam=i2s=on dtparam=spi=on # Uncomment this to enable infrared communication. #dtoverlay=gpio-ir,gpio_pin=17 #dtoverlay=gpio-ir-tx,gpio_pin=18 # Additional overlays and parameters are documented /boot/overlays/README # Enable audio (loads snd_bcm2835) dtparam=audio=on # Automatically load overlays for detected cameras camera_auto_detect=1 # Automatically load overlays for detected DSI displays display_auto_detect=1 # Enable DRM VC4 V3D driver dtoverlay=vc4-kms-v3d max_framebuffers=2 # Disable compensation for displays with overscan disable_overscan=1 [cm4] # 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. otg_mode=1 [all] [pi4] # Run as fast as firmware / board allows arm_boost=1 [all] dtoverlay=w1-gpio enable_uart=1 start_x=0 dtoverlay=mcp2515-can0,oscillator=16000000,interrupt=25

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????