Project

General

Profile

Actions

Bug #94

closed

Can't control speed anymore?

Added by peteruithoven over 10 years ago. Updated over 9 years ago.

Status:
Closed
Priority:
High
Assignee:
-
Category:
-
Target version:
-
Start date:
2013-12-19
Due date:
% Done:

0%

Estimated time:

Description

Using version master.fbcd2b0-dirty.bin we can engrave several times faster than we used to, but it seems like we can't control the speed anymore. There's no difference between a job at 100% vs. 0.01% speed

The speed ends up correctly in the simplecode. I've added the beginning of a simple engrave job below. Parameter 100 should be the speed, which is set to 1 which represents 0.01%.

201 9906
202 59816
203 505141
204 510094
7 100 1
7 101 10000
0 5841 319839

The relevant changes should be in the following commit:
84a0e03

I see for example that the xaccel is used without scaling it to a speed setting? But this isn't even specific for engraving.

plan_set_accel(cfg->xaccel);

Actions #1

Updated by peteruithoven almost 10 years ago

The following code seems relevant. But this all seems to set target speed and accelerations, I'm not sure why the given speed would be ignored in engrave mode. I also don't understand the reason for queue emptying trick.

switch ( action.ActionType )
{
    case AT_MOVE: action.target.feed_rate = 60 * cfg->speed; break;
    case AT_LASER: action.target.feed_rate = 60 * mark_speed; break;
    case AT_BITMAP: action.target.feed_rate = 60 * cfg->xspeed; break;
}

if ( action.ActionType == AT_BITMAP )
{
    while ( queue() );// printf("-"); // wait for queue to empty
    plan_set_accel(cfg->xaccel);
    plan_buffer_line(&action);
    while ( queue() ); // printf("*"); // wait for queue to empty
    plan_set_accel(cfg->accel);
}
else
{
    plan_buffer_line(&action);
}

Actions #2

Updated by peteruithoven over 9 years ago

  • Status changed from New to Closed
Actions

Also available in: Atom PDF