Additional functions
14.5 Check scope of NC language present (STRINGIS)
Job planning
676 Programming Manual, 07/2010, 6FC5398-2BP40-0BA0
Examples
In the following examples it is assumed that the NC language elements specified as string -
as long as nothing else is noted - can in principle be programmed in the control.
1. String "T" is defined as auxiliary function:
400 == STRINGIS("T")
000 == STRINGIS ("T3")
2. String "X" is defined as axis:
201 == STRINGIS("X")
201 == STRINGIS("X1")
3. String "A2" is defined as address with extension:
201 == STRINGIS("A")
201 == STRINGIS("A2")
4. String "INVCW" is defined as named G code:
202 == STRINGIS("INVCW")
5. String "$MC_GCODE_RESET_VALUES" is defined as machine data:
206 == STRINGIS("$MC_GCODE_RESET_VALUES")
6. String "GETMDACT" is an NC language function:
203 == STRINGIS("GETMDACT ")
7. String "DEFINE" is a keyword:
205 == STRINGIS("DEFINE")
8. String "$TC_DP3" is a system parameter (tool length component):
207 == STRINGIS("$TC_DP3")
9. String "$TC_TP4" is a system parameter (tool size):
207 == STRINGIS("$TC_TP4")
10. String "$TC_MPP4" is a system parameter (magazine location state):
– Tool magazine management is active:
207 == STRINGIS("$TC_MPP4") ;
– Tool magazine management is not active:
000 == STRINGIS("$TC_MPP4")
Also refer to the paragraph below: Tool magazine management.
11. The string "MACHINERY_NAME" is defined as GUD variable:
209 == STRINGIS("MACHINERY_NAME")
12. The "LONGMACRO" string is defined as macro:
210 == STRINGIS("LONGMACRO")
13. The string "MYVAR" is defined as LUD variable:
211 == STRINGIS("MYVAR")
14. String "XYZ" is a command that is not known in the NCK, GUD variable, macro or cycle
name:
000 == STRINGIS("XYZ")
To Next Page
Loading...
Need help?
General
