i just got simply 3d and its a nightmare.

keas · 2016-09-17T15:24:22.000Z

what in the hardware could be causing this, would it be something wrong with thing chip or a part on the printer? i configured it to a printer bot settings i thought.

Perry_1 · 2016-09-17T15:46:43.000Z

wirlybird said it correctly.

I would just add- head off to the S3d forums and start reading about your specific printer and the issues people may or may not be having.

Contact S3d support.

Google your issues- likely your maching or incorrect profile selection for your printer in both software packages.

keas · 2016-09-17T18:13:25.000Z

so it seems like its not zeroing in the corner of the bed like it seems to think its doing. its more towards the center of the bed. how do i modify where the program thinks zero on the x and y axis is? i still have no idea why it keeps lower the z axis into the bed. i worried that this will break the bed or the z axis. so how do i set it properly because the videos they have dont really seem to help much with my issue.

wirlybird · 2016-09-20T11:19:19.000Z

Definitely jump over here - https://forum.simplify3d.com/viewforum.php?f=1

and check it out and post the same thing as you did here. As Perry said give S3D support a yell they are good.

But since this is happening in more than on package probably contact Printbots also or google for it.

MachChris · 2016-09-20T11:29:30.000Z

I have s3d on 3 different PB’s, play, plus and simple metal, it is fantastic!

you shouldn’t need s3ds bed level if wizard since all of these printers have an auto level feature (unless you have removed it.

S3d has premade profiles for all of these printers, I suggest you use those. They work great right out of the box.

twiesner · 2016-09-20T14:05:40.000Z

What version of the simple metal do you have? Is it a ref F4, F5, or a F6? Is the build volume set to 150mm on the x,y, and z axis? I’ve had it happen to me before where the build volume accidentally got changed and it started printing in the corner of my printrbot simple. I’ve also had it happen where the printrboard started malfunctioning (rev F5) on a printrbot plus and the z-axis stop end would never get triggered and drive right into the board. Had to contact Printrbot to have them send me a new board.

I’ve attached my s3d settings under the g-code panel for my simple. See if your settings match up.

s3dSettings.jpg797×717 306 KB

ryanneufeld · 2016-09-20T16:06:25.000Z

Try my FFF profile. Dropbox - Printrbot Simple Metal.fff - Simplify your life

I’ve had more successful prints with that than any other software. I hope this helps.

keas · 2016-09-20T16:59:29.000Z

thanks that really help. it stopped it from trying to go past the max x and y axis, but it still lowering the head into the bed. do you think this could be a hard ware issue?

keas · 2016-09-20T17:00:56.000Z

how would i check that to find out what version it is should the f5 be on the board some where?

twiesner · 2016-09-20T17:02:39.000Z

Look underneath on the printer. It should say right on the printrboard

twiesner · 2016-09-20T17:07:11.000Z

You can try this to determine if the probe is going bad or being ignored for the z-axis: https://printrbot.zendesk.com/hc/en-us/articles/208275723-Auto-Leveling-Probe-Triggered-vs-Open

ryanneufeld · 2016-09-20T17:50:42.000Z

Do the auto leveling thing the other guy mentioned.

KC_703 · 2016-09-20T17:56:15.000Z

Could be as simple as reversing the XY axis… Under the G-Code tab (need to be in Advanced settings), check X & Y under “Flip build table axis”.

keas · 2016-09-28T19:01:33.000Z

yah so mine is the f5. so do i need to contact printerbot?

keas · 2016-09-28T19:06:05.000Z

so this is what came up when i ran the M119 command.

Capture_16.PNG986×740 48.2 KB

MachChris · 2016-09-28T19:15:19.000Z

Now you have to put something under the probe to trigger it and run M119 again to see if the Z status changes.

twiesner · 2016-09-28T19:21:00.000Z

Hard to tell. It looks like you just turned on your printer and enter the command and then powered off your printer.

Turn your printer on, enter the command. Home the x axis and re-enter the command. Then repeat for the y and z axis. If any of the axes remain open after being home then there is a issue.

keas · 2016-10-01T17:46:03.000Z

this is what came up when i ran it the way you said to. i also checked to see if i had a f5 board and i do will that be a problem.

Attempting connection at \\.\COM5…

Testing plaintext communication protocol…

READ: ok

Connected to machine!

SENT: T0

READ: echo:Active Extruder: 0

Active Extruder: 0

READ: ok

SENT: M105

READ: ok T:23.7 /0.0 B:0.0 /0.0 T0:23.7 /0.0 T1:22.5 /0.0 T2:38.3 /0.0 @:0 B@:0

SENT: M119

READ: Reporting endstop status

READ: x_min: open

READ: y_max: open

READ: z_min: open

READ: ok

SENT: M105

READ: ok T:23.7 /0.0 B:0.0 /0.0 T0:23.7 /0.0 T1:22.4 /0.0 T2:38.4 /0.0 @:0 B@:0

SENT: M105

READ: ok T:23.7 /0.0 B:0.0 /0.0 T0:23.7 /0.0 T1:22.5 /0.0 T2:38.3 /0.0 @:0 B@:0

SENT: M105

READ: ok T:23.7 /0.0 B:0.0 /0.0 T0:23.7 /0.0 T1:22.5 /0.0 T2:38.3 /0.0 @:0 B@:0

SENT: M105

READ: ok T:23.7 /0.0 B:0.0 /0.0 T0:23.7 /0.0 T1:22.5 /0.0 T2:38.3 /0.0 @:0 B@:0

SENT: M105

READ: ok T:23.7 /0.0 B:0.0 /0.0 T0:23.7 /0.0 T1:22.5 /0.0 T2:38.3 /0.0 @:0 B@:0

SENT: M119

READ: Reporting endstop status

READ: x_min: open

READ: y_max: open

READ: z_min: TRIGGERED

READ: ok

SENT: M105

READ: ok T:23.7 /0.0 B:0.0 /0.0 T0:23.7 /0.0 T1:22.5 /0.0 T2:38.3 /0.0 @:0 B@:0

SENT: M105

READ: ok T:23.7 /0.0 B:0.0 /0.0 T0:23.7 /0.0 T1:22.5 /0.0 T2:38.3 /0.0 @:0 B@:0

SENT: M105

READ: ok T:23.7 /0.0 B:0.0 /0.0 T0:23.7 /0.0 T1:22.5 /0.0 T2:38.3 /0.0 @:0 B@:0

SENT: M105

READ: ok T:23.7 /0.0 B:0.0 /0.0 T0:23.7 /0.0 T1:22.5 /0.0 T2:38.3 /0.0 @:0 B@:0

Disconnected.

Attempting connection at \\.\COM5…

Testing plaintext communication protocol…

READ: ok

Connected to machine!

SENT: T0

READ: echo:Active Extruder: 0

Active Extruder: 0

READ: ok

SENT: M119

READ: Reporting endstop status

READ: x_min: open

READ: y_max: open

READ: z_min: open

READ: ok

SENT: M105

READ: ok T:23.1 /0.0 B:0.0 /0.0 T0:23.1 /0.0 T1:22.4 /0.0 T2:38.3 /0.0 @:0 B@:0

SENT: M105

READ: ok T:23.0 /0.0 B:0.0 /0.0 T0:23.0 /0.0 T1:22.5 /0.0 T2:38.3 /0.0 @:0 B@:0

SENT: M105

READ: ok T:23.0 /0.0 B:0.0 /0.0 T0:23.0 /0.0 T1:22.5 /0.0 T2:38.3 /0.0 @:0 B@:0

SENT: M105

READ: ok T:23.0 /0.0 B:0.0 /0.0 T0:23.0 /0.0 T1:22.5 /0.0 T2:38.3 /0.0 @:0 B@:0

SENT: G29

SENT: M105

READ: Bed x: 10 y: 142.40 z: -0.19

SENT: M105

READ: Bed x: 10 y: 10 z: 1.01

SENT: M105

READ: Bed x: 142.40 y: 10 z: 1.30

READ: ok

READ: echo:endstops hit: Z:1.30

endstops hit: Z:1.30

READ: ok T:22.5 /0.0 B:0.0 /0.0 T0:22.5 /0.0 T1:22.5 /0.0 T2:38.3 /0.0 @:0 B@:0

SENT: M105

READ: ok T:22.5 /0.0 B:0.0 /0.0 T0:22.5 /0.0 T1:22.5 /0.0 T2:38.3 /0.0 @:0 B@:0

SENT: M105

READ: ok T:22.5 /0.0 B:0.0 /0.0 T0:22.5 /0.0 T1:22.5 /0.0 T2:38.3 /0.0 @:0 B@:0

SENT: M105

READ: ok T:22.5 /0.0 B:0.0 /0.0 T0:22.5 /0.0 T1:22.5 /0.0 T2:38.3 /0.0 @:0 B@:0

SENT: M119

READ: Reporting endstop status

READ: x_min: open

READ: y_max: open

READ: z_min: TRIGGERED

READ: ok

SENT: M105

READ: ok T:22.5 /0.0 B:0.0 /0.0 T0:22.5 /0.0 T1:22.5 /0.0 T2:38.3 /0.0 @:0 B@:0

SENT: M105

READ: ok T:22.5 /0.0 B:0.0 /0.0 T0:22.5 /0.0 T1:22.5 /0.0 T2:38.3 /0.0 @:0 B@:0

SENT: M105

READ: ok T:22.5 /0.0 B:0.0 /0.0 T0:22.5 /0.0 T1:22.5 /0.0 T2:38.3 /0.0 @:0 B@:0

Disconnected.

keas · 2016-10-01T17:48:59.000Z

this also happens to be where the printer thinks 0 is for all 3 axis.

20161001_104643.jpg3024×4032 3.28 MB

keas · 2016-10-05T17:22:00.000Z

that help with it trying to go past the max x and y axis but it still digging into the bed and dragging across the bed. Could this be a issue with the firmware?