Connection parameters in nrf ble

RE: Connection parameters in nrf ble

Karl Ylvisaker — Wed, 08 Dec 2021 10:41:06 GMT

Please go through all the conditions that would trigger a link termination by your application, and see if any of these may be triggered unexpectedly as a result of the changed connection interval.

Best regards,
Karl

RE: Connection parameters in nrf ble

Ridhi — Tue, 07 Dec 2021 14:09:07 GMT

i havent changed anything except the Connection Interval values, i am not getting why this is hampering

RE: Connection parameters in nrf ble

Karl Ylvisaker — Mon, 06 Dec 2021 16:41:55 GMT

Hello again,

Please note that we do not provide support in the forum during the weekend.

[quote user="RIDHIMA"]i found that increasing CI reduces power consumption but [/quote]

This is correct, because it will lead to much more infrequent use of the RADIO peripheral, which in turn saves power.

[quote user="RIDHIMA"]i am sharing you the wireshark traces:[/quote]

Thank you for providing the traces. I do not immediately see anything abnormal in the traces - the connections are terminated by either the peripheral or the central in either cases, with no error. Everything seems nominal.

This makes me suspect that it is a application layer logical issue that is causing this. What could cause either the peripheral or the central to terminate the connection? Are they both programmed to terminate the connection when certain conditions are met, such as no data being sent for a specific period, or similar?
Both instances have a period of empty packets leading up to the connection termination.

Best regards,
Karl

RE: Connection parameters in nrf ble

Ridhi — Mon, 06 Dec 2021 06:59:49 GMT

Karl Ylvisaker pls administer the above issue

RE: Connection parameters in nrf ble

Ridhi — Fri, 03 Dec 2021 14:15:27 GMT

Hello Karl,

My code works as:

press button

device advertise with name BTLog

Then i connect on nrf connect app on mobile

i press a button and put device in data logging mode with flash storage and temperature sensor interfaced

then after logging i press button again to make the device sleep

then again press button to readvertise

the from the service created i get the logged data using notification

i face issue in setting connection parameters :

i found that increasing CI reduces power consumption but

1st is for 7.5-100ms connection interval which accounts for more than 20 logs

2nd is for 1000-1000ms connection interval which only 4 logs after which i dont get logs

i am sharing you the wireshark traces:

devzone.nordicsemi.com/.../7.5_2D00_100ms-file.pcapng

devzone.nordicsemi.com/.../1000_2D00_1000ms.pcapng

devzone.nordicsemi.com/.../1000_2D00_1000ms-file.csv

devzone.nordicsemi.com/.../7.5_2D00_100ms.csv devzone.nordicsemi.com/.../7.5_2D00_100ms-file.txt

devzone.nordicsemi.com/.../1000_2D00_1000ms.txt

RE: Connection parameters in nrf ble

Karl Ylvisaker — Mon, 22 Nov 2021 10:40:29 GMT

You could share it using the Insert -> Image/Video/file option. Please also address my other questions.

Please share the .pcapng file, as generated by Wireshark.

Best regards,
Karl

RE: Connection parameters in nrf ble

Ridhi — Mon, 22 Nov 2021 10:33:59 GMT

for sniffer trace i have a csv file how to share it?

RE: Connection parameters in nrf ble

Karl Ylvisaker — Mon, 22 Nov 2021 10:19:38 GMT

Hello again,

[quote user="RIDHIMA"]what is the problem i am getting is that as i set 7.5-100ms i am able to get multiple logs but when i set to 1000-1000ms i get only 16 logs and after that my device stops logging[/quote]

I know this already, you have said this before, but it seems that you might be ignoring my comments about the sniffer trace and debug session.
Could you share the whole sniffer trace with me here, so I may take a look? Please provide the trace for both the working and the non-working scenario.
Have you used a debug session to verify whether the program counter is getting stuck anywhere in the 16 log cases?
I have theorized before that it might be due to a buffer overflow or buildup when you change the connection interval to 1000 ms, since the buffers will be emptied much more infrequently with this connection interval.

Furthermore, what I asked in my previous comment was; what did you try to communicate with the screenshot of the single packet? What was it that you would like me to take a look at in this packet?

Please elaborate on your issues, address my questions, and be as specific as possible - so that we together may resolve your issues more quickly.

Best regards,
Karl

RE: Connection parameters in nrf ble

Ridhi — Sat, 20 Nov 2021 08:38:40 GMT

karl what is the problem i am getting is that as i set 7.5-100ms i am able to get multiple logs but when i set to 1000-1000ms i get only 16 logs and after that my device stops logging

RE: Connection parameters in nrf ble

Karl Ylvisaker — Fri, 19 Nov 2021 14:37:08 GMT

This looks like a screenshot of a single, random packet.
Please elaborate thoroughly on what you are trying to communicate.

Best regards,
Karl

RE: Connection parameters in nrf ble

Ridhi — Thu, 18 Nov 2021 15:32:54 GMT

RE: Connection parameters in nrf ble

Karl Ylvisaker — Thu, 18 Nov 2021 13:16:24 GMT

Thanks for providing the logs.
Please also address the rest of my questions from my previous comments.

Best regards,
Karl

RE: Connection parameters in nrf ble

Ridhi — Thu, 18 Nov 2021 12:22:22 GMT

17:26:10.658 -> <info> app: BeforeFivesec

17:26:10.658 -> <info> app_timer: RTC: initialized.

17:26:10.658 -> <info> app: hello ble

17:26:10.658 -> <info> app: Before enter into sleep mode

17:26:10.705 -> <info> app: After enter into sleep mode

