Where is Verify Job (Mac)

gSender ❓ Question
1

I am using gSender 1.5.2 on a Mac. As hard as I look, I cannot find the Verify Job function, button etc. Please can someone tell me where it is.

I have Start, Pause, Stop, Outline, Start From, but I cannot see Verify Job.

Thanks

No longer supporting Test Run/ Verify
2

I have 1.5.2 on Linux and I don’t see it either.

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.

Broken G-code verification in 1.5.2
3

Thanks for investigating

Julian

1 Like
4

@JulianG I’ve moved your question to the gSender question category where it will be more likely to be seen by the Sienci gSender group.
I believe that @chrismakesstuff has previously said that the verify button is gone, but the function should still be there. I believe that it should kick in when you click to run the job. Since @_Michael seems to have shown that is not happening, something is not going as planned.
I’m not able to access a Windows-based installation of 1.5.2 to see if it is working properly in windows, but perhaps someone else here can add to the topic by doing that.

5

I never actually tried to run the file because because the description says “Warns if any invalid commands ore found when a file is opened”. I probably should have tried that!

I removed the bad G-code I had so I’ll just put ‘hello’ in a good file and run it.

G2 X-0.321 Y10.099 Z-1.500 I0.732 J0.030 K0.000 F2000.000
ok
hello
ok
G2 X0.258 Y10.233 Z-1.500 I0.331 J-0.114 K0.000 F2000.000
error:2 (Bad number format)
ok
G1 X0.330 Y10.129 Z-1.572 F2000.000
ok

It stopped after the error but there wasn’t any indication of why until I checked the console. And to be clear when I say stopped I just mean the current line stopped increasing and the visualizer stopped moving. It never ended the job, I had to hit the stop button in gSender.

Tested with grbl on a board without a machine.

6

This seems to me like two separate things:

  1. We chose to leave out the Verify button in this new version of gSender since we were finding that most people weren’t using it. We have noted down though that we might in the future re-introduce it as a setting for when you load a new file it could automatically verify it for you
  2. To @_Michael I think something’s gone sideways with our file checking process in this new version if those files are getting through no problem, or stopping up while running with no notice, so we’ll have to take a look into that
1 Like