Troubleshooting

From SweepMe! Wiki
Revision as of 19:37, 19 March 2017 by Felix Kaschura (talk | contribs) (→‎Collecting Information: information about saving debug.log)
Jump to navigation Jump to search

On this page you can find information on where to start if something does not work as desired.

Collecting Information

In the SweepMe! directory, you will find a file called debug.log, as long as SweepMe! is not started in the debug mode. 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.

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 measurement does not start The sequencer is not filled correctly Go to the Sequencer Tab in SweepMe! an put the correct Measurement Classes 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.

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.