Skip to main content

Using a RailKing PRR E-6 w/Proto 3.0

When playing PFA - you can advance the sequence by tapping the current sound (like "Arrivals") - or hit cancel to exit PFA - but the final "Departure" sequence won't end when hitting cancel. I let it play a bit - and it did say "Close that up" or something - but never seemed to end. Only way to stop it was to shut down and restart the loco.

Also the hitting the coupler icon makes a sound - but the couplers do not fire.

Last edited by Former Member
Original Post

Replies sorted oldest to newest

Also the hitting the coupler icon makes a sound - but the couplers do not fire.

I can't speak to the issue with PFA (I'm waiting on my DCS Explorer), however, if the coupler firing sound happens and the coupler doesn't open, the problem is most likely with the engine, not the DCS Explorer.
The firing of the coupler and its sound are always linked in the engine. The only time both don't happen together in a correctly working engine is when you fire the rear coupler in a lashup. In that case, the normal response is a soundless coupler firing. The technical reason for that is that the accent sounds are turned off in a lashup's trailing unit.
I've never seen a case where an engine that's working properly will make the sound without firing the coupler. I'd look at the wire path, starting at the coupler wires and proceeding back to the electronics.
Alternatively, it might be a sound file/chain file issue.
Last edited by Barry Broskowitz
Barry Broskowitz posted:

Also the hitting the coupler icon makes a sound - but the couplers do not fire.

I can't speak to the issue with PFA (I'm waiting on my DCS Explorer), however, if the coupler firing sound happens and the coupler doesn't open, the problem is most likely with the engine, not the DCS Explorer.
The firing of the coupler and its sound are always linked in the engine. The only time both don't happen together in a correctly working engine is when you fire the rear coupler in a lashup. In that case, the normal response is a soundless coupler firing. The technical reason for that is that the accent sounds are turned off in a lashup's trailing unit.
I've never seen a case where an engine that's working properly will make the sound without firing the coupler. I'd look at the wire path, starting at the coupler wires and proceeding back to the electronics.
Alternatively, it might be a sound file/chain file issue.

Thanks Barry - This is a "new to me" loco - and the first time I've run it.

I just had the A Unit on the track - maybe I'll try it with the B unit connected.

Also - I notice my cab interior lights aren't working - wondering if someone had toggled these off with function buttons? - would they remain off under Explorer control? Same with couplers? 

 

A couple of things...

First, if the A unit I powered and the B unit is a dummy, they are intended to be tethered together when run, and the odds are good that only the front coupler on the A and the rear coupler on the B are actually operating couplers. The other two would be manual or dummy couplers. In this case, if the A was on the track alone and you fired its rear coupler, you would get only the sound. However, if you fire the front coupler, it should make siunds and also open.

Second, doing a Feature Reset should turn all lights and sounds back on (assuming that, like all DCS engines that I've encountered, these all default to "on"). To Feature Reset the A unit, make it the active engine, go to the Engine Settings Screen, scroll down to "RESET" at the bottom, and tap Engine Feature Reset.


DCS Book Cover

This and a whole lot more about DCS WiFi is all in MTH’s “The DCS WiFi Companion 1st Edition!"

This book is available from many fine OGR advertisers and forum sponsors, or as an eBook or a printed book at MTH's web store!

Get the free TMCC & Legacy Addendum here!

I tried the Engine Feature Reset - if it did anything - I could not tell. Wish that process had a confirmation screen - like "Engine Reset!" or something.

Although it did seem to reset the volume on the app - so I guess that meant it reset.

Still no lights and couplers - but I for now, and without another 3.0 loco to use -  this seems less DCS - more broken train.

I'll try to understand whats happening with the PFA a little better.

Roving Sign posted:

I tried the Engine Feature Reset - if it did anything - I could not tell. Wish that process had a confirmation screen - like "Engine Reset!" or something.

Although it did seem to reset the volume on the app - so I guess that meant it reset.

Still no lights and couplers - but I for now, and without another 3.0 loco to use -  this seems less DCS - more broken train.

I'll try to understand whats happening with the PFA a little better.

The PFA feature works the same in the Explorer as it does in the WIU.  In other words, all PFA operation is the same in the app regardless of hardware.  

Once you tap "Departure" the departure sound sequence is played, the bell comes on, and the engine accelerates to the speed set when entering PFA.

The PFA control screen doesn't disappear because departure sound sequences vary in length.  To close the PFA control screen, simply tap close.  Note, when you tap close, this also terminates PFA so, if you want to hear that last bell ding, wait until it stops before closing.

We didn't want to close the window while the engine is still in PFA since some users, especially beginners, will assume they can control the engine and it would not respond properly while still in PFA.  In the remote, you simply have to "know" you can't control the engine normally until after it exits PFA. 

I hope this helps.

So glad for this forum. Mine acted up like the original post for the first time. Never did that before. Would just reboot the unit and the light would change to purple. And as others have mentioned, reset button didn't solve the issue either (and yes I have the latest firmware).

So I did the "add engine" command as explained above and , ta-daa, light goes to purple and everything works.

My single biggest complaint with the DSCS explorer is the manual. It is woefully inadequate for first time users and yet they are including it in starter sets. (And double checked the version on the MTH site before posting this). Anyone else besides me see an issue there?  

No faster way to drive people away that to make it to difficult for them to solve what turns out to be a simple problem.

Having a well thought out troubleshooting section and a full explanation of the lights would be a decent start. Would only add one page at most to do so (might even only fill in the rest of the troubleshooting page). The manual does not mention ANY of the following

1. the 5 sec  blinking red with a short

2. forcing a signal to the track if the light is a steady red and all track problems have been sorted by using add engine

3. that a steady red light can also mean track power is off due to a safety trip,

4. that a reset will not always solve the track connection issue,

5. that NO connection to the track will also cause a red light. All they say is "overloaded track"

5.  the lights and sound on any locomotive will be off, even with power to the track until you start up the locomotive, (nice note for those going from conventional to DCS)

They assume everything will be hunky dory electrically and spend more time on the app and LuCi than helping the owner with any possible issue. I've heard about a supposed update to the pdf manual for over a year and . . . nothing. Seriously, this would be one of the easiest changes to make that would go a LONG way in having satisfied customers. Yet, MTH seems to not care.

It seems customer service / relations in the O gauge section of the industry by Lionel and MTH  has gone down the tubes in the last decade. Sad, as I've seen phenomenal service from other manufacturers in other scales.

Add Reply

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