Using Basler GigE Cameras in a Wireless LAN
This topics tells you how to operate a Basler GigE camera
in a wireless local area network (WLAN).
Prerequisites
Configuring the Camera
If you want to operate a Basler camera in a WLAN, you may have to change
the network-related parameters of the camera.
This is because the bandwidth available in a WLAN may be limited, and
the default camera settings may not be sufficient to establish a stable
network connection.
To configure the camera to operate in a WLAN:
- Open the pylon Viewer.
- Set the GevSCPSPacketSize
parameter (i.e., the packet
size) to 1500.
Tip: Use the search feature
in the pylon Viewer to quickly find a parameter setting.
- Set the PixelFormat
parameter (i.e., the pixel format)
to an 8-bit pixel format, e.g., Mono 8.
- Set the GevSCPD
parameter (i.e., the inter-packet
delay) to a high value.
This decreases the current
device throughput (GevSCDCT
parameter).
The minimum inter-packet delay and the maximum current device throughput
depend on the quality of the WLAN connection. A higher connection
quality will allow a lower inter-packet delay.
- Start continuous image acquisition.
- If the resulting WLAN connection is unstable, return to step 4
and increase the inter-packet delay further.
Optimizing Settings
After the WLAN connection has been established,
you can optimize the parameter settings for most efficient use of the
available bandwidth.
To optimize the parameter settings:
- Open the pylon Viewer.
- Start continuous image acquisition.
- Check the Statistic_Failed_Buffer_Count
and the Statistic_Failed_Packet_Count
parameters.
Tip: Use the search feature
in the pylon Viewer to quickly find a parameter setting.
The failed
buffer count indicates the number of incompletely grabbed buffers.
The failed
packet count indicates the number of packets that have been reported
as "failed" by the camera.
- Decrease the GevSCPD
parameter (i.e., the inter-packet
delay) to a value just before the failed packet count or the failed
buffer count start increasing.
- Make a note of the current value of the DeviceLinkCurrentThroughput
parameter.
This helps you to find the optimum inter-packet delay again when the
payload size changes. See note below.
Any parameter settings you make will only deliver good results for
the current payload size, i.e., the current amount of data per image
and the current frame rate. The payload size depends on various factors,
e.g., the size of the image ROI and the
pixel format. If the payload size changes,
you must readjust the inter-packet delay until the DeviceLinkCurrentThroughput
parameter value is the same as the one noted in step 5.