Hey agai,

I also tried using linux services instead, which has a more detailed 
configuration file but stills the date is the wrong one:

edge2@dai-edge2:~$ systemctl status ptp4l.service 
● ptp4l.service - Precision Time Protocol (PTP) service
     Loaded: loaded (/lib/systemd/system/ptp4l.service; disabled; vendor 
preset: enabled)
     Active: active (running) since Mon 2018-01-29 21:13:04 UTC; 9s ago
       Docs: man:ptp4l
   Main PID: 97589 (ptp4l)
      Tasks: 1 (limit: 38293)
     Memory: 472.0K
     CGroup: /system.slice/ptp4l.service
             └─97589 /usr/sbin/ptp4l -f /etc/linuxptp/ptp4l.conf -i enp2s0

Jan 29 21:13:04 dai-edge2 ptp4l[97589]: [107547.002] port 1: INITIALIZING to 
LISTENING on INIT_COMPLETE
Jan 29 21:13:04 dai-edge2 ptp4l[97589]: [107547.002] port 0: INITIALIZING to 
LISTENING on INIT_COMPLETE
Jan 29 21:13:05 dai-edge2 ptp4l[97589]: [107548.047] port 1: new foreign master 
04e548.fffe.230104-1
Jan 29 21:13:09 dai-edge2 ptp4l[97589]: [107552.048] selected best master clock 
04e548.fffe.230104
Jan 29 21:13:09 dai-edge2 ptp4l[97589]: [107552.048] running in a temporal 
vortex
Jan 29 21:13:09 dai-edge2 ptp4l[97589]: [107552.048] port 1: LISTENING to 
UNCALIBRATED on RS_SLAVE
Jan 29 21:13:11 dai-edge2 ptp4l[97589]: [107554.048] master offset      -1208 
s0 freq  +21717 path delay       225
Jan 29 21:13:12 dai-edge2 ptp4l[97589]: [107555.048] master offset      -1263 
s2 freq  +21662 path delay       233
Jan 29 21:13:12 dai-edge2 ptp4l[97589]: [107555.048] port 1: UNCALIBRATED to 
SLAVE on MASTER_CLOCK_SELECTED
Jan 29 21:13:13 dai-edge2 ptp4l[97589]: [107556.048] master offset      -1247 
s2 freq  +20415 path delay       233
edge2@dai-edge2:~$ systemctl status phc2sys.service 
● phc2sys.service - Synchronize system clock or PTP hardware clock (PHC)
     Loaded: loaded (/lib/systemd/system/phc2sys.service; disabled; vendor 
preset: enabled)
     Active: active (running) since Mon 2018-01-29 21:13:10 UTC; 11s ago
       Docs: man:phc2sys
   Main PID: 97611 (phc2sys)
      Tasks: 1 (limit: 38293)
     Memory: 352.0K
     CGroup: /system.slice/phc2sys.service
             └─97611 /usr/sbin/phc2sys -w -s enp2s0

Jan 29 21:13:12 dai-edge2 phc2sys[97611]: [107555.845] Waiting for ptp4l...
Jan 29 21:13:13 dai-edge2 phc2sys[97611]: [107556.846] CLOCK_REALTIME phc 
offset      6353 s0 freq  +29047 delay   5570
Jan 29 21:13:14 dai-edge2 phc2sys[97611]: [107557.847] CLOCK_REALTIME phc 
offset      5973 s2 freq  +28667 delay   5601
Jan 29 21:13:15 dai-edge2 phc2sys[97611]: [107558.847] CLOCK_REALTIME phc 
offset      6381 s2 freq  +35048 delay   5604
Jan 29 21:13:16 dai-edge2 phc2sys[97611]: [107559.847] CLOCK_REALTIME phc 
offset       483 s2 freq  +31064 delay   5556
Jan 29 21:13:17 dai-edge2 phc2sys[97611]: [107560.848] CLOCK_REALTIME phc 
offset     -1381 s2 freq  +29345 delay   5571
Jan 29 21:13:18 dai-edge2 phc2sys[97611]: [107561.848] CLOCK_REALTIME phc 
offset     -1559 s2 freq  +28753 delay   5560
Jan 29 21:13:19 dai-edge2 phc2sys[97611]: [107562.849] CLOCK_REALTIME phc 
offset     -1136 s2 freq  +28708 delay   5561
Jan 29 21:13:20 dai-edge2 phc2sys[97611]: [107563.849] CLOCK_REALTIME phc 
offset      -659 s2 freq  +28845 delay   5609
Jan 29 21:13:21 dai-edge2 phc2sys[97611]: [107564.850] CLOCK_REALTIME phc 
offset      -361 s2 freq  +28945 delay   5578
edge2@dai-edge2:~$ timedatectl
               Local time: Mon 2018-01-29 21:14:54 UTC
           Universal time: Mon 2018-01-29 21:14:54 UTC
                 RTC time: Mon 2018-01-29 21:14:54    
                Time zone: Etc/UTC (UTC, +0000)       
