different lines at X and Y axis

Resources Common Problems
25

I forgot to include F and S values on the G1 line. It should be:

G1 X100 Y10 F600 S64

The F is feed rate (50mm/sec) and the S is power level (64 out of 255 is 25%)

26

Good Morning,
Thanks first for the help and info.
But now I do not know what to do anymore.
I again checked all connections and found no error.
On Tuesday I get a new power supply for the laser, to exclude this error.

I also drew the square and saved it as a gcode file. I insert the gcode below. Since I do not know if there is a mistake in it.

Thank you for your help.
Greetings Andre ’

; LightBurn 0.9.07
; GRBL device profile, user origin
G00 G17 G40 G21 G54
G90
G0 X0 Y0
G91
M4
; Cut @ 1300 mm/min, 40% power
M8
G0X59Y-59
G1X-118S102F1300
G1Y118
G1X118
G1Y-118
M9
G1S0
M5
G90
; return to user-defined finish pos
G0 X0 Y0
M2

27

There are no mistakes in the GCode - it is very simple.

G00 G17 G40 G21 G54    ; setup
G90                    ; use absolute coordinates
G0 X0 Y0               ; go to the user origin (X0 Y0)
G91                    ; switch to relative coordinates
M4                     ; use variable power mode
M8                     ; turn on air assist pin
G0X59Y-59              ; rapid move to the starting corner
G1X-118S102F1300       ; cut along X at 40% power, 1300mm/min
G1Y118                 ; cut along Y
G1X118                 ; cut along X
G1Y-118                ; cut along Y
M9                     ; turn off air assist pin
G1S0                   ; set laser power to 0
M5                     ; turn off laser
G90                    ; switch to absolute coordinates
G0 X0 Y0               ; return to finish position  (X0 Y0)
M2                     ; end of job
28

okay.
So it can only be a hardware error.
Cables, contacts, power supply and so on …
Thank you anyway that you have tried.
So I have to try to find the mistake.

29

Hello everybody,
I am still on the troubleshooting.
Now I had no more nerve for it and have again milled something.
I had with UGS as a gcode transmitter, when sending the gcodes an error.
“error when starting the data stream zero”

and another mistake occurred in the middle of the mowing.
the CNC just stopped.
and on UGS was no mistake.
In the macro bar, there were only no more commands.
It also did not pause and start again.

now my question.
I’m not the expert sorry.
Can my mistake on the x-axis when working with the laser possibly synonymous to it?
Maybe I have a mistake in my wiring?

Thank you for your help in advance.

Greetings Andre ’

30

Hello everybody,
a little update to my problem.
The supplied power supply with 3 amps, has absorbed the ghost. (it had become warm while burning):verzog das Gesicht:
Now I have a new one with 5 amps.:leicht lächelndes gesicht:
The laser supplier recommends taking a 5 minute break after 20 minutes.
Since I have given up cutting with the time with respect to my problem, I’m just trying to burn in pictures.
Now I’ve tried in lightburn to find a setting where I burn the automatically after a while to pause.
Is this setting available? Or is that not technically possible? :Denken:

Thank you in advance for your help.
Greeting Andre

31

There isn’t a function for periodic pausing, no.

32

Is that perhaps planned for one of the next updates?

33

You can add your support for adding this feature by signing up on our Feature Request site and placing your vote for the linked item below.

34

Thanks Rick for this hint.
I think that many (very many) have this problem.
This option would be invaluable as Carlos writes in the thread.

Thanks again and I hope that the thread helps.

Greetings Andre

35

Hello everybody,
I screwed up again.
Since I am still looking for a solution to my X axis problem, I decided today to upgrade my X-Carve after 3 years.
I finally managed to connect my x-y and Z axis limit switches to the g-shield. as in this guide http://x-carve-instructions.inventables.com/xcarve2015/step14/.
I also installed a Z touch plate (on Arduino pin A5 and GND). Then I tried the touch panel in UGS first. And what can I say, it worked wonderfully (I’m very proud of myself as an unskilled electrician)
But then my problem came when I was looking for or setting the XYZ home switches.
UGS went into ALARM and it was no longer possible to write a command to the console.
Then I opened Lightburn and looked at my GRBL settings.
Shortly after entering $$, the error also occurred here.
I’m going to attach the bug.
Sorry for my english.
Maybe someone has an idea what I did wrong.

