@chriss I started working on my corexy printer before they became popular. At the time I saw some forum posts from people who had built them using linear guides complaining that when the temperature in their shop changed 10 or 20 degrees, the XY mechanism would bind. The loose coupling for the X axis (and no additional support) was my response to that problem. I heat that printer to 50C when printing ABS and it never binds.

I haven't had any problems with first layer adhesion, either, even though the printer has no auto tramming or bed unflatness compensation.

@dc42

That is what I do at the moment. Here is my workaround bit in bed.g:

; bed.g M574 Z1 S1 P"io6.in" ; Z endstop switch M558 H10 F250:100 T6000 A20 S0.003 ; Klicky Probe settings ; bed.g script while iterations <=1 ; Perform 2 passes. G30 P0 X0 Y25 Z-99999 F6000 ; probe Z left front G30 P1 X0 Y270 Z-99999 F6000 ; probe Z left rear G30 P2 X275 Y270 Z-99999 F6000 ; probe Z right rear G30 P3 X275 Y25 Z-99999 S4 F6000 ; probe Z right front ;G1 H2 Z5 F2600 ; raise head 4mm to ensure it is above the Z probe trigger height M400 ; finish move, clear buffer M558 H1.5 ; Probe height to 1.5 while move.calibration.initial.deviation >= 0.005 ; Perform additional leveling if previous deviation was over 0.01mm. G30 P0 X0 Y25 Z-99999 F6000 ; probe Z left front G30 P1 X0 Y270 Z-99999 F6000 ; probe Z left rear G30 P2 X275 Y270 Z-99999 F6000 ; probe Z right rear G30 P3 X275 Y25 Z-99999 S4 F6000 ; probe Z right front ;G1 H2 Z5 F2600 ; raise head 4mm to ensure it is above the Z probe trigger height M400 ; finish move, clear buffer echo "Gantry deviation of " ^ move.calibration.initial.deviation ^ "mm obtained." M913 X100 Y100 Z100 ; Z current back default

You see for the first while loop I use a higher probing height so the probe won't drag over the bed.
In M558 we do already have two F values for speed. It would be nice to also have another height which then is used with the second speed set in F. Lowering speed and height does also improve accuracy.
Usage example: M558 F250:100 H10:1.5

hello Guys, i'm sorry for my late reply but i'm far form the machine this week.

i'll let you know if i solved and how when i'll apply all the test that you suggest me.

thanks again.

This is my mount for a Hemera on a CoreXY with toolboard and part cooling.
I have a PTFE tube sticking out through the bracket, guiding the filament..

I have threaded brass inserts for mounting the toolboars end the fan shroud.

There is just enough room for my index finger to operate the lever on the hemera.

The fan shroud can be adjusted up/down by oval mounting holes in the shroud.

Lastly my BL-Touch bracket, mounted on the opposite side with the hemera bolts. The long part is a cable guide.

I have some makeshift wiring in place since my toolboard partly gave up on me.

I hope you will find some inspiration by this.

Bracket.png
Bracket_2.png
Bracket_3.png
Shroud.png
BL-Touch_bracket.png
Screenshot 2022-04-09 202538.png
Screenshot 2022-04-09 202652.png

@heide

That height map looks good.

And, yes, Cura has a places for user code. I believe most slicers do.

You have to add your printer to Cura and configure the Cura settings for it.

Here is a screen shot of the Cura page where you can enter user code - you can see what I have entered.

Cura 4.x Machine Settings Page.png

Frederick

@owend said in Stopping a printing job after a warning or error:

@hobby-store said in Stopping a printing job after a warning or error:

Only that it does not even inform anymore after the upgrade to 3.4

In 3.3 there were notifications in the log

I can use own driver-warning.g and pause printing?? Have I understood the documentation correctly?
By default when it's not create this file is default is Inform user via console and continue

If you want to pause on a warning, then yes, you need driver-warning,g
@DC42 would have to confirm what waning/error disconnecting a stepper completely would cause as opposed to loss of a single wire by breakage.

Ok i must check with this files and back with informations 😉 Thx

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.

@oliof Nope. Did not work. Good idea though.

@otso Thank you very much. It works.

Best to take a look https://github.com/Duet3D/RepRapFirmware/wiki/Changelog-RRF-3.x#reprapfirmware-340

The simplest way to identify if it's related to updating to 3.4 is to roll back to 3.3 and see if the problem remains or is resolved.

@markz @zapta

At this stage I wouldn't rule anything out. I'd have some reservations about assuming that the relationship is a straight up trig function as you're relying on the leadscrew to be quite linear itself. There's also considerable force on it. At low Z heights, any small deviation would be amplified, so the table would be better assuming it's based on measured heights not calculated. Experimentation needed for both methods 🙂

@barracuda72 said in Strange Behaviour of G30:

@fcwilt
G30 Doku: If a "normal" Z parameter is given instead of -9999 or lower, then the bed is not probed, but instead that value is used as if the Z probe had triggered at that height.

so...a z-99999 is the same as a Z-10000

Using Z that way only applies when you have a P parameter which in turn means you will have X and Y parameters as well.

I just wanted to point out that G30 uses the 2 system MAcros and its not documentated...just a row rows of text would be enough that had explained that g30 always calls M401 and M402 no matter what probe type you have defined.

I suppose that since G30 requires a probe and when you specify that a probe exists it follows that the firmware will call those macros. If they are not needed you would not code them and then they would not be called.

Perhaps @Phaedrux can be beguiled into adding some to the documentation for G30 regards those macros - he is a fine fellow.

Frederick

@heide said in Mesh bed compensation:

@fcwilt I have now adjusted the config.g and it works. I stille need to level the bed by hand, but that must be later on.

Please mark it as solved and thank you very much for your help

Glad to hear you got it working and I am glad I was able to help.

Frederick

You're not the first person to have strange behaviour with Fritzbox routers, but I don't know why that may be.

When you're unable to connect to DWC are you able to ping the IP address assigned to the Duet?

Just in case it's SD card issue, do you have a spare to test with?

@brian said in Adding a Pause, continue prob:

Prusa is now producing better quality prints than S3D, thankfully.

Time to move on. 😉

If you're doing the pause for filament swaps checkout M600. I believe Prusa slicer should be able to insert those and you have complete control over the process using filament-change.g

https://docs.duet3d.com/User_manual/Reference/Gcodes#m600-filament-change-pause

If you want greater control over the mesh process you can create a macro called mesh.g and place it in the system tab. Inside that macro you can set the jerk and acceleration limits you wish for the Z axis and setup M558 however you like and then call G29 S0 to start the mesh creation. Then you can reset the z axis values back to whatever you want for normal operation.

To call mesh.g send G29 to start the process.

https://docs.duet3d.com/en/User_manual/Connecting_hardware/Z_probe_mesh_bed

@andy-vickers that's correct. The built in motion controller in the 5160 isn't useful in 3D printer applications.

@arnold_r_clark fair point 😀 I have boxes of various printer (spares), just in case.....