与 gatt_sensordata_app 2.0 固件的 Web BLE 连接

发布于 2025-01-12 08:01:04 字数 1412 浏览 3 评论 0原文

我正在尝试使用提供的 web ble 和 python 客户端示例与 gatt_sensordata_app 固件进行交互。任何人都可以确认它可以与最新的浏览器一起使用并且还使用 >2.0 固件吗?

我在 OSX 11.6.3 上使用 chrome 98.0.4758.109。还尝试了 Android 上的 google chrome,但没有成功。

一段时间以来,我一直依赖工作 javascript 代码来获取默认的 ble_std_services_ecgrr 固件( 1.9 )。最近才开始使用 gatt_sensordata_app 和 2.0 固件。 我还尝试使用部分“经过验证”的代码来调试失败的 gatt_sensordata_app index.html 服务查找,但没有成功。另外,使用 2.1.2 新安装的默认 std_services_ecgrr 固件不再通过 web ble 工作。

我将 Movesense-gatt_sensordata_app_w_bootloader.zip 上传到一台设备上,将 Movesense-ble_std_services_ecgrr_module_w_bootloader.zip 上传到另一台设备上,并且一旦我拿到第三台设备,我将尝试验证我的说法,即 web ble ble_std_services_ecgrr 1.9 交互可以正常工作。

连接后的行为:

samples/gatt_sensordata_app/web_client/index.html:

标签:已选择设备 Movesense XY。 表: 连接状态: false

控制台中根本没有 js 输出。

进一步的 JS 控制台调试: 单击“选择设备”后验证 selectedDevice['Movesense XY'].gatt.connected == true

selectedDevice['Movesense XY'].gatt.getPrimaryService('34802252-7185-4d5d-b431-630e7050e8f0').then(service = > {console.log('服务', service)}).catch(error => {console.log('error', error)});

该承诺永远不会解决,也不会捕获该错误。对我来说,它似乎仍然停留在 gatt.getPrimaryService / gatt.getPrimaryServices 调用中。

我还在树莓派( Linux 5.10.17-v7l+armv7l )上尝试了提供的 python 客户端 gatt_sensordata_app/python_client/movesense_sensor_data.py 但没有成功: 并发.futures._base.TimeoutError 任务已被销毁,但正在等待处理!

我还尝试通过 nrf connect 连接到两个 movesense 固件,这似乎有效,但我无法与 gatt_sensordata_app 交互

I'm trying to interact with the gatt_sensordata_app firmware using the provided web ble and python client samples. Can anyone confirm that it is working with uptodate browsers and also using the >2.0 firmwares?

I'm using chrome 98.0.4758.109 on OSX 11.6.3. Also tried google chrome on Android without success.

I have been relying on working javascript code since a while for the default ble_std_services_ecgrr firmware ( 1.9 ). Only recently started working with gatt_sensordata_app and 2.0 firmwares in general.
I also tried to debug the failing gatt_sensordata_app index.html service lookup using parts of that "proven" code without success. Additionaly the newly installed default std_services_ecgrr firmware using 2.1.2 doesn't work anymore via web ble.

I uploaded Movesense-gatt_sensordata_app_w_bootloader.zip onto one device, Movesense-ble_std_services_ecgrr_module_w_bootloader.zip onto another and will try to verify my claims that the web ble ble_std_services_ecgrr 1.9 interaction works as soon as I can get hold of my third device.

Behaviour:

samples/gatt_sensordata_app/web_client/index.html after connecting:

Label: Device Movesense XY selected.
Table: Connection Status: false

No js output in console at all.

Further JS console debug:
Verified selectedDevice['Movesense XY'].gatt.connected == true after clicking "select device"

selectedDevice['Movesense XY'].gatt.getPrimaryService('34802252-7185-4d5d-b431-630e7050e8f0').then(service => {console.log('service', service)}).catch(error => {console.log('error', error)});

The promise never resolves, nor catches that error. For me it looks like it somehow remains stuck in gatt.getPrimaryService / gatt.getPrimaryServices call.

I also tried the provided python client gatt_sensordata_app/python_client/movesense_sensor_data.py on a raspberry pi ( Linux 5.10.17-v7l+ armv7l ) but without success:
concurrent.futures._base.TimeoutError
Task was destroyed but it is pending!

I also tried connecting to both movesense firmwares via nrf connect and that seems to work but I can't interact with gatt_sensordata_app

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。
列表为空,暂无数据
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文