While Mastercam is not specifically written to use SLI, as some games are. The requirements of Games is quite different; many frames per second each frame requiring rendering. My experience has been that 2 Geforce cards in SLI outperform one in Mastercam. The areas where you will notice speed improvements is verify, shading and dynamic rotations. The application does not need to be written to specifically support SLI the Geforce driver takes care of it. Check out this article @ Wikipedia: https://en.wikipedia.org/wiki/Scalable_Link_Interface Allan

Quite possible that the chip conveyor is not hooked up to control in any way, and the buttons do nothing. Your Okuma Dealer is: Gosiger Indiana 4627 Independence Square Indianapolis , IN 46203 317-788-1501

Spindle is orienting because of the M6...M19 would orient the spindle as well. You could simply handwheel to the part. Move up in Z an inch or so and program like so G91 G01 Z-1.0 F100.0 G00 Z1.0 G99 This will loop forever, feeding down at 100 inches per min and rapiding up 1 inch and repeat. Allan

This will not be an easy task IMHO The z axis feed for linear motion comes from this postblock: plinout #Output to NC of linear movement - feed pcan1, pbld, n$, sgfeed, sgplane, `sgcode, sgabsinc, pwcs, pccdia, pxout, pyout, pzout, pcout, feed, strcantext, pscool, e$ #Modify following line to customize output for high-speed toolpath #tool inspection/change points if rpd_typ$ = 7, pbld, n$, "M00", "(TOOL INSPECTION POINT - POST CUSTOMIZATION REQUIRED)", e$ You can see that this postblock also outputs motion for X and Y. You will want some logic to check for Z output; then change that addressing of the feed comand. Something like: plinout #Output to NC of linear movement - feed if zabs$ = prv_zabs$, [ pcan1, pbld, n$, sgfeed, sgplane, `sgcode, sgabsinc, pwcs, pccdia, pxout, pyout, pzout, pcout, feed, strcantext, pscool, e$ #Modify following line to customize output for high-speed toolpath #tool inspection/change points if rpd_typ$ = 7, pbld, n$, "M00", "(TOOL INSPECTION POINT - POST CUSTOMIZATION REQUIRED)", e$ ] else, [ result = nwadrs(stre, feed) #change the F to an E for z motion pcan1, pbld, n$, sgfeed, sgplane, `sgcode, sgabsinc, pwcs, pccdia, pxout, pyout, pzout, pcout, feed, strcantext, pscool, e$ #Modify following line to customize output for high-speed toolpath #tool inspection/change points if rpd_typ$ = 7, pbld, n$, "M00", "(TOOL INSPECTION POINT - POST CUSTOMIZATION REQUIRED)", e$ result = nwadrs(strf, feed) # set the feed command back to F ] This logic assumes that you have the stre and strf values set in the post like so: #Address string definitions stri : "I" strm : "M" strn : "N" stro : "O" strp : "P" strq : "Q" srad : "R" srminus : "R-" sblank : "" stre : "E" strf : "F" This edit will not support arc motion with an E command FYI. Allan

14.5 year old topic still relevant and brought to the first page

Hi okumawiz; Is there some reason that the M06 call cannot and currently does not do the checking. Is the M06 a macro call itself? If it is then the check should be done there. In what situation would not having the check preformed be desired? Can the M06 command be mapped to this special macro?

Your NC precision is way too tight @ 0.0000001" you are looking for code to 10 millionths 0.00001", so the NC precision should be set to 10 millionths. The rounding is being done in the post currently and the MP.dll has had issues with that since X when the control definition was implemented. Allan Oh and your minimum arc length of 0.00002" is a disaster waiting to happen IMHO; that should be 0.002. The minimum arc rad of 0.00005" will also bite you; that should be 0.005"

My guess is that this is a lathe and you are in G99. G99 feed per rev ergo no rpm = no movement Try G98 and use feed rates in units/min Probing uses skip feed (G31 or the like) so the feed stops when the probe contacts attempting to use straight G01 commands is a good way to break the stylus off.

FYI: pfxout is a post block call not a variable the p is the givaway. You cannot evaluate the value of a postblock...you most likely want to look at the value of xabs compared to the previous value.

If you put up a zip to go of a simple part file I can sort it out for you. Allan

it looks like you have something set up already if toolcheck = 0, pbld, n$, *t$, "M6", e$ else, ptoolout Look for a switch called toolcheck. The postblock ptoolout most likely has what you need already setup. Allan

The G116 only works if you have the "tool change macro", I've seen very few machines with the macro. The macro is nothing more than a .sub file with the VATOL logic. There are switches in our master based posts, not sure what you are using as a base post. To add this in is fairly easy. You need to initilize the variables we are using: tno : "0" stooln : "" strn : "N" str1 : "1" The code I attached earlier will replace your M06 call out, could be in ptlchg, psof ect... depending on base post.

