Author: Ingo Bauer
Date: 10:59:02 02/08/05
Go up one level in this thread
Hello >its possible that my engine send "info string example" after it gets "UCI" >statement. Thats working fine under Arena. >But my ChessPartner 5.3 GUI hang up after sending this string before >"setoption x" with "uciok" comes. > >i'm not sure if its not allow to send info strings before "uciok" or its a CP >bug. > >Whats right ? Arena is very relaxed in some point regarding the UCI protocol, on the other hand if Chesspartner realy locks when a wrong statement is comming, that is wrong too because: * if the engine or the GUI receives an unknown command or token it should just ignore it and try to parse the rest of the string in this line. Why didnt you have a look at the UCI specification, it is quite clear in there: .................................................................................. * uci tell engine to use the uci (universal chess interface), this will be sent once as a first command after program boot to tell the engine to switch to uci mode. After receiving the uci command the engine must identify itself with the "id" command and send the "option" commands to tell the GUI which engine settings the engine supports if any. After that the engine should send "uciok" to acknowledge the uci mode. If no uciok is sent within a certain time period, the engine task will be killed by the GUI. ................................................................................. So only "id" and "option" and of course a "uciok" is allowed. Why do you send an info string after your engine recieves an "uci". NO need for that? Bye Ingo
This page took 0 seconds to execute
Last modified: Thu, 15 Apr 21 08:11:13 -0700
Current Computer Chess Club Forums at Talkchess. This site by Sean Mintz.