@jay_s_uk thanks... the error message doesn't come anymore!
Can I also assign the position in the end code? The job currently ends in the rear left corner and the x and y axes are no longer referenced, here is the code:

G91 ;Relative positioning
G1 E-2 F2700 ;Retract a bit
G1 E-2 Z0.2 F2400 ;Retract and raise Z
G1 X5 Y5 F3000 ;Wipe out
G1 Z10 ;Raise Z more
G90 ;Absolute positioning

G1 X0 Y{machine_depth} ;Present print
M106 S0 ;Turn off fan
M104 S0 ;Turn off hot end
M140 S0 ;Turn-off required

M84 X Y E0 ;Disable all steppers but Z

@tristanryerparke I have now tested using 3.5beta3 and the uniqueId field does get populated when I make the CAN connection after powering up both the main board and the SAMMYC21.

The only reason I can see why the uniqueId would not get populated is if the SammyC21 was running firmware earlier than 3.4.0. But in that case the uniqueId field would never be populated.

Have you sent the M587 command to add your wifi SSID and password?

https://docs.duet3d.com/User_manual/Reference/Gcodes#m587-add-wifi-host-network-to-remembered-list-or-list-remembered-networks

And yes, it will only connect to a 2.4ghz access point.

@deckingman will post updates as I go. 👍

@Phaedrux with a little delay i now understand what is meant... i exchanged the x and y axes and endstops on the board and also in the code and now everything seems to be ok... thank you very much!

@oliof yeah, that’s it. Huge pain to figure that out. I’ll add docs to klipper eventually, but it’s not my priority at the moment. Meanwhile it should be easy enough to figure out by looking at the schematics.

@wdenker from the datasheet, 143C:

https://www.trinamic.com/fileadmin/assets/Products/ICs_Documents/TMC2209_datasheet_rev1.09.pdf

However that's internal temperature generated from the MOSFETs inside the TMC2209, not chamber temperature. The hotter the chamber, the less motor current can be used before the driver overtemp kicks in.

@oliof thanks for confirming what was going on!

@Phaedrux thanks for your patience ! Maybe you could set that with z=0 in the config.g for complete beginners like me in the documentation?

@Proschi78 said in Auto Z offset calibration:

{global.tool0 = move.axes[2].machinePosition}

Should be
set global.tool0 = move.axes[2].machinePosition
however it will always be zero (or whatever your axis minima is set to with M208)
Also no need for curly brackets here.

Likewise the second calculation is going to return zero (axis minima) because you use H1
I feel you should be using H4 on the second test at least and that creating the firt global is largely redundant.

I can't test, but maybe

G1 Z50 F800 M291 S3 R"Clean the nozzle" P"The nozzle has been pre-heated. Clean it from any plastic debris" G1 Z25 F800 G4 P0 M300 S666 P666 ; beep M291 S3 P"Place the offset tool below the nozzle and press OK to perform the macro, or CANCEL to abort" G29 S2 G4 P200 ; wait 200ms G1 H1 Z-19 F50 ; move 19mm down, stop when hitting the offset tool (but don't risk crashing the bed) M400 set global.tool0 = move.axes[2].machinePosition ; Store the current Z position in tool0 G1 Z25 F3000 G28 X0 T1 G1 U175 Y110 Z25 F3000 G1 H4 Z-20 F50 ; Move Z-axis down 20 mm M400 set global.tool1 = move.axes[2].machinePosition - global.tool0 ; Calculate the difference between current Z position and tool0 and store in tool1 echo "The difference between the two nozzle heights is: " ^ global.tool1 ^ " mm." ; Output the difference to the console G4 S15 G1 Z25 F500 G28 U0

Please send an email to warranty@duet3d.com and CC your reseller. Include a link to this forum thread and the details of your original purchase. You'll receive a reply with a form to fill out.

Note to whoever repairs this board: yesterday I identified a QC issue with the soldering of the wifi module to the PCB on a different board variant. This is likely the same issue. Resoldering all the joints using no-clean flux, hotplate and fine-tipped soldering iron will probably fix this.

@techworld Its a Linux file system so you cant see them by plugging the SD card into a Windows computer

@dc42 thank you, those are some good pointers. I guess I'll leave it at that (right now I have it set at separate moves for each axis).

@Anon1337 the 1HCL will work with a wide range of 4 wire bipolar stepper motors with encoders (up to 6.3A RMS). We recommend using stepper motors with 1.8 degree step angle and an encoder with >1000PPR/4000CPR.

The 23CL builds the Duet 3 expansion board control technology + encoder into the motor casing itself( with an optional brake) so a 1HCL is not required - it can be connected directly to the CAN-FD bus.

For external controllers I recommend you use the 6XD to produce step/direction signals and select controllers that can accept these. The 1XD also allows connection to these sorts of controllers.

Whenever you have multiple motors moving the same gantry you need to take precautions to avoid the gantry getting out of tram. you can set the homing files up to move both motors at once when homing and ensure both sides of the axis touch off the homing switches before homing finishes. the 6XD and 1XD also have inputs for the "alarm"/"error" outputs that many closed loop external drivers have that should be connected and dealt with appropriately, for example, stop homing if the alarm on one or both motors are triggered.

@axiom do you have a filament sensor of some sort connected? If so you can add logic to filament-error.g which will run when it triggers. See:

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

Within that you could, for example use M291 to produce a dialog box with instructions etc:
https://docs.duet3d.com/User_manual/Reference/Gcodes#m291-display-message-and-optionally-wait-for-response

@Phaedrux said in Error: G0/G1: insufficient axes homed:

Keep in mind that your movement directions should be like this
-X to the left, +X to the right
-Y to the front, +Y to the back

The endstop position is arbitrary, so rear right is fine. But are your motor directions correct?

To have the endstops at the rear right and the low end of travel means that your axis movement would need to have

-X moving to the right, +X to the left
-Y to the back, +Y to the left

Your homing files would need to flip their directions from what you have now so that they move towards the endstop.

You may need to change the direction of rotation of the motor to achieve this.

And keep in mind this would have the effect of your prints being rotated 180 degrees from the slicer preview.

@oolyk that has nothing to do with the sd card. the firmware should be locked as instructed

I thought of coloring some easter eggs, but regular patterns require CNC control and a rotary device. Even when using laser cut motive masks it's hard to control by hand.

I got inspired by the felt pen easter egg plotter

Solved and no problem with 3.5.0 beta2 and PrusaSlicer 2.5.0 👍