Troubleshooting
On this page you can find information on where to start if something does not work as desired.
Collecting Information
In the SweepMe! public directory (Open via File -> Open Folder -> Public), you will find a file called debug.log. 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. Please note: This file may be empty if SweepMe! is still running. So close SweepMe! before accessing the file.
Alternatively, you can open the "Debug Console" (key "F2") in order to see debug messages.
Common Problems
| Problem | Reason | Solution |
|---|---|---|
| SweepMe! does not start or crashes during startup | SweepMe! installation is broken | Go to https://sweep-me.net/download and download and install SweepMe! again. |
| A defective component leads to a crash | Delete all Device Classes in the DeviceClass folder, that have been provided by third parties. | |
| The problem occurs only after a Windows Update or on a computer with a new Windows Version | Right click on SweepMe!.exe and click on Properties, select the Compatibility tab, and choose Windows 8 or Windows 7 to run SweepMe! in this compatibility mode or try different settings. | |
| 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 charakters 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 charakters. | |
| The measurement does not start | The sequencer is not filled correctly | Go to the Sequencer Tab in SweepMe! an put the correct Modules there. Also read about the Sequencer for complex measurements. |
| One or more devices are not configured correctly | Go to the device configuration tab of every device you use in the sequencer and check if you selected the correct device, port and parameters. | |
| One or more of the used Device Classes are broken | Run the device-manager.exe and check if updates for the device class are available. You can also go to https://sweep-me.net/devices.php and check the information about your device. | |
| Other | Other | Report a Problem or Bug on the SweepMe! support center website. |
Special problems
Widgets change position after loading a setting
Some of you reported that Widgets are somtimes not at their expected place after reloading a setting.
We now figured out that this problem is related to how our GUI framework (Qt5) is storing the state of the Dashboard.
It can happen that information about formerly used Widgets will remain in the state information that are stored to the settings file. After loading such a setting and adding Widgets that have the same name like these formerly used ones, there will be a confusion and the new Widget might take over the information of the formerly used Widget.
After reloading your setting, you might then experience that your widget is at the wrong position.
At the moment, we cannot fix this bug because Qt does not offer adequate functions to correctly refresh the state information of the Dashboard. We searched through all the Qt forums and found many other people reporting the same problem. All are waiting for fix and apply workarounds in the meantime.
If you experience, the same problem, you should be able to fix your setting with the following procedure:
- load the setting
- put the jumping Widget at the right position again
- save your setting again
- loading the setting, it should be fine now
Once a setting is loaded correctly, you can expect that a Widget will not jump anymore.
We are sorry about this inconvenience and already took first actions:
- All example settings are cleaned up and contain no more information about formerly used Widgets
- If you use "New setting...", a clean setting will be loaded that kicks out all information about formerly used Widgets.
We are further working on that problem by testing different strategies now. However, as these strategies have to be thoroughly tested, it will take some time to release a proper solution.
Reporting a Bug
To report a problem or a bug, 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 a settings file (see Loading and Saving Settings for instructions to create a settings file) that can be loaded to reproduce the bug.