Skip to main content

Replies sorted oldest to newest

I have a similar situation in that the old laptop with serial port and WIN98SE won't find the port.  Suggestions included dump my laptop and buy a newer one so I can use the MTH loader.

So I'm "stuck" on 4.3 and going to stay there I guess unless there is a magic bullet I can shoot to continue to use the ThinkPad to load MTH software.

Last attempt it did find the port to download the 4.3 update to the TIU but after that no other function would find it.

Tried all the suggestions from Barry et al and nothing else has worked since the one TIU upgrade load.

Only thing left to do was clone some remotes using the backup remote feature.  And that was a bomb after hours of fiddling with it.

So I'm at the point where 4.3 is working okay and I'll deal with the synchronizing of the remotes at some point.

Better projects to spend my limited time on than chasing MTH Loader software problems.

Last edited by Kerrigan

From a previous post on the same subject...

 

Before doing anything else, read the following.

 

Make sure that the jumper cable is a stereo cable and that you insert it before powering up the TIU. Note that connecting the USB cable supplies the TIU with enough power to do the upgrade.

 

Do the following:

  • Remove all cables from the TIU
  • Connect only the USB cable and wait a few seconds until the TIU's red LED stops blinking and comes on solid
  • Click on the OPTIONS tab at the top of the Loader Program's screen and select SEARCH FOR TIU
  • Press Start

If the TIU is not found, there's most likely an issue with your computer/Windows.

 

If the TIU is found, proceed as follows:

  • Disconnect everything from the TIU
  • Plug in a stereo 1/8" cable between the TIU's ProtoCast and ProtoDispatch ports
  • Connect the USB cable and ensure that the red LED comes on steady right away without any blinking first
  • Click on the icon to upgrade TIU software and press START.

If all goes well, disconnect the jumper cable and the USB cable

  • Connect the TIU to the remote with a4-conductor telephone handset cable
  • Connect the USB cable
  • Click on the icon to upgrade the remote software
  • Press START.

 

This and a whole lot more is all inMTH’s “The DCS Companion 3rd Edition", available for purchase from many fine OGR advertisers and forum sponsors, or as an eBook or a printed book at MTH's web store!

Last edited by Barry Broskowitz

So I'm having the same issue. I followed Barry's instructions on how to search for the TIU. It could not find the TIU so it's apparently a computer or Windows issue. So what do I have to do with the computer to get this to work? I'm running Windows 8.1.

 

Also, my USB to serial cable says it is compatible up to Windows Vista. This is the cable I used in the past for DCS updates. I tried updating the driver but it said the most up to date one was loaded.

Last edited by NJCJOE

I would suggest reloading the driver while the cable is attached to the computer and then check under devices to see if it is working correctly.

 

I would also suggest to check the small screws that hold the external cable to the RS232 port on the TIU since mine had backed out just enough to prevent a solid connection which killed communications.

I was trying to use the loader which came for 4.3 ... still mucking around with it.
Just completely puzzled why I was able to update both TIUs and 3 remotes to 4.3 successfully a couple of months ago with the WIN98SE machine and now I can't get it to find the TIU to do a remote backup and clone.
Baffled.
It is interesting flailing around trying to get it all to do what it's already done once ... lol!
 
Originally Posted by Barry Broskowitz:

Kerrigan,

 

It's possible that Win98se is just too old to support some function that the latest Loader Program 5.0 requires.

 

I'm running on a 3 year old Toshiba "budget" PC with Windows 7 Home Edition and all works well. It also seems to be faster than previous versions.

 

Last edited by Kerrigan

I may have figured out my issue. I think the problem was with my USB  to serial cable. I kept getting a message on the COM port that said "Device can not start (code 10)". So I tried it on my computer at work and got the same message. I then rebooted the computer with the cable connected and now it is working properly. I will try updating the DCS system again at home by trying the same thing with the cable. Hopefully that will take care of it.

My TIU and Remote upgraded to 5.0 without problems. Rev L TIU and Win 7 computer.

 

I have 3 computers, Microsoft upgraded two of them to Win 10 already and for some reason the one I use for my DCS and Legacy updates keeps saying it will let me know when the Win 10 upgrade is ready. It is an older PC, may not be fully compatible with Win 10? Anyway, guess I lucked out there? Or maybe MS is doing me a favor so I can keep my train stuff updated?

I have the old tiu with serial port. The instructions are for Tiu with usb so they don't include instructions specifically when to power the tiu from the fixed in 1 port. I too manually installed Windows 7 driver for use-serial adapter. Just once it said it found the tiu port but then never again. If you have more specific instructions for my specific setup that may help.   

Originally Posted by timbernme:

I have the old tiu with serial port. The instructions are for Tiu with usb so they don't include instructions specifically when to power the tiu from the fixed in 1 port. I too manually installed Windows 7 driver for use-serial adapter. Just once it said it found the tiu port but then never again. If you have more specific instructions for my specific setup that may help.   