Ah, the old tool is in the spindle and I can not handle that Okuma error. I post edit is in store need to add the VATOL logic. [ #Skip tool call if tool is in spindle, can have at sof or for every change tno = t$ stooln = no2str(n$) stooln = strn + stooln + str1 pbld, "IF[VATOL EQ ", *tno, no_spc$, "]", *stooln, e$ pbld, *n$, *t$, "M06", ptoolcomm, e$ pbld, *stooln, *sm01, e$ #Skip tool call if tool is in spindle, can have at sof or for every change ] This code will have the machine check if the tool you are calling up is in the spindle or not, if it is then it skips ahead to the line after the M06. It could be worse, I've seen a Mitsubishi control that would ignore a toolchange if the syntax was out of order and just use the tool in the spindle and lenght offset for the real tool and go on its merry way.

Dim tool_corner_radius = Convert.ToDecimal(ds.Field("CORNER_RADIUS", False)) Dim tool_radius = Convert.ToDecimal(ds.Field("CORNER_RADIUS", False)) The tool_radius is being set to the same value as the tool_corner_radius "CORNER RADIUS" in this example.

If you merge the STL in on its own layer; transform...you can do a save some, or just leave it there and reference it via level (depending on what you want to do with it). I don't see lost functionality here...unless I'm missing something?

I would think a shaft with shoulder and a keyway and nut washer to tighten it all down would be best for this part. My experience with expanding mandrels on turning applications taught me: 1) not a rigid setup (I would not try milling) 2) bore diameter variations are problematic 3) good for blind hole where nothing else will work Allan

"not sure if i am posting at the right place." No it is not; you should have created a new topic. A manual mill would be my choice for a 1 or 2 piece run; anything more than that I would source rectangular/square stock. BTW Welcome to the forum. Allan

Brand new mill (first CNC) and running 4 and a half year old software? You might want to talk to your Mastercam dealer about the current offerings. Allan

You will never see this as an option in drilling toolpaths. Great application for a macro; make your drill call a modal macro G67 Then have your macro check and record the current time. Then execute the drill cycle; you will need to pass the cycle type variable G81 G83 ect to the G67; you have A-Z letters to use as variables. Then check the time after every hole when the time equals whatever variable you passed or set in the local variables on control. Retract and stop spindle M00. Typically folks doing lots of drilling have macro drill cycles that check for spindle and Z axis loads and move to a sister tool or alarm out. If your doing really small holes where loading is insignificant a acoustic sensor listens for problems and alarms out when something is sensed to have happened. Allan

The hand coding suggestion is best. Looks like the tool is the WIT file so it is ran directly on center? If on center; M what ever (to turn on C axis control) G00 X0. Z.4 (position tool) G01 Z0. G01 Z-120.00 C90. F250. (broach hole) IDK feed rate will depend on conditions; better use oil. G01 Z.0 C-90. F500. (retract from hole) G00 Z20. (look for pieces of broach in chip tray) If that tool is not cutting on center; you are looking for a timed cut with the live tool and spindle running. Mastercam does not have a specific toolpath for that. It can be accomplished using a contour toolpath and a few post tweaks. Your control will need to have a Synchronizing command look for hobbing or polygonal turning in the Manual. The actual toolpath for the polygonal turning will be best hand coded.

Need to select "True Threads" button to see true threads

The bore is 2.375" and the pitch of that groove is ~5." . I believe you will have significant issues with surface footage cant spin fast enough (surface speed) because of the pitch 80 RPM yields 400i n/m Also need to start clear by ~2." to let the carriage get up to speed. I would use a thread toolpath as in example. 200892.mcx-9

The .ini files on server as well as the client machines need to change. The service on the NetHASP server will also need to be stopped and restarted to take the settings change. Allan

Since you say it started last Thursday, and there have been no updates since then, I can assume that nothing has changed software wise. You also mention the HetHASP is offsite, so the network between the 2 locations would be my first suspect. Check the connection statistics using a tracert command, your IT guy should be able to accomplish this. I would not be supprised if you will see response times in the 150+ms. The NetHASP default settings in Mastercam use the UDP protocol. Conjested networks will drop UDP packets to save bandwidth, TCP connection may prove more reliable. HTH Allan

Start All Programs Mastercam X9 Utilities Advanced Configuration Left hand side of window Graphics Support...Hardware acceleration set to disable. Then launch Mastercam, if it works, your Video card is weak or the driver does not support open gl to Mastercam specifications. HTH Allan