Delay motion - spindle spinup

More
12 Dec 2019 22:59 - 13 Dec 2019 00:58 #152559 by bevins
I found this code from Tod in the forum and just want some clarification.
If I read this right I could replace "sets spindle-at-speed true" with this and it will delay motion for the time delay set.
Is that correct?
loadrt timedelay count=1
addf timedelay.0 servo-thread

setp timedelay.0.on-delay 5
net spindle-on => timedelay.0.in
net spindle-timer <= timedelay.0.out

net spindle-timer => motion.spindle-at-speed
Last edit: 13 Dec 2019 00:58 by bevins.

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

More
12 Dec 2019 23:42 #152562 by MaHa
Replied by MaHa on topic Delay motion - spindle spinup
I use a similar configuration, rapid moves are done while timedelay, only feed mode is stoped during delay.

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

More
13 Dec 2019 12:49 #152598 by bevins
motion.spindle-at-speed does not exist.

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

More
13 Dec 2019 13:02 #152599 by cmorley
2.8 + it has changed:
spindle.0.at-speed

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

More
13 Dec 2019 13:26 - 13 Dec 2019 13:27 #152600 by bevins
loadrt timedelay count=1
addf timedelay.0 servo-thread
setp timedelay.0.on-delay 5
net spindle-on => timedelay.0.in
net spindle-timer <= timedelay.0.out
net spindle-timer => spindle.0.at-speed

This does not work. It never gets spindle-on

Is there a quick fix for this?
Last edit: 13 Dec 2019 13:27 by bevins.

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

More
13 Dec 2019 14:12 #152602 by cmorley
The quickest fix would be to use halmeter/halcmd to probe where the problem is :)

Is the spindle-on signal connected to anything?
If it is, use halmeter to see if it changes state properly.
if not, connect it to spindle.0.on

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

More
13 Dec 2019 15:50 - 13 Dec 2019 15:52 #152605 by bevins

The quickest fix would be to use halmeter/halcmd to probe where the problem is :)

Is the spindle-on signal connected to anything?
If it is, use halmeter to see if it changes state properly.
if not, connect it to spindle.0.on


ACK...... spindle-on is not connected to anything. spindle-enable is connected to spindle.0.on
Was staring me right on the face.
Last edit: 13 Dec 2019 15:52 by bevins.

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

More
13 Dec 2019 15:58 #152607 by bevins
Why is spindle.0.on connected to spindle-enable?

Shouldn't this be connected to spindle-on? This config was built with pncconf. Was it changed on purpose or is this an error?

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

More
07 Jan 2020 15:13 #154217 by andypugh
If you are using a version of linuxCNC 2.8+ then the spindle pins now have names like
spindle.0.at-speed

This is a result of changes that allow LinuxCNC to control multiple spindles.

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

More
07 Jan 2020 19:29 #154238 by cmorley

Why is spindle.0.on connected to spindle-enable?

Shouldn't this be connected to spindle-on? This config was built with pncconf. Was it changed on purpose or is this an error?


Because pncconf had a bug in it - should be fixed now.

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

Time to create page: 0.100 seconds
Powered by Kunena Forum