Share

Enhanced Machine Controller

Show:

What's happening?

  • Comment: wrong speed limit in "test axis" dialog

    I think this is better: 1980,1983c1980 < if data.doublestep(): < period = int(1e9 / maxvel / scale) < else: < period = int(0.5e9 / maxvel / scale) --- > period = int(1e9 / maxvel / scale) 1992,1995c1989 < if data.doublestep(): < maxvel = 1e9 / minperiod / abs(scale) < else: < maxvel = 0.5e9 /...

    2010-01-01 11:13:12 UTC by https://www.google.com/accounts

  • Comment: wrong BASE_PERIOD in "test axis" dialog

    I think I found the complete solution for this and the previous item: 1980,1983c1980 < if data.doublestep(): < period = int(1e9 / maxvel / scale) < else: < period = int(0.5e9 / maxvel / scale) --- > period = int(1e9 / maxvel / scale) 1992,1995c1989 < if data.doublestep(): < maxvel = 1e9 / minperiod / abs(scale)

    2010-01-01 11:10:59 UTC by https://www.google.com/accounts

  • Comment: wrong BASE_PERIOD in "test axis" dialog

    shall be in Category Stepconf.

    2009-12-31 14:23:49 UTC by nobody

  • wrong BASE_PERIOD in "test axis" dialog

    If step lenght > 5.000, I found a wrong timing of the base_thread. e.g. step len = 20.000, jitter = 20000 results in min base_period = 40.000, max freq = 12.500 Hz displayed on the first page of Stepconf. This is correct. But when I do the "test axis" dialog and measure the pulses with a scope, the base_period is approx. 53.000. The base_period performes well, when steplen

    2009-12-31 14:20:58 UTC by nobody

  • wrong speed limit in "test axis" dialog

    If step puls lenght > 5000, the limit for the axis velocity is not correct in the axis test dialog. I found an easy fix like this: 1989c1989,1992 < maxvel = 1e9 / minperiod / abs(scale) --- > if data.doublestep(): > maxvel = 1e9 / minperiod / abs(scale) > else: > maxvel = 0.5e9 / minperiod / abs(scale) Not sure of...

    2009-12-31 13:55:03 UTC by nobody

  • Comment: path control settings not restored after error

    fixed in master r74ce25ac44.

    2009-12-30 14:24:37 UTC by micges

  • Comment: metric jog increments on mini GUI

    I don't fully understand this bug report. Can you write step by step list to reproduce this problem and what is happening and what is to expected to happen(show).

    2009-12-28 20:11:32 UTC by micges

  • metric jog increments on mini GUI

    Hello My name is Michael I work for Sherline. I have noticed that in the mini GUI when opening it in imperial mode the manual jog increment presets are the still in metric, I have been able to get them to come through as imperial but only for a short period then they are metric again. I am looking in the source code to try to repair this but I am fairly new to EMC. Thank you for your time.

    2009-12-22 23:14:43 UTC by nobody

  • Timeout didn't reset between two M66 lines

    master, sim_mm.ini F1 F2 home all load attached gcode, open machine->emctop run gocde file open terminal and type: halcmd setp motion.digital-in-00 1 behavour expected: program shoud finish behaviour actual: even if second M66 is immediate type(no timeout) emc task will wait on it with timeout from first M66.

    2009-12-17 23:50:37 UTC by micges

  • Comment: Magic numbers don't match defines

    fixed in master, commit 9694e893dc.

    2009-11-21 00:04:53 UTC by micges