From 8b10429738bb1100e7b5a181291f2b3d3694a8eb Mon Sep 17 00:00:00 2001
From: Richard Parsons <503426+Capo01@users.noreply.github.com>
Date: Tue, 10 Dec 2019 15:45:23 +1100
Subject: [PATCH] Included that Zadig has native and CDC interfaces listed

---
 docs/troubleshooting.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/troubleshooting.md b/docs/troubleshooting.md
index 6ba3752e..bd02b737 100644
--- a/docs/troubleshooting.md
+++ b/docs/troubleshooting.md
@@ -113,7 +113,7 @@ You can also try increasing `<axis>.controller.config.vel_limit_tolerance`. The
  * **Linux**: Type `lsusb` to list all USB devices. Verify that your ODrive is listed.
  * **Linux**: Make sure you [set up your udev rules](getting-started#downloading-and-installing-tools) correctly.
  * **Windows**: Right-click on the start menu and open "Device Manager". Verify that your ODrive is listed.
- * **Windows**: Use the [Zadig utility](http://zadig.akeo.ie/) to verify the driver is set to `libusb-win32`.
+ * **Windows**: Use the [Zadig utility](http://zadig.akeo.ie/) to verify the driver is set to `libusb-win32`. Note that there are two options listed in Zadig for Odrive: `ODrive 3.x Native Interface (Interface 2)` and `ODrive 3.x CDC Interface (Interface 0)`. Only the native interface should have `libusb-win32` while the CDC interface should use `WinUSB`.
  * Ensure that no other ODrive program is running
  * Run `odrivetools` with the `--verbose` option.
  * Run `PYUSB_DEBUG=debug odrivetools` to get even more log output.