Topics created by Simone

@oliof thx!

@Simone I've updated the calibration macro again, so this time it actually works correctly! @OwenD was kind enough to point out the error in my maths, which gave NaN results in some circumstances, and checked that it now gives correct answers. See https://docs.duet3d.com/en/User_manual/Tuning/Orthogonal_axis_compensation#calculate-the-skew-factor

Ian

@Simone there are two versions of the thumbnail so the PanelDue display can show the 32x32 one. Glad you got this sorted out! Also, for slightly smaller size, you can use QOI format.

@Simone in my PrusaSlicer configuration I selected GCode flavor: RepRapFirmware, and it looks like in the Custom GCode section it has set Color change GCode to M600. So it may just work.

An alternative is to configure multiple tools in config.g, one for each colour, all using the same heater and extruder. In the tpost0.g file use a M291 command to ask the user "Load filament for Tool 0, press OK when done" and similarly for the other tools. Then slice the model in PrusaSlicer to use a different tool for each colour.

@Simone Eventually you have a high "first layer extrusion factor" ?

I have a macro that runs when I start the printer to do some startup tasks - heat the bed, home the printer, level the bed, generate the mesh. To deal with the issue of having the printer start moving on its own, I post a blocking M291 message to the user asking if they want to start the process. The need to give the OK.

@Simone https://docs.duet3d.com/User_manual/Reference/Gcodes#g31-set-or-report-current-probe-status P is the trigger value; certain probes report a value between 0 and 1000 (IR probe, Smart Effector, Piezo probes) and setting P allows to fine tune the trigger value of whatever gets reported.

@Simone said in how to add the z-probe status?:

how i tell the difference in height between the probe and the nozzle to the height map?

See https://docs.duet3d.com/User_manual/Connecting_hardware/Z_probe_testing#calibrate-the-z-probe-trigger-height

It would help you a lot, and speed up helping you, if you did what I asked for earlier:

Please send M115 in the console and post the response so we know what hardware and firmware you are using. Please also post your config.g, homeall.g and homez.g.

Please post these as text, not images. Ideally, post code within code tags, by clicking the button that looks like </> in the toolbar.

Ian

You can click on Change Visibility and hide one of them if you wish.