DCS upgrading

Versions from 4.0 and up have significant improvements in several areas, including running TMCC engines.

Suggest you upgrade, you won't be sorry.

Barry's DCS Companion has a very detailed description of how to do the upgrade. Perhaps he will jump in here with an excerpt from the book.

You will need a serial data cable and a serial to USB adapter. All available at Radio Shack I believe.

 

Rod

Rod's right about Radio Shack.  I got, from R-S, a Gigaware6-ft USB-A to serial cable.  Works perfectly.

Rod,

 

I would agree that the upgrade from 3.1 to 4.2 offers some nice features. However, I've found that I am not able to create lash-ups involving TMCC engines despite what this update was supposed to offer.

 

Bill

Bill,

I've found that I am not able to create lash-ups involving TMCC engines despite what this update was supposed to offer.

I find that surprising, since I've never had any problem building TMCC lashups in the past. This feature isn't new with 4.20. It's been around for a while and was first introduced in DCS 4.0.

 

Where are you having a problem?

Barry,

 

When I tried adding two Atlas engines, an F3 A and B unit as a lash-up, the A unit would start up yet the B unit remained inoperative.  However, when I would run either unit independently on the same track, each operated without issues?

 

Bill

Bill, Are you certain that you built the lashup correctly? Did it operate correctly using a Cab-1 or Cab-2?

Do you have the 2nd edition of my book? If so, follow the instructions on page 46 and see the notes on page 103.

 

 

Also, do you have a Cab-1or Cab-2 with which you can also attempt to operate the lashup?

Yes, I have your 2nd edition and just re-read the pages suggested.  I had been following those steps to create the lash-up and don't think I've overlooked anything.

 

I do have a Cab 1 and will try creating this using same engines later today.  Thanks for the insight.

I do have a Cab 1 and will try creating this using same engines later today.

Before you try to get it created using the Cab-1, first try creating it using the DCS Remote and then operating it from the Cab-1.

Barry - the lash up will show up on the DCS as I create it by name (minus the L) however,  as soon as it's created and I hit the D completing the naming process, the A unit starts up immediately and the B unit remains quiet and non-responsive.

 

When I ran this same lash up using the Cab 1, it operated just fine.

the lash up will show up on the DCS as I create it by name (minus the L) however,  as soon as it's created and I hit the D completing the naming process, the A unit starts up immediately and the B unit remains quiet and non-responsive.

What happens if you press Startup on the DCS Remote?

 

If you run it using the Cab-1, can you then also use the DCS Remote to operate it once the Cab-1 starts it up?

Thanks, Rod. My newer computer does indeed have a serial port, I didn't see it before. Now, I just have to locate the cable. I found two of them thus far, but no serial cable. I'll try to find the upgrade instructions on the internet.

Please answer the following questions:

Pressing start-up does nothing.  If anything, it has a tendency to startup when I press the D button after adding the lash up name.

 

 

I will check whether I can run it using DCS, after starting up via Cab 1 tomorrow.

Barry - following up on your recent suggestions: only the A/lead unit responds when pressing Startup on DCS remote  

 

Additionally, when I start up lashup via Cab 1, then trying to operate using DCS remote, nothing happens as it remains unresponsive.

 

I added to different Atlas engines with the results being the same.  The constant theme is th lead engine will startup however, the end unit does not respond unless addressed separately, i.e. bringing it up on the DCS screen as F3B unit.