Skip to main content

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

If you move to a new country, go to Account Info or Settings to change your country before you make purchases from the iTunes Store, App Store, iBooks Store, or Mac App Store.

 

What you need know before you change your country or region

When you change your iTunes Store country:

  • You need to update your billing address to one in your new country. When you change your billing address, the primary address in your account at My Apple ID and your other Apple services, such as the App Store and iCloud, automatically updates.
  • You might need to update your payment method. For example, only German credit cards can be used to buy content from the German iTunes Store and App Store.
  • You won't see the items that you purchased from the previous country’s store in your Purchased section.
  • You won’t see the items from your iCloud Music Library that you matched, uploaded, or added from the previous country’s store.

When you make a purchase in the iTunes Store, App Store, iBooks Store, or Mac App Store, the country in your iTunes Store account information must match the country listed in your account at My Apple ID.

Seems like this might get you the software!  Probably not in Barry's book...

Ed

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.

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.

20151102_221955

Attachments

Images (1)
  • 20151102_221955
Last edited by willygee

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?????

Last edited by RJR
MTH RD posted:
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.

I still am unable to control my TMCC engine's through DCS after the 5.0 update. Still operates perfectly with the Lionel CAB1 remote. I have the MTH TIU/TMCC DB-9 connector cable in the correct direction with TMCC labeled on one end and TIU on the other.  I've added, deleted, reset, inner track, outer track, upper track, 5 different engines without success.  I only have 1 TIU and have disconnected the WIFI for trouble shooting. DB-9 cable tested strait to TIU and in a splitter scenario. My current setup positively worked as it should before the 5.0 update. The red light no longer flashes on the base unit when executing DCS commands to it. I have two DCS remotes to test with. Again the Lionel remote works perfectly. Is there a way to tell if the MTH TIU/TMCC DB-9 connector cable is MTH part# 50-1032 or 50-1018? Is there a difference in these two part numbers and if so could this possibly be causing my inability to no longer run TMCC through DCS? I reaching here but I'm close to stumped....

# 50-1032 or 50-1018? Is there a difference in these two part numbers and if so could this possibly be causing my inability to no longer run TMCC through DCS?

Either one will work with a TMCC Command Base although the 50-1018 will not work with a Legacy Command Base.

If the command base light doesn't blink when you enter MCC engine commands on the DCS Remote, then most likely the problem is one of the following:

  • You have the wrong cable (unlikely, if it worked before the DCS update)
  • The cable is reversed end-for-end
  • The TIU has a different DCS ID# than what  you told DCS was the DCS ID# of the TIU to which the cable is connected, when you added the TMCC engines.


Last edited by OGR CEO-PUBLISHER

I'm starting to strongly suspect that there are differences in the operational characteristics of the android and apple apps, that problems show up on one and not the other.  Weird things happen.  This morning, on my android tablet, the softkey screen was a blank until I exited the app and restarted it.  I also have 1 of my 3 devices that turns off the wireless connection for no apparent (as of yet) reason while the other 2 devices continue to operate.

Allscale posted:

I am having the same problem as 350IROC.  Since I went to 5.0, I have no control either with the remote or thru the WIU.  I have changed track sections,lock-ons, power supplies, locomotives, etc., and no joy.

Allscale

Allscale did you ever find a solution to getting your DCS remote to start communicating to the TMCC base?

RJR posted:

I'm starting to strongly suspect that there are differences in the operational characteristics of the android and apple apps, that problems show up on one and not the other.  Weird things happen.  This morning, on my android tablet, the softkey screen was a blank until I exited the app and restarted it.  I also have 1 of my 3 devices that turns off the wireless connection for no apparent (as of yet) reason while the other 2 devices continue to operate.

I can attest that operational characteristics between Android and iOS apps are fundamentally different.  There are differences in how the two platforms deal with Wi-Fi connections, behavior on return from lock screens, and more that we, as app developers, have no control over.  Of course, we try to mitigate these differences the best we can in terms of the user experience but, some differences just cannot be worked around in a practical manner.

The Android app losing the softkey list on occasion is a known bug and was addressed in the current release under beta test.  I think we squashed that one.

hclarke posted:

Wow!  Lots of problems with new app.  I appreciate you guys working to figure this stuff out.

 

While I can see where someone reading this forum thread may have the impression there are lots of problems, however, there are really relatively few critical issues and we are working hard to correct them. 

