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

    • R

      AWS IoT Device Support for LoPy
      LoPy • • RSK  

      25
      0
      Votes
      25
      Posts
      12291
      Views

      R

      @juriw Thanks a Lot!
    • H

      Orange Belgium Gpy
      Discussion • gpy nbiot orange belgium • • hadjidgr  

      25
      0
      Votes
      25
      Posts
      4179
      Views

      M

      Hello all, Finally I manage to make it works. The problem wasn't in the software, but hardware. I don't use a expansion board, I use a ttl converter like this one https://www.ebay.com/itm/5V-3-3V-FTDI-FT232RL-USB-to-TTL-Serial-Converter-Adapter-Module-Arduino-Mini-Hot/182736917146 With this converter 3.3V is not enough to power on stably the board, so, I used it in 5V mode, but it seem that 5v for serial communication is ok for the python REPL, but have problem when flashing the modem or use the LTE modem. Finally, I changed my design by using another 5v power source, and use the ttl converter un 3v3 mode with common ground. And then it just works fine ;) Thank you for you support
    • tobru

      failed to set dtr/rts
      Issues & Bugs • lopy pysense pymakr • • tobru  

      25
      0
      Votes
      25
      Posts
      17173
      Views

      on4aa

      What Removed Added Resolution --- FIXED Status REOPENED RESOLVED Comment # 5 on bug 104320 from Aleksander Morgado I've pushed the 2 blacklisted devices with rules including vid:pid, but I've also added the whole vid to the "usb adapters greylist", which are only probed if manually requested to do so, so should help to avoid interference with other Microchip-vid-tagged devices. https://cgit.freedesktop.org/ModemManager/ModemManager/commit/?id=c2b956aefce495865cbdcb9971e2b3cd99cd0e99 All fine & dandy in the end…
    • S

      GPY/FiPY & Expansion Bd 3 - Multi I2C and SD Card Instances
      Discussion • fipy gpy expansion board i2c spi • • Stevo52  

      25
      0
      Votes
      25
      Posts
      3535
      Views

      S

      @robert-hh OK, I set up some code to try this out, several timers at different periods and several threads including one to start LTE, send an SMS and then deinit. From what I can see, the timers do NOT get interupted by the LTE device. It seems the timer counts are retained and dumped to REPL as soon as possible (buffered apparently). There is some corruption/mixup of REPL lines but all the timer flags are there I will investigate a bit further and see if I can use this to my advantage. One thread/timer I will need will be at 11uS preferably, so as it is too fast to capture by eye, I'll have to write to a file to a file to evaluate any impact by the LTE device. Biggest constraint might be the actual time to write to disk. A FIFO data buffer is probably a good solution - some work to do there. The test code was pretty rough and ready so its needs a lot of refinement to be truly useful as a valid test.
    • mkharibalaji

      MemoryError: memory allocation failed, allocating 2048 bytes - LOPY - 1.2.0.b1
      LoPy • • mkharibalaji  

      25
      0
      Votes
      25
      Posts
      13266
      Views

      C

      @Shaun I can enumerate at least 5 active people from this forum that required the frozen functionality.
    • P

      I2C accelerometer model MMA7455
      Getting Started • lopy i2c sensor i2c bus error mma7455 • • pablocaviglia  

      25
      1
      Votes
      25
      Posts
      10589
      Views

      P

      @jmarcelino @livius @robert-hh Hey all, thx a lot for helping me this last days with this driver. This is the code i have until now... it's a shame that i didn't make it, but i think that i could have broken the sensor when i plugged CS to 5v instead of 3V3. I think i will buy another one, that will take some weeks until it gets to Uruguay :P Anyway, this is the code we've made until now, maybe it's useful for someone else. It's not throwing the ugly i2c bus error anymore, but the device id registry is returning always zero, and that's bad... not sure if the device is broken or what, but comparing this code with the implementation @livius has referenced, and with other implementations i found on google for other languages, it looks like the retrieval of the device id is the first action almost everyone does, so... i dont know. from machine import I2C from machine import Pin from machine import Timer import time def DelayUs(us): Timer.sleep_us(us) #i2c slave address SLAVE_ADDRESS = 0x1D #registers REG_POWER_CTL = 0x2D REG_BW_RATE = 0x2C #connected to SDO and CS of MMA7455 CS = Pin("P23", mode=Pin.OUT) CS.value(1) CS.hold() DelayUs(1000) #main i2c = I2C(0, I2C.MASTER, baudrate=100000) print(i2c.scan()) def setPowerCtrl(measure, wake_up=0, sleep=0, auto_sleep=0, link=0): power_ctl = wake_up & 0x03 if sleep: power_ctl |= 0x04 if measure: power_ctl |= 0x08 if auto_sleep: power_ctl |= 0x10 if link: power_ctl |= 0x20 i2c.writeto_mem(SLAVE_ADDRESS, REG_POWER_CTL, bytes([power_ctl])) #***************************** #******* main logic ********** #***************************** data = i2c.readfrom_mem(SLAVE_ADDRESS, 0x00, 1) print("DEVID: " + str(bin(data[0]))) #set power characteristics setPowerCtrl(1, wake_up=0, sleep=0, auto_sleep=0, link=0)
    • pierrot10

      [Pysense] How can I connect a sensor to the external IO Header
      Expansion Board • pysense interrupt pins headers pic • • pierrot10  

      25
      0
      Votes
      25
      Posts
      10612
      Views

      S

      Hi @pierrot10 The internal ADC has very poor performance. The non linearity is poor and it has a high noise floor. I think someone earlier suggested using an external ADC and I think that is very good advice.
    • H

      Instructions for upgrading Pytrack / LoPy
      Firmware • lopy • • hjl  

      25
      0
      Votes
      25
      Posts
      8749
      Views

      H

      @cinezaster @jcaron thanks guys, I'll try that!
    • D

      LoPy To MultiTech Conduit
      LoPy • • dchappel  

      25
      0
      Votes
      25
      Posts
      10718
      Views

      D

      @cmsedore Sorry for the delay in merging your code. I'm testing it now and everything looks solid. This will be on the next release. Thanks for your contribution! Cheers, Daniel
    • N

      Geofencing with Pytrack
      Expansion Board • • newkit  

      25
      0
      Votes
      25
      Posts
      207
      Views

      N

      @jcaron that seems to have fixed it. Initial results look positive, will do some more testing in the next days. Thank you so much for sorting this out!
    • M

      Lopy4 433MHz
      LoPy • lopy4 433mhz • • Mladen  

      25
      1
      Votes
      25
      Posts
      5166
      Views

      bmarkus

      @robert-hh said in Lopy4 433MHz: @bmarkus Standard build of Pycom. You know that I made a version of the pycom firmware and tested that against LORIOT. It worked. I see, thanks. I was not sure your are referring to the LoRa Alliance or PyCom
    • rskoniec

      Firmware upgrade troubleshooting - checklist/procedure
      Firmware • lopy • • rskoniec  

      24
      5
      Votes
      24
      Posts
      16486
      Views

      on4aa

      Unfortunately, this is currently not working for upgrading a module through either the Pysense or Pytrack boards using any GNU/Linux distribution.
    • M

      Nano- gateway rssi
      Comments & Feedback • lopy • • MJ  

      24
      0
      Votes
      24
      Posts
      6432
      Views

      robert-hh

      @mj Depends on the antenna an it's set-up. With a short wavelength/4 antenna, I had values between 25 and 39 dBm, even depending on how I was placing myself. The wavlength/4 antennas are typicall about 10cm (4") long, whereas wavelength/2 antennas have a length of about 20 cm (8").
    • P

      [Solved] Power consumption deep sleep Pysense/Pytrack
      Issues & Bugs • lopy pytrack pysense deepsleep deep sleep • • Pwntus  

      24
      2
      Votes
      24
      Posts
      11615
      Views

      P

      @dbrgn Thanks for the notification, I can confirm that it works!
    • securigy

      FiPy + Expansion Board: Battery Question
      FiPy • • securigy  

      24
      0
      Votes
      24
      Posts
      748
      Views

      securigy

      @jcaron You are absolutely correct on all points: I jest read yesterday that ESP32 has ULP (Ultra Low Power mode) so it makes sense that FiPy will have something like that as well... another field for me to research. But for now I assume that I will not be using deep sleep. About detecting motion: really good point - however my FiPy sits on Expansion Board 3.1 that I believe does not have accelerator...another hurdle... Meanwhile, I did discover something useful that will allow me to experiment with mAh consumption with ease. Check this thread: https://forum.pycom.io/topic/5694/measuring-amperage-consumption BTW, I am using GNSS Click 5 from uBlox with NEO-M8N with cold start of under 30 sec.
    • S

      Pymakr 1.1.13 does not work with VSCode 1.60.0
      Software Tools • • Stephan Elsner  

      24
      0
      Votes
      24
      Posts
      166
      Views

      B

      @robert-hh said in Pymakr 1.1.13 does not work with VSCode 1.60.0: @jchernandez mpremote has a --help option. For copying files, you have to use the cp subcommand. So as example for copying a file to the board: mpremote connect /dev/ttyUSB0 cp myfile.py :myfile.py or just mpremote connect /dev/ttyUSB0 cp myfile.py : for using : as a shortcut for the baord's local directory and . for the PC's one. Copying back similar as: mpremote connect /dev/ttyUSB0 cp :myfile.py myfile.py or mpremote connect /dev/ttyUSB0 cp :myfile.py . The device names at Windows are similar COM3, COM4, .... Shortcuts are: u0 for connect /dev/tty/USB0 Unfortunately the mount command of mpremote does not work with the PyCom version of MicroPython. That version is too old. To run a local script without copying it to the board use the run command. If you do not enter a command after the connect, mpremote opens a REPL session cat mario And before I forget it: With Pycom devices and WiFi active you can always use FTP for copying files. A good FTP client is FileZilla. But some file managers allow using FTP paths as well. User name is micro, password is python. you can review the .py file, i think it has that problem
    • bucknall

      Alex's Corner - Week 4 - WiPy & Publishing/Subscribing With MQTT
      Events • wipy mqtt wlan webinar live • • bucknall  

      24
      3
      Votes
      24
      Posts
      13259
      Views

      R

      @bucknall just posted about sending images over MQTT, perhaps one for another Corner?
    • S

      Pytrack + FiPy setup on Win7
      Issues & Bugs • pytrack firmware error installation • • sandipg  

      24
      1
      Votes
      24
      Posts
      8855
      Views

      C

      @seb A) FiPy+PyTrack+LiPo-Battery (Not-Attached-to-USB3.0) 
