This was inspired by a comment on #407 and adds a reference for standard preferred control function addresses. This can be used as a reference for developers looking to assign a control function's preferred SA if they use a "well-known" standard function code.
As usual, users should not expect that the preferred address will be used if their NAME fails to arbitrate against another NAME on the bus that also wants that address. In those cases the stack will automatically select an appropriate address in the self configurable range if the NAME allows arbitrary address capabilities.
How has this been tested?
This information was directly sourced from the publically available ISO11783-11 database here. Since the change is header-only, no tests were required.
Describe your changes
This was inspired by a comment on #407 and adds a reference for standard preferred control function addresses. This can be used as a reference for developers looking to assign a control function's preferred SA if they use a "well-known" standard function code.
As usual, users should not expect that the preferred address will be used if their NAME fails to arbitrate against another NAME on the bus that also wants that address. In those cases the stack will automatically select an appropriate address in the self configurable range if the NAME allows arbitrary address capabilities.
How has this been tested?
This information was directly sourced from the publically available ISO11783-11 database here. Since the change is header-only, no tests were required.