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

    Heated chamber PID and 3.4 stable

    Scheduled Pinned Locked Moved
    General Discussion
    5
    23
    909
    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.
    • Tinchusundefined
      Tinchus @martin7404
      last edited by

      @martin7404 this topic is not for a debate about this I guess. But you chamber limit is 70, is way low compared to me 180 degrees chamber. At those temperatures, using bang bang is somehow complicated in order to mantein stable temperatures across the chamber for many reasons. Reaching 70 degrees is easy for my chamber with the actual "failed PID", the problem Im having is for reaching above 85 degrees, that is where I start getting errors.

      This arise with version 3.4, with previous 3.3, I had the PID working with no problems, and those values also dont work with version 3.4

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

        Does the PID tune fail at the same point each time?
        Does it succeed when tuning to a lower temperature?

        Z-Bot CoreXY Build | Thingiverse Profile

        Tinchusundefined 1 Reply Last reply Reply Quote 0
        • Tinchusundefined
          Tinchus @Phaedrux
          last edited by

          @phaedrux The tunning finishes and reports me the value, I saved them using M500 and I checked those values are in the override file. Printer has been rebooted too and those values are being used. But when I try to reach the same temperature the calibration was suposed to tune, I got the errors described above.

          1 Reply Last reply Reply Quote 0
          • Tinchusundefined
            Tinchus
            last edited by

            More information I forgot: definition of the heater is this:

            M308 S0 P"temp0" Y"thermistor" T100000 B4138 A"chamber" ; sensor 0 en pin temp0
            M950 H0 C"out7+out8" T0 ; pins out 7 and out8 for chamber heaters
            M307 H0 R0.015 K0.083:0.083 D150.25 E1.35 S0.90 B0 ; enable PID mode for the chamber heater and set PWM limit
            M141 P0 H0 ; Define H0 as a chamber heater

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

              What's the reason you're using only a 0.9 PWM value?

              Z-Bot CoreXY Build | Thingiverse Profile

              1 Reply Last reply Reply Quote 0
              • Tinchusundefined
                Tinchus @Tinchus
                last edited by Tinchus

                @Phaedrux voltage tension at home is over normal values. I should have 220V, but I have 235 V always!. The electric resistor I have is meant to be used on 220V, if I use it at 235 it burns. So by reducing the pwm to 0.9 I can use it without the need to get a new one able to work at 235V.
                I already tried both ways: I tried to tune the PID with the PWM value at 0.9 and also at 1.0 without success. Each time tunning finishes, I get what are suposed to be the values for PID. Then those values... just dont work.

                I couldnt find an explanation of what te new PID values mean or how to tune them manually, is that information available?

                1 Reply Last reply Reply Quote 0
                • Tinchusundefined Tinchus referenced this topic
                • Tinchusundefined
                  Tinchus
                  last edited by

                  I have ran the tunning again. Tunning ends and I get this (in the case of tunning being made for a temp chamber of 85 degrees):

                  M307 H0 R0.097 K0.077:0.000 D93.61 E1.35 S0.90 B0

                  I have just noticed that second pair of values on the KK0.077:0.000

                  My config includes 2 heaters separated, so just in case 1 burns I can easily detect wich one, replace it, etc.

                  Version 3.4 allows me to put tgether 2 heater under the same control, so my config uses:

                  M308 S0 P"temp0" Y"thermistor" T100000 B4138 A"chamber" ; configuro sensor 0 en pin temp0
                  M950 H0 C"out7+out8" T0 ; create bed heater output on out0 and map it to sensor 0, pins out 7 and out8
                  M307 H0 R0.097 K0.077:0.000 D93.61 E1.35 S0.90 B0 ; enable PID mode for the chamber heater and set PWM limit
                  M141 P0 H0 ; Define H0 as a chamber heater

                  As I said, when I try to heat up the chamber, it goes to something like 60/70 degrees and I get a fault. Can be those cero values on the second pair of the K be a problem?

                  Thanks in advance

                  baird1faundefined 1 Reply Last reply Reply Quote 0
                  • baird1faundefined
                    baird1fa @Tinchus
                    last edited by

                    @tinchus I have the same issue changing from 3.3 to 3.4, my chamber heaters M307 values don't seem to work anymore and I too get the heater0 rising too slowly error.

                    I find that odd that I'm getting a heater0 error since my chamber is heater3. But that aside I've tried to change the vales to get the heater to work and I'm having a tough time. My chamber is much slower heating than yours and it takes a very long time to even reach 50C. I've been running the autotunner now for several hours.

                    Phaedruxundefined Tinchusundefined 2 Replies Last reply Reply Quote 0
                    • Phaedruxundefined
                      Phaedrux Moderator @baird1fa
                      last edited by

                      @baird1fa said in Heated chamber PID and 3.4 stable:

                      I find that odd that I'm getting a heater0 error since my chamber is heater3.

                      I think that is a bug in 3.4 that has been fixed in 3.4.1 RC1.

                      When a heater fault event was generated on the main board, the heater number and CAN address parameters were swapped. This resulted in the heater number always being reported as 0.
                      When a filament error event was generated on the main board, the extruder number and CAN address parameters were swapped. This resulted in the extruder number always being reported as 0.

                      Would you be able to test 3.4.1 RC1?
                      https://github.com/Duet3D/RepRapFirmware/releases/tag/3.4.1rc1

                      Z-Bot CoreXY Build | Thingiverse Profile

                      Tinchusundefined 1 Reply Last reply Reply Quote 0
                      • Tinchusundefined
                        Tinchus @Phaedrux
                        last edited by

                        @phaedrux Im not good on this github stuff, How can I upgrade to 3.4.1 RC1? I usually do the update using th sudo apt commands

                        Phaedruxundefined 1 Reply Last reply Reply Quote 0
                        • Tinchusundefined
                          Tinchus @baird1fa
                          last edited by

                          @baird1fa In my case, heater 0 is my chamber heater

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

                            @tinchus said in Heated chamber PID and 3.4 stable:

                            @phaedrux Im not good on this github stuff, How can I upgrade to 3.4.1 RC1? I usually do the update using th sudo apt commands

                            @tinchus said in Heated chamber PID and 3.4 stable:

                            The board is a duet3 running in SBC mode, 3.4 version

                            In your case running a SBC you would need to use these directions to switch to the unstable package feed on the Pi.

                            https://docs.duet3d.com/User_manual/Machine_configuration/DSF_RPi#switch-to-unstable-packages

                            Z-Bot CoreXY Build | Thingiverse Profile

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