Initial Work Offset Posting Twice (Multiple WCS)

Initial Work Offset Posting Twice (Multiple WCS)

Anonymous
Not applicable
2,826 Views
45 Replies
Message 1 of 46

Initial Work Offset Posting Twice (Multiple WCS)

Anonymous
Not applicable

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

0 Likes
Accepted solutions (1)
2,827 Views
45 Replies
Replies (45)
Message 2 of 46

lenny_1962
Advisor
Advisor

which software and can you put the files up?

0 Likes
Message 3 of 46

Anonymous
Not applicable
Sorry, Inventor HSM.

The issue persists across three different part files that I tried at random, one of my posts and the generic Haas post.

I can put up some files on Monday, but I was wondering if anyone else was experiencing the same issue, or maybe someone could replicate it?
0 Likes
Message 4 of 46

Anonymous
Not applicable

 

 

Hi Dave and Len, I am using HSM for SolidWorks If the initial WCS is 1 in the second setup I would get the results you described. As you can see in the photo the initial WCS is 3 and then it posts out starting at G56 and then goes to G57.

Jason

 WCS EXAMPLE.PNG

0 Likes
Message 5 of 46

lenny_1962
Advisor
Advisor

I don't use that function, I copy the job and put a different offset and then order them in the tree, then select and post the ones I want.

 

that way I can post 1, 2 or all 4 or any combo.

 

did you try the first field at 2? instead of 3?

0 Likes
Message 6 of 46

Anonymous
Not applicable

After another look what I was thinking wouldn't get the results he was getting. 

 

I will try separate jobs with different offsets.

 

If the first field was 2 it would start at G55.

0 Likes
Message 7 of 46

Anonymous
Not applicable

@Anonymous wrote:

 

 

Hi Dave and Len, I am using HSM for SolidWorks If the initial WCS is 1 in the second setup I would get the results you described. As you can see in the photo the initial WCS is 3 and then it posts out starting at G56 and then goes to G57.

Jason

 WCS EXAMPLE.PNG


Setup1 - The work offset field is 1. Multiple WCS offsets is checked and number of instances set to 2 for G54 and G55.

Setup3 - The work offset field is 3 and multiple WCS set as above for G56 and G57.

 

I can post either setup individually and they run as expected (the toolpath is executed at each offset once), but if I select both setups at once I get the issue described above.

0 Likes
Message 8 of 46

lenny_1962
Advisor
Advisor

can you do a screen cast of whats happening?

 

what version of SW and HSMWorks are you using?

0 Likes
Message 9 of 46

Anonymous
Not applicable

@lenny_1962 wrote:

can you do a screen cast of whats happening?

 

what version of SW and HSMWorks are you using?


Hey Len,

 

I'm using the current release version of Inventor HSM Ultimate.

 

I've put together a simple part to show the behaviour without the posted code being too long. This uses 3 WCS on each of the 2 setups. IAll of the posted files use the stock Autodesk generic Fanuc post processor nothing modified at all.

 

PreserveOrder.nc goes through G54, G55 and G56 as it should from Setup1, but then runs G54 again before moving to Setup2 then running G57, G58, G59, then G57 again.

 

OrderByOp.nc runs through each operation at all WCS on Setup1 as it should, before running through the whole thing again at the first WCS, then moving on and doing the same on Setup2.

 

ReorderToMinTC.nc exhibits the same kind of behaviour. Working through all Ops and WCS correctly, before running the first WCS of each setup again. In this case G54 and G57 reordered to minimise tool changes.

 

I can post either Setup1 or Setup2 individually without issue.

 

 

 

 

 

0 Likes
Message 10 of 46

Anonymous
Not applicable

And here is the last attachment.

0 Likes
Message 11 of 46

lenny_1962
Advisor
Advisor

Dave sounds like an inventor issue, sorry but I do not use inventor only SW and HSMWorks

 

one of the other guys that use Inventor will have to sort this out.

0 Likes
Message 12 of 46

Anonymous
Not applicable

Thanks for looking anyway.

 

0 Likes
Message 13 of 46

keith_clausen
Collaborator
Collaborator

@Anonymous wrote:

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


Dave,

 

If I'm reading this correctly.

 

If you are posting operations from two different job setups regardless of the Multiple WCS usage, the operations will sequenced as such. The preserve order will only apply in its respective job setup.

Keith Clausen
Gcode In Motion

SolidWorks 2021
HSMWorks 2022
Fusion360 - Manufacturing Extensions
0 Likes
Message 14 of 46

keith_clausen
Collaborator
Collaborator

@lenny_1962 wrote:

