Simple Port Devices Driver

Posted By admin On 12/10/21
  1. Simple Port Devices Driver
  2. Simple Port Devices Drivers
  3. Simple Port Devices Driver Updater
  4. Simple Port Devices Driver License Test
Calman Display Calibration Software directly controls many hardware devices, including light meters, pattern sources, LUT processors, and display devices. The control interface to these devices may be USB, RS-232 serial, or wired or wireless network IP connections.

If the hardware device has a USB interface connection and is connected to a USB computer port, the computer needs to have a device driver installed (unless it is a USB HID device; see below). The device driver tells the computer how to properly handle data communications between the computer and the hardware USB device.

Normally it happens after you upgrade the system from Windows 7, 8 to Windows 10, all the devices and drivers are installed correctly, but maybe this one cannot installed. So try to download and update Intel management engine driver for Windows 10, 8, 7 to fix PCI simple communications controllers device driver missing problem. Apart from updating your PCI Drivers, installing a Driver Update Tool gives: Up to 3 times faster internet connection and download speeds; Better PC performance for games and audio applications; Smooth-running of all your PC devices such as printers, scanners etc. Better all-round performance of your PC due to automatic driver updates which will. After 3 days of digging, I found the fix for the OptiPlex 790 and 990 PCI Serial Port Driver issue which shows as a yellow triangle under Device Manager. This trouble occurs when you upgrade from Win 7 which is fully-supported by Dell on these machines, to the unsupported Win 8 or Win 10. Download other device drivers or install DriverPack Solution software for driver scan and update. System must have pci simple communications controller driver installed correctly. It displayed in Device Manager list with Yellow Mark in case driver not install. To find it you need to go Device Manager Other devices pci simple communications controller. When you install the driver then you don’t see yellow mark again.

USB HID Devices

The USB Human Interface Device (HID) class is a specification for computer peripherals such as keyboards, mice, and game controllers. A computer doesn’t require a separate device driver for USB HID devices because they are recognized and handled directly by the Windows operating system. Other devices that comply with the USB HID spec are also recognized automatically by a computer and don’t require a separate device driver.

USB HID devices that are supported by Calman include the SpectraCal C6 Colorimeter and the X-Rite i1Display light meters. When one of these meters is plugged into a computer, Windows automatically connects to the meter without requiring an external device driver.

Driver

Network Control Devices

If the hardware device is connected to a computer via a wired or wireless IP network connection, the computer does not require a device driver for that device.

Serial Control Devices

If the hardware device has an RS-232 serial connection and is directly connected to a computer serial port, the computer does not require a device driver for that device.

However, since most computers no longer provide a serial port, a serial hardware device will usually be connected to a computer via a USB to serial converter. In that case, the computer needs to have a device driver installed to properly communicate through the USB to serial converter.

USB to Serial Converters

If a hardware device has an RS-232 serial connection, a USB to serial converter is usually used to connect the serial device to a computer’s USB port.

Simple port devices drivers

The computer sends data to and receives data from the USB port on the converter. The converter translates that data, through its serial port, to a serial hardware device. The computer requires a device driver to tell it how to properly handle data communications with the USB port on the USB to serial converter.

A data buffer is included within some USB to serial converters. The data buffer improves the reliability of a device interface at high data rates. Many USB to serial converters without a data buffer do not provide a reliable interface between Calman and hardware devices. The USB to serial converters produced by FTDI include a data buffer. The FTDI converters have been tested with all hardware devices supported by Calman and have been certified to provide a reliable interface in all cases.

For more information, see the Calman setup guide for the FTDI USB to serial converters.

Obtaining Device Drivers

Device drivers can be obtained in a number of ways.

The required device driver can often be obtained from the hardware device manufacturer. Device manufacturers may package a device driver with the device or they may provide a device driver download on their device support page.

In cases where the manufacturer supplies operating software with the hardware device, the device driver may be installed as part of the manufacturer’s operating software installation.

