Random loss of the extruder
-
Good morning all
I have a problem my config works well but I randomly lose the extruder.
card: Duet 2 wifi
screen: 5 inches with Paneldue
printer: Core xy home made
I indicated several times in config.g T0 but it still ended up not being lost and in a completely random way:
I was able to print 3 hours and 2 minutes from the end of the print loss of T0
"Error: Attempting to extrude with no tool selected."
please help me i love the functions of the duet !
My configuration :; Configuration file for Duet WiFi (firmware version 3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.1.4 on Sun Jul 19 2020 13:14:37 GMT+0200 (heure d’été d’Europe centrale); General preferences
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"MyXCore 300 Duet" ; set printer name
M669 K1 ; select CoreXY mode; Network
M552 S1 ; enable network
M586 P0 S1 ; enable HTTP
M586 P1 S0 ; disable FTP
M586 P2 S0 ; disable Telnet; Drives
M569 P0 S1 ; physical drive 0 goes forwards
M569 P1 S1 ; physical drive 1 goes forwards
M569 P2 S1 ; physical drive 2 goes forwards
M569 P3 S1 ; physical drive 3 goes forwards
M584 X0 Y1 Z2 E3 ; set drive mapping
M350 X32 Y32 Z32 E16 I1 ; configure microstepping with interpolation
M92 X160.00 Y160.00 Z800.00 E111.85 ; set steps per mm
M566 X900.00 Y900.00 Z20.00 E120.00 ; set maximum instantaneous speed changes (mm/min)
M203 X6000.00 Y6000.00 Z200.00 E1200.00 ; set maximum speeds (mm/min)
M201 X800.00 Y800.00 Z25.00 E250.00 ; set accelerations (mm/s^2)
M906 X1100 Y1200 Z900 E900 I30 ; 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 X300 Y300 Z300 S0 ; set axis maxima; Endstops
M574 X1 S1 P"xstop" ; configure active-high endstop for low end on X via pin xstop
M574 Y1 S1 P"ystop" ; configure active-high endstop for low end on Y via pin ystop
M574 Z1 S2 ; configure Z-probe endstop for low end on Z; Z-Probe
M558 P1 C"!zprobe.in" H5 F200 T6000 ; set Z probe type to unmodulated and the dive height + speeds
M558 H5 ;*** Remove this line after delta calibration has been done and new delta parameters have been saved
G31 P500 X32 Y-70 Z3.30 ; set Z probe trigger value, offset and trigger height
M557 X10:270 Y30:250 S40 ; define mesh grid; Heaters
M308 S0 P"bedtemp" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin bedtemp
M950 H0 C"bedheat" T0 ; create bed heater output on bedheat and map it to sensor 0
M307 H0 B1 S1.00 ; enable bang-bang mode for the bed heater and set PWM limit
M140 H0 ; map heated bed to heater 0
M143 H0 S120 ; set temperature limit for heater 0 to 120C
M308 S1 P"e0temp" Y"thermistor" T100000 B4138 ; configure sensor 1 as thermistor on pin e0temp
M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1
M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit
;; Fans
M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency
M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off
M950 F1 C"fan1" Q500 ; create fan 1 on pin fan1 and set its frequency
M106 P1 S1 H1 T45 ; set fan 1 value. Thermostatic control is turned on; Tools
M563 P0 D0 H1 F0 ; 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 defined
; Miscellaneous
M575 P1 S1 B57600 ; enable support for PanelDue; Fin
T0 ; choix outil
M501 ; lecture des paramètres enregistrés -
@seb007 said in Random loss of the extruder:
I was able to print 3 hours and 2 minutes from the end of the print loss of T0
"Error: Attempting to extrude with no tool selected."Can you share the gcode file you were printing?
-
Thank you for your answer, I have the linked file.
I did include the T0 in my gcode file but it ended up losing the tools.
I have a smaller file but it works like no other. -
@seb007 I can't see anything particularly wrong with this gcode file. There are no other tool change commands. Is this the file from the SD card? If not, I think maybe the file on the SD card may be corrupted. This could be caused by an error in transfer, or because of a corrupt SD card.
Please send M122 to the Duet and post the response. See https://duet3d.dozuki.com/Wiki/SD_Card#Section_Troubleshooting_SD_Card_issues to test the SD card and SD socket.
What version of DWC are you using? Select Settings > General in DWC to see the version. Are "CRC32 checksums for uploads" enabled? See Settings > Machine-Specific > Communication.Ian
-
m122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.1.1 running on Duet WiFi 1.02 or later
Board ID: 08DJM-9178L-L2MSD-6JKD2-3S86L-K9DGN
Used output buffers: 3 of 24 (11 max)
=== RTOS ===
Static ram: 27980
Dynamic ram: 93868 of which 52 recycled
Exception stack ram used: 264
Never used ram: 8908
Tasks: NETWORK(ready,404) HEAT(blocked,1224) MAIN(running,1880) IDLE(ready,80)
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:01:20 ago, cause: power up
Last software reset at 2020-08-18 16:50, reason: User, spinning module GCodes, available RAM 8620 bytes (slot 3)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task MAIN
Error status: 0
MCU temperature: min 32.1, current 35.6, max 35.9
Supply voltage: min 24.1, current 24.1, max 24.3, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: standstill, SG min/max not available
Driver 1: standstill, SG min/max not available
Driver 2: standstill, SG min/max not available
Driver 3: standstill, SG min/max not available
Driver 4: standstill, SG min/max not available
Date/time: 2020-08-19 17:14:42
Cache data hit count 132751524
Slowest loop: 4.76ms; fastest: 0.13ms
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 2.6ms, write time 0.0ms, max retries 0
=== Move ===
Hiccups: 0(0), FreeDm: 169, MinFreeDm: 169, MaxWait: 0ms
Bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1
=== AuxDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
Heater 1 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
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 112.81ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 1 of 8- WiFi -
Network state is active
WiFi module is connected to access point
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.23
WiFi MAC address 2c:f4:32:3e:e9:76
WiFi Vcc 3.36, reset reason Unknown
WiFi flash size 4194304, free heap 22672
WiFi IP address 192.168.1.68
WiFi signal strength -54dBm, reconnections 0, sleep mode modem
Socket states: 0 4 0 0 0 0 0 0
here is my M122
I use the web interface I do not use the SD card.
- WiFi -
-
@seb007 said in Random loss of the extruder:
I use the web interface I do not use the SD card.
The gcode files you upload via the web interface end up on the SD card in the Duet.
So please check the things that droftarts mentions.
Your DWC version should be 3.1.1.
-
thank you I will test and come back to you