Vitalograph USB Devices Driver Download For Windows 10

Vitalograph USB Devices Driver Download For Windows 10

Vitalograph Usb Devices Driver Download For Windows 10 Pro
Vitalograph Usb Devices Driver Download For Windows 10 3 8 5
Vitalograph Usb Devices Driver Download For Windows 10 32 Bit
Vitalograph Usb Devices Driver Download For Windows 10 Offline
Vitalograph Usb Devices Driver Download For Windows 10 Laptop
Vitalograph Usb Devices Driver Download For Windows 10 64-bit

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. Why Vitalograph; Clinical Trials Why Vitalograph; Services; Devices; Telehealth Service & Support Technical Helpline; Software Activation; Product Registration; Spirotrac V; Online Shop; Resources Normal Values; Resource Articles; White Papers. Addition of the Vitalograph 2120 as a device. Addition of the Vitalograph Alpha as a device. PCF (Peak Cough Flow) Test. Challenge Testing – Mannitol, ATS 5-breath dosimeter, 2-min tidal breathing and Exercise challenge. Six Minute Walk Testing. In2itive Device Downloads/Uploads module. Alpha Touch Device Downloads/Uploads. Driver: Windows 10, 32-bit. Windows 10, 64-bit. Windows Server 2019. 2 more: 10.1. Latest: 5/7/2020: Intel® Management Engine Driver for Windows 8.1. and Windows® 10. Provides Intel® Management Engine Driver for Windows 8.1. and Windows® 10 Supporting 6th,7th and 8th Generation Intel® Core™ Processor Family (Sky Lake,Kaby Lake.
You can use Android Debug Bridge (ADB) to connect your Fire tablet to your computer for testing and debugging. You connect your computer to your Fire tablet through a micro-USB cable.
Android Debug Bridge (ADB) is a command-line utility for running and managing Android apps on your device or emulator. For more information and instructions on using ADB, see Android Debug Bridge.
Vitalograph Usb Devices Driver Download For Windows 10 ProIf you're looking for instructions on connecting to a Fire TV instead, see Connect to Fire TV Through ADB.
Check for Device Connections Using ADB (Optional)
Troubleshooting
Step 1: Enable Developer OptionsGo to Settings > Device Options and look for a Developer Options menu. If it's not there, do the following:
a. Go to Settings > Device Options > About Fire Tablet.b. Tap your Serial Number seven times.c. Return to Device Options. A new menu appears called 'Developer Options.'
Tap Developer options. (2013 models might call this option 'Security.')
Set Developer options and USB debugging to ON.
If you have a Kindle Fire 1st Generation, ADB is enabled by default.
Step 2: Install the Kindle Fire Driver (Windows Only)If you're using Windows, download this Kindle Fire driver: kindle_fire_usb_driver.zip.
After downloading the file, extract the contents into a new folder and double-click the Fire_Devices ABD drivers file.
Proceed through the installation wizard screens to install the driver.
Step 3: Install Android Studio

Vitalograph USB Devices Driver Download For Windows 10

ADB is available on your computer when you install Android Studio. If you don't already have Android Studio, download and install Android Studio. If you're not using Android Studio, you need to download and install Android SDK platform tools.
Step 4: Connect Your Fire Device to Your Computer with a USB CableUsing a USB cable, connect your Fire tablet to a USB port on your computer.
Note that Fire tablets can treat the USB with different transfer options. After connecting the USB cable, swipe down from the top of your tablet to see the USB option used. You might see various notifications, including the USB connection type that was used when you connected the cable. The relevant notification is highlighted in the screenshot below.
If you don't see 'Connected as Media Device', press Tap for other USB options. Then select Media device (MTP). Later Fire OS versions have a different interface here. If you're using Fire OS 7, select File Transfer.
Note: If your USB is connected as a Camera (PTP), Android Studio won't recognize the tablet as a device in Android Studio.
If you don't see the USB connection type in the above notifications, go to Settings > Device Options > Developer Options > USB computer connection. Set this to Media device (MTP). For Fire OS 7, select File Transfer.
When the Allow USB debugging? dialog appears on your tablet, tap OK.
Open Android Studio and look for the device to appear in devices drop-down menu:
The device's name will use the android.os.Build.MODEL property for the device. KFSUWI refers to Fire HD 10 (2017) tablet. You can see a list of build model names in the Identifying Fire Tablet Devices.
If you have not selected the 'Allow USB Debugging' dialog on your tablet, the name 'Unknown device' will appear in the devices drop-down menu in Android Studio until you allow debugging.
With the tablet connected, you can now run your app on your tablet by clicking the Run App button in Android Studio.
If you run into issues, see the Troubleshooting section below.
Check for Device Connections Using ADB (Optional)Instead of looking in the devices menu in Android Studio, you can also use some ADB terminal commands to confirm that your device is connected. ADB is useful for performing many other operations as well, such as entering sandbox mode or installing other assets. Follow these two sections:
If you skip adding ADB to your PATH, you can also Check for Connected Devices If ADB Isn't In Your PATH.
Add ADB to Your PATHFirst, add ADB to your PATH so you can more easily run ADB commands. (Your PATH is an environment variable used to specify the location of the program's executable. If you don't add ADB to your PATH, running ADB commands will require you to browse to the /platform-tools directory to run adb.)
Tip: You can check whether ADB is already added to your PATH by typing adb version from a terminal or command prompt. If you get back version information, then ADB is in your PATH. If the response says adb is an unrecognized command, ADB is not in your PATH.
To add ADB to your PATH on Mac:
Get the path to your Android SDK platform-tools directory:
Open Android Studio and click the SDK Manager button .The location to your Android SDK appears near the top next to Android SDK Location. For example: /Users//Library/Android/sdk
If this is your first time opening Android Studio, there isn't an SDK Manager button. Instead, at the Welcome to Android Studio prompt, click Configure > SDK Manager and provide the location to the Android SDK.
Copy the path to the SDK and paste it somewhere convenient, such as a text editor.
Add /platform-tools to the end of the path you copied in the previous step. ('platform-tools' is the directory containing the ADB executable.)
Copy the full path to your clipboard.
Use the following command to add ADB to your .bash_profile. Replace  with your actual username. Also, make sure the path points to your Android SDK.
Your .bash_profile file is usually in your user directory, which you can find by typing cd ~ (change to your user directory). Then type ls -a (list all) to show all files, including hidden ones.
If the file isn't there, simply create one. You can then type open .bash_profile to see the paths listed.
After you add this PATH to your bash profile, you should see the following in your .bash_profile file:
(Only instead of johndoe, you will see your own username.)
Fully restart any terminal sessions, and then type adb. If you successfully added ADB to your path, you will see ADB help info rather than 'command not found.'
To add ADB to your PATH on Windows:
Get the path to your Android SDK platform-tools directory:
Open Android Studio and click the SDK Manager button .
The location to your Android SDK appears near the top next to Android SDK Location. For example: C:UsersAppDataLocalAndroidSdk
If this is your first time opening Android Studio, there isn't an SDK Manager button. Instead, at the Welcome to Android Studio prompt, click Configure > SDK Manager and provide the location to the Android SDK.
Copy the path to the SDK and paste it somewhere convenient, such as a text editor.
Add /platform-tools to the end of the path you copied in the previous step. ('platform-tools' is the directory containing the ADB executable.)
Copy the full path to your clipboard.
Click your computer's search button (next to Start) and type view advanced system settings.
Click View advanced system settings.
When the System Settings dialog opens, click the Environment Variables button.
Under System Variables (the lower pane), select Path and click Edit.
Do one of the following:
On Windows 7 or 8, move your cursor to the farthest position on the right, type ; and then press Ctrl+V to insert the path to your SDK that you copied earlier. It may look like this: ;C:UsersAppDataLocalAndroidSdkplatform-tools. Click OK on each of the three open dialog boxes to close them.
On Windows 10, click the New button and add this location.
Restart any terminal sessions, and then type adb. If you successfully added ADB to your path, you will see ADB help info rather than 'command not found.'
Check for Connected DevicesAssuming ADB is added to your PATH, run the following commands:
Confirm that the serial number for your Fire tablet appears in the list of devices. For example:
On your tablet, your device's serial number is located under Settings > Device Options.
Check for Connected Devices If ADB Isn't In Your PATHIf your terminal doesn't recognize adb as a command (that is, you didn't add ADB to your PATH), you might have to run the commands from the SDK directory that contains ADB.
In Android Studio go to Tools > SDK Manager.
In the SDK Manager dialog box, copy the Android SDK Location.
Browse to this location in your terminal or command prompt. For example:
Mac
Windows
Then go into the platform-tools directory:
The platform-tools directory contains adb.
Now run the ADB commands as follows:
Mac:
Windows:
The response should list your device's serial number. For example:
If your Fire tablet is still not detected, you may need to reboot your computer or log out and back in for the changes to take effect.
TroubleshootingTablet doesn't appear in list of devices in Android StudioIf you don't see your tablet device in the list of devices in Android Studio, click the devices drop-down menu and select Troubleshoot device connections:
Click Rescan devices.
If rescanning devices doesn't detect your Fire tablet as a device, your micro-USB cable might be bad, you might have the wrong USB connection type (e.g, camera instead of media device), or you might not have enabled USB debugging. You can also try restarting your computer and the tablet.
Uninstall the non-ADB Driver (Windows)Vitalograph Usb Devices Driver Download For Windows 10 3 8 5If you previously connected a Fire tablet without first enabling ADB on the Fire tablet, you might need to remove the existing USB device driver and force re-installation of the driver. To remove the non-ADB driver:
Vitalograph Usb Devices Driver Download For Windows 10 32 BitUsing a micro-USB cable, connect your Fire tablet to a USB port on your computer.
On your computer (Windows 10), click the search button (next to the Start menu) and type Device Manager in the search. Then select it in the results. (Other Windows versions have different options for accessing the Control Panel.)
In the Device Manager window, expand Portable Devices.
Right-click the Fire device and then click Properties.
In the Properties window, on the Driver tab, click Uninstall, and then Confirm.
Unplug your Fire tablet from your computer.
Vitalograph Usb Devices Driver Download For Windows 10 OfflineConfirm the Fire Driver Is Installed CorrectlyVitalograph Usb Devices Driver Download For Windows 10 LaptopYou can confirm that the Fire driver is installed correctly by doing the following:

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. Why Vitalograph; Clinical Trials Why Vitalograph; Services; Devices; Telehealth Service & Support Technical Helpline; Software Activation; Product Registration; Spirotrac V; Online Shop; Resources Normal Values; Resource Articles; White Papers. Addition of the Vitalograph 2120 as a device. Addition of the Vitalograph Alpha as a device. PCF (Peak Cough Flow) Test. Challenge Testing – Mannitol, ATS 5-breath dosimeter, 2-min tidal breathing and Exercise challenge. Six Minute Walk Testing. In2itive Device Downloads/Uploads module. Alpha Touch Device Downloads/Uploads. Driver: Windows 10, 32-bit. Windows 10, 64-bit. Windows Server 2019. 2 more: 10.1. Latest: 5/7/2020: Intel® Management Engine Driver for Windows 8.1. and Windows® 10. Provides Intel® Management Engine Driver for Windows 8.1. and Windows® 10 Supporting 6th,7th and 8th Generation Intel® Core™ Processor Family (Sky Lake,Kaby Lake.
You can use Android Debug Bridge (ADB) to connect your Fire tablet to your computer for testing and debugging. You connect your computer to your Fire tablet through a micro-USB cable.
Android Debug Bridge (ADB) is a command-line utility for running and managing Android apps on your device or emulator. For more information and instructions on using ADB, see Android Debug Bridge.
Vitalograph Usb Devices Driver Download For Windows 10 ProIf you're looking for instructions on connecting to a Fire TV instead, see Connect to Fire TV Through ADB.
Check for Device Connections Using ADB (Optional)
Troubleshooting
Step 1: Enable Developer OptionsGo to Settings > Device Options and look for a Developer Options menu. If it's not there, do the following:
a. Go to Settings > Device Options > About Fire Tablet.b. Tap your Serial Number seven times.c. Return to Device Options. A new menu appears called 'Developer Options.'
Tap Developer options. (2013 models might call this option 'Security.')
Set Developer options and USB debugging to ON.
If you have a Kindle Fire 1st Generation, ADB is enabled by default.
Step 2: Install the Kindle Fire Driver (Windows Only)If you're using Windows, download this Kindle Fire driver: kindle_fire_usb_driver.zip.
After downloading the file, extract the contents into a new folder and double-click the Fire_Devices ABD drivers file.
Proceed through the installation wizard screens to install the driver.
Step 3: Install Android StudioADB is available on your computer when you install Android Studio. If you don't already have Android Studio, download and install Android Studio. If you're not using Android Studio, you need to download and install Android SDK platform tools.
Step 4: Connect Your Fire Device to Your Computer with a USB CableUsing a USB cable, connect your Fire tablet to a USB port on your computer.
Note that Fire tablets can treat the USB with different transfer options. After connecting the USB cable, swipe down from the top of your tablet to see the USB option used. You might see various notifications, including the USB connection type that was used when you connected the cable. The relevant notification is highlighted in the screenshot below.
If you don't see 'Connected as Media Device', press Tap for other USB options. Then select Media device (MTP). Later Fire OS versions have a different interface here. If you're using Fire OS 7, select File Transfer.
Note: If your USB is connected as a Camera (PTP), Android Studio won't recognize the tablet as a device in Android Studio.
If you don't see the USB connection type in the above notifications, go to Settings > Device Options > Developer Options > USB computer connection. Set this to Media device (MTP). For Fire OS 7, select File Transfer.
When the Allow USB debugging? dialog appears on your tablet, tap OK.
Open Android Studio and look for the device to appear in devices drop-down menu:
The device's name will use the android.os.Build.MODEL property for the device. KFSUWI refers to Fire HD 10 (2017) tablet. You can see a list of build model names in the Identifying Fire Tablet Devices.
If you have not selected the 'Allow USB Debugging' dialog on your tablet, the name 'Unknown device' will appear in the devices drop-down menu in Android Studio until you allow debugging.
With the tablet connected, you can now run your app on your tablet by clicking the Run App button in Android Studio.
If you run into issues, see the Troubleshooting section below.
Check for Device Connections Using ADB (Optional)Instead of looking in the devices menu in Android Studio, you can also use some ADB terminal commands to confirm that your device is connected. ADB is useful for performing many other operations as well, such as entering sandbox mode or installing other assets. Follow these two sections:
If you skip adding ADB to your PATH, you can also Check for Connected Devices If ADB Isn't In Your PATH.
Add ADB to Your PATHFirst, add ADB to your PATH so you can more easily run ADB commands. (Your PATH is an environment variable used to specify the location of the program's executable. If you don't add ADB to your PATH, running ADB commands will require you to browse to the /platform-tools directory to run adb.)
Tip: You can check whether ADB is already added to your PATH by typing adb version from a terminal or command prompt. If you get back version information, then ADB is in your PATH. If the response says adb is an unrecognized command, ADB is not in your PATH.
To add ADB to your PATH on Mac:
Get the path to your Android SDK platform-tools directory:
Open Android Studio and click the SDK Manager button .The location to your Android SDK appears near the top next to Android SDK Location. For example: /Users//Library/Android/sdk
If this is your first time opening Android Studio, there isn't an SDK Manager button. Instead, at the Welcome to Android Studio prompt, click Configure > SDK Manager and provide the location to the Android SDK.
Copy the path to the SDK and paste it somewhere convenient, such as a text editor.
Add /platform-tools to the end of the path you copied in the previous step. ('platform-tools' is the directory containing the ADB executable.)
Copy the full path to your clipboard.
Use the following command to add ADB to your .bash_profile. Replace  with your actual username. Also, make sure the path points to your Android SDK.
Your .bash_profile file is usually in your user directory, which you can find by typing cd ~ (change to your user directory). Then type ls -a (list all) to show all files, including hidden ones.
If the file isn't there, simply create one. You can then type open .bash_profile to see the paths listed.
After you add this PATH to your bash profile, you should see the following in your .bash_profile file:
(Only instead of johndoe, you will see your own username.)
Fully restart any terminal sessions, and then type adb. If you successfully added ADB to your path, you will see ADB help info rather than 'command not found.'
To add ADB to your PATH on Windows:
Get the path to your Android SDK platform-tools directory:
Open Android Studio and click the SDK Manager button .
The location to your Android SDK appears near the top next to Android SDK Location. For example: C:UsersAppDataLocalAndroidSdk
If this is your first time opening Android Studio, there isn't an SDK Manager button. Instead, at the Welcome to Android Studio prompt, click Configure > SDK Manager and provide the location to the Android SDK.
Copy the path to the SDK and paste it somewhere convenient, such as a text editor.
Add /platform-tools to the end of the path you copied in the previous step. ('platform-tools' is the directory containing the ADB executable.)
Copy the full path to your clipboard.
Click your computer's search button (next to Start) and type view advanced system settings.
Click View advanced system settings.
When the System Settings dialog opens, click the Environment Variables button.
Under System Variables (the lower pane), select Path and click Edit.
Do one of the following:
On Windows 7 or 8, move your cursor to the farthest position on the right, type ; and then press Ctrl+V to insert the path to your SDK that you copied earlier. It may look like this: ;C:UsersAppDataLocalAndroidSdkplatform-tools. Click OK on each of the three open dialog boxes to close them.
On Windows 10, click the New button and add this location.
Restart any terminal sessions, and then type adb. If you successfully added ADB to your path, you will see ADB help info rather than 'command not found.'
Check for Connected DevicesAssuming ADB is added to your PATH, run the following commands:
Confirm that the serial number for your Fire tablet appears in the list of devices. For example:
On your tablet, your device's serial number is located under Settings > Device Options.
Check for Connected Devices If ADB Isn't In Your PATHIf your terminal doesn't recognize adb as a command (that is, you didn't add ADB to your PATH), you might have to run the commands from the SDK directory that contains ADB.
In Android Studio go to Tools > SDK Manager.
In the SDK Manager dialog box, copy the Android SDK Location.
Browse to this location in your terminal or command prompt. For example:
Mac
Windows
Then go into the platform-tools directory:
The platform-tools directory contains adb.
Now run the ADB commands as follows:
Mac:
Windows:
The response should list your device's serial number. For example:
If your Fire tablet is still not detected, you may need to reboot your computer or log out and back in for the changes to take effect.
TroubleshootingTablet doesn't appear in list of devices in Android StudioIf you don't see your tablet device in the list of devices in Android Studio, click the devices drop-down menu and select Troubleshoot device connections:
Click Rescan devices.
If rescanning devices doesn't detect your Fire tablet as a device, your micro-USB cable might be bad, you might have the wrong USB connection type (e.g, camera instead of media device), or you might not have enabled USB debugging. You can also try restarting your computer and the tablet.
Uninstall the non-ADB Driver (Windows)Vitalograph Usb Devices Driver Download For Windows 10 3 8 5If you previously connected a Fire tablet without first enabling ADB on the Fire tablet, you might need to remove the existing USB device driver and force re-installation of the driver. To remove the non-ADB driver:
Vitalograph Usb Devices Driver Download For Windows 10 32 BitUsing a micro-USB cable, connect your Fire tablet to a USB port on your computer.
On your computer (Windows 10), click the search button (next to the Start menu) and type Device Manager in the search. Then select it in the results. (Other Windows versions have different options for accessing the Control Panel.)
In the Device Manager window, expand Portable Devices.
Right-click the Fire device and then click Properties.
In the Properties window, on the Driver tab, click Uninstall, and then Confirm.
Unplug your Fire tablet from your computer.
Vitalograph Usb Devices Driver Download For Windows 10 OfflineConfirm the Fire Driver Is Installed CorrectlyVitalograph Usb Devices Driver Download For Windows 10 LaptopYou can confirm that the Fire driver is installed correctly by doing the following:
On your computer, click the search button search button (next to the Start menu) and type Device Manager.
In Device Manager, under Fire Devices, verify that that a device appears called Android Composite ADB Interface.
If your Device Manager shows an Other Devices section with a second Fire device with a yellow alert sign, your computer is listing Amazon's unrecognized ADB module as a separate device. To fix this issue:
Under Other Devices, right-click the Fire device and select Properties.
On the Driver tab of the Properties window, select Update Driver…
Choose to browse for the driver software, then navigate to Let me pick from a list of device drivers on my computer > Show All Devices > Have Disk.
Navigate to the folder where you installed the Amazon driver (typically C:Program Files (x86)Amazon.comFire_DevicesDrivers) and select it.
Ignore the warning regarding installing drivers and proceed.
You should now correctly see your Fire tablet with the ADB driver installed.
Last updated: Oct 29, 2020
Vitalograph Usb Devices Driver Download For Windows 10 64-bitAugust 22, 2019 2.9.8Device 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
Added several internal interfaces for particular sensors (J003).
January 25, 2019 2.9.6Device 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
Added missing Tonemapping Auto property.
May 4, 2018 2.9.5Device 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
Enabled tonemapping for 8bit video formats, e.g. Y800, RGB24 and RGB32.
November 21, 2017 2.9.4Device 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
Repaired not working J003 mono sensor pattern fix on particular video formats.
This driver version is the last that works in Windows XP.
January 9, 2017 2.9.3Device 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
Added a pattern fix for J003 mono sensors.
January 9, 2017 2.9.1Device 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
Fixed the driver signature Code 52 error on new Windows 10 v1607 systems.
January 15, 2016 2.8.9Device 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
Changed certificates so that the driver can also be installed in Vista.
November 9, 2015 2.8.7Device 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
Fixed an error which can appear when using sharpness on older CPUs.
October 20, 2015 2.8.5Device 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
Fixed a bug which can appear on LivePause call.
July 15, 2015 2.8.0Device 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
Support of DFK ECU010-L34 with serial number property.
Added tone mapping.
February 17, 2015 2.7.33Device 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
The Auto Focus Onepush Running flag now resets correctly after the auto focus has finished.
February 5, 2015 2.7.32Device 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
Video format MJPG (2592x1944) of DFK AFU050-L34 camera can now be used.
January 14, 2015 2.7.31Device 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
Support for IMX236 based cameras.
Support for RGB64 color formats.
Several performance improvements.
June 6, 2014 2.7.9.1152Device 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
Added new properties: Brightness, sharpness, de-noise, saturation, hue and contrast.
Added new property: Highlight reduction.
Added new property: White balance temperature controls.
Pixelfix for Y16 cameras now works as expected.
VideoControl_ExternalTrigger (DirectShow property) can now be set as expected.
January 1, 2014 2.6.5.1014Device 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
Fixed missing auto-gain for DFK AFU130.
Fixed focus when start value is out of auto_focus_range.
Fixed problem with AUTOFOCUS_ROI_RIGHT: minimum possibly wrong.
Fixed auto focus ROI not working for 21*UC cameras.
Fixed crash on load/connect with certain cameras 22/72xUC.
Fixed previous exposure settings not being loaded on reconnect.
Complete reworking of internal property system.
Fixed Windows XP driver load crash.
Fixed drop counter to be accessible from DirectShow.
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).
Fixed a problem with Windows 8 usbxhci driver not allowing transfers larger then 4 MB.
February 26, 2013 2.4.14.851Device 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
WHQL certification.