Skip to content

Troubleshooting

When running a program, an exception is thrown. The exception message is 'BaslerGTC/Basler/GenTL_Producer_for_Basler_blaze_101_camera could not be created.'.

Reason: The GenTL producer for blaze cameras provided by the pylon Supplementary Package for blaze is not found.

Solution: Make sure that the GENICAM_GENTL64_PATH environment variable is set up correctly. The variable must contain the <PYLON_ROOT>/lib/gentlproducer/gtl folder.

You can use the pylon-setup-env.sh script, located in the <PYLON_ROOT>/bin directory. To set up the environment for a pylon installation in /opt/pylon, execute:

source /opt/pylon/bin/pylon-setup-env.sh /opt/pylon

If you want the environment to be persistent, you can add

source /opt/pylon/bin/pylon-setup-env.sh /opt/pylon
to ~/.bashrc

If you do not use this script, you will have to set up your environment as follows:

export GENICAM_GENTL64_PATH=/opt/pylon/lib/gentlproducer/gtl:$GENICAM_GENTL64_PATH

CMake emits lots of warnings.

Reason: Depending on the version of the PCL, the PCL's CMake configuration file causes many warnings.

Solution: For the purpose of building and running the Basler blaze samples, the warnings can usually be ignored.

The amount of warnings can be reduced by passing the -Wno-dev command-line option to CMake.

Display frame rate is low.

Reason: In debug mode, the compiler generates code without optimizations.

Solution: Make sure that the application is built in release mode.

After an application has crashed or has been killed, a device is already connected error message occurs when restarting the application.

Reason: When the application terminates unexpectedly, it can't close the connection to the camera anymore. The camera waits until the GigE Vision heartbeat timeout expires until it accepts a new connection.

Usually, this happens if you're running your application under a debugger and are using pylon 7.0 or below. Later pylon versions automatically close the camera connection on program termination.

Solution:
If you increased the heartbeat timeout, or if you're using pylon 7.0 or below and are running the application under a debugger, you either have to power-cycle the camera or to disconnect the camera from the network for a short while.

Refer to the Debugging C++ Applications and Controlling the GigE Vision Heartbeat or the Debugging .NET Applications and Controlling the GigE Vision Heartbeat sections for more details about how to control the GigE Vision heartbeat timeout.