System clock synchronized: yes                        
              NTP service: inactive       

Best regards,
Federico Murciano

M.Sc. Elektrotechnik - Telecommunications Engineer
federico.murci...@dai-labor.de
Tel. +49 (0) 30/314 -74 025 / Mob. +49 157 8642 4850
Future Communication Networks
DAI-Labor
Technische Universität Berlin
Fakultät IV – Elektrotechnik & Informatik Sekretariat TEL 14 Ernst-Reuter-Platz 
7
10587 Berlin, Germany
http://www.dai-labor.de/
DAI-Labor - Distributed Artificial Intelligence Laboratory Chief Executive 
Director: Prof. Dr. Dr. h.c. Sahin Albayrak

________________________________________
Von: Federico Murciano <federico.murci...@dai-labor.de>
Gesendet: Mittwoch, 23. März 2022 17:53
An: linuxptp-users@lists.sourceforge.net
Cc: Sebastian Peters
Betreff: [Linuxptp-users] phc2sys not synchr. to right time and date

Hello everyone,


I am trying to sync different Ubuntu computers to the ptp master clock from 
another device connected to each of them.

The setup is very easy:


Ubuntu Laptop as Slave <-> Ubuntu device with GPS signal as Master


The problem is that for one system, everything is working right, but for other 
system with the same setup, when the date is updated it is set to a day in 
2018, which is obviously not the case. I also had some offset issues that I 
believe are solved already by using phc2sys with the -O 0 option (0seconds 
offset).


Here are the steps that I follow:


Master

ptp.cfg file:


[global]

tx_timestamp_timeout 10

step_threshold 1


user@MK6C:~$ timedatectl

                      Local time: Wed 2022-03-23 16:38:27 UTC

                  Universal time: Wed 2022-03-23 16:38:27 UTC

                        RTC time: Wed 2022-03-23 16:38:28

                       Time zone: Etc/UTC (UTC, +0000)

       System clock synchronized: yes

systemd-timesyncd.service active: no

                 RTC in local TZ: no​


sudo ptp4l -A -i eth0 -m -f ptp.cfg


ptp4l[101681.741]: selected /dev/ptp0 as PTP clock

ptp4l[101681.742]: driver changed our HWTSTAMP options

ptp4l[101681.742]: tx_type   1 not 1

ptp4l[101681.742]: rx_filter 1 not 12

ptp4l[101681.742]: port 1: INITIALIZING to LISTENING on INITIALIZE

ptp4l[101681.743]: port 0: INITIALIZING to LISTENING on INITIALIZE

ptp4l[101681.743]: port 1: link up

ptp4l[101689.067]: port 1: LISTENING to MASTER on 
ANNOUNCE_RECEIPT_TIMEOUT_EXPIRES

ptp4l[101689.067]: selected best master clock 04e548.fffe.230104

ptp4l[101689.067]: assuming the grand master role


Slave-1


​​linuxptp.cfg file:


[global]

clientOnly 1

delay_mechanism        Auto

network_transport    UDPv4

#time_stamping        hardware        # for the HW-timestamping slave

#time_stamping        software         # for the SW-timestamping slave

step_threshold        1.0

utc_offset 37

# make sure our slave clock is never elected as master

priority1        255

priority2        255


[enp0s31f6]



sudo ptp4l -s -f linuxptp.cfg -m


ptp4l[105105.227]: selected /dev/ptp0 as PTP clock

