Hello @CAMXPRESS
Previously, the property was defined for the whole program.
And it was available only to the post processor.
Now the property can be used in the post, also in the machine configuration file.
(So the machine configuration will be able, when the post is associated, to pre define some properties)
And the properties can also be modified to have an operation scope.
As an explanation, if you set the machine kinematic, using a property hasAAxis, it can be a 'post' scope, or eventually a 'machine' one.
If you define a property for 5 axis smoothing, it can be an operation property. You may want to activate it or not operation by operation.
That's the goal of this scope information.
Actually we have converted the properties to this new format, but have changed the scope for any.
Later on we may change the scope for some properties, but we must support InventorCAM, HSM Works, and Fusion.
Regards
______________________________________________________________
If my post answers your question, please click the "Accept Solution" button. This helps everyone find answers more quickly!
Hello Joe,
No they are not related to the Machine Simulation. It's more a refining of the previous behaviour.
We wanted to be able to define properties on an operation level.
While thinking about the subject, it seemed smart to offer differents scopes.
The machine simulation will have more impact on the machine configuration files than to the properties.
It will also probably lead to some minors changes in the posts.
Regards.
