Am I the only one with this issue? Came in this morning and all of the sudden my Stock is sitting 1" above where it should. Perhaps its too early but here it is. Just for kicks I changed the TF001584-3 stock to round and it also moved but on X instead. Weird ! TF001585-2.MCX-7 TF001584-3.MCX-7

I've done this in the past on some SS304 screws. Worked great ! Axis Substitution !

Did you ever find a solution, I am having this problem. I had it there and enabled it for X6, I tried to enable it on X7 but the dropdown is not there for either versions now. GM

Hi Colin, Im having a problem with the debugger, the switch to enable it is not there. I had it enabled in X6, yesterday when I tried to fix a double comment output on X7 I cannot enable the debugger. HELP !

There is a string in the tool definition, for some reason it wasnt being output. I changed it to something else and all of the sudden we get the output to what it was before I changed it; weird. Can you please take a look at the following code: I cannot get brksps to work properly, I know im missing something. pstrtool #Comment for tool if strtool$ <> sblank, [ strtool$ = ucase(strtool$) if strtool$ = sstar, [ brksps = 1 *strtool$, sclose_prn,e$ sopen_prn, *strtool$ ] else, *strtool$ ] I tried brksps$ but that did not work either.

How do I search the comment string ?

Colin, Is there any other way of getting your input on some POST mods? I am getting an error or so I think. I am outputting a modified tool table, for some reason when I use a No. Drill, the string is blank. What is this due to, all I modified was a few extra strings I didnt want. See my code below : pcutinfo #Stock and Comp output [if comp_type > 0 & comp_type < 4, sopen_prn, *tloffno$, sdash, *scomp_type, sclose_prn], [if xy_stock <> 0 | z_stock <> 0, sopen_prn, *xy_stock, sdash, *z_stock, sclose_prn], e$ ptooltable #Tooltable output sopen_prn, *t$, sdash, pstrtool, #[if comp_type > 0 & comp_type < 4, sdelimiter, *tloffno$, sdelimiter, *scomp_type, sdelimiter, *tldia$], #[if xy_stock <> 0 | z_stock <> 0, sdelimiter, *xy_stock, sdelimiter, *z_stock], sclose_prn, e$ pstrtool #Comment for tool if strtool$ <> sblank, [ strtool$ = ucase(strtool$) *strtool$ ]

Colin, If you notice that above is a tungaloy facemill, its a facing cycle which has no cutter comp. Is there a way for the post not to output this when it is either a drilling tool or facing tool, or better yet if there is no cutter comp?. Wait that may be answer...jejeje Edit: I tried using the comp as a trigget, however the variable is initialized as comp_type : 0. Can this be safely changed to zero since each tool will change it as needed ? Below is my logic: if gcode$ = 1008, if comp_type <> 0, [ sopen_prn, scomm$, sclose_prn, e$ #Operation comment & pcutinfo #Stock and Comp comment ] else, sopen_prn, scomm$, sclose_prn, e$ #Operation comment Only pcutinfo #Stock and Comp output [if comp_type > 0 & comp_type < 4, sopen_prn, *tloffno$, sdash, *scomp_type, sclose_prn], [if xy_stock <> 0 | z_stock <> 0, sopen_prn, *xy_stock, sdash, *z_stock, sclose_prn], e$ I modified the original code that went into the tool table to create the block for pcutinfo.

N5 () () T5 M6 ( TOOL - 5 , 2" TUNGALOY TEN09R200 ) T1 ( FACE TOP .250 SB .270) <------------------This is on top (INSERT PNCU905GNER-MJ AH140 ) <------This is below in the Toolpath window ( D5 - WEAR COMP ) G54 G0 G90 A0. G0 G90 X4.246 Y0. S172 M3 G43 H5 Z1.

No character limit. While spotting for example on top I describe the feature and on the bottom I could write a diameter to hold for an edge break. It can also be used for threaded holes in order to communicate to the operator what diameter to hold for a lead in thread. All of this of course if it is not already called out on the print. Thanks ! GM

Colin, Sorry for bombing this thread. I have a POST question and cannot send you a PM message. I would like to have two-line operation comments, I am currently able to write them in the operation window by holding Ctrl+Tab and get to the bottom of my original comment. This however does not do well with the posted output. Can you help please. GM

You need to make the the edit at the PTLCHG and PTlCHG0 postblock, where did you make the modification ?

What do you mean it shows gaps, or it doesnt ?

This happened on my machine at work. Had to uninstall then resintall the software. Dont forget to reboot the PC in between !

I do this all the time and it works quite well. I already have to name the different groups according to the OP I am machining, choosing a different Program # is a few clicks away. I must agree though that if you copy tool paths from a previous operation they will carry over the old NCI filename and Program #; the solution to this is to create a new machine group but we've been down this road before ! GM

Still no idea why I have to setup my rotary to Z to get the proper output and toolpath. HELP !!!

Doesn't this simply add USB support for non-USB capable machines? What GCode is looking for is a way to edit at the machine without having to break the program into chunks. How about using the DNC off the Flash Drive ?

That would require for MCAM to know which program # was used prior to, I don't think that's possible. What if you are reposting a file, this might prove ineffective as MCAM will not now this. You can however setup your post to prompt, you at the time you are writing the NC code, for the program # and whether it is a repost. Is it that much of a hassle to change the program number or set it in MCAM ? GM

While in MDI mode press the programs menu, then press scape and switch to the VQC tab, press F2 in order to change from the milling template to Probing, you should now be able to arrow down and select from probing 1-8, 8-16, tool setting, calibration, and a fifth I don't recall at the moment.

I will help you out later today. Care to upload the file ?

Any thoughts on the A axis center of rotation being the Z, but when I load the machine definition I have to select A; must be a plane issue. Any help would be greatly appreciated... Jay, so we just upload revised files under a slightly different name every time ? Wow that gets crowded easy !

Clearance, or so I thought. Turns out that when I rotated my WCS for some reason my X-axis got twisted at a 45deg from the rotary center, MCAM could no longer machine the entire surface. I deleted and regenerated, its all good. Can you shed some light on the Advanced 5-axis, I still would like to try your suggestions. New file is on the FTP (MANIFOLD2.MCX-7), can anyone tell me why I had to set my rotary axis to Z when it is A ? Seems like it is going off the Main WCS rather than the one I created ! P.S. Why cant we overwrite our files on the FTP ! GM

I get the following error "You do not have permission to view this attachment.", whats up with this ?. On another note I successfully ran 1 flange(C-C), I cannot get a toolpath to work right for the other flange (F-F). Help !

My simulation engine gets changed by itself, I do a 3-axis path and the engine updates; likewise for 5-axis. Works great, it does lag a bit to load the NCI data and Solid Model.