Repository navigation
Version 3.0.5.0
- corrected interleaved requests when the client's source port didn't match the destination NTP_PORT
- Ublox compliant GNSS receivers set to Stationary GNSS mode at startup for improved timing accuracy
- added python testing script to verify server alignment
(for more information please see: https://github.com/roblatour/ESP32TimeServer/blob/main/testing/server_alignment/README.md ) - updated to use Espressif's Ethernet and OTE update (TCP 3232) processes in place of the Arduino Ethernet and OTE update (UDP 3232) processes
(for more information please see: https://github.com/roblatour/ESP32TimeServer/blob/main/misc/UsefullPowerShellCommands.md ) - improved accuracy with ESP32-P4 chips release 3.0 and beyond,
the program now measures how far the Ethernet PTP clock’s second boundary is ahead of or behind the GNSS PPS UTC-second boundary with these
results being used to discipline the PTP clock and provide better NTP response - provide for a three minute Stratum 1 holdover period (the duration can be changed in the settings).
A holdover period is the time after which the server loses its connection to its primary reference source but continues to maintain an accurate clock using its own internal oscillator.
However, during holdover, ESP32TimerServer also increases the advertised root dispersion over elapsed time to reflect decreasing confidence. - several other updates and improvements
Thanks to Github users: Duglum, spacemanspiff2007, and radiowave911 for reporting issues / requesting feature requests helping to improve ESP32TimeServer!
Important Notes
-
If you're upgrading from a prior release, please apply your prior setting file changes to the new settings file
-
Processing thresholds were lowered in this release, they are now at:
7,000 requests/second for ESP32-P4 release 1.3 chips, and
10,000 requests/second for ESP32-P4 above release 1.3 chips