Skip to main content

I need some assistance/input regarding re-addressing engines.  I will attempt to layout what I have done and  what occurred as best as possible, my apologies if the logic gets a bit skewed.

1.  Engines had been re-addressed some time ago to the 50- XX slots, want to get them into the 1 - XX slots, not important why.  All slots up to 50 are empty and have been since the original re-address exercise.  Did this when TIU and remote software was at 4.0, and possibly lower, level.  Just upgraded to v5.0 software in the last couple of weeks.

2.  Deleted all engines from all remotes with the intent to re-enter them one at a time in the order I want them to appear in the engine list.

3.  Using only one remote to re-enter engines (will copy the first remote into other remotes when re-address task is done).  Upon re-enter of the first engine , it came up with the old address.  Engine started up fine.  Re-addressed the engine to address 1 and started up fine.  Powered down the TIU, then powered it back up.  Tried to start up engine from address 1 and got error message that engine not on track.  Out of 9 engines, this happened with all but the engine I changed to address 5.

4,  Deleted all engines from remote, re-entered all and the old address came up again.  Figured the TIU might have a memory for addresses so I did a factory reset of the TIU and repeated the above steps with the same result.

5.  Deleted all but one engine from remote.  Just did a factory reset of the one remaining engine, deleted engine from remote, did factory reset of TIU then re-entered engine and it came up with the old address.

Am I doing something wrong, or missing something?

Any help will be much appreciated.

Dave

 

Original Post

Replies sorted oldest to newest

First, you need good track signal where you are doing this. PS2 engines should be charged and PS3 need to sit on powered track for a little while before attempting the change.

 I find the remote will just re-add an engine with the address it had, if that's open. So a manual change of address is needed or a factory reset of the engine to clear that address.

 Now, you state you did a factory reset and yet it still stuck. So there must be something wrong. I would bet you have weak signal or some communication issue?

I would suggest doing this on a test track set up just for this operation.

What model TIU are you using? what are you powering the track with? Have you done a signal test?

  4,  Deleted all engines from remote, re-entered all and the old address came up again.  Figured the TIU might have a memory for addresses so I did a factory reset of the TIU and repeated the above steps with the same result.

 

 Your problems are mostly battery related....

A good battery is required  to  change the engine's ID number with the edit address command.  On shut down .. If the battery is low the engine reverts back to it's old ID created when the battery was up to par.

Engine IDs stick with the engine unless edited. factory reset or ID is taken with another engine when adding.

I would start with one engine. Add it to the remote, edit the address to what ever you want, shut off track power for a few seconds. Restore track power  and then try and start the engine....  If  you can start the engine with the new address you should be fine.

Here's a pretty easy battery test,,, Start up the engine and then cut track power. Sounds should continue on for at least 6 or 7 seconds. If not the battery needs replacing or charging  and the engine will not accept any changes.

 One thing about proto-2, engines will run in command mode with a weak battery and unless we want to change a setting we don't know the battery is weak.( outside of the engine dropping into neutral at the slightest power interruption)

 

Last edited by Gregg

Engineer Joe/Gregg,

Thanks for the input.  I think I will try this again using a short test track I have rather than do it on the layout.  And you could be right about the batteries, although I did do a mass re-charge exercise within the past year and each of the engines do get run at least a couple times a month for a few hours. 

I just did a whole layout signal test with my current TIU (rev H.2 software 5.0) a couple of days ago and everything was fine.  Power is Z4000.

I'll post the results using a short test track later.

Dave,

Deleted all engines from remote, re-entered all and the old address came up again.

That's because deleting an engine doesn't change its internal DCS ID# (engine #).

Figured the TIU might have a memory for addresses so I did a factory reset of the TIU and repeated the above steps with the same result.

That's because resetting the TIU also doesn't change the DCS ID# of any engines.

 think I will try this again using a short test track I have rather than do it on the layout

That will yield the exact same result. Instead of doing that again, follow Gregg's instructions above.


DCS Book CoverThis and a whole lot more is all in “The DCS Companion 3rd Edition!"

This book is available from many fine OGR advertisers and forum sponsors, or as an eBook or a printed book at OGR’s web store!

Short test track did not help, most likely because of low battery.  The sound test for the one engine  yielded sounds staying on for no more than 4 seconds, so the battery is charging now.  Another engine that did retain the new address from the prior work has sounds staying on in excess of 6 seconds.

Looks like you guys nailed it.  I'll report tomorrow on how the re-charging works on the other engine.

Thanks to all for you input!

Dave

This would also be a good time to add the engine to the second remote since you deleted all the engines in it.(need to use a programming track)  This will verify the new ID took.

After editing the address with the first remote to whatever you want,  the engine should now add to the second remote with the same ID number.

 RJR is  pulling his hair.... Save to computer and then  duplicate.

Greg.

Exactly!  I am pulling my hair too!  Why not download first remote and copy into 2nd and 3rd remotes?  I assume this would be a quicker route, are there potential issues?

Engine still charging, wish I trusted my spare batts, but they probably aren't up to snuff either.  Tomorrow will be interesting for me.  All the batts are at least 8 years old (based on when I did the PS2 conversions) and purposefully re-charged at least 3 times since then.

QUESTION:  Would this have been a problem if I had BCRs instead of batts?

Dave

Milwaukee Road Dave posted:

Greg.

Exactly!  I am pulling my hair too!  Why not download first remote and copy into 2nd and 3rd remotes?  I assume this would be a quicker route, are there potential issues?

Engine still charging, wish I trusted my spare batts, but they probably aren't up to snuff either.  Tomorrow will be interesting for me.  All the batts are at least 8 years old (based on when I did the PS2 conversions) and purposefully re-charged at least 3 times since then.

QUESTION:  Would this have been a problem if I had BCRs instead of batts?

Dave

Saving to the computer is probably the easiest , . however adding to the second remote verifies the new ID took..

We have 8 remotes and line them up in a row  and  start adding  engines making sure the same  engine ID shows up in each remote. ( PS we have a programming track)

 WE're slowly replacing our batteries with BCRs.. I don't think you would have had this  problem with a BCR.

Add Reply

Post
The DCS Forum is sponsored by

OGR Publishing, Inc., 1310 Eastside Centre Ct, Suite 6, Mountain Home, AR 72653
800-980-OGRR (6477)
www.ogaugerr.com

×
×
×
×
Link copied to your clipboard.
×
×