Dave sounds like an inventor issue, sorry but I do not use inventor only SW and HSMWorks

 

one of the other guys that use Inventor will have to sort this out.


Len have you ever tried posting operations from two or more job setups that are defined using multiple WCS in each? Form the way I read Dave's initial post the system is behaving as I would expect it to.

Keith Clausen
Gcode In Motion

SolidWorks 2021
HSMWorks 2022
Fusion360 - Manufacturing Extensions
0 Likes
Message 15 of 46

lenny_1962
Advisor
Advisor
@keith_clausen 

no I do not, I've only really used it twice in HSMWorks since 2012.

 

If I have multiple work offsets I just copy and paste the job folders in the tree and change the offset numbers and the output post name that includes the offset #.

 

Yes I know Keith it is not optimized, just how I like to do it, it's just so friken easy if you protect all the ops, I can pick and choose and reorder the tree to have it post out what I want to cut first, second.... 15th. And I always program in the assembly because I use a sh!tload of configurations and display states to manage during programming.

 

just doesn't sound correct to me that it recuts the fist offset...???!!! 

0 Likes
Message 16 of 46

keith_clausen
Collaborator
Collaborator

Yes, I was speed reading through the initial post....my bad!

 

@Anonymous I have your file open and I will take a look at the posted code.

Keith Clausen
Gcode In Motion

SolidWorks 2021
HSMWorks 2022
Fusion360 - Manufacturing Extensions
0 Likes
Message 17 of 46

keith_clausen
Collaborator
Collaborator

@Anonymous

 

From your file I posted both setups using the Generic Haas post (Pre-NGC) and it seemed to post just fine, I even selected "Reorder to minimize tool Changes" and that to worked fine. If this is not working correctly for you It could be the fact that it is the  version of HSM you are using but more than likely it is your post processor that needs updating or tweek.

 

What version of HSM are you currently using?

Can you upload your post processor? If it is a generic post included in the install, please state.

Keith Clausen
Gcode In Motion

SolidWorks 2021
HSMWorks 2022
Fusion360 - Manufacturing Extensions
0 Likes
Message 18 of 46

keith_clausen
Collaborator
Collaborator

@Anonymous

 

Below is the posted code using the Haas Generic post.

 

%
O01001
(Using high feed G1 F5000. instead of G0.)
(T2 D=80. CR=6. - ZMIN=-0.25 - face mill)
(T4 D=40. CR=0.2 - ZMIN=-2.25 - bullnose end mill)
(T6 D=6. CR=0. TAPER=118deg - ZMIN=-22.553 - drill)
(T10 D=10. CR=0.2 - ZMIN=-20.25 - bullnose end mill)
(T30 D=8. CR=0. TAPER=45deg - ZMIN=-3.75 - chamfer mill)
G90 G94 G17
G21
G53 G0 Z0.

(Face1)
T2 M6
S10000 M3
G54
M8
G0 X132. Y-12.5
G43 Z15. H2
T10
G0 Z7.75
G18 G3 X124. Z-0.25 I-8. K0. F10000.
G1 X106.
X-26.
G3 X-34. Z7.75 I0. K8.
G0 Z15.
G53 G0 Z0.

(Face1)
G55
G17
G0 X132. Y-12.5
G43 Z15. H2
G0 Z7.75
G18 G3 X124. Z-0.25 I-8. K0. F10000.
G1 X106.
X-26.
G3 X-34. Z7.75 I0. K8.
G0 Z15.
G53 G0 Z0.

(Face1)
G56
G17
G0 X132. Y-12.5
G43 Z15. H2
G0 Z7.75
G18 G3 X124. Z-0.25 I-8. K0. F10000.
G1 X106.
X-26.
G3 X-34. Z7.75 I0. K8.
G0 Z15.
G53 G0 Z0.

(Face2)
G57
G17
G0 X127. Y-12.
G43 Z20. H2
G0 Z10.5
G18 G3 X119. Z2.5 I-8. K0. F10000.
G1 X101.
X-26.
X-40.
Z0.
X-26.
X101.
G2 X109. Z8. I0. K8.
G0 Z20.
G53 G0 Z0.

(Face2)
G58
G17
G0 X127. Y-12.
G43 Z20. H2
G0 Z10.5
G18 G3 X119. Z2.5 I-8. K0. F10000.
G1 X101.
X-26.
X-40.
Z0.
X-26.
X101.
G2 X109. Z8. I0. K8.
G0 Z20.
G53 G0 Z0.

