Broken G-code verification in 1.5.2

[_Michael]

There was a question about where the ‘Verify G-code’ button is in the new UI over here.

I’ll quote some of my reply to explain the bug.

@_Michael

I went looking through the config section to see what I could find. The closest thing I could find was ‘Warn if bad file’ so I turned that on.

Then I changed a line in a G-code file from

G2 X0.095 Y-10.323 Z-1.500 I-0.372 J-0.076 K0.000 F2000.000

to

G216752 XYZABC0.095 Y-10.323 Z-1.500 I-0.372 J-0.076 K0.000 F2000.000

Then I hit the file reload button and I did not receive any warning. Okay, maybe it doesn’t work with a reload, let’s try closing gSender and starting fresh. I connected and then loaded the file and there is still no warning.

I also tried

G2 X0.0 95 Y-10.3 23 Z-1.5 00 I-0.37 2 J-0.0 76 K0.0 00 F20 00.000

and

G2 X0.0 95 Y-10.3 23 Z-1.5 00 I-0.37 2 J-0.0 76 K0.0 00 F20 00.000
#include <stdio.h>
int main(int argc, char* argv[]) {
  printf("Does G-code allow inline C code?");
  return 0;
}
G2 X-0.345 Y-9.887 Z-1.500 I-0.091 J0.348 K0.000 F2000.000

for bad G-code.

So unless the warnings are in a new super secret place I think something is broken.

[chrismakesstuff]

@_Michael thanks for the report! We dug into things and found that actually for some reason this verification feature had stopped working almost 2 years ago and had just never been noticed by anyone

As of 1.5.3, the features is now fully implemented back in, alongside some other catches we added in inspired by your test g-code. Give it a shot and hopefully it’s now up to your standard