Skip to content

Getting Started

Jump to bottom
P0k3sm0t edited this page May 23, 2026 · 2 revisions

Getting Started

Use this page for first-time setup and the correct order to configure Ray5 Pilot.

What you need

  • A Longer Ray5 connected to your network.
  • The Ray5 IP address.
  • Ray5 Pilot v1.2.1 extracted to a folder.
  • Python and the required packages, unless you are using a packaged launcher that already handles startup.
  • Optional: a camera stream URL for overlay and timelapse.

First start

Start Ray5 Pilot using one of the methods in Launcher Options. Then open:

http://127.0.0.1:5050

The top navigation has:

  • Dashboard — normal control page.
  • Settings — Ray5 Pilot app settings.
  • GRBL — Ray5/GRBL controller $ settings.
  • ESP32 — ESP3D info, EEPROM tools, backups, and command tools.

First configuration checklist

  1. Open Settings.
  2. Set the Ray5 host/IP.
  3. Confirm the Web UI host is local unless you intentionally need LAN access.
  4. Set workspace min/max values for the laser bed.
  5. Configure camera URL if you use camera overlay or timelapse.
  6. Set SD file options.
  7. Keep test fire disabled until you are ready to test it safely.
  8. Save config.
  9. Return to Dashboard and check the Status card.

Confirm communication

On the Dashboard, the Status card should show useful values for:

  • State
  • X/Y position
  • Connection
  • System check
  • Ray5 HTTP reachable
  • Ray5 WebSocket reachable
  • SD card list working

If those are not working, go to Troubleshooting before running a job.

Basic workflow

  1. Create laser G-code in your design software.
  2. Import the file into Ray5 Pilot or place it in the watched folder.
  3. Review file bounds if available.
  4. Upload the file to the Ray5 SD card.
  5. Frame the job.
  6. Start the job only after the machine is safe.
  7. Watch the Status card during the run.

Recommended first test

Use a small low-power test file, not a large engraving. Confirm upload, frame, start, pause, resume, stop, status, camera, and SD refresh behavior before relying on the workflow for real projects.

Clone this wiki locally