Program simulation and Machine position....Crashes**

Program simulation and Machine position....Crashes**

clifford.gage
Enthusiast Enthusiast
1,371 Views
17 Replies
Message 1 of 18

Program simulation and Machine position....Crashes**

clifford.gage
Enthusiast
Enthusiast

I am having issues when I send the program out to the machine, the simulation and the actual position of the machine don’t look the same. This has caused a few crashes for us.

 

This one shows my program, you can see the head is facing towards us and the machine position for A and C axis is the same as the nc code I have written.

 

1.PNG

 

 

This picture shows the nc code on the machine, it is the same as the program

 

2.PNG

 

 

 

This picture shows the machine, the head is positioned the wrong way. It,s 180 degrees off on the C axis.

 

3.PNG

 

 

I was thinking would this be that the machine is going the quickest way to the position.

 

For example in this case from the home position it had to rotate 27.48 degrees to reach that position in picture 3, but to reach the correct position it would have to rotate 152.52 degrees.

Just a thought.

 

Would there be a way to fix this?  As it’s causing major issues for us as we have very long programs and have to leave the machine running a lot.

 

Thanks

 

Clifford Gage

 

 

 

 

 

0 Likes
Accepted solutions (1)
1,372 Views
17 Replies
Replies (17)
Message 2 of 18

craig.shipley
Autodesk Support
Autodesk Support

Hi Clifford

 

There's one or two things to try but if we are to go any further we'll need some data (project, post, MTD).

 

I am assuming you are using orientation vectors along with the "use orientation vectors calculated during simulation" ?

 

Please provide further information.

 

Thanks

 

Kind Regards

0 Likes
Message 3 of 18

clifford.gage
Enthusiast
Enthusiast

Yep, I'm using  orientation vectors.

I've attached the program.

What's MTD?

0 Likes
Message 4 of 18

craig.shipley
Autodesk Support
Autodesk Support

Machine Tool Definition (the machine simulation file you use inside PowerMill).

 

This .mtd file AND folder with machine models in should be zipped and sent across please, along with your post processor.

 

Thanks

 

Kind Regards

0 Likes
Message 5 of 18

clifford.gage
Enthusiast
Enthusiast

I've attached the post and MTD

0 Likes
Message 6 of 18

iamcdn79
Mentor
Mentor

You need to upload all of your files for the mtd including the dmt files located in the subfolder


Intel Core i9 13900KF CPU
128 GB Kingston Beast DDR4 SDRAM
PNY RTX A2000 6GB Video Card
WD 1 TB SSD Hard Drive
Windows 11 Pro

0 Likes
Message 7 of 18

craig.shipley
Autodesk Support
Autodesk Support

Hi Clifford

 

Thanks for the files but the MTD should have a folder next to it (Belotti_S.P.A_NAVY_6062) that needs to be attached to.

 

Thanks

0 Likes
Message 8 of 18

clifford.gage
Enthusiast
Enthusiast

Ok. Attached.

 

0 Likes
Message 9 of 18

TK.421
Advisor
Advisor

I may have missed it in your post, but I didnt see what version of powermill you're running?

 

this used to happen to me all the time, but powermill 2019.2.2 seems to have fixed this. I have yet to run into it.

 

 


the numbers never lie
0 Likes
Message 10 of 18

iamcdn79
Mentor
Mentor

I was told that the machine kinematics must match between the post and mtd file but I have noticed that your X and Y axis kinematics do not match  but not sure if that matters because I have that same thing where the Y axis does not match in one of my 5 axis machines which was setup by a Post support employee.

 

One quick thing to check is if the home position matches between your Powermill simulation and your actual machine. Can you postion your machine at C 0 A 0 and check if it looks like the attached image and that it has not been changed by 180 deg in the C axis?

 

Capture.PNG


Intel Core i9 13900KF CPU
128 GB Kingston Beast DDR4 SDRAM
PNY RTX A2000 6GB Video Card
WD 1 TB SSD Hard Drive
Windows 11 Pro

Message 11 of 18

craig.shipley
Autodesk Support
Autodesk Support

Thanks Clifford.

 

You may have noticed I have opened a support case for this (Case #: 15510081) but I will also keep this post updated for the interest of others.

 

Kind Regards

0 Likes
Message 12 of 18

clifford.gage
Enthusiast
Enthusiast

I didn't notice that. Thanks

0 Likes
Message 13 of 18

clifford.gage
Enthusiast
Enthusiast

Yep thats the way the machine looks in the home position

 

0 Likes
Message 14 of 18

craig.shipley
Autodesk Support
Autodesk Support

Clifford

 

Can you please confirm that the image shown has your machine in the HOME position according to the MTD and that it matches your actual machine.

 

Note the WORLD workplane showing the axis directions, these also need to match.

 

Kind Regardsmachine home.png

0 Likes
Message 15 of 18

craig.shipley
Autodesk Support
Autodesk Support

Hi Andre

 

They do need to match, but the way the post & MTD label the axis order are different, so you have to compensate for this...

 

In this post, the X&Y are in the table, but in the MTD X&Y are in the head, so the direction is opposite when this happens (-1 for post, 1 for MTD).

 

Does that make sense?

 

Kind Regards

0 Likes
Message 16 of 18

clifford.gage
Enthusiast
Enthusiast

yea that's the home position 

Capture.PNG

0 Likes
Message 17 of 18

clifford.gage
Enthusiast
Enthusiast

I think I know what you are saying. Because in this machine the head rotates instead of the table, it's causing issues.

 

How do i fix this ?

Thanks

0 Likes
Message 18 of 18

craig.shipley
Autodesk Support
Autodesk Support
Accepted solution

For the benefit of the forum post...

 

First things first, the component is being aligned on the machine using a probe... so it's not sitting exactly as we see inside PowerMill, despite the values in the control looking the same (i.e. there's an offset in the control which aligns the part).

This is the underlying issue.

 

However, it seems the post processor being used isn't the one that was originally provided for this machine.  I have now provided the original post and I am told that the simulation / code/ machine now match.

This is in the testing stage but for the benefit of the forum post appears to be solved.

 

@clifford.gage feel free to mark this as a solution as and when you are satisfied with the post I sent across.

 

Kind Regards