Performing tasks during X-axis-movement

[tottish]

Hi!
I have a problem that someone in here might know how to solve.
I have a laser mounted in a 3-axis router and would like to be able to switch it on and off from G-code without having to stop the movement.

For example:
__________
G1 X30
G3 S100
G1 X50
__________

This will make the X-movement come to a stop before the laser is turned on and then accelerate up to the specified speed.
Can I make this operation with constant X-speed? Do I have to use the ClassicLadder for such an operation?

Alternatively: Is there a function in EMC2 that is able to compensate, in the M3 S-value (normally spindle-speed), for the velocity of the machine-head? I'm told there is a function like this in Mach3 and I guess it would do the trick for my laser problem.

Thnx!
/Tottish

[Big John T]

In 2.3 beta you can use M62/63 to do that.

http://www.linuxcnc.org/docview/deve...ec:M62-to-M65:

John

[tottish]

I don't think so:
"The actual change of the specified outputs will happen at the beginning of the next motion command. If there is no subsequent motion command, the queued output changes won't happen. It's best to always program a motion g-code (G0, G1, etc) right after the M62/63."

From what I can tell this means that the router has to come to a stop and then start moving again for an M62/63-command to "execute". I need it to turn the laser on while moving. Preferably I would like to be able to set the M3 PWM that I now use for the laser but if only on/off is possible I guess it will do.

Any other Ideas?

Regards
/Tottish

[Big John T]

No, It will act just the same if you didn't have the M62/63 in the line. Just keep in mind that the switching takes place at the start of the next move.

John

[Big John T]

For example
G0 X1 Y1 M62 ( Set up to switch on at next move)
G1 X1.5 M63 (on during this part of the move)
X2 M62 (off during this part of the move)
X3 M63 (on)
G0 X1 Y1 (off)

[Big John T]

hmm, got a double post...

anyway the above move will be one smooth move within the constraints of your system.

http://www.linuxcnc.org/docview/deve...epts.html#r1_1

So it might be needed to have a G1 move before and after to maintain speed as outlined above.

John

[tottish]

Sorry Big John. I'm new to G-code manipulation and I didn't realize that the M62/63-commands would fit in seamless. I tried doing the same thing with the M3-command and since that didn't work I thought that the code was executed line by line without any knowledge about what's on the next line. It seems I came to the wrong conclusion.

Is there any way to fit in the M3 command like that? It would just be awesome. If not I will probably have to sweep the whole image one time for every shade that I want.

Thanks a lot Big John and sorry for mistrusting you. =)

Regards
/Tottish

[Big John T]

No problem, you just didn't know.

AFAIK M62/63 are the only ones that don't pause motion but I might be wrong...

John

[tottish]

Hmm, I was wrong (again). It only works for me at slow speeds. At speeds over 500mm/min it becomes clear that it does stop (or at least slow down) between the lines.
Even without the M-commands it stops.
For example this block:
G1 X10
X 20
X30
Is performed in three distinct sequences at higher speeds. I have to double check for errors tomorrow. My head is spinning around right now.

Good Night from Norway!
/Tottish

[Big John T]

Did you set G64 Pnn ?

http://www.linuxcnc.org/docview/deve...ts.html#r1_1_3

For short moves at high speed this is needed. Also EMC will not go faster than it can stop so if your acceleration is low and your asking for high speeds it looks like a bumper car...

John

[tottish]

I have now. But I'm afraidit didn't help.
When I run this program>
T1M6
G64 P0.5
G1 Z0.5 F2100.0

G0X0.000Y0.000

G1X8.525F2100.0

x10
X11
X12
X33
X34
X35
X50

G0X0.000Y0.000

G0X0Y0

M30
Everything runs smooth and it seems as if the naive CAMthingy 'morphs' all the Xmoves together and in the CodeWindow of AXIS the highlight skips right down to the last Xline and stays there until the value X50 is reached.

When I run this program, however, it is all chopped up and not smooth at all>
T1M6
G64 P0.5
G1 Z0.5 F2100.0

G0X0.000Y0.000

G1X8.525F2100.0

x10 M62
X11 M63
X12 M62
X33 M63
X34 M62
X35 M63
X50

G0X0.000Y0.000

G0X0Y0

M30
The highlight is jumping from row to row.

Any more pointers of what might be wrong here (questionmark)

Regards,
Tottish

EDIT: Oh, and the P-value for the G64 makes no apparent difference.

[Big John T]

Just to be sure are you running 2.3 beta?

It looks like the CamThingy breaks when M62/63 comes into play...

John