I’m installing the ERR Cruise Cmndr on a Lionel Legacy ten wheeler. The lcd tether has two wires. One is blue and the other is red. I’m wondering if the blue wire is for data and red is possibly a hot or ground lead. Any suggestions on how to connect things without doing damage? On the RailSounds connection, I’m pretty sure the lead closest to the pins for the R4LC is the data pin. The opposite side of the 4 pin plug is hot and the one next to hot is ground. The Railsounds in the tender works perfectly with a Lionel O-8-0 that has the same setup so I am good on that end. Thanks for any help, Ed
Replies sorted oldest to newest
Problem solved! I connected the red wire from the LCD wireless tether to pin 1 (closest to the RRLC pins) on the ERR Cruise Cmdr RailSounds port and the blue wire to the 3rd (ground) pin. My railsounds tender now works perfectly with whistle, bell and chuff and rear coupler!
Attachments
@VT Railroad posted:Problem solved! I connected the red wire from the LCD wireless tether to pin 1 (closest to the RRLC pins) on the ERR Cruise Cmdr RailSounds port and the blue wire to the 3rd (ground) pin. My railsounds tender now works perfectly with whistle, bell and chuff and rear coupler!
FANTASTIC!
So you added a TMCC based ERR CC and the Legacy sound system works and accepts commands from the TMCC based CC? G
Can you draw that out please?
Yes, Apparently the signal from the ERR CC to the lcd on the engine tether works with the receiver on the RailSounds tender. Polarity is important as I first tried the wires reversed with no results. It uses the same R4LC as the replaced Legacy system.
In the picture, I’m only using the data and ground pins.
Attachments
@VT Railroad posted:Yes, Apparently the signal from the ERR CC to the lcd on the engine tether works with the receiver on the RailSounds tender. Polarity is important as I first tried the wires reversed with no results. It uses the same R4LC as the replaced Legacy system.
In the picture, I’m only using the data and ground pins.
Are you using an ERR Railsounds board or the Railsounds Lite board that came with the engine?
Pete
I am using the original RailSounds in the tender. I never even took the shell off! Since the tender worked perfectly with a Lionel Legacy 0-8-0 that I have, I left it as is.
Which R4LC did you use? They come in 2 variations. ERR are C08 software which is TMCC 8 bit. Lionel R4LC are S code which is Legacy 9 bit. Yes they both are R4LC. So did you use the engines original R4LC Legacy, or the complete ERR CC R4LC which is TMCC.
The difference being, the ERR motor sections works with a Legacy R4LC or the Legacy RS Lite works with the ERR TMCC R4LC.
What also be good to know that it works on the layout long term. Some incompatibilities show up as a degradation of control with run time. G
@GGG posted:What also be good to know that it works on the layout long term. Some incompatibilities show up as a degradation of control with run time. G
I remember your saga with that issue.
I am using the R4LC that comes with the CComander. I’m not worried about long term degradation because there isn’t a wired connection between the TMCC engine and RailSounds tender. The link is through an optical sensor.
The ER R4LC is electrically and functionally identical to the TMCC R2LC.
How about posting a video of this thing running on your layout. Sounds & smoke all working, ……inquiring minds would like to know …..
Pat
@gunrunnerjohn
This thread has helped a bunch with my project but now I have some issues of my own that are a little different. I installed a cruise commander in my basket case Lionel tmcc M1a. I got the IR tether to work but my chuffs are intermittent. I have your chuff generator installed correctly. Video included.
regards, Tony
Attachments
Well, the chuff generator is generating chuffs that are presumably routed to the R2LC, so it would seem the issue you're having is in the serial data or IR link. I've done a few of these, and as long as I aligned the sensor and transmitter on the drawbar, it works fine for me. I don't see how this could be the Chuff-Generator as I see a regular pulsing of the LED just like I should for normal operation.
Did you use the existing IR components on the drawbar for the M1a?
@gunrunnerjohn posted:Well, the chuff generator is generating chuffs that are presumably routed to the R2LC, so it would seem the issue you're having is in the serial data or IR link. I've done a few of these, and as long as I aligned the sensor and transmitter on the drawbar, it works fine for me. I don't see how this could be the Chuff-Generator as I see a regular pulsing of the LED just like I should for normal operation.
Did you use the existing IR components on the drawbar for the M1a?
Yes, I’m using the existing IR components. Whistle blows exactly when I push the bottom on Cab2. Only chuff which I thought was weird since the light on the cg is lighting up when it’s supposed to.
-Tony
@BeefyT posted:Yes, I’m using the existing IR components. Whistle blows exactly when I push the bottom on Cab2. Only chuff which I thought was weird since the light on the cg is lighting up when it’s supposed to.
-Tony
You’re either not in alignment during chuffs, or the IR is stealing too much serial data to compute the chuffs,…..John is correct, the little LED on the chuff generator is blinking indicating it’s making the chuff signal. The output from John’s generator should go to the chuff in pin on the Cruise Commander, and to the Super Chuffer if so equipped…..if you verify your IR alignment is good, and all other sound functions work as advertised under command, you’ll more than likely need to add a serial buffer to get all features working correctly….
Pat