gSender Surfacing "Test Run" doesn't seem to work

gSender ❓ Question
1

I have gSender 1.2.2 connected to a the LongMill MK2 30 x 30 and I’m trying to surface my spoilboard for the first time. I’m able to generate the gcode and run the Outline successfully. My problem is with the “Test Run”. When I action the option all that happen is a “Checking gcode file” message flashing rapidly and nothing else. There is no error message that I coud see anywhere.

Is this a known bug or am I doing something wrong? I would really love to do a test run before ruining my spoilboard.

This is the gcode generated:

(Header)
(Generated by gSender from Sienci Labs)
G54
G20 ;inches
G90
G0 X0 Y0 Z0.12
G1 F98.43
M3 S12000
(Header End)


(*** Layer 1 ***)
(Covering Surfacing Perimeter)
(Ramping into Material)
G91
G1 Y1.02 Z-0.13999999999999999
G1 Y0.197
G1 Y-1.217
G90
(End of Ramping into Material)

G1 Y33.1
G1 X31.626
G1 Y0
G1 X0
(End of Covering Surfacing Perimeter)

G1 Y0.5
G1 X31.626
G1 Y1
G1 X0

G1 Y1.5
G1 X31.626
G1 Y2
G1 X0

G1 Y2.5
G1 X31.626
G1 Y3
G1 X0

G1 Y3.5
G1 X31.626
G1 Y4
G1 X0

G1 Y4.5
G1 X31.626
G1 Y5
G1 X0

G1 Y5.5
G1 X31.626
G1 Y6
G1 X0

G1 Y6.5
G1 X31.626
G1 Y7
G1 X0

G1 Y7.5
G1 X31.626
G1 Y8
G1 X0

G1 Y8.5
G1 X31.626
G1 Y9
G1 X0

G1 Y9.5
G1 X31.626
G1 Y10
G1 X0

G1 Y10.5
G1 X31.626
G1 Y11
G1 X0

G1 Y11.5
G1 X31.626
G1 Y12
G1 X0

G1 Y12.5
G1 X31.626
G1 Y13
G1 X0

G1 Y13.5
G1 X31.626
G1 Y14
G1 X0

G1 Y14.5
G1 X31.626
G1 Y15
G1 X0

G1 Y15.5
G1 X31.626
G1 Y16
G1 X0

G1 Y16.5
G1 X31.626
G1 Y17
G1 X0

G1 Y17.5
G1 X31.626
G1 Y18
G1 X0

G1 Y18.5
G1 X31.626
G1 Y19
G1 X0

G1 Y19.5
G1 X31.626
G1 Y20
G1 X0

G1 Y20.5
G1 X31.626
G1 Y21
G1 X0

G1 Y21.5
G1 X31.626
G1 Y22
G1 X0

G1 Y22.5
G1 X31.626
G1 Y23
G1 X0

G1 Y23.5
G1 X31.626
G1 Y24
G1 X0

G1 Y24.5
G1 X31.626
G1 Y25
G1 X0

G1 Y25.5
G1 X31.626
G1 Y26
G1 X0

G1 Y26.5
G1 X31.626
G1 Y27
G1 X0

G1 Y27.5
G1 X31.626
G1 Y28
G1 X0

G1 Y28.5
G1 X31.626
G1 Y29
G1 X0

G1 Y29.5
G1 X31.626
G1 Y30
G1 X0

G1 Y30.5
G1 X31.626
G1 Y31
G1 X0

G1 Y31.5
G1 X31.626
G1 Y32
G1 X0

G1 Y32.5
G1 X31.626
G1 Y33
G1 X0


(Returning to Zero)
G0 Z0.12
G0 X0 Y0
(End of Returning to Zero)

(*** End of Layer 1 ***)


(*** Layer 2 ***)
(Move to Starting Height)
G0 Z0.1
(End of Move to Starting Height)

(Covering Surfacing Perimeter)
(Ramping into Material)
G91
G1 Y1.02 Z-0.13999999999999999
G1 Y0.197
G1 Y-1.217
G90
(End of Ramping into Material)

G1 Y33.1
G1 X31.626
G1 Y0
G1 X0
(End of Covering Surfacing Perimeter)

