Error Message in DCS mode..

Correction: I hit "add" not start up.... the error message comes up...not picking up my engine. I dont even get to start up....

I tried 2 different engines....

First you must add the engine to the system. Not sure what you have. If you can be more specific, then the help will be a little better.

First thing I would check is to make sure the engine and tender are connected properly - sometimes the pin isn't seated corrected.   Then make sure you have the DCS system connected correctly.  

One quick question---have you already added engines prior to this one and if so did you set up any lash-ups?  If so, there is a bug which sometimes occurs - just edit your lashups to assign them a a higher number - say in the 60s or 70s.

--Greg

Gents-

I cant add the engine to the system... when I press "ADD" it says error. So I am stuck on phase one here. Its brand new so I have never had any other engine stored in the system.

Thanks

Steve

I have a brand new MTH EP-5 Electric engine . I also have a 2882 Mallet. I have not used the Mallet yet. I tried a simialr engine to the EP-5 and that got an error message as well. So I know its the system set up not the engines..

Greg-

When you say to have the DCS connected correctly...what do you mean? I think I do.

Try presssing the "READ" button on your remote to see if it's even picking up the TIU signal. If it does not read the TIU, read this thread as I had a similar problem awhile back:

 https://ogrforum.com/d...948#9173459973933948

I've had occasional setup problems with DCS too but they always turned out to be connection or track problems:

1.  Make sure that the track section the engine is on when you try to add it is very clean; trying to add or even address an engine already in the system when it's sitting on dirty or defective track can be a nightmare.

2.  Make sure that power from the transformer is connected to the TIU through the correct inputs and outputs - fixed not variable.

3.  You might need to try connecting the handset to the TIU via a telephone cord rather than relying on the wireless connection.

4.  Check which version of DCS the handset is - the splash screen should show if it's version 4 or something earlier.

5.  If all else fails, hope that the author of the DCS Bible, Barry B., sees this post or try putting it on the DCS Control System Forum.

I have the base system not the remote. I will try your suggestions!!  Thanks!

I'm not that experienced with the system that you seem to have, but I believe there is a restriction on the engine ID that this slimmed down system will work with.

I see you say the engines are new out of the box(at least eh EP-5), but are you sure there is no chance they have been on another railroad with a full DCS system where their ID could have been changed from the factory default state at some point in the past?

-Dave

The engine is new out of the box....

Sorry, I was editing while you responded.  I see the EP-5 was listed as new.

As to the system itself, do you mean the DCS Commander(50-1028 or 50-1029, depending on whether you bought it with power supply or without)?  Or maybe the DCS Remote Commander (50-1033, which is the small remote with a Infra-red receiver that hooks into the track)?

Dave-

Yes. I bought the DCS Commander...with the power supply. So I am running it off the power suppy it came with....

Dave,

As to the system itself, do you mean the DCS Commander(50-1028 or 50-1029, depending on whether you bought it with power supply or without)?  Or maybe the DCS Remote Commander (50-1033, which is the small remote with a Infra-red receiver that hooks into the track)?

Since he's getting an error message (it would be good to know what the message actually is), he must be using the DCS Commander.

What, exactly, is the error message?

Check if either engine has a DCC/DCS switch and make sure that it's set for DCS.

This and a whole lot more is all in "The DCS O Gauge Companion 2nd Edition", now available for purchase as an eBook or a printed book from MTH's web store site! Click on the link below to go to MTH's web page for the book!

Yes Barry, I am using the Commander. Only a Err comes up and that is it.

H Steve.

I also have the DCS Commander.  When I first set it up I attached the two track power leads to the output on the back of the Commander, and tried to add my first ever locomotive.

Error.  Error.  Error.

After several tries at adding the engine I reversed the two output wires on the Commander.

Everything worked.

Why?  Don't know.

Rick

Hi Rick, going to try that now....thanks. Hope thats what it is!! We will see....

Thanks Todd.

Tried it Rick, no go. Very frustrating tosay the least.

Steve

