MultiAxis Linking

[PcRobotic]

Hello everyone,

   I'm using 2017 version now and there is a nice function such as "MultiAxis Linking", it is much accurate for BACK PLOT on Horizontal and 4th Axis programming.  However, when I posted out most of the G-CODEs are FUNKY such as safety line of the second operation is not there (my post is always safety line on the second operation if different tool).

 

  I wonder where can I start with?  Is MultiAxis Linking is such as another parameter number that I have to define or how do I call out this function to my post?  Honestly, I like this function because it is great.  It's just needs to be adjusted in the post, I think.

 

 

 

 

Thank you for your help,

   S.Luong

 

+++++++++++++++++++++

Sample G-Codes

O1000G91 G0 G30 Y0. Z0.( TOOL - 3  DIA. OFF. - 3  LEN. - 3  DIA. - 1.9685 )(180 DEG 50MM ROUGH WELD PREP = CUT#1)T3M06G20 G94M38G0 G40 G80 G90G0 G90 G54 X4.407 Y5.1929 B180. S1455 M3G43 H3 Z17.4359 T51Z12.9975G1 Z12.6475 F50.G3 X4.3726 Y5.4608 R.9857(CUTTING...)X-4.407 Z17.4359(0 DEG 50MM ROUGH WELD PREP = CUT#2)Z12.9975G1 Z12.6475G3 X-4.3726 Y22.5893 R.9857(CUTTING...)G3 X-4.407 Y5.1929 R.9857G0 Z17.4359G64G91 G30 Y0. Z0. M5( 1/4 X 4" INGERSOLL SLOTTER   TOOL - 51  DIA. OFF. - 51  LEN. - 51  DIA. - 4. )T51M6M01G20 G94M38G0 G40 G80 G90G0 G90 G54 X-5.3243 Y5.5321 B0. S1050 M3G43 H51 Z17.178 T41M8X-6.2267 Y5.8713 Z16.8719(CUTTING...)X3.2096 Y-24.8657 Z17.6955(180 DEG INGERSOLL 4"X  1/4" SLOTTING CUTTER = CUT#3)X-3.2096 Y24.8657 Z18.7269(Cutting...)Z0. HOME HERE....TOOL CHANGE HERE...SAFETY LINE HERE....X3.2096 Y3.1843 Z18.7269(0 DEG INGERSOLL 4" X 1/4" SLOTTING CUTTER = CUT#4)Z13.1745(CUTTING...)G0 Z18.6916M9G64G91 G30 Y0. Z0. M5( MA FORD 1/2" X 4 FL END MILL   TOOL - 41  DIA. OFF. - 41  LEN. - 41  DIA. - .5 )T41M6M01G20 G94M39G0 G40 G80 G90G0 G90 G54 X2.3516 Y23.9411 B0. S2300 M3G43 H41 Z18.8539 T21M8X1.2861 Y23.8164 Z18.9564(CUTTING...)X-5.0741 Y23.0685 Z18.3099(O DEG 1/2 RADIUS FINSH = CUT#5)Z16.4868Z12.9975G1 Z12.3975 F100.G41 D41 X-5.1503 Y22.9393 F23.(CUTTING..)X1.0274 Y6.5574 Z17.2194(0 DEG BEAM SLOT = CUT#6)Z12.9663G1 Z12.6163 F100.X.8975 Y6.6324 F23.G3 X.8225 Y6.6525 R.15(CUTTING..)X-4.8697 Y-5.0384 Z16.5484(180 DEG 1/2 RADIUS CLEAN UP = CUT#7)X4.8697 Y5.0384Z12.7475G1 Z12.3975 F100.G41 D41 X5.0197 Y5.037 F23.G3 X5.1712 Y5.1855 R.15(CUTTING..)G1 X1.0274 Y21.1926G0 Z17.2194M9G64G91 G30 Y0. Z0. M5============> why retract here? (it should be like this)( MA FORD 1/4 DIA 5 FLUTE ENDMILL   TOOL - 21  DIA. OFF. - 21  LEN. - 21  DIA. - .25 )T21M6M01G20 G94M39G0 G40 G80 G90 ============> why tool change here? (it should be like this)G0 G90 G54 X-.0723 Y-21.3141 B180. S3500 M3G43 H21 Z17.2498 T53M8X.8831 Y-21.4356 Z17.2274(CUTTING..)(1/8 RADIUS B180. = CUT#9)X-3.7212 Y21.8 Z16.7158(CUTTING..)X3.7212 Z16.7158(1/8 RADIUS B0. = CUT#10)Z12.9975G1 Z12.6175 F25.G41 D21 Y6.3G3 X3.6713 Y6.35 R.0499(CUTTING..)G1 G40 Y21.8G0 Z16.7158M9G64G91 G30 Y0. Z0. M5( SECO WELD PREP CUTTER    TOOL - 53  DIA. OFF. - 53  LEN. - 53  DIA. - 4. )T53M6M01G20 G94M38G0 G40 G80 G90G0 G90 G54 X2.8388 Y22.0814 B0. S530 M3G43 H53 Z16.8881 T3M8X1.9485 Y22.3629 Z17.0138(CUTTING..)X-3.4196 Y24.0515 Z16.7801(0 DEG SECO WELD PREP CUTTER = CUT#11)Z18.6897Z12.9975G1 Z11.6775 F100.G41 D53 Y22.8475 F14.X3.4196G40 Y24.0657G0 Z13.1775Y3.9843Z12.9975G1 Z11.6775 F100.G41 D53 Y5.2025 F14.X-3.4196G40 Y3.9985G0 Z18.6897X-4.3947 Z18.4848(CUTTING..)X-3.4196 Z18.6897(180 DEG SECO WELD PREP CUTTER = CUT#12)X3.4196 Y3.9985Z13.4975G1 Z11.6775 F100.G41 D53 Y5.2025 F14.(CUTTING..)G40 Y24.0515G0 Z18.6897M09T3G91 G28 X0. Y0. Z0. M5G64G0B0.M30

[crazy^millman]

Look for what you need in 2018. Many post builders are not happy about how Multiaxis link sends nothing about what it is doing to the NCI. Best to old school it with curve 5 axis if you need the flags. If you don't then it is a great toolpaths, but when you need the flags for the post there is nothing from it to use that I am aware of.

[PcRobotic]

5Th Axis Consulting Group,

   It sounds like 2017 is not your favorite version, me too.  However, I have to use it because my company just "UNINSTALLED" all OLDER VERSION and decided to use 2017.

 

 

 

Thank you for your tip.

[crazy^millman]

5Th Axis Consulting Group,

   It sounds like 2017 is not your favorite version, me too.  However, I have to use it because my company just "UNINSTALLED" all OLDER VERSION and decided to use 2017.

 

 

 

Thank you for your tip.

 

2017 is good and I use what I got, but these flags have not been around since it was introduced so doesn't matter the version and it is my understanding it will be the 2018 version before they show up.

[PcRobotic]

2017 is good and I use what I got, but these flags have not been around since it was introduced so doesn't matter the version and it is my understanding it will be the 2018 version before they show up.

 

For me, I have to admit it is "GOOD".  Good for organization most of the time, it is just matter of taking time to learn the new interface (it took me 3 weeks to get used to and learned all functions).

 

Some functionalities have changed too, especially WCS manager is drastically changed the NAME and FUNCTIONs.

 

2017 still have few bugs such as BACK PLOT not doing right on horizontal, MACHINE SIMULATION is definitely need much more things to improve such as COLOR LOOP NOT THERE, ROTATION IS WRONG SHOWING....  and.... and... MULTIAXIS LINKING is also a big issue too....

 

 

 

I'm hoping they listening to us now because those bugs really lead to machine crash and fatal accident on operators. Hopefully they update those next update patch not waiting for another 12 months like we normally do.

 

 

Thank you 5th Axis Consulting Group for feedback.

[crazy^millman]

For me, I have to admit it is "GOOD".  Good for organization most of the time, it is just matter of taking time to learn the new interface (it took me 3 weeks to get used to and learned all functions).

 

Some functionalities have changed too, especially WCS manager is drastically changed the NAME and FUNCTIONs.

 

2017 still have few bugs such as BACK PLOT not doing right on horizontal, MACHINE SIMULATION is definitely need much more things to improve such as COLOR LOOP NOT THERE, ROTATION IS WRONG SHOWING....  and.... and... MULTIAXIS LINKING is also a big issue too....

 

 

 

I'm hoping they listening to us now because those bugs really lead to machine crash and fatal accident on operators. Hopefully they update those next update patch not waiting for another 12 months like we normally do.

 

 

Thank you 5th Axis Consulting Group for feedback.

 

Were a Verification software is key.

[Grievous]

Yep...same problem here. I think the new Tool change option from Safety Zone is causing the issue. There is no option to not have this option disabled somehow. It will "feed" a tool change regardless of what option from those 3 you choose. Post must be changed. I just temporary disabled the switch in my post who was causing the retraction, then post my tool path. I didn't have time to look into it, 'cause different scenarios...and no time...

Anybody else looked more into that?

[civiceg]

On a horizontal I prefer a full rapid retract in the Z when doing rotations, mainly because of different pallet sizes in use. 

[Colin Gilchrist]

On a horizontal I prefer a full rapid retract in the Z when doing rotations, mainly because of different pallet sizes in use. 

 

Have you considered a "User Defined" retract point, instead of full Z retract? This should be easy to tie into a Macro Variable on the machine, and have a Sub Program that sets the retract value, based on the specific pallet in use. I've setup a lot of machines where "G30" was that value, instead of G28, and often there would be multiple options, using "P1", "P2", ect...

[civiceg]

The reasoning behind this is, there were 7 or so different pallet sizes and a variety of sub-plates, so a retract that was safe on one pallet/sub-plate may not be safe the next time the job was setup. Jobs were only reposted for process and revision changes.

 

Operators would not use the probes and some horizontals didn't have them, so you would have to key in the variable for the pallet being used. I no longer program everyday, but I will keep the retract/variable idea in mind for future applications. 

[harryhome]

 

 

Were a Verification software is key.

 

 

Verification won't help with buggy software.

 

MCX has me perplexed. 

There's a lot of great new additions, but at the cost of losing trusted legacy functions, and introducing unreliable buggy functionality. 

 

Be very careful translating anything in MCX