I would like to know if there can be a difference in current demand from the antenna in different parts of the sketch and if the described solution could be sufficient for me...
With a Wifi.getTime() command, the board is able to receive a value from a NTP-server. This happens in the setup loop. However, when the board seems to start connection with the IoT Cloud in the void-loop (visible in the serial monitor by a message that it is connected to the programmed SSID), it hangs, resets and starts all over. Before the connection message, the loop is excuted around 30 times without any delays programmed...
Do not hijack. Thread split.
That combination of words does not make sense. An antenna does not have a current demand.
Have you tried a bigger power supply? ESP boards are notorious for rebooting on WiFi use.
I'm sorry, I thought the issues were related enough to continue on the same topic.
But I was wrong, I will try to explain in my best Dunglish! The power demand from the WiFi board was not the issue. To get the time from the server, I use the WiFiNINA and WiFiUdp libraries and run a code in the setup. When the loop started, both the mentioned library and the default Arduino iot WiFi handler are active and two captains on one ship doesn't work.
The solution was to first run all the code to get the internet time, terminate the WiFi handling by the custom libraries with a WiFi.end() command and then let the default Arduino IoT handler take over.
Hi,
Sound like trying to power up the Apollo 13 command module!!!!
Tom... 
1 Like
This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.