Skip to main content

I been running my dcs engines quite a lot latley since using the new dcs wifi app. I got a samsung 7 inch tablet dedicated for the train room. This weekeng I have been playing with the more advanced features of dcs. The new wifi app makes this a lot easyer. I ran across some quirks today though and would like to share them for disscussion and also for your feedback. If you have any quirks running your mth engines with the dcs wifi feel free to post hear also. Mabe we can solve or point out dcs wifi issues together.

So to start this off. Today while running trains I was running a lash up of two ps2 3 volt ac600 bnsf engines and when I started up the lash up only one smoke unit came on. Had to turn on and off the smoke feature to get both smoke units going. Then I noticed that the sound of one engine was louder than the other. Seems when I use the volume bar to turn down the overall volume of the engine consist the rear engines volume does not respond to the setting only the front engine in the consist. Its volume goes up and down the rear engine stays full volume regardless of any of my changes. I have to go into the engine list and pick the rear engine and lower the volume for it that way. Then go back to the consist and adjust the volume for the consist to my liking.

Next I took a ps3 es44 UP  and made a local frieght. Then I used the record feature and made a recording. Just a few small laps around my inner loop with some dialogue and some horn blows. Then I saved it and named it. I then played it back in loop mode while I started up and ran the bnsf consist on the outer loop. The es44 local frieght made the first recorded loop as recorded by me. Then during the second playback in loop mode I noticed the engine was moving rather slowly and it had no sound. The bnsf consist I was controlling was working as it should. So I stoped it and focused on the es44 engine. I restarted the loco and it ran just fine. I did not try the recorded session again though. I decided to shut down everything and quit running trains for the day. Not sure what happened in either of these two incidences,but they happened. Any suggestions as to why and what issues have you guys had while using the wifi app. 

Also one question with the advanced recording feature. why cant you playback two recorded sessions at the same time? Is this a dcs memory issue. I could have run both of these engines in one recording session and played it back,but I made a recording session for each train. One for the es44 and one for the bnsf ac600 consist. Then tryed to play them both back at the same time. I found out that dcs only lets you playback on recorded session at a time it seems. Is this correct or am I missing something.

All advice is welcome here and if you guys have any operating dcs wifi problems lets discuss them her and talk about them. I for one love this app and want to get the most out of it. My goal is to someday have operating sessions on my layout like the h.o. guys do. I also have the legacy and serial 2 hooked up to my tiu. I have only tryed to run my legacy engines a couple of times. They seemed to run fine. All in all I cant wait to get more time in the trainroom to test out the dcs wifi fully with all my engines and uncover any abnormalities so if there are any that crop up maybe the mth rnd guys can look into them. 

Last edited by Lionelzwl2012
Original Post

Replies sorted oldest to newest

Roger,

why cant you playback two recorded sessions at the same time?

Because the TIU is playing it back, not the remote, and the TIU can't be in two places at once.

I haven't tried this myself, however, try this. Play back a session from one TIU with one remote and a second session in a different TIU with a different remote. You'll have to be sure that both TIUs were not in Super TIU mode when the sessions were recorded and also when they're played back.

Last edited by Barry Broskowitz

Wifi loses the remote signal to the TIU when using the variable track power option resulting in conventional trains sometimes running away at a high voltage. The wifi seems to lose the communication to the variable track power and then it takes several refreshes before the TIU variable power is seen again. I use both Apple IPhone and IPad or my Android device. All have the proper updates to the premium apps.

 The thing about the sound volume maybe even greater using AC6000s. There was a release of the AC6000 that had one of the loudest sound sets I have seen. There were other engines that had very soft sound sets. If I put the narrow nose -8 sound set up front with an AC6000 PS2 trailing, it's hard to hear the horn on the lead unit.

 So I could not blame that on the WIFI alone. Unless you don't have this issue with the remote?

Engineer joe, thats good to know. Will try the consist with my dcs remote and report back. The dcs wifi using android only seems to lower the lead engines volume. The tail engines volume seems to not recive the volume command. Also muting the consists engine volume only mute the lead engines volume. The tail engines,engine volume is still heard. I will also try another engine lash up and see if it acts the same.

Captin coog, I have exsperianced also with my tablet sometimes it reads the track and when finished all my engines remain in the inactive list. It takes several readings to get the engines currently on my layout to show in the active list. Sometimes my screen says cant find tiu,but it shows connected when I go to my wifi settings on my tablet. Kinda strange.

Last edited by Lionelzwl2012

Tryed the bnsf consist with the dcs handheld remote. Still the same outcome on the volume control and engine mute feature.

Tryed lowering the overall engine volume on both engines with the manual volume pots on each engine. They do not even seem to work in dcs mode. I tryed addressing each engine individually and shuting each one down and then turning the manual volume pot all they way off. Then starting the engines back up. Each still had sound. The volume pots seem to do nothing. What here am I doing wrong? Tryed two other engines off the shelf and they behaved the exact same way. Also my es44 volume seems to be different from my other engines. When using the wifi app to control the sound volume with the slider bar. The engines sound volume is almost off to bearly hearable when about 1/3 the way up (going left to right) and about halfway it is at low volume. This seems to be an engine problem though. All other functions work ok. It just seems the installed sound set is much lower than some off my other engines. Would installing a different es44 sound set into this engine change the volume? What I mean is do different sound sets have different volume levels? 

 

 

Last edited by Lionelzwl2012

Also muting the consists engine volume only mute the lead engines volume.

Known bug.

Tryed lowering the overall engine volume on both engines with the manual volume pots on each engine. They do not even seem to work in dcs mode.

That's because they're not supposed to work under DCS. They're for conventional control only.

What I mean is do different sound sets have different volume levels? 

Again, that's normal. Different engines with different sound files and different sized speakers/baffles may have somewhat different sound volumes.

Lionelzwl2012 posted:

 What I mean is do different sound sets have different volume levels? 

 

 

Yes, that's exactly what I was trying to tell you!

There were complaints of certain sound sets being too low. I think some adjustments by MTH went too far. I forget the exact history but the AC6000 had one release that was around twice as loud! I have that set loaded in my BNSF AC6000 upgrade that I did.

 So, when I put that engine into a consist, I have to go into the remote's menu, and lower the sound volume of that engine. The frustrating thing is it seems that I have to do that every single time I run it. So again complaints were posted and for various reasons MTH came up with the FSV softkey to store consist's settings. Yet it still didn't work on this engine and I am always changing it's volume level. Urrrgggg!

 I tried to change the soundset to the favored narrow nose sound file a few years back. The board in this exact engine is the one with the smaller 1 meg memory and won't let you install the larger 2 meg file. You can't put every file available into every engine.

Last edited by Engineer-Joe

Thanks guys for all the great info. I am late to the dcs wifi party I know. Been running my legacy a lot lately. Got the bnsf bug and got some nice new modern engines from mth so have been playing with my dcs wifi a lot more lately. 

Barry is there a post where all the known dcs bugs currently being debugged are listed so I can get up to speed on the wifi app. I should follow the dcs forum more but with two jobs I dont have much time. Thanks again for all your input. 

 

Only been using the WIU for a couple of weeks. Just have the standard app version at the moment.

One thing I’ve noticed on the ALP-46 is that pantograph control does not work. Works fine on the DCS remote.

Is this a fault or do we need to upgrade the app to premium to control the pantographs?

Other than that, really impressed with the WIU and app.

Nick

Nick,

One thing I’ve noticed on the ALP-46 is that pantograph control does not work. Works fine on the DCS remote.

Does it fail to raise and lower when direction changes and it's in automatic mode, or does it fail to raise and lower manually in manual mode, or both?

I have this engine and haven't seen this issue, however, I may not have run it with he most current app.

BTW, ensure that you have DCS 6.1 in the TIU, 1.1  firmware in the WIU and app version 3.1.0.

Variable voltage control is erratic. The app randomly gets stuck and engines cruise off. Sometimes it shoots to 20v. It is a latency bug MTH has been aware of for almost a year without a fix.

Postwar and Modern Lionel engines blow horns continuously using MTH DCS app's variable voltage control. There is something ugly in the waveform wreaking havoc on relays and sound cards, especially at lower voltages. If you increase the voltage beyond about 15-16v, the horns and whistles stop. Drop the voltage below 15v, continuous horn again. The speed slider is no way to control horns and whistles.

At lower voltages, the MTH DCS app chops up the power so badly, it feels like 30 Hz AC - rattles E-units, runs AC motors rough. I can even make barrels charge up my postwar 362 barrel ramp without it's diode. So I know the power frequency is chopped down horribly to simulate a lower voltage.

There is a minimum starting variable voltage bug. It always starts at 5v, even when you set the minimum to be less.

All engines miss watchdog signals, unless TIU is in passive mode. Doesn't matter whether voltage is applied from variable or fixed channels. I have given up and now use a Lionel Powermaster to deliver power with a passive hookup to the TIU. 

DCS engine volume starts full blast, regardless of app setting. But as soon as you touch the volume button, it drops to the correct volume.

Legacy locomotive RPM ramping does not work.

Speed dial has a momentum bug which affects DCS, Legacy, TMCC operation. I call it the 59 mph dead zone. See attached video.

Attachments

Videos (1)
IMG_3778
Last edited by GregR
Barry Broskowitz posted:

Nick,

One thing I’ve noticed on the ALP-46 is that pantograph control does not work. Works fine on the DCS remote.

Does it fail to raise and lower when direction changes and it's in automatic mode, or does it fail to raise and lower manually in manual mode, or both?

I have this engine and haven't seen this issue, however, I may not have run it with he most current app.

BTW, ensure that you have DCS 6.1 in the TIU, 1.1  firmware in the WIU and app version 3.1.0.

Hi Barry, I have DCS 6.1, WIU 1.1 Acording to the LUCI and App Version 3.1.0.

Automatic mode works and the pantograph raises and lowers with direction changes. It’s manual mode which it fails to raise and lower.

Nick

Greg,

There is a minimum starting variable voltage bug. It always starts at 5v, even when you set the minimum to be less.

Known and reported.

Legacy locomotive RPM ramping does not work.

Known and reported.

All engines miss watchdog signals, unless TIU is in passive mode. Doesn't matter whether voltage is applied from variable or fixed channels. I have given up and now use a Lionel Powermaster to deliver power with a passive hookup to the TIU. 

I disagree.

Aside from an occasional miss with some PS3 engines due to their individual firmware, watchdog response at power-up typically is correct.

DCS engine volume starts full blast, regardless of app setting. But as soon as you touch the volume button, it drops to the correct volume.

I've never experienced anything like this, either with individual engines or 2 and 3 unit as lashups.

Variable voltage control is erratic. The app randomly gets stuck and engines cruise off. Sometimes it shoots to 20v. It is a latency bug MTH has been aware of for almost a year without a fix.

Being completely honest, this doesn't occur in normal operation, although it is possible to make the voltage surge if one intentionally abuses the speed slider.

 2 Momentum settings? One can we get accell and decell settings in a lashup please. All other engine setting are finnaly there in the settings menu. 

Second, lowered the accell rate to 1 and then taped 10mph on the screen. The engine still moved to fast to be realistic. Can this be changed or is this a overall dcs thing. Lionel legacy has better momentum control it seems. It takes real consists and engines pulling cars a while to get up to road speed. Even with accell at 1 it still seems to fast. For one you would think that you could set the accell rate to 1 then tap a desired mph then watch that engine or consist slowly go to that speed. I tryed this as stated and the engines seem to move way to fast for being prototipical at start up speeds. Am I doing it wrong or is what I am describing accurate here?

Nick,

Automatic mode works and the pantograph raises and lowers with direction changes. It’s manual mode which it fails to raise and lower.

I tested thePantograph Soft Key in both Auto and Manual mode on 4 Premier engines: ALP-36, Swiss crocodile, P5a, and PP5a Box Cab.

For all engines the DCS App's Pantographs Soft Key and its menu worked flawlessly, in exactly the same way as did the DCS Remote's MOP soft key and its menu.

The way the soft key works in the app is that when tapped, a Pantograph menu appears. When I tap Manual, the menu disappears. At this point, the engine is in manual pants mode and the pans do not move when direction is changed.

If I then tap the Pantograph Soft Key again followed by tapping an up or down button for a pantograph, the engine's pans respond appropriately.

To put the pans back in auto mode, I tap the Pantograph Soft Key followed by the Automatic button.

 As far as I can tell, there isn't any bug in the DCS App's pantograph operation.

Last edited by Barry Broskowitz

Any ideas as to why on a fairly regular basis the DCS app will find a locomotive no problem but the remote will not.  Other times it's the exact opposite.

The remote and the app communicate with the TIU in completely different ways. Regardless, your question is too broad to have other than a range of generic answers, i.e., "the usual culprits".

You need to be specific as regards each exact scenario and also whether this happens with the same engines or different engines, and all of the time or intermittently.

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.

Lash Up Smoke State: The state of the smoke setting should be stored and remain until changed.  In the event that a PS2 model has a weak battery, or whatever, the engines can get out of sync.  A simple tap of smoke on/off on the remote or app syncs things back up.  This works fine in in the app based on our testing here.

Lash Up Vol Control: The volume of all engines in a lash up are adjusted using the master volume control on the remote or in the app.  We experienced no issues here.  That said, and as someone commented, there are engines with very different overall volume levels.  This is due to physics mostly but, also, just normal variation from the sound engineers.  If you get two engines in a lash up with very different levels, the louder engine can drown out the quieter one.  And to confirm, the manual volume pot is completely ignored in command mode.  The pot only applies to conventional operation.

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.

Record/Playback:  Having an engine move slowly after playback may be due to some address conflict or, the engine simply didn't get the speed = zero command.  The fact that the sound is off is odd but, if a PS2 engine is shut down and then issued a speed command, it will move without starting up.  This is odd and I suspect some corner case.   Haven't heard this one before.

As I think Barry may have explained, the recordings take place in the TIU.  The TIU isn't smart enough to play back multiple recordings at the same time so, unfortunately, yes, a system limitation is one playback per TIU at a time.  You can get multiple playbacks if you use multiple TIUs to do so.

Variable Voltage: The variable voltage control in the app can get overwhelmed if a person slides the control too quickly.  It's actually not the app that has the issue.  It's all the communication back and forth across the WIU and TIU.  All the components cannot keep up and so, they get confused.  We are aware of this one and it's on an active list for a fix.  All we intend to do is allow the control to move as fast as the system can handle.  In the meantime, just use it like the handle of a Z4K and you'll be fine.

The variable control in the app has nothing to do with the waveform.  The variable output from the TIU is identical regardless if you are using the remote or the app.  The AC waveform from the TIU is phase control and so, varies relative to the voltage output.  Again, identical between the remote and app.

Minimum Start Voltage: OK, let's try to dispel this myth that somehow, the remote allows a min track voltage setting below 5VAC.  This is a fallacy.  The TIU will not output less than 5VAC from the variable channels.  The Z4K transformer will not put out less than 5VAC track voltage.  The venerable Lionel ZW transformer doesn't put out less than 5VAC.  Well, at least it isn't designed to do so.  The min of 5VAC track voltage is an 30+ year old quasi standard in O ga railroading.   Don't ask me why.  I just know our products honor it.  This myth about the DCS remote controlling voltage below 5VAC is just numbers on a screen.  Not voltage on a track.  We will not change the app to display false voltages.  The remote should not have been modified either.  We just won't spend time and money to correct it.

Engines Missing Watchdog:  Regardless of whether a TIU is connected passively or actively (normally) should make no difference with regard to engines receiving watchdogs.  Now, that said, in passive mode the TIU must be powered via aux or fixed one.  Once the TIU is powered, the watchdogs are sent out for some duration of time.  This issue could be the type of power signal applied or timing.  Also, you need to make sure you're running the latest version of DCS as we had an issue with watchdog timing that we corrected in the most recent update.

Volume Starts at 100%:  This is certainly not a common issue or we would have been inundated with complaints for the past 15 years.  The models retain their volume level settings regardless whether using the remote or the app.  If an engine isn't remembering the volume setting through power cycles the battery or caps are not holding up the voltage or, maybe some other issue.  There is no universal issue here.

Legacy Diesel RPM:  In Legacy mode, diesel RPMs do not vary much at all relative to speed.  We are aware of this and working on it.  That said, the test engines we have respond exactly the same way when run using the Cab2 or the DCS app.  In talking with our friends at Lionel, there is a relationship between momentum and diesel rev.  So, we tried it.  And, I can finally get some variation in our engines using the Cab2 set to medium or high momentum.  However, this is a really awkward way to run a model train layout of modest size so, not a great answer.  We're working on implementing an approach that will enhance how Legacy engines rev levels respond to speed changes.  Dare I say that Legacy operators may prefer what we do.  Stay tuned.

59 SMPH Dead Zone: Yep.  Legitimate bug.  We'll fix it on the next release.

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

Engines Not Found: Regardless of the  app or remote, having engines not found on the track is most likely a TIU and track signal issue.  While the communication path from the TIU to you, the user, is different between the remote and app, since both are telling you the engines aren't on the track, the  common denominator is the TIU and track signals.  Work on that and I'm guessing you'll see improvement in both your remote and app behavior.

 

Having said all of that, let me try to make a more general statement that I hope fosters some understanding and patience with our efforts.  While it may seem like MTH is larger than we are and has deep resources, this is simply not the case.  The entirety of what we do from a technology standpoint channels through a very small group of people.  We have many responsibilities that demand our time and attention that are frankly, much less interesting that things we would like to do.  A quick example.  We are just finalizing development of an tiny LED driver board for all the new products that have LEDs installed.  This board is a huge improvement over what we had and offers much greater flexibility, flashing features, etc., but, the same handful of staff are specifying behavior, designing hardware, writing firmware, having samples built up, testing, quoting for production, etc., etc.  This is just one example of many similar projects all running in parallel, all the time.  So, as much as we would like to focus all of our attention on DCS enhancements and new features, we simply cannot.  

Also, please understand that some of the requests made are singular preferences or, just make no sense.  So, while someone may be commenting that we aren't listening because we don't change something, I can tell you the DCS app will never attempt to adjust track voltage below 5VAC from a TIU.  Now, in DC, that will be different.  Another example is someone requesting a warning screen intended to prevent Explorer app users from upgrading be removed because it's annoying.  Well, it may be annoying to tap and clear this warning screen twice a year when an update is available but, imagine how annoying it is for a customer with the Explorer hardware to accidentally update their app for $25 only to find out they can't use any of the new features?  We, at MTH, have to consider all sides and weigh these factors against the impact relative to the time and resources we have.  We want to do everything we can for everyone.  But, unfortunately, that isn't at all practical from a business standpoint. 

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.

 

When you build a lash-up, the volume at start is very high, if not 100%. When you touch the volume down button, it seems to jump down a significant level.

I'm not sure if this is what is exactly being discussed. It happens every time I build one. It's not a big deal for me. I'm just trying to clarify what I see myself.

 I too look forward to seeing the accel/decel rates available to be set on consists.

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.

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.

IMG_0003

 

Attachments

Images (1)
  • IMG_0003

I'll weigh in on the watch dog issue.

My home layout is small, just a couple of loops so I run them both on the variable channels for a specific reason. I like to be able to shut one loop or the other off from within the app, I do however use command control 98% of the time.

So I configured the minimum starting voltage in the App & DCS remotes to 21.5 volts. Why not 22? Because when I start the VAR1 or VAR2 channels at 22 volts, the watch dog is missed 99% of the time on all engines (PS2 & PS3). This is a TIU issue as it doesn't matter if I use the remote or the app to apply the track power to have this happen.

This isn't a big deal as making the adjustment to full voltage is just one extra tap on the screen.

Last edited by H1000
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!

Mark Boyce posted:

RD, thank you!  That a lot of information!  I’m going to have to print it off (yes I’m old school). LOL

Joe, you are really busy providing a service to us all with your experience!  I don’t have the time to try things too much!

 Thank you kindly.

I have had some interesting comments against some posts of mine and a few attacks, but this is the opposite. I have run into troubles or issues and try to work thru them. I am not the best at it but I do have the time! I gladly offer any experiences I can lend, whether they actually apply or not some times.

 Again, I would like to thank MTH for their overall quality and value they put into their products. The occasional glitches can be frustrating.

Engineer-Joe posted:

When you build a lash-up, the volume at start is very high, if not 100%. When you touch the volume down button, it seems to jump down a significant level.

I'm not sure if this is what is exactly being discussed. It happens every time I build one. It's not a big deal for me. I'm just trying to clarify what I see myself.

 I too look forward to seeing the accel/decel rates available to be set on consists.

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.

The lash up volume behavior you are experiencing is normal.  Or, at least by design.  When you initialize a lash up, that is build it for the first time, we send a set of default values to have a known starting point.  The volume is cranked up to 100% which, can be annoying but, I just drag it back down to where I want it.  Thereafter, it should start up at the level previously set.

Large consists can get finicky.  If you have 4 or 5 engines lashed together then sometimes, timing gets a little difficult especially if one of the engines isn't a great signalling engine.  The TIU has to tell each engine in a lash up everything.  So, just a simple speed command is sent to all engines sequentially.  If one engine is not receiving signaling well (dirty pick-up roller, dirty track, weak ground, etc.) then the TIU has to try to tell that engine what to do a bunch of times.  This delay can cause quirky behavior.  It's a little bit nature of the beast.  We could probably do some things to overhaul the system but, it gets involved and isn't really backward compatible.  Wanna hear folks scream?  Tell them something isn't backward compatible.    

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.

IMG_0003

 

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?  

H1000 posted:

I'll weigh in on the watch dog issue.

My home layout is small, just a couple of loops so I run them both on the variable channels for a specific reason. I like to be able to shut one loop or the other off from within the app, I do however use command control 98% of the time.

So I configured the minimum starting voltage in the App & DCS remotes to 21.5 volts. Why not 22? Because when I start the VAR1 or VAR2 channels at 22 volts, the watch dog is missed 99% of the time on all engines (PS2 & PS3). This is a TIU issue as it doesn't matter if I use the remote or the app to apply the track power to have this happen.

This isn't a big deal as making the adjustment to full voltage is just one extra tap on the screen.

Interesting.  Clearly there is some relationship between full var voltage on and timing of the watchdog.  I'll confirm this issue here but, to be honest, if it's deep in the TIU code, we probably won't fix it.  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.

Add Reply

Post
The DCS Forum is sponsored by

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

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