Bugs & Issues

• S

  Pycom Wipy v2.0 sleep mode detail documentation
  • sneha  

  6
  0
  Votes
  6
  Posts
  1012
  Views

  J

  @sneha Hey, I’m just a user like you, I’m trying to help, but you probably need to do your own research, or ask Pycom directly...
• C

  Pymakr 1.2.8 - Can't find upload button or global settings
  bugs • • CodeManiac64  

  13
  0
  Votes
  13
  Posts
  2063
  Views

  C

  @seb Yes, I do get the led to blink orange. That has not been an issue at all, works fine. I tried uploading my code and keeping 3.3v and G28 connected, and the result was this: I tried removing the wire connecting 3.3v and G28 and I could finally upload! Thanks for all the help!
• C

  CRITICAL: Guru mediation erases the data from flash
  bugs • • Colateral  

  13
  0
  Votes
  13
  Posts
  2621
  Views

  

  @colateral said in CRITICAL: Guru mediation erases the data from flash: We did o LOpY but not possible on L01. it is possible but harder ;-) However in this way Guru mediation output is not catched. good point, core crash will not go then to SD card.. then only external device can catch this
• X

  Pytrack will not boot after update
  bugs • • xorlover  

  3
  0
  Votes
  3
  Posts
  658
  Views

  X

  @jmarcelino It works! Thank you.
• N

  This topic is deleted!
  • neffes  

  1
  0
  Votes
  1
  Posts
  2
  Views

  No one has replied

• T

  Accelerometer wake_up
  bugs • • ThomasP  

  20
  0
  Votes
  20
  Posts
  3566
  Views

  T

  Got it. Thanks @seb and @jcaron for all your help !
• P

  [LoPy] TX Power 2-4 dBm invalid after FW update
  bugs • • pjoerke  

  2
  0
  Votes
  2
  Posts
  619
  Views

  

  Hi, Thanks for reporting this issue, it will be resolved in the next firmware release coming shortly
• A

  I can't connect my LoPy to my computer!!
  bugs • • Areli_Anzures  

  4
  0
  Votes
  4
  Posts
  1037
  Views

  

  @areli_anzures Can you try connecting just the expansion board without the LoPy? It should still appear as a serial port. If it works without the LoPy please check if the LoPy is correctly connected and in the right orientation.
• K

  problem with reading vars on wipy 2 w/ext board and ds18b20
  bugs • • kop524  

  2
  0
  Votes
  2
  Posts
  573
  Views

  

  @kop524 format your post http://commonmark.org/help/ and show exact error message with line number and why you connect your DS18X20 to different pins? You can support few sensors on the same pin. DS18X20 work on onewire protocol. I do not know about which implementation of DS18X20 lib you have but parameter for DS18X20 is onewire bus not pin Pin can not be OUT if you need to read something from it use e.g.: oWire=OneWire(Pin('P22', Pin.PULL_UP)) temp=DS18X20(oWire, True) # you can ommit True if your lib does not have this param
• T

  Invalid: Obscure wlan scan bug?
  bugs • • this.wiederkehr  

  3
  0
  Votes
  3
  Posts
  774
  Views

  T

  @seb here you are: (sysname='LoPy', nodename='LoPy', release='1.15.0.b1', version='v1.8.6-849-baa8c33 on 2018-01-29', machine='LoPy with ESP32', lorawan='1.0.0') Forget about my code above. I thought this is the problem but it's not. Actually my board freezes when doing wlan operations. However I'm not able to reproduce with a minimum example... Just forget about it. I'll report back once I have a minimum example which shows the issue ... Sorry for bothering ...
• D

  Instability in aluminium housing
  bugs • • danielm  

  3
  0
  Votes
  3
  Posts
  680
  Views

  D

  @livius Internal antenna was used. The purpose of WiFi interface was to provide web configuration interface accessed from close proximity to the device and it worked surprisingly well with internal antenna transmitting through the aluminium housing. In case of LoPy boards which did not crash of course :).
