RailPro > RailPro Specific Help & Discussion

RP sounds and DCC issue

(1/3) > >>

ON28:
Board--

I've had LM3-S modules in an Intermountain F3 and Atlas GP7 for several years, with TCS KAs. I just updated to v2.30. Layout powered by NCE. Was running them in DCC mode when the horn and dynamics turned on by themselves. This happened running through some Atlas Custom Line switches with unpowered frogs, but this never happened with the previous version software. Both locos prior ran perfectly in RPO mode. I also cleaned the wheels for better contact. The HC shows voltage in both locos of about 12.3v. Thoughts? 

G8B4Life:
Little bit hard to formulate a theory with such a small data set.  Did it happen just this once or multiple times? If it's just once I'd test some more and see if it happens again and in the same situation etc.

Other than that all I can think of is the LM's got confused when interpreting something in the DCC waveform. Strange none the less that it'd turn on two effects if that's the case.

If it happens again I'd send a message to Ring. We don't get told much anyway but there wasn't anything mentioned about changes to DCC functionality in the 2.30 "release notes".

Now, when you say you were running them in DCC mode, were you running them as individual loco's or somehow got them to run as a consist?

- Tim

ON28:
Running separately.

ON28:
Here's what I am not looking forward to: Being told a) the TCS keep alives aren't designed for the LM and b) finding out the latest LM software update is designed to only work with the new Ring keep-alives, exclusively.

nodcc4me:
TCS Keep-Alives do work with the latest versions of LM's, including the LM-3S. I have a few installed. I don't think Ring would make them incompatible. That would really aggravate a lot of folks.

Navigation

[0] Message Index

[#] Next page