MTH Wifi DCS App Updated Today (Version 3.2.0)

yea I just update dated my app yesterday when I saw the new update, just have not had a chance to try it out yet!

thanks for the information. what a great forum! 

Thanks Greg

Nice to know.  I've been waiting for these upgrades.  Good follow thru MTH !

Now to go and try it !

Dave

Nice fixes but the "Labour Bias" for Legacy does not work.

It did work at one time....then was lost.

A previous thread on OGR was discussing this and MTH did indicate it was an issue and would address it.

I guess not on this round.

Dave

Great!!!  Will try it out later!

Soo Line posted:

Nice fixes but the "Labour Bias" for Legacy does not work.

It did work at one time....then was lost.

A previous thread on OGR was discussing this and MTH did indicate it was an issue and would address it.

I guess not on this round.

Dave

Ouch. I didn’t notice labor bias stopped working. Hopefully they will pick up that correction on the next round. 

As always, when a new update becomes available, I optimistically hope that the app’s variable voltage control issues will be addressed. They are significant issues. The power that comes out is messed up. First, the power quality gets worse and worse at lower voltages, because it appears that the frequency not the voltage is being reduced. Ten volts should be ten volts. It is not meant to be twenty volts at 30Hz. Therefore, at lower voltages, my E-units and pullmor motors take a beating with all the jarring and rattling. That’s probably why the app won’t let you go below 5 volts as the power would be garbage. Secondly, there remains a severe latency issue causing the voltage to become randomly stuck as the TIU locks up and falls behind on processing instructions from the app, no matter how slowly or carefully you make adjustments.  Lastly, horns and whistles get stuck blowing full volume non stop using variable voltage for both post war and modern era Lionel equipment. There must be some kind of DC offset in the signal too. The variable voltage control is unusable. Instead, I assign a Lionel Legacy Powermaster as an engine and use it for variable voltage control without any of these issues. I don’t blame these issues on the app. I really think these issues may be the result of hardware limitations for the TIU. I don’t think its variable voltage processing circuits have been updated, ever since it came out 18 years ago.

GregR posted:

Soo Line posted:

Nice fixes but the "Labour Bias" for Legacy does not work.

It did work at one time....then was lost.

A previous thread on OGR was discussing this and MTH did indicate it was an issue and would address it.

I guess not on this round.

Dave

Ouch. I didn’t notice labor bias stopped working. Hopefully they will pick up that correction on the next round. 

As always, when a new update becomes available, I optimistically hope that the app’s variable voltage control issues will be addressed. They are significant issues. The power that comes out is messed up. First, the power quality gets worse and worse at lower voltages, because it appears that the frequency not the voltage is being reduced. Ten volts should be ten volts. It is not meant to be twenty volts at 30Hz. Therefore, at lower voltages, my E-units and pullmor motors take a beating with all the jarring and rattling. That’s probably why the app won’t let you go below 5 volts as the power would be garbage. Secondly, there remains a severe latency issue causing the voltage to become randomly stuck as the TIU locks up and falls behind on processing instructions from the app, no matter how slowly or carefully you make adjustments.  Lastly, horns and whistles get stuck blowing full volume non stop using variable voltage for both post war and modern era Lionel equipment. There must be some kind of DC offset in the signal too. The variable voltage control is unusable. Instead, I assign a Lionel Legacy Powermaster as an engine and use it for variable voltage control without any of these issues. I don’t blame these issues on the app. I really think these issues may be the result of hardware limitations for the TIU. I don’t think its variable voltage processing circuits have been updated, ever since it came out 18 years ago.

I think you are dead on (correct). I stopped using the TIU for conventional control for this reason. I think it is a hardware issue as well, not a software issue. It is the same with the remote. I like your idea of powermasters. I use a ZW-C, which has built-in powermasters. I should see how that works. I can control it from the TMCC remote but haven't tried it as a TMCC engine. 

George

just updated my app and I am just using the engine screen. no switches or accessories with it. when I first connected my andriod tablet to the wiu and powered up the layout. as usuall the screen shows no active engines. so with track power on I did an engine refresh and OH BOY almost every engine came up in the active list.

