Wuji Hand
Wuji Glove
Wuji Studio
Wuji SDKData visualization
Device Logs
On the Visualization page, click the Show bottom bar icon in the top-right corner to expand the Bottom bar, then switch to the DEVICE LOG tab to view real-time logs from the device and software for troubleshooting.
Toolbar
| Control | Function |
|---|---|
| Filter logs | Keyword search across message content, level, source, and device name. The panel footer shows a "filtered / total" entry count (such as "42 / 100 entries") |
| Log Level | Filter by severity, showing logs at or above the selected level:
|
| Source | Multi-select filter for log sources:
|
| Auto-scroll | When enabled, scrolls to the bottom as new logs arrive. When disabled, lets you browse log history freely |
| Clear | Clears all current log entries |
Local Log Files
The log panel does not provide an export button. All logs persist to ~/.wuji/logs/ and roll over daily:
| File | Content and Use |
|---|---|
studio_YYYY-MM-DD.log | Combined runtime logs for the Studio app, SDK, and connected devices, identical to what the log panel displays. Messages from all three sources (Device, SDK, Studio) end up here. Share this file for everyday troubleshooting |
sdk_YYYY-MM-DD.log | Wuji SDK's own runtime logs. When used inside Studio, SDK content is also bridged into studio_*.log. When running the SDK standalone (such as Python package scripts) without Studio, this file is the only SDK log source |
device_YYYY-MM-DD.bin | Raw binary dump of communication data between the device and Studio. Not human-readable. Used to replay protocol frames or pinpoint a communication issue |
stderr_YYYY-MM-DD.log | The process's standard error output, capturing Rust panics and error messages written by third-party libraries. The file is typically small and only contains data when a crash or low-level exception occurs |
When no device logs are being produced, the panel shows a "Waiting for log messages..." status. Ensure the device is connected and running normally.