17:26:10.705 -> <info> app: Alarm status : 0

17:26:10.705 -> <info> app: Upper threshold : 30

17:26:10.705 -> <info> app: Lower threshold : 20

17:26:10.705 -> <info> app: Type C : 1

17:26:10.705 -> <info> app: Starting delay in sec. : 0

17:26:10.705 -> <info> app: Interval delay in sec.: 10

17:26:10.705 -> <info> app: Data EF4015

17:26:10.705 -> <info> app: Data3 15

17:26:10.705 -> <info> app: Data2 40

17:26:10.705 -> <info> app: Data1 EF

17:26:10.705 -> <info> app: Data0 0

17:26:10.705 -> <info> app: temporarylogcounter4 10 temporarylogcounter3 0 temporarylogcounter2  0 temporarylogcounter1 0

17:26:10.705 -> <info> app: log counter value : 16 

17:26:10.705 -> <info> app: Newpasskey12:123456

17:26:10.752 -> <info> app: Fast advertising

17:26:10.752 -> <info> app: start advertising

17:26:10.752 -> <info> app: Application started in Advertising Mode.

17:26:10.752 -> <info> app: Current Time service client started.

17:26:16.257 -> <info> app: Device Connected

17:26:16.257 -> <info> app: Connected.

17:26:16.914 -> <info> ble_cts_c: Current Time Service discovered at peer.

17:26:16.914 -> <info> app: Current Time Service discovered on server.

17:26:17.009 -> <info> app: Current Time received.

17:26:17.009 -> <info> app: 11/16/21-17:26:24

17:26:30.180 -> <info> app: passkeynew:123456

17:26:30.180 -> <info> app: passkeynew1:123456

17:26:30.180 -> <info> app: comaprision successful

17:27:05.129 -> <info> app: BeforeFivesec

17:27:05.129 -> <info> app: Data logging Mode.

17:27:05.176 -> <info> app: Bluetooth deactivated.

17:27:05.176 -> <info> app: Fast advertising

17:27:05.176 -> <info> app: Device Disconnected

17:27:05.176 -> <info> app: Disconnect Complete.

17:27:05.176 -> <info> app: Disconnected.

17:27:05.176 -> <info> app: defaualtpasskey ******

17:27:05.176 -> <info> app: Memory Initialization done.

17:27:05.176 -> <info> app: Temp Logging started hi.

17:27:05.176 -> <info> app: Timer started hi.

17:27:05.176 -> <info> app: Initial timer finished!

17:27:05.176 -> <info> app: data_to_send 25.88-11/16/21-17:27:05

17:27:05.176 -> <info> app: temp_write_page temp_write_offset bytes_to_write 0 0 23

17:27:05.176 -> <info> app: reading 1 done

17:27:05.176 -> <info> app: temporarylogcounter0 1 temporarylogcounter1 0 temporarylogcounter2  0 temporarylogcounter3 0

17:27:15.809 -> <info> app: data_to_send 25.88-11/16/21-17:27:16

17:27:15.809 -> <info> app: temp_write_page temp_write_offset bytes_to_write 0 23 23

17:27:15.809 -> <info> app: reading 2 done

17:27:15.809 -> <info> app: temporarylogcounter0 2 temporarylogcounter1 0 temporarylogcounter2  0 temporarylogcounter3 0

17:27:25.810 -> <info> app: data_to_send 25.88-11/16/21-17:27:26

17:27:25.810 -> <info> app: temp_write_page temp_write_offset bytes_to_write 0 46 23

17:27:25.810 -> <info> app: reading 3 done

17:27:25.810 -> <info> app: temporarylogcounter0 3 temporarylogcounter1 0 temporarylogcounter2  0 temporarylogcounter3 0

17:27:35.800 -> <info> app: data_to_send 25.88-11/16/21-17:27:36

17:27:35.800 -> <info> app: temp_write_page temp_write_offset bytes_to_write 0 69 23

17:27:35.800 -> <info> app: reading 4 done

17:27:35.800 -> <info> app: temporarylogcounter0 4 temporarylogcounter1 0 temporarylogcounter2  0 temporarylogcounter3 0

17:27:45.787 -> <info> app: data_to_send 25.88-11/16/21-17:27:46

17:27:45.787 -> <info> app: temp_write_page temp_write_offset bytes_to_write 0 92 23

17:27:45.834 -> <info> app: reading 5 done

17:27:45.834 -> <info> app: temporarylogcounter0 5 temporarylogcounter1 0 temporarylogcounter2  0 temporarylogcounter3 0

17:27:55.823 -> <info> app: data_to_send 25.88-11/16/21-17:27:56

17:27:55.823 -> <info> app: temp_write_page temp_write_offset bytes_to_write 0 115 23

17:27:55.823 -> <info> app: reading 6 done

17:27:55.823 -> <info> app: temporarylogcounter0 6 temporarylogcounter1 0 temporarylogcounter2  0 temporarylogcounter3 0

17:28:05.811 -> <info> app: data_to_send 25.75-11/16/21-17:28:06

17:28:05.811 -> <info> app: temp_write_page temp_write_offset bytes_to_write 0 138 23

17:28:05.811 -> <info> app: reading 7 done

17:28:05.811 -> <info> app: temporarylogcounter0 7 temporarylogcounter1 0 temporarylogcounter2  0 temporarylogcounter3 0

17:28:15.801 -> <info> app: data_to_send 25.88-11/16/21-17:28:16

17:28:15.801 -> <info> app: temp_write_page temp_write_offset bytes_to_write 0 161 23

17:28:15.801 -> <info> app: reading 8 done

