Fusion "looses" postprocessor between posts

[rhdfmail]

Just noticed that all of a sudden fusion didnt autoselect the postprocessor from machine-config.
Fist I ignored it as a glitch, but when i manually set it in the postdialog, post and then repost 1 min later, its gone from the dialog...

[MoshiurRashid]

seth.madore

Please have a look.

[rhdfmail]

This is still an issue

It seems that the posting process ignores the machine-config in the setup

That means that I need to select the postprocessor every time I post AND I need to manually edit the generated code  to get my homeposition right  (X0 Y0 is not a good place to go with M91...)

Please stop braking stuff that actually worked fine 

The NC-program feature looks unfinished and I havent (yet) found a way to define the machine-config there

[GeorgeRoberts]

Hello,

Sorry to hear you're having issues. The post processor should be inherited from the machine configuration in both NC programs and the post process dialog. They should also use the home position that is set in the machine configuration

If this isn't happening, can you share a copy of your machine configuration? I assume something is broken there

[rhdfmail]

Obviously something is broken somewhere 😉

The big question is when and why it suddenly broke. I have used this machine-config for  months  and another for a different machine more or less since it was introduced. 

strange enough it seems I cant attach the machine-file

[GeorgeRoberts]

Thanks for the reply. It is all working as expected my end

Can you email me the machine file and post processor you have linked to it? [email protected]

Thanks

[rhdfmail]

Files sent by email

[rhdfmail]

Temporary solution:
Create a NC program. Select the right post and fill in a link to the machineconfig in the settings for the post

In other words, I have to do it "backwards" and with a extra step instead of just create a setup, select a machine config and then klick on post-putton (or rightclick the setup and select postprocess)

[rhdfmail]

Obviously there was a bug according to the latest update (that was released 3 days ago but fusion didnt tell me... 😉 )

Homeposition is back in the code, but the post-dialog doesn't get info from the machineconfig wich post to use so I have to reselect it every time. 

I can sort of live with that for a while now when I dont need to edit my posted programs everytime and risking to forget it and having a machin alarming for X-axis overtravel and never resets tilted plane = I have to do it manually, wich I always forget and then stands there scratcing my head and wonder why the machine tells me that the axis is in wrong position when the display says C=0 B=0 ..

[rhdfmail]

Just noticed a variation of this bug/feature/strange behaviour

Created a setup,
selected a machine config from cloud 
Posted (with the annoyance of having to select post in that dialog..)

NC-Code comes out as expected

Then I created a NC program.
The post is autoselected to the same as above
Selected the operations (or rather the whole setup)
Posted and realize that the NC-code is NOT what I wanted.

It seems that NC-program doesnt find the machine-config 
When selecting my backup-post from a folder on my computer it magicly managed to find and fill in the path to the  machineconfig thats stored localy (not fusion local folder)

One difference in code:
Wrong:

19 CYCL DEF 19.0 WORKING PLANE
20 CYCL DEF 19.1 A+0 B+0 C+0

Correct:

19 CYCL DEF 19.0 WORKING PLANE
20 CYCL DEF 19.1 B+0 C+0

From my post

 if (properties.machineDefinition) {
    machineConfiguration = MachineConfiguration.createFromPath(findFile(properties.machineDefinition));
    log("");
    log("Machine configuration:");
    log(getMachineConfigurationAsText(machineConfiguration));
    setMachineConfiguration(machineConfiguration);
    optimizeMachineAngles2(0); // using M128 mode
  } else if (false) {
    // NOTE: setup your machine here
    //var aAxis = createAxis({coordinate:0, table:true, axis:[1, 0, 0], range:[-120.0001, 120.0001], preference: properties.preferTilt});
    var bAxis = createAxis({coordinate:1, table:true, axis:[0, 1, 0], range:[-120.0001, 45.0001], preference:properties.preferTilt});
    var cAxis = createAxis({coordinate:2, table:true, axis:[0, 0, 1], range:[0, 360], cyclic:true});
      //machineConfiguration = new MachineConfiguration(aAxis, cAxis);
	machineConfiguration = new MachineConfiguration(bAxis, cAxis);

    setMachineConfiguration(machineConfiguration);
    optimizeMachineAngles2(0); // using M128 mode
  }

It also ignores the settings for home-position