-
Notifications
You must be signed in to change notification settings - Fork 12
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
Removing duplicate BLE payload max length declarations #259
Conversation
Kudos, SonarCloud Quality Gate passed!
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks
…H in documentation
|
// Other than 1 MBit / s require extended advertising. | ||
if (BLE_GAP_PHY_1MBPS == scan_phys) | ||
{ | ||
scan_params.extended = 0; | ||
scan_params.extended = 1; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Was this tested on hardware? I was under impression that 2 MBit/s extended advertisements send a primary advertisement at 1 MBit / s and primary advertisement contains information about when and where the actual extended payload will be.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I tested this when implementing extended payload support on Gateway, but I agree that it looks suspicious. Let me test it again. I will tell you the result tomorrow.
No description provided.