350iroc posted:

I'm having and issue controlling my TMCC engine's through DCS after the 5.0 update. Any ideas? It's like the remote is no longer communicating to the TMCC base unit anymore. The red light is not blinking anymore when commands are being sent. 

I've seen a couple posts where people are having this issue while others are not.  Internally, we do not see it.  TIU code 5.0 shouldn't have any impact on TMCC operation under DCS.

Dave Allen posted:

I have ordered a Wi Fi module, but have just discovered that the app is not available from the Apple site in Australia. How can I get around this please? ( Obviously, I'm in Australia).

Dave,

Can you do this?  Switch to the USA Apple Store....

Change your iTunes Store country or region

JimQ posted:

Has anyone had the problem of being unable to get engines off the inactive list?  I have experienced all the issues with multiple engines and multiple TIUS and when engines get moved to the inactive list the touch screen for the inactive list does not respond... Is this also part of the upcoming fixes?

In the current version of the app, the only way to move engines from inactive to active, or visa-versa, is to do a refresh (read).  

Any engine the system  finds on the track(s) will become active.  Conversely, any engine not found is moved to the inactive list.  There is a bug in some configurations that cause the read process to be erratic.  This is explained in more detail elsewhere in this thread.

Going forward, we have plans to add the ability to selectively move a single engine to and from the active or inactive list.  I envision simply touching and holding an engine name in the list and dragging it up or down.  This is not a trivial change but, I think it would be a benefit.  It will allow users to keep their active list small and limited to engines you are running instead of all engines on powered track.

Thank you, Dave.  The selective movement would be a benefit. 

When using a remote, I find the presence of an inactive list to be a pain, and avoid a read like the plague.  To recover froma read (my grandson often hits the button), I do a restore from the PC.

I can understand your position on keeping the active list small, but if MTH gets the read function straightened out so there isn't always doubt about what's controllable by the app, I think I'd prefer not to have locos drop into inactive.  All in all, I wish the app would just keep everything active, like the remote.

Gregg posted:

Gregg posted:

Hmm... Are you going to be able to fix the regular remote  feature reset at the same time. After 14 years it's changed,

It's my understanding the feature reset  doesn't work as well with the App???  The custom name  disappears.  Id sticks though.   

Hello.... ??? 

Robert,

I wish the app would just keep everything active, like the remote.

FYI, in order to use the All Engines feature (remote only at present) one must clear the Active Engine List of all engines that will not be participating in the session. Otherwise, error messages will be abundant.

I wonder what percentage of DCS users use the all engines feature.

I will

RJR posted:

I wonder what percentage of DCS users use the all engines feature.

I use it occasionally and I think it's a pretty handy feature to have.

MTHRD, thanks for the info...  For a while I was thinking I was the only one having this trouble...  I await the new firmware and app...  Any updates on when they will be available?  End of January? First quarter 2016??

I just tried running my 2 wifis through the home network instead of the MTH.  The read function might work better????????

Two Model Railroaders • Two Train Rooms • Two Layouts &

One Photo Story

Gary: Cheers from The Detroit & Mackinac Railway

RJR posted:

Thank you, Dave.  The selective movement would be a benefit. 

When using a remote, I find the presence of an inactive list to be a pain, and avoid a read like the plague.  To recover froma read (my grandson often hits the button), I do a restore from the PC.

I can understand your position on keeping the active list small, but if MTH gets the read function straightened out so there isn't always doubt about what's controllable by the app, I think I'd prefer not to have locos drop into inactive.  All in all, I wish the app would just keep everything active, like the remote.

 

Snap ring on both of my remotes..and it is pressure proof.

Steve Kilmer posted:

Thanks MTH. 

The bell shuts off when you press the horn on android. I think this is a bug.

I have had this happening also!

Well-known bug.  Supposedly already cured in forthcoming revised firmware/app.

It's only a problem on Android. It doesn't happen on iOS.

Update on testing.  Tonight I started up my 2 wius on the home network after first powering up all tracks.  Tablet would not read locos on wiu#2 (tiu#2)  I shut down the layout, and moved outputs from TIU#2 to TIU #1, doubling up on fixed 1 & 2.  Turned off WIU#2.  Switched WIU1 to MTH mode.  Powered up, turned on wifis, and tablet read every lcoo on layout, all 24.  Turned layout off, moved wires back to TIU#2, whose wiu #2 was slaved to WIU#1, and all 24 locos were read and operable by tablet.   Tried smartphone, and that would not read all locos.

I haven't have any idea why problems above have not repeated.

I wonder if different versions of android software are yielding different results?????

I posted this in another thread.

Dave Minarik said,  The app will not find any engines (time out error) with the Fixed 2 channel powered up. 

I was getting this error on two different layouts on two out of three Rev L TIUs

It all seems to be working now.  I changed nothing.

Dave

You sound frustrated, Dave.  I know the feeling when things start working after one does nothing.  Could the app save data that helps on future reads?

Not frustrated.  I just want to figure it out.