Guest713 is now known as skunkworks_
[Global Notice] Hi all! We experienced some rather heavy ddos attacks earlier this morning causing quite a lot of disturbance to the network, the problems should be under wraps now (thanks to the OSL and NERO) and we apologise for any inconvenience caused. Hope you have a nice day and thank you for using freenode!
cradek_ is now known as cradek
fenn_ is now known as fenn
EMC: 03cradek 07TRUNK * 10emc2/tests/ccomp/lathe-comp/expected: w tool lengths changed this output. new output is correct.
EMC: 03lerman 07TRUNK * 10emc2/src/emc/rs274ngc/interp_read.cc: fix bug:  comments in O-call lines disrupt parameters
EMC: 03lerman 07TRUNK * 10emc2/src/emc/rs274ngc/interp_convert.cc: fix bug: PRINT command does not evaluate named parameters correctly.
hmmm. cradek, I just had a thought, and you can test it since you have a stepper machine
of course, I could be forgetting some old conversation where this idea was rejected
hmmm. damn. it's not as easy as I want :(
the brainstorm was that stepgen shouldn't be necessary in EMC
freqgen should be able to do the job, because motion already does accel profiles
you're talking hooey again
SWPadnos: but freqgen only gives you vel feedback
not position feedback
so if you want to do it this way, you need a PID, and a counter on the steps
yeah, that's one of the places where you get more HAL complexity
and there's no gain for users
ddt on motion output, counter on feedback should do it
except that you're back at square 1, where they need to tune stepper systems
the gain is that the confusion surrounding STEPGEN_MAX* settings goes away
which is something we gladly stepped away from emc1
small gain :)
dude, talk to jmk, and leave my stepper machine out of it
I'd advice against that
he'll get the biggest trout in a 500 miles radius
and slap you silly with it
luckily he's 700+ miles from me :)
I'm sure he'd love to hear about how everyone should change around what works so well right now
cradek: he already plans to do that
but that's a different topic :)
you mean the trout thing?
well, this was one of those thoughts that comes to you when you're preparing breakfast (at 3:00 in the afternon)
* cradek is so lost
no, making all users change configs
changing everything :)
ah, nothing wrong with that, if it's for a good reason
cradek: changing axis.* pins from motion with joint.*
like to make max work better
SWPadnos: you can run stepgen without setting maxvel or maxaccel; they default to "infinite". but skunkworks tested and found that specifying a finite accel "worked better"; I don't know why or remember the specifics of what seemed better to him.
I think infinite vels especially together with backlash moves will result in bad things for the motor
the real problem there is when the MAX_* for the TP are actually at the same value as the stepgen effective max (which could be limited due to BASE_PERIOD)
you won't get a warning then..
with an finite accel - My machine would not stall.. With an infinite accel - my machine would constantly stall during rapids.
(running it at the edge of usefulness)
(pushing the envelope)
I think SWPadnos had tried to explain to me why this was probably happening - but I don't remember why
me either :)
actually, I may remember
there was a difference between zero accel, "finite" accel, and really huge accel (effectively infinite)
I think the deal was that with 0, there is no accel applied - stepgen just goes to the new frequency immediately
if the accel limit is high enough that stepgen can get there in one servo cycle, then the make_pulses routine will actually smoothly ramp to the new frequency (within a single servo period)
good night all