Michael,
The NMRA version of RailCom, S-9.3.2 was published, in English,
back in 2012. See:
The fact that it does not include the latest updates that are
being worked out with the Rail Community is hardly any excuse for
the lack of participation by most US manufacturers.?
On the other hand, the lack of US support for RailCom (which is
virtually unknown the US market place) may be the root cause for
the lack of NMRA volunteer resources available to keep everything
current. The NMRA is its membership, and runs on its volunteers.
My guess is that the NMRA consists mostly of folks from the USA.
If it is lagging behind with RailCom, it is because there is no
volunteer running with that project. Taking a cheap shot at the
NMRA is not really a useful way out of this catch-22 situation.
JMRI does amazingly well at supporting what is being used by its
various contributors, but again, you don't see very much support
for products that we don't use. My guess is that JMRI DecoderPro
support will follow along very closely with NMRA standard product
capabilities and customer choices. I.e. we should purchase systems
that support the best programming options, not expect DecoderPro
to somehow magically make old slow designs work faster.
Dick :)
On 3/21/2025 5:01 AM, Michael Smith via
groups.io wrote:
toggle quoted message
Show quoted text
Yes the RailCommunity specs. are all in German but if you are
a Merg member they are all available to you in English and all
up to-date unlike the NMRA versions.
?
RailCom+ is known within the RailCommunity specs. as DCC - A
(for automatic login).
?
Michael
