Stop crashing/freezing while debugging G code and subs

More
07 Mar 2020 08:54 #159388 by Nitram
Hello.

I while a go I wrote some G Code which contained various sub routines, and if the program wasn't quite right it froze the controller. This made it painful for debugging as I had to restart and re-home the machine to retest each time I made a correction.

After that I read somewhere there is a setting which allows a G Code prog to run and if there is an error, it alerts, but doesn't crash out, for debugging purposes.

I simply cannot find the reference for that setting again...

Can someone help me out please?

Thanks,
Marty.

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

More
07 Mar 2020 09:14 #159390 by cmorley

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

More
07 Mar 2020 12:10 #159404 by Nitram
Thanks Chris.

No unfortunately that is not it. The functionality was that with a broken g code prog it would simply error out rather than freeze/ crash the entire control. In this way the line it crashed on could be modified without having to restart LCNC.

I wonder if I am trying to recall a certain component of the Features bit mask which does this? Having said that I cannot find the bit mask definitions anywhere aside from 1 through 16.

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

More
08 Mar 2020 03:08 - 08 Mar 2020 03:48 #159448 by Nitram
I found it I think:
(Excerpt)

To make these errors non-fatal warnings on stderr, set bit 0x20 in the [RS274NGC]FEATURE= mask ini option.

0x20 being 32
Although I have found a comment in my ini file that 44 is the correct setting.

I am also unsure whether there is a typo in the above excerpt as in my ini file it is FEATURES rather than the singular as written above...

Cheers everyone :)
Last edit: 08 Mar 2020 03:48 by Nitram.

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

More
08 Mar 2020 06:26 - 08 Mar 2020 06:26 #159456 by cmorley
I should find somewhere in the docs for that...
Was this remap ? just sub code?

Chris
Last edit: 08 Mar 2020 06:26 by cmorley.

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

More
08 Mar 2020 21:30 - 08 Mar 2020 21:33 #159515 by Nitram
At the very bottom of the "o codes doc" (section 10, errors) is the quoted excerpt

linuxcnc.org/docs/html/gcode/o-code.html

Deeper info is within the replies to an earlier question I posted on the forums asking the same question (which I finally re-found...).

forum.linuxcnc.org/38-general-linuxcnc-q...-o-code-fatal-errors

Cheers
Marty.
Last edit: 08 Mar 2020 21:33 by Nitram.

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

Time to create page: 0.096 seconds
Powered by Kunena Forum