Ron,
I guess I missed it somewhere, but you cannot input a Legacy/TMCC engine number higher than 90 into the DCS app.
That's because the DCS App, just like the DCS Remote, reserves DCS ID#'s 91-99 for TMCC or Legacy lashups. That corresponds to TMCC lashups of TR1 - TR9.
Barry Broskowitz posted:Ron,
I guess I missed it somewhere, but you cannot input a Legacy/TMCC engine number higher than 90 into the DCS app.
That's because the DCS App, just like the DCS Remote, reserves DCS ID#'s 91-99 for TMCC or Legacy lashups. That corresponds to TMCC lashups of TR1 - TR9.
Then why does the DCS app say you can use 1-99 in the Legacy/TMCC engine number change page? If it said 1-90 I would have been running engines days ago. That is what I'm mad about. Read my post.
Ron,
Then why does the DCS app say you can use 1-99 in the Legacy/TMCC engine number change page? If it said 1-90 I would have been running engines days ago.
Ask MTH.
That is what I'm mad about.
You're "mad" about a documentation error?Really?
Here is a picture of the MTH app's "Enter New Lionel Address" screen.
I never setup running TMCC engines using the handheld, so I was not familiar with the limitation Barry cited. This picture is the only instruction I was aware of until, out of frustration, I dug out the DCS manual and ran across the 1-90 limitation for the handheld.
And yes Barry I'm mad. Two frustrating days lost because MTH does not know how their own system works. And it would have been nice when I mentioned that I was using an ID of 92 in an earlier post that one of you experts would have caught that.
After reading the above posts, what is all common to us who are not getting the Legacy engines to run in the DCS app is that our Legacy/TMCC addresses are all above 90. I will give new addresses to these engines tonight at the club and see if the situation resolves itself. Will report back.
Jeff
CAPPilot posted:And it would have been nice when I mentioned that I was using an ID of 92 in an earlier post that one of you experts would have caught that.
Wow... sorry I missed that as well in your posts. Nothing like snarking at people, who are not paid to help you, when we miss something.
Here's a tip from my 21 years of running TMCC and 10 years with DCS: If you get a TMCC Loco (and now Legacy) that won't respond to the DCS remote or now the APP. Try changing the engine address/resetting back to "1". Then you'll know if it's a DCS issue or not.
Yes, whomever wrote the instruction text in the APP made a typo. (My thought: when they entered "99" they didn't think anything of it since Lionel can have 99 addresses). Heck, as I said above, a bunch of us missed it, even when you showed the screen shot.
Take a deep breath and relax. Despite your ranting, I'm sure we'll still be here to help as best we can.
sphillyj posted:After reading the above posts, what is all common to us who are not getting the Legacy engines to run in the DCS app is that our Legacy/TMCC addresses are all above 90. I will give new addresses to these engines tonight at the club and see if the situation resolves itself. Will report back.
Jeff
Good idea, Jeff. As I said in my previous post, a bunch of us who like to help totally missed that in Ron's post.
Before we jump into any of this, will it hamper the Z-Stuff Data Driver operation of DZ2500's?
Well I just changed the address on my GP35 from 92 to 25. Works with cab 2. Added into DCS app as Legacy diesel address 25 position 1. Shows as active. Engine does not respond to any commands. Although the lcs2 and wifi blink when commands are given. One thing I may add is that TIU3 is hooked up to the LCS 2. 5 TIU's all in super mode. Any ideas? Very frustrating as I was looking forward to using one app for all. Thanks
Jeff
Yesterday at the club, I was content to run both DCS and Legacy by toggling between Icab and the DCS Premium app. I was still determined to figure out why I could not run Legacy engines on the DCS app when I know my hookup was correct. When I got home I decided to go thru this thread line by line and see if there was anything I missed. Then I came across a one line post by George stating that the Old TMCC/TIU cable would not work. Did not know which cable we had. Went to the Train Shack in Burbank and purchased the 50-1032 cable. Voila! SUCCESS!!! Running, finally, Legacy Engjnes with the DCS premium app. Thanks to Marty, Barry, and especially George.
Mystery solved!
Jeff
I am not sure what happened. I have got the SER2 the pdi pdi cable etc, and nothing on LCS now lights up. UGH!!!!! help!!!
John
jbmccormick posted:I am not sure what happened. I have got the SER2 the pdi pdi cable etc, and nothing on LCS now lights up. UGH!!!!! help!!!
John
Did you get the LCS power supply and 9 pin to PDI cable?
MartyE,
Yes, thanks, I was careful to buy all the right pieces. I also read the owners manual and can now see the Lionel wi-fi network on my phone. I have it in access point mode and base (vs. no base). The green light is flashing on the LCS device but nothing is on the SER2. When I turn the track power on and dial up the power on the Legacy remote, the SER2 does respond, but nothing stays on, should it?
What would you recommend next MartyE?
John
My wifi LCS module blinks green with no additional input from the controller but the ser2 is dark. Normal.
No nothing should stay on. The red LED will flash when commands are sent down the PDI bus.
Barry the TPC works up until I plug the Lionel series module into the Y connector and then the TPC does not work. Any ideas? Do I need to get anothe Y connector? Thanks Bruce
Bruce,
Unfortunately, I know very little about the TPC.
Barry the Lionel Track Power Controller uses a hard wire to the Legacy base with 2 wires - DAT and ground. Normally the TPC is hard wired to the Legacy base. I used the Legacy cable - base-TMCC base-Serial connectors. The TPC works with this cable in place. I added the Y connector and the TPC still works. When I connect the Lionel serial box connecter to the Y connector the TPC does not work. My next step is to buy another Y connector if no one has a better idea. Thanks Bruce
A photo or clear diagram of your hookup might help shed light on this. I do not think buying another Y cable will help.
Rudy all I can supply is a writen description. Legacy base to supplied Legacy cable. Serial end to Y cable. 2nd Y cable end to serial 2 wire connection to Lionel Track Power Controller. Third end of Y connector to 6-81499 DB9 + 12V power cable that connects to 6-81326 SER2. Thanks Bruce
The Y cable supplied with a legacy base is expressly for the purpose of connecting and original base 1 to your legacy base. I do not think it should be used in your configuration. Take a look at the SER 2 manual and review the different examples there.
I have not experimented with the MTH product, but I would recommend that all connected serial devices are fed from the SER2. Perhaps a second SER2 might be necessary to connect all the equipment you have, but in any case the Y cable probably is inappropriate for this configuration.
I do what Rudy says, the SER2 output connects to the TIU serial port.
Access to this requires an OGR Forum Supporting Membership
