On 5/8/2012 7:48 PM, Steve Blackmore wrote:
> On Tue, 08 May 2012 08:39:17 -0400, you wrote:
>
>
>> On 5/7/2012 6:34 AM, Steve Blackmore wrote:
>>
>>> I also have an 8 position Enco type auto tool changer that I made, but
>>> haven't managed to get that to work with LinuxCNC. I gave up af
On Tue, 08 May 2012 08:39:17 -0400, you wrote:
>On 5/7/2012 6:34 AM, Steve Blackmore wrote:
>> I also have an 8 position Enco type auto tool changer that I made, but
>> haven't managed to get that to work with LinuxCNC. I gave up after days
>> of hal editing.
>>
>
>If you want to resurrect tha
On Tuesday, May 08, 2012 11:59:31 AM andy pugh did opine:
> On 8 May 2012 16:32, gene heskett wrote:
> >> Maybe the RS274NGC_STARTUP_CODE entry in the INI file?
> >
> > Not used in mine, possibly not included because I could never get
> > stepconfig to run,
>
> As far as I know, Stepconf doesn'
On 8 May 2012 16:32, gene heskett wrote:
>> Maybe the RS274NGC_STARTUP_CODE entry in the INI file?
> Not used in mine, possibly not included because I could never get
> stepconfig to run,
As far as I know, Stepconf doesn't add that. You would have to add it
yourself, but it ought to work to set
On 8 May 2012 13:39, Dave wrote:
> On 5/7/2012 6:34 AM, Steve Blackmore wrote:
>> I also have an 8 position Enco type auto tool changer
...
> > I gave up after days of hal editing.
> If you want to resurrect that project.
There are a couple of dedicated HAL components for that type of tool chang
On Tuesday, May 08, 2012 11:22:25 AM andy pugh did opine:
> On 8 May 2012 01:01, gene heskett wrote:
> > Lathe mode seems to default to G8, that is something I've not tweaked.
> > Another man page to read...
>
> Maybe the RS274NGC_STARTUP_CODE entry in the INI file?
> http://www.linuxcnc.org/doc
On 5/7/2012 6:34 AM, Steve Blackmore wrote:
> I also have an 8 position Enco type auto tool changer that I made, but
> haven't managed to get that to work with LinuxCNC. I gave up after days
> of hal editing.
>
If you want to resurrect that project.. post what problems you run into.
A combina
On 8 May 2012 01:01, gene heskett wrote:
> Lathe mode seems to default to G8, that is something I've not tweaked.
> Another man page to read...
Maybe the RS274NGC_STARTUP_CODE entry in the INI file?
http://www.linuxcnc.org/docview/html/config/ini_config.html#_rs274ngc_section_a_id_sub_rs274ngc_se
Sounds like a good idea Andy, as long as each axis retains it's own value.
Mike
On 7 May 2012, at 20:15, andy pugh wrote:
> On 7 May 2012 15:16, gene heskett wrote:
>> because
>> Touch Off doesn't display the current setting, but defaults to 0.0. That
>> of course makes it easy to cancel a
On Monday, May 07, 2012 11:03:14 PM Jon Elson did opine:
> gene heskett wrote:
> > On Monday, May 07, 2012 10:56:31 AM gene heskett did opine:
> >>> No - My tool 1 is my reference and touch off tool, it has offsets of
> >>> 0, 0, all other tools are referenced to that - it's a CNMG type
> >>
> >
On Monday, May 07, 2012 10:50:32 PM Greg Bernard did opine:
> Even the cheapie calipers have a serial port like the $16 one I got from
> Harbor Freight a few weeks ago. The manual doesn't even mention it but
> you can pop off a little cover opposite the battery compartment and
> there it is. There
gene heskett wrote:
> On Monday, May 07, 2012 10:56:31 AM gene heskett did opine:
>
>
>>> No - My tool 1 is my reference and touch off tool, it has offsets of
>>> 0, 0, all other tools are referenced to that - it's a CNMG type
>>>
>> An acronym I'm not familiar with, but I expect google
hat. -Thomas Edison, inventor (1847-1931)
>
> From: gene heskett
>To: emc-users@lists.sourceforge.net
>Sent: Monday, May 7, 2012 7:01 PM
>Subject: Re: [Emc-users] hal 'net' command puzzler
>
>On Monday, May 07, 2012 07:58:4
On Monday, May 07, 2012 07:58:43 PM andy pugh did opine:
> On 7 May 2012 22:26, gene heskett wrote:
> > Something like that, I've been measuring the diameter and dividing by
> > 2, writing that down in case I need to tweak it, and entering it.
>
> If you are in G7 then there is no need to divide
On Monday, May 07, 2012 07:56:47 PM andy pugh did opine:
> On 7 May 2012 15:16, gene heskett wrote:
> > because
> > Touch Off doesn't display the current setting, but defaults to 0.0.
> > That of course makes it easy to cancel a Touch Off, but I find in my
> > usage, I need to just edit it anoth
On Monday, May 07, 2012 07:49:50 PM dave did opine:
> On Mon, 7 May 2012 10:59:00 -0400
>
> gene heskett wrote:
> > On Monday, May 07, 2012 10:56:31 AM gene heskett did opine:
> > > > No - My tool 1 is my reference and touch off tool, it has offsets
> > > > of 0, 0, all other tools are reference
On Monday, May 07, 2012 05:27:18 PM Andy Pugh did opine:
> Gene said:
> >> Whoever has the touch-off code box, it sure would be nice if when you
> >> called it up, it displayed the current value separate the input box.
> >> As is, I have to write it down, so I know where I am if I only need
> >>
On 7 May 2012 22:26, gene heskett wrote:
> Something like that, I've been measuring the diameter and dividing by 2,
> writing that down in case I need to tweak it, and entering it.
If you are in G7 then there is no need to divide by 2 if you do it the
way I do it.
If I want 10mm dia then I turn
On Monday, May 07, 2012 12:42:26 PM sa...@empirescreen.com did opine:
> You do know you can do math in the touch-off window?
>
> so 5.345/2 or 5.345*2 or whatever.
>
> http://www.linuxcnc.org/docs/2.5/html/gui/axis.html#_manual_control
>
> sam
Something like that, I've been measuring the diame
On 7 May 2012 15:16, gene heskett wrote:
> because
> Touch Off doesn't display the current setting, but defaults to 0.0. That
> of course makes it easy to cancel a Touch Off, but I find in my usage, I
> need to just edit it another thou or so.
Having considered this during a long and tedious rid
On 7 May 2012 15:59, gene heskett wrote:
> Yes, that is the insert style the Glanze uses. 80 degree rhombic, 7 degree
> rake etc. Costs too much. :(
I am not too fond of C***. They have the advantage that they face and
turn equally well, but they don't miss the tailstock centre. I rather
prefe
On Mon, 7 May 2012 12:02:01 +0100, you wrote:
>On 7 May 2012 00:09, Jon Elson wrote:
>> If you have a quick-change toolpost, you should be able to set up X and Z
>> offsets for each tool in the tool table.
>
>My QC tool holder isn't spectacularly repeatable, So I generally stop
>0.5mm oversize, m
On Mon, 7 May 2012 10:59:00 -0400
gene heskett wrote:
> On Monday, May 07, 2012 10:56:31 AM gene heskett did opine:
>
> > > No - My tool 1 is my reference and touch off tool, it has offsets
> > > of 0, 0, all other tools are referenced to that - it's a CNMG
> > > type
> >
> > An acronym I'm no
2012/5/7 Andy Pugh :
>
> You can type mathematical expressions on the box, I don't know if you can use
> the #5400 or #<_x> syntax in there.
The page of Samco's link says that references to parameters are not allowed:
http://www.linuxcnc.org/docs/2.5/html/gui/axis.html#_manual_control
Viesturs
On Mon, 7 May 2012 10:59:00 -0400
gene heskett wrote:
> On Monday, May 07, 2012 10:56:31 AM gene heskett did opine:
>
> > > No - My tool 1 is my reference and touch off tool, it has offsets
> > > of 0, 0, all other tools are referenced to that - it's a CNMG
> > > type
> >
> > An acronym I'm no
Gene said:
>
>> Whoever has the touch-off code box, it sure would be nice if when you
>> called it up, it displayed the current value separate the input box. As
>> is, I have to write it down, so I know where I am if I only need to adjust
>> it say 0.0027 from where its at to get it exactly
You do know you can do math in the touch-off window?
so 5.345/2 or 5.345*2 or whatever.
http://www.linuxcnc.org/docs/2.5/html/gui/axis.html#_manual_control
sam
On Mon, 7 May 2012 10:16:11 -0400
gene heskett wrote:
> On Monday, May 07, 2012 09:20:34 AM Steve Blackmore did opine:
>
> > On Sun
On Monday, May 07, 2012 10:56:31 AM gene heskett did opine:
> > No - My tool 1 is my reference and touch off tool, it has offsets of
> > 0, 0, all other tools are referenced to that - it's a CNMG type
>
> An acronym I'm not familiar with, but I expect google works ...
>
Yes, that is the insert
On Monday, May 07, 2012 09:20:34 AM Steve Blackmore did opine:
> On Sun, 6 May 2012 21:52:21 -0400, you wrote:
> >> > What is the best practice to establish the X zero on a lathe? I am
> >> > making a test cut, measuring it and dividing that by half to enter
> >> > in a Touch Off.
>
> That's the
On Sun, 6 May 2012 21:52:21 -0400, you wrote:
>> > What is the best practice to establish the X zero on a lathe? I am
>> > making a test cut, measuring it and dividing that by half to enter in
>> > a Touch Off.
That's the only way to accurately do it.
>> If you have a quick-change toolpost,
>
On 7 May 2012 00:09, Jon Elson wrote:
> If you have a quick-change toolpost, you should be able to set up X and Z
> offsets for each tool in the tool table.
My QC tool holder isn't spectacularly repeatable, So I generally stop
0.5mm oversize, measure, then make the final cut.
I think that better
On Monday, May 07, 2012 02:17:18 AM Jon Elson did opine:
> gene heskett wrote:
> > On Sunday, May 06, 2012 09:15:18 PM Jon Elson did opine:
> >> you should be able to set up X and
> >> Z offsets for each tool in the tool table.
> >
> > That would require I get at least 3 or 4 more QC toolholders.
gene heskett wrote:
> On Sunday, May 06, 2012 09:15:18 PM Jon Elson did opine:
>
>
>
>> you should be able to set up X and
>> Z offsets for each tool in the tool table.
>>
>
> That would require I get at least 3 or 4 more QC toolholders. But then I
> am reminded that the QC post must be r
On Sunday, May 06, 2012 09:15:18 PM Jon Elson did opine:
> gene heskett wrote:
> > On Sunday, May 06, 2012 02:33:08 PM Jon Elson did opine:
> >
> >
> >
> > What is the best practice to establish the X zero on a lathe? I am
> > making a test cut, measuring it and dividing that by half to enter
gene heskett wrote:
> On Sunday, May 06, 2012 02:33:08 PM Jon Elson did opine:
>
>
>
> What is the best practice to establish the X zero on a lathe? I am making
> a test cut, measuring it and dividing that by half to enter in a Touch Off.
>
>
If you have a quick-change toolpost, you should
On Sunday, May 06, 2012 06:38:05 PM Dave did opine:
> On 5/6/2012 3:02 PM, gene heskett wrote:
> > On Sunday, May 06, 2012 03:01:18 PM Dave did opine:
> >> On 5/6/2012 2:31 PM, gene heskett wrote:
> >>> On Sunday, May 06, 2012 02:12:18 PM John Prentice did opine:
> Gene - greetings
>
>
On 5/6/2012 3:02 PM, gene heskett wrote:
> On Sunday, May 06, 2012 03:01:18 PM Dave did opine:
>
>
>> On 5/6/2012 2:31 PM, gene heskett wrote:
>>
>>> On Sunday, May 06, 2012 02:12:18 PM John Prentice did opine:
>>>
Gene - greetings
>> As an aside, as m
On Sunday, May 06, 2012 03:01:18 PM Dave did opine:
> On 5/6/2012 2:31 PM, gene heskett wrote:
> > On Sunday, May 06, 2012 02:12:18 PM John Prentice did opine:
> >> Gene - greetings
> >>
> As an aside, as many nets are best written on one line, inventing
> the signal name is tedious. It
On Sunday, May 06, 2012 02:33:08 PM Jon Elson did opine:
> gene heskett wrote:
> > Thanks to all who helped, I cut another thread this evening, wrong of
> > course but at least I now know why it was wrong. Hopefully the next
> > one will be right. ;-)
>
> Progress comes in small steps, but as l
On 5/6/2012 2:31 PM, gene heskett wrote:
> On Sunday, May 06, 2012 02:12:18 PM John Prentice did opine:
>
>
>> Gene - greetings
>>
>>
As an aside, as many nets are best written on one line, inventing the
signal name is tedious. It would suit me to allow a wildcard, "*" or
w
On Sunday, May 06, 2012 02:12:18 PM John Prentice did opine:
> Gene - greetings
>
> >> As an aside, as many nets are best written on one line, inventing the
> >> signal name is tedious. It would suit me to allow a wildcard, "*" or
> >> whatever, as signalname and HAL would invent a unique interna
Thanks Andy
On 6 May 2012, at 13:23, Andy Pugh wrote:
>
>
> On 6 May 2012, at 08:25, Mike Bennett wrote:
>
>> 1. What is the scope of a signal name. Is it machine wide or limited to the
>> Hal file it appears in?
>
> They are system-wide and are the only practical way to share data betw
gene heskett wrote:
>
> Thanks to all who helped, I cut another thread this evening, wrong of
> course but at least I now know why it was wrong. Hopefully the next one
> will be right. ;-)
>
Progress comes in small steps, but as long as each step moves in the right
direction, that is good!
Gene - greetings
>>
>> As an aside, as many nets are best written on one line, inventing the
>> signal name is tedious. It would suit me to allow a wildcard, "*" or
>> whatever, as signalname and HAL would invent a unique internal name for
>> its own purposes.
>>
>> John Prentice
>
> While that mig
On 6 May 2012, at 08:25, Mike Bennett wrote:
> 1. What is the scope of a signal name. Is it machine wide or limited to the
> Hal file it appears in?
They are system-wide and are the only practical way to share data between HAL
files.
> 2. If machine wide, are there existing signal names i
As a new user I've been following this thread with interest. My only questions
are:
1. What is the scope of a signal name. Is it machine wide or limited to the
Hal file it appears in.
2. If machine wide, are there existing signal names in existence that I have to
avoid re-declaring?
Mike
On Sunday, May 06, 2012 12:24:59 AM Jon Elson did opine:
> gene heskett wrote:
> > Greetings;
> >
> > As I read the hal manuals getting started section, where the keywords
> > loadrt, setp, addf, and net are defined, I didn't understand at first
> > that arg[3], arg[4] arg[5] etc of a "net" comme
On Saturday, May 05, 2012 11:07:28 PM Andy Pugh did opine:
> On 5 May 2012, at 23:42, gene heskett wrote:
> > I think I was in the devel branch, but similar. Right now g76 is
> > waiting forever for the index pulse, which is not good, so I
> > obviously mucked up something. encoder.0.index is v
gene heskett wrote:
> Greetings;
>
> As I read the hal manuals getting started section, where the keywords
> loadrt, setp, addf, and net are defined, I didn't understand at first that
> arg[3], arg[4] arg[5] etc of a "net" commend can be repeated to add sending
> something from arg[2] to more th
On Saturday, May 05, 2012 07:52:50 PM Andy Pugh did opine:
> On 5 May 2012, at 23:42, gene heskett wrote:
> > I think I was in the devel branch, but similar. Right now g76 is
> > waiting forever for the index pulse, which is not good, so I
> > obviously mucked up something. encoder.0.index is v
On 5 May 2012, at 23:42, gene heskett wrote:
> I think I was in the devel branch, but similar. Right now g76 is waiting
> forever for the index pulse, which is not good, so I obviously mucked up
> something. encoder.0.index is visible in hal meter, but G76 can't see it.
You need to wire up
On Saturday, May 05, 2012 06:43:45 PM John Prentice did opine:
> From: "andy pugh"
>
> > Every "net" command is followed immediately by a signal name. That is,
> > a name you have chosen yourself, to make sense to you (or to confuse
> > yourself horribly in the future, if you so choose).
> > You
On Saturday, May 05, 2012 06:37:46 PM Jeff Epler did opine:
> Are we talking about this documentation?
>
> http://linuxcnc.org/docs/2.5/html/hal/basic_hal.html#_net_a_id_sub_net_
> a if so, the syntax
> net
> doesn't really reflect what "net" will actually accept. I've revised
> the d
On Saturday, May 05, 2012 06:34:23 PM andy pugh did opine:
> On 5 May 2012 18:06, gene heskett wrote:
> > And its long list of options is something that could be readily
> > calculated from the thread pitch, clipping off the top and bottom 10%
> > of to fit the usual USS and USF thread profile, s
On Saturday, May 05, 2012 06:32:47 PM andy pugh did opine:
> On 5 May 2012 18:24, gene heskett wrote:
> > So I cannot use that signal1 defined name as an 'out1' in another net
> > statement, but must add the other targets/pins in the same line it is
> > defined in.
>
> No, that is all wrong too.
On Saturday, May 05, 2012 06:29:57 PM Lars Andersson did opine:
> My 2c trying to clear the fog.
>
> For every signal in hal defined by one or more net statements:
>
> 1) each line affecting "signal1" starts with "net signal1 "
> 2) exactly one term has to be an output
> 3) all other terms has t
On Saturday, May 05, 2012 06:03:17 PM Kent A. Reed did opine:
[...]
> OOPS I was in a hurry to get to the store and left out an important
> thought. The order of the pins in a net command is not significant.
> Their mode is defined elsewhere, not by their order of occurrence in the
> net command
From: "andy pugh"
>
> Every "net" command is followed immediately by a signal name. That is,
> a name you have chosen yourself, to make sense to you (or to confuse
> yourself horribly in the future, if you so choose).
> You can uses the same signal name on as many net commands as you like.
> But b
On 5/5/2012 2:03 PM, Jeff Epler wrote:
> Are we talking about this documentation?
> http://linuxcnc.org/docs/2.5/html/hal/basic_hal.html#_net_a_id_sub_net_a
> if so, the syntax
> net
> doesn't really reflect what "net" will actually accept. I've revised
> the documentation to hopef
On Saturday, May 05, 2012 01:37:42 PM Kent A. Reed did opine:
> On 5/4/2012 10:41 PM, gene heskett wrote:
> > Greetings;
> >
> > As I read the hal manuals getting started section, where the keywords
> > loadrt, setp, addf, and net are defined, I didn't understand at first
> > that arg[3], arg[4]
Are we talking about this documentation?
http://linuxcnc.org/docs/2.5/html/hal/basic_hal.html#_net_a_id_sub_net_a
if so, the syntax
net
doesn't really reflect what "net" will actually accept. I've revised
the documentation to hopefully improve things:
1.4 net
The command net
On 5 May 2012 18:06, gene heskett wrote:
> And its long list of options is something that could be readily calculated
> from the thread pitch, clipping off the top and bottom 10% of to fit the
> usual USS and USF thread profile, s
This would be less useful for those of us who only ever make metri
On 5 May 2012 18:24, gene heskett wrote:
> So I cannot use that signal1 defined name as an 'out1' in another net
> statement, but must add the other targets/pins in the same line it is
> defined in.
No, that is all wrong too.
Every "net" command is followed immediately by a signal name. That is
On Saturday, May 05, 2012 01:26:16 PM Kent A. Reed did opine:
> On 5/5/2012 8:46 AM, gene heskett wrote:
> > Does linuxcnc have a utility that can scan a .hal file and draw a flow
> > chart? HalShow would appear to be similar, but demands a fully legal
> > hal file so that linuxcnc can actually l
On Saturday, May 05, 2012 01:08:12 PM Andy Pugh did opine:
> On 5 May 2012, at 13:46, gene heskett wrote:
> > Which seems to say that the out1 name string in the first format,
> > becomes the signal1 name string in the second format?
>
> I have no idea what you mean, but I think you have it wron
aj 2012 14:47
> To: emc-users@lists.sourceforge.net
> Subject: Re: [Emc-users] hal 'net' command puzzler
>
> On Saturday, May 05, 2012 07:32:05 AM Andy Pugh did opine:
>
> > On 5 May 2012, at 03:41, gene heskett wrote:
> > > arg[3], arg[4] arg[5] etc of a "net&q
On Saturday, May 05, 2012 12:15:29 PM Dave did opine:
> On 5/5/2012 8:46 AM, gene heskett wrote:
> > On Saturday, May 05, 2012 07:32:05 AM Andy Pugh did opine:
> >> On 5 May 2012, at 03:41, gene heskett wrote:
> >>> arg[3], arg[4] arg[5] etc of a "net" commend can be repeated to add
> >>> sending
On 5/4/2012 10:41 PM, gene heskett wrote:
> Greetings;
>
> As I read the hal manuals getting started section, where the keywords
> loadrt, setp, addf, and net are defined, I didn't understand at first that
> arg[3], arg[4] arg[5] etc of a "net" commend can be repeated to add sending
> something fro
So I said (5/5/2012 10:05 AM):
> On 5/4/2012 10:41 PM, gene heskett wrote:
>> Greetings;
>>
>> As I read the hal manuals getting started section, where the keywords
>> loadrt, setp, addf, and net are defined, I didn't understand at first
>> that
>> arg[3], arg[4] arg[5] etc of a "net" commend can
On 5 May 2012, at 13:46, gene heskett wrote:
>
> Which seems to say that the out1 name string in the first format, becomes
> the signal1 name string in the second format?
I have no idea what you mean, but I think you have it wrong.
"signal1" will take the value of "out1" and copy that value
On 5/5/2012 8:46 AM, gene heskett wrote:
> Does linuxcnc have a utility that can scan a .hal file and draw a flow
> chart? HalShow would appear to be similar, but demands a fully legal hal
> file so that linuxcnc can actually load up and run, so would seem to be of
> no use for troubleshooting a b
On 5/5/2012 8:46 AM, gene heskett wrote:
> On Saturday, May 05, 2012 07:32:05 AM Andy Pugh did opine:
>
>
>> On 5 May 2012, at 03:41, gene heskett wrote:
>>
>>> arg[3], arg[4] arg[5] etc of a "net" commend can be repeated to add
>>> sending something from arg[2] to more than one load. B
On Saturday, May 05, 2012 07:32:05 AM Andy Pugh did opine:
> On 5 May 2012, at 03:41, gene heskett wrote:
> > arg[3], arg[4] arg[5] etc of a "net" commend can be repeated to add
> > sending something from arg[2] to more than one load. But I can't
> > name a previously used output and send it to
On 5 May 2012, at 03:41, gene heskett wrote:
>
> arg[3], arg[4] arg[5] etc of a "net" commend can be repeated to add sending
> something from arg[2] to more than one load. But I can't name a previously
> used output and send it to the 2nd place it needs to go. Its s show
> stopper error.
Greetings;
As I read the hal manuals getting started section, where the keywords
loadrt, setp, addf, and net are defined, I didn't understand at first that
arg[3], arg[4] arg[5] etc of a "net" commend can be repeated to add sending
something from arg[2] to more than one load. But I can't name
75 matches
Mail list logo
