Skip to content

Help & About


Five items in the Help & About category:

ActionWhat It Does
Replay Welcome TourPlays the guided first-run tour again (see below)
Upload Debug BundleCollects logs and system info for support (see below)
Discord CommunityJoin discord.gg/RZCT2StKhr for community help and feedback
DocumentationVisit helixscreen.org/docs for guides and reference
AboutVersion, updates, and printer info (see below)

The first time you launch HelixScreen (after finishing the setup wizard), a short guided tour walks you through the interface. It’s an eight-step overlay that highlights one part of the screen at a time, with a Skip button to leave early, a Next button to move on (it reads Done on the last step), and a step counter so you know how far along you are.

The tour covers:

  1. Welcome to HelixScreen — a quick hello.
  2. Your printer at a glance — tap any home tile to open its full controls or toggle its state.
  3. Customize your home screen — long-press any tile to enter edit mode and rearrange, resize, remove, or add widgets.
  4. Print status — monitor prints in progress and pause, resume, or cancel the active job.
  5. Controls — move the toolhead, home axes, level the bed, and tune temperatures and fans.
  6. Filament — load, unload, and swap spools, and monitor your multi-filament system.
  7. Advanced — macros, the G-code console, calibration tools, and firmware updates.
  8. Settings — network, display, sound, printer setup, and more.

The tour runs on the Home screen; tapping a navigation button to leave Home ends it early. It also reappears automatically after a HelixScreen update introduces new tour content.

To see it again, tap Replay Welcome Tour at the top of Settings → Help & About. HelixScreen returns to the Home screen and restarts the tour from the beginning. This row is always available, so you can revisit the tour whenever you like.

When you need help troubleshooting an issue:

  1. Tap Upload Debug Bundle in Settings
  2. The bundle collects your logs, system info, and configuration (no personal data)
  3. Tap Upload to send the bundle securely
  4. Share the resulting code with the HelixScreen team on Discord or GitHub

Debug bundles include:

  • System logs - recent HelixScreen log output, starting from the very beginning of startup. That matters for problems that happen while HelixScreen is still loading your settings - a settings file that could not be read, or one that had to be restored from backup. On older versions those messages happened before the log was being kept, so the bundle showed no trace of them even though you saw the message on screen
  • Configuration — your HelixScreen settings (sanitized, no passwords or API keys)
  • Printer configuration — your Klipper printer.cfg and any files it includes, so support can see how your printer is actually set up (sanitized, see below)
  • Installed macros — the names of your G-code macros (names only, not what they do)
  • System info — OS version, hardware details, display resolution
  • Crash data — if a crash occurred, the crash report and backtrace
  • Crash history — past crash submissions with their GitHub issue references (helps support identify recurring issues)
  • Device identifier — a double-hashed ID used only for correlating telemetry data (not personally identifiable)

Debug bundles contain technical information needed for troubleshooting. Before anything is uploaded, HelixScreen strips passwords, API keys and tokens, web-hook URLs (Discord, Slack, Telegram, Pushover, ntfy, IFTTT), usernames and passwords embedded in URLs, email addresses, and MAC addresses.

One thing worth knowing: your printer.cfg is your own file, and HelixScreen can only redact patterns it recognizes. File paths are left intact, so an include pointing at /home/yourname/… will show that name. If you keep something unusual in your printer config that you would rather not share, look at it before you send the code — and remember a share code is only as private as the people you give it to.


Tap the About row at the bottom of the Settings panel to open the About overlay. This sub-overlay shows system information, update management, and HelixScreen branding.

ItemDescription
HelixScreen Logo & BrandingHelixScreen logo, “by Preston Brown”, copyright notice, and a scrolling contributor marquee
Printer NameThe name of your connected printer (set during setup wizard)
Current VersionYour installed HelixScreen version
Update ChannelStable, Beta, or Dev — only visible when beta features are enabled
Check for UpdatesCheck for and install new versions (hidden on Android)
KlipperInstalled Klipper version (fetched from Moonraker)
MoonrakerInstalled Moonraker version
OSOperating system version
Print HoursTotal print hours tracked — tap to open the History Dashboard
Open Source LicensesView licenses for all open source libraries used by HelixScreen

Tap Check for Updates to look for a newer release on your selected update channel. If one is available, an update dialog walks you through installing it. You’ll see the following stages:

  1. Update Available — Shows the new version. Tap Install to begin, or Cancel to dismiss.
  2. Downloading… — A progress bar tracks the download. You can still Cancel at this point.
  3. Verifying… — HelixScreen checks the downloaded file before installing.
  4. Installing… — The new version is written into place. Do not power off your printer while this is in progress.
  5. Update installed! — Confirmation that the new version is in place.
  6. Hang on, we’ll be right back! — HelixScreen restarts itself to run the new version.

If something goes wrong, an Update Failed screen appears with a Retry button so you can try again, or Close to dismiss.

Caution: Once installation begins, leave the printer powered on until HelixScreen restarts on its own. Interrupting an install can leave HelixScreen in an inconsistent state.

This row is hidden on Android, where updates are managed through the Play Store.

  • Tap the Printer Name row seven times to launch a hidden Snake game
  • Tap the Current Version row seven times to toggle beta features — works like Android’s “tap build number” developer mode

Tap the Current Version row seven times in Settings → About to toggle beta features.

When beta features are enabled:

  • Update Channel selector appears (Stable / Beta / Dev)
  • Additional items appear in the Advanced panel (Macro Browser, Timelapse, etc.)
  • Plugins section appears in Settings
  • Tap seven more times to disable
ChannelDescription
StableRecommended. Tested releases only.
BetaPreview builds with new features. May have rough edges.
DevDevelopment builds. Requires a dev_url configured under the update section of your config file.

Note: Selecting the Dev channel without a dev_url set in your configuration shows a “Dev channel requires dev_url in config” message and won’t check for updates. Dev builds are intended for HelixScreen contributors — most users should stay on Stable or Beta.


Back to Settings | Prev: System | Next: LED Settings