All I get is no serial port detected
Have tiu revision l
Usb to usb don't work
Usb to serial port don't work
Ahhhhhhh
|
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.
Yes, did all the steps following that thread; no joy
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.
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:
If the TIU is not found, there's most likely an issue with your computer/Windows.
If the TIU is found, proceed as follows:
If all goes well, disconnect the jumper cable and the USB cable
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!
Win98SE!!
That version of Windoze wasn't any good in 1998!
well I have windows 7 computer and windows 10 computer and have had no problem with either version on any version 5.0 MTH updates, the only thing I noticed with windows 10 was I had to update the serial device driver in windows then all worked fine!
Alan
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.
8.1 HAS A LOT OF issues I would upgrade to windows 10 mine works fine and use 5.0 MTH loader and have upgraded tiu remote and send and receive sound files to engines no problem!
Alan
check your email and give me a call
Alan
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.
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.
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?
Yup, all I had to do was reboot the computer with the USB to serial cable connected and it found the port with no problem. All updated.
Still no luck upgrading my remote. TIU is v5 though. I continue to get error messages about failing to find the port. Perhaps it's a bad phone cord?
Start over and follow the instructions exactly . Remove all the cables from the previous tiu upgrade and power down the tiu. good luck.
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.
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.
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.
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.
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'm not sure why you wouldn't load version 5. As a super mode runner it's really much better than 4.3. 4.2 was a disaster for super mode runners.(scrolling issues) I hate computers and if I can upgrade anyone can... Fortunately we only have to do it every 3 or 4 years,
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
Anybody who is still having a port recognition issue should plug the cable into their computer but not the TIU. Then reboot your computer. It worked for me finding the port on two different computers.
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
Flakey software and finicky if you ask me. I can't figure out why it finds the port to program the TIU but can't find the port to program the remote.
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?
I'm having a similar problem. I have a serial to USB cable, but when I connected to my Windows 10 PC it says there is no serial port. Do I need to manually or otherwise reassign one of the ports on the PC to act as a serial port and is additional software or Hardware required to do this?
You probably need to load the proper drivers for your USB->Serial cable. If you can't see the serial port in Device Manager, that's the first step to fix.
timbernme posted:Flakey software and finicky if you ask me. I can't figure out why it finds the port to program the TIU but can't find the port to program the remote.
it will do this if something is not right on the set-up. Did you remove the sterio mini cable from the TIU?
Thank you very much for the reply. I will give it a try.
Where might I locate the drivers for a serial to USB? Is that something I would do in device manager and if so how? Thanks!
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.
It's it interesting these software loaders perform so differently on various PC/Laptops/etc! Some problems are common and some are totally off-the-wall from an IT point of view. It's like the main code was cut in China and the subroutines coded in Bangladesh.
In this day and age , the upgrade method seems so archaic. When we upgrade our tractor GPS we plug in a USB stick with the upgrade. The same goes for my Precision Planting monitor. Not too tough to upgrade my Iphone, either. No cables or clothespin holding the on button, too. I say it's time for MTH to upgrade.
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.
my two-stage upgrade (from 4.3 to 5.0 and from 5.0 to 6.0) went fine.
FYI, you could have gone directly from DCS 4.3 to DCS 6.0 directly. There is no reason to do intermediate upgrades, regardless of what DCS releases are involved.
Access to this requires an OGR Forum Supporting Membership