You're right the new loader doesn't mention the straight RS232 cable however it's mentioned  below  copied from MTH's site.

Anyway  powering up would be step 6.

 

DCS Consumer Loader Program - Version 5.00

What’s New in version 5.00?

 

This latest version of the DCS Consumer Loader software is used to program the DCS system components (Remote, TIU), Load sound files (in Proto-Sound 2.0 and 3.0 locomotives) and backup and restore the DCS Remote handheld. To review the many changes to the loader, clickHERE and below.

  • Configures TIU when loading DCS Software Version 5.0 to function with the DCS Wi-Fi Interface Unit (WIU)
  • Increased wait time on power cycle after loading Consume Package File. This accommodates the changed method of relaying information back to the user from the engine. The engines now use a Morse code audio response to indicate lading of software rather than lights. This is due to the software that supports Proto 3/2 engines
  • Re-enabled Get Sound File From Engine. This can take in excess of an hour for the large PS3 sound files
  • Added compatibility check for PS2 5V files attempting to be loaded into PS3 engines. The Loader no longer allows this due to major differences in the 5V sound files compared to the PS3 memory structure
  • Increased reliability on Original HO PS3 Steam sound file loading
  • Loads Code Chain Files (DSP Firmware, FPGA, CV Data). This is the zip file that allows any Proto-Sound 3.0 locomotive (except existing HO steam engines) to be updated to run expanded DCC features.
  • Removed the Get Sound File From Engine icon. Previously this function of the Loader allowed users to retrieve a copy of the sound file from their engines. This proved to be very time consuming for customers. All of the latest sound files can be obtained from our website atwww.mthtrains.com
  • The Loader now remembers the last folder you explored to. This is especially handy if you keep all your MTH files in the same folder (for example, the MY MTH Files folder that gets created when you install the Loader program.
  • Improves the sound file and code chain file loading by automatically adjusting the data rate for files that contain more than 50% zeros. The progress sub-bar will turn yellow to indicate a temporary data rate adjustment. Previously the Loader would try at the highest data rate, determine that an error occurred in the data transfer, then try the whole sector over again. In essence, the Loader is now much, much faster.
  • Improved communication to support USB-to-Serial adapters.
  • Improved speed.
  • Improved error recovery (that means you can retry mid-stream on a sound file load without having to restart everything from the beginning).
  • Runs on Windows XP/Vista/Windows 7/Windows 8/Windows 10
  • Enhanced display features show DSP Code version (Service Center/Dealer Loader only), Sound file size (1MB/2MB), Engine Type (5V/3V/HO), Engine Board Memory Size (1MB/2MB), and Engine Address

     

    You'll find complete instructions for installing and using the DCS Consumer Loader by clicking Here.

    NOTE: Please uninstall any previous versions of the Consumer Loader prior to installing Version 5.0.

    WARNING: 2.20, 2.30, 2.34 and 5.00 are the ONLY DCS Consumer Loader software versions you can use to program Proto-Sound 3.0 Locomotives. Using any previous version of the DCS Consumer Loader to program a Proto-Sound 3.0 equipped locomotive willdisable the Proto-Sound 3.0 electronics and require the locomotive be returned to M.T.H. for repair. You can learn more about the issues with this warning by clicking HERE.

    In addition, if you plan on operating your layout with the DCS Wi-Fi Interface Unit (WIU) and DCS App, you must reprogram your TIU with DCS Software Version 5.0 USING DCS Consumer Loader Version 5.00.

    To Use This Loader You Will Need:

    - A standard RS 232 cable, USB-Serial adapter, or a type A-B USB (for Rev L TIU only) cable which you can obtain from any computer or office supply store. - A STEREO mini-to-mini 1/8” audio cable available from MTH or many electronic stores like Radio Shack, Best Buy, etc. - An AC or DC Transformer. Z1000 bricks are the most versatile to use. - A PC running at least Windows XP. Mac users may find that running a Windows emulator might work.

    The below information details how the cables are to be used.

    Cable Types

    Reprogramming The Remote  In order to reprogram the remote, a tether cable that connects the remote to the TIU is required. The tether cable MUST be a 4-conductor handset cord from any standard telephone. This is the cable that connects the handset to the base of the phone. Radio Shack and other electronic or phone stores sell these. The cable MUST BE 4 CONDUCTORS on both ends.

    Reprogramming The TIU  In order to reprogram the TIU, a standard RS 232 cable is required. This cable is to be connected between the TIU's PC Connection Port and a COM port on a PC. If your computer does not have a 9 pin RS232 Com port, but only USB ports, purchase/install a single 9 pin Serial port I/O card, SIIG model 16550 for desktop computers or SIIG model JJ-PCM012 for laptop computers. SIIG models have been verified, equivalent manufacturers single port card may be acceptable.

    The updated Loader program also will support USB-Serial adapters from most manufacturers.

    For those users that own the Rev L TIU’s (released in December 2010) you can use a type A-B USB cable. This cable will also supply power to the TIU’s processor so that you don’t heave to bring along a transformer to power the TIU when you load TIU or Remote code. NOTE – The USB cable does NOT supply power to ANY of the TIU’s outputs.

    The mini-to-mini cable MUST BE A STEREO model. You MUST NOT use any cables that have adapters. M.T.H. p/n 50-1009 or Radio Shack p/n 42-2497 are acceptable models.

    Making Cable Connections Follow the instructions below for hooking up the cables. The DCS Loader Program will prompt you step-by-step for each of the loading options as you select them.

    TIU (Remote Input) Ensure the 4 conductors in the bottom of the Remote are all parallel and NOT touching one another. IF they do when you go to load the remote code your remote will power on.

    TIU (Proto-Cast and Proto-Dispatch Audio Jacks)

    The Stereo mini-to-mini cable should be fully plugged into the Proto-Dispatch and Proto-Cast audio jacks on the TIU. When power is applied to the TIU, look at the red LED. It should NOT blink or flicker at all. It MUST remain on constant. This indicates that the TIU is in Program Mode. If the LED blinks then it means your mini-to-mini cable is not stereo, you have some other adapters on the cable, or you do not have the cable plugged in fully at one or both of the jacks.

    NOTE: When loading the remote code and prompted by the Loader program to hold down the power button on the remote, you should notice that your remote LCD remains blank. Your remote should not power up. If it does check the handset cord cable to ensure it has 4 conductors or inspect the jacks on the TIU and the remote to ensure no pins are touching or bent over. Also, you must remove the mini-to-mini audio cable PRIOR TO loading the remote code. You must also be sure to remove power from the TIU AFTER you have loaded TIU code.

I continue to be plagued by this problem.  Have over the weeks tried new versons of loader, software, operating system(s), PCs, and two different laptops .. one with an old OS and one with WIN98SE ... and a PC with WINDOWS 7  ... and it's still hit and miss with mostly misses trying to find the port.

If it's a download of new version to the TIU, mostly works okay.

If it's trying to get a remote to backup, almost never works.

FINALLY after a heck of a lot of messing around, both here at at a friends' layout, got 4.3 loaded on everything.  Still can't "clone a remote" but at least the **** thing finally works overall.

At this point I'd say I'm through with updating DCS, and just give up on cloning remotes.

Hopefully.

It was a huge PIA, even with Barry's old and new DCS Companions.

Just a PIA ....

I have gotten that error when I tried to update my TIU even after I got an connection on that USB port. I just had to change to a different USB port every time I connected to the TIU. So I updated the TIU then when I went to update the remote I got no TIU on port error so I changed to a another USB port and it worked, when I updated the next remote I got the same error and had to change to a different USB port. Very odd but not a big enough deal for me to figure out the issue

Way too complicated for something children, or an "average person", are able to master and enjoy.  Maybe the package warning on DCS should be "For Computer Experienced Adults Only!"
 
Originally Posted by Matt Makens:

I have gotten that error when I tried to update my TIU even after I got an connection on that USB port. I just had to change to a different USB port every time I connected to the TIU. So I updated the TIU then when I went to update the remote I got no TIU on port error so I changed to a another USB port and it worked, when I updated the next remote I got the same error and had to change to a different USB port. Very odd but not a big enough deal for me to figure out the issue

 

Last edited by Kerrigan
Matt Makens posted:

I have gotten that error when I tried to update my TIU even after I got an connection on that USB port. I just had to change to a different USB port every time I connected to the TIU. So I updated the TIU then when I went to update the remote I got no TIU on port error so I changed to a another USB port and it worked, when I updated the next remote I got the same error and had to change to a different USB port. Very odd but not a big enough deal for me to figure out the issue

How do you force your PC to assign a different port? I'm at a lost on how to do that ... maybe my WIN7 or WIN98SE machines won't allow manual reassignment, or perhaps I've just not had enough coffee to figure it out?

The drivers for the USB<->Serial adapter should either be supplied with the adapter or included with Windows.  If you look in Device Manager (Open Settings, type Device Manager into the search), look under Ports (COM & LPT) and see if they're listed.  If not, there's likely a device that is flagged as having no drivers.  Here's an example in Windows 10.

Attachments

Images (1)
  • mceclip0

I also got the can't start (code 10) message under Windows 10 on several different laptops.  I found a solution in this blog entry:

http://leftbraintinkering.blog...fic-2303-device.html

If anyone who's reading this thread has tried all of the above and still no go, check to see if you're using a Prolific 2303 USB-to-serial cable.  I bought mine on eBay and the listing only said it was Windows compatible.  It didn't say it was only compatible with older Windows versions.  Apparently the chip used in the cable has reached end-of-life and Prolific has chosen not to support it under Windows 8 or 10.

I followed the steps in this blog entry to download an older driver version and install it.  This solved my problem, and my two-stage upgrade (from 4.3 to 5.0 and from 5.0 to 6.0) went fine.

I hope this helps.

Add Reply

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