Navigation

    Welcome to the Pycom forum

    Forum

    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    1. Home
    2. Popular

    Explore Pybytes | Official Documentation | Report a Firmware Bug/Issue | GitHub

    Log in to post
    • All categories
    • Announcements & News
    •      Beta Announcements & Development News
    •      Announcements only for members
    • Helium Hotspot
    •      Support
    • Pylife
    • Pybytes IoT platform
    •      Announcements & News
    •      Ideas
    •      Support & Troubleshooting
    • Getting Started
    •      Discussion
    •      WiPy 2&3
    •      LoPy
    •      SiPy
    •      GPy
    •      FiPy
    •      Pymakr
    •      Pymate
    •      Expansion Board
    •      MicroPython
    • Tutorials
    •      Projects
    •      Guides
    • Firmware
    •      Discussion
    •      Enhancements
    •      Issues & Bugs
    • Wireless Technologies
    •      WiFi
    •      Bluetooth
    •      LoRa
    •      Sigfox
    •      Cellular
    • Software Tools
    •      Discussion
    •      Enhancements
    •      Issues & Bugs
    • Events
    • Comments & Feedback
    • Jobs at Pycom
    • PyGo
    • All Topics
    • New Topics
    • Watched Topics
    • Unreplied Topics
    • All Time
    • Day
    • Week
    • Month

    • J

      SDI-12 Soil Moisture Probe Help
      LoPy • lopy sdi-12 rs485 • • jimpower  

      38
      0
      Votes
      38
      Posts
      3252
      Views

      Gusti Made Arya Wijaya

      @Bryan-Hom oh okay thanks for your advice. I only have max485 and max3485 now
    • B

      Lopy4 Guru meditation error
      Issues & Bugs • lopy4 firmware error guru meditation guru error • • bjsi9  

      37
      0
      Votes
      37
      Posts
      8870
      Views

      M

      @jmarcelino do you already searching for a solution or have found it ???? I have the same problem
    • M

      Lopy and Matchx usage
      Discussion • gateway lorawan server matchx • • misterlisty  

      37
      0
      Votes
      37
      Posts
      11903
      Views

      M

      @jmarcelino Any update on this? or suggestion?
    • D

      New firmware release 1.2.0.b1
      Announcements & News • • daniel  

      37
      3
      Votes
      37
      Posts
      12042
      Views

      D

      @arneme great to hear that, thanks for the feedback :-)
    • X

      LoPy pinout (work in progress)
      LoPy • • Xykon  

      37
      3
      Votes
      37
      Posts
      20998
      Views

      X

      @bartvandeenen said in LoPy pinout (work in progress): I plan to build an open-source wireless house thermostat Wouldn't a thermostat chip like the DS1620 be easier in this case?
    • S

      SCT-013 current sensor
      LoPy • • StefanoF  

      37
      0
      Votes
      37
      Posts
      111
      Views

      robert-hh

      @Stefano-Floriani That's better. The capacitor worked here as a means to suppress noise. You can also increase the value of R7 to 27k. Then the value should be at about 150.
    • techykermit

      PyCom alternatives?
      GPy • • techykermit  

      36
      2
      Votes
      36
      Posts
      412
      Views

      T

      If you're interested in checking out Particle I can get you a sample! LTE Developer friendly ecosystem Certified Easy transition from pycom
    • D

      New release New firmware release 1.2.2.b1
      Announcements & News • • daniel  

      36
      1
      Votes
      36
      Posts
      13406
      Views

      M

      @minkley Still struggling to get the firmware upgrade to work on linux. Note, I'm not using an expansion card but a Serial USB cable which powers the device up and allows me to connect to the wifi I'm also able to connect to the serial port with minicom and I get the following python version: >>> print(sys.version) 3.4.0 >>> When I try and update the firmware I get the following error. Namespace(file=None, port='/dev/ttyUSB0', speed=115200, tar='/tmp/tmp.zR12S6HK0s/update.tar.gz') Connecting... Uploading stub... Running stub... Stub running... Changing baud rate to 115200 Changed. Exception: empty file, on line 131 This what I am doing exactly: As root Downloaded and extracted pycom_update_1.0.0.b3.tar.gz cd into pyupgrade run ./update select WiPy 2.0 Disconnect device from USB Put G23 into GND Plug in USB cable Press and hold the the reset button for about 3 seconds Press enter on the update Type in the serial path :-> /dev/ttyUSB0 Deselect high speed Then it fails with the "Exception: empty file on line 131. Just to be sure my EMS32 connectivity is good, whilst connected via minicom, if I plug in G23 to GND hit reset, I see the device is waiting for a download >>> ets Jun 8 2016 00:22:57 rst:0x1 (POWERON_RESET),boot:0x3 (DOWNLOAD_BOOT(UART0/UART1/SDIO_REI_REO_V2)) waiting for download Perhaps someone can point me to the firmware file and a command line script I can use to test the install. I really would like to complete the upgrade and get on with using the device :)
    • M

      DS18B20 temperature sensor
      LoPy • • madsdk  

      36
      0
      Votes
      36
      Posts
      23948
      Views

      J

      @livius thanks that did the trick
    • M

      Guru Meditation Error - Pycom WiPy
      WiPy 2&3 • wipy bug coredump • • Milan  

      35
      0
      Votes
      35
      Posts
      4885
      Views

      A

      Dear @Milan and @Martinnn, if you feel lucky, you might want to try our custom build just released on [1]. More background about this is available through [2]. Please be aware that 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]. With kind regards, Andreas. [1] https://packages.hiveeyes.org/hiveeyes/foss/pycom/vanilla/WiPy-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
    • S

      Atom Pymakr Serialport.node
      Pymakr • pymakr atom • • ssmith  

      35
      1
      Votes
      35
      Posts
      14838
      Views

      Ralph

      @simonjcarr Try the latest code on the develop branch, that should solve the issue: https://github.com/pycom/pymakr-atom/tree/develop
    • X

      The future of Pycom
      Announcements & News • • Xykon  

      34
      8
      Votes
      34
      Posts
      608
      Views

      S

      @DEFRAINE-JM any further updates on what's happening with Pycom apart from Season Group buying the assets?
    • K

      Unable to update GPy modem firmware
      Issues & Bugs • gpy firmware update lte m1 lte nb iot • • ktleh  

      34
      2
      Votes
      34
      Posts
      6374
      Views

      G

      @bqpd Thank you from the future.
    • J

      Deep Sleep Summary
      Discussion • pytrack pysense deepsleep deep sleep • • jcaron  

      34
      7
      Votes
      34
      Posts
      11027
      Views

      philwilkinson

      @tuftec, yes you are correct, the machine.deepsleep() machine.remaining_sleep_time() and pin_deepsleep_wakeup() functions all work fine. I have isolated my problem was with the LoRa publishing code. When I commented out the lora_publish in my code below everything worked fine. The bug must be something to do with nvram functions i am using in my lora_publish function. Perhaps this bug is best published in a new thread. Thanks for the comment. Code published to allow others a quick start! import machine import utime from machine import Pin import pycom import config #user defined #import LoRa_publish #user defined rst=machine.reset_cause() if rst != 3: # if not woken from deepsleep utime.sleep(10) #to allow ctrl+C pycom.nvs_set('counter', 0) #button = Pin('P23', mode = Pin.IN, pull = Pin.PULL_UP) machine.pin_deepsleep_wakeup(pins = ['P23'], mode = machine.WAKEUP_ALL_LOW, enable_pull = True) machine.deepsleep(60000) else: if (machine.wake_reason()[0])==1: #pin wakeup total_count = pycom.nvs_get('counter') +1 pycom.nvs_set('counter', total_count) print('remaining deepsleep time is {}'.format(machine.remaining_sleep_time())) machine.pin_deepsleep_wakeup(pins = ['P23'], mode = machine.WAKEUP_ALL_LOW, enable_pull = True) machine.deepsleep(machine.remaining_sleep_time()) elif (machine.wake_reason()[0])==2: #RTC timer complete print('timer completed') total_count = pycom.nvs_get('counter') print('counted {} button presses'.format(total_count)) #LoRa_publish.publish(total_count) #INT published to TTN pycom.nvs_set('counter', 0) machine.pin_deepsleep_wakeup(pins = ['P23'], mode = machine.WAKEUP_ALL_LOW, enable_pull = True) machine.deepsleep(60000) #this does not restart a new interval!!
    • _

      Strategy for LoRaWAN with deepsleep 2
      LoPy • deepsleep join wake up • • _peter  

      34
      0
      Votes
      34
      Posts
      12533
      Views

      J

      @jmarcelino Is there any example code that incorporates deepsleep and LoraWAN with these new functionalities to test it? thanks
    • M

      Simple MQTT Tutorial
      WiPy 2&3 • • MrPy  

      34
      2
      Votes
      34
      Posts
      29892
      Views

      livius

      @achide I do not use pymakr but if i understand screen correctly you put it into \flash\lib\connections but you should into \flash\lib
    • D

      Trouble with FiPy code not working
      FiPy • fipy code • • Dylan  

      33
      0
      Votes
      33
      Posts
      9256
      Views

      robert-hh

      @dylan It is hard to believe that this is the reason, because the standard value for sys.path is ['', '/flash', '/flash/lib']. Since main.py resides in /flash, any code to be imported may reside at that place too, like also in /flash/lib or the actual directory (frisdt entry). The latter may be the a cause, if you have multiple copies of your code, good and bad ones, on the file system.
    • I

      New Firmware Development release v1.19.0.b4
      Beta Announcements & Development News • firmware development • • iwahdan  

      33
      2
      Votes
      33
      Posts
      9452
      Views

      X

      @reidfo said in New Firmware Development release v1.19.0.b4: On both mac and linux I'm getting unexpected sha1 checksum when I try to install the latest development release on FiPy. Are you using the beta firmware updater?
    • D

      Firmware release 1.7.3.b1
      Announcements & News • firmware • • daniel  

      33
      1
      Votes
      33
      Posts
      13349
      Views

      robert-hh

      @this.wiederkehr @peekay123 @daniel It seems, as if with release 1.7.7.b1 this issue is gone. I ran the loop&write test three times up to 2 million passes = 2048000000 Bytes successfully, at which time it stopped intentionally to avoid writing more than 2 GB into a file.
    • L

      Can't connect to my LoPy4 board
      LoPy • • Liudmila Dobriakova  

      33
      0
      Votes
      33
      Posts
      29
      Views

      robert-hh

      @Liudmila-Dobriakova said in Can't connect to my LoPy4 board: so, means what the FiPy will be dropped as well, since it's also ESP32 based? this is really pitty... Yes. It seems that only the new F01 board will be available then, if at all.
    • 1
    • 2
    • 3
    • 4
    • 5
    • 6
    • 9
    • 10
    • 4 / 10