Skip to main content

I've not run into this scenario before with any of my MTH DCS engines and I thought it best to reach out to the guru's of DCS on this forum to see what may be going on. I did a search on OGR to see if I could find an answer to this situation, but no luck. I did read the recent thread (6/20/24) posted by MissingMe&WV and that "Engine Not Found" scenario, I think, is different from what I have. So, here are the extensive details of my situation:

I have an MTH Premier AC6000 (#20-2266-1) PS-2 with a 5 volt board, (catalogued in 2000 Vol. 3), that has the correct BCR in it. I recently upgraded the speaker to a Lionel Fatboy speaker recommended by GunrunnerJohn (the sounds are great now!). I power my two-track main and layout with a Z4000 transformer and track 2 is powered by an MTH Z-1000 (in case I just want to run that track by itself without running Track 1). I have a TIU Rev. L hooked up. The remote has four Energizer Lithium Ion batteries, that are fully charged.

With the engine on the track, I power up to 16 volts to charge the BCR. I hear the "click" in the engine when power is applied. I wait a minute or so for the BCR to get charged. The engine is in the remote. I press "Start Up", and I get "Engine Not On Track". I press the soft key "SSU" (extended start-up) and get nothing.

I then go to "Menu" on the remote and "Delete" the engine. Then I go to "Add Engine / Add MTH Engine" and the engine is found.

I then hit "Start Up" and the engine sounds come on, however there are no lights, horn or bell. So I shut it down.

With the engine still on the track with power (16 volts), I go to "Menu / Advanced / Feature Reset". I select CSX AC6000 and then "Confirm". Engine is then "Reset".

I hit "Start Up" - Sounds, Lights, Horn, Bell, Cab Chatter, Ditch Lights, Smoke all work as they are supposed to. So, I run the train around the track for 15-20 minutes or so and then end the running session.

I come back to the engine the next day and I have to go through this entire process to get the engine to run. I just can't figure out why the "Feature Reset" does not "stay active" in the DCS system between running sessions for this engine. I should be able to power up the engine, let the BCR charge a minute, then hit "Start-Up or SSU" and have the engine come to life, like it should with all the bells and whistles (excuse the pun ). As a side note, is it possible the BCR has gone bad over the years? It was installed in January of 2017.

I have a few MTH PS2 5-volt and 3-volt engines and I don't have this problem with any of them. My PS3 MTH engines don't exhibit this problem either and all of these engines start up, run and work as they should over my entire layout.

So, any ideas or suggestions as to what may be going on here with this engine and how it can possibly be corrected would be appreciated?

Thank you!

Original Post

Replies sorted oldest to newest

Simple- it means that your battery subsystem- charging and more importantly, then using of the battery or super capacitor to keep the processor running when power dropped is not working as intended.

When you perform the add engine process- the new updated changed address of the engine is changed only in RAM in the engine system. It then requires the working battery subsystem to keep that processor powered- that memory powered, and then write that new updated address as the final shutdown when power is dropped.

Again, this is a well known condition or state and applies to both PS2 and PS3 engines. This is because again, if either charging or the circuit used to actually provide that stored power to the processor and memory are damaged- then proper shutdown does not happen- and the engine reverts to the OLD ID and address from the storage when it boots up again when track power is applied.

So, most basic of basic checks- when you power up the engine and sounds start- and then you cut all power to the track- do the sounds continue playing all the way through shutdown- or do they cut off abruptly shortly after power is dropped? That is one indicator of the battery system working or not working.

Hi Vernon,

Simple- it means that your battery subsystem- charging and more importantly, then using of the battery or super capacitor to keep the processor running when power dropped is not working as intended.

When you perform the add engine process- the new updated changed address of the engine is changed only in RAM in the engine system. It then requires the working battery subsystem to keep that processor powered- that memory powered, and then write that new updated address as the final shutdown when power is dropped.

Again, this is a well known condition or state and applies to both PS2 and PS3 engines. This is because again, if either charging or the circuit used to actually provide that stored power to the processor and memory are damaged- then proper shutdown does not happen- and the engine reverts to the OLD ID and address from the storage when it boots up again when track power is applied.

So, most basic of basic checks- when you power up the engine and sounds start- and then you cut all power to the track- do the sounds continue playing all the way through shutdown- or do they cut off abruptly shortly after power is dropped? That is one indicator of the battery system working or not working.

Thank you for the detailed response.

I took your suggestion and went through the start up process to get the engine up and running. I cut the power to the track by turning off the transformer. The sounds abruptly stopped after 3 seconds, as I was timing it on my watch. It definitely was not the long shutdown sounds one gets when hitting the "shutdown" button on the remote.

So, based on your last paragraph in your response, it looks like the battery system may not be working properly, correct?

@CSX Jim posted:

Hi Vernon,

Thank you for the detailed response.

I took your suggestion and went through the start up process to get the engine up and running. I cut the power to the track by turning off the transformer. The sounds abruptly stopped after 3 seconds, as I was timing it on my watch. It definitely was not the long shutdown sounds one gets when hitting the "shutdown" button on the remote.

So, based on your last paragraph in your response, it looks like the battery system may not be working properly, correct?

Yes, given both the sounds cut out what might be early and the fact you are experiencing the symptoms of not storing the address into permanent memory and thus having to add the engine each DCS running session.

Also, the reset where the engine might have previously been part of a lashup and thus lights off- but then that should have been saved and reset- but boots back up with the old setting. Yet another symptom of- the settings from RAM and the active processor session are not then stored into permanent memory and used for the next operating session.

@CSX Jim posted:

I have an MTH Premier AC6000 (#20-2266-1) PS-2 with a 5 volt board, (catalogued in 2000 Vol. 3), that has the correct BCR in it.

Could be the charging circuit not fully charging up the BCR or just not waiting long enough for it to charge. Or could be a defective BCR (super capacitors can fail and while it kinda sorta works and provided some power- not enough power to complete the critical tasks.

You can use a meter set to DC voltage- and measure the 9V style battery terminals of the BCR while plugged in and monitor the voltage of the actual BCR in-situ. This might help you diagnose.

While typing this- near my keyboard is a super capacitor bank that came out of a customer's genuine BCR that somehow died. It's rare, but not impossible.

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.
×
×