Issues & Bugs

• F

  AWS IoT topic subscribe callback never called
  • fausto.milletari  

  2
  0
  Votes
  2
  Posts
  13
  Views

  F

  OKAY! The problem has been solved by adding a receive policy to the group the thing belongs to. { "Effect": "Allow", "Action": [ "iot:Receive" ], "Resource": [ "*" ] }
• V

  Pymakr stopped working in VSCode 1.49
  • VST Admin  

  5
  0
  Votes
  5
  Posts
  35
  Views

  

  please check the new version 1.1.7
• 

  RMT preipheral won't transmit?
  • mogplus8  

  6
  0
  Votes
  6
  Posts
  22
  Views

  

  @mogplus8 P5 and P7 are fine. The ADC's are limited to 8, P13 - P20, since only ADC1 can be used. P4, P8 and P23 are connected to the SD Card adapter on the expansion board. If you want to use the SD card, you cannot use the for other purposes. Otherwise you can use them. The USB is connected through a USB/UART bridge on the expansion board to UART0 on P0 and P1.
• 

  RMT peripheral known issue and workaround
  • mogplus8  

  1
  0
  Votes
  1
  Posts
  15
  Views

  No one has replied

• Y

  WLAN issue: wlan auto-connects upon entering function body
  • yoplocheo  

  1
  0
  Votes
  1
  Posts
  16
  Views

  No one has replied

• D

  Pymakr in VSCode can't find NodeJS (but it is installed)
  • danielk  

  2
  0
  Votes
  2
  Posts
  35
  Views

  D

  I've determined so far (by a small hack to pycom.pymakr/pymakr.js after installation) that the PATH that VSCode receives does not include /usr/local/bin, where the "node" executable is installed. (VSCode is being launched from Finder.) So the problem reduces to how to get that PATH into VSCode, which appears remarkably difficult in more recent versions of MacOS, and none of the recipes I've found work reliably without manual intervention. Moving node into /usr/bin is not possible due to MacOS System Integrity Protection. I can at least use pymakr now, but the extension or the installation instructions need to be updated to provide a workaround for this issue.
• R

  Visual Studio Code - Pymark - Download issue
  • ricogte  

  1
  0
  Votes
  1
  Posts
  29
  Views

  No one has replied

• F

  Lopy4 not retry join request every 15 secs
  • fernandes.son  

  10
  0
  Votes
  10
  Posts
  259
  Views

  J

  @fernandes-son That would be consistent with what I believe the code does. The AU915 region only sends join requests at SF12, which take a long time to send, and are thus affected by the specific duty cycle. Some other regions can use faster data rates which mitigates the issue, depending on what data rate is used first. Is there a specific reason this is an issue for you? Normally a device just joins once and after that it doesn't need to do it again, so it shouldn't be a big issue. You may try restricting data rates on the channels, but I wouldn't be surprised if the code actually enforced the DR0 rule for joins per the spec.
• 

  Visual studio code 1.43.0
  • Don-iot  

  4
  0
  Votes
  4
  Posts
  139
  Views

  

  Thanks @pedroknup it works, but for some reason it has to be enabled manually over and over again.
• R

  Pytrack "dfu-util: Cannot set alt interface zero"
  • rene.garcia  

  1
  0
  Votes
  1
  Posts
  128
  Views

  No one has replied

• S

  Core dump problem
  • sita  

  4
  0
  Votes
  4
  Posts
  161
  Views

  A

  Dear @sita, @ps47 also experienced similar errors like you have been observing [1]. He is also using pure LoRa. Using the most recent 1.20.2.rc3 release seems to help here [2]. Thanks @husigeza and the whole Pycom team for mitigating this issue. I tried the new build LoPy4-1.20.2.rc3-0.8.0-vanilla-squirrel.tar.gz and not any “bad00bad bad00bad bad00bad” Core Panic happened till now. With kind regards, Andreas. [1] https://forum.pycom.io/topic/5514/random-core-panic-with-lora-socket-send-recv-device-doesnt-restart-try-with-config_esp32_panic_silent_reboot [2] https://community.hiveeyes.org/t/investigating-core-panics-on-the-lopy4/2878/29
• S

  Expansion Board 3.0 Serial Driver - doesn't exist
  • supovic  

  1
  0
  Votes
  1
  Posts
  105
  Views

  No one has replied

• J

  LoPy4 w/ PyTrack: GPS does not show up!
  gps pytrack • • jlandercy  

  8
  0
  Votes
  8
  Posts
  264
  Views

  J

  @jcaron Thank you for answering. My question is not about WPS which is also a very interesting topic anyway or smartphones applications. My question is about GPS and L76 chipset as implemented on the PyTrack. Indeed WPS helps GPS to get quicker resolution. I do agree with you the PyTrack library is very crude, thank you for the last link, this one is helpful.
• N

  “+CME ERROR: unknown network message” error while sending AT USSD command
  at commands • • nick-IT  

  1
  0
  Votes
  1
  Posts
  271
  Views

  No one has replied

• P

  BLE Advertisement Max Length
  lopy4 ble • • pvstejeswar  

  2
  0
  Votes
  2
  Posts
  234
  Views

  No one has replied

• T

  Pymakr 1.4.13 incompatible with Atom 1.38.2
  pymakr install atom settings • • Tombee  

  1
  0
  Votes
  1
  Posts
  231
  Views

  No one has replied

• J

  Atom/pymakr sync file types
  pymakr atom sync file type • • johand  

  3
  0
  Votes
  3
  Posts
  915
  Views

  J

  @goldfishalpha No, I just moved the txt-files outside the project folder. That is good enough for me. Johan
• C

  Lost PyMakr in VSCode
  vscode pymakr • • ChangedDaily  

  40
  0
  Votes
  40
  Posts
  6176
  Views

  J

  @crumble and @Paul Thornton Switching on 'show hidden devices' in the Device manager (Windows 7) did not reveal anything new. Only COM1, Dell COM3 and Dell COM5 showed up (see screenprint in earlier post). What finally worked to solve my problem is to install the driver file pycom.inf downloaded from https://github.com/pycom/pycom-micropython-sigfox/blob/master/docs/pycom_esp32/tutorial/includes/downloads/pycom.inf from within the device manager (Action >> Add Legacy Hardware >> Search for and install the hardware automatically >> Ports (COM & LPT) >> Have disk >> Browse to pycom.inf file). I installed the 'Expansion 3' option. That installed the expansion board 3 driver, but it showed an error in the device manager (device cannot start). But when I next connected an expansion board V3.1 (with lopy4) to the laptop with usb, a new COM port ('Expansion 3 COM 19') appeared in the device manager, and this one allows me to connect from Atom. Also an Expansion board V2.1A with a lopy can now be connected. So problem solved. Although I still do not know what caused the connection problem. Auto connect does still not work because the working driver is at the bottom of the serial devices list, and the auto-connect takes the first one in the list, that one does not work. But anyway, PROBLEM SOLVED, I can connect manually by selecting the right COM port. Thanks for all the help!
• C

  Sipy deepsleep shield and sigfox transmission
  sipy voltage • • crasu  

  4
  1
  Votes
  4
  Posts
  735
  Views

  P

  Hello @crasu if you use the pycom firmware tool and select "development" in the type dropdown on the communication page instead of "stable" you'll flash the latest release candidate that should have a fix for this.
• N

  Internet protocol login issues
  internet connec • • novajones001  

  2
  0
  Votes
  2
  Posts
  400
  Views

  P

  As in you have a pycom board at 192.168.1.20 that you'd like to connect to. Or are you having issues connecting to a wifi network via your pycom board?