Thanks for seeing the potential Gene.
You are lucky its morning there. 7:30 pm here. I've been up since 4:00 cos
I've been working with a US associate. I said good night to him about
lunch time so its been a long day and my imagination is really worn out
about now.!
Rod Webster
*1300 896 832*
On Saturday 16 May 2020 03:47:20 Rod Webster wrote:
> Gene, thanks, I've played around with motion_type like that for
> various things too.
>
> Reinhard,
> I'm not interested in a UI running in user space here at all. State
> tags is in the real time code section of Linuxcnc but I don't see its
Gene, thanks, I've played around with motion_type like that for various
things too.
Reinhard,
I'm not interested in a UI running in user space here at all. State tags
is in the real time code section of Linuxcnc but I don't see its available
via any pins. The state tags structure is contained
On Saturday 16 May 2020 02:01:41 Rod Webster wrote:
> Now we have both State tags and the hal_port pin type in master
> branch, it occurred to me that it might be possible to publish the
> state tags structure to a hal_port pin and a component could check
> motion.motion_type or the tag type to
Hi Rod,
On Samstag, 16. Mai 2020, 08:01:41 CEST Rod Webster wrote:
> Now we have both State tags and the hal_port pin type in master branch,
>...
>, it would allow easy access to the state tags from a custom component
> instead of letting state tags sulk in the EMC folder.
don't know, if I got
Now we have both State tags and the hal_port pin type in master branch,
it occurred to me that it might be possible to publish the state tags
structure to a hal_port pin and a component could check motion.motion_type
or the tag type to determine the data contained in hal_port.
A cursory read
