开云体育

EngineDriver users,

This version (v2.38.193) has now been released to Production.

You can see the changes here:?.

Hi Steve.

?

Long time user of ED.? Currently running the latest version on my Samsung Galaxy S23 via ESU CabControl WiThrottle server.

?

Yesterday I fired the ESU system and ED up to test some new locos, and I had some strange things happen with some function buttons.

?

When either F0, F8 or F9 are selected, I get an error message as per the screenshot below.

?

The loco then gets released and I have to select it again.

?

I tried several different locos with the same result.

?

All other functions work OK.

?

I switched over to my ESU MobileControl II throttle and the above functions worked just fine.

?

Thoughts?

?

Cheers,

?

Ian Millard

Australia

?

?

Hi Ian,

That message text is sent by the ESU system and simply displayed by EngineDriver.

Have you contacted ESU? If not, please do so and see what they say causes that error.

Unfortunately, I've no experience or testing with their WiThrottle Server.

I don't know of any differences or changes in what EngineDriver sends for function keys. But you can view or save the EngineDriver log immediately after sending an accepted FKey, then one that is not accepted. Screenshot that and we can verify the syntax is the same.

--SteveT

Ian,

As Steve asked...

?

Can view or save the EngineDriver log screen immediately after sending an accepted FKey, then one that is not accepted.

?

Screenshot that and we can verify the syntax is the same.

?

--

Peter Akers?
[South East Queensland - Australia - UTC+10]?

Hi Peter/Steve.

?

See attached log file.

?

It took me a while to scroll through and find where I was pushing the function buttons, but if you look around timestamps 13:10:06.889 to 13:10:10.661, this is where I hit F2 to play the horn, which worked, then hit F8 which is when I get the error message.? Same thing from timestamp 13:10:16.181 to 13:10:19.625, except I hit F0 after hitting F2.

?

Strange thing is I have an older version of ED installed on my MobileControl II handset and the functions worked OK.? Version number is v2.37.187

?

I haven't contacted ESU yet, but I'll wait for your response.

?

Cheers,

?

Ian

Ian,?

Thanks for the log.

?

13:10:07.131 12572 12598 D Engine_Driver: comm_thread.wifiSend: ? ? ? ? ? ?-->:M0AL954<;>F102 (2693) ? ? ? ? ? ? ?
13:10:07.155 12572 12860 D Engine_Driver: comm_thread.processWifiResponse: <--:M0AL954<;>F102 ? ? ? ? ? ? ? ? ? ??
13:10:07.727 12572 12598 D Engine_Driver: comm_thread.wifiSend: ? ? ? ? ? ?-->:M0AL954<;>F002 (596) ? ? ? ? ? ? ??
13:10:07.745 12572 12860 D Engine_Driver: comm_thread.processWifiResponse: <--:M0AL954<;>F002 ? ? ? ? ? ? ? ? ? ??
13:10:10.609 12572 12598 D Engine_Driver: comm_thread.wifiSend: ? ? ? ? ? ?-->:M0A*<;>F108 (2882) ? ? ? ? ? ? ? ??
13:10:10.610 12572 12598 D Engine_Driver: comm_thread.timingSensitive: timeSensitive msg, not requeuing: ? ? ? ? ?
13:10:10.610 12572 12598 D Engine_Driver: comm_thread.wifiSend: ? ? ? ? ? ?-->:M0A*<;>F008 (1) ? ? ? ? ? ? ? ? ? ?
13:10:10.651 12572 12860 D Engine_Driver: comm_thread.processWifiResponse: <--:HMESU: Error while writing: ?SYNTAX

?

