On Wednesday 02 June 2021 01:32:24 Chris Morley wrote: > I've considerable experience in screen building and a bit using remap. > I've fairly often came to the problem of needing information from the > remap (or linuxcnc proper) presented to the screen. By design linuxcnc > has status messages that are usually used for this but it is difficult > to extend. On a recent fanuc style lathe tool remap, I wanted the wear > offset number displayed on the screen. Parameters work well for > passing information internally, accessible in gcode and can be stored > at shutdown. But they are not accessible in screen user code. > I got around this by building a HAL component in the remap to copy a > parameter to a HAL pin. HAL is accessible everywhere and is easily > extendable. > > Then it occurred to me - why couldn't all parameter data be held in a > HAL comp? Can anyone else think of a reason it couldn't or shouldn't ? > > Chris > Sounds useful Chris. If it can be done with an update speed that would prevent the use of stale data. Say like I do for manual controls on the sheldon lathe. My dials are 100 ppr dials, and making all that stuff run at servo-thread rate makes no sense so those controls are in a seperate 200 hz thread. That worked flawlessly on a pi3, and still do now with a pi4, probably would not be needed. The pi4 can run the lathe while I'm browsing the web with firefox. On the same pi4.
Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene> _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
