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 [email protected] wrote:
> On Thu, Apr 06, 2017 a
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, an
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 [email protected] wrote:
> On Thu, Apr 06, 2017 at 10:46
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 r
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 2.8-p
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 man
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 [email protected] wrote:
> On 4 April
Thanks Dewey that helped a bunch.
- On Apr 4, 2017, at 4:42 PM, Dewey Garrett [email protected] 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 t
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 a bicycle with a pandemonium at
> 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 co
Sebastian,
I will be happy to try to write it.
Joe
- On Apr 4, 2017, at 2:34 PM, Sebastian Kuzminsky [email protected] 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, hal.HAL_
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)
h.rea
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 w
On 10 May 2014 22:30, Erik Friesen wrote:
> Where is one supposed to find information about how to use hal components?
I use this page:
http://www.linuxcnc.org/docs/html/
If you scroll down to near the bottom there is a list of all the HAL
components, and links to their manpages.
That master pa
On Sunday 11 May 2014 10:21:03 Mark Wendt did opine
And Gene did reply:
> On Sun, May 11, 2014 at 10:16 AM, Gene Heskett
wrote:
> > > Gene,
> > >
> > > We run 14.04 LTS on quite a few machines here at work (mine
> > > included). Heartbleed was fixed a few weeks ago, right after it
> > > was iden
On Sun, May 11, 2014 at 10:16 AM, Gene Heskett wrote:
>
> > Gene,
> >
> > We run 14.04 LTS on quite a few machines here at work (mine included).
> > Heartbleed was fixed a few weeks ago, right after it was identified.
> > We, at work (and me also at home) are very concerned about nasty
> > things
On Sunday 11 May 2014 10:09:41 Mark Wendt did opine
And Gene did reply:
> On Sun, May 11, 2014 at 9:59 AM, Gene Heskett wrote:
> > But I have to also agree that being stuck on 10.04.n LTS is beginning
> > to be a drag, there are later things with 14.04 LTS that we cannot
> > "backport" because sui
On Sun, May 11, 2014 at 9:59 AM, Gene Heskett wrote:
>
>
> But I have to also agree that being stuck on 10.04.n LTS is beginning to
> be a drag, there are later things with 14.04 LTS that we cannot "backport"
> because suitable libraries simply are not available for 10.04 LTS. So I
> am waiting
On Sunday 11 May 2014 08:57:00 Erik Friesen did opine
And Gene did reply:
> Yes, its one of those things. I waffled when I started this years ago
> between emc and mach3, and chose emc, still glad I did.
>
> I don't think the current state of documentation is sufficient though.
> I spent half an
Yes, its one of those things. I waffled when I started this years ago
between emc and mach3, and chose emc, still glad I did.
I don't think the current state of documentation is sufficient though. I
spent half an hour trying to find information on comp, ultimately found it
while holding my mouth
2014-05-11 5:30 GMT+03:00 Jon Elson :
> As I understand it, the first net line that creates
> a signal needs to have an output pin in the list.
>
Not necessarily. My estop loop signal is created in main hal file and has
connected only its target to it. Source is specified in second hal file.
Eri
On 05/10/2014 07:18 PM, Gene Heskett wrote:
>
> Let me correct that just a tad Jon. Those ADDITIONAL pins must be other
> module input pins. You can not wire two outputs together here, any more
> than you can in normal logic. IIRC hal will fuss about it and bail out.
>
Right. As I understand it
On Saturday 10 May 2014 20:04:55 Jon Elson did opine
And Gene did reply:
> On 05/10/2014 05:09 PM, Erik Friesen wrote:
> > Why? I obviously have some complete lack of understanding this hal
> > scheme.
>
> Oh, the same signal name can be used later to link
> ADDITIONAL pins
> to the same signal.
On 05/10/2014 05:09 PM, Erik Friesen wrote:
>
> Why? I obviously have some complete lack of understanding this hal scheme.
>
Oh, the same signal name can be used later to link
ADDITIONAL pins
to the same signal.
Jon
--
On 05/10/2014 05:14 PM, Erik Friesen wrote:
> Ok, so I prepended it with a name to make it happy. So, why? Why is it a
> requirement to create "floating names" to link items?
>
>
>
Every "net" needs a unique name. Hal could assign random names,
but then you'd have them show up in a HAL listing a
On Saturday 10 May 2014 18:09:22 Erik Friesen did opine
And Gene did reply:
> Here is what I have so far
>
> loadrt comp count=1
> loadrt constant count=1
> addf comp.0 servo-thread
> setp comp.0.in0 25
>
> #setp comp.0.hyst
> net comp.0.in1 <= hm2_5i25.0.7i76.0.0.analogin0
> net MySignal <= comp
On Saturday 10 May 2014 17:30:54 Erik Friesen did opine
And Gene did reply:
> Where is one supposed to find information about how to use hal
> components?
>
> The hal manual has nothing more than a teaser. I am looking for info
> on comp, one of the arithmetic "functions"
The best resource for t
Ok, so I prepended it with a name to make it happy. So, why? Why is it a
requirement to create "floating names" to link items?
On Sat, May 10, 2014 at 6:09 PM, Erik Friesen wrote:
> Here is what I have so far
>
> loadrt comp count=1
> loadrt constant count=1
> addf comp.0 servo-thread
> setp
Here is what I have so far
loadrt comp count=1
loadrt constant count=1
addf comp.0 servo-thread
setp comp.0.in0 25
#setp comp.0.hyst
net comp.0.in1 <= hm2_5i25.0.7i76.0.0.analogin0
net MySignal <= comp.0.out
Here is the error
Signal name 'comp.0.in1' must not be the same as a pin. Did you omit
Thanks, I did find it here. http://linuxcnc.org/docs/html/man/man9/
I find it frustrating though, I still haven't figure out how to compare a
float value and make a signal.
This would have taken about a minute in C. Something like
if(Value>25.0) return 1;
On Sat, May 10, 2014 at 5:49 PM, Ph
Hi Erik!
On 10.05.2014 23:30, Erik Friesen wrote:
> Where is one supposed to find information about how to use hal components?
>
> The hal manual has nothing more than a teaser. I am looking for info on
> comp, one of the arithmetic "functions"
Most HAL components have associated manpages, so y
Where is one supposed to find information about how to use hal components?
The hal manual has nothing more than a teaser. I am looking for info on
comp, one of the arithmetic "functions"
--
Is your legacy SCM system holdi
33 matches
Mail list logo
