DCS Not Started
-
Hello all,
I am currently having issues with my Duet3D Mini 5+ of trying to set-up the SBC, showing this error trying to connect.
Hardware being used:
- Duet3D Mini 5+
- Raspberry Pi 3 Model B+
- Elecrow 5" Touch Screen
Set-Up
I have flashed the DuetPi.zip to the Raspberry and I am able to connect to my wifi network successfully to the Duet Web Control. I made sure there is no SD card in the Duet Mini. Both Raspberry and Duet have their own separate power supply. I also made sure the ribbon is ok with a multimeter and checked the firmware to make sure it is up to date
I browsed through the forums a bit tried diagnosing and tried using
$ sudo journalctl -u duetcontrolserver -ewith this result...pi@duet3:~ $ sudo journalctl -u duetcontrolserver -e Jan 21 12:02:06 duet3 DuetControlServer[3370]: Licensed under the terms of the GNU Public License Jan 21 12:02:08 duet3 DuetControlServer[3370]: [info] Settings loaded Jan 21 12:02:08 duet3 DuetControlServer[3370]: [info] Environment initialized Jan 21 12:02:08 duet3 DuetControlServer[3370]: [fatal] Could not connect to Duet (Error 16. Cannot put line into Jan 21 12:02:08 duet3 systemd[1]: duetcontrolserver.service: Failed with result 'protocol'. Jan 21 12:02:08 duet3 systemd[1]: Failed to start Duet Control Server. Jan 21 12:02:09 duet3 systemd[1]: duetcontrolserver.service: Service RestartSec=100ms expired, sch Jan 21 12:02:09 duet3 systemd[1]: duetcontrolserver.service: Scheduled restart job, restart counte Jan 21 12:02:09 duet3 systemd[1]: Stopped Duet Control Server. Jan 21 12:02:09 duet3 systemd[1]: Starting Duet Control Server... Jan 21 12:02:09 duet3 DuetControlServer[3402]: Duet Control Server v3.3.0 Jan 21 12:02:09 duet3 DuetControlServer[3402]: Written by Christian Hammacher for Duet3D Jan 21 12:02:09 duet3 DuetControlServer[3402]: Licensed under the terms of the GNU Public License Jan 21 12:02:11 duet3 DuetControlServer[3402]: [info] Settings loaded Jan 21 12:02:11 duet3 DuetControlServer[3402]: [info] Environment initialized Jan 21 12:02:11 duet3 DuetControlServer[3402]: [fatal] Could not connect to Duet (Error 16. Cannot put line into Jan 21 12:02:11 duet3 systemd[1]: duetcontrolserver.service: Failed with result 'protocol'. Jan 21 12:02:11 duet3 systemd[1]: Failed to start Duet Control Server. Jan 21 12:02:12 duet3 systemd[1]: duetcontrolserver.service: Service RestartSec=100ms expired, sch Jan 21 12:02:12 duet3 systemd[1]: duetcontrolserver.service: Scheduled restart job, restart counte Jan 21 12:02:12 duet3 systemd[1]: Stopped Duet Control Server. Jan 21 12:02:12 duet3 systemd[1]: Starting Duet Control Server...Running out of ideas what to do or look for, any help will be appreciated
-
@kzobarlow I suggest you flash the DuetPi image once again to your microSD card. It seems like something blocks access to the TfrRdy pin which is why you get Error 16 in the DCS log.
-
I have tried this which worked having both boards by itself. But once I plugged everything up to the 3D printer I got the same error. I separated the board and pi once again then flashed the pi but now still getting the error again....
-
@kzobarlow Hi, I had the same error when I first set up my Duet 3 5+ mini with a Pi.
I had the ribbon cable plugged backwards into the Duet, which was possible since the connector doesn't have a indexing indentation. Double-check against the online documentation for the 6HC that the ribbon cable is plugged in correctly, e.g. the position of the red wire is important.
Once I had it correct everything came together without further issues. -
Seeing the mini has a key slot I don't see how it's possible to plug it in incorrectly?
image url)I made sure the red band on the cable seats on the bottom row of the pi as well
-
Do you have a different pi to test with?
-
@kzobarlow sorry, must have remembered wrongly. I might have had the cable plugged in backwards to the Pi but that doesn't seem the case with your setup.
-
not on hand but may try it at this point
-
Upgraded/Changed to a Raspberry Pi 4 Model B and still getting the same error as before....
Edit:
SD Card was re flashed before doing anything -
Thanks for testing with a new Pi. Can you confirm that you reflashed with the latest Duet Pi image download?
If you enable logging again do you get the same errors?
-
Hello,
Yes SD card was re-flashed with the latest image
This is what I got running
$ sudo journalctl -u duetcontrolserver -epi@duet3:~ $ sudo journalctl -u duetcontrolserver -e Jan 31 19:48:24 duet3 DuetControlServer[10320]: [fatal] Could not connect to Due Jan 31 19:48:24 duet3 systemd[1]: duetcontrolserver.service: Failed with result Jan 31 19:48:24 duet3 systemd[1]: Failed to start Duet Control Server. Jan 31 19:48:24 duet3 systemd[1]: duetcontrolserver.service: Service RestartSec= Jan 31 19:48:24 duet3 systemd[1]: duetcontrolserver.service: Scheduled restart j Jan 31 19:48:24 duet3 systemd[1]: Stopped Duet Control Server. Jan 31 19:48:24 duet3 systemd[1]: Starting Duet Control Server... Jan 31 19:48:25 duet3 DuetControlServer[10354]: Duet Control Server v3.3.0 Jan 31 19:48:25 duet3 DuetControlServer[10354]: Written by Christian Hammacher f Jan 31 19:48:25 duet3 DuetControlServer[10354]: Licensed under the terms of the Jan 31 19:48:25 duet3 DuetControlServer[10354]: [info] Settings loaded Jan 31 19:48:25 duet3 DuetControlServer[10354]: [info] Environment initialized Jan 31 19:48:26 duet3 DuetControlServer[10354]: [fatal] Could not connect to Due Jan 31 19:48:26 duet3 systemd[1]: duetcontrolserver.service: Failed with result Jan 31 19:48:26 duet3 systemd[1]: Failed to start Duet Control Server. Jan 31 19:48:26 duet3 systemd[1]: duetcontrolserver.service: Service RestartSec= Jan 31 19:48:26 duet3 systemd[1]: duetcontrolserver.service: Scheduled restart j Jan 31 19:48:27 duet3 systemd[1]: Stopped Duet Control Server. Jan 31 19:48:27 duet3 systemd[1]: Starting Duet Control Server... Jan 31 19:48:28 duet3 DuetControlServer[10387]: Duet Control Server v3.3.0 Jan 31 19:48:28 duet3 DuetControlServer[10387]: Written by Christian Hammacher f Jan 31 19:48:28 duet3 DuetControlServer[10387]: Licensed under the terms of the lines 980-1001/1001 (END) -
Have you tested the Duet in standalone mode to see if it's otherwise functional? What firmware is flashed on it?
Is the touch screen powered by it's own supply?
-
@kzobarlow Please use
journalctl -u duetcontrolserver -e --no-pagerbecause the error mesage is truncated. If it is the same "Cannot put line into event mode" error message (also truncated before), it indicates that something keeps blocking a required GPIO pin.If this is the case, please run the following commands:
sudo systemctl stop duetcontrolserver sudo gpioinfoIf you get an error invoking
gpioinfo, try installinggpiod(sudo apt install gpiod) first. The line starting withline 25shows you which program blocks access to the GPIO pin.Duet software engineer
-
Yes I tested it without the Pi connected and was able to interact with it through my browser
The touch screen is powered by the pi but I switched to a PC monitor powered independently so I can see the terminal screen better but still have the same problem
-
Result from
journalctl -u duetcontrolserver -e --no-pagereb 01 21:08:04 duet3 DuetControlServer[21900]: Duet Control Server v3.3.0 Feb 01 21:08:04 duet3 DuetControlServer[21900]: Written by Christian Hammacher for Duet3D Feb 01 21:08:04 duet3 DuetControlServer[21900]: Licensed under the terms of the GNU Public License Version 3 Feb 01 21:08:05 duet3 DuetControlServer[21900]: [info] Settings loaded Feb 01 21:08:05 duet3 DuetControlServer[21900]: [info] Environment initialized Feb 01 21:08:06 duet3 DuetControlServer[21900]: [fatal] Could not connect to Duet (Timeout while waiting for transfer ready pin) Feb 01 21:08:06 duet3 systemd[1]: duetcontrolserver.service: Failed with result 'protocol'. Feb 01 21:08:06 duet3 systemd[1]: Failed to start Duet Control Server. Feb 01 21:08:06 duet3 systemd[1]: duetcontrolserver.service: Service RestartSec=100ms expired, scheduling restart. Feb 01 21:08:06 duet3 systemd[1]: duetcontrolserver.service: Scheduled restart job, restart counter is at 623. Feb 01 21:08:06 duet3 systemd[1]: Stopped Duet Control Server. Feb 01 21:08:06 duet3 systemd[1]: Starting Duet Control Server...After tying this
sudo systemctl stop duetcontrolserver sudo gpioinfopi@duet3:~ $ sudo 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" unused input active-high 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 pi@duet3:~ $ ^CIf I'm seeing this right... I don't see anything that's tied to 25?
-
@kzobarlow That's a different error message now. Please ensure you do not have a microSD card in the Duet.
-
No SD card is present in the Duet Mini board
-
So again.... if I'm seeing this right "GPIO25" reads unused still and unless I'm missing something don't see anything getting blocked?
-
@kzobarlow Does the DIAG LED on the Duet blink or is it dimmed? Do you have firmware 3.3 installed on the board? If in doubt, you can flash it again. You can find firmware version 3.3 here ( Duet3Firmware_Mini5plus.uf2).
If you have a multimeter, you can also check continuity between pin 22 of the Pi and Duet. When you're at it, you could check pin 17 as well, because that signal is required for SPI comms, too.
-
Still getting DCS Error...
"Does the DIAG LED on the Duet blink or is it dimmed?"
- Not sure which one that is, looking at the wiring diagram LED V FUSED and LED 12V are the only ones active and showing a solid light.
- All other lights LED ACT, LED STATUS, LED +5V, and LED +3.3V do not turn on even during powering on the PSU
- Again Pi is powered by an independent 5V PSU and Mini is powered by a 24 PSU
"Do you have firmware 3.3 installed on the board?"
- Yes checked with M115
- Reflashed using Fallback procedure #1 and Fallback procedure #2
- SD Card was removed after confirming again with YAT RRF is up to date
"If you have a multimeter, you can also check continuity between pin 22 of the Pi and Duet. When you're at it, you could check pin 17 as well, because that signal is required for SPI comms, too."
- Checked with a multimeter and continuity is fine for both pins
Trying terminal again
Feb 06 22:19:30 duet3 DuetControlServer[4022]: Duet Control Server v3.3.0 Feb 06 22:19:30 duet3 DuetControlServer[4022]: Written by Christian Hammacher for Duet3D Feb 06 22:19:30 duet3 DuetControlServer[4022]: Licensed under the terms of the GNU Public License Version 3 Feb 06 22:19:30 duet3 DuetControlServer[4022]: [info] Settings loaded Feb 06 22:19:31 duet3 DuetControlServer[4022]: [info] Environment initialized Feb 06 22:19:31 duet3 DuetControlServer[4022]: [fatal] Could not connect to Duet (Timeout while waiting for transfer ready pin) Feb 06 22:19:31 duet3 systemd[1]: duetcontrolserver.service: Failed with result 'protocol'. Feb 06 22:19:31 duet3 systemd[1]: Failed to start Duet Control Server. Feb 06 22:19:32 duet3 systemd[1]: duetcontrolserver.service: Service RestartSec=100ms expired, scheduling restart. Feb 06 22:19:32 duet3 systemd[1]: duetcontrolserver.service: Scheduled restart job, restart counter is at 87. Feb 06 22:19:32 duet3 systemd[1]: Stopped Duet Control Server. Feb 06 22:19:32 duet3 systemd[1]: Starting Duet Control Server... ----------------------------------------------------------------------------------- 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" unused input active-high 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 -------------------------------------------------------------------------
