Mark,
The difference with RailCom is that it is part of the
NMRA specifications, not proprietary, and it may be supported by
any manufacturer. As far as I know TCS and MRC (NEXXT) are the
only US manufacturers either supporting, or planning for RailCom
support. That is a manufacturer's marketing choice, and the
European companies have chosen to support it for some time. It is
probably supported by more systems than not. (at least recently)
Note that ESU decoders support RailCom, not just their own closed
ecosystem. The chances are pretty good that if you have a loco
with a modern European decoder, it already includes RailCom.
By ignoring RailCom the big US companies have effectively kept it
hidden from the US market place. Then they excuse themselves by
claiming that their users don't ask for it. Duh!
Dick :)
On 3/20/2025 9:29 AM, Mark Granville
wrote:
toggle quoted message
Show quoted text
Heath, As others have
indicated, the LokProgrammer is faster because it only works
with ESU decoders. Kinda like that question you asked about
function labels and BLI. Single manufacturer means special
methods can be used. DecoderPro uses the NMRA method because
it has to work with a wide range of manufacturer decoders. I
have read that there is faster reads IF (1) you have a
Railcom enabled command station AND (2) the decoder is
Railcom capable and enabled. It also allows reads using POM.
Mark Granville
