"Failed to connect to duet3" via Pi4 SBC

Xavier

So I have decided to use my Pi4 to connect to my duet3, and followed this guide:
https://duet3d.dozuki.com/Wiki/SBC_Setup_for_Duet_3

I have imaged a new good quality SD card with this image via etcher and inserted it into the Pi4:
https://pkg.duet3d.com/DuetPi.zip

Both the Pi and the Duet are connected to their own power supplies, and the ribbon cable is correctly connected and firmly seated.

When I power up the devices, I see it all load up on the screen directly connected to the Pi via HDMI, once the OS is loaded it opens the browser as expected with DWC also as expected, however as DWC loads it shows the connection bar trying to connect forever and at the bottom right gives me an error message saying "Failed to connect to duet3 DCS is unavailable".

I have tested opening google on the browser and it works so internet connectivity shouldn't be the issue.

Thanks in advance for the assistance!
Cheers,
Xavier

A Former User

has the duet been used stand alone before, and updated? the default image will likely not update to the latest software to be compatible with the latest firmware.

change to the unstable package list or downgrade firmware perhaps?

Xavier

Thanks for the response bearer!

So the duet was setup a couple of days ago to run standalone, and I was able to connect properly and updated to the latest firmware (RC6).

What would you suggest given this?

A Former User

honestly, no idea what the best option is, suggest you check out the threads detailing the RC5 and RC6 releases and the associated issues.

chrishamm

@Xavier Please open a terminal and type sudo journalctl -u duetcontrolserver -e. It looks like the core component of the Raspi software for communication to the Duet 3 did not start.

A Former User

if hes on a fresh duetpi image with the stable list ( i.e dsf 1.2.4) and RC6 firmware wouldn't that be an issue?

Xavier

This is the output:

Apr 08 22:04:10 duet3 DuetControlServer[1568]: [info] Environment initialized
Apr 08 22:04:10 duet3 DuetControlServer[1568]: [error] Duet is not available
Apr 08 22:04:10 duet3 systemd[1]: duetcontrolserver.service: Succeeded.
Apr 08 22:04:15 duet3 systemd[1]: duetcontrolserver.service: Service RestartSec=5s expired, scheduling restart.
Apr 08 22:04:15 duet3 systemd[1]: duetcontrolserver.service: Scheduled restart job, restart counter is at 16.
Apr 08 22:04:15 duet3 systemd[1]: Stopped Duet Control Server.
Apr 08 22:04:15 duet3 systemd[1]: Started Duet Control Server.
Apr 08 22:04:16 duet3 DuetControlServer[1584]: Duet Control Server v1.2.4.0
Apr 08 22:04:16 duet3 DuetControlServer[1584]: Written by Christian Hammacher for Duet3D
Apr 08 22:04:16 duet3 DuetControlServer[1584]: Licensed under the terms of the GNU Public License Version 3
Apr 08 22:04:16 duet3 DuetControlServer[1584]: [info] Settings loaded
Apr 08 22:04:17 duet3 DuetControlServer[1584]: [info] Environment initialized
Apr 08 22:04:17 duet3 DuetControlServer[1584]: [error] Duet is not available
Apr 08 22:04:17 duet3 systemd[1]: duetcontrolserver.service: Succeeded.
Apr 08 22:04:22 duet3 systemd[1]: duetcontrolserver.service: Service RestartSec=5s expired, scheduling restart.
Apr 08 22:04:22 duet3 systemd[1]: duetcontrolserver.service: Scheduled restart job, restart counter is at 17.
Apr 08 22:04:22 duet3 systemd[1]: Stopped Duet Control Server.
Apr 08 22:04:22 duet3 systemd[1]: Started Duet Control Server.
Apr 08 22:04:23 duet3 DuetControlServer[1599]: Duet Control Server v1.2.4.0
Apr 08 22:04:23 duet3 DuetControlServer[1599]: Written by Christian Hammacher for Duet3D
Apr 08 22:04:23 duet3 DuetControlServer[1599]: Licensed under the terms of the GNU Public License Version 3
Apr 08 22:04:23 duet3 DuetControlServer[1599]: [info] Settings loaded
Apr 08 22:04:24 duet3 DuetControlServer[1599]: [info] Environment initialized
Apr 08 22:04:24 duet3 DuetControlServer[1599]: [error] Duet is not available
Apr 08 22:04:24 duet3 systemd[1]: duetcontrolserver.service: Succeeded.
Apr 08 22:04:29 duet3 systemd[1]: duetcontrolserver.service: Service RestartSec=5s expired, scheduling restart.
Apr 08 22:04:29 duet3 systemd[1]: duetcontrolserver.service: Scheduled restart job, restart counter is at 18.
Apr 08 22:04:29 duet3 systemd[1]: Stopped Duet Control Server.
Apr 08 22:04:29 duet3 systemd[1]: Started Duet Control Server.

