Am 21.10.2009 um 07:08 schrieb Jon Elson:
Haberler Michael wrote:
Am 21.10.2009 um 02:40 schrieb Jon Elson:
Well, there's the problem, the sampling rate is just too low.
well that's what Steve said about his setup, but it's not the problem
I described
Well, that HalScope trace sure
Am 21.10.2009 um 03:04 schrieb Stephen Wille Padnos:
Haberler Michael wrote:
[snip]
here's a halscope shot of severe Z axis oscillation:
http://mah.priv.at/gallery2/main.php?g2_view=core.DownloadItemg2_itemId=70522
Could you post the config (HAL/ini) files you used to see
Am 21.10.2009 um 14:33 schrieb Haberler Michael:
ok, following up to myself once more:
- set acceleration from 300 back to 70
- changed
net spindle_rev_count encoder.1.position = motion.spindle-revs
to
net spindle_rev_count encoder.1.position-interpolated =
motion.spindle
several folks (including me) reported problems with threading - namely
oscillations of the spindle-synchronized feed (G33 and G76), mostly
with homebrew encoders. Most people looked at their encoders and
signal properties.
I've isolated the problem now with a *simulated encoder* - decoder
Am 21.10.2009 um 02:40 schrieb Jon Elson:
Steve Blackmore wrote:
..
Here, with my hardware and PC, EMC can't read pulses reliably over
about
200 rpm with a 1024 encoder, which is totally impractical.
Well, there's the problem, the sampling rate is just too low.
well that's what Steve
Am 21.10.2009 um 00:21 schrieb Steve Blackmore:
On Tue, 20 Oct 2009 23:26:27 +0200, you wrote:
several folks (including me) reported problems with threading -
namely
oscillations of the spindle-synchronized feed (G33 and G76), mostly
with homebrew encoders. Most people looked at their
Am 21.10.2009 um 01:11 schrieb Andy Pugh:
2009/10/20 Haberler Michael mai...@mah.priv.at:
I dont fully understand the trajectory planner, but my gut feeling
it's a control loop oscillation which gets excited with the encoder
quantization/noise spectrum gets too close to the loop frequency
Am 09.10.2009 um 22:34 schrieb Eric H. Johnson:
Michael,
How recently was that updated. I just did rebuilt of smp (2.3.3)
earlier
this week and have just not gotten around to posting them.
the files in http://linuxcnc.org/experimental/hardy/smp/ are all 22-
Apr-2009 if that's what
through the improved parport detection by Jeff Epler the parport_pc
module is back in the game
unfortunately parport_pc is missing from the
http://linuxcnc.org/experimental/hardy/smp/
kernels, so I'm rolling my own as per
hhttp://wiki.linuxcnc.org/cgi-bin/emcinfo.pl?EMC_With_Custom_Kernel
how would I go about coding the equivalent of
halcmd getp halpin
in a Python script?
I'm writing a user-defined Mxxx code script in Python. It's started by
halui.mdi-command and should access a value from a Pyvcp widget.
thanks in advance,
-Michael
how would I go about to display fixed components in the backplot (e.g
the chuck footprint, the spindle axis or the footprint of a tool
height sensor for a mill)?
a suggestion (for lathe mode): how about indicating wether radius or
diameter mode is in effect by either displaying an icon
bear with me through my learning curve.. I'm using self-built trunk
via git on hardy.
1. my lathe has limit switches just outside the softlimit. Homing
works fine. Also, if I jog a joint
to its limit, jogging stops at the soft limit and wont bump into
the limit switch, which makes me
a while ago I described how I added a simple optical encoder wheel to
my lathe. Meanwhile, I eventually got it to work with G33 threading,
but it wasnt as straightforward as I would have believed, so I thought
I'd describe my experience.
My first attempt was to use the encoder component as
after spending disordinate amounts of time I'd warn folks to use Sunix
chipset parallel port cards
I have several Sunix 4008T parallel pci cards (distributed by Digitus)
which show the same symptom: one cannot reliably set 'in' mode for
pins 02-09. They seem to work ok in default (out)
it seems the PDF linked from the Wiki
http://www.linuxcnc.org/docs/devel/EMC2_Developer_Manual.pdf
ist broken
-Michael
--
___
Emc-users mailing list
I've finished a first release of a HAL userspace component to drive a
Toshiba VF-S11 VFD via Modbus, vfs11_vfd. It's adapted from gs2_vfd.c
and works fine for me so far. A description how to connect the VFD and
set initial parameters is included.
I would assume that folks with other
ok, along my quest towards VFD control via Modbus I didnt find an
appropriate command line utility to talk to Modbus, so I wrote one.
It helped me de-mystifying how to work with the Toshiba VF-S11;
results, VFD setup instructions and sample control files are included.
I think now I'll
just in case anybody has a Toshiba VFD and wants to play with Modbus -
here's a working adapter. It's *almost* standard TTL RS232.
Schematic: http://static.mah.priv.at/cnc/vfs11-rs232.pdf
The circuit is based on recommendations by Toshiba support (who were
very friendly, helpful and
my lathe was lacking a spindle index sensor and quadrature encoder, so
I built one as follows:
The code rings are printed on plain paper with an inkjet printer, and
laminated into a plastic pouch; then cut with a scissor and glued
to the spindle pulley (with some pressure so as to get a
Am 30.06.2009 um 17:09 schrieb Andy Pugh:
2009/6/30 Haberler Michael mai...@mah.priv.at:
The code rings are printed on plain paper with an inkjet printer, and
laminated into a plastic pouch
Interesting. When I tried a similar approach using clear tape I found
that the reflectivity
Am 02.06.2009 um 21:23 schrieb Kirk Wallace:
. I haven't found the specs for the PWM
feature yet. Can I assume that I can get above 20kHz? The rest of the
features will be fluff.
Yes you can.
Assuming you have a say, 12Mhz crystal, and do not prescale the clock,
an 8bit PWM would run at
Hi
I have two VFD's (a pDrive MX eco and a Toshiba VF-S11) both of which
are Modbus-capable and I'd like to integrate into Emc. I've read the
GS2 VFD driver, and adapting this good example would be an option. It
seems Modbus integration comes up frequently though.
I'd be curious what
22 matches
Mail list logo
