Jump to content

Search the Community

Showing results for tags 'MTH DCS'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • News
    • Website News & Information
  • Real Railroads
    • Restoration & Excursion News
    • Photos & Video
    • News
  • G-Scale Forums
    • Buildings, Figures and Accessories
    • For Sale / Wanted / Trade
    • General Discussion
    • Indoor Layouts
    • Kitbashing & Model Making
    • Live Steam
    • Locomotives
    • Rolling Stock
    • Track & Layout
    • Train Shows, Clubs & Events
  • Power / Sound / Control
    • Battery Power & Control
    • Digital Control
    • Sound Systems
    • Traditional Track Power
  • Vendors - Products & Services
    • Vendors offering Products & Services
    • Find a Vendor
  • Website & Help
    • Website - General Help and Info
    • Testing

Blogs

  • Digtigs69's Blog
  • enginear joe's Blog
  • Chuck's Blog
  • andiwalker's Blog
  • brian weisman

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Interests


First Name:


Last Name:


Location:

Found 10 results

  1. *Update 12/31/15* I now have PS3 upgrade boards available for those who want to upgrade their PS2 engines to PS3. Please visit my website and send me an email if interested. Feature/Enhancements list for new MTH Protosound 3 boards: PS3: (Factory pre-installed in MTH Engines) - Can use both original PS2(3v) or new PS3 sound files. - Increased memory capacity for sound files (higher quality sound) - Higher quality audio amplifier (vs PS2) for crystal clear sound reproduction - All LED lighting instead of Incandescent. (saves power and longer bulb life) - If power is temporarily lost to engine, LED lights stay lit, powered by on-board capacitors. - Auto 'Rule 17' lighting of the headlight (auto dims when idle for a period of time and brightens back up when commanded to move) - Eliminates the need for a polarity switch on the engine - Has significantly improved communication signal processor for better track signal. - You will get improved signal strength with all TIU versions. Best results with Rev L TIU or newer. - Eliminated the rechargeable battery pack (uses built in capacitors for backup power) - Can be run and controlled in a DCC environment (DCC power and control) with the flip of a switch on engine/tender. See the below link for more info on DCC PS3: - www.rayman4449.com/DCS_Overview_Videos.htm#Operating_PS3_Under_DCC - Engines now no longer take off running if they miss the TIU initial power up signal. (An issue when running under DC power) If an engine misses the signal it will power up lights and sound but stay put and not move. - Because of the improved signal processor, missed TIU startup signals will be eliminated or greatly reduced. PS32: ("PS32" Upgrade board for PS2 to PS3 upgrades) ** Different from Factory PS3 board - Can use both original PS2(3v) or new PS3 sound files. - Increased memory capacity for sound files (higher quality sound) - Higher quality audio amplifier (vs PS2) for crystal clear sound reproduction - **All connectors same as the PS2(3v) board to simplify upgrade. - **Drives original Incandescent lights to simply upgrade from PS2 to PS3. - **Does not currently have Auto 'Rule 17' lighting of the headlight (auto-dimming when idle for a period of time and brightens back up when commanded to move) - May be made functional in later PS3 board firmware versions. - Eliminates the need for a polarity switch on the engine. - Has significantly improved communication signal processor for better track signal. - You will get improved signal strength with all TIU versions. Best results with Rev L TIU or newer. - Eliminated the rechargeable battery pack (uses built in capacitors for backup power) - Can be run and controlled in a DCC environment (DCC power and control) with the flip of a switch on engine/tender. See the below link for more info on DCC PS3: - www.rayman4449.com/DCS_Overview_Videos.htm#Operating_PS3_Under_DCC - Engines now no longer take off running if they miss the TIU initial power up signal. (An issue when running under DC power) If an engine misses the signal it will power up lights and sound but stay put and not move. - Because of the improved signal processor, missed TIU startup signals will be eliminated or greatly reduced. Other notes: - PS3 engines are fully backward compatible with all existing TIUs and Remotes. - PS3 boards use chips and components that are more easily sourced on the market which will ensure there are never supplier constraints in the future. (i.e. should never be issues with getting PS3 board / upgrade kits in the future once they start making them) - All current production MTH engines are being made with PS3 installed. - PS3 is available for HO, O, One Gauge and S. (Boards for HO are different from O/One Gauge and are designed to accommodate the reduced space and amperage requirements of HO.) - All current production MTH One Gauge engines (2013 Catalog and newer) will come with PS3 pre-installed. - The O gauge PS3 and PS32 boards were made with the One Gauge line in mind so no special provisions should be required for One Gauge. To recap the key benefits for G scale/One Gauge: - Significantly improved signal processor on the engine board. (If you have had signal/communication issues in the past on your layout, this should resolve it or significantly reduce any issues. Best results, run PS3 with Rev L TIU) - This is relevant for G scale because of the much larger size of the layouts and conditions faced outdoors. - Improved audio amplifier for higher sound quality - PS3 sound samples used: Have greatly enhanced sound quality. - No more missed TIU start up signals: Engines stay put and will not start running/moving unintended in analog mode if they miss the TIU startup signal on initial power up. (Applies to DC power operation) If you had engines missing the signal in the past moving to PS3 should eliminate or greatly reduce this happening. - Eliminates the need for the polarity switch on the engine as the PS3 board is no longer polarity sensitive. - Eliminates the need for the on-board rechargeable battery pack (the only maintenance item you had on the engine) - Can now run under DCS or DCC.
  2. **Updated 12/8/19** This thread is to provide users Troubleshooting setups/tips and to provide feedback and any issues they may find in their operation. See the bottom for the list of current issues encountered, dates, etc. If you are seeing similar issues I encourage you to report them via the app on your device. Provide as much detail as you can, like using Android, PS2/PS3 engines etc. Also, be sure to report any bugs or issues to MTH directly at: https://mthtrains.com/dcs-app-contact-form *Please be sure to provide the device you are using, version of the app operating system if you have it and version of TIU if known.* Original MTH WiFi Control app thread: www.gscaletrainforum.com/index.php?/topic/35-mth-wifi-control-app-wiu-wifi-interface-unit/ Troubleshooting Steps: If you are having WIU related issues/errors, performing all of the following steps in order should clear the majority of problems: Power down WIU, TIU and Power supply: Turn off power supply for track power Unplug Aux power supply from TIU Aux power port (if you are using one) Unplug the power connector from the WIU Note: Let everything sit unpowered for a few seconds. Turn on power to WIU, TIU and Power supply: Wait 1 min for WIU to fully boot up You should see the following lights: (after 1 min) BLUE: Wifi network indicator PINK: TIU is connected indicator GREEN: WIU power indictor Unplug USB cable from TIU: With WIU, TIU and track power supply on (allow for 1 min for WIU to fully boot up), unplug the USB cable from the TIU and confirm the PINK light on the WIU goes out (Pink=TIU light on WIU). (If Pink light does not go out, plug back in and unplug again) Manually close the DCS app in the Phone/Tablet: Android: Access the currently open tasks/programs on your device using normal process. (For some devices you will look for the square button at the bottom: Example #1: (in GREEN) Example #2: (In GREEN) Note: your Android OS may be different from what is noted above. Next you will see multi-layered windows where you can then find the DCS app and press the X at the top right of the DCS app to close. Reboot Phone/Tablet: (Power device off and power back on) After device powers back on, wait about 30 seconds to fully let device boot up, then verify that you are connected to the MTH Wifi network swiping down from the top of the screen and long pressing the Wifi icon: Confirm you are connected to the MTH Wifi network: (Your MTH network name will vary) (Default Password is: mthdcswifi Start the DCS App again: Start the DCS app by selecting the MTH DCS Wifi icon on your phone/tablet *****END of TROUBLESHOOTING STEPS***** - Everything should be working. If still having issues: Turn your phone/Tablet screen saver/screen power off timer settings to the maximum allowed (30mins or greater) When some devices power down the screen it will put the DCS App to sleep, causing all engines to go inactive Exclude the MTH DCS Wifi app from any power save features by your Android or Apple OS. Review how to setup your App for the device you are using (either WIU or DCS Explorer) by reviewing this video: https://youtu.be/tTEnsUdBk6o Ensure your WIU is loaded with the latest firmware: http://www.gscaletrainforum.com/index.php?/topic/35-mth-wifi-control-app-wiu-wifi-interface-unit/ Ensure your TIU is loaded with the latest TIU firmware: http://www.gscaletrainforum.com/index.php?/topic/693-mth-dcs-remote-tiu-firmware-v610-current-version/ Note: Wifi System can be buggy if your TIU has outdated firmware If you are using a cheap, no-name brand tablet then you may find the operating experience is very buggy and inconsistent. I STRONGLY urge using a well-known, name brand tablet like Samsung or Apple. Adding engine issues: Track signal related problems: where engines aren't being found to add into the app have to be addresses separately (checking track joints, layout wiring or layout tuning) See: Layout tuning If you are trying to add MTH/DCS engine to the app and an address number shows up then disappears, then you likely have 2 engines on the layout with the same ID number and it is confusing the app. Isolate the engines that aren’t yet added in the remote on a separate track (with no other engines on the track) and add them to the app one at a time. *********************************************************************************************************************************************************************************************** Demo & Overview of the Wifi app: (Standard version) (Select 1080p HD to get max playback quality) Items to note: - Whistle not playing on start-up: (On engines with Playable whistles) - This is something MTH actually covers in the WIU Users manual. Currently if you turn playable whistle on in the settings screen then shut the engine down. The next time you start the engine up, the whistle won't activate unless you go into settings and toggle the Playable Whistle button to off (or back on again if you like). While it's not technically a bug, MTH has indicated they will be updating the app to default the Playable Whistle toggle to off when the app is shutdown/started to correct this issue. I have also made the recommendation that the Playable Whistle feature be automatically toggled to off whenever the user hits Start-up to help eliminate this issue completely. You can also just double tap the whistle cord on the screen to toggle between Playable and Regular whistle function. (Cord will turn Purple when on Playable) Issues list (Currently open): (Updated: 03/10/18) - Lash-up & Engine name change (DCS Wifi App bug) (3/10/18): If you create a lash-up and then later attempt to rename an individual engine (used in that Lash-up) with the App/Remote, the next time you go to select and startup that Lash-up, the DCS App will automatically change the name of the engine back to the original name the engine had when the Lash-up was created. The work-around is if you change the name of an engine in the App that is also in a Lash-up, you will need to also delete the Lash-up and recreate it. - Lash-up engines not responding to commands (DCS Wifi App bug) (3/10/18): Engines other than the lead engine in a lash-up may not respond to commands when you start a lash-up. Work-around: 1st step: Manually move all engines back to Active, that are automatically moved to Inactive when you select/startup a Lash-up. Moving all the Lash-up engines to Active can sometimes ensure they will respond. You can then go back to the Lash-up engine name and see if all the engines will respond. 2nd step: In some cases step 1 might not work. If so, then you will want to select the other non-lead engines individually and select STARTUP to start them up that way. You can then go back to the Lash-up engine name and they will now respond. Issues list (Fixed): (Updated: 04/20/17) Version v2.0.0 build 36 (Premium version release 4/18/17) Version v2.0.0 build 37 (Premium version release 4/20/17) - Unlock Features on additional devices: (Android) (Reported: 4/18/17 Fixed: 4/18/17) Upgraded first device to Premium and all features unlocked. However on second and later devices under same account am unable to unlock Premium features. Selecting Purchase again returns Error message it is already purchased but then does not unlock the features. This has been reported to MTH via DCS app. - No whistle under Steam or Steam Turbine Lash-up: (Android) (Reported: 4/18/17 Fixed: 4/20/17) No whistle under steam or Steam Turbine lash-up. Created a lash-up with 2 PS3 engines under DC power and after startup cannot get whistle to play. Work around for this issue is to go to the third screen and select Engine Type of Diesel. This has been reported to MTH via DCS app.
  3. Photos of the MTH Big Boy in 1:32 scale. These are probably my most favorite engines to run in my collection. For more info see the following pages: Additional Photos and Product information page: http://www.rayman4449.com/MTH_Big_Boy.htm Repairs/Modifications page: http://www.rayman4449.com/MTH_Big_Boy_mods.htm These pages are accessible off my home page at: www.rayman4449.com (Click the photo to enlarge) NEW PHOTOS (09/27/2014)
  4. If you have an Amazon Kindle (which is a great, inexpensive tablet for running the MTH DCS Wifi app) you will need to install the official Google Play Store on the tablet before the DCS Wifi app will work. (The Kindle comes installed with Amazon's custom App Store) Instructions are below to help you get the full official Google Play store installed. In addition to installing Google Play Store, also make the following changes to your tablet settings: Disable Automatic Smart Suspend: (This turns off the tablet wifi when the tablet is not in use) From the Home screen, go to: Settings -> Power -> and turn off "Automatic Smart Suspend" Installing Google Play store on Kindle Fire: *Please note that you are fully responsible for any and all actions you take by using this information or following these steps.* http://blog.the-ebook-reader.com/2016/07/02/how-to-install-google-play-on-fire-tablets-the-super-easy-way-no-pc-or-root/ How to Install Google Play on Fire Tablets Step #1: Prepare Your Fire Tablet Go to Settings > Security > Enable Apps from Unknown Sources. Step #2: Download Google Apps You need to download 4 different apk app files. The easiest way is to download them to the Fire tablet directly. Using your Kindle internet browser, go to this link (http://forum.xda-developers.com/amazon-fire/general/how-to-install-google-play-store-fire-t3486603) and download the 4 apk files listed. If you have a newer Fire tablet which has Fire OS 5.3.1.1 or 5.3.2 and up (Confirm this by going to Settings -> Device Options -> System Updates -> Note the Version of the OS listed) then use these newer apps from the link provided above instead of the older ones shown in the Youtube video below. If Google Play suddenly stopped working on your Fire tablet after updating then install the top two newer files from the XDA link above, Google Account Manager and Google Services Framework. Then restart the tablet and it should be good to go. That worked for me after the 5.3.2 update. If you download/save these files to your Kindle directly, make sure you remember where they are saved. Step #3: Install Google Apps Use the Fire tablet’s Docs app to locate the downloaded apk app files to install them. Generally the default location is Docs > Local Storage > Download if you used the web browser to download the files above. The Google apps need to be installed in the following order to work: Note: that if you are using the newer apps from XDA then follow the order listed over there, but it should work either way. · Google Services Framework · Google Play Services · Google Account Manager · Google Play Store Once that’s finished you can open the Play Store and sign in to your Google account. Step #4: Update and Restart After you open the Play Store for the first time you need to install the YouTube app and then open it. This will prompt the Play Store services to update to the latest version, an important last step. Once the update is installed (it takes awhile), power off and restart your Fire tablet. Now the Google Play Store app should be good to go! Video: How to Install Play Store on Fire Tablets
  5. Wanted to share this install with everyone since this one is so unique, one of the few One Gauge Burlington Zephyrs under Protosound 3.0. Quite a privilege to get to work on such a rare and unique engine.
  6. The latest version of the DCS Consumer Loader v5.00 has just been released. This is the PC software (free) for your computer to upload firmware to your TIU/Remote or upload/download sound files to MTH Protosound 2/3 engines. You can download the current version from: - MTH: MTH DOWNLOAD - Rayman4449.com: www.rayman4449.com/DCS_Tips.htm#DCS_Software Instructions on how to download and install the DCS Consumer Loader program: DCS Consumer Loader Program version 5.00 for Windows PC: (This is the software you install and run on your Windows PC to perform the TIU and Remote firmware/software updates) - Visit www.protosound2.com - Download the DCS Consumer Loader Program Version 5.00 by clicking the 'Download Now!' link. (*Click for example photo*) - Fill out the required info then select 'Go to Download Software Page'. (*Click for example photo*) - On the DCS Software Version 5.00 link either left click to download and note where the files are saved OR right-click and select 'Saved linked content as' and save to where you want. (*Click for example photo*) (Right click menus will vary based on Internet browser used) - You then have file "V5.0.0.exe". (This is a file that can self-extract, you do not need winzip or any other program to extract the files) - Use 'My Computer' or 'This PC' on your desktop or use Windows file explorer to go to where the file was saved. - Left-click the "V5.0.0.exe" file (which starts the self-extractor) - Then select the 'Browse' button and save to 'Desktop' so it's easy to find, then click 'Ok' then 'Unzip' (*Click for example photo*) - You now have two files "Setup.exe" and "MTH DCS Consumer Loader V5.0.0.msi". - Go to where they are saved and Left click the "Setup.exe" file to start the install process and complete. (MTH recommends un-installing older versions of the loader first) - Left click the "DCS Consumer Loader" shortcut on your Desktop - You will then see this screen where you can select icons to either load to TIU or load to remote. Click the appropriate icon and follow the instructions. (*Click for example photo*) - Note where you saved your DCS TIU and Remote files from the steps below. You will also need: DCS version 5.00 for the TIU and Remote: (These are the DCS data files that the Consumer Loader Program uses to update your TIU and Remote) - Visit www.protosound2.com - Download the DCS Version 5.00 by clicking the 'Download Now!' link. (*Click for example photo*) - Fill out the required info then select 'Go to Download Software Page'. (*Click for example photo*) - On the DCS Software Version 5.00 link either left click to download and note where the files are saved OR right-click and select 'Saved linked content as' and save to where you want. (*Click for example photo*) (Right click menus will vary based on Internet browser used) - You then have file "DCS5_00.exe". (This is a file that can self-extract, you do not need winzip or any other program to extract the files) - Use 'My Computer' or 'This PC' on your desktop or use Windows file explorer to go to where the file was saved. - Left-click the DCS5_00.exe file (which starts the self-extractor) - Then select the 'Browse' button and save to 'Desktop' so it's easy to find, then click 'Ok' then 'Unzip' (*Click for example photo*) - You now have three files. Two are the key ones you need "tiu5p0.DCSt" & "remote5p0.DCSr" to use with DCS Loader program. These files cannot be used on their own. MTH DCS Remote & TIU firmware thread: www.gscaletrainforum.com/index.php?/topic/693-mth-dcs-remote-tiu-firmware-v500-current-version/ *************************************************************************************************************************************************************************** Info on the DCS Loader v5.00 Release: Ps3 DCS 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. Among the many changes to the loader, the list below represents the most significant from previous 2.X DCS Consumer Loader software versions. Updated to load the new DCS version 5.00 to TIU and Remotes. You MUST use this new DCS Consumer Loader in order to load DCS version to TIU and Remote. 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 will disable 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. 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. (These are available here *Click to buy*) A STEREO mini-to-mini 1/8†audio cable available from MTH or here *Click to buy* An AC or DC Transformer. 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. (These are available here *Click to buy*)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 adapter cables are available here *Click to buy* 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 *Click to buy*. 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. ________________________________________________________________________________________________________________
  7. For those who may not have seen, wanted to post links and info on the overview video series and page I have setup to educate on what the system is and how it operates. Main page: www.rayman4449.com/DCS_Overview_Videos.htm (Full page with all detail information) Overview of Remote and menus: www.rayman4449.com/DCS_Overview_Videos.htm#DCS_Remote_Photo_Overview Overview videos: www.rayman4449.com/DCS_Overview_Videos.htm#Overview_Videos Part 1 of 5: Part 2 of 5: Part 3 of 5: Part 4 of 5: Part 5 of 5: (1 of 2) Part 5 of 5: (2 of 2)
  8. Just wanted to share that an updated version of the DCS Consumer Loader v2.34 has just been released. This is the PC software (free) for your computer to upload firmware to your TIU/Remote or upload/download sound files to MTH Protosound 2/3 engines. You can download the current version from: - MTH: http://www.mthtrains.com/dcs/downloads/dcsconsumerloader_v234/input - Rayman4449.com: http://www.rayman4449.com/DCS_Tips.htm#DCS_Software List of enhancements for this version: http://www.protosound2.com/service/loader234.htm Ps3 DCS Loader Program - Version 2.34 What’s New in version 2.34? 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. Among the many changes to the loader, the list below represents the most significant from previous 2.X DCS Consumer Loader software versions. 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 at www.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 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 AddressYou'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 2.3. WARNING: 2.20, 2.30 & 2.34 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 will disable 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. 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. (These are available here *Click to buy*) A STEREO mini-to-mini 1/8†audio cable available from MTH or here *Click to buy* An AC or DC Transformer. 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. (These are available here *Click to buy*)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 adapter cables are available here *Click to buy* 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 *Click to buy*. 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. ________________________________________________________________________________________________________________
  9. See this thread for most current DCS Remote and TIU firmware versions: www.gscaletrainforum.com/index.php?/topic/693-mth-dcs-remote-tiu-firmware-v500-current-version/ ***************************************************************** **OUTDATED as of 1/1/2016 Wanted to share that the latest version of the DCS remote and TIU firmware is now available. (Updates as always are free of charge.) (As Joe noted below if you have Lash-ups you may want to recreate them after upgrading if you want to gain access to the new Softkeys created) You can download direct from MTH here: www.protosound2.com OR You can download the .Zip file here: DCS v4.30.zip (**Note: You do not need to change or upload anything to your engines. This is software only for the Remote and TIU.**)) For instructions on how to upgrade the TIU and Remote software see below or my website: http://www.rayman4449.com/DCS_Tips.htm#DCS_Software_and_Upgrade_TIU_Remote (also see my website for info and photos for needed cables, additional information and troubleshooting.) Step 1: Updating the TIU **When updating to a different version of DCS software in your TIU and remote, you should always start by updating the TIU first.** Connect your TIU to the computer using either the 9 pin serial or USB cable (Your computer can already be booted up) Plug the 3.5mm stereo audio cable ends into the TIU's "Proto-Dispatch" & "Proto-cast" ports Connect the power supply to the Fixed 1 input port OR connect the Aux power supply to the Aux power port on the TIU Start the DCS Loader program Close out of any unnecessary programs or applications and do not use the computer while the update is in progress Click the load software to TIU Icon Carefully follow the instructions on the screen. (it will instruct you to connect the serial cable and 3.5mm audio cables) Then select the "*.tiu" (example: "Tiu4p30.tiu") file The update process should start and will tell you when you are finished Step 2: Updating the Remote Once you have updated the TIU software to the version you are wanting to use, then update the remote. Connect your TIU to the computer using either the 9 pin serial or USB cable (Your computer can already be booted up) BE SURE TO REMOVE the 3.5mm stereo audio cable ends from the TIU's "Proto-Dispatch" & "Proto-cast" ports Connect the power supply to the Fixed 1 input port OR connect the Aux power supply to the Aux power port on the TIU Start the DCS Loader 2.xx program Close out of any unnecessary programs or applications and do not use the computer while the update is in progress Ensure your remote has good batteries and test it by turning it on. Ensure the remote is off before you get started Connect the remote to the TIU with the 4-pin narrow phone cable. (Be sure to plug the remote into the Remote input port NOT the AIU port!!!) Click the load software to Remote Icon Carefully follow the instructions on the screen. (it will instruct you to connect the serial cable and remote cord)NOTE: When instructed to press the power button on the remote, the remote should remain off. If the remote powers up, it's not detecting it's plugged into the TIU. See below steps for troubleshooting. Then select the "*.rem" (example: "remote4p30.rem") file Follow the instructions on the screen The update process should start and will tell you when you are finished. *********************************************************************************************************************************** Version 4.30 New Features The following new features have been added into DCS 4.30: · 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 Resolved Issues The following issues have been resolved in DCS 4.30: 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 with 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 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.
  10. If you have a powered up layout in current operation there may come the time when you will want to use an unpowered siding or staging track like I do where you add the engine to an unpowered section of track, add power and drive it off. When you add power to a DCS engine, it first looks for a 'watchdog' signal which is sent by the TIU only when first turned on. After the TIU is turned on, the only way to trigger this signal to be sent again later is to hit the 'READ' button on the remote. (which is easy enough) But this idea just brought up (and many thanks to Chuck for sharing this with me) is the use of a DCS Remote Commander box passively connected to each siding. (set pictured below) These were created for inexpensive starter O gauge sets intended to control just one engine. However if you connect the DCS Remote Commander box to a siding passively (ie. Connect the red and black terminals to the siding) when the siding is powered up it will generate the watchdog signal automatically so you dont need to hit the 'READ' button when powering it up. (Also note that it does not matter what power polarity the DCS Commander box sees, it will still transmit the watchdog signal and the engine will still receive it so just connect a wire from each rail to each terminal and go.) Why this is important: If a DCS equipped engine receives track power without receiving the watchdog signal it assumes that it is supposed to run under regular analog track power and will power up and start running. So if you want to run an engine under remote control you will want to make sure you send the watchdog signal to the engine at the time it is powered up so it waits for remote commands. http://www.mthtrains.com/content/50-1033 Great tip and will be buying a couple of these for my two staging tracks on my layout. I'm trying to find out now if the box is available separately. If anyone is looking for these let me know and I can get a price for you. Raymond
×
  • Create New...