Skip to main content

OK, this is the first DCS problem in 15 yrs that I couldn't solve myself or with the help of Barry's book.

 

What is happening is that I have around 15 engines on my second remote and was trying to add 2 more. They are PS2 3v engines, one diesel and one steam. Both engines added and would run normally under DCS using the hand held remote. When I turned the power of and tried to run the engines again using the START button I would get the messages CHECK TRACK and ENGINE NOT FOUND. The engines would show on the display but didn't seem to be in the system. I did an engine reset and factory reset on each but to no avail. When I deleted the engines and added them again, they would run with all features until I turned the remote or the power off, then CHECK TRACK and ENGINE NOT FOUND messages would come on again. The other 15 engines would operate normally even after power down and restart, the problem occurred with the last two I added. I changed the batteries in the remote and checked to make sure that the RC board was secure. So, I suspect that there is something wrong with the remote or the TIU in recording or saving the engine but not sure how to check this. I read the troubleshooting pages in the DCS O Gauge Companion but couldn't seem to find a solution to this problem. Suggestions?

 

Mike

Original Post

Replies sorted oldest to newest

Mike,

 

These are classic symptoms of a weak battery. Charge each engine's battery until it can pass the following "test":

  • Start an engine up either conventionally or under DCS
  • Without pressing Shut Down, immediately turn off track power
  • If the engine sounds do not persist for at least 6-7 seconds after track power is turned off, charge the engine's battery until it does.

If charging the battery doesn't make sounds continue for 6-7 seconds, replace the battery with a new, fully-charged one.

 

Then, delete each engine and re-add it.

 

This and a whole lot more is all in MTH’s “The DCS O Gauge Companion 2nd Edition", available for purchase as an eBook or a printed book at MTH's web store!

Last edited by Barry Broskowitz

If you don't have new batteries handy put them on charge for about 2hr Then try it again. 

 

Next thing you might do is to insure that the other engines are either not on the track or power is cut to those sections.

 

Also if your handy pull the shell off and make sure that the screws holding the wires on the third rail pick up are tight and also make sure the wires leading out of the connectors on the board itself are not lose.

 

If the wiring is real tight. you might want to cut the zip ties and loosen them up a bit so there is more play and there not being pulled out of the connectors.

 

G  From phone call earlier. It was a bad motor in the smoke unit. pluged a known good smoke unit in and no issues. Engine was new.

Thanks Barry & GGG, it was the batteries, I recharged both and one was OK and the other wasn't but still showed 8 volts after charging. It was 10 yrs old so I guess it wasn't working, maybe someone can explain why it was showing 8 volts on the meter but didn't have enough power to save the data. I replaced it with a BCR and it works fine.

 

One issue related to a comment suzukovich made, the steam engine was running fine but when I turned on the smoke it would shut down. I suspect as he mentioned that the smoke unit motor is seized and is causing an overload/ short as I can't hear or feel air from the fan.

 

One comment for Barry, I looked through your DCS Companion under "Error Messages" pg 148 for "Engine Not on Track" message and didn't find anything re the battery, after a subsequent search today I found it on pages 159-162, "Battery Related Problems". In neither case was there a BAT message on the remote to steer me in that direction although it was clearly a battery problem. I might suggest that in subsequent updates to the "Companion" that you might indicate in the battery section that "Check Track" and "Engine Not On Track" messages on the remote on power up could be indicators of a low battery. Also in the section "Engine Not On Track" (pg 148 )indicate that this message could be indicative of a low battery as the engine data might not have been saved. Just a suggestion but I was unaware that the battery powers the save function on power down. Like others, I didn't read the Companion from cover to cover, only the sections that apply when I have a problem.

 

Anyway, Barry thanks for the "Companion" and the tremendous after publication support that you provide here.

 

Mike

Last edited by MohawkMike

Mike,

maybe someone can explain why it was showing 8 volts on the meter but didn't have enough power to save the data.

That's because you cannot accurately measure the strength of a battery except when it's under a load, which a meter typically doesn't do. A battery tester would have shown you that the battery was truly weak. All the meter does read is the battery's surface charge.

In neither case was there a BAT message on the remote to steer me in that direction although it was clearly a battery problem. I might suggest that in subsequent updates to the "Companion" that you might indicate in the battery section that "Check Track" and "Engine Not On Track" messages on the remote on power up could be indicators of a low battery

That's because a BAT message is indicative of low batteries in the remote, not in an engine.

Also in the section "Engine Not On Track" (pg 148 )indicate that this message could be indicative of a low battery as the engine data might not have been saved

Unfortunately, that's a symptom of the remote not finding an engine. A low battery isn't the typical reason for this message. Rather than clutter the book with every conceivable reason that the message could be generated, I set up a separate section for "Battery Related Problems".

 

