Skip to main content

Hi Everybody,

Here is a strange situation/problem that most of you will not believe... This is why I will try to give extended context and details first.  Here we go.... 

Here is the context:

At our club, we have a large layout with the main line separated in 16 center-rail isolated blocks powered by 4x TIUs (Rev L.) [50-1003] in Super TIU mode with all channels in FIX mode.   (4 TIUs X 4 Channels = 16 Blocks).  All outside rails (ground) are connected together.

These 4 TIUs are powered by 5x Z-4000  [40-4000] connected to 5x Remote Commander Receivers [40-4002] allowing easy power-up and power-down of the full layout with the Z4K Tracks feature of the DCS Remote [50-1002].  The TIU #1 is powered by two Z-4000, and the TIUs #2,3,4 are each one powered by one Z-4000.

The Z4K Tracks setup to control all 5x Remote Commander Receivers and Z-4000 is based on the method "Using More Than 3 Z-4000s With Z4K Tracks" described in the book "DCS O Gauge Companion 3rd Edition" at page 101, or in the book "DCS O Gauge Companion 2nd Edition" at page 98.

This setup has been used without any issue under DCS4.3 until very recently.

Here is the strange problem:

With any PS3 engine on the track (and we have tried more than 4 different ones so far), if we do actions like "read" or "add MTH Engine" or simply "move an engine from the inactive list to the active list" on the DCS Remote, we very frequently lose power (Z-4000 going to 0 volt) on the left side of one or two Z-4000.  This seems to only occur with PS3 engine on the track.

It looks like the Remote Commander Receivers are somehow detecting "false short circuit", or are receiving a "false TZV command" [(TZV) = resets the track voltage to zero volts] when a PS3 engine receives a "read" or an "add MTH Engine" or simply a "move engine from inactive to active" with the effect of putting the Z-4000 to 0 Volts.

We have noticed this problem recently after upgrading our layout from DCS4.3 to DCS5.0, and decided to come back to DCS4.3, but with exactly the same strange problem.  (i.e. same problem with DCS4.3 and DCS5.0)

Here are the questions:

Have anybody experienced anything like this ?  (Remote Commander Receivers+Z-4000 going to 0 volt upon a "read" or "add" or "inactive-to-active")

Do you know how the Remote Commander Receivers are detecting short circuits ?  Are they often detecting "false short circuits" ? 

Do you know a way to determine if the trigger of the 0 Volt event is a "false TZV" or a "false short circuit" ?

Do you understand why this problem seems to be linked to actions on PS3 engines only ?  Are they acknowledging commands differently than PS2 ?

Thanks,
Daniel

Last edited by Daniel Auger
Original Post

Replies sorted oldest to newest

Daniel,

   Got to admit I have only 2 Z4K Transformers with the side receivers at this point, and I am running P2, have no P3 engines, and I have never experienced a problem like you have described, with any of my P2 Engines on the Track.   This may very well have to due with your P3 at 4.3 and above.  I hope Barry sees your post and can shed some light on how to correct your problem.  Marty F & GGG also.  I will be very interested in their insights into this problem for sure.

PCRR/Dave

Last edited by Pine Creek Railroad

Daniel,

Have anybody experienced anything like this ?

Yes, frequently in the past.

I very, very rarely do a READ (I like all my engines in the Active List). However, I've seen this occur infrequently when doing an ADD ENGINE. There seems to be no distinction between a PS2 or PS3 engine as regards which is being added. I've never seen this happen when moving an engine between the Active and Inactive engine lists, in either direction. I operate exclusively in Super TIU mode.

I've discussed this a few times with MTH R&D and I've learned that what appears to happen is that, during the ADD process, one of the commands  that's issued is very similar to the command to set a Z4K Track to zero volts, as if a TZV soft key is pressed for a Z4K Track. It's not at all an imaginary short circuit, since there's no wait time for the Z4K Track to accept a power-up command, as there would be if it had to reset itself after a short circuit.

I've only rarely heard of this occurring on layouts other than my own. I've just learned to live with it, since it's a very infrequent occurrence.

What I can recommend is that you see if there's any one place where this occurs more frequently on your club layout, and verify signal strength at that location, as well as checking that track for any wiring anomalies.

Since this started occurring after you upgraded to DCS 5.0 yet continued after downgrading to DCS 4.3, I'd be suspicious of something having occurred when you removed the TIU's from the layout, either with the TIUs and/or their wiring. Also, you possibly could have floated a transceiver out of its socket through rough handling. I would also suggest a Feature Reset of the TIUs and reloading DCS 5.0, since DCS 4.3 had a really ugly Super mode bug that affected 1 of every 8 TIUs, causing them to lose DCS communications on a random channel.

Last edited by Barry Broskowitz

Daniel,  Dave and Barry,

Thank you for creating and commenting on this thread.  I have often experienced this problem with the Z4000 on my test bench.  This has occurred with both PS2 and PS3 engines and with both DCS 4.31 and DCS 5.0.  I have only the one Z4000 w/ Z4000 Receiver, which as stated before is on my bench I use for my MTH repairs.  I have adopted Barry's solution - "I've just learned to live with it, since it's a very infrequent occurrence."  If anyone has another solution,  I would like to hear about it.

Jim Osborne
MTH Service Technicain
DCS Beta Tester
Reader of "The DCS Companion 3rd Edition"
Member TCA, TTOS, NMRA. LRRC, MTHRRC. AGTTA, San Diego 3 Railers and OGR Forum

 

 

 

Barry and Jim,

Thank you for sharing your similar experience.  That is really good to know.

Now, at least, we know in which direction to look:  i.e. TVZ/TZV "noise".  (Both TVZ and TZV are mentioned in Barry`s book.  Just a typo, right ?)

In our experience, it is always the left side of the Z-4000 going to 0 Volt.  The right side of the Z-4000 stays OK with its set voltage. 

Is your experience the same ?  i.e. Only the left side going to 0 volt ? 

Thanks to all who replied to my post.

Daniel

P.S. There is obviously something or a condition that amplifies this TVZ/TZV "noise" problem... and we will try to find out what it is... and let everyone knows, of course, if we find out !

Daniel,

Just a typo, right ?

Correct. It's on the "pending corrections list".

Do you know if that TVZ/TZV "noise" is produced by the DCS Remote or by the TIU ?

That's a very imprecise statement.

First, it's not noise.

Second, it's a packet-level command, not a DCS (macro-level) command, that's being misinterpreted.

Third, it's the remote that's sending packet-level commands to the TIU, which are being picked up and erroneously interpreted by the Z4K Remote Commander receiver, that's attached to the Z4000.

Last edited by Barry Broskowitz
Pine Creek Railroad posted:

Barry,

   Yes for some reason I always go thru the Eng Button then start your sequence, just habit, I guess.   Never used the add button to add engines was my intended message.

PCRR/Dave

Are you talking about the add button being the thumbwheel? You have to use it to add an engine either way. There is no add button that I'm aware of.

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