How Old Is Your DCS System?

Have on original, and newer ones, works fine. Going to give it to a friend who needs one as soon a we locate the box for shipping it. Warned him about the lack of fuses and that it could use a software update.

 

Is it possible to still get the 4.2 ish version? Thought I had a copy but cannot locate it.

Litegide, re-entry of items was only needed after the upgrade from version 2 to version 3, because the location of much data was changed.  Not necessary on later upgrades.

 

What is a Rail KIng Barricade electronic controller?

Controller for the 30-11021 barricades. There is also a controller for the traffic lights.

(Was going to enter link but those buttons do not highlight on this 'puter.)

Sounds like a pretty bad experience with the service guy, but remember it may not be MTH's intent for that to happen, all companies have a character or two in their employment. And we all have bad days too, maybe he was having one? I usually try to give them the benefit of the doubt and at least one more chance. If it keeps up this way on the next attempt or two, then that's a whole different story. MTH has some good people, Midge has always done right by me the few times I have ordered parts. And the MTHRRC has also always treated me well. Fortunately, I have not needed any service on anything yet.

It looks like your remote is 3.0. I guess the question is.... What are you missing with a newer software version?    Not much , The double tap brake is a neat new  feature, I,m sure there are other features as well. If the layout is working I'd leave things as is. just my opinion.

 

If you upgrade from 3.0 to 4.3 I don't believe you lose anything but.... I'm not really sure.

I recently bought a used system. It has Rev13A on the bottom of the TIU. I opened it up and it has the 4 fuses for the channels, which I seem to remember reading somewhere, didn't appear until revision G. It has the serial port - not the  usb port. So, I'm not sure which revision I have.   Can anyone offer a suggestion?

 Version G was the "original TIU " from 2002. You're not going to like the next part.

 

Version I3A came out around 2008 and a number of them had serious dcs signal problems. They put a weak dcs signal.. Mth got a handle on this as quickly as possible and modified the tiu correcting the problem.  If your tiu has a silver dot beside the I3a it's  been modified and should be  good to go. If not you may run into problems..

 

If it were mine I would set up a small test track (one or 2 sections) and try adding a engine using fixed 1. If you get it  added , try a dcs track signal test.  Should be a perfect 10. 

Gregg,

What are you missing with a newer software version?    Not much

Are you kidding? There were a ton of features and fixes after 3.1!

 

Here's the list for just going from 4.2 to 4.3:

 

DCS 4.30 Software Upgrade Revision Available

March 26, 2014 - The latest version (4.30) of the software used in the DCS system includes several new features detailed below. The software can now be downloaded from the M.T.H. Proto-Sound 2.0 Website.

 

Because the memory assignments are dramatically different in software Versions 3.X and earlier, upgrading the code is required in both the remote and the TIU. The system will not function correctly if only one of the two components has been updated. In addition, if the remote and the TIU are currently running any version of 2.X DCS software, both must be reset using the appropriate System menu commands prior to uploading the Version 4.01 software into the remote and the TIU. By resetting both components, all previous information and settings (engines, accessories, switches, etc.) entered into the remote and TIU will be lost and must be reentered by the user after the software update has been completed. Users upgrading from 3.X and higher will not have to reset the remote and TIU prior to uploading the new 4.00 software.

There are two software files attached to the download. Both feature the same numeric code and should be used together (the appropriate file for the remote and TIU) when migrating from Version 3.X or earlier. 

The user MUST use the most recent DCS Loader Program, Version 2.20 to upload Version 4.30 into the TIU and Remote. Earlier versions of the DCS Loader Program prior to version 2.20 will not function with the Version 4.30 code.

 

Version 4.30 New Features

 

• The management of lashup settings has been completely rewritten to allow accurate and repeatable retention of settings. A new soft key, “FSV”, has been added as the first lashup soft key. This allows lashup settings to be changed and then retained from the time a lashup is created, through its operation, shutdown, and subsequent startups.
• When adding an engine that's already in the remote, the message "Engine in Remote" appears, the remote returns to the engine screen and displays the engine with which a conflict was found.
• A new TR screen soft key, “MSV”, allows setting a starting and ending voltage for "ALL TIU Tracks" just like individual TIU tracks. By default, "ALL TIU Tracks" start at 1 volt. Additionally, individual TIU tracks also start at 1. volt instead of the 5 volts as previously. This allows for more effective conventional engine control layout-wide. 
• A new TR screen soft key, “MSV”, allows setting a starting and ending voltage for "ALL Z4K Tracks" just like individual Z4K tracks. By default, "ALL Z4K Tracks" start at 5 volts, witch is the lowest voltage available from a Z4000 transformer. This allows for more effective conventional engine control layout-wide.
• The following lists now also support direct access to entries by keying the item’s 1, 2 or 3-digit DCS ID#: TR List, Track Setup Edit/Delete, Accessory Setup Edit/Delete and Switch Setup Edit/Delete. 

 

Version 4.30 Fixes

 

• Previously, if a PS2 or PS3 engine, when operating in a Super TIU environment, is made Inactive and is then attempted to be made Active, it would not come out of the Inactive Engine list unless it was on a track connected to the TIU with which it was last associated. The workarounds were either to perform a READ; delete and re-add the engine; or physically move the engine to a track connected to its associated TIU.  This issue has been corrected. The engine now is able to be moved out of the Inactive Engine List and also to be made active.
• Previously, ”ENGINE ERROR" would result when attempting to add an engine that had the same DCS ID# as a lashup that was already in the remote. This issue has been corrected. The engine now is able to be successfully added to the DCS Remote.
• Previously, when operating in a Super TIU environment, increasing or decreasing speed by turning the thumbwheel faster than very slowly could cause speed to go change in the wrong direction or not at all.  This issue has been very much improved.
• Previously, the time that “Out of Range” and “Engine Not On Track” messages were displayed was very long, as was the time that the remote locked-up while displaying these messages.  The time that these messages are displayed have been considerably shortened.
• Previously, when editing a scene’s accessories or changing a Scene’s name, one could not scroll to the second Scene to select it if there was more than 1 Scene in the remote. It was necessary to select the Scene by keying its DCS number in the Scene list.  This issue has been corrected. One may now successfully scroll to any item in the list of Scenes or, alternatively, still access an entry by keying its number in the list.
• Previously, if TIU #1 was in Super Mode, all TIUs were in Super Mode and if TIU #1 was in Normal Mode, all TIUs were in Normal Mode.  This issue has been corrected. Any engine that was added to a TIU that is placed into Super TIU mode will operate on all of the TIUs that are in the DCS Remote, regardless of whether a TIU is in Super TIU mode or Normal TIU mode. However, any engine that was added to a TIU that is not in Super TIU mode, will only operate on tracks connected to the TIU to which it was added.
• Previously, sometimes, when attempting to select the System menu, a different menu was selected instead.  This issue has been corrected.

As always, you'll find the 4.30 download FREE by clicking HERE.

 

I got my first set in 2008 or 2009 USED from the forum.

I believe it was at 3.2 rev software. It's now running fine with 4.2 in it.

 

I grabbed a Rev L system last spring on sale cheap at a show. It's still in the box awaiting my New Barn Layout work.

Thanks.  Since they're part of an accessory, no wonder I've not noticed them in an MTH catalog.

 

Barry, the years go by fast and minor items I forget.  Was the reset needed going freom 2 to 3 or 3 to 4?

 

Mike, Rev G was the first TIU.  It never had fuses.  USB port appeared on Rev L.  Versions are lettered alphabetically.

Robert,

 

A reset is only required when upgrading from DCS 2.x to any other release.

That's what I thought.  Somehow is misread your lengthy post. OAIH!

We bought the DCS system in 2004 with rev H TIU and the remote.  I have done all the revisions to 4.2 and nothing has been repaired on it yet, including the remote.  It has been a life saver for me as wiring in blocks conventionally was too much out of the question.  The fear of all that wiring has helped me be very kind to it all . 

 

So many good stories here   I suspect "pilot error", vice actual hardware issues, has a great deal to do with most of the problems we read about.