Chessconnect: a free chrome extension for electronic chessboards

Sort:
Ruskie_it
GeorgeGoodnight ha scritto:

Hi Jörn, I've played two rapid games with the app on a Samsung Tab 8 with my DGT Smartboard. Both were flawless. The only thing is it didn't drive my DGT3000 clock. But my guess that is something for later?

Hello everyone and thanks Jorn for this wonderful extension. I also have a DGT board, it's a Rosewood USB board and I am playing with the board connected to my computer and a DGT3000 clock.

I also must say that it seems to have some issues with the clock (the rest is flawless unless I misplace the pieces). What is strange is that it's not that it does not communicate with the clock at all, which I would understand. No, it does, because the time gets updated after the opponent makes a move. At that time, both his time and my time gets updated, and my clock starts counting down. However, when I make a move, it gets transmitted to chess.com just fine, but somehow my time on the DGT3000 doesn't stop counting down, and opponent's one doesn't start ticking down.

This is a problem not only because you don't see the time, but most importantly because when you move, since your clock keeps ticking, you can never be sure if the browser registered your move or it is still your turn, so you're forced to check the screen... Is it a known bug?

GeorgeGoodnight
Ruskie_it wrote:
GeorgeGoodnight ha scritto:

Hi Jörn, I've played two rapid games with the app on a Samsung Tab 8 with my DGT Smartboard. Both were flawless. The only thing is it didn't drive my DGT3000 clock. But my guess that is something for later?

Hello everyone and thanks Jorn for this wonderful extension. I also have a DGT board, it's a Rosewood USB board and I am playing with the board connected to my computer and a DGT3000 clock.

I also must say that it seems to have some issues with the clock (the rest is flawless unless I misplace the pieces). What is strange is that it's not that it does not communicate with the clock at all, which I would understand. No, it does, because the time gets updated after the opponent makes a move. At that time, both his time and my time gets updated, and my clock starts counting down. However, when I make a move, it gets transmitted to chess.com just fine, but somehow the my time on the DGT3000 doesn't stop counting down, and opponent's one doesn't start ticking down.

This is a problem not only because you don't see the time, but most importantly because when you move, since your clock keeps ticking, you can never be sure if the browser registered your move or it is still your turn, so you're forced to check the screen... Is it a known bug?

My clock stayed blank. But my games were on the original beta, I'm not sure if that makes a difference? Are you referring to the Android app or the extension?

I'll have another go tomorrow with my Smartboard and clock.

Ruskie_it
GeorgeGoodnight ha scritto:

My clock stayed blank. But my games were on the original beta, I'm not sure if that makes a difference? Are you referring to the Android app or the extension?

I'll have another go tomorrow with my Smartboard and clock.

Nope. My setup is DGT Usb e-board (wood), DGT3000 and Chrome on Windows. I don't have the Android app and therefore can't make the test.

As I said, one could argue that with my setup it works "more", since the times are displayed on the clock. However, the fact the the countings get updated only when opponents move causes more inconvenience than benefit, because when you move you always have the doubt that it did not register your move...

I guess that with the app, clock info is not transmitted at all, while with the Chrome extension... it is like if an event is triggered when opponent moves (and it triggers the "update_clock" functions) while when you move the event is not triggered and therefore the extension does not send clock information back to the board

joernupbde

@Ruskie_it: I had several other users reporting this problem. While others (including me) have no issues. What exact model of DGT board are you using?

Ruskie_it
joernupbde ha scritto:

@Ruskie_it: I had several other users reporting this problem. While others (including me) have no issues. What exact model of DGT board are you using?

So... I bought my e-board used maaany years ago, when Ebay was THE website for ecommerce (go figure, I had it for less than 100€, it was a bargain), so I don't have the box or the order... but I recently spoke about it with a DGT representative because I asked if it was possible to fit a bluetooth chip in it.
So he asked me for photos and he told me: "I had a look at your photos, and you are the owner of a DGT hirose e-Board." I don't know if that is enough for you to identify it.
I can add that is a usb-only eboard with the old... was it micro-a connector?

If you need, I can run some tests of a development version of your extension

joernupbde

@Ruskie_it: "micro USB" was the info I needed. I'll investigate...

Ruskie_it
joernupbde ha scritto:

@Ruskie_it: "micro USB" was the info I needed. I'll investigate...

Sure. Let me know if you need pictures, or if you want me to run tests.

joernupbde

We have enough beta testers for the app now. Now I need to have the closed beta test running for at least 14 days before I can apply for publication.

GeorgeGoodnight

Great news Jörn.

I've just played two more games on chess.com with my Smartboard. There were a few things I noticed. The first was that there was no move confirmation noise on my moves. The second was that there was an issue with the game end announcements. The outcome of the game was interrupted and the last move was repeated.

Other than that all was great, an enjoyable experience overall.

GeorgeGoodnight

Do Google need it to be used a specific amount in those 14 days?

Ruskie_it
joernupbde ha scritto:

@Ruskie_it: "micro USB" was the info I needed. I'll investigate...

Just wondering... maybe it has something to do with transmission speed? Perhaps with these slower connectors more time has to pass between the sending of the move and the response from the computer with the updated clock time?

GeorgeGoodnight
Ruskie_it wrote:
joernupbde ha scritto:

@Ruskie_it: "micro USB" was the info I needed. I'll investigate...

Just wondering... maybe it has something to do with transmission speed? Perhaps with these slower connectors more time has to pass between the sending of the move and the response from the computer with the updated clock time?

I'm sure you can replace the module to an upgraded one.

joernupbde
GeorgeGoodnight wrote:

Do Google need it to be used a specific amount in those 14 days?

I do not know. I don't think so.

joernupbde
GeorgeGoodnight wrote:
Ruskie_it wrote:
joernupbde ha scritto:

@Ruskie_it: "micro USB" was the info I needed. I'll investigate...

Just wondering... maybe it has something to do with transmission speed? Perhaps with these slower connectors more time has to pass between the sending of the move and the response from the computer with the updated clock time?

I'm sure you can replace the module to an upgraded one.

I found a section in my code that looks suspicious it might be related to this problem. I will check more closely later today.

Ruskie_it
joernupbde ha scritto:
 

I found a section in my code that looks suspicious it might be related to this problem. I will check more closely later today.

Wonderful!

On a different subject, does the clock by any chance also show draws offers? I know (because it appeared once) that it shows 1-0 or 0-1 when opponent resigns, I was wondering if it also displays a draw offer in some way

joernupbde

No. It does not.

joernupbde

@Ruskie_it and myself got the DGT3000 problem sorted out. It's a timing issue with older boards. It's fixed in 4.5.36beta which is already out. I will roll it out to the regular release next week.

Ruskie_it
Ruskie_it ha scritto:
joernupbde ha scritto:

@Ruskie_it: "micro USB" was the info I needed. I'll investigate...

Just wondering... maybe it has something to do with transmission speed? Perhaps with these slower connectors more time has to pass between the sending of the move and the response from the computer with the updated clock time?

And I take full credit for the correct guess without even looking at the code!!! tongue

All that money spent into Uni has finally shown its value!

GeorgeGoodnight
joernupbde wrote:

@Ruskie_it and myself got the DGT3000 problem sorted out. It's a timing issue with older boards. It's fixed in 4.5.36beta which is already out. I will roll it out to the regular release next week.

Great work as usual. Thank you Jörn.

SpanishStallion
It works with Square-off?