"connect error 500" with Snapmaker Artisan Firmware V2.8.0

[git24chris]

First of all, a big thank you for building and maintaining this
tool. It is the only reliable way to send gcode to a Snapmaker
Artisan without Luban, and it has been working perfectly for a
long time. I really hope this project continues!

Thanks in advance

BR
Chris

---

Environment

• sm2uploader version: win64 (latest available at time of testing: V2.9)
• Printer: Snapmaker Artisan
• Firmware: V2.8.0 (2026-02-10)
• OS: Windows
• Upload method: direct SACP via -host IP

Description
After updating the Artisan firmware from V2.7.3 to V2.8.0, all upload
attempts via sm2uploader fail with connect error 500.

The printer is reachable on the network (UDP discovery succeeds,
IP is resolved correctly), but the SACP connection is rejected
with HTTP 500.

The same setup worked without issues on V2.7.3.

Firmware V2.8.0 introduced OctoPrint-compatible direct connection
support (IP + port 8080). It is possible that the SACP endpoint was
changed or requires a different handshake in this firmware version.

Log
2026/03/17 20:38:08 Uploading file 'test.gcode' [87.6 KB]...
2026/03/17 20:38:08 connect error 500

Steps to reproduce

1. Update Artisan firmware to V2.8.0
2. Run: sm2uploader -host <file.gcode>
3. Upload fails with connect error 500

Workaround
Downgrade to Artisan firmware V2.7.3 restores full functionality.

Note
Snapmaker V2.8.0 changelog mentions port 8080 for the new
OctoPrint/Orca direct connection. It is unclear whether this
also affects the SACP port or authentication flow that
sm2uploader relies on.

[macdylan]

#33

[git24chris]

Hi,

sry, read through #33 and it leaves me clueless how to get it working again.

I'm using your tool under windows as a commandline tool to send my saved gcode to my artisan.
no service running in the background , no oct-print nothing. I have a gcode file and your tool.

How can I fix now the communication ? I don't read an answer in #33 to that aspect.

sry too ask again.

  cmd = sm2uploader -host <ip> <gcode-file>

and it returns the connect error 500.
When I use the old Artisan FW it perfectly works, which is my workaround, but this is crazy.

BR
Chris

[macdylan]

sm2up will generate a configuration file in the same directory (hosts.yaml), which contains information about connected devices.

sacp: field specifies the communication method, while id as its alias. when using the -host parameter, you can refer to this alias.

try to use cmd = sm2uploader -host <id> <gcode-file>