Tool heater always 'active'
-
I am not sure if this is a hardware issue or a config.g issue. I am working on commissioning a new Duet2 wifi based printer build. for some reason, when I power up the controller, the tool heater is locked into the 'active' state. If I click on the tool in DWC, it does not cycle through 'off', 'standby' and 'active' ... it is always 'active. Further, if I set a temperature, the heater does not seem to turn on but I also get no heater fault. If I leave out the T0 command at the end of config.g, the tool is locked in the 'off' state. If I click on the tool/nozzle rather than the heater, it toggles between 'standby' and 'active'.
Note that this is a new build and a wiring issue is not out of the question (although I think unlikely); Configuration file for Duet WiFi (firmware version 1.21) ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v2 on Sat May 25 2019 18:49:41 GMT-0700 (Pacific Daylight Time) ; updated manually to reflect changes for RRF3 ; General preferences M111 S0 ; Debug off G21 ; work in mm G90 ; Send absolute coordinates... M83 ; ...but relative extruder moves ; ; Network M550 P"Red" ; Set machine name M552 S1 ; Enable network ;*** Access point is configured manually via M587 and stored on wifi card (not on regular memory card), see above comments M586 P0 S1 ; Enable HTTP M586 P1 S0 ; Disable FTP M586 P2 S0 ; Disable Telnet M581 P1 T0 S0 R0 ; configure external trigger for emerg stop ; map axis M584 X0 y1 ; set drive mappings - x=drive 0, y=drive 1 M584 Z2:4 ; z = drive 2 and 4 M584 E3 ; extruder is drive 3 M671 X-27:255 Y332:255 S3 ; define where the two different z screws are located (x -30 and 530, y at 250 and 250), S is the maximum correction to be applied in mm ; Drives M569 P0 S0 ; Physical drive 0 goes backwards (x) M569 P1 S0 ; Physical drive 1 goes backwards (y) M569 P2 S1 ; Physical drive 2 goes backwards (Z left) M569 P3 S0 ; Physical drive 3 goes backwards (E0) M569 P4 S0 ; Physical drive 4 goes backwards (Z right) ; NOTE: when using only one of the two driver 2 connectors, the second, unused connector needs to be jumpered as they are configured serially on the board !!!!! ; The M92 commands to set steps/mm should either come after any M350 command to set microstepping, or else the M92 parameters should be correct for the default x16 microstepping. This is because when you change microstepping, the steps/mm are automatically adjusted to take account of the change in microstepping. M92 X80.20 Y80.15 Z400.00:400.00 E400 ; Set steps per mm - Z was at 406 but large print showed that 400 is the correct number. E was 405, changed to 400 as well M906 X1500.00 Y1500.00 Z800:800 E800 I50 ;:800 I50 ; Set motor currents (mA) and motor idle factor in per cent extruder motor current was too high at 800 ma, trying to prevent filament from being ground down so reduced drive to 600 ma M350 X16 Y16 Z16:16 E16 I1 ; Configure microstepping with interpolation for x,y,z,E0 M98 P"stepper_settings_default.g" ; call stepper_settings_default.g in order to set default parameters ; Axis Limits ; M208 x-14 Y4 Z-1.5 S1 ; Set axis minima, this is what the axis are set to after homing M208 x335 Y298 Z280 S0 ; Set axis maxima ++++++++++++++++++++ does not account for x offset of second extruder ; set up BlTouch ; set up probe type M558 P9 C"^zprobe.in" H3 F60 T6000 A10 R1.25 S0.03 B1 ; Set Z probe type/mode 9. H=Dive Height. F=Speed probe speed, ; T= speed between probe points, A10 = probe up to 10 times ; R1.25 = allow settlement time, S0.008 = two consecutive probes need ; to be within 0.008 mm, ; B1 = turn off heat for the actual probing ; B0 = leave heating on M950 S0 C"exp.heater3" ; create servo/gpio 0 on heater 3 on expansion connector ; set up offset of probe to nozzle 1 ; X is negative if probe is in front of nozzle towards front of printer ; Y is negative if probe is towards y=0 of nozzle ; We start with a Z offset of 0.0mm in regards to actual probe activation and factual distance. ; This value will be adjust later on, to match our setup. ; Important: It is important to have Z-offset at 0 before calibrating. ; P is the value needed to trigger the BLTouch. Doesn't seem to matter ... G31 x-29.4 y2.8 z3 ; set offset of probe from nozzle. If the probe is to the left of the nozzle the offset is negative, if the probe is in front of the nozzle it is negative ; if the nozzle is too low then lower the Z offset amount (subtract the amount needed to establish correct clearance) ; Endstops M574 X1 S1 P"xstop" ; configure active-high (S1)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 M950 J1 C"e1stop" ; configure E1 stop (e1stop) as input pin 1 (J1) M574 Z1 S2 ; Z endstop is the z probe both Z0 and Z1 seem to work to activate probe and not use regular endstop, home to minimum ; Emergency stop button M581 P1 T0 C0 S1 ; configure input pin number 1 (P1) .... T0 = emergency stop on trigger, C0 = allow trigger at any time (not just during print), S0 triggers on falling edge (NC) ; Heaters ; note that this printer uses an external power control box (SCR based) to power the bed. If that box is not present or disconnected the bed will not heat up. M308 S0 P"bedtemp" Y"thermistor" T100000 B4900 ; configure sensor 0 as thermistor on pin bedtemp (main bed temp sensorsor) ; measured 68.5 degrees when bed temp was set to 70 degrees (with B4200) - seems fine, took a long time to equalize ; was B4200 but read considerably higher than actual temp - changed to B4900 M950 H0 C"bedheat" T0 ; create bed heater output on bedheat and map it to sensor 0 M140 H0 ; set bed heater to heater zero M143 H0 S120 ; set temperature limit for heater 0 to 120C M307 H0 B0 S1.00 ; disable bang-bang mode for the bed heater and set PWM limit ; not used ;M308 S1 P"e0temp" Y"thermistor" T100000 B3700 ; configure sensor 1 as thermistor on pin e0temp ... (this is the hot end sensor) ; was B4200 but B3700 was a better match with 200 set temp giving 205 actual and 250 set temp giving 246 actual ; Tool heaters and sensors ;------------------------------------------------------------------------------- M308 S1 P"e0temp" Y"thermistor" T100000 B4200 ; 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 M143 H1 S300 ; set temperature limit for heater 1 to 300C M307 H1 B0 S1.0 ; disable bang-bang mode for the nozzle heater and set PWM limit ; Fans ; FAN1 is set up as a thermostatically-controlled fan by default because it is typically used to control the hot end heatsink fan. ; To use it as a normal controlled fan, you must first cancel thermostatic mode by sending M106 P1 H-1. ; note that fan1 is heatsink fan, fan 0 is first tool fan M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency M950 F1 C"fan1" Q500 ; create fan 1 on pin fan1 and set its frequency M950 F2 C"fan2" Q500 ; create fan 2 on pin fan2 and set its frequency ;M106 P0 S1 H1 T45 ; set fan 1 value. Thermostatic control is turned on. This fan turns on if heater1 is over 45 degrees ; Tools ; NOTE: G10 COMMANDS IN CONFIG-OVERWRITE.G OVERWRITE THESE PARAMETERS !!!!!!!!!!! M563 S"Nozzle 0" P0 D0 H1 F0 ; define tool 0 (P0), first available extruder which was defined as drive 3 with M584 above (D0), heater 1 (H1), fan 1 (F1) G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C ; set up filament sensors M591 D0 P1 C"!e0stop" S1 ; enable (S1) filament sensor (normal switch) on Extruder 0 , connected to E0 sensor ;M591 D1 P1 C"e1stop" S1 ; enable (S1) filament sensor (normal switch) on Extruder 1 , connected to E1 sensor ; Automatic power saving M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; Set voltage thresholds and actions to run on power loss ; Custom settings are not configured ; Mesh grid ; note that probing macros overwrite this ! ;M557 X0:290 Y0:290 p7:7 ; Set mesh grid to start sampling at x0 y0 + offset of probe and go to x290 and y290 plus probe offset, sample 7 * 7 matrix M557 X25:280 Y25:280 P3:3 ; set area to be probed and number of probe points ; set up default heater parameters from config-override.g ; M501 to load values stored in config-override.g should be at or near the end, so that the commands in config-override.g don't get overridden themselves. ; Miscellaneous ; ; for pressure advance calibration use ; http://www.sternwolken.de/tmpup/3dprint/pressureadvance2.py ; change parameters as needed and then run python3 pressureadvance2.py > output.gcode ; ;g31 x-23 y-2.8 ;M98 P"/sys/Toffset.g" ; Set tool offset x, y, z ;M570 H0 P30 T50 ; change the default heater error parameters H0 - bed heater, P10 - temperature anomality must persist for 10 seconds, ; T20 - permitted temperature excursion ;M570 H1 P10 T20 ; reconfigure hot end fault trip point M501 ; Load saved parameters from non-volatile memory ;-------------------------------------------------------------------------------------------------------------------- ; heater fault ; extend fault trigger time to avoid fault when going from standby to active heater mode or preheat to active mode ;-------------------------------------------------------------------------------------------------------------------- M570 H1 P6 T15 ; An anomaly on heater 1 must persist for 6 seconds, and must be greater or less than 15C from the setpoint, to raise a heater fault. ******************************************************************************************************************** ; set pressure advance ******************************************************************************************************************** M572 D0 S0.15 ; adjust processor temperature display M912 P0 S-10 ; Processor temperature is about 10 degrees lower than un-calibrated reading says T0 ; select first/default/only toolWhen I click on Heater 1 in DWC, I also get a message box that says "The M568 command is no longer needed"
-
@jens55
T0sets the current tool heaters to active. -
@chrishamm, ok, I can remove the "T0" in config.g but as I indicated, that puts the tool heater in the 'off' state and clicking on the heater does not change the status. It doesn't cycle through 'active', 'standby' and 'off' so something is amiss (plus where does the M568 message come from?).
What would cause the heater not to cycle through it's states. Could I have something wired incorrectly?
Even when the SSR for the bed heater is physically missing, I can still step through the three states of the bed heater and if I set the bed heater to active I get a heater fault since the SSR is not connected. -
Verified that the thermistor for the nozzle heater reports correctly. Tried things with the nozzle heater disconnected and there is no change in how DWC reacts. I am still stuck in the 'off' mode.
-
@jens55 I can't for the life of me see anything amiss in your config.g. Your heater and tool definitions look fundamentally the same as mine (except that I use different pins) yet I can cycle through active/standby/off just fine. So, clutching at straws I note that your M307 doesn't have any PID parameters. I guess this is because you save them to config_override .g (I see you have M501)? So is there anything else in config.g_override.g that might be buggering things up? Other than that, the only other thing I can think of is does your DWC version match your firmware version?
-
just to make sure @jens55 -- RRF and DWC both are on the same version, and you have disabled all script blockers for the DWC page?
Also, in the console, can you switch the tool modes using G10 command?
-
@deckingman, great idea to check firmware! .... I decided to upgrade while I was at it. Downloaded 3.4.6, uploaded it, asked for it to be installed and promptly bricked the Duet2
I am currently in the process of re-learning how to bring a dead duet back to life. Even though I went through that not too long ago, I am having old fart issues
Bossa can't connect ....
Working on it .... -
@deckingman, you were right on the nose. While I have a ton of stuff to sort out from my issues of the last two days, clicking on the heater now steps through all the usual states.
-
@jens55 Thanks for letting me know. It was just a wild guess, but given that your configuration looked fine, it had to be something like that.
-
undefined dc42 marked this topic as a question
-
undefined dc42 has marked this topic as solved