Danal

V3 RC6 software in the flash on the Duet board should work just fine. You've verified the physical setup, let's check some other basics:
From the first post:
@Xavier said in "Failed to connect to duet3" via Pi4 SBC:
Both the Pi and the Duet are connected to their own power supplies
For now, for debugging, disconnect the Pi power supply and move the jumpers to the default configuration. That is, per the Dozuki instructions, allow the Pi to be powered from the Duet. You can change it to your desired configuration later.
NO SD CARD in the Duet board itself. Socket must be empty (this is not 100% true, but go with it for now, for debugging)
Pi was built with the image, AND the post-install steps were executed. These steps are all on the Dozuki, but it covers a lot of options so I made myself a "just do it this way" instruction sheet, please use it as a verification checklist:

# Get your Pi booted and on your network:

# Download image (not lite) from https://duet3d.dozuki.com/Wiki/Getting_Started_With_Duet_3#Section_DuetPi
# Do not unzip it. 
# Etch image to SD card. (search google for balena etcher) 
# Ignore windows error messages for the next drive letter after your SD.  DO NOT format. 
# On the SD card, edit wpa_supplicant.conf for your network
# On the SD card, create a file named 'ssh'.  Empty is fine. 

# Insert SD in Pi and power up. First boot takes an extra minute or two. 
# Find IP address (varies a lot by router)  or try "duet3.local"
# From your PC, enter:
ssh pi@x.x.x.x

# Default password is raspberry  CHANGE IT after you connect for the first time!
# From the Pi command prompt:
passwd

#You now have a running Pi, but it is not completely built 
# to run a Duet 3 printer yet. 

#Set up OS options for Duet Software Framework:
sudo raspi-config 
# Navigate to 5 interface options, then P4 SPI, and 5 again, P3 VNC
# Verify via 
ls /dev/spidev* 
# Look for /dev/spidev0.0
# You may also wish to set country, time zone, etc. with raspi-config

# Now complete setup for duetsoftwareframework. 
wget -q https://pkg.duet3d.com/duet3d.gpg
wget -q https://pkg.duet3d.com/duet3d-unstable.list
sudo mv duet3d.gpg /etc/apt/trusted.gpg.d/
sudo mv duet3d-unstable.list /etc/apt/sources.list.d/duet3d-unstable.list
sudo chown root:root /etc/apt/trusted.gpg.d/duet3d.gpg
sudo chown root:root /etc/apt/sources.list.d/duet3d-unstable.list

sudo apt-get update
sudo apt-get install apt-transport-https
sudo apt-get install duetsoftwareframework

# Verify you can connect to DWC via web server. 
# If you have configuration files (config.g, tool macros, etc) use DWC to upload them now. 

# Update the Pi itself:

sudo apt-get update
sudo apt-get upgrade  (this may take 15 to 60 minutes)

# Reboot is not absolutely required... but... 
sudo reboot


#########################################
# End of required install for Duet 3 Pi #
#########################################

A Former User

https://github.com/dc42/RepRapFirmware/blob/v3-dev/WHATS_NEW_RRF3.md#reprapfirmware-301-rc6

Users of Duet 3 with attached SBC should upgrade to DSF 1.3.0 at the same time as upgrading to this release

chrishamm

@Danal said in "Failed to connect to duet3" via Pi4 SBC:

V3 RC6 software in the flash on the Duet board should work just fine. You've verified the physical setup, let's check some other basics:

This is not true unless the latest unstable DSF package is installed. DSF 1.2.x should be used with RRF 3.0 only.

