Artillery3D M1 Pro - Klipper GPLv3 infringement

As this may be of interest, it appears that Artillery3D/YunTu has released the M1 printer, utilizing Klipper.

However, they have yet to release their code, despite my repeated and polite requests - calling it at some point “proprietary”.

Their modifications to Klipper include the removal or comment-out of versioning (?!). They have used (or nearly used) the commit https://github.com/Klipper3d/klipper/commit/ba2a149e9ab093a36120226c2e76ba8f3f4e7ed9 as their base.

Most changes implement some “quick wins” in the original code to support their specific hardware/oddities.

On Klippy, some “updated” parts are delivered as Python code, some as only pyc (which could be reversed) and sadly, others where delivered as Cython .so files and cannot be reversed.

Furthermore, there is no other Klipper source code available - making it extremely complex to investigate issues.

I have uploaded what I could find or salvage: GitHub - pijalu/artillery-m1-klipper-code at artillery-m1, for the curious and as evidence..

It’s worth noting that they have also made changes to moonraker, but all the code could be retrieved from the printer: Artillery M1 Pro 1.0.11.00 Moonraker updates · Arksine/moonraker@8416bfa · GitHub

I’m not sure how this community handles this situation, but it would be ideal if some copyright holders and Klipper users could politely request that Artillery3D comply with the license and provide the source to their “firmware”.

You can contact them at support@artillery3d.com, artillery3d@hotmail.com, or info@artillery3d.com.

Thank you !

1 Like

Interesting. Great work figuring out the git diff between mainline and the M1 software. It’s still sad to see companies modifying Klipper instead of submitting PR’s to mainline.

1 Like