On Fri, 1 May 2020 at 00:28, Leonardo Marsaglia wrote:
> Now I only need to
> filter the encoder from the spindle to get rid of that noisy output wich is
> not hurting anything but it would look better filtered.
It's fine to have a filtered version for GUI display, but probably
best to use the r
You're welcome! :)
El jue., 30 abr. 2020 a las 22:19, Gene Heskett ()
escribió:
> 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
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
> *spindle.M.speed−out
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
are
>
> 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 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 I
>
> 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:
>
> https://git
>
> 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.
> Bu
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:
https://github.
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 m
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 f
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
for
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 I
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 (<
ldmarsag...@gmail
>
> 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've
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 I
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 spin
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 sp
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
t
>
> 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 som
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 tr
>
> 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 ()
escribió:
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 acc
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 I
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 rpm
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 o
Hello Gene,
I'm using a step generator from the 7i52 to feed the pulse command input on
the Yaskawa v1000. So I have to play with the scale factor to modify the
frequency. The driver accepts a maximum frequency of 32 khz and it has a
max freq setting inside that range to set up the maximum velocit
On Wednesday 29 April 2020 19:02:17 Leonardo Marsaglia wrote:
> It's me again,
>
> We managed to get the spindle VFD working with pulse input command.
> The problem is, I can't get to work the G96 code or the feed override
> on axis. I'm able to set different speeds via MDI and it responds well
>
It's me again,
We managed to get the spindle VFD working with pulse input command. The
problem is, I can't get to work the G96 code or the feed override on axis.
I'm able to set different speeds via MDI and it responds well but that's
all. The feed override slider is behaving like a on/off switch
29 matches
Mail list logo
