U Disk Printing Function User Guide
This document details how to use the U disk printing function in the FlyOS-Fast system and provides solutions for common issues.
Function Overview
The U disk printing function allows users to store G-code files on a U disk and execute print tasks by directly reading the files from the device. This function is particularly suitable for the following scenarios:
- Unstable or unavailable network connections
- Rapid deployment of print tasks
- Offline printing environments
- File transfer between multiple devices
Detailed Usage Steps
1. U Disk Preparation and Formatting
- Capacity Requirement: An 8GB or larger capacity U disk is recommended
- File System: Must be formatted as
FAT32 - Formatting Methods:
- Windows: Right-click the U disk → Format → Select FAT32
- macOS: Disk Utility → Erase → MS-DOS (FAT)
2. File Preparation and Storage
- Supported Format: Standard G-code files (
.gcodeextension) - File Placement: Copy the G-code files directly to the U disk root directory or any folder
- File Naming: It is recommended to use English names and avoid special characters
3. Connection and Recognition
- Insert the prepared U disk into the device's USB port
- The system will automatically recognize and mount the U disk
- In the web interface, U disk files will appear in the file manager
4. File Selection and Printing
- Browse the U disk files through the device's web interface
- Click on the target G-code file for preview
- Click "Start Printing" after confirming the print parameters
- The system will automatically load the file and begin the print task
Important Notes
- The U disk can be safely removed during printing, as the system copies the file locally before starting the print
- It is recommended to verify the file integrity before printing to avoid interruptions
- For large G-code files, loading time may be longer; please wait patiently
Frequently Asked Questions
❓ U Disk Not Recognized
Symptoms: No reaction after inserting the U disk, and the contents do not appear in the file manager
Solutions:
- Check if the U disk is formatted as FAT32
- Try using a different USB port
- Test the U disk on other devices for compatibility
- Restart the device and reinsert the U disk
❓ File Reading Failure
Symptoms: The U disk is recognized, but the G-code files cannot be read
Solutions:
- Confirm that the file extension is
.gcode - Check if the file is corrupted and try re-slicing
- Ensure the file has no read or write restrictions
- Avoid using Chinese or special characters in the file name
❓ U Disk Accidentally Removed During Printing
Symptoms: Concern about the impact of accidentally removing the U disk during printing
Solutions:
- No need to worry: The system has already copied the file locally before starting the print
- The print task will continue normally, unaffected by the U disk connection status
- The U disk can be reinserted after printing for the next task
❓ Slow Transfer Speed
Symptoms: Long file loading times affect printing efficiency
Optimization Suggestions:
- Use a U disk with a USB 2.0 interface (best compatibility)
- Avoid using USB 3.0 devices (blue interface), as they may have compatibility issues
- Regularly clean up the U disk to maintain sufficient free space
- Consider optimizing slicing settings if the G-code file is too large
❓ File Format Compatibility
Supported Formats:
- ✅ Standard G-code files (
.gcode)
Unsupported Formats:
- ❌ 3D model files (
.stl,.obj, etc.) - ❌ Slicing project files
- ❌ Other binary files
Best Practices
File Management
- Create categorized folders on the U disk to manage multiple print files
- Regularly back up important G-code files
- Clean up completed files promptly after printing
Device Maintenance
- Safely eject the U disk before physically removing it
- Regularly check whether the USB port is loose or dusty
- Keep the system firmware updated to the latest version
Print Preparation
- Preview the first layer before each print to ensure the file is correct
- Confirm sufficient filament and completed bed leveling
- For important print tasks, it is recommended to test a small portion locally first
Technical Support
If you encounter issues not covered in this document, please get help through the following methods:
- Check the system logs for detailed error information
- Contact technical support with a detailed problem description
- Visit the official forum to view related discussions and solutions