Knowledge Base / Why Windows enforces strict PTP profiles

Why Windows enforces strict PTP profiles

Check Windows PTP client compatibility against GMR6000 profiles, including profile-dependent one-step and two-step synchronization.

Applies to: GMR, PCIe
Back to search

Check client compatibility

A Windows PTP client and its time source need compatible PTP settings. Confirm the requirements for the Windows version and PTP client implementation in use before changing the grandmaster configuration.

GMR6000 profiles

The GMR6000 Rev D datasheet lists the following preconfigured profiles for its optional PTP feature:

GMR6000 preconfigured profiles, Rev D, page 3
ApplicationListed profiles
DefaultDefault E2E IEEE 1588-2008; Default P2P IEEE 1588-2008
Media and audio/videoSMPTE ST 2059-2; AES67; SMPTE 2110 with ST 2059-2/AES67 interoperability
PowerIEEE C37.238-2011; IEEE C37.238-2017
TelecomG.8275.1

IEC 61850-9-3 is also listed in the network-feature section on page 2. It is not separately listed in the preconfigured-profile table on page 3. The datasheet also describes manual adjustment for other profiles.

Use the profile required by the Windows PTP client implementation. The datasheet is a GMR6000 capability reference; it does not specify a single Windows profile, domain number, or flag configuration.

One-step and two-step synchronization

One-step: the precise Sync transmit time is supplied in the Sync message as it is transmitted. Two-step: a subsequent Follow_Up message supplies the precise transmit timestamp for the corresponding Sync message.

One-step or two-step operation is user-selectable where the selected PTP profile permits it. Some profiles restrict the permitted behavior, so both modes are not available under every profile. Check the selected profile and the receiving client’s requirements before changing this setting.

This setting describes how Sync timing information is delivered. It is separate from the E2E/P2P delay mechanism and does not by itself guarantee a particular synchronization accuracy.

Information needed for a compatibility check

Related configuration checks

See Windows PTP requires specific flags and domains for the domain and flag checklist. For a consistent UTC offset, see PTP time appears 37 seconds offset from UTC. Exact Windows profile requirements must be confirmed against the documentation for the client in use.

Article ID: KB-PTP-002
KB Version: