3.2-RC2 - Timeout while waiting for transfer ready pin

GTech

Hi,

during the update I had the same issue I had on Beta 4.1

This time I did the following:

Downloaded a new image of DuetPI put it on a new SD card, enabled SSH and configured WiFi, booted and confirmed normal operation of the Duet stack.
Updated the kernel and user land to the latest version (apt update/upgrade) and confirmed normal operation once more.
Switched to the unstable Duet repo and executed the update (apt update & upgrade).. Like with Beta 4.1, the control server was unable to connect to the Duet3.

I am using a RPI4, 4GB

root@duet3:/opt/dsf/bin# ./DuetControlServer -l debug
Duet Control Server v3.2.0-rc2
Written by Christian Hammacher for Duet3D
Licensed under the terms of the GNU Public License Version 3

[info] Settings loaded
[info] Environment initialized
[fatal] Could not connect to Duet (Timeout while waiting for transfer ready pin)
[debug] System.OperationCanceledException: Timeout while waiting for transfer ready pin
   at DuetControlServer.SPI.DataTransfer.WaitForTransfer(Boolean inTransfer) in /home/christian/Duet3D/DuetSoftwareFramework/src/DuetControlServer/SPI/DataTransfer.cs:line 1086
   at DuetControlServer.SPI.DataTransfer.ExchangeHeader() in /home/christian/Duet3D/DuetSoftwareFramework/src/DuetControlServer/SPI/DataTransfer.cs:line 1148
   at DuetControlServer.SPI.DataTransfer.PerformFullTransfer(Boolean connecting) in /home/christian/Duet3D/DuetSoftwareFramework/src/DuetControlServer/SPI/DataTransfer.cs:line 162
   at DuetControlServer.SPI.DataTransfer.Init() in /home/christian/Duet3D/DuetSoftwareFramework/src/DuetControlServer/SPI/DataTransfer.cs:line 104
   at DuetControlServer.Program.Main(String[] args) in /home/christian/Duet3D/DuetSoftwareFramework/src/DuetControlServer/Program.cs:line 113
root@duet3:/opt/dsf/bin#

This time i was able to run the g-codes requested when I reported the error for Beta 4.2.

M115
FIRMWARE_NAME: RepRapFirmware for Duet 3 MB6HC FIRMWARE_VERSION: 3.2-RC2 ELECTRONICS: Duet 3 MB6HC v0.6 or 1.0 FIRMWARE_DATE: 2020-12-24

M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.2-RC2 running on Duet 3 MB6HC v0.6 or 1.0 (standalone mode)
Board ID: 08DGM-9T66A-G63SJ-6J9F2-3S86Q-TA0BA
Used output buffers: 1 of 40 (1 max)
=== RTOS ===
Static ram: 149788
Dynamic ram: 91516 of which 396 recycled
Never used RAM 117132, free system stack 160 words
Tasks: NETWORK(ready,547) HEAT(blocked,353) CanReceiv(blocked,927) CanSender(blocked,371) CanClock(blocked,352) TMC(blocked,53) MAIN(running,1345) IDLE(ready,19)
Owned mutexes: USB(MAIN)
=== Platform ===
Last reset 00:05:23 ago, cause: reset button
Last software reset details not available
Error status: 0x00
Aux0 errors 0,0,0
Aux1 errors 0,0,0
MCU temperature: min 21.7, current 24.3, max 24.5
Supply voltage: min 23.9, current 23.9, max 23.9, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.1, current 12.2, max 12.2, under voltage events: 0
Driver 0: position 0, standstill, reads 53913, writes 11 timeouts 0, SG min/max 0/0
Driver 1: position 0, standstill, reads 53913, writes 11 timeouts 0, SG min/max 0/0
Driver 2: position 0, standstill, reads 53913, writes 11 timeouts 0, SG min/max 0/0
Driver 3: position 0, standstill, reads 53913, writes 11 timeouts 0, SG min/max 0/0
Driver 4: position 0, standstill, reads 53913, writes 11 timeouts 0, SG min/max 0/0
Driver 5: position 0, standstill, reads 53914, writes 11 timeouts 0, SG min/max 0/0
Date/time: 1970-01-01 00:00:00
Slowest loop: 2.59ms; fastest: 0.05ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 25.0MBytes/sec
SD card longest read time 2.1ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 125, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters = -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
=== GCodes ===
Segments left: 0
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
USB is ready with „M122“ in state(s) 0 0
Aux is idle in state(s) 0
Trigger is idle in state(s) 0
Queue is idle in state(s) 0
LCD is idle in state(s) 0
SBC is idle in state(s) 0
Daemon is idle in state(s) 0
Aux2 is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 0.16ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions Telnet(0), 0 sessions
HTTP sessions: 0 of 8
- Ethernet -
State: disabled
Error counts: 0 0 0 0 0
Socket states: 0 0 0 0 0 0 0 0
=== CAN ===
Messages queued 0, send timeouts 1614, received 0, lost 0, longest wait 0ms for reply type 0, free buffers 47
ok

I had to downgrade to 3.1.1 in order to restore normal operation.

chrishamm

Please make sure there is no SD card in the Duet when you use it in SBC mode.

GTech

Okay, that worked, thanks!

Solved 3.2-RC2 - Timeout while waiting for transfer ready pin