I just upgraded to os 6.9 and after following the tutorials to update config to a 6.x file its working but i cannot get webusb to stay connected to the proffie. I seems to drop the connection while im editing the settings. I am using usb not ble and have tried a few different cables just to make sure its not a connector issue.
I can program and upload with arduino ide no problems. just keeps dropping in webusb app. I am using the latest version of chrome.
There is no 6.9. Maybe you meant 6.6? (or 5.9?)
What OS is your computer using?
What browser are you you using?
Dropping the connection is a problem that other people have reported, but I’ve never been able to figure out what’s causing it, so I’m motivated to figure it out if you’re williing to work with me on it.
You are correct 6.6 it was a typo. Im using windows 10 home edition version 21h2 and os build 19044.1586. I have been using chrome Version 99.0.4844.74. I was thinking that i might try another browser that is webusb enabled. We have to use chrome at work and are usually having problems with it on a regular basis. Any suggestions on other browsers and i will check them and see what i can come up with.
Ans as i checked the version of chrome it just updated on me, i can check the new version later this evening and see if anything changed.
Anything else you need let me know. I like the webusb so much better than the old code reflash cycle.
Dave
No, my suggestion was going to be chrome actually.
The next step would be to check the javascript console and see if there are any interesting error messages there. (Dot-dot-dot menu → More Tools → Development Tools → Console tab.) If we’re lucky it will tell us what’s going on.
There is also an internal chrome URL or two that might be helpful, like: chrome://usb-internals/ but I’m not sure what to look for there.
Ok so i connected and the console shows that is working. I went into the setting, gear button. and got this shortly after the page loaded
app.html:1346 Uncaught (in promise) DOMException: A transfer error has occurred.
RunUSB
@
app.html:1346
await in RunUSB (async)
onclick
Here is the console log for a few seconds after the initial error
Uncaught (in promise) DOMException: A transfer error has occurred.
RunUSB @ app.html:1346
await in RunUSB (async)
onclick @ app.html:1563
app.html:477 Sending get_preset
app.html:477 Sending off
app.html:477 Sending on
app.html:477 Sending off
app.html:1356 Loop exit!
app.html:836 Uncaught (in promise) timeout
Off @ app.html:836
await in Off (async)
onclick @ app.html:1639
app.html:830 Uncaught (in promise) timeout
On @ app.html:830
await in On (async)
onclick @ app.html:1636
app.html:836 Uncaught (in promise) timeout
Off @ app.html:836
await in Off (async)
onclick @ app.html:1639
app.html:1360 Uncaught (in promise) timeout
DoRunLoop @ app.html:1360
await in DoRunLoop (async)
Run2 @ app.html:1279
await in Run2 (async)
RunUSB @ app.html:1341
await in RunUSB (async)
onclick @ app.html:1563
app.html:1350 DoRunLoop
app.html:477 Sending get_preset
4app.html:1 Uncaught (in promise) DOMException: A transfer error has occurred.
app.html:1356 Loop exit!
app.html:1360 Uncaught (in promise) timeout
DoRunLoop @ app.html:1360
setTimeout (async)
WatchDog @ app.html:460
setTimeout (async)
RunWatchDog @ app.html:468
WatchDog @ app.html:462
setTimeout (async)
RunWatchDog @ app.html:468
WatchDog @ app.html:462
setTimeout (async)
RunWatchDog @ app.html:468
(anonymous) @ app.html:481
Send @ app.html:476
Loop @ app.html:1387
await in Loop (async)
DoRunLoop @ app.html:1354
Run2 @ app.html:1279
await in Run2 (async)
RunUSB @ app.html:1341
await in RunUSB (async)
onclick @ app.html:1563
app.html:1350 DoRunLoop
app.html:477 Sending get_preset
app.html:1356 Loop exit!
app.html:1360 Uncaught (in promise) timeout
DoRunLoop @ app.html:1360
setTimeout (async)
WatchDog @ app.html:460
setTimeout (async)
RunWatchDog @ app.html:468
WatchDog @ app.html:462
setTimeout (async)
RunWatchDog @ app.html:468
(anonymous) @ app.html:481
Send @ app.html:476
Loop @ app.html:1387
DoRunLoop @ app.html:1354
setTimeout (async)
WatchDog @ app.html:460
setTimeout (async)
RunWatchDog @ app.html:468
WatchDog @ app.html:462
setTimeout (async)
RunWatchDog @ app.html:468
WatchDog @ app.html:462
setTimeout (async)
RunWatchDog @ app.html:468
(anonymous) @ app.html:481
Send @ app.html:476
Loop @ app.html:1387
await in Loop (async)
DoRunLoop @ app.html:1354
Run2 @ app.html:1279
await in Run2 (async)
RunUSB @ app.html:1341
await in RunUSB (async)
onclick @ app.html:1563
app.html:1350 DoRunLoop
app.html:477 Sending get_preset
app.html:1356 Loop exit!
app.html:1360 Uncaught (in promise) timeout
DoRunLoop @ app.html:1360
setTimeout (async)
WatchDog @ app.html:460
setTimeout (async)
RunWatchDog @ app.html:468
WatchDog @ app.html:462
setTimeout (async)
RunWatchDog @ app.html:468
(anonymous) @ app.html:481
Send @ app.html:476
Loop @ app.html:1387
DoRunLoop @ app.html:1354
setTimeout (async)
WatchDog @ app.html:460
setTimeout (async)
RunWatchDog @ app.html:468
WatchDog @ app.html:462
setTimeout (async)
RunWatchDog @ app.html:468
(anonymous) @ app.html:481
Send @ app.html:476
Loop @ app.html:1387
DoRunLoop @ app.html:1354
setTimeout (async)
WatchDog @ app.html:460
setTimeout (async)
RunWatchDog @ app.html:468
WatchDog @ app.html:462
setTimeout (async)
RunWatchDog @ app.html:468
WatchDog @ app.html:462
setTimeout (async)
RunWatchDog @ app.html:468
(anonymous) @ app.html:481
Send @ app.html:476
Loop @ app.html:1387
await in Loop (async)
DoRunLoop @ app.html:1354
Run2 @ app.html:1279
await in Run2 (async)
RunUSB @ app.html:1341
await in RunUSB (async)
onclick @ app.html:1563
app.html:1350 DoRunLoop
app.html:477 Sending get_preset
I know its the 3rd proffie i bought, its about yr and a half old. I dont remember where i got it from, possibly saber bay. I do have 2 other sabers i can upgrade to 6.6. I did try opera and had the same problem. I also checked the java updater and there was an update. Im going to try again they the updated java.
I can try upgrading they other sabers tomorrow.
Dave
AFAIK, there is no Java involved here, so updating Java shouldn’t make a difference.
It you’ve tried more than one browser, then that probably means that it’s not the browsers fault. (Although Chrome and Edge shares a lot of code, so they can have the same bugs.)
So… If it’s not the cable, and not the browser, then it must be…
proffieos workbench
windows
proffieos
the proffieboard itself
If we can narrow it down to one of these, then it will be much easier to start actually figuring out what the problem is.
I think the next thing to check is the serial monitor though. Like, does it say anything interesting when the disconnect happens? Does the serial monitor stay connected, or does it also disconnect?’
Ok Prof get ready. I upgraded my original saber to 6.6 and tried changing the settings with chrome. I got the same transfer error. I then loaded arduino ide and opened the serial monitor. Here comes the head scratcher, I was able to edit the blade settings in the webusb app without a problem. i then closed the browser and disconnected the saber and tried again. I was able to get into the app and edit the settings again. But the second time i did get the transfer error after i was done editing it and clicked the button to go back to the main app menu.
All the while the serial monitor was showing the correct input commands and output responses.
But when i got the transfer error there were no error messages in the serial monitor. It looked like everything was working. I will try with another saber later tonight and remember to copy and paste the results.
Now I am scratching my head, you would figure that there would be an error in the serial monitor if something was not responding correctly.
I am going to try on my linux machine as well as my android phone to see if i get the same results.
Dave
So, the board basically has a separate serial monitor for the webusb connection.
So you can’t see the commands that are executed there, but you will see some debug messages while that is happening. You may also be able to use the “monitor serial” command to see what’s going on on the weusb connection.
One good thing though; if the serial monitor keeps working while the webusb connection fails, that rules out proffieos crashing, which is one possible reason why webusb would not be working.
Yes, i could not see the commands but i could see the status output via the serial monitor as well as the basic responce of the board.
Can the webusb be used without fetts mods? If so i may rey a fresh install and see what happens.
Ill try ooening serial minitor, then webusb on my sabers that arent connecting to webusb. My proffieboard 3.7, and now 3 proffie 2.2s (all from Electronics 1,2,3 wont connect to webusb. When you click on usb connectiin in the app, it never advances to the workbench screen. Im also on windows 10, and using chrome.
MegtoothSith, please start a separate thread to avoid making things confusing.
If some boards work, but not others, then there must be one of the following things:
chrome itself is paired with some of these boards already, and a bug somewhere is preventing that from working.
The OS is for some reason assigning different drivers to these boards.
Some minor, difference in the configuration of these boards is randomly causing problems for webusb. (Can be tested by using the same configuration for different boards.)
Some difference in the hardware of the CPU is causing these to work differently. (Which shouldn’t happen if they are the same cpu model, unless st-micro did an oops, or the CPUs are fake.)
Hey all, Sorry for the delay, got sick this week. I was able to work on some trying other ideas. I tried my linux computer and it kept disconnecting. I also upgraded to 6.7 and tried that. When i checked the console it was the same transfer error. I didnt have a chance to try my phone or another windows machine since my other laptop has crapped out.
I was able to get most of the colors set. One issue that did seem to be constant was that when i was working on the drag settings it would disconnect.
The odd thing is that that the board was still connected in windows and i could access the sd card as well as use the serial monitor in arduino ide.
On the linux machine i was able to load the webusb successfully once and it disconnected while adjusting the blade colors. After that it wouldnt connect through web usb at all. I even restarted linux and reconnected it and i was able to use the serial monitor and get the information with arduino ide, but webusb would not work at all.