MTH Wifi DCS App Updated Today (Version 3.2.0)

GregR posted:

@MTH RD I have a few suggestions:

1. Can we please move the + and - speed control buttons down the screen by about 1/4" to 3/8"? They are not in the way for DCS, Legacy, or TMCC32 speed dials. However, for default TMCC,  R100, and TAS speed control displays, both the + and - buttons overlap and conflict with the dial operation. It seems like every time my finger tries to latch onto that finicky speed dial needle, these buttons are in the way. This would also help solve a nasty issue for DCS and Legacy operation because the + button, at its present location,  is just WAY WAY too close (within a hair of touching off a 200 mph speed request). Every couple of days, I get an engine racing off when I accidentally miss the + button by a millimeter. Don't need the heart palpitations.

2. Can we get an option for linear (up-down) speed dials, similar to the variable voltage slider? I can't draw a perfect circle staring at a piece of paper, let alone trace a circle on my phone while looking up at a train. Don't get me wrong, the speed dials are beautiful, but a simple up-down motion of the thumb is more reliable for those of us who would rather look at our trains than a tablet or phone display.

3. Lashups: Can we please get the ability to EDIT lashups that have already been created? Every time I create a lashup, it takes multiple attempts and permutations of forward/backward, head/middle/rear before everything works. Wouldn't it be nice if we could click edit, and get back to that nice screen where we choose the components of the train and set positions and directions. Mistakes could be quickly corrected, instead of having to delete the whole lashup and start the entire process all over again.

4. Lashups Again: Can Lashups be identified with bold text, or a symbol next to their name for easy identification in the engine list?

4. Volume Control: The volume up/down buttons located at the bottom of the screen below the rev up/down  and boost/brake buttons do not work for TMCC locomotives, but they do work for Legacy locomotives. Can these buttons please be programmed to increase/decrease volume by sending the commands AUX1-1 and AUX1-4 respectively, when a TMCC locomotive is in operation?

OK, I'll try to reply to your list.  Please remind me of your device platform again.  Are you iOS or Android?

1. It is certainly possible to move the "+/-" speed buttons down or, wherever.  The problem becomes, if we move them down, they will be very close to the direction buttons on phones.  There seems to be room on tablets but, for phones, things get crowed.  For DCS engines, you can set a max speed that avoids the 120 smph tap on the speedo bezel.  With regard to "infinite" dials like default TMCC, R100, and TAS, the needle doesn't interfere with the "+/-" buttons.  Once you have control over the needle, the buttons are ignored.  I can see if you stopped the needle directly on one of the buttons but, in this case, if you just tap an hold the needle slightly above the buttons, it works just fine.  I'm not sure how many people use the "+/-" buttons to run their trains but, I certainly agree, it would be nice if there were more room.  I suppose, we could look at reducing the relative size of the speedometer but, many/most really like this form of control.  I've looked at it again at your suggestion and can see your point.  Let me soak on this one and get some more feedback from other users.  
2. Sure, linear speed control options would be relatively easy.  We could use the conventional control sliders for example.  There is probably around $5K in software time to offer this option.  So, this is where the steel hits the rails.  And it sparks.  There is a ton of really cool stuff, options, etc., we could do if only our budget was unlimited.  I hear you on this preference but, I have to say, it would take a lot more customers requesting it to make the light of day.  Sorry.
3. The same cost barrier in #2 above applies to editing lash ups.  It takes seconds to build a DCS lash up.  If I screw it up and have to build it again, it's really not that cumbersome.  Again, I hear you though and appreciate your suggestions.
4. The volume buttons on the secondary control screen (below the main engine control screen) work OK on our TMCC test engines here in both iOS and Android platforms.  There are only like 4 volume steps but, they work the same as using the aux1-1 (vol up) and aux1-4 (vol down) buttons. 

Again, please help me out and give me more details about your device, OS, revision level, etc.  We only have a cross-section of TMCC and Legacy test engines.  We see behavior vary across them depending upon when they were built, etc.  In the current app and using current Lionel engines, things seem to work OK.  Well, we confirmed the labor bias is broken in Android.  While doing so, we found a couple of other little cuties that we'll fix as well.  I'm surprised nobody reported them.

Again, I thank you for your patronage and taking the time to make suggestions.  It's not that we won't do any of them but, I hope you can understand that we are unable to do everything anyone requests.  It just isn't feasible.

@MTH RD

Thank you for your thoughtful replies. I certainly understand that improvements are carefully selected. It all takes time and money. 

One last suggestion on the +/- speed buttons. How about a max speed setting for Legacy engines Just like DCS? No more deadly 200mph touch. My mustang dial goes up to 160mph.  Either one at full speed results in a crash or jail time.

