Duet2 Wifi 3.2beta to 3.3 stable-T0 error boot /Heat Excursion
-
Seems to be an odd error / issue.
Upgraded Duet2 wifi board from 3.2 beta to 3.3 stable. I did not have a defined T0 in my config.g anywhere prior to migrating to 3.3
I have recently - whilst on 3.2beta, started using the Filaments feature and config.g and load and unload so I can do FW retraction and such with SuperSlic3r/PrusaSlic3r. Was working well. Decided to go up to 3.3 rrfw. Partly as I was having some issues with slicers and start.g I was advised I needed to add a T0 to my config.g and in my start.g to quell some PrusaSlic3r funky add in deprecated Gcode to my start.g
Now when I restart the board, it starts heating my bed, and the nozzle - to whatever Filament[s] are currently loaded on T0. Its using my Filaments config.g info for T0 Nozz temps and stnadby temp ... and the bed print temp ...
I know its getting the settings and data from there because its the only place I specify a standby temp.
If I remove the T0 from my config.g - I do not get the unxpected Heat of nozz and bed at board start - which is kinda spooky ... but it also throws heater fault on both bed and Nozz
- [ nozzle first ] 15*C Temperature Excursion Error
Apparently is proper practice to define your tool / T0 - single tool printer - in the config.g, but If I conform - I have this weird error. Searched for a while couldnt locate a thread on this yet - google and in this forum. Seems a weird / odd error.
-
not worthy of a response by anyone at duet ?
-
My workaround was to remove the T0 from my config.g to avoid the above error .. and to add info into the custom start.g macro in Prusa Slicer - where I tricked it with some M codes for the two heaters - thereby preventing prusa slicer from adding its safety nozz temp heater settings and an M116 to wait tilll temps [ which wreaks havoc on rrfw 3.4beta etc.
NOW ... since id been waiting for a reply here - and getting some printing done - Ive an added issue.
During sensorless homing after a print the previous day ... my bed was at Y0 ... it homes to Y maxima, and uses sensorless ... there is a 10 mm negative move prior to moving to Y maxima - but since Y was manually pulled previously to Y0 - it could not move- it made the grinding sound and then triggered a stall - not at Y maxima.
So the home all where z fires was going to crash the hotend into some bed hardware - so Estop - nozz was saved but fan shroud was hitting a bed clip and was tweekin ... so before i powered off ... manually lifted z 40 mm
Powered off ... let it sit .... checked for carnage ... Power back on, and now its screwed ...
Cant connect to it over wifi, and paneldue sits there saying Connecting. Console and manually typing on paneldue M122 - gives me nothing M115 as well no moves nothing works
in Paneldue setup screen baud rate shows 56700
-
@sputnikoc3d adding T0 to config.g should be safe if the G10 for T0 has S0, R0 (i.e. set it to 0 temperature). what did you have in config.g?
