“Configured Xyce executable path is invalid” in the status bar —
open Plugin Settings and make sure the Xyce path points to the
Xyce executable, not a folder or an unrelated file.
“No netlist content to simulate” — the netlist is empty. In
standalone mode, open a .cir file first; in KiCad mode, check the
schematic produces a netlist.
“Failed to create temporary netlist file” — a transient system
problem; retry the run.
Check the Simulation Output panel
for the Xyce error messages — parse errors, unknown devices, and
convergence failures are reported there line by line.
While the run is in flight the status bar already counts what Xyce has
reported: an amber N warnings and a red N errors. Clicking the
status bar opens the output panel, and clicking a count in the panel
header jumps to the first occurrence.
“Simulation failed (exit code N)” — the Xyce process exited with
an error; the log above it usually contains the cause.
“Simulation finished but output file could not be found” — the
run completed but produced no plottable output. Make sure a .PRINT
line is present for the analysis you ran; any plottable format works
(RAW, PROBE, CSV or the default .prn formats — see
Simulation Output Files).
DC convergence problems: add .NODESET hints or .IC conditions in
the Operating Point tab, or save
a converged bias point with .SAVE and reuse it.
The progress bar only fills for a transient analysis: Xyce reports
its progress as a percentage of the simulated time and reports nothing
for a DC sweep, an AC, a harmonic balance or an operating point run.
Those runs show an indeterminate bar with the elapsed time instead,
which is all Xyce knows at that point.
The percentage moves in coarse steps on a short run, and Xyce never
reaches 100% — the run simply ends after the last marker it wrote.
The estimated time is Xyce's own extrapolation from the steps taken so
far, so it grows after a hard part of the run and settles again
afterwards.
Click the status bar to open the output panel and read the live log;
the Current system time markers show how far the run really is.
“No expressions selected for FFT” — select at least one
expression in the FFT dialog.
“FFT computation skipped: no data in the selected range” — the
chosen Data Range (Current Zoom / Custom) contains no samples. Widen
the zoom window or use All.