I will be happy to do that. Did you notice any other discrepancies with the
man page. It was a shot from the hip in a way since I am trying to learn and
document at the same time. :-)
Joe
- On Apr 6, 2017, at 11:33 AM, Sebastian Kuzminsky s...@highlab.com wrote:
> On Thu, Apr 06, 2017
On Thu, Apr 06, 2017 at 11:25:06AM -0500, Joe Hildreth wrote:
> I probably should correct that and resubmit it, yes? Thanks for
> reading it, hind-sight being 20/20 and all, I probably should have
> asked you to look it over before submitting it.
No problem. It's already a solid step forward,
I probably should correct that and resubmit it, yes? Thanks for reading it,
hind-sight being 20/20 and all, I probably should have asked you to look it
over before submitting it.
Joe
- On Apr 6, 2017, at 11:12 AM, Sebastian Kuzminsky s...@highlab.com wrote:
> On Thu, Apr 06, 2017 at
On Thu, Apr 06, 2017 at 10:46:56AM -0500, Joe Hildreth wrote:
> Well, what a learning experience that was. Have the manpage written,
> forked the linuxcnc project, added my page, committed and signed,
> and done a pull request. (With some help from some folks on the devel
> IRC channel). At any
Sebastian,
Well, what a learning experience that was. Have the manpage written, forked
the linuxcnc project, added my page, committed and signed, and done a pull
request. (With some help from some folks on the devel IRC channel). At any
rate, it shows up in the documentation for 2.7 and
On 04/04/2017 05:54 PM, Joe Hildreth wrote:
> DOH!
>
> I guess I should have dug a little more. Thanks Andy.
>
> So would you guys still like me to tackle the man page for the component.
> Been reading up on how to construct them, and I am willing to give it a go.
It would be good to have a
DOH!
I guess I should have dug a little more. Thanks Andy.
So would you guys still like me to tackle the man page for the component. Been
reading up on how to construct them, and I am willing to give it a go.
- On Apr 4, 2017, at 6:21 PM, andy pugh bodge...@gmail.com wrote:
> On 4 April
Thanks Dewey that helped a bunch.
- On Apr 4, 2017, at 4:42 PM, Dewey Garrett dgarr...@panix.com wrote:
>> So this tells me what pins are created,
>> the only one I am unsure of is the
>> change_button, can someone explain this one?
>
> By default, one must click the 'Continue'
> button on
On 4 April 2017 at 19:56, Joe Hildreth wrote:
> I am looking through the docs and cannot find a man page for the
> hal_manualtoolchange userspace component,
It is hidden:
http://linuxcnc.org/docs/2.7/html/gui/axis.html#_manual_tool_change
--
atp
"A motorcycle is
> So this tells me what pins are created,
> the only one I am unsure of is the
> change_button, can someone explain this one?
By default, one must click the 'Continue'
button on the tool change popup gui to
acknowledge the manual tool change.
The pin 'hal_manualtoolchange.change_button'
may be
Sebastian,
I will be happy to try to write it.
Joe
- On Apr 4, 2017, at 2:34 PM, Sebastian Kuzminsky s...@highlab.com wrote:
> On 04/04/2017 01:13 PM, Joe Hildreth wrote:
>> Looking at the ha;_manualtoolchange.py file, I see the following:
>>
>> h = hal.component("hal_manualtoolchange")
>>
On 04/04/2017 01:13 PM, Joe Hildreth wrote:
> Looking at the ha;_manualtoolchange.py file, I see the following:
>
> h = hal.component("hal_manualtoolchange")
> h.newpin("number", hal.HAL_S32, hal.HAL_IN)
> h.newpin("change", hal.HAL_BIT, hal.HAL_IN)
> h.newpin("change_button", hal.HAL_BIT,
Looking at the ha;_manualtoolchange.py file, I see the following:
h = hal.component("hal_manualtoolchange")
h.newpin("number", hal.HAL_S32, hal.HAL_IN)
h.newpin("change", hal.HAL_BIT, hal.HAL_IN)
h.newpin("change_button", hal.HAL_BIT, hal.HAL_IN)
h.newpin("changed", hal.HAL_BIT, hal.HAL_OUT)
Hello all,
I am looking through the docs and cannot find a man page for the
hal_manualtoolchange userspace component, and only see reference to it in the
HAL Examples section of the doc. Also missing is the man page for the parport
rt module. Who do I need to request for these docs, or is it
14 matches
Mail list logo