#temperature sensor chamber
36 messages · Page 1 of 1 (latest)
what error are you getting exactly and what did you comment out? is this your nitehawk chamber thermistor or an additional one?
its the nitehawk chaber sensor.
nitehawk works otherwise? or you're getting MCU failure?
seems to work otherwise
it looks like its reporting temp in your klippy.log. so gotta give me more info
from last row of your log
not sure. while it was heating up to print it suddenly shut down and gave this error, I think it said unknown temperature_sensor chamber error. I reset, and it did it several times. I hashtagged out the section uner TH., but it did it again. I found it in the start print macro and I hashed it out there and its printing. but like I said, it was fine last night.
Its been acting weird though. I have the beacon and it also started smashing the print. so I tried reseting things and it still did it. I recalibrated the beacon and it printed fine. next day it did the same thing. had to recalibrate and it was fine. but it does that before each print.
The temperature sensor chamber has been there. its nothing new
can I fix something?
oh wait
no its not
but your print_start macro is looking for that sensor with the name chamber
thats why it does it before each print
update your print_start macro to reference temperature_sensor chamber_temp
to match the sensor you have defined
that should solve your unknown sensor issue
the beacon i will guess is unrelated
I will do that. but its strange. I checked my saved config and its the same it has been. it never said chamber_temp.
idk what to tell you. just going off what you shared
is that chamber sensor plugged into your nitehawk? i'm guessing a nitehawk SB?
correct. nitehawk sb
then that thermistor should be defined in your nitehawk.cfg i think
im not running a nitehawk-sb right now to verify
yep
https://github.com/MotorDynamicsLab/Nitehawk-SB/blob/master/Firmware/Klipper Configs/nitehawk-sb.cfg
chamber_temp is the default name for it
I see that it is [temperature_sensor chamber_temp]and it is shown that way , it just wasn't in the macro. but the macro has always said it without the temp. just odd that it suddenly decided it doesn't like it. I will test it shortly. after the test print finishes.