Troubleshooting
Debug log
Record the exchanges with the machine and the error messages, from startup if needed, to understand a problem that happens again; nothing is sent.
The debug log records, time-stamped, the exchanges with the machine, the error messages shown and, when opened from startup, the first steps of the launch: version, system, language and the reason it was opened. It helps understand a problem that happens again: open it, repeat what goes wrong, then attach it to the support data. Nothing is sent.
- Mac and iPad: Settings › Maintenance › Debug Log. The setting is kept: at the next launches, the log opens from startup. It is written to
debug.log, in the app folder (beyond 5 MB, it becomesdebug-precedent.log); Show Log in Finder (Mac) or Share Log (iPad). - Launch option (Mac and desktop app): launching Dusty with
-d(or--debug) opens the log from startup for this session only, without changing the setting; Settings (or the Help menu) say so. On Mac, in Terminal:open -a Dusty --args -d. On Windows (installer from the website), add-dat the end of the target of a Dusty shortcut; the Microsoft Store version takes no option: tick Help › Debug log instead, it will open from the next startup. On Linux:dusty-desktop -d, or the AppImage name followed by-d. - Dusty Studio: Help › Debug log (kept in this browser, opened from the next page load), or
?debugadded to the page address (for example…/studio/?debug) for this page only. The log stays in the page: Save Debug Log… writes it to a file. - Desktop app: like Dusty Studio, and the log is also written as it goes to
debug.log, in the app’s data folder: it is kept even if the app closes badly.
This manual is also built into Dusty: press F1, or open the Help menu, to read the topic for what you are doing. A mistake, a missing answer? Tell us
Try it in Dusty, for free.
Free CNC milling software: design, toolpaths and machine control. Mac, iPad, iPhone, Windows and Linux.