All it takes is to look at the man page and IEC standards documents.
The Power Profile uses the Ethernet transport as defined in IEEE 1588 with P2P delay measurement. In essence, yes, PTPd can support this transport, but it does not specifically support the Power Profile, just the generic 1588 properties that are the same for 1588 and power profile. It is missing support for the IEC PTP MIB, support for the power profile Grandmaster ID TLV and alternate timescales / local time TLVs. The easiest way is to test it with a Power Profile compliant device. PTPd is also missing support for hardware timestamping for the Ethernet transport, but that should be possible in future. Explicit Power Profile support is not a priority for PTPd right now, but full support may be possible in future.
Thanks,
Wojciech
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
My question is in subject.
Mirek
All it takes is to look at the man page and IEC standards documents.
The Power Profile uses the Ethernet transport as defined in IEEE 1588 with P2P delay measurement. In essence, yes, PTPd can support this transport, but it does not specifically support the Power Profile, just the generic 1588 properties that are the same for 1588 and power profile. It is missing support for the IEC PTP MIB, support for the power profile Grandmaster ID TLV and alternate timescales / local time TLVs. The easiest way is to test it with a Power Profile compliant device. PTPd is also missing support for hardware timestamping for the Ethernet transport, but that should be possible in future. Explicit Power Profile support is not a priority for PTPd right now, but full support may be possible in future.
Thanks,
Wojciech
Thanks
Mirek