<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Rerouting AT interface for power measurement using external supply</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/76896/rerouting-at-interface-for-power-measurement-using-external-supply</link><description>Hi there, 
 We received your devkits on Friday, 25th of June and started evaluation of the modules this morning (Magnus Pederson and Brian Kim @ Nordic arranged the devkits for us). We are able to successfully connect to the network and do current measurements</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 08 Jul 2021 10:38:30 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/76896/rerouting-at-interface-for-power-measurement-using-external-supply" /><item><title>RE: Rerouting AT interface for power measurement using external supply</title><link>https://devzone.nordicsemi.com/thread/319122?ContentTypeID=1</link><pubDate>Thu, 08 Jul 2021 10:38:30 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:3c62047b-b1bc-49be-98f4-a28ad550fec3</guid><dc:creator>Frikkie Badenhorst</dc:creator><description>&lt;p&gt;Thanks Stian, your help has been extremely helpful in testing the module! Have a lovely summer time!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Rerouting AT interface for power measurement using external supply</title><link>https://devzone.nordicsemi.com/thread/318958?ContentTypeID=1</link><pubDate>Wed, 07 Jul 2021 11:16:54 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c8b235a6-4e72-43c2-ac96-238cbba2251a</guid><dc:creator>Stian R&amp;#248;ed Hafskjold</dc:creator><description>&lt;p&gt;And:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;The default keepalive time can be specified with the `CONFIG_MQTT_KEEPALIVE` Kconfig option.&lt;/p&gt;
