Comments

• 

  about 4 hours ago by mkubecek | Reply

  Some challenges:

  1. While the the boards, whether old ones with serial port or newer ones with USB (micro or Type C), are presented as serial device on Linux, the communication protocol is not publicly documented. Parts of the reverse engineering made by other projects can be reused and I was also able to recover a previously published documentation which disappeared from the DGT site but some extensions for new devices still need to be found by trial and error.

  2. The board itself does not identify moves but only events like "e2 is now empty" or "a white pawn appeared on e4". Translating these events has to be done by software which is a non-trivial task, especially for complex moves (capture, castling, promotion) and some specifics of the board implementation make it even trickier. For example, the squares are scanned in certain order and this scan takes a non-trivial time so that events may be sent in order different order than they actually happened. (E.g. for a move a2-a4, the "white pawn appeared on a4" event may precede the "a2 is now empty" one.) Also, when a piece is shifted from the initial square to destination one, it may be seen on intermediate squares for a short moment.

×
Edit Comment 12757
# A First Level Header
## A Second Level Header

Use one asterisk to *emphasize*

Use two asterisks for **strong emphasis**

- Use hyphens
- for unordereed
- lists

This is an [link to example.com](http://example.com/)

This is an image ![an openSUSE geeko icon](https://en.opensuse.org/images/d/d0/Icon-distribution.png)

This is a user link @hans

This is a project link hw#some-cool-title
More Complex Markdown Help
Formatting Help
• Edit
• Preview
Some challenges: 1. While the the boards, whether old ones with serial port or newer ones with USB (micro or Type C), are presented as serial device on Linux, the communication protocol is not publicly documented. Parts of the reverse engineering made by other projects can be reused and I was also able to recover a previously published documentation which disappeared from the DGT site but some extensions for new devices still need to be found by trial and error. 2. The board itself does not identify moves but only events like "e2 is now empty" or "a white pawn appeared on e4". Translating these events has to be done by software which is a non-trivial task, especially for complex moves (capture, castling, promotion) and some specifics of the board implementation make it even trickier. For example, the squares are scanned in certain order and this scan takes a non-trivial time so that events may be sent in order different order than they actually happened. (E.g. for a move a2-a4, the "white pawn appeared on a4" event may precede the "a2 is now empty" one.) Also, when a piece is shifted from the initial square to destination one, it may be seen on intermediate squares for a short moment.
 
×
Reply to mkubecek
Some challenges:
1. While the the boards, whether old ones with serial port or newer ones with USB (micro or Type C), are presented as serial device on Linux, the communication protocol is not publicly documented. Parts of the reverse engineering made by other projects can be reused and I was also able to recover a previously published documentation which disappeared from the DGT site but some extensions for new devices still need to be found by trial and error.

2. The board itself does not identify moves but only events like "e2 is now empty" or "a white pawn appeared on e4". Translating these events has to be done by software which is a non-trivial task, especially for complex moves (capture, castling, promotion) and some specifics of the board implementation make it even trickier. For example, the squares are scanned in certain order and this scan takes a non-trivial time so that events may be sent in order different order than they actually happened. (E.g. for a move a2-a4, the "white pawn appeared on a4" event may precede the "a2 is now empty" one.) Also, when a piece is shifted from the initial square to destination one, it may be seen on intermediate squares for a short moment.
---
# A First Level Header
## A Second Level Header

Use one asterisk to *emphasize*

Use two asterisks for **strong emphasis**

- Use hyphens
- for unordereed
- lists

This is an [link to example.com](http://example.com/)

This is an image ![an openSUSE geeko icon](https://en.opensuse.org/images/d/d0/Icon-distribution.png)

This is a user link @hans

This is a project link hw#some-cool-title
More Complex Markdown Help
Formatting Help
• Edit
• Preview