Duet3/pi DCS is unavailable after wiring 24V

fractalengineer

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

Curious, did it affect the blinking led?

not at all unfortunately; blinking led still present, still unable to connect to DWC; no progression of the symptoms since the original post

But we know the board is mostly working at least.

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

I also updates all packages according to the thread you mentioned earlier; everything is now running those versions:

that means the firmware has to be running RC6 (or there is a link in the thread above on how to specify 1.2.5 and use RC5 due to issues with RC6)

Danal

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

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

Your photo shows Duet power by VIN (which is good!).

No it shows the board powered by usb, albeit with VIN connected. And with nothing else connected a single USB power source isn't going to cause a problem and is easier to relay than the alternatives, while keeping the potential for damage to a minimum.

Got it! Thanks for the clarification.

fractalengineer

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

But we know the board is mostly working at least.

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

I also updates all packages according to the thread you mentioned earlier; everything is now running those versions:

that means the firmware has to be running RC6 (or there is a link in the thread above on how to specify 1.2.5 and use RC5 due to issues with RC6)

But the M115 just above shows it's running 3.0

I don't know what else to do I think I will nuke the card and redo a fresh install

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

But the M115 just above shows it's running 3.0

true; but to run RRF 3.0 with DSF, DSF can't be 1.3.1 - but 1.2.4 as it was should have worked.

as you have DSF 1.3.1 upgrading to RRF 3.01-RC6 is the path of least resistance.

The alternative dc42 reccomneded in the other thread was to use RRF 3.01-RC5 with DSF 1.2.5

or get DSF back to DSF 1.2.4 (to run with RRF 3.0)

fractalengineer

@bearer Ok;

I just flashed to RRF 3.01 RC6 with the previously updated DSF 1.3.1 ; still blinking, still can't connect to DWC

Tried RRF 3.0 with 1.2.4 earlier before original post; wasn't working either.

Nuking the card now; let's see if it does anything

Not 100% sure the blinking is a problem though; the unable to connect bit on the other hand is.

Make sure the board shows up with the Duet3 vid/pid and responds to M115 and/or M122.

Plus any combination of reccomended versions as pr the link where dc42 and chrishamm list their reccomendation and then see if one of them have anything to add I guess. I'm off for a bit.

fractalengineer

@bearer Thank you for all the help; I agree the flashing led is not an issue; just a symptom I want to mention as it's supposed to be shut in normal operation.

Nevertheless, just completed the flashing and setup on fresh install, and still the same issue.

Here's the current status:

pi@duet3:~ $ apt list 2>/dev/null | grep duet
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]

pi@duet3:~ $ sudo journalctl -u duetcontrolserver -e
Apr 12 15:58:45 duet3 DuetControlServer[4490]: [info] Environment initialized
Apr 12 15:58:46 duet3 DuetControlServer[4490]: [error] Duet is not available
Apr 12 15:58:46 duet3 systemd[1]: duetcontrolserver.service: Succeeded.
Apr 12 15:58:51 duet3 systemd[1]: duetcontrolserver.service: Service RestartSec=
Apr 12 15:58:51 duet3 systemd[1]: duetcontrolserver.service: Scheduled restart j
Apr 12 15:58:51 duet3 systemd[1]: Stopped Duet Control Server.
Apr 12 15:58:51 duet3 systemd[1]: Started Duet Control Server.
Apr 12 15:58:52 duet3 DuetControlServer[4530]: Duet Control Server v1.2.4.0
Apr 12 15:58:52 duet3 DuetControlServer[4530]: Written by Christian Hammacher fo
Apr 12 15:58:52 duet3 DuetControlServer[4530]: Licensed under the terms of the G
Apr 12 15:58:54 duet3 DuetControlServer[4530]: [info] Settings loaded
Apr 12 15:58:55 duet3 DuetControlServer[4530]: [info] Environment initialized
Apr 12 15:58:56 duet3 DuetControlServer[4530]: [error] Duet is not available
Apr 12 15:58:56 duet3 systemd[1]: duetcontrolserver.service: Succeeded.
Apr 12 15:59:01 duet3 systemd[1]: duetcontrolserver.service: Service RestartSec=
Apr 12 15:59:01 duet3 systemd[1]: duetcontrolserver.service: Scheduled restart j
Apr 12 15:59:01 duet3 systemd[1]: Stopped Duet Control Server.
Apr 12 15:59:01 duet3 systemd[1]: Started Duet Control Server.
Apr 12 15:59:01 duet3 DuetControlServer[4569]: Duet Control Server v1.2.4.0
Apr 12 15:59:01 duet3 DuetControlServer[4569]: Written by Christian Hammacher fo
Apr 12 15:59:01 duet3 DuetControlServer[4569]: Licensed under the terms of the G
Apr 12 15:59:04 duet3 DuetControlServer[4569]: [info] Settings loaded
Apr 12 15:59:05 duet3 DuetControlServer[4569]: [info] Environment initialized

