--
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/2d4876ec-c40a-4b71-bbeb-8c57338cabcbn%40googlegroups.com.
--
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/1241809c-0c8c-46bc-9825-3b88dd6b9914n%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/picochess/b1d247c4-849c-4df2-bad8-32fd44f25057n%40googlegroups.com.
This image will fit on a 4GB card. A 7zip-compressed version has a download size of 985 MB (Compared to the previous base image, which ks 1.4GB to download and expands to 7.6 GB.)
After I finish the dev-image (woth git in there and so on), and testing them to see if they actually write and boot correctly, I'll open a new thread to describe the features and for downloading them.
Hi Marcel,
The hciuart.service needs to be replaced to enable the standby mode of the DGT Pi. You can turn the DGT Pi “off” by pushing the button on the bottom and leaving the power connected. When pushing the button again the Pi restarts but the Bluetooth chip does not and is in a different state as the pi expects. This means Bluetooth no longer works after standby. The new hciuart.service fixes this.
Best 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/92e07d30-c64e-4e71-b9ca-4ea9b4d557c7n%40googlegroups.com.
Am 04.08.2020 um 22:21 schrieb mvanthoor <mj.va...@gmail.com>:
To view this discussion on the web visit https://groups.google.com/d/msgid/picochess/4fcf1a9e-7da3-4446-bef1-bc53cdc0581en%40googlegroups.com.
Randy
The instructions I listed were mostly copied from http://docs.picochess.org/en/latest/installation.html#manual-installation.
Randy
If I remember correctly the only change I had to make is the baud rate of the Bluetooth module. At first boot the module has a fixed baud rate. Changing this means the second boot won’t work because the pi assumes the default baud rate. In the service I could change the baud rate to the default value instead of a higher one.
For the new version of RPi OS a lot has changed I guess. Maybe the same trick of only changing the baud rate in the new script still works.
Best regards,
Lucas van der Ploeg | DGT
From: pico...@googlegroups.com [mailto:pico...@googlegroups.com]
On Behalf Of mvanthoor
Sent: 05 August 2020 09:54
To: PicoChess <pico...@googlegroups.com>
Subject: Re: New Picochess v0.9n base image
Lucas says this, earlier in the thread:
--
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/c5c41f45-95e6-4bae-ad4b-2cf615795ca0n%40googlegroups.com.
Or copy btuart and put it in /opt/picochess/etc, change it there, and then add instructions to either replace hciuart.service (Pi3's) or btuart (Pi4's).
I'll change the speed to 115200 in the line in btuart that the Pi4 will execute. People with DGT-boards and/or DGTPi 3 or modded DGT Pi 4 will then have to test it.
Hm.... your install script copies hciuart.service from the picochess/etc directory to /lib/systemd/system. Maybe at the time you wrote your script, there wasn't a hciuart.service, or it was called differently, so you weren't overwriting anything.
Hi Marcel,
this is the „bluetooth fixing thread“ with Eric’s scripts:
https://groups.google.com/g/picochess/c/4dyvi9di6Nc
I have the bash shell script installed and Al the python version - both obviously work, I couldn’t see a big difference…
I will attach both files again in this post.
Just copy the scripts to the picochess/script folder and add the command line to crate like Eric has describe, eg
@reboot /opt/picochess/scripts/fix_bluetooth_4b.sh 1>/opt/picochess/logs/fix_bluetooth_4b.log 2>&1
for the bash shell scripts.
Yep - it looks like we can use the default hciuart service (at least in combination with the fixing scripts for a PI4).
Regrading the USB connection of the BT board: It is a mini USB connection (so not the smallest one) and USB-C is only used in the latest DGT Smart Board (USB only).
I am happy with the speed of the BT connectivity but I think USB might be a little fester - at least what I can tell from various YouTube movies.
Before my Personal V 1.0 version it was a real pain for me to play quick games especially via BT because you often got a „set pieces“ message when executing the engines and your own move too fast in sequence.
With my „Pre-Moves“-Option it is now a real joy for me to play rapid and Blitz games with picochess (you can even execute your own move before the engines move ;-) There might be better or more elegant ways to implement this feature but thatÄs all I could do and for me it works.
By the way: with a BT board and its built-in battery and with an external battery for the DGTPI it gets almost kind of a mobile chess computer solution with almost no cables…
Dirk
P.S: I have never "requested" that you shouldn't use my 2.01 version for your work or base image- I just said it makes no sense to commit changes to my repository because I have already enhanced and further developed my version and I would not recommend to implement some features exactly like I have done etc... So it is up to you to use it or not.
Thanks for posting the files and instructions. I will look into them tomorrow.
Because of this statement, "I would not recommend to implement some features exactly like I have done etc...", I gathered that you wouldn't be happy with your code ending up in a new image as the basis for new developments, because you're not satisfied with this code.
Di you wish me to rephrase this in the roadmap or remove it entirely?
It would be a pity if your work wouldn't be used, because you dud implement some interesting features. I fully intend to "forward port" those to a PicoChess version after it has all its libraries updated. I would certainly appreciate a collaboration for achieving this.
With regard to the pre-move function... I played a very fast game yesterday to test the new player for move announcements. Move announcements are much faster than the clock, but the setup didn't go down the drain. After the computer was out of book and started thinking, the clock was still displaying past moves for some seconds :P
Maybe the USB-board is different in this regard to the BT boards.
After I recover from my cataract operation, I'll start looking into ...