@crumble Thanks for the quick reply. I had tried a similar thing with Chrono earlier, but it failed because while executing, if that section of code isn't encountered within the stipulated time, then it skips it and the model would lose a message. This is the sample code I had tried (For testing purpose, I kept the interval of 5 seconds): #When no beacon nearby else: chrono = Timer.Chrono() chrono.start() if (chrono.start() or 5<chrono.read()<=6): s.send(msg) if (s.send(msg)): print("Message Sent") chrono.reset()

@rcolistete I was incorrect in my previous posting. When using a Pysense/Pytrack and the deepsleep functions available in there respective API's. the main ESP32 processor is powered off and thus the RTC data is lost. Example: https://docs.pycom.io/pytrackpysense/apireference/sleep.html #from pytrack import Pytrack from pysense import Pysense from LIS2HH12 import LIS2HH12 import time #py = Pytrack() py = Pysense() # display the reset reason code and the sleep remaining in seconds # possible values of wakeup reason are: # WAKE_REASON_ACCELEROMETER = 1 # WAKE_REASON_PUSH_BUTTON = 2 # WAKE_REASON_TIMER = 4 # WAKE_REASON_INT_PIN = 8 print("Wakeup reason: " + str(py.get_wake_reason())) print("Approximate sleep remaining: " + str(py.get_sleep_remaining()) + " sec") time.sleep(0.5) # go to sleep for 5 minutes maximum if no accelerometer interrupt happens this will also lose the RTC data. py.setup_sleep(300) py.go_to_sleep() When using the API available in the machine library. The RTC data is retained during deepsleep. import machine machine.deepsleep(5000) # sleep for 5 seconds. and retain the RTC data. this does not power off the esp32 but does put it in a very low power state

@abhishek2101 two aspects: are we allowed to? The answer is yes. Adafruit uses the MIT licensing, which gives you a lot of freedom. will the libraries work? Not out-of-the box for most of them. You typically have to adapt access to peripheral devices like I2C, SPI etc. Adafruit uses a different hardware abstraction method. But the required changes are typically small, and the adafruit libraries are often well designed.

Hi, did you make it? I want to send login data from my smartphone to Lopy.

Cool, I need it the other way around. I would like to send login data from my mobile phone to my Wipy/Lopy. Can you help me with how to proceed?

@paul-thornton No errors that I can see. Is there a log file? I am connecting to the windows machine using the same usb cord that works on the mac.

@crumble said in Lopy freezes after 6 - 12 hours: I do not understand why pycom does not declare the 1.20 branch as stable. It fixed so many errors for me that I like to see it as the stable branch. Maybe they want to deploy it together with some cloud changes. But 23 will be the better number for this ;) Features are still being worked on and improved. Even more stability cant hurt :D

@johand Thanks for the answer this work prefect

@paul-thornton said in How to send/receive LORAWAN MAC Commands?: https://docs.pycom.io/firmwareapi/pycom/network/lora.html#lorastats I'm not sure whether lora.stats() rx_timestamp is of use, it does not seem to represent a time value, but if it does, how do I convert it? [LORA ] 2019/02/21 04:51:55 (rx_timestamp=0, rssi=0, snr=0.0, sfrx=0, sftx=0, tx_trials=0, tx_power=14, tx_time_on_air=0, tx_counter=0, tx_frequency=0) [LORA ] 2019/02/21 04:52:04 (rx_timestamp=30539834, rssi=-45, snr=7.0, sfrx=3, sftx=5, tx_trials=1, tx_power=0, tx_time_on_air=57, tx_counter=0, tx_frequency=0) [LORA ] 2019/02/21 04:52:11 (rx_timestamp=38155453, rssi=-38, snr=8.0, sfrx=3, sftx=5, tx_trials=1, tx_power=0, tx_time_on_air=47, tx_counter=1, tx_frequency=0) [LORA ] 2019/02/21 09:04:47 (rx_timestamp=45778581, rssi=-43, snr=8.0, sfrx=3, sftx=5, tx_trials=1, tx_power=0, tx_time_on_air=47, tx_counter=2, tx_frequency=0) [LORA ] 2019/02/21 09:15:32 (rx_timestamp=690412324, rssi=-47, snr=6.0, sfrx=5, sftx=5, tx_trials=2, tx_power=0, tx_time_on_air=57, tx_counter=4, tx_frequency=0) [LORA ] 2019/02/21 09:15:38 (rx_timestamp=696682500, rssi=-48, snr=6.0, sfrx=5, sftx=5, tx_trials=1, tx_power=0, tx_time_on_air=57, tx_counter=5, tx_frequency=0) [LORA ] 2019/02/21 09:15:44 (rx_timestamp=702935506, rssi=-47, snr=6.0, sfrx=5, sftx=5, tx_trials=1, tx_power=0, tx_time_on_air=57, tx_counter=6, tx_frequency=0)

