Skip to main content

I installed the CC-M replacing the Lionel DCDR per the ERR installation manual and connected pin 1 of the 10 pin, J4, connector on the CC-M to pin 1 on the R2LC07C board. This hardware installation went smoothly and cleanly. After that I had to improvise because I do not have a CAB-1 but a CAB-2. However, I was able to do a manual configuration programming the engine ID, name, road number, setting the option to 08 (diesel with smoke), and selecting 100 speed steps. The engine runs forward and reverse in 100 speed steps. Now for the issues.

 1. As soon as power is applied to the track the engine thinks it is being addressed and starts up rail sounds. If I move the throttle it will move forward.

2. The horn/bell does nothing.

3.The electrocouplers do not open or make sound.

 On the CC-M J4, 10 pin connector, a wire is attached to pin 2 designated Serial Data OUT to sound system. The installation manual does not say where to attach this wire. Could this be the problem? I need help.

Original Post

Replies sorted oldest to newest

My bad. The installation manual does not say what pin to connect to the R2LC but shows a picture instead. It turns out that pin is pin 24 on the R2LC. So my installation is correct. I did a reconfiguration of the engine and options. My electrocouplers do work. I was not pressing hard enough on the buttons, but I still have basically the same issues.

The engine starts up as being addressed as soon as power is applied to the track. I have no sounds other than the engine. I have no control from the soft keypad such as volume, tower com, rpm, etc.

The Serial Out is quite useful, it amazes me why folks hesitate to hook it up...

Only the Serial Out on the Cruise M has sufficient drive to run the Railsounds.   When you attach the Cruise M to the R2LC serial line, it affects the Serial data levels on pin 24, and as a result the data going to Railsounds is not strong enough - and Railsounds quits working.  The best way to install the Cruise M is to isolate the serial data from the R2LC radio pin 24 and place the output of the R2LC pin 24 into the Cruise M *only*, and then the output on pin2 of the Cruise M back into the isolated serial line.  This will keep the signal levels proper for the Railsounds to work.

I designed the Cruise M board, so ask questions and I will do my best to answer them.

jon

SantaFeFan posted:

The Serial Out is quite useful, it amazes me why folks hesitate to hook it up...

Only the Serial Out on the Cruise M has sufficient drive to run the Railsounds.   When you attach the Cruise M to the R2LC serial line, it affects the Serial data levels on pin 24, and as a result the data going to Railsounds is not strong enough - and Railsounds quits working.  The best way to install the Cruise M is to isolate the serial data from the R2LC radio pin 24 and place the output of the R2LC pin 24 into the Cruise M *only*, and then the output on pin2 of the Cruise M back into the isolated serial line.  This will keep the signal levels proper for the Railsounds to work.

I designed the Cruise M board, so ask questions and I will do my best to answer them.

jon

Pictures?

SantaFeFan posted:

The Serial Out is quite useful, it amazes me why folks hesitate to hook it up...

Only the Serial Out on the Cruise M has sufficient drive to run the Railsounds.   When you attach the Cruise M to the R2LC serial line, it affects the Serial data levels on pin 24, and as a result the data going to Railsounds is not strong enough - and Railsounds quits working.  The best way to install the Cruise M is to isolate the serial data from the R2LC radio pin 24 and place the output of the R2LC pin 24 into the Cruise M *only*, and then the output on pin2 of the Cruise M back into the isolated serial line.  This will keep the signal levels proper for the Railsounds to work.

I designed the Cruise M board, so ask questions and I will do my best to answer them.

jon

Jon,

That's interesting, I tried to use the serial out several times a number of years ago, and I was never successful at getting a proper serial data stream to trigger the sound card.  I simply stopped using it, but I'll have to revisit it again with your comments in mind.  I just figured there was something I didn't understand about the serial data out line.

FWIW, my usual experience is the CC-M stops working properly before the RailSounds when you just parallel the serial data.

BTW, for the CC-M documention, other than mentioning "Serial Data Out" in the Pin Designations table, that lead is never mentioned in the text that I can see.  The example for a K-Line Allegheny shows all three serial signals connected to the same place, feeding pin-1 of the CC-M, no mention of pin-2.  This led me to believe that serial data out was for some other function.

On diesels, with the serial data to the RS card going through the motherboard, it would be necessary to find and cut the trace to separate them, and that is also not mentioned.

I did find a mention of pin-2 in this paragraph, but it wasn't clear that using the serial data out was more beneficial than just injecting the horn for configuration changes.

The serial data is repeated on pin-2 of the 10-pin connector on the Cruise “M”. In this
repeated data stream, any configuration changes on the Cruise “M” will inject a
“horn” command. This can be used for confirmation of configuration changes.

 

Attachments

