Other Host Installation
This page is intended for non-FlyOS-FAST general Linux hosts, such as Raspberry Pi, FLY Pi, and other systems that have already installed Klipper.
- The system must have Klipper installed, with the directory
/home/<username>/klipperpresent. - The system must have the Klipper data directory configured, with the directory
/home/<username>/printer_datapresent. - For non-FlyOS-FAST systems, use a regular user to execute
sudofor installation; do not switch directly to therootuser to run the script.
One-Click Installation
Log in to the host terminal as a regular user and execute:
curl -fsSL https://cnb.cool/3dmellow/public/FlyScreen/-/git/raw/main/scripts/install.sh | sudo bash
The installation script will automatically perform the following operations:
- Check the Klipper and
printer_datadirectories. - Clone or update the FlyScreen project to
/home/<username>/FlyScreen. - Select the corresponding FlyScreen executable based on the system architecture.
- Copy
FlyScreen.confto/home/<username>/printer_data/config/FlyScreen.conf. - Create and enable
FlyScreen.service. - Stop and disable any running KlipperScreen service.
- Write
FlyScreenintomoonraker.asvc.
Status Check
After installation, you can check the service status using the following command:
systemctl status FlyScreen.service
View real-time logs:
journalctl -u FlyScreen.service -f
Frequently Asked Questions
Prompt: Klipper not detected
Please confirm that Klipper exists in the current regular user's directory:
ls -ld ~/klipper
If Klipper is installed in a different path, please organize the directory according to the current system's Klipper installation method, or contact after-sales support to confirm whether the one-click script is suitable.
Prompt: Data directory does not exist
Please confirm that printer_data exists in the current regular user's directory:
ls -ld ~/printer_data
If a custom printer_data path is used, ensure that Moonraker and Klipper are properly configured before installing FlyScreen.
KlipperScreen is disabled after installation
This is normal behavior. Both FlyScreen and KlipperScreen are local display interfaces. The installation script will stop and disable KlipperScreen to prevent both screen services from occupying the display device simultaneously.
Configuration:FLY Screen Configuration