Messages

2241

Mach4 General Discussion / Mach4 Probing and reporting

« on: May 02, 2014, 10:58:58 PM »

HIYA Brian,

 I see from the probing notes you included that when a Probe file is OPEN and the G31 reaches the end point without tripping that it WRITES the endpoint values to file.

Could we PLEASE have it so that instead of writing the endpoints it writes an error code for each axis to the file. IF it reaches the endpoint then it IS an error probing wise. AS it is there is virtually no way to find the missed points in a 3d probe file.

Also could you please make that error show up as an LED flashing. It means 1 of 2 things the programming is OFF and it is missing things OR the probe TIP is broken

This was a big problem in MACH3.

(;-) TP

2242

G-Code, CAD, and CAM discussions / Re: Display a variable on the status line

« on: May 02, 2014, 09:10:07 PM »

The problem with the DRO is that is you MUST put a G4P0 at the end of the looped code. Otherwise mach3 cycles all the loop numbers and you never get to see them process.

You can add code to the Macropump that will UPdate the message line BUT it overwrite all your status and comment messages from Gcode.

You can do as YANVR said and use a the (222) dro to display the count, don;t forget the G4p0.

You can add code to the macropump to update a new USER message line or DRO from the #vars Update count.

You can even make it show it count UP and/or  Count down.

(;-) TP

2243

Mach4 General Discussion / Re: Mill GCode Manual G12-G13

« on: May 02, 2014, 08:59:29 PM »

HIYA RUSS the NEW g12/13 is very different from the OLD G12/13  The old one was the oddball. The new one seems to use I with J to set the starting point . A start point in deg offset from zero is the preferred way to do that, a lot easier on the old brain

IF you want to see a GOOD G12/13 look at the Haas version. It is top notch.

(;-0 TP

2244

Mach4 General Discussion / Re: Comments about Mach4 in Demo

« on: May 02, 2014, 08:21:56 PM »

HIYA Steve you ask for a program that shows the A axis creep. This one does here. It gets to the G65 call then stalls and the A axis SLOWLY creeps towards the "A" value in the call. If you wait until it gets there THEN the program continues. IF you set the A value to ZERO then it does not stall. IF you PRESET the A dro to the" A "value it does not stall.

(;-)TP


O0008 (Main program)
    N005 G54 G90 S800 M03 T02 F100(Select coordinate system, absolute mode, start spindle, get next tool ready)
    N010 G00 X3.0 Y2.5 (Rapid to center of bolt hole pattern)
    N015 G43 H01 Z.1 (Instate tool length compensation, rapid up to workpiece)
    N020 G65 P1008 X3.0 Y2.5 Z0 R1.75 D0.75 A45.0 H8.0 C81. F50 (Machine entire bolt hole pattern with drilling cycle)
M30


    O1008 (Custom macro to machine bolt hole circle)
    #101=1 (Initialize counter)
    #102=#1 (Initialize current angle to A)
    #103=360 / #11 (Constant for incremental angular distance between holes)
    #104=#26 + 0.1 (Constant for rapid approach plane)
    #105=#26 - #7 (Constant for Z bottom position of hole)
    N1 IF [#101 GT #11] GOTO 99 (Test if loop is finished)
    #110=#24 + COS[#102] * #18 (Calculate X position for current hole based on current angle)
    #111=#25 + SIN[#102] * #18 (Calculate Y position for current hole based on current angle)
    G#3 X#110 Y#111 R#104 Z#105 F#9 (Machine current hole)
    G80 (Cancel cycle)
    #101=#101 + 1 (Step counter)
    #102=#102 + #103 (Step current angle)
    GOTO 1 (Go back to test at loop beginning)
    N099
 M99 (End of custom macro)
 %
 

2245

Mach4 General Discussion / Re: Comments about Mach4 in Demo

« on: May 02, 2014, 07:59:52 PM »

HIYA steve, Here is a macro example. 3 problems popped up.

1. When I try to single step through the program and it gets to a GOTO call lets say GOTO5. It jumps to the line AFTER the N5 line NOT to it.

2. Every time it runs  the macro STALLS at the Tool change call  and does not proceed you have to hit STOP.

3 Sometimes at the G43 call it stalls as well.

I have not gotten to verifying IF the G65 parameters are compatible with Mach4 I had problems in single step mode.


 O0001 (Main program)

(Machine hole)

N075  (1.0 END MILL)
N080 G54 G90 S1200 M03 T05 (Start spindle)
N085 G00 X2.5 Y2.0 (Rapid to hole-center)
N090 G43 H04 Z0.1 (Rapid approach in Z)
N095 M08 (Turn on coolant)
N100 G65 P1000 X2.5 Y2.0 D3.0 R0.1 Z-1.0 A1.25 T1.0 F5.0 H1.0
(Mill circle)
N105 G91 G28 Z0 M19 (Return to tool change position)
N110 M01 (Optional stop)

(Program continues)

N200 M30 (End of main program)



o1000 (Circle milling custom macro)
(TEST FOR MISSING ARGUMENTS)
N1 IF [#24 EQ #0] GOTO 95 (X)
IF [#25 EQ #0] GOTO 95 (Y)
IF [#26 EQ #0] GOTO 95 (Z)
IF [#18 EQ #0] GOTO 95 (R)
IF [#7 EQ #0] GOTO 95 (D)
IF [#20 EQ #0] GOTO 95 (T)
IF [#9 EQ #0] GOTO 95 (F)
IF [#1 EQ #0] GOTO 95 (A)
IF[#11 EQ #0] GOTO 95 (H)
(A MUST BE BIGGER THAN HALF OF T)
IF [#1 GT [#20/2 +0.1]] GOTO 2
#3000=101(APPROACH RADIUS TOO SMALL)
(RAPID TO APPROACH POSITION)
N2 G00 X#24 Y#25]
Z#18

(TEST FOR HOLE IN CENTER)
IF[#11 EQ 1.0] GOTO 5
G01 Z#26 F#9
GOTO 6
N5 G01 Z#26 F[#9 * 5]

(MOTIONS TO MILL CIRCLE)
N6 G01 Y[#25 + #7/2 - #1] F#9
X[#24 - #1 + #20/2]
G02 X#24 Y[#25 + #7/2 - #20/2] R[#1 - #20/2]
J-[#7/2 - #20/2]
X[#24 + #1 - #20/2] Y[#25 + #7/2 -#1] R[#1 - #20/2]
G00 Z#26
X#24 Y#25
GOTO 99
N95 #3000=100 (INPUT VALUE MISSING)
N99 M99 (End of custom macro)

2246

Mach4 General Discussion / Re: Mill GCode Manual G12-G13

« on: May 02, 2014, 06:28:35 PM »

HIYA Russ I was just testing the G12/13  There seemed to be some quirks (;-)  I am not sure of the J parameter. Also not sure why the Start point for a pocket unless it includes Circular slots BUT then you have no control for Z if you are trying to that.

I would SEEM that the Z should be controlled from inside the G12 call otherwise you cannot cut a start circle without plowing through the interior material.

Also would be nice to have a Z stepdown. In the Fanuc world one normally uses the Circle pocket macro as I don't not recall a G12/13.

Just a Thought, (;-) TP

2247

G-Code, CAD, and CAM discussions / Re: Display a variable on the status line

« on: May 02, 2014, 03:56:29 PM »

Please explain what ,when, from where, and why you need to do this. Then perhaps we can help you work it out. It all depends.

(;-) TP

2248

Mach4 General Discussion / Re: Comments about Mach4 in Demo

« on: May 02, 2014, 10:56:54 AM »

HIYA Brian a while back we talked about in Mach4 that it "could" display the #vars as real numbers in the Gcode window as the program ran. Did this make it into Mach4 ??

(;-) TP

2249

Mach4 General Discussion / Re: Comments about Mach4 in Demo

« on: May 01, 2014, 09:57:09 PM »

Hiya Steve I found the reason for the "Cannot load file at this time" error.

I was using single block mode and Mach 4  does not load IF it cannot run the postcheck on the Gcode.  A better Error message maybe ??

By the way the LEDS on the screens do not work, I cannot telll IF Single block mode is on or off.

(;-) TP

2250

Mach4 General Discussion / Re: Comments about Mach4 in Demo

« on: May 01, 2014, 09:35:24 PM »

hIYA Brian I cannot find an example of arcs in G16 can you give a simple example of how it would be used or called ??

Thanks (;-) TP