yes it´s possible, but take care wenn using setJointAlias! Don´t forget a documentation about that. When it´s possible, I would suggest to create a adress with the name "GV_B" which points to the B-Axis. It´s more flexible and clear for everyone.
thank you for the notice.
I created an adress with GV_B, now it's red marked.
The metacode looks like that and an error appears with the message "variable not declared":
please clarify what you want to do?
- you have an axis in the KIM with its name "GV_B"?
- you move this axis with the following NC code by e.g. B10?
Almost right, but please turn the trouble like that:
- I have an axis in the KIM with its name "B"
- I move this axis with the following NC code by e.g. GV_B=10
In that case you need the "power" of the CSEPreprocessLine ;-) because "GV_B" is no valid axis adress for the parser. This method is called for every NC Code line BEFORE the string is send to the parser.
It´s similar to the SetJointAlias function... BE CAREFUL!! Take care of a good traceability and documentation!
<Name>CSEPreprocessLine</Name> <Param>strLine</Param> <Execute> <AssignCommand> <Variable>strLine</Variable> <Value>replaceSubstr("GV_B",strLine,"B")</Value> </AssignCommand> <ReturnCommand> <Value>strLine</Value> </ReturnCommand> </Execute>
Thank you very much! Very good...
But I also found another way and wrote this into the main.ini :
DEFINE GV_B AS G0 B
I've got a new problem.
How can I define Y2 as a new second geo axis by checking a variable (isDefined)?
Normally the second geo axis is Y1. I use NX 10.0.2.6 MP1.