search

magazino / pylon_camera

ROS-Driver for Basler Cameras
BSD 3-Clause "New" or "Revised" License
78 stars 108 forks source link

Feature request: Automatic configuration in case multiple gige cameras are connected #16

Closed marc-up closed 7 years ago

marc-up commented 7 years ago

This affects the applyCamSpecificStartupSettings() method in the pylon_cameragige.hpp. ` cam->GevSCPSPacketSize.SetValue(parameters.mtusize); cam_->GevSCPD.SetValue(parameters.inter_pkgdelay); ` The inter-pkg-delay should be adapted but one has to figure out how this can be done. As far as I know, this depends the image size in bytes and the number of connected cameras. The mtu size might no longer be a required parameter, but can be read out of the network config instead. The number of connected cameras should be a parameter instead. Further documentation can be found here

jonbinney commented 7 years ago

@marceldebout I get a 404 error when I follow the documentation link you posted.

marc-up commented 7 years ago

@jonbinney This is the desired document

But I think this issue can be seen as closed, because the inter-pkg-delay is already provided as a parameter and and can't be calculated directly. It's furthermore recommended to be figured out via trial and error with the usage of the PylonViewerApp. The number of lost frames depends the cabling, the NIC as well as the amount of launched ros-nodes (the communication via the network stack). By increasing the inter-pkg-delay lost frames can be prevented by taking into account a lower maximum framerate. Also the number of cameras triggered in parallel can be configured by adapting the inter-pkg-delay parameter.