Driver / motor just stop responding
-
Im having a strange issue. I have 1 motor working ok, but after some time the motor just stop rsponding. I though it was a cable problem and change the cable, and the motor started working again. SO I though problem solved, but then it happened again. Driver showing this issue is driver 0
I sent an diagnostic command and I got this:=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.4.1 (2022-06-01 21:09:01) running on Duet 3 MB6HC v1.01 or later (SBC mode)
Board ID: 08DJM-956BA-NA3TJ-6J1FL-3S46L-9986S
Used output buffers: 1 of 40 (15 max)
=== RTOS ===
Static ram: 151000
Dynamic ram: 64640 of which 1512 recycled
Never used RAM 130520, free system stack 159 words
Tasks: SBC(resourceWait:,0.5%,478) HEAT(notifyWait,0.0%,353) Move(notifyWait,0.0%,250) CanReceiv(notifyWait,0.0%,944) CanSender(notifyWait,0.0%,374) CanClock(delaying,0.0%,333) TMC(notifyWait,8.0%,58) MAIN(running,91.4%,923) IDLE(ready,0.0%,30), total 100.0%
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 16:21:11 ago, cause: software
Last software reset at 2022-06-21 21:26, reason: User, GCodes spinning, available RAM 130544, slot 1
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0044a000 BFAR 0x00000000 SP 0x00000000 Task SBC Freestk 0 n/a
Error status: 0x00
Step timer max interval 134
MCU temperature: min 39.0, current 39.5, max 39.7
Supply voltage: min 23.9, current 23.9, 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.2, under voltage events: 0
Heap OK, handles allocated/used 99/5, heap memory allocated/used/recyclable 2048/1732/1660, gc cycles 1
Events: 0 queued, 0 completed
Driver 0: standstill, SG min n/a, mspos 312, reads 52733, writes 0 timeouts 0
Driver 1: standstill, SG min n/a, mspos 296, reads 52733, writes 0 timeouts 0
Driver 2: standstill, SG min n/a, mspos 8, reads 52733, writes 0 timeouts 0
Driver 3: standstill, SG min n/a, mspos 8, reads 52733, writes 0 timeouts 0
Driver 4: standstill, SG min n/a, mspos 8, reads 52732, writes 0 timeouts 0
Driver 5: standstill, SG min n/a, mspos 8, reads 52733, writes 0 timeouts 0
Date/time: 2022-06-22 13:47:25
Slowest loop: 1.07ms; fastest: 0.04ms
=== Storage ===
Free file entries: 10
SD card 0 not detected, interface speed: 37.5MBytes/sec
SD card longest read time 0.0ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 125, segments created 6, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 913, completed 913, 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 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP* is doing "M122" 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 doing "G4 P1000" in state(s) 0 0, running macro
Aux2 is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty
=== CAN ===
Messages queued 1567, received 0, lost 0, boc 0
Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 50 (min 50), ts 871/0/0
Tx timeouts 0,0,871,0,0,696 last cancelled message type 30 dest 127
=== SBC interface ===
Transfer state: 5, failed transfers: 0, checksum errors: 0
RX/TX seq numbers: 34449/34449
SPI underruns 0, overruns 0
State: 5, disconnects: 0, timeouts: 0 total, 0 by SBC, IAP RAM available 0x2b880
Buffer RX/TX: 0/0-0, open files: 0
=== Duet Control Server ===
Duet Control Server v3.4.1
Daemon:
Buffered code: G4 P1000 ; Duracion de la pausa determina periodos de daemon.g
==> 32 bytes
Executing macro daemon.g, started by system
Number of flush requests: 1Next stack level
Code buffer space: 4096
Configured SPI speed: 8000000Hz, TfrRdy pin glitches: 0
Full transfers per second: 39.50, max time between full transfers: 45.3ms, max pin wait times: 36.3ms/0.5ms
Codes per second: 0.60
Maximum length of RX/TX data transfers: 3788/568Thanks in advance
-
Have you tried that motor on a different driver, or tried a different motor on driver0?
Do you get any error messages along with it?
-
@phaedrux Yes I connected the motor inmediatly to driver 1, and the motor moved.
After switching cables and conenecting cable to driver 0 again, same cable, same motor, the moro was responding again.I touch the driver, it is not hot. The motor is somehow hot, not enough to create a problem I think.
In the diagnosis data I can see a "movement lock held by null", is thta important?
No error reported when this happens, not in the console either
-
Can you take some photos of the front and back of the board? Particularly the driver area? Do you notice anything different about the soldering for that driver?
How hot is the motor getting?
Have you tried a different motor on driver0?
