Hi,
The new wooden e-Board replaces both the old USB and Serial (tournament) e-Boards. It is not a wireless e-Board, but it is compatible with a wireless system that is under development. The Smartboards are also compatible with this wireless system. To connect to the boards using the new wireless system some modifications are needed to Picochess as it uses Bluetooth Low Energy instead of classic Bluetooth like used in the current Bluetooth e-Boards and Revelation II.
You can recognize the new e-Boards by the USB-C port and the different look of the side plate:
More information on:
http://dgt.nl/index.php/news/607-say-goodbye-to-old-serial-connections
kind regards
Lucas van der Ploeg | DGT
--
You received this message because you are subscribed to the Google Groups "PicoChess" group.
To unsubscribe from this group and stop receiving emails from it, send an email to picochess+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/picochess/d67ccb8f-d551-4de1-b32d-2c1d532fbc58n%40googlegroups.com.
Am 16.12.2020 um 21:08 schrieb Brian Erdelyi <brian....@gmail.com>:
I think I understand why some people connect the DGT3000 directly to the Raspberry Pi now :).
--
You received this message because you are subscribed to the Google Groups "PicoChess" group.
To unsubscribe from this group and stop receiving emails from it, send an email to picochess+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/picochess/d5d1339b-d933-4026-9b93-c3056bc06627n%40googlegroups.com.
You can find more information in these follwong threads:
The hardware I use: https://groups.google.com/g/picochess/c/jC-EEwEd15M
More about the features of the PicoChess V3 software: https://groups.google.com/g/picochess/c/HM2Dtzt6gic
More about my „enhanced uci engine“ concept which allows to easily integrate my PGN replay engine and online engines: https://groups.google.com/g/picochess/c/czHRxH9HLw4
The thread for the V3 image for the Raspebrry Pi (DGTPI and nonDGTPI versions):https://groups.google.com/g/picochess/c/SpNFpp2Scw4
Am 16.12.2020 um 21:20 schrieb Brian Erdelyi <brian....@gmail.com>:
Randy: I expect the clock is the same in the DGT Pi and DGT3000. I expect it's a limitation of communicating with the clock through the DGT board.Dirk: What did PicoChess v3 do regarding DGT3000 or DGT Pi? Do you have screenshots of the DGT3000 or DGT Pi displays showing some of the new features?
--
You received this message because you are subscribed to the Google Groups "PicoChess" group.
To unsubscribe from this group and stop receiving emails from it, send an email to picochess+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/picochess/3db4a530-2126-496d-95a4-f2f3e09e96e9n%40googlegroups.com.
Actually this is one of the advantages of the new e-Board and the Smartboard, they support the new protocol (I²C) instead of the old one (SBI). This means you can use the full functionality of the DGT3000 from these chess boards. You can put 11 characters on the screen, you can program the clock and you can get much more information out of it. Also the communication to the clock is much faster.
Unfortunately all the old board cannot support this (including Bluetooth e-Bard) and they would need new electronics to get these functionality.
There are new commands to use these features. Do not send these commands to the old boards, so if you want to implement this you have to make sure you are talking to a board with version number higher than or equal to 4.0.
#define DGT_SEND_I2C_CLOCK 0x56
/* Results in a DGT_MSG_I2C message
*/
#define DGT_SEND_UPDATE_I2C 0x57
/* Results in DGT_MSG_FIELD_UPDATE messages and DGT_MSG_I2C messages
*/
#define DGT_SEND_UPDATE_I2C_NICE 0x58
/* results in DGT_MSG_FIELD_UPDATE messages and DGT_MSG_I2C messages,
* the latter only at time changes,
* as long as the board is in UPDATE_NICE mode*/
#define DGT_I2C_CLOCK_MESSAGE 0x2c
/* This message contains a command for the clock. There are clock commands
* for showing text, displaying icons, setting beep, clearing display,
* and for setting clock times. All these clock commands are wrapped
* within the DGT_I2C_CLOCK_MESSAGE command.
*
* byte 1 - DGT_CLOCK_MESSAGE (= 0x2c)
* byte 2 - the size of the following bytes (total-2) 5 to 64
* byte 3..n-1 - I2C packet
* byte n - end of message (= 0x00)
*
* for I2C packet description see dgt_i2c.h
*/
#define DGT_MSG_I2C 0xa3
/* byte 1: DGT_MSG_I2C
* byte 2: LLH_SEVEN(size)
* byte 3: LLL_SEVEN(size)
* byte 4..n: I2C packet
*
* for I2C packet description see dgt_i2c.h
* see dgt_i2c.h
*/
The contents of these I²C messages can be found in https://github.com/lucasvdp/dgtpi
First byte is destination, second byte source, third byte length, fourth byte command, last byte CRC16 checksum.
I will talk to my colleagues about putting the full documentation online.
Best regards,
Lucas van der Ploeg | DGT
From: pico...@googlegroups.com [mailto:pico...@googlegroups.com]
On Behalf Of RandyR
Sent: 16 December 2020 21:14
To: PicoChess <pico...@googlegroups.com>
Subject: Re: Next Gen DGT Wireless eBoard
Is this a software limitation of the DGT board when sending info to the clock via the clock cable? Maybe DGT could update the firmware to support 11 characters. Or maybe it's in the clock?
Randy
--
You received this message because you are subscribed to the Google Groups "PicoChess" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
picochess+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/picochess/67a0321c-6b9c-478d-b257-d8b0c60aa535n%40googlegroups.com.
Hi,
That is correct, the Smartboard can support the 11 characters. Only this is not just changing one command, you would also need to change the way you read the buttons start the clock and read the clock. This all without breaking stuff for people who do not have a Smartboard or new USB-C e-Board.
Best regards,
Lucas van der Ploeg | DGT
To view this discussion on the web visit https://groups.google.com/d/msgid/picochess/99ad6642-75b4-4c0e-a170-0466558cfcffn%40googlegroups.com.