ERR Cruise Commander V4.1 board problem

You can use another R2lc, but it should be -08 revision.

Have you tested other locomotives to be certain that the problem is in the loco and not with your remote?

The buttons on CAB-1 and CAB-1L will "wear out" in this manner. I do not know about CAB-2.

Any R2LC that's 08 or later firmware will work, and of course the R4LC with the 08 firmware.  Roy is right, that's about 98% sure to be the R2LC, doesn't sound like the Cruise Commander.

Thanks for your help.  I have 2 Cab-1 controls with the same result from both.  I have no problem using either control with any of my other engines.

A problem with the R2LC is a possibility.  The placement of the antenna outside the engine shell seems to be critical.  I tried running the engine without its cover so the antenna could be repositioned easily and without cover interference.  Antenna position and length was more critical than I think it should be.  The R2LC is rev 8 so I will try exchanging it with an R2LC rev 8 from a good engine and see if the problem follows the board.  I will post an update.

What sound system are you using?  Part of this sounds like a corruption of the serial data that I have experienced mixing and matching parts.

Obviously with Brass engines, the antenna must be outside the shell, or the shell must be insulated.  Surprised the CC is not inside tender too???

If none of the above work, unplug Rail Sounds from power and serial data and run engine.  See if smoke control, rear coupler and other functions now work. 

If they do you can try attaching serial data to the R2LC pin, vice using the 4 pin connector on the CC.  You can get power from the 4 pin, but use serial data direct from the R2lC via the header pin.  Just like Lionel does, without those buffers ERR installed on the CC.  G

The fact that the smoke output ceases to work after a short time, even with the tender disconnected, makes me think it's probably not serial data.  The smoke output triac operation shouldn't have any relationship to the serial data.

Why not, triac gets turned on and off with serial data commands.  I have engines just stop while running.  Same principle right?  Hard to say, but this bad behavior that follows a timeline I have seen before.  So it is a possibility, as are many other items.  G

The triac in internally connected directly to the microprocessor, so I'd think it unlikely that the serial data output being loaded would cause that.  However, I'll yield the point, I obviously can't say that's a 100% certainty.  I will say that's not the first place I'd look for this particular set of circumstances.

This morning I removed the Williams "J" R2LC board and connected it in a K-Line steam engine.  The "J" problems moved to the K-Line.  The "J" ran perfectly with the K-Line's R2LC.  So the problem appears to be a defective R2LC.

Thanks everyone for your help.  I have ordered a new R2LC board.

I would have been surprised if it was anything else based on your symptoms, glad it's an easy fix.