FAQ & Troubleshooting¶
Common questions and solutions for WireFrame EDA issues.
Installation Issues¶
The application does not start / shows a blank window
Possible causes and solutions:
- Missing OpenGL driver — WireFrame requires OpenGL 3.3+. Check your GPU driver:
- Linux:
glxinfo | grep "OpenGL version"— should show 3.3 or higher. - Windows: Update your GPU drivers from the manufacturer (NVIDIA, AMD, Intel).
- Linux:
- Wayland compatibility — On Linux with Wayland, try forcing X11:
- Missing shared libraries (Linux) — Install missing dependencies:
- Corrupted config file — Delete the config and restart:
macOS: 'WireFrame cannot be opened because it is from an unidentified developer'
This is a Gatekeeper restriction. Follow these steps:
- Open Terminal and run:
- Then go to System Settings → Privacy & Security and click Open Anyway.
- Launch WireFrame again — it should open without the warning.
See Installation — macOS for full details.
Windows: SmartScreen blocks the installer
Windows SmartScreen may flag the installer because it has not yet accumulated enough reputation:
- Click More info on the SmartScreen dialog.
- Click Run anyway.
- The installer will proceed normally.
This is expected for new or infrequently downloaded software.
Linux: dpkg fails with dependency errors
Run the following after the failed dpkg install:
Activation & Sign-In¶
I cannot activate — the server is not responding
- Check your internet connection.
- Verify the activation server URL is correct (contact support if needed).
- If you're behind a corporate proxy, ensure the proxy allows HTTPS connections to the activation server.
- Try again after a few minutes — the server may be temporarily unavailable.
How do I reset my activation / log out?
Delete the configuration file:
- Linux:
~/.config/wireframe/user_config.json - Windows:
%APPDATA%\WireFrame\user_config.json - macOS:
~/Library/Application Support/WireFrame/user_config.json
On next launch, the activation overlay will appear again.
Can I use WireFrame on multiple computers with one license?
Check your license terms. Typically, a single license allows activation on a limited number of devices. Contact support for clarification.
Libraries¶
My KiCad symbols / footprints do not load
Common causes:
- Wrong file format — WireFrame supports KiCad v6/v7/v8
.kicad_symand.kicad_modfiles. Older.liband.modformats may have limited support. - File encoding — Ensure files are UTF-8 encoded.
- Corrupted files — Open the library file in a text editor and check for syntax errors.
- Parser errors — Check the Logger overlay for error messages during loading. They may indicate which symbol/footprint failed to parse.
How do I create custom footprints?
Use the built-in Footprint Wizard (Tools → Footprint Wizard):
- Configure pin count, layout (single, dual, grid, quad), pad size, and pitch.
- Preview the generated footprint in real time.
- Export to
.kicad_modformat.
See Footprint Libraries for details.
How do I link a footprint to a symbol?
- Load both symbol and footprint libraries.
- In the Library panel (schematic mode), right-click a symbol.
- Choose Link Footprint and select the corresponding footprint.
- Future instances of that symbol will automatically have the footprint assigned.
See Symbol Libraries.
Schematic Editor¶
Wires don't connect to pins — I see no junction dots
- Ensure the wire endpoint exactly touches the pin tip. Zoom in to verify alignment.
- Wire snapping is grid-based — if the pin is off-grid, you may need to zoom in and place the wire endpoint manually.
- Junction dots appear automatically when three or more connections meet at one point.
My net names are wrong or duplicated
- Check that Net Labels are placed correctly and their values match.
- The netlist is rebuilt from wires and labels. Use Properties panel to verify the net name of a selected wire.
- Conflicting net names can occur if two different labels are connected by the same wire — review the schematic for overlapping labels.
Undo/Redo does not work as expected
- Some operations (like loading libraries) are not undoable — they are immediate.
- If undo seems stuck, check the Logger for error messages.
- As a workaround, reload the file from disk (File → Open the same file).
PCB Editor¶
Ratsnest lines don't disappear after routing
- Ensure the trace connects exactly to the pad center at both ends.
- The ratsnest is recomputed after each routing action. If lines persist, the trace may not be on the correct layer or net.
- Check the net assignment in the Properties panel after selecting the trace.
DFM/DRC shows many clearance errors
- Review your Design Rules (Tools → Design Rules) — the default clearance may be too tight for your design.
- Common fixes:
- Increase minimum clearance.
- Increase trace width for power nets.
- Reroute traces that pass too close to pads or other traces.
- Double-click each violation to zoom to the problem area.
Zones (copper pours) look incorrect or have gaps
- Run zone fill rebuild after making changes to traces or footprints.
- Check zone priority — higher priority zones override lower ones.
- Verify the zone's net assignment and clearance settings.
- Gaps around pads are expected (clearance areas) unless the pad is on the same net (thermal connections).
Export & Fabrication¶
Gerber export produces empty files
- Ensure there is content on the layers you selected for export.
- Check that the board has a valid board outline (Edge.Cuts layer).
- Verify in the Gerber Viewer (Tools → Gerber Viewer) that the generated files contain data.
BOM CSV is missing components
- Only components with a non-empty Value property are included in the BOM.
- Ensure footprints are placed on the PCB (not in the "available" list).
PDF export has wrong colors or missing elements
- PDF export converts colors to black/grey for printing. This is by design.
- If elements are missing, ensure they are on visible layers before exporting.
Performance¶
The application is slow or laggy
Tips to improve performance:
- Reduce loaded libraries — unload libraries you don't need for the current project.
- Simplify zone fills — complex zones with many cutouts take longer to compute.
- Close unused tabs — each open document consumes memory.
- Check GPU acceleration — ensure your system uses hardware OpenGL, not software rendering.
- Reduce window size — on very high-DPI displays, a smaller window may help.
3D Viewer is very slow
- Loading STEP files requires significant computation (mesh tessellation). First load is slow, but subsequent renders use cached meshes.
- Use simpler 3D models if possible (low polygon count).
- Close the 3D viewer when not needed to free GPU resources.
Still Need Help?¶
If your issue is not listed here:
- Check the Changelog for known issues in your version.
- Search the GitHub Issues page.
- Open a new issue with:
- Your OS and WireFrame version.
- Steps to reproduce the problem.
- Any error messages from the Logger.
- Screenshots if applicable.