How to program Lionel AA E8 both powered

How about the Lionel product number?  Issues sometimes come up with early Legacy MU configurations, but later A-A units were actually made to run with a single ID, no need to program them as an MU.  It depends on what you have.

Well he says they have Bluetooth so I suspect they are pretty new but you are right a product number is always the first thing that should be posted.

Considering BT, they may run just programming them the same number, my newer stuff does.

Sorry should have gave the number but not sure what it is. They are the custom run Amtrak from mr muffin.   So we can use this one from Lionel same run. 2033340 Which is the Amtrak version.

well when I programmed just the front one the rear wasn’t moving under its own power.  But maybe when I program them, both need to be on the program switch? But I was afraid it would make the second one run forward which it is backwards.

Program one, then the other, different id's.  Then build them as A train.  With the proper direction for each loco entered

Both need to have the PGM / RUN switch in PGM when changing the IDs.  You can do one at a time or since they are getting the same ID you can do them together.  Since these are newer AA sets they are factory programmed to operate together using the same ID.  The rear facing unit will run in reverse.  If you want to prove this leave them uncoupled and assign them the same ID.  Start them out and the second unit should run in reverse.

@Sparty1225 posted:

What is the proper way to program the AA E8 both powered?  If I use Bluetooth they act as one unit with the trail unit know to run backwards.  

Do I give them both their own id in the legacy system and then create a lash up?  However I did try that but I could get the trailing unit to program.  

thanks for the help.

Both units should have a program switch.  Switch to program and follow the standard setup as you would for a single unit.  Turn both switches to run and you should be okay.  

Roger that. Thank you all. I will put them both in program and assign one Id.  I will give that a try

@MartyE posted:

Both need to have the PGM / RUN switch in PGM when changing the IDs.  You can do one at a time or since they are getting the same ID you can do them together.  Since these are newer AA sets they are factory programmed to operate together using the same ID.  The rear facing unit will run in reverse.  If you want to prove this leave them uncoupled and assign them the same ID.  Start them out and the second unit should run in reverse.

Yep, all the recent ones I've seen have been configured this way, makes it easy to configure them.

More detailed programming available from this document.   Starts: Page22, Advanced operating techniques.  Most of this has not changed, even with the Legacy upgrades. The Complete guide to Command Control was part of the original Cab1/Command base sets.

The above mention control, limits coupler use and lighting sequence. Idea is:  A combination of engines/locomotives assigned a TR (train) number operates as a unit, front coupler/rear coupler funtional, all other couplers do not function once the consist is established.

There is programming for:

(1.) Lead engine facing forward

(2.) Middle engines facing either way

(3.) Tail engine facing forward or backward.

@Mike CT posted:

More detailed programming available from this document.   Starts: Page22, Advanced operating techniques.  Most of this has not changed, even with the Legacy upgrades. The Complete guide to Command Control was part of the original Cab1/Command base sets.

Well, it's a buttload easier with Legacy, not to mention that the recent sets are designed to run properly without configuring for an MU, certainly simpler than configuring an MU.

@gunrunnerjohn posted:

Well, it's a buttload easier with Legacy, not to mention that the recent sets are designed to run properly without configuring for an MU, certainly simpler than configuring an MU.

Apparently Lionel figured-out that most in the hobby had problems reading________ their pretty good instruction.  IMO.  Mike CT.

Applies either way you program a consist.   Assigning a Train to (TR 0)  clears all consist programming.

Deleted and reprogrammed with both on The track with program switches on. Both now move together.  But now my sensor track won’t upload the data when it rolls over.  Tried another locomotive and it programmed fine but didn’t upload. Hmmm?  Green light comes one sensor track. Could it just be dirty, first though but haven’t gone back out to look, or something I changed on the legacy remote?  

If two different locomotives don't get sensed, I suspect you have a configuration issue with the LCS sensor track.

Thank you gunrunner, I’ll investigate.

Sparty:   Ref "Deleted and reprogrammed with both on The track with program switches on. Both now move together.  But now my sensor track won’t upload the data when it rolls over. "

A bit ago I had a couple of engines that my sensor track wouldn't upload engine data when rolled over.  I had previously programmed/numbered a different engine with that ID.  Then I opted to use that engine ID for a new engine ... just wanted to change the ID scheme I was using.  Anyway, I then placed a new Command engine on my track; programmed it to the same ID; placed pgm/run switch back to run and rolled the engine over my LCS sensor ... no upload joy.  Was able to manually enter the engine data via CAB2, but was puzzled as to why the data didn't automatically upload via LCS sensor.

Some weeks later, upon further prodding around trying to figure out the "why", I discovered that the original engine was still included in my Legacy System Utility engine data that I could view on my computer.  Apparently the LCS sensor "knew" I had another engine with the same engine ID thus did not upload the new engine data.  Do I understand why overwriting the new engine ID via CAB2 was not enough?  No. I suspect that there is a procedure to do via CAB2 that deletes discarded engine data/ID.  However, I don't know what that procedure is.  

Anyway, wound up deleting the offending "old" engines in my Legacy System Utility on my computer.  Then I programed the new engines via my CAB2; and voila, they then uploaded their engine data upon rolling over my LCS sensor track.

Don't know if you have Legacy System Utility loaded on your PC.   Might give this approach a try if you do.

Regards,

Tom

Thank you Tom .  I was thinking you were for sure onto something.  Before trying your suggestion  I came across this and tried this first and phew, loaded on the remote!  I must have sat on the remote haha or did it on accident.  I have read the manual for the legacy controller but with working on the layout I use it only hear and there and forget more than I remember about it haha. Thank you all for the help