-
Notifications
You must be signed in to change notification settings - Fork 0
ESP32 and ESP3D
The ESP32 page exposes Ray5 ESP3D information, WebSocket status, EEPROM settings, backups, compare tools, and command boxes.
Use this page for deeper controller/network troubleshooting. Most users should not need it for normal jobs.
Use the top navigation:
ESP32
| Section | Use |
|---|---|
| Refresh All | Reload ESP3D info, EEPROM, and WebSocket status |
| Open Native ESP32 Page | Open the Ray5's own ESP32/ESP3D web page |
| ESP3D Info | View device/info output |
| WebSocket Status | Check live status connection details |
| EEPROM Settings | View/edit ESP3D EEPROM settings |
| Backup List / Compare | View backups and compare to current settings |
| Command Box | Send G-code or ESP commands |
| Raw Log | Read raw command/log output |
Ray5 Pilot backs up EEPROM before saves. Keep backups before changing network or ESP3D settings.
Sensitive values are masked in logs/backups where possible, but still treat backup files as private.
Be careful with ESP32 network settings. A wrong value can make the Ray5 harder to reach over Wi-Fi.
If changing network values, make sure you know how to reconnect to the Ray5 directly if needed.
The page includes separate command tools for:
- G-code commands.
- ESP commands.
Use the Dashboard Live Console for simple GRBL command testing. Use the ESP32 page when troubleshooting ESP3D-specific behavior.
| Problem | Fix |
|---|---|
| Native ESP32 page will not open | Check Ray5 IP and network |
| EEPROM load fails | Ray5 ESP3D API may be busy/offline |
| Save is blocked | Backup may have failed or value validation failed |
| Network save is blocked | Network-changing settings require explicit permission |
| WebSocket status fails | Confirm port 8849 and Ray5 connectivity |
| Raw log exposes private info | Do not share full logs without checking/redacting |