@chrishamm pressing the button while it is on?

Thanks for the help!
Xavier

@jay_s_uk the firmware was updated back in the day as it was one of the early cards. Odd that it would now be out of date, maybe it was reset somehow? The commands don't work so maybe I need to do it manually again...?

Cheers,
Xavier

Diagnostics below:

FIRMWARE_NAME: RepRapFirmware for Duet 3 MB6HC v0.6 or 1.0 FIRMWARE_VERSION: 3.0 ELECTRONICS: Duet 3 MB6HC FIRMWARE_DATE: 2020-01-03b3

M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC v0.6 or 1.0 version 3.0 running on Duet 3 MB6HC
Board ID: 08DJM-956L2-G43S8-6J9F0-3SN6Q-9U0YG
Used output buffers: 1 of 32 (4 max)

(can't show the rest or it flags the message as spam )

Hello,

I had to do a clean install on a new SD card, I previously had the Duet3 working with a Pi 4B absolutely fine, however now in DWC it stays at "Status: Starting", doesn't seem to detect my config, probably because it is not starting correctly, and in the diagnostics it looks like I have an incompatible firmware, I have tried updating everything as per the documentation, Pi should be updated fine using the latest DuetPi and then updated just in case, the duet firmware shouldn't have changed, as it was working previously, though I ran the update on that too. What am I missing?

I get this on startup:
Warning: Incompatible firmware, please upgrade as soon as possible
Connection interrupted, attempting to reconnect...
DCS has been stopped

So I have my duet3 up and running with an sbc (rpi 4) and I was wondering, is it possible to connect a speaker to the audio jack on the raspberry pi and use it to reproduce audio files on command? The use case would be to play a specific notification when there is a crash, when there is a print started, ended, filament out sensed etc.

Ok great thanks, one last question, as the ground pin for the probe is already grounded, will I be good to go if I just put the white temp cable into the temp pin, or do I need to duplicate the ground cable to ground via both connectors?

I have been scouring the forum for any advice on using the PINDA 2 probe (with thermistor) with the Duet3, it seems that there are some use cases with previous duet boards but I can't find much regardingthe Duet3. I know that RRF3 supports the use of z probes with thermistor, but I was hoping someone could give advice on wiring and configuration.

Can the IO pins deal with probing and thermistor data, or do I need to spit the wiring into two headers, probing into IO pins and separate thermistor wiring into the temp pins? Do I then need to use M308 to configure a sensor that uses the thermistor, then specify that sensor to provide the temperature compensation in G31?

Thanks!
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

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.

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.