I only had 3 mth engines on the layout. one engine in the inactive list was one the track. also tmcc and legacy engines witch were on my shelf and no where near the track were in the active list. plus the lashup mute sound issue is still there. I would like also at some point also when building a consists that individual engine sounds could choosen such as the horn. as it is now if you want all engines in the consist to blow there horns you have to address the middle and tail engines and turn up thier horn volumes. only the lead engines horn sounds when a lashup is made. having the ability to choose that all engines horns sound when blowing the horn would be a lot easier than it is now. I like all my engine horns blowing at the same time in a consist it just makes for a cool sound experience,plus it make for a real loud show for visitors. 

also I was told by andy edelman that the volume sliders would get plus and minus symbols to either side of thier respective Dot like sliders to make it easier to set sound volumes to exact levels. that feature was not present. at least for me and my Android app update. it seems they made it worse rather than better. really hope they get this app right at some point as I really love using it. it is what got me back into mth engines again. 

I have been running my trains with an ipad mini, first generation.  When I tried to update the app to the latest version, 3.2 from 3.1, it says the app will not run on this operating platform.  The last operating system for 1st generation ipad mini is 9.3.5.  Apparently I am stuck with 3.1 on this device.  Version 3.2 requires iOS 10.0 or later.

gregr,are you using apple or andriod for the app? to all wifi andriod users please post how the new app version is working for you. 

Lionelzwl2012 posted:

gregr,are you using apple or andriod for the app? to all wifi andriod users please post how the new app version is working for you. 

 As requested.... I'm using an older Galaxy tablet that is Android. No problems so far. I did notice that it initialized a lot faster than the old version. Now I run just plain ol vanilla DCS so I can't tell you about all the advanced features but the MTH engine and the conventional engine I ran were fine... 

Lionelzwl2012 posted:

gregr,are you using apple or andriod for the app? to all wifi andriod users please post how the new app version is working for you. 

I am using the apple version.  

You mentioned that TMCC/Legacy engines were on the active list even though they were on shelves. This is actually related to an improvement in the app. It no longer deletes TMCC/Legacy items from the active engine list every time you refresh. Now these engines are both added and deleted manually. For example, if you had six TMCC engines on the track, and you wanted to add an MTH DCS engine, you would have to do a refresh to add it to the list. The app used to automatically delete all the TMCC engines and make you manually add them back to the list every time you refresh. Now it leaves them there until you choose to remove them. However, having said that, your app shouldn’t have added Lionel engines on a refresh. Hopefully, that was one time only bug when you first powered up after the update.

I don’t know about DCS engines, but a Lionel lashup will sound all horns if you assign the same TMCC ID to all engines in the lashup. You just can’t use the electrocouplers because they would all fire at the same time.

Is this just an update to the app or also a hardware update for the wifi unit?

Also, while I appreciate MTH upgrading this app, why don't they offer available upgrades automatically when the app is opened? Why is it necessary tht Android users be required to go to Google play each time they open this app to see whether there's a new version iavailable for download?

greg my active list not only showed lionel engines, but dcs engines not on the layout. also running two dcs engines in a lashup last nite. when I addressed the lashup and ajusted the overall volume. the lead engine was fine,but the tail engine got quieter. I had to address the tail engine bring its overall volume up and then go back to the consist. every time I ajusted the volume of the consist this happened. also when running a consist the mute button only mutes the lead engine. it has been that way in the previous version of the app. when these lashup bugs in andriod get sorted out. the app will be ok I belive at least for me.

ogaugeguy posted:

Is this just an update to the app or also a hardware update for the wifi unit?

Also, while I appreciate MTH upgrading this app, why don't they offer available upgrades automatically when the app is opened? Why is it necessary tht Android users be required to go to Google play each time they open this app to see whether there's a new version iavailable for download?

My android system via the google play store notification automatically notifies me when an update is available for download and install.  You can set your operating system (Android or iOs) or sometimes w/i each app to update automatically w/o notification or just receive the update available notification and select if you wish to update or not.

