• Halliburton Energy Services Usb Devices Driver Download For Windows 10 64-bit
• Halliburton Energy Services Usb Devices Driver Download For Windows 10 64
• Halliburton Energy Services Usb Devices Driver Download For Windows 10 Free
• Halliburton Energy Services Usb Devices Driver Download For Windows 10 Windows 10

Starting with Windows 10, release 1703, a USB Audio 2.0 driver is shipped with Windows. It is designed to support the USB Audio 2.0 device class. The driver is a WaveRT audio port class miniport. For more information about the USB Audio 2.0 device class, see https://www.usb.org/documents?search=&type%5B0%5D=55&items_per_page=50.

Hold down the Shift key while selecting Restart. Restart is located under Power options menu (Windows 8: located under Charms or on the login screen) (Windows 10: located on the Start Menu). The PC will reboot, enabling you to select Troubleshoot. Select Troubleshoot Advanced options Startup Settings. Semiconductor device manufacturing: process (Class 438) Electrical connectors (Class 439) Marine propulsion (Class 440) Buoys, rafts, and aquatic devices (Class 441) Fabric (woven, knitted, or nonwoven textile or cloth, etc.) (Class 442) Electric lamp or space discharge component or device manufacturing (Class 445) Amusement devices: toys.

The driver is named: usbaudio2.sys and the associated inf file is usbaudio2.inf.

The driver will identify in device manager as 'USB Audio Class 2 Device'. This name will be overwritten with a USB Product string, if it is available.

• 2012-06-15 Assigned to HALLIBURTON ENERGY SERVICES, INC. Reassignment HALLIBURTON ENERGY SERVICES, INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: BITTAR, MICHAEL S., PAULK, MARTIN D., MENEZES, CLIVE D. 2012-10-04 Publication of US9A1 publication Critical patent/US9A1/en.
• In order to get Windows 10 support for USB Type-C, you must plug into the UCM device stack. USB Type-C MUTT requirements for HLK tests. The Windows HLK for Windows 10 contains tests for USB host and function controllers. To test your system, use a USB C-A adapter. These tests are listed in Windows Hardware Certification Kit Tests for USB.
• Download the Support Services Datasheet Whether you are a Digi customer, channel partner, distributor, or solution partner, Digi Technical Services is at the ready to offer an exceptionally broad range of support services to help you resolve issues, create innovative products, and get to market faster with higher-quality solutions.

The driver is automatically enabled when a compatible device is attached to the system. However, if a third-party driver exists on the system or Windows Update, that driver will be installed and override the class driver.

Architecture

usbaudio2.sys fits within the wider architecture of Windows USB Audio as shown.

Related USB specifications

The following USB specifications define USB Audio and are referenced in this topic.

• USB-2 refers to the Universal Serial Bus Specification, Revision 2.0
• ADC-2 refers to the USB Device Class Definition for Audio Devices, Release 2.0.
• FMT-2 refers to the Audio Data Formats specification, Release 2.0.

The USB-IF is a special interest group that maintains the Official USB Specification, test specifications and tools.

Audio formats

The driver supports the formats listed below. An alternate setting which specifies another format defined in FMT-2, or an unknown format, will be ignored.

Type I formats (FMT-2 2.3.1):

• PCM Format with 8..32 bits per sample (FMT-2 2.3.1.7.1)
• PCM8 Format (FMT-2 2.3.1.7.2)
• IEEE_FLOAT Format (FMT-2 2.3.1.7.3)

Type III formats (FMT-2 2.3.3 and A.2.3):

• IEC61937_AC-3
• IEC61937_MPEG-2_AAC_ADTS
• IEC61937_DTS-I
• IEC61937_DTS-II
• IEC61937_DTS-III
• TYPE_III_WMA

Feature descriptions

This section describes the features of the USB Audio 2.0 driver.

Audio function topology

The driver supports all entity types defined in ADC-2 3.13.

Each Terminal Entity must have a valid clock connection in compatible USB Audio 2.0 hardware. The clock path may optionally include Clock Multiplier and Clock Selector units and must end in a Clock Source Entity.

The driver supports one single clock source only. If a device implements multiple clock source entities and a clock selector, then the driver will use the clock source that is selected by default and will not modify the clock selector’s position.

A Processing Unit (ADC-2 3.13.9) with more than one input pin is not supported.

An Extension Unit (ADC-2 3.13.10) with more than one input pin is not supported.

Cyclic paths in the topology are not allowed.

