Question about TMCC TR Mode

Are you controlling the Train using a Cab1 & Base?  If so, then the original TMCC protocol used by that base cannot send commands for many Legacy sound features.  The Engine and Train commands available within the TMCC protocol are the same so I can't explain why some commands disappear in Train mode.   Firmware within the units?  You need a Legacy base and ensure all the train units are set to Legacy control mode to enjoy all of the sound features (the Legacy protocol is extended for sound, light, and effects features)

@RIRocket posted:

... right now I’m running them in TMCC TR mode.  When I do so, other features disappear—talking, revs up and down—even if I isolate an engine and try that.  Is this normal?

How many units are in the train you've assembled using the "TR" function?

• Lead 'A'?
• Second 'A"?
• Super Bass 'B'?
• StationSounds Diner?

I assume that it's only sounds that are missing, and not motion, and that these are locomotive-specific sounds that should be coming from the Super Bass unit.  Is this correct?

You mentioned isolating an engine.  Does the isolated engine move under command control?  Since one wouldn't normally configure a single single engine using "TR" are you running it normally using "ENG" when you hear it's sound problems?

Mike

I’m running an ABA consist.  Everything is fine, except I can’t trigger the tower talk, crew talk, revs up an down, or volume when in TR mode.  You can address a single engine while in TR mode, and when I do, that engine will respond to only revs up and down.  

Not sure this is your issue but what TR # are you using?

@RIRocket posted:

I’m running an ABA consist.  Everything is fine, except I can’t trigger the tower talk, crew talk, revs up an down, or volume when in TR mode.

Where is the sound presently coming from (if anywhere), and where in your opinion should it be coming from?  'A' facing forward, 'A' facing back, or Super Bass 'B'?

Mike

The sound is fine—it’s coming from the A and B units.  Just nothing else triggers in TR mode in TMCC.  

If memory serves, in TR mode, only the ENG# you entered first building TR is the head of the TR and will be sent sound commands. Similar to fact that in TR mode, open Front coupler only sent to ENG# entered first as head of TR, and open Rear coupler only sent to ENG# entered last. I may be way off base, but hopefully this will jog someones memory and get to a solution.

@MED posted:

If memory serves, in TR mode, only the ENG# you entered first building TR is the head of the TR and will be sent sound commands. Similar to fact that in TR mode, open Front coupler only sent to ENG# entered first as head of TR, and open Rear coupler only sent to ENG# entered last.

I think you're right on the money here, and it's because Cab-1/Base-1's support for MU's (Lash-ups) is limited compared to Cab-2/Base-2's.

This means that @RIRocket will have to use a work-around.  The one that has been recommended here on the forum in the past is as follows.  This should give you sounds from two of the three units, assuming that they're capable of producing sounds, but not all three:

1. Presently we assume that all three units have separate command ID's.  You'll need to change one of them.
2. Find the ID for the front-facing 'A' unit and reprogram the Super Bass 'B' to that ID.  Make them the same.
3. Make sure that the ID for the rear-facing unit 'A' is different.
4. Recreate your TR but only enter the forward-facing unit and the rear-facing unit.  Leave the Super Bass 'B' out of the sequence.  Even though on the track the 'B' will be physically positioned in between the front-facing and rear-facing units (most operators would place it here) the Cab-1/Base-1 will think that your lash-up is only two units long, consisting of only the two 'A's.
5. Your sounds-related commands will now go to both the front-facing 'A' and the 'B' simultaneously since they both share the same ID.  Unfortunately with this approach the rear-facing 'A' will be silent.

Let us know if this is close to what you're looking for.  Because of the limitations of Cab-1/Base-1 there's not much more that can be done.

Also, be aware that if you activate a remote uncoupler function, or smoke activation, intending for it to go to the front-facing 'A' it will also, simultaneously, operate the matching one on the 'B' because they have the same ID.

Mike

I bought a used Lionel Legacy Rock Island E7 set, one powered, one dummy. Last time I used them had the blue CAB-1L and base (Switched to older CAB-1 because I have more remotes and I leave them all over the basement). I don't remember having to use TRain, just ENGine. Throwing the Superbass in there might 'complimicate' things, but assuming it has no electrocouplers, could you just assign it the same ENG address? I can't remember how I did not have the coupler on the rear dummy unit not open.

I have a pair of Lionel postwar F3's converted to TMCC set to the same address, the powered has some Electric RR, the dummy rear an LCRX controlling the lightbulb and electrocoupler, wired up to be the rear bulb and rear electrocoupler.

I do not have CAB-2. I do not have a CAB-3 on order. I may regret that later.

@illinoiscentral posted:

... but assuming it has no electrocouplers, could you just assign it the same ENG address? I can't remember how I did not have the coupler on the rear dummy unit not open.

You can, specifically because you have one powered and one dummy.  They won't fight each other when you try to get rolling, which would happen if you put two powered units tail tail and they have the same ID.

The TR (lash-up) feature allows you to couple two powered units with differing IDs tail to tail, among other things (like the ability to put additional powered units in between them), and activate only the electrocouplers on the very front and the very rear of the linked pair.  It also supports more than two linked together in the same fashion.

Mike

Got it all going in Cab-1, and features are there.  A friend let me know those features won’t work in TMCC TR mode.  Also got it working with Bluetooth!  Awesome!  Everything is on the way with which to update Legacy.  Thanks for the brainstorming.  These new engines come with a learning curve, I guess.