Vin = 4.09~4.10 V 3V3 = 3.32 V B) PyTrack+USB-Serial-device (Attached-to—USB3.0) same port as A)
 Vin = 4.85 V 3V3 = 0.23 V C) PyTrack+USB-Serial-device (Attached-to—USB3.0) + Hotswap-in-FiPy same port as A) & B)
 Vin = 4.55 V 3V3 = 3.32 V D) PyTrack+FiPy+NO-USB-Serial-device (Attached-to—USB3.0) same port as A) & B) & C) same combo as C) Just unplugged USB from PyTrack, and re-attached it…
 Vin = 1.69~2.51 V 3V3 = 1.15~1.91 V Also, worth nothing is that if my hand slips with the measuring probes, I get it to “boot-up” by accidentally shorting GROUND & 3V3, and I get a USB-Serial-Devices on my computer [ergo like A), B) & C) …] … And then, I get the same Vin & 3V3 as C) Which makes me conclude that you’ve guys have a Firmware issue!!! … and not a “bad usb-cable” or “bad usb-port” … etc etc. For some reason, in the boot-sequence of the PyTrack Firmware, it choose not to boot-up FiPy and enable USB-Serial … And, again, it’s odd that I can short GROUND & 3V3 with my measuring probes, and then it boots up FiPy and enables USB-Serial…
    • T

      FiPy deepsleep methods
      FiPy • • tuftec  

      24
      0
      Votes
      24
      Posts
      264
      Views

      B

      Hey @frederik-Leys, the LoPy does not have an LTE Modem so lte = LTE() should be have no effect on LoPy but und FiPy it should start the modem. Change your code to: import pycom import machine import time from network import LTE from network import WLAN wlan = WLAN() lte = LTE() time.sleep(5) lte.init() wlan.deinit() pycom.heartbeat(False) print(pycom.heartbeat_on_boot()) print(pycom.lte_modem_en_on_boot()) print(pycom.pybytes_on_boot()) print(pycom.smart_config_on_boot()) print(pycom.wdt_on_boot()) print(pycom.wifi_on_boot()) #colors in hexadecimal (0xRRGGBB) pycom.rgbled(0x00FF00) # Red time.sleep(1) lte.deinit() machine.deepsleep(40*1000) To get in uA range. Or let it run in powersave mode like: import pycom import machine import time from network import LTE from network import WLAN wlan = WLAN() lte = LTE(psm_period_value=1, psm_period_unit=LTE.PSM_PERIOD_1H, psm_active_value=5, psm_active_unit=LTE.PSM_ACTIVE_2S ) print(lte.psm()) time.sleep(5) lte.init() wlan.deinit() pycom.heartbeat(False) print(pycom.heartbeat_on_boot()) print(pycom.lte_modem_en_on_boot()) print(pycom.pybytes_on_boot()) print(pycom.smart_config_on_boot()) print(pycom.wdt_on_boot()) print(pycom.wifi_on_boot()) #colors in hexadecimal (0xRRGGBB) pycom.rgbled(0x00FF00) # Red time.sleep(1) lte.deinit(detach=False, reset=False) machine.deepsleep(40*1000) which brought me to 300uA.
    • robert-hh

      Confusing development process
      Discussion • micropython version management • • robert-hh  

      24
      4
      Votes
      24
      Posts
      3204
      Views

      robert-hh

      @iwahdan There is another branch now called stable_update. I understand that this is the trial update to 1.18.1.rx. I left a note there on one of the newer commits. Having a note somewhere about the intention of each branch would be helpful.
    • 1
    • 2
    • 6
    • 7
    • 8
    • 9
    • 10
    • 8 / 10