Package Details: klipper-git r2786.c36fe76d-1

Git Clone URL: https://aur.archlinux.org/klipper-git.git (read-only, click to copy)
Package Base: klipper-git
Description: 3D printer firmware with motion planning on the host
Upstream URL: https://github.com/KevinOConnor/klipper
Licenses: GPLv3
Conflicts: klipper
Provides: klipper
Submitter: the_lf
Maintainer: loredan13
Last Packager: loredan13
Votes: 2
Popularity: 0.142682
First Submitted: 2018-10-19 05:10
Last Updated: 2020-02-03 19:32

Pinned Comments

loredan13 commented on 2020-01-07 19:30

README

After you have this package installed, copy an example config from /opt/klipper/config to /etc/klipper/klipper.cfg and adjust the values to suit your printer.

Copy the firmware out of /opt/klipper to your user directory and follow the procedure as outlined in the documentation: https://github.com/KevinOConnor/klipper/blob/master/docs/Installation.md#building-and-flashing-the-micro-controller

Then, start/enable the klipper service with systemctl.

Logs can be seen using journalctl

OctoPrint

Use the socket /run/klipper/sock. OctoKlipper is highly recommended.

WARNING

If you have ARM MCU on your printer you won't be able to compile firmware on ARM PC (which is the case for most computers running klipper). You will have to compile firmware on x86_64 PC

Latest Comments

1 2 Next › Last »

celogeek commented on 2020-01-24 18:13

hi, thanks for the patch

also I have dig more, and compile all have alert on build directory that appear in the binary package.

I have fix this way (also the way to bundle python package):

-    python2 -m compileall klippy
-    python2 klippy/chelper/__init__.py
+       python2 -m compileall -d /opt/klipper/klippy klippy
+       python2 -O -m compileall -d /opt/klipper/klippy klippy
+       python2 klippy/chelper/__init__.py

So I add an optimize compilation after the usual one, and include the final destination in the compile process.

loredan13 commented on 2020-01-21 08:12

Okay, thank you everyone, everything you said seems valid, I will include your changes in the package.

dack, about the logs, I removed that option with the intention of letting systemd-journal take care of it, but I wasn't aware of thread handling in klipper. I'll revert it to log file

dack commented on 2020-01-21 07:38

Apologies for repeating myself - I accidentally deleted my previous comment.

I think it would be better to go back to logging to a file (via the -l option), rather than letting systemd/journald do the logging. When logging to stdout (journald), klipper warns "No log file specified! Severe timing issues may result!". From looking at their code, logging to a file is handled completely differently. It uses a separate thread to log asynchronously to file. This would prevent log buffer issues from affecting time critical tasks. Logging to stdout is done in the main thread, which has the potential to cause issues.

celogeek commented on 2020-01-13 20:43

Hi,

The packaging also fail to include compile file and version file resulting in FIRMWARE_VERSION: ? in the log

I applied this change to fix this:

+        python2 scripts/make_version.py ARCHLINUX > klippy/.version
+       python2 -m compileall klippy
+       python2 klippy/chelper/__init__.py
        GLOBIGNORE=.git cp -r * "$pkgdir/opt/klipper"
-       chown -R klipper:klipper "$pkgdir/opt/klipper"

This way the package contains precompiled files and starts faster.

celogeek commented on 2020-01-11 10:09

Hi,

I want to install this package and got this errors:

==> Starting pkgver()...
==> Updated version: klipper-git r2748.2f8ad5e6-1
==> Sources are ready.
==> Making package: klipper-git r2748.2f8ad5e6-1 (Sat 11 Jan 2020 11:04:18 AM CET)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> WARNING: Using existing $srcdir/ tree
==> Starting pkgver()...
==> Removing existing $pkgdir/ directory...
==> Entering fakeroot environment...
==> Starting package()...
chown: invalid user: ‘klipper:klipper’
==> ERROR: A failure occurred in package().
    Aborting...
Error making: klipper-git

I guess the klipper exists at this stage

FIX:

instead of chown inside the install process, add this to your tempfile:

d /etc/klipper 0755 klipper klipper - -
z /etc/klipper/klipper.cfg 0644 klipper klipper - -
d /run/klipper 0755 klipper tty - -
Z /opt/klipper - klipper klipper - -

It will adjust automatically the right on config and opt directory

loredan13 commented on 2020-01-09 10:09

Sorry, I made a mistake of updating instructions without properly testing everything myself. I ended up reverting to /run/klipper/sock because /tmp/printer is not accessible by octoprint in current setup

plutonium commented on 2020-01-08 09:38

I just updated klipper and am unable to connect from octoprint.

[Errno 2] could not open port /run/klipper/sock: [Errno 2] No such file or directory: '/run/klipper/sock'' @ comm.py:_openSerial:2661 (hook default)

Your latest instructions tells to use /tmp/printer, but I don't have it on my system... and according to klipper.service listed in sources, the socket is still /run/klipper/sock (and it exists indeed on my RPi)...

[edit] I got it to work with /run/klipper/sock

loredan13 commented on 2020-01-07 19:30

README

After you have this package installed, copy an example config from /opt/klipper/config to /etc/klipper/klipper.cfg and adjust the values to suit your printer.

Copy the firmware out of /opt/klipper to your user directory and follow the procedure as outlined in the documentation: https://github.com/KevinOConnor/klipper/blob/master/docs/Installation.md#building-and-flashing-the-micro-controller

Then, start/enable the klipper service with systemctl.

Logs can be seen using journalctl

OctoPrint

Use the socket /run/klipper/sock. OctoKlipper is highly recommended.

WARNING

If you have ARM MCU on your printer you won't be able to compile firmware on ARM PC (which is the case for most computers running klipper). You will have to compile firmware on x86_64 PC

loredan13 commented on 2020-01-07 18:04

dack: the problem is with compiling ARM MCU firmware, it requires arm-none-eabi-gcc package, which is only for x86_64 architecture, and I still haven't found an alternative.

I have adopted the package, and I will try to update it as much as I can

dack commented on 2020-01-05 21:32

Deathwarror: Are you talking about requirements to compile the PKGBUILD, or to compile AVR microcontroller firmware?

If you are talking about the PKGBUILD, gcc and make are part of base-devel. That should not be listed as a dependency in the PKGBUILD as per the wiki page for Makepkg ("Before continuing, install the base-devel group. Packages belonging to this group are not required to be listed as build-time dependencies (makedepends) in PKGBUILD files.").

If you are talking about compiling the AVR microcontroller code, avr-gcc is already listed as a runtime dependency. Make is not listed, and should perhaps be added as a runtime dependency. Most people will probably not encounter that issue, since they would have already installed base-devel (and therefore make) in order to compile the PKGBUILD.