Quantcast
Channel: Forum - Recent Threads
Viewing all articles
Browse latest Browse all 5781

NX SNTP nx_sntp_client_receiving_updates

$
0
0

Dear Forum,

Has anyone had any luck getting the example from the documentation to work for NTP?  In using it in unicast mode.  In nx_sntp_client_receiving_updates Im getting back NX_SUCCESS for status but the server_status Im getting back NX_FALSE.  (0).  It should be NX_TRUE for it to proceed to get the nx_sntp_client_get_local_time.  After just initializing the client I would presume the receive status should be coming back as a NX_TRUE, unless the max time lapsed with out a valid update or limit on consecutive updates is incorrectly set so that in a init situation its server status is = 0.  Im not sure what those two registers are called if I want to change them.  


Also, in this example there is a thread spawned and all the ntp stuff is done in the thread.  Creates the client server and then makes calls with nx_sntp_client_get_local_time.  Is it recommended that a thread be spawned off and start this client server.  Can I simplify this by simply calling nx_sntp_client_get_local_time when I need to get the time without having this client service running?  My time needs are to get the time at boot, then when ever a user requests it, and then once every few hours/day to keep the rtc on time. 

Thanks

Matt


Viewing all articles
Browse latest Browse all 5781

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>