You received the message because, when you added the engine the first time, the battery was too weak to save the engine's new DCS ID#. This caused the remote to, in effect, search for an engine that was' present, under the DCS ID# where the remote last found it.

 

Last edited by Barry Broskowitz

Mike, I was very happy using batteries for years, until in the last year I increased my loco stable to 25, which means they sit for long periods.  I've been replacing the 2.4 volt batteries with Digikey 2.5F supercapacitors, which are priced so as to make the switch cost effective, and to date have been quite pleased. 

I have three PS3.0 engines that I can add engine individually and run individually without any problems using my DCS remote handheld.
The problem is running a lash-up. I can successfully create a lash-up, add the engines to the lash-up, and name the lash-up. When I press startup, I get a "Check Track Engine Not on Track" error message.
My current version is 6.10 which is the latest software.
@pdash posted:
I have three PS3.0 engines that I can add engine individually and run individually without any problems using my DCS remote handheld.
The problem is running a lash-up. I can successfully create a lash-up, add the engines to the lash-up, and name the lash-up. When I press startup, I get a "Check Track Engine Not on Track" error message.
My current version is 6.10 which is the latest software.

Just to be sure in this process- when building the lashup- all 3 engines were on the same track and powered at the same time as creating the lashup?

You tried deleting the lashup and rebuilding it?- again, with all 3 engines on the track and powered up during the operation?

Just to be sure in this process- when building the lashup- all 3 engines were on the same track and powered at the same time as creating the lashup?

You tried deleting the lashup and rebuilding it?- again, with all 3 engines on the track and powered up during the operation?

Correct! Both PS3.0 engines are on Track 1. Again, each engine runs fine as single units.

I took your advice and restarted the process all over...

I placed both engines on the same track, powered up throttle to 18v, created lashup, added engines, and gave the lashup a name. As soon as I press startup, I get the Check Track No Engine On Track error message.

While this doesn’t solve your problem with a lashup. Your engines run fine individually. Just curious what happens if you tried to run them using the ALL Feature on the same section of track.
I’m reaching here.  Where DCS requires 2 way communication. If your signal strength is low in spots. Does the more things you throw at in ways of engines have an effect. One engine may get by. But multiples maybe not. If it can’t find one engine in the lashup. Doesn’t the  whole lashup go down with an error message.

@Dave_C posted:

While this doesn’t solve your problem with a lashup. Your engines run fine individually. Just curious what happens if you tried to run them using the ALL Feature on the same section of track.
I’m reaching here.  Where DCS requires 2 way communication. If your signal strength is low in spots. Does the more things you throw at in ways of engines have an effect. One engine may get by. But multiples maybe not. If it can’t find one engine in the lashup. Doesn’t the  whole lashup go down with an error message.

Please give me instructions on how to use the All feature. I assume it is a pseudo lashup feature. How does it work?

Currently, I have deleted my lash-up and pulled my engines from the inactive list to the active list. Right now, I have 2 PS3.0 engines on the same track which is Track 1.

@pdash posted:

Please give me instructions on how to use the All feature. I assume it is a pseudo lashup feature. How does it work?

https://www.mthtrains.com/site...niques_Article_7.pdf

"the ALL Engines feature makes all active PS2 (and PS3) engines run at the same speed and respond to the same commands — speed changes, direction, bell, whistle, etc. — at the same time"

Last edited by Vernon Barry

https://www.mthtrains.com/site...niques_Article_7.pdf

"the ALL Engines feature makes all active PS2 (and PS3) engines run at the same speed and respond to the same commands — speed changes, direction, bell, whistle, etc. — at the same time"

Eureka! The All operation mode works!!! It's like a poor man's lash-up.

Now, it got me more curious as to why my lash-up build does not run. Is it weak batteries or a weak TIU signal. My TIU is operating in passive mode. So, there is no power pack for the TIU.

I still have no answer. My point of trying the All feature was just to see if your system the way it’s setup could handle 2 or 3 engines all receiving commands at the same time.
When you tried to start up the lashup and you got the No Engine on Track message. Was there a consist of lighted passenger cars coupled to the engines or a caboose or in the same block ?  Some lighted cars are known to degrade the track signal as well as a few cabooses.
It’s been a long time since I created lashup with DCS. From what I remember it was pretty straight forward. So it seems you’ve done it correctly. You mentioned you have 3 engines. Can you try putting 2 of them in a lashup and place the 3rd one in the same block. If you get the error message and no start up on the lashup. Can you start up the 3rd engine on it’s own and do a signal test.

Add Reply

Post
The DCS Forum is sponsored by

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

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