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

    LoPy4, WLAN and FileZilla connection

    Scheduled Pinned Locked Moved LoPy
    lopy4filezillawifi
    6 Posts 3 Posters 1.4k 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.
    • S Offline
      ssmith
      last edited by

      Having trouble getting FileZilla to connect to a LoPy4. If I leave it in AP mode I can connect just fine. If I connect the LoPy to my WiFi then I can't connect to it with FileZilla or PyCharm. I get a connection but FZ says it's waiting on a welcome message. Any ideas on what might have changed in the WiFi?

      C L 2 Replies Last reply Reply Quote 0
      • C Offline
        crumble @ssmith
        last edited by

        Have you limited the amount of connections in fileZilla to one?
        If the LoPy is in AP mode and is not running any scripts, it can deal with more than one connection. I think running a script will limit this amount to 1.

        1 Reply Last reply Reply Quote 0
        • S Offline
          ssmith
          last edited by

          It is set to 1. The same code has been running on the LoPy for a year.

          1 Reply Last reply Reply Quote 0
          • L Offline
            livius @ssmith
            last edited by

            @ssmith
            I do not properly understand you.

            If I connect the LoPy to my WiFi

            then you have changed it to STA mode to connect it to wifi?
            If yes than, no surprise.
            try with WLAN.STA_AP mode

            think about people first, then computers

            S 1 Reply Last reply Reply Quote 0
            • S Offline
              ssmith @livius
              last edited by

              @livius Correct, when it's in STA mode I connect to it's IP address. When it's in AP mode I connect to 192.168.1.4.

              I'm narrowing it down. It appears to be a timing issue with multiple things running. If I slow down my timer tic from 100mS to 1S then I can access the device. The issue appears to be in the interrupt processing because I also cannot get LoRa packets through.

              1 Reply Last reply Reply Quote 0
              • S Offline
                ssmith
                last edited by

                Found the issue. It was actually caused by gc.collect() run time going from 6mS to 48mS. This was being run inside a timer tic ISR (I know, that's a no-no). The ISR was taking longer to run than the timer tic period. I assume the UART Int is a lower priority than the timer so it was never being processed.

                Is gc.collect() taking so long because of the extra memory or is this a bug?

                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