ptp4l[105105.228]: port 1: INITIALIZING to LISTENING on INIT_COMPLETE

ptp4l[105105.228]: port 0: INITIALIZING to LISTENING on INIT_COMPLETE

ptp4l[105105.894]: port 1: new foreign master 04e548.fffe.230104-1

ptp4l[105109.894]: selected best master clock 04e548.fffe.230104

ptp4l[105109.894]: running in a temporal vortex

ptp4l[105109.895]: port 1: LISTENING to UNCALIBRATED on RS_SLAVE

ptp4l[105111.895]: master offset     -18633 s0 freq  +24199 path delay       267

ptp4l[105112.895]: master offset     -18834 s2 freq  +23998 path delay       267

ptp4l[105112.895]: port 1: UNCALIBRATED to SLAVE on MASTER_CLOCK_SELECTED

ptp4l[105113.895]: master offset     -18827 s2 freq   +5171 path delay       267

ptp4l[105114.895]: master offset        -22 s2 freq  +18328 path delay       262

ptp4l[105115.895]: master offset       5676 s2 freq  +24019 path delay       262

ptp4l[105116.895]: master offset       5669 s2 freq  +25715 path delay       257

ptp4l[105117.895]: master offset       3948 s2 freq  +25695 path delay       262

ptp4l[105118.895]: master offset       2246 s2 freq  +25177 path delay       267

ptp4l[105119.895]: master offset       1066 s2 freq  +24671 path delay       267

ptp4l[105120.895]: master offset        363 s2 freq  +24288 path delay       288

ptp4l[105121.895]: master offset         79 s2 freq  +24113 path delay       273

ptp4l[105122.895]: master offset        -36 s2 freq  +24021 path delay       273

ptp4l[105123.895]: master offset        -63 s2 freq  +23984 path delay       268


edge2@dai-edge2:~$ timedatectl

               Local time: Mon 2018-01-29 20:52:35 UTC

           Universal time: Mon 2018-01-29 20:52:35 UTC

                 RTC time: Mon 2018-01-29 20:52:35

                Time zone: Etc/UTC (UTC, +0000)

System clock synchronized: yes

              NTP service: inactive

          RTC in local TZ: no



sudo phc2sys -s enp0s31f6 -O 0 -m


edge2@dai-edge2:~$ sudo phc2sys -s enp2s0 -O -36 -m

phc2sys[105266.195]: CLOCK_REALTIME phc offset       -72 s0 freq  +31297 delay  
 5547

phc2sys[105267.196]: CLOCK_REALTIME phc offset      -131 s2 freq  +31238 delay  
 5503

phc2sys[105268.196]: CLOCK_REALTIME phc offset       -70 s2 freq  +31168 delay  
 5574

phc2sys[105269.197]: CLOCK_REALTIME phc offset        17 s2 freq  +31234 delay  
 5481

phc2sys[105270.197]: CLOCK_REALTIME phc offset       102 s2 freq  +31324 delay  
 5588

phc2sys[105271.197]: CLOCK_REALTIME phc offset        60 s2 freq  +31313 delay  
 5590

phc2sys[105272.198]: CLOCK_REALTIME phc offset        58 s2 freq  +31329 delay  
 5559

phc2sys[105273.198]: CLOCK_REALTIME phc offset        22 s2 freq  +31310 delay  
 5569

^Cphc2sys[105274.179]: CLOCK_REALTIME phc offset       -66 s2 freq  +31229 
delay   5546


edge2@dai-edge2:~$ timedatectl

               Local time: Mon 2018-01-29 20:53:33 UTC

           Universal time: Mon 2018-01-29 20:53:33 UTC

                 RTC time: Mon 2018-01-29 20:53:33

                Time zone: Etc/UTC (UTC, +0000)

System clock synchronized: yes

              NTP service: inactive

          RTC in local TZ: no



This is working correctly in one setup but in other two I get this weird 2018 
date set.


Am I missing something? Any help would be very appreciated. Thanks in advance!

Best regards,
Federico Murciano​

_______________________________________________
Linuxptp-users mailing list
Linuxptp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxptp-users

_______________________________________________
Linuxptp-users mailing list
Linuxptp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxptp-users

Reply via email to