I was concerned that w/ this update you are now granting the app permission to access your photos/media/files.  Is this related to the "Added support for DCS playable horn" feature? I didn't update my version to 3.2.0.  Maybe I'm overcautious due to so many applications that want permission to access components/files/locations/router/IP etc. that often seem way beyond the function of the app's marketed purpose, rather it also serves as an information profile collector that is marketed to others.  For now, I'll take the wait and see approach w/ this update.

I have an Apple Mini4 and cannot update to the new level.  Any Ideas?

Bruce, 

My iPad Mini 4 updated just fine.

Soo Line posted:

Nice fixes but the "Labour Bias" for Legacy does not work.

It did work at one time....then was lost.

A previous thread on OGR was discussing this and MTH did indicate it was an issue and would address it.

I guess not on this round.

Dave

Could you please help us understand how you are using labor bias?  What is it you are attempting to do and how does it work with the Cab2?  We sometimes find behavior the same between Cab2 and the app, such as no diesel rev with speed in some engines.  It would help to know your exact application so we can duplicate it here.  Thanks.

Is there any official listing of the changes the new app implements?

George S posted:

GregR posted:

Soo Line posted:

Nice fixes but the "Labour Bias" for Legacy does not work.

It did work at one time....then was lost.

A previous thread on OGR was discussing this and MTH did indicate it was an issue and would address it.

I guess not on this round.

Dave

Ouch. I didn’t notice labor bias stopped working. Hopefully they will pick up that correction on the next round. 

As always, when a new update becomes available, I optimistically hope that the app’s variable voltage control issues will be addressed. They are significant issues. The power that comes out is messed up. First, the power quality gets worse and worse at lower voltages, because it appears that the frequency not the voltage is being reduced. Ten volts should be ten volts. It is not meant to be twenty volts at 30Hz. Therefore, at lower voltages, my E-units and pullmor motors take a beating with all the jarring and rattling. That’s probably why the app won’t let you go below 5 volts as the power would be garbage. Secondly, there remains a severe latency issue causing the voltage to become randomly stuck as the TIU locks up and falls behind on processing instructions from the app, no matter how slowly or carefully you make adjustments.  Lastly, horns and whistles get stuck blowing full volume non stop using variable voltage for both post war and modern era Lionel equipment. There must be some kind of DC offset in the signal too. The variable voltage control is unusable. Instead, I assign a Lionel Legacy Powermaster as an engine and use it for variable voltage control without any of these issues. I don’t blame these issues on the app. I really think these issues may be the result of hardware limitations for the TIU. I don’t think its variable voltage processing circuits have been updated, ever since it came out 18 years ago.

I think you are dead on (correct). I stopped using the TIU for conventional control for this reason. I think it is a hardware issue as well, not a software issue. It is the same with the remote. I like your idea of powermasters. I use a ZW-C, which has built-in powermasters. I should see how that works. I can control it from the TMCC remote but haven't tried it as a TMCC engine. 

George

There are a lot of points to respond to here so, I'll be general.  The GUI issues that cause things to pause, hang, etc., is an issue of too many commands for the system (WIU/TIU) to process too quickly.  Unfortunately, we can't do much about making the TIU a little quicker.  Hey, it's getting older like the rest of us.  We are looking at how to improve the user experience by essentially waiting for user's to stop making voltage changes before updating the TIU.  Well, you don't have to stop but, we'll effectively update at some rate the TIU can handle.  It should seem pretty seamless to the user.

The issues resulting from the AC waveform, etc., are not app related as George pointed out.  The TIU uses phase control (shark fin) as the AC signal and it isn't perfectly compatible with all the various engine platforms out there.  As a side note, the Z4K doesn't put out less than 5V either.  This is an old quasi standard that we followed and has nothing to do with changing frequency, etc.  

While you didn't see any progress in this update, hang in there.  We're working on some things that will address both of these.

MTH RD posted:

Soo Line posted:

Nice fixes but the "Labour Bias" for Legacy does not work.

It did work at one time....then was lost.

A previous thread on OGR was discussing this and MTH did indicate it was an issue and would address it.

I guess not on this round.

Dave

Could you please help us understand how you are using labor bias?  What is it you are attempting to do and how does it work with the Cab2?  We sometimes find behavior the same between Cab2 and the app, such as no diesel rev with speed in some engines.  It would help to know your exact application so we can duplicate it here.  Thanks.

