Having trouble with zero

[wayne_webb]

I am trying to cut a vacuum plenum. I have set the zero to the dead center of a 4x8 but every tiem i try to run the file, it runs off one end of th table.
what am i doing wrong?
thanks

[harryball]

you are setting 0 in the middle and I assume telling the bot it is 96 inches long. So it starts at what it thinks is 0 and tries to move to 96" which is 48" beyond the end of the machine. This sounds like your file is expecting 0,0 to be at the home corner of the table.

You should set the 0,0 to the true physical 0,0 of the machine bed and try that.

Hope that makes sense, if not keep posting, someone can explain it better than me.

/RB

[wayne_webb]

The reason I did that is because the instructions in the manual said that the plenum file runs from a zero at the center of the table.
Maybe i read it wrong. i will check.
thanks

[wayne_webb]

"This file is made to be zeroed to the center of your plenum board. The best way to do this is to draw an X from corner to corner, then zero to the intersection. The Z axis should be zeroed to the surface of this board. Are you set up properly? Y/N" &setup
&setup="&setup"

[myxpykalix]

Draw your X on the table. Then take your bit and zero your X,Y to the center of the X. Then zero your Z to the table surface.

Sometimes it's the obvious things we screw up and someone else has to point them out. I do it myself sometimes.
But after you run the bit to the center do you reset your X,Y to Zero?

[wayne_webb]

Jack, tell me if i'm doing this right.
I jog the bit over to my mark at the dead center of my 4x8 table.
select "zero" from the dropdown
select "zero[2] axes x and y"

then do the same with the z

then do a "move to home" check to see if it does and it does.

My table is setup as a 48x96 and i'm selecting the plenum file for 48x96.

It gives me a box which says this file exceeds the table limit.
The bit makes a beeline fo the end of the table and past the limit switch

[ernie_balch]

move your bit to the lower left corner of the table and set this as 0,0 for X,Y just as you described
(Z then 2)

Now you will be able to go 96" in X and 48" in Y

ernie

[knight_toolworks]

that should work. I know where the zero is for the corner so I type in j2 48, 24 the z2 and that's it. it sounded like you zero'd right.

[jerry_stanek]

shouldn't that be j2 -48, -24.

[wayne_webb]

I don't know what i'm doing wrong.

I set the zero to the bottom left corner, opened the 48x96 plenum file and it's still doing it.

[myxpykalix]

I seem to recall for some reason when i first got my bot I had somehow set the table coordinates in such a way that in preview the "grid" of the table looked like it was half way off the square that represented the table in the preview.

Check to make sure your table coordinates are ok? Does this happens with any other file? Use PW to create a 48x96 square and have a offset inwards of one inch (a square that is 47x95)with some various circles to emulate that file and make sure you use center 0,0 and just try to aircut that and see if it moves around the table ok.
Then make the same file with your 0,0 at the lower left corner and try it.
Also try running these files in preview to see what you get. Just because it says the file is to be run from the center doesn't mean that it is setup that way, maybe someone altered it, is this something you got somewhere or created yourself?

[myxpykalix]

also try a different plenum file to aircut. If the bot goes all around the table chances are it is that file is somehow corrupt.

[bill.young]

Hi Wayne,

It sounds like you're doing the zeroing correctly for the plenum files in the Vacuum folder...at the center of the table... but that file only covers from -45 to +45 in the X-axis so it definitely shouldn't go beyond your tabletop edge. Support can probably help get you going the quickest, but here are some possibilities off the top of my head.

*) This is a long shot but are you sure your table top is a full 96" long? Measure from the center point that you made with diagonals to the edge, and make sure it's 48"

*) If that's correct..and it most likely is...make sure the tool goes the correct distance in moves. With the bit still zeroed at the center of the table, give it an "MX, -48" command and see if it goes right to the edge (stay close to the e-stop though, just in case!). If it goes more than 48" then your unit values are most likely wrong and will need to be corrected.

*) This doesn't have anything to do with the tool physically going past the limits, but if your table base coordinates are out of whack the software will lose touch with where the "real" tool is and can give table limit error messages. Re-zeroing to the normal 0,0 home corner using the current XY_zero routine gets them synced back up.

Bill