(Face2)
G59
G17
G0 X127. Y-12.
G43 Z20. H2
G0 Z10.5
G18 G3 X119. Z2.5 I-8. K0. F10000.
G1 X101.
X-26.
X-40.
Z0.
X-26.
X101.
G2 X109. Z8. I0. K8.
G0 Z20.
M5
G53 G0 Z0.

(2D Contour1)
M9
M1
T10 M6
S12000 M3
G54
M8
G17
G0 X-5.5 Y-13.5
G43 Z15. H10
T4
G0 Z4.75
G1 Z0.75 F7200.
Z-19.25
G18 G2 X-4.5 Z-20.25 I1. K0.
G1 X-3.5
G17 G3 X-2.5 Y-12.5 I0. J1.
G1 Y-2.5
G2 X-1.036 Y1.036 I5. J0.
G1 X0.964 Y3.036
G2 X4.5 Y4.5 I3.536 J-3.536
G1 X75.5
G2 X79.036 Y3.036 I0. J-5.
G1 X81.036 Y1.036
G2 X82.5 Y-2.5 I-3.536 J-3.536
G1 Y-22.5
G2 X81.036 Y-26.036 I-5. J0.
G1 X79.036 Y-28.036
G2 X75.5 Y-29.5 I-3.536 J3.536
G1 X4.5
G2 X0.964 Y-28.036 I0. J5.
G1 X-1.036 Y-26.036
G2 X-2.5 Y-22.5 I3.536 J3.536
G1 Y-12.5
G3 X-3.5 Y-11.5 I-1. J0.
G1 X-4.5
G18 G3 X-5.5 Z-19.25 I0. K1.
G0 Z15.
G53 G0 Z0.

(2D Contour1)
G55
G17
G0 X-5.5 Y-13.5
G43 Z15. H10
G0 Z4.75
G1 Z0.75 F7200.
Z-19.25
G18 G2 X-4.5 Z-20.25 I1. K0.
G1 X-3.5
G17 G3 X-2.5 Y-12.5 I0. J1.
G1 Y-2.5
G2 X-1.036 Y1.036 I5. J0.
G1 X0.964 Y3.036
G2 X4.5 Y4.5 I3.536 J-3.536
G1 X75.5
G2 X79.036 Y3.036 I0. J-5.
G1 X81.036 Y1.036
G2 X82.5 Y-2.5 I-3.536 J-3.536
G1 Y-22.5
G2 X81.036 Y-26.036 I-5. J0.
G1 X79.036 Y-28.036
G2 X75.5 Y-29.5 I-3.536 J3.536
G1 X4.5
G2 X0.964 Y-28.036 I0. J5.
G1 X-1.036 Y-26.036
G2 X-2.5 Y-22.5 I3.536 J3.536
G1 Y-12.5
G3 X-3.5 Y-11.5 I-1. J0.
G1 X-4.5
G18 G3 X-5.5 Z-19.25 I0. K1.
G0 Z15.
G53 G0 Z0.

(2D Contour1)
G56
G17
G0 X-5.5 Y-13.5
G43 Z15. H10
G0 Z4.75
G1 Z0.75 F7200.
Z-19.25
G18 G2 X-4.5 Z-20.25 I1. K0.
G1 X-3.5
G17 G3 X-2.5 Y-12.5 I0. J1.
G1 Y-2.5
G2 X-1.036 Y1.036 I5. J0.
G1 X0.964 Y3.036
G2 X4.5 Y4.5 I3.536 J-3.536
G1 X75.5
G2 X79.036 Y3.036 I0. J-5.
G1 X81.036 Y1.036
G2 X82.5 Y-2.5 I-3.536 J-3.536
G1 Y-22.5
G2 X81.036 Y-26.036 I-5. J0.
G1 X79.036 Y-28.036
G2 X75.5 Y-29.5 I-3.536 J3.536
G1 X4.5
G2 X0.964 Y-28.036 I0. J5.
G1 X-1.036 Y-26.036
G2 X-2.5 Y-22.5 I3.536 J3.536
G1 Y-12.5
G3 X-3.5 Y-11.5 I-1. J0.
G1 X-4.5
G18 G3 X-5.5 Z-19.25 I0. K1.
G0 Z15.
M5
G53 G0 Z0.

(2D Contour2)
M9
M1
T4 M6
M88
S12000 M3
G54
G17
G0 X77.5 Y19.5
G43 Z15. H4
T6
G0 Z4.75
G1 Z0.75 F10000.
Z-2.25
Y-0.5
Y-24.5
Y-44.5
G0 Z15.
G53 G0 Z0.

(2D Contour2)
G55
G0 X77.5 Y19.5
G43 Z15. H4
G0 Z4.75
G1 Z0.75 F10000.
Z-2.25
Y-0.5
Y-24.5
Y-44.5
G0 Z15.
G53 G0 Z0.

