Troubleshooting

This page lists common issues and their resolutions. If a problem persists, collect the log files (see Collecting logs) and forward them to support.

Hardware acquisition

The acquisition frontend is not detected

• Confirm the device is connected and powered, then reopen the acquisition tab so the device list refreshes.
• A USB device binds to one driver at a time. The Deepsona path needs the device on its self-developed binding (portable recorders → WinUSB; modular controllers → FTDI). If the device is on another driver, the selected path will not enumerate it.
• Check Settings → Acquisition Driver. The default is Deepsona Driver (self-developed). Switch to Vendor Driver only if you intend to use the vendor stack.

Channels show no signal or a flat line

• Verify the channel is enabled and its sensor sensitivity is set correctly in the Recorder configuration.
• For ICP sensors, confirm ICP power is switched on for that channel.

Geometry / CAD import

An imported STEP model looks like a wireframe instead of a solid surface

Full curved-surface tessellation uses an external OpenCASCADE converter. When it is not present, Deepsona automatically falls back to a dependency-free wireframe importer — the model still loads, at lower fidelity. To get full surfaces, ensure tools\step2mesh.exe is deployed next to the application. No Python installation is required on the target machine.

AI Assistant

"AI is not configured: no API key found"

• Open Settings → AI Assistant, choose a provider, and enter its API key.
• Reopen the AI panel after saving — the key is read when the panel is opened.
• Alternatively, place a .env file next to the application with DEEPSEEK_API_KEY=....

"Model not exist" or an authentication error

• Check that the key matches the selected provider (a DeepSeek key will not work against OpenAI, etc.).
• If you set a custom Model under Advanced, confirm the model name is valid for that provider; leave it empty to use the provider default.

Performance

The application starts slowly on first launch

On a clean machine, antivirus (e.g. Windows Defender) may scan the signed binaries on first run. Subsequent launches are faster. Adding the installation folder to the antivirus exclusion list removes the delay.

Collecting logs

Open Settings → Diagnostics → Open log folder. The application folder contains crash.log (unhandled-exception details). The USB acquisition log is written to %TEMP%\vlisten_winusb.log. Send both files when reporting a problem.