Marlin: BED PID Tune not working

[mesnik]

---

Bug Report

• Description: PID for Bed autotune failing
• Expected behaviour: system to run the autotune

• Actual behaviour: error message: "Heating failed. PRINTER HALTED Please reset"

• Steps to reproduce:

  • in Simplify3D, Communication's tab, run commad M303 E-1 C5 S80
    Marlin_27Dec17_v1.zip

First time writing in here! Looks very nicely organized!! I have been using Skynet3D for the last year and decided to change to Marlin. Everything seems to be normal, prints are great and all. The only issue I am facing is to run the Bed PID autotune. I reloaded Skynet and ran the Bed PID autotune from there fine. Reflashed Marlin and still getting error. So I must be missing a configuration somewhere... I did a search and couldn't find the answer...

Thanks for the help!!!!

[revilor]

What exactly happens to the bed temperature when you run PID autotune? Is the bed heating but very slowly, or not heating at all? And are bed PID parameters in your Configuration.h (DEFAULT_bedKp etc.) the ones you got from Skynet3D autotune?

[mesnik]

Thanks for the reply!!

So nothing happens. The bed doesn’t heat up.

And yes, the info I loaded into Configuration.h was what I was using on Skynet3D autotuned.

What is weird to me is that the bed runs normal when I print something...

[revilor]

Well, the job of the PID controller is to hold the bed temperature as close to the target as possible. From ambient to target temperature it's 100% power anyway. So you could try to manually heat the bed up to 75° or so and start PID autotune from there.

PID tuning was a little bit tricky for my heated bed too, because the required settings to avoid huge overshoots when heating up also mean that it takes some time in the beginning before some effect on bed temperature is visible at all. One could try to set WATCH_BED_TEMP_PERIOD to a very high value in that case, but preheating the bed for PID tuning did the job for me.

[mesnik]

Thanks for the suggestion. Unfortunately it did not work...

As the message says, it halted and the both temps (extruder and bed) just shut off.

: (

[patrovite]

Hi,

I had the same problem on my Anet A8 with the firmware 1.1.8.

[mesnik]

Ah! Good! I mean, bad for you, but good that I am not the only odd ball out here (as far as this goes...hahahaha!)

[xkilowatts]

Is it just your bed? Or hotend as well? I can't PID tune either, as soon as I send the M303 command via Terminal on Octoprint it kills the printer, doesn't even give it a chance to start heating.

[mesnik]

Funny enough, it is the bed only!!??

[galluslongus]

Try to disable

define THERMAL_PROTECTION_BED

For PID Tuning, after Tuning Switch it on again.

[mesnik]

You are a GENIUS!!! It worked perfectly!!!! Thanks so much for posting!!!

HAPPY NEW YEAR!!

[houseofbugs]

This is a bug and you should not have to turn that off to PID tune the bed. I have submitted a report as well. Just tested on 2 different machines running 1.1.8 release.

[mesnik]

Thanks for checking into it!!!

[thinkyhead]

@RowanMeara — I've been looking over the M303 thermal protection code and can't locate the source of the issue. Apparently it only applies to the bed thermal protection, and it throws the error quickly. I will do some more testing later today, but maybe you can spot the cause…?

[galluslongus]

Yes, it only happens on Bed Pid Tuning. I copied my working PID setting from 1.1.6 to 1.1.8 config to be sure it works properly. In normal printing there is no issues. But when you try to Tune your PID for the Bed again, the thermal protection comes in quickly. My workaround is to disable thermal protection for the bed during the pid tuning and enable after it.

[revilor]

PR #9037 fixes the issue, or setting WATCH_BED_TEMP_PERIOD in Configuration_adv.h to no more than 127 seconds

[xeddog]

I have just completed a new install of a RAMPS 1.4 board and Marlin 1.1.8. I just wanted to add that I have this problem with the bed, AND the nozzle. I'm not sure if this matters, but it happens when using Octoprint terminal and entering the command, or when using the control box menu. Hopefully a fix will resolve both.

Wayne

[thinkyhead]

@xeddog — Please test with the latest bugfix-1.1.x (and/or bugfix-2.0.x) branch to see where it stands. If the problem has been resolved then we've done our job. If you still see the bad behavior we should investigate further.

[xeddog]

Side question if I may. I have only read a little, but it seems like Marlin 2.0 is mostly restructuring the code and adding 32-bit processor support. Are any new features being added for the 8-bit users amongst us?

Thanks,

Wayne

---

From: Scott Lahteine [e-mail]
Sent: Friday, February 23, 2018 8:09 AM
To: MarlinFirmware/Marlin
Cc: xeddog; Mention
Subject: Re: [MarlinFirmware/Marlin] BED PID Tune not working (#8942)

@xeddoghttps://github.com/xeddog — Please test with the latest bugfix-1.1.x (and/or bugfix-2.0.x) branch to see where it stands. If the problem has been resolved then we can close this issue. If you still see the bad behavior we should investigate further.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/MarlinFirmware/Marlin/issues/8942#issuecomment-367938864, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AH8EQNNJAJM1iVHkM2qhFaD7fXooLrhPks5tXnJOgaJpZM4ROwTw.

[thinkyhead]

@xeddog — Marlin 2 for AVR has perfect parity with Marlin 1.1 at this time. However, 1.1.9 will be the last major Marlin 1.x.x release, so all users will be required to update to Marlin 2.0 for new features after that.