Standard DCC is a one-way protocol: [NMRA] standard DCC command stations can
only send messages to DCC decoders and DCC decoders cannot send messages to
[NMRA] standard DCC command stations (yes, there is RailCom, but that is
something different). Normally, DCC decoder CVs cannot be directly "read".
Reading CVs is done via a trick. The DCC command station asks if a bit is a
one or zero and the decoder does (or does not) run the motor a little if the
bit is a one and the command station detects the slight current draw. To read
a CV byte, the DCC command station asks 8 times, once for each bit in the
byte. This process takes time. All [NMRA] standard DCC command stations do
this the same way, so all take the same amount of time.
At Wed, 19 Mar 2025 17:17:52 -0700 "Human[c]ity Junction" <heath@...> wrote:
I really like Decoder Pro. But, the ESU Programmer is significantly faster at reading/writing ESU decoders. Is there a command station or other computer to DCC interface that I can use with JMRI Decoder Pro that would give me similar read/write as the ESU Programmer?
It is my understanding that the weak link of decoder pro is the computer to track interface.
--
Heath @ Human[c]ity
( )
( )
( )
--
Robert Heller -- Cell: 413-658-7953 GV: 978-633-5364
Deepwoods Software -- Custom Software Services
-- Linux Administration Services
heller@... -- Webhosting Services
