Introduction In the world of embedded systems, automotive diagnostics, and industrial automation, the Controller Area Network (CAN) bus remains the gold standard for robust communication. To interface a PC or laptop with a CAN network, USB-to-CAN adapters are essential tools. Among the various manufacturers in this space, ITEK has carved out a reputation for producing reliable, cost-effective USB CAN interfaces.
| Error / Symptom | Likely Cause | Solution | |----------------|--------------|----------| | | ITEK driver lacks Microsoft WHQL signature. | Reboot into Disable Driver Signature Enforcement (Shift + Restart → Troubleshoot → Advanced → Startup Settings). Or install via pnputil with admin override. | | Device shows “Code 10” – Cannot start | Conflicting driver (e.g., Windows assigned an FTDI serial driver). | In Device Manager, right-click → Uninstall device → Check “Delete driver software” → Reinstall ITEK driver. | | CAN bus remains in “Bus-Off” state | Baud rate mismatch; other nodes are transmitting, but your adapter is not syncing. | Confirm bus baud rate with an oscilloscope. Try listen-only mode first. Ensure termination resistors (only two per bus). | | No frames received (but can transmit) | Listen-only mode enabled. | Disable listen-only in config utility. | | High latency / dropped frames | USB polling interval too slow or CPU overloaded. | Reduce CAN baud rate for testing. Use a dedicated USB controller port (not a hub). Increase USB buffer size in driver settings (if configurable). | | Linux module fails to compile | Kernel headers missing or API changes. | Run sudo apt install linux-headers-$(uname -r) . Check git repo for kernel version compatibility. | Advanced Diagnostic: Using Wireshark with USB Capture If the driver seems dead, capture USB traffic: itek usb can driver
A: Windows 11 enforces stricter driver signing. You may need to run Windows 11 in test mode ( bcdedit /set testsigning on ) or request an updated driver from ITEK. Introduction In the world of embedded systems, automotive