Messages

581

General Mach Discussion / Re: Custom plasma probing code?

« on: December 26, 2015, 12:02:14 PM »

One way around teh switch being effected by motion is to just use the solenoid to swing a transfer bar into play between the material and the switch. That way the switch never moves only the transfer bar does.

Also a way to keep more direct Gcode into play would be to use a SUB routine to hold the motion code for teh TOM routine and call it as a SUB (M98) . Subs are very stable in Mach3. You would store teh SUB in teh SUB directory and call it as needed .

(;-) TP

582

General Mach Discussion / Re: Custom plasma probing code?

« on: December 26, 2015, 11:50:50 AM »

OK from the top. IF you are to fire a solenoid to position a very sensitive switch to detect the metal surface (TOM)then the motion ACTION of the solenoid will more that like trip your sensitve switch(Been There).

It is NOT a good idea to use M7 M8 M9 as they are interrelated and if you turn on M8 then M7 and tried to ONLY turn off M7 with M9 you end up turning off M8 as well.

Yes it is BEST to do all the needed TOM (Top of Material) functions from a macro. There are several advantages on being you have all the needed code in 1 place and you can modify it once and it is a gobal update. Also RFH ( run from here) works very well as the motion Gcode G28.1 does NOT run from a macro when the RFH is called.  BUT sometimes Mach3 can pitch a witch with running Mcodes So it is all a tradeoff.

You may want to consider Ohmic touch off and use it with teh Z switch as a combined backup IF the ohmic misses then the Zswitch will kick in. OR in your case if you use the 30A consumables then it can simple run from the Zswitch .  OR you can use a combination of ALL that and still have your solenoid lower a probe tip for the ohmic side.

The ideal way would be to create a function to  minimize mixing Gcode and macro script in a macro. Do as much Motion in straight Gcode as you can and not have it run inside the macro.  YES that sounds mixed up as I say earlier that doing teh function is better from a Mcode BUT mach3 can be a funny bird sometimes (;-) It all depends

Yes it always a bad idea to call a macro from inside of another macro you can run into timing issue with Mach3. There is a WAY to run outside script code from inside of a macro that does not involve calling teh Mcode. It is only doable in the later versions of Mach3.  Check teh Mach3 CB programers manual for details.

NOW to add to the confusion The more that you hybridize the function the harder it is to deal with in the real world of program useage. You would never be able to share any of your Gcode OR use other's Gcode to run on your table.

I am willing to help you in any way I can so you can try all your options (;-)

(;-) TP

583

General Mach Discussion / Re: Limit switch issues

« on: December 26, 2015, 11:08:01 AM »

OK from what I see that you posted you have Zero CNC experience and Zero PC building experience and Zero PC usage experience to speak of. IF you had all that experience it would have taken you about 15 minutes to figure Mach3 out. 

You are simply here to get  the attention that you crave but are not getting elsewhere in life.

584

G-Code, CAD, and CAM discussions / Re: Edit post for xy position move then z

« on: December 25, 2015, 08:49:46 PM »

Artcam HAS a post configuration manual have you read it ??

(;-) TP

585

G-Code, CAD, and CAM discussions / Re: Edit post for xy position move then z

« on: December 25, 2015, 08:45:58 PM »

This is just a best guess , see what it does.


; Set up program header
;
START = "([FILENAME])"
START = "(Material Size) (X=[XSIZE], Y=[YSIZE], Z=[ZMATERIAL])"
START = "(Tool Number:[T]) ([TOOLDESC])"
START = "G90G80G20G49"
;START = "G0[ZH]"
;
; Program moves
;
FIRST_RAPID_RATE_MOVE  = "G0 [X] [Y] "
RAPID_RATE_MOVE  = "G0 [X] [Y] [Z]"
;
FIRST_FEED_RATE_MOVE   = "G1 [X] [Y] [Z] [F]"
FEED_RATE_MOVE         = "[X] [Y] [Z]"
;
FIRST_CW_ARC_MOVE      = "G2 [X] [Y] [J] [F]"
CW_ARC_MOVE            = "G2 [X] [Y] [J]"
;
FIRST_CCW_ARC_MOVE     = "G3 [X] [Y] [J] [F]"
CCW_ARC_MOVE           = "G3 [X] [Y] [J]"
;
NEW_SEGMENT_POST_TOOLCHANGE= "(Tool Number:[T]) ([TOOLDESC])"
NEW_SEGMENT_POST_TOOLCHANGE= "M3 [S)"
;
; End of file
;
END = "G0[ZH]"
END = "G0[XH][YH]"
END = "M30"
; M30 = program end and rewind

586

G-Code, CAD, and CAM discussions / Re: Edit post for xy position move then z

« on: December 25, 2015, 07:43:30 PM »

Are you SURE you want to do it that way ??. Normally you would want to FIRST move to Z rapid height THEN move in XY to teh start position then lower Z at feedrate to start.

That is what your first example is doing.

IF you first MOVE in XY without lifting Z to rapid clearnace you could easily tear something up if you hit something with teh tool. The Machine has NO idea where anything is so that is teh reason you would move it to a safeZ height BEFORE teh XY moves.

What Cam program is that ?  I can guess what to change but easier and safer to just look it up then you are sure.

Just a thought, (;-) TP

587

General Mach Discussion / Re: More inputs and outputs needed in Mach3

« on: December 25, 2015, 06:43:46 PM »

You also need to understand is the ESS has larger memory and I think A larger faster processor. THAT can make a BIG difference in what you can have programmed on the motion unit itself.  With an outside controller the controller has to be the Big Brain and do ALL of teh actual motion through pulsing ect AND do limits homing,probing. The PC just becomes the basic  planner.

Commercial CNCs have been using that scheme for decades Most also run Windows as the user interface and either use Ethernet or Fiber ethernet for teh Com link. Fiber link is also nothing new for CNC it has been around for a long time now and very stable. When the USB SS  was first being planned I talked to Greg about fiber link (;-). Other controllers had been using it for years even some DIY units.

The New UC400 ETH  from CNCdrives is reported to have a  large memory and a wickedly fast processor and ethernet with their OWN com protocol that makes the Com side almost real time in nature. Contrary to popular believe even real time controllers have a buffer (;-)

Also the old MsDOS 6.0  made a nice controller and it was real time as well.  There are STILL modern Commercial controllers that run MSdos as it's OS.

Just  a thought, (;-) TP

588

General Mach Discussion / Re: Limit switch issues

« on: December 25, 2015, 04:24:59 PM »

I think you hit the nail on the head when you said you had no idea of what you are doing and it does not seem that you want to make the effort to learn. Many thousands HAVE made the effort and now enjoy a really cool hobby.

Did you REALLY believe the sales hipe of plug in plug and professional sales people?  Here is a hint NOT everything on the internet is the truth. There are just as many shysters on it as there were 100 years ago in any other sales market.

AND Mach3 DOES have a recent file list (;-).

589

General Mach Discussion / Re: Limit switch issues

« on: December 25, 2015, 04:17:14 PM »

There is your answer get a makerbot that will solve all your problems (;-)

You are seriously WRONG about everything changing like you say Most have stayed within a very narrow margin of change FOR A GOOD REASON.

 (;-) So what do you think changed about printers in the last 20 years.  You plug them in load the driver and loade teh print cartridge and configure your program to use it load the right size paper and away you go.

There are Plugin in play Commercial CNC machines . Set them in place ,  load your tools and material , insert Gcode program and push teh Big green button and have at it. ALL the pre engineering and setup already done for you.

All you have to do is open your wallet then learn Cad and CAM and tooling and material applications (;-). There really is no escaping reality, try as you might.

590

General Mach Discussion / Re: G76 Lathe Theading Problem

« on: December 25, 2015, 03:45:48 PM »

Mach4 would definetly be a science project at this point. Do a simple search for the best ver for turn and threading it may NOT be V062 it is probably an older version.

(;-) TP