Fanuc Post Processor For Powermill
Martta
I don't know I get it right or not but it's seems I had to edit this htmls so I did but after I edit this html files and delete the lines I want nothing changed after write a NC program, everything is like before
I am not sure if I understand correctly what you have done, but no html's need to be edited for your request. The html's that I have shown you are for reading, not for editing. Maybe it would be better if you contact your support.
I followed BS_agru's method and output a dmp file of the fanuc15m post, i did have to specify a location for the output that i was permitted to write to, C:\temp\fanuc15m.dmp change extension from .txt to .opt
Mpfan and Mpmaster are good choices for a 3 axis post, but if your Hitachi Seiki is one of the 4 axis horisontal machines, then they will not work, at least not for simultaneous 4 axis work. But you might contact us, we have delivered post processors for 4 axis Hitachi Seiki machines. You should e-mail [email protected], specifying the model and axis setup.
Both Mpfan and Mpmaster (which is entirely based on Mpfan) will support 4-Axis positioning (toolplane indexing), any of the rotary substitution toolpaths, and 4-Axis moves created by any of the multiaxis toolpaths. For a horizontal machine, a small amount of modification will be necessary (e.g. vmc : 0, rot_on_x : 2, etc). In Mpmaster, it's a matter of removing comments before the 'typical horizontal' section.
Having said that the rotary axis calls on the Hitachi Seiki may be different than those produced my Mpfan or Mpmaster, although this has not been my experience. I should mention though that Christian obviously knows his stuff and has 'zinged' me a few times in the past - so I'm prepared to stand corrected!
This is a 3-Axis machine. After James had replied I checked with Mastercam and asked for there suggestion. Greg of Mastercam recommended the MPFan and was not aware of the MPMaster post. I informed him about Mr. Mayette's recommendation and he suggested I pursue the MPMaster post because "if anyone would know, James Mayette would." Thanks for the help everyone. I am going to start with the MPMaster and make post modifications as necessary.
If you do not need the subprogram support from version 8, you might be best off by choosing the Mpfan post from version 6, and updating it by using the Uptxt8.dll C-Hook. The Mpfan post from version 6 is far less complex, so it will be easier to edit, but the drilling cycles may need some more work (that is not likely on a Fanuc control, though).
I also got the generic 3-axis haas machine definition to work, however the post always included the tool-change, tool probe, and tool length compensation canned cycles in them. Those will cause prompts on the Onefinity controller and will result in an offset for zero when the program runs on the router.
Those first few lines of the gcode had to be manually removed. But I got tired of having to do that so I edited the postprocessor file (.pst) script to remove those outputs and everything works now.
Be aware that once the settings of the machine definition are changed/saved to remove canned cycles you will usually need to close Mastercam and open it again for the all of the changes to be applied to any existing programs.
Although you probably will not find a post that you can download and that works perfectly without editing, there are few things that might help you out. The link below will bring you to the PTC GPOST Central Resource page. Although this site has not been updated in years (2004-2005), it still has a lot of useful information regarding post processors. There is a link on the bottom of this page titled "PRODUCTION POSTPROCESSORS". This will bring you to a page that has a few dozen downloadable posts. These are a great place to start and you may find one that gets you 90% of the way there. There are also a lot of useful training presentations and other files, so make sure to browse through all of the links.
I have gone in here a number of times to get a good starting post and then have updated it to meet my needs. I never had any formal training on creating posts; just simply used the training available on this link and have had pretty good success.
Hello everyone,
I am experimenting with a postprocessor for PowerMill and need some advise.
The postprocessor is for Kuka KR150, i am trying to use it for Kuka KR2150 - or KR150/2 - series 2000
I am getting errors when trying to execute the code on the robot. Not sure if i am doing all of this right as i am tottaly new to robots, thats why i am attaching the src and dat files from the postprocessor. i am attaching also the error screen.
Any help will be appreciated! Thanks!
The "Commanded Torque" errors are a bit more unusual -- the path planner appears to believe that executing the current motion will exceed the torque limits of the axis. This is a predictive error rather than a realtime error. I would recommend checking the acceleration settings and the load data.
Thank you SkyeFire, where should i look for these?
Also, all this code is coming from the postprocessor - how can i limit the axis 5 singularity?
I am not sure if i need to do something specific for the robot base information?
I did the tool calibration (4 point) and base calibration (XYZ), may be i need to do something else as a calibration?
Thanks again!
Have you performed a payload analysis of your end effector? Mass, CG, and inertial moments must all be entered into the LOAD_DATA array for the tool number you are using. Does your robot have the Load Determination tech package installed?
As for the A5 singularity, there's only one way to address it, really: Don't make that move. If your Powermill simulation is driving the robot through a linear motion that drives A5 too close to zero, you can't make that move. The only alternatives are to reduce the robot's speed enormously (which, as A5 approaches zero, becomes less and less possible), change the move from LIN to PTP (not possible during a milling cut motion), or allow the TCP orientation to "float" during the move (also not something you want to happen during a milling cut motion).
There's nothing you can really fix in the postprocessor to handle A5 singularity -- this issue has to be addressed at a higher level. Usually, when simulation shows that a required motion will drive the robot too close to A5 singularity, the tooling design is altered in such a way that all critical LIN motions can be performed without A5 coming close to 0.
Hi SkyeFire, and thank you for the time
finally i have some success with this postprocessor - the robot started moving
I think the problem is with the correct base and tool
Tha tool is fine, but when i checke the base it was something like null, not base N1 which was supposed to. when i changed to base 1 it started to execute the code.
Today i will play a bit more, unfortunately, i can use the roboto only out of the working hours, but anyway it is very exciting
The output file is a series of PTP points (which as I learn more doesn't seem to be right for a milling operation.... given the robot will not necessarily take a direct line between points as it would with Lin command.. )
Hello,
Long time not working in Powermill, but as i remember my issue was caused by singularities and the speed when i have those - you should move the robot VERY slow when you see it is close to singularity
As i worked with Powermill without the Powermill robot plugin - it was impossible to say in advance when i have singularities and to avoid them. That was the reason to go for Sprutcam and i am still using it
Something else - as you are saying your code is all PTP motions - that is wrong - you should use LIN or CIRC motions only when milling. and PTP only for air moves.
Another issue i had at the time - i did the robot calibration, but only with XYZ 4point - that gives ONLY the TCP point coordinates, but not the tool vector. You should be sure that you have the right tool vector used in the robot - that is the A, B and C numbers - did you do it?
When you program manually the tool orientation is not important as you do it by hand.
What Powermill version are you using? What is the postprocessor?
Another person who saw it running said it was very slow... I think this might be due to a huge amount of PTP data produced (drip fed by CamRob) instead of LIN commands... thanks for your confirmation about this being incorrect!!
When importing the model into powermill the axis is in solidworks orientation with Y axis vertical. I then create a workplane aligned with my Base system (z axis vertical and x and y plane creating the surface on which the part sits.... I thought this is all that would be required with all PTP data created relative TCP and this Base/workplane.
My tool axis in powermill and Kuka are not the same... kuka using standard x axis for tool direction but powermill is using z or y. I didn't originally think this would matter but maybe because of the Status and Turn information included in the PTP command it does!!! (Learning heaps... and so much more to go!!). I haven't been able to find how to change the tool coordinate axis orientation in powermill but did find in some reading tonight that the MTD file might be the place to do this and this is why I couldn't find an option within powermill frontend.
I use powermill, I had the same problems even gentlemen of delcama could not master it.I started to do the trial and error method myself, my wniosek is a well set up utility and database and typing this data well into powermilla.Attach my postprocessor that I use
Hello, i've have this problem and i've solved change the ptp xyz for the ptp a1, a2,a3... only for review if the robot reaches the position correctly the problem almost always is the base or the coordinate with the code was used can be tool, base, dynamic base can you review with the actual base and tool and position of robot for review.
Best regards