Haas VR-9 suspected post processor issue

[nzerkle]

Currently running into an issue with the Haas VR-9 post where the Z and Y value appear to be flipping based on individual tool paths. If we post the individual tool path or suppress certain operations, the code is fine, if we post the whole program, the Z and Y values are different on certain tools and will cause a Collison or overtravel. Is there a setting that needs to be activated or is the post processor creating an issue. I can provide models if necessary. Attached a screenshot showing the different values with the same post just suppressed operations vs the whole job. 

[AchimN]

Hi @nzerkle ,

Thanks for your feedback! This seems to be a post processor issue, could you please share the model which includes the toolpaths you mentioned?

Thanks!

[nzerkle]

@AchimN Thanks! I attached the file, we have a modeled stock so I had to pack and go the file, let me know if they're any issues. 

[AchimN · Accepted solution]

Thanks for sharing the sample part.
I can confirm that you found a bug there. I will fix it right now, the updated post processor will show up on the post library shortly:
https://cam.autodesk.com/hsmposts?p=haas_vr-9

[AchimN]

@nzerkle FYI, the updated post is online now.

Thanks for your feedback!

[nzerkle]

@AchimN Thank you!!!!

[nzerkle]

@AchimN We are noticing a new issue with the updated post and contouring. Same kind of issue where some bores on the part will machine fine and one will skip a finishing pass, if we move the contour around in the code or post it individually it posts fine.  I attached both a screenshot of the code and the Zip file. 

[AchimN]

I cannot reproduce this, which operations do I have to select to be able to see the problem? It always posts fine here on my end.

[nzerkle]

@AchimN Ah, you are correct. We have isolated this to one computer, it works fine on my laptop but the desktop my main programmer uses reproduces this issue when both job folders are posted at the same time. He is on the new post and the newest revision of HSM, Any ideas on an isolated issue like that? 

[AchimN]

Hmm i double checked with latest versions also, still good. Can you tell me the exact HSMWorks version where you see this problem? I dont think that this is a post processor related issue tbh.