In older firmware versions, the time server is fixed to ntp.reciva.com and can not be changed.
However, if you have a broadcast time server on your local network then the radio will trust that and set its clock accordingly.
From about v257-a-295 onwards, the radio will respect the NTP server specified in its DHCP parameters, or fall back to ntp.reciva.com if none is given there.
Starting from that version, too, the radio will ignore broadcast time announcements if it has managed to establish direct communications with a time server.
(It will still accept broadcasts as a fallback if the configured time server is invalid or unreachable.)
- if your DHCP server specifies an NTP server address, the radio will try to contact the server you specified;
- if your DHCP server doesn't specify an NTP server, the radio will try to contact ntp.reciva.com by default;
- if neither of the above succeeds, but there is an NTP server broadcasting on your network, the radio will synchronise to these broadcasts;
- if all the above fail, you will have to enter the time manually.
If you set the time by hand then the radio will assume that you are really trying to set the local time offset of your own timezone.
It remembers the difference between the time you have set and the NTP clock (which always reads in UTC) and applies this same offset for all future corrections.
Some radio models do have a different way of setting the time, where you are prompted to choose your timezone from a list and the radio then figures out the appropriate offset for itself.
However, this only really works for radios that are intended for sale in a particular geographical market since otherwise the list of timezones becomes unmanageably large.