Bug #86
closed
Better acceleration algorithm
0%
Description
Hi guys,
I was trying to speed up our lasercutter for engraving.
Using the following settings it engraves around the same speed as the native hardhard (Morntech).
motion.speed 800
motion.accel: 12000
But with a motion.accel more than 3000 it makes a complete mess of regular cut jobs. And even at 3000 and 100% it's clearly inaccurate (it can't make straight rectangles). At motion.accel 1300 30% it can be kinda accurate. At motion.accel 1000 1% speed starts cutting trough 4mm wood etc etc.
So there is a huge difference between what's a useful for engraving and cutting.
Anyway we can greatly increase the acceleration when it's just doing straight longer lines?
I know we can't make a exception for an engraving mode, because there is no (proper) engrave mode, VisiCut sends it as a regular cut job.
Updated by jaap almost 11 years ago
- Category set to firmware
At this time, accelleration and speed settings are for X and Y axis at the same time. The X axis can move much faster then
the Y axis, so it makes sense to have motion.accel and motion.speed seperately (and even Z?). Line cutting and engraving would then still use the lowest accelleration, but raster engraving can use the higher X settings.
Updated by peteruithoven almost 11 years ago
Hi Jaap, I'm not fully following your post. You mean that acceleration and speed settings for X and Y axis are always the same? You think we should have separate motion configurations per axis?
The X axis can be faster because it's motor has to move a much smaller piece of the frame than the Y axis?
Good point, that sounds like something I might even be able to implement.
How does a separate motion configurations make sure line cutting and engraving use the lowest acceleration? Because I don't believe the hardware knows it actually engraving something.
Updated by reinoud over 10 years ago
peteruithoven wrote:
How does a separate motion configurations make sure line cutting and engraving use the lowest acceleration? Because I don't believe the hardware knows it actually engraving something.
Well, a cutting movement is always `just' a move from XY to X'Y' with the laser either on or off where as its engraving its actually generating a very fine pulse train representing the bits. Or is the engraving implemented as a heap of linear movements of say a few steps with the laser on or off?
Updated by peteruithoven over 9 years ago
- Status changed from New to Closed