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 in the emcmotCommand structure created in motion.c using the structures defined in statetags.h and motion.h The hal_port is a new "string" pin available in hal. So what I propose is a "marriage" between them. Copy the statetags as an untyped "blob" in a hal_port pin so that an interested hal component could read the blob, determine how to decode it from motion_type and overlay the typed structure over the top. What I want to access is the radius of an arc so I can make adjustments to the plasma cutting process in real time. An alternative (simpler) approach would be to create a new motion pin for the arc radius, but I thought the hal_port marriage might allow anybody to access all of the state_tags data from a component. I just don't quite know where to start. But it would be a powerful enhancement to our awesome platform. Rod Webster *1300 896 832* +61 435 765 611 VMN® www.vmn.com.au On Sat, 16 May 2020 at 16:53, Reinhard <reinha...@schwarzrot-design.de> wrote: > 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 you right - to me it sounds as if you oppose the > state > tags. > > From my point of view, state tags are for communication with frontend / > UI, > whereas hal is the communication with hardware / drivers. > So state tags are far from being complete. But I don't think, that they > are > equivalent or should be. No. There might be information, that will be > important for the hardware-side and be of little interest for the frontend > side. > I think, if NML is the communication portal of linuxcnc to other software, > than an UI should not have to bother with hal. > An UI may do that to give the users another taste of UI, but tools for hal > exists and work, why reinvent the wheel? > So I appreciate state tags and would like them to become more complete to > be > able to offer all informations around machine state ... > > May be, my point of view does not reflect the state of linuxcnc. > But that's what I think and would like to become true one day :) > > > cheers Reinhard > > > > > _______________________________________________ > 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
