Bugs & Issues

• E

  MicroWebSrv2 : Server is too slow
  • ElinhohHD  

  9
  0
  Votes
  9
  Posts
  311
  Views

  E

  @jcaron said in MicroWebSrv2 : Server is too slow: polling Are the files you are requesting static files (I suppose not) dynamically generated one the fly? The files are generated . Are you using TLS? No Is your WiFi not on a congested channel? Maybe I will try to change channel . thanks . Is your WiPy doing anything else at the same time? Yes , but even he ' s doing nothing , I found this problem.
• A

  Bug with ussl and socket setblocking(False)
  • amstaff88  

  1
  0
  Votes
  1
  Posts
  88
  Views

  No one has replied

• P

  LoadProhibited core panic when initialize wlan
  • pat_hslu  

  16
  0
  Votes
  16
  Posts
  433
  Views

  A

  Dear @pat_hslu, Espressif is constantly improving the WiFi software stack [1], it might happen that we see improvements if this will be incorporated some day. Apart from that, @robert-hh said in LoadProhibited core panic when initialize wlan: This happens sometimes caused by a power supply problem. As soon as WiFi starts, the power consumption increases a lot. If you tried already other USB ports or cables, it might be related to the hardware of that unit. how is your power source? Will you be able to just try a different cable in order to take that out of the equation? For more details about the potential power issue, see also [2] ff. May I also ask whether you followed the installation instructions and the notes for LoPy, LoPy4, SiPy and FiPy devices? Completely erasing the flash will trigger a full RF-calibration on the next reboot. Maybe this helps with the WiFi behavior you are observing. With kind regards, Andreas. [1] https://github.com/espressif/esp32-wifi-lib/commits/master [2] https://github.com/espressif/esp-idf/issues/113#issuecomment-302971958
• K

  sys.stdout.write appends size to output
  • kruthers  

  2
  0
  Votes
  2
  Posts
  99
  Views

  K

  Nevermind, just figured out that the length is the return value and it's printed out immediately after in the repl. Sorry, nothing to see here... K
• F

  DevNonce always 0000
  • fernandes.son  

  3
  0
  Votes
  3
  Posts
  121
  Views

  F

  @jcaron This problem occurs after a wdt reset. This conditions is caused because the device is too far from the gateway and not received the ack message. It get stuck on lora send function and the wdt reset the board. It seems that the communication with the SX1276 is lost. The SX1276Read seems to read 0. The last firmware update was on january. The device is on a farm tractor, def lora_send_data(sock, data): """ Send a message, can use confirmed message or not, depending the configuration :param sock: a lora socket :type sock: object :param data: the data to be sent :type data: bytes """ global lora_send_completed global lora_ack_error lora_ack_error = False lora_send_completed = False if conf.LORA_MESSAGE_CONFIRMED: try: sock.setblocking(True) sock.send(data) if(settings.LORA_DEBUG): print("lora sent data:",ubinascii.hexlify(data)) sock.setblocking(False) except OSError as e: sock.setblocking(False) if e.args[0] == 11: if settings.LORA_DEBUG: print("tx_exception") else: sock.send(data) def lora_cb(lora): """ lora_send_data Call back function :param lora: lora configuration :type lora: object """ global lora_send_completed global lora_ack_error events = lora.events() if events & LoRa.TX_PACKET_EVENT: lora_ack_error = False if settings.LORA_DEBUG: print('Lora packet sent') if events & LoRa.TX_FAILED_EVENT: lora_ack_error = True if settings.LORA_DEBUG: print('Lora packet tx failed') lora_send_completed = True
• N

  WiPy 3.0 Socket Server connection issues
  • not_karl  

  8
  0
  Votes
  8
  Posts
  269
  Views

  N

  @Xykon Hi, appreciate the response. I get back -97 for the RSSI from the router. I've run this same server from the WiPy acting as an access point with no change in behavior. The behavior has been confirmed using both an integrated application and netcat itself from more than one device. Is there any logging from the WiPy that can be accessed to show reasons it may potentially lose connectivity or disassociate from an access point? Thanks, Karl
• G

  USB PyMakr Failed to establish connection to board
  • guyc  

  1
  0
  Votes
  1
  Posts
  72
  Views

  No one has replied

• A

  MicroPython CoAP library
  • ArnaudP  

  3
  3
  Votes
  3
  Posts
  363
  Views

  R

  @nftylitak said in MicroPython CoAP library: Hello Arnaud in case you are still in need in CoAP implementation in micropython, we have created a minimal port that we internally use. It is open-source and is available here: https://github.com/insighio/microCoAPy Any comments are welcomed. Thank you very much for the very detailed help!
