@peterp Tried that, did not help. But i have now found out that the problem is caused by the timer-alarms alone, not because of actually transferring. If i put the transfer inside a while loop instead, with a 4 second sleep interval, i dont have the same delay... So if you want precise timing of events, you can only use a single timer-alarm, which is kinda bad, since Timer-alarms are otherwise a good way of ensuring precise timing..

@juse Same here! Guess the folks at Pycom corrected the issue with the device registration.

Are you also using client.check_msg() to check if messages has been sent to the device? When I use this function and no message is the queue its blocking my code until I send a message to the device but I would like to only check if there is a message and then the code should be continued. Do you have any suggestions for this problem?

In the meantime I found also https://forum.pycom.io/topic/4146/wdt-reset-rtc-also-reset

@pmb_nl i have the same problem, do You have some solution about it? Thanks

@hayesey I am looking for a SIM card NB-IoT enabled in the UK. Could you let me know how you get your SIM card, or where I can find one please?

Still hoping for an answer. In short: How do i get to use ADC 2? How do i take readings from pin P3 for instance? Can i use both ADC channels, maybe even two pins at channel 1 and two pins at channel 2, at the same time?

@robert-hh Great Thanks :)

@jcaron You are absolutely correct on all points: I jest read yesterday that ESP32 has ULP (Ultra Low Power mode) so it makes sense that FiPy will have something like that as well... another field for me to research. But for now I assume that I will not be using deep sleep. About detecting motion: really good point - however my FiPy sits on Expansion Board 3.1 that I believe does not have accelerator...another hurdle... Meanwhile, I did discover something useful that will allow me to experiment with mAh consumption with ease. Check this thread: https://forum.pycom.io/topic/5694/measuring-amperage-consumption BTW, I am using GNSS Click 5 from uBlox with NEO-M8N with cold start of under 30 sec.

I made it work with the following: rtc = machine.RTC() rtc.ntp_sync("pool.ntp.org", update_period=15) time.sleep(5) print(rtc.now()) The update period, if not given as an argument, is kinda slow. As i use in the example, minimum update period is 15 sec, so you may want to sync with the server in boot.py, and do some other stuff / wait a bit in your main.py, before you print the rtc time.

Installing python 2.7 instead of 3.X solves the problem , now the serial port is working fine .

@jcaron @robert-hh Thank you guys. It works right now. The problem was RX and TX. I swap them, it works right now.

@robert-hh and @andreas Thank you for the help. Yeah the last one is kinda obvious now! :)

FiPy is alive :D Thank you so much!