- Posts: 153
- Thank you received: 0
Lathe stops at code line
so i wanted to test my rebuildet cnc lathe, but got this thing i cant find.
i have made a little program in fusion. i set up the lathe for a dry run, but it stops at line 18.
i got a post processor from autodesk.
Please Log in to join the conversation.
It is an error if:
A new feed rate is not specified after switching to G94 or G95
Another possibility is motion.spindle-speed-in not connected properly or backwards etc
Please Log in to join the conversation.
For accurate handling, if i count the lines to 18 in the file i end up with :
N22 X18.
I mention that the fusion postprocessor can be updated to remove some dot's.
linuxcnc.org/docs/2.6/html/gcode/gcode.h...sec:G93-G94-G95-Mode
G95 - is Units per Revolution Mode In units per revolution mode, an F word is interpreted to mean the controlled point should move a certain number of inches per revolution of the spindle, depending on what length units are being used and which axis or axes are moving. G95 is not suitable for threading, for threading use G33 or G76. G95 requires that motion.spindle-speed-in to be connected.
It is an error if:
1. Inverse time feed mode is active and a line with G1, G2, or G3 (explicitly or implicitly) does not have an F word.
2. A new feed rate is not specified after switching to G94 or G95
Pcw wrote about the feed rate (2), it can be also option (1), but G93 is not the problem in this case.
I think it has to to with this : the controlled point should move a certain number of inches per revolution of the spindle.
With reducing X18 to X0.005 the machine will problably pass this line.
Please Log in to join the conversation.
Which line is highlighted when the motion stops?
Note that if spindle-at-speed is active then G0 moves will happen, but the machine will pause and wait for the spindle-at-speed pin to go true before any G1 move after a spindle speed change.
Please Log in to join the conversation.
andypugh wrote: I suspect that this is a spindle-at-speed problem.
Which line is highlighted when the motion stops?
Note that if spindle-at-speed is active then G0 moves will happen, but the machine will pause and wait for the spindle-at-speed pin to go true before any G1 move after a spindle speed change.
Thanks all for your answers.
I mend in deed line N22.
I've tried to remove the point and even edit it eith extra decimal.
I think it is indeed that speed problem.
The lathe has a spindle servo motor with encoder. 1:1 ratio.
The encoder output from the driver is connected to the mesa 7i76e board. What do I need to change?
Please Log in to join the conversation.
(And is this LinuxCNC 2.7 or 2.8? As I changed all the spindle pin names in 2.
Please Log in to join the conversation.
andypugh wrote: Do you see any mention of "motion.spindle.at-speed in your HAL file?
(And is this LinuxCNC 2.7 or 2.8? As I changed all the spindle pin names in 2.
yes, i fount the line "motion.spindle.at-speed " in the HAL file.
also i don`t know if i have the scale right.
linuxcnc is version 2.7.14
Attachment not found
Attachment not found
Please Log in to join the conversation.
I suspect you might find that your spindle-velocity-fb has a different sign to the spindle-velocity-cmd. If it is that make your encoder scale negative. That's [SPINDLE_9]ENCODER_SCALE in your INI.
Please Log in to join the conversation.
andypugh wrote: I suggest opening three halmeters and looking at near.0.in0, near.0.in1 and near.0.out
I suspect you might find that your spindle-velocity-fb has a different sign to the spindle-velocity-cmd. If it is that make your encoder scale negative. That's [SPINDLE_9]ENCODER_SCALE in your INI.
okay. so at 1500 rpm near.0.in1 gives a value of 25.
that should be fine. (1500/60)
but spindlevel-fb-rps gives a mutch lower value. and not constantly. it pops up ones a while. just enough to make a picture.
encoder scale is: 1024
Attachment not found
Please Log in to join the conversation.
hm2_7i76E.encoder.00.count is solidly on zero. This leads me to suspect that one of the spindle encoder phases is not connected.
(If this is deliberate then you need to set counter-mode to true for that encoder)
Please Log in to join the conversation.
