Messages

21

General Mach Discussion / Re: lathe spindle speed

« on: August 28, 2008, 08:31:37 PM »

Well I copied my lic file into the directory and low and behold, it works! Guess it's locked out in the demo version. Seems to have fixed my problem with rapiding thru the first two cuts after i rapid jog away or closer.   

Thanks again guys,
Mark

22

General Mach Discussion / Re: lathe spindle speed

« on: August 28, 2008, 05:02:27 PM »

I'll try copying my license when I get home. I installed the new in a separate directory to not overwrite the existing and copied the XML but didn't get the license. Maybe that'll do the trick.
I'll let you know

Thanks
Mark

23

General Mach Discussion / Re: lathe spindle speed

« on: August 28, 2008, 02:57:05 PM »

Thanks for taking a look at this, Hood. I realized awhile after I had posted last nite, that I should include the XML, but it was getting late 

Mark

24

General Mach Discussion / lathe spindle speed

« on: August 27, 2008, 09:18:44 PM »

Just upgraded to V3.041 cuz I was having some issues with the lockdown.
Using a G95 to calculate feedrate from spindle speed. Have an index to get RPM, but spindle is not controlled by Mach, I turn on and off and set the RPM.
Problem is it sets feedrate to COMMANDED instead of ACTUAL spindle speed. If there is no commanded RPM it gives an error of no RPM in G95 mode and rapids thru cut. If I command a RPM, it sets the FR and won't change it if I vary speed. It worked in the lockdown, usually; sometimes it would rapid thru 2 cuts if I had rapided tool away after setup. That's what I'm trying to get away from.
Using the same XML file as the lockdown. What do I need to change so it will use the actual RPM to set feedrate?

Thanks in advance

Mark

25

General Mach Discussion / Re: Cuts getting progressively deeper

« on: June 13, 2008, 06:55:00 PM »

Sounds like it's loosing steps on the way up.
I'd drop the speed down to half or so and also drop the acceleration too, just to see what happens. It'll take longer to cut, but it might get you through this job til you can talk to the manufacturer

Just thought of this: check the coupler too

Mark

26

General Mach Discussion / Re: How to use a simple offset

« on: June 04, 2008, 02:54:36 PM »

OK give this a try. It was late last night and I didn't think it out completly. xy & z need to return to starting point before looping thru

%
g0 x0 y0
m98 p1234 l35 (runs subprogram 35 times)
G90 (sets back to absolute mode as a safety thing)
m30

o1234
g0 g91 x-.074 y-3.518
g0 z-2.116
g1 x-2.35 z-2
g1 x-3.65
g1 x-5.89 z-2.116
g1 y-3.500
g1 x-3.65 z-2
g1 x-2.35
g1 x-.074 z-2.116
g0 Z10.348    (moves z back to where it started this toolpath)
x18.038 y7.018  (moves x & y back to where they started)
y-.1   (increments y-.1)
m99 (returns to main)
%

Mark

27

General Mach Discussion / Re: How to use a simple offset

« on: June 04, 2008, 08:45:58 AM »

you need the m99 after the end of the subprogram to return to the main. I still don't think it will work. Let me look at it again when I get to work.

Mark

28

General Mach Discussion / Re: How to use a simple offset

« on: June 03, 2008, 10:16:11 PM »

try this:
%
g0 x0 y0
m98 p1234 l35 (runs subprogram 35 times)
G90 (sets back to absolute mode as a safety thing)
m30

o1234
g0 g91 x-.074 y-3.518
g0 z-2.116
g1 x-2.35 z-2
g1 x-3.65
g1 x-5.89 z-2.116
g1 y-3.500
g1 x-3.65 z-2
g1 x-2.35
g1 x-.074 z-2.116
g90 z0 ( or above part, for safety)
g91 y.1   (sets to incremental mode and moves y +.1)
m99
%

HTH
Mark

Note: you don't need to put a g1 on each line. g1, g2, g3 and g0 are modal and stay in effect until replaced by one of the others in the group. I'm kinda lazy and try to find the easy way to do things

29

General Mach Discussion / Re: Well Blow my bugle.

« on: March 12, 2008, 11:15:30 PM »

 
I for one don't see what the problem is!

Mark

30

General Mach Discussion / Re: upgrade problems

« on: March 10, 2008, 11:39:32 PM »

Well, I got it to work without a lot of sweat. I did some looking around on this forum at lunch today at work and here's what I found will work in case anyone else has this problem.
I changed the tool change to Auto Tool Changer. Apparently this changes  the tool DRO to the commanded tool and nothing else. No movement even when the axes are moved away. This is what I wanted. After the M6 I have an M01. Then I touch off and set offset. Move Z up to a safe place and press Cycle Start. All is good
Also, not sure if this had anything to do with this, is I added a G43 to the initialization string.
The angular designation is probably better called "rotary" axes; A B and C rotate around the X Y & Z axes in the Fanuc world, which is where I reside, I'm a programmer by day.
Thank you for your ideas

Mark