@Raxtus14 M997 S2 updates the Raspberry Pi. Send M997 or M997 S0 to update the 6HC itself. See https://docs.duet3d.com/en/User_manual/Reference/Gcodes#m997-perform-in-application-firmware-update

For SBC setup, see https://docs.duet3d.com/en/User_manual/Machine_configuration/SBC_setup

Ian

@jay_s_uk Got it and good to go now- can be changed to solved. Thanks for all the help!

@SpeedyDad If you can find the MCU on the PanelDue, you can check which version it is, see https://docs.duet3d.com/Duet3D_hardware/Accessories/PanelDue#version-history

Early version 2 - ATSAM3S2B processor (64MHz, 32kb RAM, 128kB flash)
Version 2 (Manufactured from August 2016) - ATSAM3S4B processor (64MHz, 48kb RAM, 256kb flash).

Most likely it's over 9 years old, which isn't a bad run!

Ian

@rodneysramosj Is the X endstop a max endstop or min endstop? Currently your G1 H1 X... homing moves are positive, so should be moving to the right, towards a max endstop. If this is wrong, you probably need to check the direction the motors are moving is correct, see https://docs.duet3d.com/en/How_to_guides/Commissioning#h-10-check-stepper-motors

Your printer origin X0 Y0 Z0 should be in the front left corner. Positive X moves should move the nozzle to the right, positive Y moves should move the nozzle towards the back.

Ian

Thanks for the help, Everything is up and running after the update. Now looking to experiment with input shaping.

@oozeBot We have some more background information about the cause of this problem; it appears to affect the 6HC/6XD only. @dc42 is going to improve the upgrade mechanism in 3.6.0 stable.

@kazolar for touch mode it's the same as for any other probe type, use the A parameter in the M558 command that configures the probe. There isn't a facility to do multiple scans in scanning mode.

@gloomyandy said in SZP for bed level in 3.6-RC1:

You are not setting the probe threshold/trigger value in config.g (the P parameter to G31), so it will be using whatever the default is (which is almost certainly not correct) until you have performed a M558.1.

Correct. You can't guess this value so it would just be a random number. Before any use of the SZP I run a M558.1, such as in bed.g and mesh.g.

As to the mesh not reading zero at the centre of the bed. I would expect the scan to return 0 for wherever you have homed/set Z=0, ideally you will be homing and calibrating the probe at the same location

correct. I answered myself above when I remembered I am setting Z=0 with a separate probe at the back of the bed. So the bed scan does not necessarily cross zero, especially if the G31 offset for that probe isn't close enough.

Everything seems to be running well. I don't know why I had so much trouble setting it up. I understood the documentation but thought that I didn't because the results were so flaky. Knock on wood but it is stable right now. It is a very slick setup and much better than what I had before. Thanks for the help.

@thomasvanderwal said in Duet 2 v1.02 not responding:

Calibration is now the problem. After setting the trigger height and z0 I wanted to Run Delta calibration. This is going well. But the mesh compansation is not going well : Error: G29: Probe was not triggered during probing move
The nozzle even goes besides the bed? I have in config.g : M557 R95 S10. The bed is 20cm in diameter,

As this thread is now well over 100 posts and does not match the description and initial issue, I think you'd have better luck starting a new thread for your delta calibration issue. You're more likely to get some helpful delta users to lend a hand with calibration.

@Phaedrux Ok! Thank you very much! That's work fine now. 👍

I had a problem with my tablet but I found the solution on this post.
I also had an error report with my ZPROBE line in my config.g but after a complete reboot of the printer I no longer had an error.

Please give us more information.

https://forum.duet3d.com/topic/5909/guide-for-posting-requests-for-help

@dc42 Thank you for your help! We had to fix the jumpers and connect a power supply for the fan pins to work.

Great! I’ll proceed the way you’ve outlined.

Thank you for the detailed response. Extremely helpful!

@konvalm FYI we have an outstanding ussie regarding this situation:

https://github.com/Duet3D/RepRapFirmware/issues/1082

T3P3 created this issue in Duet3D/RepRapFirmware closed SAME70 - Firmware update failures #1082

@T3P3Tony said in 4 Z Axis Leadscrews:

Please paste config.g in use the code block (</> icon in the text formatting menu), to format it

I have edited your post to paste in the contents of the file in a code block. this makes it much easier for people to help you.

from the documentation here:
https://docs.duet3d.com/User_manual/Connecting_hardware/Z_probe_auto_levelling#axis-levelling-using-endstops

When homing, RRF3 will home both axes, and stop each motor when each endstop is triggered. Note that DWC and M119 will only show one endstop per axis, but will show the axis endstop as triggered if either switch is triggered. So you can test them by triggering one at a time.

That is true for the object model as well.