Creality K1C Setup
Get HelixScreen running on your Creality K1C (also works for K1 and K1 Max).
Time required: ~20 minutes
What You Need
Section titled “What You Need”- Creality K1C with firmware v1.3.3.5 or later (check: Settings on the touchscreen)
- K1C connected to your WiFi network
- A computer on the same network with an SSH client
Step 1: Enable Root Access
Section titled “Step 1: Enable Root Access”On the K1C touchscreen:
- Go to Settings > Root account information
- Read the disclaimer, wait 30 seconds, then confirm
That’s it. Root is now enabled.
Step 2: SSH Into the Printer
Section titled “Step 2: SSH Into the Printer”From your computer:
ssh root@<PRINTER_IP># Password: creality_2023Find the IP address on the K1C touchscreen under Settings > Network, or check your router’s DHCP client list.
Step 3: Install Simple AF (Recommended) or Guilouz Helper Script
Section titled “Step 3: Install Simple AF (Recommended) or Guilouz Helper Script”HelixScreen needs Moonraker (the Klipper API server) to be running on your K1C. Stock firmware doesn’t include it, so you need community firmware.
Option A: Simple AF (Recommended)
Section titled “Option A: Simple AF (Recommended)”Simple AF is the easiest path and has first-class HelixScreen support.
cd /usr/datagit clone https://github.com/pellcorp/creality.git pellcorpcd pellcorpsh installer.shFollow the prompts. This installs Klipper, Moonraker, and GuppyScreen. Once it’s working (GuppyScreen appears on the touchscreen), proceed to Step 4.
Option B: Guilouz Helper Script
Section titled “Option B: Guilouz Helper Script”If you prefer the Guilouz Helper Script:
git clone --depth 1 https://github.com/Guilouz/Creality-Helper-Script.git /usr/data/helper-scriptsh /usr/data/helper-script/helper.shFrom the menu, install Moonraker at minimum. Optionally install Fluidd or Mainsail for web access.
Note: If git clone fails with an SSL error, run
git config --global http.sslVerify falsefirst.
Step 4: Install HelixScreen
Section titled “Step 4: Install HelixScreen”Option A: Direct Install (Recommended)
Section titled “Option A: Direct Install (Recommended)”If your K1C has internet access, install directly on the printer via SSH:
wget -O - http://dl.helixscreen.org/install.sh | shThis works because dl.helixscreen.org serves over plain HTTP, which BusyBox wget supports. No need to download anything on your computer first.
Option B: Two-Step Install
Section titled “Option B: Two-Step Install”If your printer doesn’t have internet access, download on your computer first, then copy to the printer.
On your computer:
Go to the latest release page and download:
helixscreen-k1.zip(the K1 release archive)install.sh(the installer script, under “Assets”)
Or use the command line (replace vX.Y.Z with the actual version):
VERSION=vX.Y.Z # Check latest at https://github.com/prestonbrown/helixscreen/releases/latestwget "https://github.com/prestonbrown/helixscreen/releases/download/${VERSION}/helixscreen-k1.zip"wget https://raw.githubusercontent.com/prestonbrown/helixscreen/main/scripts/install.shCopy to the printer and install:
scp helixscreen-k1.zip install.sh root@<PRINTER_IP>:/usr/data/ssh root@<PRINTER_IP> # password: creality_2023sh /usr/data/install.sh --local /usr/data/helixscreen-k1.zipThe installer automatically:
- Detects your K1C platform
- Stops GuppyScreen (or whatever screen UI is running)
- Installs to
/usr/data/helixscreen/ - Creates the boot service (
/etc/init.d/S99helixscreen) - Configures Moonraker update manager for easy future updates
Step 5: Complete Setup on the Touchscreen
Section titled “Step 5: Complete Setup on the Touchscreen”HelixScreen starts automatically after install. The on-screen wizard walks you through:
- Language selection
- Moonraker connection — should auto-detect on
localhost:7125 - Printer identification — the K1C is in the printer database
- Hardware discovery — heaters, fans, sensors, LEDs
Managing HelixScreen
Section titled “Managing HelixScreen”# Start/stop/restart/etc/init.d/S99helixscreen start/etc/init.d/S99helixscreen stop/etc/init.d/S99helixscreen restart
# View logscat /tmp/helixscreen.logtail -f /tmp/helixscreen.log # live followUpdating
Section titled “Updating”From Fluidd/Mainsail (easiest)
Section titled “From Fluidd/Mainsail (easiest)”If you have Fluidd or Mainsail installed, HelixScreen appears in the update manager. One-click update.
From SSH
Section titled “From SSH”# On your computer (replace vX.Y.Z with actual version):VERSION=vX.Y.Zwget "https://github.com/prestonbrown/helixscreen/releases/download/${VERSION}/helixscreen-k1.zip"scp helixscreen-k1.zip root@<PRINTER_IP>:/usr/data/
# On the printer (use the bundled install.sh - no need to download it again):/usr/data/helixscreen/install.sh --local /usr/data/helixscreen-k1.zip --updateUninstalling
Section titled “Uninstalling”/usr/data/helixscreen/install.sh --uninstallThis restores GuppyScreen automatically.
Troubleshooting
Section titled “Troubleshooting”| Problem | Fix |
|---|---|
| Can’t SSH in | Make sure root is enabled (Step 1). Password is creality_2023 |
curl or SSL error | K1 doesn’t support HTTPS downloads. Use the two-step install (Step 4) — download on your computer, then scp to the printer |
| Installer says “Moonraker not found” | Complete Step 3 first — Moonraker must be running |
| Blank screen after install | Check logs: cat /tmp/helixscreen.log |
| Touch not responding | Reboot: reboot |
For more help: Troubleshooting Guide | Discord | GitHub Issues
Firmware Upgrade Path
Section titled “Firmware Upgrade Path”If your K1C is on older firmware, you must upgrade in order:
| Starting Version | Upgrade To |
|---|---|
| v1.2.9.14 or earlier | v1.2.9.15 → v1.2.9.22 → v1.3.0.30 → v1.3.1.4 → latest |
| v1.2.9.17 – v1.2.9.21 | v1.2.9.22 → v1.3.0.30 → v1.3.1.4 → latest |
| v1.3.0.30 | v1.3.1.4 → latest |
| v1.3.1.4+ | Latest directly |
Download firmware from Creality’s site, put the .img on a FAT32 USB drive, insert into the printer, and follow the on-screen prompts. Factory reset from Settings before installing rooted firmware.
After factory reset, root access must be re-enabled (Step 1) and community firmware reinstalled (Step 3).