@papasmurph Use the socket.bind( x ) where x is your desired port before doing the send

@prashanth I have seen that TTN uses SF9 @ 869.525 MHz for the RX2 response. There is a rational that a gateways can send with higher power at that frequency, and therefore cover the same distance, while having shorter transmission times. That works, if the node has been connected with OTAA. In that case the RX2 parameters are sent to the node. I was a little bit surprised when I stumbled over that.

Well for some reason this was no longer a problem anymore, even though I don't believe I changed anything.

'\t' is the same code as '\x09', see https://theasciicode.com.ar/ascii-control-characters/horizontal-tab-ascii-code-9.html

@jcaron AFAIK, file I/O is already buffered. Glancing at the code, it seems to be 512 byte. I recalled 4k, but that was for the ESP8266 port. So using a larger buffer may improve things.

@Lucas_Vieira There is one here: https://github.com/robert-hh/BME280 It is a driver by Adafruit driver and others, based on the Bosch data sheet and examples, which I ported to the Pycom family devices. There are two variants, bme280_float.py and bme280_int.py, which differ from the way the internal calculations are made (integer or float numbers). The representation of results differs for one method (returning integers of floats). But that is documented in README.md

@andrethemac As far as I recall, the voltage regulator is a LM3281. The docs pages have been reorganized, and it got only worse. Not only that the omissions and faults were not fix, information disappeared which used to be there. Also, this regulator is only specified down to 3V input.

Bottom line here is that PyCom sells less than user friendly devices and provides poor documentation on use. I have been trying repeatedly to get my LoPy4 to OTAA join to no avail. I have scoured and tried just about every code sample on GitHub and nothing. Sadly, I did get my 32u4 feather to join with no issues whatsoever. This pisses me off because I dropped nearly $80 on PyCom (board, LoPy4, antenna, shipping) The forum is hardly readable. As are the docs. Just plain lousy.

@dnear1 can you use FTP to check the contents of the file system including main.py? Also what happens if you Send Ctrl-C on the serial interface?

@Eric73 Great, thanks for your help !

Have you actually tried to see if you can transfer data at this range? You may need to try alternative spreading factors to be sure but 1km is readily achievable without having to resort to breaking regulations on plower limits. Andrew

After firmware update this problem vanished in my case.

@robert-hh Ah, Thanks !!

@abhishek2101 Not sure I understand the question? Just set up deep sleep to wake up after 60 minutes. If you are using "native" deep sleep (machine.deepsleep), then just pass the sleep time as an argument to machine.deepsleep. The argument is in milliseconds, so 60 minutes would be 60 * 60 * 1000. If you are using PyTrack/PySense/PyScan-controlled deep sleep (py.go_to_sleep), then pass the sleep time as an argument to setup_sleep. The argument is in seconds, so 60 minutes would be 60 * 60. When you wake up, do your thing, then go back to sleep. The details of what you should do while awake (especially in terms of network) depends a lot on the network used and many parameters, but this has been covered a lot in various topics in this forum, including some you initiated. You should probably go re-read the answers that were made to your previous questions.

@cyby I think @robert-hh meant the right connector among the 3 présent on the board (there’s one for WiFi/BLE, one for 868 and one for 433 MHz). It’s easy to mistakenly connect the antenna to the wrong one.

@caseyrodgers Pycom may have a database of device numbers & types. That one may have wrong entries. You can send a mail to Pycom with the WiFi Mac address, explaining the trouble, such that they can fix the database. You can get the mac with: import machine,binascii binascii.hexlify(machine.unique_id())