Welcome, Guest. Please login or register.
Did you miss your activation email?
October 18, 2017, 06:55:57 PM

Login with username, password and session length
Search:     Advanced search
* Home Help Search Calendar Links Login Register
  Show Posts
Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 »
1  Tangent Corner / Tangent Corner / Re: QR Codes. on: July 07, 2017, 07:36:38 AM
I sent it to my Dropbox folder as a text file and it worked fine, no formatting issues at all.
have to think it's an issue in the mail transfer/conversion.
2  Tangent Corner / Tangent Corner / Re: QR Codes. on: July 07, 2017, 06:45:58 AM
cool idea Undecided

did notice on sending an email from my phone to myself it did not format cr/lf
have to do some additional testing but it does have possibilities.
but i am  rookie at these smartphones just bought my first phone a CAT S60 so still learning.
3  Mach Discussion / Mach4 General Discussion / Re: Integers defined on: June 06, 2017, 04:07:38 PM
unless you set your variable X_Axis=0 then your variable X_Axis will equal "Nil"

the integer value are shown in () for each axis
4  Mach Discussion / Mach4 General Discussion / Re: How to Emulate a Momentary switch? on: June 04, 2017, 05:24:01 PM
Here is another idea, using the millisecond #3001 variable
just need to add output condition
as I am just showing the time value in the history.
can be set to any time and all jogging or other functions are still active
with some additional coding should be able to use these functions for other timers

Code:
--add to PLC Script
function Timer(varnum)
    local inst = mc.mcGetInstance() -- Get the current instance
    varvalue1 = mc.mcCntlGetPoundVar(inst, varnum); -- Get MiliSecond Time
    return varvalue1
end
function TimedOut(varnum,varvalue,ontime)
    local inst = mc.mcGetInstance() -- Get the current instance
    varvalue2 = mc.mcCntlGetPoundVar(inst, varnum); -- Get MiliSecond Time again
    increment=(varvalue2-varvalue) -- current milisecond increment
    if (varvalue2>(varvalue+ontime)) then
        timerupFlag=0 -- be sure to set this global variable flag set in screen load cript
        mc.mcCntlSetLastError(inst, "Times Up "..tostring(increment))
    else
        timerupFlag=1
    end
    return increment
end
if (timerupFlag==1) then
    increment = TimedOut(milisecondVar,varvalue1,ontime)
end


-- Add to Left up Button Script
timerupFlag=1 -- set global that timer routine is in use
milisecondVar=3001 --the Milisecond # Register
ontime=5000 -- miliseconds on time so its 5 seconds minimum
valvalue1 = Timer(milisecondVar) --set start time
5  Mach Discussion / Mach4 General Discussion / Re: Cutter height advancement problem on: May 08, 2017, 01:37:44 PM
You might be better off learning about G50 and work offset shifts
Increment the whole work offset Z #variable position.

Screw around with tool length offsets is subject to a whole new set of "what the hell happened there"
You might beable to write to the tool length variable then call it with an H offset but resetting it and knowing where your at any one time is going to be suspect too.

Being new to this  I advise to learn the basic before you crash, burn then  Cry
6  Mach Discussion / Mach4 General Discussion / Re: Cutter height advancement problem on: May 08, 2017, 09:10:50 AM
you would have to increment all your Z's to move down the same amount, correct?
#103=0 (make sure this is done too in the main)
#103=[#103-#100] (add a step down just for the arcs)
example Z[1.545902+#103]
thou I have to admit I don't remember creating 3d arcs like your trying
but if it runs your one loop fine now, then I see no reason that adding the step down should not work.

your original code;
G91 Z-0.001                     (step down 0.001 per pass)
G00 X0.250409 Z1.500977 "This is an incremental move too, but to where Huh?? from where Huh??"
G90 "set it back to absolute moves"

I thought your original start depth was Z1.500977 now its 0
but admit I did not look close and notice that was an incremental position from who knows where, as there was no reference position move before it.
So not sure wtf your up too really or where your starting at.
Scary code, as your original code started, going vertical then step back down.
Re-think your approach
always look one line at a time and say to yourself "from where I'm at, what setting & position do I need to get me to the place I want to be next"
7  Mach Discussion / Mach4 General Discussion / Re: Cutter height advancement problem on: May 05, 2017, 05:27:47 PM
wefinish
you have a good start, you just need to learn to use pound variables to increment the steps down

here is an example of one I posted years ago of how to increment.
http://www.machsupport.com/forum/index.php/topic,16372.msg147299.html#msg147299

all my gcode other than some profiles and 3d contours are all variable based
as most routines are repetitions of whittling away material. (really sweet for lathe routines, turning  facing, threading)
cleaner shorter code and easier for me to write and edit for the next similar routine.
so the path "like you have" is a call with M98 from the main routine and the first thing it does is add the step increment down variable for the Z position variable
ever time it re-enters the loop it computes the new Z depth variable.
just remember to set the Z increment position variable to zero before calling the loop

good luck have fun

8  Mach Discussion / General Mach Discussion / Re: ISO, BT, NT Taper angle on: January 08, 2017, 11:10:09 AM
Your welcome

did find this info that might verify for you:

http://www.practicalmachinist.com/vb/general/what-angle-bt40-taper-272649/

Good luck Have Fun
9  Mach Discussion / General Mach Discussion / Re: ISO, BT, NT Taper angle on: January 08, 2017, 08:59:13 AM
 Wink  I just had to machine some grinder spindle hubs over the holidays. So I wrote a program (using Arts Gearotic/Auggie/Monkey C code) to help me understand the start and stop points for my lathe

Interested to see if these are correct for you; I used the major OD dimension and a length of a holder I'd found on the net.
24/7 = 12/3.5 = 3.5" per foot

I'd verified my grinder spindle taper dimensions with autocad.
the trick to my programming was to remember the taper is included angle not a right triangle. So the calculations had to take that into account.

I modified a Bridgeport spindle a few years ago with my tool post grinder on a manual lathe, still works great for my needs. Now handles both R8 and Cat30 collets.
10  G-Code, CAD, and CAM / G-Code, CAD, and CAM discussions / Re: Trispokedovetiles: CNC code to cut tiles on: December 28, 2016, 08:10:01 AM
I did a quick test in Auggie's Simulator to see if it would run.

notice I removed the start and stop of the laser control as Auggie takes care of it with movement.

Does need a provision for adding Mcodes for my Air Blow On/Off Mcodes M103/M104

be an added bonus if it recognized "\n" the end of line command, so we could input multiple commands example: M104\n%

Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 »
Powered by MySQL Powered by PHP Powered by SMF 1.1.20 | SMF © 2013, Simple Machines Valid XHTML 1.0! Valid CSS!