NUS server on Android

RE: NUS server on Android

FormerMember — Tue, 25 Jul 2017 08:53:57 GMT

What I meant is that you can use nRF Connect to check if the it can do proper service discovery on the Android server device, to verify that the NUS service/characteristics have been added correctly.

RE: NUS server on Android

Akinobu Yokawa — Tue, 25 Jul 2017 01:29:54 GMT

The nRF Connect does not implement NUS server. It is GATT client. I cannot make it sure.

RE: NUS server on Android

FormerMember — Mon, 24 Jul 2017 11:31:57 GMT

If you use nRF Connect (PC/Android/iOS) to do service discovery on the Android device. Does that work like normal?

RE: NUS server on Android

Akinobu Yokawa — Fri, 30 Jun 2017 06:08:00 GMT

It returned NRF_ERROR_BUSY.

RE: NUS server on Android

FormerMember — Fri, 30 Jun 2017 05:52:22 GMT

Which error code did sd_ble_gattc_characteristics_discover() return?

RE: NUS server on Android

Akinobu Yokawa — Fri, 30 Jun 2017 01:27:36 GMT

If you set the log "level" in the nRF52 central to "DEBUG" the ble_db_discovery module will give additional debug information.

I tried it. I confirmed that characteristics_discover() was called in on_primary_srv_discovery_rsp().

In ble_db_discovery_on_ble_evt, the event BLE_GATTC_EVT_PRIM_SRVC_DISC_RSP came once. After that, the event BLE_GATTC_EVT_CHAR_DISC_RS never came.

RE: NUS server on Android

FormerMember — Thu, 29 Jun 2017 14:17:54 GMT

In the NUS_Android sniffer log there is only service discovery ("Find Type by value request/response"), and no characteristic discovery ("Read by type request/response").

If you set the log "level" in the nRF52 central to "DEBUG" the ble_db_discovery module will give additional debug information.

If you set a breakpoint in on_primary_srv_discovery_rsp() and run the chip in debug mode, you can check if characteristic discovery is being initiated (characteristics_discover() ).

RE: NUS server on Android

FormerMember — Thu, 29 Jun 2017 06:11:01 GMT

Could you upload the .pcapng version of the sniffer logs? ("The file contains record data that Wireshark doesn't support")

RE: NUS server on Android

Akinobu Yokawa — Thu, 29 Jun 2017 00:48:53 GMT

I have attached the sniffer logs in the question. Could you check them please?

RE: NUS server on Android

FormerMember — Wed, 28 Jun 2017 09:30:14 GMT

If you add some more logging during the service discovery, do you see which services/characteristics that were found?

RE: NUS server on Android

Akinobu Yokawa — Tue, 27 Jun 2017 03:55:53 GMT

Thanks. I have captured the sniffer log. There are the following packets. However, there is not the packet "Read By Type Request, GATT Characteristic Declaration" from master which is central (nRF52832).

Find By Type Value Request, GATT Primary Service Declaration, Handles: 0x0001..0xffff
Find By Type Value Response

RE: NUS server on Android

FormerMember — Mon, 26 Jun 2017 13:39:01 GMT

@akinobu-yokawa : Could you double check that the TX/RX NUS UUIDs in you app are correct? I.e, not interchanged?

RE: NUS server on Android

endnode — Mon, 26 Jun 2017 08:27:52 GMT

I would suggest to get RF trace from some BLE sniffer and compare these two GATT Service Discovery procedures, it should give you good glimps where (and why) NUC central hangs/misses NUS service on mobile side...