@peirof U3 is one of the regulator chips on the board (5v to 3.3v I think?) Check thr labels on the board and you'll spot it, or look at the schematics.

Moreover though, you almost certainly have an issue in your wiring, probably with your z probe. You need to fix this before blowing up another board! As the others have said, get a multimeter and check ever connection & wire twice before they cause further damage

@dc42 Thank you! This is what I needed. I come from the Ultibot days when they gave us a Simplify3D conifugration than ran a G28 every print. I'll give this all a go, I was having all sorts of issue but after microstepping back 0.9mm each print has been perfect so I'll let you know soon.

Did a lot of work upgrading from 1.16, replaced duet wifi 2, re-wrired (and checked my crimps) and checked everything w my multi-meter, installed new PETG tube inside e3d, installed new themistor, replaced my PEI bed, so I wanted to be sure everything was good now that I know more this go around.

Thanks @jay_s_uk !

@gloomyandy Yes M122 does show an IP. So that is worth looking into but so far I cant find those settings on the Deco, I can bar devices but not specifically give them permission to join the mesh. I will keep looking.
Thanks

@gloomyandy Ahh I didn't know that. It is counter-intuitive but thanks for letting me know. TIL

@peirof, there is also a phase 5 with the part cooling fan on if you are calibrating tools instead of a heater (using the T option rather than the H option)

@alankilian manual process to to tun a command that allows it below z, set to it to right where it holds a paper and set G92 Z0, then you can get offset with G30 S-1. Like I said it never works for me, just leave it at zero. I believe but not positive after homing if you run G30 it'll set the homed height, and then when you create the mesh map it doesn't complain. I can do that, just the manual process doesn't work for me.

I keep printing a PITA object so if it fails again here I'll move to some benchy type stuff.

@fcwilt

Discovered today that my filament sensor is missing.
I'll go back through my original config.g to see if I can find the settings.

Got the 1st test print completed.
I had to baby step +0.4 to get filament to come out.
This is with mesh comp. on.

Figured out why homing wasn't working.

For some reason, X needs to be homed 1st followed by Y.
So, I had to split those up in the homez.g file

I still get the "jump" when homing.

@randyl00123 did you get the board from AliExpress? There is a fuse on the Duet to protect that circuitry from fires, it won't necessarily act fast enough to protect circuitry from over voltage.

@ddxdesign Great to hear you got there in the end!

@fcwilt M561 also cancels babystepping AFAIR, so if you issue M561, you don't need an M290 R0 S0. (see https://github.com/Duet3D/RepRapFirmware/blob/123d4362a04a709103971dd10b94e916b8790ef8/src/Movement/Move.cpp#L581). I was wrong.

@user3d said in Gaps in wall while printing:

@dc42 Any suggestions to resolve this backlash problem in preloaded ball screw system.

Are there grub screws involved in coupling the ball screws to the motors?

You have a huge amount of backlash in the direction bottom left/top right in the first and last images you posted. How does that direction line up with the axes of your printer?

@o_lampe said in Duet3 Incorporation with Roll2Roll Manufacturing:

@t3p3tony If they'd pretend that the encoder represents closed loop signals of the Y-axis, they only have to invert the counter measures => More pulses from the encoder increase Y speed instead of lowering

That"ll work when X-motion and Y-motion have fixed ratio.

Thats what sparked this idea, but hoping we could gain more freedom than having the ratios between the two axis similar, or fixed.

I have also checked the converter with my drone DJI Mini, and it worked quite well.

@marco_76 said in Multiple z motors homing with firmware 3.3:

]

Solved!
I changed the names of the pins: exp.e2stop --> duex.e2stop
So now the sensors for Z are the following and it is working fine

M574 Z1 S1 P"zstop+duex.e2stop+duex.e3stop"

thanks,
Marco

@peirof forget it.... Google has the power...