• BLE UUID Explorer 1
  • BLE UUID Explorer 2
  • BLE UUID Explorer 3
  • BLE UUID Explorer 4

BLE UUID Explorer

The App is a tool to discover and explore with the services and characteristics for the BLE Peripheral Devices. More than 340 UUIDs, including the listed UUIDs by Bluetooth SIG, as well as several known private UUIDs, are collected in the App. The scanned EIR fields are explained, which is helpful to inspect advertising information. Characteristic I/O (Read/Write) and Known Transparent (UART) Service are supported. BLE Connection for the dual mode chip is automatically enabled. The long packet problem (>=20 bytes) of Android BLE is solved by automatic packet segmentation. Hot keys for throughput test (20~10KBytes) can be selected from the menu of I/O activities.Note:1. A long connection time (5~15 seconds) of BLE for dual mode chip is needed. Stop and restart the App again if the connection time is too long (>30 seconds).2. Known Transparent (UART) Service: Nordic UART Service: tested. ISSC Transparent Service: tested. HM-10 : listed, but not tested yet.References:[1] Bluetooth Core 4.0 [Vol 3], Part C [Generic Access Profile], Section-18 [APPENDIX C (NORMATIVE): EIR AND AD FORMATS] The App is a tool to discover and explore with the services and characteristics for the BLE Peripheral Devices. More than 340 UUIDs, including the listed UUIDs by Bluetooth SIG, as well as several known private UUIDs, are collected in the App. The scanned EIR fields are explained, which is helpful to inspect advertising information. Characteristic I / O (Read / Write) and Known Transparent (UART) Service are supported. BLE Connection for the dual mode chip is automatically enabled. The long packet problem (> = 20 bytes) of Android BLE is solved by automatic packet segmentation. Hot keys for throughput test (20 ~ 10KBytes) can be selected from the menu of I / O activities.Note:1. A long connection time (5 ~ 15 seconds) of BLE for dual mode chip is needed. Stop and restart the App again if the connection time is too long (> 30 seconds).2. Known Transparent (UART) Service:    Nordic UART Service: tested.    ISSC Transparent Service: tested.    HM-10: listed, but not tested yet.References:[1] Bluetooth Core 4.0 [Vol 3], Part C [Generic Access Profile], Section-18 [APPENDIX C (NORMATIVE): EIR AND AD FORMATS]
Note:1. A long connection time (5~15 seconds) of BLE for dual mode chip is needed. Stop and restart the App again if the connection time is too long (>30 seconds).2. Known Transparent (UART) Service: Nordic UART Service: tested. ISSC Transparent Service: tested. HM-10 : listed, but not tested yet.

References:[1] Bluetooth Core 4.0 [Vol 3], Part C [Generic Access Profile], Section-18 [APPENDIX C (NORMATIVE): EIR AND AD FORMATS]

Note:1. A long connection time (5 ~ 15 seconds) of BLE for dual mode chip is needed. Stop and restart the App again if the connection time is too long (> 30 seconds).2. Known Transparent (UART) Service:    Nordic UART Service: tested.    ISSC Transparent Service: tested.    HM-10: listed, but not tested yet.

References:[1] Bluetooth Core 4.0 [Vol 3], Part C [Generic Access Profile], Section-18 [APPENDIX C (NORMATIVE): EIR AND AD FORMATS]

Category : Tools

Related searches

Reviews (1)

Jun. H. Feb 8, 2021     

It can not find any bluetooth device, let alone UUID. I tied to use other bluetooth detector app in the same time, a lot devices found.