Greetings Andre ’

Waiting for connection …
Waiting for connection …
Port opened, waiting for response.
Grbl 1.1h [’$’ for help]
[MSG: ‘$ H’ | ‘$ X’ to unlock]
[MSG: Caution: Unlocked]
OK
$$
$ 0 = 10
$ 1 = 255
$ 2 = 0
$ 3 = 3
$ 4 = 0
$ 5 = 1
$ 6 = 0
$ 10 = 115
$ 11 = 0020
$ 12 = 0002
$ 13 = 0
$ 20 = 0
$ 21 = 1
$ 22 = 1
$ 23 = 3
$ 24 = 25,000
$ 25 = 750,000
$ 26 = 250
$ 27 = 1,000
$ 30 = 255
$ 31 = 0
$ 32 = 1
$ 100 = 40,000
$ 101 = 40,000
$ 102 = 188,976
$ 110 = 8000.000
$ 111 = 8000.000
$ 112 = 500,000
$ 120 = 500,000
$ 121 = 500,000
$ 122 = 50,000
$ 130 = 790,000
$ 131 = 790,000
$ 132 = 100,000
OK
Starting stream
Stream completed in 0:00
ALARM: 1
[MSG: Reset to continue]

36

“ALARM:1” : _(“Hard limit triggered. Machine position is likely lost due to sudden and immediate halt. Re-homing is highly recommended.”),

This probably means the controller hit a limit switch that it was not expecting to hit, so you may have them wired incorrectly (to the wrong axis, for example) or have the homing directions set wrong. I haven’t configured a GRBL device for homing before, so I won’t be much help beyond this. The GRBL docs should help: https://github.com/gnea/grbl/wiki/Grbl-v1.1-Configuration#22---homing-cycle-boolean

37

That’s the problem. As soon as I connect, the error comes shortly afterwards and it cannot be operated or moved.
Oh my god what have I done again?

38

I always have to go to ugs to unlock and after that it can be moved again.

39

Something is triggering the hard limit, which likely means that one of your homing switches (or the Z plate) is triggering when you don’t want it to, and the controller thinks that a limit has been hit. Check the wiring.

40

I checked the cables. I do not find anything.
But tomorrow I will let a friend of the electrician look over it again.
Here again a new error message.
Maybe you will recognize the mistake in it.
I have also read something on the Internet that there may be electrical faults in the cable and therefore the Arduino gives the error.
Does anyone know that?

**** Connected to COM3 @ 115200 baud ****
Grbl 1.1h [‘$’ for help]

