LCS Wi-Fi Module Connection Issue

3 years later, new LCS Wifi unit just received today - it does not want to connect to my Ubiquiti Access points. (AP Network is 2.4ghz only). The gainspan module used seems to be quite crappy, really wish an ethernet port would have been available (to connect to the development switch just 2 feet away!)

On the brightside, my Wifi nic on my dev PC is unused, so I can leave the module in AP mode and just direct access it that way

I had to resort to the LcsWiFiMonitorLE to get mine connected to my router.  That allows me to keep Internet connectivity while using devices to connect to the Legacy.  Also, my desktop can connect to the Legacy system using the LSU and I can edit engines, routes, switches, etc. at my leisure from desktop.

Here's a link to my post with the install files for the monitor.

https://ogrforum.ogaugerr.com/...1#166277369142741941

Wow!  I can't believe this thread is still going.  The LcsWiFiMonitorLE software never helped me get connected. I gave up on it years ago and never looked back.  I have always used a separate switch.  I think I was the one who started this thread.

@Harvy posted:

Wow!  I can't believe this thread is still going.  The LcsWiFiMonitorLE software never helped me get connected. I gave up on it years ago and never looked back.  I have always used a separate switch.  I think I was the one who started this thread.

I just checked and I did start it.  Unfortunately I have much bigger problems to deal with these days.

@Harvy posted:

Wow!  I can't believe this thread is still going.  The LcsWiFiMonitorLE software never helped me get connected. I gave up on it years ago and never looked back.  I have always used a separate switch.  I think I was the one who started this thread.

Yep I'm working on the gargantuan task of building out a REST API-exposed system of controls to bridge the MTH/Legacy remote gap, so I stumbled across this thread troubleshooting.

And yeah the only useful thing for the LCS Monitor software is spying on the serial commands as they bounce around. That wifi connector only likes to tell me the large number of connect errors from when I flip it into Join network mode

@Harvy posted:

Wow!  I can't believe this thread is still going.  The LcsWiFiMonitorLE software never helped me get connected. I gave up on it years ago and never looked back.  I have always used a separate switch.  I think I was the one who started this thread.

What can I say, you're a sample of one.

I got connected in a flash once I had the monitor software and could configure for my router's SSID and password.  The WPS was the stumbling block for most people, it didn't seem to work for many routers.  I helped a few people get their WiFi connected once the monitor was released.

It's way more convenient to have the LSU connected to my computer, editing on a full screen is way better than spinning the knob for hours on the CAB2 to configure locomotives!

@SirCaptain posted:

Yep I'm working on the gargantuan task of building out a REST API-exposed system of controls to bridge the MTH/Legacy remote gap, so I stumbled across this thread troubleshooting.

And yeah the only useful thing for the LCS Monitor software is spying on the serial commands as they bounce around. That wifi connector only likes to tell me the large number of connect errors from when I flip it into Join network mode

Works like a champ here...

@gunrunnerjohn posted:

Works like a champ here...

Yep I suspect it's an issue with multiple AP's. Not going to dig too deep in to it since I have my fallback, just a minor annoyance

Will the base 3 use the LCS and LSU or is it using its own software?

The Base3 has Wi-Fi built-in.  It will still use other LCS modules, but not the Wi-Fi module.

Well, it's certainly going to have it's own software base.  As to what, if any, similarity to the existing WiFi capability or compatibly with the tools like the WiFi monitor, that's clearly a case for someone like @Dave Olson, if anyone can answer the question, he can.