Cruise M = No Reverse

Hmmm... I just ran into the same problem with an Atlas RS-3.  Standard Lionel TMCC installed.  Engine works fine forward and is def. using speed control.  Reverse switches the lights, some sort of sound happens, etc.  But, no actual movement.  Will check the board.  Hopefully I won't have to pull the heat sink back off since that takes a while to get on.  I'll try to issue the proper sequences to enter 100 steps speed mode in case that's an issue.  I used the DCS handheld to select "128 speed steps," but who knows what that actually sent.

Anyone know where to connect wire 2 off the ten pin connector on the Cruise M?  It is supposed to go into the sound system somewhere to provide confirmation of commands.

Thanks,

Mike

  You should already have confirmation sound. The second wire on the cruise "M" is not used unless your installing in a steam engine with a tether.

Bill 

Somehow I missed the fact that this has the Cruise Commander M board, so the previous comments may be useful.  I'd look closely at those resistors near the four pin connector.

I know that pin 3 on the RS connector on any of the AC or DC Commanders or the Mini-Commander goes to a logic high when the horn it blown, it's used to trigger a conventional horn board.  I don't think it's used for the Cruise Commander M, but I wouldn't swear to it.  I've never tried to use that feature with the Cruise Commander M, since I always had sound in anything I was installing the board into.

ERR had no help to offer.  I pulled the unit out (much easier now that I know exactly how to do it) and re-installed the original cruiseless board. Reverse works.  I can't see anything wrong with the Cruise-M.  Guess I'll send it back.

Thanks for all the suggestions,

Mike

Well, if the original works and the CCM doesn't have reverse, it's probably bad.  Sending it back seems like the way to go.

Hi Bill,

I missed this post originally.  I do not have confirmation sounds.  So, either I am not driving the board properly (I am using DCS to send TMCC commands, so this is possible), or something else is wrong.

Hmmm... wonder if DCS "does" reverse in a slightly different manner, and this is the cause?  I don't know enough about TMCC to know if this makes any sense.  The other electronics in the engine see the DIR change.  The light changes and sounds happen.

Mike

I just noticed this thread resurfaced. As a followup, resoldering the resistor did not last. It worked for a few hours then lost reverse again and I was not able to get it working again. Thanks to my dealer, Boxcar Bill, the board was returned to ERR and replaced. Thank you again Bill and Jon.

Pete

Well, if the standard DCDR works and the CCM doesn't work, I would think that isn't likely the MB connector, the pins serve the same function.  The only difference with the CCM is you have to run the data line to the R2LC pin, you should be able to verify that one is connected.

  Mike

     I strickly use Tmcc, I don't know about DCS. To get confirmation you would need a cab1 or legacy so you could set the features and then you would receive confirmation.   

 It might also help to do a reprogram.

Bill

I did do a reprogram.  You can do that from a DCS unit.

I think I am just going to send it back and ask that the next one (the third) be tested in a locomotive before sending it out, or else issue a refund.

I'll try and pick up a CAB-1 at York just to make things in the future easier.

Mike

I will point out that the instructions for the CCM manual states you must program the feature code for it to work properly.

Why is it necessary to set the Feature Code?

The Cruise Commander uses the serial data from the R2LC receiver to detect the throttle settings. This serial data signal is dependent on the feature code. If this is not properly set, the loco will not respond to throttle commands and may even enter into conventional mode and rocket down the rails!  Additionally, features like the smoke unit will not operate until the feature code is set. It is always a good idea to know your loco feature codes for proper operation of smoke/strobe/cab/marker lighting effects. This is true of your entire TMCC loco stable.

Yeah... I saw that.  I specifically asked ERR that question, and they said it would not make a difference.  And I did set the feature code on the last board.  I'll try on this one.

edit: No change.  I do get a horn blow after aux1-8.  8 is the code the Atlas directions said to use.  I also changed the engine ID from 1 to 2.  Sometimes things don't do what you might expect if you are not really changing anything.  Engine worked forward only on ID 2.  The only option I can see at this point would be to make a rig so I can run the engine without it moving and look at the signals on J1 (I think that's the correct connector.  The one that controls direction.)

Mike

Looking at this, I think it applies more to the Cruise Commander, not the Cruise Commander M.  This may have just been copied from the other document and never removed.

Since all this board gets is the PWM signal and power, I can't see how the feature code should affect it's operation.

Right - the feature code programs the R2LC - which I didn't replace?  New terminology for me :-)

Mike

Since ERR shipped a new J1 to MB cable, I decided to use it.  Thinking maybe the pins were different sizes - something like that.  It is interesting that the ERR cable only had three wires, but still, no change.

I was playing with the engine anyhow.  The controller did a nice job of pulling a heavy consist up and down decent grades at very, very slow speeds.  2 out of 100.

Hope I can get it to work.  It's a decent controller.

Mike

I've been very happy with the Cruise Commander in my conversions, it works better than either the TAS EOB or the original Odyssey speed control.  I will have to say that the new Legacy locomotives I have with Odyssey 2 are great runners, I think they have the edge over the ERR CC or CCM.  OTOH, it's easy to install the ERR cruise, one of it's endearing qualities.

Third time was a charm.  So, be aware that either they kept sending the same one back or they have a batch with issues.  Never a word on what the issue might be or anything.  At least they sent replacements promptly.

Mike

It's a bummer that you have to keep shipping something like this back, but I'm glad you finally got it working.