WEB USB Proffieboard Workbench Interface on Proffieboard 3.7/2.2s not working (solved 4/22 by Bobby Susenbach)!

ProffieOS
41

Of course, if the chip is a fake, it will have the “correct” markings.

1 Like
42

ah sure.
Well FWIW all the ones I have say 433

43

Yeah, all 433 for me as well.

44

Bump WEB USB Inteprface freezes once you select “usb” connection button on Proffieboard workbench.

I initially noticed this on my Proffieboard 3.7, but since, I have now run across the same issue on 3 Proffieboards from Electronics 1,2,3. I do not have this issue on any KR Sabers Proffieboard 2.2s.

I am using Windows 10 and Chrome

45

First step: Check if these boards are using the same drivers or not. (They should, but windows might be be messing it up somehow.)

Second step, use the chrome javascript console and see if you get the same error on all the boards that aren’t working.

Third step: Pick two 2.2 boards, one that works and one that doesn’t, and try installing exactly the same configuration on them, and clone the SD card as well. Once the installations are identical, do we still see a difference in webusb? If we do’ then the problem cannot be the software.

46

Time clock is ticking away on me, heading to Disneyworld Galaxy’s Edge in AM, but I’ll see what I can accomplish tonight.

Bad Proffie 2.2 (won’t connect to webusb) driver: libwdi___6.1.7600.16385___USB\MS_COMP_WINUSB(libwdi auto generated)

Good Proffie 2.2 (connects to webusb) driver:
libwdi___6.1.7600.16385___USB\MS_COMP_WINUSB(libwdi auto generated)

So both have the same driver. I think I’m running out of time to create mirror configs and mirror SD’s to test; however, I can tell you that I have done that on one of my sabers, and the KR Proffie connected, while the E123 Proffie did not.

I am assuming this is a hardware issue. When the E123 boards arrive, and I plug them into my PC, they demand I insert an SD Card. I assumed this was because they programmed them for mass storage at the factory.

KR Sabers Proffies never called for an SD card when plugged in initially. The E123 boards look slightly different, but to my untrained eyes, components are all the same, unless the processor is a fake.

My only other thought is that perhaps Chrome is doing something screwy on Windows only, because we also have the issue of my 3.7 not connecting on WEBUSB for me; however, it did for everyone else that I know of. NoSloppy’s worked, yours worked, I didn’t hear any other feedback on the 3.7s. The only thing that makes me suspect something screwy on Chrome is this fact.

Here is the readout from Chrome when I try to connect:

sw.js:58 [Service Worker] Fetch https://profezzorn.github.io/lightsaber-web-bluetooth/Starjedi.ttf
app.html:356 Service Worker Registered
app.html:1530 VERSION: $Id: 49552f7dc621c04225bac19d2abb45cd82131926 $
app.html:1531 10/28/2021 01:09:20
sw.js:58 [Service Worker] Fetch https://profezzorn.github.io/lightsaber-web-bluetooth/manifest.json
sw.js:58 [Service Worker] Fetch https://profezzorn.github.io/favicon.ico
/favicon.ico:1          Failed to load resource: the server responded with a status of 404 ()
2sw.js:58 [Service Worker] Fetch https://profezzorn.github.io/lightsaber-web-bluetooth/icon-256.png
app.html:1307 USBAlternateInterface
app.html:1307 USBAlternateInterface
app.html:1307 USBAlternateInterface
app.html:1322 OUT EP 5 IN EP 5
app.html:1346 Uncaught (in promise) DOMException: Unable to claim interface.
sw.js:58 [Service Worker] Fetch https://profezzorn.github.io/lightsaber-web-bluetooth/app.html
sw.js:58 [Service Worker] Fetch https://profezzorn.github.io/lightsaber-web-bluetooth/manifest.json
47

I believe i was having the same problem. I was using 2 different KR V2 boards, one of which I had successfully connected to WebUSB and edited saber with before. I did the following and they both connect/ function properly with WebUSB now.

  1. Disconnect cord
  2. Goto settings (windows), Locate your devices (mine was System>Bluetooth and other Devices.)
  3. Unpair/ remove device (proffie board).
  4. Open WebUSB website, selectUSB.
  5. Reconnect cord, Select proffie, select connect…
3 Likes
48

Bobby, and @profezzorn

This fixed my Proffieboard 3.7 connection. I am now connected to WEB USB on Proffieboard 3.7!!! I’m going to try this with my other boards that won’t connect via WEB USB.

3 Likes
49

Yep, that fixed my other Proffieboard 2.2 as well! Sounds like a local issue on Windows 10 system.

2 Likes
50

I have even tried all my E 1,2,3 Proffieboards, and they are all now connecting via WEB USB as well!!! Now I don’t have to swap this sound board in this build!!! Thank you Bobby!!!

3 Likes
51

I was using the workbench for the first time today…as it did the same disconnecting issue after editing. I dont know if this was already talked about but i had the settings for my v2…serial,mass storage, web usb selected. NOTE…I changed my selection to just serial, web usb… and it stayed connected and i was able to edit , save, and get out…and back in.
But i was wondering if the only way to disconnect from the workbench is to pull the plug,???.. would there be a integration of connect/disconnect feature on the app? If i missed it i apologize for not seeing it. But just to say it was cool to use and figure out and it truly worked great! Thanks.

1 Like
52

You can also close the tab/browser/app.

53

Understood.