Transversemovements extremely slow Atomstack X40

It did work, now it has fast movement.

But I see something strange…

My test was using a few boxes at 8000 mm/min and 1% power, and the laser draw a tiny line in the wood. In the tests I did yesterday, there was no real draw (too fast and low power).

Does this have anything to do with the “variable laser power” option turned off?

It does not work, as it should.

Although it has fast speed, the values for speed / (laser) force, are wrong, and it does not burn correctly.

I made a file and export it, in the screenshot you can see it:

FILE 0: all the options disconected, as in Parsec capture.
FILE 1: the same, but “variable laser power” ON
FILE 2: the original file, the one that burn as expected but with low traverse speed.

It works.
Your code is wrong what have you changed?
Something wrong with your custom device.


Create a new Custom GCode device and try first with a simple square 10% and 50% power with units set to mm/m in your case.
Variable Laser Power dos nothing because M4 is already set.

I have not changed anything, just “export”, “change laser”, “export”

Duplicate your GRBL device and convert to Custom and test again.

I have just make a test on my home computer and the files are identical but the M4/M5, I don’t know why the one at my work is not.
I exported the laserfile from my home computer to the work one and the files look fine.
Real world tests will be done later.

1 Like

Also export the device from your home computer then import in the work one.

I mean exported the device file.

1 Like

In your GRBL-M3 Custom GCode device change the S-value max to 1000.
.
Click Create Manually, Custom GCode, Next


.
Click Serial, Next

.
Input the name and dimensions then click Next
image
.
Select the correct options for your laser and click Next
image
.
Select GRBL-M3, S-value-max=1000 TSA off, VLP off, click Next, Finnish, Ok .

.
Select your Custom GCode device

.
Click Device Settings image
.
Set Tool On to M4, click Ok.

.
Test and get back with your results.

Manually changing the s value in the text editor to 1000 in the GRBL-M3 (1.1e or earlier) code brought the desired result.

Your custom code device setting also brought the desired result.

After a short test I can also say that it was because of the tool state automatic that the movements were too slow.

And because of the s value that it didn’t cut properly.
Test Travers custom code.gc (1,2 KB)

Now you know :slight_smile:
The firmware doesn´t interpret the signal and runs G0 as G1 with 0 power.

by testing.
tool state automatic on = too slow rapid movements
tool state automatic off = fast rapid movements as it should be

without your help I would never have figured it out.
now I just have to find the time and test everything, engraving and cutting at different speeds and power.

1 Like

and the nonsense continues.
with the custom code it no longer engraves…
unless you activate tool state automatic…
and the rapid movements are slow either way…
test gravur grbl.gc (19,2 KB)
test gravur custom GCode tool state automatic on.gc (19,5 KB)
test gravur custom GCode.gc (19,5 KB)

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