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

L2CAP fragmentation on Windows #1702

Open
itecnet opened this issue Dec 19, 2024 · 1 comment
Open

L2CAP fragmentation on Windows #1702

itecnet opened this issue Dec 19, 2024 · 1 comment
Labels
3rd party issue The issue is with the Bluetooth stack, the BLE device, or other 3rd party code not with Bleak itself Backend: WinRT Issues or PRs relating to the WinRT backend

Comments

@itecnet
Copy link

itecnet commented Dec 19, 2024

  • bleak version: 0.22.3
  • Python version: 3.13
  • Operating System: Windows10/11

Description

I have a BLE communication from PC to a Nordic MCU (NUS Service) and use Bleak. My application works perfectly under Linux. If I copy my application to Windows (without changes), I get a strong fragmentation of the user data. The only difference is the operating system and the BLE adapter (Linux: Intel AX211 , Windows: EDIMAX BT-8500).

What I Did

I use a standard MTU (517) with data length extension and each packet has a payload of 242 bytes per PDU.
Unfortunately I am new to Windows, but maybe someone can give me a tip on how to remove the fragmentation. I need to transfer 600 kB and the time difference between Linux and Windows is way too big.

Logs

I have attached a Wireshark dump because I could not find a cause.

bleak-win.zip

@dlech
Copy link
Collaborator

dlech commented Dec 19, 2024

This is happening at the OS level, so probably not anything we can do about it from Bleak.

Not sure what else to suggest other than trying a different Bluetooth adapter that uses a different driver.

@dlech dlech added 3rd party issue The issue is with the Bluetooth stack, the BLE device, or other 3rd party code not with Bleak itself Backend: WinRT Issues or PRs relating to the WinRT backend labels Dec 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3rd party issue The issue is with the Bluetooth stack, the BLE device, or other 3rd party code not with Bleak itself Backend: WinRT Issues or PRs relating to the WinRT backend
Projects
None yet
Development

No branches or pull requests

2 participants