Random Temperature Issue



  • Hello Everyone,

    I am having a very random hotend temperature issue. I can not recreate it, nor do I know when it will happen.

    I have my Gcode set up to first set and wait for the bed to reach temperature, then it sets and waits for the hotend to reach temperature. But once in awhile, it will either jump past the hotend setting.

    For example... I will start a print, the bed gets to temperature, then my printer will start the printing process (home, then start print). During this time the hotend is getting upto temperature, and it starts extruding filament before the hotend is at the temperature needed to extrude. So I grind the filament because the hotend is not hot enough.

    Other example... I will start a print, the bed gets set, and print starts, but hotend temperature is never set, and a warning pops up saying could not extrude (because hotend is to cold).

    With both of these examples, I am printing from the SD card (no USB connected), and if I cancel and reprint the same file, everything works like it should. Not using a display, everything is being controlled through the web GUI. I am running the latest firmware (non-bata). I can't remember seeing this happen on the previous firmware.

    This is aggravating because I can't reproduce this on command. And I don't know when it will do it.

    Thanks


  • administrators

    It sounds as though your GCode file isn't waiting for hot end temperature to be reached before starting the print. Please post the first 50 or so lines (not counting comment lines) of a GCode file that you have had this problem with.



  • I will post part of my Gcode tonight when I get off work.

    I originally thought the issue was with the Gcode file. But then I questioned myself... Why is it only doing it once? I do not change anything. Once I see the problem, I stop the print, then restart the exact same file, and the problem does not happen. Even if I reset (even pull power) the DuetWiFI, the problem will not show up again on the exact same file that showed the problem. That is what is driving me up the wall, I can't recreate it ondemand.


  • administrators

    @iamturbo1978 said in Random Temperature Issue:

    I will post part of my Gcode tonight when I get off work.

    I originally thought the issue was with the Gcode file. But then I questioned myself... Why is it only doing it once? I do not change anything. Once I see the problem, I stop the print, then restart the exact same file, and the problem does not happen. Even if I reset (even pull power) the DuetWiFI, the problem will not show up again on the exact same file that showed the problem. That is what is driving me up the wall, I can't recreate it ondemand.

    Perhaps because the second time, when you start the print the nozzle is already nearly at operating temperature?



  • @dc42 if that was the case, what about the other situation... The hotend would not even be powered up. The web interface would say "standby" for the extruder.

    I think I might of just figured it out though. I just changed the setup from a dual extuder, back to a single. I could of sworn I changed everything back to a single extruder in the configuration file. Maybe it is getting stuck on dual extruder mode, and it is switching to another tool that is not showing up on the web interface. I don't think my gcode sends a "T0" since my slicer is set up for a single extruder. I'll have to check tonight.



  • OK, I did some checking in my config file, and there is nothing I can see that would make a hidden tool that would stop my hotend from being turned on when it should.

    Included is my config file

    Here is a few lines of one file that did not activate the hotend, but did activate after I restarted the print.

    G90
    M83
    M106 S0
    M140 S70
    M190 S70
    M104 S245 T0
    M109 S245 T0
    ; *** Event Logging ***
    M929 P"eventlog.txt" S1 ; start logging to file eventlog.txt
    M111 P5 S1 ; debug heat
    ; *** Motor Fans ***
    M106 P2 S255
    ; *** Pressure advance ***
    M572 D0 S0.0
    ; *** BLTouch ***
    M280 P3 S160 I1 ; BLTouch alarm release
    G4 P100 ; delay for BLTouch
    ; *** Home and Bed Mesh ***
    G28 ; home
    ;G29 S1 ; load bed mesh
    ;M376 H10 ; Set bed compensation taper to 10mm
    ; *** Prime Hotend ***
    G0 X0 Y0 F9000 ; Go to front
    G0 Z0.3 ; Drop to bed
    G92 E0 ; zero the extruded length
    G1 X40 E25 F500 ; Extrude 25mm of filament in a 4cm line
    G92 E0 ; zero the extruded length
    G1 E-1 F500 ; Retract a little
    G1 X80 F6000 ; Quickly wipe away from the filament line
    G1 Z0.3 ; Raise and begin printing.
    G1 E-3.0000 F3600
    G1 Z0.075 F600
    ; process Process1
    ; layer 1, Z = 0.075
    T0
    ; tool H0.150 W0.540
    ; skirt
    G1 X83.052 Y107.255 F24000
    G1 E3.0000 F1080
    G1 X83.250 Y107.172 E0.0065 F1080

    Hopefully I can figure this out.

    Config File: 0_1534198751719_config.txt



  • I think your T0 command comes too late. Try adding T0 to the end of your config.g so that it is selected at startup.



  • @phaedrux said in Random Temperature Issue:

    I think your T0 command comes too late. Try adding T0 to the end of your config.g so that it is selected at startup.

    Thanks, I will give it a try. Hopefully that is all that is wrong.


  • administrators

    Try that, however unless you are using very old firmware then the M109 T0 command earlier in the file ought to select T0.


Locked
 

Looks like your connection to Duet3D was lost, please wait while we try to reconnect.