I cannot verify that my cDAQ-9189 is synchronized with a 3rd party grandmaster, in this case a TimeMachine TM2000B GPS Time Server that is configured to use 802.1AS. The two devices are plugged directly into each other via ethernet with no switch in between.
Using the shipping example "Configure and Monitor 802.1AS.vi", the 9189 only ever reports a Grandmaster Clock ID that is its own MAC address. The board time is also incorrect and reports a date of 1969.
I have configured the TM2000B to have a priority of 1, so it should win the election process.
The TM2000B does include configuration options (Peer to Peer vs End to End, Unicast vs Multicast, Log Sync Interval, etc), but I cannot find the NI implementation published anywhere to match it. However, I'm pretty sure 802.1AS must be Peer to Peer and Multicast. Some of the settings, such as Log Sync Interval do appear as properties in the niSync API, but they throw an error of "The requested property is not supported by the time reference specified on the Active Item."
There is a "Transport Specific Field" 0-255 numeric option in the TM2000B configuration page that says it must match the client's configuration. Is anyone aware of what this option should be for a cDAQ-9189?
This exercise is not limited to the TM2000B and might be helpful in general for others attempting to use a 3rd party Time Server. The options to define 802.1AS can be found here: TM2000BManual.pdf (timemachinescorp.com)