• F

  guru meditation error (Lopy firmware version 1.8.0.b1)
  bugs • • fbt  

  3
  0
  Votes
  3
  Posts
  1177
  Views

  

  This error refers to a old firmware version, have you updated to the latest firmware?
• I

  FiPy + LTE CAT M1: Problem when stablishing a connection
  bugs • • icorredor  

  3
  0
  Votes
  3
  Posts
  1939
  Views

  I

  @brotherdust thanks for your proposal. It seems the best way to speed up any connection test with the LTE modem. Regarding AT commands, can you suggest me a sequence that worked under same (or similar) technical conditions?
• A

  BLE scan
  bugs • • apantano  

  1
  0
  Votes
  1
  Posts
  702
  Views

  No one has replied

• L

  [SOLVED]uModbus Serial Library fails after firmware update
  bugs • • lsoria  

  6
  0
  Votes
  6
  Posts
  1477
  Views

  L

  Hi, I've been following this thread, in which had problems with Modbus Serial too: https://forum.pycom.io/topic/2363/lopy-sp3485-modbus-lib-test-register-read-error I've upgraded the uModbus libraries to the latest ones, as well as the LoPy firmware: https://forum.pycom.io/topic/2541/new-firmware-release-v1-15-0-b1/8 After performing these actions both the demo and my code worked again! This thread can be considered solved. Cheers!
• A

  Power consumption
  bugs • • apantano  

  19
  0
  Votes
  19
  Posts
  4383
  Views

  A

  @apantano Hi I took a new LoPy+Pysense and I measured the consumption w/o LAN and BT by modifing the boot.py (the main.py is empty) like this Import os import machine from machine import UART from network import WLAN, Bluetooth uart = UART(0, baudrate=115200) os.dupterm(uart) wlan = WLAN() wlan.init(mode=WLAN.STA) wlan.deinit() bt = Bluetooth() bt.deinit() machine.main('main.py') The currrent is 45-46 mA. Probably there is some active resource that I don't know. Thanks Andrea
• G

  FiPy + Extension Board Power consumption
  bugs • • Gomez  

  3
  0
  Votes
  3
  Posts
  1140
  Views

  G

  Hi, RTS and CTS remove ( also the LED one ). Performed a couple of reset, the deep mode still consume 70-80 ma. During wake up it rise to 240 ma, 80 - 84 ma during boot and main. Does the sigfox init library routine ( or socket ) without send anything cause power drain? Do you suggest to init LTE modem and then deinit? ( Anyway if you write in the boot.py insert LTE.init() and LTE.deinit() one after the other, Fipy stuck you need to remove the lines above, maybe a small delay can help. ) Thanks, Andrea
• 

  timeq and uasyncio.* on WiPy 2.0 (or 3.0?)
  bugs • • rkeiii  

  8
  0
  Votes
  8
  Posts
  2530
  Views

  

  @rkeiii Version 1.15.0b1 now contains the utimeq module and a slightly changed utime module, which matches the needs of the uasyncio lib. The only change needed to the lib is swapping the arguments of the single utime.ticks_diff() in usanycio.core.py.
• R

  TTN code for LoPy does not work on LoPy4
  bugs • • Robin  

  8
  0
  Votes
  8
  Posts
  2296
  Views

  D

  Hello, The problem with this particular device is that it was flashed with a LoPy firmware instead of a LoPy4 firmware. Cheers, Daniel
• R

  libusbK (v3.0.7.0) Vs USB Serial(CDC) [ and Atom connection ]
  bugs • • R.W  

  3
  0
  Votes
  3
  Posts
  1420
  Views

  R

  @Xykon , thanks. Btw are there any advantages of using libusbK? cos I used USB Serial(CDC) driver ( when flashing from zadig ) and it works well. I see the COM port and I can use Atom/Pymakr to program. With libusbK, I wasn't sure how to connect from Atom as there is no longer a serial port available.