M88 Evaluation Kit User Guide
Using the PTP engine
STO-DEV7227-HB Rev. 2.1
24
*** PTPv2 up and running ***
6. Set Port 1 to Unicast Slave
A:/root> ptp2 port 1 unicast slave
A:/root> Unicast port state: PTP2_STATE_SLAVE
7. Add the Qg 2 to the list of accepted masters
A:/root> ptp2 unicast 1 node add 192.168.2.100 0 0 0
A:/root> *** Unicast node dataset ***
{
Clock identity: FF:FF:FF:FF:FF:FF:FF:FF
Network protocol: UDP/IPv4
Network address: 192.168.2.100
Node type: MASTER
Announce granted: FALSE
Announce interval: 1
Announce duration: 300
Sync granted: FALSE
Sync interval: 0
Sync duration: 0
Delay response granted: FALSE
Delay response interval: 0
Delay response duration: 0
Local priority: 0
}
8. Wait for the following message to appear
A new master time is received or the network topology was changed.
Update local clock with new offset: sec: -0 nsec: 866271987
Please refer to [1] for commands on how to further control and monitor the PTP communication.
14
Using the PTP engine
Detailed information about how to interact with the PTP engine can be found in [1] which can be
downloaded from our web site.
Any commands that the M88 should execute at startup, such as setting message rates etc. can be stored
in the startup.ini file under the systems folder.
Using the serial port, the startup.ini file can be transferred to your PC using the
kermit
–
s <filename>
command, edited on your PC and then downloaded to the M88 again using
kermit
–
r
. If the terminal
program in Developer is used, the commands
send
and
recv
can be used to transfer files instead of
Kermit. Type
help send
respectively
help recv
for more information. Alternatively, FTP can be used
over the network to upload the startup.ini file, edit the contents of the file, and then download to the
systems folder.
