Abrupt increase in the current readings Amidst Logs in Temperature Data Logger after connecting the peripheral while in the Advertising mode.

RE: Abrupt increase in the current readings Amidst Logs in Temperature Data Logger after connecting the peripheral while in the Advertising mode.

Simonr — Fri, 26 Nov 2021 09:00:09 GMT

Thank you for the traces. It does not seem like this extra current is tied to a changed connection interval, and it seems like the spikes are consistently occurring every ~190ms so the most likely culprit is a timer somewhere that triggers and wakes the chip every 190ms. Can you provide some more details on what your application does exactly? Can you also explain how exactly you measure the current consumption. Do you measure the current on a DK or on a custom board, and do you measure the current of the entire board or just the nRF?

What do you mean by "stops logging after 3 logs" exactly? What is one log in this context, one BLE/connection event, or one set of data in I.E. a UART log? I would imagine it goes to sleep after these three logs, which is why it stops. Please check what other functions use the connection interval defines in their functions. You can also do a diff between to make sure that only the connection interval has been changed in the two applications.

Best regards,

Simon

RE: Abrupt increase in the current readings Amidst Logs in Temperature Data Logger after connecting the peripheral while in the Advertising mode.

Ankush — Thu, 25 Nov 2021 11:04:30 GMT

I have uploaded the trace of cases 1 and 2 separately as well as combinedly
devzone.nordicsemi.com/.../Trace_5F00_1_5F00_2_5F00_1_2B00_2.zip

[quote userid="75734" url="~/f/nordic-q-a/81957/abrupt-increase-in-the-current-readings-amidst-logs-in-temperature-data-logger-after-connecting-the-peripheral-while-in-the-advertising-mode/340528#340528"]Are any other parameters affected by the changed connection intervals?[/quote]

Yea, you'll notice that in case 2 the BLE peripheral automatically stops logging after 3 logs, which is not the case in case 1. Kindly explain the reason behind this as well.

RE: Abrupt increase in the current readings Amidst Logs in Temperature Data Logger after connecting the peripheral while in the Advertising mode.

Simonr — Wed, 24 Nov 2021 11:59:08 GMT

Can you export the PPK trace of Case 2 and upload it here on DevZone in a .zip file so we can do a review. Or alternatively zoom in on the events between the data logging events so we can get a better look at them to determine if it's just random noise or BLE events (which it looks like).

My guess is that the slave latency is affected by the connection interval changing, and that this causes more BLE activity than you bargain for. Are any other parameters affected by the changed connection intervals?

Best regards,

Simon

RE: Abrupt increase in the current readings Amidst Logs in Temperature Data Logger after connecting the peripheral while in the Advertising mode.

Ankush — Tue, 23 Nov 2021 10:15:01 GMT

Hi there!
Your quick response is appreciated,

[quote userid="75734" url="~/f/nordic-q-a/81957/abrupt-increase-in-the-current-readings-amidst-logs-in-temperature-data-logger-after-connecting-the-peripheral-while-in-the-advertising-mode/340232#340232"]Is the connection interval the only thing you change between cases 1 and 2?[/quote]

Yes!

I am using STTS751 Temperature Sensor and W25Q16 Flash Memory.

[quote userid="75734" url="~/f/nordic-q-a/81957/abrupt-increase-in-the-current-readings-amidst-logs-in-temperature-data-logger-after-connecting-the-peripheral-while-in-the-advertising-mode/340232#340232"]You're using a PPK2 to do all these measurements, correct?[/quote]

Yes!

[quote userid="75734" url="~/f/nordic-q-a/81957/abrupt-increase-in-the-current-readings-amidst-logs-in-temperature-data-logger-after-connecting-the-peripheral-while-in-the-advertising-mode/340232#340232"]Are the sampling parameters set to the same value in case 1 and 2?[/quote]

Yes! they're the same for cases 1 and 2.
For the 3rd instance, I am attaching an image below with similar sampling parameters

[quote userid="75734" url="~/f/nordic-q-a/81957/abrupt-increase-in-the-current-readings-amidst-logs-in-temperature-data-logger-after-connecting-the-peripheral-while-in-the-advertising-mode/340232#340232"]Also, what device is this central device?[/quote]

I am using nRF Connect Android app on my smartphone.

[quote userid="75734" url="~/f/nordic-q-a/81957/abrupt-increase-in-the-current-readings-amidst-logs-in-temperature-data-logger-after-connecting-the-peripheral-while-in-the-advertising-mode/340232#340232"]Can you confirm that the device actually communicates with the central in case 1, doing this data logging at all?[/quote]

Like I said:
The data logger functions first in the Advertising mode followed by the data logging mode and then Sleep mode. It wakes up in the advertising mode where the Central is connected to read the logs.
So, in cases 1 and 2, I am connecting the Logger in the Advertising mode, but in case 3, I am putting the Logger directly into the data-logging mode without firstly connecting it in the advertising mode.

RE: Abrupt increase in the current readings Amidst Logs in Temperature Data Logger after connecting the peripheral while in the Advertising mode.

Simonr — Tue, 23 Nov 2021 07:02:11 GMT

Is the connection interval the only thing you change between cases 1 and 2? From the consistent activity I would think this was the nRF reading data from a sensor for example, or using some other peripheral continuously. You're using a PPK2 to do all these measurements, correct? Are the sampling parameters set to the same value in case 1 and 2? I see that they're not in cases 2 and 3 for instance. Can you confirm that the device actually communicates with the central in case 1, doing this data logging at all? Also, what device is this central device?

Best regards,

Simon