Replies: 2 comments 1 reply
-
Thanks for investigating on the Fuldho screen! This is interesting to see a smart screen working differently than the other models I've seen so far. I think it would be difficult to integrate this screen to the existing project because of the current code architecture: the https://github.com/mathoudebine/turing-smart-screen-python/blob/main/library/lcd/lcd_comm.py abstract class that is used as the base for all supported display drivers (Turing / Xuanfang..) has been written so that the display does not actually know any of the hardware sensors data. Instead it is only used to draw generic content on the display like text, progress bars or bitmaps. If the Fuldho screen needs to know which sensor the data comes from to display it properly, it would require to change the base architecture of this project. There may be a way to do it that I didn't think of! For now I will just add a link to your project https://github.com/braewoods/hidss in the Readme for other people to know |
Beta Was this translation helpful? Give feedback.
-
Technically it doesn't really care where it comes from. It just has some input data IDs set aside for certain purposes that it then updates the screen with if the currently loaded theme uses them at all. I think it may be possible to add new features the original software does not support in terms of theme generation. |
Beta Was this translation helpful? Give feedback.
-
I noticed this on the main README and decided to investigate the hardware. I've spent the last week or so reverse engineering it. I am not quite finished but I am getting close.
The hardware works off a completely different approach to other more common screens. It doesn't use the regular approach of implementing a custom protocol over data endpoints. Instead it pretends to be a USB HID and uses vendor specific reports.
It doesn't allow arbitrary drawing via BLIT type operations. The screen does all the drawing, using a "theme" that was previously uploaded by the theme editor. In normal operation, custom reports are used to update the system information on the screen.
I am currently working on understanding how the "theme" binary file is formatted, which is the last major thing left before alternative software can be written.
Given all this, is there any room for this device in this project? Given what I know of the project, chances are the best you could do is translate the existing themes from the current editor and add something to pass system data to the screen.
Beta Was this translation helpful? Give feedback.
All reactions