G76 works but not 33
- TejasDragon
- Offline
- New Member
-
Less
More
- Posts: 10
- Thank you received: 0
28 Dec 2014 00:44 #54316
by TejasDragon
G76 works but not 33 was created by TejasDragon
Been getting my lathe setup and all looks good except G76 works but not G33.
Spent yesterday going over post of problems but have not figured out why.
what could I be missing?
thanks
henry
Spent yesterday going over post of problems but have not figured out why.
what could I be missing?
thanks
henry
Please Log in or Create an account to join the conversation.
28 Dec 2014 00:48 #54317
by BigJohnT
Replied by BigJohnT on topic G76 works but not 33
Does your spindle have an encoder with A B and Index? G33 requires that where as G76 only needs Index and A IIRC.
And do you have full spindle control via G code?
JT
And do you have full spindle control via G code?
JT
Please Log in or Create an account to join the conversation.
- TejasDragon
- Offline
- New Member
-
Less
More
- Posts: 10
- Thank you received: 0
28 Dec 2014 02:04 #54319
by TejasDragon
Replied by TejasDragon on topic G76 works but not 33
I have Index and A , can set up B if needed.
I do not have full spindle control, just read the encoders on it.
I get a message on G33 that says the spindle is not turning.
henry
I do not have full spindle control, just read the encoders on it.
I get a message on G33 that says the spindle is not turning.
henry
Please Log in or Create an account to join the conversation.
28 Dec 2014 02:42 - 28 Dec 2014 02:42 #54320
by PCW
Replied by PCW on topic G76 works but not 33
I dont think G33 requires a full quadrature encoder (with A and B )
since it does not necessarily reverse (G33.1 _does_ require full quadrature)
If you look at the GCode reference: for G33, it says:
I suspect you don't have the motion.spindle-at-speed pin connected appropriately in your hal file
since it does not necessarily reverse (G33.1 _does_ require full quadrature)
If you look at the GCode reference: for G33, it says:
HAL Connections
The pins motion.spindle-at-speed and the encoder.n.phase-Z for the spindle must be connected in your HAL file before G33 will work. See the Integrators Manual for more information on spindle synchronized motion.
I suspect you don't have the motion.spindle-at-speed pin connected appropriately in your hal file
Last edit: 28 Dec 2014 02:42 by PCW.
Please Log in or Create an account to join the conversation.
28 Dec 2014 03:01 #54321
by BigJohnT
Replied by BigJohnT on topic G76 works but not 33
Opps yes I meant G33.1 needs A, B and I and spindle control.
www.linuxcnc.org/docs/html/examples/spin...d_spindle_feedback_a
If G76 works G33 should work as well.
What is the encoder A and Index connected to in your HAL file?
JT
www.linuxcnc.org/docs/html/examples/spin...d_spindle_feedback_a
If G76 works G33 should work as well.
What is the encoder A and Index connected to in your HAL file?
JT
Please Log in or Create an account to join the conversation.
- TejasDragon
- Offline
- New Member
-
Less
More
- Posts: 10
- Thank you received: 0
28 Dec 2014 09:51 - 28 Dec 2014 09:52 #54331
by TejasDragon
Replied by TejasDragon on topic G76 works but not 33
I admit the hal file has me a bit confused at this point, I have attached 2 files. One is the hal from StepConfig Wizard, the other is one
I did from examples, both give the same results.
G76 but no G33
Henry
I did from examples, both give the same results.
G76 but no G33
Henry
Last edit: 28 Dec 2014 09:52 by TejasDragon.
Please Log in or Create an account to join the conversation.
28 Dec 2014 21:56 #54335
by BigJohnT
Replied by BigJohnT on topic G76 works but not 33
I looked at the stepconfig file and it looks normal.
Try testing your index for proper polarity.
gnipsel.com/linuxcnc/tuning/encoder.html
JT
Try testing your index for proper polarity.
gnipsel.com/linuxcnc/tuning/encoder.html
JT
Please Log in or Create an account to join the conversation.
29 Dec 2014 00:28 - 29 Dec 2014 00:29 #54339
by PCW
Replied by PCW on topic G76 works but not 33
The problem seems to be that motion.spindle-at-speed is not connected in either of the the HAL files.
In the stepconf generated hal file, line 48 and lathe sample line 30 you have:
net spindle-at-speed => motion.spindle-at-speed
which connects motion.spindle-at-speed to the signal spindle-at-speed
but the signal spindle-at-speed is never connected to a source pin.
Normally this should connect to a "near" component that checks that
the actual spindle speed is sufficiently close to the commanded spindle speed
to begin the synchronized motion (is this a stepconf omission?)
In the stepconf generated hal file, line 48 and lathe sample line 30 you have:
net spindle-at-speed => motion.spindle-at-speed
which connects motion.spindle-at-speed to the signal spindle-at-speed
but the signal spindle-at-speed is never connected to a source pin.
Normally this should connect to a "near" component that checks that
the actual spindle speed is sufficiently close to the commanded spindle speed
to begin the synchronized motion (is this a stepconf omission?)
Last edit: 29 Dec 2014 00:29 by PCW.
Please Log in or Create an account to join the conversation.
29 Dec 2014 00:37 - 29 Dec 2014 00:38 #54340
by BigJohnT
Replied by BigJohnT on topic G76 works but not 33
Good catch Peter, I'll try and see what is missing from stepconf if I get time.
You can edit the HAL file and add the near component as shown here:
www.linuxcnc.org/docs/html/examples/spin...c_spindle_at_speed_a
A short intro to HAL is here:
www.linuxcnc.org/docs/html/hal/basic_hal.html
JT
You can edit the HAL file and add the near component as shown here:
www.linuxcnc.org/docs/html/examples/spin...c_spindle_at_speed_a
A short intro to HAL is here:
www.linuxcnc.org/docs/html/hal/basic_hal.html
JT
Last edit: 29 Dec 2014 00:38 by BigJohnT.
Please Log in or Create an account to join the conversation.
29 Dec 2014 00:51 #54341
by cmorley
They may be connected in the (unposted) postgui file as that's where stepconf puts those connections.
Replied by cmorley on topic G76 works but not 33
The problem seems to be that motion.spindle-at-speed is not connected in either of the the HAL files.
In the stepconf generated hal file, line 48 and lathe sample line 30 you have:
net spindle-at-speed => motion.spindle-at-speed
which connects motion.spindle-at-speed to the signal spindle-at-speed
but the signal spindle-at-speed is never connected to a source pin.
Normally this should connect to a "near" component that checks that
the actual spindle speed is sufficiently close to the commanded spindle speed
to begin the synchronized motion (is this a stepconf omission?)
They may be connected in the (unposted) postgui file as that's where stepconf puts those connections.
Please Log in or Create an account to join the conversation.
Time to create page: 0.092 seconds