Bugs & Issues

• T

  Safe Boot whereas P12 is connected to ground through resistor
  • thibault  

  3
  0
  Votes
  3
  Posts
  261
  Views

  T

  I have use the DragonFly firmware from Andreas to run our code without the LoadProhibited core panic. I thank him for give me information how about precompiled our code with mpy-cross (version 1.11). We havn't any more problem with our electronic card (OEM lopy on it).
• K

  Connecting to PyBytes Via Wifi.
  • katoa_mangu  

  3
  0
  Votes
  3
  Posts
  210
  Views

  K

  Hi @jirkakrepl ! Thank you so much for your prompt reply! The error was caused due to restrictions in our internal work wifi system, after taking it home it worked within seconds. The debug mode really helped in solving that error. It made me realize I was continuously getting data_packet receive errors. Thanks, Purak
• B

  NB-IoT attaching to AT&T, USA
  • BillOtto  

  1
  0
  Votes
  1
  Posts
  92
  Views

  No one has replied

• R

  FiPy Wake on Movement
  • Riley  

  3
  0
  Votes
  3
  Posts
  127
  Views

  R

  Im using the latest version of Pysense, i realized that using any of the sleep functions even just setting up sleep would break the CLI. I manually changed the memory address for the sleep reason to 1. It was working as i would expect. After powering it up a day later the memory address for the sleep reason is back to 12.
• J

  pybytes.connect() hangs in _pybytes.py, line 128, in send_info_message (using NB-IoT with gpy on Orange network Belgium)
  • jand  

  1
  1
  Votes
  1
  Posts
  153
  Views

  No one has replied

• L

  This topic is deleted!
  • lanaserena  

  1
  0
  Votes
  1
  Posts
  5
  Views

  No one has replied

• N

  Pycom LoPy, boot.py and WiFi connection.
  • NickBoots  

  6
  0
  Votes
  6
  Posts
  260
  Views

  N

  @mnovella The weird thing is, I'm trying this code now on a WiPy too, both that and the Lopy have the latest firmware as of writing this. 1.20.1.r2. wlan.ssid() doesn't return anything, even if I set it and then check it again...
• J

  Lopy4 sending confirmed messages on 915 problem
  • Johnjoe  

  1
  0
  Votes
  1
  Posts
  123
  Views

  No one has replied

• H

  Wipy + Development Board 3.0 TTL to RS232 UART Printer Problem
  • handloomweaver  

  4
  1
  Votes
  4
  Posts
  188
  Views

  

  @handloomweaver It looks OK. What happens if you bridge RX/TX at the RS232 side. Then at least you can check that the data is passing through the Level converter. Then, the modem control lines could be the problem.
• N

  Gpy with PySense won't Attach.
  • NickBoots  

  9
  0
  Votes
  9
  Posts
  595
  Views

  N

  @jcaron 41019 Sorry for the ultra-late reply, project got on hold for a while.
• J

  This topic is deleted!
  • jand  

  1
  0
  Votes
  1
  Posts
  37
  Views

  No one has replied

• J

  FiPy LTE-M Connection Problems
  • JFarque  

  3
  0
  Votes
  3
  Posts
  259
  Views

  J

  I've discovered that lte.attach() sets CFUN=1 and that subsequent AT+CFUN=1 commands cause the SYSSTART to occur. Allowing the lte.attach() function to set CFUN to 1 seems to have cleared up the "spurious" restart issue. I still cannot get the modem to attach, however. Any help is appreciated. Jason
• Q

  probleme with download
  • quentho  

  3
  0
  Votes
  3
  Posts
  189
  Views

  Q

  @crumble thank you for your answer, where can i check this ?
• F

  L76GNSV5 Library OSError: I2C bus error
  • ferfersan6  

  10
  0
  Votes
  10
  Posts
  545
  Views

  C

  @robert-hh Don't care about power right now. I like to see version chaos for the pytrack as well. Why do they only improve the expansion board and don't place a better antenna and a plug on the pytrack? And a battery plug which is more common in my area? Version chaos now! And a wiki in which user can keep the documentation/examples in snyc with the firmware. Yes, it is a risk, but Pycom seems to small for keeping the documentation actual - and the forum is not the best place for user collected best practice and workarounds.
