Connection issues with Klipper?

[Peurif]

Basic Information:

Printer Model: Vcore 31
MCU / Printerboard: Octopus Pro + EBB42
Host / SBC rPI
klippy.log Can’t download it

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:

Yesterday afternoon I updated and made a print…

Since the print did NOT come out well, I was going to reprint this morning, but…

I get an error message, this one:

The last thing I remember is that I updated Fluidd, but then I restarted and managed to print, although it did not end well…

I tried to download the klipper.log, but I could not, I get this error window…

YES I was able to download the Moonraaker.log, which I attached, in case it helps
moonraker.log (275.1 KB)

Afterwards I tried to connect via console and check that it detected the MCUs, and it seems that it did…

Any ideas?

I tried with KIAUH, to undo the Fluidd update, but the same, I still get the error

Some ideas?
…

Add aditional info…

In Fluidd interface, in configuration section there is more logs… and one of them… its called “fluidd-error.log”, attach them…

fluidd-error.log (5.3 KB)

[Peurif]

Some news…

with Kiauh, i have installed Mainsail, and the error message its more descriptive…

It seems that it cannot connect to the printer board… but the rPi does detect it via USB…

[Peurif]

With Kiauh, I got the klipper.log

klipper.zip (3.4 MB)

I had to compress it in ZIP because it was very large

[Peurif]

More info…

i have checked Monraker.conf

...
[server]
host: 0.0.0.0
port: 7125
klippy_uds_address: /home/pi/printer_data/comms/klippy.sock
...

[Peurif]

Hi,

if change this:

klippy_uds_address: /home/pi/printer_data/comms/klippy.sock

for

klippy_uds_address: [klipper in Octopus IP x.x.x.x]

Would it work?

How do I find out Klipper’s IP?

[Peurif]

In Mainsail update manager, Klipper appears how corrupt…

I have tried to correct it, and I get a PIN NAME error

[Sineos]

Please do not mess with these settings.
IF they worked before AND you did not touch them, then there is no indication that you should be modifying any of them.

No update will change these settings unless you are doing something really strange.

Your klippy.log indicates that the last Klipper start was successful.
Revert the changes and try to simply restart your entire system, including the RPi

[Peurif]

I followed your recommendation… but I still get an error, it seems to be a configuration error, and I don’t know how to fix it.

The error is this:

Unknown pin chip name ‘probe’

Once the underlying issue is corrected, use the “RESTART”
command to reload the config and restart the host software.
Printer is halted

I usually use a text search engine to search for the text string that is causing the error until I find and fix it. But this time I did that, and I can’t find the “probe” text string (isolated) in the configuration.

Where can I search?
What does this error mean? (Unknown pin chip name ‘probe’)

[EddyMI3D]

Looking at your klippy.log in post #3, you are referring to probe multiple times in the config, but non of these probes are defined:

[Peurif]

SOLVED…

Something made me suspect that the problems were being caused by the zProbe (Beacon3d).

Beacon support helped me solve it…

The solution was to reinstall Beacon3d…

Thx for help and comments