@paul-thornton I replied on another thread that I think you responded to that I have this issue with 1.20.0.rc0. I reverted back to my unmodified build of 1.19.0.b4 and the problem disappeared. I found that after machine.reset() the clock still would not sync reliably (or at all) and even sometimes after a hard reset by hitting the reset button.

@wolli01 Hier mein Code import urequests userdata = {"p1": "Wohnzimmer", "p2": "24.12.2018", "p3": "23.97"} url = 'https://Homepage.de/live1.php' res = urequests.post(url, headers={"Content-Type": "application/json", "Accept": "application/json"}, data= str(userdata)) res.close() auf den PHP Server: <?php //Sensor1 $p1 = $_GET["p1"]; $p2 = $_GET["p2"]; $p3 = $_GET["p3"]; $inhalt = array($p1, $p2, $p3); // Speichern der Datei $eintrag = implode(";", $inhalt); file_put_contents("sensor1.txt", $eintrag); ?>

@aniket_yeole you can change some of the parameters (including SF) using setsockopt. To change the frequency you’ll need to remove all channels and re-add channels with your chosen frequency. But beware, the network can change those settings via MAC commands.

@tttadam No, not compatible. The pigtails have either a male or female (tech speak) SMA plug. The one with the rod is the male one. There are adapters available, but better get another pigtail. P.S.: That happened to me too. I ended up in having all sorts of pigtails and adapters in my drawer.

In case anybody else has this problem. In our case it was either a defective L01 OEM module or a manufacturing defect with the PCB. We built a second unit and the LoRa worked fine in that L01 module. It did not hang or crash, and the LoRa pings worked fine over several minutes of testing.

Hi guys, I didn't read everything below in detail, but I just wanted to add that the Pymakr package for Atom has an option for not rebooting after upload :) No need to switch to FTP if the reboot part is the issue. Actually, VSCode is supposed to have the same option, but when testing it just now it shows a bug (it doesn't show any output in the terminal after upload). I'm going to fix that now and add it in the next release. After that, you can add "reboot_after_upload" key to the global or project config file ("reboot_after_upload": false) and it will not reboot the board after uploading or downloading.

Ok, some news: If I publish something to any of my topics with QoS set to 1, I can receive the message from the topic I subsrcibed to, but, unfortunately, only one time. The callback function runs fine, but then, the main loop is blocked. I can see, that the sensor threads are still running fine, but there are no more data published, because of the blocked main loop. Cheers, Thomas

@re Yes. The SX1272 of the LoPy of SX1276 of the Lopy4 can only listen to one frequency and one SF/BW setting at a time. The target platform for these chips is motes (= Lora nodes, AFAIK), not gateways. Gateways use typically a different chip set, like the combination of Semtech SX1257 and SX1301/SX1308. If you need a full service gateway, you must get one. There are raspi add-on boards Like the IC880a from ICMP and the RAK831 which offer full service. Or you buy a ready gateway. Look at the The Things site for product lists. ICMP offers also a ready built box with raspi, receivber & software for testing.

@jmarcelino What is bluetooth.init(id=0, mode=Bluetooth.BLE, antenna=None) used for then? I also noticed when I was trying to run it, that Bluetooth.BLE as the mode did not work at all.

@ledbelly2142 I'm very glad that you found a way. The Expansion board 2 has no firmware. Only expansion board 3 has. If the other board you used was a model 3, it could have been caused by the firmware updater, requiring multiple resets. I faintly recall something like that.

In my opinion RESET pin should not be left floating. Try to connect pull-up resistor to 3.3V in 10k-20k range. Check L01 OEM Baseboard schematic: https://docs.pycom.io/product-info-datasheets/oem/l01_reference Edit: Sorry, now I noticed the reset pull-up already being in your schematic. Anyway try to use FTP client for script uploading.

@paloma You can configure Filezilla in a way, that double-click on a file in the LoPy pane will open that file in your Favorite editor. Storing that file will transfer it back to the LoPy. For REPL, you might also use other tools like screen, picocom, putty, .., which support VT100 code sequences, in case you need them.

@robert-hh I looked at that device but I'm trying to keep my system as simple as possible so I did not pursue that option. I does, however, look like a viable alternative in the event your s/w solution was inadequate for some reason. thanks.

Hello Xykon, I kindly wanted to check, if there is an update on the Nanogateway support for PyBytes? It would be fantastic for me to have that supported. I'm running multiple LoPy's that are repoting sensor data via LoRa to a Nanogateway.

@william About topic 1: I do not know that the LoPy has any of that by itself. There is a 3.3V power regulator, but thta cannot handle string interference, which may com in at each and every signal line. Topic 2: The watchdog is software, can handle some run-away software situation. You might need a separate hardware watchdog which pulls reset.