I am using an iPhone 8 and iPad Mini. iOS 12. Latest versions of app, TIU and WIU firmware. I am hooked up to Legacy system via SER2 and proper cables. I enjoy challenging the DCS app to operate DCS, Legacy/TMCC, and conventional equipment of every imaginable vintage. Sorry, but I love trying to break your app in ways never imagined.

I wouldn’t invest too much time in trying to resolve every irregularity with TMCC/Legacy equipment. Each one is a one of a kind unicorn.  I know that I am happy as things work on the majority of engines.

I was excited about your ideas to handle the variable voltage issues. I think the idea of throttling back on the data speed to the TIU’s slow brain is terrific. Like, maybe the faster a user moves the slider, the more the resolution of voltage increments decreases to have larger less frequent voltage steps.

Thanks again for all your hard work and outstanding efforts to listen and consider ideas from your hardcore users. Much appreciated. 

PS: I used to be a strictly Lionel guy but I have been buying more and more MTH equipment directly as a result of this terrific app that unifies control of all my equipment.

Gary I have had NO luck in updating my Apple I will take it to York next week and maybe a Apple guru can help.  Bruce

brucefclark posted:

Gary I have had NO luck in updating my Apple I will take it to York next week and maybe a Apple guru can help.  Bruce

Hi Bruce:

I would like to suggested you call Apple Care at: 1-800-275-2273 and ask for a Senior Advisor on iPad Mini using Apps.  These folks maybe able to help. Do not work with a level one Advisor they will tell you to delete the MTH DCS Wi-Fi App and re-install, not a good plan.

If you live near an Apple Store go as a walk-in and see if someone can help or better yet make an appointment with your Apple Store for the Genius Bar at the back of the store.

I had this similar issue with my ‘Carrier App’, that operates my furnace and air conditioning.

Hope this helps. Gary

Soo Line posted:

Thanks Greg

You wouldn't have an Android device you could try. ...... ?

Or if anyone else can chime in on Labor Bias for Legacy engines using Android.

Just trying to determine if it's on my end or MTH.....I'm thinking it's on MTHs side.

Thanks

Dave

Sorry if you didn't see my reply to Greg.  Labor bias is definitely broken in Android.  It's fine (at least here) using iOS.  Even with our test diesels.  Lionel has had several significant hardware changes over the years and there are differences in how the engines respond to the same commands.  We have a BN SD45 and labor bias using the iOS works.  It's subtle and a little delayed but, it works.  I can't guess why it wouldn't work on other Legacy diesels.  Same commands are being sent to all.  We'll sort it out eventually.

brucefclark posted:

Gary I have had NO luck in updating my Apple I will take it to York next week and maybe a Apple guru can help.  Bruce

If your iPad mini is running iOS 9 you cannot update to the latest version of the app.  It stinks, I know.  My iPad mini is older and cannot go beyond iOS 9 either.  We are doing some testing to see if the app will run OK on iOS 9.  If so, we'll do an update.  However, because of how Apple handles these things, this might only be a one-time reprieve.  In short order, we'll have to leave older iOS operating systems behind.  

Did the accel/decel rate adjustment for consists ever get addressed? It's nice to set the accel to 1 so when an engine takes off in the wrong direction, it doesn't immediately tear a whole train apart. 

I know, I know, that isn't something that happens. 

I just need to swap out about ten or twelve G scale electro couplers from it happening..... (or not happening).

Anyone want just one direction button that changes color depending on what direction you are in?  That's the only gripe I have with the layout of the app when using an Ipad,  Left on one side and Right on the other, drives me nuts.  Would be better with an smart phone also.

MTH RD posted:

Soo Line posted:

Thanks Greg

You wouldn't have an Android device you could try. ...... ?

Or if anyone else can chime in on Labor Bias for Legacy engines using Android.

Just trying to determine if it's on my end or MTH.....I'm thinking it's on MTHs side.

Thanks

Dave

Sorry if you didn't see my reply to Greg.  Labor bias is definitely broken in Android.  It's fine (at least here) using iOS.  Even with our test diesels.  Lionel has had several significant hardware changes over the years and there are differences in how the engines respond to the same commands.  We have a BN SD45 and labor bias using the iOS works.  It's subtle and a little delayed but, it works.  I can't guess why it wouldn't work on other Legacy diesels.  Same commands are being sent to all.  We'll sort it out eventually.

Yes MTH RD.  I did see that sentence buried in your response to Greg.

Thank You for that.

Will look forward to a fix on the next upgrade.....

Really appreciate your correspondence with us here on OGR.

Dave

