Messages

941

General Mach Discussion / Re: PART CNC PART MECHANICAL

« on: May 17, 2012, 12:13:10 PM »

Hood
xml attached
Spindle relays are enabled
Graham

Not according to your xml Graham...

Ian

942

General Mach Discussion / Re: Can you help me make 2 identical components in one sheet?

« on: May 17, 2012, 08:44:01 AM »

If you're using CAD/CAM surely you just copy and paste the part and generate the toolpath for both parts. (Sorry for calling you shirley )

Ian

943

General Mach Discussion / Re: m03 floating head programing

« on: May 17, 2012, 08:34:59 AM »

hIYA Ian I was just pulling your leg(;-).

I knew that  

The G28.1 method uses a % of rapid as defined in Config/homing. It IS adjustable.

In the SECOND stage yes - but the guide says the FIRST stage is done at FEEDRATE - which it isn't - it's done at 100% RAPID.

Also with the G28.1 function there IS a waypoint feature. With this you can direct the Z to move to the way point at rapid then finish the function at home speed.

That's what I'm saying

With Plasma you are rarely anywhere but a  0.100 " or so off the top of material at any time.

Well I'd say that depends on what you're cutting and how much it's warped/may warp upwards for whatever reason - but anyway let's say 0.1 is OK

So I just do

G28.1 Z.500   That sends the Z UP to .500 at rapid as a SAFEZ and then resumes the Home function at the preset speed I have defined.

I don't get this bit. If 0.1 is safely above the material why would you send it further up before coming down again - seems a complete waste of time to me with no benefit.

I use SafeZ as .500 as it is not safe to go zooming around the thin guage material as it warps and there may be kickups hidding that will tear the torch right off the head IF you are just skimming the top of the material.

Sorry if I'm being a bit slow but a minute back you seemed to be saying 0.1 was safe.

Ian

944

G-Code, CAD, and CAM discussions / Re: Subroutine for Raster Scan

« on: May 16, 2012, 11:50:54 AM »

Hi John

You're quite right Mach doesn't support selection but does support iteration. It does support macros but in a different context i.e. you can create your own M codes with CB (cypress basic). That said you don't need either for your task because Mach does support gcode subroutines.

a short example and I'll leave you to do the rest - hint - subs can be nested.

N10 #1000 = 10 (user gcode vars start at 1000)
N20 M98 P123 L#1000 (do sub called 123 L times)
N30 M30 (end of main)
o123 (start of sub - note that's an o not a zero and no line numbers allowed on sub labels)
N40 (do whatever)
N50 M99 (return from subroutine)

Ian

945

General Mach Discussion / Re: m03 floating head programing

« on: May 16, 2012, 08:58:54 AM »

Could the problem be associated with the G28.1 command?

Well I've just spent a while scoping G28.1's behaviour and I'm not sure if you'd call it a problem or just the way it is but G28.1 appears to behave a little weird depending on WHERE you start from,  where the commanded point is and where the switch is made ACTIVE. If you make sure the commanded point is always ABOVE where the switch will go ACTIVE then you're ok. Otherwise it can be - well let's say - "inconsistant". I can do the details if you want but generally if the switch goes ACTIVE at or above the commanded point then G28.1 behaves quite differently.

Another quick point: Just because the home LED is on doesn't mean your ACTUALLY "Torch on surface" - it may be slightly above it depending on HOW you homed.

@Terry - Hi Terry

I'm not disputing that wait states are sometimes required and that WHERE they're needed appears to be version and perhaps system hardware dependant. All I was saying above is that this was NOT the fundamental reason why the first code posted didn't work and also I stand by what I said that there is ZERO point in putting them after a FUNCTION call.

Ian

EDIT: Hmmmm - Seems G28.1 doesn't do what it says on the tin as far as the speed to the commanded point either. According to the blurb it travels at current feedrate - nope - it travels at rapid rate!

946

Modbus / Re: Arduino (UNO) ModBus and Mach3

« on: May 16, 2012, 04:50:48 AM »

Hi - There are NO bugs in Mach   

First - please confirm you've read the Mach3 section on downloads/Mach3 at the top of this page. In particular the bits about laptop, 32 bit windows etc. Then read the install/config guide in menu support/documentation/"Mach3Mill Install and Config Guide" - particularly section 2.2. and running the PP driver test. If you're still stumped then tell us about your system - PC, OS, Parallel port type etc.

Ian

947

Show"N"Tell ( What you have made with your CNC machine.) / Re: Constructing a Low Profile Tool Height Setter.

« on: May 15, 2012, 02:41:45 PM »

'tis not so much ball busting as banter - keeps us frosty 

948

Show"N"Tell ( What you have made with your CNC machine.) / Re: Constructing a Low Profile Tool Height Setter.

« on: May 15, 2012, 10:39:24 AM »

There's always photoshop - Doh! 

949

General Mach Discussion / Re: axis are stopping during cutting process?

« on: May 15, 2012, 10:35:01 AM »

What do you use OutPut2 for?
Hood

It swiches off automatic arc height control before leadout or in case it is better to cut in manual THC mode.

So you're getting dive at kerf crossing and/or slow down at leadout.

You should really use anti-dive but if you prefer to switch off THC then you can't do it with ANY macro without Mach stopping. It's not so much that a macro takes time to do what it does, it's because Mach's CV planner doesn't blend movement accross a macro call and therefore you get an exact stop between the two moves.

Do a search for the E1P0/E1P1 command family which were created for laser users but may help you.

Ian

950

Show"N"Tell ( What you have made with your CNC machine.) / Re: Constructing a Low Profile Tool Height Setter.

« on: May 15, 2012, 09:56:13 AM »

That's it Ian, give that Brit a challenge.

...you mean my FELLOW Brit... 

Ian