How To enable pylon logging
Using pylon 2.3 and higher: The setup installs a batch file to start the pylon Viewer with logging enabled.
- In the folder where the pylonViewerApp.exe is located (typically C:\Program Files\Basler\pylon 2.3\apps\i386) there is a batch file called StartPylonViewerWithLogging.cmd. Double click this files to start the pylon Viewer with logging enabled. There is no startmenu shortcut for this batch file.
- To log a customer's application, copy the .cmd to their .exe's folder and run: StartPylonViewerWithLogging.cmd myprogram.exe
- By default a logfile named pylonLog.txt is created in your %TEMP% folder and entries are appended to this file.
An easy way to open your %Temp% folder is to press Win+R, enter %TEMP%, and press Enter. This will open an explorer window in your current %TEMP% directory.
If you are using any pylon version before 126.96.36.1999 use these steps to enable logging:
- Copy the attached logging configuration file file to your HDD and remember the location. Starting with pylon 2.3 the setup already installs this logging config file in the pylon installation directory (typically: C:\Program Files\Basler\plyon 2.3\DebugLogging.properties)
- Open System properties -> Advanced -> Environmental Variables
- Add a new System variable: GENICAM_LOG_CONFIG_V2_0=<location were you stored the .properties file>
- Make sure to click on OK when closing the windows boxes.
- (Re-)start the pylon Application
The log file will be created in the temp folder. The filename is: %TEMP%\pylonLog.txt.
Note: With the attached debugLogging.properties file it is no longer required to use Dbgview.exe to capture the logging output.
Note: The logging works for the applications shipped with pylon as well as for custom application using pylon.
Note: It is important to restart the application after setting the environment variable.
Using advanced CameraLink logging when using pylon 2.3 or higher with Camera Link cameras:
Starting with pylon 2.3 pylon adds advanced logging for CL cameras. Due to technical limitations the advanced logging cannot be configured using the batch file as shown above. Here are the steps to enable advanced CL logging:
- Enable standard pylon logging as described above using the evironment variable and the .properties file.
- Activate the Scroll Lock by pressing the ScrLock keyo on your keyboard.
- Start DbgView.exe (can be found http://live.sysinternals.com/Dbgview.exe)
- Start your pylon application.
Advanced logging will output verbose information about baud rate detection / device probing / timeouts etc.
If you turn off ScrLck advanced logging will be disabled.