Troubleshooting

Program does not start, exists unexpectedly or controls do not work

In this case, you must run the program from the command line using:

python -m pyilper

This is how error messages are displayed in the console. There are two types of error messages to distinguish between

• Python errors: A Python error message (traceback) can be recognized by a structured text output in the terminal, which usually begins with the line `Traceback (most recent call last):`. Python provides detailed information about where (file, line number) and what type of error occurred. This error message is usually caused by a programming error in pyILPER or configuration file problems (see below).
• Other errors: Other error messages that can mean all sorts of things usually indicate installation problems or incompatibilities of the Python or Qt software and your operating system.

Configuration file problems

Crashes at the start of the program are often caused by a corrupted configuration file. In this case the configuration file must be deleted. The location of the file is platform dependent:

Platform	Directory
LINUX	$HOME/.config/pyilper
Windows	%HOMEDRIVE%%HOMEPATH%\pyilper_config
Mac OS X	$HOME/Library/Application Support/pyilper
Other	$HOME

The name of the configuration file is pyilpern, where n is the version number of the configuration file. The version number of the file is increased every time if the layout of the configuration file of a new pyILPR version changes. In this case, pyILPER must be configured again.

If the program does not start at all, you should delete the configuration file and check the file permissions of the configuration directory.

You can invoke pyILPER with the --clean option in initializing the configuration file with default values as well.

Main application error messages

Cannot connect to PIL-Box
The application did not succeed in initializing the PIL-Box. Check if the PIL-Box is connected to the correct port and if the baud rate is configured according to the PIL-Box jumper setting. Check also if the correct port is specified in the program configuration.

Cannot create configuration path
The application did not succeed in creating the directory for the configuration file (see above). Check the path and permissions.

Cannot read configuration file>
The application could not read the configuration file. Check the file permissions. If the permissions are correct, purge the file.

Cannot write default configuration
The application did not succeed in creating the configuration file. Check path and permissions.

Cannot write to configuration file>
The application did not succeed in writing to the configuration file. Check path and permissions.

Cannot change to working directory
The application did not succeed in changing the working directory to the configured file path. Check the path and permissions.

Cannot close xxx log file
The application did not succeed in closing the printer or scope log file

Cannot open xxx log file
The application did not succeed in opening the printer or scope log file. Check path and permissions of the working directory.

Cannot write to xxx log file
The application did not succeed in writing to the printer or scope log file. Check file and directory permissions.

PIL-Box disconnected after error (Status line message)
The application was terminated due to a runtime error. These may be caused by various reasons. See additional error information.

File does not contain a LIF type 1 medium with valid layout information. Using default layout.
The LIF image file does not contain a properly initialized header with valid layout information. The default layout is used.

Warning! If the default layout does not match the current medium, data corruption may occur!

Your configuration files are of pyILPER version: XXX that is newer than the version you are running. The program might crash or mishehave. Do you want to continue?
You probably downgraded pyILPER to an older version. The current configuration files might contain data that are not compatible with the running version. To avoid problems, you should reset the configuration files. See the chapter above.