Welcome to the Pycom forum Forum
    • \[\[global:header.categories\]\]
    • \[\[global:header.recent\]\]
    • \[\[global:header.tags\]\]
    • \[\[global:header.popular\]\]
    • Login
    1. Home
    2. Popular

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

    Log in to post
    • All Time
    • Day
    • Week
    • Month
    • All Topics
    • New Topics
    • Watched Topics
    • Unreplied Topics

    • All categories
    • B

      Pycom FiPy ADR not working on AS923 (TTN and Chirpstack)

      Watching Ignoring Scheduled Pinned Locked Moved FiPy
      38
      0 Votes
      38 Posts
      188 Views
      J
      @Gijs Hello, I am currently using FiPy and LoPy4 and I am also trying to activate the ADR but using this firmware "pycom_firmware_updater_1.16.6". I have read here that you were able to achieve ADR with this firmware FiPy-1.20.2.r4_adr4.tar.gz I have yet to try with this. I also read that the change of SF was only after 70 packets, isn't possible to change after 2/3? In my use case, the gateway will pass by the end-node at a high speed.
    • X

      LoPy pinout (work in progress)

      Watching Ignoring Scheduled Pinned Locked Moved LoPy
      37
      3 Votes
      37 Posts
      21k 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?
    • D

      New firmware release 1.2.0.b1

      Watching Ignoring Scheduled Pinned Locked Moved Announcements & News
      37
      3 Votes
      37 Posts
      12k Views
      D
      @arneme great to hear that, thanks for the feedback :-)
    • M

      Lopy and Matchx usage

      Watching Ignoring Scheduled Pinned Locked Moved Discussion matchx gateway lorawan server
      37
      0 Votes
      37 Posts
      12k Views
      M
      @jmarcelino Any update on this? or suggestion?
    • B

      Lopy4 Guru meditation error

      Watching Ignoring Scheduled Pinned Locked Moved Issues & Bugs firmware lopy4 error guru meditation guru error
      37
      0 Votes
      37 Posts
      9k Views
      M
      @jmarcelino do you already searching for a solution or have found it ???? I have the same problem
    • S

      SCT-013 current sensor

      Watching Ignoring Scheduled Pinned Locked Moved LoPy
      37
      0 Votes
      37 Posts
      114 Views
      robert-hhR
      @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.
    • M

      DS18B20 temperature sensor

      Watching Ignoring Scheduled Pinned Locked Moved LoPy
      36
      0 Votes
      36 Posts
      24k Views
      J
      @livius thanks that did the trick
    • D

      New release New firmware release 1.2.2.b1

      Watching Ignoring Scheduled Pinned Locked Moved Announcements & News
      36
      1 Votes
      36 Posts
      13k 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 :)
    • techykermitT

      PyCom alternatives?

      Watching Ignoring Scheduled Pinned Locked Moved GPy
      36
      2 Votes
      36 Posts
      414 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
    • S

      Atom Pymakr Serialport.node

      Watching Ignoring Scheduled Pinned Locked Moved Pymakr pymakr atom
      35
      1 Votes
      35 Posts
      15k Views
      R
      @simonjcarr Try the latest code on the develop branch, that should solve the issue: https://github.com/pycom/pymakr-atom/tree/develop
    • M

      Guru Meditation Error - Pycom WiPy

      Watching Ignoring Scheduled Pinned Locked Moved WiPy 2&3 wipy coredump bug
      35
      0 Votes
      35 Posts
      5k 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
    • M

      Simple MQTT Tutorial

      Watching Ignoring Scheduled Pinned Locked Moved WiPy 2&3
      34
      2 Votes
      34 Posts
      30k Views
      L
      @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
    • _

      Strategy for LoRaWAN with deepsleep 2

      Watching Ignoring Scheduled Pinned Locked Moved LoPy deepsleep join wake up
      34
      0 Votes
      34 Posts
      13k Views
      J
      @jmarcelino Is there any example code that incorporates deepsleep and LoraWAN with these new functionalities to test it? thanks
    • J

      Deep Sleep Summary

      Watching Ignoring Scheduled Pinned Locked Moved Discussion deep sleep pysense pytrack deepsleep
      34
      7 Votes
      34 Posts
      11k Views
      philwilkinsonP
      @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!!
    • K

      Unable to update GPy modem firmware

      Watching Ignoring Scheduled Pinned Locked Moved Issues & Bugs firmware update gpy lte m1 lte nb iot
      34
      2 Votes
      34 Posts
      6k Views
      G
      @bqpd Thank you from the future.
    • X

      The future of Pycom

      Watching Ignoring Scheduled Pinned Locked Moved Announcements & News
      34
      8 Votes
      34 Posts
      624 Views
      S
      @DEFRAINE-JM any further updates on what's happening with Pycom apart from Season Group buying the assets?
    • D

      Firmware release 1.7.3.b1

      Watching Ignoring Scheduled Pinned Locked Moved Announcements & News firmware
      33
      1 Votes
      33 Posts
      13k Views
      robert-hhR
      @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.
    • D

      Trouble with FiPy code not working

      Watching Ignoring Scheduled Pinned Locked Moved FiPy fipy code
      33
      0 Votes
      33 Posts
      9k Views
      robert-hhR
      @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

      Watching Ignoring Scheduled Pinned Locked Moved Beta Announcements & Development News firmware development
      33
      2 Votes
      33 Posts
      9k 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?
    • L

      Can't connect to my LoPy4 board

      Watching Ignoring Scheduled Pinned Locked Moved LoPy
      33
      0 Votes
      33 Posts
      31 Views
      robert-hhR
      @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