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

    Pymate fails to setup boot.py with the right known net

    Scheduled Pinned Locked Moved Pymate
    16 Posts 4 Posters 5.8k Views 4 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.
    • K Offline
      kurt @Xykon
      last edited by

      @Xykon Yes, this confirms OSError 104 ECONNRESET 104 /* Connection reset by peer */
      I also tried

      >>> socket.getaddrinfo('mqtt.pycom.io', 1883)
      [(2, 1, 0, '', ('198.199.124.44', 1883))]
      

      A pleasant surprise, as socket.getaddrinfo() did not work last week.

      What's next? Why is the server resetting the connection? Timeout, wrong data...?

      My current plan is to get my WiPy working. It has a bad safe boot pin and I need to compile the firmware for another pin before trying Pymate on it...

      1 Reply Last reply Reply Quote 1
      • X Offline
        Xykon administrators
        last edited by Xykon

        The server mqtt.pycom.io does not listen on port 1883.

        nmap -p 1883 mqtt.pycom.io
        
        Starting Nmap 7.01 ( https://nmap.org ) at 2016-11-06 14:35 GMT
        Nmap scan report for mqtt.pycom.io (198.199.124.44)
        Host is up (0.022s latency).
        PORT     STATE  SERVICE
        1883/tcp closed unknown
        
        Nmap done: 1 IP address (1 host up) scanned in 0.10 seconds
        
        

        Christian Ehlers

        K 1 Reply Last reply Reply Quote 0
        • K Offline
          kurt @Xykon
          last edited by

          @Xykon Meanwhile got my WiPy 1.0 working and upgraded it to the most recent firmware. But the result in regards to the Pymate is almost the same.

          ...
          Error: error connecting to the pymate server, connection closed
          Error: error connecting to the pymate server, connection closed
          Error: error connecting to the pymate server, connection closed
          Error: error connecting to the pymate server, connection closed
          Error: error connecting to the pymate server, connection closed
          Traceback (most recent call last):
            File "boot.py", line 39, in <module>
            File "/flash/lib/pymate_basic.py", line 13, in <module>
            File "/flash/lib/pymate_library.py", line 354, in run
          KeyboardInterrupt: 
          MicroPython v1.8.5-121-g5c3d75c on 2016-11-06; WiPy with CC3200
          Type "help()" for more information.
          ```
          1 Reply Last reply Reply Quote 1
          • M Offline
            microman7k
            last edited by

            @kurt Thanks, so we could agree that the problem is in pycom site? Hey, Pycom (@daniel) can you provide us with some information that Pymate is even working or not?

            1 Reply Last reply Reply Quote 1
            • R Offline
              Roberto
              last edited by

              Hello @kurt @microman7k

              We have fixed this issue and updated some files in the server.
              You will need to go to the setup stage again, delete your device by swiping it left and add it again.

              To make sure that everything works properly please boot your device in safe mode
              https://docs.pycom.io/lopy/lopy/general.html#boot-modes-and-safe-boot
              and remove the connection between 3v3 and G28 (P12) when Pymate asks you to reset the device.

              X 1 Reply Last reply Reply Quote 1
              • X Offline
                Xykon administrators @Roberto
                last edited by

                @Roberto I gave this a quick test... the installation works OK now, the LoPy connects to my AP and I can see it go online and show the firmware version in Pymate.

                I created a button in Pymate and told it to use digital pin 4.. I have an LED connected from P4 -> 1k resistor -> LED -> GND.

                When I switch the button ON/OFF in Pymate the LED stays at a dim level.

                When I bypass execfile('/flash/lib/pymate_basic.py') and use from machine import Pin; p_out = Pin('P4', mode=Pin.OUT); p_out(1) then the LED lights up bright and turns off with p_out(0).

                I thought maybe Pymate is using expansion board numbers for digital pins so I also tried digital port 11 but I don't see any change.

                Christian Ehlers

                R 1 Reply Last reply Reply Quote 0
                • R Offline
                  Roberto @Xykon
                  last edited by

                  @Xykon I did the same test in my end and it works. To be clear, yes, the pins used by the apps are the expansion board pins (G 11) in you case.

                  Check List:

                  1. Go to the device list and refresh using the refresh button to make sure that the device is connected.
                  2. Once int he dashboard (widgets) long click on the button widget to edit. Make sure is of type button, and that is set the the right pin (11). As an output pin.
                  3. Save
                  4. Once back in the dashboard make sure you press the Plat button on the top. This will send the configuration of the pin to the device and allow you to use the button widget.

                  Make sure you do this before doing any code input in your device (for test propose) and check if the LED Turns on.

                  One last thing The User LED on the expansion board is the pin 16 G16. You can test with this Led first to make sure that everything is working as it should.

                  1 Reply Last reply Reply Quote 0
                  • X Offline
                    Xykon administrators
                    last edited by

                    Thanks I got it to work now. I think I just didn't save it properly when switching from digital 4 to 11.

                    Christian Ehlers

                    R 1 Reply Last reply Reply Quote 0
                    • R Offline
                      Roberto @Xykon
                      last edited by

                      @Xykon Great!. Hopefully @kurt will get it working as well

                      K 1 Reply Last reply Reply Quote 0
                      • K Offline
                        kurt @Roberto
                        last edited by

                        @Roberto Yes, thank you, I got it working on the lopy as well. My wipy 1.0 is still resisting, but I'm not sure if this device is healthy. I try it again when I have more patience for it. Cheers!

                        R 1 Reply Last reply Reply Quote 1
                        • R Offline
                          Roberto @kurt
                          last edited by

                          Great @kurt im glad to know that things are working on your side. Thanks for all the input

                          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