Bed heating issue now that I'm on 3.1.1

PorscheHusky

Here are my config files
config-override.g
config.g

fcwilt

@PorscheHusky said in Bed heating issue now that I'm on 3.1.1:

Here are my config files
config-override.g
config.g

Hi,

I'm one of those difficult folks that ignores warnings in files.

I don't use config_override.g.

Yes when tuning heaters I used M500 to save the data in that config_override.g file BUT I then copy that information into my config.g file into the appropriate locations and delete config_override.g

Frederick

@fcwilt said in Bed heating issue now that I'm on 3.1.1:

Yes when tuning heaters I used M500 to save the data in that config_override.g file BUT I then copy that information into my config.g file into the appropriate locations and delete config_override.g

you don't even need to temporarily store it in config-override.g, you could just query the paramters an copy that into config.g from the gcode console afaik?

and thats fine when you know what you're doing, something it seems like OP also tried doing, however only with the heater and not the delta calibration and other contents of his override file.

given OP didn't add M501 to his config I guess thats the approach he wants to go down?

PorscheHusky

@bearer said in Bed heating issue now that I'm on 3.1.1:

@fcwilt said in Bed heating issue now that I'm on 3.1.1:

Yes when tuning heaters I used M500 to save the data in that config_override.g file BUT I then copy that information into my config.g file into the appropriate locations and delete config_override.g

you don't even need to temporarily store it in config-override.g, you could just query the paramters an copy that into config.g from the gcode console afaik?

and thats fine when you know what you're doing, something it seems like OP also tried doing, however only with the heater and not the delta calibration and other contents of his override file.

given OP didn't add M501 to his config I guess thats the approach he wants to go down?

So I did add the M501 to my root config.g as you mentioned and thanks to the links you provided. I checked before and afters of running a PID on the hotend first then the bed and it seems to be working. I'm about to try to perform a test of the bed to see if that nipped this problem in the arse; fingers crossed!
I'm just waiting for it to cool completely as if the printer had been sitting for a few hours/days, which is about23C-25C. Dang thing takes a long time to simmer down

PorscheHusky

@fcwilt
I think mine will make that file regardless if I delete it or not because that's where my delta calibration params are stored as well as the bed mesh if I'm correct in assuming. So I don't mind that it's there, just so long that it's doing what it's supposed to

I think mine will make that file regardless if I delete it or not because that's where my delta calibration params are stored as well as the bed mesh if I'm correct in assuming.

it will not re-create the file unless you re-do the calibration

So I don't mind that it's there, just so long that it's doing what it's supposed to

it wil do if you put ~~M500~~ M501 in config.g, if not it'll be ignored

fcwilt

@PorscheHusky said in Bed heating issue now that I'm on 3.1.1:

@fcwilt
I think mine will make that file regardless if I delete it or not because that's where my delta calibration params are stored as well as the bed mesh if I'm correct in assuming. So I don't mind that it's there, just so long that it's doing what it's supposed to

Hi,

The bed mesh (height map) is stored in the file heightmap.csv

And while relying on the config_override.g file is fine everything there can be moved into config.g.

There is nothing unique about the contents of config_override.g that requires it to be in that file.

Just FYI.

Frederick

PorscheHusky

@bearer
@fcwilt

It's sorted! mucho thanks!
The issue was indeed the lack of M501 in my config.g! Added that as instructed, waited for the printer to fully cool off then performed another autotune. After the autotune, I M500ed the new params and when I checked config-override, there were there!

So I waited for the machine to cool down again then heated the bed, it was still kind of slow ramping up but once it hit 30c and no faults/safeties tripped, I about jumped the roof!
It prints like a dream again and everything seems to be fully operational once again!
Thanks a lot, you two!

One more thing; I elected to run PID instead of Bang-Bang because I thought that was the original issue but now that it's working, I was concerned that maybe PID may not be ideal for my hardware?
Does PID put more stress on my components vs Bang-Bang? My Little Monster is fully stock; 24V PSU with the factory 12V silicon heated bed.

@PorscheHusky said in Bed heating issue now that I'm on 3.1.1:

I was concerned that maybe PID may not be ideal for my hardware?

elaborate? PID with a PWM frequency matching the type of heater should be fine for most setups.

dc42

PID is recommended; but if you are using an SSR to control the bed heater, reduce the PWM frequency to 10Hz (Q parameter in the M950 H0 command). Using bang-bang to control the bed heater can result in Z banding.

PorscheHusky

@dc42 I don't think Tevo Little Monsters came from the factory with SSRs. Maybe one of these days I can crack open the PSU and have a look.

I'm no electrician, so forgive me for any inaccuracies I may assume but I'm thinking all I'd have to look for is some external looking module inside the PSU box?

zapta

@bearer said in Bed heating issue now that I'm on 3.1.1:

you don't even need to temporarily store it in config-override.g, you could just query the paramters an copy that into config.g from the gcode console afaik?
and thats fine when you know what you're doing,...

This is what I am doing, editing the printed parameters into the M307 in my config.g file.

Always wonder why the Duet don't just prints the recommended M307 and planed to ask Duet3d to add it so here it is https://forum.duet3d.com/topic/17958/feature-request-please-have-m303-printing-the-recomanded-m307 . Feel free to support that request