Forum Header

configuring lathe problem stepconfig

More
11 years 7 months ago - 11 years 7 months ago #57021 by Clive S
Hi
Would somebody care to look at my configs attached.

Problem is the Z axis is not working (DRO goes round but the motor does not).

I have had my lathe working ok under axis and I have been trying to set an encoder up to have a go at screw cutting.

I set the encoder index ,A and B up in stepconfig and its added lines in the hal ini.

I have noticed that in the ini file it show 3 axis but I have only set it to X and Z.
In the hal ini it seem to show U step and U dir (should this not be Z step etc)

The encoder appears to work as it is giving me the rpm on the axis screen.

I don't see the wood for the trees. Thanks. Clive



File Attachment:

File Name: Myford_Lathe.hal
File Size:3.16 KB


File Attachment:

File Name: Myford_Lathe.ini
File Size:1.73 KB
Last edit: 11 years 7 months ago by Clive S. Reason: trying to attach file

Please Log in or Create an account to join the conversation.

More
11 years 7 months ago - 11 years 7 months ago #57030 by ArcEye
Hi

It shows 3 axes because it counts X Y Z etc, that is normal, does not mean you have to use all of them and you have the correct coordinates set as X Z

It looks like you just need to change udir and ustep to zdir, zstep.

Do it in gedit not stepconf or you risk messing up an otherwise OK config

No idea how the names got that way to start with

regards

EDIT

Attached is an altered copy, try that, can't immediately see anything else wrong with it
Last edit: 11 years 7 months ago by ArcEye.

Please Log in or Create an account to join the conversation.

More
11 years 7 months ago #57034 by Clive S

ArcEye wrote: Hi

It shows 3 axes because it counts X Y Z etc, that is normal, does not mean you have to use all of them and you have the correct coordinates set as X Z

It looks like you just need to change udir and ustep to zdir, zstep.

Do it in gedit not stepconf or you risk messing up an otherwise OK config

No idea how the names got that way to start with

regards

EDIT

Attached is an altered copy, try that, can't immediately see anything else wrong with it


Ok update It was the ustep and udir that I had to change (I had done it before but I use caps Z) it seems to like only lower case.

What I did notice was that I ran a new stepconfig with lathe and again it put in ustep and udir for the pins in the HAL strange!!

I have now tried a G76 line and as expected it runs the thread cycle if you stop the spindle you can turn it by hand and the thread Z moves
if you reverse the spindle say 10 revs the go forward again the thread does not start again until the 10revs have been done.

if you turn the spindle backwards the Z does not move is that correct?

Would you mind giving me a sample G76 line of code for say a M10 x 50mm so I can do further tests then I can learn how to program it. I use mm for the lathe.

I still need to calibrate the z move it seem to move about half what is required.

Many thanks for the help. Clive

Please Log in or Create an account to join the conversation.

More
11 years 7 months ago #57061 by cmorley
What version of linuxcnc are you using? master?
U and V axes were added recently and there may be a bug.

Chris M

Please Log in or Create an account to join the conversation.

More
11 years 7 months ago - 11 years 7 months ago #57062 by Clive S

cmorley wrote: What version of linuxcnc are you using? master?
U and V axes were added recently and there may be a bug.

Chris M


I installed the 2.6 hybrid iso then ran the update which brought it up to 2.7 (so a complete new install)

my ini files are attached in #57021

edit I don't remember having the same problem on the mill just had it on the lathe profile

I have been playing with gmocappy (only saying this for completeness)

Clive
Last edit: 11 years 7 months ago by Clive S. Reason: Added text

Please Log in or Create an account to join the conversation.

More
11 years 7 months ago - 11 years 7 months ago #57063 by ArcEye

Would you mind giving me a sample G76 line of code for say a M10 x 50mm so I can do further tests then I can learn how to program it. I use mm for the lathe.


This is a template so will cover whatever thread size
(ignore the M code, that is just a local one to set the pulley number for correcting the speed)
Code:
;; Threading with G76 ;; Speed of 300 is stable and only requires F450 to cut 1.5mm thread ;; P[itch] ;; Z[FinalExtent] - Ensure there is an overrun element so that deceleration happens beyond end of thread, 3 mm sufficient in this example ;; I[ThreadPeakOffset - cant be 0, neg for external pos for internal, if diameter is critical you can add PeakOffset to Diameter to negate this value] ;; J[FirstCutDepth - positive offset] ;; R[DepthDegression 1.0 is constant depth 2.0 is constant area 1-2 depth decreases & area increases 2> area decreases] ;; K[FullThreadDepth positive offset beyond I for root of thread]- Q[CompoundSlideAngle eg 29.5] ;; H[SpringPasses at full thread depth] E[TaperAmount in units - normally 0] L[Taper- L0 None L1 entry L2 Exit L3 Both] #<_Diameter>=40 #<_Z_LeadIn>=15 #<_Pitch>=1.5 #<_Z_Finish>=-15 #<_PeakOffset>=-0.001 #<_First_Cut_Depth>=0.01 #<_Depth_Regression>=1.0 #<_ThreadDepth>=1.5 #<_CompoundSlideAngle>=0 #<_Spring_Passes>=2 #<_TaperAmount>=0 #<_TaperType>=0 #<_Feed>=1.5 #<_Speed>=300 G18 G21 G40 G49 G54 G80 G95 G90 G7 M101 P3 (SET PULLEY SETTING 3 FOR GOOD TORQUE) F#<_Feed> S#<_Speed> M3 G4 P10 M7 (GO TO OS DIA AND Z LEAD IN G0 X#<_Diameter> Z#<_Z_LeadIn> G76 P#<_Pitch> Z#<_Z_Finish> I#<_PeakOffset> J#<_First_Cut_Depth> R#<_Depth_Regression> K#<_ThreadDepth> Q#<_CompoundSlideAngle> H#<_Spring_Passes> L#<_TaperType> G00 X45 M9 M5 G28 M2

The Z lead in figure is quite important, because that is what enables everything to be aligned and at the right speed before cutting commences
I normally allow 10x the thread pitch roughly, so 15mm for a 1.5mm pitch

if you reverse the spindle say 10 revs the go forward again the thread does not start again until the 10revs have been done.


I am not sure why anyone would ever do that, but I suspect it is because you have both A and B channels on your encoder,
so it knows you have moved away from position in reverse and is bringing you back to where you were, before starting.

regards
Last edit: 11 years 7 months ago by ArcEye.

Please Log in or Create an account to join the conversation.

Time to create page: 0.189 seconds
Powered by Kunena Forum