Structured Logic 

The post offers limited structured logic capabilities. This functionality allows logical decisions when necessary. The following describes the format and required syntax.

IF, ELSE, and ENDIF Statements 

Here's a sample of a ToolChange sequence that uses if/then logic in 2 different places - first, to control dual-range spindle speed (M41, M42), then again to suppress the “pre-indexing” in the last tool change. (blank lines have been added for clarity to separate the "logic" sections from the rest of the sequence):

...as you can see from the example above…

• Either one or both of the 2 values on the if line must be a [variable]. It can even be a variable that is set from an ASK statement - letting you give the operator a set of processing "options"... let your imagination run wild!

• The lines 'inside' the IF structure may be indented. (Note: They may be indented one space only! If more than one leading space is used, that line will become a 'comment' - ignored by PostHaste!)

Here are the actual “rules” that apply to the if / then logic:

The IF line must have a variable or a number followed by a 1 or 2-character “logical operator”, then another variable or number. As usual, all items must be separated by a single space. The optional Else line and the required Endif line do not use any "parameters". Here are some sample "If" lines:

IF [Val1] = 2

If [Tool] > 24

if [speed] <= 500

(Note: Just as with all variable, sequence and command names, please notice that the capitalization of the words If, Else and EndIf doesn't matter.)

This is a list of the legal logical operators that can be used on the if line:

Restrictions

   1.   IF can only be used within a sequence or canned cycle.

   2.   An ENDIF line is required (even if there are no more lines after ENDIF within that sequence).

   3.   The ELSE line is optional.

   4.   The IF, ELSE and ENDIF lines must have at least 1 line of “code” between them.

   5.   IF statements cannot yet be nested.

   6.   You are limited to fifty IF structures within each machine format area.

Testing 2 conditions: Using AND and OR with IF

You can use the words AND and OR to make an IF function test for 2 conditions at a time as in the following examples:

if [Tool] > 5 OR [Val1] = 1

 ...do these lines...

ENDIF

if [LastHole] <> 1 AND [SpeedType] < 97

 ...do these lines...

ENDIF

Operators 

Legal operators are >, <, =, <> (not equal), <= and >=

Following is an example of a tool change sequence using logic to control dual-range spindle speed (M41,M42) and suppression of the pre-indexing of the last tool. (Blank lines were added for clarity to separate the “logic” sections from the rest of the sequence):

Toolchange

M<9>

G<28> G<49> Z<0> S<100>

N<Block> M<6>

This "IF" structure sets the "gear range" (M41 or 42):

IF [Speed]>500

G<0> G<40> G<80> G<Work> X<H> Y<V> M<42>

ELSE

G<0> G<40> G<80> G<Work> X<H> Y<V> M<41>

ENDIF

G<43> Z<D> H<Lcomp> M<Direct> S<Speed>

M<Cool>

Here the pre-indexing of the last Tool is suppressed:

IF [NextTool] <> [Tool1]

T<NextTool>

ENDIF

END

As you can see, either one or both of the 2 values must be a [variable]. It may be a variable that is set from an ASK statement—letting you give the operator a set of processing “options.”

The Set Command 

The SET command allows a variable to be set to any other variable or constant. Place this within an IF structure, and you can set a variable to a number.

Following is an example of how to support spindle ranges: