Where Does Candle Store Settings and Files?
Where the Candle GRBL controller keeps settings and files, and why the whole folder counts as the backup.
Last updated
Candle ships as a portable archive rather than an installer. The extracted folder is the app: exe, libraries and local state travel together. There is no documented single config filename in the published builds.
That layout makes backup simple and version upgrades manual. Copy the folder whole instead of hunting one ini file. Machine parameters still live on the controller board, so export those separately from inside the app before wiping anything. Probe offsets and tool tables need that export step too.
Where Candle stores this, by platform
[ExtractFolder]\Candle.exe
Portable app folder with exe and local state together. No installer and no fixed published config filename. Back up the whole folder plus your G code files.
[ExtractFolder]/Candle
Same portable layout from the tar archive. Settings and heightmaps follow the extracted folder. Keep G code in a stable path outside tmp.
Frequently asked questions
How do I back up Candle settings?
Copy the entire extracted Candle folder to a safe place with the app closed. Settings and heightmaps travel with the exe since no installer spreads them elsewhere. G code files stay where you saved them, so collect those too.
Where does Candle store heightmaps?
Save the probed file explicitly after running the probe cycle. Heightmaps live alongside your G code in user chosen files, not in a fixed app path. The controller reads them from disk each run rather than caching inside.
Notice an outdated path? Let us know.