DeviceOK
SearchDevice checks
Home / Checks / USB & Serial Hardware Check
Makers, developers, barcode scanners, serial adapters, controllers and microcontrollers

USB & Serial Hardware Check

Check whether this browser supports the hardware API and whether a user-selected HID, USB, or serial device can be opened safely.

Inspection principle

WebHID, WebUSB, Web Serial and Web Bluetooth expose only devices and interfaces the browser/platform allows. 'Not listed' can mean unsupported API, protected interface, driver ownership or device mode—not broken hardware.

Progress0 of 8 checks recorded
Run next live test ↗

Run the browser-visible checks, then record the physical/native checks below. Progress stays in this browser unless you deliberately copy the fragment share link.

Live evidence

Browser-visible checks

1
Browser hardware API supportSee which hardware-facing browser capabilities are available before trying camera, gamepad, MIDI, USB, HID, serial, or Bluetooth diagnostics.
Run test ↗
2
HID deviceRequest a compatible HID device in browsers that support WebHID and display its browser-exposed product and vendor identifiers.
Run test ↗
3
WebUSB deviceRequest a compatible USB device through WebUSB and display the browser-exposed manufacturer, product, vendor, and product IDs.
Run test ↗
4
Serial portChoose a serial port, open it at a safe test baud rate, and close it to verify browser-level serial access.
Run test ↗
5
Bluetooth LE deviceOpen the browser Bluetooth chooser for compatible Bluetooth Low Energy devices in supported environments.
Run test ↗
Outside the browser

Physical & native checks

These close the blind spots a website cannot inspect.

1
Known-good data cable

Use a cable known to carry data, not just power, and avoid adapters while isolating the problem.

Why it matters: Cable capability is a common hidden variable.
2
Device operating/boot mode

Confirm the peripheral is in the documented HID/serial/bootloader/BLE mode required for the connection.

Why it matters: Many devices expose different interfaces in different modes.
3
OS device enumeration

Check Device Manager/System Information or the maker's tool to see whether the OS sees the device.

Why it matters: OS enumeration separates browser API limits from a lower-level connection failure.
Stop / escalate

Conditions that deserve caution

  • Unknown voltage/pinout on exposed serial/board connections.
  • Firmware flashing or destructive commands are proposed without a verified recovery path.
Decision rule

How to use the evidence

First prove physical/OS enumeration, then browser API support/permission, then application protocol. Do not call a device dead because one Web API cannot claim it.

0 passed0 need attention0 skipped