@Xavier I suggest you install RRF 3.0 again and see if that helps. The error message you see indicate that the Duet isn't available at all, i.e. no data could be transmitted over SPI. Please make sure the red led on the Duet 3 blinks in 1s intervals and that the connection between the Duet and the Pi is okay.

dc42

@chrishamm said in "Failed to connect to duet3" via Pi4 SBC:

This is not true unless the latest unstable DSF package is installed. DSF 1.2.x should be used with RRF 3.0 only.

More precisely:

DSF 1.2.5 will work with RRF 3.01-RC5. I think it should also work with all earlier 3.01RC versions, and with 3.0 release (but not with some 3.0beta versions)
DSF 1.3.x and RRF 3.01-RC6 use a modified SPI protocol. However, DSF 1.3.x should work with RRF 3.01-RC5 sufficiently to upgrade it to 3.01-RC6.

A Former User

Maybe OP should just run apt list 2>/dev/null | grep duet and eliminate the guesswork about which version is running.

(If the recommendation is to run from the sable list with DSF 1.2.4 + RRF3.0 and DSF isn't working you can flash the Duet3 with a USB cable and running a script that will build bossac, download the stable version for the Duet (RRF3.0 for the Duet3 at the time of writing) , send the Duet to bootloader and flash it. wget -q https://pastebin.com/raw/wekeLGhS -O - | tr -d '\r' | bash)

edit:
@Xavier said in "Failed to connect to duet3" via Pi4 SBC:

Apr 08 22:04:16 duet3 DuetControlServer[1584]: Duet Control Server v1.2.4.0

dc42

For those Duet 3 + RPi users who don't want to be on the bleeding edge, I suggest DSF 1.2.5 and RRF 3.01-RC5 until DSF 1.3.x/DWC 2.1.x/RRF 3.01-RC6 have settled down.

A Former User

Then maybe 1.2.5 should be published to the stable list? Presently 1.2.4 is the latest. Installing 1.2.5 from the unstable list might not be the simplest task. (But I suppose Alex Horne is encouraging #hometasking..!)

duetsoftwareframework/unstable 1.2.5.0 armhf
duetsoftwareframework/unstable,stable 1.2.4.0 armhf

Xavier

Ok there are a lot of instructions since my last post and I am not entirely sure how to proceed now as a new user, I do not need to be on the bleeding edge as dc42 suggested, I just want it working for the moment.

In case it helps I can confirm the followng:

The Duet has no SD card inserted
I have not touched the jumpers on the duet, so they are where they were when I received the board (Internal 5V jumper and 5V -> SBC jumper inserted)
"apt list 2>/dev/null | grep duet" returns:
duetcontrolserver/stable,now 1.2.4.0 armhf [installed,automatic]
duetruntime/stable,now 1.2.4.0 armhf [installed,automatic]
duetsd/stable,now 1.0.5 all [installed,automatic]
duetsoftwareframework/stable,now 1.2.4.0 armhf [installed]
duettools/stable,now 1.2.4.0 armhf [installed,automatic]
duetwebcontrol/stable,now 2.0.7-1 all [installed,automatic]
duetwebserver/stable,now 1.2.3.1 armhf [installed,automatic]

Also the red light next to the reset is blinking o and off every second.

A Former User

To follow dc42's suggestion, you still need to change to the unstable list to be able to install DSF 1.2.5, and if you update normally it will go to 1.3.x unless we mark the package as held; which you need to undo when you do want to update later - so you'll be on a edge if not the bleeding edge.

To follow chrishamm's suggestion all you need to do is to install RRF 3.0 on the Duet 3 and keep the Pi as is. (But there are various issues with all the older versions, which is why I suggested you read the threads concerning the updates to determine for yourself).

My posts above might help you achieve either option. but the choice is yours. I recon its easier to start with chrishamm's suggestion to install RRF 3.0 and move on to switching to the unstable list and installing DSF1.2.5 as per dc42's suggestion (which should then also update the Duet3 to 3.01-RC5 as part of the process)

Xavier

I just changed firmware to 3.0 and it works! I owe you all a pint of beer

Fantastic support, thanks!

Now let's see what else I can break