Уважаемые участники, сегодня заказал данный аппарат. Естественно, в руках еще не держал.
Хочу сделать NTP-сервер stratum-1.
Есть ли возможность снимать параллельно данные GPS-времени (NMEA или 1PPS) не мешая основной работе коробки по назначению?
Синяя система имеет встроенный сервер NTP-stratum-1.
(2017-08-14, 23:28)kevinmcc Wrote: [ -> ]Синяя система имеет встроенный сервер NTP-stratum-1.
Thank you for information. I would like to ask you to clarify two things.
First, is this correct that all of outher (WAN) users can sync a time by SystemsBlue NTP server (if port #123/udp is forwarded by router)?
And second - what kind of software provide SystemBlue's NTP-service? Is this BSD-like 'ntpd' or self-made implementation?
Regards,
Yes, just map the port to System Blue IP address.
Not sure what the server software is.
Only setting on System Blue is a check box to enable or disable NTP server.
(2017-08-16, 01:39)kevinmcc Wrote: [ -> ]Yes, just map the port to System Blue IP address.
Not sure what the server software is.
Only setting on System Blue is a check box to enable or disable NTP server.
It uses the GPS time together with the local 1 PPS timing pulse.
enable the NTP server,
for example, in Windows, go to cliock settings,
set by internet,, and paste the controller LAN url into
the server select box, as in attached....
(remember the default lan is...235 not 217)
Now, the clock did set, when I tried connecting from WAN
but indicated that it 'didn't' because it timed out....
This is another 'add on' that can slow the controller down, by the way.
(2017-08-15, 07:42)flytux Wrote: [ -> ] (2017-08-14, 23:28)kevinmcc Wrote: [ -> ]Синяя система имеет встроенный сервер NTP-stratum-1.
Thank you for information. I would like to ask you to clarify two things.
First, is this correct that all of outher (WAN) users can sync a time by SystemsBlue NTP server (if port #123/udp is forwarded by router)?
And second - what kind of software provide SystemBlue's NTP-service? Is this BSD-like 'ntpd' or self-made implementation?
Regards,
It is convenient to use gps based clock only if you have time-sensitive application and it is "network far" from core ntp services. I'm happy with MSK-IX clock, it is "close":
onthehill:$ ping ntp.msk-ix.ru
PING ntp.msk-ix.ru (194.190.168.1): 56 data bytes
64 bytes from 194.190.168.1: icmp_seq=0 ttl=60 time=8.850 ms
64 bytes from 194.190.168.1: icmp_seq=1 ttl=60 time=4.610 ms
64 bytes from 194.190.168.1: icmp_seq=2 ttl=60 time=4.328 ms