First, test that when you use the X and Y jog buttons, the head moves in the correct directions. You can send M562 H0 first to allow movement before homing. Next, operate the X and Y homing switches manually and use the M119 command to check whether they are reporting the correct stopped/not stopped status for the correct axes.

Leave the M201 Z value alone but try 1400 for X and Y.

@oliman I was going to. Awaiting a bit more reviews on the MMU2 and maybe the first design iterations.

nice post thank you http://www.ufa007.com/ufabet

@briskspirit said in Help choose: Maestro vs WiFi: Should I switch to thermistor as they are cheaper and don't need expansion board? (Do not plan to go higher than 300C) IMO, thermistors work fine. You print at the temperature which works best for you and which varies from filament to filament. So even if the thermistor was (say) 5 degrees off, and reads 200 when the true temperature is 195, it doesn't matter - you just print at 200. In reality, I swapped from some unreliable PT 100s (the wires kept breaking) to thermistors and didn't have to alter my print temperatures.

oops, typo ... when the three axis are recombined the three z-motors do NOT move together. RepRapFirmware for Duet 2 WiFi/Ethernet version 2.0(RTOS) running on Duet WiFi 1.02 or later + DueX5 Using the Duex5 for the extruder E5. The 3 motors are moving separately in homez.g to align the z-motors. at the endstops. Each z-motor stops independently when the build platform reaches that z-motors corresponding limit switch endstop. I had previous set it up with Drivers 5,6,7 on the Duex5 for the three z-motors and the behavior was exactly the same.

And, @dc42 , my questions weren't really answered here or in the page you linked. Baby-stepping, how is it implemented? Is it a permanently applied offset that affects all of the z moves or is it just during a print. And, it seems like applying baby-steps isn't just after the currently running command, they seem to come in bursts. I've clicked -.05 rapidly and nothing happens for quite a while, then all of a sudden, boom, they all kick in at once. I'm not trying to be a pain, but I'm not really getting the support I need here.

@kulitorum said in 8x8x6 METER concrete printer: Thanks for the nice words Custom slicer? No. I wrote a plugin for Simplify3d that is run after the slicing (replace the gpx.exe and export as a Makerbot file) that adds the rotation gcode. It also performs other small changes to the gcode, but nothing crazy. Nozzle: We normally use a nozzle with flaps, but we broke three during the print, supposedly because of small rocks in the mixture. It's not easy to get recycled materials that are clean and free from oversized rocks. We do not have any noticeable z-wobble some nice work there!!! is there any way you can share the plugin you made so that others can use it? I'm currently working on a project that i need to be able to make the G code to turn the head on my printer. just like your U axes. if you can share it or help make a plug in that would be amazing. you can see here what i'm trying to do. Thank you! ~Russ

SPLEH SIHT EPOH

The revision 1.04 Duets can tolerate up to 30V on the Z probe input pin. However, an 8MHz processor will be more than fast enough to process the signal.

You would need to connect the FAN- pin to the bltouch control wire and also connect a pull-up resistor between that wire and +5V. It will need to be a fan connector on the Duet, not on the DueX5. Don't connect to the V_FAN pin of the fan connector. Are you really using all 8 heater outputs?

Do you have B0 on that M307 line to disable bang-bang mode too?

This is one I designed to be as minimal as possible. https://www.thingiverse.com/thing:2476165

*** Taking crystal ball *** Check all your config files, I bet you are missing a ";" (semicolon) on some line that contains a comment with the word 'bed' (maybe you used used a ":" (colon) by mistake)

@fcwilt said in Forced averaging for M558: Hi, I would like to see an option for M558 to force the averaging of a fixed number of probes. No checking for consecutive readings, just probe A times and average them all. Perhaps some special value for for S could be used to enable this mode? Thanks. Frederick Yes, that should be straightforward to implement. Please remind me a week from now and I'll see if I can implement it in the 2.02 release.

Well, that will help. Thank you!

10um is a very tight tolerance, especially if the bed is a soft material such as PEI. Try S0.02 to double it to 20um.

@gorf26 said in multi color hot ends ?: let me know how that works out, will it work with the duet2wifi? Thanks gary Yes, but you will need a DueX2 to provide the 2 extra stepper drivers.

It's just odd that the motors will move properly when commanded manually but not when printing. Can you verify the motor current while printing? Send M906 and then M913 without parameters in the console and it will report what the current is set to along with any percentage scaling. Maybe there is a rogue current reduction command happening somewhere.