Ken C, Gentlemen,
Further to my issue, when I run a loco around the loop with only
1 action being triggered by 1 sensor at a time, thereby spacing
out the commands, then all is fine and everything updates as
expected; but if a JMRI LOGIX says to do, say, 3 or more things
simultaneously [if x, then v, w, x, y, etc..] then as then
commands come in rapid succession, that is when signal aspect
updates get missed.?
On 25/04/2025 2:36 pm, Nimble
Knumblebum via groups.io wrote:
toggle quoted message
Show quoted text
Hi Ken,
I'm running the signals as [to quote the NCE Light-it
documentation], "Using the Light-it as an NRMA conforming signal
decoder". Thus they are programmed [addressed] under 'signal
address programmimg' [as per NCE instructions].
You're correct. I could use an NCE switch-it [or Switch 8] to
do the job. And it does require two accessory addresses for a 3
aspect signal.?
Some time ago I did some testing with the now retired TAM
Valley LEDcoder. It worked okay, but then NCE finally brought
out their 'Light-it' decoders that would operate on the
alternative set of signal addresses. [Should be much more
digitally efficient.]
Nimble
----------------------------------------------------------------------
-----On 24/04/2025 8:42 pm, Ken
Cameron wrote:
Nimble,
?
One thing I should have asked was which
configuration did you have the Light-It using? My memory
seems to say that using it via the signal aspect method is
the more reliable way to use it. That means one appearance
is one aspect using a single command per board. I recall
that when configured as an accessory decoder, and two
commands to the same board go out back to back, it tends to
miss the second command.
?
Others may have a better memory of
possible solutions.
?
By the ¡®NCE List¡¯ I meant the user list
on groups.io for NCE. /g/NCE-DCC
?
-Ken
Cameron, Member JMRI Dev Team
?
?
