Sebastian, et al, The run-away problem seems to be licked, at least for relatively slow speeds. I am, however, still getting following errors at higher velocities. These start to occur at about 3IPS. The motors should max out at about 12 IPS. Max step rate on the motors should be 20 RPS * 200 steps per revolution * 16 micro-steps per step, or 64000 steps per second. At 3 IPS, it should be about 16000 steps per second.
I have base period set to 25000 nsec, and servo period set to 200000 nsec. I assume the following error results from position-fb getting too far behind position-cmd, but I do not know what needs to be done to resolve this problem. Secondly, now that I am back to it, the PWM does not seem to be changing. It is either off, or what seems to be close to full on. My meter reads either 0V or 3.16V. I did find that a mirror must have gotten bumped, resulting in apparently low output from the laser. Following a beam alignment, laser power does look to be close to full on. Any ideas on how to troubleshoot this is appreciated. Regards, Eric I modified stepgen.c, about line 103 and 104 as follows: if (s->hal.param.maxvel > fabs(max_pos_per_s) s->hal.param.maxvel = fabs(max_pos_per_s); On the development system, whch is not connected to hardware, the following error has gone away and it basically looks to be working. I can jog, for example and the values count off properly. I will move it over to the real machine and see if it works there. ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
