Page 1 of 1

mcp - position readout

Posted: Thu Oct 27, 2016 11:13 am
by arhi
after homing mcp will set position readout to 0,0,0 which is not always correct ... for e.g. on my machine I home Z on "z_max" and not on "z_min" so after homing my Z is not 0 but 136 or 200 or 500 or 2000000 depending on my machine ..

ideally you can use M114 to read the last known position of the printer. it's support by almost all firmware's
http://reprap.org/wiki/G-code#M114:_Get ... t_Position

Re: mcp - position readout

Posted: Thu Oct 27, 2016 11:45 am
by CompoundCarl
My delta printer is the same way. Did you set the homing direction for the Z-axis in S3D correctly (it's on the G-Code tab). I set mine to max for the Z and the readout is correct when I home the Z axis.

So I would check and make sure you set the direction correctly

Re: mcp - position readout

Posted: Thu Oct 27, 2016 12:20 pm
by arhi
CompoundCarl wrote:My delta printer is the same way. Did you set the homing direction for the Z-axis in S3D correctly (it's on the G-Code tab). I set mine to max for the Z and the readout is correct when I home the Z axis.

So I would check and make sure you set the direction correctly
cool, that was part of the problem, thanks :)
(it still ignores the calibration height data etc.. would be better to M114 but this will solve the problem for me)

Re: mcp - position readout

Posted: Fri Oct 28, 2016 5:52 am
by CompoundCarl
arhi wrote:it still ignores the calibration height data
The calibration height is just the true distance from the endstops to the bed, right? So just input that for your Z-axis height and it will be correct.

Re: mcp - position readout

Posted: Fri Oct 28, 2016 9:53 am
by arhi
CompoundCarl wrote:
arhi wrote:it still ignores the calibration height data
The calibration height is just the true distance from the endstops to the bed, right? So just input that for your Z-axis height and it will be correct.
that's true just not very convenient :D (different print boards will have different starting point, changing it every time in process is not very convenient :D, auto reading it from firmware is hell of a lot more convenient) .. anyhow the homing direction solved the issue, I would not dwell on it, if I noticed the homing direction I would not created the thread at all :D