$$
[MSG: ‘$ H’ | ‘$ X’ to unlock]
$ 0 = 10 (step pulse time, microseconds)
$ 1 = 255 (Step idle delay, milliseconds)
$ 2 = 0 (step pulse invert, mask)
$ 3 = 3 (Step direction invert, mask)
$ 4 = 0 (Invert step enable pin, boolean)
$ 5 = 1 (Invert limit pins, boolean)
$ 6 = 0 (invert probe pin, boolean)
$ 10 = 115 (Status report options, mask)
$ 11 = 0.020 (junction deviation, millimeters)
$ 12 = 0.002 (Arc tolerance, millimeters)
$ 13 = 0 (report in inches, boolean)
$ 20 = 0 (soft limits enable, boolean)
$ 21 = 0 (hard limits enable, boolean)
$ 22 = 1 (homing cycle enable, boolean)
$ 23 = 3 (homing direction invert, mask)
$ 24 = 25,000 (homing locate feed rate, mm / min)
$ 25 = 200,000 (homing search seek rate, mm / min)
$ 26 = 10 (homing switch debounce delay, milliseconds)
$ 27 = 1,000 (Homing switch pull-off distance, millimeters)
$ 30 = 255 (Maximum spindle speed, RPM)
$ 31 = 0 (minimum spindle speed, RPM)
$ 32 = 1 (laser mode enable, boolean)
$ 100 = 40,000 (X-axis travel resolution, step / mm)
$ 101 = 40,000 (Y-axis travel resolution, step / mm)
$ 102 = 188,976 (Z-axis travel resolution, step / mm)
$ 110 = 8000,000 (X-axis maximum rate, mm / min)
$ 111 = 8,000,000 (Y-axis maximum rate, mm / min)
$ 112 = 500,000 (Z-axis maximum rate, mm / min)
$ 120 = 500,000 (X-axis acceleration, mm / sec ^ 2)
$ 121 = 500,000 (Y-axis acceleration, mm / sec ^ 2)
$ 122 = 50,000 (Z-axis acceleration, mm / sec ^ 2)
$ 130 = 790,000 (X-axis maximum travel, millimeters)
$ 131 = 790,000 (Y-axis maximum travel, millimeters)
$ 132 = 100,000 (Z-axis maximum travel, millimeters)
OK
$ G
[detailed] GrblFeedbackMessage {message = ‘[GC: G0 G54 G17 G21 G90 G94 M5 M9 T0 F0 S0]’, distanceMode = ‘G90’, units = ‘G21’}
[GC: G0 G54 G17 G21 G90 G94 M5 M9 T0 F0 S0]
OK
[detailed] <Alarm | MPos: 0.000,0.000,0.000 | Bf: 15.128 | FS: 0.0 | Pn: X | WCO: 0.000.0.000, -58.765>
[detailed] <Alarm | MPos: 0,000,0,000,0,000 | Bf: 15,128 | FS: 0.0 | Pn: X | Ov: 100,100,100>
[detailed] <Alarm | MPos: 0.000,0.000,0.000 | Bf: 15.128 | FS: 0.0 | Pn: X>
[detailed] <Alarm | MPos: 0.000,0.000,0.000 | Bf: 15.128 | FS: 0.0 | Pn: X>
[detailed] <Alarm | MPos: 0.000,0.000,0.000 | Bf: 15.128 | FS: 0.0>

41

I think I found the bug.
$ 22 stood at 1 for homing.
I have not yet set or done that.
Now there is no more error message. In between I even disconnected the limit switches.
And yet the mistake came.
I would have to deal with that tomorrow.
Then tomorrow I’ll see if I can find a simple explanation somewhere (preferably in my mother tongue German), which describes how to set up or do a reference run on an X-Carve.
Or how it works at all.

I thank you very, very, very, very much Oz for your excellent help.

Greetings from Germany Andre ’

42

That’s saying the X pin is triggered, so that’s the one to look at.

43

Small update.
Today I exchanged all cables that go to the limit switches.
Limit switch with the multimeter checks whether they are all connected the same way.
Have you been.
Then a new attempt with reference travel.
And…
Nothing worked.
The limit switches did not trip.
Then I removed all cables from the limit switches and triggered them manually during the reference run.
And now it’s getting weird.
X axis cables were together and triggered when I separated them.
Z axis were disconnected and triggered when they touched.
Y axis did not respond at all. (Not when closed or open).
All solder joints on the Gshield v5b were also checked and switched through.
All connections checked again at github.

I just wanted to finally completely upgrade my X-carve.
But what does my friend Charles always say “don’t change a running system”.

What I am particularly pleased about is the forum here and your help.
Here you describe your problem and there is always someone to help you.
THANKS FOR THAT. :smiley::+1:

I posted the same problems in the Inventables Forum (where I bought the X-carve), but unfortunately there is none there that responds to my problems. I find that very sad and not exactly customer-oriented. :-1: :Denken:

Greetings Andre ’

44

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.