"NFC (Near Field Communication) tag reader is a technology that allows devices to communicate wirelessly over short distances. It enables data exchange and interaction between compatible devices, such as smartphones, tablets, and NFC tags. NFC tags are small, passive devices that can store and transmit information when brought into proximity with an NFC reader. To understand what an NFC tag reader is in more detail, you can refer to the article ""What is NFC Tag Reader"" on Appuals.com (https://appuals.com/what-is-nfc-tag-reader/). The article provides a comprehensive explanation of NFC tag readers, their functionality, and various applications. Here is a step-by-step summary of the information provided in the article: Definition and Introduction: The article starts by explaining the basic concept of NFC technology and its use in tag readers. How NFC Tag Readers Work: It describes the technical aspects of NFC tag readers, including the radio frequency used, operating range, and the principle of electromagnetic induction. Reading NFC Tags: The article explains the process of reading NFC tags using a compatible device like a smartphone or tablet. It highlights the importance of enabling NFC functionality and bringing the device close to the NFC tag. Applications of NFC Tag Readers: The article lists several practical applications of NFC tag readers, such as mobile payments, access control systems, transportation, and data exchange between devices. Compatibility and Limitations: It mentions the compatibility of NFC tag readers with different devices and discusses certain limitations, including the short-range communication and the need for proximity. Conclusion: The article concludes by summarizing the key points about NFC tag readers and highlighting their potential for future technological advancements. Overall, the article on Appuals com provides a comprehensive understanding of NFC tag readers, their working principle, applications, and limitations. It serves as a valuable resource for anyone looking to gain insights into this technology."

@Dale-Fletcher Which firmware version do you use? The time window for receiving a OTAA join confirmation is small (~10 ms after 5 or 6 seconds) and the PyCom (ESP32) device have not You could try to join with a lower data rate or init Lora with a higher spreading factor. That will increase the time window for receive. Edit: Do you see the join request in the TTN gateway console?

I am having the same problem. Is there a solution?

@Danny-Helwegen I understand, but that was not the intention of my question. You could try the following: Disconnect the device from the GPy and measure the current that flows from either output of the device to GND of GPY, with the other device output floating and the GPY's USB port connected to your PC. The current should be 0. If not, the device has internal connections to GND, which can have the effect you see.

@SanOls When you look at the file, do you see any lines with coordinates with values null or 0 or something similar? I think you need to add more logs, including: Timestamps, ideally before and after send, coordinates and recv Logs of the return value of coordinates in all cases Logs of any retries (which I believe would happen if recv returned something other than 'bob' What is the duration of each good/bad phase? Looks like about 8 to 10 points, which should be 15-20 seconds each, is that the case? What is the range of the RSSI values?

@jcaron MERCI DANKON THANG VIELENDANK

Have a look at the docs on Github: https://github.com/pycom/pymakr-vsc#readme especially: https://github.com/pycom/pymakr-vsc/blob/next/GET_STARTED.md https://github.com/pycom/pymakr-vsc/blob/next/WHATS_NEW.md Hope it helps!

@firemonkey Did you have success with this? I'm having issues where the pygate drops off the network (usually when the router loses power) and it never reconnects.

@BADREDDINE-Bouatrous Pycom INC went bankrupt a while ago, and the follow up company Pycom B.V. discontinued all previous products. The new products seem not to be available yet

@hjoe Hardly. If you purchased through the kickstarter campaign, then there is anyhow no guarantee for a value. If you purchased from Pycom Inc, then this company went bankrupt, and the time slot for register claims ended a while ago. The new owner of Pycom BV is hardly interested to refund any claims against the previous Pycom. Anhow I think the brand name Pycom lost its reputation.

@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!

You will have to sync RTC with some NTP server first. See: https://docs.pycom.io/firmwareapi/pycom/machine/rtc/ and https://docs.pycom.io/tutorials/networkprotocols/ntp/ Of course, this means you will need to connect to the internet in some way.

I think I finally found an answer on how to properly reset the modem in case it just won't attach to a network. Reset the modem by sending following AT-command: lte.send_at_cmd('AT+SQNSFACTORYRESET=?') Unlike lte.factory_reset() - which seems to use AT-command AT+SQNSFACTORYRESET - this command will successfully reset the modem to factory state. A reboot of the device is necessary to finalize the reset! After this process the modem should attach to the network without any issues! Also, for further information see: AT Commands Reference Manual, 15.1 Device Reset to Factory State

@ErickM said in Connect to wifi: VS say missing imports VS do not know pycom libraries at all, so do not worry.

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.