• State Verified Answer
  • Locked Locked
  • Replies 39 replies
  • Subscribers 74 subscribers
  • Views 8808 views
  • Users 0 members are here
Attachments (15) Download All
Nordic Case Info
  • Case ID: 273097
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

NB-IOT JIO SIM Not connecting asset tracker Work Up to RRC Connected and stuck there.

Hardik.Harpal

Using NB- IOT JIO SIM in india, not connecting asset tracker Work Up to RRC Connected and stuck there. This is custom code very similar to asset tracker example. We are using custom board, same setup works fine on Ibasis SIM in USA.

[00:00:00.215,576] [0m<inf> asset_tracker: Connecting to LTE network.[0m
[00:00:00.215,942] [0m<inf> asset_tracker: This may take several minutes.[0m
[00:00:00.223,205] [0m<dbg> lte_lc.lte_lc_system_mode_set: Sending AT command to set system mode: AT%XSYSTEMMODE=0,1,1,0[0m
[00:00:00.259,643] [0m<inf> lte_lc: PDP Context: AT+CGDCONT=0,"IPV6","JioIPIoT"[0m
[00:00:00.267,608] [0m<dbg> lte_lc.lte_lc_system_mode_set: Sending AT command to set system mode: AT%XSYSTEMMODE=0,1,1,0[0m
[00:00:27.635,711] [0m<dbg> lte_lc.at_handler: +CEREG notification: +CEREG: 2,"C061","00282218",9
[0m
[00:00:27.636,444] [0m<inf> asset_tracker: LTE cell changed: Cell ID: 2630168, Tracking area: 49249[0m

trace-2021-07-13T00-06-58.563Z.pcapng

trace-2021-07-13T00-06-58.563Z.bin

Parents
  • 0

    Hi! Håkon has gone on vacation so I have taken over this case.

    The conclusion from the modem trace you provided is that the Attach procedure is prevented due to the modem reset loop restriction feature which was introduced in MFW 1.3.0. We have just released a white paper on the feature which should explain the functionality in detail: nWP042 - nRF9160 Modem Reset Loop Restriction

    In short, the feature restricts Attach attempts to the network for 30 minutes in the case where the modem detects that the UE is in a reset loop. This can also happen if the modem is manually reset too many times.

    The AT+CFUN = 0 command should be used for shutting down the modem gracefully in order to avoid this restriction. 

    Please let me know if this solves the issue you are seeing. 

    Best regards,

    Heidi

  • 0 in reply to Heidi

    Hi,

    But I am seeing similar results in Modem firmware version 1.2.3 and earlier version on Dev kit I have 1.2.3 let me send you modem log from it. I will use MQTT simple example and configure it for nbiot.

    Can AT_Client example running with link monitor can provide modem trace by default or do I have to change prj config changes to enable it?

    Can you analyze this  new log withing next 22 hours? I have meeting with  JIO support team. If anything from their side I can provide our observation from Log they're asking for more detailed modem log as I explained in previous replies, I shared same modem trace (wireshark playable) with them. There are higher chances it is from network, but we need to figure it out as it is a month long now.

    Regards,

    Hardik Harpal

  • 0 in reply to Hardik.Harpal

    There are a lot of traces lost during decoding, which isn't something we've seen before. Unfortunately, our tracing tool experts aren't back to work until next week.

    The last NAS level trace shows that it is requesting RRC connection establishment for the Attach Request which was not the case in MFW 1.3.0 in which Attach procedure was blocked due to reset loop restriction.

  • 0 in reply to Heidi

    Okay. So let's wait for next week, If anything required again, just let me know.

    If any progress made from my side I will update you.

  • 0 in reply to Heidi
    Heidi said:
    There are a lot of traces lost during decoding, which isn't something we've seen before. Unfortunately, our tracing tool experts aren't back to work until next week.

    If I collect log from old trace collector, I am using trace collector v2 preview v0.0.10, is it possible to analyze log without tracing tool expert.  I am thinking may be issue with this preview version and old modem firmware version 1.2.3

  • 0 in reply to Hardik.Harpal

    Hi again,

    So we had the tracing tool experts take a look at the traces you provided.

    The MFW 1.3.0 log seems to be ok from a tracing perspective, i.e. no errors. So if you could get a new log with 1.3.0 starting from startup and about 1 minute long. Please confirm that the reset loop detection is not active before taking the log. Modem domain event notifications, including notifications of the modem reset loop restriction's activation, can be subscribed with AT%MDMEVAT=1.

    With regard to the 1.2.3 log there are a lot of errors, and we suspect the problem lies in NCS. 

    Which version of NCS are you using with MFW 1.2.3, and which version are you using with MFW 1.3.0?

    Best regards,

    Heidi

Reply
  • 0 in reply to Hardik.Harpal

    Hi again,

    So we had the tracing tool experts take a look at the traces you provided.

    The MFW 1.3.0 log seems to be ok from a tracing perspective, i.e. no errors. So if you could get a new log with 1.3.0 starting from startup and about 1 minute long. Please confirm that the reset loop detection is not active before taking the log. Modem domain event notifications, including notifications of the modem reset loop restriction's activation, can be subscribed with AT%MDMEVAT=1.

    With regard to the 1.2.3 log there are a lot of errors, and we suspect the problem lies in NCS. 

    Which version of NCS are you using with MFW 1.2.3, and which version are you using with MFW 1.3.0?

    Best regards,

    Heidi

Children
Related
Terms of service