M115
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
ok
M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC v0.6 or 1.0 version 3.0 running on Duet 3 MB6HC
Board ID: 08DJM-956L2-G43S4-6J9F6-3S86T-KA5LD
Used output buffers: 1 of 32 (1 max)
=== RTOS ===
Static ram: 152720
Dynamic ram: 148504 of which 0 recycled
Exception stack ram used: 280
Never used ram: 91712
Tasks: NETWORK(ready,1984) HEAT(blocked,1452) CanReceiv(suspended,3808) CanSender(suspended,1476) CanClock(blocked,1424) TMC(suspended,252) MAIN(running,4656) IDLE(ready,160)
Owned mutexes:
=== Platform ===
Last reset 00:04:40 ago, cause: reset button
Last software reset at 2020-04-04 15:59, reason: User, spinning module LinuxInterface, available RAM 79620 bytes (slot 0)
Software reset code 0x0010 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0440f000 BFAR 0x00000000 SP 0xffffffff Task 0x4e49414d
Error status: 0
Free file entries: 10
SD card 0 not detected, interface speed: 37.5MBytes/sec
SD card longest block write time: 0.0ms, max retries 0
MCU temperature: min 40.4, current 41.5, max 41.6
Supply voltage: min 0.3, current 0.3, max 0.4, under voltage events: 0, over voltage events: 0, power good: no
12V rail voltage: min 0.2, current 0.2, max 0.3, under voltage events: 0
Driver 0: ok, reads 0, writes 0 timeouts 0, SG min/max 0/0
Driver 1: ok, reads 0, writes 0 timeouts 0, SG min/max 0/0
Driver 2: ok, reads 0, writes 0 timeouts 0, SG min/max 0/0
Driver 3: ok, reads 0, writes 0 timeouts 0, SG min/max 0/0
Driver 4: ok, reads 0, writes 0 timeouts 0, SG min/max 0/0
Driver 5: ok, reads 0, writes 0 timeouts 0, SG min/max 0/0
Date/time: 1970-01-01 00:00:00
Slowest loop: 0.22ms; fastest: 0.08ms
=== Move ===
Hiccups: 0(0), FreeDm: 375, MinFreeDm: 375, MaxWait: 0ms
Bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
=== AuxDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
=== Heat ===
Bed heaters = -1 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
=== GCodes ===
Segments left: 0
Stack records: 1 allocated, 1 in use
Movement lock held by null
http is idle in state(s) 0
telnet is idle in state(s) 0
file is idle in state(s) 0
serial is ready with "M122" in state(s) 0
aux is idle in state(s) 0
daemon* is idle in state(s) 0 0, running macro
queue is idle in state(s) 0
lcd is idle in state(s) 0
spi is idle in state(s) 0
autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 0.15ms; fastest: 0.01ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 0 of 8
- Ethernet -
State: 0
Error counts: 0 0 0 0 0
Socket states: 0 0 0 0 0 0 0 0
=== CAN ===
Messages sent 0, longest wait 0ms for type 0
=== Linux interface ===
State: 0, failed transfers: 0
Last transfer: 280751ms ago
RX/TX seq numbers: 0/1
SPI underruns 0, overruns 0
Number of disconnects: 0
Buffer RX/TX: 0/0-0
ok

