Unknown command:SET_LED-pauses print no apparent issue

[Gixxerfool]

Basic Information:

Printer Model: Mercury One.1
MCU / Printerboard: Manta M8P/EBB36
Host / SBC: CB1
klippy.log (5.6 MB)

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:

…

This has been an ongoing issue for me over the past couple of months. Prior to this I would get a UNKNOWN COMMAND: SET_LED message and it would unload the filament and pause the print. Today the only message I had was the above message and nothing else and it paused the print again. No filament unload.

At the suggestion of the Robert Lorencz on the FB Orbiter group I adjusted the filament sensor switch in the filament run out sensor by a .5mm and this is the first time I have had the issue again.

I attached the log and a pic of the console output. Ignore the shutdown I accidentally hit the panic button on the klipperscreen.

[Sineos]

I’m not sure, what you are trying to achieve.
The SET_LED command is only available if you have defined some LEDs to be controlled. See LEDs and [led]

It looks like your configuration is not complete or does not match the Orbiter version you are using.

[Gixxerfool]

Just trying to get a print to complete. I only copy and pasted the config for the orbiter and sensor from the project site. I do not run nor have I set up any LEDs so there is a possibility the commands are there, but I have no use for them. As in my screenshot this is what is displayed and the print is paused. I do not know what is causing this to happen as it is not user requested.

I have had many successful prints with this setup this is a newer issue.

[Sineos]

Well, just “copy and pasting” large chunks of macros might create unexpected behavior.

Since you apparently never had some LEDs configured, this command never worked, so also this is quite unlikely a “newer issue”. (BTW, the log contains another unknown command, coming from a macro)

In addition, the log does not contain any evidence of a pause event.

[Gixxerfool]

I only copy and pasted since that was the setup instructions for the Orbiter runout from the Orbiter team.

It may have been there the whole time, but the issue of the printer stopping mid print and pausing just recently cropped up.

While the log may not show it, the printer stopped and parked the toolhead where in the pause position.

I can only report what happens.