Skip to main content

I recently acquired a set of Vision Line Ethanol Tank Cars. Using DCS WIFI, I created a Legacy lashup up using a Legacy engine and the tank cars. The cars were added as Legacy engines. After building the lashup everything ran fine except the horn on the engine was disabled. I tried a different engine but had the same result. 

I've been searching through Berry's book (The DCS WIFI Companion) but can't seem to find a fix for this problem. Any help would be appreciated.

 

Last edited by Lantom
Original Post

Replies sorted oldest to newest

Watch out switching between your Cab-2 and DCS app with regard to lashups. If you build a lashup using the DCS app, and subsequently build the same lashup using your Cab-2, the lashup will no longer function when you return to the DCS app. Likewise, the opposite is true if you build a lashup with your Cab-2 and then move to the DCS app. 

The big difference is what happens next. When your Cab-2 forgets a lashup, the configuration details for the lashup are retained, and you only need to press the “build” button to bring it back to life. However, with the DCS app, you are required to start over and rebuild the entire lashup right from the beginning. It’s a royal PITA, particularly if you have some complex arrangement that has taken a lot of time to set up via trial and error with regard to lead engines, orientations etc.

My preferred solution is using the DCS app to run only an engine or group of engines as the lashup, excluding sound cars. Then I just use a Cab-1 or Cab-2, to directly address any cars with sounds. I do this with station sounds dining cars and it works very well.

Barry Broskowitz posted:

Lantom,

Have you tried using the Cab-1 or Cab-2 to build the same lashup and then running it with the Lionel device?

Berry,

Thanks for the response.

I have built the lashup and trainlink with the cab-2 with success. All engine functions work well. 

GregR posted:

Watch out switching between your Cab-2 and DCS app with regard to lashups. If you build a lashup using the DCS app, and subsequently build the same lashup using your Cab-2, the lashup will no longer function when you return to the DCS app. Likewise, the opposite is true if you build a lashup with your Cab-2 and then move to the DCS app. 

The big difference is what happens next. When your Cab-2 forgets a lashup, the configuration details for the lashup are retained, and you only need to press the “build” button to bring it back to life. However, with the DCS app, you are required to start over and rebuild the entire lashup right from the beginning. It’s a royal PITA, particularly if you have some complex arrangement that has taken a lot of time to set up via trial and error with regard to lead engines, orientations etc.

My preferred solution is using the DCS app to run only an engine or group of engines as the lashup, excluding sound cars. Then I just use a Cab-1 or Cab-2, to directly address any cars with sounds. I do this with station sounds dining cars and it works very well

Greg,

This is really good information I wasn't aware of. Using both systems sounds like a good work around. 

Thanks,

Tom

Add Reply

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