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

    Unable to telnet with Virgin LoPys

    Scheduled Pinned Locked Moved LoPy
    6 Posts 3 Posters 1.6k 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.
    • L Offline
      LarryTru
      last edited by

      Hello,

      I have 2 virgin LoPys which will obviously need firmware updates, but I seem to be having an even more fundamental problem. With the factory firmware, I should be able to telnet to 192.168.4.1 after connecting to it via wifi. Right? both of mine accept the wifi connection, but neither respond to telnet. I am using OS X 10.11.6. Pymakr also fails to connect.

      Possibly the new firmware is required even to telnet to them via wifi, but I didn't see that reported in the forum.

      Any assistance is greatly appreciated.

      Thank you,

      Larry

      1 Reply Last reply Reply Quote 0
      • L Offline
        LarryTru
        last edited by

        Well, I'm not aware of doing anything differently tonight, but for some reason I am now able to get basic connectivity for both LoPys and one of them upgraded without a fuss.

        Larry

        1 Reply Last reply Reply Quote 0
        • R Offline
          Ralph
          last edited by

          Hi @LarryTru,

          It should work out of the box, but the REPL script should be in place in the boot.py file for Pymakr to connect to the board. You can find it here. Upload it through FTP first.

          If you have any firmware updating issues left, try the new release of 0.9.2.b1. It has a fix for a bug where the flash memory of some boards would (partly) end up in a read-only state.

          L 1 Reply Last reply Reply Quote 0
          • L Offline
            LarryTru @Ralph
            last edited by

            @Ralph Thanks, I heard there was going to be an update to the firmware updater for that problem. I "think" that is the only problem I currently have and that with only one of the units. Thanks for the tips.

            Larry

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

              @LarryTru Not sure if that's still a problem for you. But I had the problem that the connection via telnet to 192.68.4.1 takes a very long time. This is apparently due to some DNS reverse lookup which is Mac specific. This confused me a lot. But then I learned that if I wait long enough then it works. This is also specific only to the mode when the LoPy is the access point.

              L 1 Reply Last reply Reply Quote 0
              • L Offline
                LarryTru @stevie
                last edited by

                @stevie Thanks for that info. I noticed the slowness, but I hadn't figured out the pattern. I definately think it could be the explanation for what I was running into. I just didn;t wait long enough.

                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