DGT-3000 Clock issue with latest Bookworm Image on RPI5

[Peter Eggen]

Hi all,

I am just curious as I knew that in the past, my DGT-Clock and Pi worked fine when connected to the USB SmartBoard. The clock showed the eval and moves on the display but now in Mode 25 all I get is -:-------    -:--------- Display. 

Did I missed anything? Maybe this is a result when moving to 64bit OS? If so is there a most recent 32Bit OS port with latest Picochess still available?

Kind regards Peter

[Roy]

Hello Peter,

at the moment it is not possible to use a Raspberry Pi 5 inside a DGT-3000.

The only solution would be a complete reimplementation of a program called "dgtpicom" which is the program that talks to the DGT-3000 via I2C-Protocol.

The RPi5 is using a new system architecture wich the old "dgtpicom" does not support.

Ghislain and I were talking about this problem in this thread: https://groups.google.com/g/picochess/c/tM4Mk3gwsyQ

The problem is not that hard to solve but still requires some skills and time.

Let's see when I find the time to dig deeper into it.

Kind regards,

Roy

[Peter Eggen]

Hi Roy,

thanks for the information, but I knew of the HW differences. I was not intending to wire a DGT-Clock with the I2C Bus of the Pi (which I have tested earlier to be working with a RPI3b), but instead using the Pi in a mode connected to my DGT-Board. So the PI is connected via USB to the Board and the Clock is connected with the standard clock cable to the Board (not the Pi). Previously I was able to see some numbers such as Eval and Moves Information on the Clock Display (despite not using the full display as there are HW limitations when not using the I2C wire), but with the Pi5 and or with the Pi 5 an Bookworm 64 Bit OS I am no longer seeing this. So my intent is to use the Pi in a non-DGTPi kind of mode zo not always look on my iphone to get the moves / evals displayed when clock does same.

Regards Peter

[Peter Eggen]

Fyi: This has now been confirmed to be related to a HW issue with the clock. After a device exchange by the vendor, this has now been resolved and everything seem to work as expected now.

.

Regards Peter