Autodesk HSM Post Editor for Visual Studio Code goes live

[fonsecr]

Hi all post developers,

We just pushed Autodesk HSM Post Editor for Visual Studio Code live as an Open Source project under the MIT license. Check it out at:

https://github.com/Autodesk/cam-posteditor

This project is an extension for Visual Studio Code that makes life much easier when developing posts.

You can get the installation for Visual Studio Code at:

https://marketplace.visualstudio.com/items?itemName=Autodesk.hsm-post-processor

@GeorgeRoberts has been working on this until now. But my hope is that we can work together as a community to make it even better. So if you are interested in contributing make sure to engage. Of course you are welcome to just make requests for the post team also. You can use the post idea station for such requests.

Note that you need to sign a small agreement before we can accept contributions.See the README for details.

George will post introduction to the extension here.

[makko74]

Hey @GeorgeRoberts

thanks for your reply and suggestion.

I had already tried that but somehow still no window was to be seen, I try it again on Monday.

Since I seem to be the only one with such special post-processors and I now know where to change it, it should not be necessary to insert it as a parameter. (But I would enjoy it anyway.  )

Thanks a lot and a nice weekend

Mario

[makko74]

Hello @GeorgeRoberts,
i've tried again but without success, the post.exe window does not want to be visible. Now I have a property in the postprocessor that suppresses the messages. At least that's the way it works.

Thank you for your help

Mario

[Anonymous]

(sorry, had made reply to wrong post)

[Anonymous]

hi
I have same issue as guys above. 
Depend on a point I click a line in the processes NC file in right pane in VSC - it navigates to different code point in left pane. It looks like when more right side I click then more deep in call stack it shows.

May be it's such feature? 🙂

PS. At 2:45 of the intro video you click to bore.cnc file (in CNC SELECTOR pane) and then VSC showed the command bar on top of code pane. My VCS doesn't that so I have to run process manually from command bar. Maybe I had disabled something in VSC? How to enable it?

[makko74]

@GeorgeRoberts

Unfortunately, it does not work to get the post.exe window visible. Maybe I have a wrong setting in vscode, I do not know.
But what helped was adding the parameter "--allowui" to the extension.js. So at least the message boxes are visible during the post process, that's all I need.

Mario

[fdboswell]

Very cool VS Code extension, thanks. And another upvote for MAC support.

[AchimN]

Hi all,

FYI, we have pushed an update for the HSM Post Editor Addin today which offers support for showing and modifying the post properties. This gives you the option to test your post with your properties without actually changing the property defaults into the post since it is easy to forget to change them back.
Let us know if you have issues with it.

Thanks, Achim

[sharmstr]

I cant seem to get the post to work.  Every time I try I get an error saying "Post processing failed, see log for details".  I have no idea what log its referring to, but I did find a renderer1.log file.  In there, there are errors about a file lock on /appdata/local/temp/debuggedfile.log.

I'm running Windows 10 and using the generic HAAS post. I've restarted my computer to "unlock" the file, but I still get the same error.

[CAMXPRESS]

Hello All,

I have a problem when I like to run the postprocess inside VSCode. I have the following error:

- Running the contributed command:'HSM.postProcess' failed.

What I have:

- The latest VSCode : 1.32.3

- Installed ADSK HSM PP Extension: 2.1.1

- Linked the post.exe what is the plugin directory (getting from Fusion directory, mozjs.dll also)

The other functionality of the plugin works well : Function list etc.

What is worng with my installation?

Any help would welcome.

Regards,

Joe

[AchimN]

Please update the extension, the latest version is 2.3.4

[CAMXPRESS]

Thank you Achim, It is working now!

Regards,

Joe

[Anonymous]

Does this still not work on macOS? Just installed it in VSC and it doesn't work on Mojave.

[Anonymous]

Hello !

I have the same problem ... the extension does not work for VSCode in MacOS ... are you planning a version for Mac users?

Thank you !

[daniel_lyall]

@GeorgeRoberts  a nudge How's the Mac version going I so want it.

[GeorgeRoberts]

@daniel_lyall I've now added support for MAC. You should be able to get it from the extension store

It's tricky finding the post executable (in the fusion install location), need to find a good way of doing that... Hopefully I can get something this week

[daniel_lyall]

Thank you

[Anonymous]

Hi George, I've already tried it and it works!

In my case, the executable of my post processor is in this path :

"/Users/youruser/Library/Application Support/Autodesk/webdeploy/production/randomcodelikethisaaf284e803ac0029ad088753e/Libraries/Applications/CAM360/"

The best way I had to get to this file has been with the following steps:

- control + click on the Fusion360 icon to show the options ..
- then go to options
- view in finder (finder opens)
- then navigate to .. Libraries - Applications - CAM360
- there is the "post" file
- control + click in "post" file and press option key to copy "post" as path
- in VSCode go to .. HSM: Change Post Executable - Browse

- press shift + command + G and paste you path ..

- select "post" file, and click open ..

- ready it will be working ! ..

Thanks again George ..

[bozboyle]

Hi everything appears to be ok. I can choose my custom cnc file and my .cps post and my post .exe. But when I do a CTRL ALT G it says

  Running the contributed command: 'HSM.postProcess'failed.

and nothing happens

regards Boz

[GeorgeRoberts]

Thanks for posting. That error usually means something in the extension has failed to start...

Do you have a .cps file open? If so, are the functions / CNC files shown in the explorer sidebar?

[CAMXPRESS]

Hello George,

Do we have any method to post Machine Kinematic information to the VSCode export file and use it

directly at VSCode?  How we could easily handle the Machine Kinematic related parameters at VSCode?

Regards,

Joe