Just to be super clear. I'm sending the spindle speed cmd velocity to a
step generator in velocity mode. Could this be the source of the problem?
Or does LCNC internally set the speed of the spindle based on the X
diameter?
El jue., 30 abr. 2020 a las 12:57, Leonardo Marsaglia (<
On Fri, 10 Apr 2020 01:05:03 +0100
andy pugh wrote:
> On Fri, 10 Apr 2020 at 00:58, Todd Zuercher wrote:
> >
> > I've liked the cables I've gotten from Igus.
> > https://www.igus.com/product/1074
>
> This looks good for a dedicated encoder cable:
> https://www.igus.com/product/1117
Without
On Thu, 30 Apr 2020 at 16:59, Leonardo Marsaglia
wrote:
>
> What I would like to know is. Does G96 only work when lathe mode is on?
>
Possibly, though I would be surprised as LATHE is an INI entry in the
[DISPLAY] section.
> Does it automatically recognise the X axis? Because I don't know if
On Thursday 30 April 2020 12:36:00 Leonardo Marsaglia wrote:
> Just to be super clear. I'm sending the spindle speed cmd velocity to
> a step generator in velocity mode. Could this be the source of the
> problem? Or does LCNC internally set the speed of the spindle based on
> the X diameter?
>
I
On Thu, 30 Apr 2020 at 18:00, Leonardo Marsaglia
wrote:
*and it works perfectly. But that makes me question the naming on these
> pins. Aren't all the CMD tagged pins supposed to be used to feed PWM,
> Stepgens, etc?
>
The docs are no help either, but there is a clue in the code:
> With the pitch of the
> ballscrew at 3mm just how does one get the fine step size back .
With a timing belt reduction system. Timing belts have zero-backlash and
can increase torque and precision. They also can absorb tiny amounts of
misaignment between the motor and the lead screw like a
On Thu, 30 Apr 2020 at 17:38, Leonardo Marsaglia
wrote:
> Just to be super clear. I'm sending the spindle speed cmd velocity to a
> step generator in velocity mode. Could this be the source of the problem?
No.
--
atp
"A motorcycle is a bicycle with a pandemonium attachment and is designed
Solved!
I was using *spindle.M.speed−cmd−rps *to drive my stepgen and VFD and this
pin sets to the maximum speed when in G96. I'm now using
*spindle.M.speed−out−rps
*and it works perfectly. But that makes me question the naming on these
pins. Aren't all the CMD tagged pins supposed to be used to
Voltage drop? @26AWG has 0.134 ohms per meter.It might matter if you
are running 20 meters of cable. As for connectors those "aviation plugs"
are good quality and not expensive. They come in 12mm and 16mm diameters
(or more accurately with M12 and M16 threads)I've been using M16 for
On Thursday 30 April 2020 19:25:16 Leonardo Marsaglia wrote:
> > However if that Yaskawa actually is counting steps, something I've
> > never ever seen one of the clones I am using do, then you are
> > probably just sending too many steps/second. I could be wrong, as
> > its not impossible, but
>
> However if that Yaskawa actually is counting steps, something I've never
> ever seen one of the clones I am using do, then you are probably just
> sending too many steps/second. I could be wrong, as its not impossible,
> but I'm thinking you may have miss-read the Chinglesh in the manual.
>
>
> The docs are no help either, but there is a clue in the code:
>
> https://github.com/LinuxCNC/linuxcnc/blob/master/src/emc/motion/mot_priv.h#L57
>
>
> I would expect that this will always show the D number in G96 mode.
> (As you found)
>
> And this commit explains why it exists:
>
>
On Thursday 30 April 2020 15:36:05 Chris Albertson wrote:
> Voltage drop? @26AWG has 0.134 ohms per meter.It might matter if
> you are running 20 meters of cable. As for connectors those
> "aviation plugs" are good quality and not expensive. They come in
> 12mm and 16mm diameters (or
Yes, they are not actually made for use on aircraft but they are of that
style. Even the way-cheap versions are very reliable and easy to use.
If driving a motor you really must do the math and compute the voltage drop
and keep it to maybe less than 2%. Twisted pairs really do help. I think
On Thu, Apr 30, 2020 at 7:42 PM Gene Heskett wrote:
> My fav cable for motors where 4 wire is sufficient is
> star-quad, the worlds best shielded microphone cable, shielding is
> around 120 db! 4 wires in a twist pattern that for mikes, balances out
> any noise, plus a mylar shield with a 68%
On Thursday 30 April 2020 20:35:55 Leonardo Marsaglia wrote:
> > Great, but from what to what, so the fix becomes part of the list
> > archive?
>
> I started using *spindle.M.speed−cmd−rps *and it worked ok until I
> tried G96. Three hours later I found that I needed to use
>
By the way, now that I have a really complex machine I can notice lots of
things I didn't notice/learned before. So if I can help to improve the
manuals I'm more than ok with that. At least, it's a good starting point to
give something back to this awesome community. But I really don't know how
On Thursday 30 April 2020 21:40:59 Przemek Klosowski wrote:
> On Thu, Apr 30, 2020 at 7:42 PM Gene Heskett
wrote:
> > My fav cable for motors where 4 wire is sufficient is
> > star-quad, the worlds best shielded microphone cable, shielding is
> > around 120 db! 4 wires in a twist pattern that
>
> Great, but from what to what, so the fix becomes part of the list
> archive?
I started using *spindle.M.speed−cmd−rps *and it worked ok until I tried
G96. Three hours later I found that I needed to use
*spindle.M.speed−out−rps*.
I don't know if this should be fixed because it's meant to be
On Thu, 30 Apr 2020 at 15:23, Leonardo Marsaglia
wrote:
>
> G96 is reading the speed well because the feed appears noisy on screen. And
> also If I set different max RPMs I get different feeds. The problem here is
> that, whatever I do, I'm always clipping to max rpm.
Is the X axis position
The fact that the spindle override slider isn't working as expected - makes
me think of some sort of basic configuration error..
sam
On Thu, Apr 30, 2020 at 10:30 AM andy pugh wrote:
> On Thu, 30 Apr 2020 at 15:52, Leonardo Marsaglia
> wrote:
>
> Working in G54 with the tool selected and G43
>
> Is the X axis position accurate (and positive?)
Hello Andy,
Working in G54 with the tool selected and G43 I get positive diameter. The
only negative values are in machine coordinates but G96 it's not supossed
to use that value right?
El jue., 30 abr. 2020 a las 11:38, andy pugh ()
Well I just corrected my scale and activate the encoder filter and now I'm
pretty much spinning the spindle at the rpms it's asked to.
The problem is still my g96 code. When the program tries that command with
a 700 rpm limit, the lathe starts to spin to that maximum speed no matter
the position
>
> What does the program actually say for the SxxxM3 line? As Andy asked,
> Is the X positive?
>
Hello Ed,
One of the lines for example is G96 D600 S40 M4. The X is always positive.
El jue., 30 abr. 2020 a las 12:19, Ed () escribió:
> On 4/30/20 9:20 AM, Leonardo Marsaglia wrote:
> > After
On 4/30/20 9:20 AM, Leonardo Marsaglia wrote:
After some testing this is what happens:
G96 is reading the speed well because the feed appears noisy on screen. And
also If I set different max RPMs I get different feeds. The problem here is
that, whatever I do, I'm always clipping to max rpm. I
After some testing this is what happens:
G96 is reading the speed well because the feed appears noisy on screen. And
also If I set different max RPMs I get different feeds. The problem here is
that, whatever I do, I'm always clipping to max rpm. I tried to set the S
value really low like 0.5 and
If I set the spindle to G97 to work in RPM mode the
spindle.0.speed.cmd-rps works as expected.
El jue., 30 abr. 2020 a las 12:26, Leonardo Marsaglia (<
ldmarsag...@gmail.com>) escribió:
> I'm running the Axis simulated lathe and I encounter the same problem but
> take a look at this video. The
On Thu, 30 Apr 2020 at 15:52, Leonardo Marsaglia
wrote:
Working in G54 with the tool selected and G43 I get positive diameter. The
> only negative values are in machine coordinates but G96 it's not supossed
> to use that value right?
No. And despite what the docs say I don't think G96 uses
I forgot to tell you that I'm driving the spindle open loop yet. But again
I don't think that could be the problem.
El jue., 30 abr. 2020 10:03, Leonardo Marsaglia
escribió:
> Well I just corrected my scale and activate the encoder filter and now I'm
> pretty much spinning the spindle at the
>
> Is the X axis (hal pin) position correct and in the machine base units?
Here's a picture https://imgur.com/uFjq7s0 (doesn't read to well but I
think it's fine to understand the numbers) that may answer this. I'm
getting negative values on those pins depending on my offsets but from what
I'm running the Axis simulated lathe and I encounter the same problem but
take a look at this video. The spindle.0.speed.cmd-rps is cliped to the
max speed here too. But the pyVCP is showing the spindle increase in RPM as
the diameter gets smaller. I'm using G96 and jogging the X axis by hand by
On 30/04/2020 05:45, Przemek Klosowski wrote:
On Wed, Apr 29, 2020 at 5:05 AM Lester Caine wrote:
For the observant ... what is wrong with the front and back image of the
BPI-F2S ...
OK I give up---what's wrong? I assume you're talking about
On 29/04/2020 17:48, John Dammeyer wrote:
Yes. Up until recently micro-stepper drives ran 10:1 but now they can do 256:1
although the jury is out on whether anything past 10:1 is useful. But that's a
different discussion.
The drivers I use have always had 128:1 but I've never found anything
33 matches
Mail list logo
