G76 works but not 33
- TejasDragon
- Offline
- New Member
-
- Posts: 10
- Thank you received: 0
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.
- BigJohnT
-
- Offline
- Administrator
-
- Posts: 7000
- Thank you received: 1175
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
-
- Posts: 10
- Thank you received: 0
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.
- PCW
-
- Online
- Moderator
-
- Posts: 18404
- Thank you received: 5025
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
Please Log in or Create an account to join the conversation.
- BigJohnT
-
- Offline
- Administrator
-
- Posts: 7000
- Thank you received: 1175
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
-
- Posts: 10
- Thank you received: 0
I did from examples, both give the same results.
G76 but no G33
Henry
Please Log in or Create an account to join the conversation.
- BigJohnT
-
- Offline
- Administrator
-
- Posts: 7000
- Thank you received: 1175
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.
- PCW
-
- Online
- Moderator
-
- Posts: 18404
- Thank you received: 5025
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?)
Please Log in or Create an account to join the conversation.
- BigJohnT
-
- Offline
- Administrator
-
- Posts: 7000
- Thank you received: 1175
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
Please Log in or Create an account to join the conversation.
- cmorley
- Offline
- Moderator
-
- Posts: 7870
- Thank you received: 2125
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.