Bed Heating Issue, wifi issue & Nozzle crashing!
-
Hi All,
I am having some issues, when I try to use my duet from the user web interface i get the below error?
This is every 10 seconds but then sometimes it will work for over an hour with no issues? Is there any way to go about troubleshooting this?
Also, I keep getting the warning about my bed being slow to heat up, I've calibrated the bed heater yet to no resolve. Is there a way to disable this?
Edit: May aswell include all the issues im getting in one post: I am also having problems with the hotend crashing into the bed at the start of a print althought I have zeroed my Z axis? What variable do I need to change to give my nozzle more clearance
Thank you for your help.
Kind Regards,
Adam -
Please share some more detailed information. Lets start with your full config.g and send M122 and M98 P"config.g" in the gcode console and copy and paste the results here.
-
@Phaedrux Hi Phaedrux my config is here:
; Configuration file for Duet WiFi (firmware version 3.3) ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v3.3.14 on Sat Oct 29 2022 18:08:10 GMT+0100 (British Summer Time) ; General preferences G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"Printer" ; 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 M569 P4 S0 ; physical drive 4 goes forwards - E1 M584 X0 Y1 Z2:5 E3:4 ; set drive mapping M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation M92 X80.00 Y80.00 Z400.00 E420.00 ; set steps per mm M566 X900.00 Y900.00 Z60.00 E120.00 ; set maximum instantaneous speed changes (mm/min) M203 X6000.00 Y6000.00 Z180.00 E1200.00 ; set maximum speeds (mm/min) M201 X500.00 Y500.00 Z20.00 E250.00 ; set accelerations (mm/s^2) M906 X1500 Y1500 Z1500 E1500 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 X550 Y410 Z500 S0 ; set axis maxima ; Endstops M574 X1 S1 P"!xstop" ; configure switch-type (e.g. microswitch) endstop for low end on X via pin xstop M574 Y1 S1 P"!ystop" ; configure switch-type (e.g. microswitch) 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" H30 F120 T6000 ; set Z probe type to unmodulated and the dive height + speeds G31 P500 X35 Y0 Z13 ; set Z probe trigger value, offset and trigger height M557 X15:525 Y10:400 S30 ; 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 M143 H1 S300 ; set temperature limit for heater 1 to 300C ; 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 S"MATERIAL 1" 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 M563 P1 S"MATERIAL 2" D0 H1 F0 ; define tool 1 G10 P1 X0 Y0 Z0 ; set tool 1 axis offsets G10 P1 R0 S0 ; set initial tool 1 active and standby temperatures to 0C
M122:
=== Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.1 (2022-06-01 21:05:28) running on Duet WiFi 1.02 or later Board ID: 08DGM-917NK-F23T0-6JKDJ-3SD6N-TDBJF Used output buffers: 3 of 26 (24 max) === RTOS === Static ram: 23860 Dynamic ram: 75184 of which 12 recycled Never used RAM 13024, free system stack 184 words Tasks: NETWORK(ready,13.8%,225) HEAT(notifyWait,0.0%,317) Move(notifyWait,0.0%,363) MAIN(running,86.1%,460) IDLE(ready,0.0%,30), total 100.0% Owned mutexes: WiFi(NETWORK) === Platform === Last reset 00:05:06 ago, cause: power up Last software reset time unknown, reason: User, GCodes spinning, available RAM 13024, slot 1 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a Error status: 0x00 Step timer max interval 0 MCU temperature: min 25.3, current 25.8, max 26.0 Supply voltage: min 24.1, current 24.2, max 24.4, 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: 0 queued, 0 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 n/a 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-08 17:47:07 Cache data hit count 4294967295 Slowest loop: 7.81ms; fastest: 0.19ms 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 3.2ms, write time 0.0ms, max retries 0 === Move === DMs created 83, 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, 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: 200.03ms; fastest: 0.08ms Responder states: HTTP(1) HTTP(1) 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 1 WiFi firmware version 1.26 WiFi MAC address b4:e6:2d:53:0c:f9 WiFi Vcc 3.37, reset reason Turned on by main processor WiFi flash size 4194304, free heap 23488 WiFi IP address 192.168.1.247 WiFi signal strength -41dBm, mode 802.11n, reconnections 0, sleep mode modem Clock register 00002002 Socket states: 2 2 0 0 0 0 0 0Also, suprisingly, I only have config.g.bak?! But my machine still runs fine? Could you help me understand this please?
THANK YOU FOR YOUR HELP!!
-
download a copy of your config.g.bak for safe keeping, then rename it on the Duet to config.g
It seems like your main config.g has been lost and no config is being applied which could explain some things.
Once you've done that I suggest you update your firmware. Download this zip file and upload it to the system tab in DWC.
https://github.com/Duet3D/RepRapFirmware/releases/download/3.4.4/Duet2and3Firmware-3.4.4.zip
-
@Phaedrux Thank you very much for this!! I think this has solved my issue! Did you see any errors or anything in my M122 command?
-
@Phaedrux Can I also ask a further question since you seem like the expert... how do i adjust my z so that when i start a print my hotend doesnt slam into the bed?
Thanks again!
-
@Adam_Sw3 said in Bed Heating Issue, wifi issue & Nozzle crashing!:
how do i adjust my z so that when i start a print my hotend doesnt slam into the bed?
Go through this. Sounds like you need to measure your probe trigger height.
https://docs.duet3d.com/en/User_manual/Connecting_hardware/Z_probe_testing
-
@Phaedrux Thank you! so once I hav mesh bed levelling and this variable then I should be away!
Cheers! -
Share your homeall.g and homez.g if you want a sanity check on your homing.
