Skip to main content

The actual procedure is the same, how you connect the PC to the base to make the module is the difference.

Depending how your WiFi is configured either part of the home network or as a stand alone access point, use the LSU 2.0 (Legacy System Utility) to connect  but go to the configure tab and change the communication type to WiFi. You’ll either connect directly to your LCS WiFi module or via your home network.  Enter the IP address of the WiFi module.

Once connected it's all the same.

Eric's Trains has a pretty good video as well.

EC096159-7226-4031-885C-C42FD782A31C

Attachments

Images (1)
  • EC096159-7226-4031-885C-C42FD782A31C
Last edited by MartyE

GRJ-

i have not had good experience with having the LCS WiFi part of my network (not due to lack of trying).  I’m fairly network savvy and I had frequent problems with losing connection from my iPad/iPhone losing connection while operating.  I even ordered another LCS WiFi unit to see if that might improve things and it didn’t.  Quite possibly a function of other network traffic around my home.  Really wanted it to work on “Join to Network” but had to revert to “Access Point” which works perfectly.

consider yourself lucky that it’s successful for you!  

@LionelAG posted:
Really wanted it to work on “Join to Network” but had to revert to “Access Point” which works perfectly.

consider yourself lucky that it’s successful for you!  

Until I had the LCS WiFi Monitor LE installed, I had no luck in getting it connected to the network.  The WPS only aspect of the Lionel WiFi was one of the lamest things I've ever seen!  It actually boggles my mind that the lazy developers didn't have a backup plan!  I had no less than four routers, all with WPS, and none of them would connect!  With the LCS WiFi Monitor, I was able to manually configure the network and all was well.

Until I had the LCS WiFi Monitor LE installed, I had no luck in getting it connected to the network.  The WPS only aspect of the Lionel WiFi was one of the lamest things I've ever seen!  It actually boggles my mind that the lazy developers didn't have a backup plan!  I had no less than four routers, all with WPS, and none of them would connect!  With the LCS WiFi Monitor, I was able to manually configure the network and all was well.

Same with my new router. Use the WiFi monitor. There is a video at Lionel that explains how to use it. Just Google Lionel LCS WiFi monitor.

Okay, so I'm back to Join to Network and so far so good.  I previously went through "join to network" and even used the LCS WiFi Monitor program (perhaps user error, etc.).  Was losing IOS device connections.  So...now all IOS devices are connected via LCS WiFi "Join to Network" and I'll report on any problems seen.  I sincerely hope it works long term as I greatly prefer the convenience.

Thanks Gang!

Last edited by LionelAG

My only issue is the Google Mesh Network doesn't have a DHCP reservation feature and occasionally the IP address of the WiFi unit moves and I have to find it again.  Not a big deal, and with a better router, I'd be able to lock it into a fixed IP address.

WAIT!  I looked and apparently Google updated, I see DHCP reservations now!  That may solve the last annoyance!

False alarm, it doesn't work!

Last edited by gunrunnerjohn
@MartyE posted:

And the file contents changed... From the read me file  There is now a Cab 1.7 file and new Read Me.txt

The Cab2 changes made from v1.61 were as follows:
---------------------------------------------

• Added Legacy ENG Type AUX TENDER
• Added the Legacy version touchpad for the Crane and Boom car
• Bug fixes related to ENG Type TMCC Acela
• Fixed bug where red light frequently came on when transmitting to base
• Corrected bugs related to the Train Builder

Do Legacy Crane and Boom cars operate any different than TMCC ones? Will this update at all change how a Cab1-L runs?

@BobbyD posted:

Do Legacy Crane and Boom cars operate any different than TMCC ones? Will this update at all change how a Cab1-L runs?

I don’t have the Legacy crane but I suspect it just allows you to have the proper icons in Legacy mode.

As far as a Cab1L goes this update is only for a Cab2 so there will no change in the operation of a Can1L.


False alarm, it doesn't work!

Its too bad the WiFi monitor doesn't allow you to plug in a static IP.  Its easy to set up the range on any router for non-DHCP addresses.  Sure would take a lot of the random behavior out of the equation.  Since the LCS WiFi probably is not powered regularly when not running, the chance is high that an IP address change/conflict will occur otherwise.

Lionel (Dave), think you can tweak the LCS WiFi Monitor tool to add this seemingly easy addition (Static IP)?  I think THIS alone would greatly enhance stability of LCS WiFi in a "Join to Network" setup.

Well, the WiFi monitor isn't the stumbling block there, you have to have the access point (router) reserving that IP address by MAC address or it's likely to get stepped on at some time in the future.  Reserved addresses really have to be handled by the access point and not by the client.  If the AP reserves an address based on MAC address, anytime that client (the LCS WiFi in this case) makes a DHCP IP address request, it'll always get the reserved address.  Note that MAC addresses are unique, in theory there is only one device in the world that has that six byte MAC address.  In practice it's not quite that perfect, but the system generally works.

@Ron_S posted:

What would keep a legacy 990 base from accepting the upgrade to 1.6?

One of the clubs is 1.52. the upgrade starts but then there is 6 blinking yellow center light before it should be complete.

Have you used the module before in other bases?  I've had a  module write the code perfectly and then not upgrade the base similar to your experience.  A different module worked.

Add Reply

Post
This forum is sponsored by Lionel, LLC
×
×
×
×
Link copied to your clipboard.
×
×