Topics created by The Chairman

@the-chairman Typically but the scope in which it applies can vary

@the-chairman said in G32 Error: Probe already triggered before probing move started:

@stephen6309 & @fcwilt thanks to both of you... that really helps a lot. My mod wire needs to be connected to exp HEATER3. "exp" means expansion header. Cool. Simple enough to do.

Now, how do I define HEATER3 as the real "Mod"? Do I have to edit config.g and add it somewhere?

Go back and look at my configuration.

You use M950 to create the PWM output signal which deploys/retracts the probe pin.

You use M558 to specify the probe characteristics and which input pin is to be monitored for probe state.

These are commonly put into config.g. There are other ways but that might just confuse you at this point.

Frederick

@dc42 Thanks! I am currently getting this error:

G32 Error: Probe already triggered before probing move started

I'm not even sure I have it wired correctly, but I think I do. 😄 I'll check out that link in a bit and see if I can suss it out from there.

@the-chairman, copy and pasting from your config.g file above
M203 X6000.00 Y6000.00 Z180.00 E1200.00 ; set maximum speeds (mm/min)
That is the maximum that the system allows but not necessarily the fastest it can go. That becomes a trial and error thing where you increase the speed until you loose steps and then you back off on the speed until you are happy with te safety margin.