I’m looking to start a new discussion about the TFT screens Ryan is looking at selling. There’s a thread here where he’s talking about it a little.
There are a couple of great mods for the TFT screens already, and although they aren’t exactly the same versions, there seems to be a lot that can be transferred. So I’m really interested in talking about lessons learned from those developers and thoughts on how we can keep this maintainable.
It looks like @blomsd had a good starting point here:
I’ve looked at this a little. It looks like it works great, and it has pulled in the main repo as of Vx.x.25.
It looks like @loki edited that version. Loki’s version is here:
It looks like it incorporated a lot of blomsd’s changes, but it is built on BTT’s Vx.x.26, and it is convenitently in a fork, so it seems easier to update.
But in either case, there are some very destructive changes (naturally). Are there any ideas on how to make updates from BTT’s firmware come in more smoothly?
Ryan has started a repo with a fork of the BTT firmware. He’s started mostly from BTT to keep it up to date, and has focused on just getting rid of the errors. I want to work in this space, with the great fixes that have already been developed.
I’m seeing that @ronnycowart is editing some things as well. I didn’t find any details about what edits are going on though.
What features are working? What features aren’t?
I personally think the G92 stuff is the best.
I also like the gcode sender. Although the M105 prints were making reading responses super annoying. I am not sure what the cost of disabling that is, or if it would be better to just not print those in the gcode window. The laser and spindle stuff seems great, although I know not everyone will actually be able to use it. Blomsd’s code didn’t work with the knob for me (The version Ryan is selling has a knob). I haven’t tried Loki’s yet (I will today).
I’d love to see an M119 screen, showing the states of the endstops. That’s the first thing I did in the gcode screen.
I’d love to see the M115/M503 stuff. If nothing else, to tell us the version from Ryan’s firmware (425D, etc.).
I’d like to see baby stepping, although that can be a pain. I use on my printers with mesh leveling, but I wonder if it could also be used on a normal CNC to adjust the Z a little after a job has started. I’m not interested in the M851 interaction ATM, just a general Z offset on the fly.
The coolest feature would be Steve’s touch to jog screen that shows you the whole bed area, and then lets you jog to a particular part of it just by touching that part of the screen. I have no idea how hard it is to code something like that in these screens, but we’ve all got enough talent to figure something like that out.
What about interfacing with grbl?