Troubleshooting
Top  Previous 

Below is the list of the most frequently encountered issues and remedies for their resolutions:

Problem description


Cause
Resolution
The camera is not recognized by ActiveUSB. "No USB3 Vision camera found" message appears in the control window.
The camera is not receiving power.




USB3 Vision Camera Driver
is not installed for the camera.





The camera is not USB3 Vision™ compliant.


This is a typical issue for USB3 hubs that do not provide power to external devices. Use powered USB3 hubs or connect your camera directly to a USB3 port on your computer.

ActiveUSB will not work with a system driver provided by your camera manufacturer. Refer to Driver Setup for the USB3 Vision driver installation procedure.


ActiveUSB
only works with USB3 Vision™ compliant cameras. Non-compliant USB3 cameras (without USB3 Vision™ logo) will not be recognized by ActiveUSB. Use the manufacturer's provided software.
Live video would not start or occasionally freezes.
The camera and USB3 adapter have a compatibility problem.



The computer/USB3 adapter/cabling has an intermittent hardware issue.
Some USB3 Vision boards/chipsets are known not to perform well with certain models of USB3 cameras. Replace your board with a board recommended by your camera manufacturer.

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.
The camera and USB3 board have a compatibility problem.

The processor has an extensive latency in the C3 power state transition.

See the solution above.


This problem is common for notebook computers. To correct the latency setting, run C3State.reg file located in the Driver folder. Restart the system for the changes to take effect.
When I select certain Formats, I am getting a split or scrambled video
Some cameras offer manufacturer-defined formats not compatible with USB3 Vision specifications
Use one of the standard formats listed in the Format chapter.

Problem description


Cause
Resolution
When switching to certain video modes, I get blank screen.
Some cameras require turning the acquisition off while switching between video modes.
Turn the acquisition off by setting the Acquire property to off, then select the desired video mode and turn the acquisition on.
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 the right permissions due to User Account Control (UAC).
Copy the Samples folder from C:\Program Files\ActiveUSB\ 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 ActiveUSB 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 the Visual Studio, the application shows "Camera in use by another process" message.
Visual Studio does not close the design view while starting the application.
The design window of the IDE maintans control over the camera blocking your application from initiating the acquisition. Make sure to close the design view before running your application.


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 ActiveUSB 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 (such as an SSD) and/or faster CPU.

Problem description
Cause
Resolution


ActiveUSB installation fails with the following error: "ActiveUSB.dll failed to register, HRESULT -2147024770"
Runtimes components of Visual C++ 8.0 are not installed on your system
Install Microsoft's VC80 Redistributable Package, then run ActiveUSB installation again.

For the 64-bit OS you may also need to install VC80 Redistributable Package 64-bit


ActiveUSB installation fails with the following error: "ActiveUSB.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
·o Start Menu/Run  
·o type "cmd"  
·o press "ENTER"  
3. Using the atl.dll filename and path, call regsvr32, i.e. at the command-line prompt, type:
·o regsvr32 "C:\WINNT\system32\atl.dll"  
·o press "ENTER"  
4. You should see a regsvr32 window, confirming success: Close it.
5. Repeat ActiveUSB installation.