WiFi connection always fails on first try

[FrightRisk]

ED version 2.39.195
Samsung Galaxy S21+
DCC-EX CSB1 v5.4.6

Have not noticed this before, but had mostly used a Mega, 8874, and WiFi shield before. I used to be able to leave default settings where I did not have to set my 5G and 2.4G home connection to "do not automatically reconnect". Now I do. Still, the first time I run engine driver, it finds the network and I click on it. The first attempt always fails ("failed to connect") and then I click on it again and it works. The ED 3000ms delay setting doesn't seem to be the issue, since I can let ED run for a minute before clicking on the DCCEX_123456 network.

Also, isn't there any way to save the logs to the download folder instead of a very long and obscure folder? On my phone at least, you have to download a 3rd party utility or connect the phone via USB to find the correct folder. And while "Internal shared storage\Android\data\jmri.enginedriver\files/" is a long folder name, "jmri" in the name is confusing. And a name like "logcat1699833098998.txt" might be more intuitively named "engine_driver_20250315001.log" or similar than logcat and a .txt extension. At least then you could search for "engine" or "driver".

Tried to find help on the ED website, but searching variations of "log" and "save" and looking through all the menus do not have any information about saving log files, where they are, etc. The name on my phone is too long to show me the entire name, but found it on the DCC-EX website instructions. I could help provide a help page since you are having to do it all with just one or two of you.

Log below. The phone log shows "Can't connect to 192.168.4.1:2560 fro 192.168.4.2 - failed to connect to /192.168.4.1(port 2560) from /192.0.0.2(port 40994) after 3000ms.

logcat1742071861926.txt

[flash62au]

Saving a log file is described in detail on the website
https://enginedriver.mstevetodd.com/operation/interface.html#saving-a-log-file

It is a permission issue as to why we can't save it elsewhere.

The system itself generates the log file. We have no control over the name.

Peter

[mstevetodd]

@FrightRisk
Regarding the "1st time connect fail", do you refer to 1st-time with an instance of EngineDriver? Or the 1st time since restarting the EX-CS? Or something else? In other words, if you restart ED but not EX-CS, do you have the issue again?
Also, are you able to try it with other permutations (as a test), like using WiThrottle protocol, or via JMRI, or other?
I've not been able to duplicate it with my traveling setup (EX-CS on the Internet). I'll try it again when I'm in range of the EX-CS wifi.
It would also be helpful to have a serial log of the failed and successful connection attempts. I'll try to grab one of those as well.

[mstevetodd]

@FrightRisk
I loaded v2.39.195 on my Pixel 8 Pro and v5.4.6 on my EX-CSB1, connected to the DCCEX_nnnnnn network, and I cannot duplicate your issue. I connect first time, every time.
Note that I have no Routes, Turnouts or Rosters defined for this test. Can you try that?
--STeveT

[flash62au]

I have at times seen the issue, but it has never been consistent. I can't reliably reproduce it.