Node id detection

[Poikilos]

This may require discussion, unless you are ok with implementing conventions (as in module features that are a superset of standards).

[Poikilos]

• Added unified function (validate_lcc_id) which handles conversion to hex as well so that there can be a single piece of code that handles the convention (can be used for either validation or conversion to hex or both).
  • Allows elements without zero padding.
    • Adding the function (and related comments and tests for that and only_hex_pairs) also makes that lenience an explicit convention.
• moved conversion from hex to dot notation to new conventions.py (hex_to_dotted_lcc_id)

[Poikilos]

If you could, please make sure the docstring in 2e2e77a is correct, especially control, and the comment under nodeCode =.

[Poikilos]

Also, is 4b94c25 correct, or are partial (right a.k.a. more local side) IDs allowed in dot notation?

• or is there some reason to allow silently degrading to 0 here--I didn't think so since in the case of dot notation we are dealing with user-entered data not packets.

[bobjacobsen]

If you could, please make sure the docstring in 2e2e77a is correct, especially control, and the comment under nodeCode =.

Looks good to me. The mask was written as 0x10_000_000 because the CAN fields are 12 bits each, but changing it to 0x10_00_00_00 definitely makes it easier to read.

Also, is 4b94c25 correct, or are partial (right a.k.a. more local side) IDs allowed in dot notation?

or is there some reason to allow silently degrading to 0 here--I didn't think so since in the case of dot notation we are dealing with user-entered data not packets.

I think this is fine. Thanks for making the change.