ERR Cruise Commander M not working

I purchased a Cruise Commander M as a last resort, along with an R2LC board and a C420 motherboard, and cobbled them together to make something that would give my MTH Blue Comet TMCC.

I got it to run both directions without an issue, but when I tried to splice in my serial data cable from my Railsounds Commander, I got sound but the motor will not move, even after I removed the sound system connection. 

Any ideas?

Thanks 

Original Post

Try buffering the serial data to the sound board with this arrangement.  The older CC-M didn't like the lower amplitude serial data that was produced when the sound board optical isolator was added to the mix.

Attachments

Photos (1)
gunrunnerjohn posted:

Try buffering the serial data to the sound board with this arrangement.  The older CC-M didn't like the lower amplitude serial data that was produced when the sound board optical isolator was added to the mix.

I will try this when I get home.

Could I have damaged the Cruise Commander M board?

Probably not, it's a known issue when you connect the RailSounds board to the serial data with the CC-M.  There was a change and the new CC-M versions had a better input circuit sensitivity to handle the issue.

Before you add that buffer circuit, try to get the R2LC and Cruise M to make the engine run again without Railsounds. You shouldn't need extra circuitry to make that happen. If you have any older TMCC engines you could try and swap boards to see which one isn't working. Also unplug your Command or Legacy base and see if it runs in conventional. Shouldn't need serial data for that.

Pete

Pete, sometimes it does require a buffer.  I did a pair diesels with two of these boards, and they needed the buffer to drive the RS boards and the cruise module.  I also had the same issue with the TMCC Camelback with the wired tether, same solution.

Interesting. I have used about ten of these and never needed a buffer. I never used the TMCC version with a wireless tether though. The motherboards for the Legacy version has a buffer on board for the wireless tethers.

Still curious what blew the OPs Cruise M.

Pete

The wireless tether installations have always needed the buffer for me, but I ended up having to use one on several wired installations.  FWIW, the new single board RS (RS-Lite) has an optical sensor on the input serial signal and loads the serial data more than previous RS electronics.

Well, it looks like it's all a moot point now. I tried to run Railsounds in conventional mode, and now the chuff sound doesn't work. All other sounds do. I tried disconnecting the reed switch, and touching the wires together produced no sound.

Whatever ruined the Cruise Commander M also ruined the Railsounds Commander.

Add Reply

Likes (0)


OGR Publishing, Inc. PO Box 218, Hilliard, OH 43026 330-757-3020
www.ogaugerr.com
×
×
×
×
×