WinBoard and XBoard are GUI's, but they are your pre made interface to any of the chess engines..... people have already taken all the hassle out of interfacing to the actual engine, which by the way, is what actually analyzes the game, the GUI's are just there to "Show" you what is going on with your game and the engine..... Best thing I can suggest is to download the one for you operating system, install it, play with it, and learn it. Then you can determine how much work you want to put into it.My understanding so far is that Winboard and Xboard are just GUI (one for windows and the other for unix or linux I forgot...lol) used to analyse the actual game on the screen...
You have not answered my question regarding the amount of work and the choice of the engine!
Thanks!
Well step 1 is find some open source chess game with source code you can pull the chess logic from. Its gonna have to be a 1 player game but should be easy to find. So once you gots your robo up, you won't have to teach it chess.Hi All
Before I post this I browsed around to find out if it was discussed before and found this link:
http://forum.allaboutcircuits.com/showthread.php?t=64123&highlight=chess
which would be a very good starting point as some of my questions have already been answered there but I will have to re-read this for further understanding and questioning.
First I want to go one step backward and plan my design and stick to it!
BTW, I am trying to make a robot that would be able to play chess!
Here's the high level design block diagram I came up with based on the discusion in the above link as seen in attachment hlevel
Any comments or better suggestion?
second, I decided to break the above high level into different modules to design separately and to be assembled later (attachment mod1, mod2, mod3). I have categorised them into hardware and software modules.
The hardware ones has the following ones:
module1 --> design of chessboard & pieces
module2 --> design of the controller to move pieces
As for module2, I am thinking of design an arm that would be used to move and lift the pieces...But this seems to be the most difficult one for me!!!
And I could not even come up with a good block diagram for it...
The software one has:
module3 --> implementation of Chess engine (on a PC) and all that goes with it.
(still researching/investigating on this one)
Third, the possible different interfacings between these modules:
1. interfacing between module1 and module3: I read somewhere (can't remember) parallel port would be easier,...
2. interfacing between module3 and module2: serial cable, bluetooth,...
3. interfacing between module2 and module1 (how are the board and the controller 'arm' attached together? this would be mechanical I guess)
Any suggestion on the different interfacing and their advantages (would definitely choose the one that would make my life easier)
The system would also have the additional software modules:
module4 --> communication protocol between module1 and module3
module5 --> communication protocol between module3 and module2
Anything missing in my design strategy?
All comments are welcomed!