Re-calibrate the paneldue touch screen
-
During the Paneldue update process to 3.4.0 from 1.24, accidentally the touch screen calibration went a bit wrong, and was completely mis-calibrated. It seems impossible to enter the setup tab to re-calibrate it.
Re-flashing the firmware using M997 S4 does not prompt the calibration steps again. The notes in the paneldue firmware update process state that:
On version 2.0 and earlier boards, whenever new firmware is uploaded, the touch panel calibration and touch pad orientation is lost. Therefore, on starting up the software enters the touch panel calibration phase. Touch the spots as instructed on the screen as accurately as possible. It is more accurate to use the tip of your fingernail or a stylus (print one!) rather than the pad of your finger. If the display is upside down or inverted left-right, you can correct it after touch calibration using the options provided on the Setup page.
would it be required to first downgrade to a 1.x version of the paneldue before updating again to 3.4.1? Or is there a different way of erasing the calibration process to not need to go through this process.
-
reflashing may be the only way to force a touch recalibration.
From DC42: flash the wrong firmware (same PD version but different screen size), let it power up with that firmware. Then install the correct firmware.
-
@phaedrux Sadly this did not seem to work. The unit is a Paneldue 7i, and tried flashing the 3.4.1 5i and the 3.4.1 v2 4.3 variants, but neither triggered the re-calibration prompt. Will try downgrading to 1.24 then back to 3.4.1 later
-
@comediantf2 the 3.4.1 5i version is exactly the same as the 3.4.1 7i. Try the 3.4.1 v3 7" non integrated build.
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
@dc42 Sadly this did not trigger the calibration prompt
Downgrading to 1.24 and then back to 3.4.1 did the trick, it erased the calibration data going back to 1.24 and triggered the prompt going both to 1.24 and then again when going to 3.4.1.
-
@comediantf2 I'm glad you got it working.
-
undefined dc42 marked this topic as a question
-
undefined dc42 has marked this topic as solved
