xanathon
commented
3 years ago I got it to work, but there seem Web Bluetooth compatibility issues and this may not run on every platform and every configuration.
Desktop computer with Win10/64 and a confirmed working bluetooth dongle by TP-Link: no way to get this to work.
Surface Pro with Win10/64: it did work, but Web Bluetooth connection took a long time to find the robot.
I am trying to get the OSKR OTA onto one of my robots.
The process described in the official docs works as long as I use @kercre123 s web setup instead of DDL's. I factory reset the robot and then do a recovery reboot. I am then able to connect via bluetooth and can get into the console. There I connect to wifi and then start the ota update with the "latest.ota" linked in the DDL docs. The update works and the robot reboots. It looks like he is not on the latest firmware after that, he shows 1.6.0.3331 instead of a 1.7 version.
If I now try to again connect via Bluetooth this seems to work, as Chrome says the tab is connected to a Bluetooth device and subsequent connection tries show the robot as "paired" in the Chrome Web Bluetooth pairing dialog. However, the web app only shows a rotating progression icon and nothing happens, I can no longer get into the emulated console in Chrome.
I repeated the process multiple times, clearing and recovery booting, being able to connect fine, then doing ota-start with the recommended image and after that: no console.
I already tried force reloading the browser tab and I also already retried starting Chrome new.
If I open the web developer console in Chrome and try to connect I get the following error:
"DOMException: GATT Server is disconnected. Cannot perform GATT operations. (Re)connect first with device.gatt.connect."If I recover again I am again able to connect to the robot running on 0.9 via web setup, but after updating him to 1.6 via ota-start the above problems are there again and connection is not possible. Latest Chrome on Windows 10/64.