-
Notifications
You must be signed in to change notification settings - Fork 0
Jobs and Uploads
P0k3sm0t edited this page May 23, 2026
·
1 revision
The Imported Jobs card is for local G-code files that you want Ray5 Pilot to manage before uploading or running.
Typical laser G-code extensions:
.gcode
.gc
.nc
Ray5 Pilot includes a G-code safety scanner to help reject accidental 3D-printer slicer files.
- Click Choose File in Imported Jobs.
- Select a laser G-code file.
- Click Import.
- Refresh if needed.
- Review the job entry.
| Action | What it does |
|---|---|
| Upload | Sends the file to the Ray5 SD card |
| Upload + Run | Uploads the file, verifies it when possible, then starts it |
| Frame | Generates and sends a frame path around detected job bounds |
| Delete | Removes the imported local copy |
| Refresh | Reloads the imported job list |
If configured in Settings, Ray5 Pilot can watch a folder and automatically import compatible G-code files.
Use this when your design software exports to a fixed folder.
Settings > Upload controls whether Ray5 Pilot preserves original file bytes or rewrites/sanitizes the file.
Recommended default:
- Preserve original file content: on.
- Screen-compatible rewrite: off unless troubleshooting.
- M4 to M3 conversion: off unless your firmware needs it.
- Auto-shorten long filenames: useful for Ray5 screen readability.
The scanner checks for common 3D-printer slicer signs, including hotend/bed temperature commands and extrusion moves.
If a file is rejected, confirm you exported laser G-code and not 3D-printer G-code.
| Problem | Cause | Fix |
|---|---|---|
| File will not import | Unsupported extension or scanner rejection | Use laser G-code and supported extension |
| Upload fails | Ray5 HTTP/SD interface not responding | Check Status card and Ray5 screen |
| Upload + Run fails after upload | Ray5 may reconnect slowly after writing SD | Refresh SD list and verify file appeared |
| Bounds look wrong | G-code uses unusual coordinate setup | Check design software origin and G92 use |
| Frame is outside expected area | Workspace min/max or job bounds are wrong | Check Settings and file origin |