Skip to main content

We need your questions for MTH to answer at the 18th York DCS User Group Meeting next month!

 

We'll submit them in advance of the meeting so that MTH has time to do any necessary research required to formulate an answer. You do not have to be present at the meeting to submit a question.

 

You can post your questions here or on the main meeting thread, or you can E-mail them to me at the address in my profile.

 

The cut-off is the end of the day, Sunday 9/28.

 

Thanks in advance!

Last edited by Barry Broskowitz
Original Post

Replies sorted oldest to newest

Originally Posted by MartyE:

Since I am asking the same of Lionel  concerning Legacy at the LUG meeting, will we see DCS technology available in more operating cars and accessories?

 

Thanks!

 

Originally Posted by Barry Broskowitz:

Marty.

 

That's already on the list.

 

Thanks!

Glad this was requested.  Years ago MTH hyped the future potential or possibilities of their technology that they used in the Coors Light set reefer cars, but all that seemed to go dark with the economic and the hobby industry's general decline from 2008.

I'll ad focus to the desire for Add on modules for cars:

I need a small module with a protocoupler for various cars.

It will need to be addressable, perhaps that unused AUX key and addresses like engines?

And Yes, 4 digits for Eng numbers would be nice but I'd be happy with 3, Who has more than 999 engines???

Last edited by Russell

Barry

 

Tried it again. The sounds Horn and bell stay with the initial lead engine. the headlight, number boards and cab light change with direction.The ditch lights also change except I have it set for always on and flashing with horn on initial lead unit, when in reverse ditch lights out and flash with horn, I can live with that. Might have something to do with settings of individual locomotive. I guess I just want the horn and bell to move with direction. Doesn't matter much with a two unit lash up, but with three or more it is noticeable…... I like 4 to 6 units in a lash up.

Thank you Barry

 

Clem 

I think it would be more helpful to users if the remote would display the actual problem, if it was possible, when it encounters one during a session or an add. I don't know what's available for message resources. I think it would be helpful to users to know that there's a problem the remote is seeing and knowing exactly what that problem is, to help us correct it.

 An address that's currently used that won't move for example. An engine that won't respond (maybe a dead battery or unpowered).

 I know there's the "out of range", and "engine error ones", etc. They seem to be overly used for different errors.

Joe,

An address that's currently used that won't move for example.

There aren't any,any more. DCS 4.30 corrected that bug.

 An engine that won't respond (maybe a dead battery or unpowered).

If an engine can't respond, how can DCS know that there's an engine present?

 

The error messages do the best they can, however, DCS can't tell if an engine is not present or present but not responding. How could it?

 

 Sorry Barry, I don't know the sequence. I was thinking that the system may see the engine, but can't get it to do something, like change the address. I guess the system would have no way of knowing the condition of the battery. I would have thought it checks for the address to stick even temporarily. Not getting any response from the engine, I can see your point.

 I didn't realize that the address bug was really fixed!

Add Reply

Post
The DCS Forum is sponsored by

OGR Publishing, Inc., 1310 Eastside Centre Ct, Ste 6, Mountain Home, AR 72653
800-980-OGRR (6477)
www.ogaugerr.com

×
×
×
×
Link copied to your clipboard.
×
×