• E

  Ambient temperature with pysense v3
  • ezahrai  

  1
  0
  Votes
  1
  Posts
  122
  Views

  No one has replied

• _

  Lopy4 does not send messages in DR4 in US915 frequencies
  • _peter  

  10
  0
  Votes
  10
  Posts
  499
  Views

  _

  Hi @oligauc. Your suggestion to set dr_min=0 for the channel 64 did the trick! Modifying just that using the same code now the device send four messages using DR0 through DR3 at 902.7 and the last one at DR4 at 903.0 If I go back putting dr_min=4 I obtain the same problem again. I still need to make other tests using the OTAA mode, but in the mean time I want to thank you for your support.
• A

  No LoPy 4 WiFi after updating the firmware
  • aqi  

  16
  0
  Votes
  16
  Posts
  1244
  Views

  

  @Xykon Thanks, yes. I had seen that already and I am using it now, since the CLI firmware updater 1.16 does not work anymore with the new tar files. Reason unkown.
• F

  OSError: error renaming file when OTA UPDATE
  • Francesco123  

  6
  0
  Votes
  6
  Posts
  281
  Views

  F

  @robert-hh ah ok thanks for the explanation.
• T

  LoPy4 - LoRa Nano Gateway - Guru Meditation Error
  • titi  

  7
  1
  Votes
  7
  Posts
  547
  Views

  A

  Dear @titi and @jason_gladen, if you feel lucky, you might want to try our custom build just released on [1]. More background about this is available through [2]. If we are lucky together, this will improve the stability significantly. If you will be still receiving the core dumps, I will be happy if you would share its content with us. Please be aware that when upgrading to the current 1.20.1.r1 release these builds are based upon, you will have to erase your device completely before flashing in order to keep things straight. You will find respective references to this on the forum. Hint: Use pycom-fwtool-cli --port /dev/ttyUSB0 erase_all, see also [3]. Please also be aware that this procedure will also erase the LoRa MAC stored on the device. @robert-hh thankfully outlined the procedure to restore it appropriately: If you still know the value the LoraMac had before, then you can follow the procedure explained at https://forum.pycom.io/topic/1272/lora-mac-ffffffffffffffff/21. If you do not know it, you will have to use the Pycom updater to restore it: First, use the Pycom updater (GUI version) to install a recent image (like pybytes 1.20.1) from the Internet. You do not have to use it, the installation process itself already restores both the LoRa MAC and the Sigfox ID. Then, use the Pycom updater to flash the custom image. Do not erase the flash in between. As it turned out to gain more robustness for others already [4,5], we will be happy to learn if this happens to you as well. With kind regards, Andreas. P.S.: @titi: Especially, we would be interested if this firmware will be stable without the workaround you outlined above. [1a] https://packages.hiveeyes.org/hiveeyes/foss/pycom/vanilla/LoPy-1.20.1.r1-0.6.0-vanilla-dragonfly.tar.gz [1b] https://packages.hiveeyes.org/hiveeyes/foss/pycom/vanilla/LoPy4-1.20.1.r1-0.6.0-vanilla-dragonfly.tar.gz [2] https://community.hiveeyes.org/t/investigating-random-core-panics-on-pycom-esp32-devices/2480 [3] https://community.hiveeyes.org/t/installing-the-recent-pycom-firmware-1-20-1-r1-requires-erasing-the-flash-memory-completely/2688 [4] https://community.hiveeyes.org/t/testing-the-custom-dragonfly-builds-on-pycom-devices/2746 [5] https://github.com/pycom/pycom-micropython-sigfox/issues/361#issuecomment-553399627
• S

  PyMesh Guru Meditation Error
  • sylvainm  

  2
  0
  Votes
  2
  Posts
  228
  Views

  A

  Dear @sylvainm, @lars_r also experienced core panics on his LoPy4 and we have been able to help him out of being stuck with it [1]. However, the fixes improve general stability which is not specific to any mesh networking features. Saying this, it might still improve things for you. Please read [1] carefully regarding the erase_all step and how to eventually restore your LoRa MAC. Thanks again to @robert-hh for his knowledge on how to do that. With kind regards, Andreas. [1] https://github.com/pycom/pycom-micropython-sigfox/issues/361