Anyone else had trouble putting a non-ESU decoder in the DC/Silent Rapido GE 44-Tonner that was released in September 2025? The page “Installing a DCC Decoder” page in the manual that comes with the loco warns against it, but I saw no warnings in the product descriptions when I ordered. Movement, horn, bell, cab chatter all worked with a Soundtraxx TSU2 N-18 installed, but I never could get the lights (that work fine on DC) to work. Nor could I change any CVs (other than the decoder’s address). A nightmare. Finally sent it to Soundtraxx who ripped out the ESU motherboard and replaced it with their N-18 Adapter. I’m waiting for it to be returned now.
It’s really annoying that some manufacturers are now going away from being able use the decoder of your choice rather than their’s. Scaletrains are a nightmare to change to a non-ESU decoder. I have heard that ESU is apparently offering to design the motherboards for free as long as a ESU decoder is the sound option. And surprise, surprise the motherboard only works with ESU decoders, so it just means yet again restricting choice.
Thanks, Lee. This is definitely a BAD trend. The lesson I have learned — the HARD way — is that “DC/Silent” is definitely NOT the same as “DCC Ready.” As I wrote earlier, in fairness to customers the sales literature of DC/Silent should point out that that’s really how such locos are intended to be used — on DC and with no sound. They are NOT designed for the installation of a decoder other than the one the importer uses with its DCC/Sound version if you wish to put one in later. Caveat emptor!
Soundtraxx has a You Tube video for swapping out a factory installed decoder with a Tsunami.
Peter
He covers the light issue from 6:43 on.
Thx, Guys — Yes, that’s the video I watched before ordering my DC/Silent 44-Tonner and TSU2 N-18 decoder last fall. It was made using the first release of that loco. (Norman has since departed Soundtraxx.) I carefully followed all the instructions after receiving the new (September ‘25) release in October.
It just doesn’t work — not for me using two different DCC Command Stations nor for Soundtraxx at their office in Durango where I shipped my loco when all else failed. We cannot change any CVs.
Best guess: Rapido/ESU have changed the motherboard so that non-ESU decoders don’t work when installed in place of the dummy/DC plug that comes with the DC/Silent version of this loco.
To wit: Here is the page from the manual which you get when the loco is delivered to you:
Lesson learned — the hard way.
“We won’t apologize for that.”
“Sorry.”
Did Rapido just contradict themselves?
The phone number “equation” was funny, though.
This has been a problem - particularly with Rapido - since the first release of their E8s several years ago. My understanding is that there is an NMRA compliant serial control that can be used to control more lighting with any decoder, but ESU purposely chose not to use it and make the motherboard proprietary, instead.
It’s a hard-ball business decision. I don’t blame them, if they can do it, but it sucks for us customers.
The problem is not limited to ESU. Broadway’s Stealth models are not really compatible with TSC decoders and there are troubles with others besides ESU. In their defense, the Paragon decoder design in their locomotives doesn’t lend itself to cross-compatibility with many decoders. Many decoders don’t do smoke and Broadway also depends heavily on a daughter-board in the locomotive to minimize that giant wiring harness between loco and tender.
Bottom line, we should all expect some degree of difficulty when using a decoder that wasn’t designed-in by the loco mfr.
VERY GOOD, HELPFUL RESPONSE! Thank you, IC_Tom.
Potential customers should be warned before buying a loco version that can (supposedly) accommodate a different decoder than the one the importer includes with their “fully loaded” model.
Has MR mag done an article about this?
I note that the page from the Rapido manual doesn’t say the engine won’t work with a non-ESU decoder; nor does it “warn” you not to do it. It just says that if you put in a non-ESU decoder, the CVs for the various functions will have to be mapped by the purchaser. So in other words, the CVs that control say the lights on a Soundtraxx decoder aren’t the same as an ESU decoder, and which function does what isn’t necessarily the same.
ScaleHogger says they were unable to change any CVs other than the loco address. Was this using a programming track, or JMRI, or ??
What the physical situation appears to be is that there is a special processor incorporated in the light board that accepts output from the ESU decoder to operate the lights. It was my understanding from other discussions that the addressing to this processor was done with a proprietary, possibly undocumented protocol, not with common DCC-compliant commands. Presumably this was done to facilitate installing everything in the limited volume and packaging space in a 44-tonner.
In order to ‘map the lights using CVs’ it may be necessary to bypass or remove the board, complete with processor, and wire the lights directly to the decoder or to pins on the decoder socket. That’s a lot of work for someone thinking they bought an engine that was ‘DCC ready’ for something other than an ESU device, just as hacking the lighting board involves skillz that many model railroaders are likely to possess or value.
I wonder whether some group within JMRI could formalize the interface and APIs for these processors (which I understand, rightly or wrongly, to have been co-developed by ESU and Rápido as a ‘feature’) and incorporate some sort of protocol-translation tool that would let a command stream address the physical light control via the “appropriate” NMRA-specific CVs or a logically-extended set of codes structured as CVs for compatibility.
To be fair, no one said, “the engine won’t work with a non-ESU decoder.” The fact is that it won’t work completely. For headlights, horn, bell, and motor control, everything will work just as with a LokSound … other stuff not so much.
Woke Hoagland is correct in his summary just posted above. There is more lighting than other decoders can fully address with built-in functions. My understanding is that this is also true with ScaleTrains and I know for a fact it is true with Broadway Limited Stealth models. For instance, Broadway lists LokSound and Soundtraxx, but TCS is not mentioned at all. You will be able to connect a TCS decoder into a Broadway Stealth and be able to run the loco, but not everything may work. Rapido is definitely not the only one.
The demand for more lighting capability outstripped the NMRA’s ability to develop pure function standards for the extra capability, I think. I’m way out of my depth here, but I believe the NMRA standard for serial communication with a decoder is something called SUSI (Serial User Standard Interface), yet ESU fails to use it with their custom motherboards developed for Rapido and ScaleTrains. (I believe Broadway does their Stealth motherboards.)
I guess this is what I was looking at. Not being to change CVs is still what I find odd.
