Straight out of the packaging, “Prototype” throttle mode is default. This mode integrates the motor’s BEMF with the prime mover sound so that it reacts to changes in speed and load. At any given speed step, the motor could be at notch 8, idle, or anywhere in between depending on what the locomotive is doing. “Traditional” throttle mode simply ties the prime mover “notches” to speed steps. (i.e, the faster the throttle is set, the higher the RPM of the prime mover.) “Prototype” mode is the bread-and-butter of the TCS software, and once calibrated, it’s a thing of beauty. (Calibrating it–not so much. Lots of trial and error, and the manual isn’t as clear as it could be.)
By default, the deceleration CV (CV4) is programmed to 60 in what TCS calls “mainline” mode. At this setting (on my loco) it takes about 53 seconds to come to a complete stop from full speed. With CV4 set to 255 (maximum), my loco takes about 3.5 minutes to stop from full speed. I currently have it set to 180, so it takes about 2.5 minutes to come to a complete stop from full speed.
For those who think 2.5 minutes to come to a complete stop is far too long, that’s what the brake function is for. TCS uses a progressive 5-step brake structure, where each successive press of the brake key (F7) increases the braking amount by a programmable amount. By default, it’s 20%, 40%, 60%, 80% and 100%, though I’m not sure the percentages are quite accurate. On my loco, without brakes, it takes about 2.5 minutes to come to a complete stop from full speed. Pressing the brake key once decreases that dramatically to just under 30 seconds. Pressing it twice drops the stopping time to around 22 seconds. Three times 16 seconds, 4 presses stops me inside of 10 seconds, and a fifth press stops me inside of 5 seconds from full speed.
TCS also has what it calls “switching” momentum. This (by default) is set to 5 for both acceleration and deceleration, giving you near instant response time to changes in the throttle. You can toggle between “switching” and “mainline” momentum by pressing the F15 key. (This is handy for kids or adults who don’t quite grasp the notion of using a separate key for slowing down the locomotive.)
Note: The values for acceleration and deceleration in “mainline” and “switching” mode are set via the 4-CV programming protocol. Simply changing CVs 3 and 4 does not affect these values. For example, the decoder comes with the “mainline” acceleration and deceleration values of 20 and 60 respectively. I find that too quick, so I re-program CVs 3 and 4 to 60 and 180. The loco reacts based on those new settings. I change to “switching” momentum via the F15 key. Doing so writes a value of 5 to both CV3 and CV4. I switch back to “mainline” mode. The default values for “mainline” mode are still 20 and 60, so the decoder will write 20 and 60 to CV3 and CV4 respectively. In order for my 60/180 to become permanent for “mainline” mode, I must re-program the default using the 4-cv programming (or Decoder Pro). Then, I can toggle back and forth to my heart’s content. (Another place where more clarity in the manual might be helpful.)
I’ve got probably around 40 hours or so on my latest TCS WowDiesel decoder (the same one Greg and Martin have). I’ve not had any of the issues Greg has experienced with respect to sound dropping out or runaway locos. I don’t use custom speed tables, so I can’t speak to the issues Greg seems to have with them. Outside of an occasional stutter at slow speeds, mine has been rock solid. TCS decoders do occasionally go berserk and need to be reset in order to behave properly once again. I’ve seen it with other TCS decoders I have in use, and have read of others’ experiences as well. Perhaps that’s why TCS has a “no questions asked” return policy–just in case.
Later,
K