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

    Nanogateway uplink fails after 30minutes every time.

    Scheduled Pinned Locked Moved Issues & Bugs
    nanogatewaywifi
    2 Posts 2 Posters 753 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.
    • D Offline
      Dylan
      last edited by Dylan

      Hello,

      I am using a PyTrack with LoPy as a nanogateway. After successfully connecting to eduroam (WPA2 enterprise I believe) everything works fine for exactly 1900 seconds every time give or take a few milliseconds. I am wondering where to start with this problem, I have looked through the code for anything that might indicate something happening everything 30 minutes but no success.

      I don't believe eduroam is the problem since I am using two laptops and a phone all connected by wifi with no problems. In the past I was connecting the nanogateway via mobile phone hotspot and having no troubles.

      I was just wondering if anyone would have any ideas on where I start, or if I can at least find a way to determine whether its the nanogateway, or something to do with the eduroam, in which case I'll contact our IT guys.

      Cheers,

      Dylan

      J 1 Reply Last reply Reply Quote 0
      • J Offline
        jmarcelino @Dylan
        last edited by jmarcelino

        @dylan
        The nano gateway uses the Semtech standard protocol which is uses UDP on port 1700, this is very different from your usual WiFi traffic and likely to be treated differently by your institution’s network policies.

        I guess you can ask them what is their policy for long running UDP sessions on port 1700 but in my experience, unless you are able to talk to core networking staff, you might not get a straight answer.

        Since UDP is a connectionless protocol the LoPy has no idea about the state of the connection either, by definition UDP is a “send packets and hope for the best” protocol.

        What you can do is point the nanogateway at another server, maybe some server you control outside of your institution network and have something listen on UDP/1700 there, can be as simple as Netcat:

        netcat -u -l 1700

        Then wait that half an hour and see if the nanogateway messages still arrive there. Doing a packet capture (tcpdump) on port 1700 will probably help. If the packets stop arriving - the gateway will always send status packets even without LoRa traffic - you’ll know at least that you have a networking problem and nothing related to LoRa.

        You should also monitor the nano gateway, ideally over Serial to see if no error messages pop up.

        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