FLYOS-FAST System Configuration Guide

This guide is used to set up the device platform, network, printing environment, screen, camera, and CAN communication for FLYOS-FAST. The system services for H3, H5, and H618 are used in a similar way, but hardware-related options cannot be copied across platforms.

Pre-configuration Confirmation

Before starting, confirm the following information:

Item	Content to Confirm
System Image	The image platform matches the device chip: H3, H5, or H618
Device Model	Used to select the correct board
Printing Environment	Whether Klipper or RRF is used
Local Display	No screen, HDMI, FLY-TFT, USB screen, KlipperScreen, FLY Screen, or serial screen
Camera	Not enabled, Crowsnest, or GoCam newly added in FLYOS-FAST v1.4.0
CAN Rate	The mainboard, toolboard, and system uniformly use 1000000, 500000, or 250000

Prioritize setting board

board affects hardware configurations such as serial ports, SPI, screen, and onboard MCU. An incorrect selection may cause interfaces to become unavailable, screen abnormalities, or firmware handling errors on first boot. Do not copy the complete configuration first and then modify the device name; instead, start from the original config.txt of the current image and set each item one by one.

Recommended Configuration Order

1. Select the system image that matches the device and board。
2. Set up Wi-Fi, time zone, and printer name.
3. Choose printer=klipper or printer=rrf。
4. Choose the actual screen type and screen UI.
5. Enable the camera or Moon2UART as needed, and test them one by one.
6. When using CAN, set the baud rate for all devices uniformly.
7. After saving, restart and confirm each service and hardware interface one by one.

Choose configuration method

• Configure Myprint
• Directly modify the configuration file.

Using Config Myprint to Configure the System Card

Config Myprint is suitable for graphically setting up the system card before the first startup. Insert the burned system card into the computer, open the software, and wait for the software to recognize the FlyOS-Conf partition.

Software Interface and Image Versions

The options available in the software may be updated later than the system image. After writing is complete, open FlyOS-Conf/config.txt and check whether board, screen, camera, and CAN bitrate match the actual device. New configuration items not shown in the software need to be added manually; do not substitute them with similarly named items.

Step 1: Enable System Configuration

Turn on the Enable System Configuration switch.

Loading...

Step 2: Complete Basic Settings

Configuration File Management

• Only select the folder that stores the printer configuration file; do not select a single file.
• The software will copy the configuration from the selected folder to the system card and load it on the first startup.
• Before writing, confirm that there are no leftover printer.cfg files or duplicate configurations from other printers in the folder.

Loading...

Wi-Fi Network

Enter the available Wi-Fi name and password. You can leave this blank if you are using a wired network or plan to configure Wi-Fi later.

Loading...

Klipper Web Interface

Select Fluidd or Mainsail. This option only affects the default web interface used in Klipper mode.

Loading...

Local Display

Select the actually connected display interface, then decide whether to enable KlipperScreen or FLY Screen. If both are enabled at the same time, the system will start KlipperScreen first; when using FLY Screen, KlipperScreen should be disabled.

Loading...

Step 3: Complete Advanced Settings

Printer Name

Set an easily identifiable printer name. It is recommended to use only English letters, numbers, hyphens, and underscores.

Loading...

Camera Service

Enable Crowsnest as needed. For v1.4.0, if GoCam is needed, confirm after writing is complete that config.txt contains crowsnest=0 and gocam=1; do not enable both services at the same time.

Loading...

Language and Time Zone

Select the system's initial language and actual time zone. After the system connects to the network, it will display time according to this time zone.

Loading...

CAN Communication Bitrate

Select a bitrate consistent with the mainboard and all CAN toolboard firmware. Common values are 1000000, 500000, or 250000; different bitrates cannot be mixed on the same CAN bus.

Loading...

Step 4: Write and Check

After completing all settings, click Manual Write Configuration. If you only select options in the interface but do not click write, the configuration will not be saved to the system card.

Loading...

After writing is complete, perform the following checks:

1. Open FlyOS-Conf/config.txt.
2. Confirm that board exactly matches the actual device.
3. Confirm that only the required screen UI and camera service are enabled.
4. Confirm that canbus_bitrate is consistent with all CAN device firmware.
5. After saving, safely eject the system card, then insert it into the target device to start.

Modifying the Configuration File

The system configuration file of FLYOS-FAST appears under different names in different locations, but they all point to the same configuration:

Usage Scenario	File Location	Applicable Situation
System card connected to a computer	FlyOS-Conf/config.txt	Set network, device model, and initialization options before first boot
Inside the Linux system	/config/config.txt	Check configuration via SSH
Fluidd / Mainsail	.flyos-config/sys-config.conf	Modify options that are read at every boot online after system startup

