Messages

3661

General Mach Discussion / Re: Plasma Consumable Tracking

« on: November 05, 2012, 12:48:57 PM »

OK back to the G68 Coord Rotation Function. I had to break this back out to a 2 part function as the latest ver's do not like my ole SusWHileDo() routine that worked in older versions. AND yes I borrowed that idea "Thanks Stirling".

YOU CAN ONLY USE THIS FUNCTION if you use the G31 to run the TOM routine. The G28.1 version will not work.  Brian would have to fix the G28.1 function IF you had to have it that way.

Create 2 screen buttons Part1, Part2.

MOve to the 0,0 point then press the part1 button. Then move to a position on the rotated line you drew. Then press the 2nd button. It should calculate the require rotation angle AND apply it to the G68 and rotate the program for you.

You can then use the Preveiw function to verify it fits.

'Macro Plasma Coord Rotation G68
Dim X1 As Double
Dim X2 As Double
Dim Y1 As Double
Dim Y2 As Double
Dim XL As Double
Dim YL As Double
Dim CRA As Double
Dim RotAng As Double

DoButton(8)
While Ismoving()
Wend
DoButton(9)
While Ismoving()
Wend
X1= GetDro(0)
While Ismoving()
Wend
Y1= GetDro(1)
While Ismoving()
Wend
Setvar(301,X1)
SetVar(302,Y1)
Message"Move To 2nd refrence point and START Part2"
MsgBox "Move To 2nd refrence point and START Part2"
End



##################################################


'Macro For G68 Coord Rotation Part 2
X1= GetVar(301)
Y1=GetVAr(302)

X2= GetDro(0)
While Ismoving()
Wend
Y2= GetDro(1)
While Ismoving()
Wend
XL= (X1-X2)
YL= (Y1-Y2)
While Ismoving()
Wend
CRA= Atn(XL / Yl)
While Ismoving()
Wend
RotAng = ((CRA * 57.2957795)* -1)
MsgBox "Rotation Angle: " & RotAng
Code"G68 X0Y0 R"& RotAng
While Ismoving()
Wend
DoOEMButton(160)
While Ismoving()
Wend
MsgBox "Rotation Complete"
End

3662

Tangent Corner / Re: Spindle drive options "REQUEST"

« on: November 05, 2012, 11:18:24 AM »

(;-)  THose are FAMOUS last words.

The tech replied would "most likely" work fine .

By the time you buy the VFD, Load resistor bank, VFD rated motor you are getting closer to a servodrive/motor in cost.

WE KNOW the servo drive/motor works(;-).

Just a thought, (;-) TP

3663

Tangent Corner / Re: Flatbed scanner that doesn't stretch or skew?

« on: November 05, 2012, 11:11:27 AM »

I have had the best luck with EPSON scanners. IS there something common I can scan for you and send you the image for testing . That way you know for sure if it works for you.

Just a thought, (;-) TP

3664

VB and the development of wizards / Re: Numberpad function problem

« on: November 05, 2012, 09:11:54 AM »

I don't have a thing to do with fixing it. I just use it from time to time.

(;-) TP

3665

G-Code, CAD, and CAM discussions / Re: Digitizer output comand?

« on: November 04, 2012, 10:12:57 PM »

Not sure exactly what you need . If you explain your process maybe I can help.

(;-) TP

3666

General Mach Discussion / Re: Plasma Consumable Tracking

« on: November 04, 2012, 09:56:17 PM »

GL you are correct I keep in my head that I use the Max-Min to get size because some of our work 0,0 is not the Lower right but may be center of work then we have to work in all quadrants x+ x- y+ y-  . SOmetimes I gets cornfused. Tha is why we do the double check with Scam AND Mach3 sizes.

(;-) TP

3667

General Mach Discussion / Re: Mach3 and Tapmatic Tapping Head

« on: November 04, 2012, 09:38:58 PM »

IF you are doing small blind holes then Spiral points  are NOT the tap you want. They push the chips ahead of the tap. Use a std or bottom tap and the H factor you need for thread spec.

You are a brave soul learning with M2-3 taps (;-) BUT a thread is a thread by any name or size. 

(;-) TP

3668

General Mach Discussion / Re: Plasma Consumable Tracking

« on: November 04, 2012, 09:13:41 PM »

While Ismoving()  is not just for when Mach3 is physically moving . It is IF mach3 is doing anything other than idleing. 

Used after a SetDro() call makes MACH3 wait until after it does the update to carry on with the script.  SOmetimes without it mach3 will hop right over a group of code.

Best to make it wait than let it have free run without thread sync. AND sometimes even that does not stop it.

The point I was trying to make about the extents IS the putor does not know what axis I am going to choose to master the scaling by. 

(;-) TP

(;-) TP

3669

General Mach Discussion / Re: Plasma Consumable Tracking

« on: November 04, 2012, 07:23:49 PM »

You are doing VERY well, (;-) TP

3670

General Mach Discussion / Re: Plasma Consumable Tracking

« on: November 04, 2012, 06:40:58 PM »

THought that too at first BUT IF the OP did not set 0,0 then the extents can be WAY OFF from what it really is.

IF you load a program and the table is at say X30Y50 MACHs calculation of extents includes the amount it is off from 0,0.

I forget that on my main screen there is a PART size DRO that tells the size of X and the size of Y of the part based on extents BUT that depends on the Machine setting at 0,0 to be accurate, ALSO I have in the Gcode comments the Part size from Scam. IF the 2 do not jive +/- then something is wrong. Normally the machine is not at 0,0.

Then I can look at the sizes and deside which axis is the master to control the scaling as BOTH axis have to be scale the same amount to maintain the same aspect ratio AND if you try to do only one MACH3 will error out on Circles as it would produce an elispe and MACH3 will not allow that with scaling. AND it shouldn't.

AND remember that YOU decide which axis is the master for scaling. Could be X OR it could be Y. Just depends on what you need it to do.

(;-) TP