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 directly via the device. This function is particularly useful in the following scenarios:
- Unstable or unavailable network connections
- Rapid deployment of print tasks
- Offline printing environments
- File transfers between multiple devices
Detailed Usage Steps
1. U Disk Preparation and Formatting
- Capacity Requirements: It is recommended to use a U disk with a capacity of 8GB or more
- File System: Must be formatted as
FAT32 - Formatting Methods:
- Windows: Right-click the U disk → Format → Choose FAT32
- macOS: Disk Utility → Erase → MS-DOS (FAT)
2. File Preparation and Storage
- Supported Format: Standard G-code files (
.gcodeextension) - File Placement: Copy G-code files directly to the root directory or any folder on the U disk
- File Naming: Use English names, avoiding 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
- The U disk files will appear in the file manager on the Web interface
4. File Selection and Printing
- Browse the U disk files via the device's Web interface
- Click the target G-code file to preview it
- Click "Start Printing" after confirming the print parameters
- The system will automatically load the file and begin the print task
Important Notes
- It is safe to remove the U disk during printing as the system copies the file locally before starting the print
- Confirm the file integrity before printing to avoid interruptions
- Large G-code files may take longer to load; please be patient
Frequently Asked Questions
❓ U Disk Not Recognized
Symptoms: No response after inserting the U disk, and its contents are not displayed in the file manager
Solutions:
- Check if the U disk is formatted as FAT32
- Try using a different USB port
- Test the U disk's compatibility on other devices
- Restart the device and reinsert the U disk
❓ File Reading Failure
Symptoms: U disk is recognized, but G-code files cannot be read
Solutions:
- Confirm that the file extension is
.gcode - Check if the file is damaged and attempt to re-slice it
- Ensure the file has no read/write restrictions
- Avoid using Chinese or special characters in filenames
❓ U Disk Removed During Printing
Symptoms: Concern about printing being affected after accidentally removing the U disk
Solutions:
- No need to worry: The system has already copied the file locally before printing began
- The print task will continue normally, unaffected by the U disk's connection status
- You can reinsert the U disk for the next task after printing completes
❓ 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), which may have compatibility issues
- Regularly clean the U disk to maintain sufficient free space
- Consider optimizing slicing settings for large G-code files based on their size
❓ 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 Practice Recommendations
File Management
- Create categorized folders on the U disk to better manage multiple print files
- Regularly back up important G-code files
- Clean up completed print files promptly after printing
Device Maintenance
- Safely eject the U disk before physically removing it
- Regularly check whether the USB ports are 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 that the filament is sufficient and the bed is leveled
- For critical print tasks, it is recommended to test a small section locally first
Technical Support
If you encounter issues not covered in this document, please seek assistance through the following methods:
- Check the system logs for detailed error information
- Contact technical support with a clear problem description
- Visit the official forum to view related discussions and solutions