Advanced Tracing of GigE Problems (Error c2000001)
In some rare cases while using GigE cameras, you might encounter errors thrown from the Microsoft Socket Library that do not give an exact indication of the origin of the problem
For example:
PylonC error #c2000001 'Failed to execute command for node.' <-1040187391>
Function 'GenApiCommandExecute' failed in source file
'<ROOT>\Pylon\PylonC\PylonC\GenApiC.cpp'
line #1935 Caused by an exception thrown from source file
'<ROOT>\Pylon\PylonTL_GigE\PylonGigE\GxPort.cpp'
line #87.
Failed to read memory at 0x40024, 0x4 bytes. The access to a socket was forbidden due to the socket's access rights.
Since similar error messages are not thrown from pylon, they cannot be tracked down precisely by any pylon logging mechanism.
Hence, one should use a low level GxApi Tracing in order to gather more information about a given problem.
To do that one may use the files attached to this article.
Usage:
- Store both files to an arbitrary writable folder
- run the "trace.cmd" file by double-clicking on it
- run your pylon-based application or run the pylon actions you wanted to until the problem is reproduced.
- Once you get the given error message, simply press any key with focus to the "trace.cmd" window in order to stop logging.
- Now you will find a file called "pylonLog.etl" in the folder where the files were stored.
This file, together with the exact pylon version used, should be provided to Basler AG support for further investigations.
Note: With pylon 5.1 the GxApi file was changed causing the tracing function to stop working properly. In order to fix this immediately please replace the gxapi_v11.dll in C:\Program Files\Basler\pylon 5\Runtime\x64 with the one included attached to the Article. The fixed GxApi is available for x64 systems only. It is recommended to save a copy of the old gxapi_v11.dll. The tracing function is fixed with the pylon 6 release.