Notes Before Modifying

• Back up the original configuration file first.
• Keep the key=value format; do not change it to key: value.
• Do not add duplicate configuration items with the same name; edit the original value directly when modifications are needed.
• Do not use the browser's webpage translation feature to edit the configuration, to avoid the content being rewritten.
• Use only English letters, numbers, hyphens, and underscores for names and paths whenever possible.
• Do not modify anything after ######### PLEASE DO NOT EDIT THE FOLLOWING #########.

• Modify the System Card Before First Boot
• Modify via Web Page After System Boot

1. After flashing the image, reconnect the system card to the computer.
2. Open the removable disk named FlyOS-Conf.
3. Open config.txt with a plain text editor.
4. Modify board according to the actual device, then set Wi-Fi, print mode, screen, and CAN baud rate.
5. Save the file and safely eject the system card, then insert it into the device and boot.

First Boot Items

Initialization items such as language, printer_name, and firmware should be modified here. After the system has completed first boot, editing these values will not re-trigger the initialization process.

1. Ensure the computer and the host board are connected to the same network.
2. Open the device IP address in a browser, for example http://192.168.1.2/.
3. In Fluidd, uncheck "Filter hidden files and folders," or in Mainsail, check "Show hidden files."

Loading...

Loading...

4. Open sys-config.conf in the .flyos-config folder.

Loading...

5. Modify the required configuration items and save.

Loading...

6. Completely restart the host board to reload system services and hardware configuration.

Web Page Modification Limitations

The web page method is suitable for modifying configuration items that are read at every boot. Initialization items that have already missed the first boot cannot be re-run by simply restarting; use the respective feature's own modification method instead.

Check After Saving

After restarting, verify at least the following items:

• The web page opens normally, and the print mode and web interface selection are correct.
• The local screen, touch orientation, and screen UI are functioning properly.
• Only the required optional services, such as camera or Moon2UART, are enabled.
• When using CAN, the system baud rate matches the firmware baud rate of the mainboard and toolboard exactly.
• Klipper or RRF can connect to the corresponding control board normally.

If the system fails to boot properly after modification, connect the system card to the computer, restore the previous config.txt, then modify and verify items one by one.

View configuration options by platform

• H618: C5 / C8P / Pi V3
• H3 / H5 devices

H618 Configuration Items

The following default values and optional values have been verified against FlyOS-Conf/config.txt in the H618 v1.3.10 official image; configurations newly added in v1.4.0 are marked separately.

Wireless Network

WIFI_SSID and WIFI_PASS are read at every boot. When using an open network, the password can be left blank; when using an encrypted network, both items must be filled in.

Configuration Item	Default Value	Optional Values	Description
WIFI_SSID	Empty	Wi-Fi name	Once filled in, the system automatically connects to this network at boot
WIFI_PASS	Empty	Wi-Fi password	Can be left blank for open networks

First Boot Settings

language, printer_name, and firmware are only used during the first boot process after a full image is flashed. After the system has completed its first boot, modifying these items will not re-execute initialization.

Configuration Item	Default Value	Optional Values	Description
language	zh-CN	Language codes listed in the image such as zh-CN, en, ja, ko	Sets the initial language for Fluidd and Mainsail
printer_name	Empty	Any name without special characters	Sets the initial printer name
firmware	/usr/lib/firmware/klipper/stm32h723-128k-usb.bin	A firmware path within the image, or /config/klipper.bin	C5, C5 V1.1, and C8P can automatically flash the onboard MCU according to board during first boot; Pi V3 will not use this item to flash an external mainboard

Auto-flash Conditions

Auto-flash is only executed when the first boot flag exists, both board and firmware are valid, and the firmware file exists. Do not manually create a first boot flag just to repeat flashing; for subsequent firmware maintenance, use the firmware flashing tutorial for the corresponding mainboard.

System and Mainboard

The following settings are read at every boot.

Configuration Item	Default Value	Optional Values	Description
board	none	fly-c5, fly-c5-v1.1, fly-c8p, fly-pi-v3	Selects the actual device model; this value affects the H618's serial port and SPI peripheral configuration
localtime	Asia/Shanghai	World time zone names	The system time zone used after network time synchronization
printer	klipper	klipper, rrf	Selects the print control environment to start
console	serial	serial, both	Sets the system console; keep the default unless there is a clear need
canbus_bitrate	1000000	1000000, 500000, 250000	Sets the system CAN interface bitrate, which must match all CAN devices on the bus

Correctly Select board

The original image configuration is board=none, and the device will first try to read the hardware identification result; if it still cannot be identified, H618 v1.3.10 will fall back to fly-c5. Therefore, C8P, C5 V1.1, and Pi V3 users should explicitly select their device model before first boot rather than relying on the fallback value.

