Messages

2961

Mach4 General Discussion / Re: last line not executing

« on: March 04, 2019, 02:19:15 PM »

Hi,
the message box only pops up if the mc.CntlGcodeExecuteWait() call FAILS. You wont see it if the call
progresses.

What's happening is the mcAxisHome() call is tying up the axis so the subsequent mcCntlGcodeExecuteWait() call
fails. We need to give some more thought to how to ensure that the X axis is homed before progressing.

I will give it some thought over the day and come back to you.

Craig

2962

Video P*r*o*b*i*n*g / Re: 3d Probing on Granite slabs

« on: March 03, 2019, 11:37:56 PM »

Hi,
the AXBB controller has just been released, I'm not sure that it has a Mach3 plugin yet.
Check with CNCDrive if it is your intention to use it with Mach.

The older UC100, UC300 and UC400 all do have a Mach3 plugin and so you could use either Mach OR UCCNC.

Craig

2963

Mach4 General Discussion / Re: Auto tool zero...Z-probing

« on: March 03, 2019, 11:26:01 PM »

Hi,
use a utility like Paint to resize the screen shot. Ideally you would post no file bigger than 500k.

Craig

2964

Mach4 General Discussion / Re: Lua Error Code on Start up

« on: March 03, 2019, 11:23:42 PM »

Hi,
did you create an individualized screen set?

Lets say that your machine requires a screen set with all the facilities of wx4.set say. What you would do is make a copy
of it and rename it to individualize it. Then you use that screen set and any edits, tweaks and additions get applied to it.

Should you create a fault in the screen set from which you cant recover you can load the standard wx4.set which should be
as shipped overwriting the faulty code.

It all depends on whether you created a separate screen set or not. If you didn't you'll have to download Mach4 anew to get a fresh
copy. It will overwite your previous and now faulty wx4.set

Craig

2965

Mach4 General Discussion / Re: Auto tool zero...Z-probing

« on: March 03, 2019, 11:07:59 PM »

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

2966

Mach4 General Discussion / Re: Lua Error Code on Start up

« on: March 03, 2019, 11:00:51 PM »

Hi,
do you recall what it was you edited that caused the fault? If you do there is a way to have Mach open directly
into the screen edit mode which would allow you to correct the mistake.

Does Mach open at all? If it does then go to the screen edit mode and fix it.

How many edits and tweaks have you applied to your screen set and does it have an individualized name?
If your screen set is not overly modified you could load a fresh copy of wx4.set, or whatever the basis of your
screen set is. That should restore it to standard.

I have tried editing the ScreenScript.lua but have had no success

The ScreenScrpit.lua is not editable. All the separate pieces of editable lua code get gathered together in one big
file, called the ScreenScript.lua. You can view it but not edit it. You must go to each of the different scripts that
make up the overall file if you wish to change something.

Craig

2967

Mach4 General Discussion / Re: Auto tool zero...Z-probing

« on: March 03, 2019, 10:49:56 PM »

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

2968

Mach4 General Discussion / Re: Auto tool zero...Z-probing

« on: March 03, 2019, 10:26:55 PM »

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

2969

Mach4 General Discussion / Re: Auto tool zero...Z-probing

« on: March 03, 2019, 08:54:08 PM »

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

2970

Video P*r*o*b*i*n*g / Re: 3d Probing on Granite slabs

« on: March 03, 2019, 08:25:20 PM »

Hi,
just about any decent external motion controller will offer four axes.

The UC***** series from CNCDrive  are required for UCCNC but are also applicable to Mach.

Craig