People here are a bit touchy about just giving a post, I think it's part of the forum rules not to request one here and to call your reseller. Everyone here however is very knowledgeable and helpful when it comes to help you modify the current post. You can start a basic post and take it from there.

It is Nov 4, 2011 Im still checking everyday to the download page of MasterCAM. Reading about the enhacements makes me even more anxious about wanting the file to be available. Im keeping my fingers crossed !

Can you post some a pic of the geometry to get a better idea. Some of us are more visual ! Are you surfacing with a DiscMill ? or just contouring ?

Blend takes longer to calculate, unless you have a monster of a PC with Xeon. The direction of flowline is controlled by the underlying grid seen when the surface is unshaded, nice trick with Mold PLus to be able to change the direction and machine it then. Great tip !

Post an image of what you want to machine, the chaining is a bit different than conventional chaining methods.

Here is what we have at work, we have Fadals with 32MP and 88HS controls. They both work OK with the same post and the following settings. What post do you have ?

Glad to help, you would have placed the pspc block in the Tool Comment/ Manual Entry Section # -------------------------------------------------------------------------- # Tool Comment / Manual Entry Section # -------------------------------------------------------------------------- ptoolcomment #Comment for tool... ... ... pspc # Creates spaces based tool level setting if sav_spc = one & omitseq$ = no$, " " Just out of curiosity what was in those lines in your post ?

How do you create a nethook? where do you create the file and how do you have Mastercam recognize it.

That works for the MPMaster post but what about the In-House, how about you post a snippet of the block that outputs the bad code so we can take a look at it.

Wouldn't removing pfxout, pfyout not place the points for the first hole ? I think it should be more like this Colin pmisc2$ #Canned Misc #2 Cycle - G84.1/G74.1 pdrlcommonb feed = (1 / n_tap_thds$) * speed pbld, n$, *sgdrill, *sgdrlref, pfzout, pcout, prdrlout, *tap_speed, *feed, e$ pfxout, pfyout, e$ pcom_movea I will make the mod on our post and post again, our Fadals also need a G84.2 to prepare for Rigid taping before the G84.1. Does your need this also BTA ?

Look at the post lines in the error report 29 Oct 2011 04:22:00 PM - <2> - PST LINE (766) - Label has not been defined[7] 29 Oct 2011 04:22:00 PM - <2> - PST LINE (769) - Label has not been defined[4] 29 Oct 2011 04:22:00 PM - <2> - PST LINE (2222) - Label has not been defined[7] If you open the post in the Mastercam editor towards the bottom right the is a line counter. You might have used a Label that has not been defined or you didnt define it properly. Dont forget that you have to place preadbuf5 if (opcode$ > 0 & opcode$ < 16) | opcode$ = 19, [ n$, pspc, scomm_str, "MAX - ", *max_depth, scomm_end, e$ n$, pspc, scomm_str, "MIN - ", *min_depth, scomm_end, e$ ] In the ptlchg$ and psof$ blocks like Chris mentioned; after the M06 string for the info to come out on every toolchange.

Wow 1000SFM for Aluminum is fairly low, I use 1000 for Mild Steel only because of the limitation on the Machine (Fadal). Imco is a great endmill, great results with their M550 series even at 2.5"LOC.

How about we all use vericut and that will solve all our problems.

I run mastercam on Windows 7 X64 no problems. All they eye candy is turned on, have you tried uninstalling and reinstalling the Server NetHaspX; this sounds more of a server problem than a workstation problem. We have had that issue here at work but not that often, the Admin simply restarts the License Sever and Voila.

What controls are they, do you have the manuals ? usually from there you can determine if they will. If they are different controls and new features have been added then a modification will need to take place.

Are you rolling the toolpath, post a pic of the geometry identify the problem better. If you are in fact placing the geometry at the defined angles than it might be what gcode mentioned, it could also be you Max/Min angle tolerance in your Control Definition.

How bout PM is private message.

Ill have a crack at it if you still need help, im leaving work right now but will try to tackle it at home; if not tomorrow here at work. What you want are pretty simple fixes, easy money if you ask me.

I have no idea how you got N180 G43 H3 Z1. scoolant N190 / M08 Unless you moved scoolant and did not comment it out pbld, n$, "G43", *tlngno$, pfzout, next_tool$, e$ # scoolant <------- like this pbld, n$, pfbld, scoolant, e$ (new line ) That would have given you the spelled out scoolant you got, I agree with Colin editing the M8 string to /M8 would have saved you the trouble to add the "/". Then again you wanted it on a separate line so moving the scoolant was required. Glad my little input was able to help you, as many others have helped me.

Same here but for our Fadals we use an E instead of H, here is my code; fmt E 4 g_wcs #WCS G address Then down below in the pwcs block if wcs_mode = two, # 'E' fixture offset mode [ sav_frc_wcs = force_wcs if sub_level$ > 0, force_wcs = zero if workofs$ <> prv_workofs$ | (force_wcs & toolchng), [ g_wcs = workofs$ + 1 *g_wcs ] force_wcs = sav_frc_wcs !workofs$ ] Then at the default miscellaneous interger values # Default Miscellaneous Integer Values - Read during post update only - Set in CD # -------------------------------------------------------------------------- 301. Work Coordinates [0-1=G92, 2=E's] (mi1)? 2 302. Absolute or Incremental [0=ABS, 1=INC] (mi2)? 0 303. Reference Return [0=G28, 1=G30] (mi3)? 0

pbld, n$, *sg28ref, "Z0.", e$ pbld, n$, *sg28ref, "X0.", "Y0." [if rot_on_x > zero, "A0."], e$ pfbld, n$, sg92, *xh$, *yh$, *zh$, e$ This is what my post uses, search for peof$ this is the end of file block.

Agree, feed at .01-.020/rev; you could also use a finishing insert that will actually break a chip at .005/rev. We use Sumitomo ESU breakers and they leave a shiny finish on all our parts, pretty smooth to the touch.

What is this The Circle™ ? I keep seeing this on several member's signatures.

You have to make sure that the "scomm_str, scomm_end" are defined as parenthesis in your post, in mine its "sopen_prn, sclose_prn" so I got a OP1 with out parenthesis, you also have to define snull in the Misc. Strings as "" unless you have an MPMASTER based post.

I have a custom POST for Fadal,I can help you out to midify yours. Please post an example of code and what you would need it to be in order for your machine to work. Then I can show you the modified postblocks that make G84.1 work.