This is a minor update over 1.2.7 - the following are the main updates:

Addition of new device IDs to monitor INF

Additional HDK-derived devices will have a name associated with their entry in "Device Manager" under "Monitors". Since this INF is currently cosmetic (naming) only, this is purely a cosmetic change, though it may help in troubleshooting to be able to identify if an HDK display interface is visible to Windows.

Addition of a metadata package for the HDK 2 beltbox, revision of other metadata packages.

Belt boxes shipped with the HDK 2 vary slightly in their hardware identifiers and so may not have been assigned a friendly name and photo icon in the "Devices and Printers" Control Panel. A new metadata package has been added to identify these belt boxes.

Other metadata packages have been slightly modified, primarily removing references to HDK 1.x when the associated component may also be found with HDK 2.

Cleanups and compatibility improvements for INF files
While they shouldn't have prevented anyone's usage of the devices, the INF files had some warnings or errors in Microsoft verification tools that were not false-positives and that could be resolved. This release includes those cleanups, which may in a few cases cause the cosmetic INF files to apply on systems where they had not installed before (primarily 32-bit systems).


The attached executable installer includes:

  • The USB-CDC (USB serial) driver (for that "OSVR unknown device") used by the OSVR Control app (for updating firmware, etc). (Required on Windows 8.1 and below, will show up on Windows 10 as well) - shows up as OSVR HMD Communications Device under Ports in Device Manager
  • Windows 7 and up: "Device Metadata Packages" - aka, the data that makes nice icons appear in Devices and Printers - for:
    • OSVR HDK
    • OSVR HDK display panel (see #2 for why this is separate)
    • OSVR HDK 1.2/1.3/1.4 Belt Box/Audio (primarily for control of the USB Audio codec on the belt box that lets you plug analog headsets in - handles the "OSVR Audio" or the mystery "RAZER USB AUDIO" you might have seen there before, but also changes name to help indicate the HDK hardware model you likely have)
    • OSVR HDK 2 Belt Box/Audio (same purpose as above but for a minor variation in the belt box shipped with some HDK 2 units)
    • OSVR HDK IR Tracking Camera (will change name and icon indicate if an outdated firmware version is detected)
  • "Atmel USB DFU" driver needed for when the HDK is in firmware-upgrade mode.
  • Extra .inf drivers (primarily for naming purposes in the Device Manager - they do not need to override the behavior of the system-bundled driver yet), for:
    • OSVR HDK Head-Mounted Display - under Monitors (normal for this to be missing/hidden when in direct mode)
    • OSVR HDK Orientation Tracker (and its parent device, OSVR HDK USB HID Interface) - under Human Interface Devices
    • OSVR High-Speed Infrared Tracking Camera - under Imaging devices

Note that the device metadata installer that is a part of the executable bundle requires the .NET framework v4 client profile. You probably already have it, but if not, you can get it through Windows Update or at http://www.microsoft.com/en-us/download/details.aspx?id=24872

As with previous installer executables, it can be run in silent mode by passing /S (case-sensitive!) on the command line to the installer.

The zip file contains only the .inf drivers for the USB-CDC (USB serial) device and the naming in Device Manager - it does not contain the "Devices and Printers" device metadata. It is provided as an option for those on non-x86/x64 platforms or as a convenience for advanced bundling purposes: its contents are a strict subset of the executable installer.

All drivers, as well as the installer, have been digitally signed by Sensics, Inc.

Revised metadata for HDK 1.4, improved Windows 10 support

@rpavlik rpavlik released this Jun 2, 2016 · 35 commits to master since this release

There are two main changes in this release compared to 1.2.6.

The first is a modification to the device metadata files to clarify that a given device may either be an HDK 1.3 or 1.4, to avoid confusing HDK 1.4 owners who see 1.3 pop up. (The electronics and drivers are substantially similar, so this is a cosmetic change only.)

The second is some minor updates to the .inf drivers: the USB serial port driver has been adjusted so that on Windows 10 it installs and wraps the bundled ("in-box") Windows 10 USB serial driver, and the IR camera driver has been modified slightly to better match the in-box USB video drivers on Windows 10 and to fix a corner case where the displayed name in the Device Manager would not always be overridden by the installation of the .inf file.


The attached executable installer includes:

  • The USB-CDC (USB serial) driver (for that "OSVR unknown device") used by the OSVR Control app (for updating firmware, etc). (Required on Windows 8.1 and below, will show up on Windows 10 as well) - shows up as OSVR HMD Communications Device under Ports in Device Manager
  • Windows 7 and up: "Device Metadata Packages" - aka, the data that makes nice icons appear in Devices and Printers - for:
    • OSVR HDK
    • OSVR HDK display panel (see #2 for why this is separate)
    • OSVR HDK 1.2/1.3/1.4 Belt Box/Audio (primarily for control of the USB Audio codec on the belt box that lets you plug analog headsets in - handles the "OSVR Audio" or the mystery "RAZER USB AUDIO" you might have seen there before, but also changes name to help indicate the HDK hardware model you likely have)
    • OSVR HDK IR Tracking Camera (will change name and icon indicate if an outdated firmware version is detected)
  • "Atmel USB DFU" driver needed for when the HDK is in firmware-upgrade mode.
  • Extra .inf drivers (primarily for naming purposes in the Device Manager - they do not need to override the behavior of the system-bundled driver yet), for:
    • OSVR HDK Head-Mounted Display - under Monitors (normal for this to be missing/hidden when in direct mode)
    • OSVR HDK Orientation Tracker (and its parent device, OSVR HDK USB HID Interface) - under Human Interface Devices
    • OSVR High-Speed Infrared Tracking Camera - under Imaging devices

Note that the device metadata installer that is a part of the executable bundle requires the .NET framework v4 client profile. You probably already have it, but if not, you can get it through Windows Update or at http://www.microsoft.com/en-us/download/details.aspx?id=24872

As with previous installer executables, it can be run in silent mode by passing /S (case-sensitive!) on the command line to the installer.

The zip file contains only the .inf drivers for the USB-CDC (USB serial) device and the naming in Device Manager - it does not contain the "Devices and Printers" device metadata. It is provided as an option for those on non-x86/x64 platforms or as a convenience for advanced bundling purposes: its contents are a strict subset of the executable installer.

All drivers, as well as the installer, have been digitally signed by Sensics, Inc.

This release primarily improves the user experience in the "Devices and Printers" window, with some INF file updates for Windows 10.

A new metadata package has been added for the HDK 1.3 beltbox audio. This fixes issue #7 for Windows 7 users, and since we can distinguish the beltbox shipped with the 1.3 from that shipped with the 1.2 (and earlier), the names for the devices have been updated to include an HDK version number, which may be convenient for all users. Below is a screen capture from "Devices and Printers" on a machine with both a HDK 1.2 and HDK 1.3 plugged in.

versioned-beltboxes-in-devices-and-printers

(Note: On the off chance you're using an older prototype than a 1.2, it will likely show up as a 1.2 belt box - if you go into Properties, it does actually report "v1.0-1.2" - or possibly as a harmless uncategorized.)

Similarly, a new device metadata package has been added to warn users if they have an outdated firmware version on their infrared camera, since this can seriously impact tracking performance.

camera-needs-update

Right-clicking on such a device will reveal a menu entry to bring you to a page where you can download a firmware upgrade tool.

camera-context-menu

Outside of the device metadata/Devices and Printers interface, the major version numbers on some of the "cosmetic" INF file drivers (currently that's display, HID, and camera) have been bumped to 10 to pre-empt the basic in-box Windows 10 drivers. This isn't critical, since they are cosmetic only (they just rename devices in the Device Manager), but it is nice to have. We are still using the standard "in-box" Windows 10 USB Serial driver.

win10-monitor-devnode
win10-ircam-devnode
win10-hid-devnodes


The attached executable installer includes:

  • Windows 8.1 and below: The USB-CDC (USB serial) driver (for that "unknown device") used by the OSVR Control app (for updating firmware, etc). (Windows 10 includes a driver that works fine) - shows up as OSVR HMD Communications Device under Ports in Device Manager
  • Windows 7 and up: "Device Metadata Packages" - aka, the data that makes nice icons appear in Devices and Printers - for:
    • OSVR HDK
    • OSVR HDK display panel (see #2 for why this is separate)
    • OSVR HDK 1.2/1.3 Belt Box/Audio (primarily for control of the USB Audio codec on the belt box that lets you plug analog headsets in - handles the "OSVR Audio" or the mystery "RAZER USB AUDIO" you might have seen there before, but also changes name to help indicate the HDK hardware model you likely have)
    • OSVR HDK IR Tracking Camera (will change name and icon indicate if an outdated firmware version is detected)
  • "Atmel USB DFU" driver needed for when the HDK is in firmware-upgrade mode.
  • Extra .inf drivers (primarily for naming purposes in the Device Manager - they do not need to override the behavior of the system-bundled driver yet), for:
    • OSVR HDK Head-Mounted Display - under Monitors (normal for this to be missing/hidden when in direct mode)
    • OSVR HDK Orientation Tracker (and its parent device, OSVR HDK USB HID Interface) - under Human Interface Devices
    • OSVR High-Speed Infrared Tracking Camera - under Imaging devices

Note that the device metadata installer that is a part of the executable bundle requires the .NET framework v4 client profile. You probably already have it, but if not, you can get it through Windows Update or at http://www.microsoft.com/en-us/download/details.aspx?id=24872

As with previous installer executables, it can be run in silent mode by passing /S (case-sensitive!) on the command line to the installer.

The zip file contains only the .inf drivers for the USB-CDC (USB serial) device and the naming in Device Manager - it does not contain the "Devices and Printers" device metadata. It is provided as an option for those on non-x86/x64 platforms or as a convenience for advanced bundling purposes: its contents are a strict subset of the executable installer.

All drivers, as well as the installer, have been digitally signed by Sensics, Inc.

Fixed multi-lingual install

@rpavlik rpavlik released this Nov 9, 2015 · 59 commits to master since this release

This release differs from 1.2.4 in correcting a bug that resulted in the automated installer not working on some non-US locales. As a part of this fix, the text in the driver installer is more generic, but it should work reliably on varied locales.

As the only difference is in the installer, the driver version numbers remain at 1.2.3. If you were able to install 1.2.4, there is no need to update to this version, though it is safe to install over existing versions. If you just want the .zip of the .inf files, use the ones from v1.2.3


The attached executable installer includes:

  • Windows 8.1 and below: The USB-CDC driver (for that "unknown device") used by the OSVR Control app (for updating firmware, etc). (Windows 10 includes a driver that works fine) - shows up as OSVR HMD Communications Device under Ports in Device Manager
  • Windows 7 and up: "Device Metadata Packages" - aka, the data that makes nice icons appear in Devices and Printers - for:
    • OSVR HDK
    • OSVR HDK display panel (see #2 for why this is separate)
    • OSVR HDK Belt Box/Audio (primarily for control of the USB Audio codec on the belt box that lets you plug analog headsets in - handles the mystery "RAZER USB AUDIO" you might have seen there before)
    • OSVR HDK IR Tracking Camera
  • "Atmel USB DFU" driver needed for when the HDK is in firmware-upgrade mode.
  • Extra .inf drivers (primarily for naming purposes in the Device Manager - they do not need to override the behavior of the system-bundled driver yet), for:
    • OSVR HDK Head-Mounted Display - under Monitors
    • OSVR HDK Orientation Tracker (and its parent device, OSVR HDK USB HID Interface) - under Human Interface Devices
    • OSVR High-Speed Infrared Tracking Camera - under Imaging devices

Note that the device metadata installer that is a part of the executable bundle requires the .NET framework v4 client profile. You probably already have it, but if not, you can get it through Windows Update or at http://www.microsoft.com/en-us/download/details.aspx?id=24872

As with previous installer executables, it can be run in silent mode by passing /S (case-sensitive!) on the command line to the installer.

Now also includes "Atmel USB DFU" driver for firmware upgrading

@rpavlik rpavlik released this Oct 22, 2015 · 62 commits to master since this release

This release differs from 1.2.3 only in that the combined installer now includes the Atmel USB DFU drivers, which are used when the HDK is put into firmware upgrade mode. Since those drivers are used unmodified from Atmel, with their driver signature intact, you may see an additional prompt from Windows asking you if you trust drivers signed by Atmel (in addition to the prompt mentioning Sensics).

No other contents (and thus driver version numbers) have changed since 1.2.3. Safe to install on a fresh machine as well as right over an earlier package. If you just want the .zip of the .inf files, use the one from the previous release.


The attached executable installer includes:

  • Windows 8.1 and below: The USB-CDC driver (for that "unknown device") used by the OSVR Control app (for updating firmware, etc). (Windows 10 includes a driver that works fine) - shows up as OSVR HMD Communications Device under Ports in Device Manager
  • Windows 7 and up: "Device Metadata Packages" - aka, the data that makes nice icons appear in Devices and Printers - for:
    • OSVR HDK
    • OSVR HDK display panel (see #2 for why this is separate)
    • OSVR HDK Belt Box/Audio (primarily for control of the USB Audio codec on the belt box that lets you plug analog headsets in - handles the mystery "RAZER USB AUDIO" you might have seen there before)
    • OSVR HDK IR Tracking Camera
  • "Atmel USB DFU" driver needed for when the HDK is in firmware-upgrade mode.
  • Extra .inf drivers (primarily for naming purposes in the Device Manager - they do not need to override the behavior of the system-bundled driver yet), for:
    • OSVR HDK Head-Mounted Display - under Monitors
    • OSVR HDK Orientation Tracker (and its parent device, OSVR HDK USB HID Interface) - under Human Interface Devices
    • OSVR High-Speed Infrared Tracking Camera - under Imaging devices

Note that the device metadata installer that is a part of the executable bundle requires the .NET framework v4 client profile. You probably already have it, but if not, you can get it through Windows Update or at http://www.microsoft.com/en-us/download/details.aspx?id=24872

As with previous installer executables, it can be run in silent mode by passing /S (case-sensitive!) on the command line to the installer.

Devices named and metadata included

@rpavlik rpavlik released this Oct 12, 2015 · 72 commits to master since this release

The attached executable installer includes:

  • Windows 8.1 and below: The USB-CDC driver (for that "unknown device") used by the OSVR Control app (for updating firmware, etc). (Windows 10 includes a driver that works fine) - shows up as OSVR HMD Communications Device under Ports in Device Manager
  • Windows 7 and up: "Device Metadata Packages" - aka, the data that makes nice icons appear in Devices and Printers - for:
    • OSVR HDK
    • OSVR HDK display panel (see #2 for why this is separate)
    • OSVR HDK Belt Box/Audio (primarily for control of the USB Audio codec on the belt box that lets you plug analog headsets in - handles the mystery "RAZER USB AUDIO" you might have seen there before)
    • OSVR HDK IR Tracking Camera
  • Extra .inf drivers (primarily for naming purposes in the Device Manager - they do not need to override the behavior of the system-bundled driver yet), for:
    • OSVR HDK Head-Mounted Display - under Monitors
    • OSVR HDK Orientation Tracker (and its parent device, OSVR HDK USB HID Interface) - under Human Interface Devices
    • OSVR High-Speed Infrared Tracking Camera - under Imaging devices

Note that the device metadata installer that is a part of the executable bundle requires the .NET framework v4 client profile. You probably already have it, but if not, you can get it through Windows Update or at http://www.microsoft.com/en-us/download/details.aspx?id=24872

As with previous installer executables, it can be run in silent mode by passing /S (case-sensitive!) on the command line to the installer.

The zip file contains only the .inf drivers for the USB-CDC device and the naming in Device Manager - it does not contain the "Devices and Printers" device metadata. It is provided as an option for those on non-x86/x64 platforms or as a convenience for advanced bundling purposes: its contents are a strict subset of the executable installer.

All drivers, as well as the installer, have been digitally signed by Sensics, Inc.

Screenshot of Devices and Printers:
devices-and-printers

Device Manager screenshots:
camera
hid
monitor-and-cdc

Now the driver should do something, in addition to installing...

@rpavlik rpavlik released this Sep 30, 2015 · 130 commits to master since this release

Contains a revised driver that has been tested to actually let you open the serial port, in addition to just seeing it in the device manager. (Oops! Clearly my test plan had a hole in it...)

As with the previous release, the zip file contains just the inf and cat, while the installer takes care of installing them for you. There is now snazzy documentation and troubleshooting info: https://github.com/OSVR/OSVR-HDK-Windows-Drivers/blob/master/HDK-CDC-Installer-Instructions/README.md

You can install this right over the old one.

Initial Release (fixed)

@rpavlik rpavlik released this Sep 29, 2015 · 136 commits to master since this release

Initial release of the Sensics-authored CDC .inf file and associated installer. The .inf file and associated .cat file are signed by Sensics and should work on all Windows platforms (x86, x64, IA64, ARM)

  • The .zip file just contains the .inf and .cat, and are suitable for use with pnputil or the "have disk" method on the unknown "OSVR" device on any Windows architecture.
  • The .exe is a simple wrapper to handle installing the driver automatically, but only works with x86 and x64 (since it's a native executable). This installer is also signed by Sensics. You can pass the command line argument /S (case sensitive) to install in silent mode.
    • Has been tested with the HDK both plugged-in and unplugged when running the installer, with both the silent and "non-silent" modes.

Both contain the same .inf and .cat and thus are functionally the same.