The H618 peripherals enabled by different board values are as follows. This table is only used to illustrate the impact of an incorrect selection and does not mean that these serial ports or SPI interfaces can be freely repurposed.

board Configuration Value	Onboard Peripherals Enabled by the System
fly-c5	UART1
fly-c5-v1.1	UART1, SPI1.2
fly-c8p	UART1, UART3, UART4, SPI1.2
fly-pi-v3	UART1, UART3, UART4, SPI1.2

Screen and Interface

Configuration Item	Default Value	Optional Values	Description
screen	hdmi	none, hdmi, fly-tft-v2-r, fly-tft-v2-c	Selects the display interface; none disables local display output
rotate	auto	auto, 0, 90, 180, 270	In auto, HDMI defaults to 0 degrees and FLY-TFT defaults to 90 degrees; manual angles are also applied to HDMI display and touch orientation
klipper_screen	0	0, 1	Enables KlipperScreen in Klipper mode
fly_screen	0	0, 1	Enables FLY Screen in Klipper mode
moon2uart	0	0, 1	Enables the Moon2UART serial screen service
m2u_port	/dev/ttyS1	Actual serial device path	The serial port used by Moon2UART
m2u_baud	115200	The baud rate required by the screen	Moon2UART serial communication rate

When klipper_screen=1 and fly_screen=1 are set at the same time, the system prioritizes starting KlipperScreen. When using FLY Screen, you should set klipper_screen=0 and fly_screen=1.

OTA Upgrades Retain Old Configurations

After an OTA upgrade from an older version, config.txt may lack fly_screen, m2u_port, or m2u_baud. If the corresponding functions are needed, add the configuration items according to the table above.

Klipper Web Interface and Camera

Configuration Item	Default Value	Optional Values	Description
klipper_webui	fluidd	fluidd, mainsail	The web interface used in Klipper mode
crowsnest	0	0, 1	Enables or disables the camera service

New Configuration in v1.4.0

Configuration Item	Default Value	Optional Values	Description
gocam	0	0, 1	Enables the GoCam UVC camera service

The v1.3.10 official version does not have gocam. In v1.4.0, if crowsnest=1 and gocam=1 are set at the same time, the system prioritizes starting Crowsnest. When using GoCam, you should explicitly set crowsnest=0 and gocam=1.

How to Use GoCam: View the GoCam camera service

Power-off Shutdown

In the original configuration of H618 v1.3.10, shutdown_pin_state and shutdown_pin are commented out by default, meaning power-off shutdown detection is not enabled. The trigger level may differ across products and hardware versions. Please fill them in according to the "Power-off Shutdown and Power-loss Resume Printing" document for the corresponding product, and do not directly copy values from other devices.

Mutually Exclusive Functions

Power-off shutdown and power-loss resume printing cannot be enabled at the same time. When power-loss resume printing is needed, keep power-off shutdown detection disabled.

Advanced Configuration

Configuration Item	Default Value	Optional Values	Description
spidev	spidev0.0	SPI device combinations explicitly given in the product documentation	Controls the SPI devices provided to the Linux user space

Items such as spidev and overlays are used for low-level hardware enabling. Unless explicitly required by a product tutorial, keep the image default values, and do not modify the content after ######### PLEASE DO NOT EDIT THE FOLLOWING #########.

H3 / H5 Configuration Items

The following configurations have been verified against the FlyOS-Conf/config.txt in the official H3 and H5 v1.3.10 images. The service configurations for both platforms are essentially the same, but board, screen models, and low-level hardware options cannot be used interchangeably.

Wireless Network

Configuration Item	Default Value	Optional Values	Description
WIFI_SSID	Empty	Wi-Fi name	Once filled in, the system attempts to connect to this network at startup
WIFI_PASS	Empty	Wi-Fi password	Can be left empty for open networks

These two items are read at every startup. When the name or password contains spaces or special characters, the double-quote format in the image should be preserved.

First Boot Settings

Configuration Item	Default Value	Optional Values	Description
language	zh-CN	Language codes listed in the image	Sets the initial language for Fluidd and Mainsail
printer_name	Empty	A name without special characters	Sets the initial printer name
firmware	Disabled by default	Firmware path specified in the product documentation	Only used when the corresponding product explicitly supports first-boot flashing

language, printer_name, and firmware are only used during the first-boot process after a full image is flashed. Do not uncomment firmware on your own or copy firmware paths from other products.

Device Platform and board

Image Platform	Device	board Configuration Value
H5	FLY-Pi	fly-pi
H5	FLY-Pi V2	fly-pi-v2
H5	FLY-Gemini V1	fly-gemini-v1
H5	FLY-Gemini V2	fly-gemini-v2
H5	FLY-Gemini V3	fly-gemini-v3
H5	FLY-C8	fly-c8
H3	FLY-Lite2	fly-lite2
H3	FLY-Lite2.1	fly-lite2.1
H3	FLY-MiniPad	fly-minipad

