Welcome to the Pycom forum Forum
    • \[\[global:header.categories\]\]
    • \[\[global:header.recent\]\]
    • \[\[global:header.tags\]\]
    • \[\[global:header.popular\]\]
    • Login

    Explore Pybytes | Official Documentation | Report a Firmware Bug/Issue | GitHub

    lte.connect() CID and its purpose

    Scheduled Pinned Locked Moved Comments & Feedback
    lteconnectiongpycid
    3 Posts 2 Posters 758 Views 3 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • P Offline
      panda
      last edited by

      Re: lte.connect Connection ID (cid)

      Please would someone clarify how the cid value plays into connections? I have the following scenario:

      My GPy modems function really well. I appear to be avoiding the many issues other people have with connecting, hanging etc. However, I am experiencing locations where the modem initially connected with cid=1 then later (days/weeks later) would only connect with cid=3. Now one particular location is back to only connecting with cid=1. Carrier and physical location have remained constant.

      When unable to connect I get the following exception with lte.connect(cid=x):

      "the requested operation failed"

      However, while the modem threw an exception and indicates it is not connected my SIM provider (Hologram) indicates is IS connected.

      Please help me understand what CID is and how I can know which to select and when. Yes, I see in the docs it's an indicator of carrier, but my experience says that really does not affect which carrier is used (according to Hologram dashboard). I want these devices to be able to be deployed without having to fiddle with various modem settings for each location. Should that be possible (within reason) if I am deploying to major cities across the US?

      1 Reply Last reply Reply Quote 0
      • P Offline
        panda
        last edited by panda

        @robert-hh said in LTE Available Towers:

        RRC:showDetectedCell

        The response from the "RRC:showDetectedCell" command is:

        ['No permission to use the RRC private debug CLI', 'OK']

        The other commands seem to work fine. If the error message is accurate how do I enable permission?

        robert-hhR 1 Reply Last reply Reply Quote 0
        • robert-hhR Offline
          robert-hh @panda
          last edited by

          @panda try lte.send_at_cmd('AT!="setDbgPerm full"') before using the command lte.send_at_cmd('AT!="RRC:showDetectedCell"')

          1 Reply Last reply Reply Quote 0

          Hello! It looks like you're interested in this conversation, but you don't have an account yet.

          Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

          With your input, this post could be even better 💗

          Register Login
          • 1 / 1
          • First post
            Last post

          Pycom on Twitter

          Pycom