Machsupport Forum
Mach Discussion => Mach4 General Discussion => Topic started by: Greg F. on March 03, 2019, 12:05:38 AM
-
Ok need some help I'm new to mach4..
When I go to z probe it doesn't go down I have
To get it about 1/16 above for it can touch it
Maybe I'm doing something wrong ..and also if
I send it to cut it stays high above the surface...
-
Hi,
we need more information before we can help. Probing is enacted by the motion controller, being realtime, under
Machs supervision.
What motion controller are you using?
Do you have it setup correctly, that is can you issue MDI commands like G0's and G1's?
Do you have the steps per unit value correctly programmed in each of the axes? That is if you command G0 X4,
does it travel exactly 4 inches. I am assuming you are using inch units?
How are you probing, that is which button or Mach function are you using?
Have you tried to MDI a G31?
Craig
-
I have Ess smoothsteooer with bob MB2
And using mm..using the auto tool zero button
From mach4..yes I tried MDI
-
Hi,
have you got the axes setup correctly ie the 'steps per unit' value?
Are you using inch units?
Which button or function, there are several.....perhaps a screen shot of it?
You tried MDIing what.....a G31?
Craig
-
Hi,
sorry, disregard:
Are you using inch units?
you did answer it in your reply.
Craig
-
Is it better to use inches..
-
Hi,
no, it is strictly your preference.
Mach4 being a US product has preloaded parameters in inch units however they can be changed.
I use mm units and probe no problem.
Fill in some of the gaps....what touch/probe routine are you using?
Have you got the axes set u correctly?
What happens I you MDI a G31 move?
Craig
-
Did you mean the script...
-
Hi,
yes the script......if that's what you are using or one of the buttons.
Craig
-
The button I'm using is the AUTO TOOL ZERO...
-
Hi,
which one? A screen shot ....something?
I am asking questions and you are not answering.
Have you got the axes moving accurately?
What happens when you MDI g31's?
Craig
-
Ok also let me double check to make sure my
STEP PER UNIT is correct
-
I redid my step per unit.. is still the same thing I dont understand what I'm doing wrong....also when I do g31 it goes down only 1" but I have higher number for it to probe
I have to be like .125" over the plate
-
Hi,
if you are using mm units why are you describing in inch units?
Lets establish a few basics.
If you look on the Output LEDs panel on the Machine Diagnostics panel does the Probe LED light up when
you manually touch the plate? If not your probe circuit and/or connection to your BoB/controller is faulty
or you have not correctly assigned the port and pin to Machs probe input signal.
To establish whether G31 works jog to over the top of the touch plate, about 2mm above the surface.
<Zero> the Z axis.
Now MDI G31 z-5 f100.
The machine should lower at 100mm/min until it touches the touch plate and stop.
Were you to check now the value of the pound variable #5073 it should contain the current Z axis coordinate relative
to the Z=0 you started at.
Craig
-
The led works fine and when I did the G31 it also work good
But I can't find the #5073....
-
Hi,
#5073 is a pound variable.
Diagnostic/Regfile.....per attached
Brings up the Regfile diagnostic panel. Note that it can be pinned to the top level if you need it for diagnostics while
running a file for instance. Expand the pound variable tree. Use the Pound Variable Display Range to see variables you are
interested in.
Either way, whether you can see the pound variable or not it appears that G31 probe command is working.
That is the basis of all probe and touch off routines. You have proved that the hardware is doing its part.
Exactly what touch off routine are you using?. Maybe the underlying code is visible which would allow you to see
why your setup is not working.
Craig
-
My #5073: -36,378382 that's what shows
-
Hi,
try clearing it by double clicking and overwriting.
Then try your G31 MDI again.
Have you read page 38 of the Mill Gcode Programming Guide in the Docs folder?.
I may have put you crook with the pound variable number. See page 38 for what each variable is.
Craig
-
--touch button script
If (Tframe == nil) then
--touchoff module
package.loaded.mctouchoff = nil
mctouch = require "mctouchoff"
Tframe = mctouchoff.Dialog()
else
Tframe : show()
Tframe : Raise()
end
This is what I have ...
-
Hi,
look in Mach4Hobby/Modules for the file mcTouchOff.lua and you will find the code. It is unfortunately a biggish
file (292k) and so the chance of you spotting the fault is slim unless you are already good with Lua.
I suspect that you are putting in the wrong parameters into the probing routine.
Can you take a screen shot of the parameters you are loading?
Craig
-
I was trying to send you pictures..
But gives me error it says it's to large
-
Ok I found it..like to know where do I put it at...
-
Hi,
use a utility like Paint to resize the screen shot. Ideally you would post no file bigger than 500k.
Craig