Startup error

General Discussion
1

Basic Information:

Printer Model: TwoTrees SP5 V3
MCU / Printerboard: MKS Robin Nano V3
Host / SBC BTT Pad7
klippy.log
klippy (1).log (123.7 KB)
config-20250328-114945.zip (2.3 KB)

Fill out above information and in all cases attach your klippy.log file (use zip to compress it, if too big). Pasting your printer.cfg is not needed
Be sure to check our “Knowledge Base” Category first. Most relevant items, e.g. error messages, are covered there

Describe your issue:

Suddenly today when starting Klipper I get this error:
Option ‘control’ in section ‘heater_bed’ must be specified

I can’t figure out why as i haven’t changed anything with the config and it’s been working for months. I’ve checked back and everything pertaining to this is unchanged. The only thing I have done was add some macros that back up configs to Github but haven’t even been able to get to the point where I can try running them. I’ve attached the printer.cfg file in case it might be useful but this is the part referred to.

[heater_bed]
heater_pin: PA0
sensor_type: EPCOS 100K B57560G104F # Stock
sensor_pin: PC0
min_temp: 0
max_temp: 100

Thanks

2

You can address the error by adding the required control: pid line. Your log indicates it was specified previously but then removed.

2 Likes
3

Hmmm… Haven’t a clue as to how that happened. I added it and now the error is:
Option ‘pid_Kp’ in section ‘heater_bed’ must be specified
I think because I put it under heater_bed which I assume isn’t correct because I noticed this in the SAVE CONFIG area at the end of the fie.
``
##
## [heater_bed]
## control = pid
## pid_kp = 70.323
## pid_ki = 1.267
## pid_kd = 975.730

I couldn’t find anything in the docs (yes believe it or not I do try looking there) referring to it, the sample for heater_bed looks the same and same for the older backups of the .cfg file.
I’m confused.

4

Please attach a new log and your printer.cfg

5

Actually I found it! I had installed a script for shell commands to try out and it had put [include shell_command.cfg] at the very bottom of the printer.cfg file. I never scrolled down far enough to notice it. Didn’t look right so I moved it up above the SAVE_CONFIG area and the error disappeared.

Thanks to both of you for your help and time.