I use a G65 macro call to set DOC, feedrates, etc. for my G71 canned rough turn cycle. The sub also sets the starting S-value. We purchased two T42 lathes at the same time. One with 16C collet, the other with 20C collet. The latter alarms unless I put a value in the starting S-code. Both have 18T controls. I think a FIX statement could be written to force the S-value to be a whole number...but why should I have to?

All the other Hardinge and Daewoo lathes will process this without an error. This includes the 21i and OT controlled machines. I talked to Hardinge Brothers, but they didn't know what parameter might be causing it. Haven't as yet contacted Fanuc to see if they could solve the problem. Figured I'd tap the extensive knowledge on this forum first.

My code looks like this: S[3.82*#119/#115] where #119=SFM & #115=stock size.

I got tired of writing 4 or 5 programs for the same job...on the same machine...because of using different stock sizes. I originally changed my rough turn operation to a G71 canned cycle to make my life easier.

However, I've been teaching myself variable programming the past year. Finally got to the point where I realized I could write a 'While' statement that would do it for me. I loaded it in the contols as a subprogram and use the G65 call to set all my variables. Works like a champ. :D

Well except for this one lathe. :(

BTW, I find Hardinge Brothers to be top notch with their support. They are always willing to try and help regardless of the type of problem I am having. Not that we have a lot of problems with Hardinge lathes. This is the first time I've called them in at least a couple years.

What fault or error do you get? Can you compare the parameter settings between the two lathes?

What fault or error do you get? Can you compare the parameter settings between the two lathes?

I can compare the parameters. These 2 machines are in the same cell. Don't recall the message. I will check Monday if time allows. Got 2 machines needing set-up, plus problems with another set-up.

Make sure you don't have a typo or punctuation wrong. Sometime, you'll swear everything is good, but after some headscratching you'll see an extra . or something.

Make sure you don't have a typo or punctuation wrong. Sometime, you'll swear everything is good, but after some headscratching you'll see an extra . or something.

It is really weird. Friday morning a job was sent back where I had had to change the S-code to a normal one. I tried a little experiment on a Daewoo Lynx that had previously run this type of cycle with no problem. MDIed in S100.5 & control gave me an illegal use of decimal point alarm. (Expected.) MDIed in S[2000/7]M3 and it worked. (Also expected.) Went over to the Hardinge that hasn't been accepting this code, and MDIed in S[2000/7]M3. It worked! What the...?

So I modified the rough turn cycle back to S[3.82*#119/[#115+.05]], maually input values in #115 and #119, hit cycle start and it ran! Very next program was set up with the same cycle. It also ran.

Now I am totally confused. Up until I MDIed in the S[2000/7]M3 this control had never run this command. It wouldn't alarm. Just sit there. Control would be locked up. Had to power down & back up before you could do anything with the control.

Guess I will have to wait to see if it is now going to run all my programs with this type of code in it. Next time I will double check to make sure that the G65 is in fact loading the variables. Thought it did before, but maybe I only thought I had checked for them.