Drivers CMS USB Devices

admin



To install a certain driver using the DevCon utility, you need the INF file which comes bundled with the driver files. Now, to install a device driver, use the following command. Don’t forget to replace “Path to INF file” with the actual path and the “hardwareID” with the actual hardware ID. Windows 8, 8.1 & 10 Fresh Install of Instrument USB driver: If you currently don't have any applications that talk to your instrument using USB, then it is relatively simple to use the drivers provided with Argyll, since you don't have to deal with the instrument already having an assigned driver. As well as drivers for various types of devices with extended temperature range (ET) and different types of PCBs System requirements: Windows Vista (32-bit), XP (32-bit)., 2000, 98/Me. For Microsoft Windows XP (32-Bit) digital signed.

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)

For 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.

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.

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

Usb-->

Symptoms

Consider the following scenario:

  1. You connect a Universal Serial Bus (USB) audio device, such as an audio adapter or USB digital-to-analog converter (DAC), to a Windows 10 Version 1703-based computer for the first time.
  2. The operating system detects the device and loads the standard USB audio 2.0 driver (usbaudio2.sys).
  3. Windows then downloads the device-specific driver from Windows Update.
  4. The downloaded device driver replaces the usbaudio2.sys driver.

In this scenario, the device cannot be used, and the computer does not have sound. The speaker icon on the task bar is marked with an X mark. When you select the icon, you receive the following message:

Audio services not responding. Both the Windows Audio and the Windows Audio End Point Builder services must be running for audio to work correctly.

Unknown Usb Device Driver Download

Examples

Cause

This 'audio not playing' problem occurs because the default USB audio 2.0 driver (usbaudio2.sys) uses the WaveRT port for operation but the device-specific driver does not. However, both drivers use the 'wave' reference string when the device interface is registered.When the device-specific driver replaces the default driver, the device interface that is created by usbaudio2.sys is still used because the reference strings overlap. Therefore, the operating system assumes that the new driver also supports the WaveRT port. Because the new driver does not support the WaveRT port, the system cannot access the driver.

Resolution

To fix this problem, use one of the following methods.

Method 1

Uninstall the device. To do this, follow these steps:

  1. Open Device Manager.
  2. Select and hold (or double-click) the name of the device, and then select Uninstall.

Note:In step 2, don't select the Delete the driver software for this device check box.

Best Usb Devices

Method 2

Connect the device to a different USB port. The problem may not occur if the device is connected to a different USB port.

Method 3

USB

If the device is not yet connected, install the device-specific driver first. You can do this by using the appropriate installer for the device. Then, connect the device. Windows now selects the device-specific driver instead of the default USB audio 2.0 driver. This method works in this situation because the problem occurs only if the device-specific driver replaces the default driver after the device is connected.

See Also