You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
C3 and S3 have a workaround where different power levels could be set for e.g. advertising or scanning. The workaround does not take into account advertisement data, which keeps sending "default" channel with incorrect dbM value to the advertisement packet.
The fix should be backwards compatible since it only adds an optional parameter when Tx level is added into the advertisement packet.
Tested and verified that I now see -3 dbM when previously setting the Tx Level like this:
C3 and S3 have a workaround where different power levels could be set for e.g. advertising or scanning. The workaround does not take into account advertisement data, which keeps sending "default" channel with incorrect dbM value to the advertisement packet.
The fix should be backwards compatible since it only adds an optional parameter when Tx level is added into the advertisement packet.
Tested and verified that I now see -3 dbM when previously setting the Tx Level like this:
NimBLEDevice::setPowerLevel(ESP_PWR_LVL_N3, ESP_BLE_PWR_TYPE_ADV);
Without the fix some default value is transmitted.
The text was updated successfully, but these errors were encountered: