DCS Setup Help

Have you tried tethering the remote to the TIU via a handset cord?  If that works either the TIU or Handset RF board could be loose.

I haven't tried connecting the two, I give it a try.

While you there hit the "read"  . You should get the message tiu  #1 found. This sounds more like  tiu remote communications as Marty mentioned.

I connected the remote to the tiu and was able to get 2 of the ps3 engines programmed. But on the other ps3 and the ps2 I get a "TIU ERROR" or "No engine to add" on the remote. 

Any ideas?

jlm1973,

    You may have a low battery in your P2 engine, if it does not hold charge, replace it with a BCR, the P3 should program thru if your other P3 engines have programed.  You may have something wrong with your P3, maybe Guns or GGG will give you a hand with that.

PCRR/Dave

 

One thing I notice was the two that didn't program made noises when I put power to them while the two that programmed didn't.  Don't know if that makes a difference but thought I'd add that information.

Thanks for everyone's help.

James

Definitely sounds like you have a loose transceiver board in the remote or tiu if you have to tether the 2 together. (probably the remote, it gets moved around and naturally is a lot harder to take apart )  Hope you're trying to add each engine with no other engines on the track anywhere. (they should be on dead track if left on the layout) TIU error ?? cycle tiu power a couple of times.

I have power through the TIU to the track

 

Do you mean that you are using the FIXED 1 circuit?  If not, you MUST power the TIU itself through the AUX post, using a 12-18 volt wall wart or similar power supply.  When properly powered, a LED lights inside the TIU, in the corner near the VARIABLE 1 input.

 

when I power up you can hear the locomotive go into DCS mode.

How do you know which mode it is in?  The sounds are the same whether in conventional or DCS mode.  On my layout, I set the conventional volume pots higher, so I can tell from the volume.  Turning on the power with no DCS signal on the tracks will cause a conventional sound.

 

First thanks for everyone's input.  

 

Here is an update of what I have done so far and what has worked or hasn't worked.

 

1. I added a cable between the remote and the TIU and this took care of the RF issue.  From this I removed the cover of the TIU to see of the RF board had come loose.  This board was securely in place.  Based on this it has to be in the board in the remote.  Are there any suggestions on how to get the remote apart to check the board.  I'm thinking I might take it to my local hobby shop and see if it will communicate with the TIU on their layout confirm before breaking open the remote.

 

2.  I've been able to program two of my rs3 locomotives with no issues.  I have deleted each and reprogrammed them a number of times to make sure it was a fluke.

 

3.  I've tried multiple times to program another rs3 engine and an rs2.  I let the rs2 engine charge for 10 minutes and then tried to program it with no luck.  I plan to replace the battery with a BRC and try again.   The message I consistently get with both engines is "engine not found".  I'm also temped to take both of these engines to my local shop and have them try them on their layout just for confirmation.

 

4. I'm doing this all on a short test track instead of the layout.  

 

That is what I have for now if anyone has some additional suggestions or comments I greatly appreciate them.

 

James

 

 

Don't want to be picky but Fixed 2 is a straight through connection that will allow power to the track but not turn the tiu on. You must use fixed 1 or an aux power supply to turn the tiu "on".

 

Since all you hear is a click when power is first applied  with the problem engines ... That's a good thing. It means they're seeing the dcs watch dog signal ( you

must be using fixed 1) 

 

So you still  have 1 proto 2 and 1 proto3 that don't t want to add.  I might reset the remote and start over with the  problem engines, This will clear any ID  conflicts, One engine on the track at a time.  good luck

 

We know the Tiu and Remote aren't communicating with each other unless tethered.

 

 You may want to do a DCS track signal test on each channel to determine what else (if anything) is wrong with the thing. A engine" ADD" requires a pretty good track signal .Yeah I know you can add some engines but not others. If you need a hand let us know.

.

Try loading the trouble engines on a specific Programming track.

Just a 30" piece of track connected to Fixed out #1 all by itself.

 

And IF you don't have Barry's book, Get it.

Everything anyone knows about DCS is in there somewhere.

I'm getting things figured out.  Tonight I opened up the remote and reset the rf board, now the remote works.  I also ran a check on the signal and it is between 3 and 5, this is on the 40" test track and the layout.  Tomorrow i'll make some good wire leads with good crimped on connectors and rewire the TIU, track and transformer connections.  Also Barry's book showed up today and just skimming through it I'be learn a few things to try. I feel like I see light at the end of the tunnel.

 

Again thanks for everyone's help.

 

James

jlm1973,

    I do believe now that you have Barry's book you will figure out the DCS a little easier, I also suggest you purchase the OGR Video Guide to DCS, if you are a visual learning type person, it really is a good educational tool also.  Especially for someone just getting started with DCS.

PCRR/Dave

 

A dcs  track signal between 3 &5 on a 40 inch piece of track is not a  good thing.

 

It could be a dirty track ,engine pickups.  or a faulty TIU... Take a look on the bottom of the tiu. There was a bad batch of tiu around 2008 that put out a low dcs signal... If your Tiu is I3A it could be one of them. .  Hope not.

this is on the 40" test track and the layout.

Try disconnecting the layout from the TIU while using the test track.  I assume the test track is apart from the layout.

jlm,

   Gregg & RJR are giving you good advise you want a 10 track signal as much as you can get it, isolate your programming track away from your main layout, and program only having one engine at a time on the programming track, for best results.

PCRR/Dave