motion.spindle-at-speed

More
04 Nov 2016 13:22 #82417 by beltramidave
I want to prevent machine movement until my spindle is at speed. I believe that if I use an output signal from the vfd tied to the motion.spindle-at-speed hal command, that I can accomplish this. By doing this, will it still allow me to jog and home the machine without the spindle running? I only want to prevent movement when running a program.

Does anyone have the code that they wish to share to accomplish this?

Thanks

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

More
04 Nov 2016 13:59 #82420 by beltramidave
Is it as simple as adding this to my HAL file? I already have parallel port setup.

net spindle-at-speed <= parport.1.pin-03-out
net spindle-at-speed => motion.spindle-at-speed

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

More
04 Nov 2016 14:22 - 04 Nov 2016 14:24 #82421 by Todd Zuercher
Yes, the machine will only pause to wait for the spindle at speed signal before a cutting move. It will still perform any G0 moves then wait at the start of the first G1,G2... until the pin goes true. All non auto movement is unchanged (jogging, MDI...) Once the at speed signal goes true the machine will not pause again if it later goes false, unless a spindle speed change or start is commanded.
Last edit: 04 Nov 2016 14:24 by Todd Zuercher.
The following user(s) said Thank You: beltramidave

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

More
05 Nov 2016 03:13 #82479 by beltramidave

Yes, the machine will only pause to wait for the spindle at speed signal before a cutting move. It will still perform any G0 moves then wait at the start of the first G1,G2... until the pin goes true. All non auto movement is unchanged (jogging, MDI...) Once the at speed signal goes true the machine will not pause again if it later goes false, unless a spindle speed change or start is commanded.


My application is multiple drilling routines, so my moves between holes are at full speed, I have no G1 moves. Obviously my plunge speed is at a reduced feedrate. Would this still work then?

Thanks for your help.
Dave

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

More
05 Nov 2016 12:03 #82490 by Todd Zuercher
So what mode are your drilling plunges? As long as they are not G0 moves it should wait. Are you using drilling cycles like G81-G83?

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

More
05 Nov 2016 12:48 #82493 by beltramidave
Yes, using a G81 drill routine.

G20 G90 G64 G40 G58
( INCHES, ABSOLUTE MODE, CONTINUOUS MODE, CANCEL CUTTER RADIUS COMP, SELECT COORDINATE SYSTEM )
G0 Z.50
( RAPID TO: Z=.50 )
G17
( XY PLANE SELECT )
M3 S5000
( START SPINDLE CW @ 5000 RPM )
G4 P1.50
( DWELL TIME = 1.5 SEC )
G0 X2.875 Y-11.8125
( RAPID TO CAD DWG COORDINATES: X=2.875 Y1=11.8125 )
G98
( RETRACT TO "R" POSITION )
G81 X2.875 Y-11.8125 Z-1.70 R0.50 F30.0
( RAPID TO CAD DWG COORDINATES: X=2.875 Y1=11.8125 )
G81 Y-16.8125 Z-1.70
( Y2=16.8125 )
G80
( CANCEL DRILL CYCLE )
M5
( STOP SPINDLE )
G0 Z.50
( RAPID TO: Z=.50 )
M30
( OTHER STOP CODES )

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

More
05 Nov 2016 20:30 #82498 by Todd Zuercher
I believer that won't be a problem at all,
It "should" stop and wait at the beginning of your G81 line for the spindle at speed single to go true, if it hasn't already.
To be honest I haven't ever used a canned cycle in Linuxcnc so I can't say for sure if that is the case. All of my Linuxcnc machines are wood carving routers and I do use the spindle at speed signal with them. The spindles can take 10-20 seconds to spin up, and even after starting the spindle first thing at the beginning of the file and making a 5-8ft positioning move, the machine will still often have to wait a few seconds for the spindle(s) to come up to speed before starting the first cut.

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

More
05 Nov 2016 22:13 - 05 Nov 2016 22:14 #82501 by beltramidave
Thank you Todd. When I get my spindle and vfd, I will report back as to if it works.
Last edit: 05 Nov 2016 22:14 by beltramidave.

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

More
12 Apr 2017 15:39 #91252 by HalaszAttila
Hello,

here is my video about motion.spindle-at-speed behavior. Linuxcnc version is 2,7,8.
The spindle-at-speed signal is a digital input, and i activate with push button. In auto mode i open a lathepawn.ngc example g code, and run it.
At the first and second G01 moves the feed is waiting for spindle-at-speed signal, as you can see on video (i two times pressed the button). But after second feed move and until the end, never wait again for spindle at speed signal before feed move. And this is not clear for me.

On the end of the video I paused the program, stopped the spindle and resume the program without spindle rotation, but the move doesnt wait for spindle at speed.

Why?

In the hal file the pusbutton input is just connected to motion.spindle-at-speed pin, and to gmoccapy led.

Here is a video link, and a first some line from g code.


G21
G64
G18 G8
G00 X13.5 Z1.0 S1000 M3
Z0.488
G94 G01 X-1.0 F50.0
Z0.975
G00 X0.383 Z1.269
X13.5
Z0.0
G01 X-1.0
Z0.488
G00 X0.383 Z0.782
X13.5
Z1.0
Z2.0
X11.237
G01 Z-34.973 F50.0
X12.2 Z-35.95
Z-37.95
X12.625

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

More
13 Apr 2017 14:28 #91313 by andypugh
Replied by andypugh on topic motion.spindle-at-speed
linuxcnc.org/docs/html/config/core-compo...html#sec:motion-pins

Describes what is expected. I believe that the system only pauses for spindle-at speed when the motion-type switches from G0 to G1 or when the spindle speed request changes.

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

Time to create page: 0.099 seconds
Powered by Kunena Forum