Troubleshooting
On this page you can find information on where to start if something does not work as desired. For problems with AI assistants that control SweepMe! via the MCP server, see Troubleshooting MCP connections.
Collecting Information
SweepMe! writes its debug messages to a file called debug.log in the SweepMe! public folder (open via File → Open Folder → Public). In this file you may find useful information about a problem. If you do not know what the messages mean, this information can still be useful for others, so always attach the debug.log file when asking for support.
- The file is overwritten each time SweepMe! starts. If SweepMe! crashed, copy the file before you start SweepMe! again.
- If several SweepMe! instances run at the same time, each further instance writes its own file named debug_instance<number>.log into the same folder.
Alternatively, you can open the Debug widget (key F2) to see debug messages while SweepMe! is running. To see all debug messages, start SweepMe! with the command line option --debugmode.
Common Problems
| Problem | Reason | Solution |
|---|---|---|
| SweepMe! does not start or crashes during startup | SweepMe! installation is broken | Go to the download page, download SweepMe! and install it again. |
| A defective component leads to a crash | Drivers or modules provided by third parties in the folders CustomDevices or CustomModules of the public folder might cause the problem. Move them to another folder, restart SweepMe!, and add them again one by one. | |
| The Windows version is not supported | SweepMe! requires a 64-bit Windows 10 or higher. Install the latest Windows updates and the latest version of SweepMe!. If the problem persists, send us your debug.log file. | |
| Starting SweepMe! using a command line yields "LoadLibrary(pythondll) failed". | This error typically occurs if you start SweepMe! from a path which is not supported by your Windows language settings and characters of your path are not correctly shown in the Windows command line. Please change your SweepMe! path or change your Windows language settings in order to support all characters. | |
| The measurement does not start | The sequencer is not filled correctly | Go to the Sequencer tab in SweepMe! and put the correct modules there. Also read about the Sequencer for complex measurements. |
| One or more modules are not configured correctly | Go to the tab of every module you use in the sequencer and check if you selected the correct driver, port, and parameters. | |
| One or more of the used drivers are broken or outdated | Open Tools → Version Manager, press Refresh online versions and check if a newer version of the driver is available. You can also check the information about your instrument on our website. | |
| The measurement does not start and a message says that measurements with multiple branches require a SweepMe! Pro license | From version 1.6, the free version runs measurements with one active branch in the sequencer. | Uncheck the modules of all branches except one, or use SweepMe! Pro. The message also offers to get a SweepMe! Pro trial. See Licenses. |
| The measurement does not start and a message says that a valid SweepMe! Pro license is required for a Pro module | The sequence uses a Pro module, but no SweepMe! Pro license is active, or all licenses on this computer are in use by another running measurement. | Activate your license key via Tools → Version Manager → menu License. See Licenses. |
| A driver is not shown in SweepMe! 1.6, although it can be used in SweepMe! 1.5 | The entry architecture in the config.ini file of the driver does not include Python 3.14, e.g. architecture = "3.9-64". This is the case if a driver needs a package that is not yet available for Python 3.14. Drivers that do not list the running Python version are not shown.
|
Check the Version Manager for a newer version of the driver. For your own drivers, test them with SweepMe! 1.6 and add 3.14-64 to the entry architecture. See the Migration guide. If you need a driver that is not yet available for SweepMe! 1.6, contact us.
|
| A module is missing after changing to SweepMe! 1.6 | Modules that have been downloaded for SweepMe! 1.5 are built for Python 3.9 and cannot be loaded by SweepMe! 1.6. | Open the Version Manager, press Refresh online versions and download the latest version of the module. |
| A driver or module that you changed in its installation folder is no longer loaded | SweepMe! checks whether an installed driver or module has been modified. A modified version is not loaded, and the debug.log file contains a message that it "has been modified and will not be loaded". | Install the version again or delete it in the Version Manager. To change a driver, right-click the driver version in the Version Manager and select Create custom version. This copies the driver into the CustomDevices folder of the public folder, where you can edit it. |
| A self-written driver or CustomFunction script that worked in SweepMe! 1.5 raises an error in SweepMe! 1.6 | SweepMe! 1.6 is based on Python 3.14 and newer versions of packages such as NumPy and PyVISA. | Adapt the code and the included libraries as described in the Migration guide. |
| SweepMe! has an internet connection, but some modules or drivers cannot be downloaded with a generic error message. | Your company firewall blocks certain downloads. | Reach out to your IT department to allow an exception for SweepMe! downloads. |
| The WebInstaller does not show any version | A firewall or proxy blocks the communication between the WebInstaller and our server. | Log in to your sweep-me.net account and download the full installer from the dashboard, see WebInstaller. |
| An AI assistant cannot connect to SweepMe! | The MCP server is not started in Tools → Interfaces (Pro), or the AI client uses another URL than the one shown there. | See Troubleshooting MCP connections. |
| Other | Other | Report a problem or bug on the SweepMe! support center website. |
Reporting a Bug
To report a problem or a bug, use Help & Info → Report a Bug in SweepMe! or go to https://support.sweep-me.net. Describe your problem or how to reproduce the bug as detailed as possible. Also attach the debug.log file and the sequence file (.seq) or setting file (.set) that can be loaded to reproduce the bug, see Sequences.