DanielaSpreafico
commented
1 year ago I cheched the involved attributes and clarified the correct behaviour:
leaf duplex-distance { type int32; units "kHz"; description "Distance between transmitter and receiver frequencies.
leaf actual-duplex-distance { type uint32; units "kHz"; config false; description "Computed distance between Tx and Rx frequencies."
The 'duplex-distance' is used to define the 'rx-frequency' starting from 'tx-frequency' and could contains both negative (to have rx<tx) or positive values (to have rx>tx). The 'actual-duplex-distance' report the distance between tx-frequency and rx-frequency (already known and reported) so only positive values (unsigned) are reported.
This issue could be closed.
Email from Daniela,
I have a question (raised by our Sw development team) as a my understand confirmation:
The question from our Sw development team) • (If we use a shifter, I assume the configuration value is should be a signed value relative to the TX value (i.e. TX > RX implies negative shifter). Is this correct (the YANG shifter value is signed)? Interestingly, the actual-duplex-distance value is unsigned.
My reply: the duplex-distance to configure (as an alternative of rx-frequency configuration) is int32 (so signed) to allow to have negative shifter for Rx < TX , but for actual-duplex-instance we report only the positive value.
Action: validate the understanding of interpretation of duplex-distance