G1 Y0.5
G1 X31.626
G1 Y1
G1 X0

G1 Y1.5
G1 X31.626
G1 Y2
G1 X0

G1 Y2.5
G1 X31.626
G1 Y3
G1 X0

G1 Y3.5
G1 X31.626
G1 Y4
G1 X0

G1 Y4.5
G1 X31.626
G1 Y5
G1 X0

G1 Y5.5
G1 X31.626
G1 Y6
G1 X0

G1 Y6.5
G1 X31.626
G1 Y7
G1 X0

G1 Y7.5
G1 X31.626
G1 Y8
G1 X0

G1 Y8.5
G1 X31.626
G1 Y9
G1 X0

G1 Y9.5
G1 X31.626
G1 Y10
G1 X0

G1 Y10.5
G1 X31.626
G1 Y11
G1 X0

G1 Y11.5
G1 X31.626
G1 Y12
G1 X0

G1 Y12.5
G1 X31.626
G1 Y13
G1 X0

G1 Y13.5
G1 X31.626
G1 Y14
G1 X0

G1 Y14.5
G1 X31.626
G1 Y15
G1 X0

G1 Y15.5
G1 X31.626
G1 Y16
G1 X0

G1 Y16.5
G1 X31.626
G1 Y17
G1 X0

G1 Y17.5
G1 X31.626
G1 Y18
G1 X0

G1 Y18.5
G1 X31.626
G1 Y19
G1 X0

G1 Y19.5
G1 X31.626
G1 Y20
G1 X0

G1 Y20.5
G1 X31.626
G1 Y21
G1 X0

G1 Y21.5
G1 X31.626
G1 Y22
G1 X0

G1 Y22.5
G1 X31.626
G1 Y23
G1 X0

G1 Y23.5
G1 X31.626
G1 Y24
G1 X0

G1 Y24.5
G1 X31.626
G1 Y25
G1 X0

G1 Y25.5
G1 X31.626
G1 Y26
G1 X0

G1 Y26.5
G1 X31.626
G1 Y27
G1 X0

G1 Y27.5
G1 X31.626
G1 Y28
G1 X0

G1 Y28.5
G1 X31.626
G1 Y29
G1 X0

G1 Y29.5
G1 X31.626
G1 Y30
G1 X0

G1 Y30.5
G1 X31.626
G1 Y31
G1 X0

G1 Y31.5
G1 X31.626
G1 Y32
G1 X0

G1 Y32.5
G1 X31.626
G1 Y33
G1 X0


(Returning to Zero)
G0 Z0.12
G0 X0 Y0
(End of Returning to Zero)

(*** End of Layer 2 ***)


(Footer)
M5 ;Turn off spindle
(End of Footer)
2

I think you just don’t understand what Test Run does. It uses GRBL’s Check mode, which just parses all lines without running any movements. Test run just turns on Check mode, sends all lines to see if it’s all valid g-code, and turns check mode off. What you described is perfectly in line with that - I’m not sure what behaviour you were expecting.

1 Like
3

@jbf Since I was guilty this past week of posting without first reading the gSender docs, I’ll add to @KGN post. :grinning:

Here is the description of the Test feature from the gSender docs

“As well, the ‘Test Run‘ button enables gSender to go through your g-code to look for potential errors or unknown commands, without running it on the machine yet. This will give you an idea of what running your job will look like before running it for real.”

1 Like
4

@KNG, thank you for your answer.
The problem here from my point of view is that the function doesn’t report what it did, or did it too fast for a normal human being to read. I was expecting some sort of success message or maybe some movement of the spindle. I may be picky (developper deformation perhaps) but it’s bad practice not to give your user visual clues as to what just went down. Anyway, I guess it only report on failures.

5

Thank you @gwilki . I’m usually very good at figuring software out without resorting to manual and I would have figured thi one out. The reason I wrote is mostly because of the lack of visual clues. I was “forced” into RTFM in this case but it didn’t help much because I kept expecting some confirmation message or CNC simulation. Thank you for confirming that it did indeed worked.

6

@jbf I understand your point of view entirely. You may want to post in the gSender suggestion topic putting your idea out as an improvement to gSender.

Since gSender is working as intended, I’ll close this thread.