Turing 8.8" New Hardware Revision!? not working

[ninharp]

Looks like there is an other hardware revision of the Turing Smart Screen 8.8".
After i connect mine it will offer me two usb devices but none of them providing any serial interface.
Either i do it completely wrong or there is for real a new hardware revision.

[ 2187.135120] usb 5-4.1.4.3: new full-speed USB device number 10 using xhci_hcd
[ 2187.254226] usb 5-4.1.4.3: New USB device found, idVendor=1cbe, idProduct=f00
0, bcdDevice= 0.01                                                              
[ 2187.254233] usb 5-4.1.4.3: New USB device strings: Mfr=1, Product=2, SerialNu
mber=3                                                                          
[ 2187.254236] usb 5-4.1.4.3: Product: USB-Daemon                               
[ 2187.254239] usb 5-4.1.4.3: Manufacturer: turzx.com                           
[ 2187.254241] usb 5-4.1.4.3: SerialNumber: 0123456789                          
[ 2188.145129] usb 5-4.1.4.1: new high-speed USB device number 11 using xhci_hcd
[ 2188.241838] usb 5-4.1.4.1: New USB device found, idVendor=1cbe, idProduct=008
8, bcdDevice= 0.00                                                              
[ 2188.241842] usb 5-4.1.4.1: New USB device strings: Mfr=1, Product=2, SerialNu
mber=3                                                                          
[ 2188.241844] usb 5-4.1.4.1: Product: TURZX1.0                                 
[ 2188.241846] usb 5-4.1.4.1: Manufacturer: TURZX                               
[ 2188.241848] usb 5-4.1.4.1: SerialNumber: 051xxxxxxxxxxxxxx

Describe the bug
No connection possible with this display due to lack of serial port

Environment:

• Smart screen model [Turing 8.8"]
• Revision of this project [main branch]
• OS with version [Linux Arch]
• Python version [Python 3.13]
• Hardware [AMD Ryzen 9 3900XT]

[jurjevic]

Same here :-(

[mathoudebine]

Hi @ninharp @jurjevic
It seems there is indeed a new generation of Turing 8.8" screens that do not communicate the same way as the previous gen.
For now the new generation is not supported with this program ☹
Can you share where you bought yours? I would also be interested by the original software provided for it.

[ninharp]

Hi @ninharp @jurjevic It seems there is indeed a new generation of Turing 8.8" screens that do not communicate the same way as the previous gen. For now the new generation is not supported with this program ☹ Can you share where you bought yours? I would also be interested by the original software provided for it.

I bought it on Aliexpress on the Elec Zone Store. Here is a link https://de.aliexpress.com/item/1005005538293555.html
The original software provided for the display is the same as for the other devices, it just detects the display as 8.8"

I will try to capture the usb frames when the display is enabled in windows. Maybe the software captured frames are enough to reverse engineer the usb data used to drive the display. I also will dissassemble the device soonish to see if there are any other connectors which could be used, maybe a dedicated uart port or something similar.

[phstudy]

I also purchased the same new version on March 28 from Taobao.

[jurjevic]

Same here - I've a 3,5" version running and it works fine. I just wanted a bigger display, but the 8,8" seems to work completely different :-(

[loonatic-lee]

I too have recently purchased an 8.8" version from eBay : https://www.ebay.co.uk/itm/365422061073

The internal driver board states that it's a version 1.1

[phstudy]

I just used Wireshark to dump the packets and had ChatGPT generate a sample code.
Tested it on my Ubuntu machine, and replaying the previously dumped packets successfully updates CPU, GPU, and other metrics on the display.

sample_python.zip

[phstudy]

Yesterday I tried analyzing the packets. It seems that part of the data is encrypted using DES, which makes it difficult to directly reuse the old data format.

[psychomuser]

Same problem here. I bought it on aliexpress on March 29 from electree store, the package is the same as in the picture, and it is not detected... Do you recommend to make the return? Or maybe support will be added in the future?

Thank you for your attention and the beautiful app

[phstudy]

I’ve written a sample CLI tool that supports several commands for the Turing Smart Screen - TURZX 88inch V1.1:

• sync
• restart
• refresh-storage
• brightness
• save

Example usage:

python turing_screen_cli.py sync
python turing_screen_cli.py restart
python turing_screen_cli.py refresh-storage
python turing_screen_cli.py brightness --value 80
python turing_screen_cli.py save --brightness 90 --startup 0 --rotation 0 --offline 0

You can check it out here:
🔗 https://gist.github.com/phstudy/e7dcca4ce1e39b38d25cce09419c856d

I’ll continue adding more features when I have time.

[phstudy]

I've added the send-image command, which allows sending 480x1920 PNG files to the device. I think this should be enough for the project to support the new revision.

Example usage:

python turing_screen_cli.py send-image --path ./102_25011_payload.png

[phstudy]

I also just got the send-video command working. Here's an example that plays a video in loop mode:

python turing_screen_cli.py send-video --path ./AMD.mp4 --loop

So far, it works well on the new screen version.

[phstudy]

I tried porting the current command implementation into the project. It's not fully polished yet, but it works properly on my Mac. Feel free to fork the branch and adjust it as needed.

Repo link:
 https://github.com/phstudy/turing-smart-screen-python/tree/feature/support-8.8-v1.1

[loonatic-lee]

I've added the send-image command, which allows sending 480x1920 PNG files to the device. I think this should be enough for the project to support the new revision.

Example usage:

python turing_screen_cli.py send-image --path ./102_25011_payload.png

Firstly, many thanks for the great work you've done in getting this far, really appreciated.

However, I am having a problem sending large PNG files, either from the CLI tool or via my own code which converts a PILLOW Image to a PNG file as implemented in your latest update. Small size files work fine. Its as if the data needs to be chunked and sent in parts.

Have you experienced this? Have you tried sending a large PNG file to the display?

Many thanks, Lee