From: Michael H. <ma...@ma...> - 2013-05-31 10:30:14
|
Am 31.05.2013 um 12:07 schrieb andy pugh <bod...@gm...>: > On 24 May 2013 16:43, Sebastian Kuzminsky <se...@hi...> wrote: > >> One thing i'd like to do at the hackfest is talk about what features people want in 2.6, > > One thing that I am finding really handy is the ability to read HAL > and INI from G-code. > If you set the correct feature mask then you can use > > G1 X#<_hal[pyvcp.random-control]> for example. > > I don't actually know what the logic is behind making this feature > maskable, what is the hidden disadvantage of it? The reason for it to be masked at the time was: This is executed at readahead time, so was usable only for very limited scenarios; and it is not motion-synced like the M6x operations however, meanwhile it occurred to me one could make it a queuebuster like the M6x codes, and then it should be fine as a start, use this: http://preview.tinyurl.com/mjpmuoz and execute it before accessing the hal pin this should reflect the current machine state value in the pin (btw this 'G103 Lookahead Mode' code shouldnt be a remapped code to start with - readahead control is something very fundamental and better be a builtin) - Michael > > -- > atp > If you can't fix it, you don't own it. > http://www.ifixit.com/Manifesto > > ------------------------------------------------------------------------------ > Get 100% visibility into Java/.NET code with AppDynamics Lite > It's a free troubleshooting tool designed for production > Get down to code-level detail for bottlenecks, with <2% overhead. > Download for free and get started troubleshooting in minutes. > http://p.sf.net/sfu/appdyn_d2d_ap2 > _______________________________________________ > Emc-developers mailing list > Emc...@li... > https://lists.sourceforge.net/lists/listinfo/emc-developers |