Hi t0bit0bsen,
The screensavers are self-contained directories created as plugins. But there are also the icons representing each screensaver. Those icons are located outside of screensaver directories. If you want to replace/update the existing screensaver (e.g. Clock) you can just replace the existing directory ( e.g. screensaver/clock) by new one and it will work. For new screensavers it's more complicated - besides the new directory you need the screensaver icon in the 'icons' directory and entry in the config.txt file for each screensaver in the section [screensaver.menu].
Best regards
The screensavers are self-contained directories created as plugins. But there are also the icons representing each screensaver. Those icons are located outside of screensaver directories. If you want to replace/update the existing screensaver (e.g. Clock) you can just replace the existing directory ( e.g. screensaver/clock) by new one and it will work. For new screensavers it's more complicated - besides the new directory you need the screensaver icon in the 'icons' directory and entry in the config.txt file for each screensaver in the section [screensaver.menu].
Best regards
Hi rpi,
thanks for the fast reply. It worked, somehow. But for "image"-mode of the clock something strange happens, the assignment of the images does not work as expected:
Instead of the colon, a 6 is displayed, number 3 shown as tube is in fact a 1, if I see the colon, it is meant to be a 2 and so on. I renamed the Nixie-Images and time is presented correct:
Do you have a similar issue?
Best regards
Tobias
thanks for the fast reply. It worked, somehow. But for "image"-mode of the clock something strange happens, the assignment of the images does not work as expected:
Instead of the colon, a 6 is displayed, number 3 shown as tube is in fact a 1, if I see the colon, it is meant to be a 2 and so on. I renamed the Nixie-Images and time is presented correct:
Do you have a similar issue?
Best regards
Tobias
Hi, this is a bug in the code. The default file sort order is different on Windows (used for development) and Linux (Pi).
The following line should be added to fix the issue:
https://github.com/project-owner/Pe...3aaa00679ebb3/screensaver/clock/clock.py#L186
I'll update the disk images soon.
Thank you!
The following line should be added to fix the issue:
https://github.com/project-owner/Pe...3aaa00679ebb3/screensaver/clock/clock.py#L186
I'll update the disk images soon.
Thank you!
Hi,
There is no image for 1.3" display. So, the recommendation is to use the Headless image, make sure everything works (use Web Browser for UI) then install display driver. You can check Amala's comments about the display driver here:
https://github.com/project-owner/PeppyPlayers.doc/wiki/Gallery#nanopeppy-by-amala-indonesia
Best regards
There is no image for 1.3" display. So, the recommendation is to use the Headless image, make sure everything works (use Web Browser for UI) then install display driver. You can check Amala's comments about the display driver here:
https://github.com/project-owner/PeppyPlayers.doc/wiki/Gallery#nanopeppy-by-amala-indonesia
Best regards
Decided to give peppy a try. Very impressed with what I read and I would be very please with the CD drive capabilities. Want to use a Pi 3B with a 7" HDMI + touch drive (Ali Express part). As there is no 7" HDMI image available I downloaded the 5" HDMI version. Read that this version would likely be fully operational. Starting up thind look fine, however the touch function does not operate. Tried to make changes with the suggestions I read in several places but that does not get me anywhere. In general after changes things seem to be corrupted so much that the device does not completely start up anymore (cycling the start up screen, however SSH still active) or Web service not working anymore or completely dead. In all cases I still do not get touch working.... So I keep writing the SD-card again and again. Does anyone have a suggestion how to get this touch screen working? The 7" HDMI touch screen des seem to be a popular device, so I would exprect that someone went through the process before. Thanks in advance for your input!
By the way, the touch screen is operational when I run the 32 bit Buster OS and when I install Peppy it is the Signac 5"version.
Hi,
Please provide the link to the display. Is there any driver for that display which you need to install? Did you install it?
After driver installation I'd recommend to follow the steps for touchscreen calibration described here:
https://github.com/project-owner/Pe...e-5.0#configure-the-touchscreen-functionality
Just ignore the driver installation steps as that should be the driver for your display.
Best regards
Please provide the link to the display. Is there any driver for that display which you need to install? Did you install it?
After driver installation I'd recommend to follow the steps for touchscreen calibration described here:
https://github.com/project-owner/Pe...e-5.0#configure-the-touchscreen-functionality
Just ignore the driver installation steps as that should be the driver for your display.
Best regards
Hi RPI! Thank you for your very prompt reaction 
.
First of all a driver was not needed to get the device working on the standard Raspberry Buster OS. Just plug and play as one hopes...
I will have a look at the page you suggest tomorrow. We are late on the Saturday evening and we all know what happens with reading accuracy and understanding of what is written. Will get back on this.
Regards,
Peter.
.First of all a driver was not needed to get the device working on the standard Raspberry Buster OS. Just plug and play as one hopes...
I will have a look at the page you suggest tomorrow. We are late on the Saturday evening and we all know what happens with reading accuracy and understanding of what is written. Will get back on this.
Regards,
Peter.
Oh, the link you requested is:
https://www.aliexpress.com/item/100...t_main.24.25ec79d2xPqoEp&gatewayAdapt=glo2nld
https://www.aliexpress.com/item/100...t_main.24.25ec79d2xPqoEp&gatewayAdapt=glo2nld
It looks like a clone of this Waveshare display:
https://www.waveshare.com/product/displays/lcd-oled/lcd-oled-1/7inch-hdmi-lcd-h.htm
https://www.waveshare.com/wiki/7inch_HDMI_LCD_(H)_(with_case)
but almost two times cheaper.
Before the calibration process you need to stop the player service to "release" the display for the calibration by running the following command in a terminal:
sudo systemctl stop peppy.service
Then run the calibration command and follow the instructions on the screen. The device in the command can be /dev/fb0. You can check which device is available by listing the folder content in a terminal (ls /dev). Calibration command:
sudo TSLIB_FBDEVICE=/dev/fb1 TSLIB_TSDEVICE=/dev/input/touchscreen ts_calibrate
That will create the device /dev/input/touchscreen which is used by the player as a source of touch events.
After calibration start the player service:
sudo systemctl start peppy.service
Best regards
Last edited:
Hi rpi.
Thank you for your second follow-up message of yesterday.
I did an attempt today but I am afraid I did not get very far.....
I checked the ls /dev and found that I do have a fb0
Also noted that device /dev/input/touchscreen exists, but that will likely have been created earlier when you prepared the image for the 5" display.
Anyway the next step was stopping the player service with "sudo systemctl stop peppy.service"
To my surprize however this command seems to kill everything, including the SSH connection. The Pi is dead and a power cycle is needed to bring it to life again. So I am not able to run the callibration.....
Am I missing something? Your input is appreciated.
Peter.
Thank you for your second follow-up message of yesterday.
I did an attempt today but I am afraid I did not get very far.....
I checked the ls /dev and found that I do have a fb0
Also noted that device /dev/input/touchscreen exists, but that will likely have been created earlier when you prepared the image for the 5" display.
Anyway the next step was stopping the player service with "sudo systemctl stop peppy.service"
To my surprize however this command seems to kill everything, including the SSH connection. The Pi is dead and a power cycle is needed to bring it to life again. So I am not able to run the callibration.....
Am I missing something? Your input is appreciated.
Peter.
Please run the following command before the 'stop' command:
sudo systemctl disable peppy.service
and then:
sudo systemctl stop peppy.service
This way after restarting the player it will not be running and should allow calibration. When you are done with calibration run these command:
sudo systemctl enable peppy.service
sudo systemctl start peppy.service
Best regards
sudo systemctl disable peppy.service
and then:
sudo systemctl stop peppy.service
This way after restarting the player it will not be running and should allow calibration. When you are done with calibration run these command:
sudo systemctl enable peppy.service
sudo systemctl start peppy.service
Best regards
To give a bit more information, when I issue the calibration command with /dev/fb1 I get the reply "open fbdevice: No such file or directory". This is as expected. Issuing with /dev/fb0 the reaction is "xres = 800, yres = 480" and the crosshair on screen. However, as mentioned above, no reaction touching the screen.....
The native/hardware resolution of your display is 1024×600. It's probably not required but recommended to define it in the /boot/config.txt:
https://github.com/project-owner/Pe...e-5.0#configure-the-touchscreen-functionality
Define your resolution instead of 800x480.
Later on you need to do the same in the player:
https://github.com/project-owner/Peppy/blob/98faba2e1b88b3fcdb4083a600cc17dc52ff1efb/config.txt#L2
It looks like you have /dev/fb0 for your display. It should be specified in the calibration command:
sudo TSLIB_FBDEVICE=/dev/fb0 TSLIB_TSDEVICE=/dev/input/touchscreen ts_calibrate
Also make sure that you have the following rule in the file /etc/udev/rules.d/95-ads7846.rules:
SUBSYSTEM=="input", KERNEL=="event[0-9]*", ATTRS{name}=="ADS7846 Touchscreen", SYMLINK+="input/touchscreen"
If all this doesn't help after reboot then more likely the chipset used on your display is not ADS7846 and it should be found.
Best regards
https://github.com/project-owner/Pe...e-5.0#configure-the-touchscreen-functionality
Define your resolution instead of 800x480.
Later on you need to do the same in the player:
https://github.com/project-owner/Peppy/blob/98faba2e1b88b3fcdb4083a600cc17dc52ff1efb/config.txt#L2
It looks like you have /dev/fb0 for your display. It should be specified in the calibration command:
sudo TSLIB_FBDEVICE=/dev/fb0 TSLIB_TSDEVICE=/dev/input/touchscreen ts_calibrate
Also make sure that you have the following rule in the file /etc/udev/rules.d/95-ads7846.rules:
SUBSYSTEM=="input", KERNEL=="event[0-9]*", ATTRS{name}=="ADS7846 Touchscreen", SYMLINK+="input/touchscreen"
If all this doesn't help after reboot then more likely the chipset used on your display is not ADS7846 and it should be found.
Best regards
Hi there.
Thank you again for your support!
I have changed the display setting to 1024 x 600 as per your suggestion.
Also verified the calibtation device setting and the rules. They were both correct.
Tried to run the calibration program (after stopping the peppy service) and, besides the resolution change which gave smaller characters (obviously), thre is no change. Crosshair is on the screen, but clicking it does not seem to work and th eprogram is halted untill I enter a Ctl C.
I did a dmsg to see what can be found related to touch or ADS7846. Found a couple of entries. Maybe this helps??
[ 7.665244] input: 深圳市全动电子技术有限公司 ByQDtech 触控USB鼠标 as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3/1-1.3:1.0/0003:0483t/input1
[ 7.665983] hid-multitouch 0003:0483:5750.0001: input,hidraw0: USB HID v1.10 Device [深圳市全动电子技术有限公司 ByQDtech 触控USB鼠标] on us1.3/input0
[ 7.694130] brcmfmac: F1 signature read @0x18000000=0x15264345
[ 7.725243] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
[ 7.727205] usbcore: registered new interface driver brcmfmac
[ 8.053612] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
[ 8.053806] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
[ 8.077362] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Jan 4 2021 19:56:29 version 7.45.229 (617f1f5 CY) FWID 01-2dbd9d2e
[ 8.602797] ads7846 spi0.1: supply vcc not found, using dummy regulator
[ 8.603701] ads7846 spi0.1: touchscreen, irq 200
[ 8.612199] input: ADS7846 Touchscreen as /devices/platform/soc/3f204000.spi/spi_master/spi0/spi0.1/input/input2
[ 8.994727] random: crng init done
and towards the end:
[ 879.050820] usb 1-1.3: USB disconnect, device number 4
[ 882.930353] usb 1-1.3: new full-speed USB device number 6 using dwc_otg
[ 883.063706] usb 1-1.3: New USB device found, idVendor=0483, idProduct=5750, bcdDevice= 2.00
[ 883.063729] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 883.063745] usb 1-1.3: Product: ByQDtech 触控USB鼠标
[ 883.063760] usb 1-1.3: Manufacturer: 深圳市全动电子技术有限公司
[ 883.063774] usb 1-1.3: SerialNumber: DF77ECDCAE8C
[ 883.069573] input: 深圳市全动电子技术有限公司 ByQDtech 触控USB鼠标 as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3/1-1.3:1.0/0003:0483t/input3
[ 883.070263] hid-multitouch 0003:0483:5750.0002: input,hidraw0: USB HID v1.10 Device [深圳市全动电子技术有限公司 ByQDtech 触控USB鼠标] on us1.3/input0
[ 916.174662] usb 1-1.3: USB disconnect, device number 6
[ 919.290444] usb 1-1.3: new full-speed USB device number 7 using dwc_otg
[ 919.423834] usb 1-1.3: New USB device found, idVendor=0483, idProduct=5750, bcdDevice= 2.00
[ 919.423858] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 919.423874] usb 1-1.3: Product: ByQDtech 触控USB鼠标
[ 919.423889] usb 1-1.3: Manufacturer: 深圳市全动电子技术有限公司
[ 919.423903] usb 1-1.3: SerialNumber: DF77ECDCAE8C
[ 919.429406] input: 深圳市全动电子技术有限公司 ByQDtech 触控USB鼠标 as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3/1-1.3:1.0/0003:0483t/input4
[ 919.430042] hid-multitouch 0003:0483:5750.0003: input,hidraw0: USB HID v1.10 Device [深圳市全动电子技术有限公司 ByQDtech 触控USB鼠标] on us1.3/input0
[ 1520.338635] usb 1-1.3: USB disconnect, device number 7
[ 1523.964105] usb 1-1.3: new full-speed USB device number 8 using dwc_otg
[ 1524.097450] usb 1-1.3: New USB device found, idVendor=0483, idProduct=5750, bcdDevice= 2.00
[ 1524.097473] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1524.097486] usb 1-1.3: Product: ByQDtech 触控USB鼠标
[ 1524.097499] usb 1-1.3: Manufacturer: 深圳市全动电子技术有限公司
[ 1524.097512] usb 1-1.3: SerialNumber: DF77ECDCAE8C
[ 1524.103108] input: 深圳市全动电子技术有限公司 ByQDtech 触控USB鼠标 as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3/1-1.3:1.0/0003:0483t/input5
[ 1524.103693] hid-multitouch 0003:0483:5750.0004: input,hidraw0: USB HID v1.10 Device [深圳市全动电子技术有限公司 ByQDtech 触控USB鼠标] on us1.3/input0
Not only is some of the text Japanese, to me it is all Chinese
But it seems that a QDtech chip is used, however there does also seem to be a ADS7846 reaction.
What puzzles me is that on Raspberry Buster the touch function is working without any additional action, so it would look like the standard driver is operational?
Hoping maybe this listing helps us forward.
Peter.
Thank you again for your support!
I have changed the display setting to 1024 x 600 as per your suggestion.
Also verified the calibtation device setting and the rules. They were both correct.
Tried to run the calibration program (after stopping the peppy service) and, besides the resolution change which gave smaller characters (obviously), thre is no change. Crosshair is on the screen, but clicking it does not seem to work and th eprogram is halted untill I enter a Ctl C.
I did a dmsg to see what can be found related to touch or ADS7846. Found a couple of entries. Maybe this helps??
[ 7.665244] input: 深圳市全动电子技术有限公司 ByQDtech 触控USB鼠标 as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3/1-1.3:1.0/0003:0483t/input1
[ 7.665983] hid-multitouch 0003:0483:5750.0001: input,hidraw0: USB HID v1.10 Device [深圳市全动电子技术有限公司 ByQDtech 触控USB鼠标] on us1.3/input0
[ 7.694130] brcmfmac: F1 signature read @0x18000000=0x15264345
[ 7.725243] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
[ 7.727205] usbcore: registered new interface driver brcmfmac
[ 8.053612] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
[ 8.053806] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
[ 8.077362] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Jan 4 2021 19:56:29 version 7.45.229 (617f1f5 CY) FWID 01-2dbd9d2e
[ 8.602797] ads7846 spi0.1: supply vcc not found, using dummy regulator
[ 8.603701] ads7846 spi0.1: touchscreen, irq 200
[ 8.612199] input: ADS7846 Touchscreen as /devices/platform/soc/3f204000.spi/spi_master/spi0/spi0.1/input/input2
[ 8.994727] random: crng init done
and towards the end:
[ 879.050820] usb 1-1.3: USB disconnect, device number 4
[ 882.930353] usb 1-1.3: new full-speed USB device number 6 using dwc_otg
[ 883.063706] usb 1-1.3: New USB device found, idVendor=0483, idProduct=5750, bcdDevice= 2.00
[ 883.063729] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 883.063745] usb 1-1.3: Product: ByQDtech 触控USB鼠标
[ 883.063760] usb 1-1.3: Manufacturer: 深圳市全动电子技术有限公司
[ 883.063774] usb 1-1.3: SerialNumber: DF77ECDCAE8C
[ 883.069573] input: 深圳市全动电子技术有限公司 ByQDtech 触控USB鼠标 as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3/1-1.3:1.0/0003:0483t/input3
[ 883.070263] hid-multitouch 0003:0483:5750.0002: input,hidraw0: USB HID v1.10 Device [深圳市全动电子技术有限公司 ByQDtech 触控USB鼠标] on us1.3/input0
[ 916.174662] usb 1-1.3: USB disconnect, device number 6
[ 919.290444] usb 1-1.3: new full-speed USB device number 7 using dwc_otg
[ 919.423834] usb 1-1.3: New USB device found, idVendor=0483, idProduct=5750, bcdDevice= 2.00
[ 919.423858] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 919.423874] usb 1-1.3: Product: ByQDtech 触控USB鼠标
[ 919.423889] usb 1-1.3: Manufacturer: 深圳市全动电子技术有限公司
[ 919.423903] usb 1-1.3: SerialNumber: DF77ECDCAE8C
[ 919.429406] input: 深圳市全动电子技术有限公司 ByQDtech 触控USB鼠标 as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3/1-1.3:1.0/0003:0483t/input4
[ 919.430042] hid-multitouch 0003:0483:5750.0003: input,hidraw0: USB HID v1.10 Device [深圳市全动电子技术有限公司 ByQDtech 触控USB鼠标] on us1.3/input0
[ 1520.338635] usb 1-1.3: USB disconnect, device number 7
[ 1523.964105] usb 1-1.3: new full-speed USB device number 8 using dwc_otg
[ 1524.097450] usb 1-1.3: New USB device found, idVendor=0483, idProduct=5750, bcdDevice= 2.00
[ 1524.097473] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1524.097486] usb 1-1.3: Product: ByQDtech 触控USB鼠标
[ 1524.097499] usb 1-1.3: Manufacturer: 深圳市全动电子技术有限公司
[ 1524.097512] usb 1-1.3: SerialNumber: DF77ECDCAE8C
[ 1524.103108] input: 深圳市全动电子技术有限公司 ByQDtech 触控USB鼠标 as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3/1-1.3:1.0/0003:0483t/input5
[ 1524.103693] hid-multitouch 0003:0483:5750.0004: input,hidraw0: USB HID v1.10 Device [深圳市全动电子技术有限公司 ByQDtech 触控USB鼠标] on us1.3/input0
Not only is some of the text Japanese, to me it is all Chinese
But it seems that a QDtech chip is used, however there does also seem to be a ADS7846 reaction.
What puzzles me is that on Raspberry Buster the touch function is working without any additional action, so it would look like the standard driver is operational?
Hoping maybe this listing helps us forward.
Peter.
I believe the touchscreen works with Desktop OS when you see the windows on your desktop, right? The PeppyPlayer uses so-called Lite OS (without desktop) as it doesn't need the desktop environment. That's why it's more difficult to configure touchscreens for such environments.
It's also possible that the previous display driver installed on this disk image for 5" display could install something which affects your display. Please check this thread and see if you can define your ByQDtech chipset in the rules file:
https://forums.raspberrypi.com/viewtopic.php?t=139983&start=275#p1906372
Best regards
It's also possible that the previous display driver installed on this disk image for 5" display could install something which affects your display. Please check this thread and see if you can define your ByQDtech chipset in the rules file:
https://forums.raspberrypi.com/viewtopic.php?t=139983&start=275#p1906372
Best regards
Last edited: