Drivers Paradigm USB Devices

To verify that your driver is working, you should see a difference in the following pictures after plugging the CH340 to a USB port. To check that the CH340 enumerates to a COM port, you can open the device manager. You can click the Start or ⊞ (Windows) button and type 'device manager to quickly search for the application. Locate the Unknown Device. RELATED: How to Use the Windows Device Manager for Troubleshooting You’ll see information about Unknown Devices in the Device Manager.To open it on Windows 10, 8.1, or 8, right-click in the bottom-left corner of the screen or press Windows Key + X and select Device Manager.

First, start the PC client. You’ll find a shortcut to DroidCam Client under Start Menu and on your Desktop.

If there is a separate admin account on the system, these shortcuts will be created on that users Desktop/Start Menu during installation.

Connect via WiFi


1. Turn on WiFi on your phone and connect to your home network as you normally would.

2. Start the phone app. The app will show Wifi IP & Port information.
If the IP is all zeros (0.0.0.0) – you are not properly connected to a WiFi network.

3. On the PC client, make sure the connection method is “WiFi/LAN”. Enter the IP and Port as displayed on the phone. Click [start].

4. The phone app should start showing the camera output. The PC client should start updating the “webcam” output, you can check in Skype/Zoom/etc. Find ‘video input’ settings in the options/preferences of these programs.

If the connection fails, try:
– Closing and re-opening the app
– Toggling the Wifi on phone and/or laptop
– Restarting your Wifi router (unplug from power, wait a few seconds, and plug it back in)
– Changing the connection port number in the app & client (eg. 4748 …)

Connect via USB (Android)

USBFor USB connections, you need to: a. enable USB Debugging on the phone, b. install drivers for your phone on the computer.

1. First, make sure “USB Debugging” is enabled on your phone. Its located in the phones Settings, under Developer Options.

On most phones the Developer Options screen is hidden by default. To unlock it, open the phones Settings, go to About Phone and search for Build number. Tap Build Number seven times to unlock Developer options.

If you’re having trouble, try the instruction here: https://www.howtogeek.com/129728/how-to-access-the-developer-options-menu-and-enable-usb-debugging-on-android-4.2/

Once unlocked, search for USB Debugging and turn it On.

2. With “USB Debugging” turned on, connect your device to the computer via USB.

In the DroidCam PC client, pick the USB connection option and click the refresh button. The client will try to detect connected devices. If the client detects your phone, you’ll likely get a dialog on the phone asking Allow USB Debugging, you need to tap OK. You can also skip the next step.

3. If the device is not detected, you need to install drivers for it as an additional step.

If you have a Google Nexus/Pixel, or a OnePlus, get the Google USB drivers:
https://developer.android.com/studio/run/win-usb.

Samsung USB drivers:
https://developer.samsung.com/mobile/android-usb-driver.html

LG Mobile Drivers:
https://www.lg.com/us/support/help-library/lg-mobile-drivers-and-software-CT10000027-20150179827560.

For other brands, this page provides links to most manufacturers websites: http://developer.android.com/tools/extras/oem-usb.html#Drivers.

You can also do a web search, ADB Drivers for ____.
Eg: ADB Drivers for HTC.

After the drivers are installed, re-connect the device to the computer and try again to refresh the USB list on the DroidCam PC Client. On the phone you may get a dialog asking Allow USB Debugging, you need to tap OK.

4. Once the client detects the phone, click Start to establish a connection just like you would over WiFi.

If you get “connection reset”, “connect lost”, “error receiving video headers” errors:
(1) On the phone, make sure the DroidCam app is open and ready.
(2) On the phone, pull down the notification area and open “USB Options”. Try picking the ‘PTP’ (Picture Transfer), or ‘Camera’, or just ‘Charging’ mode.

If the connection is still failing, try
(1) If you skipped the driver installation step above, try installing the drivers for your phone manually. Sometimes Windows auto-installs incorrect ones.
(2) Try changing the ‘DroidCam Port’ setting in the app, and on the client. Use, for example, 4848, 5050, 5151, etc.
(3) Try this alternate USB setup tool. The tool will detect and setup local port forwarding against all connected devices. If it works, you can replace the adb folder under Program Files x86 > DroidCam with the one in this download.

Connect via USB (iOS)

USB connections for the iOS app require iTunes to be installed and that it detects your iDevice when you plug it in.

Click the refresh button on the DroidCam Client ‘USB’ tab and any available iOS devices will be listed as a string of random characters, this is the unique ID of the device. Click Start to establish a connection just like you would over WiFi.

Notes:
– Make sure you have at least v6.2.3 of the Windows client which includes iOS support.

– The Windows Store version of iTunes may not have the necessary components for this to work. If you have the Windows Store version of iTunes and the DroidCam client is not detecting any devices, try re-installing iTunes manually by following the “Windows” link, or see this help article by Apple.

Connect with internet browsers (Android)



To use the “IP Cam” feature you normally don’t need to install any extra software on the computer.

1. Turn on WiFi on your phone and connect to a WiFi network as you normally would.

2. The app will show Wifi network name, and IP & Port information. If the IP is all zeros (0.0.0.0) – you are not properly connected to a network.

3. Open your internet browser (Firefox, Chrome, etc), and enter http://ip:port into the address bar (replace these with the actual ip and port values from the app). This should open a web page with the camera feed embedded inside.

Tip: Use an MJPEG viewer app or program to access the raw feed via http://ip:port/video (eg. on a Tablet, another smartphone, or a media player such as VLC). You can also specify resolution in the URL, and use the word “force” if you’d like to override any existing connections: http://ip:port/video.force?1280×720.
This can be handy is you want to connect many devices to eg. OBS Studio. If you’d like to connect over USB using the http method, use this USB setup tool which will create local port mappings to all connected phones via adb and the special 127.0.0.1 IP address.

WiFi Hotspots, USB Tethering, USB-C Ethernet

Both USB Tethering and WiFi Hotspot connections with your phone can work with DroidCam. Some phones also work with USB-C to Ethernet wired connections.

On Android, you’ll need to find the IP address of the phone and enter that into the WiFi tab of the DroidCam client.
The easiest way is to open the phones Settings, scroll down to “System” or “About”, and look for the ‘Network’ section.

USB

On iOS, for USB Tethering you can use standard USB connection option in the DroidCam client (see above).

For WiFi hotspots, try these standard IPs 172.20.10.1, 10.0.0.1, 192.168.0.1. Alternatively, on your PC open the Start menu and launch the Command Prompt program. Enter ipconfig command, and look for ‘router’ or ‘gateway’ address, and use that as the phone IP.

Drivers & Downloads. Inspiron, Latitude, or other Dell product, driver updates keep your device running at top performance. Step 1: Identify your product above. Step 2: Run the detect drivers scan to see available updates. Step 3: Choose which driver updates to install. Drivers and Downloads FAQs. Emsense Port Devices Driver download Download drivers to communicate with NI products or third-party instruments. Download drivers to communicate with NI products or third-party instruments. Toggle navigation. Provides support for NI data acquisition and signal conditioning devices. Provides support for Ethernet, GPIB, serial, USB, and other types of instruments. Global Nav Open Menu Global Nav Close Menu; Apple; Shopping Bag +. Select Update Driver. If Windows doesn't find a new driver, you can try looking for one on the device manufacturer's website and follow their instructions. Reinstall the device driver. In the search box on the taskbar, enter device manager, then select Device Manager. Right-click (or press and hold) the name of the device, and select Uninstall.

WiFi Server Mode (DroidCamX only)

Instead of connecting to the phone app from the PC client, DroidCamX can connect to PC client(s) from the phone.

1. Use the “WiFi Server” option on the PC client. Click [Start] to wait for a connection.

3. Open DroidCamX on your phone, use the options menu (⋮) and choose “Connect to Server”. You will need the computers local IP address (usually 192.168…) – look in your network settings or open a Command Prompt and type in ipconfig.

Back to Home Page How to switch to 720p