Audio streaming

The driver supports the following endpoint synchronization types (USB-2 5.12.4.1):

• Asynchronous IN and OUT
• Synchronous IN and OUT
• Adaptive IN and OUT

For the asynchronous OUT case the driver supports explicit feedback only. A feedback endpoint must be implemented in the respective alternate setting of the AS interface. The driver does not support implicit feedback.

There is currently limited support for devices using a shared clock for multiple endpoints.

For the Adaptive IN case the driver does not support a feedforward endpoint. If such an endpoint is present in the alternate setting, it will be ignored. The driver handles the Adaptive IN stream in the same way as an Asynchronous IN stream.

The size of isochronous packets created by the device must be within the limits specified in FMT-2.0 section 2.3.1.1. This means that the deviation of actual packet size from nominal size must not exceed +/- one audio slot (audio slot = channel count samples).

Descriptors

An audio function must implement exactly one AudioControl Interface Descriptor (ADC-2 4.7) and one or more AudioStreaming Interface Descriptors (ADC-2 4.9). A function with an audio control interface but no streaming interface is not supported.

The driver supports all descriptor types defined in ADC-2, section 4. The following subsections provide comments on some specific descriptor types.

Class-Specific AS interface descriptor

For details on this specification, refer to ADC-2 4.9.2.

An AS interface descriptor must start with alternate setting zero with no endpoint (no bandwidth consumption) and further alternate settings must be specified in ascending order in compatible USB Audio 2.0 hardware.

An alternate setting with a format that is not supported by the driver will be ignored.

Each non-zero alternate setting must specify an isochronous data endpoint, and optionally a feedback endpoint. A non-zero alternate setting without any endpoint is not supported.

The bTerminalLink field must refer to a Terminal Entity in the topology and its value must be identical in all alternate settings of an AS interface.

The bFormatType field in the AS interface descriptor must be identical to bFormatType specified in the Format Type Descriptor (FMT-2 2.3.1.6).

For Type I formats, exactly one bit must be set to one in the bmFormats field of the AS interface descriptor. Otherwise, the format will be ignored by the driver.

To save bus bandwidth, one AS interface can implement multiple alternate settings with the same format (in terms of bNrChannels and AS Format Type Descriptor) but different wMaxPacketSize values in the isochronous data endpoint descriptor. For a given sample rate, the driver selects the alternate setting with the smallest wMaxPacketSize that can fulfill the data rate requirements.

Type I format type descriptor

For details on this specification, refer to FMT-2 2.3.1.6.

The following restrictions apply:

Class-Specific AS isochronous audio data endpoint descriptor

For details on this specification, refer to ADC-2 4.10.1.2.

The MaxPacketsOnly flag in the bmAttributes field is not supported and will be ignored.

The fields bmControls, bLockDelayUnits and wLockDelay will be ignored.

Class requests and interrupt data messages

The driver supports a subset of the control requests defined in ADC-2, section 5.2, and supports interrupt data messages (ADC-2 6.1) for some controls. The following table shows the subset that is implemented in the driver.

Additional information on the controls and requests is available in the following subsections.

Clock source entity

For details on this specification, refer to ADC-2 5.2.5.1.

At a minimum, a Clock Source Entity must implement Sampling Frequency Control GET RANGE and GET CUR requests (ADC-2 5.2.5.1.1) in compatible USB Audio 2.0 hardware.

The Sampling Frequency Control GET RANGE request returns a list of subranges (ADC-2 5.2.1). Each subrange describes a discrete frequency, or a frequency range. A discrete sampling frequency must be expressed by setting MIN and MAX fields to the respective frequency and RES to zero. Individual subranges must not overlap. If a subrange overlaps a previous one, it will be ignored by the driver.

A Clock Source Entity which implements one single fixed frequency only does not need to implement Sampling Frequency Control SET CUR. It implements GET CUR which returns the fixed frequency, and it implements GET RANGE which reports one single discrete frequency.

Clock selector entity

For details on this specification, refer to ADC-2 5.2.5.2

The USB Audio 2.0 driver does not support clock selection. The driver uses the Clock Source Entity which is selected by default and never issues a Clock Selector Control SET CUR request. The Clock Selector Control GET CUR request (ADC-2 5.2.5.2.1) must be implemented in compatible USB Audio 2.0 hardware.

Feature unit

For details on this specification, refer to ADC-2 5.2.5.7.

Halliburton Energy Services Usb Devices Driver Download For Windows 10 64-bit

The driver supports one single volume range only. If the Volume Control GET RANGE request returns more than one range, then subsequent ranges will be ignored.

The volume interval expressed by the MIN and MAX fields should be an integer multiple of the step size specified in the RES field.

If a feature unit implements single channel controls as well as a master control for Mute or Volume, then the driver uses the single channel controls and ignores the master control.

Additional Information for OEM and IHVs

OEMs and IHVs should test their existing and new devices against the supplied in-box driver.

There is not any specific partner customization that is associated with the in-box USB Audio 2.0 driver.

This INF file entry (provided in a update to Windows Release 1703), is used to identify that the in-box driver is a generic device driver.

The in-box driver registers for the following compatible IDs with usbaudio2.inf.

See the USB audio 2.0 specification for subclass types.

USB Audio 2.0 Devices with MIDI (subclass 0x03 above) will enumerate the MIDI function as a separate multi-function device with usbaudio.sys (USB Audio 1.0 driver) loaded.

The USB Audio 1.0 class driver registers this compatible ID with wdma_usb.inf.

And has these exclusions:

An arbitrary number of channels (greater than eight) are not supported in shared mode due to a limitation of the Windows audio stack.

IHV USB Audio 2.0 drivers and updates

For IHV provided third party driver USB Audio 2.0 drivers, those drivers will continue to be preferred for their devices over our in-box driver unless they update their driver to explicitly override this behavior and use the in-box driver.

Audio Jack Registry Descriptions

Starting in Windows 10 release 1703, IHVs that create USB Audio Class 2.0 devices having one or more jacks have the capability to describe these jacks to the in-box Audio Class 2.0 driver. The in-box driver uses the supplied jack information when handling the KSPROPERTY_JACK_DESCRIPTION for this device.

Jack information is stored in the registry in the device instance key (HW key).

The following describes the audio jack information settings in the registry:

<tid> = terminal ID (As defined in the descriptor)

<n> = Jack number (1 ~ n).

Convention for <tid> and <n> is:

• Base 10 (8, 9, 10 rather than 8, 9, a)
• No leading zeros
• n is 1-based (first jack is jack 1 rather than jack 0)

For example:

T1_NrJacks, T1_J2_ChannelMapping, T1_J2_ConnectorType

For additional audio jack information, see KSJACK_DESCRIPTION structure.

These registry values can be set in various ways:

• By using custom INFs which wrap the in-box INF for the purpose to set these values.

• Directly by the h/w device via a Microsoft OS Descriptors for USB devices (see example below). For more information about creating these descriptors, see Microsoft OS Descriptors for USB Devices.

Microsoft OS Descriptors for USB Example

The following Microsoft OS Descriptors for USB example contains the channel mapping and color for one jack. The example is for a non-composite device with single feature descriptor.

The IHV vendor should extend it to contain any other information for the jack description.

Troubleshooting

If the driver does not start, the system event log should be checked. The driver logs events which indicate the reason for the failure. Similarly, audio logs can be manually collected following the steps described in this blog entry. If the failure may indicate a driver problem, please report it using the Feedback Hub described below, and include the logs.

For information on how to read logs for the USB Audio 2.0 class driver using supplemental TMF files, see this blog entry. For general information on working with TMF files, see Displaying a Trace Log with a TMF File.

For information on 'Audio services not responding' error and USB audio device does not work in Windows 10 version 1703 see, USB Audio Not Playing

Feedback Hub

If you run into a problem with this driver, collect audio logs and then follow steps outlined in this blog entry to bring it to our attention via the Feedback Hub.

Driver development

This USB Audio 2.0 class driver was developed by Thesycon and is supported by Microsoft.

See also

How to determine whether a USB 3.0 device is operating at SuperSpeed?

USB 3.0 introduces a new operating speed called SuperSpeed. Compared to USB 2.0 bandwidth of 480 Mbps, SuperSpeed supports 5.0 Gbps making it 10 times faster than USB 2.0. USB 3.0 also supports lower operating speeds: high speed, full speed, and low speed. Along with increased bandwidth, USB 3.0 host controllers and devices come with the promise of compatibility. USB 3.0 controllers are required to work with all existing USB devices. The fact that current PCs ship with both USB 2.0 and USB 3.0 ports presents an interesting challenge: how should you determine whether a USB 3.0 device is indeed operating at SuperSpeed?

Here are some ways to determine the operating speed of the USB device. Each is explained in more detail in the respective sections below:

