On Mon, 26 Jul 2021 at 19:58, Chris Radek wrote:
> (Note I'm not saying it would be bad to add this feature)
The Fanuc numbers are in unclaimed space in the LinuxCNC parameter
range, so I think I would go further and suggest that it would be good
to add this feature.
I recall this being one of
Simply put, I don't want workarounds, I want a solution as simple as #5021
to give me the ability to track where my machine is from my home positions
without having to stand on one foot, rub my belly and hope I'm not using
coordinate rotation. I write logic in Fanuc, Mitsubishi and Siemens
I think it's brilliant
Goto (standard loop to startpoint with error)
Gotof (forward)
Gotob (backward)
Gotoc (continue looping without error)
It's not so much the fact that they have four goto, it's the fact that they
have that many ways to do it... If that makes sense. Their manuals
literally
I have added the parameters you asked for. I had the same problem when I
programmed my toolprobe macro. Will push to master shortly. According to the
fanuc docs it includes the tool offset. Does this make sense?
> On 27. Jul 2021, at 15:41, Feral Engineer wrote:
>
> I think it's brilliant
>
On 27.07.21 15:51, Feral Engineer wrote:
Send me what you have, I'll take a look. It should not include tool offsets
of any kind. 5063 (skip position) does, 5043 does (absolute position off of
current work offset) but 5023 should just be the raw machine position from
the home positions (current
An interesting set of features! However, "...and four different methods of
GOTO." doesn't sound like a feature to laud.
-Original Message-
From: Feral Engineer
Sent: July 27, 2021 8:20 AM
To: EMC developers
Subject: Re: [Emc-developers] Question for the devs
Simply put, I don't want
Send me what you have, I'll take a look. It should not include tool offsets
of any kind. 5063 (skip position) does, 5043 does (absolute position off of
current work offset) but 5023 should just be the raw machine position from
the home positions (current g53 position).
Phil T.
The Feral Engineer
On Tue, 27 Jul 2021 at 16:03, Feral Engineer wrote:
> In fact, anyone that prefers programming languages over G code would love
> Siemens high level because it's fairly close to a programming language in
> functionality. No other control I've been on let's you define string,
> integer and real
Thank you!
Send me the Fanuc document you have. I'm curious of what you saw. Machine
position never includes tool length offset, absolute position from current
work offset includes TLO, which would be the 5040 variables, not the 5020.
You guys might actually like Siemens cycle calls, they look
Andy,
Siemens high level is much like fanuc macro logic and LinuxCNC o code. It
works within a g code environment while offering more a more in depth
scripting language than fanuc macro b can offer.
A comparison would be:
fanuc:
G0 G90 G54 X#100
Siemens
G0 G90 G54 X=R0
Fanuc:
#100=0
While
Hi everyone,
Are there plans to switch the master branch to main? Just curious. I saw they
changed it for the Mesa3D git repo and that's the default now for Github.
https://cgit.freedesktop.org/mesa/mesa/
Cheers,
Alec
___
Emc-developers mailing
Not entirely true.
Inside of a main program file, I can do something like this:
G0 G90 G54 X0 Y0
G43
Z1.
#1=0
o1 while[#1LE10.]
(debug, #1)
#1=[#1+1]
o1 endwhile
m30
This all works fine and as expected as long as i preface the logic with an
o-code. This isn't a subprogram, just a main program I
On Tue, 27 Jul 2021 at 18:32, Feral Engineer
wrote:
I don't think this would require a different interpreter,
It would, because LinuxCNC sees "While" as "move the W axis to hile" and
"hile" is not a valid number...
--
atp
"A motorcycle is a bicycle with a pandemonium attachment and is
13 matches
Mail list logo
