Need ERR Cruise Commander M Instructions

Follow this link:

  Cruise Commander M Instruction Manual | ERR

Mike

In the future, 3rd Rail's ERR section has all the instruction manuals for the ERR products.

ERR by 3rd Rail Manuals

I appreciate everyone's help.  I found the instructions, and have made progress.  After a really frustrating day yesterday, I have everything working but the smoke and headlight.  This may be due to poor soldering on my part, still troubleshooting.

One thing that I did misunderstand in the instructions was placement of the serial buffer.  It needs to be wired between the "receiver" board and the Commander board, not after the board then to the tender tether.  Also, per one of John's posts in a related thread, it appears you shouldn't use the "green wire" on the Cruise Commander M 10 pin connector to drive tether.  I wired the serial buffer "out" wire to both the Cruise Commander and the tether in one connection, essentially bypassing the Cruise Commander with regards to sending signal to the tender.  Even though the FAQ sheet I got from the supplier said to use the 10 pin green wire, if I did, then it still didn't work.

Again, thanks for everyone's help!

If you were upgrading the TMCC unit with Cruise M, the Head light and smoke would not/should not be affected.  You are just replacing the driver board on the engine.  Normally you can just splice into the serial data signal, or direct solder to pin 24 of the MB for R2LC.  If for some reason that drags down the Serial data for the Railsounds in the tender then a buffer is needed.  Normally not the case. Supposedly the serial out on pin 9 was for diesel I believe, but since that conversation with Jon Z was so long ago, I don't remember for sure.  I have only run into issues with mismatch parts and usually the more advance elements of RS and Legacy.  Not the RS 4 of older units.  G

Serial data is pin 24 on the R2LC. Goes to Pin 1 on the ten pin connector on the Cruise M. Pin 23 is the antenna wire.

Pete

@Burl posted:

One thing that I did misunderstand in the instructions was placement of the serial buffer.  It needs to be wired between the "receiver" board and the Commander board, not after the board then to the tender tether.

I normally wire the serial buffer right at the R2LC socket, and then use it's serial output to drive the Cruise Commander M.  That gives be a certainty of having a good signal to the CC-M.  If everything else was working before off the serial data, it should still continue to work as the serial buffer presents almost no load on the R2LC output data pin.

@Burl posted:

Also, per one of John's posts in a related thread, it appears you shouldn't use the "green wire" on the Cruise Commander M 10 pin connector to drive tether.

There are at least two versions of software for the CC-M, one outputs serial data on pin-2 of the 10-pin connector, the other outputs "duty cycle" on pin-2.  "Duty cycle" is a signal that just pulses when the motor is moving, it's intended for diesel installations to drive the Railsounds 4 prime mover ramp up and ramp down.  Obviously, the CC-M that outputs "duty cycle" can't be used to repeat the serial data.  If you know you have serial data on pin-2 of the CC-M, it's fine to use that to drive the IR tether.

@GGG posted:

If you were upgrading the TMCC unit with Cruise M, the Head light and smoke would not/should not be affected.

He was also installing the Super-Chuffer.

Yes 24 sorry. Correction made. G

Information is available:  Search ERR Cruise Commander M Instructions.   1.98" Long X 1.28" Wide X 1.00" High.  ERR  is probably not a forum sponsor.

@Mike CT posted:

Information is available:  Search ERR Cruise Commander M Instructions.   1.98" Long X 1.28" Wide X 1.00" High.  ERR  is probably not a forum sponsor.

I hope in the intervening two and a half years he solved his installation problem.

GRJ - There certainly are a lot of threads where a problem is discussed, but, no resolution offered. 🤷🏼‍♂️🤷🏼‍♂️🤷🏼‍♂️

@Mark V. Spadaro posted:

GRJ - There certainly are a lot of threads where a problem is discussed, but, no resolution offered. 🤷🏼‍♂️🤷🏼‍♂️🤷🏼‍♂️

Not sure what you're referring to.  In this thread, I offered a lot of detail about the issue.

@gunrunnerjohn posted:

Not sure what you're referring to.  In this thread, I offered a lot of detail about the issue.

It appears the OP never returned to give us a final report on his issue, and left the outcome in the air.

@Mark V. Spadaro posted:

It appears the OP never returned to give us a final report on his issue, and left the outcome in the air.

Oh, that.  Happens all the time, I'm used to it.