Frequently Asked Questions¶

Find answers to common questions about TrueFidelity Desktop.

General¶

Q: Which operating systems are supported?

A: Windows 10/11 (x64), macOS 10.15+, and Linux (x86_64 with GUI). Docker Desktop is required for ECU simulation.

Q: Does TrueFidelity require administrative privileges?

A: Installation may require elevated permissions. Day-to-day usage requires Docker Desktop running, which may need admin setup initially.

Q: Where are application settings stored?

A: Settings are stored in browser local storage under the key truefidelity-settings. Application cache locations vary by OS: - Windows: %APPDATA%\TrueFidelity - macOS: ~/Library/Application Support/TrueFidelity - Linux: ~/.config/TrueFidelity

Q: Does TrueFidelity require Docker?

A: Yes, Docker Desktop is required for ECU simulation.

System Design & Files¶

Q: How do I share a system design with colleagues?

A: Share the .json system definition file. Include any referenced BLF/MDF4 log files and DBC signal definition files.

Q: Can I open multiple systems at once?

A: TrueFidelity Desktop works with one system at a time. Switch between saved systems using File → Open.

Q: How do I recover a system after a crash?

A: Reload the last saved .json system file. Always save your work frequently as there's no autosave feature currently.

Q: What file formats are supported?

A: - System definitions: JSON format (truefidelity-system.json) - Log files: BLF and MDF4 (version 4.x) - Signal definitions: DBC files - Traffic export: Text, CSV, JSON, candump - Capture recording: BLF, MDF4, CSV

ECU Management¶

Q: How do I add an ECU to my system?

A: In System Design mode, drag an ECU from the Toolbox onto the System Canvas. Configure its properties in the Properties panel.

Q: Why won't my ECUs start?

A: 1. Ensure Docker Desktop is running 2. Check Docker has sufficient resources (8+ GB RAM, 4+ CPU cores) 3. Review ECU Console panel for error messages

Q: How do I connect ECUs to networks?

A: ECUs connect to bus nodes, not directly to each other: - Drag from ECU port to a bus node on the network - CAN networks need CAN bus nodes - Ethernet networks need switch ports - LIN networks need LIN bus nodes

Q: Can I run multiple ECU systems simultaneously?

A: Yes, but each ECU container consumes CPU and memory. Monitor resources using the Resource Monitor panel and Docker stats.

Q: What happens if an ECU crashes?

A: The ECU Hardware Status panel shows error state (red indicator). Check ECU Console panel for error messages. Stop and restart the system from the toolbar.

Q: Can I modify ECU configuration while running?

A: No, you must stop the system first. Make changes, save the system, then restart.

Monitoring & Console¶

Q: Why can't I connect to an ECU terminal?

A: - Terminal access is only available for Linux-based ECUs (FSL Linux, Ubuntu) - ECUs running Zephyr or FreeRTOS do not support terminal access - Verify ECU is running (green status in ECU Hardware Status panel) - Use ECU Console for log viewing on all ECU types - For Zephyr ECUs, use GDB debugging instead of terminal

Q: How do I filter logs from a specific ECU?

A: In the ECU Console panel, use the ECU dropdown filter at the top to select a specific ECU. You can also filter by log level (INFO, WARNING, ERROR, DEBUG).

Q: Why are Resource Monitor graphs showing zero?

A: - Verify agent code is included in your firmware build (resource data is collected by agent code running on the ECU) - Ensure ECUs are actually running - Check time range dropdown includes recent activity - Verify Resource Monitor panel is visible - Docker stats must be accessible

Q: Can I export monitoring data?

A: Yes, you can export: - Network Traffic view: Text, CSV, JSON, or candump format - Capture recordings: BLF, MDF4, or CSV format - Signal data as CSV - Screenshots of charts (PNG format)

Playback & Analysis¶

Q: Why does playback stutter on large logs?

A: - Move BLF/MDF4 files to local SSD (avoid network drives) - Start with 1x playback speed - Close unused panels - Clear Network Traffic panel if full - Limit charted signals to 4-6

Q: Can I play multiple logs simultaneously?

A: No, the Signal Player works with one log file at a time. You can switch between files but not play them concurrently.

Q: How do I handle very large BLF files?

A: - Files over 2 GB may cause performance issues - Consider splitting into smaller segments externally - Work with filtered subsets when possible - Ensure adequate system memory (16+ GB recommended)

Signals & DBC¶

Q: What happens if multiple DBC files define the same signal?

A: The first loaded DBC takes precedence. Remove and re-add DBC files to change priority.

Q: How do I handle encrypted CAN messages?

A: TrueFidelity doesn't decrypt messages. Decrypt using external tools before importing.