(2D Contour2)
G56
G0 X77.5 Y19.5
G43 Z15. H4
G0 Z4.75
G1 Z0.75 F10000.
Z-2.25
Y-0.5
Y-24.5
Y-44.5
G0 Z15.
M5
G53 G0 Z0.

(Drill1)
M89
M1
T6 M6
M88
S6366 M3
G54
G0 X67.5 Y-12.5
G43 Z15. H6
T30
G0 Z5.
G98 G81 X67.5 Y-12.5 Z-22.553 R2.75 F1145.92
G80
G0 Z15.
G53 G0 Z0.

(Drill1)
G55
G0 X67.5 Y-12.5
G43 Z15. H6
G0 Z5.
G98 G81 X67.5 Y-12.5 Z-22.553 R2.75 F1145.92
G80
G0 Z15.
G53 G0 Z0.

(Drill1)
G56
G0 X67.5 Y-12.5
G43 Z15. H6
G0 Z5.
G98 G81 X67.5 Y-12.5 Z-22.553 R2.75 F1145.92
G80
G0 Z15.
M5
G53 G0 Z0.

(2D Chamfer1)
M89
M1
T30 M6
S12000 M3
G54
M8
G0 X69.45 Y-12.5
G43 Z15. H30
T2
G0 Z5.
G1 Z2. F1500.
Z-3.75
G3 X65.553 Y-12.6 I-1.95 J0.
X69.44 Y-12.3 I1.947 J0.1
G0 Z15.
G53 G0 Z0.

(2D Chamfer1)
G55
G0 X69.45 Y-12.5
G43 Z15. H30
G0 Z5.
G1 Z2. F1500.
Z-3.75
G3 X65.553 Y-12.6 I-1.95 J0.
X69.44 Y-12.3 I1.947 J0.1
G0 Z15.
G53 G0 Z0.

(2D Chamfer1)
G56
G0 X69.45 Y-12.5
G43 Z15. H30
G0 Z5.
G1 Z2. F1500.
Z-3.75
G3 X65.553 Y-12.6 I-1.95 J0.
X69.44 Y-12.3 I1.947 J0.1
G0 Z15.
G53 G0 Z0.

(2D Chamfer2)
G57
G0 X66.95 Y-12.
G43 Z20. H30
G0 Z10.
G1 Z7. F1500.
Z-1.5
G3 X63.053 Y-12.1 I-1.95 J0.
X66.94 Y-11.8 I1.947 J0.1
G0 Z20.
G53 G0 Z0.

(2D Chamfer2)
G58
G0 X66.95 Y-12.
G43 Z20. H30
G0 Z10.
G1 Z7. F1500.
Z-1.5
G3 X63.053 Y-12.1 I-1.95 J0.
X66.94 Y-11.8 I1.947 J0.1
G0 Z20.
G53 G0 Z0.

(2D Chamfer2)
G59
G0 X66.95 Y-12.
G43 Z20. H30
G0 Z10.
G1 Z7. F1500.
Z-1.5
G3 X63.053 Y-12.1 I-1.95 J0.
X66.94 Y-11.8 I1.947 J0.1
G0 Z20.

M5
M9
G53 G0 Z0.
X40.
G53 Y0.
M30

%
Keith Clausen
Gcode In Motion

SolidWorks 2021
HSMWorks 2022
Fusion360 - Manufacturing Extensions
0 Likes
Message 19 of 46

keith_clausen
Collaborator
Collaborator

I ran through Dave's file and posted it different ways using the Hass (pre-NGC) post and all seems as it should be. My guess is that his post is possibly out of date, may have hard coding for the WCS management and or a WCS reset in the post that is preventing the code from posting correctly.

Keith Clausen
Gcode In Motion

SolidWorks 2021
HSMWorks 2022
Fusion360 - Manufacturing Extensions
0 Likes
Message 20 of 46

Anonymous
Not applicable
Hi Keith,

Thanks for looking into this for me.
I first discovered my issue with a Mazak post that I modified from the Autodesk generic Mazak.cps . I then tried posting with the generic Haas to try and narrow it down to an issue with my PP, but the issue was still there.

My example problem code was posted using the Autodesk generic Fanuc.cps.

As far as I know we are updated to the latest release version of Inventor HSM and the generic posts were selected by me at random from HSM’s generic posts folder (which would be updated with any updates of Inventor, correct?)

I’m on U.K time, so I’ll put up the Mazak post I’m using up for you when I get into work tomorrow.

Thanks again
0 Likes