13:10:16.571 12572 12598 D Engine_Driver: comm_thread.wifiSend: ? ? ? ? ? ?-->:M0AL954<;>F102 (2417) ? ? ? ? ? ? ?
13:10:16.588 12572 12860 D Engine_Driver: comm_thread.processWifiResponse: <--:M0AL954<;>F102 ? ? ? ? ? ? ? ? ? ??
13:10:17.241 12572 12598 D Engine_Driver: comm_thread.wifiSend: ? ? ? ? ? ?-->:M0AL954<;>F002 (670) ? ? ? ? ? ? ??
13:10:17.276 12572 12860 D Engine_Driver: comm_thread.processWifiResponse: <--:M0AL954<;>F002 ? ? ? ? ? ? ? ? ? ??
13:10:19.579 12572 12598 D Engine_Driver: comm_thread.wifiSend: ? ? ? ? ? ?-->:M0AL954<;>F100 (2338) ? ? ? ? ? ? ?
13:10:19.580 12572 12598 D Engine_Driver: comm_thread.timingSensitive: timeSensitive msg, not requeuing: ? ? ? ? ?
13:10:19.580 12572 12598 D Engine_Driver: comm_thread.wifiSend: ? ? ? ? ? ?-->:M0AL954<;>F000 (0) ? ? ? ? ? ? ? ??
13:10:19.619 12572 12860 D Engine_Driver: comm_thread.processWifiResponse: <--:HMESU: Error while writing: ?SYNTAX

?

Note: The number in parenthesis is the time since the last message.

?

So the errors match the only 2 times we sent an FKey without the normal 200ms delay.?

My _guess_ is ESU cannot handle two commands without a gap. You could verify this with them if you'd like.

?

As a further test, I'd like you to try various FKeys, but with very deliberate down, wait, up presses. Then try quick presses. Send us that log file.

?

I don't recall why EngineDriver treats some (or all) FKeys as "timesensitive", maybe Peter recalls.

If this is the problem, maybe we should add an exception for "ESU" to always enforce the gap between commands.

?

--SteveT

?

I can't think of any reason why we would bypass the timer.?

?

I'll look tonight.?

--

Peter Akers?
[South East Queensland - Australia - UTC+10]?

Hi Steve,

?

See attached new log file.? Not sure if I was doing your requested F-key presses correctly.? I pretty much went through functions 0 to 9 with varying delays between each press.? Again, F0, F8 and F9 produced the SYNTAX error.

?

As a further test, I found I had ED on an old Samsung tablet, with v2.37.187 installed and it's functions keys worked perfectly.? I then loaded the latest version of ED on another Samsung tablet and the same "SYNTAX" error happened with F0, F8 and F9.

?

This to me points to an issue with the latest version of ED compared to v2.37.187.

?

Cheers,

?

Ian

?

?

?

?

Thanks. Can you provide a similar log from one of the devices that does not cause the error?

I'd like to compare what we are sending.?

Other than the timing, I'm not seeing a difference yet.

--SteveT?

?

Ian,

I'm looking at your 2nd log now. In this one, twice, the error occurred on the DOWN message, with plenty of time since the prior message. Only one shows the error on the UP, with little gap. So it doesn't look like the timing is the issue.

The syntax of all of the FKey messages is exactly the same, so I still don't understand why ESU doesn't like some of the F00, F08 and F09 messages.

I'd still like to compare a log from a device that doesn't show this issue. I'll be surprised if the messages are different, but I'd like to see for sure.

Unless we find some difference, ESU is going to need to advise what could cause that message.

In the past, several hardware manufacturers sent me demos of their WiThrottle Servers so I could test with EngineDriver. ESU did not, so users like you become the first line of testing and debugging.

--SteveT

Hi Steve,

?

Find attached the log file from the Galaxy Tablet with ED v2.37.187 installed.? Functions all worked OK.

?

Cheers,

?

Ian

Ian,

Thanks for that log.

I see a definite change in what EngineDriver is sending.?

The one that ESU likes (v2.37.187):

-->:M0A*<;>F08 --FKey 8 down

-->:M0A*<;>F18 --FKey 8 up

The one that ESU doesn't like (v2.39.193):?

Ian,

Please try the v2.39.194b alpha version available for manual install here:

It removes the leading zero from the F0-F9 commands. I'm hopeful this will make the ESU command station happy again.

--SteveT

Hi Steve,

?

Yep, that's fixed the issue.? F0 to F9 all working as they should.

?

Ian