Re: [Linuxptp-users] How do I use "slave_event_monitor" to get the management info(such as offset, delay, master time) which should from PMC.

Mon, 20 Jun 2022 20:17:51 -0700 

Thanks a lot, I have got it and I will try it. 
The parameter ??duration?? represent the subscribe client 
whether in the validity period? 
If duration time is expired ptpt4l will remove it and the client need to 
re-subscribe it? 
Another question: Is there any conditions for using "slave_monitor_event"? 
eg. delay_mechanism must be E2E or P2P or both are OK.
montior_delay() is only called in case DELAY_RESP(process_delay_resp()) while 
not in case PDELAY_RESP.


switch (msg_type(msg)) { case SYNC:     process_sync(p, msg);   break; case 
DELAY_REQ:  if (process_delay_req(p, msg))          event = EV_FAULT_DETECTED;  
    break; case PDELAY_REQ:         if (process_pdelay_req(p, msg))             
    event = EV_FAULT_DETECTED;      break; case PDELAY_RESP:        if 
(process_pdelay_resp(p, msg))                event = EV_FAULT_DETECTED;      
break; case FOLLOW_UP:  process_follow_up(p, msg);      break; case DELAY_RESP: 
        process_delay_resp(p, msg);     break; 








------------------ Original ------------------
From: &nbsp;"Richard Cochran";<richardcoch...@gmail.com&gt;;
Send time:&nbsp;Tuesday, Jun 21, 2022 2:49 AM
To:&nbsp;"?????9?2 ??????"<957993...@qq.com&gt;; 
Cc:&nbsp;"linuxptp-users"<linuxptp-users@lists.sourceforge.net&gt;; 
Subject: &nbsp;Re: [Linuxptp-users] How do I use "slave_event_monitor" to get 
the management info(such as offset, delay, master time) which should from PMC.



On Mon, Jun 20, 2022 at 10:32:55PM +0800, ?????9?2 ?????? wrote:
&gt; Thanks very much.
&gt; I also want to know&amp;nbsp;how can I subscribe to receive PORT_DATA_SET 
and TIME_STATUS_NP via the push method? 
&gt; Could you help me some example and guidance? Thanks a lot.

pmc is your friend...

root@ctm:~# pmc -b0 -u
&nbsp;&nbsp;&nbsp; 
help

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [action] USER_DESCRIPTION
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [action] DEFAULT_DATA_SET
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [action] CURRENT_DATA_SET
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [action] PARENT_DATA_SET
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [action] TIME_PROPERTIES_DATA_SET
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [action] PRIORITY1
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [action] PRIORITY2
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [action] DOMAIN
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [action] SLAVE_ONLY
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [action] CLOCK_ACCURACY
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [action] TRACEABILITY_PROPERTIES
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [action] TIMESCALE_PROPERTIES
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [action] TIME_STATUS_NP
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [action] GRANDMASTER_SETTINGS_NP
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [action] SUBSCRIBE_EVENTS_NP
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [action] SYNCHRONIZATION_UNCERTAIN_NP
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [action] NULL_MANAGEMENT
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [action] CLOCK_DESCRIPTION
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [action] PORT_DATA_SET
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [action] LOG_ANNOUNCE_INTERVAL
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [action] ANNOUNCE_RECEIPT_TIMEOUT
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [action] LOG_SYNC_INTERVAL
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [action] VERSION_NUMBER
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [action] DELAY_MECHANISM
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [action] LOG_MIN_PDELAY_REQ_INTERVAL
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [action] PORT_DATA_SET_NP
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [action] PORT_STATS_NP
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [action] PORT_PROPERTIES_NP

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The [action] can be GET, SET, CMD, 
or COMMAND
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Commands are case insensitive and 
may be abbreviated.

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; TARGET [portIdentity]
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; TARGET *

get SUBSCRIBE_EVENTS_NP
sending: GET SUBSCRIBE_EVENTS_NP
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; a0369f.fffe.10cfaf-0 seq 0 RESPONSE 
MANAGEMENT SUBSCRIBE_EVENTS_NP 
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
 duration&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
 NOTIFY_PORT_STATE off
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
 NOTIFY_TIME_SYNC&nbsp; off

set SUBSCRIBE_EVENTS_NP duration 60 NOTIFY_PORT_STATE on NOTIFY_TIME_SYNC on
sending: SET SUBSCRIBE_EVENTS_NP
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; a0369f.fffe.10cfaf-0 seq 1 RESPONSE 
MANAGEMENT SUBSCRIBE_EVENTS_NP 
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
 duration&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 60
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
 NOTIFY_PORT_STATE on
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
 NOTIFY_TIME_SYNC&nbsp; on

get SUBSCRIBE_EVENTS_NP
sending: GET SUBSCRIBE_EVENTS_NP
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; a0369f.fffe.10cfaf-0 seq 2 RESPONSE 
MANAGEMENT SUBSCRIBE_EVENTS_NP 
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
 duration&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 26
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
 NOTIFY_PORT_STATE on
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
 NOTIFY_TIME_SYNC&nbsp; on
_______________________________________________
Linuxptp-users mailing list
Linuxptp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxptp-users






















					Reply via email to