-
产品中心
计算机视觉硬件工业相机 镜头 机器视觉光源 采集卡 线材 配件 网络和外围设备计算机视觉软件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
- 公司概况
What to do if you got the error message "SocketBufferSize not valid!" in pylon4linux on Linux?
If you are trying to run a GigE camera on a Linux system and get the following error message while trying to grab images, you may want to try the solution described below:
"Failed to allocate resources
Failed to set stream grabber property. SocketBufferSize not valid!
../../../../pylonsrc/Pylon/PylonTL_GigE/PylonGigE/GxStream.cpp : 1178"
At the start of image acquisition pylon sets the SocketBufferSize to the maximum supported by the given OS value.
This value can be also changed in the StreamGrabber Nodemap every time, of course.
In the initialization stage pylon checks the maximum supported value for SocketBufferSize, which is reported by the system.
This value can be also retrieved with the command:
sysctl net.core.rmem_max
This value will then be used as the maximum value for the SocketBufferSize in the Feature Properties in pylon viewer (see attached screenshot).
Pay attention though, "sysctl" returns values in [Bytes], but the Nodemap works with [KBytes].
Hence, the reported maximum value in pylon viewer should have the following value:
"sysctl net.core.rmem_max" / 1024.
If pylon should fail at reading out the value for the SocketBufferSize for any reason, it will always use a default value of 2048 [KBytes].
However, under circumstances this value may be too big and hence not supported by the given system. This will in turn result in the mentioned error message!
Hence, if you run in this error message, you should check the current and maximum value for SocketBufferSize reported in the Feature Properties in pylon viewer first (see the attached screenshot).

Then open a console and execute "sysctl net.core.rmem_max". Now divide the reported value by 1024 and compare it with the maximum value reported in pylon viewer.
If these two values should be different, this means that pylon has failed in reading out the maximum system value, i.e. "net.core.rmem_max".
In this case you should manually set the SocketBufferSize to a smaller, secure value, e.g. 64, and try to grab images then.
Pay attention though, the value for the SocketBufferSize should be as big as possible in order not to degrade the performance.