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

    Trouble trying to get the lte modem to responding

    Scheduled Pinned Locked Moved GPy
    2 Posts 2 Posters 38 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.
    • H Offline
      hakan sanli
      last edited by hakan sanli

      We can't use the pycom firmware so we are using esp-idf. I have ported the lte logic over from the pycom-micropython-sigfox branch. After startup the modem works perfectly. But when I do a soft reboot it stops working. I have tried using the pymakr to just use raw uart and write exactly the same AT commands, when I do this it works.
      So in summary

      from machine import UART
      import time
      serial = UART(1, baudrate=921600, pins=('P5', 'P98', 'P7', 'P99'), timeout_chars=1)
      print(serial.read())
      while True:
      	serial.write("+++" + '\r\n')
      	time.sleep(1)
      	print(serial.read())
      	serial.write("AT" + '\r\n')
      	time.sleep(1)
      	print(serial.read())
      	serial.write("AT" + '\r\n')
      	time.sleep(1)
      	print(serial.read())
      

      This code will wake up the modem inside pymakr's environment. But when I do exactly the same in esp-idf. It doesn't do anything. The lte modem doesn't respond

      I thought maybe there is an internal pin that I need to reset to reset the modem? Or do something with the uart before starting?

      A 1 Reply Last reply Reply Quote 0
      • A Offline
        André Maree @hakan sanli
        last edited by

        @hakan-sanli

        I noticed you have not received any reply yet, a pattern I think relates to the fact that Pycom's primary focus is on their backend service offering, hardware is just a tool to get there, hence they discourage non Pycom firmware development.

        We have just started out on the same road, but still cannot get to flash WiPy or FiPy devices reliably using the PySense and PyTrack boards. Have connected a switch to EN pin and tried 5 different USB adapters, 4 different types. No luck getting any output

        But (using PySense or PyTrack) the devices connect to the dev platform and can be flashed, upgraded and operated.

        Any suggestions?

        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