Duet3D Logo Duet3D
    • Tags
    • Documentation
    • Order
    • Register
    • Login

    Warning or Pause on heater failure detection

    Scheduled Pinned Locked Moved
    Tuning and tweaking
    3
    12
    581
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • Phaedruxundefined
      Phaedrux Moderator
      last edited by

      Please post your config.g and the gcode you're trying to print.
      What does your heater graph look like?
      Was the heater at temp or not?

      Z-Bot CoreXY Build | Thingiverse Profile

      1 Reply Last reply Reply Quote 0
      • toufou54undefined
        toufou54
        last edited by

        It happen on all my prusaslicer generated gcodes, just after the start gcode, I didn't found any M104 S1 in the code.
        I'll send the code tomorrow now, going to sleep right now.

        But yes the gcode seems to send a heater temp to 1 just before print and the warning came later when it detect that the temp is to low to extrude, but it does not stop the print !

        1 Reply Last reply Reply Quote 0
        • toufou54undefined
          toufou54
          last edited by

          here the begining of one gcode file:

          ; generated by PrusaSlicer 2.2.0+win64 on 2020-05-24 at 17:05:55 UTC
          
          M107
          
          M582 T1 ; check if filament is present
          
          M220 S100 ;Reset Feedrate
          M221 S100 ;Reset Flowrate
          
          M140 S55 R40 ; set bed temp
          M190 S55-10 ; wait for bed temp
          M104 S210 ; set extruder temp
          
          M300 S40 P10 ; chirp
          
          M118 P3 S"HOMING" ; message HTTP
          M118 P4 S"HOMING" ; message TELNET
          
          G28 ; Home all axes
          ;M420 S1; restore manual mesh
          
          M300; beep
          G92 E0 ;Reset Extruder
          G1 Z2.0 F3000 ;Move Z Axis up
          G1 X5 Y20 Z2.0 F3000.0 ; Move to start position
          M109 S210 ; wait for extruder temp
          G1 X5 Z0.3
          G1 X5 Y200.0 Z0.3 F1500.0 E15 ; Draw the first line
          G1 X5 Y200.0 Z0.3 F5000.0 ; Move to side a little
          G1 X5.4 Y20 Z0.3 F1500.0 E30 ; Draw the second line
          G92 E0 ; Reset Extruder
          G10 S1; retract
          G1 Z10 F3000 ; Move Z Axis up
          G1 X30
          G11; recover after retraction G10
          
          M118 P4 S"PRINT_START" ; message TELNET
          G21 ; set units to millimeters
          G90 ; use absolute coordinates
          M82 ; use absolute distances for extrusion
          G92 E0
          ; Filament gcode
          G1 Z0.260 F30000.000
          G1 E-3.00000 F2700.00000
          G92 E0
          G1 X64.064 Y47.624 F30000.000
          G1 E3.00000 F2700.00000
          G1 F1200.000
          G1 X65.084 Y46.449 E3.07805
          G1 X66.328 Y45.514 E3.15611
          G1 X67.739 Y44.860 E3.23416
          G1 X100.092 Y36.264 E4.91391
          G1 X101.141 Y36.067 E4.96746
          
          zerspaner_gerdundefined 1 Reply Last reply Reply Quote 0
          • Phaedruxundefined
            Phaedrux Moderator
            last edited by Phaedrux

            Try adding T0 to the start of your start gcode so that the first tool is activated. You can also add it to the end of config.g if it's not there already to have the tool activated at startup.

            Also, M104 S210 ; set extruder temp sets the temp and does not wait. Use M109 instead if you want it to wait for the temp to be reached before proceeding.

            https://duet3d.dozuki.com/Wiki/Gcode#Section_M109_Set_Extruder_Temperature_and_Wait

            Z-Bot CoreXY Build | Thingiverse Profile

            1 Reply Last reply Reply Quote 0
            • zerspaner_gerdundefined
              zerspaner_gerd @toufou54
              last edited by

              @toufou54

              It doesn't look right to me:

              G10 S1; retract

              https://duet3d.dozuki.com/Wiki/Gcode#Section_G10_Retract

              Board: Duet WiFi 1.03 | Firmware Version: 3.1.1 | WiFi Server Version: 1.23 | Web Interface Version: 3.1.1

              toufou54undefined 2 Replies Last reply Reply Quote 1
              • toufou54undefined
                toufou54 @zerspaner_gerd
                last edited by

                @zerspaner_gerd you are certainly right, I will modify this (this is my gcodes than I uses on Marlin, I just went to Duet a few days ago...)

                And btw T0 is not the solution, tested without luck.

                Thanks guys, I'll post results when I could try

                1 Reply Last reply Reply Quote 0
                • toufou54undefined
                  toufou54 @zerspaner_gerd
                  last edited by toufou54

                  @zerspaner_gerd It was that, thanks !!

                  but now I have a new error, I don't think it's relative but appeared right after the change :
                  Error: M106: Fan number 2 not found

                  It appear twice, the only call to M106 en config is this :

                  ; 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

                  No call to a fan number 2...

                  Thanks

                  1 Reply Last reply Reply Quote 0
                  • Phaedruxundefined
                    Phaedrux Moderator
                    last edited by

                    Post the gcode file that produces that error please. Along with your full config.g

                    Z-Bot CoreXY Build | Thingiverse Profile

                    1 Reply Last reply Reply Quote 0
                    • toufou54undefined
                      toufou54
                      last edited by

                      Very weird but errors disappears as they came...

                      My errors are disappears now (at least those, I have others..)

                      But what about the warning and not a critical default and automatic print stop in case of heater fault ???

                      1 Reply Last reply Reply Quote 0
                      • Phaedruxundefined
                        Phaedrux Moderator
                        last edited by

                        Post the gcode file that produces that error please. Along with your full config.g

                        Z-Bot CoreXY Build | Thingiverse Profile

                        1 Reply Last reply Reply Quote 0
                        • toufou54undefined
                          toufou54
                          last edited by

                          that's ok now thank you , I just have Z stall height errors, I need to tune that.

                          I just want to know how can it be done, make an emergency stop in case of heater failure (or at least a pause during the print).
                          Is it possible ?

                          1 Reply Last reply Reply Quote 0
                          • First post
                            Last post
                          Unless otherwise noted, all forum content is licensed under CC-BY-SA