would we give cvs commit access to someone who has contributed an AXIS translation in the past and would like to continue?
I would think yes, if that was the easiest way for the person to contribute
for doing just a translation is it the easiest way?
He may also find that things are not marked in the source
oh well, it's night time here...
let's talk about it tomorrow
Here's what I'm thinking of adding to homing: http://emergent.unpy.net/sandbox
sounds good except I don't understand the name of the first one, I suggest SHARED_HOME_SWITCH=boolean
it's hard to be self-documenting and terse both
HOME_SWITCH_SHARED? I think it should have a HOME_ prefix...
is that the only way it's useful (shared)?
it's all I can think of right now
what do you think of HOME_SEQUENCE?
I think it's good enough for most any cartesian machine
though if you have a regular 3-axis mill with some fixtures you not only want to be sure that Z has been homed before you home X and Y, you want it to be at a set position..
as a way to allow a "home all" button I think it's sufficient
right I was just in the process of typing that.
before I allow axis N to home I need axis 0..N-1 in their home *positions*, not just homed
but that's not a simple gui hack.
there's a flag for "axis is in home position", at least in the motion controller
I didn't know that
this would all have to be in the motion controller. Otherwise I could jog X while Z is homing and screw it up. (it should probably abort, or disallow the jog, or something)
I don't know how complex or foolproof you want to make it
I don't know either
I want a HOME ALL button that will work on a reasonable cartesian machine
the SHARED_HOME_SWITCH is simple, and it's obvious how to do it, and it's very useful to prevent a dangerous and common thing from happing
I think sequential homing (home all when using combined switches) is a ball/can of wax/mud/worms
most of me wants to say "if you want home-all, use separate home inputs (and have a setup that can't cause a crash)"
e.g. you better be above your fixtures when you hit it, and Z better home "up"
but even with switches separate, you can prevent a certain crash by homing Z (up) first
so now I'm back to thinking it's a good idea (assuming you use "homed and in the home position" criteria)
as long as HOME_SWITCH_SHARED is set properly, I don't see that the shared/unshared business matters
AT_HOME is cleared when you jog in free mode, but not if
you do a coordinated move... perhaps that is the intended
\todo FIXME - I'm not sure AT_HOME is being reported correctly.
I'd want my sequence to be Z, then X & Y together
that requires separate X,Y switches
yes, but you can do the second-best Z, then X, then Y (or vice versa with X and Y)
so some sequences are just illegal if some switches are shared
in this machine you could share Z and X switches, and have sequence Z, XY
yes, and it would be up to the ini author to make sure it was OK
your flags allow that, right?
ok I think this sounds really good then
assuming AT_HOME works of course
[AXIS_0] SHARED=1 SEQUENCE=1 [AXIS_1] SHARED=0 SEQUENCE=1 [AXIS_2] SHARED-1 SEQUENCE=0
I think you'll have to put it all in the motion controller
I mean the home-all smarts
I was hoping I could avoid it
If you have a good spec (I think you do) I bet jmk will help
he's talked about this kind of thing before
I think the first implementation could be in userspace
I don't think you have access to at-home
hmm maybe I don't
I can still compare the position to the inifile HOME_OFFSET
or something janky like that
if SEQUENCE=-1 then this joint is not homed by the HOME ALL sequence
on another note, I still want "two-way homing" (search both ways for limit switches, set soft limits inside them, also home
or, at least some way to set soft limits at runtime
think of three buttons like margins on a typewriter: set this as the left soft limit, set this as the right soft limit, temporarily override the soft limits
so before going to HOME_OFFSET you'd go in the same direction until you closed the (other) limit switch, set the soft limit to just short of that value, and go the other way to HOME_OFFSET?
would it make sense to allow axes to be excluded from the HOME ALL sequence (e.g. I don't have any switches on my A axis but I want to home XYZ)?
yes I think that would do it, assuming you home on one limit switch
jepler: without switches it just zeroes, seems like you would want that when you "home all"
but OTOH allowing exclusions doesn't hurt anyone
I imagined that at least one limit would be "fixed" (e.g., the chuck on your lathe doesn't move), and that's the side where the home/limit switch is
yes I think you're right
I wonder if there's a (useful) machine where both limits move WRT home
I mean hard limits here
SWP_away is now known as SWPadnos
hi jepler - how are things?
when you're back on the ground I want to talk about getting some access to the webserver to automatically update the html and pdf documentation
ok. I may be able to do that from here
there's no hurry
ok. I may not do that from here ;)
odd thing.. had an update on dapper today
mostly linux image, and headers for the stock kernel
and the updater complained it cannot be verified
huh that is a surprise
maybe it's an evil package put there by a hacker
jepler: thought that too
did you have an update on the stock kernel lately?
linux-image-2.6.15-26-386 is the package name, 2.6.15-26.47 version
I found it odd that the changelog doesn't say anything at all
alex_joni: I only have an ubuntu system handly
I'll ask in ubuntu-kernel
jepler: I think it was because of connectivity loss
I did an apt-get update
and now the packages are validated
alex - this? http://www.electronicsam.com/images/KandT/update.png
So it is safe? :)
although it's still odd.. if you go to 'show details'
there's nothing in the changelog
it's probably safe
I see .47 is the latest version
yah - nothing in the change log here also. It has a discription though
sometimes the changelogs show up later
jepler has been busy!
thanks for noticing
the home all stuff looks pretty good
reading back on the other channel I saw you trying to troubleshoot something
did you figure it out>
no -- I was still seeing some kind of random error on startup
it would happen once in awhile
I forget exactly what the message was but you should see it in the scrollback