Hello Guest it is May 23, 2019, 11:51:16 PM

Author Topic: G31 issue  (Read 4670 times)

0 Members and 1 Guest are viewing this topic.

Re: G31 issue
« Reply #10 on: February 20, 2013, 01:04:02 PM »
Might try G28.1.  We didn't go that route originally because of G68 issues, but I understand that this has been corrected.

Offline BR549

*
  •  6,865 6,865
    • View Profile
Re: G31 issue
« Reply #11 on: February 20, 2013, 01:10:00 PM »
G31 from Gcode is very dependable.  From a macro NOT so much.

Problem NOW is you cannot RFH or reverse run with a G31 active in Gcode(;-).

You may want to give the G28.1 routine a try. So far it has never crashed  the plasma here AND it was fixed so you can run the G68 and use the G28.1.

SIGH, IF we only had conditional Gcode life would be much simpler that using CBmacros.

(;-) TP

Offline BR549

*
  •  6,865 6,865
    • View Profile
Re: G31 issue
« Reply #12 on: February 20, 2013, 01:14:35 PM »
When you went back to Gcode can you still do a RFH ?? or reverse run ?? 

Might want to give the G28.1 method a shot it has never crashed the plasma here .

(;-) TP
Re: G31 issue
« Reply #13 on: February 20, 2013, 08:53:02 PM »
No.  I didn't try RR but RFH fails when it does the simulation.  G28.1 seems to work with everything so I think that's the way I'll go.  I don't think we'll miss Z homing.  I'll just change the Ref All button to ref only the X and Y.
Re: G31 issue
« Reply #14 on: February 20, 2013, 09:06:47 PM »
Here's something a little wierd.  When I put the following code in a macropump, I can't scroll the code window.  Every time the code executes, the code window rewinds back to the top.  I tested by putting a sleep(5000) after the code and I could scroll for 5 seconds, but as soon at the code executed, it rewound to the top.

I ended up putting the code in a macro, then call the macro at the beginning of the program.

code "#1 =" & getUserDRO(1510)
code "#2 =" & getUserDRO(1508)
code "#3 =" & getUserDRO(1551)
code "#4 =" & getUserDRO(1520)
code "#5 =" & getUserDRO(1561)
code "#6 =" & getUserDRO(1570)
code "#7 =" & getOEMDRO(54)   
code "#8 =" & getUserDRO(1512)

Offline BR549

*
  •  6,865 6,865
    • View Profile
Re: G31 issue
« Reply #15 on: February 20, 2013, 09:28:43 PM »
OK you have me curious as to WHY all the parameters to do a simple TOM

Here I use

G31 Z-5 F20   ;Probe down or use G28.1)
G92 Z0          ;Set Z zero
G0 Z.110        ;Move up for switch allowance
G92 Z0           ;Set Z0 as T0M

In macro form the G28.1 behaves

Code" G28.1 Z.500 "   'Probe down
While Ismoving()
Wend
Code"G92 Z0"            'Set Z zero
Code"G0 Z.110"         'Move up for switch allowance
Code"G92 Z0"            'Set Z0 as T0M
While Ismoving()
Wend
End

With running the macro you can then run FRH.

Just a thought, (;-) TP
« Last Edit: February 20, 2013, 09:32:46 PM by BR549 »
Re: G31 issue
« Reply #16 on: February 20, 2013, 10:44:34 PM »
The parameters are not just for the TOM.  Only 3 of them are...Switch Offset, Pierce Height and Slow Zone.  The others are for feedrates, pierce delay and safe Z.  We make all of that available to the operator so it he wants to use a different material, all he has to do is change the cutting parameters on screen rather than generating a new program.  The only thing SheetCAM hard codes is the kerf width.  We could do that in Mach also, but then the operator would have to maintain a tool table.

I kind of like it all in Gcode.  RFH works fine with G28.1 in Gcode.  It seems to know not to "execute" the G28.1 when it does the simulation.