MTH

On the Lionel Cab 2.  The EFX feature allows for intensive "labour" of an engine either steam or diesel in Legacy engines.  There are additional sounds and the smoke output is increased when you increase the EFX feature.

The Labour Bias did the same thing for Legacy engines and was active and present early in the app initially.  It worked well.

Then on the upgrade before this latest one it failed to be available and continues to be unavailable.

We did have a lengthy discussion on this in a previous thread.  I actually bought another phone just to make sure it was not on my end.  MTH at the time acknowledged that there was an issue with the app and would look into a fix on the next upgrade.

Thank you for taking the time to ask.

It is a nice feature and would hope you might be able to add it on the next round.

Dave

Lionelzwl2012 posted:

just updated my app and I am just using the engine screen. no switches or accessories with it. when I first connected my andriod tablet to the wiu and powered up the layout. as usuall the screen shows no active engines. so with track power on I did an engine refresh and OH BOY almost every engine came up in the active list.

I only had 3 mth engines on the layout. one engine in the inactive list was one the track. also tmcc and legacy engines witch were on my shelf and no where near the track were in the active list. plus the lashup mute sound issue is still there. I would like also at some point also when building a consists that individual engine sounds could choosen such as the horn. as it is now if you want all engines in the consist to blow there horns you have to address the middle and tail engines and turn up thier horn volumes. only the lead engines horn sounds when a lashup is made. having the ability to choose that all engines horns sound when blowing the horn would be a lot easier than it is now. I like all my engine horns blowing at the same time in a consist it just makes for a cool sound experience,plus it make for a real loud show for visitors. 

also I was told by andy edelman that the volume sliders would get plus and minus symbols to either side of thier respective Dot like sliders to make it easier to set sound volumes to exact levels. that feature was not present. at least for me and my Android app update. it seems they made it worse rather than better. really hope they get this app right at some point as I really love using it. it is what got me back into mth engines again. 

OK, so, I'll use this post to try and respond to everyone concerning the enhancements to the engine list(s).  Many of you asked to leave your lash ups and Legacy/TMCC engines active after a refresh.  So, we listened.  Now, when you build a DCS lash up, we no longer move the member engines to the inactive list.  If you want them there, you can move them.  If they are in the inactive list and you do a refresh/read, they will be come active again (assuming they are on the track).  Lionel engines, regardless if they are active or inactive, remain where you had them.  Since they can't respond to the DCS system, we just assume you have them where you want them and leave it alone.  This is how we should have handled things from the start.  

As far as varying volumes in lash ups, etc., this is unrelated to these changes and not something we see here.  Please just know engines can have very different actual volume levels at the same setting.  The lash up control is sending the same volume commands to all of your engines.

Blowing all the horns in a lash up is something we just don't offer and, to be honest, may never.  There is very little demand for doing this and considerable expense so, not really on our radar.  The work around you are using seems reasonable.  Sorry.  

GregR posted:

Lionelzwl2012 posted:

gregr,are you using apple or andriod for the app? to all wifi andriod users please post how the new app version is working for you. 

I am using the apple version.  

You mentioned that TMCC/Legacy engines were on the active list even though they were on shelves. This is actually related to an improvement in the app. It no longer deletes TMCC/Legacy items from the active engine list every time you refresh. Now these engines are both added and deleted manually. For example, if you had six TMCC engines on the track, and you wanted to add an MTH DCS engine, you would have to do a refresh to add it to the list. The app used to automatically delete all the TMCC engines and make you manually add them back to the list every time you refresh. Now it leaves them there until you choose to remove them. However, having said that, your app shouldn’t have added Lionel engines on a refresh. Hopefully, that was one time only bug when you first powered up after the update.

I don’t know about DCS engines, but a Lionel lashup will sound all horns if you assign the same TMCC ID to all engines in the lashup. You just can’t use the electrocouplers because they would all fire at the same time.

 

 

Wow!  This is some kind of magic!  Ha, ha..  In our testing, TMCC/Legacy engines remain where they are, active or inactive, after a refresh/read.  If your behavior is different, please let us know.

Nice work around for the TMCC lash up "all horn" feature.  

ogaugeguy posted:

