Messages

1

General Mach Discussion / Re: program stops while cutting

« on: March 25, 2016, 12:15:32 AM »

Glad to hear it  thanks for replying

2

General Mach Discussion / Re: program stops while cutting

« on: March 24, 2016, 12:06:46 PM »

I'm surprised there's no reply here. 
I will chime in with limited value probably.

I have only had a shutdown like that once with the smooth stepper and it was my fault.  I accidentally allowed a powersaver mode to startup on the laptop.
I took a chance despite the Mach3 warning message and hit run after the pc was back online.  Tore a nice line before I could hit stop.  Never again.

I know this shutdown thing happens though it has not been a problem for me.
Thoughts:
1) No unnecessary software or programs to run on the Mach3 computer.  No firewall or antivirus on mine. NO POWER SAVE MODE.
2) rule out electrical interference (keep ethernet cable isolated). 
3) rule out poor cable connections or jiggle

Beyond that, I dunno....

Steve

3

General Mach Discussion / Re: Is Z zero supposed to be saved in a saved fixture?

« on: March 29, 2015, 07:51:16 PM »

This shows what happens when I import my g-code object with its 0,0,0 axis.  The object resides at the G54 location as it should but the purple crosshairs jump off the table.  Crosshairs can be returned to the origin of the object by zeroing the X and Y DRO's.  Is this normal behavior?

Thanks

4

General Mach Discussion / Is Z zero supposed to be saved in a saved fixture?

« on: March 29, 2015, 06:05:13 PM »

I have a fixture, the default G54 at the moment.
When I load my Gcode the object appears in Mach3's tableview window at G54's X0,Y0 (about mid table).
However, although I had previously zeroed Z (at table height), this data appears not to have been saved.
If I hit "GoToZero", the machine head will go to G54's X0,Y0 as expected.  However the Z axis will then drive for the floor!  Not pleasing.
I'm OK as long as I  zero Z manually before hitting "GoToZero"

Also perplexing to me (because I'm new at this): When I open the Gcode, although the object's imported 0,0,0 axis appears at the right place on the table (the last G54), the DRO's and the cross hairs are way out off the table.
What works is this: I zero Z manually, perform "GoToZero",  and then zero both X and Y (in the DRO's).  Then the crosshairs are right, I'm 0,0,0 and the program is a go.

I'm sure I'm missing something here....

Steve

5

G-Code, CAD, and CAM discussions / Re: tool library Mach3 vs CAM

« on: March 21, 2015, 02:33:16 AM »

Excellent. Thanks to all! I sort of imagined it must be that way but hadn't yet come across an explanation

6

G-Code, CAD, and CAM discussions / Re: tool library Mach3 vs CAM

« on: March 19, 2015, 12:39:33 AM »

Your reply is greatly appreciated.
I am likely being dense here.  The issue is that there are two distinct libraries that one can choose to deal with:

1) The library that is part of the CAM program (MadCam in this case) which can be constructed, modified, saved.
2) The library that can be constructed within Mach3 itself - you seem to be able to define any tool you want in Mach3 and give it a number that is it's identity within Mach3's own library.

So, when the G-code runs how does it know what tool #1 refers to?  Is it the tool that was labelled #1 in MadCam.  Or is it the tool labelled #1 in Mach3?

Steve

7

G-Code, CAD, and CAM discussions / tool library Mach3 vs CAM

« on: March 18, 2015, 05:39:44 PM »

I am obviously choosing a tool from MadCam's own tool library to generate my G-code.
This is imported and used in the running of Mach3's routine.
Is there any reason to enter a tool choice from the Mach3 library then? 

I assume that if you did change the tool number to one residing in Mach3 library that it would have to match exactly the tool used in MadCam to generate the toolpath?

Is there a possibility of "tool confusion" if there is a Tool #1 in Mach3 library and a Tool #1 that comes in with the CAM file (which might obviously be a DIFFERENT tool)

Steve