It appears that the Duet can communicate with my computer over serial USB, but can't communicate with the Pi for some reason.

See

Apr 12 13:32:45 duet3 DuetControlServer[1405]: [error] Duet is not available

Any ideas how to take it from there? Thanks everyone

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

It appears that the Duet can communicate with my computer over serial USB, but can't communicate with the Pi for some reason.

it leaves the spi connection over the ribbon cable, or problems with the DSF package on the pi. Double check the ribbon cable, although i don't think it would work if it was off by a row/column.

while waiting I suppose you could try populating the SD card with /sys/config.g + DWC in /www and run it without the Pi to see if it helps determine if there are any problems with the board.

fractalengineer

@bearer sure of course I'll try anything to make it work

The ribbon cable looks mint and was very clearly connected properly

I just replaced the config.g file with the machine one and inserted the SD card in the boar but how did you mean to connect to it?

The diag led is still blinking

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

but how did you mean to connect to it?

when the Duet3 has an SD card with a config.g file it will for all intents function as a Duet 2 Ethernet, so having DuetWebControl on the SD card and using the Ethernet connection it should function without DSF on the Pi. No change needed to the firmware, it will detect the config file on the SD card in the SD card socket on the Duet 3.

fractalengineer

@bearer I see; I never had a Duet 2 this is my first board; thank you for clarifying.

Well I then followed the Duet 2 Ethernet Dozuki and enable networking; this is what I get now;

Still can't connect, led still blinking

Different error message though

dc42

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

The diag led is still blinking

That is what it is supposed to do on a Duet 3 in normal operation. It shows that the Duet is alive and running RRF. When expansion boards and/or tool boards are connected to the Duet 3 via CAN bus, the LEDs on those boards blink in sync with the one on the Duet 3 to indicate that time synchronisation has been established between them.

There have been problems with the 3.01-RC6 and DSF 1.3.x combination, and new releases will be available soon. Until they are available, it's best to run either RRF 3.01-RC6 in standalone mode (i.e. without the Pi), or RRF 3.01-RC5 with DSF 1.2.5 (and DWC 2.0.7 in either case).

Hmm, if you're using a compatible version of DWC that should rule out problems with anything DSF and Pi related.

Looking at the https://github.com/dc42/RepRapFirmware/releases/tag/3.0 page it says DuetWebControl 2.0.4. Or go with 3.01-RC6 + DWV 2.0.7 as suggested by dc42.

fractalengineer

@dc42 thanks for the response; ok so the blinking led is just a status light. I didn't remember it flashing before but now I know.

Ok so I started by flashing to 3.01-RC6 in standalone; still no chooch

DWC is still in 2.0.7 stable from the last status update.

what would you advise to do next? There's probably nothing that will come from trying to run it off the Pi if it doesn't even run by itself?

I'd look at the network traffic next; using wireshark to capture the packets to/from your computer.

And yeah, whatever the problem is, it will be the board itself or something networking related so might as well keep it simple and leave the Pi out of it for now. However if the issue is networking its strange DCS said DuetControlServer[4530]: [error] Duet is not available when on the Pi.

fractalengineer

@bearer good day,

Man that's getting very technical I've never worked with such software.

Is this the only way to troubleshoot moving forward? @dc42

fractalengineer

@bearer ok I managed to get wireshark to run and show interfaces; needed some troubleshooting too to work on Win10

It's capturing now; what should we be looking for?

Thanks

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

It's capturing now; what should we be looking for?

upload the file and I can take a look if I see anything to suggest where the problem lies?

(Edit: Start the capture, open a private browsing window or incognito window or whatever your browser calls it, try to open the Duet web page and then stop the capture. Don't have anything you'd consider sensitive going on at the same time)

fractalengineer

@bearer Thank you; sure here's a capture file; I started recording right before sending the M552 S1 command so there shouldn't be anything missing

I then attempted connecting to the DWC until the network error message showed up

https://we.tl/t-gPUhISpL9Z