&lt;/blockquote&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Rerouting AT interface for power measurement using external supply</title><link>https://devzone.nordicsemi.com/thread/318938?ContentTypeID=1</link><pubDate>Wed, 07 Jul 2021 09:39:39 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a9144986-df8f-4243-aa49-c4ef6543cb56</guid><dc:creator>Stian R&amp;#248;ed Hafskjold</dc:creator><description>&lt;p&gt;Feedback from the SW developers:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;MQTT is over TLS or TCP, which is restricted by MSS of modem IP stack (708) for one packet. But APP side does not really need to care about this, as MQTT lib loops to send out MQTT payload in multiple packets.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://github.com/zephyrproject-rtos/zephyr/blob/main/subsys/net/lib/mqtt/mqtt_transport_socket_tls.c#L107"&gt;https://github.com/zephyrproject-rtos/zephyr/blob/main/subsys/net/lib/mqtt/mqtt_transport_socket_tcp.c#L69&lt;br /&gt;https://github.com/zephyrproject-rtos/zephyr/blob/main/subsys/net/lib/mqtt/mqtt_transport_socket_tls.c#L107&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;To publish in normal AT command mode, it’s limited by MQTT_MESSAGE_BUFFER_LEN defined for SLM/MQTT service, which has a default value of below:&lt;/p&gt;
&lt;p&gt;&lt;code&gt;#define MQTT_MESSAGE_BUFFER_LEN NET_IPV4_MTU&lt;/code&gt;&lt;/p&gt;
&lt;p&gt;You can increase the MQTT_MESSAGE_BUFFER_LEN to send/receive larger payload. The other limitation are the size of AT command/response. Current AT command size is limited to 4096:&lt;/p&gt;
&lt;p&gt;&lt;a href="https://github.com/nrfconnect/sdk-nrf/blob/master/applications/serial_lte_modem/src/slm_at_host.c#L32"&gt;https://github.com/nrfconnect/sdk-nrf/blob/master/applications/serial_lte_modem/src/slm_at_host.c#L32&lt;/a&gt; &lt;/p&gt;
&lt;p&gt;And the AT response size is limited to 1152 (twice of CONFIG_SLM_SOCKET_RX_MAX):&lt;/p&gt;
&lt;p&gt;&lt;a href="https://github.com/nrfconnect/sdk-nrf/blob/master/applications/serial_lte_modem/src/slm_at_host.c#L72"&gt;https://github.com/nrfconnect/sdk-nrf/blob/master/applications/serial_lte_modem/src/slm_at_host.c#L72&lt;/a&gt; &lt;/p&gt;
&lt;p&gt;These values can be changed too.&lt;/p&gt;
&lt;p&gt;In NCSv1.6.0, we added support for datamode for MQTT publish, for which the MQTT payload is only limited by datamode buffer limitation, i.e. half of AT command buffer size – DMA block size = 4096/2 – 256 = 1792 bytes.&lt;/p&gt;
&lt;/blockquote&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Rerouting AT interface for power measurement using external supply</title><link>https://devzone.nordicsemi.com/thread/318786?ContentTypeID=1</link><pubDate>Tue, 06 Jul 2021 12:20:35 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:80adf1a4-acc3-48d8-b8a7-6a05da9beabf</guid><dc:creator>Stian R&amp;#248;ed Hafskjold</dc:creator><description>&lt;p&gt;Hi I&amp;#39;m sorry, waiting for feedback from one of the SW engineers. Due to summer holidays many of the modem experts are out of office, so things take a bit longer. Anyways, I don&amp;#39;t think this is any hard limitation of the modem. If you just set up a TCP socket connection, the network MTU should be at least 1500 (if I remember correctly). I don&amp;#39;t know how this translates into the MQTT protocol though. Maybe Didrik&amp;#39;s answer here can shed some light: &lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/58357/nrf9160-packet-data-receive-buffer-size/238816#238816"&gt;https://devzone.nordicsemi.com/f/nordic-q-a/58357/nrf9160-packet-data-receive-buffer-size/238816#238816&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Rerouting AT interface for power measurement using external supply</title><link>https://devzone.nordicsemi.com/thread/318676?ContentTypeID=1</link><pubDate>Mon, 05 Jul 2021 15:13:50 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f89b1736-fb0b-4753-abcb-ee1716b2b1d4</guid><dc:creator>Frikkie Badenhorst</dc:creator><description>&lt;p&gt;Hi Stian,&lt;/p&gt;
&lt;p&gt;Could you please provide some clarity on this as soon as possible?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Rerouting AT interface for power measurement using external supply</title><link>https://devzone.nordicsemi.com/thread/318296?ContentTypeID=1</link><pubDate>Thu, 01 Jul 2021 16:38:25 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d6dd4137-749a-42ef-b0d1-c04851b52c39</guid><dc:creator>Frikkie Badenhorst</dc:creator><description>&lt;p&gt;Hi Stian, I have identified another important question:&lt;/p&gt;
&lt;p&gt;According to the&lt;a href="https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/applications/serial_lte_modem/doc/MQTT_AT_commands.html"&gt; MQTT AT command used with this Serial LTE&lt;/a&gt; Modem app allows only a max publish payload of 576 bytes. Is this only limited by the application itself and can be increased by simply adjusting a variable, or is this a hard limitation of the modem? I cant think 576 is the max payload, thus I believe it is the former.&lt;/p&gt;
&lt;p&gt;I also believe we will be able to specify our own MQTT keep-alive time, and not the default 60 seconds?&lt;/p&gt;
&lt;p&gt;I am asking this on this ticket, as this is still related to the hex file you prepared for us!&lt;/p&gt;
&lt;p&gt;Thanks!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Rerouting AT interface for power measurement using external supply</title><link>https://devzone.nordicsemi.com/thread/318268?ContentTypeID=1</link><pubDate>Thu, 01 Jul 2021 14:23:08 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:814f6c97-be9a-46fd-92d0-fd37e730c1ff</guid><dc:creator>Frikkie Badenhorst</dc:creator><description>&lt;p&gt;Ok for now we are still not able to get it in a lower power between DRX cycles. Will have to look into the setting of the field on the SIM. When testing a modem from a different manufacturer however, we are not seeing this, which makes me wonder if it is indeed the SIM.&lt;/p&gt;
&lt;p&gt;Nonetheless for now we can work with this value we are seeing as a test.&lt;/p&gt;
&lt;p&gt;Thanks for all your assistance, Stian.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Rerouting AT interface for power measurement using external supply</title><link>https://devzone.nordicsemi.com/thread/318246?ContentTypeID=1</link><pubDate>Thu, 01 Jul 2021 13:27:33 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:393b5e48-1580-4a70-90b2-447766ad0eb8</guid><dc:creator>Stian R&amp;#248;ed Hafskjold</dc:creator><description>&lt;p&gt;The text marked in red in the previous answer is kind of important as well. This field has to be set in the SIM, which it&amp;#39;s usually not by default. If you have a regular test-SIM for your callbox, you probably have the ADM key and can change this field.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Rerouting AT interface for power measurement using external supply</title><link>https://devzone.nordicsemi.com/thread/318244?ContentTypeID=1</link><pubDate>Thu, 01 Jul 2021 13:22:58 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:99341cf0-15fd-4375-bc92-97d5d7eb0e49</guid><dc:creator>Stian R&amp;#248;ed Hafskjold</dc:creator><description>&lt;p&gt;Sorry, forgot to mention, you need to set the power saving profile. Use the &lt;a href="https://infocenter.nordicsemi.com/topic/ref_at_commands/REF/at_commands/mob_termination_ctrl_status/xdataprfl_set.html?cp=2_1_4_16_0"&gt;AT%XDATAPRFL&lt;/a&gt; command and set the level to 0.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;The power saving level has an effect on the shutdown of the UICC during &lt;a title="A method to conserve the battery of an IoT (Internet of Things) device by allowing it to remain inactive for extended periods." href="https://infocenter.nordicsemi.com/topic/ref_at_commands/dita_common/glossary/glossary.html#edrx"&gt;&lt;dfn&gt;Extended Discontinuous Reception (eDRX)&lt;/dfn&gt;&lt;/a&gt; cycles. On power level 0, the modem deactivates the UICC if the eDRX period is longer than 60 seconds and &lt;span style="color:rgba(255, 0, 0, 1);"&gt;UICC deactivation is allowed through EF-AD under USIM ADF.&lt;/span&gt; The modem activates the UICC and performs the necessary checks before setting up any signaling or data connections with the network. Otherwise, the UICC is not activated because of modem functionality.&lt;/p&gt;
&lt;p&gt;On power levels 1–4, the modem deactivates the UICC if the eDRX cycles are longer than 10 minutes. The UICC is activated before any signaling or data connections are set up with the network and when waking up from eDRX. This means that the UICC is deactivated and activated at every eDRX cycle.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Rerouting AT interface for power measurement using external supply</title><link>https://devzone.nordicsemi.com/thread/318222?ContentTypeID=1</link><pubDate>Thu, 01 Jul 2021 12:49:38 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7ff2f0ee-17e9-400b-b0c2-90c567c90d15</guid><dc:creator>Frikkie Badenhorst</dc:creator><description>&lt;p&gt;Thanks Stian, we have a fully configurable test network and base station (Amarisoft Callbox Mini), so we force the network to basically accept any timer request by the UEs.&lt;/p&gt;
&lt;p&gt;When using the 5 minute TAU wakeup and 0 minute active time as you mentioned, I can see the device going into a 3uA state.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;However, as a test I am setting the following:&lt;/p&gt;
&lt;p&gt;Active timer: 30minutes&amp;nbsp;&lt;/p&gt;
&lt;p&gt;TAU: 7 hours&lt;/p&gt;
&lt;p&gt;eDRX cycle: 655sec (+- 11 minutes)&lt;/p&gt;
&lt;p&gt;PTW: 5.12 sec&lt;/p&gt;
&lt;p&gt;From this,&amp;nbsp;&lt;/p&gt;
[quote userid="4556" url="~/f/nordic-q-a/76896/rerouting-at-interface-for-power-measurement-using-external-supply/318180#318180"]This is probably due to the SIM card being active. The SIM is active if the DRX interval (the spikes you see every 640ms (?)) is less than 1 minute[/quote]
&lt;p&gt;I would think that the SIM should be deactived since the DRX cycle is larger than 1minute, but we still see the 39uA current after the PTW is complete:&lt;/p&gt;
&lt;p&gt;&lt;img alt=" " src="https://devzone.nordicsemi.com/resized-image/__size/320x240/__key/communityserver-discussions-components-files/4/pastedimage1625143658838v1.png" /&gt;&lt;/p&gt;
&lt;p&gt;Is this expected behaviour? Then I guess that the SIM card is always active during the active time, regardless of the DRX cycle?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Rerouting AT interface for power measurement using external supply</title><link>https://devzone.nordicsemi.com/thread/318180?ContentTypeID=1</link><pubDate>Thu, 01 Jul 2021 11:59:19 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:3a38d005-da3f-4aaf-9d1b-69467fb81256</guid><dc:creator>Stian R&amp;#248;ed Hafskjold</dc:creator><description>&lt;p&gt;This is probably due to the SIM card being active. The SIM is active if the DRX interval (the spikes you see every 640ms (?)) is less than 1 minute.&lt;/p&gt;
&lt;p&gt;You can check this by measuring the voltage on the SIM current measurement header. If it&amp;#39;s 1.8V the SIM is in clock stop mode and is consuming between 20-100 uA depending on the SIM card. It should be 0V when the SIM is shut down.&lt;/p&gt;
&lt;p&gt;Try to put the modem in PSM mode, which will turn off the SIM, to get the lowest current consumption. The following AT command requests PSM mode with a 5 minute (&amp;quot;10001010&amp;quot;) TAU wakeup interval, and the active time set to 0 (&amp;quot;00000000&amp;quot;). The active time specifies how long the modem should stay in DRX mode after going to PSM, after each wakeup.&lt;/p&gt;
&lt;pre&gt;AT+CPSMS=1,&amp;quot;&amp;quot;,&amp;quot;&amp;quot;,&amp;quot;10001010&amp;quot;,&amp;quot;00000000&amp;quot;&lt;/pre&gt;
&lt;p&gt;You should also enable unsolicited notifications at level 5, which will return the PSM settings which is actually given by the network. It does not always match the requested ones.&lt;/p&gt;
&lt;pre&gt;AT+CEREG=5&lt;br /&gt;AT+CEREG?&lt;/pre&gt;
&lt;p&gt;The response should look something like this:&lt;/p&gt;
&lt;pre&gt;+CEREG: 1,&amp;quot;7BD5&amp;quot;,&amp;quot;0106C601&amp;quot;,7,0,2,&lt;span style="color:rgba(255, 0, 0, 1);"&gt;&amp;quot;00000000&amp;quot;,&amp;quot;10001010&amp;quot;&lt;br /&gt;&lt;/span&gt;&lt;/pre&gt;
&lt;p&gt;If the fields in red above are set to 11100000, PSM is not activated and might not be supported by the network&lt;/p&gt;
&lt;p&gt;&lt;a href="https://infocenter.nordicsemi.com/topic/ref_at_commands/REF/at_commands/nw_service/cereg_set.html?cp=2_1_7_7_0"&gt;https://infocenter.nordicsemi.com/topic/ref_at_commands/REF/at_commands/nw_service/cereg_set.html?cp=2_1_7_7_0&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="https://infocenter.nordicsemi.com/topic/ref_at_commands/REF/at_commands/nw_service/cpsms_set.html?cp=2_1_7_2_0"&gt;https://infocenter.nordicsemi.com/topic/ref_at_commands/REF/at_commands/nw_service/cpsms_set.html?cp=2_1_7_2_0&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Rerouting AT interface for power measurement using external supply</title><link>https://devzone.nordicsemi.com/thread/318158?ContentTypeID=1</link><pubDate>Thu, 01 Jul 2021 11:09:20 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:182d40fc-e8c4-4ebe-9b03-aacf78aafd75</guid><dc:creator>Frikkie Badenhorst</dc:creator><description>&lt;p&gt;Hi Stian, it looks as if we are still seeing a base current of 30-40uA with 8547.merged.hex in the idle state.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;img alt=" " src="https://devzone.nordicsemi.com/resized-image/__size/320x240/__key/communityserver-discussions-components-files/4/pastedimage1625137696195v2.png" /&gt;&lt;/p&gt;
&lt;p&gt;We have tried both AT#XSLEEP=0 and AT#XSLEEP=1&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Rerouting AT interface for power measurement using external supply</title><link>https://devzone.nordicsemi.com/thread/318144?ContentTypeID=1</link><pubDate>Thu, 01 Jul 2021 10:22:08 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6a16b942-b59c-4d0f-b522-7031f28f04f2</guid><dc:creator>Frikkie Badenhorst</dc:creator><description>&lt;p&gt;Excellent, thanks Stian! Your help is greatly appreciated&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Rerouting AT interface for power measurement using external supply</title><link>https://devzone.nordicsemi.com/thread/318143?ContentTypeID=1</link><pubDate>Thu, 01 Jul 2021 10:15:28 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:36b7051f-9c69-44b5-9466-dbd2a49a6458</guid><dc:creator>Stian R&amp;#248;ed Hafskjold</dc:creator><description>&lt;p&gt;Yes, here is a new hex file with the expected idle current: &lt;a href="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/8547.merged.hex"&gt;devzone.nordicsemi.com/.../8547.merged.hex&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Rerouting AT interface for power measurement using external supply</title><link>https://devzone.nordicsemi.com/thread/318119?ContentTypeID=1</link><pubDate>Thu, 01 Jul 2021 08:35:23 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a4044fe5-e92f-4015-89fe-aae277e47064</guid><dc:creator>Frikkie Badenhorst</dc:creator><description>&lt;p&gt;Thanks Stian.&lt;/p&gt;
&lt;p&gt;I have accidentally closed the ticket, but I believe you are still preparing the update LTE Serial Modem app which will allow the expected idle current.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Rerouting AT interface for power measurement using external supply</title><link>https://devzone.nordicsemi.com/thread/318114?ContentTypeID=1</link><pubDate>Thu, 01 Jul 2021 08:18:30 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ec235ecc-14ae-4cc1-9acb-839ee85b1ee4</guid><dc:creator>Stian R&amp;#248;ed Hafskjold</dc:creator><description>&lt;p&gt;Hi, button 1 on the DK should wake the device up again&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Rerouting AT interface for power measurement using external supply</title><link>https://devzone.nordicsemi.com/thread/318105?ContentTypeID=1</link><pubDate>Thu, 01 Jul 2021 07:50:50 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a62474f0-ce9e-4cdc-9f36-2ecffd0b4a5e</guid><dc:creator>Frikkie Badenhorst</dc:creator><description>&lt;p&gt;Hi Stian,&lt;/p&gt;
&lt;p&gt;after calling AT#XSLEEP, how can we wake the device/UARTs up again so that we can send some more AT commands?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Rerouting AT interface for power measurement using external supply</title><link>https://devzone.nordicsemi.com/thread/317926?ContentTypeID=1</link><pubDate>Wed, 30 Jun 2021 10:40:33 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:612db689-b71e-4238-98e3-e5945d0be50b</guid><dc:creator>Frikkie Badenhorst</dc:creator><description>&lt;p&gt;Thank you Stian! Looking forward to seeing the device in operation!&lt;/p&gt;
&lt;p&gt;Please keep me updated on the updated hex file, thanks&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Rerouting AT interface for power measurement using external supply</title><link>https://devzone.nordicsemi.com/thread/317923?ContentTypeID=1</link><pubDate>Wed, 30 Jun 2021 10:22:15 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6057ee1c-ea17-4baf-b4be-b7f89e034843</guid><dc:creator>Stian R&amp;#248;ed Hafskjold</dc:creator><description>&lt;p&gt;Hi, sorry for the late reply. Here a hex file for you: &lt;a href="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/3005.merged.hex"&gt;devzone.nordicsemi.com/.../3005.merged.hex&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;It is currently consuming 30 uA in idle, after calling AT#XSLEEP=0, ideally you should see around 2-3 uA. So I will have to look into what changes they made in the newest NCS release v1.6.0 in order to get it down to the expected idle current. Anyways, you should be able to get started with the hex I posted above, and I will get back to you shortly with an updated one.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Rerouting AT interface for power measurement using external supply</title><link>https://devzone.nordicsemi.com/thread/317916?ContentTypeID=1</link><pubDate>Wed, 30 Jun 2021 09:44:59 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:43a3d26e-0c06-4928-b114-18cc623a216b</guid><dc:creator>Frikkie Badenhorst</dc:creator><description>&lt;p&gt;Hi Stian, will you be able to provide the hex files of the Serial LTE Modem app? It is very urgent as we need to do testing on the hardware as soon as possible.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;We are having issues with installing the SDK and SES as mentioned here,&amp;nbsp;&lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/76895/zephyr-base-not-set-and-open-ide-not-present-in-toolchain-manager/317882#317882"&gt;https://devzone.nordicsemi.com/f/nordic-q-a/76895/zephyr-base-not-set-and-open-ide-not-present-in-toolchain-manager/317882#317882&lt;/a&gt;&amp;nbsp;, so cant build the application ourselves.&lt;/p&gt;
&lt;p&gt;Thanks a lot for your help so far!&lt;/p&gt;
&lt;p&gt;Regards,&lt;/p&gt;
&lt;p&gt;Frikkie&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Rerouting AT interface for power measurement using external supply</title><link>https://devzone.nordicsemi.com/thread/317760?ContentTypeID=1</link><pubDate>Tue, 29 Jun 2021 14:25:13 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b4c2f741-e006-43a8-a3ca-08cd439415c2</guid><dc:creator>Frikkie Badenhorst</dc:creator><description>&lt;p&gt;Setting up our own test environment, is exactly what we want to do and the Serial LTE Modem application sounds perfect. As mentioned, for now we are having issues installing the SDK and SES.&lt;/p&gt;
&lt;p&gt;Would you be so kind to provide me with the HEX files of this application, which I can use with the Programmer tool provided in nRF Connect for Desktop to flash the app?&lt;/p&gt;
&lt;p&gt;Thanks so much, Stian.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Rerouting AT interface for power measurement using external supply</title><link>https://devzone.nordicsemi.com/thread/317756?ContentTypeID=1</link><pubDate>Tue, 29 Jun 2021 14:13:26 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:23b27943-6d4a-4984-90dc-23312a27afcb</guid><dc:creator>Stian R&amp;#248;ed Hafskjold</dc:creator><description>&lt;p&gt;I don&amp;#39;t think we have any precompiled examples in the SDK, but I could probably create some hex files for you if you want.&lt;/p&gt;
&lt;p&gt;I would recommend starting with the &lt;a href="http://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/samples/nrf9160/udp/README.html"&gt;UDP sample&lt;/a&gt;. It transfers a UDP packet at a regular interval and going into PSM or eDRX idle between the transfers. It&amp;#39;s power optimized and easily configurable from the .conf file. If you want I can create a hex file with the parameters you want.&lt;/p&gt;
&lt;p&gt;Alternatively, you can use the &lt;a href="http://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/applications/serial_lte_modem/doc/slm_description.html"&gt;Serial LTE Modem&lt;/a&gt; application. This is based on using a terminal to submit AT commands to the modem over UART, so you can set up your own test environment. Then before doing current measurements you can issue the &lt;a href="http://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/applications/serial_lte_modem/doc/Generic_AT_commands.html#power-saving-xsleep"&gt;AT+XSLEEP&lt;/a&gt; command to turn off UART and putting the nRF91 in the lowest power mode.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Rerouting AT interface for power measurement using external supply</title><link>https://devzone.nordicsemi.com/thread/317693?ContentTypeID=1</link><pubDate>Tue, 29 Jun 2021 11:57:59 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:368808a3-1bf8-4a69-8772-a100370470aa</guid><dc:creator>Frikkie Badenhorst</dc:creator><description>&lt;p&gt;Hi Stian,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Thank you for your response. Yes the SMU looks as if it will work.&lt;/p&gt;
&lt;p&gt;Also, what application can we flash onto the the SiP in order to do manual current testing?&amp;nbsp;&lt;/p&gt;
&lt;p&gt;We currently have the asset tracker application flashed onto the module, however we are having issues installing the nRD Connect SDK and getting it running with SEGGER Embedded Studio (I have created a seperate ticked for that), so thus for now cannot create our own custom apps.&lt;/p&gt;
&lt;p&gt;Should simply erasing the firmware on the app processor be fine?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Rerouting AT interface for power measurement using external supply</title><link>https://devzone.nordicsemi.com/thread/317686?ContentTypeID=1</link><pubDate>Tue, 29 Jun 2021 11:47:37 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2d559fd8-8863-4cff-92c7-45ea32bd8892</guid><dc:creator>Stian R&amp;#248;ed Hafskjold</dc:creator><description>&lt;p&gt;Hi, please follow my guide here on how to measure current on the nRF9160 DK: &lt;a href="https://devzone.nordicsemi.com/nordic/cellular-iot-guides/b/hardware-design/posts/getting-started-with-current-measurements-on-the-nrf9160"&gt;https://devzone.nordicsemi.com/nordic/cellular-iot-guides/b/hardware-design/posts/getting-started-with-current-measurements-on-the-nrf9160&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;I think the easiest way is using the SMU method, then you can supply P22 directly with the voltage you need and measure current at the same time. You leave the USB cable plugged in for UART/debugging, and the USB will then power everything on the DK except the nRF91 VDD itself. So there will be now leakage current from the nRF91 to the rest of the DK, nor will the nRF91 be powered by the USB. &lt;/p&gt;
&lt;p&gt;No modifications to the DK are needed, and SW6 can be left in the default position.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>