If you will only ever connect one or two USB devices to a Calman computer, you may wish to obtain the device driver for your device(s) directly from the device manufacturer.

Simple Port Devices Driver

For convenience, SpectraCal provides a Device Driver Pack that includes device drivers for most of the hardware devices supported by Calman.

To ensure that you have the proper driver, or if you will be connecting a number of different USB devices to Calman, you may wish to download the Calman Device Driver Pack from the Calman Download page to install all supported device drivers on the Calman computer.

Installing Device Drivers

Installing the SpectraCal Device Driver Pack on a Calman computer automatically installs and registers the included device drivers for Calman supported hardware. Installing a driver that you obtain directly from a device manufacturer also automatically registers the device driver in Windows.

When a hardware device is then connected to the Calman for the first time, the proper device driver is automatically associated with the device.

Unsigned Device Drivers

Many currently available device drivers have not been tested and certified by Microsoft. These drivers are referred to as unsigned device drivers. Some of the drivers provided in the SpectraCal Device Driver Pack are unsigned.

Windows 7 or Earlier

If you are installing an unsigned device driver in Windows 7 or earlier, a Windows Security dialog will open to give us a choice of whether or not to install an unsigned device driver. If you feel comfortable with the source of your device driver file, you will probably want to select the Install Anyway option.

Windows 8.0 or Later

If you are installing an unsigned device driver in Windows 8.0 or later, you will need to follow one of the special driver installation procedures below.

  • Windows 8.0
  1. Open Settings (move your mouse to the top or bottom right corner of the screen and wait for the charm bar to appear, then click the Gear icon)
  2. Click Change PC Settings
  3. Click General
  4. Scroll down and click Restart Now under Advanced Startup
  5. Click Troubleshoot
  6. Click Advanced Options
  7. Click Windows Startup Settings
  8. Click Restart
  9. When the computer restarts, select Disable Driver Signature Enforcement from the list.
  10. You can now load the unsigned driver(s). After restarting the computer, any drivers that you installed will continue to function.
Simple Port Devices Driver

Note: This may need to be repeated each time you update your graphics driver.

  • Windows 8.1 and Windows 10
  1. While holding down the Shift key, go to SettingsPowerRestart
  2. On shutdown, you will be presented a list of Options. Select Troubleshoot
  3. On the Troubleshoot menu, select Advanced Options
  4. On Advanced Options, select Startup Settings
  5. Click Restart - Machine will reboot.
  6. This will bring you to Startup Settings. Select 7 - Disable driver signature enforcement

When Windows starts, Driver Signature Enforcement is disabled.

You can now load the unsigned driver(s).

After a normal reboot, Driver Signature Enforcement will re-enable. Any drivers that were installed while it was disabled will continue to function.

Windows Device Manager

When a USB-controlled hardware device is connected to a computer, Windows first needs to recognize the device and properly connect to it. The proper device driver needs to be registered with Windows to support that device connection. Only if Windows is properly connected to a device, will Calman also then be able to connect to the device.

Windows Device Manager is the important software utility for managing Windows connections to the external hardware devices that we are then going to want to connect to Calman. Device Manager allows us to check a device connected to Windows and manage the device’s driver registration.

Note: When Calman is unable to connect to a USB-controlled hardware device (or a USB to serial converter), Device Manager is one of the first places to check.

