I was trying to simulate an NC code program with calls to a custom engraving macro we use.
It is not setting the variables correctly
Example: G65 P9060 I10. I20. I30. I40. I50. I60. I70. should have these variable set in subprogram level
#4=10 #7=20 #10=30 #13=40 #16=50 #19=60 #22=70
The variable watch in NX11 simulation shows #4=70 and all others undefined.
My questions are:
1. Is it possible to update the parser to handle this?
2. would this require a Machine Configurator licence?
From our machine control documents.
Argument specification II Format: A_B_C_I_J_K_I_J_K_!!!!! Detailed description - Up to a maximum of 10 sets of arguments that each consist of addresses I, J, and K, as well as A, B, and C, can be specified. - If identical addresses overlap, specify them in the required order. - Addresses whose specification is not required can be omitted. - The relationship between addresses that can be specified using argument specification II, and variables numbers in a user macro unit, is shown in the following list:
Argument specification II addresses - Variables in macro programs
Note: In the list above, the numerals 1 through 10 have been added to addresses I, J, and K to denote the order of arrangement of the designated sets of arguments: these numerals are not included in actual instructions.
short feedback is that the Fanuc Parser and CCF (Meta Codes) installed with NX supports the argument specification Ionly.
The argument specification IIcan be customized. Needed customization the Python Parser as well as in the CCF Meta Code implementation for the last one a MAchei Configurator License is required. As it needs some more insight I suggest to get in contact with Siemens service or a experienced Siemens partner.
Thomas Schulz Siemens PLM Manufacturing Engineering Software