Init. Moonraker: checkKlippyState

General Discussion
1

Basic Information:

Printer Model:
MCU / Printerboard:
klippy.log

Fill out above information and in all cases attach your klippy.log file (use zip to compress it, if too big). Pasting your printer.cfg is not needed
Be sure to check our “Knowledge Base” Category first. Most relevant items, e.g. error messages, are covered there

Describe your issue:

…
Hi all,
im getting this error and have attached logs
An error was detected during initialization the moonraker component ‘checkKlippyState’. Please check the log file and fix the issue.
moonraker(1).log (312.6 KB)
klippy(1).log (2.5 MB)
Could someone please point me in the right direction. Thanks.

2

Except that you are trying to load a not exiting bed_mesh here:

[delayed_gcode bed_mesh_init]
initial_duration = .01
gcode = BED_MESH_PROFILE LOAD=default

there are no additional errors in your log and also no mentioning of checkKlippyState.

Try fixing this and then reboot your host to have a clean start and if there are new errors come back with new logs.

3

I just wanted to note that the latest version of Moonraker does not clear out any checkKlippyState errors even after they’re resolved and you’ve rebooted - you have to click on the “xed” out alarm symbol manually.

I’m not sure if this is the optimal workflow as it can be hard to know if you’ve resolved the error.

4

Interesting. Never noticed this. Is there a reference? Is it just a notification or does it have a practical consequence?

5

Huh. I was able to do a quick demo of this.

I took a working printer.cfg and changed the pin name of an LED to somethingInvalid and then did a “Save & Restart” - the error was flagged.

Next, I changed the pin back to its valid value, did a “Save & Restart” and the flag appears with the checkKlippyState:

image
image742×281 26.1 KB

I just did a RESTART and the flag is still there and only goes away when I click on the icon in the lower right. When you do that, you’re queried as to whether or not you want the flag to reappear.

EDIT: here’s the system information:

image
image1016×462 46.5 KB

6

Ok, just checked myself:

  1. It is a Mainsail only thing
  2. It seems just a sticky notification that needs to be acknowledged
  3. It has no practical consequences
1 Like
7

Well, if you’re new or not sure if you’ve fixed the problem you’ll probably end up looking for something that isn’t there.

As I said, I don’t think it’s the optimal workflow - it can be lived with but it could be done better.

8

I agree, sometimes too much information is rather detrimental than helpful, especially if there are no real actions to take.
Maybe @meteyou has some thoughts on it.

1 Like
9

Yeah that might be because i have not been able to get a bed mesh in yet as i have been trying to fix other errors first. Like the BL Touch probe bouncing on the bed some on the second deploy please see video in my google drive too big to be an attachment 20231221_193510.mp4 - Google Drive

10

ohhh sry… i didn’t see this ping.

I fixed this bug already. This was a wrong notification, when Klipper wasn’t running during the init process.

1 Like
11

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.