Drivers Paradigm Usb Devices Pc Camera

  • August 22, 2019 2.9.8

    Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.

    Version

    2.9.8

    Released

    August 22, 2019

    Type

    ZIP

    Filesize

    3MB

    Requirements

    • Intel Core i3 or similar, 2 GB RAM
    • USB 3.0 controller
    • Graphics card with 24 or 32 bit
    • Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit)
    • DirectX 9.0c or higher

    Changelog

    1. Added several internal interfaces for particular sensors (J003).
  • January 25, 2019 2.9.6

    Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.

    Version

    2.9.6

    Released

    January 25, 2019

    Type

    ZIP

    Filesize

    3MB

    Requirements

    • Intel Core i3 or similar, 2 GB RAM
    • USB 3.0 controller
    • Graphics card with 24 or 32 bit
    • Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit)
    • DirectX 9.0c or higher

    Changelog

    1. Added missing Tonemapping Auto property.
  • May 4, 2018 2.9.5

    Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.

    Version

    2.9.5

    Released

    May 4, 2018

    Type

    ZIP

    Filesize

    3MB

    Requirements

    • Intel Core i3 or similar, 2 GB RAM
    • USB 3.0 controller
    • Graphics card with 24 or 32 bit
    • Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit)
    • DirectX 9.0c or higher

    Changelog

    1. Enabled tonemapping for 8bit video formats, e.g. Y800, RGB24 and RGB32.
  • November 21, 2017 2.9.4

    Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.

    Version

    2.9.4

    Released

    November 21, 2017

    Type

    ZIP

    Filesize

    3.2MB

    Requirements

    • Intel Core i3 or similar, 2 GB RAM
    • USB 3.0 or USB 2.0 controller (depends upon camera model)
    • Graphics card with 24 or 32 bit
    • Windows XP, Windows Vista, Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit)
    • DirectX 9.0c or higher

    Changelog

    1. Repaired not working J003 mono sensor pattern fix on particular video formats.
    2. This driver version is the last that works in Windows XP.
  • January 9, 2017 2.9.3

    Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.

    Version

    2.9.3

    Released

    January 9, 2017

    Type

    ZIP

    Filesize

    3.2MB

    Requirements

    • Intel Core i3 or similar, 2 GB RAM
    • USB 3.0 or USB 2.0 controller (depends upon camera model)
    • Graphics card with 24 or 32 bit
    • Windows XP, Windows Vista, Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit)
    • DirectX 9.0c or higher

    Changelog

    1. Added a pattern fix for J003 mono sensors.
  • January 9, 2017 2.9.1

    Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.

    Version

    2.9.1

    Released

    January 9, 2017

    Type

    ZIP

    Filesize

    3.2MB

    Requirements

    • Intel Core i3 or similar, 2 GB RAM
    • USB 3.0 or USB 2.0 controller (depends upon camera model)
    • Graphics card with 24 or 32 bit
    • Windows XP, Windows Vista, Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit)
    • DirectX 9.0c or higher

    Changelog

    1. Fixed the driver signature Code 52 error on new Windows 10 v1607 systems.
  • January 15, 2016 2.8.9

    Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.

    Version

    2.8.9

    Released

    January 15, 2016

    Type

    ZIP

    Filesize

    2.3MB

    Requirements

    • Intel Core i3 or similar, 2 GB RAM
    • USB 3.0 or USB 2.0 controller (depends upon camera model)
    • Graphics card with 24 or 32 bit
    • Windows XP, Windows Vista, Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit)
    • DirectX 9.0c or higher

    Changelog

    1. Changed certificates so that the driver can also be installed in Vista.
  • November 9, 2015 2.8.7

    Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.

    Version

    2.8.7

    Released

    November 9, 2015

    Type

    ZIP

    Filesize

    2.3MB

    Requirements

    • Intel Core i3 or similar, 2 GB RAM
    • USB 3.0 or USB 2.0 controller (depends upon camera model)
    • Graphics card with 24 or 32 bit
    • Windows XP, Windows Vista, Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit)
    • DirectX 9.0c or higher

    Changelog

    1. Fixed an error which can appear when using sharpness on older CPUs.
  • October 20, 2015 2.8.5

    Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.

    Version

    2.8.5

    Released

    October 20, 2015

    Type

    ZIP

    Filesize

    2.3MB

    Requirements

    • Intel Core i3 or similar, 2 GB RAM
    • USB 3.0 or USB 2.0 controller (depends upon camera model)
    • Graphics card with 24 or 32 bit
    • Windows XP, Windows Vista, Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit)
    • DirectX 9.0c or higher

    Changelog

    1. Fixed a bug which can appear on LivePause call.
  • July 15, 2015 2.8.0

    Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.

    Version

    2.8.0

    Released

    July 15, 2015

    Type

    ZIP

    Filesize

    2.4MB

    Requirements

    • Intel Core i3 or similar, 2 GB RAM
    • USB 3.0 or USB 2.0 controller (depends upon camera model)
    • Graphics card with 24 or 32 bit
    • Windows XP, Windows Vista, Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit)
    • DirectX 9.0c or higher

    Changelog

    1. Support of DFK ECU010-L34 with serial number property.
    2. Added tone mapping.
  • February 17, 2015 2.7.33

    Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.

    Version

    2.7.33

    Released

    February 17, 2015

    Type

    ZIP

    Filesize

    2.4MB

    Requirements

    • Intel Core i3 or similar, 2 GB RAM
    • USB 3.0 or USB 2.0 controller (depends upon camera model)
    • Graphics card with 24 or 32 bit
    • Windows XP, Windows Vista, Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit)
    • DirectX 9.0c or higher

    Changelog

    1. The Auto Focus Onepush Running flag now resets correctly after the auto focus has finished.
  • February 5, 2015 2.7.32

    Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.

    Version

    2.7.32

    Released

    February 5, 2015

    Type

    ZIP

    Filesize

    2.4MB

    Requirements

    • Intel Core i3 or similar, 2 GB RAM
    • USB 3.0 or USB 2.0 controller (depends upon camera model)
    • Graphics card with 24 or 32 bit
    • Windows XP, Windows Vista, Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit)
    • DirectX 9.0c or higher

    Changelog

    1. Video format MJPG (2592x1944) of DFK AFU050-L34 camera can now be used.
  • January 14, 2015 2.7.31

    Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.

    Version

    2.7.31

    Released

    January 14, 2015

    Type

    ZIP

    Filesize

    2.3MB

    Requirements

    • Intel Core i3 or similar, 2 GB RAM
    • USB 3.0 or USB 2.0 controller (depends upon camera model)
    • Graphics card with 24 or 32 bit
    • Windows XP, Windows Vista, Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit)
    • DirectX 9.0c or higher

    Changelog

    1. Support for IMX236 based cameras.
    2. Support for RGB64 color formats.
    3. Several performance improvements.
  • June 6, 2014 2.7.9.1152

    Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.

    Version

    2.7.9.1152

    Released

    June 6, 2014

    Type

    ZIP

    Filesize

    2.1MB

    Requirements

    • Intel Core i3 or similar, 2 GB RAM
    • USB 3.0 or USB 2.0 controller (depends upon camera model)
    • Graphics card with 24 or 32 bit
    • Windows XP, Windows Vista, Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit)
    • DirectX 9.0c or higher

    Changelog

    1. Added new properties: Brightness, sharpness, de-noise, saturation, hue and contrast.
    2. Added new property: Highlight reduction.
    3. Added new property: White balance temperature controls.
    4. Pixelfix for Y16 cameras now works as expected.
    5. VideoControl_ExternalTrigger (DirectShow property) can now be set as expected.
  • January 1, 2014 2.6.5.1014

    Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.

    Version

    2.6.5.1014

    Released

    January 1, 2014

    Type

    ZIP

    Filesize

    1.9MB

    Requirements

    • Intel Pentium IV or similar, 2 GB RAM
    • USB 3.0 or USB 2.0 controller (depends upon camera model)
    • Graphics card with 24 or 32 bit
    • Windows XP, Windows Vista, Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit)
    • DirectX 9.0c or higher

    Changelog

    1. Fixed missing auto-gain for DFK AFU130.
    2. Fixed focus when start value is out of auto_focus_range.
    3. Fixed problem with AUTOFOCUS_ROI_RIGHT: minimum possibly wrong.
    4. Fixed auto focus ROI not working for 21*UC cameras.
    5. Fixed crash on load/connect with certain cameras 22/72xUC.
    6. Fixed previous exposure settings not being loaded on reconnect.
    7. Complete reworking of internal property system.
    8. Fixed Windows XP driver load crash.
    9. Fixed drop counter to be accessible from DirectShow.
    10. Fixed Windows 8 problem with certain video formats needing converters with standard DirectShow filters (e.g. Y800, capturing to an Y800 avi file was not possible).
    11. Fixed a problem with Windows 8 usbxhci driver not allowing transfers larger then 4 MB.
  • February 26, 2013 2.4.14.851

    Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.

    Version

    2.4.14.851

    Released

    February 26, 2013

    Type

    ZIP

    Filesize

    1.9MB

    Requirements

    • Intel Pentium IV or similar, 2 GB RAM
    • USB 3.0 or USB 2.0 controller (depends upon camera model)
    • Graphics card with 24 or 32 bit
    • Windows XP, Windows Vista, Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit)
    • DirectX 9.0c or higher

    Changelog

    1. WHQL certification.