jrodrigo
-Interested User-
Posts: 8
Joined: Apr 25, 2015
|
Posted: Jan 28, 2016 04:20 PM
Msg. 1 of 10
I've run some tests with the beta 5.2.0.6 and it does not connect after issuing: S,CONNECT
It simply does nothing, if I click the connect button it connects OK.
Under the 5.1.3.1 version it works as expected, I issue AUTOCONNECT OFF and then CONNECT and it works, no problem.
The beta 5.2.0.6 seems to reconnect when I issue CONNECT after a network loss. It is only the first time after launching the client that CONNECT does not work???
I'm requesting the 5.1 protocol by the way. Here is the the input from the client:
S,CURRENT PROTOCOL,5.1,\r\n S,REGISTER CLIENT APP COMPLETED,\n S,CURRENT LOGINID,xxxxxxx,\n S,CURRENT PASSWORD,xxxxxxx,\n S,LOGIN INFO SAVED,\n S,AUTOCONNECT OFF,\n S,STATS,,,0,0,1,1,0,0,,,Not Connected,5.1.3.1,xxxx,0,0,,0.15,0.0,,\n S,STATS,,,0,0,1,2,0,0,,,Not Connected,5.1.3.1,xxxx,0,0,,0.22,0.22,,\n S,STATS,,,500,0,1,0,0,0,,,Not Connected,5.1.3.1,xxxx,0,0,,0.28,0.14,,\n [...]
Issuing multiple CONNECT and never connects.
Using wine under Linux:
wine-1.9.0-36-g43197e6
Edited by jrodrigo on Jan 28, 2016 at 04:40 PM
|