|
Troubleshooting
|
|
|
Problem description
|
Cause
|
Resolution
|
|
The camera is not recognized by ActiveGige. "No Give Vision camera found" message appears in the control window.
|
The camera and network adapter are assigned non-matching IP-addresses.
Firewall is enabled. A non-compatible system driver is used with the network adapter The camera is not GigE Vision™ compliant. |
Make sure that the camera and corresponding network adapter 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 connected to the camera. ActiveGige will not work with "high-performance" drivers provided by certain camera manufacturers. Make sure the manucaturer's default driver is installed for your networkd adapter. ActiveGige only works with GigE Vision™ compliant cameras. Non-compliant Ethernet cameras (without GigE Vision™ logo) will not be recognized by ActiveGige. Use the manufacturer's provided software. |
|
Live video 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. |
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 in ActiveGige down to 1500. Replace the cable or try to run the camera/software on a different system. |
|
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
|
See the solution above.
|
|
When I select certain Formats, I am getting a split or scrambled video
|
Some cameras offer manufacturer-defined formats not compatible with GigE Vision specifications
|
Use one of the standard formats listed in the Format chapter.
|
|
I am getting a message about mismatching camera's and network card IP addresses even though they match each other.
|
You are using a camera that responds to the discovery message in a non-standard way (for example, Toshiba Teli and Hitachi cameras)
|
Run the IP Configuration utility, go to the GigE tab and select "Use Multiple sockets".
As an alternative, you can try to change the order of your network cards in the system by going to Network Connections->Advanced->Advanced Settings->Adapters. |
|
Problem description
|
Cause
|
Resolution
|
|
I work with multiple cameras, and they get radnomly disconnected from ActiveGige.
|
Excessive activity on the network prevents discovery messages from being received in time.
|
Run the IP Configuration utility and set the Broadcast Channel Timeout to a larger value. If you do not expect the cameras to be plugged/unplugged on the fly, set the Broadcast Channel Period to 1000000.
|
|
When I try to compile sample projects from their default directories in C:\Program Files, I get an error message "Could not create an output directory"
|
You do not have write permissions due to User Account Control (UAC).
|
Copy the Samples folder from C:\Program Files\ActiveGige\ to one of your user directories (e.g. Desktop) and open sample projects from there.
Alternatively, ask your system administrator to provide you with writing permissions for the ActiveGige folder. |
|
VB.NET and C# sample applications do not work.
|
.NET framework is not installed on the system
|
Install the latest .NET framework from Microsoft:
http://msdn.microsoft.com/netframework/default.aspx |
|
When I run a live video application from within Visual Studio.NET, everything freezes.
|
Live video is active in the Design mode. Visual Studio.NET doesn't close the designer while starting the application.
|
ActiveGige cannot run two instances of live video acquired from the same camera. Make sure to close the design view before running your application. The best way to avoid this problem is not to use live display in the design mode except for testing purposes. You can initiate acquisition in your code by setting the Acquire property to true.
|
|
I am trying to do real-time image processing in .NET, and I experience a significant drop in the frame rate.
|
VB.NET and C# have performance issues when working with large arrays.
FrameAcquired event has an overhead that might affect the performance |
For performance boost, use unsafe code and pointers to directly access ActiveGige image buffer. A pointer to the image buffer is provided by GetImagePointer.
For VB.NET, C# and C++ applications use FrameAcquiredX event. |
|
AVI files are not recorded in real-time, many frames are being dropped.
|
Your system does not provide enough throughput or CPU power to keep up with the camera frame rate
|
Switch to a lower resolution mode or reduce the frame rate. If you are using a Bayer camera, consider recording the monochrome video instead of color one. Alternatively, upgrade your system to a faster hard drive and/or CPU.
|
|
Problem description
|
Cause
|
Resolution
| |||||||||||||||||||||
|
ActiveGige installation fails with the following error: "ActiveGige.dll failed to register, HRESULT -2147024770"
|
Runtimes components of Visual C++ 2005 are not installed on your system
|
Install Microsoft's VC++ 2005 Redistributable Package, then run ActiveGige installation again.
For the 64-bit OS you may also need to install VC++ 2005 Redistributable Package 64-bit | |||||||||||||||||||||
|
ActiveGige installation fails with the following error: "ActiveGige.dll failed to register, HRESULT -2147220473"
|
This error is usually caused by a corrupted registration of atl.dll system file.
|
1. Locate atl.dll, generally found in "C:\WINNT\system32" or "C:\WINDOWS\system32".
2. Open the command-line prompt
5. Repeat ActiveGige installation. |