Topics created by tom_Nbg

@Wilber Please start a thread for your issue and provide some detail on your setup and configuration.

@dc42

Thank you for the great reply - im having similar issues and have been for ages. I had been chalking it up to the BuildTac Magbed stick on sheet as being the culprit - but I suspect now it is - for me - a combo of all those 3 issues you mentioned above + the Magbed.

I need a bridgeport Knee mill some MIC6 🙂

@tom_Nbg said in Help: mesh compensation ist not correcting right:

The problem is, that I need G32 because of the printers setup. When powering off or on the printer, the screws sometimes move a bit and so I have another tilt on the x-gantry..

Right, but what I'm saying is can you manually level it instead of G32, just in case there is something wrong with your G32.

If you do it manually and it works fine, then we have narrowed it down to a problem with your bed.g.

Ok, so you're manually mechanically leveling the X axis first and then running G29, and it's during G29 that it's cooling?

I suppose it's the large DC heat bed that's producing a magnetic field to interfere with the BLTouch.

You could increase the R value in M558 to add a bit of a pause between probing moves. That may allow the heatbed to maintain temp a bit better, but would add a few seconds to each probe move.

There was talk of having drivers report 0C when not enabled and something like 50C when enabled, but that hasn't been implemented. It's not clear to me that 50C would be the correct value. For example, one of my printers has a fan that turns on when the MCU temperature exceeds 45C or the drivers give an overheat warning. With enabled drivers reporting 50C, that would always turn the fan on, which I don't want to do because it isn't necessary. But a user running the drivers at 2A current probably would want to turn the fan on any time the drivers are enabled.

@dc42 , @SIam

Thank you again!
It is working now and I understood why 🙂

@tom_Nbg said in Problems with Mesh compansation:

I had LDO/Nema17 Steppers on z (rated to 1A).

Try setting motor current to M906 Z800.

Ian

The R parameter in M305 and M308 commands is only needed in config.g files for legacy Duets, i.e. Duet 0.6 and 0.8.5 boards. For all other boards, all versions of RRF know the correct resistor values, so the R parameter is never needed.

@tom_Nbg Yes. Your original configuration had values for multiple extruders separated by colons but you have only defined a single extruder in your M584. Steps per mm, accelerations, jerk, speed and motor current only need single values for X,Y Z and E.