17:28:15.801 -> <info> app: temporarylogcounter0 8 temporarylogcounter1 0 temporarylogcounter2  0 temporarylogcounter3 0

17:28:25.789 -> <info> app: data_to_send 25.88-11/16/21-17:28:26

17:28:25.789 -> <info> app: temp_write_page temp_write_offset bytes_to_write 0 184 23

17:28:25.789 -> <info> app: reading 9 done

17:28:25.789 -> <info> app: temporarylogcounter0 9 temporarylogcounter1 0 temporarylogcounter2  0 temporarylogcounter3 0

17:28:35.807 -> <info> app: data_to_send 25.88-11/16/21-17:28:36

17:28:35.807 -> <info> app: temp_write_page temp_write_offset bytes_to_write 0 207 23

17:28:35.807 -> <info> app: reading 10 done

17:28:35.807 -> <info> app: temporarylogcounter0 A temporarylogcounter1 0 temporarylogcounter2  0 temporarylogcounter3 0

17:28:45.788 -> <info> app: data_to_send 25.75-11/16/21-17:28:46

17:28:45.788 -> <info> app: temp_write_page temp_write_offset bytes_to_write 0 230 23

17:28:45.835 -> <info> app: reading 11 done

17:28:45.835 -> <info> app: temporarylogcounter0 B temporarylogcounter1 0 temporarylogcounter2  0 temporarylogcounter3 0

17:28:55.799 -> <info> app: data_to_send 25.75-11/16/21-17:28:56

17:28:55.799 -> <info> app: reading 12 done

17:28:55.799 -> <info> app: temporarylogcounter0 C temporarylogcounter1 0 temporarylogcounter2  0 temporarylogcounter3 0

17:29:05.819 -> <info> app: data_to_send 25.63-11/16/21-17:29:06

17:29:05.819 -> <info> app: temp_write_page temp_write_offset bytes_to_write 1 20 23

17:29:05.819 -> <info> app: reading 13 done

17:29:05.819 -> <info> app: temporarylogcounter0 D temporarylogcounter1 0 temporarylogcounter2  0 temporarylogcounter3 0

17:29:15.791 -> <info> app: data_to_send 25.63-11/16/21-17:29:16

17:29:15.791 -> <info> app: temp_write_page temp_write_offset bytes_to_write 1 43 23

17:29:15.791 -> <info> app: reading 14 done

17:29:15.791 -> <info> app: temporarylogcounter0 E temporarylogcounter1 0 temporarylogcounter2  0 temporarylogcounter3 0

17:29:25.826 -> <info> app: data_to_send 25.63-11/16/21-17:29:26

17:29:25.826 -> <info> app: temp_write_page temp_write_offset bytes_to_write 1 66 23

17:29:25.826 -> <info> app: reading 15 done

17:29:25.826 -> <info> app: temporarylogcounter0 F temporarylogcounter1 0 temporarylogcounter2  0 temporarylogcounter3 0

17:29:35.783 -> <info> app: data_to_send 25.63-11/16/21-17:29:36

17:29:35.830 -> <info> app: temp_write_page temp_write_offset bytes_to_write 1 89 23

17:29:35.830 -> <info> app: reading 16 done

17:29:35.830 -> <info> app: temporarylogcounter0 10 temporarylogcounter1 0 temporarylogcounter2  0 temporarylogcounter3 0

17:29:45.819 -> <info> app: data_to_send 25.63-11/16/21-17:29:46

17:29:45.819 -> <info> app: temp_write_page temp_write_offset bytes_to_write 1 112 23

17:29:45.819 -> <info> app: reading 17 done

17:29:45.819 -> <info> app: temporarylogcounter0 11 temporarylogcounter1 0 temporarylogcounter2  0 temporarylogcounter3 0

17:29:55.804 -> <info> app: data_to_send 25.63-11/16/21-17:29:56

17:29:55.804 -> <info> app: temp_write_page temp_write_offset bytes_to_write 1 135 23

17:29:55.804 -> <info> app: reading 18 done

17:29:55.804 -> <info> app: temporarylogcounter0 12 temporarylogcounter1 0 temporarylogcounter2  0 temporarylogcounter3 0

17:30:05.819 -> <info> app: data_to_send 25.63-11/16/21-17:30:06

17:30:05.819 -> <info> app: temp_write_page temp_write_offset bytes_to_write 1 158 23

17:30:05.819 -> <info> app: reading 19 done

17:30:05.819 -> <info> app: temporarylogcounter0 13 temporarylogcounter1 0 temporarylogcounter2  0 temporarylogcounter3 0

17:30:15.813 -> <info> app: data_to_send 25.50-11/16/21-17:30:16

17:30:15.813 -> <info> app: temp_write_page temp_write_offset bytes_to_write 1 181 23

17:30:15.813 -> <info> app: reading 20 done

17:30:15.813 -> <info> app: temporarylogcounter0 14 temporarylogcounter1 0 temporarylogcounter2  0 temporarylogcounter3 0

17:30:25.820 -> <info> app: data_to_send 25.50-11/16/21-17:30:26

17:30:25.820 -> <info> app: temp_write_page temp_write_offset bytes_to_write 1 204 23

17:30:25.820 -> <info> app: reading 21 done

17:30:25.820 -> <info> app: temporarylogcounter0 15 temporarylogcounter1 0 temporarylogcounter2  0 temporarylogcounter3 0

17:30:35.790 -> <info> app: data_to_send 25.50-11/16/21-17:30:36

17:30:35.790 -> <info> app: temp_write_page temp_write_offset bytes_to_write 1 227 23

17:30:35.790 -> <info> app: reading 22 done

17:30:35.790 -> <info> app: temporarylogcounter0 16 temporarylogcounter1 0 temporarylogcounter2  0 temporarylogcounter3 0

17:30:45.824 -> <info> app: data_to_send 25.50-11/16/21-17:30:46

17:30:45.824 -> <info> app: reading 23 done

17:30:45.824 -> <info> app: temporarylogcounter0 17 temporarylogcounter1 0 temporarylogcounter2  0 temporarylogcounter3 0

17:30:55.814 -> <info> app: data_to_send 25.63-11/16/21-17:30:56

17:30:55.814 -> <info> app: temp_write_page temp_write_offset bytes_to_write 2 17 23

17:30:55.814 -> <info> app: reading 24 done

17:30:55.814 -> <info> app: temporarylogcounter0 18 temporarylogcounter1 0 temporarylogcounter2  0 temporarylogcounter3 0

17:31:05.816 -> <info> app: data_to_send 25.50-11/16/21-17:31:06

17:31:05.816 -> <info> app: temp_write_page temp_write_offset bytes_to_write 2 40 23

17:31:05.816 -> <info> app: reading 25 done

17:31:05.816 -> <info> app: temporarylogcounter0 19 temporarylogcounter1 0 temporarylogcounter2  0 temporarylogcounter3 0

17:31:21.150 -> <info> app: data_to_send 26.00-11/16/21-17:31:22

17:31:21.150 -> <info> app: temp_write_page temp_write_offset bytes_to_write 2 63 23

17:31:21.199 -> <info> app: reading 26 done

17:31:21.199 -> <info> app: temporarylogcounter0 1A temporarylogcounter1 0 temporarylogcounter2  0 temporarylogcounter3 0

17:31:25.793 -> <info> app: data_to_send 25.75-11/16/21-17:31:26

17:31:25.793 -> <info> app: temp_write_page temp_write_offset bytes_to_write 2 86 23

17:31:25.793 -> <info> app: reading 27 done

17:31:25.793 -> <info> app: temporarylogcounter0 1B temporarylogcounter1 0 temporarylogcounter2  0 temporarylogcounter3 0

17:31:35.814 -> <info> app: data_to_send 25.75-11/16/21-17:31:36

17:31:35.814 -> <info> app: temp_write_page temp_write_offset bytes_to_write 2 109 23

17:31:35.814 -> <info> app: reading 28 done

17:31:35.814 -> <info> app: temporarylogcounter0 1C temporarylogcounter1 0 temporarylogcounter2  0 temporarylogcounter3 0

Case of multiple logs with CI: 7.5-100ms

Case of getting only 16 logs with CI: 1000-1000ms: after 16 logs not able to get log

12:47:30.329 -> <info> app: BeforeFivesec

12:47:30.329 -> <info> app_timer: RTC: initialized.

12:47:30.329 -> <info> app: hello ble

12:47:30.329 -> <info> app: Before enter into sleep mode

12:47:30.329 -> <info> app: After enter into sleep mode

12:47:30.329 -> <info> app: Alarm status : 0

12:47:30.329 -> <info> app: Upper threshold : 30

12:47:30.329 -> <info> app: Lower threshold : 20

12:47:30.329 -> <info> app: Type C : 1

12:47:30.329 -> <info> app: Starting delay in sec. : 0

12:47:30.329 -> <info> app: Interval delay in sec.: 10

12:47:30.329 -> <info> app: Data EF4015

12:47:30.329 -> <info> app: Data3 15

12:47:30.329 -> <info> app: Data2 40

12:47:30.376 -> <info> app: Data1 EF

12:47:30.376 -> <info> app: Data0 0

12:47:30.376 -> <info> app: temporarylogcounter4 3 temporarylogcounter3 0 temporarylogcounter2  0 temporarylogcounter1 0

12:47:30.376 -> <info> app: log counter value : 3 

12:47:30.376 -> <info> app: Newpasskey12:123456

12:47:30.376 -> <info> app: Fast advertising

12:47:30.376 -> <info> app: start advertising

12:47:30.376 -> <info> app: Application started in Advertising Mode.

12:47:30.376 -> <info> app: Current Time service client started.

12:48:10.486 -> <info> app: Device Connected

12:48:10.486 -> <info> app: Connected.

12:48:11.282 -> <info> ble_cts_c: Current Time Service discovered at peer.

12:48:11.282 -> <info> app: Current Time Service discovered on server.

12:48:11.282 -> <info> app: Current Time received.

12:48:11.282 -> <info> app: 11/16/21-12:48:53

12:48:36.287 -> <info> app: passkeynew:123456

12:48:36.287 -> <info> app: passkeynew1:123456

12:48:36.287 -> <info> app: comaprision successful

12:49:11.552 -> <info> app: BeforeFivesec

12:49:11.552 -> <info> app: Data logging Mode.

12:49:11.552 -> <info> app: Bluetooth deactivated.

12:49:11.552 -> <info> app: Memory Initialization done.

12:49:11.552 -> <info> app: Fast advertising

12:49:11.552 -> <info> app: Device Disconnected

12:49:11.552 -> <info> app: Disconnect Complete.

12:49:11.552 -> <info> app: Disconnected.

12:49:11.552 -> <info> app: defaualtpasskey ******

12:49:11.552 -> <info> app: Temp Logging started hi.

12:49:11.552 -> <info> app: Timer started hi.

12:49:11.552 -> <info> app: Initial timer finished!

12:49:11.598 -> <info> app: data_to_send 25.75-11/16/21-12:49:12

12:49:11.598 -> <info> app: temp_write_page temp_write_offset bytes_to_write 0 0 23

12:49:11.598 -> <info> app: reading 1 done

12:49:11.598 -> <info> app: temporarylogcounter0 1 temporarylogcounter1 0 temporarylogcounter2  0 temporarylogcounter3 0

12:49:22.178 -> <info> app: data_to_send 25.63-11/16/21-12:49:22

12:49:22.178 -> <info> app: temp_write_page temp_write_offset bytes_to_write 0 23 23

12:49:22.225 -> <info> app: reading 2 done

12:49:22.225 -> <info> app: temporarylogcounter0 2 temporarylogcounter1 0 temporarylogcounter2  0 temporarylogcounter3 0

12:49:32.181 -> <info> app: data_to_send 25.63-11/16/21-12:49:32

12:49:32.181 -> <info> app: temp_write_page temp_write_offset bytes_to_write 0 46 23

12:49:32.228 -> <info> app: reading 3 done

12:49:32.228 -> <info> app: temporarylogcounter0 3 temporarylogcounter1 0 temporarylogcounter2  0 temporarylogcounter3 0

12:49:42.218 -> <info> app: data_to_send 25.63-11/16/21-12:49:42

12:49:42.218 -> <info> app: temp_write_page temp_write_offset bytes_to_write 0 69 23

12:49:42.218 -> <info> app: reading 4 done

12:49:42.218 -> <info> app: temporarylogcounter0 4 temporarylogcounter1 0 temporarylogcounter2  0 temporarylogcounter3 0

12:49:52.210 -> <info> app: data_to_send 25.50-11/16/21-12:49:52

12:49:52.210 -> <info> app: temp_write_page temp_write_offset bytes_to_write 0 92 23

12:49:52.210 -> <info> app: reading 5 done

12:49:52.210 -> <info> app: temporarylogcounter0 5 temporarylogcounter1 0 temporarylogcounter2  0 temporarylogcounter3 0

12:50:02.208 -> <info> app: data_to_send 25.63-11/16/21-12:50:02

12:50:02.208 -> <info> app: temp_write_page temp_write_offset bytes_to_write 0 115 23

12:50:02.208 -> <info> app: reading 6 done

12:50:02.208 -> <info> app: temporarylogcounter0 6 temporarylogcounter1 0 temporarylogcounter2  0 temporarylogcounter3 0

12:50:12.213 -> <info> app: data_to_send 25.50-11/16/21-12:50:12

12:50:12.213 -> <info> app: temp_write_page temp_write_offset bytes_to_write 0 138 23

12:50:12.213 -> <info> app: reading 7 done

12:50:12.213 -> <info> app: temporarylogcounter0 7 temporarylogcounter1 0 temporarylogcounter2  0 temporarylogcounter3 0

12:50:22.203 -> <info> app: data_to_send 25.50-11/16/21-12:50:22

12:50:22.203 -> <info> app: temp_write_page temp_write_offset bytes_to_write 0 161 23

12:50:22.203 -> <info> app: reading 8 done

12:50:22.203 -> <info> app: temporarylogcounter0 8 temporarylogcounter1 0 temporarylogcounter2  0 temporarylogcounter3 0

12:50:32.197 -> <info> app: data_to_send 25.63-11/16/21-12:50:32

12:50:32.197 -> <info> app: temp_write_page temp_write_offset bytes_to_write 0 184 23

12:50:32.197 -> <info> app: reading 9 done

12:50:32.197 -> <info> app: temporarylogcounter0 9 temporarylogcounter1 0 temporarylogcounter2  0 temporarylogcounter3 0

12:50:42.199 -> <info> app: data_to_send 25.63-11/16/21-12:50:42

12:50:42.199 -> <info> app: temp_write_page temp_write_offset bytes_to_write 0 207 23

12:50:42.199 -> <info> app: reading 10 done

12:50:42.199 -> <info> app: temporarylogcounter0 A temporarylogcounter1 0 temporarylogcounter2  0 temporarylogcounter3 0

12:50:52.188 -> <info> app: data_to_send 25.50-11/16/21-12:50:52

12:50:52.188 -> <info> app: temp_write_page temp_write_offset bytes_to_write 0 230 23

12:50:52.188 -> <info> app: reading 11 done

12:50:52.235 -> <info> app: temporarylogcounter0 B temporarylogcounter1 0 temporarylogcounter2  0 temporarylogcounter3 0

12:51:02.193 -> <info> app: data_to_send 25.63-11/16/21-12:51:02

12:51:02.193 -> <info> app: reading 12 done

12:51:02.193 -> <info> app: temporarylogcounter0 C temporarylogcounter1 0 temporarylogcounter2  0 temporarylogcounter3 0

12:51:12.203 -> <info> app: data_to_send 25.63-11/16/21-12:51:12

12:51:12.203 -> <info> app: temp_write_page temp_write_offset bytes_to_write 1 20 23

12:51:12.203 -> <info> app: reading 13 done

12:51:12.203 -> <info> app: temporarylogcounter0 D temporarylogcounter1 0 temporarylogcounter2  0 temporarylogcounter3 0

12:51:22.216 -> <info> app: data_to_send 25.63-11/16/21-12:51:22

12:51:22.216 -> <info> app: temp_write_page temp_write_offset bytes_to_write 1 43 23

12:51:22.216 -> <info> app: reading 14 done

12:51:22.216 -> <info> app: temporarylogcounter0 E temporarylogcounter1 0 temporarylogcounter2  0 temporarylogcounter3 0

