Hello Guys, havin the following Problem:
when using
time.h
and
configTime(0, 0, server1, server2, server3)and for example the first server is not avaiable, the code does not switch to the second and third server!
But my expecation was if one is not accessible it switched to the other ones.
@hasenradball I believe the sntp servers are passed through to the sdk
@devyte Hi wat do you mean?
it means that it's the sdk who is supposed to handle the servers, and that if something is broken with that, it's likely in there
assuming I'm right, of course
@devyte if I understand you right, you mean the server handling is done in the SDK and that does actually not work?
half right about what I mean
the server handling is done in the SDK, so if it does not work, the issue is in the SDK and not in our core
but you need to make sure of that. Personally, I don't think I've ever seen multiple sntp servers tested
@devyte Thank you, do you know where to look at in the SDK?
no. To test it for correctness you'd have to make a small project that only uses the sdk without our core (there are examples out there), then set up the wifi, and try out the api that sets up the sntp servers. The sdk api is described in document 2C of the Espressif documentation (NONOS api reference pdf)
you can also look at our use of the sdk api in our core, just look at the source of configTime
and I just saw your issue
as you can see, our configTime is a paper-thin wrapper around the sdk api, so if something is messed up, it's most likely in the sdk and not our core
the sdk is hosted here: https://github.com/espressif/ESP8266_NONOS_SDK
but be aware they're not very good at responding to issues. You have to giftwrap issues for them
@devyte Thanky you, just one thing: what does NONOS stand for?
NONOS NON-OS no operating system
as opposed to the freeRTOS sdk, which does integrate a real time os
but leaves you with a whole lot less available mem as a result
@devyte How can we check the Problem is located in the SDK?