-
Notifications
You must be signed in to change notification settings - Fork 246
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BFW-6788] [BUG] Core One has no CHAMBER_TEMPERATURE capability and does not report C temperature #4479
Comments
I am guessing the cause for this is that Marlin expects active heating for the chamber?
But then I am not sure why it doesn't print |
Oh I was wondering when someone would come up with this :) Yes, we didn't implement the chamber temperature through the standard Marlin structures, because Marlin code is hell, plus it only considers heated enclosures, and the API overall was not powerful enough for our needs. This resulted in our chamber code to be actually sane, but we are left with having to hack back some of the OG Marlin support for the Octo guys. |
I was mostly trying to get a log of the chamber temperature over time depending on different bed temps and to see how well the cooling works. :) But I guess the Octo guys might want these too, yes. |
Created internal ticket BFW-6788 |
I just pushed a PR to make C1 great again :) |
The PR has been modified and doesn't compile as of now, but that is intended as is. Reason is: The chamber api will be separated and then the PR will be updated and included. |
We will try to finish it up internally |
Printer model
Core One
Firmware version
6.3.0+10073
Upgrades and modifications
None
Printing from...
does not apply
Describe the bug
The Core One reports it has no CHAMBER_TEMPERATURE capability on
M115
:It also does not report the chamber temperature (
C
) onM105
orM155
?How to reproduce
Send the above GCodes
M115
,M105
andM155 ...
over the serial interface.Expected behavior
CHAMBER_TEMPERATURE
should show1
and the temperature reports should have aC
with the chamber temperatures.Files
No response
The text was updated successfully, but these errors were encountered: