Duet3/pi DCS is unavailable after wiring 24V

fractalengineer

@dc42 @bearer

But shouldn't it work anyway on the stable release? RRF 3.0 is known to be working fine on raspberry Pi isn't it?

chrishamm

@fractalengineer Yes it should but in any case that will require a working SPI link between the Duet 3 and your SBC. From the RRF diagnostics I can see that this is not the case.

To be sure: You must not have a SD card in the Duet 3 to use the SBC interface. Are you sure there is none in the Duet?

A Former User

@chrishamm said in Duet3/pi flashing Diag LED after wiring 24V DCS is unavailable:

You must not have a SD card in the Duet 3 to use the SBC interface. Are you sure there is none in the Duet?

thats why I asked him to add the M122 output that shows no sd card.

fractalengineer

@chrishamm

No SD card in the duet 100%; only have one so it’s in the pi

A Former User

anyways, update is live on the unstable package feed; so switch to that and update - fingers crossed

chrishamm

I rather suspect that you have a broken cable or a misconfigured SPI device - you should be seeing at least a few transfers from DSF in the RRF diagnostics. I'll get back to this.

Are you using DuetPi or the stock Raspbian image?

A Former User

The output does indeed look identical to a (correctly configured) Pi without a Duet3 attached. (And yeah, DuetPi image confirmed)

dc42

@fractalengineer, we suspect a problem with either the Duet or the ribbon cable. However we would like you to try with the latest firmware first. @chrishamm is building a new firmware image, and will post to this thread when it is ready.

fractalengineer

@dc42 said in Duet3/pi flashing Diag LED after wiring 24V DCS is unavailable:

@fractalengineer, we suspect a problem with either the Duet or the ribbon cable. However we would like you to try with the latest firmware first. @chrishamm is building a new firmware image, and will post to this thread when it is ready.

Got it; will try the image, thanks to you both for your answer.

I will check continuity on the ribbon in the meantime
Edit: All strands of the ribbon show continuity from one side to the other (tested by probing the sockets pins on the pi and duet)

A Former User

@fractalengineer said in Duet3/pi flashing Diag LED after wiring 24V DCS is unavailable:

I will check continuity on the ribbon in the meantime

measuring could provide enough pressure on pins to make a connection if poorly terminated connector, but still probaly a worth while test given shipping delays everywhere i suppose.

if you have some supplies you can roll your own; i wanted other stuff in there on the pi, but still a single connector on the Duet3 and the power grouped so mine is a little untraditional perhaps. Still 5 signals + 4 power is all you really need, 1:1 straight connection.

(can use a bunch of single wire female-female jumpers as well)

chrishamm

@fractalengineer Please flash RRF 3.01-RC7 using bossa and this image on your SD card using Win32DiskImage or Etcher: https://pkg.duet3d.com/testing/image_2020-04-14-DuetPi.zip When you are done, please start the Pi, connect to it via SSH or open a terminal from an attached monitor, and send sudo journalctl -u duetcontrolserver -e. Once done, please post the output here.

fractalengineer

@chrishamm Hi Chris, thank you for the image; I just completed all the steps, still no luck; same issue.

pi@duet3:~ $ sudo journalctl -u duetcontrolserver -e
Apr 15 02:56:16 duet3 systemd[1]: duetcontrolserver.service: Succeeded.
Apr 15 02:56:21 duet3 systemd[1]: duetcontrolserver.service: Service RestartSec=
Apr 15 02:56:21 duet3 systemd[1]: duetcontrolserver.service: Scheduled restart j
Apr 15 02:56:21 duet3 systemd[1]: Stopped Duet Control Server.
Apr 15 02:56:22 duet3 systemd[1]: Started Duet Control Server.
Apr 15 02:56:22 duet3 DuetControlServer[1737]: Duet Control Server v1.3.2
Apr 15 02:56:22 duet3 DuetControlServer[1737]: Written by Christian Hammacher fo
Apr 15 02:56:22 duet3 DuetControlServer[1737]: Licensed under the terms of the G
Apr 15 02:56:25 duet3 DuetControlServer[1737]: [info] Settings loaded
Apr 15 02:56:25 duet3 DuetControlServer[1737]: [info] Environment initialized
Apr 15 02:56:26 duet3 DuetControlServer[1737]: [fatal] Duet is not available
Apr 15 02:56:26 duet3 systemd[1]: duetcontrolserver.service: Succeeded.
Apr 15 02:56:31 duet3 systemd[1]: duetcontrolserver.service: Service RestartSec=
Apr 15 02:56:31 duet3 systemd[1]: duetcontrolserver.service: Scheduled restart j
Apr 15 02:56:31 duet3 systemd[1]: Stopped Duet Control Server.
Apr 15 02:56:31 duet3 systemd[1]: Started Duet Control Server.
Apr 15 02:56:32 duet3 DuetControlServer[1777]: Duet Control Server v1.3.2
Apr 15 02:56:32 duet3 DuetControlServer[1777]: Written by Christian Hammacher fo
Apr 15 02:56:32 duet3 DuetControlServer[1777]: Licensed under the terms of the G
Apr 15 02:56:35 duet3 DuetControlServer[1777]: [info] Settings loaded
Apr 15 02:56:35 duet3 DuetControlServer[1777]: [info] Environment initialized
Apr 15 02:56:36 duet3 DuetControlServer[1777]: [fatal] Duet is not available
Apr 15 02:56:36 duet3 systemd[1]: duetcontrolserver.service: Succeeded.

