bigtreetech / bigtreetech/CB1

Klipper Shutdown trough apparent thermal throttle

Open
#213 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
No language data
Stars
496
Forks
86
PR merge metrics
No merged PRs in 30d

Description

Hello,

I've noticed that the CB1 board begins thermal throttling at around 60°C. While this temperature threshold might seem reasonable, it causes Klipper to lose connection due to timing issues ("timer too close" errors). This is particularly frustrating since the CB1 runs relatively hot even under active cooling in a controlled environment.

I'm looking for help regarding this issue, and I have a few specific questions:

1. Is it possible to increase the thermal throttling threshold on the CB1?
If so, how can it be done, and what are the potential risks regarding stability and long-term reliability?

2. Alternatively, is it possible to mitigate this problem through Mainsail or Klipper configuration changes—perhaps by adjusting timing tolerances or connection handling?

Any advice, insights, or shared experiences would be greatly appreciated!

Contributor guide

No contributing guide indexed for this repository

Research direction

No files, tests, or entry points are named; begin by identifying where CB1 thermal throttling and Klipper connection behavior are configured. Done means documenting whether the threshold or configuration can be changed, the required steps, and the stability risks.

Written by the indexing model from the issue text.

Assessment

Domain
embedded-iot, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.