spectrum-analyzer-debug

Spectrum display freezing typically stems from capture not running, WebSocket stream disconnection, or frontend rendering issues. Check capture status via REST endpoint, verify WebSocket connection in browser console, and inspect for JavaScript errors to identify and resolve the root cause.

Incorrect frequency labels indicate inconsistency between frontend frequency calculations and backend spectrum endpoint data. Validate that FFT size, sample rate, and center frequency are consistent across capture settings and frontend calculations to restore accurate labeling.

Poor FFT resolution results from FFT size misconfiguration relative to sample rate. Increase FFT size or reduce sample rate to improve frequency resolution, then verify the change propagates through the spectrum endpoint and updates the display.

Excessive noise floor can indicate gain misconfiguration, improper sample rate settings, or bandwidth constraints. Validate sample rate matches hardware capability, check gain levels, and confirm the noise floor persists across multiple captures before adjusting hardware parameters.

Yes. The skill guides checking WebSocket connection status through browser developer tools, verifying REST capture status remains active, and identifying network or frontend errors causing disconnection to enable rapid reconnection or restart.

Performance degradation in spectrum display often stems from excessive FFT size, high sample rate overload, or frontend rendering bottlenecks. Optimize FFT configuration, validate WebSocket stream stability, and monitor browser resource usage to restore smooth waterfall updates.