Unable to write tmc spi 'stepper_x' register GLOBALSCALER
-
Duet 3 6HC
The printer was working fine, and suddenly it began displaying this error message. There doesn't appear to be any damage to the board. I'm unable to connect any of the 6 motor drivers. I haven't made any changes to the code, and I've checked my motor connections. Even when I attempt to connect the driver without the motors attached, it displays 'DRV_STATUS: 00000000' for every driver. Apart from this issue, the board appears to be functioning normally.
Using Klipper
-
@Venaticus best test it with RRF to see if the drivers are still working. You won't find any support for klipper here
-
@jay_s_uk Is there an other way maybe to check if there drivers are working? It was a such a hassle to run klipper on this thing.
-
@Venaticus best ask on the klipper discord
-
@Venaticus as a first step I suggest you check that the fuse that supplies VIN power to the stepper drivers and 12V regulator is working. RepRapFirmware monitors the 12V feed to the drivers and doesn't attempt to program them until they have sufficient voltage; but I think Klipper tries to program them regardless, which will fail if they don't have power from the 12V regulator.
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
@dc42 Hello, the VIN Fuse is fine, but I am not sure where exactly the 12 V regulator is and how to check if it is working.
-
@Venaticus you can check the 12V supply on the voltage select headers for OUT4-6 and OUT7-9.
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
@dc42 Yes, I am getting 12V from both of them.
-
@Venaticus I can't think of anything else to try, other than to install RRF on it and check the driver status in DWC, or to ask for suggestions on the Klipper discord.
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
@dc42 Hello, I did switch back to RRF and set up the DWC. Everything started working just fine. I was suddenly able to move every axis and M122 said everything was alright.
However, now I can do and move everything except for my extruder. I know the Motor isn't the problem because I was able to move is otherwise. Also turned on Cold extrusion with the M302 P1, that also isn't a problem. If I click on retract or on extrude I don't get any error but also nothing happens.
-
M92 X80.00 Y80.00 Z400.00 E102400.00 ; set steps per mm
Your E steps/mm looks far to high to me, faster than any reasonable motor could move.
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
@dc42 Yes, you are right. Which was done by mistake. However, the extruder never reacted even without the changes. Now I changed it back to the initial value but still nothing.
Edit: I tried switching the Drivers to the X from 0.0 to 0.3 and E from 0.3 to 0.0. Now from, I am unable to move the X motor, but the extruder works fine. Upon further inspection I realized I can't move any Stepper which is connected to the drivers 3, 4 or 5.
Also, even though the motors do not move, I do not get any errors and the tool Position and Printer Status changes. Like i mentioned before all motors and their connections are intact because they all run with the drivers 0, 1 and 2
The M122 command tells me: the driver status is okay though.
M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.4.6 (2023-07-21 14:11:38) running on Duet 3 MB6HC v1.02 or later (standalone mode)
Board ID: 08DJM-956BA-NA3TJ-6JKDL-3S06P-9T8LS
Used output buffers: 3 of 40 (13 max)
=== RTOS ===
Static ram: 153252
Dynamic ram: 98440 of which 0 recycled
Never used RAM 98980, free system stack 208 words
Tasks: NETWORK(ready,37.8%,155) ETHERNET(notifyWait,0.1%,320) HEAT(notifyWait,0.0%,321) Move(notifyWait,0.0%,352) CanReceiv(notifyWait,0.0%,943) CanSender(notifyWait,0.0%,335) CanClock(delaying,0.0%,343) TMC(notifyWait,7.6%,90) MAIN(running,54.3%,1101) IDLE(ready,0.2%,30), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:01:08 ago, cause: software
Last software reset at 2023-11-20 16:46, reason: User, GCodes spinning, available RAM 98908, slot 0
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0044a000 BFAR 0x00000000 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Step timer max interval 789
MCU temperature: min 27.3, current 28.7, max 28.9
Supply voltage: min 23.9, current 24.0, max 24.0, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.1, current 12.1, max 12.3, under voltage events: 0
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: ok, SG min 0, mspos 0, reads 56236, writes 14 timeouts 0
Driver 1: ok, SG min 0, mspos 0, reads 56236, writes 14 timeouts 0
Driver 2: ok, SG min 0, mspos 0, reads 56236, writes 14 timeouts 0
Driver 3: ok, SG min 0, mspos 0, reads 56236, writes 14 timeouts 0
Driver 4: ok, SG min 0, mspos 9, reads 56240, writes 11 timeouts 0
Driver 5: ok, SG min 0, mspos 9, reads 56240, writes 11 timeouts 0
Date/time: 2023-11-20 16:47:53
Slowest loop: 3.17ms; fastest: 0.05ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 25.0MBytes/sec
SD card longest read time 2.3ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 125, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters 0 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
Heater 1 is on, I-accum = 0.0
Heater 2 is on, I-accum = 0.0
=== 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 idle in state(s) 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
=== CAN ===
Messages queued 618, received 0, lost 0, boc 0
Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 50 (min 50), ts 344/0/0
Tx timeouts 0,0,343,0,0,273 last cancelled message type 4514 dest 127
=== Network ===
Slowest loop: 2.78ms; fastest: 0.03ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 1 of 8
= Ethernet =
State: active
Error counts: 0 0 0 0 0 0
Socket states: 5 2 2 2 2 0 0 0
= WiFi =
Interface state: disabled
Module is disabled
Failed messages: pending 0, notready 0, noresp 0
Socket states: 0 0 0 0 0 0 0 0
=== Multicast handler ===
Responder is inactive, messages received 0, responses 0 -
Please send an email to warranty@duet3d.com and CC your reseller. Include a link to this forum thread and the details of your original purchase. You'll receive a reply with a form to fill out.
