Menu
▾
▴
linuxptp-users
|
From: jawad a. s. <jaw...@ho...> - 2020-01-15 15:06:36
|
Hi, Is there a documentation which explains what all these different PMC GET commands return? For example, what does the data returned in GET PARENT_DATA_SET mean? There is gm.ClockClass field in returned data which is not the same as clockClass field returned in GET GRANDMASTER_SETTINGS_NP. Can you please explain what is the difference? Thanks. Regards, Jawad |
|
From: Richard C. <ric...@gm...> - 2020-01-15 18:25:48
|
On Wed, Jan 15, 2020 at 03:06:24PM +0000, jawad ahmed saleemi wrote: > Is there a documentation which explains what all these different PMC GET commands return? With the exception of the custom NP TLVs, these are standard management messages documented in IEEE 1588. > For example, what does the data returned in GET PARENT_DATA_SET > mean? There is gm.ClockClass field in returned data which is not the > same as clockClass field returned in GET > GRANDMASTER_SETTINGS_NP. Can you please explain what is the > difference? The GRANDMASTER_SETTINGS_NP are the values used if the local clock becomes the GM. Below are my notes about the various TLVs. HTH, Richard * CURRENT_DATA_SET stepsRemoved 0 offsetFromMaster 0.0 meanPathDelay 0.0 * PARENT_DATA_SET # find out the GM identity parentPortIdentity e89a8f.fffe.74f796-0 parentStats 0 observedParentOffsetScaledLogVariance 0xffff observedParentClockPhaseChangeRate 0x7fffffff grandmasterPriority1 128 gm.ClockClass 248 gm.ClockAccuracy 0xfe gm.OffsetScaledLogVariance 0xffff grandmasterPriority2 128 grandmasterIdentity e89a8f.fffe.74f796 * TIME_PROPERTIES_DATA_SET # find out whether time is globally traceable currentUtcOffset 35 leap61 0 leap59 0 currentUtcOffsetValid 0 ptpTimescale 0 timeTraceable 0 frequencyTraceable 0 timeSource 0xa0 * PORT_DATA_SET # knowing the portState can be useful, SLAVE and MASTER portIdentity e89a8f.fffe.74f796-1 portState FAULTY logMinDelayReqInterval 0 peerMeanPathDelay 0 logAnnounceInterval 1 announceReceiptTimeout 3 logSyncInterval 0 delayMechanism 1 logMinPdelayReqInterval 0 versionNumber 2 * GRANDMASTER_SETTINGS_NP # values used when nodes becomes the GM # SET action useful for GPS time server clockClass 248 clockAccuracy 0xfe offsetScaledLogVariance 0xffff currentUtcOffset 35 leap61 0 leap59 0 currentUtcOffsetValid 0 ptpTimescale 0 timeTraceable 0 frequencyTraceable 0 timeSource 0xa0 * DEFAULT_DATA_SET # discover the numberPorts twoStepFlag 1 slaveOnly 0 numberPorts 1 priority1 128 clockClass 248 clockAccuracy 0xfe offsetScaledLogVariance 0xffff priority2 128 clockIdentity e89a8f.fffe.74f796 domainNumber 0 * AVB... * TIME_STATUS_NP # designed for use with gPTP and free_running master_offset 0 ingress_time 0 cumulativeScaledRateOffset +0.000000000 scaledLastGmPhaseChange 0 gmTimeBaseIndicator 0 lastGmPhaseChange 0x0000'0000000000000000.0000 gmPresent false gmIdentity e89a8f.fffe.74f796 * PORT_DATA_SET_NP # gPTP: SET neighborPropDelayThresh and GET asCapable neighborPropDelayThresh 20000000 asCapable 0 |
|
From: jawad a. s. <jaw...@ho...> - 2020-01-16 12:17:09
|
Thanks Richard. So, PARENT_DATA_SET has all the information about grand master? Regards, Jawad ________________________________ From: Richard Cochran <ric...@gm...> Sent: Wednesday, January 15, 2020 11:25 PM To: jawad ahmed saleemi <jaw...@ho...> Cc: lin...@li... <lin...@li...> Subject: Re: [Linuxptp-users] PMC GET commands On Wed, Jan 15, 2020 at 03:06:24PM +0000, jawad ahmed saleemi wrote: > Is there a documentation which explains what all these different PMC GET commands return? With the exception of the custom NP TLVs, these are standard management messages documented in IEEE 1588. > For example, what does the data returned in GET PARENT_DATA_SET > mean? There is gm.ClockClass field in returned data which is not the > same as clockClass field returned in GET > GRANDMASTER_SETTINGS_NP. Can you please explain what is the > difference? The GRANDMASTER_SETTINGS_NP are the values used if the local clock becomes the GM. Below are my notes about the various TLVs. HTH, Richard * CURRENT_DATA_SET stepsRemoved 0 offsetFromMaster 0.0 meanPathDelay 0.0 * PARENT_DATA_SET # find out the GM identity parentPortIdentity e89a8f.fffe.74f796-0 parentStats 0 observedParentOffsetScaledLogVariance 0xffff observedParentClockPhaseChangeRate 0x7fffffff grandmasterPriority1 128 gm.ClockClass 248 gm.ClockAccuracy 0xfe gm.OffsetScaledLogVariance 0xffff grandmasterPriority2 128 grandmasterIdentity e89a8f.fffe.74f796 * TIME_PROPERTIES_DATA_SET # find out whether time is globally traceable currentUtcOffset 35 leap61 0 leap59 0 currentUtcOffsetValid 0 ptpTimescale 0 timeTraceable 0 frequencyTraceable 0 timeSource 0xa0 * PORT_DATA_SET # knowing the portState can be useful, SLAVE and MASTER portIdentity e89a8f.fffe.74f796-1 portState FAULTY logMinDelayReqInterval 0 peerMeanPathDelay 0 logAnnounceInterval 1 announceReceiptTimeout 3 logSyncInterval 0 delayMechanism 1 logMinPdelayReqInterval 0 versionNumber 2 * GRANDMASTER_SETTINGS_NP # values used when nodes becomes the GM # SET action useful for GPS time server clockClass 248 clockAccuracy 0xfe offsetScaledLogVariance 0xffff currentUtcOffset 35 leap61 0 leap59 0 currentUtcOffsetValid 0 ptpTimescale 0 timeTraceable 0 frequencyTraceable 0 timeSource 0xa0 * DEFAULT_DATA_SET # discover the numberPorts twoStepFlag 1 slaveOnly 0 numberPorts 1 priority1 128 clockClass 248 clockAccuracy 0xfe offsetScaledLogVariance 0xffff priority2 128 clockIdentity e89a8f.fffe.74f796 domainNumber 0 * AVB... * TIME_STATUS_NP # designed for use with gPTP and free_running master_offset 0 ingress_time 0 cumulativeScaledRateOffset +0.000000000 scaledLastGmPhaseChange 0 gmTimeBaseIndicator 0 lastGmPhaseChange 0x0000'0000000000000000.0000 gmPresent false gmIdentity e89a8f.fffe.74f796 * PORT_DATA_SET_NP # gPTP: SET neighborPropDelayThresh and GET asCapable neighborPropDelayThresh 20000000 asCapable 0 |
|
From: Richard C. <ric...@gm...> - 2020-01-16 17:15:32
|
On Thu, Jan 16, 2020 at 12:16:56PM +0000, jawad ahmed saleemi wrote: > So, PARENT_DATA_SET has all the information about grand master? Yes, about the currently selected GM. Cheers, Richard |
|
From: jawad a. s. <jaw...@ho...> - 2020-01-21 19:49:58
|
Thanks Richard. Is it possible to get the information on Grand Master's timesource using one of the pmc management commands? Regards, Jawad ________________________________ From: Richard Cochran <ric...@gm...> Sent: Thursday, January 16, 2020 10:15 PM To: jawad ahmed saleemi <jaw...@ho...> Cc: lin...@li... <lin...@li...> Subject: Re: [Linuxptp-users] PMC GET commands On Thu, Jan 16, 2020 at 12:16:56PM +0000, jawad ahmed saleemi wrote: > So, PARENT_DATA_SET has all the information about grand master? Yes, about the currently selected GM. Cheers, Richard |
|
From: Richard C. <ric...@gm...> - 2020-01-22 04:14:14
|
On Tue, Jan 21, 2020 at 07:49:45PM +0000, jawad ahmed saleemi wrote: > Is it possible to get the information on Grand Master's timesource using one of the pmc management commands? Yes, by checking the TIME_PROPERTIES_DATA_SET.timeSource attribute. HTH, Richard |
|
From: jawad a. s. <jaw...@ho...> - 2020-01-24 12:08:12
|
Thanks Richard. I have another question if it is ok 🙂 In my config file, I have "slaveOnly" set to 1 but linuxptp still selects the local clock as best master in case it does not find any grandmaster. Any idea what could I be missing? Regards, Jawad ________________________________ From: Richard Cochran <ric...@gm...> Sent: Wednesday, January 22, 2020 9:13 AM To: jawad ahmed saleemi <jaw...@ho...> Cc: lin...@li... <lin...@li...> Subject: Re: [Linuxptp-users] PMC GET commands On Tue, Jan 21, 2020 at 07:49:45PM +0000, jawad ahmed saleemi wrote: > Is it possible to get the information on Grand Master's timesource using one of the pmc management commands? Yes, by checking the TIME_PROPERTIES_DATA_SET.timeSource attribute. HTH, Richard |
|
From: Richard C. <ric...@gm...> - 2020-01-24 18:01:53
|
On Fri, Jan 24, 2020 at 12:07:58PM +0000, jawad ahmed saleemi wrote: > In my config file, I have "slaveOnly" set to 1 but linuxptp still > selects the local clock as best master in case it does not find any > grandmaster. Any idea what could I be missing? That is the expected slaveOnly behavior when no master is present. Thanks, Richard |
|
From: jawad a. s. <jaw...@ho...> - 2020-01-24 18:08:23
|
Is it possible for slave to not select itself as mastee in case no master ia present? Get Outlook for Android<https://aka.ms/ghei36> ________________________________ From: Richard Cochran <ric...@gm...> Sent: Friday, January 24, 2020 7:01:42 PM To: jawad ahmed saleemi <jaw...@ho...> Cc: lin...@li... <lin...@li...> Subject: Re: [Linuxptp-users] PMC GET commands On Fri, Jan 24, 2020 at 12:07:58PM +0000, jawad ahmed saleemi wrote: > In my config file, I have "slaveOnly" set to 1 but linuxptp still > selects the local clock as best master in case it does not find any > grandmaster. Any idea what could I be missing? That is the expected slaveOnly behavior when no master is present. Thanks, Richard |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X