Specs on the rotary encoder.
3=Quadrature with index
25=0.25 bore
127=127 pulse/rev Probably way too coarse. Apparently super Z axis
accuracy wasn't real important on this mill back in 1990.
All three ball screws are 5 TPI.
On 3/31/2014 7:22 AM, Dave Cole wrote:
The scales should not be a
Actually 127 Pulse/rev works ok.
If you have 5 TPI screws it works out to: 0.2 / 127 = 0.00157 per
pulse. If you count all of the edges of the full quad signal (which is
normal) you can divide that by 4 which is approximately .00157/4 =
.000393 in/count.
That seems adequate to me.
Dave
On Tue, Apr 1, 2014, at 09:52 AM, Dave Cole wrote:
Actually 127 Pulse/rev works ok.
If you have 5 TPI screws it works out to: 0.2 / 127 = 0.00157 per
pulse. If you count all of the edges of the full quad signal (which is
normal) you can divide that by 4 which is approximately .00157/4 =
Wow, this is frustrating. :)
I can create HAL pins just fine, and wire them up with signals just-so. I
can watch them turn on and off at appropriate times with halscope, etc.
BUT I can't access them anywhere from code! The remap code for M6 has the
hal python component, but:
1. If I try to
Am 01.04.2014 15:01, schrieb John Kasunich:
127 is an odd encoder count, but I understand why:
0.000393 is 0.01mm.
I wonder if this mill was used to make metric parts
and they wanted the control and readout to use
metric units natively?
Until the early 1990ies, many lathes were produced in
Rod,
Again, I had the same experiance with trying to use Python for tool changer and
went back to O code. I know have a complete tool change program for a carousel
style tool changer
that raises the Z axis. Still in simulator, will be testing on real machine
soon, but, it keeps track of
On 1 April 2014 16:18, Rod Fitzsimmons Frey rodf...@gmail.com wrote:
Wow, this is frustrating. :)
I can create HAL pins just fine, and wire them up with signals just-so. I
can watch them turn on and off at appropriate times with halscope, etc.
BUT I can't access them anywhere from code! The
Billy: Thanks, I think I'm giving up too, and moving to the O-word
subroutine call. I'll probably be asking for help soon. :)
Andy: Don't worry, I don't think there were any false paths. I needed a
userspace HAL component regardless to integrate the signal lines from my
spindle. The python
On 04/01/2014 08:01 AM, John Kasunich wrote:
127 is an odd encoder count, but I understand why:
0.000393 is 0.01mm.
I wonder if this mill was used to make metric parts
and they wanted the control and readout to use
metric units natively?
Yup, any time I see encoders with 127 or 2540 or
On 04/01/2014 10:32 AM, Peter Blodow wrote:
Until the early 1990ies, many lathes were produced in Germany with inch
screws and a 127 teeth gear wheel to drive them in order to end up with
metric threads.
But that means you can't disengage the half nuts and
re-engage them
for the next
OKay, some discussion going around on the thread about using Python.. I gave up
on that.. was too complicated.. I really wanted to use it though.. and no clear
documentation no how
to read AND set pins...
So, I'm now I'm back to using O-code -- and have a complete working script in
my
Also forgot to ask... Was trying to make use of #5600 and #5601.. but to no
avail.. On a error.. I'm currently just doing a (abort, Message)
Anyone know anything about #5600 and #5601 ? other than this?
5600 toolchanger fault indicator. Used with the iocontrol-v2 component. 1:
toolchanger
On 4/1/14 11:51 , Billy Huddleston wrote:
OKay, some discussion going around on the thread about using Python.. I gave
up on that.. was too complicated.. I really wanted to use it though.. and no
clear documentation no how
to read AND set pins...
So, I'm now I'm back to using O-code -- and
After some calming words from my therapist I'm coming to grips with the
idea that I can't get access to pins directly from embedded python. (maybe
through emccanon? Ah, leave it behind.)
However I seem to have made progress by using the mappings of M62-M65 to
the dout-00 through 03 pins. M66
Sebastian,
Thanks for the input.. however, Not all carousel tool changers are random..
such as the case with this one. The carousel moves into position. The
Z-lowers. grabs the tool and the
carousel moves out. To put the tool, The Z moves to the Z-change height, ram
moves in, Release tool,
On 1 April 2014 19:15, Billy Huddleston bi...@ivdc.com wrote:
5600 toolchanger fault indicator. Used with the iocontrol-v2 component. 1:
toolchanger faulted, 0: normal. Volatile.
You may not be using iocontrol-v2.
(I am not sure if it is even selectable)
--
atp
If you can't fix it, you
On 4/1/2014 7:01 AM, John Kasunich wrote:
On Tue, Apr 1, 2014, at 09:52 AM, Dave Cole wrote:
Actually 127 Pulse/rev works ok.
If you have 5 TPI screws it works out to: 0.2 / 127 = 0.00157 per
pulse. If you count all of the edges of the full quad signal (which is
normal) you can divide
Ah. Okay.. So that's something new then...
On 04/01/2014 03:56 PM, andy pugh wrote:
On 1 April 2014 19:15, Billy Huddleston bi...@ivdc.com wrote:
5600 toolchanger fault indicator. Used with the iocontrol-v2 component. 1:
toolchanger faulted, 0: normal. Volatile.
You may not be using
Rod,
Am 31.03.2014 um 21:22 schrieb Rod Fitzsimmons Frey rodf...@gmail.com:
I've looked at this and see where the bitmask, but it seems I can only read
pins with the hal component, not set them?
that is correct
How can I turn on my power drawbar valve, trigger the blow valve, etc?
you can
On 1 April 2014 21:00, Billy Huddleston bi...@ivdc.com wrote:
Ah. Okay.. So that's something new then...
I don't know if it is new, default, or abandoned. The INI config docs
for both 2.5 and Master make no mention of it.
http://wiki.linuxcnc.org/cgi-bin/wiki.pl?ToolchangerProtocolProposal
says
I have it working the other way.. so no big deal.. just need to get my other
questions answered now.
On 04/01/2014 04:11 PM, andy pugh wrote:
On 1 April 2014 21:00, Billy Huddleston bi...@ivdc.com wrote:
Ah. Okay.. So that's something new then...
I don't know if it is new, default, or
On 4/1/2014 9:32 AM, Peter Blodow wrote:
Am 01.04.2014 15:01, schrieb John Kasunich:
127 is an odd encoder count, but I understand why:
0.000393 is 0.01mm.
I wonder if this mill was used to make metric parts
and they wanted the control and readout to use
metric units natively?
Until the
Am 01.04.2014 um 22:11 schrieb andy pugh bodge...@gmail.com:
On 1 April 2014 21:00, Billy Huddleston bi...@ivdc.com wrote:
Ah. Okay.. So that's something new then...
I don't know if it is new, default, or abandoned. The INI config docs
for both 2.5 and Master make no mention of it.
I don't have configs/sim/axis/python_demo/axis-iocontrolv2-demo.ini or even
configs/sim/axis/python_demo and I'm running the latest master...
On 04/01/2014 04:20 PM, Michael Haberler wrote:
Am 01.04.2014 um 22:11 schrieb andy pugh bodge...@gmail.com:
On 1 April 2014 21:00, Billy Huddleston
Am 01.04.2014 um 22:27 schrieb Billy Huddleston bi...@ivdc.com:
I don't have configs/sim/axis/python_demo/axis-iocontrolv2-demo.ini or even
configs/sim/axis/python_demo and I'm running the latest master...
master as of now:
Am 01.04.2014 um 22:27 schrieb Billy Huddleston bi...@ivdc.com:
I don't have configs/sim/axis/python_demo/axis-iocontrolv2-demo.ini or even
configs/sim/axis/python_demo and I'm running the latest master...
master as of now:
I'm on call 24/7, and I'm damn glad the days of the pager are long gone. I
had to have one of them strapped on my all the time.
Ever tried to water ski with a pager?
No, but I did go to a Peter Gabriel concert with one once - told them at
work that gosh - somehow I missed the beep! (the
Electrically, yes if you use a microstepping drive. :-)
But if your ball screw has slop in it, then no. :-(
Dave
On 4/1/2014 2:57 PM, Gregg Eshelman wrote:
On 4/1/2014 7:01 AM, John Kasunich wrote:
On Tue, Apr 1, 2014, at 09:52 AM, Dave Cole wrote:
Actually 127 Pulse/rev works ok.
If
here is an example for what I described below:
http://git.linuxcnc.org/gitweb?p=linuxcnc.git;a=commit;h=d426cc90b5e1338f1a2b8ad403ea11e0a24f3b50
try 'M465 P0Q1' and 'M465 P0Q0' and watch motion.digital-out-00
- Michael
Am 01.04.2014 um 22:10 schrieb Michael Haberler mai...@mah.priv.at:
Rod,
Thanks, Michael! I had read much of the C++ code but not that bit... I got
to SET_DIGITAL_OUTPUT_BIT and thought that was as good as it got. It
seemed at that point I might as well just execute(G64 P01) etc.
On Tue, Apr 1, 2014 at 6:53 PM, Michael Haberler mai...@mah.priv.at wrote:
here is
Am 02.04.2014 um 02:26 schrieb Rod Fitzsimmons Frey rodf...@gmail.com:
Thanks, Michael! I had read much of the C++ code but not that bit... I got
to SET_DIGITAL_OUTPUT_BIT and thought that was as good as it got. It
seemed at that point I might as well just execute(G64 P01) etc.
I suggest
On 04/01/2014 02:57 PM, Gregg Eshelman wrote:
On 4/1/2014 7:01 AM, John Kasunich wrote:
On Tue, Apr 1, 2014, at 09:52 AM, Dave Cole wrote:
Actually 127 Pulse/rev works ok.
If you have 5 TPI screws it works out to: 0.2 / 127 = 0.00157 per
pulse. If you count all of the edges of the full
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 and a garden
variety LPT can handle two quadrature
Hi everyone
If I sound confused, Good I am.
1. how is Xenable triggered, it doesn't appear to be going high
2. Attached is a file called uln2003.hal which is a file I downloaded and
have used as a basis for my .hal. It is for a 2 axis 4 wire connection and
sets out the pins for A B C an D
34 matches
Mail list logo
