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

    Bed heater faulting out after RRF 3.0 and later update

    Scheduled Pinned Locked Moved Solved
    General Discussion
    2
    12
    397
    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.
    • GBusy24undefined
      GBusy24
      last edited by

      I'm currently running RRF 3.4 on a corexy machine with an E3D PCB bed heater that worked fine til updating. Now it faults out saying it's heating too slowly. Here's my config.g. Let me know if more info is needed. I appreciate any help.

      Configuration file for Duet WiFi (firmware version 3.3)
      ; executed by the firmware on start-up
      ;
      ; generated by RepRapFirmware Configuration Tool v3.3.10 on Mon Jan 24 2022 20:50:56 GMT-0500 (Eastern Standard Time)

      ; General preferences
      G90 ; send absolute coordinates...
      M83 ; ...but relative extruder moves
      M550 P"CoreXY 1" ; set printer name
      M669 K1 ; select CoreXY mode

      ; Network
      M552 S1 ; enable network
      M586 P0 S1 ; enable HTTP
      M586 P1 S0 ; disable FTP
      M586 P2 S0 ; disable Telnet

      ; Drives
      M569 P0 S0 ; physical drive 0 goes forwards
      M569 P1 S0 ; physical drive 1 goes forwards
      M569 P2 S0 ; physical drive 2 goes forwards
      M569 P3 S0 ; physical drive 3 goes forwards
      M584 X0 Y1 Z2 E3 ; set drive mapping
      M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
      M92 X80.00 Y80.00 Z400.00 E852 ; 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 Z900.00 E1200.00 ; set maximum speeds (mm/min)
      M201 X500.00 Y500.00 Z20.00 E250.00 ; set accelerations (mm/s^2)
      M906 X800 Y800 Z800 E1200 I30 ; set motor currents (mA) and motor idle factor in per cent
      M84 S30 ; Set idle timeout

      ; Axis Limits
      M208 X0 Y0 Z0 S1 ; set axis minima
      M208 X320 Y185 Z300 S0 ; set axis maxima

      ; Endstops
      M574 X1 S1 P"!xstop" ; configure switch-type (e.g. microswitch) endstop for low end on X via pin xstop
      M574 Y2 S1 P"!ystop" ; configure switch-type (e.g. microswitch) endstop for high end on Y via pin ystop
      ;M574 X1 Y2 S1 ; X home to min. Y home to max. Normally Closed limit switches.
      M574 Z1 S2 ; Define Z to use Probe. Home to Min

      ; Z-Probe
      M950 S0 C"exp.heater3" ; create servo pin 0 for BLTouch
      M558 P9 C"^zprobe.in" H5 F120 T6000
      G31 P500 X-41.8 Y32.2 Z2.1
      M557 X10:320 Y0:190 S50 ; define mesh grid

      ; Heaters
      M308 S0 P"bedtemp" Y"thermistor" T100000 B4138 ; configure M307 H0 R0.378 K0.438:0.000 D2.11 E1.35 S1.00 B0sensor 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.352 K0.487:0.000 D1.76 E1.35 S1.00 B0; disable bang-bang mode for the bed heater and set PWM limit
      M140 H0 ; map heated bed to heater 0
      M143 H0 S120 ; set temperature limit for heater 0 to 120C
      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 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit
      M143 H1 S280 ; set temperature limit for heater 1 to 280C

      ; 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

      ; Tools
      M563 P0 D0 H1 F0 ; 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

      No such thing as spare time. No such thing as free time No such thing as down time. All you got is lifetime. Go!

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

        @gbusy24 have you reran PID tuning? the algorithm changed around RRF3.2

        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

        GBusy24undefined 1 Reply Last reply Reply Quote 0
        • GBusy24undefined
          GBusy24 @jay_s_uk
          last edited by

          @jay_s_uk I just reran it.

          No such thing as spare time. No such thing as free time No such thing as down time. All you got is lifetime. Go!

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

            @gbusy24 and is it still the same? what values do you have in config-override? are they different values to the ones in config?

            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

            GBusy24undefined 1 Reply Last reply Reply Quote 0
            • GBusy24undefined
              GBusy24 @jay_s_uk
              last edited by

              @jay_s_uk They're different.

              ; config-override.g file generated in response to M500 at 2022-06-26 17:57
              ; This is a system-generated file - do not edit
              ; Heater model parameters
              M307 H0 R2.429 K0.714:0.000 D5.50 E1.00 S1.00 B0
              M307 H1 R2.429 K0.714:0.000 D5.50 E1.00 S1.00 B0 V0.0
              ; Workplace coordinates
              G10 L2 P1 X0.00 Y0.00 Z0.00
              G10 L2 P2 X0.00 Y0.00 Z0.00
              G10 L2 P3 X0.00 Y0.00 Z0.00
              G10 L2 P4 X0.00 Y0.00 Z0.00
              G10 L2 P5 X0.00 Y0.00 Z0.00
              G10 L2 P6 X0.00 Y0.00 Z0.00
              G10 L2 P7 X0.00 Y0.00 Z0.00
              G10 L2 P8 X0.00 Y0.00 Z0.00
              G10 L2 P9 X0.00 Y0.00 Z0.00

              No such thing as spare time. No such thing as free time No such thing as down time. All you got is lifetime. Go!

              GBusy24undefined 1 Reply Last reply Reply Quote 0
              • GBusy24undefined
                GBusy24 @GBusy24
                last edited by

                @gbusy24 I guess I need to do an M500.

                No such thing as spare time. No such thing as free time No such thing as down time. All you got is lifetime. Go!

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

                  @gbusy24 assuming you haven't rebooted yes. If you have rebooted and the values in config are the correct ones, rerun that line (copy and paste it into the console) and then M500.
                  Or you could remove M501 at the end of your config and reboot

                  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

                  GBusy24undefined 1 Reply Last reply Reply Quote 0
                  • GBusy24undefined
                    GBusy24 @jay_s_uk
                    last edited by

                    @jay_s_uk I haven't rebooted and ran M500, but e-thing stays the same in config.g- override. Shouldn't they change?

                    No such thing as spare time. No such thing as free time No such thing as down time. All you got is lifetime. Go!

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

                      @gbusy24 yes, they should change. i suggest repid tuning and running M500 straight afterwards

                      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

                      GBusy24undefined 2 Replies Last reply Reply Quote 0
                      • GBusy24undefined
                        GBusy24 @jay_s_uk
                        last edited by

                        @jay_s_uk Okay

                        No such thing as spare time. No such thing as free time No such thing as down time. All you got is lifetime. Go!

                        1 Reply Last reply Reply Quote 1
                        • GBusy24undefined
                          GBusy24 @jay_s_uk
                          last edited by

                          @jay_s_uk Thanks for your help. Everything is sorted out and working proper now. No more faulting out.

                          No such thing as spare time. No such thing as free time No such thing as down time. All you got is lifetime. Go!

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

                            @gbusy24 glad to hear 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

                            1 Reply Last reply Reply Quote 0
                            • Phaedruxundefined Phaedrux marked this topic as a question
                            • Phaedruxundefined Phaedrux has marked this topic as solved
                            • First post
                              Last post
                            Unless otherwise noted, all forum content is licensed under CC-BY-SA