• Make sure that you have USB 3.0-capable hardware

• View device information in Device Manager

• Use USBView to view the bus speed

• Follow the troubleshooting steps listed below

Halliburton Energy Services Usb Devices Driver Download For Windows 10 64

Make sure that you have USB 3.0-capable hardware

Typically, newer PCs with USB 3.0 support have both USB 3.0 and USB 2.0 controllers, and both those ports are exposed. The receptacles on USB 3.0 ports are usually blue to distinguish from the receptacles on USB 2.0 ports, which are black. So, if the PC has a blue port, that is a good indication of USB 3.0 support. Note this is not a requirement of the official USB specification, rather a convention adopted by some PC makers.

Figure 1 shows a typical USB 2.0 port on the right hand side with a black receptacle, and a typical USB 3.0 port on the left side, with a blue receptacle.

Figure 1. USB 3.0 port with a blue receptacle, USB 2.0 port with a black receptacle.

Attributed to Bubba73 at English Wikipedia, via Wikimedia Commons

Figure 2 shows the USB 2.0 logo.

Figure 2. USB 2.0 logo

Figure 3 shows the USB 3.0 logo.

Figure 3. USB 3.0 logo

You should also look for the logo on USB 3.0 devices and cables.

Figure 4 shows the USB 3.0 logo on the connector of a USB 3.0 cable.

Figure 4 USB 3.0 logo on USB 3.0 cable.

By smial (Own work), GFDL 1.2, via Wikimedia Commons

View device information in Device Manager

Next, confirm that Windows enumerated the host controller as a USB 3.0 controller. To confirm that, open Device Manager and locate the controller under the Universal Serial Bus controllers node. If Windows recognized it as a USB 3.0 controller, USB 3.0 eXtensible Host Controller is appended to the device description as shown in Figure 5.

Figure 5. USB 3.0 eXtensible Host Controller in Device Manager

Use USBTreeView to view device information about the bus speed

USBView is a tool from Microsoft. More information on the tool can be found in the USBView article on Microsoft's website.

USBTreeView is also available for download directly from the following link. USBTreeView in this release has been updated to display SuperSpeed information.

Figure 6 shows a USB 3.0 device operating at SuperSpeed in USBView.

Figure 6. USBView – Message for a USB 3.0 device that is operating at SuperSpeed

Check Capture OEM

When a USB 3.0 camera is connected to a USB 2.0 port, Capture OEM will display a 'WARNING: REDUCED LINK SPEED' error, as seen in the following screenshot.

If you see this error, please confirm that your computer is connected to a USB 3.0 port. Next, review the troubleshooting steps below.

Troubleshooting

Here are a few things to try if you find that your USB 3.0 device is capable of operating at SuperSpeed but is operating a lower bus speed:

Halliburton Energy Services Usb Devices Driver Download For Windows 10 Free

• Make sure that you do not have a USB 2.0 hub between the device and the PC. That is because USB 3.0 devices that are attached to a USB 2.0 hub can only operate at high speed. In this case, either switch to a USB 3.0 hub or attach the device directly to the USB 3.0 port on the PC.

• Ensure that the USB 3.0 hub that your device is attached to appears correctly in Device Manager. For certain unsupported USB 3.0 hubs, Windows may disable the SuperSpeed portion of the hub and report it as “Non Functional” in Device Manager.

Figure 7 shows a non-functional hub in Device Manager.

Halliburton Energy Services Usb Devices Driver Download For Windows 10 Windows 10

Figure 7. SuperSpeed USB Hub is not functional

• Make sure that the cable that is used to connect the device is a USB 3.0 cable. It is also possible that the USB 3.0 cable has signal integrity issues. In that case, the device might switch to high speed. If that happens, you must change the USB 3.0 cable.

• Update the firmware for the USB 3.0 device by obtaining the latest version from the manufacturer site. Some USB 3.0 device manufacturers release fixes, for bugs found in the device, as firmware updates.

• Update the firmware for the USB 3.0 controller by obtaining the latest version from the manufacturer site. Some USB 3.0 controller manufacturers release fixes, for bugs found in the controller, as firmware updates.

• Update the BIOS for your system by obtaining the latest version from the manufacturer. On some motherboards, the BIOS can incorrectly route a device that is connected to a USB 3.0 controller to a USB 2.0 controller. That incorrect routing allows the USB 3.0 device to operate at high speed but not at SuperSpeed. A BIOS update might fix such a problem.