Just an idea for a more flexible extension.
[SomwareInTheINI]
[RS274NGC]
USER_PARAM_5021 = name_of_realtime_component
name_of_realtime_component has to calculate that value, and then its
avaiable in as #5021 in the interpreter.
I don´t know for sure if every value for abs position is avaiable in the
RT-Components. But i think would be a great way to add more of such
values in a flexible way without changes in source-code. Just like
HAL-RT-componets.
With such a solution some of my huge/complicated macros would be very
much handier. Additionally it would be possible to get better debugging
by writing out some values into HAL and monitor them with halscope for
example.
And, by this way it would be possible to write out values to hal
in a easier way. (Do i correctly remember its not possible by default
and we have to use M-Codes?)
Don´t know anything about how much code must be changed in the
"untouchable interpreter code" and about side effects, but as more as i
think about this extension as more ideas i get how many things could be
made easier with that.
Greets from Bavaria
Freisei
(Sorry for the topic-change, but i could no more read such a bad subject)
Am 27.07.2021 um 14:19 schrieb Feral Engineer:
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
controls constantly and see a lot of missing features in the o code stuff
that I would be more than happy to address myself if I could ever get to
that level in CPP.
Not sure how familiar you all are with the aforementioned controls, but I'd
be happy to provide manuals for the logic sections of all 3 so you could
see what each one is about. Fanuc and Mits are like 99% identical, but
Siemens is completely different and way more powerful. Some examples would
be that control has both WHILE and FOR loops, 3 dimensional data arrays,
unlimited nonvolatile variable assignment via GUD tables and four different
methods of GOTO.
Phil T.
The Feral Engineer
Check out my LinuxCNC tutorials, machine builds and other antics at
www.youtube.com/c/theferalengineer
Help support my channel efforts and coffee addiction:
www.patreon.com/theferalengineer
On Tue, Jul 27, 2021, 6:17 AM andy pugh wrote:
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 my very first questions on the IRC when I
first started with LinuxCNC. I can't remember why I wanted current abs
position, but I did, and ended up using the G28.1 inelegant
workaround.
(It is inelegant because it has side-effects)
--
atp
"A motorcycle is a bicycle with a pandemonium attachment and is
designed for the especial use of mechanical geniuses, daredevils and
lunatics."
— George Fitch, Atlanta Constitution Newspaper, 1912
___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers
___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers
___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers
