This one baffles me -

Delete it from remote B and add it back again making sure it has the same ID number. I've run across this type of thing  before and have no idea why it happens. Yes I know it doesn't make sense. (operating in super mode)

I'd be tempted to do a factory reset on the engine from one remote, then delete it's instance from the other remote.  After that, add it back to each remote and see what you get.

I tried the easy way first.

I deleted the engine from the remote that could not access it (Remote-B), and then added a new MTH engine. Unfortunately, it added an engine that was on the track and which it already had, but gave it a new (and different) address number. The engine had an address of 19, and Remote-B added it with address 10. So I deleted the engine with address 10 as 19 is the proper address.

Now to do it the proper way.

I turned off all the sidings and spurs with MTH engines on them, and left on only the engine that I had just deleted and needed to add, the SD9043MAC. Remote-B found it, told me to CHECK TRACK, but added the engine with address 12, which is the same address it had before I deleted it, and the same address as for Remote-A.

Everything works fine now, except it still takes a few seconds after the engine starts for it to recognize or accept commands such as speed up (move), and the whistle (Horn). After 10 seconds or so, everything works fine, and both remotes can now access this engine.

THANK YOU for your help!

Alex

I don't believe the remote addresses have any effect, all mine are #1.

Alex   50 lashes.... You know better to try and add with other engines powered up. Anyway glad to hear it's fixed. BTW I have heard of the occasional  slow delay from my friend with the large super mode layout.( running 4.3)

The read may change the engine/tiu association but I don't think it can change an engine  ID .

my 2 identical loaded remotes use same engine ID address for a particular engine or MU.The last remote used is what the engine sees.

The engine ID and the remote ID are two different things.

The engine # in ALL remotes has to be the same or the engine won't be found by the remote with the incorrect engine #.

John wrote:

The engine # in ALL remotes has to be the same or the engine won't be found by the remote with the incorrect engine #.

Correct. When I record a Record & Playback session, I use both remotes, mostly one remote for the engines, and the other for the switch-tracks. Occasionally, though, I want two engines operating at the same time, and I will used both remotes interchangeably to control the engines. When I started doing this, I was a bit apprehensive; but after many such sessions I realized that it works just great.

Thanks!

Alex

Gregg,

The read may change the engine/tiu association but I don't think it can change an engine  ID .

Correct.

Alex,

   One final thought on your problem, I know this is simple but if your P2 Engine batteries are old replace them, either with a new Battery or a BCR.  Way back before I changed over to BCR's I had a similar problem to what you are having, after getting rid of the old Batteries everything went back to normal.  Even if your old Battery seem to be fine, which mine seemed to be, replace the very old Engine Battery, and see what happens.

PCRR/Dave

When I open a PS/1 or 5V PS/2 locomotive and see one of the old white or silver MTH batteries, that's the first thing that hits the trash!  I don't see any point in "testing" it as they are way beyond their useful life span.  A ten or more year old NiCad is past due for replacement.