Fill out above information andin all cases attach yourklippy.logfile (use zip to compress it, if too big). Pasting yourprinter.cfgis not needed Be sure to check our “Knowledge Base” Category first. Most relevant items, e.g. error messages, are covered there
Describe your issue:
Can anyone help me understand where I’m going wrong here? Trying to configure “nitehawk-sb.cfg” post Stealthburner/Nitehawk toolhead hardware install. On startup, I get the following error: Option ‘z_offset’ in section ‘probe’ must be specified. Okay, opened up nitehawk-sb.cfg and added “z_offset:” with no parameters. Restarted machine, and got the following error: Unable to parse option ‘z_offset’ in section 'probe. Not unexpected. So again I opened up the config file, and added the value of 0.00 to the z_offset, and restarted. Now, this: Internal error during connect: math domain error.
I understand only in the vaguest terms what the error is; I’m at a total loss to understand why this failure would be associated with a parameter in “z_offset.” I tried entering both positive and negative integers, and all entries yield the same error message of math domain error.
Have not the slightest clue what to do with this. Looking at the ‘unhandled exceptions’ at the end of the klippy.log shows a number of errors in the ‘klippy.py’ file, which is way above my pay grade, and the last entry just states ‘math domain error.’ Not much to go on, for this relative newbie. Any ideas or pointers would be greatly appreciated!
…
Thanks for the reply. Trying to get machine to start without errors. Replaced original print head with a Stealthburner, and used a nitehawk-sb toolhead (USB bus.) Downloaded LDO’s config file for the nitehawk, commented out things that weren’t relevant (like X & Y stops - - still using original OEM), and so far it’s been one error after another; been dealing with them one by one, then this “math domain error” pops up and I can’t get past it.
I did see those lines, but as I understand it, the errors appear to be in the klippy.py file, which I haven’t touched in any way. Likely I’m not understanding what it’s telling me, but that’s what I see when I read them. It would seem I’ve either omitted something it wants, or entered invalid values for something… or both. Anything I do from here would be shooting in the dark, without further input from more knowledgeable heads
Think I figured out Klipper’s issue with the PT1000 (as it is in my config file.) As soon as I changed both references to it from “PT1000” to “pt1000,” it stopped complaining about it and went on to the next error, which is still the “math domain error” in response to ANY value entered into “z_offset.” No “z_offset” results in a demand to have one in the “Probe” section; a bare “z_offset:” with no value entered returns a “can’t parse value” error, any entry of any kind in ‘z_offset’ results in the math domain error. Still have NO idea what to do with this.
Made the suggested changes; saved & restarted. Now the first error that shows is "Unknown temperature sensor ‘PT1000’ Changed to ‘pt1000’ in the event it matters (seemed to when I made that change in my initial config file)… error persists.
Have read in several places that if using a pt1000, ideally, it needs a 1K 1% pullup resistor. If I can make Klipper happy, I was planning to replace the 2.2K (R19) with a 1k 1% 0204 SMD resistor. Does that seem accurate to you, or more like nonsense? In either case, that’s obviously down the road apiece AFTER it’s running.
sensor_type: PT1000
sensor_pin:
# Analog input pin connected to the sensor. This parameter must be
# provided.
#pullup_resistor: 4700
# The resistance (in ohms) of the pullup attached to the sensor. The
# default is 4700 ohms.
Have you tried with PT1000 at all points where you use it?
So far, it doesn’t seem to matter whether I put it in the “extruder” section of printer.cfg, or delete the “extruder” section from printer.cfg and just use the one in the nitehawk-sb.cfg file. It doesn’t like “PT1000” in either location. If I “define” the PT1000 in the nitehawk-sb.cfg, (temp1/resistance1, 2, and 3) and leave it as “PT1000,” it still doesn’t like it. If I then change from upper case to lower case (pt1000) it stopped haranguing me and moved on to the math domain error, which so far nothing has affected, other than as I described above. As I understand it, it could be in both locations, and as the last file read, the nitehawk-sb.cfg entry will override the one in printer.cfg, so technically it shouldn’t matter… though likely it does and I just don’t know how.
In the [extruder] section in the included nitehawk config set the sensor type to PT1000
For any new issue, please follow the above instructions and provide only one klipyy.log file and one set of configuration files. I prefer not to guess which files to examine.
My apologies for the multiple files - - I didn’t realize one of them contained both config files. I’ll make it a habit to look at them before uploading them.
BINGO! Got it in one!! Well, two… but that was entirely my fault. I appreciate your help, and patience with a newbie.
Oh… followed (correctly and completely, the second time…) Sineos’ instructions listed above: Modify nitehawk-sb.cfg,… delete from nitehawk-sb.cfg… and last, delete from printer.cfg. All the error ‘redscreens’ went away and it was ‘bluescreen’ for a few minutes, then errored (amber) with can’t connect. With all the cut/copy/paste and deleting, I took a piece of the [mcu] section out and didn’t notice. Wasn’t hard to spot, just ‘had a moment’ when reconfiguring thermistor and stepper driver entries caused a ‘can’t communicate’ error. Quickly noticed the truncated [mcu] section and checked a backup file… yep, “baud:” and "restart_method: " were missing. No wonder… Fires right up now, homes all axes, good to go! Thanks again, Sineos!
