Initial Work Offset Posting Twice (Multiple WCS)

[Anonymous]

Hello there,

When I post multiple WCS over more than one setup at the same time, it will run through all the WCS in the setup in sequence in whatever way I specify (preserve order, order by op.....) and then it will run the first WCS in that setup again, in full preserved order, before moving to the next setup, where it does exactly the same thing.

For example,

Setup1 runs at G54 and G55 (in preserve order to keep it simple).

Setup2 runs at G56 and G57 (again in preserve order).

If I select both setups at the same time and post it out, it runs as follows: G54, G55, G54, G56, G57, G56. I think I had the same issue with the reorder to minimise tool changes box checked too. 

If I post the setups individually they post out as expected. The issue exists using the Mazak post I've modified and a test done with the generic Haas too.

Is anyone else experiencing this issue? Any ideas what the problem could be?

Thanks,

Dave

[keith_clausen]

Regarding how your HSM updates with Inventor updates, I'm not sure.

I am primarily a HSMWorks guy but have it all in-order to help as I am primarily an HSM guy and it all is pretty much the same.

Yes, upload your post when you get a chance and check you version # and let us know.

[Anonymous]

Hey Keith,

I did have a few updates available to me (seems my Autodesk Desktop App isn't showing any new updates that have been released), that have been installed via account manager. However there is no change in the situation!

Currently running:

Inventor 2018-Build 227-Release 2018.2.3

Inventor HSM Ultimate-Build 5.4.1.69

I downloaded the same Haas (pre NGC) cps file that you used from the online post library (to ensure it is indeed current), but my code still has the same issues that I've described before.

Here is the Haas (pre NCG) post I used and the posted code (in preserve order for ease of scanning):

[keith_clausen]

Hi Dave,

Odd results. 

Using your file, setting multiple WCS to "Preserve Order", using the post you attached, then I posted the code and it is producing a different NC code file from what you last attached.

Take a look at the attached and compare the code to confirm.

At this point I'm not sure what is going on to produce the results you are getting.

[keith_clausen]

Currently running:

Inventor Professional 2018-Build: 112-Release:  2018.2.3 - Date Thu 02/16/2017

Inventor HSM Ultimate-Build 5.3.2.65

[keith_clausen]

Just so you know, I just downloaded the latest update for InventorHSM "Inventor HSM Ultimate-Build 5.4.1.69" and produced the same code results as "1003.nc"

[Anonymous]

---

@keith_clausen wrote:

Hi Dave,

Odd results. 

Using your file, setting multiple WCS to "Preserve Order", using the post you attached, then I posted the code and it is producing a different NC code file from what you last attached.

Take a look at the attached and compare the code to confirm.

At this point I'm not sure what is going on to produce the results you are getting.

---

Yes Keith, I think so too! Your code is what I would expect to be produced.

Thank you very much for your time on this.

Does anyone from Autodesk have any input?

[keith_clausen]

Dave at this point I would for sure contact your reseller and/or Autodesk for escalated support.

@Matthew-R , @jeff.pek can you direct this issue to someone at ADSK that can help Dave with the issue he is having. I've tested and confirmed positive results with his file and post on my end but the problem persists on his end and as far as I can narrow down it is not his file or post that is producing the issue. If you require additional input from me please reach out to me directly.

[Matthew-R]

@bob.schultz would you be able to have a look at this?

[keith_clausen]

@Matthew-R @bob.schultz Please Keep in mind that @Anonymous is located in the UK.

[bob.schultz]

---

@Anonymous wrote:

Hey Keith,

I did have a few updates available to me (seems my Autodesk Desktop App isn't showing any new updates that have been released), that have been installed via account manager. However there is no change in the situation!

Currently running:

Inventor 2018-Build 227-Release 2018.2.3

Inventor HSM Ultimate-Build 5.4.1.69

I downloaded the same Haas (pre NGC) cps file that you used from the online post library (to ensure it is indeed current), but my code still has the same issues that I've described before.

Here is the Haas (pre NCG) post I used and the posted code (in preserve order for ease of scanning):

---

Hello Dave,

The version number you list here is strange.  The latest version of HSM Ultimate that I can see being available is "Inventor HSM 2018 5.4.0.234".  With that said this is not a post (.cps) problem.  The logic to output the operations is in HSM so it really does not matter what post you are running, the results will be the same.

I get the same good results as @keith_clausen and am not able to duplicate the problem.  Can you run the part against the 'dump.cps' post processor provided here and then supply the output .dmp file.  I would like to check the revision of the post engine.

Thanks,

Bob

[keith_clausen]

Hi Bob,

I just updated InventorHSM yesterday and I have the same build as Dave.

Update white paper

[bob.schultz]

Hello Keith,

It could be that the last developer version made it into production and the version number changed.  From my understanding you could not duplicate Dave's problem either.  Can you do me a favor and run the provided dump.cps post against his model and provide the output .dmp file.  This way I can compare apples to apples with Dave's output.

Thanks,

Bob

[keith_clausen]

That's correct Bob. I could not duplicate the issue. Give me a couple of minutes and I will post the dump output.

[keith_clausen]

Here is my dump file.

[Anonymous]

---

@bob.schultz wrote:

---

@Anonymous wrote:

Hey Keith,

I did have a few updates available to me (seems my Autodesk Desktop App isn't showing any new updates that have been released), that have been installed via account manager. However there is no change in the situation!

Currently running:

Inventor 2018-Build 227-Release 2018.2.3

Inventor HSM Ultimate-Build 5.4.1.69

I downloaded the same Haas (pre NGC) cps file that you used from the online post library (to ensure it is indeed current), but my code still has the same issues that I've described before.

Here is the Haas (pre NCG) post I used and the posted code (in preserve order for ease of scanning):

---

Hello Dave,

The version number you list here is strange.  The latest version of HSM Ultimate that I can see being available is "Inventor HSM 2018 5.4.0.234".  With that said this is not a post (.cps) problem.  The logic to output the operations is in HSM so it really does not matter what post you are running, the results will be the same.

I get the same good results as @keith_clausen and am not able to duplicate the problem.  Can you run the part against the 'dump.cps' post processor provided here and then supply the output .dmp file.  I would like to check the revision of the post engine.

Thanks,

Bob

---

Hey Bob,

Thanks for looking.

Here you go......

[bob.schultz · Accepted solution]

Hello Dave,

I brought up this issue with our developers and found out that this is a known problem when you select the Top Level Operation(s) item in the operations tree.  This issue is currently being looked at.  You can get the correct output by selecting the Setups that you want to post process instead.  The following picture demonstrates the selection of multiple Setups (by holding down the Ctrl key when selecting the second setup).  Do not select the Operation(s) (red arrow) for post processing.  This should resolve your issue.

[keith_clausen]

Hi Bob,

Is that something specific to InventorHSM or HSM kernel in general?

I guess I could have caught that as a variable, it is just my default to select the Job Setups.....legacy of working with HSM as long as I have I guess. 

Good information and thank you for getting this resolved for @Anonymous.

I guess this can be set to solved once Dave has a chance to test.

[bob.schultz]

From what I was told, it is specific to Inventor HSM.  Like you I always select the Setups and didn't think to select the top level list of Operations to duplicate it.

[Anonymous]

---

@bob.schultz wrote:

Hello Dave,

I brought up this issue with our developers and found out that this is a known problem when you select the Top Level Operation(s) item in the operations tree.  This issue is currently being looked at.  You can get the correct output by selecting the Setups that you want to post process instead.  The following picture demonstrates the selection of multiple Setups (by holding down the Ctrl key when selecting the second setup).  Do not select the Operation(s) (red arrow) for post processing.  This should resolve your issue.

Hey Bob,

In my case the work around you suggest doesn’t provide the correct output.  It was actually the method I used when first discovering the issue. 

---

[keith_clausen]

Hi Dave,

So just to clarify, selecting "setup1" folder and "setup2" folder and then post processing is still tendering incorrect post code?