F3-SF#22 AA + F3B SuperBass - Building A Train - 6-85186+85190

Looks good to me.  The "signals" and "crew" switches on the B-unit turn off the horn/bell and crewtalk sounds, respectively.  But that doesn't matter if you're running command control, as those won't play unless you use Trainlink to reference the B-unit.  Most of these only really apply to conventional operation.

I'm pretty sure these are made to run under a single ID for all 3 units.  The switches then allow you to disable couplers and sounds as needed.  You can still create a MU (lashup) if you want but you will save TMCC IDs if they are all the same.

@MartyE posted:

I'm pretty sure these are made to run under a single ID for all 3 units.  The switches then allow you to disable couplers and sounds as needed.  You can still create a MU (lashup) if you want but you will save TMCC IDs if they are all the same.

@MartyE

I made a lashup with 3 IDs, so you say I can put all 3 units in only one ID? Or did I get it wrong?

I put each unit in different ID, ID22 = A Powered, ID23 = B Superbass and ID24 = A No Powered
This uses too many IDs from the legacy system I think!

Thank you,

@Leandro Garcia posted:

@MartyE

I made a lashup with 3 IDs, so you say I can put all 3 units in only one ID? Or did I get it wrong?

I put each unit in different ID, ID22 = A Powered, ID23 = B Superbass and ID24 = A No Powered
This uses too many IDs from the legacy system I think!

Thank you,

I have this same set.  I'd have to double check but I believe I am only using 1 ID for all 3.  Easiest way to check is to assign the 2 A units the same ID and don't couple them together.  One will respond in the forward direction, the other in reverse.

Edit... I confirmed via my iCab app that ENG 3 in my base is currently supporting the A-B-A SF set.

@Leandro Garcia posted:

@MartyE

I made a lashup with 3 IDs, so you say I can put all 3 units in only one ID? Or did I get it wrong?

I put each unit in different ID, ID22 = A Powered, ID23 = B Superbass and ID24 = A No Powered
This uses too many IDs from the legacy system I think!

Thank you,

If you look up the manual on Lionel's website for that set, it describes two ways of doing it.  Assign all three the same ID #, or assign each a separate ID and link together using the "TR" train function.  The manual recommends assigning each a separate ID for the most control and features, but says using just one ID number is an option to save ID space on your remote.

The controls for couplers, signals, and crewtalk only come into play when running conventional or when assigning all the same ID #.

So in the end, you're doing it right (the same way I do it on my layout), but there are other options as well.

@Catonsville Central Railway posted:

If you look up the manual on Lionel's website for that set, it describes two ways of doing it.  Assign all three the same ID #, or assign each a separate ID and link together using the "TR" train function.  The manual recommends assigning each a separate ID for the most control and features, but says using just one ID number is an option to save ID space on your remote.

The controls for couplers, signals, and crewtalk only come into play when running conventional or when assigning all the same ID #.

So in the end, you're doing it right (the same way I do it on my layout), but there are other options as well.

@Catonsville Central Railway,

Woody, exactly!

I found it very interesting to use only one ID, because today I have few locomotives still, but each one already uses an ID, in my new purchases in York, PA last month for the three new trainsets that are using 8 new IDs, so I think I will do a test using only one ID.

Thanks a lot for the tips.

My remote is filling up.  When the single ID is an option I'm using it and putting those switches under the hatch to work.

@MartyE posted:

My remote is filling up.  When the single ID is an option I'm using it and putting those switches under the hatch to work.

Honestly, as my collection grows, that option is looking more tempting...may have to experiment