Topics created by Synapsis

Yes that should work, except that you should also put this line in config.g:

M584 Z2:4 U11 E3 P3

Also use the same Z homing code in the Z homing section of homez.g, or have homeall.g call homez.g using M98 to do Z homing.

Connect the U axis endstop switch to the E0 endstop input.

Thanks David

http://www.garlandogioielli.it/images/CAM.mp4

OK found out that the security type has to be the same one both routers, some device don't care bu the duet does.

Thanks Ian for the suggestion after what you said I will at this point leave them as they are.
Of that little wooble like you say isn't a problem no need to change if it works.

Thanks to all for the info.

Thanks David probaly the ground connection as it was dark and to be honest I redid the wiring.

Now without doing anything its working but I ill check the connection.

I will leave as they are I perfer the precision over the speed I have no need for the plate to rush 40 cm down in 5 secs.
🙂

@DjDemonD:

Just put your minimum travel limit as a negative number.

Eg my corexy with titan x needs to start 10mm after the endstop so I use
M208 X-10 S1
M208 X270
This sets min and max. It can home to the endstop but then it will say x=-10 on panel due or DWC. Since your slicer is never going to command a move to a negative x coordinate (unless its a delta printer) it will never move to hit the endstop.

I must have something setup backwardsas this does not work for me.

Where is your endstop on the right or left and where is your Y0 X0 right or left.
When I home, if I have set M208 X385, in the DEC its say x position 385, now I move left to zero using M208 X-2 S1 as my limit so it stops befor hitting the motor mount.
But if I move to the right, positive X, it will keep going until it hits the endstop say X 385 in the DWC.

If i use any other number it will move left that amount so if I use M208 X 200 it will stop in the middle.

Having M83 in config.g only causes problems if you slice your models using absolute extruder coordinates (instead of the relative coordinates we recommend) AND you don't include a M82 command in the start gcode to tell the firmware that.

In macro files, extruder coordinates are always relative to the present position, because there is no way for the macro to know how much extrusion has already been done.

Absolute extruder coordinates are a hangover from the early days of 3D printing. Now that we have extrusion factor modification (M221), mixing extruders and macro files, they make no sense.

@dc42:

Perhaps you need to reduce the maximum speed (M203) and/or maximum acceleration (M201) of the Z axis.

I did but not knowing what a good balance would be would you be so kind to give me an idea?
Also the second Benchy has problems on the layers could that be the z aixis?

I'm still looking for a setup so I can use a nema 17 motor with an extruder to pull the filament from the spool.
Can this be done?

thanks