Swing Catalyst + Foresight: Avoiding IP Conflicts (Cameras vs Launch Monitor)

This guide prevents IP conflicts between Swing Catalyst camera networks and your Foresight launch monitor. We don’t configure Swing Catalyst or cameras.

Scope & responsibility

• We do not support or configure Swing Catalyst or cameras. Follow Swing Catalyst/vendor docs for camera setup.

• Our goal here is IP hygiene so the launch monitor doesn’t collide with the camera network.

Connection recommendations

• Best (recommended): connect the Foresight launch monitor by USB-C to the PC (no IP, no conflicts).

• If Ethernet is required:

  • Use a different NIC (or VLAN) than the camera NIC.

  • Put the launch monitor on a different subnet than the cameras.

  • Do not plug the launch monitor into the camera-only switch unless that switch/VLAN is isolated for it.

Quick verification (before/after changes)

• Run ipconfig and confirm:

  • Camera NIC (example): 192.168.100.x / 255.255.255.0 (Gateway blank).

  • Launch-monitor NIC (example): 192.168.200.x / 255.255.255.0 (separate range).

• Open Swing Catalyst and your Foresight software; ensure cameras are discovered and the Foresight trigger records a test swing.

IP Address Configuration (The link takes you to the Swing Catalyst Support Page for more information)

We recommend using a static IP setup on both the camera and network adapter to ensure optimal stability.

Before changing the IP addresses on each network adapter, set the IP address on the camera first. Make sure to save the changes to the camera, and then make the changes to the network adapter. 

1. Download and Install the MVS Software (If not installed)
2. Launch MVS Software to determine what ethernet port cameras are connected to.
   • (As per the picture below camera 1 is connected to "Ethernet 4"):

3. Set Network IP Address in Windows
   • The MVS Software will be able to determine which Ethernet # the camera(s) is/are connected to. For example, if the camera is connected to Ethernet 2, then you must change the IP address by going to the Control Panel and in the search bar typing “View Network connection":

4. Right-click on the Ethernet adapter you want to change the IP address on. Then click on the IPv4 to highlight it:

5. Click on Properties (highlighted yellow in the above screenshot) and change the Static IP as shown below. If there is more than 1 Camera, repeat the above process and use the next Network IP (10.0.2.1, etc...). The Subnet mask stays the same 255.255.255.0:

6. Set Camera IP Address
   • Right-click the camera and select “Modify IP”, then set the values as listed below:
     • Camera 1 IP: 10.0.1.10 - Default Gateway: 10.0.1.1
     • Camera 2 IP: 10.0.2.10 - Default Gateway: 10.0.2.1 (If applicable)

If the IP address is not saving after restart of the PC disconnect/unplug the camera(s) then add the IP address again. Reconnect the camera(s) and restart the PC. Verify the IP address saved.

FAQs

Cameras disappeared after I connected the launch monitor via Ethernet.

• The launch monitor likely joined the camera subnet. Move it to USB or a different NIC/subnet and retest.

Should the camera NIC have a gateway?

• No. Leave Gateway blank on the camera NIC to keep the camera LAN isolated and predictable.

Can I keep cameras and the launch monitor on the same NIC/switch?

• It can work but is fragile. If you must, use separate IP ranges/VLANs and watch for duplicate addresses.

Trigger isn’t firing in Swing Catalyst.

• Verify the Foresight trigger is enabled in Swing Catalyst and the launch monitor is connected/reading shots. USB often simplifies this.