Bug parsing GCode comments

JPoepsel

Hi all!

Not only, that the ddcsv hangs, if it parses too long comments, it seems to try to interprete them!
Why else should a line of GCode like

(Toolpaths: Planen1, Planen1 [4], Planen1 (3), Planen1 (2))

cause a syntax error?! If the "[4]" is deleted, all works perfect...

Two solutions to this problem:

1) Update your post processor to not generate this sort of comments
2) (More unlikely, since Digital Dream seems not to read this forum and react accordingly...): We get a bug fix...


Cheers

Josef

JPoepsel

Hello again!

It may be I was wrong talking about a bug in the comment parsing.
When I tested it, I deleted the complete comment line and the G code worked after this.
I think the real Problem are the nested "()" in the comment. And this are due to an error of the post processor from Brian Right, which I use (after some modifications) for Fusion 360 (see http://www.brainright.com/Projects/CNCController/DDCSV11.cps).

There the function "writeComment" is coded as

function writeComment(text) {
  text = text.replace('(', '[').replace(')', ']');
  writeln("(" + text + ")");
}

This code replaces only the first "(" and ")" in a comment, others are untouched.
I changed it to

function writeComment(text) {
  text = text.replace(/\(/g," ").replace(/\)/g," ");
  writeln("(" + text + ")");
}

using the global replacement of the JS-replace function. To be on the save side, I replaced the brackets with a space, not with "[" and "]".
Those, who use Brians Post Processor should change it...

Josef

JPoepsel

Hi all!

Just to inform you: I contacted Jay (not Brian, sorry Jay) directly and he already updated http://www.brainright.com/Projects/CNCController/DDCSV11.cps!

Josef