@Phaedrux thanks for the reply. When I remove the screen from the case, the issue disappears. My theory is, when it’s in the case, the board twists and causes the digitizer to come off the screen. It was definitely the digitizer as I can tell now that it’s out of the case that the digitizer floats on the screen and is only attached at the edges. I ordered it from Printed Solid on 9/13/2022. I will drill out the mounting holes on the case to prevent it from twisting the board.

Cancel this one, I was on Buster and not Bookworm. I followed this:
https://docs.duet3d.com/en/How_to_guides/SBC_Buster_to_Bookworm

And now it is working fine on 3.5.2.

Thanks,
Ed

@jay_s_uk Thank you! I tried B4092 but it is still off by exactly 20 degrees Celsius after re-tuning. I think I just need to contact the manufacturer of the bed and ask them which thermistor they used.

@dougal1957 That was exactly the issue. I looked at the top of the lead screw and it has a 4 start. I changed Z steps per mm to 800 and now it is perfect.

Ignore this one please. I can't delete it. I rephrased the posted a better question here:
https://forum.duet3d.com/post/230220

Cancel this one, I was on Buster and not Bookworm. I followed this:
https://docs.duet3d.com/en/How_to_guides/SBC_Buster_to_Bookworm

And now it is working fine on 3.5.2.

Thanks,
Ed

Hi all,
I am trying to upgrade my 6HC with a raspberry pi from 3.5.0-rc.2 to 3.5.2 by using apt-get commands and I am getting the following:

Get:1 https://pkg.duet3d.com unstable/armv7 armhf duetwebcontrol all 3.5.2 [9,515 kB]
Err:1 https://pkg.duet3d.com unstable/armv7 armhf duetwebcontrol all 3.5.2
  File has unexpected size (9518150 != 9514722). Mirror sync in progress? [IP: 134.209.94.168 443]
  Hashes of expected file:
   - SHA512:561698d07f2189530af8cb63e0509bb56e9b7af6b3b7c7cce095683e6721c03cca576cae7978d1372b5fd816c53c85cc906a62b7daa28bf75fe3087143af7d36
   - SHA256:d4e53e0771abd0b5b9d6cebb9de680949c6c583a9513893da4ba3e5083586bb3
   - SHA1:f86bda7304a1779cfadb13639e120bc748f22af2 [weak]
   - MD5Sum:4e835f776bc5ec021d88b8c8e691e214 [weak]
   - Filesize:9514722 [weak]
E: Failed to fetch https://pkg.duet3d.com/dists/unstable/armv7/binary-armhf/duetwebcontrol_3.5.2_all.deb  File has unexpected size (9518150 != 9514722). Mirror sync in progress? [IP: 134.209.94.168 443]
   Hashes of expected file:
    - SHA512:561698d07f2189530af8cb63e0509bb56e9b7af6b3b7c7cce095683e6721c03cca576cae7978d1372b5fd816c53c85cc906a62b7daa28bf75fe3087143af7d36
    - SHA256:d4e53e0771abd0b5b9d6cebb9de680949c6c583a9513893da4ba3e5083586bb3
    - SHA1:f86bda7304a1779cfadb13639e120bc748f22af2 [weak]
    - MD5Sum:4e835f776bc5ec021d88b8c8e691e214 [weak]
    - Filesize:9514722 [weak]
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?

Any idea on this one?

Thanks,
Ed

@Phaedrux just reporting back that it was definitely the issue. Once I drilled the holes out in the case and re-mounted the PanelDue, the issue was fixed. Thanks!

@Phaedrux thanks for the reply. When I remove the screen from the case, the issue disappears. My theory is, when it’s in the case, the board twists and causes the digitizer to come off the screen. It was definitely the digitizer as I can tell now that it’s out of the case that the digitizer floats on the screen and is only attached at the edges. I ordered it from Printed Solid on 9/13/2022. I will drill out the mounting holes on the case to prevent it from twisting the board.

I just installed a PanelDue on my 6HC and it’s awesome, but it appears to have a wavy film that doesn’t appear to be fully adhered to something below it. I already removed one screen protector before installing it. Is this another screen protector I needed to remove or is it the digitizer, etc.

@arnold_r_clark
That was it exactly, thank you!

12/19/2021, 2:29:38 PM	G32
Leadscrew adjustments made: 0.001 0.005, points used 2, (mean, deviation) before (0.003, 0.001) after (0.000, 0.000)
12/19/2021, 2:29:02 PM	G32
Leadscrew adjustments made: 0.008 -0.005, points used 2, (mean, deviation) before (0.002, 0.004) after (-0.000, 0.000)
12/19/2021, 2:28:28 PM	G32
Leadscrew adjustments made: 0.015 -0.016, points used 2, (mean, deviation) before (0.001, 0.011) after (-0.000, 0.000)
12/19/2021, 2:27:56 PM	G32
Leadscrew adjustments made: -0.023 -0.281, points used 2, (mean, deviation) before (-0.140, 0.089) after (0.000, 0.000)

Hello,
i have a custom built Cartesian 3d printer with 2 independent Z motors running the 6HC with 3.3 firmware. I noticed when I run repeated lead screw leveling commands, the initial probe before adjustments for every command are about the same and the left side appears to be consistently higher than the right side. I'm using a genuine BLTOUCH for leveling.

I have these commands in my config.g:

M584 X0.0 Y0.1 Z0.2:0.3 E0.4:0.5                   ; set drive mapping
M671 X-20:350 Y150:150 S5; leadscrews at left and right of X axis
M208 X0:340 Y0:310     ; set axis limits

For testing purposes, I configured my bed.g file with the following:

G28 ; home
G30 P0 X20 Y150 Z-99999 ; probe near front left leadscrew
G30 P1 X275 Y150 Z-99999 S2 ; probe near rear leadscrew

I kept repeating the G32 command but the bed doesn't appear to be getting any more level:

12/18/2021, 1:55:32 PM	G32
Leadscrew adjustments made: -0.114 -0.118, points used 2, (mean, deviation) before (-0.116, 0.001) after (0.000, 0.000)
12/18/2021, 1:54:24 PM	G32
Leadscrew adjustments made: -0.122 -0.121, points used 2, (mean, deviation) before (-0.122, 0.001) after (0.000, 0.000)
12/18/2021, 1:53:18 PM	G32
Leadscrew adjustments made: -0.164 -0.075, points used 2, (mean, deviation) before (-0.124, 0.031) after (-0.000, 0.000)
12/18/2021, 1:33:03 PM	G32
Leadscrew adjustments made: -0.154 -0.053, points used 2, (mean, deviation) before (-0.109, 0.035) after (-0.000, 0.000)

Could this mean I have a hardware issue or is the adjustment not taking place for some reason?

Thanks much,
Ed

@droftarts Thanks, this is exactly what I was looking for.

@o_lampe Thanks, that was a typo, but the question still remains, how do you change the home offset to compensate for the print head being offset?

Ignore this one please. I can't delete it. I rephrased the posted a better question here:
https://forum.duet3d.com/post/230220