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

    PING kills LoPy after a successful HTTP request to a server

    Scheduled Pinned Locked Moved LoPy
    socket crash
    1 Posts 1 Posters 789 Views 1 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.
    • U Offline
      ulde
      last edited by

      Using socket to connect to an HTTP server, then closing the socket, the LoPy keeps going just fine, until I simply ping the LoPy's IP address. It returns a single ICMP reply then crashes.

      The firmware is the most recent version to date. Am I doing something wrong?

      Thanks,
      Ulde

      Here's the code:

      boot.py

      import os
      from machine import UART
      uart = UART(0, 115200)
      os.dupterm(uart)

      main.py

      import os
      import network
      from network import WLAN
      import socket
      import time

      WLAN_SSID = 'myssid'
      WLAN_SEC = WLAN.WEP
      WLAN_KEY = '456c7***********726461'

      wlan = WLAN(mode=WLAN.STA)
      wlanconnectingtime = time.time()
      wlan.connect(WLAN_SSID, auth=(WLAN_SEC, WLAN_KEY), timeout = 10000)
      while not wlan.isconnected():
      time.sleep_ms(50)
      print(wlan.ifconfig())
      print(os.uname())

      s = socket.socket()
      s.connect(socket.getaddrinfo("google.com", 80)[0][-1])
      s.write(b"GET / HTTP/1.0\r\n\r\n")
      print(s.read(4096))
      s.close()
      print('CLOSED')

      while True:
      print(time.time())
      time.sleep(1)

      The terminal dump:

      rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
      ets Jun 8 2016 00:22:57

      rst:0x10 (RTCWDT_RTC_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
      ...
      entry 0x4009fc9c
      ('192.168.0.52', '255.255.255.0', '192.168.0.1', '192.168.0.1')
      (sysname='LoPy', nodename='LoPy', release='1.9.2.b2', version='v1.8.6-796-g489fafa0 on 2017-10-15', machine='LoPy with ESP32', lorawan='1.0.0')
      b'HTTP/1.0 302 Found\r\nCache-Control: private\r\nContent-Type: text/html; charset=UTF-8\r\nReferrer-Policy: no-referrer\r\nLocation: http://www.google.it/?gfe_rd=cr&dcr=0&ei=BFn_WfKtI9Pw8Aet_pWgAQ\r\nContent-Length: 268\r\nDate: Sun, 05 Nov 2017 18:31:32 GMT\r\n\r\n<HTML><HEAD><meta http-equiv="content-type" content="text/html;charset=utf-8">\n<TITLE>302 Moved</TITLE></HEAD><BODY>\n<H1>302 Moved</H1>\nThe document has moved\n<A HREF="http://www.google.it/?gfe_rd=cr&amp;dcr=0&amp;ei=BFn_WfKtI9Pw8Aet_pWgAQ">here</A>.\r\n</BODY></HTML>\r\n'
      CLOSED
      2
      3
      4
      5
      6
      7

      And the ping "killer":

      $ ping 192.168.0.52
      PING 192.168.0.52 (192.168.0.52): 56 data bytes
      64 bytes from 192.168.0.52: icmp_seq=0 ttl=255 time=6.143 ms
      Request timeout for icmp_seq 1
      Request timeout for icmp_seq 2
      Request timeout for icmp_seq 3
      ^C

      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