Despx,
<<I try to pull the UART as frequently as possible but it is inevitable that I lose some commands from the ESP-01 coming from Engine Driver>>
So the command packet makes it to your server, but you lose it after it arrives successfully? That really doesn't sound like a problem the remote client should be concerned with. How do you know how many messages you missed? For which throttle?
Alternate approach: since you know your current value, just send it back to the client to update the UI.
<<It works but it's like turning off the engine of a car every time you change the gear>>
Not from my perspective. This only occurs on loss of connection. So more like restarting the car after getting a new engine, and having it maintain current speed, radio station and volume. :)
<<any program has a help>>
You're not asking for user help, we have quite a bit of that, plus internet videos, etc. You're asking for programming help to write a replacement server for your use. Not really a big audience there.
Regarding the WiThrottle protocol documentation (you linked earlier), if you find something lacking, please create a PR with suggested updates and additions.
<<I was hoping for something simpler .... like JMRI log files>>
logcat is the recommended (required?) Android logging method. adb provides excellent filter functions, etc. Have you tried it?
Despx, your goal is laudable, but I think the Engine Driver developers' time is better spent adding user-focused features.
Regards,
SteveT
