Messages

4901

General Mach Discussion / Re: Quick tool change question :)

« on: November 03, 2011, 05:15:44 PM »

I don't think it will bypass the M6start it just waites for a MANUAL cycle start to run.

(;-) TP

4902

General Mach Discussion / Re: I can't get the G95 feedrate to work properly in Macro

« on: November 03, 2011, 12:51:07 PM »

It failed on the Gcode file call from your file. The problem is a Sync problem with CB and Gcode inside the macro .

To fix add in a wait state after the G95 call Forcing Mach3 to WAIT until it has completed the G95 call update. NOW you may have to add more or less wait states with YOUR system.  It seems to be CPU related as to the waits required.

IF it were my code I would use the WhileIsmoving() Wend after each Code"" line to make SURE it stays in sync.

THAT is why I recommended you use a Gcode SUB routine call. It does NOT have the sync problems, But some of the latest version did have a bug that created a loop in the subs. DOn't know if that ever got fixed.

'M975.m1s  Tapping Macro
'
'Set Editable Parameters in Main Program
'#1=0.36         (Set Thread Depth)
'#2=16.0         (Set Thread Pitch in Turns per Inch)
'#3=400         (Set RPM)
'#4=0.1      (Set Rapid Height)

'(Internal Parameters)

OrigFeed = GetOEMDRO(55)
CODE "#103=0.91"      'Underfeed, 0.91 -> 9 %
CODE "#104=[#103 * 1.0/#2]"  'feed rate adjusted for under feed

CODE "G95 F#104"
While Ismoving()
Wend
CODE "S#3 M3 M8"
CODE "G4 P4"
CODE "G1 Z[#103 * #1/-1]"
CODE "S#3 M4"
CODE "G4 P0.5"
CODE "G1 Z#4"
CODE "G94"
CODE "F" & OrigFeed

4903

General Mach Discussion / Re: I can't get the G95 feedrate to work properly in Macro

« on: November 03, 2011, 12:42:33 PM »

I was running your code I will test with your Gcode program call.

(;-) TP

4904

General Mach Discussion / Re: I can't get the G95 feedrate to work properly in Macro

« on: November 03, 2011, 11:54:53 AM »

I have run it 10 ways to sundays here and it works fine every time.

What version of mach3 are you running?

If you look in the mode line does it show switching to G95??

Are you sure you have your #vars set before you run the Macro?

(;-) TP

4905

G-Code, CAD, and CAM discussions / Re: g-code from a spread sheet ?

« on: November 02, 2011, 07:48:52 PM »

I would ask Les over at SheetCam to write a post to do the cranks. Just draw the offset pins  and let Scam do the math AND the gcode(;-).

He did helps us with a Camshaft Grinding post. Draw the lobe and time the lobe then Scam did the rest.  

Somewhere I do have a MACRO that can generate the Crankshaft math and then WRITE the gcode file.

You can do the Gcode MATH with spreadsheets and then export it out as a text file.

(;-) TP

4906

General Mach Discussion / Re: Dynamic Steps per Unit for fast rapids

« on: November 02, 2011, 07:23:05 PM »

The moment  you tried to dynamically change the steps per MACH would loose track of position as it depends on the MATH to keep track of position. From that point there is no going BACK (;-).

Then you have the problem CAN the motors even RUN that fast(;-)accurately AND the acell settings problems(;-)

The several times we have tried something LIKE that we had to refhome the machine before continuing as at that point MACH was lost.



BUT give it a whirl and see what you getts, (;-) TP

4907

General Mach Discussion / Re: Dynamic Steps per Unit for fast rapids

« on: November 02, 2011, 06:31:59 PM »

2nd question would be WHY(;-) If you spend that much time in rapid then I would think you might want to fix that part first(;-)

If servo driven first plan only the #steps to meet accuarcy levels then the rapids would take care of themselves.

No point in having .00001 steps for .001 accuracy then complain about slow rapids. Not picking on you just an example.

For your example How would you control accuracy when you changed the steps(;-) The steps per are to MAKE the machine move the distance correctly.

If you change those midstream then MACH would be lost as to where it actually was and could NEVER return to a know point.

Just a thought, or three (;-) TP

4908

General Mach Discussion / Re: I can't get the G95 feedrate to work properly in Macro

« on: November 02, 2011, 02:13:21 PM »

The macro may be outrunning the Gcode side. You may have to add wait states to keep things in sync between the CB side and the Gcode side.

'M975.m1s  Tapping Macro
'
'Set Editable Parameters in Main Program
'#1=0.36         (Set Thread Depth)
'#2=16.0         (Set Thread Pitch in Turns per Inch)
'#3=400         (Set RPM)
'#4=0.1      (Set Rapid Height)

'(Internal Parameters)

OrigFeed = GetOEMDRO(55)
CODE "#103=0.91"      'Underfeed, 0.91 -> 9 %
CODE "#104=[#103 * 1.0/#2]"  'feed rate adjusted for under feed

CODE "G95 F#104"
While Ismoving()
Wend
CODE "S#3 M3 M8"
CODE "G4 P4"
CODE "G1 Z[#103 * #1/-1]"
While Ismoving()
Wend
CODE "S#3 M4"
CODE "G4 P0.5"
CODE "G1 Z#4"
While Ismoving()
Wend
CODE "G94"
CODE "F" & OrigFeed

(;-) TP

4909

General Mach Discussion / Re: G84 SRT

« on: November 02, 2011, 01:48:24 PM »

The G84 is correct for what it is (rigid tapping). IF you are using it with a floating tap holder then you must allow for the transition of the spindle from Cw to CCw. That way when the tap gets back to the top it does NOT have any spring load to it.(not always possible)


Also do not use it IF you are using spindle sync as the sync part is broken in mill ( last I used it) Turn OFF spindle sync and use the programed S speed.

IF you are doing tapping in MAch3 I would just setup a Tapping Sub and use variables to program it.  Works Everytime and you can specify feed and retract to account for the dwell.

(;-) TP

4910

General Mach Discussion / Re: I can't get the G95 feedrate to work properly in Macro

« on: November 02, 2011, 01:40:24 PM »

COde looks ok here . HOW have you got your Spindle setup? do you have an index to show true RPM,  do you have the spindle synced to feedrate?

(;-) TP