-
产品中心
计算机视觉硬件工业相机 镜头 机器视觉光源 采集卡 线材 配件 网络和外围设备计算机视觉软件pylon Camera Software Suite VisualApplets 其他软件产品线嵌入式视觉产品线 医疗和生命科学产品线 CoaXPress产品线面阵相机Basler ace 2 Basler ace Basler MED ace Basler boost Basler beat Basler dart Basler pulse Basler scout线阵相机Basler racerBasler racerBasler racer - the right choice镜头固定焦距镜头机器视觉光源Basler相机光源系列
- 选型工具
- 解决方案
- 下载中心
- 品牌中心
- 销售与支持
-
Vision Campus
相机技术Sony IMX CMOS芯片系列型号比较 为什么要对相机进行色彩校准? 专家教您如何为视觉系统找到合适的镜头 适用于嵌入式视觉系统的五大专家级技巧 什么是多光谱成像? CMOS相机比较 图像处理过程中的色彩 处理板 什么是图像处理 图像处理中的3D技术 什么是嵌入式视觉? 为何选择CMOS图像芯片? 什么是ToF (Time-of-Flight)? 什么是成像质量? 相机尺寸 数字相机的工作原理是什么? 芯片技术:CMOS与CCD的对比 实时性 NIR: 即使在弱光条件也可以呈现清晰图像 高灵敏度图像处理相机显示更多收起接口和标准System Setup with CoaXPress 2.0 什么是CoaXPress? 哪一款接口适合嵌入式视觉? 配备GigE 2.0的多相机系统 USB 3.0 – 引领未来的标准化接口 接口是什么? Camera Link 千兆网(GigE) GenICam标准 USB 3.0和USB3 Vision
-
公司概况
关于我们供应商
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.