I get the same thing every so often. The other issue well two are... viewports still don't print and... If I hit F1 with any type of text on the screen the text is off of the print page.

thanks Pete.

Is there a setting I am missing? It seems the dimension and text is view dependent. If I create it in top view it is not visible in any view except for top.

Thanks medaq, the macros should be installed already if the hurco controller is capable. I will find out Monday. Outta here for today. thanks again everybody.

Ok thanks Steve.

The H0 callout was caused by my tool #1 had a length offset = to 0 H was looking for the length offset.

Looks like that is what I needed. It weird the older machine has it hard coded in to retract Z to home on Cycle start. Oh well. Thanks John. I will try to figure out that H0 callout now.

I see the G20. Here is the ouput I get now by adding that. N100G20 N110G0G17G40G49G80G90 /N120G91G28Z0. /N130G28X0.Y0. /N140G92X10.Y10.Z10. (MILLSTAR 1 1/4 BULL CUTTER WIH 6MM RAD TOOL - 1 DIA. OFF. - 0 LEN. - 0 DIA. - 1.25) N150T1M6 N160G0G90X-1.353Y-3.4774S2250M3 N170G43H0Z5. N180Z4.75 Does the forward slash null the block?

Gotcha thanks guys. Will give it try and see what it looks like. One more question if I may. the smetric$ what is that doing? Like I said I got this from a dealer and I do not use metric, will that be an issue?

the $ signs are missing CUZ its early and that was copied from the V9.1 post. Doh!

this is my psof. psof #Start of file for non-zero tool number pcuttype toolchng = one if ntools = one, [ #skip single tool outputs, stagetool must be on stagetool = m_one !next_tool ] "%", e *progno, e "(PROGRAM NAME - ", sprogname, ")", e "(DATE=DD-MM-YY - ", date, " TIME=HH:MM - ", time, ")", e pbld, n, *smetric, e pbld, n, *sgcode, *sgplane, "G40", "G49", "G80", *sgabsinc, e sav_absinc = absinc if mi1 <= one, #Work coordinate system [ absinc = one pfbld, n, sgabsinc, *sg28ref, "Z0.", e pfbld, n, *sg28ref, "X0.", "Y0.", e pfbld, n, "G92", *xh, *yh, *zh, e absinc = sav_absinc ] pcom_moveb c_mmlt #Multiple tool subprogram call ptoolcomment comment pcan if stagetool >= zero, pbld, n, *t, "M6", e pindex if mi1 > one, absinc = zero pcan1, pbld, n, *sgcode, *sgabsinc, pwcs, pfxout, pfyout, pfcout, *speed, *spindle, pgear, strcantext, e pbld, n, "G43", *tlngno, pfzout, scoolant, next_tool, e absinc = sav_absinc pcom_movea toolchng = zero I would think it needs to be added here

Yes if Z 0 would be machine home. Also I checked and I had con def set to "from tool" and the tool number is 1 so the H should be 1 as well in the post I would think.

John yes i am in X. I will check that. This is a new post the Hurco guy sent me from 9.1 so I hadn't reveiwed the con def yet. My old def was for the old hurco post and it was set like that. Thanks for the reminder. As far as output, I would like to see the Z move before the X Y at the start of the program because... look in O/T and see smash. Pretty funny.

Yes there is... Sort ascending/descending tool number, by creation, diameter you name it.

I have been using an old hurco post for my old machines. Now we have a new Hurco and it will not move Z to safe position before cycle start or at cycle start like the old machines. I think it is hard coded in the old ones. Anyhow... I will get an X Y position call out before a Z and the foreman smashed the cutter and knocked the piece out of the vise last night by not knowing what he was doing.. Funny story check O/T. SMASH. Here is an example of the code and notice the weird H0 callout for T1 also. That looks wrong to me. N150T1M6 N160G0G90X-1.353Y-3.4774S2750M3 N170G43H0Z5. Thanks guys. Don't know what I'd do without this forum and everyone's help.

James, that is what I am looking for. Renishaw uses macros written into your controller. example they show is... Format G65 P9863 [Hh Mm Ss Yy Zz] where [ ] denotes optional inputs Example G65P9863 H5. M1. S2800 Y3. Z6. BUT I still can not verify if this macro will work with this Hurco. They have something in the appendix that states... Appendix B Yasnac controller settings The Yasnac range of controllers – MX3, J50, I80 and J300 – use a different configuration of tool offset options to those used by Fanuc. There are no separate wear and geometry registers. Not sure if this means it won't work. I do have another question that arose at the end of the day yesterday about the post. I am going to start a new topic for it though. Kind of a funny story to go with it...I'll put that in O/T.

I had seen a post about this before. Make sure you do not have anything pre-selected. If it is and you haven't cleared selections you can move it without knowing.

Uhh No it wasn't. I have been reading on Renishaw's site. Will see if the macro program they have for tool breakage is available for Hurco which I think may be the same as Yasnak. Thanks guys.

Thanks Ron, Yes we were basically looking for a way to see if the tool is broken before sending in smaller cutters. Instead of coming in in the morning to find the 1/4 ball broke first then the 1/8 etc.. etc.. I would suspect tech is limited. At least as far as the guy they sent out to "train".

No. I meant I would save my original file. Keep it open and mirror all of my geometry which turns my toolpaths dirty. Then regenerate them and save the file off as a mirror of the original. Original 4516SLT Mirror M4516SLT It works like that fairly easily but anyone not familiar with the transform mirror function may get bitten badly.

We just got our new Hurco (don't laugh) and they went with the Renishaw laser to help eliminate operator error (don't laugh). The tech guy they sent out didn't know how to answer my question. Here is what I asked... My boss wants or intended on us using the laser to verify tools before and after cuts before a tool change is made to see if cutter held up. How or where do I begin to get that into my programs? The tech didn't know if it was a gcode command or not and he didn't know where I would put it in. Do any of you use this? If you do, could you please give me some guidance? Help is much appreciated. Thanks Bill...new to this laser stuff.

Not sure in X but it does have a function under tools to import an NCI file. In V9 I would change the post to RPFAN and pick the NC file. That would give you your nci file. Backplot save geo. Probably the same for X when imorting the nci although you may be able to alter the toolpath with edit.

For safety sake they should just remove the option of reversing it. Verify in turbo shows it works but if someone is not careful it could Rapid to the bottom of solid stock and and create a mess.

This has been a problem for a while in previous versions. I have several ops z level cuts. I have a mirrored component of the same and wanted to mirror the toolpaths but KEEP the cutter climb cutting so I pick reverse toolpaths. It reverses not only the direction but the cuts from top to bottom TO bottom to top. It would be nice if it worked correctly but seldom ever does seeing I use z level cuts most of the time. Work around? Saving ops and regenerating on the mirrored object is what I usually have to do. Anyone else notice this?

It worked. Changed it to =0 Nathan and Brett thank you.