mathoudebine / mathoudebine/turing-smart-screen-python
Unsupported display ID / device not recognized (USB Serial COM3, CherryUSB CDC DEMO, 462x1920, VID_33C3 PID_7788)
Open
Nobody has claimed this yet.
enhancement
New model support
- Dominant language
- Rich Text Format
- Stars
- 2.3k
- Forks
- 412
- Avg merge
- 21h 10m
- Merged PRs (30d)
- 7
Description
Hi! I'm trying to use turing-smart-screen-python with a case built-in display (Pichau Ikaros).
Display connection:
- Not HDMI/monitor mode. It is USB-only and shows up as USB Serial Device (COM3).
- AIDA64 identifies it as: "USB Composite Device (CherryUSB CDC DEMO)" and "USB Serial Device (COM3)".
- Hardware IDs: USB\VID_33C3&PID_7788&REV_0100 (and/or USB\VID_33C3&PID_7788)
Panel resolution (from the vendor software / HT_MONITOR):
- 462 x 1920 (portrait)
What works:
- Official vendor app (HT_MONITOR / HT_software) can drive the screen and show CPU/RAM/etc.
What does not work:
- turing-smart-screen-python debug build connects to COM3 but loops with:
"Display returned invalid or unsupported ID"
"Display returned invalid or unsupported ID length"
Environment:
- Windows 11
- COM port: COM3
- Intel Arc GPU (temps are fine in Windows Task Manager and other tools; unrelated to the screen detection)
Request:
- Is this device supported / can support be added?
- If you need logs, please tell me which debug output / command-line flags to enable to print the raw display ID bytes.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The report names no repository files or tests. Start with the debug build's COM3 connection and capture the raw display ID bytes requested in the issue, then compare them with the device-identification behavior used by the project. Done means the device has a documented support decision based on reproducible logs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- embedded-iot
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100