bigtreetech / bigtreetech/CB1

CB1 + BTT Pi 3.0.0 internal mcu temperature error (it is in software somehow)

Open
#229 0 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 just spent 3 days trying to figure out why my printer have random MCU timeout errors.
Swaped USB cables, reinstalled, new memory card, different hardware but there was common problem. CB1 minimal image 3.0.0.
What i found is that after some time internal error happens on MCU and MCU temperature probe go nuts.
In my case, when i had it monitored by probe MCU shown different examples most common is (-60°C) and one time on CB1 in PI4B adapter board (+267°C)
I had in my printer CFG specified this

[temperature_sensor BTT-CB1]
sensor_type: temperature_host
min_temp: 10
max_temp: 100

which restarted the mcu since temperature went -60 or +267 and printer got in to safety mode.
once i commented out min and max
like this no more errors on MCU timer too close

[temperature_sensor BTT-CB1]
sensor_type: temperature_host
#min_temp: 10
#max_temp: 100

Including images from last print with the error :)
Happens on BTT PI 1.2 and CB1 in adapter board.
Didnt have time to test original 2.3.4 release sorry guys

Image

After restart

Image

My system info

Image

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing the issue on the CB1 minimal image 3.0.0 with a temperature_host sensor and configured min_temp/max_temp, then compare behavior with release 2.3.4. Done means the MCU temperature no longer reports implausible values that cause MCU timeouts or safety-mode restarts on the affected boards.

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
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.