Images (1)
  • mceclip0
Last edited by gunrunnerjohn

So...in lack of pictures...

You connect pin 1 of J4 to pin 24 of R2LC. Then cut loose the trace on the motherboard where pin 24 went. Then you connect pin 2 of J4 to that trace. So the Cruise M buffers the serial data line before it goes to the sound system instead of loading it down?

That's the idea. Her's what I did since I soldered the pin 1 wire from the Cruise M on top of pin 24. I cut pin 24 just beneath the right angle then pulled the pin down half way to the motherboard. That provided an easy post on the motherboard to solder the pin 2 wire from the Cruise M. Done. I suspect as long as the data signal comes out of the R2LC , goes directly to the Cruise M on pin 1 to J4, then comes out of the Cruise M on pin 2 and goes to the motherboard at the pin 24 connection this should work every time.

John

gunrunnerjohn posted:

I'll have to try it again, last time was a few years ago, and for whatever reason, it didn't have a useful signal on pin-2.

There is an Odyssey version of the Cruise M, which places pulses on pin2 for ramping the diesel prime mover.  This is for replacing the Lionel Odyssey cruise board in a diesel.  Maybe you had the wrong version Cruise M??

I am sorry the manual does not have more info, maybe it needs an update.  Although as modifications go on our trains, intercepting the serial line  is straightforward, just as the OP indicates. 

 

Last edited by SantaFeFan

Jon,  I have to admit, I have not seen any difference either.  John and I have discussed this, and I think you and I also.  Many Lionel diesels I have seen do not use it either.  It is rare to see a Lionel model with it (at least for me).

As stated the instructions for K-line install show a direct connection to serial data as it comes off R2LC.  Frankly, I never really had an issue with CCM integrating with engines that are RS4.0.

Now my most recent experience with Cruise CDR, had issue with any sound working with a few, unless I used a R2LC in place of the R4LC.  This was CC with ERR Sound board.  I think we determines there was some software differences for the R4LC. 

Are there some versions that need to be reconciled to ensure what can work with what? I really thought the latest CCM was done to work with anything.  SO a single board for any application, steam, IR tether, or diesel.  Only the 4 pin plug vice 6.  G

 

GGG posted:

 

Are there some versions that need to be reconciled to ensure what can work with what? I really thought the latest CCM was done to work with anything.  SO a single board for any application, steam, IR tether, or diesel.  Only the 4 pin plug vice 6.  G

 

I was also under the impression that for the last few years there was only one version of the Cruise M that worked in all applications including diesels and wireless tethers. Jon, do you know if thats the version that was given to Scott to produce or some earlier version? From some of the experiences here Scott may not have the latest version.

Pete

gunrunnerjohn posted:

I think you may be on to something Jon,  I actually did look at the signal a long time ago, and determined it looked nothing like serial data, so that's when I stopped trying to use it.

Dumb question, is there still an Odyssey version or are all Cruise Commanders created equal now?

John,

I would think both firmware versions are available, but Scott would know best.   The Odyssey version was *specifically* for the Diesels when replacing an Odyssey cruise board in a *Lionel* Loco.   The Odyssey cruise used pin 2 to generate the pulses to Ramp the Prime Mover; so the code in the Cruise M was changed to support that pulse train or the Prime Mover would not ramp up at all.

For the most part, the Cruise M boards sold should have the serial data line output on pin 2.  In many cases it works by just connecting Pin 1 up to the Cruise M, and in the examples in the manual that is what it showed.  The problem to document the wiring for using pin 2 is complicated, as so many versions of the wiring in Lionel product exist.   At the time, it was felt that the application for Cruise M (remember circa 2005 when I designed this!!!) would be K-Line as their cruise was awful, and the manuals reflected such in the pictures.  It is probably time to rethink the applicability of the Cruise M, and show a few pictures in the manuals to help folks.

Bottom Line, if it is easy enough to intercept the serial, you should.  The ability to intercept the serial data is fairly straightforward, and it is best to know how the loco is wired up in that level of detail to insure the upgrade results are robust and work as the electronics age.

 

FWIW I just installed a Cruise M in my Odyessy Alco FA. Simply added the serial data wire to pin 1 on the CCM 10 pin connector and left the trace to the Railsounds untouched. No problem with Prime mover ramp up. Maybe that's why I never used the wire and at Pin 2. This engine also has an AC smoke regulator further sucking current from serial data. No problems.

Ignorance is bliss.

Pete

Last edited by Norton

Add Reply

Post

OGR Publishing, Inc., 1310 Eastside Centre Ct, Suite 6, Mountain Home, AR 72653
800-980-OGRR (6477)
www.ogaugerr.com

×
×
×
×
Link copied to your clipboard.
×
×