Skip to content

Using Basler GigE Cameras in a Wireless LAN#

This topic tells you how to operate a Basler GigE camera in a wireless local area network (WLAN).


Basler recommends using GigE cameras in wired networks.

Configuring the Camera#

Initial Settings#

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. The default camera settings may not be sufficient to establish a stable network connection.

To configure the camera to operate in a WLAN:

  1. Install the pylon Software Suite (Windows or Linux).
  2. Make sure the camera is installed and configured as described in the Hardware Installation (GigE Cameras) topic.
  3. Connect your computer to the WLAN.
  4. Open the pylon Viewer.
  5. 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.
  6. Set the PixelFormat parameter (i.e., the pixel format) to an 8-bit pixel format, e.g., Mono 8.
  7. 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.
  8. Start continuous image acquisition.
  9. If the resulting WLAN connection is unstable, return to step 7 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:

  1. Open the pylon Viewer.
  2. Start continuous image acquisition.
  3. 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.
  4. 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.
  5. 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.