Messages

3211

General Mach Discussion / Re: Vise placement/reference?

« on: January 18, 2013, 12:26:11 PM »

Unless you have a fixture with a set reference point the point of origin for a part will always be a variable point depending on the part.

If you use your vise AND the part can always be placed at the edge of the fixed jaw(X Y intersection) then the origin can remain constant. BUT you will have to plan it that way in CAD/CAM as well.

It does NOT matter where the POO(point of origin) is as long as both CAM and Mach3 agree as to where it is to be.

Just a thought, (;-) TP

3212

General Mach Discussion / Re: Issues getting Mach3 to recognise my .tap files

« on: January 18, 2013, 10:59:16 AM »

Can you load the Roadrunner test file and it work?

Just a thought, (;-) TP

3213

Brains Development / Re: How are variables used in Brains - variable as Brain input locks up MACH

« on: January 18, 2013, 10:33:20 AM »

Dros  1000 - 1255    are tied to #vars 15000-15255.  BUT here is the dragon to deal with

You can use them from inside a GCODE program  as

#15000= 999 and it updates the DRO1000

Update the DRO1000 and it updates the #var 15000

From CB you have to use  Code" #15000=999"

BUT NONE of that works with SetVar() GetVar() from inside CB.

AS I understand Mach4, NONE of this will be in it including BRAINS. Mach4 will go to a ladder logic PLC type program  like other Controllers use.

Yes I know GGRRRRRRR, (;-) TP

3214

General Mach Discussion / Re: Issues getting Mach3 to recognise my .tap files

« on: January 18, 2013, 10:25:23 AM »

You may want to post a sample cut fie and a copy of you XML file so it can be checked.

Hopefully HOOD will see this and check the XML.

(;-) TP

3215

Brains Development / Re: How are variables used in Brains - variable as Brain input locks up MACH

« on: January 17, 2013, 05:36:05 PM »

Steve I don't know if this would help you but there ARE a block of VARs tied directly to a block of DROs. One updates the other.

Just a thought, (;-) TP

3216

Brains Development / Re: How are variables used in Brains - variable as Brain input locks up MACH

« on: January 17, 2013, 03:12:16 PM »

The var is there to hold values you need to hold locally inside the brain.

I agree and remember talking with Art about it  BUT the brains came at the END of Art's control over Mach3 and it is what it is Unfortunately.

Also you will find that not all things work as one would expect(;-)

As to Docs there is VERY little detailed info on the working of the brains. Just a couple of Vids and some user contributions.

(;-) TP

3217

General Mach Discussion / CNC study guide tutorial

« on: January 17, 2013, 02:23:34 PM »

If anyone needs a FREE cnc study /tutorial guide here is a Haas manual that does a very good job explaining most commands.

The Haas Gcode system  is very compatible with MACH3 . There are a few exceptions.


http://www.egr.unlv.edu/~kevinn/CNCworkbooks/MillProgrammingBook.pdf


(;-) TP

3218

General Mach Discussion / Re: Issues getting Mach3 to recognise my .tap files

« on: January 17, 2013, 12:06:23 PM »

 It appears that SheetCam did not post anything.

Have you tried loading a previous file ?

(;-) TP

3219

Brains Development / Re: How are variables used in Brains - variable as Brain input locks up MACH

« on: January 17, 2013, 11:26:24 AM »

The variables in Brains are unique to only brains. They are NOT the same thing as Gcode #Vars.

Just a thought, (;-) TP

3220

General Mach Discussion / Re: Help: M6 macro acts weird

« on: January 16, 2013, 11:45:19 PM »

ALSO you may want to try the routine from another macro outside of the M6 routine.

Create a new macro like this and see IF the output2 does the same thing

ActivateSignal(output2)       'activate clamp
Sleep(1000)                       'wait 1 sec
ActivateSignal(output1)       'Activate Cylinder
Sleep(1000)
DeactivateSignal(ouput1)     'Deactivate Cylinder
Sleep(3000)
DeactivateSignal(ouput2)        'Deactivate Clamp
End

(;-) TP