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

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. [image: 1678031203013-pymesh-problem.jpg] 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.

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

@Beatriz-Tomé can you clarify what exactly you are doing (including relevant code), what you are expecting, and what is actually happening (with relevant logs/errors)? At this time it is unclear to me what your issue is.

Thanks for the answer. I already tried using callbacks, but couldn't quite figure it out. Luckily, i managed to find some piece of code on the web which seems to check if there are any data in the socket. # Check if the socket is busy r, w, x = select.select([tx], [tx], [], 0) if r or w: tx.send(package) Where tx is the name of the socket.

@keik I'm a bit puzzled... In raw LoRa you define all the modulation parameters, which includes the raw data rate, and the rest can be computed from there. What is it exactly you're trying to find out? What is the maximum data rate you can use and still receive data at the other end for a specific pair of devices (taking into account distance, obstacles, etc.)? Note that this can vary over time (e.g. weather, people moving around, foliage on trees...), and depends on what is an acceptable packet loss. What is the maximum actual data rate for a given modulation, taking into account overhead, duty cycles, etc? Something else? What is the LoRaWAN feature you mention that does this exactly?

@Andres-Ortega You can set up the lopy4 as WiFi AP and connect it with the Arduino. Then you can do socket level data exchange. That's easy with the LoPy4, and some more work with the Arduino. But there should be many examples to go for. You could as well set up a MQTT server in your network (any PC, RPi, etc will do) and use it by both the LoPy4 and Arduino for data exchange.

@nadvorvo For anyone having the same issue today, this solved it for me too

Hello everyone, if you are seeing this comment !... So coming back to the problem I had. Since I was beginner so I tried almost all the tools and tricks to connect the pycom lopy4 using pymakr and vscode. But the issue was resolved by updating the firmware of the module to the latest one. Hence if you are having such issues don't forget to update the firmware. thanks to Robert, btw!

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

It says OSError: connection refused after trying to connect with connect(adv.mac)