Uncaught Error in runtime status "Cannot Read Property 'document' of undefined" in Extension Fusion 360 Post Processor

[bernard5BABD]

Hello all, 
I believe the title says it all. I have already used this extension with success, but now I am setting up my IDE to work more intensively, for a whole, on a post processor (Roeders RMS6)
To my surprise, I see no syntactic coloration and this error. As I thought it might have something to do with this specific file, I tried with another post-processor that I know well and have already modified, GRBL. Exact same error.

Could this have anything to do with the fact that I am on the preview program? I doubt post-processor editing would be linked in some way to Fusion 360 version number, but what do I know?

I really need this to work ASAP, so your help is more than welcome!
Thanks, and best regards,

Bernard

[bernard5BABD]

Works by downgrading the Extension from 3.5.6 to 3.5.5, but that is a workaround, not a solution.

[serge.quiblier]

Hello @bernard5BABD 

your issue with syntaxic coloring can be caused by the loss of this association:

Regarding the "Cannot read..." error, is it an error appearing when posting, or when using the post extension?

Can you provide a screen capture?

Are you running a localized version of VS Code?

Cheers

______________________________________________________________

If my post answers your question, please click the "Accept Solution" button. This helps everyone find answers more quickly!

[bernard5BABD]

Thank you for your answer. I had already checked the association was there. What seems a little strange (to me) is that, as I said, I had to downgrade to 3.5.5, added the post.exe to the settings, and it worked. 
Once everything works fine, if I upgrade back to 3.5.6, it's still working fine....
Now, your other questions: I totally refuse to use a localized version of VScode. 😉 Much better to stick with English (for me). The cannot read error was only when using the post extension. I don't see this error anymore, but I don't see any post properties either.

Thanks for your help, and best regards,

Bernard

[serge.quiblier]

Hello @bernard5BABD 

fixture,graphite, RMAX, cleanAir ... are all post properties, they are displayed in the nc program dialog to tweak the gcode generation.

So the error could have been i can't find the properties defintion in the post.

Or when using the elements from the post extension (cnc selector, machine selector, functions list...) it could be n issue identifying the active document.

(But i never encountered an error, if the nc code is active, it doesn't display or update anything, but doesn't error out)

Regards.

[bernard5BABD]

Well, yes, I know and I have seen them listed in the outline. But when they are listed under "post properties" it allows me to change the value of the property on the fly, and see changes in G-code. It's totally possible to work without this, but it can be handy when one wants to test what effect have those properties on the generated G-Code.

I will go back (once again) to 3.5.5, as I believe it was working with that version. Looks like there are some fixes to be done to 3.5.6.

[bernard5BABD]

Going back to 3.5.5, post properties are now listed there, and modifiable from VS Code, as expected.

[AchimN]

@bernard5BABD When do you see that error message showing up? When you open a file? When you post process?
Regarding the properties, did you try to re-initialize the property list as shown below?

[bernard5BABD]

I don't see that error message anymore. It was showing up when I opened the cps file. And yes, I tried refreshing the list more than once.

[bernard5BABD]

I finally understood what was a mystery for me. (I mean, I believe I understood 🙂 )
When there is a new version of Fusion, there is a new directory created, so post.exe is not found anymore until you select the new place where it lives now. That was the reason why it was working, then suddenly not anymore.

Being a member of the "insider" program, I get new releases often.
This brings the question: is it really necessary to have post.exe location release dependent? I guess it does not change as often as Fusion itself does, so why not put it in a more stable location? Just a suggestion.

Thank you,

Bernard