Messages

121

VB and the development of wizards / Re: VB and variables in G code

« on: March 24, 2009, 06:18:08 PM »

OK, I see what you mean. I am cutting holes in a plastic box.
For multiple depths using this macro just feed down and call the macro as many times as needed.
I guess it wouldn't be to hard to modify the macro to increment Z down until #552 variable was reached and set #552 in the G-code.

122

VB and the development of wizards / Re: VB and variables in G code

« on: March 24, 2009, 01:32:25 PM »

What you have there is , it will go to X1Y1 then bore a hole striaght down to -.5 then try to cut the circle (;-) You might want to add in 2 more params.

Param1 sets #550 with Setvar(550,Param1)
#551 gets set with Code"#551=[#550/2]"
From there everything is in place to cut the circle. I am using it and it works great.

123

VB and the development of wizards / Re: Dedicated Mach variables

« on: March 23, 2009, 10:06:56 PM »

I finally found the table of Mach parameters again. It is in Mach3Mill_1.84.pdf section 10.
It lists numbers starting with 5161 = G28 home X and continues to 5326 = Work offset 6 C and then states
"And so on every 20 values until"  and then the chart continues with 10281 = Work offset 254 X until 10306 = Work offset 255 C.
Then the page ends with

"A Mach3 machining system maintains an array of 10,320 numerical parameters. Many of
them have specific uses. The parameter which are associated with fixtures are persistent
over time. Other parameters will be undefined when Mach3 is loaded. The parameters are
preserved when the interpreter is reset. The parameters with meanings defined by Mach3
are given in figure 10.1"

Does the last line mean that I am free to use any parameter NOT listed in figure 10.1?

124

VB and the development of wizards / Dedicated Mach variables

« on: March 22, 2009, 10:58:15 PM »

Some where I came across a table of Mach 3 variables that were in the 5000+ range. Where is it? Are these the only ones that I should not casually change?
When using #123=x.xx in G-code to set a variable what variable numbers are open to use and what numbers should not be used?

125

VB and the development of wizards / Re: VB and variables in G code

« on: March 22, 2009, 10:40:38 PM »

Here is the final version of my M79 hole boring macro.


'M79.m1s
Setvar(550,Param1)
Code"#551=[#550/2]"
Code"G90 G92 X0. Y0."
Code"G01 X[#551] Y[#551]"
Code"G03 X.0 Y[#550] I[-1* #551] J.0 G90"
Code"G03 X.0 Y[#550]I.0 J[-1*#550] G90"
Code"G03 X [-1*#551] Y[#551] I.0 J[-1*#551] G90"
Code"G01 G90 X.0 Y.0"
Code"G92.1"
End

and it will bore any size hole by calling it like this

G0G90X1.Y1. (Position to hole center)
G01Z-.5 F10. (feed to depth)
M79 P1.000
G0Z0

The macro feeds from the center, does a 90deg arc to a point tangent to the circle to be cut, runs a circle, does a 90deg arc toward the center and then feeds back to the center.

126

VB and the development of wizards / Re: VB syntax

« on: March 22, 2009, 04:21:03 PM »

Hi

You appear to be confusing integers with strings and are showing a integer value within string quotes
The below is not strictly necessary but clearly shows the difference between the 2 types of data you are combining.
(   Str() converts an integer to a String and Val() does the reverse  )

Dim V As Double
Dim s1 As String

V= GetVar (550)

s1 = "G90 G00 X" &Str(V) & " Y" &Str(V)

Code s1

regards

Melee

Actually, when I first set V with

V= GetVar (550)

I am implicitly declaring V as Double. The same is true when I then set V1 with

V1=[V/2]

because the value being set is Double.

127

VB and the development of wizards / Re: VB syntax

« on: March 22, 2009, 11:50:50 AM »

I think you may be missing the fact that

Code"#551=[#550/2]"

does set 551. In reality, I don't need

GetVar (550)

Variable 550 is set in the calling G-code and I could either set 551 as I am doing in the macro or with

#551=[#550/2]

in the G-code following the #550=  line.

128

VB and the development of wizards / Re: VB syntax

« on: March 21, 2009, 01:45:42 AM »

The idea for this bit of code came from Bridgeport's G79 boring cycle. I took your code above and changed it to this

'M79.m1s
GetVar (550)
Code"#551=[#550/2]"
Code"G90 G92 X0. Y0."
Code"G01 X[#551] Y[#551]"
Code"G03 X.0 Y[#550] I[-1* #551] J.0 G90"
Code"G03 X.0 Y[#550]I.0 J[-1*#550] G90"
Code"G03 X [-1*#551] Y[#551] I.0 J[-1*#551] G90"
Code"G01 G90 X.0 Y.0"
Code"G92.1"
End

and it will bore any size hole by calling it like this

G0G90X1.Y1. (Position to hole center)
G01Z-.5 F10. (feed to depth)
#550 = 1.    (radius of hole-radius of tool)
M79
G0Z0

I use this code to bore multiple holes of different sizes in an enclosure.

129

General Mach Discussion / Re: screen

« on: March 20, 2009, 09:10:19 PM »

Thank you, That works

130

General Mach Discussion / Re: screen

« on: March 20, 2009, 08:38:13 PM »

Well the use hot keys box is checked and if I un check it and then re check it I get a box that says Type the hot key now but when I hit the first number the box goes away an 99 is the new key code. This is on the G-code button next to the Reset button.