Please don't take this as a cop out but, given the complexity of what is going on in the overall DCS system, we feel pretty good about how well the apps and WIU are holding up in the real world.  In our lab environment, we simply cannot replicate the diversity in your applications out there.  We expected issues and yes, there are some but, we've addressed the critical ones and soon, with the release of new WIU firmware and app updates, the majority of issues identified will be resolved.

Admittedly, to address each and every issue would delay the release longer than we are comfortable with.  So, let us get the critical items fixed over the next couple weeks and then we'll swing around and hit some of the nuisance issues.  After that, the real fun begins as we add new features and enhance the many we already have.  

The fun of running trains in this new and flexible way is only just beginning.  Stay tuned.

 

Last edited by MTH RD

Thanks for the update, MTHRD.  That softkey list loss has only happened to me once in several weeks of testing.

My observations is that, not only is what you say about android vs apple true, but there are diffferences between different android devices running different versions of android.  I can appreciate that this presents problems to MTH.

FYI, I started another thread "Multiple wifi units," so we users could interchange information about any special problems when using multiple wifis.  It seems us android users are the minority.  I'm looking forward to the app and firmware updates to see what issues they cure.

MTH RD posted:
hclarke posted:

Wow!  Lots of problems with new app.  I appreciate you guys working to figure this stuff out.

 

While I can see where someone reading this forum thread may have the impression there are lots of problems, however, there are really relatively few critical issues and we are working hard to correct them. 

Please don't take this as a cop out but, given the complexity of what is going on in the overall DCS system, we feel pretty good about how well the apps and WIU are holding up in the real world.  In our lab environment, we simply cannot replicate the diversity in your applications out there.  We expected issues and yes, there are some but, we've addressed the critical ones and soon, with the release of new WIU firmware and app updates, the majority of issues identified will be resolved.

Admittedly, to address each and every issue would delay the release longer than we are comfortable with.  So, let us get the critical items fixed over the next couple weeks and then we'll swing around and hit some of the nuisance issues.  After that, the real fun begins as we add new features and enhance the many we already have.  

The fun of running trains in this new and flexible way is only just beginning.  Stay tuned.

 

Do you have a beta program?  I'd be interested in helping out.

MTH RD, your second post was made while I was writing the above.  I agree that there are relatively few critical items.  Maybe I encounter more than the average operator because my layout is a bit complex---2 tius, 6 channels, 75 blocks, 38'x16'---and I wring out the capabilities.  I recognize that MTH has now gone into areas, apple and android and networking, where it doesn't have control of the operational devices.  Recognizing that MTH had limited ability to perform real world testing, I've been posting issues so you're aware of them and, more importantly for me, to pick the brains and experience of others.

I will say that I am encountering very few problems when I use my tablet.

I don't see how, unless they come up with a way to connect a wifi unit to the receiver, and since the receiver is no longer made, I doubt there's sufficient market.  Using the remote was handy, when I would correct aderailment on the far side of the layout, and could use the remote to reset the Z4000 breakers.  But until the $25 app is released, with the ability to control switches, the app is of limited usability..

willygee posted:
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.

20151102_221955

That is funny!

1'st issue with MTH WiFi. I am using the MTH home network. Engines are now in the inactive list. My iPad mini is connected to the MTH network, all 3 lights are on solid but there is no wifi connection to the TIU. The refresh button indicates no TIU found and the roster icon slowly fades in and out but the iPad  indicates the network is connected. From the get go the engines would all go into the inactive list when I closed down. I could however bring them into the active list by tapping and I ran trains but not now obviously. The TIU and remote still work just fine. Would this be in part related to the 'bug' referred to earlier? My initial thought was with the serial to usb cable but it was working fine and hasn't been touched or jogged.  Suggestions appreciated. FYI, glitches aside this is a great app and I am looking forward to more developments down the road.

Last edited by JimRK

Feedback. My issues do not reflect on the DCS hardware nor  the WiFi software.  Suggestion #1 didn't work. #2 did. Finally got hold of my 'IT' guy who knows and has worked on my stuff and indicated the problem was probably with my older style router. It would be prudent to upgrade and I will. The MTH mode works great but it is a little cumbersome as the DCS Companion says. A long overdue router will be in place next week. Barry thanks for giving your time and advice.

Add Reply

Post
The DCS Forum is sponsored by

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

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