• T

  W01 OEM broken
  • thibault  

  4
  0
  Votes
  4
  Posts
  171
  Views

  S

  @robert-hh said in W01 OEM broken: @thibault google street view Could be cause by some over voltage event. Is the 18LF4431 still intact, or is it broken too? It seems that this device is connected to a motor. Thanks very much for that information.
• N

  wlan.scan() works fine in REPL, not when ran in Script.
  • NickBoots  

  7
  0
  Votes
  7
  Posts
  229
  Views

  S

  Hello I found a fix to the problem so i though I would share: I am new to Pycom and Python i general however I had the exact same problem. I found out by trial and error that if I put in a decent delay between wlan = WLAN(mode=WLAN.STA) and nets = wlan.scan() I can now find all networks when rebooting the LoPy. Seems like any time.sleep() below 5 seconds is not enough. 7-8 seconds seems to reliably find all ssid's. I can only speculate with my limited coding abilities to why the delay is necessary. The scanning is performed when changing the WLAN mode and wlan.scan() is just a container for the result? Or maybe the wlan code is not ready for use so quickly after chaning mode? Who knows... I havent looked into the library. /SeaAnt
• B

  OTTA only joins successfully if close enough to the Gateway
  bugs • • berni  

  8
  0
  Votes
  8
  Posts
  188
  Views

  B

  @jcaron thank you for reply. I will look into this with more details. It seems like the problem is quite common and could be more complex than I expected: https://www.thethingsnetwork.org/forum/t/diagnosing-unreliable-join-accept-reception/24498
• S

  No GPS fix at all (occasionally), location inaccuracy (occasionally), LTE stops working (around a specific place)
  • smarok  

  3
  1
  Votes
  3
  Posts
  70
  Views

  J

  @jcaron mmmmhhh.... looking back at what’s left of your satellite pictures it seems to be a lot less dense than I initially thought. It would be interesting to log more information from the GPS chip, it can provide a lot of information including how many satellites are visible and used, which ones, and so on. Recording the full output should allow you to “play it back” later in dedicated tools for this.
• S

  Is it Bluetooth 4.1 or Bluetooth 4.2 ?
  • smarok  

  3
  0
  Votes
  3
  Posts
  100
  Views

  S

  @jcaron said in Is it Bluetooth 4.1 or Bluetooth 4.2 ?: m not even sure there is anything in the advertisement that could let you know the BT version of the advertiser (other than the presence of features that did not exist in previous versions, of course Ahhh, Thank you
• S

  Conflict between documention on pycom website and GitHub
  • smarok  

  2
  0
  Votes
  2
  Posts
  69
  Views

  P

  docs.pycom.io is leading. We should clean up the other old version ;)
• S

  Bluetooth advertisement problems
  • smarok  

  4
  0
  Votes
  4
  Posts
  123
  Views

  J

  @smarok Comparing BLE and LoRa is probably quite difficult given the differences in timing, range, etc. You should probably start by increasing the advertising interval. I would probably set it to 1 second or more. Also, if you intend to send actual data, a better option is probably to connect and send data via characteristics (use the write or notify mechanisms depending on the direction) rather than just broadcast via advertisements.
• S

  Different GPS Fix time on different PyTracks
  • smarok  

  5
  0
  Votes
  5
  Posts
  162
  Views

  J

  @smarok I believe this shows that by default the GPS chip does not save any state at all when powered off, so you are in a cold start scenario in those cases, while you are in warm start after a reset. I wonder what makes the difference between the scenarios with ≈30s TTFF and those with immediate fix, though. It would be interesting to log the chip’s full output in both cases, there are probably hints in there.
• 

  LTE-M antenna doesn't fit into the IP67 Case
  bugs • • rskoniec  

  4
  0
  Votes
  4
  Posts
  1247
  Views

  

  @rskoniec You can bend the antenna to make it fit. Besides that, you may use a different antenna, as long as it has about 50 Ohm impedance at the frequency you use and the matching connector. It may have a slightly different gain. But the way the supplied antenna could be installed in the package, any gain figure is anyhow questionable. P.S.: if you look for "lte pcb antenna" at aliexpress.com, you will get quite a selection, larger and smaller ones.
• S

  No documentation available for a Bluetooth function
  • smarok  

  1
  0
  Votes
  1
  Posts
  67
  Views

  No one has replied

• S

  Bluetooth mac address is slightly different
  • smarok  

  1
  0
  Votes
  1
  Posts
  302
  Views

  No one has replied

• S

  This topic is deleted!
  • smarok  

  1
  0
  Votes
  1
  Posts
  5
  Views

  No one has replied