How do I receive the return value of these AT instruction subscription messages?

[peter.min]

1. I tested the following AT instruction on ncs v1.3, returned OK, but did not return the subscription message, need to modify where to return the subscription message did not return the subscription message at the AT instruction has the test step step step 26 step 27 step 28.

2. What are the steps required to register with the AT instruction to the network? I tried to simulate LTE Link Monitor registration to the network steps down step0-step25 to test, but step 17 place must be delayed by 10 seconds to get the IP address, but LTE Link Monitor registration to the network can get the IP address without delay, please tell me why this difference.

3. In the course of the test appeared messages dropd, why cause the loss of log, please help me deal with the loss of log

4.LTE Link Monitor registration to the network log below

5.step0-step25 registered to the network log below

6. Test code see annex

15_hello_world_at_lte.rar

[Simon]

Currently, a huge portion of the support team (including the expert on AT commands) is on summer vacation, but I will do my best to answer your question.

Question 1

If I understand you correctly, you are wondering if the functions "AT%XVBATLVL=1" (step 26),  "AT%XOPNAME=1" (step 27) and "AT%XTIME=1" (step 28) only returns "OK".

The mentioned functions will (according to the AT Commands Reference Guide), however you may receive notifications as a consequence, but it is no guarantee that you will (as I understand it).

You may receive notifications after "AT%XVBATLVL=1"  if the following happens:

• "The notification is sent when the battery voltage level is under the currently set low level."

You may receive notifications after "AT%XOPNAME=1"  and "AT%XTIME=1" if the following happens:

• "Notification is sent after network registration (attach) if the network sends EMM INFORMATION PDU. However, there is no guarantee that this notification is ever sent. This is described in the AT reference guide"
  • This answer was given by another support engineer, I can get in contact with the person if anything is unclear about this.

Question 2

Could you test out the solution suggested by Martin in this ticket about the XEPCO command?

Question 3

It seems like ncs\v1.3.0\zephyr\subsys\logging\log_msg.c-->log_msg_chunk_alloc()-->k_mem_slab_alloc() fails

Try increasing these CONFIG_LOG_BUFFER_SIZE and CONFIG_LOG_STRDUP_BUF_COUNT, as mentioned in https://lists.zephyrproject.org/g/devel/message/6983?p=,,,20,0,0,0::Created,,messages+dropped,20,2,0,74032390

Best regards,

Simon