Nitehawk, Z-Offset issues

[kharrisma]

Issue resolved.  Apparently the problem was mainly multiple entries and split entries (?) across both config files,  and mainly it was entering a definition for the pt1000 in the thermistor section of nitehawk.cfg, then 'calling' the thermistor after defining it.  Klipper already understands what a pt1000 is, and it would seem that treating it as if it didn't pissed it off.    

 

modify nitehawk-sb.cfg:

[extruder]
step_pin: nhk:gpio23
dir_pin: nhk:gpio24
enable_pin: !nhk:gpio25
heater_pin: nhk:gpio9
sensor_pin: nhk:gpio29
pullup_resistor: 2200
sensor_type: PT1000

delete from nitehawk-sb.cfg:   (all other references to a pt1000)

thermistor pt1000]
temperature1: 0.0
resistance1: 1000.0
temperature2: 100.0
resistance2: 1385.1
temperature3: 200.0
resistance3: 1758.6

 

[temperature_sensor hot_end]
sensor_type: pt1000
sensor_pin: nhk:gpio29
pullup_resistor: 4700
min_temp: 0
max_temp: 275

delete from printer.cfg:  (extruder stepper driver data belongs with "[extruder]", not driver in printer.cfg and [extruder] in nitehawk-sb.cfg) 

 

[tmc2209 extruder]
uart_pin: PC11
tx_pin: PC10
uart_address: 3
#  Following line: original value 0.650; changed for Galileo 2 6/19/24
run_current: 0.6              
stealthchop_threshold: 999999

[heater_fan heatbreak_cooling_fan]
pin: PC7
# (FAN_1 on card.)
 

Have to give credit where due: this is from Sineos up on the Klipper Discourse site.  That guy has forgotten more about this stuff than I've managed to learn to date.

Thanks for taking some swings at this.  Going to take some time to understand why a z_offset entry caused a math domain error... or likely it's one of those things I'll move on and forget about!