Jymmm: small deer ;)
alex_joni: That's like telling someone "DONT LOOK", so what do they do? They look!
alex_joni: I wonder if this could be related to the problem we are seeing with > 2 cpus (at least AMD): https://mail.gna.org/public/adeos-main/2010-08/msg00000.html
mozmck: sounds like it
although from your stories it's more frequent than every 100 boots
another thought.. what if we limit CPUs to 2 ?
that was close - I almost got sucked into the latest g33 debate
come on you know you want to :)
has all been said before
The g33.1 documentation says the final move is 'An unsynchronized move back to the original coordinate.' Is it a rapid or a feed?
now when someone says 'fudge' the threading cycle to make tapered threads - is that because they don't know how to use math?
a spec for a tapered thread specifies the pitch a certain way - to actually cut it you need to program it a different way
you need to know the tiniest bit of trig to program the tapered thread (although you also need the same amount of trig to calculate the endpoints to get the taper before you thread it)
that is what I would think
for a thread that measures 12tpi when you're measuring 20 degrees from it, you get 12/cos20 along it
as I'm sure you know... :-)
skunkworks: besides the unintended change to axis.py, did you find that the "commanded spindle speed" change worked for your needs?
Yes - I don't see any issue with it. (I have no problem multiplying it by 60 for my needs)
solves my issue
(of not knowing the commanded spindle speed)
Thanks again for that. You're a life saver!
in that case I'll stick it on master
jepler- is now known as jepler
EMC: 03jepler 07master * ra1c66d4949f1 10/src/emc/motion/ (control.c mot_priv.h motion.c): Put commanded spindle speed on a hal pin