Any device that is connected to a computer’s USB port will create a device listing in Device Manager. The device will either be listed under an existing device type (e.g. “Ports (COM & LPT)”, or a new Device Type will appear (e.g. “X-Rite Devices”)

Under its particular Device Type, the device will be given a Device Description (e.g. “USB Serial Port (COM6),” “ColorMunki Smile”).

Alternately connecting and disconnecting the USB plug for the device in question may help to identify which device listing in Device Manager corresponds to the hardware device in question.

Virtual COM Port Drivers

Some USB devices use a Virtual COM port (VCP) driver, which causes the USB device to appear as an additional COM port available to the PC (listed in Windows Device Manager, under the Ports (COM & LPT) type, as a “USB Serial Port (COMx)” device.

Calman software can then access the USB device as it would a standard COM port. Note the designated COM port number in Device Manager (COMx), as you will need to select that port number on the Calman device connect dialog.

Normal Device Manager Listings

Following are many of the popular hardware devices that are supported by Calman that require a Windows device driver to support their USB connection. Following each device name is the Device Type and Device Description, as they will be listed in Device Manager when the proper device driver is installed.

If your device is listed some other way in Device Manager, the device driver is not installed properly.

  • AV Foundry VideoForge Classic
    • Network Adapters > RNDIS Gadget
  • EIZO Monitors
    • Human Interface Devices >
  • Fujifilm IS-mini
    • Universal Serial Bus Controllers > IS-mini
  • FTDI USB to Serial Converter
    • Universal Serial Bus Controllers > USB Serial Converter
  • HDfury Integral 4K60
    • Universal Serial Bus Controllers > USBXpress Device
  • HP Z27x
    • Libusb-win32 devices > HP Z27x USB
  • Klein K10
    • Universal Serial Bus Controllers > USB Serial Converter
      (meter has internal FTDI converter)
  • Lumagen Radiance Pro
    • Ports (COM & LPT) > USB Serial Port (COMx)
  • Murideo SIX-G
    • Ports (COM & LPT) > USB Serial Port (COMx)
  • Quantum Data 780-series generators
    • Ports (COM & LPT) > USB Serial Port (COMx)
  • SpectraCal C3 Colorimeter
    • X-Rite Devices > ColorMunki Smile
  • SpectraCal C6 Colorimeter
    • Human Interface Devices > USB Input Device
  • SpectraCal ColorBox/eeColor
    • Universal Serial Bus Controllers > USB Serial Converter A, USB Serial Converter B
      (unit has internal FTDI converters)
  • SpectraCal VideoForge PRO
    • Ports (COM & LPT) > USB Serial Port (COMx)
  • UPRtek MK550T Spectroradiometer
    • Human Interface Devices > USB Input Device
  • X-Rite i1Pro 2
    • X-Rite Devices > i1 Pro
  • X-Rite i1Display
    • Human Interface Devices > USB Input Device

Updating a Device Driver

If a hardware device was connected to the computer before its correct device driver was installed, Windows may have registered an incorrect device driver to the device. In that case, you may need to uninstall the incorrect driver (in Windows Device Manager), then reconnect the device to the correct device driver.

Follow these steps to update a device driver:
  1. Identify the device listing in Windows Device Manager that corresponds to the hardware device of interest. Alternately connect and disconnect the device USB connection as you are watching the Device Manager screen to identify the listing.
  2. Right-click on the device description and select Update driver from the pop-up menu.
  3. When asked how you want to search for drivers, select Browse my computer for driver software
  4. On the following screen, click the Browse button.
  5. Navigate to the drive folder containing the correct driver for the hardware device. For the Device Driver Pack, that is:
    C:Program Files (x86)SpectraCalDrivers (corresponding device folder)
  6. Click the OK/Next button to update the driver.
-->

Simple I/O plug-ins are extensions to the Windows Driver Test Framework (WDTF) that implement generic device-specific I/O functionality. If a plug-in exists for the type of device being tested, the Device Fundamental tests use the WDTF Simple I/O interfaces to test I/O.

This topic lists the device types that have Simple I/O plug-ins and indicates if there are specific requirements for testing the device. These are the same requirements you need to follow when you use the Windows Hardware Lab Kit (Windows HLK). The topic also offers ideas to troubleshoot and triage test failures.

If your device type is not listed, you can create one, see How to customize I/O for your device using the WDTF Simple I/O Action Plug-in

Driver

For a list of Device Fundamental tests that have specific requirements, see Device Fundamental tests that have specific device configuration requirements

Audio

Requirements

  • The device must have at least one render type endpoint connected (speakers, headphones, or the like).

  • If the targeted audio device has HDMI video and audio output capability, to perform audio tests, the device must be connected to an HDMI audio capable device such as an HDMI Monitor or an A/V Receiver.

Type of I/O plug-in performs (audio)

  • Plays a sine tune on render type endpoint. Captures audio on a capture type endpoint.

How to triage test failures

  • Look at failing HRESULT to perform initial triage.
  • If test is not responding, use the kernel debugger on the target computer to narrow down the root-cause.
  • Run traces:
    • Start kernel traces:
  • Start audio traces:
  • Run tests.
  • Stop traces:
  • Merge traces:
  • View the merged trace file with Xperf (xperfview).

Bluetooth

Bluetooth requirements

  • No special requirements.

Type of I/O plug-in performs (Bluetooth)

  • Uses BluetoothFindFirstDevice function to find a Bluetooth device.

CDROM

CDROM requirements

  • Drive letter is assigned.
  • Media is present in the device.
  • Files are present on the media inserted.

Type of I/O plug-in performs (CDROM)

  • Finds files on the CD-ROM and performs read operation using the Win32 ReadFile API.

How to triage test failures (CDROM)

  • On the test computer, navigate to the CD/DVD drive in question and confirm you can access the contents of the drives.
  • The CD-Rom Simple I/O plug-in searches for files on CD/DVD to use to perform reads from. Ensure the CD/DVD has files encoded on disk.
  • This Simple I/O plug uses the Win32 CreateFile, WriteFile, ReadFile functions. Error returned are most likely Win32 error codes from these APIs.

Disk

Disk requirements

  • Disk has at least one associated volume Drive letter is assigned.

Type of I/O plug-in performs (Disk)

  • Uses the Simple I/O plug-in for Volumes.

Display

Display requirements

  • No special requirements for testing.

Type of I/O plug-in performs (Display)

  • Uses D3DX APIs to exercise graphics adapter.

How to triage test failures (Display)

  • Look through the test logs, which report failures from the APIs that are used.

GPS devices (and GPS devices in systems)

Requirements (GPS)

  • The device must be tested in a location with proper GPS signals.

Type of I/O plug-in performs (GPS)

  • Uses the I/O plug-in for Sensors.

LAN

Requirements (LAN)

  • Device has an IPv6 address.

  • Device has an IPv6 gateway address (otherwise the WDTFREMOTESYSTEM parameter should be passed to the test with an IPv6 address that the test NIC can ping).

  • The network operation status of the device is IfOperStatusUp.

  • Network device is not a WWAN or a WLAN device.

Type of I/O plug-in performs (LAN)

  • Pings IPv6 network gateway address.

How to triage test failures (LAN)

  • Confirm that there is an existing IP address.
  • Confirm that there is a gateway IPv6 IP Address.
  • Confirm the IP gateway address manually (use ping.exe).

Mobile broadband

Requirements (Mobile broadband)

  • No special requirements for testing.

Type of I/O plug-in performs (Mobile broadband)

  • Uses IMbnInterface interface and calls GetHomeProvider, IMbnInterface::GetInterfaceCapability method, and IMbnInterface::GetReadyState method APIs to exercise the device.

How to triage test failures (Mobile broadband)

  • The MobileBroadbandPlugin has limited areas it can fail.

    • 'MobileBroadbandPlugin: Getting all Mobile Broadband interfaces returned failure.'
    • 'MobileBroadbandPlugin: Getting the interface returned failure.'
    • 'MobileBroadbandPlugin: Getting the DeviceId returned.'
    • 'MobileBroadbandPlugin: Getting the interface capabilities returned failure'
    • 'MobileBroadbandPlugin: Getting the ReadyState returned failure.'
  • The best place to investigate the failure is starting from the device and determine if it was unable to indicate Ready Information or Device Capabilities. To debug further OS Trace file need to be collected.

    • Run the command: netsh trace start wwan_dbg
    • Reproduce the issue.
    • Run the command: netsh trace stop

Portable devices

Requirements (Portable devices)

  • Device has a storage component where folders and files can be created.

Type of I/O plug-in performs (Portable devices)

  • Reads and writes a file to the storage component on WPD device using WPD APIs.

Smart card readers

Requirements (Smart card readers)

  • Device has Athena T0 test card inserted.

Type of I/O plug-in performs (Smart card readers)

  • Reads and writes data to Athena T0 card inserted in the card reader.

Sensors

Requirements (Sensors)

  • The GPS device must be tested in a location with proper GPS signals.

Volume

Requirements (Volume)

  • Volume has a drive letter assigned.
  • Volume has 5MB of free space.
  • Volume is not write-protected.
  • Media is present in the device.

Type of I/O plug-in performs (Volume)

  • Creates a directory called WDTF_Volume_IO and creates a file called SimpleIO.tmp. The I/O is performed by calling ReadFile and WriteFile APIs to this file.

How to triage test failures (Volume)

  • On the test computer, navigate to the drive in question and confirm you can access the contents of the drive.
  • Attempt to save a file to the drive. Ensure you can save and access it readily.
  • This Simple I/O plug uses the Win32 CreateFile, WriteFile, ReadFile functions. Error returned are most likely Win32 error codes from these APIs.

Webcam

Requirements (Webcam)

  • No special requirements for testing.

    Note

    The Simple I/O plug-in for webcam devices has a dependency on the MFPlat.dll file, which is not available on versions of Windows that do not include Media Player and related technologies, for example Windows 7 N or Windows 7 KN. On these version of Windows, the Media Feature Pack must be installed. The Media Feature Pack is available for download. For more information, see KB Article 968211.

Driver

Type of I/O plug-in performs (Webcam)

  • Uses Media Foundation interfaces to capture video.

WLAN

Requirements (WLAN)

  • See Troubleshooting WLAN SimpleIO plugin failures that are logged by Device Fundamentals tests in the HCK documentation.

Type of I/O plug-in performs (WLAN)

  • See Troubleshooting WLAN SimpleIO plugin failures that are logged by Device Fundamentals tests in the HCK documentation.

How to triage test failures (WLAN)

  • See Troubleshooting WLAN SimpleIO plugin failures that are logged by Device Fundamentals tests in the HCK documentation.

USB Controller and HUB with Mutt

Requirements (USB)

  • No special requirements for testing.

    Device has a Symbolic link.

Type of I/O plug-in performs (USB)

Simple Port Devices Drivers

  • USB transfer tests using the Microsoft USB Test Tool (MUTT) device. Transfer types covered are control, bulk, isochronous, interrupt, and streams (only if SuperMUTT is plugged into USB 3.0 controller)

How to triage test failures (USB)

  • Start by examining the messages in the test log files.
  • Further investigate by enabling Event Tracing for Windows (ETW) on the USB 2.0 and USB 3.0 stacks.
    • For USB 2.0, see Microsoft Windows USB Core Team Blog - ETW in the Windows 7 USB core stack
    • For USB 3.0, see the Microsoft Windows USB Core Team Blog - How to Capture and Read USB ETW Traces in Windows 8

Device Fundamental tests that have specific device configuration requirements

Simple Port Devices Driver Updater

Before you run the following Device Fundamental tests, the devices on the test computer must be configured according to the requirements described in this topic for the specific device types.

  • PCI Root Port Surprise Remove Test (PCI devices only)
  • Device Path Exerciser Test (Certification)
  • Sleep and PNP (disable and enable) with IO Before and After (Certification)
  • Plug and Play Driver Test (Certification)
  • Concurrent Hardware And Operating System (CHAOS) Test (Certification)
  • Reinstall with IO Before and After (Certification)
  • Device Install Check For File System Consistency (Certification)
  • Device Install Check For Other Device Stability (Certification)

Simple Port Devices Driver License Test

Related topics