machine pivot / tool lenght in gpost

[prejar]

I am trying to write a post for a 5-axis Thermwood with 91000 controller, using gpost. I have the pivot option in gpost set to the pivot lenght of the machine.
After posting Iverify the post by using Vericut.


My tools eithercut way above the intended surface or gouge the surfaceI am trying to machine. I think this is probably due to my tool lenghts in Pro/ Manufacturing not being transferred to the post.


I am new at this , could some one please explain how I can transfer my this info to Gpost ?


AlsoI presently use an old version of ICAM, where we actually have a tool list in the form of a .TXT added to the post.

 

[appinmi]

Turn the "pivot" option off, or at least set it to zero. Then re-post the CL file and play it with vericut. See what happens. Normally, you do not need the "pivot" option on the get a good NC code.

 

[peterbrown77]

You need to add the parameter "GAUGE_Z_LENGTH" to your tools in order for it to be transferred to Vericut (if using solid tools) or fill in the appropriate value for it in the "Settings" tab of Tools Setup if using parameter tools.





Regards
Edited by: peterbrown77

 

[sohail abbas]

just send me the CL file, the post processed file and the value of Pivot Distance,


so that i can have look where the problem is?

 

[prejar]

sohail


2006-10-29_011731_gpost.rar


i have attached the ncl file, pocessed file and lst file.


i have also attached a working file that was made with icam


the pivot lenght is 10.483


i havepivot lenght in gpostset at zeroinstead i am using the "GAUGE_Z_LENGTH" option my first tool posts okay for 'x' and 'y' values but 'z' ,'a', 'c' axes are wrong


any help will be appreciated.

 

[prejar]

hello


i have got this far with my thermwood 5-axis post-processor using gpost.


y, a and c axes are posting fine. x and z are off by my tool gauge lenght.


this is what i get:


N12 %LOAD T124
N13 G92 X0.0 Y0.0 Z4.98
N14 S0 M3
N15 G0 X20.8852 Y-12.6807 A90.028 C90.0
N16 Z5.0
N17 Z2.8827
N18 G1 X19.8852 Z2.8832 F500.0
N19 Y1.7669 Z2.892
N20 Z5.0 F200.0
N21 G0 X20.8849 Y-12.7167
N22 Z2.1623
N23 G1 X19.8849 Z2.1628 F500.0
N24 Y-11.1448 Z2.1094
N25 Y-9.5725 Z2.0719
N26 X19.8848 Y-7.9999 Z2.0505
N27 Y-7.8563 Z2.0493
N28 Y-1.1857 Z2.0527
N29 Y-0.2203 Z2.0669
N30 Y0.7448 Z2.0933
N31 Y1.7095 Z2.1322
N32 Z5.0 F200.0
N33 G0 X20.8845 Y-12.751
N34 Z1.3546
N35 G1 X19.8845 Z1.3551 F500.0
N36 Y1.6554 Z1.3639
N37 Z5.0 F200.0
N38 G0 X22.628 Y-0.0908 A93.111 C140.094


N161 %LOAD T206
N162 G0 X0.0 Y0.0 Z4.98 A90.0 C0.0
N163 S0 M3
N164 G0 X20.7852 Y-12.6807 A90.028 C90.0
N165 Z5.0
N166 Z2.8827
N167 G1 X19.7852 Z2.8832 F500.0
N168 Y1.7669 Z2.8921
N169 Z5.0 F200.0
N170 G0 X20.7851 Y-12.6938
N171 Z2.6508
N172 G1 X19.7851 Z2.6512 F500.0


this is what I need:


%LOAD T124 (2" DIAMOND X Tool Length as per Tool Table) IN PRIMARY SPINDLE
%A ROTARY PIVOT IS 12.
%SET TOOL HEIGHT HERE
%USE 5" GAUGE
N5G92X0.Y0.Z4.98A0.C0.
N6G01X32.8852Y-12.6807Z3.0A90.028C90.
N7Z-9.1232
N8G1X31.8852Z-9.1227F500.
N9Y1.7669Z-9.1138
N10Z-7.0059F900.
N11G0X32.8849Y-12.7167
N12Z-9.8435
N13G1X31.8849Z-9.843F500.
N14X31.8848Y-9.718Z-9.9311
N15Y-9.1239Z-9.9455
N16Y-8.5035Z-9.9544
N17Y-7.8563Z-9.9565
N18Y-1.1857Z-9.9531
N19Y-.6633Z-9.9475
N20Y-.0603Z-9.9355
N21Y.5212Z-9.9184
N22Y.7102Z-9.9115
N23X31.8849Y1.7095Z-9.8737
N24Z-7.0059F900.
N25G0X32.8845Y-12.751
N26Z-10.6513
N27G1X31.8845Z-10.6508F500.
N28Y1.6554Z-10.6419
N29Z-7.0059F900.
N30G0X30.315Y9.1008Z-7.6512A93.111C140.094


%LOAD T206 (4.8"TALL X .750" Hogger X PER TOOL CHART) IN PRIMARY SPINDLE
%A ROTARY PIVOT IS 13.9
%SET TOOL HEIGHT HERE
%USE 5" GAUGE
N5G92X0.Y0.Z4.98A0.C0.
N6G01X34.6852Y-12.6807Z5.0A90.028C90.
N7Z-11.0241
N8G1X33.6852Z-11.0236F500.
N9Y1.7669Z-11.0147
N10Z-8.9068F900.
N11G0X34.6851Y-12.6938
N12Z-11.256
N13G1X33.6851Z-11.2555F500.





as you can see first tool 'x' and 'z' tool 124posts with a difference of 12, next tool 206 also post with a difference of 13.9.


I would like to write a .filmacro that would extract tool lenght data from a .txt file and and have gpost utilize this during posting.I would like to have gpost calculate the pivot lenght instead of utilizingcontroller offsets.


This makes life easier for our operators, they do not have to mess with any tool tables.We program the pivot lenght and the just set tool lenghts.


thanks in advance for any help

 

[MR_NC]

This may not be what you are after but it is what I do sometimes.

pivot1 = 0
$$ pivot1 = 2.000

rslt=POSTF(02,3,0635,pivot1) $$set the A primary pivot distance

Then I edit the value of pivot1 = to machine setup for pivot distance. This is for a 5x table-table setup I work with. I am not sure it would work as required for a table-head or head-head setup.

I post code based on WORLD numbers and then let Gpost sort the deal out at post time. This plays nice with Vericut. It goes without saying that it would NOT play nice with Vericut without some work if Vericut was checking G-code (the included version does not).

Best regards,
Sean

 

[prejar]

Thanks for taking the time to answer my post Sean!


Ihave a machine with a moving gantry and this would probably not work , however i have been able to write the .fil macro to do what i wanted.


I work with Aluminum honeycomb and we use tools that have varying lenghts so its easier to post this way as supposed to posting with a zero pivot.


I set the pivot distance foreach tool using the'z gage offset' in the Proe Tool Manager and then have gpost capture this value while posting.


I am beta-testing the code now for various scenarios . Itbeen okay so far. I do not have to do any editing after posting.


If you would like to try it I'll email it to you.


Regards


Yaw