@abhishek2101 Go to the profile of the person you want to chat with, and in the middel right there is a circle with some dots. If you open that, teh first topic is: start a chat.

Fair enough, I did quite a bit of reading on TTN about Gateways, Nodes, Applications, etc... I think once I can muster up some more funds for an actual Gateway; I will convert this to a Node. This PyCom LoPy4 is really a learning experience for me. The idea of using MicroPython is all new to me. Cheers,

@johand After I've set IP for HTTP server wlan.ifconfig(id=1, config=('192.168.4.10', '255.255.255.0', '192.168.4.1', '192.168.4.1')) i've tried to read IP address of HTTP Server and that was the problem, it's keep returning me '0.0.0.0'. IP address was set properly to '192.168.4.10' but function returns '0.0.0.0'. print('Network config:', wlan.ifconfig()) Network config: ('0.0.0.0', '0.0.0.0', '0.0.0.0', '0.0.0.0') Thank you for your help. @pigamonte I've managed to do it with 1.18.2.

@snehasg96 Can you try the same thing with utime.sleep() instead? I haven't tried it myself yet, but I plan to do so.

@hobbypy any programming language with a serial library should work. simply open a serial connect to the board via your preffered language / framework. and send the code as a string over it. The response will come back over serial just like the REPL does.

@abhishek2101 most GPS modules have standard NMEA output, so I would be surprised if this one didn’t.

@pyshi were you able to connect the adafruit gps to lopy4 ?

@pierrot10 Hi, are you able to solve the issue?

@gustavo said in RED LORA CON LOPY4: buenas noches @John-Baird si es correcto pero estoy tratando de usar estos equipos lopy4 tanto para el nodo como para el gateway nose si se pueda hacer eso y el sensor para medir el flujo de agua 1/2" YF-S201 nose si ud conoce otro sensor mas bueno y es para armar una red lorawan por favor quisiera su opinion y su ayuda sobre este proyecto gracias Hi Gustavo - Sorry for the delay, I've been unwell for the past two weeks. Darn influenza! I'm not sure about the LoRaWAN side of things as I mostly use LTE for wide area networking. There are folks on this forum who use LoRaWAN a lot who can help. As for the YF-S201, there are a few things to consider: The device requires at least 4.5v to run. This means you can run it from the VIN of the WiPy, but only if you are supplying it with more than 4.5v. The WiPy will run happily from 3.5v - the YF-S201 will not. This might make using batteries difficult. The YF-S201 has an accuracy of 10%, but most of this is on the low side. A measurement of 100L might be as much as 110L, but is probably somewhere between 100L and 90L. If you wish you can experiment and figure out a "correction factor". Be aware that the lower the flow rate, the worse the error is. The device works best if it measures the output of a pump. If the water is moved by gravity it's not so good. The YF-S201 out is 5v TTL, while the inputs of the WiPy are 3.3v. This means you need to shift the level of the output. A simple pair of resistors will work. I'd suggest you look at using the output of the meter to drive an interrupt on the WiPy. This will let you count pulses while doing other things. If you need help with any of the above, let me know. Hola, Gustavo. Lo siento por la demora, no he estado bien durante las últimas dos semanas. Maldita gripe! No estoy seguro del lado LoRaWAN de las cosas, ya que principalmente uso LTE para redes de área amplia. Hay gente en este foro que usa mucho LoRaWAN que puede ayudar. En cuanto al YF-S201, hay algunas cosas a considerar: El dispositivo requiere al menos 4.5v para funcionar. Esto significa que puede ejecutarlo desde el VIN del WiPy, pero solo si lo está suministrando con más de 4.5v. El WiPy se ejecutará felizmente desde 3.5v, el YF-S201 no lo hará. Esto podría dificultar el uso de las baterías. El YF-S201 tiene una precisión del 10%, pero la mayoría está en el lado bajo. Una medida de 100L puede ser tanto como 110L, pero probablemente se encuentre entre 100L y 90L. Si lo desea, puede experimentar y averiguar un "factor de corrección". Tenga en cuenta que cuanto más bajo es el caudal, peor es el error. El dispositivo funciona mejor si mide la salida de una bomba. Si el agua es movida por la gravedad no es tan buena. El YF-S201 de salida es 5v TTL, mientras que las entradas del WiPy son 3.3v. Esto significa que necesita cambiar el nivel de la salida. Un simple par de resistencias funcionará. Le sugiero que mire el uso de la salida del medidor para provocar una interrupción en el WiPy. Esto te permitirá contar pulsos mientras haces otras cosas. Si necesita ayuda con alguno de los anteriores, hágamelo saber.