Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FTDuino can not connect using WebUSB, Scratch nor Brickly #11

Closed
KKempen opened this issue Dec 26, 2019 · 2 comments
Closed

FTDuino can not connect using WebUSB, Scratch nor Brickly #11

KKempen opened this issue Dec 26, 2019 · 2 comments

Comments

@KKempen
Copy link

KKempen commented Dec 26, 2019

Hi, just got the FTDuino in the mail and wrote the first few programs, now I wanted to use Scratch so I downloaded the IOServer software as described in the manual.

On my Win10 machine when I try to connect using the online Scratch editor nothing shows up in the popup window;
Screenshot
When i do the same thing on my linux machine (Debian 10 Mate on a i386 architecture) usin' Chromium FTDuino shows up in de selection window, however when I try to connect. An error is returned: "Connection error: NotFoundError: The interface number provided is not supported by the device in its current configuration."
Can you please comment on this behaviour?

@harbaum
Copy link
Owner

harbaum commented Apr 17, 2020

Regarding the Windows issue: WebUSB can be rather tricky under Windows in general as seen e.g. here: WICG/webusb#143

There are two "popular" ways to deal with this. Sometimes the following hint helps:

Enabling new usb backend for Windows on Chrome flag solved the problem for us, chrome://flags/#new-usb-backend

And sometimes (more often) this one:

Try to install WinUSB drivers manually with Zadig - https://zadig.akeo.ie/

@harbaum
Copy link
Owner

harbaum commented Apr 17, 2020

Regarding your Linux issue: I have never seen/heard that. The error message is not very detailed. Two things come to mind:

a) Is the correct sketch installed with the Board set to "ftduino (webusb)"?

b) The Udev rules have been setup correctly? Especially this one:
ATTRS{idVendor}=="1c40" ATTRS{idProduct}=="0538", ENV{ID_MM_DEVICE_IGNORE}="1", MODE="0666"

@harbaum harbaum closed this as completed Jan 28, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants