@justus2342 first check that the problem isn't caused by the face of the display being screwed too tightly to the enclosure.

It's possible to replace the touch membrane. If you use the Search facility in this forum to search for "membrane" then you may find some suggestions.

On the SBC side of the house. I had an idea to write a X Window app that is basically the PD layout. People may argue why not just run DWC? But in my mind this app would basically be the PD and screen for the SBC at the same time. and not connect via network but direct to OS&DSF. Basically klipper screen concept for RRF+SBC makes obtaining a touchscreen for your RRF printer really easy hardware wise.

I think this a great idea but lack the skill to actually make it haha. I'm useless that way 🙂

@phaedrux Will do thank you

according to @fbunel the issue was solved.

Moved to the developers forum.

Moved to developer's forum.

@knutselsmurf there is no easy fix, because you need two separate UARTs to drive the PanelDue and the Neopixel board, and the only user-accessible UART on Duet WiFi is the one connected to the PanelDue port.

Hey @redrout,

closing this thread due to inactivity. Please re-open if your issue persists with newer version of paneldue.

@erfreuterstudent
that's a premier for me too, but we'll try.
With a toolchanger you could poll the diameter of the current tool in tpost#.g by using M118 S2 P"toolnumber"
Now the arduino reads this message and sends the aquired data, but here it get's shady for me. It is easy to receive messages and display them on DWC, but reading data into a global variable is unknown to me. I tried it over I2Cport, but fell into the same dark hole...
Maybe @dc42 has a solution now?

Figured it out. Needed to add M575 to config.g. All good now:

@krohm-koala - Thank you for your reply. I was just trying to point out that you should value your own time, even a day developing your own and you are basically valuing your time at very little per hour after material costs. Thats why we made them available for others. Take care.

That message is coming from a user macro and not the firmware. What did you push before you got that message?

Hardware seems functional. For further help you'll have to provide some config files. config.g, homeall.g, homex homey homez bed.g and results of M98 P"config.g".

@Phaedrux said in 7" touch display connect with duet 3d board:

https://duet3d.dozuki.com/Wiki/Getting_Started_With_Duet_3

Have you actually gone through any of the documentation?

Well, I took the plunge and updated to firmware 3.1.1

A few things were a royal pain, things that I'd tuned that needed finding and re-entering. Like extruder steps that were entirely wrong. There didn't seem to be a spot in the configurator for using 2 motor drives for the Z axis, Pressure advance needed tuning, and it scared the crap outta me when it said that the heat bed was faulting. (PID tuning needed to happen again.) All that stuff I figured out 2 years ago and have since forgotten.

So far, so good.

I just picked up a few of these fysetc panels (LCD800480 V1.1). The important thing to look at is that yes its more like a paneldue 7i in form factor, but the back of the pcb says it is based on the paneldue v3 not the 7i. So once I flashed the board with PanelDue-v3-7.0.bin files everything was as expected now.

@DDD said in Custom Splash Screen:

that's the info on the board

as in silk screen or also the marking on the cpu? does bossa agree as well?

EDIT:
I have Firmware Version 1.17 on my PanelDue and will Upgrade to the latest. The macros are only supported from 1.20 in.

And yes, external tools works fine. Its only internal tools that don't.

Lowracer. I'm interested in converting my um2+ extended to DUET Wifi as well. Did you follow a tutorial or just figure it out yourself?

I'm scared to mess things up.

Thanks!