Re: [CAD_CAM_EDM_DRO] Re: 2 Axis Motion at Last, P machine INI FILE !!! HELP!!!

With your MAX_VELOCITY set at 12, there is little pospect of you getting more
than 28ipm. This can be calculated quite simply by:-

12*60/25.4 = 28.347 ipm - Or:-

[AXIS_n}MAX_VELOCITY * 60 Sec = Units per Min

As you are using metric, and looking to acheive 2500mm per min (from an
earlier email), you would need to set MAX_VELOCITY=42

Changing the PERIOD will have little effect on the maximum speed you can
acheive. Using your sample ini file on an 800Mhz machine, I was able to go
down to PERIOD=0.000008, but screen updates suffered - I normally run at
0.000016.
Despite having a faster processor, I would get a following error on longish
rapids - Reducing the MAX_VELOCITY to 9 on each axis finally allowed me to do
rapids without triggering any errors.

Assuming you are using 200 step per rev motors, your INPUT and OUTPUT scales
are also incorrect. With a half step drive and a 5mm pitch lead screw, you
would need 400/5 steps per mm, or SCALE = 80.

After running several simulations on this machine, the best settings I
acheived with freqmod was :-

PERIOD = 0.000014

[AXIS_0]
MAX_VELOCITY = 10
INPUT_SCALE = 80 0
OUTPUT_SCALE = 80 0

This is on a Duron 800Mz running the current CVS version of EMC with linux
2.4.16 and rtai. Odd though - Using an ini file set up for imperial units, I
can get 180 ipm or 4500 mm per min in simulations, and changing yours, I get
600ipm.

Conclusion - Set your ini file up as if it were an imperail machine, and
force EMC to start up displaying mm and G21 active by default.

Regards, Paul.

P.S. If you need it, I can send you the ini file I used.

On Friday 05 April 2002 11:44, ajv2803959 wrote:
> Yesterday night, I was trying set period parameter in increments from
> 0.000020 until 0.000016
> OK in 0.000020 interfaz and mouse run slowly but velocity don´t
> improve.
> In 0.000016 velocity don´t improve
> In 0.000017 and 0.00016 system crash or reboot in Pentium 233 and
> velocity don´t improve in Pentium 333