Hello Guest it is March 28, 2024, 05:33:18 PM

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Ya-Nvr-No

351
Mach4 General Discussion / Re: Creating a Probe File
« on: May 19, 2014, 04:24:23 PM »
 ???
have no idea what your referring too
here is a snippet of the probing code
you sure your not sniffin flux?  :-X
that code you posted has to do with reading and writing to registers.
that's what I used for the wizzard I created
I think I kind of mixed you up when I answered Gerrys question when it really had nothing to do with the probing routine. Sorry

g61
#98 = 50 (rough probe speed)
#97 = 5 (fine probe speed)
g91
g01 z0.0
g31 y-1 f#98
g01 y.1
g31 y-.2 f#97 (Get the -Y Pos)
#102 = #5062
g0 y.1
g31 y2 f#98
g01 y-.1
g31 y.2 f#97 (Get the +Y Pos)
#103 = #5062
#104 = [#102 + [#103-#102]/2]
g90 g0 Y#104


352
Mach4 General Discussion / Re: Creating a Probe File
« on: May 19, 2014, 02:36:59 PM »
you dont have to script a thing I just did it to create a text file of the probed points
I'm looking at it for a future point cloud scanning routine.

that's what the probing routine was all Gcode, then I ran it as a regular program. Do believe that the button script can call the gcode file, load it, run it and move the machine to where you want to be left at and then have it set the DRO's to whatever you programmed in the code for it to be. So on a hole it might be centered 1" above the face of the part (X0Y0Z1) all done with variables.

353
Mach4 General Discussion / Re: Creating a Probe File
« on: May 19, 2014, 11:47:57 AM »
Also tested the Probe file creation file I posted above with the Signal Script in the Load Screen Script section. Added a block of code for input13, then in mach turned on the input 13 and associated to the probe input. When it was tripped it created the file and added the data. So straight forward and easy to make happen. Just takes awhile to wrap your head around the new capabilities of Mach4 :-\
Spent a lot of time throwing rocks as Terry says.

354
Mach4 General Discussion / Re: Creating a Probe File
« on: May 19, 2014, 10:59:38 AM »
Just tested Probing... Worked better than expected.
I created a Button and then when pushed it called a probing.tap file that I ran with cycle start.
Did as it was coded and was fast
no more "isMoving", all seemed to get handled in the G31 move.
Liking/Lovin it  ;D



355
Mach4 General Discussion / Re: Mach4 Printer Port Discussions
« on: May 19, 2014, 10:53:07 AM »
I just tested the Probing in Darwin and it works sweet, and so fast. ;D
I'm Happy to say it was so easy to setup and get working.
Great job guys.

356
Show"N"Tell ( Your Machines) / Re: Home Brew 5 Axis Milling Machine
« on: May 18, 2014, 06:53:55 PM »
looks to me based on your description in one of your videos you have XYZBC axis you stated AB might be why, what your seeing doesn't match what you think should be happening or you just misspoke the axis labels.

Looks to be moving smooth, have fun.

357
Mach4 General Discussion / Re: Variables reading and writing
« on: May 18, 2014, 06:19:08 PM »
Added a Feed Rate Over Ride DRO and took the view variables idea to the next step and put all values not equal to zero in a combobox

The update button is attempt to update the combo box, haven't quite got the handle on getting that to work as of yet.  :P

358
Mach4 General Discussion / Re: Variables reading and writing
« on: May 18, 2014, 03:45:34 PM »
the list I got from Steve Murphree

the script was posted, not much to it. so ya don't need big rocks or many of them to paste the script in a button click.
You do have to set up the iRegs0 with the variable names, don't forget to restart Mach4 to initiate them.

http://www.machsupport.com/forum/index.php/topic,27256.msg192478.html#msg192478

359
Mach4 General Discussion / Re: Variables reading and writing
« on: May 18, 2014, 08:34:53 AM »
found this worked to 15000 for me (at least I did not get any messages, so assume it works)

    if (v1 < -1000000 or v1 > 1000000) then
        --filters out big numbers
    elseif v1 ~= 0 then
        l1output = string.format ("%5d = %0.6f \n",rowno,v1)  --formats registry var number for writing
        file:write(l1output)  --writes to file
    else
    end

Thanks Nick ya did good. nice to have new tools.  ;D

360
Mach4 General Discussion / Re: Creating a Probe File
« on: May 18, 2014, 08:07:38 AM »
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