How Many Locomotives Can Be Programmed Into a TMCC And/Or Legacy Remote And Other Programming Questions

98 locomotives, typically.  Lionel says not to use ID #0, and id #99 is the generic "run everything" ID for Legacy.

The locomotive data is stored in the command base, and only one command base for a layout, so all the remotes will see the same locomotives.

Like John says, if you use a Legacy base, any CAB-2 handheld that connects to it will show the same locomotives, as the information is stored in the base.  If you use TMCC and a CAB-1 or Legacy lite and CAB-1L, then no info is stored in the bases.  In all TMCC and Legacy locomotives their ID is stored int he locomotive, so you can have as many locomotives you want with the same ID, just as long as they aren't on the track at the same time.  If they are on the track at the same time, they'll both respond, no matter what the display of the CAB-2 remote says.  As clear as mud yet?

You can, in Legacy, easily have multiple databases stored on a PC.  These can be downloaded to the base fairly quickly using LSU software and WiFi.  I do it quite a bit when doing demos.  I load my demo database when taking my base on the road and then reload my home database when I come back.  Not quite "on the fly" but I can manage more stored engines than the system allows.

A big advantage to this is when I have a group over.  When they add to my database, I can revert back to where it was before they came over.

gunrunnerjohn posted:

98 locomotives, typically.  Lionel says not to use ID #0, and id #99 is the generic "run everything" ID for Legacy.

The locomotive data is stored in the command base, and only one command base for a layout, so all the remotes will see the same locomotives.

 

That's what I thought, thank you.

sinclair posted:

Like John says, if you use a Legacy base, any CAB-2 handheld that connects to it will show the same locomotives, as the information is stored in the base.  If you use TMCC and a CAB-1 or Legacy lite and CAB-1L, then no info is stored in the bases.  In all TMCC and Legacy locomotives their ID is stored int he locomotive, so you can have as many locomotives you want with the same ID, just as long as they aren't on the track at the same time.  If they are on the track at the same time, they'll both respond, no matter what the display of the CAB-2 remote says.  As clear as mud yet?

I would say so. Thank you very much for the info. I currently own a CAB-2 but never really looked into a CAB-1L. May look into it at some point to have as a backup plan. I am no where near having enough engines to occupy an entire CAB-2 remote just yet but hey, might as well plan ahead just incase that day ever comes.

MartyE posted:

You can, in Legacy, easily have multiple databases stored on a PC.  These can be downloaded to the base fairly quickly using LSU software and WiFi.  I do it quite a bit when doing demos.  I load my demo database when taking my base on the road and then reload my home database when I come back.  Not quite "on the fly" but I can manage more stored engines than the system allows.

A big advantage to this is when I have a group over.  When they add to my database, I can revert back to where it was before they came over.

Huh, never heard of someone ever doing that before. That's pretty neat!

I have been goofing around with my Legacy Remote and skimming through the Manual a bit today and discovered a sorta loophole. The Legacy System has Nine Different "Channels" so if at for example a Train Show, there was two Lionel Legacy equipped layouts nearby, one layout could be on Channel 1 and the other could be on Channel 2 to avoid any interference from one another (It's on Pages 56 & 57 of the Manual). I did an experiment were I programmed an engine on Channel 1, to Address 1. I then switched my Base and Cab-2 Remote to Channel 2 and Address 1's data was empty! I then went back to Channel 1, the data in Address 1 still appeared to be there.

Now obviously, if you go and program a new Address 1 on Channel 2, the Address 1 from Channel 1 is probably going to respond to your commands if it's still on the layout and being powered.

Now obviously, it would get kinda of obnoxious switching from channel to channel but, that's one to do it I suppose. 

I suspect that the data is there.  If what you said were correct, every time you changed channels you'd have to re-load all the information into the base again.  Changing the channel does not give you access to 98 more database entries.  I've had to change channels and my data was always there just as on the previous channel.  Can't say what you saw but my experiences are definitely different.

I've changed the channels on my Legacy set several times and never lost data, it's always there showing the same locomotives no matter the channel.

Hmm, I guess I was wrong then. I tried it again and it shows the same data no matter the channel. My mistake, sorry!

RailwayMan47 posted:

Hmm, I guess I was wrong then. I tried it again and it shows the same data no matter the channel. My mistake, sorry!

No need to apologize... you could have discovered something.  Never hurts to put it out there.

What do you do when you have more than 98 in Legacy.  Between engines, cranes and others I am close to running out of numbers.  

That's kinda why I made this thread, so I can plan ahead in case that day ever comes.

That's why I read this thread!!!  

rboatertoo posted:

That's why I read this thread!!!  

See my first post.  IMO that is probably one of the easier solutions.  I would suspect that you would never have them all on the layout at once and with a little management could use alternated saved databases to work this.  Is it perfect, no.  It's a solution though.

The other solution would be to have your modules on hand and load as you go and manage duplicate addresses.

Do newer Legacy engines still include modules, or do you have to get one of those LCS Sensor Tracks to program it?

RailwayMan47 posted:

Do newer Legacy engines still include modules, or do you have to get one of those LCS Sensor Tracks to program it?

Seems to be hit or miss.  My VL GG-1 had one but the shays did not.  All the info can be entered manually as well but the module or sensor track is the easiest method.