12:51:32.177 -> <info> app: data_to_send 25.75-11/16/21-12:51:32

12:51:32.177 -> <info> app: temp_write_page temp_write_offset bytes_to_write 1 66 23

12:51:32.224 -> <info> app: reading 15 done

12:51:32.224 -> <info> app: temporarylogcounter0 F temporarylogcounter1 0 temporarylogcounter2  0 temporarylogcounter3 0

12:51:42.216 -> <info> app: data_to_send 25.63-11/16/21-12:51:42

12:51:42.216 -> <info> app: temp_write_page temp_write_offset bytes_to_write 1 89 23

12:51:42.216 -> <info> app: reading 16 done

12:51:42.216 -> <info> app: temporarylogcounter0 10 temporarylogcounter1 0 temporarylogcounter2  0 temporarylogcounter3 0

12:52:05.716 -> <info> app: BeforeFivesec

12:52:05.716 -> <info> app_timer: RTC: initialized.

12:52:05.716 -> <info> app: hello ble

12:52:05.716 -> <info> app: Before enter into sleep mode

12:52:05.716 -> <info> app: After enter into sleep mode

12:52:05.716 -> <info> app: Alarm status : 0

12:52:05.716 -> <info> app: Upper threshold : 30

12:52:05.716 -> <info> app: Lower threshold : 20

12:52:05.716 -> <info> app: Type C : 1

12:52:05.716 -> <info> app: Starting delay in sec. : 0

12:52:05.716 -> <info> app: Interval delay in sec.: 10

12:52:05.716 -> <info> app: Data EF4015

12:52:05.716 -> <info> app: Data3 15

12:52:05.763 -> <info> app: Data2 40

12:52:05.763 -> <info> app: Data1 EF

12:52:05.763 -> <info> app: Data0 0

12:52:05.763 -> <info> app: temporarylogcounter4 10 temporarylogcounter3 0 temporarylogcounter2  0 temporarylogcounter1 0

12:52:05.763 -> <info> app: log counter value : 16 

12:52:05.763 -> <info> app: Newpasskey12:123456

12:52:05.763 -> <info> app: Fast advertising

12:52:05.763 -> <info> app: start advertising

12:52:05.763 -> <info> app: Application started in Advertising Mode.

12:52:05.763 -> <info> app: Current Time service client started.

12:52:32.666 -> <info> app: Device Connected

12:52:32.666 -> <info> app: Connected.

12:52:33.414 -> <info> ble_cts_c: Current Time Service discovered at peer.

12:52:33.414 -> <info> app: Current Time Service discovered on server.

12:52:33.414 -> <info> app: Current Time received.

12:52:33.414 -> <info> app: 11/16/21-12:53:02

12:52:47.276 -> <info> app: passkeynew:123456

12:52:47.276 -> <info> app: passkeynew1:123456

12:52:47.276 -> <info> app: comaprision successful

12:53:01.240 -> <info> app: Logging started!

12:53:01.380 -> <info> app: tempread temp_read_page temp_read_offset bytes_to_read   0 0 23

12:53:01.380 -> <info> app: tempread temp_read_page temp_read_offset bytes_to_read   0 23 23

12:53:01.380 -> <info> app: tempread temp_read_page temp_read_offset bytes_to_read   0 46 23

12:53:01.380 -> <info> app: tempread temp_read_page temp_read_offset bytes_to_read   0 69 23

12:53:01.380 -> <info> app: tempread temp_read_page temp_read_offset bytes_to_read   0 92 23

12:53:02.270 -> <info> app: tempread temp_read_page temp_read_offset bytes_to_read   0 92 23

12:53:02.270 -> <info> app: tempread temp_read_page temp_read_offset bytes_to_read   0 115 23

12:53:02.270 -> <info> app: tempread temp_read_page temp_read_offset bytes_to_read   0 138 23

12:53:02.270 -> <info> app: tempread temp_read_page temp_read_offset bytes_to_read   0 138 23

12:53:02.318 -> <info> app: tempread temp_read_page temp_read_offset bytes_to_read   0 161 23

12:53:02.318 -> <info> app: tempread temp_read_page temp_read_offset bytes_to_read   0 184 23

12:53:02.318 -> <info> app: tempread temp_read_page temp_read_offset bytes_to_read   0 184 23

12:53:03.253 -> <info> app: tempread temp_read_page temp_read_offset bytes_to_read   0 184 23

12:53:03.300 -> <info> app: tempread temp_read_page temp_read_offset bytes_to_read   0 207 23

12:53:03.300 -> <info> app: tempread temp_read_page temp_read_offset bytes_to_read   0 230 23

12:53:03.300 -> <info> app: tempread temp_read_page temp_read_offset bytes_to_read   0 230 23

12:53:03.300 -> <info> app: tempread temp_read_page temp_read_offset bytes_to_read   1 20 23

12:53:03.300 -> <info> app: tempread temp_read_page temp_read_offset bytes_to_read   1 20 23

12:53:04.278 -> <info> app: tempread temp_read_page temp_read_offset bytes_to_read   1 20 23

12:53:04.278 -> <info> app: tempread temp_read_page temp_read_offset bytes_to_read   1 43 23

12:53:04.278 -> <info> app: tempread temp_read_page temp_read_offset bytes_to_read   1 66 23

12:53:04.278 -> <info> app: tempread temp_read_page temp_read_offset bytes_to_read   1 66 23

12:53:05.261 -> <info> app: tempread temp_read_page temp_read_offset bytes_to_read   1 66 23

12:53:05.261 -> <info> app: tempread temp_read_page temp_read_offset bytes_to_read   1 89 23

