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

bed heating issue on a new bed

Scheduled Pinned Locked Moved
Tuning and tweaking
3
13
1.1k
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.
  • undefined
    sunkenbier
    last edited by 10 Jul 2018, 14:24

    I just upgraded from a semecnc v3 heated bed to the v10. I have had issues with the bed holding temperatures over 70c. I tuned the bed successfully and saved it:

    Heater 0 model: gain 70.7, time constant 452.2, dead time 23.6, max PWM 1.00, calibration voltage 12.2, mode PID, inverted no, frequency default
    Computed PID parameters for setpoint change: P48.3, I0.467, D799.2
    Computed PID parameters for load change: P4

    I tuned the bed a second time successfully and saved it.

    Heater 0 model: gain 82.8, time constant 491.4, dead time 11.0, max PWM 1.00, calibration voltage 12.2, mode PID, inverted no, frequency default
    Computed PID parameters for setpoint change: P96.5, I1.314, D741.9
    Computed PID parameters for load change: P9

    When heating the bed to 90 I receive the below issue error:
    Error: Heating fault on heater 0, temperature rising much more slowly than the expected 0.0°C/sec

    Sometimes this happens within 10 min of the print job, other times it is when the bed is heating up to print. It is not consistant but has not made it farther than 10 min.

    Would this be a hardware issue or is there something Im missing in ensuring the duet is configured properly for the bed.

    undefined undefined 2 Replies Last reply 10 Jul 2018, 14:26 Reply Quote 0
    • undefined
      sunkenbier @sunkenbier
      last edited by 10 Jul 2018, 14:26

      As a note. I am running the most current duet firmware.
      I have also tried increasing the dead time without success.

      1 Reply Last reply Reply Quote 0
      • undefined
        Flo
        last edited by 10 Jul 2018, 14:29

        Have you tried to input the information in a M307 command in config.g?
        I’ve had the same issue with one of my printers heaters until I composed the M307 from the autotune result, as it was not reading the values from config-override.g

        undefined 1 Reply Last reply 10 Jul 2018, 14:58 Reply Quote 0
        • undefined
          dc42 administrators
          last edited by 10 Jul 2018, 14:38

          Is the bed actually capable of reaching 90C when run at full power, with the print cooling fan on?

          Duet WiFi hardware designer and firmware engineer
          Please do not ask me for Duet support via PM or email, use the forum
          http://www.escher3d.com, https://miscsolutions.wordpress.com

          undefined 1 Reply Last reply 10 Jul 2018, 14:57 Reply Quote 0
          • undefined
            sunkenbier @dc42
            last edited by sunkenbier 7 Oct 2018, 15:16 10 Jul 2018, 14:57

            @dc42 I know with my v3 I was able to hit 110c during prints. I normally ran it at 90 so I would imagine the v10 would be able to achieve the same results. The seemecnc site does not say what temp it should be able to hit but during the tuning it hit 90c

            1 Reply Last reply Reply Quote 0
            • undefined
              sunkenbier @Flo
              last edited by 10 Jul 2018, 14:58

              @flo Ill try manipulating the config.g. I had been making the modifications to the config-overide.g when I made changes in testing

              1 Reply Last reply Reply Quote 0
              • undefined
                dc42 administrators @sunkenbier
                last edited by 10 Jul 2018, 15:27

                @sunkenbier said in bed heating issue on a new bed:

                When heating the bed to 90 I receive the below issue error:
                Error: Heating fault on heater 0, temperature rising much more slowly than the expected 0.0°C/sec

                That message suggests that the bed temperature was below 90C but the temperature was not rising. it could be that your print cooling fan makes the difference between the bed reaching 90C and not. You could try tuning the bed heater with the effector lowered and the fan running.

                Duet WiFi hardware designer and firmware engineer
                Please do not ask me for Duet support via PM or email, use the forum
                http://www.escher3d.com, https://miscsolutions.wordpress.com

                undefined 1 Reply Last reply 10 Jul 2018, 16:03 Reply Quote 0
                • undefined
                  sunkenbier @dc42
                  last edited by 10 Jul 2018, 16:03

                  @dc42 As a test I heated the bed with no fans running and just the bed heated at 90c. It hit the 90c and held it for about 10 minutes. There were no spikes in the heat graph but then the temp just stopped heating which resulted in the below error.

                  8:12:16 AM
                  M140 S90
                  8:29:04 AM
                  Error: Heating fault on heater 0, temperature excursion exceeded 15.0°C

                  undefined 1 Reply Last reply 10 Jul 2018, 16:19 Reply Quote 0
                  • undefined
                    dc42 administrators @sunkenbier
                    last edited by 10 Jul 2018, 16:19

                    @sunkenbier said in bed heating issue on a new bed:

                    @dc42 As a test I heated the bed with no fans running and just the bed heated at 90c. It hit the 90c and held it for about 10 minutes. There were no spikes in the heat graph but then the temp just stopped heating which resulted in the below error.

                    8:12:16 AM
                    M140 S90
                    8:29:04 AM
                    Error: Heating fault on heater 0, temperature excursion exceeded 15.0°C

                    Strange, I don't see how that error can occur without the temperature deviating from 90C by at least 15C for a few seconds.

                    Duet WiFi hardware designer and firmware engineer
                    Please do not ask me for Duet support via PM or email, use the forum
                    http://www.escher3d.com, https://miscsolutions.wordpress.com

                    undefined 1 Reply Last reply 10 Jul 2018, 16:25 Reply Quote 0
                    • undefined
                      sunkenbier @dc42
                      last edited by sunkenbier 7 Oct 2018, 16:26 10 Jul 2018, 16:25

                      @dc42 said in bed heating issue on a new bed:

                      @sunkenbier said in bed heating issue on a new bed:

                      @dc42 As a test I heated the bed with no fans running and just the bed heated at 90c. It hit the 90c and held it for about 10 minutes. There were no spikes in the heat graph but then the temp just stopped heating which resulted in the below error.

                      8:12:16 AM
                      M140 S90
                      8:29:04 AM
                      Error: Heating fault on heater 0, temperature excursion exceeded 15.0°C

                      Strange, I don't see how that error can occur without the temperature deviating from 90C by at least 15C for a few seconds.

                      Although the display showed the heater status as active, the temperature just dropped as if it were turned off. It was not a sudden drop. It slowly just dropped down from 90 into the 70s over a minute or two

                      That's why I'm having such a hard time trouble shooting this. The errors seem so strange to me.

                      undefined 1 Reply Last reply 10 Jul 2018, 16:28 Reply Quote 0
                      • undefined
                        dc42 administrators @sunkenbier
                        last edited by 10 Jul 2018, 16:28

                        @sunkenbier said in bed heating issue on a new bed:

                        @dc42 said in bed heating issue on a new bed:

                        @sunkenbier said in bed heating issue on a new bed:
                        Although the display showed the heater status as active, the temperature just dropped as if it were turned off. It was not a sudden drop. It slowly just dropped down from 90 into the 70s over a minute or two

                        Did the temperature start to drop at the same time that the error message appeared, or before it?

                        Duet WiFi hardware designer and firmware engineer
                        Please do not ask me for Duet support via PM or email, use the forum
                        http://www.escher3d.com, https://miscsolutions.wordpress.com

                        undefined 1 Reply Last reply 10 Jul 2018, 16:36 Reply Quote 0
                        • undefined
                          sunkenbier @dc42
                          last edited by 10 Jul 2018, 16:36

                          @dc42 Temp dropped before the error. Message came up when it drop to 75.

                          undefined 1 Reply Last reply 10 Jul 2018, 17:31 Reply Quote 0
                          • undefined
                            dc42 administrators @sunkenbier
                            last edited by 10 Jul 2018, 17:31

                            So something caused heating to stop, perhaps a bad connection. I suggest you check the bed heater connections, in particular check that the screws in the bed heater output terminal block are still tight.

                            Another possibility is that the power supply overheated and reduced its output voltage. If it happens again, run M122 and check the max and min VIN voltages in the report.

                            Duet WiFi hardware designer and firmware engineer
                            Please do not ask me for Duet support via PM or email, use the forum
                            http://www.escher3d.com, https://miscsolutions.wordpress.com

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