The image and device must match

H5 images cannot use H3's board, and H3 images cannot use H5's board. The startup script will reject device values that do not belong to the current platform. Before first boot, you should clearly fill in the actual device and not rely on the image's default value.

The original default value for the H5 v1.3.10 image is board=fly-pi-v2, and the original default value for the H3 v1.3.10 image is board=fly-lite2.1. The default value can only be retained when the actual device exactly matches these models.

System and Communication

Configuration Item	Default Value	Optional Values	Description
localtime	Asia/Shanghai	World time zone names	The system time zone used after network time synchronization
console	serial	serial, both	System console mode; keep the default unless there is a clear need
printer	klipper	klipper, rrf	Selects whether to start the Klipper or RRF printing environment
canbus_bitrate	1000000	1000000, 500000, 250000	System CAN bitrate, which must match all devices on the bus

Screen Type

Image Platform	screen Optional Values
H5	none, hdmi, fly-tft-v1, fly-tft-v2-r, fly-tft-v2-c
H3	none, hdmi, fly-tft-v1, fly-minipad-r, fly-minipad-c, fly-tft-v2-r, fly-tft-v2-c

Configuration Item	Default Value	Optional Values	Description
screen	hdmi	Values supported by the current platform in the table above	Selects the display interface; none disables local display output
rotate	auto	auto, 0, 90, 180, 270	When auto, HDMI uses 0 degrees by default, and TFT uses 90 degrees by default
klipper_screen	0	0, 1	Enables KlipperScreen in Klipper mode
fly_screen	0	0, 1	Enables FLY Screen in Klipper mode
moon2uart	0	0, 1	Enables the Moon2UART serial screen service
m2u_port	/dev/ttyS1	Serial port path specified in the product documentation	The serial port used by Moon2UART
m2u_baud	115200	Baud rate required by the screen	Moon2UART serial baud rate

When klipper_screen=1 and fly_screen=1 are both set, the system starts KlipperScreen first. The screen model, interface orientation, and serial port path should be based on the corresponding product documentation.

Web Interface and Camera

Configuration Item	Default Value	Optional Values	Description
klipper_webui	fluidd	fluidd, mainsail	The default web interface used in Klipper mode
crowsnest	0	0, 1	Enables or disables the Crowsnest camera service

The official H3 and H5 v1.3.10 images do not have a gocam configuration item. Do not copy the settings from the v1.4.0 image.

Power Loss Shutdown and Advanced Configuration

shutdown_pin_state, shutdown_pin, spidev, and overlays are related to specific device hardware. They can only be modified when the corresponding product documentation provides explicit values. Do not copy configurations from other mainboards, other hardware versions, or other chip platforms.

Power loss shutdown and power loss resume printing cannot be enabled at the same time. When power loss resume printing is needed, power loss shutdown detection should be disabled according to the corresponding product tutorial.

Common Feature Combinations

Goal	Key Configuration	Notes
Web only, no local screen	screen=none, klipper_screen=0, fly_screen=0	Moon2UART serial screen can be independently enabled as needed
HDMI + KlipperScreen	screen=hdmi, klipper_screen=1, fly_screen=0	rotate sets display and touch orientation
Use FLY Screen	klipper_screen=0, fly_screen=1	screen still needs to select the actual display interface
Use USB screen	klipper_screen=1, fly_screen=0 or fly_screen=1, klipper_screen=0	No need to configure screen=; requires v1.4.0 or above
Use Crowsnest	crowsnest=1	For v1.4.0, gocam=0 should also be kept
Use GoCam	crowsnest=0, gocam=1	Applicable to v1.4.0 and above; View tutorial
Use Moon2UART	moon2uart=1	Also verify m2u_port and m2u_baud
Use CAN	Set a unified canbus_bitrate	The system, mainboard, and all CAN nodes must be consistent

Completion check after restart

Check Item	Normal Result
Network	Accessible via device IP or direct connection address 10.10.10.1 Open the webpage.
Device Platform	Serial port, SPI, and onboard functions are consistent with the actual product
Print Service	Klipper or RRF only starts the selected environment
Screen	Display, touch, and rotation direction are normal
Camera	Run only one selected option from Crowsnest or GoCam
CAN	All nodes can be queried without any rate inconsistency errors

Modify only one group of related options at a time. If an exception occurs, first restore that group's configuration, and do not change multiple settings simultaneously. board, screen, CAN, and advanced hardware parameters, to avoid being unable to determine the source of the problem.