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

    Testing Receiving Windows in Chirpstack

    Scheduled Pinned Locked Moved Comments & Feedback
    2 Posts 2 Posters 25 Views 2 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.
    • G Offline
      Gonçalo Ferreira
      last edited by

      Hi, thanks for the attention!!!

      I have a Lopy4 and I am trying to test the communications with different values of Rx Windows. I have a lora-server, chirpstack, and I change the values in the Network Server .toml file. I also restarted the server so the changes would apply.
      I tried the worst scenario, a SF12 with full data bytes communication from my end device with a downlink response, however the downlink was still received in the board.
      Basically I was trying to see how the messages parameters (SF and size data) affect the TonA by limiting the Rx time. Can somebody help me by saying me a method so I can test this???

      J 1 Reply Last reply Reply Quote 0
      • J Offline
        jcaron @Gonçalo Ferreira
        last edited by

        @Gonçalo-Ferreira can you clarify exactly which settings you are changing, and what values you are setting them to?

        Not familiar with Chirpstack settings, but the usual RX window settings are just an offset from end of uplink to start of RX1, and then RX2 happens a second later. The duration of the windows is based on allowed data rates.

        When you change RX windows settings, the settings are sent to the device in the join accept IIRC, so changing those settings won’t affect the ability of devices using OTAA to receive downlinks.

        The ideal RX offset is the default, 1 second. Anything longer will require the device to stay on longer and draw more power.

        Not that the device doesn’t listen for the full max duration of a frame, but just enough to recognise a preamble or thereabouts. So even at SF12 it’s only a fraction of a second, not over a second.

        1 Reply Last reply Reply Quote 1

        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