Skip to main content

This discussion got me curious enough to actually compare the serial output of the Legacy base versus the TIU when controlling TMCC engines. 

 

  • Under DCS, there is no functional difference between "128 step" and "REL" mode.  In both cases the TIU issues TMCC relative speed commands (generally +/- one speed step).  This is the same as "CAB1 mode" under Legacy control.
  • The remote displays the supposed speed in 128-step mode, but there is no connection between the displayed speed and what the engine has actually been commanded to do.  (I think this is the equivalent of R100 mode under Legacy - relative commands with the supposed speed graph).
  • In 32-step mode, the TIU issues TMCC absolute speed commands (I know, duh).  Any non-Lionel engine that was not designed to accept absolute speed commands will ignore the TIU in 32-step mode, just as it would ignore the CAB-2 in "TMCC mode" (again, duh).  This may include all third-party cruise systems.
 
That said, there are a few differences between DCS and Legacy in response to TMCC commands (I don't have a CAB-1 for comparison).  Whether these would result in any operational difference I don't know.
 
  • In TMCC mode, when changing from one speed step to another, the CAB-2 issues an additional relative (step) command before issuing the new absolute speed command.
  • In TMCC mode, when you turn the CAB-2 knob past a detent but without incrementing the TMCC (32-step) speed, the CAB-2 reissues the current TMCC absolute speed command.
  • In CAB-1 mode, rapid spinning of the CAB-2 knob will result in relative commands greater than one step.  (E.g., +/- 2 steps, +/- 3 steps, etc.).  The DCS remote will almost never issue >1 speed step unless the thumbwheel is rapidly reversed from one direction to the other, and inconsistently at that.
 
 
 

 

Some of what is written here are duplicates of what I have posted beforebut in total context may add to understanding of some of the dynamics going on.

 

I took the worst performer of the three apart to determine what boards were in there. Remember I bought this engine from a forum member knowing that the smoke unit was not working and that the individual had never tested it with TMCC.

This B6 engine operates like this.

 B6 Cab 505 – Started up in 32 step speed. Quickset available and functions! Switch to 128 step speed, engine still functions, quickset does not. In either speed step, it operates erratic and poorly under DCS but well under cab1. If I start this in 32 step, with medium momentum, do a quickset speed at 8-12 steps and realize that stopping or uncoupling takes multiple taps, the engine operation meets basic operational requirements.

Note that each of the three engines requires a startup procedure unique to the other two to obtain operational usefulness which is cumbersome. Without some chart of board IDs and mutual compatability it is too hard to determine when the guts of the engine are correct or by human interference has been mucked with. For instance, this engine has a board which was obviously an ERR replacement, so doe one of the other two engines, so who knows.

I still am searching for compatability charts on all  TMCC boards. Are there any out there?

Kline B6 060 switcher

Engine Boards

Base Board - (Large K painted on bottom)

Top side of base board – Marked ‘Lionel Trains’ 691-PCB1-089 Rev ‘A’ with 24 pin connector.

 24 Pin R2Lc Board- Marked R2LC-08 , LT/ERR This is plugged into the base board.

 Reverse / Motor control board – Marked (printed) LY200 and over stamped FW. This board is seperately mounted in engine with heat sinks for the triacs.

 Tender Boards

 Base Board – Screwed to the base. Two 24 pin connectors attached and it contains all female plug connectors. – Marked, Lionel USA, 691-PCB1-050 Rev ‘A’ This board number’s  last digit partially blocked by connector plug on board, hard to make out.

 

Rear most 24 pin plug board – (small K painted on) Marked on plug side, RS27S012, Lionel Lines on chip. On the top side  on another chip, marked Lionel Lines & ATLAN-F and on board RS3 Rev ‘C’, 691-PCB1-04C.

 I make the following comments and  judgements:

  1. R2Lc-08 ERR was probably a replacement board since this engine starts up in 32 steps, like Lionel but unlike other Kline which come up in 128 steps. This is really good because ‘quickset speed’ on DCS controller works very well. Start up at step 8-12.

 Engine came to me without an operating smoke unit. Power out of base board feeding smoke unit on/off switch was not delivering any voltage. Same thing happened to smoke unit when I put ERR cruise M into the other KLINE K4 engine. This I fixed by clipping wire at the board, placed a diode in the circuit and attached to roller pickup. This delivers ½ roller voltage to smoke unit, about 9V. Smoke unit works superior to original board connection.

 

 2. I also added a 22uh 6 amp choke to input rollers. Hard to say if it made much difference but I can say engine control, knowing the step speed, choosing the optimum M range and using quickset start at 8-12 MPH, this engine is now running relatively well.

 

 3.Major complaint about control loss remains in two areas, stopping using the Direction button and firing the rear coupler. Both work reliably using the CAB1 but not so using the DCS remote. Here is why! I realized this by watching the TMCC controller light when operating.  When the DIR button on the CAB1 is pushed, it sends multiple signals based on how long the finger is on the button. I believe at least two ‘blinks’ even with slightest touch. Same true about the coupler rear button.  The result with multiple signals is a high reliability of signal out to the engine and rarely a failure if ever.

 

4. In each of these situations, using the DCS controller, no matter how long you hold either button, it sends only one ‘blink’ signal. If engine fails to get this one blink, control is lost. Knowing this, being prepared to provide multiple taps on the rev or couple buttons increases ability to control. Even though ‘stop’ happens, when precise is necessary this ain’t good enough. Question remains as to why just one ‘blink’ signal in DCS? Question is also open as to the reliability of the reverse motor control board in each engine? When multiples come, reliability is assured. When engine is stopped and the REVerse  button on DCS is depressed, tender makes a HSSH sound if single blink is received, nothing, if not received. By testing, each  kline engine has a different response level from about 70 to 90%.

 

I am done fooling with these engines as I now  really understand the unique characteristics of the KLINE’s that I own. Start each of  them up the way each likes best and be ready to create multiple key tap blinks and they operate acceptably. I still would like compatability charts.

 

There might be an easy microcode patch fix MTH could make to give multiple ‘blips’ but I will not pursue such a request.  I will however be much more careful buying any more TMCC engines for use with DCS, not sure how but if the engine is all original electronics, I will take a shot at it.

Thanks for all your comments and input, information and idea exchanges are what this forum is all about.

 

 

 

 

 

 

Post
The DCS Forum is sponsored by
×
×
×
×
Link copied to your clipboard.
×
×