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 browser
Using Config Myprint to Configure the System Card
Config Myprint is suitable for graphically setting up the system card before the first boot. Connect the flashed system card to your computer, open the software, and wait for it to recognize the FlyOS-Conf partition.
Available options in the software may lag behind the test image updates. After flashing is complete, you should open FlyOS-Conf/config.txt and check whether board, screen, camera, and CAN rates match the actual hardware. New configuration items not displayed in the software need to be added manually; do not substitute with similarly named options.
Step 1: Enable System Configuration
Turn on the Enable System Configuration toggle.
Step 2: Complete Basic Settings
Configuration File Management
- Only select the folder that contains the printer configuration files; do not select a single file.
- The software will copy the configurations from the selected folder to the system card and load them on the first boot.
- Before writing, ensure the folder does not contain leftover
printer.cfgfiles or duplicate configurations from other printers.
Wi-Fi Network
Enter a valid Wi-Fi name and password. Leave this blank if you are using a wired network or plan to configure Wi-Fi later.
Klipper Web Interface
Select either Fluidd or Mainsail. This option only affects the default web interface used in Klipper mode.
Local Display
Select the actual display interface connected, then decide whether to enable KlipperScreen or FLY Screen. If both are enabled simultaneously, the system will prioritize booting KlipperScreen; when using FLY Screen, KlipperScreen should be disabled.
Step 3: Complete Advanced Settings
Printer Name
Set a printer name for easy identification. It is recommended to use only English letters, numbers, hyphens, and underscores.
Camera Service
Enable Crowsnest as needed. For the v1.4.0 beta image, if you need to use GoCam, confirm that config.txt contains crowsnest=0 and gocam=1 after flashing; do not enable both services simultaneously.
Language and Timezone
Select the initial system language and the actual timezone. Once the system is online, it will display the time based on this timezone.
CAN Communication Rate
Select a rate that matches the firmware of the mainboard and all CAN tool boards. Common values are 1000000, 500000, or 250000; different rates must not be mixed on the same CAN bus.
Step 4: Write and Verify
After completing all settings, click Manually Write Configuration. If you only select options in the interface without clicking write, the configuration will not be saved to the system card.
After the write is complete, perform the following checks:
- Open
FlyOS-Conf/config.txt. - Confirm that
boardexactly matches the actual hardware. - Confirm that only the required screen UI and camera services are enabled.
- Confirm that
canbus_bitratematches the firmware of all CAN devices. - Save, then safely eject the system card before inserting it into the target device to boot.
- 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 the 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 generally consistent, but board, screen models, and underlying hardware options must not be mixed.
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. If the name or password contains spaces or special characters, retain the double-quote format from the image.
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 product documentation | Only used when the corresponding product explicitly supports firmware flashing at first boot |
language, printer_name, and firmware are only used during the first boot process after flashing a full image. 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 H5 image cannot use the H3 board, and the H3 image cannot use the H5 board. The startup script will reject device values that do not belong to the current platform. Before the first boot, explicitly fill in the actual device and do not rely on the image default value.
The original default value in the H5 v1.3.10 image is board=fly-pi-v2, and in the H3 v1.3.10 image it is board=fly-lite2.1. Only keep the default value when the actual device exactly matches these models.
System and Communication
| Configuration Item | Default Value | Optional Values | Description |
|---|---|---|---|
localtime | Asia/Shanghai | World timezone names | System timezone used after network time synchronization |
console | serial | serial, both | System console mode; keep the default unless there is a clear requirement |
printer | klipper | klipper, rrf | Select whether to start the Klipper or RRF printing environment |
canbus_bitrate | 1000000 | 1000000, 500000, 250000 | System CAN bitrate, must match all devices on the bus |
Screen Types
| 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 from the table above | Select the display interface; none disables local display output |
rotate | auto | auto, 0, 90, 180, 270 | When auto, HDMI defaults to 0 degrees and TFT defaults to 90 degrees |
klipper_screen | 0 | 0, 1 | Enable KlipperScreen in Klipper mode |
fly_screen | 0 | 0, 1 | Enable FLY Screen in Klipper mode |
moon2uart | 0 | 0, 1 | Enable the Moon2UART serial screen service |
m2u_port | /dev/ttyS1 | Serial port path specified in product documentation | Serial port used by Moon2UART |
m2u_baud | 115200 | Baud rate required by the screen | Moon2UART serial port speed |
When both klipper_screen=1 and fly_screen=1 are set, the system starts KlipperScreen first. Screen model, interface orientation, and serial port path should follow the corresponding product documentation.
Web Interface and Camera
| Configuration Item | Default Value | Optional Values | Description |
|---|---|---|---|
klipper_webui | fluidd | fluidd, mainsail | Default web interface used in Klipper mode |
crowsnest | 0 | 0, 1 | Enable or disable the Crowsnest camera service |
The H3 and H5 v1.3.10 official images do not include a gocam configuration item. Do not copy settings from the v1.4.0 beta image.
Power Loss Shutdown and Advanced Configuration
shutdown_pin_state, shutdown_pin, spidev, and overlays are related to specific device hardware. They may only be modified when the corresponding product documentation provides explicit values. Do not copy configurations from other motherboards, other hardware revisions, or other chip platforms.
Power loss shutdown and power loss resume printing cannot be enabled simultaneously. When power loss resume printing is needed, disable power loss shutdown detection according to the corresponding product tutorial.