@bearer thanks; I probed the pins on the underside of the boards with the ribbon connected; that should validate good continuity through the ribbon and contact in the connectors?

Cheers

A Former User

@fractalengineer said in Duet3/pi flashing Diag LED after wiring 24V DCS is unavailable:

@bearer thanks; I probed the pins on the underside of the boards with the ribbon connected; that should validate good continuity through the ribbon and contact in the connectors?

its hard to say other than "probably" and "maybe". but given the effort already made to troubleshoot i'd think the sensible thing is to replace both.

fractalengineer

@bearer But is it really? I probed the pins directly on the board like so and they all showed continuity; that is the direct signal from one board to another

@chrishamm any feedback on the image result?

Thanks

A Former User

@fractalengineer said in Duet3/pi flashing Diag LED after wiring 24V DCS is unavailable:

But is it really? I probed the pins directly on the board like so and they all showed continuity; that is the direct signal from one board to another

unless the probe exert no force on the board and connector, I'll stick to "probaly", or even "most likely" but at the end of the day it doesn't matter, the cable is a fraction of the cost of the board so just get both replaced for good measure even if its most likely not a cable fault.

Azul

@fractalengineer same problem i just completed the procedure described still no luck

dc42

@fractalengineer, thanks for doing that. We suspect a hardware problem. Please ask your supplier to replace the Duet and ribbon cable under warranty. You may refer your supplier to this post for authorisation.

@Azul, please start a new thread for your issue, explaining what the problem is, what software versions you are using, and what you have tried.

fractalengineer

@dc42 Hi Tony; well ok I bought it directly from Duet, order #7829. Will send a request RMA. Thanks

dc42

@fractalengineer said in Duet3/pi flashing Diag LED after wiring 24V DCS is unavailable:

@dc42 Hi Tony; well ok I bought it directly from Duet, order #7829. Will send a request RMA. Thanks

In that case, see https://www.duet3d.com/warranty for the procedure.

fractalengineer

Hi Again...

So I just received my replacement board and I'm still getting an error

Here's what I did upon opening up the box:

1-Wrote @chrishamm image on the SD card
2-Flashed the board to 3.01 RC7 using Bossa
3-Connected the pi to the board

Here's the error message I get; it's different than last time:

pi@duet3:~ $ sudo journalctl -u duetcontrolserver -e
Apr 23 11:09:06 duet3 DuetControlServer[2500]: Licensed under the terms of the G
Apr 23 11:09:09 duet3 DuetControlServer[2500]: [info] Settings loaded
Apr 23 11:09:09 duet3 DuetControlServer[2500]: [info] Environment initialized
Apr 23 11:09:10 duet3 DuetControlServer[2500]: [fatal] Duet is not available
Apr 23 11:09:10 duet3 systemd[1]: duetcontrolserver.service: Succeeded.
Apr 23 11:09:15 duet3 systemd[1]: duetcontrolserver.service: Service RestartSec=
Apr 23 11:09:15 duet3 systemd[1]: duetcontrolserver.service: Scheduled restart j
Apr 23 11:09:15 duet3 systemd[1]: Stopped Duet Control Server.
Apr 23 11:09:15 duet3 systemd[1]: Started Duet Control Server.
Apr 23 11:09:16 duet3 DuetControlServer[2566]: Duet Control Server v1.3.2
Apr 23 11:09:16 duet3 DuetControlServer[2566]: Written by Christian Hammacher fo
Apr 23 11:09:16 duet3 DuetControlServer[2566]: Licensed under the terms of the G
Apr 23 11:09:18 duet3 DuetControlServer[2566]: [info] Settings loaded
Apr 23 11:09:19 duet3 DuetControlServer[2566]: [info] Environment initialized
Apr 23 11:09:20 duet3 DuetControlServer[2566]: [fatal] Duet is not available
Apr 23 11:09:20 duet3 systemd[1]: duetcontrolserver.service: Succeeded.
Apr 23 11:09:25 duet3 systemd[1]: duetcontrolserver.service: Service RestartSec=
Apr 23 11:09:25 duet3 systemd[1]: duetcontrolserver.service: Scheduled restart j
Apr 23 11:09:25 duet3 systemd[1]: Stopped Duet Control Server.
Apr 23 11:09:25 duet3 systemd[1]: Started Duet Control Server.
Apr 23 11:09:26 duet3 DuetControlServer[2596]: Duet Control Server v1.3.2
Apr 23 11:09:26 duet3 DuetControlServer[2596]: Written by Christian Hammacher fo
Apr 23 11:09:26 duet3 DuetControlServer[2596]: Licensed under the terms of the G

I don't understand what's going on anymore.

Following the getting started guide I even enabled SPI and started DCS; still no luck

Really bummed out now; any idea what to do?

I left all the components version as is from the image:

pi@duet3:~ $ apt list 2>/dev/null | grep duet
duetcontrolserver/now 1.3.2 armhf [installed,local]
duetruntime/now 1.3.2 armhf [installed,local]
duetsd/now 1.0.6 all [installed,local]
duetsoftwareframework/now 1.3.2 armhf [installed,local]
duettools/now 1.3.2 armhf [installed,local]
duetwebcontrol/now 2.1.2 all [installed,local]
duetwebserver/now 1.3.1 armhf [installed,local]