Hancock52 posted:I'm not an expert on DCS and in particular on the WiFi app (which I do not use), but the "inactive" description and the fact that the engine appears to have started up in conventional when you first applied power is an issue I have had. Also various lighting features (like the beacon on my DDA40X) not operating sometimes. I wonder if it would be a good idea to try using the remote first without the WiFi?
It should not make any difference that you are using a small section of track as long as it is wired up to the TIU properly. I assume you went through the routine of adding the engine and the "READ TRACK" function - otherwise I don't know how it would be listed as inactive. Try READ TRACK again and see if it shows in the display.
I see that you do have (or had) firebox glow. I don't know whether there is any independent control of this through the softkeys. It's easy to accidentally turn things such as sound effects and lighting on and off by hitting the wrong button. Basically I had to check each softkey command for each of my DCS engines in order to be clear what I had turned on and off - it's far from an intuitive system - but a feature or factory reset is an alternative for checking the status of a feature. For that you will need to have the engine recognized as active by the DCS system.
Someone more expert may weigh in but the above is what I would try.
Thanks for the reply @Hancock52
I agree, it does seem to have started up in conventional mode. When i had it on my Holiday floor layout complete with the WiFi and TIU (thanks for correcting me on that acronym) set up it had never started the engine up automatically on powering up the TIU. I always had to press the Start Up soft key in the app.
I do not have the DCS remote. But from what I am reading here and there perhaps I should purchase one.
So from what I seeing the firebox glow only works when the engine is started in what is looking like a default to conventional mode. Keep in mind that my TIU/wifi app is set to Command mode. Not sure why the engine is being detected as conventional yesterday and this morning.
Further futzing with the engine I did the following.
- moved the tender and ending closer to the MTH clip-on that is powering the track. I have two 30 inch sections connected to equal 60inches total of track
- Powered up the Wifi
- Powered up the TIU after about 15-20 seconds of the WiFi
- now the engine did not automatically power up.
- opened the app after making sure I was on the DCS wifi stand alone network
- Hit "start up", hence the engine started up in idle mode... holiday lights, sound effects, cab light all start as expected.
- put cab forward and backward at a 1,2,3,-- 8 SMPH to see if firebox would glow.... nope it does not.
- Oddly one of the times in moving the engine it seemed it decided to automatically shutdown (fwiw track is on a carpet). (never happened before), keep in mind I had this engine and a long train of cars operating well over a month during the holidays on a large oval in my living room floor (hardwood).
- I thought, let me make sure the wireless tether is tight, when I applied pressure to the tether on the tender side (per MTH instructions she fired up.
- Ok, odd because the tether did not seem to be loose or even move upward or "click" into place.
- shut her down. scratching my head...
- Started it up once more.. moved her, no firebox glow... stopped.
- Now I got stupid here
Looking at the app, while engine was powered up but idle I changed the app from Command to Conventional .. bad idea because of course the track has full 18volts and the engine quickly accelerated forward and I'm sure I saw the firebox glowing but panicked to shut her down as it hit the track bumper. Glad to report I pulled the power and shut it down, no damage. ...
So at this point it seems clear that the Firebox Glow only works in Conventional mode for some reason.
I have also tried an "Engine Factory reset" and the "Engine Features reset" from the app, neither of which help the firebox glow.
