@mfs12 Moved relevant files to VSCode toolkit directory solved the issue.

@Makergal3D I think the ribbon cable was not properly attach to the panel due 🤦

You can close it

Sorry

@jay_s_uk ok

@droftarts Aside from M575 P1 B57600 S1? Any writeup on how to change the pin on the Duet?

@Phaedrux okay I'll check that tmw

@Phaedrux M115 says that the firmware is 3.2.2, and the hardware is a Duet 2 Wifi and PanelDue 7i.

(Commenting out the M552 has got me underway. Thank you.)

@chrishamm Thank you. Sorry to ask, what will be the timeline for this?

Actually we have installed a printer to an institute and they dont prefer Wifi. So we are using Panel due.

@Phaedrux Board -

Duet 3 MB 6HC V1.02 with RPI 3B.
DSF Version: 3.4.5
Firmware: RepRapFirmware for Duet 3 MB6HC 3.4.5 (2022-11-30)
Duet Web Control 3.4.5

Panel Due 5i - Firmware - 3.4.x

I needed the fan control in the front screen. Is it possible?

Also, if I connect the Pen drive (USB drive) to SBC, how to show in Panel due (It is showing in DWC).

When i clicked the Print icon, it is showing the Sd card option only. It is showing two partitions - one is gcodes and other is firmware files folder

@Exerqtor I bought the clone paneldue in 2019. Never got it working then, but had not tried that hard either. I did flash the v3 7in firmware this morning by mistake and the colors were all messed up on the display.

@jay_s_uk

Unfortunately the buttons aren't accessible without removing the screen. Not the end of the world, but just wanted to see if there was something I was doing wrong.

@CNCModeller Did you get this working ?

I had my Diabase version connected to my Tiny-M at MRRF and people really liked it.

@sinned6915

@sinned6915 said in PanelDue ATX power supply on off toggle?:

i have an optocoupled relay triggerd by PS_ON pin on the Duet2 board and always on 5V power supply.

Same here.

I see how you have configured the pin state for enabling the PSU, now I am wondering how to combine the two functions- the screen macro and physical button.

I'm not sure to understand: a button press triggers the dialog which then requests a confirmation. What do you want to combine more than that?

@oliof said in Panel no work!:

뽑았다가 다시 꽂아 보십시오.
직렬 USB를 통해 연결하여 PuTTY를 사용하여 보드와 직접 통신

Where is the serial USB to connect PuTTY?
I'm using a duet2 Wi-Fi product, but I can't see the USB port on the board.
Also, if you run M122, it shows as below, so please check it.

7db0bf8d-500e-4f41-a5f0-b4616541fe57-image.png

@r3cvr i've asked @droftarts to update the docs

I think I found a way that works without knowing the font widths 🙂

[for sake of easy readability, I removed the initialisation: - heat up bed and hotends - let the user clean the nozzles - remove the print plate - move the bed to measurement position] ; move to reference screw in centre back G1 H2 X0 Y86 ; move M400 ; wait for the motion to finish var ZReference = 0 ; 1. measure and correct z value while iterations <=6 G4 P200 ; wait 0,2s G30 S-1 K0 ; measure z set var.ZReference = var.ZReference + sensors.probes[0].lastStopHeight G1 H2 Z5 F3000 ; move back up set var.ZReference = var.ZReference / 6 ; move hotend to probe point at front left G1 X-115 Y94 F3000 ; move M400 ; wait for the motion to finish ; measure error and let the user correct it ; start loop var Measurement1 = false var loopcount = 0 ; message timeout *must* be adapted to probing speed as good as possible. To avoid message buffer ; overflows, message (und thus measuring) interval should be significantly slower than 1s to let the ; Duet catch up if needed. while var.Measurement1 = false set var.loopcount = 0 G4 P200 ; wait 0.2s G30 S-1 K0 ; measure Z ; A "case" command, a kingdom for a "case" command... but we only have "if"... if sensors.probes[0].lastStopHeight > 0.5 M291 S1 T1.4 P"=>|<==========-..-==========" R"turn left bed screw" elif sensors.probes[0].lastStopHeight <= 0.5 && sensors.probes[0].lastStopHeight > 0.45 M291 S1 T1.4 P"=>|<=========-..-==========" R"turn left bed screw" elif sensors.probes[0].lastStopHeight <= 0.45 && sensors.probes[0].lastStopHeight > 0.4 M291 S1 T1.4 P"==>|<========-..-==========" R"turn left bed screw" elif sensors.probes[0].lastStopHeight <= 0.4 && sensors.probes[0].lastStopHeight > 0.35 M291 S1 T1.4 P"===>|<=======-..-==========" R"turn left bed screw" elif sensors.probes[0].lastStopHeight <= 0.35 && sensors.probes[0].lastStopHeight > 0.3 M291 S1 T1.4 P"====>|<======-..-==========" R"turn left bed screw" elif sensors.probes[0].lastStopHeight <= 0.3 && sensors.probes[0].lastStopHeight > 0.25 M291 S1 T1.4 P"=====>|<=====-..-==========" R"turn left bed screw" elif sensors.probes[0].lastStopHeight <= 0.25 && sensors.probes[0].lastStopHeight > 0.2 M291 S1 T1.4 P"======>|<====-..-==========" R"turn left bed screw" elif sensors.probes[0].lastStopHeight <= 0.2 && sensors.probes[0].lastStopHeight > 0.15 M291 S1 T1.4 P"=======>|<===-..-==========" R"turn left bed screw" elif sensors.probes[0].lastStopHeight <= 0.15 && sensors.probes[0].lastStopHeight > 0.1 M291 S1 T1.4 P"========>|<==-..-==========" R"turn left bed screw" elif sensors.probes[0].lastStopHeight <= 0.1 && sensors.probes[0].lastStopHeight > 0.05 M291 S1 T1.4 P"=========>|<=-..-==========" R"turn left bed screw" elif sensors.probes[0].lastStopHeight <= 0.05 && sensors.probes[0].lastStopHeight > 0.03 M291 S1 T1.4 P"==========>|<-..-==========" R"turn left bed screw" ; There is no non-blocking and time-out-able message the user can acknowledge ; Workaround: verify measurement several times, then display a blocking message elif sensors.probes[0].lastStopHeight <= 0.03 && sensors.probes[0].lastStopHeight >= -0.03 while sensors.probes[0].lastStopHeight <= 0.03 && sensors.probes[0].lastStopHeight >= -0.03 && var.loopcount <= 10 ; okay, but verify some times... if iterations > 0 ; not for the first loop G4 P200 ; wait 0.2s G30 S-1 K0 ; measure z G1 H2 Z5 F3000 ; move back up if sensors.probes[0].lastStopHeight <= 0.03 && sensors.probes[0].lastStopHeight > 0.01 ; just okay M291 S1 T1.4 P"==========->|<..-==========" R"turn left bed screw" set var.loopcount = var.loopcount + 1 elif sensors.probes[0].lastStopHeight <= 0.01 && sensors.probes[0].lastStopHeight >= -0.01 ; perfect M291 S1 T1.4 P"==========-.>|<.-==========" R"turn left bed screw" set var.loopcount = var.loopcount + 1 elif sensors.probes[0].lastStopHeight < -0.01 && sensors.probes[0].lastStopHeight >= -0.03 ; just okay M291 S1 T1.4 P"==========-..>|<-==========" R"turn left bed screw" set var.loopcount = var.loopcount + 1 if var.loopcount = 10 && sensors.probes[0].lastStopHeight <= 0.03 && sensors.probes[0].lastStopHeight >= -0.03 M300 S2000 P200 ; B G4 P200 ; e M300 S2500 P300 ; e G4 P300 ; p M291 S4 K{"OK","Repeat"} T1 P"Bed screw adjusted! End measurement?" R"Left bed screw adjusted" if input = 0 set var.Messung1 = true set var.loopcount = 99 if input = 1 set var.loopcount = 0 elif sensors.probes[0].lastStopHeight < -0.03 && sensors.probes[0].lastStopHeight >= -0.05 M291 S1 T1.4 P"==========-..->|<==========" R"turn left bed screw" elif sensors.probes[0].lastStopHeight < -0.05 && sensors.probes[0].lastStopHeight >= -0.1 M291 S1 T1.4 P"==========-..-=>|<=========" R"turn left bed screw" elif sensors.probes[0].lastStopHeight < -0.1 && sensors.probes[0].lastStopHeight >= -0.15 M291 S1 T1.4 P"==========-..-==>|<========" R"turn left bed screw" elif sensors.probes[0].lastStopHeight < -0.15 && sensors.probes[0].lastStopHeight >= -0.2 M291 S1 T1.4 P"==========-..-===>|<=======" R"turn left bed screw" elif sensors.probes[0].lastStopHeight < -0.2 && sensors.probes[0].lastStopHeight >= -0.25 M291 S1 T1.4 P"==========-..-====>|<======" R"turn left bed screw" elif sensors.probes[0].lastStopHeight < -0.25 && sensors.probes[0].lastStopHeight >= -0.3 M291 S1 T1.4 P"==========-..-=====>|<=====" R"turn left bed screw" elif sensors.probes[0].lastStopHeight < -0.3 && sensors.probes[0].lastStopHeight >= -0.35 M291 S1 T1.4 P"==========-..-======>|<====" R"turn left bed screw" elif sensors.probes[0].lastStopHeight < -0.35 && sensors.probes[0].lastStopHeight >= -0.4 M291 S1 T1.4 P"==========-..-=======>|<===" R"turn left bed screw" elif sensors.probes[0].lastStopHeight < -0.4 && sensors.probes[0].lastStopHeight >= -0.45 M291 S1 T1.4 P"==========-..-========>|<==" R"turn left bed screw" elif sensors.probes[0].lastStopHeight < -0.45 && sensors.probes[0].lastStopHeight >= -0.5 M291 S1 T1.4 P"==========-..-=========>|<=" R"turn left bed screw" elif sensors.probes[0].lastStopHeight < -0.5 M291 S1 T1.4 P"==========-..-==========>|<" R"turn left bed screw" [the same will be repeated then with the third probe point. Finally, save the updated z value and bring the printer back to a safe position]

Edit: fixed a generous amount of stupid typos, changed message type to S1 since the PanelDue does not seem to display S0 messages at all. Anything below "start loop" works now if I feed it with dummy data - for the rest I need the Duet built into the printer 🙂
2nd edit: updated to reflect how the script actually runs now, in case someone stumbles upon this and wants to use it.

@mikeabuilder I have updated the documentation and we have adjusted the behaviour to match it in RRF 3.5.0-beta.4. The general rule is:

For a blocking message, timing out is equivalent to the user pressing the Cancel button Therefore, a blocking message can only have a timeout if it also has a Cancel button.

@pdsm it's the reading from the Z probe. For most types of probe the value is 1000 when triggered and 0 when not triggered.

@mfs12

Flashed RC6, tested - seems to have been solved. Thank You! 🙂