Hi Matt
Gmoccapy is now a stand alone program and no longer rides on the gscreen
program. Gscreen is a program on it own and so is gmoccapy. You should
load any one of the two.
On 2014-04-03 06:50, Matt Shaver wrote:
> I can start gmoccapy in two different ways, either DISPLAY = gmoccapy,
> or D
I can start gmoccapy in two different ways, either DISPLAY = gmoccapy,
or DISPLAY = gscreen -c gmoccapy. However these seem to be two somewhat
different programs, both called gmoccapy :)
My questions are:
1. Most of the docs I can find relate to the DISPLAY = gmoccapy version.
Is there documentat
On Sat, 2014-03-29 at 15:02 -0400, John Kasunich wrote:
>
> On Sat, Mar 29, 2014, at 12:01 PM, Jon Elson wrote:
> > On 03/29/2014 03:39 AM, Jeshua Lacock wrote:
> > >
> > >
> > >
> > > My 1080 pound 4x5 foot granite surface has a glass cut looking surface
> > > that I bought surplus.
> > > Anyway
Hi Seb,
Few questions:
Who made decision about not including ubc and when?
Where are the emails that invite developers to irc meeting to vote this?
Why voting about need to integrate ubc before 2.6 from irc meeting
http://wiki.linuxcnc.org/cgi-bin/wiki.pl?Meeting201306 was ignored?
Why you ignor
On Wednesday 02 April 2014 12:26:19 Peter Blodow did opine:
> Am 02.04.2014 14:11, schrieb andy pugh:
> > On 2 April 2014 12:54, Peter Blodow wrote:
> >> No problem with that, because reversing the drive is done with one
> >> lever, no cranking, no re-engaging, no dial or indicator necessary.
> >
On 04/02/2014 08:39 AM, Peter Blodow wrote:
>
> I don't even know what threading dials are and where they are installed,
> sorry. I usually cut a thread up to a given length, then stop and
> retract the tool in one instance. It's a two hand job. I can put the
> drive directly in reverse for a fract
On 04/01/2014 11:27 PM, Gregg Eshelman wrote:
Oops, didn't read to the end.
>
> Or is there a single board that plugs into one parallel port, can run up
> to four stepper drives, read up to four TTL quadrature scale/encoder
> inputs, has an e-stop input, limit switch inputs for 3 or 4 axes, can
>
On 04/01/2014 11:27 PM, Gregg Eshelman wrote:
> Now back to the question, now that it's established exactly what kind of
> signal the scales and encoder put out.
>
> What *hardware* do I need to interface them safely with a PC? I've read
> that it's "simple" to connect "directly" to a parallel port
With the large number of changes to the architecture, will there be a jump
to 3.0 after 2.7?
On Wed, Apr 2, 2014 at 4:25 AM, sam sokolik wrote:
> Yay! This is a good decision. Just a stepping stone to 2.7. (which
> won't be as long as 2.6 was)
>
> I have seen all the sausage making - with th
Thanks, Andy,
I now see that I can get as old as a gnu and still learn dazu... Never
seen anything like that counter, and wouldn't know where to mount it on
the lathes I know. It's a good idea to make a run out groove that way -
I usually have to cut it right in the beginning (with a parting too
Am 02.04.2014 um 16:23 schrieb Rod Fitzsimmons Frey :
> Thanks, your explanations really help. I actually think there's a
> astonishing lack of entropy in the code, given its age and the inherent
> complexity of the problem. It's all coming together for me with your
> explanations.
would you m
Thanks, your explanations really help. I actually think there's a
astonishing lack of entropy in the code, given its age and the inherent
complexity of the problem. It's all coming together for me with your
explanations.
On Wed, Apr 2, 2014 at 7:29 AM, Michael Haberler wrote:
>
> Am 02.04.201
On 2 April 2014 14:39, Peter Blodow wrote:
> I don't even know what threading dials are and where they are installed,
Here is a typical one:
http://www.practicalmachinist.com/vb/attachments/f25/5191d1216225324-thread-dial-specs-9-junior-9-inch-thread-dial.jpg
It simply counts the leadscrew thre
Am 02.04.2014 14:11, schrieb andy pugh:
> On 2 April 2014 12:54, Peter Blodow wrote:
>
>> No problem with that, because reversing the drive is done with one
>> lever, no cranking, no re-engaging, no dial or indicator necessary. All
>> thread cutting is done this way over here in the shops, I've ne
On 2 April 2014 12:54, Peter Blodow wrote:
> No problem with that, because reversing the drive is done with one
> lever, no cranking, no re-engaging, no dial or indicator necessary. All
> thread cutting is done this way over here in the shops, I've never seen
> any other.
I would imagine that it
Am 02.04.2014 13:06, schrieb andy pugh:
> On 2 April 2014 11:29, Peter Blodow wrote:
>> There is no problem in disengaging the half nuts,
>> re-arranging things and closing again. Multiple pass cuts are, of
>> course, always done by retracting the tool und reversing the drive.
> The point is that
Am 02.04.2014 um 12:41 schrieb Rod Fitzsimmons Frey :
> To test my understanding: is it legitimate for the python mapping code to
> call canon methods directly? Would that mess up state for the interpreter
> when it continued executing?
to be more clear:
canon is primarily a 'downwards' API -
Rod,
Am 02.04.2014 um 12:41 schrieb Rod Fitzsimmons Frey :
> To test my understanding: is it legitimate for the python mapping code to
> call canon methods directly?
yes, definitely - it's just what the interpreter itself does all the time
the basic logic of the interpreter inner loop is:
- par
On 2 April 2014 11:29, Peter Blodow wrote:
> There is no problem in disengaging the half nuts,
> re-arranging things and closing again. Multiple pass cuts are, of
> course, always done by retracting the tool und reversing the drive.
The point is that you have to reverse the drive rather than dise
Michael,
the control flow is this:
>
> what happens here: Python calls back into the interpreter C++ code to
> parse and execute this line. Since is basically a new block, it
> must save the current block context, do the job, restore the current block
> context, return. That's where the design re
Not really, Jon, all the metric/Whitworth-conversion is done within the
feed gear box. I can select between 60 metric and imperial feed rates
each. I switch metric to imperial with the flic of one lever. This is
done, however, by a combination of gear wheels (34/26*79/41) to avoid
the use of a
Yay! This is a good decision. Just a stepping stone to 2.7. (which
won't be as long as 2.6 was)
I have seen all the sausage making - with the relatively few people
actively working on linuxcnc - big features/improvements are in the
works. (and this takes time) (but thing are coalescing..)
Rod,
Am 02.04.2014 um 10:57 schrieb Rod Fitzsimmons Frey :
> Thanks Michael, I really appreciate the help. For clarity, could you tell
> me why calling G64/G65 to set a pin results in recursion? In the example
> code you sent on line 49 that is done:
>
> self.execute("G64 P0.001",lineno())
t
On 2 April 2014 05:51, Bill Brettle wrote:
> 1. how is Xenable triggered, it doesn't appear to be going high
Xenable isn't a HAL pin, so I assume that it is a signal that is
created in your HAL file.
You probably want to connect it to axis.0.amp-enable-out.
http://www.linuxcnc.org/docs/html/man/
I can see that happening. Went to a Metallica concert a few years back,
and couldn't hear a thing for about a week. Had to have everybody text
message me if they needed something. ;-)
Mark
On Tue, Apr 1, 2014 at 4:52 PM, John Alexander Stewart
wrote:
> > I'm on call 24/7, and I'm damn glad t
On 2 April 2014 05:27, Gregg Eshelman wrote:
> Recommend something? I've searched some and findings range from "Yeah,
> TTL quadrature outputs can be connected to a parallel port." (without
> the author giving any specific details) to "Here's a schematic and a
> BOM, now get out your soldering ir
Thanks Michael, I really appreciate the help. For clarity, could you tell
me why calling G64/G65 to set a pin results in recursion? In the example
code you sent on line 49 that is done:
self.execute("G64 P0.001",lineno())
Also, while I have your attention. :) Would this job [1] be better done
27 matches
Mail list logo
