@phaedrux said in PanelDue 4pin connector vs CONN_SD for long distance connection?:

Feel free to try S4. I think having crc should be an improvement

To use S4 you will need to use the latest beta PanelDueFirmware.

The PanelDue firmware may also be too old to allow update from the duet. What version does it show in the settings page? You may need to update it once manually using bossa before you are able to update it directly from the Duet.

https://docs.duet3d.com/en/User_manual/RepRapFirmware/Updating_PanelDue

@resam that looks to me like a hardware issue with the display. However, you could try downgrading to the older firmware version to see if the issue continues.

@gallaghersart, I think I put a switch on the XPT2046 output. If possible, cut the trace close the the IC, before any pull-up resistor if any.

https://www.buydisplay.com/download/ic/XPT2046.pdf

(Of course I can't be responsible to any damage).

I'm the same... now. I've swapped the io0.in and io0.out with each other a few times over the past few days. Looks like this now:

my duet connection.JPG

And from the picture, I can confirm the PanelDue RXD (black wire in my photo, blue in yours) connects to the signal io0.In on the io0 connector.

paneldue.JPG

But I've solved it! I did two things and not sure if both were needed or only the second (I suspect only the second).

First - I had been using io_0 as an endstop and had it inverted. I thought maybe the inversion was lingering, so I sent an M950 to not invert the signal. I suspect this made no difference.

Second - RTFM I took a quick triple check of my M575 command against the documentation and noted that in my config.g (above), I have M575 P0 S1 B57600, and the documentation states clearly that it should be M575 P1 S1 B57600.

So a quick change a reboot and it's working! And so is the SDcard connected via the modified ribbon cable.

Thanks to @dc42 and @Phaedrux for your time and energy on this. I'll do penance by trying to help answer some other questions in the forum (I've made enough mistakes to learn a bit).

Mike

Ok, gotta scroll down duh.

@mfs12 it needs updating on the docs site too
Screenshot_20220321-090429.png

do you experience this problem with DWC as well?

@phaedrux just wanted to report back: new paneldue arrived, attached -> works perfectly. thx again

@createc3d glad you solved it.

I think this may be a hard limit of the older V1 boards. Since it is a PanelDue with a separate board, you may be able to buy a V3 board to swap with, which would allow the use of the 3.x Paneldue firmware.

Or perhaps you could create a dummy heater for the bed to take up the position.

@achrn

Sweet, that did the trick ❤

@t3p3tony I wired a usb c breakout board to the back of the jst header, just with the d+ d- pads

Preview images with QOI are now supported since pd-3.4.1-pre1.

https://github.com/Duet3D/PanelDueFirmware/issues/246

mfs12 created this issue in Duet3D/PanelDueFirmware closed Add support for QOI thumbnails in gcode files #246

@oozebot
Good idea.
About the only thing possible at present is to create a macro for each filament.
I have "centralised" my filament setup so that I only store filament specific settings in the respective/filaments/xxx/config.g and have a universal load/unload.
But to get buttons in PanelDue I'd have to do individual buttons each passing which filament to load.
A bit tedious if you have a lot of choices though.

Maybe a possible enhancement function for DWC would be dynamically created buttons where the parameters could be contained in a text file?

DisplayText, MacroCalled, ParameterPassed
Load ABS, M701, S"ABS"
Unload ABS,M702,S"ABS"
My Macro, M98 P"0/macros/mymacro.g", A"123" B"abc"

@phaedrux Thank you!

Did this start after updating the PanelDue to 3.4 pre4?

Do your wires run near other cables?

Can you please try updating to Duet firmware 3.4 RC1 and PanelDue 3.4.1 pre1?

https://github.com/Duet3D/RepRapFirmware/releases/tag/3.4.0rc1
https://github.com/Duet3D/PanelDueFirmware/releases/tag/3.4.1-pre1

Can you try reflashing the firmware? Does the touch calibration work afterwards?