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

    Bed heater switches to standby randomly while printing

    Scheduled Pinned Locked Moved
    Duet Hardware and wiring
    3
    6
    201
    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.
    • Strider007undefined
      Strider007
      last edited by

      I have an Ultimaker clone, with a used Duet 2 WIFI. The heater appears rock solid viewing DWC until it switches to standby. I see the temp drop on DWC or if looking at the PanelDue, the normally red indicator turns yellow. I get no heater fault, or message. If I use either the PanelDue or the DWC I can easily reset the bed temp back to active. I've been saving my prints by setting my bed standby temp to 93C (2 degrees below my desired active temp). So far it has not slipped past the standby temp but what is going on.

      Note, the motherboard was purchase used from Europe and shipped over.It is a clone, and driver 0 was blown. Since I only need 4 drivers I just programmed around that issue.

      The system runs on a 12v supply but the bed heater is powered by mains with a SSR-25 controlling it so I don't believe it to be momentary PS sag. Possibly a memory issue? Running RRF3.5.1. Here is my config for this system.

      ; Configuration file for Duet WiFi (firmware version 3.5.1)
      ; executed by the firmware on start-up
      ;
      
      ; General preferences
      M575 P1 S1 B57600                              ; enable support for PanelDue
      G90                                            ; send absolute coordinates...
      M83                                            ; ...but relative extruder moves
      M550 P"U-2"                             ; set printer name
      
      ; Network
      
      ; WIFI on for home network
      M552 S1                                        ; enable network
      M586 P0 S1                                     ; enable HTTP
      ; No WIFI for stand alone, network off
      ; M552 S0                                      ; disable network
      ; M586 P0 S0                                   ; disable HTTP
      
      M586 P1 S0                                     ; disable FTP
      M586 P2 S0                                     ; disable Telnet
      
      ; Drives
      ;  Driver P0 is not functional
      M569 P1 S0                                     ; physical drive 1 goes backwards
      M569 P2 S1                                     ; physical drive 2 goes forwards
      M569 P3 S1                                     ; physical drive 3 goes forwards
      M569 P4 S0                                     ; physical drive 4 goes backwards
      M584 X1 Y3 Z2 E4                               ; set drive mapping
      M350 X16 Y16 Z16 E16 I1                        ; configure microstepping with interpolation
      M92 X80.00 Y80.00 Z1600.00 E400.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 X900 Y900 Z900 E490 I30                   ; set motor currents (mA) and motor idle factor in per cent
      M84 S90                                        ; Set idle timeout
      
      ; Axis Limits
      M208 X-98 Y-120 Z0 S1                         ; set axis minima
      M208 X112 Y90 Z300 S0                         ; set axis maxima
      
      ; Endstops
      M574 X1 S1 P"!xstop"                            ; configure switch-type (microswitch) endstop for low end on X via pin xstop, active low
      M574 Y2 S1 P"!ystop"                            ; configure switch-type (microswitch) endstop for high end on Y via pin ystop, active low
      M574 Z1 S1 P"zstop"                            ; configure switch-type (Optical) endstop for low end on Z via pin zstop, active high
      
      ; Z-Probe
      M558 P0 H5 F120 T6000                          ; disable Z probe but set dive height, probe speed and travel speed
      M557 X-90:90 Y-90:90 S20                       ; 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 R0.766 K0.379:0.000 D2.01 E1.35 S1.00 B0	; Auto tune provided values for PID mode 11-2022
      M140 H0                                        		; map heated bed to heater 0
      M143 H0 S100 A2										; shut heater off temporarily if tripped
      M143 H0 S110 A0                                 	; set temperature limit for heater 0 to 110C, set fault if tripped
      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 R2.371 K0.338:0.000 D10.03 E1.35 S1.00 B0 V11.8		; parameters derived from Autotune on 11-2022 PID mode.
      M143 H1 s250 A2										; shut heater off temporarily if tripped
      M143 H1 S260                                   		; set temperature limit for heater 1 to 250C
      
      ; Fans
      M950 F0 C"fan0"                                 ; create fan 0 on pin fan0 and set its frequency
      M106 P0 S0.0 H1 T45                             ; set heatsink fan 0 value. Thermostatic control is turned on at 45C
      M950 F1 C"fan1"                                 ; create fan 1 on pin fan1 and set its frequency
      M106 P1 S0.0                                    ; set part cooling fan 1 value. Thermostatic control is turned off
      
      ; Tools
      M563 P0 D0 H1 F1                               ; 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
      
      ; Custom settings are not defined
      M501											; Use settings in override file that were dervived from Auto tuning system
      
      

      Any insight would be appreciated.

      jay_s_ukundefined 1 Reply Last reply Reply Quote 0
      • jay_s_ukundefined
        jay_s_uk @Strider007
        last edited by jay_s_uk

        @Strider007 going into standby will turn he heater off unless you've set a standby temp
        You probably have something in your gcode that's doing it

        Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

        Strider007undefined 1 Reply Last reply Reply Quote 0
        • Strider007undefined
          Strider007 @jay_s_uk
          last edited by

          @jay_s_uk
          I considered that but the same gcode files print fine on my other two machines. It is only this machine that has this issue. This totally random. Some times it holds and performs normally, other times, it will switch the bed to standby before the print starts. I have done several prints where it dropped to standby multiple times. Setting bed standby to 94C is all that saves my prints.

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

            Check your gcode files for heater related commands?
            What slicer are you using? Is it set to use RepRap firmware gcode flavour?

            Z-Bot CoreXY Build | Thingiverse Profile

            Strider007undefined 1 Reply Last reply Reply Quote 0
            • Strider007undefined
              Strider007 @Phaedrux
              last edited by Strider007

              @Phaedrux
              Thank you. I currently use Cura 5.5.0. I will look over the several files that have exhibited this issue today but I run those same files on two other machines with no bed heater issues. Only this machine exhibits the unreported fault. That is the reason I believe it is something with this specific motherboard rather than the files. It does have driver0 damage; perhaps an EOS event hurt the processor.

              Can anyone suggest any diagnostics I could run while printing that might catch this fault? I'm assuming there is a latch or memory location that holds the "heater active" data. Can that be monitored, and capture what's going on?

              Yes Cura calls Reprap during file generation.

              Strider007undefined 1 Reply Last reply Reply Quote 0
              • Strider007undefined
                Strider007 @Strider007
                last edited by

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