-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FR] Full Klipper Support #1555
Comments
Please see #290 and also the pinned FR ticket. |
Yes, I did read the pinned ticket, which links to #290 as I also did in my FR. |
The basic support did not happen in more than one year. Hmmmm. Lets see. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Hey, not sure if you're aware of Desuuuu's Klipper fork that allows a type of dwin TFT serial display to work with Klipper directly through mainboard, well now he's cooking something else 😄. He's working on a sort of serial pass-through implementation that will allow dynamically control of TFTs or basically any MCU directly from the klippy host through the mainboard's secondary serial interface. He said that this will work in a similar way Klipper already works with I²C and SPI. If anyone's interested in adding touchscreen support for Klipper, check his work on the runtime-uart branch. Maybe someone could use that to finally port the btt touchscreen firmware in Klipper |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Is your feature request related to a problem? Please describe.
TFT Screen will not work with Klipper out of the box, simulated can be fixed.
Describe the solution you'd like
To implement serial pass-through or serial listener, so Klipper remains in control but can take commands.
In short, make a proper emulator and make the touchscreen work with Klipper.
Describe alternatives you've considered
Even a generic mode would be ok, so more than Klipper can utilize the screens.
An intermediary config file for translating commands, i.e screen wants G29, but when pressed will send "BED_MESH_CALIBRATE" instead, so config file could be G29=BED_MESH_CALIBRATE instead of standard G29=G29.
Additional context
There has been discussions about getting the emulator to work an @teeminus has gotten it to work decently here https://github.com/teeminus/BIGTREETECH-TouchScreenFirmware
Also there is/was progress being made here #290
Then we have one line that i was curious about here -> https://github.com/bigtreetech/BIGTREETECH-TouchScreenFirmware/search?q=klipper+repo%3Abigtreetech%2FBIGTREETECH-TouchScreenFirmware
So there might have been a tought of adding support for Klipper?
Might add that Klipper is growing and is just such a perfect firmware, i do not ever believe that it will be less used. Definitively in the custom printer market.
I bought one of these tft screens well knowing it might not work flawlessly OOTB.
But surely you could make the GUI be able to pass commands.
Big shoutout for @teeminus for making the LCD usable for me!
The text was updated successfully, but these errors were encountered: