Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

error22 but the G-Code is correct #1235

Closed
ltspicer opened this issue May 11, 2019 · 7 comments
Closed

error22 but the G-Code is correct #1235

ltspicer opened this issue May 11, 2019 · 7 comments

Comments

@ltspicer
Copy link

ltspicer commented May 11, 2019

My G-Code:

`
(Generated with: DXF2GCODE, Version: Py3.6.7 PyQt5.12.2, Date: $Date: Thu Jan 3 16:29:29 2019 +0100 $)
(Created from file: ....)
(Output format description: G-CODE for LinuxCNC)
(Time: Sat May 11 23:42:18 2019)
G21 (Units in millimeters)
G90 (Absolute programming)
G64 (Default cutting) G17 (XY plane) G40 (Cancel radius comp.) G49 (Cancel length comp.)
G0 Z 20.000

(*** LAYER: Ebene_1 ***)

(* SHAPE Nr: 2 *)
G0 X 156.984 Y 58.969
M3 S1000
G0 Z 2.000
F120
G1 Z -0.100
F1000
G2 X 156.889 Y 59.250 I 0.513 J 0.330
G2 X 156.887 Y 59.300 I 0.624 J 0.050
G2 X 156.887 Y 59.323 I 0.614 J 0.000
.
.
.
`
First, I have to remove the title. Everything in parentheses ()
After starting in UGS 2 the error 22 appears:
'G2X1 56.887Y59.323I0.614J0.000': (error 22) Feed rate has yet been set or is undefined.
Is the J0.000 the problem?

In UGS 1.0.9 it works.

Is this a bug in UGS 2+ ?

@AbySet
Copy link

AbySet commented May 12, 2019

Take a look here: gnea/grbl#255

@ltspicer
Copy link
Author

ltspicer commented May 12, 2019

Is not possible to add a parameter in the startup from UGS?
The link says, i have to add a line in every gcode.
Why the error comes only on the 3rd G02 line?

@AbySet
Copy link

AbySet commented May 12, 2019

I am just a user like you trying to help people.
The question "Why the error comes only on the 3rd G02 line?" is actualy a good one.
Maybe Winder or breiler can analyse this issue.

@AbySet
Copy link

AbySet commented May 12, 2019

I just tested you gcode file by removing (comment) G64 line like this:

G21
G90
;G64
G0 Z 20.000

G0 X 156.984 Y 58.969
M3 S1000
G0 Z 2.000
F120
G1 Z -0.100
F1000
G2 X 156.889 Y 59.250 I 0.513 J 0.330
G2 X 156.887 Y 59.300 I 0.624 J 0.050
G2 X 156.887 Y 59.323 I 0.614 J 0.000

And all ran just fine (no errors) on my machine (first ran CHECK mode then run for real).

@breiler
Copy link
Collaborator

breiler commented Oct 27, 2019

Regarding G64, the editor now checks if the command is supported by the hardware and displays a hint. There was an issue with the coordinate parameters containing a space displaying errors which I've fixed.

image

I couldn't reproduce the error with the error 22 with missing feed parameter though. I'm closing this, reopen it if the error still exists and provide your current GRBL version.

@fbonin5491
Copy link

I have many errors in UGS , and it also in GRBL controler bluetooth.I think it does not accept more than one space between X.Y.Z an the coordinate.Because if i remove one space its ok , if i add it back it is not.Why UGS find 2 spaces for exemple after the command G3 X , they are not existants in the text file
(Generated with: DXF2GCODE)
(Version: Py3.10.12 PyQt5.15.6, Date: $Date: Mon Feb 6 21:49:45 2023 +0100 $)
(Created from file: /home/bobphils/Bobphils.dxf)
(Used Postprocessor: postpro_config.cfg)
(Output format description: G-CODE for GRBL)
(Time: Fri Aug 18 16:26:49 2023)
G21 (Units in millimeters)
G90 (Absolute programming)
M3 M8
G0 Z 15.000

(*** LAYER: 0 ***)
(Tool number: 1)
M6
S6000

(* SHAPE Nr: 9 *)
G0 X 105.623 Y 39.019
G0 Z 3.000
F150
G1 Z -0.200
F200
G3 X 100.832 Y 40.083 I -4.819 J -10.376
G3 X 99.842 Y 35.755 I -0.008 J -2.276
G2 X 99.843 Y 35.754 I -0.216 J -0.451
G1 X 105.592 Y 32.980
G2 X 104.167 Y 26.750 I -1.425 J -2.952
G2 X 97.879 Y 27.893 I -0.005 J 17.837
M9M5
M2 (Program end)

@breiler
Copy link
Collaborator

breiler commented Aug 18, 2023

@fbonin5491 please open a new issue and attach the sample gcode.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants