Messages

2031

Mach4 General Discussion / Re: Mach 4 Feature Request

« on: May 19, 2014, 10:47:33 PM »

"OK! It well be great if the machine side under Mach4 control is just suppose to follow the gcode BUT without pauses in motion when Mcodes does switching.
In Mach3 any M command will cause a pause in the motion if it comes in the cut path.
Now I'am  not using an M command. Necessary to me data I receive from Mach3 variables. But in Mach4 SDK I do not see any of these variables, and I'm interested in how to implement the desired function."

It just means you are using the wrong approach to have it work WITHOUT pauses.

(;-) TP

2032

Mach4 General Discussion / Re: Creating a Probe File

« on: May 19, 2014, 05:00:34 PM »

I am dragging out an old Mach3 PC and getting it ready for Darwin.  Hopefully THEN I can set up a manual switch to control the probe function.

I Don't think that probe emulation works in the SIM. Doesn't here.

(;-) TP

2033

Mach4 General Discussion / Re: Creating a Probe File

« on: May 19, 2014, 04:36:08 PM »

NO sniffing but I have been throwing rocks at LUA. The dust must be effecting my PEE BRAIN.   


OK but in the example you are not opening, writing to and closing the Points files. From your example I can assume that the Writing to the Trip point registers WORK in mach4 ?

#5061-#5066

When I try to OPEN a points file I get a Call " call name" <nil> error and that normally means there is NO such call AND I do not see that call in the list.

Nor do I see a #var for the trip condition, But I do see a signal call for the trip condition but you cannot use that in Gcode.

Probably best for me to WAIT for a working Mach4 instead OF THE demo(sim) VERSION.

(;-) TP

2034

Mach4 General Discussion / Re: Mach 4 Bug Reports

« on: May 19, 2014, 04:23:17 PM »

Sometimes running Gcode editor on a OPEN file it will CLOSE back down before you can select the file you want to work with.

(;-) TP

2035

Mach4 General Discussion / Re: Mach 4 Feature Request

« on: May 19, 2014, 04:20:30 PM »

I have seen it COMPILE OK  in the editor and error (Lua error running chunk) on load in mach4.   Can't explain it but i have seen it here.

Just a thought, (;-) TP

2036

Mach4 General Discussion / Re: Creating a Probe File

« on: May 19, 2014, 04:07:11 PM »

I forgot to add that Mach4 must update the #5061-5064 vars on trip.

2037

Mach4 General Discussion / Re: Mach 4 Feature Request

« on: May 19, 2014, 04:03:33 PM »

Sorry but you are wrong it is VERY easy for the CAM post to determine what you need and ADD a corrective Call AUTOMATICALLY based on conditions.

No hand coding needed or required.

IF you are required to hand code these things you may want to consider a NEW cam.  SheetCam does a wonderfull job in these areas.

(;-) TP

2038

Mach4 General Discussion / Re: Creating a Probe File

« on: May 19, 2014, 03:48:13 PM »

I use it like this:
first you have to create a reg variable name and know the path
then fill it with something

    local Xval = mc.mcAxisGetPos(inst,0);
    WriteReg("iRegs0/Xvalue", Xval);

then go get it with something like this

    local hXval = mc.mcRegGetHandle(inst, "iRegs0/Xvalue");
    local Xval = mc.mcRegGetValue(hXval);

so you would have to pass the trip points into a register then read the register

I am still lost Was THE ABOVE QUOTE  part of what you did to make it all work ??  


Something needs to OPEN the SavedPoints file (M40 #4000 =0) , ( AND it ALWAYS opens in a specific Directory, C:\\Mach4Hobby\\Points Files )

YOU need to see IF the probe tripped (#*********x = 0/1) to continue or error(#3000 = x , Probe reached Endpoint)

Something needs to write the Trip points to file (Mxx?) on demand
   OR automatically write to file on trip.  (For Example #4000 = 0 /Auto OFF   #4000 = 1 /Auto ON)

Something needs to CLOSE the SavedPoints file (M41)

2039

Mach4 General Discussion / Re: Mach 4 Feature Request

« on: May 19, 2014, 01:51:33 PM »

OH,OH I know that one well.

(;-) TP

2040

Mach4 General Discussion / Re: Creating a Probe File

« on: May 19, 2014, 01:50:12 PM »

Ok maybe I missed something but WHY  did you have to do ANYTHING scripting wise to make probing WORK in Darwin

All that code must be built into Mach4 not rely on scripting to make it work.

I am close to having a new 3d routine for probing Might need you to test it.  Hard to verify some of the moves without a moving  machine where probing works. It will be a G65 macro type function where you program in the #vars to program the function.  ALL in GCODE no scripting.

(;-) TP

(;-) TP