|
Troubleshooting
|
|
|
Problem description
|
Cause
|
Resolution
|
|
The simulated camera is not detected by the remote GigE Vision client application
|
The network adapters bound with the simulator and client application have non-matching IP-addresses.
Firewall is enabled. The client and server PCs have a secondary network connection, possibly through the local network Several virtual cameras are connected to the same network adapter, but their IP or MAC addresses are the same. A third-party application is blocking the GigE Vision traffic. |
Make sure that the network adapters on both ends have IP addresses assigned to the same subnet (typically 169.254.x.x). Refer to Network Setup or manufacturer's documentation for details.
Disable the Windows Firewall or any additional third party firewall on the NIC used by the virtual camera. Make sure that your server and client PCs are connected only through a single network path. Assign a unique IP and MAC address to each simulated camera. See Working with multiple cameras for more details. Some network applications such as Dropbox may block an outgoing GigE Vision traffic. Try to disable processes running in the system one by one until you find the one that causes the problem. |
|
Live video from the simulated camera would not start or occasionally freezes.
|
Firewall is enabled.
UDP packet size exceeds the maximum value allowed by your network configuration. The computer/network card/cabling has an intermittent hardware issue. Both GigESim-based server application and client application are running on the same computer, and the client application uses a network filter driver. |
Disable the Windows Firewall or any additional third party firewall on the NIC connected to the camera.
Configure your network adapter for Jumbo frames. If Jumbo option is not available for your NIC, reduce the packet size for the virtual camera down to 1500. Replace the cable or try to run the camera/software on a different system. The filter driver prevents the client application from receiving video packets. Deactivate the filter driver associated with the client application in the properties of the network card used by GigESim. |
|
The video is corrupted (frames are broken into parts, or synchronization is lost). Some video formats and frame rates do not work.
|
UDP packet size is incorrect
|
Configure your network adapter for Jumbo frames. If Jumbo option is not available for your NIC, reduce the packet size for the virtual camera down to 1500.
|
|
The transfer speed between my virtual camera and client application is about 600 Mbps, way below 1 Gbps
|
Network adapter on the server side is not configured for the optimal performance
Network adapter on the server side has a mediocre transmission performance |
Use our Network Setup instructions to configure the network card.
Make sure to use a high-performance network card such as Intel PRO/1000 CT. |
|
I work with multiple virtual cameras, and they get randomly disconnected from the client application.
|
Excessive activity on the network prevents discovery messages from being received in time.
|
Set the Broadcast Channel Timeout in your client application to a larger value.
|
|
I added new features to my virtual camera object, but the client application does not see them.
|
The client application uses an old XML file from an xml cache folder.
|
Use SetDeviceInfo in your code to modify the version of the XML file. As an alternative solution, locate the xml cache folder of your client GigE Vision software and delete an xml file that corresponds to your virtual camera.
|