System Configuration Guide
- This guide will walk you through the basic configuration of the FlyOS-Fast system, helping you get started quickly and optimize your user experience.
Configuration Methods
- Configure the system via Config Myprint software
- Configure the system via a browser
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.
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.
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.cfgfiles or duplicate configurations from other printers in the folder.
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.
Klipper Web Interface
Select Fluidd or Mainsail. This option only affects the default web interface used in Klipper mode.
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.
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.
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.
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.
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.
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.
After writing is complete, perform the following checks:
- Open
FlyOS-Conf/config.txt. - Confirm that
boardexactly matches the actual device. - Confirm that only the required screen UI and camera service are enabled.
- Confirm that
canbus_bitrateis consistent with all CAN device firmware. - After saving, safely eject the system card, then insert it into the target device to start.
- When configuring the system via a browser, please ensure that your device is connected to the same network so that you can access the configuration interface smoothly.
- You need to install the system card and start the system according to the SSH connection to the host machine tutorial, and then access the system IP address through a browser for configuration.
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 |
- Back up the original configuration file first.
- Keep the
key=valueformat; do not change it tokey: 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
- After flashing the image, reconnect the system card to the computer.
- Open the removable disk named
FlyOS-Conf. - Open
config.txtwith a plain text editor. - Modify
boardaccording to the actual device, then set Wi-Fi, print mode, screen, and CAN baud rate. - Save the file and safely eject the system card, then insert it into the device and boot.
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.
- Ensure the computer and the host board are connected to the same network.
- Open the device IP address in a browser, for example
http://192.168.1.2/. - In Fluidd, uncheck "Filter hidden files and folders," or in Mainsail, check "Show hidden files."
Loading... | Loading... |
- Open
sys-config.confin the.flyos-configfolder.
- Modify the required configuration items and save.
- Completely restart the host board to reload system services and hardware configuration.
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.
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 |
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.