The Hole Axis Chook thread can be found here: Hole Axis for X2 After installing it there is a category in the toolbar customize called Verisurf Hole axis that will give you the icon/shortcut that you can place where you like. To run the chook using Alt-C you'll need to browse to the verisurf sub dir in the chooks folder. For those of you having trouble with it I suggest posting in the Hole axis thread and doing what you can to get it to work. (work arrounds suck)

Hole axis c-hook?

Look in your post for: code: arcoutput : 0 # 0 = IJK, 1 = R no sign, 2 = R signed neg. over 180 Change it to: code: arcoutput : 1 # 0 = IJK, 1 = R no sign, 2 = R signed neg. over 180 Welcome to the Forum Allan

I second Erics suggestion if they cant help you call: Renishaw Inc. 5277 Trillium Blvd, Hoffman Estates IL 60192 USA United States T: +1 847 286 9953 F: +1 847 286 9974 E: [email protected] They sell the Macros for Fanuc Marco A on this page: Renishaw Macro A

Take out the *spindle like this: code: if opcode$ = 3 & nextdc$ = 3, #check for rigid tap = NO "speed" output pcan1, pbld, n$, *sgcode, [if not(index), sgabsinc, pwcs], pfcout, strcantext, e$ else, pcan1, pbld, n$, *sgcode, [if not(index), sgabsinc, pwcs], pfcout, *speed, *spindle, strcantext, e$

Hey Tom; how is the Gibbs working out for you? Allan

You could use the Cimco Editor function that changes Heidenhain to ISO and then run that thru the nc2cdl.exe.

What does your file format look like? I just tried something simple like: X1.313774 Y0.4931055 Z0 X0.8805456 Y-0.1620204 Z0 X0.7854466 Y0.3909622 Z0 X0.1232764 Y-0.07748801 Z0 X-0.19372 Y0.3909622 Z0 X-0.8136241 Y-0.0598771 Z0 X-1.007344 Y0.4790168 Z0 X-1.310252 Y0.232464 Z0 Chose lines in the options and I got lines. Let see what your file looks like. Allan

In the file open box (when you choose ASCII) there is an options box; choose lines for the entity type and you should be all set. Allan

Yes and No: Anyone with Version X can read a postscript file (EPS, AI, PS) in Version 9 this was avail only with Rast2vec. Allan

The AI (Adobe Illustrator) file that I link to is a vector format file that can be read directly into Mastercam via the file open and it looks exactly like the picture shown above. There should be no need to e-mail or post file anywhere, but what do I know.

Here is the logo in AI format: Logotypes.ru Pip; CSA is the Canadian Standards Association CSA , something like CE Certification for europe. CE Marking

You will want to make a call to a post block like this on the retract moves: code: pspindle #Spindle speed calculations for RPM if maxss$ = zero | maxss$ > max_speed, maxss$ = max_speed if css_actv$, [ #Spindle speed calculations for strt_spd w/CSS speedx = abs(xa) if opcode$ = 104, speedx = abs(c1_x_min) if opcode$ = 105, speedx = abs(tcr$) if speedx < 0.001,speedx = 0.001 speedrpm = (conversion * g_speed) / (pi$ * speedx * two) ] else, speedrpm = g_speed #zero indicates spindle off (not a mistake) if speedrpm, [ if speedrpm > maxss$, speedrpm = maxss$ if speedrpm < min_speed, speedrpm = min_speed ] #Spindle speed for RPM with lathe drill, thread if opcode$ = 104 | opcode$ = 105, css_actv$ = zero if css_actv$ = zero, g_speed = speedrpm HTH Allan

The posts are not normally set-up like what you are talking about. Most likely the post writer has captured the inital calculated G97 speed, and is simply outputing that value before the retract. I've been asked to actually do away with the inital G97 call and just go to G96 many times, there is a switch in some post files for that now. The diffrences that you have in your speed values are quite small, does it actually cause a problem? It is possible to re-calculate the RPM value, have eyou asked your dealer? Allan

I've had similar problems with drip feeding on Mazak, the problem is in handshaking, usually it can be solved by increasing the Baud rate to 9600 or more and setting an end of line delay in your DNC software. EDIT: You will also want to turn off the FIFO buffer for the port in the device manager of Windows.

What control? Is it the dynapath? Perhaps the format of the arcs is incorrect, how does it compare to the sample in the machine manuals? I seem to recall that the dynapath uses (2) or (3) to define arc g codes, there is no plane definitions.

Is the file a Pro-E file (add on translator) or a UG file (add on translator) or a CadKey file (your on your own)?

You'll need to make a new variable and format it diffrently. Something like: Near top of post file my_new_variable : 0 #initilize variable Format statment section fmt 3 my_new_variable # Z home position Choose a format statment that gives you #Integer, not leading Then where you want to use it set the new variable equal to the next_tool variable like: my_new_variable = next_tool Hope this helps Allan

There is on some lathes (with live tooling) an option for orientating at an angle usually M?? S(angle) and those style machines only index at 7.5 or 15 deg. depending on the option purchased. Modern machines like the SL-20 mentioned use a full C axis but only if the machine came with live tooling. Why put a C axis on a lathe with no live tooling? Allan

The pneumatic drill would work; but if your looking for more than one hole relative to the other, your out of luck they dont put a C axis on a machine that does not have live tooling. Allan

No I think he is saying that Fanuc style feed hold and cycle start to resume has problems where Z is whacked. I've never run into that specific problem, on other systems like that, the control software rev is important (some work some don't) also the spftware that transmits the file to the machine most times has some type of translator that version is also important. Allan

Did you check out Festo? Here is a link: Festo Pressure switch Allan

The folks at Cimco have a cable guide here: Cable Guide Most set-up use the software handshake method. Allan

elbro; I thinks Chris is saying the post is from V7 not that he wants to use it in V7 The variable you are looking for is: n_tap_thds$ HTH Allan

Robert There is a product called Prodrill that will take the hole wizzard info and apply the correct drilling op. You would run a macro in Solidworks and the programmer will import an .x_t or .sldprt set the WCS run prodrill pick your file the macro created...cycle start. Allan