Skip to main content

So I have had my DCS Commander for about a year and I bought it used. I recently bought a 3rd Proto 3.0 engine. When I added this engine it wasn't responding well, and I thought I had a defective engine. But then I removed each of my engines and they all had the same behavior. As I start the system up and switch to DCS they respond to the startup commands but when they begin to move they don't move forward cleanly and then after only moving about 12 inches they stop and perform their shutdown. My Lionchief that I have on the same track are running just fine. I have removed them as well but they all behave in the "correct" way. Is their a way to test a Commander? Is this a serviceable event?

Thank you.

Last edited by AtoZ Lewis
Original Post

Replies sorted oldest to newest

Hi Chessie, it's Fastrack. I have it setup with a star pattern from a main panel, which is where the Commander is connected. I do know that the Commander has a specific +/- side and I used a meter to confirm that the + is on my center rails. I read that somewhere when I was putting in my new layout and knew that I was going to start with a Commander. It's been fine until this week.

I was just reading in another thread about adding engines with no others on the track. That I was not aware of. Maybe I just need to reset my 3 PS3 trains?

Mike,

You need to reflect on the "intuitive" approach to problem solving, from page 152 of The DCS Companion 3rd Edition:

Intuitive Approach 

The intuitive approach makes the assumption that the problem has occurred due to some recent change in the train room. There are three questions that, if answered, will most likely yield the source of the problem. Using the intuitive approach can often quickly provide the answer to a troublesome problem. Even when the intuitive approach fails, it provides a thorough review and understanding of the problem. 

The first question is, "What changed prior to the problem occurring?" If things were working fine and now a problem has developed, there's a good chance that something that changed in the layout has caused the problem. It's a good idea to think back over any recent wiring or track changes that were made, or other changes that might have caused a problem. 

The second question to ask is, "What did I do prior to the problem occurring?" It's sometimes the case that something the operator did, perhaps unknowingly, caused the problem to occur. If the problem is an intermittent short circuit, perhaps adding a new passenger car with misaligned trucks is causing a problem when traversing a switch track. It may also be the case that, while modifying the track work a screw was dropped between the rails where the motion of a train is causing the screw to short circuit between control rails on an operating track. Again, a careful review of what transpired between the time that all was well and the current problem situation may yield the solution to the problem. 

The third question to ask is, "Has it happened before and what was the solution?" There are some things that, due to the layout construction habits of the individual operator, may cause the same problem to occur from time to time. If possible, keeping a log of problem symptoms and resolutions can save a lot of time if a problem reoccurs.


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!

GGG awhile back i had my mth gp35 would go 2 to 3 feet shut down and then took my williams engine run fine on the track and was not stopping so found out the straight pieces of track was not making good connection so i bent my center pins and also check wire on track and changed ends and i have not had anymore trouble with mine.Thats why i mentioned what i did to mike but i know everybody has different issues.    

Thanks to all. What it seems to be is a combination of items. Two main items seem to have caused the issue. First I don't think the Commander properly rostered the most recent engine. Then I believe I had some dust / spider webs on the track as well. Here is how I tracked it down.

I took out the Commander and it's power supply and substituted with a CW-80 I had around. I ran my LC+ trains around and discovered a distinct stopping point. While I appreciated Chessie's suggestion, I really didn't want to unscrew, lift up and disconnect my track. Also the point where the trains were stopping wasn't near where the trains were balking and stopping. I used my usual alcohol based wiping cloths to clean the track. As I said above I really only seemed like some spider webs and I could see some dust collected on them. I do need to invest some time / money into a track cleaning car.

OK, that problem solved, I put the Commander back on the track with the 100w supply. I ran it in convention mode, powered it up to full and again successfully ran the LC+. Then I re-rostered each of the PS3 engines and ran them 1 at a time. When done everything is running again and the combination of PS3 and LC+ is working as well.

Thank you everyone for your help.

Add Reply

Post
The DCS Forum is sponsored by
×
×
×
×
Link copied to your clipboard.
×
×