Thermistor Sensor type issue

[kharrisma]

Hi Forum Folke,

Hammering away at config file errors, post-Nitehawk SB installation and post-update to Klipper and Mainsail. Managed to shoot each one down, untii this one:

For the sake of simplicity and ease of reading the config files, I added an {include nitehawk-sb.cfg} to the beginning of my printer.cfg file... which leaves me with a dilemma: *where* does the information for the heat-block thermistor go? In the printer.cfg, or in the nitehawk-sb.cfg? It's a V6 hot end, which typically uses an ATC Semitec 104NT-4-R025H42G. Klipper accepts this thermistor type, but gives me that error message. Meter across the thermistor at room temp (65F/18C) giving a 4.4MEG ohm reading?? That doesn't seem right; according to the chart, it should be about 139 ohms. Thought it might be a bad thermistor or wiring, so I plugged in a new Winsinn HT-NTC100K from my parts box (meter showed 135 ohms, which is about what the RT chart calls for) and edited the config files accordingly, did a firmware restart... but I *still* get the same message, just with a different temperature:

At a loss for direction at this point. Not sure if the issue is having thermistor data in two config files, or if only one should have them, which one. Need to sleep on this and try again tomorrow, maybe with some ideas from you folks.

 

[shiftingtech]

So, a couple of things.

1. Any setting can go in any file. What you don't want to do, is you don't want to set the same thing in multiple files. Because then one will Overwrite the other, and it will get confusing. So what you want, is to have the any given settings in the file *that makes sense to you*, and erase the redundant settings in the other file.

2. I think you're misreading the charts. A 104nt reads 100,000 (or 100K) ohm at 20c. The winsinn is similar at room temp.

3. 4.4 megaohm sounds like a wire is broken

 

[kharrisma]

Thanks, Shiftingtech; my bad, I *was* misreading the charts; it clearly says K-ohms on the headers.

I'll have to double-check the terminal crimps; might have got more insulation than wire in the crimp. It *was* working fine in the older hot-end it came out of; only change was trimming the leads to fit the Stealthburner and crimping on new terminals.

I'll try reducing to one set of parameters. Thanks for clearing that up; I understand how things work (more or less) with the SBC running the show, but what I didn't understand was what introducing *another* MPU into the mix was doing; obviously the Notehawk is much more than a passive connection board. Didn't know if I should "pull" all functions that the Nitehawk is handling from the printer.cfg and put them in the nitehawk-sb.cfg (which is what makes sense to me), or leave them all in printer.cfg. Tried commenting a few out in printer.cfg, but Klipper said an entry was mandatory, which just fueled the confusion.

I'll give it another shot using what you gave me and see what shakes out! ;-)

 

[shiftingtech]

I'd be curious what you commented out that led to the mandatory message. If its a setting that has a dupe in the nitehawk file, and the nitehawk file is properly included, that really shouldn't happen

 

[kharrisma]

Wish I'd been collecting screenshots through all this so I could be more specific/accurate; my recall-in-hindsight isn't always the best, especially if I've been trying multiple things to resolve the problem. I think it was when I commented out the sensor_pin: for the thermistor in the extruder section in printer.cfg, thinking the entry in nitehawk-sb.cfg would cover it, and was told that sensor_pin was a mandatory entry in section extruder (doesn't help things that Klipper doesn't specify which *.cfg file the error is in, when you have more than just the one printer.cfg.) I tried adding something to the same section, and was told it was an invalid entry for the section as well. I'm more mechanic than coder, and find this area confusing and sometimes frustrating. I'm guessing that I got the mandatory entry message because Klipper reads the {include} files before it gets to printer.cfg, Likely wrong, but it's all I've got at the moment! ;-)

I pulled that V6 thermistor, checked the terminal crimp and found it okay. Peeled back the heatshrink on the splice and read directly from the solder joints, and the thing *still* reads 4.4 M-ohm at 18-ish C. The metal sleeve that goes in the heat block *looks* okay (no retaining screw dents), but maybe I overtightened it and damaged the internals. I ordered a PT1000 and I'll try that when it arrives. And get a meter reading *before* it goes in so I've got a 'baseline' reference! ;-)

 

[shiftingtech]

If that description is accurate, I'm almost sure you don't actually have the nitehawk file [include]ed

 

[kharrisma]

Unless I flubbed this somehow, the first lines in my printer.cfg are
[include mainsail.cfg]
[include nitehawk-sb.cfg]
[include tacho_macros.cfg]
[include stealthburner_led_effects_barf.cfg]

At the moment, I ave the last two commented out so I can focus on the first two and get them to play nice together. ;-) Are those [include] files supposed to be in a specific directory other than where printer.cfg lives, so they aren't being seen? I just drag & drop the *.cfg files into the files section of the Klipper front end; no idea where it puts them, or whether I'm supposed to specify a location (or how to do that if so.) What I don't know would fill university libraries! :-/

 

[shiftingtech]

Should be fine. Also, the files must have dropped in the right place, because otherwise klipper would yell about THAT.

 

[kharrisma]

Yah, that's true... Klipper seems just as quick to yell about omissions as it is about errors! Which in my case is a good thing!