Duet 3 Mini + RPI4 + Touchscreen HDMI 7"

greeno76

Hi,

I've successfully set-up my new Duet3 mini with a Raspberry Pi 4 and all seemed to be working fine. I'm excited to install this control system into a new CNC router asap (I have a Duet2 wifi in my 3D printer which works beautifully).

This evening I've added the Waveform 7" HDMI touchscreen and I'm now getting the error, "Failed to connect to Duet3.home. Failed to connect to Duet, please check your connection (DCS is not started)".

I've searched the forums for similar issues but I haven't found anything yet. I've run the command, "sudo journalctl -u duetcontrolserver -e" which gave the following log.

Feb 15 19:00:51 duet3 systemd[1]: Starting Duet Control Server...
Feb 15 19:00:52 duet3 DuetControlServer[8331]: Duet Control Server v3.3.0
Feb 15 19:00:52 duet3 DuetControlServer[8331]: Written by Christian Hammacher for Duet3D
Feb 15 19:00:52 duet3 DuetControlServer[8331]: Licensed under the terms of the GNU Public License Version 3
Feb 15 19:00:53 duet3 DuetControlServer[8331]: [info] Settings loaded
Feb 15 19:00:53 duet3 DuetControlServer[8331]: [info] Environment initialized
Feb 15 19:00:53 duet3 DuetControlServer[8331]: [fatal] Could not connect to Duet (Error 16. Cannot put line into event mode.)
Feb 15 19:00:53 duet3 systemd[1]: duetcontrolserver.service: Failed with result 'protocol'.
Feb 15 19:00:53 duet3 systemd[1]: Failed to start Duet Control Server.
Feb 15 19:00:53 duet3 systemd[1]: duetcontrolserver.service: Service RestartSec=100ms expired, scheduling restart.
Feb 15 19:00:53 duet3 systemd[1]: duetcontrolserver.service: Scheduled restart job, restart counter is at 692.
Feb 15 19:00:53 duet3 systemd[1]: Stopped Duet Control Server.
Feb 15 19:00:53 duet3 systemd[1]: Starting Duet Control Server...
Feb 15 19:00:53 duet3 DuetControlServer[8369]: Duet Control Server v3.3.0
Feb 15 19:00:53 duet3 DuetControlServer[8369]: Written by Christian Hammacher for Duet3D
Feb 15 19:00:54 duet3 DuetControlServer[8369]: Licensed under the terms of the GNU Public License Version 3
Feb 15 19:00:54 duet3 DuetControlServer[8369]: [info] Settings loaded

There is clearly an error in there ( "Could not connect to Duet (Error 16. Cannot put line into event mode.") but I don't know how to overcome it. Can anyone help me, please? Is there a code / pin conflict going on?

Any help appreciated!

Many thanks, Jason (UK)

Phaedrux

How are you powering the Duet, the Pi and the touchscreen?

chrishamm

@greeno76 Did you have to change anything on the stock DuetPi image to get the touchscreen working (provided you're using that)? It sounds like there is a conflict with some peripheral device that prevents DSF from accessing a required GPIO pin, hence the error message. The output of sudo gpioinfo may provide extra information about potential programs interfering with it.

greeno76

Thanks both for kindly replying.

Regarding the power, the Pi4 has its own Raspberry Pi branded power supply. The 7" HDMI touchscreen is powered via USB to the Raspberry Pi.

The Duet3 mini is powered by it's own USB supply. Jumpers haven't been changed so should be in their default potision. The board is not yet connected to any motors or sensors. I've only had it running with the RPi for testing and basic config purposes so far.

The RPi also has a camera connected via the Camera interface running mpeg-streamer. This was running fine along with DCS before the HDMI screen was installed.

The RPi is running the 3.3 version software as you can see in the output above. It's the Duet IMG downloaded from the official repo. I haven't altered it, aside from running apt-get update/upgrade, installing mpeg-streamer and now sudo ./ LCD7-1024x600-show X, which I think appends the config.txt file with the HDMI info in the root filesystem.

FYI, Touchscreen is this one: Link to HDMI on Pi Hut. Here's the manual for the screen for reference.
7inch_HDMI_LCD_User_Manual_EN.pdf

I've copied the output from sudo gpioinfo below. I'm not sure how to interpret it. Perhaps you can see some conflicted pins here?

pi@duet3:~ $ gpioinfo
gpiochip0 - 58 lines:
        line   0:     "ID_SDA"       unused   input  active-high
        line   1:     "ID_SCL"       unused   input  active-high
        line   2:       "SDA1"       unused   input  active-high
        line   3:       "SCL1"       unused   input  active-high
        line   4:  "GPIO_GCLK"       unused   input  active-high
        line   5:      "GPIO5"       unused   input  active-high
        line   6:      "GPIO6"       unused   input  active-high
        line   7:  "SPI_CE1_N"   "spi0 CS1"  output   active-low [used]
        line   8:  "SPI_CE0_N"   "spi0 CS0"  output   active-low [used]
        line   9:   "SPI_MISO"       unused   input  active-high
        line  10:   "SPI_MOSI"       unused   input  active-high
        line  11:   "SPI_SCLK"       unused   input  active-high
        line  12:     "GPIO12"       unused   input  active-high
        line  13:     "GPIO13"       unused   input  active-high
        line  14:       "TXD1"       unused   input  active-high
        line  15:       "RXD1"       unused   input  active-high
        line  16:     "GPIO16"       unused   input  active-high
        line  17:     "GPIO17"       unused   input  active-high
        line  18:     "GPIO18"       unused   input  active-high
        line  19:     "GPIO19"       unused   input  active-high
        line  20:     "GPIO20"       unused   input  active-high
        line  21:     "GPIO21"       unused   input  active-high
        line  22:     "GPIO22"       unused   input  active-high
        line  23:     "GPIO23"       unused   input  active-high
        line  24:     "GPIO24"       unused   input  active-high
        line  25:     "GPIO25" "ads7846_pendown" input active-high [used]
        line  26:     "GPIO26"       unused   input  active-high
        line  27:     "GPIO27"       unused   input  active-high
        line  28: "RGMII_MDIO"       unused   input  active-high
        line  29:  "RGMIO_MDC"       unused   input  active-high
        line  30:       "CTS0"       unused   input  active-high
        line  31:       "RTS0"       unused   input  active-high
        line  32:       "TXD0"       unused   input  active-high
        line  33:       "RXD0"       unused   input  active-high
        line  34:    "SD1_CLK"       unused   input  active-high
        line  35:    "SD1_CMD"       unused   input  active-high
        line  36:  "SD1_DATA0"       unused   input  active-high
        line  37:  "SD1_DATA1"       unused   input  active-high
        line  38:  "SD1_DATA2"       unused   input  active-high
        line  39:  "SD1_DATA3"       unused   input  active-high
        line  40:  "PWM0_MISO"       unused   input  active-high
        line  41:  "PWM1_MOSI"       unused   input  active-high
        line  42: "STATUS_LED_G_CLK" "led0" output active-high [used]
        line  43: "SPIFLASH_CE_N" unused input active-high
        line  44:       "SDA0"       unused   input  active-high
        line  45:       "SCL0"       unused   input  active-high
        line  46: "RGMII_RXCLK" unused input active-high
        line  47: "RGMII_RXCTL" unused input active-high
        line  48: "RGMII_RXD0"       unused   input  active-high
        line  49: "RGMII_RXD1"       unused   input  active-high
        line  50: "RGMII_RXD2"       unused   input  active-high
        line  51: "RGMII_RXD3"       unused   input  active-high
        line  52: "RGMII_TXCLK" unused input active-high
        line  53: "RGMII_TXCTL" unused input active-high
        line  54: "RGMII_TXD0"       unused   input  active-high
        line  55: "RGMII_TXD1"       unused   input  active-high
        line  56: "RGMII_TXD2"       unused   input  active-high
        line  57: "RGMII_TXD3"       unused   input  active-high
gpiochip1 - 8 lines:
        line   0:      "BT_ON"       unused  output  active-high
        line   1:      "WL_ON"       unused  output  active-high
        line   2: "PWR_LED_OFF" "led1" output active-low [used]
        line   3: "GLOBAL_RESET" unused output active-high
        line   4: "VDD_SD_IO_SEL" "vdd-sd-io" output active-high [used]
        line   5:   "CAM_GPIO"       unused  output  active-high
        line   6:  "SD_PWR_ON" "sd_vcc_reg"  output  active-high [used]
        line   7:    "SD_OC_N"       unused   input  active-high

I'm a bit stuck. Is it worth me trying to reinstall the Duet software?

Once again, any help is hugely appreciated.

Thanks again,

Jason

Phaedrux

@greeno76 said in Duet 3 Mini + RPI4 + Touchscreen HDMI 7":

The 7" HDMI touchscreen is powered via USB to the Raspberry Pi.

The only thing I would try changing would be powering the display from it's own supply as well.

greeno76

Hi,

Thanks for your suggestion. I tried separate power supplies for all devices but unfortunately the issue still persisted.

Given that this is an as-yet unconnected system I've simply started from scratch and reinstalled the DuetPi img. The Duet3 mini board has successfully connected. I have since configured the HDMI touchscreen and Camera and the Duet3 is still connecting fine.

So, I'm not sure what I learned there!, Slightly concerning but hopefully it'll be fine if I don't meddle too much and I can go ahead and start wiring-up and configuring the CNC.

Many thanks for your replies.

Best wishes,

Jason

Phaedrux

So you started with the DuetPi image that came on the SD card and reflashing the SD card with a fresh image solved it?

greeno76

@phaedrux I should clarify in case its misleading for anyone in the future.

The original DuetPi image was downloaded from the official GitHub location as was the last install which appeared to solve my problem.

I think I must have bodged the HDMI screen installation tbh. I ran some install command but really it just needed to be configured in config.txt.

All seems to be working now. I've since upgraded to the 3.4 RC and I've successfully tested motion on the stepper motors.

Thanks again.

Jason