TinyG icon indicating copy to clipboard operation
TinyG copied to clipboard

Status of M6 gcode?

Open TheOncomingStorm opened this issue 8 years ago • 11 comments

What is the status of the M6 function thus far? I'm having an issue where I can't use the ChiliPeppr touch plate widget when my program calls an M6. Or rather when I do use the touch plate widget during a tool change it makes the TinyG unresponsive, usually requiring power cycling the TinyG. This is in more detail here:

https://www.synthetos.com/topics/hangs-due-to-attempted-use-of-touch-plate-during-program/#post-9908

Apparently this has to do with issue 75. My tool change macro is simple and the only thing it calls that affects this is the M6 command. Once it does that if I try to use the touch plate widget, TinyG locks up and becomes unresponsive.

TheOncomingStorm avatar Sep 11 '16 16:09 TheOncomingStorm

Anyone?

TheOncomingStorm avatar Nov 24 '16 17:11 TheOncomingStorm

Can you give your exact steps to replicate this issue outside of Chilipeppr. If I follow your information its when you issue an M6 in the middle of a program?

ril3y avatar Nov 25 '16 15:11 ril3y

@Hi, yes, that's essentially it. I run a program that has tool changes in it, and when it issues an M6, if I try to do use a G38.2, it locks up the TinyG and typically won't respond again until I press the reset button. So it goes like this...

Run program until M6. Attempt to do a G38.2. TinyG locks.

TheOncomingStorm avatar Nov 25 '16 22:11 TheOncomingStorm

I have not seen this happen myself, although I haven't issued a G38.2 after a tool change in a while, but what ChiliPeppr does on an M6 is simply not send any of the Gcode file after the M6 line. It essentially treats the M6 line as if it is the end of the Gcode file. Then when it sees the TinyG say it executed that M6 line it pops up the window in ChiliPeppr saying "ok, m6 pause". Then you can do whatever you want in ChiliPeppr. Then, when you unpause the Gcode widget it just starts playing the file again from the line after the M6. So, if you think about it, ChiliPeppr does pretty much nothing at all because it's just treating the Gcode file as if it is multiple files.

What would help on this bug better, is to show the actual Gcode from the Serial Port Console in ChiliPeppr that you do after the M6. My gut tells me this has nothing to do with M6 at all and simply is a crash on the G38.2 which I do recall seeing in older firmware.

BTW, I ran a ton of G38.2's over the last week and they worked like a champ.

chilipeppr avatar Nov 25 '16 22:11 chilipeppr

Ok, I've been away from the CNC for a while so I'll have to head down there and run one of the programs that was causing it. What is the best way to capture the gcode from the serial port console, I'm guessing a simple copy/paste, or is there a log or save function?

G38.2 works by itself just fine as far as I can tell. It seems to only be the combination of using it with M6 that causes the problem but that doesn't necessarily mean that M6 is the cause... Give me a day to churn something out. I'll make a really simple program so we don't have to deal with the full project I was working on.

TheOncomingStorm avatar Nov 25 '16 23:11 TheOncomingStorm

Run spjs via verbose? John thoughts?

On Fri, Nov 25, 2016, 6:32 PM Eric [email protected] wrote:

Ok, I've been away from the CNC for a while so I'll have to head down there and run one of the programs that was causing it. What is the best way to capture the gcode from the serial port console, I'm guessing a simple copy/paste, or is there a log or save function?

G38.2 works by itself just find as far as I can tell. It seems to only be the combination of using it with M6 that causes the problem but that doesn't necessarily mean that M6 is the cause... Give me a day to churn something out. I'll make a really simple program so we don't have to deal with the full project I was working on.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/synthetos/TinyG/issues/186#issuecomment-263032319, or mute the thread https://github.com/notifications/unsubscribe-auth/AAOJM3Tswcdo1TLdcuWVBAZBrL50fhoiks5rB2_wgaJpZM4J6DK3 .

ril3y avatar Nov 26 '16 02:11 ril3y

Nah. That won’t help. I bet tinyg gives an error, but it’s hidden in serial port console unless you turn off the filter (funnel) icon.

From: Riley [mailto:[email protected]] Sent: Friday, November 25, 2016 6:41 PM To: synthetos/TinyG [email protected] Subject: Re: [synthetos/TinyG] Status of M6 gcode? (#186)

Run spjs via verbose? John thoughts?

On Fri, Nov 25, 2016, 6:32 PM Eric <[email protected]mailto:[email protected]> wrote:

Ok, I've been away from the CNC for a while so I'll have to head down there and run one of the programs that was causing it. What is the best way to capture the gcode from the serial port console, I'm guessing a simple copy/paste, or is there a log or save function?

G38.2 works by itself just find as far as I can tell. It seems to only be the combination of using it with M6 that causes the problem but that doesn't necessarily mean that M6 is the cause... Give me a day to churn something out. I'll make a really simple program so we don't have to deal with the full project I was working on.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/synthetos/TinyG/issues/186#issuecomment-263032319, or mute the thread https://github.com/notifications/unsubscribe-auth/AAOJM3Tswcdo1TLdcuWVBAZBrL50fhoiks5rB2_wgaJpZM4J6DK3 .

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHubhttps://github.com/synthetos/TinyG/issues/186#issuecomment-263040098, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AA8jlae7umEvGhrQIfQv57-GzRdZqasrks5rB5wtgaJpZM4J6DK3.

johnlauer avatar Nov 26 '16 04:11 johnlauer

Sorry for the delay. I think I removed the filter(it's hard to tell...no color change or the like to the filter button) but regardless I tried it, then pressed the filter button again and tried it again, both gave me the same output.

http://pastebin.com/71MzU1Dy

TheOncomingStorm avatar Dec 13 '16 20:12 TheOncomingStorm

I tHink ChiliPeppr just looks for m6 not m06. That could be it. That's a small code change.

On Dec 13, 2016 12:44 PM, "Eric" [email protected] wrote:

Sorry for the delay. I think I removed the filter(it's hard to tell...no color change or the like to the filter button) but regardless I tried it, then pressed the filter button again and tried it again, both gave me the same output.

http://pastebin.com/71MzU1Dy

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/synthetos/TinyG/issues/186#issuecomment-266856353, or mute the thread https://github.com/notifications/unsubscribe-auth/AHidbVuoJPdaAycHXUMqMMH2oSCAR8tQks5rHwO2gaJpZM4J6DK3 .

chilipeppr avatar Dec 13 '16 20:12 chilipeppr

I probably also had this as M6 as well. I changed the tool change macro several times to debug, and I'm pretty sure that I changed from M6 to M06 when I was reading a page on Gcode syntax.

TheOncomingStorm avatar Dec 13 '16 21:12 TheOncomingStorm

My gut tells me this is a TinyG bug then. G38.2 has crashed on me in the past in older firmware versions.

chilipeppr avatar Dec 13 '16 21:12 chilipeppr