Moonraker can't connect to Klipper

[HemlockMimosa]

Hi folks! Wondering if you can help me.

I installed Klipper on my Pi using KIAUH, then followed instructions for flashing Klipper onto the SV06, all of which seem to have worked.

sudo service klipper status returns the following:

klipper.service - Klipper 3D Printer Firmware SV1
Loaded: loaded (/etc/systemd/system/klipper.service; enabled; vendor prese>
Active: active (running) since Wed 2023-03-22 01:15:53 GMT; 9min ago
Docs: https://www.klipper3d.org/
Main PID: 965 (python)
Tasks: 2 (limit: 3933)
CPU: 1.690s
CGroup: /system.slice/klipper.service
└─965 /home/andre/klippy-env/bin/python /home/andre/klipper/klippy>

Mar 22 01:15:53 raspberrypi systemd[1]: Started Klipper 3D Printer Firmware SV1.
lines 1-11/11 (END)
● klipper.service - Klipper 3D Printer Firmware SV1
Loaded: loaded (/etc/systemd/system/klipper.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2023-03-22 01:15:53 GMT; 9min ago
Docs: https://www.klipper3d.org/
Main PID: 965 (python)
Tasks: 2 (limit: 3933)
CPU: 1.690s
CGroup: /system.slice/klipper.service
└─965 /home/andre/klippy-env/bin/python /home/andre/klipper/klippy/klippy.py >

I think this means that Klipper is successfully running on my printer, which means that the problem is occurring when I try to modify my configuration file.

ls -l /dev/serial/by-id/ returns the following: lrwxrwxrwx 1 root root 13 Mar 22 00:55 usb-1a86_USB_Serial-if00-port0 -> ../../ttyUSB0

I've attempted to modify my configuration file in Mainsail by adding either the entire string, "usb-1a86_USB_Serial-if00-port0 -> ../../ttyUSB0" or just "usb-1a86_USB_Serial-if00-port0"

None of these have worked. In addition, I've tried to perform the "make flash FLASH_DEVICE=/dev/serial/by-id/usb-1a86_USB_Serial-if00-port0" only to learn that there is "No rule to make target 'flash'"

Do any of you have any troubleshooting advice, or is there any step I'm missing? Thanks for your advice and comments.

[bassamanator]

Do no use make flash, it's not something that works with all boards.

I don't think the board is flashed. Please post out put from ls -l /dev/serial/by-id/ and paste it with backticks, or use the code option above.

EDIT: hard to see on the device I'm using, but yeah, klipper is not flashed. Please see Flash Firmware section in readme.md, there is a link to a video as well. FAT filesystem, less than 16GB, no other files on the card.

[HemlockMimosa]

Hello and thanks for getting back to me! Here is the output you requested:

total 0 lrwxrwxrwx 1 root root 13 Mar 22 01:08 usb-1a86_USB_Serial-if00-port0 -> ../../ttyUSB0
...this compels me to ask what might be a very basic question. I've only installed Klipper once before, about a year ago, so you may have to forgive my lack of understanding.

Basically, I flashed Klipper onto my printer by taking the klipper.bin file from the zip file containing your configuration, placing it on a blank SD card, and then powering up my printer with the SD card installed.

Should I have instead generated a .bin file by following the configuration steps listed here?

[bassamanator]

Okay let's take a few steps back. I have updated the Flash Firmware section, and have also compiled a new klipper.bin using the latest version of Klipper.

I want you to flash marlin back onto the board (included now in this repo). Then I want you to flash the latest klipper.bin (included now in this repo). Then let's see what happens.

Please read the Flash Firmware section again.

What device are you using to host klipper? RPi?

[HemlockMimosa]

Okay! I may be getting somewhere.

First, I did as you asked and flashed marlin, using the SD card that came with the printer, adding a single letter to the end of the .bin

This worked! I was able to restore the Sovol firmware.

Next, I tried the same approach using the klipper file from your repo. This actually didn't seem to work the first time -- the printer booted to Marlin as normal. I tried again and this time it seemed to flash. The printer booted to a blank screen instead of the Sovol logo.

Then I ran ls -l /dev/serial/by-id/ with the same result as before. Output was total 0 lrwxrwxrwx 1 root root 13 Mar 22 01:08 usb-1a86_USB_Serial-if00-port0 -> ../../ttyUSB0. Adding this to the printer.cfg in Mainsail produced no result, as before.

This made me suspect that something was going on other than a faulty SD card or flashing method. So, I tried using a different USB cable in a different port. This time, running ls -l /dev/serial/by-id/ produced an error message: ls: cannot access '/dev/serial/by-id/': No such file or directory

So, we're still not fixed, but at least I was able to produce a different result? What do you make of this?

[bassamanator]

Paste your mcu section here, surround it with 3 backticks on their own separate lines.

Check klippy.log for "Permission denied" error. If that is the case, paste this into terminal: sudo usermod -a -G tty pi. Source. This is likely not the case but worth checking.

[HemlockMimosa]

Sure! here is the mcu section from the printer.cfg in mainsail:

# NOTE Obtain definition by "ls -l /dev/serial/by-id/"
'serial: usb-1a86_USB_Serial-if00-port0 'restart_method: command

klippy.log does not appear to contain any error messages.

[bassamanator]

Change your mcu section as follows:

[mcu]
# NOTE Obtain definition by "ls -l /dev/serial/by-id/"
serial: /dev/serial/by-id/usb-1a86_USB_Serial-if00-port0
restart_method: command

[HemlockMimosa]

That doesn't appear to have done anything, unfortunately.

[bassamanator]

Restart firmware.

[HemlockMimosa]

I rebooted klipper, moonraker, and the host in sequence, still not working.

…

On Wed, Mar 22, 2023 at 9:09 PM Bassam Husain ***@***.***> wrote: Restart firmware. — Reply to this email directly, view it on GitHub <#16 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AZ7POXIMOAD5X6PIZFFF7ZLW5OPE5ANCNFSM6AAAAAAWDGG3GQ> . You are receiving this because you authored the thread.Message ID: <bassamanator/Sovol-SV06-firmware/repo-discussions/16/comments/5399421@ github.com>

[HemlockMimosa]

Does it make a difference how I plug in the RPI? For example, do I plug in the RPI first, then turn the printer on? Or do I turn the printer on and then plug in the RPI? On Wed, Mar 22, 2023 at 9:13 PM Andrew Sanders < ***@***.***> wrote:

…

I rebooted klipper, moonraker, and the host in sequence, still not working. On Wed, Mar 22, 2023 at 9:09 PM Bassam Husain ***@***.***> wrote: > Restart firmware. > > — > Reply to this email directly, view it on GitHub > <#16 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AZ7POXIMOAD5X6PIZFFF7ZLW5OPE5ANCNFSM6AAAAAAWDGG3GQ> > . > You are receiving this because you authored the thread.Message ID: > <bassamanator/Sovol-SV06-firmware/repo-discussions/16/comments/5399421@ > github.com> >

[bassamanator]

Paste all logs here in code blocks. Paste a picture of the error screen. On Wed, Mar 22, 2023, 9:15 p.m. HemlockMimosa ***@***.***> wrote:

…

Does it make a difference how I plug in the RPI? For example, do I plug in the RPI first, then turn the printer on? Or do I turn the printer on and then plug in the RPI? On Wed, Mar 22, 2023 at 9:13 PM Andrew Sanders < ***@***.***> wrote: > I rebooted klipper, moonraker, and the host in sequence, still not working. > > On Wed, Mar 22, 2023 at 9:09 PM Bassam Husain ***@***.***> > wrote: > >> Restart firmware. >> >> — >> Reply to this email directly, view it on GitHub >> < #16 (comment) >, >> or unsubscribe >> < https://github.com/notifications/unsubscribe-auth/AZ7POXIMOAD5X6PIZFFF7ZLW5OPE5ANCNFSM6AAAAAAWDGG3GQ > >> . >> You are receiving this because you authored the thread.Message ID: >> <bassamanator/Sovol-SV06-firmware/repo-discussions/16/comments/5399421@ >> github.com> >> > — Reply to this email directly, view it on GitHub <#16 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AOY5H434VHN3H32SZYOQADTW5OP3FANCNFSM6AAAAAAWDGG3GQ> . You are receiving this because you commented.Message ID: <bassamanator/Sovol-SV06-firmware/repo-discussions/16/comments/5399445@ github.com>

[HemlockMimosa]

moonraker conf.txt

Here you go! I'm sorry this has been such a pain in the ass.

[bassamanator]

No worries. In moonraker.conf, change the following line:

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

to

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

Also edit cfgs/misc-macros.cfg and change

[virtual_sdcard]
path: /home/pi/printer_data/gcodes

to

[virtual_sdcard]
path: /home/andre/printer_data/gcodes

[HemlockMimosa]

It feels like we're really close now, because I got to a new error message.

mcu 'mcu': Unable to connect
Once the underlying issue is corrected, use the "FIRMWARE_RESTART" command to reset the firmware, reload the config, and restart the host software.
Error configuring printer

I'm attaching the latest logs:

moonraker (3).log
klippy (6).log

[bassamanator]

Firmware_restart?

[Trilis29]

Hi, I think I have same proble. Everything configured as on tutorial still can't connect.

[SporePrint]

I know this is an old post, but I'm running into some issues similar to comment #6;
I've printed loads with my SV06 using bassamanator's configs as a starting point(you're an mvp homie, thank you for your work); then my printer sat for about a year. I reinstalled linux on my host due to auth issues, and am back to the point of calibrating/fine-tuning my printer.

For some reason, I'm having a lot of trouble getting my host to connect to my printer upon initial boot up. I have to sit and fiddle, going back and forth between my printer and my remote klipper interface. I "restart" klipper via the interface, and have to toggle the printer on and off a few times before klipper errors out in order to connect, sometimes needing to restart klipper multiple times. If I power up my printer and then restart klipper, it seems that my printer times out/freezes before klipper attempts to connect. Once it connects, I'm good to go for the duration of both machines staying online, but that initial connection seems so finnicky for some reason, and I don't remember it to be so.

I'm posting here mostly because I thought it may be relevant to anyone experiencing issues similar to above - just because your setup doesn't smoothly boot up first try doesn't necessarily mean you didn't flash properly or have your config setup properly, it really seems to just be finnicky to boot up!

If you have suggestions on why this may be or how to resolve it, I'd love to hear them!

[bassamanator]

Out of curiosity, how long is the USB cable that connects the printer to the host?

[SporePrint]

I believe it's 180-300cm; it's a cord from an old xbox controller. When I was using the rpi it was the only one in my house that gave a reliable connection(neither side loose in the connector, power+data, robust/low-gauge), so I've trusted it for a long while.

[bassamanator]

Considering that the mcu was not found via ls upon 'waking', and that everything else is looking as it should, I believe the length of the cable is a factor.

[SporePrint]

So, are you thinking it's searching for a fingerprint of a sleeping serial connection, and until that mcu is awake the "search signal" is too weak to detect it because of voltage drop across the cable, but once the mcu cycles it can see it because a signal is coming from both ends? Interesting, though this is the same cable I used last year with what I remember to be less connection drama.

I'll have to wait till after the holidays to try new cables, as I mentioned any others in the house are insufficient and I don't have the means to purchase new at the moment

[bassamanator]

Yes, something along those lines.

I too would hate to buy yet another USB cable. Perhaps see if a friend/neighbour/colleague is able to let you borrow a more standard length cable for ~24 hours. This way you can cross this potential issue off the to check list without waste.