Suddenly no more motor movement

benecito

Hi,

I am facing a little challenge right now. I am in Germany and a customer from Ecuador called in with a problem the other day.
He said after a print there suddenly was no more motor movement on any axis. Also the motors are all turned off and move freely all the time.
I checked everything before shipping and it also worked when it arrived.

I tried to diagnose (and fix) the problem today using teamviewer and WhatsApp, but I am out of ideas now.

Setup: Duet 3 mini in SBC mode connected to a pi. Everything is running on RRF3.3

What I tried:
I checked if everything has power -> it has
I checked if heating works -> it does
I restarted the whole system multiple times -> no change
I made sure all config files are there and correct -> they are
Connected one of the stepper motors to Driver 4 (was free before) and checked if I got any movement here. -> I did not

As far as I can tell everything gets loaded correctly when starting up. So I don't think it's a firmware problem on the duet or something broken in dcs.
Do you agree? Is there an easy way to reinstall DCS (and if needed DWC)? How likely is it that the firmware got corrupted but is still working in general? Is there a way to flash it again from the connected pi

How likely is it that all 4 stepper motors brake at once or all 5 motor drivers brake at once?

I am open to any ideas! If possible I don't want the customer to mess around in the printer too much and measure any voltages or alike, but I can of course ask him if needed.
My next step would be to prepare a new Image for the pi, and copy it to the sd card and try again, but I don't think thats the problem...

Gixxerfast

@benecito I would check with a m122.

If the PSU is bad and supplying under 10V (IIRC) the drivers will not be enabled.

dc42

@benecito there is a CRC check on the firmware when it loads, so it's unlikely that the firmware got corrupted.

Please get a M122 report so that we can see whether the stepper drivers have been initialised successfully and what VIN voltage the Duet reads.

benecito

@dc42 thanks - I could have thought of that myself.

Here is the M122 response:


Recv:11:21:06.752: === Diagnostics ===
Recv:11:21:06.752: RepRapFirmware for Duet 3 Mini 5+ version 3.3 (2021-06-15 21:46:11) running on Duet 3 Mini5plus Ethernet (SBC mode)
Recv:11:21:06.752: Board ID: 37LW3-Y196U-D65J0-40KM4-3013Z-RS7G9
Recv:11:21:06.753: Used output buffers: 1 of 40 (11 max)
Recv:11:21:06.753: === RTOS ===
Recv:11:21:06.753: Static ram: 102724
Recv:11:21:06.753: Dynamic ram: 93344 of which 0 recycled
Recv:11:21:06.753: Never used RAM 44780, free system stack 130 words
Recv:11:21:06.753: Tasks: SBC(ready,5.2%,330) HEAT(notifyWait,0.0%,366) Move(notifyWait,0.1%,305) CanReceiv(notifyWait,0.0%,941) CanSender(notifyWait,0.0%,371) CanClock(delaying,0.0%,340) TMC(notifyWait,0.3%,115) MAIN(running,93.6%,439) IDLE(ready,0.0%,29) AIN(delaying,0.8%,273), total 100.0%
Recv:11:21:06.754: Owned mutexes: Telnet(MAIN)
Recv:11:21:06.754: === Platform ===
Recv:11:21:06.754: Last reset 00:23:05 ago, cause: power up
Recv:11:21:06.754: Last software reset at 2022-02-21 07:00, reason: User, none spinning, available RAM 44780, slot 1
Recv:11:21:06.754: Software reset code 0x0012 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00489000 BFAR 0xe000ed38 SP 0x00000000 Task SBC Freestk 0 n/a
Recv:11:21:06.754: Error status: 0x00
Recv:11:21:06.755: MCU revision 3, ADC conversions started 1385569, completed 1385569, timed out 0, errs 0
Recv:11:21:06.755: Step timer max interval 1250
Recv:11:21:06.755: MCU temperature: min 34.4, current 37.9, max 37.9
Recv:11:21:06.755: Supply voltage: min 23.6, current 23.7, max 23.8, under voltage events: 0, over voltage events: 0, power good: yes
Recv:11:21:06.755: Heap OK, handles allocated/used 99/0, heap memory allocated/used/recyclable 2048/4/4, gc cycles 0
Recv:11:21:06.756: Driver 0: position 0, assumed not present
Recv:11:21:06.756: Driver 1: position 0, assumed not present
Recv:11:21:06.756: Driver 2: position 0, assumed not present
Recv:11:21:06.756: Driver 3: position -604724, assumed not present
Recv:11:21:06.756: Driver 4: position 0, assumed not present
Recv:11:21:06.756: Driver 5: position 0, assumed not present
Recv:11:21:06.756: Driver 6: position 0, assumed not present
Recv:11:21:06.756: Date/time: 2022-02-21 11:21:06
Recv:11:21:06.757: Cache data hit count 3262370444
Recv:11:21:06.757: Slowest loop: 1.18ms; fastest: 0.09ms
Recv:11:21:06.757: === Storage ===
Recv:11:21:06.757: Free file entries: 10
Recv:11:21:06.757: SD card 0 not detected, interface speed: 0.0MBytes/sec
Recv:11:21:06.757: SD card longest read time 0.0ms, write time 0.0ms, max retries 0
Recv:11:21:06.757: === Move ===
Recv:11:21:06.758: DMs created 83, maxWait 0ms, bed compensation in use: none, comp offset 0.000
Recv:11:21:06.758: === MainDDARing ===
Recv:11:21:06.758: Scheduled moves 1, completed moves 1, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
Recv:11:21:06.758: === AuxDDARing ===
Recv:11:21:06.758: Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
Recv:11:21:06.758: === Heat ===
Recv:11:21:06.758: Bed heaters = -1 -1, chamberHeaters = -1 -1
Recv:11:21:06.758: Heater 1 is on, I-accum = 0.0
Recv:11:21:06.759: === GCodes ===
Recv:11:21:06.759: Segments left: 0
Recv:11:21:06.759: Movement lock held by null
Recv:11:21:06.759: HTTP is idle in state(s) 0
Recv:11:21:06.759: Telnet* is doing "M122" in state(s) 0
Recv:11:21:06.759: File is idle in state(s) 0
Recv:11:21:06.759: USB is idle in state(s) 0
Recv:11:21:06.760: Aux is idle in state(s) 0
Recv:11:21:06.760: Trigger* is idle in state(s) 0
Recv:11:21:06.760: Queue is idle in state(s) 0
Recv:11:21:06.760: LCD is idle in state(s) 0
Recv:11:21:06.760: SBC is idle in state(s) 0
Recv:11:21:06.760: Daemon is idle in state(s) 0
Recv:11:21:06.760: Aux2 is idle in state(s) 0
Recv:11:21:06.760: Autopause is idle in state(s) 0
Recv:11:21:06.761: Code queue is empty.
Recv:11:21:06.761: === CAN ===
Recv:11:21:06.761: Messages queued 6707, received 0, lost 0, longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 17 (min 17), ts 3726/0/0
Recv:11:21:06.761: Tx timeouts 0,0,3726,0,0,2981 last cancelled message type 4514 dest 127
Recv:11:21:06.761: === SBC interface ===
Recv:11:21:06.761: State: 4, failed transfers: 1, checksum errors: 0
Recv:11:21:06.761: Last transfer: 2ms ago
Recv:11:21:06.762: RX/TX seq numbers: 8089/8089
Recv:11:21:06.762: SPI underruns 0, overruns 0
Recv:11:21:06.762: Disconnects: 0, timeouts: 0, IAP RAM available 0x10b2c
Recv:11:21:06.762: Buffer RX/TX: 0/0-0
Recv:11:21:06.762: === Duet Control Server ===
Recv:11:21:06.762: Duet Control Server v3.3.0
Recv:11:21:06.762: Code buffer space: 4096
Recv:11:21:06.763: Configured SPI speed: 8000000Hz
Recv:11:21:06.763: Full transfers per second: 101.72, max wait times: 8.7ms/0.0ms
Recv:11:21:06.763: Codes per second: 1.01
Recv:11:21:06.763: Maximum length of RX/TX data transfers: 2976/676

dc42

@benecito the processor has failed to communicate with the stepper drivers so they are all showing as "assumed not present". Please confirm that you have nothing plugged into the 2-driver expansion socket (if you have a 2-driver expansion board there, remove it).

benecito

@dc42

No, nothing plugged in there!

dc42

@benecito as the reported VIN is within range, it sounds to me like a hardware failure.

benecito

@dc42 Do you have any reseller who could take care of the replacement in Ecuador or somewhere nearby?
Your official reseller list does not state any.
That would probably make it easier than to ship it to Germany and then to the UK.
Thanks!

Phaedrux

Ecuador to the US may be the closest, but who is the original vendor?

benecito

@phaedrux
I guess still better and cheaper then from Germany
The board is from CR3D.
Would be very happy if you can organise the replacement with one of your resellers. You can contact me on info@chocolate3.de for the address.

Phaedrux

I can see if something is possible, but I make no promises. It's a bit unusual.

In meantime, 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.

benecito

@phaedrux just sent it. Any news if the replacement from the US will work?