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

Allow faster bitmap moves #14

Open
pbrier opened this Issue Oct 27, 2013 · 10 comments

Comments

Projects
None yet
2 participants
@pbrier
Copy link
Member

pbrier commented Oct 27, 2013

Bitmap marking moves may be faster than the normal engraving moves,
as usually only one axis is involved, and this axis is faster than the other axis.

Now the speed is calculated relative to the axis speed (xspeed) instead of speed.
The axis speed configuration parameter (x.speed) can be set higher in the config file than the general speed parameter (motion.speed).

@ghost ghost assigned pbrier Oct 27, 2013

pbrier added a commit that referenced this issue Oct 27, 2013

Issue #14: Faster raster scanning. Now speed and accel is taken from …
…x axis, and not global. Set x.speed and x.accel in config file to configure right values
@pbrier

This comment has been minimized.

Copy link
Member

pbrier commented Oct 27, 2013

@pbrier pbrier closed this Oct 27, 2013

@pbrier pbrier reopened this Oct 27, 2013

@pbrier

This comment has been minimized.

Copy link
Member

pbrier commented Oct 27, 2013

make sure you add x.speed and x.accel in your config file, and set them to sane values.

x.accel: typical 1000 to 10000 mm/sec2, (lower if it skips steps)
x.speed: typical 100 to 1000 mm/sec (lower if it skips steps, or quality is bad)

@peteruithoven

This comment has been minimized.

Copy link
Contributor

peteruithoven commented Oct 27, 2013

Great work! I'll test it soon.
Is this version build with the new compilation method and new libraries? In other words, should I also briefly debug the whole system?

@pbrier

This comment has been minimized.

Copy link
Member

pbrier commented Oct 27, 2013

No currently the GCC4MBED route is still used.
There are some issues when using the latest mbed libraries.
Please use the GCC4MBED route, with the referenced MBED library revision when compiling.

@peteruithoven

This comment has been minimized.

Copy link
Contributor

peteruithoven commented Oct 29, 2013

It looks like I was able to independently increase the speed for engraving. But it looks like our small lasercutter just won't get very fast so it's hard to know for sure. When the bigger lasercutter is free I'll try it on that one. No big issues though.

@peteruithoven

This comment has been minimized.

Copy link
Contributor

peteruithoven commented Oct 29, 2013

Seems to work nicely!
I engraved the following image in 1min and 9 sec.
200 dpi
5x5 cm
with:

x.speed 1000 
x.accel 10000 

img_0127

The movement is a bit weird, some horizontal movements go quicker than others...

Fablab Amersfoort is grateful

@peteruithoven

This comment has been minimized.

Copy link
Contributor

peteruithoven commented Oct 29, 2013

In the end I used:

x.speed 1500
x.accel 12000

But again, there is something strange happening during acceleration or deceleration. Using the closed source contoller it moves a bit more consistent.

@pbrier

This comment has been minimized.

Copy link
Member

pbrier commented Oct 31, 2013

Describe "strange"
Does it jerk during moves, or just waits between some moves?

@peteruithoven

This comment has been minimized.

Copy link
Contributor

peteruithoven commented Oct 31, 2013

It moves irregular, not consistently. Some horizontal movements go slower than others.

It happened much sooner on the smaller lasercutter, maybe I'm just on the limits of what the motors can handle.

On the smaller lasercutter there sometimes was a slight deceleration 1/3 of one movement to the left.

@peteruithoven

This comment has been minimized.

Copy link
Contributor

peteruithoven commented Nov 5, 2013

Watch out with the settings. I set the speed and acceleration so high the whole lasercutter was reset because it was probably asking to much power. I noticed this while engraving wider images. So a good test is to engrave an image of 20 cm wide.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment