Messages

1731

General Mach Discussion / Re: What is the latest Mach3 ver. known to have probing working?

« on: December 21, 2014, 04:34:40 PM »

OK when using a SS the SS is what will control probing IT IS a different ballgame.

" probing a feed screw with an alternating lead "

To use a sub just calculate the distance and divide the pitch for the number of total turns then add a couple for good measure. I am still not real clear on what you are doing. Are you trying to map the screw ?

(;-) TP

1732

General Mach Discussion / Re: Why does my slave axis do this?

« on: December 20, 2014, 09:44:33 PM »

I see over at the Zone,  GERRY explains how to fix the problem. You have to change out the button code to do a RefCombination() THAT will home BOTH axis at the same time.

(;-) TP

1733

General Mach Discussion / Re: Why does my slave axis do this?

« on: December 20, 2014, 09:41:08 PM »

In the vid the Axis moves until it binds up and stalls the stepper. When the stepper is stalled it has no torque and the axis SPRINGS back . Once it is back in position it regains the torque and tries to complete the move to the switch . IT will just repeat the process over and over again until you stop it.

(;-) TP

1734

General Mach Discussion / Re: Why does my slave axis do this?

« on: December 20, 2014, 09:25:02 PM »

IF you mean the REF ALL Home button then THAT will not work it will do exactly as you see in the vid. It is trying to HOME each axis independantly  won't work with a slaved axis.

You may want to try RefCombination() as that will attempt to home BOTH axis at the same time. NOW that will also require that you have separate HOME switches for each axis (Master Slave) .

(;-) TP

1735

General Mach Discussion / Re: Why does my slave axis do this?

« on: December 20, 2014, 09:09:57 PM »

What code are you using to HOME square the Axis and slave at the same time.  IF it is trying to home one axis at a time then what you see is what happens.

(;-) TP

1736

Mach4 General Discussion / Re: Screen Set Ideas

« on: December 20, 2014, 09:04:15 PM »

I guess I cheated I just view a JPG copy of the Drill ,Tap, Charts  (;-)

Nice work though on the LUA grid/chart , I was looking at Importing the CAMs tool table into Mach4 .

Perhaps you could fix the Mach4 tool table (;-)

(;-) TP

1737

General Mach Discussion / Re: Why does my slave axis do this?

« on: December 20, 2014, 08:33:04 PM »

Make SURE that your config is correct and you have selected  {Home Slave with master axis}  in Gen Config.

(;-0 TP

1738

General Mach Discussion / Re: What is the latest Mach3 ver. known to have probing working?

« on: December 20, 2014, 08:07:47 PM »

NOW as to the actual probing routine it would BEST be done as a SUB routine using #vars. You can USE a Mcode(macro) to program the routine using the #vars.

This Routine is STONE COLD reliable in its use. You just have to program what you want instead of using a WHILE LOOP like in a MACRO. 

NOW for the record MACH4 should be as reliable in the fact that you can use conditional Gcode . I have not been able to TEST mach4 Conditional yet but in "THEORY" it should be dependable. It works well in Fanucese and Haasese (;-)

IF you need more help holler, (;-) TP

(;-) TP

1739

General Mach Discussion / Re: OEM Trigger or Code and how they function.

« on: December 20, 2014, 06:13:40 PM »

OEMcods are internal functions that where brought out for your use.

OEMTriggers are the path to allow you to use outside inputs (buttons) and map them to internal functions by assigning the trigger to an OEMCODE.

No you cannot create an OEMCODEs they are hardcoded internally.

You can monitor the OEMTrigger input LEDS and create special functions via outside inputs

Hope that helps, Might want to download a read the Customizing Mach2 manual AND the Mach3 Programmers manual.

(;-) TP

1740

General Mach Discussion / Re: What is the latest Mach3 ver. known to have probing working?

« on: December 20, 2014, 03:46:30 PM »

OH MY (;-).  You have run into the LOST MACH syndrome .  It is where SOMETHING in the XML is corrupt and it make MAch3 do strange things at times.

My suggestion is to backup all your special stuff then wipe out mach3 completely and start over from scratch.

DO you have an original XML that you saved at the beginning of your adventure   NO the saved XMLs from mach won't do as you do not know at what point it started going bad.

ALSO make sure you delete all of the backup xmls (wipe out the directory).

NOW from scratch recreate mach3 AND THEN when everyting is working SAVE a copy of the XML to a safe place OUTSIDE of the mach3 directory. THat way IF it starts again just copy the OLD XML over the NEW XML and off you go again.  I had a BATCH file I ran from the DOS prompt that did the whole show in a wink.


That Helps to stabalise Mah3 when you are working in macros and mixed Gcode.  Can'rt say why and ART could never find what it was that triggered it.


NOW down to your Probing macro.  It will cause problem when you try a While loop with mixed Gcode. The CB and Gcode are runing in seperate threads and get messed up Faster PC have more problems with this than slow PCs ALSO single cores seem better than multi cores . SOMEWHERE someone got the multi threading UNSTABLE.

NOW that is for MachMILL  who knows what works in MachTURN.

So what exactly are you trying to do ? Your code is a bit confusing without seeing the whole picture. I assume that you are doing a probing routine in TURN.

(;-) TP