Seeking guidance



  • I received my new WiPy 2 yesterday, and have been unsuccessful at getting it operational.

    Using "screen" (on OSX) I can see that the board is running.
    I used the update tool to update to (sysname='WiPy', nodename='WiPy', release='0.9.3.b2', version='d78a5a3 on 2016-11-05', machine='WiPy with ESP32')

    I can connect to the wifi network (and see the connection message using screen:

    n:6 0, o:6 0, ap:6 1, sta:255 255, prof:6
    add 1
    station: 28:37:37:1e:cd:1a join, AID = 1, n, 20

    What I can't do is telnet or ftp over wifi to update files like boot.py etc. nor can I get Pymakr IDE to connect (Pymakr also fails with my WiPy1 but at least I can ftp and telnet to that).

    the following commands all time out
    ftp ftp://micro.python@192.168.4.1
    ftp ftp://micro.python@192.168.4.1/
    ftp ftp://micro.python@192.168.4.1/flash
    ftp ftp://micro.python@192.168.4.1/flash/
    ftp 192.168.4.1

    ftp: Can't connect to 192.168.4.1': Operation timed out ftp: Can't connect to192.168.4.1'

    telnet 192.168.4.1
    Trying 192.168.4.1...
    telnet: connect to address 192.168.4.1: Operation timed out
    telnet: Unable to connect to remote host

    I WANT this to be great, so I'm suppressing frustration :)

    Thanks

    Jon



  • try filezilla with passive mode and restriction to only one connection



  • @jonirons Nice that you are making progress. You should be able to pass the password using the ftp command. It's also worth giving a try to FileZilla or another ftp client, it is very convenient for such things.



  • Turns out pressing the reset button wasn't enough. A full power down was needed. That might be worth updating in the updater instructions.

    Now I'm at the point that I can connect as
    ftp 192.168.4.1 but I can't pass in the password - i have to type it.

    ftp ftp://192.168.4.1 fails (and all with ftp://)
    ftp micro.python@192.168.4.1 prompts for the password again and fails
    ftp micro@192.168.4.1 prompts for the password and works.

    Progress!


Log in to reply
 

Looks like your connection to Pycom Forum was lost, please wait while we try to reconnect.