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

    Receiving b"

    Scheduled Pinned Locked Moved LoPy
    lopylopy lora mode
    6 Posts 5 Posters 1.4k Views 5 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.
    • R Offline
      rajarahul96 Pybytes Beta
      last edited by

      We bought two LoPy modules with expansion boards and antennas. When we tried to communicate between them using the codes in documentation i.e, Lora mac, Lora to Lora . W e are getting b" as result that is an empty buffer. Please help us.

      1 Reply Last reply Reply Quote 0
      • B Offline
        bucknall
        last edited by

        Hi @rajarahul96,

        Please update to the latest firmware! If you are running an earlier version, you may be running into a bug that was present in an earlier version!

        You can check which version of the firmware you are using, with these commands:

        import os
        os.uname()
        

        Developer Evangelist - Pycom

        1 Reply Last reply Reply Quote 1
        • R Offline
          rajarahul96 Pybytes Beta
          last edited by

          Thanks. It is working.

          B 1 Reply Last reply Reply Quote 0
          • B Offline
            bilou7 @rajarahul96
            last edited by

            @rajarahul96 hello, I have the save problem. Could you please tell me which firmware did you change ? The pymakr version, or the lopy firmware version ? It would help me a lot. Thanks!

            G 1 Reply Last reply Reply Quote 0
            • G Offline
              goldfishalpha @bilou7
              last edited by

              @bilou7 I would try doing it on the LoPy first as there is probably nothing to loose in any case. (backup your the files on the lopy, first just in case).
              Just be sure all ends are speaking the same LoRa specifications.
              Example: If you have a device provisioned on a server somewhere at 1.0.0 and the firmware happens to upgrade you to 1.0.2

              1 Reply Last reply Reply Quote 0
              • T Offline
                tuftec
                last edited by

                I am seeing a similar issue with my FiPy device (when using NB-IOT communications).
                I suspect the problem has something to do with the sockets code and not specifically LoRa.
                I am running the latest version of software on my FiPy.

                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