Sorry about that swing and a miss.  Have you tried following the directions for both a "feature" reset followed by a "factory" reset for the engine?  Also try the "system" reset for the commander itself.  System reset is the choice for the commander itself.

They all involve the same use of the rest button on the commander.  the difference is the number of times that you are depressing the reset button to page thru these three choices.  

Rick

Check if either engine has a DCC/DCS switch and make sure that it's set for DCS.

 

This and a whole lot more is all in "The DCS O Gauge Companion 2nd Edition", now available for purchase as an eBook or a printed book from MTH's web store site! Click on the link below to go to MTH's web page for the book!

 

http://www.mthtrains.com/content/60-1279

 

Thank you Barry.... gonna check that on engine.... also will be purchasing the book. 

Hi Polarxpress3,

Of the engines you have tried, which are SP2 and which are PS3?

Have you tried running any of the engines in conventional mode with the DCS Commander?  If not, press the "CONV" button and give it a try.  When the display switches to showing conventional DC voltage, scroll down to 0.0 and let everything sit for a good 10 seconds.  Then scroll up to 9.0 volts.  If it's a PS2 engine you should get sounds and lights right away.  If it's a PS3 engine you should get sounds and lights in about 7 seconds.  Give that a try and report back.

Dave-

Just did that...got a bell and lights but train does not move...

OOPS!  My goof.  Call that a brain f@rt on my part as I was about to go outside to clean up some leaves.

Assuming that your engines are ps2 with the 3-volt board (we need the model number of both engines) this sounds light a weak battery. I had this problem years ago when I first started using the DCS commander. You need to let the batteries charge over night. Even if the engines are new the commander to me seems to be very picky at finding engines with weak batteries. Also what kind of track system are you using, If you haven't done so already set up a test track. One pieces of 30in track hooked up to the dcs commander by itself and see if it can find the engine. 

Hi Polarxpress,

Just did that...got a bell and lights but train does not move...

Given your answer, we really do need to know what engines you're working with to advise you further.  PS2 and PS3 engines can have different causes for this behavior.  There's also a difference between how older (5 volt) and newer (3 volt) PS2's behave on DC track power.  Please post the item numbers for your engines and we should be able to point you in the right direction.

Dave-

Have you tried this yet?  Hooking the DCS up to a test track will certainly help in your troubleshooting.

Dave,

After several tries at adding the engine I reversed the two output wires on the Commander.

 

Everything worked.

  

Why?

Because DCS PS2 engines require the DC + on the center rail and the DC - on the outer rails in order to see DCS commands. If the DCS Commander instruction manual fails to state this, it's most likely because the DCS Commander is intended to be used with MTH HO PS3 engines, and PS3 engines don't have this requirement.

Your problem now appears to be solved, correct?

I also tried that Barry with no success. Frustrating to say the least. The engine will not even run in convential mode via the DCS commander. I have it attracted to the brick it came with. On the commander it says "HO" so Barry I tried what you just said and it still did not work.

You say you have a new MTH EP-5 eletric engine, ok we need to know the model number for that engine. It should be a 6 digit number with 2 dashes something like 20-2197-1 or 20-5531-1. The reason is there are older ep-5 eletric engines that will not run with the DCS Commander. The number should be on the side of the box. the other way is to check the charging port on the bottom of the engine if the port rectangular shape with 2 small pins. then the engine should work. if it is a circle shape with one pin in the middle (just like the jack on the back of the commander) then that engine will not work with the commander.

It's number 20-2195-1

This is a PS1 engine and does not have the ability to run in command control.  PS1 was a sound system only

20-2195-1 is listed as a 1999 release.  I don't believe DCS was available then - if the box says "ProtoSounds" and has a QSI logo, then the locomotive didn't come with DCS.

This engine is from 1999 and will not run on the commander

that engine is a "protosounds" engine, which is now referred to as "ps1".  Ps1 engines are not command control engines, they run like the old lionel engines you may remember, with a transformer.  You need to get engines that are protosounds2 (aka ps2) or protosounds3 ( ps3) engines to use your command controller.  Ps2 is command control and ps3 is just a newer version.