Short, Long, Address Range Spec

[DrEVILish]

What's your stance on below:

When using DCC-EX, in the config.h file.

/////////////////////////////////////////////////////////////////////////////////////
// REDEFINE WHERE SHORT/LONG ADDR break is. According to NMRA the last short address
// is 127 and the first long address is 128. There are manufacturers which have
// another view. Lenz CS for example have considered addresses long from 100. If
// you want to change to that mode, do 
//#define HIGHEST_SHORT_ADDR 127
// If you want to run all your locos addressed long format, you could even do a 
//#define HIGHEST_SHORT_ADDR 0
// We do not support to use the same address, for example 100(long) and 100(short)
// at the same time, there must be a border.

The NMRA Address Specification is (1-127) Short, (128-10239) Long.

The Extended Address range is 1 through 10239 (Hexadecimal values 1 – 27FF).

Notable mentions for spec
https://dccwiki.com/Address_Range#cite_note-AddressRange-20

[reinder]

Technically is it is possible to encode addresses 1-127 as short AND long address (never tried it but I expect it to work), most systems however have a border. If there is a distinct border Traintastic enforces that. In case of LocoNet it is 1-127 for short and 128 and up for long. For DCC-EX this is also the case, based on the snippet above it should be a setting as it is configurable in DCC-EX. (Allthough I think most users don't alter it.)

[DrEVILish]

Again I think it might be one of those things to have in the nice-to-have pile, as if some people change it then have Traintastic as the limiting factor.

I'd be fine with it if you say "no, I wanna stick to the NMRA spec." 127-128 being the border.

[reinder]

Yeah this is a nice-to-have one, although it is not that hard to add. But...adding more settings in also increasing the user error possibility, so it should at least be some kind of advanced option, maybe something to combine with #71.