Dsc wifi operational quirks... have any? Lets post them here and discusse them.

BobbyD posted:

MTH RD posted:

All,

Sorry to be tardy on replying to issues raised in this link.  We've been pretty busy with a variety of new projects as well as enhancements to the app.  Here's a brief response to the issues and some insights that hopefully will help clarify some things.  First, the issues.

With regard to the engine sounds on/off toggle (mute) this only applies to the head engine.  This is true in both the remote and the app.  To be honest, I'm not sure why.  We're going to look into this as I see no reason why we can't mute all the engines in a lash up.  We simply turn the volume down.

Lash Up Accel/Decel: This seems reasonable to add.  We can get it on the list and will try to implement relative to demand.

 

So, please know that we very much intend to continue to improve and enhance the DCS system and continue to take it and all of our products forward with new and exciting features and benefits.  We probably need to think about how to better communicate with you guys, the community, our customers, about what we are doing and why we are doing it.  I'll give that some thought.  In the meantime, I hope I've at least offered some answers and helped with a general understanding of tech development priorities at MTH.  

Thanks.

 

Realize everyone is going gaga over the WIU and that is your focus now, is it possible to have the grade crossing sounds added into lash ups? They retain both the Forward two toots (which I can manually do:-) and Reverse sounds sequence yet drop out the near impossible to duplicate grade crossing sequence!

Thank you!

Seems like a reasonable request.  I'll put it on the list of feature enhancements.  

@T1Titan_ZachF posted:

REQUEST TIMED OUT!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

"No TIUS or WIUs found"!!!! But they are turned on and connected!???? This is a big problem at my club layout. 

I can imagine this being an issue.  I wouldn't put up with it.  So, let's find the cause.  If the device is connected to the same network as the WIU and the TIU is powered up, this should be a very rare occurrence.   As Barry suggested, try resetting the WIU.  Also, try to focus on troubleshooting when the system gets in this mode.  I know when it happens to me, it's almost always my fault.  I cycled power on the WIU and my device auto connected to a different network.  Or, I killed power to  the TIU and the WIU can't talk to it since it's connected via USB/Serial adapter.  Etc., etc.  

This cannot be a common issue or, we couldn't sell the product.  I'll bet there is some oversight.  Maybe try having one WIU and TIU powered up and run that way for a while.  And then, if all goes well, add in more WIU/TIU combinations.  In other words, start small and work up and see if you can find what has changed when the failure occurs.  

Just my $0.02.

Oh, and one more thing.  Please make sure all of your WIUs, TIUs, and apps are fully updated to the latest revisions of firmware.  There can be issues with mixed versions across devices.

Maxrailroad posted:

Signal cuts in and out for DCS all around my layout. Also programming trains only works on certain spots on my track. 

It would seem you have general signaling issues.  There is much to suggest and try here starting with making sure you have reasonably clean track and trains.  Barry's book does a good job of getting into the common causes of weak signals.  Maybe give that a read and I'm pretty sure you'll find your culprit.  

There are 2000 sqft layouts running reliably with DCS.  It's just a question of getting the fundamentals in order.

MTH RD posted:

Even if you have the input voltage to the TIU var channels at say, 20VAC, if you just set your starting voltage to maybe 21VAC, you will have the full 20VAC on the rails and there really isn't any need to go in and max them out.  I'm just offering an idea for a work around that alleviates you having to go in and turn the voltage up that last 0.5VAC.  It probably isn't necessary.

WHOA!!!

That's not how it works on the TIU for the Variable channels. Really the VAR1 & 2 operate as a percentage output of the available input voltage. So if I have 20VAC on VAR1 Input and increase VAR1output to 21VAC my real output voltage is only 95% of the available input and so I only get 19.1 volts coming out of VAR1. Only until I max the voltage to 22 volts will the TIU give me the full 100% input voltage to the output side of the TIU (and the sine wave is no longer chopped).

The issue is that the TIU always assumes that there is 22 volts coming in to the VARIABLE inputs when that isn't the case for everyone.  I really wish that we could change / inform the app & DCS remote what the input voltage is so that when we run conventional, 12 volts is really 12 volts. Right now I have 18 volts in and when I set the TIU to 12 volts the actual output voltage is just below 10.

But as you said earlier, this issue is deep in the code, my rev. G & L have both done this no matter the version of the firmware, and the problem is easy to mitigate.

MTH RD posted:

BobbyD posted:

MTH RD posted:

All,

Sorry to be tardy on replying to issues raised in this link.  We've been pretty busy with a variety of new projects as well as enhancements to the app.  Here's a brief response to the issues and some insights that hopefully will help clarify some things.  First, the issues.

With regard to the engine sounds on/off toggle (mute) this only applies to the head engine.  This is true in both the remote and the app.  To be honest, I'm not sure why.  We're going to look into this as I see no reason why we can't mute all the engines in a lash up.  We simply turn the volume down.

Lash Up Accel/Decel: This seems reasonable to add.  We can get it on the list and will try to implement relative to demand.

 

So, please know that we very much intend to continue to improve and enhance the DCS system and continue to take it and all of our products forward with new and exciting features and benefits.  We probably need to think about how to better communicate with you guys, the community, our customers, about what we are doing and why we are doing it.  I'll give that some thought.  In the meantime, I hope I've at least offered some answers and helped with a general understanding of tech development priorities at MTH.  

Thanks.

 

Realize everyone is going gaga over the WIU and that is your focus now, is it possible to have the grade crossing sounds added into lash ups? They retain both the Forward two toots (which I can manually do:-) and Reverse sounds sequence yet drop out the near impossible to duplicate grade crossing sequence!

Thank you!

Seems like a reasonable request.  I'll put it on the list of feature enhancements.  

I thought this was an older issue introduced with the remote and was said to be dependent on, if the lead engine had the crossing signals or not?

MTH RD posted:

Soo Line posted:

Thank You MTH for your responses.

I would like to add the following WIU issue:

I have lost LABOUR BIAS on Legacy Engines.

It was present right from the beginning when I installed my WIU months ago.

WIU version is 1.1

DCS,  both TIU and Remote are 6.10  -  Rev L  -  new system prior to WIU.

Everything is hooked up properly and as mentioned was working perfectly.

Here is a pic of my screen in Legacy.......that is all I now get.  The digit will sometimes change to 8.  The "graph" or slide button used to increase or decrease BIAS is gone.

I've done nothing to alter or made any changes to my system or layout.

I have refreshed and "Uninstalled" and "Reinstalled" the app.....no change.

Thanks for considering this matter.

 

First, sorry about this.  It appears you have found some ugly bug.  Have you tried resetting the app?  If you have engines, etc., that you don't want to lose, export them and then import after the reset.  But, first, before the import, see if the labor bias feature is corrected.  This is some kind of odd glitch in the app or your device.  Try power cycling the device also.  The fact the app is displaying incorrectly is very odd.  

Is this iOS or Android?  What version of the app?  

Thanks for your reply.

I have reset the App....no change.

App version 3.1.0 Build 49

Android 5 with no sim card.  Bought exclusively to use with the WIU.

Again....the LABOUR BIAS was working fine with my Legacy engines.

Any other thoughts on what I might try?

Thank You

Soo Line posted:

MTH RD posted:

Soo Line posted:

Thank You MTH for your responses.

I would like to add the following WIU issue:

I have lost LABOUR BIAS on Legacy Engines.

It was present right from the beginning when I installed my WIU months ago.

WIU version is 1.1

DCS,  both TIU and Remote are 6.10  -  Rev L  -  new system prior to WIU.

Everything is hooked up properly and as mentioned was working perfectly.

Here is a pic of my screen in Legacy.......that is all I now get.  The digit will sometimes change to 8.  The "graph" or slide button used to increase or decrease BIAS is gone.

I've done nothing to alter or made any changes to my system or layout.

I have refreshed and "Uninstalled" and "Reinstalled" the app.....no change.

Thanks for considering this matter.

 

First, sorry about this.  It appears you have found some ugly bug.  Have you tried resetting the app?  If you have engines, etc., that you don't want to lose, export them and then import after the reset.  But, first, before the import, see if the labor bias feature is corrected.  This is some kind of odd glitch in the app or your device.  Try power cycling the device also.  The fact the app is displaying incorrectly is very odd.  

Is this iOS or Android?  What version of the app?  

Thanks for your reply.

I have reset the App....no change.

App version 3.1.0 Build 49

Android 5 with no sim card.  Bought exclusively to use with the WIU.

Again....the LABOUR BIAS was working fine with my Legacy engines.

Any other thoughts on what I might try?

Thank You

I'm afraid I don't have much to offer here.  Clearly, the device and app have some issue with displaying the screen correctly.  If you uninstall and reinstall the app and have the same issue, then we have to start looking at the device and the OS on that device.  If your device is exclusive for running the trains I wonder if you could reset it.  I'll discuss this further with our app developers but, at the same time, you can see how this is isolated to your device.  We've never heard of anything like this before.  Try deleting the app, resetting the device, and then reinstalling the app.  Sorry, I don't have much more to offer on this.

Engineer-Joe posted:

MTH RD posted:

BobbyD posted:

MTH RD posted:

All,

Sorry to be tardy on replying to issues raised in this link.  We've been pretty busy with a variety of new projects as well as enhancements to the app.  Here's a brief response to the issues and some insights that hopefully will help clarify some things.  First, the issues.

With regard to the engine sounds on/off toggle (mute) this only applies to the head engine.  This is true in both the remote and the app.  To be honest, I'm not sure why.  We're going to look into this as I see no reason why we can't mute all the engines in a lash up.  We simply turn the volume down.

Lash Up Accel/Decel: This seems reasonable to add.  We can get it on the list and will try to implement relative to demand.

 

So, please know that we very much intend to continue to improve and enhance the DCS system and continue to take it and all of our products forward with new and exciting features and benefits.  We probably need to think about how to better communicate with you guys, the community, our customers, about what we are doing and why we are doing it.  I'll give that some thought.  In the meantime, I hope I've at least offered some answers and helped with a general understanding of tech development priorities at MTH.  

Thanks.

 

Realize everyone is going gaga over the WIU and that is your focus now, is it possible to have the grade crossing sounds added into lash ups? They retain both the Forward two toots (which I can manually do:-) and Reverse sounds sequence yet drop out the near impossible to duplicate grade crossing sequence!

Thank you!

Seems like a reasonable request.  I'll put it on the list of feature enhancements.  

I thought this was an older issue introduced with the remote and was said to be dependent on, if the lead engine had the crossing signals or not?

Yes, the xing signal sounds would come from the head engine so, if it didn't have the feature, it wouldn't play.  But, for all the engines that have it, I don't see a problem adding the softkey.  That said, the softkey would be there for engines that didn't include it and we'll get calls and reports about how the feature doesn't work on some lash ups.  There is no really good way to communicate these nuances to everyone so, we have to make judgement calls all the time.  

Engineer-Joe posted:

…..

I'm having different issues with large consists of mixed PS2 and PS3 engines after power cycles. I noticed it with the remote too so I was leaning towards this DCS version. I gave up searching and try to limit it's use. Overall, my app is working very well. Our grandson still prefers the app so it must be good.

I keep getting replies about signal strength or an engine that maybe not responding to commands from outside reasons like dirty track, etc.

The thing here is that when the mixed PS2 and PS3 consist is built, it works fine. It's after power cycling, or trying to run it days later for example, the consist won't work. I have to rebuild the consist. It seems that it's always the PS2 trailing or middle engines that get confused over directions or even lost by the software.

 There was an instance where even the lead PS3 engine, got scrambled and had to be reset. On another occasion, a middle PS2 engine was lost and it took about a week for me to get the engine to be able to be recognized by the system again. It had a good battery and ran fine in conventional.

 I traced and searched for the reasons for weeks and ended up abandoning the use of mixed consists of PS2 and PS3 for the growing pains of these types of results. I get replies of it's my fault (poor conditions) and I have ruled that out time and time again. I can run 6 O scale all PS3 engines or several all PS2 consists without these issues.

 I think my next test should have been an all PS2 with at least 6 engines but to be frank, I'm tired of researching and shooting myself in the foot, only to come here with results that get bashed down to my problem only.

 You should poll users (ones who run large consists) on what DCS version they are using, who have resisted upgrading because of these poor consist results.

MTH RD posted:

Engineer-Joe posted:

MTH RD posted:

BobbyD posted:

MTH RD posted:

All,

Sorry to be tardy on replying to issues raised in this link.  We've been pretty busy with a variety of new projects as well as enhancements to the app.  Here's a brief response to the issues and some insights that hopefully will help clarify some things.  First, the issues.

With regard to the engine sounds on/off toggle (mute) this only applies to the head engine.  This is true in both the remote and the app.  To be honest, I'm not sure why.  We're going to look into this as I see no reason why we can't mute all the engines in a lash up.  We simply turn the volume down.

Lash Up Accel/Decel: This seems reasonable to add.  We can get it on the list and will try to implement relative to demand.

 

So, please know that we very much intend to continue to improve and enhance the DCS system and continue to take it and all of our products forward with new and exciting features and benefits.  We probably need to think about how to better communicate with you guys, the community, our customers, about what we are doing and why we are doing it.  I'll give that some thought.  In the meantime, I hope I've at least offered some answers and helped with a general understanding of tech development priorities at MTH.  

Thanks.

 

Realize everyone is going gaga over the WIU and that is your focus now, is it possible to have the grade crossing sounds added into lash ups? They retain both the Forward two toots (which I can manually do:-) and Reverse sounds sequence yet drop out the near impossible to duplicate grade crossing sequence!

Thank you!

Seems like a reasonable request.  I'll put it on the list of feature enhancements.  

I thought this was an older issue introduced with the remote and was said to be dependent on, if the lead engine had the crossing signals or not?

Yes, the xing signal sounds would come from the head engine so, if it didn't have the feature, it wouldn't play.  But, for all the engines that have it, I don't see a problem adding the softkey.  That said, the softkey would be there for engines that didn't include it and we'll get calls and reports about how the feature doesn't work on some lash ups.  There is no really good way to communicate these nuances to everyone so, we have to make judgement calls all the time.  

I understood that the soft keys followed the locomotives, that is not the case? So if the engine doesn't have the feature by itself, why would the soft key magically appear when it is the lead engine of a "lash-up" then?

In any event these two Proto 3 engines when double headed in "lash-up" lose the outstanding Grade Crossing signal. (which Lionel doesn't have) Guests who are not model train buffs love it, and for regulars it allows them to signal for grade crossings and immediately return to avoiding the crash that is about to occur. How many MTH engines don't have that feature now? And from how many years ago? In a post by Dave Hikel on 08/12/13 he says the SXS came out in 2005 Proto 2 engines. That is going to be 14 years, and thousands of engines ago!!!

Time to put the Lash-up SXS soft key in!!  (Even if it is going to require a painful round of software updating...)

MTH RD posted:

Soo Line posted:

MTH RD posted:

Soo Line posted:

Thank You MTH for your responses.

I would like to add the following WIU issue:

I have lost LABOUR BIAS on Legacy Engines.

It was present right from the beginning when I installed my WIU months ago.

WIU version is 1.1

DCS,  both TIU and Remote are 6.10  -  Rev L  -  new system prior to WIU.

Everything is hooked up properly and as mentioned was working perfectly.

Here is a pic of my screen in Legacy.......that is all I now get.  The digit will sometimes change to 8.  The "graph" or slide button used to increase or decrease BIAS is gone.

I've done nothing to alter or made any changes to my system or layout.

I have refreshed and "Uninstalled" and "Reinstalled" the app.....no change.

Thanks for considering this matter.

 

First, sorry about this.  It appears you have found some ugly bug.  Have you tried resetting the app?  If you have engines, etc., that you don't want to lose, export them and then import after the reset.  But, first, before the import, see if the labor bias feature is corrected.  This is some kind of odd glitch in the app or your device.  Try power cycling the device also.  The fact the app is displaying incorrectly is very odd.  

Is this iOS or Android?  What version of the app?  

Thanks for your reply.

I have reset the App....no change.

App version 3.1.0 Build 49

Android 5 with no sim card.  Bought exclusively to use with the WIU.

Again....the LABOUR BIAS was working fine with my Legacy engines.

Any other thoughts on what I might try?

Thank You

I'm afraid I don't have much to offer here.  Clearly, the device and app have some issue with displaying the screen correctly.  If you uninstall and reinstall the app and have the same issue, then we have to start looking at the device and the OS on that device.  If your device is exclusive for running the trains I wonder if you could reset it.  I'll discuss this further with our app developers but, at the same time, you can see how this is isolated to your device.  We've never heard of anything like this before.  Try deleting the app, resetting the device, and then reinstalling the app.  Sorry, I don't have much more to offer on this.

Once  again ....Thank You for your reply.

I have since reset my new phone .....uninstalled and reinstalled the App ....again.

I have done all I can and have followed all instructions.

All my MTH equipment if fully updated.

It must be in the WIU.

Will MTH exchange my WIU for another?  Mine is barely 6 months old with very little home use.

Thank You

Yes, and I would like it in there too.

Yet I know there will be several posters who immediately complain that it does not work. They will probably be people who have a couple of engines and just happen to put the lead engine with one that does not have that feature. 

Soo Line posted:

MTH RD posted:

Soo Line posted:

MTH RD posted:

Soo Line posted:

Thank You MTH for your responses.

I would like to add the following WIU issue:

I have lost LABOUR BIAS on Legacy Engines.

It was present right from the beginning when I installed my WIU months ago.

WIU version is 1.1

DCS,  both TIU and Remote are 6.10  -  Rev L  -  new system prior to WIU.

Everything is hooked up properly and as mentioned was working perfectly.

Here is a pic of my screen in Legacy.......that is all I now get.  The digit will sometimes change to 8.  The "graph" or slide button used to increase or decrease BIAS is gone.

I've done nothing to alter or made any changes to my system or layout.

I have refreshed and "Uninstalled" and "Reinstalled" the app.....no change.

Thanks for considering this matter.

 

First, sorry about this.  It appears you have found some ugly bug.  Have you tried resetting the app?  If you have engines, etc., that you don't want to lose, export them and then import after the reset.  But, first, before the import, see if the labor bias feature is corrected.  This is some kind of odd glitch in the app or your device.  Try power cycling the device also.  The fact the app is displaying incorrectly is very odd.  

Is this iOS or Android?  What version of the app?  

Thanks for your reply.

I have reset the App....no change.

App version 3.1.0 Build 49

Android 5 with no sim card.  Bought exclusively to use with the WIU.

Again....the LABOUR BIAS was working fine with my Legacy engines.

Any other thoughts on what I might try?

Thank You

I'm afraid I don't have much to offer here.  Clearly, the device and app have some issue with displaying the screen correctly.  If you uninstall and reinstall the app and have the same issue, then we have to start looking at the device and the OS on that device.  If your device is exclusive for running the trains I wonder if you could reset it.  I'll discuss this further with our app developers but, at the same time, you can see how this is isolated to your device.  We've never heard of anything like this before.  Try deleting the app, resetting the device, and then reinstalling the app.  Sorry, I don't have much more to offer on this.

Once  again ....Thank You for your reply.

I have since reset my new phone .....uninstalled and reinstalled the App ....again.

I have done all I can and have followed all instructions.

All my MTH equipment if fully updated.

It must be in the WIU.

Will MTH exchange my WIU for another?  Mine is barely 6 months old with very little home use.

Thank You

It's highly unlikely the WIU could somehow distort a specific graphic in the app display.  It literally has no way to do that.  So, before you take that path, load the app on another device, a friend or family member's phone, whatever, and I'm pretty sure you will see the issue resolved.  You can log into your Google account on another device and then you won't need to purchase another copy of the app.  

What is the specific device having this issue?  What brand, model, etc?  

MTH RD posted:

Soo Line posted:

MTH RD posted:

Soo Line posted:

MTH RD posted:

Soo Line posted:

Thank You MTH for your responses.

I would like to add the following WIU issue:

I have lost LABOUR BIAS on Legacy Engines.

It was present right from the beginning when I installed my WIU months ago.

WIU version is 1.1

DCS,  both TIU and Remote are 6.10  -  Rev L  -  new system prior to WIU.

Everything is hooked up properly and as mentioned was working perfectly.

Here is a pic of my screen in Legacy.......that is all I now get.  The digit will sometimes change to 8.  The "graph" or slide button used to increase or decrease BIAS is gone.

I've done nothing to alter or made any changes to my system or layout.

I have refreshed and "Uninstalled" and "Reinstalled" the app.....no change.

Thanks for considering this matter.

 

First, sorry about this.  It appears you have found some ugly bug.  Have you tried resetting the app?  If you have engines, etc., that you don't want to lose, export them and then import after the reset.  But, first, before the import, see if the labor bias feature is corrected.  This is some kind of odd glitch in the app or your device.  Try power cycling the device also.  The fact the app is displaying incorrectly is very odd.  

Is this iOS or Android?  What version of the app?  

Thanks for your reply.

I have reset the App....no change.

App version 3.1.0 Build 49

Android 5 with no sim card.  Bought exclusively to use with the WIU.

Again....the LABOUR BIAS was working fine with my Legacy engines.

Any other thoughts on what I might try?

Thank You

I'm afraid I don't have much to offer here.  Clearly, the device and app have some issue with displaying the screen correctly.  If you uninstall and reinstall the app and have the same issue, then we have to start looking at the device and the OS on that device.  If your device is exclusive for running the trains I wonder if you could reset it.  I'll discuss this further with our app developers but, at the same time, you can see how this is isolated to your device.  We've never heard of anything like this before.  Try deleting the app, resetting the device, and then reinstalling the app.  Sorry, I don't have much more to offer on this.

Once  again ....Thank You for your reply.

I have since reset my new phone .....uninstalled and reinstalled the App ....again.

I have done all I can and have followed all instructions.

All my MTH equipment if fully updated.

It must be in the WIU.

Will MTH exchange my WIU for another?  Mine is barely 6 months old with very little home use.

Thank You

It's highly unlikely the WIU could somehow distort a specific graphic in the app display.  It literally has no way to do that.  So, before you take that path, load the app on another device, a friend or family member's phone, whatever, and I'm pretty sure you will see the issue resolved.  You can log into your Google account on another device and then you won't need to purchase another copy of the app.  

What is the specific device having this issue?  What brand, model, etc?  

Thank You for your reply.

Followed your instructions and used my ASUS tablet.  Android.  Reinstalled the APP.

Same thing.....but this time you can see how the digit changed to number 8 from 7.

My dedicated phone is RCA Android 5.  All equipment is up to date.

As mentioned earlier in these posts......the LABOUR BIAS worked without issue on both devices and I have not changed anything with respect to my system or the layout.

I have to think WIU or APP.....

Thank You

MTH RD posted:

Soo Line posted:

MTH RD posted:

Soo Line posted:

MTH RD posted:

Soo Line posted:

Thank You MTH for your responses.

I would like to add the following WIU issue:

I have lost LABOUR BIAS on Legacy Engines.

It was present right from the beginning when I installed my WIU months ago.

WIU version is 1.1

DCS,  both TIU and Remote are 6.10  -  Rev L  -  new system prior to WIU.

Everything is hooked up properly and as mentioned was working perfectly.

Here is a pic of my screen in Legacy.......that is all I now get.  The digit will sometimes change to 8.  The "graph" or slide button used to increase or decrease BIAS is gone.

I've done nothing to alter or made any changes to my system or layout.

I have refreshed and "Uninstalled" and "Reinstalled" the app.....no change.

Thanks for considering this matter.

 

First, sorry about this.  It appears you have found some ugly bug.  Have you tried resetting the app?  If you have engines, etc., that you don't want to lose, export them and then import after the reset.  But, first, before the import, see if the labor bias feature is corrected.  This is some kind of odd glitch in the app or your device.  Try power cycling the device also.  The fact the app is displaying incorrectly is very odd.  

Is this iOS or Android?  What version of the app?  

Thanks for your reply.

I have reset the App....no change.

App version 3.1.0 Build 49

Android 5 with no sim card.  Bought exclusively to use with the WIU.

Again....the LABOUR BIAS was working fine with my Legacy engines.

Any other thoughts on what I might try?

Thank You

I'm afraid I don't have much to offer here.  Clearly, the device and app have some issue with displaying the screen correctly.  If you uninstall and reinstall the app and have the same issue, then we have to start looking at the device and the OS on that device.  If your device is exclusive for running the trains I wonder if you could reset it.  I'll discuss this further with our app developers but, at the same time, you can see how this is isolated to your device.  We've never heard of anything like this before.  Try deleting the app, resetting the device, and then reinstalling the app.  Sorry, I don't have much more to offer on this.

Once  again ....Thank You for your reply.

I have since reset my new phone .....uninstalled and reinstalled the App ....again.

I have done all I can and have followed all instructions.

All my MTH equipment if fully updated.

It must be in the WIU.

Will MTH exchange my WIU for another?  Mine is barely 6 months old with very little home use.

Thank You

It's highly unlikely the WIU could somehow distort a specific graphic in the app display.  It literally has no way to do that.  So, before you take that path, load the app on another device, a friend or family member's phone, whatever, and I'm pretty sure you will see the issue resolved.  You can log into your Google account on another device and then you won't need to purchase another copy of the app.  

What is the specific device having this issue?  What brand, model, etc?  

One more thing.  You would have needed to execute the steps in this order.

1. Unistall app

2. Reset device

3. Reinstall app

MTH RD posted:

MTH RD posted:

Soo Line posted:

MTH RD posted:

Soo Line posted:

MTH RD posted:

Soo Line posted:

Thank You MTH for your responses.

I would like to add the following WIU issue:

I have lost LABOUR BIAS on Legacy Engines.

It was present right from the beginning when I installed my WIU months ago.

WIU version is 1.1

DCS,  both TIU and Remote are 6.10  -  Rev L  -  new system prior to WIU.

Everything is hooked up properly and as mentioned was working perfectly.

Here is a pic of my screen in Legacy.......that is all I now get.  The digit will sometimes change to 8.  The "graph" or slide button used to increase or decrease BIAS is gone.

I've done nothing to alter or made any changes to my system or layout.

I have refreshed and "Uninstalled" and "Reinstalled" the app.....no change.

Thanks for considering this matter.

 

First, sorry about this.  It appears you have found some ugly bug.  Have you tried resetting the app?  If you have engines, etc., that you don't want to lose, export them and then import after the reset.  But, first, before the import, see if the labor bias feature is corrected.  This is some kind of odd glitch in the app or your device.  Try power cycling the device also.  The fact the app is displaying incorrectly is very odd.  

Is this iOS or Android?  What version of the app?  

Thanks for your reply.

I have reset the App....no change.

App version 3.1.0 Build 49

Android 5 with no sim card.  Bought exclusively to use with the WIU.

Again....the LABOUR BIAS was working fine with my Legacy engines.

Any other thoughts on what I might try?

Thank You

I'm afraid I don't have much to offer here.  Clearly, the device and app have some issue with displaying the screen correctly.  If you uninstall and reinstall the app and have the same issue, then we have to start looking at the device and the OS on that device.  If your device is exclusive for running the trains I wonder if you could reset it.  I'll discuss this further with our app developers but, at the same time, you can see how this is isolated to your device.  We've never heard of anything like this before.  Try deleting the app, resetting the device, and then reinstalling the app.  Sorry, I don't have much more to offer on this.

Once  again ....Thank You for your reply.

I have since reset my new phone .....uninstalled and reinstalled the App ....again.

I have done all I can and have followed all instructions.

All my MTH equipment if fully updated.

It must be in the WIU.

Will MTH exchange my WIU for another?  Mine is barely 6 months old with very little home use.

Thank You

It's highly unlikely the WIU could somehow distort a specific graphic in the app display.  It literally has no way to do that.  So, before you take that path, load the app on another device, a friend or family member's phone, whatever, and I'm pretty sure you will see the issue resolved.  You can log into your Google account on another device and then you won't need to purchase another copy of the app.  

What is the specific device having this issue?  What brand, model, etc?  

One more thing.  You would have needed to execute the steps in this order.

1. Unistall app

2. Reset device

3. Reinstall app

Okay......Thank You

1)  Used ASUS tablet, Android.......uninstalled and reinstalled APP.....NO change.  You will see in the attached pick.....only the number changed from 7 to 8.

2)  Followed your instructions on sequence noted above with RCA Android 5 phone and again....NO change.

The Labour Bias worked on both devices without issue.....then one day it did not.

No changes were made to my system. 

Pleased to continue with any other suggestions.

Thanks        ASUS tablet pics here.

OK, so the issue applies both devices you've been using.  Did you, at any point, export/import to share the files between the devices?

What I am suggesting is to get a virgin device that has never had the app installed and sign in with your Google credentials.  Download and install the app on this new device and it would be really hard to imagine how the problem could remain.  

There is a conflict between the devices and the DCS app that's causing an inappropriate screen display.  The conflict could be caused by some other app or setting.  I can't possibly guess at what this might be but, obviously it's difficult to troubleshoot remotely.  

You're running a version of Android released nearly 4 years ago.  I would certainly try updating your O/S to something more recent.  I think there are 4 updates available.  It could be some artifact of the old O/S combined with an app or setting, etc.

Outside of these thoughts and suggestions, I'm not sure how we can help.

MTH RD posted:

OK, so the issue applies both devices you've been using.  Did you, at any point, export/import to share the files between the devices?

What I am suggesting is to get a virgin device that has never had the app installed and sign in with your Google credentials.  Download and install the app on this new device and it would be really hard to imagine how the problem could remain.  

I think this is the most likely scenario. When I first started with Premium app I had a problem with accessories that would not activate when I'd create a scene. I troubleshooted the problem quite a bit and after I realized the problem cloned to my other devices I knew the issue was with the data in the app.

I reset the app, plugged all of my switches, accessories, routes and scenes back into the app and BOOM, problem solved.

I now keep a "Known Good" backup copy of my app data so that I can easily restore my app back to a working state if this were to ever happen again vs. re-entering my layout & engine data.

Good luck, I hope you get this figured out.

So in regards to MTH RD's comment: "I can tell you the DCS app will never attempt to adjust track voltage below 5VAC from a TIU", I guess people like me who run PS1 and other conventional engines can not use the DCS app to run their trains properly. That's a shame because I really like the app and I was hoping to use the app exclusively without the need for my Cab1, Command Base, and TCP400

I guess I'm going to hook up my TIU in passive mode and use my TPC400 to control variable track power. I'm still not 100% clear on how to do that. I have Barry's book and I understand it, but it makes no mention of how to power the TIU. Is it powered by connecting the output of the TCP400 (which I am using) to the TIU fixed output 1 or does it have to be powered my an aux power supply like my Z750? Or maybe there is a preferred mode in which case please someone tell me which is better?

And once all is hooked up, can I address the TCP400 using the DCS app to control track power? And I guess I won't be able to control my TMCC engines with the app because the command base will be connected to the TPC400 not the TIU, right?

Any help would be appreciated. Thanks

And can I address the TPC400 as Track 1 in the DCS app?

Rickw2 posted:

So in regards to MTH RD's comment: "I can tell you the DCS app will never attempt to adjust track voltage below 5VAC from a TIU", I guess people like me who run PS1 and other conventional engines can not use the DCS app to run their trains properly. That's a shame because I really like the app and I was hoping to use the app exclusively without the need for my Cab1, Command Base, and TCP400

I guess I'm going to hook up my TIU in passive mode and use my TPC400 to control variable track power. I'm still not 100% clear on how to do that. I have Barry's book and I understand it, but it makes no mention of how to power the TIU. Is it powered by connecting the output of the TCP400 (which I am using) to the TIU fixed output 1 or does it have to be powered my an aux power supply like my Z750? Or maybe there is a preferred mode in which case please someone tell me which is better?

And once all is hooked up, can I address the TCP400 using the DCS app to control track power? And I guess I won't be able to control my TMCC engines with the app because the command base will be connected to the TPC400 not the TIU, right?

Any help would be appreciated. Thanks

The reason I said the app will never attempt to adjust AC track voltage below 5VAC is because the app can only control voltage coming from the TIU and the minimum voltage output from the TIU is 5VAC.  We're not going to display something less than 5VAC when that's the minimum available in the hardware.

Because the DCS remote mistakenly allows a min track voltage of 1VAC to be set user's apparently think there is actually 1VAC on the track.  If you connect a meter and set the remote to 1 VAC min track voltage, as soon as you roll the thumbwheel to 1VAC there will be 5VAC on the track.

The Z4K puts out a minimum of 5VAC on the track.  The old original Lionel ZW puts out a minimum of 5VAC on the track.

People have been running PS1 and older Lionel trains with the Z4K, ZW, and TIU for over 15 years (longer for the ZW of course) without issue.  I'm not sure what your concern is.  I don't think a PS1 engine will even turn on with less that 5VAC on the track.  To be honest, I haven't run one in years so, maybe some do.  

Try running your PS1 engines using the TIU and remote (or app) and I would be surprised if you have a minimum voltage problem.

Rick,

Is it powered by connecting the output of the TCP400 (which I am using) to the TIU fixed output 1 or does it have to be powered my an aux power supply like my Z750?

The TIU will be powered either by connecting a power supply to the TIU's Aux Power port or by connecting track power to the output of Fixed Channel #1, in Passive TIU Mode.

MTH RD posted:

OK, so the issue applies both devices you've been using.  Did you, at any point, export/import to share the files between the devices?

What I am suggesting is to get a virgin device that has never had the app installed and sign in with your Google credentials.  Download and install the app on this new device and it would be really hard to imagine how the problem could remain.  

There is a conflict between the devices and the DCS app that's causing an inappropriate screen display.  The conflict could be caused by some other app or setting.  I can't possibly guess at what this might be but, obviously it's difficult to troubleshoot remotely.  

You're running a version of Android released nearly 4 years ago.  I would certainly try updating your O/S to something more recent.  I think there are 4 updates available.  It could be some artifact of the old O/S combined with an app or setting, etc.

Outside of these thoughts and suggestions, I'm not sure how we can help.

No I have never shared files between devices.

My mistake ....my phone purchased solely for WIU use is indeed an Android 6 ....not 5 as I previously indicated.

So, you feel reasonably sure it is not the WIU.  With both my devices acting exactly the same way.....having reset and reinstalled several times.  On the tablet I took it back to factory settings and began from new.......NO change with all these efforts.

Are you sure it isn't the APP?  Have you had any other reports of this nature?

Appreciate all the help......not sure where to turn now.

Running out of devices unless I borrow the neighbour's ! 

MTH RD posted:

Rickw2 posted:

So in regards to MTH RD's comment: "I can tell you the DCS app will never attempt to adjust track voltage below 5VAC from a TIU", I guess people like me who run PS1 and other conventional engines can not use the DCS app to run their trains properly. That's a shame because I really like the app and I was hoping to use the app exclusively without the need for my Cab1, Command Base, and TCP400

I guess I'm going to hook up my TIU in passive mode and use my TPC400 to control variable track power. I'm still not 100% clear on how to do that. I have Barry's book and I understand it, but it makes no mention of how to power the TIU. Is it powered by connecting the output of the TCP400 (which I am using) to the TIU fixed output 1 or does it have to be powered my an aux power supply like my Z750? Or maybe there is a preferred mode in which case please someone tell me which is better?

And once all is hooked up, can I address the TCP400 using the DCS app to control track power? And I guess I won't be able to control my TMCC engines with the app because the command base will be connected to the TPC400 not the TIU, right?

Any help would be appreciated. Thanks

The reason I said the app will never attempt to adjust AC track voltage below 5VAC is because the app can only control voltage coming from the TIU and the minimum voltage output from the TIU is 5VAC.  We're not going to display something less than 5VAC when that's the minimum available in the hardware.

Because the DCS remote mistakenly allows a min track voltage of 1VAC to be set user's apparently think there is actually 1VAC on the track.  If you connect a meter and set the remote to 1 VAC min track voltage, as soon as you roll the thumbwheel to 1VAC there will be 5VAC on the track.

The Z4K puts out a minimum of 5VAC on the track.  The old original Lionel ZW puts out a minimum of 5VAC on the track.

People have been running PS1 and older Lionel trains with the Z4K, ZW, and TIU for over 15 years (longer for the ZW of course) without issue.  I'm not sure what your concern is.  I don't think a PS1 engine will even turn on with less that 5VAC on the track.  To be honest, I haven't run one in years so, maybe some do.  

Try running your PS1 engines using the TIU and remote (or app) and I would be surprised if you have a minimum voltage problem.

Thank you for your reply MTH RD.

Yes I have run my PS1 engines (mostly trolley, subway, and a Genesis) using the app. I can't get them going smoothly from a full stop. They take the 5v before they do anything and then start moving quickly with some buzzing from their sound system. And forget my Williams FA2, it takes off once it starts moving. The same thing goes for all my older Lionel conventional engines, they don't start moving smoothly from a stop.

OTOH, when using Cab1/TCP400 or a CW-80 they all start smoothly from a stop as they always have. There must be something in the app or WIU that's causing the jerky start and buzzing because it just does not happen without the TIU/WIU/App controlling track voltage.

Barry Broskowitz posted:

Rick,

Is it powered by connecting the output of the TCP400 (which I am using) to the TIU fixed output 1 or does it have to be powered my an aux power supply like my Z750?

The TIU will be powered either by connecting a power supply to the TIU's Aux Power port or by connecting track power to the output of Fixed Channel #1, in Passive TIU Mode.

Thank you for your reply Barry.

My question is which is better? Connecting the Z750 to the aux power port in addition to connecting the power output of my TPC400 to the fixed output 1 of the TIU knowing the output of the TCP400 will be variable, or just connecting the output of the TCP400 to the fixed 1 out of TIU.

One online train blog suggests it's not a good idea to connect any power to the aux in port.

Rick,

My question is which is better? Connecting the Z750 to the aux power port in addition to connecting the power output of my TPC400 to the fixed output 1 of the TIU knowing the output of the TCP400 will be variable, or just connecting the output of the TCP400 to the fixed 1 out of TIU.

I'd connect to the Aux Power port. That way, if the TPC shuts off power to Fixed #1 for any reason, the TIU remains powered up.

One online train blog suggests it's not a good idea to connect any power to the aux in port.

That would be a bad suggestion to follow. There's absolutely no reason to not use the Aux power port, as well was some good reasons to use it.

Rickw2 posted:

And can I address the TPC400 as Track 1 in the DCS app? Tweak the app to allow users to assign a TPC or Powermaster’s TMCC ID to a “Track”.  Sorry, but the TIU’s variable voltage control and power quality is just plain bad. The best workaround is to assign a Lionel Powermaster as a TMCC engine and use the TIU in passive mode. 

@MTH RD 

Now that is a golden idea!!! Tweak the app to allow users to assign a TPC or Powermaster’s TMCC ID to a “Track”.  Sorry, no offense, but the TIU’s variable voltage control and power quality is just plain bad. I’ve given all my reasons in previous posts, so I won’t beat a dead dog. It’s dead and won’t get any better.  The best workaround is to assign a Lionel Powermaster as a TMCC engine and use the TIU in passive mode. Wouldn’t it be nice if we could control a Powermaster as a track instead of assigning it as an engine??? 

Then we could use that nice linear slider. Yes, the one where your thumb can slide up and down without having to look down. Oh how I hate that circular dial...running trains with that thing is like trying to draw a circle drunk and blindfolded. 

Which brings me to another great idea: let us have the option between a slider and dial for the app as a global setting.  Oh how I’d love that!

Thanks MTHRD!

Barry Broskowitz posted:

Rick,

My question is which is better? Connecting the Z750 to the aux power port in addition to connecting the power output of my TPC400 to the fixed output 1 of the TIU knowing the output of the TCP400 will be variable, or just connecting the output of the TCP400 to the fixed 1 out of TIU.

I'd connect to the Aux Power port. That way, if the TPC shuts off power to Fixed #1 for any reason, the TIU remains powered up.

One online train blog suggests it's not a good idea to connect any power to the aux in port.

That would be a bad suggestion to follow. There's absolutely no reason to not use the Aux power port, as well was some good reasons to use it.

Thank you Barry, I will follow your suggestion.

But in passive mode, will I be able to control my TMCC engines with the app? The Command Base will be connected to the TPC400 not the TIU.

Rick,

But in passive mode, will I be able to control my TMCC engines with the app? The Command Base will be connected to the TPC400 not the TIU.

You'll have to connect the command base to both the TPC and the TIU. Use a serial splitter cable.

Barry Broskowitz posted:

Rick,

But in passive mode, will I be able to control my TMCC engines with the app? The Command Base will be connected to the TPC400 not the TIU.

You'll have to connect the command base to both the TPC and the TIU. Use a serial splitter cable.

OK thanks, good to know. I didn't know I could do that. Will do.

Edit: Ordered serial splitter cable

I had a legacy lashup with two legacy engines set up on the app and my legacy cab2 remote. They were set up and both devices. I use the cab2 to do the fuel refill sequence when the crewtalk diolag states fuel is low. I have to do this on the cab2 because it seems it cant be done on the wifi app as of right now. Also it seems you can not activate the legacy engines sequence control feature with the dcs wifi app either. These two features would be nice to access via the dcs app in the aux screen. 

Now that said it seems when I set up the legacy lashup in the dcs app and control the lashup with the dcs app and then go back to the cab 2 to control the lashup. The lashup does not respond when trying to control it with the cab 2. To get the legacy lashup to function again on the cab 2 I have to reset up the lashup on the cab 2 remote. This is a little anoying to say the least. Have any legacy users exsperiance this?

Also the max speed contol setting in the control screen for each engine is wonderfull.  This is very usefull especially if you accidentally touch the mph dial and the engine runs off at 100 mph because you accidentally touch the dial while blowing the whistle or trying to scroll to the bottom function such as the coupler buttons. Could this also be added to dcs and legacy lashups and legacy engines in general? Also just a thought could the max speed arrow that appears on the dcs mph speed dial in the wifi app when max speed is set. Could this be configured in the software to just place your finger on the arrow and then dragged to the desired max speed limit for all engines in the main control screen. This would be very usefull for a quick setting of the max speed limit of all engines and lashups when running trains with the dcs app. Just my two cents.

Lionelzwl2012 posted:

 

Now that said it seems when I set up the legacy lashup in the dcs app and control the lashup with the dcs app and then go back to the cab 2 to control the lashup. The lashup does not respond when trying to control it with the cab 2. To get the legacy lashup to function again on the cab 2 I have to reset up the lashup on the cab 2 remote. This is a little anoying to say the least. Have any legacy users exsperiance this?

 

as I run a lot of legacy lash-ups I had this happen and just stopped using the app for legacy lash-ups.

I was able to buy and install premium app on my ipad, and grandson's ipod. However, cannot access premium app for android device to purchase it.

Is there a premium app for android,

You should be able to do a search for MTH in the google play store. That will locate the Wi-Fi DCS app. Once you install the free app go to "More" and select upgrade to pay for and install the premium upgrade.

I'm missing something somewhere.

when I set up app, I select WIU. Then when I go to more, upgrade, before I can purchase Premium, a page pops up saying "you must replace the DCS explorer hardware with a DCS WIU and TIU.

I've deleted the app, restarted the phone, reloaded the app, and same thing happens.

I've successfully upgraded to premium on two different Apple units, but this android has me stumped.

Jim,

Then when I go to more, upgrade, before I can purchase Premium, a page pops up saying "you must replace the DCS explorer hardware with a DCS WIU and TIU.

That sounds like a new "feature" in the 3.1.0 version of the app. I get the same thing and also on my iPad mini 4.

Just tap "Continue" and then proceed with the upgrade.

Jim M Sr posted:

I'm missing something somewhere.

when I set up app, I select WIU. Then when I go to more, upgrade, before I can purchase Premium, a page pops up saying "you must replace the DCS explorer hardware with a DCS WIU and TIU.

I've deleted the app, restarted the phone, reloaded the app, and same thing happens.

I've successfully upgraded to premium on two different Apple units, but this android has me stumped.

Jim, the warning screen is there so Explorer user's don't accidentally set their app to the WIU version and then spend $25 upgrading only to find out the Explorer doesn't support the additional features they just paid for.  

Apparently, some people upgrade so often (I don't know why.  Once you upgrade, no need to ever do it again) the act of tapping continue to ignore this screen is overly burdensome.  

I consider these little things first world problems.  As the manufacturer, it is very difficult to help a customer "un-purchase" an app upgrade so, we error on the cautious side.

Sorry for your troubles.

bigdodgetrain posted:

Lionelzwl2012 posted:

 

Now that said it seems when I set up the legacy lashup in the dcs app and control the lashup with the dcs app and then go back to the cab 2 to control the lashup. The lashup does not respond when trying to control it with the cab 2. To get the legacy lashup to function again on the cab 2 I have to reset up the lashup on the cab 2 remote. This is a little anoying to say the least. Have any legacy users exsperiance this?

 

as I run a lot of legacy lash-ups I had this happen and just stopped using the app for legacy lash-ups.

Thanks for the feedback guys.  We were unaware of this.  I'll try it here and, I'm sure, will see the same thing.  Off hand, I can't see why this would be the case but clearly, something odd is happening.  I'll get this on a short list of fixes as we are moving to enhance the Lionel Legacy experience with the app.  

Lionelzwl2012 posted:

I had a legacy lashup with two legacy engines set up on the app and my legacy cab2 remote. They were set up and both devices. I use the cab2 to do the fuel refill sequence when the crewtalk diolag states fuel is low. I have to do this on the cab2 because it seems it cant be done on the wifi app as of right now. Also it seems you can not activate the legacy engines sequence control feature with the dcs wifi app either. These two features would be nice to access via the dcs app in the aux screen. 

Now that said it seems when I set up the legacy lashup in the dcs app and control the lashup with the dcs app and then go back to the cab 2 to control the lashup. The lashup does not respond when trying to control it with the cab 2. To get the legacy lashup to function again on the cab 2 I have to reset up the lashup on the cab 2 remote. This is a little anoying to say the least. Have any legacy users exsperiance this?

Also the max speed contol setting in the control screen for each engine is wonderfull.  This is very usefull especially if you accidentally touch the mph dial and the engine runs off at 100 mph because you accidentally touch the dial while blowing the whistle or trying to scroll to the bottom function such as the coupler buttons. Could this also be added to dcs and legacy lashups and legacy engines in general? Also just a thought could the max speed arrow that appears on the dcs mph speed dial in the wifi app when max speed is set. Could this be configured in the software to just place your finger on the arrow and then dragged to the desired max speed limit for all engines in the main control screen. This would be very usefull for a quick setting of the max speed limit of all engines and lashups when running trains with the dcs app. Just my two cents.

As I mentioned in a previous post, we'll look into the loss of lash up control with the Cab2 after using the app.  We should be able to resolve this once we understand what is going on.

As for the expanded Legacy features you're interested in, please keep the feedback coming.  It is our intention to add any commonly used Legacy features to the app if cost feasible.  We think everyone, you, us, and Lionel, all benefit from the app supporting Legacy/TMCC operation.

The max speed setting on the speedo bezel was actually implemented originally.  Then, the little guys at train shows would just set it to 120 smph and crash our trains on display!  In thinking about it, we might be able to use the lock/unlock setting to also lock and unlock the max speed pointer.  Again, this is good feedback and I'll look at it. 

Thanks.

Soo Line posted:

MTH RD posted:

OK, so the issue applies both devices you've been using.  Did you, at any point, export/import to share the files between the devices?

What I am suggesting is to get a virgin device that has never had the app installed and sign in with your Google credentials.  Download and install the app on this new device and it would be really hard to imagine how the problem could remain.  

There is a conflict between the devices and the DCS app that's causing an inappropriate screen display.  The conflict could be caused by some other app or setting.  I can't possibly guess at what this might be but, obviously it's difficult to troubleshoot remotely.  

You're running a version of Android released nearly 4 years ago.  I would certainly try updating your O/S to something more recent.  I think there are 4 updates available.  It could be some artifact of the old O/S combined with an app or setting, etc.

Outside of these thoughts and suggestions, I'm not sure how we can help.

No I have never shared files between devices.

My mistake ....my phone purchased solely for WIU use is indeed an Android 6 ....not 5 as I previously indicated.

So, you feel reasonably sure it is not the WIU.  With both my devices acting exactly the same way.....having reset and reinstalled several times.  On the tablet I took it back to factory settings and began from new.......NO change with all these efforts.

Are you sure it isn't the APP?  Have you had any other reports of this nature?

Appreciate all the help......not sure where to turn now.

Running out of devices unless I borrow the neighbour's ! 

Exchanged my phone for a new phone and I have the exact same issue.

LABOUR BIAS does not work with my Legacy engines.

I have followed all your instructions..................so you're sure it could not be the WIU?

Have you had others with this issue?

Thank You