These links should help.
I believe that endstop switches will need to be wired to the 2 outside pins of the connector.
Just wanted to add that after I had posted this issue on /r/3dprinting, a couple other people mentioned that this issue did not go away after upgrading to the meanwell psu.
Some people with an ender 3 pro (that has the meanwell psu) also have the same issue. This makes me to believe that this is simply an issue with the cheap ender 3 mainboard.
Why the noise is only on the X-Axis is unclear, but people that switched the X and Y connections had the noise and vibrations also switch to the the Y-Axis, so it has to do something with the X-Axis driver.
Anyways, I'll update this once I have converted to the Duet. For now I'll simply try to print with the bed off, or enable PID again, even if that noise and vibration will drive me insane...
@dc42 That's done it! It was user error after all. I manually installed the screen macros into the system editor thinking that was where they belonged, and I was editing them there. The actual version being read is what was auto-installed into Display Editor. Thank you for taking the time to set me straight.
Thanks everyone that gave me direction on this one. I'm running firmware 2.02RC5(RTOS) (2018-11-28b1).
Turns out you were right @ phaedrux. I had my motors AND my endstops backwards, making it appear as though everything was playing nice. I flipped the motors and home code around and it's moving as expected now!
I really appreciate the help!
Have you got "lift head" checked?
If not it will just reduce the speed to the minimum set value.
This may still be less than the minimum layer time you have set.
The resulting G code looks like this if the limits are reached
;Small layer, adding delay
G0 X69.27 Y91.783 Z3.7
G0 X89.258 Y92.474
From link above :
"You must use the M671 command to define the X and Y coordinates of the leadscrews. The M671 command must come after the M584 command and must specify the same number of X and Y coordinates as the number of motors assigned to the Z axis in the M584 command; and these coordinates must be in the same order as the driver numbers of the associated motors in the M584 command. The M671 command must also come after any M667 or M669 command."
Are you sure that ALL conditions mentioned above are met? Specially the one in bold?
@pro3d said in Can I use relative pos by +/-?:
My badly stated question was if I could just use [XYZE]+[nr] instead of switching back and forth between relative and absolute just by using the +/- sign in the command line
No you can't. Commands such as G1 X-10 already have a defined meaning, i.e. move to X coordinate -10. Similarly, G1 X+10 means the same as G1 X10.
@smoki3 said in Unretract after Tool Change:
yes because you get stringing between the last known position and the next print move
But if the next move is a print move including extrusion, then you need to unretract before making that move, so you won't get stringing. If on the other hand, the next move is simply a change of position without extrusion, then you might get stringing. In that case, the unretract needs to happen after the first non print move and before the next print move.
So the unretract needs to be conditional depending on whether the next move has an "E" element.
I can't off hand think of a way to do that other than a post processing script.
@owend said in Z probe fails - BL Touch - print continues:
M98 Pdeployprobe.g ; deploy mechanical Z probe
M98 Pretractprobe.g ; retract mechanical Z probe
This isn't necessary for the BLtouch when using M558 P9 probe type and firmware 2.0 or later. The Duet will keep track of the deployed state of the probe and manage it as needed during probing.
Everything else looks good.
Reading through the active ripple damping on the Duet2s there is quite a tie between instant speed, acceleration, and print speed.
I wonder if when one of the situations occur your system becomes more susceptible to wobble/ripple/ghosting.
Duration of acceleration is an exact multiple of major stepper size.
Actual 0-Instant speed time is an exact multiple of major stepper size.
Step rate an integer multiple of resonant speed.
Next time I buy steppers I'll be getting double ended so I can try some mass dampers.
Well, we've drifted off just a little bit
In order to add a little bit to the original topic: I managed to get the end stops and the trigger commands to work but I realized that my magnetic latching mechanism is too weak. So tomorrow I'll try to improve that. I also need to design a part cooling duct but the first print with the new Extruder showed that a lack thereof isn't all too bad
Looks like your connection to Duet3D was lost, please wait while we try to reconnect.