Installing on Other Hosts
This page is for ordinary Linux hosts that are not running FlyOS-FAST, such as Raspberry Pi or FLY Pi systems with Klipper already installed.
- The system must have Klipper installed, with the
/home/<username>/klipperdirectory existing. - The Klipper data directory must be configured, with the
/home/<username>/printer_datadirectory existing. - 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 complete the following steps:
- Check for the Klipper and
printer_datadirectories. - Clone or update the FlyScreen project to
/home/<username>/FlyScreen. - Select the appropriate FlyScreen executable based on the system architecture.
- Copy
FlyScreen.confto/home/<username>/printer_data/config/FlyScreen.conf. - Create and enable the
FlyScreen.service. - Stop and disable any running KlipperScreen service.
- Add
FlyScreentomoonraker.asvc.
Status Check
After installation, use the following command to check the service status:
systemctl status FlyScreen.service
View real-time logs:
journalctl -u FlyScreen.service -f
Common Issues
Klipper Not Detected
Please confirm that Klipper exists in the current regular user's home directory:
ls -ld ~/klipper
If Klipper is installed in another path, please organize the directory according to the current system's Klipper installation method, or contact after-sales support to confirm if the one-click script is suitable.
Data Directory Not Found
Please confirm that printer_data exists in the current regular user's home 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 Disabled After Installation
This is normal behavior. FlyScreen and KlipperScreen are both on-screen interfaces. The installation script stops and disables KlipperScreen to prevent two screen services from occupying the display device simultaneously.
Configuration Guide: FLY Screen Configuration Guide