Page 2 of 3

Re: Program eratic after a tool change Lathe

Posted: Fri Mar 22, 2024 12:11 pm
by PhilipTrueman
Ken Rychlik wrote: Fri Mar 22, 2024 9:07 am What about trying the pc tuner? Maybe a communication issue. With it being after a tool change, it makes me wonder about tool offsets G43, G49, Does it go to a G55, G56 ect....
I have just run PC tuner there are no faults.

Re: Program eratic after a tool change Lathe

Posted: Fri Mar 22, 2024 1:33 pm
by PhilipTrueman
cncsnw wrote: Thu Mar 21, 2024 12:14 pm What does this program look like on the graphic preview (F8/Graph) display?

Do programs that you wrote prior to last week still run correctly?
I have just tried a program that i wrote last week in Intercon and that runs correctly. How strange is that.

Re: Program eratic after a tool change Lathe

Posted: Fri Mar 22, 2024 1:55 pm
by tblough
The fact that it does not return to zero, implies that you are overdriving your motors and loosing steps. What are your programmed feed rates for the grooving tool? Common mistake is to program a valid range in feed per minute, but have the feed set for feed per rev. That will almost always cause missed steps.

Re: Program eratic after a tool change Lathe

Posted: Fri Mar 22, 2024 2:33 pm
by cnckeith
this doesn't sound like a software version issue. so don't dig yourself a hole by changing around from one version to another.

Re: Program eratic after a tool change Lathe

Posted: Fri Mar 22, 2024 2:34 pm
by cnckeith
tblough wrote: Fri Mar 22, 2024 1:55 pm The fact that it does not return to zero, implies that you are overdriving your motors and loosing steps. What are your programmed feed rates for the grooving tool? Common mistake is to program a valid range in feed per minute, but have the feed set for feed per rev. That will almost always cause missed steps.
i second this!

Re: Program eratic after a tool change Lathe

Posted: Fri Mar 22, 2024 3:02 pm
by PhilipTrueman
I have slowed the rapids down to 40% than they were set to. I have always had them set to 40% more without any steps being lost.
The motors are 9NM so are not underpowered. They are hybrid motors and have encoders on them so they shouldn't be loosing any steps.
Two weeks ago i made 20 parts 90mm diameter without any issues.
The programs that i made in Intercon 2 weeks ago still work without any mistakes. It is just new programs made in intercon that have the issue on the second tool change.
Why would one older program work and a new program not work both made with the same version of cnc12 ?
Feeds in the software are feed per rev and the same in intercon.
It can't be a hardware issue otherwise the old program would be doing the same as the new program.

Re: Program eratic after a tool change Lathe

Posted: Fri Mar 22, 2024 4:05 pm
by cnckeith
when you say older program do you mean G code or Intercon?

please post the working program and a non working program

Re: Program eratic after a tool change Lathe

Posted: Fri Mar 22, 2024 4:20 pm
by PhilipTrueman
cnckeith wrote: Fri Mar 22, 2024 2:34 pm
tblough wrote: Fri Mar 22, 2024 1:55 pm The fact that it does not return to zero, implies that you are overdriving your motors and loosing steps. What are your programmed feed rates for the grooving tool? Common mistake is to program a valid range in feed per minute, but have the feed set for feed per rev. That will almost always cause missed steps.
i second this!
For the grooving tool i was feeding the tool at 0.03MM per rev 1000CSS

Re: Program eratic after a tool change Lathe

Posted: Fri Mar 22, 2024 4:25 pm
by cnckeith
i loaded your report and intercon test file on a test bed machine (without a spindle encoder) and i changed the intercon program to F/M and it seems to run fine, (not like the video short posted)

Re: Program eratic after a tool change Lathe

Posted: Sat Mar 23, 2024 4:16 am
by PhilipTrueman
cnckeith wrote: Fri Mar 22, 2024 4:25 pm i loaded your report and intercon test file on a test bed machine (without a spindle encoder) and i changed the intercon program to F/M and it seems to run fine, (not like the video short posted)
I will try running the program again.
I will duplicate the old intercon program again and see if there are any changes to the g code.
Is the program just following using the g code or are there any other parameters that will affect the operation?
When you ran the program did it have a turret toolchanger?