Why is the offset still so huge here? The timestamp which is printed on the left matches the current time.
And why is the 'state' alternating between "PTP_SLAVE" and "PTP_LISTENING" all the time?
The clock is correctly adjusted from 2020-01-01 00:02:37 to 2019-09-18 12:59:29 but there is still shown "Offset above 1 second (9025384.784915000 s)".
Why is the offset still so huge? 9025384 seconds are around 104 days (however, the date 2019-09-18 is show correctly).
Any ideas?
Thanks,
Thomas
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It seems to be a problem with a wrong interrupt vector number in the function getTime().
Does someone know, why the getTime() function is based on an interrupt for QNX Neutrino systems and interrupt-les for all other systems?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello,
The time master was a Linux system with PTP4L started as:
ptp4l -i eth0.1234 -S -E -2 -m -q
The ptpd client was started as:
ptpd2 -i vlan1234 -s -E -C -L --ptpengine:transport="ethernet" --ptpengine:use_libpcap="Y"
The output I get from ptpd client is the following:
Hint: The client system was set to 2020-01-01 00:00:00 before starting PTP.
Now the clock syncs to the time master and jumps to the current time which was received via PTP:
Why is the offset still so huge here? The timestamp which is printed on the left matches the current time.
And why is the 'state' alternating between "PTP_SLAVE" and "PTP_LISTENING" all the time?
Thanks,
Thomas
Last edit: Thomas F. 2019-09-16
The same behavior occurs also when only using ptpd (as master and slave).
MASTER:
SLAVE:
The clock is correctly adjusted from 2020-01-01 00:02:37 to 2019-09-18 12:59:29 but there is still shown "Offset above 1 second (9025384.784915000 s)".
Why is the offset still so huge? 9025384 seconds are around 104 days (however, the date 2019-09-18 is show correctly).
Any ideas?
Thanks,
Thomas
It seems to be a problem with a wrong interrupt vector number in the function getTime().
Does someone know, why the getTime() function is based on an interrupt for QNX Neutrino systems and interrupt-les for all other systems?