dareposte: what are you basing your "I need 3000 lbs" on?
you have quite a toolpost if you are willing to put a ton and a half on the tool
is there a HAL signal for "currently running the job?"
so if you hit the "stop" button (not the estop) it turns off the axis enable?
sorry, I thought this was a game of free association
why do you want it, would something like a spindle on signal work?
I always feel bad when I'm the only one answering questions since I'm an idiot
yo yo ! anybody in the mood to help a n00b? :)
Just getting things running for the first time tonight. Running a G540 with EMC2 on 8.04, on an X2.
my leadscrew pitch is set correctly in EMC2, but I'm not moving the right distance. Does my microstepping have anything to do with this , if that value is set wrong?
and no - i haven't measured "exactly" how far I'm off yet -but its a magnitude.
measure and it might tell you easier than we can
if you are off by exactly 5:1, 2:1, etc, that will point you in the right direction
archivist: shouldn't you be sleeping?
I guess the question is - will that value have any bearing on distance travelled?
eric_unterhause1, sleep is for wimps
and is that value something i need to look at my steppers for, or my stepper controller for?
assuming it's not a steps/rev problem
yeah step/rev is correct.
making a change now, will know momentarily :)
sweet that did it. thx.
now to try another run :)
that got me in the ballpark. thx guys
now to start measuring and seeing what my backlash looks like. outta here. l8r
heyo.. I'm trying to write some gcode that will turn my laser on and off without interrupting motion
we've tried just about every signal.. z-pos, spindle, tool, coolant.. and they all cause a discontinuity in x/y motion
this is emc2
what about turning it on anytime the machine is in g1?
and off in g0.
although i don't get why Z pos would do it.
would cause discontinuity, that is
can we send that to a parallel port pin?
oh, i haven't a clue
you'll have to ask someone who understands emc
there's got to be SOME way to turn that into an output
there was somebody on here in the last couple of weeks that was trying to do this
we've tried various ways of mapping on/off to the z axis and we always either get a discontinuity or inaccurate timing
jmkasunich: I am basing it on the published specs of the haas tl-1
although now that i think about it, that is probably their "peak" servo output
and not the continually rated output
i don't particularly like the haas, but it has the spec's conveniently published
and it seems to be more than adequate for the job
eric_unterhause1: jedediah_ is working with Optic, that might have been who you are thinking of :)
* hypa7ia is lurking
elmood is probably going to help me build another PIC for the laser that handles all the realtime stuff
sleep now! nite folks :)
jedediah_: the only thing I know is using M64/65, but you need emc2-2.3.0-beta for that
sorry I had to ditch out yesterday, I never did figure out if the "maximum thrust" listed in manufacturer's machine specs was the servo peak output, or if it was maximum sustained output
for example: http://haascnc.com/specs.asp?ID=SL-20&mdl=SL-20&webid=LATHE_SL#CNCLatheTreeModel
for the Haas SL-20 it lists X maximum thrust as 2400 lbs
and Z as 2400 lbs
no Z as 3700 lbs
so since I don't have the benefit of a big R&D facility or test bed, I just want to duplciate what they have done in terms of servo and screw sizing
under the assumption that it is a typical and acceptable setup for most cnc turning
so if it's peak output, then the servos could be sized at 700 in-oz peak
which seems pretty reasonable
but if its continuous output, the servos would have to be sized for 700 in-oz continuous, which is much larger servos
fenn: how do you know?
if i were a specman
and someone said 'write a brochure with our technical specs on it'
then i'd use peak values wherever possible
do you know what frame size servos are common on that type of equipment?
the only servos i could find with enough torque were NEMA56's
which seems waaaay too big
i know the servos on the mazak were about 6 inches diameter
maybe they are NEMA56 sized then
the haas looks quite a bit smaller though
can't you just go look at one?
i could if i had one
i think there's a dealership in cinci
i don't particularly care about the haas, just using it as an example
their spec is one of the easier ones to find
one of the bridgeports at work has a CNC kit on it
and the servos look bigger than 700 in-oz peak though
[19:46:02] <dareposte> http://www.flashcutcnc.com/beta/php/bridgeportRetrofitKits_specsServo.php
that says 520 in-oz continuous
for a bridgie type conversion
We got our engraver working!
made anything yet??
It needs some tweaking
We burned some text into cardboard. :)
We need to find a way to turn the laser on and off without emc stopping the motion
Were using z axis now
Optic: 10:25 < alex_joni> jedediah_: the only thing I know is using M64/65, but you
need emc2-2.3.0-beta for that
but the switching can only happen when you have a different move
so if you're going from X0 to X10, and want to switch laser on at 2.54
then you need a move G1 X2.54
or something like that
Optic: can't you use the spindle on and off to control your laser?
oh you would have to stop for that...
Optic: Or coolant/mist on and off ?
that would still stop motion...
m64/65 doesn't stop?
* JymmmEMC pokes alex_joni
I think you missed JymmmEMC
need a longer stick
Bigjohn: those commands affect movement
We did some tests
We also tried spindle speed
And tool change. :)
I kind of thought that after I typed it
what you really need is two seperate controls one to move your carriage and one to fire the laser I guess
Emc is so close to being the right thing
your printing with a laser more or less right?
So speed affects kerf
we need a printer driver for EMC :)
err.. sorry :)
no, in 2.3.x M64/65 will be seamless integrated
that means they don't screw up motion or blending
That is *perfect*
Are they in any betas?
Optic: pm (private message)
alex_joni: is m64/65 changed in real time now?
BigJohnT: it was before too
I mean in 2.2.x
but it was poorly implemented, and it broke blending
which caused moving hickups
ok then the manual is wrong
well.. to be frank in 2.2.x you can only use M62/63 (which are the ones that break blending), M64/65 didn't do anything (they were implemented at one point, then reverted when the TP got rewritten)
but in 2.3.x you have 62/63 which get issued immediately when motion receives them
and 64/65 which get queued and will get issued when the next move starts
so is this wrong alex_joni http://www.linuxcnc.org/docview/devel/html//gcode_main.html#sec:M62-to-M65:
err.. that is right
* alex_joni was backwards
does m64/65 still break blending?
I think so
but one would have to test it to make sure
but I don't think it can work otherwise
* alex_joni goes look at the code
what is the use case for m64/65?
i dont see how it could be useful to turn something on at some random time whenever the interpreter feels like it
fenn: not wanting to use a motion with the change
maybe MDI for debugging
* BigJohnT goes out to plasma more deer critters out
good night all