Categories

• Announcements & News

  Announcements regarding our community

  Beta Announcements & Development News
  240
  Topics
  3551
  Posts

  E

  i need 5.000 pieces pycom w01 module...who can help to me?
• Helium Hotspot

  Helium is a LoRaWAN service that allows you to send and receive LoRa packets from your nodes. Feel free to discuss it here!

  32
  Topics
  187
  Posts

  N

  @Kevin-James ItItss the IP address of the miner, log into your router to find it.
• Pylife

  Discuss our new product here

  15
  Topics
  225
  Posts

  

  @Daniel-Almeida PyGo products are not support by the new Pycom BV company, and in fact they never worked. The community is waiting, if there is some activity by Pycom BV for PyGo, like publishing the hardware design and the firmware sources. But even if, it will take time.
• Pybytes IoT platform

  Pybytes IoT platform for all Pycom devices

  Announcements & News

  Ideas

  Support & Troubleshooting
  314
  Topics
  1098
  Posts

  B

  If a want to register my Pycom LoPy 4 device in the Sigfox backend I get this error: "CRA rejected the modem ownership transfer: Invalid PAC code: xxxxxxxxxxxxxxxx (please contact your device supplier to obtain this code)" I tried also an other LoPy4 device and then I get this error: "Invalid PAC code: xxxxxxxxxxxxxxxx (please contact your device supplier to obtain this code)"
• Getting Started

  Post in here for any discussion, questions or support you need with your projects!

  Discussion

  WiPy 2&3

  LoPy

  SiPy

  GPy

  FiPy

  Pymakr

  Pymate

  Expansion Board

  MicroPython
  5073
  Topics
  26645
  Posts

  V

  @Christo-Vorster Pycom did restore the Sigfox credentials in the 1.16.6 Firmware updater, so you should now be able to get your devices registered as I just did!
• Tutorials

  Tutorials for your Pycom stuff

  Projects

  Guides
  131
  Topics
  596
  Posts

  J

  @Yorick-Blom See https://forum.pycom.io/topic/7505/fast-fft-for-iot-application/2
• Firmware

  Support for Pycom Firmware

  Discussion

  Enhancements

  Issues & Bugs
  716
  Topics
  3764
  Posts

  A

  Hello! I'm trying to create a LoRa Mesh or PyMesh network. I'm using LoPy4 and FiPy with expansion board 3.1v. After a few problems, I was able to create a PyMesh network using Pybytes. I have a project on Pybytes with WiFi and LoRa added as networks. The devices have the same firmware version (1.20.2.rc11). They connet to Pybytes and they get a role (the rgbled change its color). However, I checked the monitoring tab and they don't find neighbours. Moreover, I set the FiPy as Border Router, but something happened because in the image above it isn't appear as I defined previously. I'm running tests right now, the FiPy is the leader of the network (MAGENTA) and the LoPy4 is a router (GREEN). Do I need another LoPy/FiPy to find neighbours between them? I read the tutorials in the Pycom website, but I'm getting a bit confused because what I found here (https://docs.pycom.io/pymesh/licence/) works, but couldn't find neighbours in the network, and what I also found on the website (https://docs.pycom.io/firmwareapi/pycom/network/lora/pymesh/) doesn't work. It throws an error: Guru Meditation Error: Core 1 panic'ed (LoadProhibited). Exception was unhandled. Core 1 register dump: PC : 0x400ff85a PS : 0x00060030 A0 : 0x800ff890 A1 : 0x3ffdd450 A2 : 0x00000000 A3 : 0x00000000 A4 : 0x3f433b18 A5 : 0x3ffdd5b8 A6 : 0x0000002a A7 : 0x0000098a A8 : 0x3f40fc38 A9 : 0x3ffdd430 A10 : 0x00000000 A11 : 0x00060023 A12 : 0x00060020 A13 : 0x00000000 A14 : 0x0000000a A15 : 0x3ffdd5e0 SAR : 0x0000001e EXCCAUSE: 0x0000001c EXCVADDR: 0x00000000 LBEG : 0x4009527c LEND : 0x40095287 LCOUNT : 0xffffffff ELF file SHA256: 0000000000000000000000000000000000000000000000000000000000000000 Backtrace: 0x400ff85a:0x3ffdd450 0x400ff88d:0x3ffdd470 0x40108334:0x3ffdd490 0x40101e71:0x3ffdd4c0 0x400fe299:0x3ffdd4e0 0x4010a251:0x3ffdd500 0x40101f84:0x3ffdd5a0 0x400fe299:0x3ffdd600 0x400fe2c6:0x3ffdd620 0x400e1679:0x3ffdd640 0x400e1908:0x3ffdd6e0 0x400e01bd:0x3ffdd720 The code above had some core dump info but it was a bunch of letters without much sense and I decided not to put it here. So I would appreciate if someone can give me some hints about whats happening or what to do now.
• Wireless Technologies

  Discuss your project, questions, issues with wireless technologies here

  WiFi

  Bluetooth

  LoRa

  Sigfox

  Cellular
  3
  Topics
  24
  Posts

  A

  I am woking on an IoT project that uses a device with LTE Cat M1 capability, and I was wondering if I would be able to use a Data only SIM from Google Fi?
• Software Tools

  Support for Pymate, Pybytes, Pymakr and the Firmware Upgrade Tool

  Discussion

  Enhancements

  Issues & Bugs
  222
  Topics
  975
  Posts

  K

  Hi all, I'm interested in developing a healthcare app that can connect patients with doctors and healthcare professionals in real-time. I came across Devlight healthcare app development services and their telemedicine app development caught my eye. Does anyone have any experience with them in this area?
• Events

  Discuss things about Pycom Hackathons, Workshops, Webinars and more!

  15
  Topics
  133
  Posts

  C

  @Renate-Chaplin I'm on the West Coast and I think somewhere near the bay area would be good.
• Comments & Feedback

  Got a question? Ask away!
  320
  Topics
  1344
  Posts

  M

  Re: microWebSrv2
• Bugs & Issues

  GitHub Repos for Bugs & Issues

  Pytrack & Pysense

  Pycom Devices (LoPy, WiPy 2.0, etc.)
  509
  Topics
  2527
  Posts
  No new posts.
• Jobs at Pycom
  7
  Topics
  12
  Posts

  B

  Do we know a Pinout designer who can do beautiful pinout drawings for our next generation OEM modules and their accessories? If so, please would that person get in touch with bettina@pycom.io. Drafts available. This is a paid project.
• PyGo

  Pygo & Pylife section

  11
  Topics
  65
  Posts

  

  @hjoe It's a shame that Pycom does not publish the documentation about and the firmware & tools of the PyGo. Then the community could create useful applications for it. And I have doubts, that the can sell this to someone. Technically, the value should be low. The only value could lie in intellectual property, which could be of use in IP disputes. The bad design decision seems for me, that the device have no hard fall-back mechanism to recover using the ESP32 bootloader, without cracking the enclosure.