Jon Elson wrote:
Sebastian Kuzminsky wrote:
If I disable the steppers on the 7i43 (with config=num_steppers=0) and
run it with 4 servo channels (and 24 accessible GPIOs), I get these figures:
read time=191, tmax=203
write time=190, tmax=239
That's about 1 KHz.
Very
A more elegant solution based on the same principle if you need a
continuous track would be to generate a probe hit signal when the the
current position has moved more than XX units from the previous
position. That way you don't generate uneeded points when standing
still/moving slowly and they
Emm yes and no
My cnc mount a Kress and it dont have a rapid change tool, when emc2
find M6 pause the program, i change tool, but the new tool isnt to
zero.
Whit a collet I can do the change correctly, but Im more happy if I
find an automatically zero tool procedure whit a switch/probe.
Andy,
This link shows how to connect leds to the parallel port for testing.
http://www.epanorama.net/circuits/parallel_output.html
I took a printer cable and hacked one end off and used that when I was testing
my
parallel port. Then when I got my BOB with leds from CNC4PC testing was easy.
On Wed, Aug 13, 2008 at 10:33:00AM +0200, snoopy wrote:
Whit a collet I can do the change correctly, but I?m more happy if I
find an automatically zero tool procedure whit a switch/probe.
http://cvs.linuxcnc.org/cvs/emc2/nc_files/tool-length-probe.ngc?rev=1.4
This Gcode program shows how I
Sebastian Kuzminsky wrote:
Jon Elson wrote:
Sebastian Kuzminsky wrote:
If I disable the steppers on the 7i43 (with config=num_steppers=0) and
run it with 4 servo channels (and 24 accessible GPIOs), I get these figures:
read time=191, tmax=203
write time=190, tmax=239
That's
Thanks Alex and John for the suggestions. I will pass them along! :)
Andy
John Thornton wrote:
Andy,
This link shows how to connect leds to the parallel port for testing.
http://www.epanorama.net/circuits/parallel_output.html
I took a printer cable and hacked one end off and used that
Sebastian Kuzminsky wrote:
Yeah something's not right there, 190 us is way too long.
Hm, these numbers come from 'halcmd show param hm2_7i43.*.time', which I
thought was in nanoseconds, but looking at hal_lib.c I see that it's in
CPU clock cycles. Is that intentional?
In
Hi All,
I occurred to me that all you need to do is poll your positions once a
second and then construct a G01 from that.
For the feed rate use G93 F60, inverse time, so it completes the move
in one sixtieth of a second.
I think a one second position update interval will work fine for
Jon Elson wrote:
Sebastian Kuzminsky wrote:
Yeah something's not right there, 190 us is way too long.
Hm, these numbers come from 'halcmd show param hm2_7i43.*.time', which I
thought was in nanoseconds, but looking at hal_lib.c I see that it's in
CPU clock cycles. Is that intentional?
On Wednesday 13 August 2008, John Kasunich wrote:
Unfortunately, conversion from clocks to time is non-trivial, so we
simply report the results in clocks.
(get_cycles()*10^6)/cpu_khz
Is that non-trivial ??
The situation is getting worse, not better. In the name of progress, we
now have to
On a machine that has rather different axes, with different maximum
velocities, I find it inconvenient that Axis
(as I know how to use it) seems to read only one value for
MAX_LINEAR_VELOCITY from the [TRAJ] section of the .ini file and uses
this to determine the Jog Speed range for all 3
On Thursday 14 August 2008 03:23, Kirk Wallace wrote:
snipped
Are there other CPU's that would better cater to realtime? Some sort of
lean, fast RISC, not designed to cope with Windows upgrades.
There are a bunch out there, just look at the number of archs that debian is
available for. It
Thats where I saw it! Sure it's not a fancy automated function implemented as
a feature in EMC but the variables are there to make it possible. Thanks for
the link Chris - my machine is covered with some tarps right now and the dual
boot system is in Billy Goat mode crunching away at video
Typo Alert!
I occurred to me that all you need to do is poll your positions once a
second and then construct a G01 from that.
For the feed rate use G93 F60, inverse time, so it completes the move
in one sixtieth of a second.
Edit..one sixtieth of a minute
I think a one second position
Yes i agree, that would have been ewen better as you tend to go slow in
compex mowements, but then again the track would be better when the
mowements are compex and more coarce if you are going fast straight
foreward, a solution for the standstills is too just stop the clock if
there are no
Sebastian,
I am getting close. I generated a single hal file for a two stepper and one
pwm configuration. Currently in the ini file I have it configured for only 2
axes and references only the single hal file. The error I am getting is a
following error any time I try to move an axis. I have
Eric H. Johnson wrote:
# set stepgen module accel limits - get values from ini file
# setp hm2_5i20.0.stepgen.00.maxaccel [AXIS_0]STEPGEN_MAXACCEL
# setp hm2_5i20.0.stepgen.01.maxaccel [AXIS_1]STEPGEN_MAXACCEL
# setp stepgen.2.maxaccel [AXIS_2]STEPGEN_MAXACCEL
I didn't read everything,
John,
I commented them out because it generated an error. I do not see pins for
maxaccel with hostmot2.
# set stepgen module accel limits - get values from ini file # setp
hm2_5i20.0.stepgen.00.maxaccel [AXIS_0]STEPGEN_MAXACCEL # setp
hm2_5i20.0.stepgen.01.maxaccel [AXIS_1]STEPGEN_MAXACCEL
hm I am seeing something similar with the step generator. Its feedback
position never changes. no errors in dmesg.
(jmk, there's not (yet) an enable, or velocity or accel limit
pins/parameters in hm2--I imagine that's why the lines are commented
out)
[running in an interactive halrun]
halcmd:
Kirk Wallace wrote:
On Wed, 2008-08-13 at 12:03 -0500, Jon Elson wrote:
John Kasunich wrote:
Unfortunately, conversion from clocks to time is non-trivial, so we
simply report the results in clocks. The situation is getting worse,
not better. In the name of progress, we now have to deal
Jeff Epler wrote:
hm I am seeing something similar with the step generator. Its feedback
position never changes. no errors in dmesg.
Yes, I can reproduce this here - stepgen doesnt work on the 5i20. Sorry
guys... How embarassing. :-(
My test setup consists of a PC running emc2 TRUNK. It's
Peter, could you make the stepgen Rate register read/write, so I can
read back the command for sanity checking?
I'll do that sometime tommorow...
--
Sebastian Kuzminsky
Cryogenic travel has improved since then... I woke screaming in a
translucent box. “There, there,” said the box.
Sebastian Kuzminsky wrote:
My test setup consists of a PC running emc2 TRUNK. It's got a 7i43
plugged into a parport and a 5i20 on the PCI bus. The 7i43 has two
steppers on it, and the 5i20 has 3 servos on it.
This setup conspicuously doesnt test steppers on the 5i20 or servos on
the
24 matches
Mail list logo
