Can I ask about an XPT2046 Touch Controller here?
-
Just thought I'd check before I ask.
Mac
-
@mac you can can’t connect that directly to the Duet, but it looks like it can connect to a Raspberry Pi. You could run your Duet in SBC mode, where it is directly connected to the Raspberry Pi, and the screen can then show DWC. See https://docs.duet3d.com/User_manual/Machine_configuration/SBC_setup
Ian
-
@droftarts thanks for the up-vote?
I have a pi 3 B+, so I will look into that.
I already tried the 4-wire method presented in Duet's documentation. It' not working so far.
I tried to send you a link but it didn't work.
-
@mac I just meant, yes, feel free to ask!
The controller on the display has to be able to ‘talk’ RepRapFirmware if you want to connect it directly to the Duet, which is limited to the PanelDue, 12864 displays (uses a different means of communication though), and some BigTreeTech displays, afaik.
Ian
-
@droftarts I had that 12864 attached, and I put those two lines of gcode into my config file, and the 3 LEDs did their thing, but the screen never appeared.
Anyways, thanks for the Pi-link, I'll get there, but I have to get my printer running first.
Do you have your interface setup to refuse video links?
Mac / Mark / Corlissmedia (2.0)
-
you can also just run the display on a raspberry pi and connect to the printer via the network if all you need is DWC. It's pretty cramped though, DWC doesn't work well below 7" screens (and the changes in 3.4 need more refinement for that).
@droftarts the BTT touch display support for RRF is recklessly getting broken by people doing changes for Marlin, and the person that kept fixing it has given up. Best bet is PanelDue or an 12864, or the RepPanel. I'm looking forward to the new screens that 3.5 is getting support for ...
-
@oliof as I told Ian, I had the fysetec 12864 installed, and I had those two lines of code in the config file, but the screen never did anything but show me it's pretty LED's.
-
The FYSETC works on a bunch of machines, so it's either a wiring issue or a faulty display unit.
-
@oliof I think it's an operator / config.g writer error.
I mean: wiring wise, what's there to screw up? The box I printed had 1 and 2 next to the holes where the cables go. The cables are keyed, as are the receptors on the board. I don't think I screwed that up (but it's possible).
The problem is me. I've just never done any coding. Duet's documentation is good, but it seems to ignore the amount of coding must do to make the board AND the printer actually do anything.
I say that not with malice, but out of my frustration. And my high blood pressure, which is killing me today.
Mark