Testing of Current time service

[swathi p]

Hi,

I am unable to test current time service example.I followed all the steps mentioned to test CTS Example.But, below are the log messages:

Again if I try to reset and try to connect to the device.The log messages are as below:

Please suggest me to rectify the errors and also the right way to test CTS example with 1SDK and mobile application.

Thanks & Regards,

Swathi P.

[Karl Ylvisaker]

Hello Swathi P,

Did you follow the Setup and Testing section of the CTS Example Documentation?
From your error logs, it seems that the Current Time Service is not found on the central device, which causes the peripheral to auto-disconnect.
You need to make sure that the central is providing this service.
Which smartphone application and OS are you using?
If you are using the nRF Connect application, you will need to configure your GATT server to include the Current Time Service, with the Current Time characteristic. The initial value of the characteristic should be C2 07 0B 0F 0D 25 2A 06 FE 08, as detailed in the CTS Example documentation referenced above.

Please let me know if this resolves your issue,

Best regards,
Karl

[swathi p]

Hi,

Thank you for the reply.

In example provided it has already advertising current time service,I think this means central is provided with service.

I am using Oppo A71,it is android.

I have configured Server on the mobile.

To write the initial value the service is not getting discovered.

Can you also please let me know,what content the initial value of characteristic "C2 07 0B 0F 0D 25 2A 06 FE 08" is holding?

Thanks & Regards,

Swathi P

 

[Amanda Hsieh]

Yes.

-Amanda H.

[swathi p]

Hi Amanda Hsieh,

Thank you.I tried testing by adding the code that you sent,It is working fine on android.But I found no change with iOS.It has same connectivity issues as I said before.

Regards,

Swathi P.

[Amanda Hsieh]

Hi Swathi, 

Please provide the debug log and sniff log. Thanks. 

-Amanda H.

[swathi p]

Hi,

Connectivity issue solved on iOS,but there is delay in disconnection and pairing.After I press disconnect on nRF Connect,It is getting disconnected after around 30sec.If I press to pairup it is getting bonded after 30sec.Can I know the reason for the delay?

Thanks & Regards,

Swathi P. 

[Amanda Hsieh]

Hi Swathi, 

For pairing, I see it spend a lot of time on encryption between the mobile and device before the security procedure (peer_manager) from the sniff log. The current implementation requires security to be established before service discovery.

For disconnection, I don't see any delay issue as the sniff log. 

If you still have the delay issue in disconnect, please provide the sniff log. I can check it. 

-Amanda H.

[swathi p]

Amanda Hsieh said:

For pairing, I see it spend a lot of time on encryption between the mobile and device before the security procedure (peer_manager) from the sniff log. The current implementation requires security to be established before service discovery.

ok.Can you please let me know what exactly I can do to establish security before service discovery?

[Amanda Hsieh]

Hi Swathi, 

Sorry to cause the misunderstand. If you take a look at the log, you can see the application will do the security procedure with peer_manager before service discovery. 

<info> peer_manager_handler: Connection secured: role: Peripheral, conn_handle: 0, procedure: Bonding

<info> ble_db_disc: p_db_discovery->discovery_in_progress: 0.

<info> peer_manager_handler: Peer data updated in flash: peer_id: 0, data_id: Bonding data, action: Update

<info> peer_manager_handler: Peer data updated in flash: peer_id: 0, data_id: Peer rank, action: Update

<info> ble_cts_c: Current Time Service discovered at peer.

<info> app: Current Time Service discovered on server.

-Amanda H.

[swathi p]

Hi,

Amanda Hsieh said:

Sorry to cause the misunderstand. If you take a look at the log, you can see the application will do the security procedure with peer_manager before service discovery. 

yes.Then what might be the reason for delay?

Amanda Hsieh said:

Please provide the debug log and sniff log.

Sniffer works between two nRF Chips that communicate over the air.I don't have to boarads to test CTS sniffer data.

Thanks & Regards,

Swathi P

[Amanda Hsieh]

Hi Swathi, 

swathi p said:

Then what might be the reason for delay?

Please see the blue block part in the figure, there are many handshakings between the master (phone) and the slave (nRF device) for pairing and encryption.  

 

swathi p said:

Sniffer works between two nRF Chips that communicate over the air.I don't have to boarads to test CTS sniffer data.

Without sniffer log, I could not know what happens in the air. I could not reproduce that on my side either. 

-Amanda H.

[swathi p]

yes,we can see there are many handshakings between the master (phone) and the slave (nRF device).I could notice that there are repeatative handshakings.is it so?Any repeatition is happening unneccessarily,so that by avoiding such repeatition could we solve this delay issue?or is this the protocol internally happens that it has to undergo handshakings several times? 

Amanda Hsieh said:

Without sniffer log, I could not know what happens in the air. I could not reproduce that on my side either. 

But,as already discussed on this with you that I am testing CTS using nRF chip and mobile by configuring gatt server on mobile.I am unable to provide sniff log.Is there any other way that we can get sniff log info fr one DK and mobile?