Getting phase errors for extruder motor
-
Try mapping the extruder to another driver and test again. If it works as expected, you may have a damaged driver chip. If it doesn't work on that driver either but that driver works with other motors, then it's likely a wiring issue.
It would also help to see your full config.g and the results of M122.
-
@Phaedrux So I tried another motor on the same driver and got the same error. I mapped the extruder to another driver and got the same error. Tried a new motor on the new driver and same error.
Here is my config.g file:
; Configuration file for Duet WiFi (firmware version 3) ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v3.2.3 on Tue Apr 06 2021 11:31:03 GMT-0400 (Eastern Daylight Time) ; General preferences G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"HartingsLabFlashforge" ; set printer name M555 P1 ; Network M552 S2 ; Turn network on in access point mode ; Drives M569 P0 S0 ; physical drive 0 goes forwards M569 P1 S1 ; physical drive 1 goes forwards M569 P2 S1 ; physical drive 2 goes forwards M569 P3 S1 ; EXTRUDER physical drive 3 goes forwards M584 X0 Y1 Z2 E3 ; set drive mapping M350 X64 Y64 Z16 E16 I1 ; configure microstepping with interpolation ;M92 X376.48 Y376.48 Z400.00 E15360.00 ; set steps per mm ;M92 X378.37 Y380.41 Z403.83 E15360.00 ; set steps per mm M92 X377.46 Y380.41 Z403.83 E15360.00 ; set steps per mm M566 X180.00 Y180.00 Z60.00 E6.00 ; set maximum instantaneous speed changes (mm/min) M203 X1800.00 Y1800.00 Z600.00 E60.00 ; set maximum speeds (mm/min) M201 X150.00 Y150.00 Z150.00 E15.00 ; set accelerations (mm/s^2) ;M566 X600.00 Y600.00 Z60.00 E6.00 ;FAST set maximum instantaneous speed changes (mm/min) ;M203 X6000.00 Y6000.00 Z600.00 E60.00 ;FAST set maximum speeds (mm/min) ;M201 X600.00 Y600.00 Z150.00 E15.00 ;FAST set accelerations (mm/s^2) M906 X550 Y550 Z450 E1100 I70 ; set motor currents (mA) and motor idle factor in per cent M84 S30 ; Set idle timeout ; Axis Limits M208 X0 Y0 Z0 S1 ; set axis minima M208 X105 Y150 Z50 S0 ; set axis maxima ; Endstops M574 X2 S1 P"!xstop" ; configure active-high endstop for high end on X via pin xstop M574 Y2 S1 P"!ystop" ; configure active-high endstop for high end on Y via pin ystop M574 Z2 S1 P"!zstop" ; configure active-high endstop for high end on Z via pin zstop ; Heaters M140 H-1 ; disable heated bed (overrides default heater mapping) ; Fans ; Tools M563 P0 D0 ; define tool 0 G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C ; Custom settings are not definedMy M122:
m122 === Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.4 (2022-10-20 16:17:41) running on Duet WiFi 1.02 or later Board ID: 0JD2M-9F8TA-GJ4TD-6J1D6-3SD6M-16PQ6 Used output buffers: 1 of 26 (26 max) === RTOS === Static ram: 23860 Dynamic ram: 74320 of which 0 recycled Never used RAM 13828, free system stack 140 words Tasks: NETWORK(ready,15.4%,257) HEAT(notifyWait,0.0%,388) Move(notifyWait,0.0%,322) MAIN(running,83.6%,438) IDLE(ready,1.0%,30), total 100.0% Owned mutexes: WiFi(NETWORK) === Platform === Last reset 00:03:12 ago, cause: software Last software reset at 2022-11-13 15:51, reason: User, GCodes spinning, available RAM 13828, slot 0 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a Error status: 0x04 Step timer max interval 0 MCU temperature: min 29.7, current 30.1, max 30.8 Supply voltage: min 24.4, current 24.7, max 25.1, under voltage events: 0, over voltage events: 0, power good: yes Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0 Events: 3709 queued, 3709 completed Driver 0: standstill, SG min n/a Driver 1: standstill, SG min n/a Driver 2: standstill, SG min n/a Driver 3: standstill, SG min 0 Driver 4: standstill, SG min n/a Driver 5: Driver 6: Driver 7: Driver 8: Driver 9: Driver 10: Driver 11: Date/time: 2022-11-13 15:55:05 Cache data hit count 4294967295 Slowest loop: 7.67ms; fastest: 0.18ms I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0 === Storage === Free file entries: 10 SD card 0 detected, interface speed: 20.0MBytes/sec SD card longest read time 6.1ms, write time 0.0ms, max retries 0 === Move === DMs created 83, segments created 3, maxWait 49999ms, bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves 2, completed 2, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 2], 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, chamber heaters -1 -1 -1 -1, ordering errs 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 Daemon is idle in state(s) 0 Autopause is idle in state(s) 0 Code queue is empty === Network === Slowest loop: 13.35ms; fastest: 0.00ms Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) HTTP sessions: 1 of 8 = WiFi = Network state is active WiFi module is providing access point Failed messages: pending 0, notready 0, noresp 0 WiFi firmware version 1.27 WiFi MAC address a6:e5:7c:03:da:75 WiFi Vcc 3.36, reset reason Power up WiFi flash size 2097152, free heap 24896 WiFi IP address 192.168.0.1 Connected clients 1 Clock register 00002002 Socket states: 0 0 0 0 0 0 0 0 -
I also get this error when nothing is plugged into the drivers
-
@bwenig said in Getting phase errors for extruder motor:
I mapped the extruder to another driver and got the same error.
So it follows the motor and the driver?
Did the new motor you tried on the new driver use the same wiring?
So you have two drivers now that are not working?
So which drivers are the ones having a problem?
Have you tried one of the drivers that is currently working on one of the existing axis like X?
@bwenig said in Getting phase errors for extruder motor:
E15360.00
This is a very high steps per mm. What kind of extruder is this?
Can you post some photos of the driver chips?
-
@Phaedrux
Yes, it follows the motor and driver.
Yes I used the same wiring, and tried switching the A and B as well/
So now I have two drivers not working: E0 and E1.
I am hesitant to try the motor on a working axis! But I will test it now.I am using a Replistruder. I got the config.g file from a research paper.
Here are some pics of the board:
-
@bwenig said in Getting phase errors for extruder motor:
I used the same wiring
You should use new wiring.
-
So plugging the extruder motor into the x axis results in the same error, but I heard some clicking out of the motor, it tried to move a little bit.
I plugged the x driver back into the x motor and luckily everything still works fine.
-
@bwenig said in Getting phase errors for extruder motor:
I am using a Replistruder. I got the config.g file from a research paper.
I don't know what that is, but 16000 steps per mm is insanely high. How fast are you trying to command the extruder to move?
-
@Phaedrux My extruder has very fine movement, so I think 160000 steps might not be too bad? Here's a video of me moving it manually:
-
Well it may limit speed.
-
@Phaedrux Should I try a much smaller E value? Not sure what else I could try to get these drivers to cooperate
-
Do the drivers work if you move the X/Y axis to them and remap?
-
@Phaedrux No, they throw the same phase errors
-
And if you put the X/Y motors on the drivers you were using for the extruder and remap do they work there?