Is this just an update to the app or also a hardware update for the wifi unit?

Also, while I appreciate MTH upgrading this app, why don't they offer available upgrades automatically when the app is opened? Why is it necessary tht Android users be required to go to Google play each time they open this app to see whether there's a new version iavailable for download?

This is a regular app update.  No update to the WIU is required.

Whether or not your app updates automatically is a local setting on your device.  We don't have any control over that.

Keystone posted:

ogaugeguy posted:

Is this just an update to the app or also a hardware update for the wifi unit?

Also, while I appreciate MTH upgrading this app, why don't they offer available upgrades automatically when the app is opened? Why is it necessary tht Android users be required to go to Google play each time they open this app to see whether there's a new version iavailable for download?

My android system via the google play store notification automatically notifies me when an update is available for download and install.  You can set your operating system (Android or iOs) or sometimes w/i each app to update automatically w/o notification or just receive the update available notification and select if you wish to update or not.

I was concerned that w/ this update you are now granting the app permission to access your photos/media/files.  Is this related to the "Added support for DCS playable horn" feature? I didn't update my version to 3.2.0.  Maybe I'm overcautious due to so many applications that want permission to access components/files/locations/router/IP etc. that often seem way beyond the function of the app's marketed purpose, rather it also serves as an information profile collector that is marketed to others.  For now, I'll take the wait and see approach w/ this update.

Huh.  I wasn't aware there was a change requiring users to grant permissions to your files.  I suspect this has something to do with Google and not us but, I'll look into it.  Maybe it should have been there before since the app can import/export data files.  I'm sure it has nothing to do with the playable horn.  Wait, what?  Playable horn?  Really?  What is that....?  ;-}

MTH RD, is there any listing of the changes or new features in this app?  The above posts seems to concentrate on running the other brand and on lash-ups.

I saw the list when updating the app, but I forget what was on it.  I've only used the app a little bit. 

Here is the list from the Google Play Store.

Thanks, michrr.

"Wait, what?  Playable horn?  Really?  What is that....?  ;-}"

So now MTH RD knows.

I discovered some Legacy features that were either included in this latest update or were there the whole time and I just discovered it. Maybe these have been previously posted but I thought I would share if any missed it like me.  By pulsing or rapidly tapping certain soft keys you can bring up or prolong certain Legacy sound features such as water tower operation, coal loading, steam injector sounds and steam release.  I’ve edited my soft keys on the attached photo so you can see which soft keys correspond to specific sounds.  With regards to the coal loading, the first sound will be a quick whistle blast, but as you continue to pulse the soft key the coal loading sounds will start until you stop.

rjsmithindy posted:

I discovered some Legacy features that were either included in this latest update or were there the whole time and I just discovered it. Maybe these have been previously posted but I thought I would share if any missed it like me.  By pulsing or rapidly tapping certain soft keys you can bring up or prolong certain Legacy sound features such as water tower operation, coal loading, steam injector sounds and steam release.  I’ve edited my soft keys on the attached photo so you can see which soft keys correspond to specific sounds.  With regards to the coal loading, the first sound will be a quick whistle blast, but as you continue to pulse the soft key the coal loading sounds will start until you stop.

Having to tap these soft keys repeatedly seems more like a bug. The software may not be sending a signal of adequate duration with a single button press. For example, in conventional mode, I often find myself having to tap the "bell" button 2 or 3 times rapidly, because the software doesn't emit a negative DC offset of sufficient duration to activate bells on many Lionel Engines.

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

Soo Line posted:

MTH RD posted:

Soo Line posted:

Nice fixes but the "Labour Bias" for Legacy does not work.

It did work at one time....then was lost.

A previous thread on OGR was discussing this and MTH did indicate it was an issue and would address it.

I guess not on this round.

Dave

Could you please help us understand how you are using labor bias?  What is it you are attempting to do and how does it work with the Cab2?  We sometimes find behavior the same between Cab2 and the app, such as no diesel rev with speed in some engines.  It would help to know your exact application so we can duplicate it here.  Thanks.

MTH

On the Lionel Cab 2.  The EFX feature allows for intensive "labour" of an engine either steam or diesel in Legacy engines.  There are additional sounds and the smoke output is increased when you increase the EFX feature.

The Labour Bias did the same thing for Legacy engines and was active and present early in the app initially.  It worked well.

Then on the upgrade before this latest one it failed to be available and continues to be unavailable.

We did have a lengthy discussion on this in a previous thread.  I actually bought another phone just to make sure it was not on my end.  MTH at the time acknowledged that there was an issue with the app and would look into a fix on the next upgrade.

Thank you for taking the time to ask.

It is a nice feature and would hope you might be able to add it on the next round.

Dave

Thanks for the further detail on the labor bias issue.  I just ran a Lionel Legacy steamer and regardless of speed, I can move the labor bias slider on the settings tab of the DCS app and hear the chuffing intensity change on the fly.  It works as I would have expected it to.  Now, on my Legacy diesel, I'm not hearing any change with the labor bias setting.  I'll try the diesel with the cab2 EFX feature and see what I get.  I do recall there being a previous discussion about this but, I don't recall the outcome.  Also, the issue isn't on any bug, feature, or enhancement lists that we have.  So, maybe it was tested on our Legacy steamer and believed to be working.  We'll pursue it further this time around.  Agree it's a cool feature.  I like it.  Are you using an Android or iOS device?

Hello Again MTH RD

Running Android 6.0

Here is a picture of my screen.  Running a Legacy Mallet and as you can see the BIAS just sits there with the number 8 beside it.  There is no slide bar to use.

Everything else seems to work and I have it fully upgraded to the recent release.

I also took a picture of the labor / drift button.  It goes "grey" with no function.  Not sure if that is the way it is suppose to be?  Due to lighting it is not grey in the picture but it is on screen.

Anyone reading this.......can you get the BIAS to work with Legacy?

Thanks

Dave

Soo Line posted:

Hello Again MTH RD

Running Android 6.0

Here is a picture of my screen.  Running a Legacy Mallet and as you can see the BIAS just sits there with the number 8 beside it.  There is no slide bar to use.

Everything else seems to work and I have it fully upgraded to the recent release.

I also took a picture of the labor / drift button.  It goes "grey" with no function.  Not sure if that is the way it is suppose to be?  Due to lighting it is not grey in the picture but it is on screen.

Anyone reading this.......can you get the BIAS to work with Legacy?

Thanks

Dave

 

So, my first advice is to ditch Android and get yourself an iPhone.  Just kidding.  Let me take a look with a couple of Android devices and OS revisions and see what we find.  By the way, I was just not hearing the subtle change in our Legacy diesel test engine.  Labor bias works just fine for both steam and diesel when running in iOS.

Well thanks for that MTH RD. 

Very curious to know your results using your Android device.

I suggest it is something on your end.  As mentioned before, I did have this feature with my Android device when I first bought and used MTH WIFI and then it disappeared.

In the last lengthy thread on this issue, MTH RD suggested I get another device to try.  Thinking it might be the phone I was using, I took it back to the store for a new one.

Still no results.

Thanks for following up.

Dave

brucefclark posted:

I have an Apple Mini4 and cannot update to the new level.  Any Ideas?

Hi Bruce:

Did you get this issue resolved? If so what was the solution?

Gary

MTH RD posted:

Soo Line posted:

Hello Again MTH RD

Running Android 6.0

Here is a picture of my screen.  Running a Legacy Mallet and as you can see the BIAS just sits there with the number 8 beside it.  There is no slide bar to use.

Everything else seems to work and I have it fully upgraded to the recent release.

I also took a picture of the labor / drift button.  It goes "grey" with no function.  Not sure if that is the way it is suppose to be?  Due to lighting it is not grey in the picture but it is on screen.

Anyone reading this.......can you get the BIAS to work with Legacy?

Thanks

Dave

 

So, my first advice is to ditch Android and get yourself an iPhone.  Just kidding.  Let me take a look with a couple of Android devices and OS revisions and see what we find.  By the way, I was just not hearing the subtle change in our Legacy diesel test engine.  Labor bias works just fine for both steam and diesel when running in iOS.

I have the iOS version. Labor bias works for Legacy steam, but did not work for 3 different Legacy diesels that I tried. 

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