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.send_at_cmd delay Error

    Scheduled Pinned Locked Moved GPy
    3 Posts 3 Posters 80 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.
    • C Offline
      coon.fu
      last edited by

      Hi,

      I'm getting an error on send_at_cmd delay param.

      >>> import os
      >>> from network import LTE
      >>> lte = LTE()
      >>> lte.send_at_cmd("AT", delay=1000).split('\r\n')
      Traceback (most recent call last):
        File "<stdin>", line 1, in <module>
      TypeError: extra keyword arguments given
      

      Omitting delay executes the function properly but documentation says it should work with the delay param.

      What am I missing here?

      Br. C

      X 1 Reply Last reply Reply Quote 0
      • X Offline
        Xykon administrators @coon.fu
        last edited by

        @coon-fu We removed the delay parameter from the command and it seems the documentation hasn't been updated accordingly. We will get this fixed as soon as possible.

        All AT commands should now work properly without specifying a delay. If you encounter any commands that require this please let us know.

        Christian Ehlers

        M 1 Reply Last reply Reply Quote 0
        • M Offline
          mchristiansen @Xykon
          last edited by

          @Xykon I am using a Hologram SIM with a GPy and am attempting to follow their instructions here: https://support.hologram.io/hc/en-us/articles/360035697393-Modem-SIM-annotated-diagnostic-test specifically the last instruction to run AT+COPS=? to get information on networks in reach. Their document specifically says this command could take up to 3 minutes to execute, but when I run it via the LTE module it comes back in approximately 10 seconds with no response. I am assuming this is a timeout, but I can't say for sure without any response from the module. I was trying to use the delay parameter to increase the timeout for this use case.

          As a side note: the documentation has not been updated yet, and still advertises the delay parameter.

          Thanks,
          Mike

          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