|
64 | 64 | * added or removed by the user. |
65 | 65 | * <p> |
66 | 66 | * A datapoint type consists of a data type and a dimension. The data type is referred to through a main number, the |
67 | | - * existing dimensions of a data type are listed through sub numbers. The data type specifies format and encoding, while |
| 67 | + * existing dimensions of a data type are listed through subnumbers. The data type specifies format and encoding, while |
68 | 68 | * dimension specifies the range and unit.<br> |
69 | 69 | * A datapoint type identifier (DPT ID or dptId for short), stands for one particular datapoint type. The preferred - |
70 | | - * but not enforced - way of naming a dptId is using the expression "<i>main number</i>.<i>sub number</i>".<br> |
| 70 | + * but not enforced - way of naming a dptId is using the expression "<i>main number</i>.<i>subnumber</i>".<br> |
71 | 71 | * In short, a datapoint type has a dptId and standardizes one combination of format, encoding, range and unit. |
72 | 72 | * |
73 | 73 | * @author B. Malinowsky |
@@ -567,7 +567,7 @@ public static DPTXlator createTranslator(final DptId dpt) throws KNXException { |
567 | 567 | * <p> |
568 | 568 | * The translation behavior of a DPT translator instance is uniquely defined by the supplied datapoint type ID. |
569 | 569 | * <p> |
570 | | - * If the {@code dptId} argument is built up the recommended way, that is "<i>main number</i>.<i>sub number</i>", |
| 570 | + * If the {@code dptId} argument is built up the recommended way, that is "<i>main number</i>.<i>subnumber</i>", |
571 | 571 | * the {@code mainNumber} argument might be left 0 to use the datapoint type ID only.<br> |
572 | 572 | * Note, that we don't enforce any particular or standardized format on the {@code dptId} structure, so using a |
573 | 573 | * different formatted dptId solely without main number argument results in undefined behavior. |
@@ -595,10 +595,10 @@ public static DPTXlator createTranslator(final int mainNumber, final String dptI |
595 | 595 | } |
596 | 596 |
|
597 | 597 | /** |
598 | | - * Creates a DPT translator for the given datapoint type main/sub number. |
| 598 | + * Creates a DPT translator for the given datapoint type main/subnumber. |
599 | 599 | * |
600 | 600 | * @param mainNumber datapoint type main number, 0 < mainNumber |
601 | | - * @param subNumber datapoint type sub number selecting a particular kind of value translation; use 0 to request any |
| 601 | + * @param subNumber datapoint type subnumber selecting a particular kind of value translation; use 0 to request any |
602 | 602 | * type ID of that translator (in that case, appending the physical unit for string values is disabled) |
603 | 603 | * @param data (optional) KNX datapoint data to set in the created translator for translation |
604 | 604 | * @return the new {@link DPTXlator} object |
@@ -659,7 +659,7 @@ private static DPTXlator createTranslator(final DPT dpt) throws KNXException { |
659 | 659 | /** |
660 | 660 | * Creates a DPT translator for the given datapoint type ID. |
661 | 661 | * |
662 | | - * @param dptId datapoint type ID, formatted as {@code <main number>.<sub number>} with sub |
| 662 | + * @param dptId datapoint type ID, formatted as {@code <main number>.<subnumber>} with sub |
663 | 663 | * numbers < 100 zero-padded to 3 digits, e.g. "1.001" |
664 | 664 | * @param data (optional) KNX datapoint data to set in the created translator for translation |
665 | 665 | * @return the new {@link DPTXlator} object |
|
0 commit comments