Prinrtbot Simple "ZProbe Outside Bed"

[pbtalkAM]

Hi Guys - I have X upgrade and Z upgrade and it worked well. I recently had to replace the Printrboard (bot tilted over and broke the microusb). I resetup things correctly with the new board, and used it for a few prints. Then just now, after doing some maintenance (I found the Z coupler got loose) I get this message after zeroing X and Z.

I did some searching, and someone pointed out that M211 should have X at 0, but the Printrbot Guide says to set it to X-25, which is what it has been.

I set it back to X =0 and it started to work. I have zero clue why. Any ideas? I thought very clearly it was supposed to be X-25.

This is what I have:


> M501
< echo:Stored settings retrieved
< echo:Steps per unit:
< echo: M92 X80.00 Y80.00 Z400.00 E96.00
< echo:Maximum feedrates (mm/s):
< echo: M203 X125.00 Y125.00 Z5.00 E14.00
< echo:Maximum Acceleration (mm/s2):
< echo: M201 X2000 Y2000 Z30 E10000
< echo:Acceleration: S=acceleration, T=retract acceleration
< echo: M204 S3000.00 T3000.00
< echo:Advanced variables: S=Min feedrate (mm/s), T=Min travel feedrate (mm/s), B=minimum segment time (ms), X=maximum XY jerk (mm/s), Z=maximum Z jerk (mm/s), E=maximum E jerk (mm/s)
< echo: M205 S0.00 T0.00 B20000 X20.00 Z0.40 E5.00
< echo:Home offset (mm):
< echo: M206 X0.00 Y0.00 Z0.00
< echo:PID settings:
< echo: M301 P22.20 I1.08 D114.00
< echo:Min position (mm):
< echo: M210 X0.00 Y0.00 Z0.00
< echo:Max position (mm):
< echo: M211 X250.00 Y152.00 Z250.00
< echo:Bed probe offset (mm):
< echo: M212 X-25.00 Y0.00 Z-0.80


EDIT:

Well what a surprise - after Setting M212 X-0, that third Z point, just like the manual said, completely missed the bed, and the probe dug into the board. Luckily I have a PEI surface and that took most of the impact so nothing serious happened. Why can't I zero the Z axis with M212 X-25?

[novice]

If this is the Simple Metal 1403, I believe M212 X20 is what you desire. . Your probe height could also probably use some tweaking if Z-.80 is actually required.

[pbtalkAM]

[pbtalkAM]

FYI that fixed it. Thanks all, been printing like a fiend since then. So sad that PB's own database of support is full of inaccurate information.

[Mooselake]

PBT was started back in 2011 because they didn't have any support at the time. My memory is fuzzy about exact dates, but even by 2014 it probably still wasn't very good. Like most high-tech vendors they don't go back and update errors in old product info (got a lot of support on your early 2016 smartphone?). I hear it's a lot better now, but since the 2011 model still works great I've never updated or needed it.

Kirk