difference between motmod M-Codes (eg. M62) to custom M-Codes

More
10 Nov 2023 09:21 #285015 by piflixe
Hi there,

in the implementation of a tool changer I came across the motmod M-Codes (such as M62). I was wondering what exactly is the difference to defining custom M-Codes. My hopes are that M6X would have better real-time performance than custom M-Codes but I wanted to make sure that is correct.

I recently implemented a laser-engraver using custom M-Codes. Is it recommended to use M6X rather than custom M-Codes for turning the laser on and off as well? If the machine waits for some time it could leave a burn mark on the part.

Looking forward to your replies! Kind regards.

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

More
10 Nov 2023 12:17 #285023 by andypugh
There are actually three types of M-code.

Built-in M-codes
Custom M-codes (M100 - M199)
Remapped M-codes.

The built-in ones are realtime

The Custom ones shell out to an external executable file (bash, python, whatever) and are not realtime.

Remapped M-codes can be realime if the interpreter converts them into canonical commands in the queue (even if they are Python, as long as the result is commands in the realtime queue)

At least, that is my understanding of the situation.

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

More
13 Nov 2023 13:12 #285251 by piflixe
Thanks for the reply and the explanation. So I guess it would be best to use M62 / M63 to turn a laser on and off on an engraving or cutting machine?

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

More
13 Nov 2023 13:56 #285256 by andypugh
Yes, I think that would be better, to keep the laser synched to the motion.

But also see: linuxcnc.org/docs/devel/html/man/man9/raster.9.html
(Only in the 2.10 dev version of LinuxCNC)

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

Time to create page: 0.142 seconds
Powered by Kunena Forum