12:53:05.261 -> <info> app: ***All Readings have been sent.!!!***

12:53:22.263 -> <info> app: Fast advertising

12:53:22.263 -> <info> app: Device Disconnected

12:53:22.263 -> <info> app: Disconnect Complete.

12:53:22.263 -> <info> app: Disconnected.

12:53:22.263 -> <info> app: defaualtpasskey ******

RE: Connection parameters in nrf ble

Karl Ylvisaker — Mon, 15 Nov 2021 10:20:50 GMT

Please share logs using the Insert -> Code -> Text option rather than sharing screenshots of the logs. Proper formatting drastically increases readability and thus makes debugging easier.
Please also show me the log for the scenario in which the application seemingly stops after 16 logs.
Have you run a debugging session and checked out if the program counter gets stuck anywhere following the 16'th logging?

Please see my previous comment about the sniffer.
Could you capture a sniffer trace of these two scenarios in addition to the logs?

Best regards,
Karl

RE: Connection parameters in nrf ble

Ridhi — Mon, 15 Nov 2021 05:53:41 GMT

Karl pls look into at earliest

RE: Connection parameters in nrf ble

Ridhi — Sat, 13 Nov 2021 06:47:20 GMT

with above configuration i get many log values and logging continues:

but with

after 16 logs nothing happens and logs stop without any error but in power profiler i saw that logging stopped after 16 values

no value after 16 logs

RE: Connection parameters in nrf ble

Karl Ylvisaker — Fri, 12 Nov 2021 13:15:39 GMT

[quote user="RIDHIMA"]

ans: as suggested by you i had set :

#define MIN_CONN_INTERVAL MSEC_TO_UNITS(1000, UNIT_1_25_MS)
#define MAX_CONN_INTERVAL MSEC_TO_UNITS(1000, UNIT_1_25_MS)

and next time as:

[/quote]

Setting the peripheral's preference is not equal to verifying what connection interval that is actually being used. As mentioned the peripheral may only request an update of the parameters. It does not have any decision making powers over the central.
To verify which connection parameters are used you will either have to have the logger of the peripheral or central output the used connection parameters and updates or use the nRF Sniffer tool to see which interval is actually being used.

[quote user="RIDHIMA"]

and next time as:

#define MIN_CONN_INTERVAL MSEC_TO_UNITS(4000, UNIT_1_25_MS) /**< Minimum acceptable connection interval (0.5 seconds). */
#define MAX_CONN_INTERVAL MSEC_TO_UNITS(4000, UNIT_1_25_MS) /**< Maximum acceptable connection interval (1 second). */
#define SLAVE_LATENCY 1 /**< Slave latency. */
#define CONN_SUP_TIMEOUT MSEC_TO_UNITS(16010, UNIT_10_MS) /**< Connection supervisory time-out (4 seconds). */

then i got only 16 logs which rendered sleep afterwards.

[/quote]

Is there anything else unexpected that happens?
Does the device reset? Does anything unexpected appear in the logs you are seeing? Does the central device log anything unexpected?
Saying that you suddenly only see 16 logs does not provide me with any information to debug with.

I am not sure we will be getting anywhere with this until we see a sniffer trace. Could you capture a sniffer trace of these two scenarios, and upload the traces along with the peripheral's logs?
It is hard for me to suggest anything at all from your current description of the issue.

Best regards,
Karl

RE: Connection parameters in nrf ble

Ridhi — Fri, 12 Nov 2021 12:36:30 GMT

Could you also elaborate how you verified that the connection interval was actually 1000 and 4000 ms?

ans: as suggested by you i had set :

#define MIN_CONN_INTERVAL MSEC_TO_UNITS(1000, UNIT_1_25_MS)
#define MAX_CONN_INTERVAL MSEC_TO_UNITS(1000, UNIT_1_25_MS)

and next time as:

then i got only 16 logs which rendered sleep afterwards.

However with Connection Interval as:

#define MIN_CONN_INTERVAL MSEC_TO_UNITS(7.5, UNIT_1_25_MS)
#define MAX_CONN_INTERVAL MSEC_TO_UNITS(100, UNIT_1_25_MS)

device did not fall to sleep and gave logs continuously

RE: Connection parameters in nrf ble

Karl Ylvisaker — Fri, 12 Nov 2021 11:54:19 GMT

[quote user="RIDHIMA"]1). 'same issue' : is the issue i described in my previous comment, where the button press does not produce the expected logs when connection interval was 1000.[/quote]

Thank you for specifying.

[quote user="RIDHIMA"]

2). when i had set to 7.5-100ms the current between logs was

556.76 µA

but when connection interval was 1000ms it increased to

685.85 µA

why is the current between logs increasing?

[/quote]

It is hard for me to speculate about this without seeing the current code.
However, this might be another symptom of the issue you are seeing with the missing / less-than-expected logging. I suggest that we focus on resolving this issue first, so that we potentially does not spend time debugging a symptom that may go away when we resolve the root issue.

[quote user="RIDHIMA"]3). i didnt get what is the overflow you meant bcz with 7.5-100ms i am able to get many logs but not with changing interval to 1000ms [/quote]

What I meant is that there might be an overflow in your buffers if you change the connection interval from 7.5 ms to 1000 ms unless you have taken specific actions to accommodate for the increase in time between transfers.
For example, if you have a sensor you are reading from every 15 ms, that would mean 1 buffered packet between every other connection event. If you then change to 1000 ms connection interval, you will suddenly buffer 67 packets between each connection event. If the connection interval is the only thing that you have changed, there might be issues with the buffers overflowing when you make this change.
Again, this is just speculations on my part, since I have not actually seen the code in its current state.