Q: Why aren't my signals decoding?

A: - Verify correct DBC file is loaded - Check CAN IDs in DBC match those in log - Ensure standard vs. extended ID format matches - Verify byte order (Intel vs. Motorola) is correct

Q: Can I edit DBC files within TrueFidelity?

A: No, use external DBC editors. TrueFidelity imports DBC files for signal decoding only.

Data Injection¶

Q: How do I inject CAN messages?

A: Use the Signal Player & Injection panel: 1. Open Signal Viewer and click on a signal row to configure injection 2. Set the override value and injection options 3. Start the system (ECUs must be running) 4. Click "Start all" in the Injection controls section

Q: Can I schedule injection patterns?

A: Currently only simple Start/Pause/Stop controls are available. Complex scheduling features are not yet implemented.

Q: How do I stop injection quickly?

A: Click Stop in the Signal Player panel or stop the entire system from the toolbar.

Exports & Reports¶

Q: Why is my export empty?

A: - Verify the timeline range contains data - Check that signals are selected - Ensure filters aren't excluding all data - Confirm the source file has loaded properly

Q: Where are exports saved?

A: You choose the location when exporting. There's no default export folder setting.

Q: What export formats are available?

A: - Traffic export (from Network Traffic panel): Text, CSV, JSON, candump - Capture recording: BLF (Vector), MDF4, CSV - Signal data: CSV with decoded values - Charts: PNG screenshots

Q: Can I customize export formats?

A: No, export formats are fixed. CSV includes timestamps and signal values. BLF maintains raw CAN frame data.

Performance & Stability¶

Q: How do I improve performance?

A: - Increase Docker Desktop resources (memory and CPU) - Use local SSD storage for files - Clear accumulated data in panels - Close unnecessary panels

Q: The app feels sluggish after hours of use.

A: - Clear Network Traffic panel - Restart TrueFidelity Desktop - Clean Docker containers: docker system prune - Check system memory usage

Q: How much memory does TrueFidelity need?

A: - Minimum: 8 GB system RAM - Recommended: 16 GB for large files - Docker Desktop should have 8+ GB allocated

Docker & Containers¶

Q: Do I need Docker Desktop?

A: Yes, Docker Desktop is required for ECU simulation.

Q: How do I configure Docker resources?

A: Open Docker Desktop Settings: - Memory: Allocate at least 8 GB - CPU: Allocate at least 4 cores - Disk: Ensure adequate space for images

Q: What if Docker won't start?

A: - Check Docker Desktop is installed - Verify virtualization is enabled in BIOS - On Linux, ensure user is in docker group - Try restarting Docker service

Q: How do I clean up Docker resources?

A: Run these commands:

docker container prune  # Remove stopped containers
docker image prune -a   # Remove unused images
docker system prune -a  # Complete cleanup

Settings & Configuration¶

Q: What settings can I customize?

A: Currently only delete confirmations can be toggled in Settings. More options are planned for future releases.

Q: How do I reset settings?

A: In Settings dialog, click "Reset to Defaults" or clear browser local storage.

Q: Is there a light theme?

A: Currently only dark theme is available. Light theme is planned for a future update.

Troubleshooting¶

Q: How do I capture logs for support?

A: 1. Open browser console (F12) 2. Reproduce the issue 3. Copy console output 4. Include Docker logs: docker logs <container-id>

Q: What information should I provide to support?

A: - OS and version - Docker Desktop version - TrueFidelity Desktop version - Steps to reproduce - Browser console logs - Screenshots of the issue

Q: Where can I find more help?

A: - Check the Troubleshooting guide for detailed solutions - Review other documentation pages - Contact support with diagnostic information

Updates & Installation¶

Q: How do I update TrueFidelity?

A: Download and run the latest installer. Your settings and system files remain intact.

Q: Will updates modify my system files?

A: No, JSON system files are forward compatible. Always keep backups as a best practice.

Q: Can I run multiple versions?

A: Not recommended. Use one version at a time to avoid conflicts.

Keyboard Shortcuts¶

Q: What keyboard shortcuts are available?

A: - Ctrl/Cmd + N: Create new system - Ctrl/Cmd + O: Open system - Ctrl/Cmd + S: Save system - Ctrl/Cmd + R: Refresh application - F12: Open developer console - Escape: Close dialogs - Delete: Remove selected element (with confirmation)

Q: Can I customize shortcuts?

A: No, keyboard shortcuts are currently fixed. Customization is planned for future releases.

Still Need Help?¶

If your question isn't answered here:

Check the Troubleshooting guide for detailed problem solutions
Review other documentation sections
Gather diagnostic information (logs, screenshots, system info)
Contact your support representative with complete details