MTH RD, While I have not made any suggestions, I have been following along.  I also really appreciate you taking the time to work with all the folks here on the OGR Forum.  You are doing what so many consumers wish companies would do to make their products better and customers happier!

I called Apple and it looks like I have the update BUT when I look at the app info in the apt it still shows 3.1  Where do I go [ how do I get there when I open the apt ] to find what level I am at?  Thanks Bruce

brucefclark posted:

I called Apple and it looks like I have the update BUT when I look at the app info in the apt it still shows 3.1  Where do I go [ how do I get there when I open the apt ] to find what level I am at?  Thanks Bruce

Bruce,

When you open the app, click on the "More" button which is located in the bottom right corner of your screen (it is part of the ribbon along the bottom which also has the Engines, Track, Switches, etc commands.

Then press "App Settings"

Look at the bottom of your screen. The version number will be displayed.

@MTH RD

Suggestion: Would you please consider using variable length strings instead of fixed (16-character) strings for holding engine and lashup names? There is plenty of real estate on screen to let us have more text, but I keep fighting to use creative abbreviations to avoid getting truncated by the app. My god, it's not FORTRAN   And, when you click "edit" on an engine name, could we please have that field pre-filled with the current name instead of retyping?

Thanks,

Greg Reinke

We did the upgrade on the day MTH released the new version 3.2.0.  This has given us several days to ‘RUN MY TRAINS’. We have both Lionel TMCC and MTH locomotives on our layout.  We found no issues to report to MTH, all is working as advertised. We are using an iPhone 7 Plus, IOS 12.0.1with twenty locomotives on the MTH • DCS Wi-Fi.

Today my grandchildren were over and we ran some trains. Ages 3 & 4 and they like this system and they have learned how to share because I only have one iPhone. When their Dad stays we use his android phone.

Wait there is more. After hanging out in the train room we played out side. In the sand and making bubbles.

Some screenshots from the install process.

Gary

Looks like we could all learn how to use it from the grandsons!

Mark not only that, but it sure seams like when they come over Gary has a lot more fun the normal! We could probably learn something from that also! Maybe I need to let my grandkids run the roost! LOL

All in fun Gary, sure looks like a great time!

You are right, Mike!  You get your grandchildren to run the roost, and I’ll find some grandchildren to adopt!  LOL

Mark Boyce posted:

You are right, Mike!  You get your grandchildren to run the roost, and I’ll find some grandchildren to adopt!  LOL

Careful Mark, you may want to try them out first! LOL

You’re right Mike!  I’ll have to give them a probationary period!

Engineer-Joe posted:

Did the accel/decel rate adjustment for consists ever get addressed? It's nice to set the accel to 1 so when an engine takes off in the wrong direction, it doesn't immediately tear a whole train apart. 

I know, I know, that isn't something that happens. 

I just need to swap out about ten or twelve G scale electro couplers from it happening..... (or not happening).

Hey, sorry for the delayed response.  I just can't get out here as much as I would like. 

I don't think we've really taken a serious look at it but, I will.  I can tell you this.  If it requires even moderate TIU code modifications, we would be pretty hesitant.  The TIU code is old and tired.  It doesn't like to be messed with.   If we can do this with GUI changes to the app, etc., then we might get it done.  Stay tuned.

GregR posted:

@MTH RD

Suggestion: Would you please consider using variable length strings instead of fixed (16-character) strings for holding engine and lashup names? There is plenty of real estate on screen to let us have more text, but I keep fighting to use creative abbreviations to avoid getting truncated by the app. My god, it's not FORTRAN   And, when you click "edit" on an engine name, could we please have that field pre-filled with the current name instead of retyping?

Thanks,

Greg Reinke

Reasonable suggestions Greg.  We've retained the 16 character names to try and retain some compatibility with the remote.  But, as  time rolls on, this will become less and less of an issue.

For the edit engine name issue, I think we intended this as more of a rename engine than edit.  I mean, c'mon, it's 16 characters.  It isn't a novel!  But, the change shouldn't be a big deal.  I'll get it on a list but, it's probably not gonna get a high priority.  Sorry.

Thank you MTH!

I have updated my Android device to the new version of the DCS Wifi Ap.  So far, no issues at all.  I can quill the whistle on my only Legacy locomotive and everything is working as it should.

Very nice that the TMCC and Legacy locomotives do not drop off of the active list anymore!

I also say "Thank you MTH!"

I can’t get my Lionel engine to run on the premium app. I think it’s the U wire going from my Legacy 990 to the same u wire that goes to the track.

when i connect the 990 the tiu flashes on the wiu.

my Mth engine works but won’t pick my brand new sw7