Swing Catalyst Support Center

How to configure Point Grey / FLIR GigE camera's with Swing Catalyst

How to setup Point Grey GigE camera's to work with Swing Catalyst.

 

For camera setup please see this article: https://support.swingcatalyst.com/hc/en-us/articles/204945617

 Drivers can be found here: https://www.swingcatalyst.com/drivers

This article covers setting up the IP addresses of both the camera & network card.

Note: Camera support is limited, and camera control is limited to the FlyCapture (Point Grey software), unless you purchase the Swing Catalyst Universal Camera Support.

Supported camera types: GigE, Firewire and USB 2.0 / 3.0 that support the FlyCap2 SDK.

 

Compatible network adapters & configuration:

Please see: https://support.swingcatalyst.com/hc/en-us/articles/205460708-Gigabit-Ethernet-GigE-Vision-camera-network-recommendations

 

Note: Spinnaker SDK is not supported. We only support FlyCapture2 SDK camera's at the time of this article.

Note, important for performance: If you have an Intel network card, please download & install the Intel drivers, as this will give you options to set interrupt moderation rates, which may be unavailable with the Windows drivers.

Setting up your Point Grey / FLIR GigE Camera:

Steps:

  1. Open the Point Grey GigE Configurator application (it can be found in: C:\Program Files\Point Grey Research\FlyCapture2\shortcuts\utilities).

explorer_2017-05-09_12-28-42.png

2. Open up the Point Grey GigE Configurator application.

GigEConfigurator_2017-05-09_13-38-39.png

Please make sure to uncheck DHCP under IP Address Assignment Configuration if you want to use a static IP setup.

Note the IP address configuration.

Our recommendations is to have one dedicated network card, or network interface for each camera. However, with the BlackFly 03S3C-CS model you can use two camera's for each network port with the use of a network switch.

Our recommended IP Setup:

Each camera and Ethernet card (also known as NIC) should be configured with static IP's on different subnets (and a subnet mask).

Example:

Cameras on network card 1:
nic ip: 10.0.1.1
cam ip: 10.0.1.10 ... 10.0.1.20
subnet mask:255.255.255.0

Cameras on network card 2:
nic ip: 10.0.2.1 (different subnet from nic1)
cam ip: 10.0.2.10 ... 10.0.2.20 (different subnet from nic1)
subnet mask: 255.255.255.0

 

Setting the IP address of the camera:

Click on the camera & set the IP address there as well:

Note make sure to set the IP under Persistent IP Configuration, or the IP configuration will not be saved to the camera's memory and ergo lost if the camera looses power.

GigEConfigurator_2017-05-09_13-07-49.png

 

Setting the IP address of the NIC:

Note which Network Adapter the camera is connected to, in the GigE Configurator it will mention specifically which adapter each respective camera is connected to. In our case, it's Ethernet 3 (as displayed in the picture above).

Click on the respective Ethernet adapter listed under Network Adapters.

GigEConfigurator_2017-05-09_12-43-26.png

You should see something similar to the screenshot below.

You can set the IP address & Subnet Mask as described earlier under IP address recommendations and then click on Set IP Address / Subnet. After doing so click on Open Network Connections.

Note: You will need to do this for each network adapter / camera.

GigEConfigurator_2017-05-09_12-40-56.png

Note, setting static IP addresses is not needed but highly recommended as automatic IP configurations can cause trouble with IP address conflicts, e.g the same IP address being used elsewhere. We highly recommend setting up a static setup for all studio installations.

 

Click Test Camera Connection to verify that the connection is working and that you're receiving data from the camera.

GigEConfigurator_2017-05-09_12-35-04.png

 

Configuring the Network Adapter(s) for best performance:

Assuming you now have setup static IP addresses for both the camera(s) and the network card, lets move on to configuring the network adapter.

 

Click the Advanced tab. Note: The configuration is different for each network adapter and depending on the driver, please refer to your network cards documentation for specific information on how to change the specific settings shown below.

rundll32_2017-05-09_12-49-14.png

Ensure Interrupt Moderation is enabled and the Interrupt Moderation Rate is set to Extreme.

If you do not have Extreme as an option set it to High. In some circumstances interrupt moderation can be turned off, but as long as you have a recommended network card these options should be available.

Interrupt moderation being enabled is crucial to lowering CPU usage when handling large amounts of packages, especially on higher FPS camera's.

 

rundll32_2017-05-09_12-47-50.png

 

Enable support for Jumbo Packets (set it to 9014 Bytes).

rundll32_2017-05-09_12-53-02.png

 

Receive Buffers:

It's recommended to set this value as high as it can go. This can help avoid dropped frames when using multiple camera's & or higher resolution GigE camera's.

rundll32_2017-05-09_13-00-48.png

 

Using the camera(s) in Swing Catalyst

Using Point Grey camera's in Swing Catalyst is a matter of setting the camera angle and clicking enable. Click the Play button to make sure the camera works.

All camera configuration needs to be done through Point Grey's FlyCapture Software.

 SwingCatalyst_2017-05-09_13-42-02.png

 

Please see this article on how to setup the camera:

https://support.swingcatalyst.com/hc/en-us/articles/204945617

 

Troubleshooting

 

If you're dropping frames, or having problems with sync with your FLiR / Point Grey camera's please check the packet size under Flycapture2 -> Custom Video modes.

Point_Grey_FlyCap2_2017-10-02_16-46-18.png

 

You can try turning up the packet size from the minimum value to 9000, or down from 9000 depending on your CPU. What works best may vary depending on the computer setup.

Point_Grey_FlyCap2_2017-10-02_16-43-20.png

Remember to go to Advanced Camera Settings, and save the settings to bank 1 as covered by the camera setup article,  https://support.swingcatalyst.com/hc/en-us/articles/204945617

 

For more detailed information please see FLiR / Point Grey's support article on dropped frames: https://eu.ptgrey.com/tan/10899

 

 

Have more questions? Submit a request

Comments

Powered by Zendesk