-
-
Notifications
You must be signed in to change notification settings - Fork 8
Troubleshooting
This guide helps resolve common issues with UltraLog.
- Installation Issues
- File Loading Issues
- Display Issues
- Performance Issues
- Export Issues
- Platform-Specific Issues
Problem: Windows SmartScreen blocks the application with "Windows protected your PC" message.
Solution:
- Click "More info"
- Click "Run anyway"
Why this happens: The application is not code-signed with an Extended Validation (EV) certificate.
Problem: macOS Gatekeeper blocks the application.
Solutions:
Option 1: Right-click Open
- Right-click (or Control-click) the application
- Select "Open"
- Click "Open" in the dialog
Option 2: System Preferences
- Try to open the app (it will be blocked)
- Go to System Preferences → Security & Privacy → General
- Click "Open Anyway"
Option 3: Remove Quarantine
xattr -d com.apple.quarantine /path/to/ultralogProblem: Corrupt download or quarantine issues.
Solutions:
- Re-download the file
- Remove quarantine attribute:
xattr -cr /path/to/ultralog
Problem: The binary doesn't have execute permission.
Solution:
chmod +x ultralog-linux
./ultralog-linuxProblem: Error about missing shared libraries (libgtk, libcairo, etc.)
Solution: Install required dependencies:
Ubuntu/Debian:
sudo apt-get install -y \
libgtk-3-0 \
libglib2.0-0 \
libcairo2 \
libpango-1.0-0 \
libgdk-pixbuf2.0-0 \
libatk1.0-0Fedora:
sudo dnf install -y gtk3 glib2 cairo pango gdk-pixbuf2 atkProblem: UltraLog cannot identify the ECU format.
Possible causes and solutions:
-
Unsupported ECU system
- Check Supported-ECU-Formats for supported systems
- Request support via GitHub Issues
-
Wrong file format
-
ECUMaster: Export to CSV (not
.emuprolog) - Haltech: Export from NSP to CSV
-
Speeduino: Use
.mlgfiles directly
-
ECUMaster: Export to CSV (not
-
Corrupted file
- Try re-exporting from your ECU software
- Check file size is not 0 bytes
-
Wrong encoding
- Ensure CSV is UTF-8 encoded
- Avoid special characters in file path
Problem: UltraLog prevents loading the same file twice.
Solution: This is intentional behavior. If you need to reload:
- Close the existing tab for that file
- Load the file again
Problem: File loads successfully but channel list is empty.
Possible causes:
- Log file contains no data records
- Parser couldn't identify channels
- File is header-only (no actual data)
Solution:
- Verify the log file has actual data
- Check if logging was started in the ECU
- Try opening in a text editor to verify contents
Problem: Large files take a long time to load.
Normal behavior:
- Files up to 50MB: A few seconds
- Files 50-100MB: 5-15 seconds
- Files 100MB+: May take longer
Tips:
- Loading happens in a background thread - UI remains responsive
- Consider splitting very large logs in your ECU software
- Use release build for best performance
Problem: Values appear incorrect (e.g., temperature showing 363 instead of 90°C).
Solutions:
- Check Units menu and select appropriate units
- Verify your ECU's native units match expected
- Some channels may not support unit conversion
Note: Some ECUs store data in unusual units. Haltech stores temperature in Kelvin, which UltraLog converts automatically.
Problem: All channels appear as flat horizontal lines.
Possible causes:
- No variation in data - The logged values didn't change
- Very small variations - Normalized display makes small changes invisible
- Wrong time range - Zoomed to a static portion
Solutions:
- Check the Min/Max values in the legend
- Zoom out to see more data
- Verify the ECU was actually logging changing data
Problem: Legend displays NaN (Not a Number) or obviously wrong values.
Possible causes:
- Data contains invalid values from ECU
- Sensor errors during logging
- Parser couldn't interpret certain values
Solutions:
- Check the raw log file for unusual entries
- Verify sensor connections in your ECU
- Report the issue with a sample file
Problem: Chart lines look too similar.
Solutions:
- Enable Colorblind Mode (View → Colorblind Mode)
- Select fewer channels (max 10)
- Use channels that don't overlap
Problem: UI feels sluggish, especially with large files.
Solutions:
-
Check build type
- Release builds are much faster than debug builds
- If building from source:
cargo build --release
-
Close unused tabs
- Each open file uses memory
- Close files you're not actively analyzing
-
Select fewer channels
- More channels = more rendering work
- Focus on channels you need
-
Check system resources
- Close other heavy applications
- Ensure adequate RAM (8GB+ recommended for large files)
Problem: UltraLog using excessive RAM.
Normal memory usage:
- Empty: ~100MB
- Per file: ~1-2× file size
- Large files may use 500MB+
Solutions:
- Close tabs for files you're not using
- Restart the application periodically
- Consider splitting very large log files
Problem: Playback animation is not smooth.
Solutions:
- Use release build
- Reduce playback speed
- Select fewer channels
- Close other applications
Problem: Exported PNG shows nothing or is entirely black.
Solutions:
- Ensure at least one channel is selected
- Verify the chart area shows data
- Try zooming to a different view before export
Problem: Error when trying to export PDF.
Solutions:
- Ensure you have write permission for the save location
- Try a different save location
- Avoid special characters in filename
Problem: PNG export appears pixelated or low resolution.
Current behavior: Export captures the current view at screen resolution.
Tip: Maximize the window before exporting for higher resolution.
Issue: Application crashes on startup
- Ensure Windows 10 or later
- Install Visual C++ Redistributable if missing
- Try running as administrator
Issue: File dialog doesn't open
- Restart the application
- Check antivirus isn't blocking
Issue: Application name shows as "ultralog" in Dock
- This is normal for command-line distributed binaries
- Wrap in .app bundle for proper name display
Issue: Drag and drop doesn't work
- Grant file access permissions when prompted
- Check System Preferences → Security & Privacy → Privacy → Files and Folders
Issue: Window decorations missing
- May occur on some tiling window managers
- Try running with
GDK_BACKEND=x11 ./ultralog-linux
Issue: Blurry text on HiDPI displays
- Set scaling:
GDK_SCALE=2 ./ultralog-linux - Or adjust your desktop environment's scaling settings
- Check this troubleshooting guide
- Search existing GitHub Issues
- Try the latest release version
When opening a GitHub issue, include:
- UltraLog version (check Help → About)
- Operating system and version
- Steps to reproduce the issue
- Expected behavior vs actual behavior
- Sample log file if related to parsing (if possible)
- Error messages or screenshots
For new features or ECU support:
- Open a GitHub Issue
- Describe the use case
- For ECU support: include ECU name, software version, and sample file
| Problem | Quick Fix |
|---|---|
| Can't open on Windows | Click "More info" → "Run anyway" |
| Can't open on macOS | Right-click → Open |
| Can't run on Linux | chmod +x ultralog-linux |
| Wrong units | Check Units menu |
| Slow performance | Use release build, close unused tabs |
| File won't load | Check format is supported, try re-export |
- FAQ - Frequently asked questions
- Installation - Detailed installation guide
- Supported-ECU-Formats - File format details
Links