Open tofe-INA opened 4 months ago
@tofe-INA Thank for the feedback. Currently, we dint got a way to configure the transportSpecific/majorSdoID field, but we will explore on it. Before we go deeper, we would like to understand what is your preferred way of configuring the field? How about passing in the value via one of the Clock Manager API call?
@tofe-INA some latest update on this issue: currently we are in the direction of adding transportSpecific as input argument for jclklib_proxy. When running Proxy, user can chose to set their desired transportSpecific. Let us know if you have any input on this design.
Hello,
I tried to use the Clock Manager within a gPTP environment. According to the log of the proxy it connects to the ptp4l uds, but no events are received on the client. The major difference between a Default PTP and gPTP instance is that transportSpecific / majorSdoId is 0x1. Therefore messages from the proxy are not answered by ptp4l.
In the "default" libptpmgmt it is possible to parameterize the PTP instance for different PTP Profiles via "MsgParams" (transportSpecific, domain number, boundary hops, etc.) , as shown in the default check_sync.cpp from libptpmgmt.
If I start ptp4l with default 1588 parameters and start the proxy, the client receives some events and it seems to work.
Question: Is there currently a convenient way to configure the transportSpecific/majorSdoID field for the messages between the proxy and the uds of ptp4l to be able to use the Clock Manager with gPTP?
Thanks in advance.
Best regards, Tobias