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

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.

Thanks barry will do.

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.

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? 

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.

I use the explorer for my small two train set up, and so far everything runs great!

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. 

Roger,

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.

No, there is not.

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.

Prairie Land Junction posted:

I use the explorer for my small two train set up, and so far everything runs great!

I should hope it does.

MTH RD has focused on explorer app development almost exclusively.

Maybe it's time for some housekeeping on the TIU/WIU side?

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

Nick,

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

When I have a chance, I'll check on that. I have several engines, including the ALP-36, with operating pans.

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?