Please also see my other previous questions:

[quote user="Karl Ylvisaker"]Could you also elaborate how you verified that the connection interval was actually 1000 and 4000 ms?[/quote][quote user="Karl Ylvisaker"]Is there any errors occurring when you use the 1000 ms connection interval? Does the device reset unexpectedly?[/quote]

Best regards,
Karl

RE: Connection parameters in nrf ble

Ridhi — Fri, 12 Nov 2021 05:53:26 GMT

1). 'same issue' : is the issue i described in my previous comment, where the button press does not produce the expected logs when connection interval was 1000.

2). when i had set to 7.5-100ms the current between logs was

556.76 µA

but when connection interval was 1000ms it increased to

685.85 µA

why is the current between logs increasing?

3). i didnt get what is the overflow you meant bcz with 7.5-100ms i am able to get many logs but not with changing interval to 1000ms

RE: Connection parameters in nrf ble

Karl Ylvisaker — Thu, 11 Nov 2021 14:53:03 GMT

Please be specific - which issue do you refer to when you say 'same issue'?
Is it the issue you described in your previous comment, where the buttonpress does not produce the expected logs, or is it the issue you had before with being unable to set the desired connection parameters? The former sounds like an application logic issue, and the latter sounds like a configuration issue.

Could you also elaborate how you verified that the connection interval was actually 1000 and 4000 ms?

Best regards,
Karl

RE: Connection parameters in nrf ble

Ridhi — Thu, 11 Nov 2021 09:23:25 GMT

yes i have verified this infact i also did with

as told by you. still it is giving same issue

but with values as 7.5-100 ms it works fine

RE: Connection parameters in nrf ble

Karl Ylvisaker — Thu, 11 Nov 2021 09:21:30 GMT

It is hard for me to say anything about what might be going on here, from your description alone. Is there any errors occurring when you use the 1000 ms connection interval? Does the device reset unexpectedly?
I would think that you might get buffer overflows etc when increasing the connection interval by this much, if you have not also made changes to your sensor-data buffer sizes.
Have you verified that the connection interval being used is actually 1000 ms?

Best regards,
Karl

RE: Connection parameters in nrf ble

Ridhi — Thu, 11 Nov 2021 08:50:40 GMT

Hello Karl

I have a ble nrf52832 dev kit. I have interfaced flash and temp sensor STTS with it. I am using it for temp data logging. I have intially set the connection parameters as:

#define MIN_CONN_INTERVAL MSEC_TO_UNITS(7.5, UNIT_1_25_MS)
#define MAX_CONN_INTERVAL MSEC_TO_UNITS(100, UNIT_1_25_MS)

#define SLAVE_LATENCY 0
#define CONN_SUP_TIMEOUT MSEC_TO_UNITS(9000, UNIT_10_MS) /
#define FIRST_CONN_PARAMS_UPDATE_DELAY APP_TIMER_TICKS(5000)
#define NEXT_CONN_PARAMS_UPDATE_DELAY APP_TIMER_TICKS(3000) /
#define MAX_CONN_PARAMS_UPDATE_COUNT 3

I press a button my device advertsises

then i connect using nrf connect app

.Created a custom service ,

press button deevice goes to logging mode and gives abot 20 logs for 10 mins say.

then i again press button to put device in sleep mode

then again press button to re advertise and connect on app

then enable notification of the created service and then read the temp logs.

with above connection parameters i am able to get the logs but when i set the values for power optimization as:

#define MIN_CONN_INTERVAL MSEC_TO_UNITS(1000, UNIT_1_25_MS)
#define MAX_CONN_INTERVAL MSEC_TO_UNITS(1000, UNIT_1_25_MS)

i am only able to get 4 logs just for 1 min and then my system is going to sleep state instead of giving logs

RE: Connection parameters in nrf ble

Karl Ylvisaker — Thu, 28 Oct 2021 07:39:36 GMT

[quote user="RIDHIMA"]i have slave latency of 0 say, in nordic blinky code there are two services: button and led. how will pheripheral know that it has no data to send so it sets the slave latency.[/quote]

I am sorry to hear that, RIDHIMA. Please do not hesitate to ask if any part of my answer should be unclear, so that I may elaborate.

[quote user="RIDHIMA"]say i have nordic blinky code and i set the supervision timeout as 4 secs. i am not getting what and how this we can see its effect on nrf connect app. [/quote]

The simplest explanation of the connection supervision timeout is: "It is how long will the device attempt to contact a peer that has stopped responding"
So, if you have 4 s supervision timeout on your peripheral, and you are in connection with a nRF Connect central. If the central stops responding to the peripheral (they both expect to exchange a packet at least for once every connection interval) such as if it leaves the area, or goes into an elevator or similar, they will both still try to communicate with each other for each passing connection interval - in hopes that they will hear from each other again, and continue the connection. The connection supervision timeout tells them how long they should keep trying to reach the peer that is no longer responding.
When a connection is terminated the devices will usually go back into either scanning or advertising so that they can find a new connection. This will not happen until the connection supervision timeout has expired., because both devices still consider the connection as working so long as it has not expired (even though they do not hear anything from their peer).

[quote user="RIDHIMA"]how will pheripheral know that it has no data to send so it sets the slave latency.[/quote]

The peripheral can know this by checking the contents of the packet it intends to send in the upcoming connection event.
If the packet is empty and the slave latency is > 0 it can skip the upcomming connection event. If the packet is non-empty (contains data) it should transmit during the event.

Best regards,
Karl