MachineConfiguration = MachineConfiguration.createFromPath(findFile(properties. The first bit is where the generic heidenhain gets the machine configuration from a file: The Haas posts are definitely pulling stuff from either the machine configuration in the post, or from the HSMWorks machine configuration.
It's not like normal code where you declare the references at the top of the javascript file. I can't see that code in the post where it loads the HSMWorks machine configuration. See the generic Heidenhain this is set-up to support machine configs.(The only post I know that does this by default) If you're getting any other kind of license prompt besides asking you to log in (if you're not already), then it's using one of the other options. It should prompt you to choose between Premium, Ultimate, and Fusion Entitlement. The machine config only is loaded if you specify where it is. The key thing is how you install HSMWorks. If a 4 or 5 axis machine definition is specified in HSMWorks then 4 & 5 axis code is output even though the 'multi axis machine definition' is disabled in the post.
The Generic Haas post is an interesting one. It's interesting that some of the latest posts a-axis & inverse time posts still have that set to false. So that only overrides anything that is declared in the post & in the software? I can still pull values or test parameters which are in the HSMWorks machine configuration right? There is no way to set a rotary axis to cyclic in the HSMworks machineconfig.
0 kommentar(er)
