Open victorklos opened 6 years ago
Many thanks for your effort!
Using http://reelyactive.github.io/advlib/ I found that the raw data from the sniffer contains 12 bytes before the actual PDU.
PDU
For example, when the received string was (hex):
0028005107655923D6BE898E40180419ED5A48E30201040E09424243206D6963726F3A62697496C97419A5
with the first 12 bytes removed:
40180419ED5A48E30201040E09424243206D6963726F3A62697496C97419A5
Entering this last string into the website above yields:
{ "type": "ADVA-48", "value": "e3485aed1904", "advHeader": { "type": "ADV_IND", "length": 24, "txAdd": "random", "rxAdd": "public" }, "advData": { "flags": [ "BR/EDR Not Supported" ], "completeLocalName": "BBC micro:bit" } }
which matches the device in question exactly.
Also, removing the last 3 bytes from the string changes nothing, indicating this may indeed be a CRC.
Hii, the Texas instruments has a set of commands for that chip. Whay not to use thir commands.
@avikovakova can you share a link?
Many thanks for your effort!
Using http://reelyactive.github.io/advlib/ I found that the raw data from the sniffer contains 12 bytes before the actual
PDU
.For example, when the received string was (hex):
with the first 12 bytes removed:
Entering this last string into the website above yields:
which matches the device in question exactly.
Also, removing the last 3 bytes from the string changes nothing, indicating this may indeed be a CRC.